Database Develop

[Q] Milestone reboots after switching from flight mode to normal

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.

Wifi off after reboot

This has become a minor irritant... when I first installed CM7 my Nook Color was happy to connect to wi-fi directly after rebooting.
At some point in the past week I attempted toggling airplane mode just to see what it would do. The checkbox doesn't stay checked, as it seems to error out of trying to enter that mode. Subsequent to that attempt, every time I reboot, the tablet starts up with wi-fi disabled. I can turn it back on and it works, but after a reboot it's off again.
Has anyone else run into this?

cmstlist said:
This has become a minor irritant... when I first installed CM7 my Nook Color was happy to connect to wi-fi directly after rebooting.
At some point in the past week I attempted toggling airplane mode just to see what it would do. The checkbox doesn't stay checked, as it seems to error out of trying to enter that mode. Subsequent to that attempt, every time I reboot, the tablet starts up with wi-fi disabled. I can turn it back on and it works, but after a reboot it's off again.
Has anyone else run into this?
Click to expand...
Click to collapse
yup, lots of people. This might help http://forum.cyanogenmod.com/topic/18630-wifi-not-working/

Thanks for the link. I tried the solution of forgetting a secured network and then re-adding it. Rebooting now to see if that killed the "ghost airplane mode"...
No it didn't. Wifi is still off post-reboot.
Trying the sqlite instructions to see if that works... YES! Perfect solution.

cmstlist said:
Thanks for the link. I tried the solution of forgetting a secured network and then re-adding it. Rebooting now to see if that killed the "ghost airplane mode"...
No it didn't. Wifi is still off post-reboot.
Trying the sqlite instructions to see if that works... YES! Perfect solution.
Click to expand...
Click to collapse
I was all ready to flash the ROM again when I found the sqlite fix. My first time messing around with editing DB's. Worked for me too! WHEW!

I know this is old but all you need to do is download "Android Assistant" and turn off the Airplane Mode via the settings.

Thank you for the link. The only answer that worked for me.
pastordl

[Q] Recurring wifi error

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

[Q] Xperia V: Weird behaviour with Cyanogenmod 10.2

Hey, I'm new here, I apologise in advance if I'm posting it at the wrong place. I also searched for similar issues, but found nothing quite like the symptoms I experience.
I have two new Xperia V phones. I unlocked both and installed Cyanogenmod 10.2 on them.
One of them is not doing any problems. The other has the following behaviour: every once in a while, when I leave it untouched for a few hours, it turns itself off. Well, I'm not sure if it's really turned off, but touching or holding the turn on button doesn't do anything. Only after I remove the battery and put it back in place can I turn the phone back on.
I noticed this behaviour happens regardless of whether I leave the phone charged (say, for the night) or it's just lying around for a few hours. I haven't been able to establish any problem pattern (like how much time of inactivity it takes before the problem kicks in).
Could anyone here help with me with my problem or give me pointers on how to further debug it?
Thanks in advance,
alteclanding

Did the problem exist when you run stock firmware?
Sent from my Xperia V using Tapatalk

No, but unfortunately I don't know how relevant it is, as I didn't really use the stock firmware for a long time -- I pretty much installed Cyanogenmod right away (after around 2 days).

alteclanding said:
Hey, I'm new here, I apologise in advance if I'm posting it at the wrong place. I also searched for similar issues, but found nothing quite like the symptoms I experience.
I have two new Xperia V phones. I unlocked both and installed Cyanogenmod 10.2 on them.
One of them is not doing any problems. The other has the following behaviour: every once in a while, when I leave it untouched for a few hours, it turns itself off. Well, I'm not sure if it's really turned off, but touching or holding the turn on button doesn't do anything. Only after I remove the battery and put it back in place can I turn the phone back on.
I noticed this behaviour happens regardless of whether I leave the phone charged (say, for the night) or it's just lying around for a few hours. I haven't been able to establish any problem pattern (like how much time of inactivity it takes before the problem kicks in).
Could anyone here help with me with my problem or give me pointers on how to further debug it?
Thanks in advance,
alteclanding
Click to expand...
Click to collapse
Next time this happens, connect the phone to your computer and see if it's recognized with ADB. If it is, then it's on, which I think is most likely the case, I've seen it happen before; phone goes to sleep and can't wake back up, which doesn't make sense if you installed the exact same ROM on both phones, and are running the same apps, but at least you can check.
If it is on, you can pull a logcat and dmesg with ADB in order to see what's going on, and even reboot the phone without having to take out the battery.

Antiga Prime said:
Next time this happens, connect the phone to your computer and see if it's recognized with ADB. If it is, then it's on, which I think is most likely the case, I've seen it happen before; phone goes to sleep and can't wake back up, which doesn't make sense if you installed the exact same ROM on both phones, and are running the same apps, but at least you can check.
If it is on, you can pull a logcat and dmesg with ADB in order to see what's going on, and even reboot the phone without having to take out the battery.
Click to expand...
Click to collapse
I've been waiting for it to happen again, and today it happened. But connecting it to my computer, I wasn't able to recognise any device with adb. Nothing on lsusb, no kernel messages, phone is completely dead until I take out battery and put it back again.
Is there any way to check logs after the phone has rebooted? Any logs before the last 'crush'?

i've been using tsubasa 10.2 for months and gave me headache for only had 5hrs battery....
it's just only 4days ago i change to this rom using the backup zip option and having back my xperia v battery to more longer battery service...

WiFI Quit Working... Hardware?

Hey Guys,
Nexus 6 got really hot on N4 build tonight, so hot it felt like it was going to burn my hand. It was supposed to be on standby, but I noticed the screen was on? It was a very strange bug, but I immediately turned it off to let it cool. Now WiFi isn't working. I've let it cool some more, FDR it, and installed a completely different ROM (CyanogenMod) just for kicks to see if it would start working..... It won't. Did the WiFi modem burn out? Cell data works fine...
Any advice would be great. Tried all the recommendations for a fix already. I have a warranty if I need to use it.

nikeman513 said:
Hey Guys,
Nexus 6 got really hot on N4 build tonight, so hot it felt like it was going to burn my hand. It was supposed to be on standby, but I noticed the screen was on? It was a very strange bug, but I immediately turned it off to let it cool. Now WiFi isn't working. I've let it cool some more, FDR it, and installed a completely different ROM (CyanogenMod) just for kicks to see if it would start working..... It won't. Did the WiFi modem burn out? Cell data works fine...
Any advice would be great. Tried all the recommendations for a fix already. I have a warranty if I need to use it.
Click to expand...
Click to collapse
Without a logcat no one is going to be able to offer any advice.