Related
having trouble getting my Pioneer AVIC D3 to connect with the bluetooth on my Tilt; the bluetooth audio works just fine, but i cannot make or recieve calls on the Navi system and its pissing me off. i already made sure the device is visible and bluetooth sharing is turned on (idk if i need it on but trying this anyways)
anyone else have a similar problem or a suggestion?
ugh, i want an AVIC so bad. but my truck is only 1.5 din. wold require a custom install
My silly thoughts:
1. Your Tilt doesn't need to be discoverable, you AVIC does.
2. If the AVIC doesn't show under settings-connections-bluetooth, then you haven't created a proper partnership.
3. If it does show there, then you should tap & hold that entry and see if you get "Set Headset" or "Set Handsfree". If you don't then the device isn't reporting a BT profile for phone use to the Tilt.
If you go through all of that and it doesn't work, I'd check with Pioneer for software/firmware upgrades for the AVIC. It may be an issue that they've fixed with updated code.
bump, tried the above with no luck. my sony S710a works fine and this is REALLY pissing me off; i spent almost $500 on the phone and another 1,000 on the damn navi system, if this doesnt work out soon im selling the Tilt and going back to the Sony
It is more of a problem with the pioneer unit rather then the phone. I have the tilt (flashed to htc) and have a problem of auto pairing. Everytime I get in the car I have to turn bluetooth off/on to get the deck (9800bt) to see the phone. This is something pioneer knows about a realesd a patch for the avic z2 (is that right) to fix the problem.
check this place out for more info (sorry don't have a direct link)
http://www.avic411.com/
blackcracker said:
It is more of a problem with the pioneer unit rather then the phone. I have the tilt (flashed to htc) and have a problem of auto pairing. Everytime I get in the car I have to turn bluetooth off/on to get the deck (9800bt) to see the phone. This is something pioneer knows about a realesd a patch for the avic z2 (is that right) to fix the problem.
check this place out for more info (sorry don't have a direct link)
http://www.avic411.com/
Click to expand...
Click to collapse
thanks im a member at avic411 as well as here and have had no success thus far; looks like SIM swapping with my Sony S710a is the best i can do. too bad because skipping songs or going thru my playlists via bluetooth is freakin sweet.
yah, i have the avic-d3 and the att/tilt, im so almost about to take the phone back. Even my crappy iphone paired withno issue. Please post if you figure it out.
Sad to see there has been no progress. I just got my new Kaiser, and I can only use it for bluetooth music and not as hands free with Avic D3. What a piss offf!!!!!!!!!!
I believe its a conflict with WM. I have the Pioneer 6800DVD and bt adapter and the same issue with my Treo 750 and Tilt.
I was able to get it to work on my treo using a bt program called jetware. I haven't tried it on my tilt yet. but it might work
I can confirm that the Jetware patch works great with my Tilt! You MUST uncheck bluetooth stereo (on your tilt) and only use the handsfree feature.
Hi, I'm pleased to say that setting up my TyTN II to sync via Bluetooth with my laptop running Vista's Windows Mobile Device Centre was a doddle. None of the nonsense I had before on WM5 and my Wizard.
However, it appears Bluetooth sync needs to be invoked manually each time from the TyTN. This makes this lovely feature next to useless.
With Nokia PC Sync for example, Bluetooth sync to a Nokia phone can happen whenever the phone comes back into range, or every 15 minutes if you so choose.
So, is there any way to specify this with Windows?
I don't think so at the moment. It's a problem within the Microsoft WM OS.
I too used to love my old Nokia 9100's capability to do this but with having so many connection variants on this unit (GPRS, WiFi and BT) Microsoft have probably opted for a safe solution.
At least with manual select, you wont have it running down your battery with lots of data traffic while its in your pocket/purse at home/work without you knowing!
Maybe we could pass this on to the Kaiser Tweak guys to see if it could be made selectable?
Worth a try!
Sure, can you do it?
Will have a go but my 'Street cred' is a little low here at the moment....
I hope one of the other patient dev guys may look at this and take it up???
your not alone
Check out these other threads. All describe different problems people are having (including mine - not being able to automatically re-pair with my car kit).
All seem to stem from the auto re-pair problem.
If a developer could help, that would be great.
http://forum.xda-developers.com/showthread.php?t=349841
http://forum.xda-developers.com/showthread.php?t=349050
http://forum.xda-developers.com/showthread.php?t=350046
http://forum.xda-developers.com/showthread.php?t=346970
http://forum.xda-developers.com/showthread.php?t=337575
No-one seems to have come to our aid with a new BT stack.
Reminds me very much of the early days of the hermes ... remember these days http://forum.xda-developers.com/showthread.php?t=285419
A
Many thanks.. I've looked at those and they are mostly concerned with BT connection to audio devices.. What we are looking for is an automatic polling of your device by Activesync over BT as PCsync used to do for the Nokia. The connection has to be initiated by the SW for it to work. Cheers anyway!
Sure, they are mainly about audio, however (at least in my case) the audio is perfect when its paired.
My main concern is exactly the auto polling. I can pair my device the first time to the car kit, but every time i get back into the car I have delete the pairing and pair it manually again. This is not how bluetooth should work.
I think this is very similar to the problem the author of this thread describes.
adamcullen said:
Sure, they are mainly about audio, however (at least in my case) the audio is perfect when its paired.
My main concern is exactly the auto polling. I can pair my device the first time to the car kit, but every time i get back into the car I have delete the pairing and pair it manually again. This is not how bluetooth should work.
I think this is very similar to the problem the author of this thread describes.
Click to expand...
Click to collapse
Yep, my BT audio is good and you never know, if we start looking at auto-polling of data/stereo devices we may cure a lot of problems on here..
Thing is we may have to go around the Activesync overide (which is the slowest block on this setup!) and use a priority connect to BT similar to WM5torage on usb!
What ya think XDA???
Yeah its one of the few things I miss about my Nokia 7710 was that i walked into my house and it would sync with my computer automatically. sigh
Its definately a WM/Activesync 'Non-feature' as when you first pair your device to an Activesync capable BT PC or laptop you get a pop-up message on the WM device reminding you to disconnect your BT Activesync link to avoid draining your battery!
Hi all,
I've just bought my first HTC unit ever (Kaiser), which is also my first Windows Mobile Phone (I used PocketPCs since 2001 but with no integrated phone so far), and it seems to have a lot of issues in the areas of "regular phone" functionality.
However, the one that is really freaking me out so far is the whole "Bluetooth audio" area. I'm just wondering whether I would ever be able to get what I want or am I asking too much.
I have 3 Bluetooth audio devices, all of them are dual Headset/Headphone ones: in-car fixed Motorola T605, Jabra BT8010 and Plantronics 590. Now, naturally, I want to use the T605 in the car, Jabra for phone calls only throughout the day and for music occasionally, and Plantronics when I'm in the gym, for both music and occasional incoming phone calls.
I had all this working flawlessly with my SonyEricsson K800i phone: each device connected to the phone automatically when powered up and automatically took over both Headset and Headphone functions. The only minor problem was reconnecting Jabra when stepping out of the car, which required only a short tap on the button.
Now, with Kaiser, things are much more complicated. When a device (any of them) is connected to the phone, both as Headset and Headphones, it works mostly OK, although sometimes there is a problem of sound not coming through the device when an incoming call was answered while playing music. The music is suspended OK, but the sound comes from the phone speaker instead of the respective Bluetooth device. This happens from time to time, not always.
But the biggest problem is the initial connection of a device after another one has already been connected. When I enter my car and fire up the engine, I want the T605 to automatically connect to the phone even if Jabra has already been connected. This I was unable to achieve. Instead, I have to manually disconnect Jabra (by powering it off or temporarily powering off Bluetooth on the phone) and then manually connect the phone with the T605, for both Headset and Wireless Music (two actions required!). Now, for me, this is unacceptable.
Moreover, when I arrive to a destination and want to step out of the car, I have to manually reconnect my Jabra to the Kaiser, again, through the phone’s Bluetooth settings as described above. A short tap on Jabra’s button no longer works for this purpose, in opposite to SE K800i.
Making the long story short, this is completely unacceptable behavior for me, and I haven’t found so far a way to make it the way I need it.
Any advices?
mpogr said:
Hi all,
I've just bought my first HTC unit ever (Kaiser), which is also my first Windows Mobile Phone (I used PocketPCs since 2001 but with no integrated phone so far), and it seems to have a lot of issues in the areas of "regular phone" functionality.
However, the one that is really freaking me out so far is the whole "Bluetooth audio" area. I'm just wondering whether I would ever be able to get what I want or am I asking too much.
I have 3 Bluetooth audio devices, all of them are dual Headset/Headphone ones: in-car fixed Motorola T605, Jabra BT8010 and Plantronics 590. Now, naturally, I want to use the T605 in the car, Jabra for phone calls only throughout the day and for music occasionally, and Plantronics when I'm in the gym, for both music and occasional incoming phone calls.
I had all this working flawlessly with my SonyEricsson K800i phone: each device connected to the phone automatically when powered up and automatically took over both Headset and Headphone functions. The only minor problem was reconnecting Jabra when stepping out of the car, which required only a short tap on the button.
Now, with Kaiser, things are much more complicated. When a device (any of them) is connected to the phone, both as Headset and Headphones, it works mostly OK, although sometimes there is a problem of sound not coming through the device when an incoming call was answered while playing music. The music is suspended OK, but the sound comes from the phone speaker instead of the respective Bluetooth device. This happens from time to time, not always.
But the biggest problem is the initial connection of a device after another one has already been connected. When I enter my car and fire up the engine, I want the T605 to automatically connect to the phone even if Jabra has already been connected. This I was unable to achieve. Instead, I have to manually disconnect Jabra (by powering it off or temporarily powering off Bluetooth on the phone) and then manually connect the phone with the T605, for both Headset and Wireless Music (two actions required!). Now, for me, this is unacceptable.
Moreover, when I arrive to a destination and want to step out of the car, I have to manually reconnect my Jabra to the Kaiser, again, through the phone’s Bluetooth settings as described above. A short tap on Jabra’s button no longer works for this purpose, in opposite to SE K800i.
Making the long story short, this is completely unacceptable behavior for me, and I haven’t found so far a way to make it the way I need it.
Any advices?
Click to expand...
Click to collapse
Have you tried the Bluetooth fix on HTC's website?
Asking is easy, searching is hard work for some people it seems. No offence..
I'm using Schap's ROM which is supposed to have this fix built-in.
mpogr said:
I'm using Schap's ROM which is supposed to have this fix built-in.
Click to expand...
Click to collapse
Ahh. didn't see that in your first post..
I think you are suffering the same prob as many. Every time a BT device comes out, it never seems to work with what we had before. BT protocols are NOT fixed (The IEEE STILL have not fully implemented a specific proto!), they change faster than we change our devices.
As I said before (without meaning any offence) search the whole forum, many threads have been out on this subject and some advice/fixes or equipment references are out there.
Well, I did search these forums and haven't seen someone referring to the same kind of problems I'm having.
Now, regarding your comment about variety of BT devices... I don't buy that. My SE K800i is 1 year old and works perfectly with this combination of devices.
I have pretty extensive experience with Broadcom/Widcomm BT stack on PC and older models of PocketPC (the one I have is IPAQ 5555) and I suspect these foes are direct derivatives from the fact Kaiser uses MS BT stack, which is much inferior. However, it seems nobody was able to make Broadcom/Widcomm stack work on Kaiser so far...
mpogr said:
Well, I did search these forums and haven't seen someone referring to the same kind of problems I'm having.
Now, regarding your comment about variety of BT devices... I don't buy that. My SE K800i is 1 year old and works perfectly with this combination of devices.
I have pretty extensive experience with Broadcom/Widcomm BT stack on PC and older models of PocketPC (the one I have is IPAQ 5555) and I suspect these foes are direct derivatives from the fact Kaiser uses MS BT stack, which is much inferior. However, it seems nobody was able to make Broadcom/Widcomm stack work on Kaiser so far...
Click to expand...
Click to collapse
OK, I'm sorry if you don't. I only tried to help. Seem's you've asked a question and have already formed an opinion to it!!!
I have personal experience of Sony's proprietory connection limitations.
My BT works fine on all my devices....will leave you to others.
Looks like I found a partial solution which makes my life almost perfect...
It seems the real problem is taking over Kaiser from a previously connected device. So, if I switch my Jabra off several seconds before I fire up my car's engine, my T605 is able to connect to it. Same goes the other way around, I can turn off the car engine and then fire up the Jabra several seconds later. In this case all is good.
Looks like the MS BT stack is still ill-implemented though, as, for example, when in active Wireless Music BT connection, the device is unable to discover any other Bluetooth devices or to connect to other device's BT serial interface, which makes using external GPS devices difficult.
This could be a problem for me since my car (Citroen C5) has special anti-radiation coating on its windshield which quite effectively screens the satellite signals. Therefore I came up with a solution of having a BT GPS device permanently located in the car (actually, in the driver's seat back pocket) hardwired to the mains as well as to an external GPS antenna. This setup is effectively beating both reception and start-up time problems.
With Kaiser’s limitation on simultaneous BT connections I’m unable to use this setup anymore. Yes, I could bypass using an additional GPS device by connecting the external antenna to Kaiser’s internal GPS, but this looks like a cumbersome solution as I couldn’t find a Kaiser-compatible mounting with a socket for hardwiring an external GPS antenna.
Luckily for me, I still have my old IPAQ loaded with GPS software which I prefer to use for navigation anyway thanks to its significantly bigger screen
mpogr said:
Looks like I found a partial solution which makes my life almost perfect...
It seems the real problem is taking over Kaiser from a previously connected device. So, if I switch my Jabra off several seconds before I fire up my car's engine, my T605 is able to connect to it. Same goes the other way around, I can turn off the car engine and then fire up the Jabra several seconds later. In this case all is good.
Looks like the MS BT stack is still ill-implemented though, as, for example, when in active Wireless Music BT connection, the device is unable to discover any other Bluetooth devices or to connect to other device's BT serial interface, which makes using external GPS devices difficult.
This could be a problem for me since my car (Citroen C5) has special anti-radiation coating on its windshield which quite effectively screens the satellite signals. Therefore I came up with a solution of having a BT GPS device permanently located in the car (actually, in the driver's seat back pocket) hardwired to the mains as well as to an external GPS antenna. This setup is effectively beating both reception and start-up time problems.
With Kaiser’s limitation on simultaneous BT connections I’m unable to use this setup anymore. Yes, I could bypass using an additional GPS device by connecting the external antenna to Kaiser’s internal GPS, but this looks like a cumbersome solution as I couldn’t find a Kaiser-compatible mounting with a socket for hardwiring an external GPS antenna.
Luckily for me, I still have my old IPAQ loaded with GPS software which I prefer to use for navigation anyway thanks to its significantly bigger screen
Click to expand...
Click to collapse
Glad to here you have a resolution (albeit a partial one).
Just one thing, why would you want to connect to an external BT GPS at the same time as your car kit? Can't you get a good enough signal on the internal GPS or is there another reason?
Farsquidge said:
...Can't you get a good enough signal on the internal GPS...?
Click to expand...
Click to collapse
Yes, that's what I wrote in my post above. This antiradiation coating is a real satellite signal killer...
But, IMO, Kaiser's screen is too small for in-car navigation anyway, so having a dedicated unit is always a plus
mpogr said:
Yes, that's what I wrote in my post above. This antiradiation coating is a real satellite signal killer...
But, IMO, Kaiser's screen is too small for in-car navigation anyway, so having a dedicated unit is always a plus
Click to expand...
Click to collapse
Sorry, blind AND stupid!
Yes I agree the screen is too small for general use. I have a dedicated GPS in the car and only use the TyTnII as a temporary routefinder whenever needed.
So I have an xperia, and I have a new JVC Bluetooth deck, I was so impressed how flawlessly it worked with my old phone the Kaiser/tilt, but to my surprise I have not been able to get it to properly pair up with my newer xperia. They will read each other and try to connect but I always end up getting an error. Sometimes it still shows up as connected but nothing works. I used my kaiser/tilt for both calls and streaming music through my new JVC bluetooth deck and I loved it, so its pretty dissapointing when I upgrade to what is/was one of the hottest & expensive windows mobile phones and it apparently has bluetooth issues.
I tried a few fixes already like changing the registry to read as a normal phone and I added in a missing bt profile, unfortunately nothings changed. I am curious tho because i had a magician and they had whole bt stacks that I messed around with, and I'm also wondering if a flash or two of a new rom may make a difference. Ocerall I'm really happy with the X1 (unlike my tilt/kaiser which had lots of problems) so much so that I don't really feel the need to flash a new rom, but if it might have a chance of fixing my bt I'm all for it.
Let me know if anyone has any suggestions, tia.
Hi Guys
Would really appreciate some help with this one, i am sure it been covered to some degree in other threads.
Since owning my unit I have wanted one application to run and I am not fussed about anything else, the app is ALPconnect.
ALPconnect is a application that connects to my radar detector via BT 4.0 only so it displays all the information on the dash for radar frequencies.
https://play.google.com/store/apps/details?id=com.alpriority.alpconnect&hl=en
Due to the limitations in the Bluetooth, no current rom has been able to allow the application to turn the BT on and search for the ALPconnnect Module
http://www.alpriority.com/product/alpconnect-bluetooth-module-gen2/
Over on the other forum i am apart of http://radarandlaserforum.com, one member has spent upwards of 2000$ buying android head-units to see if this app would run and connect on it.
our small thread is ongoing at @ http://radarandlaserforum.com/showt...-InCar-Enetertainment-unit-ALPconnect-Testing about this issue.
I don't normally ask for help, but I could really use some help and I am sure others on the forum that purchased it for that reason would greatly appreciate it too.
This is the last information I received from agentdr8, thank you aswell
agentdr8 said:
It's severely limited, when compared to any other Android device with BT. This is due to the OEM's choice of the BC5/BC6 module, and their poor BT implementation. Instead of routing BT audio traffic through the Android system, like a normal device would, they route it through the MCU. That would be fine on its own, except they route pretty much all BT interactions through the MCU, via serial AT commands, which is very non-standard. Simple things like pairing, or using SPP profile just don't work, or require a bit of finagling.
On top of that, there's code (at least in MTCB; dunno about newer MTCD) in MTCManager that filters which devices can pair via BT for OBD use. It checks the device name and if it starts with OBD, it will allow it to pass to the next step during pairing. I can only imagine they chose to do that so they could sell their companion BT OBD adapters with the headunits?
My XMTC module had accounted for this limitation in name-based filtering (apparently not the only limitation though; if your adapter was at least v1.4 it should work), but it hasn't been updated to work on any 2016 roms. Since I no longer have time to maintain that project, it's been open sourced on my github. The BT pieces could be extracted into their own module, but I thought I had read someone else (maybe MVG70?) had made a BT xposed module for these devices to try and address compatibility issues.
Click to expand...
Click to collapse
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Sent from my iPhone using Tapatalk
shanetrainST said:
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Click to expand...
Click to collapse
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
agentdr8 said:
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
Click to expand...
Click to collapse
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
shanetrainST said:
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
Click to expand...
Click to collapse
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Guess the manufacturer is reluctant to release the source then.
Sent from my iPhone using Tapatalk
agentdr8 said:
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Click to expand...
Click to collapse
Just a couple of questions
1.Do you know if any developer is currently working injecting the drivers into the kernel, as impossible as it sounds.
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
3.Have any of the manufactures hinted at releasing the source and letting other developers fix the issue with custom roms
Just on another note
I have 30 emails from Eonon saying that their tech cannot do this and have assured me that.
We have our own brand and R&D department.
We use our software.
Click to expand...
Click to collapse
Which I don't believe for a second
I'm quite interested in getting this fixed as well - I have both an ODB2 adapter and Navdy that I'm unable to connect due to this limitation. And the fact that there's no available workaround via External BT is infuriating.
shanetrainST said:
Just a couple of questions
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
Click to expand...
Click to collapse
From my understanding, the only way to get this to work is through an external (USB) BT adapter, since the built-in BT stack sends everything through the MCU instead of directly to android. So enabling the proper USB drivers for BT in the Kernel would fix it. I'm not aware of any other USB devices that don't work (maybe gamepads or other HID devices, unconfirmed) so it seems they've cherry picked which USB devices to allow. Considering the otherwise hackable nature of these devices, it'd make sense to me to just enable all available USB devices and let us plug in whatever we want to plug in.
I'm in the same boat. I have an OBD adapter (Hondash) which refuses to pair. I've tried 2 Xposed modules which are supposed to sort this. I'm wondering if my particular issue is down to my 5.1.1 ROM so might try it on my old RK3066 4.4.4 HU which I gave to my Dad.
So I'm monitoring this thread in the hope a fix is found.
I am doubtful, I have contacted Klyde/Eonon/others and nobody is willing to release the kernel source code or address the issue.
So when someone gets a copy from Klyde/some reseller/MTC or whoever and a developer has the motivation to correct it, that can be the only solution.
I have given up hope on this one
Sent from my iPhone using Tapatalk
Does anyone know the location in the Android file system where the Bluetooth pairings are saved?
FINALLY! Someone with a similar issue. I've got a Valentine One, and the BT module for android, (connecting using YaV1) and I've been trying to get my android unit to pair with it as well. In for potential solutions.
This question may be off topic, and I apologize for that, but are you referring to the app not being able to turn on BT and look for the adapter; just getting stuck at "Turning on bluetooth..."?
I have an OBDII scanner which I can pair no problem. When I use a specific app (OBD Card Doctor Pro (or reg)) and attempt to connect it, I get a prompt letting me know that an app wants to turn on BT. I click allow and then it just sits there and never does anything. Is that the problem ALPconnect has?
Torque does not prompt me with this and initiates the BT connection just fine.
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
monza20vt said:
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
Click to expand...
Click to collapse
So this emulated effect is what causes my system get stuck "Turnning on bluetooth..." if I understand you correctly? There's no Android control over the BT hardware so the request is just lot in limbo?