Database Develop

[Q] Samsung Galaxy S and Bluetooth Issues

Hi there, (not to sure if this is the right place, please redirect me
if it is wrong)
Basically I am writing an application which receives data from a blue tooth enabled device which has no user interface. I've been developing with the Nexus One with Android 2.2 however I decided to test it on a Samsung Galaxy S (Model GT-I9000) to ensure that it worked properly on other handsets. The Samsung is running 2.1-update1 albeit it's been customised by Samsung.
First thing I noticed was that the blue tooth enabled device did not show on the search results when attempting to pair the device which was odd considering that it appears on the Nexus One without any problem.
To get around this I wrote a few lines of code to scan the available devices and attempt a connection to the device matching the advertised name, which in turn would start the pairing process and the phone would remember the device.
So I have a very simple BroadcastReciever class which has the Intent filters for device found and discovery finished events. What I found whilst debugging in Eclipse was the following in LogCat:
E DTUN_HCID Device [00:07:CF:59:04:38] class is 0x00 - skip it
The 'skip it' part worries me because no intents are fired for the BroadcastReciever to process and I have only found this with the Samsung handset, I've yet to try others (as I have no others to hand) Has anyone else ever encountered this problem or could perhaps suggest a work-around or at least a pointer to where I could at least override this behaviour?
Thanks for any help.

I've exactly the same problem with the HTC Desire (2.1 or FroYo). Looks like they crippled the bluetooth scan, so it doesn't list devices like these.
I can connect to the device (at least under 2.2) by giving it the bluetooth address directly and it works fine. It even is listed as paired after that...
Any idea how to fix this (i don't know yet, where this message ("...class is [0]...") originates from)?

For what it's worth I had a quick look at the Samsung open source and this message comes from vendor/brcm/adaptation/dtun/dtunc_bz4/dtun_hcid.c in function dtun_dm_sig_device_found, so it's probably Broadcom's fault, but I can't see a workaround, it looks like it will never interactively pair with something with class of device=0.

hello,
I'm having the exact same problem on the galaxy s.
Have you found a sollution for this?
It is rather critical for my application :-(
Greetings,
Kristof taveirne

Hi Guys, thanks for the replies, didn't get an e-mail to let me know that there was a response.
@TheBeano: Thanks for having a look at that. You can pair the device if it initiates a connection to the phone, however the device I'm using makes this very difficult. Thanks for your efforts.
@fheldt: I have no idea on a workaround bar attempting to trace logs, find the address and attempting to connect to the device, however that isn't exactly an elegant solution.
@Liquinno As far as theBeano has stated there doesn't look like a workaround, it's rather critical to my application. Sorry I can't help further
Thanks for your efforts, if you come up with an idea or workaround, would mind letting us know ?

Maybe we'll have some luck with the Froyo firmware update that's coming up later this month.
For now I'm using other BT devices that are not class 0x00 to continue development. But I'll definitely get back on this.
Kristof

fheldt said:
I've exactly the same problem with the HTC Desire (2.1 or FroYo). Looks like they crippled the bluetooth scan, so it doesn't list devices like these.
I can connect to the device (at least under 2.2) by giving it the bluetooth address directly and it works fine. It even is listed as paired after that...
Any idea how to fix this (i don't know yet, where this message ("...class is [0]...") originates from)?
Click to expand...
Click to collapse
"I can connect to the device (at least under 2.2) by giving it the bluetooth address directly and it works fine. It even is listed as paired after that..."
are you sure???
can you describe how you did that please (step by step) ?

running JP5 and froyo still skipping class 0x00 any clues ??

just patched libbluetoothd.so to allow class 0x00 on pairing, please back up your /system/lib/bluetoothd.so and copy this one in /system/lib, once your pairing is done replace your old libbluetoothd.so
this library comes from a JPA so it maybe ok for froyo, not for enclair.

Hi everyone,
I encounter the same issue with a Samsung Galaxy 3 GT-I5800 and a HTC Wildfire on Android 2.1. I am writing an application to exchange data with a simple Bluetooth device using Serial Port Profile. I tried scanning devices with both of these but the class of the device is not recognized. I'm a bit desperate right now.
Is there any issue to make it discoverable? Or there is no way and it's definitely over. Thanks in advance for your help.
Lorenth

yes, by patching libbluetoothd.so

Did you not say that it's working on Froyo but not on Eclair?

yes, that patch is for froyo only.

Well I'm using Eclair Is there a chance to have the same thing on Eclair? Or did you aware about another solution to fix it? Thank you for help anyway.

you need root and give me /system/lib/libbluetoothd.so and i will fix it.

husq510 said:
just patched libbluetoothd.so to allow class 0x00 on pairing, please back up your /system/lib/bluetoothd.so and copy this one in /system/lib, once your pairing is done replace your old libbluetoothd.so
this library comes from a JPA so it maybe ok for froyo, not for enclair.
Click to expand...
Click to collapse
so can we use this to pair our device with a wiimote? what do you mean by saying "once your pairing is done replace your old libbluetoothd.so" do we still need the old libbluetoothd.so even after using your patched version? another question, will this version work with JPO? if not, here is a JPO version to get patched by you! thanks in advance, would love to pair a wiimote with my sgs

bump bump bump bump

BlueEyes99 said:
so can we use this to pair our device with a wiimote?
Click to expand...
Click to collapse
No the Wiimote issue is a different one, the native Bluetooth libraries don't behave in the way the Wiimote IME developer is expecting on the SGS and HTC.

Verizon reply from their Admin
See this link:
add the http etc...
community.vzw.com/t5/Other-Android-Devices/Bluetooth-broken-on-Verizon-Galaxy-Tab/m-p/343162
From the admin: Moates
Re: Bluetooth broken on Verizon Galaxy Tab?
Options
12-06-2010 04:40 PM
We are aware of this issue and we are diligently working on resolving it. As soon as we get some additional information we will be sure to pass it along.

wow, this works!!
husq510 said:
just patched libbluetoothd.so to allow class 0x00 on pairing, please back up your /system/lib/bluetoothd.so and copy this one in /system/lib, once your pairing is done replace your old libbluetoothd.so
this library comes from a JPA so it maybe ok for froyo, not for enclair.
Click to expand...
Click to collapse
ok this is just super fine.
here is what i did (i am running DocRom XXJPU 2.0 now) while phone was running normally and fully switched on:
on SGS do:
turn BT off
reboot phone
after fresh reboot when phone is running normally and fully switched on
mount /system as r/w (use SGS tools)
on PC do:
> adb push <this libbluetoothd.so file> /system/lib/libbluetoothd_patched.so
> adb root
> adb shell
> cp -p /system/lib/libbluetoothd.so /system/lib/libbluetoothd_orig.so
> cp -p /system/lib/libbluetoothd_patched.so /system/lib/libbluetoothd.so
now on your SGS turn on BT and search, it will find your class 0x00 device
pair it and enter code
now back to the still open adb shell:
> cp -p /system/lib/libbluetoothd_orig.so /system/lib/libbluetoothd.so
> exit
on SGS do:
mount /system as r/o (use SGS tools)
and it all worked just super fine.
if somebody else would need this, we can make a script and automate this process

[S10e][Bluetooth] can't receive any file using BT

Hello,
I try to transfer photos from my Galaxy watch to my S10, but without success ... (in the other direction, it works without problem)
The tests I have already done:
- install different explorers on the watch > same result
- connected my S10 to my wife's P30 Pro > same result
Then I cut the BT, cleared the cache and deleted the data from the BT application.
After that, I reactivated the BT and reconnected the watch and the P30.
From there, transfers between the P30 and S10 worked in both directions and the same for the watch!
So I thought I had fixed the problem ...
This morning I wanted to transfer a photo from my Galaxy watch to my S10e again and it no longer works .... I did the same attempt again by deleting the data and the cache of the BT application, restarted the phone and the watch, but nothing to do ....
I even made a Wipe Cache Partition, but that didn't change anything ....
I specify that the "dialogue" is established between the watch and the phone, when I send the photo from the watch, there is the notification on the phone (and I can see the watch in the Galaxy Wearable app)
The only difference is that when the transfer works, there is a request for acceptance on the phone then, after validation, the transfer is executed.
Conversely, when it does not work (as currently), I have a notification on the phone of a transfer from the watch, but not the famous validation request ....... and after a moment I have the message of failure ....
And today, I made a factory reset on the watch and my S10e, and after restoring everything, the problem is still the same.... I can't receive file on my S10 by bluetooth...
Any one can give me some advice?
Thanks...

Hello, does anyone have this problem?

jbs68 said:
Hello, does anyone have this problem?
Click to expand...
Click to collapse
Sadely I haven't any smartwatch to test that but I would like to know : which firmware did you flash to get One UI 2.1 on your device ?
I red in your signature that you're currently running U4CTC9 firmware version that isn't rolling out yet in France on XEF CSC (France unbranded like me xD)

that's right, i used the latest DBT
DBT is a multi-CSC firmware (XEF is include) and if your current CSC is XEF, after flashing this one with the file named "Home_CSC_xxx" you'll keep your XEF CSC.
If you're French, you can have a look at here.

Hello,
The issue seems to have been fixed with the latest update of the Galaxy Wearable app....

Just rooted my s9

I've been using an s20 FE 5g. It's a great phone but touch screen issues, of course you can't root the thing and avoid mandatory software updates, news about the glass over the camera breaking, I also just got really tired of not being able to control my own phone. So I bought a used s9 exynos.
I went through a couple of root tutorials online but the one that finally worked was: https://www.thecustomdroid.com/samsung-galaxy-s9-plus-root/
With other methods I kept getting boot loops and couldn't mount the system.
Anyway, this seems to have worked for me, so I'm putting it out there in case anyone needs it. And now some terms in case someone does a google search:
root galaxy s9 android 10 sm-g960f

Have you been able to restore all or some of the functionality that's lost by tripping Knox, such as Secure Folder, Samsung Health, Samsung Pay, Google Pay, iris scanner, logging into secure apps with the fingerprint reader? I've read about MagiskHide but apparently that doesn't work for everything, and I've seen some application-specific instructions, but I'd very much like to hear from someone who knows from experience what lost functionality can be restored and what gotchas you can run into.

kettir said:
I've been using an s20 FE 5g. It's a great phone but touch screen issues, of course you can't root the thing and avoid mandatory software updates, news about the glass over the camera breaking, I also just got really tired of not being able to control my own phone. So I bought a used s9 exynos.
I went through a couple of root tutorials online but the one that finally worked was: https://www.thecustomdroid.com/samsung-galaxy-s9-plus-root/
With other methods I kept getting boot loops and couldn't mount the system.
Anyway, this seems to have worked for me, so I'm putting it out there in case anyone needs it. And now some terms in case someone does a google search:
root galaxy s9 android 10 sm-g960f
Click to expand...
Click to collapse
Thanks! I had the same experience you had trying to root my S9 Plus (SM-G965FD) on Android 10 One UI 2.5. This guide worked for me!

Question Android Wear OS

Can Wear OS run on the X Fold?
I have TAG connected watch and I read that it does not work with Chinese ROM

I have the TicWatch 3 PRO Ultra and although it was a pain in the ... to make it work, Managed it with both the Chinese and Play versions of the Wear OS app installed together. it is fiddly but eventually, it works. Also, I get all the notifications on the watch (even the ones that will not show up on the phone...

dee163 said:
Thanks for the feedback
Click to expand...
Click to collapse
Can you direct me a tutorial for this ?

dee163 said:
Can you direct me a tutorial for this ?
Click to expand...
Click to collapse
Tutorial unfortunately no as I did not follow any... First tried installing Wear OS from the Play store but it was not finishing the setup. Then I downloaded Wear OS from the Vivo store (the so-called Chinese version. This one does not have any Google Account integration) I gave all possible permissions to both of them (yes, they can be installed at the same time.) Then somehow the Play Store version worked and connected to the watch. I installed also the TicWatch App that is needed (in my case. Guess TAG has one too) and after some more fiddling with notification permissions, it just worked. I get all my notifications and everything seems to sync properly.
I hope that they will really release the phone in India next month, as usually, the Indian releases are Global ROMs with more compatibility with everything. Then we should be able to flash it on our devices...

I have my Galaxy Watch connected.
First loaded the Chinese Wear app, then the Galaxy Wear app.
BUT it won't stay connected. It's OK while the phone is open, but as soon as the phone logs off the Bluetooth disconnects.
I've given the Wear apps every possible permission and power settings but it just won't stay connected.

Just to update from my last post, I've decided to trade in my Galaxy Watch 3 for the new Watch 5. Will be interested to see if that makes any difference. Probably not

I have the same issue - cannot keep my galaxy watch connected (it's the 1st gen)
All is fine and after a while it just disconnects.
The galaxy Buds Live are fine and keep connected.
I'm using the Galaxy wearable app. (as these devices are not Wear OS i think)

Morb81 said:
I have the same issue - cannot keep my galaxy watch connected (it's the 1st gen)
All is fine and after a while it just disconnects.
The galaxy Buds Live are fine and keep connected.
I'm using the Galaxy wearable app. (as these devices are not Wear OS i think)
Click to expand...
Click to collapse
My Watch 5 is due later today. I'll be interested to see if that stays connected.

RR-99 said:
My Watch 5 is due later today. I'll be interested to see if that stays connected.
Click to expand...
Click to collapse
No success with the Watch 5, as I reported in a separate thread. I'll wait for the Pixel Watch.

Got my Galaxy watch (1st gen i guess) successfully paired and it keeps connected. As long as the 2 devices are bound. (once disconnected i have to reconnect via the wear app - no big deal)
Thing is though - battery usage of the watch is through the roof. I hardly get a full day out of it.
Anyone know what might be causing this?

Morb81 said:
Got my Galaxy watch (1st gen i guess) successfully paired and it keeps connected. As long as the 2 devices are bound. (once disconnected i have to reconnect via the wear app - no big deal)
Thing is though - battery usage of the watch is through the roof. I hardly get a full day out of it.
Anyone know what might be causing this?
Click to expand...
Click to collapse
First gen Galaxy Watches did not have a very good battery life to begin with... 1.5 to 2 days at most with good use. Another thing is that the connection between the watch and the phone is not stable for some reason (probably due to the stupid Vivo battery optimizations or some Bluetooth issue)... For instance, my Ticwatch Pro 3 Ultra GPS (names those things) lasted about 3 days with my old Galaxy S21 Ultra but now I struggle to get 2 with the Vivo X Fold...

Which Watch work with X Fold ? It seems no one actually. i have 2/3 Xiaomi, nothing work and it's not Band !!

Samsung Watch 3 works. Samsung Watch 5 does not work.
I now have Huawei GT3 pro and it works perfectly. Does not use Wear. Great battery life, eight days so far !

I agree nt so bad... nothing better than others... But qualitative.
Everything work ?

lesscro said:
Which Watch work with X Fold ? It seems no one actually. i have 2/3 Xiaomi, nothing work and it's not Band !!
Click to expand...
Click to collapse
Huawei models works without problems

maxant69 said:
Huawei models works without problems
Click to expand...
Click to collapse
Good to know !

OrionBG said:
Tutorial unfortunately no as I did not follow any... First tried installing Wear OS from the Play store but it was not finishing the setup. Then I downloaded Wear OS from the Vivo store (the so-called Chinese version. This one does not have any Google Account integration) I gave all possible permissions to both of them (yes, they can be installed at the same time.) Then somehow the Play Store version worked and connected to the watch. I installed also the TicWatch App that is needed (in my case. Guess TAG has one too) and after some more fiddling with notification permissions, it just worked. I get all my notifications and everything seems to sync properly.
I hope that they will really release the phone in India next month, as usually, the Indian releases are Global ROMs with more compatibility with everything. Then we should be able to flash it on our devices...
Click to expand...
Click to collapse
I have a Vivo X Note and also a TicWatch Pro 3 Ultra. Wear OS works well together with the Chinese version. The only and for me the biggest problem is that I cannot pay with a card via Google wallet from watch. When I open the apk and want to add a payment card, it says a connection error with my mobile phone, and on my X Note Wallet does not open through google play services, and I cannot add the card to the watch. I have no problem with paying on my mobile, Wallet works ok there. If I connect the watch to the Lenovo Yoga Tab tablet, Wear OS from the Google Play Store works there without any problems, and I also add all the cards to the Wallet in the watch. I read on the forums that the problem is with the new versions of the Google Play services and that it will help to downgrade the older version lower than 21.26.58. The problem is that when installing, the system gives an error and cannot be installed... So at the moment I have a working watch, but no payment, which is frustrating. Have you tried paying with your watch?

Kucko34 said:
I have a Vivo X Note and also a TicWatch Pro 3 Ultra. Wear OS works well together with the Chinese version. The only and for me the biggest problem is that I cannot pay with a card via Google wallet from watch. When I open the apk and want to add a payment card, it says a connection error with my mobile phone, and on my X Note Wallet does not open through google play services, and I cannot add the card to the watch. I have no problem with paying on my mobile, Wallet works ok there. If I connect the watch to the Lenovo Yoga Tab tablet, Wear OS from the Google Play Store works there without any problems, and I also add all the cards to the Wallet in the watch. I read on the forums that the problem is with the new versions of the Google Play services and that it will help to downgrade the older version lower than 21.26.58. The problem is that when installing, the system gives an error and cannot be installed... So at the moment I have a working watch, but no payment, which is frustrating. Have you tried paying with your watch?
Click to expand...
Click to collapse
I never got google wallet to work on mine too…

Kucko34 said:
I have a Vivo X Note and also a TicWatch Pro 3 Ultra. Wear OS works well together with the Chinese version. The only and for me the biggest problem is that I cannot pay with a card via Google wallet from watch. When I open the apk and want to add a payment card, it says a connection error with my mobile phone, and on my X Note Wallet does not open through google play services, and I cannot add the card to the watch. I have no problem with paying on my mobile, Wallet works ok there. If I connect the watch to the Lenovo Yoga Tab tablet, Wear OS from the Google Play Store works there without any problems, and I also add all the cards to the Wallet in the watch. I read on the forums that the problem is with the new versions of the Google Play services and that it will help to downgrade the older version lower than 21.26.58. The problem is that when installing, the system gives an error and cannot be installed... So at the moment I have a working watch, but no payment, which is frustrating. Have you tried paying with your watch?
Click to expand...
Click to collapse
I will never work, as Android Auto, Google backup, Google Timeline and Ok Google activation.
Vivo doesn't use a full Google Play Service framework as they have Jovi application instead of Google one.

Hello
Does anyone manage to make the Remote Connection work? It's missing in the Galaxy Wear settings.
I'm guessing it's related to the Wear OS China version app.

Accessories Galaxy Watch 5 - Good news, Bad news

Just got my new Galaxy Watch 5. It looks great, very smooth appearance
Installed it in the usual way after removing all the old apps and starting from scratch including Watch 5 patch.
Good news - Galaxy Wear found the watch straight away and did the bluetooth pairing.
Bad news - Galaxy Wear immediately said "This watch is not supported on this phone."
I'll be having an other go later on, but it's looking like the watch will be going back.

If you have an older copy of Wearables try that after uninstalling the new version. Make sure you get all the apps for the watch.
Firewall block the old version's updates though before opening it... or it will update.
Conversely try updating everything including the watch firmware. Sequence* of your actions here can effect the outcome. Wearables can be quit the terror but I've always gotten my Buds+ to work right, one way or another
Samsung tech may be useful as may Samsung forums. It sucks but so does a lot of things; bennies for success, nothing for failure.
*trial and error, and yes it can take multiple attempts. DO NOT factory reset!
Clearing the system cache and especially a network reset may help. Make sure Wearables has all its permissions, CHECK!!! It will puke on you if it doesn't! No warnings why either

I've been back again, tried everything I learned in getting the Watch 3 to work. But this one is different, it's not like the failures before when something just doesn't work or goes into a loop. This is the first time Galaxy Wear has connected to the Watch and then said definitely that it is not comparible with the phone. I'm having bad feelings about it.
The other thing I would say though is, are Samsung going to sell the Watch 5 into China? If so it should work with Chinese phones - unless it has different firmware.

Watch 5 returned. Waiting for Pixel Watch.

RR-99 said:
Just got my new Galaxy Watch 5. It looks great, very smooth appearance
Installed it in the usual way after removing all the old apps and starting from scratch including Watch 5 patch.
Good news - Galaxy Wear found the watch straight away and did the bluetooth pairing.
Bad news - Galaxy Wear immediately said "This watch is not supported on this phone."
I'll be having an other go later on, but it's looking like the watch will be going back.
Click to expand...
Click to collapse
Another horrible news about Vivo Security and policies.

Anyone had the Samsung Galaxy Watch 5 to work with the Wear OS version from Vivo app store?

yes i have the watch 5 pro working i have had vio x fold,vivo x fold plus and now vivo x fold 2 and it worked on all
what you have to do is uninstall all the versions you have of samsung wearables and plugins then go to this link and install this version of wearables http://samsung-gear.apk.watch/2.2.41.21071361/for/huawei-honor-8
once that is installed open up the settings of ur phone go to bluetooth and connect to your watch then open up the wearables app and it will download an update follow it through and it will work perfect for you
just remember to set the wearable and watch os apps to be locked in the task killer screen and set the battery management to high power for the wearable and watch os apps to make sure you get all your notifications and for it to stay connected

darzy88 said:
yes i have the watch 5 pro working i have had vio x fold,vivo x fold plus and now vivo x fold 2 and it worked on all
what you have to do is uninstall all the versions you have of samsung wearables and plugins then go to this link and install this version of wearables http://samsung-gear.apk.watch/2.2.41.21071361/for/huawei-honor-8
once that is installed open up the settings of ur phone go to bluetooth and connect to your watch then open up the wearables app and it will download an update follow it through and it will work perfect for you
just remember to set the wearable and watch os apps to be locked in the task killer screen and set the battery management to high power for the wearable and watch os apps to make sure you get all your notifications and for it to stay connected
Click to expand...
Click to collapse
I have both watch 4 and watch 5 connecting to vivo without any issues. Do not use the Samsung wearable app from the play store but use the above apk. Once the phone is synced, all the Samsung plugins gets updated to the latest version.