Database Develop

[Q] Cannot receive incoming calls

Sprint HTC Hero
DarchDroid v2.8
Recovery: RA-Darchstar (v1.7... I think)
PRL: 60667
I bought this phone last week, rooted it, and attempted three or four different ROMs before settling on DarchDroid (which is awesome, by the way!). I was initially having issues with multiple FCs and it eventually became unusable until I read up that my device might not be able to handle the OC to 710mhz. I installed the OC widget and throttled it down and now it works like a champ and is still WAY faster than the stock 2.1 ROM. I am still having issues though, that hopefully, somebody can help me with or point me in the right direction. I've spent the last hour scouring almost all parts of the forum and can't find any answers to these issues. Forgive me if I looked them over...
1) All incoming calls go directly to VM. I can make calls and send / receive texts, but no incoming voice calls.
The next one is a two-parter...
2a) The phone will occasionally become so sluggish (borderline non-operational) that I need to reboot it. When I do, I clear the cache and it will reboot then function normally. Could this be a result of a widget that I have installed? (OC widget, battery monitor?)
2b) When I reboot the phone without booting into recovery (normal reboot) it goes into a continuous boot loop. When I try to restore my Nandroid, it still boot loops and I have to wipe and re-flash the ROM. Is this normal?

Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.

I had the same issue with the latest Fresh Rom so I ended up switching to Zen Hero and have never had a FC on an incoming call since. I tried all the fixes for Fresh and never had any luck. I would suggest trying another rom.
p.s. I was able to OC the rom also and it still works fine.

chromiumleaf said:
Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.
Click to expand...
Click to collapse
Thanks for the advice. I ended up biting the bullet and calling Sprint and it turns out all that was needed was a refresh on my account, the phone works like a champ now! I'm using the OC widget and throttled it down to 595mhz, and even OC'd that little bit, it still BLAZES when compared to the Pre that I came from. No hitches or waiting - when I open a program or app, IT ACTUALLY OPENS QUICKLY... an amazing concept!
One more question though: in case I need to reboot, is there a way to save all of my phone settings? I already moved all of my apps to the SD card so I don't have to download them again, but it would be really helpful if I could just load a save file that would re-set my settings to the way I had them before. Is there an app or setting in the ROM for that?

Make a nandroid backup through recovery. It saves every little detail of your phone and if you ever need to go back to that you can simply restore that backup. Titanium Backup is another popular tool but I've never used it myself so I don't know anything about it.

[Q] droid 1, lagging.

hello all, I have a droid one, love the cell! I have a few problems with it i would like to see if anyone can help me out with. first, I used the manual FB01B update from google to update my totally stock 2.1 cell. then used Easyroot and rooted my phone. no problems. I looked around at different roms and decided I really just like froyo and would rather it just run faster. So I decided to load up a kernel from P3 and Oc it using setCPU. I'm using the low voltage 125 kernel with it set for ondemand. I set it after a lot of trial and error to 400/900. but with this setting it still has problems and slows down and gets a bit crazy when going back to the home screen. It will freeze up for 10 seconds with no icons or anything. then slowly come back. I'm thinking of restoring back to factory then updating to froyo without rooting. whats the easiest way to do this? I did use search and didnt find a good wrote up on it. when setting it back to factory will it wipe the p3 kernel and install the stock one? thanks for the help in advance.

What Home Screen Launcher are you using??? Might just be redrawing the home screen everytime depending on what your settings are.

stock launcher. I put a different kernel in this morn and it has seemed to help some. doesnt do the lag near as bad if at all now. im wondering if the low voltage kernel and maybe lack of memory space was culprit,

JAC kernel bug: using audio randomly kills phone

(I figured to post this in Android Development as it wasn't really a fit for any other forum; and made its own thread since multiple ROMs and threads use non-stock kernels.)
I ran into an issue running JAC's OC/UV kernel, as detailed at http://forum.xda-developers.com/showthread.php?t=806116 . Essentially, whenever any kind of audio was playing, whether through headphones or the speaker, local media (i.e. mp3 player) or remote (i.e., Pandora), at some point the phone would just.. die. Capacitive buttons wouldn't light up, no unlock; music would die; and basically a battery pull was required to turn the phone back on. adb logcat reports nothing - you can see the audio streaming, then the logcat shut off with the phone.
Based on the thread above (and searching the Bionix thread), it seems that a non-stock kernel does this. (There are only a couple of posts out of the thousands on Bionix's thread.) I have not tested KingKlick's kernel, only JAC's; perhaps KK doesn't suffer from this. This issue is independent of overclocking/underclocking the phone (verified by setting JAC kernel to 1000/200, then uninstalling setcpu); Voodoo lagfix (verified by disabling lagfix and running audio for about an hour); and ROM (tested using multiple versions of Franken-Twiz and Hybrid - maybe there's an inherent issue with eugene's mods, but I haven't seen any other posts.)
I suppose this thread serves as a warning/bug report for anyone that might encounter this issue if running a non-stock kernel. The best way to resolve AFAIK is to revert to a stock kernel.

Thank you for posting this! My phone had suffered from this at random times since I started using JAC's kernel. I asked about it in a couple of threads but never got a single reply. Glad to know it's not only me

I'm running the same kernal and about 20 minutes ago running pandora my phone just turned off too and had to pull the battery to restart
Sent from bionix 1.9.1 jacs oc/uv kernel

Had that issue at the Gym the other day, not even on Bionix.

I had similar issues, also with the KK Kernel, its not just JAC's kernel. You don't have to pull the battery either to get out of the freeze, you can hold the power button for several seconds and it does a hard reset.
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Just a little work around, try it to see if it works for you.
Sent from my SGH-T959 using XDA App

Actually this is a known problem since even the G1.
If you have anything like setCPU, which I do, and you set the idle or lowest speed lower then 400 Mhz the phone will more then likely freeze up when playing music or when going to idle.
I don't remember off the top of my head what causes it to do this when it goes below that certain Mhz, but Im sure I or someone here can dig the old thread up.

Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App

Ive had this problem to.... but it was ONLY with Jacs 1.1, I revert every ROM back to his 1.0 and have no problems. Everytime I dont, I get a phone freeze.

I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys

jmercil said:
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Click to expand...
Click to collapse
Interesting. I'll try installing JAC OC/UV/Voodoo again and see if this observation is consistent.

r6kid said:
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
Click to expand...
Click to collapse
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.

Would have to agree. There's a bug somewhere. Not sure if its limited to jacs though.
Currently on masters rom kk. Only problem is pandora.

i had this problem too. kinda disappointed cause the kernels make everything run so much better. so i had to go back to using stock cause i listen to music a lot :/

There's definitely some hardware variability, because I can't recreate this bug. I listen to music all day long (MixZing, Slacker, Pandora) running 1.8 w/ JAC's OC/UV Voodoo. Never seen this.

Likewise with Jacs 1.1, had a couple other weird issues running that specific kernel too, not a single problem when I flashed back to 1.0
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo

i get this same thing. ive had it happen with SetCPU both installed and not. right in the middle of a good song bam phone just shuts up. walk over to my toolbox and sure enough the phone is in a state of being divided by zero and only a battery pull lets it return to the world of the living. not greally a good thing when i have sevearl iphone dorks in the shop and they pop on over to my speakers and they say out of the way lets plug in a REAL phone. makes me want to scream LOL. ****ing iphone >_<
i retort with soooo when you get it out of the box....thats it right? nothing can be changed right? oh look that program sucks....what you cant make your own? ...yea...i thought so. hey look im making a call in the scrap room surrounded by 4ft thick concrete walls.... i got full bars lol. they got nothing in the empty parking lot cuz there holding it wrong LOL

Blkegk said:
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Glad it worked for ya!
Sent from SGSV Bionix 1.9.1 KK OC/UV with the quickness!

sxfx said:
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Click to expand...
Click to collapse
I tried that though, as you can see in the thread I linked to above. Uninstalling SetCPU didn't help..

I think it's hardware.... One of the unlucky ones....

Try with a stock kernel. Jac and kk kernels do uv by default, which is like overclocking in reverse. It has the same possible stability issues.

[q] paragon 5.1

Ok...I am a 'somewhat' noob. I do have my phone rooted and have watched many videos and read through the forums. I have not yet flashed to a custom rom, but am thinking of making the jump. Just have a few questions....
Firstly...Anyone have any negative experience with PARAGON's rom? Looking though the many different ones, this one seems to keep catching my eye...
Next...I have backed up all my necessary files including using Titanium pro backup. As I said the phone is rooted. I am running stock 2.1. I have also used one click lagfix. Do I need to remove the lagfix? Can I use Odin to just master clear or do I need to flash to odins stock first? I have rom manger dowloaded also!
Thanks for any input and help in advance!

paragon is an awesome rom
You must disable the lag fix prior to flash. You can odin back to stock as long as you have all your backups. You do not need to be rooted to flash a rom. Odin will get rid of lag fix, but app should do so as well. If you use odin there is an update.zip on your sd. Leave it there, when on stock boot recovery, reinstall packages twice, you well have clockwork recovery. Install zip from sd, choose zip, select paragon, confirm
If you do not disable the lag fix you will get stock in a boot loop

gandalf21502 said:
Firstly...Anyone have any negative experience with PARAGON's rom? Looking though the many different ones, this one seems to keep catching my eye...
Click to expand...
Click to collapse
Yeah...I got tired of waiting for at&t to release an update so took my froyo fate into my own hands...so to speak.
I ran Cognition 2.b3 - 3.02 and was pleased with the performance. I started watching this ROM at RC5 and just pulled the trigger today. The process went exactly as described. One thing I noticed is that this modem supports hsdpa, maybe cog3.0x did too...but never noticed. Went outside and turn GPS on and got 12 sat lock in seconds....sweet. locked in within 10'...very nice results.
Anyway, just get your feet wet, try it, don't like flash back to stock, or try another flavor. So far I'm very pleased with this ROM.

Paragon is great ROM. Been running it for about 6 weeks. I'm on RC5 now, waiting for RC6. I've had no issues. I'm running OC/UV (not required) with very conservative settings. Getting great performance, battery life and pretty good GPS.
Enjoy.

Paragon is a great ROM hands down!

Yeah, I'm running Paragon 5.1 and it's been running great. I haven't changed the OC/UV settings, just running default, with good battery and good speed.
Try it, you'll like it.

There's a reason he named it Paragon.
eSPyeL did his homework, paid attention to the details, and doesn't rush things.
If you like the ROM, throw him a bone. He's sticking with the Captivate for a good while and things will only get better.

THANKS for all the input!
I like my captivate! BUT the main reason I am looking to flash a custom rom is even with the lagfix, seems slow compared to my HTC flavors. I MUCH prefer this phone over them just want better responses. Also really want flash. I am an o/c'er by heart...ever since I have owned a PC I have o/c my CPU/GPU. Just like to get the most 'bang for buck' out of my parts...lol.
I think I shall give this a try...hopefully all goes well...

Take a look at Cezars Continuum v 2.1
After trying at least 10 different roms i am sticking with this one.

I am on paragon 5.1 with the 1.4Ghz 500hz kernel. I absolutely love it. Obviously I'm using the OC/UV to tweak it. I'm getting pretty fantastic battery life. Great GPS. I personally love the look and feel to it. I would reccomend this rom over and over again. I haven't found anything that I don't like about it so far. It's a solid working beast of a rom.

I have been running Paragon since RC3 and it has worked great. I have had a couple flashes that seemed to cause some issues with my phone, but when I had more issues than I could handle, I reflashed it and my phone worked great since. My first issues occurred when I flashed RC4 the first time, I was getting a lot if Force Closes of the system. I flashed RC4 again and didn't have any problems. The last time I had an issue was this past weekend with my flash of RC5.1. I was having some slow down issues where unlocking the phone or going back to the home screen would take more than 5 seconds. I just reflashed on Saturday and haven't experienced what I was before.
The flash issues I've had could be limited to my phone, so I won't be giving any grief to the ROM itself, and reflashing seems to fix it.
I like Paragon because it is fast, I like the theme and don't have to change it every time I flash, battery life is good enough for me to make it every day with only charging at night, and it has Bluetooth voice dialing. The Dev is also constantly updating the ROM to make it better and is doing a great job at it.

Seems over all everyone is VERY happy with the rom...Like I said before I have browsed many roms and Paragon seems to be the one.
Couple more questions. Reading through various posts in the forums, there seems to be quite a few different ways to flash. Is it necessary to remove the battery and external SD card to get into download mode then run ODIN to go to stock 2.1 and then master clear? Some say yes, some say not necessary to use ODIN if you are currently running stock 2.1. I have removed my lagfix btw.
Is it necessary to use ROM MANGER opposed to simply booting into revovery mode yourself to flash the rom?
Paragaon defaults when installed with a standard o/c of 1200 correct? Seems most find that very stable, where 1400 is possilbe but less likely to hit.
Thanks again!

So this was my setup when auto-rotate decided to cut itself out on me. I had been using this setup for over a week now at least.
Paragon RC 5.1, default kernel (1200MHz, 500Hz?)
Generation X 2.0 theme, blue version (from i9000 theme forums)
Now, out of nowhere, my phone's gyroscope stops working on me. Out of nowhere as in, phone hasn't been reset, nothing flashed recently, no new apps installed, nothing, just regular usage.
I tried using the methods in the other threads I found (deleting /data/system/ms3c_yamaha.cfg, then running /system/bin/sensorcalibutil_yamaha to manually recalibrate). Didn't work. Reflashed, wiped, all using CWM, nothing worked.
The sensor was stuck, and all the sensor readings would show that it was flat on a table (0,0,213 or something like that, the calibration utility in the Settings menu would show the ball dead center and not move).
Then I got stuck in bootloop and lost 3-button recovery mode after trying to flash 2.2 Rogers stock via CWM and forgetting to wipe data, and having to Odin flash to stock 2.1 AT&T in order to get 3-button recovery back, then flashed 2e, got CWM and clean installed Paragon from there, and then got rid of the AT&T splash screen.
However, I did notice that after flashing 2.1 AT&T (JH7) and booting to check if the update went through, the gyroscope sensor was working again.
Weird. But I guess that's why people say in the forums to flash to stock via Odin...
ANYWAYS. I literally just finished fixing it. What a painful work-around just because of auto-rotate, in order to get the gyroscope working again, and I don't even know why it stopped working. Definitely a huge negative experience. On the other hand, I'm sure it's an isolated incident not to do specifically with the rom.
On the plus side, battery life is reasonable, call quality and signal strength are great, JS3-based which means lots of themes from the i9000 forums, frequent updates, lots of features and oc/uv options. Did I mention it's fast?

Please PLEASE make sure you know how to restore your phone before flash ANY ROM!
I don't personally run this ROM (for the moment but I've heard good things overall about it.
Good thing about flashing custom ROM's - if you don't like it you have a doze others to choose from!

Well I took the plunge and installed Paragon 5.1...and SO FAR I LOVE IT. Blazing fast compaired to stock even with lagfix installed. Haven't had much time to test all things...but so far...SWEET!

I loved this rom. The best.
Senda from my Captivate with Paragon RC5.1 wait for rc6

Well been using it for a few days now, and I must say...IMPRESSIVE! Speed is great! So far I have found no bugs myself. The GPS is AMAZING! Locks in just a few seconds and I can now travel on an interstate at 65 and it keeps up with me, never thought I would see that on the captivate. Only issues really is my battery life is a bit less, but not much. just installed Juice Defender to see if that helps a bit. I am going to donate for this one! Can't wait to see what RC6 will be like...

gandalf21502 said:
Well been using it for a few days now, and I must say...IMPRESSIVE! Speed is great! So far I have found no bugs myself. The GPS is AMAZING! Locks in just a few seconds and I can now travel on an interstate at 65 and it keeps up with me, never thought I would see that on the captivate. Only issues really is my battery life is a bit less, but not much. just installed Juice Defender to see if that helps a bit. I am going to donate for this one! Can't wait to see what RC6 will be like...
Click to expand...
Click to collapse
Juice defender will actually shorten your time between charges....don't use it. Paragon for me has been awesome. I have been running it since rc3 and it has definitely stopped my urge to flash. Battery life has been amazing and average between 18 and 26 hours on my phone (usually around 20 hours). Play with some tweaks, try out the different paragon kernels and play with your uv settings. When you find the right settings you will be amazed!
********
Sent from my Samsung Captivate using the XDA app
ROM: Paragon RC5.1 1200 mhz/100hz kernel

I love this rom is fast and nice look
Senda from my Captivate with Paragon RC5.1 and waiting for rc6

Issues with Juice Defender? I have heard good things about it....what problems have you had using it? I installed it yesterday, really haven't seen any 'real' difference myself, but I am just using the defualt settings for now.
I am using the default kernel that came with the rom 1200/500. I set via OC/UV all my settings to -75. Max core 1200. Min 100.

[Q] Anyone care to share up-to-date SoD remedies?

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.