Database Users

[Q] Help! Stuck in airplane mode

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!

[Q] Tiamat ROM Xoom Reboots

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.

Screen keeps on turning itself on/off on stand-by

I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.

I would try a blur ROM first to make sure it isn't your phone. Then you can start thinking about hardware issues on the phone.
Sent with Tapatalk from my Blackberry Playbook

barry_ said:
I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.
Click to expand...
Click to collapse
Very weird, but I noticed a similar problem the last few days. While at work, my phone goes into airplane mode(no reception in the building). When I was on CM7 neutrino, I had an instance where the phone drained the battery completely.
Recently I switched to cm9 Turl v8, and at work I pulled my phone out...the screen was on, Bluetooth was on and my battery had went from ~85% to ~20% mind you, I hadn't turned Bluetooth on.
A few days later I noticed I pulled my phone out and the screen was on...showed the screen and phone had been awake for a few hours....while in my pocket.

thanks for the replies
I got lucky i guess? I decided to start deleting recent apps/themes and the first few I deleted (themes for GOsms) stopped the screen turning on ect, no idea why but hey ho at least it stopped the fault.

Do not restore any thing after a fresh install of cm7 (complete wipe and clean before installation) and ull sure face no problems, i also had these problems not any more.
barry_ said:
I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.
Click to expand...
Click to collapse

New update won't allow my screen to lock

The newest update that was installed on my phone caused a glitch where it won't allow my screen to lock, I placed a timer, to see how long it would take for my phone to turn off,
My phone died after 5 hours, without the screen turning off...
Where is the fix? How do I get it to stop, seriously. This is unacceptable.

Well, the good part is you get at least 5 hours SOT.
I have had this happen periodically, usually a cache wipe fixes it. Still don't know why it happens, and it's quite rare and random, though. Try booting to recovery and wiping cache and see if that fixes it. If not a factory reset may be in order.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T

Galaxy s7 Edge launching Google assistant continuously, maybe a hardware failure?

Been a while since I had any issues with a phone I couldn't fix, but this is usually the best place to come when you run into something weird. Whilst I very much suspect that my phone has reached the end, there maybe something I can do if someone here has seen this before and managed to fix it.
A couple of days ago my phone started acting weird. Google assistant would start up for no apparent reason. Sometimes if I was in an app I'd just get a pop-up message but at other times I'd be taken to my home screen. The frequency came and went, but at it's worst it would happen every few seconds and would last for a good 5-10 minutes.
Thought it was just something weird in the OS so I booted back to the factory reset menu, wiped the cache and the system partition and started again. That didn't work. The start-iup process began with voice assistant turned on and every button click requiring activation and double clicking. I've since tried 5 factory resets.
I've disabled Google Assistant now and removed any updates. I've wiped out it's cache and tried all of the settings to make it stop so I no longer get Google Assisitant launching, but I do get something happening which asks me to "complete action using" and shows me the Samsung internet app, S Voice and Quick dial.
This is making me wonder if I'm looking at a hardware problem. I've switched everything off and given everything a good clean just in case one of the buttons has something stuck in it but that hasn't changed the situation.
If anyone here has any ideas or suggestions then they would be very gratefully received.
Thank you

Clean dalvik cache and update stock software through odin or custom rom may solve your problem

Thanks, will give it a go, forgot about the dalvik cache in the last reset so a good heads up. Will have to look into Odin, not had to use that in years.