Has anyone had their screen stop timing out? I've had my phone for 11 months, noticed this problem periodically but now my screen won't time out at all. My phone has been rooted for 6 months, never any big problem with the screen. About 3 weeks ago it stopped timing out completely. I have adjusted the settings from 2-1-.5 minutes, and it would work for the first while then it stops. I haven't installed anything on my phone that I can say triggered this. Resetting and taking the battery has no effect. I believe I have froyo on here.
Thanks for your help
this is on my incredible
Related
Hi Guys,
I just recently had a problem with the screen of my 750. The screen stops responding after the first touch.
I would like to know if theres is a way to skip this alignment screen process. Right now i´m stuck at this screen.
Thanks for your help
http://forums.palm.com/palm/board/message?board.id=hardware&thread.id=16220
I think this will help u.
jesusodin said:
Hi Guys,
I just recently had a problem with the screen of my 750. The screen stops responding after the first touch.
I would like to know if theres is a way to skip this alignment screen process. Right now i´m stuck at this screen.
Thanks for your help
Click to expand...
Click to collapse
After using my used Treo 750, WM 6, AT&T for about two months, it started experiencing the screen problem. Upon hard reset, the screen would respond to the first tap, and be almost unresponsive to the calibration. I had to press repeatedly very firmly. Went through a couple of hard resets and it didn't get better.
The screen would respond find for a while and then start working. I thought that I had it all taken care of and was working well yesterday until the afternoon rolled around. It started being unresponsive again. After a hard reset, it would respond to the first touch and then calibration barely worked.
Finally, I was able to get into it and installed Palm's Device Reset and ran it. It has since then been calibrating fine. I'm only using it bare bones right now and won't be able to test it more in depth until this weekend to see if the problem is resolved.
I did notice using SKTooks that the gwes.exe process was running at a high percentage while this was occurring, near 40-50 % when it is running at 0% now.
Any thoughts? ANyone tried the device reset at:
http://kb.palm.com/SRVS/CGI-BIN/WEBCGI.EXE?New,kb=PalmSupportKB,t=ooccase,case=obj(9260)
Treo 750 touch problem
Hi , I'm having the same problem wit my Treo . Did you solve your problem?
Hey Davidoff,
For quite a while, mine acted up, so much that I bought a used Wizard to replace it. Even after performing the device reset as I noted above, it would still be unresponsive at times, with the GWES.exe process (as shown by SKTools) running much higher.
For a while, I let it set without it's battery (perhaps a week) and then reinserted, fully charged it and immediately disabled ALL today plugins. So far, it has been running great but I'm very tentative to switch back to it as my primary phone, even though I love it.
I'm wondering if you can try disabling your today screen plug-ins, set the screen backlight to dim at one minute and the device to auto-off at one minute and see if this helps to resolve the issue. I'm curious as to whether any of those three combinations made a difference in mine, or have just bought time until it acts up again.
Anyways, I'd be interested to learn your results.
Brian
So I've been having these issues for a while now and I'm finally tired of being a slave to my xoom's idiosyncrasies.
For the last 6-7 months or so, and plenty of roms within the timeframe, my xoom freezes to a blank black screen shortly after leaving my wifi for the mobile network. In fact last night as soon as I got into the car it started boot looping.
The second issue is Android Over Clock constantly not responding and lagging or freezing up. In fact I wonder if it is what's causing my freezing issue.
Has anyone had similar issues?
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Something similar ....
I had a similar experience on the 15th .... took my N5 off the Qi charger and the screen froze when i tried to unlock it.
I hit the power button and was able to unlock and get a few touches in before it froze again.
I was finally able (after much screen off/on cycles) to get down to the developer options and turn on show touches & show cpu usage.
... background processes looked fairly normal when the screen was frozen(touches showed as frozen) ...
I was rooted, stock rom except for xda user Jishnu Sur's N5 camera mod and running a couple tried & true root apps(Stickmount & QuickBoot). Thought some software issue might be jamming up the digitizer i/o causing it to freeze.
Reverted entirely to stock (the Team Win recovery was also experiencing screen freeze - buttons worked fine) including removing TRWP and re-locking the boot loader!!
The screen freezing problem persists ... my conclusion is that it's a hardware issue. :crying:
It's possible you are seeing the same thing, but I haven't seen anything in the forums to indicate it's a widespread problem.
Returning it for a replacement phone ... :fingers-crossed:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
biggiephat said:
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Click to expand...
Click to collapse
Freezes tend to happen on custom kernels specially if you under-volt it too much. have you done that?
Screen Freeze
canaillou2k5 said:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
Click to expand...
Click to collapse
Last week I had the same problem with my new NEXUS 5. IT’S TOTALLY A HARDWARE ISSUE.
LG products are however not so bad in the JAPAN market but still we are expecting a lot from LG technology.
LG services suck.
I am facing the same problem with my Nexus 5. Unrooted, bought 7 months back from India itself, was working fine till around two weeks back,when the lags, screen freeze, blacking out n all appeared. Got it repaired twice at the LG centre. They changed the front display touchpad as well as the charging connector strip. The problem still persists.
I have this Nexus 5 for 11 months but for last 1 to 2 months it's backlight is like blinking and going off for several seconds and coming back again and partially dimming at a side and then recovering the brightness again. It started when I started playing clash of clans, and the phone got heated(around 45°C); but even after I uninstalled the game, it didn't stop. This is happening sometimes, everyday, but not all day long. That's why I wasn't concerned much, but yesterday after blinking for few seconds the bottom right side of the screen stayed a little dark(ish)[ not very prominent, but visible to me ]. It's still like that and still the blinking hasn't stopped. Anybody had this experience before, or anybody has a clue to fix this, help me.
P.S - The phone is fully functioning during this and, rebooting is ending the blackout, but that may be because the time taken for rebooting.
Hi all,
Hope somebody can shed some light on this issue I'm facing. This is my first ever post. All your input will be very much appreciated.
I purchased this S7 Edge DUOS (Dual sim version) around 8 weeks ago. Around 3 weeks into my ownership, I've started facing a persistent issue which I've tried to resolve with the best of my knowledge but unfortunately I haven't succeeded.
Randomly the phone will freeze for around 5 to 10 seconds and then restart. Sometimes a pixelated set of lines would appear across the screen when it freezes, a lot of the times they are green.
When the phone does reboot and I return back to the main screen, everything is back to normal and the apps I was using remain opened in the background, so it's not a proper reboot.
There is no such pattern on when this happens, it happens while being used on any app and a lot of the times it reboots while the phone is in my pocket. The only reason I realise is because the phone will be on the startup lock screen.
Battery life seems okay, nothing seems to be draining the battery. Although sometimes it does get hot and drains it temporarily.
I have cleared cache partition, done a factory reset and deleted third party apps. Nothing has resolved the issue. When I did the factory reset, the phone didn't crash for a good few days then started doing it again.
I just cannot work out what it may be and it's getting really frustrating!
I really hope somebody can shed some light on this, I am trying to avoid going down the return route.
Many Thanks in advance for all your help.
Hassan
Hi my mate had the exact taste problem with his s7 Edge single dim version, it woody of freeze and reboot and pixilated just as u explained and turned out his phone his cpu overheated and this was the result of it, he then returned it to Samsung and he received a brand new handset so best is to maybe return it as it sounds to be a faulty handset.
Sent from my SM-G935F using Tapatalk