Hi to all!!!!!
finally patch are available!!!
I haven't yet tried, but tomorrow i will post my impression!
Ciao, ilVanni.
argh!!!
the patch was removed from website!!!! The support told me that are only a website test...
... it's back....
same file to download.
Specification of fix:
"i-mate™ is aware of the problems being experienced with the i-mate™ PDA2k Bluetooth. We are delivering a compete fix in two stages. The first patch increases the scan time of the i-mate™ PDA2k when searching for other nearby Bluetooth devices, thus improving other devices detectability. It should be used by customers regularly bonding with other distant devices. If the required devices are not identified after this extended period, pressing the scan again button will repeat the search. The second part of the fix will be released shortly and will improve the signal quality when using audio headsets. "
Great Thanks... I'm waiting for this patch!!!! The second one, I mean....
Now all we need is the A2DP profile supported and I will really start loving my MDAIII... I just got my B-Speech headset yesterday... didn't have much time to play with it yet though... I'd really like to get these HP bluetooth headphones too...
Treo
Yahoo!
but these 2 patches doesnt address the memory error message where the bluetooth fails to turn on... or am i missing something?
It does not address the device turning itself on all the time either. It is a joke. They are not fixing the things that are really broken.
yup i think they dont know how to fix it! ahhhhhhh refund refund! how can they even release the blueangel with such a flaw, how can their engineer miss that , did they not use their own creation for more than 15 minutes, they would hav saw the error msg
May not be IMate's fault...... of course they could have probably stuck with the lousy MS BT Stack.. might be less problems.. but anyway.. Its the OS..Remember the 32 process limitation that's still there? well. there is also a limitation on driver memroy.. I found this link that might help..
http://www.pocketfms.com/2-knownissues.htm
"The Bluetooth Radio failed to turn ON due to Insufficient driver memory available. Especially in PocketPC 2003 the Bluetooth Manager has been equipped with a lot of extra options like File Transfer, Audio Gateway and so on. If you go to Bluetooth settings and disable all services except for the Bluetooth serial port, a lot more driver memory will be available. Furthermore it's best to turn the Bluetooth radio on (and sometimes to connect to the GPS, configuration depending) prior to starting PocketFMS."
Doesn't fix the problem.. but its probably the same problem across the board for a number of devices out there..
Do a Search on Google for pocketpc "driver memory" .. you'll notice we're not alone... Then check the newsgroups.. the xda IIs has the same issue : http://groups.google.com/groups?hl=...%22&hl=en&lr=&client=firefox-a&sa=N&scoring=d
"disable all services except for the Bluetooth serial port, a lot more driver memory will be available"
THAT IS NOT TRUE, I tried to disable EVERYTHING and ONLY headset profile left and it still gives the error just as often. Sucks..... SUCKS...
umm.. U DON'T HAVE TO YELL AT PEOPLE.. All I was trying to do was pass along any information that might help the situation.... Also, make note that IMate is the only device to experience these issues.. HP and Ipaqs have the same issues....
I for one have not had any major problems with the bluetooth driver(knock on wood). I turn it on and off a lot and only rarely do I see the driver memory issue. However, I do see it more often when I turn on/off the WLAN driver for wireless access. I also tend to use GPRS a lot and have not had issues with the bluetooth with GPRS. I also use a bluetooth GPS unit... I have it bonded to an Sony Bluetooth HB-35 headset as well.
lol sorry, it wasnt yelling, i was actually just making main points bold... we are all suffering from this issue it's time for them to fix it.
Complaining to Carrier Devices will help a little...but the key point here is that this goes beyond them.. I think it has more to do with Microsoft and Broadcom(they bought widcomm). Microsoft and their stupid limitations on the pocketpc operating system and Broadcom committing to enhancing their widcomm drivers so as to not use heaping loads of memory..
I agree it needs to get fixed.. however, these fixes will take time and sometimes might take months to fix as you can see from all the other issues revolving around the Ipaqs...
I've got the same problems with the T-Mobile MDAIII - not enought driver memory, turns itself on, licence has expired, rebonding. These things really should have been sorted before now, considering that for the last twelve months we've all put up with similar problems on the XDAII.
This should fix the license expiry for the Imate. I received it via email from their tech support.. according to their tech support.. you can choose any of the key addresses...They sent it to me even though I never received the license expiry issue.
As for constantly turning on.. read someone on Howardforums on a possible workaround -> http://www.howardforums.com/showthr...50658&threadid=495366&perpage=15&pagenumber=2
Firebird, forgive me if this seems stupid, but what do i do with the file you posted after unziping it? Do i run it on my pda once or what....???? have no idea... THANKS. :shock:
Don't know if it works on an XDAIII.. but copy both files to the IMate PDA2k and run the executable.. then choose any address to update it.. I just chose each and every address and updated all of them..
and this will fix the license expired error msg on the pda2k ???
That is what its supposed to do. still wont' fix the driver memory issue.... I haevn't seen the license expiry issue ever since i applied the patch..
Related
Help !~
My O2IIs Bluetooth when I turn on it and go to susupend(standby mode?!) around 5 min ,then I resume the OsIIs again but the bluetooth will be turn off and on .....that have a big problems when I"m using the handset and have incoming call ! The OsIIs is going to resume ..... then the handset will be disconnect (because the BT was turn off automatically)~~But any problem when I do it in 5 min !! ......and I'm sure is not my handset connection problem!!
How can I Sovle it??
Thx ~~
First thing I'd do is ugrade to the latest ROM - you are still using the older one. If you still have problems after that it may be worth going from BT3500 to 3900.
If you don't know how to do either of the above have a little search around the forum. The new ROM is on the O2 site and there are numerous postings about the 3500 to 3900 upgrade all over this forum.
R
rakh1 said:
First thing I'd do is ugrade to the latest ROM - you are still using the older one. If you still have problems after that it may be worth going from BT3500 to 3900.
If you don't know how to do either of the above have a little search around the forum. The new ROM is on the O2 site and there are numerous postings about the 3500 to 3900 upgrade all over this forum.
R
Click to expand...
Click to collapse
Don't bother. I have 3900 on my IIs and it still does the same thing.
Thanks for rakh1 and kevinnugent reply~~
In fact ,I tried to downlaod and upgrade the newest ROM form the O2 website ! but my O2IIs is not buy in UK ! so....
In the mean time ,I"m also "cooked" (crack?!.. I don't understand what difference on "cooked" and "crack",haha~) the ROM by the "XDA3nbtool",but have the error message on installation ,that show "Radio image file checksum Error ",when I replace the original radio image,that will show the other image file checksum error.....
And I contact the O2 Custom Center in HK ,but they ask me to contact the Singapore customer service ,and said "they just have a repair service only!they haven't technical support ! "
OMG!! haha...a sick joke !! :lol: :lol:
Finally,the Singapore Custom Center still haven't the solution about this problem !... they just send the "bluetooth BT3500 update patch " for me to try (haha!!...) it can solve this problem or not !!
I have the same problem about BT disconnection
I posted an item about the same problem two days ago...
And the "official" technical support did the same to me: send me the 3500 BT Stack (and I found it in the web and installed two weeks before. Great technical support!).
In fact it's frustrating: I need a car kit that works well for my job, but impossible with Qtek. So, if I want to have a hands free car kit...I must buy another phone?.
Incredible for an expensive machine like Qtek 9090.
I have'nt tryed for the sort of multiple patchs of 3900, but I have no faith in it.
I you find a solution, please let me know.
Good luck!.
j.m.
Hey ~I have the solution now?!~and I tried it a whole day~any problem!
Firstly You must stop the "Auto Power Off" Function on the O2IIs,then go to:
http://www.pocketgear.com/software_detail.asp?id=14621
to download the "screenlock" (software) and install it ,after the installation ,you will not have the icon on the “Program file “ (haha…may be the software bug),than go to “file exploroe” ->”My Device”->”Program files”->”screenLock”->”screenlock.exe”,When you run it the first time it will be create the icon on “program file”,If you want to leave it, press the button 1 and 4 (Calendar and Message button on the IIs) simultaneously! Now !the Bluetooth will be connected every time ~
but I still hoped the O2IIs announce the newest rom update for the Asia user soon……..
By the way, when updated the BT3500 ,the “auto resume” problem will be solve or not ??because I’m updated to BT 3900 still no change…..
Thx
Cangratulations Alextly!
ScreenLock works fine, and although this is like killing flyes with a bazooka, it's the only solution that I know about it, and this convert this solution in the better one.
The only question I've got now it's about power consumption. This program Locks (turns down) the screen but, if I understood well, with the screen locked the CPU is sitill gorking "underground", so the battery life can be reduced (I must do some proves).
As far as I know, the BT3500 doesn't solve the problem (I installed and it's the same). I ignore if the 3900 it does, but I'm afraid that it will not. I have not installed because the 3900 I've fount it's some sort of different patches that and they doesn't seem to be very reliable. So I prefer to wait for official Patche. And as says "kevinnugent" seems not to work.
Let's keep the faith for official technical service (my faith it's going down for minutes).
Thanks for you're finding and congratulations. I would never find this one.
j.m.
ScrrenLock
ScreenLock it's not as fantastic as I though: it shuts down the PDA automatically when you are in no-battery mode (for exemple when you're using TOMTOM), and increase battery consumption dramatically.
j.m.
Interesting... I don't seem to have the same symptoms with my SX66 paired with my SE HBH-300 and HCB-30 (car kit). When the SX66 goes into standby, the BT seems to stay connected. If it does disconect with either handsfree, I just press the call pick-up on the handsfree and it re-establishes the BT connection within 2-3 seconds.
I'm using 3900.
Ken
SX66
In fact I think the connection must not be disconnected. And with my Qtek if you have good luck and re-establish the in some way, maybe you will hear nothing...
My car kit it's Drive Blue from Parrot.
j.m.
Hey, someone sent me this:
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=5802839981
From first glance, it totally looks like a hoax. However, is it possible that someone figured out a way to rewrite the ROM to replace the BT stack?? And why would it require the IMEI number?? I have some serious doubts, but I'd like to hear some others informed opinnions.
-Chris
Looks like a hoax. They do have 99 feedback, but then that probably means someone probably just hacked their account. :roll:
Here is the main wording from the ad, it I notice that nobody has bought one of these yet so no feedback on whether it works. Why would it be emailed to the phone if it is a zip file, it would make more sense to send it by normal email. I think the imei may be a protection device to prevent you using the patch on other phones, the patch will probably work only with that specific imei number.
It's very simple to install this. Just include your your IMEI number from your Siemens Cingular SX66 in the notes field when you make the paypal payment and I will configure and email you a specific update for your phone. To lookup your IMEI, just type *#06# on your phone. When you get my update, unzip the file and upload it to your cell phone memory. use the folder/file viewer on the phone to click on the file. This will install the update. Then unplug your battery for a few seconds, plug it in again and your update will be complete. Then remove any bluetooth settings, delete any profiles, delete any paired BT devices and rescan and pair your BT headset. It's that simple. This update takes about 10 seconds normally. I have never seen any loss of data or any other errors due to this update
Here are some quotes from the Cingular forum (where I found about this patch) on this topic http://forums.cingular.com/cng/board/message?board.id=siemens&message.id=10667 (at the end of the page)
From the author: arikinthecity
It has nothing to do with the wireless.
I am selling a software update the I created for the SX66. The problem is not with the headset that you are buying. It is with the bluetooth software on the SX66. Siemens doesn't want to spend the time and money to fix the problem. They will not even discuss it. They don't care. The reason is that they don't sell enough. This model will be replaced with another model soon and Siemen's will just move on. So will Cingular. That's why I got sick and tired of waiting and I created an update.
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=5802839981
Now you can buy the same update and install it on your phone in a few minutes. I'm selling the update on ebay.
Click to expand...
Click to collapse
From the author: RonNatalie
OK, I'll bite. I've just sent you the $4.95 and my imei.
I'll report here what I've found.
Click to expand...
Click to collapse
From the author: RonNatalie
Well, I just installed it. As near as I can tell with my Jabra 250 earpiece, it makes no difference. The static is certainly still there. I am pretty convinced this isn't a 'software' issue anyhow.
Click to expand...
Click to collapse
From the author: arikinthecity
Well that's your opinion. I know that this update fixes the SX66. I have tested it on a few SX66 and it makes a world of difference. The only earpiece I recommend is the Motrolla HS820 earpiece. Jabra BT earpieces create problems with other cell phones so I don't recommend them for the SX66. Anyway for those of you who are interested, get my upgrade. If you feel that my efforts should not be rewarded for a small amount of $5 then enjoy using your SX66 plastered to your face. It doesn't work well with any wired earpiece because it needs a stereo 3 conductor plug. It doesn't work with any BT earpiece with the regular siemen's upgrade.
If you are angry at me, your anger is misguided. I am trying to find a solution. It's Siemens that is not updating this phone properly like Audiovox, Sprint, Orange, and other brands are. HTC gives the tools to update it. They just won't bother because it costs too much.
Have a great weekend everybody. If you still want to get the update, just follow the link in my previous posts.
Click to expand...
Click to collapse
From the author: RonNatalie
It's not an opinion. It's a fact. As I stated the JT250 doesn't work any better with your fix than it did before. Your unbiased and intelligent appriasal of the situation is indicated by your childish response. I was willing to blow the $5 to find out, but since you're going to insult me you can deal with the Paypal complaint.
The phone works fine with a wired earpiece. I don't know what you think the plug problem is. I have used it with my Noise Cancelling aviation headset.
Click to expand...
Click to collapse
There can be 2 methods how to do such a fix:
1. Buy a 1000$ SDK from Broadcomm, and make a fix. But in this case 5$ is a very little price for such work.
2. Extract the audiogw.dll from one of the extended ROMs and give this DLL as his own "fix". In this case he is taking money for a free update offered by some operator. Imate offered such an update some time ago, maybe he is selling this update.
Just post it here, I think the IMEI number is bull****.
It's a fix isn't it, what does that has to do with IMEI.
Let the guys here extract the fix to see what has changed.
Greetz,
[email protected] :?
I think Mamaich is correct....this smells...
Why does he need an IMEI number? This has NOTHING to do with BT. I think he is offering an existing upgrade that anyone can download and in the meantime make money (to make it look "real") and getting your IMEI number (so he can sell it, and make more cash).
I contacted the seller...
I described my configuration (see signature). He told me that I would not see any benefits and suggested that the patch is to an earlier configuration (actually told me not to buy it!).
He claimed the IMEI number was keyed into the copy protection scheme that he was using.
Bottom line: if you're keeping up with the updates on this board, there's probably no reason to shell out the 5 bucks on an upgrade you already have.
goestoeleven wheare can I get the upgrade you have?
It solve the BT problem?
I'm tired of looking oktions to use my bluetooth headset clearly...
I have no Bluetooth solution
it still stinks... until we get an upgraded build, we're stuck with static...
If you haven't already done so, check out the SX66 Standardization Project:
http://home.comcast.net/~sx66-blueangel/
This is probably the best you can do with what's available to us today... (waiting for WM2005)
If any of you have the problem that BT goes sleep mode and disconnects your headset, you may try this. It worked for me today. (note: this is only a workaround to prevent BT going sleep mode. This will not fix any of the BT distortion)
Click on the BT icon located at the bottom right of the today screen. Select BT Manager. Then, DON'T click on the X (Close) button of the BT Manager. Just click on the Start > Today icon. This will hide the BT Manager, but it will leave it running on the background (so this way it does not go in sleep mode). I tried this morning and my headset haven't disconnected in all day.
Hope it helps...
Just to summarise:
Tap on the BT Icon on bottom right, turn on BT, tap on the headset to activate then not click the "OK" on top right, instead "Start-Today" ??
Isn't working for me, tried it 10 times. Everytime I send the PDA into Standy and reactivate it and I tap on the BT icon it shows that the BT is not active.
daaaammmmnnnn... It looked soooo good the have a small solution for it.
Saisoku-R said:
Just to summarise:
Tap on the BT Icon on bottom right, turn on BT, tap on the headset to activate then not click the "OK" on top right, instead "Start-Today" ??
Isn't working for me, tried it 10 times. Everytime I send the PDA into Standy and reactivate it and I tap on the BT icon it shows that the BT is not active.
daaaammmmnnnn... It looked soooo good the have a small solution for it.
Click to expand...
Click to collapse
after I posted that, it had worked that entire day and the next. Then at one time I did a soft reset, and followed the same steps, but sometimes it turn off the BT. So it works... sometimes.
pulsorock said:
If any of you have the problem that BT goes sleep mode and disconnects your headset, you may try this. It worked for me today. (note: this is only a workaround to prevent BT going sleep mode. This will not fix any of the BT distortion)
Click on the BT icon located at the bottom right of the today screen. Select BT Manager. Then, DON'T click on the X (Close) button of the BT Manager. Just click on the Start > Today icon. This will hide the BT Manager, but it will leave it running on the background (so this way it does not go in sleep mode). I tried this morning and my headset haven't disconnected in all day.
Hope it helps...
Click to expand...
Click to collapse
I assume that you turn on the b/t first,correct? So, tap b/t icon>turn on b/t>start>today ??? Is this correct?
Thanks...........Later 8)
but it's a small step in the correct direction :wink:
WM5 Bluetooth A2DP
Just to share what I found...it may not be significant....
I Manage to see a Universal/O2 Exec proto device myself that Supports A2DP. It seems that MS Bluetooth Stack is not that crap afterall.
To use Bluetooth Stereo, the device has a shortcut under programs that says "Turn on Stereo HeadSet" and I have successfully paired the WM 5.0 device with my iTech S35 Stereo headset myself on the spot.
Anyway after what I saw I felt that this can be achieved on my BA WM5.
Hence, I started looking into the registry and started enabling the AudioGateway entries.......Suprise!!!! my iTech S35 was detected to have HeadSet Profile!!! But wat was missing was the Audio headset s/w......
oh yah bear in mind when I was trying the above my BA WM5 was without the "Headset today" patch.
okay -- my gprs connection disappears after a day or so and i have to make another connection -- if i give it the previous name then i am told that the connection already exists. any way around
second problem is that i am using bluetooth headset and i can hear songs on it but no calls -- i can hear only a loud hiss. is it a known issue and is there a way aoound it??
The Bluetooth is a known, and very "annoying"problem to say the least. The trouble is that it is not clear where it comes from. It seems to affect also ppl who have upgraded their firmware...
And in the best end-user support tradition, neither the manufacturer (HTC) nor the distributor (O2 et al) even bother to acknowledge it or say if they intend to fix it.
Are you sure the GPRS actually dissapears? There is a known problem where it will not re-connect,if you put it into flight mode and then back out of flight mode you may find the GPRS wil re-connect. As for the BT issue, have you recently upgraded the rom? The 169 version from O2 had known BT headset issues.
I will answer both the questions -- firstly regarding the upgradation of the radio version -- i have not upgraded the firmware as far the bluetooth is concerned but i did upgrade the radio version. but the fact remains that i can hear the songs being played on the media player. what i am looking for is some tweak or a setting i am missing. i have already tried to uninstall and install the drivers again but i have had no joy.
regarding the gprs a soft reset is helping but yes -- it does disappear. and the fact is though i cannot find the first connection i made, i a told that i cannot make the next connection with the old name. can i know what speeds i would be getting over the gprs connection anyway??
thanks a ton
Before you even start tellin me that this question has been posted many times, read through...
I know we went through this few times but I just haven't found the clear answer.
The question is simple: can I use WIDCOMM on 8125? Or maybe someone knows a better way of communication between 8125 and LEGO NXT brick?
Any help will be appreciated.
Many thanks...
Your problem won't be the bluetooth stack. I don't believe that the NXT software can run on WM. If it does, then it should be a simple matter to pair with the LEGO device.
I know that NXT soft won't run on PPC... What I'm trying to do is to send BT message from NXT to the phone and vice versa. I know it works with simple Sony Ericsson, yet it does not want to work with my 8125.
The NXT box clearly says that the NXT brick supports WIDCOMM stack only.
My phone found the brick and the only available service is COM port. When the NXT sends the message it gets an error. When I do it all the way around ie. I pair NXT with the phone I get the same message...
Simply because I'm curious I'll ask: does anyone own or have acces to play with LEGO NXT?
you might have better luck using a more open version of BT with a phone such as the 6515 by iPaq, or the upgraded version. I've noticed that some of the BT options on the 8125 seem to be hidden, or restricted, unlike the iPaq versions (more protocols show up when paring, etc, with the HP). I'm not sure if Cingular is pulling a VZW move here with restricting BT profiles included in their phone... because that would be aweful.
That might explain your WIDCOMM issues.
the newer hps also use the widcomm stack I believe
Indeed. I've had HP 6515 and it did have WIDCOMM. However, I couldn't live with 240x240 screen resolution...
I've found some clues pointing that there is a way to somehow hack the registry and upload some crazy files in 8125 so that it uses WIDCOMM. However, the place I found it warned about some legal issues connected with this... (not that I care about it that much :twisted: )
Anyone has some more clues?
Then what I would say is that the widcomm stack on the 8125 is rather burried, or non-existant in the usable format that you'll need. If you do find a way to modify it so I can use things such as FTP File Transfer across BT, that would be excellent to post, especially if it could be incorp into a cab for easy installation.
Please, keep me informed of your discoveries - I'll see what I can dig up but you seem to know where to look more so than I.
As a former Treo700 user, I've followed the Widcomm transplant threads with some interest. However, like cold fusion, some have reported wild success but the results have been hard to duplicate.... :wink:
However, this may have changed by now since I ditched my 700 for an 8125 almost 6 months ago.
Firstly, a big thank you to all contributors here, for the first time I thought I would contact HTC re problems with the diamond and believe me, I won't ever bother again with HTC support.
Over the years I've had many HTC devices and like many people here, have a strong understanding on subjects like push email. I just can't believe how difficult it is to talk to anyone from support areas regarding issues. I just thought HTC technical dept may be different, but sadly they are not.
The issues I have are (they have been discussed before but the threads have died with no solution)
1) Bluetooth headset, when disconnecting causes the Diamond to loose abilty to make any sound, be it ringing, alarm or music. This is random and only a soft reset cures the problem.
HTC response, Only HTC branded bluetooth devices are supported, tough!
2) Push E-mail, randomly forgets to check back with the server to see if their is a conenction and if not re-establish one. Logs show the device goes into sleep mode and is woke say 8 mins later (does change due to heartbeat interval changing) to ping server. however, its not waking. So I had a situation when the last server communication was 6am, and by the time I noticed I wasn't getting any mail 6 hours had past! Activesync on the device still show connected!!!
HTC response, clearly its your connection settings with your email. Hard reset and try again. Cant be our software.
Any ideas guys, I'm loosing the plot here. The handset is so much smaller and lighter than my kaiser, but I never had these issues.
P.S. I would never have bought another HTC device again if it wasn't for XDA. This forum has helped me so much over the years and also tought me the joys of WinMob!! HTC should be paying you guys!!
Bump:
Anyone else suffering from these problems? Push email is particularly frustrating.
I have this problem too. The answer from HTC is wrong because bluetooth is an universal standard and , is no reason to say to use only HTC bluetooth devices. Bluetooth should mean compatibility with all bluetooth devices . Another stupid answer from HTC.... Anybody to help us ...?
flashflash said:
Firstly, a big thank you to all contributors here, for the first time I thought I would contact HTC re problems with the diamond and believe me, I won't ever bother again with HTC support.
Over the years I've had many HTC devices and like many people here, have a strong understanding on subjects like push email. I just can't believe how difficult it is to talk to anyone from support areas regarding issues. I just thought HTC technical dept may be different, but sadly they are not.
The issues I have are (they have been discussed before but the threads have died with no solution)
1) Bluetooth headset, when disconnecting causes the Diamond to loose abilty to make any sound, be it ringing, alarm or music. This is random and only a soft reset cures the problem.
HTC response, Only HTC branded bluetooth devices are supported, tough!
2) Push E-mail, randomly forgets to check back with the server to see if their is a conenction and if not re-establish one. Logs show the device goes into sleep mode and is woke say 8 mins later (does change due to heartbeat interval changing) to ping server. however, its not waking. So I had a situation when the last server communication was 6am, and by the time I noticed I wasn't getting any mail 6 hours had past! Activesync on the device still show connected!!!
HTC response, clearly its your connection settings with your email. Hard reset and try again. Cant be our software.
Any ideas guys, I'm loosing the plot here. The handset is so much smaller and lighter than my kaiser, but I never had these issues.
P.S. I would never have bought another HTC device again if it wasn't for XDA. This forum has helped me so much over the years and also tought me the joys of WinMob!! HTC should be paying you guys!!
Click to expand...
Click to collapse
I currently don't use BT headset anymore. However, before using Diamond, I use the HTC Touch Elf with A2DPTOGGLE http://www.teksoftco.com/forum/viewtopic.php?t=1626
It can switch between BT headset or speaker. I tried beforeWM will not automatically switch between them. I know there is problem using the same A2DPTOGGLE in Diamond, because it is a Today plug-in and Diamind hide the Today from TouchFLO 3D. You may try to use "Second Today" together with the A2DPTOGGLE to fix your issue.
Another issue with your pushmail (via GPRS), I constantly working with pushmail and there is no missing mail. there are 2 things you may need to take into account.
1) check your peak or non-peak time. if you need to constantly receive mail immediately in 7x24, you need to set non-peak time also "arrive immediately". something like that.
2) apperantly, WM will save battery when device in sleep mode, WI-FI will deactivated. if you use WI-FI to work with pushmail, you may need some registry settings (i dunno which registry to control this) to disable such energy saving capability. Or, use normal GPRS or 3G data connectivity to test.
P.S. I hate to be the support of HTC product, but seems HTC have well-known bad after sales service.
Using adv. config. I disabled ,,joint stereo'' . I have no problems with ''no sound'' after using BT headset anymore. Can somebody else to confirm this ?
emilceteras said:
Using adv. config. I disabled ,,joint stereo'' . I have no problems with ''no sound'' after using BT headset anymore. Can somebody else to confirm this ?
Click to expand...
Click to collapse
I've tried but doesn't work, this problem's still here