Hello all,
First of all the credit of this mod goes to @nuuits at this forum.
With this mod you can disable or enable the Navbar which is not really needed if you have pie control.
Flash "enableNavbarG4" in TWRP to enable the navbar.
Flash "disableNavbarG4" in TWRP to disable the navbar.
Download and install LMT Launcher from here to get pie control.
Cheers!
You could also disable navigation bar by adding the line "qemu.hw.mainkeys = 1" at the end of the build.prop. If you ever need it back again, just remove the line.
0rigin said:
You could also disable navigation bar by adding the line "qemu.hw.mainkeys = 1" at the end of the build.prop. If you ever need it back again, just remove the line.
Click to expand...
Click to collapse
Sure you can do that - this does the same thing but just with a flash.
Ahh, only now I've checked the links. Yeah I guess it's more or less the same.
Except that I have a phobia and don't wanna flash stuff unless I know exactly what it is and I actually need to. :]
Thank you for crediting me!
0rigin said:
Ahh, only now I've checked the links. Yeah I guess it's more or less the same.
Except that I have a phobia and don't wanna flash stuff unless I know exactly what it is and I actually need to. :]
Click to expand...
Click to collapse
Very understandable. I created this to be an easier (lazier?) way of doing that, and there were extra steps to enabling the navbar (+ disabling capacitive keys) on the HTC One M7, so this actually made the process much quicker for that device.
The navbar enabler zip comments out the physical key layout lines so the capacitive keys on the M7 are effectively disabled. Then I created a script to add the relevant line to build.prop (so nothing else is overwritten or changed) that executes while flashing. The disabler zip replaces the key layout file with the original, re-enabling the capacitive keys. The script removes that line while keeping the build.prop intact.
The G4 doesn't have capacitive keys, so the key layout files are not relevant to this device. I'm attaching a modified zip to this post that has the capacitive key stuff removed. Please feel free to add the attachments to your post, @MrCreel
nuuits said:
Thank you for crediting me!
Very understandable. I created this to be an easier (lazier?) way of doing that, and there were extra steps to enabling the navbar on the HTC One M7.
The navbar enabler zip comments out the physical key layout lines so the capacitive keys on the M7 are effectively disabled. Then I created a script to add the relevant line to build.prop (so nothing else is overwritten or changed) that executes while flashing. The disabler zip replaces the key layout file with the original, re-enabling the capacitive keys. The script removes that line while keeping the build.prop intact.
The G4 doesn't have capacitive keys, so the key layout files are not relevant to this device. I'm attaching a modified zip to this post that has the capacitive key stuff removed. Please feel free to add the attachments to your post, @MrCreel
Click to expand...
Click to collapse
Thank you man, really appreciate it
Build.prop
0rigin said:
You could also disable navigation bar by adding the line "qemu.hw.mainkeys = 1" at the end of the build.prop. If you ever need it back again, just remove the line.
Click to expand...
Click to collapse
How can I do that? Where do I find the build.prop? Do I need root? Thanks!!!
Kleber Ancona
kancona said:
How can I do that? Where do I find the build.prop? Do I need root? Thanks!!!
Kleber Ancona
Click to expand...
Click to collapse
You need Root, You find it in /system
Does the Google swipe up still happen lmt has a hard time opening with that still running
Anyone confirm that its there or is it gone, lmt has a hard time working with Google swipe up
cyan pac said:
Anyone confirm that its there or is it gone, lmt has a hard time working with Google swipe up
Click to expand...
Click to collapse
Install "LG PIE Support" if you have xposed to remove the Google swipe up.
LG Pie Support is working, even when its last update was 2014 [emoji14]
So I'm using lmt pie launcher and tried to make the dual window pop up one of the short cuts but to no avail. Anyone able to do this?
Sent from my LG-H811 using Tapatalk
Related
avlock[10] is a (the first?) real, *system-level* lock screen replacement for Android (CM 5.0.6).
it replaces the standard "connect the dots" behavior with pin-like mechanism. patterns can be arbitrarily large, and nodes can be repeated. also, there are no numbers -- just circles. definitely not for everyone, but i think some people may like it.
here's how it works:
http://files.clangen.org/avlock/avlock.m4v
if you want to try it you must have CM 5.0.6 installed, then:
1. reboot to bootloader
2. nandroid backup <-- do it. seriously. just in case.
3. flash avlock[x].zip
4. reboot
5. if you don't have a lock pattern already, set one: Home > Menu > Settings > Location and Security > Set Unlock Pattern
faq:
q: what happens if something goes really wrong and i can't log in?
a: i've been tweaking this mod for a long time and you shouldn't have any problems. BUT IF YOU DO:
* restore from nandroid backup made in step 2 above
OR
* if you know how to use adb, just delete the file pattern file and reboot:
adb remount
adb shell rm /data/system/gesture.key
adb shell reboot
q: what files are replaced by the patch?
a: framework.jar, framework-res.apk, android.policy.jar, Settings.apk
q: why not just distribute this as a simple .apk file?
a: this is a system-level mod because it replaces system-level components. it cannot be distributed as an .apk.
changelog:
avlock[8]:
* initial release
avlock[9]:
* added tactile feedback
* reduced login delay
avlock[10]:
* disabling "Use visible pattern" works now
* better integration with system and Settings.
* re-added drag lock option.
avlock[11]:
* added the ability to specify a pattern timeout
use at your own risk. i am not responsible for any damages caused by this software. MAKE A NANDROID BACKUP FIRST!
caution: if you update your rom, install a theme, or flash another mod that replaces framework.jar, framework-res.apk, or android.framework.jar, you may not be able to log in upon reboot (or even spin into a boot loop). either (1) make sure you disable your lock screen before flashing or (2) rm gesture.key as described in the faq!
download:
avlock[11]: http://droidbasement.com/db-blog/?p=202 (thanks, pershoot)
sources:
http://github.com/avatar5d
wow, nifty and works well enough
It'd be really nice if it was faster, there is close to a 2 second lag between entering and unlocking
Cool Thanks
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Good work.
Thanks
imfloflo said:
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Good work.
Thanks
Click to expand...
Click to collapse
You could always unzip the zip and push the files manually
adb shell stop
adb push these files to their respective places framework.jar, android.policy.jar, Settings.apk
adb shell start
If you forget the pattern, you can get it emailed to you right?
Looks awesome in the video, nice idea, better executed!
NICE MOD!
Nice work!!!
prettyboy85712 said:
Nice work!!!
Click to expand...
Click to collapse
+1 Nice ...
Good Job !
This looks awesome! Nice work
@ _avatar
Any chance to make this work with Enom's ROM ?
Nice work!
imfloflo said:
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Click to expand...
Click to collapse
Unfortunately, because this is a system-level mod it cannot be installed as a simple .apk.
bobtentpeg said:
It'd be really nice if it was faster, there is close to a 2 second lag between entering and unlocking
Click to expand...
Click to collapse
The delay is there on purpose. Once you stop touching the circles for 2 seconds, the combination is verified. Without this delay, there would need to be some sort of "OK" button, which I think is undesirable. However, I'll look into making the delay shorter (1 second?) for future builds. The value needs to be long enough so people can still enter their combination relatively slowly, but fast enough so it's not annoying.
pvillasuso said:
Any chance to make this work with Enom's ROM ?
Click to expand...
Click to collapse
Possibly. Is Enom's source available, and easily buildable like Cyanogen's? I'm not super familiar with his project.
This is hot, installing now. My main complaint with the stock lock pattern was the inability to re-use points. just gotta set a good lock pattern and see how this works.
Thanks.
Wow.. this is pretty damned cool! Good job.
One thing, tactile feedback is not working with this, any way to restore that?
daveid said:
One thing, tactile feedback is not working with this, any way to restore that?
Click to expand...
Click to collapse
It's on my TODO list
EDIT: added to avlk[9] build. see original post!
Can you make a them of some sort and replace the dots with numbers?
Can it run on 1.8.1 rom
Re: [MOD] avlk[9], a real, system-level lock screen replacement
anyway to incorporate trackball wake-up in this for us desire port guys ;-)
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
_avatar said:
Possibly. Is Enom's source available, and easily buildable like Cyanogen's? I'm not super familiar with his project.
Click to expand...
Click to collapse
http://android.git.kernel.org/
You'll want to ask him which actual tag he's building for current versions. Also, since I'm not up on framework patching, it might be more complicated if you don't want to break the trackball-wake and/or notification features. Best to contact him @enomther or for someone to raise the suggestion in his thread.
Hey everybody!
***New APK editor added! Set the keys to whatever you want, see below!***
****I will not be held responsible if your Nook Color starts eating babies!!****
****Or if it breaks either!!****
****Added a revert, for those who may have issues returning the keylayout to stock (like 1.1 users who can't run the keylayout app)****
****As an added request, if anyone knows how to reload the keylayouts sans reboot, please let me know, as that is really the only thing missing from this little thing. I would love to be able to quickly reload these as needed.****
So after creating the flashable zip file for the keylayouts, and receiving some feedback that implied it would be nice to have more options, I decided to brush up on the coding skills and write a nice little app that can re-write the keylayout files without having to flash anything. This is actually my first android app, so please provide me with any feedback you may have, the more the better. The way I see it, the more I know, the better things I can make.
The keylayout app currently supports mapping the volume keys to these items:
Volume Up
Volume Down
Menu
Back
Search
D-pad Center
and can additionally support wake on press, if desired. Once written, you will need to reboot your device for the keylayout to be effective, but it's still easier than manual edits or multiple flashes.
***Note that using the app requires su access, and also at this point requires that you first flash one of my v5 keylayout zip files***
***I have received notice that the application does not run on stock rooted 1.1.0 I will be looking into this and posting an update, and most likely a revert to stock zip in case anyone needs it.***
Thanks go to whoever first suggested this, I'll be damned if I can't remember who I got this from, but thank you, whoever you are, I'll be sure to give you props when I figure out who you are.
History over, now for the details:
To install: Simply flash either zip file in CWM after flashing your CM7 or Honeycomb build to your eMMC. Once you do this, you can install and use the apk file to make changes to the keylayouts to your heart's content.
The CWM zips have been confirmed to work on most all versions of android for the nook, and in theory, the APK should work as well, however YMMV. If it works, or if it doesn't, please please post your version or build info, and let us all know what works and what doesn't.
Feedback and/or critiques accepted, may be subject to rebuttal. Hope this helps someone else, and thanks to everyone on this forum for all the hard work you do!
FYI: For those who still want an easy way to change the volume when these keys are no longer volume keys, try replacing the longpress home app with Recent Plus, by local forum contributor timoskrempel, which I first found HERE and works very well as a replacement.
Version History
-----------------------
apkv0.1b - Initial version of the keylayout app. Feedback appreciated.
v5: added files that apparently weren't as useless as I assumed. Also created inverted keys zip, use INV zip to switch the buttons.
v4: removed useless files from update zip, cause I'm being a bit too perfectionist.
V3: added files to improve compatibility (HC v4 tested, should work on Froyo, maybe stock)
V2: removed wake on press (thanks jasoraso)
V1: First Version
I definitely prefer hard keys, even with the modifications in CM7. I'll give your zip a try next time I flash a rom (I've already changed my qwerty.kl on this rom).
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
jasoraso said:
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
Click to expand...
Click to collapse
An excellent point. Editing my zip and attaching v2. thanks to you!
success! just flashed this along with nightly#4 and it works like a charm.
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
digitalslacker said:
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
EpicFail236 said:
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
Click to expand...
Click to collapse
thanks, i'll check it out.
What would be really cool and I'm not sure it's possible and I know it's not in the scope of this thread; but a way to change functionality of the buttons per app. So for example when in Pandora (or music app of choice) buttons behave as volume buttons, but under other various apps like gallery it could be home+back button set.
Seems like you'd have to have an app running as a service and monitor the currently running focused app (not in sleep mode) and depending on what has focus do a live update to the qwerty.kl file to change buttons to expected functionality, not sure if a reboot is required after an update to the kl file though?
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
Click to expand...
Click to collapse
change mapping in step 4 from here:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
adb pull /system/usr/keylayout/TWL4030_Keypad.kl
adb pull /system/usr/keylayout/omap_twl4030keypad.kl
edit 'TWL4030_Keypad.kl' and 'omap_twl4030keypad.kl' with a unix line ending aware text editor (Notepad++, gedit, vi)
replace 'VOLUME_DOWN' with 'BACK' and replace 'VOLUME_UP' with 'MENU' in each (or vice-versa)
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push TWL4030_Keypad.kl /system/usr/keylayout/TWL4030_Keypad.kl
adb push omap_twl4030keypad.kl /system/usr/keylayout/omap_twl4030keypad.kl
adb shell
cd /system/usr/keylayout
chmod 644 omap_twl4030keypad.kl
chmod 644 TWL4030_Keypad.kl
exit
adb reboot
Click to expand...
Click to collapse
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Thanks for the heads up, will review and post v5 sometime today.
my status bar always shows with HoneyComb, so I always have the back menu buttons. are there apps where this is not the case?
Anyone try this on froyo yet?
fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Yeah, I totally deleted an extra file, added to v5 and it should now work with this eMMC build. oops.
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Click to expand...
Click to collapse
I will have to put together a stock zip and put it up sometime in the near future. Your swap keys is not easily done directly, but I have posted a new flashable zip that will swap the keys, flash INV-v5 to have the volup function as back and voldown to work as menu. This one I haven't tested, as I don't actually have my nook with me here now, but in theory it should be OK, as all I did was swap the mappings in the kl files.
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
rickpref said:
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
Click to expand...
Click to collapse
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
EpicFail236 said:
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
Click to expand...
Click to collapse
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
rickpref said:
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
Click to expand...
Click to collapse
My ADB machine was down and out at the time, so I had to do it via ES file manager and the terminal on the nook itself, but yeah, manual replacement was the way to go. sometimes a bit of command-fu is just easier than the alternative.
digitalslacker said:
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
I use Volume Widget by Futon Redemption. It gives you two little onscreen +/- buttons to adjust the volume.
Hello!
I tried to enable softkeys on my HTC Desire X [Root (SU + Bbox), Xposed, Stock Rom] with softkey enabler, but after reboot nothing happens. After that, I added the line
Code:
qemu.hw.mainkeys=0
at the end of my buil.prop myself, but nothing happens
What can I do?
Is it possible to flash a modified build.prop via recovery? If yes, how to do it?
Thanks for your answers,
weely_XD
In order for that to work, the required resources must exist in SystemUI.apk. This device doesn't exactly have the biggest internal memory, so HTC likely removed those to save space. GravityBox may be able to add them, but you'll likely have better luck with a CM10 Rom. Why do you want the navigation bar anyway?
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
For the powersaver mode, try this from a computer with working ADB
Code:
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
Code:
hide_ui_user_powersaver=1
Then try
Code:
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:
Code:
adb shell "settings list secure"
To get a list of all the settings.
Click to expand...
Click to collapse
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Must have missed that one. I went through that post a couple days ago. Guess this will work for those that can't or don't know how to setup and use adb
Sent from my HTC6545LVW using Tapatalk
Evocm7 said:
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
Click to expand...
Click to collapse
If it is like the M9 on marshmallow, after making that edit, if you factory reset it, the menu option should appear in the standard menu. its alot easier to either put it in as a shortcut, or use xtended settings, and add it to the power menu, or gravity box, and add custom quicksetting tiles (1 of which being battery, it will also show battery temp and mAh remaining).
Once we get a deodexed based, or even a stock odex flash, we can make those edits prior to flash and it will be in the menu as normal
edit, i also believe if you edit the next line (120) def_hide_ui_user_powersaver and set it to 0, this is what will enable the menu on factory reset
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
hgoldner said:
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
Click to expand...
Click to collapse
Can confirm that the latest update definitely does break this ability (no root). =(
im_high_tech said:
Can confirm that the latest update definitely does break this ability (no root). =(
Click to expand...
Click to collapse
I think the only way to do this is to write to \system; so for those who don't want to flash a custom ROM or write to \system, it's out of reach for now.
And especially galling because the 10's on all the other carriers have the feature. Verizon kills it.
@andybones has it in the stock deodex base, but if you are working off of the odex base, the easiest way is probably gravitybox, and using the QS tile to toggle it (still requires root). Just make sure you are using systemless xposed to not touch the system partition as @hgoldner pointed out, if you need it.
by stock base, i mean OTA to 1.19.605.22
Battery Saver Mode Settings
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
klarthur said:
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Click to expand...
Click to collapse
This modification can be done using Magisk, without editing /system. You need to cache-mount the edited default.xml using Magisk, and Magisk mount the patched SystemUI.apk and HtcPowerManager.apk from @andybones' deodexed stock ROM. HUUUGE thanks to @Captain_Throwback for helping me figure this out and tolerating all-too-frequent stupid mistakes getting to this point, and, of course, none of this would be possible without the amazing efforts of @topjohnwu in creating Magisk in the first place.
I will post detailed instructions if someone is interested.
jackebuehner said:
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
Click to expand...
Click to collapse
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Chewieez said:
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
jackebuehner said:
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
Click to expand...
Click to collapse
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
mrbacks said:
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
Click to expand...
Click to collapse
You'll likely need a custom kernel for that, which means root access and either unlocked bootloader or S-OFF. Once you're in that boat, you'll need Magisk to clear Safety.net. It's not otherwise doable on pure unrooted stock. FWIW, if you are rooted, you can use @flar2's ElementalX kernel which is quite good, especially when used with the helper app allowing you to tweak all settings.
1.
Black shark2(only)
H0 : Download this firmware mp3
H0_EEA : Download this firmware mp3
rename "update.zip" then put it "ota" Directory in your phone(if you don't have this directory, make it)
if you find step bs2 pro downgrade, see this link
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Won't this break the sensors?
batuken said:
Won't this break the sensors?
Click to expand...
Click to collapse
which sensor?
ripiad said:
which sensor?
Click to expand...
Click to collapse
Proximity and accelorometer sensors. I've just tried it and it didn't break them. Thanks for this.
ripiad said:
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
I'm not sure if this is going to flash probably this way on BS 2 Pro, as this contain extracted partitions and there is a flash script 'flash_all.bat' which I made to flash those partitions.
So 'flash_all.bat' should be executed to flash this.
Click to expand...
Click to collapse
Thanks for this thread this will make it easier for people to understand.
ripiad said:
1.
Black shark2
H0 : Download this firmware mp3
H0_EEA : Download this firmware mp6
then up it "ota" Directory in your phone(if you don't have this directory, make it)
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
then up it "ota" Directory in your phone(if you don't have this directory, make it)
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Click to expand...
Click to collapse
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
spikywits said:
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
Click to expand...
Click to collapse
There are may bugs in joyui11.
Navigation buttom array can reverse in fullscreen display which located settings. (select mirror button)
Lock the background app is possible. view recent app(press home button or slide bottom up) and long press app what you want to lock.
Then, you can see lock icon
ripiad said:
There are may bugs in joyui11.
Navigation buttom array can reverse in fullscreen display which located settings. (select mirror button)
Lock the background app is possible. view recent app(press home button or slide bottom up) and long press app what you want to lock.
Then, you can see lock icon
Click to expand...
Click to collapse
Sorry. I forgot to mention - I need to do this for stock android 9 on BS2. Once I downgrade from 10 to 9.
The older joy ui navigation menu sucks. It offers only gesture navigation and no option to lock apps. There is no 3 button navigation like other android platforms.
spikywits said:
Sorry. I forgot to mention - I need to do this for stock android 9 on BS2. Once I downgrade from 10 to 9.
The older joy ui navigation menu sucks. It offers only gesture navigation and no option to lock apps. There is no 3 button navigation like other android platforms.
Click to expand...
Click to collapse
how about using this? using adb.
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
" "<- you can change this order
caution : when you reboot your phone, it go back previous
ripiad said:
how about using this? using adb.
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
" "<- you can change this order
caution : when you reboot your phone, it go back previous
Click to expand...
Click to collapse
Thanks for the trick. I think there must be a way to persist this setting.
If I remember correctly, there are apps on store to change dpi on non rooted phone, which runs some adb commands to change the dpi value and make it to persist across reboot.
or using fluid navigation gestures app
https://play.google.com/store/apps/details?id=com.fb.fluid&hl=en
2. Then dial this from your phone
Code: *#*#1027#*#*
Click to expand...
Click to collapse
This code is not working on my device skw-h0. Any help would be appreciated.
spikywits said:
This code is not working on my device skw-h0. Any help would be appreciated.
Click to expand...
Click to collapse
Did you use 3rd party dialer?
this method based on google dialer(require default dialer)
ripiad said:
Did you use 3rd party dialer?
this method based on google dialer(require basic dialer)
Click to expand...
Click to collapse
I use the stock dialer and it the default one, although I have truecaller installed along with.
Regardless, I managed to fix the issue.
I did the following:
Code:
adb reboot recovery
wipe/factory reset
with nothing installed, dialed *#*#1027#*#* and got the ota update app to popup.( I had the dpi set to lower than stock before reset, not sure that could be a reason for incompatibilities. )
Thanks, I will come back if I get into issues again with the downgrade.
spikywits said:
I use the stock dialer and it the default one, although I have truecaller installed along with.
Regardless, I managed to fix the issue.
I did the following:
Code:
adb reboot recovery
wipe/factory reset
with nothing installed, dialed *#*#1027#*#* and got the ota update app to popup.( I had the dpi set to lower than stock before reset, not sure that could be a reason for incompatibilities. )
Thanks, I will come back if I get into issues again with the downgrade.
Click to expand...
Click to collapse
I think truecaller make this issue.
additional dialer caused this situation
ripiad said:
I think truecaller make this issue.
additional dialer caused this situation
Click to expand...
Click to collapse
I don't think truecaller cause this.
I successfully downgraded from android 10 to 9. Installed truecaller and tested the dial code, it instantly popsup the update software.
Thanks for documenting the steps. Infact, I used the updated ota image from KM7 thread - SKYW2003090OS00MP6.
I will work on to root this device now and keep it on 9 forever. No more miui based Android 10
Update:
warning: flashing SKYW2003090OS00MP6 directly broke my sensors.
Had to flash the MP3 update.zip in the opening post to keep the sensors working. Thanks for the zip.
spikywits said:
Is there by any way I can get the navigation buttons at the bottom as like Android 10 or earlier than 9? the gesture based Android 9 is annoying and not able to lock the background app as we do on other android systems.
Click to expand...
Click to collapse
This can be done by turning off 'Swipe up on Home button' gesture, in Settings > System > Gestures.
spikywits said:
I don't think truecaller cause this.
I successfully downgraded from android 10 to 9. Installed truecaller and tested the dial code, it instantly popsup the update software.
Thanks for documenting the steps. Infact, I used the updated ota image from KM7 thread - SKYW2003090OS00MP6.
I will work on to root this device now and keep it on 9 forever. No more miui based Android 10
Update:
warning: flashing SKYW2003090OS00MP6 directly broke my sensors.
Had to flash the MP3 update.zip in the opening post to keep the sensors working. Thanks for the zip.
Click to expand...
Click to collapse
KM7 thread - SKYW2003090OS00MP6. is not OS00 firmware. that's OS01 firmware. Because I'm sharing this files first.
Today. I could get SKYW2003090OS00MP6 factory firmware(Korea ver.) so I'll modify it.
ripiad said:
1.
Black shark2
H0 : Download this firmware mp6
H0_EEA : Download this firmware mp6
then up it "ota" Directory in your phone(if you don't have this directory, make it)
Black shark2 pro
Download this firmware mp2 and rename update zip. - thank you for KM7
then up it "ota" Directory in your phone(if you don't have this directory, make it)
2. Then dial this from your phone
Code: *#*#1027#*#*
3. push "local update"
4. If it done, reboot your phone
5. Your phone enter recovery that requires factory reset. therefore, proceed factory reset your phone
6. wait for reboot
Click to expand...
Click to collapse
normal work on the black shark 2 pro DLT-H0?
my version is DLTR2004231OS00MQ0
I click on local update and nothing happens and non-local update when I click appears on the following message.
the list of update packages update / package_list does not exist