So I asked this question last week under the VZW LG G3 Q&A and never got any feedback so hopefully I can get some sort of response here.
http://forum.xda-developers.com/verizon-lg-g3/help/bluetooth-media-phone-lg-g3-pioneer-fh-t2920008
I recently got my LG G3 a few days ago and I've been having trouble getting media to play through my aftermarket head unit (Pioneer FH-P8000BT).
I had used it via Bluetooth with my HTC Incredible, Galaxy Nexus and Galaxy S3 all with (for the most part) no issues streaming Pandora, Google Play Music, etc. The only time Bluetooth gave me trouble is on my S3 whenever i loaded an ASOP ROM, it would have a hard time connecting but it would be intermittent. Any TouchWiz roms, no issues (the Galaxy Nexus never had any problems no matter the ROM).
With the G3 I just got I had first performed a factory reset so it's 100% stock (rooted). I had also cleared the memory on my Pioneer unit.
When first connecting, it goes through without any problems and I'm able to stream media. The moment I shut my car off then turn it back on, it's unable to connect media audio (phone still works). And it had the same issue regardless of if the app is closed out or open and even restarted the phone.
I got the unit back in 2008 so I realize it's using an older version of Bluetooth and it looks like Pioneer dropped support as there are 0 firmware updates since it's been released. I saw another post (different forum) about someone having similar issues connecting their G2 to the same HU however they responded LG had released an update and they've been working since.
I'm almost tempted to upgrade the unit but would rather wait for Android Auto to come out. Hoping anyone in the forums knows a fix and can help out.
Thank you!
Click to expand...
Click to collapse
I've tried and retried all the steps I've taken already with no success. I'd like to be able to use streaming music in my car again so I'd appreciate if anyone could help out.
I'm hoping someone can help me here. I have an T-Mo LG G3 (D851) that had been running the D85120b software from April 7, 2015. We all know that WiFi Calling was not working on that version of software, which is why T-Mo pulled it and quit distributing it after only a couple of weeks. But Bluetooth worked perfectly for me. Then on June 9, the new D85120e came out to fix the wifi calling. So I updated to the new 20e yesterday without any problems. But now, bluetooth won't work through the phone no matter what I do. Even with LG wireless headphones or in my car. I have removed all devices, re-paired all devices, everything possible. Can't place or receive calls on my headset now, nor can I place or receive calls through my car now, even though both devices say paired and connected (1 at a time of course). This just started yesterday when I upgraded to D85120e. Any ideas out there? Please help and thank you very much.
I had to delete and pair my bluetooth devices again after I upgraded to 20e. That fixed it for me.
jobella said:
I had to delete and pair my bluetooth devices again after I upgraded to 20e. That fixed it for me.
Click to expand...
Click to collapse
Thanks for the reply, but as I said in the original post, I have already done that numerous times. I have also done complete "factory" resets of both bluetooth devices (headphones and car system) and I still get the same result. I wish it had been that easy. Thanks for answering though.
Issue resolved. Just an update to close this thread. Fortunately for me, after I had upgraded to D85120e, I had done a complete TWRP backup. After that I flashed 2 TWRP zips that i wanted to use. I flashed the zip to delete Carrier IQ and the zip file by @spiderio to raise the volume level of the speakers. It was one of these zips that killed the bluetooth. ( I am guessing it was the Volume increase since that one dealt with sound issues)
In any case, I restored the TWRP backup to the system before those 2 flashes and bluetooth came back fine. I hope this may help someone else sometime. Just FYI.
My Bluetooth used to work when it was on 5.x and when I updated to 6.0.1 yesterday, my car's Bluetooth is disconnecting every couple of minutes and connecting itself back, same thing happening with my Gear S2. It stays connected for a minute then disconnects and connects back.
Anyone else facing this issue?
I'm on MM (the sideloaded version) and have never had bluetooth issues with any connection. In past updates, as much as this may suck, so many issues like this one can be fixed with a factory reset.
jack man said:
I'm on MM (the sideloaded version) and have never had bluetooth issues with any connection. In past updates, as much as this may suck, so many issues like this one can be fixed with a factory reset.
Click to expand...
Click to collapse
will try that.. thank you!
Dear XDA members,
I'm sorry for posting in this section, but since I'm new to the scene I can't post questions or topics in the appropriate section. So sorry for my noobyness..
Anyway I installed the new CM13 Nightly today. It is working great and even got the storage bug (gallery crash) fixed by removing the line ro.sdcardfs.enabled=true from build.prop (hint for anyone else needing this fix ). However I've found a bug that was stopping me from using CM13 in the first place, it was rebooting my device everytime it started up and connected to wifi... Whenever I connect to my Apple Airport Extreme the device crashes and reboots (just like the gallery bug). It is an older model Airport Extreme (the 802.11n version, so no ac wifi). It doesn't happen on the other router installed here, which is a Comtrend.
Could someone tell me where and how I report this bug or maybe even how to fix it? I haven't seen anyone else post it on the forums and it doesn't happen on OxygenOS or pre-official releases of CM13 based roms.
Thank you!
ShotByMeir said:
Dear XDA members,
I'm sorry for posting in this section, but since I'm new to the scene I can't post questions or topics in the appropriate section. So sorry for my noobyness..
Anyway I installed the new CM13 Nightly today. It is working great and even got the storage bug (gallery crash) fixed by removing the line ro.sdcardfs.enabled=true from build.prop (hint for anyone else needing this fix ). However I've found a bug that was stopping me from using CM13 in the first place, it was rebooting my device everytime it started up and connected to wifi... Whenever I connect to my Apple Airport Extreme the device crashes and reboots (just like the gallery bug). It is an older model Airport Extreme (the 802.11n version, so no ac wifi). It doesn't happen on the other router installed here, which is a Comtrend.
Could someone tell me where and how I report this bug or maybe even how to fix it? I haven't seen anyone else post it on the forums and it doesn't happen on OxygenOS or pre-official releases of CM13 based roms.
Click to expand...
Click to collapse
Thanks for the gallery fix!
The thing was driving me nuts...
I'm on the July 30th nightly and there is no issue with the WiFi connection.
Corpal said:
Thanks for the gallery fix!
The thing was driving me nuts...
I'm on the July 30th nightly and there is no issue with the WiFi connection.
Click to expand...
Click to collapse
My wifi is working fine with any other router, my op3 just crashes when I connect to my Airport Extreme..
This seems to be a persistent bug because when i connect to my Apple airport Router my phone crashes too.
Hi
I've a same problem with connection on Airport. But my ROM is Ressurection Remix (Build 30/07/16). I think that the problem is present on all CM-Based ROM.
Jesus, finally, that bug make me crazy. Airport Extreme and CM13 in my OnePlus3 crash and reboot the device. Im waiting for fix patiently.
Whit oficially ROM or based ROMS all ok.
and, THANK YOU DEVELOPERS FOR ALL.
Best regards.
P. D. - Sorry for my poor english.
Wynztech said:
Jesus, finally, that bug make me crazy. Airport Extreme and CM13 in my OnePlus3 crash and reboot the device. Im waiting for fix patiently.
Whit oficially ROM or based ROMS all ok.
and, THANK YOU DEVELOPERS FOR ALL.
Best regards.
P. D. - Sorry for my poor english.
Click to expand...
Click to collapse
Yes me too, would like to post this in the Official CM13 Forum but can't since I'm a junior member :/
This is the only problem I have, CM13 is quite stable in its current condition
Seems to only be with the airport
Same problem
Thank you! I thought I was crazy. For some strange reason i crashes hard when getting an IP address. I connect via an old Apple time capsule.
rumagent said:
Thank you! I thought I was crazy. For some strange reason i crashes hard when getting an IP address. I connect via an old Apple time capsule.
Click to expand...
Click to collapse
Old airport extreme here and Does exactly what you said. Went back to OOS for this. I went to the dentist, connected to wifi and my phone rebooted. Was a bit too annoying
ShotByMeir said:
Old airport extreme here and Does exactly what you said. Went back to OOS for this. I went to the dentist, connected to wifi and my phone rebooted. Was a bit too annoying
Click to expand...
Click to collapse
Can you post the issue on the development thread. Please. I'm too new to do so.
akiva.r said:
Can you post the issue on the development thread. Please. I'm too new to do so.
Click to expand...
Click to collapse
Already did that. Someone was supposed to look into it but didn't. I provider logs, but I guess it is nog considered a very important bug I already started a thread in the cyanogen forums so let's hope that helps.
Btw if you want to use cm, you van use Arter97's build. That build with his kernel (you Have to add it manually) doesn't have the wifi bug official CM with his kernel also doesn't have the wifi bug.
Believe to have figured out the issue
I am having this exact same problem when connecting my OP3 to my Airport Extreme. I have messed around with several different ROMs and discovered that the original Oxygen OS and Freedom OS (basically a modified version of Oxygen) don't crash when connecting to the Airport Extreme. This has happened to me in two different places, with two different Airport routers. It would connect just fine until I first updated one router to the latest version for the Airport (version 7.7.7), and then a few days later the same upgrade with the other one before realizing that this was why my phone kept crashing! Problem is, is I'm not sure what firmware of the Airport actually worked with my OP3. I've tried downgrading my Apple router (generation 7), but it will only let me go down to version 7.7.3 which still crashes the phone.
It has to be an issue with router's version, rather than a ROM issue because this only started happening with me after the Airport update. Best thing probably to do at this point is report it to Apple, and hopefully they will do something about it instead of just locking every non-apple product out of their 'Apple Products only can communicate with one another circle'... I'm unable to post an actual link to the website to report bugs to apple, so here is the link in a 'disguised' manor. apple(dot)com(ForwardSlash)feedback(ForwardSlash)airportextreme(dot)html
I just typed out a bug report myself and sent it to apple. The more people that report it, the more likely they will be to fix it. In the meantime, I also requested that they provide me with the original firmware that the 6th generation Airport Extreme came with, because I know it worked with my OP3. If I get it, and it works I'll provide a Dropbox or Google Drive link for the download on a future reply to this thread.
cquick7 said:
I am having this exact same problem when connecting my OP3 to my Airport Extreme. I have messed around with several different ROMs and discovered that the original Oxygen OS and Freedom OS (basically a modified version of Oxygen) don't crash when connecting to the Airport Extreme. This has happened to me in two different places, with two different Airport routers. It would connect just fine until I first updated one router to the latest version for the Airport (version 7.7.7), and then a few days later the same upgrade with the other one before realizing that this was why my phone kept crashing! Problem is, is I'm not sure what firmware of the Airport actually worked with my OP3. I've tried downgrading my Apple router (generation 7), but it will only let me go down to version 7.7.3 which still crashes the phone.
It has to be an issue with router's version, rather than a ROM issue because this only started happening with me after the Airport update. Best thing probably to do at this point is report it to Apple, and hopefully they will do something about it instead of just locking every non-apple product out of their 'Apple Products only can communicate with one another circle'... I'm unable to post an actual link to the website to report bugs to apple, so here is the link in a 'disguised' manor. apple(dot)com(ForwardSlash)feedback(ForwardSlash)airportextreme(dot)html
I just typed out a bug report myself and sent it to apple. The more people that report it, the more likely they will be to fix it. In the meantime, I also requested that they provide me with the original firmware that the 6th generation Airport Extreme came with, because I know it worked with my OP3. If I get it, and it works I'll provide a Dropbox or Google Drive link for the download on a future reply to this thread.
Click to expand...
Click to collapse
It was a rom issue and it is fixed in CM builds after 18/9, I tested the commit before it went live. Don't use any kernel before that date and you're fine . The Apple routers are fine haha. There was a variable defined as a wrong type, which caused a stack overflow when connecting to an airport.
ShotByMeir said:
It was a rom issue and it is fixed in CM builds after 18/9, I tested the commit before it went live. Don't use any kernel before that date and you're fine . The Apple routers are fine haha. There was a variable defined as a wrong type, which caused a stack overflow when connecting to an airport.
Click to expand...
Click to collapse
Same issue with RR.How to solve using any zip or replacing files.?
amol1223 said:
Same issue with RR.How to solve using any zip or replacing files.?
Click to expand...
Click to collapse
Flash newer kernel over it or just wait for a new build.
amol1223 said:
Same issue with RR.How to solve using any zip or replacing files.?
Click to expand...
Click to collapse
Worked. Thanks a bunch.
Hey so I've been having this issue with my Galaxy A50 where the wifi would keep hiccuping in a constant pattern, this is very noticeable when I try to stream games using either Steam Link or Moonlight, the wifi would cut for like a split second each 5 ish seconds. I did however find a workaround, and that it so enable and disable airplane mode, it would completely fix the hiccups.
So today, I regretted updating my phone so much (7th of July update), because now, the hiccups are back and they are more constant than ever. The trick I'd use to make the wifi stable no longer works, I need to keep airplane mode enabled at all times to avoid these hiccups.
I would like one of either solutions: can I fix this issue once and for all, because it's supper annoying, I tried removing my sim cards and all but the issue persists, if there is no fix for this, then I'd like to revert to the previous version I had, I have already downloaded the files from Sammobile, but I'm worried that it would brick my phone or even refuse to install period, here's the ROM that I'd like to install:
https://www.sammobile.com/samsung/galaxy-a50/firmware/SM-A505FN/SER/download/A505FNPUS5BTF1/347209/
I've explained this issue a bit better on the steam forums, so I'm gonna copy what I typed there;
Thank you very much in advance.
Okay so, recently I got a brand new Galaxy A50 phone, and whenever I'd try to stream games (over local network using WiFi) I'd get frequent and consistent hiccups that last about a split second each 3 seconds ~, I suspected that the issue could be from my phone being faulty or whatever, but I tried my brother's phone which is the same as mine, but the issue persisted.
On very rare occasions, the hiccups would not occur and the stream would be absolutely perfect, so I know for sure it might not be a hardware issue and that a stutter free experience is possible for sure, however I have no clue how to keep it consistent.
Mind you I have tried many other devices, my old Galaxy S5 and S6, even tried a Huawei phone and an Oppo phone and they all seem to work just fine, I even tried different streaming services like Parsec, TeamViewer, Moonlight etc... So the issue is certainly not my network as it is working just fine with other devices.
The A50 is a pretty popular mid-range phone so I'd expect at least someone to use Steam link (or similar apps) on it and experience this problem, yet I haven't found a single post about this issue online, the only thread that pops up is another one of mine related to this issue (on Reddit).
Can anybody help me come up with a solution? I tried quite literally everything I can, including updating my OS and all of my apps.
Thank you in advance
Click to expand...
Click to collapse