o2 official ROM upgrade - MDA III, XDA III, PDA2k, 9090 General

Contacted o2 (UK) requesting a date for an official ROM upgrade to WM2005 and WMP10.. not definitive news, but if you believe their reply then it's on it way:
"A rom upgrade for the XDAIIs is still in test. We are unable to give a
release time or confirm it's contents until it is fully accredited.
As soon as any information is available it will be posted at
www.my-xda.com"
Fingers crossed, I don't fancy trying one of the modded versions just yet - I rely on the phone a bit too much at the mo.
-FM

O2's 2003SE software isnt exactly stable. I did the upgrade yesterday and its fine except the BT keeps turning off

If you want to increase the stabilty of an O2 XDAIIs, I'd do a hard reset. (Hold the power button whilst pressing the reset button). It'll come up saying it's going to install a load of stuff. Thats OK. When it asks if you want an O2 config or a corporate config, select corporate. You will then be prompted for a pin number. The numbre you require is 0506. Enter the numbers. The phone will eventually finish without installing the O2 active stuff. This, in my experience, turned a phone/pda that was always locking up into a very stable thing!
Hard reseting removes everything and returns it to it's out of the box state. You can restore a previously saved backup as this will put O2 active back on! I learnt this the hard way!

mine was still unstable after the corporate reset and removal of the o2 software....
running tomtom5, BT and media player doesnt help though

What are the chances of the NEW UK XDAIIS ROM containing support for i-mode?
I've got a sneaky suspicion it's why they have dragged the release of it out a bit.... It's taken a long time considering Asia has a ROM all done, that needed a few bugs fixed, but surely would not take this long....?
Must be something 'extra' going into it.
O2 i-mode launch is 'imminent'
http://www.theregister.co.uk/2005/09/20/o2_i-mode_autumn/
What is i-mode?
http://www.sourceo2.com/imode.html
from Wikipedia:
"Opposed to the WAP standard which utilizes WML on top of a specific protocol stack for wireless handheld devices, i-mode borrows from fixed Internet protocols such as C-HTML based on HTML, as well as DoCoMo proprietary protocols ALP (HTTP) and TLP (TCP, UDP). "
I may be completely barking up the wrong tree, but it should be manageable through a software update.....
Anyone know if this is a possibility?

Related

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_v131139_upgrade.exe Update

Hi guys,
Recently installed the latest ROM offered by O2 onto my XDA2s, having firstly been incredibly frustrated that I'd lost all my txt messages and installed applications, I have since found that the phone locks up almost daily now - it particularly seems to be whenever switching the phone on/off with the topright power button - at which stage it'll just freeze.
Sometimes when making a call, I'll dial the number, and when ringing starts, switch the phone display off so as to save batteries, when doing the same since the ROM update, the phone seems to hang.
VERY frustrated, anyone any ideas, or experiencing the same?
Another question, with Bluetooth Audio, is there any way to stream a telephone call through my PC via a bluetooth link allowing me to chat/hear through the PC instead of the phone?
And finally, does anyone else find the Network Connections settings on the PocketPC OS incredibly stupid, confusing and impossible to accurately setup for Internet access through Wireless/Bluetooth??
Cheers, Ash
this may help
http://forum.xda-developers.com/viewtopic.php?t=18350
follow the above thread. I found by doing what it said about removing o2 active stuff I havent had to soft reset since..
I would also add that I have also upgraded to radio rom 1.12.00 and Blue tooth 3900 (shortly after so not certain it was due just to that but likely)
If I can be any help at all PM me and I will try and assist maybe talk on instant messenger..
But I must repeat it hasnt locked since the above and the battery life seems much much greater.... for instance I left it on from 6pm last night until 7am this morning and it appeared to loose only 10% battery including making a couple of calls..
I would do it again with and uk xda2s
Hope that helps
as for the rest of your questions no idea LOL
Stay happy
Thanks for your reply, I did install the upgrade in Corporate mode having read that thread first, but its still installed all the O2 Active stuff - so should I now remove the bits from my Startup folder that relate to O2?
Also, I now cannot find any easy way to disconnect GPRS once its connected????
yep
I would get rid of the active bits as said.. to disconnect gprs simply press and hold the red hang up button
I will look again at your posts and answer anything else I can.. dont know if you have noticed but this site is slow so sorry for the delay in replying
have you upgraded the radio rom and BT version?????
stay happy
did you enter a corporate code when setting up in corporate mode?
0506 i belive
stay happy
Ahhhhh, I thought Corporate Code was for the screen password lock or something, so I just entered my usual code - should I rewrite the rom upgrade again, or can I run the setup program separately on the XDA to enter the 0506 code??
I'm currently running...
Rom V: 1.31.00 WWE
Rom Date: 12/13/04
Radio V: 1.06.00
Protocol: 1337.38
ExtRomV: 1.31.139 WWE
Is that the latest? got from the official O2 website.
Thanks also for the GPRS disconnect, that helps, shame it doesn't tell you, hehe!
you should just be able to do a hard reset and put it into corporate mode. do a backup first though..
The versions you are running are the latest from O2 I think.... however you can find the ones I am using on this forum... I have found them much better and if you are going to do a hard reset you might want to do them first....
anything else just shout..
stay happy
Yeah but if you back up then you are backing up the O2 active stuff as well. When you do a hard reset and choose corporate ok. But when you use backup restore the O2 active gets restored. I use Sprite as backup and i can't see offhand how to backup everything EXCEPT the O2 active stuff so that it won't reinstall on a restore. I've manually put back all my progs etc and then backed up so O2 Active won't come back.
I have to say that the latest O2 Rom update using the personal rather than corporate mode is a disaster. My phone was locking up every day. I was getting really p***** off with it. Now I have got shot of the O2 active stuff everything works fine.
Hi
Here are the instructions I got form Brian at O2 data Support. Back up to PC rather than storage card and restore from there. Here goes:
Workaround - setup a 'Corporate' install that doesn't include the Active
User Interface
Before starting insure important data is saved by syncing to Outlook on your
PC if needed (do not use backup/restore)
* Hard reset.
* Near the end of the custom applications auto-install you will be
given a choice of "Corporate" or "Personal". You should choose "Corporate".
Note: you will only have approx 5 seconds to choose this option, after which
the 'Personal' option will be automatically selected
* You will be asked for a pin. Enter 0506 (that's zero five zero
six) and tap Finish
* You will see the message "Welcome corporate user, O2 Active won't
be installed". Your device is now ready and you will have everything except
the Active User Interface.
Important: the mobile web, WAP and mms settings WILL still be preset.
Hope this helps
Regards
Chris

XDA IIs Software and Bluetooth Headset

I've recently purchased an XDA IIs (unlocked and used on Vodaphone). Overall very impressed but I am having some annoying problems that I'm hoping for advice on (my collegue has also purchased one and is having similar problems, so I don't think it a hardware problem)
The XDA has just the standard O2 software apps installed and I have upgraded to ROM 1.31.00 WWE (from my-xda.com a few days ago), its say radio version is 1.06.00
Problems:
1) Very unreliable software, I quite frequently (several times a day) have to press the reset button. I seem to have the most recent version from O2. I see some comments on the forum about disabling O2 Active software?
2) I'm using a Bluetooth headset (Jabra BT250), this worked well with my previous phone a Nokia 6310i. Specifically:
- When I receive an incoming call it rings on the headset, if I answer by pressing the button on the headset in generally (but not always) answers with the headset connected as I need. But if I answer by pressing the answer button on the phone (hard button or pop-up menu button) the headset isn't connected and its a struggle to get it to connect mid call. However if I make outgoing calls in nearly always uses the headset correctly. Very annoying an inconsistent behaviour. I'd rather not use a different headset as I like the Jabra and the problems seem to be due to the XDA as it worked fine on the 6310i
- The range is hopeless, people say its very hard to hear me if the XDA is more than a couple of feet away, even turning my head so the Jabra and XDA are on opposite sides degrades the quality badly, I didn't think my head was that thick! With the 6310i I could be at least 10 feet away
- The volume, even at maximum, is too low, especially in a noisy environement like a car. It's much less than with the 6310i on exactly the same BT 250
I hope there are some fixes for this. I think the XDA is a great, really useful all in one device, but the poor relaibility and terrible bluetooth headset support are really spoiling it for me
Regards
Mike
Hi...
I just ordered my XDA IIs..hehe..selling my PDA2k now..love the black color..
Hehe..anyway, my PDA2k was using the BT 3500 drivers and i have the same problem as yours occasionally.
Most of the time, when i answer from the unit (not the BT headset's button), the caller can barely hear my voice.
However if i use the BT headest's button, it was fine...
I was using the Jabra BT250 also..but sold it to get the Motorola HS850..
Both are giving me the same problems...
I've read on several threads where poeple are successful in using the BT 3900 patch (sorry of i'm wrong)..but my PDA2k does not work with the patch..the screen turns garbage n messed up..had to hard reset it
I love this unit..canlive around with its current problems..hehe..hopefully it gets fixed.
Cheers!
The BT problems described above appear fairly common amoung xdaIIs users. Based on my research on this, there are a few things listed below that can help. Listed in order of ease to do. Start with 1 and progress to 5 if you are feeling brave :? or wait for 6!
1. (EASY) Keep your add on "Today Plugins" to an absolute minimum: I have found that SBP Pocket Plus to be particularly troubelsome and had to uninstall it.
2. (NOT TOO DIFICULT) Disable O2 Active: O2 advised me that the xda2s is more stable in "corporate mode" with O2 Active disabled. To do this you will need to back up your device data to your PC and then do a hard reset. As the device boots up and starts to go through the configuration process, you will be prompted to choose "corporate mode". You only have about 5 seconds to say "yes" before the configuration continues and installs personal mode. Select 'yes' and you will be prompted for a code. Enter 0506 (that's zero five zero
six) and tap Finish. You will see the message "Welcome corporate user, O2 Active won't be installed". Your device is now ready and you will have everything except the Active User Interface.
3. (MORE DIFFICULT) Upgrade your BT Stack from BT Build 3500 to BT 3900. Details on how to do this are provide in the companion wiki-developers forum
4. (A LITTLE SCARY) Upgrade your Radio Stack to 1.10 and your BT Stack to Build 3900. If you want to upgrade the radio stack at all, WIKI folks recommend upgrading the radio stack first and then the BT Stack.
5. (MORE SCARY!) Upgrade your BT and Radio Stack AND your ROM. WIKI have posted 1.40, which it seems can be used in conjunction with the existing extended ROM on the O2 XDA 2s. Not for the feint hearted, although the instruction they post for this are pretty comprehensive I must say.
I "talked" to one xda2s user who had gone through to step 5 and most of his issues had been resolved. I am at number 2 right now... Thinking of going to 3,4,and 5, but probably waiting for 6.........
6...?......ah yes...., wait for O2 to post the next full ROM update... :wink:
Hope that helps
Regards
Chris
The BT problems described above appear fairly common amoung xdaIIs users. Based on my research on this, there are a few things listed below that can help. Listed in order of ease to do. Start with 1 and progress to 5 if you are feeling brave :? or wait for 6!
1. (EASY) Keep your add on "Today Plugins" to an absolute minimum: I have found that SBP Pocket Plus to be particularly troubelsome and had to uninstall it.
2. (NOT TOO DIFICULT) Disable O2 Active: O2 advised me that the xda2s is more stable in "corporate mode" with O2 Active disabled. To do this you will need to back up your device data to your PC and then do a hard reset. As the device boots up and starts to go through the configuration process, you will be prompted to choose "corporate mode". You only have about 5 seconds to say "yes" before the configuration continues and installs personal mode. Select 'yes' and you will be prompted for a code. Enter 0506 (that's zero five zero
six) and tap Finish. You will see the message "Welcome corporate user, O2 Active won't be installed". Your device is now ready and you will have everything except the Active User Interface.
3. (MORE DIFFICULT) Upgrade your BT Stack from BT Build 3500 to BT 3900. Details on how to do this are provide in the companion wiki-developers forum
4. (A LITTLE SCARY) Upgrade your Radio Stack to 1.10 and your BT Stack to Build 3900. If you want to upgrade the radio stack at all, WIKI folks recommend upgrading the radio stack first and then the BT Stack.
5. (MORE SCARY!) Upgrade your BT and Radio Stack AND your ROM. WIKI have posted 1.40, which it seems can be used in conjunction with the existing extended ROM on the O2 XDA 2s. Not for the feint hearted, although the instruction they post for this are pretty comprehensive I must say.
I "talked" to one xda2s user who had gone through to step 5 and most of his issues had been resolved. I am at number 2 right now... Thinking of going to 3,4,and 5, but probably waiting for 6.........
6...?......ah yes...., wait for O2 to post the next full ROM update... :wink:
Hope that helps
Regards
Chris
Chris
Thanks for this. I changed to Corporate mode 6 days ago and its only had one crash, compared to before 5-6 times PER DAY!
Any idea when O2 are meant to be offering the next ROM update (are we talking weeks or months)?
Regards
Mike
I can't not see the 5 seconds page for selecting "corporate mode" when i do a hard reset.
I do hard reset by press on/off button + press on reset button.
Hi Mike
Well, it is supposed to be the end of April, so my guess is that it will be weeks, rather than months at this point. Also, the 1.40 ROM posted on wiki is a WWE version, so maybe this is a 'bootleg' version of what is to come from O2... only a guess on my part here...not really sure of it's origin...
Regards
Chris
Hi MR2046
What device and what ROM version do you have loaded?
Regards
Chris
Hi cbrow51,
I use O2 XDAIIs
ROM : 1.31.00 WWE
Radio : 1.02.00
Protocal : 1337.32
ExtROM : 1.31.920 WWE
Thanks
2046
Hi MR2046
The option to select corporate mode comes up close to the end of the install after you do the hard reset. You only get about 5 seconds to say 'yes' and then enter the code, before personal mode continues and installs the O2 Active stuff.
I see from your info that you have the older radio ROM (Current 02 version is 1.06) and a different extended ROM (I have 1.31.139WWE)... Not sure if the difference in extended ROM would cause you not to get this option or not...
I would try hardresetting again and see if you get the corp mode option. if you don't, then you might want to download the latest ROM from the O2 web site.
Hope this helps
Chris
Thanks a lot
But the O2 asia website did not update anything. There is only a small patch for BT upgrade.
BTW, which O2 website you meant?
BT sync and internet access
Hi all,
what about Bt sync/internet access? does anyone manage to do it ? i do not use a headset but i am trying for some weeks to get connected to my desktop via BT - with no results... i upgraded to 3900 just today but it did not help .
the manual of the device is not helpful for doing so...
which O2 Website
Hi MR2406
ah! that probably explains it. Sounds like you have the O2 Asia ROM then, correct?
I am using the UK ROM from the UK O2 web site. I am not sure if you would be able to download the UK ROM to your device, which I assume is of Asian origin..? O2 UK state that you should only download their ROM if your device meets certain criteria. Take a look on the site and check compatibility before downloading / installing.
From the very rudimentary understanding that I have from looking through the wiki site, its possible that you might get some kind of country and or operator code errors if you install the UK rom on your device. That said, there are detailed instructions on how to correct these errors also.
If I were you, I would look through all the materials on wiki, check the O2 site in UK and then decide on the best approach.
Hope that helps
Regards
Chris

Has your TomTom Device ID changed?

guys,
when I moved from WM5 to WM6 (both official ROMs), my device ID appeared to change (assumption by virtue of the fact it changed in TomTom 6).
Can anyone else confirm they have seen this? I'm still waiting for HTC UK support to contact me. ABout a week now.
I thought it might be helpful to see who has seen this (regardless of ROM details).
Hi,
Yes, all time you Flash your PPC with new Rom, Your Device ID change, and Tomtom need to be change too (Trafic, SN, etc...)
If you have Tomtom Trafic option, go to tomtom site to change your device id, it's work fine.
As far as I know, it is only the DOPOD, and DOPOD based ROMs that have this problem, and it is a bug in the firmware. The very latest DOPOD release has apparently fixed it- so Mun's Indigo Full which uses the latest ROM is OK, but Lite shows the problem.
Device ID's are a complex matter. Some are based on the IMEI, some derived from the ROM version and some by other means. TomTom and Mobipocket both use 'other means' to derive the Device Code, and it is only with the 'faulty' ROMs that the Device Code changes.
I've taken my Trinity through about 7 ROM updates, and the TomTom Device Code remained the same except in the DOPOD WM6 ROMs; reverting to another ROM resulted in the Device Code going back to what it should be.
This is a real problem for TomTom users because they are currently refusing to relink the new Device Code to the Traffic and Weather account, even if you succeed in obtaining a new activation code. So you have a situation where the software is working fine, but you can't access your TomTom Home subscriptions. Customer Support are now asking for 'proof of purchase' of the WM6 ROM upgrade, which of course can't be provided as there is no 'proof of purchase' for most ROMs.
We have had quite a long topic on this on 4Winmobile, and the latest situation is that it could be a case for Trading Standards to investigate, as TomTom are effectively blocking users from accessing services they have paid for.
hi Neil,
that's most interesting feedback, thanks.
I too have installed at least 6 ROMs on my Trinity. From the OEM Orange UK WM5 (the phone came with) through to mUns TE and others the device code remained static.
Then when I went to the officical Dopod WM6 ROM it changed. I believe I also used the latest official of their ROMS the other week, which was rumoured to fix this issue, but it has not. I think people are confusing the other issue of changing with each hard reset- which I do not have the problem of.
I'm very frustrated with TomTom- it's a month now with no Traffic- and I use it for my work driving the length of the country.
I've suggested that it shouldn't be my problem- after all I have paid the subscription, and it's an official ROM. OK it costs them time to make a change- but it costs them more to keep sending emails to-and-fro asking me for proof etc etc. I've wasted hours on this chasing, HTC (Dopod), Microsoft and TomTom, plus investigating on the web. It's clearly an issue, but no-one will hold their hands up.
If someone could post a link to the latest Dopod ROM which definitively does not change the ID I'd be eternally grateful. And by definitive, I'd prefer first hand experience ;-)
folks,
tonight I bit the bullet and installed mUn's Indigo Full. Very quick to install, nice looking ROM but the Device ID has still changed :-(
So every Dopod official ROM and now the full Indigo changes the device ID from the original WM5 ROM and every other WM6 ROM.
I've tried 3 ROM in 7 days now. This is getting silly!
I think I will not be renewing my TomTom Traffic. Oh and I forgot to say, HTC Europe sent me a fob- off email tonight.
"Contact your phone supplier......" Thanks. They seem to be deliberately avoiding this- I gave them the chance to just say "yes" we know there is an issue. That would be enough for TomTom.....
TomTom and license key
I have heard that TomTom only allows the use of the license key twice. Has anyone found this to be true? Because, if so, a lot of people who have installed WM6 on their Trinity and have been asked to activate Navigator again (myself included) will have to think twice before switching ROMs again.
Hmm I'm not sure if this is correct- if the map is activated, and you change the device ROM, TomTom does not need the map to be reactivated normally.
This ONLY happens if you change the device ID- i.e. you then need to reactivate with the licence.
If Device ID's change again then yes there is a problem.
Please lets not confuse the issue here- the problem is for Traffic subscriptions- you can only change your device in the TomTom account online once in 6 months.
After this you must go through TomTom support.
It's not got customer service to be waiting 1 month with no resolution.
sickboy555 said:
Hmm I'm not sure if this is correct- if the map is activated, and you change the device ROM, TomTom does not need the map to be reactivated normally.
This ONLY happens if you change the device ID- i.e. you then need to reactivate with the licence.
If Device ID's change again then yes there is a problem.
Please lets not confuse the issue here- the problem is for Traffic subscriptions- you can only change your device in the TomTom account online once in 6 months.
After this you must go through TomTom support.
It's not got customer service to be waiting 1 month with no resolution.
Click to expand...
Click to collapse
I also had the "famous" devide-id change after upgrading to the official WM6. But in my case something very strange: I DID send a proove of repair to TomTom (I really had a repair) and then TomTom DID reset my device-id to the correct device-id (when I actually look at the TomTom-site my settings are all correct).
But now I still get an error using traffic (and other Plus-services). I resettet my device on the TomTom site many times but no effect.
The situation now is that I have alle the correct codes, can use TomTom (6) but still can't use traffic!
When I go back to an unofficial ROM (p.e. Sleuth 3.2) with another device-id everything's ok.
Frustrating... don't know what to do anymore, TomTom did their job.
oh no Pietrucci, that's bad news. And very odd if they changed the ID, but going back to another ROM with old ID, Traffic works.
So if TomTom update my device ID and Traffic still doesn't work I'm scuppered.
Apparently they never let you go back to an old ID in your account, which means going back to an old ROM may not help either. Maybe there is something wrong with their account system for Traffic, if your old one still works???
pietrucci said:
I also had the "famous" devide-id change after upgrading to the official WM6. But in my case something very strange: I DID send a proove of repair to TomTom (I really had a repair) and then TomTom DID reset my device-id to the correct device-id (when I actually look at the TomTom-site my settings are all correct).
But now I still get an error using traffic (and other Plus-services). I resettet my device on the TomTom site many times but no effect.
The situation now is that I have alle the correct codes, can use TomTom (6) but still can't use traffic!
When I go back to an unofficial ROM (p.e. Sleuth 3.2) with another device-id everything's ok.
Frustrating... don't know what to do anymore, TomTom did their job.
Click to expand...
Click to collapse
I have exactly the same problem. Online my plus services shows that the TomTom Device ID is correct, BUT traffic still doesn't work.
Going back to the older version of WM6 with the older device code and it works. So TT Plus servers must still have the old device code associated with my PLUS account even though PLUS online is showing the new code.
I've told TT that it's not working but no fix so far.
MAJOR UPDATE: New build of WM6 fixes the device ID change issue. The device ID is the same as in WM5 - the first cooked ROM to include the fixed build is Schap's 3.60a.
Best get onto TT and have that code reverted back sharpish!
hi eaglerest can you post a link to the specific new build of WM6 you are referring to please (the OEM ROm, not the cooked one).
The 8th of August DOPOD rom DOES NOT fix the device ID bug.
i.e. this one RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship
hi,
sorry it's a hermes build.....
http://forum.xda-developers.com/showthread.php?t=322905
ah, so it's not just confined to the Trinity then.
thanks for the info eaglerest.
right, I've given up with this ridiculous Device ID business!
I told TomTom to leave the ID alone (after 6 weeks with no Traffic) and have gone back to mUn's TE, which preserves the old Device ID.
Not what I really wanted but I think I'll be an old man before it gets resolved.
HTC In Asia and Europe fobbed me off and wouldn't even acknowledge this as an "event" let alone a bug.
Hi all, am I missing something? I thought that the latest release of code i.e. OS 5.2.1620 Build 18125.0.4.2 was going to fix this? Or have I mis-read the posts. I ask because I tried the latest Bepe build, and my device ID still changed. Does anybody know excatly why the ID is changing?
moondevil said:
Hi all, am I missing something? I thought that the latest release of code i.e. OS 5.2.1620 Build 18125.0.4.2 was going to fix this? Or have I mis-read the posts. I ask because I tried the latest Bepe build, and my device ID still changed. Does anybody know excatly why the ID is changing?
Click to expand...
Click to collapse
Not really sure what you think you have misread. perhaps you are thinking of a bug whereby the Device ID apparently changed on EACH hard reset? I personally have not seen this.
My problem is that WM5 = DEVICE ID A (My Traffic is registered to this.
mUns TE WM6= DEVICE ID A
Official DOPOD WM6 ROm, Indigo FULL = DEVICE ID B. Now my Traffic will not work.
TomTom will only change the registered device if I can provide proof from HTC or someone else that this is a bug. Guess what- they've been no help at all. Neither have Microsoft or Orange.
sickboy555 said:
Not really sure what you think you have misread. perhaps you are thinking of a bug whereby the Device ID apparently changed on EACH hard reset? I personally have not seen this.
My problem is that WM5 = DEVICE ID A (My Traffic is registered to this.
mUns TE WM6= DEVICE ID A
Official DOPOD WM6 ROm, Indigo FULL = DEVICE ID B. Now my Traffic will not work.
Click to expand...
Click to collapse
OK, just so I'm clear on this because I'm (nervously) about to go down the path of updating for the first time. I'm coming from WM5, having never flashed before, will upgrading with Bepe's latest of .74 change my Device ID or not?
probably, but I have no idea for sure. Not used that ROM.
If you use TomTom Traffic and it does change, you will not be able to use it anymore. If you have never changed your device ID with TomTom, you can do it yourself- but only once per 6 months via your account on their website.
You will have to re-register all your maps too.
If you saw moondevils post, his ID changed with one of bepe's builds. I imagine that bepe uses the same core OS for all his builds so your ID will likely change.
mUns TE is the only Wm6 ROM I have tried which keeps the ID (and I've tried many many).
sickboy555, thanks for your reply.
I *thought* I'd seen something relating to the newer build not changing the ID, but I was obviously mistaken. Like you, I've tried most of the "post Dopod official" Roms and they all change my device ID. I followed the link to the Hermes build and saw that it was a 18125.0.4.2 build, and thought that maybe this would cure it. But obviously not.
What I find funny is that Bepe is building Tomtom in to his builds, and I'd love to use it, except I just upgraded from my SPV M5000 (1 change) and now tomtom won't let me reregister my maps.
Bugger!

New XDA Zest firmware

There's a new Zest firmware available for download from http://www.my-xda.com/. The filename is Xda_Zest Firmware Update_V7.7.0S.WWE20.00_M4.6.5.P7_V2.1.4 GBR20, which seems to be updates to most of the roms inside the zest. It's installing at the moment, and the upgrade interface on the phone is displaying "GalaxyMini5 Eboot (3.33.0). Since this appears to be a codename for the P565, I guess this is more evidence that the XDA Zest is simply an underclocked P565 and more evidence that P565 firmware may well work on it.
Warning, this firmware does not appear to contain the O2 menu software, or the free GPS software that comes with the phone (although maybe the latter can be re-installed from the SD card). Shame - I rather liked the O2 menu interface.
what improvements does it have? Is it actually worth upgrading?
Thanks.
The only things I can see that I don't remember seeing before are a couple of new or updated control panel entries. Video calling is probably the really important one.
You seem to lose the RSS reader, the O2 auto settings, the O2 menu and the GPS s/w (although the latter was only a demo). I have no idea if using the SD card that came with the Zest will restore these, as I don't have it. (If the software is all on there somewhere, and someone could bung me a copy, I'd be really grateful.)
It does make me wonder how the P565 firmware compares. I understand it has a nice touch interface on it.
It seems odd that the new firmware would remove all the o2 specific bits. Great if you want to use it on another network I suppose, but I quite like the mobile shell or o2 menu.
The satnav software isn't on the sd card - only the maps.
The instructions say:
Please note that if you already have CoPilot satellite navigation software on your Xda, refer to the Xda Zest user manual before upgrading your device software.
Click to expand...
Click to collapse
I couldn't see anything of significance in the user manual.
Interesting. I actually have Tomtom for GPS on a different SD card, which is related to the reason I don't have the original SD card. Tomtom autoinstalls from the SD card, so I thought it might be that the O2 software installed itself from the SD card provided by O2. I guess that if it's only maps on the SD card then that's not the case, and the new firmware does strip out all the O2 extras, which seems like a peculiar decision to say the least.
Still, it did get me to try the new SPB mobile shell 3, which is what the O2 menu is based on, but nicer. I'm trying to decide whether it's worth the $35 for just a flashy finger driven interface. The weird thing is, it actually might be.
I'm actually going to upgrade my firmware to new one which is currently available in O2 site. What I want to know is if upgrade mine to the latest what would be the changes I may seen... Is it worth upgrading by loosing all the software?
So far I've seen nothing to write home about. The only reason might be if you can't already make video calls and want to do so. (I never make them, so I have no idea whether or not they're supported in the original firmware.)
I just upgraded mine to new firm ware. It worked fine for me. I didn't lose any O2 extras inc O2 menu. It was Oki but haven't tried yet to make video calls.. I will install iGO8 and will uninstall the co-pilot.
SPB Mobile shell 3.0 Rocks working smoothly with my Omnia and Xda Zest
I've just updated, and I didn't lose any O2 extras either (including Copilot). I backed up the Program Files\Copilot folder on the device to my PC before updating, and copied it back over after the update and voila, I've still got my fully activated version of Copilot. It did still prompt for allowing it to connect to the net during the 14-day trial the first time I ran it, but the license screen confirms it's the full version.
aDe
I have a working theory that the autorun on my Tomtom SD card might have run in preference to some autorun that might otherwise have run the first time the OS booted. I could test this by re-installing the firmware, but it's kind of a pain to have to put all the data on again.
Having played around some more and browsed the Extended ROM on my device, this does appear to be what happened, as all the CAB files are present. Fortunately this is a bonus for me, since I'm not on O2, and most of these files are useless to me, and I can therefore just pick and choose the apps I'd like to install.
This might be useful to other Zest users - the hack to make the Extended ROM visible:
Use your favourite Registry Editor to make HKLM\System\StorageManager\Profiles\ONDisk2\FATFS\MountHidden set to 0 (default is 1)
You can then browse to \ASUS_ROM\ in Total Commander to view your Extended ROM partition. The ROM does not appear to be write protected, so you can now put all the packages *you* want re-installed on a hard reset in there. Neat.
I contacted O2 support about this issue, and they replied saying that:
On occasions the O2 menu can drop off after a ROM upgrade, but this would usually be resolve by either hard resetting or running the upgrade again. The o2 menu is still installed on the new ROM.
Click to expand...
Click to collapse
I have now done this upgrade and have retained the 02 menu. The radio reception seems a bit better as I now get HSDPA at home, which I didn't previously, so the radio upgrade seems to be worth it.
ringer
ive got the zest and am happy with it so far apart from the last 2 days i cannot hear it when i get a call everything else works ie.system sounds,core player etc but the actual phone wont ring it just vibrates ive reset it a million times and checked system settings etc but nothing so if anyone has any ideas i would be very grateful, also how do you know if you are getting hdspa or not is there a setting for it or something, cheers guys.
The connectivity icon at the top right of the screen shows what communication protocol is being used by showing a symbol (usually just a single letter) in a solid square. The letters I have seen so far are:
G - GPRS (2G)
E - EDGE
3G - 3G (this is the odd one out with the two letters squashed together)
H - HSDPA
It's worth mentioning that on my train ride home I see all four protocols at different points, and the hand-off between them is very smooth.
thanks for quick reply i will keep an eye on it, still no joy with my ringer though its very strange. never had a problem like it on my orbit. i will keep investigating ,also do you know if anyone will be coming up with a rom for zest as i miss manila 2d although mobile shell v3 is good.
Have you checked:
Start->Settings->Sounds & Notifications
On the Notifications tab you can select the "Ring type", one possible choice of which is "Vibrate", which will make the phone only vibrate on incoming calls. Just guessing.
yes ive tried all that it might be affected by software ive installed recently i will try unistalling them one by one and see if that helps, failing that il do a hard reset i guess, anyone know how to hard reset the zest? thanks for your help.
There is a contortional key sequence for this, but you can also reset it by going to:
Start->Settings->System Tab->Default Settings
cheers managed to sort it , i installed mini lyrics software and ticked all in associating files which for some reason stopped the phone from ringing
thanks for your help.
Failure of firmware upgrade
Ive just had a power failure whilst upgrading the firmware on my new xda Zest and all it it shows when turning on is "OS Update failed! Please update again". Is there anything i can about this or will it need to be returned to O2. Any suggestions. thanx

Categories

Resources