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.

[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

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

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] 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