Database Develop

The Boot Loop of Death (BLOD)

Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....

Reserved for future use

My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.

I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done

wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.

I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.

I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.

I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)

The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.

While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.

I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.

I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.

cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.

I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.

DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.

MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?

DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.

I have this on stock 2.1u1 EPE54B

I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.

tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?

[Q] Weird OC/UV Kernel Issue...

Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.

HTCOmega said:
Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.
Click to expand...
Click to collapse
Kernel flashing doesn't always go smoothly. Repeated kernel flashing without complete system wipes in between can cause some things to start going horribly wrong.
Don't use SetCPU to set clockspeeds. Just stick with voltage control.
If you forgot to disable any lagfixes at any point along the way, that could explain alot of the problem.
Suckerpunch kernel is a great concept and is showing alot of promise, but I personally have had alot of stability issues while using it, including random freezes (YMMV, of couse).
Just my opinion, but I would just back up all your data, flash back to stock, master clear, wipe all your cache data, reflash your rom, pick a kernel and stick with it for a while. If you want pure stability and battery life, use the most recent version of either DG's Firebird kernel 2 or Hardcore's speedmod kernel. If you want stability and oc/uv enabled, stick with Glitterball's kernel. Those 3 have been the best for me personally (again, YMMV).

[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][i9000] Custom Firmware?

I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.

Pinpong blockbuster rom - ticks all your boxes. Get faster fix from market.
Your gps will never be 100% satisfactory in the city, in fact it will probably always be poor - no matter what custom rom you use.

Halkus said:
I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.
Click to expand...
Click to collapse
Have you think about CM7? Great Rom, works well on my phone, and add many new things.

Hi Mate, I tried many custom roms and finally settled for
(ROM)GingerCriskeloV77-9LS-CamHack- SIP + NoIncRing I9000/T/M JVP 2.3.4
Cheers

Well, I managed to get it on. Booting up is weird though, it looks for a long time as if the screen is broken, but eventually ti comes on to the Blockbuster lock screen and then everything is fine. It does seem faster - but I'll only really know when I get to one of those situations where I feel the phone is frustratingly slow.
Thanks very much Woolf!
Time allowing I'll give the other roms a shot, although this Blockbuster one does seem to be good enough for me.

Sadly my phone now reboots constantly. it seems to do it when the screen locks

Halkus said:
Sadly my phone now reboots constantly. it seems to do it when the screen locks
Click to expand...
Click to collapse
Check you got the installation right for that rom, maybe you had to flash a jvp stock first or some similar omission?
Sent from my GT-I9000 using XDA Premium App

Sorry to hear you're having issues. Try flashing to a totally stock JVQ first (with repartition) once you've backed up, then if you don't like that, try a custom ROM. I don't think many JVQ custom ROMs are worth trying if you want a taste of custom ROMs. Better to try CM7 or MIUI for something fast and different.
As a side note, the best tip I've seen for fixing the dreadful GPS we have with the i9000 is to buy a Nexus S or just ANY other phone! Yes, some radios appear better than others, but nobody can prove anything and it's almost all subjective feedback. A drop in the ocean of improvement needed for satisfactory function. If you must use it, a bluetooth GPS receiver and 3rd party navigation app seem the best way to deal with it.

I've now stepped away from Blockbuster. Even doing the a perfect install it crashed often and repeatedly. I did try upgrading to the very latest and that crashed several times in the past hour. Part of the problem was the rom starts with a lockscreen that has a messaging unlock on it, but it isn't set to an app that comes with the rom, so it reboots every time. Sadly that wasn't the only problem, as I was still getting loads of reboots.
So that's out of the way.
I'm now a lot more comfortable using Odin so I'll be able to try other options. I'll try the other two suggested in this thread first of all.
Next to test is CM7.
Thanks for the help folks!
CM7 aborted. Instructions are incorrect, the file they say to download doesn't actually match the instructions so that's out. Plus it clearly states it's not suitable for day to day use... so I don't thnk the time in working out how to fix it is justified since it looks like it wouldn't be useful.
I'm going back to the original question in the thread, to say that I'm looking for something stable. I now think that a custom rom is not the way to go. However some modifications may well be.
Can anyone suggest some kind of lagfix/speedup that isn't a complete overhaul like CM7, Blockbuster etc, that is very stable and that'll make my phone faster?
Edit : Part of what I was doing to install Blockbuster was install Speedmod kernel. So I've gone and put that on, and used the clockwork mod to root it, and also convert to ext4. I think things are looking pretty fast so far. I'm not sure if there's a lagfix for this, but I'm quite comfortable just now footering around - unlike the complete rom I don't feel out of my depth. So I think I'll be ok for now.

[Q] Is it possible that my D3 has a problem that prevents running other roms?

I'm running SS 3.05 and have been able to flash several roms (all GB because I need a camera) that others rave about. I have not gotten good performance out of any of them. The worst ones seem to cause almost non-stop force closes on apps while the "best" ones function but my phone runs very hot even when not being used. Just tried Steel Droid 5 over the weekend and I at least got it up and running but the phone was noticeably hot even when just sitting on the counter with the screen off.
I've uninstalled and reinstalled Safestrap a couple of times, deleted and recreated rom slots repeatedly and have just had no success. Is it possible that there is something weird about my phone? Is it just wonky? It does run normally on the stock rom, or at least as normally as any D3 can run but I'd love to run a meaner, leaner rom on my phone.
If anyone has any ideas I'd love to hear them.

JoeHockey said:
I'm running SS 3.05 and have been able to flash several roms (all GB because I need a camera) that others rave about. I have not gotten good performance out of any of them. The worst ones seem to cause almost non-stop force closes on apps while the "best" ones function but my phone runs very hot even when not being used. Just tried Steel Droid 5 over the weekend and I at least got it up and running but the phone was noticeably hot even when just sitting on the counter with the screen off.
I've uninstalled and reinstalled Safestrap a couple of times, deleted and recreated rom slots repeatedly and have just had no success. Is it possible that there is something weird about my phone? Is it just wonky? It does run normally on the stock rom, or at least as normally as any D3 can run but I'd love to run a meaner, leaner rom on my phone.
If anyone has any ideas I'd love to hear them.
Click to expand...
Click to collapse
Weird. Minimoto ran great for me. I wonder if it's an app you install?

Maybe you just have a bad app or two. You can try loading the phone stock and install only an app or two at a time and see if the phone runs better. Maybe after loading one particular set of apps you'll notice a problem.
I run minimoto as well. I don't get the miracle battery savings that others report - mine is essentially the same as running stock for me - but it is rock-solid stable, unlike stock, which tends to go wonky on me after about 5 days or so.

1
I have noticed something like that, I´m on XT862 and I have better baterry performance on Steeldroid 5.0 and If I give a try with Minimoto I have noticed higher battery drain and hot back of my device. So I always went back to SD 5.0. Strange that people have different experiences =).

doogald said:
Maybe you just have a bad app or two. You can try loading the phone stock and install only an app or two at a time and see if the phone runs better. Maybe after loading one particular set of apps you'll notice a problem.
I run minimoto as well. I don't get the miracle battery savings that others report - mine is essentially the same as running stock for me - but it is rock-solid stable, unlike stock, which tends to go wonky on me after about 5 days or so.
Click to expand...
Click to collapse
Would a app that tracks battery usage by app possibly give me that info as well? Slowly adding apps one at a time will be a major chore...

JoeHockey said:
Would a app that tracks battery usage by app possibly give me that info as well? Slowly adding apps one at a time will be a major chore...
Click to expand...
Click to collapse
Settings-applications-battery use