Database Develop

[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] Overcome oc 2.2 custom VS Stock 2.3: Is it worth it?

Hi,
I'm still running the oc'd 2.2 Overcome fw with oclf and from the moment it booted I was just like Woohooo, that's pretty fast right there!
At 1,4 GHz games ran like a charm and flash vids also. Response time to input is absolutely amazing in comparison to stock rom.
So for those who already flashed to 2.3 on their tabs:
Is it worth it to update to GB?
And lets keep things like power management or battery indication aside and please focus on useful features like the lit buttons while the screen is on eg.
I got everything ready and off to go update, but I somehow love the tab right now and don't wanna mess up this high perf thingy and am afraid, that I'll not be able to reproduce this condition.
Thanks in advance.

K here you go.
The 4 "hard" button lights never turn off. Drives me nutts.
I ran quadrant and got a score of a lowely 940. I am used to getting over 2400 at 1.4 ghz. Plus the test ran wierd. The graphics were really low end, makes me think our graphics card is not being utilized correctly as of now with current update.
Linpack gave me a 11. As opposed to the 19, 20 i got at 1.4
I dont think we have voodoo lagfix yet. I stream alot of video, and I need this fix!
Had to contact Gameloft to get fresh links for all my games as the old ones were for 2.2. That sucked explaining to them I have a "official" firmware that is not out yet.
Had to reinstal uninstal flash several times to get it to work correctly. Finaly had to settle on 10.1. Web pages indicated I didnt have flash.
In my opinion, I would wait untill you can overclock it. Or atleast a cm7. I am gonna stay on it to mess around with some games that need 2.3.3
I was excited about the prospect of an actual google voice. As it needs gingerbread to work correctly, but that is a bust so far cause our phone number cannot do incomming calls. So basically it works the same as on 2.2.1. You can use it in conjuntion with groove ip to call out and get voicemails, but no incomming calls. Google chat is a bust also. No video chat for us yet.
Also, I havent seen any conformation that we can go back to 2.2 or 2.2.3
HIT THE THANKS BUTTON IF I HAVE HELPED.
Sent from my GT-P1000 using XDA Premium App

Well, after some time on GB I don't wanna go back =)
Only the OC/UV kernel is a bit tricky.

[Q] JVH 2.3.3 wake up problem

hi to everyone,
I instaled to my SGS new room JVH from samfirmware.com and it works great except one very important thing.
Very often when somebody calls me, the screen dosn't wake up and I can't see who is calling
The same happened when I try to use the cell phone and push the home button, the screen also dosn't wake up and the screen always remain black.
sometimes after a few attempts it started to work well untill the next time...
I have already posted this problem on another forum but nobody helped me.
thanks in advance for your help.

Try installing autokiller, set to optimum. Sounds like you are running out of ram/memory management.

markdj57 said:
Try installing autokiller, set to optimum. Sounds like you are running out of ram/memory management.
Click to expand...
Click to collapse
Unfortunately it didn't help, still the same problem.

Which kernel are you using?

-IK- said:
Which kernel are you using?
Click to expand...
Click to collapse
I only installed the firmware I9000XWJVH from samfirmware.com with release date May 4 and nothing more.
http://www.samfirmware.com/WEBPROTECT-i9000.htm
in my phone I found this information:
2.6.35.7-I9000XWJVH-CL184813
[email protected] #2

I suspect its known issue with external sd card.
If you have ex-sdcard inserted, try taking it out and see if the problem still present.

Do you use setCPU?

ulsa said:
Do you use setCPU?
Click to expand...
Click to collapse
I dont use it.

dirn1111 said:
I suspect its known issue with external sd card.
If you have ex-sdcard inserted, try taking it out and see if the problem still present.
Click to expand...
Click to collapse
dear dirn1111,
It seams you were right
After removing the external SD card and testing during the whole day the problem has never appeared again !
Do you know if the Samsung programmer are working to solve this bug ?
Thank you very much for this advice !

doll00 said:
dear dirn1111,
It seams you were right
After removing the external SD card and testing during the whole day the problem has never appeared again !
Do you know if the Samsung programmer are working to solve this bug ?
Thank you very much for this advice !
Click to expand...
Click to collapse
I don't know if Samsung will fix this issue or not,
but I think no..
In my opinion, since SGS has huge internal storage, many people will use without sd card..?? Also not many people actually reported that issue even if it is present.
just my opinion..
its problem with sgs, just try not to use ex-sd..
and also it affect the device overall function,
I just read from somewhere that it decreased quadrant score by 100~200.( although it can be merely numbers, but thats strange)

I've facing this problem as well...
but mine is not related with the ext-sd card problem because im not using it...
anyone can help?

I just had the problem this morning, had to hold power button for 10 seconds to reset. Stock JVH.
AFAIK, the phone was still running but wouldn't turn on as the battery usage showed the battery discharging overnight.

Did any other else facing this problem as well?
because i face again with stock JVO + CF root for JVO.

Yeah I have this problem occasionally, hitting the power button sometimes doesn't wake up the phone, I have to hit the home button or the power button several times I think, cannot remember exactly, but I always manage to bring it up. It's annoying I agree.

I can always bring my phone back by hitting the power button around 10 sec, the boot up screen will occur if it success...
but this is really annoying, and totally a big problem, just wonder is there other else facing the same problem like us or only few users facing it?
Is the GB problem? because i nvr facing this kind of **** when using 2.2.1...

hi i also upgraded my phone from 2.2.1 to 2.3.2 gb i am also facing the same problem. can any body help in rolling back to original oem foryo 2.2.1?
pls help

Has happened on froyo too.
Sent from my GT-I9000 using XDA App

whats the solution for this?

Use stock lock screen has helped me. Probably reducing number of widgets, therefore ram use will help too.
SetCPU app with a minimum of 200 or more Mhz might also help??

i was facing the same problem since i started to use JVH and JVO with Cf-root.. i was using froyo JS8 with speedmod kernel because of the problems coming with JVB so far but when JVH was out i decided to flash it.. first i was using it with Cf-root.. after a long reading time i decided between CF-root and fugumod.. i have chosen fugumod and never experienced not-waking up issue..
but then i switched to JVO and realised its not good with fugumod, i came back to Cf-root and had those "eternal sleeps" 2 or 3 times.. but yesterday i made a whole clean flash of JVO and Cf-root.. so far, no problem..
i red people complaining about the same issue with Cf-root under the fugumod topic.. but i dont know if Cf-root is to blame.. it might be JVO and JVH to blame because fugumod is JVB based, so its normal that i didnt have any not-waking up problems..
PS: i dont think its because the memory is not enough.. because i never use any task killer (not even the task manager itself) but only watchdog for android OS and my RAM usage is normally like 225/329 Mb..

[Q] YA "Which ROM" thread - with details

Advance apologies for the common request.
Background:
Used to run Serendipity 6.4 and loved it.
Phone's internal flash went bad. Samsung replaced "guts" and sent back with AT&T 2.3.5 installed.
So, looking for a more modern ROM with some (or all) of what I liked about my old one. I assume I now have GB bootloaders, so figured I might as well put something else on it now. It doesn't look like Serendipity VII is getting updates.
Things I really liked about Serendipity 6.4:
Voodoo Sound (pretty much a Must Have)
Display tweaks
Packet data setting (plus lots of other stuff) in the long-press power menu
Auto-brightness that works
GPS worked fine, but could be due to other patches I installed.
Stable!
Things I like about stock GB:
USB works better
If you know of a ROM that can turn off the cell radio but leave WiFi active, I'd just about kill for that (fringe cell signal at home kills the battery). I don't care about over/under clocking.
I don't know if I care if it's an i897 or i9000 based ROM. I haven't really noticed the Audience chip improvement since I got the phone back. I haven't been able to get a GPS fix yet, though.
Thanks a lot,
- LoopinFool

LoopinFool said:
Advance apologies for the common request.
If you know of a ROM that can turn off the cell radio but leave WiFi active, I'd just about kill for that (fringe cell signal at home kills the battery). I don't care about over/under clocking.
- LoopinFool
Click to expand...
Click to collapse
Just put in airplane mode and then turn wifi back on, worked on stock and every other rom ive used.
Im running helly bean and it is awesome

master2828 said:
Just put in airplane mode and then turn wifi back on, worked on stock and every other rom ive used.
Im running helly bean and it is awesome
Click to expand...
Click to collapse
Either that didn't work in Eclair/Froyo or I'm an idiot -- or both.
Thanks for that,
- LoopinFool
PS:
I see Helly Bean mentioned a lot here recently and I'll look into it. Please continue with suggestions as I'd like a few good options to look at.

Thread closed
The best ROM is the one that works best for your phone. Try them and make your own decision.

[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.