Hey has anyone tested BT data on Flipz test 2.1 build? I tried it to upload my contacts to my navi but I couldn't get it to go but curious if anyone tried on any other levels.
Thanks!
Related
Hello,
i have the same problem of bluetooth disconnection problem that other users are reporting.
I've read many seems to have found a solution but all the fix suggested didn't solved. Right now I'm running xdalive 2 with 1.38 radio rom, and the disconnections are much less frequent but still happens.
Who solved the issue can please details the changes that made it works?
With this version (XDALIVE) I haven't already tried the registry settings. With LVSW I tried but it didn't changed the behavior of bluetooth.
Thanks
anyone?..
I am having the same problem with my Trinity and my A4.
What I have found is that if you go into commections and refresh the handsfree then the unit re-connects on saving. Does anyone know if this could be done automatically upon recieving a call or could a macro be written to perform a refresh through the phone menu?
Thanks
stepir said:
Hello,
i have the same problem of bluetooth disconnection problem that other users are reporting.
I've read many seems to have found a solution but all the fix suggested didn't solved. Right now I'm running xdalive 2 with 1.38 radio rom, and the disconnections are much less frequent but still happens.
Who solved the issue can please details the changes that made it works?
With this version (XDALIVE) I haven't already tried the registry settings. With LVSW I tried but it didn't changed the behavior of bluetooth.
Thanks
Click to expand...
Click to collapse
I would try black 2.0. With this rom I now have better bluetooth support for my Jeep Cherokee. With this ROM I now get signal strength and battery guage to show on my Cherokee nav/radio system when making calls
Hello all. This is my first time posting a new thread although I've been lurking around here for a while soaking up all the information from this wonderful site. That said, I have been researching my problem for days now both here and on google and have found no solutions that work. So I'll see if there's anyone here who can help. Here goes....
I have recently flashed DCD's 3.2.6 ROM on my Verizon XV6800 and it works great (love the aGPS too, Thanks GC14) in every area but my car. I have a 2004 Audi A4 with the RNS-E Nav system with integrated bluetooth. Before I flashed to DCD, I had the original stock ROM (2.09.605.8 with Radio 1.30.00) which gave me full functionality with Jetware Mobile (Phonebook and Recent, Received & Missed Calls all transferred). Now, with DCD, it'll only connect to the car and won't transfer anything. If I try to load Jetware, it'll just lock up my phone while I'm connected to the car. Thanks in advance for any help you can provide.
No one else has this problem or a fix for it?
TGabriele said:
No one else has this problem or a fix for it?
Click to expand...
Click to collapse
I wish I was rich enough to afford such a car, then I could maybe help you out. LOL
But I would gladly accept such a car as payment for figuring out your problem.
Nevermind that the car is an Audi. Does anyone else have this problem with a factory BT system that transfers the phonebook to their car.
I had this same issue on my X3 and it seemed to be the way the PPC wanted to transfer the phonebook was by using some file transfer protocol the car did not understand. I could sync it and make and receive calls but no phonebook. Took it to the sprint store and we tried a blackberry and a standard moto handset. The blackberry did not sync the phonebook either but the standard moto phone did. I don’t think it’s possible based on the profiles in the car so I gave up on the phonebook. Try changing the bluetooth stack in the rom, you will have have to make your own rom and beware of the stack you use to make sure it is one for your phone.
I flashed DCD's rom using the kitchen, so making a custom rom from there is no problem to me. What I'm not sure of is how to change the bluetooth stack. I thought it is part of the hard coding for the OS? If you or someone else reading this thread has any information on this or can point me to some info on this it would be greatly appreciated.
I have the 6800 with DCD 3.2.6, and an Audi, with full phonebook transfer so I'll try to help you out:
1. Which 6800 radio are you using? I have found 3.42.50 to be the best as far as Audi bluetooth compatibility is concerned.
2. Jetware will not work with WM 6.1 on the 6800, but you don't need it, since 6.1 included phonebook transfer enhancements.
3. What version of Audi software are you at? There have been several releases since your year. You should be able to get more info from www.navplus.us and of course from your stealer.
4. You do have your bluetooth settings set for "discoverable", right? And, (I don't know why this is the case) it seems when OBEX is on, the phonebook and other items transfer quicker.
If you have the 6800 radio and Audi software updated, you should have no problem. Jetware is no longer necessary.
1. I am using radio ROM 3.42.50
2. The reason I loaded Jetware is to have it sort my contacts by Last,
First. Is there another way to do this?
3. I am running sw0200 on my RNS-E, but was considering moving up to
sw0260.
4. I haven't tried this, but I will.
Lately I've also had the issue where if the phone is connected to the car for a while, the bluetooth on the phone will shut itself off and not turn back on until I do it manually. I'm beginning to wonder if I should just hard reset and start from scratch. Any ideas? Thanks in advance.
I'm sure there's a reg tweak for listing First name first in contacts. Hunt around here or at ppcgeeks. If you want to stay on 6.1 jetware will not work (unless they release a new version).
Definitely update the Audi software to the newest version.
DCD has done nicely fixing power settings in the last few ROMS to solve the bluetooth shutting off issue, although when memory gets very low, it may still happen. You must have some other program or process running that sucks up memory if you are still experiencing this.
It never hurts to hard reset, as long as you have the time.
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
TGabriele said:
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
Click to expand...
Click to collapse
I'm running an after market HU (Pioneer AVH-P4000DVD) and DCD's latest ROM, and Jetware works fine on mine. Just re-transfered my phone book earlier today....
I'm currently running DamageControl 1.0 but have also tried AOSP 2.1 and DarchLegend 4.1 and cannot get my phone to pair the 'calls' part to my Pioneer car stereo. The music part pairs fine but not the phone. It worked perfectly on every version of 1.5 I ran.
Is there a way to push some 1.5 bluetooth files to a 2.1 rom?
I searched XDA and it appears that some folks with Eris phone using the latest leak are also experiencing this same thing, one guy specifically stated he had a Pioneer deck as well - coincidence? Could it be Pioneer?
Reading the rom specific threads it appears that most folks have working bluetooth so it may be my situation, hence the question, can I push some 1.5 files to 2.1 to get the phone to pair? If so, any help as to which ones?
ItsDon said:
I'm currently running DamageControl 1.0 but have also tried AOSP 2.1 and DarchLegend 4.1 and cannot get my phone to pair the 'calls' part to my Pioneer car stereo. The music part pairs fine but not the phone. It worked perfectly on every version of 1.5 I ran.
Is there a way to push some 1.5 bluetooth files to a 2.1 rom?
I searched XDA and it appears that some folks with Eris phone using the latest leak are also experiencing this same thing, one guy specifically stated he had a Pioneer deck as well - coincidence? Could it be Pioneer?
Reading the rom specific threads it appears that most folks have working bluetooth so it may be my situation, hence the question, can I push some 1.5 files to 2.1 to get the phone to pair? If so, any help as to which ones?
Click to expand...
Click to collapse
I am also running into this with all 2.1. I have a premier(pioneer) deck. Any luck finding a solution?
CharlyDigital said:
I am also running into this with all 2.1. I have a premier(pioneer) deck. Any luck finding a solution?
Click to expand...
Click to collapse
Nope. I tried everything possible but nothing got the phone and radio to pair. I just can't go back to 1.5 so I've resorted to using a BT earpiece until the official 2.1 is released. Hopefully it will have an updated Bluetooth.
If you come across something I'd love to be kept in the loop.
Truely sorry i cant be much help...but you might consider posting your question in damages thread, or pm him.
Cheers
Just wondering if it's possible to pull out everything related to bluetooth and A2DP (Stereo Bluetooth Audio) from 1.5 and insert it into damages 2.1 ROM.
I have tried every 2.1 ROM and I can't seem to get reliable bluetooth audio through my headphones, it skips and cuts out. It is very frustrating.
I have tried several headset to no avail, it always work flawless in 1.5.
I just got done running a logcat as well, and everytime it would skip or cutout nothing showed in the logcat, it was very strange!
Thanks
Roman
Roman G said:
Just wondering if it's possible to pull out everything related to bluetooth and A2DP (Stereo Bluetooth Audio) from 1.5 and insert it into damages 2.1 ROM.
I have tried every 2.1 ROM and I can't seem to get reliable bluetooth audio through my headphones, it skips and cuts out. It is very frustrating.
I have tried several headset to no avail, it always work flawless in 1.5.
I just got done running a logcat as well, and everytime it would skip or cutout nothing showed in the logcat, it was very strange!
Thanks
Roman
Click to expand...
Click to collapse
These ROMs still are not official builds from Sprint and HTC. They are leaked beta versions.
I am sure until Sprint officially releases their update that some of these things will be buggy.
Everything else in his newest ROM is flawless.
DJAscendance said:
These ROMs still are not official builds from Sprint and HTC. They are leaked beta versions.
I am sure until Sprint officially releases their update that some of these things will be buggy.
Everything else in his newest ROM is flawless.
Click to expand...
Click to collapse
Oh I realize that, I was just wondering how hard it is to do that and if it could be done!
Some of the other Roms I have tried have been complete dumps and none of them have worked either!
I was wondering if anyone had figured out a fix for this problem:
The USB audio out function when using any dock application no longer works in any 2.3 build. It had worked in every 2.2 build/ROM I have tried, but regardless of what I try on 2.3, no dice.
I have tried the SGS Audio Dock routing app and setting it manually, with no luck. Has anyone else encountered this and figured out a solution/workaround (besides just putting in the 3.5 jack or bluetooth )?
Even if someone could point me in the right direction of where to poke around, that'd be great! I honestly just don't know where to begin...
tragicallyhip said:
I was wondering if anyone had figured out a fix for this problem:
The USB audio out function when using any dock application no longer works in any 2.3 build. It had worked in every 2.2 build/ROM I have tried, but regardless of what I try on 2.3, no dice.
I have tried the SGS Audio Dock routing app and setting it manually, with no luck. Has anyone else encountered this and figured out a solution/workaround (besides just putting in the 3.5 jack or bluetooth )?
Even if someone could point me in the right direction of where to poke around, that'd be great! I honestly just don't know where to begin...
Click to expand...
Click to collapse
Which rom? EF02 stock? It works for me using Galaxy Dock Sound Redirector on AA i3.
Edit: Just noticed you said EE03. If you still have EE03 you need to upgrade to EF02 to get audio through USB, as it was not supported in EE03.