Hi there, my first post on a bug I think I've found in Sentinels ROM v4.80 for my Nexus 10 32GB.
Problems arises when trying to sync up Sixaxis utility to PS3 controller - it worked fine in the previous version now not working at all. Have tried various permutations of ROM and the default kernel and also tried Trinity Kernel still no bluetooth/sixaxis sync.
I have performed a full wipe as per instructions in SentinelROM thread.
Would be grateful if you could look into this as this is my fave ROM by far :laugh:
Have tried ParanoidAndroid, Cleanrom, Saber, EOS, Purity (comes close but AOSP browser crashes every 2-5 mins).
I would also like to take the opportunity to say thank you to all the developers:good: I've been trying roms since the early days of my HTC G2, through Xperia Play, Nexus 4 and Nexus 10 and it's been a wild journey:fingers-crossed: sometimes:laugh:
All the best
Just updating this thread as other folks are having problems with connecting bluetooth devices using Sentinels ROM v.4.80. Hopefully it'll be fixed in the next version:good: Fantastic job on the ROM otherwise
4.80 blutooth
Tablet talk no longer works with 4.80 over blutooth either.
I recently got a Fitbit Force as a gift and noticed that it uses BLE (Bluetooth Low Energy) to pair with your phone. I tried from my Razr M running the CM11 20131228 nightly and it doesn't find it.
Anyone know if there is a way to get this to work?
Does BLE run on the CM10.2 20131102 Snapshot build or any other roms?
Bluetooth BLE is not supported in CM releases it seems, my Tab didn't have any issues finding BLE devices on stock ROMS only CM releases
If you go to Apps/All & scroll drown, your find org.codeaurora.bluetooth ,
maybe you could raise the question here: https://www.codeaurora.org/forums/bluetooth
Hi I have searched for answers but am stumped now.
I am using Google Play Edition 06-08-2014 by Danvdh and I love the rom but when using the phone in my 2011 Mercedes Benz the phone was randomly rebooting on the 4.4.2 rom.
After updating to 4.4.3 rom the bluetooth connection drops out sometimes when trying to make or receive a call, it eventually reconnects but it is very frustrating. I am even considering moving back to my iphone if I can't sort this one out.
Any advice would be greatly appreciated.
Cheers
The first paragraph of the rom you are using:
This is the latest build for the I9505-G Google Edition S4 official from Google/Samsung, I have made quite a few optimizations to the ROM and added the tools necessary to give it the features (100% working features that is) of an AOSP ROM, Google edition does not use open source proprietary which mean's Bluetooth, and most importantly the camera will work way better out of the box since Samsung builds this ROM (Full HDR support, 1080p video recording, no green lines on the front cam).
I don't think there is much you can do. Maybe a different kernel would work, but I doubt it.
If you want working bluetooth you should flash an TW based rom.
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Blazing angel said:
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Click to expand...
Click to collapse
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
BassBlaster said:
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Click to expand...
Click to collapse
It is a rev_11
paul c said:
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
Click to expand...
Click to collapse
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Mine is also a rev11, 303k. I guess that rules out hardware issue
Blazing angel said:
It is a rev_11
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
I'm experiencing exactly the same problems than Blazing angel.
Bluetooth is unusable in my car, "Unfortunately, the process com.android.bluetooth has stopped" being displayed repetitively.
I suspect it's not hardware related as I do not have problem using the stock or paranoid ROMs. Unfortunately, my favorite ROMs (AOKP, CN or Carbon) are causing problems.
Do you think it's possible to pickeup some files in the paranoid files and inject them to Carbon to solve the problem ?
Thanks in advance for your help !
paul c said:
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
Click to expand...
Click to collapse
Great ! I was able to bypass my bluetooth problem using this Android 4.4.4 rom, without loosing great features of Carbon or Pac-ROM ! :victory:
Thanks for sharing this ROM Paul ! :good:
Hello Community,
Has anyone have had any success with AOSP based rom and syncing their phones via bluetooth with their car audio?
I've tried numerous roms, including CM11, Carbon, and SlimKat with no success.
Although, my phone successfully paired and everything. However, upon returning to my car (2013 Prius), my phone doesn't reconnect successfully. Oftentimes, I get these "bluetooth has crashed not responding" popup.
TouchWiz rome work flawlessly, of course.
Anyhow, if there is a trick to get this to work, I would really appreciate it. I love AOSP.
Thanks!