Hi, I've an annoying problem with the Bluetooth: when it's turned on, it turns off randomly and after few seconds it turns on.
It's impossibile to keep connection with other devices.
I've the last firmware version.
Please help me!
Try a factory reset to see if it is a problem with the software or an app.
If it still keeps dropping it might be a broken Bluetooth module which has to be repaired...
I have root and recovery. Can I reflash the firmware I have with root and dualrecovery included? If yes, what I lost?
Thanks
I have a similar problem with various CM12 and CM12.1 builds ... Bluetooth just can't be turned on, after turning it on, it turns itself off after a few seconds.
Originally I thought, it maybe a hardware defect, but when going back to a previous version of CM (restoring a nandroid backup), Bluetooth worked flawlessly. As I didn't want to stay with a build from November, I kept updating the ROM, but Bluetooth stayed offline.
Until today when I made the suggested factory reset. Now Bluetooth works without problems, even after reinstalling all the apps I had installed before. So thanks for your advice, Schlengge
Related
Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.
Hi there,
Just wanted your point of view regarding something really strange that happened to me yesterday.
(btw, I looked it up all over the forum + google but still unabale to find a proper answer)
So basically, I droped down my phone, which crashed on the floor but nothing really serious. Ever since, every time I try and turn on the wifi, it says "Error".
I've tried rebooting it several times and still get the issue.
Do you guys think the wifi chip could have been broken? Is there any report log I could find using terminal or root explorer?
Phone specs:
Virtuous Unity v1.29.0
Android 2.3.3
Phone rooted
Bluetooth does turn on
Thanks in advance for your help
Try flashing a different rom, back up your current one first, and check out if the wifi is working without restoring any apps.
Did you ever fix this? I did the exact same thing, dropped onto hard tile. Wifi error and couldn't read data partition.
Randomly after a day or 2 it fixed itself and was fine for 2 weeks.
BUT...just happened again today. I wiped caches, reflashed ARHD, fixed all permissions. Data partition became readable again (not sure which of those fixed that) but i still get "Wifi Error" when turning wifi on.
Any help/suggestions much appreciated.
Hi guys,
My f400l has been experiencing issues for a while now. One morning, I woke up to find an unresponsive device. Took out battery and turned it on again to find that the device had partially reset itself (ie. going back to stock launcher and layout, missing apps). Device was still rooted so I tried to restore apps and settings via titanium backup. However, phone kept freezing throughout restore process.
Next, I decided to flash back to stock. This is when i noticed that wifi would remain at 'wifi turning on' but never actually turn on. Additionally, bluetooth could not be turned on. I then upgraded to lollipop via normal firmware update from lg software on my pc. Phone then would freeze after every 2 mins.
After trialing many rooms, I am now on cloudyg3 2.1 but wifi/bluetooth are still not working and phone still freezes occasionally (usually at the beginning of the day).
Really at a loss here, can anyone suggest what seems to be happening and what I can do about it?
Thanks everyone!
smarikoe said:
Hi guys,
My f400l has been experiencing issues for a while now. One morning, I woke up to find an unresponsive device. Took out battery and turned it on again to find that the device had partially reset itself (ie. going back to stock launcher and layout, missing apps). Device was still rooted so I tried to restore apps and settings via titanium backup. However, phone kept freezing throughout restore process.
Next, I decided to flash back to stock. This is when i noticed that wifi would remain at 'wifi turning on' but never actually turn on. Additionally, bluetooth could not be turned on. I then upgraded to lollipop via normal firmware update from lg software on my pc. Phone then would freeze after every 2 mins.
After trialing many rooms, I am now on cloudyg3 2.1 but wifi/bluetooth are still not working and phone still freezes occasionally (usually at the beginning of the day).
Really at a loss here, can anyone suggest what seems to be happening and what I can do about it?
Thanks everyone!
Click to expand...
Click to collapse
reflash the modem and kernel and you should be set
suljo94 said:
reflash the modem and kernel and you should be set
Click to expand...
Click to collapse
sounds simple enough.
Would these be the right links?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-rin-kernel-1-0-t2847581
http://forum.xda-developers.com/showthread.php?t=2784501
If flashing the modem, wouldn't I need to first revert back to stock kitkat?
smarikoe said:
sounds simple enough.
Would these be the right links?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-rin-kernel-1-0-t2847581
http://forum.xda-developers.com/showthread.php?t=2784501
If flashing the modem, wouldn't I need to first revert back to stock kitkat?
Click to expand...
Click to collapse
flash the correct one
https://www.androidfilehost.com/?w=files&flid=22640
suljo94 said:
flash the correct one
Click to expand...
Click to collapse
Argh! So i tried flashing and upon reboot, phone came up with a security error. Currently reverting back to stock via download mode. I couldn't get back into recovery. Did I do something wrong? Thanks for the help so far tho!
EDIT: ahhh just realized i flashed a kitkat kernel, woops! Will see how things pan out for now
So i went back to stock and flashed a kernel but that didn't seem to help. Can't seem to find a zip file for kitkat baseband so I'm a bit lost as to how to flash a modem.
One thing I also noticed is that fact that i cannot access recovery via hardware buttons? I use power and volume down but the combo doesn't work. It just boots normally?
Hi,
i'm hoping someone could help me with an issue that has happening since i flashed a ROM onto my one M8.
Before i flashed a rom, the bluetooth audio connection worked perfectly with the radio in my Skoda (a Kenwood DNX525 DAB), ever since I flashed a rom, i have had problems with the audio cutting out, or stuttering every 30 seconds or so. If i unpair and delete the connection from both devices, then re-pair the devices, it might work without problems for one journey, then after restarting the car the stuttering is back.
The first rom i flashed was Mikes Android revolution HD 45, then flashed 53.1, and i am now running LeeDroid V8.2.1 and all have had the same problems.
As far as i can tell i am doing all the clean caches, and formatting i need to, but i would really like to get this working without having to resort to going back to a stock ROM.
If anyone has any ideas how to fix this, or trouble shooting i could try myself, please let me know.
Thanks in advance for any help.
Try seeing if your head unit has some setting option (might be pretty buried in a sub-menu) to "re-initialize" the system. This will wipe any settings you've made (to factory defaults, I believe).
Hopefully, this will help your BT connection issue. I had a similar issue on my Subaru head unit (which I understand Kenwood supplies - at least for my 2012 model) where the phone would not properly auto-reconnect, after flashing a ROM. Unpairing, and re-pairing didn't help. But re-initializing fixed it right up. If so, you may have to do this with every new ROM flash. Although, backing up Bluetooth Pairings with Titanium Backup, and restoring after a ROM flash, also seems to work okay for me.
If you were on a Sense ROM originally (when BT connection was working well) I wouldn't think there would be much (if any) difference in Bluetooth stacks. So I'm guessing and hoping that re-initializing the head unit, and re-pairing will solve the issue.
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
KartmanCV said:
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
Click to expand...
Click to collapse
Guys any help
KartmanCV said:
Guys any help
Click to expand...
Click to collapse
Use some other rom... Recommended crdroid latest build... Use picogapps... And try again...
The issue could be rom related and even after trying new rom the problem still persists then it could be a baseband issue...
Try the recommended rom first with complete full wipe .. Good luck
Hi,
Were you able to fix this?
I'm facing the same issue. Tried several basebands and ROMS. Also, flashed stock rom through QFIL/QPST, but the issue is still there.
Thanks,
nicky.phoenicks said:
Hi,
Were you able to fix this?
I'm facing the same issue. Tried several basebands and ROMS. Also, flashed stock rom through QFIL/QPST, but the issue is still there.
Thanks,
Click to expand...
Click to collapse
Were you able to fix it??? How did you resolve? After three years, I faced this issue all of a sudden after I changed my phone's battery, and tried everything with software but no fix. Any possibility that it is a hardware issue? How can it be deeply inspected to find the real cause of this problem?
KartmanCV said:
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
Click to expand...
Click to collapse
Is there any fix found for this? or is it forever? Need help, need to give this phone to someone but can't fix this issue. Please help through any ways.
You may try resetting the carrier and wifi network. This may help.
You may try resetting the carrier and wifi network. This may help.