Closed GoogleCodeExporter closed 9 years ago
Install the latest Launcher over SSH. You have a duplicate I believe.
Instructions
are on the issues trac, please search
Original comment by Sam.Nazarko
on 22 Dec 2009 at 3:30
I also have the two Launcher menus on two ATVs.
Installed with patchstick 3.0.
Original comment by anoch...@gmail.com
on 22 Dec 2009 at 7:28
Looking into it.
Original comment by Sam.Nazarko
on 23 Dec 2009 at 1:27
You did run the patchstick on a fresh aTV right? Or did you already have an old
version of Launcher on the Apple TV and you re-applied the patchstick.
Original comment by Sam.Nazarko
on 23 Dec 2009 at 1:28
I initially tried installing by using Mac OSX version not realizing it was
incompatible
with ATV 3.0. It ran through the install sequence and appeared to work but no
menu was
added. I revisited the web site, saw that the XP version was compatible with
ATV3 and
re-ran the installation process using the one for XP.
Original comment by gftray...@gmail.com
on 23 Dec 2009 at 2:00
Restore your Apple TV to factory settings, re-run the patchstick and tell me if
the
problem persists.
Oh, and the Mac version is compatible but as you said the software is not. It
must
be updated which requires jumping through some hoops.
Original comment by Sam.Nazarko
on 23 Dec 2009 at 3:18
I had one ATV factory reset and one updated ATV. Two launchers on both machines
with
patchstick 3.
Original comment by anoch...@gmail.com
on 23 Dec 2009 at 6:49
I figured it out:
The duplicate Launcher's appear when you update Launcher (as you were
instructed in
the app). This is because it is downloading and installing a lower version. I
will
speak to the dev of XBMCLauncher about this. It is not a fault with our
patchstick.
Original comment by Sam.Nazarko
on 23 Dec 2009 at 7:23
Here's what you should do for now:
Restore aTV
Re-patch
Do not update Launcher until it says it is safe to do so here.
And you will have no dupe-menus.
Original comment by Sam.Nazarko
on 23 Dec 2009 at 7:33
Sorry it was an issue at our end. Launcher was being deployed in two seperate
directories. This was because Davilla did not extract the XBMCLauncher
directory. It
is completely fine to update now.
If you have experienced this problem go to the menu and download the latest
Launcher. The install script has been updated to fix this issue. However future
installations will not experience this issue at all due to new images in
revision
153. These new versions will be automatically downloaded by atv-win-3.0
Original comment by Sam.Nazarko
on 24 Dec 2009 at 4:18
Original issue reported on code.google.com by
gftray...@gmail.com
on 22 Dec 2009 at 3:23