Related
So as the title states, my Epic has been plagued by random reboots since installing EG22. The unit was a new replacement, not a refurbished replacement that tech support normally gives. I've had it all of four weeks now. It ran EF02 pretty perfectly. I have tried reloading EC05 (with ODIN) then loading EG22, and no dice. Before I flash EG22 I wipe the phone, cache, and dalvik 3 times. I've also redownloaded and hash checked the EG22 update I use (using the stock/deodexed EG22 update.zip from the development forum). Still no improvement, the phone will randomly reboot every 1-2 hours. Any advice on what I could try next is appreciated.
radugb out
UPDATE: also I cannot get into the "SYSTEM UPDATES" menu in the Settings/About Phone menu. Each time I try I get a forced close then a system reboot. Could the phone just not like EG22?
I have experienced reboots on both EE03 and EF02. I haven't tried EG22 as of yet. I hae never had it happen on EC05. I figure I'll just wait until the release because my phone just doesn't like the beta/leaked stuff.
Any test software has a chance that it will not work 100%
All Gingerbread leaks crash and reboot in low signal areas. I am assuming this is one of the reasons official hasn't been released yet.
Sent from my SPH-D700 using XDA App
Ok, but one I have an airave about 12 ft away from my phone so I get a great signal. And two, I'm still getting FC's when I try to enter the system updates menu. So I still think it could be something wrong with my phone.
radugb said:
Ok, but one I have an airave about 12 ft away from my phone so I get a great signal. And two, I'm still getting FC's when I try to enter the system updates menu. So I still think it could be something wrong with my phone.
Click to expand...
Click to collapse
How did you install EG22? If you did it through CWM it could have just been a bad flash. For the system menu problem. The crashes occur for me too, like above post low signal areas are not a gb leaks friend.
Sent using TouchPal Curve Input
I have been flashing zip versions thru CMW. I'll look up an ODIN-able EG22 tar or md5 and try it that way. But I will ODIN back to EC05 (with repartition to wipe the phone) then update to EG22. I'll let you all know.
As far a signal goes though, I'm getting full bars right now because my Airrave is so close to me.
radugb said:
I have been flashing zip versions thru CMW. I'll look up an ODIN-able EG22 tar or md5 and try it that way. But I will ODIN back to EC05 (with repartition to wipe the phone) then update to EG22. I'll let you all know.
As far a signal goes though, I'm getting full bars right now because my Airrave is so close to me.
Click to expand...
Click to collapse
You are right, that shouldn't happen with an Airave. A reflash may fix the issues you are having. Also don't use any CPU managers like SetCPU or Voltage Control on GB until source code and custom kernels show up.
Sent from my SPH-D700 using XDA App
Yup. That was it. Bad flash. This time I d/l'ed a .tar version of EG22 to flash with ODIN. Much better than before. No more FC's from the system menu and its been running 8 hours straight with no reboots. Muchas garcias.
radugb out
Glad to help.
Sent from my SPH-D700 using XDA App
Spoke too soon. I've had two random reboots, one yesterday, one today. So it definitely fits with what all y'all said that leaked GB ROMs tend to crash. Still not as bad as before, and I no longer get the FC's from the system updates menu.
I had one last night and one tonight at my house which I get a crap signal at in what Sprint describes as an "excellent coverage area" No other problems anywhere else.
I've had my first random reboot. Phone was WIFI connected, and forced roaming (Sprint has a tower down in my area, going on 7 days now). It was in the middle of a content update for an application I run, so I'm wondering if there is a memory leak for the network user or kernel space.
Does anyone know of an application that will keep a log of memory usage to track if a process is not releasing its resources?
Yup, same here. About once every two days I get a reboot. I haven't been able to connect anything I'm doing to the reboots, and it usually does it while the phone is just sitting.
Trouble is, Gingerbread is soooo much better than Froyo I don't want to go back
I really think it is the modem crashing.
You may want to try another modem.
also, i realised that on my wife's epic with eg22, it rebooted about 5 times a day, most of the time, it was right after using the slide out keyboard.
i deleted the keyboard counter slide apk thingy, since then, 1 reboot a day.
not great, but definitely better than 5.
x130844 said:
I really think it is the modem crashing.
You may want to try another modem.
also, i realised that on my wife's epic with eg22, it rebooted about 5 times a day, most of the time, it was right after using the slide out keyboard.
i deleted the keyboard counter slide apk thingy, since then, 1 reboot a day.
not great, but definitely better than 5.
Click to expand...
Click to collapse
Are you sure it is not a loose battery connection? My phone would do that with the extended battery and case. Had to put a little piece of thick paper in there to hold it tighter.
Definitely was the modem. I flashed the EE02 modem & now no random reboots. Signal(s) & battery life have gotten better too. I would have flashed the EF02/EF10 modem but that downgrade notice is oh so damn annoying!
Me and my friend have the same issue on our Epics OP, Its annoying but Im dealing with it cause these roms are so much better than pre eg22.
I dont have any random reboots but I get a random double vibrate. I have no idea where that is coming from
I've had two random boots since I've odin'd from EC05.. though I feel it was memory leak,and the phone just shutdown without sufficcient ram.
SchizioPunk's Epic Experience 2.1 Eclair -> Odin to EC05 Froyo. Rooted. Bloatware Removed. Voodoo Sound V9 Module Loaded. TouchWiz4. Enjoying my Customized Stock Experience.
Yeah well I tried the EH06 modem and it broke the 4G (amongst other things). So I got ol' reliable EE03 to fall back on.
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
bbecker42 said:
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
Click to expand...
Click to collapse
The force closing is probably due to not having Journaling on.
I believe in the SRF 1.2 OP, there is a JournalingOn.zip, flash that (no wipes) and that should stop the force closing.
If it still is unstable for you, I recommend just reflashing the ROM.
Hope this helps.
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
nikon120 said:
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
Click to expand...
Click to collapse
Exactly right
Sent from my SPH-D700 using XDA Premium App
I had friend who had the same issue. He went back to SFR1.1.1
then installed ACS updater and flashed SFR 1.2. That fixed his problem. I did it that way too and have not had any issues. Calibrate battery after flashing.
Sent from my SPH-D700 using XDA App
That sort of worked. It made it take longer for things to get hosed over again.So I tried resetting it to stock then flashing EG22, but each time I flash EG22, it doesnt do anything.The version stays at 2.2.1. What am I doing wrong?
What did you flash that is EG22?
Sent from my SPH-D700 using XDA Premium App
In order to better assist you, can you give us a step-by-step listing of everything you are doing? The files you are using with version #'s and your computer OS (with bit version).
I would recommend a full wipe of the phone, to remove any corrupted data
then do a clean install of SRF 1.2
then install the zip to turn on journaling
note: DO NOT use the reboot option until AFTER you have turned on journaling
What I did last night was returned it to factory stock EC05.
Im working with Windows 7 Home x64 on a Mac Pro, because for some reason neither Epic I've ever had will work with my custom built computer.
I flashed the EG22modem.bin with Odin 1.61. That didnt seem to do anything.
So later today, I am going to try this
http://forum.xda-developers.com/showthread.php?t=1184134
The modem only changes the baseband..
regardless, imo it sounds like the problems you are having are due to restoring backups.. is that the case?
I installed this
http://forum.xda-developers.com/showthread.php?t=1205024
and everything is hunky dory in the hood. Thanks for all the help
I am very new with flashing a rom. I have flashed mkasick's kernal over the samfirmware release and now Toad's amazing rom. I am experiencing unusual results on both. Out side of reading the threads and watching for updates, is there something else I should be doing? I have checks relevant threads every day for the last week or so. I am beginning to think I may need a new epic. I will reodin this thing again to see if the results improve, but I have the ever discouraging feeling I may need to go back to Froyo. Stock unrooted Froyo for me had reboots and shut downs more than any other rom since but at least I knew when my phone shut down. Any suggestions to help me out would be much appreciated. Thanks!
You did it wrong. The kernel goes after the ROM.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
You did it wrong. The kernel goes after the ROM.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I see my written english is just as terrible late at night as it is during the day. What intended to state was that I have flashed 2 roms in my time with my epic. First the Samfirmware one along with that amazing kernal and more recently I have flashed Toad's rom. I did not mean I flashed a kernal first (though I almost did try by accident the first go).
At this time, I am still having issues. I know this odin, like most, contain everything (as toad stated many times in his thread), but I lack confidence that I didn't miss something obvious. I flashed odin with the pit file as stated and removed the md5 extension before doing so. If any other details would be helpful to know, I would be glad to provide them.
What are the exact issues you are seeing?
Sent from my SPH-D700 using XDA App
Post my second Odin'ing, I have only had a few app issues. For starters the 'My Files' was gone until reboot. Upon a reboot, I had a random android icon in my app drawer that didnt correspond to any particular app and stated it was missing (whatever it was). That is it as of now. On the first odin'd usage, I had freezes where the phone would make the startup sound and even the sprint screen would flash but I could use the screen button to turn the screen on and off during this. I had other random freezes where screen would just look up on the home screen and another where I had full function, but the status bar no longer existed. Last night before I flashed again, I had some screen tearing right below the status bar. I have not been able to reproduce any of the errors, but I suppose my epic may just hate me. Thanks for taking the time to ask.
There are apps that some ROM builders take out for bloat or to make room for superuser and busybox (rooting). These may be Sprint TV, Asphalt, TeleNav and others. Once you figure out which app you are missing we can help you get it back. Some also remove myfiles but I see yours came back. This is a good reason to run Titanium backup before flashing anything. You can restore missing apps with it.
I am running Titanium as we speak. I never realized the difference between that and App Backup & Restore. Night and day there... Thanks again for the help.
I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?
TheManCalledX said:
I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?
Click to expand...
Click to collapse
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.
That's the min for gingertiny right? If so, then yes. But I've literally never run into this problem since going from CM back to Sense. Never once had it happen during all my different Sense ROM flashes. Could it be something to do with the way CM does it's storage tree vs sense? I'm at a loss right now and just want some ideas on what to look into.
Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?
TheManCalledX said:
Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?
Click to expand...
Click to collapse
Flash amon ra recovery from rommanager. Then go into the recovery and select other anf fix apk uid mismatches, and fix permissions. You can flash back to clockwork when your done. I would also raise your min freq to 245000, and try that for awile.
Okay, I flashed a Nandroid backup from the very first day I rooted my phone. Then a couple others from other sense ROMs I have run. Every once in a while I'm still dealing with a little lag loading something, and I'm trying to let things settle in for a couple days before I flash a new kernel.
But, a friend at work also has an Inc, and after going from Sense to CM back to Sense, he's experienced similar problems. So I have a vague idea of what the problem is, but literally no idea how to fix it.
cmlusco said:
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.
Click to expand...
Click to collapse
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
Sent from my ADR6300 using Tapatalk
tiny4579 said:
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
EDIT: I thought i would also mention that this happens on all governers except performance, not just on sa or sa2.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.
cmlusco said:
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.
Click to expand...
Click to collapse
I never had the problem using 128 before I switched to CM and back to Sense.
TheManCalledX said:
I never had the problem using 128 before I switched to CM and back to Sense.
Click to expand...
Click to collapse
Well i have never used CM, i have always used sense roms.
Try smartass governor (not smartass v2) and see if it helps. I don't know about reboots but there is no wake lag or virtually none.
Sent from my ADR6300 using Tapatalk
Ok, I posted a test release in the kernel thread. Please test it if you're having lag issues.
to themancalledx
I had the exact same problem going from aosp to sense. For me it was a pretty simple fix. I hope it works for you. Go into recovery select advanced and then fix permissions. Good luck.
New kernel released. Try that one.
Sent from my ADR6300 using Tapatalk
I'm not sure if this has happened to anyone else..
However, this seems to be an ongoing issue with me and Android.
I've had the X10a and Nexus One .. both after only rooting it and using a different rom. While making phone calls and charging.. my phone would reboot..
Or playing a game on the phone.. it would reboot. I basically couldn't do anything without the phone rebooting. Which was sad.
Now with the Galaxy S2X.. This very same issue just happened to me moments ago.
Should I have never rooted it or changed the rom in the first place?
It was running very well before I decided to do so.. even while charging and talking on the phone.
Its funny because it just happened while charging.... I'm not even on the phone myself.
Does anyone seem to have any problem with this when using custom ROMs?
Because if this is true.. then I guess I'll flash the stock kernel and stuff back on the phone just to HOPE it doesn't occur then. :/
I've only experienced this after trying different roms and kernels. I flashed the stock kernel and the deodex rooted stock rom back at the same time and have had no such things happen again.
Imo, stock always runs better than any other rom. I always get better battery too.
My sensation was/is the same way, reboots, dropped signals and all until I put it back to stock rooted. Now it's fine.
——————————
Deebo took your bike too?
Yes I have had it more often on this phone though but it has been fixed by wiping the proper things first then flashing. If not then you might need to redownload the file.
If that doesnt work then you need to make sure that the kernel you are using is compatible with the rom
Also make sure that you are using the proper cpu software for the kernel.. Setcpu seems to work good for most but on Juggernauts new kernel they highly recommend Fauxclock .
I've run roms and kernels since we got root. Never had a random reboot or any other problem for that matter.
Sent from my SGH-T989 using Tapatalk
no6969el said:
Yes I have had it more often on this phone though but it has been fixed by wiping the proper things first then flashing. If not then you might need to redownload the file.
If that doesnt work then you need to make sure that the kernel you are using is compatible with the rom
Also make sure that you are using the proper cpu software for the kernel.. Setcpu seems to work good for most but on Juggernauts new kernel they highly recommend Fauxclock .
Click to expand...
Click to collapse
The only thing I'm worried about is if I continue to wipe and reinstall these customs ROM's that this issue could worsen, but you said that Fauxclock was highly recommended for Jug's Rom? I should try that out myself.
I've always done exactly what was written on the Instructions themselves.
But as for now. . I did a full wipe.. including my SD and the USB data and did a practice call for roughly an hour with me playing games and surfing. So far, there has been any problems. I hope this is perm!
I'd hate to waste another $500 phone D:
As far as the problem kernel with rom etc..
I am running Jug's rom straight. No different kernel's nothing.
I just had it happen to me last night. First time on this phone it has happened. It its stock, rooted. Happened while I was paying music in the car. My other phones with custom roms used to do it all the time.
I wonder if this has happened to anyone without ANY mods on their phone? =X
Fix Permissions
What exactly does that do?
jangst123 said:
Fix Permissions
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
none, with Juggernaut, they did an excellent job
yes, with stock ROM
Sighx said:
I'm not sure if this has happened to anyone else..
However, this seems to be an ongoing issue with me and Android.
I've had the X10a and Nexus One .. both after only rooting it and using a different rom. While making phone calls and charging.. my phone would reboot..
Or playing a game on the phone.. it would reboot. I basically couldn't do anything without the phone rebooting. Which was sad.
Now with the Galaxy S2X.. This very same issue just happened to me moments ago.
Should I have never rooted it or changed the rom in the first place?
It was running very well before I decided to do so.. even while charging and talking on the phone.
Its funny because it just happened while charging.... I'm not even on the phone myself.
Does anyone seem to have any problem with this when using custom ROMs?
Because if this is true.. then I guess I'll flash the stock kernel and stuff back on the phone just to HOPE it doesn't occur then. :/
Click to expand...
Click to collapse
Are you overclocking?
I am running jugs rom. Before I cleaned everything I did move a lot of apps to SD. Maybe that cause it but as for now I have no.problem. definitely report in the future should there be anymore.
AllGamer said:
none, with Juggernaut, they did an excellent job
yes, with stock ROM
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
Reviving old thread... I have a completely stock S2X running 4.0.3 and it randomly reboots or shuts itself off.
I'm trying to figure out if it's a wayward app or a hardware problem. Thinking of rooting and removing the bloatware.
I also saw that it could be a faulty power button, but it also happens by itself, sitting on a desk.
jabela said:
Reviving old thread... I have a completely stock S2X running 4.0.3 and it randomly reboots or shuts itself off.
I'm trying to figure out if it's a wayward app or a hardware problem. Thinking of rooting and removing the bloatware.
I also saw that it could be a faulty power button, but it also happens by itself, sitting on a desk.
Click to expand...
Click to collapse
Root try new rom and kernel see if that fixes it.
Did anyone find any solution? everything in this thread failed for me ..
Have you tried updating to jellybean? Mu phone used to randomly reboot on 4.0.4 probably once a day, and hasn't done it since I did. I am on stock rom.
Sent from my SGH-T989D using Tapatalk 4 Beta