I have searched this and could not come up with any fixes, but here goes.
On my 8525 most of my front buttons would quite working (Send, End, OK, Start Menu, and Both Top Menu select buttons) on every Cingular 2.06 Rom. This would be a daily thing that could be fixed by a soft reset. Then I upgraded to XDA Live 2.0 everything worked great for a while when all of a sudden all of the front buttons stopped working, all of them except the dpad. I did a soft reset and even a hard reset, and every time it would still not be working. I freaked out the only thing I could think to do is to downgrade to the original Rom 1.34 that was on it when I received it so I could try to send it in for warranty. After the downgrade all the buttons have been working now.
So in my mind I am thinking this is a software issue rather than a hardware problem. But if that is the case what would cause this? Is there any kind of fix?
I really want to put WM6 back on my device, but not at the cost of my hardware buttons.
Any help or advice would be greatly appreciated.
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Never heard of this problem before. There is a fix for the 8525 keyboard in the XDA Live extras, but I'm almost certain it doesn't affect the front buttons.
I'd almost say that its a problem physically with a broken/barely connected button membrane or something similar.. and the action of you moving the phone to reset it/pressing the button is enough to connect it again.
If you're sure its working 100% now, try flashing XDA Live again and seeing if it kills it again!
Philux-X said:
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Click to expand...
Click to collapse
Just a couple ideas. First, what 3rd party apps have you installed after upgrading and have you changed anything in the "softkey" program? Also, when you said you did a hard reset, was it a real hard reset, or just a power down? Some people at first get the two mixed up.
Also, the radio and bl wouldn't have anything to do with a problem like this.
Like TAURUSBulba said, I would think that it HAS to do with some cab/registry or executable you install that is common to all the ROMS that makes it do this. I would suggest you check out your installed applications and research what might create this problem.
The Rest was an actual "hard reset" with nothing else installed on phone except for system files (fresh system). I did not think the BL or Radio would have anything to do with it, I just wanted to be sure. I will try to re-upgrade to XDA Live 2.0 again when I can find some extra time. I will post results if anything changes or I continue to keep having this problem.
I appreciate your feedback.
Thank You
Related
Hi experts...
Well, I have just recently upgraded to WM2003SE with ZeroXtreme modified ROM. Lately, while I was using my xda 2, probably it process pretty much heavy task and got hang. I did a soft the first time, it was somehow froze at the splash screen. Thought I waited longer than the usual time it'd load to windows, impatiently I soft reset the second time.
Surprisingly It proceeded to the align window which was actually done by hard reset. I was still puzzled even now, wonder whether it does happen like with the upgrade or just on my machine.
However, before this happen, I did somehow accidentally got my xda 2 knock against the ground quite lightly and a little scratch was on my baby's... Not sure if that was part of the cause of the auto-hard reset?
After reinstalling all applications back, I did some trial and error to test if it reoccur by soft resetting a few times and pressing multiple buttons simultaneously or any other way that I could think of to test out.
And so far it didn't auto-hard reset again. But, sometimes, if I soft reset it, it'd froze at the 2nd splash screen (the first splash screen where it displays the rom version,etc for short). Hence, i need to soft-reset it another time to get back working.
Experts please give advise or anyone experience the same occurence please do share. thanks.
Hi buddy,
The hang/delay while soft reset seems to be a common problem for 2.06 ROM. I have the same problem as well. Someone suggested the XCPUScaler could help a bit and it does....well, not totally. Sin from Australia suggested a merge of 2.02t and 2.06 ROMs can resolve the problem. I haven't try it yet but if you would like to give it a go, do a search in the Forum.
Have a great Christmas!
Cheers!
Check the DB_notify_queue database as it might contain lots of records ... use CheckNotify to clear it as the clearnotify.exe fix doesn't
P.S: it shouldn't contain more than 20 records in average
Biso007 said:
Check the DB_notify_queue database as it might contain lots of records ... use CheckNotify to clear it as the clearnotify.exe fix doesn't
P.S: it shouldn't contain more than 20 records in average
Click to expand...
Click to collapse
Hi!
I use CheckNotify and check that they were 21 records. I guess it's normal then, since you said it shouldn't be more than 20 records. So, do you think I should still run the "clearfix.exe"?
I was just puzzled, how on earth that it could hard-reset by itself, when I was expecting a soft-reset on the machine.
I tried to recollect how was it possible to happen, and I thought it could be due to the one time that it slipped off my hand and knock on the ground lightly while I was trying to snap a picture that's closed to the floor. Other than these, I'm not too sure what's the cause could be, cause it might be too technical for me to discover :?
I think this is the problem of using non-official rom, especially main one. I have similar problem but not that serious. This is our trade off as no one force us to flash our rom.
Sometime I think it might be hardware problem too, as my wife is using 1.66WWE (I did not flash her machine), it sometimes hard reset automatically too... Also, everything change sim card - even if the 2nd battery is full, it still lost all the data.
Might be the machine is too complicated or might be this is a common feature of all the windows products.
Hi all,
I have Qtek S200 (Prophet).
I tried several WM6 ROMs, but all attmpts ended with following problems:
- after few soft resets the machine starts forgetting e-mail accounts
- the same time BT problem apears, all pairings are gone and are not saved anymore
- the problem appears sometimes directly after the flash, sometimes it can hold correct state for 2 weeks, but no version is stable in long time
- if I unlock ExtROM I have it with name like "Extrom2", so all apps which you cook to be at Extended ROM do no work
Currently I had to go back to WM5, because I need the BT and e-mail.
Am I doing something wrong, or it is common problem? How should I solve this?
thanks
Jaba
at first try to use the "search" function, these problems were discussed alot of times
lepus said:
at first try to use the "search" function, these problems were discussed alot of times
Click to expand...
Click to collapse
Yes I did
But any of proposed solutions like hard power off or email recovery program does not solve it.
Hard power off is instead of "saving" data generating the problem with 100% "success".
I did not find any other solution .... just something like "you are using it at your risk, nothing is guaranteed"
I cope with this ... but I'm sure I'm not the only one, who has the problem. Maybe someone had realy invented something ....
I'm also trying to provide the clue: Extended ROM is in my case renamed to "ExtRom2". Why?
Maybe the Extended ROM changed name can cause the data are not saved?
If there is no solution, I will accept it.
that's ALL
thanks
jaba
you do now that you generally should NOT use the stylus to reset the device? That causes these errors..
Da9L said:
you do now that you generally should NOT use the stylus to reset the device? That causes these errors..
Click to expand...
Click to collapse
Nice advice, but my dear machine has tendency to reset itself occasionally with no reason. WOW ... here it comes.
It's not so often, but even one self-reset in 2 weeks is enough to make problems.
Do you have any clue, if WM 6.1 solved this?
My personal opinion is that it can have also link to "forgetting" PIN password with reset. The mechanism is the same. After reset some data are lost.
Or it can be connected to renamed Ext rom? I'm able to many tweaks with WM, but this one is out of my reach.
You know ... I'm looking for real solution rather than for workarround like "do not reset it"
Maybe nobody knows... Than OK. But let's to say it clearly.
If there is no known fix, the WM6 on Prophet are unsable for real life, maybe it can work as a gadget to play with
thanks
jaba
Let start by telling I don't have a solution either, sorry.
But... I can't remember encountering this problem of spontanious resets, nor have I red about someone else suffering from it. Perhaps you are looking in the wrong direction by pointing to WM6 in general as the cause of your missery. Perhaps you should have a closer look at your hardware. Just a suggestion.
As for the gadget part. I am using WM6 for almost a year now, even for proffesional (PDA, GPS and email) use, and it haven't failed me more then the original WM5 ROM. Perhaps I'm one of the lucky few, who will tell...?
rondol1 said:
Let start by telling I don't have a solution either, sorry.
But... I can't remember encountering this problem of spontanious resets, nor have I red about someone else suffering from it. Perhaps you are looking in the wrong direction by pointing to WM6 in general as the cause of your missery. Perhaps you should have a closer look at your hardware. Just a suggestion.
Click to expand...
Click to collapse
I suppose, this is not matter of HW. Under WM5 there are no self-resets. They appeared as I begun to try WM6. When I reflashed back to WM5, it's stable again.
But this topic satified my hunger for information
There is no hope for me to have stable Prophet with WM6. I will stay with WM5 and start save money for new toy.
thanks for response
jaba
Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Just for future reference...never has your phone been a brick. A bricked phone is just that...a brick, a paperweight, won't do anything at all. It can't be turned on, it can't boot, it can't be reflashed or fixed. It's obvious you're having a problem with something, but I constantly see people on a daily basis saying their phone is bricked when in actuality, very very few people have actually bricked phones.
Sorry, but I have no idea. You're apparently alone in facing this.
Have you tried reflashing to another third party or stock radio/ROM combination to help rule software or a bad flashing out as a cause?
mrfantastic said:
Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Click to expand...
Click to collapse
What bootloader are you running? Maybe a bad install of the bootloader?
no, that's not a possibility, the bootloader isn't like a copy of Windows... besides, it's getting stuck on the windows mobile logo, that means its at the kernel.
my advice is to dump that ROM and flash something else.
Olipro said:
my advice is to dump that ROM and flash something else.
Click to expand...
Click to collapse
In case that is interpreted negatively, quite a few are using builds from my kitchen and he's been quite alone in reporting this.
Sorry, I just had to chime in to defend my work.
That said, if one is facing such problems the first avenue to problem solving is not to keep flashing the same radio/build of an OS ROM into perpetuity. Mix things up. Isolate.
I'm not saying i'm 100% positive on this one, but sounds like to me he's using some kind of software that is coded poorly, or something that is corrupting his kernel or the necessary files that boot the os. Sounds like the phone is getting hung up right when it's trying to execute these files at boot.
My advice to you, that is if you want to keep using key's rom, is to create a CLEAN rom, and don't install any software. Run it for a while clean and see if the problem goes away...if that's the case, you need to re-evaluate which software you use.
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
This is a very misleading title for this post. You can't unbrick a true 'brick' - unless it was a brick because you left the battery out.
A true 'brick' can't ever be turned on. It's a dead paperweight. So, there's no chance of unbricking it.
Flashed Keys rom to few phones....never had a problem !
I used olipro 2.40
Right now the phone is fine, it appears to happen randomly, Keys rom is great otherwise (no insult intended). What was meant by the problem with HTC home?
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
Click to expand...
Click to collapse
The windows mobile splash screen or the "silly green screen that says windows mobile" as you put it is not HTC Home. It is not HTC Home that is causing him to lock up at boot time.
To the OP, read my post, it's some piece of software that is causing your lockup. Guaranteed, if you make a clean rom (no software installed except the rom, with nothing cooked into it) I bet you see your problems go away. I then would install each piece of software one by one testing to see if you see the lockups after each one.
help
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
kaos29205 said:
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
Click to expand...
Click to collapse
Kaos,
You will find you get more answers by posting in the appropriate thread. This is not a WM6 thread so chances are that most ppl would ignore your post.
As you are probably on dcd 3.0.x, I have answered your question over there in the dcd 3.0.4 thread. http://forum.xda-developers.com/showpost.php?p=2177772&postcount=459
Apart from the fact that your are more likey to recieve an answer when posting in the correct thread, it will also help others with the same problem find the answer wheb they do a SEARCH.
Also another good place to find general information is in the titan wiki (see the sticky at the top of the titan upgrading section).
Lastly, you could try starting a new thread if you just cant seem to find the appropriate place to get your answer.
So I looked around and couldn't seem to find the answer to this anywhere.
Why exactly do you have to Hard-Reset after flashing a new ROM? (When the screen calibration comes up) I have almost never Hard-Reset after flashing and I haven't had any troubles what-so-ever, so why is it recommended? I certainly haven't seen any improvement the few times I did Hard-Reset. Is this a ticking time bomb to not do it, or is it just more likely that something will go wrong if you don't Hard-Reset? Is there some underlying damage I'm doing to my phone? To me it seems like it works fine without a Hard-Reset, why spend the extra time?
Any insight?
-Hobadee
Hobadee said:
So I looked around and couldn't seem to find the answer to this anywhere.
Why exactly do you have to Hard-Reset after flashing a new ROM? (When the screen calibration comes up) I have almost never Hard-Reset after flashing and I haven't had any troubles what-so-ever, so why is it recommended? I certainly haven't seen any improvement the few times I did Hard-Reset. Is this a ticking time bomb to not do it, or is it just more likely that something will go wrong if you don't Hard-Reset? Is there some underlying damage I'm doing to my phone? To me it seems like it works fine without a Hard-Reset, why spend the extra time?
Any insight?
-Hobadee
Click to expand...
Click to collapse
i think you might find your answer if you read this post #25).
http://forum.xda-developers.com/showthread.php?t=448008&page=3
hope it helped you
When you flash a stock rom with the HTC ruu, it automatically does the hard reset for you. The hacked, custom ruu's skip the hard reset (so you can flash a radio or splash w/o the hard reset). I couldn't tell you why thr hard reset is necessary, but if HTC seems to think it's important, then that's good enough for me.
semsem1969 said:
i think you might find your answer if you read this post #25).
http://forum.xda-developers.com/showthread.php?t=448008&page=3
hope it helped you
Click to expand...
Click to collapse
Perfect, thanks! Sorry I couldn't find it with search. :-/
Hobadee said:
Perfect, thanks! Sorry I couldn't find it with search. :-/
Click to expand...
Click to collapse
Meh..
1200+ posts. Enjoy reading. Maybe I am lazy. I always leave SIM and SD in and rarely HR after flash. You can always hard reset (free, no charge)
When you are flashing more than once a week, and better yet, cooking a new rom more than once a week, you won't bother reading drivel (you won't have time).
You'll get your own feel for the need for another HR after flash. Pattern-seeking is basic human nature. You'll figure it out
Hobadee said:
So I looked around and couldn't seem to find the answer to this anywhere.
Why exactly do you have to Hard-Reset after flashing a new ROM? (When the screen calibration comes up) I have almost never Hard-Reset after flashing and I haven't had any troubles what-so-ever, so why is it recommended? I certainly haven't seen any improvement the few times I did Hard-Reset. Is this a ticking time bomb to not do it, or is it just more likely that something will go wrong if you don't Hard-Reset? Is there some underlying damage I'm doing to my phone? To me it seems like it works fine without a Hard-Reset, why spend the extra time?
Any insight?
-Hobadee
Click to expand...
Click to collapse
You want to reset after install because it helps clear any left over data and the rom will load from phone and not activesync. The best way to do it is to install the rom from sd card then reset. This helps make sure you get a good flash. I havent had a bad flash in along time but it does happen.
Always perform a Hard Reset after every flash.
AFAIK, you do need to reset between ROM flashes; the loader and Custom RUU were changed to allow for flashing of Radio, ROM, and Splash - so not all areas are reformatted during flash. Most chefs perform the Hard Reset when the Stylus Calibration appears - I used to personally wait until TF3D so as to ensure that all post-reset processing has completed successfully.
For a while, I was skipping the Hard Reset ... then I spent 30 mins trying to figure out why files were was missing from Application Data, Content, and Music. As a rule, I now perform these steps:
SD Card ROM Flash
Hold Volume Down & Action
Push Reset
Perform reset phase & wait for completion
Press Volume Up
Hold Volume Down (enter bootloader)
ActiveSync (cradle):
Similar steps can be performed while connected via ActiveSync (cradle):
Power Off Phone
Hold Volume Down & Action & Reset
Power On Phone
Perform reset phase & wait for completion
Press Volume Up
Hold Volume Down (enter bootloader)
USB connects, launch Custom RUU
Reference
http://forum.xda-developers.com/showpost.php?p=3673222&postcount=790
http://forum.xda-developers.com/showpost.php?p=3966093&postcount=7
hilaireg said:
AFAIK, you do need to reset between ROM flashes ...
Click to expand...
Click to collapse
I never hard reset, unless I experience some major weirdness and I (almost) never have any issues. Sometimes I have issues when I switch from lets say EnergyROM to NATF's but really rare.
I never reset any other devices I flash (I have flashed so many different types of phones, routers, ipods and so many other different devices.)
hilaireg said:
AFAIK, you do need to reset between ROM flashes ...
Click to expand...
Click to collapse
I thought you hard reset after the flash?
DJGonzo said:
I never hard reset, unless I experience some major weirdness and I (almost) never have any issues. Sometimes I have issues when I switch from lets say EnergyROM to NATF's but really rare.
Click to expand...
Click to collapse
Few things to keep in mind: frequency of ROM flashes (i do many while chef'ing), ROM size (going from larger to smaller can cause unpredictable results), device non-volatile settings (the area of the device that contains altered settings such as registry, file additions/removals, etc.).
DJGonzo said:
I never reset any other devices I flash (I have flashed so many different types of phones, routers, ipods and so many other different devices.)
Click to expand...
Click to collapse
Some devices operate differently. From my 25+ years experience in the business, I've run into several issues where a factory (hard) reset cleared up the problems experienced post-firmware update. I've even had situations where uploading the backed up configuration would cause the device to halt/crash.
magicman0 said:
I thought you hard reset after the flash?
Click to expand...
Click to collapse
In the very beginning, I used to Hard Reset twice, once before a flash and then once after a flash. Noonski posted a more efficient method which eliminated one of the Hard Reset and ensured that the device always functioned as anticipated. See steps and thread noted above that contains Noonski's observation.
I've been using the noted methods above since then and have never run into issues as I had before.
I hard reset twice, too. The first one is so quick, there's no good reason not to-it may help the flash go properly as well. I don't hit volume up, though. When the reset is done, I just go straight to bootloader and flash from my card. Then I do the second one at the tap here screen.
Still, sometimes funky things happen in customization. I always remove the sim card, but occasionally instead of getting a soft reset after customization, the stupid dialer will pop up, as well as the 'customization will start in 3 seconds' pop-up. Then the phone freezes. This happened a couple days ago to me, and voice command and gscroll wouldn't work. A 3d hard reset got me going, lol.
Hey!
I've noticed that in a few applications (or settings) i have issues with my touch-input. This is e.g when changing the default ringtone i can't just tap "ok" but have to press the "ok" button from the side with my whole finger, otherwise it won't be regocnised. Sometimes when using the keyboard, the buttons on the right side are very hard to use. That would be the "p" "l" and "backspace". Have anyone else had this problem? The weird thing is that sometimes it works perfect, but sometimes it's just a pain in the ass to get things done?
I think sometimes the touch screen can just not work properly, just luck of the draw I guess.
Has yours always been like this or is it a recent change? I am assuming its always been like this.
if it has then its a hardware failure (most likely) and will need to go back under warranty for repair.
If its a new change, then what has happened to cause it? Could just be a new rom or something causing the calibration to be off.
It hasn't always been like this. Lately it has begun to screw with me. And i don't think it has anything to do with luck, since it's always the same programs that do this. e.g. changing ringtone, accepting the google maps license on first run etc.
One could think this is a hardware failure, that's what i thought at first, but the strange thing is, that the same "area" on the screen works prefectly in other applications. I've tried several roms, but they all act like this. Perhaps I should install the stock rom and try with that.
I have a similar issue, and even more, sometimes once I am pressing the screen, the keys are starting to "dance" like the hero is trying to think which button to choose, by itself, and I am watching it, and smiling :-(
I've had it since SenseHero 1.5 and others as well. I just reinstalled the official htc rom and calibrated again the screen... but I am afraid the issue is still there, though less frequent...
Next week at the doorsteps of Orange I guess
Possibly is lag related?
Maybe the phones memory management is not working very well on the ROM you have installed and is causing large amounts of lag that the phone is interpreting touches (or not touches).
Lennyuk said:
Possibly is lag related?
Maybe the phones memory management is not working very well on the ROM you have installed and is causing large amounts of lag that the phone is interpreting touches (or not touches).
Click to expand...
Click to collapse
Possible, But with all the speed tweaks, task killer and stuff, maybe even the overclock widget that I started to use only after this issue appeared... don't know, have no idea how to solve it.
Now it is like beginning, with official htc rom, no additional apps installed neither contacts, and still, I have this issue.
Suggestion?
Got the exact same problem.
Almost exclusively buttons on the bottom of the screen and as you already said the right part of the keyboard (especially the goddamn backspace drives me nuts sometimes!).
It hasn't always been like this, started somewhen after flashing more than just Modaco I think.. And the severity varies a lot, sometimes I got barely any issues and then again I can't even finish an sms. Unnerving.
At htcpedia someone who obviously has the same problem pm'ed me his solution:
Your Problem with Screen
I had to wipe everything of.... installed the WWE original ROM, then re-root the phone and now working with Modacco 3.1, seems to be working ok now....think the problem was with LOX latest ROM.
Click to expand...
Click to collapse
I think - not sure - it startet with some lox rom for me too. Do you remember which Rom you were using when this first occured?
Well anyway, might give it a try.
I haven't tried it yet for 3 reasons:
1 - the link for the german version of the original firmware is down
2 - i don't have a windows computer, so the .exe is pretty much useless for me
3 - I'm way too lazy as currently it's not that bad
same problem
hye there, I seldomly post here..
But i got the same problem before... keyboard dances, hard to click OK... could not finish a sms without swearing F*** F***..
yep, its a hardware problem.. maybe its bcoz of the shape of the hero making its touch screen easily damage.. Not sure though..
flashed so many roms, to try to fix this problem.. thought it was a software issue.. but.... nothing..
went to HTC care centre.. and changed the touch screen (warranty, had to revert everything to stock) and now...
Good as New with Villain 3.4
hope this helps...
Oh thx guys. "Happy" not to be the only one with this issue. For starters I'll try the solution with the original rom. I think I still have some version of windows installed on one of my harddrives. If it don't work I'll have the screen changed. I'll report soon.
rehet said:
hye there, I seldomly post here..
But i got the same problem before... keyboard dances, hard to click OK... could not finish a sms without swearing F*** F***..
yep, its a hardware problem.. maybe its bcoz of the shape of the hero making its touch screen easily damage.. Not sure though..
flashed so many roms, to try to fix this problem.. thought it was a software issue.. but.... nothing..
went to HTC care centre.. and changed the touch screen (warranty, had to revert everything to stock) and now...
Good as New with Villain 3.4
hope this helps...
Click to expand...
Click to collapse
When you revert to stock Rom, do you need to reinstall a stock recovery as well? or is it automatic? because I reverted and when I try to boot into recovery with "power + home" I get a kind of error: the symbol of a triangle with an exclamation mark in it, and a phone symbol lies down beneath it.
Is there another way to go into recovery? or is it not installed actually? (I went back to the official RUU from htc site).
Thanks for the help.
Ok, I've just tried the solution with the stock rom. As a matter of fact, it does fix the keyboard-issues. However, some of the other random touch-input-issues still persist. I can't really see how this could be hardwarebased, since the same area on the screen works in other applications just fine.
The official rom from HTC completly restores your phone as it was when you got it. You'll have to install your custom recovery again, as you did the first time.
I had a similar issue.
A fix for this: VillainROM6.1-Full-signed.
Now, keyboard its ok.
Try it.