I've updated my moto g to cm13/marshmallow 6.0.1 nightly build on 15th Dec and have been facing WiFi connectivity issues since then(it keeps disconnecting every 10-15 seconds). I am aware that nightly builds are unstable, but now I am unable to get back to lollipop and stuck. I tried to factory reset the phone but no success. Does anybody have a workaround or any solution to this.
Eagerly waiting for reply!
Did you tried to wipe the /data partition from TWRP Recovery to fix the issue ? Try to upgrade to the latest nightly from CM.
Its a cm13 bug all device i know that using cm13 have the same issue in wifi if im right that problem is in the WPA-PSK/WPA2-PSK security on because when i remove the security on my wifi connection it doesnt disconnect anymore, and i think the cm13 doesnt support old wifi router's wifi security
Related
Hi, I have a big issue on my Nexus 5 runnig L 5.1. Basically, I made some mistakes flashing various rom/kernels so I had to wipe evrything and flash the stock rom in order to fix it. Evrithing went fine, but now my wi-fi doesn't seem to work. I can't see any wifi network.
I have unlocked bootloader with the latest twrp. Hope you can help me solve my usse. Thanks in advance!
Turns out it wasn't the issue, but I managed to fix it. Basically the 5.1 hates wi-fi on channel 12 or 13, so I fixed it changing my router's channel from 12 to 10. So I leave this post here, just in case somone alse has some issue. You may close.
OPO running CM14
My WiFi works perfectly fine at home. But when I am at school and*try to connect to their guest WiFi network, it has issues. I select the network in settings. It connects. Then I go to do the web login and before it can load it disconnects the*WiFi.
What I've tried:
Putting my phone in airplane mode while connecting
I turned off captive portal detection
I've tried a few "WiFi fix" apps
I've tried switching to static IP and it doesn't change anything
Restarting several times
Resetting network settings
I'll also note that it did this*before I flashed CM14 when I was on Sultan's CM13. I wiped everything except internal*storage which makes me wonder if I might have some kind of certificate installed*or something like that.
I do have aggressive WiFi handover off
Your problem is your running a very unstable CM14. NEVER run CM14 until the official snaphot cyanogenmod 14 build from the cyanogenmod website is available
JT1510365 said:
Your problem is your running a very unstable CM14. NEVER run CM14 until the official snaphot cyanogenmod 14 build from the cyanogenmod website is available
Click to expand...
Click to collapse
I was having the issue when I was on Sultan's CM13 though too. Do you think I should try doing a complete wipe (including internal memory) and flash a more stable rom?
Hi,
I was running CM12.1 with TWRP + SuperSU without any issues until I broke the screen . Then I replaced the screen and started seeing intermittent issues with GSM signal. There would be signal for some time and it'll drop intermittently. I thought that it would be a software issues and upgraded to cm13.1 and then cm14.1 and finally lineageos 14.1 . I still see the same issues. I've tried changing the firmware as well and don't see any improvement.
How do I debug whether this is a hardware issue? Can I view some log/kernel messages which can be used for debugging the actual. Looking for more systematic approach to debugging the issue.
ROM : LineageOS 14.1
modem firmware: DI.3.0.c6-00241-M8974AAAAANAZM-1
TWRP version: 3.0.2-0
re500 said:
Hi,
I was running CM12.1 with TWRP + SuperSU without any issues until I broke the screen . Then I replaced the screen and started seeing intermittent issues with GSM signal. There would be signal for some time and it'll drop intermittently. I thought that it would be a software issues and upgraded to cm13.1 and then cm14.1 and finally lineageos 14.1 . I still see the same issues. I've tried changing the firmware as well and don't see any improvement.
How do I debug whether this is a hardware issue? Can I view some log/kernel messages which can be used for debugging the actual. Looking for more systematic approach to debugging the issue.
ROM : LineageOS 14.1
modem firmware: DI.3.0.c6-00241-M8974AAAAANAZM-1
TWRP version: 3.0.2-0
Click to expand...
Click to collapse
Did you tried flashing radio/modem?
Mr.Ak said:
Did you tried flashing radio/modem?
Click to expand...
Click to collapse
Tried a couple of firmware. Just tried XNPH44S-modem.bin from cm11s. Looks like it's stable. Let me monitor it for some more time and see how that works.
My XT1032 is dropping out of Wi-fi randomly every 2 minutes when I use android Nougat and Marshmallow, I have tried the following solutions:
- Clean Flashing the Marshmallow AOSP Rom and the Lineage OS 14.1 Rom
- On the AOSP Marshmallow Rom I even tried using the legacy DHCP client and setting the Wi-fi to be on even when the phone is sleeping
- Replacing the "WCNSS_qcom_wlan_factory_nv.bin" file on the persist folder
The weird thing is when I´m using Android Kit Kat or Pie I don´t have this problem, the Wi-fi works perfectly.
I hope you can help me solve this issue. Thanks in advance!
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
atharvvvg said:
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
Click to expand...
Click to collapse
Hello members,
Last week i'v also installed the latest lineageOS version ( 17.1, android 10) Gapps nano, on my Samsung A3 2017. With the TWRP tool., Nice ROM!
Unfortionally with the same issue as above, Samsung and other camera app's very often not working, need to reboot to fix that.
The flashlight does not work either then, and much more irritating BlueTooth not working anymore, my A3 always had perfect connection with my Parrot carkit CK3100.
I'v found in several forum some workarounds for this but these do not solve the issues long enough.
But the issues are also found in older releases from LineageOS.
Will there be a update for these mentioned 3 issues?
If not, i need to install another ROM which is not based on LineageOS.
The Cam and BT must work without any problems.
Thank you very much.
Frank.