Related
Dear all,
I am getting reboot if I turn flight mode on and then off. This is happening every time.
I first created replies in CM6 and Froyo topics, but I've already tried CM7 and got the same behavior - so, issue seems to be in bootloader or hardware.
Could you please advice what could be the reason and how to fix it?
I'm attaching a logcat. Thank you in advance.
illi4 said:
Dear all,
I am getting reboot if I turn flight mode on and then off. This is happening every time.
I first created replies in CM6 and Froyo topics, but I've already tried CM7 and got the same behavior - so, issue seems to be in bootloader or hardware.
Could you please advice what could be the reason and how to fix it?
I'm attaching a logcat. Thank you in advance.
Click to expand...
Click to collapse
Same problem here
BTW, could you please advice in which case battery will be drained more:
a. If I switch the phone to flight mode, leave phone for 6-7 hours and then reboot it.
b. If I do not enable flight mode and leave phone for 6-7 hours
I think that the battery life will be better with the Airplane Mode on (because the phone doesn't search for signal - somebody please correct me if I'm wrong!). Par example, a few weeks ago, I was at my grandparents, at countryside, where there is no Orange signal at all. I switched my phone to Airplane mode and with music (~3hours), some Doodle Jump (~1h) and some photos I got ~two days (my phone's battery usually lasts ~25-30 hours when on normal use, with Airplane Mode off).
same problem =(
can anyone help me?
edit:
Im using CM7 RC4.1
telus canada sbf
this problem only happens using the "Claro" chip, other service provider chips works fine.
this also happens on any custom rom Ive tried, cm7, miui and sm.
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
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
Help!! My XT has been running fine since I got it last September however since yesterday my device just shuts down when connected to network. Not a restart I actually have to physically turn it back. My device runs fine in airplane mode but as soon as I turn airplane mode off 3 seconds later off.
I am running a locked boot loader with non rooted 141 loaded through PCC so completely stock setup.
Is this looking like a hardware issue possibly or will reloading the stock firmware fix this?
Thanks
Sent from my Transformer TF101 using xda app-developers app
A quick update:
Issue sorted its self out in the evening, Managed to get conected to a network but only with data off, by the morning all was working fine again.
BUT
Later on saturday I had exactly the same cycle of issues again.
Device was fine all day yesterday YAY
However today has seen a return to being dead.
The difference being I didnt drive anywhere yesterday along with this rareity known as "British Summer". We have had some very warm days of recent and I am assuming the shutting down is a fail safe as the device gets too warm.
I guess there is nothing I can do but ride this out. Given we only have this sort of weather for about a week or so a year(if at all).
How do you guys who live in the more consistently warm climates cope with this device which clearly has heat issues?
Issue is getting much worse.
All last night it was out of action worrying as I use it as an alarm so ran it over night in airplane mode.
This morning working fine but now turns off everytime I send a text message.
I had an issue similar to this but it was whenever i connected to a particular WiFi network. For me changing the WiFi channel worked.
ITHORA said:
I had an issue similar to this but it was whenever i connected to a particular WiFi network. For me changing the WiFi channel worked.
Click to expand...
Click to collapse
No issues linked to WiFi seen here just when connecting to network.
issues have only come up since I updated to 141. everyone says this one prevents these issues which I never saw on earlier softwares.
I have done a repair through PCC and will see how that goes now.
Ok, device is not fixed by the repair.
I am no longer having the device randomly shut down completely but the the device is restarting. It has happened 4 times in the last hour.
1- As soon as sent a text.
2- Moving some apps around in the draw
3- Sending another text
4- unlocking phone
Does anyone have any ideas at all what is wrong with my device. Running smoothly for so many months and then now phone is becoming completely unusable.
Not sure if related but issues dont seem to arise when on charge and issues today only started once batter got below 60%.
Hi,
I've been using the stable version of CM 10.1.3 since Christmas and have experienced no issues whatsoever, it's worked flawlessly...until today. I woke up this morning to find my phone charging as I had left it, but the hardware lights were turned on. Thinking it was odd, I turned the screen on then off again and the lights turned back off as they should. When I came back after breakfast however, they were on again! This has been happening all day; I'd check my phone and find that the lights had turned on. I can't seem to find any pattern (like always 2 minutes after screen off) and it doesn't even happen all the time - I left it for half an hour and they didn't turn on, but the next time I turned off the screen they turned on again after a few minutes.
Has anyone else experienced this issue and, if so, how did you fix it? I haven't yet done a factory reset as I was hoping someone else would have a good fix that doesn't mean I have to reconfigure everything.
I've also noted signal dropping a lot today, but after turning the phone off and reinserting the SIM card it seems to be back for good (well, an hour at least). Could this be related?
Any help would be great
creativeusernamea said:
Hi,
I've been using the stable version of CM 10.1.3 since Christmas and have experienced no issues whatsoever, it's worked flawlessly...until today. I woke up this morning to find my phone charging as I had left it, but the hardware lights were turned on. Thinking it was odd, I turned the screen on then off again and the lights turned back off as they should. When I came back after breakfast however, they were on again! This has been happening all day; I'd check my phone and find that the lights had turned on. I can't seem to find any pattern (like always 2 minutes after screen off) and it doesn't even happen all the time - I left it for half an hour and they didn't turn on, but the next time I turned off the screen they turned on again after a few minutes.
Has anyone else experienced this issue and, if so, how did you fix it? I haven't yet done a factory reset as I was hoping someone else would have a good fix that doesn't mean I have to reconfigure everything.
I've also noted signal dropping a lot today, but after turning the phone off and reinserting the SIM card it seems to be back for good (well, an hour at least). Could this be related?
Any help would be great
Click to expand...
Click to collapse
I have the same problem. But i have CM11. Help please
joaoumbelino said:
I have the same problem. But i have CM11. Help please
Click to expand...
Click to collapse
This was really strange. The day after making this post I did a factory reset, which didn't help so I flashed a 4.4.2 Vanir Nightly. After a while this issue developed again on there, so I decided to change to official CM 11. The issue continued for an afternoon, but overnight it fixed itself - I haven't dropped signal or had the light issue for a few days now. I'd still like to know what the issue was though in case it happens again! Here's hoping yours fixes itself too