Hey guys, ran into a problem, I was able to root mytouch 3g and installed
http://forum.xda-developers.com/showthread.php?t=538633 3.6.8 release 4. Problem is when the phone goes sleepmode (screen turns black) after you wake it up the screen turns fuzzy/blurry. Is there an easy solution to this problem? or should I install a different ROM? Any suggestions? I really like this rom besides the blurry screen issue.
thanks for any help!
Hey same thing is happening to me...I wiped and reflashed but still having the problem
This is a problem many of us has encountered, I don't know why, try other ROM's I have found 1 that works for me.
I think it's a issue with the refresh rate of the screen.
Ditto. I have this problem as well with Cyanogen v4.0.1.
I've done the customary wipe prior to installing the ROM but the problem is the same.
This is the ROM I am using at the moment with no blurry screen problem.
http://forum.xda-developers.com/showthread.php?t=549755
i'm not using cyanogen but i am experiencing this issue with ZeroXd's Casper-4.2r2. i'm going to wipe the phone again and start over. So far, the Casper ROM is the only one that won't work for me and it was working well too
I'm having the same issue, but have ONLY noticed it with HERO-based roms. The Cyanogen 4.0.1 rom looked/worked fine.
Interested in the "fix" here...
Screen turns blurry
I am having the same issue but ONLY with the Hero roms. Cyanogen's new 4.xx roms are the frackin bomb so I'm not too sad. They work great for me. Definately want to know how to fix the issue though.
alot of ppl have this problem most of hero roms there is no fix yet sucks i know
yipcanjo said:
I'm having the same issue, but have ONLY noticed it with HERO-based roms. The Cyanogen 4.0.1 rom looked/worked fine.
Interested in the "fix" here...
Click to expand...
Click to collapse
what fix >?
Just experienced it for the first time after installing Drizzy's NoName V3. Have installed 10-15 roms prior and never experienced it until now. Trying out another Hero rom at the moment, will let ya know.
Update: QTek's rom seem's to work alright for me without the blur.
format sd card
seems to fix the problem....at least it did for me...
korndub said:
seems to fix the problem....at least it did for me...
Click to expand...
Click to collapse
The v3 noname I tried was on a newly partitioned/formatted sd card. :-\ QTek's is still going strong though. With the v3, after the first sleep it was blurry. I've been running QTek's for about 30-45 minutes now and no issues.
+1 to this issue. i had the same problem with some cyanogen ports in the sapphire thread, but using new cyan roms has not given me any issues. also noted that formatting does not help.
possibly an issue with engineering SPL?
i also noticed that a rom would flash fine, but as soon as my screen would lock thats when the issue would occur.
i wonder if it is a kernel / spl incompatibility. I had this same issue with JACxROM that runs great on and ION and is bassically the same phone. So I am a little confused. I am going to try and use Cyanogens newest 4.0.1 build and copy the boot.img to a JACxROM v1.3 and see if it does the same thing or not. Will report back to let you know what happened.
I have tried to use following HERO ROMs but they all turns blurry after sleep mode (when I unlock screen by pressing menu or similar button)
Champion v2, Fullv2 No Name, Superlite Hero etc.
Installed on myTouch 3g after rooting it using one click.
arunchowdhary said:
Installed on myTouch 3g after rooting it using one click.
Click to expand...
Click to collapse
Is this possibly *part* of the issue here? I'm using the "1 click" root method as well. Also, my SD card does have the proper 3 partitions, if that means anything.
Just installed the JACxHEROskiv1.4 ROM, which does not appear to exhibit this behavior. Nice ROM so far!
yipcanjo said:
Is this possibly *part* of the issue here? I'm using the "1 click" root method as well. Also, my SD card does have the proper 3 partitions, if that means anything.
Click to expand...
Click to collapse
I used the gold card method to root and I am experiencing the same thing with all the HERO roms. When you try to reinstall Cyanogens ROM's afterwards you experience the same thing. Only way I found to fix it was to format the SD card.
:/
We really need a fix for this. I am dying to use some Hero ROM's.
Well I fixed mine, I clean wiped everything and installed the cyanogen 4.0.1 rom. All is good now. I haven't messed with Hero, but I am liking the new cyanogen rom and he fixed the screen problem as well.
timafey said:
Well I fixed mine, I clean wiped everything and installed the cyanogen 4.0.1 rom. All is good now. I haven't messed with Hero, but I am liking the new cyanogen rom and he fixed the screen problem as well.
Click to expand...
Click to collapse
how did you go about clean wiping everything? I went ahead and bought a brand new sd card just to see if a fresh sd card cures it as well.
I did a full wipe from Senseay where everything was working fine even the amaze camera, but I had bad battery life. My friend recommended insert coin. I did a full wipe, cache wipe and dalvik wipe, then installed ic 3.4.0, also installed tmous addon and installed bricked 1.41. Everything seemed to work fine. I needed to take a pic to win a prize from school and the camera didn't work, force closed. I downloaded the amaze cam mod, and the revert back to 3.5 mod from ic folder of mods. Nothing is working! Needless to say, I didn't win any prizes from my school. Does anyone know how to fix this issue? Also in about an hour that I've been using the phone, my battery is half full, I was getting at least 6 with senseay. Any recommendations for that as well?
i dont know why. i have insercoin 3.4.0 with the latest bricked kernal and my camera works fine. i still have the stock camera. did you flash the camfix as well?
if you flash the bricked kernal without flashing the camfix your camera will not work
I flashed both camera fixes after I noticed the problem.. still nothing..
Hi All,
I own a Motorola Defy. I am kind of new to android developement. i had 2.2 on my phone and wanted to upgrade, followed all the steps available online for cyanogen 7.1, liquid arc, etc. with all the ROM's i had the same problem. Everything goes fine, until i reboot my phone. The moment i do that after installing new ROM. I loose network connectivity and a pop up msg comes up continously saying android.phone.com stopped responding. From there i have to do the complete wipe once again. i read in some forum about flashing radio, however i dont see this option in my recovery mode at all.
Anybody who knows how to resolve this????????
I looked this up in the forums. This applies to going from 2.1 to 2.2, but sounds like it may help you. http://forum.xda-developers.com/showthread.php?t=947578
Thank you for the reply.
However, I was already running Froyo on my defy. I can also go back to that via RSD or by restoring it to the ROM i backedup before i started this testing. My concern is why i am not able to Install this custom ROM and make it working when all others can do it without any issues. I am still running Cyanogen nightly ROM (2.3.7). I also know the moment i restart my phone it will loose network connectivity and will keep getting those pop msgs. Is there a way to curb that.
Appreciate the help...
You can look for MIUI for the defy. I have also MIUI on my Defy and it works perfect
Sent from my Galaxy Nexus using XDA App
Thanks for your reply....
I was missing the defy baseband update. Thank fully that fixed the network connectivity issue. Now i am running ICS 4.0.1 perfectly. Except the camera everything is working smooth. Had little issue with restore from Titanum backup. But an unregistered version of TB fixed it.
Flashed the CM 10 ROM on my HTC One S. Everything works amazing, but for some reason the autoflash on the camera doesn't work at all. If I turn the flash on manually it works.
I have tried a couple of other camera apps (camera 360 and Ucam) and the autoflash feature works with no problems.
Has anyone had this happen or does anyone out there know of a fix.
Thanks for the help.
scottgold said:
Flashed the CM 10 ROM on my HTC One S. Everything works amazing, but for some reason the autoflash on the camera doesn't work at all. If I turn the flash on manually it works.
I have tried a couple of other camera apps (camera 360 and Ucam) and the autoflash feature works with no problems.
Has anyone had this happen or does anyone out there know of a fix.
Thanks for the help.
Click to expand...
Click to collapse
I don't remember issues like this on CM10 though I am currently having autoflash issues with CM10.1 nightlies. When you say doesn't work - does it still take a picture with no flash or does it not take a photo at all? In CM10.1, the camera seems to "hang" when the flash is required.
It actually does still take a picture. If I turn the flash to ON, it works without any issue. I'm on the stable release of CM 10
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Meshelton said:
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Click to expand...
Click to collapse
If you were happy with everything working WHY in the world did you upgrade to a Nightly? Nightly by definition is only for people who know what they're doing and are not afraid of the Night.
Anyway, there are like 6.0221413e+23 changes from cm 10.0.0 to 10.1 RC2. What can I say you did a dirty flash (upgrade!), and probably didn't back up.
So the first thing you should do is back up. NOW (go to CMW recovery and back up)
Download a better behaving nightly like the one JD1639 uploaded. get it from http://forum.xda-developers.com/showthread.php?t=2272261
Download the UCMC1 radio (assuming you're on at&t)
Download the gapps 20130301
Put them all on in one folder for easy access
goto the CWM recovery and get to work:
1-backup
2-cleanup: go to mounts and format data, cache, system (don't format the sdcard!!!) and don't reboot until everything is finished
3-clean dalvik cache from advanced
4-install in this order: RADIO file.zip (UCMC1)
5-CM ROM
6-gapps
7-go to Advanced Restore option, find you back up and restore the "DATA" portion ONLY
This should save you ... good luck,
Commodore 64
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Meshelton said:
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Click to expand...
Click to collapse
You know I don't think it is a hardware issue since it started after one of your updates. If you were on a ROM for while, and one morning you wokeup and the sound didn't work ... maybe. But i'm not convinced since also I remember around Feb-March there were some complains on sound not working after flashing to 4.2.2 version of the cm. Try flashing back to the stock UCMC1 ROM (absolute stock flashed with Odin not CMW) and then do a factory reset.