Database Info

Blurry Screen - Testers and Problem Solvers UNITE!

Ok, so wanted to start this because I have seen ALOT of people have this issue and I myself have loaded Hero and Non Hero ROMs onto a few MyTouch's and get this issue randomly. Figured we could start a thread devoted to people willing to test what the issue could be and people willing to try and help come up with a solution or at least pinpoint the cause of the problem.
Please try to keep this thread to the point as always guys!
I can tell you right now that I had two brand new MyTouch's today and did the exact same procedure on both and put QTek's latest Hero ROM on them and one has the blurry screen and one does not. The SPL was NOT changed from the .2006 SPL, simply loaded the FlashRec.apk, loaded Amon Ra's Recovery image, and wiped and applied the Qtek Hero ROM.zip.
Also it only happens to me when loading a Hero ROM, Cyanogen or any Non Hero works fine without any blurriness on BOTH devices.
This has happened multiple times ALL with the exact same procedure. So as far as I can tell it isn't the SPL or the ROM.
Any ideas what we can do to these MyTouch's to try and narrow something down to what the difference is between the two?

I have the same problem with mine. I rooted using the gold card method. Immediately after rooting I flashed a 32B radio then threw haykuros SPL on it. I have no problem with any of cyanogens ROMs nor with eViL 1.9 & 2.0.
I have tried:
JACxHEROski v1.4 - no fuzzys
JACxHEROski v1.6r2 - fuzzys (I'm thinking it has something to do with the kernel.)
Qtek - fuzzys
ZeroXD - fuzzys
and obviously didn't work. I'm willing to test any ideas anyone has because I'm ready to throw this phone out the window

spyz88 said:
I have the same problem with mine. I rooted using the gold card method. Immediately after rooting I flashed a 32B radio then threw haykuros SPL on it. I have no problem with any of cyanogens ROMs nor with eViL 1.9 & 2.0.
I have tried:
JACxHEROski v1.4 - no fuzzys
JACxHEROski v1.6r2 - fuzzys (I'm thinking it has something to do with the kernel.)
Qtek - fuzzys
ZeroXD - fuzzys
and obviously didn't work. I'm willing to test any ideas anyone has because I'm ready to throw this phone out the window
Click to expand...
Click to collapse
Kernel is a good place to start
Do you know what kernel versions the 4 ROMs you mention use or where we can find that info (short of bugging the crap out of the 3 developers lol)?

Hi, although I don't experience this problem, I noticed that my screen became blurry when it rotated (as it darkens it becomes blurry as well), when I was using Amon_RA's 1.2.1 ROM with his 1.0.1 kernel. I initially thought it was on purpose (it looked kinda nice), but after I flashed to his latest kernel, 1.1.0, the blurring on rotation no longer occurs. So I'd say there's a high chance it's the kernel...

Wysie said:
Hi, although I don't experience this problem, I noticed that my screen became blurry when it rotated (as it darkens it becomes blurry as well), when I was using Amon_RA's 1.2.1 ROM with his 1.0.1 kernel. I initially thought it was on purpose (it looked kinda nice), but after I flashed to his latest kernel, 1.1.0, the blurring on rotation no longer occurs. So I'd say there's a high chance it's the kernel...
Click to expand...
Click to collapse
That is most likely the "Animation" option being on or off.
Goto Settings > Sound and Display then turn ON Animation and see if that brings back you darkening/blurriness you are referring to.
If it does then it isn't the issue we are referring to, but thanks for the input! Appreciate any help/ideas we can get to solve this crap lol

Just tried that, no difference. So it may be the kernel... I've posted about it on Amon_RA's thread, maybe he can help with it more .

I have MT3G and have never experienced the blurry screen. I downgraded the SPL to 005 with the glod card method. I have C1.4 recovery. Have been runing Fatal1ty's HERO and now Zero's HERO...
I dont see how it would be the kernel. It is most likely something to do with the drivers. I wonder if there is more than one manufacturer for the touch screen or video chip or different versions.
What was the purchase date on the phones that get the blurry screen. I doubt that is software (unless somehting is enabled that is causing it to crash), it has to be hardware. There are too many people that dont get the problem running the same ROMs.

Well as far as from the threads I combed through I found this info. It seems as if:
eViL is using JAC-SKI's kernel.
ZeroXd is using JAC-SKI's also.
JACxHEROski 1.6 says its using Amon_Ra's kernel.
I know they cant all be using Amon_Ra's kernel. As far as version numbers I have no patience to figure it out now. I think I have to also agree with zambezy that it might be a hardware issue. It has to be. Same ROM's different hardware. I really should have kept my G1. The grass is always greener...

really stupid question but what sdcards are you guys using with blurry screens?

zambezy said:
I have MT3G and have never experienced the blurry screen. I downgraded the SPL to 005 with the glod card method. I have C1.4 recovery. Have been runing Fatal1ty's HERO and now Zero's HERO...
I dont see how it would be the kernel. It is most likely something to do with the drivers. I wonder if there is more than one manufacturer for the touch screen or video chip or different versions.
What was the purchase date on the phones that get the blurry screen. I doubt that is software (unless somehting is enabled that is causing it to crash), it has to be hardware. There are too many people that dont get the problem running the same ROMs.
Click to expand...
Click to collapse
I got these from others (didn't purchase them myself) so not sure when or where they got them, can't really ask them either.
But I am noticing the problem more and more frequently than when the phone first came out, so maybe there is something to the purchase date idea.
But again, how could it JUST be hardware, if some people can get other ROMs to function properly, ya know? It seems so random, certain ROMs work and certain ones don't and the ones that work for one person don't for another so the ROMs themselves must play some part, right?

spyz88 said:
Well as far as from the threads I combed through I found this info. It seems as if:
eViL is using JAC-SKI's kernel.
ZeroXd is using JAC-SKI's also.
JACxHEROski 1.6 says its using Amon_Ra's kernel.
I know they cant all be using Amon_Ra's kernel. As far as version numbers I have no patience to figure it out now. I think I have to also agree with zambezy that it might be a hardware issue. It has to be. Same ROM's different hardware. I really should have kept my G1. The grass is always greener...
Click to expand...
Click to collapse
Yea and I found that the kernel is the same on the two phones I am using right now (one works and one doesn't)...
Not kernel safe to say I think...

I was having this same problem on jacxrom orginally. Currently i unrooted, did the one click root, used the modified spl and cyanogens recovery and flashed the new jacxrom and working like a chram now.

Jrbourque said:
really stupid question but what sdcards are you guys using with blurry screens?
Click to expand...
Click to collapse
A brand new 8gb class 6 card

im just givin my 2cents in this and i think its the kernal i once used one of evil d's roms and gave mt the blur then he did another rom and fixed that so iunno but i feel its the kernal cuz wen i uploaded his new rom no blur just my 2cents

Not sure how much this adds BUT, I just unrooted my MT3G today and went the Goldcard method instead of One-Touch method. I first installed the ZeroXD with RAv1.2.1. This resulted in a blurry screen. I wiped and reformatted and tried my luck with eViL HeRo v2xx 32B and RAv1.2.1 and its running fine. First Hero ROM I have actually gotten to run without Blurring.

Could someone with a blurry screen and a 32A try to fastboot this kernel and see if the blur is fixed or not?
Code:
fastboot boot kernel.RAv1.1.0
The above command will not flash you a new kernel, it will just boot it.

Amon_RA said:
Could someone with a blurry screen and a 32A try to fastboot this kernel and see if the blur is fixed or not?
Code:
fastboot boot kernel.RAv1.1.0
The above command will not flash you a new kernel, it will just boot it.
Click to expand...
Click to collapse
I have tried this kernel with RAv1.2.1H ROM, and the screen still blurry.
Only RAv1.1.0H ROM have no blurry screen on my 32A.
Could you add Chinese Simplified to RAv1.1.0H ROM for me?
http://forum.xda-developers.com/showthread.php?t=554653
Thanks a lot!

I have the blury screen using any cyanogen mod ROMs...hero Roms are okay, just slow.
Used Amon's HBR to unroot, then flashed with the RAV1.2 recovery
Using red T-Mo mytouch (manf. 7/26)
About to replace with an entire new device.

Long shot.... : Could someone extract /system/lib/hw/lights.msm7k.so from RAv1.1.0 and push it to their blurry ROM and reboot?

My mytouch is same to this
pintspin said:
i am using following
1.33.2010 Engineering SPL 32Aboard HTC brand
i have flashed followign roms in sequence with results.. against them .
1, AMon _Ra rom ( 1.1.0) working perfectly fine...! no BLUR
2, H-hero-1.79.482.3-32A-RAKrnl.zip blurring
3, v3_Full_Hero_32a-gbo_v2 blurring
4, hofo ion rom 1.05 32a blurring
5, JACxROM v1.3 blurring
6, myhero-1.0.0 blurring
7, RA-IONv1.2.1H.ziRom-RA-IONv1.2.1H.zip blurring
8, Rom-RA-IONv1.2.0H.zip blurring
9, cyanm-4.0.2-32a.zip blurring
1o .....again.... went back to AmonRa 1.1 the best working rom for me so far....! i beleive all the new roms after 1.1 update are having some problem ....
one more thing i noticed that after flashing...every rom was working perfectly means NO BLUR but it will be blurring just after the screen go to sleep for once and when it came back from sleep it becomes blurry and the GAMMA seems to be increased automatically
Click to expand...
Click to collapse

[Q] I regret flashing CM7

I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?

Nandroid backup didn't work?
And what problems are you having with gapps?

Me myself have problems in CM7 as well -> the gapps cannot be installed (well, CWM didn't mention any error when installing) but after boot up no gapps is there, after tons of research here and no solution too, and I rolled back to froyo.

Barfaroo said:
I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?
Click to expand...
Click to collapse
CM7 working fine on my HD2. I'm running it from my SD though because I don't want to root.

From what I understand the GPS will not be fixed by a cm update its got something to do with the hardware you have to do http://forum.xda-developers.com/showpost.php?p=11853529&postcount=2085 this to fix it. After I did the gpsclr fix mine has worked flawlessly. Also I don't think its only cm roms that have this issue.
Sent from my PC36100 using XDA Premium App

ah i mistook gps for gapps. my mistake... lol

Odd... CM7 works perfectly on my Motorola Droid and Nook Color and I've also never had a GPS problem (even on older nightlies). What make and model is your phone? And are you running off a CM7 nightly (if so what build?) or an RC (the latest is RC4 as far as I know)?

Gps worked perfectly using Froyo (rooted, ROM from AddictiveTips). I have an HTC Desire (CDMA) from US Celular. No, I'm not running off nightlies. I installed CM7 RC4.
The fix suggested above sounds like I would have to first flash a sense ROM and then come back to CM7. Other than giving me extra space for apps, it isn't worth it. I could get by with Froyo since everything worked with it. With CM7, the gps doesn't work at all. Maps keeps searching for satellites and never finds them. I really miss not having voice directions.

Barfaroo said:
I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?
Click to expand...
Click to collapse
all you need to do>
get a fresh rom myns or any that you like in reality it doesnt have to be sense if you just want to get away from cm7 altogether
but then boot into cm7,
plug it into your computer
load the new rom onto your phone
boot into recovery
then install the new rom.
sound good?

I appreciate the suggestions, but I decided to go back to Froyo and my gps is working again! Unfortunately, Clockworkmod won't let me re-install any backups, and I have no idea why. All I get is a blank screen. Fortunately, I can install from the SD card, which I did to get Froyo back. Since nandroid backups don't seem to work, I have to setup my phone from scratch everytime I make a ROM change.

[Q] Phone shuts down.

My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody

What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App

The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123

Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...

SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?

I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.

I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.

Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.

Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..

Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...

I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps

I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?

Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.

This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.

And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...

I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?

Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.

I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.

Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.

[Q] Can't turn screen back on after hitting the power button in the camera app

This is doing my head in to the point I have borrowed a new HTC Sensation only to find the problem exists on this phone also.
When using the Camera App If I hit the power button the screen turns off. I am then unable to switch the screen back on - It appears the phone crashes.
Behaviour some times differs depending whether I have taken a photo or not.
The following behaviour is observed:
The lights stay illuminate on the soft keys at the bottom of the screen.
The phone can receive calls how ever it doesn't ring and I unable to answer them.
This problem is confirmed on 2 seperate devices which have been flashed with:
Android Revolution HD 3.6.12
10.58.9035.00U_10.15.9035.02_2 radio
I have also run super wipe on the phone before installing the HD Rom.
Please help!?

Ive also had this problem on a few diffrent roms.
But i flashed amaze camara update, and not had any prob since.
Im now running the latest ICS with sense, with what ever camara software came with the rom. And not had any problem

big_sw2000 said:
Ive also had this problem on a few diffrent roms.
But i flashed amaze camara update, and not had any prob since.
Im now running the latest ICS with sense, with what ever camara software came with the rom. And not had any problem
Click to expand...
Click to collapse
Cheers moved to ICS and its now fixed.

edwardblum said:
Cheers moved to ICS and its now fixed.
Click to expand...
Click to collapse
Having the same issues on both mine and my wives phones, both running AR 3.6.11 along with lag and other issues! Pretty fed up - and considering a different ROM. How is the ICS ROM, any issues like the 3.6.11? Is it hard to install?

I would try Elegancia ICS. Maybe a little pain to install, if you need to update your firmware.
http://forum.xda-developers.com/showthread.php?t=1429953
Firmware
http://forum.xda-developers.com/showthread.php?t=1432220
You may have to superCID if the firware dont work. Also easy todo
See post 4
http://forum.xda-developers.com/showthread.php?t=1192300
Have a read of the last 10 pages or so of the ICS thread for superCID info if your stuck, but it is easy.

I will give it a try! Do you just download the zip firmware and flash it?

It's not a rom problem, it is faux's kernel problem.
You can flash bricked kernel to solve.

banasik72 said:
I will give it a try! Do you just download the zip firmware and flash it?
Click to expand...
Click to collapse
Put the img zip directly on the SD card, not in any folder.
Boot the phone in to bootloader Power on volume down same time.
Just follow the instructions.
DO NOT POWER OFF REMOVE BATTERY ETC.
You will have to remove file from memory card before rebooting.
If you fail with the upload, then you will have to superCID

[Q] Reaper ROM problem

I'm having some trouble running the Reaper Rom. My phone is S-OFFed with revolutionary and using Hboot: 0.98.2000. I have been able to succesfully install the MIUI ICS ROM and CM7.
I have formatted and wiped everything from 4EXT recovery and then installed the latest Reaper 2.1. During the first boot it freezes at the ROM loading screen. After about 20 minutes it reboots and this time loads the ROM but then freezes again after about a minute. This then continues in a loop.
Has anyone else experienced similar problems and has any ideas about how I could fix this?
Thanks for any help.

Does this happen each time you clean instal it or just the once?
Possibly try to re-download it again in case you have bad download
Swyped from my Desire S using XDA Premium

I've tried installing it a few times and always the same problem. The MD5SUM value is correct for the download but is there still a chance it could be bad.
I also tried installing an earlier version Reaper 2.0 but had the same problem with that.
Could it be a specific incompatibilty between something on my phone and Reaper since the other ROMs I've tried all work OK?

rajamuffin said:
I've tried installing it a few times and always the same problem. The MD5SUM value is correct for the download but is there still a chance it could be bad.
I also tried installing an earlier version Reaper 2.0 but had the same problem with that.
Could it be a specific incompatibilty between something on my phone and Reaper since the other ROMs I've tried all work OK?
Click to expand...
Click to collapse
No, your phone probably can't handle the default voltage settings. Search my posts on the reaper thread for a "stability patch" I posted for a early version. You're the third person with this problem.
Cheers
Sent from my HTC Desire S using xda premium

Thanks for the advice, I'll try it tonight. Hopefully it will work since it seems like a graet ROM.

Thanks lowveld, the stability patch worked perfectly.