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!!!
Related
hi,
I am driving a BMW series 1. I have an integrated hands free system in the car. I can connect the Touch Diamond with it. Even all the contacts can be shown and dialed with the multi functional buttons on the steering wheel and the radio. Here comes the issue:
During a call the BT connection aborts. Sometimes after 5 seconds, sometimes after 5 minutes. When TomTom Navigator is running it hardly ever worked. So my guess is, it is a performance issue and if TomTom is not running then it only aborts because the battery gets below 60% and perhaps some kind of powersave mode would be activated? I am using a cooked Rom based on the latest original HTC Rom. With the original ROM it was even worse. I hope a cooked ROM would solve the issue. Unfortunately not.
The technical support from HTC told me to ask my car manufacturer. They told me of course the opposite. After I told the HTC guy that it works fine sometimes and I guess it is because of the battery, he just told me to keep it loaded all the time. Quiet funny, but if the performance is the reason then it will never work with TomTom used at the same time.
So, does anyone has any good idea what I could do? Are there any patches available?
I would be really happy for any answer. thanks
Sascha
R 1.11.25.1
G 52.58.25.30H
D udk syrius topaz R3 based on 2.04.00.00
I had an issue with connecting my diamond to my X5. I fixed it by changing the bluetooth handsfree gateway dll from HTC custom dll to the Microsoft voicecommand dll. Not sure if it will address your issue, but it is worth a shot.
I posted it on ppcgeeks.com. (Sorry i dont have the link handy at the moment)
thanks a lot. i will try and post the results.
Okay I read, well skimmed the FAQ, thanks to the authors.
I am about to buy a used SPV M2000 ORANGE with sat nav software.
I already have an Orange pays as you go phone and am happy with Orange.
Is there any point in me upgrading the SPV to the latest ROM software etc. or is this really just for enthusiasts who want to tinker (nothing wrong with tinkering if that's your thing).
I really just need a decent phone, sat nav, (important) mp3 player. Dont watch utube or play games, take the odd photo.
Thanks for taking the time to read/reply.
hi and welcome to the forum.
interesting question you have there.
well, upgrading to the latest roms has pros and cons.
pro:
+ nice look
+ latest software can be installed
+ nice ui (many things are easier now)
+ finger friendly
+ new features like a2dp...
+ envy factor
+ stable
+ no loss of data if battery empty
con:
- not as fast as wm2003
- maybe not available in your native language.
- keeping up with latest builds and reading this forum can be addictive
if you hadn't had a blueangel before, you should definetely upgrade it, the minute you unwrap it. then you don't see the slight drop of speed and responsivity. also, while sat nav and mp3 are not even the tip of the iceberg of what the device is capable of, it seems, both those uses are for on the road, meaning you probably don't have time to fumble around with the stylus all the time (pro upgrading).
depending on what sat nav software you plan on using, you will most certainly be able to use a newer version with a newer operating system. bluetooth gps receivers are more compatible with wm6 than before, also the pairing and setting up is easier.
for mp3, im wm2003 you basicly have 2 options: the integrated windows media player (it sucks btw.) or TCPMP. in wm6 you can pick literally from hundreds, which one fits your needs best. S2P is nice for dashboard music playing, TCPMP is better for in pocket playing, because it can be operated using the side buttons. also, as mentioned before, the newer builds offer a2dp, bluetooth stereo output.
let me just describe a short situation here:
stereo bluetooth handsfree
phone (in my case it was the UNI)
bluetooth gps
the phone can connect to both bluetooth devices at once, you can listen to the sat nav commands through your handsfree, while, when it does not talk, listening to music, wireless and if a call comes in, you can still answer it.
this is only possible with a cooked rom, because of a2dp, extreme multitasking , new apps that wouldn't work with wm2003.
one last thing, if i'm getting that right, you are planning on upgrading once and staying with that os. while the newer builds are stable and fast, there is always room for improvements, the development never stops and so there will always be even newer builds coming out, that have more features, are easier to use, faster and have longer battery life. that's why i said this is addictive.
regards
Chef_Tony
Thanks, for reply, I will give upgrade a go.
Hopefully not too complex, I am used to flashing the rom on my satellite box, - easy.
Fingers crossed.
it's a little more complicated than that, especially when done for the first time. but all steps are logical and need to be done just once, then you are good to go, and every possible following upgrade will be a piece of cake, a few simple steps. have a look at the tutorial linked in my signature. it is constantly updated after user input and i believe that makes it pretty clear and understandable. also, you will find all the software needed for the procedure. if something is unclear, please report it to me and either i can add more instructions to the tutorial or explain, what it means.
From my opinion,its not good to go for old one.
i always prefer to buy a new one.
And for upgrade question,it is always possible to get it.
-------------------------
escorts toronto | toronto incall agency
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
I've had my captivate for quite some time now. After trying a few different roms I slowly gravitated towards Continuum. The fact it lets me use netflix, fully customize my look and feel built in, as well as having some of the most popular mods just seems like a win-win to me. It appears they still don't use the original bluez stack for bluetooth functions.
After doing some research, it appears that CM7 have changed the proprietary samsung blue tooth for the linux based bluez stack that allows wii remote pairing with the device.
Does anyone know if theres a kernal you could flash over continuum to be able to do just that? If not, what features might I lose if I were to switch to CM7. With so many nightly builds, its hard to keep up to date with CM7.
Any help on this subject would be greatly appreciated.
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