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/platform/frameworks/base/+/b88fa82^!/) 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
Hello!
I too am working on such a project and during my studies have successfully connected my android to my iPhone with one extra step: since android can only act as the central and connect to a peripheral, the iPhone has to be put into peripheral mode, for which I used LightBlue (look in the app store). After they connected I was able to discover the GATT service, but I'm new to android and this is a huge project so I'm kinda lost after that. Would you mind sharing your code with me so I can collaborate with you on this? I'd love to release something like this to the XDA community, and if you're closer than I, I'd love to help!
I hope this answer helps you, but I may be completely misunderstanding the question.
Thanks!
Zachal
Related
Hi Guys, i would like to know if someone is interested to work on a MANET running on android phones...
i have actual develop an specific Routing Protocol for Manets and simulated in Opnet and works well, i don't have to much skills on Java Programming or android software development and need help to develop the code for it...
basically the project is to run several android phone that will be able to use adhoc mode to create network and each node to be able repeat the signals to the next near node....
Regards
You may want to post code in C or C++ . No doubt someone would convert it into the proper Java android code. I suspect some of it would need to be wrapped anyway and that it's highly likely to require root access.
Finally
Finally someone working on Mobile Adhoc Network have acomplish a MANET protocol on android Phones, they have implemented an OLSR and BATMAN routing protocol..
http://www.servalproject.org/
Thank you serval for this implementation....
Hello,
First off, apologies if I have posted this in the incorrect forum.
The company I work for is looking to update one of it's product lines and has been toying with the idea of using Android as a development platform. Up until now the philosophy has always been to develop simple, bespoke embedded software that provides only the functionality that is needed at the time. The device itself will be a medical device, and as such will have no telephony requirements (and associated things like contacts, calander and the large majority of the pre-installed Android apps).
I have read, and understand it is possible to re-compile Android from source and remove all of these non-required functionality. My question is really if that is worth doing? i.e. stripping out all un-needed applications that get build into a stock ROM. Or would it be a more efficient to use some form of OTS embedded Linux platform?
Something in Android 4.0 that does seem to be useful is the support for Bluetooth HDP.
Kind Regards,
Simon
Well there are other devices that aren't phones that use Android. Take the motoactv for example. It's a fitness watch that runs a stripped version of Android, but it's still Android and applications can still be programmed and installed to it.
May be a dumd question, but I'm asking anyway. Why is Android so hardware specific?. or better yet, why can't you install any android system on any phone?
example: you can install windows or linux on any system, you don't have to have a certain set of chips. Is it a propitiatory type thing with these phone makers. is the whole android system so small, that the coding can't be added to make it installable on any phone.
I'm not a coder, or prgrammer, I do understand it enough to read what it is doing, but cannot write anything. Can someone shed some light on this
Thanks in advance
You've got this completely bass ackwards. Android is decidedly not hardware specific. Phones, tablets, computers, car stereos, home heating/AC, watches, TVs, etc. Android is open source, which means anybody can develop it to work on just about any platform they wish. I mean, you can get refrigerators and microwaves that run Android for Pete's sake.
If you're complaining that you can't get Android on an iPhone or a Nokia Lumia, then you're barking up the wrong tree.
To add some more "devices" to the list above on which android can be installed - cars! I'm working in that industry now
And the answer above is right - if your device is totally closed for others, then you will not be able to install anything on it, maybe, without really breaking into it. Android can be put mostly on any hardware - if the hardware manufacturer wants it. The short description is - Android is implemented on top of HALs (Hardware Abstraction Layer) which are then implemented by manufacturers specific to their devices and then Android works "out of the box".
Can we have nexus 7 2013 lte act as bluetooth headset and have phone book access profile please.....
www.bluez.org they have the whole source code to put this in to any rom, i do not know how to put but someone who knows i think should be straight forward
also there are roms from huifei who manufactures car stereos with bluetooth functionality in them and they are based on android ... http://forum.xda-developers.com/showthread.php?t=2660662
can we have this functionality please in nexus 7 ?
infra4800 said:
Can we have nexus 7 2013 lte act as bluetooth headset and have phone book access profile please.....
www.bluez.org they have the whole source code to put this in to any rom, i do not know how to put but someone who knows i think should be straight forward
also there are roms from huifei who manufactures car stereos with bluetooth functionality in them and they are based on android ... http://forum.xda-developers.com/showthread.php?t=2660662
can we have this functionality please in nexus 7 ?
Click to expand...
Click to collapse
Last I checked, the bluez stack was missing some important Android functionality, so getting this functionality would require sacrificing other capabilities and it would also require a LOT of work.
It would also probably make life a living nightmare for some of our device maintainers.
Entropy512 said:
Last I checked, the bluez stack was missing some important Android functionality, so getting this functionality would require sacrificing other capabilities and it would also require a LOT of work.
It would also probably make life a living nightmare for some of our device maintainers.
Click to expand...
Click to collapse
There is source code available for a product called carpod, and android car head unit which also has this bluetooth functionality... i downloaded the source code, and it has gradle files etc... i have no idea how and what to look in to the source code... any suggestions where to look? how to open the complete source code in android development studio etc?
the link for that source code is under Helpful Links section -->> http://forum.xda-developers.com/showpost.php?p=55200512&postcount=1
i really hope a developer can just add this functionality which is already implemented in many available car head units running on android...
infra4800 said:
There is source code available for a product called carpod, and android car head unit which also has this bluetooth functionality... i downloaded the source code, and it has gradle files etc... i have no idea how and what to look in to the source code... any suggestions where to look? how to open the complete source code in android development studio etc?
the link for that source code is under Helpful Links section -->> http://forum.xda-developers.com/showpost.php?p=55200512&postcount=1
i really hope a developer can just add this functionality which is already implemented in many available car head units running on android...
Click to expand...
Click to collapse
Is it possible? Yes.
Is it more work than we have time for? Absolutely
To do so would involve either adding a new profile to the Android BT stack (none of us have any familiarity with it) or dropping in BlueZ, which has some really nifty features (such as native DualShock controller support), but its support for other important features (like Bluetooth LE) is, if you read their changelogs, a heavy work in progress and experimental. Which means that if we did this for your niche feature, we'd break widely used functionality (like communication with Android Wear watches). There's also the fact that EVERY device maintainer would have to make changes to their audio routing configs to support this, and trust me, messing with audio routing is a MASSIVE PAIN IN THE ASS that no one wants to mess with.
Hello Devs,
I am working on idea where i want to make my android device as input device to other devices(PC,PS,IOS phones,android devices).
I am able to achieve this using bluetooth client and sever application running on 2 devices.
But after lot of research i found that android device can be used as bluetooth HID input device i have got rooted device with me but i am unable to use HID profile to implement this.
I have seen some projects but they are developed with different version of android which are not compatible with greater that 4.2.
Can anybody help me with this ,any kind of system level modification can be accepted as i have rooted device.