Hi, yesterday I upgraded from Paranoidandroid 3.68 to the new project Paranoidandroid 3.99 from http://forum.xda-developers.com/showthread.php?t=2397762
But I have an annoying problem - The touch button backlight keeps randomly turning on and switches off only when i click on screen. This only happens when I use it, it seems to be some kind of response or something. I have gone in settings>buttons>backlight and disabled it yet this does not disable the random turning on of it. Anyone know how can I completely disable it without installing custom kernels? Or what is causing it to randomly turn on all the time.
That's due to the touch key backlights. On 4.2.2 (PA 3.68) there was an option to disable them. On 4.3 it was removed by CM so a lot of other ROMs don't have the option either. What I've done on other 4.3 ROMs is to install the device settings apk and use that to turn them off. I haven't tried it on PA though.
I'm on mobile so can't give you a link... Search through my past posts from a couple weeks back. I posted the apk and instructions a couple of times, once in the PACman thread, once in Q&A. I also saw the steps quoted in Q&A by someone else too, you might come across that thread.
Oh wait you could probably even go to my 'most thanked posts'. It might be one of those. See how you go.
Sent from a galaxy far, far away
Hmm, thanks! But I did that, installed whole custom settings apk and launched the custom settings and turned the backlight off in there too, but it's exactly the same. Also this rom already has backlight button setting in options, so it didn't do anything new as far as i can tell.
The key backlight turns on randomly after like 5-30sec of pressing on screen. It's not like the usual backlight turning on keypress but it turns on after some time instead.
Edit: Backlight keeps turning on even if i have the default 3sec deley. the backlight would turn off after 3 sec and then back on after like 10sec until screen turns off or i press again on screen. Weird, maybe rom bug? I cant post on rom thread because i don't have enough posts
Edit 2: OK I have linked it to screen brightness. Every time screen brightness changes (from adaptive lightning, screen timeout and app/game setting) the key backlight turns on. I have no idea how to force the key backlight to stay off though, so thats why im here
Oh wow. Good job narrowing it down to that, I imagine it wasn't easy to figure out what was causing it. Have you read the rom thread for the last 15 pages or so? See if someone else is having the same issue. Also read the OP and following posts, for known bugs /FAQ. You should have read OP before flashing anyway but read it again
If you don't find anything else, try to get a few extra posts and then post in the thread. You seem to know what you're doing, so try helping out a few other people on Q&A maybe.
Sent from a galaxy far, far away
The latest(todays) build fixed the issue. Thanks for help!
Related
Greeting everyone.
I recently got an Android and I also recently decided to root and stick a custom ROM on it. Everything went fine and dandy with that and I'm currently on Cryanogen 9 Alpha ROM (it's spectacular to say the least).
On the default ROM you could choose to turn off the key lights (I'm talking about the touch keys on both sides of "the master button"). However, neither does Cryanogen 7 or 9 offer me this option and because I'm so used to it, lights seem weird and unnecessary.
So, after searching the interwebz for a while, I couldn't find anything useful and hence my post.
Thanks in advance for any help given.
Furthermore, fantastic video!
Bump! (Too few characters apparently).
tried this?
https://market.android.com/details?id=neldar.bln.control.free&hl=en
TheFaixy said:
tried this?
https://market.android.com/details?id=neldar.bln.control.free&hl=en
Click to expand...
Click to collapse
This requires .bln (BackLightNotifiation) mod which isn't featured in my current ROM (Cyanogen 9).
Thanks for the input anyhow.
I would like to know this too. The keys are allways on in CM9 unfortunately
Verstuurd van mijn Galaxy S II met Tapatalk
It turns out that you can turn them off in CM7 but unfortunately I'm yet to find a fix for CM9.
you can try to modify the following script in the middle of this post to make it work in cm9
forum.xda-developers.com/showpost.php?p=17058177&postcount=1
JLowe said:
you can try to modify the following script in the middle of this post to make it work in cm9
forum.xda-developers.com/showpost.php?p=17058177&postcount=1
Click to expand...
Click to collapse
Thanks a bunch for the link.
I'll definitely give it a try when I have a bit of spare time.
EDIT: This script also requires BLN (which I talked about above) and after searching long and hard, I have found out that there is no ICS kernel with BLN support (while some others knew this, I certainly didn't).
After looking around further it seems that I/we won't get the feature for a while since BLN seems to be the only way apart from integration within the ROM (like it is within TouchWiz or CM7) that you can turn off your soft keys.
Latest build of CM9 has removed backlight!
'Tis a glorious day.
JLowe said:
you can try to modify the following script in the middle of this post to make it work in cm9
forum.xda-developers.com/showpost.php?p=17058177&postcount=1
Click to expand...
Click to collapse
Wow, I've been looking for a way to disable the keys and while the script won't work for me messing with the settings did the job, that was my only issue so far. Cheers for the share. I'm using MIUI with siyah if anyone cares in order to make it work.
PS: games and movies look much better with no white lights :O
EDIT: Well, guess I was beat by the software had a notification during the night, and now the lights only stay off until the first time the screen gets turned off, after that they go back to their normal behaviour unless I reboot :|. On the look again for another way.
EDIT 2: Ok, I'm not giving up, for now I found yet another way for anyone interested (you need a BLN kernel however).
I installed BLN Control Pro, disabled everything and put BLN blinking: On and Led OFF time 3 minutes.
Now what I do is enter Test mode, turn the screen off and on, and now, the lights will be off for as long as I keep the program running. The only problem with this, is that BLN stops the phone from going into Deep Sleep, so I just need to remember to turn the test mode off and to disable BLN whenever I don't need the buttons off.
It's not a pretty solution but for now it's the best I could come up.
no setting for that
Hi everyone!
Short question. I've got a galaxy s3, so far a great phone!
Vibrate and haptic feedback works when i press the back or menu button. But i cannot seem to get it to work when i touch the screen. i.e. touching an icon on the screen does not create the haptic feedback that i'm used to.
Is this a normal thing or an error/bug?
Uhm you can turn on this function
Yeah..you mean the haptic option under settings - sound?
It enables the haptic feedback for the back and menu button. But not the touches on the screen itself.
that function will be implemented into roms and anyways its not needed it just sucks battery
So, short answer is that it's not a default option on the galaxy?
It's been a long time since i've had a stock rom so i don't know any better
SuppleX said:
So, short answer is that it's not a default option on the galaxy?
It's been a long time since i've had a stock rom so i don't know any better
Click to expand...
Click to collapse
not on my original sgs wasnt a feature
Same Issue(Resolved)
Well i had the same issue and the solution was pretty simple for me. Turn off power saving mode.
same problem but nothing seems to work
ok I have the same problem; haptic feedback not working and neither is vibrating on notifications, some vibrations working. The problem showed up like 1 week ago, without having installed anything special that day (can't remember if I installed anything at all that day).
My device (sgs3 I9300) was when the problem appeared on Paranoid android 3+, now it's on some cyanogenmod 10.1 nightly build.
what i've tried: going through all the settings, sound manager, turning off all vibrations the rebooting then turning them all on then rebooting again, changing rom (incl. factory reset of course), reading all kinds of threads about such problems.
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day.
The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure.
I have tried everything - loaded stock firmware back and ran casual again, flashed Beans 14 and set my entire device back from a fresh install.
Again, tonight, screen froze twice and I had to to a battery pull
Does anyone have any idea what's going on? I never has this issue before and it's driving me nuts - having flashbacks of blackberry battery pulls
Clean or dirty flash? This happened to me the other day, froze out of nowhere for no reason
jcastagnino said:
I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day.
The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure.
I have tried everything - loaded stock firmware back and ran casual again, flashed Beans 14 and set my entire device back from a fresh install.
Again, tonight, screen froze twice and I had to to a battery pull
Does anyone have any idea what's going on? I never has this issue before and it's driving me nuts - having flashbacks of blackberry battery pulls
Click to expand...
Click to collapse
Do you have ripple effect, ink color or any of the TW features enabled while using AOSP Lockscreen?
Because if you do, and your phone times out, your phone will freeze and you will need to do a battery pull.
If you use AOSP lockscreen, you have to disable any of the TW lockscreen features.
jcastagnino said:
I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day. The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure...
Click to expand...
Click to collapse
You will get more input if you post in the Beans thread
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
trentb12 said:
Do you have ripple effect, ink color or any of the TW features enabled while using AOSP Lockscreen?
Because if you do, and your phone times out, your phone will freeze and you will need to do a battery pull.
If you use AOSP lockscreen, you have to disable any of the TW lockscreen features.
Click to expand...
Click to collapse
Wow, I didnt know the AOSP lockscreen would casue those issues....so turned it all off, and so far so good!! Guess I never had those options selected before.
I have not had a single lockup/freeze yet. I wonder why Beans does not gray those options out when the AOSP lockscreen is selected.
I have searched everywhere for a solution to this problem and trust me, the search button has never had this many presses before
I have a HTC HD2 and 'almost' everything works, but there are a few issues I have.
I'm not a noob in ANY sense and I always try and find a solution to my problems before posting about them, that is IF I can't solve the problems myself
First off, this is my current setup for the HD2:
HD2: International 512mb HTC HD2
Radio: 2.15.50.14
HSPL2.08
MAGLDR V1.13
Recovery: MAGLDR CWM Recovery v3.0.2.4
Current ROM: NexusHD2 JellyBean CM10.1.3 V2.7 by Tytung
Previous ROM: PACman HD2 v1.2a by Xylograph
Kernel: tytung_jellybean_r2
Ok, the problems. What are they?
First off, the phone will NEVER, and I really mean NEVER, enter Deep Sleep. Deep Sleep is always amongst the unused CPU states. I have tried everything to get it to go to Deep Sleep to no avail. I tried another ROM to see if the ROM/kernel was at fault, but it isn't. They all have that problem. There are no apps that are causing wake-locks and even using an app that forces Deep Sleep will not work. The lowest the CPU will go is 96Mhz and never below it. I have the Max CPU speed set to 1190Mhz and the lowest set at 96Mhz. I also can never confirm a time when Deep Sleep did work, because it never did
Second problem, the physical buttons on the device act very erratically. I don't have the well-known power button issue, but I have something similar. The power button doesn't work on a long-press. If you long-press the power button it should give you the power menu, right? In my case, that never happens. What will happen is the display will turn off, as if I simply pressed and released it, like when you lock the phone. No matter how long you hold it in, the power menu will never appear.
Other buttons also act odd. The volume down button does work, but it also triggers the multitasking window to appear, every time I press it. This behaviour is not restricted to being in Android. Scrolling in CWM with the volume rocker, because that is the only way you can navigate this version of CWM, also does this. The log window will disappear and re-appear constantly, but sometimes it doesn't do this. This problem is only with the volume down button. The volume up button works just like it should. Other buttons do give problems, but they are not ever-persistent like the ones I mentioned above. The others just have constantly changing behaviour. They will perform different tasks at random when pressed, like open the dialer, or go home, or open the multitasking window as well, or even go back sometimes.
Now, I don't know what happened to Tytung on XDA, nor do I want to find out because it isn't important to me, but I'm not trying to advertise his work. I'm just trying every ROM I can find.
The phone does have water damage, but that was many years ago. No repairs were done to it, but it still works just like it should. The only problems are the ones I mentioned above. I do think that the water damage did do something to the buttons of the phone, but is it even possible that Deep Sleep can be affected by this? Isn't Deep Sleep something that is software-based?
I really would like to know what the is going on here
Any help would be greatly appreciated
I hope I provided enough information about this problem
D395267 said:
I have searched everywhere for a solution to this problem and trust me, the search button has never had this many presses before
I have a HTC HD2 and 'almost' everything works, but there are a few issues I have.
I'm not a noob in ANY sense and I always try and find a solution to my problems before posting about them, that is IF I can't solve the problems myself
First off, this is my current setup for the HD2:
HD2: International 512mb HTC HD2
Radio: 2.15.50.14
HSPL2.08
MAGLDR V1.13
Recovery: MAGLDR CWM Recovery v3.0.2.4
Current ROM: NexusHD2 JellyBean CM10.1.3 V2.7 by Tytung
Previous ROM: PACman HD2 v1.2a by Xylograph
Kernel: tytung_jellybean_r2
Ok, the problems. What are they?
First off, the phone will NEVER, and I really mean NEVER, enter Deep Sleep. Deep Sleep is always amongst the unused CPU states. I have tried everything to get it to go to Deep Sleep to no avail. I tried another ROM to see if the ROM/kernel was at fault, but it isn't. They all have that problem. There are no apps that are causing wake-locks and even using an app that forces Deep Sleep will not work. The lowest the CPU will go is 96Mhz and never below it. I have the Max CPU speed set to 1190Mhz and the lowest set at 96Mhz. I also can never confirm a time when Deep Sleep did work, because it never did
Second problem, the physical buttons on the device act very erratically. I don't have the well-known power button issue, but I have something similar. The power button doesn't work on a long-press. If you long-press the power button it should give you the power menu, right? In my case, that never happens. What will happen is the display will turn off, as if I simply pressed and released it, like when you lock the phone. No matter how long you hold it in, the power menu will never appear.
Other buttons also act odd. The volume down button does work, but it also triggers the multitasking window to appear, every time I press it. This behaviour is not restricted to being in Android. Scrolling in CWM with the volume rocker, because that is the only way you can navigate this version of CWM, also does this. The log window will disappear and re-appear constantly, but sometimes it doesn't do this. This problem is only with the volume down button. The volume up button works just like it should. Other buttons do give problems, but they are not ever-persistent like the ones I mentioned above. The others just have constantly changing behaviour. They will perform different tasks at random when pressed, like open the dialer, or go home, or open the multitasking window as well, or even go back sometimes.
Now, I don't know what happened to Tytung on XDA, nor do I want to find out because it isn't important to me, but I'm not trying to advertise his work. I'm just trying every ROM I can find.
The phone does have water damage, but that was many years ago. No repairs were done to it, but it still works just like it should. The only problems are the ones I mentioned above. I do think that the water damage did do something to the buttons of the phone, but is it even possible that Deep Sleep can be affected by this? Isn't Deep Sleep something that is software-based?
I really would like to know what the is going on here
Any help would be greatly appreciated
I hope I provided enough information about this problem
Click to expand...
Click to collapse
I have a similar set up with the opposite problem: won't come out of deep sleep! Hate to hijack your topic but if anyone knows what could be causing this...?