On a Motorola Moto-Z the Wlan and BT can not be activated - the 'Wi-Fi' switch does not move to the On position, and any step to use BT produces a 'Bluetooth has stopped'.
This phenomenon appeared on the stock Android 6, and remainded after installing lineage-OS 17.1.
Basic Question, device independent:
Is Wlan/BT typically controlled by software internally?
Could it be repaired by updating (a part of) the firmware?
Related
I'm having one major problem that I've been unable to solve. Every so often the bluetooth stops working and the sound locks giving error=2. Bluetooth reports "failed to turn on due to insufficient memory". If I try to increase the volume it goes back to 0. The only solution is a full hardware reset. It's happens so often I've transferred all the cab's onto a separate sd card so I can reinstall the lot without a PC.
I have a feeling it is USB related as it seems when it's stuck into a port it can on occasion initiate the problem.
The only way I've managed to sort the issue was by upgrading the bluetooth to a newer version (broadcomm_bt_stack.CAB 1.7.6) via a hack found on one of this forum, however while the sound then works the bluetooth is off completely probably because registry settings are using the wrong port etc.
Here's a list of the PDA spec:
OS: 5.01, 20061016
ROM: 1.10.15
Firm: 3.0
Bootloader: v2.17
Bluetooth: Broadcom 1.7.1 Build 8700
I have attached the bluetooth registry values (before I try to update the stack).
Any ideas???
Afternoon all.
I love my N5 and am keen to stick with it - however I have an issue with Bluetooth.
I am a keen runner and user a Garmin Forerunner 220 GPS. This has the ability to pair with a Garmin app using BTLE to transfer run data. However, Garmin are saying that there are underlying issues with the N5 implementation of BTLE that makes this unreliable - resulting in a need to re-pair the devices in the app everytime I turn BT off, or reboot the phone. Due to where I work, I have to do this every day and its a pain!
More details here: https://forums.garmin.com/showthread.php?75976-Compatible-Devices
and some of the reasons for the issues here (I was pointed to this link by Garmin in the thread above): http://au.ibtimes.com/articles/533189/20140107/nexus-5-7-android-4-kitkat.htm#.UxCieF5yFvY
So my question.... is there a ROM available that would give me the same underlying bluetooth stack as the Samsung phones that Garmin declare as compatible (S3/S4, Note2/Note3) ? Would this mean trying to put a pre-KitKat ROM onto the N5 (is this even possible?), or is there a KitKat based ROM that has the same underlying bluetooth stack as the Samsung devices ?
(ps I'm happy flashing ROMs etc. The Samsung devices I have had in the past had a different ROM most weeks! N5 is currently stock but unlocked and rooted).
Hi all,
Upon some research, i found out that some people are affected by this issue
The bluetooth metadata won't show while connecting to car interface (Mazda Connect, Ford Sync, etc), or perhaps any other bluetooth interface
Apparently other devices like several One Plus model at Nougat is also suffering from it
The related pages that talk about it are as below
forums.oneplus.net/threads/bluetooth-to-car-audio-artist-and-song-title-showing-as-unknown.498810/
talk.sonymobile.com/t5/Xperia-XZ/Bluetooth-Metadata-not-displaying-after-Nougat-update/td-p/1183263/page/3
My observation are as below:
1. Any build on stock 7.1.1 will not be able to show bluetooth metadata (Song control and connectivity is fine)
2. 7.0 (F8332_39.2.A.0.442) works fine
3. Marshmellow works fine too
Anyone has any idea to fix this?
Currently i've already backup TA, unlocked bootloader, rooted, and prepared to flash each and every ROM to find out which ROM will fix this annoying issue...
The screenshot
scontent.fkul8-1.fna.fbcdn.net/v/t34.0-12/22686531_10155051291302828_1132401615_n.jpg?oh=ccc6197274cb2dcc320d03e6fb54f0eb&oe=59EE4D61
Pls add https:// at those links as i cant input any links due to new member policy
Hey everyone, if your issues is displaying meta data in you car there is a option you can select in the developer options that fixed this for me in my 2013 Mazda 3. Once you enable developer options go to "Bluetooth AVRCP Version" and select any of the options. The option I had to choose was "1.3". After you select it you will need to restart your phone. Good Luck!
A silly question but I've been struggling to work this out across a few ROMs (all AOSP/LOS base). I can get bluetooth on, broadcast presence, find devices & connect but the dialog to confirm the key pair never appears. This means the confirmation times out on the device I'm connecting to and so it effectively doesn't work.
Anyone have any ideas on the likely source of the dialog so I can root around the apks/services that might be playing up in more depth? I thought it would've been in either Bluetooth Share or Bluetooth Midi but they're both present & unrestricted in terms of permissions, privacy and so on.
Hi,
I am trying to use Android Auto (AA) through "Headunit Reloaded for android auto" application. My phone is saying that AA is connected to the device but I'm getting these images (below) on my Android head unit version 4.4.4.
When connecting the phone to the device it appears image 1, then after I tick "Use by default for this USB device" and click OK, appear images for Microphone, Location, Phone and Settings.
Any help is appreciated.