Related
Does anyone else have a problem with their Bluetooth and HTC touch? I have tried 2 motorola and a LG BT headset and no one can hear me, but I can hear them. I tried pairing and repairing. I deleted it and added it as a new device. I have even tried the BT with another phone and it works with that phone with no problems, so I know it's my phone. I even tried a hard reset. Does anyone have a solutoin to this problem? I have the latest ROM update from HTC's website for a Bell HTC touch. My motorola headset was working fine, but I think after the latest Bell ROM update it stopped. Does anyone else have this problem or can anyone suggest a solution? thanks. paul.
my jawbone did this but my plantanics 510 fine
My jawbone works fine but there's a problem using hands free connection with my '05 range rover. The phone and the truck connect but then the connection is dropped. My buddy has a motorola razor and his phone works great w/my truck. It appears to be my phone that's the problem. Any suggestions on this?
Thanks so much.
jarmijo said:
My jawbone works fine but there's a problem using hands free connection with my '05 range rover. The phone and the truck connect but then the connection is dropped. My buddy has a motorola razor and his phone works great w/my truck. It appears to be my phone that's the problem. Any suggestions on this?
Thanks so much.
Click to expand...
Click to collapse
This thread is 7 months old...
What ROM are you running?
I am running the NFSFAN 6.5 rom V11 and have he same issue with a motorola BT headset.
edit: i just noticed that the initial question was about a newer ROM update and bluetooth, but ill leave my initial reply here, cuz i often look for solution in old posts, so if this can help anybody :
NFSFAN 6.5 rom V11 and bluetooth
i dunno, but my bluetooth stuff somehow works with the 6.1 update, if you cant find any working solution within an hour, id suggest using a "well tried and tested" ROM version, like the 6.1
i stopped picking the "latest and greatest" in cars, devices, apps, or O.S. for the last two years, and been living a whole lot happier since.
about my 6.1 bell mobility ROM and bluetooth :
i like to tweak my weapons alot, my htc touch has a 6.1 ROM update, and i use bluetooth everyday, and it KINDA works well, enough for me anyway...
listening to mp3 and flv everyday on the transit,
then switching at work on the audio dongle adaptor on the pc,
using an pair of sonorix bsh-100 ( foldable stereo headset + optional plug-in mike)
to me the thruth is that bluetooth is a ****ty technology, i love it, and it's well taught,
but the developpers quickly code ****ty interfaces to it.
my settings all work from htc touch to dongle, but i often have to connect the touch to the headset like up to 3 times, where it tells me its connected, but isnt, when i hear the beep, it means it actually IS.
same at work, connect sometimes once, twice, even four, it eventually connects.
it's isnt button wear off or bad contact, its just the code is ****.
i rented a SUV that had bluetooth, tried connecting my phone, worked first time, a week later we rented the same SUV model, and for the whole trip i wasnt able to connect at all... back at the rental we tested the SUV with the clerck htc touch ( nice coincidence ) it worked right away.
i want to add here that whenever i try to connect through bluetooth, it usually works the first time.
my point is, bluetooth creators did a fine innovative job, but werent supported by developpers.
test your bluetooth phone alot with friends owning bluetooth accessories, youll detect behaviors after a while, and will learn to know its "demons" !
a bluetooth everyday user
V13 seemed to fix the issue
Just upgraded to V13, seems like BT works a lot better.
A bit on my history with BY, I just upgraded from a motorola V710, had a Moto Q for a few months too. Never had any issues with BT using the same Motorola BT earpiece, and varouis others through the last 5 years or so. Always worked like a champ, this was my first experience with BT issues.
I'm tryin to use my phone in my car using the build-in handsfree device (BMW 3-series). Sometimes it works but most times the car looses the pairing after a few minutes. After that the connection is only possible when I switch bt off and on again. But then again a pairing is not possible. I already used the phone with Android successfully in the car but only once or twice.
I used several sense-builds with a variety of different kernels such as mdjs and hastarin. I also changed the connection value in the bluetooth main.conf from 7 to 15 but without any success.
What can cause a problem like this where a connection is possible only for minutes but is working sometimes like expected?
Has anyone a similar problem with a Bluetooth headset?
Thanks for your help.
======================== SOLUTION ========================
Finally I found out, that it has nothing to do with radio ROMS, nothing with the WiMo-ROM nor with the Android itself. The failure lies in the sync between android and Outlook. One of my contacts included more then 80 telephonenumbers (3 particular numbers many times) what crashed the pairing between my car and the phone. I just deleted the contact and re-added it manually. Further I stopped the sync with Outlook and now only sync appointments of the calendar...
======================== SOLUTION ========================
Sent from my HTC HD2 using XDA App
Really no help for me...
I've got the Fiat Blue & Me system in by Abarth, it has similar problems to the one you're having in the BM, if I'm right in thinking that the Bluetooth stack is part of the radio ROM then trying a few different radio versions should help. I've found one that's fairly stable but still unpairs itself occationally. it's Leo_RADIO_2.15.50.14 running on mdee jay Evo Sense Evolution with hastarin's 8.1 kernel.
Updating the radio ROM didn't help. I could make one single call but after that it began losing pairing again. That's so sad because everything else is working pretty good so far.
Sent from my HTC HD2 using XDA App
I own a BMW 320d E90 and i have no problem with BT pairing.
I use the Androide 1.5 build done by Crazy_Cbr in htcmania.com (a spanish forum), with Radio 2.15 and Official Kernel #127.
Maybe your BT device needs a firmware update if your Serie 3 model is old. I have heard that you can update it in your BMW dealer, but not sure as far as i haven't needed to do it.
Greetings! (and sorry for my english)
Thank you... I have a 2010th E92 so I think the firmware is no problem. Furthermore the Version 1.5 is pretty old. I had this one with my G1 phone and was not very pleased. I also need Sense which is - afaik - not available for 1.5. Why do you not use a 2.x version?
Sent from my HTC HD2 using XDA App
This build is based in 2.2 but his name is "Androide 1.5", the point is that is a Senseless one...
Anyway i guess the problem is not in the build. Does BT work fine with WM?
Yes it worked pretty well with WM what brings me to the point isolating the problem on the hacked Android builds. Perhaps it'll work in the future.
@Nandeh: Which ROM Version do you use for your HD2 device (Radio ROM, WM-ROM and HSPL)???
Sent from my HTC HD2 using XDA App
I found out that the bluetooth pairing is stable as long as I don't have any phone numbers saved in my phone. Any ideas?
Any updates on this?
I have a 2005 1-series. First I was running WM 6.5 on my HD2 and never had problems connecting to the handsfree built in to the car. Then I installed tytungs NexusHD 2.9 NAND ROM (Android 2.3.5). After this, I can pair with the car, but the connection keeps dropping out and then reconnecting with some random intervals between maybe 3 seconds and half a minute.
I have tried to edit audio.conf and audio_pairing.conf, and also an earlier version of audio.so with no luck.
I really don't want to get a different ROM, as I really like the one from tytung.
(Link to tytungs ROM: http://forum.xda-developers.com/showthread.php?p=16555125#post16555125)
Hey All,
I have been scouring the web in hopes of answers and can find none. Evidently I'm not the only EVO owner in this boat either. I own a 2011 Ford Explorer with Sync & MyFord Touch (Fully updated). I pair the phone to the car it makes the connection fine. Begins the setup and sometimes will even connect and be recognized for a bit. But then the phone drops the bluetooth headset part of the connection. It appears (but I can't confirm) that Bluetooth streaming audio is still connected. There was a blissful 3 day window where it all just worked. Then it went to hell...... I saw one post where it said to switch the Bluetooth name back to "PC36100" and that didn't help. I saw another that said use a 4 digit pairing code and that didn't help either.
Its worth noting that I'm running Myn's Warm 2.2 rls5 with the stock & fully updated HTC kernel. So here's what I'm hoping to figure out:
*Have you had this issue with ANY car?
*Have you had this issue with Ford SYNC/MyFord Touch
*Aside from unpairing & repairing were you able to get around it?
*Is there a Kernel with a better bluetooth stack I should try?
Thanks for any help, many thanks will be given!
Unfortunately, the HTC bluetooth is totally worthless. I have a 2010 Ford Focus with Sync and it would connect and sometimes work for awhile, but people on the other line always complained of poor quality. And it wouldn't even connect all the time either. Lots of deleting and readding the phone.
Couple weeks ago I switch to CM7. Since CM has a bluetooth stack they built themselves and actually implemented correctly, I haven't had any problems pairing my phone. I can make calls, stream music, gps, etc and it is all fine. Always connects too. What is nice also is the audio will automatically stop if Google Navigation is giving directions or if someone calls. When I shut my car off and open the door, the audio stops and when I get back in it automatically starts again where it left off.
Basically if you want to use your Evo with a Ford Sync system, you'll need to run a version of CM.
Arg. I'm still waiting on my Explorer
On my 08 Explorer with Sync and Myn's RLS4, all is good. I turn BT off and make sure it is on before I turn the key. I stream audio constantly, and talk a bit. I literally just got around to putting on RLS5 today, haven't driven yet.
I partially agree with teamgreen02. It's HTC, not Ford. Does texting work with CM7? That would push me over the edge (or Explorer, pun intended)
It seems that there are a bunch of phones that have issues maintaining connectivity with the latest Sync system. I had to re-pair a BlackBerry to an '11 Explorer this afternoon. There is a backwards pairing procedure that may help rectify your issue. If you try searching for your phone from the vehicle instead of searching for sync from your phone, it has, in my experience, minimised connection drops, especially on the latest versions of Sync...
Btw, I am like the only tech at my dealership who really understands how to even pair phones to Sync, let alone diagnose the concerns our customers have described. There is also a system compatibility chart that we reference to determine if a particular device has been tested and verified to work with certain features of Sync. Last I checked (the October 2010 update) the Evo still wasn't certified compatible/tested...
Sent from my PC36100 using XDA App
Does anyone have any updates on this? My wife's Sync is working fine with her Evo but the sound quality sucks when she calls. Her phone isn't rooted.
I did update the Sync software from v1 to 1.1 (She has a 2008 Ford Edge Limited) but need to do further updates to the system since there are updates available.
Here is my experience/.02.
My wife drives a 2011 Ford Edge with sync....she has a stock Evo4g. When she bought the car 2 months ago, bluetooth seemed to work fine...now she is having the exact same issues everyone else is having. The bluetooth connects/disconnects and just plain doesn't work. I attempted to fix it and.....no. If i unpair from both the car/phone then retry to connect them, it connects for a second and when it tries to send the phonebook from the phone to the car, the connection dies. The phone still displays that bluetooth audio (not phone) is connected.
I then tried my Evo 4g (CM7) on her car...no problems whatsoever. Sync'd and connected fine...phonebook transferred over in about 5 seconds and everything worked great.
To note, my Evo 4g also works perfectly on my 2011 Infiniti G37...
So I think my example further proves that HTC's bluetooth software is likely the causative agent and is likely junk....root or die i guess =p
hope this helps someone
I rooted and installed MIUI and dont have any problems yet with sync.
Although,
I was looking looking to pull the bluetooth stack of the droid X which has the MAP bluetooth profile, that will allow ford sync to read and write text messages for you.
any ideas on how to do this? Or where to find in in the droid X?
2010 Ford Focus here, works fine for me. Using Fresh 3.5.1.
The bluetooth stack should all be dependent on what kernel you are using on your rom, so if you already have it rooted, try to change kernels and see how it improves...
as far as the MAP profile, i found this thread in the Q&A section, and it also recommends pulling the MAP profile (for text messessaging) from the motorola droid kernels.
I wish i knew how to do this.
I was hoping for someone to be able to do this for us
EDIT: I also found this thread:
http://forum.xda-developers.com/showthread.php?t=741332
its trying to get the MAP profile into the nexus one...
they found the new bluez stack had the MAP profile included:
http://code.google.com/p/google-summer-of-code-2010-bluez/updates/list
I have not used sync in a long time in my 2010 escape, but I'm wondering if the text message function works as well. Any word on this?
Sent from my PC36100 using XDA Premium App
lawmangrant said:
I have not used sync in a long time in my 2010 escape, but I'm wondering if the text message function works as well. Any word on this?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
No, the text messaging does not work for the unrooted Evo and it doesn't work for a rooted Evo under Myn's Warm TwoPointTwo RL5.
I Just had a 2011 Explorer limited for the past week as a rental and it worked fine for me (music & calls). I know this does not help much hope you get it going.
i had my EVO running fresh 3.5 and worked great in my Escape, i just switched to twopointtwo ROM and now here i am looking for a solution, not sure if its the rom or the kernel since i switched both..
alexdogg said:
i had my EVO running fresh 3.5 and worked great in my Escape, i just switched to twopointtwo ROM and now here i am looking for a solution, not sure if its the rom or the kernel since i switched both..
Click to expand...
Click to collapse
got it working for a day but its disconnected again, im going to explain what i did hoping someone with more knowledge can help us SYNC users to connect bluetooth
used fresh EVO 3.5 for a while and worked great, then i got bored and changed rom to myn's warm 2.2 with the kernel included and bluetooth started disconnecting after 30 seconds or so...
i tried
ms79723's SBC for Netarchy's CFS More Aggressive 4.1.9.1 Kernel (v7)
Ziggy471 Warm TwoPointTwo RLS4 Kernel
they didnt work either... so heres the funny thing..
i wiped and reflashed a fresh version of the same rom (Myn´s warm 2.2), this time i didnt restore anything, no apps, no contacts, anything, left it clean.. then i paired it up and voila.. it worked for a long time in my ESCAPE, so i thought it was working and restored all my apps and data.. and to my frustration... its disconnecting again.
so does this have to do with the kernel or with some apps or what.
has anyone figured out how to get sync working with blue tooth messaging.
marcw2 said:
has anyone figured out how to get sync working with blue tooth messaging.
Click to expand...
Click to collapse
I don't think the android kernels have the message access protocol that is needed for this to work.
Sent from my HTC Evo 4G
2010 Ford Focus. Bluetooth sucked with stock ROM and warm, dropped connection all the time. Works great with CM7. Definitely an issue on the phone side and not the car in my case.
I am also wondering if we can somehow get the text messaging working. I don't think its officially supported on any Sprint phones.
2010 Moutaineer here - never had a problem with Bluetooth on rooted stock EVO ROM.
Listen to music all the time - even the "call-transfer" functionality works fine when I enter the vehicle while talking on the phone.
Only thing is - I wish the damned thing would auto-synch for media-audio on Aux1 instead of me having to select the source all the time - anyone know how to do this?
2010 Lincoln with mytouch/sync and rooted with stock rom. No problems at all. Sometimes it gets a little static sound but I just turn my Bluetooth off then back on.
Sent from my PC36100 using XDA App
Think the problem lies with the Sense BT stack.
Hi guys,
I have a very strange problem with my beloved note. After I get in the car and drive off I remember that I have to turn bluetooth on so it can connect to the hands free system. The thing is that it doesn't connect automatically, I have to go into the settings and tap the BT name in order to connect it. If on the other hand if I have BT already enabled on the phone before starting the car, it conmects automatically. With the first version of GB the Note had in November I didn't have this issue, but after the first update it started not to work. Now I am on official unrooted ICS 4.0.3. Never had this problem with any other phone.... Any help would be highly appreciated.
Thanks.
Sent from my GT-N7000 using XDA
Anyone?
Sent from my GT-N7000 using XDA
n.vasiliu said:
Hi guys,
I have a very strange problem with my beloved note. After I get in the car and drive off I remember that I have to turn bluetooth on so it can connect to the hands free system. The thing is that it doesn't connect automatically, I have to go into the settings and tap the BT name in order to connect it. If on the other hand if I have BT already enabled on the phone before starting the car, it conmects automatically. With the first version of GB the Note had in November I didn't have this issue, but after the first update it started not to work. Now I am on official unrooted ICS 4.0.3. Never had this problem with any other phone.... Any help would be highly appreciated.
Click to expand...
Click to collapse
You can try Automatic Bluetooth Toggle PRO (I think there is trial version on Google Play). I don't know if it will help you. If not then I'm sorry you will probably have to go back to GB. I'm still on GB as I was also having issues with bluetooth on stock ICS (CM9-based ROMs worked well though).
Thanks a lot. GB had the same annoying problem though :-(... so it's not that....
Sent from my GT-N7000 using xda app-developers app
Hi,
Did you allow the pairing automatically between the devices?
When you pair at installation, it isn't permanently (= automatic) yet. When you get in your car and pair for a second time, normally your phone asks you if you allow your hands free system to access your phone; at that moment you have to tick "don't ask me again" and "yes" for automatic paring.
You might want to disassociate the two and try a new setup (pairing).
To disassociate, stop the system in your car (that cuts the BT connection between the two), disassociate on the phone (push and hold your hands free system in the BT section of the phone and chose disassociate), reboot your phone (so it forgets your cars BT system) and start pairing all over again.
I would provoke the second connection so you get the "automatic" question to make it work.
Good luck :good:
I have the same problem with the original ICS rom.
Flashing a custom ICS rom fixes this problem.
I tried kingdroid (worked ok)
I tried Cyanogen (phone ok, no media audio over BT but connection OK).
I had a similar problem after upgrade with stock ICS through software update. I couldn't pair Note with Mercedes bluetooth. Galaxy Note recognized Mercedes BT & vice versa, but connection was impossible. I read every forum on internet but no help. Everybody was blaming Samsung and ICS. Some suggested resseting Note to factory default, others downloading bluetooth app etc.
Until...I finally figured out that something was confusing my car's BT, so I resseted car system, and the problem was solved.
Sent from my GT-N7000 using xda app-developers app
These is a twist with "old" BT systems and ICS: Old BT systems want you to insert a pin code, ICS wants you to to confirm a code that the BT system sends and that ICS shows on the screen.
It's obvious that that ICS on an old system can be a hassle.
A work around is to put the car in discover mode (so it shows the pin code) and then send a contact (or a picture) from the phone to the car system. As the car replies, your phone will show the possibility to insert the PIN Code.
After that your system should work.
At second connection make the pairing automatic (as I described above) and you're happy.
(This is not my discovery, I found this solution on the SE XPeria Ray forum as I had problems with my wifes phone )
Thaks a lot. I will try as soon as I get the chance and will let you guys know.
Sent from my GT-N7000 using xda app-developers app
So with the workaround mentioned above - it doesn't work. When turning on bt on the phone it won't automatically connect to the car.
Sent from my GT-N7000 using xda app-developers app
Try A2DP Volume on the market.
I have the same problem as you. I used a leaked ics rom on my galaxy s2 and also had the same problem we now have on our ics galaxy notes. My car's head unit is a 3 year old eclipse cd5030. For the last month ive just been manually pairing it every time. PITA. Ill try the workaround suggested earlier in this thread and let you know. Otherwise i think cyanogen mod rom may work.
Sent from my GT-N7000 using Tapatalk 2
Let me know. I am.not going through the trouble of putting anoyher ROM on the phone.just for that
Sent from my GT-N7000 using xda app-developers app
n.vasiliu said:
Let me know. I am.not going through the trouble of putting anoyher ROM on the phone.just for that
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I had similar issues with Parrot 9200 kit in my car. Paired automatically under GB but on stock ICS wouldn't pair unprompted. Sometimes it would but only after minutes.
I'm on Paranoid Android 0.4 now which is CM9 based. It's better but often still slow to pair unprompted. Main improvement for me is that the phone doesn't carry on playing music through its own speaker, like it did on stock ICS, when I turn off the engine.
There is an app on the market called "Auto Connect 2.0", but it is only available for ICS and above Android versions
atiesfo the
i have same problem with my note, but with my Galaxy S1 works fine, when i upgrade the android to 4.0.4 solves the problem.
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: