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

[Q] Stuck in bootloop - What should I do?

Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961

Hi there,
Bootloops happen every now and then, if something collides or is misconfigured.
In my very own experience most boot loops happen to be script related.
This is why you should´t worry too much.
You still can enter CWM?
If so enter CWM and wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If it still is in boot loop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodels which slightly differ from original)
In case you do not have a rooted device without CWM only thing you can do, is to begin from scratch by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device including you´ll keep all your private stuff.
Flashing the Samsung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #

DJ-Tumor said:
Hi there,
Bootloops happen every now and then, is somethine collides or is misconfigured.
In my very own experience most boot loops happen to be skript related.
This is why you should´t worry too much.
You still can enter CWM?
If so Enter CWM, wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If ist still is in bootloop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodel which slightly differ from originall)
In case do not have a rooted device without CWM only thing you can do, is to begin from scrath by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device incl. you keep all your private stuff.
Flashing the Sasmung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #
Click to expand...
Click to collapse
Have done as you said, but still problems.
One of the problems maybe can be that it isn't CWM but RedPill.
Yes, I did download the whole file, so no strange abort of the download.
And this is the correct ROM for the Galaxy Note.
If I still have this problems in 24 hours I will contact my store and let them know what I think. I want my money back. I can also add that I'm studying law, so I let the lawbook speek for itself.
But thanks for a fast answer!

Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of

DJ-Tumor said:
Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of
Click to expand...
Click to collapse
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?

MinnesotaVikings1961 said:
Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961
Click to expand...
Click to collapse
You need to flash rocket rom v20 before v22 that i belive is or problem if u can mount sdcard to computer u may have to take sdcard out of your phone and put in something else to load the program on the card then put back on phone and then flash v20 of rocket rom and then see if it boots up if it dose then u can flash v22
Sent from my GT-N7000 using XDA Premium HD app

Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?[/QUOTE]
U could in download mode with odin pc
Sent from my GT-N7000 using XDA Premium HD app

Quick google search shows boot loops are pretty well known with this rom.
No you only can flash original rom with odin.
If there are important data on the device connect it cia usb and boot into cwm.
Now wath what happens. If you´re lucky mass storage mode is enables in the kernel and you got your storage mounted automated.
If not it´s time to cross fingers and search for an option to mount by hand.
I´m completely new to NOTE - all my knowledge comes from my i9000 which is a mega active community compared to the one of the NOTE
There is have the choice between 5 different ICS kernels alone
Each one has it´s abilities, so does one have the option to mount storage by hand.
This option can be found in "advanced". Hope this menu option is present in your rom
good luck!
# Rodger #

MinnesotaVikings1961 said:
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?
Click to expand...
Click to collapse
Yeah you can. Just go to this thread. Get a rootable rom downloaded. Just follow the instructions to the word of how to flash via odin. And you will have stock rom. And you can again root and install custom rom!! No need to run back to store !
Links-
Roms and guide- http://forum.xda-developers.com/showthread.php?t=1424997
Rooting and odin - http://forum.xda-developers.com/showthread.php?t=1329360

Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?

chasmodo said:
Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?
Click to expand...
Click to collapse
Well, I had been using ICS MidNote for a short time, due to a friend mine wanted to see ICS for the Note.
Now I tried to get back to my regular GB ROM.
/ Jimmy

You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6

chasmodo said:
You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
Click to expand...
Click to collapse
Sorry for being confusing you!
Before this bootloop I was running MidNote V2.0, ICS. I then tried to flash ROCKET ROM, V22. And when I started up, this bootloop came up, and isn't solved in writing moment, very many hours later.
/ Jimmy

Case closed
I can now say that the case is closed. What I did is very simple. In fact, so simple I never thinked about it. The only thing I did was to unroot my phone using Odin.
But thanks for all tips and support!
/ Jimmy

Returning to a 'Virgin' Clean System

So..
I've been playing around for a while with kernels, ROM's and so on... And I've made a decision to return the beast to it's virgin state..
Intentions are as follows;
- Flash Stock GB Firmware (Via PC Odin)
- Format internal / External SD
- Wipe cache / Dalvik
- Update to ICS 4.0.3 (Probably just do it OTA or I have the Odin file)
- Root
- Install Mobile Odin
- Install preferred kernel
From the above, Anyone have any additional advices?
Cheers

you missed out the biggest one, Factory reset :silly: lol
Obviously you just forgot to add it in
But other than that, That sounds spot on ! thats exactly the same procedure I do except reverting to GB you could just wipe on a safe kernel

azzledazzle said:
you missed out the biggest one, Factory reset :silly: lol
Obviously you just forgot to add it in
But other than that, That sounds spot on ! thats exactly the same procedure I do except reverting to GB you could just wipe on a safe kernel
Click to expand...
Click to collapse
I still find it hard to believe there are such things, even the kernel devs hesitantly use the term "SHOULD" ..
And yep, Factory reset should have been included

I dont follow ??
Anyway, Safety is the main thing and if you feel safer reverting to GB then thats fine, it only takes <10mins to flash and could be the difference between a clean note and a bricked note
ive wiped lots of times on my current kernel so i know it to be safe.

azzledazzle said:
I dont follow ??
Anyway, Safety is the main thing and if you feel safer reverting to GB then thats fine, it only takes <10mins to flash and could be the difference between a clean note and a bricked note
ive wiped lots of times on my current kernel so i know it to be safe.
Click to expand...
Click to collapse
You still running NoteCore?
I've got SpeedMod K3-9 installed on the ICS build at the moment but as you say - it's not an epic task and for super safety I'm happier wiping and formatting in GB...

I was until about 5 mins ago lol, Im just in the middle of flashing Staxxtanium
I just fancy a change lol its been a while, no doubt il be back to cleanote tomorrow but i have to satisfy the cravings

azzledazzle said:
I was until about 5 mins ago lol, Im just in the middle of flashing Staxxtanium
I just fancy a change lol its been a while, no doubt il be back to cleanote tomorrow but i have to satisfy the cravings
Click to expand...
Click to collapse
I was looking at that myself after dabbling in the PA World.. let me know what you think..

I sure will !
I really liked PA, But i was new to the Note at the time and liked the S-Pen features and apps, Now i dont really use them as much but only stayed with CleaNote to support the dev (im loyal like that )
But i get these urges to flash (in more ways than one ) and i havent flashed anything except a kernel for a few days now.

OK ran in to an issue - is standard recovery there's no format options available...hmmm
Maybe flash Abyss?
Ahh.. that's right, it's in settings ^o)

yeah flash abyss or any other CWM containing kernel, The stock one is a bag of sh!te

azzledazzle said:
yeah flash abyss or any other CWM containing kernel, The stock one is a bag of sh!te
Click to expand...
Click to collapse
Managed to clear the storage int/ext from settings so will set off on the root to gettin back to where I was..Just without SpeedMod K3-9 as Wi-Fi is unstable on that..

JBroid
Question re: Jbroid Kernel cleaning script..
- Is it worth running following the above?
- If so, can I run it under ICS ( Flash Abyss > Jbroid > Flash Kernel of choice > Reboot)?

Well that went well..
Now jus need to figure out a kernel and I'm "Back in the game"

[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