Database Develop

What determines how fast the phone wakes?

I'm running CM7 stock and I have very inconsistent wake times. Sometimes I'll wipe and flash CM7 and wake from sleep is instant. Sometimes it's a full second.
This doesn't seem tied to CPU speed or governor (I've tried several options with no effect).
What's the best way to ensure wake is instant?
Sent from my GT-I9000 using xda premium

Why are you posting this here?
Go away.
Sent from my Galaxy S using XDA Premium App

Simple answer: because the people here know the answer and it very much relates to kernels and how they handle sleep/wake.
Longer answer is I don't know how to move it now that I've posted it.
(Yes, I'm fully aware the longer answer is shorter...)

I have the same issue. I have found that the NEO kernel 18 on nightly 181 has relatively consistent wakes though it still is often over a full second. Worse if you have had your phone in sleep for longer periods of time, I imagine it has to do with deep sleep.
For some reason it seems that pressing volume down and power button often wakes up the phone instantly (if it puts the phone into mute or ring mode) but this method is not very consistent. If my phone is connected to power, it wakes up instantly.
I have also tried different governors and overclocking including putting the phone at minimum 200Mhz but it still wasn't consistent.
Flashing a stock Gingerbread Samsung ROM does have instant wake-up. I haven't tried flashing older CM7 Nightlies to see fi the issue emergers at an specific point, but not unlike you it seems to be a recent issue with me somewhere in the ~170s nightlies.

I'm finding I get fairly consistent instant wake with Glitch's V13 kernel (even with max 800mHz to save battery).
Just wondering what the method is behind the madness.

I don't think it would be an app as freshly flashed still shows the problem. Ill try that kernel see how I go with it.
Sent from my GT-I9000 using xda premium

omnikai said:
Simple answer: because the people here know the answer and it very much relates to kernels and how they handle sleep/wake.
Longer answer is I don't know how to move it now that I've posted it.
(Yes, I'm fully aware the longer answer is shorter...)
Click to expand...
Click to collapse
Stupid. This area is for development.
Sent from my GT-I9000 using xda premium

This is a very good question, and something that has bothered me about the Galaxy S for a very long time. HTC devices snap on instantly when you hit the button regardless of how long it's been off, but the SGS takes an annoyingly long time to wake up most of the time.
That said, these folks are right, this doesn't really belong in *development* unless we are investigating the cause at a lower level or working on a solution.

BHuvan goyal said:
Stupid. This area is for development.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
This is directly relevant to the development of SGS roms and kernels and we're attempting to discuss the problem and possible resolutions - I am hoping for a "low level" answer regarding the scheduler in use, perhaps. However obviously some disagree, so I'm happy to move it, but I have no idea how.

omnikai said:
This is directly relevant to the development of SGS roms and kernels and we're attempting to discuss the problem and possible resolutions - I am hoping for a "low level" answer regarding the scheduler in use, perhaps. However obviously some disagree, so I'm happy to move it, but I have no idea how.
Click to expand...
Click to collapse
well, afaik this is a bug in latest cm7 nightly, i am running older cm7 nightly, mintberry crunch miui and super osr and my wake is instant.

Among other things maybe, it has to do with the voltage set at sleep mode... i think.
Notice how it wakes up instantly when the charger is plugged in..
Those interested could use setvcell to change the voltage at the lowest speed for the sake of experimenting.. but do give us your feedback please.

[Q] Sleep of Death?

I've recently loaded up my dad's OG Galaxy Tab up with Cyanogenmod's release of Jelly Bean, the October 7th release to be specific. He uses it infrequently, but has been suffering from sleep of death issues so he has to power it up every time he wants to use it.
Is there any fix for this at all?
Has anyone else been having these issues?

Hi,I've had the same problem a few times also,and random reboots. I read a few suggestions that putting the min CPU frequency to 400 might stop sods. Hope that helps.
Sent from my GT-I9100 using xda app-developers app

SamBroomby said:
I've recently loaded up my dad's OG Galaxy Tab up with Cyanogenmod's release of Jelly Bean, the October 7th release to be specific. He uses it infrequently, but has been suffering from sleep of death issues so he has to power it up every time he wants to use it.
Is there any fix for this at all?
Has anyone else been having these issues?
Click to expand...
Click to collapse
I'd suggest going for the most up to date nightly, I've not had any problems with sleep of death, although I have had maybe 2 complete shut downs at night when its been on charge.

You tried to change the governor?

[Q] black screen of death

I'm baffled and trying my very best to work out why I'm getting the BSOD on this phone. There appears to be no logic or pattern to when it occurs, so it's very difficult to diagnose what's causing it. I've now had two of these phones where it has occurred. The first one I took back and got a replacement under warranty. The second one worked like a charm on stock GB with no flashing of basebands, but since messing about and installing both CM10 and the latest ICS ROMS it's started happening again.
It seems to occur most when I go to charge the phone. It'll just die a death and I'll have to take the battery out before it even thinks about starting up again. Perhaps the most annoying thing of all is that it resets all time and dates and will then fail to use the network provided settings.
Has anyone else had this problem and found a solution that works long term? What about the cause? The strange thing about it is that it can go for a week without doing it...then, it'll happen twice in one day. And it's getting frequent to the point of being very irritating. I'm wondering If a different baseband would help. It currently detects it as unknown, but if memory serves I flashed the old 528 original stock baseband for use when I first installed CM10.

I have experienced it in every rom (I have experienced it in: cm10, all GB roms Ive tried, all ICS roms etc..) but not in cm 7 ... so I usually go back to that rom most of the time..

What baseband are you using? Whether or not it has anything to do with it I don't know. Desperately trying to find a fix. I'm thinking it can't be a rom issue. I'm just hoping it's not the phones hardware.
Sent from my LG-P990 using xda app-developers app

The worst thing is don't know how we carry cm10 bugs after flashing over different roms even with full wipe..I lost my amazing battery life after cm10 flash got new battery calibrated food full wow did smart flash still battery life drains like in 10% in hour even without any use....gross

This bug has been reported in the CM10 Bug Thread, you should take a look at it.
Basically the workaround is to turn on your screen before plugging the phone to a charger. There are users saying that they also have a lot of BSOD's when plugging the phone in CM10.

Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.

Rayman96 said:
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Click to expand...
Click to collapse
You seem to be in a foul mood lately, passing such comments on all threads.
And for your info, increasing min cpu clock frequency has no effect on cm10 bsod. It may work in some roms, but not on this one.

Rayman96 said:
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Click to expand...
Click to collapse
Dude if you read my post im saying it occurs whether cm 10 or not. Changing clock frequency did nothing for me so thanks for pointing out the obvious. Like i say, it's a problem I've always had with this phone whether I was on stock gb or not and im getting sick of it. I just wondered if anyone knew the reason and a sure, concrete solution.
Sent from my LG-P990 using xda app-developers app

I am on CM10, and I never get random BSODs. I am on the 11/20 nightly.
For me, the one and only time a BSOD occurs is if my screen is off, and I plug in the charger (USB or wall), and the charger doesn't cause the screen to turn on automatically. If the screen turns on the moment the charger is plugged in, I won't get a BSOD.
My "solution" at the moment is to always turn on the screen before plugging in my charger. No more BSODs.
I used to get random BSODs even off the charger on earlier nightlies, but after 11/10 it was all right.

Mine is just the opposite....whenever i dont have it charging the bsod will appear sooner or later if its plugged in everything is ok...i tried changing min freq and clean installed all cm 10 nightlies so far but nothing has helped.
Sent from my LG-P990 using xda premium

haunterx said:
Mine is just the opposite....whenever i dont have it charging the bsod will appear sooner or later if its plugged in everything is ok...i tried changing min freq and clean installed all cm 10 nightlies so far but nothing has helped.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Same here with CM10, and some days worse than others. Although weirdly it was exactly the opposite with stock GB or CM7 - it would do it mostly while charging.

See this is my point.. Just how many folk are having this problem with the device? I might contact LG support to see if it's a known issue. I have it both whilst charging and not whilst charging. A Google of the topic does support a fair number of everyday stock users as having this issue. I just don't think it's a rom specific issue. The occurance is so spasmodic I think it's simply coincidental.
Sent from my LG-P990 using xda app-developers app

withoutwings said:
Same here with CM10, and some days worse than others. Although weirdly it was exactly the opposite with stock GB or CM7 - it would do it mostly while charging.
Click to expand...
Click to collapse
Same here. With CM7, very, very rarely would the phone just "die" with a black screen when charging. If I had it plugged in via USB to my computer and then immediately plugged into the wall charger, it would almost always BSOD. The only way to recover was to unplug it, pull out and re-insert the battery. This happened so rarely (especially if I always rebooted the phone after using USB) that it wasn't a problem for me.
With CM10, it will instead BSOD if it's just left idle with nothing connected. This happens 0 to 10 times a day with no logical pattern. Some days, I almost think the problem is gone, others the phone is almost unusable because it keeps dying. It has never had a BSOD while charging. This has happend with every nightly build of CM10. I've also had the problem where the caller/person I call just hears "dialup modem" type noise.
Monday evening I flashed SU660 V30c baseband. Still no BSOD as of today (noon on Wednesday). However it has gone this long without BSOD before, so fingers crossed. I have a "Made in Korea" P990 and it previously had Baseband 20I-EUR. Also going to do a few test calls to see if the noise problem is still there.

That's very useful to know. As you say the problem is so bizarre and so random that's almost impossible to know until weeks later if it's been solved for good. I just hope that final ics and baseband release will put the issue to bed once and for all. Can anyone confirm whether or not they have had this issue with the latest leaked ics baseband?
Sent from my LG-P990 using xda app-developers app

48 hours without a BSOD after flashing BB 30C however now calls have gone completely quiet. Neither party can hear a thing.
Back to the drawing board :silly:

Is anyone else's phove really hot when BSODed or is it just mine? When I was on Gueste 3.6 everything was ok until it BSODed, that's when cm10 came out, tried it, changed a few basebands and didn't have it for almost a month, suddenly a few days ago while I already returned to default bootldr and partition sizes on gueste 3.8ext3 with v28g bb I think (20121110)
Sent from my Optimus 2X using xda premium

UPDATE ON BSOD: I used Titanium Backup to freeze the stock browser (using chrome now lol) and for the past 3 days I haven't had a BSOD. Can people try to do the same and report what they find?

neovdr said:
UPDATE ON BSOD: I used Titanium Backup to freeze the stock browser (using chrome now lol) and for the past 3 days I haven't had a BSOD. Can people try to do the same and report what they find?
Click to expand...
Click to collapse
Truth is that I always use root uninstaller and remove the stock browser and this is the first time I haven't. Hmm... let's see...
Sent from my Optimus 2X using xda premium

I think BSODs occur when the relationship between rom, kernel and baseband is not so good.

Yes it appears to be that way. Unfortunately we don't have a BB for the P990 that works properly with ICS/JB ROM (call audio bugs etc.), which is why development of CM10 for P990 was abandoned. I'm now back on CM 7.2 and everything works as it should.

Battery problem

Hi Folks, I hve had my note for 1 year now and haven't had any battery problems until 2 days ago when I flashed a jb rom. All was fine for about 10 hours when I started to recharge the battery again that went fine, charged to 100% and unplugged, the phone said it was at 100%. After another few hours the phone cut out, no warning just cut out. I could get the phone back on but only when plugged into the charger. So, heres my problem, phone says battery is fully charged but when I unplug the charger it cuts out now. if I boot in to recovery with out the charger it stays on for hours. if I try to start the phone up normally with out charger it doesn't work. I have tried another battery again it started fine for almost a day then the same problems again. I have tried several kernels and roms in case it was one of those that was causing the problem but its the same every time. Im not a newb when it comes to flashing roms some im 100% sure its all ok in that department. any help would be appreciated.
thanks
Graham

My note is also about 10 months old. I want to know if my battery stats. I feel like my phone is giving me short time.
My question is do i need a replacement with these stats????
Sent from my GT-N7000 using xda app-developers app

qazibasit said:
My note is also about 10 months old. I want to know if my battery stats. I feel like my phone is giving me short time.
My question is do i need a replacement with these stats????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
What really matters here is your screen on time (I can get around 4h30 with heavy use). I also see you have a few notifications so there might be some draining apps running in the background (like that *** Facebook app which is constantly running in the background even with notifications off). In any case BBS should help you identify the "rogue" app (if any). Also I don't use Google Now as it's kind of a battery killer.

this problem is same with me...after 1 year use gnote
and this is battery problem..i dont know whats is causing it...
i try to enter recovery mode and ..battery is good..almost 4 hours screen on recovery mode
but if I try to start the phone up normally phone is reboot after 1minute in homescreen android
trying with different rom jb ..same problem ..
after replace my battery ..problem is gone..

@strachg If the phone used to work well before you flashed JB I'd recommend going back to ICS to see if the problem persists. If it disappears the reason is JB which would not supprise me since all JB roms for the Note are not really bug free. If the phone continues to behave like you described and changing the battery does not help either I'd say it's a hardware failure.
Sent from my revived Galaxy Note

altae said:
@strachg If the phone used to work well before you flashed JB I'd recommend going back to ICS to see if the problem persists. If it disappears the reason is JB which would not supprise me since all JB roms for the Note are not really bug free. If the phone continues to behave like you described and changing the battery does not help either I'd say it's a hardware failure.
Sent from my revived Galaxy Note
Click to expand...
Click to collapse
Hi, Yeah I already tried going back to ics and it was just the same, it just seems like a bit of coincidence and really annoying lol. The only thing I can think off that is causing it is as you say that its a hardware fault and it must be overcharging the battery and breaking it. If it was JB that was causing it im sure I wouldn't have been the only one by now.
thanks
Graham

how did you install jb? Was it clean on safe kernel? You havent eliminated the possibility of software issues.
Qazibazit, it looks ok.
Guideline 3,5-4,5 hours on screen time is normal (if you play games can be less, thus is from full to 1%). Total standby time, usually more then 24 hours is normal.
If you have a lot less, go read ahalfords sticky on wakelocks. All you need to know to optimize battery.
Sent from my GT-N7000 using xda app-developers app

Hi baz 77 yeah using safe kernel, tried a few actually. And using utackas. Version of paranoid android now again tried a few Roms. Everything was wiped and redone the process about 20 times. I looked through all the roms. And kernel threads and no one has had this problem. New battery coming so will see how it goes now.
Cheers
Sent from my GT-N7000 using Tapatalk 2

strachg said:
Hi baz 77 yeah using safe kernel, tried a few actually. And using utackas. Version of paranoid android now again tried a few Roms. Everything was wiped and redone the process about 20 times. I looked through all the roms. And kernel threads and no one has had this problem. New battery coming so will see how it goes now.
Cheers
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
yep thats pretty definitive, at least if all those roms are not having same base and thus posibly same issues.
Your new battery will improve your experience quite a bit if its a good one!
Have fun with it and let us know if it worked for you

[Q] Screen burn?

Hi guys, I tried charging my phone while it is turned off. After 20 mins, I get back to check it , it was very hot and has a white patch on the black screen.
I am running on Official CM10.1 Nightly 04/17. Any idea what caused this? Will this go away or do I need to send it in for repairs?

I hope they set in cyanogenmod the charging current not to high. Because if it´s to high it can damage the battery an maybe other components.
I read something in another thread, somebody set it to 1,55 A.
It has its reason why LG sets it not to high.
@anGel_pLayer
let cool it down, and see what happens then

anGel_pLayer said:
Hi guys, I tried charging my phone while it is turned off. After 20 mins, I get back to check it , it was very hot and has a white patch on the black screen.
I am running on Official CM10.1 Nightly 04/17. Any idea what caused this? Will this go away or do I need to send it in for repairs?
Click to expand...
Click to collapse
In my opinion, Nightlies are not trustable...
And I think that, only when someone gets a damaged device, people will start to think twice
before install it.

RuedasLocas said:
In my opinion, Nightlies are not trustable...
And I think that, only when someone gets a damaged device, people will start to think twice
before install it.
Click to expand...
Click to collapse
This was my first time charging on nightly with the phone turned off...
The white patch is gone... But, I can still see the "grid-like" distortion on the display where the patch was... Will, try to wait this out for a day or two...
This maybe could serve as warning to others..

That's BS, a nightly may contain bugs of course but they won't include any extreme system changes without telling you. This is just an unlucky flaw, my phone has randomly started scorching while charging, on stock ROM so its not the CM teams fault. On the other hand fastcharge in the kernel is risky, but the official nightlies definitely don't have this
Sent from my rooted P880

@non4 said:
That's BS, a nightly may contain bugs of course but they won't include any extreme system changes without telling you. This is just an unlucky flaw, my phone has randomly started scorching while charging, on stock ROM so its not the CM teams fault. On the other hand fastcharge in the kernel is risky, but the official nightlies definitely don't have this
Sent from my rooted P880
Click to expand...
Click to collapse
I agree with you but, If that happends in ICS or JB, can be resolved with LG Service (inside of warranty).
In CM I don't think soo... even because it means that bootloader was unlocked.
While CM is not stable/official whatever, everything but a nightly, I recomend people to keep bootloader the way it is, locked.
Don't make any sense to risk when there's nothing 100% functional, I'm talking about ROMs of course. Only official ICS and JB are
stable and 100% functional.
I unlocked mine and I try everything because I don't care. The phone can even explode, I'll buy other... But for a lot of people
it's not so easy.
Apart of that... a big thanks to the CM Team and all devs, I hope they find a stable ROM for O4X.

Ouch. That doesn't look good.
The official CM doesn't have any kernel changes, so it's likely a hardware fault (e.g. short on circuit board) causing overheating. Should get it serviced if it's still under warranty.

After like around 6 hours, the effects of the damage was gone and i decided to charge it again, it charged normally. I really don't know what caused it.
Sent from my LG-P880 using xda app-developers app

anGel_pLayer said:
Hi guys, I tried charging my phone while it is turned off. After 20 mins, I get back to check it , it was very hot and has a white patch on the black screen.
I am running on Official CM10.1 Nightly 04/17. Any idea what caused this? Will this go away or do I need to send it in for repairs?
Click to expand...
Click to collapse
When I saw the pictures my heart dropped to my feet. I didn't know this could happen.. Seems like some weird glitch and I've seen other people post about this same issue but I've been on CM since the 2nd nightly and I haven't had this issue happen to me, thank god.
Sent from my LG-P880 using xda app-developers app

I realized that it gets hot when it is turned off and I charge, too...
But I never had those awkward problems... Let's hope that it only happened once

anGel_pLayer said:
Hi guys, I tried charging my phone while it is turned off. After 20 mins, I get back to check it , it was very hot and has a white patch on the black screen.
I am running on Official CM10.1 Nightly 04/17. Any idea what caused this? Will this go away or do I need to send it in for repairs?
Click to expand...
Click to collapse
I have this too and i pull my battery out about half hour and i solve with this and now its everything ok.dont turn your phone off when you charging phone,this hapens only when phone is turned off and i dont know why
Sent from my LG-P880 using xda app-developers app

igorstoja83 said:
I have this too and i pull my battery out about half hour and i solve with this and now its everything ok.dont turn your phone off when you charging phone,this hapens only when phone is turned off and i dont know why
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
If the phone is turned off, then the charger chip either is bypassed or not configured properly, since the CPU is off and there's no kernel running. Also thermal protection is done by reading a separate temperature sensor in the kernel then reconfiguring the charger. You would think LG has considered this not uncommon scenario though...

I don't know if you guys had seen my thread about exactly the same thing happening to me, first ac charge on cm10, left my phone for about 10 minutes came back to see the whole left hand side of the screen looked exactly the same as the op's with lines running through it also.
I was devastated lol only had the phone 2 weeks, but it fixed itself over time and within 12 hours the screen was completely back to normal.
I believe the cm10.1 nightlies are missing the lg thermal throttling that the stock firmware had (im only assuming of course) , when the phone got too hot while charging it would slow charge. Doesn't seem to do this with cm10.
Since then ive only charge via a usb port and haven't had any issues at all.
Edit: My phone was turned on when this took place.

igorstoja83 said:
I have this too and i pull my battery out about half hour and i solve with this and now its everything ok.dont turn your phone off when you charging phone,this hapens only when phone is turned off and i dont know why
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
On stock ROM this didn't happen so, I guessed CM caused it. But really, I don't know

Is it possible to change the charge current in CM settings?

anGel_pLayer said:
Hi guys, I tried charging my phone while it is turned off. After 20 mins, I get back to check it , it was very hot and has a white patch on the black screen.
I am running on Official CM10.1 Nightly 04/17. Any idea what caused this? Will this go away or do I need to send it in for repairs?
Click to expand...
Click to collapse
notice the difference between graphical image of stock rom's off-line charging and the one that goes with CM10.1 ? the stock roms came with nice colourful battery animated image, while CM10.1 only came with small white-colored animated battery..
I think there's something missing in the CM10.1 bootimage.. but on my O4X that overheat or white patch didn't happened. I've try several nightlies ( 20 - 28 april)
but still use stock JB for daily usage..