Database Develop

Tips - use G button as camera button / lock screen (change key binding)

I found it in a chinese forum (bbs.gfan.com/android-2014369-1-1.html)
I'm sure most people found the G button useless, so it would be nice to change that. The following is my experience with it:
The position of the G button make it perfectly useful as lock/unlock button, you can use it to shutdown as well, but cannot use it to switch on the phone, I guess it is electrically hardwired to the power button at the top.
Not too bad for camera, long press it will launch the camera app, but it don't have 2 levels so press it once and it will start auto-focus and take picture immediately, similar to touch and release shutter button in camera app, which mean you can't "dis-engage" a failed focus attempt.
here is the method:
1. make sure you have root and r/w to system partition
2. the file in question is "TWL4030_Keypad.kl", it's in /system/usr/keylayout/
3. before making any changes, copy the file to SDcard as a backup
4. open the file with any text editor, scroll down to 3rd line from the bottom, it should be "key 95 GESTURE"
5. if you want to use it as camera button, change it to "key 95 CAMERA WAKE_DROPPED"
if you want to use it as power/lock button, change it to "key 95 POWER WAKE_DROPPED"
6. save the changes, reboot to see the changes.

Very good.
In fact, I may even use this on nova.

the method is work.
after edit file it create backup file which is name "TWL4030_Keypad.kl.bak"

It works! Great!

worked perfectly thx!

thank u..
this work

hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??

My phone still on Original ROM.
After modify to Power/Lock mode, it's work.
but into Shutter mode, doesn't work.
Any idea?
SnoopyZ

digezter said:
hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??
Click to expand...
Click to collapse
did u reboot after making the changes?

digezter said:
hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??
Click to expand...
Click to collapse
notice you need to long press to start the Camera App. (you should feel the phone vibrate)
or just start the camera app, then press the G button to take a picture to see if it works.
It should be a pretty straight forward modification.

Could it be
"key 95 RECOVERY WAKE_DROPPED" ???

wow, very nice

Very nice. Thanks.
To all who could not manage get it to work: You must take care of file attributes after modyfing the file content ( otherwise it won't work ). It must be CHMOD 644.
( I use SD Maid for this )

It doesn't work for me, i am using pays ROM. Can someone upload the file? Thank u!
Enviado desde mi LG-P970 usando Tapatalk

"key 95 HEADSETHOOK WAKE"
to use headset button

I tried modifying the file and saving it ... but the it always comes up as an error and doesn't allow me to save it... any solutions???

you need to have your phone "root" AND mount system partition as read and write

fjsw said:
you need to have your phone "root" AND mount system partition as read and write
Click to expand...
Click to collapse
Hey my phone is rooted, how do I mount system partition a read and write ? Sorry I'm a noob

if you use ES File Explorer, goto setting, select 2 checkboxs "Root Explorer" and "Mount File System"
if you use root explorer, change directory to /system, then press "Mount R/W" button

yabgo said:
"key 95 HEADSETHOOK WAKE"
to use headset button
Click to expand...
Click to collapse
Sorry to ask but: what is the "headset button" and what is it good for?
Thanks,
Kusie

Allow or Disallow the Home key from waking up the Phone [Galaxy Note]

PREVENT - ALLOW GALAXY NOTE HOME KEY FROM ACCIDENTALLY WAKE UP DEVICE:
Some people complained about the Home keys of Galaxy Note sometime is touched and turned on accidentally when taking it in-out of the pocket.
After studying some articles on-line for Droid X phone (not same as the Galaxy Note), I digged around in the directory system/usr/ keylayout. Finally, I have found a way to do it. I can disable the HOME key from wake up the phone in off-screen state, but still let it to move from apps drawer to standby screen as usual. And I think it works!!
- Goal: Modify 2 file related to wake up function of the Home key (code 102).
- How to:
+ Using Root Explorer go to the folder: system/usr/keylayout, set permission to Mount R/W;
+ Click to select the 2 files: gpio-key.kl and sec_key.kl to modify them. When the menu appears, select: Text Editor to modify the files.
+ Move to the line: "key 102 HOME WAKE" in the 2 files above and put the cursor on the position of "WAKE" to erase the word "WAKE".
+ Press Menu hard button, select Save Changes, the phone will save the backup file and save the current files.
+ Set permission to Mount R/O for the folder: system/usr/ keylayout.
+ Shut down and then restart, Ahh, it worked!
Note: If you want to use Home key to wake up Galaxy Note again, go to delete two above modified files and rename the two backup files to gpio-key.kl and sec_key.
For people don't want to do it manually, I make the 2 flashable files for Allow and Disallow the Home key for Note and tested for working, at least on my Galaxy Note.
The 2 flashable files to do that is attached below. Copy to SDCard/ExternalCard and flash them in CWM Recovery, then reboot:

works for me. thx.
Sent from my GT-N7000 using XDA

kui425 said:
works for me. thx.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
OK. Hope that help.
Thanks for reply.

flashable zip
Could you make a flashable zip file for this?
Would be great!
Thanks in advance...

bunique said:
Could you make a flashable zip file for this?
Would be great!
Thanks in advance...
Click to expand...
Click to collapse
Yes..please.
+1
GT-N7000-LiquidSmooth-V [2.2] .

Wish I could give u more thanks for this. Works like a charm. Very very annoying that the home button would wake the phone up by default.

Flashable files to Allow or Disallow the wake-up function of Home key for Note
Flashable file for Allow and Disallow the Home key for Note
Phew! I tried my best to make the flashable file and tested for working, at least on my Galaxy Note.
Here is the link for Allow and Disallow the Home key for Note.
Copy to your SDCard and flash them with CWM Recovery.
Hope them could help.
bunique said:
Could you make a flashable zip file for this?
Would be great!
Thanks in advance...
Click to expand...
Click to collapse
firasusman said:
Yes..please.
+1
GT-N7000-LiquidSmooth-V [2.2] .
Click to expand...
Click to collapse

a big THANKS for the flashable files!
will give it a try....

Works perfectly, thanks
Cassie's xtra lite v2.9

Good Job

AWESOME. thanks!

Do not work on JB SLIM BEAN
Sent from my GT-N7000 using Xparent ICS Blue Tapatalk 2

I can not thank you enough for this as I have struggled with this issue for the past 12 months and as my job is a dirty one I can feel my phone getting hot in my pocket but cannot take it out as by hands are black. Thanks.

looks like this is not working in Jelly Bean / Cyanogen 10.1
vasiaeva said:
Do not work on JB SLIM BEAN
Sent from my GT-N7000 using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
does somebody know whitch file(s) to edit for this to work in Jelly Bean or Cyanogenmod 10.1.
I'm on asylum 4.2.2.this is a cyanogen 10.1 mod , like slim bean .
It looks like we need to change more/other files for this to work , wile when i canche the here adviced ones , nothing seems to change ,, the volume buttens still behave the same.
/system/usr/keylayout/sec_key.kl is changed to..
key 115 POWER WAKE
key 114 POWER WAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
look at line 115 and 114 this would change te volume button function in the power funtion , i suspect , AM I RIGHT ????
in fact this does not change the behavior of the volume buttons at all it still changes te volume , btw i did restart after changing te sec_key.kl file
please advice manny thanks in advance

Is it possible to add long press action to Home key or other capacitive keys like in CM roms ? How to make it turn on flash light ?

Any idea if this works on the s4 too?

StuartTheFish said:
Any idea if this works on the s4 too?
Click to expand...
Click to collapse
Just tried, and yes it does work on the s4. We only have the one file though, gpio-key.kl. Same location though. Find the line that says home, and delete the word wake. Save changes and reboot, job done!

[Q] Noob just rooted with KindlFirste Aide

Sorry should have posted here in first place
Hi all
Eventually........have rooted KFHD then got brave and installed Google Market....only issue is that KFHD will not auto rotate and bottom menu bar is missing.
Any help please?

Download LMT https://www.dropbox.com/s/h7xwelcg8uzyaee/LMT_v1.91.apk.... Install.
Open and choose start service. Click the pie tab at the top and configure your pie items. (eg. Pie item 1, set to home. Pie item 2, set to back. Etc)
If you want the stock softkeys/navbar back then do this next:
Download ES File Explorer here https://www.dropbox.com/s/u227um3vt3o2yzx/ES.apk
Install and open. Open the menu (using one of the LMT pie buttons you created) scroll to the bottom. Choose root settings. Check all (grant su permission)
Navigate to /system/
Open build.prop with es note editor. Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back.
Sent from my KFHD using xda premium

Visual help.
Sent from my KFHD using xda premium

Krsmqn said:
Download LMT https://www.dropbox.com/s/h7xwelcg8uzyaee/LMT_v1.91.apk.... Install.
Open and choose start service. Click the pie tab at the top and configure your pie items. (eg. Pie item 1, set to home. Pie item 2, set to back. Etc)
If you want the stock softkeys/navbar back then do this next:
Download ES File Explorer here https://www.dropbox.com/s/u227um3vt3o2yzx/ES.apk
Install and open. Open the menu (using one of the LMT pie buttons you created) scroll to the bottom. Choose root settings. Check all (grant su permission)
Navigate to /system/
Open build.prop with es note editor. Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back.
Sent from my KFHD using xda premium
Click to expand...
Click to collapse
Thanks for reply Krsmqn.
I have downloaded and installed LMT. Set pies to menu, back etc I already have ES File Explorer installed.
Now i get lost ............. Open the menu (using one of the LMT pie buttons you created) scroll to the bottom. Choose root settings. Check all (grant su permission)
Navigate to /system/
Open build.prop with es note editor. Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back...........
Sorry for being thick but can you please explain this part a bit more?
Many thanks
fs1023
found .....Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back...........
It is already set at 0

Krsmqn said:
Visual help.
Sent from my KFHD using xda premium
Click to expand...
Click to collapse
I have gone to Pie and set menu etc but how do i set permissions?

Sure.
I assume that one of the pie keys have been set to the menu option.
Check the pictures below.
The first picture is the settings bar. Choose settings.
Scroll down to "root settings" (see second picture near the bottom)
Open root settings and make sure all are checked, 3rd picture (4 or 5 boxes, depends on version) and grant su permission.
Navigate to the /system/ folder as seen in 4th picture.
click on build.prop and choose ES Note Editor, as seen in 5th picture
Find the code I point out in the 6th picture and carefully change the 1 to a 0 by clicking on the screen. If it already says 0, then we need to get you the softkeys.apk.
lets try this first.
Sent from my KFHD using xda premium

Exuse my ignorance....i get picture 1 but where are the others from? KFHD menu?

fs1023 said:
Exuse my ignorance....i get picture 1 but where are the others from? KFHD menu?
Click to expand...
Click to collapse
The 2nd and 3rd picture are of the settings menu in ES File Explorer. The others are the ES File Explorer interface and the build.prop properties.
I see you found the qemu.hw.mainkeys and have found it set to zero.
Ok. lets try this...
Gimme a second to prepare the files.

Went through your instructions mate and that code IS set to 0

Before we have you download anything, let's make sure you need to.
Open ES File Explorer and navigate to the /system/app/ folder. Look to see if you have "SoftkeyBar.apk" installed.

Yes mate its a square grey box with 'Kindle' written on it.
BTW how do I buy you a beer for your help?

fs1023 said:
Yes mate its a square grey box with 'Kindle' written on it
Click to expand...
Click to collapse
Hmm... I'm puzzled. There's no reason for you to have no softkey bar.
Go back to Build.prop file in /system/
Sometimes there's a second entry of "qemu.hw.mainkeys=1" in there. Look for it.
Could you also let me know what method you used to root?
---------- Post added at 02:35 PM ---------- Previous post was at 02:32 PM ----------
fs1023 said:
BTW how do I buy you a beer for your help?
Click to expand...
Click to collapse
I appreciate it but I quit drinking some time ago. Just knowing that I helped is enough. I've been blessed with outstanding help on these forums before, so I just want to pay it forward.

There is no 'second entry of "qemu.hw.mainkeys=1"
The qemu.hw.mainkeys=1 is qemu.hw.mainkeys=0 on my Kindle is this correct?
I rooted through Kindle firste aide step 21. Admitttidly it took me 4 times. I can/could not do a clean 'unroot' and in one instance it rooted the device again. Do you think i have corrupted files?

fs1023 said:
There is no 'second entry of "qemu.hw.mainkeys=1"
The qemu.hw.mainkeys=1 is qemu.hw.mainkeys=0 on my Kindle is this correct?
I rooted through Kindle firste aide step 21. Admitttidly it took me 4 times. I can/could not do a clean 'unroot' and in one instance it rooted the device again. Do you think i have corrupted files?
Click to expand...
Click to collapse
Yes, qemu.hw.mainkeys= # is the code. 1 or 0 is just the number that identifies the different state. So it's all good.
As far as why your nav bar isn't showing up...... I dunno. You have now passed the realm of which I can be of assistance.
I suggest you post your problem on the Kindle Fire First Aide thread. Be sure to include the information we have already covered to save some time.
I'm sorry I couldn't help you resolve the issue, but Chris (prokennexusa) and those guys on that thread will get you sorted out.
Good luck!

Ok thanks for all you time and help it has been most appreciated and keep up the good work in helping others.
regards
fs1023

Krsmqn said:
Yes, qemu.hw.mainkeys= # is the code. 1 or 0 is just the number that identifies the different state. So it's all good.
As far as why your nav bar isn't showing up...... I dunno. You have now passed the realm of which I can be of assistance.
I suggest you post your problem on the Kindle Fire First Aide thread. Be sure to include the information we have already covered to save some time.
I'm sorry I couldn't help you resolve the issue, but Chris (prokennexusa) and those guys on that thread will get you sorted out.
Good luck!
Click to expand...
Click to collapse
Hi all
Can anyone follow on from Krsmqn and help me with my problem?
Sent from my KFTT using Tapatalk 2

fs1023 said:
Hi all
Can anyone follow on from Krsmqn and help me with my problem?
Sent from my KFTT using Tapatalk 2
Click to expand...
Click to collapse
Sent from my KFTT using Tapatalk 2

Krsmqn said:
Download LMT https://www.dropbox.com/s/h7xwelcg8uzyaee/LMT_v1.91.apk.... Install.
Open and choose start service. Click the pie tab at the top and configure your pie items. (eg. Pie item 1, set to home. Pie item 2, set to back. Etc)
If you want the stock softkeys/navbar back then do this next:
Download ES File Explorer here https://www.dropbox.com/s/u227um3vt3o2yzx/ES.apk
Install and open. Open the menu (using one of the LMT pie buttons you created) scroll to the bottom. Choose root settings. Check all (grant su permission)
Navigate to /system/
Open build.prop with es note editor. Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back. "
Sent from my KFHD using xda premium
Click to expand...
Click to collapse
I have always wanted to know how to change the DPI but I didn't want to fiddle around and softbrick I have a factory cable but hate to pull it out, Would you mind taking a screenshot of the line I have to edit for the DPI change?
Sent from my KFTT using xda app-developers app

Open build.prop with ES Note Editor (found in /system/)
Find the code below. Change it, back out without changing anything else. Save. Reboot.
Sent from my KFHD using xda premium

Forgot image. Here it is. Be very careful.
Sent from my KFHD using xda premium

[TWEAK] Remove Brightness Slider from Notification Panel

This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.

guyd said:
This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.
Click to expand...
Click to collapse
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.

Yoshi910 said:
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.
Click to expand...
Click to collapse
I can mod systemui.apk to remove them, if you want it.

mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol

guaneet said:
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol
Click to expand...
Click to collapse
haha, yea im not a fan of having a ton of threads all with mostly the same thing. ill see what i can do about the toggles, i can for sure get rid of the other stuff.

You can also simply install Lux and turn off its persistent notification

Could this be used to do other tweaks like remove icons/clock from the status bar?

mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.

teiglin said:
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.
Click to expand...
Click to collapse
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.

mikeyinid said:
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.
Click to expand...
Click to collapse
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Edit for basic instructions:
Use a root-enabled file manager or console to replace /system/priv-app/SystemUI/SystemUI.apk with the attached file, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz. Make sure the permissions of the new SystemUI.apk are rw-r--r-- (chmod 644 /system/priv-app/SystemUI/SystemUI.apk at the console). Reboot and enjoy.
Caveat: you may not be able to swipe away notifications from within the region previously taken up by the sfinder/qconnect bar.

Great! Can also be done via adb:
Code:
adb shell settings put system notification_panel_brightness_adjustment 0

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Thanks! Works great.

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
How would you get it to work, I tried to install it but it won't install.

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Worked fine, thanks !

EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons

EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
v2.2v said:
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons
Click to expand...
Click to collapse
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.

teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
That worked flawlessly, thank you.

teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
perfect! thank you so much

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...

Painless001 said:
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...
Click to expand...
Click to collapse
BINGO. Yea i forgot to mention that in my response, as well. Always fix permissions

[guide] black navigation bar

Hey all. Other day i look around floating_feature.xml in system/etc and i found the line for config nav bar:
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_NAVIGATION_BAR_THEME>SupportLightNavigationBar|SupportForceTouch|SupportCustomBgColor|SupportNaviBarRemoteView</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_NAVIGATION_BAR_THEME>
I think if theres an option "SupportLightNavigationBar" lets see if "SupporrDarkNavigationBar" works. And it worked
Don't know if anyone have dicover that but i wann share it with you.
Final code:
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_NAVIGATION_BAR_THEME>SupportLightNavigationBar|SupportForceTouch|SupportCustomBgColor|SupportNaviBarRemoteView|SupportDarkNavigationBar</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_NAVIGATION_BAR_THEME>

marquelito said:
Hey all. Other day i look around floating_feature.xml in system/etc and i found the line for config nav bar:
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_NAVIGATION_BAR_THEME>SupportLightNavigationBar|SupportForceTouch|SupportCustomBgColor|SupportNaviBarRemoteView</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_NAVIGATION_BAR_THEME>
I think if theres an option "SupportLightNavigationBar" lets see if "SupporrDarkNavigationBar" works. And it worked
Don't know if anyone have dicover that but i wann share it with you.
Final code:
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_NAVIGATION_BAR_THEME>SupportLightNavigationBar|SupportForceTouch|SupportCustomBgColor|SupportNaviBarRemoteView|SupportDarkNavigationBar</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_NAVIGATION_BAR_THEME>
Click to expand...
Click to collapse
It works only for rooted S9?

Meknes23 said:
It works only for rooted S9?
Click to expand...
Click to collapse
I think you can push it via adb. If anyone could help with it

marquelito said:
I think you can push it via adb. If anyone could help with it
Click to expand...
Click to collapse
Fairly sure you need to be rooted to mod system files even with ADB, or at least have TWRP installed, in which case you might as well root too as you have already tripped KNOX

or you can just use this app:
https://play.google.com/store/apps/details?id=by4a.setedit22
set
need_dark_navigationbar to 1
need_dark_statusbar to 1
then go switch it to black..
you might need adb initially to get the app permission but its only needed to do once.. actually, you dont need permission for that as its in system settings.. if u want to change secure or global settings you need to set the adb perms

*Detection* said:
Fairly sure you need to be rooted to mod system files even with ADB, or at least have TWRP installed, in which case you might as well root too as you have already tripped KNOX
Click to expand...
Click to collapse
not true in this case.. those values are in settings.. you can do it in adb also if you use the settings binary similar to what i just posted.. the app is probably the easiest tho plus u can edit pretty much any setting with the app

elliwigy said:
or you can just use this app:
https://play.google.com/store/apps/details?id=by4a.setedit22
set
need_dark_navigationbar to 1
need_dark_statusbar to 1
then go switch it to black..
you might need adb initially to get the app permission but its only needed to do once.. actually, you dont need permission for that as its in system settings.. if u want to change secure or global settings you need to set the adb perms
Click to expand...
Click to collapse
Just changed those lines both to 1, but no black has appeared
Also I have a problem with low notification / ringtone sounds, I see there are level settings for that too
What is the adb command to get the full permissions for the app to edit everything? The values are reset back to 0 after a reboot

*Detection* said:
Just changed those lines both to 1, but no black has appeared
Also I have a problem with low notification / ringtone sounds, I see there are level settings for that too
What is the adb command to get the full permissions for the app to edit everything? The values are reset back to 0 after a reboot
Click to expand...
Click to collapse
Did you have any luck figuring this out? The settings don't seem to stick on reboot.

knoxjon said:
Did you have any luck figuring this out? The settings don't seem to stick on reboot.
Click to expand...
Click to collapse
Not with this method, I use this now instead, works flawlessly
https://play.google.com/store/apps/details?id=org.inteks.samtweak2&hl=en
Exclude the app from power saving though or you'll need to open it again to reapply some of the tweaks

knoxjon said:
Did you have any luck figuring this out? The settings don't seem to stick on reboot.
Click to expand...
Click to collapse
not sure why u guys have a hard time lol.. i change the value to 1 then wait a few mins then when i go to navbar settings its black..
works every time for me