[Q]Best JB Rom with working BT? (or alternative CM9) - TouchPad Q&A, Help & Troubleshooting

Hey guys, ive been running CM9 on my touchpad for ages but want to move to a JB rom. Im going to be using my Touchpad as a media device for outdoor speakers i have in my patio so i can walk around and change music as need be (instead of having to go inside where the receiver is to change music then go back outside). I was looking for improved roms with better battery life maybe and especially working bluetooth with A2DP. Are there are any JB roms that fit the bill? Some googling turns up Jscullins roms, but i was reading he was only doing it as an experiment and figured his BT fixes would be included in more (and possibly better) roms. Something stable with decent battery life and working BT with A2DP is what im after. Any suggestions? Thanks folks.
also, if there is nothing that fits the bill what would be the best CM9 ROM that does? I have noticed that my current CM9 build has an annoying issue with the touchscreen where if im scrolling around and let go, sometimes it registers that as a tap/click. My girlfriend hates it. A smooth CM9 build with good battery life, good working A2DP BT for music streaming, touch issues fixed (which i heard of for CM9 builds so thats why i mention it), and stable would be awesome.

Well I am running JC Sullins 0808 CM10.1 (4.2.2) ROM, and this is working well with BT keyboard and mouse. I did sync it to the car for BT Audio and that worked fine on the 5-10 minutes I used it, not tested audio over BT for any longer than that.
Generally the ROM has been stable, and am happy with it. I hope his fixes make it back into the dailies/weeklies, but we'll see, been a while now.
I did a complete wipe and start again on the device to get it working, and so far very happy with 10.1. I also am starting to use BT Audio more and more, so BT is important to me.

Related

Bluetooth curiosities?

I didn't want to bog down any of the various ROM threads with this, but I've noticed some odd behavior when pairing my D4 to my JVC head unit.
With stock Moto ICS and Eclipse 1.3.2 (still ICS), when paired to the HU, I can voice dial and control Pandora. I can sort-of control Google Music, but it won't display the ID3 tag info for any of the music, and although I can skip tracks it never recognizes anything but the player being stopped.
Now, if I go to Hashcode's WIP unofficial CM10 port, the HU control of GMusic works completely (as does all the Pandora control). I get ID3 tags, it recognizes when the player is stopped, playing, paused, etc. Of course, the current state of the CM10 port has the same BT issues with the phone side of things that the D3 had early in its development.
So now I'm wondering why there's the difference with the GMusic control/ID3 info. Does anyone know if it's something in the ICS/JB framework, or is it something related to the BT stack? Or perhaps something else entirely?
edit: So it turns out stock ROMs from pretty much every manufacturer (maybe all of them) do not support AVRCP 1.3+, but CyanogenMod does. I'm currently loading Hashcode's stock CM9 to see how it fares.
edit 2: Apparently CM9 has the same BT phone issues as CM10, I hadn't realized that. I guess I'm stuck with stock/Eclipse with no tag info until CM10 matures a bit more.
It is amazing just how many problems that this Droid 4 has when it comes to Bluetooth, and everything else. I don't understand how they could release these phones with so many issues. I see it more of a false advertising deal that just goes unchecked. I have major issues with bluetooth, if I get call waiting it resets my bluetooth connection (to where I hear my BT headset replay its boot up music). Half the time I have to pair the headset, then turn off the BT section and then turn it on again just for it to work. I am also constantly repairing the headsets as well. My two motorcycle headsets also also not happy and do not play well with the Droid 4. These headsets all seem to work fine with my older phones, T-Mobile G1, G2, G2x, and my Acer Iconia A500 tablet as well.
Here are my Headsets:
Jawbone Icon(Current Edition sold at Costco)
Parrot SK4000
Cardo Scala Rider FM
Not sure if my list helps any with research going forward, but it is something.
Tom
Yeah, BT performance is all over the place between Moto-stock, stock-ish Eclipse/mybearfish, and CM9/10.
I noticed while driving around today that in addition to everything I mentioned already, Moto-stock will tell the head unit when I get a text message, but stock-ish Eclipse/mybearfish doesn't. IIRC CM10 wouldn't do it either, but that's not all that surprising given its alpha state now.
I'm at a point now where I might finally be willing to give up the HW keyboard and just get a GNex in a month or two after Google announces whatever the hell is going on with the next Nexus phone(s).
Eh, BT works flawlessly for me. If you aren't stock, you shouldn't complain about BT because it probably isn't Motorola's fault.
If you are stock, that try a factory reset (sorry ), and if it still doesn't work, get a replacement 'cause your stuff is broken (just make sure it isn't your headset first!)
Except it doesn't work "flawlessly" because Motorola didn't put in support for anything newer than AVRCP 1.0. No amount of resets and replacements will change that.
I've only rooted, so it is not that big of a deal. Still is it that hard to upgrade that bluetooth section to something newer? This was supposed to be their latest hardware keyboard phone.
Sent from my DROID4 using xda app-developers app

Bluetooth problem with Cyanogenmod 10.1

I was just wondering if anyone else was having problems with a bluetooth headset using Cyanogenmod 10.1? The call quality while using the handset is great, but when I use my bluetooth (Jawbone Era, Motorola Sliver Elite) the call quality is absolutely terrible, the person can't even hear what I'm saying.
I say Cyanogenmod because that's my favorite rom, but it also happens on AOKP, PAC, ParanoidAndroid, and pretty much every other Vanilla type Rom.
Any help or suggestions?
The same problem with Jawbone Era. All works fine in Samsung stock 4.1.2 ROM.
Yep. I have this problem, too.
Bummer, as I'm writing a Bluetooth headphone round-up for a magazine this month, and I can't review call quality without borrowing a friend's phone.
Known Issue
Hey guys the bluetooth isssue your speaking of is a VERY well known issue in CM its one of the few bugs that is still being ironed out. Its also present in basically every other aosp type rom because they are all based on CM. The awesome cyanogen devs are working on it constantly and im sure they will get it figured out :good:
So if you here any reference of an "upstream" issue in a ROM thread its most likely referring to it being an issue in CM and therefore the ROM in question. :good:
Bluetooth car connections drops and really bad audio quality when on call.
FanDroid09 said:
Hey guys the bluetooth isssue your speaking of is a VERY well known issue in CM its one of the few bugs that is still being ironed out. Its also present in basically every other aosp type rom because they are all based on CM. The awesome cyanogen devs are working on it constantly and im sure they will get it figured out :good:
So if you here any reference of an "upstream" issue in a ROM thread its most likely referring to it being an issue in CM and therefore the ROM in question. :good:
Click to expand...
Click to collapse
Hi everyone, I have used PARANOIDANDROID in the past for Samsung Note and had a great experience using it. Just installed the PARANOIDANDROID on my new HTC one.
I am having two issues that are forcing me to go back to a stock rom,.
1st) Bluetooth connection with car, when calling the audio quality is really bad. The person on the other end cannot understand what I am saying.
2nd) when on a call with a headphone /w mic and connected to my Mac, the mass storage keeps going on and off. This affects the audio quality of the phone call.
All other issues that have been reported here I am OK to way for, but the BlueTooth issue forced me to look for a stock ROM for now.
I hope the great the people working on these Rom ( Paranoidandroid and Cyanogenmod ) can fix these issues quickly.
no bluetooth for voip apps
I've tested CM on note I and II, the same issue shows up, I cannot use bluetooth with voip apps. Same goes for 10.2. Too bad

[Q] cm 10.1 rom w/ most working features?

hi:
im about to trade in my cm 9 for cm10.1.. mainly for the sake of bluetooth support..
ie.. bluetooth earphones, keyboard, mouse , tethering might be handy at some point.. how many pairings at one time is the max?
i dont really go in for flashing daily..
so i would like to know what the most stable and feature rich rom is usable..
it seems that "Jcsullins Full CM10.1 Bluetooth Build [20131210] based on Milaqs Nightly builds" would be best for me.
any opinions/ user experience/ advise, etc would be greatly appreciated.
thanx
Works great for me
amkaos said:
hi:
im about to trade in my cm 9 for cm10.1.. mainly for the sake of bluetooth support..
ie.. bluetooth earphones, keyboard, mouse , tethering might be handy at some point.. how many pairings at one time is the max?
i dont really go in for flashing daily..
so i would like to know what the most stable and feature rich rom is usable..
it seems that "Jcsullins Full CM10.1 Bluetooth Build [20131210] based on Milaqs Nightly builds" would be best for me.
any opinions/ user experience/ advise, etc would be greatly appreciated.
thanx
Click to expand...
Click to collapse
I flashed 20131210 yesterday and it works fine. Bluetooth seems solid but I haven't tried tethering. It is fast and smooth, battery use seems about the same as every ROM I've used.

[Q] cm11 tenderloin KitKat now 4.4.2 ?

Does the 12-12-13 update include kernel changes which are suppose to repair black box issue in default browser api ?
UPDATE: Forgive my ignorance. I now see the commits included in Milaq's CM11 KK 4.4.2 update for the TouchPad (tenderloin). And understand the devs are still working updating 3.6 kernel. So will need to live with the Kernel 2.6.35 for a while longer. But until then apps utilizing default browser api are problematic. At least Chrome and Firefox are working.
I'm running Milaq's 4.4 ROM also. Happy to run with it for now even with "black box" issues, is running incredible smooth so far. Using shortcuts to Chrome bookmarks is my workaround for Gmail etc just now, although same issue in the BBC news app (and others I'm sure
I don't have enough posts to post or reply in development forum so posting here.
On the CM11 dev thread a couple posts about audio issues. I've flashed the 12/10, 12/12 & 12/14 CM11 nightlies and have not observed/heard audio issues.
And BT and WiFi are working ok. And file transfer via USB and BT ok (although BT transfer appears slower from what I recall in CM7/CM9 or WebOS).
Haven't yet figured out how to get BT streaming (from a Windows PC) to work.
If I could get my Plantronics Backbeat 9033+ BT headset to charge correctly, I could test those with CM11 (previously I the BT headset working well in CM9 as well as WebOS). Wish I never bought this particular headset, as they hurt my ears, no matter which eartips I use. And now will not charge. (I only used a few times since purchasing late last spring). Need to look up my warranty. Sorry I digress OT.
woodytrain said:
And BT and WiFi are working ok. And file transfer via USB and BT ok (although BT transfer appears slower from what I recall in CM7/CM9 or WebOS). Haven't yet figured out how to get BT streaming (from a Windows PC) to work.
If I could get my Plantronics Backbeat 903+ BT headset to charge correctly, I could test those with CM11 (previously I the BT headset working well in CM9 as well as WebOS). Wish I never bought this particular headset, as they hurt my ears, no matter which eartips I use. And now will not charge. (I only used a few times since purchasing late last spring). Need to look up my warranty. Sorry I digress OT.
Click to expand...
Click to collapse
When I stated BT was working ok, I was referring to paring the TouchPad with an HP TouchPAd Wireless Keyboard as well with a WIndows XP PC.
I was able to get the BT headset working with my WIndows PC (it was charging ok...issue was operator error). And when I search for BT devices on the TouchPad CM11) my headset displays in the device found list. But when attempting to pair the CM11 Touchpad with the headset, Bluetooth on the TouchPad turns off, and then within a few seconds BT turns back on.
Anyone able to get a BT headset working with CM11...yet?
I probably should just sit back a bit and wait for the updated kernel.

Bluetooth issues on CM based roms, but not stocked based. (VS980)

Hi everyone, thanks for taking the time to look at this.
I'm having an issue where if I run any CM based rom I get "com.bluetooth.android has stopped responding" when connecting to my Mazda car stereo or my jawbone speakers. I've had this issue on every version of CM that has been out since November. If I use a stock based rom, everything works fine and I don't have any issues. It doesn't matter if I'm using 4.4.2 or 4.4.4, the previous scenario still holds true.
Any ideas what I can try in order to solve the issue or at least narrow it down further?
I really like flashing different roms and checking out the awesome features everyone has added, but I unfortunately need my bluetooth to work properly.
Thanks in advance for all the help!
nuggetfn22004 said:
Hi everyone, thanks for taking the time to look at this.
I'm having an issue where if I run any CM based rom I get "com.bluetooth.android has stopped responding" when connecting to my Mazda car stereo or my jawbone speakers. I've had this issue on every version of CM that has been out since November. If I use a stock based rom, everything works fine and I don't have any issues. It doesn't matter if I'm using 4.4.2 or 4.4.4, the previous scenario still holds true.
Any ideas what I can try in order to solve the issue or at least narrow it down further?
I really like flashing different roms and checking out the awesome features everyone has added, but I unfortunately need my bluetooth to work properly.
Thanks in advance for all the help!
Click to expand...
Click to collapse
Ha. I have the exact opposite problem. I have a 2013 Subaru Outback and every AOSP rom works perfectly and any stock rom has issues. Calls work fine on both stock and AOSP based roms, but media playback has always presented a problem for me on stock roms. On AOSP roms I can play Netflix, Youtube, music, etc through my car speakers but I can only get Play Music to work on stock roms. Sometimes on a stock rom, Youtube will play for 2 seconds but then cutoff the audio. The video will continue to play, but the audio is lost. Very strange.
I've searched around a bunch, and it looks like i's not an uncommon issue, but it doesn't look like there's a systematic solution. I assume there are too many variables (car makes, models, years, stereo upgrades, Nav options, etc) to be able to isolate an issue. You just have to keep trying different iterations.
Keep me posted if you find a solution.

Categories

Resources