Hi all, anyone here using bluetooth headset please help me. I am using MDA Pro with Motorola HS820 (mono). It works well with bluetooth turned on by comm manager but I recognised that it eat the battery quick. I try to use Pocket Zen Phone with communication setting of BT to: BT turn on when on Call (MS). That setting will turn on the BT when the phone has a call, but the connection with the BT headset is not smooth, sometime it doesnt connect. My question: is there any way to set BT of Universal to 'Auto' mode as SE phone? I missed my last SE P800 phone for that feature, save battery while still connect well to BT headset. Any help will be highly appreciated.
PS: sorry for my English because I am not native
I use dayly my jasjar with a sony ericsson hbh660 and battery is no problem at all. I tryed pocketZen few months ago, but it didn't work for me. After alla if you can turn bluetooth on on incomin calls, you can't do anything if you want to voice dial throu your headset.
Thanks for replying. I see the battery will last longer if I dont turn the BT on. Voice dialing also dont attract me because I just make 2-3 calls per day. Still looking for any software could turn on the BT on call smoothly. Any advice? TIA.
http://forum.xda-developers.com/viewtopic.php?t=60832&highlight=battery
Menneisyys
Posted: Wed Aug 30, 2006 09:52
Subject: Power consumption measurements of the HTC Universal
--------------------------------------------------------------------------------
It was a few days ago that I’ve published some test results of the HTC Wizard (a.k.a. i-mate K-Jam, T-Mobile MDA Vario, Qtek 9100, MDA Vario, XDA mini S, SPV M3000, VPA Compact II, Dopod 838), Bluetooth and infrared power consumption-wise. Now, the HTC Universal follows suit.
Bluetooth
First and foremost, the case of the Universal seems to be very similar to that of the Wizard: that is, it’s almost impossible to measure the additional power consumption of the Bluetooth module. The difference between the switched on and the switched off case was 1% (at most!) a day (if at all).
This, incidentally, corresponds to my measurements of the BT unit with the PDA switched on. According to my measurements, the BT unit burns between 1 and 2 mA’s in those cases. This, as the device has a 1620 mAh battery, corresponds to between 800 and 1600 hours battery life alone - that is, not taking into account the need to power the dynamic RAM, which is pretty much the same as with the HTC Wizard, which is around 1.25 mWh corresponding to about 2% battery level drop/day (don’t forget that the Wizard has a smaller, 1250 mAh battery; this is why it had a bigger, 2.5% battery charge level drop figure).
Related
I have purchased an O2 XDAII in Oz which is loaded with the 1.66 ROM. I have tried connecting two headsets to the phone over bluetooth with many problems.
Both seem to bond ok and work initially but later they fail - the XDAII doesn't respond to anything I press on the headset. Or the XDAII does respond (answer or end call) but no-one can hear me either through the headset or the phone.
Deleting and re-bonding seems to temporarily solve the matter. But if the XDAII goes to sleep and comes back on it stops working. Will also just stop working for no reason after a call or two is made or received.
I have tried installing the bluetooth tools which is cool because the XDAII can recognise some of those extra headset profile functions (like redial) but I still get the same problems as above.
Tried Plantronics M3000 and Motorola HS801
What can I do? Is it this Bluetooth stack problem from MS I have read about? Do I need a ROM upgrade? Do I need Widcomm something installed on the XDA II? I don't know how to do any of these myself. Any kind advice from a pro is appreciated in advance.
When you installed bluetooth tools did you delete any bonding and pairing of devices beforehand? it can make a difference if you havent done this.
Yes. I tried it twice thinking that maybe I might guess a way to make it work.
First I deleted the bonds after installing BT Tools and then rebonded.
Then I deleted the bonds before installing BT Tools and then rebonded.
I spoke to my Telstra dealer again today and they received a list from Brightpoint (a distributor) that matches various headsets against various PDA's available in Oz.
Not all BT headsets will work competently with all PDA's. The M3000 is marked as NOT compatible with the O2 XDA II available in OZ. So was the Motorola too.
I am now using a Hello II headset which so far is fantastic (very small and comfortable to wear) and is working with no modifications to the XDA. I will post back in a week with a fuller review. I'm going to re-install BT tools and see if that make a difference with the available functions.
Anyone else wanting to test these out in Perth, WA, (Australia) - they are available from Communications Plus.
Help
I can stop the sleep mode ... I have a MOTOROLA HS-801 Bluetooth Headset
Help
how can I stop the sleep mode ... I have a MOTOROLA HS-801 Bluetooth Headset
I had a problem with my Plantronics M3000 too so I called Plantronics themselves who said that the problem is with the phone, not the headset. It's a compatibility issue with the software.
Unlikely to be any fix, at least not in the near future.
These stacks I believe are newer than the Widcomm 1.5.0 series
I think Broadcom reset the version 1.0.0
These are Broadcom 1.0.0.3000 and Broadcom 1.0.0.3500
Build 3500 is slightly unstable but newer.
These came from an i-mate patch for a PDA2K.
DO NOT USE on an i-mate PDA2K (get the orginal unhacked ones from Club i-mate).
I removed files specific to that phone and basically left just the BlueTooth stack.
Recommend a HARD RESET before installing.
I've tested theses patches on a Sprint PPC-6601 (Blue Angle CDMA phone).
Do not do a restore of a backup before or after installing this because it may restore incompatible configuration files that may crash. Build 3100 is more robust against this problem.
Hey Bro
These two are for the Qtek 9090/Xda IIs or Xda II?
I am running 2.20CHS translated with Radio 1.18 and have been unable to get this stack to work. Has anyone tried it?
The ones I posted above are hacked by me to work on the CDMA version (Namely Sprint PPC-6601).
The ones referenced in this reply below are the original patches I started with that came from i-mate club. The offical phone name that the patches are for is "i-mate™ PDA2k" (GSM Slide out keyboard). I don't know how well they would work on the Qtek 9090.
Build 3500 http://www.blueridge.net/dereck/bt/PDA2k_Bluetooth_Fix.CAB
Build 3000 http://www.blueridge.net/dereck/bt/new/OEM_WWE_122_008.sa.CAB
Yes, good link but already bad quality with all bluetooth headset.
It's a shame.
It's a shame you don't give more details.
Which phone, which patch and what happened.
Works great on my phone.
I'm using the 3100 patch from the first post in this thread on a PPC-6601 with a HBH-300. Installed on top of a HARD RESET. That has Build 1.0.0.2200.
It's almost working perfect. Once in a great while if I go out of range for a long time I just toggle bluetooth and it reconnects immediately.
Dial Up Networking and Active Sync all work.
No static. No dropouts. Will go to sleep and wake up and still be connected.
I think that the "shame" was not for you but for imate as their patch don't solve all the issues. Maybe only a bad english ?
Tried on Himalaya_SE 2.06...
I'd merged the files from 2.02 and 2.06 and get a fairly stable handsfree, but I saw your files and got greedy... :twisted:
hmmm, it didn't work though. The installation freeze at splash screen after i cold reset the device.
I believe that there are still device specific entries in the cab files, but it's beyond me at this moment. :?
yes sorry. Just bad english because i am french
This website is wonderfull and a lot of information
But i bought a qtek 9090 (850 euros) and i realize that they sell some device with a lot of bug
Here is my qtek config
qtek9090
Patch fr bt 3000 or 3500 (it's the same : they are bugs both for headset quality)
Windows mobile 2003 SE 4.21.1088 build 14132
rom 1.12.20 FRE
radio rom 1.02.00
ext rom 1.12.146 FRA
Ericson 300 works good but it's too big for me. I am not robocop
But each headset i have tested with bt 3000 and 3500 becomes bad when you stay more than 1 metter from your device. There is scrashesssssssssss in the headset. You have to stay front of the device (in car for exemple) and it works perfectly.
But when i work the pda stay in my bag or other place then quality is horrible
That's why i said it's a shame from imate.
I think there is a defect on this device. I don't know what can i do to increase the audio quality when you stay far from the PDA.
If somebody can help me ????????
But i can see that everybody have the same problem and can't solve it.
Waiting for another ROM. HIHIHIHIHIHIHI they are mad to sell this device like this.
If somebody can find bt 3500 patch from imate in french i am very interested.
Thanks to everybody from xda developer : a great site
yes sorry. Just bad english because i am french
This website is wonderfull and a lot of information
But i bought a qtek 9090 (850 euros) and i realize that they sell some device with a lot of bug
Here is my qtek config
qtek9090
Patch fr bt 3000 or 3500 (it's the same : they are bugs both for headset quality)
Windows mobile 2003 SE 4.21.1088 build 14132
rom 1.12.20 FRE
radio rom 1.02.00
ext rom 1.12.146 FRA
Ericson 300 works good but it's too big for me. I am not robocop
But each headset i have tested with bt 3000 and 3500 becomes bad when you stay more than 1 metter from your device. There is scrashesssssssssss in the headset. You have to stay front of the device (in car for exemple) and it works perfectly.
But when i work the pda stay in my bag or other place then quality is horrible
That's why i said it's a shame from imate.
I think there is a defect on this device. I don't know what can i do to increase the audio quality when you stay far from the PDA.
If somebody can help me ????????
But i can see that everybody have the same problem and can't solve it.
Waiting for another ROM. HIHIHIHIHIHIHI they are mad to sell this device like this.
If somebody can find bt 3500 patch from imate in french i am very interested.
Thanks to everybody from xda developer : a great site
Note that I attached to the first post of this thread Build 3500 release 124 of the i-mate patch stripped down for use on PPC-6601 and VZ6600.
BT problems
Just installed the 3500 fix.
It improves slightly on the Jabra 250, but not enough to actually use it.
It Stabilized the connection between my Holux GR230 GPS and the Qtek 9090.
Hope there will be a better fix.
Try to look at the connection, problem with the Jabra is that it fluktuate from just right to zero every other second.
Nice to pay 800 Euro for something that do not work :shock:
I've added new patches to this the start of this thread.
They work primarily on PPC-6601. Read the attached notes.
Hi mswlogo,
Can you help me if you know which version works on a win2003se translated from chinees on himalaya?
Thanks
That phone is quite different.
I think some other folks are working trying to get this stack working on other phones like yours.
Most of the patches above have registry scripts run in them that will very likely not work on your phone.
The other patches assume you are already running late version BroadComm Stack.
I have HP hx4700 and the Widcomm version is 1.5.0 Build 2000
which one is newest?
That's a really good question.
I'm amazed to see BroadComm on 1.5 instead of WidComm.
What are the dates on the bluetooth files \windows\bt*.*
They are generally around 12/9/2004
It's hard to say what BroadComm and the venders are doing here.
Bluetooth stack on h6315
I just found a new bluetooth stack from:
http://www.ppcw.net/?itemid=2210#cmt9543
Installed on my t-mobile h6315. Device was previously inoperable with bluetooth headset. Device would go into power standby mode, and if bluetooth was running when it went to sleep, it would freeze requiring a soft reset. Now device wakes on power button, with bluetooth running, as it's supposed to. Device also wakes on incoming call, reconnects headset in less than 1 second, and allows me to answer call on the headset buttons. All other headset functions are working as designed, and sound quality seems good. My headset is plantronics 2500. Also, this stack adds a profile in the list for A2DP (??) high quality stereo headphones. Don't have any of these headphones, so don't know if this works on the h6315. Also, don't know if this is the same Broadcom/Widcomm stack you guys have been working with.
Installation is straightforward - put it on the device and tap it. Reset, delete existing device pairings, re-establish the device pairings, and you're ready to test.
All that patch is supposed to do is add two new bt profiles to the pda2k.
* High-Quality Audio support (A2DP)
* Keyboard support (HID)
I'm slightly suprised you got a performance gain out of it.
h6315
It's definately fixed the problems with my device hanging when it goes into standby with bluetooth running and the headset connected.
Now my question is should I install the build 3500 for the 6315 listed above? It appears to be a newer release than this. Any thoughts as to the differences? I'm having a hard time following from the thread as to all the other changes that are in this .cab, and why they are there? Can any one help summarize that?
Hi all, I bought a Qtek S100 and tried to connect it with my BT GPS receiver (Falcom Navi 1). It didn't work properly and I suddely lost te BT icon on the lower right hand side of the S100. It hasn't re-appeared even after several soft resets?
Does the S100 have the sae BT problems with GPS as the xdaII had?
I use BT GPS and the only problem so far is that I have to re-pair them sometimes.
Try Start->Settings->Connections->Bluetooth to get to the same screen as you would get to by clicking the BT icon.
THanks for the reply. Which BT GPS do you use? and with what Navigation program?
Holux GR-231 and TomTom3.
I am having problem with Bluetooth GPS as well. I have 2, one is iTrek Bluetooth GPS and one is ArcoreTech Bluetooth GPS.
Since I have tried both GPS units, I am pretty sure it's i-Mate JAM's Bluetooth problem.
Instead of upgrading my ROM to 1.06.00 WWE, I should have tried it out with version 1.03 first. I upgraded from 1.03 to 1.06 as soon as my JAM finished charging. BIG MISTAKE!
I ended up usiing "Pocket Bluetooth Tool" to designate COM8 (for example) for my GPS. However, if I happen to soft reset or turn of Bluetooth, I would have to pair it again.
I read many article's on the internet and the problem seems to point to the MS Bluetooth stack (instead of Widcomm used in my i-Mate PDA2K - and by the way PDA2K works perfectly with my GPS units).
Hopefuly i-Mate will address this problem during the next ROM update.
So how come Loboman's holux works ok?
Loboman are you using a different BT stack?
I would like to guess that he uses ROM version 1.03...
Jazzedout said:
So how come Loboman's holux works ok?
Loboman are you using a different BT stack?
Click to expand...
Click to collapse
I use 1.06.00. All i do is that I tap on the BT icon, choose 'Devices', tap 'New...' and waits until the phone finds the GPS. Then I add it and pair it with the passkey. Then I had to scan all serial ports using a program that Holux supplies (I bet it works with any BT reciever though) to find out that my port was COM5 and finally I set my programs to use COM5. As I previously stated, I do have to re-pair them sometimes for some reason, but I can live with that.
I previously had an Acore unit which worked ok with my iPAQ 5450 (also MS BT stack) in WM2003. It took me all the way from northern Sweden to Barcelona in Spain last summer
I have not used Pocket Bluetooth Tool, but I have read about it. I think that it works without it so far. I also leave my BT on 24/7 since I don't think that it uses too much battery.
I hope things work out for you.
Absolutley no problems with Rom 1.01.01 Ger and Navilock BT-308 GPS-Mouse
I am not sure if the following has anything to do with Bluetooth but at least it cured my Bluetooth vs. GPS problem, for now.
On Club i-Mate's ROM update page, I found out that if the radio version is 1.10, then I am NOT suppose to apply the camera patch. After I uninstalled it, my JAM seems to work better with Bluetooth GPS units. My biggest problems were:
1. Once I soft reset my JAM, I have to re-pair my GPS units.
2. PrymeNav software took a long time to scan for GPS - and crashes sometimes when I designate already-scanned port.
3. Unable to hold two paired GPS units in Bluetooth Device List (though only used on at a time).
I have played with it after I uninstalled the camera patch and to this morning my GPS units still function well. Another key is to turn on the GPS unit and make sure it is linked (as indicated by its LED) - then turn on the GPS software. That way the hardwares are ensured to be linked.
As a side bonus, now I can perform Bluetooth Activesync on my Mac (via PocketMac software). However, I still require Pocket Bluetooth Tool installed on my JAM.
Weird!
I have a t-mobile mda II with the shipped rom that has the usual problem with the bt turning on and off.
I have tried most of the fixes posted, only way I could get a reliable connection was to plug the car charger in and leave the display on.
Have had a good trawl through the bluetooth sections of the registry and noticed a key hklm\software\microsoft\bluetooth\sys and key DisableAutoSuspend as shipped this has a value of 1.
I have changed this value to a 0 and done a soft reset for last 2 days my ck3100 has not lost the connection with the mda II running on battery in suspend mode.
may be worth a try
I'll give it a try on my TyTn this evening.
Sure hope this fixes the problem with the connection dropping all the time and BT turning itself off when using it on my Audi MMI BT carkit.
played telephone tennis between t-mobile and htc uk today.. Finaly ended up talking to a chap called John at HTC, who said they were aware of an issue and were in the final stages of testing a release rom update..
T-Mobile had never heard of the mda vario II disconnecting from bt car kits.
Have notice if i do a soft reset and do not connect back to gprs or 3g (so i have a x instead of a g/3g simbol ) the bt connection is much more reliable
woke said:
I'll give it a try on my TyTn this evening.
Sure hope this fixes the problem with the connection dropping all the time and BT turning itself off when using it on my Audi MMI BT carkit.
Click to expand...
Click to collapse
Still the same ... guess it will be waiting for a new ROM ...
Hi there, 2 questions:
1) The built-in GPS receiver turns OFF when switching the device standby - that's really bad for me because I like to log my GPS track when I go hiking. Is there any setting (registry? hack?) to tell GPS NOT to turn off?
2) I thought of a "workaround" to use my old Holux GPS bluetooth mouse. Pairing works, but after switching the device in standy mode, it TURNS ITSELF ON AGAIN!!! (after 3 seconds) - so battery is again burned. Is there any setting to tell the device NOT to turn itself on? It seems to be the case with any kind of incoming bluetooth connection, the screen goes on. That's really bad for me...
So anyone can help? Is it a generic WM 6.0 annoyance or an Ipaq 614 "special"?
Greetz B.
go to battery settings and let the device work with no time limt
then use this app
http://www.mobiletopsoft.com/board/1313/turn-your-pocket-pc-screen-off-with-awady-screenoff.html
(there are more freeware for this issue )