Develop Bugs

Several serious problems with Qtek 9090

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

stereo bt but mono sound

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.

BT Audio re-direction

Having successfully installed TomTom6 and Skype, I really want to get the audio re-directed to the BlueTooth headset. I am currently trying BlueMusic since this appears to be the only solution that also re-directs the mic input so that Skype can be used via a BT headset.
However, it's not working as it should.
Pressing the headset button re-directs it for a few seconds, then the Voice dial app appears and audio goes back to the speaker.
Pressing the buttons in BlueMusic's Today plug-in switches it away from the speaker, but it doesn't get to the BT headset which remains silent.
Awaiting a response from Teksoft about this, but has anyone here experienced this or even better know how to fix it?

No-one seems interested, but I'll update this thread in any case.
Teksoft released a newer version that works correctly. I'm so impressed I bought the product.
Need I say more?

UKenGB said:
No-one seems interested, but I'll update this thread in any case.
Teksoft released a newer version that works correctly. I'm so impressed I bought the product.
Need I say more?
Click to expand...
Click to collapse
I remember I got it automayically when I was on the Dopod ROM Try that and see. I tend to listen to radio in the car so TomTom on BT is not a priority My skype usage does not waarant the extra software

Bluetooth headgear disconnect mid-call

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.

bluetooth paring problems WM6.5

Yesterdaty I updated to WM6.5 and now try to get everything working again. Somehow my TP2 won't pair with my bluetooth carkit anymore. With WM6.1 this was no problem. The phone still pairs perfectly with my computer (also bluetooth connection) so I think the bluetooth connection is ok.
When parining to my carkit it finds the device, then I have to enter a password on the TP2, and after that it just sais "pairing connection failed", and it will not work. I am sure the password is not changed since yesterday. I tried it several times. I do not know what to do anymore. Could this be a setting somewhere? I get the feeling my password is not send properly but have no idea.

Meanwhile I tried pairing my carkit with another phone and no problems there. So my conclusion is: something has changed with bluetooth, updating to WM6.5 which makes it now impossible to pair my TP2 with my carkit.
Is there maybe a programm for the TP2 which give me more controll over bluetooth (like maybe go to an older standard)?

I have exactly the same problem as you

good to hear I am not the only one. Hope someone will come up with a solution for this.

I did nor observed any issues when pairing my TP2 after reflashing to WM6.5
There is another issue however - I can not hear any voice until it is charging.
Unplugging of the charger fixes this issue immediately. Horrible...
Seems, HTC guys are saving money on testing by using us as Beta Customers.

Would a custom ROM be a solution for us?

I updated to the "energy 6.5.1 rom" and guess what..............
The same problem. The rom is very nice, but my TP2 still won't pair with my BT carkit which is very big problem for me.
Is there maybe a way to downgrade just the BT part of a rom to WM6.1. I read on different forums there is something that is called a BT stack. Could this be the problem?

I have a ton of problems with bluetooth pairing now. However, I don't know whether it's the fault of 6.5 or the Tilt 2. Here is what I am experiencing...
- On car deck or headphones, the skip buttons don't do anything
- on car deck or headphones, I have to disconnect Stereo Audio and then reconnect to actually get sound. It NEVER works when it auto connects.
- Music will do a brief skip when you shut the screen off
- Stupid message about volume control every time it connects (resolved by switching to custom rom)
- SMS or any kind of alert tone now turns music way down so that the tone is the only thing you hear. Which is super awesome when I'm driving my drunk friends around and they are singing along to a song when suddenly it mutes so everyone can hear my incoming text message.
Not a single one of these issues existed when I had my Fuze.

Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM

orb3000 said:
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
Click to expand...
Click to collapse
No I do not think so, because I used the official WM6.5 with the same problem. Does someone know a way around this issue. I strongly believe that if only I could pair I have some options to work with it (in 6.1 it worked like a charm). If I only could pair without having to send the passkey it would be great step forward. I presume with sending the passkey, the bluetooth of the TP2 sends out other "rubbish" that confuses my carkit.

My problem is solved and guess what, it had nothing to do with my TP2. The problem was my carkit. It has a maximum number of bluetooth devices (5) it can pair to and the last one (the WM6.1 version of my phone) had been reached. So a hard reset on the bluetooth carkit and the problem was solved.
Well, at least I now know how to flash a rom to my phone and I think I learned more about the phone reading through all the forums. Thanks all for thinking with me on this problem!

Does anyone else still have this problem?? I have removed all the devices from my car and continue to have the same pairing error just after entering the passcode. Stock Spint ROM worked great, but multiple 6.5 upgrades don"t pair..............suggestions/ideas??????

bluetooth settings, advanced, enable beam data exchange,check the box

Interesting.....I actually found a fix. Instead of pairing the phone with the car, I paired the car with the phone. I didn't even know that this was possible, but it did the trick!