Related
My phone is stuck in airplane mode...
It just started earlier today, about the time I had lost signal and would have gone into roaming on the way to my dads house.
In the past Ive run Epic experience with xtreme kernel, and with 2.2 I have tried the original leak, Mammon, and I was on Quantum when it started doing this. I just tried wiping and reflashing to the newest version and its still stuck.
Any ideas?
Note: I did NOT make any attempt at flashing the 2.2 modem.
So this is what I did and it worked flash the stock rom firon or noobnl posted I foget and then flash to 2.2 again it worked for me after a few times.
Sent from my SPH-D700 using XDA App
So flash the stock 2.2 that Firon had posted to get airplane off, then flash back to whatever I want? Or do you mean flash stock as in out of the box 2.1?
Ive never had to odin or whatever all that jazz is, wasnt an option on the hero obviously, and I try to keep my messing with the epic to a minimum. So it makes me a little nervous.
Well you could flash the modem.bin in odn to make it easier idk wher t find that tho search the forums.
Sent from my SPH-D700 using XDA App
Similar Problem with Epic stuck in Airplane Mode
There is a similar thread about this problem under the Sprint Forums. Myself and several others have experienced multiple instances of the Epic randomly going into Airplane Mode on its own. Sometimes it gets stuck there for several hours. It appears that this has something to do with a weak signal. For me, it happens only at my home, where I have little to no signal. I have an Air Rave, but for some reason it appears to go into Airplane Mode more often with the Air Rave on than with it off. This is very frustrating. Sprint does not acknowledge the problem. They say it must be a hardware issue, and we should just get new phones, but I'm on my fourth phone, as is another person on the Sprint forum, so it appears to us that this is really some sort of software bug, but it does not occur often enough to cause Sprint or Samsung to take notice and do something about it.
This happened to me as well the day before yesterday... I had installed ViperRom IMpact, and had car home running navigating me to LAX, and all of a sudden, my phone reboots and then was always stuck in airplane mode after that. I recovered my original rooted rom, stock 2.1 just rooted, and worked fine... Installed SyndicateRom (2.1) and still could get signal. Tried to install another 2.2 ROM, and get the same thing where it's stuck in airplane mode... So I think I'm going to stick it out with SyndicateRom for a bit...
had the same problem a couple weeks ago for several hours. spontaneously fixed. and about 20 mins ago it went into the problem again. no apparent solution.
Possible solution...
I am on EF02 with EF10 modem. This happened to me after the phone was not touched for hours. After many reboots I decided to boot into clockwork (purple) and flush the cache and after the reboot service was restored. Possibly just a coincidence or maybe a solution?
-This is more for googlers than the op.
I have this problem pretty often when I am in a place with bad signal. Reboot the phone into clockwork recovery, in advanced options, fix permissions. This has fixed it every time. Also sometimes just rebooting it will fix it but that only seems to work randomly.
zndotcom said:
I am on EF02 with EF10 modem. This happened to me after the phone was not touched for hours. After many reboots I decided to boot into clockwork (purple) and flush the cache and after the reboot service was restored. Possibly just a coincidence or maybe a solution?
-This is more for googlers than the op.
Click to expand...
Click to collapse
I've had the same thing happen on EF02; every time, I pull the battery, boot into recovery, wipe caches & occasionally battery stats (hey why not), & every time the phone reboots with full service again.
I've seen it happen on my phone and a friend's phone. The advice below always works.
tragiquexcomedy said:
I've had the same thing happen on EF02; every time, I pull the battery, boot into recovery, wipe caches & occasionally battery stats (hey why not), & every time the phone reboots with full service again.
Click to expand...
Click to collapse
p3dr0maz said:
I've seen it happen on my phone and a friend's phone. The advice below always works.
Click to expand...
Click to collapse
Just had the same issue pop up on my wife's phone, & wiping caches fixed it a well. Thank God for XDA & Clockwork!
I have never been able to get a tiamat kernel to work on my xoom. I followed a set of directions to completely start from scratch (again, plus formatted whole xoom 3-4 times before doing that) and flashed Tiamat ROM and it worked! I was even able to OC to 1.4, 1.5, then tried 1.7 which caused it to freeze and crash. Then it started acting funky so I did a restore and everything is fine until I turn the screen off or let it turn itself off with a timeout.
The system reboots into M screen and/or a black screen. A reset or two gets it rebooted. I increased the min freq and reset max to 1ghz. What can I do to fix this?? Thanks!
--- Update --- The browser causes a reboot as well. Random reboots into black screen. Def could use some help
ALWAYS stays on black screen when screen times out. Also does it after clearing data via honeycomb. Looking for a little help, can't post on the ROM thread yet
Well I would start from new wipe everything and reflash. Can't hurt. Sounds like something is broke. You can also try to fix promissions as well.
I've completely formatted the xoom including the sdcard and then started w/ 3.0.1 then did the 3.1 flash via CWR then the ROM install. The booting is better after complete wipe but screen still doesn't come back on after a time-out or i shut screen off manually. Browser also causes are boot which takes me to a 2-3 'M' reboot which then times out into black screen. 2 or 3 resets later and it boots up but then reboots within a couple minutes.
The official 3.1 update had my browser crashing which is why i said screw it, i'll flash new stuff. Could def use a hand
I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..
Me as well I've tried everythingeverything. Currently on tiamat 1.1. With rc4 3.3.0
go into wifi settings and make sure your wifi disconnect policy is set to never
2JZ GZE said:
I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..
Click to expand...
Click to collapse
+1
also occassionally find the xoom stuck on motorola boot screen without me trying to turn off or back on..
Ill try but I don't think the wiring has anything to do with the black screen. This will lock even if wifif is off
Mine didnt like 1.7 either, I ended up leaving it sat next to a desk fan for a while to cool it down whioe switched off, then very quickly when it booted managed to get into antutu widget to drop the speed down and hit apply before it locked up again, rebooted all fine now, set it to 1.2ghz to be safe..
Kippui said:
go into wifi settings and make sure your wifi disconnect policy is set to never
Click to expand...
Click to collapse
Dude. I think this worked. I switched my wifi disconnect setting to, never while charging..it was set as, never(uses more battery power). I am currently on Tiamat 1.4.5 with CWM (rc4)3.2.0. Just let it chill over night and charge after a factory reset and viola. Have booted the screen in rotation and a few power offs. Even running at 1.2 g with set CPU. Been running smooth for 2 hours and I can't force it to even freeze. Could it really be that simple. Hahahah. Well see.
Ok odd thing keeps happening. My epic will randomly power off but will not power back on until i do a battery pull. I am currently running 2.2.1 RandomRom 2.2 Final EC05. I dont think it is the rom but who knows. Any Ideas would be great! Thanks Everyone in advance.
Do you use setcpu or anything like that? Some phones dont like to run below 200mhz.
Posted by Mr. Z's Epic 4G via Tapatalk
Nope not running anything. It only does it when the phone is not charging. If its on the charger it stays on. If i pull it off the charger it could turn off 20min to 3 hrs later.
harmhimself said:
Nope not running anything. It only does it when the phone is not charging. If its on the charger it stays on. If i pull it off the charger it could turn off 20min to 3 hrs later.
Click to expand...
Click to collapse
My last one did that, but it was because I dropped it. Have you ruled out a hardware problem?
Posted by Mr. Z's Epic 4G via Tapatalk
Not that i know of. Its never been dropped. I wonder if i should factory reset and start all over. I just dont know what else it could be.
It's most likely that it's a third party app causing the issue.
That said, the best way to exonerate the software is to ODIN to the stock EC05. If it does it with that, it's probably a hardware issue. If it doesn't, it's probably a ROM or kernel issue.
P.S. it's humorous that RandomROM might be causing RandomREBOOTS.
Haha.....yea. I liked it at first but guess its back to finding something new.
Yeah I'm having a similar problem also but only recently like no more then a couple weeks... my phone doesn't shut down completely but it randomly restarts itself and the ODD thing is that when it would power back up it would be in AIRPLANE mode. No matter how many times I tryed to disable airplane mode it just would not turn off! Even after I would shut down my phone and power back up it was still in airplane mode. So I took out the battery for a couple of seconds and put it back in, powered up and every thing works fine again... its only happened about 3 times I'm running that new gingerbread leak so that might be the issue but I've been rnning it for a while now and only recently had this problem with the phone.
I run ACS Frozen 1.2 have the same issues, I've had the same issue since froyo sourced roms have come out.... phone randomly powers off..... only happens maybe once or twice a week. It happened extremely more frequently before I changed back to RFS and turned journaling on. It didn't completely correct the problem, but it helped a lot.
Nothing like waiting for a text back from your GF only to find out that your phone has turned off sometime in the last hour since you sent out a text. I call it "The Samsung **** Block"
this happens to me sometimes, if you have journaling off, something might be corrupted. when the phone tries to access the corrupted data it puts the phone in an infinite loop, you might notice a huge decrease in battery life when you do reboot. A fresh clean install is the best way to fix it.
mrhocuspocus said:
this happens to me sometimes, if you have journaling off, something might be corrupted. when the phone tries to access the corrupted data it puts the phone in an infinite loop, you might notice a huge decrease in battery life when you do reboot. A fresh clean install is the best way to fix it.
Click to expand...
Click to collapse
Thanks. I've noticed this.
Sent from my SPH-D700 using XDA Premium App
I was on my way home from vacation (5 hour drive) and I had my phone plugged in the car charger with GPS, Google Maps and Pandora running all at the same time, when my phone overheated and shut-down. A warning sign came on saying that it was either "too hot or too cold to charge." Well, i decided to swap batteries and that point when I booted the phone, I got a FC boot loop. I had journaling ON btw.
I had a CWM backup ready, and simply restored it. So nothing was lost. But still, i didn't know our phones could heat up like that.
btw: i was on srf 1.2 w/Genocide 1.2. Underclocked to 800mhz and undervolted slightly.
Anyone else experience and issue like this?
Yep, except I was on bonsai and my problem with the fc made me Yank the battery. Upon reboot there was the android telling me to touch him to begin.
Sent from my Illudium Q-36 Explosive Space Modulator.
I've had that happen once, while using the tethering function, but couldn't replicate it even when trying (yes, I don't know why I tried to break my phone either, but I guess that's what they say about curiosity killing things..)
I did over memorial day weekend. Visiting the west side of Mi... Phone outside charging via wall, streaming pandora through wifi, plugged into speakers sitting in the sun. I use a battery monitor widget that gives a readout of temp... I looked ay the phone and it was at 128°F! Quickly unplugged, shut down the phone, pulled battery and took inside to cool. After 30 minutes when phone and battery seemed to return to room temp I turned the phone back on and once the os booted up everything fc... Nothing would run at all! Luckily I also had a backup to cover me. I was on srf 1.1.1 btw...
Sent from my SPH-D700 using XDA App
i disassembled my entire phone and when i reassembled it i got a bunch of force closes till i restored a back up.
I have had this happen quite often.. It is usually when I am charging and talking on me way home from work.. I will have the phone sitting on the seat next to me, using a headset, sitting in the sun most the time. And it will give me the warning and then reboot, usually when I get off the phone. And when it loads FC's out the butt and just loops. I normally never have a backup, so I just clockwork and reload the rerfs zip and it takes me back to rooted stock and i reload from there.. I can do it pretty quick these days... It actually did it over the weekend and I tried clearing the dalvik cache(sp??) and the cache and it seem to fix the fc's. But I need to just get in the habit of keeping a current backup.. Any way to schedule one in clockwork??? That would be a nice feature..
I actually had a post on this a long time back and got 1 reply..
I think thats a serious flaw in the design of the phone.
You can't charge AND use the phone at the same time? Because it will over heat and cause data corruption? That's ridiculous.
Does this only happen to rom'd phones? or does this happen to stock phones as well?
futureprospect said:
I think thats a serious flaw in the design of the phone.
You can't charge AND use the phone at the same time? Because it will over heat and cause data corruption? That's ridiculous.
Does this only happen to rom'd phones? or does this happen to stock phones as well?
Click to expand...
Click to collapse
i think it only happens to phones with journaling off.
it happen to me as well
but it messed everything up had to wipe and reflash sfr then everything was good but the phone was useless. luck was on my side and it was at the end of my trip.
I have always ran with journaling on!! And dang it, just got back from lunch and guess what... I didnt even have the phone plugged in.. Just talking on it.. It was sitting on my seat and all of a sudden it just rebooted. When it came back up the fc's were there and the same loop as always.. I am currently trying to see what will get me going again. I did the wipes and nothing.. The last time I got the fc's to stop, I also hit fix permissions by accident.. So I am running that now. I am not even sure what that does, but like I said last time it seemed to work.. We shall see... LOL and yeah no backup to use in clockwork.. You think I would have made one this morning huh? And I never noticed this problem until after froyo...
BTW- The fix permissions and combo cache wipe has me back in business..
I think the ability to schedule a regular backup weekly or something would be a GREAT feature for any recovery....
Sent from my SPH-D700 using XDA Premium App
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
CapsLockKey said:
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
Click to expand...
Click to collapse
Was the CRT script based on the EI22 framework?
I got it from the EI22 CRT off thread in the theme section.
Last night I also had an odd reboot. Not like the old random reboots that would happen when the phone was asleep, this one seemed like it was caused by a GPS crash. I had been using an app that triggered the GPS, (weatherbug I think) and when I closed it, the GPS icon stayed on. Even after I turned off GPS it still stayed on. The phone also started getting pretty warm. GPS itself no longer worked. After a few minutes of trying to shut down GPS the phone locked up. A minute later it did a "partial" reboot, playing the startup sound and eventually giving me the launcher screen. It was still not running right, with the GPS icon stuck on and the phone very sluggish. I did a shutdown and restart. The phone took a long time to start up, sitting on the "big S" for a while just like on it's first startup. Makes me think something got corrupted in the cache and it had to rebuild it.
I don't know if this was just a random event or the sign of problems to come.
This was on Stock EI22, installed as an OTA upgrade over a fresh EC05 install. The only mod was the CRT off / Circular battery mod that I created at the UOT kitchen.
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
CapsLockKey said:
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
poit said:
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
Click to expand...
Click to collapse
Tried clearing data, reinstalling, etc. Doesn't matter, still FC's immediately after reboot. Problem must be with Launcher Pro not liking something, because I just flashed CleanGB Rom (which includes the CRT-off and several other tweaks) to try it out and it does the same thing on that.
Update: Seem to have solved it, but not sure why. Had Voodoo Plus set to load module on boot, when I turned that off LP did just fine after rebooting. Decided to flip the load on boot back on to see if it would start FCing again and magically enough it hasn't.
I just had a random reboot and im in stock EI22..... Why?
Sent from my SPH-D700 using XDA App
Been on it since it was released, no reboots here... Working great for me.
ive had this off and on for a few days now. i find it to be caused by having multiple launcher in my case spb shell .had it running stock the first day so i flashed a rom and its still there. also other apps that use alot of resources will cause it. it partail reboots about 3 or 4 times and then runs normal.
CapsLockKey said:
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
I have the same issue with Zeam Launcher, clearing defaults doesn't seem to help. I wonder if there's some kind of half-assed check to make sure that TWLauncher is running? I dunno, but it's obnoxious considering how many times a day I'm forced to reboot EI22, added to the fact that they got rid of the deathgrip reboot.
My phone has "Randomly" rebooted on me several times, usually in an area with little signal coverage. Each time, it seems like there's some program (like Spotify or DI.FM) running that's making network calls when the signal craps out.
EI22 has been nothing but problems for me.
Just had my first random reboot. I'm stock EI22 not rooted yet. Imanually installed on the first day and this was my first. Phone was off just sittin on the table and the screen come on showing low battery but was still sittin at 30% and it shut off and the samsung screen come up and went thru the boot up process.
Sent from my SPH-D700 using xda premium
Please see this thread if you get random reboots with WIFI on.
http://forum.xda-developers.com/showthread.php?t=1359315
My Stable setting with no random reboots !!!!
After trying out virtually every rom/kernel out there (started with stock) I finally got a configuration in which I hadn't got any random reboot (or any other silly issues). My current setting are :
ROM : ERA Lagendary RC2
Kernel : Samurai 2.0.1 (inbuilt with Rc2)
Theme : Ei22Ics version 2 (just for fun !!!)
I have used Voltage control to OC it with settings : 400 Mhz minimum(recommended somewhere in dev post), 1340 Mhz maximum(~1400 mv voltage which I think maximum my handset can handle) with ONDEMAND governor.
My Epic is running flawlessly with no random eboots of FC's since last 4 days (while it used to reboot atleast 3-4 times daily earlier).
Hope this helps !!!!
Epic Timezzzzzzzzz !!!!!!
I still get random reboots in EI22, but not as many as I did on the GB leaks. I can cause a reboot by scrolling to fast in Settings, Applications, Manage Applications, All. I have had the phone run for 90 hours without a random reboot so I'm happy.
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
rando991 said:
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
Click to expand...
Click to collapse
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
i dont get any with
ROM = ASC AICS 5.5
Kernel : Samurai 2.0.6
Theme = Shake & Bake Mix Up v.5.9
kennyglass123 said:
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well I did notice it only happened on that particular charger (from Walmart)...also, my wife's epic didn't reboot, but had the charging light stuck on all day. I had to power it off and remove the battery to end it. Would that be maybe the same problem?
Been on CleanGB for quite a while. Went out of town this weekend to Chicago and ended up being rebootpalooza on my phone. Probably had almost half a dozen, once it just shut down in the middle of a phone call at the train station after the low battery notice came up, even though after I powered it back on it still had 28%. Another reboot was I unplugged the car charger shortly after the "full" indicator light came on. Others were just amazingly random. I've loved my Epic up until this trip when it turned into the most unreliable thing I've had.