Related
After playing for a while the wifi just turns off and so does Bluetooth. I cannot turn it back on (especially wifi as the selector is greyed out) Bluetooth is selectable but turns off within a second of turning on. This is the second time I'm having this issue. I've tried clearing cache. I'm on stock Android 4.3 JSS15R. The only thing I haven't tried is a factory reset. Anyone else with this issue ? Need help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update 1: Factory Reset did not help. Still no wifi !
Update 2: After the factory reset my Wifi doesn't work and i cannot get past the welcome screen (which needs wifi connectivity). Great work *Google* [email protected]#[email protected]$
Any ideas ppl ? coz i', sh*t out of 'em.
Interesting... I have a similar experience but my WiFi doesn't turn off - I just lose the ability to transmit/receive data.
When I first heard that the Nexus 7 2013 could use a bluetooth keyboard AND mouse I jumped on purchasing the device. Of course, once both were connected, bluetooth lagged out and repeated keys and the mouse lagged - but if I used ONE bluetooth device it wasn't a problem. However, when I went home to my 5Ghz router, I could connect bluetooth headphones, keyboard, mouse, AND surf the web without a problem.
So it looks like Bluetooth and WiFi share the 2.4Ghz antennae? I haven't had my WiFi shut off but I've had issues if I connect more than one bluetooth device to my Nexus 7 while connected to a 2.4Ghz network. I can have 1 device connected just fine (usually bluetooth headphones).
I'm actually not sure whether to get a replacement or wait for a fix ?! It's basically as good as bricked 'coz im stuck at the welcome screen and no way to even test the hardware.
One thing i had noticed however was the mac address was "unavailable". So does that mean the hardware has failed ? or the OS is broken ?
BigMcGuire said:
Interesting... I have a similar experience but my WiFi doesn't turn off - I just lose the ability to transmit/receive data.
When I first heard that the Nexus 7 2013 could use a bluetooth keyboard AND mouse I jumped on purchasing the device. Of course, once both were connected, bluetooth lagged out and repeated keys and the mouse lagged - but if I used ONE bluetooth device it wasn't a problem. However, when I went home to my 5Ghz router, I could connect bluetooth headphones, keyboard, mouse, AND surf the web without a problem.
So it looks like Bluetooth and WiFi share the 2.4Ghz antennae? I haven't had my WiFi shut off but I've had issues if I connect more than one bluetooth device to my Nexus 7 while connected to a 2.4Ghz network. I can have 1 device connected just fine (usually bluetooth headphones).
Click to expand...
Click to collapse
rednav said:
I'm actually not sure whether to get a replacement or wait for a fix ?! It's basically as good as bricked 'coz im stuck at the welcome screen and no way to even test the hardware.
One thing i had noticed however was the mac address was "unavailable". So does that mean the hardware has failed ? or the OS is broken ?
Click to expand...
Click to collapse
Wow that's terrible - as soon as I stop the multiple bluetooth device interference, my wifi comes back. Not being able to see the mac address seems like a hardware problem to me too. If I were you, I'd wait to see if anyone else replies to this forum, and if no one responds by end of work today, I'd take your device into the store - show them what it is doing and get a replacement.
BigMcGuire said:
Wow that's terrible - as soon as I stop the multiple bluetooth device interference, my wifi comes back. Not being able to see the mac address seems like a hardware problem to me too. If I were you, I'd wait to see if anyone else replies to this forum, and if no one responds by end of work today, I'd take your device into the store - show them what it is doing and get a replacement.
Click to expand...
Click to collapse
Update 1: I was so frustrated that I used the nexus 7 toolkit and unlocked the boot loader and reinstalled the entire JSS15R (stock rom). It still didn't work.
All of a sudden Wifi appears and all works well. I'm seriously confused. I'm still gonna get a replacement.
Update 2: After setting up my accounts Wifi and Bluetooth dead again.
So, i have 2 different vehicles that have Bluetooth calling. When i get in my car, the vehicle connects to my phone and i can make and receive calls through the car and the sound goes through the speakers. Now that my watch is connected as a calling device with the new speaker activated, my vehicles will not connect to my phone. The only i can think of around this is to disable the Bluetooth or enable airplane mode on the watch which is a real pain every time i get it my car. Anyone else have this issue and a solution?
Same here, the car will connect to the phone but will then disconnect. This keeps repeating. If I turn watch off, car connects to phone OK.
Sent from my SM-G928F using Tapatalk
Oh, that's bad! But it's somehow also logical. The phone can only be connected to one handsfree/handset device at a time. Even so the car audio is the better choice, the phone does not know this, and will just stay connected to the watch.
Have you tried to connect to the car audio by the BT menu on the smartphone? You car audio is listed under paired devices and you can connect to it manually.
Maybe it will also remember this decision.
---------- Post added at 08:26 PM ---------- Previous post was at 08:16 PM ----------
Just searched a bit on the internet. The problem is not new, as people with headsets and a BT car stereo experienced the same problems in the past, so maybe there is already a solution for this. I quickly searched and found a potential solution by apps, that manage the BT connection and offer prioritization, like this one claims to be capable of: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
Maybe this is also something you may investigate into.
I'm very interested on a solution, because I drive a lot of rental cars and I usually connect my phone to the car stereo (if available).
Completely disconnecting the watch is not an option for me, as one reason for buying the watch was to get quick notifications also when I'm in the car.
foo said:
Oh, that's bad! But it's somehow also logical. The phone can only be connected to one handsfree/handset device at a time. Even so the car audio is the better choice, the phone does not know this, and will just stay connected to the watch.
Have you tried to connect to the car audio by the BT menu on the smartphone? You car audio is listed under paired devices and you can connect to it manually.
Maybe it will also remember this decision.
---------- Post added at 08:26 PM ---------- Previous post was at 08:16 PM ----------
Just searched a bit on the internet. The problem is not new, as people with headsets and a BT car stereo experienced the same problems in the past, so maybe there is already a solution for this. I quickly searched and found a potential solution by apps, that manage the BT connection and offer prioritization, like this one claims to be capable of: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
Maybe this is also something you may investigate into.
I'm very interested on a solution, because I drive a lot of rental cars and I usually connect my phone to the car stereo (if available).
Completely disconnecting the watch is not an option for me, as one reason for buying the watch was to get quick notifications also when I'm in the car.
Click to expand...
Click to collapse
just disable in the bluetooth settings of the watch on the phone the "phone audio" and it works fine again.
Had the same problem that my car connected to my phone and played music, but the calls were still connected with my watch
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah, but if you disable on the watch, you can't use the speaker that was just activated on the watch to make calls.
I actually found a program called triggers that will disconnect the watch and allow the car to connect.
same issue with bt headphones. Kinda annoying.
Motawa88 said:
same issue with bt headphones. Kinda annoying.
Click to expand...
Click to collapse
Kinda annoying? This should have never left Google like this.
Maybe this googled answer will help: http://superuser.com/questions/3979...tooth-connection-priority-for-various-devices
Scott said:
Maybe this googled answer will help: http://superuser.com/questions/3979...tooth-connection-priority-for-various-devices
Click to expand...
Click to collapse
I tried that. Doesn't help if you are already connected to the watch and get in your car.
Apple watch doesn't have this problem. Google really need to fix this.
Sent from my SM-G928F using Tapatalk
Yes, I have this problem too. I will try to play with BT priority, maybe it will help.
So I tried using triggers and it worked to activate my car bluetooth. However, the sound does not go through my car stereo. I went in and had to disable phone calling on the watch bluetooth in my phone to get my car to work correctly. It sucks to have a speaker on a watch and you can't even use it to make calls because it interferes with other devices. I think the basic fix for this is to have a widget or shortcut on the Watch to enable airplane mode when you get into your car. Right now you have to go into settings and scroll through to get to airplane mode.
All I have to do is pull down the quick settings and choose my cars Bluetooth instead of the watch and it switches just fine
yes, priority do not work.
mgorman said:
All I have to do is pull down the quick settings and choose my cars Bluetooth instead of the watch and it switches just fine
Click to expand...
Click to collapse
This works for me also. For those having the issue here is one option. Use tasker and secure settings plugin. Create a profile in tasker to monitor BT near. Choose your cars BT. Create a task that uses secure setting plugin to connect to cars Bluetooth. Once done whenever your phone sees the cars BT it will connect. Rooting is not necessary.
Sent from my Nexus 6 using Tapatalk
crawrj said:
This works for me also. For those having the issue here is one option. Use tasker and secure settings plugin. Create a profile in tasker to monitor BT near. Choose your cars BT. Create a task that uses secure setting plugin to connect to cars Bluetooth. Once done whenever your phone sees the cars BT it will connect. Rooting is not necessary.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I used tasker and triggers to get my car to connect to my phone. The problem is, as long as bluetooth is enabled for the watch, i don't get sound through my car. I have to actually disable the watch to get sound to work.
dschachm said:
I used tasker and triggers to get my car to connect to my phone. The problem is, as long as bluetooth is enabled for the watch, i don't get sound through my car. I have to actually disable the watch to get sound to work.
Click to expand...
Click to collapse
I'm not having that problem. Might try with secure settings to see if you get a different result. If not it must be a phone or car head unit thing.
Sent from my Nexus 6 using Tapatalk
crawrj said:
This works for me also. For those having the issue here is one option. Use tasker and secure settings plugin. Create a profile in tasker to monitor BT near. Choose your cars BT. Create a task that uses secure setting plugin to connect to cars Bluetooth. Once done whenever your phone sees the cars BT it will connect. Rooting is not necessary.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
dschachm said:
I used tasker and triggers to get my car to connect to my phone. The problem is, as long as bluetooth is enabled for the watch, i don't get sound through my car. I have to actually disable the watch to get sound to work.
Click to expand...
Click to collapse
It seems that bluetooth near is actually working. I never even knew that existed. Hope it continues. Thanks
Can anyone give me a newbies guide to what you're talking about with triggers and tasker and how to configure?
I'm aware of tasker and have used it a long time ago when I used to root my Android devices, but I'm not entirely sure about the config nowadays especially for this kind of thing.
thisispete said:
Can anyone give me a newbies guide to what you're talking about with triggers and tasker and how to configure?
Click to expand...
Click to collapse
+1
Sent from my SGH-I747M using XDA Free mobile app
Hi everyone,
So I bought my HTC 10 a month ago.
Yesterday I took one of my cars, which I haven't driven for a long time, and tried to pair my phone with the car kit. For the record, I have a Parrot Mki9200 installed, since the car's kit did not have BT.
Now the weird part:
- I search the device - OK
- I pair the devices - everything still OK
-after that, it is supposed to instantly connect with the unit and then download my contacts. Long story short, it cannot connect, no matter what. I tried many times but all that happens is I keep waiting until I get an error from the phone " unable to connect" and then something like "make sure that your devices are one, etc".
I could really use some help on this. I even made a factory reset on the Bluetooth unit just to eliminate any conflicts. I called the authorized service in my country and they told me it should be a problem with the phone.
The weird thing is that my M8 connects flawlessly (on Android 6.0), so does a Huawei P9 lite on Marshmallow, so do all the other devices.
Any help?? The last thing I want is to make a factory reset on the phone and make no difference whatsoever.
Is there any way to reset the BT settings on the phone without factory reset? Any other way to fix it or even find the cause?
FYI, on 1.90 firmware currently, no root.
Any help will be highly appreciated, since I cannot imagine what else I can do with a new phone and no option to connect it in my car.
Thanks in advance,
Cheers,
Thanos
Sent from my HTC 10 using Tapatalk
Nobody???
This is what I am getting btw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC 10 using Tapatalk
I had the same problem with pairing the device with my sony srs-x5 bt speaker.Got no luck,tried cleaning dat and cache,didn't help;and did a factory reset.Taht fixed it.This happened to me once on stock rom,now I am on custom without any connection problems.
Did you pair it without problem but was not able to connect??
Thnx
Sent from my HTC 10 using Tapatalk
thanito said:
Did you pair it without problem but was not able to connect??
Thnx
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Yes,it was paired but not connected.I got the same error message.
ordeniz said:
Yes,it was paired but not connected.I got the same error message.
Click to expand...
Click to collapse
A few hours ago I finally found the culprit of the problem, just to let anyone know if they have the same issue.
When you are requested to enter the pairing PIN, a bit below there is an option to allow the BT unit to download the contacts, which is selected by default as always.
All phones never have a problem with that.
Anyhow, this time I deselected this option and guess what, it instantly connected!
Afterwards I selected again this option in settings and now everything works like a charm, it connects instantly every time and the contacts are properly synced.
Best regards,
T.
Sent from my HTC 10 using Tapatalk
Hi thanito,
Thanks for the hint ! I had the same problem, your comment was very helpful, I could connect my phone. Although phone works fine and contact are correctly synced, I'm not able to connect the device in Media Audio mode.
The Bluetooth in the car shows "Audio connected". In the device I see only Phone Audio and Contact Sharing. I unpaired and paired it again unsuccessfully.
Do you have an idea how to correct the problem?
Thanks for your help
Fred
Do you have the same car kit unit? Did you try to enter the settings of the paired device and select media audio?
Sent from my HTC 10 using Tapatalk
thanito said:
Do you have the same car kit unit? Did you try to enter the settings of the paired device and select media audio?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Hi, yes is the same car kit. It went suddenly wrong, I didn't change any settings. I tried to unpair and pair it many times.
When I'm pairing the device I can't select media audio. I'm only asked if I agreed to sync the contacts.
Something strange: when I get a call whatsapp, Soma or Google Duo, I can hear it trough the car Bluetooth for few second then it cuts.
I don't see how to add the Media Audio to a paired device.
Moreover, I don't have Media Audi problem when I connect the HTC10 to the MINI Bose Bluetooth. It works perfectly
Car kit works properly with my Samsung S6 Edge: Phone Audio, Audio Media & Contact sync.
FredMD11 said:
Hi, yes is the same car kit. It went suddenly wrong, I didn't change any settings. I tried to unpair and pair it many times.
When I'm pairing the device I can't select media audio. I'm only asked if I agreed to sync the contacts.
Something strange: when I get a call whatsapp, Soma or Google Duo, I can hear it trough the car Bluetooth for few second then it cuts.
I don't see how to add the Media Audio to a paired device.
Moreover, I don't have Media Audi problem when I connect the HTC10 to the MINI Bose Bluetooth. It works perfectly
Car kit works properly with my Samsung S6 Edge: Phone Audio, Audio Media & Contact sync.
Click to expand...
Click to collapse
Check the photo attachments to see the option in settings ?
Sent from my HTC 10 using Tapatalk
thanito said:
Check the photo attachments to see the option in settings
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Hi,
See my picture: Audi... = Car Kit, MINI Bose = Music Bluetooth player.
In the options for the paired Audi, I don't have Media Audio and can't select this option. few weeks ago it was ok and suddenly, the Media Audio option disappeared. I can't set it again.
FredMD11 said:
Hi,
See my picture: Audi... = Car Kit, MINI Bose = Music Bluetooth player.
In the options for the paired Audi, I don't have Media Audio and can't select this option. few weeks ago it was ok and suddenly, the Media Audio option disappeared. I can't set it again.
View attachment 3866658
Click to expand...
Click to collapse
I see..
Did you try unpairing/deleting stored device from both devices?
Usually in factory car kits you get the option to delete the paired device from the memory.
When done, try to find again the phone from the car kit or the car kit from the phone, uncheck the option for the contacts, then recheck it and hope that you are asked to allow media audio access, contact access, etc. I remember that I am prompted for these every time I pair the phone with a new BT device
Sent from my HTC 10 using Tapatalk
thanito said:
I see..
Did you try unpairing/deleting stored device from both devices?
Usually in factory car kits you get the option to delete the paired device from the memory.
When done, try to find again the phone from the car kit or the car kit from the phone, uncheck the option for the contacts, then recheck it and hope that you are asked to allow media audio access, contact access, etc. I remember that I am prompted for these every time I pair the phone with a new BT device
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Hi, I tried all options, pairing/unpairing/deleting devices, etc... no way.
I finally decided to reset (factory) my phone HTC10...
Now it works fine, Phone Audio, Media Audio & Contacts Sync options are visible and connected successfully...
Many thanks for your support
Still in process, this may not work for every remote, especially those will lost pairing after reboot, and I found some remote will disconnect after a few hours and need pairing again, dunno this is bug of shield or anything else
Tested on Sheid TV 16gb 2017, firmware 5.01 (developer)
1. side load this app to your shield: "nRF Connect for Mobile", or any BLE scanner/connect app
2.a scan the remote and press connect
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.b when connected, shield tv will ask for pairing
2.c paired and connected but it still not work
3.a adb pull /data/misc/bluedroid
3.b you will see a list of paired device in bt_config.conf, include the 3rd party remote but it will lack most info
Code:
[XX:XX:XX:XX:XX:XX]
Name = 小米蓝牙遥控器
DevClass = 1344
DevType = 2
AddrType = 0
Timestamp = 1486758640
LE_KEY_PENC = a27d02fb2083ba5847f1e4734XXXXXXXXXXXXXXX
LE_KEY_PID = 1731754feb64c60edcd09XXXXXXXXXXXXXXXXXX
LE_KEY_PCSRK = 00000000db21e99ab6XXXXXXXXXXXXXXXXXX
LE_KEY_LENC = ef8ac21724e8fc31837XXXXXXXXXXXXXXXXXX
LE_KEY_LCSRK = 00000000842e019dd2caXXXXXXXXXXXXXXXXXXX
LE_KEY_LID =
Service = 00001812-0000-1000-8000-00805f9b34fb
HidReport = 4d2a0101222e4d2a020122324d2a030122364d2a0002223a4d2ae00322454d2ae10322484d2ae203224b4d2ae303224e4d2ae40322514d2ae50322544d2ae60322574d2ae703225a4d2ae803225d4d2ae90322604d2aea0322634d2aeb032266
HidAttrMask = 0
HidSubClass = 0
HidAppId = 255
HidVendorId = 10007
HidProductId = 12800
HidVersion = 273
HidCountryCode = 0
HidSSRMaxLatency = 0
HidSSRMinTimeout = 0
HidDescriptor = 05010906a1018502050719e029e71500250175019508810295017508810195057501050819012905910295017503910195067508152825fe0507192829fe8100c0
[XX:XX:XX:XX:XX:XX]
Name = 小米蓝牙遥控器
DevClass = 7936
DevType = 2
AddrType = 0
Timestamp = 1486758704
LE_KEY_PENC = fe426d85f40053734a9eXXXXXXXXXXXXXXXXXXXXXXXXX
LE_KEY_LID =
Service = 00001812-0000-1000-8000-00805f9b34fb
3.c
now fill in the miss part, mainly the "Service", and HID part which you can omit some of them, and never change those key nor add any missing key. For service most of them will be "00001812-0000-1000-8000-00805f9b34fb "
It is suggest to copy these info from another device, I copy them from my HTC 10
beware of the order of those line, wrong order may will refuse to work
suggest to use some text editor support unix format (LF for new line) such as pspad
4. after modify push back to shield tv, reboot (I didn't try if turning on/off bt will work or not)
5. refer to this post for key mapping https://forum.xda-developers.com/shield-tv/general/change-3rd-party-remote-key-layout-root-t3548871
for china version of xiaomi box bt remote, 1st version bt remote which use CR2032 will need repairing after reboot and also will disconnect after about 1 day, but it can pair by shield tv, it will say cannot pair for 1st try, just don't touch the remote and let shield pair it again, it will pair mostly in 2~3 try
2nd version of this bt remote without voice (just $4 usd) , which us 2xaaa battery can be pair using the above method, sheild tv cannot search for it, it will not disconnect after shield tv reboot/power off, I am still testing it, hope it will not disconnect after a few hours of using.
Tmall bt voice remote same as xiaomi 1st version bt remote, and the power button is IR, voice will not work
Edit
Sorry, rereading your post, i see were not discussing the same issue, my apologies
Edit2
Although you may have giving me some places i could look into, like the config file locations, reviewing them before pairing, after pairing, and after loss of pairing, so thanks for that
Im having this similar issue on marshmellow full android
Im having no problems with seing and pairing devices, but the shield forgets the pairing when i turn off, then turn on the bluetooth, making me have to repair again, which when you have so many devices to pair becomes a pain.
Ive not tested extensively, but the pairing seems to stick, at least in the first instance of turning bluetooth on and off, as long as the bluetooth device was connected when i turn off the bluetooth
I can test this a bit more, like pair more then one device(ive only been pairing/testing one device at a time), keep one device connected, turn off the bluetooth, and see if the shield remembers all the pairings, or just the one that was still connected, when i turned off the bluetooth
I do hope a solution becomes available, as i rely quite extensively on the shields bluetooth
Researching up on it, seems theres a little issue with marshmallow and bluetoth but not this exact problem, so im stumped, this post, and another on zulus marshmellow thread are the only places ive seen mention of this particular pairing problem, the forgetting your pairings issue
http://www.videomap.it/forum/viewto...d=01cc9900293e5b3a59e3dba77a43f876&start=1000
Lukecastle
'hi zulu,
I was wondering why everytime I turn on the shield from a shutdown. I'd always have to pair my bluetooth devices. For some reason it doesnt remember the already paired devices. Thanks'
Tried to signup to that site to add to lukecastles post, but it wont let me, im a spambot apparently
banderos101 said:
I was wondering why everytime I turn on the shield from a shutdown. I'd always have to pair my bluetooth devices. For some reason it doesnt remember the already paired devices. Thanks'
Tried to signup to that site to add to lukecastles post, but it wont let me, im a spambot apparently
Click to expand...
Click to collapse
Your problem actually the same as some of my bt device and I don't have a solution, it may be a mix of the bt device firmware problem and the Shield bt, every time it happen I saw a GATT disconnect then device refuse to connect again. What I know is some of my device is fixed after a firmware update(the bt device).
Edit:
Saw some similar bug on nexus, may be they are related, need time to keep digging
DummyPLUG said:
Your problem actually the same as some of my bt device and I don't have a solution, it may be a mix of the bt device firmware problem and the Shield bt, every time it happen I saw a GATT disconnect then device refuse to connect again. What I know is some of my device is fixed after a firmware update(the bt device).
Edit:
Saw some similar bug on nexus, may be they are related, need time to keep digging
Click to expand...
Click to collapse
Dont know if this will be any help in your search, but theres a floating/popup/overlay logcat on the playstore called 'logcat extreme' that might be usefull, maybe give you some clues you may understand better then me.
I tend to pause the log, clear it, then unpause right before an action, in this case
1. Turning on bluetooth(with nothing paired) (pause, then save log)
2. Clear log, unpause, pair device, pause, save log
3. Clear log, unpause, turn off bluetooth, pause, save log
4. Clear log, unpause, turn on bluetooth(testing the pairing), pause, save log
Ill probably go over this again more thoroughly if more information comes out that helps me look out for something specific, perhaps this "GATT disconnect " that you speak off
The fact that this issue is happening on the nexus, as you say, seems to indicate that this is an issue with android itself, so im hoping, once xposed comes out for nouget, that this issue will be resolved when i update, which will be fun, seing as my adb/fastboot is not working........hoping flashfire app will do the job in this case, aswell as, hopefully, fix the adb/fastboot, but i digress
Edit
I have a very strong feeling that im gonna turn my device into a door stop when i eventually test/hope/hail mary with flashfire, a new shield purchase may be in my future just hope their still selling the 2015 model when/if i do
banderos101 said:
Dont know if this will be any help in your search, but theres a floating/popup/overlay logcat on the playstore called 'logcat extreme' that might be usefull, maybe give you some clues you may understand better then me.
I tend to pause the log, clear it, then unpause right before an action, in this case
1. Turning on bluetooth(with nothing paired) (pause, then save log)
2. Clear log, unpause, pair device, pause, save log
3. Clear log, unpause, turn off bluetooth, pause, save log
4. Clear log, unpause, turn on bluetooth(testing the pairing), pause, save log
Ill probably go over this again more thoroughly if more information comes out that helps me look out for something specific, perhaps this "GATT disconnect " that you speak off
The fact that this issue is happening on the nexus, as you say, seems to indicate that this is an issue with android itself, so im hoping, once xposed comes out for nouget, that this issue will be resolved when i update, which will be fun, seing as my adb/fastboot is not working........hoping flashfire app will do the job in this case, aswell as, hopefully, fix the adb/fastboot, but i digress
Edit
I have a very strong feeling that im gonna turn my device into a door stop when i eventually test/hope/hail mary with flashfire, a new shield purchase may be in my future just hope their still selling the 2015 model when/if i do
Click to expand...
Click to collapse
Thanks for the app, really helpful. Beside logcat you can also take a look of HCI bluetooth snoop.
a little bit off topic:
When try to stop the shield being discoverable I found that even it stop being discoverable by default bt_addr it will become discoverable by a different bt_addr if you scan for it long enough (about 1~3mins), and there are at least two different bt_addr.
you can try yourself by change the scan mode in bt_config.conf, there also an app call bluetooth settings (by4a.bluetoothsettings) can do that for you, just need to restart after install that app or the setting may not stick
Notes
I tested with another device, bluetooth mouse(which i believed to have a higher bluetooth version then the bluetooth keyboard version i was testing previously), ive been making an assumption, that under bluetooths settings "paired devices", if it comes up empty, then the pairing/s was/were forgotten, but clicking on the bluetooth mouse buttons, to auto connect, brought up a "enter pin popup"(shows up everytime i connect, so its not "fixed"), which connects ok after entering pin, so the pairing was still there, just not showing up in bluetooth settings
So at least i know its not deleted of the system
Search goes on
Edit
Bluetooth keyboard still cant auto connect(needs repairing), unlike the bluetooth mouse(which needs the pin entered every auto connect, which was not previous behaviour)
Although mouse works, the bluetooth "paired devices" sections is still empty, untill i press buttons on the mouse to auto connect
Hopefully someone finds this usefull, i sure hope im not jacking your thread dummyplug
banderos101 said:
Notes
I tested with another device, bluetooth mouse(which i believed to have a higher bluetooth version then the bluetooth keyboard version i was testing previously), ive been making an assumption, that under bluetooths settings "paired devices", if it comes up empty, then the pairing/s was/were forgotten, but clicking on the bluetooth mouse buttons, to auto connect, brought up a "enter pin popup"(shows up everytime i connect, so its not "fixed"), which connects ok after entering pin, so the pairing was still there, just not showing up in bluetooth settings
So at least i know its not deleted of the system
Search goes on
Edit
Bluetooth keyboard still cant auto connect(needs repairing), unlike the bluetooth mouse(which needs the pin entered every auto connect, which was not previous behaviour)
Although mouse works, the bluetooth "paired devices" sections is still empty, untill i press buttons on the mouse to auto connect
Hopefully someone finds this usefull, i sure hope im not jacking your thread dummyplug
Click to expand...
Click to collapse
Enter pin is actually an old pairing method before bt auto pairing. Anyway seems the bluetooth is quite buggy on shield, let hope it will be better for future firmware.
DummyPLUG said:
Enter pin is actually an old pairing method before bt auto pairing. Anyway seems the bluetooth is quite buggy on shield, let hope it will be better for future firmware.
Click to expand...
Click to collapse
Yeah, thats what im counting on when i have the opportunity to upgrade to nouget, hopefully the stock OTA download/OTA flash method works and fixes bluetooth and all my other various issues.
Also, for informations sake, i dont remember that particular bluetooth mouse of mine needing to enter a pin before i started having bluetooth issues, come to think of it, i realise the the initial pairing of my mouse auto pairs still, only after every auto connect does the pin show up
Ive encountered the blutooth/pin code popup many'ya times in the past and, well, quite recently i guess, i had assumed, that it was based on the bluetooth device you were pairing that dictated whether a popup pin would occur, and not so much android, different bluetooth peripherals having different bluetooth versions, some having or not having support for any particular bluetooth authorisation method introduced in higher/lower bluetooth standards.
Maybe part of the problem for me specifically is that my shield is not able to identify/communicate correctly with my devices
Its like you said, buggy ......and weird.......heres to hoping the ota fixes it
So does this remote - http://www.gearbest.com/smart-home-controls/pp_257680.html stay paired after reboot using this method?
GalaxyWhy said:
So does this remote - http://www.gearbest.com/smart-home-controls/pp_257680.html stay paired after reboot using this method?
Click to expand...
Click to collapse
I use the older one which don't have voice and take 2*aaa battery, beware the firmware may different, I had 4 of them and out of 2 behave a little bit different but still stay pair after reboot and don't affect usage
I have this exact remote and It has never even worked for me, does not make a beeping sound and pressing home + back any ideas why this remote wouldnt turn on at all?
hxxp://xxx.ebay.com/itm/HOT-Original-Xiaomi-Mi-remote-control-Apply-to-xiaomi-TV-and-Mi-tv-box-Pro-Cool/311829970277?_trksid=p2047675.c100005.m1851&_trkparms=aid%3D222007%26algo%3DSIM.MBE%26ao%3D2%26asc%3D41375%26meid%3D2cd664f8927e4787a3a56bf779251134%26pid%3D100005%26rk%3D5%26rkt%3D6%26sd%3D222539565729
As I know only the old one will beep, and it should be "home + menu"
my 1st xiaomi remote which using cr2032 will not work very well with shield, may be mine got a outdate firmware
I have HA head unit with 10 inch screen it is using HA_PX5_6.0(20171214) and MTCE_HA_V2.71
I have a problem connecting an OBD2 adapter, the adapter is called Response PP-2145.
Running a scan from the BT app in the head unit discovers the OBD2 adapter but it will not pair. This adapter cost quite a lot and was to replace a very cheap £3 one which works OK but does not find all available pids on the car.
If I search for the old (working) adapter it appears as an OBD symbol, a pairing attempt then asks for the password 1234 and it pairs OK.
The new adapter is found but has a mobile symbol and a pairing attempt does nothing at all. Yet pairing the new adapter to a Galaxy S6 works properly, there is no password asked for it just connects.
Edit forgot to say the factory setting for BT is set to SD-968, there are others but from memory trying to use MD725 (I think) results in no name or password in BT
Hi, known issue. Refer graser tool and information here
marchnz said:
Hi, known issue. Refer graser tool and information here
Click to expand...
Click to collapse
Thank you, I had read that thread but I assumed that the issue was different as it says "Bluetooth OBD devices that name does not start with "OBD" does not communicate with the OBD app, as the app does not detect the OBD device and wants to open the Bluetooth connection."
My unit does not even pair, do you think this is the same issue? as perhaps I have misunderstood but I read it as meaning that the OBD2 would pair but apps could not connect to it if the name was not OBD or OBDII my adapter appears in the BT scan list called OBDII the same as one that does work.
Please do not think that I am questioning what you have told me, I would like to check that you think this would fix my particular problem before I take the risk (I am not experienced with this) of installing Xposed etc Thanks again for your help.
JohnLynn said:
Thank you, I had read that thread but I assumed that the issue was different as it says "Bluetooth OBD devices that name does not start with "OBD" does not communicate with the OBD app, as the app does not detect the OBD device and wants to open the Bluetooth connection."
My unit does not even pair, do you think this is the same issue? as perhaps I have misunderstood but I read it as meaning that the OBD2 would pair but apps could not connect to it if the name was not OBD or OBDII my adapter appears in the BT scan list called OBDII the same as one that does work.
Please do not think that I am questioning what you have told me, I would like to check that you think this would fix my particular problem before I take the risk (I am not experienced with this) of installing Xposed etc Thanks again for your help.
Click to expand...
Click to collapse
It seems that your obd2 device is a low energy bt4.0 or above...
That devices don't need a pin number to pair...But I think the head unit is not prepared for that kind of obd2 devices...working normally with cheaper obd2 bt devices that need a pin to be paired (bt3.0 and lower)
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
It seems that your obd2 device is a low energy bt4.0 or above...
That devices don't need a pin number to pair...But I think the head unit is not prepared for that kind of obd2 devices...working normally with cheaper obd2 bt devices that need a pin to be paired (bt3.0 and lower)
Click to expand...
Click to collapse
With Device name being "PP2145" (did you buy from Jaycar?) This device may only be installed with graser tool. Search discussion thread for instruction.
Sorry I have been a long while replying, yes the PP-2145 came from Jaycar and it does pair with a phone without asking for a password. The cheap one does ask for a password 1234
I will read the Graser tool thread and see if I have success, thank you for your continued efforts to help.
JohnLynn said:
Sorry I have been a long while replying, yes the PP-2145 came from Jaycar and it does pair with a phone without asking for a password. The cheap one does ask for a password 1234
I will read the Graser tool thread and see if I have success, thank you for your continued efforts to help.
Click to expand...
Click to collapse
I have a VGate iCar2 which reports itself as "V-LINK" and does not require a password either (although the manual says it should ask for 1234). With the stock ROMs of November and December it pairs and is recognised as OBDII adapter (blue icon in the notification bar) without the need of the Graser tool.
One thing that helped others is to change the passcode of the unit to 1234 (from presumably 0000 it is now?).
Yes I had tried changing the head unit to 1234 but unfortunately that didn't work either. The adapter instruction book says "to pair select the PP-2145" but the adapter does not appear as PP-2145 it shows up as OBDII which is exactly the same as the cheap one that does ask for a password and does pair. The only noticeable difference is that the working one appears in the list of available devices as OBD but the one that does not pair is shown as a mobile phone symbol.
Am I right in thinking that the Graser tool is to enable the head unit to accept a device named something other than OBD? this is why I am so confused as this adapter does show in the available devices as OBDII not PP-2145
abagos said:
I have a VGate iCar2 which reports itself as "V-LINK" and does not require a password either (although the manual says it should ask for 1234). With the stock ROMs of November and December it pairs and is recognised as OBDII adapter (blue icon in the notification bar) without the need of the Graser tool.
One thing that helped others is to change the passcode of the unit to 1234 (from presumably 0000 it is now?).
Click to expand...
Click to collapse
Even the Android system dos not show a dialog asking for a password, the password is required...for the VGATE 2 you need to set up the pin as 1234 or otherwise it will not pair...
the Graser tool helps to specific OBD2 devices to have the available port to transmit the data to MTCD units.....but i dont think it helps on pairing.
Before with my VGATE Icar3 I had to use Graser's tool to the android Torque app to recognize the paired OBD2 device, but the device was already paired. Now, as you pointed, Grasr's tool is no needed anymore as HCT removed the limitation of OBD2 devices to have a discovering name starting by "OBD" caharacters
ikerg said:
Even the Android system dos not show a dialog asking for a password, the password is required...for the VGATE 2 you need to set up the pin as 1234 or otherwise it will not pair...
the Graser tool helps to specific OBD2 devices to have the available port to transmit the data to MTCD units.....but i dont think it helps on pairing.
Before with my VGATE Icar3 I had to use Graser's tool to the android Torque app to recognize the paired OBD2 device, but the device was already paired. Now, as you pointed, Grasr's tool is no needed anymore as HCT removed the limitation of OBD2 devices to have a discovering name starting by "OBD" caharacters
Click to expand...
Click to collapse
My problem is that both Torque and DashCommand have trouble establishing a connection with the OBD. When they are started, the connection to my iPhone is lost, often I have to re-enter the OBD settings in DashCommand.
Probably it has to do with my OBD? It has the feature to auto power off after thirty minutes and I have to press a button to wake it up. After I re-start the application it connects and works fine.
The V-LINK shows up in the paired devices but never turns green (like the phone) and all options other than "Unpair" are grayed out.
abagos said:
My problem is that both Torque and DashCommand have trouble establishing a connection with the OBD. When they are started, the connection to my iPhone is lost, often I have to re-enter the OBD settings in DashCommand.
Probably it has to do with my OBD? It has the feature to auto power off after thirty minutes and I have to press a button to wake it up. After I re-start the application it connects and works fine.
The V-LINK shows up in the paired devices but never turns green (like the phone) and all options other than "Unpair" are grayed out.
Click to expand...
Click to collapse
in my case I have to unplug/plug again to Torque/DashCommand connects to the Device (I think due to the auto poweroff of the device), but you will see on the sattus bar how the OBD logo changes to BOLD when transmnitting to any app.
I have no issues of phone disconnection (Android Galaxy S8) when OBD devices connects
Would it be any use in my case with the not pairing issue trying an external BT adapter if there is a USB device that would work on these head units?
Today I was able to try my BT adapter in a friend's head unit which has the Malaysk rom. This of course has the Graser tool as standard.
Unfortunately the symptoms were identical, the unit recognises the BT adapter although shows a phone symbol and pressing pair results in absolutely nothing happening. This was from the BT app, if the same thing was tried from the settings/bluetooth then the adapter appeared named 1OBDII so we used the Glaser tool to add this name plus a few others such as PP-2145 but with no success.
I do not understand enough about the Glaser tool to try anything other than adding new names, there is a line above the name with "cv" written in it what is this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG][/IMG]
JohnLynn said:
I have HA head unit with 10 inch screen it is using HA_PX5_6.0(20171214) and MTCE_HA_V2.71
I have a problem connecting an OBD2 adapter, the adapter is called Response PP-2145.
Running a scan from the BT app in the head unit discovers the OBD2 adapter but it will not pair. This adapter cost quite a lot and was to replace a very cheap £3 one which works OK but does not find all available pids on the car.
If I search for the old (working) adapter it appears as an OBD symbol, a pairing attempt then asks for the password 1234 and it pairs OK.
The new adapter is found but has a mobile symbol and a pairing attempt does nothing at all. Yet pairing the new adapter to a Galaxy S6 works properly, there is no password asked for it just connects.
Edit forgot to say the factory setting for BT is set to SD-968, there are others but from memory trying to use MD725 (I think) results in no name or password in BT
Click to expand...
Click to collapse
Hi
I have exactly the same problem as you, my Audio Video Nav Unit is a MTCE_MX2_V2.75_1 - Android 6.0.1
I also have a costful OBD reader OBDLink LX that i like very much, the BT discovered it with the phone symbol BUT simply don't get paired. With a cheap ELM327 Obd it works fine, but these cheap readers not always work properly.
I've tried several things but still don't work, if you get a solution post here
I will continue to search...
Good luck
pauloroxa said:
[/IMG][/IMG]
Hi
I have exactly the same problem as you, my Audio Video Nav Unit is a MTCE_MX2_V2.75_1 - Android 6.0.1
I also have a costful OBD reader OBDLink LX that i like very much, the BT discovered it with the phone symbol BUT simply don't get paired. With a cheap ELM327 Obd it works fine, but these cheap readers not always work properly.
I've tried several things but still don't work, if you get a solution post here
I will continue to search...
Good luck
Click to expand...
Click to collapse
There are multiple posts on this issue. Set pin code in BT app to 1234. Push button on Odblink then scan on headunit. Await for discovery to complete then press on Odblink in app to pair. You might need to push pair button on Odblink a second time.
Well i've tried almost everything...result: nothing. It continues to Discover and identify the OBDLink LX, but DON'T PAIR. I even reset the px5 MTCE to factory settings to clear All caches and start All the process ...nothing.
Is There anybody here from Scantool.net to gimme a reply?
Yes I am afraid that I have run out of things to try, setting pine code to 1234 as suggested above in my case does nothing as my unit does not have a pin. It would be good to know why our head units recognise the OBD unit as a phone?
JohnLynn said:
Yes I am afraid that I have run out of things to try, setting pine code to 1234 as suggested above in my case does nothing as my unit does not have a pin. It would be good to know why our head units recognise the OBD unit as a phone?
Click to expand...
Click to collapse
Hi John
well, i'm like you very sad not to set this up because the OBDLink LX is the best BT scan tool i ever used, cheap obd elm 327 have no comparison with LX, my cheap Obd already gave me ABS errors on the dash can you imagine and cut transmission very often, its useless.
the only thing their good is Pairing right away
But i didn''t gave up from LX yet...
I discover that our OBDLink LX firmware is STN 1155 V.4.3.0 identifying ELM327 V.1.3a and the cheap chinese ELM327 is V2.1, i think the problem is here... we need an older firmware
Keep in touch if you know something
Good luck
pauloroxa said:
Hi John
well, i'm like you very sad not to set this up because the OBDLink LX is the best BT scan tool i ever used, cheap obd elm 327 have no comparison with LX, my cheap Obd already gave me ABS errors on the dash can you imagine and cut transmission very often, its useless.
the only thing their good is Pairing right away
But i didn''t gave up from LX yet...
I discover that our OBDLink LX firmware is STN 1155 V.4.3.0 identifying ELM327 V.1.3a and the cheap chinese ELM327 is V2.1, i think the problem is here... we need an older firmware
Keep in touch if you know something
Good luck
Click to expand...
Click to collapse
It doesn't matter the version of elm chip....(in fact I think odblink lx is not an elm)...the point here is the version of Bluetooth of the obd2 device....your device is low energy bt 4.1...and head unit recognizes it as phone...
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
It doesn't matter the version of elm chip....(in fact I think odblink lx is not an elm)...the point here is the version of Bluetooth of the obd2 device....your device is low energy bt 4.1...and head unit recognizes it as phone...
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Thanks Ikerg for your time.
And why doesn't pair even being recognize as a phone? If the head unit treats it like a phone, at least it might paired like one...
I think the problem also is the 6 digit code that OBD LX requires, but the head unit never received that request besides have 4 digit space 0000 or 1234
i even dispaired all my devices in head unit and nothing.
Is there any app or firmware that we can install on HU android that runs on low energy devices?