Hello Folks,
I seen a rumor that Android may about to support iOS on its wear platform. Think Moto360 with iPhone.. See This
Since Android shipped about 720,000 device in 2014, compared to 4.6 million wearable devices in 2014 by estimates. See Here
I have been working on developing an application for the Android Wear platform that will allow iOS communication, but there is a well known bug in Android that is preventing connecting to an iOS device. This is despite Android Wear supporting Bluetooth LE GATT profile, and will connect with most other bluetooth devices over Bluetooth LE using the GATT profile. You would think it seems like an iOS issue. When you dive into the communication handshake between the devices when attempting a connection between Android Wear and iOS, you get an error.
This has been reported to Android and since then, not fixes. I understand they have bigger fish to fry than allowing their watches to support iOS, but since their devices are not selling well this may push them into fixing the bug.
See This ... It explains how the bug in android is failing connecting to iOS devices due to their bug..
I did some deep diving and reviewed the code for the BluetoothDevice.java file in the Android Development Studio and found that there is the option to select either Normal Bluetooth or LE via a transport parameter with connecting... BUT... When android implemented their specific code, they OMITTED the transport parameter and it SHOULD connect via LE, but doesn't.
Here is my comment on the above thread (Issue 58896):
Reviewing the android code for BluetoothDevice.java I found that connectGatt() function has a hidden int TRANSPORT variable that will allow you to use AUTO or specific LE or BR/EDR only.
For some reason, this is available in the BluetoothDevice.java file in android studio, but not listed in the android code reference. When you attempt to use this, it gives you an error. If someone can explain how we can fix the compiler on android studio to compile our code using the TRANSPORT_LE option instead of TANSPORT_AUTO which I assume is being used.
I see someone with Broadcom has requested that the transport parameter be added in May 2014 on the android GIT page (https://android.googlesource.com/pla...+/b88fa82%5E!/) which is almost 7 months ago. If this is such a seemingly prominent problem and so many fixes since then and this hasn't been fixed??
So this has been reported by Broadcom in May 2014..... and no fix as of yet???
I am curious how MohammadAG bypassed this snafu. Any thoughts?
Here is his proof..
hhttps://www.youtube.com/watch?v=DIIYmVSc9Yw
I seen a rumor that Android may about to support iOS on its wear platform. Think Moto360 with iPhone.. See This
Since Android shipped about 720,000 device in 2014, compared to 4.6 million wearable devices in 2014 by estimates. See Here
I have been working on developing an application for the Android Wear platform that will allow iOS communication, but there is a well known bug in Android that is preventing connecting to an iOS device. This is despite Android Wear supporting Bluetooth LE GATT profile, and will connect with most other bluetooth devices over Bluetooth LE using the GATT profile. You would think it seems like an iOS issue. When you dive into the communication handshake between the devices when attempting a connection between Android Wear and iOS, you get an error.
This has been reported to Android and since then, not fixes. I understand they have bigger fish to fry than allowing their watches to support iOS, but since their devices are not selling well this may push them into fixing the bug.
See This ... It explains how the bug in android is failing connecting to iOS devices due to their bug..
I did some deep diving and reviewed the code for the BluetoothDevice.java file in the Android Development Studio and found that there is the option to select either Normal Bluetooth or LE via a transport parameter with connecting... BUT... When android implemented their specific code, they OMITTED the transport parameter and it SHOULD connect via LE, but doesn't.
Here is my comment on the above thread (Issue 58896):
Reviewing the android code for BluetoothDevice.java I found that connectGatt() function has a hidden int TRANSPORT variable that will allow you to use AUTO or specific LE or BR/EDR only.
For some reason, this is available in the BluetoothDevice.java file in android studio, but not listed in the android code reference. When you attempt to use this, it gives you an error. If someone can explain how we can fix the compiler on android studio to compile our code using the TRANSPORT_LE option instead of TANSPORT_AUTO which I assume is being used.
I see someone with Broadcom has requested that the transport parameter be added in May 2014 on the android GIT page (https://android.googlesource.com/pla...+/b88fa82%5E!/) which is almost 7 months ago. If this is such a seemingly prominent problem and so many fixes since then and this hasn't been fixed??
So this has been reported by Broadcom in May 2014..... and no fix as of yet???
I am curious how MohammadAG bypassed this snafu. Any thoughts?
Here is his proof..
hhttps://www.youtube.com/watch?v=DIIYmVSc9Yw
Aucun commentaire:
Enregistrer un commentaire