Ok, I was having some software issues with my Tilt 2 (TP2) and I talked to Tech @ AT&T, cause I wanted to get it exchanged. So they had me go and check to see if my ROM was outdated, which it was. I bileive it was on 1.59-ish, and now its on the most current one direct from HTC's Support site. My main problem right now is that the phone is 99% unuseable at the moment. AT&T has already agreed to send a replacement after talking with them a few hours ago, but its going to take about a week to get here, and it'll most likely have the same ROM and the same problems, so here I am posting to let people know whats going on, and see if anyone else knows what causes this/has this issue.
Right now the phone is completely stock, only installed app is MS My Phone so I could sync my contacts. I can let the phone sit till the screen shuts off from idle, but if I need to turn on the screen once it turns off, it requires the battery to be taken out. Right now my phone is sitting in front of my keyboard, with its screen black and off, while the keyboard is lit up. Something to note - the keys on the bottom of the screen are NOT lit up. Pushing buttons on the keyboard does nothing. Caps Lock and FN do NOT light up their coresponding indicator lights. If I am lucky, I can get the phone to come out of this state by having someone call me, but aside from that, taking out the battery has been the only way to reset it. Only way to keep the screen from freezing is to constantly use the phone. Using the phone is slow as balls. I thought TF3D was slow, Sense is just as bad. It worked perfectly fine at first, right after it was updated, it was nice and fast, but now that its been used for a few hours, its sluggish.
Anyone ever had this issue with this ROM?
And does anyone know how to possibly fix this issue, or at least get it so the screen will show that its on? I can deal with it being slow, so long as I can use the screen
Thanks guys
null_x86 said:
Ok, I was having some software issues with my Tilt 2 (TP2) and I talked to Tech @ AT&T, cause I wanted to get it exchanged. So they had me go and check to see if my ROM was outdated, which it was. I bileive it was on 1.59-ish, and now its on the most current one direct from HTC's Support site. My main problem right now is that the phone is 99% unuseable at the moment. AT&T has already agreed to send a replacement after talking with them a few hours ago, but its going to take about a week to get here, and it'll most likely have the same ROM and the same problems, so here I am posting to let people know whats going on, and see if anyone else knows what causes this/has this issue.
Right now the phone is completely stock, only installed app is MS My Phone so I could sync my contacts. I can let the phone sit till the screen shuts off from idle, but if I need to turn on the screen once it turns off, it requires the battery to be taken out. Right now my phone is sitting in front of my keyboard, with its screen black and off, while the keyboard is lit up. Something to note - the keys on the bottom of the screen are NOT lit up. Pushing buttons on the keyboard does nothing. Caps Lock and FN do NOT light up their coresponding indicator lights. If I am lucky, I can get the phone to come out of this state by having someone call me, but aside from that, taking out the battery has been the only way to reset it. Only way to keep the screen from freezing is to constantly use the phone. Using the phone is slow as balls. I thought TF3D was slow, Sense is just as bad. It worked perfectly fine at first, right after it was updated, it was nice and fast, but now that its been used for a few hours, its sluggish.
Anyone ever had this issue with this ROM?
And does anyone know how to possibly fix this issue, or at least get it so the screen will show that its on? I can deal with it being slow, so long as I can use the screen
Thanks guys
Click to expand...
Click to collapse
You already ruled out a software issue by flashing another stock ROM. This is something hardware related. Sense on the AT&T ROM is dreadfully slow. Use a custom ROM if you want the features of Sense, but in a faster iteration.
Related
I've been running Black 1.2 for some time. Love it. Never soft reset. Only hard reset it once. I'm using a Cingular 8525. What's weird is that it powers itself off randomly lately. 3 times in a row. It was pretty hot outside when it happened, so don't know if the heat caused it, but the screen would just die and turn off. Anyone have this happen? Any ideas as to what causes this powering down? The battery is full. It was just super hot out? Hmmm.
I would suggest you upgrade to a newer rom dude
take a look in my guide thread which has the latest ROMs listed.
mrvanx said:
I would suggest you upgrade to a newer rom dude
take a look in my guide thread which has the latest ROMs listed.
Click to expand...
Click to collapse
I considered it, but since Black 1.2 was released, I never had a problem with it. Very stable. Could it now after all this time just all-of-a-sudden cause random power-offs? Also, I noticed the device likes to power-off when I slide the qwerty keyboard out and lock it in place. Not every time I open it, but it has happened a few times now. ROM related? Let me know. I'll probably up to a newer ROM tonight.
Thanks.
-fin
Ok, update: Seems that EVERY time I slide out and lock the qwerty the device shuts off when I go to reply in a messgae using Palm SMS Threader. Is it the device or the app?
I had the same problem with my old JAMin (Prophet). I would keep the phone in a case and then wonder why I wasn't receiving any calls, then check and see the phone having turned itself off. Reloaded it with a different ROM and the problem went away.
Yeah, that's happened a bunch of times now. Just recently did I hard reset my device, and all was running great like before. Just all of a sudden am I having this issue with power offs and the qwerty kicking the phone off when I open it.
I have the same problem and I have come to one conclusion because I can repeat it.
If you are closing or opening the keyboard, but you do it quickly (like slamming the keyboard shut or open), it will turn off. Also, if you squeeze it while it is closed, it turns off. And I have made sure im not hitting the power button.
Try it and see what happens.
Yeah, it does it when you slide it out really fast. Noticed that. Haven't been able to repeat it every time, but the times it does shut-off, its from sliding it open fast. Now to understand why this happens, since it didn't do this in the past.
Hi folks, I've lurked here for quite a while and gotten some invaluable info; so first off thanks for all of the contributions from the gurus here!
Now, I have a pretty strange issue that I haven't been able to find an answer on anywhere. I'm hoping that someone can help me sort this.
The background story:
My wife has a MyTouch 3G Slide that I bought for her back in July. Last week she managed to drop it in some water. It DID NOT get fully submerged since the water was very shallow. However, it did get a slight amount of intrusion. She pulled the battery in a relatively quick amount of time and we let it sit in a bowl of rice to dry out for a couple days.
The current deal:
When I felt the phone was sufficiently dried after a few days, I fired it up. It took a very long time to get out of the MyTouch splash screen and loaded noticeably slower than normal. Once in, the phone functioned perfectly normal. Absolutely no issues at all with any functionality once you get past the security pattern.
However, whenever you put the phone to sleep, it does some funky stuff. The screen goes black for a second and then comes back on, ready for you to swipe down and then enter the security pattern again. Then it will go black again. Then it comes back on. It just continues to do this, never stopping. Sometimes it will go to the security pattern screen too.
So I figured this may have been some hardware issue since it was acting like someone was just repeatedly pressing the power button. First I wanted to try a simple reboot though. Upon rebooting, the phone would not get past the splash screen. It just froze there.
I pulled the phone apart to see if maybe there was some corrosion on the PCB from the water intrusion. Everything looked fine, but while I was in I did a little wipe-down with some alcohol, then I put it back together. After multiple attempts, I was able to get it to boot again. But the boot process was still VERY slow. Occasionally, it would boot into safe mode as well. But when it booted normally, everything would always function great once logged into the phone. This convinced me that it wasn't a hardware problem since the phone would not cut into sleep mode or anything when logged in. It worked perfectly fine. So I figured that maybe there was some sort of corruption that occurred in the software.
So I tried a hard reset. Didn't fix it.
Then I figured that maybe I needed to do a reflash. So I rooted the phone since the water plunge voided the warranty anyways. Once rooted, I flashed TeamFenix 1.7.1 successfully.
But the phone still only fully boots intermittently, and the boot process is still slow. It also has the same problem in sleep mode which is killing the battery fast since the screen is pretty much constantly on. But once in, the flashed ROM works perfectly just like the stock ROM.
Video of the condition:
Since I'm new, I'm not allowed to put any links in my post. But if you type in the string below after the YouTube url, you'll see a quick video I posted of the condition.
watch?v=dX55URtaRHo
So it seems that there is some crazy issue only upon bootup and when the phone is put to sleep. Can anything be done to fix this? Is there a way to locate and fix corrupted software? Any and all help is appreciated!
Sorry for the self bump. Any devs out there have any suggestions? I gotta get this thing sorted.
If its happening on both stock and teamfenix, I'm pretty sure it's a hardware issue. Flashing a rom completely replaces the software, so it doesn't sound like its that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It actually seems like a problem in the power button. Did you check the contacts for the power button? Repeatedly pressing the power button will first lock it initially and dim the screen. Press again, then it gives you the chance to unlock. Press again and it goes back to sleep. Wash rinse repeat...
Yes, I understand. But if it were an issue with the power button, when you logged into the phone, it would randomly put itself to sleep. It doesn't do that, it functions perfectly normal with no errors whatsoever when you are logged into the phone. This problem is only exhibited in sleep mode which would rule out a hardware issue with the power button.
Using the stock ROM for the Galaxy Nexus, Android 4.04 from Google, I'm finding this bug (which has been elsewhere reported, but not acted upon by Google) where the touch screen is unresponsive. You press the 'power' button, the 'slide to unlock' screen appears, but the touch screen doesn't respond to anything.
If I get a call while the phone is sleep, the same thing occurs - can't answer the phone.
I usually have to put the phone to sleep/wake it up 5, 6, or more times before the touch screen again becomes enabled in these situations.
Does anyone know why this happens? There has been much conjecture about this, but I have yet to see anyone say for sure why this would be happening. A disabled touchscreen at such a crucial point in a GUI is pretty horrific.
- Tim
was gonna make a new thread on this but since i found one with the exact same thing happened figured why waste space, but anyway this just happned to me running stock 4.0.4 cdma unrooted. was just charging my phone unlocked it to check twitter and the lock screen was completely unresponsive for whatever reason. I continued to turn the screen off and on several times and then just decided to pull my battery and it worked fine.
This is the first time its happened to me and its kinda troubling as I dont want this to be a recurring thing and was wondering if this continues to happen or its just some single random occurence?
HI,
I guess others have had this problem but i cant really find the answer.
I have a problem with proximity sensor that i have to press the phone at the top left side in order to switch it off after its on. It works fine like that when i test it at service tests but when i don't press the phone at the top left side it does not turn off most of the time. Yesterday i also had problems that the screen was off for few minutes at high light no matter what i did. since i finished what i had with phone i did not remove the battery to see if the problem will repeat, all i did after the screen was on, was a reboot but i did not have the chance to test it again at direct sunlight again.
I don't have something on top of it, all i have is the screen protector that came with the phone.
it is with unlocked bootloader, stock rooted rom, supercharged and with removed bloatware software's. this is all i can remember to tell for my phone, i have never tried other custom rooms since i did not have the time because of school.
The phone is new, not even 2 months old, hope i don't have to send it to repair.
Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz
I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.
I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.
Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.