Related
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
so i have a mytouch 3g with the perfected SPL (i believe ... says HBOOT-1.33.0006 when I check the version with back+power) and I've been using AmonRa's 1.6.2 rom for quite some time now.
I have been looking to upgrade to the Eclair roms floating around the forums which states that it requires a newer SPL so I downloaded the Engineering SPL 1.33.2010 along with the new rom
My question is (after some research) can i just boot into recovery mode and flash the new SPL that way? or is the only way the goldcard way?
You can just flash from the recovery images, but make sure the spl is completed and then he upgrade let me know how it goes
thanks, i'll give it a go and hope it doesn't brick
OK so i got the ENG SPL to install with no problems, but I can't get the rom to install
i'm trying to use Eugene's v2.3 rom found here http://alldroid.org/viewtopic.php?f=130&t=515
it flashes, says install complete, but upon reboot, it loads the mytouch splash page, then about a minute or 2 later, it loads this strange screen with colors that form an X in the middle of the screen and keeps doing that ... i've never seen that before so I flashed back to the 1.6.2 ion rom i used prior
anyone have any ideas?
thats the boot screen...the first time i got it I had to wait 45min for it to finish loading the rom....restarts (after first boot) are quicker....just be patient...I suggest flashing + rebooting then going to sleep...wake up in the morn...if its still going then u have a prob.
This is the screen ur getting right?
http://www.youtube.com/watch?v=lAFSEsEZnnE&feature=player_embedded
yeah, tahts the screen...scared the crap out of me...doesn't make any sense to use an "X" as the boot screen as "X"s are a negative symbol ... i did wait it out, however, took about 5 minutes, but it worked!
I am now running on the 1.33.2010 ENG SPL with eugene's 2.1 rom and it is quite flawless (minus the fact that there's no camera). Hope the camera fix comes out soon!
Hi, everyone:
My phone is Vodafone G2 Magic 32A, a problem has confused me for a period. When i tried 1.6, the problem occurred.
With any 1.5 rom, the phone work well. But with 1.6, 2.0,2.1 rom, the phone always auto reboot or crashed, whether i use the phone or not, and i think the reason is not a specific operation or software. I have tested all the rom i can find, and change the spl and radio for several times, but the problem still have. And the same problem also confuse other people. We have a group to discuss how to solve the problem, we all think the reason is not the hardware error, because the 1.5 version always work fine.
Here is some infomation of my G2 phone
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Jun 2 2009, 17:27:03
we hope someone can help us to solve the problem
Hi，my phone is TIM，the information is
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0008(SAPP10000)
CPLD-12
RADIO-3.22.20.17
the problems is the same as yours.
Very sad about it.
me too!
but,I have changed my phone SPL2007 did not crash when the FLASH ROM.
which kind of rom did you flash?
The same problem i had, as lots of people.
Unless rom 1.5, other rom include 1.6, 2.0 and 2.1, it made the G2 crashed and auto reboot.
We have doubted about the recovery img, spl, radio, and so on. And someone have tested all of them, the problem have still being.
This is my G2 information:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009(SAPP10000)
CPLD-12
RADIO-3.22.20.17
May 8 2009,21:02:32
Hope someone can help us.
Thanks.
Same problem!
HTC G2
, is anybody can help us?
Or teach us a way to find the really problem
for example: a program running in our Magic phone, when the phone crash or reboot, it will record some useful infomation.
I had a similar problem, my G2 freezed totally when used other roms.
In my case, it seemed to be the kernel. Using 2.6.27 worked fine.
so vanilla android 1.5 worked, and GyD and MyHero worked, but not others.
When I ran MyHero, I also noticed that my CPU didn't seemed to scale.
I ended up substiting my phone for another of the same model.
using "adb logcat" didnt give me any information, the error did never get logged.
Hey, got the. Same. Phone running on. Android. 2.1 for a while now
You have too flash the. 32b rom. And. Then. Before booting the 32a port. Witch. Provided. On the same site where you downloade the rom from
I had. The same problem,
Good luck,
hi, i have 32A spl1.33.2010 recovery 1.5.2H radio 3.20.22.17
i had similar problems with stuck at htc boot screen or crash part way through set up, i was wiping and partitioning my sd card 96/512/fat32.
what worked for me was upgrading my spl and recovery to the above,
do back up
wipe- data/factory; davlik-cache;sd ext partition,
no partitions on sd card,
flash rom then flash 32A port then reboot system
currently enjoying ahmgsk port of eugenes espresso/hero 2.1 rom
i hope this helps??
Hello, iv got similar problem, on 1.5 work fine too but on on ROMs above 1.5 reboot my phone when i i use my camera i can do 1 picture but when i want to delete it phone just reboot, on google goggles too. I try Cyanogen ROM, SuperD and 1 ROM on android 2.x version. Someone maybe have same problem and fixed it ? or someone know how to fix it and btw i wiped data i try to install same ROM several times too and nothing helped
I'm having big problems with my 32A and any 1.6 ROM. Never tried changing the SPL though, but I've tried anything else: partitioning, installing different ROMS, almost every combination of wipe/reset and so on.
How could changing the SPL affect stability of a ROM?
Hi,
I have an HTC Magic 32A and lately i've decided to flash it with cyanogenmod v4.2.15.1 everything went well except for when the OS boots, applications start to crash, phone reboots so I tried to re-flash but same exact problems happen...
Is there a ROM available that is stable and up to date??
Also, Could you please point me to some guides?
Thanks,
N4rc071x.
I find CM crazy stable... strange how you encounter those problems.
same here..no issues on my CM. try running fix permission.
I re-flashed with Magic GyD and everything is working fine now... phew!
Is it possible to flash a recovery/engineerings SPL ROM with HBOOT-1.33.0009?
Are there any tutorials I can follow?
Are you using the fender (headphone jack) or just the normal one? If you're using the normal one, find the cursorsense 1.2.6.1 rom and he gives you details on how to flash an enginerring spl. PLEASE Don't flash the Hero SPL/Radio. You wanna use the 1.33.0010 and the radio that goes with it. (NOT THE 6.35)
Are there any problems with radio 6.35?
So basically when flashing, you need to take care of matching the SPL/Radio versions right?
Are there any android 2.x (possibly with flash support) that don't require 6.35??
Since you're looking for a stable rom, I would suggest not going to 2.x It's ok to use but there may be lots of problems. I tried it and went back to 1.6 right away. Some people like it though so it doesn't hurt to try.
And there are no problems with the radio 6.35 and yes you have to match spl/radio. You may not brick if you don't match (it'd cause problems though) but I wouldn't wanna give it a try lol
Thanks a lot for your help mate
Hello all,
I have just got a new HTC Dream and proceeded to do the following :
I started by flashing dreaimg.nbh drc 7, then a rooted using telnet following the instructions on cyanogen wiki. I then flashed the new radio 26i and the death spl. I have installed cyan 5.0.7t2 plus google apps.
Now however when I boot it up it is staying on the g1 boot up screen and not continuing. Earlier versions of cyanogen mod work but not 5.0.7 for some reason.
Any ideas?
i just had the same prob. im on moto droid. comming from droidmod 1.0 after reboot after flashin newest cgnmod it jut hangs on moto logo. went back to last backup
Cyan doesn't support the droid does it? :S
Mraellis said:
Hello all,
I have just got a new HTC Dream and proceeded to do the following :
I started by flashing dreaimg.nbh drc 7, then a rooted using telnet following the instructions on cyanogen wiki. I then flashed the new radio 26i and the death spl. I have installed cyan 5.0.7t2 plus google apps.
Now however when I boot it up it is staying on the g1 boot up screen and not continuing. Earlier versions of cyanogen mod work but not 5.0.7 for some reason.
Any ideas?
Click to expand...
Click to collapse
Make sure the death spl was installed and make sure to wipe before installing. Install cyan and then gapps without rebooting in between.
I usually have to install gapps after cyanogen. Some people before, some people after. It's kinda odd.
Also, for the droid, there is a cyanogenmod. Dunno if CM5 is on there yet, though. Don't really know anything about the Droid.
I read somewhere that there was a bug in 5.0.7 where you can't use the terminal method to install it, you have to use amon-ra recovery instead (I can't find the page anymore)
I think CM 5.0.8 fixes this