Related
I dont know how many other people out there use androids built in vpn, but i hate the fact that you are required to use a security screen (pattern, pin, password) to do so. I have found a way to bypass this if you are rooted. This has only been tested on the stock kk rooted ota. However i would think it is the same on almost any stock based rom.
This assumes you already have your vpn and a security screen setup and working.
Go to the market and download a root capable data base (db) editor. I use SQLite Editor which is a paid app, but im sure there are free ones too.
Open the db editor. SQLite Editor sorts it by the app (in this case Android System) the data base is associated with, others may not work this way and may require you to navigate to the db file directly (/data/system/locksettings.db).
Open locksettings.db and select the locksettings directory. Look for the line that says "lockscreen.password_type". Under the value colum it will show some random number. Select the line and edit the value to be 0 (zero). Save if required by your db app, and restart your phone.
When it reboots you should no longer have a security lock screen only the swipe up screen. When you go to settings - more - vpn, it will still say you need to setup a security lock. Hit CANCEL, and it will show you your list of setup vpn's. Select one and connect. Boom working vpn with no pattern, pin, password screen required.
To undo this just go to settings - security - screenlock, and setup a new lock pattern, pin, or password.
You can also disable the swipe up lock screen by editing the "lockscreen.disabled" value in the locksettings.db to be a 1 instead of a 0.
good write up, thank you sir.
Where did you get stock kk rooted?
Sent from my HTC One
I was already unlocked and s-off, so i ruu'd took the kk ota and then rooted it. But i believe santod has his thread in development where you can download the stock rooted kk rom.
an alternative method
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Alternative method
found it on another forum
The process does not require rooting its more like a bug
worked on my i9300 with 4.3 firmware
1. Add a VPN
2. Lock the device with a pin
3. Enter the pin wrong 5 times
4. Press OK to the message that pops up
5 Press Forgot Pin
6. Sign into your Google Account
7. Select pin lock
8. Press cancel.
and now u got unlocked screen with working vpns
the method works, but after I reboot, when I enter VPN screen is aks me for "password for credential storage"... how can I solve? thanks in advance
Hirishiolo said:
the method works, but after I reboot, when I enter VPN screen is aks me for "password for credential storage"... how can I solve? thanks in advance
Click to expand...
Click to collapse
Yeah i have the same issue (nexus 10 rooted 4.4.3 stock)
Hit cancel, and it should bypass it.
cmlusco said:
Hit cancel, and it should bypass it.
Click to expand...
Click to collapse
it should.... but it does not for me (Sony Xperia Z1 with CM11 4.4.3)
schickel said:
it should.... but it does not for me (Sony Xperia Z1 with CM11 4.4.3)
Click to expand...
Click to collapse
same for me, it does not work
ebackbone said:
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Click to expand...
Click to collapse
Thank you :good:
ebackbone said:
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Click to expand...
Click to collapse
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
i am on kk 4.4.2
vadimo said:
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
i am on kk 4.4.2
Click to expand...
Click to collapse
My locksettings.db is empty as well. Does anybody know why?
Geilerzucker said:
My locksettings.db is empty as well. Does anybody know why?
Click to expand...
Click to collapse
on mine one its not empty
Hirishiolo said:
same for me, it does not work
Click to expand...
Click to collapse
i also followed the tutorial now and same as you guys, doesnt work
worked for me initially on samsung mega (jellybean), but after reboot i'm getting the 'enter password for creditial storage' issue and pressing cancel doesn't solve it.
is there any other solution?
In 4.4 there is no such file
Code:
/data/system/locksettings.db
.. any ideas?
Clauu said:
In 4.4 there is no such file
Code:
/data/system/locksettings.db
.. any ideas?
Click to expand...
Click to collapse
Try a different file manager.
It failed like that for me with ES File Explorer,
but worked when I used SM File Browser.
---------- Post added at 10:53 AM ---------- Previous post was at 10:42 AM ----------
vadimo said:
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
Click to expand...
Click to collapse
Tap on the "QUERY *" button to see the file contents.
---------- Post added at 11:11 AM ---------- Previous post was at 10:53 AM ----------
pajenn said:
worked for me initially on samsung mega (jellybean), but after reboot i'm getting the 'enter password for creditial storage' issue and pressing cancel doesn't solve it.
Click to expand...
Click to collapse
What I do here: just type something.. anything, doesn't matter. At least one character.
Then on the next screen, where it asks to set up a lockscreen, just Cancel.
This seems to be necessary once per boot -- any password, different time or the same, works.
After that it lands me on the VPN manager screen, all functional.
Well I kind of messed up. I tried to open with SQLite but it would give me an error 14. So i decided to try to open just like that using ES Explorer and edit it like regular note(SQL is totally different I had no idea). Anyways i didnt edit anything but now i cant set a pin or any type of security on my phone. When i try to set up a pin it still shows a swipe and when i try again my Note 3 freezes and get an error message saying settings stopped responding.
Any idea on how to fix this? Im rooted and im running the latest firmware 4.4.2 if that helps.
Sorry for the newb question but, I'm not able to get venom rom tweaks to hold the ability to keep system as r/w. I'm trying to make changes to build.prop and default.prop but they keep reverting on boot. I imagine I need to flash one of the boot images as mentioned in the first couple posts but am not sure which one would work with Rogers/Tbaytel GSM. It's odd tho cause selinux does hold permissive when set thru venom tweaks. Kernel changes thru an editor won't stick either.
Running
Viper 6.0
Elemental X 5 kernel
Rooted and S-off
Managed to get kernel to save settings now by disabling remaining write protection using su adb shell command. Haven't tested the .prop edits yet but I will shortly. Also wondering what does ro.rilvmail settings effect as viper build seems to be based of European area.
Update: Prop settings still revert on reboot. Going to try to adb push and pull a configured prop file.
How are you changing the file? It could be an app issue. I have had issues with certain file explorers not saving files properly or at all. I have best luck with es file explorer.
Make sure the file permissions are correctly set before you reboot.
Beamed in by telepathy.
shivadow said:
How are you changing the file? It could be an app issue. I have had issues with certain file explorers not saving files properly or at all. I have best luck with es file explorer.
Make sure the file permissions are correctly set before you reboot.
Beamed in by telepathy.
Click to expand...
Click to collapse
All good man I was able to use adb with root permission to remount and push altered build.prop file just not able to do default.prop but no biggie it was only to change the default USB connection. My only question relates to the ro.rilvmail settings now and what they would be for Canadian Rogers/tbaytel. Phone is almost perfect just have to use qpst and such to enable all network bands in my area and I will finally have my ultimate M9. There are not enough words to describe how amazing this phone is with all these tweaks and mods thank you so much to xda for making this all possible and the community of devs for your invaluable work.
Bump anyone have any info??
I was trying to change model no. In build prop but after reboot changes not save.
Check if you have root. Bcoz sometimes magisk fails to function properly.
Laz said:
Check if you have root. Bcoz sometimes magisk fails to function properly.
Click to expand...
Click to collapse
Thanks for the suggestion and you are right there is a magisk module(external sd card enabler) which keeps on reverting the build.prop edits........ So than i figure it out that i have to edit build.prop which is created by magisk module in magisk folder in system or delete the module than edit build.prop
Again Thanks for your help!!!?
You're welcome!
Doesn't magisk prevents system modification ? It's how it works, correct me if I'm wrong.
You can't tweak via root explorer, you can't flash the usual twrp flashable stuff, you gotta build your magisk module. Which is in all honestly uber simple and very convenient.
you are far from right duck...
Magisk is a root solution, so you get to have the rights. You can edit via file explorer , granted with root permission. Lolz. Building Modules is really simplified thou, right on that mate.
"YOU CAN TWEAK, via Root Explorer, lol. <-from a guy using Magisk. You just gotta need that root.
Yup.
Pretty much as OP I did a bunch of root editing / flashed some stuff via twrp, and nothing remained at reboot. Never saw that before, and since it works with magisk I may had jumped to conclusions too fast.
figured it out!!!!!
i know im late to the party but i recently came across this same problem. all yous gotsa doos is modify the build.prop located in /sbin/.magisk/mirror/system
after saving changes just check thru all the other location you know for build.prop just to double check that the changes have been made. if the build.prop is not the same in all locations, then the changes will not stick. if the changes affect all system build.props your good to go reboot device and do whacha do (note: just the system build.prop, not the vendor).
sm00th4f3 said:
you are far from right duck...
Magisk is a root solution, so you get to have the rights. You can edit via file explorer , granted with root permission. Lolz. Building Modules is really simplified thou, right on that mate.
"YOU CAN TWEAK, via Root Explorer, lol. <-from a guy using Magisk. You just gotta need that root.
Click to expand...
Click to collapse
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
i know im late to the party but i recently came across this same problem. all yous gotsa doos is modify the build.prop located in /sbin/.magisk/mirror/system
after saving changes just check thru all the other location you know for build.prop just to double check that the changes have been made. if the build.prop is not the same in all locations, then the changes will not stick. if the changes affect all system build.props your good to go reboot device and do whacha do (note: just the system build.prop, not the vendor).
v1nd1cta85 said:
figured it out!!!!!
i know im late to the party but i recently came across this same problem. all yous gotsa doos is modify the build.prop located in /sbin/.magisk/mirror/system
after saving changes just check thru all the other location you know for build.prop just to double check that the changes have been made. if the build.prop is not the same in all locations, then the changes will not stick. if the changes affect all system build.props your good to go reboot device and do whacha do (note: just the system build.prop, not the vendor).
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
i know im late to the party but i recently came across this same problem. all yous gotsa doos is modify the build.prop located in /sbin/.magisk/mirror/system
after saving changes just check thru all the other location you know for build.prop just to double check that the changes have been made. if the build.prop is not the same in all locations, then the changes will not stick. if the changes affect all system build.props your good to go reboot device and do whacha do (note: just the system build.prop, not the vendor).
Click to expand...
Click to collapse
Thanks, this helped me out.
I'm using the Magisk module but it doesn't seem to be working
GroovinChip said:
I'm using the Magisk module but it doesn't seem to be working
Click to expand...
Click to collapse
So many variables in play with getting the native hotspot working. Mine is working fine. I'm on a Google Pixel XL. (Verizon) Android 9. Unlocked. Rooted (with Magisk 16.7 (1671)), Magisk Manager 5.8.3, and using the module MagiskHide Props Config to set the prop net.tethering.noprovisioning to true.
On Android 8 and earlier, the module "Tethering Enabler" worked, but I found it no longer worked once I upgraded to Android 9. The module MagiskHideProps Config allows you to set various custom props systemlessly (much as we used to back in the day by just editing the build.prop). You can find information on how to use the module on XDA and it is linked in the module documentation itself. (The module is very well documented. and creates a terminal UI that you execute from a terminal on your device (or via ADB if prefer). I use Termux (from play store on my device). Once you get the custom prop setup via the "Props" program, you can verify it is working via terminal emulator on the device or from computer/ADB by running as root getprop net.tethering.noprovisioning and verifying it returns true. I suspect that your issue is with the Tethering Enabler module (assuming that is what you are using) as I don't believe it was updated to keep up with the changes in Magisk and perhaps Android 9.
Anyways - good luck. Let me know how it goes.
sb1893 said:
So many variables in play with getting the native hotspot working. Mine is working fine. I'm on a Google Pixel XL. (Verizon) Android 9. Unlocked. Rooted (with Magisk 16.7 (1671)), Magisk Manager 5.8.3, and using the module MagiskHide Props Config to set the prop net.tethering.noprovisioning to true.
On Android 8 and earlier, the module "Tethering Enabler" worked, but I found it no longer worked once I upgraded to Android 9. The module MagiskHideProps Config allows you to set various custom props systemlessly (much as we used to back in the day by just editing the build.prop). You can find information on how to use the module on XDA and it is linked in the module documentation itself. (The module is very well documented. and creates a terminal UI that you execute from a terminal on your device (or via ADB if prefer). I use Termux (from play store on my device). Once you get the custom prop setup via the "Props" program, you can verify it is working via terminal emulator on the device or from computer/ADB by running as root getprop net.tethering.noprovisioning and verifying it returns true. I suspect that your issue is with the Tethering Enabler module (assuming that is what you are using) as I don't believe it was updated to keep up with the changes in Magisk and perhaps Android 9.
Anyways - good luck. Let me know how it goes.
Click to expand...
Click to collapse
If you're on Verizon you don't need to anything other than root the phone and the hotspot will work just fine.
airmaxx23 said:
If you're on Verizon you don't need to anything other than root the phone and the hotspot will work just fine.
Click to expand...
Click to collapse
That is only if you are subscribed to the hotspot as part of your plan. Most Verizon plans include some level of hotspot subscription - albeit with throttling to barely usable speeds after hitting data thresholds. I didn't mention that I am on a grandfathered unlimited plan which does not include hotspot. The setting of that build.prop that I mentioned circumvents the subscription check and allows my hotspot to work. Even if rooted, without that prop set, I hit the subscription check and am told to contact Verizon to subscribe. As I said - lots of variables with getting hotspot to work.
sb1893 said:
That is only if you are subscribed to the hotspot as part of your plan. Most Verizon plans include some level of hotspot subscription - albeit with throttling to barely usable speeds after hitting data thresholds. I didn't mention that I am on a grandfathered unlimited plan which does not include hotspot. The setting of that build.prop that I mentioned circumvents the subscription check and allows my hotspot to work. Even if rooted, without that prop set, I hit the subscription check and am told to contact Verizon to subscribe. As I said - lots of variables with getting hotspot to work.
Click to expand...
Click to collapse
I'm not on a hotspot plan and all I've ever done is root my device (currently a Pixel XL) and setup the hotspot and it works. I'm also grandfathered in with unlimited data and I did it just recently when installing Pie.
airmaxx23 said:
I'm not on a hotspot plan and all I've ever done is root my device (currently a Pixel XL) and setup the hotspot and it works. I'm also grandfathered in with unlimited data and I did it just recently when installing Pie.
Click to expand...
Click to collapse
Hmmmm - well that is interesting and certainly a different experience than mine. I've always had to do some level of mod - build.prop edits, modified carrierentitlement.apk in the SuperSu days and then tethering enabler or the systemless prop edit I just described on Magisk....(I'm also on a Pixel XL / Stock)
sb1893 said:
Hmmmm - well that is interesting and certainly a different experience than mine. I've always had to do some level of mod - build.prop edits, modified carrierentitlement.apk in the SuperSu days and then tethering enabler or the systemless prop edit I just described on Magisk....(I'm also on a Pixel XL / Stock)
Click to expand...
Click to collapse
Yeah that is a bit strange.
BuildProp Editor
Add line:
net.tethering.noprovisioning=true
save
reboot
crackerjack1957 said:
BuildProp Editor
Add line:
net.tethering.noprovisioning=true
save
reboot
Click to expand...
Click to collapse
This did it, thanks!
Sent from my Google Pixel XL using XDA Labs
Here is the newest module for magisk. Works for me.
tweaked said:
Here is the newest module for magisk. Works for me.
Click to expand...
Click to collapse
Cool - I didn't realize that module had been updated to work on PIE. Looks like a few viable options to get tethering working depending on preference. I'm going to stick with the MagiskHideProps method for now as it also allows for other systemless build.prop edits if any are needed in the future....Thanks, all!
tweaked said:
Here is the newest module for magisk. Works for me.
Click to expand...
Click to collapse
Do you install this via recovery? Or do I have to drop zip into a specific folder?
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
sb1893 said:
Cool - I didn't realize that module had been updated to work on PIE. Looks like a few viable options to get tethering working depending on preference. I'm going to stick with the MagiskHideProps method for now as it also allows for other systemless build.prop edits if any are needed in the future....Thanks, all!
Click to expand...
Click to collapse
Curious what you are using to edit build prop. I have MagiskHideProps installed via Magisk but not sure how to edit build prop
cwburns32 said:
Do you install this via recovery? Or do I have to drop zip into a specific folder?
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Curious what you are using to edit build prop. I have MagiskHideProps installed via Magisk but not sure how to edit build prop
Click to expand...
Click to collapse
You can Flash with TWRP just make sure you know where you put it. I like to keep my stuff in downloads.
Sent from my Pixel XL using Tapatalk
cwburns32 said:
Do you install this via recovery? Or do I have to drop zip into a specific folder?
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Curious what you are using to edit build prop. I have MagiskHideProps installed via Magisk but not sure how to edit build prop
Click to expand...
Click to collapse
There are build.prop editors on the play store to make it easier
cwburns32 said:
Do you install this via recovery? Or do I have to drop zip into a specific folder?
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Curious what you are using to edit build prop. I have MagiskHideProps installed via Magisk but not sure how to edit build prop
Click to expand...
Click to collapse
MagiskHideProps allows you to enjoy the effect of editing build.prop without actually physically altering the file. You are basically injecting build.prop values into system memory at boot time (my understanding). This achieves the same effect as editing build.prop without making changes to the file itself in system. (systemless change) Once you have installed MagiskHideProps you can use a terminal emulator on your phone or ADB Shell session via your computer to execute the simple program "Props". The documentation of MagiskHideProps is very detailed and easy to follow. You need to add a new prop set to True for net.tethering.noprovisioning. Good luck.
S
roman.ramirez.12 said:
You can Flash with TWRP just make sure you know where you put it. I like to keep my stuff in downloads.
Click to expand...
Click to collapse
Phalanx7621 said:
There are build.prop editors on the play store to make it easier
Click to expand...
Click to collapse
sb1893 said:
MagiskHideProps allows you to enjoy the effect of editing build.prop without actually physically altering the file. You are basically injecting build.prop values into system memory at boot time (my understanding). This achieves the same effect as editing build.prop without making changes to the file itself in system. (systemless change) Once you have installed MagiskHideProps you can use a terminal emulator on your phone or ADB Shell session via your computer to execute the simple program "Props". The documentation of MagiskHideProps is very detailed and easy to follow. You need to add a new prop set to True for net.tethering.noprovisioning. Good luck.
S
Click to expand...
Click to collapse
Thank you all. I ended up using zip file but still have MagiskHideProps installed for future build.prop edits. Thanks again!
guys my hotspot is unlocked i just want to hide my hotspot useage from verizion. is there a guide to do this???
crackerjack1957 said:
BuildProp Editor
Add line:
net.tethering.noprovisioning=true
save
reboot
Click to expand...
Click to collapse
Excellent! I edited the build.prop using a text editor and added this setting but to no avail. I guess the trick is to use the BuildProp Editor app and follow your instructions. My Pixel 3 XL's native hotspot works like a champ now. Thanks again!!!!
crackerjack1957 said:
BuildProp Editor
Add line:
net.tethering.noprovisioning=true
save
reboot
Click to expand...
Click to collapse
:good: You rock! Quick and easy fix. Did it in less than a minute and that included downloading the app.
*****ONLY WORKS FOR FIREOS 5.6.2.0 OR LOWER*****
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0 or 5.6.2.0****
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
Code:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
4. Long press power button. Score. :highfive:
P.S. This framework also contains all previous modifications. References:
How to guide: Enable 'ok Google' to work from ANY screen
[ROOT] [HD 10 2017] FireTabletSettings.apk Rewritten [August 22, 2018]
[FIRMWARE] [STOCK] Pre-rooted, optimized, stock firmware for HD 10 Suez [APRIL 2019]
[Root] [HD 10 Suez] Remove parental control applications/restrictions [May 2019]
[TEST] [Flash Zip] [HD 10] [ROOT] All-in-1: The ultimate hacks, tricks & mods zip
[Root] [App] [All tablets] Disable & replace lock screen - set custom wallpaper
NO ROOT REQUIRED: Working Screen Mirroring
UPDATE (for 5.6.1.0):
June 1, 2019
- Increased default system volumes from -6 db to 8
- Set preference for 5ghz wifi to false. Setting this to true only allows 5ghz connections. 2ghz are ignored if set to true.
- Fixed typo in time server I found in the system logs.
- Extend network attributes (I don't know if these actually work but doesn't hurt either way)
- Wpa_supplicant_scan_interval by default is set to 15000.... milliseconds. Raised value to 150000000. This may have been the cause of disconnects on a constant level.
- preferences prefer dual pane set to true
- Bar separating notifications from system messages was narrow (set to true). Set it to false.
- Low battery warning is now 10% instead of 25%. Extreme low battery warning (almost dead battery) set at 5%
DragonFire1024 said:
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.a
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0*** (5.6.2.0 comes soon. Possibly 5.3.x.x)
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
Code:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
4. Long press power button. Score. :highfive:
Click to expand...
Click to collapse
I have updated to the latest, 5.6.3.0 (erroneously called 5.3.6.4). I guess it is risky to do this until someone tries it and says it works? I've been using retyre's prerooted installs for the last couple of releases. So if this screws things up, I would have to adb sideload and root again, which I'd like to avoid.
Ignoring that issue, can the file just be copied into the correct folder with a file manager since I'm already rooted?
sga999 said:
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.a
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0*** (5.6.2.0 comes soon. Possibly 5.3.x.x)
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
I have updated to the latest, 5.6.3.0 (erroneously called 5.3.6.4). I guess it is risky to do this until someone tries it and says it works? I've been using retyre's prerooted installs for the last couple of releases. So if this screws things up, I would have to adb sideload and root again, which I'd like to avoid.
Ignoring that issue, can the file just be copied into the correct folder with a file manager since I'm already rooted?
Click to expand...
Click to collapse
There was one report of it working a week or two ago. No one has said anything since. If it doesn't work, worst case is you need to flash back to 5.6.x.x
DragonFire1024 said:
There was one report of it working a week or two ago. No one has said anything since. If it doesn't work, worst case is you need to flash back to 5.6.x.x
Click to expand...
Click to collapse
1. If it fails, and I'm unable to boot, I will have to redo the sideload of the bin file. Then I have to reroot. As I said, I've just been using the prerooted version for the last couple of releases which means I don't have to go through extra steps to root. Since I am rooted, I just use Flashfire to flash the new prerooted version by retyre.
2. I was asking about copying the framework file that you put out there. If I ignore the problems of it possibly messing up my system, and I just want to try it anyway, why is it necessary to use Adb insecure and the PC? Since I'm rooted, can't your framework file just be copied to the correct folder?
3. Finally, can you tell me exactly what you changed in the framework? In your other thread about modifying the framework, you give some good instructions on how to decompile and recompile. I might want to try that instead of using the version that you have created here (since I'm on 5.6.3.0). Is it really just one boolean that needs to be changed?
sga999 said:
1. If it fails, and I'm unable to boot, I will have to redo the sideload of the bin file. Then I have to reroot. As I said, I've just been using the prerooted version for the last couple of releases which means I don't have to go through extra steps to root. Since I am rooted, I just use Flashfire to flash the new prerooted version by retyre.
2. I was asking about copying the framework file that you put out there. If I ignore the problems of it possibly messing up my system, and I just want to try it anyway, why is it necessary to use Adb insecure and the PC? Since I'm rooted, can't your framework file just be copied to the correct folder?
3. Finally, can you tell me exactly what you changed in the framework? In your other thread about modifying the framework, you give some good instructions on how to decompile and recompile. I might want to try that instead of using the version that you have created here (since I'm on 5.6.3.0). Is it really just one boolean that needs to be changed?
Click to expand...
Click to collapse
1. Yes
2. With a root explorer yes.
3. For this? An integer was all. Everything else? That's too much to type. Honestly I spend hours and days reading them testing and mostly failing. I can't tell you the amount of bookmarks i have, maybe close to 500 or more. A lot of times I have to mix together old tricks. you spend most time reading than anything.
DragonFire1024 said:
1. Yes
2. With a root explorer yes.
3. For this? An integer was all. Everything else? That's too much to type. Honestly I spend hours and days reading them testing and mostly failing. I can't tell you the amount of bookmarks i have, maybe close to 500 or more. A lot of times I have to mix together old tricks. you spend most time reading than anything.
Click to expand...
Click to collapse
I don't understand your answer to 3. I'm just interested in what you changed in the framework-res to get the advanced power menu. You said it's just an integer. If I decompile framework-res.apk, where is the integer that must be changed? When you said "everything else", maybe you mean all your changes in the thread about hacks, tricks, and mods? I'm not asking about those. I'm only asking about the advanced power menu that you are talking about in this thread.
sga999 said:
I don't understand your answer to 3. I'm just interested in what you changed in the framework-res to get the advanced power menu. You said it's just an integer. If I decompile framework-res.apk, where is the integer that must be changed? When you said "everything else", maybe you mean all your changes in the thread about hacks, tricks, and mods? I'm not asking about those. I'm only asking about the advanced power menu that you are talking about in this thread.
Click to expand...
Click to collapse
If you decompile it, it would be in res/values/integers. The config would be (paraphrasing) 'long_press_on_power'. Since in this AOSP framework the global actions are active, you have a choice of values of 0 or 1. 0 being no action, 1 being the action. It's a few lines away from 'long_press_on_home' which is supposed to be between 0 and 3. 2 would activate the voice assist. But for some reason I haven't figured out, setting that value does nothing one way or the other but gravitybox fixes it.
You can change around the global action menu too I saw, but didn't have time to experiment with that yesterday.
@DragonFire1024
Nice hack! Like your new power menu - always wanted something like that!
Now, given that it'd be such a burden to update this for every FireOS version, any chance you'd take a stab at putting this together as an Xposed module? Other rooted Fire tablets could use it too.
I recall sometime in the past there were modules designed for FireOS - if you find that on XDA, you could start from that one.
DragonFire1024 said:
If you decompile it, it would be in res/values/integers. The config would be (paraphrasing) 'long_press_on_power'. Since in this AOSP framework the global actions are active, you have a choice of values of 0 or 1. 0 being no action, 1 being the action. It's a few lines away from 'long_press_on_home' which is supposed to be between 0 and 3. 2 would activate the voice assist. But for some reason I haven't figured out, setting that value does nothing one way or the other but gravitybox fixes it.
You can change around the global action menu too I saw, but didn't have time to experiment with that yesterday.
Click to expand...
Click to collapse
Here's what is in my integers.xml file for 5.6.3.0. Are you saying I need to change 2 to 1 in the first one? And no changes to the others?
<integer name="config_longPressOnPowerBehavior">2</integer>
<integer name="config_shortPressOnPowerBehavior">1</integer>
<integer name="config_doublePressOnPowerBehavior">0</integer>
<integer name="config_triplePressOnPowerBehavior">0</integer>
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
sga999 said:
Here's what is in my integers.xml file for 5.6.3.0. Are you saying I need to change 2 to 1 in the first one? And no changes to the others?
<integer name="config_longPressOnPowerBehavior">2</integer>
<integer name="config_shortPressOnPowerBehavior">1</integer>
<integer name="config_doublePressOnPowerBehavior">0</integer>
<integer name="config_triplePressOnPowerBehavior">0</integer>
Click to expand...
Click to collapse
Correct. First config set to 1 and leave the others as is, unless you want to test them out.
Rortiz2 said:
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
Click to expand...
Click to collapse
I have not. I rarely touch that at least not Amazon smali. It doesn't translate well at all. And haven't really had to so far. And the framework is odexed...well the .jar in system/framework is, so they don't have smalis.
bibikalka said:
@DragonFire1024
Nice hack! Like your new power menu - always wanted something like that!
Now, given that it'd be such a burden to update this for every FireOS version, any chance you'd take a stab at putting this together as an Xposed module? Other rooted Fire tablets could use it too.
I recall sometime in the past there were modules designed for FireOS - if you find that on XDA, you could start from that one.
Click to expand...
Click to collapse
I was thinking about that however if gravity box works to bring out the rest (reboot etc) I imagine other power menu modules will also work now.
DragonFire1024 said:
I was thinking about that however if gravity box works to bring out the rest (reboot etc) I imagine other power menu modules will also work now.
Click to expand...
Click to collapse
Gravity box might work - AFTER your framework-res.apk replacement (which needs updating after each OS version). As is, for me Gravity does not bring anything out beyond the stock "Power off" option. It seems a module could simply patch framework with the correct flag, and then Gravity will do its thing. Same logic would apply to other features that Amazon might have chosen to disable.
bibikalka said:
Gravity box might work - AFTER your framework-res.apk replacement (which needs updating after each OS version). As is, for me Gravity does not bring anything out beyond the stock "Power off" option. It seems a module could simply patch framework with the correct flag, and then Gravity will do its thing. Same logic would apply to other features that Amazon might have chosen to disable.
Click to expand...
Click to collapse
Install framework in OP then you need to enable the advanced power menu in gravitybox, power tweaks. Then long press power button, tap restart, then you get your options for reboot.
Rortiz2 said:
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
Click to expand...
Click to collapse
Also for the most part Amazon just moved configurations around maybe changed a few characters or couple of words. But for the most part a significant portion if not almost all of the Android source for this version was left inside these files. There are very few things I actually had to rebuild. The battery stats is one of those things. Other things are more difficult and require other pieces of software, for example specific apks. That took quite a lot of time to hunt down working versions of certain apks. Remember we are working with what is considered a stone age OS version. So we have to literally search for needles and haystacks just to find the one tiny thing that makes it all work... Well at least some of it
Gosh, I tried for a long time to decompile/recompile framework-res.apk (5.6.3.0)...no luck! I'm using your instructions in post 2 in the 7 wallpaper thread as a guideline. I can decompile successfully. Then, even without making any changes at all, recompile does not work. I won't bother to put the error display here unless you're interested. (systemui.apk fails on the recompile also, but in a different way). A "regular application" will decompile and recompile just fine.
So I have no idea what's wrong. I do have xposed/gravitybox installed, and I wonder if that causes the problem (but it sounds like have those also?). Or some change to 5.6.3.0 that you did not encounter with prior releases. I'm wondering if you can upload your framework-res.apk somewhere so that I can try that. At least that would narrow it down to the new release or my error.
There are lots of posts about this kind of problem, but they mostly talk about wrong paths, etc. That is definitely not my issue.
I had downloaded the most recent apktool, 2.3.4. Just for fun, I just tried 2.2.0. There are 4 warnings, but otherwise, it worked. I haven't tried to install the new framework, so I can't be sure all is okay, but it's certainly a good sign. I will also try more recent versions of apktool, i.e. ones between 2.2.0 and 2.3.4, and see where it went wrong.
EDIT: 2.3.2 and earlier are good, 2.3.3 and 2.3.4 are bad.
---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------
If it ain't one thing, it's another! After changing the integer, I'm trying to drag and drop with 7zip from the new apk to the old, as you described in your other thread. For resources.arsc, it works as you said, i.e. it asks if I'm sure I want to copy. But for the res folder, it doesn't ask me anything and just starts extracting into the old. I cancel it before it can complete.
Do you recall doing something different for the res folder? I could be on a different 7zip version than you, of course. I've used 7zip, but I'm not that familiar with it.
EDIT2: I don't think a notification is done if my edit gets combined with my prior post. I tried both reply and quick reply, and both ended up combining. Can someone tell me how to make it do a new post? Or maybe I'm wrong and another notification occurs, in which case, ignore this!
sga999 said:
I had downloaded the most recent apktool, 2.3.4. Just for fun, I just tried 2.2.0. There are 4 warnings, but otherwise, it worked. I haven't tired to install the new framework, so I can't be sure all is okay, but it's certainly a good sign. I will also try more recent versions of apktool, i.e. ones between 2.2.0 and 2.3.4, and see where it went wrong.
EDIT: 2.3.2 and earlier are good, 2.3.3 and 2.3.4 are bad.
---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------
If it ain't one thing, it's another! After changing the integer, I'm trying to drag and drop with 7zip from the new apk to the old, as you described in your other thread. For resources.arsc, it works as you said, i.e. it asks if I'm sure I want to copy. But for the res folder, it doesn't ask me anything and just starts extracting into the old. I cancel it before it can complete.
Do you recall doing something different for the res folder? I could be on a different 7zip version than you, of course. I've used 7zip, but I'm not that familiar with it.
EDIT2: I don't think a notification is done if my edit gets combined with my prior post. I tried both reply and quick reply, and both ended up combining. Can someone tell me how to make it do a new post? Or maybe I'm wrong and another notification occurs, in which case, ignore this!
Click to expand...
Click to collapse
Lol it's going to take a bit to get used to everything. I actually had messed around with apktool when I first started all this and got so frustrated I just stopped trying. 6 months after that I tried again and it took me a week or so before I successfully compiled and installed a system apk. My initial goal was to use this method to try and trick a non rooted tablet into thinking it was installing an update to a system app. Though it worked on rooted devices, I could never get it to work for non rooted ones. Don't give up,keep trying and re check everything, especially make sure your PATH to the proper tools is correct. I'll look at the latest fireOS framework tomorrow.
P.S. without any further modifications, I tested APM+ Xposed module and it works too. You can add and remove all the optioions plus add different ones depending on the module. No further tweaking needed on my end.
Okay, when dragging and dropping res, it does finally ask if I really want to copy AFTER it takes quite a while "extracting". I was confusing extracting with unzipping or unpacking...or some other term that would imply it was changing the format. I'm still not sure if it's doing it properly, but I'll keep trying. And I'd still like to know how to make these combined posts cause a notification, and if not, how can I force it to.