I've been trying out disabling some services / bloat and seeing what side effects there are.
So far here is what I've disabled:
Code:
[email protected]:/ # pm list packages -d
package:com.amazon.precog
package:com.amazon.recess
package:com.amazon.whisperplay.contracts
package:com.amazon.bueller.photos
package:com.amazon.kindle.cms
package:com.amazon.client.metrics
package:com.amazon.device.software.ota
package:com.amazon.whisperlink.core.android
package:com.amazon.application.compatibility.enforcer
package:com.amazon.whisperplay.service.install
package:com.amazon.device.software.ota.override
package:com.amazon.bueller.music
package:com.amazon.tv.launcher
If you need to use the FireOS Settings you *can't* disable 'com.amazon.tv.launcher' as when that is disabled it prevents you from accessing the system settings which you could get into via FireStarter or TV Launcher. But when this is disabled there is an android prompt that lets you pick your new default launcher and until you pick 'use always' each time you press the home button you can pick between your various launchers before deciding on the one to use, once you pick one then the home button goes back to normal behavior. So now my default launcher is TV Launcher, with FireStarter kept so that I can still access app settings to delete cache, clear data, uninstall, force stop, etc... and I've also got the Android TV leanback launcher installed but haven't been using it.
I do have rbox's FTV mod apk for xposed installed (not sure exactly what it is called off the top of my head) so its possible that this may also play a role in the home behavior.
Once I have root on my FireTV Stick when rbox is able to get the custom recovery and pre-rooted ROMs done I plan to disable those same services as the Stick is terribly slow on 5.0.x (still on 5.0.3 dev preview, thanks amazon :-/ ) as I believe the usability of the device will improve enough that I can actually use it again.
Does anybody know what "com.amazon.device.software.ota.override" is for? Sounds like it needs to be disabled like "com.amazon.device.software.ota".
I'm not sure what it is but I did disable it and haven't had any side effects.
And I did figure out that you can choose to temporarily disable the Amazon launcher and then pick a new default (like TV Launcher) and then re enable Amazon launcher and then it will no longer run at startup and you can just jump into it for prime usage as needed. I also did update the stick to 5.0.5.0 and rooted it with King root and disabled the same services on the stick.
I can't disable the ime. Everything becomes broken!
Iamandrewj said:
I can't disable the ime. Everything becomes broken!
Click to expand...
Click to collapse
"ime"? What is the full package name?
com.amazon.tv.ime
This is the package we used to to disable in fire os 3. It's to disable the on screen keyboard.
Ludacrisvp said:
I've been trying out disabling some services / bloat and seeing what side effects there are.
So far here is what I've disabled:
Code:
[email protected]:/ # pm list packages -d
package:com.amazon.precog
package:com.amazon.recess
package:com.amazon.whisperplay.contracts
package:com.amazon.bueller.photos
package:com.amazon.kindle.cms
package:com.amazon.client.metrics
package:com.amazon.device.software.ota
package:com.amazon.whisperlink.core.android
package:com.amazon.application.compatibility.enforcer
package:com.amazon.whisperplay.service.install
package:com.amazon.device.software.ota.override
package:com.amazon.bueller.music
package:com.amazon.tv.launcher
If you need to use the FireOS Settings you *can't* disable 'com.amazon.tv.launcher' as when that is disabled it prevents you from accessing the system settings which you could get into via FireStarter or TV Launcher. But when this is disabled there is an android prompt that lets you pick your new default launcher and until you pick 'use always' each time you press the home button you can pick between your various launchers before deciding on the one to use, once you pick one then the home button goes back to normal behavior. So now my default launcher is TV Launcher, with FireStarter kept so that I can still access app settings to delete cache, clear data, uninstall, force stop, etc... and I've also got the Android TV leanback launcher installed but haven't been using it.
I do have rbox's FTV mod apk for xposed installed (not sure exactly what it is called off the top of my head) so its possible that this may also play a role in the home behavior.
Once I have root on my FireTV Stick when rbox is able to get the custom recovery and pre-rooted ROMs done I plan to disable those same services as the Stick is terribly slow on 5.0.x (still on 5.0.3 dev preview, thanks amazon :-/ ) as I believe the usability of the device will improve enough that I can actually use it again.
Click to expand...
Click to collapse
Thanks for your post. I followed your instructions at the same as rooting my Fire Sticks for the first time, but I've found that no Amazon Instant Videos will play now.
Would any of these disabled services affect that, or is it maybe just because it is rooted that Amazon won't allow video playback? Just trying to pinpoint the problem.
If you disable com.amazon.tv.launcher that will prevent you from accessing the menu to see any prime videos.
Otherwise, no those shouldn't have an impact on playing prime. I've had no issues with prime video playing.
I do have com.amazon.tv.launcher enabled but not set as my home screen. Once you disable it as long as you have 2 other "launchers" android will ask you which one you want to use. Then you pick the new default you want and then you can reenable the Amazon launcher and still have the launcher you want as default.
Ludacrisvp said:
If you disable com.amazon.tv.launcher that will prevent you from accessing the menu to see any prime videos.
Otherwise, no those shouldn't have an impact on playing prime. I've had no issues with prime video playing.
I do have com.amazon.tv.launcher enabled but not set as my home screen. Once you disable it as long as you have 2 other "launchers" android will ask you which one you want to use. Then you pick the new default you want and then you can reenable the Amazon launcher and still have the launcher you want as default.
Click to expand...
Click to collapse
Thanks for the reply, but I didn't disable that one, because of your previous warning.
What version do you have installed?
Ludacrisvp said:
I've been trying out disabling some services / bloat and seeing what side effects there are.
So far here is what I've disabled:
Code:
[email protected]:/ # pm list packages -d
package:com.amazon.precog
package:com.amazon.recess
package:com.amazon.whisperplay.contracts
package:com.amazon.bueller.photos
package:com.amazon.kindle.cms
package:com.amazon.client.metrics
package:com.amazon.device.software.ota
package:com.amazon.whisperlink.core.android
package:com.amazon.application.compatibility.enforcer
package:com.amazon.whisperplay.service.install
package:com.amazon.device.software.ota.override
package:com.amazon.bueller.music
package:com.amazon.tv.launcher
If you need to use the FireOS Settings you *can't* disable 'com.amazon.tv.launcher' as when that is disabled it prevents you from accessing the system settings which you could get into via FireStarter or TV Launcher. But when this is disabled there is an android prompt that lets you pick your new default launcher and until you pick 'use always' each time you press the home button you can pick between your various launchers before deciding on the one to use, once you pick one then the home button goes back to normal behavior. So now my default launcher is TV Launcher, with FireStarter kept so that I can still access app settings to delete cache, clear data, uninstall, force stop, etc... and I've also got the Android TV leanback launcher installed but haven't been using it.
I do have rbox's FTV mod apk for xposed installed (not sure exactly what it is called off the top of my head) so its possible that this may also play a role in the home behavior.
Once I have root on my FireTV Stick when rbox is able to get the custom recovery and pre-rooted ROMs done I plan to disable those same services as the Stick is terribly slow on 5.0.x (still on 5.0.3 dev preview, thanks amazon :-/ ) as I believe the usability of the device will improve enough that I can actually use it again.
Click to expand...
Click to collapse
Where can I get leanback launcher? Will it work on fire stick? I'm about to disable all the services you recommend.
Will you upload somewhere the android leanback launcher? Many thanks.
Enviado desde mi A0001 mediante Tapatalk
Ludacrisvp said:
"ime"? What is the full package name?
Click to expand...
Click to collapse
i too cannot disable com.amazon.tv.ime or I will get a black screen on my aftv2. On my aftv1 it disables without issue.
Antieco said:
Where can I get leanback launcher? Will it work on fire stick? I'm about to disable all the services you recommend.
Will you upload somewhere the android leanback launcher? Many thanks.
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
I was able to install the Leanback Launcher on my stick a few weeks back but it must be installed / converted as a system app for it to run.
dave157 said:
I was able to install the Leanback Launcher on my stick a few weeks back but it must be installed / converted as a system app for it to run.
Click to expand...
Click to collapse
Would you share the apk please
Enviado desde mi A0001 mediante Tapatalk
Sure, no problem. I just got home from work, give me an hour or so and I'll post a link and the procedure I used. FYI, I was also able to load Google Play (Leanback) but wasn't able to download/update apks for some reason. It would go through the whole procedure (asking you to accept permissions, etc...) but when the download started , Play store would crash.
I'm definitely more exhausted from work than I thought I was, but I promise to have the link up tomorrow morning (9-10 am East. US)
dave157 said:
I'm definitely more exhausted from work than I thought I was, but I promise to have the link up tomorrow morning (9-10 am East. US)
Click to expand...
Click to collapse
No worries, thanks.
Do I need to install Google play services?
Enviado desde mi A0001 mediante Tapatalk
I do have Play Services installed as well as the other Google apk's (Login Mgr, Svc Framework). After following sconnyuk's guide to rooting the stick (http://forum.xda-developers.com/showthread.php?t=3399298) and then disabling ota/bloat/services, I installed the google apps and the Android TV Launcher (Leanback). The launcher will not run until converted to a system app. https://www.dropbox.com/s/1fntiva8r5ilj6d/FireStick Leanback.zip?dl=0
I found this list here in the for of a script.
I disabled everything in this script except the home related section.. Will tinker with it later some.
Basically if you are not using your firetv for anything amazon related.. This list is fine.
Notice in the script the # before some commands. These will not initiate in script by default and I did not disable those. A few I did but you got to pick and choose. They are not meant to just go disabling on a whim.
Also o didn't run the script.. I wen through and manually added each one in terminal on my fire TV
This is more for people who are not amazon subscribers and just don't want all the amazon junk. If you use it, some of these may not be for you.. Me though, I wanted to strip amazon from the device as much as possible.
https://github.com/esc0rtd3w/firestick-loader/blob/master/scripts/debloat/bloat-disable.sh
There is the link. And that guy ets the credit. I just stumbled into it. It is a more expansive list if you are wanting to remove most of the amazon from your fire tv
adam_ky said:
I found this list here in the for of a script.
I disabled everything in this script except the home related section.. Will tinker with it later some.
Basically if you are not using your firetv for anything amazon related.. This list is fine.
Notice in the script the # before some commands. These will not initiate in script by default and I did not disable those. A few I did but you got to pick and choose. They are not meant to just go disabling on a whim.
Also o didn't run the script.. I wen through and manually added each one in terminal on my fire TV
This is more for people who are not amazon subscribers and just don't want all the amazon junk. If you use it, some of these may not be for you.. Me though, I wanted to strip amazon from the device as much as possible.
https://github.com/esc0rtd3w/firestick-loader/blob/master/scripts/debloat/bloat-disable.sh
There is the link. And that guy ets the credit. I just stumbled into it. It is a more expansive list if you are wanting to remove most of the amazon from your fire tv
Click to expand...
Click to collapse
Excellent find. Will be using this on my devices as I only have a handful of things disabled, I wonder if the stick is more responsive with all this disabled.
Related
I was trying to fix xbmc by uninstalling, I have xbmc launcher auto loading xbmc but now that I uninstalled it is stuck on a black screen giving me a message that it can't find xbmc. I can't load anything else now. Help, what can I do?
Zorak27 said:
I was trying to fix xbmc by uninstalling, I have xbmc launcher auto loading xbmc but now that I uninstalled it is stuck on a black screen giving me a message that it can't find xbmc. I can't load anything else now. Help, what can I do?
Click to expand...
Click to collapse
My guess is you need to do a factory restore. First post here tells you how:
http://forum.xda-developers.com/showthread.php?t=2799779
And here is my recommendation. Do NOT use XBMC as a launcher for your AFTV. While that saves you 1 click, the bad points seem to out weigh that bit of laziness. Use FiredTV as the laucher, move xbmc so it's the first icon.
good luck.
Is it not possible that you install XBMC via adb and then restart?
The problem is the launcher prevents the FTV from rebooting so ADB isn't going to help. You need to boot into recovery and then do a factory restore. Guide here: http://www.aftvnews.com/how-to-unbr...nd-factory-reset-the-amazon-fire-tv/#more-898
I did this myself. Duh.
There is a newer version of XBMC Launcher available from Google Play (http://www.aftvnews.com/how-to-unbr...nd-factory-reset-the-amazon-fire-tv/#more-898) which fixes this issue.
See What's New for info.
jmerrilljr2 said:
The problem is the launcher prevents the FTV from rebooting so ADB isn't going to help. You need to boot into recovery and then do a factory restore. Guide here: http://www.aftvnews.com/how-to-unbr...nd-factory-reset-the-amazon-fire-tv/#more-898
I did this myself. Duh.
There is a newer version of XBMC Launcher available from Google Play (http://www.aftvnews.com/how-to-unbr...nd-factory-reset-the-amazon-fire-tv/#more-898) which fixes this issue.
See What's New for info.
Click to expand...
Click to collapse
Blonde question of the day: if I have SPMC installed (which replaced the AFTV launcher as default) will I be able to install this launcher for the dreaded day when I mess up SPMC and can't get into a launcher? Ie...will it still install and possibly prompt me to chose a default launcher (again)?
I assume this would be similar to deleting the default preference in Settings.
Ipse_Tase said:
Blonde question of the day: if I have SPMC installed (which replaced the AFTV launcher as default) will I be able to install this launcher for the dreaded day when I mess up SPMC and can't get into a launcher? Ie...will it still install and possibly prompt me to chose a default launcher (again)?
I assume this would be similar to deleting the default preference in Settings.
Click to expand...
Click to collapse
Well SPMC comes in two flavors -- with or without the built in launcher.. If you want to use the XBMC launcher you need to have the non-launcher version of SPMC installed. Otherwise when you use your Home button the system gets confused.
When you launch the XBMC Launcher, you get a screen asking you to select which flavor of XMBC is your default. That way you can toggle back and forth with no issues, as long as SPMC is the non-launcher version.
jmerrilljr2 said:
Well SPMC comes in two flavors -- with or without the built in launcher.. If you want to use the XBMC launcher you need to have the non-launcher version of SPMC installed. Otherwise when you use your Home button the system gets confused.
When you launch the XBMC Launcher, you get a screen asking you to select which flavor of XMBC is your default. That way you can toggle back and forth with no issues, as long as SPMC is the non-launcher version.
Click to expand...
Click to collapse
Ah...now it makes sense. I must have taken for granted that SPMC only comes with built in launcher - I checked the semperpax page and see the difference.
Probably should try and change my install at some point, because I resisted putting the custom recovery (I just don't want to mess up Netflix SHD+DD....) therefore I have no system backup, just SPMC backup.
Zorak27 said:
I was trying to fix xbmc by uninstalling, I have xbmc launcher auto loading xbmc but now that I uninstalled it is stuck on a black screen giving me a message that it can't find xbmc. I can't load anything else now. Help, what can I do?
Click to expand...
Click to collapse
I'm probably too late, but it it's getting to the point of saying it can't find XBMC, then ADB should be up. Simply uninstall XBMC Launcher via adb using "adb uninstall se.blunden.xbmclauncher".
nyder said:
And here is my recommendation. Do NOT use XBMC as a launcher for your AFTV. While that saves you 1 click, the bad points seem to out weigh that bit of laziness. Use FiredTV as the laucher, move xbmc so it's the first icon.
Click to expand...
Click to collapse
What bad points? It looks like the OP's problem was caused by a bug in a third party app (which appears to have since been fixed), not by XBMC itself. If you run my XBMC build or SPMC, both of which have launcher capabilities built in, you won't have this issue.
elmerohueso said:
I'm probably too late, but it it's getting to the point of saying it can't find XBMC, then ADB should be up. Simply uninstall XBMC Launcher via adb using "adb uninstall se.blunden.xbmclauncher".
What bad points? It looks like the OP's problem was caused by a bug in a third party app (which appears to have since been fixed), not by XBMC itself. If you run my XBMC build or SPMC, both of which have launcher capabilities built in, you won't have this issue.
Click to expand...
Click to collapse
Bad points like:
XBMC takes up a bit of memory, so you can't always launch other apps (mostly games currently take up the big memory) from XBMC and if you are using it's launcher, then you are a bit sol there.
XBMC messing up and the launcher still takes you to it.
Uninstall XBMC without uninstalling the launcher messes you up (though I heard they fixed that, but people don't always upgrade to the latest version when it's not automatic).
You are missing out on other crap your AFTV can do if you just go into XBMC all the time.
Though I guess if you are a dev of an XBMC app, you might be more into selling the idea that the AFTV is a great XBMC machine and that is all you need it for.
But I understand, people just want it for a XBMC player, and they probably install the software and then leave it alone because it works. I don't blame them. Somethings when I get it to work, that is good enough. But that doesn't change my opinion that using a launcher to just load up the 1 program is silly and at the least, handicaps your system.
But tbh, I haven't used a xbmc launcher, so i don't know the specifics. What happens if you exit of out XBMC, does it just load it back up, or does it send you to the original amazon launcher? If the former, then crappy design, if it's the latter, then cool, that at least would clear up one or two of my bad points.
Okay, here's a bad point: http://forum.xda-developers.com/fire-tv/help/blocked-getting-settings-tabs-t2907505
Sounds to be that maybe a xbmc launcher wasn't really thought out by those who programmed it. Still going to say there isn't any bad points?
nyder said:
Bad points like:
XBMC takes up a bit of memory, so you can't always launch other apps (mostly games currently take up the big memory) from XBMC and if you are using it's launcher, then you are a bit sol there.
Click to expand...
Click to collapse
I used to run into this every now and then, but some tweaking and setting my FTV to automatically reboot nightly seems to have cleared up the issue.
nyder said:
XBMC messing up and the launcher still takes you to it.
Uninstall XBMC without uninstalling the launcher messes you up (though I heard they fixed that, but people don't always upgrade to the latest version when it's not automatic).
Click to expand...
Click to collapse
The XBMC Launcher app is quite different from having XBMC with launcher intent built in.
If you have the XBMC Launcher app, that app itself is actually acting as your home launcher, and it then calls XBMC to launch. The OP's problem (and the issue in the other thread) is that the XBMC Launcher app had a bug where it would still try to act as the launcher and would freak out if it couldn't find XBMC (to the credit to that app's developer, that bug has been fixed).
If you have a build of XBMC that has launcher intent built in, there's no additional app needed, and there's no chance of a similar problem.
nyder said:
You are missing out on other crap your AFTV can do if you just go into XBMC all the time.
Click to expand...
Click to collapse
You can still access the FTV launcher through the Apps/Programs menu in XBMC. Every other app is also accessible in XBMC's Apps/Program menu. So no, you're not missing out on "other crap". It's still there and easily accessible.
nyder said:
But that doesn't change my opinion that using a launcher to just load up the 1 program is silly and at the least, handicaps your system.
Click to expand...
Click to collapse
What handicapped these systems was (an old version of) the XBMC Launcher app itself, not XBMC. Not even a version of XBMC with built-in launcher intent.
nyder said:
But tbh, I haven't used a xbmc launcher, so i don't know the specifics.
Click to expand...
Click to collapse
Don't knock it 'till you try it. If you use XBMC a lot, I'd recommend trying XBMC for Fire TV (mine) or SPMC (made by Koying of team XBMC). No matter which version you run, though, you might like some of the tweaks in my XBMC repo.
elmerohueso said:
I used to run into this every now and then, but some tweaking and setting my FTV to automatically reboot nightly seems to have cleared up the issue.
The XBMC Launcher app is quite different from having XBMC with launcher intent built in.
If you have the XBMC Launcher app, that app itself is actually acting as your home launcher, and it then calls XBMC to launch. The OP's problem (and the issue in the other thread) is that the XBMC Launcher app had a bug where it would still try to act as the launcher and would freak out if it couldn't find XBMC (to the credit to that app's developer, that bug has been fixed).
If you have a build of XBMC that has launcher intent built in, there's no additional app needed, and there's no chance of a similar problem.
You can still access the FTV launcher through the Apps/Programs menu in XBMC. Every other app is also accessible in XBMC's Apps/Program menu. So no, you're not missing out on "other crap". It's still there and easily accessible.
What handicapped these systems was (an old version of) the XBMC Launcher app itself, not XBMC. Not even a version of XBMC with built-in launcher intent.
Don't knock it 'till you try it. If you use XBMC a lot, I'd recommend trying XBMC for Fire TV (mine) or SPMC (made by Koying of team XBMC). No matter which version you run, though, you might like some of the tweaks in my XBMC repo.
Click to expand...
Click to collapse
Thanks for the offer to try it, but no. I'm happy with my FireDTV launcher. I'm happy NOT running XBMC at the start, and I'm happy knowing that even if I uninstall XBMC (which i've done recently, to put in the kodi version), my system will still work right.
Anyways, I said my piece, I'm done with it. Hopefully we won't get many more post about the old launcher messing up peeps systems.
Thanks for all the useful info everyone, I ended up doing a factory reset, reroot, then installed a fresh xbmc. I was unable to connect to adb until the factory reset. Sticking with fired tv for now.
Using the newest Cusom Pre-Rooted Rom (51.1.5.0_515030720) and newest SPMC (14.2.0), the Screen Saver works great but the transition from Screen Saver to Sleep never happens! It just stays on Screen Saver forever (until pressing anything).
* I can't tell if it's only for SPMC or the entire system (SPMC is my Launcher as well).
* When choosing Sleep from the Fire TV Settigs Menu, sleep works great.
I'm started to worry because the Fire TV is always ON and never sleeps...
A full factory reset is nearly out of the question - I have worked tons of hours to configure and mod my system to the way it is finally ideal...
Any ideas?
Recently I had an issue with my FTV not sleeping. Think it might have been due to certain Google apps not working properly due to Google Play Services auto-updating itself to v7.3.2.9 (v7.0.9.9 is the latest "good" version).
Anyways to figure out my issue I used apps like Titanium Backup and ROM Toolbox Pro (App Manager) to freeze various apps, and see if the FTV would go to sleep afterwards. Eventually I figured it out, and now my FTV sleeps like a baby.
To add my 2 cents, knowing nothing about whats installed or how your FTV is setup etc. I noticed when I updated, the new netflix (white icon) never allows the device to sleep! you have to EXIT manually before it will sleep. Also SPMC 14.2 is bugged and unstable due to an early backport of seek steps that has many memery leaks and it will eventually crash over and over FYI.
Gaiosan said:
Using the newest Cusom Pre-Rooted Rom (51.1.5.0_515030720) and newest SPMC (14.2.0), the Screen Saver works great but the transition from Screen Saver to Sleep never happens! It just stays on Screen Saver forever (until pressing anything).
* I can't tell if it's only for SPMC or the entire system (SPMC is my Launcher as well).
* When choosing Sleep from the Fire TV Settigs Menu, sleep works great.
I'm started to worry because the Fire TV is always ON and never sleeps...
A full factory reset is nearly out of the question - I have worked tons of hours to configure and mod my system to the way it is finally ideal...
Any ideas?
Click to expand...
Click to collapse
Do you have Google Play installed?
MetalMan2 said:
Recently I had an issue with my FTV not sleeping. Think it might have been due to certain Google apps not working properly due to Google Play Services auto-updating itself to v7.3.2.9 (v7.0.9.9 is the latest "good" version).
Anyways to figure out my issue I used apps like Titanium Backup and ROM Toolbox Pro (App Manager) to freeze various apps, and see if the FTV would go to sleep afterwards. Eventually I figured it out, and now my FTV sleeps like a baby.
Click to expand...
Click to collapse
Actually now that I think about it, Google play has stop working as well! I get a white screen whenever entering it, should i downgrade my Google apps? Where can I get the apk? Thanks!
Skater4599 said:
To add my 2 cents, knowing nothing about whats installed or how your FTV is setup etc. I noticed when I updated, the new netflix (white icon) never allows the device to sleep! you have to EXIT manually before it will sleep. Also SPMC 14.2 is bugged and unstable due to an early backport of seek steps that has many memery leaks and it will eventually crash over and over FYI.
Click to expand...
Click to collapse
So which SPMC build should I use? Thanks!
krawhitham said:
Do you have Google Play installed?
Click to expand...
Click to collapse
Yes...
Gaiosan said:
Actually now that I think about it, Google play has stop working as well! I get a white screen whenever entering it, should i downgrade my Google apps? Where can I get the apk? Thanks!
Click to expand...
Click to collapse
There's a thread about Google Play Services auto-updating itself. This post has the APK for the appropriate version:
http://forum.xda-developers.com/showpost.php?p=60393176&postcount=17
You can't stop it from auto-updating again... I freeze Google Play Services when I don't need it, then defrost it when I do, to prevent it from updating.
MetalMan2 said:
There's a thread about Google Play Services auto-updating itself. This post has the APK for the appropriate version:
http://forum.xda-developers.com/showpost.php?p=60393176&postcount=17
You can't stop it from auto-updating again... I freeze Google Play Services when I don't need it, then defrost it when I do, to prevent it from updating.
Click to expand...
Click to collapse
By freezing Google Play Services, do you mean via Titanium Backup?
Axecaster said:
By freezing Google Play Services, do you mean via Titanium Backup?
Click to expand...
Click to collapse
Correct, or by some other app like ROM Toolbox Pro (App Manager).
MetalMan2 said:
Correct, or by some other app like ROM Toolbox Pro (App Manager).
Click to expand...
Click to collapse
Does one tend to work better than the other on the Fire TV? Only have the paid Titanium Backup so far.
Axecaster said:
Does one tend to work better than the other on the Fire TV? Only have the paid Titanium Backup so far.
Click to expand...
Click to collapse
They both work equally well, and both require a mouse.
I use both, but prefer ROM Toolbox Pro for this specific purpose because of its grid layout of apps (vs. Titanium Backup's list layout).
MetalMan2 said:
They both work equally well, and both require a mouse.
I use both, but prefer ROM Toolbox Pro for this specific purpose because of its grid layout of apps (vs. Titanium Backup's list layout).
Click to expand...
Click to collapse
Odd question: Play Store through desktop browser claims ROM Toolbox Pro is not compatible with the Fire TV.
Obviously, you're reported otherwise. Should it work just fine pushing over the app from a jellybean tablet or kitkat phone, or might that cause conflicts? Or should we edit the xinstaller module to change the Device ID?
Axecaster said:
Odd question: Play Store through desktop browser claims ROM Toolbox Pro is not compatible with the Fire TV.
Obviously, you're reported otherwise. Should it work just fine pushing over the app from a jellybean tablet or kitkat phone, or might that cause conflicts? Or should we edit the xinstaller module to change the Device ID?
Click to expand...
Click to collapse
There are many apps which will be listed as "incompatible" for the Fire TV.
You have a couple choices: sideload, or use Market Helper to temporarily spoof your Fire TV's identity (and thus find lots of "compatible" apps in the Play Store).
I recently rooted my Fire TV 2 and wanted to have it launch straight to Kodi like my original Fire TV does (using either Elmerhueso version or SPMC). Just found out that Xposed isn't yet available for Fire TV 2 since there is no custom recovery yet.
Does that mean this feature isn't yet available? I know about Firestarter but would prefer to go straight to Kodi rather than having a bunch of apps on the screen first. Thanks.
It maybe an option once Rbox gives us the recovery/custom rom which shouldnt be too far away now? But at the moment NO we cant.... But there is an option in Firestarter that once launched it will boot to any app you choose, so say you choose Kodi then once your Fire Tv device boots up after a little while (about roughly 5-10seconds) it will start to boot Kodi. For now this should surfice for what you what until the new stuff starts getting created after custom rom & recovery is released.
Hope this helps mate
deanr1977 said:
It maybe an option once Rbox gives us the recovery/custom rom which shouldnt be too far away now? But at the moment NO we cant.... But there is an option in Firestarter that once launched it will boot to any app you choose, so say you choose Kodi then once your Fire Tv device boots up after a little while (about roughly 5-10seconds) it will start to boot Kodi. For now this should surfice for what you what until the new stuff starts getting created after custom rom & recovery is released.
Hope this helps mate
Click to expand...
Click to collapse
Thanks for the idea. Is it worthwhile then for me to do anything else with my newfound root? The main thing I like the Fire TV for is to use Kodi so I'm guessing until we get Rbox's method there isn't anything else worthwile for me to do. I did disable updates.
ks-man said:
Thanks for the idea. Is it worthwhile then for me to do anything else with my newfound root? The main thing I like the Fire TV for is to use Kodi so I'm guessing until we get Rbox's method there isn't anything else worthwile for me to do. I did disable updates.
Click to expand...
Click to collapse
If you have a wired console or pc controller around the house you could install an emulator or 2 & play some old console games? Look in the Q&A section of this Fire TV thread & your see my compatible sideloaded apps & accessories thread if you need it & it will save you some time trying out different apps or accessories to see if they work or not?
Have fun & press that thanks button If this helped you
Sent from my SM-G900F using Tapatalk
ks-man said:
I recently rooted my Fire TV 2 and wanted to have it launch straight to Kodi like my original Fire TV does (using either Elmerhueso version or SPMC). Just found out that Xposed isn't yet available for Fire TV 2 since there is no custom recovery yet.
Does that mean this feature isn't yet available? I know about Firestarter but would prefer to go straight to Kodi rather than having a bunch of apps on the screen first. Thanks.
Click to expand...
Click to collapse
uses titaium backup and freeze kftv launcher, after that you can switch the launcher.
obviously make sure you have another launcher already installed before you freeze kftv
mejdam said:
uses titaium backup and freeze kftv launcher, after that you can switch the launcher.
obviously make sure you have another launcher already installed before you freeze kftv
Click to expand...
Click to collapse
Wow I wouldn't wanna be the guinea pig doing that for the first time! Does this really work for the AFTV2?
Sent from my SM-G900F using Tapatalk
deanr1977 said:
Wow I wouldn't wanna be the guinea pig doing that for the first time! Does this really work for the AFTV2?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
I cant remember if the official Kodi apk has the launcher intent or not to allow it to be set as default, I know SPMC does though but thats a little outdated I think as most of the Android specific changes were merged into the main Kodi branch.
I only quickly had a play the other week as its boxed back up till rbox's custom ROM and recovery.
I think I had to freeze the Kindle Launcher and use: https://play.google.com/store/apps/details?id=se.blunden.xbmclauncher&hl=en to launch Kodi as default.
Be warned though, freezing KL will also stop a lot of other things working like the FTV settings page etc and you'll need to unfreeze to access them.
Better off waiting for Xposed and hopefully rbox kindly ports his modules to allow alternative launchers without freezing.
Dude360 said:
I cant remember if the official Kodi apk has the launcher intent or not to allow it to be set as default, I know SPMC does though but thats a little outdated I think as most of the Android specific changes were merged into the main Kodi branch.
I only quickly had a play the other week as its boxed back up till rbox's custom ROM and recovery.
I think I had to freeze the Kindle Launcher and use: https://play.google.com/store/apps/details?id=se.blunden.xbmclauncher&hl=en to launch Kodi as default.
Be warned though, freezing KL will also stop a lot of other things working like the FTV settings page etc and you'll need to unfreeze to access them.
Better off waiting for Xposed and hopefully rbox kindly ports his modules to allow alternative launchers without freezing.
Click to expand...
Click to collapse
This is what I use on my 1st gen Fire TV to get launcher capabilities. I'm still on an old version (13.2 I think) but it appears he has updated it to 15.2
http://forum.xda-developers.com/showthread.php?t=2790392
I have used an app called autologin. works on rooted and non rooted devices. allows you to launch multiple apps with begining delay and delay between apps. easy to configure. I set it on firetvstick with 12 sec delay after statrup (firestarter) then 5 sec between apps (kodi)
ks-man said:
This is what I use on my 1st gen Fire TV to get launcher capabilities. I'm still on an old version (13.2 I think) but it appears he has updated it to 15.2
http://forum.xda-developers.com/showthread.php?t=2790392
Click to expand...
Click to collapse
Yeah this was the mod I was talking about (launcher intent). This is what the Xposed module will allow but without using a modded apk.
Nothing wrong with using elmerohueso builds but be aware you wont be able to use Firestarter to update Kodi as the modded apk has been signed differently. To update you'll have to use adb to sideload the new apk everytime theres an update.
Theres several ways to achieve Kodi as a launcher but like most things on the AFTV, for every upside theres also several downsides...
rp201 said:
I have used an app called autologin. works on rooted and non rooted devices. allows you to launch multiple apps with begining delay and delay between apps. easy to configure. I set it on firetvstick with 12 sec delay after statrup (firestarter) then 5 sec between apps (kodi)
Click to expand...
Click to collapse
Not heard of that one but Ill take a looksy, especially if it works on unrooted!
I have a ftv v2 with root and recovery. I want to change the default Launcher and use kodi instead.
Can i just freeze aftvlauncher and use xbmclauncher to use kodi? Will firestarter work normally if i set it to launch with 2 home button presses?
I am afraid to freeze aftvlauncher and don't be able to start any app. Bricking my ftv.
Thanks
Why freeze aftv launcher ? Just let firestarter/Kodi launch at startup and let the avtf launcher run in background...doesn't matter I think, you will not really recognize it...
KillerJoeBR said:
I have a ftv v2 with root and recovery. I want to change the default Launcher and use kodi instead.
Click to expand...
Click to collapse
Try using the XBMC Launcher. This launcher works to perfection on a rooted first generation Fire TV. Not sure if it will work when updating to OS 5. May have to wait for a new release of [MOD][XPOSED]Fire TV Mods by rbox. I'll probably not update to OS 5 until I know for sure that this launcher will work with it.
I've disabled the stock launcher, along with some other things, details in this thread there are side effects of disabling the stock launcher but I'm ok with them:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I can't say for certain if XBMC Launcher will work or not (not tried using it). I know you can't have the standard Kodi 16 as a 'launcher' as you cannot choose it from the launcher selection window you get when the AFTV launcher is disabled.
---------- Post added at 04:50 PM ---------- Previous post was at 04:48 PM ----------
Spotti said:
Why freeze aftv launcher ? Just let firestarter/Kodi launch at startup and let the avtf launcher run in background...doesn't matter I think, you will not really recognize it...
Click to expand...
Click to collapse
The reason behind disable / freeze is that it will stop the launcher from consuming resources.
May not be entirely needed on AFTV2 but on the Stick (and maybe AFTV1) I'm sure it would help.
Ludacrisvp said:
I've disabled the stock launcher, along with some other things, details in this thread there are side effects of disabling the stock launcher but I'm ok with them:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I can't say for certain if XBMC Launcher will work or not (not tried using it). I know you can't have the standard Kodi 16 as a 'launcher' as you cannot choose it from the launcher selection window you get when the AFTV launcher is disabled.
Click to expand...
Click to collapse
Thanks for your answer. I saw your post but i thought it was a bit extreme. I only need to access kodi with the home button and firestarter with 2 presses so i can stop kodi when it sometimes freezes.
I used xbmclauncher before with FTV v1 OS3 and it worked great. But i didn't see anyone saying if it works with OS 5.X so i'm afraid of testing it myself. And i think it needs the rbox module to work and its outdated but i guess is still working? Rbox says it will update his module so i guess i should wait.
KillerJoeBR said:
Thanks for your answer. I saw your post but i thought it was a bit extreme. I only need to access kodi with the home button and firestarter with 2 presses so i can stop kodi when it sometimes freezes.
I used xbmclauncher before with FTV v1 OS3 and it worked great. But i didn't see anyone saying if it works with OS 5.X so i'm afraid of testing it myself. And i think it needs the rbox module to work and its outdated but i guess is still working? Rbox says it will update his module so i guess i should wait.
Click to expand...
Click to collapse
Configure firestarter to start your "launcher" or Kodi with a single click. Set it to launch firestarter with a double click. You really can't brick doing this. If you find out you can't get back into the default Fire TV launcher for any reason, just side-uninstall firestarter via adb.
I had some issues when setting Kodi as launcher using XBMCLauncher on my Stick.
Kodi didn't seem to like it and moving back and forth to other apps like iPlayer etc it would reset its settings and act like it'd been reverted to default until I FC'd it. When it froze it could get itself into a loop as well as because it hasn't closed properly it try to 'launch itself again (if that makes sense)
I found it better to set Firestarter as Launcher, single click, start on boot and set Kodi as double click. Put Kodi in top left of app drawer as well so its always close if you click back to FireStarter by accident.
This way you always have FireStarter to fall back on if Kodi crashes.
You can also edit the Kodi keymap to have the 'Back' button on the Home screen open something else like favorites so that you don't accidentally back out of Kodi when navigating menus etc.
(Not knocking XBMCLauncher at all, I use it on my OUYA for exactly this and it works fine, just noting issues I've had on the AFTVS for others)
Dude360 said:
I had some issues when setting Kodi as launcher using XBMCLauncher on my Stick.
Kodi didn't seem to like it and moving back and forth to other apps like iPlayer etc it would reset its settings and act like it'd been reverted to default until I FC'd it. When it froze it could get itself into a loop as well as because it hasn't closed properly it try to 'launch itself again (if that makes sense)
I found it better to set Firestarter as Launcher, single click, start on boot and set Kodi as double click. Put Kodi in top left of app drawer as well so its always close if you click back to FireStarter by accident.
This way you always have FireStarter to fall back on if Kodi crashes.
You can also edit the Kodi keymap to have the 'Back' button on the Home screen open something else like favorites so that you don't accidentally back out of Kodi when navigating menus etc.
(Not knocking XBMCLauncher at all, I use it on my OUYA for exactly this and it works fine, just noting issues I've had on the AFTVS for others)
Click to expand...
Click to collapse
Thanks for your input. Did you disable amazon launcher while doing this?
Enviado de meu SM-T320 usando Tapatalk
KillerJoeBR said:
Thanks for your input. Did you disable amazon launcher while doing this?
Enviado de meu SM-T320 usando Tapatalk
Click to expand...
Click to collapse
Yeah, froze using Titanium.
One thing to be aware of is if your using another/freezing AFTVLauncher and use the Android dialog to set the new Launcher as 'default' then there is no way to reset this like in normal Android. Theres no option in Amazon Settings or anywhere else in the GUI.
I think thees a way using SQL or by installing another Home Launcher which will prompt the Android dialog again.
Dude360 said:
I think thees a way using SQL or by installing another Home Launcher which will prompt the Android dialog again.
Click to expand...
Click to collapse
Or maybe unfreezing the amazon launcher and deleting the other one?
Anyway I have another question. Do you set firestarter with adb detection? Cause I am afraid if activate this and something goes wrong I won't be able to access the firetv using wifi adb? Is that correct? And also does firestarter works without adb detection while also not having the amazon launcher?
Thanks again
KillerJoeBR said:
Or maybe unfreezing the amazon launcher and deleting the other one?
Anyway I have another question. Do you set firestarter with adb detection? Cause I am afraid if activate this and something goes wrong I won't be able to access the firetv using wifi adb? Is that correct? And also does firestarter works without adb detection while also not having the amazon launcher?
Thanks again
Click to expand...
Click to collapse
Yup, unfreezing AFTVLauncher will do it but you have to be able to get to Firestarter to launch it, not good if everything is frozen
If I remember, FireStarter has the launcher intent so if its the only launcher available, Android will default to that anyway.
So, if its the default Launcher, you wont need to use adb detection as it will use the Home button and start on boot anyway.
Is it possible to set Firestarter as a default launcher without disabling a stock one? If so -- how?
I use Fs on fire tv on os5 and it works fine. Just setup your single and double click home buttons.
I am running the latest rbox prerooted ROM (5.2.7.2_r1)
I would like to remove bloatware and pretty much anything that wont break any of the main functions of the device.
I don't use any of the Amazon apps or services except for the built in launcher, to retain access to the settings menu and the app market.
I've seen a few posts about debloating the different models, such as the stick 2, with a list of things that have been disabled or uninstalled, and I would imagine alot of it is the same, but I just wanted to be sure.
so what all is safe to get rid of without breaking the launcher?
LazorBlind said:
I am running the latest rbox prerooted ROM (5.2.7.2_r1)
I would like to remove bloatware and pretty much anything that wont break any of the main functions of the device.
I don't use any of the Amazon apps or services except for the built in launcher, to retain access to the settings menu and the app market.
I've seen a few posts about debloating the different models, such as the stick 2, with a list of things that have been disabled or uninstalled, and I would imagine alot of it is the same, but I just wanted to be sure.
so what all is safe to get rid of without breaking the launcher?
Click to expand...
Click to collapse
Here is a packages of Amazon junk to disable using System App Remover app:
Code:
com.amazon.device.software.ota - part of the OTA updates
com.amazon.device.software.ota.override
com.amazon.hedwig - what's the app name
com.amazon.avod
com.amazon.vizzini - part of the Amazon voice support
com.amazon.bueller.photos - required to access Amazon screensaver
com.amazon.bueller.music
com.amazon.device.sale.service - suspecting to block the recommendations in Android TV (Leanback) launcher
com.amazon.firebat - what's the app name
com.amazon.venezia
* com.amazon.dcp.contracts.library - part of the Amazon services
com.amazon.precog
com.amazon.tv.nimh
* com.amazon.tv.launcher - Amazon KFTV Launcher
* com.amazon.tv.settings - Amazon TV settings
You can see the asterisk (*) to indicate the necessary apps.
Thank you. This has helped!