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?
Related
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.
Hey kiddos.
WisTilt2 wanted to get some more testers for this kernel, so please download and put it thru the ringer!
This is RHOD ONLY! Please, don't ask if any other devices will work as currently it probably will not! Use at your own risk!
UPDATE 5/14/11 Temp test, SOD prevention!
So the newest autobuild has been plagued with an odd SOD condition. WisTilt2 thinks he traced the issue, and he wants people to run this kernel to see if it's SOD-free (compared to the newest autobuild).
WisTilt2 said:
Current git tree, my pm/fb patch with the proc_comm test. Need to see if anyone gets SOD's. Should have very fast sleep and wakes still, leds are like autobuild also.
Click to expand...
Click to collapse
Let me know guys, thanks!
(In this case, I will leave the old kernel - but do please test this new kernel against the autobuild, see if the SOD's disappear...)
Archive:
UPDATE 4/15/11 SCBS integration
This is the new battery meter code that jonpry has been working hard on. To get the full benefits, you'll need an APK and a new rootfs.img. Please see jonpry's thread on PPCG for more information.
So download this kernel, grab the apk and rootfs from jonpry's thread (don't grab the kernel in his thread!) and follow his instructions if you want to give SCBS a spin. I've already noticed a difference, and I haven't generated a model yet. Rule of thumb with generating the model/algo is the more data the better - so go thru a few charge cycles, some heavy use, some sleep - the more usage the better the algo! Enjoy!
Just to be clear - this new kernel only has the updated SCBS code. Nothing else has been changed since the previous 4/4 test kernel.
UPDATE 4/4/11 Minor fixes...
Just an update to the previous kernel, stylus should be fixed (meaning it will boot into landscape again, fix needs to happen in userland) along with the button lights (when keyboard is open, button lights do not light now). Nothing major!
UPDATE 4/2/11 *Hopefully* failed panel wakes are gone!
WisTilt2 said he found and irq that was set wrong... and it was related to the touchscreen - hence the reason touching the screen wakes it! So this kernel seems to wake very nicely for me - how does it for you?
UPDATE 3/31/11
WisTilt2 said:
This fixes the button lights so they go out when you open kbd and they turn on when you close kbd just like winmo. Also fixed the portrait/landscape unlock screen so at boot it should be in portrait so you don't have to do the back arrow trick to switch it.
Click to expand...
Click to collapse
Update: On the button lights, when the keyboard is open - the button lights will act odd... seems the kernel is torn, it flips them on and then quickly back off .
UPDATE 3/30/11 Button lights, PM Rework, kbd flicker/repeat key, and failed wake fixes!!
WisTilt2 has been trying to clean up his code so he can commit - this is working towards that goal. This new kernel has fixes for the kbd flicker/repeat ("stuck") key bug, the failed panel wakes have also disappeared for me - the panel doesn't always wake instantly, but I've never had to touch the screen to get it to wake - it's ALWAYS come up! Let me know, YMMV as always! Oh and yes, the 4-button light LEDs should now work perfectly as well .
Update - ok, might've jumped the gun on the repeat letter thing - but it does seem better... Just not perfect yet .
RHOD100/AUO users - really need to know if this new kernel breaks your phones! I also would like to know if the SoD issue is actually squashed. I haven't had an SoD in forever, so to those who have recently, let me know!
Perhaps also good to note, is the sleep LED is changed in this one. Initially it will blink green to show that processes are going down and it's trying to sleep (a wakelock of some sort is present in other words). Solid green is full, deep sleep. So you should see blinking green when charging, with GPS enabled etc. You won't get a solid green LED until it's completely sleeping, as usual.
In addition, WisTilt2 has changed the boot screen. Hopefully it'll boot faster, but you'll see a lot less flying text - don't panic! It's normal .
Enjoy! Please feel free to report how this kernel works, so we can get the changes committed!
**Notice**
These kernels are meant for testing purposes - there is no public GIT repo that this kernel code resides on, however the majority of the changes get pushed to the master GIT repo for XDAndroid. The ones that don't didn't work or were simply in place for testing - again the changes that are being tested here are eventually destined for autobuild. Please contact me if you have any technical questions related to this kernel, I will do my best to explain the changes - if you want specifics, I can put you in contact with WisTilt2, the man in charge of pumping out these test kernels. Feedback is not only welcomed but encouraged, please reply to this thread with it!
Downloading and testing now...
UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?
Yep, testing now.
Incidentally, with both this and 1245 I cannot seem to boot my neopeek system. They fail to see the root partition at /dev/mmcblk0p2 and either hang or reset.
The 1242 kernel still works fine . Weird
Anyway, I will test this out with my XDAndroid setup.
Cheers!
Sorry to be an echo of the others... before I test it, is it built from the 1245 kernel?
1245 seems to be working sweet for me so far....
This should have all the newest commits + WisTilt2's modifications. He said all but bzo's latest commits... I guess git died on him. I'll upload a new one if he builds another.
First impressions on Rhod400:
Speakerphone volume is still fairly low for my taste...when the volume setting is at 1/3 it is barely audible...at full I have to hold it fairly close to hear all words clearly...
Also there is a lot of background "noise" when the external speaker is on...sounds like white noise or static...
Otherwise everything is running smooth...
New Test Kernel (WisTilt2) - 2nd edition - Rhodiums Only
Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodiums to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.sleep_mode=1 patch for even better battery life when you're overclocking. So set pm.sleep_mode=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Please also mention your rhodium model. They may not all behave the same. Thanks.
WARNING: This kernel is for RHODIUMS only. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.
Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.
Rhodium Only - Kernel & Stripped Modules File(1.94MB version):
wistilt2-kernel-pack-stripped.zip
Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):
wistilt2-kernel-pack.zip
@pdawg17 the static is expected atm, but how loud is it compared to the actual call. same volume or pretty quiet?
People that post here, make sure to specify which model you have, eg. 100, 300. If you don't know you likely shouldn't be testing experimental kernels.
F22 said:
Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodium owners to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.mode_sleep=1 patch for even better battery life when you're overclocking. So set pm.mode_sleep=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Thanks.
WARNING: This kernel is for RHODIUMS ONLY. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.
Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.
Rhodium Only - Kernel & Stripped Modules File(1.94MB version):
wistilt2-kernel-pack-stripped.zip
Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):
wistilt2-kernel-pack.zip
Click to expand...
Click to collapse
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news
I have RHOD100_de with pm.sleep=1
Well i can say that:
1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...
2) WiFI shows error
3) The in-call/speakerphone volume seems OK
4) Auto backlight function seems to be OK, since it was OK in other kernels.
5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.
If You say me on what exactly to focus i'll give more info
So far testing the Rhod kernel:
1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...
2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...
3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...
4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...
5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...
I'll keep it running today to see how battery life is...
Otherwise it is great! I'll keep testing!
UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...
UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!
Rhod400 (Sprint TP2)
Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static
pdawg17 said:
Downloading and testing now...
UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?
Click to expand...
Click to collapse
This isn't built off of 1245. I believe it's built off of 1238 with WisTilt2's modifications on top as well as some of the newer patches like 1239 and 1241 added into the mix. I don't believe commits 1243-1245 made it into this test kernel.
Rhodium 100 Panel Issue
solevi said:
I have RHOD100_de with pm.sleep=1
Well i can say that:
1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...
Click to expand...
Click to collapse
Most rhodiums have an EID panel. Some rhodium 100's however have an AUO panel instead. The kernel doesn't properly initialize the AUO panel yet, it only worked before because Win Mo set it up and the kernel never fully turned it off. So now that the kernel is turning it off some rhod 100's aren't waking up. This issue isn't limited to just this test kernel, but exists in all recent kernels. ACL is working on getting the init info for your panel into the kernel. Hopefully it's just the two panels. Should there be a 3rd panel out there it will still be screwed until we can get a volunteer to grab the panel init info from it via haretconsole for us.
2) WiFI shows error
Click to expand...
Click to collapse
Both the stripped and non-stripped versions of the modules file? And are you getting the same stuttery slowness that pdawg17 is experiencing?
3) The in-call/speakerphone volume seems OK
Click to expand...
Click to collapse
Good. That was one of the new things in this test kernel.
4) Auto backlight function seems to be OK, since it was OK in other kernels.
Click to expand...
Click to collapse
Good.
5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.
Click to expand...
Click to collapse
Get back to us on that one when you can. That's one of the new modifications that WisTilt2 is specifically testing in this kernel.
If You say me on what exactly to focus i'll give more info
Click to expand...
Click to collapse
Battery.
SD Card Issue
thomas d said:
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news
Click to expand...
Click to collapse
Back up your data via Titanium Backup (downloadable from the market) and try renaming your data.img file to something else. Android will recreate it the next time you boot and hopefully your sd card issue will be gone.
Stuttery Slowness
pdawg17 said:
So far testing the Rhod kernel:
1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...
2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...
3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...
4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...
5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...
I'll keep it running today to see how battery life is...
Otherwise it is great! I'll keep testing!
UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...
UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!
Rhod400 (Sprint TP2)
Click to expand...
Click to collapse
The stuttering slowness means system_server was running amok on your handset. When it goes berserk, it puts a stranglehold on the cpu, preventing wifi and other things from getting their fair share of resources. This issue has existed for months, but it used to be much less common. It appears to be occurring far more frequently in newer kernels with the latest system.ext2.
Thanks for the feedback!
Sleep of Death
vnes1984 said:
Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static
Click to expand...
Click to collapse
Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)
LOL, thanks for takin care of mah thread F22
Not much for me to do there tho
F22 said:
until we can get a volunteer to grab the panel init info from it via haretconsole for us.
Click to expand...
Click to collapse
Already uploaded to ppcgeeks.
And I did some more testing:
1) I've renamed data.img file and commented lines in froyo.user.conf (from tiad8's 3D Package post) to have a clean system.
2) Tried with stripped modules: Wifi shows error.
3) Deleted this newly created data.img file and tried to boot with not stripped kernel modules: Wifi seems OK.
As told pdawg17 screen lights up, then dim out. Sometimes it is working OK. This behavior exist either with autobacklight enabled or disabled.
Still not enough time to check battery :-(
F22 said:
Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)
Click to expand...
Click to collapse
I haven't experienced this with other kernals. well for awhile. I've since updated to the most recent kernal after the SOD. (working very well btw) It seemed the test kernal had very inaccurate battery readings compared to other kernals. I would hit the power on button to wake and the screen would flicker slightly, it wasn't until I swiped my thumb across the bottom of the screen that the phone would wake up. Once I left it sleeping for about an hour and tried everything to wake it up but no such luck. (rhod400)
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.
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…)
Hi,
I received my RN8 Pro just yesterday (22nd Oct) (India).
The first thing I noticed is the screen quality.
I find the screen is calibrated a tad bit warmer than usual. Even if you go to the screen settings and tweak it to 'cool', it still remains yellowish.
I came from OnePlus5, which had an AMOLED screen (not fHD/SuperAmoled). There the screen was obviously more crisp, I don't really expect that here. However, the calibration looks bit different if I hold these 2 phones side by side.
What I want to know is, is this just my RN8 Pro, or others also feel the same?
Also, in MIUI where is the 'night light' setting, where I can either manually or automatically turn the screen hue warmer? It's one of the main features in OxygenOS. Actually, the current RN8P calibration looks like 'night light' is already set.
Issue summary:
1) Daytime screen temp looks like as if the 'night mode'/'night light' is already ON. (Note, I don't mean 'reading mode', that's different)
2) Night time screen temp gets very yellowish, almost as if the 'reading mode' is on
3) Screen calibration (warm/default/cool) doesn't change it a lot
4) Can not find the setting to turn off the 'night mode' in #1
Thanks.
In RN8P you can find Night Light in "Reading Mode" in Display option, it turns the screen hue warmer. I'm not sure about the warm color. May "Reading mode" is enabled which is causing this. Try to check that option.
frosthawk said:
In RN8P you can find Night Light in "Reading Mode" in Display option, it turns the screen hue warmer. I'm not sure about the warm color. May "Reading mode" is enabled which is causing this. Try to check that option.
Click to expand...
Click to collapse
No, it's turned off still the screen feelings yellowish.
Exactly. It's so yellowish all the time!
Shubhayudatta said:
Exactly. It's so yellowish all the time!
Click to expand...
Click to collapse
I feel it's not all the time, it's mostly at night. Will compare again now. I got it yesterday afternoon.
Yes. And there is no quick way to disable the night time extra yellow tint.
You think it would be eligible for a replacement?
If you could compare it to another rn8 pro and see an obvious difference then yes you should claim for warranty.
frosthawk said:
If you could compare it to another rn8 pro and see an obvious difference then yes you should claim for warranty.
Click to expand...
Click to collapse
I don't know anyone around who has another RNP8.
I am waiting for others to comment here, for their own devices.
If I find mine is an exceptional issue, I'll try to get it replaced, though I feel that may not exactly come under their replacement policy.
Shubhayudatta said:
I don't know anyone around who has another RNP8.
I am waiting for others to comment here, for their own devices.
If I find mine is an exceptional issue, I'll try to get it replaced, though I feel that may not exactly come under their replacement policy.
Click to expand...
Click to collapse
It's fine in day time, I'm using this phone.
At night the screen turns yellowish automatically, it's miui issue, sceen is fine. Don't bother about replacement, just report the bug from the phone and wait for software update for fix.
@SidDev said:
It's fine in day time, I'm using this phone.
At night the screen turns yellowish automatically, it's miui issue, sceen is fine. Don't bother about replacement, just report the bug from the phone and wait for software update for fix.
Click to expand...
Click to collapse
Goto Settings >> Display >> Reading Mode and turn of Good Night's read option
Its clear that based on the Sunrise and Sunset reading mode is enabling
Its default set as off. And that's the bug, that it's functional even if it's set off.
Shubhayudatta said:
Its default set as off. And that's the bug, that it's functional even if it's set off.
Click to expand...
Click to collapse
Try enabling and disabling it. turn off schedule option if it is enabled.
Check whether night light settings are there in developer option or not
Tried all the enable disable combinations, set as disabled right now, can say it works or not only after the sunset.
And, can't find any related option in the developers setting.
SunilSuni said:
Goto Settings >> Display >> Reading Mode and turn of Good Night's read option
Its clear that based on the Sunrise and Sunset reading mode is enabling
Click to expand...
Click to collapse
Brother with due respect, not everyone is noob.
Those who have phone know what's happening. Everything is turned off in that setting still it gets activated after sunset.
It's a bug and we have to wait for the fix.
---------- Post added at 05:00 PM ---------- Previous post was at 04:58 PM ----------
SunilSuni said:
Try enabling and disabling it. turn off schedule option if it is enabled.
Check whether night light settings are there in developer option or not
Click to expand...
Click to collapse
It's not available, I have wasted some time trying to find what's happening. Trust me, it's a bug.
Shubhayudatta said:
Tried all the enable disable combinations, set as disabled right now, can say it works or not only after the sunset.
And, can't find any related option in the developers setting.
Click to expand...
Click to collapse
Update: All the toggling experiments didn't work. Its again yellowish.
Shubhayudatta said:
Update: All the toggling experiments didn't work. Its again yellowish.
Click to expand...
Click to collapse
As soon as the clock hits 10 pm IST, it became yellowish.
Confirmed bug.
I urge everyone to report this, I have already done that.
@SidDev said:
As soon as the clock hits 10 pm IST, it became yellowish.
Confirmed bug.
I urge everyone to report this, I have already done that.
Click to expand...
Click to collapse
For me it's 6pm. I know 'coz I was waiting for it today.
Shubhayudatta said:
For me it's 6pm. I know 'coz I was waiting for it today.
Click to expand...
Click to collapse
It's 10 pm for me, I hope someone else having phone confirm this too.
Looks like mine got fixed on its own. No more automated yellow tint.
Possibility#1: Xiaomi pushed some OTA
Possibility#2: I forcedly changed the 'good night read' schedule to some random time. 'ON' from 11pm to 1am, and kept the scheduler 'ON'. So, it didn't turn yellow at 6pm (the approx sunset time). Once it's past 6, I turned off everything there. It didn't turn yellow. Rebooted. Didn't turn yellow. Will observe again tomorrow.