Develop Bugs

Response From O2 !!! Re XDA IIs Bugs

Had the following response to o2 as a result of emailing them with a load of bugs in the XDA IIs a while ago. My email to them it still on the end of their response.
Hi Nigel,
Thanks for this detailed and comprehensive report.
Most of your observations relate to the core Microsoft OS or the integration of the WIFI software, and we will pass them on to the right groups.
In response to some of your comments:
- When will O2 be releasing the firmware update that HTC have already made available to resellers?
* A new ROM image is planned for release in the next few months. We cannot advise a specific date at this time.
- Will this update fix the bluetooth issues
* We are looking to include a new version of the Bluetooth software from the Vendor, Broadcom.
- Will this update include mobile media player 10 as recently made available to integrators by MS
* WMP10 is planned for a later release of the software, later in 2005
- Have any of the hardware faults above been fixed on later units, have you managed a software work-around for the microphone issues?
* O2 reviews all customer feedback with it's supplier, and changes to device manufacture are made from time to time. We cannot comment on what changes are made or when, but we are aware of your observations and are actively discussing with our vendor.
Regarding the yellow screen: our experience is that if Cleartype is enabled, this will significantly affect the quality of the screen display. Please disable cleartype if it is enabled. If the screen is still visibly yellow then you should discuss returning the unit for repair under warranty with your service provider.
thanks,
O2 Product Management
-----Original Message-----
From: Nigel Webber [mailto:[email protected]]
Sent: 04 January 2005 11:54
To: [email protected]
Subject: List of issues discovered on O2 XDA IIs
Hi
Having owned an O2 XDA IIs for 6 weeks now, I have discovered a huge number of bugs - its actually the most buggy product I have ever purchaced, and I do buy alot of gadgets. I am a programmer by trade, so you can rest assured that these issues are genuine and not 'finger trouble' on the part of the user.
Anyway, I suspect MS/HTC have fixed most of these by now, I note that both QTEK and IMATE have released firmware updates based on new firmware from HTC for the Blue Angel. We are yet to see the same from O2.
Connectivity Problems
---------------------------------
Add a new profile to connection manager and then add a 'modem' to that connection. Go and fiddle elsewhere for a while. Often when you come back to change the settings for that connection the 'modem' has dissapeared. (its still there, a soft reset will cause it to re-appear).
Skype does not work with the XDA IIs. This is not a skype issue, but rather an issue with the WiFi implementation on the XDA IIs. Using skype with the XDA IIs (more than 10 metres from your AP) will cause the XDA IIs to drop the connection, and worse still, the WiFi system on the 2s locks up completely requiring a soft reset. No app should be able to cause WiFi to crash like this! This is fully repeatable on Skype versions 1.00.14 and 1.00.20 (latest).
Often, after setting connection manager to always use certain profiles, and then encountering a problem, you head into connection manager and find that your selections never stuck
VPN connections do not always stick when set, they dissapear from the menu (aka the modem settings)
I have tried for ages and failed to make a VPN connection over anything GPRS, WiFi etc. VPN was one of the reasons that I bought the device (access to home and work networks), but it just does not work. Additionally, the instructions with the unit offer no help about how to get it working. Perhaps O2 can offer an FAQ on this feature.
IMAP support is very very bad. Its quite common for an IMAP server to not store mail folders in the root. In decent clients you can specify the root imap folder, not in pocket outlook, it ends up pulling the entire dir struct from your home dir!! I rebuilt the imap daemon on my linux box to compile in a default root folder. This solved the previous problem, but the imap support is not suitable for use away from wifi cause its so damned slow. It does not just look for new messages, and there is no way to tell it to do this. Also, when you send an item it ends up in the default sent items, not the imap sent items. Imho, the main reason to use imap is to keep your emails intact (be able to see what you sent from the mobile device from a desktop). I realise that this is an MS issue, but its pretty naff. (Outlook 2K3 on the desktop has the same issue re sent items btw, but at least that supports rules so you can put it right.)
MS wrote pocket outlook for connecting to an exchange server, which, I suspect only 50% of the devices purchaced will ever do. Pocket Oulook *always* starts pointing at the exchange folder structure, not your POP3/IMAP account, and there is no way to config this. Unessesary taps required. Why can I not DELETE the default exchange folders if I dont need them? I have a work-around for this, perhaps O2 should FAQ it. Changing the shortcut for outlook in the appbuttons folder makes the outlook button on the device start outlook in a user specified mail folder. Just change the shortcut to: 19#"\Windows\tmail.exe" -service "ServiceName"
Sending/recieving MMS messages is unrelable. I seem to have to go into the connections manager and manually select 'MMS Network' in the Work and Internet sections, then I can send/recieve MMS messages. After this, I then have to reset Network Connections to what they were before. MMS should automatically select MMS network when the user is sending/recieving an MMS message and automatically put the original setting back afterwards. There is an option in pocket outlook asking the user which connection to use. This is set to MMS network, but it keeps asking for a password all the time, and fails to remember the password when told, and fails to retrieve the MMS message. To get MMS to work, I have to manually select MMS network in the Connections Manager.
WiFi
-----
WiFi Reception is **attrocious** my laptop will tell me that I have a full signal and the XDA IIs will barely register when at the same location. Even holding the 2s 1 ft from the AP does not cause the signal indicator to go past 40%. I have tried the unit with several AP's all with the same result. Did someone forget to fit a WiFi patch antenna on the Blue Angel??!
Refuses to connect to a network that is not broadcasting the SSID. In general, when you want to add a new box, you can set AP to broadcast SSID, it will then find the network, after it has connected, you can hide the SSID. For future connections from 'pre-registered' boxes, no SSID is required. Not so for the XDA IIs, refuses to connect to a base station that is not broadcasting an SSID, or in some cases, creates a new connection with the name "" (i.e nothing) (which again refuses to connect).
Right, now, if you have 2 wifi networks listed in PPC settings, it will sometimes sit there for ever failing to connect, do a soft reset and it connects.
Another one: you have two connections in the 'configure wireless networks' dialogue, one is 'connecting' other is 'unavailable'. The one that is connecting is obviously not gonna connect despite 100% correct settings, so I select 'remove' it does not dissapear!!! If I had written this software, the user would see a dialogue box thus 'This network is connecting/connected, are you sure you wish to remove its settings?' Selecting yes, would either terminate the connection attempt, or terminate the connection and then remove the damned setting with no further agro!
In network settings, I often get some *stupid* status info. It sometimes says that my home network is 'available' or 'connected' when I am at work, and that the AP thats 3 ft away is 'unavailable' Clearly it isn't, wifi does not travel 10 miles! Soft reset solves (it connects to the AP thats 3 ft away).
Sometimes, when Wlan is disabled, and I enable it, it stays disabled. i,e I try and re-enable it and the tick has dissapeared again. This continues until I give up and soft reset the device. This seems to happen more when there are two networks present, and more still when the disable WLan after X mins of inactivity option is used.
BlueTooth
---------------
When you use bluetooth, for network access, all the stuff in connection manager gets reset. If this needs to be changed to facilitate bluetooth network access then I would expect it to return to the old settings once the BT Network access session was ended.
Sometimes bluetooth fails to start complaining about insufficient driver space. I write windows KMD's all the time, I suspect its somet daft like a lack of available stack space, or stack recursion. Soft reset cures
Also, sometimes when I try to start bluetooth, I get a daft message saying that the licence for the bluetooth stack has expired!!! It then starts BT and all is OK.
Most usefull application of bluetooth is the headset. Unfortunately, no headsets work with the XDA IIs. It says it supports bluetooth, but it does not. When will this be fixed and will O2 be releasing a bluetooth stand-alone patch like Imate have?
Applications
------------------
The bundled O2 active stuff is very flaky. Take the end programs applet - it often crashes its self while trying to force an app that is 'not responding' to stop. The built in 'stop app' applet (which they burried in settings) seems to work but...
- If you reconfig your shortcuts (so you can find stuff!) Then the applets 'camera' and 'O2' always seem to copy themselves back out into the root of StartMenu-->Programs again. *why?*
Go into the find applet and get it to do a search that takes some time. Wait for it to get going and then click stop. PDA hangs. It does come back eventually (2-3 mins later), but remains sluggish until you do a soft reset. Trying to suspend while its hung just switches the backlight off!
There are a load more issues as well... I currently do around 10 soft resets/day. My basis is that a wait of more than 10 secs means that the device has crashed. Perhaps if I was willing to wait 5 mins all the time for it to get its arse into gear then the number of soft resets could be reduced!
Hardware Issues
------------------------
Microphone: No one can hear a word I say to them on the phone. This is especially bad with the built in microphone, but also present with the supplied headset. Is this a hardware/software issue? do I need to return my unit to be exchanged for one with a working microphone?
Keyboard slider mechanism: This gets progressively looser until it starts flopping around. Has this issue been solved on later units?
Yellow screen: The screen takes on a yellow hue when view off angle (by say 10 deg). XDA II did not suffer from this problem. Is there a fault with the LCD on the 2s?
Questions
---------------
Since my device is basically a door stop due to the huge number of issues above, I have some questions:
- When will O2 be releasing the firmware update that HTC have already made available to resellers?
- Will this update fix the bluetooth issues
- Will this update include mobile media player 10 as recently made available to integrators by MS
- Have any of the hardware faults above been fixed on later units, have you managed a software work-around for the microphone issues?
If you require any more info on the above problems, let me know. The XDA IIs could be a decent unit, there aint ought else like it which is why I am documenting my problems rather than buying a competitors product. I would like to see these issues fixed.
Regards
Nigel Webber

If you're a chewin' the fat fan, you'll know what I mean when I say I'm taking a seriously big sniff and there's a hint of something in the air.
Sounds to me like they really are just fobbing us off with standard responses and aren't taking complaints seriously.
* O2 reviews all customer feedback with it's supplier, and changes to device manufacture are made from time to time. We cannot comment on what changes are made or when, but we are aware of your observations and are actively discussing with our vendor.
Click to expand...
Click to collapse
Well thats just pish isnt it?
We cannot comment? Why not? Is it because they would have to acknowledge the product has gone to market well before it should have?
The least they can say is that they have gone to HTC with the list, and what HTC are planning on doing about it.
This is what I got:
Hello,
Thank you for yoru email,
Unfortunatley we don't have any dates at present for an upgraded
Bluetooth stack, we are aware of issues with it and are pushing our
products group for an update or at least a timescale.
I will keep this mail, and as soon as any information is released, we
will let you know.
Regards,
Paul
O2 Data Support UK
-----Original Message-----
Sent: 12 January 2005 01:03
To: O2 Data Support (UK)
Subject: XDAIIs Rom Upgrade timetable
Hi
Have you guys got a timetable for rolling out an upgraded ROM for the
XDA IIs?
I'm having quite a few complaints from callers saying they cant really
hear me well and bluetooth isnt working particularly well either.
From what I've read on the web, this is a known fault with the default
ROM version included as standard.
Also, i'm interested in the Blackberry functionality once it becomes
available, but at present, I'd settle for a handset thats not annoying
colleagues and customers.
Thanks
Darren
Click to expand...
Click to collapse

I don't want to seem too critical (after all, if you're really having to reset 6-10 times a day you must be on the verge of killing someone by now) but a lot of the issues you list aren't bugs, they're useability issues. Someone working in a customer complaints department (wouldn't wish it on anyone) is going to take a lookat the list and dismiss most of it as whining because you present personal gripes and subjective observations as bona-fide bugs. It is very tempting when angry to try to oversell parts of a long list of complaints, but this just gives the recipient amo to dismiss the lot.
I also think you should get your unit replaced with a new one ASAP. So few people are having the problems you describe, particularly surrounding the WiFi signal strength and screen, that you do seem to have a barely working unit!
You do have my complete sympathies. To spend so much money on something that SHOULD be as near as dammit perfect, only to end up with a damp squid is hugely frustrating (it has happened to me a couple of times).

I agree, most of this list is not bugs that anyone has. Some are even limitations of the operating system.
If you are soft resetting 6-10 times a day you should hard reset your device because it is 3rd party software, do not restore from backup, do not install software and see how it is. If you still have to reset your xda is defective and its time to send it back!
I would agree with some points mostly that bluetooth is a mess and needs to be fixed, the o2 bt patch resolves the connection issues but there still is static issues! But this is not exclusive to the XDA iis but all blue angels. The siemens model SX66 has no update at all!!!
Oh remember when we had our xda II & imates and wanted to dump the microsoft BT stack and would do anything for the widcomm stack. LOL we sure got what we wished for. Bet most of us would go back if we could.

Indeed, got it all of my chest in one go! Trouble is, with PDA's your only point of contact is with your reseller. I dont have a way of contacting HTC, Broadcom, MS separately as I would if this were a PC with faults in several manufacturers programs/hardware.
I am indeed, not expecting the likes of the mail/imap issues to be addressed for the blue angel, I would like to have some mechanism to tell MS where they are going wrong from me (the user's) point of view.
If we have no mechanism to provide feedback then we just end up with half baked kit in the next iteration as well. Perhaps this is why Windows Mobile 2005 will be the 6th? release of what was originally called windows CE, and why 'CE' is now on its third name? And I still doubt whether they will have got it right!
Nigel

I suspect that I just expect too much!!
Its not third party software cause I have hard reset the device, and installed nothing and I still have to do regular soft resets. I doubt very much whether it is a hardware issue either, and all XDA IIs devices have the same firmware. Most of the time, my soft resets are done to pursuade said device to see the wifi ap thats 2ft from it. I regularly use three different AP's in three different locations. I suspect that this is not the case for most people.
I am also very impatient (a device such as this should be quicker than I am!) The PPC OS suffers from 'pregnant pauses' where the whole thing appears to lock up. If they last longer than 30 secs then I am likely to get bored waiting and do a soft reset. Give me a 3GHz PDA with a 10 hour battery life!
My mate is getting one soon, so I will compare his with mine and return mine if the issues have been fixed. I'd hate to return mine and end up with one thats even worse ;-)
Nigel

veletron said:
MS wrote pocket outlook for connecting to an exchange server, which, I suspect only 50% of the devices purchaced will ever do. Pocket Oulook *always* starts pointing at the exchange folder structure, not your POP3/IMAP account, and there is no way to config this. Unessesary taps required. Why can I not DELETE the default exchange folders if I dont need them? I have a work-around for this, perhaps O2 should FAQ it. Changing the shortcut for outlook in the appbuttons folder makes the outlook button on the device start outlook in a user specified mail folder. Just change the shortcut to: 19#"\Windows\tmail.exe" -service "ServiceName"
Click to expand...
Click to collapse
Could you explain this workaround a bit more. Are you just changing the name of the shortcut within \windows\appbuttons or is this some sort of programing? Sorry if I'm missing something obvious but I'd really like to get this one working.
Thanks, JD

@jdee246
http://forum.xda-developers.com/viewtopic.php?t=13755&highlight=

I agree with Nigel on the issues with the XDA2s some i have not seen because i dont use it to its full. I also rest probly 5-10 times a day. I got my first XDA2s on 5th November i am now on my 5th one and in a few days i will be changing for a new one. I simply ring them and go over the list of faults, and then remind them that the device they send me will be no better than the one i have and i will be calling again soon to change it. They told me as long as its less that 28 days since the last one was sent to me it can be changed. So i will keep swoping it for new ones until they get me a working one ( we know this will never happen) but at least the new ones dont slide open on there one when you pick it up for a couple of weeks. So i asume i will contine to do this untill the XDA2i is released then i return the current XDA2s (probley number 20 by then) and do a up grade to the new XDA2i

veletron said:
@jdee246
http://forum.xda-developers.com/viewtopic.php?t=13755&highlight=
Click to expand...
Click to collapse
Thanks Veletron. That worked like a charm. Thats been hacking me off for ages.
JD

@applecom
How long does O2 take to send you a new unit, and whats this 28 days thing? Surley if its faulty then they are obliged to sort it as long as its within the 1 yr guarantee.
You are saying that apart from the keyboard not sliding open, the new ones are no better? If thats the case then there is no point in my sending mine back cause I'll get one with the same problems.
My screen is only yellow when viewing the unit from an angle, and the keyboard does not fall open (although it is very sloppy).
Any idea if the wifi reception is better on the later units that you have had?
Nigel

XDA IIs Customer Services Response
Hi
As an addition to this subject I contacted the company I bought my XDA from re the poor microphone issue and they asked if I had read up on the issue via any support websites as they (she) did not think the issue had been resolved and I wouldn't gain by receiving a new product.
I agreed that I didn't think it possible yet but wanted to keep within the 28 day replacement window for as when they did.
The response was to:
A) Open up the 28 day replacement window on this problem for a further 3 months and
B) State that if a fix was forthcoming then a recall would take place and I would get a replcement anyway.
On this basis I decided to hold for the moment to see what happens.
In all maybe an easy solution for them but it suits me for the moment! :wink:
veletron
The 28 day window is for an immediate (a few days?) replacement
with a new unit, after this period your unit is taken away for repair with no replacement and no estimate of when it will be returned/replaced.
pvb

they replace it same day, I recieve it by courier the next day and give them my old XDA2s, some times i do a restore from a backup and some i reinstall my software from fresh. But no they are all the same i am hopeing for one that has newer rom and thus might work correctley

Agree with all the problems above, the few that really frustrate me are...
- Floppy keyboard slide, should latch back in?
- Hands Free needs to be louder, could someone build a preamp util?
- Annoying that picture contacts seems to be a separate app to regular contacts?!
- Still slow, thought the faster CPU would mean no delays!!
Cheers, Ash

XDA IIs Battery issue
I have just upgraded from an XDA II to a IIs and other than the normal unlock problem I have just brought a second battery, when I changed the batteries the unit did a hard reset, I thought this was because the new battery was fully discharged.
I did some further testing and found that when ever you remove the battery and replace it the unit does a hard reset (all batteries are fully charged).
Any comments or do I have a unique unit?

Hello to you all.
I have just read all the above with great interest as I am seriously thinking of buying an XDAIIs this week. I will be moving from a Treo 600.
I am very concerned about all the problem you seem to be having and I am starting to think that buying one may not be the best idea. The other phone I am looking at is the Nokia 9500. I already have an HP 4150 and so I really dont need all that the XDA IIs has to offer.
I would be interested in hearing peoples comments on the phone to help me make my mind up. I do have to say that when the Treo came out loads people reported a lot of problems but I had mine for a year and it worked perfectly for 10 months then the screen gave up. It appears that nearly all these "Smart/PDA" style phone have teething problems that are mostly down to the product being shipped before it is really ready.
What do people think? Should I take the plunge?
All the best.
Raymond

XDAIIs Battery Issue
I have two batteries and swap them regularly. Your backup battery is either not charged or faulty if the unit hard-resets when you swap them - I think a warranty claim is likely.

XDA IIs and Bluetooth Problem.

When I turn on Bluetooth on XDA IIs, I got this error message :
"The bluetooth radio radio failed to turn on due to insufficient driver memory available. You must perform a normal reset before you can turn on the bluetooth radio."
Anyone can advise how to resolve this ? Soft reset does not cure the problem. Thanks.

have you upgraded to bluetooth stack version 3900 ???
if you have then im fresh outta ideas, if you havent find this at our FTP site,
ftp://xda-developers.com/
login and password = xda

got the same problem when i installed one of the bluetooth upgrades on its own. then i installed the new rom and everything was fine. not sure where the connection is but thought id share my problem

Problem solved.
By the way, what is the latest version of ROM for XDA2s, and where to get it from ?
Thanks.

So I was wrong.
After upgrading the BT upgrade, things was OK yesterday. But this morning i got the same error again.
Went to ftp://xda-developers.com/ as suggested, can anyone mentioned the filename of the ROM mentioned by thakkergaurav above ?
Thanks.

The latest ROM is 1.40
You can find it here: http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel

Hmmm..... :?
This BT issue is really getting to be NOT FUNNY! :evil:
Running the new ROM 1.40 and BT 3900 I'm now getting the "no sound" problem on the handset and caller cannot hear me on a HS801!
I use the turn on/turn off BT trick or soft re-set and the handset is OK for a couple of hours but the HS801 still does not work even though its OK with my old PocketPC,a nokia and a Motorola V3!
Is there any consistancy with this problem? It seems the different ROMs, Radio Stacks and BT versions are being effected.

Well, emailed the tech support, and all they can say was ...
"There is a ROM upgrade in development which is in the final stages.
We request your patience as we are trying to release the upgrade as soon as possible."
And that was 2 weeks ago.

even my bluetooth is upgraded to 3900,
i get the same error message also..
i cannot believe a 96mb memory is still not enough
i never get this kinda nonsense when i was using the 5450 ipaq
my today plugins was all over the screen and I had never encountered low memory...

I had the same problem but I have a Harrier not a BA so I thought it was related to that and you BA guys wouldn't get it.
Anyway, the solution on the harrier was to
-turn flight mode on
-soft reset
-turn bluetooth on
-turn flight mode off
Hope this helps

Here is a possible solution from wiki:
The ExSenetoR wrote:
Delete Run_BTTrayCE_10.lnk from your Windows\Startup folder and soft reset. Now you wont have the BT icon on the tray bar, but you wont have the no sound problem. If you still need bluetooth you can start it from the Windows directory as BTTrayCE.lnk.
Have fun.
Click to expand...
Click to collapse
Have not tried this myself, but I believe others have had success with it. You may want to save the file somewhere else, in case you want to reinstate it later...
Hope this helps
Chris

I posted this in another thread.
It really does look like a combo of the 1.40 ROM and 1.12 Radio Stack that is causing this problem (in this case, anyway. See sig). After trolling various forums, it seems that both BT build 3900 and 3500 are having the same issues.
IMHO it seems that the Blue Angel is trying to send the call to my HS801 even when BT is not activated.
Has anyone had a good look at the current radio stack? I've tried contacting Broadcom (BT chipset supplier) but it has been 3 weeks with no answer.
I've done the Run_BTTrayCE_10.lnk workaround but this is only a bandaid and I don't really have enough experience to attempt to cook the ROM. Any ideas?

I have a Motorola HS801 as well and I can receive calls just fine but when I make calls the other party can't hear me. I'm giving up on the HS801 - it's a cheapie anyway and I don't know of anyone else who's got it working either. Running BT3900

8525 + Jawbone + 3 seperate ROMS = No Sound!!!

Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...

BombaMyte said:
Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...
Click to expand...
Click to collapse
I am currently using my Jawbone with Schnaps 4.01 Lite rom and no problem. Before that I have been using all of Matt's Pandora Kitchen roms, right up to the latest and never had a problem. I ran Schnaps 4.30 Full rom too, but really can't remember if I used the Jawbone during the testing time. If someone else can't help I can flash that rom again and test the Jawbone with it too. Let me know ho wit goes.

works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?

I have an 8525 running Schaps 4.30 with radio 1.48.00 and mine is working. I did however have to return one Jawbone because it would connect and I could hear the conversation but the mic didn't pick up my voice. I tried that one on my wife's razor and it had the same symptoms though. What radio are you running?

Using with TNT's latest ROM and no problems, however not real impressed with Jawbone so far. Most people I call say it sounds "tinny".

mthomas said:
works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?
Click to expand...
Click to collapse
AFAIK, the BT radio works. Like I said, I can pair up with it just fine, and even see the other BT-enabled phones/devices at my job. I just can't get any type of audio from my JB. I'm currently using vp3G as well.
UPDATE: Well to be on the safe side, I tested my Jawbone on a couple other phones; sure enough it's working fine, so it's got to be something up with my poor Hermes... Any advice?

Mine Jawbone Works fine also. I remember when I first got it I was having trouble with my sound. I remember changing the audio bitrate from 48 bit to 44 bit in the advanced config utility 1.1 Also try changing the stereo setting to mono.
May help you out, hope so.

Just a quick update: I reflashed vp3G's 3.62 ROM, reset my JB and repaired it; same effect, nothing. Just to be on the safe side I paired the JB with my Wizard, BB Pearl, and a couple of phones at my store and it works as it should.
@ mthomas: I'm using 1.48.00 for my radio. Since you and I seem to have the same type of setup, did you install any other cabs that help your BT out?

Do you have another Bluetooth headset to test. Even thought it can pair ok, it only means the "data" channel is working. The problem could easily be the voice channel which is not working. If possible, may be borrow another headset to try.

That's my next idea. I think I have an old Plantronics I can charge up and test out...

*BUMP!*
Gotta keep this fresh. Funny thing I noticed though: when I have the Jawbone connected and the phone rings, I still hear it's little tone in my ear, but no audio comes or goes through. No registry edits have been made; I've even done a hard reset, re-paired and tried again, to no avail.
C'mon you guys! Why am I the only 8525/Jawbone user around here that *can't* use his Jawbone??? Help me out here...

wish i had the answer. im using the most current att radio 1.54.07.00. how did your device work w/ another headset?no additional tweaks

Okay, now I'm getting pissed.
I tried using my old Plantronics 320. It pairs fine with the Hermes, but making phone calls is a no-go.
The only thing I removed (from anyone using vp3G's 3.62 Full) was Sleuth's PTT Fix; I need PTT more than being able to re-map the button. So I doubt this is the culprit.
WTH can't I use my good Jawbone with this thing?!?!

Quick *bump*

Same Problem
I have tried everything, I can hear the calls just fine but no sound from my mic. I have paired with other phones & it works fine. Please let me know if you find a fix!!

UPDATE: I tried using a Moto H700 and a Plantronics 340-no dice. Now I'm starting to think if it's a BT stack issue...

Now I'm completely stumped. I just flashed back to the original ATT WM5 rom, paired up, SR, then made a phone call to my 8525 from my house line. Jawbone rang in my ear, sure. I answer the call, no sound.
Could there be a problem with my BT radio? And if there is, how can I be sure/troubleshoot it?

Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another

myv6mustang said:
Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another
Click to expand...
Click to collapse
Good thought... But I already did that, still no joy. In fact, I just flashed over to HTC's official TyTN rom, and still nothing. I'm going to call a friend of mine and see if I can get it to work on their 8525. Here's a good ? tho: Should it matter if it's Cingular or AT&T branded? Are there any differences in hardware between the two types? Or could it be a faulty BT radio? I'm racking my brain trying to figure this out.
Worse comes to worse, I'm sure I could exchange my Jawbone; I *do* work for AT&T so it should be okay...

Okay, here's another question: If I were to flash *ALL* the way down to the original Cingular shipped ROM, RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship, would this have any effect on the BT stack? I'm only asking because I can't seem to find any type of information about replacing the built-in stack (outside of the Widcomm project and that's too beta for me ATM), and I still can't understand why so many headsets that I've tried with this damned 8525 don't seem to work, but so many people here @ XDA can use theirs. There's no differences between the Cingular branded and AT&T branded models (at least hardware/software-wise), and if I pair up my trusty Jawbone with another 8525 (AT&T branded, btw), it works fine.
I know I've been going back and forth with this, but I did pay a good amount for my 8525 and I don't want it to be partially or mostly functional. Hell, if my poor Wizard can handle my Jawbone, why can't my Hermes?
BTW, thanks for all of the suggestions you guys have given me to help me with this problem. Even though none of them have worked, I still need to give props where they're due.

Bluetooth Devices Lost

All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6

BrianP6 said:
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
Click to expand...
Click to collapse
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh

Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.

BrianP6 said:
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
Click to expand...
Click to collapse
This bug appears only when 2 or more devices get paired.
I've been trying everything, even abusalza himself suggested some module replacement. i'm working on replacing drivers and certain folders in sys in my kitchen but still nothing yet... so far not yet, but it's fixable, i just gotta figure it out.

Thanks Josh,
I guess you'd know this anyway, but for completeness and for the benefit of the whole forum.........
Even though the paired devices are no longer shown in the Bluetooth Devices window, and you can no-longer use your HTC to pair more devices, then so long as you carefully initiate the pairing from the other device, it will be recognised, PINs will be requested and devices configured appropriately. I have just done:
Audi A4 in car kit
Laptop via Internet sharing
Jabra earpiece
None appear on the Devices window, but all (so far) appear to work perfectly.
Cheers,
Brian.

I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?

austinsmartie said:
Has this happened to anyone else?
Click to expand...
Click to collapse
Yep, I have experienced everything you mentioned at one time or another, even the square characters showing up in the device list.
I have gone all the way back to test Faria R32 ROM. It's amongst the best I've found for A2DP with the S9's along with some of PDACorners early ROM's. The drawback are that it doesn't have the 1% battery increase .dll cooked in and also still exhibits the "numbers for character during a call" bug.
It does have nearly 31 MB of memory free after fresh install though. (using 4MB pagepool - default is 6MB)

austinsmartie said:
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
Click to expand...
Click to collapse
It frustrated me enough that I started building my own rom!
I released one version here that I have been running for quite some time with no issues in the bluetooth at all.
I need to tweak it a bit more to make it "polished" but it is very useable and stable. I just wanted to run it for a while to see how it is going to act over a longer duration before I continue to fool with it, and I have been rather busy here lately.

Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.

joshkoss said:
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Click to expand...
Click to collapse
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?

Hmmm - doesn't happen on my ROMs...
The suspect things I'd be looking at in SYS are:
Bluetooth
Bth_A2DP
Bth_HID
Try replacing those folders with known good ones and see if the problem still happens...

austinsmartie said:
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
Click to expand...
Click to collapse
No Magic potion! lol
I basically did what CRCinAU described. (His rom doesn't have the issue, and feels a bit faster than mine. But, I was looking to create "My perfect rom").
But I also replaced files in the redist folder with "bt" in their name, with files from a known working rom (anryl's 20755). Like I said I wanted to run the rom for a while, now I just need to go back and tweak and clean up some things in the rom before I make another release.

summary
stickybud said:
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Click to expand...
Click to collapse
it is a really odd issue and seems to only affect the hermes... Here is the deal, Some chefs when porting sys grab the cplmain.dll to get the build number and keep some other items in their kitchen sys for stability purposes... I have noticed in my experience when porting, if the cplmain.dll does not match some other components with the same build number it will cause this issue. usually resist, shell, os, folders have been containing these sensitive items. so in short, if the issue is occuring cplmain.dll in redist folder does not match other components in your sys causign the conflict.
edit, and oh. i've tried replacing all bluetooth which had no effect.
So to fix this, the chef needs to report sys correctly and recook the rom.

Probelm with WiFi

Hello there,
What I Have: Att 8525 Herm100
Rom: Att's Mobile 6
Everything is stock but the extended life battery
The problem I am having is when ever I try to activate my WiFi the phone doesn't do anything. I am not sure if there is a wifi card or not but that's want I want to know. I have tried everything from activating it in com manager to going into the settings and activating it manually and nothing happens it acts like I didn't even hit the button to activate it. Is there a wifi card in the phone or is it integrated on the motherboard in the phone. Note: I bought this phone off e-bay and the wifi never worked when I received the phone.
I am new here and if there is a post about this already I am sorry.

I hate it when that happens.
To begin, there were two ATT OEM WM6 roms relevant to the 8525 that I noticed deep in the bowels of XGA.
I chose the later file (higher revision numbers) I found it here:
http://wiki.xda-developers.com/index.php?pagename=Available Original Shipped WM6 ROM Versions
From comm manager when I click the tower button on within a second the spinning windoze icon shows something is happening. It then starts "sniffing" for my preset wifi connection (ATT supplied 2wire portal 802.11g).
Now, if yours does not show the spinning windoze working icon when you turn on wifi? There obviously is a problem. This could be software, or hardware related (duh). If there is no error message related to "wifi is not an option, unavailable, or screwed" then my first guess is there is something missing or damaged in the ROM update that was applied to your device. As far as I know all 8525 (herm100) were shipped with wm5. It had been mentioned in the volumes of xda that the first AT&T WM6 rom was a little buggy. Try the later released AT&T WM6 update.
It was a run file so no muss no fuss. Sync the phone run the update from the pc, three minutes later the phone is flashed to ATT WM6 professional.
You could take it to a ATT shop? But, I think that without a doubt they would hand it back and say you need a new phone with a 20 year contract and 3g data plan even Obama would blush at.
Try the hard reset. take a picture of the startup screens so you have the numbers and see if the wifi startup is working after the reset. If not then compare the numbers to the above mentioned roms. If the indications are you have the first issue of WM6 from ATT try flashing the second release. If that still fails then your device could indeed have a hardware problem.
The wifi is indeed built into the system and if that chip on the board is not working it could be a overly expensive problem. Possibly a shop has a working board they would swap out cheap? Otherwise, it is a fun phone you can keep notes on, run gps software if you have a bluetooth gps receiver and software like tomtom.
To be honest the wifi on my 8525 has been convenient when around the house to check the local weather radar when I hear a thunder outside, or browse headlines from the porcelain room or even leave messenger turned on incase a gamer friend is looking for someone to get shot up in a game.
I have used the live search voice thing to amaze the neighbors once. But, the limited range of wifi is a real drawback to how truly wonderful that addition could be.

HELP Please! Wi-Fi not working!!!
Hi to XDA all users !!!
MY Hermes - HTC TyTN [Herm200]
I bought HTC Hermes myself year ago.
there was flashed a WM5.0, I've just downloaded from here HARD SPL & WM6,1 (Custom) Flashed.
Wi-Fi will works on WM5.0.
Well here I am at 6.1 flashed and now is not working Wi-Fi. When i pressed Power ON - loading long and nothing happens.
Other methods are also tried on Commanager and Settings - but did not help.
What do I need to do my dear.
HELP!
Thank you for your attention!

Hi Nurk.
Since the wifi worked on wm5 but failed after the 6.1 flash. I would guess the problem is in the 6.1 components. You might start with contacting the kitchen rom you employed for WM6.1 thread and see if this has happened to others. Next step would be to check the radio rom version. I did see on xda an assortment of Radio roms.
If your not totally in love with the current rom you have flashed? Try another 6.1 or even a 6.5 and see whats poppin.

and what you have in HKLM\Software\HTC\CommManager\WLAN\DeviceName?

utak3r said:
and what you have in HKLM\Software\HTC\CommManager\WLAN\DeviceName?
Click to expand...
Click to collapse
I have get this from registry:
HKLM\Software\HTC\CommManager\WLAN\DeviceName - {98C5250D-C29A-4985-AE5F-AFE5367E5006}\TIACXWLN1