Yesterday after installing a zip from UOTKitchen i noticed that my softkey lights would not turn off! Normally they dim after about 15 seconds but they would not turn off at all. Not only am i concerned about the battery life but it is also quite annoying. One more thing is that now the keyboard lights will not turn on! Any help appreciated!
What is uotkitchen?
Sent from my T-Mobile G2 using XDA Premium App
Nevermind. Thank u google
Sent from my T-Mobile G2 using XDA Premium App
This happened to me as well. I'd be very interested in a solution.
So far I've tried restoring old backups w/ data wipe, reinstalling CM from scratch w/ data wipe, and formatting the system folder from clockwork.
I've also tried changing the CM backlight display options as well as the automatic brightness and none of it is working =/
I tried changing ROMs completely (Pure Stock, GingerSense, etc) and it fixed the problem. But when I switch back to a CM ROM - regardless of which version - the problem returns. I can't explain why this is happening now since it worked before and why other ROMs fix the problem.
I've tried switching ROMs around noticed that the other ROMs are also exhibiting backlight issues although not as blatant as CM.
The sensor appears to work properly since the backlight is fine as long as the LCD display is on. So since this now appears to an issue with my /SYS files, is there a way for me to get a new version of them or something?
Any help would be great.
Sent from my HTC Vision using XDA App
Checked out the files via ADB. When the LCD display is on, I can adjust the button backlights easily.
Once the screen goes off, I am no longer able to adjust the lights. The 'brightness' file is set to 0 (as it should be) but the light is very clearly on. Editing it to other values does not change the intensity of the light.
Since this seems to disprove that there is something wrong with the /sys files, I can only assume this is some weird hardware issue now. I guess it's back to T-Mo...
Related
Update on Issue #1: 2010.11.29
This issue appears to affect all unlocked Froyo devices on the Rogers network. It MAY affect all Froyo devices, regardless of network lock status, but we have been unable to confirm this (yet) on the only Froyo device locked to Rogers - The Acer Liquid e.
There are currently 4 threads (that I am aware of) scattered around XDA. As this problem affects multiple devices I will start posting updates in the General Discussion/Q&A thread, and will stop posting updates here. If you are looking for more information, please refer to:
Main Thread: http://forum.xda-developers.com/showthread.php?t=845152
Other Device Specific Threads:
N1: http://forum.xda-developers.com/showthread.php?t=849969
DZ: http://forum.xda-developers.com/showthread.php?t=848793
SGS: http://forum.xda-developers.com/showthread.php?t=850784Wanted to see if this is isolated to my phone or if others have these issues.
_________________________________________________________________________________________________________________
Phone is Rooted, S-Off, Paul Obriens Custom ROM with HTC Sense on Rogers Network.
1. Cannot get a location lock unless I use GPS, it will not give me a location in Maps at all unless I turn on GPS.
2. Display is set to Automatic Brightness but the screen stays the same no matter if i'm in direct sunlight or in a pitch black room
3. Have SMS Timestamp fix but am still getting messages which sometimes show hours behind or hours ahead
Bump
Sent from my HTC Vision using XDA App
For the GPS issue, you should post this up in the thread on Paul's ROM, to see if others have the problem. I presume your GPS worked fine on the stock ROM ?
Others have reported issues with the automatic brightness setting. I suspect it doesn't work at all, even on the stock ROM.
Also have issue with automatic brightness adjusting not working.
ayewhy said:
Also have issue with automatic brightness adjusting not working.
Click to expand...
Click to collapse
I don't think I've seen anyone saying that it *does* work for them in the stock ROM. Anyone ?
steviewevie said:
For the GPS issue, you should post this up in the thread on Paul's ROM, to see if others have the problem. I presume your GPS worked fine on the stock ROM ?
Others have reported issues with the automatic brightness setting. I suspect it doesn't work at all, even on the stock ROM.
Click to expand...
Click to collapse
Will do, hopefully it can get fixed. The GPS works fine, locks fast. It's when I don't have GPS enabled that it won't give a location using the wireless network now.
Wonder if making a single thread regarding auto brightness would be good. I've emailed HTC and they gave the typical "pull battery, factory reset" garbage. And after "exhausting" those "fixes" they simply say to call and RMA the device...ugh
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away. It changes back after going to sleep and unlocking. Also, it won't go below approx. 50%.
Edit: I checked it again and it does change back, it just takes a few seconds.
Sent from my HTC Vision using XDA App
andijvie42 said:
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away. It changes back after going to sleep and unlocking. Also, it won't go below approx. 50%.
Edit: I checked it again and it does change back, it just takes a few seconds.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Can you take a video possibly of this, what are the details of your phone? Rooted? S-Off?
The screen will "dim" when the backlight times out but it never actively dims because of the sensor on my phone.
Stealth1985 said:
Can you take a video possibly of this, what are the details of your phone? Rooted? S-Off?
The screen will "dim" when the backlight times out but it never actively dims because of the sensor on my phone.
Click to expand...
Click to collapse
My phone is completely stock. The dimming might be too little to be noticed, have you tried to shine a light directly in the light sensor, while being in a fairly dark room, so that you can observe the maximum change of brightness?
You could also download one of the sensor apps out there and see if the sensor works. Mine says light level 0 in a darker room, and max when i shine a light in the sensor.
I doubt the sensor is very useful though, as the brightness only goes from approx. 50 to 80%...(going from zero light to lightest) might be better if these values could be set.
About the video, the only camera I have right now is the DZ, so I'll see what I can do.
Sent from my HTC Vision using XDA App
andijvie42 said:
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away.
Click to expand...
Click to collapse
That's interesting, thanks, I'll give that a try.
Sounds like the auto-brightness and the keyboard/cap buttons backlight (both of which use the light sensor) might both suffer from the same thing - i.e. very poor programming/implementation.
I have issues 1 and 2 (but not 3).
I would like to add that auto-brightness seemed to work fine when I (briefly) used CyanogenMod RC2, though I have no other Android devices to compare with.
I dumped the stock Sense ROM pretty quickly so this might have worked fine on the original ROM.
This definitely sucks, what ROM do you have that the location doesn't work too?
Pretty disappointed that I'm having these issues and HTC's response is send it in. I am not paying to re-unlock another phone because they can't make something that fully works.
Sent from my HTC Vision using XDA App
I have some bad news for you about point 1. It looks like a number of people on various unlocked android devices (N1, Desire, SGS i9000m) are experiencing the network location problem.
http://forum.xda-developers.com/showthread.php?t=845152
There is w (crappy, but still functional) work around, but...
For most of us it started sometime around Nov 14th.
It has some pretty unhappy implications for those of us who prefer android and want a top-end phone.
Good luck.
Damn Rogers seems to have screwed things up.
Sent from my HTC Vision using XDA App
Yeah. Maybe.
It seems to be an interaction between Rogers and unlocked android phones. We don't know whether it is all unlocked android phones, though, or even if it is specific models (i.e. would an unlocked Rogers Captivate have the same problem), or a specific OS (i.e. we don't know yet if the problem happens on eclair - while not directly useful to the DZ owners, it would at least help to pinpoint the problem and might help to get Google to step-up).
There are just too many unknowns, and how do you speak with someone with sufficient knowledge to speak intelligently? Rogers tech support hasn't been much help, and Google and Rogers seem to want to bounce the problem between each other.
Auto-brightness: Using My sensors free market app, checked the light sensor. All the sensors but the light gives live info. Looks like it doesnt work at all, like not switched on.
Uk htc z, stock rom.
-- sent from htc z using xda app
tbalden said:
Auto-brightness: Using My sensors free market app, checked the light sensor. All the sensors but the light gives live info. Looks like it doesnt work at all, like not switched on.
Click to expand...
Click to collapse
Could be that the app doesn't work with the DZ light sensor properly though ? I know my light sensor does something, because the keyboard/cap keys backlight turns on and off kind of randomly depending on light levels (and if you block the sensor then the lights come on).
Thats true. It happens here too. But still might be related...
-- sent from htc z using xda app
Ok.with very bright flash light around it gives data with the my sensors app. Then its the levels its moving light level between,as mentioned in this thread before.
-- sent from htc z using xda app
tbalden said:
Ok.with very bright flash light around it gives data with the my sensors app. Then its the levels its moving light level between,as mentioned in this thread before.
Click to expand...
Click to collapse
Cool, kinda sounds like it works, just very very badly.
Hello,
I recently bought an Incredible for my girlfriend on craigslist. It was only 2 months old (in great condition to boot). Either way after flashing CM7.0 I noticed that the automatic backlight setting did not work. I just set it to around 25% and figured I would figure it out later. After 7.0.2.1 came out I flashed that and no change. I then decided to figure it out. It seems that after waking the sensor doesn't work unless really flooded with direct bright light (such as the flash light from my incredible). After that it works mostly as intended.
Here is how I tested it. I lock the phone when in the custom light levels screen. When unlocking the Sensor (filtered / raw) is at 10/10 and will not change no matter what I do until I hit it directly with a bright light. I believe that it will also change eventually letting it just sit. Most of my tests involved using bright light sources. After that the sensor works just fine and changes almost instantly when I cover it with my hand and then move it into regular room light. Is this a known issue? I checked the bug tracker briefly but did not see anything. I have had two others test. One had fine light sensor response the other had the same issue as me.
Anyone have any idea?
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
k_nivesout said:
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It does work but the sensor doesn't respond in a timely fashion.
Have you tried changing the sample interval?
Sent from my ADR6300 using XDA App
What settings are you using? I.E. do you have filtering enabled? What is your window length? Sample interval? Etc.
I've never seen anyone discuss this as a CM7 bug. Based on the way you are describing it, it sounds like you might just need to tweak your settings.
For example, if your window length is very long and sample interval slow, that might be why your readings are taking so long to update. As for why the reading changes as soon as you hit it with a bright light, you could be tripping the reset threshold.
Just in case you haven't checked it out already:
Numerical explanation of the CM7 automatic backlight settings
I will check when she gets off work. All I did was flash cm7. I didn't mess with light sensor settings.
Ok... I have checked it... Not good. Sample intervals were set to 1s. Even still they were not enabled. Messing with the settings didn't yield any results either. It was still sluggish until hitting it with bright light...
I would search, there are multiple threads around where people have posted their settings, I would try those then tweak it to your liking. Also check out byrong's thread, the man knows his stuff.
Sent from my ADR6300 using XDA App
The automatic brightness sucks on stock as well. Just turn it off. You can't see the screen in bright sunlight no matter what the setting is, and you can see it just fine at 64/255 inside. All the automatic brightness does is give you a headache.
After upgrading to gingerbread, EI22, I noticed that my hardware buttons don't dim any more. Under display settings, I do have keyboard dimming set, but it doesn't seem to help. Normally it shouldn't be a big deal, but I use my phone for a bedside clock, and they are kinda bright
So far tried with both Legenday and ICS ROMs, with 3-4 different themes, they all seem to do that
Any ideas?
Thank you!
Auto Brightness perhaps? Keep it on and I've heard it may dim the capacitive buttons.
Both controlled by the same driver.
Sent from my Epic 4G
Just tried different combinations of Automatic Brightness and Power Saving Mode, they both don't seem to have any effect
i wish we could disable those buttons at will but afaik it would require a kernel to completely disable them. or at least thats how kernels on the moment worked, they came with LEDon or noLED versions
Sent from my SPH-D700 using xda premium
So that's a new feature of 2.3 kernels?
It was fine for me on stock rooted EI22. If I flash any other ROM or kernel, they stay on in night clocks. It was like this for CM7 1024 build as well. I thought I read in the CM7 thread that it will be fixed in a new build, but don't quote me on that. ;P
oh, sweet! Thank you guys!
I have a similar problem with ACS ICS ei22. The lights simply never turn off when the screen is on even though I have the screen set for 30 seconds and the light set to 6 seconds.
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
You have to use auto brightness.
cm9 illumination
If you mean display auto brightness ok but when I'm outside I can't see the screen...guess ibhave to toggle back and forth. I had switched back to cm7. In your opinion is 9 worth changing to. It seems like in 7 everything is working pretty well.
Thank you for the reply
pmpic said:
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
Click to expand...
Click to collapse
Toggling auto brightness on and off solves it. Just tinker with it..
Sent from my Incredible 2 using xda premium
cm9 illumination
Thank you....I appreciate it
Menu keys...
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
atomwes said:
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
Click to expand...
Click to collapse
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
pmpic said:
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
Click to expand...
Click to collapse
Unfortunately, I can't answer that question for you, as my phone doesn't like our ICS builds. Until we get a leaked official kernel and some source, I'm SOL.
RegnierD said:
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Click to expand...
Click to collapse
Where exactly are these settings? Running CM7 with the same problem as the OP and can't find it anywhere. Edit: found the settings and putting them all at 255 didn't do anything. Any other ideas?
Hello, my device was working great for a month, now suddenly, screen flicker, it flickers quickly every now and then.
Is this hardware related or can it be fixed by software?
It appeared after I installed a new Rom, but now it appears in different roms.
It also started appearing after I played with root dim app, setting screen brightness to lower than usual (and not only laying a filter). Not sure if that might have anything to do with it.
In it is not present when brightness is at 100 %. But anything lower it is there.
Read somewhere about someone opening the device and clean the connector apparently solving his flicker. Hoping I won't have to do that though.
Thanks in advance!
Sent from my Nexus 7 using xda app-developers app