I have tried many cooked ROMS, Darkys, DOC for example and several others. They are all great and fast, a few bugs here and there, but in general I'm a fan, but.
Everyone of them breaks the bluetooth rSAP profile and makes my phone pretty unusable in my Audi.
Symptoms are dropping connection, no phonebook (or intermittent) transfer. No connection at all after it drops until phone is rebooted. Similar problems are with HFP bluetooth profile as well. This is with any cooked ROM.
My only solution to the issues was to install a stock gingerbread 2.3 JVK ROM with no mods.
I have posted a few times on the developers threads but nobody seems interested.
So just a message to developers, what could it possibly be that you are all doing that breaks the bluetooth so badly?
Maybe try a cooked rom but using stock kernel. Don't even root it. If it doesn't than probably it has something to do with the kernel.
Possibly, but most cooked ROMs come pre-rooted with tweaked kernels.
I guess I could build one in the DOC's kitchen without any tweaks.
You only talking about 2.3.3 ROMS? Or does Darky's V9.5 do it as well? If 2.2.1 works fine on a custom ROM, that would be more important to me than having a non-stable gingerbread ROM until Samsung release an official update? V9.5 is pretty unreal so I see no reason to bother with 2.3.3 yet That is if you rely on bluetooth working in your car more than 2.3.3 ^_^
craigyb said:
I have tried many cooked ROMS, Darkys, DOC for example and several others. They are all great and fast, a few bugs here and there, but in general I'm a fan, but.
Everyone of them breaks the bluetooth rSAP profile and makes my phone pretty unusable in my Audi.
Symptoms are dropping connection, no phonebook (or intermittent) transfer. No connection at all after it drops until phone is rebooted. Similar problems are with HFP bluetooth profile as well. This is with any cooked ROM.
My only solution to the issues was to install a stock gingerbread 2.3 JVK ROM with no mods.
I have posted a few times on the developers threads but nobody seems interested.
So just a message to developers, what could it possibly be that you are all doing that breaks the bluetooth so badly?
Click to expand...
Click to collapse
I had same problem... I've changed the kernel to Supercurio kernel and since then not even single problem, else I use to have same problems as u having and were happening several times in a day. Cook a rom in romkitchen with SC kernel and see if that help
It has happened since around 8.0 of Darkys ROM, I must admit I have always used Voodoo Kernels with lagfix, so maybe an SC kernel will fix the issues.
I just installed the stock gingerbread 2.3.3 yesterday afternoon and I've had no issues since, before that the highest release I used was JS8 with the latest ginger modem JVK?
I was on 2.2.1 Ultimate and there wasnt any issues with BT headset stereo using headphone and media profile. It was also working fine with my MB car connections.
Now I'm on Criskelo GB and besides the crappy sound of gingerbread, bt still not an issues with MB car or headset. Criskelo is based on DaminGTO kernel.
It was also working on the Pioneer BT Audio receiver, xplod series.
I never had those problems with using Stock FW.
Now iam on JVK erveryting is fine.
Iam on rSAP with a Mercedes Comand NTG1 + V2 BT Module.
One thing never worked, is the PBAP Phonebook Access Profile,
so only the sim contacts are visible in the comand!
Ok, stock JVK is ok and a cooked JVK ROM from the kitchen with a supercurio kernel is ok as well.
Full phonebook/dialled/missed/received transfer in rSAP mode to my Audi A7 with MMI 4G.
So it seems the issue is Voodoo kernels.
Related
So I having a recurring problem with all of the non-Sense builds that I've tried here on the forum. The bluetooth would pair and connect perfectly in all the cases. However, the problem arises when I tried to make a call. The phone would freeze up or come to crawling halt. The dialing screen would go black, and then I would get the android.phone.process force close error. And I would need to pull the battery and reboot.
The issue has happened every single time with any of the non-sense builds I've tried so far: NexusHD2-FRG83, HyperDroid v1.6, Bangsters v1.5, and shubCRAFT v1.5.
I've tried with the included kernels with each build, and also with different combinations of kernels with the above builds as well, hasparin r4.1, r7.2, r7.4, r7.5 and michyprima r11. And still the same issue.
I'm certain there are other people with this same exact problem. So there has to be something going on with these non-Sense builds.
I have two bluetooth headsets, Plantronics 925 and 975. Same problems on both.
I don't like Sense, but I have to use a Sense build because bluetooth calling is very important to me. I hope some of you developers can come up with something to fix this.
Hi. I had exactly same problem.
Try to push play&pause music ,start&stop voice action
before start use bt.
Another solution is push bt call button immediate after make call
Sent from my Nexus One using XDA App
That didn't work for me.
I had the same problem as the OP and thats why i switch to a sense build also
Did you try this before?
http://forum.xda-developers.com/showthread.php?p=8348326
zoftdev said:
http://forum.xda-developers.com/showthread.php?p=8348326
Click to expand...
Click to collapse
Yes, I've tried that. But those files are for sense builds, and when I transfer them to a non-sense build, BT wouldn't even turn on.
See the FAQ in my signature. Some of the builders have BT working on CM6 with the EVO kernel so you should soon see builds that support it.
Sent from my HTC HD2
hastarin said:
See the FAQ in my signature. Some of the builders have BT working on CM6 with the EVO kernel so you should soon see builds that support it.
Sent from my HTC HD2
Click to expand...
Click to collapse
Wow! That's superb news.
BT Works
raysacr said:
So I having a recurring problem with all of the non-Sense builds that I've tried here on the forum. The bluetooth would pair and connect perfectly in all the cases. However, the problem arises when I tried to make a call. The phone would freeze up or come to crawling halt. The dialing screen would go black, and then I would get the android.phone.process force close error. And I would need to pull the battery and reboot.
The issue has happened every single time with any of the non-sense builds I've tried so far: NexusHD2-FRG83, HyperDroid v1.6, Bangsters v1.5, and shubCRAFT v1.5.
I've tried with the included kernels with each build, and also with different combinations of kernels with the above builds as well, hasparin r4.1, r7.2, r7.4, r7.5 and michyprima r11. And still the same issue.
I'm certain there are other people with this same exact problem. So there has to be something going on with these non-Sense builds.
I have two bluetooth headsets, Plantronics 925 and 975. Same problems on both.
I don't like Sense, but I have to use a Sense build because bluetooth calling is very important to me. I hope some of you developers can come up with something to fix this.
Click to expand...
Click to collapse
I have been running with BT on several builds for a couple of months now including the NexusHD2-FRG83 builds mentioned above. In fact if a build does not have working BT I skip it. I have found that the first time you install the build and try to use handsfree you need to do the trick of selecting/de-selecting and then selecting BT in the call screen before the actual connection. I use my phone constantly for work with speaker phone (Motorola EQ7) and my headset (BlueAnt T1). No problems making or receiving calls. I use the BT in both phone audio and media audio modes without any issues.
jinharry said:
I have been running with BT on several builds for a couple of months now including the NexusHD2-FRG83 builds mentioned above. In fact if a build does not have working BT I skip it. I have found that the first time you install the build and try to use handsfree you need to do the trick of selecting/de-selecting and then selecting BT in the call screen before the actual connection. I use my phone constantly for work with speaker phone (Motorola EQ7) and my headset (BlueAnt T1). No problems making or receiving calls. I use the BT in both phone audio and media audio modes without any issues.
Click to expand...
Click to collapse
before it's only supported on RMNET or non evo kernel.. the NEW NexusHD2 that was just released now supports BT on all currently available kernels... you don't even have to do the on, off, on trick anymore for the bluetooth to work.. i think it's the closest to being the perfect android build for our HD2.. everything just works including the MMS which i'm having problem with all the sense builds (low res image)..
I will load NexusHD2 1.5 tonight and see what I find
Finally a non-sense build with working bluetooth. I was able to bluetooth music and make a call using my car stereo. I just had to post this. http://forum.xda-developers.com/showthread.php?t=804210
Hi all,
I wonder why no one is asking or investigating the AVRCP issues on ROM's without Sense? It looks like something is missing in those roms that can be found inside Sense ones.
The bt call function is working as designed but play/pause/next/prev doesn't.
Any ideas?
The issue is that HTC have used their own bluetooth stack in their Sense based roms.
This stack supports the features that you are talking about.
Unfortunately, stock roms use a different stack which do not have the same features as the Sense stack.
This isn't an issue only on the HD2.
Can we get that stack and put it to nonSense roms?
AVRCP has been working on every CM6 build I've tried until recently. Just over the last week or so since I've updated to more recent nightlies I've found its stopped working. I'm currently using ginger_hd2 and it doesn't work. Also the mdj aosp gingerbread doesn't work and mdj streak ram v0.5. All the builds I've tried today!
I was using passion nightly 270 (or bravo, can't remember) and that worked fine.
Sent from my HTC HD2 using XDA App
Never worked for me since I tried HyperDroid and other roms.
I'm going to revert back to my old build later today to see if it still works. I thought it might be a problem with my headset as I dropped it the other day but I tested it last night with Windows Media Player on my PC and it worked OK, switching tracks, play, pause, etc.
Will let you know how it goes.
Sent from my HTC HD2 using XDA App
OK - It definitely works with my previous build.
This build is based on the Passion nightly CM6.1 v270
As I say, I've had it working on pretty much every build since the beginning of Android on the HD2 - it's only stopped working on the Gingerbread-type builds.
ie. It doesn't work on MDJs actual 2.3, or the Ginger_HD2 based on 2.2.1 with Gingerbread-style notifications, etc.
I can't work out if it's coincided with me using builds which have the newer initrd.gz...
Let's hope someone who knows about this stuff reads this thread!
What is this build with CM 6.1? Can you link it?
http://www.multiupload.com/FQCU3UV070
Try this... this one's based on 293 nightly.
Mine was a hybrid I kinda created myself using michyprima's nightly build v4, then incorporating the passion 270 files. If you look at this thread:
http://forum.xda-developers.com/showthread.php?t=824601
It'll explain how to do it...
OK, well I did some trying to fix it using MDJs Gingerbread v0.8 but no joy.
I tried replacing the three bluetooth libraries (libbluedroid.so, libbluetooth.so and libbluetoothd.so) with the working ones from my build but that didn't work.
I also tried replacing the AudioBTID.csv file as it had some slight changes and whilst it didn't fix the issue, it doesn't seem to have broken anything.
I'm currently looking at the bluetooth conf files in /system/etc/bluetooth to see if there's any differences there... think we need some dev help on this one though - I'm pretty much at the limit of what I can do....
Nope, no difference in the conf files. Also changed over the two .so files in /system/etc/lib/bluez-plugin
Again, this didn't work but didn't seem to break stuff!
That's bad. Even Sense roms has problems with media controls profile such as connecting automatically to Phone Audio only.
I feel like 1 from 1000 use it, so nobody cares
Just in case anyone finds this thread again...
MDJs NAND CM7 builds now have AVRCP working again. If you want a build without sense but with this working I suggest you try them! I'm a happy camper again!
Sent from my HTC HD2 using XDA App
Any updates on AVRCP on our devices? I am on CM7 (BoyPPC HoneyComB v31), and AVRCP does not work Do the GB sense ROMs have AVRCP capability?
I tested a few SD ROMS and AVRCP works with:
RAFDROID_HD_SD_4_2 (Sense)
AmeriCanAndroid (Gb)
JaguarMIUI-V11 (Gb)
I've tried all the froyo and gingerbread rooms for my GT540 but none seen to have Bluetooth headsets working. As I use the phone for work and have a long drive coming up it looks like I'm going to have to go back to stock 2.1 so I can drive hands free.
I would have through that due to the legal implications in some countries Bluetooth headsets would be a high priority.
Anyone working on a 2.2+ rom with Bluetooth headset working?
Why don't you try 2.1 ROM soft-modded by MMXTREM ? I found it very fast for a 2.1 ROM (some things like opening the SMS are faster on 2.3 ROMs) and almost 100% stable (Elegance 2.1 ROM had some problems with stability and force closing apps), and with Link2SD you have more than enough space for applications. Also, battery life is double the time on 2.2/2.3 (4-5 days for me, use it mostly for calls and some SMS, wifi 10mins a day).
I run it because of EAP protected wireless networks (2.2 and 2.3 ROMs have some problems with them) and after trying almost all ROMs, had it for the longest time on my phone.
EDIT:
DL for Recovery:
http://fileshare.in.ua/4169544
Thanks would try it if I could get it to download from the link
OK got it from Murz shared folder, Bluetooth works.
Will use this one while I wait for a 2.2 or 2.3 gets sorted
Thanks
I've never seen a dedicated thread on this but I've seen people make off-hand comments about this issue from time to time. I think it started happening in Tytung R9 and higher kernels.
I am using a BlueAnt T1 Bluetooth headset. It pairs just fine and I can use it generally without any issue.
The problem comes when I use voice dialing to initialize a call from the Bluetooth headset. It connects to the phone and I get the normal Android "Speak now...." I speak my command "Call <person> on <service>...." It states the command back like normal and then _as soon as_ it switches to the phone app (eg, com.android.phone process) it locks up the phone and the only way to recover is to pull the battery.
If, instead, I go to the phone app, find the person, and call them that way (even with Bluetooth paired) it _always_ works without any problems. This isn't a long-term solution for me because I need to use voice dialing when I'm in my car.
Now that GPS looks to be fixed and CLK data over PPP is much more stable, this Bluetooth issue is the last thing standing between me and treating the HD2 as my full-time native Android phone (currently I tinker on the HD2 but use my Nexus One as my daily driver).
I've tried multiple different ROMs, from HyperDroid-CM7, HyperDroid-GBX, Typhoon CM7, and Nexus-HD2-Gingerbread. They all have the same issue though Nexus-HD2 appears to be worse than the others (that is, the problem happens more often there).
I've used the infamous audio.conf update as well as the various no-wonk and libaudio patches and none of them help this issue.
Anyone else experienced this and have any feedback on how you overcame it?
I have the same kind of problem and tried a lot of different ROMs - not help.
I tried Blueant ST3, Motorola t305.
Phone book copied to blueant very well, but voice dial has same simptoms like yours - even if phone does't hang sound goes away from phone permanently(needs reboot). Is there any other ROM which works well with bluetooth hadsfree?
Any one?
P.S. Looks like it is real problem, but non of developers pay attention to it - they just don't have handsfree maybe
Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...
clio94 said:
Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...
Click to expand...
Click to collapse
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....
This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).
svet-am said:
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....
Click to expand...
Click to collapse
I think it is not the kernel, same kernel will crash in CM7 but no in CM6. I think the problem is related to the libaudio.so and other libs in system/lib.
robrob777 said:
This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).
Click to expand...
Click to collapse
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"
svet-am said:
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"
Click to expand...
Click to collapse
I'm using it as my daily driver (CM6), I came back just bc of the calling issues in Gingerbread.
the build that I'm using has not been updated since Jan 7, however I applied around 10+ patches and now it works as good as the new builds.
I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.
robrob777 said:
I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.
Click to expand...
Click to collapse
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.
i just verified the problem exists in MIUI as well. I tested MIUI since it's allegedly a "clean room" type of build environment.
svet-am said:
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.
Click to expand...
Click to collapse
Yes, I tested successfully in a Froyo based ROM.
I went back for a moment to CM7 and tested...sound couldn't return to the phone after calling with BT, also during the call I was not able to switch to speaker phone like I do in the froyo based ROM.
Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.
zcdg said:
Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.
Click to expand...
Click to collapse
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.
svet-am said:
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.
Click to expand...
Click to collapse
Yes you are right. It is just what Tytung said(i asked in his thread). Probably he meant GB for HD2....Soon or later they will figure it out i think...
For now will use Froyo 1.9G....
tytung said:
I don't have any Bluetooth headset.
AFAIK, some people have the sound issues, e.g. causing the phone app FC, since using Gingerbread 2.3.4.
But it doesn't affect all people, I don't know why.
No solution so far. To use Gingerbread 2.3.3 instead if you are one of them.
Click to expand...
Click to collapse
I finally found Tytung's exact quote as to why he won't look into the issue. It can be seen in context over here: http://forum.xda-developers.com/showthread.php?t=905060&page=524#
So, it might not be Froyo that's the fix but rather older versions of Gingerbread as well.
i have found a workaround fix for this bug.I tried it in tytung`s v2.9 rom and in dorimanx cm7 light rom with driztee v2 libaudio file.For bt voice commands i am using cyberon voice commander because google app doesnt support yet greek language
i connect my bt headset (motorola h300) and then i use super bt mono froyo free app https://market.android.com/details?id=com.steven.supermonofroyofree&feature=search_result to send audio to bt headset.
After pushing the bt headset button cyberon voice starts and i can give the command i want.After giving the command, audio goes back to the phone (you will hear a beep from phone speaker).The weird thing is that the audio is in extremely low level for hearing music but when you receive a call it is in normal level.
If i close super bt mono froyo app,audio returns to phone in normal level.
But if i accidentally (after i close the app) push the button for voice bt command,audio will disappear.
If the app is on and you receive a call,all audio will go again to bt headset and to return it to phone speaker after end call, i push bt headset,cyberon voice starts and i dont give any comand.After cyberon ends,audio goes back to phone with low level for media hearing.
Sure this isnt the perfect solution,but the important thing for me is that with this way,audio is not go away and i can give bt voice commands.
Also i tried bt mono app http://forum.xda-developers.com/showthread.php?t=950472 and it have a little different behaviour.I cant start from bt headset cyberon voice comander,but only from the phone and after giving a command,audio returns to bt headset if you have enable the setting "restart after call".So i think it maybe be helpful to people who want to have audio all time in a bt carkit.
Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.
zcdg said:
Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.
Click to expand...
Click to collapse
thanks for that follow-up and testing. I was wondering if whether or not it might be a "fault" in the VoiceDialer.apk or even in the Phone.apk. I have been using my Nexus One for daily stuff. I might try replacing VoiceDialer and/or Phone.apk in a newer ROM (eg AOSP 2.3.5 or so) with the old version and see if it works.
Ive wondered about this as it is to me the last issue I have with my HD2. Here is a search link for some entries in Tytungs rom & kernal thread...
http://forum.xda-developers.com/search.php?searchid=86308155
Also here is a comment from the man himself...
http://forum.xda-developers.com/showpost.php?p=15996942&postcount=5953
and here is a post in reply that talks about the same issue being replicated using Bluetooth...
http://forum.xda-developers.com/showpost.php?p=15997234&postcount=5956
Some more chat about the sound issues...
http://forum.xda-developers.com/showpost.php?p=16113973&postcount=6045
Another thread with logcats on it...
http://forum.xda-developers.com/showthread.php?t=1060486
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: