[ROM][May08][GRJ22] -=MDJ's CyanogenMod 7.1 v.1.2=- [Android 2.3.4][OC 1.9GHz]
Hi there, I'm not sure if this is the right place to put this thread or in the device specific one and I can't post in the dev forum for this Rom either..
This is the 4th rom I've used and really want to stay on this rom, however after I've flashed it, it sometimes freezes and I will have to take the battery out and turn it back on. I've had this rom for a day now and the phone has frozen about 4-6 times.
I also flashed the recommended radio for it too.
12.48.60.23U_26.08.04.07_M3
I haven't had any other problems with previous roms.
Any ideas?
I Know this should be in the Developer section, but I don't have enough posts. (Since you have to have at least 10 to do so...)
BUT, I installed a kernel from Blades which is the 1.6ghz with the latest version of CWM. The problem is that whenever I try to boot up the device it just stays on the first startup screen, and it also makes a weird popping noise from the speakers about every 10 seconds. I did wipe Dalvik Cache and I also made a back up before installing the new kernel. I've tried restoring but it does the same thing every time. Before installing the kernel I was running PRIMEORDIAL! v3.1...
Any help would be greatly appreciated....
Thanks
cdp
Hi Mate, You are not the only one. Unfortuantely 3.0.1 kernels don't work too well with 3.1 roms as you have discovered.
Not to worry though as this is an easy fix.
Simply flash the 3.1 stock kernel and you're up and running again. You can get it from here... http://forum.xda-developers.com/showpost.php?p=14283676&postcount=94
Wow, I didn't even realize that kernel was only for 3.0.1 lol. THANK YOU! Flashed it and it started right up! C:
You may now have wifi problems, since the kernel update will have installed a different module to the one you need, if this is the case just reflash whatever rom you are using.
Okay cool, I'm on wifi now and it seems to be working fine. So thanks again! :]
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
76redrum said:
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
Click to expand...
Click to collapse
Hi,
What version did you install?
3.6.8 or 4.1.8?
Did you do a MD5 checksum?
Did you super wipe?
Did you add any mods?
If you want help,you need to post more information...
Hi i had the same sort of problem with my ARHD but I find out that the faux kernel was causing for difficulties.
Installed a stock kernel and all problems solved.
Still respect all developers
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
76redrum said:
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
Click to expand...
Click to collapse
Hi,
It does sound like a kernel problem.
Try the kernel in my signature.
Absolutely no problems there.
ill try the stock kernel thanks to all
phone:htc senation
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any digestions would be very appreciated
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any sugestions would be very appreciated
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
seatown1two said:
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
Click to expand...
Click to collapse
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
---------- Post added at 03:15 PM ---------- Previous post was at 02:25 PM ----------
Hawke84 said:
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
Click to expand...
Click to collapse
Hi, i've been running the 3.6.x Roms for a while now and think they're great, but was getting interested in the sense 3.5 stuff. What in particular do you like about the 4.1.x roms? Just seeing if it's worth the full wipe effort .
Thanks
Mike
ArcticWolf91 said:
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Click to expand...
Click to collapse
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Hawke84 said:
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Click to expand...
Click to collapse
Lol yes, you are not the first to tell me that, and believe me lesson learned. Though I did mention that it was rooted and that it would be running this Rom. But yes now I am troubleshooting the phone with this person and I may have to give them a refund because they opened a case with eBay.
mrew42 said:
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
Click to expand...
Click to collapse
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
seatown1two said:
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
Click to expand...
Click to collapse
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
mrew42 said:
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
Click to expand...
Click to collapse
how do you up the speed for idle..silly question i know
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.
so i was running team eos 1.0 since the day of release and just decided to swap it over today.....
i looked through that post to try to find my answer then google searched it when i couldnt find it on xda so im going to make the post in the general since xda wouldnt let me start a post in dev untill i posted 10 comments elsewhere.
my problem is as the title says i have no data after installing it i never had this issue from 1.0 eos rom and i didnt have any problems from the install or anything. and i saw in that thread that some users only had to restart a couple of times to get data working but that didnt work for me so im seeing if anyone else has had this problem and how they fixed it im thinking of just downloading a nightly real quick to see if it works on that install
Update info
so i have tried some other things.
1) loading the newest nightly
2) loading an old nightly version 18 before 1.0 released
3) my xoom is now stock and relocked with honey comb
no luck with any of these
also called verizon no help there they made sure the numbers were matching on the switch and such but everything looked good on their end i supose
fixed
Got it fixed turns out some ota stuff must have effected how the data works in the EOS 2.0 and older original stock img.
If you want to know specifics on what fixed it pm me. When I think it OK to give more info I will edit this post