Hi I'm new to the site, i had read a lot post about upgrading roms from different companys, i read people describe how good the a2dp quilty is, but the problems comes, i first upgraded the rom to T-Mobile , then i found there are a high pitch nosie, at first, i though it was just my earphone, after i changed it, it still the same, then i upgrade to the QTEK rom, the nosie still comes, the nosie comes as the singer start to sing!!! it makes my so dizzy, i had try to link my BT to my PC, but they sound much different! no nosie plus clearer sound!
the second problem is that when a phone call-in, the ringtone goes via BT rather than built-in speaker???
the third problem is if you set ur BT as both hands free/set and wireless stero, during a connected phone call, if you press any button on the dial pad, all the sound will gone, but the phone is still connected, i found this problem when i using my voice mail?!
also after i update to the non-O2 rom, my phone is no longer accept any MMS, i already config all the setting from O2, is just that i don't have my MMS acount appear on my mail box. i also try the .cab setting file too!
My A2DP BT is i-Tech S35
ROM Version: 1.30.77WWE (QTEK)
Radio Version: 1.09.00 (QTEK)
ExtROM Version: 1.13.188 WWE (O2)
Many Thanks!!!
Was it just me than having this problem???
- I've not the first problem.
- I've the second problem
- I never experienced third problem
:wink:
http://forum.xda-developers.com/viewtopic.php?t=46540
Click on the above link , download the file and run it on your phone, do not alter any of the options, just click next on everything it will fix your MMS problem
thx a ur advice coff... but it still doesn't work, plus i starting to think that the nosie might cause by my s35, due to the campasility.. (sorry can't spell)
Hi MicmiC901,
Yes, it probably is something "locally" with your phone/headset/area/etc, since I also have same experience as asci, meaning;
1. NO, don't have that problem
2. YES, I have same issue (to me this is actually OK, since when headset is connected, I WANT it to only ring in the headset)
3. NO, never experienced this problem
I use the latest Qtek ROM with AKU2 and A2DP, but have never experienced that high-frequent-noise-issue you mention with any other of the A2DP ROMs on my JasJar (TMobile Germany ROM, a custom-ROM from the forums).
so RonnyGydar, which bt headset u using @ the moment? i just try with my friends logitech bt headphone, it get worse than my i.tech, sound get Stuttering , so i think i better change a new bt, would u recommand moto ht-820?
Hi MicmiC901,
Sorry the veeery slow response...but now I have even one more BT Stereo headset...so then you get the "bonus" of even more info in my reply!
I have 3 BT Stereo Headsets, and here is a short summary of experience of them all.
HP BT Stereo Headphones (same HW as the Logitech ones as I understand).
Sound is good, clear, OK bass. Nothing exceptional, but I was very pleased with them. Sound could be a bit higher at the highest volume...if you plan to use then in noisy environments...but not really an issue...since they are quite loud.
Motorola HS820
Soundwise (clarity and bass) very simmilar to the HP ones...can't point my finger on any differences. But they seem actually a little less loud than the HP ones...so with these I struggeled to hear Podcasts when I sat on a bus going through tunnels. The HP headphones are slightly louder, I think.
Bonus of these are the excellent batterylife and miniUSB plug...plus the HP ones do not have a microphone, so the HP ones are only for music. So I would easily chose the Motorola's before the HP headphones.
One minus for me with the Motorola's are that they hurt my ears after a couple of hours of use. ...that at lack of "powerfull" bass, got me to look at the i-Tech BluePRO's...
i-Tech BluePRO
These have very good bass (and they sure look like they should have it too...pretty big earmufflers...with these, you look like you are working at a construction site or something, but the clarity of the sound is actually worse than HP and Motorola...they sound a bit fuzzy.
...but I still use these all the time...mainly for two reasons. One is the excellent bass (I like to listen to techno and trance...and then bass is important, the other is that they isolate outside sounds (due to the enormous padding), so I can have the sound as low as I prefer...and STILL hear all my music without disturbance from other sounds in the environment (like sitting on the bus in a tunnel, or at a noise Gym).
It also seems that there is quite a bit difference in how the different manufacturers implement BT profiles.
My Motorola and i-Tech BluePRO have problems with "Pause/Resume"-button on headset when used with my JasJar (Pause works, but not resume...or opposite...not sure which it was, dont have the headsets with me today)...but the HP ones does not (I tested them a couple of times, and the HP headphones worked all the time)!?
Re-connection after a time without use seems also to vary a bit. The Motorola I can turn off/on the headset, and they reconnect automatically to my JasJar. The i-Tech BluePRO's I must choose re-connect in "Bluetooth settings" on my JasJar every time I want to use them.
The "famous" "lag-issue" everybody experiences I experience with all my headphones in some situations...and it does not seem any better or worse among the headsets. It seems to also be affected by general radio disturbance, since I have a lot of problems with lag at work, but no problems at all at the Gym (which is good for me...since that is the place I am most happy with having my wireless headphones), and some issues at home.
Hope this was of any help!
actually i have the problem micmic is talking about.. it happened when i upgraded my wiz to a newer rom to get the a2dp function. eventually i do not have a bt.stereo -headset yet.. (coming in about 2 weeks) but i have the issues with the sound. it's almost like a bad bitrate or something? ..wierd it is since i remains even if i downgrade my rom. =/
Hi epluribus and MicmiC901,
Is the "stuttering" you both mentioning the same as I call "occational lag"?
IF it is...it you should certainly not have it when you do the following test;
1. Reset your JasJar/Universal (to clean memmory completely)
2. Started listening to music over headset with...
3. The Universal lying on the desk in front of you completely still 50cm from your face
4. You sitting completely still
5. No WiFi on close to you.
...this test is completely overkill...but if it STILL stutters in that "controlled scenario"...well then it must be something different with your Universal or headset HW. Cause I can walk around with my JasJar (also in areas I know there are 5-6 WiFi connections active...like my appartment), and even put the JasJar on the table and walk 5-10 meters away from it...and have no or at least nothing more than an "occational stutter"/"lag".
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).
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.
I have BTW had the exact same problems before with Qtek2020 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.
...so it can seem that HTC is getting slightly better on each new device...?
Hope this info can be of some use!
...but it might not...if my assumption at the beginning here is wrong, and your "stuttering"-issue is something completely different than the "lag"-issue I talk about!?
Related
I'm having several problems with my Qtek 9090
There's a rather loud constant high-pitched noise comming from the screen whenever it is turned on (which is when the device is on!). At first I though it was comming from the speaker, but the screen is definitely the source of the noise. It doesn't matter if the backlight is on or off.
People can't hear what I say when using the phone - it makes no difference whether I use the included headphones or just speak directly into the microphone.
I haven't been able to find a BT headset that works with it. They all have the same problem; The sound scratch so much they're unusable. I tried 3 different brands that all works well with my 2020!
The GSM link often "falls out" - even though there's plenty of link the phone doesn't work (nothing happens when I try to call someone). A soft reset solves this problem!
As you can see, I can hardly use the device as a phone at all I've had the device replaced once, but all the problems persists on the replacement.
Does anyone have similar problems?
1. No, don't have this problem. Strange that it happened on the replacement too.
2. Yes.
3. I have just ordered a jabra headset in the hope it will fix problem#2.
4. Yes.
These problems with GSM are a real headache. One of the primary reasons for buying the PDA2k was to consolidate my mobile into one device. I have seen other people experiencing such problems but from what I could gather, voice over BT worked much better. Have you updated the ROM since you bought it? I should know the answer to 3 today, if DHL delivers, and I can tell you I will not be a happy man if the answer is Yes!
Try a Motorola HS810 headset... works fine for me.
harry_mb said:
1. No, don't have this problem. Strange that it happened on the replacement too.
2. Yes.
3. I have just ordered a jabra headset in the hope it will fix problem#2.
4. Yes.
These problems with GSM are a real headache. One of the primary reasons for buying the PDA2k was to consolidate my mobile into one device. I have seen other people experiencing such problems but from what I could gather, voice over BT worked much better. Have you updated the ROM since you bought it? I should know the answer to 3 today, if DHL delivers, and I can tell you I will not be a happy man if the answer is Yes!
Click to expand...
Click to collapse
I've already tried Jabra Freespeak 250, which didn't work for me
No I haven't updated the ROM as I've been told by the supplier that no new version is available yet!
outz said:
Try a Motorola HS810 headset... works fine for me.
Click to expand...
Click to collapse
I also tried both a Motorola and a SonyEricsson BT headset, but I don't remember the specific models - they both scratched immensely
i use SE 60 and it works ok
As you said, the Jabra250 is pretty much unusable!
Crackling is not constant but goes in waves, even though I do not move.
Am at a bit of a loss what to do now... the device is great apart from this.
>> People can't hear what I say when using the phone - it makes no difference whether I use the included headphones or just speak directly into the microphone
yes PBT read my other post
I have the same problem!!
it is scandalous to sel an device with this big defect!!
Sony HBH-660 works good for me.
People say that they can't hear me when I use the handset, but I don't have any crackling, etc with the headset and voice is clear. You just never know if the headset is going to connect when the phone rings though.
sound from screen
there's a rather loud constant high-pitched noise comming from the screen whenever it is turned on (which is when the device is on!). At first I though it was comming from the speaker, but the screen is definitely the source of the noise. It doesn't matter if the backlight is on or off
Click to expand...
Click to collapse
I have this problem also, I was told to use the new rom but this has made no difference, Please let me know if you have found a solution
[/quote]
Guys,
the hissing coming from the screen is a power supply problem. keep swapping phones until it goes away! I used to build switching power supply and the hissing (in a system designed to operate well above 20kHz) is only able to be heared when unstable, inductor core or cap is broken. The hissing is very 'not normal'.
It appears that the Q9090 is standing out as having more problems than the MDAIII, one is the mic volume, most of the other phones are not complaining about this so there may be something with they way the Q9090 are updated or shipped.
With the Jabra 250, don't forget to pair it pressing BOTH the volume and phone button on the headset on discovery with the 9090.(On bonding, turn off headset, turn on again pressing both buttons)
Funny thing is, I had the cracking also. I deleted the headset in BT manager and paired it again as described above. Now it works ok.
Hi,
I bought a Qtek 9090 a few days ago and I also have the same problem with volume level. People can't hear me when speaking, either with the headset or base microphone.
Using a different headset doesn't help (that's even worse sometimes) but I didn't try a BT heaset (and I don't want to as it would raise potential connection problems). I'm going to contact Qtek for support on this...
Pierre
I too am having problems with the Jabra 250 BT headset and my SPV M2000. The Jabra 250 worked fine on the XDAII but is terribly crackly on the newer model.
This is even when pairing it with the enhanced pairing of pressing Volume Up and Phone button together to pair.
Any ideas?
qtek 9090 bluetooth problem
Hi All,
I have new qtek9090 with cellink bluetooth headset. It is work normal, but i am loosing connection to headset each time qtek go to stand by mode. I need to switch off/on the bluetooth in order to restore the connection. Any ideas?
I often get a message stating:
"The Bluetooth Radio failed to turn ON due to insufficient driver momory available. You must perform a normal reset before you can turn ON the Bluetooth Radio."
Does your device also give you this message?
Is it also using the Broadcom "Bluetooth for Windows CE BT-PPC/PE Version 1.0.0 Build 2200"?
Interested to know if you have the same problems with the same bluetooth driver.
same problem
My qtek 9090 shows te same problem
This is a known problem with the Blue Angel, unfortunately, until they bring out a fix, all you can do is a soft reset.
upgrade
hi all,
how can i get updates from www.imateclub.com?
I can't register there, because I have qtek 9090 and not i-mate
thanks
O2 Sourced info on which BT headsets work
See: http://www.my-xda.com/downloads/Other_Bluetooth.pdf
THE PDA2K is a TERRIBLE MACHINE!
SSSoo many bugs....
1) BLUETOOTH JUNK
Bluetooth (after their so called patch), still headset causes it to turn on repeatedly draining your battery in no time. So unless you are connected to a powersupply, the bluetooth headset is useless cause I have to turn off the bluetooth anyway (if I want battery). Yes, I know it's been discussed many times, it still amazes me everyday.
2) ALBUM MOVIE PLAYER DOESN'T WORK AFTER BLUETOOTH PATCH
yep, I've made many tests, clean hardreset machine with no bt patch = I can record video and playback video (MP4) with no problem. Now after installing the BT patch, clicking on the ALBUM app or clicking on PREVIEW after fliming a video in mp4 will freeze the machine for about 5 seconds, and then soft reset it automatically. I've hard reseted twice to check and it's obvious the BT patch ruins it. Mysteriously, it sometimes does work even after the patch. I just wanted to show off my machine today and got laughed at (with good reason!) by a P900 user.
3) CASE IS USELESS
The case that comes with the machine is a joke, it pressed all the buttons even if you almost don't touch the case. They should have left alittle padding. Locking the keys is a must.
4) MORE BLUETOOTH ISSUES
I get repeatable bizzare errors of "memory problems" with bluetooth, and I need to reset the machine (ain't it great?). I also got twice a message about my BT expired.. LMAO. more resets. I actually thing about mapping one of the primary front keys to do a soft-reset.
5) BUILT-IN FAX SOFTWARE IS RUBBISH
A friend of mine tried it numerous times with no success. At clubimate they told him it doesn't work properly. (So why the hell did they put it there?)
6) POWER BUTTON TOO NEAR THE STYLUS
Happened to me several times that when I try to pull out the stylus, it pressed the power button and poweroff the machine. (bad human engineering here)
7) MORE BLUETOOTH MANIA
Amazingly the BT Headset (I tried 3 different models) cannot function for voice recognition, recording or hearing prompts. Seems the driver doesn't support it. If it did, the voice recognition with my Logitech new headset could have been better. Car BT hands-free also don't work for anything else than strictly during a conversation. I almost purchased a Motoroal Handfree BT Car set because I thought I could also use to hear navigation with my GPS Navigation software. I can't gear prompts cause again, it only functions during the conversation, lously.
8) TERRIBLE MICROPHONE DURING CONVERSATION
I've had several people complaining about not hearing me at all while I use the PDA2K directly (no BT headset). I have to should and hold the machine funny close to my mouth. Oh, and setting the microphone AGC gain control to Enable, does NOTHING for increasing microphone sensitivity, it only works for voice recording/notes taking.
9) OK, SO AT LEAST SET THE MICROPHONE AGC ENABLE FOR NOTES TAKING RIGHT? WRONG!
For taking voice notes or recording conversation, setting the microphone to AGC is a must or else you will hear almost nothing. So you Enable it out of no choice... But OOPS.. Now you find out the Voice Recognition software (Both Microsoft Voice Command or Fonix Voice Central) will disable it back, voice recognition software don't work well with the AGC gain enable. So.. you have to choose here Notes taking? Or voice recognition?
I have the machine just about two weeks and already got tired of it. It is a game, it's not a professional machine that you can actually work flawlessly with. Like a delicate toy, far from being a sturdy trusted pocket pc. Don't get me wrong, I'm a gadget freak, and I am willing to 'eat it up and shut up' but this is just to much. I've had a Cassiopeia E-125 for 4 years !!!! And Wwoooff.. ONLY now I can truly appreciate the Casio, 4 years and worked perfectly even though I dropped it many times, slept on it once, hit it by mistake and so on. Never failed me, and I didn't even knew what the Reset button looked like!
I'm truly disappointed... You get many features, but you pay the price of total instability and absolutly horrible amature like support from the HTC guys. No matter how many bugs other can find on iPaqs such as the 6315, I doubt it can reach to the extent this machine has.
:evil: :x :roll: :?
you are the weakest link...
goodbye
Well, since 3 of your 9 are bluetooth and 1 is the case, I think that says good things for the phone that you couldn't come up with any more...
I have the Sprint PPC-6601, which is basically the same phone with no wifi, but with fast 'vision' internet access...
I notice the bluetooth issues too. I have the zenphone profilier, and only turn bluetooth on when I am actually using it, in the car, for instance...
Other than that, I haven't had your issues. Power button seems fine to me. Callers report hearing me loud and clear, and I can hear them extremely well (it's the first phone I've had that can be made 'too' loud...)
Fax/Album/Recording. Haven't tried the fax. I use Resco for Album and recording, as the internal apps are really just 'lite' programs.
For my money, this is a great phone, and I'm very happy. Will be 100% when the get bluetooth working properly..
- Regards,
Ben
ben1000 said:
Well, since 3 of your 9 are bluetooth and 1 is the case, I think that says good things for the phone that you couldn't come up with any more...
I have the Sprint PPC-6601, which is basically the same phone with no wifi, but with fast 'vision' internet access...
I notice the bluetooth issues too. I have the zenphone profilier, and only turn bluetooth on when I am actually using it, in the car, for instance...
Other than that, I haven't had your issues. Power button seems fine to me. Callers report hearing me loud and clear, and I can hear them extremely well (it's the first phone I've had that can be made 'too' loud...)
Fax/Album/Recording. Haven't tried the fax. I use Resco for Album and recording, as the internal apps are really just 'lite' programs.
For my money, this is a great phone, and I'm very happy. Will be 100% when the get bluetooth working properly..
- Regards,
Ben
Click to expand...
Click to collapse
Actually, I found dozens of similar complaints at the clubimate forums (as well as here) In particular, the so many BT complaints, microphone. I've used WINCE ever since it was version 2 16-gray scal on an old casio with 8mb of ram (gee that's history), I just wish HTC could have made a good job of actually making all the features work. The potential is super, and I guess (and hope) that most of the bug can easily be fixed with a decent programmatical procedures. You'll see dozens of complaints at the clubimate forums, lots of disappointed customers. Only HTCs fault for not making enough QA (or some say none)
To use the fax you have to have it enabled by your mobile provider (if they provide it at all)
You sound frustrated....sell it now and move on... Oh thats right there is NOTHING else like it out there.
When they get the bluetooth issues solved (and Im sure they will) you can then rebuy it.
BlueTooth is going to stuck until Microsoft can integrate a decent stack into the OS. It shouldn't be the job of the phone manufacturer to have to do that.
But it should be their job to properly QA it prior to selling it to their customer base.
Hi
I see all your issues and a load more. This device has the capability to be excellent. I hope that they fix the bugs promptly, and that the manufacturers take the bug fixes, and release appropriate updates shortly after.
Currently, O2 are sending out standard replies to all queries regarding this device (O2 XDA IIs) basically they say 'if you're not happy, send it back for a refund'. This is exactly the same as I got when I phoned them.
They keep offering to replace it, but that will not help to solve a software issue!
They did (eventually) fix most of the issues on the XDA II (although bluetooth still does not work correctly on that device either). I hope that the IIs gets the same treatment (with working bluetooth as well!)
Perhaps we should just ignore new releases, run 1 release behind... When the XDA 4 comes out, buy the 3, buy the 4 when they ship the 5 !!
We, the consumer are partly responsible for the manufacturers rushing products to market well before they are ready I suppose.
I checked out the reviews of the XDA IIs (and its friends) before I bought it, they did not have a bad word to say about it. All I can think is that the reviewers, either A) never even clapped eyes on the device, or B) never used it in anger, or C) were only allowed to review it if they said nice things about it. If I had seen a review that listed all the problems, then I would have waited a while --> and probably bought the Motorola MPx instead (which is probably just as bad, and ships with a *stupid* 32MB memory!!)
Nigel
I wish more companies were like Nebula-Electronics.com They released a freeview card 2 years ago, and have been improving upon the software ever since and offering it to customers for free. Their releases are spot on, they respond to bug reports, and they *beta* test the software with end users before they actually release the new version.
The nebula is is the best bit of software/hardware that I have ever bought... Unfortunately, most companies are not like nebula and simply move onto new hardware products without first having fixed the issues in old products.
Nigel
I bought a PDA2k from eXpansys USA, and was NOT able to repro the problem with the video camera. I was able to take video and play it back without any problems at all.
Perhaps you have a truly defective unit. Can you try returning it under warranty?
When the MPX finally ships, (which must be soon as Motorola have finally officially announced it last week and said it will be available to Asian markets this month and Europe Q1 2005) I think we're really going to see what a buggy device can be. I can't see that it's possible to run any software concurrently with wifi or bluetooth with only 32Mb of RAM and wm2003se taking up more than a third of that from bootup.
Still, the form factor is the appeal of the MPX and I can't wait to get one.
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.
Heya,
for a long time i have been looking for some decent bluetooth stereo headset.
now it has come down to two models. well, actually one only
my choice: motorola s9
and the second possibility: Motorola T820
from reading the comments on amazon on those devices i realize that my phone needs to be A2DP compatible to get the best sound out of the headset.
i use s2p as music player and i know it is A2DP compatible... but is real question is: is my phone (HTC P3300 WM6) compatible with this tecnology
also: if you can suggest any other good headsets, please do so.
key features i seek:
- able to use on my phone and pc
- a2dp
- good sound and microphone quality
a2dp not working
Hi,
I have HTC artemis. I recently purchased wireless bluetooth stereo headsets (Jabra bt325)
I cannot connect it to use as wireless stereo. Its working fine as handsfree. After pairing, I cannot see wireless stereo option. Its Greyed. I know that artemis is A2DP compatible.
But i am sure that headset is fine because I tested it with n95 and it worked fine.
Please give me a solution.
Try this:
Start - settings - connections - bluetooth - and add new device
If your headset is already added, use your stylus and press on the bluetooth headset name until the following menu comes up:
Edit
Delete
Set as Hands-free
Set as Wireless Stereo
Choose no. 4
yes it is.
I'm using Dopod M700 which is the P3300 w/o the GPS module.
It works with dell BH200 BT stereo headset and also the o2 BT stereo earphones.
It works on joint stereo in WM5 and since its now running WM6.1 its real stereo.
Dell BH200
Hi thanks for the suggestion even after setting the Bluetoot head set as "set as Handsfree" it did not work, as soon as I receive or make a call the head set goes off, looks like its some compatibility with A2DP not sure, if some one has done some development or found a patch to make this work would be a great help
sameerbs said:
Hi thanks for the suggestion even after setting the Bluetoot head set as "set as Handsfree" it did not work, as soon as I receive or make a call the head set goes off, looks like its some compatibility with A2DP not sure, if some one has done some development or found a patch to make this work would be a great help
Click to expand...
Click to collapse
might be a specific problem of your headset model.
i use a motorola s9 and it's quite nice. fits nice, does not disturb after hours, controls work fine, calling works fine...
BUT (and there's always a but) it has some major drawbacks i found out. while it's still nice to listen music without wires, i encounter this problems. which MIGHT be due the phone, not the headset... but i have no way to test that.
so, basicly, P3300 + motorola S9 through A2DP:
- insides works like a charm. phone in my belt, headset on. music cuality nice with some small music interrupts every now and then (maybe once per 5 minutes). phone calls nice and i can hear and they can listen me well.
but my oh my when i get on the street...
- constant music interrupts every 15 seconds. i have hang the phone around my neck so it's where my chest is to not get interrupts so often (still get one every 2-3 minutes)
- as the mic is where the ear is, if i have a call, it's impossible to hear me due the background noise. this also applies to the underground/metro. it's not that bad in a bus
and well. without A2DP enabled my music player uses so little resources the phone still works fine...
if A2DP is enabled, the phone gets REAL slow and the battery drain is MASSIVE.
when this motorola S9 break... i'll get another model to test. and when that breaks i'll probably get back to some nice wired ones (unless the CPU issues and the battery drain on the phone gets solved) ... but maybe i actually change the phone before that happens. who knows.