Related
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.
I have been sent a link from O2 Data Support for downloading the new XDA2s ROM upgrade, which apparently will fix the Bluetooth problems.
The link is...
http://www.sourceo2.com/O2_Developers/Devices/O2_Xda_II/XdaIIs_launchROM.htm
Haven't done anything with it yet, but thought you guys might like to know...
regards,
Guy
Hmm I wonder if I can use this update on my O2 Xda2s.
I got it in Malasyia.
Noel
I installed it on my UK XDA 2s, I will report back later.
In the PDF it's saying that this version is only for devices sold by O² UK or O² Ireland... Not sure if I should give it a go on my version..
Noel
I think I might wait and see what others say about this before I install it myself. So many that have it already say it is great but then you hear others say it has caused problems.
That post is the launch rom, not an upgrade. LMAO It is intended for people who attempt to flash the XDA IIs with a different vendors rom and screw it up.
Mike
Nope, its not, click the link. O2 are obviously just too lazy to create a new page for a new rom!
Nigel
HAHA you are correct!!! LMAO oh well. :shock: :lol:
Hi..have installed the update..and have encountered several problems...was wondering if anyone could help me.
I hate the fact that the clock has disappeared from the top right so whe u are using applications its no longer visible. Is there any way of bring it back?
Also now when you click the o2 at the top it dosn't give the active connections anymore. Therefore whats the quickest way to disconnect the gprs? and is there any way of bringing that back to how it used to be?
I have also had to reset my phone more often that I had to before.
Was wondering if anyone had encountered the same problems and how to resolve them.
Thanks so much...
Bit the bullet and upgraded last night, wifi still works and as I use Corporate mode I don't get any issues with 02 active, icons or clocks. All seems normal, so far!
Have to agree with Dave. I finally bit the bullet and installed the update last night. Don't like the new O2 active and put the clock straight back with the registry key.
Other than the missing clock and poor O2 Active software which I never use anyway no real problems. Tom Tom still works fine with my Bluetooth GPS receiver. WIFI still works fine with WPA security and everything locked down on the access point.
Still receive SMS notification and its nice that you're not limited to 70 char when using ' in sms text messages now!
All ok.
har5ha:
Just get the old O2 active back. To to this, head to the xda-dev FTP site, find the old O2 XDA IIs extended rom, pull it, find the file install.ARM.CAB (O2 active)
Sync/backup yr stuff then hard reset the XDA IIs, and let it do its stuff. When leave it to install the extended rom, but be ready to soft reset it when you get asked the 'corporate/personal' question (you'll have to watch the screen since there is a timeout). Once it reboots, copy install.ARM.CAB to the machine, and execute it. It will soft reset yr device at the end.
I use 2 things from O2 active, the battery plugin and the O2 icon to kill connections. Shame billy did not think to include a disconnect dialogue as well really (he put on in for vpn).
There might be a way to install old over new, dunno. I tried and it locks loads of files (even if you prevent it from loading).
Nigel
thanks Nigel...I ended up installing gb soft for the disconnect button.
So its ok...still getting loads of crashing. I think am going to reinstall it and then use corporate mode..hopefully it will crash less!
can I get an update on xda iis rom update
Hi all, I'm still new to this whole thing but reading and researching all I can. Don't have an xda iis as of yet, but on the high streets waiting list. I like the phone and in one way, can't wait, but don't want problems when I get it, especially at the price. Can anyone on o2 that has purchased their phone from o2 let me know how you are getting on...problems...ect, before and after the update.? To be honest, I'm a bit afraid to bite the bullet and get one right now due to what I'm hearing...especially since I'm not very computer smart. I do understand that it depends a lot on the manufacturer of the phone but if I had problems like I'm hearing about it would really do my head in...(no patience). Thanks
Well I love my phone to bits...had issues with the update but now that I have hard reset it and put it corporate mode its not freezing anymore.
But you have to remember its a pocket pc...like a pc..will need to be reset every so often...I was resetting mine of average once a day. It just takes a minute.
There are some negative points..but the positive outweighs the negative I think. My old pda was palm os (clie) and this is windows which is really good! As well as the fact that it has a phone built in too!
Hi all.
Can you please post some more feedback on this rom.
How is the BT stability?
Range?
Crackling noise?
License Expired troubbles?
I know its Build 3500, but maybe something else in this rom makes a difference.
How about the problem with sound dissapering when you answer a call.
Any troubbles here? This is really a pain in the (_!_)
Running the New Rom for a couple of days now and it seems much better than the launch Rom, The O2 active stuff is just as pants as usual so remove that and the "Connections" exe from Windows\startup.
Best thing is that it's stopped the annoying bug of the GPRS settings being screwed up when you enable/disable Wi-Fi.
Recommend it myself
Password
Anybody knows the password for this rom
PDA2K Upgrade
Hi, Can this rom replace the i mate rom on the 2K.& If so will it then be sim locked to O2? as I want to use an O2 pay as you go, & T-mobile sim
many thanks in advance............
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
Hey guys,
I recently upgraded my T-Mobile UK MDA Compact III to WM6.
I now have an intermittent problem with the GPRS/Internet. Basically, if fails to connect.
From what I've read, I think I need to delete my current connection settings, and then run the CAB from the WM5 Rom.
Has anyone on T-Mobile UK, done this with success? If so, can you point me in the direction of the CAB file you used?
Cheers,
Tim
I just set mine up manually.
Go to T-Mobile Website, click on phone support
http://www.t-mobile.co.uk/help-and-advice/phone-support/
enter your phone number and follow instructions for setting up MMS and you get a .pdf with instructions to set up both GPRS and MMS.
Delete any current settings and follow the above instructions.
I too am getting these issues. I have recently upgraded to the WWE dopod WM 6 rom (official HTC release) 3.7.707.1. I started to notice that if my phone was out of reception for any amount of time GPRS would fail to reconnect until a soft reset was performed. I have added the radio 02.94.90 to try and resolve this but no joy. I have added the GPRS settings exactly as per the TMob site again no joy. GPRS Auth is set to PAP which I think is correct.
One point to note is that I have not installed any items from the Dopod ext rom.
Once I have soft reset the connection will be fine until I lose reception again.
Hi,
Same issue here with all WM6 ROMs I've tried so far (to at least some extend). Most noticable is irritating behavior in Google Maps with WM6. In WM5 when the connection is unavailable the GPS tracking just continues till data comes in again. In WM6 the result is an error message. It's one of the reasons that makes me consider going back to WM5 for quite a while now. New features are nice but if old ones aren't at least as solid as before it makes no sense when you need them.
Recently I bumped into the every same issue you describe (requiring a soft reset) with B&B 3.7.. Which is a step worse in terms of stability then what I experienced before. At the same time there have been periods that I don't bumb into the issue. So I'm not sure what the cause is. My guess is that it's triggered when you've been in a bad reception area for some time.. But I don't have any hard facts to confirm the exact trigger of the problem.
Al66 said:
I too am getting these issues. I have recently upgraded to the WWE dopod WM 6 rom (official HTC release) 3.7.707.1. I started to notice that if my phone was out of reception for any amount of time GPRS would fail to reconnect until a soft reset was performed. I have added the radio 02.94.90 to try and resolve this but no joy. I have added the GPRS settings exactly as per the TMob site again no joy. GPRS Auth is set to PAP which I think is correct.
One point to note is that I have not installed any items from the Dopod ext rom.
Once I have soft reset the connection will be fine until I lose reception again.
Click to expand...
Click to collapse
I thought i'd try hard resetting my phone today to see if it would help but still no joy. the problem appears to affect voice as well as data and only occurs after at least 15 - 20 mins out of reception.
any ideas folks? I would go back to wm5 but the tmobile rom isn't available.
Hi All,
I have thesame problem previously with my Wizard. Found out that one my today plug-in is the culprit. The plug-in is "Battery Status Today ......" the one that shows the , Operator's name, speed, temp, V, A etc of your PPC on the today screen.
I dunno whether this is true and working for anyobe but in my case, my GPRS back to normal after after disable the plug-in. You can try the same too.
Other way, is to disable all non-standard today plug-in, test your Egde/GPRS with connect and disconnect(pressing the red button for more than 3seconds).
Activate one plug-in at a time and do the same test. Hopefully, you can indentify the problem and solve it.
regards,
morisa
Downloading the O2 ROM to see if that helps.. I have a feeling it might resolve this issue (fingers crossed!). I will post back here if it does.
Cheers
Alex
Once off the tube this morning my phone connected straight up and downloaded my emails. I hope I'm not speaking too soon but I think the O2 ROM has resolved the issue which would suggest it is a bug in the Dopod SEA ROM.
I will probably get the radio upgraded to 02.94.90 at some today and test that too.
Cheers
Alex
02.95.90 is now available
The problem is one of the most annoying ones you can have: it appears only from time to time and you don't know when and even when it does you don't notice.
Simply my phone is not accessible for others even it shows full range and so on. The message "...the phone is switched off...". This problem occurs in as far as I remember 3 releases of ROMS (full, vanillas, etc). The radio ROM was also changed. I don't remember having such issue in early WM6 or in original 2005.
Since it's not related directly to any of the releases I post it as a new thread.
Now I have 3 options:
1. Downgrade to 2005
2. Throw the unit through the window, wait until end of contract and buy an iPhone
3. Try to fight with T-Mobile UK - which is not really an option since I just recovered from fighting with Orange for over a month
Does any of you experienced such problem?
Any known issues with downgrading to 2005 like ISPL required before flashing original ROM?
Any suggestions?
Adigital said:
...
Any known issues with downgrading to 2005 like ISPL required before flashing original ROM?
..
Click to expand...
Click to collapse
Well, I got the answer - couldn't wait and did the downgrade using original ROM. If anyone interested it went without problems. No ISPL needed. Connected, fired-up the exe file and worked OK.
I'll see how about the availability problem.
Ok, seems that it's only me having the conversation ;o)
I apologize for the thread location - it doesn't seem to be related strictly to WM6 anymore as I...
...installed WM5 and did some tests:
(I have voice mail switched off)
- Call waiting enabled = no calls allowed when GPRS active
- Call waiting disabled = no calls when transferring data (large file) but received when no transfer
- Used W660i SonyEricsson handset - could receive calls regardless of GPRS activity
Rang T-Mobile tech support where they told me that this is network feature that when internet connection is active no calls are allowed and since my voicemail is turned off all callers get message that my phone is switched off. In the light of GPRS specification and my tests this is a bull****.
Now I'm asking anyone on UK T-Mobile Web'n'Walk and who wants to help - please do such test. Just try to call your number from different phone when opening a web-page.
This is pretty important to me - I need internet on the move and don't want to get rid of my MDA.
Thanks in advance!
Hi there,
I'm on T-Mobile UK too and I ran some tests myself and found that you are absolutely correct. When you transfer data you cannot receive phone calls.
I've got an O2 device with me I can do some more tests on and I'll also try and borrow my Wife's Samsung and test that too. I'll post my findings here.
Cheers
Alex
ok, i've just tested this on an O2 3G device and there was no problem, next to try a none windows mobile t-mobile phone.
seems this problem has been around for while and on other networks.
http://www.freenfo.net/mobile/archive/index-t-64022.html
ok, final test and conclusion.
I tested the same o2 phone as above but in a NON 3g area (i.e. gprs only) and found the exact same issue.
conclusion: this seems to affect all types of phone and multiple networks but only when using gprs NOT 3g.
I'm suprised we havent heard more about this problem.
cheers
Alex
Thank you Alex very much for your help.
I did some research on the topic last night and found the same info as guys in the thread your linked. It must be that T-Mobile UK operates in NOM-2, which allows to suspend GPRS session only when no data is transferred. When packets are transmitted the device doesn't 'see' incoming calls as it's 'busy' with dealing with the packets. NOM-1 is 'able' to encapsulate information about incoming call into one of the packets and the device is notified about - so it can react, suspend the transmission and pick up the call.
The fact is that our MDA/Artemis uses Class B of GPRS which doesn't allow simultaneous CDA/GPRS at the same time. Even if it can suspend active data transfer it is the network that has to support that feature.
What I must notice is that I had lot more problems wiht this when I was using WM6. It seems that there were some packets transmitted by the system or something. I had my mail set to check servers every 15 mins at the beginning but lately ony once an hour or two. Other soft that could transmit anything was Weather module from SPB or Touch. Now when I'm on WM5 and was checking the issue during loading a page I was unavailable but as soon as a page was completely loaded my phone was accessible back.
My surprise is that if the 'issue' seems to be quite normal and there is nothing to do about it why I couldn't find any info about it here. Doesn't it affect anyone of our community?
I may be wrong with the WM6 expirience but still. If WM6 works fine in that respect it must have happened that someone missed a call when browsing the net.
i hadnt noticed to be honest
mugglesquop said:
i hadnt noticed to be honest
Click to expand...
Click to collapse
Did you try ringing your phone when it was loading a long page or downloading a file?
TBH I think I've noticed it just as much on WM6 as I did (or didn't) on WM5, I think I put these odd voice mails turning up down to weird WM issues! Now I know the truth though.
Obv. there isn't a lot we can do about this and I'm not prepared to turn off my Windows Live Mail or my direct push. I think we just have to wait until our contracts are up for renewal and get over to a 3G device - I'm liking the look of the Touch Cruise myself, or the Touch Dual if I want that keyboard back and by the time my contract is up I think they should be on T-Mob UK.
does the same thing happen in Edge areas or as that rolls out will the problem disappear?
I'm not sure about how EDGE works but the problem affects GPRS rather than 3G due to the fact that GPRS and the incoming call are submitted alongside each other and 3G is seperate. I don't think t-mob uk have edge running yet so I can't test, perhpas some else can test for us.
Bro.. My first 3rd party ROM is the Touch 3.0.. and yes.. my connnection did go off once a while (no bars as well).. that was kinda irritating. I have to go to connection manager and toggle my data connection or something like that, before my phone will get the GSM signal.
And yea.. the original WM5 and WM6 have no such issues.. I wonder if this is because of the new radio version..