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.
Related
Hi Guys,
i have this problem for a long time and didn't find anything about it in web or in xda forums.
I have a HTC Dream + HBH-IS 800 Sony Ericsson Headset.
When i listen to music via A2DP the connection is not very stable...
the connection interrupts very often for about 2 or 3 seconds, then works for about 3 seconds.
This only happens when i am outside, not in buildings. I this the reason is because of interferences. The connection gets better when i move the G1 into a specific orientation (upper side up) and don't turn my head to the right
On my old Windows mobile phone i played around with bitpool (=ratio between quality and connection stability by constant bitrate) settings... is there a possibility to get the connection more stable, when playing around with this setting?!
How can this setting be changed on android?
Further information:
-ROM Cyanogen 4.2.5 but same problem on stock ROM
-HTC Dream has been replaced one by a new device -> same problem
-Headset was never exchanged, but worked perfectly on my old Touch Pro with WM 6.1
Thanks for your help
There is a known issue on the Bluetooth stack and is suppose to be fixed in the Elclair 2.0 fix, the temporary work around is to first pair and connect then disconnect and reconnect it again i'm having to do that several times a day when i use my RocketFish bluetooth stereo headset. Hope that helps
thanks for this workaround, will try it tomorrow and will post if it works for me too
hmm, didnt really work for me... no change after pairing disconnecting and connecting again.
i wonder why this only happens outside, not in buildings... another frequencys which interferences maybe?!
Be sure to disable wifi.
Not trying to hi-jack your thread. If you want me to open another i will. However this is a BT question as well.
my G1 is set to connect to my stereo in my car. Pioneer BT head unit. I find that i have to manually tell it to connect every time i get in the car. When i had a blackberry before it would just connect every time on its own without me doing anything once i made the initial connection.
Any ideas?
thanks.
Press1Now said:
There is a known issue on the Bluetooth stack and is suppose to be fixed in the Elclair 2.0 fix, the temporary work around is to first pair and connect then disconnect and reconnect it again i'm having to do that several times a day when i use my RocketFish bluetooth stereo headset. Hope that helps
Click to expand...
Click to collapse
Worked on Dell Streak A1.6
I have Dell BH200 headset as well, and I have the same exact problem its like the audio stutters but when I first connect it its more stutter than music so you can barely even understand the music until after 30secs when it starts to normal out.
ATM im runnning Stock 1.6 for G1, im going to try Cyanogenmod 6.0 tomorrow and see if anything changes.
but everyday I go back and forth with my laptop and phone since my headphones run for atleast 3-4 days.
wow, finally someone having the same problem.
and even the same description of the connection issues.
I recently bought a orange SanFran and, as the device is fairly cheap, a nokia bh-504 along with it.
The connection isnt stable even when I put it in my breast pocket.
As soon as I move my head to the right, the streaming stops. Completely.
I can easily stop the music when holding my hand in front of the right earpiece.
so i will try the disconnect / connect again "workaround", but I don't think that will help.
I paired the same headset with my gf's netbook and I could walk through the whole apartment and the signal was stable even through up to 4 walls.
so no one here knows how to tweak BT settings in android?
For some reason when my phone connects to a headset that supports both audio and phone the audio will not auto connect. I have to open the bluetooth options and hold down on the device i want to connect to then check the audio box.
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
It worked before fresh 1.1 so maybe it was just a change in something.
I'm using the stock software and I have the problem so it is not freshrom
man we need an update HTC!!!!!!!
q1 almost over so we're that much closer to getting our official 2.1 update.
I've also got a bluetooth problem - would really appreciate any help you can offer.
I have a Tomtom and headphoned in my Bike Crash Helmet. I want to connect so I can hear music and phone calls through the phone in my helmet and also hear the TomTom.
The Tomtom connects to the Helmet, the phone connects to the Tomtom and I can get calls through the speakers via the Tomtom but music won't play (apart from an annoying second or two after dropping a call).
If I can get the phone to advertise headset features I could connect the Tomtom to the phone and the phone to the speakers (think that would work), otherwise I believe the Tomtom is not advertising media audio, only phone audio and don't expect I can change that.
Any thoughts...?
PS - Have tried the market headset app - unfortunately it doesn't fix the problem...
Time_Lord said:
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
Click to expand...
Click to collapse
well now the source for the CDMA hero is out so shouldnt be long till a lot of the little bugs arre resolved.
I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea
Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane
My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.
Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...
Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.
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
Anyone else experience bluetooth connectivity issues on the new 4.2.2 firmware?
My car and BT headphones now take a lot longer to connect and disconnect to the phone compared to previous firmware.
In fact, the first time (after the update) i needed to manually connect to each deivce, almost like I had to remind the phone it was paired with them.
In comparison, my Nexus devices connect almost immediately on 4.2.2
Can anyone who is on 4.2.2 help test this?
Help confirm whether it is just me experiencing this or not. Thanks.
I have the same problem with my Mercedes BT System.
I connect my phone and lost my connection in 3-4min. After 10sec its connected again.
So my temporary work around was this:
1) Disconnect the Phone with my car
2) Clear Connetcion
3) Start new search and conntect the phone to BT
4) Didn´t allow the Mercedes BT to use my sms, contacts and so on.
With this it´s working if the BT System didn´t check my sms and contacts. But erverytime when I switch of the connection or car, I have to disallowed the BT System to check sms and contacts --- so this is only temporare and I hope for a better solution!
(Sry for my writen english - its bad )
My Bluetooth devices connected very quickly.
And no problems with sms and contact request?
Do you made a fullwipe?
My BMW simply won't pair with my XZ since updating to 4.2.2 - was working fine before on 4.1.2, but when I try to pair now, they recognise eachother, and I enter a code on the car to be verified on the phone, but after I enter the code on the phone, it all just freezes. The car sits there saying "Pairing...", but the phone thinks it's all been successful.
I have a bose audio system in my car, my XPERIA Z running PAC Rom - will pair, no audio or phone book exchange, My Dads Xperia z Works fine with stock rom. there is some issue I think with 4.2.2 maybe? I tried the Audio v19 and bluwtooth fix. NO LUCK!
Yes.. Having the same problem as well with Volvo's sensus multimedia system. It used to work fine.. Now it takes multiple tries to get it to connect since 4.2.2
I have the same problem.
I am having the same problem with the sbh25.
When i turn on the headphones my phone registers the pairing but no sound will be on. I have to manually turn the phone to speaker output then back to headphones for the music to stream through the bluetooth headset. This works first time 9/10 times. The other time i have to repeat the output step a couple of times for the music to be heard.
I had a couple of issues too with the latest 4.2.2. on my Kenwood system in the car.
This is terrible, clearly Sony did not thoroughly test the BT stack in this latest firmware.
I can honestly say, BT was pretty much working perfectly on 4.1.2 firmware. I may have to consider downgrading.
Thanks for everyones confirmation.