I have an HP x4000b bluetooth mouse that works fine on stock and blur roms. cm11 and aokp roms dont work. same result with both is it attempts to pair and seems to pair successfully but never goes to a connected state. more than happy to help with dumps and testing and such. can someone lead me in the right direction?
Related
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
Since I am no longer using my P990 as a smartphone I am thinking of using it as a "mini HTPC" on my TV. I tried several ROMs and different things to get the most of it but I have a huge problem with my bluetooth mouse and keyboard.
On Gingerbread and (the new v30a) ICS I can pair the devices but I wont see a mouse pointer and the phone will simply not react to inputs I do with my mouse and keyboard.
On JB CM10 I can pair the devices and also see a pointer. Both mouse and keyboard work perfect the way I want them to but the main problem I have with CM10 is the HDMI landscape problem.
It´s quite cool to get bluetooth with my devices working but it´s also pretty useless if the TV output is rotated 90 degrees.
Is there any way I can get my devices working with the original ICS? Is bluetooth a kernel problem or can´t this be fixed easily?
I also searched for the CM10 HDMI out problem and possible fixes but couldn´t find anything. If there is something out there, please let me know.
Thanks a lot!
So I did some more tests yesterday and it seems that bluetooth is not kernel related. Are there any hacks/tools/apps to support more input devices on ICS?
Hi guys!
I have a problem with my Trust bluetooth mouse.
It connects to the phone (shows "connected" on bluetooth device list on the phone) but it doesn't work. No pointer no working buttons.
On Galaxy Note 2 it works fine.
Any idea?
Thanks!
New firmware arrived but bluetooth mouse still not working
We are on firmware 4.2.2 but things are going worse.
Now the mouse cannot pair at all. (Before it paired, connected but nothing happened)
Fu**ing bug!!
IT'S WORKING!!!!
Waited so much but with this last update (4.3) everything works.
Now we can use it like a small laptop!
Enjoy!
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.
Sorry if this question has been asked before but I did some searching and was unable to find a straight answer anywhere and my question is a bit different.
Is there any hope for getting the Sixaxis PS3 Controller app working properly on any of the Android builds for the Touchpad. CM9 is the only thing it worked on as far as I can tell.
CM 10.1, 10.2, 11, as well as the offshoots, none of them connect to the controller. They connect to other bluetooth things I've tried, like keyboards and speakers, but no PS3 controller. Any other controllers work that I'm not aware of?
I've heard people saying something along the lines of there being an issue with the bluetooth stack on the newer ROMs, or that it is just a problem with the newer Androids in general. Though my phone, Galaxy S4, is running a 4.4.4 Slimkat build, with the 3.4 kernel, and it connects to the controller no problem.
I greatly appreciate all the Touchpad developers and all you guys have done to keep this thing alive, it's simply amazing. I'm just wondering if any of you have any idea as to why this aspect doesn't work and if it is even feasible to get it working? As it's a large factor in determining what ROM I will run on my Touchpad. I have no problem staying on CM9 if that's what it comes down to, but if we could somehow get it working on KitKat or Lollipop, that would be fantastic.
I'm willing to do whatever to help if someone is able to help me. I'm no developer but I'm very comfortable with a computer and with flashing ROMs and whatnot, as well as troubleshooting issues, so I'd be able to test some things out, take some logs of things, in order to help someone more literate in the development side of things see what is going on and where the problem may lie. I'm sure I'm not the only one wishing this would work, and I'll help to get it working in any way I can.
Thanks in advance, guys.
DBak451 said:
Sorry if this question has been asked before but I did some searching and was unable to find a straight answer anywhere and my question is a bit different.
Is there any hope for getting the Sixaxis PS3 Controller app working properly on any of the Android builds for the Touchpad. CM9 is the only thing it worked on as far as I can tell.
CM 10.1, 10.2, 11, as well as the offshoots, none of them connect to the controller. They connect to other bluetooth things I've tried, like keyboards and speakers, but no PS3 controller. Any other controllers work that I'm not aware of?
I've heard people saying something along the lines of there being an issue with the bluetooth stack on the newer ROMs, or that it is just a problem with the newer Androids in general. Though my phone, Galaxy S4, is running a 4.4.4 Slimkat build, with the 3.4 kernel, and it connects to the controller no problem.
I greatly appreciate all the Touchpad developers and all you guys have done to keep this thing alive, it's simply amazing. I'm just wondering if any of you have any idea as to why this aspect doesn't work and if it is even feasible to get it working? As it's a large factor in determining what ROM I will run on my Touchpad. I have no problem staying on CM9 if that's what it comes down to, but if we could somehow get it working on KitKat or Lollipop, that would be fantastic.
I'm willing to do whatever to help if someone is able to help me. I'm no developer but I'm very comfortable with a computer and with flashing ROMs and whatnot, as well as troubleshooting issues, so I'd be able to test some things out, take some logs of things, in order to help someone more literate in the development side of things see what is going on and where the problem may lie. I'm sure I'm not the only one wishing this would work, and I'll help to get it working in any way I can.
Thanks in advance, guys.
Click to expand...
Click to collapse
I've got it to work, will try it on lollipop.