Related
Hi guys, I have to clear my mind on a problem:
I have a XT1562 european mono-SIM Moto X Play, and I've upgraded it to Marshmallow (the indian dual-SIM firmware) after unlocking the bootloader and flashed Squid kernel some weeks ago (and then updated to the last build, of course).
Sometimes I'm experiencing an annoying thing: after a reboot RIL dies, and on the best, on the next reboot it reappears; on the worst, after multiple reboots with no luck, I have to do a wipe cache to see it again.
I have root and Xposed (and so, also busybox).
Is anyone experiencing something similar?
There's a way to fix it that maybe I didn't find here on XDA?
Nobody?
have u tried flashing the modem for ur rom?
anks095 said:
have u tried flashing the modem for ur rom?
Click to expand...
Click to collapse
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
nplezka said:
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
Click to expand...
Click to collapse
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
anks095 said:
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
Click to expand...
Click to collapse
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
nplezka said:
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
Click to expand...
Click to collapse
I don't know if this is the same thing as you but I had "Emergency Calls Only" sporadically as well but it would come back either after a short period of time or after a reboot. I also had random reboots too (didn't matter which ROM I was on at the time).
I lived with this for a bit but then upgraded my SD card (it was old) and I haven't had either problem since.
My guess is that my SIM card might not've been seated properly in the little carrier and/or the SD card I had was mucking things up somehow. I wasn't using it as internal storage either.
Anyways, if you haven't tried this already, might be worth taking out your SIM card and re-seating it (and maybe give the contact part a careful wipe). If you still have the problem and you have an SD card remove it and see what happens. Good luck!
Hi guys! I'm here with news:
after several tests in these days, I discovered the problem was every module that can modify the systemUI.
I tried activating and disabling those modules one by one (I'm talking about GravityBox first, then little modules like Advanced Power Menu or a newer one called NeoPowerMenu), and I saw that without them, I had network at every reboot. The only exception in systemUI is SignalIconsAOSP (I really hate that big "4G" icon next to the signal indicator) and it works at every reboot I did. The other modules (like Xposed GEL Settings, Lolistat, YouTube AdAway) don't annoy the system.
So, I don't know, Moto seems dislike too much modifications on the UI or it's a strange bug. Maybe a bug.
Please I need your help guys.
My OnePlus2 recently started behaving weird. The Bluetooth, WiFi and External speaker just stopped working for no apparent reason. Every other thing is working. 3G works just fine. I am able to make calls through the normal speaker (i.e. by putting the phone to the ear), but if I decide to switch the calls to the loudspeaker, I can't hear anything. Also, if I play music to the external speaker I can't hear anything unless I connect a wired earphone through the jack. When I try to turn ON the Bluetooth and Wifi, they just turn themselves back OFF, so they have become useless.
Please has anyone experienced anything like these before; if yes, please how did you solve it.
isadeiza said:
Please I need your help guys.
My OnePlus2 recently started behaving weird. The Bluetooth, WiFi and External speaker just stopped working for no apparent reason. Every other thing is working. 3G works just fine. I am able to make calls through the normal speaker (i.e. by putting the phone to the ear), but if I decide to switch the calls to the loudspeaker, I can't hear anything. Also, if I play music to the external speaker I can't hear anything unless I connect a wired earphone through the jack. When I try to turn ON the Bluetooth and Wifi, they just turn themselves back OFF, so they have become useless.
Please has anyone experienced anything like these before; if yes, please how did you solve it.
Click to expand...
Click to collapse
Not too sure about the External Speaker issue, but generally whenever I get Bluetooth and WiFi issues exactly like yours in the past - a reset solved the problem.
But I only ever had issues like that if I'm using a Custom ROM.....
Is your 1+2 using OxygenOS by any chance?
LogicalJunkie549 said:
Not too sure about the External Speaker issue, but generally whenever I get Bluetooth and WiFi issues exactly like yours in the past - a reset solved the problem.
But I only ever had issues like that if I'm using a Custom ROM.....
Is your 1+2 using OxygenOS by any chance?
Click to expand...
Click to collapse
Thank you for your help.
What I mean by the External Speaker is the speaker at the bottom of the phone next to the charging port that enable you listen to the audio, either call or music, without putting the phone to your ear.
Yes, I am on the stock Oxygen 2.1.0. I have also restarted and wipe data and cache more than five times but nothing different has happened so far.
Ahh so the loudspeaker is faulty? The loudspeaker and the wireless module are quite separate hardware, so we've got to hope that it's a software fault - rather than both multiple prices of hardware being faulty.
At this stage do a nandroid backup, then Clean Install OxygenOS 2.2.0. If that doesn't solve the issue, just let us know. (If you need specific instructions on how to do the nandroid backup & clean install, just let us know as well).
LogicalJunkie549 said:
Ahh so the loudspeaker is faulty? The loudspeaker and the wireless module are quite separate hardware, so we've got to hope that it's a software fault - rather than both multiple prices of hardware being faulty.
At this stage do a nandroid backup, then Clean Install OxygenOS 2.2.0. If that doesn't solve the issue, just let us know. (If you need specific instructions on how to do the nandroid backup & clean install, just let us know as well).
Click to expand...
Click to collapse
Thanks for your support.
I did a nandroid backup as advised and I downloaded and clean install the Oxygen 2.2.0.
The situation didn't change. Its as if the modules are just not present.
For example, when I try to activate the WiFi or Bluetooth, they are animate as if to turn ON; but after a couple of minutes it simply turn back OFF and grey-out.
I even installed the unofficial CM 13 hoping this might solve the problem, but it remains the same.
Do you think this may in any way be connected with the kernel?
isadeiza said:
Thanks for your support.
I did a nandroid backup as advised and I downloaded and clean install the Oxygen 2.2.0.
The situation didn't change. Its as if the modules are just not present.
For example, when I try to activate the WiFi or Bluetooth, they are animate as if to turn ON; but after a couple of minutes it simply turn back OFF and grey-out.
I even installed the unofficial CM 13 hoping this might solve the problem, but it remains the same.
Do you think this may in any way be connected with the kernel?
Click to expand...
Click to collapse
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....
LogicalJunkie549 said:
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....
Click to expand...
Click to collapse
Thank you very much for your time @LogicalJunkie549.
I will download the kernel as advised and install it.
I will come with the update after the installation.
LogicalJunkie549 said:
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....
Click to expand...
Click to collapse
I have done the suggested steps.
The phone remains the same.
Please see attached the screen shots.
It looks as if these modules/chips just went dead
Flash Oxygen OS Zip via Stock Recovery & Wipe Cache & Data
isadeiza said:
I have done the suggested steps.
The phone remains the same.
Please see attached the screen shots.
It looks as if these modules/chips just went dead
Click to expand...
Click to collapse
For your speakerphone issue, I can bet it is related to the modem/ radio.
Please update to the latest modem/ radio (via fastboot) for your device.
Then test calling again and report back.
Note that this issue and solution is not specific to Oneplus. It is applicable to CM 13 on all devices across manufacturers.
Hit the 'Thanks' button if this solution works for you.
Where can I get the OnePlus 2 Modem/Radio File
s_u_n said:
For your speakerphone issue, I can bet it is related to the modem/ radio.
Please update to the latest modem/ radio (via fastboot) for your device.
Then test calling again and report back.
Note that this issue and solution is not specific to Oneplus. It is applicable to CM 13 on all devices across manufacturers.
Hit the 'Thanks' button if this solution works for you.
Click to expand...
Click to collapse
Thank you for your support.
Please any idea where I can get Modem/Radio file to download.
A link will help, because I have been searching for it but no luck so far.
isadeiza said:
Thank you for your support.
Please any idea where I can get Modem/Radio file to download.
A link will help, because I have been searching for it but no luck so far.
Click to expand...
Click to collapse
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Thank you. I am currently on OxygenOS 2.2.1
I will try your suggestions and revert back asap.
LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Thank you @localjunkie549.
I have tried installing the modem and bluetooth files in the downloaded file in the link.
I am afraid the phone response remains the same.
I even tried installing the new OxygenOS 3.0, still the same.
Speaker working Now. But BT and WiFi still down.
LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Hi guys, thank you all for your support.
After a long time, my experience are as below.
After upgrading to OxygenOS 3.0, the behavior of the phone did not change. No sound from loudspeaker, no Bluetooth and no WiFi.
Well I stopped using it until my other phone started heating up so I came back to the OnePlus Two again. One day, I was surprised when the phone started ringing loudly as someone called my line. It worked for about 3 - 4 hours and stopped again. After about 5 days, it came up again for some 4 hours and stopped working again. It does this for over 6 cycles and about 3 days ago it kept working without stopping since.
So I am still observing it for the past three days and it seems to have repented, holding my hopes up high that it will continue to work without hitches again; though I cannot say now what happened, why it stopped working and why it started working now.
The problem of the Bluetooth and WiFi still persist and I still can't use the BT and WiFi. It just behave as if the modules are not present. My fingers crossed expecting them to "miraculously" come back to functional state just as the loudspeaker did on its own.
Thank you all guys for your support.
Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.
SwimDrewid said:
Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.
Click to expand...
Click to collapse
I had something like this before on my Nexus 5. Clearing the cache from the 'phone' app did it for me. Worth trying
maarten08 said:
I had something like this before on my Nexus 5. Clearing the cache from the 'phone' app did it for me. Worth trying
Click to expand...
Click to collapse
Already tried that. Then clean flash. Then updated ROM with latest vendor and radio images. No luck
i have a similar issue when connect to my Huawei Watch. once i turn off bluetooth i can call correctly.
do you still have an IMEI under settings
Gytole said:
do you still have an IMEI under settings
Click to expand...
Click to collapse
Yeah. Att thinks it's hardware. Time to test my Google warranty
SwimDrewid said:
Yeah. Att thinks it's hardware. Time to test my Google warranty
Click to expand...
Click to collapse
What does your prl version say under your IMEI settings? I had this exact problem when I flashed the latest PN build. I tried everything to fix it. Flashing my EFS backup worked for a while but sometimes on a reboot I had the same issue again. Flashing EFS would fix it again but it was temporary. The permanent fix for me was a clean flash of Chroma ROM. Just curious but what carrier are you on? It seems like this issue has been affecting CDMA carriers like Verizon more than others.
murphyjasonc said:
What does your prl version say under your IMEI settings? I had this exact problem when I flashed the latest PN build. I tried everything to fix it. Flashing my EFS backup worked for a while but sometimes on a reboot I had the same issue again. Flashing EFS would fix it again but it was temporary. The permanent fix for me was a clean flash of Chroma ROM. Just curious but what carrier are you on? It seems like this issue has been affecting CDMA carriers like Verizon more than others.
Click to expand...
Click to collapse
On att
Emei sv: 61
Says not roaming but I have that set
SwimDrewid said:
On att
Emei sv: 61
Says not roaming but I have that set
Click to expand...
Click to collapse
When I had this problem the prl version in my screenshot said unknown as well as the MIN number. If you problem started after flashing an update I'll guarantee its software and not hardware. If you have an EFS backup I would try and flash that first if not I would do a backup in TWRP and then clean flash Chroma. If it doesn't work you can always just flash your backup and be back to where you are now.
murphyjasonc said:
When I had this problem the prl version in my screenshot said unknown as well as the MIN number. If you problem started after flashing an update I'll guarantee its software and not hardware. If you have an EFS backup I would try and flash that first if not I would do a backup in TWRP and then clean flash Chroma. If it doesn't work you can always just flash your backup and be back to where you are now.
Click to expand...
Click to collapse
Ah. I don't have that info. Didn't do update till after this problem. May not have efs backed up. But did full clean install of latest du weekly including radio and vendor this morning.
Will check if I have efs backed up
SwimDrewid said:
On att
Emei sv: 61
Says not roaming but I have that set
Click to expand...
Click to collapse
I'm sure you have already checked the APN settings but it would be a good idea to make sure they were not changed when you updated. Are you in a good LTE area? A lot of people with this issue could make and receive calls over LTE but when they didn't have it they couldn't even though they had service. That's why I think it affected CDMA carriers more. LTE goes over GSM and 3g goes over CDMA. Does your phone number show up under SIm info?
murphyjasonc said:
I'm sure you have already checked the APN settings but it would be a good idea to make sure they were not changed when you updated. Are you in a good LTE area? A lot of people with this issue could make and receive calls over LTE but when they didn't have it they couldn't even though they had service. That's why I think it affected CDMA carriers more. LTE goes over GSM and 3g goes over CDMA. Does your phone number show up under SIm info?
Click to expand...
Click to collapse
Checked APN. I have efs from November MDBO8M from when I first got phone
SwimDrewid said:
Checked APN. I have efs from November MDBO8M from when I first got phone
Click to expand...
Click to collapse
The EFS doesn't change. The original backup you have is all you need as long as you have a backup of just the EFS partition and nothing else with it. It might not fix your issue but it won't hurt anything. I tried Chroma after reading it fixed a lot of others problems with the same issue and that worked for me also. I'm still running it but others have said they were able to go back to their preferred ROM after flashing it and all was good.
SwimDrewid said:
Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.
Click to expand...
Click to collapse
Could it be a sim card issue? Have you tried remove and re-inserting the sim?
ckarrow2 said:
Could it be a sim card issue? Have you tried remove and re-inserting the sim?
Click to expand...
Click to collapse
Yep. Removed / reinserted before coming here
murphyjasonc said:
The EFS doesn't change. The original backup you have is all you need as long as you have a backup of just the EFS partition and nothing else with it. It might not fix your issue but it won't hurt anything. I tried Chroma after reading it fixed a lot of others problems with the same issue and that worked for me also. I'm still running it but others have said they were able to go back to their preferred ROM after flashing it and all was good.
Click to expand...
Click to collapse
I'll transfer to my phone and try in a bit. Any known problems going from DU to chroma? I'll try that too
ckarrow2 said:
Could it be a sim card issue? Have you tried remove and re-inserting the sim?
Click to expand...
Click to collapse
SwimDrewid said:
I'll transfer to my phone and try in a bit. Any known problems going from DU to chroma? I'll try that too
Click to expand...
Click to collapse
As long as you clean flash their shouldn't be any issues. Just go to advance wipe and select system, data, cache and dalvic. Just make sure you don't check internal storage. Then flash chroma and the recommended gapps and you should be good to go. Make a backup first and you can always just flash back to the point where you are now if it doesn't work.
murphyjasonc said:
As long as you clean flash their shouldn't be any issues. Just go to advance wipe and select system, data, cache and dalvic. Just make sure you don't check internal storage. Then flash chroma and the recommended gapps and you should be good to go. Make a backup first and you can always just flash back to the point where you are now if it doesn't work.
Click to expand...
Click to collapse
I don't have an EFS backup on my google drive (like I thought I did). I think I have the backup in the office, but not available now.
No joy on the Chroma -- still no PRL data, no phone sound on dialing, no receiving calls
At this point, I figure it's hardware related
Thanks for your help
SwimDrewid said:
I don't have an EFS backup on my google drive (like I thought I did). I think I have the backup in the office, but not available now.
No joy on the Chroma -- still no PRL data, no phone sound on dialing, no receiving calls
At this point, I figure it's hardware related
Thanks for your help
Click to expand...
Click to collapse
Have you changed any settings in the test menu? Another option would be to swap sim cards out with another phone to see if yours works in theirs and vice versa. As a last resort before you RMA you should wipe everything and flash the stock images and start fresh. Even if that doesn't fix it I think you would have an easier time with the RMA process being completely stock and relocking your bootloader.
murphyjasonc said:
Have you changed any settings in the test menu? Another option would be to swap sim cards out with another phone to see if yours works in theirs and vice versa. As a last resort before you RMA you should wipe everything and flash the stock images and start fresh. Even if that doesn't fix it I think you would have an easier time with the RMA process being completely stock and relocking your bootloader.
Click to expand...
Click to collapse
So, uh, I forgot to mention a critical piece of data: I live in Georgia, but this occurred at one of the South Carolina beaches, over 300 miles away.
I had full LTE, but noticed the phone said Not Roaming (or roaming: false).
As soon as we got home today, boom -- could make and receive calls again.
So, I think I can close this thread and open a new thread on how to get roaming to stick.
Thanks for all your help! :good:
Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.
pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.
J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs
Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.
I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.
Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps
It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.
Below is my original post; however, I've since solved the problem. In an effort to help others with the same problem, I've written a Guide, which should explain exactly what to do if your WiFi is suddenly "broken" due to flashing issues.
Here's the link: OnePlus 5 WiFi Fix
Many thanks to everyone who offered help, especially subaash and hallo dare, who put me in the right direction.
--------------------------------------------------------------------------------------------------------------------------------------
Greetings, everyone.
Sadly, for specific reasons unknown, my WiFi appears to be completely broken.
Over the last few days I've gone "flash happy" by trying several Oreo ROMs for my OP5. Some worked while others just froze at the boot animation.
Unfortunately, shortly after flashing the xXx-NoLimits Oreo ROM, which got me to the initial set-up screen, my WiFi would not connect. So, I then bypassed the WiFi part and finished the set-up. Everything seemed to be working very well, but I could not get WiFi to work.
Yes, I could engage the Wifi slider to the ON position, and there would be a list of SSIDs; however, oftentimes even my 2 SSIDs would not display. When they did, and I tried to connect, I would see the connection attempt, but it would not complete the connection. Only the word "saved" would be shown under the SSID name. Then it would automatically try to reconnect, but without success.
I've tried virtually everything I can think of to solve the problem, but I can't connect to WiFi.
All other communications work, i.e., Bluetooth, Data, making and receiving calls. It's ONLY the Wifi that's not working.
Yes, I completely wiped my device and re-installed the original OxygenOS (4.5.14), but that didn't work. I also tried completely wiping the device and then installing that latest OxygenOS v4.5.15, but that didn't solve the problem, either.
I went back and flashed all the previous custom ROMs in an attempt to see if any of them would work, but nothing. I tried NitrogenOS, HalogenOS, Liquid Remix, xXx NoLimits, and they all could not connect to WiFi.
I even tried a few WiFi Fix apps on Google Play, but they didn't work, either.
Oh, yes … I even checked my router. It's perfectly fine. I can get WiFi on my laptop without a problem. Furthermore, when I went to a local coffee shop this morning that provides free WiFi, my phone could not connect, just like at home.
Does anyone have ANY suggestions?
Thank you,
Peter
I would say this is to do with your firmware/modem.
I did have this issue on a non Oreo ROM and in the end I just did a dirty flash and it worked.
dladz said:
I would say this is to do with your firmware/modem.
I did have this issue on a non Oreo ROM and in the end I just did a dirty flash and it worked.
Click to expand...
Click to collapse
I've tried flashing both the 4.5.14 and 4.5.15 firmware, with no luck; however, I accidentally deleted my modem nandroid about a week ago.
Do you know where I might find a flashable modem file?
Thanks,
Peter
Addendum: I found the following site for Firmware & Modems:
https://www.jamal2367.com/?dir=OnePlus 5/Firmware + Modems/Android 7.1.1/OxygenOS
I'll try flashing them and report back.
Addendum 2: NOPE! Didn't work. I flashed a few different firmware & modems, 4.5.13, 4.5.14 and 4.5.15, but WiFi is still broken. Yes, I first flashed the appropriate OS version before flashing the firmware and modem. In other words, I always matched the OS version with the firmware & modem version, but no success. Everything works except WiFi. Hmm, still stumped.
PeterGuru said:
I've tried flashing both the 4.5.14 and 4.5.15 firmware, with no luck; however, I accidentally deleted my modem nandroid about a week ago.
Do you know where I might find a flashable modem file?
Thanks,
Peter
Addendum: I found the following site for Firmware & Modems:
https://www.jamal2367.com/?dir=OnePlus 5/Firmware + Modems/Android 7.1.1/OxygenOS
I'll try flashing them and report back.
Click to expand...
Click to collapse
Careful with modems mate. There's a thread here on XDA containing modems and firmwares..just make sure you get the right one.
dladz said:
Careful with modems mate. There's a thread here on XDA containing modems and firmwares..just make sure you get the right one.
Click to expand...
Click to collapse
Thanks! I'm quite aware of the need for caution with modems. Sadly, though, it didn't solve the problem.
yea my freind in idia s 1p5 was flasing anything and his oneplus 5 got weird but turns out ok googles cousin hey google had a hangover, i cleared her cache and threatened her with king root & she slowed her role, i asked her why her cousins voice is so shot out,she said ok google has a hi and low voice cuz she burnt out but now ok google took my vpn and dipped to inda for some oneplus christmas party. what ever just watch out for hey google, cuz if you got volte 5g and a vpn they b will go offline and dipp with your vpn to india. i guess india likes oneplus. hold up this is the be delighted thread?
Did you get this sorted, having the very same issue
hallo dare said:
Did you get this sorted, having the very same issue
Click to expand...
Click to collapse
Sadly, no. I've tried absolutely everything I can think of, all without success. It's very frustrating because absolutely everything else works, except WiFi.
All I can do now is wait for suggestions from others, or take the phone to a repair shop (which I'm hesitant to do).
Peter
Thanks for replying. If you happen to get it sorted, please let me know. I will do likewise if I manage to fix it. Thanks
Try reflashing the rom. Not sure why, but that happened to me and reflashing the rom fixed it.
ab7casper said:
Try reflashing the rom. Not sure why, but that happened to me and reflashing the rom fixed it.
Click to expand...
Click to collapse
Done that already, tried old roms of OOS and Oreo, but still no joy. Heads wrecked with it.
hallo dare said:
Done that already, tried old roms of OOS and Oreo, but still no joy. Heads wrecked with it.
Click to expand...
Click to collapse
Do you have a full rom backup? I mean of the last working rom you had before all the flashing? If so, from a full stock rom (1.53gb or close) of the same build as the backup (ie... 4.5.14) wipe and flash that rom, then wipe and restore the backup you have if the last working rom. If they doesn't work I think you're likely looking at a hardware issue.
Eric214 said:
Do you have a full rom backup? I mean of the last working rom you had before all the flashing? If so, from a full stock rom (1.53gb or close) of the same build as the backup (ie... 4.5.14) wipe and flash that rom, then wipe and restore the backup you have if the last working rom. If they doesn't work I think you're likely looking at a hardware issue.
Click to expand...
Click to collapse
Thanks, i'll give that a go
---------- Post added at 07:36 PM ---------- Previous post was at 07:02 PM ----------
Eric214 said:
Do you have a full rom backup? I mean of the last working rom you had before all the flashing? If so, from a full stock rom (1.53gb or close) of the same build as the backup (ie... 4.5.14) wipe and flash that rom, then wipe and restore the backup you have if the last working rom. If they doesn't work I think you're likely looking at a hardware issue.
Click to expand...
Click to collapse
Ok I done that, and now, wifi is still doing the same thing and under the network i pick it just goes to saved and then says disabled under it.
hallo dare said:
Thanks, i'll give that a go
---------- Post added at 07:36 PM ---------- Previous post was at 07:02 PM ----------
Ok I done that, and now, wifi is still doing the same thing and under the network i pick it just goes to saved and then says disabled under it.
Click to expand...
Click to collapse
Same problem but only on my 5GHz network and dont know how to fix
PeterGuru said:
Greetings, everyone.
Sadly, for specific reasons unknown, my WiFi appears to be completely broken.
Over the last few days I've gone "flash happy" by trying several Oreo ROMs for my OP5. Some worked while others just froze at the boot animation.
Unfortunately, shortly after flashing the xXx-NoLimits Oreo ROM, which got me to the initial set-up screen, my WiFi would not connect. So, I then bypassed the WiFi part and finished the set-up. Everything seemed to be working very well, but I could not get WiFi to work.
Yes, I could engage the Wifi slider to the ON position, and there would be a list of SSIDs; however, oftentimes even my 2 SSIDs would not display. When they did, and I tried to connect, I would see the connection attempt, but it would not complete the connection. Only the word "saved" would be shown under the SSID name. Then it would automatically try to reconnect, but without success.
I've tried virtually everything I can think of to solve the problem, but I can't connect to WiFi.
All other communications work, i.e., Bluetooth, Data, making and receiving calls. It's ONLY the Wifi that's not working.
Yes, I completely wiped my device and re-installed the original OxygenOS (4.5.14), but that didn't work. I also tried completely wiping the device and then installing that latest OxygenOS v4.5.15, but that didn't solve the problem, either.
I went back and flashed all the previous custom ROMs in an attempt to see if any of them would work, but nothing. I tried NitrogenOS, HalogenOS, Liquid Remix, xXx NoLimits, and they all could not connect to WiFi.
I even tried a few WiFi Fix apps on Google Play, but they didn't work, either.
Oh, yes … I even checked my router. It's perfectly fine. I can get WiFi on my laptop without a problem. Furthermore, when I went to a local coffee shop this morning that provides free WiFi, my phone could not connect, just like at home.
Does anyone have ANY suggestions?
Thank you,
Peter
Click to expand...
Click to collapse
So first of all the reason why it is broken is because of the oreo firmware that you flashed earlier. Now what you should do is flash stock recovery and flash the oreo build and boot it up and running. Once you've done that flash the rollback rom (which suppose to downgrade your oreo firmware to nougat firmware). Once you've done it basically it fixes you're wifi issue.
PeterGuru said:
Thanks! I'm quite aware of the need for caution with modems. Sadly, though, it didn't solve the problem.
Click to expand...
Click to collapse
There's a button for that son..
Also the firmware / modem will be the problem, either upgrading or rolling back..either way it'll be the cause.
ab7casper said:
Try reflashing the rom. Not sure why, but that happened to me and reflashing the rom fixed it.
Click to expand...
Click to collapse
Eric214 said:
Do you have a full rom backup? I mean of the last working rom you had before all the flashing? If so, from a full stock rom (1.53gb or close) of the same build as the backup (ie... 4.5.14) wipe and flash that rom, then wipe and restore the backup you have if the last working rom. If they doesn't work I think you're likely looking at a hardware issue.
Click to expand...
Click to collapse
Dimontiman said:
Same problem but only on my 5GHz network and dont know how to fix
Click to expand...
Click to collapse
Okay, let me first answer a couple of questions. Like I said in my first post, I DID flash the original ROM, as well as other OEM OxygenOS ROMs, all without success. Yes, I used the exact same ROM that was working perfectly before the problem. Yes, I also had a FULL Nandroid of the working system, but restoring that also did nothing to solve the problem.
Okay, with that out of the way, I went to a repair shop this morning to try and solve the problem. It was unsuccessful. The technician said it's unlikely to be hardware related because I can still get the phone to recognize all local SSIDs. I simply can't connect to any of them. Just like hallo dare said in his post a few back, when I try to connect to my SSID, it tries to connect for a second or two, and then it just shows "saved" and wifi is disabled.
So, for now I'm still completely stumped.
Peter
subaash said:
So first of all the reason why it is broken is because of the oreo firmware that you flashed earlier. Now what you should do is flash stock recovery and flash the oreo build and boot it up and running. Once you've done that flash the rollback rom (which suppose to downgrade your oreo firmware to nougat firmware). Once you've done it basically it fixes you're wifi issue.
Click to expand...
Click to collapse
dladz said:
There's a button for that son..
Also the firmware / modem will be the problem, either upgrading or rolling back..either way it'll be the cause.
Click to expand...
Click to collapse
Okay, I will do exactly what subaash said and report back. I, too, agree that it's probably software related, which is why I'm actively attacking this issue.
Be back as soon as I can.
Peter
P.S. "Son?" Hmm, I have a sneaking suspicion that I'm older than you (will be 60 in March).
Success ... maybe?
Well, well. It appears the previous suggestions were correct. So far it's successful, but I haven't quite finished the initial set-up. All I can say is that WiFi is working, and I'm grateful for that.
However, it was a frightening ordeal. At one point I thought my device was bricked, and I didn't know what to do. However, with some thought, I was able to solve the problem.
Good news, though, is that I DID NOT have to revert back to Nougat. I'm now running Oxygen Oreo 8.0.0 Open Beta 2.
I will provide a detailed instructions of what I did a bit later. I simply want to get everything up-and-running, which could take a few hours.
Here's an abbreviated version:
Downloaded Oxygen Oreo 8.0.0 Open Beta 1 from here:
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_openbeta_1/
Downloaded Stock Recovery from Post #2 here:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Copied both files above to root of device internal storage
Reboot into TWRP recovery
Flashed stock recovery in TWRP
Reboot into stock recovery
COMPLETELY Wiped the entire system ... absolutely everything ... including internal storage. This is where I had the initial problem. I did not wipe everything, including internal storage, and I ended up with a mixture of jumbled numbers and letters when looking at the file structure.
Using ADB Sideload within the stock recovery, I "moved/flashed" the ROM ZIP to the device
After successful sideload, I said yes to installing the ROM
The ROM then installed and, voila, I'm at the initial set-up screen.
Okay, that's all for now. I'll be back later.
Peter
Format data resolves the problem (at least with me...)