Guys, can anyone tell me the solution for this weird issue that I noticed recently. If I leave my phone alone say for about 30min or so, and if I make call on my phone from different phone, I can hear the call going through but, my phone wont ring and it'll go to google voice. But if I unlock my phone and then call again, it works without any issue.
Therefore my question is, is there something that causing this thing to die after certain minutes. (I'm not using any Task killer app).
Thanks.
krips2003 said:
Guys, can anyone tell me the solution for this weird issue that I noticed recently. If I leave my phone alone say for about 30min or so, and if I make call on my phone from different phone, I can hear the call going through but, my phone wont ring and it'll go to google voice. But if I unlock my phone and then call again, it works without any issue.
Therefore my question is, is there something that causing this thing to die after certain minutes. (I'm not using any Task killer app).
Thanks.
Click to expand...
Click to collapse
What ROM are u using? Did u try replicating the issue on a different ROM?
diablo009 said:
What ROM are u using? Did u try replicating the issue on a different ROM?
Click to expand...
Click to collapse
Yes, I was able to replicate the issue on 2 different roms.
First time it happened was on 'Ginger Clone 2.2 Final R5' and
second time it happened on 'Cezar's ROM Stable XXJPX/XXJPY no-voodoo - Froyo 2.2.1 Captivate' (this is the current rom I'm using). So I don't know if the Tibu is causing issue when restoring the app (I don't backup or restore system app) but I only restore app (no data). I have also tried installing different i9000 based modem (like jk3, jk4, jl3)
krips2003 said:
Yes, I was able to replicate the issue on 2 different roms.
First time it happened was on 'Ginger Clone 2.2 Final R5' and
second time it happened on 'Cezar's ROM Stable XXJPX/XXJPY no-voodoo - Froyo 2.2.1 Captivate' (this is the current rom I'm using). So I don't know if the Tibu is causing issue when restoring the app (I don't backup or restore system app) but I only restore app (no data). I have also tried installing different i9000 based modem (like jk3, jk4, jl3)
Click to expand...
Click to collapse
Try replicating the issue on stock. If yes, it might be a good idea to swap the phone.
Hello Community!!
I am seeing a problem with my Revo, and I'm putting it out here because you guys are good at finding answers.
I am running Gingervolt 1.3 with the blitzkreig kernel installed. I have previously tried Hicks' little ICS responsiveness script.
Here is my problem. Most days after little to moderate use, Phone/text, I have to reboot my phone by either soft reboot (power button) or a hard reboot (battery pull) because nothing at all is responding. By nothing I mean, touch the screen..nothing, open a program...nothing...etc.
It is a slow degrade sometimes where (and my wife has mentioned it using my phone) that the touch screen is really really laggy and non responsive, especially when using a keyboard or even trying to play angry birds.
I have done a full wipe including data, cache, dalvik. I have formatted my internal and removable SD card, I have not used previous backups, instead resorted to downloading programs and installing from scratch.
This is a very frustrating issue. If it was a computer I'd say either the processor was overworking, or the ram was used up. But since we don't use program killers in GB I'm kind of at a loss. And I'm tired of having to wipe my phone every few days just so I have meh performance (and no, I'm not hating on the phone, or the rom or any of the developers, nor do I have any interest in changing phones,etc)
I'm just looking for suggestions/solutions etc. I'm sure I missed something in my troubleshooting steps.
Thanks in advance for those who read through this and try to give a hand. I appreciate it.
Wow. Since you've already gone to extreme measures, I'm at a loss. My suggestion would be to freeze the apps you do install to look for a culprit there. Or, don't install any and see how the phone performs.
I restored a nandroid prior to Google's 10ยข apps promo and my phone is back in fine form. It was lagging badly before that. I was rebooting daily. Now I go for days and the phone's solid.
Sent from my VS910 4G using Tapatalk
I was experiencing similar issues about a week after updating to blitzkrieg 1.0. I restored from backup and it's been stable since. I just installed 2.0 today, so I'm curious to see if it'll have the same effect.
Sent from my VS910 4G using xda premium
I can't say yet whether or not 2.0 has added to or taken away from the response type issues. I did have to do a couple of battery pulls yesterday just to get firefox to do anything. I'm going to uninstall that one. I may, just for S&G's do one more factory wipe and put all the tweaks and mods in place before downloading anything but the most essential programs. I did this phone, but the unresponsiveness sometimes can be a real pain.
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
revo_65 said:
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Currently I have it at 1.7, before when it was really bad, the oc wasn't sticking and I was at 1024, so not overclocked much. I am sure its an app that is causing the problem, but I'm not sure what.
I've never had this type of issue using Blietzkreig or any of the other tweaks so I'd guess you're right in thinking it's an app. Since you've pretty much tried everything else I would say maybe try going back to complete stock then rooting again? That just seems like what I would try if I had tried everything else and nothing worked.
And yeah you definitely don't want to overclock too much because it could definitely damage the hardware of your phone since it's not meant to run at that level. But you said you had it at 1.0ghz so it doesn't seem like that is the problem unless the damage was cause when running at 1.7ghz. I had mine at 1.9 and didn't see any issues except my phone randomly started to vibrate for a while then just restart. It did that twice when i first flashed everything but it seems fine now. I brought it down to 1.0ghz just cuz i'm not really using it now and I don't want it causing any problems with the hardware.
Thanks for the Feedback everyone. I am not sure what the issue is/was/going to be. I think Firefox was a big part of it and I have since removed it. But I am still getting random freezes, almost like the deep sleep while the screen is on. Oh well, maybe I do need to go back to complete stock.
Quick one here, I hope. I flash a new ROM everyone few weeks or so and when I do it seems very fast at first then just starts to chug like no other. Happens with CM9, CM10, AOKP, Slimbean, helly bean, etc. I know it's not the ROM then. I do the standard wipe/reset and then flash the ROM, then flash the Gapps, then let it boot up and go from there. Not sure if I really need to wipe the cache partition, or cache, or davlik cache...but usually do. Why do they always seem to slow down so easily ?
I use a wiki widget, sound search, and the clock... nothing more and close apps out often. It just seems to chug when just navigating, or going through pictures, or just typing. Any ideas or good habits I should have ? Thanks !
Bad question? Anyone I can ask ? Thanks
Sent from my SGH-I897 using xda app-developers app
One thing that I found to help was to reboot the phone every night. I flashed often, so I set schedule in titanium backup premium to redo my backup every night, and then reboot the phone. This dramatically helped the rom slowdown.
Sent from my AT100 using Tapatalk 2
cheddleson said:
One thing that I found to help was to reboot the phone every night. I flashed often, so I set schedule in titanium backup premium to redo my backup every night, and then reboot the phone. This dramatically helped the rom slowdown.
Sent from my AT100 using Tapatalk 2
Click to expand...
Click to collapse
I agree with this. Also, all roms naturally tend to get slower after use. One reason they get slower is due to human psychology. We become used to the rom's speed, so it seems slower after a period of time. Another reason is all the data that is created after you start using a rom. During day to day usage of your phone, a lot of caches and personal data is stored, so they clunk up your system and ultimately slow down your phone. Rebooting deletes a lot of temporary caches and restarts services that may have started leaking memory, so it speeds up your phone.
There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.
So far the solutions I've tried that did not work for me...
-Increased minimum clock speed
-Increased voltage of minimum clock speed
-Removed Titanium Backup
-Removed all third party apps
-Disabled deep idle
-Removed/didn't use task killers
-Tried various ICS & JB ROMs
-Tried various ICS and JB kernels, including baked-in versions
-Tried i9000 bootloaders
These are pretty much all the details I have so far on these SoDs, hopefully they add up to a possible cause or explanation...
-SoDs happen anywhere from 1-2 times an hour to 1-2 times a day and only when screen is locked/phone is idle
-Having GrooveIP or Skype running doesn't prevent SoDs, but Pandora Radio running seems to prevent it
-Sometimes on a fresh ROM install I can go about 24-36 hours before the first sleep death, but after that they occur normally
-If I unlock the screen every few minutes it seems to stay on. If I let it sit anywhere from 15-30 minutes or longer then it will usually shut off.
-The only time I can get this phone to not suffer an SoD is on stock software(GB KK4). Not sure what this means, but it is aggravating because I would like to have better software.
What remedies have you tried, and what worked/didn't work for you?
johnnyrichter said:
There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.
So far the solutions I've tried that did not work are...
-Increase minimum clock speed
-Increase voltage of minimum clock speed
-Remove Titanium Backup
-Remove all third party apps
-Oneclick back to stock with most recent GB bootloaders
-Disable deep idle
-Remove/don't use task killers
My sleep-deaths are random, almost always occur over night while I'm asleep, can sometimes happen within seconds or minutes after locking the screen. Leaving apps running also doesn't stop the problem(GrooveIP is always running, Skype is running most of the time).
The only thing that stops sleep deaths on my phone is leaving it plugged in.
What remedies have you tried, and what worked/didn't work for you?
Click to expand...
Click to collapse
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.
BWolf56 said:
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.
Click to expand...
Click to collapse
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.
I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.
johnnyrichter said:
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.
I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.
Click to expand...
Click to collapse
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel user config (not saying this is the case here).
Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?
If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.
Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?
BWolf56 said:
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel user config (not saying this is the case here).
Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?
If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.
Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?
Click to expand...
Click to collapse
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.
The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.
johnnyrichter said:
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.
The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.
Click to expand...
Click to collapse
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.
If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?
BWolf56 said:
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.
If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?
Click to expand...
Click to collapse
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.
I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.
I have also tried no OC with at least three different kernels/ROMs.
johnnyrichter said:
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.
I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.
I have also tried no OC with at least three different kernels/ROMs.
Click to expand...
Click to collapse
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).
So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.
You got some testing to do, I'll be looking forward to the results.
BWolf56 said:
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).
So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.
You got some testing to do, I'll be looking forward to the results.
Click to expand...
Click to collapse
The only apps that have been consecutive across all my different software installations have been...
-Gapps
-Gmail
-Facebook
-Pandora
-GrooveIP
-Heywire
-Skype(Only been using this for a couple of weeks so I can probably rule it out)
I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.
You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.
johnnyrichter said:
The only apps that have been consecutive across all my different software installations have been...
-Gapps
-Gmail
-Facebook
-Pandora
-GrooveIP
-Heywire
-Skype(Only been using this for a couple of weeks so I can probably rule it out)
I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.
You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.
Click to expand...
Click to collapse
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.
BWolf56 said:
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.
Click to expand...
Click to collapse
I'll check out that app right now and report back with any findings.
johnnyrichter said:
I'll check out that app right now and report back with any findings.
Click to expand...
Click to collapse
Booted phone up just now after an SoD and the only log available is the one it just started. So if it logged anything before it looks like it didn't save it. Crap.
One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...
-GoLauncherEX
-Skype
-Gmail
-Facebook
-Opera
-GrooveIP
-Heywire
While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.
If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this.
johnnyrichter said:
One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...
-GoLauncherEX
-Skype
-Gmail
-Facebook
-Opera
-GrooveIP
-Heywire
While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.
If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this.
Click to expand...
Click to collapse
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Still no SoD and that's with/without Skype running. GrooveIP boots with phone.
If it won't SoD on stock software then I wonder what the problem could be? It's SoD'd with every kernel and ROM I've ever tried.
Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?
I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
Sent from my SGH-I897 using xda app-developers app
JoeCastellon said:
Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?
I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
SoD means, while idle, that it randomly turns itself off. It was a defect in X amount of phones produced up to a certain IMEI number, and ATT/Samsung at one point offered an exchange program so people can turn theirs in for a model that didn't have the issue.
What you're suffering from is low memory. You probably have apps running in the background that are utilizing X amount of RAM, and your browsing/gaming is eating up the rest which slows down the phone. Some ways to fix this...
-Use a kernel that allows you to increase maximum memory. I think Devil kernel allows up to 396mb with no downsides, and 413mb at the cost of something that has to do with playing a certain video resolution IIRC.
-Use a task killer. This lets you kill running tasks except for those you choose to "lock." Some advise against using a task killer, but honestly I've yet to have a problem with any of them. My favorite is the one you can get for GOLauncherEX.
-Use Titanium Backup to delete(or freeze if you buy the pro version) apps that you don't use that you can safely remove, specifically items that constantly run in the background eating up your RAM.
-Use a different ROM. There's plenty of ROMs out there including slim/aosp/etc releases that are faster and arguably better-performing.
I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.
I'm not sure if that would change anything, but try flashing Mosaic.
BWolf56 said:
I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.
I'm not sure if that would change anything, but try flashing Mosaic.
Click to expand...
Click to collapse
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.
Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?
ETA: If it matters any, when I got the phone I believe it was on GB KK4 and was never modded before. When I got it I used the easy-root to corn 7.0a method and first ran Legend5 ICS ROM. That was the first time I started suffering sleep deaths. Ever since then I have used the one-click back to stock w/ GB bootloaders before using any other kernel or rom.
I've used several different kernels/cwm versions to obtain root, at least 6 different ROMs, several different versions of gapps, and numerous other kernels after ROM installation. I've also used the baked-in kernel of each ROM for at least several days before upgrading to something like Devil or Sema. SoDs on everything, both ICS and JB.
I have also tried one-clicking back to stock with what I believe were "up-to-date" GB bootloaders. This was posted by another member that did it and fixed his SoD problem. It didn't produce any sort of a change for me.
I have not tried checking for SoDs on just a root(without ROM). I suppose if I did this I could figure out if it's the root or the ROM that is triggering the sleep deaths, but even if I did get any results from that I'm still not sure how to figure out exactly what's causing the problem since this event apparently can't be logged.
johnnyrichter said:
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.
Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?
Click to expand...
Click to collapse
Mosaic is a ROM that was made by The Family; http://forum.xda-developers.com/showthread.php?t=1061203
It is I9000 based so I'm thinking you won't get any SoD on it. Thing is that it's not JB based. Devs aren't porting from I9000 anymore so you won't find a I9000 ported JB ROM. (Hoping I'm not wrong on this lol)
And yeah, many users reported that flashing the I9000 bootloaders with a JB ROM fixed their SoD problem. Back in GB, it wasn't suggested to have I9000 bootloaders and run a I897 ROM (music player wouldn't work and some other little things) but it seems fine now.
EDIT: I highly doubt root is the problem.