Database Develop

[Q] All apps randomly close with any custom rom!!

Foremost, I apologize if this has been asked and answered before. I've been searching for weeks...maybe I'm a bad searcher.
My issue is that I have been experiencing random force closings on random apps, including random partial reboots when unlocking the Unlock screen (screen freeze then goes to Rom intialization screen). Sometimes Dolphin HD closes when loading pages, same with stock browser and Opera Mini, though sometimes the same page will load fine (both with JS on and off and with Flash turned off in Froyo ROMs). Swype (v.2.15) will sometimes close when typing in the search widget or an SMS message in both ChompSMS and stock messaging app. Titanium Backup and Astro sometimes close when scrolling down the app list. The only consistant factor that I can think of is available RAM or the processor overheating.
I have installed multiple ROMs thinking its ROM-specific, but the same behavior manifests in each one. I've tried Assonance 5.2, Cognition 3.04, Phoenix 4.5 and Serendipity 5-1.4.
With each new flashing I first use Odin to get back to stock, then use Odin to Master Clear, then root the phone, then install Clockwork, flash it's recovery app and then use Clockwork to flash the new ROM.
I did fresh installs of any apps I installed from the Market as I know user data from 2.1 will cause issues with 2.2.
Because I thought it was a RAM issue I installed Autokiller Memory and used the 'Optimum' preset.
After all this I still have the same issues with random apps closing and the phone doing ROM reboots when at random times I unlock the phone. Can anyone give me some guidance?

1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.

diablo009 said:
1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.
Click to expand...
Click to collapse
I'll give your ROM a shot.
Stupid question - Do all ROMs have kernels and modems cooked into them? I was just thinking that I've been flashing tons of ROMs lately and I'm not sure of the most stable kernels to have.

Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.

avgjoegeek said:
Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.
Click to expand...
Click to collapse
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?

DRoc740 said:
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?
Click to expand...
Click to collapse
When u restore to stock, format the internal SD from within windows. (Ok, I won't contest anyone's arguments on this, but I personally find it easier than doing a master clear and to wipe off even the basic folders android os format creates.)
And, I would recommend u download a fresh copy of 5.5, with a kernel that does not have any OC in it, to play safe. 5.5 is available in two versions - one with OC kernel, and one with non-OC kernel.
It could be a case of kernel too. Try swapping kernel and see if that helps. Not all kernels go well with all hardware. That's the reason I swapped to xcalibur kernel as soon as I loaded 5.5.
I think, personal opinion here, u could do away with clockwork recovery too. U cud download the cwm console update.zip and put it on ur sdcard root. And apply the update.zip with in console in stock to load up CWM console. This is the most non-intrusive way of going to CWM console as far as I know.

I've been running stock since yesterday with zero issues. My force closing issue usually appears within an hour of flashing a new ROM so this is a very good sign that its a flashing and not a hardware issue.
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Maybe its a kernel issue as I think i've exhausted all other options. I'll try xcaliburinhand's v2.3.2 01.31.2011 and see if it works.
Any other suggestions?

DRoc740 said:
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Click to expand...
Click to collapse
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.

diablo009 said:
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.
Click to expand...
Click to collapse
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?

DRoc740 said:
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?
Click to expand...
Click to collapse
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not now be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.

diablo009 said:
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.
Click to expand...
Click to collapse
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything

DRoc740 said:
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything
Click to expand...
Click to collapse
welcome to the world of flashing. let me (us) know if u need any more help

diablo009 said:
welcome to the world of flashing. let me (us) know if u need any more help
Click to expand...
Click to collapse
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?

DRoc740 said:
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?
Click to expand...
Click to collapse
did you restore anything with titanium backup?

Pirateghost said:
did you restore anything with titanium backup?
Click to expand...
Click to collapse
No, didn't restore anything.
I flashed the update and had the force closings within a few minutes while I was typing an SMS using Swype.

Bumping
I have the same problem

[Q] CWM Restores a perfect restore?

I was wondering how perfect of a restore a CWM restore is.
I was running a custom GB ROM (rocket rom to be exact) and it was running flawlessly. I then decided I might try this new CM9 ICS ROM.
So to be sure about the CM9 install, I figure I'd install from a stock GB Rom. So I first did a CWM backup of my current rocket rom and then I restored an older stock (rooted) ROM. It seemed to work fine. Then.... after reading about the (few) issues wit this new CM9 rom I decided I'd wait a bit longer until a few more of the quirks are worked out.
So I then restored back my Rocket rom backup and even doing the flash cache and davik cache also. But now I notice my once working Rocket ROM is experiencing a lot of SODs.
So now I'm wondering how perfect my restore was. I really don't have a lot of apps or wireless networks and can easily restore my contact list. For that reason, do you think it'll help if I do a factory reset wipe and then reinstall everytyhing....or even go so far as reinstall rocket rom and then reinstall everything else manually without any restores...would that be really the best clean install....or would any of this not make a difference at all and wiping/reinstall a toatl waste of time and my prob is actuaully something else....
Thanks

I could do with knowing the answer to these questions too.
It would be good to get a detailed idiots guide to CWM, do's and don't's etc.

Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything

abhisahara said:
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
Click to expand...
Click to collapse
Sorry for the noob question.... what are SOD's?

adrok76 said:
Sorry for the noob question.... what are SOD's?
Click to expand...
Click to collapse
sleep of death, its the device not waking up properly from sleep

Pus it doesnt include efs, so its not complete backup. Handy if yu stay n same rom version, but thats likely not.
Squicky clean install is always best. Even only app and data recovering thought titanium can mess things up. Make it laggy and nonfunctional etc, Blegh
Sent from my GT-N7000 using Tapatalk 2

1. Install abyssnote42
2. Factory wipe, cache, dalvik
3. Restore your rocketrom backup
That's what i do with my rocketrom v23 backup
Zapped through server hops to XDA forums

its not perfect but its the best so far
all i can say is that cwm is the best and simple thing for me so far and if u get trouble some times while trying to shift from CM9 to normal ics or from gb to ics all I suggest is use redpill recovery from abbysnote

Richy99 said:
sleep of death, its the device not waking up properly from sleep
Click to expand...
Click to collapse
Yeah, mine does that from the clock on Dragon ICS 2.4 when charging it didn't use to, started since I started Dual Booting. 2.5 is out in the next hour or so according to the Dev page. Hope it fixes an otherwise awesome ROM.. Otherwise it's back to single booting and possibly on to Omega 12 until CheckROM is released..

[Q] Captivate shuts off when using an apps after CM10 flash

Hey guys, so i recently updated my phone to CM10 with the Sephamore Kernel. What happens is if i use the phone for anything other than calling or texting it will crash. Any app will make my phone crash after 2 minutes of use. Even texting sometimes kills my phone, when i try and reboot it crashes at the boot animation. Only after i wait for 15+ minutes of off time or plug in the charger does the boot finish.
I've tried reflashing, different kernels, as well as going back to CM9. Still crashes. Battery life stays the same, some times there are random fluctations but it stays relatively stable. Is my battery shot or is the problem with how i flashed the roms?
Sorry if there aren't enough details, let me know what i can do to help solve my own problem
THANKS!

Cabtn said:
Hey guys, so i recently updated my phone to CM10 with the Sephamore Kernel. What happens is if i use the phone for anything other than calling or texting it will crash. Any app will make my phone crash after 2 minutes of use. Even texting sometimes kills my phone, when i try and reboot it crashes at the boot animation. Only after i wait for 15+ minutes of off time or plug in the charger does the boot finish.
I've tried reflashing, different kernels, as well as going back to CM9. Still crashes. Battery life stays the same, some times there are random fluctations but it stays relatively stable. Is my battery shot or is the problem with how i flashed the roms?
Sorry if there aren't enough details, let me know what i can do to help solve my own problem
THANKS!
Click to expand...
Click to collapse
Did you make any mods?
Also, are you using any new apps you didn't before flashing CM10?
Did you factory reset when you flashed CM10?

Alright
1. No i didn't make/or add any mods.
2. The apps i've been using are Facebook, Google Play, Fun Run. Stuff i'm pretty sure should be working.
3. I did a factory reset/User data wipe.
As of now i am back to CM9 stable with the CWM that comes with zip. Still crahes after ~5 minutes of use.

Cabtn said:
Alright
1. No i didn't make/or add any mods.
2. The apps i've been using are Facebook, Google Play, Fun Run. Stuff i'm pretty sure should be working.
3. I did a factory reset/User data wipe.
As of now i am back to CM9 stable with the CWM that comes with zip. Still crahes after ~5 minutes of use.
Click to expand...
Click to collapse
Which version of Semaphore did you flash? Also, are you on CM10.1 or CM10?

I used the nightly build of CM i believe it was CM nightly 20130105 155Mb. The sephamore version i used was the 2.9.8c.
I think maybe my voltage is all messed up? If i just leave it, the phone works just fine, i receive texts and can send them just fine. But the second i try to play pandora or any app just anything with a slight use of memory or even go into settings it dies.
I went to the performance options of CM 9 and tried to bring the cpu down but that just froze it. Maybe a different rom? Flash it back to stock?
Just need a fix until March thats when im due for an upgrade, just let me know if i need a new battery. I might try out the new Lumia or Nexus 4

Cabtn said:
I used the nightly build of CM i believe it was CM nightly 20130105 155Mb. The sephamore version i used was the 2.9.8c.
I think maybe my voltage is all messed up? If i just leave it, the phone works just fine, i receive texts and can send them just fine. But the second i try to play pandora or any app just anything with a slight use of memory or even go into settings it dies.
I went to the performance options of CM 9 and tried to bring the cpu down but that just froze it. Maybe a different rom? Flash it back to stock?
Just need a fix until March thats when im due for an upgrade, just let me know if i need a new battery. I might try out the new Lumia or Nexus 4
Click to expand...
Click to collapse
Alright, that's CM10.1. Just wanted to make sure you were using the right version of Semaphore for it.
You could try changing your governor and scheduler (I think I used SmartassV2 and noop on my cappy). If nothing works, flash back to stock after a good backup is probably the best solution (Odin KK4 without bootloaders). Start fresh from there.

Thanks! I'll give it a try

Sorry one last question. Do you think this would be a good ROM to restore to? Not sure if i have the right bootloaders since i have CM9. Never had to flash back and worry about bootloaders. Thanks!
http://forum.xda-developers.com/showthread.php?t=1285616
If not which from this list would be good?
http://forum.xda-developers.com/showthread.php?t=1300843

Cabtn said:
Sorry one last question. Do you think this would be a good ROM to restore to? Not sure if i have the right bootloaders since i have CM9. Never had to flash back and worry about bootloaders. Thanks!
http://forum.xda-developers.com/showthread.php?t=1285616
If not which from this list would be good?
http://forum.xda-developers.com/showthread.php?t=1300843
Click to expand...
Click to collapse
Odin KK4 without bootloaders: http://hotfile.com/dl/137871658/d25...O_Bootloaders_Re-partition_Full_Wipe.zip.html

[Q] Note 1 - hangs several times a day and slowed down since 4.1.2 upgrade

Hi,
I have recently updated my galaxy note's firmware to 4.1.2. Eversince the upgrade, the phone hangs several times a day and has slowed down drastically.
There is a huge lag even in simple things like typing on whatsapp, clicking a photo, watching a video, playing music files.
I have seen that there are a few others who have experienced similar problem in Note II.
Can someone please suggest me a way to fix this? I am having to restart the phone atleast 6 times everyday.
Thanks
bkgrc

How did you upgrade?

bkgrc said:
Hi,
I have recently updated my galaxy note's firmware to 4.1.2. Eversince the upgrade, the phone hangs several times a day and has slowed down drastically.
There is a huge lag even in simple things like typing on whatsapp, clicking a photo, watching a video, playing music files.
I have seen that there are a few others who have experienced similar problem in Note II.
Can someone please suggest me a way to fix this? I am having to restart the phone atleast 6 times everyday.
Thanks
bkgrc
Click to expand...
Click to collapse
Hi
i have been having the same problem have you found the solution if yes please share it,
i upgraded my galaxy note in February and i have my galaxy note is really slow many time and i have to restart it many times a day...And it gets really hot too.....

Note 1 hangs after upgrade
Hi baz77,
I did the upgrade via samsung kies, connect phone to my PC. few weeks ago.
Thx

system is too heavy on a stock JB rom.. root it and remove some unused apps like chaton , google plus etc etc..

Note 1 hangs after 4.1.2 upgrade
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx

bkgrc said:
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
Click to expand...
Click to collapse
Rooting does void your warranty but the process is relatively simple. Follow 1a method in this guide.

the link rcheung28 has provided is the perfect way / safe way

bkgrc said:
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
Click to expand...
Click to collapse
If ever you have to return your phone to the service center, simply flash an official wipe ROM through PC Odin (that will remove the root and restore the phone to its "original" state). That's what I did when I had to replace mine (I flashed a Gingerbread ROM, made sure the phone booted fine and I was good to go).

nokiamodeln91 said:
system is too heavy on a stock JB rom.. root it and remove some unused apps like chaton , google plus etc etc..
Click to expand...
Click to collapse
What if I just disable the app instead of root delete? Any idea which app can be disabled without affecting phone normal operation? Thanks

i wonder if restoring factory settings will result to improvements..
and if it is safe now using the JB kernel?..

jaycm1130 said:
i wonder if restoring factory settings will result to improvements..
and if it is safe now using the JB kernel?..
Click to expand...
Click to collapse
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:

devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
I haven't used a stock ROM for while, not because of battery drain (which is mostly app-related and can be checked with BBS), but because it was sluggish compared to CM.
As for the media scanner issue, you can try this app.

devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
did you tried stock kernel?
what is your feedback to it?..
i was wondering if the stock kernel for DXLSE was safe to do factory reset..

jaycm1130 said:
did you tried stock kernel?
what is your feedback to it?..
i was wondering if the stock kernel for DXLSE was safe to do factory reset..
Click to expand...
Click to collapse
Was on stock when I did the factory reset before flashing Philz. Nothing happen to my phone but I cant confirm that nothing is wrong. Maybe its because I got away with it. But I can only let you know that I did the reset on stock JB DXLSE Rom and kernel.
Even after doing the reset. Can still notice the batt drain and sometimes some apps can hang. Theres some laggy interface. Isnt as smooth as when I was on ICS 4.04.

devll said:
Was on stock when I did the factory reset before flashing Philz. Nothing happen to my phone but I cant confirm that nothing is wrong. Maybe its because I got away with it. But I can only let you know that I did the reset on stock JB DXLSE Rom and kernel.
Even after doing the reset. Can still notice the batt drain and sometimes some apps can hang. Theres some laggy interface. Isnt as smooth as when I was on ICS 4.04.
Click to expand...
Click to collapse
maybe the custom kernel that you installed eats a lot of battery and/or the apps that you installed consumes resource even on the background..
try all stock kernel and rom.. let it settle for a week..
try also to replace the battery..
now if you insist in custom kernels, due to the fact that they are proven safe and has working CWM..
try tweaking with the settings.. through its governors,,
try debloating your rom by removing unnecessary bloatwares..
see if either any of this make sense to your device..

jaycm1130 said:
maybe the custom kernel that you installed eats a lot of battery and/or the apps that you installed consumes resource even on the background..
try all stock kernel and rom.. let it settle for a week..
try also to replace the battery..
now if you insist in custom kernels, due to the fact that they are proven safe and has working CWM..
try tweaking with the settings.. through its governors,,
try debloating your rom by removing unnecessary bloatwares..
see if either any of this make sense to your device..
Click to expand...
Click to collapse
Philz kernel is stock kernel with brink bug removed. So basically its a stock one.
For settings. I managed to set it as the same when Iam on ICS 4.04. For bloatware, all are disabled. Practically I set it as the same when Iam on ICS 4.04. Thats why Iam sure the batt drain and slight lag is there.
Hopefully someone here have a solution to it. :fingers-crossed:

devll said:
Philz kernel is stock kernel with brink bug removed. So basically its a stock one.
For settings. I managed to set it as the same when Iam on ICS 4.04. For bloatware, all are disabled. Practically I set it as the same when Iam on ICS 4.04. Thats why Iam sure the batt drain and slight lag is there.
Hopefully someone here have a solution to it. :fingers-crossed:
Click to expand...
Click to collapse
Philz kernel is stock based kernel not a stock one..
try this app: https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en

devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
One thing that I've noticed that I haven't heard people talk about (maybe because it's stupid and non-applicable) is to go into your DCIM folders, both on your SD and in the phone and delete the entire .thumbnails directory. Mine somehow managed to accumulate a good GB or so of thumbs and that appeared to be bogging down media searching.
Even after that, phone has been really laggy lately. Going into running apps, I noticed a "Software Update" process running, even though I know this phone will not OTA update. Killed that process and things were ok again. YMMV.

[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