So I've noticed that the Verizon model is missing a couple of options, anyone find any others?
Ability to change Font styles, it's missing
Battery saver mode is missing
It seems like they've messed with the Quick Settings bar
The first two on your list are not missing. I changed my fonts already, and there is a battery saver mode.
Fonts: settings> personalize> change theme> menu button on top left, scroll down to Fonts and pick the one you want, then apply it (you can change icons, sounds, wallpapers, etc in here too)
Battery Saver is called Extreme Saver and is in the Quick Settings bar.
Customizing the Quick Settings is not available, as HTC has disabled our access to the System UI Tuner.
Thanks man, I swear I did look for those, but this just goes to show that I'm not very smart. LOL
Is there a way to use a font that I purchased? I can't seem to find how to select it.
mahercs said:
The first two on your list are not missing. I changed my fonts already, and there is a battery saver mode.
Fonts: settings> personalize> change theme> menu button on top left, scroll down to Fonts and pick the one you want, then apply it (you can change icons, sounds, wallpapers, etc in here too)
Battery Saver is called Extreme Saver and is in the Quick Settings bar.
Customizing the Quick Settings is not available, as HTC has disabled our access to the System UI Tuner.
Click to expand...
Click to collapse
Thanks for the info, I looked at the Extreme power mode and that's not the same as the normal Battery Saver. It doesn't appear like you can add fonts that you purchased.
Yeah, I don't use the battery saver mode, so I don't know the difference between them. If you got the font from the HTC theme store, I would think you could apply it the same way as free ones. If you bought it from the Play store, I don't know how to apply that.
I figured out how to add purchased fonts, Settings/personalize/edit current theme/scroll down & select "font" , click the v arrow, next to fonts in the top left. Select "others", & if you've already purchased fonts then they should show up.
Same "Power Saver" issue here
Dragbike Racer said:
Thanks for the info, I looked at the Extreme power mode and that's not the same as the normal Battery Saver. It doesn't appear like you can add fonts that you purchased.
Click to expand...
Click to collapse
I am having the same issue on my Verizon HTC 10. There is an "Extreme Power Saver" mode, but no regular "Power Saver" mode - Why is this not on Verizon's HTC 10? The "Extreme Power Saver" is not what I ever want to use as it makes the phone pretty much useless. Why would a feature like "Power Saver" mode be removed?
There is no "PowerSaver" mode on stock Verizon handsets. The carrier claims that it interferes with the 911 requirements. Rooted Verizon handsets can reactivate the option through mods (I believe it's a SQLlite edit of a database; that's how it was on the M9). I had PowerSaver always running on my M9 once it was rooted.
For the powersaver mode, try this from a computer with working ADB
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
hide_ui_user_powersaver=1
Then try
Code:
adb shell "settings put secure hide_ui_user_powersaver 0"
This does not require root if done from a computer. It will require root if done from a terminal on the device. This is what works on an M9 running Marshmallow. It may or may not work on the 10. You can also try
Code:
adb shell "settings list secure"
To get a list of all the settings.
l7777 said:
For the powersaver mode, try this from a computer with working ADB
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
hide_ui_user_powersaver=1
Then try
Code:
adb shell "settings put secure hide_ui_user_powersaver 0"
This does not require root if done from a computer. It will require root if done from a terminal on the device. This is what works on an M9 running Marshmallow. It may or may not work on the 10. You can also try
Code:
adb shell "settings list secure"
To get a list of all the settings.
Click to expand...
Click to collapse
I'll look into this when I get home, thanks!!
l7777 said:
For the powersaver mode, try this from a computer with working ADB
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
hide_ui_user_powersaver=1
Then try
Code:
adb shell "settings put secure hide_ui_user_powersaver 0"
This does not require root if done from a computer. It will require root if done from a terminal on the device. This is what works on an M9 running Marshmallow. It may or may not work on the 10. You can also try
Code:
adb shell "settings list secure"
To get a list of all the settings.
Click to expand...
Click to collapse
I can confirm this works. Just did it on my VZW 10 and good ol' regular Power Saver mode is now present under Settings > Power.
thedrizzle said:
I can confirm this works. Just did it on my VZW 10 and good ol' regular Power Saver mode is now present under Settings > Power.
Click to expand...
Click to collapse
I can also confirm that this works. Performed the instructions above and then rebooted my phone and I now have both Power Saver and Extreme Power Saving Mode!
Thank you!
l7777 said:
For the powersaver mode, try this from a computer with working ADB
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
hide_ui_user_powersaver=1
Then try
Code:
adb shell "settings put secure hide_ui_user_powersaver 0"
This does not require root if done from a computer. It will require root if done from a terminal on the device. This is what works on an M9 running Marshmallow. It may or may not work on the 10. You can also try
Code:
adb shell "settings list secure"
To get a list of all the settings.
Click to expand...
Click to collapse
So I just tried this and "Power Saver" mode is now present and I can turn it on and off, but when I try to go into it to change the settings I get a fault that says "Power has stopped unexpectedly". Could there be another setting that needs changed? I'll be looking through the list to see if there is, but thought I'd ask also.
I went through the list and the setting is showing "hide_ui_user_powersaver=0" , but it won't let me change the when the Power Saver starts.
Son of a gun, works here, too. Thanks!
Can we not use an sqlite editor to get power saver back anymore?
Sent from my HTC6545LVW using Tapatalk
Evocm7 said:
Can we not use an sqlite editor to get power saver back anymore?
Click to expand...
Click to collapse
Don't think we have been able to since the m9, as I recall, it wouldn't open settings storage. But they are easy edits to default XML.
aer0zer0 said:
Don't think we have been able to since the m9, as I recall, it wouldn't open settings storage. But they are easy edits to default XML.
Click to expand...
Click to collapse
I'll look into that. Been ages since I've done any of that stuff. Thanks!
Sent from my HTC6545LVW using Tapatalk
Evocm7 said:
Can we not use an sqlite editor to get power saver back anymore?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
So can you change the settings? Such as when it takes effect.
Thanks
Whoops, wrong person I was trying to quote
Related
Is it possible to completely disable the automatic activation of the screensaver? I don't see it in settings, the longest interval for this to happen is 1 hour, but no option to disable it completely. I already installed the No Lock app, but this only helped me to get rid of the slide to unlock screen. Thank you for any ideas.
Martin
Martin2603 said:
Is it possible to completely disable the automatic activation of the screensaver? I don't see it in settings, the longest interval for this to happen is 1 hour, but no option to disable it completely. I already installed the No Lock app, but this only helped me to get rid of the slide to unlock screen. Thank you for any ideas.
Martin
Click to expand...
Click to collapse
All settings are here:
http://developer.android.com/reference/android/provider/Settings.System.html
In you case you'll need:
adb shell
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
-- check current value
select * from system where name='screen_off_timeout';
120000 - 2 min
3600000 - 1 hour
2147483647 = 596.5 hours
-- set
update system set value='2147483647' where name='screen_off_timeout';
.q
^d
or you can pull/mod/push alternatively.
Won't disabling the screensaver keep the screen and IR sensors active, thus eating up battery life significantly when not in use?
I know some folks would like to get rid of the swipe, waking up on a screen tap (mostly for accessibility issues), but I think some sort of screen (actually, battery) saver is still important.
Great link, ApokrifX. Would you happen to know if WIFI_SLEEP_POLICY does anything on the NST? I use Tasker to shut wifi off when the screen goes off, but I wonder if that might be easier?
bobstro said:
Great link, ApokrifX. Would you happen to know if WIFI_SLEEP_POLICY does anything on the NST? I use Tasker to shut wifi off when the screen goes off, but I wonder if that might be easier?
Click to expand...
Click to collapse
No idea.
I bet, it won't work...
Try and let us know?
ApokrifX said:
No idea.
I bet, it won't work...
Try and let us know?
Click to expand...
Click to collapse
I need to find a program that will let me know when wifi is on or off relative to the screen. On other devices, I can see that info in the battery status, but I'm not finding a similar option for the NST.
I *did* find a little program that would toggle it, but the NST lasts so long on battery, it's hard to tell if it's making any difference.
Actually, to disable the screensaver completely:
Code:
update system set value=-1 where name='screen_off_timeout';
I haven't found a way to disable the keyguard yet, but if you have one of the side keys set as Menu that dismisses the keyguard.
Renate NST said:
Actually, to disable the screensaver completely:
Code:
update system set value=-1 where name='screen_off_timeout';
Click to expand...
Click to collapse
Hi Renate again ( you adviced me with manual time set in NST
http://forum.xda-developers.com/showthread.php?p=30560605#post30560605, thanks).
I like the tweak (to disable the screensaver completely) also. But not understanding how to do this in internal terminal. Not shell and not busybox know the sqlite3 app and update command?
I fixed it so:
you must install SQLite3 to the NST you can just push it to the device. [unzip sqlite3 (push to n2e).zip]
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push sqlite3 /system/bin
download it from here:
http://forum.xda-developers.com/showpost.php?p=14747007&postcount=2
bobstro said:
Won't disabling the screensaver keep the screen and IR sensors active, thus eating up battery life significantly when not in use?
Click to expand...
Click to collapse
This makes a lot of sense... it explains my battery drain when the screen gets stuck on the "drag to unlock your NOOK" page after a reboot. Basically you have to make sure the Nook really goes to sleep.
Disabling the IR sensors and wifi are then the key to long battery life on the NST.
For anyone trying this technique: I used the pull/mod/push approach and Renate's recommendation of a -1 value, and everything seems to be working well, but I had to powercyle (power down, then power up) my Nook to get the change to take effect.
Well, as you may or may not know, CM10 has an option to slide your finger on the status bar on the top to change brightness. I enabled that, and initially it worked. I then started using the brightness button in the notification bar, and after like 3 clicks it got stuck on auto mode. Now no matter how many times I click it or go into display and turn off auto, restart, remove the button from the notification bar, etc, the widget stays on auto (it still changes brightness, it just says its on auto) and I can't enable the status bar brightness slide, which I personally favor over the button. Does anybody know how to get rid of the glitch? Would reflashing work?
Thanks,
thejrcrafter
thejrcrafter2 said:
Well, as you may or may not know, CM10 has an option to slide your finger on the status bar on the top to change brightness. I enabled that, and initially it worked. I then started using the brightness button in the notification bar, and after like 3 clicks it got stuck on auto mode. Now no matter how many times I click it or go into display and turn off auto, restart, remove the button from the notification bar, etc, the widget stays on auto (it still changes brightness, it just says its on auto) and I can't enable the status bar brightness slide, which I personally favor over the button. Does anybody know how to get rid of the glitch? Would reflashing work?
Thanks,
thejrcrafter
Click to expand...
Click to collapse
I had this same issue on CM9. For some reason once you turn on auto with the notification bar you cannot turn it off with the other setting. The way I fixed it was to use SQLiteEditor (a paid app by root explorer) to manually edit the settings database. Then I went into the setup for the notification bar to remove the option to toggle through auto so it would not happen again. If you don't want to use the paid app, another solution is to wipe data and start over, then immediately go to the notification setting and disable the auto toggle.
leapinlar said:
I had this same issue on CM9. For some reason once you turn on auto with the notification bar you cannot turn it off with the other setting. The way I fixed it was to use SQLiteEditor (a paid app by root explorer) to manually edit the settings database. Then I went into the setup for the notification bar to remove the option to toggle through auto so it would not happen again. If you don't want to use the paid app, another solution is to wipe data and start over, then immediately go to the notification setting and disable the auto toggle.
Click to expand...
Click to collapse
Thanks. I already tried removing data for the "Settings Data" App. Should I disable auto toggle first? It also has this error in the homescreen widget (the one with all the system toggles like btooth, wifi, brightness, etc). Also, would any SQLite or other database editor work? Where would the database file be found?
Thanks again!
thejrcrafter2 said:
Thanks. I already tried removing data for the "Settings Data" App. Should I disable auto toggle first? It also has this error in the homescreen widget (the one with all the system toggles like btooth, wifi, brightness, etc). Also, would any SQLite or other database editor work? Where would the database file be found?
Thanks again!
Click to expand...
Click to collapse
Yes it is probably a good idea to turn off the toggle first.
Any database editor that works will do. But I don't know of any free ones that have a GUI to make it easy. The free ones are command line apps that are a pain.
The settings database is in /data/data/com.android.providers.settings/databases/settings.db
leapinlar said:
Yes it is probably a good idea to turn off the toggle first.
Any database editor that works will do. But I don't know of any free ones that have a GUI to make it easy. The free ones are command line apps that are a pain.
The settings database is in /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Had the same problem on my Nook HD running CM10.1 on the hybrid install and this fixed it today. My issue was that I think I clicked "auto" while adjusting on the slider and then the brightness was stuck and the "auto" was not checked nor was it selectable. Flipped the bit from 1 to 0 and now it's working ok. Doing a CWM backup now so I'll have the fix in my gold install.
Had this problem on my Samsung T679. Just fixed it and figured I'd record the steps for my own and other's reference. I'm cheap and like doing things the hard way, so I didn't spring for SQLiteEditor. I found that sqlite3 was already installed on the phone.
Before starting: use cwm to make backup, just in case.
1. Force-stop Settings app.
2. Get /data mounted read-write.
3. Open a shell (recommend via ssh/adb, because we have some typing to do).
4. cd /data/data/com.android.providers.settings/databases
5. rm settings.db-shm settings.db-wal (not sure about this step, but the change didn't seem to stick otherwise.)
6. sqlite3 settings.db
Here is my session, you should get the idea:
Code:
sqlite> .tables
android_metadata bookmarks system
bluetooth_devices secure
sqlite> select * from system
...> where name like "%bright%";
71|status_bar_brightness_control|1
278|screen_brightness_mode|1
605|expanded_brightness_mode|0OV=I=XseparatorX=I=VO1OV=I=XseparatorX=I=VO3OV=I=XseparatorX=I=VO5
607|screen_brightness|30
sqlite> update system
...> set value=0
...> where _id=278;
sqlite> .quit
screen_brightness_mode needs to be changed to 0. Don't forget the semi-colons. Now fire up the Settings app and you should be able to enable the status-bar swipe brightness control. I had to toggle it once before it worked.
Step 1: Enable Stamina mode and Low battery mode.,
Step 2: Set both of them to only activate when battery level is below 1%
Step 3: Don't let your battery level drop below 1%
That should take care of those 2 notifications. If anyone has figured out how to get rid of all the other annoying Sony notifications, please post.
There is another way to stop it
If these stamina notification fade in you can use two fingers on this notification and pull it down...
there is a checkbox you can deselect to hide these upcoming notifications
tsc.smith said:
There is another way to stop it
If these stamina notification fade in you can use two fingers on this notification and pull it down...
there is a checkbox you can deselect to hide these upcoming notifications
Click to expand...
Click to collapse
Like every notification on Android, you go in the Application menu, you search for the app concerned and uncheck "show notifications"
Gregz78 said:
Like every notification on Android, you go in the Application menu, you search for the app concerned and uncheck "show notifications"
Click to expand...
Click to collapse
Have you actually tried this? Which application is responsible for the power management tips notifications? Post a screenshot.
yeah_mike said:
Have you actually tried this? Which application is responsible for the power management tips notifications? Post a screenshot.
Click to expand...
Click to collapse
I thought every app having the permission to post a notification was in the app listing with the possibility to disable the notifications. Eco mode Control have his checkbox greyed out.
Apparently, the "real" apps involved are “SemcPowerSaveModule.apk , Settings.apk and SuperStamina.apk” and I don't see them in the app list so forget my quote :silly:
tsc.smith said:
There is another way to stop it
If these stamina notification fade in you can use two fingers on this notification and pull it down...
there is a checkbox you can deselect to hide these upcoming notifications
Click to expand...
Click to collapse
Thank you so much. Worked on my Z5c. Great hint.
Gregz78 said:
I thought every app having the permission to post a notification was in the app listing with the possibility to disable the notifications. Eco mode Control have his checkbox greyed out.
Apparently, the "real" apps involved are “SemcPowerSaveModule.apk , Settings.apk and SuperStamina.apk” and I don't see them in the app list so forget my quote :silly:
Click to expand...
Click to collapse
OK: Interesting bit of knowledge, which in this case doesn't help much, but might still be nice to know:
If you don't see an app in the listing or if it's checkbox is greyed out, use this:
Code:
adb shell
pm hide com.package.name
to reverse it, replace "hide" with "unhide".
This hides the app from the system, including in the drawer. It is similar to "disabling" system apps. Not recomended for things you actually use, e.g. com.android.settings or com.sonymobile.superstamina. They will not work afterwards. It works very well with the annoying "low storage" notification though. Package name is com.sonymobile.storagechecker. Just try it out, you can always unhide, and the changes are instantaneous.
ADB is great.
You can for example find packages by
Code:
adb shell
pm list packages searchterm
so for example
Code:
pm list packages settings
produces a list of all packages with "settings" in the name.
Code:
pm list packages -s settings
shows only system apps with "settings" in the name.
If you want to play around in ADB by yourself, use a questionmark after a command to see all the avaliable options for this command. The two basic commands are am (activity manager) and pm (package manager)
Code:
adb shell pm ?
Just got my essential phone today. Rooted and did my normal phone setup which includes gmd gesture control. Everything was fine until I did a build prop edit I do on all my other phones adding "qemu.hw.mainkeys = 1" to the end to disable the navigation buttons. Every time I reboot, I get a system ui force close 2 or 3 time then everything seems normal. I'm not sure how to find the log file. If anyone knows what's causing this or might be able to send me in the right direction, it would be appreciated. Btw, loving this phone so far. Coming from the nexus 6 which is still awesome as well ?
All I know is because of the a/b partition, any change made to a system file, even if you just add a file and then remove it, will result in flagging the safety net. I didn't have any issues with my phone not passing safety net (still running stock Nougat, rooted with Magisk, Xposed, and substratum themes), but that's gotta have something to do with it. Did u get it figured out?
Sent from my PH-1 using Tapatalk
No calling it a night. It's been crashing every so often but am still able to use the phone. Do you know where I can find a log file?
Gimmemabrewski said:
No calling it a night. It's been crashing every so often but am still able to use the phone. Do you know where I can find a log file?
Click to expand...
Click to collapse
Doing the build.prop edit to remove the navigation keys is the problem. The PH-1 does not like this for some reason. I have been trying to find a way to remove them and use LMT for navigation.
nrage23 said:
Doing the build.prop edit to remove the navigation keys is the problem. The PH-1 does not like this for some reason. I have been trying to find a way to remove them and use LMT for navigation.
Click to expand...
Click to collapse
Immersive mode is what you want.
· Hide Status Bar only type:
adb shell settings put global policy_control immersive.status=*
· Hide Navigation Bar only type:
adb shell settings put global policy_control immersive.navigation=*
· Hide Both Bars type:
adb shell settings put global policy_control immersive.full=*
· Back to normal/default state:
adb shell settings put global policy_control null*
This Is Important If You Do Any Of The Above - If You skip this step you will have battery drain issues.:
Exclude Google apps
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
nrage23 said:
Doing the build.prop edit to remove the navigation keys is the problem. The PH-1 does not like this for some reason. I have been trying to find a way to remove them and use LMT for navigation.
Click to expand...
Click to collapse
Did you figure out a way? I used to use gmd auto hide but it doesn't seem like it works right since android 7. That and my ocd doesn't even like seeing them momentarily on a reboot ?
Edit: Overlooked the above reply. I'll give that a try tonight. Thanks
tech_head said:
Immersive mode is what you want.
· Hide Status Bar only type:
adb shell settings put global policy_control immersive.status=*
· Hide Navigation Bar only type:
adb shell settings put global policy_control immersive.navigation=*
· Hide Both Bars type:
adb shell settings put global policy_control immersive.full=*
· Back to normal/default state:
adb shell settings put global policy_control null*
This Is Important If You Do Any Of The Above - If You skip this step you will have battery drain issues.:
Exclude Google apps
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
Click to expand...
Click to collapse
Will this keep it in immersive mode through reboots? And by excluding gapps, will that cause it to pop up when using those apps? I've never had an issue with the build prop edit until now. And I'm hoping when a good custom Rom comes out, I'll be good to go again.
This thread why I'm not ready for Oreo. Gravitybox is working great on stock Nougat. Long press Power for expanded desktop mode.
Sent from my PH-1 using Tapatalk
I'm using custom navigation bar. It's not perfect but at least it stops the system ui crashes
Launcher Hijack V4
Allows a custom launcher on Amazon Kindle Fire's and Fire TV's
An early, insert seasonally appropriate celebration here, present from me. Adds support for Fire TV devices and the new Fire Tablets. Enjoy.
Please find instructions for use here (https://github.com/BaronKiko/LauncherHijack/blob/master/HELP.md#fire-tvs). Adb required for first time setup on Fire TV's.
Find the latest release here (https://github.com/BaronKiko/LauncherHijack/releases). I'm working on Aptoide and F-Droid releases for those that prefer those methods. Hopefully in the next few days.
If you want to look at my rushed and sloppy code then feel free to look here (https://github.com/BaronKiko/LauncherHijack)
Please send any issues here (https://github.com/BaronKiko/LauncherHijack/issues)
Feeling kind and want to donate? Find instructions here (https://github.com/BaronKiko/LauncherHijack/blob/master/README.md#donations)
Huge thanks to ParrotGeek1, Speeddymon and Urbanman2004.
ParrotGeek1 made V1 and without him I would have never started this project.
Speeddymon donated a 2018 Fire TV allowing me to implement Fire TV support. If you have a Fire TV you should thank him
Urbanman2004 created the lovely logo/app icon. Be sure to thank him too.
Finally I don't really check these forums often anymore so please head over to the github page and post there if you are having any issues. Usually I am pretty quick to respond there.
im not having any luck getting the accessibility function to work. i am on fireos 5.2.4.2
EDIT: I also have a fully updated firestick with the same issue. 5.2.6.7. hijack says accessibility needs to be enabled.
I believe I have a solution. I had to enable and disable some system accessibility settings to get the setting to take effect.
krsmit0 said:
im not having any luck getting the accessibility function to work. i am on fireos 5.2.4.2
EDIT: I also have a fully updated firestick with the same issue. 5.2.6.7. hijack says accessibility needs to be enabled.
I believe I have a solution. I had to enable and disable some system accessibility settings to get the setting to take effect.
Click to expand...
Click to collapse
You have to run an adb command to get it going on the fire tv's. Instructions explain it all.
The adb command alone wasn't enough. I use settings get... To verify it was there. But through several reboots it wouldnt work until I toggled other accessibility settings. This was the case for 2 different sticks.
Can you post what you did?
even with the adb command it still says accessibility needs to be enabled
huffmybrd said:
even with the adb command it still says accessibility needs to be enabled
Click to expand...
Click to collapse
Go into the standard fire TV settings and toggle.on some accessibility options. Then press home and see which launcher pops up.
Do you have the option in the settings? On the firestick 4k, fire tv (3rd gen?) and the cube (all running fire os 6.x) there are no options so you have to set it via adb. If you can do it through the system ui do it there I just thought all fire tv's didn't have the option.
Honestly I only own my fire tv because speeddymon donated it so that I could implement support for it, and I rarely use it as I have a computer hooked up to my tv making it entirely useless. In short I don't really know the in's and out's of the device.
Please do let me know what devices and fireos versions you are all running so I can update the instructions. Also what exact menu's you have to go through to get to the option.
As an aside you probably need to drop "secure" from the adb command to get it working on devices with the menu option but the system UI option is just better. Google changed it's category to stop you setting it without adb when they removed the menu option.
BaronKiko said:
Do you have the option in the settings? On the firestick 4k, fire tv (3rd gen?) and the cube (all running fire os 6.x) there are no options so you have to set it via adb. If you can do it through the system ui do it there I just thought all fire tv's didn't have the option.
Honestly I only own my fire tv because speeddymon donated it so that I could implement support for it, and I rarely use it as I have a computer hooked up to my tv making it entirely useless. In short I don't really know the in's and out's of the device.
Please do let me know what devices and fireos versions you are all running so I can update the instructions. Also what exact menu's you have to go through to get to the option.
As an aside you probably need to drop "secure" from the adb command to get it working on devices with the menu option but the system UI option is just better. Google changed it's category to stop you setting it without adb when they removed the menu option.
Click to expand...
Click to collapse
its not the home button option that needs to be toggled. like you say, its not there. but toggling some of the other options seems to get this to work after you have done the adb command. but doing the adb command alone and rebooting doesnt make this work. the system doesn't think it is enabled. toggling other accessibility options on and off finally made it work for me.
BaronKiko said:
Launcher Hijack V4
Allows a custom launcher on Amazon Kindle Fire's and Fire TV's
An early, insert seasonally appropriate celebration here, present from me. Adds support for Fire TV devices and the new Fire Tablets. Enjoy.
Please find instructions for use here (https://github.com/BaronKiko/LauncherHijack/blob/master/HELP.md#fire-tvs). Adb required for first time setup on Fire TV's.
Find the latest release here (https://github.com/BaronKiko/LauncherHijack/releases). I'm working on Aptoide and F-Droid releases for those that prefer those methods. Hopefully in the next few days.
If you want to look at my rushed and sloppy code then feel free to look here (https://github.com/BaronKiko/LauncherHijack)
Please send any issues here (https://github.com/BaronKiko/LauncherHijack/issues)
Feeling kind and want to donate? Find instructions here (https://github.com/BaronKiko/LauncherHijack/blob/master/README.md#donations)
Special thanks to ParrotGeek1 and Speeddymon. ParrotGeek1 made V1 and without him I would have never started this project. Speeddymon donated a 2018 Fire TV allowing me to implement Fire TV support. If you have a Fire TV you should thank him
If somebody with some artistic talent wants to make a logo that would be much appreciated as the little android guy looks out of place in my app drawer.
Finally I don't really check these forums often anymore so please head over to the github page and post there if you are having any issues. Usually I am pretty quick to respond there.
Click to expand...
Click to collapse
Awesome.. Thanks for the update. It seems to be a lot more robust then v3. I just got done doing some quick testing. Will detail what worked in my case on a separate post below.
I do have a request. Is there any chance you can take a look at keeping Launcher Hijack as it's own app. But also can you please take a look to see if you can create a fork of a merger of your Launcher Hijack latest version & the last GitHub release of AppStarter v4.0 (Found @ : https://github.com/sphinx02/AppStarter ). AppStarter is the best launcher for FireTV devices. But it is due for an update/upgrade. Adding your Launcher Hijack code would be great. Also updating the SPMC & Kodi link changes would be great. Also merging other opensource projects like On Boot AppStarter (Found @: https://bitbucket.org/Mirakel/onbootappstarter/src would be another). Another of the major things that will need change/updating is what the Settings button (The 3 lines button to the right of the Home button) does in AppStarter vs Launher Hijack. Since right now trying to open the FireTV long press Settings also opens the AppStarter App FireTV Settings popup. Giving you an extra thing to close after coming back from the long press Settings menu.
I can test & help in anyway you want. Let me know if something you are willing to take on. All the pieces are there. They just need to be merged & upgraded.
krsmit0 said:
im not having any luck getting the accessibility function to work. i am on fireos 5.2.4.2
EDIT: I also have a fully updated firestick with the same issue. 5.2.6.7. hijack says accessibility needs to be enabled.
I believe I have a solution. I had to enable and disable some system accessibility settings to get the setting to take effect.
Click to expand...
Click to collapse
You where right. Will get more specific in a separate post below.
BaronKiko said:
You have to run an adb command to get it going on the fire tv's. Instructions explain it all.
Click to expand...
Click to collapse
On FireTV devices below FireOS v6. It seems we need two steps to enable everything needed. Will give more detail of some testing below.
krsmit0 said:
The adb command alone wasn't enough. I use settings get... To verify it was there. But through several reboots it wouldnt work until I toggled other accessibility settings. This was the case for 2 different sticks.
Click to expand...
Click to collapse
I bet both FireTV Sticks are on FireOS v5 FW ?
TimmyP said:
Can you post what you did?
Click to expand...
Click to collapse
Will get specific below.
huffmybrd said:
even with the adb command it still says accessibility needs to be enabled
Click to expand...
Click to collapse
Info on how to successfully enable everything posted below.
krsmit0 said:
Go into the standard fire TV settings and toggle.on some accessibility options. Then press home and see which launcher pops up.
Click to expand...
Click to collapse
The ADB command is still needed first. Then the only accessibility option that needs toggling is "Screen Magnifier". Just toggle the setting like you are going to turn it on. The instructions screen should popup. Then just choose "TURN OFF MAGNIFIER" at the instructions screen. Hitting "TURN OFF MAGNIFIER" will opens up Launcher Hijack v4. There you can choose AppStarter or your chosen launcher. Then you are all set.
BaronKiko said:
Do you have the option in the settings? On the firestick 4k, fire tv (3rd gen?) and the cube (all running fire os 6.x) there are no options so you have to set it via adb. If you can do it through the system ui do it there I just thought all fire tv's didn't have the option.
Honestly I only own my fire tv because speeddymon donated it so that I could implement support for it, and I rarely use it as I have a computer hooked up to my tv making it entirely useless. In short I don't really know the in's and out's of the device.
Please do let me know what devices and fireos versions you are all running so I can update the instructions. Also what exact menu's you have to go through to get to the option.
As an aside you probably need to drop "secure" from the adb command to get it working on devices with the menu option but the system UI option is just better. Google changed it's category to stop you setting it without adb when they removed the menu option.
Click to expand...
Click to collapse
Right. It seems FireOS v5 devices need a two-step setup. In correct order both the ADB command & a ACCESSIBILITY Menu Toggle (Screen Magnifier ONLY) are needed for it to proper register everything. The good news is that it only needs to be done once. And it survives a FireTV reboot. Bad news is that if you deliberately stop the Launcher Hijack App. Then you have to do do the two step setup again.
I also tried dropping the "secure" from the adb command but got he following results:
Run Code:
Code:
settings put enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
And
settings enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Both gave the following return:
Code:
ty_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ <
Invalid namespace 'enabled_accessibility_services'
usage: settings [--user NUM] get namespace key
settings [--user NUM] put namespace key value
settings [--user NUM] delete namespace key
'namespace' is one of {system, secure, global}, case-insensitive
If '--user NUM' is not given, the operations are performed on the owner user.
[email protected]:/ $
Let me know if I should test anything else regarding this.
Will post specifics of what worked for me on a separate post below.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
krsmit0 said:
its not the home button option that needs to be toggled. like you say, its not there. but toggling some of the other options seems to get this to work after you have done the adb command. but doing the adb command alone and rebooting doesnt make this work. the system doesn't think it is enabled. toggling other accessibility options on and off finally made it work for me.
Click to expand...
Click to collapse
Right, thanks to your post I was able to narrow it down to a single Accessibility Toggle. Working on a post that explains everything now.
Y314K said:
Right, thanks to your post I was able to narrow it down to a single Accessibility Toggle. Working on a post that explains everything now.
Click to expand...
Click to collapse
Great, thanks. I wasn't sure what exactly was working, but i spent sometime on both sticks until it worked. I am on fireos 5 on both sticks. I think the issue i have now is i keep ending up back on the fire tv launcher. i think hijack or my launcher choice (TVLauncher) are getting kicked out of memory. Other then that this feels extremely stable and very consistent.
Guide for FireTV's on FireOS 5 FirmWare v0.5...
Guide for FireTV's on FireOS 5 FirmWare v.05
This guide should work on all FireTV devices on any FireOS 5. Rooted & Non-Rooted
**Will update guide with method to install Launcher Hijack from the FireTV itself.**
Tested on:
- FireTV 1 Box - Rooted with Bootloader fully unlocked.
- On PreRooted Fire OS 5.2.6.6 (617513220)
- Running without SuperSU which means NO Root access except in TWRP.
- Basically it runs like on stock FW with the option to enable root.
- Should be the same for all other FireTV's on FireOS 5 that have the Accessibility option in Settings.
Installation (Based on the Launcher Hijack GitHub Guide):
ADB Code Method
Navigate to this GitHub's downloads page (https://github.com/BaronKiko/LauncherHijack/releases) on your desktop/laptop and download the latest APK.
Install ADB on your desktop/laptop (Google will help you) and ensure a connection to your Fire TV.
Install Launcher Hijack with this command:
adb install <path to downloaded APK>
Click to expand...
Click to collapse
Ensure you have some Launchers installed.
Enable the Accessibility Service using these two commands (exactly in this order):
adb shell
Code:
settings put secure enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Then...
Code:
settings put secure accessibility_enabled 1
Click to expand...
Click to collapse
If this is a first/fresh install of LH (Launcher Hijack). LH will open.
Select your desired Launcher from the list provided
If you had previously opened LH & selected a desired Launcher.
Your previously chosen Launcher will open.
Reboot your device (Recommended but not required).
Congratulation, if all is working correctly your home button should now open your chosen launcher
Accessibility Toggle Method
Navigate to this GitHub's downloads page (https://github.com/BaronKiko/LauncherHijack/releases) on your desktop/laptop and download the latest APK.
Install ADB on your desktop/laptop (Google will help you) and ensure a connection to your Fire TV.
Install Launcher Hijack with this command:
adb install <path to downloaded APK>
Click to expand...
Click to collapse
Ensure you have some Launchers installed.
Enable the Accessibility Service using this command:
adb shell
Code:
settings put secure enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Click to expand...
Click to collapse
On your FireTV go to & click on [ Settings / Accessibility / Screen Magnifier ]
The Screen Magnifier instructions menu will popup.
Click on [ TURN OFF MAGNIFIER ].
If this is a first/fresh install of LH (Launcher Hijack). LH will open.
Select your desired Launcher from the list provided
If you had previously opened LH & selected your desired Launcher.
Your previously chosen Launcher should open.
Reboot your device
Congratulation, if all is working correctly your home button should now open your chosen launcher
Important, Accessing Settings and the Long Press Menu
Unfortunately for FireTV devices a compromise had to be made. To access the long press menu and with it settings you have to hold menu and home together. You can also get to the default launcher by simply pressing them together.
Troubleshooting
If you are having issues then there are some common issues you can check here:
Ensure you are using an Amazon TV device running Fire OS 5, compatible with all versions as of release (FW 5.2.6.7 = latest).
Ensure you have enabled the accessibility service with the command: adb shell settings put secure enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Ensure you can open your launcher directly i.e. Using any launcher, other than your chosen launcher, open you chosen launcher like any other app, this should open your chosen launcher.
Ensure you have selected your chosen launcher in Launcher Hijack.
Reboot your device after following all previous steps.
After clicking home initially wait 10 seconds and press home again. This happens when your chosen launchers process gets killed in the background and may happen from time to time, especially after a reboot. There are plenty of existing apps that already keep a chosen application in memory so try one of those if this is a reoccurring issue for you.
If all else fails try using one of the following launchers with known compatibility: AppStarter or HALauncher.
now, any working solution to keep the launcher in memory?
Y314K said:
Guide for FireTV's on FireOS 5 FirmWare v.05
This guide should work on all FireTV devices on any FireOS 5. Rooted & Non-Rooted
**Will update guide with method to install Launcher Hijack from the FireTV itself.**
Tested on:
- FireTV 1 Box - Rooted with Bootloader fully unlocked.
- On PreRooted Fire OS 5.2.6.6 (617513220)
- Running without SuperSU which means NO Root access except in TWRP.
- Basically it runs like on stock FW with the option to enable root.
- Should be the same for all other FireTV's on FireOS 5 that have the Accessibility option in Settings.
Installation (Based on the Launcher Hijack GitHub Guide):
Navigate to this GitHub's downloads page (https://github.com/BaronKiko/LauncherHijack/releases) on your desktop/laptop and download the latest APK.
Install ADB on your desktop/laptop (Google will help you) and ensure a connection to your Fire TV.
Install Launcher Hijack with this command:
Ensure you have some Launchers installed.
Enable the Accessibility Service using this command:
On your FireTV go to & click on [ Settings / Accessibility / Screen Magnifier ]
The Screen Magnifier instructions menu will popup.
Click on [ TURN OFF MAGNIFIER ].
If this is a first/fresh install of LH (Launcher Hijack). LH will open.
Select your desired Launcher from the list provided
If you had previously opened LH & selected your desired Launcher.
Your previously chosen Launcher should open.
Reboot your device
Congratulation, if all is working correctly your home button should now open your chosen launcher
Important, Accessing Settings and the Long Press Menu
Unfortunately for FireTV devices a compromise had to be made. To access the long press menu and with it settings you have to hold menu and home together. You can also get to the default launcher by simply pressing them together.
Troubleshooting
If you are having issues then there are some common issues you can check here:
Ensure you are using an Amazon TV device running Fire OS 5, compatible with all versions as of release (FW 5.2.6.7 = latest).
Ensure you have enabled the accessibility service with the command: adb shell settings put secure enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Ensure you can open your launcher directly i.e. Using any launcher, other than your chosen launcher, open you chosen launcher like any other app, this should open your chosen launcher.
Ensure you have selected your chosen launcher in Launcher Hijack.
Reboot your device after following all previous steps.
After clicking home initially wait 10 seconds and press home again. This happens when your chosen launchers process gets killed in the background and may happen from time to time, especially after a reboot. There are plenty of existing apps that already keep a chosen application in memory so try one of those if this is a reoccurring issue for you.
If all else fails try using one of the following launchers with known compatibility: AppStarter or HALauncher.
Click to expand...
Click to collapse
Many thanks for the detailed write up.
Can I just confirm that on the latest 4K firestick, there is no way to do the above without running the ADB commands? I recall using the launcher highjack on the 2nd Gen firestick WITHOUT running any ADB commands.
thanks again
Gosh that's a lot to break down.
Y314K said:
I do have a request. Is there any chance you can take a look at keeping Launcher Hijack as it's own app. But also can you please take a look to see if you can create a fork of a merger of your Launcher Hijack latest version & the last GitHub release of AppStarter v4.0 (Found @ : https://github.com/sphinx02/AppStarter ). AppStarter is the best launcher for FireTV devices. But it is due for an update/upgrade. Adding your Launcher Hijack code would be great. Also updating the SPMC & Kodi link changes would be great.
Click to expand...
Click to collapse
Merging the code into AppStarter would be a lot of work with no real benefit. Simply install them both separately and select AppStarter in Launcher Hijack. Also as I said in a previous post I honestly don't use my Fire TV so I don't really want to maintain AppStarter. I see more use in making the Fire TV a dedicated kodi/plex box with Launcher Hijack anyhow.
Y314K said:
Also merging other opensource projects like On Boot AppStarter (Found @: https://bitbucket.org/Mirakel/onbootappstarter/src would be another).
Click to expand...
Click to collapse
On Boot AppStarter is just a broadcast receiver which this app already uses to start on boot. Again there would be no benefit to a merge as it's not related to Launcher Hijack.
Y314K said:
Another of the major things that will need change/updating is what the Settings button (The 3 lines button to the right of the Home button) does in AppStarter vs Launher Hijack. Since right now trying to open the FireTV long press Settings also opens the AppStarter App FireTV Settings popup. Giving you an extra thing to close after coming back from the long press Settings menu.
Click to expand...
Click to collapse
Unfortunately this is the best compromise I could make and it effects whatever app you happen to have open. I chose this because generally the menu press is something easy to cancel (as you said you just press back or menu again). I could cache the menu press and activate it with a delay but that could break applications that depend on long press of the menu button (don't know any apps that do that but it's possible) so it's just not worth it. It would also be a whole lot of work when I'm busy trying to get another job as I tend to like eating.
Y314K said:
The ADB command is still needed first. Then the only accessibility option that needs toggling is "Screen Magnifier". Just toggle the setting like you are going to turn it on. The instructions screen should popup. Then just choose "TURN OFF MAGNIFIER" at the instructions screen. Hitting "TURN OFF MAGNIFIER" will opens up Launcher Hijack v4. There you can choose AppStarter or your chosen launcher. Then you are all set.
Right. It seems FireOS v5 devices need a two-step setup. In correct order both the ADB command & a ACCESSIBILITY Menu Toggle (Screen Magnifier ONLY) are needed for it to proper register everything. The good news is that it only needs to be done once. And it survives a FireTV reboot. Bad news is that if you deliberately stop the Launcher Hijack App. Then you have to do do the two step setup again.
Click to expand...
Click to collapse
That's totally bizarre, no idea why that would be the case. My assumption is the settings aren't being applied for whatever reason after the command. Would really like a purely adb solution.
Y314K said:
I also tried dropping the "secure" from the adb command but got he following results:
Run Code:
Code:
settings put enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
And
settings enabled_accessibility_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Both gave the following return:
Code:
ty_services com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ <
Invalid namespace 'enabled_accessibility_services'
usage: settings [--user NUM] get namespace key
settings [--user NUM] put namespace key value
settings [--user NUM] delete namespace key
'namespace' is one of {system, secure, global}, case-insensitive
If '--user NUM' is not given, the operations are performed on the owner user.
[email protected]:/ $
Let me know if I should test anything else regarding this.
Click to expand...
Click to collapse
Ok it's under secure then, I assume you don't get an invalid namespace error for the original command?
Oh boy there's a whole other post I didn't see before getting this far. Wont quote it as it's really long but I'm glad to see you have a reliable way to set it up. I found this command that may help if run first:
Code:
settings put secure accessibility_enabled 1
No idea if it will fix the issue I just saw it mentioned in a post over here: https://autotools.helprace.com/i98-control-accessibility-via-secure-settings It does seem like your trick could set this variable allowing it to work, I just don't know. Regardless I will update the instructions with your findings so others don't have such issues.
krsmit0 said:
Great, thanks. I wasn't sure what exactly was working, but i spent sometime on both sticks until it worked. I am on fireos 5 on both sticks. I think the issue i have now is i keep ending up back on the fire tv launcher. i think hijack or my launcher choice (TVLauncher) are getting kicked out of memory. Other then that this feels extremely stable and very consistent.
Click to expand...
Click to collapse
Launcher Hijack is a service so it shouldn't ever be ousted from system memory. It is possible but if it ever does happen then it calls my close function (there so code can wrap up) and the code simply starts a new instance. If it went down you would have to disable then enable the service via adb or reboot. If you just have to press home again it's the launcher. After some Googling there are "sticky intents" that may help but apparently they are not great to use as they can cause memory issues. It leads to the fundamental issue, is it a smart thing to fix? These devices don't have a lot of memory to begin with and the fact that your launcher is getting killed means the device has run out. In that case I would say the right thing to do is to kill the launcher an it can be started again later and it's better that what you are doing lagging badly.
If I find some time, big if there, I can see if sticky intents are the magic they seem to be, honestly I'm doubtful but, if so I can put it as an option via settings. Right now your best bet is to use a light weight launcher or simply press home again.
Been writing this for an hour now -_-
But finally can one of you with a Fire TV (or stick) running Fire OS 5 check that the settings menu in Launcher Hijack has "Hardware Button Detection", "Broadcast Receiver Detection" and "Disable while menu held" checked by default and the others off. You can load the defaults with the menu if you changed any of the options. Just want to make sure that the defaults are correct for your device.
Yet another post:
Intenti0n said:
Many thanks for the detailed write up.
Can I just confirm that on the latest 4K firestick, there is no way to do the above without running the ADB commands? I recall using the launcher highjack on the 2nd Gen firestick WITHOUT running any ADB commands.
thanks again
Click to expand...
Click to collapse
You can enable "Overlay Detection" in the Launcher Hijack settings to get it working like the old Launcher Hijack but it's just not as good and you can't use the long press menu so I don't suggest it.
krsmit0 said:
now, any working solution to keep the launcher in memory?
Click to expand...
Click to collapse
Have not had experience on this. I still use AppStarter v4.0. Which seem to be pretty good at staying in memory. Specially since I also use [NOROOT] On Boot AppStarter v1.0. For it to load on Boot. I don't remember it ever being closed. Unless I choose to close it.
Intenti0n said:
Many thanks for the detailed write up.
Can I just confirm that on the latest 4K firestick, there is no way to do the above without running the ADB commands? I recall using the launcher highjack on the 2nd Gen firestick WITHOUT running any ADB commands.
thanks again
Click to expand...
Click to collapse
Seems to be a new method found by the developer to work with the changes that Google/Amazon have made between FireOS 5 & FireOS 6 (Google's base Android code usually has the biggest changes). Harder to do when your dealing with two different versions of Android.
Y314K said:
Have not had experience on this. I still use AppStarter v4.0. Which seem to be pretty good at staying in memory. Specially since I also use [NOROOT] On Boot AppStarter v1.0. For it to load on Boot. I don't remember it ever being closed. Unless I choose to close it.
Seems to be a new method found by the developer to work with the changes that Google/Amazon have made between FireOS 5 & FireOS 6 (Google's base Android code usually has the biggest changes). Harder to do when your dealing with two different versions of Android.
Click to expand...
Click to collapse
To be clear you don't need AppStarter, this app does that on it's own for the selected launcher. Appstarter simply uses very little memory so it rarely gets kicked. It's also super quick to boot so if it does get kicked it can usually start in time.
Also you should have enabled the accessibility service on the old version too, I just use it more now and disabled the old method be default as it causes issues when both methods are running in parallel.
You can enable "Overlay Detection" in the Launcher Hijack settings to get it working like the old Launcher Hijack but it's just not as good and you can't use the long press menu so I don't suggest it.
Click to expand...
Click to collapse
I have enabled the "Overlay detection" and rebooted. After rebooted, the HAL launcher starts up automatically.
However, when I press the home key on the remote, it goes back to the default launcher.
is that expected?
Intenti0n said:
I have enabled the "Overlay detection" and rebooted. After rebooted, the HAL launcher starts up automatically.
However, when I press the home key on the remote, it goes back to the default launcher.
is that expected?
Click to expand...
Click to collapse
It probably shouldn't do that but I'm gonna say that feature just isn't supported on fire TV's. It's for 2017 and earlier fire tablets and you just don't need it on the TV's.
BaronKiko said:
It probably shouldn't do that but I'm gonna say that feature just isn't supported on fire TV's. It's for 2017 and earlier fire tablets and you just don't need it on the TV's.
Click to expand...
Click to collapse
OK thanks, I will try the ADB method then