My X1i won't run GLbenchmark. It installed fine, and the menu comes up when it starts. I click "run the test" and the screen flashes various colours for ~5 seconds then stops on a random colour and goes nowhere.
If I tap the screen it goes away and I am back to the today screen.
SOMETIMES it finishes the flashy colours and draws a multicoloured line across the screen, then freezes.
Is this indicating a faulty unit?
Related
Last night my XDA Mini S froze while using PIE, so I did a soft reset, put the phone down and went to sleep. Noticed this morning that it's stuck at the Windows Mobile splash screen - still in Landscape mode which is what I was using when PIE froze. Done another soft reset, same problem. My LEDs are flashing as usual, one green and the Bluetooth one.
Any ideas?
Thanks
Ok, it started working for some reason - but I noticed when it got to my today screen that my NotesToday plugin wasn't there. I went into Settings > Today > Items, and NotesToday was ticked. I unticked it, clicked OK, then re-ticked it and it showed up again on my today screen. Fine. However now everytime I press the power button to come out of sleep mode, my Today screen flashed up fine for about 0.5 sec, then flashed white for a millisecond, then comes up fine EXCEPT the whole "top" bar (i.e. the part of the screen with Start button, clock, signal strength, etc) stays solid white, and I can't see any of those icons. Rest of the screen is fine. If I click Unlock, the whole screen is fine after that.
Help!
I had a similar problem with a different part of the screen staying white after coming out of hibernate (the O2 active UI sidepanel)...Hard reset fixed it and the problem hasn't returned (although I don't use the O2 UI now...)
If your device freezes on the Windows loading screen, then soft reset it and while it is loading the next time, press one of the hardware buttons, such as the D-pad or the green or red phone buttons, continually as it loads. This should keep the lights behind the buttons turned on, and it should load Windows without a problem.
Had the same error on my phone, I think it tries to hibernate as it loads Windows or something equally stupid. Pressing a button continually prevents this and allows it to load normally.
i was using wifi and opera browsing while all of a sudden i though it was reloading but the screen went black except for the top bar where the signal, volume and connection icons are, when i press any button the screen appears to react like if i pressed the lock button the top showed it was on the lock screen but still black below the top bari could not soft reset since the blackpart of the lcd was black and had no slider, i attached the USB cable and the Active sync/Disk Drvie screen appear when i chose either active sync or disk drive it got stuck on that page but the top part still reacted to the buttons so i took out the battery and put it back in
what could have been the problem, was it an issue with the phone but the screen though black was bright since the led lights were on so was it Sense having the problem the last hing i remember doing while using opera was aborting cleanRAM since i was using the device i did not want opera to close
any ideas?
After doing a hard reset on my perfectly-functioning Pro the other day, the screen and buttons have now stopped working. My question is two-fold:
1. What the heck is going on?
The phone worked fine until I did the hard reset. Now, when I do a hard reset, everything appears to work correctly through the screen-alignment. The screen responds properly at that stage. Immediately afterward, the normal Today screen pops up for a split second. After that, the "Treo Customization" screen comes up, and that's where it all goes to hell. After the "Treo Customization" runs its course, the phone says "tap screen to reset." After tapping the screen, the phone responds and resets itself.
After that, a blank today screen appears. The tool bar on top is there and the background is there, but that's it. The screen and buttons are unresponsive except to brighten the screen after it periodically dims. Several other functions continue to work. I can activate wifi via the side button. The top button turns off the screen. Strangely enough, the QWERTY keyboard is completely unresponsive, except that the search button works (alt button and magnifying glass).
Does this sound like a hardware problem? Could it be fixed with a flash and new rom?
2. I tried to flash the phone and install a new rom to see if that would help, but I was unsuccessful for the following reasons: 1) When I run PANTHER_CDMA_HSPL_V101, the bootloader screen appears, but immediately upon that occurring, my sync connection disappears, so I can't proceed through my computer. 2) I can't run the manual flash program (SSPL-Manual-PantherCDMA) because I have no functioning controls on the phone itself.
Any ideas? Is there any way to achieve a flash on an unresponsive phone, or should I start shopping?
Thanks!
Mark Pemberton
Hi,
I experienced today a strange behavior:
I used my nook, turn off wifi, let it in my bag for 1 or 2 hours and when i tried to wake it the screen didn't turn on.
At first i though it was SOD but when i looked closer to the screen there was something on it, it was the CM7 boot logo (the tony hawks droid
The logo was not very visible, most like old "ghost image" on CRT screen when he same image is displayed for long periods of time.
I should have taken a photo, i will if it reproduce.
Kinda sounds like it was rebooting without turning on the backlight. Could you see the arrow circling? I've had "n" turn on the backlight with no image, but tapping power turns off the backlight, then tapping it again turns the screen on properly.
Sounds like somebody's state machine has a leak...
i will never know (i pressed power 8s, if it was booting, i just stopped it)
With my settings set to Automatically lock (immediately after sleep) and power button instantly locks with a visible patter screen lock, my Nexus 7 on wake-up [pushing the power button immediately] either right after an invalid pattern code (where device then sleeps) or waiting a few seconds with no activity until the device sleeps (where the Nexus 7 fades to a black screen) will have a delay in bringing up the lock screen OR sort of flicker presenting some sort of black and white bar lines background at the bottom half of the screen for a split second before bringing up the lock screen. In essence, when waking the phone from sleep, the screen "glitches" for like a fraction of a second where the "glitch" is a set of white lines that flash on the screen before the lock screen appears on the display. This "rarely" occurs and has to be done fairly quickly, but I have seen it a few times as I continuously tried it over and over again; you can blame my OCD Anyway... I was wondering if this is normal or it is in fact a defect? It doesn't seem to affect the performance of the device itself.
The following are video recordings of the "issue":
http: //youtu.be/lFhr0DxhA_Q
http: //youtu.be/yTmrWgBoAjQ
Does this happen for anyone else?
Thanks in advance!
Praesidium said:
With my settings set to Automatically lock (immediately after sleep) and power button instantly locks with a visible patter screen lock, my Nexus 7 on wake-up [pushing the power button immediately] either right after an invalid pattern code (where device then sleeps) or waiting a few seconds with no activity until the device sleeps (where the Nexus 7 fades to a black screen) will have a delay in bringing up the lock screen OR sort of flicker presenting some sort of black and white bar lines background at the bottom half of the screen for a split second before bringing up the lock screen. In essence, when waking the phone from sleep, the screen "glitches" for like a fraction of a second where the "glitch" is a set of white lines that flash on the screen before the lock screen appears on the display. This "rarely" occurs and has to be done fairly quickly, but I have seen it a few times as I continuously tried it over and over again; you can blame my OCD Anyway... I was wondering if this is normal or it is in fact a defect? It doesn't seem to affect the performance of the device itself.
The following are video recordings of the "issue":
http: //youtu.be/lFhr0DxhA_Q
http: //youtu.be/yTmrWgBoAjQ
Does this happen for anyone else?
Thanks in advance!
Click to expand...
Click to collapse
*Bump*