Am I the only one who can not use BT on GT p1000 (FROYO.XXJK5)?
After a few seconds of call (30?), screen turns off and BT disconnects! Call continues on speaker - unusable as a phone! (BT ear peace is Emporia BT voice). It worked like charm on winmo Blackstone and Leo (until screen died after rom update (official).
Have I missed (or messed) some settings?
Thanks for quick help
Help, please, more than 30 views, no ideas? What am I doing wrong? It is disconnecting from bluetooth in Toyota factory BT also. Screen off in call and BT off also!!
Any ideas????
Related
hi ppl
i use an austrian mda2 w/ ROM 1.6.00GER and ExtROM 1.60.07 together with a parrot ck3000 handsfree in my car.
i use the original bt stack w/o ANY changes.
making calls and taking calls is no problem at all and works most of the times.
the problem is as follows: when i enter the car, bt turned on, and also profile says "BT Headset ist eingeschaltet (means bt headset is turned ON)", and the n i want to place a call, the call is not routed over the handsfree. explanation is simple: when i change back to "today" - bt is turned OFF !!!
so my conclusion: everytime bt is used for the first time after disconnetion from the handsfree, it just turns OFF when it should connect. after i turn bt on by hand again it works w/o any problem. ('till i come back to the car of course - and everything starts again)
this is very annoying....
so has anyone any hint what to do? i wouldn't really mind updating to an english rom - if i just knew that that does work.
thanks,
servus ize|man
when i use this one
http://bluetooth.i-networx.de/index_e.html
my device turn bluetooth on when i call even though i dont have a bluetooth headset maybe it'll help you
thanks rudegar
i know that stack by TOWA. unfortunately that does not work at all here
i'd love to use it, but w/ this stack my handsfree is reconized sometimes, sometimes i have to pair the devices every time i start my car, and i can NEVER place calls with the combination mda2 with networx bt manager installed.
maybe someone has the same experiences and can report them
servus ize|man
When the headset is paired with the phone can I somehow receive a call on the phone and not on the headset or I should turn off the headset if I want to do that ?
Sorry if the answer is in the 2020 manual - didnt get it when I bought it
Thanks
If you want to answer the call with the PDA, you'd use the green button on the himalaya. If you don't press the control in the headset and get the call using the green button the audio comes out from the PDA and not from the headset.
I hope my poor english is understandable.
omg, yes I undesranded you perfectly, thanks
You just reminded me of my big problem once, somehow I ve changed digital clock to analog in the today screen. After some time I ve forget how did I do that and no matter of what I used to try clock remained analog. Digged thru the 2020 from alpha to omega, digged thru the registry... No luck. Utils, no luck. Clock remained analog.
Asked my friend, qtek user, about the problem. Guy clicked and holded the stylus on the clock for a few seconds. Menu appeared - digital or analog
Obviusly some simple solutions are not always visible to all of us
Thank you once more
ahh one more quickie please, if the headset is paired to the phone and Im a caller how can I talk to someone using the PDA not headset ?
thanks
BT headset (not work ;P )
Gosh.. I would like to have your problems... I can't turn on headset on BT... when I turn it on the headset connects once and after the connection there is no option to turn it on... only fisconnect of bluetooth and reconnect ;/
O2 XDA 2 with WM 2003 SE
Help, Help, Help....
My HD for some reason cuts off at approximately 5 mins during every converstaion on my handsfree.
Phone is paired using Bluetooth and its paired to the bluetooth on the radio in my Pug 407. Really annoying - as I cant seem to get the call back.
Any ideas ???
Cheers
Si
I have a jade working with a BT110 it answers the call fine but after the call the headset apears to turn off which it is supposed to do but the phone thinks that it is still connected so you have to turn soft reset the phone before you can make/recive a call and hear it via the handset.
has anyone else had this problem or could it possibly be the headset rather than the phone?
Tom
paperclip69 said:
I have a jade working with a BT110 it answers the call fine but after the call the headset apears to turn off which it is supposed to do but the phone thinks that it is still connected so you have to turn soft reset the phone before you can make/recive a call and hear it via the handset. has anyone else had this problem or could it possibly be the headset rather than the phone?
Tom
Click to expand...
Click to collapse
My experience - I use Jabra BT. The BT does not switch off after call is disconnected, until you switch it off. And the phone always thinks that BT is on (even when the BT set is switched off) until BT is disabled using the comm function.
I tried another Jabra headset last night, and although slightly better behaved it still didn't release the phone when turned off?
does anyone use a BT headset with the jade that works properly? what are peoples experiances.
anyone know what it is about the jade that makes it not work right?
I'm having much fun with my new Legend, and I love android 2.1!
Everythings goes smooth except the connection with my car.
I have a pretty new Audi TT from 2008, and with my old phone (t-mobile G1), I used it without a problem for over a year.
One month ago I bought the Legend, and bluetooth connection to the car seems to hang!, Even when I disable bluetooth, the phone becomes slow, and the bluetooth icoon keeps displaying in my notification erea.
One thing works, when I reset the phone, I can use the carkit for about 10 minutes, then it starts to disconnect. The adress book never syncs.
Can people please reply if they got their legend work properly with their bluetooth car kit.
Also when other people have problems, please reply here!
Thnx
I have a mini cooper S with BT car kit.
The connection is good and all the contats are correctly transferred but sometimes the connection has been lost.
It seems it happens during the net switch (between UMTS/GSM).
Same problem here. Kenwood DDX7029 with BT. 5 out of 10 times the phone won't connect when starting the car. Dis- and enabling BT does the trick.
David67 said:
I have a mini cooper S with BT car kit.
The connection is good and all the contats are correctly transferred but sometimes the connection has been lost.
It seems it happens during the net switch (between UMTS/GSM).
Click to expand...
Click to collapse
This implies that if you disable data-roaming, it would work all the time?, I'm gonna try that out! Thanks for your reply!
Hi there. My first post in XDA
So cool that I found this thread because I have the exact same problem. I have an Audi A3 and the bluetooth connection is 9 out of 10 times lost during conversations and then the bluetooth icon just hangs until I boot the phone.
I'm gonna try to disable the data-roaming and see whether it works.
Still problem carkit/bluetooth Legend!!
Hi all,
I still/also experience problems with my Audi A4 carkit.
Also my colleague with a Opel Insignia experiencing the same problems.
I have to reset the bluetooth or reboot the phone te fix it
It is very annoying when you loose the bluetooth connection within a call.
I have already sent a message to HTC...and still waiting!
Switching off the data roaming or fix the UMTS/GSM settings doesn't help
Somebody a sollution?
Br Dide
Audi UHV 6654 problems
I have a BIG problem with this car kit connection...BIG means the device is useless till now.
I've paired the Legend with my A4 factory car kit and there are several problems:
1. No sounds come from the speakers (car speakers), still the michrophone is working fine. I had to put the phone on loudspeaker to hear something but of course this is not the normal way of using a car kit
2. There is no sound till the call is actually ongoing (the other party respond)...that means no ringing, busy tone, or whatsoever sound... I don't even know if the call is made if I'm not looking to the phone (and if it's entering power saving mode, I stare at a blank screen).
I don't have any problems of this kind using a Nokia phone and also they (especially point 2) are happening with all smartphones I've tried (WinMo or Android ones).
Is there any software (even a paid one) to outcome this?
Please don't tell me to "try" this and that, I don't want to spend money "trying" things...I would appreciate if someone had a similar problem and managed to solve it somehow.
P.S The phone is brand new (got it for 2 days by now) and it is not rooted.
P.S.2 The car kit is a "basic" one, don't have navigation, contacts downloading and all that stuff...It's a plain BT car kit, I would just like to be able to make and receive phone calls with it.
Seems like many have bad experience in making the legend and car kit work together.
As of yet I could only pair my legend with my blaupunkt audio system, but they have not yet connected each other successfully to make use of the bluetooth feature. I've had no problem at all using my audio set with my samsung galaxy spica's bluetooth. So it probably is not an android issue.
Is there anyone who didn't experience any such trouble with their legend and car audio system's bluetooth ?
To add some more details...
I search for BT devices, phone finds the Audi UHV car kit. Then I'm asked for the pairing password and I enter it, than I get that "connection sound" from the car speakers but the phone is still "connecting..." endlessly. The BT icon on the phone appears but is the standard one, no headset or car kit icon appears (does it have such an icon after all?)
From here...nothing special happens. When I make or receive a call only the phone is ringing, no sounds came from the car speakers. Only when the call is connected, then I have the bord computer showing "Call..." and the radio/CD is muted...and that's all. The conversation can be heard only into the phone not from car speakers as it was the case with the ringing tone before. When call ends, music resumes.