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?
Couple of things i've noticed....
First, does the notification LED have a mind completely of its own?? I get a voicemail...and the light flashes...then 2 minutes later get another voicemail and nothing.
Got an SMS, nothing showed...got another, nothing showed, just got one now and it starts flashing at me.
Secondly, when i've received an SMS, i've gone into messaging app...and the screen dimmed and came back again quickly, so i clicked on settings and it dimmed completely like an LCD with no backlight, exit settings and it comes back again, go back into settings and it goes etc etc. Lock screen, unlock and it works fine...bit weird.
The most annoying one is definitely the useless notication LED because...if i'm sat at my desk listening to music rather loud and i cant hear a notification because of the quiet speaker, or i'm away when a message arrives...i don't know i've got it because it isn't flashing.
Y U not use the search engine?
There are multiple threads about this 'problem' and the only useful advise is always: https://market.android.com/details?...29uc3VsdGluZy5hbmRyb2lkLmxpZ2h0Zmxvd2xpdGUiXQ..
Y U not read?
I'm not bothered about colours or customising the LED, i'm quite happy with the white flash, i'm also well aware of lightflow and there's reasons why i wont use it.
the problem is the sheer randomness of the standard notification LED randomly deciding to flash or not flash based on...absolutely nothing
bleets said:
Y U not read?
I'm not bothered about colours or customising the LED, i'm quite happy with the white flash, i'm also well aware of lightflow and there's reasons why i wont use it.
the problem is the sheer randomness of the standard notification LED randomly deciding to flash or not flash based on...absolutely nothing
Click to expand...
Click to collapse
I have had several phones with notification LED and this one is the only one that doesn't work correctly. Hopefullly the boneheads in the LED department over at Google can fix this. By the time they do, we will probably be able to choose from several ICS phones.
On a $700 phone, why do you need to download a 3rd party app to make one of the phones features work ?
randypurcz said:
I have had several phones with notification LED and this one is the only one that doesn't work correctly. Hopefullly the boneheads in the LED department over at Google can fix this. By the time they do, we will probably be able to choose from several ICS phones.
On a $700 phone, why do you need to download a 3rd party app to make one of the phones features work ?
Click to expand...
Click to collapse
This $700 phone has more problems than the $500 Galaxy S2 it seems. ICS is good, but hardware problems are starting to outweigh the benefits in my opinion. We need to keep downloading apps to manage these little things like the notification light, battery usage, volume problems (which the apps around still cause friction with ICS) etc.
This is my first Nexus and when I went into Vodaphone the other day the man at the store admired my phone. Then proceeded to tell me Nexus have always had little problems surrounding the hardware and software of the phones, the quality control isn't as good as the Galaxy S range. I'm starting to get that feeling too.
Well considering the galaxy s and s2 had their share of problems and the last two nexus are Samsung phones I find that trivial. I'm not having a lot of the problems people are having and my battery life is great, especially considering 4.65" amoled screen. Maybe apples don't fall far from the tree.
Sent from my Galaxy Nexus using xda premium
so has nobody at all had the weird dimming screen thing?
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?
So I seem to have a whole bunch of problems with my D851, and am curious if others have the same problems and know of fixes. Mine has 20g (stock Lollipop) installed, and is rooted.
Main problem: enabling Xprivacy makes this phone become significantly slower. The settings menu crawls with Xprivacy turned on. Anyone else experience this?
Auto brightness is *way* too dim to use. Surely, I must not be the only person experiencing this? I see a few people mention it in passing, but it doesn't seem to be an big deal. Are people not using auto brightness? Or do most folks not have this issue? All other devices I have with Lollipop allow a brightness range if set on auto. This one doesn't ? Can I get this feature somehow?
Even when I set the brightness manually, it keeps getting reset to 100% some half the times it wakes up from sleep. Anyone else experiencing this? Anyone know of a fix?
Also, the display off time never gets set. I set it to 30sec or 1min, and it always gets reset two 2 min.
The notification LED is virtually useless. It blinks once in like 20 seconds when I get an email (gmail app). I rely on this. Is there a fix to get it to blink every second or 2 seconds? Light manager didn't work.
What I don't understand is, since I experienced all these issue on pretty much a phone out of the box + rooted, I'm surprised they don't seem to be common problems.
Thanks in advance.
fivemill said:
So I seem to have a whole bunch of problems with my D851, and am curious if others have the same problems and know of fixes. Mine has 20g (stock Lollipop) installed, and is rooted.
Main problem: enabling Xprivacy makes this phone become significantly slower. The settings menu crawls with Xprivacy turned on. Anyone else experience this?
Auto brightness is *way* too dim to use. Surely, I must not be the only person experiencing this? I see a few people mention it in passing, but it doesn't seem to be an big deal. Are people not using auto brightness? Or do most folks not have this issue? All other devices I have with Lollipop allow a brightness range if set on auto. This one doesn't ? Can I get this feature somehow?
Even when I set the brightness manually, it keeps getting reset to 100% some half the times it wakes up from sleep. Anyone else experiencing this? Anyone know of a fix?
Also, the display off time never gets set. I set it to 30sec or 1min, and it always gets reset two 2 min.
The notification LED is virtually useless. It blinks once in like 20 seconds when I get an email (gmail app). I rely on this. Is there a fix to get it to blink every second or 2 seconds? Light manager didn't work.
What I don't understand is, since I experienced all these issue on pretty much a phone out of the box + rooted, I'm surprised they don't seem to be common problems.
Thanks in advance.
Click to expand...
Click to collapse
I think maybe you got a dud. Try flashing a rom and see if problems stop,if they don't then get another phone through warranty
Still_living714 said:
I think maybe you got a dud. Try flashing a rom and see if problems stop,if they don't then get another phone through warranty
Click to expand...
Click to collapse
Thanks, I think that was a part of it, but not all of it. I tried flashing stock on a different unit, and I found that the brightness issue was largely (but not fully) better, and the display settings not getting set issue went away. The Xprivacy and LED notification issues remain, and will occur on all units as far as I can tell. I haven't seen anything here that contradicts that info.
fivemill said:
Thanks, I think that was a part of it, but not all of it. I tried flashing stock on a different unit, and I found that the brightness issue was largely (but not fully) better, and the display settings not getting set issue went away. The Xprivacy and LED notification issues remain, and will occur on all units as far as I can tell. I haven't seen anything here that contradicts that info.
Click to expand...
Click to collapse
I have xprivacy and my phone is still very smooth plus my LED works just fine. I even changed the colors
Still_living714 said:
I have xprivacy and my phone is still very smooth plus my LED works just fine. I even changed the colors
Click to expand...
Click to collapse
Thanks a bunch for the info, this is good to know, and good to hear from another D851 user. The Xprivacy issue may be less easy to measure. The LED issue may be more objective. I have no trouble with changing LED colors. It's the blink rate that's at issue. Are you able to get it to blink say, twice per second, or even once per second when you get new email in your gmail app if you use that? Are you using any kind of an LED app?
Also, are you running Lollipop? Stock? Rooted? Thanks.
fivemill said:
Thanks a bunch for the info, this is good to know, and good to hear from another D851 user. The Xprivacy issue may be less easy to measure. The LED issue may be more objective. I have no trouble with changing LED colors. It's the blink rate that's at issue. Are you able to get it to blink say, twice per second, or even once per second when you get new email in your gmail app if you use that? Are you using any kind of an LED app?
Also, are you running Lollipop? Stock? Rooted? Thanks.
Click to expand...
Click to collapse
I'm always rooted lol I'm running fulmics 5.0 and in the settings it gives you the option of length and speed of the LED. I highly recommend that rom if you want to try out marshmallow.
Still_living714 said:
I'm always rooted lol I'm running fulmics 5.0 and in the settings it gives you the option of length and speed of the LED. I highly recommend that rom if you want to try out marshmallow.
Click to expand...
Click to collapse
Very good to know again, thanks for the recommendation! And the LED options are an additional reason. I'll try out fulmics soon.
I depend on the LED to see notifications when my phone is idle.
I've read that charging the phone forces the LED on and blue.
Assuming I will be rooting, and using xposed, is there any option available to disable this such that the LED functions normally at all times?
Notification light comes on as normal even when charging.
tofuboi01 said:
Notification light comes on as normal even when charging.
Click to expand...
Click to collapse
So what's the blue LED that is forced on when using dash charge that I've read about?
Trel said:
So what's the blue LED that is forced on when using dash charge that I've read about?
Click to expand...
Click to collapse
Basically, while charging the phone has a solid blue LED whoever if you get a notification the blue stops and is replaced by the blinking green or whatever colour for the other notification is
Trel said:
So what's the blue LED that is forced on when using dash charge that I've read about?
Click to expand...
Click to collapse
No idea about it being forced on while dash charging but that's just to indicate it's charging at dash speeds. Notification alerts will blink priority over charge indication.
What I think: When you charge at 'normal' speed the led is red, with dash it is blue (and this can't be changed). That's all... Like said as soon as you get a message it will change until you checked it.
superiscch said:
What I think: When you charge at 'normal' speed the led is red, with dash it is blue (and this can't be changed). That's all... Like said as soon as you get a message it will change until you checked it.
Click to expand...
Click to collapse
I think you're missing the point.
Suppose I have an notifications for specific email accounts that's blue and red.
I'm on the other side of the room (or in bed) and I glance at my phone to see if I have anything I need to address.
The LED is on and Blue/Red.
Do I have an email or is it charging?
Trel said:
I think you're missing the point.
Suppose I have an notifications for specific email accounts that's blue and red.
I'm on the other side of the room (or in bed) and I glance at my phone to see if I have anything I need to address.
The LED is on and Blue/Red.
Do I have an email or is it charging?
Click to expand...
Click to collapse
Steady blue is charging, blinking or different color is email...
superiscch said:
Steady blue is charging, blinking or different color is email...
Click to expand...
Click to collapse
*sigh*
Let me be specific.
I want it OFF when charging unless there's a notification.
Can I do that with some combination of
1. Stock software
2. Root
3. Xposed
Trel said:
*sigh*
Let me be specific.
I want it OFF when charging unless there's a notification.
Can I do that with some combination of
1. Stock software
2. Root
3. Xposed
Click to expand...
Click to collapse
No need to *sigh* when people try to help you. Just making clear how the situation is, i see it it too hard for you to see if a led is blinking or not. Good luck finding a solution.
I know I won't waste any more time here.
If you are willing to flash a nougat based rom ( as I have flashed AOKP N 7.1 on mine), you'll get the option to disable charging led under lights in display settings.
P.S. Not sure other N ROMs have got this option or in stock OOS or CB.
AJay27 said:
If you are willing to flash a nougat based rom ( as I have flashed AOKP N 7.1 on mine), you'll get the option to disable charging led under lights in display settings.
P.S. Not sure other N ROMs have got this option or in stock OOS or CB.
Click to expand...
Click to collapse
Any chance that's in any of the Marshmallow roms?
I do need to have access to Xposed for Gravitybox and other tools I use, which isn't yet available on Nougat.
Trel said:
Any chance that's in any of the Marshmallow roms?
I do need to have access to Xposed for Gravitybox and other tools I use, which isn't yet available on Nougat.
Click to expand...
Click to collapse
Sorry. I don't know. Maybe someone else could help.
Trel said:
Any chance that's in any of the Marshmallow roms?
I do need to have access to Xposed for Gravitybox and other tools I use, which isn't yet available on Nougat.
Click to expand...
Click to collapse
thats the most basic feature and available in all roms
Ajaykumar21066 said:
thats the most basic feature and available in all roms
Click to expand...
Click to collapse
That being the case, would you recommend any particular 6.0.1 rom (that does allow me to disable the charging LED) then?
I'm trying to get as close to stock Android or at the very least stock OxygenOS as humanly possible while still being able to disable the hardware buttons in favor of enabling the software ones.
Just to update, I found (still on my Nexus 5) an option in Gravitybox to disable charging LED. I don't know if that would work on the Oneplus 3, but it looks hopeful. I'm likely going to make the purchase soon then.
Trel said:
Just to update, I found (still on my Nexus 5) an option in Gravitybox to disable charging LED. I don't know if that would work on the Oneplus 3, but it looks hopeful. I'm likely going to make the purchase soon then.
Click to expand...
Click to collapse
I'm pretty sure any of the cm13 will have that option
Trel said:
Just to update, I found (still on my Nexus 5) an option in Gravitybox to disable charging LED. I don't know if that would work on the Oneplus 3, but it looks hopeful. I'm likely going to make the purchase soon then.
Click to expand...
Click to collapse
Worked on op3?