Related
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....
Hi there,
I installed the VoIP hack for WM6.1 to get the VoIP feature, so that worked, can use Voxalot over HSDPA/WiFi etc now. But.... Guess what... GPS is not working anymore.
So I found a few files that should enable GPS and VoIP, but still GPS is not working. TomTom say 'no GPS device found'...
Anyone here got VoIP and GPS working on his/her Xperia? Would you please tell me what files I should use?
Argh, that's happened to mine too. Just when I thought I was done with hard resets!
Yeah... hehe... But still, anyone got a solution for this?
i have the same problem! ARGH! im gonna brake my xperia in half, im tierd of hard reseting all the time. have anyone solved the problem yet?
This seems worthy of a *bump* since it's an X1 only problem that doesn't seem to have gotten any attention anywhere at all yet; and also VOIP would be cool.
In addition to the bump, I've followed the instructions from this topic and I got VoIP to work WITH GPS. Howeverrrrr.. As I've posted overthere, unlike the 'normal' suggested cabs, the sound now comes from the external speaker, which of course sucks. I want it to come from the internal speaker.
When you use a Bluetooth headset there is no problem at all, but who wants to walk around with one of those all day long? Was wondering if anyone had a fix for that...!
Hi guys,
i recently received my iTech R35 A2DP Bluetooth Headset for my Touch HD which is identical to HTC BH S100 since its only rebranded.
Pairing, controls and everything works fine, but when playing music the connection constantly gets lost for short terms regardless of the distance between the phone and the Headset.
The weird thing about it is, that the headset works perfectly with my friends HD. He even could go away like 10m without any kind of interruption.
I already tried some different settings with HD Tweak but no improvement.
Besides I noticed that overall bluetooth performance with my phone, as it once took about 30 minutes to send a 50MB file, isn't that good.
Thanks for any help!
Update:
I tested the Headset today with two other phones (SE W950i and some Nokia). It worked perfectly so I figure something has to be wrong with my phone. I'll perform a hard reset on the weekend and see if it changes anything. Otherwise I'll have to contact the customer service.
Has anybody here experience with german support. If I had to send the phone in, how does it usually take til u get your phone back?
Well, I just performed the hard reset and it solved the issue. Very strange since I hadn't installed that much programs.
Well, the problem returned and I now figured it out in detail.
There's no correlation with the programs installed.
Once the Bluetooth headset is in the Bluetooth-Device-List as it was connected before the constant lags are there.
If I delete it and re-pair the headset the lags are gone for this one time until the headset got disconnected. Even if I get out of range and return in reach connection is crappy from then on.
Didn't anybody recognize such a strange behaviour too?
I have a similar issue with my Sony Ericsson HBH-IS800 phones.
I thought I'd solved it by re-pairing with the handset, and initially that pairing seemed to last for a while, but now it seems I have to re-pair at least once a day to avoid the stuttering (it's really bad, isn't it?)
Frankly, I'm getting pretty disenchanted with my HD. Every time I discover a tweak which sorts an issue, another issue raises its head. I've lost count of the many hours I've spent trrying to get it to work as it ought to.
Wishing I'd got an iPhone. Okay it's not as good on paper, but at least everything works....
I have to agree the bluetooth is dodgy for me at the best of times in trying to connect to any computer.
Surprisingly, Ive had a good file transfer between my HD and MaxOSX, I can't say the same for Windows XP or Vista where on both accounts it has failed to connect via bluetooth to perform an active sync.
Petee said:
I have a similar issue with my Sony Ericsson HBH-IS800 phones.
I thought I'd solved it by re-pairing with the handset, and initially that pairing seemed to last for a while, but now it seems I have to re-pair at least once a day to avoid the stuttering (it's really bad, isn't it?)
Frankly, I'm getting pretty disenchanted with my HD. Every time I discover a tweak which sorts an issue, another issue raises its head. I've lost count of the many hours I've spent trrying to get it to work as it ought to.
Wishing I'd got an iPhone. Okay it's not as good on paper, but at least everything works....
Click to expand...
Click to collapse
Thanks for your information. At least I'm not the only one with this issue.
Meanwhile I tested this behaviour with my buddies HD and it's the same pattern with his one.
I contacted german support today and will report after their answer.
i've been having the exact same problems with my hd. i would be able to pair it with my landrover, but then the connection would be lost. (there's another thread on this somewhere).
anyway, i tried installing BTRestore and BTRestart along with Mortscript and a custom script to help keep the bluetooth active. however, my problem was not that the bluetooth was turning off, but that the connection would not stay active.
so i installed a custom rom, Dutty's version 1.7, and also installed jetware bluetooth program (www.jetwaremobile.com); so far so good (*fingers crossed*). this is my 3rd day and the bluetooth works great. the phone connects with the car instantly, my phonebook works and i can make and receive calls without losing the connection.
so maybe updating the rom will help you too.
Sorry, it's been a while since HTC answered my questions but since their answer was quite disappointing I had no rush to post it.
Summarized they told me the HTC BH S100 was not compatible with the Touch HD even though I pointed out that it's in compatibility-list of the Diamond and both are running the same Chipset and OS and that it works fine after the first pairing.
As I'm tired of reconfiguring my phone I'll wait some time to flash another ROM. I hope WM 6.5 will be released soon and fix this problem, too.
So I flashed to a froyo ROM over the weekend and have found someone posted a fix for the gps issues, but I'm having BT issues as well. Has anyone else experienced this: I can pair certain BT accessories but not others, and even when paired the devices cannot connect without multiple connection requests.
My specific issue is that I have motorola rockr bt earbuds, and a Jabra car kit, and they both pair with the phone (after a few trys) but neither will automatically connect to the phone once they're turned on. With the earbuds I have to manually try to connect 6 or 7 times in a row before they'll connect, and even then they may only connect with the phone audio only. This wasn't an issue with the stock ROM so I'm assuming its the bt radio library for Froyo thats the problem?
I'm not new to development, but I'm kinda new to development on Android. I've been trying to learn more about the radios and how they're configured within the OS but I haven't found a lot of good documentation on it. I'd be happy to work this out for myself and post any improved radio to the forum but it would be helpful if someone could send me a link to some learning material? If someone has an improved Epic Froyo BT radio to flash that would be helpful as well
yes bluetooth issues as well, but different in that only when i turn bluetooth on it foreclose's. the bluetooth is otherwise not affeceted. only on the initial start up.
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Delta1Fox said:
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Click to expand...
Click to collapse
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
revjtanton said:
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
Click to expand...
Click to collapse
I noticed that too with the stock 2.1. However, Bluetooth voice dialing is a feature built into 2.2. I've read that some people having it work great, but other's like myself, are not having it work at all. Oh well. I'll live for now. Hopefully if it isn't fixed beforehand then it'll be fixed with the "official" release. LOL.
now that you mention it, i had this problem too doing some bluetooth file transfers between my buddy and I's phones last night. it struggled to connect multiple times but after the first successful transfer it seemed to stop having problems for a little. I'm moving back to 2.1 until we get some non-beta custom roms for froyo because i use bluetooth and gps everyday. just out of curiosity though, for those who are having problems, which rom and modem are you using?
I put the DI18 modern on there and that has seemed to fix the gps more or less. I think I'm going to go back as well. Maybe I didn't flush data enough times but layar can't find the camera, neither can the bar code scanner...it's close, but Froyo just isn't ready for the Epic yet.
Sent from my SPH-D700 using XDA App
Still having Bluetooth problems with official Froyo release on Epic 4G
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
I am using the new official Froyo release from Samsung/Sprint. having the same buggy issues I had with the old leaked version.
donkeysauce said:
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
Click to expand...
Click to collapse
I can confirm these issues still exist in the official release.
I'm having the same problem, but when I use bluetooth in my car, it insists on transmitting sounds to my car's bluetooth, even when I repeatedly uncheck Use for media audio. I don't have an option in my car to disable A2DP. My only complaint with Eclair, other than speed (I'm using Bonsai4All, and previously, Syndicate) was that I was running out of space for software (was using EpicExperience). Sometimes, bluetooth won't connect at all, necessitating a phone reboot, or going into airplane moe and then back out. So I'm gathering that this is across the board, regardless of Froyo build? Syndicate didn't work at all with my car.
Good morning fellow forum member. I've recently begun having some significant bluetooth connectivity issues with my continuum and Ford Sync system in my 2011 Fiesta. Now, before you start ranting about your loath for microsoft or Ford please hear me out. In theory, the Sync system, combined with bluetooth technology, is a great way to go hands free. It also allows for the coordination of the system and Pandora & Stitcher Radio on an Android phone.
Anyway, lately my bluetooth connection to my car has been causing FCs on my phone. They are the type of FCs that cause the "long-short-short-short" haptic feedback but doesn't throw a pop-up message describing the cause of the FC. So, when the feedback occurs the phone will sometimes lock up but it always disconnects the bluetooth. I don't use bluetooth in any other fashion so I can't be positive that it's not an issue with the car's bluettoth system.
With all of that said, is there an inherent issue with the bluetooth system on our phone? If so, is there a fix for this? I'm currently running the EC07-clean_new ROM. This was installed over the SCH-I400-EC07-FROYO-REL-PRODUCTION ROM. My broadband version iss:i400.0.6v.EC06, Kernel 2.6.32.9 and build SCH-I400.EC07.
Any help that you brilliant folks could offer would be much appreciated.
Thanks,
Ray
I run bluetooth constantly (it's the only way I talk on my phone, driving or not.) I've never run into this issue. Have you recently downloaded any new apps? I found that there are some apps that simply don't play well with our phones. Especially radio based apps (I.E. the issues a lot of us were having with gps based apps, or gps losing it's lock, after a while. Wireless tether 3.06 beta completely screwed my phone up... etc). The only other thing I could suggest is to drop your phone from the sync, and reconnect it... I do this with all my bluetooth devices at least twice a week as a matter of course. And if you want to experiment to see if it's sync or your phone, assuming you have bluetooth stack on your computer, you could connect it to your phone. Other than that, maybe find a friend that has bluetooth and connect it?
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Reborn627 said:
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Click to expand...
Click to collapse
I think you should be good with rourine disconnect/reconnect. Asfor too many apps, the only thing rhat matters there is storage space. Android wint let you run "too many" at once. Itll delete from ram as needed. I was just saying that certain apps dont seem to play well with others. But that is an android issue, not your phone in particular.
I'm not here for a long time. I'm here for a good time. To hell with the red wine. Pour me some moonshine. - King George
I'm totally stumped here. Yesterday I decided to reflash my phone. I figured any issues might be ironed out. It must be an app issue, although it is going to be a PIA to uninstall then reinstall each app and test the BT after each app install. I thought that it might be the trailblazer101 car cradle, desk cradle or the sticher apps that were giving me the problem but that doesn't seem to be the case. Maybe I'll try replacing the BT files with the ones from eclair to see if I end up with the same trouble. Any idea if that might cause more problems? Are the BT files android version specific?
Peace
EDIT: I've not swapped the BT files from eclair but I did spend an hour or so listening to Stitcher radio via a bluetooth headset. It doesn't seem to be a BT issue. More likely an issue with the connection to the Sync system itself. Connecting via bluetooth is no problem in the car. It's not until I attempt to engage a function other than the phone that an issue occurs. I may try to reflash the EC07-clean ROM and see if there was something with the EC07-Clean_new version that I've been running for the last few weeks.
OK, the BT issue seems to be corrected. I flashed adrenalyn's EC07-clean ROM and that seemed to do it. Something must have gotten corrupted. So, issue resolved...i guess.