Disable soft button lights on aosp? - Verizon Samsung Galaxy Note II

I am running the unofficial AOKP. 4.3. It has the option to disable the lights on the soft buttons, but it works for a second and just comes back on. Anyone know how to get rid of them? It's really annoying reading in the dark.
Sent from my SCH-I605 using XDA Premium 4 mobile app

lightsout said:
I am running the unofficial AOKP. 4.3. It has the option to disable the lights on the soft buttons, but it works for a second and just comes back on. Anyone know how to get rid of them? It's really annoying reading in the dark.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Depends on what ROM you are using.
PAC used to have this issue with devil kernel. The latest builds work, and the soft button lights don't go on.

kimdoocheol said:
Depends on what ROM you are using.
PAC used to have this issue with devil kernel. The latest builds work, and the soft button lights don't go on.
Click to expand...
Click to collapse
Oh is that right? Because I am using Devil. Pac has become too bloated imo trying to stay away from it. Thanks for the help.

Yeah, pac has that same issue with 4.3.1 but it wasn't present in 4.3 so probably something changed that had to be fixed. But yes, pac no longer has that issue.
Sent from my SCH-I605 using Tapatalk

Related

screen delay on aokp rom

based on the aokp rom-->http://forum.xda-developers.com/showthread.php?t=1574718
nobody seems to have a working solution for this problem...after clicking the power button, there is a 2-3 second delay for the screen to turn on..this started after flashing this rom.
i have tried:
1) removing widgets, live wallpaper, closing running apps, etc....
2) turn of crt animations
3) changed kernel to neak for aokp.
4) i flashed UCLE5 and the problem stopped but i dont want the stock.
nothing has worked. what else could be causing this?
xnotoriouzpakix said:
based on the aokp rom-->http://forum.xda-developers.com/showthread.php?t=1574718
nobody seems to have a working solution for this problem...after clicking the power button, there is a 2-3 second delay for the screen to turn on..this started after flashing this rom.
i have tried:
1) removing widgets, live wallpaper, closing running apps, etc....
2) turn of crt animations
3) changed kernel to neak for aokp.
4) i flashed UCLE5 and the problem stopped but i dont want the stock.
nothing has worked. what else could be causing this?
Click to expand...
Click to collapse
Posting in the thread, and starting a new one. Good work!
I believe this is the dreaded "DEEP SLEEP" bug.
Sent from my SGH-i777 using xda app-developers app
MotoMudder77 said:
Posting in the thread, and starting a new one. Good work!
Click to expand...
Click to collapse
Lol he wasn't satisfied with Tasks answer apparently? It's deep sleep bro. It's good for ya.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Phalanx7621 said:
Lol he wasn't satisfied with Tasks answer apparently? It's deep sleep bro. It's good for ya.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
:banghead::banghead::banghead::banghead::banghead::banghead:
brought to you by HAL 2000
bigsmitty64 said:
I believe this is the dreaded "DEEP SLEEP" bug.
Sent from my SGH-i777 using xda app-developers app
Click to expand...
Click to collapse
Phalanx7621 said:
Lol he wasn't satisfied with Tasks answer apparently? It's deep sleep bro. It's good for ya.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
^^^^^^^both of these.
Get it?
Sent from my SGH-i777 using XDA
It's all fine and dandy to say that it's deep sleep and that it's just how the phone works...I'd just like to know why it is that the HTC Inspire's screen comes on instantly with the button while its idle battery drain is twice as good as the S2. Clearly there's something wrong with the way Samsung is doing something.
DO NOT DOUBLE POST...

Static (hardware) keys dont light up sometimes. Help.

I'm running Mazdas AOKP 3.0 and ive noticed that on some AOSP ROMs sometimes the harware keys (home,menu, etc.) Dont light up. When I firsf flash rom they work fine but after a while they dont turn on most of the time. Anyone know how to fix this? Thanks for your help.
Sent from my PG86100 using xda app-developers app
DroidManIc said:
I'm running Mazdas AOKP 3.0 and ive noticed that on some AOSP ROMs sometimes the harware keys (home,menu, etc.) Dont light up. When I firsf flash rom they work fine but after a while they dont turn on most of the time. Anyone know how to fix this? Thanks for your help.
Click to expand...
Click to collapse
I'm not sure why they stop working with that ROM, but here's a post with a manual way to adjust the brightness.
ramjet73
So I gave it a try and it worked but it didn't. The lights turn on but now they wont turn off even when screen locks unless I reboot and then I have to edit again. So Ill keep searching. Thanks though man its better than it was...
Sent from my PG86100 using xda app-developers app

[MOD] disable/enable capacitive buttons

very simple mod very simple op
*** THIS IS FOR THE CAP BUTTONS - Menu - Home - Back - Search - not for nav bar ***
since the new cm rebase kernel was pushed some things have changed.
my old enable/disable no longer works on the new rebase so here is the new zips
should work on all cm/aosp based 4.2.2 and 4.3 roms
disable: http://www.blownco.com/index.php/doc_download/13402-disable-capacitive-buttons-new-jd81
enable: http://www.blownco.com/index.php/doc_download/13403-enable-capacitive-buttons-new-jd81
for 4.1.2 roms use
disable: http://www.blownco.com/index.php/doc_download/639-disable-capacitive-buttons-jd81-zip
enable: http://www.blownco.com/index.php/doc_download/640-enable-capacitive-buttons-jd81-zip
just flash in recovery and reboot *put both zip's on your phone* flash disable and reboot, if you dont like it then flash enable and go on with your day
if this zip doesnt work for you *ie buttons still work after reboot* well then you dont have the proper rom,
either go on with your day or
-open a file manager
-go to /system/usr/keylayout
-delete the file sec_touchkey.kl
-reboot and go on with your day
Nice! Thanks Jamie, will definitely come in handy for me Pie/Nav bar addition! :thumbup:
Sent from my SGH-I717 using xda app-developers app
I like how you want ppl to go on with their day lmao. Great mod!
From me to you thru my Gnex
Haven't tried the enable but the disable zip works on 4.3.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
pockets916 said:
Haven't tried the enable but the disable zip works on 4.3.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
it should, there was no change from 4.2.2 to 4.3 in the touch drivers like there was with 4.1.2 to 4.2.2
Wasn't sure if it did once I knew I wanted to share with others.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
supporting question
Hello, first off, well done with this, its working perfectly for my note on PAC JB rom, but was wondering if there is anyway to disable the lights for the buttons, they don't work, but still light up, just wondering, have been searching for a bit and will continue to, but thought I would ask here too, thanks again for all the work you do, have a good one!
MBrad10 said:
Hello, first off, well done with this, its working perfectly for my note on PAC JB rom, but was wondering if there is anyway to disable the lights for the buttons, they don't work, but still light up, just wondering, have been searching for a bit and will continue to, but thought I would ask here too, thanks again for all the work you do, have a good one!
Click to expand...
Click to collapse
Used to be in advanced settings so ask the dev to get them back
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
JamieD81 said:
Used to be in advanced settings so ask the dev to get them back
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I actually think that I found the setting through the rom, thanks for responding though, and again, thanks for the mod! :victory:
JamieD81 said:
Used to be in advanced settings so ask the dev to get them back
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I didn't find them in the carbon uput out either...lol it's cool I luv it any ways
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
cougar11 said:
I didn't find them in the carbon uput out either...lol it's cool I luv it any ways
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Yeah because we are currently using cm's msm8660-common device on carbon
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Bummer...
This doesn't work on Cyanogenmod 10.1 RC on my HTC EVO 4G LTE unfortunately. Bummer. I need to grab that new Nexus 5 when it comes out. I HATE capacitive buttons...
joniler said:
This doesn't work on Cyanogenmod 10.1 RC on my HTC EVO 4G LTE unfortunately. Bummer. I need to grab that new Nexus 5 when it comes out. I HATE capacitive buttons...
Click to expand...
Click to collapse
Check blownco there are files for cm10.1 there
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
edit: i updated op to link to older files
Thought I'd share this for anyone who wants to disable the capacitive button lights. Credit goes to the original post I found at..
http://forum.xda-developers.com/showthread.php?t=2210765
To turn off capacitive button lights:
1. Download a file manager with root access. I used Root Browser.
2. Go to system/lib/hw
3. Find the file named 'lights.msm8660.so'
4. Rename it to anything such as "lights.msm8660.so.old"
5. Reboot.

[Q]Landscape keyboard on Badseed Tranquil ROM

Just flashed the Badseed Tranquil ROM last night and noticed today that when I'm in landscape there is an empty space on the right of the keyboard. I can see through to the app behind the keyboard. Is that supposed to be like that or is there a way to fix it? Also I'm getting some reasonable lag while I'm using the keyboard that I didn't get before. Any help would be great.
Sent from my HTC6435LVW using xda app-developers app
What space on the keyboard , I'm not seeing it , snap a screen shot and show me . I will help any way I can .
BadSeed Tranquil DNA
screenshot
It's really odd. Tried dirty flashing back over and that didn't help either.
Sent from my HTC6435LVW using
xda app-developers app
I flashed using twrp and came from Hatka Supreme if that helps at all. I'm also having problems in the extended settings with the kernel options. Won't let me set tweaks on boot. Dunno if that's a Rom issue or kernel issue though. I'm running cubed but might switch back to beast. Thought cubed would help cuz since I installed roms my car charger won't charge the phone. Gives me the notification error message.
Sent from my HTC6435LVW using xda app-developers app
djeleet said:
It's really odd. Tried dirty flashing back over and that didn't help either.
Sent from my HTC6435LVW using
xda app-developers app
Click to expand...
Click to collapse
Try a clean flash. Dirty flashes are going to cause issues.
Sent from my HTC6435LVW using xda app-developers app
When I got hone from work I wiped everything and flashed from the beginning. Then the keyboard worked, then I put all my apps back on, went to send a txt and therer it was again. So I went into every app that I could use the keyboard on and discovered the empty space is only there in certain apps. My stock messaging and stock browser are fine but gosms and xda and chrome have the empty space by the keyboard. Really disappointing cuz I absolutely love the Rom otherwise. Blue is my favorite color and especially that color blue lol. My case and even my car is that shade blue hahaha. See if that problem happens with anyone else and if it ends up getting fixed in an update I will surely be switching back!
Sent from my HTC6435LVW using xda app-developers app
djeleet said:
I flashed using twrp and came from Hatka Supreme if that helps at all. I'm also having problems in the extended settings with the kernel options. Won't let me set tweaks on boot. Dunno if that's a Rom issue or kernel issue though. I'm running cubed but might switch back to beast. Thought cubed would help cuz since I installed roms my car charger won't charge the phone. Gives me the notification error message.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
This is a Kernel issue , I suggest BeastMode 5.9 , and you set the options you want in aroma . If you want to change things on the fly feel free to try another kernel , CP's kernel for example .
djeleet said:
When I got hone from work I wiped everything and flashed from the beginning. Then the keyboard worked, then I put all my apps back on, went to send a txt and therer it was again. So I went into every app that I could use the keyboard on and discovered the empty space is only there in certain apps. My stock messaging and stock browser are fine but gosms and xda and chrome have the empty space by the keyboard. Really disappointing cuz I absolutely love the Rom otherwise. Blue is my favorite color and especially that color blue lol. My case and even my car is that shade blue hahaha. See if that problem happens with anyone else and if it ends up getting fixed in an update I will surely be switching back!
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Bro I'm still not seeing it .
Sent from my HTC6435LVW using Tapatalk 4 Beta
That is so confusing. Maybe I was wrong and chrome wasn't one. I was trying to remember from last night lol. I know gosms definitely was one though cuz I send so many txts. Give it a try and if it doesn't do it for you then maybe it's an app that I installed that's making it do that. I also have lmt pie installed and that works from that side of the screen so it could possibly be that.
Sent from my HTC6435LVW using xda app-developers app
djeleet said:
That is so confusing. Maybe I was wrong and chrome wasn't one. I was trying to remember from last night lol. I know gosms definitely was one though cuz I send so many txts. Give it a try and if it doesn't do it for you then maybe it's an app that I installed that's making it do that. I also have lmt pie installed and that works from that side of the screen so it could possibly be that.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Ok I see what you are talking about , I tested on newts Rom and joelz rom and it seems to be a go sms issue as it does it on them too .
Sent from my HTC6435LVW using Tapatalk 4 Beta
Damn gosms! That's giving me issues with the floating notifications app too. Guess I might have to switch. I just hate the stock app so much and I dunno if any others out there have the privacy box with gesture lock like go has. Hmm will have to do some digging. Also do you know if the problem I'm having with my car charger saying it's unsupported on my phone is a kernel issue or Rom issue?
Sent from my HTC6435LVW using xda app-developers app
djeleet said:
Damn gosms! That's giving me issues with the floating notifications app too. Guess I might have to switch. I just hate the stock app so much and I dunno if any others out there have the privacy box with gesture lock like go has. Hmm will have to do some digging. Also do you know if the problem I'm having with my car charger saying it's unsupported on my phone is a kernel issue or Rom issue?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Stock kernel will give a slow charging warning , beastmode will get rid of that .
Sent from my HTC6435LVW using Tapatalk 4 Beta
Ok thank you so much for the help! Once I find a txt messaging app that will function the way I want it to and work with the Rom I will definitely be switching back. Any plans for put PA's Halo on your Rom in the future? That would be awesome. Just saying lol
Sent from my HTC6435LVW using xda app-developers app

Cm10.1 screen flicker

I'm running flyhalfs latest cm build and I'm getting screen flicker like crazy. I'm running crpalmers latest kernel and I have tried the stock kernel and it does the same thing. It won't do it for a few hours and then I'll turn my screen on and it will be flickering all around the edges . doesn't matter what brightness. Wondering of anyone has any ideas or if it's just a bug for now. Thanks.
Sent from my HTC6435LVW using xda app-developers app
Tiskra25 said:
I'm running flyhalfs latest cm build and I'm getting screen flicker like crazy. I'm running crpalmers latest kernel and I have tried the stock kernel and it does the same thing. It won't do it for a few hours and then I'll turn my screen on and it will be flickering all around the edges . doesn't matter what brightness. Wondering of anyone has any ideas or if it's just a bug for now. Thanks.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Other people have been reporting the same thing. I think I read someone saying disabling hw overlays in developer options helped. For some reason I'm not having this problem on carbon... Running crpalmers latest
Sent from my DNA using Tapatalk 2
Yea I found that and tried it out didn't seem to make a difference. It's so weird it sometimes it won't flicker at all and then I'll pull my phone out of my pocket and it will be flickering big time for a couple hours and then be gone again.
Sent from my HTC6435LVW using xda app-developers app
Tiskra25 said:
I'm running flyhalfs latest cm build and I'm getting screen flicker like crazy. I'm running crpalmers latest kernel and I have tried the stock kernel and it does the same thing. It won't do it for a few hours and then I'll turn my screen on and it will be flickering all around the edges . doesn't matter what brightness. Wondering of anyone has any ideas or if it's just a bug for now. Thanks.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
add script on your build.prop (need root access) ;
hwui.render_dirty_regions=false
if that appeared, then change to :
debug.hwui.render_dirty_regions=false
No need to do that. This thread is from June and crpalmer has worked out the screen a flickering bug about a month or two ago.
And, for the record, the fix is in the current CM 10.2 and 11.0 but not 10.1. If someone is on 10.1, please update!

Categories

Resources