Hi guys,
I have just bought an o2 xda ii and am having serious problems
was trying to establish a bluetooth connection with nokia 6600 and it just froze displaying the today screen
now xda hangs after switching on and nothing works only the bluetooth light keeps on flashing
cant try anything as it doesnt function at all.
Can anybody help
Isn't There anyone who can help me...??????
Isn't There anyone who can help me...?????? :roll: :roll: :roll: :roll:
when you mean turn on do you talk about turn on as in turn on the top power connector
or a softreset ?
if you mean top power connector then that dont reset the pda you need to do a softreset
if you did mean a softreset then i dont know any other way then a hardreset which of cause delete all your data
Inderts the stylus in the reset hole, if that doesnt work then as the man said you will need to do a hard reset and all data will be lost, hard reset is done by pressing power while inserting stylus in reset hole.
Hi
Thanks for yr reply
I have aslo tried a hard reset but no luck
The device switches on and freezes on the blue O2 screen or sometimes goes thru the setup procedure & freezes at the today screen
Tried it a couple of times
Is there any other way please let me know.
Thanx again :? :? :?
Which ROM do you use? You can try to flash your ROM. There are plenty of treads on this forum on how to do this. Make sure you don't use a USB hub when connected to flash you're ROM. Your MDA II must be connected to a normal USB connection (I learned it the hard way....)
Wouter
Hi
Sorry for the late reply as i was out of town
Dunno exactly how to identify the rom version but when switched on it shows
R 1.05.14
G 1337.14
D 1.03.00 USA
Can u please suggest what to do
Thanx
You can see which ROM version you have by going to:
Settings, System tab and then Device information.
Mine says:
ROM version 1.60.00WWE
ROM date: 12/03/03
Radio version: 1.06.01
Protocol version: 1337.16
ExtROM version: 1.60.06
So I guess you can do a ROM upgrade. To find out how to do it, just do a search on this forum for ROM upgrade and you'll find detailed describcions on how to do it. Make sure that your device is not connected via a USB hub otherwise you can have some trouble getting it done.
Wouter
Thanx for the prompt reply but the problem is that the device starts goes on thru the new device setup programme & hangs nuthing beyong that
So am unable to go to the system settings
Is there any other way i can see the rom version...
Well the colors at the beginning tell you which ROM you have (but are only very short on the screen so hard to read) but you can defenitely upgrade.
Wouter
No Bluettoth Hardware Installed Error Msg
Hey, this sounds like the same problem I have too! I have just posted a new subject in the "Using It" section of this Forum. Does your device also suffer from the following i.e. when the software ha loaded and you hit the bluetooth icon, does this error message come up "There is No Bluetooth Hardware Installed on this Device"? Pls read my post below.
"I have an XDA II, bought from the UK. I live in E. Africa so sending it back is a hassle. EVer since I bought it, although it was OK for a few days, a msg then came up saying "There is no bluetooth hardware installed on this device". This means I cannot put b/t on or off. Also, it affects the performance of the XDA II as it crashes frequently and loses ActiveSync connections frequently. The odd thing is that SOMETIMES, after a hard reset, it's OK again. But then when I do a subsequent hard or even soft reset the same problem occurs! So it DOES work. But not consistently. I conttacted O2 by email & tel. They were semi-helpful. I returned the XDA II to the O2 repair centre in London by courier (expensive). It came back, apparently repaired, but they had addressed the wrong thing and the problem still persists! I am loathe to sending it back without trying something for it - if you have any suggestions. Perhaps I can try a Rom Update or something to see if it sorts it. Even O2 are baffled, but I do not have the privilege of sending it off again because of where I live. Any suggestions or advice please? Many thanks. "
'Frozen' O2 screen with bluetooth light flashing
Hi to all,
I 've been having similar problems since I got my unit last November. You may be able to relate with my problems.. screen won't respond to any taps.. when you send SMS, the 'Send' button freezes... tried soft resetting, sometimes lucky, gets back to normal... at worst, does a hard reset...
after a few months of no reliable answer from local and foreign XDA help.. i'm used to either removing my battery/sim.. wait for awhile.. try to find a place where there's better network signal.. then, puts back the SIM and battery.. many times a get lucky by doing this... but there are also times that I had to do hard reset.. like two hours ago..
Hopefully, some help will come ...
For those who have yet to develop a routine to address similar problem, you may try mine...
Helpless xda II fanatic(???)
Archel Angeles
I have similar experience too. I got my XDAII last November, it runs smoth without a single hang for the first month until one day in January, while using it reboot by itself, after that day the device will just reboot anytime anywhere!
Thinking that this might be caused by some installed softwae, I hard reset my device. After the initial setup then it hang while running the auto installation from the extended rom saying that some file is missing. I hard reset again and it still hang while running the auto installation but saying another file is missing. On the day alone, I hard reset my device for more than 10 times! Each time it will either hang on the O2 startup screen or during the auto installation. Until finally one time manage to pass through the initial setup and auto installation.
On the second day, I quickly bring my set to the service centre for repair, while I describe and showing the faulty set to the service officer, the device self reboot for another couple of times.
I took back my set two days later, the service officer told me they cannot find the fault of this so they re-flash the rom for me, and they have tested it with internet browsing, mms, sms etc without any problem.
The 'repaired' set works fine for another one month until couple of week ago it start to hang during some incoming calls. When call was received, I press the answer key to answer the phone, the device would just hang with the ballon still showing on the screen, i'm not able to answer the call at all.
Last Friday, I finally hard reset the device again and re-install some my software applicaton and games. Second day morning while I was waiting for my friend, I start to attach photo to my contact, just when I attached the first photo and click on the save, the device hang! I press the soft reset button and the screen goes off without rebooting. I press the reset button again but the screen just won't come back. I even took out the battery and put in my backup battery, still the screen refuse to come back! The screen only come back when I performed a hard reset.
Today i found another problem with the device, the free memory is getting lesser and lesser by itself! Just before I type this reply, I soft reset my device and leave my device on the momory status screen, the allocated momory for the program showing 63.02Mb, in used 16.96MB and the Free momory 46.06MB. Now the in use memory increases to 30.75MB while the Free memory drops to 32.27MB!! I did not run anything in the background, I did not even tough my device!!
Anybody here can help save my device?
I have the same problem now. It is really a nightmare for all of us!!!
Exactly
Have a very similar problems 4 days in the row. Self-Blackhangs without any knowing reason. Impossible to use device longer then 10 min. HELP!!!
P.S. Some days before I try to uninstall Intellisync, wich I try, but does not use for a long time. Uninstall was unsuccessful cause .exe was "in use". There problems begins. May be. After one of hard-resets I remove .exe manually and then uninstall prog, but problems persists.
Hi guys, Fortunatly I do not have the same problems with my XDA II but I was thinking maby it is a type of software that has been installed on the device, I have noticed that some apps can cuase VERY strange things to happen (Even some THEMES!!!).... LOOK out for this..
Maybe you could try and run the XDA II after doing a hard reset as bare as possible... As in not installing any other themes or thirdparty software for a day or two and see if the device still gives your any problems... Will be interesting to find out.. I have had resets on my XDA II from using some themes avalible from the O2 website (that users have made not O2, but still) and since using the default theme I have not had a crash or a reboot since... (THIS TOOK ME FORVER to find out)... but might be worth a try..
Keep us all informed how you go with things.. Hopfully its just a pice of software or somthing simple like that...
GOOD LUCK ALL!!!
So, guys, I think that there is a HW problem. MDA freezing during initial install or during HardReset before install. Maybe "motherboard" is microbroken or so on.
Week ago I return my MDAII to T-Mobile and they will repair it to some way. I will report this way to you all as soon as possible. Let we see.
V.
Hi all,
I have the following devis info of mine:
ROM version 1.66.00WWE
ROM date: 02/20/04
Radio version: 1.10.00
Protocol version: 1337.18
ExtROM version: 1.66.101
This Rom works great, just search for it and upgrade!!
Wish you all luck!!!
sounds a lot like the problem I'm having.
Can any of you guys install a new rom at all? mine freezes up and activesync disconnects the second it does... So I guess when flashing your rom and having it freeze up on you, you'd be even further from a solution... thoughts pls
I fixed it guys...
seems a corrupted rom was the problem hitting bootloader mode (power + action + stylus) and installing a new rom fixed my problems
let me know how it works out for you guys
Hi,
Running w2k3se 2.06 wwe for a day now. Looks quite stable. As this is intrim build (in between dcs and CHS version) there are bound to be bugs.
Most have noted camera failing the landscape. I think it would be better if we can list the bugs so that we can try to solve them.
I found many of the bugs cropped if we used older external rom files with w2kse .
Good that many of us are coming out with home cooked extended rom files. The big problem is to find which of these files are better and which are not.
Let me give you example MIDI56.sa.CAB give a better performance than MIDI561.sa.CAB. And rember the cleartype of 1.60 to 1.72 and so on.
The other problem with cooked extrom is that 70-80% file are same in many of them with very few new files. I am on dialup and it takes quite a bit of time to down load 6MB file just to get a customised cab. Also the server will have that much of load.
So my sugestion is we need a repository of file which are included in extrom. Why not seperate the cab files and just publish their customised config.txt in the post.
I think we need to create a thread of only those files. Suggestion are welcome.
RE
OK! Lets starrt the ball rolling.
Noted the followings for v2.06 ROM posted by mystery man:-
1) Sometimes the bluetooth icon on the Today screen would mysteriously disappear. Worst case is when the Today Settings don't even have the Bluetooth Profile although the blue light is blinking.
2) The camera menu got stuck in landscape mode after repeated switching from portrait-to-landscape and vice versa. Soft reset could not resolve the problem. However, after some time of use the problem automatically resolves itself.
:roll:
"The phone is not ready. Wait 15 seconds then try again"
This is when accessing the phone icon in the settings menu, or when trying to send an sms message.
Jez.
Re: RE
FOSA said:
OK! Lets starrt the ball rolling.
Noted the followings for v2.06 ROM posted by mystery man:-
1) Sometimes the bluetooth icon on the Today screen would mysteriously disappear. Worst case is when the Today Settings don't even have the Bluetooth Profile although the blue light is blinking.
2) The camera menu got stuck in landscape mode after repeated switching from portrait-to-landscape and vice versa. Soft reset could not resolve the problem. However, after some time of use the problem automatically resolves itself.
:roll:
Click to expand...
Click to collapse
same here the Today Screen BT will play games with em :twisted:
hi,
few more bugs on 2.06
1. After playing around with landscpae and portrait several times, phone would loose last two rows of buttons both in landscape as well as potrait mode. Soft reset corrected it.
2. MMS composer is not started if you choose from programs, but this can be bypassed by going to the outlook and start coposing.
If you notice startup folder of w2k3se several of the w2k3 startup programs are missing. Is that why SE is faster and I noticed my battery now lasts longer than W2K3 ;-)
Jez said:
"The phone is not ready. Wait 15 seconds then try again"
This is when accessing the phone icon in the settings menu, or when trying to send an sms message.
Jez.
Click to expand...
Click to collapse
This is something I've always seen if trying to access any of the phone's advanced functionality right after a reset, even with my old XDA.
This is akin to trying to access phone numbers on ye olde ubiquious nokia phone SIM card right after turning on.
Finally I upgraded to WM2003SE (2.06).
Direct reason was the declining performance under WM2003 (1.72). What happened was that when running TomTom 5.1 and a phone call came in (or I made one) the connection with my SD was lost. Exit TomTom, take-out & re-insert SD end eventualy restarting TomTom solved that on an incident basis.
With WM2003 SE that problem has gone. BUT I got something back: The sound in TomTom (5.1 and 5.21) is severely distorted ('clicking' like sound). The same (but not that severe) happens when I run Tomtom and I play an MP3 using WMP9.
I tried XCPUScalar, but the CPU load most of the time is around 60-70% (@400MHZ).
My Extended ROM does not have suspicious tools that run permanently in it.
Any clues?
Update: Same issue happens with ROM 2.20.07CHS (translated).
I received a clue from mamaich :
Create a "Priority256" key under HKLM\drivers\builtin\wavedev and set it to 128 (0x80)
First results are promising!
mmm looks like I am talking to myself in this thread.
Anyway: The registry hack worked fine for me. Even better: the GB-Tweak applet I allready have does just the same (via the Audio priority option).
I am now very happy with the 2.20 translated SE ROM for my Himalaya. I might just keep on using it until my Wizard arives in two weeks 8)
Had the same problem, tomtom stutterd, GB-Tweak did the trick.
Thanks for the help.
Andy
I've been trying various versions of dcd's mods hoping to remedy a problem with my mogul. It seems that my unit locks-up/freezes when all of the following are true:
1. Bluetooth is on
2. Phone is locked
3. Goes into sleep mode
When i try to awake phone; none of the buttons work; simply black screen and needs a soft reset. This does not happen all the time, just enough to be annoying.
Any thoughts? Is this a radio 1.47 problem??
Thanks guys.
bump. i have the same problem with DCD 1.6.8 Rom. i thought it was codyppc battery/performance hack so I uninstalled that(still happened), then i thought it was s2u2 so i uninstalled that( still happened today).... so any ideas?
can we verify whether this happens on dcd_titan_1.6.10 rom with NO software, tweaks, etc etc installed? it does not happen for me (i have been using BT lately) but that doesnt mean it wont happen for you guys.
Are you by anychance using S2U2 with the Power Off setting?
I was having this problem, and since I've set S2U2 not to Power off the phone, I have not had this problem. Being going well over 24 hours now.
Mine also freezes/locks up from time to time. I'll make the changes in S2U and see what happens.
Sorry for the newb question, but what is S2U?
got it; slide to unlock.
Is this app worthwhile?
I'm running 2.17 ROM and I get this error, although I'm NOT running S2U2
I have got the same problem. I just flashed to custel 1.1 6mb pagepool (awesome rom for alltel users) had no time to install anything extra paired bt locked phone about 10 mins later tried to make call and it was froze. i did however find out if you constantly use the bt it dont freeze (I finaylly installed ms voice command and if i constantly ask for date or time it stays unfroze.).
edit: I just upgraded to radio v2.13 ( ftp://xda:[email protected]/Titan/Radio_Roms/titan_2.13_CDMA.rar ) totally cured bt reception problem on both ends but once again same problem phone freezes. helppppp!!!!!!
Hope someone can help.
I recently started to re-use my HTC HD2 after almost a year of non-use.
It is a stock handset running WM6.5 on the O2 network in the UK.
As I hadn't used the handset in a year, I had factory re-set it so, once I inserted my SIM card, I had to run through the set-up process.
Once done, the handset was working fine.
After a few days, I decided to change the ringtone from the default O2 one, to another one.
However, since doing this, the handset never rings when I get an incoming call and only vibrates.
I have factory reset the handset several times but this makes no difference.
I have searched on the internet and found some details of people with similar issues, but the recommended fix of creating a 'volatile' directory is not working for me.
Does anyone have any experience of this issue and can advise how to resolve?
have not experienced the same but some thoughts below ...
Does the speaker work when playing audio file via music player or from file explorer.
If no sound from speaker try blowing into grill left of camera or taping that area while a file is playing.
If speaker plays sound try removing SD card & test, also check & try a few changes in, Settings>Sounds & Notifications>Notifications & see what results you get !
Final option could be HSPL4 & load HSPL2.08 & try a smooth running standard style custom ROM such as CleanEX RV Standard 1.02 as should be a far better WM experience than the O2 branded ROMs ...
Thanks for the reply Mr B.
I have only just got round to checking this post but, yesterday, for some un-known reason the phone is now ringing as normal.
Very bizarre!