I have had my SX66 since Wednesday. Here are the issues I have found, and if anyone has any suggestions, PLEASE let me know!
1. Bluetooth is really bad. Scratchy, drop connections, says signal is low even when headset (Jabra 250) is right next to the unit. (I have the O2 3500 stack installed)
2. Bluetooth response time for headset answer button is SLOW, as is sending the data to the headset when a call comes in and is answered by headset.
3. When Bluetooth is ON, the phone will turn the display ON at random intervals, killing the battery if the backlight is left in the on mode.
4. WiFi is horrible, drops connections constantly, even in same room with router (Linksys w/5db antennas atached). Also, it will NOT work with a network unless the SSID s broadcast - so much for security!
5. The phone features are SO vastly different than regular phones, it makes you wonder if it is working. My unit will NOT echo the DTMF into the headset (which every phone I have ever owned did) to confirm pressing (for VM retirval, etc.). Very confusing.
6. Answer after x rings is a joke. I have it set to 2 rings, and it will never answer automatically headset or not...what's the point?
I hope someone out there can help, otherwise, I may have to put this baby on eBay...because it really sucks at this point!
Tom
Update
Well, I downloaded the O2 update, and that seems to have made a difference in the STABILITY of the BT connection; the unit did not drop my headset at all during the day; further the "response" of the SX66 to a command from the headset seems faster.
Also, since I installed this update, I have NOT seen the screen turn on...perhaps this helped that problem...?
:evil: The BT is STILL scratchy/noisy, but not as bad...perhaps the next round will help...?
I will keep you posted!
I have/had the same issues you are describing. The bluetooth patch 3500-124 fixed almost all my BT issues except the extremely low signal. I tried the HS810, HS820 and the Jabra 250. All were horrible. I even went as far as installing the latest i-mate pda2k ROM 1.22.00 wwe on my sx66. I finally took the advice of a poster on another forum (thanks mswlogo) and purchased a sony hbh-300. So far it has been great. It handles the low signal like a champ and doesnt offer any static or popping.
Need a friggin repeater!
Someone should make a BT repeater...or maybe I should try one of those internal antennas..."as seen on tv!"
iam currently using latest rom from dopod and motorola 820, although the two earpiece have sounds it is only mono, can someone help to make it stereo? o recomend what rom to use, thanks
In order to have stereo audio on a Bluetooth device, you need a profile called A2DP, which is currently only supported by the latest Qtek Universal ROM at the moment:
ftp://xda:[email protected]_Updates/UNI_QTEK_13077_176_10900_WWE.exe
Dopod has not released a ROM supporting A2DP yet.
thanks for the help, God bless
No problem. Do let us know whether it works well or not.
it works, i have stereo sound, but need improvements, in a song the bluetoth stops 3 to 4 times when playing, the player dont stop its the motorola 820 that stops several times.
I did come across a post with a patch for the A2DP flaw the other day. It's somewhere on this site - do a search and see if you're lucky.
Found it: http://forum.xda-developers.com/viewtopic.php?t=46811&highlight=universal+a2dp
It worked for me for a little while so try it.
Hi,
I have used A2DP a lot with my JasJar the last 4-5 months, and had written a summary of my experiences with this "lag/stuttering"-issue in another thread here...I have copied the most essential of that text below...might be usefull info for you;
-----------------------------------------------------------------------------------
It seems to be two major factors affecting this "stuttering"/"lag" (from my experiences at least...I have used A2DP a lot with my Universal...couple of hours every day);
1. Universal struggling outputting(RAM/CPU...or both!?)
One help here is to apply the registry "A2DP priority" fix (found it in the forums here...and so did richardlai).
Another is to close all programs before using it (I usually do not do this...I usually only do it in hindsight when I get the problem).
2. Signal between Universal and headset struggling (obstructions between Universal and headset, WiFi nearby, so forth)
I for example get this problem if I put my Universal in my trouser pocket (I know, I must have big pockets, and walk around, I get stuttering/lag occationally. If I then take it out, and hold it in my hand farily still when I walk...no stuttering. I have found, that when I walk, it is Ok to have it in my backpack/rugsack...then for some reason it very rearly stutters...so I usually do that.
But when I walk of the bus at work, and walk into the "campus" of my workplace, which is cramped with radiotransmitters (is norways largest Telecom company)...I get a lot of stuttering, and need to take it out of backpack, and hold it in my hand, at it gets a lot better.
In short: A2DP with the Universal works, but is sensitive to disturbance/obstructions/moving around...and to make it worse, it is also sometimes dependant of the Universal itself struggling with CPU/RAM. So you can not totally get rid of the problem...but you can do a lot to minimize it...I almost never experience it now...except in the campus-area at work that is.
I have BTW had the exact same problems before with Qtek 2020 and Qtek9090 (which I got hold of some "A2DP patches", when I had those devices). ...but I really had a LOT more stuttering with those two...so much so, that I never used A2DP with them on a daily basis.
-----------------------------------------------------------------------------------
I also wrote a short post on my experiences with the different stereo headsets I have...yes, they actually act a little bit different it seems (regarding resume/pause button, and how easy/automatic they "reconnect"). You can see it here; http://forum.xda-developers.com/viewtopic.php?t=47977
Hope this is of some help for you!
RonnyGydar: I came across your little summary a little while ago and have done the registry fix, but the problem still exists! Do you think altering the value in some way would help?
richardlai,
I added the registry value manually...found a reg-file (or was it a CAB-file!?) that supposedly should add it...but when I checked later the key was still not added in the registry?
So I added it manually.
BUT, I do still have the problem...but that seems to be radio interference/distance so forth...since when I hold JasJar in my hand and don't move it around, I NEVER have an problem. ...and actually fairly rearly when I have it in my rugsack/backpack.
With 1 or 2 exceptions...where it lagged "all the time"...but then a soft-reset cured it.
So if you have this problem with your phone lying in front of you on the table...then it really sounds like it is the JasJar/Universal that IS the cause (and not interference)...and yes then the registry hack should help.
BUT I have not done any real testing of the effect of it...I am not sure how much effect it really has...all I know is that I had a "lot of problems" with lag before...and now I almost never have it.
...I hate those "diffuse" problems...when it is impossible to measure in a "scientific" way that "this cures it", and "this do not"! :-(
Sorry about the "little help" I give here...but this issue is a bit "fuzzy"...I have gotten it enough under control to that it isn't a problem any more (during a 1 hour workout, I will typically get this gap/lag 0-2 times...and that is not a problem for me...at least compared to what I experienced 6 months ago, where I was lucky if I could hear 10 seconds without any problems).
The stuttering problem seems to be permanent now... Luckily I have a HP hx4700 (which has a Broadcom bluetooth module) and works perfectly with my Jabra HT620s. Anyone using an A2DP ROM other than Qtek? I'd like to try a different ROM to see if it would make a difference.
only a second of sound
i use the qstarz bt stereo headset (http://www.qstarz.com/products/bh-q392s.aspx) and it works fine for phonecalls, but when i set it for wireless stereo and start a media player (TCPMP, WMP, Pocket Player...) i mostly only get sound for one second and then it shuts up. the players keep playing, the buttons on the headset can pause, resume and change tracks but there is no sound at all.
i get full wireless stereo playback occasionally, but i can't figure out what differs from time to time.
i applied the above patch with no success. anyone has a thought on the matter?
Ariel.
richardlai said:
The stuttering problem seems to be permanent now... Luckily I have a HP hx4700 (which has a Broadcom bluetooth module) and works perfectly with my Jabra HT620s. Anyone using an A2DP ROM other than Qtek? I'd like to try a different ROM to see if it would make a difference.
Click to expand...
Click to collapse
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
edit:
I use the latest OFFICIAL Qtek 9000 WWE ROM. (Without the ExtROM though ) And i did not use any patches regarding A2DP or Bluetooth.
this is what i tried, many times. i get the activesync sound, sometimes from the speakers, sometimes in the headset, but almost always only one second of sound afterwards.
i found that by pairing the headset to the universal by pressing and holding the green button on the headset untill the universal recognises (doesn't take long) gives better results.
pairing it by the instructions of the headset (putting it in discover mode, and then searching for a device with the universal) will give me the one second sound almost every time.
Biffert said:
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
Click to expand...
Click to collapse
Well, this has ALWAYS been the sequence I use (and I don't think you can do it in any other way). The real problem here is either the buffer memory or processor load.
richardlai said:
Biffert said:
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
Click to expand...
Click to collapse
Well, this has ALWAYS been the sequence I use (and I don't think you can do it in any other way). The real problem here is either the buffer memory or processor load.
Click to expand...
Click to collapse
Then there is no A2DP problem, the only solution is to lower the overal systemload. Stop all programs you have running, disable every today plugin that need frequent updating (memory, battery meters etc.) Free up as much RAM as you possibly can. I have AT LEAST 16 mb RAM free when playing music via BT.
I have a Cavalier with it's original WM6 (not 6.1) ROM and I am having some stereo bluetooth headset issues and wondered if anyone has a solution.
On my Jabra BT320s (with Latest firmware) as well as my Motorola DC800 I have issues with it playing consistently. From time to time it will start to loose it's pitch. This sounds a lot like an old record player with the disk slowed down. This will continue for some time and then be ok for a bit again. It can also have drop outs from time to time as well. I've tried insuring nothing is running in the background, and even turned off the cell to insure the phone is not getting busy. In reading around the web this is not an uncommon issue. Has anyone had this problem and found a solution? Is the BT stack in 6.1 better than in 6? Is my solution to upgrade to 6.1? Could anything else be the cause? This never happens with a wired headset btw ...
Thanks in advance for your time, I love my Cavalier. Probably one of the best WM devices I've played with to date!!
Sorry if I'm posting a question that's been answerred before, but I haven't been able to find a thread to this problem:
sometimes my Nokia BH-102 will disconnect in the middle of a conversation in the car. The only option at that time is to pull the TP2 from it's holder and put it to my ear.
Whether it's the headset or the phone, I don't know, but it used to work in combo with the old Nokia E60 I used to operate......
Chances are it's the TP2, but how to fix it?
Only 'tweak' was to install tomtom, but without the 2 dll's which have been causing some problems.
Has anybody experienced anything similar?
Bluetooth visor problem
I have had problems with my headset - Supertooth Visor One Bluetooth Car Kit. Not quite the same as you though - the problems I have is that when I make an outgoing call, everything works fine but when I recieve an incoming call the audio stays on the handset rather than coming out of the bluetooth headset - which means I have to pick up the phone. I also have installed TomTom 7 and I had to do the 2 dll fix as my bluetooth was completely broken otherwise. So I guess maybe TT7 is responsible in some way. Only thing is, I dont want to do a hard reset to find out!!
I'd already read about the Tomtom BT-issue so I cleared the 2 dll's out of the cab prior to installation.
So the originals should still be in use. BT is/was working and I have been synching using BT. That's not the problem.
There should be threads out here pointing you to the original dll's. you could past them over the current ones and see if it helps.
I experiencing the same problem, and didn´t install tomtom.
So now it looks like it's a problem in the TP2 then.
Hopefully a BT-guru can investigate? This is way beyond my capabilities.
In the meantime I'll know what to do if and when it happens: take a chance on the cops seeing it and issuing a ticket.....
I'm having a similar issue, my headsets plural, have this problem. It will disconnect but what is happening is the headset is shutting down. If I hold the power button on the headset it comes back on and will work again.
If it was one headset I would think it is faulty but I've had this problem with three headsets and the Bluetooth in my car.
Is it possible that the phone is sending a shutdown command? BTW I am using the stock TMOUS 6,5 ROM and have tried some of the cooked ROMS with the same effect.
Just wondering if anyone else the same problem here.
I have spend the whole morning tring to pair my Touch Pro2 with my Ford Mondeo (5 second job with the Iphone). I have finaly paired it after much F'ing and Jeffing only to find it is not clearing down properly when I end calls with the steering wheel controls.
If I use the phone to answer and make calls the handsfree works great. However if I use the controls with the car to navigate through the address book and dial from here the call is fine but never clears down. I have to turn bluetooth off on the phone to force the car to clear the call!
I had a similar problem with an old XDAII and loaded BTexplorer on to the phone and this cured it but I can't find BTexplorer for the TP2.
A tad frustrating because I was using a Blackberry before but banged on to everyone how useless it was so I have convinced the company to bin them all and go with these, how stupid I will look when the whole company fleet of cars are Mondeo's!
Someone please save my shame with some ideas or know where I can get hold of BTexplorer for WM6.5 or something similar.
I have noticed that winmo seems to be picky about how calls are made and answered with a BT headset (or radio for that matter).
Look in the menu for something about turning hands free on when in a call. Usually I just call voice mail. Sometimes this helps. While I don't have a Mondeo, I do have a few BT headsets and a BT radio in my car. Its not very intuitive, and it sucks, but that's winmo.
I just got my TP2 yesterday, after fighting with sprint for about 6 months and at least 6 junk TP1s and will have to do some experimenting with this new handset.
The most annoying thing for me is the crapshoot when answering a call winmo will sometimes not put it through to the handset. Leaves me shouting "HOLD ON A MINUTE!" while I fumble through the menus to get the audio routed.
If nothing else, I feel your pain. hehe
diggy said:
Just wondering if anyone else the same problem here.
I have spend the whole morning tring to pair my Touch Pro2 with my Ford Mondeo (5 second job with the Iphone). I have finaly paired it after much F'ing and Jeffing only to find it is not clearing down properly when I end calls with the steering wheel controls.
If I use the phone to answer and make calls the handsfree works great. However if I use the controls with the car to navigate through the address book and dial from here the call is fine but never clears down. I have to turn bluetooth off on the phone to force the car to clear the call!
I had a similar problem with an old XDAII and loaded BTexplorer on to the phone and this cured it but I can't find BTexplorer for the TP2.
A tad frustrating because I was using a Blackberry before but banged on to everyone how useless it was so I have convinced the company to bin them all and go with these, how stupid I will look when the whole company fleet of cars are Mondeo's!
Someone please save my shame with some ideas or know where I can get hold of BTexplorer for WM6.5 or something similar.
Click to expand...
Click to collapse
Try the solution in this thread: http://forum.xda-developers.com/showthread.php?t=591322
It has fixed problems with other car kits caused by the TP2's Widcomm bluetooth stack.
Thank you!
Thank you dwboston and the other guys, this fix worked a treat for me and most others by the looks of that thread.