Database Info

[FIX] The screen unresponsive fix

Obviously... YOU NEED ROOT... and you NEED NAND unlocked... And preffered a custom rom... and also SetCPU 1.6.0... VERSION IS CRITICAL... oh and buy it its only 2 bucks...
im on hardware 0002 idk about if this works 0003
Ok... go here
http://forum.xda-developers.com/showthread.php?t=695750
boot into fastboot (requires NAND unlocked)
adb reboot bootloader
then flash the overclock zimage with command
fastboot boot zImage_supersonic_oc-uv
mind you that the zimage needs to be in the folder with abd and also fastboot.exe... it souhld be packed already in the A SDK...
now... itll boot...
go to SetCPU... ...use autodetectDO NOT PUT IT at 1228...itll reboot cuz of the kernel panic...
put it at the second to last setting
voila... screen issue fixed
OMG ALL CREDIT GOES
to coolbho3000
once you reboot it will lose the zimage

could you give a brief explanation how this fixes the unresponsive screen? and by unresponsive screen are you referring to the evo on the bed (improperly grounded) where it doesnt respond to touch inputs?

anytime you mess with cpu mhz, you risk briking your phone.
These are tiny chips and they don't like heat. Unless you hooked up a liquied cooler to it or somthing. Then i can see how this would help, but not fix it.

changed title. To be honest I had no idea what the thread was about from looking at the title. Also removed unneeded swearing.

Just wanna say that I tried this, but my phone locks up after like five seconds.

nevermind...

This will only work on hardware revision 002 devices not 003 they won't boot toasts kernel source but does tell us that it can pretty easily be fixed once HTC decides to wake up n give us source

im not gonna try this, but would like to know how this fixes the issue... simply over clocking fixes it?

what's strange:
i have 2 evo's .. my wife's and mine. i've left hers on stock 2.1, updated to current. mine's fully rooted, running DamageControl 3. Both have the same Seidio Innocase2 and Zagg screen protector as in the video that shows this issue.
Mine has no issue while ungrounded (sitting on the coffee table). Hers does. Neither have any signs of the screen 'unpeeling' from the phone itself, so that's been ruled out.
I'm guessing that this has to do with something that's different in the two ROMS, stock versus DC3. I haven't had any other platforms to test on though. Can anyone else test this at all? It seriously seems like the issue has been fixed unintentionally in post-root created ROMS like DC. We really need more testing on this... This one's really hit/miss, and there's no real distinguishing factor as far as hardware, specific software elements, available resources, etc as of yet. I just know that I don't have the issue on mine.

myndwire said:
what's strange:
i have 2 evo's .. my wife's and mine. i've left hers on stock 2.1, updated to current. mine's fully rooted, running DamageControl 3. Both have the same Seidio Innocase2 and Zagg screen protector as in the video that shows this issue.
Mine has no issue while ungrounded (sitting on the coffee table). Hers does. Neither have any signs of the screen 'unpeeling' from the phone itself, so that's been ruled out.
I'm guessing that this has to do with something that's different in the two ROMS, stock versus DC3. I haven't had any other platforms to test on though. Can anyone else test this at all? It seriously seems like the issue has been fixed unintentionally in post-root created ROMS like DC. We really need more testing on this... This one's really hit/miss, and there's no real distinguishing factor as far as hardware, specific software elements, available resources, etc as of yet. I just know that I don't have the issue on mine.
Click to expand...
Click to collapse
update -- the issue actually goes away completely on hers when i reboot after ~24 hours of use. it's got to be a resource allocation thing, which would explain it being corrected by DC. thoughts?

I... don't think this will work. I didn't touch anything related to the touch screen. Otherwise, anything using toastcfh's source will fix this as well.

coolbho3000 said:
I... don't think this will work. I didn't touch anything related to the touch screen. Otherwise, anything using toastcfh's source will fix this as well.
Click to expand...
Click to collapse
good point, so the froyo dev builds shouldn't' have this issue since they're using his kernel too.
we seem so vague on details so far, but this is good some people are able to resolve the issue ... heading in the right direction!

see, i had a feeling someone already had fixed this one in the mix! good deal. i'd say stay away from this until we understand exactly what it is exactly. especially when it involves messing around setups. just my .02.

Screen problem?

Hi,
I have a problem with my TF700T. For s few seconds after waking my tablet up, image displayed has wired colors. It looks like screen displays less colors and in few seconds it fluently becomes as it should be (pls see attachements).
This only takes place when tablet is in eco mode. In balanced and normal mode everything is OK.
Does anybody have similar effect in eco mode?

I have this too. Not that severe, but i have noticed it.
I think this is due to governor change or something related to cpu clocking. I had this with many custom roms on my phone and i don't think is a hw problem at all. So, no worries.

Svashtar said:
I have this too. Not that severe, but i have noticed it.
I think this is due to governor change or something related to cpu clocking. I had this with many custom roms on my phone and i don't think is a hw problem at all. So, no worries.
Click to expand...
Click to collapse
Thanks for reply. It also came to my mind that probably in eco mode CPU is too weak to handle full HD display.
All in all, such thing should not take place on tablet that is supposed to be one of the best and is one of the most expensive on the market.

PiotrekZ said:
Thanks for reply. It also came to my mind that probably in eco mode CPU is too weak to handle full HD display.
All in all, such thing should not take place on tablet that is supposed to be one of the best and is one of the most expensive on the market.
Click to expand...
Click to collapse
Agree.

Looks like last firmware update has solved my problem. Screen works just fine now

Rotating fails :( Only at my device?

I made a video, here is the link:
http://youtu.be/_4KC8wnc_zE?t=23s
It won't rotate correctly, I already tried several apps for setting the wallpaper, but no one worked
This seriously looks sh**
Is it only my device that has this problem?
Greetings

What do you mean it fails? It looks exactly just as it should. I have audio off, so if you said something crucial there, can you repeat it here.
I don't see anything worrying apart from a slight lag, but this may be your camera.
Edit: Sorry, after looking at it for the second time and in the full-screen mode now, I can see what you mean - there's a black bar that gets updated later. It certainly shouldn't be this way. I had similar issues with pdf rendering in the power-saving mode. What settings are you on?

d14b0ll0s said:
What do you mean it fails? It looks exactly just as it should. I have audio off, so if you said something crucial there, can you repeat it here.
I don't see anything worrying apart from a slight lag, but this may be your camera.
Click to expand...
Click to collapse
I dont have mine yet, but compared to my wife's ipad2, with whats in the video, it seems there is a lot of lag?
Shouldnt that thing turn almost a second after you have turned it?

It can take like 2 or 3. It seems slower than iPad, but also have in mind that iPad uses the animation that lasts about a second itself. Anyway, should be faster, I agree, although I think it's only a little worse on this video than what I normally experience, so if there's a speed issue, it's not rotation issue, but a general one. Try different power modes and be sure to update to .26 firmware.
Edit: Sorry, after looking at it for the second time and in the full-screen mode now, I can see what you mean - there's a black bar that gets updated later. It certainly shouldn't be this way. I had similar issues with pdf rendering in the power-saving mode. What settings are you on?
The thing about wallpaper misguided me a bit though.

lardo5150 said:
I dont have mine yet, but compared to my wife's ipad2, with whats in the video, it seems there is a lot of lag?
Shouldnt that thing turn almost a second after you have turned it?
Click to expand...
Click to collapse
No, that is not "real" lag, it has been included to make sure you really want to turn it to landscape for example (as far as I know).
On my galaxy nexus with 4.1 the lag seems to have gone, seems to me like they disabled it there.
So just wait for 4.1 if you don't like the "lag".
But thats not the point. d14b0ll0s, you correctly recognized the black bar, and the picture itself seems to zoom in and out sometimes, aligning itself to the left, to the right and then in the center.
But I don't know what to do, is that definitely not the case on your device? Am I really the only one?
In that case I have to hardreset it

Not only do hard reset, but - what's more important - try re-flashing firmware (you can actually start with it). If the problem remains, return the device. I'm definitely not getting anything like that.
Use Titanium Backup or MyBackup if you have something you don't want to lose and copy the files to your PC.

Problem solved
You'd never guess what caused the problem:
_Wallpaper Wizardrii_
Deleted that and it's gone

paysen said:
Problem solved
You'd never guess what caused the problem:
_Wallpaper Wizardrii_
Deleted that and it's gone
Click to expand...
Click to collapse
Geeze, of all things
Nice job man.

Glad it's solved, but you should've mentioned you're using apps changing your desktop / wallpaper behaviour in any way.
BTW, I knew there was a reason not to like this app in the first place

lardo5150 said:
Geeze, of all things
Nice job man.
Click to expand...
Click to collapse
Luckily I haven't done a hard reset before recognizing the sh***y impact of the app
d14b0ll0s said:
Glad it's solved, but you should've mentioned you're using apps changing your desktop / wallpaper behaviour in any way.
BTW, I knew there was a reason not to like this app in the first place
Click to expand...
Click to collapse
I really should have mentioned this, but forgot it. And it's on the 2nd site of my app-launcher, just started it one time ;D

Phone getting slow after some time

My phone is dropping the framerate on touching the screen occasionally, stuttering for a short time. It is fine again after rebooting, but I am facing this problem since I got the phone three weeks ago. Does anyone else experience this? Is there a solution? I am worried this could be a hardware defect.

Try to reinstall the ROM. You can install full ROM without losing data. If that doesn't help, try a clean install.

Yes I see it too. In fact I started a thread on this in Q&A section but nobody seems to be interested
Nothing I seem to do in terms of tweaking the performance parameters seems to help. It can be fine for half an hour and then out of nowhere a few frames are dropped and it looks awful
It's ok 98% of the time but those 2% are making it hard for me to love this phone.

Lownita said:
My phone is dropping the framerate on touching the screen occasionally, stuttering for a short time. It is fine again after rebooting, but I am facing this problem since I got the phone three weeks ago. Does anyone else experience this? Is there a solution? I am worried this could be a hardware defect.
Click to expand...
Click to collapse
It sounds like a rogue app is taking control of your phone. I checked your Profile GPU rendering screenshot against mine, and indeed, mine never goes much higher above one-half length of the green line, which I think may be the 120fps limit (the green line itself is 16ms or 60fps.)
Seems to me that you need to uninstall some custom/rare apps to troubleshoot this issue.
It is definitely not normal behavior.

carlos67 said:
Yes I see it too. In fact I started a thread on this in Q&A section but nobody seems to be interested
Nothing I seem to do in terms of tweaking the performance parameters seems to help. It can be fine for half an hour and then out of nowhere a few frames are dropped and it looks awful
It's ok 98% of the time but those 2% are making it hard for me to love this phone.
Click to expand...
Click to collapse
So my guess is that either people don't notice it, but I think that's quite impossible as even some kernel devs told me they wouldn't experience this. Or it's a fault in oos itself. Or we are using an app or some setting that's causing this. Or it's a kind of defect, which I think is unlikely but not impossible.
I am about to reset the phone completely to stock with msm download tool and start from scratch. Have you already done something similar?
Next idea would be flashing Omni ROM as I believe this is one of the most clean and fluid custom roms. If all of this fails, I would start to believe it's a hardware problem.

Lownita said:
I am about to reset the phone completely to stock with msm download tool and start from scratch. Have you already done something similar?
Click to expand...
Click to collapse
I would suggest you learn adb/ fastboot to do this so you learn to know what, how and why you doing this and that.
Not really difficult but extremly helpful if you face problems.

The large amount of applications and internet uses it may slow. Better cleared all caches and it's working properly.

Question Screen weirdness on me the other day.

My pixel 7 pro freaked out on me the other day and went black on me when I played a game and didn't come back for over 15 minutes then finally was responding again. Any reason why this happened . Hopefully software and not hardware. Hasn't happened since but still concerning .

Anyone ?

Redbeardkevv said:
Anyone ?
Click to expand...
Click to collapse
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.

jaseman said:
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
Click to expand...
Click to collapse
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.

EtherealRemnant said:
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
Click to expand...
Click to collapse
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?

Hmmm

jaseman said:
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Click to expand...
Click to collapse
That's called a hardware defect if the hardware can't cope. Going blank for 15 minutes is not normal.

Hardware hmm and not software?

Redbeardkevv said:
Hardware hmm and not software?
Click to expand...
Click to collapse
What were you playing? If it was a graphically intensive game, I would definitely lean more towards blaming the hardware. It's very rare that a game can actually make a phone that unstable. In fact I can't remember the last time I've had a game make my phone unresponsive.

Roblox with my nephew

Redbeardkevv said:
Roblox with my nephew
Click to expand...
Click to collapse
I've never played that game but their site seems to suggest some rather low requirements so I would be shocked if an ARMv8 processor like Tensor 2 is going to struggle with it.
Android warning screens
Due to the very large number of Android devices in existence, we cannot be certain that all devices will run optimally even if they are running the correct version of the operating system and do not have a Tegra 2 chipset.
We have 2 levels of unsupported Android devices - skippable and unskippable:
Skippable Devices: These types of devices will get a warning telling you that your device may not be powerful enough to play experiences smoothly. This is just a warning to let you know that while your device isn't specifically supported, experiences might still run though they will likely lag a little (or a lot). Tapping outside the warning box will make it go away and the experience should keep loading.
Unskippable Devices: will get a message that informs you that your device doesn't meet the minimum system requirements. This means the device is not able to play experiences on Roblox. This message usually shows up on devices that use the Tegra 2 graphics chipset or a processor older than ARMv7. These kinds of tablets/phones do not support features that the Roblox needs to be able to function. However, users with these unskippable messages will still be able to access all other parts of the app outside of experiences.
Click to expand...
Click to collapse
https://en.help.roblox.com/hc/en-us/articles/203625474-ROBLOX-Mobile-System-Requirements

Yea I was thinking it had low requirements. Maybe bad coding ??? But then again no other app or game has caused that to happen. Sooo. Yea

I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
I've had a few wonky screen issues that hard locked my phone. Had one go black, but fortunately came back after holding power down. It once went all yellow with weird shapes/sections. And then just had some freezes with artifacts on the screen.
I'm going away for the holidays so I'll send it back when I get home if I'm still having issues. If you're going away, I'd suggest taking a backup phone just in case. Had mine die the first time when I was visiting my folks out of state. It sucked with no backup.
One thing I noticed is the screen does a fuzzy flash whenever I plug in a USB charger. It's only a split second but it is noticeable. Has anyone else experienced that?

Superguy said:
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
Click to expand...
Click to collapse
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.

V0latyle said:
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
Click to expand...
Click to collapse
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev

Superguy said:
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
Click to expand...
Click to collapse
Yeah, that's definitely a display issue. I'm talking about when the device doesn't work or respond at all, maybe vibrates on power up but doesn't respond to anything, and usually will come up as "Qualcomm Bulk USB" or something when connected to PC
Superguy said:
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Click to expand...
Click to collapse
For sure, active development may or may not have stability issues, it's all a learning process!