Database Develop

SGS Running CM10 Turns off automatically

Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers

HazzaGalaxy said:
Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers
Click to expand...
Click to collapse
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.

Hi,
Is you IMEI ok ? I had this problem with CM10 too but now my IMEI is ok I have no pb at all

have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason

SKArabaeus said:
have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason
Click to expand...
Click to collapse
Hey
Where is deep idle?
I have no idea where it is and ive looked everywhere in settings.
Do you have photos?
That would help.
Cheers

ThrashJan said:
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.
Click to expand...
Click to collapse
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Cheers

HazzaGalaxy said:
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Click to expand...
Click to collapse
Okay, let's start from the beginning :silly:
Whats the exact name of the rom you flashed?
How do you flashed it? (Wipe, etc.)
Have you flashed any other stuff? (Inverted Gapps, Battery mod, Kernel, etc.)
Have you many apps installed?
If i where you, i would flash the newest build with a full wipe, so you got a new, bugfree and stable system

same issue
I have been having the same issue ever since switching to CM10, I have been installing nightlies hoping it will end, but appears to be isolated. Would it help to manually flash boot for each ROM? It cuts off randomly and won't turn on unless charged by a wall charger, or other high-power input (doesn't turn on or charge from car outlet). It doesn't appear to be caused by an app.

Did you wipe when installing nightlies?
If you try to go stock with Odin, and the issue is exactly the same, I think you should consider it could be battery malfunction.
Sent from horseback.

[Q] Galaxy NOTE SOD problems.

My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:

Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2

abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware

Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.

Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?

if u're using pure stock rom still facing the same problems then definitely is hardware issues！
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...

Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..

psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2

I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab

updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?

SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...

Update issue with CM12.1

Hi !
A strange thing happen every time I update my phone : after the update it get slower during 3 out 4 days.
During this time the battery loss is increased, like very much ! It usually lasts 35-40h, but during those days it's not 8-10h !!!
Also the phone gets warmer. Sometimes I can't hold it in my pocket, it burns to much my leg !!!
During all this time its almost unusable so slow it is.
In the end, for no appearing reason, all this bad mood disappear, and I can use my phone again.
Is all this normal ???
Sent from my Xperia SP using XDA Free mobile app

It is not normal! Try coming back to stock 4.3 to see if that happens there too

MizoSome said:
It is not normal! Try coming back to stock 4.3 to see if that happens there too
Click to expand...
Click to collapse
No, I will not do this. "Stock" is less efficient than CM.
And, I forgot to tell, this crazy thing happen since I use CM12.1.
I was thinking to format the phone and clean install CM12.1, again. It could help having a clean phone, but would it help correcting those bugs ?
I'll tell here if it worked, but, ltely, I am very busy so I'll do this later.

OK

CPU small cores do not stop, big cores not working

So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.

baconbeacon said:
So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
Click to expand...
Click to collapse
did u tryed to install a custom rom? or a stock but flashing a kernel?

op3n said:
did u tryed to install a custom rom? or a stock but flashing a kernel?
Click to expand...
Click to collapse
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…

baconbeacon said:
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
Click to expand...
Click to collapse
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?

op3n said:
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
Click to expand...
Click to collapse
Well, if that's normal, this shouldn't be an issue. Though I do wonder where's the big little concept gone.

Did it ever occur to you guys that it might be dynamic hotplugging and a specific configuration/setup is being used ?
Or is it in your case really being buggy and broken ?
You left something working in the background and monitored how the cores behaved ?
Using different apps ? (say: kernel adiutor [or kernel adiutor mod], EX Kernel Manager, CPU Z, etc.)

My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.

My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.

Mi A2 Max Clock speed cut to half, and battery life improved.

So recently many users were saying that the four core were maxed out to 2.2Ghz, I faced the same problem, so instead of rooting my phone and putting the CPU governor in On demand/power saving I tried some methods and bought the clock frequency to 1.1Ghz/1113Mhz. I'm still not sure how this happened but here are the things I tried
After a full day use yesterday nearly 3hrs of screen on time and my battery percentage was left to 37% so, I charged my phone to 90% cleared the cache using fastboot, uninstalled useless apps like clash of clans, pubg, Internet speed meter, and some other.
Note clear only cache
And the results see the images. I can't guarantee that it will work for you, but it worked for me.
As you can see I don't have root accces, so this is done without rooting.

Check for some more time and report here

I can report that clearing cache (complete wipe) totally worked in my case. I had this issue and i reported it to xiaomi, anyway.. i was going through the process of rooting and enabling HAL3 for google camera and the phone was completely wiped (I did not play around with the CPU ) anyway surprisingly the battery life improved so yeah it might be a cache problem.

Chaitanya Kumar said:
So recently many users ...
Click to expand...
Click to collapse
DiesFrae said:
I can report that clearing cache (complete wipe)...
Click to expand...
Click to collapse
Which is the command to clear cache guys, please?
Thanks!

bixirulo said:
Which is the command to clear cache guys, please?
Thanks!
Click to expand...
Click to collapse
Fastboot erase cache

Does this definitely solve the issue? Has it come back?
I'll try later, I have this problem too.

k278467 said:
Does this definitely solve the issue? Has it come back?
I'll try later, I have this problem too.
Click to expand...
Click to collapse
No it does'nt. At least for me. I've unlocked the bootloader (which wipes everything) and changed the scaling governor. This was the 'default solution'... I've experienced the problem 2 more times after that, but it is waaaay less common...

hugopg said:
No it does'nt. At least for me. I've unlocked the bootloader (which wipes everything) and changed the scaling governor. This was the 'default solution'... I've experienced the problem 2 more times after that, but it is waaaay less common...
Click to expand...
Click to collapse
That's so annoying... Is this the kind of bug Xiaomi would normally fix? I bought this phone 4 days ago and still can return it, I'm seriously considering it...

k278467 said:
That's so annoying... Is this the kind of bug Xiaomi would normally fix? I bought this phone 4 days ago and still can return it, I'm seriously considering it...
Click to expand...
Click to collapse
If you can, and you're unhappy... why not? I mean, this bug happened in pixel 2 XL months ago and was fixed. Its a software problem and it will likely be fixed in the future, but an ETA only Xiaomi can give you

hugopg said:
No it does'nt. At least for me. I've unlocked the bootloader (which wipes everything) and changed the scaling governor. This was the 'default solution'... I've experienced the problem 2 more times after that, but it is waaaay less common...
Click to expand...
Click to collapse
For me i was just playing around and unlocked the bootloader (wipes everything) and re-locked the bootloader (also wipes everything) but i didn't change anything and the problem seems to go away like today i had 37 mins SoT with only 9% battery drain so by this rate the battery should be drained in almost 7 hours SoT and that's really good IMHO

Someone can post the complete process or give link with the process?
Enviado de meu Mi A2 usando o Tapatalk

maybe a weird question , but i found that my phone have bootloader unlocked. this is te problem that i cant do ota updates...i know the trick power down and powerbutton to get in the fastboot mode....what im doing wrong when i press those keys i wont get into fastboot i will get a black screen nothing more.....help me pleaseeee