Database Users

[Q] Controlling key backlight LEDs

Has anyone figured out how to control the backlight on the Home, Menu, etc soft buttons on a rooted Epic?
I am looking in /sys/class/leds/ and there are five directories:
blue/
red/
mmc0::/
mmc1::/
mmc2::/
By changing the content of the brightness file in blue/ and red/ I am able to turn the blue and red notification LEDs on and off; but the mmc* directories don't seem to do anything, and I can't figure out how to control the softkey LEDs.
Code:
# cd /sys/class/leds/mmc0\:\:/
# cat brightness
0
# echo 255 > brightness
# cat brightness
0
# cat /sys/class/leds/device/leds/mmc0\:\:/brightness
1
# echo 0 > /sys/class/leds/device/leds/mmc0\:\:/brightness
# cat /sys/class/leds/device/leds/mmc0\:\:/brightness
1
What I primarily want to do is get those softkey lights to turn off and stay off while I am reading an ebook. This was easy on my Samsung Moment:
Code:
echo 0 > /sys/class/leds/button-backlight/brightness
Any clues?

I have been wanting this since the beginning. The softkey leds seem to be connected to the keyboard backlight. Even if I could just turn off the keyboard backlight entirely (i.e. changing the timeout does not help ebook reading), I would be happy.

Just set it to 3secs then it would turn off fast works for me when reading ebook.
Sent from my SPH-D700 using Tapatalk

Hmmm. The choice between a bright light shining in my face or a bright light flashing in my face? Neither are acceptable.

in fact, i hope it could be on when screen is on, although there is an option "Same as screen timeout", it simple set the timeout the same as screen's, i mean, they just do not sync. when you opened some app keep the screen on, the keys will fade a few moment later, no matter what you've set, that's really frustrating me!

I've been searching for the control file and found this. It looks promising, but its zero length. I was expecting it to contain a value like the blue & red ones.
Code:
/sys/devices/platform/s3c-keypad/brightness

After forgetting about this for a long while, I found it!
/sys/devices/virtual/misc/melfas_touchkey/brightness is the file that controls the softkey backlight on the Epic.
Use
Code:
echo 0 > /sys/devices/virtual/misc/melfas_touchkey/brightness
to turn off the backlight.
Code:
echo 1 > /sys/devices/virtual/misc/melfas_touchkey/brightness
to turn on the backlight.
Code:
chmod 0333 /sys/devices/virtual/misc/melfas_touchkey/brightness
to prevent other apps from changing the backlight's on/off status. And
Code:
chmod 0647 /sys/devices/virtual/misc/melfas_touchkey/brightness
to undo the previous line's lockdown.

Please post questions in General section.

Try out SimpleLEDToggle Plus in the Market. It's 99 cents. It didn't work for me but that's probably because I'm not rooted. There was a comment that it worked on the Epic. It specifically said that you can use it for reading ebooks with the lights off.
Sent from my SPH-D700 using XDA App

dennistpm said:
Try out SimpleLEDToggle Plus in the Market. It's 99 cents. It didn't work for me but that's probably because I'm not rooted. There was a comment that it worked on the Epic. It specifically said that you can use it for reading ebooks with the lights off.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Big plus if this works...I will check it out.

SimpleLedtoggleplus doesn't work. I lost my buck but I contacted the dev and told him about this thread. 15 minutes it too short. It should be 60 at least

This line does not work under 2.2 rooted,
Code:
echo 0 > /sys/devices/virtual/misc/melfas_touchkey/brightness
The updated line is
Code:
echo 2 > /sys/devices/virtual/misc/melfas_touchkey/brightness
Works for me, your mileage may vary.
The suggested chmod seems to have no impact, for me, nor does 0444 or 0000.
Now to find a way to tie a desktop icon to a shell script... (sure it's easy for you, but I'm a n00b)
Chisight

a way to tie a desktop icon to a shell script

ZenInsight said:
SimpleLedtoggleplus doesn't work. I lost my buck but I contacted the dev and told him about this thread. 15 minutes it too short. It should be 60 at least
Click to expand...
Click to collapse
Thing is, with android and linux being so free in regards with what you can do, 15 minutes is just under enough time to download the app, install, back up the app data, transfer it to your pc, then request a refund.
Sent from my Epic 4G via Tapatalk

It wouldn't take 15 mins to do that...
Sent from my Nexus S using XDA App

chisight said:
This line does not work under 2.2 rooted,
Code:
echo 0 > /sys/devices/virtual/misc/melfas_touchkey/brightness
The updated line is
Code:
echo 2 > /sys/devices/virtual/misc/melfas_touchkey/brightness
Works for me, your mileage may vary.
The suggested chmod seems to have no impact, for me, nor does 0444 or 0000.
Now to find a way to tie a desktop icon to a shell script... (sure it's easy for you, but I'm a n00b)
Chisight
Click to expand...
Click to collapse
Wow!!! Did you actually get the hard key lights to shut off???!

I've been wanting this for about a year now and finally found a solution.
I odin'd EF02Plus rom (gingerbread) yesterday and last night while reading I noticed that the button leds now do not come on when I touch the screen (YES!!!). The leds do come on just fine if you tap a hardware button. Perfect setup for night reading.
Not sure if this is the same in all EF02 based roms or not, but I'm guessing it probably is.

retrobits said:
I've been wanting this for about a year now and finally found a solution.
I odin'd EF02Plus rom (gingerbread) yesterday and last night while reading I noticed that the button leds now do not come on when I touch the screen (YES!!!). The leds do come on just fine if you tap a hardware button. Perfect setup for night reading.
Not sure if this is the same in all EF02 based roms or not, but I'm guessing it probably is.
Click to expand...
Click to collapse
You are kidding? That's it? I wonder if it's the rom or kernel.

Hey guys,
Not sure if this is still useful to anybody. I'm on EH 17 CM7.1 Kang and I found the values for controlling the brightness of the softkeys and the hardkeys
For the face soft keys (better reading ebooks):
Code:
/sys/devices/virtual/sec/t_key # echo 0 > brightness
For the keyboard keys (to save power either typing or playing emulated games):
Code:
/sys/devices/platform/s3c-keypad # echo 2 > brightness
Hope this helps.

thephawx said:
Hey guys,
Not sure if this is still useful to anybody. I'm on EH 17 CM7.1 Kang and I found the values for controlling the brightness of the softkeys and the hardkeys
For the face soft keys (better reading ebooks):
Code:
/sys/devices/virtual/sec/t_key # echo 0 > brightness
For the keyboard keys (to save power either typing or playing emulated games):
Code:
/sys/devices/platform/s3c-keypad # echo 2 > brightness
Hope this helps.
Click to expand...
Click to collapse
Very cool! Disabling soft key backlight does turn them off and stop them from lighting on screen press in cm7, but pressing a softkey lights them up again. I hope this info can help the screen filter app dev on our epics!

Auto Rotate

I installed the froyo beta, and ever since then, my phone won't auto rotate anymore. Ive already ODINed back to stock, it still wont work Any ideas or help?
-Edit-
I downloaded Accelerometer Test to make sure that the accelerometer wasn't busted. It's working fine. The phone just will not rotate.

Only two things I can think of:
1: Go to settings > Sound and Display > Make sure Orientation is checked.
2: (If using Launcher Pro). Menu button while on homescreen > Preferences > Behavior Settings > make sure Enable Auto-rotation is checked.
Other than that, no idea :\

SemiGamer said:
Only two things I can think of:
1: Go to settings > Sound and Display > Make sure Orientation is checked.
2: (If using Launcher Pro). Menu button while on homescreen > Preferences > Behavior Settings > make sure Enable Auto-rotation is checked.
Other than that, no idea :\
Click to expand...
Click to collapse
Its on, and i even toggled it. And no launcher pro. Just flashed stock

spitefulrain said:
Its on, and i even toggled it. And no launcher pro. Just flashed stock
Click to expand...
Click to collapse
On stock, the homescreens wont rotate unless the keyboard is slid out.
Is it rotating on the browser and on pictures?

SemiGamer said:
On stock, the homescreens wont rotate unless the keyboard is slid out.
Is it rotating on the browser and on pictures?
Click to expand...
Click to collapse
No. And if i slide the keyboard out, it rotates. But then it gets stuck in landscape unless i go to something that forces portrait mode, such as the home screen.

spitefulrain said:
No. And if i slide the keyboard out, it rotates. But then it gets stuck in landscape unless i go to something that forces portrait mode, such as the home screen.
Click to expand...
Click to collapse
Ah if its even getting stuck in landscape mode than its got to be something framework or .apk related.
Beats me, sorry man :\ Hope someone is able to help you more so than I could.

SemiGamer said:
Ah if its even getting stuck in landscape mode than its got to be something framework or .apk related.
Beats me, sorry man :\ Hope someone is able to help you more so than I could.
Click to expand...
Click to collapse
Im downloading a new copy of the DI18 for ODIN, hope it helps. Thanks anyway. If not i guess its time for my first replacement ever.

spitefulrain said:
Im downloading a new copy of the DI18 for ODIN, hope it helps. Thanks anyway. If not i guess its time for my first replacement ever.
Click to expand...
Click to collapse
please let me know if you find a solution. i have the exact same issue, caused the exact same way...

Wipe /data.

go to horizontal calibration in display settings on the froyo rom lay your phone on a level surface horizontally calibrate it and should work it did for me!!!!!!!!!!!!!!!!!!!!!!!!!!!

wcheek226 said:
go to horizontal calibration in display settings on the froyo rom lay your phone on a level surface horizontally calibrate it and should work it did for me!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
on which rom did you do this?
also, firon, wipe/odin, nothing works

found a solution:
"Originally Posted by tmspyder
I was able to recalibrate my g sensors as follows ..
This worked for me but I'll take no responsibility if it mucks something else up
1. Download a terminal app from the market
2. Enter one line at a time.
su
/system/bin/sensorcalibutil_yamaha
3. Follow the onscreen directions, while making sure you device is flat.
pay attention to the bump at bottom on back.
I hung said bump off the edge of table
I preformed this AFTER flashing to stock and then flashing my former ROM.
So it was not done in 2.2"
THANK YOU TO: tmspyder

Blush
THANK YOU TO: tmspyder
Click to expand...
Click to collapse
Your Welcome
Original source of the solution
smartanuj.com/samsung-galaxy-s-troubleshooting-and-optimizing-guide
Im not yet allowed to post links sorry

deleted post please ignore this inkspot

THANK YOU! I had the same problem and this fixed it. Of course, i had to root my shizzle again. By chance did anyone with this problem run the Froyo 2.2 built-in calibration before this came about?

Oh wow, thank you so much!! The fix using the terminal emulator totally worked for me too, I thought I was going to have to go back to stock to see if it would fix itself! After running the lines in the terminal, it still wouldn't automatically detect orientation, so went to the display settings, unchecked orientation, and checked it again, and now works perfectly! The lack of orientation was so frustrating, especially after using the keyboard and the only way to fix it was turning off the screen... thanks again!

Does this increase the speed of rotating in froyo beta cuz i noticed the rotating is really slow
Sent from my SPH-D700 using XDA App

deano0714 said:
Does this increase the speed of rotating in froyo beta cuz i noticed the rotating is really slow
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This helped for me. I was having the slow rotation problem as well. This fixed it. I didn't see results right away though. Took a few minutes and a restart to work
Sent from my SPH-D700 using Tapatalk

Just wanted to bump this. I had issues with auto rotation broken after going to DK28 and downgrading back to DI18.
I didn't test if it fixed it or not, however it did remove the annoying lag on DK28 when the screen rotates. Only reason I was downgrading

What terminal app did you use?
It says "su" is not found
Sent from my SPH-D700 using XDA App

Softeky lights on - off trackball on - off

Here is a couple of scripts of everyone, this will make your roms ANYROM for the eris turn on or off your trackball lights, and or softkey lights
I noticed a few roms that have problems with lights so I figured I would put these here to fix this problem.
If you just want to be able to turn on or off your softkey lights or trackball just download the script and put then in /sdcard/gscript
now download gscript app from the market and load a script file from sdcard
save the script and run threw gscript.
http://www.multiupload.com/1EWEV8MK48
If your a rom developer you can easily make these changes to the init.post-boot.sh and have the settings started at boot just add what ever script you want to init.post-boot.sh like this
open init.post-boot.sh add to file at the very top second line
Code:
# Initialize lights at boot to enable softkey lights noti$
echo 1 > sys/class/leds/vtkey-backlight/brightness
sleep 1
save and reboot.

So, to be clear, these scripts switch on or off the softkey lights and only switch on the trackball light, right? They do not enable or turn on the ability of the ROM to control these, right? For that you would have to incorporate some system components (or a 3rd-party app like Light Flow, which seems to be able to do the same thing). I'm not trying to give a hard time, just trying to understand how this works. I've tried doing similar things on evervolv and GST with no luck.
Oh, and one other thing, in your readme you mention
Notice, if you make trackball on run at boot your phone will lag, and after a while reboot this is a known issue to do with memory loss. Just run from gscript and you will be ok, it doesnt do anything to memory, just uses up all the ram/buffer so your phone reboots. if run at startup if it is just run through gscript everything will work fine.
Click to expand...
Click to collapse
What is the "known issue to do with memory loss?" I'm working on a navigation-related reboot problem at the moment and wondering about the ROM using up the RAM/buffer and if it is related. Mil gracias!

klobkelosh said:
So, to be clear, these scripts switch on or off the softkey lights and only switch on the trackball light, right? They do not enable or turn on the ability of the ROM to control these, right? For that you would have to incorporate some system components (or a 3rd-party app like Light Flow, which seems to be able to do the same thing). I'm not trying to give a hard time, just trying to understand how this works. I've tried doing similar things on evervolv and GST with no luck.
Click to expand...
Click to collapse
the lights on works but need to find out how to make them go off,, i add them to the rom but lights jjust stay on even with the phone sleeping , i sent a pm just waitin on a answer

Ok, you can use Light Flow from the market to control the lights but yes, this is only to enable and disable the light. for some reason roms are haveing a problem turning on the lights there just doesnt seem to be any one or off switch. I also have found that in alot of the roms a few that i have flashed that have been ported from the hero are missing a few of these lines
chown system system /sys/class/leds/vtkey-backlight/brightness
chown system system /sys/class/leds/amber/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/green/brightness
Click to expand...
Click to collapse
and few others like trigger,uevent if you want the full list ill pm it

androidifyme said:
Ok, you can use Light Flow from the market to control the lights but yes, this is only to enable and disable the light. for some reason roms are haveing a problem turning on the lights there just doesnt seem to be any one or off switch. I also have found that in alot of the roms a few that i have flashed that have been ported from the hero are missing a few of these lines
and few others like trigger,uevent if you want the full list ill pm it
Click to expand...
Click to collapse
im looking in my boot img and i see all those lines u mentioned

pming.....

ok ,, and btw i linked them to ur thread in the op

[MOD] Navigation Bar for CM10

Flashing this will enable navigation bar, and disable capacitive touch buttons on Nexus S.
Make sure to set the Backlight Dimmer delay to 0 using the NSTools, so the capacitive touch buttons don't light up.
If you are using the navigation bar, I recommend setting the LCD density to 200 or 190. Edit it with Rom toolbox, or
navigate to /system/build.prop/ro.sf.lcd_density=200 edit it with text editor and reboot.
Always do a backup before flashing. It should work for any JB rom.
To disable navigation bar, reflash the rom, restore the backup or flash disable nav bars.
You are doing this at your own risk.
Its based on Brainmaster's tweaks for android, all thanks goes to him.
Added files, they set dpi to 190 or 200 or disable Nav bars.

Screenshots please.
Gesendet von meinem Nexus S mit Tapatalk 2

AzN MusiQ said:
Screenshots please.
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
You get these three buttons on bottom of your screen.
http://cdn3.digitaltrends.com/wp-co.../samsung-galaxy-nexus-review-home-buttons.jpg

Or you can just add
qemu.hw.mainkeys=0
To your build.prop and reboot. It works with every ROM I think. To disable, just set it back to =1.
Sent from my Nexus S using xda premium

But that won't disable the capacitive buttons
Sent from my Nexus S using xda app-developers app

Does DPI of 200 break the play store? I'm at 210 and its breaking some installs

tehkraft said:
Does DPI of 200 break the play store? I'm at 210 and its breaking some installs
Click to expand...
Click to collapse
First time I went from 240 to 200, I wiped googleplay, everything else worked okay, as far as I remember.
If you get FC's wipe that app.

If BLD is set to zero, this will just turn off the backlight right, but they will still work when pressed. Is there a way to disable them for real otherwise what's the point of the nav bars, right?
Sent using the xda mobile app

apatal said:
If BLD is set to zero, this will just turn off the backlight right, but they will still work when pressed. Is there a way to disable them for real otherwise what's the point of the nav bars, right?
Sent using the xda mobile app
Click to expand...
Click to collapse
They are disabled...

Serris said:
They are disabled...
Click to expand...
Click to collapse
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app

apatal said:
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
Click to expand...
Click to collapse
Yes you are correct, I used NSTools, and set it to 0, I assumed its the same with CM settings, I will try to fix it. Thanks
EDIT: OK no go, CMsettings work like that, if its set to BLD 0 its always on, NSTools looks like overrides it.

great! this is working just great. really thanks! but i don't see any problem by leaving screen density to 240 though. been opened all apps installed on my ns
quick edit: i am using CM 10 nightly

What's about the menu button? Is it build in the apps? Can I configured them?
Gesendet von meinem Nexus S mit Tapatalk 2

AzN MusiQ said:
What's about the menu button? Is it build in the apps? Can I configured them?
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
Yes you can see the three dots in the navigation bar, and in aplications

Serris said:
Yes you are correct, I used NSTools, and set it to 0, I assumed its the same with CM settings, I will try to fix it. Thanks
EDIT: OK no go, CMsettings work like that, if its set to BLD 0 its always on, NSTools looks like overrides it.
Click to expand...
Click to collapse
I'm using a script it works like a charm with 0 if you don't use bln.
Sent from my Nexus S using xda premium

BenHeng said:
I'm using a script it works like a charm with 0 if you don't use bln.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
So all you have to do, is disable BLN, and put below code(script) in init.d?
Code:
echo 1 > /sys/devices/virtual/misc/backlightdimmer/enabled
echo 0 > /sys/devices/virtual/misc/backlightdimmer/delay

Works for me at least
Sent from my Nexus S using xda premium

Tried the mod last night and it works! Unfortunately, my fingers are already too big for the default PDI, and reducing it to 200 won't really help me very much. Thanks for sharing this anyway. I'm sure some users have been looking for this.
Sent using the xda mobile app

apatal said:
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
Click to expand...
Click to collapse
in order to turn off capacitive buttons follow these:
1. using root browser lit go to system.
2.then "usr" then " keylayout"
3. open sec_touchscree.kl > open as > text file > rb text editor
4. insert "#" in front of lines u want to make them stop working.
like
#key 158 BACK virtual
will make back button stop working.

Remove brightness slider.

Hello has año even able to remove the brightness slider in lollipop. Using sqlite did not work properly for me.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

have you considered getting a 3rd party brightness manager?
I don't know about 5+, but on 4.4.4 the brightness slider hides itself when the phone detects an app that manages auto-brightness.

thedicemaster said:
have you considered getting a 3rd party brightness manager?
I don't know about 5+, but on 4.4.4 the brightness slider hides itself when the phone detects an app that manages auto-brightness.
Click to expand...
Click to collapse
Yes but if I hide the notification from that app I get a bug like this.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

egren58 said:
Yes but if I hide the notification from that app I get a bug like this.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
hi,
i am on Lollipop (software.. BOC3) N910F, and using 3 rd party app, Lux and i am happy to say it notification "scales" fine as can see in snapshot
Point is that it can scale properly?
Good luck

willcor said:
hi,
i am on Lollipop (software.. BOC3) N910F, and using 3 rd party app, Lux and i am happy to say it notification "scales" fine as can see in snapshot
Point is that it can scale properly?
Good luck
Click to expand...
Click to collapse
Yes but try hiding all notification including lux.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

egren58 said:
Yes but try hiding all notification including lux.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
hi ,
Sorry ,hiding my relevant notifications is not an option to me ,as my apps need "it " to keep in memory/function ,as to not be "close/kill "by device or Greenify (?)
It needs the Notifications to functions properly../stay in memory .(.You would notice i have certain apps ,GMD gestures also Swipepad ,Nortons security ,eCid app .. to read certain notifications ...etc etc ,which is very important for me,that it works 100%)
Obviously your needs seems to differ ,to me as long as it scales right i am happy !
good luck in your quest .
post note ..however in lockscreen it also scales ok ( with my notifications )

egren58 said:
Hello has año even able to remove the brightness slider in lollipop. Using sqlite did not work properly for me.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
HERE. Simple guide

not-i said:
HERE. Simple guide
Click to expand...
Click to collapse
Not so simple for me. Lol i have no idea how to decompile
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

egren58 said:
Not so simple for me. Lol i have no idea how to decompile
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Then you'll need a SecSettings.apk from a rom with it already modded.

I didn't mod the SecSettings.apk, but I was able to remove the brightness adjustment by editing the settings database directly.
Here are the steps:
1. Install SQLite Debugger, if you haven't already.
2. Launch SQLite Debugger and open /data/data/com.android.providers.settings/databases/settings.db.
3. Open "system" table
4. Modify the SQL query in the followin manner: "SELECT * FROM system WHERE name='notification_panel_brightness_adjustment'
5. Run the query (click on arrow in the top right corner)
6. You should see the query result with 1 entry
7. Click on it and in the popped-up menu select "Update value"
8. Remove "name='notification_panel_brightness_adjustment'" from the query (after SET keyword) and replace it with "value='0'" (without double quotes)
9. IMPORTANT: make sure that you still have the "WHERE _id = xxx" (xxx is some number that matches the ID of notification_panel_brightness_adjustment entry)! Do not modify it. For reference, on my phone this ID is 279.
10. Run the query. You should see a toast message "1 row updated"
11. Click "Commit" in the lower right corner. And once again click "Commit" in the popped-up dialog
12. Reboot you phone and you are done.
Disclaimer: Instructions are provided as-is. Use at your own risk.

vponomarev said:
I didn't mod the SecSettings.apk, but I was able to remove the brightness adjustment by editing the settings database directly.
Here are the steps:
1. Install SQLite Debugger, if you haven't already.
2. Launch SQLite Debugger and open /data/data/com.android.providers.settings/databases/settings.db.
3. Open "system" table
4. Modify the SQL query in the followin manner: "SELECT * FROM system WHERE name='notification_panel_brightness_adjustment'
5. Run the query (click on arrow in the top right corner)
6. You should see the query result with 1 entry
7. Click on it and in the popped-up menu select "Update value"
8. Remove "name='notification_panel_brightness_adjustment'" from the query (after SET keyword) and replace it with "value='0'" (without double quotes)
9. IMPORTANT: make sure that you still have the "WHERE _id = xxx" (xxx is some number that matches the ID of notification_panel_brightness_adjustment entry)! Do not modify it. For reference, on my phone this ID is 279.
10. Run the query. You should see a toast message "1 row updated"
11. Click "Commit" in the lower right corner. And once again click "Commit" in the popped-up dialog
12. Reboot you phone and you are done.
Disclaimer: Instructions are provided as-is. Use at your own risk.
Click to expand...
Click to collapse
Thanks. I found one. But now is to remove the sfinder bar lol.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

egren58 said:
Thanks. I found one. But now is to remove the sfinder bar lol.
Click to expand...
Click to collapse
Oh, didn't notice that you already tried the SQLite route. But have you checked if this value stayed at '0' after reboot?

vponomarev said:
Oh, didn't notice that you already tried the SQLite route. But have you checked if this value stayed at '0' after reboot?
Click to expand...
Click to collapse
I actually went with the method posted a few pages back
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

egren58 said:
I actually went with the method posted a few pages back
Click to expand...
Click to collapse
Just out of curiosity, which one?

vponomarev said:
Just out of curiosity, which one?
Click to expand...
Click to collapse
Pulling a modded secsettinga with the option to disable the slider
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

vponomarev said:
Just out of curiosity, which one?
Click to expand...
Click to collapse
Any settings for sfiner in sqlite?
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

egren58 said:
Pulling a modded secsettinga with the option to disable the slider
Click to expand...
Click to collapse
Oh, ok. That works too
But for me it's just a one-time change ("set and forget" kinda thing), because I always use auto-brightness. Editing the DB is a quicker than modding the package.

vponomarev said:
Oh, ok. That works too
But for me it's just a one-time change ("set and forget" kinda thing), because I always use auto-brightness. Editing the DB is a quicker than modding the package.
Click to expand...
Click to collapse
Yeah true.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app

egren58 said:
Yeah true.
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
was u able to remove the brightness bar?

Souds hard to do man. U a true pro at it wish a new stuff like that