[GUIDE/TUT] How to get ICS devices run OBD2 interfaces via WIFI WITHOUT DROPS - Android General

Did you end up buying a OBD2 Wifi (not bluetooth) interface for your car, noticing android got some problems with ad-hoc connections and can't connect that easy, that you may have thought?
Well, if so, I'm at least not the only one
In my case I wanted to have a look at my engine stats etc. You might also be happy about checking the vin stored in the cars ecu with the one you got on paper, when buying a used car or else. Anyway I did not want those crappy bluetooth thing for some bucks. I wanted it to use wifi and also to be able to connect via usb to a laptop, if neccessary.
I got mine from eBay for about 80$. There is a bunch of these things avaible everywhere. I can't really tell you which one is better in which way. Most of them come out of china and are built pretty cheap, just like mine
BUT at least they work the way the should, once configured right.
IN GENERAL --> without any kind of workaround you shold keep in mind:
BT OBD2 is used for android devices. No Problem
WIFI OBD2 is usually used for iDevices, as they're not allowed to share BT with non-iDevices.
I didn't really make up my head about the second part, as I'm using android on every device I personally own.
Here's a tutorial on how I solved it anyway:
1. Buy yourself some OBD2 interface with wifi and the software you desire. Didn't test anything else but torque pro; no guarantee that other apps support these android-wifi-adhoc-obd-interface-workarounds
2. you need a rooted phone, in every possible case afaik.
3. Plug in your OBD interface and look, if you can see it in your wlan list.
In my case...I couldn't^^
If you see it jump to Number 4.4, if not, just keep on reading.
4. Getting my device, which is a HTC Sensation, with ARHD 6.6.7 - 4.0.3 ICS, connected to it required some effort:
4.1. I used a different wpa_Supplicant, to be able to see adhoc networks
I got this one: http://forum.xda-developers.com/showthread.php?t=1549065&highlight=adhoc also attached in the Thread. Full Credits go to the dev, although I don't know who it was exactly.
4.2. REMEMBER TO BACKUP YOUR ORIGINAL WPA_SUPPLICANT AND SWITCH WIFI OFF BEFORE!
It's stored in system/bin; so you'll need a explorer (mount R/W) for your phone's file system. I always used the root explorer. Worked flawlessly everytime. (mount R/O afterwards).
4.3. Flash the attached file in recovery -> I did at least find the adhoc network after it. Remember that some wifi off, wifi on sometimes solves problemes with this. This was at least the case for me. Reboot.
4.4. Now that you can see the OBD interface in your wlan list, you propably tried to connect, didn't you?
For most of us, this won't work, that easy, as your OBD interface doesn't work as a DHCP router, so you're in the need of taking a static IP.
Therefore it always depends on which IP range your interface is networking. In the most cases this will be 192.168.0.X
Picture #1 is a screen of the config tool, that came with mine so I can modify these values. (What is not really neccessary, cause you're doing this with your phone.)
Picture #2 are my stats. You can edit yours by long pressing on your desired OBD device in your phones wifi list and pressing "edit network". After that, change to advanced configuration and choose static IP.
4.5. Save your preferences and try to connect. Again I think my wifi needed a reboot to work with the values set now. So just swith it off/on again.
5. You're done. More or less. Because this is just what made me able to connect but drop my connection to the OBD after trying to access it via torque. It did connect (as seen on adapter status in torque), but lose connection after some seconds. It just didn't really work for a longer period of time. There also used to be connecting errors with my home wifi.
5. After hours of testing and experimenting with this whole topic I came to the conclusion my home network didn't work anymore or rather my phone couldn't keep up the connection. What you have to do is switch back to your old wpa_supplicant. Don't worry, your OBD interface should be saved and is still accessable afterwards.
5.1. SWITCH WIFI OFF. Navigate to system/bin via root explorer or similiar. (mount R/W) locate the wpa_supplicate and delete/rename/remove it and put the original file back in it. (mount R/O afterwards). Reboot.
(Picture #3 shows how it looked on my device after switching back to the original file.)
5.2. You're finally done.
Remember not to forget that wrong permissions could lead to errors. Refer to my attached screenshot or your original file, if neccessary.

where you found the configuration tool??

Related

Problems Connecting to External Bluetooth GPS

So I picked up an external GPS receiver off ebay. It's the Globalsat BT-359C (http://www.usglobalsat.com/p-214-bt-359c.aspx). Turned it on, everything went fine as far as my fuze finding it. I'd goto add new device, it'd pull up "BT-GPS371D88", i'd select it, put it the four "0" 's, and it'd give me the message "your pocketpc is now connected with BT-GPS371D88". It comes up in the list but under disconnected. So i'm like eh whatever, and setup the outgoing com port to COM0 as per the instructions, and make sure its unsecure.
I go back to devices, highlight BT-GPS371D88, click it. Check off "Serial Port" in select services to use, and save. Then heres where everything goes wrong, I hit connect, and it gives me the following message "Your device did not connect with BT-GPS371D88. The connection failed or the passcode is incorrect." I've been tinkering with it all day, searching various forums to no avail. Even downgraded my 6.5 rom to 6.1 thinking it was maybe incompatible with something so new.
Now i'm stuck, I really want to get it working so i can use it for a trip thats coming up in a few days. Has anyone else had such a problem? is there like a quick fix that i'm over looking, or is it simply not compatible with the fuze? I managed to get it paired up and connected fine to my blackberry curve just to see if the gps unit was defective (did buy it off ebay). Any Ideas guys? Not sure where else to turn now.
Oh yeah btw my current rom that i'm using is
At0mAng Fusion Power V 5.X ROM Series
Windows Mobile 6.1 (Build 21051 1.6.4)
Located @ http://forum.xda-developers.com/showthread.php?t=537501
jimshepp said:
So I picked up an external GPS receiver off ebay. It's the Globalsat BT-359C (http://www.usglobalsat.com/p-214-bt-359c.aspx). Turned it on, everything went fine as far as my fuze finding it. I'd goto add new device, it'd pull up "BT-GPS371D88", i'd select it, put it the four "0" 's, and it'd give me the message "your pocketpc is now connected with BT-GPS371D
Click to expand...
Click to collapse
have a BT GPS for my Dell axim x51v, got some trouble too getting it to connect, but eventually did
here are some pointers:
1) Delete all pairings and com port pairings on the device
2) Pair the device (make sure that you put 'request authorization' or something... this ensures that you need to put the 0000 code to connect)
3) you need to set up at outgoing port on your device, to the BT GPS... COM 8 is norm
4) External GPS setting in the Start>Settings tab
hardware port is where you put the outgoing port in (3)
software port is where you put for your GPS software... COM4 is norm
third column where WinMo will manage GPS, say yes
This worked for me:
I have a Hermes (WM6.5) with a holoux bluetooth GPS, but the GPS was not connecting for me properly either. It seems to be a problem with the way WM6.1 pairs with bluetooth devices.
I managed to get mine to work without reflashing by downloading this alternative bluetooth manager:
http://forum.xda-developers.com/showthread.php?t=353774
Hope this helps.
Not trying to bump up an old thread for no reason, but I figured this info would be helpful for people utilizing searches.
After lots of research and frustration the past week I have gotten my external GPS (USGlobalSat BT-368i) to work with my HTC Fuze! Below are the steps I followed that have worked for me. Note that I still have the phone configured to use the internal GPS if the program is set to "Let windows manage GPS settings".
1. Pair the device using Bluetooth.
2. Under the devices tab select your external gps device, and check the box to use "Serial Port". Then choose Save.
2. Under the Bluetooth settings choose "COM Ports" tab.
3. Choose "New Outgoing Port", and then select your device and click next. Choose your port and preferred "secure" option. Then click Finish. (I have configured mine to use COM0 & Secure Connection)
The device will still show as "Disconnected", and you will not be able to connect it under the Bluetooth manager. It will give you an error saying unable to connect.
To use the external GPS device you can simply select the outgoing port you configured above in your program, and most likely you will use a baud rate of 4800. Once you enable the GPS in the program it should connect itself via Bluetooth to your device and begin using it.
You should also be able to configure it to automatically use your external GPS instead of the internal one under the "External GPS" settings, but my current ROM has the hardware portion of External GPS manager broken @ the moment. Therefore I have not configured this, and cannot confirm it.
Hope this helps someone!

[Q] Tethering

This question has probably been asked a million times but i couldn't find an answer.
On my HTC Hero (android 2.1), there was an option to tether once you plugged the phone into your computer. This could also be used as a wireless receiver for a desktop computer lacking a wireless access card. I was using this as a last resort after losing dozens of Ethernet cables to vermin under the house. Basically the idea was: connect to your homes wireless router on the phone, then plug the phone into the usb slot of your computer and it would share that wifi connection with your computer. Recently I have switched over to the all powerful HTC HD2 and I am realizing there is no way to do this, that I can tell, with the stock phone. Is there something I'm missing?
I have tried using the Internet Sharing option, as well as the CMInternetSharing.cab I downloaded from you guys, and neither seem to bring this ability to the table. Is there an app out there that can solve this problem?
Ussually a Custom rom will fix this most have the Internet share or WiFi router but you need to HARDSPL your phone. also theres a way for you to do it just deleting your or editing your REGISTRY.
---------------------
Here is the Thread for the roms for your phone
http://forum.xda-developers.com/forumdisplay.php?f=534
and this is the rom I Recomend
http://forum.xda-developers.com/showthread.php?t=591784
use the Cookie GTX (white theme)
Follow the intructions on how to install it(rom) also onces done click on your Window button>tools>WiFi Router and you can use your phone as a wireless router also if you connected your phone Via usb to your conputer you can connect using internet sharing.
fixed the problem
WMWifiRouter has a wifi to usb mode.
will definitely be buying it after my trial runs out.

[Q] Is bluetooth broken on the Nexus S, or am I doing something terribly wrong?

I'm being driven nuts trying to make any use of bluetooth on my new Nexus S 4G. I'm running the stock firmware, though it is now rooted. The same problems were present before I rooted it.
No matter which computing devices I try to pair nor how many times I try to re-pair, I get "paired but not connected." This means several things I need won't work, such as GPS sharing or file transfer. I've tried 2 different Android tablets, another Android phone, 2 different Windows Mobile phones, a desktop and a notebook with exactly the same results.
The NS4G will pair with my car, but it will only transfer phone numbers, not street addresses, email addresses, web sites, or notes. Names are transferred as all "first name" (the full name or company name appears in the first name field), irrespective of whether there's even a first name listed at all. This means I can't ever sort by last name or company in the car, which I often wish to do. My primitive Windows Mobile phone can handle all this with no difficulty at all. The "Car Home" interface won't auto-start no matter what I do.
I'm having difficulty believing that Bluetooth functionality could possibly be this lousy in any modern device, especially one that works so well in every other way. Can anyone help me track down whether I'm somehow doing something wrong, or if I need to give up on the phone and swap it for something else?
I had the same problem couldn't receive anything through Bluetooth, but I download Bluetooth File Transfer and now receives And pairs with any device
I'm not having problems. I've sent files between phones via bt, used head sets, and played games with an emulator and wii controller. I've never had the need to transfer contacts. Try reboot the phone and or make the other device go into forced pairing mode. Maybe you're doing something wrong. On the other hand, I never can connect the phone to my macbook. It's such an ordeal. I've tried xp too and never had success. Im probably doing something wrong.
Ram1500 said:
I had the same problem couldn't receive anything through Bluetooth, but I download Bluetooth File Transfer and now receives And pairs with any device
Click to expand...
Click to collapse
I downloaded it and was able to use it to transfer a file between the Nexus S and an Android tablet. This does not, however, appear to have fixed anything else. Settings still shows "paired but not connected," no other bluetooth utilities work, and I'm still unable to transfer contacts to the car.

HID Bluetooth Device FIX for 2.3.5 and 2.3.6!!

NOTE TO MODERATORS: I have discovered a workaround solution to a bug that plagues many android devices running 2.3.5 and 2.3.6, however I cannot post in the development forum. If this thread is moved to the development forum please unlock my ability to post in that forum.
Like many of you I was extremely excited to learn that android now supports HID devices and immediately rushed out to purchase a HID-BT Keyboard. Getting home, I fired up the phone and keyboard, entered the 6 digit code to pair them and saw the device connecting and disconnecting in an infinite loop. I was crushed and disappointed.
What went wrong? As stated above this is merely a workaround. But the problem lies somewhere between the kernel and broadcom chipset. This fix will reset your bluetooth pairings. It has been tested on my Samsung Galaxy SII I727 but it should work with any other device.
-----------------------
The Fix (Workaround)
-----------------------
While this works for me it is not guaranteed to work for you, and while it is unlikely to brick your phone, you could be left with non-working bluetooth. So please make sure to backup all files, especially /system/bin/btld This tutorial assumes a certain level of knowledge about android, if this does not make sense to you PLEASE do not try this!!
1. Make sure that your bluetooth is turned off under settings
2. Download a file manager like ES File Explorer with root capabilities
b. Optionally you can push your files over adb, but I will not cover that in this tutorial.
3. Backup /system/bin/btld to a safe location on your device.
4. Backup /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/ (where XX:XX... is the MAC of your device)
5. Delete the folder titled with your MAC under /data/misc/bluetoothd/
6. Download the zip file contained as an attachment to this thread
7. Extract btld anywhere on your device.
8. Copy btld from the zip to /system/bin/btld (you must have root access)
9. Set btld permissions to 0755
10. Restart your device.
11. Go into bluetooth settings, pair the phone with your HID device.
b. You might get a prompt to enter a keycode on device 00:00:00:00:07:00; this is a ghost device, harmless but a bit annoying, just hit ok and ignore it
12. Your phone should pair and connect with your HID device.
b. If your phone does not connect, stop here and post back on the forum.
13. Turn off bluetooth DO NOT TURN IT BACK ON UNTIL COMPLETING THE FINAL STEPS OR YOU MIGHT HAVE TO START OVER
14. Open your file explorer, go to /data/misc/bluetoothd/XX:XX.../
b. You should see a file titled hidinfo, open it with a text editor
c. Delete the CONTENTS of this file and save the file
d. Set permissions to 0444 (read only) for hidinfo
15. Restart your device
Bluetooth should be working properly with your HID device. You might continue getting a prompt to pair with a ghost device, just hit ok and ignore it.
Reserved....
Working on Samsung Galaxy i8150
Confirmed working for my mouse on Galaxy Wonder I8150. Android 2.3.5. I do however see the ghost device, but that's not a problem.
Although it seems to be working for a single device at a time, I have trouble using a mouse together with a headse. The pairing process had to be done a number of times before succeeding. It requested the pairing pin code, but sometimes requests the pin code for a "" device. (the headset is a Phillips SHB6017 and supports a2dp audio profile + headset profile)
Sometimes both devices won't connect at all, sometimes the status is connected, but it doesn't actually work.
All in all to much trouble for me. I'm reverting back. Thanks for the effort so far.
Although I have not tried pairing multiple devices, I'll try with a headset and keyboard tomorrow, you can ignore pair requests from device "". I only paired my keyboard once and it just works, although I do get requests from "" whenever I turn on bt that I ignore.
I was in a situation where hid wasn't working at all though, so the trouble is worth it for me
I'll test with two devices tomorrow
Just want to report that I have no trouble connecting with my Blueant BT and Logitech for Android KB on my I727 Samsung SII LTE. I find that once I pair the devices they connect automatically most of the time once turned on. My BT didn't pair automatically once but I just power cycled it and hit the connect button and it worked.
If anyone else has tried this fix please report your results so others can learn from it
Glad it works for you. Here are the devices I used.
My mouse is a Logitech Laser Travel Mouse (blue). The Headset is a Phillips SBH6017.
I did try to power cycle and ignore the "" requests, and I eventually could get both devices paired and connected. But the sound will not play over the headset. Reconnecting didn't help much. When I reverted back it worked instantly(headset) but the mouse (as expected because of the HID bug) doesn't work after reverting back.
thank you so mutch... i bought an A4Tech Mouse BT-630 to use it whit Samsung GSII I9100, MHL and an LG LCD TV to watch videos on Youtube when my brother is at the PC and it would paire but not connect... i was so dissapointed thinking that the mouse is not good and i just wasted my money on it. I folowed your tutorial and i can confirm that it works! Thanks againe !!! PS: english is not my native language...
I was really excited when I saw this post. But it didn't seem to work. I got to step 4. There was no file showing up with my MAC address... no files at all in that directory.
I went ahead anyway. One thing to check: I set the permissions of the btld to:
user: read, write, execute
group: read, execute
other: read, execute
Is that right? There are no numbers in the choices.
Also should the btld file go directly into /system/bin/ folder? Or should there be another folder there: /system/bin/btld/btld
SPH-D700, Samsung Epic
2.3.6, EL30
SleeperRom
zeckwoy said:
I was really excited when I saw this post. But it didn't seem to work. I got to step 4. There was no file showing up with my MAC address... no files at all in that directory.
Click to expand...
Click to collapse
If you've used bluetooth on the device even once those files should be automatically generated by the bluetooth driver. Please confirm that you are in the root directory under /data/misc/bluetoothd/ It should be a folder with your MAC and files inside, this folder needs to be generated for the fix to work.
zeckwoy said:
I went ahead anyway. One thing to check: I set the permissions of the btld to:
user: read, write, execute
group: read, execute
other: read, execute
Click to expand...
Click to collapse
Those are the right permissions for btld, btld should go under /system/bin/ directly. You should backup the old file before doing this so that you can revert if needed.
jaapsen said:
Glad it works for you. Here are the devices I used.
My mouse is a Logitech Laser Travel Mouse (blue). The Headset is a Phillips SBH6017.
I did try to power cycle and ignore the "" requests, and I eventually could get both devices paired and connected. But the sound will not play over the headset. Reconnecting didn't help much. When I reverted back it worked instantly(headset) but the mouse (as expected because of the HID bug) doesn't work after reverting back.
Click to expand...
Click to collapse
Could you describe the order that you power on your devices when they don't work, or the order that you've found has worked? I do find that sometimes my BT headset won't connect automatically but if I go under settings/bluetooth and hit to pair with it it connects successfully and works.
The fix isn't overly complicated, all you're doing is really replacing the bluetooth stack with an older version. Did you delete the contents of hidinfo under data/misc/bluetoothd/XX:XX:XX../ and set permissions to read-only?
Sorry, it doesn't work for me. I get the same message as always:
"Sorry, but HID device is not supported on this phone."
I get that when I try to pair. I have two different keyboards, and both get the same response.
The one keyboard did work when I was running ICS Cyanogen Mod (without your fix), but doesn't work when I run Sleeper Gingerbread (with your fix.)
Thanks anyway. Wish it worked!
Hello,
i have a same problem with my 2.3.6 on my Galaxy note N7000
my HID bluetooth device Also Samsung .. after upgrade to the new 2.3.6 version
my Headset cannot pair ..
please i think i need your BTFIX file .. but it seems i'm not be able to use it .. it said " CRC error " the file was corrupt ..
please i need your new file ..
Worked
Awesome, thanks! (galaxy note 2.3.6)
Did not help me on Galaxy W
This did not help me on Black Notes Hybrid 2 nor Bionic Cow 2. Interestingly - Bluetooth works great on stock ROM.
Re: Did not help me on Galaxy W
dushino said:
This did not help me on Black Notes Hybrid 2 nor Bionic Cow 2. Interestingly - Bluetooth works great on stock ROM.
Click to expand...
Click to collapse
Update from me: After some experiments I found that the problem was in kernel! (Samsung Galaxy W, Bionic COW ROM or Black Notes Hybrid 2) When I installed
stock kernel, Bluetooth started to work without modififying any configuration files or replacing a single binary.
Please note that there is a lot things what can go wrong when something does not work. It means that I am not saying kernel replacement solves it all - receipt mentioned here still might work for you.
Galaxy Exhibit
I have an Exhibit II, now called Galaxy Exhibit in its new 2.3.6 firmware. The 2.3.5 firmware actually worked well with my Logitech Android Tablet Keyboard but 2.3.6 didn't. Following the lead of this post I replaced btld with the version from the previous firmware and that worked -- once. Now that I have also made the changes to hidinfo.txt it seems to be working better -- EXCEPT that I am getting the Settings app crashing nearly every time Bluetooth is turned on or off.
Also I think the Home button on the keyboard was working that first time, but it isn't working now... and the keyboard is not listed under paired devices.
it woked for me.thank u very very much genius.
I can't overwrite btld... How do i overwrite it?
Close, but no cigar ... (SGT P1000 running 2.3.6)
tommystery said:
NOTE TO MODERATORS: I have discovered a workaround solution to a bug that plagues many android devices running 2.3.5 and 2.3.6, however I cannot post in the development forum. If this thread is moved to the development forum please unlock my ability to post in that forum.
Like many of you I was extremely excited to learn that android now supports HID devices and immediately rushed out to purchase a HID-BT Keyboard. Getting home, I fired up the phone and keyboard, entered the 6 digit code to pair them and saw the device connecting and disconnecting in an infinite loop. I was crushed and disappointed.
What went wrong? As stated above this is merely a workaround. But the problem lies somewhere between the kernel and broadcom chipset. This fix will reset your bluetooth pairings. It has been tested on my Samsung Galaxy SII I727 but it should work with any other device.
-----------------------
The Fix (Workaround)
-----------------------
While this works for me it is not guaranteed to work for you, and while it is unlikely to brick your phone, you could be left with non-working bluetooth. So please make sure to backup all files, especially /system/bin/btld This tutorial assumes a certain level of knowledge about android, if this does not make sense to you PLEASE do not try this!!
1. Make sure that your bluetooth is turned off under settings
2. Download a file manager like ES File Explorer with root capabilities
b. Optionally you can push your files over adb, but I will not cover that in this tutorial.
3. Backup /system/bin/btld to a safe location on your device.
4. Backup /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/ (where XX:XX... is the MAC of your device)
5. Delete the folder titled with your MAC under /data/misc/bluetoothd/
6. Download the zip file contained as an attachment to this thread
7. Extract btld anywhere on your device.
8. Copy btld from the zip to /system/bin/btld (you must have root access)
9. Set btld permissions to 0755
10. Restart your device.
11. Go into bluetooth settings, pair the phone with your HID device.
b. You might get a prompt to enter a keycode on device 00:00:00:00:07:00; this is a ghost device, harmless but a bit annoying, just hit ok and ignore it
12. Your phone should pair and connect with your HID device.
b. If your phone does not connect, stop here and post back on the forum.
13. Turn off bluetooth DO NOT TURN IT BACK ON UNTIL COMPLETING THE FINAL STEPS OR YOU MIGHT HAVE TO START OVER
14. Open your file explorer, go to /data/misc/bluetoothd/XX:XX.../
b. You should see a file titled hidinfo, open it with a text editor
c. Delete the CONTENTS of this file and save the file
d. Set permissions to 0444 (read only) for hidinfo
15. Restart your device
Bluetooth should be working properly with your HID device. You might continue getting a prompt to pair with a ghost device, just hit ok and ignore it.
Click to expand...
Click to collapse
Sadly, no luck on my SGT P1000 running Overcome(4.1.0) GB 2.3.6. Most of the steps work fine, but at the moment of connection the tablet reboots and I must start over. I really was hoping this workaround would work as I am very happy with my current configuration, and perfection would be being able to connect to my HID keyboard. Thanks anyway for the post! :good:
Getting same type of problem
I have a Galaxy Nexus and I CAN pair with a Dell BT mouse but I don't get a pointer. Would this fix work on my phone or is there another problem. I looked all over for a fix and I seem to be the only one with a GNex having this issue. Mouse tested and works on Thunderbolt. My Bluetooth works with BT headphones. Any help is greatly appreciated.
Samsung Galaxy Nexus
android version: 4.1.1
Base Version : FF02/FG02
Kernal Version : 3.0.42-Air_kernal_stable_G512mhz_for_JBN
AOKP version : AOKP_toro_jb-build-1
build number : JRO03H

Question Bluetooth connectivity issues

I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Turn off global power management completely in Device Care.
Network reset, reboot and clear system cache from the boot menu.
Ok, I've done a network reset, and cleared the cache partition. I checked Device Care for something like global power management, and I couldn't find anything. Most of the pwm settings are off except the "optomise daily" setting.
I'll let you know later if I have the same issue again.
These, this is a N10+ running on Pie.
To check if you have disabled global power go to Developer options>standby apps, all buckets should show as active otherwise power management is enable.
KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
Are those the only three devices you connect via BT? What other apps do you use that need to use BT (i.e. Galaxy Wear, Apple Music, etc.).
You mentioned "Nordic Semiconductors Bluetooth App." I looked it up. Why do you need a third party generic BLE connecting app? It seems to me that could be the problem. You shouldn't need a third-party app to connect your BLE devices. The S22U's native pairing will work with any BT device that adheres to BT standards.
Try uninstalling the nRF Connect app and see what happens.
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
KindarConrath said:
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
Click to expand...
Click to collapse
Ok. I recommend uninstalling nRF Connect anyway. If anything, to rule out the app. How old is your car and the Raspberry Pi? Even though BT 5.2 is backwards compatible, sometimes older BT devices won't work with newer devices. That doesn't account for the S Pen issue though.
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
OP- Have you debloated at all and if so maybe you've removed something relevant that might be causing these issues?
No, stock image, no OS modification beyond the things that Samsung offers (GoodLock and Stock customisation)
I have our in-house apps for interacting with our equipment (over Bluetooth) installed, but #1 they shouldn't affect anything if they are not open and #2 they don't do this to ANY of our other test equipment.
I would just like to say, that I appreciate the assistance that you are all offering! I have used many forums over the years when looking for support on things and I rarely find a place that is more ready to try and help than XDA forums!
KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Rubby1025 said:
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Click to expand...
Click to collapse
As cool as I think Smart-Switch is as a program, I actually never use it when moving from one phone to another. The junk that Google drags with me from one phone to the next is already too much, I like to use a new device as a chance to do some housecleaning. So no old-data oddities here.
KindarConrath said:
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
Click to expand...
Click to collapse
Hmmm.. Ok. You're probably right about the suspect causes. I know there is a code you can dial to get into diagnostic mode, I just don't know what it is.
The only other option you can try (as a last resort) is to factory reset it. If it is update caused, a factory reset MAY fix it. If you take it to a service center, send it in for repairs, or do a warranty replacement, they're going to factory reset it, or have you reset it.
have you tried running diagnostics in device care ?
or check with this dc
android
Bluetooth test*#*#232331#*#*
samsung
Bluetooth Test Mode*#232331#
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
KindarConrath said:
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
Click to expand...
Click to collapse
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
doubledragon5 said:
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
Click to expand...
Click to collapse
Yes, and I've disconnected, reconnected and even unpaired and re-paired the phone to the car.
gernerttl said:
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
Click to expand...
Click to collapse
Unless having multiple connections causes the BT to fail completely, no. Even after turning the car off and walking away, it still will not connect to the S Pen. The only BT devices I use with that phone regularly are:
S Pen, Car (Music & Calls)
At work I develop devices that use Bluetooth and I sometimes connect to them, but only ever one at a time.

Categories

Resources