Database Users

Bluetooth audio dropping out on DI07?

Anybody else having problems with keeping Bluetooth audio working after the DI07 update?
I'm on a replacement phone and my A2DP headset seems to lose sound after a while of inactivity and needs to be re-paired. The previous phone was on DG27 and didn't have this issue, so I'm guessing the update had something to do with it.

lordsandwich said:
Anybody else having problems with keeping Bluetooth audio working after the DI07 update?
I'm on a replacement phone and my A2DP headset seems to lose sound after a while of inactivity and needs to be re-paired. The previous phone was on DG27 and didn't have this issue, so I'm guessing the update had something to do with it.
Click to expand...
Click to collapse
I have noticed this also. Cuts out during calls also.

Yep have this problem as well. Very very annoying.
Sent from my SPH-D700 using XDA App

Crap, guess that justifies trying an overclocked DG27 kernel to see if it fixes the issue. Not like GPS was resolved with the update anyway.

I also have the problem. Hope it gets addressed soon.
Sent from my Epic 4g

Flashing a rooted kernel didn't help, I think it's the DI07 baseband that's screwing up. May revert to DG27 stock later to see what happens.

lordsandwich said:
Flashing a rooted kernel didn't help, I think it's the DI07 baseband that's screwing up. May revert to DG27 stock later to see what happens.
Click to expand...
Click to collapse
I'm still running DG27 and this issue is present here also. Except when I was running DI07, I would also get soft re-boots while connecting or disconnecting to and from Bluetooth devices.

Restored to stock DG27, applied one-click ClockworkMod and flashed Mixup kernel. So far things seem stable unless I start restoring the system and data images from my DI07 Nandroid backup.
I'm going to test my user apps one at a time to see if any of them was affecting the Bluetooth audio, however unlikely that may be.
EDIT: Looks like stock DG27 solved it, music apps are all running fine.

Has anyone with this problem tried upgrading to DI18 to see if Bluetooth is fixed? I'm a little hesitant to try now that I've got everything working again.

I am running D118 with MixUp nonvodoo kernel. I just install a bt headunit tonight and tried bt audio. I have audio drop out but I also restored apps and data with Titanium Backup. I dont't know if that makes any difference. I tried a call with bt and that seemed fine.

Toggle Speaker Phone Outgoing Calls

I've tried all the leading ROMS based on DK28 and all seem to have on re-occurring issue.
When I place a call about 75% of the time I have have no audio until I toggle the speaker phone. Usually I toggle back to the handset just in time to hear "hello... helllo?"
Am I alone on this? I've flashed back to stock using ODIN and then to a ROM, and every combination in between but nearly every ROM has this issue yet stock 2.1 does not. Thoughts?

Have you ever flashed cyan rom? I did and I have the same problem.. =(

sasha101 said:
Have you ever flashed cyan rom? I did and I have the same problem.. =(
Click to expand...
Click to collapse
I have not, I use MMS and the camera to much to use CM.

I have that issue also I think it's a bug ... Also the end call hangs hate that
Sent from my SPH-D700 using XDA App

It's a bug on dk28 there was a previous thread on this and a lot of people had it including mysel.

I have that bug too but 75% of the time sounds high to me. It happens to me around 30% of the time.

OKi doki, as long as I'm not alone.

If I just wait a sec, and let the call timer start before I put the phone to my head, it usually doesn't need the spkr toggle trick... I think its the prox sensor that is a lil finicky
Sent from my SPH-D700 using XDA App

I have this bug as well and it's atrocious when trying to stream audio via bluetooth, then I get a call, then try to resume bluetooth, or another call, or speaker phone.. i have to reboot the phone for it to return to normal.. otherwise I get so upset that I wanna smash my phone w/ a brick.

Two phones, two paths, fixed same way ... my wife and I have the same phone, I did the odin flash via download mode and the dk28 from sprints website. I updated hers via the "update.zip" found on the one click root and update thread. Her phone has this issue and no gps. My phone works fine, calls gps, BT audio and HF. Once I flased her phone, with the same file I did mine with, everything worked fine. Nothing fancy. Hope this helps.
Sent from my SPH-D700 using XDA App

i.mykol said:
Two phones, two paths, fixed same way ... my wife and I have the same phone, I did the odin flash via download mode and the dk28 from sprints website. I updated hers via the "update.zip" found on the one click root and update thread. Her phone has this issue and no gps. My phone works fine, calls gps, BT audio and HF. Once I flased her phone, with the same file I did mine with, everything worked fine. Nothing fancy. Hope this helps.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Where do you find the dk28 from sprint's website ?
dk28 is a leak, therefore wouldn't be available via sprint's website AFAIK

[Q] GPS reset utility?

Does anyone know of a utility to reset the internal GPS completely?
I use location-based tools all the time, and this annoying GPS failure in EC05 is a real PITA.
I know some folks have had some luck doing a "cold start" using the GPS Status utility, but this has not worked for me.
Symptoms are that the GPS works fine for a while, then loses lock. Going into GPS status reveals no satellites visible at all, and the GPS icon on the notification bar is gone..
Using Menu/Tools/Manage A-GPS state I have tried both reseting the state (cold start) and downloading assistance data. Turning the GPS off and on again also does nothing. OTOH, if I simply reboot the phone, the GPS comes back right away.
Many have reported this issue was fixed in EB13, but came back in EC05. I'm running SRF 1.1 right now, but I also had this problem in the stock EC05 that I received OTA.
Having the GPS just work properly all the time would be ideal. But short of that, being able to restart it from scratch without having to reboot the phone would be an acceptable workaround. Even a command-line utility would be better than nothing.
-Sean

It's aggravating... I have the issue and I too am waiting for some kind of fix/workaround.

I use my GPS at my evening job pretty extensively. I suffered from this issue on DI18 ROMs daily, but I haven't experienced it yet since the dk17 froyo beta.

Exact same problems here. I am on Bonsai 4 but have also had the same problem with all the other EC05 roms I've flashed and the stock EC05. It was fantastic while it was working in EB13.

fnordsnafu said:
Exact same problems here. I am on Bonsai 4 but have also had the same problem with all the other EC05 roms I've flashed and the stock EC05. It was fantastic while it was working in EB13.
Click to expand...
Click to collapse
To those still having this issue, what method did you use to get to EC05?

It came back in ec05 because people didn't use the fixes we used in going from di18 > dk28 > eb13. Search these threads and do what we did and you won't have the problem either.
Sent from Bonsai 7.0.3

mattallica76 said:
To those still having this issue, what method did you use to get to EC05?
Click to expand...
Click to collapse
I was on whatever the stock Eclair release was out of the box -- bought the phone literally the day after Sprint suspended the EB13 OTA rollout.
I got EC05 pushed to me OTA a month later. GPS had the same issue on Eclair and EC05.
To get from the OTA EC05 to SRF I had to Odin back to EB13, but I only had EB13 on the phone for a few minutes -- did not test the GPS behavior.
-Sean

mattallica76 said:
To those still having this issue, what method did you use to get to EC05?
Click to expand...
Click to collapse
I've tried a few things.. but at present, I went back to stock Eclair through Odin, then took the OTA to EC05.
Basically, I installed clean, so it's a mystery to me why others don't have this. Actually I think quite a few do, but haven't realized it yet... because the first time you get a fix after boot, it works magnificently well... 3-10 seconds. Great.
It's the down time after that, the hours that pass after that first fix that seems to change things. Without doing anything specific, just using the browser and other things.. the ability to AGAIN get a fix is hindered. Sometimes the GPS doesn't get one at all.
I'll let all the smart guys work on this one. I'm just a competent end user with no real knowledge of how the GPS works.

Just wanted to chime in..
I was waiting for someone to bring up this issue. Symptoms identical to OP's. Stock eclair worked perfectly, and this problem appeared in eb13, after a manual update. Ec05 did not change a thing and Gps status cold start did not help either.
This sucks since I use gps all the time.
Sent from my SPH-D700 using XDA App

PowderedToast said:
Just wanted to chime in..
I was waiting for someone to bring up this issue. Symptoms identical to OP's. Stock eclair worked perfectly, and this problem appeared in eb13, after a manual update. Ec05 did not change a thing and Gps status cold start did not help either.
This sucks since I use gps all the time.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
As I noted above, I'm not a real gifted technician.. but I'm guessing this issue has something to do with the internal compass. I noticed that my two co-workers who both bought the Epic based on their favorable impressions of my phone, had issues with screen rotation after going from stock Eclair to EC05. Neither are advanced users. Neither rooted or otherwise messed with their phones. I too have tinkered with the compass.. the upside-down calibration and the terminal command pertaining to Yamaha.
I can effect the quality and time of the fix by waving the phone in a figure eight pattern in an attempt to calibrate.. so I'm thinking it's all related.

Running SFR 1.1.0 and I haven't experienced this yet. Took a three hour walk yesterday and CardioTrainer locked me the entire time even through the trails.
How long does it usually take for GPS to lose lock?
If it matters, I only enable GPS, not network-based location.

othan1 said:
Running SFR 1.1.0 and I haven't experienced this yet. Took a three hour walk yesterday and CardioTrainer locked me the entire time even through the trails.
How long does it usually take for GPS to lose lock?
If it matters, I only enable GPS, not network-based location.
Click to expand...
Click to collapse
On DI18 based ROM's, the GPS data cache would not flush itself properly and you would lose GPS functionality usually within hours after it seemed to be working fine. My evening job I work as a delivery driver, and I would have to reboot my phone a couple times a night because of this bug. But as I stated earlier in this thread, I have not experienced this bug since dk17. I did experience some issues in DK28 where the GPS signal would drop out for a few seconds here and there, but since EB13, it's been perfect. No issues. My other Epic is stock EC05, so I will run some tests with that one tonight to see if I can get it to foul up.

So is anyone running Bonsai 4 experiencing this problem at all?
My understanding is that Bonsai uses an EB13-based kernel with only select EC05 elements, so perhaps it is not prone to this issue. If that's the case, that may be enough to make me switch to Bonsai from SRF.
It would also appear that the problem is not universal across all EC05 (and EC05-based ROM) users, as there have been several reports in this and other threads from people with no GPS problems at all. This makes me wonder, among other things, whether or not some specific app or module is either causing (or clearing?) the problem. Since lots of folks on stock OTA have the issue, that would likely be an OEM app.
This problem is a real PITA for me as I use the GPS all the time. Really, really want to find a solution.
-Sean

slwelsh said:
So is anyone running Bonsai 4 experiencing this problem at all?
My understanding is that Bonsai uses an EB13-based kernel with only select EC05 elements, so perhaps it is not prone to this issue. If that's the case, that may be enough to make me switch to Bonsai from SRF.
It would also appear that the problem is not universal across all EC05 (and EC05-based ROM) users, as there have been several reports in this and other threads from people with no GPS problems at all. This makes me wonder, among other things, whether or not some specific app or module is either causing (or clearing?) the problem. Since lots of folks on stock OTA have the issue, that would likely be an OEM app.
This problem is a real PITA for me as I use the GPS all the time. Really, really want to find a solution.
-Sean
Click to expand...
Click to collapse
I'm currently running on one of my Epics a modified version of Bonsai 4.0.1, which is fully EC05 based, and I'm not having any gps problems.
Sent from my SPH-D700 using Tapatalk

Same here. My GPS works flawlessly. I used yo have to use my wife's evo gps on di18 but now I dont
mattallica76 said:
I'm currently running on one of my Epics a modified version of Bonsai 4.0.1, which is fully EC05 based, and I'm not having any gps problems.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Sent From My Evo Killer!!!

slwelsh said:
Does anyone know of a utility to reset the internal GPS completely?
Click to expand...
Click to collapse
If you just want to reset your GPS cache data, there is an onboard utility invoked by a dialer code. Open your phone dialer and punch in
##GPSCLRX#
That opens a dialog that requires you to key in the MSL code for your phone. Normally the Sprint support desk has to give this to you. (If they do, write it down for future use.) There are other methods to find the MSL, including this one.

mattallica76 said:
I'm currently running on one of my Epics a modified version of Bonsai 4.0.1, which is fully EC05 based, and I'm not having any gps problems.
Click to expand...
Click to collapse
Thanks for that data point, but I was really asking about stock Bonsai, since if I switch, that's where I'd go.
boomerbubba said:
If you just want to reset your GPS cache data, there is an onboard utility invoked by a dialer code. Open your phone dialer and punch in
##GPSCLRX#
That opens a dialog that requires you to key in the MSL code for your phone. Normally the Sprint support desk has to give this to you.
Click to expand...
Click to collapse
Thanks, I have the MSL. I've also now placed a shortcut on the home screen directly to this utility, which actually bypasses the MSL. From Launcher Pro, long press on a blank area then select Shortcuts/Activities/com.android.hiddenmenu/GPSCLRX.
We'll see if using this GPSCLRX utility brings the GPS back to life next time it locks up.
While I am on the hiddenmenu subject, does anyone know which module is the GPSsetup utility? Supposedly this ships with the phone, and was previously (pre-Froyo) invoked with the dialer code *#1472365# but, according to threads on some other Galaxy-S forums, Samsung changed the code due to customer abuse. The alleged replacement code does not work for me, and I've tried all the obvious modules in hiddenmenu with no success.
In the interim, I've flashed LBSTestMode, which seems to work fine for reading and testing the GPS chipset, but is purportedly for a different chipset and so it is not clear if it can actually change settings (see androidforums.com/samsung-epic-4g/308885-gps-aquistion-ec05.html).
-Sean

slwelsh said:
While I am on the hiddenmenu subject, does anyone know which module is the GPSsetup utility? Supposedly this ships with the phone, and was previously (pre-Froyo) invoked with the dialer code *#1472365# but, according to threads on some other Galaxy-S forums, Samsung changed the code due to customer abuse. The alleged replacement code does not work for me, and I've tried all the obvious modules in hiddenmenu with no success.
In the interim, I've flashed LBSTestMode, which seems to work fine for reading and testing the GPS chipset, but is purportedly for a different chipset and so it is not clear if it can actually change settings (see androidforums.com/samsung-epic-4g/308885-gps-aquistion-ec05.html).
Click to expand...
Click to collapse
Does nothing show up in LauncherPro with a name like GPSSetup or GPSsetup?

slwelsh said:
Thanks for that data point, but I was really asking about stock Bonsai, since if I switch, that's where I'd go.
-Sean
Click to expand...
Click to collapse
As of last night, that version is now stock Bonsai.

boomerbubba said:
Does nothing show up in LauncherPro with a name like GPSSetup or GPSsetup?
Click to expand...
Click to collapse
I could not find anything. The only Activity I saw with GPS in the name was the aforementioned GPSCLRX. However I should note that I am on SRF 1.1.0, and it is possible that K0nane removed this module from the ROM. Does anyone know if it is in the stock EC05 build? Also, what's the .apk named, so I can try to find it and load it?
-Sean

[Q] CM 10.2 mic and hear speaker audio not working on phone calls

Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.

I have you seen s you. Have you found a solution yet? When I use a bluetooth headset it works Fine

You need to update your radio
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931

wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app

SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I was having this issue as well, and that worked perfectly! Thanks man!

*system error* said:
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I tried that and that app and messed with different settings and it didn't work. I'm gonna try updating the radio and see what that does.

SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
That worked actually. Thanks!

SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
Huge thanks for this one. I had been searching google for a solution to this one for a week or so now. I will have to say, the most annoying thing I've had to deal with in quite some time. I should have just come to XDA first like an adult.

T-mobile s4
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?

Try the T-Mobile S4 Forum
ptsite said:
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Click to expand...
Click to collapse
Sorry, but I don't know if this applies to the Samsung S4. I would try posting over in the T-Mobile Galaxy S4 forum.

Exclamation mark on Wifi/Signal icon

I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.

tluley51 said:
I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.
Click to expand...
Click to collapse
That's means your router has no Internet not the phone. It's your WiFi router losing its Internet connection. Without seeing your setup I can only speculate as to the exact issue.

Gizmoe said:
That's means your router has no Internet not the phone. It's your WiFi router losing its Internet connection. Without seeing your setup I can only speculate as to the exact issue.
Click to expand...
Click to collapse
There are 2 problems with that. All my computers and other phones in the house do not have this problem, so it definitely is not the router. Also, I am not always connected to my home router. I will be on my commute to work (no wifi) and it will happen. Hell, it will happen AT work and we have an enterprise network with update to date Cisco switches and APs.

tluley51 said:
There are 2 problems with that. All my computers and other phones in the house do not have this problem, so it definitely is not the router. Also, I am not always connected to my home router. I will be on my commute to work (no wifi) and it will happen. Hell, it will happen AT work and we have an enterprise network with update to date Cisco switches and APs.
Click to expand...
Click to collapse
Rma then. It's not normal.

Gizmoe said:
Rma then. It's not normal.
Click to expand...
Click to collapse
Funny thing is, I am back to unrooted stock and it instantly goes away. I was having the issue last night and into this morning on my home Wifi, on my way to work, then at work on LTE and when on the Wifi. I reverted the phone back to stock and now all is well. Why would a custom rom have something to do with not connecting to Google Services??

tluley51 said:
Funny thing is, I am back to unrooted stock and it instantly goes away. I was having the issue last night and into this morning on my home Wifi, on my way to work, then at work on LTE and when on the Wifi. I reverted the phone back to stock and now all is well. Why would a custom rom have something to do with not connecting to Google Services??
Click to expand...
Click to collapse
There could be many reasons. Custom Roms are modified and usually have custom kernels. Lots of stuff can go wrong. It's the risk of flashing custom Roms. I find with the 6p, stock rooted is the best. There isn't anything you can't do between xposed and root access. Each time I try a rom I have radio issues to be honest. I just stay stock.

That's a good call. Really the only thing I want root for is theming and double tap to wake, both can be achieved without custom rom (I believe)
Although I use Android Pay and even with systemless root, I am unable to get it to work....So maybe I should stay stock for awhile, but that is for another thread.
Appreciate your help, Gizmoe!

tluley51 said:
That's a good call. Really the only thing I want root for is theming and double tap to wake, both can be achieved without custom rom (I believe)
Although I use Android Pay and even with systemless root, I am unable to get it to work....So maybe I should stay stock for awhile, but that is for another thread.
Appreciate your help, Gizmoe!
Click to expand...
Click to collapse
I think Google has updated the safetynet API that prevents Android Pay working with Systemless root. I had it working until the latest update of Android Pay.

tluley51 said:
I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.
Click to expand...
Click to collapse
I see you are running Pure Nexus, seems you are not the first to have an issue with wifi. Beans has suggested a potential fix.

SlimSnoopOS said:
I see you are running Pure Nexus, seems you are not the first to have an issue with wifi. Beans has suggested a potential fix.
Click to expand...
Click to collapse
Unfortunately, I had tried that. I am not even sure it is Wifi related though as I was getting the ! on my cell signal as well when I wasn't even on wifi.

tluley51 said:
Unfortunately, I had tried that. I am not even sure it is Wifi related though as I was getting the ! on my cell signal as well when I wasn't even on wifi.
Click to expand...
Click to collapse
Hmm, that is unusual. Is this all occurring with the matching Vendor.img to the Pure Nexus build you are using?
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Hmm, that is unusual. Is this all occurring with the matching Vendor.img to the Pure Nexus build you are using?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes, it was. I have reverted back to stock unrooted and I am no longer having the issue. I did not want to do this, but unfortunately I have to actually use my phone as a phone and need the basic functionality that I was losing with the continuous issue.

tluley51 said:
Yes, it was. I have reverted back to stock unrooted and I am no longer having the issue. I did not want to do this, but unfortunately I have to actually use my phone as a phone and need the basic functionality that I was losing with the continuous issue.
Click to expand...
Click to collapse
I suggest trying another rom and testing that out. May help you isolate the problem. Perhaps its has to do with 2.4 ghz vs. 5.0 ghz Wi-Fi networks, either can be forced in Wi-Fi settings. Or it may be a conflict with a mod in Pure Nexus if this does not occur on another rom.
Sent from my Nexus 5X using Tapatalk