Related
When I was using Helmi's 1.3.2 rom (I have since switched back to the latest WM2003 rom) I had some odd, seemingly hardware related, Issues:
*Back light randomly turned on and off, programs opened and closed and did random things, then the device would reboot.
*It would just randomly reboot.
*I would get a "Problem with bluetooth hardware" Error message when trying to scan for new devices some times, and I would have to soft reset.
*I could not turn off the screen in WMP while using A2DP
*The device would shut off completely and wouldn't turn back on occasionally, and the only way I could get to turn back on was to plug it in. After doing that, all the version numbers on the first boot screen would read "NONE" and I would have to soft reset the device several times to get the wireless working again.
I have taken very good care of my SX66 (I have only dropped it once), and these problems worry me...has anyone else experienced these?
I had also a lot of trouble after having installed a new version of WM5, because I forgot to wipe the memory clean (check step 9 - and especially 9.2 - in http://wiki.xda-developers.com/index.php?pagename=Helmi). Just repeating this step will solve it... it dit for me. that's another thing I won't forget anymore
Hello everyone,I have the Vanilla ROM. 1.4 I believe, what has happened is that I had a friend look at my blue angle because he was considering getting one himself, he went to my Mobile Shell application from SPB, activated the portrait view (took time to load and he did not know that) so he decided to press is like a lot!!
So it tried to do landscape/portrait mode a lot! so we rebooted the thing. Then another problem came that the phone locked itself, and when trying to unlock the phone nothing worked, (press the "*" again to unlock the phone) that did not work at all.
After spending a lot of time I fixed that, then the screen alignment/navigating with the D-Pad was all screwed up, I managed to get to the screen alignment program and fixed that. Now I have this serious problem.
The phone cannot connect to my service provider (Cingular). And here is the funny part... Hard Reset does not at all!! very strange. Using a backup file I had useing SPB backup that also did not work.
(also I tried draining the backup battery and that did not work as well, guess the volatile memory thing in WM5 worked).
Please someone help me in this problem as I cannot use my phone! :'(
Fixed
Sorry about the post, I have fixed it by doing
http://forum.xda-developers.com/showpost.php?p=1164331
worked perfectly, reset the phone easily and now restoreing with a backup.
But if anyone can please tell me why Power/Reset did not do a hard reboot?
Hard reset is not enough
I've flushed my phone about 50 times during last two weeks.
I think, that there are some cases, that same data or state of "things" can survive flashing and hard reset. At least using helmi_c or my ROM.
Simply test: flash any helmi rom, turn on wifi and/or set button lock to wake up only using power button and perform hard reset. State of lock button is not changed, wifi tries to connect to any access point. Even reflashing with the same rom is not enough.
I'm guessing only: I think, that there is small bug - reset procedure checks validity of any particular block (or blocks) of data and skips initialization of same data it if is looks valid.
Maybe you have got the same.
The following (long!) post was originally posted at the PointUI forum, but I thought it best to cross post it here. I've tried to organize it as best as I can and appreciate those with the patience to read it and the good will to offer help.
------------------------
My AT&T Tilt (HTC TyTN II) is basically out of commision right now, and I can only track the source of the problems back to the latest update of PointUI (v1.02b, Feb. 4th 2008), as I've done nothing else with the phone since. However, seeing as how I've uninstalled PointUI and the problems persist (and are getting worse), I suspect a virus is afoot, or some other lovely problem.
Since the update, I've experienced the same problems as everyone else on this PointUI thread (system hangs on "running apps" screen and randomly), but in addition to that, several other things. I am running the stock AT&T ROM without the bloatware. These have been my symptoms for the most part since then:
Periodically, animations between menus would slow down considerably and sometimes freeze for a moment, even when I had nothing else running in the background. This would happen for any menu: the cog, the bottom bar, favorites, etc.
The touchscreen would stop working (usually, only within PointUI). This usually happened when animations would slow down, but it would also occur alone, randomly. The hardware buttons would still work during touchscreen failure, usually, but sometimes they wouldn't, and I would have to soft reset.
Sometimes, the power button wouldn't work, and I would press it several times thinking I didn't do it hard enough the first few times. After ~20 seconds, the screen would turn itself off and on. When the screen was on, it would not responding to touches.
The PointUI top bar that appears when using any application would, at random, not work. By this I mean when I would tap it, it's like it wasn't even there -- the Start menu would come down, or the volume control, date/time, etc. depending on where I tapped it. Also, the top right button (red X, or the check mark) would not display correctly in programs or the today screen (a check mark when it should be an X, etc.), randomly, and would not be responsive.
Yesterday (Feb. 23rd), things took a turn for the worse. Here's what happened:
When I started up Tom Tom, the screen went completely non-responsive. Only buttons would work.
After exiting Tom Tom (in an attempt to restart it), the touchscreen would continue not to work, both in PointUI and regular old Windows.
Shortly following this, buttons would stop working, and the entire phone would freeze up. Couldn't turn the touchscreen on and off. I did a soft reset.
During startup, when it showed the AT&T logo, the screen dimmed itself to the lowest brightness setting (it never does this). It would remain this way all the way through the bootup process and into Windows as well, never getting any brighter. Even after going to the backlight settings and increasing the brightness, the screen would get brighter, but would never turn off.
Once in Windows, the touchscreen was completely non-responsive. Buttons would still work, but everything would move really slow.
The screen would never turn itself off. Also, when pressing buttons, the screen would never get any brighter.
After mashing the buttons a bit (in anger, yes, but lightly), the touchscreen alignment application came up, asking me to touch the screen in a few places. This worked.
Then, a call came in. The screen froze during the animation for the notification of an incoming call. Also, the phone started to ring, but within 1 second stopped. However, it would vibrate nonstop (my phone is setup to ring and vibrate at the same time) till the end of the earth!
At this point, none of the buttons would work, not even the power button. Did a soft reset.
This was followed by the same exact symptoms ~4 times (touch screen not working, never turning off and staying at the same brightness level, etc). Outgoing calls would work ok, but each time, a call would come in and freeze up my phone.
Eventually, after several resets, the touchscreen would work without having to mash the buttons to get the touchscreen alignment app running. However, it would still freeze on incoming calls (only).
Somewhere between all the resets, I realized that sliding out the keyboard would never switch the screen to landscape. I can still type and my text would show up on-screen, and screen taps still work properly (even touchflo), but all of this would occur while still in portrait mode.
Lastly, the power button would only work once. It can turn the screen off, but not back on, ever.
Somewhere, between the resets, I uninstalled PointUI, which did nothing. I also tried running Sprite Backup, which would never open (and still doesn't at time of writing)!
Before the PointUI update, none of these symptoms were present (earlier release was v1.01b, used since early January). After the update, they began creeping up, getting worse over time. I have installed nothing else since the update, and have only ever sync'd the phone with my computer to charge it.
Today (Feb. 24th), it started getting a little worse...
When I make calls, sometimes the microphone doesn't work at all. I can hear the person I'm calling, but they can't hear me.
Sometimes, the green phone button won't start the phone application.
Power button isn't turning off the screen anymore at all.
This is the current status of the phone. Weathered, battered and beaten, it marches on, still capable of opening the HTC Audio Manager and playing my MP3's in consolation.
Any help regarding the source of these issues is greatly appreciated.
Some additional notes/summary:
I am running the stock AT&T ROM without the bloatware.
I haven't dropped the phone or let it get wet.
I may hard reset sometime this coming week, probably Monday. The first thing I'll do is reinstall PointUI v1.02b, and maybe TomTom. We'll see how that goes.
You know, the more I read this post, the more it seems like a virus.
Man... just hard reset/flash a new rom and be done with it.
SH4YD33 said:
Man... just hard reset/flash a new rom and be done with it.
Click to expand...
Click to collapse
I thought the above was the reason we DIDN'T have WM viruses?
Virus + Hard Reset = Problem solved?
SH4YD33 said:
Man... just hard reset/flash a new rom and be done with it.
Click to expand...
Click to collapse
I agree, at least that way you know if its hardware or software related and you stop fighting a losing battle
MM
tsadek said:
I thought the above was the reason we DIDN'T have WM viruses?
Virus + Hard Reset = Problem solved?
Click to expand...
Click to collapse
That's why I haven't bothered with any of the anti-virus programs out there. Why bother having a constant drain on the system resources when you can do a hard reset, and restore all the cabs & hacks in under 30 minutes?
-Jay
Just an update here, my phone started acting up again ~5 days ago: freezing on incoming calls, not switching to landscape when sliding out the keyboard, never turning the screen off, etc. 3 days ago it got better, and I was able to run Sprite Backup and tried to restore the phone back to my pre-PointUI days. It had to reset, and on that same reset, Sprite didn't run -- the phone just booted into Windows, and all my problems came back.
Last night, I got a call that froze up my phone again. So I reset it, and by surprise, Sprite Backup ran and started restoring my phone. Now it's back to the way it was in January, and everything works perfectly! This backup was made before I ever installed PointUI.
Bottomline, no PointUI, no problem.
However, I should say that with v1.01b, I never experienced any of these issues. Because of my experience, I'm not giving any test versions a try, but I may install 1.03b, when it comes out. Definitely doing another backup before that too.
Thank you everyone.
Sounds to me more like a hardware issue, perhaps with your SD card.
I had the same issues you were havingh, but without ever having installed PointUi on my Kaiser.
I was using Dutty's Rom version 7 with radio 1.27.xx
only installed aps : TomTom and SPB brain training
So it would seem this is a WM or TomTom triggered issue....
My Kaiser just started doing this very same thing today. I'm running the standard AT&T WM6.1 ROM and have been successfully since December 07. I have a 6GB SD card with TomTom on it, also have had no issues until now. Today, the screen didn't switch into landscape upon sliding the keyboard out; the camera freezes and/or is unresponsive; power button doesn't work (on OR off; with or without SD card inserted); couldn't pick up a call earlier today; TomTom freezes when loading; WM player freezes while loading media.... I have not installed any apps on this thing since January. Seems to me like some memory corruption going on, possibly page file related.
I *did* notice that I had about 45MB worth of temp internet files cached and cleaned those up earlier today after these symptoms started. Didn't fix the problem though, but being low on main storage may have contributed to the corruption problem.
I had hoped I wouldn't need to hard reset my phone but here we go....
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Dr. Strangelove said:
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Click to expand...
Click to collapse
Few Tricks, Make sure you are not plugged in USB. Make sure you are not "fat fingering it." Some people use chopsticks to be sure. And Hold it for long after the Screen goes Black.
Believe me, I've already tried the things you said.
Although I successfully mananged in the past to hard reset my phone, I checked the threads and the following vid:
How To Hard Reset Kaiser:
http://www.youtube.com/watch?v=fZPzT_L2FZQ
Usually I am the problem, but this time I can't figure out what I'm doing wrong.
Just wondering:
Which part of the Phone (ROM) is in control of the Hard Reset part? (e.g.: Bootloader, Radio Rom, Regular Rom,...)
Use "Clear Storage". It does the same thing.
Also, JM is most likely correct. It is most likely an issue of how you are pushing the buttons. Make sure you hold only ythe soft keys first, using your fingernails, then push the reset tab on the bottom & hold it. Don't just push the reset & release, but keep it held down.
Based on your previous message about your phone being haunted - mine is too btw, I think it's because the soft buttons aren't being acknowledged by the OS - which implies some REAL big problems.
I took mine back to the T-Mobile store today where I got told that it needs to be sent back to their workshops to fix it... and then got told that "mostly they just send out a new phone".
My phone is exhibiting the following symptoms.
1) Green and Red phone buttons do not work.
2) Soft buttons do not work.
3) D-Pad and wheel work intermittently.
4) (and most strange) the back-space key on the slide out keyboard does nothing, and on the virtual keyboard it flashes (to suggest that the key is being pressed) but still does nothing.
I've tried to access the bootloader, and perform a hard reset. I'm now looking for the original T-Mobile ROM to install (which was why I went into the shop), as the issue around the backspace key implies to me that the issue is in the OS not in the hardware.
Jon
Thanks already for all the input.
I've been trying all weekend in every different possible way to perform a hard reset. Fat fingering is really no possibility anymore. I've used every possible tool I had (needle-nose pliers, chopsticks, pens,...) to eliminate fat fingering.
But nothing helped. Jon (a nice guy) might have given a possibly correct diagnosis for my problem. But it wouldn't explain why I still can get into the bootloader.
Problems since receiving my phone from repairs:
Backlight changed out of itself => performed Hard Reset
Phone pad pops up and seems to start dialing => flashed new ROM
Wakes up constantly after a few seconds from standby => performed Hard Throw against the wall
As you can see, my latest problem is that the phone automatically wakes up from standby after a few seconds. The weird thing: it only does this when I put it in standby, but it doesn't wake up if it enters standby by itself.
=> NOTE: This may support the 'fat finger'-theory: the Kaiser gets some sort of keyboard input due to faulty hardware. Therefore I cannot Hard Reset my device, because of the additional faulty input.
I've used the "Clear Storage" method to perform one of my hard resets, but this has to be solved. I will be sending the phone back for yet another repair.
Thanks again for your input everyone.
Problem found?
I think I found the problem:
I just noticed that the camera button is already pushed in halfway (like when you focus the camera before you take a picture). If I push the button gently, it immediately takes a picture without focussing (it does automatically focus before taking the shot, but not on my command).
Also, when I enter the camera app, it sometimes instantly focuses. Other times I cannot focus at all.
Hard reset is still no go.
Yet another thanks for your useful help.
Maybe found the solution?
Hi Guys...
I found that by tapping the base of the phone, it "unlocks" itself, thereby making it work. It's become *S*L*O*W* as hell, and I'm really tempted to ask them to take a look at it, but right now I need all the functions, so I'm holding off.
But, give that a try and see what happens!
Jon
Thanks for still answering my question. Go community!
Dr. Strangelove said:
...
I will be sending the phone back for yet another repair.
...
Click to expand...
Click to collapse
Last week I finally received a fully functional and working Kaiser (have been waiting for that since december...). I couldn't accept a disfunctional Kaiser coming back from repairs.
The problem did indeed seem to be the camare button that was stuck. I tried really hard to get it to unblock, but I didn't work. I must say, I didn't try your method (didn't think of it).
Still thanks a lot.
I am experiencing exact same issues on my Kaiser (Tilt), it randomly starts to type stuff in the phone application on its own and I can't do anything to stop it, I have replaced ROMs, SPLs, Radios, now using a shipped rom with shipped radio but still that problem comes up after a few days of usage and doesn't go away until I hard reset, anyone knows what I can do to fix it? it's probably out of warranty. I checked the camera button and it seems fine.
Dear buds,
I've bought a TD2 with WinMO 6.5 lately. I had lots of bugs and fixed them all but one...
After some time from bootup (after 1 or 2 hours) the sound of phone goes off without a reason. No sound from speaker, headset or volume control buttons. However everything goes well instead sound. Phone vibrates when get call, notifications and alarms vibrate without sound etc. My only solution to get back the sounds is soft reset. After soft reset everything gets fine...
I think this is a sound driver issue but... If someone to help or show the way on forum please help (because I couldn't find same issue on search)
Thanks in advance.
If there aren't any other programs causing this by adjusting your volume levels, It may be a driver issue and you'll probably have to hard reset.
This is a common issue when flashing a new ROM without hard resetting after.
Dear Bruce,
Thanks for solution suggestion.
I hard reset three times until I bought the phone but nothing changed. I'm using the official shipped ROM and I didn't flash any other ROMs.
Extra programs list:
Klaxon
SKTools Lite
Garmin Mobile XT (Because my Copilot runs only after first installing then crashes forever)
Sportypal
Google Translator
Could that happen because of wrong flashing at factory or service etc.? I mean, this phone is a Vodafone version.
In Turkey, Vodafone signal often goes off and usually my phone gets stuck when the signal is off. Could this be the reason for unloading driver?
The digits of my phone are here:
ROM version: 2.16.468.4 (67041) WWE
ROM Date: 11.12.09
Radio Version:4.49.25.17
The fact that it works for a short while after soft reset perplexes me.
You have verified your volume is on when the sound turns off? (Sorry I have to ask this)
Any other programs running at the time is stops?
GPS software can conflict with system volume and backlight, so maybe make sure Garmin is set to dynamic settings.
Other than that, I really have no suggestions as a hard reset has not helped.
Perhaps hard reset, test for a while and see if it fails w/o any programs. Then install one prog at a time until you find the cause.
There is a slight possiblity that it was a bad flash and the driver is corrupt, which would mean reflashing the stock ROM.
Sorry I couldn't be of more assistance.
Dear Bruce
Sorry for very late answer for your last post
It's sure the phone volume is on
I've been examining the phone for one week and tried some possibilities and still no way for the bug
First I hard reseted again, then didn't install any other programs. After 6 hours, the same issue occured.
I uninstalled CoPilot (which I didn't use after hard reset) then soft reset and wait, just only some hours later, the sounds went off again.
After several soft resets, I decided to play music and monitor if it happens. Then BINGO! The sound went off just after poor GSM signal. When the phone lost the signal, it temporarily locked itself. After 2 or 3 issue, the phone sounds went off.
I think, phone starts a search after signal loss, then it tries to execute rest after 10 or 30 seconds either the signal comes back or not. After some trials it cannot reload sound .dll and sounds lock forever. But after soft reset, everything gets fine again.
To be sure about signal loss, I took the phone in flight mode for one day and wait for the same bug and the second BINGO came Phone didn't show the same bug.
After all, I reflashed the official ROM of TD2 and tried the same things but nothing changed. It's sure that the bug is not due to the wrong flashing the ROM.
For now, I'm sure that the bug occurs because of poor GSM signal of Vodafone in my region. So the question comes
Is there anything (such as a registry tweak or vice versa) to make the phone not to lock itself while loosing the signal and searching? Or do I have a way to increase the signal sensitivity?
Thanks for the worthful answers.
Regards