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.
Related
Which features of a ROM Kernel or Modem have the most influence on BT function. I recently purchased a Kenwood X994 for the car and the Captivate seems to have to be "connected" every time. Sometimes it loads the phone book, other times not. I have never been asked for a PIN code when pairing. Even after flashing a new ROM and reinitialization the Kenwood. It does work but even with th Gamin BT the connections were automatic.
I think the Developers might have an idea what influences the BT stack and if any ROM/Kernel/Modem is better in that regard.
If this post is in the wrong area please move it.
bump - I have the same concerns. Can't seem to find consistent bluetooth connection that was better than stock with lots of trying different roms with different modems and am totally confused on what directly affects the bluetooth connection
tbong777 said:
Which features of a ROM Kernel or Modem have the most influence on BT function. I recently purchased a Kenwood X994 for the car and the Captivate seems to have to be "connected" every time. Sometimes it loads the phone book, other times not. I have never been asked for a PIN code when pairing. Even after flashing a new ROM and reinitialization the Kenwood. It does work but even with th Gamin BT the connections were automatic.
I think the Developers might have an idea what influences the BT stack and if any ROM/Kernel/Modem is better in that regard.
If this post is in the wrong area please move it.
Click to expand...
Click to collapse
I am not trying to sell my ROM to you as I don't and am not here to make any money but I have not found a device that Phoenix Ultimate can not connect to. Just a thought for you.
Unless your making your own kernel thats special , their is some devices that it will have trouble connecting to, specifically certain car Bluetooth sets. this was a problem with every kernel I tried, and other users reported this also. I don't think it has anything to do at all with the Rom anyway,(it could, I didnt look into it too much), it think its an issue with kernels built from I9000 source.
adamholden85 said:
I am not trying to sell my ROM to you as I don't and am not here to make any money but I have not found a device that Phoenix Ultimate can not connect to. Just a thought for you.
Click to expand...
Click to collapse
Adam I have used (and am currenty trying out Phoenix Ultimate) and really find you ROMS useful, The BT works fine but the issue is I have to "connect" the phone even though it has been paired
The Kenwood X994 uses Parrot BT system which is supposed to be the best (which is why I chose the Kenwood LOL), I am just wondering why the device cannot auto connect when I get in the car as it did with the Garmin and the Honda. IS there a task I can set up using task manager?
Maybe its the Kenwood. But searches in that arena show no ill effect except with the Captivate and some Droids. IPhone is flawlwess with that system (wouldn't you know it) as are HTC phones it appears. I really hate having to select a phone based on BT in the car.
di11igaf said:
Unless your making your own kernel thats special , their is some devices that it will have trouble connecting to, specifically certain car Bluetooth sets. this was a problem with every kernel I tried, and other users reported this also. I don't think it has anything to do at all with the Rom anyway,(it could, I didnt look into it too much), it think its an issue with kernels built from I9000 source.
Click to expand...
Click to collapse
Which I thought as well so I flashed Cognition 4.2 and had the same issue...and decided to try Phoenix (GPS was terrible on Cog) Well I guess until I get another phone brand I will have to just make sure I connect the already paired devices. Although iPhone doesn't interest me...maybe HTC,
Moved as not android development
Hi all,
I know this is at the back of lots of gamers mind's who are using an i9000.
I am running a Darky Rom so I still get TV out - which is a big thing for me.
I got rid of my HD2 for this i9000 - and I still have not been able to connect a Wiimote to my device.
I was playing FPSCE with the wiimote on the HD2 and I really really miss this functionality.
I am aware that the bluetooth Kernal is the issue and that the Cynogen mod roms and others based around this are running a different BT imp which addresses and resolves this issue, but if I jump to Cynogen, I loose my TV out which is sadly more important (blame Ttorrent).
Has anyone heard of anything happening anywhere that will let me play with my wiimote whilst TvOUTed?
I am not holding my breath
Many thanks
Hi Guys....
I change my HTC Kaiser TYTN II to Android from Winmo rom cooked by shifu
suvil.com/products_freeaudiobt_en.html#product/gallery/free_audio_bt_2.jpg
My Bluetooth headset Suvil works fine to WinMO
Hard SPL 3.29
Radio 1.70.19.09
WinMO rom By shifu
Then i tried Android rom
Not so super froyo by kyle
fresh froyo by dark prince
I cant make my bluetooth headset media buttons to work
I tried to update the:
Hard SPL
3.34
3.56
Radio
1.71.09.01
1.65.21.18 downgrade
Kernels
L1q1d .32/.25
dzo .25
myns .32
still no luck! Cannot use the play/pause rewind/forward button functions
if i click the play/pause twice , it calls the last person on my log
Please help me Masters. TIA!
Thanks for letting me know that. Cheers!
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
n2rjt said:
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
Click to expand...
Click to collapse
As a diamond user, i hope you can fix the whole pack... Rhodium, Fuse, Diamond, and Topaz
n2rjt said:
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
Click to expand...
Click to collapse
OMG!!! Some Masters did reply to my post!...Hope im not too late for this!
I have a friend who is using Samsung I5510 built with Froyo 2.2.2
and media buttons on my headset works fine
Well the problem is dont know how to extract the driver or configuration of that ROM and install it to my kaiser. (i dont know as well if android works that way)
Just the forward/next Play/Pause buttons are not working, never mind the Volume control as Bluetooth headset has its own controller
Hope this helps and thanks in advance!!!
I'm looking for ROMs for the i9000 that have audio working when the phone is placed in the Docking Station. I'm stuck with Android 2.3.6 for so long it's really frustrating, but although I tried several ROMs there is always something not working.
Apparently I must be the only person who uses Audio Dock and TV Out 'cause every single "stable" ROM I tried didn't have this feature working and I use them daily.
It doesn't have to be the latest version of Android - I would just appreciate any links you can give me so I, and other people who use this feature often, have something to choose from. MIUI and others as well. Anything really. ANYTHING! :cyclops:
_LeCiel_ said:
I'm looking for ROMs for the i9000 that have audio working when the phone is placed in the Docking Station. I'm stuck with Android 2.3.6 for so long it's really frustrating, but although I tried several ROMs there is always something not working.
Apparently I must be the only person who uses Audio Dock and TV Out 'cause every single "stable" ROM I tried didn't have this feature working and I use them daily.
It doesn't have to be the latest version of Android - I would just appreciate any links you can give me so I, and other people who use this feature often, have something to choose from. MIUI and others as well. Anything really. ANYTHING! :cyclops:
Click to expand...
Click to collapse
Let me know, when you've find one. I have two desktop docks and I will be very happy, when the first (actual) ROM with working audio support is online ...
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.