Database Develop

Constant rebooting

i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.

If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?

I do have a overclocked under volted kernal

sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...

WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !

Does your phone lock up (unresponsive) before rebooting?

Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.

Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.

I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.

Reboot & Wifi "error" after 2 weeks of using any ROM

Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!

Sorry for the double post,
Is there a better forum to post this in?

spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate

Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.

Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance

spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.

I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.

bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...

New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?

New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl

Does anyone knows how to stop rebooting problem?

I am now using the Original Stock ROM and downloaded several Apps. After few days, it just gave me headache because of rebooting issues.
I downloaded already the following files:
CWM 5.0.7
Titanium Backups
BusyBox
SuperUser
But still, I encountered rebooting problem.
Can somebody help me?
If this one solve, then, I will add the solution to my Official Thread.
Thanks in advance Guys.

im on v20m stock rom...rooted but havent flash any clockwork recovery...so far havent got any reboot and in fact its the most stable ROM i use so far(from v20f stock to cm7 to cm9 to v20j stock to v20m stock)
what stock version do you have?
you said it started after downloading certain apps...try uninstalling those then check if it will still reboot.
last i would recommend is smartflash the stock rom again

In my experience, I've had random reboots for a number of different reasons. It's hard to tell what may be the cause just based on your description. Please provide more details. For example, Does it boot at all and then reboot after some use? Or are you stuck at the boot animation and cannot go to the home screen at all?
And when you said you are on stock ROM, is it the same stock you had before? Or is it a different one?
To share some of the reasons I've had in the past...
1) Incompatible kernel (may not be your problem since you are on stock)
2) Overheating (usually due to overclocking too rigorously and/or wall charging)
3) Messing up with settings somewhere
And as chupi said, just basing on what you wrote, it may be related to one or a combination of the apps you installed. Or, there may be just a bad combination of the apps that you are using.
I hope you have a backup prior to the app installation. That should help narrow down things, or at least go back to the pre-problem stage.

chupi_24 said:
im on v20m stock rom...rooted but havent flash any clockwork recovery...so far havent got any reboot and in fact its the most stable ROM i use so far(from v20f stock to cm7 to cm9 to v20j stock to v20m stock)
what stock version do you have?
you said it started after downloading certain apps...try uninstalling those then check if it will still reboot.
last i would recommend is smartflash the stock rom again
Click to expand...
Click to collapse
Thanks Chupi.
It is Okay now. I think, it is because of Fruit Ninja, Half Brick application. So, I just uninstalled it.
Also, I disable Background Apps of Yahoo Mail.
Everything is now OK.
I am using V20M.
Regards,
Jose Rey

aragorn7 said:
In my experience, I've had random reboots for a number of different reasons. It's hard to tell what may be the cause just based on your description. Please provide more details. For example, Does it boot at all and then reboot after some use? Or are you stuck at the boot animation and cannot go to the home screen at all?
And when you said you are on stock ROM, is it the same stock you had before? Or is it a different one?
To share some of the reasons I've had in the past...
1) Incompatible kernel (may not be your problem since you are on stock)
2) Overheating (usually due to overclocking too rigorously and/or wall charging)
3) Messing up with settings somewhere
And as chupi said, just basing on what you wrote, it may be related to one or a combination of the apps you installed. Or, there may be just a bad combination of the apps that you are using.
I hope you have a backup prior to the app installation. That should help narrow down things, or at least go back to the pre-problem stage.
Click to expand...
Click to collapse
Thanks Aragorn.
I think, some applications are not suitable for SU660. Right now, I just uninstalled the Fruit Ninja (Half Brick) and disabled the Background Apps of Yahoo Mail. Everything is Ok Now.
I recharge it through my laptop.
I am using V20m and it is the latest version.
Regards,
Jose Rey

I have the same problem. It regularly happens when Im playing games but when the weather is cold for some reason, it rarely happens. must be hardware.

Stability problem

Hello, I'm using Semaphore + CM10 JB for few weeks (installed with your support).
However I have a problem. The stability. My phone likes to resets byself, even few times per day. It happens irregularly. What's interesting, sometimes phone resets to the CWM. Sometimes resets and backs to work, sometimes totally offs the phone (and i need to pull out the battery) or freeze on cyanogenmod start screen (but not on normal start, only when resets)
Sometimes it happens when i'm using the phone, sometimes not. He likes to do that when i'm sleeping (for example, goes to the CWM and discharge the battery by whole night on full bright).
And much smaller, but maybe important issue: when the phone starts, shows the message Warning! A problem was detected with your device. Your device IMEI number is invalid. And invalid IMEI number could cause network issues including the inability to call emergency numbers.
Firstly I installed CM10, i had the problems with the network, but after @xsenman's help (reinstall with older ROM before flashing CM10) everything works correctly and i can see IMEI too. I made an EFS backup in that old ROM, should i use that? This message doesn't intrude me, but i'm just thinking if this could be connected with reseting problems. My SGS works really nice, but that one issue is really annoying.

100 views and really no one can help?
Come on, i feel so lonely

I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color

thanks for your answer. However, maybe it's not a ROM problem? Maybe some application makes an issue. Is there any log where i can check that?

That IMEI stuff definitely isn't app-caused. I can only repeat my statement above. Don't worry about data, you can backup everything using Titanium Backup and SMS Backup+.
Btw: What ROM are you on?
Best regards
Sent from my Gameboy Color

True, IMEI not, but it's not a real issue for me. Actually, i'm absolutely satisfied of my i9000 (maybe flashlight absence, but it's hardware). Everything works fine, but reseting problem makes me nervous when I use the phone as car dvr or for endomondo ect.
I use Cyanogenmod 10, one of october's nightly versions.

So basically you don't want to change anything but you want us to help you? Sorry, that's not the way a community works.

You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.

przemek211 said:
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
Click to expand...
Click to collapse
Since when has this problem occurred? I doubt an app makes a phone reset itself.
Edit: I looked around your post history and you seem to have posted in the semaphore thread. Maybe something is wrong with the kernel?
Sent from my GT-I9000

Thanks for your answer. It's hard to say because I've flash a ROM and out of hand I installed the applications. It's the worst type of problems, because it doesn't happen instantly or regularly. Actually since i wrote the topic, i didn't see the problem, however i saw two-three times the attention about IMEI, so i think, the phone resets, but not seen.
/// amerkiller: you are using i9000 too, could you recommend me any other ROM? Probably I will need to install a ROM and wait, two-three days and check if the ROM makes any issues.
/// maybe, but how can i check it? It looks like work nice, my question in Semaphore's thread was about the features

I use Remics-JB, you can try it out if you want a Samsung touchwiz feel, and apps from the S3.
Slimbean if you want a minimalist ROM.
Hopefully, the problem will disappear.
Powodzenia
Edit: regarding the kernel, you can flash Devil and see if the problem persists.
Sent from my GT-I9000

So I will try Devil + Slimbean, thank you
amerkiller1995 said:
Powodzenia
Click to expand...
Click to collapse
Poles everywhere?
pozdrawiam

BlueFlame4 said:
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
Click to expand...
Click to collapse
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?

przemek211 said:
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
Click to expand...
Click to collapse
You can find tutorials about flashing to stock.
http://forum.xda-developers.com/showthread.php?t=1102881
Flashing the stock ROM will recover your IMEI number if you currently don't have it and will wipe your personal files. Backup your IMEI while you're on GB and if you lose it, then restore it. Fyi I never lost my IMEI, it's not common. You should flash JB / cm10 twice, ICS/cm9 should be okay after one flash. Remember to wipe if the instructions say so.
When you'll attempt to flash cm10 in recovery, you'll get a warning about partition change. You'll have to chose to flash second time, this time it should work and the phone will reboot into a bootloop. Pull out the battery and enter recovery and flash cm10 again. This time it well install and reboot successfully.
Sent from my GT-I9000

It's everything working nicely? Asking out of curiosity.
Sent from my GT-I9000

Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.

przemek211 said:
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
Click to expand...
Click to collapse
Restarts shouldn't happen that was some unusual circumstance. The video problem is weird, post here if it happens again, lets hope its just bad luck.

Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.

przemek211 said:
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
Click to expand...
Click to collapse
In regards to two way recording, i don't think it's solved...
http://forum.xda-developers.com/showthread.php?t=863074&page=38
I never needed that feature, so i won't be much help, try different apps and remember some apps are on XDA, not only the play store.
Sent from my GT-I9000

I saw that, but it is only for Froyo, when i installed it into gingerbread i needed to re-flash my SGS
I tried a lot of apps, however it looks like being locked (if worked they made 0kB files)

[Q] Cyanogenmod 10.1?

Hi guys, I have done research on this but seem to get very different responses, I wanted to flash my cappy to Cyanogenmon 10.1 nightly (jellybean 4.2.2) but now I'm not sure, I've flashed it for testing for an hour before going back to stock, the problems I had is that boot times seemed to be a LOT longer and after I restored my messages with Titanium Backup the messaging app force closed as soon as I open a conversation. I also met a guy when buying resistors (to make a jig lol) and he said that when he had cyanogenmod his battery went down twice as fast and his apps started force closing (but I don't know when that was and if the mod is more stable now).
So, I really need some advise and want to know the pros and cons of the mod, also would be nice to know how I can backup and restore my messages without FC's, also how can I get the samsung apps that came with the phone to cyanogen mod (and would restoring data from a nandroid backup restore all my apps?).
Thanks in advance,
Nik

You have many more options, not only CM10.1 (still in experimental stage) and stock. What firmware you'll chose is your personal preference. Take a look at Captivate Android Development section. Notice how many downloads most popular ROMs have. Do you think those thousands of people fight every day with stability issues and FC? Me personally, I'll never go back to stock. After trying many different ROMs I found what I'm looking for and my phone is now faster (including boot time), stable (I don't remember last FC) and can do way more compared to stock. My battery life with JB is actually better than stock GB. And yes, you can have Samsung apps. For me this bloatware was one of the first things to remove after rooting stock GB. My very first ROM to flash was CM10 stable. Never had any issues with it. Most of the problems are user created (corrupted flash files, incorrect flash sequence, missed reset/format steps, incorrect system data restore from previous Android versions, etc). And you don't need a jig to enter download mode. I never had one, had my phone soft bricked twice, flashed it countless times with Odin and through CWM... and it's still alive. Read carefully all the tutorials and troubleshooting guides.

Val D. said:
You have many more options, not only CM10.1 (still in experimental stage) and stock. What firmware you'll chose is your personal preference. Take a look at Captivate Android Development section. Notice how many downloads most popular ROMs have. Do you think those thousands of people fight every day with stability issues and FC? Me personally, I'll never go back to stock. After trying many different ROMs I found what I'm looking for and my phone is now faster (including boot time), stable (I don't remember last FC) and can do way more compared to stock. My battery life with JB is actually better than stock GB. And yes, you can have Samsung apps. For me this bloatware was one of the first things to remove after rooting stock GB. My very first ROM to flash was CM10 stable. Never had any issues with it. Most of the problems are user created (corrupted flash files, incorrect flash sequence, missed reset/format steps, incorrect system data restore from previous Android versions, etc). And you don't need a jig to enter download mode. I never had one, had my phone soft bricked twice, flashed it countless times with Odin and through CWM... and it's still alive. Read carefully all the tutorials and troubleshooting guides.
Click to expand...
Click to collapse
WOW Thanks for such a detailed reply, the reason I needed a jig is that odin froze during flashing and I got bricked (the brick screen didn't work as download mode in this case). I'll have a look at other ROMs, may I ask what ROM you went with at the end?
Thanks,
Nik

10.1 is fine and stable. messaging is a system app, so don't try to restore it, but restoring only the data should work.
after flashing, you can expect the rom to have a long boot the first time, and to be pretty laggy for as long as 10 minutes. later boots will be quicker. I also use an app, system tuner, to prevent a number of apps from loading at startup.
I stayed with cm10.1, after trying a few other roms. for me cm10.1 is fav.

nosurlife said:
I'll have a look at other ROMs, may I ask what ROM you went with at the end?
Click to expand...
Click to collapse
Yes, but it's gonna cost you $10 per every flash/testing I did for you. And the total is a lot of money... :laugh:
Read your PM -> Info what I use + links where to find it on XDA. But again, first read carefully all tutorials and flash instructions.

laughingT said:
10.1 is fine and stable. messaging is a system app, so don't try to restore it, but restoring only the data should work.
after flashing, you can expect the rom to have a long boot the first time, and to be pretty laggy for as long as 10 minutes. later boots will be quicker. I also use an app, system tuner, to prevent a number of apps from loading at startup.
I stayed with cm10.1, after trying a few other roms. for me cm10.1 is fav.
Click to expand...
Click to collapse
Thanks, I'll look into it.
Val D. said:
Yes, but it's gonna cost you $10 per every flash/testing I did for you. And the total is a lot of money... :laugh:
Read your PM -> Info what I use + links where to find it on XDA. But again, first read carefully all tutorials and flash instructions.
Click to expand...
Click to collapse
I wish I could spam the thanks button multiple times haha, I'll go check out the ROMs, so there's no way to keep my txts?
And is there any difference in RAM usage between stock and other ROMs?
Thanks,
Nik

nosurlife said:
Thanks, I'll look into it.
I wish I could spam the thanks button multiple times haha, I'll go check out the ROMs, so there's no way to keep my txts?
And is there any difference in RAM usage between stock and other ROMs?
Thanks,
Nik
Click to expand...
Click to collapse
You can backup your texts with a app like Titanium Backup.

BWolf56 said:
You can backup your texts with a app like Titanium Backup.
Click to expand...
Click to collapse
I did that but now the messaging app has the conversations when I open it but when I try to open a conversation it FCs,
What can I do now?

nosurlife said:
I did that but now the messaging app has the conversations when I open it but when I try to open a conversation it FCs,
What can I do now?
Click to expand...
Click to collapse
Ok fixed it, did a reset and restored with SMS Backup & Restore now no FCs.
Thanks to everyone I am now happily running Slim Bean release 3 (4.2.2).

CyanogenMod 10.1 taking more RAM
BWolf56 said:
You can backup your texts with a app like Titanium Backup.
Click to expand...
Click to collapse
Hi,
I have flashed my cappy with CM 10.1 Nightly(JB 4.2.2), but now it seems this is using more RAM. already in captivate we have only 512 MB RAM and it uses about 322 MB of it. Is there any solution for this ?? or will flashing some other rom will help ?

mangaicaptivate said:
Hi,
I have flashed my cappy with CM 10.1 Nightly(JB 4.2.2), but now it seems this is using more RAM. already in captivate we have only 512 MB RAM and it uses about 322 MB of it. Is there any solution for this ?? or will flashing some other rom will help ?
Click to expand...
Click to collapse
That's normal.
As long as your phone runs fast and smooth, don't worry about your RAM. Also, if you have bunch of apps running in the background, stopping them will lower your RAM consumption.

BWolf56 said:
That's normal.
As long as your phone runs fast and smooth, don't worry about your RAM. Also, if you have bunch of apps running in the background, stopping them will lower your RAM consumption.
Click to expand...
Click to collapse
Aww I was going to say that haha, the main thing to watch is CPU as RAM is managed differently on android from a PC.
Another thing I noticed is that having a lot of widgets can cause a bit of lag too.

RE: RAM usage
mangaicaptivate said:
I have flashed my cappy with CM 10.1 Nightly(JB 4.2.2), but now it seems this is using more RAM. already in captivate we have only 512 MB RAM and it uses about 322 MB of it. Is there any solution for this ?? or will flashing some other rom will help ?
Click to expand...
Click to collapse
As laughingT suggested, try an app like System Tuner to try to get startup apps under control. Greenify is another app to try before jumping ROMs. You can also go into Settings->Apps and Disable apps you do not use (personally I disable Gmail among others, seems to help battery life too). Additionally, alternate kernels may give you more usable RAM.
Edit: oops, missed the second page of posts... great responses to this question already

Just to confirm - uninstall/freeze apps you don't use (careful with system apps, some are required for the OS to run properly) but don't install any memory managers or task killers, especially auto task killers. They will only make things worse (slow). Android with full memory runs faster and smoother. Also, don't clear app cache for no reason.

After I bought the phone in 2010, it took me 6 months to build up the nerve to root. Then 2 weeks after that to start flashing.
I went back to stock GB rom at one point and gave up - from my experience,GB is the least stable of the Android versions, bloats the easiest and is overall a lousy system. It;s the armpit of Android, really.
At one point last summer I gave up on Captivate and started using an old iPhone gifted from a friend. At that point the Cappy has 3 hour batter life, nothing worked, and absolutely nothing worked stably - I thought Android was done for, but I was wrong. After about 3 months with the iPhone, I woke up the Cappy, took her back to stock (and I am talking Eclair here) and then forward to CM10. I never looked back. I am currently on yesterday's nightly CM10.1. CM10 Stable was buttery smooth and with no problems at all, but now I am hungry for the new features, so I update the CM10.1 builds about once a week.
This is not to say other builds are not as good. CM is the ROM that revived my Cappy. I am happy with it, it works and is consistently developed with high quality control. I have no reason to switch. But there are many other fantastic-looking roms out there. The Experia roms, the PAC man roms .. they seem to have unique feature sets and stable code.
What I am saying, is that DO NOT stick to stock. And although CM is a great choice, there are many, many options out there .
PS: I have soft-bricked my phone a lot of times. After the first couple times, you will a) learn the value of backing up your data before doing anything, and b) you will have all the files/programs on your computer to revive your phone with a few well-rehearsed steps. (having a backup phone also does not hurt - for a long time I carried the iPhone with me - worried the cappy would crap out on me. I finally stopped worrying)
Best of luck.

dozyaustin said:
After I bought the phone in 2010, it took me 6 months to build up the nerve to root. Then 2 weeks after that to start flashing.
I went back to stock GB rom at one point and gave up - from my experience,GB is the least stable of the Android versions, bloats the easiest and is overall a lousy system. It;s the armpit of Android, really.
At one point last summer I gave up on Captivate and started using an old iPhone gifted from a friend. At that point the Cappy has 3 hour batter life, nothing worked, and absolutely nothing worked stably - I thought Android was done for, but I was wrong. After about 3 months with the iPhone, I woke up the Cappy, took her back to stock (and I am talking Eclair here) and then forward to CM10. I never looked back. I am currently on yesterday's nightly CM10.1. CM10 Stable was buttery smooth and with no problems at all, but now I am hungry for the new features, so I update the CM10.1 builds about once a week.
This is not to say other builds are not as good. CM is the ROM that revived my Cappy. I am happy with it, it works and is consistently developed with high quality control. I have no reason to switch. But there are many other fantastic-looking roms out there. The Experia roms, the PAC man roms .. they seem to have unique feature sets and stable code.
What I am saying, is that DO NOT stick to stock. And although CM is a great choice, there are many, many options out there .
PS: I have soft-bricked my phone a lot of times. After the first couple times, you will a) learn the value of backing up your data before doing anything, and b) you will have all the files/programs on your computer to revive your phone with a few well-rehearsed steps. (having a backup phone also does not hurt - for a long time I carried the iPhone with me - worried the cappy would crap out on me. I finally stopped worrying)
Best of luck.
Click to expand...
Click to collapse
Yep, I'm never going back to stock I'm running slim bean (based on CM) android 4.2.2 and really enjoying all the features, the phone is so much smoother and looks much more professional then GB (no offense google lol).
Thanks,
Nik