Related
So I've been using the same ROM (in my sig) on my T-Mobile TP2 for 2 weeks now. Last night I tried to wake my phone (it was on for 8 hours already; being used 4 hours prior to make a PowerPoint using JetCet Presenter 5), and the phone wouldn't wake up. I pressed the soft reset button on the side, and everything was fine. I pressed the power button again before I put it in my holster. Ten minutes later, I pressed the power button to wake it, and it wouldn't wake up again! I did the soft reset thing, and battery was down 5-10%, so I know the phone was on the whole time.
I did a hard reset, and still had same problems. I was going to return it with warranty, so I flashed the stock T-Mobile WM6.1 ROM and everything was fine (I couldn't replicate any of my problems). I went to a different ROM (the latest Valkyrie Leo 23815, I believe?), and I got the same "can't wake" problem.
Now my real problem is the fact that I can't replicate it on the stock ROM. I think it's not the custom ROM because I've used the same one for 2 weeks. I don't know how I can get a warranty swap in this situation... It's not like I can say "Look, I have your stock WM6.1 ROM and it works. How come it can't work with a custom ROM?!"
*I confess I did just download the JetCet Presenter5 cab from these forums just two days ago. I made a PPT (as stated in the first paragraph) for a class and I saved it on my SDHC card. It was working afterwards, but the "can't wake" problem only occurred 4 hours later, and still persists after the hard reset.
Can I please get any help here? I really need a working device with a custom ROM and I don't know how to do a warranty swap in this situation.
Thanks.
SOLUTION: post#19.
(I replied this also on TmoNews forum)
What do you have to do create this problem...just wait and it happens eventually? Or does it happen right away the first time it goes into standby, or you put it in standby? Or is there a specific sequece of events?
How long did you wait after flashing the stock WM6.1 to see if the problem came up?
Maybe you could try flashing the "hidden" official WM6.5 rom...just on the chance that it might fix/delete whatever is wrong. Or it might show the problem so you could return it...after the Jan-20 official release.
Good luck
MCbrian said:
(I replied this also on TmoNews forum)
What do you have to do create this problem...just wait and it happens eventually? Or does it happen right away the first time it goes into standby, or you put it in standby? Or is there a specific sequece of events?
How long did you wait after flashing the stock WM6.1 to see if the problem came up?
Maybe you could try flashing the "hidden" official WM6.5 rom...just on the chance that it might fix/delete whatever is wrong. Or it might show the problem so you could return it...after the Jan-20 official release.
Good luck
Click to expand...
Click to collapse
(Replied this on TmoNews, but this might help others willing to help out)
On the custom ROMs, the first time it goes into standby, I can't wake the phone anymore and I just noticed that it won't recognize the USB cable (no charge from the outlet; no sync with the PC). If I soft reset and prevent it from going to standby, everything's normal (even the USB problem).
I flashed the stock WM6.1 ROM one hour before my first post. Everything is fine except for the annoying old Start Menu and the small, non-finger-friendly buttons!
I'll try the "hidden" official ROM now, just in case. I just don't know how I'll survive without WM6.5.x until after the official release date!
Thanks! I'll need the luck.
...So I think after all the testing I've done, and the weird problems others have posted [in various threads], I believe the problems I've experienced were a result of the new Sense2.5 build 1922 ROMs.
I just flashed the old EnergyROM Dec.4 Leo 28008 (Sense2.5 build 1921) and the problems are no longer present.
Newbie to WM!!!
Having similar Problems with my TP2. My phone has had several "wake up" probs since I have the phone. I installed directly after purchasing the WM 6.5 ROM directly from HTC-support (german). My real problems are right now that my alarm clock is not working properly (sometimes it works, sometimes not) and my phone often does not wake up after stand-by. Last night watched the clock at 04:30 and almost got problems caused by a non working alarm clock... (phone was connected to power supply)
anyone knows more about it? Is it a bug? user faults?
additional added software: Brians Task bar, Mort-player and powerbutton 12.
Just wanna get sure, that the phone is not damaged from hardware's site (warranty)...
Well.. I have (in this days) this problem.. It seems that it's getting worst day by day.
First of all: I've never used a "cooked" rom!
I had the original HTC rom (6.1).
I had this problem so I flashed the 6.5 update and it magically was solved!
Everithing was fine till 4-5 days ago: I can't understand what is the problem..
But I had only one time an "alarm problem".. But maybe was my fault..
I don't know what is the problem but it is NOT related to "cooked rom".
The worst thing is that RADIO MODULE IS ON!
So people call you, write you.. AND THEY KNOW YOUR PHONE IS ON!!!!!
This is totally unacceptable!!!
I would try a coked ROM.. But, as I can read, it would be useless..
And anyway: What is the most STABLE ROM in this jungle?
I'll write to italian HTC support.. I don't know if they will solve anything..
To: chrizz.o and DJ Palmis
chrizz.o: The alarm clock in WM is unreliable sometimes. You could download a 3rd party app alarm clock like Klaxon or G-Alarm.
DJ Palmis: You could also download an alarm app (see my response to chrizz.o). I don't know if you're talking about you can't turn your screen on after it goes into standby (my problem).
I don't know if you guys are confused but my problem is: I can't turn on the screen if the phone goes in standby (screen goes off). The phone is still on, but the screen is permanently off. This only happens to me in the new custom Leo ROMs. It doesn't happen in stock ROMs or old custom ROMs, so I cannot return it.
DJ Palmis, I don't know why it's happening in a stock ROM. You can try a hard-reset (wipe device) by pressing/holding Power button, Talk/Send key, and End key at the same time when the phone is off. That might help. If it doesn't, return it to HTC.
BTW, I think the most stable ROMs are the EnergyROMs, ValkyrieROMs, and the Rhodium_AF (ark666) ROMs.
Same issue w Att Tilt 2
I'm experiencing the same issue, occasionally the screen won't come on from standby when I know the phone is on. It shipped with 6.5 and it remains with the stock rom.
The issue is so hit-&-miss that it is difficult/impossible to trouble shoot.
sumflipnol said:
chrizz.o:I don't know if you guys are confused but my problem is: I can't turn on the screen if the phone goes in standby (screen goes off). The phone is still on, but the screen is permanently off. This only happens to me in the new custom Leo ROMs. It doesn't happen in stock ROMs or old custom ROMs, so I cannot return it.
Click to expand...
Click to collapse
I think we have the same problem, indeed. And i don't want to hard reset because i did not change anything in the last weeks.. I'm only using my phone more frequently.. So more text messages, videocall and so on..
But this does not justify this problem.
It would be nice to know what happens during this "freeze".
Maybe it is related to notification queue (that's why a new rom "solves" problem for a while)?
Well.. Anyway I had this problem on my old HTC Universal.. So it is related to WinMobile or Qualcom..
when i had a issue similar to that. i just hard reset my touch pro and flashed a whole new rom. and hard resetted again and i was bug and error free.
charlieb620 said:
when i had a issue similar to that. i just hard reset my touch pro and flashed a whole new rom. and hard resetted again and i was bug and error free.
Click to expand...
Click to collapse
The OPs issue must be a little different.
He tried flashing several different roms -- stock and custom -- and only the stock T-MoUSA WM6.1 or WM6.5 roms or custom roms that were a month or two old would stay "fixed".
sumflipnol said:
chrizz.o: The alarm clock in WM is unreliable sometimes. You could download a 3rd party app alarm clock like Klaxon or G-Alarm.
Click to expand...
Click to collapse
Cheers for upadating me. Appreciate it. Will try another alarm clock in a while. BUT: I use mort's player as an additional "alarm", as well, and even that does not work propperly. Might be, that it is no real alarm clock. strange and weird.
But it is good to know, that the "will-not-wake-up" problems are more or less known by several other users. I almost thought it is my stupidity to use a win mobile phone *lol*
Does anybody know, eventually, if there's a more stable rom (maybe with the new manila like on HD2) for germany which might solve the freezing problem?
thxx for updates
I'm also getting will not wake problems on the leaked official TmoUS WM 6.5 Rom. I would get it about twice a day. My stock tmobile US 6.1 never had this issue.
A fix that works for me:
Change the power settings to always on for a like 10 minutes and put the default settings back. You would have to do this after every soft reboot.
HTC Italy told me to set Band selection to auto (booth choices) and to change network selection (auto if set to manual or manual if auto) and then they told me to soft reset by button.
I'll write you if I have news.. But i think they know something more than us about this problem. And they are on the way of solving because i noticed that this problem happens in bad quality signal areas and ALWAYS when phone is ON.. So it is related to radio module.
I think it may be related to SIM card, too.
Because they told me to change SIM.. And at last to do an Hard Reset..
Maybe my 3 card is not fully compatible with my radio version?
Hey,
thxx for the updates. Indeed, I have quality differences in our flat, bandwidth switching between HSDPA, 3G and GPRS, depends on, in which room I am.
Asking HTC Germany about this problem, they told me, it is a not known issue. The more I follow up here, I cannot believe that.
Do you really think, it may also be caused by the SIM-card? Mine is about 2 years old (VF GER).
chrizz.o said:
Do you really think, it may also be caused by the SIM-card? Mine is about 2 years old (VF GER).
Click to expand...
Click to collapse
Mine too!
What I know is that i had this problem on my old HTC Universal... So maybe problem is not in the "age" of SIM card.. But in some technical compatibility between SIM and Qualcom.. (You know: 64 KB, 128KB and so on..).
Maybe Qualcom has some problem on european SIM card? I don't know..
DJ Palmis said:
I think it may be related to SIM card, too.
Because they told me to change SIM.. And at last to do an Hard Reset..
Maybe my 3 card is not fully compatible with my radio version?
Click to expand...
Click to collapse
I read somewhere in a ROM thread (I don't remember exactly where) that some people are experiencing constant freezing on their phones after a few weeks of use. Someone recommended taking out the SD card because it might be corrupt, and that interferes with the phone's performance. Some people said it worked; they found out their SD cards were actually corrupt, and using a new one made the phone function well.
Having used ValkyrieROMs before, I remember a pre-installed app (I forgot the name) that let you format your SD card. When I tried it (even after I formatted my SD card to FAT32 on my PC), the app said my SD card was corrupt and cannot be located. The last time I used the app was 1+ months ago. I think I'll try to flash a ROM without the SD card when I have time.
...But I still don't know how the SD card would give me a problem with a (new) ROM that I had on my phone for 2 weeks...and no problem on an older ROM (that I have now)...
sumflipnol said:
SD card because it might be corrupt,
Click to expand...
Click to collapse
Well I don't know, What I can say you is that till now i have no problem with HTC istructions.. Maybe i solved.. I hope..
SOLUTION!!!
I finally got my phone working with new ROMs again!
It was the SD card! I connected my TP2 to the PC as a "Disk Drive" and I went to My Computer > [right click] Removable Storage (SD card) > Properties > Tools > fix... something something (I can't remember exact words). It fixed the corrupt SDHC card I have; now my phone is working again!
This might help you, too, DJ Palmis...
Just had done this right before the last freezing-problem. My SD-card was not corrupt, so this did not solve my problem.
At least I swapped my SIM-card, made another hardreset and checked my SD-card again. Let's see what's happening...
The soft keys were lighting up just fine, I have installed BeastMod II vs 2.1 and am using Go Launcher everything seemed to be working the first day and now the second day, the soft keys do not light up anymore. Does anybody know why this has happened or a possible fix?
Edited: Idk their exact name, soft keys, on screen buttons. (If theres any confusion...)
did you install any new Kernel for BLN ?
@Allgamer, no i did not install any Kernals. Only the Rom mention and Go Launcher
Edited: Installed Jaug's Rom it started working now, could have been a rom bug...
I did some search and found older threads with similar problems but found nothing that really fix my issue...
Just bought Samsung Bluetooth earpiece for my T989, it was working perfectly for 2 days. Now i can't turn on bluetooth at all. It search for devices for 10 seconds and come back to off by itself. Sometimes i can get it works after turning it on for 7-8 times.
I thought it was a Rom issue because was using jedi jelly (att Leak) for few days only... So i wipe everything, going back to my old Jedi Mind Tricks but still having problems turning bluetooth on.
So i Odin it back to stock, now Bluetooth come back to life... Re-install Jedi Jelly, Bluetooth still works perfectly.... I used it for 3 days and now it dead again...
Anyone else with similar issue ???
Tornade69 said:
I did some search and found older threads with similar problems but found nothing that really fix my issue...
Just bought Samsung Bluetooth earpiece for my T989, it was working perfectly for 2 days. Now i can't turn on bluetooth at all. It search for devices for 10 seconds and come back to off by itself. Sometimes i can get it works after turning it on for 7-8 times.
I thought it was a Rom issue because was using jedi jelly (att Leak) for few days only... So i wipe everything, going back to my old Jedi Mind Tricks but still having problems turning bluetooth on.
So i Odin it back to stock, now Bluetooth come back to life... Re-install Jedi Jelly, Bluetooth still works perfectly.... I used it for 3 days and now it dead again...
Anyone else with similar issue ???
Click to expand...
Click to collapse
Yes . Hardware Issue for sure . I've done countless things . Flashed to stock, flashed various roms and radios and the issue remains . I just gave up on bluetooth. Sometime it works and.sometimes it doesnt .
Fixed for me
batvan said:
Yes . Hardware Issue for sure . I've done countless things . Flashed to stock, flashed various roms and radios and the issue remains . I just gave up on bluetooth. Sometime it works and.sometimes it doesnt .
Click to expand...
Click to collapse
I've struggled with this for months and I've finally fixed it.
It was the root! When I unrooted all went back to normal. I tell you, before that I tried EVERYTHING and nothing worked.
Sorry to bump this again but missed last post and because i still carry this issue 1 year later, i decided to try to unroot just for fun....Lol!!! Finally, I can confirm the root interfere with bluetooth... That's why when i odin back to stock, bluetooth start to work again! If i Root, after 1 day or 2 using bluetooth functionnality, problem came back!
Anyone else having this issue ?
Any other way to root without having this bluetooth issue ??
Tornade69 said:
Sorry to bump this again but missed last post and because i still carry this issue 1 year later, i decided to try to unroot just for fun....Lol!!! Finally, I can confirm the root interfere with bluetooth... That's why when i odin back to stock, bluetooth start to work again! If i Root, after 1 day or 2 using bluetooth functionnality, problem came back!
Anyone else having this issue ?
Any other way to root without having this bluetooth issue ??
Click to expand...
Click to collapse
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
Hi folks,
I'm not sure what's up with my phone. I have CM10 beta on it and since earlier today the D button on the keyboard is completely unusable. Also, I have a hard touch hitting R. I have tried touching the same area in other apps and it seems to work fine. Maybe there's a tool out there I could use to confirm this?
I had this happen before on an earlier build of CM10. When it happened before (and as of now), rebooting doesn't fix it. Last time I gave up and just upgraded my CM10 ROM, and it has been working ever since (around a month or so).
Today, the touch screen experienced some "glitches". What I mean is, I took it out to use it and it seemed like it was detecting touch/drag events in various spots, and I had to put it to sleep to get it working again.
I have no idea where to start with diagnosing this. It doesn't seem to be a hardware issue, since re-flashing before fixed it. Any ideas?
Go back to stock, if you have the same problem then it will probably be hardware issues.
Sent from my One V using xda premium
Few days earlier I started to notice this problem after 5 months of use of my device. My screen starts rapidly shaking left to right and front touch panel stop working, it happen when I freshly open an apps. To temporarily fixed it, I have to press power button to turn off the screen. Is it a hardware or software problem?
Did you flashed any rom or kernel?
Do you use trickster?
Some people sayed that uninstalling trickster solved their ghost touches on the keyboard (may not work in your case).
I had a similar problem and was because of a kernel.
If you had modified anything try to use stock for a while and see if the problem persist
Enviado do meu Optimus G através de Tapatalk
Stock, I guess I should wait for official kitkat. Dont have time thinkering my fone atm.
I was ghosts touches on my screen. One was pressed on all sides. To fix it I had to turn off and turn on the screen. I decided to change the touchscreen and the problem was fixed. Now it works ok.
Sorry my english.
Enviado desde mi LG-E975 mediante Tapatalk
where do you get you're replacement touchscreen? any online site that offer spare parts?
yawako said:
where do you get you're replacement touchscreen? any online site that offer spare parts?
Click to expand...
Click to collapse
I bought it on ebay. Screen+touch+ frame. This option:
http://pages.ebay.com/link/?nav=item.view&id=111278902215
But You can buy other options.
1. Touch + screen+ frame (medium dificult)
2. Touch + screen without frame (best option)
3. Only touch screen. (very dificult option)
Many people have told me that the best option is 2, without frame to not be taking off parts that are originally attached to the frame.
You can see totorials on youtube
Ghost Touch now keeps rapidly pulsing at the buttom edge of my screen (portrait) my phone is sometimes uncontrollable. I never thought this kind of newer high end device gets broken so easily under short period of time. I never experienced this from my good old Galaxy Y, Xperia mini and X8 that I accidentally deep under water even now still working in mint condition. So sad with LG products. I was planning to buy LG G Pad but because of this I probably get Nexus 7 instead.
Im going to sell this for $155
Reflash it again with stock firmware twice, problem still persist
Its now a hardware issue
Touch screen seems deteriorating overtime. At first Ghost Touch, then on the next day a dead touch portion just above the home screen panel where the ghost touch first occurred rapidly moving back and then after few days a ghost touch appeared again just below in the middle of the screen (portrait) then after an hour probably about 1.5mm size thickness dead touch. Now a I have 2 horizontal dead touch portion of my screen and probably more to come if I keep using it.
Few days ago i'v got first phaton/ghost touch problem. I used Omni 4.4.4 so
- reflash to clean OmniRom (try few kernels) - the same
- flash to Android L Preview - the same
.....
fu***
Install - ARTMod ROM so 99,9%of stock - and as for now all its ok.
Strange.
Update:
One day and zero problems.
htomasz said:
Few days ago i'v got first phaton/ghost touch problem. I used Omni 4.4.4 so
- reflash to clean OmniRom (try few kernels) - the same
- flash to Android L Preview - the same
.....
fu***
Install - ARTMod ROM so 99,9%of stock - and as for now all its ok.
Strange.
Update:
One day and zero problems.
Click to expand...
Click to collapse
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
dashcsn said:
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
Click to expand...
Click to collapse
On this ROM 0 phantom/ghost touch
http://forum.xda-developers.com/optimus-g-intl/development/rom-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
OK, this is freakin' weird...
I have been running KitKat on my F180S pretty much from the time it got released (different versions: full stock, VDT, Sling...). Yesterday, out of the blue, my digitizer started getting crazy with ghost touches in the upper portion of the screen (around the strip where Q-slide apps usually are in the notification shade, or the clock area on a weather widget where most people have it). This made the phone 100% unusable, as it was constantly registering touches. Rebooted to recovery to do a factory reset, and the problem was persistent in the recovery, too (I am using PhilZ Touch). So, at that point it looked like a hardware issue to me. To clear my consciousness, I opened the phone, disconnected the digitizer, cleaned the connectors, plugged it in again. No dice. Still, I thought about reflashing a full stock KDZ, just for the heck of it (no root, no custom recovery, locked BL). Here is what happened:
1. F180S V30c KitKat - same problem.
2. F180S V30b KitKat (downgraded a notch) - same problem.
3. F180S V20n Jelly Bean - everything is working fine, no ghost touches. Huh?!?
4. Rooted V20n, unlocked BL (Mako method) and flashed CWM using FreeGee - no problem, everything is still OK.
5. Flashed my favourite JB ROM - no problem, everything is still OK.
So, the phone is now running on rooted JB, with unlocked BL and CWM recovery, with no touchscreen problems whatsoever. I may try going to KK again at some point, but will just leave it for now, as I need a stable working phone.
WTF??? I am just scratching my head, trying to understand where the issue came from. It appears to be directly related to KitKat, since eliminating unlocked BL and custom recovery didn't solve the issue, but going back to JB (either full stock, or unlocked BL with CWM) totally cured it. The most bizarre thing is that it started out of nowhere, as I didn't do anything to my phone recently, apart from installing some apps here and there...
kt-Froggy said:
OK, this is freakin' weird...
I have been running KitKat on my F180S pretty much from the time it got released (different versions: full stock, VDT, Sling...). Yesterday, out of the blue, my digitizer started getting crazy with ghost touches in the upper portion of the screen (around the strip where Q-slide apps usually are in the notification shade, or the clock area on a weather widget where most people have it). This made the phone 100% unusable, as it was constantly registering touches. Rebooted to recovery to do a factory reset, and the problem was persistent in the recovery, too (I am using PhilZ Touch). So, at that point it looked like a hardware issue to me. To clear my consciousness, I opened the phone, disconnected the digitizer, cleaned the connectors, plugged it in again. No dice. Still, I thought about reflashing a full stock KDZ, just for the heck of it (no root, no custom recovery, locked BL). Here is what happened:
1. F180S V30c KitKat - same problem.
2. F180S V30b KitKat (downgraded a notch) - same problem.
3. F180S V20n Jelly Bean - everything is working fine, no ghost touches. Huh?!?
4. Rooted V20n, unlocked BL (Mako method) and flashed CWM using FreeGee - no problem, everything is still OK.
5. Flashed my favourite JB ROM - no problem, everything is still OK.
So, the phone is now running on rooted JB, with unlocked BL and CWM recovery, with no touchscreen problems whatsoever. I may try going to KK again at some point, but will just leave it for now, as I need a stable working phone.
WTF??? I am just scratching my head, trying to understand where the issue came from. It appears to be directly related to KitKat, since eliminating unlocked BL and custom recovery didn't solve the issue, but going back to JB (either full stock, or unlocked BL with CWM) totally cured it. The most bizarre thing is that it started out of nowhere, as I didn't do anything to my phone recently, apart from installing some apps here and there...
Click to expand...
Click to collapse
Kinda like my situation.
I have the sprint version of the phone,in every kitkat GEE ROM I have ghost touches, but not in Gproj kitkat ROMs neither in stock or JB.
some weird sh*t is happening here lol
FcoEnrique said:
Kinda like my situation.
I have the sprint version of the phone,in every kitkat GEE ROM I have ghost touches, but not in Gproj kitkat ROMs neither in stock or JB.
some weird sh*t is happening here lol
Click to expand...
Click to collapse
Yeah... But at least in your case the problem seems to be consistent. I was using my phone without any issues, and then it just crapped out for no apparent reason. Nothing changed, same ROM that was working fine before...
kt-Froggy said:
Yeah... But at least in your case the problem seems to be consistent. I was using my phone without any issues, and then it just crapped out for no apparent reason. Nothing changed, same ROM that was working fine before...
Click to expand...
Click to collapse
It started the same way for me.
....
The same thing happened to me. Are you guys familiar with Sky Vega phones? I had a Vega Iron before and also it began having ghost touch issues after upgrading to kitkat. I was frustrated, i also flashed any custom rom i could search and no luck at all. I just sold it recently! and i heard this ghost touch issue is also a common on Nexus 4.
dashcsn said:
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
Click to expand...
Click to collapse
http://forum.xda-developers.com/optimus-g-intl/development/rom-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
Hello everybody,
I have the same problem with my LG - ghost touch and dead zones on the display. First installed the ROM from this link - http://forum.xda-developers.com/opti...te-10-t2811342 , but the issue still exist.
Then change the display with a new one. Dead zones vanished but ghost touch doesn't. Tried some other ROMs even the original stock ROM.
When I installed the new display the ghost touch is mostly when I use Facebook Messenger.
What can I do in this situation?