Database Info

Random restarts

Would a kernel or a ROM be responsible for random restarts? I ask this because I feel it is my duty to inform the developer.
Droid Charge
0731 PBJ
Altered Beast 5

ZepHed69 said:
Would a kernel or a ROM be responsible for random restarts? I ask this because I feel it is my duty to inform the developer.
Droid Charge
0731 PBJ
Altered Beast 5
Click to expand...
Click to collapse
If you did not wipe data or caches, that could be your culprit. Anyways Altered Beast is a pretty old ROM and has not been updated in a while. There are more recent kernels than that too. Reflash and it should fix your problem.

Good point, although I like the theme, colors, and stuff, it is getting old. What do you suggest for kernel and ROM....I'm ready to try a new combo.
Droid Charge
0731 PBJ
Altered Beast 5

ZepHed69 said:
Good point, although I like the theme, colors, and stuff, it is getting old. What do you suggest for kernel and ROM....I'm ready to try a new combo.
Droid Charge
0731 PBJ
Altered Beast 5
Click to expand...
Click to collapse
Gummycharged.
Sent from my SCH-I510 using XDA Premium App

And Imoseyon's kernel.
Sent from my SCH-I510 using XDA Premium App

i had this issue on gummy 1.8.5. phone would randomly restart every day or two. switch to his GB rom and its gone.

ZepHed69 said:
Good point, although I like the theme, colors, and stuff, it is getting old. What do you suggest for kernel and ROM....I'm ready to try a new combo.
Droid Charge
0731 PBJ
Altered Beast 5
Click to expand...
Click to collapse
I was on AB when I first came to the Charge (my first smart phone). I Odined over GummyCharged 1.9.1 FE and never looked back. Now I'm part of Team GummyCharged as thread support. I came a long way. Lol.
Check out the developer forum.

Use gummy, eclipse or stock debloated. Gummy has nothing that intrigues me until they release 2.0, stock debloated is cool if you just want a good stock rooted experience and eclipse is a really nice looking version of stock, themed after touchwiz 4. As for the kernel? Just use the latest PBJ non-otb for best battery life.
Sent from an awesome phone using an awesome app.

I have a stock Droid Charge and mine randomly restarts too sometimes, and I've only had my phone a week.

I experience these random restarts a lot when I am using a custom ROM/kernel.
Doesn't matter what ROM I try the random restarts happen. I always wipe factory setting, cache, and dalvik cache before each install.
When I revert back to stock the problem goes away.
If anyone has more info on why these random restarts happen that'd be great.

Have you undervolted? Undervolting by too much seems to be the main cause of freezes and restarts for me.
Sent from my SCH-I510 using XDA App

asxa86 said:
I experience these random restarts a lot when I am using a custom ROM/kernel.
Doesn't matter what ROM I try the random restarts happen. I always wipe factory setting, cache, and dalvik cache before each install.
When I revert back to stock the problem goes away.
If anyone has more info on why these random restarts happen that'd be great.
Click to expand...
Click to collapse
Do you use Titanium Backup? Overclock or undervolt at all?

I noticed if I keep flashing without going back to stock first it happens to me as well. No matter what kernel. I also wipe and clear setrings
Sent from my SCH-I510 using XDA App

Same questions that I asked asxa86. Give me some info to work with please.

Well I mainly used GC w/PB&J which undervolts. So I was thinking my processor just couldn't handle the undervolting but then I just tried GC 2.0 recently which uses a new kernel and I'm still getting the random restarts.
I actually went to verizon today and got them to send me a replacement phone to see if i'm having hardware failure. Which doesn't make sense unless these custom ROMs/kernels are stressing my system more than stock would...
To answer the original question, i do not use titanium back up.
This is my process:
stock ED1 + PIT file flashed with odin
OTA EE4 update
Phone runs completely fine other than the usual laggyness of the stock phone
-root phone using ED1 root flashed with odin
-CWM flashed with odin
-factory rest, cache, and dalvik cache wipe
-install through CWM GC 2.0
everytime there is a new GC I get excited and flash the new ROM to my phone only to experience the random restarts the next day

Well, see if your replacement likes everything better, then you'll know it was your hardware.
Sent from my Droid Charge running GummyCharged 2.0

Ok, replacement phone came in today. I am reverting my old phone back to stock so it can be shipped back to verizon. Once I have my new phone up and running I will install gummycharge and see how everything works.
Just to be safe I had installed gummycharge 2.0 on my old phone and like I thought it would it ended up restarting itself x2 yesterday.

So having acquired the replacement phone and installing GC 2.0 FE on it. The phone went almost a full day with out restarting itself...
Don't know what to do now.

asxa86 said:
Well I mainly used GC w/PB&J which undervolts. So I was thinking my processor just couldn't handle the undervolting but then I just tried GC 2.0 recently which uses a new kernel and I'm still getting the random restarts.
I actually went to verizon today and got them to send me a replacement phone to see if i'm having hardware failure. Which doesn't make sense unless these custom ROMs/kernels are stressing my system more than stock would...
To answer the original question, i do not use titanium back up.
This is my process:
stock ED1 + PIT file flashed with odin
OTA EE4 update
Phone runs completely fine other than the usual laggyness of the stock phone
-root phone using ED1 root flashed with odin
-CWM flashed with odin
-factory rest, cache, and dalvik cache wipe
-install through CWM GC 2.0
everytime there is a new GC I get excited and flash the new ROM to my phone only to experience the random restarts the next day
Click to expand...
Click to collapse
I am experiencing the same issues on Gummy 2.0
My install method is:
Odin 1.9, boot to configuration, then cwm Gummy 2.0.
When I was previously on the Gingerbread Gummy I did not have this issue.

I have been experiencing this issue since I first began doing theses flashes.
I started with gummy 1.8.1 have tried other ROMs and even Gingerbread ROMs. It never fails. I get random restarts. I asked verizon for a replacement phone, got one and tried flashing again....random restart.
My process I stated above.

Replaced battery now FC galore.

When i picked up my charge i also got the desk cradle with the extra battery. Yesterday at work i was listening to music and drained the battery pretty quickly so i swapped in the extra battery. Once i rebooted i started getting a bunch of FC's. I'm getting ones for Google Services Framework, messaging, android.processes.acore and one or two others i can't remember. I reflashed GC and still get the errors. Anyone have any idea why this would happen after swapping batteries and how to fix this?
Sent from my SCH-I510 using XDA App

It just happens sometimes. Ill have to do this once every 3 months or so. Hope you made a backup...If you have the EXT4 formatter saved then just mount all in CWM, wipe all user data, dalvik, cache, etc. Then run EXT4 formatter, then flash GC. If you don't have it, you have to restock with the EE4 Odin and PIT, then reflash GC.
Sent from my Droid Charge running GummyFroyo 1.9.1

Happened to me a week or so ago, huge pain because I hadn't backed up in a while but it took me about a day or two to get all my apps back in order. In all honesty though it was one of the most annoying things that could happen. Had to redownload a ton of my apps and all the apps I had backed up were outdated(like ColorNote, I lost like 4 notes because it was an old backup). Happened totally out of the blue, I just rebooted the phone because apps weren't installing and I got spammed with FCloses. Not even a factory reset/cache/Dalvcache worked I had to flash the .pit/ee4factory.md5 to get my phone working again. PAIN IN TEH ASH.

Well son of a batch of cookies. That was my last resort but i suppose i will give that a shot this evening and report back to ya.
Sent from my SCH-I510 using XDA App

I finally got around to restoring my phone using the EE4 ODIN. I had no idea it was going to take over an hour to do, lol. Anyway, the flash completed and passed so I unplugged the USB cable, pulled the battery, but now I can't get the phone to turn on. Is there something else that I screwed up?

Lockett said:
I finally got around to restoring my phone using the EE4 ODIN. I had no idea it was going to take over an hour to do, lol. Anyway, the flash completed and passed so I unplugged the USB cable, pulled the battery, but now I can't get the phone to turn on. Is there something else that I screwed up?
Click to expand...
Click to collapse
It should have not taken an hour. If you flashed without the battery try flashing again with the battery in.
Also make sure you are using the PDA button.. not phone. Flash will show pass if you use phone but it will not boot.
Sent from my SCH-I510 using XDA App

Yep that was the mistake i made. I was in a rush to get my phone back up and running before i went to sleep that i accidently used the phone option. I reflashed using PDA and all is well. Now i just have to reroot.
Sent from my SCH-I510 using XDA App

I dont know if you were rooted and on a rom already but for future ref., when this happened to me I just went into CWR, fixed permissions, wiped cache and dalvik, rebooted and bam the FClosing stopped. my wifes phone on the other hand I had to just go into CWR and flash the rom over again and it cleared the problem rather than going through ODIN.

jrock7885 said:
I dont know if you were rooted and on a rom already but for future ref., when this happened to me I just went into CWR, fixed permissions, wiped cache and dalvik, rebooted and bam the FClosing stopped. my wifes phone on the other hand I had to just go into CWR and flash the rom over again and it cleared the problem rather than going through ODIN.
Click to expand...
Click to collapse
I was rooted and running GC 1.9.1. I went into CWR and tried wiping just the cache and dalvik as well as flashing the rom again and I couldn't get the FC's to stop. Thanks for the info, I'll keep this in mind next time this happens.

I was on GC 1.9 when my mega galore of FC's started happening too, my end result was a replacement phone from Verizon... I really don't know what happened or why. It just randomly happened under normal use.

Wow, that kinda sucks. They didn't say anything about the phone being rooted? They gave me hell for trading my rooted D2G for my charge.

Lockett said:
Wow, that kinda sucks. They didn't say anything about the phone being rooted? They gave me hell for trading my rooted D2G for my charge.
Click to expand...
Click to collapse
No because I flashed a bone stock ED1 with no root and nothing at all on the phone, I even had a blank 2GB SD Card in it.

Same happened to me. Yesterday I just clicked on camera and got a force close, then froze. Pulled battery, then everything was force closing. Only thing that would function was browser. Flashed everything, wiped data, you name it. Nothing has worked for me.

Happy! said:
Same happened to me. Yesterday I just clicked on camera and got a force close, then froze. Pulled battery, then everything was force closing. Only thing that would function was browser. Flashed everything, wiped data, you name it. Nothing has worked for me.
Click to expand...
Click to collapse
Just do what I said.
Sent from my Droid Charge running GummyFroyo 1.9.1

Did the rom you were running have journaling turned off by default?? If so, any improper shutdown will result in data corruption.
Sent from my SPH-D700 using xda premium

And I second clearing the cache and dalvik.
Sent from my SPH-D700 using xda premium

nismology said:
And I second clearing the cache and dalvik.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
When I had this problem clearing cache and dalvik didn't help at all.
Sent from my Droid Charge running GummyFroyo 1.9.1

kvswim said:
When I had this problem clearing cache and dalvik didn't help at all.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
It depends on the level of data corruption I suppose. As an aside, roms should really be released with journaling enable or at least have that option. The slight speed increase is not worth the hassle IMO.
Sent from my SPH-D700 using xda premium

When it happened to me one the first things I tried was wiping cache and nothing worked. If you follow kv's advice and that doesn't work then the only other method would be to odin back to stock and start fresh. I did have one fc for android.processes.acore but I can't remember what I did to cause or replicate it. The only thing I'm having trouble with now that I rerooted the phone is that I cannot get back into CWR. I flashed the latest version and was able to get in to flash gc and everything else but now when I try to get in it locks up on the samsung logo.
EDIT: I wasn't able to get past the Samsung logo no matter what I tried. I ended up having to odin back and start fresh....again.
Sent from my SCH-I510 using XDA App

nismology said:
It depends on the level of data corruption I suppose. As an aside, roms should really be released with journaling enable or at least have that option. The slight speed increase is not worth the hassle IMO.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Is there any way to re-enable it?

[Q] Faux kernel problem

This just started when i tried to switch my DS faux kernel to CM. I wiped my phone data and cache to flash the newest stable CM7. And since the DS kernel 0.4.1 was giving me really funky battery readings, i decided to go with CM 0.4.3. So i flashed the newest CM7 (again, not nightly) and then proceeded to flash the kernel. Once all was finished i rebooted the phone and the LG logo appeared for about 3 seconds then the screen went black. I waited for about 10 minutes but no changes. What happened?

stevan6 said:
This just started when i tried to switch my DS faux kernel to CM. I wiped my phone data and cache to flash the newest stable CM7. And since the DS kernel 0.4.1 was giving me really funky battery readings, i decided to go with CM 0.4.3. So i flashed the newest CM7 (again, not nightly) and then proceeded to flash the kernel. Once all was finished i rebooted the phone and the LG logo appeared for about 3 seconds then the screen went black. I waited for about 10 minutes but no changes. What happened?
Click to expand...
Click to collapse
Had this happen once. I rebooted to recovery, wiped cache and dalvik, reflashed my kernel, fixed permissions then rebooted. Everything was fine afterwards.
Sent from my LG-P999 using xda premium

worked like a charm, Thanks a lot!

stevan6 said:
worked like a charm, Thanks a lot!
Click to expand...
Click to collapse
Glad I could help.
Sent from my LG-P999 using xda premium

Battery status always 100% after flashing HellFire Sandwich v1.9

Hello my name is Alex and I am from Germany, Bavaria.
I'm new here and would like to apologize for my bad english at the beginning.
Since 2 weeks I'm the proud owner of an LG G2x P999 smartphones.
I've flashed directly with the Hellfire Sandwich v1.9 ROM.
That also works without problems by the good instructions.
Now I have the problem that the battery indicator is always set to 100% and does not change anymore.
Can someone help me here?
Thanks in advance.

Hodanflechta said:
Hello my name is Alex and I am from Germany, Bavaria.
I'm new here and would like to apologize for my bad english at the beginning.
Since 2 weeks I'm the proud owner of an LG G2x P999 smartphones.
I've flashed directly with the Hellfire Sandwich v1.9 ROM.
That also works without problems by the good instructions.
Now I have the problem that the battery indicator is always set to 100% and does not change anymore.
Can someone help me here?
Thanks in advance.
Click to expand...
Click to collapse
Your English is fine and did u wipe ur data factory reset, clear cache partition, and clear dalvik partition because I know not clearing it can cause problems. If not try that and see what happens. Also how long has it been at 100% are you using it a lot too?
Sent from my LG-P999 using xda app-developers app

Laxshanth said:
Your English is fine and did u wipe ur data factory reset, clear cache partition, and clear dalvik partition because I know not clearing it can cause problems. If not try that and see what happens. Also how long has it been at 100% are you using it a lot too?
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply.
Here the order of my wipes:
1) data and factory reset
2) wipe cache
3) wipe dalvik cache
4) wipe battery statistic
The battery charge level indicator shows always 100% until the phone turns of because an empty battery.
If i charged the phone to 100%, i have the same problem as before.

Always having 100% Battery sounds like a good thing to me!! :laugh:
What version of clockworkmod (how did you flash it), are you running and are you flashing any custom Kernels?

Nexus S 4g Will Not Stop Rebooting

Hi,
I recently have flashed some new roms on my phone. So heres what happened... I had been using MIUI for months now for my NxS4g but the MIUI rom was just getting too laggy for me for daily use. So then I flashed Factory Rom. Worked good for a while then it started this rebooting randomly.. I Did Full Wipe, Format etc before flashing.. It seems fine while using it but once I turn the screen off and let it sit it just starts to randomly reboot. So I thought oh well its just the rom. Then I went back to MIUI and flashed the new Miui 2.10.26.2 which is a great running rom and I thought it fixed my problem because I spent an hour or 2 installing fresh new apps from the market, didnt restore anything or flash a custom kernel everything was stock and all fresh new apps. So I went to bed woke up at 6am like usual and noticed my phone had stopped responding... had to take the battery out and boot it up.. sometimes it does that and i have to pull the battery and sometimes it fully reboots. So now I am stumped ive tried everything i know. full format/wipes, fixing permissions, wiping dalvik and cache, and still not working! I hope my phone isnt dying or something. It was working fine. Please if anyone has a fix or knows what to do please help me! The only thing I haven't done is formatted my SD card which is what im about to try.
Thanks in Advance!
Adam

Hi,
What factory ROM?
Every ns4g responds to different kernels differently...maybe the newest version of that ROM u installed had a different kernel that sometimes causes many random reboots... so check that plz.
But u say udid a factory reset and stuff... did u wipe Dalvik and cache? Cuz that is important.
Good luck
Vs Nexus S4G using tapatalk2