Just recently i noticed that the botton 4 hardware buttons are not on during the homescreen. Is there a way i can fix this? it wasnt like this before. (yesterday) please help
i didnt flash anything last thing i remeber changing is replacing the phase beam wallpaper with a blue version
edit: also when i click them they blink
edit 2 : i did a battery pull and im on the screen and it works actually
edit 3: i take that back -_-
BLD. Configure it in NSTools
Harbb said:
BLD. Configure it in NSTools
Click to expand...
Click to collapse
Where is that? Is tgat backlight dimmer? But now that I'm using matr1x it works so far now
Sent from my Nexus S 4G flashed to Boost Mobile
Harbb said:
BLD. Configure it in NSTools
Click to expand...
Click to collapse
lol now i see. I had it on and configured to 0 ms delay. Thanks
Related
So if anyone is using jboogie's liquidarc rom, i have a question for you: can anyone succesfully run setcpu and milestone or setvsel and successfully overclock/undervolt and scale the cpu? when i do those and run the scaling script from sorensim's guide on modifying the defy, my home and search button stop working, haptic feedback works on them, but they dont do anything when pressed. I love this rom but i cant use it if those 2 keys dont work. ive wiped before and after restoring the rom, flashed the sbf 3.4.11 first and then restored, and then the boot sbf, and still no progess. any tips?
Is usb debugging enabled or disabled? Not sure if this will help, but worth a try to switch back and forth to see if it helps. I have been using liquidarc for a few weeks now and loving it with no real issues to speak of. I was using milestone (what came with rom), but have since removed and gone back to setvsel and have overclocked/undervolted without any issues. All my buttons work.
You might need to redo the steps, and download the files again as perhaps a file was corrupted during download/installation?
i dont see how usb debugging could be a problem, but ill try
I popped onto modmymobile...looks like jboogie just replied to your question.
darule_2011 said:
I popped onto modmymobile...looks like jboogie just replied to your question.
Click to expand...
Click to collapse
yeah i just saw, thanks for replying though
well problem still happens, dosent matter if i use setcpu, milestone, or setvsel, dosent matter if i dont overclock, just cpu scaling, it still happens
I had to shift to his wonderful Korean rom only because of this issue. Any app I use, end up with nonfunctioning home button and search button.
chaihg said:
I had to shift to his wonderful Korean rom only because of this issue. Any app I use, end up with nonfunctioning home button and search button.
Click to expand...
Click to collapse
ok jboogie showed me a fix, dont touch vsel or threshold and it should work perfectly.
zencoran said:
ok jboogie showed me a fix, dont touch vsel or threshold and it should work perfectly.
Click to expand...
Click to collapse
? I use SetvSel and it works perfectly..
I change the threshold to 84% and change completely the others.. They're still working. I got this problem too with Pays-Rom 5.1. The home button still had haptic feedback, but didn't function.
WIIstpM said:
? I use SetvSel and it works perfectly..
I change the threshold to 84% and change completely the others.. They're still working. I got this problem too with Pays-Rom 5.1. The home button still had haptic feedback, but didn't function.
Click to expand...
Click to collapse
jboogie told me not to touch the threshold and it should be fine so idk
i got no problem with LiquidArc and running SetVsel
Hey all. I just recently got an HOX and of course the first thing I did was root and flash a ROM. I'm on cm10 with rohan kernel and my LED isn't lighting up for notifications. It turns on when charging, red and green. It also works for notifications when plugged in but not when unplugged. Anyone else have this issue and or a fix?
pOLLYpOCKET said:
Hey all. I just recently got an HOX and of course the first thing I did was root and flash a ROM. I'm on cm10 with rohan kernel and my LED isn't lighting up for notifications. It turns on when charging, red and green. It also works for notifications when plugged in but not when unplugged. Anyone else have this issue and or a fix?
Click to expand...
Click to collapse
Which version of cm10 did you install (I mean date)
Sent from my Nexus 4 using xda app-developers app
Q: My Notification LEDs dont seem to work right?
A: Go to Settings -> Display -> Notification LEDs -> Add each application you want to have a notification for -> Set it to green color and long. (thanks to Richard V. for digging through this!)
abhipati said:
Which version of cm10 did you install (I mean date)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
11/26/12 nightly.
area51avenger said:
Q: My Notification LEDs dont seem to work right?
A: Go to Settings -> Display -> Notification LEDs -> Add each application you want to have a notification for -> Set it to green color and long. (thanks to Richard V. for digging through this!)
Click to expand...
Click to collapse
Did this. I'll try it out and report back. Thanks!
Hi all,
Since installing CM7 (20130201) and Mazout's 2.6.32.60 kernel, my phone's home and search buttons are no longer functioning. Any ideas how to fix it? These are important functions.
It also doesn't go to sleep anymore, even when I push the power button.
Sounds like some gremlin mischief. Have you tried using the nullifier to wipe?
Edit: here's the link
http://forum.xda-developers.com/showthread.php?t=1854850
Thanks TwitchyEye. That worked, for a while, but the issues are back now. And randomly, the menu/home/back/search icons light up when the phone's otherwise asleep.
TwitchyEye said:
Sounds like some gremlin mischief. Have you tried using the nullifier to wipe?
Edit: here's the link
http://forum.xda-developers.com/showthread.php?t=1854850
Click to expand...
Click to collapse
Maybe it's something you restored?
natescape said:
Thanks TwitchyEye. That worked, for a while, but the issues are back now. And randomly, the menu/home/back/search icons light up when the phone's otherwise asleep.
Click to expand...
Click to collapse
Those are your lights acting as a notification. You can turn it off in cyanogenmod settings.
Sent from my LG-P999 using xda app-developers app
Where might I find that in the settings? I went through and couldn't find it.
natescape said:
Where might I find that in the settings? I went through and couldn't find it.
Click to expand...
Click to collapse
Settings => CyanogenMod settings => Interface => LED notifications. I select unconfigured then, edit category settings, LED mode, and force LED off. I suppose if you wanted to you could set individual settings for applications. There's also a few apps in the play store that take care of it too.
Is there any way to disable soft key lights? (or complety the soft keys)
And of course not permamently I mean I won't disassembly my NS
using AirKernel.
Pls reply as soon as possible
Sensitivity said:
Is there any way to disable soft key lights? (or complety the soft keys)
And of course not permamently I mean I won't disassembly my NS
using AirKernel.
Pls reply as soon as possible
Click to expand...
Click to collapse
Hi
What ROM?
And do u mean just for notifications or literally entirely.
(I could see ur point if u do since I use the navigation bar for everything now)
But yes to both:
For notifications use NS tools app.
For "entirely" ID have to verify what to do so let me get back to U.
Vs Nexus S4G using tapatalk2
vidaljs said:
Hi
What ROM?
And do u mean just for notifications or literally entirely.
(I could see ur point if u do since I use the navigation bar for everything now)
But yes to both:
For notifications use NS tools app.
For "entirely" ID have to verify what to do so let me get back to U.
Vs Nexus S4G using tapatalk2
Click to expand...
Click to collapse
Rom: XenonHD 6.0
for notification, i want the key ligts to blink (solved with BLN control)
But i wanna use pie or nav bar control, and really irritating the soft keys light
Did you even try searching for one? I remember someone posted the exact same question and I responded to them giving them the files, so if you search for one you'll find it.
Just download the NSTools app from the Play Store and turn on backlight dimmer and set the delay to 0 ms.
For notifications turn on the backlight notifications too.
Here is an app that allows you to hold your back button to kill the currently open application.
If popularity is high enough, I will update it with things like whitelist etc.
If you use a Samsung device, the only problem is that you can't show the MultiWindow bar anymore. I will work on a fix for it. I only made this because xposed doesn't work on Samsung Lollipop yet so this is what I wanted until it is. Once it works, I prolly won't ever touch this app again.
Thanks everyone!
UPDATE:
- Performance improvement
useful, thanks for this!!!!
Great job! I've been missing this feature since I switched to Lollipop. Thanks!
hi,
It seems to be working on CM12 but a little too good
Apps get killed right away when i press "back"whatever time-out i set in the settings.
Droidphilev said:
hi,
It seems to be working on CM12 but a little too good
Apps get killed right away when i press "back"whatever time-out i set in the settings.
Click to expand...
Click to collapse
I dont know i dont have cm12. i know cm12 has a default native option to hold back to kill maybe that is enabled?
elesbb said:
I dont know i dont have cm12. i know cm12 has a default native option to hold back to kill maybe that is enabled?
Click to expand...
Click to collapse
Hello, CM12 with standard navbar (3 buttons) doesn't have that setting. It s only implmented in roms with navbars with extra settings like opening an app etc etc
Having Trouble
I'm having a similar problem where even a single tap on the back button is closing the app. I have a rooted Galaxy S4 running Android 4.4
Droidphilev said:
Hello, CM12 with standard navbar (3 buttons) doesn't have that setting. It s only implmented in roms with navbars with extra settings like opening an app etc etc
Click to expand...
Click to collapse
ndg1988 said:
I'm having a similar problem where even a single tap on the back button is closing the app. I have a rooted Galaxy S4 running Android 4.4
Click to expand...
Click to collapse
So this is happening when using the navbar and not the physical buttons?
It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.
elesbb said:
So this is happening when using the navbar and not the physical buttons?
It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.
Click to expand...
Click to collapse
hello again,
No, i dont use the navbar In cm12 (disabled) I use hardware buttons. If ndg1988 uses stock then he doesn't have a navbar so i guess he uses the hardware buttons too
Droidphilev said:
hello again,
No, i dont use the navbar In cm12 (disabled) I use hardware buttons. If ndg1988 uses stock then he doesn't have a navbar so i guess he uses the hardware buttons too
Click to expand...
Click to collapse
Hm, I truly don't know then. I really would need the device in hand to test with. I could try to do testing by sending you a file with loads of debug information in it. Would you mind that?
Good News
elesbb said:
So this is happening when using the navbar and not the physical buttons?
It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.
Click to expand...
Click to collapse
I was just an idiot that assumed the activation time was in units of seconds, not milliseconds. This may be what most people are having trouble with. It works well now, so thank you and keep up the good work.
ndg1988 said:
I was just an idiot that assumed the activation time was in units of seconds, not milliseconds. This may be what most people are having trouble with. It works well now, so thank you and keep up the good work.
Click to expand...
Click to collapse
Haha okay good. Nice one It does say "milliseconds"
elesbb said:
Hm, I truly don't know then. I really would need the device in hand to test with. I could try to do testing by sending you a file with loads of debug information in it. Would you mind that?
Click to expand...
Click to collapse
no, but it will take a while. i need to test multirom on my device and i have have to finish the translation of an app first.
Thanks mate
Awesome - best thing that can happen to a rooted stock rom.
btw its labled "Main Activity" in App Drawer, not "Hold Back To Kill"
Droidphilev said:
no, but it will take a while. i need to test multirom on my device and i have have to finish the translation of an app first.
Click to expand...
Click to collapse
What delay are you setting for it in the settings?
leechseed said:
Awesome - best thing that can happen to a rooted stock rom.
btw its labled "Main Activity" in App Drawer, not "Hold Back To Kill"
Click to expand...
Click to collapse
Yup. Realized that after releasing and didn't care too much about it. In the next update (if ever one would exist) i'll fix it.
elesbb said:
What delay are you setting for it in the settings?
Click to expand...
Click to collapse
I have tried 2, 3, 4 and 5 seconds
Did you put in 2 or 2000? (check post #11)
leechseed said:
Did you put in 2 or 2000? (check post #11)
Click to expand...
Click to collapse
DAMNED!!!!!!!!!!!!!!!!!!!!!!!!!!
Thank you, leechseed! Was making the same mistake.
OP please forget all my postings. Working very well!!!
leechseed said:
Did you put in 2 or 2000? (check post #11)
Click to expand...
Click to collapse
Droidphilev said:
I have tried 2, 3, 4 and 5 seconds
Click to expand...
Click to collapse
Droidphilev said:
DAMNED!!!!!!!!!!!!!!!!!!!!!!!!!!
Thank you, leechseed! Was making the same mistake.
OP please forget all my postings. Working very well!!!
Click to expand...
Click to collapse
That is why I asked. I have it set to milliseconds because I have mine set to a value of 200 milliseconds
Love seeing everyone helping everyone. Thanks guys!!!