Hello. I've had Khalpowers v4 for a few weeks now and it has been great. I've changed themes a few times with no problems with the last one I used was SilverBlackXT except wallpaper doesn't change with it. still haven't figured that one out. But thats not my problem. I just tried to install his new SteelEpicBlueXT theme and it seemed to cause all sorts of issues. Seems it has done the same to others but no one is getting any kind of answers. After installing it caused my phone not to boot, was stuck at boot animation. So after trying to reinstall a few times and restore v4 a few times I finally had to format and partition my memory card again, and start from scratch. I flashed back the cincinnati bell rom and then flashed dexters v1.3 and then to V4. So after doing all that I have my phone back and decided to try and change my theme again back to the SilverBlackXT. After reboot nothing changed. It did not work. So in short Themes aren't installing anymore and hope someone can figure this out soon. Thank you all for your help this site is great
I was thinking it could possibly be a my SD card as I'm using the one that came with the phone and it is only a class 2 I think. The partitions with swap could be a little too hard on it. So I do plan to get a better card and maybe that will solve some of the issues.
I guess nobody pays any attention to questions and answers forum lol.
Related
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.
First of all i'd like to thank anyone who takes time to answer this because this has been driving me nuts for the past 2 days.
Now that thats out of the way; I have a Droid 2 and i'd consider myself a noob with this phone. I rooted the phone yesterday and had problems with ROM manager flashing cwm 2.5.0.8, so what i did was downloaded cwm3 off the internet and moved it onto my SD, renamed cwm3 to 2.5.0.8 and all of a sudden my recovery system works. Once i got that all taken care of i began messing with ROMs. My brother put the beta version of tanzanite on and bricked my phone, i fixed that. Once i got rid of tanzanite i tried using gingerblur 1.3 and got stuck in a bootloop. Right now im in the process of trying to use gummyjar 2.5. More so to the point, what my main question is, is since i'm using clockworkmod 3 would that restrict my phone from being able to use any semi-older ROM versions such as the ones previously stated?
Again, thanks a bunch to anyone who can answer my retardedly long question
Hi,
I've recently used Unrevoke and rooted my phone. I've tried Cyanogen and Ginger Villain, but had a problem with partitioning my SD card, so I'm in limbo at the moment.
However, the partitioning seems to be sorted out, so I'm ready for a final ROM flash and then I can leave it alone. Fingers crossed.
1. Once I've used Unrevoke, do I need to use it again or is it always rooted now? I suspect it is.
2. In the future, if I change ROMs, is it simply a case of backing up, resetting to factory, flashing the ROM and restoring?
3. I have Cyanogen on at the moment, and I love the ADW launcher as it keeps three apps permanently on whatever screen you're on. However, it doesn't support A2SD+ so I'm looking for a Gingerbread ROM with A2SD and ASDW launcher or similar?
Does anyone have any suggestions?
Many thanks and apologies if this information is obvious, but I wasn't able to find it out there.
Appologies for not replying to the original MIUI thread. I am not a new user and i am very experienced in flashing roms etc, especially on samsung devices. I have been around for a while now but this is my first post so i cannot post in the dev section yet.
Last night i flashed MIUI to my infuse. I followed the instructions in the op here exactly.
http://forum.xda-developers.com/showthread.php?t=1278053
I had no problems flashing and everything was successfull, however there were 2 major issues. First being the soft keys. The four buttons menu, home, back, and search buttons did not function at all. They werent even backlit. The volume rocker and power buttons functioned fine. I reflashed from blue cwm twice and still nothing.
This is where i ran into my second issue. There were no posts about anyone having the soft key issue however i did notice alot of people losing their recover and being stuck on the samsung boot screen. This eventually happened to me.
I went to samfirmware and downloaded 2.1 and odin'd it, then odin'd the community kernel to get ext4 and red cwm then restored my nandroid so i am back to normal. I wanted to post about my soft key issue but as i said i had to post in q&a due to my lack of posts.
Any suggestions? if not, i at least wanted to inform the dev of the issue.
Thanks
have you tired CM7, just asking cuz they have almost the same bugs....so i would curious to see if your softkey issue transfers to that rom as well. and if not........
i would try loading up CM7, wiping from the orange CWM and flashing MiUi from there. it Should have worked the way you did itk if you were coming from stock. but who knows maybe seeing if it happens on Cm7 will lead to your answer.
just an idea though
no i havent been able to try cm7 yet as i dont have a build environment set up anymore and havent seen a release yet, would love to give it a shot if someone wants to send me a zip.
i really hope it doesnt have the same issue or ill have to donate this thing to my fiance and get a gs2 or something lol.
Check your mail, you seem to know what your doing so test it out see what happens.
Happy Flashing
Happy flashing indeed, thanks for this im going to give it a go right now, bbl with results.
Hell the only reason i was flashing miui to begin with is b/c i am currently unable to build cm7 so hope this works..
Thanks a ton!!
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
powdered_donuts said:
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
Click to expand...
Click to collapse
Glad it all worked out.....
My issue has been plaguing me for several weeks now. I just stared developing for Android, so I'm a bit of a noob (forgive any obvious mistakes that I have made, or do make)
I have an HTC EVO 3D that I got about 8 months ago. One of the first things I did after I got it was root the puppy and flash a custom Gingerbread ROM to it. That worked great as a development tool for a while, with no issues, whatsoever.
After some time, I updated my custom Gingerbread ROM to a custom ICS ROM, which again, worked fine, minus the minor inconvenience of it occasionally rebooting when I would hit the debug icon on my IDE (Eclipse). That would only happen every once and a while. However, one day last week, all it did, when I hit debug, was reboot. I figured that the ROM was bad in some way, and flashed a custom JellyBean ROM to it. Same issue. I flashed another JB ROM(CM 10), with the same issue. After that, I've done everything that I can think of to fix this issue. I've tried flashing everything that Clockwork would let me flash (Dalvik, cache, did a factory reset, etc) I tried reformatting the SD card, and even tried 3 new ones. I tried reflashing the ROM, I tried 3 other computers, and even re installed Windows on one of them! In my experimentation, I have discovered that it also reboots when I try to record video with the native JB camera (I say that because I installed another camera app from the Play Store, and that works fine).
I'm thinking maybe a memory leak? I honestly have no idea.
HTC EVO 3D
HBOOT 1.40
S-OFF
Thanks in advance
Next step is to use the Eclipse debugger and read the debug output once it crashes/reboots. The output from the debugger will provide more information about what happened so you can start narrowing the problem down more.
It's a memory or cpu problem (i guess) . Try the cpu a bit lower. I hope it will help you
If you have flashed your phone allot, and you have under clocked your CPU first, it may be a NAND issue. It has been a problem on my end with the HTC HD2 after like 1000+ flashes. You should be able to use a tool to check for bad NAND blocks, don't remember off the top of my head what it was called when I used it but that's something you could do. That is all (if) you have not tried to under-clock your CPU first and make sure the ROM is not bugging out like it sounds like it is.
Another way to test your NAND is to try a SD ROM that runs on your MicroSD card.