Yeah, yeah, i know, have a lot of it on the forum, but, until now, i didn't find any real answer about it.
Sometimes i read that isn't hardware problem, sometimes i read that is.
Sometimes i read that need to change some keys on registry, but what keys?
The problem is the same of other users: the green and red key, videocall, Windows, Ok, "the left and right software buttons", the IE and Message buttons doesn't work. And the diretional buttons, the first time i press when i turn on the Hermes open the browser.
I don't know what to do anymore. That phone already stayed at the HTC Support for 3 months, and came back with the same problem. BTW, the HTC Support is a @#&ยจ%$$!!!!!
OK, atleast try a different ROM first, ie schaps or pandora naked???
IF it works on the newer ROMs then theres your answer.
Is the device a Tytn, Vario II, 8525 etc..?? ie let us know which brand it is.
I've tried a lot of ROM's, but not the newer ones. I'll try today. I'll try Pandora Naked and Schaps, in this order, and will post the results.
My device is a TyTN.
Tried the both ROM's (Schap's and Pandora) and still have problems with the buttons.
Hardware issue, suggest a 3rd party repair facility??
mrvanx, i've read something about the registry. Changing some keys in the registry i can solve this problem? Is there anyway to be something like that? I think, in a hard reset or a ROM change, the registry goes to the original situation. Therefore, if was a registry problem it'll be solve doing that HR. Am i right?
Like i said, it already stayed on the HTC Support for almost 3 months and they do NOTHING about it.
Anyway, thanx Mrvanx, i think that will be the solution.
Sounds like you're out of luck. I'm using an AT&T 8525 with WM6 and excluding the d-pad, all of the front buttons do not respond. The bug appears to be in the software since I, along with many of the other with this trouble, have attempted the hard reset are able to do so successfully (which requires holding down both of the soft menu buttons under the screen). I have also tried the hardware solution posted by another user and it was not successful with my device. Thanks for the remarks regarding HTC. I'll avoid sending my device to them.
Scg033, good luck. I'm trying to take my friend's TyTN and checking the registry. The seller insists that my problem is not a hardware problem. This is my last chance to try something. I'll try today and will post the results, anyway.
Well, i've tried to look into another TyTN's registry and made mine exacly like that one and... Nothing Happens. Still having problems. I think it's not a software problem.
Related
Hello,
First and foremost I should note that I tried searching the forums but I was not entirely sure what to search for. I tried a few different queries and they yielded negligible results for my issue. Now, onto my issue:
8525 with wm6 black 3.01
I have my 8525/hermes/tytn/etc/ set to turn the device off after 3 minutes of inactivity in order to preserve battery life. Sometimes, this poses no issues and I can just hit the power button to turn it back on when I need to. Other times however, and perhaps more frequent, I press the power button and nothing happens. Try as I might and regardless of how many times I press the damned button, it will not turn on. I have to use my stylus to do a soft reset in order to have my phone back in operation. Needless to say, this has gotten very annoying. I have since turned that feature off but now my battery drains far too quickly.
Is this a known issue or has anyone experienced similar issues? If so, is there a fix for this? If not, would ATT accept my phone for a warranty exchange with this greymarket software on it? If not, can I just flash it with an official ATT image and then send it in? Thanks.
It's called Sleep of Death... SOD... I had it and I flashed the official AT&T rom and havent had it since.
thanks.. looking into it!
How many apps do you have running. Where are they installed also. I currently run Black Majik, and NEVER have the SoD, or soft reset, so I think it's the stuff you put in your device that may be causing this. Flashing a new ROM wont always solve this, since you and I have the same phone, I think it's what you put in that may cause this.
ronfin44 said:
How many apps do you have running. Where are they installed also. I currently run Black Majik, and NEVER have the SoD, or soft reset, so I think it's the stuff you put in your device that may be causing this. Flashing a new ROM wont always solve this, since you and I have the same phone, I think it's what you put in that may cause this.
Click to expand...
Click to collapse
running? usually just whatever program I have opened since I have it set up to completely escape the program when I X out. As far as where things are installed, everything is installed on my device sans iGo.. However, this issue arised prior to iGo being put on my SD card.
Try this. After a hard reset, load one app to your device, let it sit, test it, and then do another. take your time. See if something you load is causing this. I did a HR on mine cause I had tons of crap on there, loaded stuff slowly and noticed the ButtonFlo CAB is what screwed my ROM from working good, so got rid of it. Since then, its awesome.
Leave the Black and go with JJ's Majik. Is the only ROM to date that hasn't SOD'ed me ... and I run the same apps, the same way, on all the ROM's.
http://wmblack.info/
is this so? i'm going to try at&t's wm6 for a bit, see howt aht works..
Don't belive so
I read a lot of threads regarding the problem, i tried AT&T and same problem, others had it with black, now i am having it with latest LVSW, may be a software problem, i had it using SPB WEATHER and SPB TIME, i hard reset install all but them, worked fine for two days, installed TWEAK2K2, problem came back, now trying without TWEAK2K2, but i doubt problem can be solved
My Opinion
been running through threads all over, just found out that there is no solution, because when a program pushes the unit to wake up from standby it freezes, this program can be weather, alarm, mail, active sync, and even a CALL can cause this, so it's a permanent bug in wm6 and PPC :-(
Does anyone else experience unresponsive Messaging, IE, ok, etc, keys?
I know there were brief threads about this a while back, and most were either not conclusive, or someone blamed the hardware.
I did a test, and flashed almost all current cooked and uncooked WM6 ROMs, and every single one of them has this issue.
Then I flashed WM5, and voila! No key problem.
Any ideas, or suggestions to further troubleshoot this?
TIA
Ali -
i have problems with unresponding keys too. I have too push very hard on the qwerty keyboard. Espesially the "U" key. No matter what ROM I use.
Sounds similar to what I'm referring to in this thread:
http://forum.xda-developers.com/showthread.php?t=319516
I can confirm that you're not alone. I have random problems with an unresponsive keyboard as well. It happens occasionally on all WM6 Roms I've used (currently on AT&T leaked rom), and without any discernable pattern. I don't THINK it is a problem with the actual keyboard hardware, but I've not tested this specific issue enough to be totally sure. Only a soft reset will bring the keyboard back, and then it may be fine for days. I haven't tried pressing hard on the keys to try to bring it back, as others have. If normal force doesn't work, then I will just reboot.
I hope this info helps.
Seems to be a common thing. I get this sometimes too. I have found it happened slightly less often with either Faria's super-clean or Black Satin. That could be coincidence thoguh.
Although a physical problem which requires the insides to be cleaned is something that could happen to any unit, there is an issues with Hermes keys failing to respond either quickly or at all in certain situations.
I'm honestly not sure if anyone's done enough testing to ascertain the exact circumstances that this can come up in, but it seems that a Soft Reset will always sort it as you'd expect - except for 'physical' problems of course.
Im also getting this problem now and then.. It just happens when im using the keypad allot, or typing faster then the ppc can put it on screen it seems.. But its almost most of the time when im using java apps and MMS and SMS. Wierd..
I got this problem even worse when i had Black Satin installed.. It will happen as soon as i start typing something..
updates?
I hate to ressurect this old thread, but was there any update to this issue that I might have missed? I am still having the dead keys issue, and I know it's not hardware as the pressing of the keys wakes up the device but doesn't do what the key is supposed to do.
I've had this Happen to Me Since Upgrading to WM6. When On WM5 It never Happened. Usually after a soft reset It's ok on WM6. I say Test out some WM5 for like a Week And if it doesnt' happen then It's the OS. Prolly Software to Hardware issues.
I have had a scout around and no one seems to have this problem so thought I would run it by you all..
I was using Schapps WM6 ROM (6.0) until a few weeks ago when I decided to upgrade to a Kaiser. I decided to reflash the Hermes ROM to T-Mobile UK's official WM6 ROM so that I could flog it. Now the camera comes up with no picture but Green lines. The picture reacts when the camera moves so it can't be the hardware - could it be a driver issue?
A hard reset does not work. Before I attempt a different ROM, I wondered if anyone else has this issue or had come across it.
See the JPG.
Cheers
p.s stuck the thread here in the WM6 forum because I think its s/w and therefore ROM related.
believe me, its hardware related...
probably try cleaning the camera contacts (if thats possible)...
It's for sure no software issue...
you should look after a take apart direction and follow it to clean the contacts...
Regards
Thanks, after a change of camera software and ROM it still shows. T-Mobile give two year warranties over here so hopefully they will repair to free of charge. Although if I can get into the handset without them finding out it will be much easier if I can fix it myself - HTC are not that good at admitting to faults with their products.
dpswatson said:
I have had a scout around and no one seems to have this problem so thought I would run it by you all..
I was using Schapps WM6 ROM (6.0) until a few weeks ago when I decided to upgrade to a Kaiser. I decided to reflash the Hermes ROM to T-Mobile UK's official WM6 ROM so that I could flog it. Now the camera comes up with no picture but Green lines. The picture reacts when the camera moves so it can't be the hardware - could it be a driver issue?
A hard reset does not work. Before I attempt a different ROM, I wondered if anyone else has this issue or had come across it.
See the JPG.
Cheers
p.s stuck the thread here in the WM6 forum because I think its s/w and therefore ROM related.
Click to expand...
Click to collapse
i have the same problem on spv m3100 and i am desperate!i don't know how but after sometimes and a lot of try suddenly the camera make good photo but after i put a new rom the prblem come again!did you think is from contact?i should open my spv?hmmm... risky operation
i can imagine it's form the contacts... but a hardware failure in general (camera related hw) is the most likely for this kind of symptoms... if i would be you i wouldn't open it, if i had warranty left ;-)
regards
after a lot of trying i decide to open my spv m3100 and take a look in it!so ...i open it i look at it clean it(although it wasn't necessary) and i reasembly the device!lucky me the camera wortk like a charm!i was very glad and i thought all my problem disapeared but..... after i doing first soft reset .......my camera show like in the bro attachaments!**** off!i was very unhappy and tried once again to fiox it!i decide to put radio version 1.51.00.10 (of course nothing happend) and after that i decide to use the old russian trick(kick the ****ing device with a hammer)!herhehheheeh!you'll never belive me but it works!heheheh!old russian trick always work!from now on i decide not to make any soft reset until one of you discover what happend in fact!
please do not apply russian method on your device(esspecialy with a hammer) take it easy but hit the buster!heheheh!
i think i found the mistery!at least to me it works!
be attentive:
on the back of the phone on camera is a little bumb!i move it up and down several times and oups the camera works!i made soft reset and again camera dosen't work and i repeat those up and down manouver and camera begin works!i made this operations several times and everytime after that manouver camera works!i belive that is a mechanical problem on camera!i take a look at camera and also at photo and i see a little arch maybe is decalibrated and possible that is the cause!it dosen't release something don;t no for sure!see the attachement!if your device is in warranties go to service to solve the problem if not ....well try what i said!
Here is how it happens :
i slide the keyboard out, write an sms or something , then slide the keyboard back in quickly : it soft resets itself.
It also happen when sliding the keyboard out and in without doing anything else.
This doesnt happens 100% of times of course, but in 2 days, it happened to me twice. And it pretty annoying.
I dont know if its something i have installed or not, but i dont see how it can be related (have tomtom, Batti, skype, Resco File Explorer, CorePlayer)
Am i the only one with this problem?
Thanks in advance if you can help me
Seems like the power cuts off sometimes you slide it. (in other words, it's broken). Return it and ask for another one.
Little chance this is the cause of any software interferrence.
But first try a hard reset... if that doensn't help, than you can consider a RMA
Hi,
I've had exacly the same. It looks like we did get a monday morning device
I've returned it to the shop and got a new one, this one is fine. I would suggest you do the same.
Toolman
hmm, mine is also doing that as well. Hard reset did not fix it. Bought from Techrific in Melbourne. Just negotiating return now.
Although my issue is not really a reboot. The phone just does an ungracefull shutdown. Have to power it back on.
i did a hard reset.
And so far, no unwanted reset... I am crossing my fingers.
FYI : unlike my first time, i didnt install Tomtom 7... i dont know if its related or not. So i just wanted to know if those experiencing those unwanted reset also had Tomtom 7 installed ?
May not be the same issue, but be aware of this problem with TomTom7 on the TP2...
http://forum.xda-developers.com/showthread.php?t=522373
ianjd said:
May not be the same issue, but be aware of this problem with TomTom7 on the TP2...
http://forum.xda-developers.com/showthread.php?t=522373
Click to expand...
Click to collapse
yes i found out this problem with the BT files... I had this problem too.
So i didnt install it yet since my hard reset, so i will wait a little bit before testing it out .
But so far, no more problems with my TP2, i dont regret upgrading from my Kaiser
Hello XDA Rhodium Community!
I've been lurking these forums for a few weeks since I purchased a TP2 about a month ago.
I own a Verizon CDMA TP2 and GSM unlocked it for use with my T-Mobile sim card (pay as you go). I have successfully tried many of the custom roms available here and settled on using Mr. X's latest Sense UI release for it's excelllent speed.
The phone worked great for about 2-3 weeks before I started to get a problem with my backlight/screen.
If, for any reason, the screen goes into sleep mode or shuts off it WILL NOT COME BACK ON until I reset the phone. The screen dim function no longer works either, it's either 100% brightness or it's completely off. I re-flashed to many different ROMs (including Verizon stock and the Bare Naked ROM), ran task29, reset storage, and anything else I could think to wipe the memory and the problem continues to occur.
Needless to say this is very annoying. I've been working around it for now by turning off ALL POWER saving options and attempting to keep the screen on at all times, but it will still turn off if I place my head on it during phone calls or accidentally press the backlight button on the top.
Anyone have any clue how to fix this? I love this phone and really don't want to have to buy a new one because of this
Has anyone else run into this problem???
well mine sometimes does this... however tis like if i try messing with it when its booting up... if i leave it for the 5-10 mins it sometimes takes to fullly wake up then its fine.
I always allow it to fully boot before using it. It wake up again no matter how long I wait.
Anyone have any ideas?
Hi
Having just joined the Touch Pro 2 club from the Touch Diamond 2 and creating a custom ROM, the only thing i can think of is this:
CDMA TP2's have a few things different in hardware to the GSM ones.. Perhaps there is a driver conflict now causing a SOD (Standby of Death)
Craig
I am having the same problme as the OP. I've had my Verizon TP2 for over 6 months without this problem, the last 2-3 months running a custom ROM. A few days ago the SOD started and I have not found a solution. I have cleaned it with Task29 and tried a number of ROMS (including going back to the "official" VZW MR1/WM6.1 release) with no luck. I'm now running Android in order to get through the day. I think the only solution is a hardware exchange with VZW (although it's not a hardware issue).
Try installing LUMOS to avoid SOD
i have a couple of TP2 with the SOD problem.
I read several post recommending LUMOS, so i did a quick test and it seems that it's really solving the SOD and also giving a little more battery dimming the screen.
Give it a try and let us know your comments.
I've tried LUMOS, but no luck. WM can't control the brightness and neither can LUMOS. I'm starting to wonder if I've got a bad light sensor.
audiomixman said:
I've tried LUMOS, but no luck. WM can't control the brightness and neither can LUMOS. I'm starting to wonder if I've got a bad light sensor.
Click to expand...
Click to collapse
You've got the wrong backlight.dll driver. I had this while experimenting with Topaz drivers on my GSM Rhodium. I also got a Standby of Death (SOD) with the Topaz drivers.
Craig
I'm all up for trying a different driver, but I've hard reset a number of times and flashed back to carrier ROMS with no luck. Wouldn't that have put the correct driver back? I was also running a single custom ROM for months with no changes with the SOD started to happen. Howevere, if you could post the correct driver, I'd appreciate it.
Hi,
I am also getting this problem, mine is a GSM, original rom was from vodafone uk, 6.1. I am on my 3rd tp2 from vodafone after complaints of this problem and within a couple of months use i get the SOD.
Its not as bad as the OP but i normally get the SOD a number of times per week. I have tried my first custom rom a couple of days ago (deepshining x10.235xx, i love it) with the aim of solving this problem but since i have had SODs 3 or 4 times in the last two days.
I am wondering if its a memory/ram issue as my TP2 after boot up starts with about 60-65mb free ram and with a little use the best i can get with all programmes closed is only 45mb (after using clean ram).
i do not believe it is a hardware issue because i have had the same problem with 3 phones now.
any solutions please let me know.
@audiomixman - when you flash back to carrier, do u flash back to the shipped SPL, ie remove HardSPL? I'm unable to post the correct driver as i think it needs to be cooked into the rom. I also have the GSM ver.
@rob_cunningham - I wouldn't think its memory as i routinely get down to 22mb with opera and music n about a weeks use. I also would guess if you've HSPL'd it, that could be the issue.
I don't really think its a hardware issue, more driver / poss HSPL
@both - does it happen on a clean hard reset build with no other software installed?
Craig
Craig,
I haven't removed the HardSPL because all the notes on the relocker thread say to only do as a last resort before returning device for warranty purposes.
Without removing the HardSPL, I have reverted to my carrier's 6.1 and 6.5 ROM releases and still get the same result without any software reinstalled. Right now I'm back to booting up with MightROM but with nothing installed. Once booted into WM, I go to Android. At least with Android while the screen won't quite turn off (it goes to "black" but the backlight is still on), it will come out of standby.
If you search, you will find many casues of SOD, although essentially there are two primary causes:
-Bad light sensor (actually pretty common)
-Conflicting drivers / IRQ overlap
for many, unchecking the box that allows WM to automatically control your light settings does the trick, others that does nothing. If you have a a bad light sensor, this usually works.
If you have a driver issue or IRQ conflict, usually not and going to a new ROM can help, but not a cooked ROM, as there are so many variations of hardware/software combinations for the TP2 in various countries / carriers that only real solution is to get back to the original shipped state of the phone with the carriers ROM and experiement from there. Many of the add-ons, like photo software, games, utilities all have some code that uses the light sensor and screws up the IRQ settings.
For me, I had the problem with the original ATT ROM, but the recently released update with Sense 2.5 solved my problem.
Good luck, not an easy one to find a solution to.
Hmmm, in that case, i'm lost sorry.
As the previous post mentions, I don't use the automatic backlight (and never have) you could try disabling it and seeing what happens.
Craig