Hey Guys,
I'm not sure what the cause of the issue is, I've been dealing with 3 phones that have been having the same issue.
Quite literally, as long as Data is turned on, the phone will periodically go into airplane mode. Sometimes more often than others.
Something tells me it's the area, because all 3 phones are running different versions.
Any ideas?
I have no clue of cause or solution, but I am currently sitting here with a phone that will not make or receive calls due to going into flight mode.
I can however search 3g internet fairly well and text no problem.
I am trying to upgrade firmware from JG9 to JH2 somehow to see if that helps.
the phone does not supposed to go into airplane mode automatically
did you install NoBars or some other system tools recently ?
I performed multiple wipes on each phone.
The only difference on two of them is software, I have flased multiple versions of 2.1/2.2 on the two in question, one is left as bone stock, I have a feeling it's a location issue, however my sim cards work in other phones flawlessly.
Really confused about this, any effort is appreciated.
Mine is factory reset, with never have been rooted or lagfixed or anything special. Used some apps from the market but that is about it. I do wish I could get JH2 flashed to it tho, see if that magically fixes it.
Related
All, having a weird issue. I was on the phone yesterday using an automated menu system and my phone restarted. No rhyme nor reason why. It did that repeatedly throughout the day. I tried flashing a new ROM version, Phoenix 6.0!!, with no luck. I tried a normal restart, power down and then up, running a virus scan, pulling the batter for 30 minutes and no difference. The phone continued to restart. I finally got fed up and my battery was almost dead so I turned the phone off.
The phone was off for probably 5 hours and I charged it while off. I restarted the phone and transferred all of my content off, expecting to Odin back to stock and reflash Phoenix. The phone seemed to be behaving so I left it alone and plugged it into the wall for the night.
I got up this morning and everything appeared to be good. Went to work and still no problems, phone had an uptime of over 12 hours. Which would be what I would expect. Had the phone on my desk and I noticed it had restarted. When I mean it restarted, it went back to the boot animation and then loaded to the android screen and performed media scan and all my apps loaded on the home screens and services started up.
I went back to Settings->About->Status and the uptime was 18 hours now. So even with the restart, the uptime was still counting. Needless to say, I'm at a lose. Can't isolate any event that causes this reset or any app. Could I have gotten something from the automated call system? Is something just weird. I had been running Phoenix 5.2 for a few weeks with now problems so I'm confused. Any suggestions would be appreciated. I will probably flash back to stock and start again but I'd like to isolate this problem if possible.
To the best of your knowledge, no apps were just added, our settings adjusted?
Either way I would odin flash master clear. May even run stock for a but to see if behavior stops
Sent from my Captivate using XDA Premium App
sounds like a problem with the infamous 850-1900mhz handoff....
if your signature is accurate, that modem you are using is 1900mhz only i believe....it doesnt support 850, so if you are in an area where its trying to hand off to 850, it will cause a soft reboot.....i have seen it a million times myself when playing with the first run of i9000 roms
Pirateghost said:
sounds like a problem with the infamous 850-1900mhz handoff....
if your signature is accurate, that modem you are using is 1900mhz only i believe....it doesnt support 850, so if you are in an area where its trying to hand off to 850, it will cause a soft reboot.....i have seen it a million times myself when playing with the first run of i9000 roms
Click to expand...
Click to collapse
Hmmm...I have been using an i9000 roms for a few months with no issues. The last modem I was using was I9000UJK4, I think? I don't know without flashing back, whatever came with Phoenix 5.2 ROM. I had zero problems. I only flashed to that modem/ROM, Phoenix 6.0, in an attempt to fix the soft reboot.
flash just the JK4 modem and i bet the soft reboots stop. what you have listed there is i believe a 1900mhz only modem....
Pirateghost said:
flash just the JK4 modem and i bet the soft reboots stop. what you have listed there is i believe a 1900mhz only modem....
Click to expand...
Click to collapse
I will try that, when I can find it to download but the problem started with the JK4 modem. I was running Phoenix 5.2 with a JK4 modem and only flashed to the new one in an attempt to wipe whatever was causing the data.
Flashing UGJK4 right now, I'll see if that fixes anything however I'm not super confident since the problem occurred originally with a JK4 modem.
Update: Rebooted once after modem flash. Going to wait for a bit and see what happens.
if that doesnt work, i would think its a problem with your hardware
Pirateghost said:
if that doesnt work, i would think its a problem with your hardware
Click to expand...
Click to collapse
If the modem switch doesn't work, I'm first going to flash to stock and master clear. If the problem goes away, I'll flash to Phoenix again. If the problem comes back, it'll have to be part of my SW. If the problem persists at stock, back to AT&T for a refurbished phone.
Update: Looks like things are pretty stable right now. I'm not super in-tune with how the modems work but is there a way to allow the JK4 modem to use 850 or 1900 speeds, like an auto setting that will choose the best one. I use SGS tools for secret codes so if its in there let me know. So far so good, thanks pirate.
Reviving an old thread because I am also having soft reboot issues.
Unlike the previous poster, I am not using an i9000 based kernel. I am running the latest leaked Gingerbread for the i897 (JK3), rooted via Fugu kernel swap method; the only other tweak to stock has been to freeze via TiBu the AT&T Tethering Manager. I am even using the stock launcher as I try to isolate what is causing this.
The phone goes through spells where it will soft reboot every 10 minutes or less, and then periods where it will go days where it is stable. I have had this issue with multiple versions of the 2.3.3 and 2.3.5 leaks and am nearing wits end figuring out the cause.
Before each flash (and I have flashed multiple times with different stock leaks) I am wiping data and cache via recovery (I do not have CWM installed), then restoring apps only via TiBu. I have tried to be judicious about what I reinstall, but have not been able to identify if there is a misbehaving one yet.
I suspect this is software and not hardware, since I had this problem on my first Cap and have already done one warranty exchange; the external SD card, though, is the same for both.
I've looked for kernel panic logs and have not seen any, and have yet to find a good way to trap what is causing this.
This is my work issued phone (does Exchange sync and has company policies sent to it), so I am loathe to go all the way to a custom ROM, even though I realize that I voided the warranty when I rooted and went to leaked ROMs.
Anyone have an ideas as to what could be causing this, how I can isolate the problem, and hopefully resolve it once and for all? Worst case, I could go back to Froyo until AT&T finally drops the promised Gingerbread update, but I had different issues with Froyo with Market updates not always finishing and apps on the SD card not always being recognized.
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium
Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium
ATT auto updated my phone. Everything seems to work like it should except that the area next to my sim card is hot enough to burn me. If I put my phone in airplane mode everything is fine. My battery life is less than 4hrs. I have done a factory reset with no success. I want to install a custom rom but I cannot find a root for this new version. Is there any way to install a new rom with no root?
luxveritas said:
ATT auto updated my phone. Everything seems to work like it should except that the area next to my sim card is hot enough to burn me. If I put my phone in airplane mode everything is fine. My battery life is less than 4hrs. I have done a factory reset with no success. I want to install a custom rom but I cannot find a root for this new version. Is there any way to install a new rom with no root?
Click to expand...
Click to collapse
I am also having the same issues. I thought it was a hardware problem, but after seeing your post I'm suspecting it is something else. I even went to the AT&T store to get a new SIM just in case that was the issue. It suxs, my phone is getting intermittent network connectivity and the right side of the phone is roasting. I also performed a factory reset to no avail... Anyone else having this issue?
I am having the exact same issue. Its basically made my phone unusable. Once the phone starts connecting/talking it gets very hot and i lose cell service. It like the cell radio starts working overtime, over heats and stops working . I have to put it in airplane mode t get the phone to cool down. Not sure what to do since it seems like a software issue. All started after the update.
krperegrin said:
I am having the exact same issue. Its basically made my phone unusable. Once the phone starts connecting/talking it gets very hot and i lose cell service. It like the cell radio starts working overtime, over heats and stops working . I have to put it in airplane mode t get the phone to cool down. Not sure what to do since it seems like a software issue. All started after the update.
Click to expand...
Click to collapse
Since my phone is unusable and there is nothing I can do software wise (Installed all AT&T updates and performed factory reset), I decided to call Samsung and put the phone in for a warranty repair. We shall see what happens after the 9 days it takes them to make repairs. Guessing that they wont actually troubleshoot the issue, just verify nothing is physically wrong with the phone, liquid spill, drop damage, etc. and then just send me a clean referb.
Success!!!
I performed a factory reset and set the phone up as a new phone ignoring my backups. I installed all the updates and everything is working again.
The locked bootloader on this phone is bull****. ATT/Samsung broke my phone with an update and I could not install root to fix it myself. I will only buy apple or google phones from now on. I hope that the companies that make the OS might be a little more careful with their updates.
Hey all! New here. I just soft bricked my phone, i woke up to it not booting. I tried various fw in Odin, but no success. This is my day to day use phone, I don't have anything else, so I'd like to make it work again ASAP, hopefully without factory reset.
Hi
what manipulation did you do to get there before flashing a lot of stuff in odin?
I've been just pressing the buttons all around, then I read about Odin, so I tried it. Now my battery died, let's see if I can get to wipe the cache...
Update: no success. Is there a way to get it into recovery? the old volume up+bixby doesn't seem to work.
Sometimes its because the recovery itself is error so that button combination is not working..
Charge your battery until full, then factory reset it with odin, let see if that works
But before you do that make sure you download correct fw that match your phone model. dont try all fw available there, make sure you download fw for SM N950F..
Well it worked and it broke again... Back to square one.
Your infos are kinda vague.
Did you modify your phone and it got triggered by user-action, or did it hit the fan by itself?
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
fzoli469 said:
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
Click to expand...
Click to collapse
This was happening to me too before my phone just started bootlooping to recovery
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
fzoli469 said:
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
Click to expand...
Click to collapse
Try changing build prop, ro.config.tima to 0