My screen occasionally will not sleep. It does not even Dim.
I don't have any background apps installed like setcpu, oc etc.
Just straight apps. Calculator, weather bug (with backgroud updates turned off), etc.
It does not happen all the time. Just occassionally.
Sometimes even after a reboot it will just stay on and not sleep.
Some times just hitting the power button to force sleep fixes it. I wake it and then it goes to sleep fine.
I posted this problem in CleanROM thread and Scott (the CleanROM author) said he occasionally sees it to and does not know the cause.
I was curious if this occurred in other ROMs and if anyone might know the cause.
I'm running the Kernel that came with Clean ROM 2.9.5 by mwalt2 (with the DIM buttons and always on until cleared notification LED).
I also tried restoring CleanROM 2.5 and it did it too (I think it uses the same kernel).
Please use the Q&A Forum for questions Thanks
Moving to Q&A
mswlogo said:
My screen occasionally will not sleep. It does not even Dim.
I don't have any background apps installed like setcpu, oc etc.
Just straight apps. Calculator, weather bug (with backgroud updates turned off), etc.
It does not happen all the time. Just occassionally.
Sometimes even after a reboot it will just stay on and not sleep.
Some times just hitting the power button to force sleep fixes it. I wake it and then it goes to sleep fine.
I posted this problem in CleanROM thread and Scott (the CleanROM author) said he occasionally sees it to and does not know the cause.
I was curious if this occurred in other ROMs and if anyone might know the cause.
I'm running the Kernel that came with Clean ROM 2.9.5 by mwalt2 (with the DIM buttons and always on until cleared notification LED).
I also tried restoring CleanROM 2.5 and it did it too (I think it uses the same kernel).
Click to expand...
Click to collapse
Try reflashing the rom after doing a full wipe, and don't try to restore anything. I would also maybe try out a different kernel and see if that doesn't fix the issue.
#Winning# said:
Try reflashing the rom after doing a full wipe, and don't try to restore anything. I would also maybe try out a different kernel and see if that doesn't fix the issue.
Click to expand...
Click to collapse
I never restore anything after a wipe. Defeats the purpose of a "wipe"
I think it might be the Kernel.
People are to quick to say, I have no idea, so wipe it.
If I had to do that every time someone at work had a computer problem I'd be fired.
Related
I installed Axura 2.0 and it's awesome. I can't say that this issue is related, but I got a FC error from Launcher Pro, and from that point on (as shown in See PU), the CPU meter is frequently going into the red area and either staying there or completely locking the phone so nothing functions, necessitating a reboot. Oddly enough, if it is not completely frozen and I open Set CPU, that will often get the meter to go back into the green. I've already reflashed the ROM, it's "better" but still does it a bit. Does anyone have any ideas as to what could be causing this? I'm thinking something with launcher Pro, maybe? TIA...
Did you try reflashing and not installing any extra apps for a bit?
Also, next time the cpu goes under heavy load, check the samsung task manager to see what is sending so many processes to the cpu.
Chalup said:
Did you try reflashing and not installing any extra apps for a bit?
Also, next time the cpu goes under heavy load, check the samsung task manager to see what is sending so many processes to the cpu.
Click to expand...
Click to collapse
Hey, thanks for the response. I did reflash once, I did not take anything off that was already on, as I never had the issue before. I think then what I will do (if necessary) as a test is to re-flash (or, maybe 2.0.1 will be out sooner than later) and then just put the basics on and use My Backup Pro or Titanium to add things back slowly. On the second suggestion, I had never used it, as it appears to be new to FroYo or maybe Axura added it, but I never saw it before. Assuming the "Usage Time" screen is where I should be looking, it says (for Launcher Pro):
-Application Count 77
-3400895 ms
I'm not sure what all that means, but those numbers are so far above what anything else is using, and with the fact that a Launcher Pro FC started all this mess, I have to believe that this is the issue,or at least a part of it. I think I'll pitch it first and see what happens. Thanks...
If you hold down the home button, then select "task manager" and you should be able to see what is using the cpu so much. Also, try using a different launcher to see if the problem goes away
The one thing I've hated about DJ05, DL09, and now our Froyo releases is that the timeouts on the capacitive touchkey backlights have gotten longer and longer. In DI01 it was a couple of seconds, in DJ05 it was the length of your screen timeout, and by EB01 and beyond it's now the length of your screen timeout AND reset every time you touch *anything*.
Well, I've finally gotten around to figuring out where the change was (setScreenOffTimeoutsLocked() in PowerManagerService.smali in services.jar) and modding it back. Now, as in DI01, the keys will only light up for a few seconds after you press one. I haven't reverted the recent change of regular screen touches resetting this time after the touchkeys have gone on, though: since the baseline is very short, this isn't a big issue.
Note that the version of services.jar on which this is based is from Super Clean 2.9.2. However, a diff seems to show that the only difference between adrynalyne's services.jar and the stock EB01 is the inclusion, in the former, of the battery notification/data throttling removal mods. So it *should* work with any deodexed EB01-based framework, though I've only tested on the self-customized SC292 I'm running.
The mod does *not* interfere with BLN.
UPDATE 4/28: I've removed the previous EC01/ED01 versions because they were turning on the lights a bit too often (screen press as well as button press). Instead, here are two fixed Edify-script versions for ED01.
Evil Fascination/stock ED01 folks should use shortlight-evil341, which basically just includes the light fix and the sbrissen mods. Community ROM folks should use shortlight-community12, which has a couple of other options unique to that framework.
The new files include a permissions fix, so just install the zip and reboot. (Those installing the original file -- SC292/EB01 and Amend only -- still need to manually mount /data and /dbdata and run the fix permissions script in CWM 2.5 after installation.) First boot will take a while.
UPDATE 5/17: From version 3.5 forward, Evil Fascination folks should use the community zip as well. Evil341 is still good for stock ROM users.
UPDATE 6/13: New version (shortlight-cROM2) uploaded for Community ROM 2.0. Edify only, like the 4/28 version.
UPDATE 8/31: New version for Powerwashed (ED05). Edify only.
To be honest I like it when the keys are lit up. Especially in the dark and you're trying to hit one of those buttons. But I do agree that they shouldn't be on after you lock the screen....
Syn Ack said:
To be honest I like it when the keys are lit up. Especially in the dark and you're trying to hit one of those buttons. But I do agree that they shouldn't be on after you lock the screen....
Click to expand...
Click to collapse
Do your keys really stay lit up after you lock the screen? What rom are you using these days?
I'm running Adyn's latest superclean (2.92) and jt's ec10 kernel (TW_kernel-0327-2) and haven't seen this issue. I'm wondering if there is a bug somewhere that is causing this issue with other people.
I don't have a problem with their time staying on..I do wish they weren't so bright..
Has anyone noticed that the in-call "buzz" is related to the soft-key lights being on? I haven't used a Touchwiz ROM in a while (including Superclean), but this is something I've noticed running other ROMs.
This fix might help with that.
Awesome!! Thanks, I can't stand the long backlight time. This is perfect!
DeezNotes said:
Has anyone noticed that the in-call "buzz" is related to the soft-key lights being on?
Click to expand...
Click to collapse
Yep.
It's funny, a bunch of people like the long lights -- and it's their complaints, I think, that made Samsung edit the behavior in later firmwares. But I'm also sure there are a bunch of people who don't, so now there's a choice.
I also think if the lights were as muted as they are on, say, a Captivate, things might be different.
I tried this out. If I wake up my phone the lights stay off but as soon as I press one they never go off until the phone goes to sleep again.
Sent from my Fascinate
Superclean 2.9.1
EB16 voodoo kernel
EA28 radio
No current theme
s44 said:
I also think if the lights were as muted as they are on, say, a Captivate, things might be different.
Click to expand...
Click to collapse
Yea, the lights help locate the buttons in the dark, but they are so bright that they almost overpower the screen. As handy as they are, I'd rather do without them all together personally. But this is a great compromise.
scarfman4 said:
I tried this out. If I wake up my phone the lights stay off but as soon as I press one they never go off until the phone goes to sleep again.
Click to expand...
Click to collapse
You sure it flashed? This is basically the standard behavior.
s44 said:
You sure it flashed? This is basically the standard behavior.
Click to expand...
Click to collapse
I believe so. I booted into CWM, wiped data and cache twice, flashed it and rebooted.
Sent from my Fascinate
Superclean 2.9.1
EB16 voodoo kernel
EA28 radio
No current theme
Yikes, you wiped data!
Don't do that, this is a tiny framework change. (I think I'll add that to the OP.)
Not sure what could be off -- I assume the framework didn't change between 2.9.1 and 2.9.2. You used Red clockwork and not Orange, right? Maybe try reflashing...
(Since you're also in the SC thread, note that flashing any ROM will undo this change.)
Thanks! I have been looking for this!
Superclean 2.9.2
EC10 voodoo
s44 said:
Don't do that, this is a tiny framework change.
Click to expand...
Click to collapse
It worked perfectly for me, and I didn't wipe anything - data, cache or dalvic.
thank you very much s44, I've always wanted this!
This by far is the best mod yet. Not to dis the other great developers but I really hate that the backlights are brighter than my screen and always on.
Sent from my SCH-I500 using XDA App
s44 said:
Yikes, you wiped data!
Don't do that, this is a tiny framework change. (I think I'll add that to the OP.)
Not sure what could be off -- I assume the framework didn't change between 2.9.1 and 2.9.2. You used Red clockwork and not Orange, right? Maybe try reflashing...
(Since you're also in the SC thread, note that flashing any ROM will undo this change.)
Click to expand...
Click to collapse
My mistake, I didn't wipe data, only cache and dalvik (that's what I get for typing in a hurry).
I have Red clockwork, the latest from 3/30. I'll try again after my battery finishes charging.
Bizarrely, the lights seem to revert to "always on after touch" mode while the screen is in power-low super dim mode. Not sure if or how I can do anything about this.
s44 said:
Bizarrely, the lights seem to revert to "always on after touch" mode while the screen is in power-low super dim mode. Not sure if or how I can do anything about this.
Click to expand...
Click to collapse
I bet that was why it wasn't working for me. I was only at about 5% battery when I tried this.
Works perfectly for me.
Nice job.
Also just a heads up for any noob. My first reboot after took extra long but went fine. No problems.
Sent through mental telepathy
I'm not sure if this is an ADW launcher thing or something with the rom, but I just did a full wipe on Sunday because of a reboot issue when using the gps on GSB 3.5 and I decided to install Condemned V10 Stripped and give it a shot.
So far so good, I'm really liking the rom, but my phone doesn't go to sleep unless I hit the End button and cut off the tv screen. Is that the expected behavior with ADW (or this rom), or a glitch? Has anyone else experienced this? Under the Settings menu, it is set to sleep after 1 minute, but the screen just dims some, doesn't go totally dark.
Thanks.
Nope - I'm not experiencing it at all and I've been on this ROM for a week now, after switching from the odexed GSB V3.5. Mine is timing out & going to the blank screen after a minute - don't see ADW being a problem either as I've used it with other Eris ROM.
You did do a full SD card reformat, delete the android folder with USB enabled in recovery mode, and did cache/dalvik wipe, etc. flashing this ROM & also reflashed Gapps (I used the March 2011 GB version.)
Have you look at your CM settings? Auto Brightest On or Off?
Perhaps you want to reflash CM Rom again (just do a cache/dalvik wipe only) to see if it will help.
Auto Brightness is set to On. I didn't do a full wipe of the SD card, just the phone. I can try a dalvik wipe/reflash tonight to see if that helps before wiping the sd card and the android folder.
Thanks.
snortman said:
Auto Brightness is set to On. I didn't do a full wipe of the SD card, just the phone. I can try a dalvik wipe/reflash tonight to see if that helps before wiping the sd card and the android folder.
Thanks.
Click to expand...
Click to collapse
Try checking in Settings>CM Settings>Lockscreen>Timeout and delay and make sure they aren't set to a long period of time. Maybe also try out of curiosity if that doesn't help... Turn off the screen of animation in CM Settings as well. Maybe that's causing a hiccup or something. I've never had a problem with the phone not going to sleep.
Thanks for the tips, guys. I reblasted with V10 (decided to do full version instead of stripped) after a dalvik wipe, and everything went well. Phone goes to sleep fine now, except for text messages from work during the night (which unfortunately isn't something that will ever totally go away while I work in IT).
Stephen
- Great, sounds (looking) good then.
Just in case you haven't set it - for late night beeps & flashing LED, go to Settings > CM >Sound - - - set "Enable quiet hours" to mute so that no sounds will be played, disable vibrations & dim LED brightness. That should help during regular periods of DND (do not disturb) as it is for me w. multiple mail accounts merged & pulled by Google mail - then pushed. Pop3 mail not a problem - don't get or use SMS much on mine so it's not an issue & I don't enable my twitter feeds unless I need to.
(LOL, if I can only "teach" my alpha-numeric pager to do the same, I would not jumping out of bed at 4 am or what not but that's a different story in & of itself.)
Off topic: just in case, CS is reading the post again, this latest vanilla/full ROM is really rocking & rolling - I haven't seen a repeat of the phone not charging - out on assignment Tuesday evening & had NAV-Car Mode on for 2 hours and no FC, etc. Low-power USB charging/generic mini-usb cable and/or home charger (generic/Moto, etc.) putting out only 500 or 600 maH while plugged in seemed to be the culprit in failing to even trickle charge the Eris & draining it fast. It's getting kind of quiet & no news or bugs popping up lately over at the main thread in the developer's subforum .... Overall, it's a job well done - thanks !!
Letitride said:
- Great, sounds (looking) good then.
Just in case you haven't set it - for late night beeps & flashing LED, go to Settings > CM >Sound - - - set "Enable quiet hours" to mute so that no sounds will be played, disable vibrations & dim LED brightness. That should help during regular periods of DND (do not disturb) as it is for me w. multiple mail accounts merged & pulled by Google mail - then pushed. Pop3 mail not a problem - don't get or use SMS much on mine so it's not an issue & I don't enable my twitter feeds unless I need to.
(LOL, if I can only "teach" my alpha-numeric pager to do the same, I would not jumping out of bed at 4 am or what not but that's a different story in & of itself.)
Off topic: just in case, CS is reading the post again, this latest vanilla/full ROM is really rocking & rolling - I haven't seen a repeat of the phone not charging - out on assignment Tuesday evening & had NAV-Car Mode on for 2 hours and no FC, etc. Job well done - thanks !!
Click to expand...
Click to collapse
Glad everything is straightened out now
Thanks for the feedback on v10 as well. I'm testing 11 as we speak. So far so good. Should be posting it later tonight
Sent from my ERIS using Tapatalk
My Thunderbolt is rooted, and I have tried several different ROMs (some AOSP even) and different kernels, and still I get this strange problem... I use WidgetLocker and fairly often when I go to unlock my phone, the touch screen doesn't work. I have to turn the screen on and off several times and sometimes that works, but it may take up to several minutes for it to finally register my touch. I even sometimes have to pull the battery because after ten minutes, nothing is responding. At first, I thought it the ROM/kernel - I used BAMF in the beginning and that is when I noticed it. Then I switched to ShiftSense, and I barely noticed the touch screen ever failing on me, but the lack of GPS locking and accuracy made me switch to NonSense, which I enjoy but again the touch screen not working at the WidgetLocker lock screen comes up again. My other theory was maybe the HTC Ring Lock Screen gets in the way, so I downloaded NoLock and disabled it, but that didn't work. Then I tried use the WL HomeHelper, but that didn't work... I tried different settings, but no avail. I really enjoy WidgetLocker and I want to try to keep it, but I am not sure what other things I should try to fix this problem. Any suggestions would be greatly appreciated! Thanks guys!
widget locker did that to me several times so I gave up on it. Its definitely a problem with widget locker and not your phone or ROM. It freezes. I even set it to unlock with long press of back button and that would freeze as well.
my phone does the same thing, i think its a problem with our phone and gingerbread. it happens less with froyo. I believe its a radio issue.
Sent from my ADR6400L using xda premium
I have used widget locker on over 10 different android devices I've own. I've never had a freeze issue with it. Reason I've had freeze issue starting with low RAM device. Then voltage to low or cpu frequency to low.
Is there a good alternative with Widget Locker? I just love the use of my own custom slider/widgets/custom background... Does any other app do that? I sort of want to try another app and test to see if it is in fact my phone/RAM/ROM/whatever or Widget Locker.
Aup808 said:
Is there a good alternative with Widget Locker? I just love the use of my own custom slider/widgets/custom background... Does any other app do that? I sort of want to try another app and test to see if it is in fact my phone/RAM/ROM/whatever or Widget Locker.
Click to expand...
Click to collapse
take off or freeze widget locker for a few days and see how your phone does. If it doesn't freeze, then you know its the app.
As for the guy that has used widget locker on 10 devices without problems, I call BS, I tried it on stock, and several customs and always had problems.
I sort of like the features of WidgetLocker than my default lock screen doesn't have and the look of it, so if I turn it off, I sort of want to try to find a replacement app in the meantime.
I just wanted to chime in and say I have this issue with my Thunderbolt and Widgetlocker as well. I've found that it usually freezes if I let my screen turn off by timing out. I'll turn it back on and the screen doesn't respond at all. I've found that if I let my screen timeout again while on the Widgetlocker screen, my touch screen will be responsive the next time I turn it on again.
Sent from my Bolt
Same problem here, I stopped using widget locker and just use the sense 3 lockscreen now.
I just wanted to put in my two cents - I was have the same problems with WidgetLocker on BAMF Forever (1.0.7 & 1.0.9). I found another thread on here (http://forum.xda-developers.com/showthread.php?t=1151269) that someone with a BAMF Sense 3 ROM and a custom kernel was having the same issue. Someone else suggested upping the voltage on the kernel to 368 or changing the kernel. It didn't work for him, but it did for me. I'm not using a custom kernel, but there is an option to change that in BAMF Settings. I've been running it at 368 for several days now and I only had one lockup (but that was shortly after bootup and the phone was probably busy doing other things in the background). HTH
Hi guys,
Trying to work out if my phone is faulty or not.
When I turn the screen off, sometimes when I press the middle button to turn the screen back on, it won't turn on. The only way to turn it back on again is if I hold the power button for about 5-6 seconds to restart the phone again.
Does anyone know why? Or any solutions to this?
Happens twice on average a day, it's annoying having to restart the phone!
I think your getting SOD (sleep of death).
try using dorimanX kernel on default settings then see what happens.
Sent from my Galaxy SII
I will try it and see.
If it doesn't fix it, does it mean it's the phone?
Have you overclocked, underclocked, overvolted, undervolted, flashed anything in a bad order, flashed anything at all, changed GPU speeds, turned BLN on? If you answered yes to any of them I suggest you do a reset, reformat, flash a Samsung stock ROM, don't play with any apps that change the default CPU/GPU etc settings and see what happens before you buy a new phone.
postfatal said:
Have you overclocked, underclocked, overvolted, undervolted, flashed anything in a bad order, flashed anything at all, changed GPU speeds, turned BLN on? If you answered yes to any of them I suggest you do a reset, reformat, flash a Samsung stock ROM, don't play with any apps that change the default CPU/GPU etc settings and see what happens before you buy a new phone.
Click to expand...
Click to collapse
The only thing I did was flash Resurrection Remix ROM. Everything else that's there I haven't touched.
I'll format to stock and see if it does it.