Related
I have been using the new XDAII for about three weeks or so and already I have experienced over 6 times critical crashes that caused the device to not even be able to restart after reseting. Even more troubling is that even when pressing the on/off button and hard reseting, the problem still cannot be solved. The only way I got around it is by actually removing the battery and letting it sit for a few minutes, put in the battery and then performing the hard reset. Of course, then I lose all data that was previously on the device. Right now, what I do is use the xBackup program to back everything to SD card and just wait for the device to crash. Then ultimately recovering. I can get around, but this is really quite annoying.
I have written to O2 about it and they said something about a radio version 10513A0, and that if this is the version (and it is), then I need to either register (which I did and wait for some upgrade), or send it in to O2 collection point for repairs. I really don't want to send it in because then I would have nothing to use (since its both phone and PDA). I just don't see why O2 could not just simply fork over the upgrade software. Also, I have experienced twice that the device would suddenly no longer be recognized by Activesync (newest version). It would automatically connect as GUEST and nothing could be done about it. No shuting down Activesync and restarting, or rebooting computer or/and xdaII, or even removing and reinstalling Activesync could solve the problem. Again, the only solution I have is to perform the infamous full reset, wipe out the whole xdaII and then everything works again.
Anyway, all of this is really killing me here, just wondering if anyone has experienced this kind of situation and maybe have some advise.
By the way, the Bluespoon Digital seems to work fine with the XDAII although sometimes it does crash and a pairing must be done again, but definitely not like the Jabra 200 problem.
I had the same sort of problems with my first XDA-2 and as time pasee the problems got worse, So i returned it to o2 and got another one, same software and hardware versions, but this time with no real problems
John
XDA II Critical Crash
I have had the exact same problems as you experienced and was about to throw that gadget out the window... but then
Following advice received from an XDA II owner I tried the following:
I hit soft reset each time upon seeing the red text in the lower right corner 5 consecutive times. Then I waited and my XDA II came back to life effectively performing a soft reset rather than having to do a hard reset. Fascinating, let's see whether you have as much success !!!!
Thanks for the tip... I'll try it next time it happens again! However, I'm still wondering about the ROM v 1.06 and that Radio software upgrade. Thanks!
I'm also finding the XDAII needs a hard reset more often than the XDAI (although fewer soft resets). Had to do it twice last night, very annoying. Interesting tip about the soft reset at the boot screen, will give that a try next time.
O2 really should do something about it!
Ya, I totally agree. All this reseting and crashing and recovering is really not acceptable. The product features are definitely good and they did make some improvements, but this kind of quality is a definite downgrade. Even O2 admits that if your radio number is 10513A0 then you should send it in to a collection point for a software upgrade. They also insisted on registering which I did, but I just don't understand why they could not just simply post a downloadable software upgrade or ROM upgrade so that we don't have to be without a device. After all, we are talking about something that is both your PHONE and your PDA.
The ROM upgrade is definately necessary. I sent mine in and after that, no hangs whatsoever. No more hard/soft resets at all either. :lol:
if only it was so easy
I would have sent it in, but since I am traveling and don't live in HK, there is just no way to send it in. Besides, it takes about a week, which means nothing to use during the time. O2 really should be more considerate about this. If this was just a functionality upgrade or a boost in bells and whistles, waiting is reasonable. However, we are talking about crippling disfunctionality in a US$800+ device, they should atleast have the sense to post a fix to solve the problem. I heard something will be released in January, I wonder if this is confirmed. I am really sick of waiting. After all, MDA and T-Mobile supposedly already have something out. If they don't do something soon, I would really reconsider anything from O2 next time.
I have experient the same problem on my XDAII, and after 7 times hardreset during 14 days business trip in USA. I send it back to O2 and wait for the solution(already 1 week pass). And even a hardreset sometime could hardly be reached. You need to try 6-10 times. I think it should be a hardware problem because I acutrally upgrade my rom to a newer one(and not the english version), and after two days, I lost my phone function again. I have faced the same problem on my older PPC phone once(LENOVO ET180) and after I send it back to the vendor, they said the mainboard has failure, need to be replaced. After doing so, it works 6 months without a hardreset. I saw the same issue on PPCSG and PCCW.net, they all send their PDA+Phone back to the service. I think you better do it now as maybe there is no a ROM upgrade could solve the problem.
Goog luck. and if without those issues, it is really a perfect PDA+Phone. I love it. When I faced those ****, the only thing I could think is to buy another XDAII
I've the same problem
I've tried your tip to restart my Mda2 with XDA2 rom, and it works!!!!!!!!!!
Now I'm looking for a new Rom upgrade to change my radio version...
Still I think it's the solution and not to replace the radio hardware...
Cant Trust My XDA II
Well it's now Dec 2004 and I ALSO have the same problem.
I've only had my XDA II a couple of months and already I'm quickly loosing my patience with it!!
It crashes at least TWICE a week causing me major headaches.
If I was abroad and it did this I would be in severe trouble.
I brought this as a business tool and I'm afraid it is to unreliable to place
my trust in...
I have the latest ROM update installed
I can ill afford to send it in because it holds my customer base,
day to day stuff, Navigator and many other stuff I use on a daily basis.
"O2, what can you do for me?"
Topdog38uk, what software have you installed - especially any today plugins?
rgds,
Alex.
sigh... i haven't had such a problem since i bought it..... till i update the new rom from O2 uk site... now i feel like throwing to on the ground lolz. anyway i just installed WM2003 SE upgrade mysterman from the forum and 1 crash so far.... :roll:
How bad is this alignement issue...
and pls write down your SN..and hermes type
I got Ht626 on O2 Trion..
Thanks
Subject edited:
TyTN: ht630f21xxxx
No problems yet accept SPB backup screws up the .NET CF so Tweaks2K2.NET no longer functions after a restore...
This ticks me off :evil:
One more lovely issue
If I soft-reset the device while it is being powered via USB (doesn't have to be sync'd, just being powered) the device locks up at the Windows Mobile Splash screen...
Fo Some reason SPB Backup screws the registry during a full backup (yes, it is installed to main memory) so I have to restore with no registry then restore a backup of the registry with Resco Registry...never had to do something so stupid with a new PDA
Someone seems have found the root cause (in japanese)
http://forum.xda-developers.com/viewtopic.php?t=62063&start=25
I found the issue to start after a week, starting on the right hand side, and then moving towards the centre of the screen. Happens all the time now.
Voda v1605 S/N - 626
Somebody with the problem needs to disassemble their TyTN and power it up with the front cover completely removed and the digitizer assy loose. If there's a mechanical issue based on the gaskets or some other case ideoysncracy, the alignment issues will immediately disappear. If my TyTN starts acting up I'll do this myself. We need to divide this problem to conquer it by answering this first all-important question:
Is it Hardware, Software or a combination of both?
HTC's own repair kit tends to indicate that its hardware and that the above test will resolve any issues. However, there have been reports that software changes solve it too and these are backed up by a compelling video that shows a person tapping on the same spot of the kbd SIP and sometimes it would register the correct key and sometimes it would register the key to the right of the one tapped. If the problem were hardware, this wouldn't happen; the offset tap registration would happen consistantly.
Sleuth255, unfortunately it is a hardware issue.
HTC is replacing faulty units and repairing (changing the LCD) if you don't have the original box.
rdtce said:
TyTN: ht630f21xxxx
No problems yet accept SPB backup screws up the .NET CF so Tweaks2K2.NET no longer functions after a restore...
This ticks me off :evil:
Click to expand...
Click to collapse
rdtce said:
If I soft-reset the device while it is being powered via USB (doesn't have to be sync'd, just being powered) the device locks up at the Windows Mobile Splash screen...
Fo Some reason SPB Backup screws the registry during a full backup (yes, it is installed to main memory) so I have to restore with no registry then restore a backup of the registry with Resco Registry...never had to do something so stupid with a new PDA
Click to expand...
Click to collapse
What? Ehm... I use SPB Backup... and I havent still done a restore... So, I'm afraid of something pranky behaviour if I must go to restore a backup ...........
pof said:
Sleuth255, unfortunately it is a hardware issue.
HTC is replacing faulty units and repairing (changing the LCD) if you don't have the original box.
Click to expand...
Click to collapse
I partially concur. Here is the video that I referred to earlier which, after closer examination, has made me change my opinion as to its root cause:
http://www.youtube.com/watch?v=FQIVv4b2jOI
(notice how his alternating finger pressure on the right side of the case is causing the alignment to shift right by one char).
Nevertheless, I still see posts such as this one which point to a software related cause as well:
mcalbala said:
I had the alignment issue, and the phone started to slow down, I bit the bullet and reimaged the phone (clear memory and reset to factory default), reinstalled software and resynced, and the problem went away totally - seems to be part of the software for the Tytn - Good that it doesnt seem to be hardware related
Click to expand...
Click to collapse
Maybe there's two completely different issues that are being tied together here.
save yourselves the headache and send it for replcement ...!!
:roll:
@sectorlord: I'd say hard reset first and run for a day w/o re-installing any software. If alignment problem re-surfaces, send it in because you've got the hardware problem that HTC has identified.
Why be without your TyTN if its not hardware? Remember: I'm not disagreeing with the hardware hypothesis here. It's obvious that one cause of screen alignment problems is digitizer/case related. What I'm saying here that there may be two seperate issues here, both of whose effect are screen alignment issues. If this is true, posters following the "just send it in" rationale who actually have the second software related issue, will be sorely disappointed when they get their TyTN back after an indeterminate wait based on regional service differences because the problem will crop right back up after they restore from backup.
I myself can't ignore data just because it doesn't fit the model. Calling this problem solely hardware ignores the data that I posted above from mcalbala as well as countless other posters who have reported similar success from hard resets.
I guess I'll just have to wait for that first post from someone who sent their TyTN in for the fix only to have the problem crop back up to see if my "two problem" hypothesis is correct.
I agree with you... I know some people have success getting rid of the issue by :
1) Hard reset
2) Upgarding ROMs
3) Loosening up the screws
4) Offsetting the calibrations
5) Unticking the USB-PC options
etc ..etc..
I tried all of these, and my unit improves but never totally fixed. I am trying to save you the headache I got.. if you can swap it..do it !
I returned my Trion, and bought a new Dopod838pro WWE HT636XXXX yesterday...
Knock on wood... It's a gamble on my part. I just trust Dopod HK, that they will release these units when this issue is resolved, and they release it last Thursday starting with HT636XXXX.
Is it fixed...I dont know... but surely I will be screaming on SIS if not..
:twisted:
Few days ago I received my repaired tytn back. SN HT627.
According to the serviceburo it should now be repaired according to the instruction of HTC.
parts used:
1x Gasket, Keypad.Apache For.
1x MYLAR,LCM CONN, BREEZE FOR
So, hopefully this really solved the problem.
Regards,
Piet
Sleuth255 said:
@sectorlord: I'd say hard reset first and run for a day w/o re-installing any software. If alignment problem re-surfaces, send it in because you've got the hardware problem that HTC has identified.
Why be without your TyTN if its not hardware? Remember: I'm not disagreeing with the hardware hypothesis here. It's obvious that one cause of screen alignment problems is digitizer/case related. What I'm saying here that there may be two seperate issues here, both of whose effect are screen alignment issues. If this is true, posters following the "just send it in" rationale who actually have the second software related issue, will be sorely disappointed when they get their TyTN back after an indeterminate wait based on regional service differences because the problem will crop right back up after they restore from backup.
I myself can't ignore data just because it doesn't fit the model. Calling this problem solely hardware ignores the data that I posted above from mcalbala as well as countless other posters who have reported similar success from hard resets.
I guess I'll just have to wait for that first post from someone who sent their TyTN in for the fix only to have the problem crop back up to see if my "two problem" hypothesis is correct.
Click to expand...
Click to collapse
Reopening the question: A week ago suddenly the notorious screen alignment problem appeared on my device. Never had it before, now every 2 hours, sometimes after 10 minutes already. In my case the SA-problem has several appearences: one time it misallignes a bit to the right, the other time a far end to the left. But always in horizontal line. B.t.w.: in landscape mode the alignment problem always was gone!
So finally after trying everything I knew (from XDA) I did a hardreset with the intention to send it back for repair. But now after the hardreset my SA-problem seems to be gone! I'm testing for hours now, do everything what might cause the problem but nothing (till so far). I only installed TomTom 6 after the hardreset...
Could this be software (programs or settings) cause after all?
Howdy all,
Well, I sure have learned a lot lurking around here in recent weeks. After an iPAQ fiasco a couple of years ago, I gave up on the converged idea. But then the 8525 came along, and Amazon.com put them on an amazingly affordable sale, so I made the leap again. It's been much better this time around, but I sure have high hopes for WM6 (if my recent "upgrade" to Vista is any indicator, I'm going to be deeply dissappointed!).
Anyway, new problem developed as of late. I have spb backup set to execute at 3:00 each morning. Every time this program runs, I get two registry keys being reset. They are:
HKCU>ControlPanel>Backligh>BatteryTimeout (being reset from whatever value I input to "7" of all things)
and
HKCU>ControlPanel>Backligh>LockLevel>Locklevel (being reset to "1," needs to be "0" for any change to the above key to take effect).
Any ideas about this? I found in another forum that I am not alone in having this problem, but I did not find a solution. I have not had sbp backup for long, so I don't know enough about it to know how to prevent it from making such changes. Or why it would in the first place...
Thanks all!
Hi again,
so i recently fixed my keyboard issue and to lighten up darkness: it was not a software-issue.
after playing with the thought of returning the phone to tmobile, i flashed the "new official" tmobile-DE rom, and the tmobile service center told me, that this would void my warranty because the rom hasn't been downloaded from the offical tmobile-DE website... so i discarded the option of returning the phone in the next few month
toda i woke up and retried my hardware-keyboard on the vario 2, i recognized something which was: the reason for the vario dropping so much keypresses, was a bad contactivity... i mean: i can hear the key i press "clicking" but no char appeared on the screen... so i disassembled the vario 2 todays morning, and searched for a way to fix this, a way to give the keyboard a better fitting, or somewhat like that. the difficultest thing was to remove the "void"-label without tearing it... took me about 15 minutes to remove this damn label, but it remained intact
after that, i systematically disassembled the phone, and i did the following things to the keyboard-parts:
removed the white label which was on the "contact-side" of the keyboard-circuit
realligned this label and put it back on the circuit
then i put the keys and the circuit back into the housing, and got a piece of paper
i cut this to be as long an high as the circuit itself is, and put 3 of those paper-sheets onto the back of the keyboard-circuit, then fixed the 3 sheets a little with the flex-cable connecting the keyboard to the main-circuit.
then put the phone back together an tested it
my keyboards working like a charm right now, i'm so happy that my phones completely working again, without returning it
i thought this might help someone who has got same problems, perhaps my keyboard got this malfunction after the first drop, i do not remember when this problem occured the first time, and actually... i don't have to anymore
greetings from germany
garfield
this is the orignal post said:
hellow to all
so i'm using my hermes (MDA Vario II) for as much as two months now.
I dropped it two times, first time 20cm onto carpet, second time 40cm onto the street -.-
but as far as i can see, not much damage, some scratches, nothing to worry about.
since i have this phone, i flashed several roms onto it. Black/Faria/Schaps/t-mobile_shipped/dopod wm6/black wm6 final/and many others... even some of my own roms got tested in there
i wasn't able to test the shipped status for very long, because i flashed the first custom rom about five days after hardware-arrival
the one thing driving me insane at the moment is the f**king hardware-keyboard. sometimes the "red dot" (for the second assignment of the keys) gets locked, without me wanting this. or i press "space" and nothing happens, or even worse, it adds some crazy special symbols to my sms wich then extends to four or more sms...
the e and w keys sometimes do not respond, and worst case ever had: keyboards gets fully locked up... had to soft-reset.
during the testing of the many custom roms, which were pre-finals, (in contrast to wm6-release versions), i thought: "yes everythings working, and the keyboard driver is producing crap". but even with the dopod rom (wm6) now active on my hermes, i have problems described above.
may it be the 1.50 radio? should i go back to 1.47?
or is it an hardware issue? should i return the phone to my loval mobilcom-store?
its driving me insane, i have to recheck every word two times... and i have to correct many things... actually i'm typing very fast, and this lowers my typing speed by, lets say 2000%
looking forward to hear your ideas,
will be grateful for every idea, which gets me some closer to a solution...
greetings
and keep up all your good work
garfield
(sorry for typing bad english (if i did so), at least im german)
Click to expand...
Click to collapse
There can be software issues that cause freezing and perhaps laggy behaviour on the keyboard. However, from what you describe, I tend to think it's primarily a hardware issue. (Possibly made worse or even more annoying by software slow downs for unrelated reasons.
If having used different ROMs, key behaviour is still largely the same (eg the same keys respond poorly or require harder presses) then I suggest you have the not uncommon hardware keyboard issue:
Keyboard dismantling pics:
http://forum.xda-developers.com/showthread.php?t=319315&page=2
If changing ROMs leads to varying issues with the key board, but the behaviour of the keys changes ie different keys cause problems then it could either be software or the keyboard ribbon cable is poorly connected.
Mike
thanks for the link,
actually i thought about disassembling my hermes, but then again thought about warranty because its just 2 months of age...
i'll test the keys some more, especially the space, e, w, and "reddot" seem malfunctional... will keep an eye on the keys, and if original WM5 rom does not help, i will reflash the phone to factory default, and return the phone to my nearest store... they will have a solution and if it will be a replacement i'll be happy with it either
greetings
garfield
hi @ all...
sorry for digging this thread out
but recently i recognized my keyboard to be malfunctional again.
with "again" i mean, i thought it worked quite good for some time (lets say a month or so) but for some tome now, i assume 3weeks now, my keyboard throws the same annoying malfuntions as it had done the time i opened this thread. perhaps i ignored them for a while, so i haven't recognized the malfunction, but maybe my phone was really "cured" for some time.
Note: i've been running on the official dopod wm6 rom all the time since i opened this thread. WM% and WM5 original didn't help me, so i decided to stick to WM6. i've just tried 3 different roms, and two pandora self-cooked-roms in the last hour, and tested my keybard very much.
but it seems to be faulty... it lags some keys (in fact "reddot", e, w, space, colon (as a result of the reddot hang) and sometimes i get the "reddot" locked with only pressing it a single time. three words later i recognize that i am writing crap
so... any remainig ideas? or should i return it back to t-mobile?
i tried wm5/6 several roms
also tried various radios, at the moment running on 1.54...
if i want to return it, what do i have to look out for? should i flash it back to original t_mob_101_shipped_rom? and should i restore the original SPL?
i've simunlocked the phone... but did'nt SUPERCID it... always used the Hard-SPL 2.10. Is there any way to bring my phone into a state in which it would be possible and safe to return it?
greetings
garfield
fixed my problem (see first post)
As weird as it may sound, my prophet is not loading up successfully since this morning. It was working well until last night and for no reason seems to have lost it's way.
I see the Splash screen with the IPL / SPL etc. information and then it proceeds into the blue Windows Mobile Screen (Windows loading screen) and doesn't get any further.
Has anyone faced a similar problem earlier and have a resolution to it. I do not want to Hard Reset my device at the moment.
I had this problem last time but it worked after n soft resets. I'm sure today I have far exceeded that number n in doing a soft reset on my device. Any help is appreciated.
Thanks,
Umesh.
O2 Neo (WM5)
Feasibility of a probable solution
Read this solution on another forum and thought of bringing it up for discussion here.
It said that these PDA phones have backup power source probably as a battery / capacitor to store ROM data in absence of the main battery. In case of situations like mine where the boot sequence is probably hitting a deadlock or some other problem , it might work to drain the back up battery / capacitor completely.
This might force the PDA to look for a fresh boot sequence or default.
Is this a possibility ? Do the senior members / experts here believe or know anything about this. I feel it's worth a discussion, if so.
Thanks,
Umesh.
The probable solution!!!
Hi
I had almost the same problem and I guess you maight have done the same mistake.Have you newly installed any weather forcasting programs which install some plugins into your TODAY SCREEN?If yes,it is the one which is responsible for your failure.(Many of plugin installers in today screen may cause the sme problem)
Hope you can succeed with resolving it.
puzzled
Have you tried start up minus the SD card...?
amiromario said:
Hi
I had almost the same problem and I guess you maight have done the same mistake.Have you newly installed any weather forcasting programs which install some plugins into your TODAY SCREEN?If yes,it is the one which is responsible for your failure.(Many of plugin installers in today screen may cause the sme problem)
Hope you can succeed with resolving it.
Click to expand...
Click to collapse
I did install the HTC Home Plugin but I'm also sure that did not cause the problem cause I had it running great for about 3 weeks now. The last software I tried installing on my device was Merriam-Websters pocket pc dictionary. It had some flash card feature which ran at start up and to my surprise the morning (without restart) before my cell went into the struggling mode. But unless it reloads itself, I cannot do anything about any of the softwares.
How did you resolve the same problem with your device. Did you also have to do hard reset ?
Rivendell63 said:
Have you tried start up minus the SD card...?
Click to expand...
Click to collapse
I have tried with and without the SD Card - that had got my prophet working last time I had this problem but unfortunately, this time not. I even tried pulling it off at different intervals while the cell is stuck in the load mode, but to no luck.
You'd better to...
umesh said:
I did install the HTC Home Plugin but I'm also sure that did not cause the problem cause I had it running great for about 3 weeks now. The last software I tried installing on my device was Merriam-Websters pocket pc dictionary. It had some flash card feature which ran at start up and to my surprise the morning (without restart) before my cell went into the struggling mode. But unless it reloads itself, I cannot do anything about any of the softwares.
How did you resolve the same problem with your device. Did you also have to do hard reset ?
Click to expand...
Click to collapse
Hi
Actually,I installed a POCKET WEATHER, a weather forecasting program which installs some plugins on today sceern.Then my problems with the device(same as your)started to appear.I waited for 2 or three days,but finally I found the solution in removing it from my device.Once I deleted it,my device returned back to its great condition that it had before.I guess, you should ignore and put away those programs which leave a trace in today screen.Don't ask me why(Cause I don't know that much!!! )but I heard about some subsequent problems with your rom's cash, or something.You'd better removing them and I hope they will help you to solve the problem.
I did not have any luck and had to hard reset my device. I had not done it even once since I brought this handset about a year ago and am only glad to have done this now. Just realised how slow my device was working with all the software installs and uninstalls I had experimented with it over the year.
I did loose some data - but in the end a fair trade off.
hard reset keys dont work
Hi! i got the same problem, i installed an updated TouchFlo in my phone, but it hangs at start up, so i tryed to hard reset the phone, BUT my phone is a chinese clone of pharos 3470 / dopod P660 and the hard reset keys dont work (camera + power + reset) i have been trying diferent combinations of keys but i cant find any solution.
does anyone know a possible way to hard reset a phone?
i did it before, but from inside the windows settings and it worked well, but i cant do it with the keys, and i cant get in windows settings when it is stucked at startup
please help!