I'm currently running the 7-1 nightly of CM10.1. After every restart, bluetooth is stuck in the off selection and won't turn on. The only way I can fix it is flashing with any nightly (even the same one) and it brings it back up. Now, I just can't restart my phone until I find a fix. It also did this with any version of CM, including RC5 and earlier nightlies.
Still no solution for this issue except to not reboot the phone and have the latest nightly standing by for the next time it crashes/reboots for it to hopefully fix the issue. I don't see this problem on any other threads, so it sounds unique to me
Related
When I try to enable WIFI on my G1, for a couple of seconds it says: enabling WIFI, but then the phone becomes unresponsive (for about 1 second) and it reboots.
IIRC the problem started when I upgraded to the new CynogenMod ROM (4.1.99, but not sure), but it doesn't seem to be linked to the ROM.
I have always used CyanogenMod and update with every new version.
I tried to go back to the default HTC rom, but this doesn't solve the issue.
Does anyone know what may cause this or give me some tips on how to debug this?
I tried to run 'adb logcat' but it shows no info.
The exception browser in the CyanogenMod is also empty.
I don't know what else I could try.
Some extra info:
HSPL 10.95.3000
Radio 2.22.19.26I
CynogenMod ROM 4.1.99 is not the newest. Wipe, flash the htc image, flash cyan's newest and try wifi again.
No, I know, but I think that's when the problems started.
Latest version I installed was 4.2.13
I have installed the RC7 dreaimg.nbh now (used to root the G1), and when I try to enable WIFI on this rom, the phone doesn't reboot, it keeps working, but I get an error saying that WIFI could not be started.
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
mattb3 said:
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
Click to expand...
Click to collapse
This is consistent with my experience as well. By far, the VAST majority of spontaneous reboots that have occurred on my phone have been when using wifi. Some of the older Cyan ROMs were really bad about this, but this continues to occur (although much less frequently) regardless of the ROM. I am presently using SuperD and have had one reboot in the past week.
This seems to happen most often when using the wifi heavily; for instance, I get a reboot probably every 3rd or 4th time when I'm doing my weekly podcast downloads. I don't remember any reboots when just surfing the web or downloading apps, though.
I have never had this happen when I was running cyan.
Are you wiping everything? Even EXT and dalvick?
Are you using any other apps when this is running and rebooting? Perhaps an offending app?
You should also open ADB and run ADB Logcat and try to replicate the issue and try to get a log submitted so the dev can help determine what is causing this issue.
I wiped everything and even without any apps installed, it just reboots.
adb logcat doesn't show a thing when the phone reboots, it just exits.
In addition to the home and talk buttons not working. The phone will not lock when I hit end, it just puts into a sleep mode.
Holding end only gives a reboot and shut down option. This problem surfaced after installing the new SuperD mod. I did a wipe and reinstalled it two nights ago and the problem was resolved, but it has resurfaced tonight.
Anyone have any thoughts on the matter? Should I go back to the old version?
Which new version? The beta or 1.10.2? If it's beta - then you def should go back to stable. If it's 1.10.2 - then you most likely have a hardware problem. A lot of people run Super-D with no problems.
Further more, sometimes your trout-keypad-v3.kl (located in /system/usr/keylayout/) can get corrupted and cause that. It's extremely rare but you may try either re-flashing or just pushing that specific file.
Word of advice (which you may already know): if anything goes wrong and you want to rule out software problem - install a base rom (like the defanged from Cyan's wiki), complete wipe and min options (no Apps2sd, no swap, etc) and see if it fixes the problem. If the problem is gone - you're in lock and something went wrong with the rom. If problem is still there- start looking for a new phone.
Good luck.
I did a fresh install. I repartitioned the sd card, reinstalled all apps. did a factory wipe, reinstalled the base defanged, then did super D. It wasn't the beta, i had upgraded to 1.10.2 and experienced the problems.
It would work fine for two days, then if my phone would shut off (battery has weird contacts) then it would boot back up and my settings would be all messed up, and the keys would work. I would try re installing the ROM, but no fix.
A wipe remedies the problem. I went back to cyanogen last night to see if the problem appears on this rom, so far it hasn't.
I never had this problem until i upgraded from 1.9.3
I recently bought a nook color and flashed CM7 to the internal memory. It worked perfectly for about 2 weeks. Then the trouble started. My wifi would not connect. It would get to the point where it would say, obtaining IP address, then begin the process again without ever actually connecting. So i decided to try to reinstall CM7 hoping that would fix the problem. I attempted this, and to my disappointment, the nook wouldnt boot past the green cm7 logo. I reverted to stock from a backup i made initially, and the nook booted just fine into the stock OS, but the wi fi still would not connect (doing the same thing as in cm7). I reinstalled cm7 and again was greeted with the same boot issue as before. I then followed the "dummies guide to fixing my nook wont boot" and returned it to the stock image and reformatted the data and system partitions as the guide states. I then (again) flashed CM7 (nightly 134). This time, it booted as it should, but the wifi still will not connect, and also the softkeys are not present. In settings, if i select the CM7 settings, i am given a force close notification. I am beyond frustrated at this point and would greatly appreciate any help.
Thank you
I have the same problem with my wifi. It's really weird. It was working last night, then I backed up the current rom and when it rebooted the wifi wouldn't work again. I'm about to just remove cm7 because I don't have the time to fiddle with trying to figure out how to troubleshoot it. A buddy of mine at work is the one who flashed it for me but it hasn't been a great experienced. Rom Manager also doesn't show an updated version of cm7, I think the one that is flashed on my NC is like from may 25th or something.
idk what the hell's going on with it...i cant get it to work no matter what I do and it's driving me crazy. I posted here and on the CM7 forums and havent gotten any help yet, nor have i seen anyone else with the same problem (aside from the above poster).
Hello everyone,
I flashed CM 10.1.2 with build-date 2013 Jul 11 and I can't activate my WiFi anymore.
Bluetooth is ok, but I can't disable NFC - same as WiFi.
I push the button and it's "working" to activate wifi or deactivate nfc - but nothing happens. [edit: nfc working after reboot]
I've got not many ideas what I can do. Everything is working fine with the stock rom v.20a EUR_Open.
Has got someone an idea what I can try?
I did every step on it's own to have a look on which point the problem appears - after installing cm 10.1.2 with cwm recovery.
Bootloader is unlocked.
I'm looking forward to your suggestions and please accept my apologies for my bad english.
Kind Regards
FChaos
For nfc, just restart once, that will fix it
Hey,
im having the same issue with wifi.
When i try to activate the switch gets stuck in grey but it does not activate.
I have it since I installed CM 10.1.2 stable. Before everything worked just fine.
Any solutions for this problem?
Greetz
Wipe cache & dalvik cache
Fix permissions
Reboot
If that doesn't work then full wipe and reflash.
Note: WEP encryption will not work with CM v10.x so make sure you are using WPA on your wireless networks.
I already tried everything you mentioned, but nothing works for me.
WEP is not the problem, because I can't even get to the point to select my router. Also I'm using WPA2 at home.
eliarno said:
I already tried everything you mentioned, but nothing works for me.
WEP is not the problem, because I can't even get to the point to select my router. Also I'm using WPA2 at home.
Click to expand...
Click to collapse
I presume the CM build you refer to is a nightly? Try a different one or CM stable - nightlies are a beta software and may have random bugs.
The problem occurs since I installed the CM 10.1.2 stable.
After that I also tried some of the new CM 10.2 nightlies, but the problem still exists.
Any other ideas?
Edit:
When I install Android 4.1.2 Stock everything works just fine, but the moment I install CM wifi does not work anymore.
Hi all,
I recently flashed the cm-11-20140913-SNAPSHOT-jcsullins-tenderloin on my HP TP first time after WEBOS and love to have android on my TP. Although it was working perfectly regarding all aspects, but two days back wifi stops working suddenly and it doesn't turn on. When i slide the bar of wifi from OFF - ON it didn't move and the screen says WIFI TURNING ON and remains. After that i completely wiped all the data and flashed another version of CM11, it did work for some minutes and again the same problem with wifi. I then tried (After Wipping again) the old CM10.1 version with supported files but again it doesn't on from the start. One thing i want to mention that when i change the CM11 version it stops working after couple of minutes and then i shut down and check in the morning it was again working and then again stop after rebooting. I also tried to control it from WIFI Apps i.e. wifi control, wifi manager when it works for some minutes but the apps also failed to TURN ON THE WIFI when it fails from the system.
I also try to search this topic but i didnt find any which worked for me.
Any help regarding this issue would be highly appreciated.
Regards
No any Response:S
First of all, how did you "flash" the ROM? Are you using tptoolbox?
Also, there are several newer versions of jcsullins ROM available to install.
What gapps did you use?
Please provide more information on your part so folks are able to help you.
Get the newest Jcsullins CM11 build
hsroomi said:
Hi all,
I recently flashed the cm-11-20140913-SNAPSHOT-jcsullins-tenderloin on my HP TP first time after WEBOS and love to have android on my TP. Although it was working perfectly regarding all aspects, but two days back wifi stops working suddenly and it doesn't turn on. When i slide the bar of wifi from OFF - ON it didn't move and the screen says WIFI TURNING ON and remains. After that i completely wiped all the data and flashed another version of CM11, it did work for some minutes and again the same problem with wifi. I then tried (After Wipping again) the old CM10.1 version with supported files but again it doesn't on from the start. One thing i want to mention that when i change the CM11 version it stops working after couple of minutes and then i shut down and check in the morning it was again working and then again stop after rebooting. I also tried to control it from WIFI Apps i.e. wifi control, wifi manager when it works for some minutes but the apps also failed to TURN ON THE WIFI when it fails from the system.
I also try to search this topic but i didnt find any which worked for me.
Any help regarding this issue would be highly appreciated.
Regards
Click to expand...
Click to collapse
gtallmadge said:
First of all, how did you "flash" the ROM? Are you using tptoolbox?
Also, there are several newer versions of jcsullins ROM available to install.
What gapps did you use?
Please provide more information on your part so folks are able to help you.
Click to expand...
Click to collapse
Yep thats right, the more info the better when reporting problems and make sure you've got the most up to date rom. Full guides can be found in my signature below.
Get the most updated Jcsullins Rom here cm-11-20150113-SNAPSHOT-jcsullins-tenderloin
I have this same issue, wifi works fine on lollipop, but not on cm11, i originally used tp toolbox to remove webos, resize partitions and flash lollipop. I tried going to cm11 for full functionality and wifi would not work, i tried 3 different cm11 based roms and none worked, i went back to lollipop and wifi worked right away.