Hi all,
Have been using my Jawbone UP on stock and custom rom's like Monx with the Xperia Z1 for some time now but as of recent I switched to an AOSP type rom, primarily Carbon ROM (great ROM) but the UP isn't syncing nor is it being recognised, I use my UP all the time and would like to have both the ROM and the UP working together.
Has anyone had any issues with theirs or some knowledge which may help besides going back to stock.
Many thanks
FYI, i'm using the wired Jawbone UP not the wireless one.
Related
Anyone else have issues getting Bluetooth audio to work on this ROM? My device will pair just fine, but audio is not transmitted. I love the ROM and hate to switch back to a non-Sense one, but I really need the audio.
Lynne
That's an issue with all 2.2 sense roms, along with a broken camera and Mobile Network settings FCing. If you need bluetooth, you can't use sense on 2.2.
That's so sad! I've tried several ROMs over the last few years and some have great features, but I always miss the Sense UI. Currently, I had a number of issues flashing some of the 2.3 ROMs so I've put the rooted Sprint final release on my Hero. I guess I'll stay there for awhile and keep a lookout for new ROMS.
Lynne
lrandolph said:
Anyone else have issues getting Bluetooth audio to work on this ROM? My device will pair just fine, but audio is not transmitted. I love the ROM and hate to switch back to a non-Sense one, but I really need the audio.
Lynne
Click to expand...
Click to collapse
Sorry about Not Posting the Bluetooth Issue in my Thread...
Tell you the Truth I Don't use it so I wasn't even Aware it Didn't Work! Glad to hear you like the Rom tho, Hopefully Soon I'll have some Updates!
Sent from my Hero using XDA App
Hi all,
Got a really weird bug... was interested to see if anyone else has the problem. I've tried 4 different ROMS with very very very clean installs so I know it's common, but it's obviously rare as I'm not seeing it coming up here.
In short 4.1.2 - Slimbean, Asylum etc Bluetooth to my car for hands free calls works fine.
10.1 or 4.2.1 - Asylum, Revolt, Utacka Paranoid etc don't work with my car, but they do work with a headset..??? WTF..?
So I can hear the phone ring, then once the call comes in sound is not transmitted in either direction.
I'd appreciate any suggestions on things I can do to troubleshoot or fix the problem.
Matt
I have the same problem in my car. I can't hear the phone ringing or anyone else picking up on the other line. If I can't get this working soon I may have to go back to the stock ROM.
I've tried Paranoid Android, PACMAN and AOKP with the same issue on all three. Also I flashed the bootloader to the latest version of SuperSlim.
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
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.
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.