I'm wondering if there is anyone out there that might be interested in building a "stock" ROM for the Nexus 5 that uses the BlueZ bluetooth stack instead of the default Bluedroid stack. It should be very simple, as the BlueZ for Android project has done most of the work, including building the kernel. It looks to be as simple as downloading the various source files and compiling. I was attempting to do it myself but I couldn't ever get Linux installed on my PC. Well, I got it installed but could never boot into it. I feel bad asking someone else to build it, but like I said, my PC setup seems to be Linux-averse and my understanding is that this is a simple build.
The impetus for this is that I recently upgraded my car stereo to a bluetooth-enabled unit but I can't transmit the track metadata. Even though the head unit supports AVRCP 1.3, and the Nexus 5 should also support AVRCP 1.3. I'm unlikely to get a firmware update from the stereo manufacturer. All my reading on the issue suggests that bad things happened for Android bluetooth when Google switched from the BlueZ to Bluedroid stack. I'm hoping that incorporating BlueZ in my phone might just increase compatibility between my phone and head unit.
The relevant links for making the build are here:
http://git.kernel.org/cgit/bluetooth/bluez.git/tree/android/README
https://code.google.com/p/aosp-bluez/
What is BlueZ?
Related
So i understand that there are Pioneer Avic car stereos that run windows ce and there is a way to access the windows side of the ok. seeing as that is possible would it be a possibility to flash android to the stereo and integrate all the components. perhaps use something similar to the fm app that comes on the htc evo for radio and create an app for dvd/cd/etc etc and use the integrated BT to interface with a phone to access internet and apps.
this would be an awesome project however i do not have the programming expertise that would be necessary and i believe there would be many others interested.
I LIKE THIS IDEA!!!! I Have a Pioneer AVH-P4200DVD model... im not a pro yet, but I would love to learn how to mod my stereo if it was possible. Do you have a base idea or any resources on how to do it yet?
there are discussions on this forum about gaining access to the windows CE OS on the AVIC but i have no resources, out here driving truck it is not often i get online
If you get in to the WinCe probably you can use Haret to boot in Linux/Android. but actually you have to build an android image for your hardware. So first you need to investigate what is the hardware on which the WinCe work, then you can search for an android port for this hardware or start porting the OS by your self. Good Luck!
Hey,
I've recently dived head first into android app development. I was messing around with the LatinIME that is available on the the AOSP source code tree.
I've managed to get it working fine on my 4.0.3 device, but i'm having serious problems trying to get it to work on devices with lower API Levels.
It's got lots of deprecated packages inside it, so i believe there must be some easy way of getting it to run without FC's on older devices, but i just can't figure it out!
Other people have already done this, as it's available on the market, and i'd appreciate any guidance anyone can offer.
Is it just a case of rewriting the 4.0 only functions?
Thanks,
Jack.
Ever since Android replaced Bluez with BlueDroid, people (incl. myself) were upset by the lack of L2CAP.
Fortunately, BlueZ guys took the extra mile and created the BfA (BlueZ for Android) project, which, as of today, is already feature-complete, it seems. More about it here:
https://01.org/bluez-android
http://www.bluez.org/release-of-bluez-5-21/
If we can believe those articles, replacing BlueDroid with BlueZ should be fairly straightforward. Would love to see OmniRom with Bluez and L2CAP support (plus all the goodies of BlueZ), especially for my Galaxy SII
also it would be good to have AVRCP 1.5 in. browsing media files and so on via BT is a thing that is really missing...
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
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.