Related
Greetings!
As mentioined in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=418150&highlight=issue+list I have encountered similar problems.
I own my TP for 3 days (2 nights) and on both mornings after being charged over the night the TP was absolutely unresponsive and only to be awakened by a soft reset. It couldn't receive calls, and the alarm of course didn't work also (so I missed one this morning - but wasn't late at work) Anyway, this is a serious issue to me, since it makes the phone absolutely unreliable. And I am not in favor of doing regular hard resets by the way ...
Help on this would be really appreciated.
Greetings, hugo
Mine does this everyday, but have you tried pressing one of the buttons like the home button, I know nothing happens for a minute but then it comes back to life with out the need for a soft reset
Haven't tried ...
Well, I haven't tried pressing a button and waiting, but this is not exactly the behavior, to expect from a phone of this kind. You see this wouldn't solve the Problem of not being reachable by phone and missing appointments. In fact I don't know, that how long I was unreachable on phone and in my profession this isn't just disturbing but unacceptable.
Hugo
I've had the same problem, not every time it's charged, but enough times to be a problem. I've switched off TF3D (Start, Settings, Today, Items, untick TouchFLO 3D, tick some standard items).
The problem has gone. Of course, so has TouchFLO.
Cheers,
Graham.
graham.hughes said:
The problem has gone. Of course, so has TouchFLO.
Click to expand...
Click to collapse
This could be of course a last resort, but TouchFlo is quite nice to use (although I cannot get TF to use PocketInformant as calendar app, although it is defined as standard - the original MS calendar app must be hardcoded somwhere ...). And of course as TF is one of the main features of this phone a great amount of it's costs are caused by that software. So if I couldn't use it, the phone would loose a lot of it's value.
Isn't there a sort of event log in wm6.1 to see, which event crashes the system?
Hugo
I get a similar problem in that I lose all sound overnight, so I too miss my alarms. I also get no sound through the earpiece so, although it vibrates when it is supposed to be ringing, I cannot speak on the phone as I cannot hear the other person, and it seems they cannot hear me either, so it obviously affects the microphone as well. I have done a hard reset but it still happens, so it's definitely a bug with TF3D. I know this because if I try to play one of my music tracks using the music tab in TF3D, it plays for about 5-6 seconds (obviously with no sound) and then it crashes TF3D and restarts itself, which sorts the sound issue out. No need for a soft reset here but it's still unacceptable as my alarms are useless, and for £500+ I don't expect such a stupid flaw in the software. Hopefully, a ROM upgrade will sort this out, but when that will be is anyone's guess at the moment.
matmaneyre said:
...so it's definitely a bug with TF3D.
Click to expand...
Click to collapse
That's also my conclusion.
matmaneyre said:
Hopefully, a ROM upgrade will sort this out
Click to expand...
Click to collapse
I think that's what we have to wait for. Until then, it's a choice between bland-but-working or cute-but-unreliable.
have you tried any of these little mem resident babys to get your ram back and kill bad things while it sleeps
http://forum.xda-developers.com/showthread.php?p=2136914
Hmm...I'm just wondering why not more people are reporting this? Anyone NOT experiencing this problem?
Not till now I didn't
Using Stock ROM
I am more and more convicee, that TF3D is quite a buggy piece of software (Aussen hui - innen pfui!). Additionaly to the described above, I got a "broken glass" effect yesterday.
I sure do hope, that HTC releases a ROM update soon, although up until now the Touch Pro isn't even listed on HTC's german support pages.
Maybe I'll give SPB mobile shell a try ...
Hugo
Having same problem, not all the time though.
koppee1 said:
Hmm...I'm just wondering why not more people are reporting this? Anyone NOT experiencing this problem?
Click to expand...
Click to collapse
I have the same problem...
A few times already... even this morning.
TP is totally unresponsive and had to soft reset it to get it back alive.
ROM 1.90.401.1 WWE
Radio 1.02.25.19
Protocol 52.33.25.17U
I've had the HTC Touch Pro for about three weeks now, and since then it's crashed or become unusable at least once a day. I do not believe for one second that these issues are restricted to my handset, and comments on this forum back that up.
Problems I've experienced:
1. TouchFlo 3D screen corruption - "broken glass effect". The TouchFlo interface appears fragmented and split - it continues to function, but is unwatchable. The OS and other applications are unaffected. Cause unknown. Cured by soft reset.
2. Complete screen corruption + freeze. The entire screen gets a still image that looks like 'white noise' - random black and white pixels. The device is completely locked. Cause unknown. Cured by soft reset.
3. Device fails to wake up. Screen has been powered down, either having been switched off manually, or by timeout. Device later fails to respond to Power button. Happens occasionally without warning, and frequently (almost 100%) during overnight charge. Note - leaving the Touch Flo interface on 'Programs' tab (i.e. not 'Home') during charge seems to alleviate this (I don't yet have enough evidence to back up this claim).
I like this phone and its touch interface, but am pretty disgusted by the reliability issues, which I would guess are largely connected to the TouchFlo 3D code and/or hardware drivers. HTC really need to sort this out.
I've had the alarm fail on two mornings so far, needed soft reset.
I'm going to try disabling touchflo I think. Be nice to have pocketbreeze running again anyway.
Just out of curiousity
Do you have your phone set to turn off the screen even if it is charging? I don't have the Pro... yet, but with my 6700 I used to have to ensure the screen stayed on over night if I wanted to have a chance at the phone actually being responsive in the morning so the alarm would go off. Otherwise it would be as your Pro's seem to be doing. Will not turn on or anything until a soft reset. (It is not a fix by any means, I am just curious if it is still the same patern.)
I never charge over night simply to avoid it being charged for 8 hours straight. I keep a charge kit at work, and charge during the day as needed. In less than an hour, I get full battery. Then, I sit it next to my bed at night with no failed alarms.
Maybe it doesn't like the long charges.
I'm trying DCS's ROM now to see if it makes any difference at all. I'll report back in a couple of days. Maybe if I didn't have to charge it so often it wouldn't be so bad!
Wether screen is on or not, it doesn't make a difference. (Why should it on a working phone?)
I sincerely hope, that if those strange behaviours are gone in non stock cooked roms, that there will be some in German language as well ...
I am looking forward to another night!
By the way, SPB Mobile Shell didn't quite meet my expectations. (eg. it has also the sucking MS calender hard coded)
Experienced the "non-responsive in the morning" problem 2 times in 3 days, without the phone being charged. Both times I had the white noise effect on the screen.
Turned off TF3D (I like the phone more without it, actually) and the problem didn't occur in the last 5 days since I did this. It's most likely a TF3D related issue and it will prolly be fixed by the next update.
-KickFlo
I've been having a problem since shortly after I got my Fuze, that sometimes on reset it doesn't want to finish starting up -- maybe on one out of three resets. It seems to hang just before starting TF3D. It's still semi-responsive ... the backlight brightness turns back up if I hit a button, and an on-screen button may react if I press it (though it doesn't get as far as launching the application or bringing up the start menu)
Usually forcing another soft reset via the pinhole button results in it booting just fine.
I'm currently using ROMeOS, but I've run into this problem with multiple ROMs, including the stock one. I don't think it's a hardware issue ... I haven't had any other problems that suggest the unit itself is bad.
I tried to figure out what I've done each time I've customized my setup. I stayed away from registry tweaks that affect things like caches or hardware performance this time, and still got the issue. I tried uninstalling some of the apps that I always use. No dice.
But I think I've narrowed down the issue. I uninstalled mun background4allpages, which puts the wallpaper you select onto every tab. After several resets, no problem. I'll continue to test throughout the day, resetting sporadically. But I haven't seen anyone else report a problem like this with background4allpages ... so I'm not sure this is it.
Anyone have anything like this, with any cause at all?
I have his problem every once in awhile with ROMeOS too. I'm not sure what causes it but I'll have to do three or four restarts before it continues on. I think it usually happens after I install an app that has a Today plugin with it. But I'm not totally sure about that but I do know if is after I install a cab.
Looks like a today screen hangup. I can fix it by going to the Today Items tab in settings->today then choosing ok (which causes today to refresh plugins).
imtribble -- I've never needed to do 3-4 resets to clear it. I'm not sure I've even needed to do 2. But I know in my case, it's happened without any cab installed since the last boot.
Sleuth255 -- I'd actually tried that (though not for that purpose) but it doesn't seem to have helped, at least not permanently.
With background4alltabs uninstalled, it seems like the problem is gone (at least so far). I wonder if it might actually be the collision of using both background4alltabs and manilla customizer to change my clock -- since I read somewhere that the files background4alltabs changes also affect the clock. If I can confirm after several more resets that this was the problem, I'll post something in that thread.
I'm just so confused that it only happens sometimes, not all the time. Odd.
Actually, Sleuth255, that may have helped after all. I reinstalled background5allpages, and the problem reappeared. But then I did the Today "OK" and haven't been able to make it freeze since ... so maybe. Will report back further after more testing.
It is not just on ROMeOS though, with my fuze the same thing happens and I am running elite ROM RC2. It is some kind of today screen hangup and sleuth's solution did not help me. It takes ~2-3 soft resets to get it working correctly. If I hold the power button to reset rather than pressing the stylus reset it boots up with no hangs though. Interesting.
mdow09 -- are you using background4allpapers? how about manila customizer (and if so, what have you used it to change)? anything loading in your startup group? trying to figure out what the common elements among people having this problem might be.
its happened to me on provens rom and when i had romeos
but a second reset always fixes it
Not using background4allpapers or manila customizer, the clsoest thing I am using to that is TF3D config. My senses tell me it is something to do with my secondtoday screen. My startups are as follows:
Answer key disabler
autoshortcut.ink
cleartemp.ink
filedlgchgs.ink
G-alarm reload
HTC startup
PKG.ink
poutlook.ink
startclean.ink
hmmm.... I've not gotten a permanent fix either, I occasionally hang up after a reset. When I have my issue, the start menu is operational and I can load programs etc w/o issues. It's only the today screen that's hung which is why I tried fixing it by refreshing the items list in today settings. I'm not running touchflo either if that makes a diff.
mdow09 -- It looks like the only things in common we're running are the processes that are always there. Nothing from an installed app.
Sleuth -- How long does the today/ok seem to fix it for? Do you do something in between that could be re-triggering the problem? I've done 6-7 resets since I reinstalled background4allpapes. I got a freeze on the first. I tried the today/ok and it hasn't frozen since. Been running various apps and doing various tasks in between the resets.
I -MAY- have solved this, or at least worked around it.
Previously, I tried uninstalling Background4allpages. That seemed to solve it, but I only had it uninstalled for a day or so. No conclusive word on whether it was involved.
I tried Sleuth's Today/OK trick. That seemed to stave it off for a while. Still came back. Possibly after installing new apps or doing other things that affect the Today setup. Not sure.
But here's my most recent attempt -- I moved TouchFlo3d (almost) all the way to the top in the list of Today items, with everything else (as normal) unchecked. You can't go all the way to the top, because the date entry is there. My working theory (based on nothing concrete yet) is that the plugins are loaded in the order in which they appear in that list, and the Today function isn't getting to load one that's problematic. Perhaps it's a similar issue - when the problem appears, Touchflo itself won't load because of another plugin that loads first, but each would be fine independently. In any case, pushing it to the top priority seems to be preventing the problem -- at least for now.
Obvious holes in my theory -- It seems strange that Today would still load unchecked plug-ins at all, though maybe it still does some sort of cursory scan of them. And wouldn't the problematic plugin still then load AFTER touchflo in my new setup? Maybe it is, but it's only causing a problem if it loads before TF3D?
As before, will report back after more observation ...
Wordsmith9091 said:
Sleuth -- How long does the today/ok seem to fix it for? Do you do something in between that could be re-triggering the problem? I've done 6-7 resets since I reinstalled background4allpapes. I got a freeze on the first. I tried the today/ok and it hasn't frozen since. Been running various apps and doing various tasks in between the resets.
Click to expand...
Click to collapse
Its intermittent for sure. I've not been able to peg down what causes it yet.
Anyone else finding that PhoneEx locks up on them after awile? Seems like a great program otherwise but 2 or three times a day I'll bring it up and it won't do anything other than hide and show itself. It won't navigate between favorits, calls, contacts, etc. It is completely unresponsive. Attempting to kill the process with MemMaid generally toasts the phone and I have to reset it.
Just wondering if I'm alone in this, or if anyone else has discovered a magic combination of things that may be leading to this.
AJ
Well I can possibly answer my own question. On a hunch, I disabled S2U2 from automatic startup and I haven't had PhoneEx lockup once since.
Would suck cause I like S2U2, with PhoneEx I can ditch about three other programs I've been using, so I guess if it continues to work I will have to do without S2U2. Or perhaps I will try fiddling with it to see if there's a particular setting in S2 that is causing this issue.
AJ
Although since removing S2U2 the PhoneEx lockups have diminished in freqeuncy, they haven't gone entirely. I woke up this morning to find that PhoneEx was unresponsive, but, as is always the case, the rest of the system works normally (I haven't yet received a call with it in this state - it will be interesting to find out what happens).
Has no one else experienced this problem, or does no one else use PhoneEx?
AJ
PhoneEx
I am... for about 4 days on two phones...nothing like that happend...yet and hopefully never does. love s2u2 and PhoneEx...i personally do not use phoneex to answer the incoming calls...i let the s2u2 to do all the job including the notifications....which is better to let s2u2 to deal with them so you won't get any conflicts...take care
Ps.
by the way a new version it's gonna pop up any day now 1.4 the russians done a new improved version it take about four times less memory(about 300kb instead of 1000 kb) and fixed some bugs to it...it's out there already but only in chirilic language...the only problem i have so far is that i can't use the speaker button it kinda do weird noise when activate as if the speaker it's to close to the mic.
PhoneEX
I does not lock up for me, although it took me 2 days to note that the keboard locks during a call and you have to unlock it to use the keyboard (could that be your problem?)
I do have another problem though and that is if I do a soft reset for whatever reason PhoneEx then spends 3 or 4 minutes "Intialising Contacts" before I can use my HTC Touch HD.
Anyone got a solution for this.
Sam
iconsoft.com (phoneEx)
phoneEx is a great program. my friend has it and he has never had a problem with it on his windows mobile device.PhoneEx is a great program people with a windows mobile device should definatly look in to the program . i am curenty using the trial i am about to get the program i am looking forward to it i canot wait i can already see its going to be great . my phone is doing great with this program i love it and thanks Iconsoft you guys are really smart for putting the program on there . you can get the program by going to www.iconsoft.com
i recomend it it is a great program
Installed PhoneEx (no to answer phone) on my Elf today after a week of using S2U2 - and had four lockups already. Any hope for this? *trying again with the "don't use keyboard lock " setting set to true as per another thread/post.
Hey folks,
I have been having a lot of problems with my X7510 lately. The screen keeps locking up in standby mode. When the device is in standby I turn it on and it prompts me for my password. After putting in my password I just get a black screen with the word "password" at the top. While the device is in this state I can still sync (and see all of the files on it) when I connect to my computer. The screen on the device, however, is locked up. This problem has been happening several times a day lately and I cannot receive calls when it happens (nor do I get any indication of missed calls). The only way to get the X7510 to work is to do a soft reset.
At first I thought it might have something to do with the password manager, so I turned the password off today. A couple of hours later I found it locked up anyway. When I pressed the power button it did not come on at all, though the GSM and BT/WIFI lights continued to flash.
Is anyone having this issue? Were you able to figure out what was causing the problem? I am very frustrated right now. My device locks up so much that it is practically unusable since I have to do a reset 2-4 times a day.
Yes- I'm seeing the same issue from time to time. Haven't had time to investigate yet.
Last time it happened was yesterday- Green and Amber lights were flashing, but all buttons unresponsive, and had to do a soft reset.
Running PocketPlus 4.03 as a front end.
That is probably a software issue. Better enumerate your softwares and find out the common one causing it. Usually start with the last one you installed prior to having the problem.
cktlcmd said:
That is probably a software issue. Better enumerate your softwares and find out the common one causing it. Usually start with the last one you installed prior to having the problem.
Click to expand...
Click to collapse
I agree it's definitely a software issue. The only recent addition for me has been Spb Keyboard. PP4.03 has been on since day one, and did not initially seem to be associated with lockups.
When I have time, I'll try and narrow it down a bit.
I have not installed any new software in over six weeks. The only thing that has changed in the last week is an update to IM+. I have uninstalled it completely and will see what happens. If this fails I am not sure what to do.
LocoHarami said:
I have not installed any new software in over six weeks. The only thing that has changed in the last week is an update to IM+. I have uninstalled it completely and will see what happens. If this fails I am not sure what to do.
Click to expand...
Click to collapse
Just for the record, I don't use any sort of Instant Messaging!
With my Advantage on the ultra-extreme blinks I suffered the tortures of the damned, tortures of the damned. No less than once every couple of hours I'd find my device locked up. Upon direction from my kind forum mates, I decided to uninstall the last software change on the not-so trusty X7510. After removing the IM+ software the PDA still locked up two more times that day. I gave up hope and decided to do an hard reset.
The next day, however, it did not hang up at all. The same goes for today, so after locking up five times a day for a week I have not locked up once in the last 48 hours. No hard reset and all is viddy well, little brother, Viddy well.
Unsure if it was the IM+ update or not, since it locked up twice after the uninstall, but I will not be reinstalling the IM+ update. In the name of science, I will install the original version this afternoon and see what happens.
Most gracious thanks to all those who took time out to reply to this thread.
I can concur that 3rd party software running in the background is usually the culprit.
In my case, I'm having an on-going saga with Hebrew localization bought from P.D.A.C. If I put the device to "sleep", with the email program set to download every 15 minutes (via wifi - no SIM installed), I come back to find a device that will turn on when the power button is pressed (a bit longer than usual), but then no response from any hardware button or screen - a soft reset via the hole in the back is the only way out.
I can in general say that the localization has other problems, like slowing the device down, and generally causing unpredictable hangs, but I'll save that for another thread.
To their credit, PDAC have taken a stab at trying to fix it, but since they don't have (and apparently don't intend to purchase) an HTC 7510 for testing, it's become a slow, hit-or-miss proposition.
One of the problems for gadget fiends like me who are not programmers is choosing a device that isn't massively popular - the support by third-party developers is not adequate. So here I find myself trying to learn how to fix what should work properly out-of-the-box.....and being frustrated by lack of background/knowledge.
-avi
Had this lockup problem since i received the device.
The other week in an attempt to fix this i have flashed to the latest 3.29 Rom from cmonex (thanks!) with ExtRom 3.29. As i have a Chinese x7510 version this ExtRom has fixed Opera text block problem, but still had constant lockup after putting unit into sleep mode.
Yesterday, i tried option 'Do not lock buttons' in Key Lock under Settings. Since I have not had one single lockup! Even having in sleep overnight, hit power button and up pops today screen. Normally i would have to soft reset.
This is what i have done so far. I'll have to start installing apps and see how it goes...
G'day from LA
Hi AvantX,
Another Aussie here, but living in LA for the last 7 years.
I loaded cmonex's hard SPL on to my x7510 some time ago, but so far I've been loathe to load an other ROM on to my x7510 as I have been unclear on the return path to the stock rom in the evet of a mishap. I've been hoping to see some ROM development on this forum similar to Kaiser & TyTN but so far we have not seen too much, other than the promise of AP4 amd MichyPrima's ROM somewhen.
Can you show here some screen shots of the 3.29 ROM? Does it look the same as the stock ROM and how does it run compared to the stock ROM? The stock ROM is 3.27.405.3 - is 3.29 an improvement? Does loading 3.29 affect the radio - mine is 1.58.
Thanks mate in advance.
Hello,
Here is my issue, i have the latest TAEL Sense ROM from December. My phone just hard reset when i put it on charge while it's powered ON. This has happen on 3 occasions and does not occur when the phone is OFF and charging.
Here is what happenned the last time. Battery was low, just plugged the phone in for charging, came by after 1 hour and saw a miss called, tried to get to the call history screen, but impossible, HTC Touch Sense was not responding.
I was able to get to the windows 6.5 application menu while using the HOME button. Then I used the reset shortcut to reboot the mobile.
Took a long time to reboot(Normal boot screen) and then gave me the Stylus configuration screen, and booted up again to configure TAEL sense rom.
Then everyting gone, contacts messages,... like a fresh HARD RESET...
Does anybody have a clue why this happen ?
Could there be some issue with my battery charger ? or USB Cable ?
Or is this a ROM related issue.
Thanks for your feedback on this one.
thanks for the heads up, man. pretty much the same as in my thread: http://forum.xda-developers.com/showthread.php?t=613653
and i did forget to mention that both times it hard-resat itself, it was charging as well.
update: it resat itself when i got to work this morning, after being on charge all night.
same here 2 month ago with new Romeos: HR while charging...
did you solve it? any patterns?
Charging successful when mobile is OFF
Last night, i put my mobile on charge all night while it was switched off. when i booted it this morning, everything seems working fine... no resets...
There might be something going on with some applications that are installed on the mobile ?
all i had: calendar and contacts backup. t-mobile mms size fix cab, fuze keyboard fix cab. try leaving it on while charging!
disabled touch flo, put it on charge - nothing so far.
no resets so far - disabled the touch flo. any other feedback?
never mind: put it on charge earlier today and once i opened the keyboard the theme layout changed to stock, so i assume it's going to hard-reset once again
2 resets in one day
There has been 2 resets, yesterday night... i have tried to disabled HTC Sense and install Mobile Shell. but the OS was really unstable and when i rebooted was already hard reset... i wasn't charging the phone... seem to me, that this is an issue at the windows mobile 6.5 level... i'll post a link on Tael Roms page, maybe other persons have the same issue.
flashed back to stock 6.1 - no problems so far.
I've had the exact same problem, but with my Touch Pro 2. I started a thread here, but got no replies so far. I'm wondering if something in custom ROMs is causing this.
that's what it looks like. since reverting back to stock 6.1 no resets whatsoever. knock.knock.knock.