Bluetooth can't find any devices, and can't be found from the other devices.
I have flashed MMB29S via flashtool - doesn't work.
I've updated OTA to MMB29Q (the last one) - nothing changed.
What I can do with it?
I am sure that other devices' bluetooth is alright, i've tested it. The problem is in Nexus 5.
Nexus 5, 32GB, 6.0.1 [MMB29Q]
Try flashing a stock MM ROM with a factory reset.
audit13 said:
Try flashing a stock MM ROM with a factory reset.
Click to expand...
Click to collapse
already flashed. i'm always flashing ROMs with factory reset, to avoid problems like this.
baseband is newest, btw.
Does wifi work? I have a Nexus 5 with dead wifi and bluetooth and I could never solve the issue via flashing. Only thing that fixed the problem was a replacement motherboard.
audit13 said:
Does wifi work? I have a Nexus 5 with dead wifi and bluetooth and I could never solve the issue via flashing. Only thing that fixed the problem was a replacement motherboard.
Click to expand...
Click to collapse
of course, phone is fully functional, doesn't had any problem with wi-fi, always stable signal and fast speed. LTE is stable too.
update: because i am running out of solutions - i'll try to flash last factory image via linux debian.
update2: flashed newest factory image via debian, latest adb and fastboot tools. the problem is still there.
If everything else functions properly, I'd conclude that there is a hardware problem.
audit13 said:
If everything else functions properly, I'd conclude that there is a hardware problem.
Click to expand...
Click to collapse
it's so bad? there is no sowtware solution, and the official service center is the only way out?
The fact that you have flashed other ROMs and everything works with these other ROMs except Bluetooth spells hardware issue to me.
Related
I am running stock Motorola 4.4 with gravity box and Xposed. My WiFi connection is very unstable where it basically drops randomly for a few seconds which is a severe ordeal when using apps like hangouts and skype. My internet connection has no issues and this happens with my phone well within range. I have turned off the 'drop poor connections' option from the WiFi settings. I also turned off WiFi optimization if that is supposed to do anything.
Previously I was running CM and Gummy ROM and had no such issues with them. Its interesting to note that previously I was running with jelly bean radio and only updated my radio when I came to stock ROM. I suppose I could go back to a custom ROM and see if its still happening but man restoring and all is just so much time consuming.
What I want to know is that are other people facing the same issue with stock ROM?
Sent from my XT1032 using Tapatalk
Also having wifi issues for the first time this am. I had the phone off during the night. Turned it on this am and wifi is very unstable. It keeps turning off. I reconnect and it turns off again. I'm completely stock with 4.4.3.
Router is fine. My other devices work great. I'm only 3 feet from the router and the Moto G still can't maintain a connection.
No issues here. If I where you, I would download the full 4.4.4 firmware image for your model and flash via fastboot. That will absolutely solve your problem.
lost101 said:
No issues here. If I where you, I would download the full 4.4.4 firmware image for your model and flash via fastboot. That will absolutely solve your problem.
Click to expand...
Click to collapse
Can you guide me a little on how to do that?
Sent from my XT1032 using Tapatalk
http://forum.xda-developers.com/showthread.php?p=47820707
https://www.youtube.com/watch?v=-L44JqysUy8
lost101 said:
http://forum.xda-developers.com/showthread.php?p=47820707
https://www.youtube.com/watch?v=-L44JqysUy8
Click to expand...
Click to collapse
Thank you so much man this really solved the problem completely as you had said. I wouldn't have figured it out myself I thought I was already using a stock phone lol.
Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?
Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?
Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?
After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave
deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?
My Nexus 5 which I upgraded from a 5.01 to the 5.1 (stock Google rom, without wipe) has a very big battery problem: the device never reaches deep sleep.
I have some years experience in identifying wakelocks, but this wakelock is new. And the strange thing is: I can't even find a thing on Google. Nothing!
The wakelock is a kernelwakelock (PowerManagerService.Wakelocks). I investigated at partial wakelocks which wakelock it is. It's a wakelock called 'ProxyController'. It's related to the phone process/app.
I wiped cache, tried different Kernel (elementalx). Changed CPU gov, wiped dalvik, changed network, refreshed some settings. Disabled unused apps. I even reinstalled the image and other files through recovery. But nothing helps.
Also I noticed, it might be related, that sometimes my phone reboots or it looses sim and signal. (Which worked perfect in 5.01!). All problems started after 5.1 upgrade.
Ofcourse I can do a full wipe, or revert back or try a custom rom. But I hope it is possible to fix, because besides these weird problems it was / is perfect!
Edit: Important, I couldn't be called either. Also calling someone was difficult and the phone process kept freezing. My phone (and then the phone part) was totally broken! Radio of 5.01 did fix. Read comments below!
Have you tried flashing an older radio.img version and/or a clean flash?
Elluel said:
Have you tried flashing an older radio.img version and/or a clean flash?
Click to expand...
Click to collapse
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
cognosco said:
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
Click to expand...
Click to collapse
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Elluel said:
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Click to expand...
Click to collapse
Yes I fear that too.
However, it started immediately after the 5.1 upgrade, before all was good...
It also seems there might be a link with screenoff/standby. When it's in standby and I switch the device on I see it has no connection or is reconnecting. As if something goes wrong with the connection then. Maybe important information.
I will investigate further. Ofcourse all new tips, ideas and infos are welcome. I will also keep you updated.
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Update: a few days later. Running 5.1 rom with 5.01 radio and all seems ok and fixed!
cognosco said:
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Click to expand...
Click to collapse
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
DarkSorcerer said:
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
Click to expand...
Click to collapse
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
cognosco said:
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
Click to expand...
Click to collapse
Hi,
Thank you for your quick answer. I'll try it first thing in the morning.
It is weird indeed.. My provider is the equivalent of Orange. As with you, it only started to happen after the update to 5.1.
I'll report back. Thanks!
Hi there,
Everything was working just fine, but since I switched to a new carrier I can't get the network back as soon as my OP looses it (subway for example). I have 4G as my favorite internet mode and my APNs are good.
Only a full reboot fixes it, not even a soft one. What can I do?
I use the lastest CM 12.1 S rom (YOG4PAS3JL)
Maybe I should try to flash Oxygen's modem? http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
It seems many users are affected by the problem but I didn't find a real solution, hence my post.
Thank you!
After a long investigation, it seems that the OPO is having trouble switching for and from 4G. I solved it using 3G as my preferred network, but I'd have loved using 4G
reinstall the system... u can google fastboot images for opo... flash them through CMD
I've tried 3 ROMS and at least 4 modems so I think I've tried eveything that's available atm
I have had the same problem for some time now. But no reliable solutions found. Have tried various versions of ROM and Radio. Currently using 44S and CM 12.1 S (YOG4PAS3JL).
Lamner said:
Hi there,
Everything was working just fine, but since I switched to a new carrier I can't get the network back as soon as my OP looses it (subway for example). I have 4G as my favorite internet mode and my APNs are good.
Only a full reboot fixes it, not even a soft one. What can I do?
I use the lastest CM 12.1 S rom (YOG4PAS3JL)
Maybe I should try to flash Oxygen's modem? http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
It seems many users are affected by the problem but I didn't find a real solution, hence my post.
Thank you!
Click to expand...
Click to collapse
kingalpha said:
I have had the same problem for some time now. But no reliable solutions found. Have tried various versions of ROM and Radio. Currently using 44S and CM 12.1 S (YOG4PAS3JL).
Click to expand...
Click to collapse
For how long have you been using that? Did that fix the problem?
This is very annoying!!!!
xupi said:
For how long have you been using that? Did that fix the problem?
This is very annoying!!!!
Click to expand...
Click to collapse
Didn't fix the problem. Finally reverted back to Oxygen OS. Complete reinstall, including bootloader, storage, everything. Got it done at OPO service centre. Much better reception now.
So last night my phones wifi was working fine. That's until I made a few modifications to it.
Things I did:
Installed TWRP Recovery Menu Moto G port
Installed CM13 Osprey Nightly 20160704
Installed SuperSU
Installed Gapps
Right after all that I realized my WiFi wouldn't connect during the CM13 setup. It just said saved after I entered the password. I tried manually connecting it, it went from full bars to one bar then goes back to saved.. When my phone actually connects to the WiFi it is running extremely slower than normal. It also disconnects at random times.
Things I've tried to fix the problem:
Reinstalling ROM w/wo Gapps & w/wo SuperSU
Trying new router
Allowing all permissions that were not allowed
Enabled legacy DHCP client (saw on a forum)
Contacting ISP to see the strength of modem
If anybody has a solution it would be appreciated. I am not sure what to do. Also im in the same room as the router so the connection strength should be solid. If any other information is needed I'll provide it asap. Thank you.
Try Resurrection Remix, Turbo, CandySix or another ROM... there was grumblings of WiFi issues on the last few CM nightlies in various forums (not just Moto G, but not all devices).
Just flash Resurrection Remix (or whichever ROM) and Mini or smaller gapps package, should be better.
acejavelin said:
Try Resurrection Remix, Turbo, CandySix or another ROM... there was grumblings of WiFi issues on the last few CM nightlies in various forums (not just Moto G, but not all devices).
Just flash Resurrection Remix (or whichever ROM) and Mini or smaller gapps package, should be better.
Click to expand...
Click to collapse
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
itzrishi said:
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
Click to expand...
Click to collapse
It shouldn't. If you are using a case check by removing it. Otherwise flashing firmware via fastboot again may help. I was having a problem of phone rebooting when sim was inserted, I flashed firmware and was good to go. It can solve issues with phone radio and subsequently (maybe) your wifi.
Broadcasted from Zeta Reticuli
itzrishi said:
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
Click to expand...
Click to collapse
Very odd... Flashing a ROM or recovery doesn't touch the modem/radio firmware, although the WiFi on the Moto G 2015 is largely driven by the kernel modules that are compiled with it. Both CM and Turbo, and most roms for the G3 are based on CyanogenMod.
My next step would be to try another kernel, I use squid and WiFi works fine, but any newer kernel has the latest kernel drivers. If the results are the same, might be time to step back and reflash the latest stock Marshmallow image completely and work backwards... Root, test, Flash kernel, test, flash rom, test, etc.
You were in marshmallow before starting the whole thing, right?
Sent from my MotoG3 using Tapatalk
acejavelin said:
Very odd... Flashing a ROM or recovery doesn't touch the modem/radio firmware, although the WiFi on the Moto G 2015 is largely driven by the kernel modules that are compiled with it. Both CM and Turbo, and most roms for the G3 are based on CyanogenMod.
My next step would be to try another kernel, I use squid and WiFi works fine, but any newer kernel has the latest kernel drivers. If the results are the same, might be time to step back and reflash the latest stock Marshmallow image completely and work backwards... Root, test, Flash kernel, test, flash rom, test, etc.
You were in marshmallow before starting the whole thing, right?
Click to expand...
Click to collapse
I was on marshmallow before I did everything. Before I proceed with flashing the original Marshmallow image, is there anything I should take not of during the processes? Also this will make me sound like a noob but what do you mean flash the kernel?
Gravemind2015 said:
It shouldn't. If you are using a case check by removing it. Otherwise flashing firmware via fastboot again may help. I was having a problem of phone rebooting when sim was inserted, I flashed firmware and was good to go. It can solve issues with phone radio and subsequently (maybe) your wifi.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I do not have a case on my phone. But I will try to remove my sim card while I go back to the original Marshmallow image. Hopefully it works out
itzrishi said:
I was on marshmallow before I did everything. Before I proceed with flashing the original Marshmallow image, is there anything I should take not of during the processes? Also this will make me sound like a noob but what do you mean flash the kernel?
Click to expand...
Click to collapse
Restoring the stock images is pretty simple, just log the process... It will return to compete stock.
In the Original Development area there are custom kernels, you can flash them with TWRP to replace the stock ROM kernel. Squid is my personal favorite, we'll balanced without tweaks.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Restoring the stock images is pretty simple, just log the process... It will return to compete stock.
In the Original Development area there are custom kernels, you can flash them with TWRP to replace the stock ROM kernel. Squid is my personal favorite, we'll balanced without tweaks.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I am using squids twrp recovery. I have a question. How do I go back to stock android? Or do I just flash the stock android rom?
itzrishi said:
I am using squids twrp recovery. I have a question. How do I go back to stock android? Or do I just flash the stock android rom?
Click to expand...
Click to collapse
Either restore the nandroid you (should) have from before rooting/flashing, or use lost101's guide and rom images to flash via fastboot. The threads are in general.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Either restore the nandroid you (should) have from before rooting/flashing, or use lost101's guide and rom images to flash via fastboot. The threads are in general.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I don't have a backup because I don't have enough storage. But I did follow lost101s guide.
The bad news is I am still having issues with the wifi. It's not as bad though the speed is decent and it disconnects a lot and just shows saved.
Therefore the problem shouldn't be with the custom rom and I tried using a different device to see if it's my internet but it worked fine.
My conclusion is either the wifi/Bluetooth adapter needs to be replaced.
Although my problem was not solved thank you for trying to help me solve the issue! Much appreciated.
Oh a post after a long time.
I have been having exactly same issues but only with nougat roms.
If I restore my rr marshmallow backup wifi works just fine.
Is flashing stock firmware the only solution?
nikhilsnigam said:
Oh a post after a long time.
I have been having exactly same issues but only with nougat roms.
If I restore my rr marshmallow backup wifi works just fine.
Is flashing stock firmware the only solution?
Click to expand...
Click to collapse
Make sure you have the latest radio stack installed.
acejavelin said:
Make sure you have the latest radio stack installed.
Click to expand...
Click to collapse
Yes I just downoaded the stock package and flashed modem(Older 1)
Seems to work. Haven't had any disconnects till now.