Re: Verizon 6.0 OTA update, LG G3, after the update last month, my Bluetooth connections (three different headsets) became useless, with both parties to a call cutting in and out and the BT indicator going on and off repeatedly. After a series of complaints and escalations Verizon sent a replacement with Lollipop installed. Problem solved until VZW pushed the update to the new unit. Now I have the same trouble with BT. I am cell tech savvy but at the end of my patience. Has anyone experienced this issue and is there a fix? Many thanks.
I have not had the issue but I only connect to my car's built in bluetooth for call audio.
i had a little issue pairing to my plantronics voyager legend but it was getting the headset into pairing mode. once paired, flawless.... just make sure you turn off those stupid smart sensors on the headset. they cause tons of disconnect issues.
i also have it paired to a tone pro (HBS-730) and a JBL Clip, and pioneer headunit in my van. no issues.
Brian
Similar problem here. Since the Marshmallow update, I cannot pair to my Basis Peak fitness monitor, pair intermittently to my Aukey wireless headphones, and am getting erratic operation on my Wahoo Kickr Snap smart bike trainer.
No issues with my car (Hyundai) or Logitech boombox speaker with a clean install. Try deleting all of the Bluetooth devices from your phone, then delete the phone profile from the device if possible, power cycle both and pair again.
Third G3 VS985 in a row broken by MM update!
(I am the OP this thread): Third replacement unit has BT issues following the 46A update. VZW "2nd tier tech support" claims no one else has reported this issue, which is, of course, bull****.
I have an appointment in early March with an attorney who does consumer class action work. No guarantees, but she is interested in hearing more. Anyone else experiencing similar problems should message me. Thanks.
wjanowski said:
Similar problem here. Since the Marshmallow update, I cannot pair to my Basis Peak fitness monitor, pair intermittently to my Aukey wireless headphones, and am getting erratic operation on my Wahoo Kickr Snap smart bike trainer.
Click to expand...
Click to collapse
Same here (but Motorola Moto G 3rd Edition 2015 with OTA Marshmallow) . I suspect that Basis Peak is just not fully compatible to Android 6.0.1 in general.
BT issue on Marshmallow update
I have found that my G3 will now not pair with devices that use a dedicated app to pair with the phone. All other devices seem to pair normally.
I have 2 devices that use a dedicated app to sync over BT and they will not connect.
I have 2 devices that sync using the basic BT pairing method on Android and they connect no problem.
I wonder if there is an added security setting in Android 6.0 that is blocking these types of connections.
I had the same problem - won't connect to my Basis Peak, but is fine with my Pioneer radio after the update. I opened a helpdesk ticket with Basis, and here is their response:
I hope you are well. We have discovered that there is a connectivity issue with the LG G3 phone.
In mid-February, Verizon upgraded its LG G3 users to the newest Android operating system, Marshmallow (Android 6.0.0). Following this update, Verizon LG G3 customers, now running 6.0.0, became unable to sync or pair with their Basis Peaks.
When Basis became aware of this issue, our Android team began running tests to determine what was causing the incompatibility. Our team discovered that the LG G3 has trouble maintaining a stable bluetooth connection when running 6.0.0. The Peak uses a secure communication link to transmit data to your phone, which requires a more complex connection process. What is happening is that the unstable bluetooth connection of a LG G3 running 6.0.0 tends to drop before the secure communication link can be established, thus the Peak can neither pair nor sync with the phone.
Several other BT devices are having difficulties with the LG G3 handset running 6.0.0. The company, Tile, saw a BT issue with 6.0.0 and they worked with Google to develop a fix which is being rolled out with 6.0.1 While Tile’s issue was not specifically related to the LG G3, we believe that the next Android release may resolve the issue we are experiencing, as we have several customers who are able to sync while on 6.0.1.
(More information about Tile’s 6.0.0 issue can be found here: (I can't post URL's yet...)
We currently are working towards being able to validate that 6.0.1 will resolve the communication issue between the LG G3 and the Peak.
We take this situation very seriously and will update you as soon as we know more. We appreciate your patience.
Verizon pushed update to 47A today, BT issue unchanged
I was hopeful when I saw a new system update to the LG G3, but it doesn't help the Bluetooth issue with 6.0...
My JBL Flip worked fine with 46A but only supports call audio with version 47A.
Why has Verizon Wireless abandoned customers using the LG G3?
Verizon Wireless customers using the LG G3 (VS985) received a mandatory update to "Marshmallow" (6.0) earlier this year. Following the update, four of my five Bluetooth devices no longer worked reliably. Verizon referred me to LG, which in turn suggested that I contact Google.
I discovered (on this forum and Verizon's own) a large number of Verizon customers complaining that they too have had their Bluetooth functionality badly reduced. Some of us have spent additional money on higher priced devices in order to use the phone legally on the road. My hearing aid connects to the phone via BT, so I'm s*** out of luck.
Verizon's troubleshooting steps do not address the problem. There is an apparent solution in 6.0.1, but Verizon declines to make it available on the G3.
Having worked in the wireless industry, I believe nothing is pushed to Verizon customers until and unless it has been vetted and approved by the carrier. My educated guess is that Verizon failed to do proper diligence and wants to get out from under the problem by dropping support for the G3 and suggesting that customers pay to "upgrade" to a newer model.
Within the next few days, I'll be moving my numbers to one of their competitors. Verizon Wireless has failed to support a large group of its customers and deserves to lose them.
bobgowa said:
Within the next few days, I'll be moving my numbers to one of their competitors. Verizon Wireless has failed to support a large group of its customers and deserves to lose them.
Click to expand...
Click to collapse
I understand what you're saying, and the frustration. If I were in the same position, I'd downgrade to 10B, root and put @xdabbeb_vs985_2.0.0 ROM on (based on 35B). All carriers tend to not care anymore once they've delivered what they expected to be their last OTA to a device.
roirraW "edor" ehT said:
I understand what you're saying, and the frustration. If I were in the same position, I'd downgrade to 10B, root and put @xdabbeb_vs985_2.0.0 ROM on (based on 35B). All carriers tend to not care anymore once they've delivered what they expected to be their last OTA to a device.
Click to expand...
Click to collapse
I'd love to. However, while I'm pretty capable with RF technology, this is above my pay grade and I don't know anyone who can do it for me. Any ideas out there?
I'm pretty tired of my LG G3 which I've owned now for a few months.
I started off on the stock Kitkat it came with. Connectivity with Verizon 4g was fine, but the phone overheated regularly.
Then I updated to Fulmics 5.2, which worked okay, but only gave me slow 3g data.
Next I reverted all the way back to stock 10b, and then tried Xdabebb's Stock 47a. The rom works fine, but 4g connectivity is ****! I get constant blinking triangles (roaming) even though roaming is turned off. Worse yet, I don't get phone calls or texts half the time, and it constantly loses data connection. I got a new sim card, which works fine in my Nexus 6, but fails to be consistent in my LG G3.
Here's my questions:
1. Is there a fix with XDAbebb's 47a? Should I reflash the 35b bootstack?
2. If XDAbebb's 47a is the problem, is there a ROM that people have had good Verizon experience on?
3. Or should I just sell my LG G3 and move onto another phone or go back to my nexus 6 (which I like but it's so huge!)
I don't want to waste a lot of more time on this.
Wasn't this already answered in your other thread?
http://forum.xda-developers.com/verizon-lg-g3/help/fulmics-5-2-verizon-4g-fix-t3383242
Isn't your phone an international phone and not really the VS985? I'm only going by what was stated in the other thread where you were asking about getting Fulmics to work with your phone.
Thread reopened.
I had two G3s where the celluar, Wi-Fi and GPS radios had connectivity issues for 5 to 6 months before eventually not connecting at all. After the 2nd G3 did this I was bumped up to a G4 and now connectivity issues are happening again. The tech at the AT&T store mentioned he found an article stating the G3 and G4 have the same exact radios. This time when I go in for troubleshooting they may stick me with a G5, but now I'm weary that it shares the same radios components as the previous generation. Can someone confirm that the G5 does not share the same radios as the G3/G4?
These tablets were exclusive to Verizon as I understand it. I posted this to XDA Assist but perhaps this is the better location.
I have used my tablet for most of the time I've had it without a SIM. It's fine except I can't get any updates to Android. I'm a T-Mobile customer and I recently got a SIM, hoping that would help get the update. (I've had lots of Xperia phones and they all--except the Z3--got updated to Marshmallow over T-Mobile's network.) Sadly, it did not. I've spent quite a lot of time on the phone with T-Mobile, Sony, and Verizon. I've googled the issues and found no solution other than getting a Verizon SIM. But that costs $40 and will be non-refundable.
When I try searching for an update via wifi, I get "Error during DM session."
When I try searching via T-Mobile's data network, I get "No network found."
T-Mobile suggests a factory reset. But what I've read says that will do nothing but cause me to have a headache putting it all back the way I want. Sony says to contact Verizon. Verizon says to contact Sony, find a friend with a Verizon SIM I can borrow, or ask a Verizon store to borrow a SIM until I get the update.
My 13yo thinks-he-knows-everything son, thinks he can do it with button combinations (power-volume, etc.) but I won't hold my breath. I had an issue with this tablet in July which kind of messed up things like that. It powered all the way down due to an issue with our rental car's power ports. Then, after charging on a magnetic charger for hours, wouldn't turn on. I plugged in a USB and it still wouldn't turn on after charging. No lights no nothing. Eventually learned about the little button beside the SIM card slot and it came on again. But will it not charge on magnetic chargers anymore and it doesn't not want to cooperate with those button tricks.
Like the title implies, I was using a galaxy s7 to connect. Now that I have upgraded, I have not been able to connect to the adapter as usual. I have upgraded firmware on the adapter to the current version. The phone also updated to its most current version. I have been able to connect to a Samsung tv via smart view. It holds the connection.
I see on Microsoft's website that listed for Android support only goes to version 5.0. Why would this protocol not work though... thought it was standard.
Anyone have suggestions?
Anyone using another dongle to connect direct to tv without having Wi-Fi available?
Regards
That is the same problem for me. I wish I had a solution. It worked perfectly yesterday. Today my note 8 got the oreo update. Now i connect, shows the screen mirror as normal, but disconnects after about 2 seconds.
Microsoft wireless firmware is 2.0.8350. Wish I could roll back the android update.
Not getting much response on here but I think I found that Samsung has stopped supporting MHL a crucial protocol for using anything other than Samsung's smart view connectivity or Google Chromecast. These are not the best options for me and a serious setback for a new phone and operating system. I hope they change their mind if not I may be looking at other options.
Many are ditching the old protocols. You just got on it at the start.
Do you happen to know if there are any non-wifi dependent screen mirror options (either wired or wireless) that will work to an hdmi source?
I guess the usb-c to hdmi would still work. Miracast is the component no longer available?