Hey all,
I experienced something a few mintues ago. I installed a new rom, Blissdroid. I 'discovered' that the backlight of the touch input (under the screen) was reacting dynamicly to sunlight. It went off in full sun. I couldn't find a setting to let it lighten up all the time.
I went back to Virtuous Unity, 2.35. It seems like the same thing is happening. I don't know if it's just normal (and I never discovered it before) or is there a setting I have to change (because I can't find one)?
Someone who can help me?
Thanks!
Settings>Display>Brightness and turn off automatic brightness and set it to a value manually see if that works for you.
dstylazz said:
Settings>Display>Brightness and turn off automatic brightness and set it to a value manually see if that works for you.
Click to expand...
Click to collapse
I tried that, didn't work.
For you it is always lighten up, even if you are outsise/inside where it is really bright? When I go outside, full sun, those 4 touch inputs will stop shine. It seems there is something wrong with my DHD? Or Am I mistaken? Someone who can confirm it is always lighten up?
Nahsen said:
I tried that, didn't work.
For you it is always lighten up, even if you are outsise/inside where it is really bright? When I go outside, full sun, those 4 touch inputs will stop shine. It seems there is something wrong with my DHD? Or Am I mistaken? Someone who can confirm it is always lighten up?
Click to expand...
Click to collapse
When inside those buttons will be on. When you go outside they will turn off. They don't have a setting to turn that off
Sent from my Desire HD using XDA
trh1341 said:
When inside those buttons will be on. When you go outside they will turn off. They don't have a setting to turn that off
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Oh, so it is just a normal feature of DHD? Weird that I just discovered that yesterday
rcmix 4.0 and roms that use rctweaks have settings for this. alternatively you can set it to your exact preference if you edit framework-res according to this:
http://forum.xda-developers.com/showthread.php?t=1034743&highlight=systemui+apk
the link is manly aimed at tweaking your autobrightness, but it has info on butons too
Thank you. I only feared a problem, caused by changing ROM, as I never saw that before. I Thought those inputs were always lighten up, in every dark/bright situation.
depends on rom authors preference i suppose
if you are using sense 3.5 runnymede port, you can also flash tweaks as addon. some very nice features in there
Thank you all. I'm not great in flashing ROMs, certainly nog all those tweaks. I tried Virtuous Affinity and Blissdroid, but in both I heard a pop sound after playing music, sound, ringtone,... It seemed like I was not alone.
So I went back to Virtuous Unity 2.35, which doesn't give me any problem, except for a random bootloop from time to time (for example after playing Angry birds and once just after sending a message) what I can fix by replacing the battery. This happens 1 time in 3 months or so.
I just don't want to brick my phone, so I don't experiment much. Maybe one day, when I've got a new phone, I can use my DHD to experiment more.
Related
Hey ho fellas ,
I was working on adding power management + initialisation/de-initialisation sequence for rhodium´s lcd panel. Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
I would like that all of you users that are willing to help to test the kernel ( zImage+modules + latest commits included ) and give some feedback.
Test the power on/off sequence, leave it sleeping for ~30mins and unlock it,...then give me here some feedback on your lcd panel behaviour.
zImage + modules ( mediafire or attachment ):
http://www.mediafire.com/?ny18wpc3z8utxrf
Prerequisites:
- Backup your data.img if you have some valuable data on it ( anyway it should not affect it )
- Delete pm_sleep cmd from your startup.txt
What do you mean by this?
Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
Click to expand...
Click to collapse
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Lennyz1988 said:
What do you mean by this?
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Click to expand...
Click to collapse
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
lilchicano said:
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
Click to expand...
Click to collapse
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
uub11 said:
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Click to expand...
Click to collapse
Yeah, its a little bit hard to explain, but its like you said.
arrrghhh said:
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
Click to expand...
Click to collapse
Yeah, test it out and post your feedback
ReWind402 said:
Yeah, its a little bit hard to explain, but its like you said.
Yeah, test it out and post your feedback
Click to expand...
Click to collapse
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
I uploaded it here on xda, check the 1st post.
uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
Ha, responded a little late. I removed it...
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Lennyz1988 said:
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Click to expand...
Click to collapse
It would better that pm_sleep has the default value.
Will give this a try as I go about my day today. I don't OC and use pm_sleep=1 yet still get terrible battery life (b/c I'm a power-user, on e-mail constantly). Any positive change will be wonderful We'll see how it goes.
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Lennyz1988 said:
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Click to expand...
Click to collapse
1. Try deleting pm_sleep from your startup.txt ( then the default value will be used - i recommend that ) or put 1
2. never seen that on android
Anyway i am really sry for the inconvenience regarding launcer pro, kernel change should not affect those kind of settings :s
solevi said:
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Click to expand...
Click to collapse
Yeah its a common problem for now we are investigating this.
So i have a confirmation that the screen is really powered off?
Anyway guys try putting 1 into pm_sleep or deleting it from startup.txt (i recommend the 2nd choice ).
I ran into an interesting problem however I did not see the previous post...
Several time it went into standby (I assume) and the screen was pitch black meaning the backlight was not on. To get it out of standby, I woul click the end button like normal. after a couple of hours I pulled the phone out of my holdster, and it was abnormally hot. I do not have an overclock and my pm sleep is set to 1. I did not press the screen to see if it would respond so maybe that is what was being mentioned in the last post. None of the buttons would bring it back to life and the LED was amber and solid, where typically it would flash with this new zimage and modules. I will try to get it back to that state and see if I can click the screen even though it is dark. One thing that worries me is the battery though. Could this be damaging to it? Even when I did have it overclocked it never reached that temperature.
Anything else I can do to help troubleshoot?
EDIT: Sorry, forgot to mention I am on a Sprint RHOD400
I'm on the RHOD400 model, no OC, pm_sleep=1
Couldn't really get it to be stable, had to switch back to WinMo for the day (and trust me, that's desperation ). Once restarted in my pocket without any interaction on my part. I would press the end key to turn on screen, and had it auto reboot at that point as well. Also got a "sleep of death" twice and had to restart. While in your kernel I didn't have notification LEDs as well (not even for power events), vs the guy above that had blinking red.
I'm sure you'll get it eventually, keep up the hard work!
Hi!
Any news? Are we gonna wait for new kernel with committed code or it development is stalled?
hi, considering all the amazing work going on here by the devs, this is really minor.
using Clemsyn froyo 2.2 with Haret but maybe typical question.
when it wakes from sleep with power button the screen stays alight for about 2secs. sometimes it will black out before the white/multicoloured screen goes.
can i change to say 1 min this anywhere like the screen timeout. i always have it set to 10mins for the main display. its no prob to just press end or power to relock.
ps. did have some probs with sound but solved after changing radio from 1.64.08.21,
tried 1.71.09.01 and 1.65.21.18 but no good either. using 1.65.24.36 on kaiser now and seems to be ok.
what is strange about sound is how LOUD everything is compared to the barely audible winmo and whispering ringtones
gazzacbr said:
hi, considering all the amazing work going on here by the devs, this is really minor.
using Clemsyn froyo 2.2 with Haret but maybe typical question.
when it wakes from sleep with power button the screen stays alight for about 2secs. sometimes it will black out before the white/multicoloured screen goes.
can i change to say 1 min this anywhere like the screen timeout. i always have it set to 10mins for the main display. its no prob to just press end or power to relock.
ps. did have some probs with sound but solved after changing radio from 1.64.08.21,
tried 1.71.09.01 and 1.65.21.18 but no good either. using 1.65.24.36 on kaiser now and seems to be ok.
what is strange about sound is how LOUD everything is compared to the barely audible winmo and whispering ringtones
Click to expand...
Click to collapse
The timeout is related to the number of fake v-syncs the phone is doing. There is a parameter to adjust that. Run a search for it as I forget where/how to adjust it.
aceoyame said:
The timeout is related to the number of fake v-syncs the phone is doing. There is a parameter to adjust that. Run a search for it as I forget where/how to adjust it.
Click to expand...
Click to collapse
hmm, ok thanks. will have to do some reading then.
a google search came up with some stuff to check...
and a youtube video:
"Britney Spears : Lip-Sync + Boobs being Fake"
so maybe check that one out also sometime :-D
lmao I wouldn't use google for this search. I would search inside the kaiser forums only. I am pretty sure no other phones have a need for fake v-sync's except us. I remember asking L1qu1d to add the ability to be able to adjust it several weeks ago which he did. Before it was a static value that couldn't be changed.
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.
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?
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)