• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][FINAL] CM7 7.2 RC1 - g60 style [7.11.12]

What is weird is why a hardware error might only show in cm7. My problem is I like cm7 (especially till we get ics cameras) so I am going to give this another try. Reflashing with minimal apps for a bit to see what happens.
 
I just wiped both caches. First boot, android.phone fc'd and apps took about 20-30 seconds to load. Its just a pain setting everything back up again cause I have loads of apps.
 
I did a factory reset this time, full wipes every other time. Reformatted the sd card, all of that. I'm of the opinion that it's a hardware issue because it's just constant. Miui did it, but I will say that cm7 does it more often. It's one of the main reasons I'm switching phones when the new one drops. Other than that, this rom is butter smooth, so it sucks that I can't solve this.
 
So far so good. Got it up and running again. Adding apps very gradually. Have rebooted myself a couple of times and no issues. But when I reboot the lockscreen does not come up. Should that be the case? I do get a lockscreen I lock the phone but not on a reboot. Just haven't seen that before.
 
wigginst said:
So far so good. Got it up and running again. Adding apps very gradually. Have rebooted myself a couple of times and no issues. But when I reboot the lockscreen does not come up. Should that be the case? I do get a lockscreen I lock the phone but not on a reboot. Just haven't seen that before.
Click to expand...

The lock screen should come up unless it's disabled. Check
Settings--> Location & Security--> Set up screen lock
Pick one, see of the problem goes away.
 
dsmryder said:
Hey, do you want to add this to your FAQ? It gives a good explanation of the file system used on Android phones. That way people can have a deeper understanding on what they are doing when the clear cache, data, or format system.
Click to expand...
I might as well. If people understand more properly what part of android holds what, they won't wind up bricking their phone so often. Remember people, do not format anything besides what you are told to format! I am going to add more sections to the FAQ on how to upgrade and how to do a fresh wipe. I must have forgotten some obvious stuff.:confused:
 
Made a nandroid of it since it has been working ok so far. At least that way I may not have to go all the way back to the start if it goes awry. I am digging this rom as I can set it basically as I had cm9 but with a working camera etc.
 
So far still working well! This rom and the new b kernel seem to being working well now. Made another backup for myself just in case but do far I am liking this setup!
 
wigginst said:
So far still working well! This rom and the new b kernel seem to being working well now. Made another backup for myself just in case but do far I am liking this setup!
Click to expand...

Didn't B advise against using his bKernel for currently dev'd CM7 ROMS because it's outdated and that he's working on a new one for CM7?
 
Yeah you can use the Whyzor Kernel which is default, Mantera's TheOC, or B_randon's bkernel. However b_randon did state the following

b_randon14 said:
CM7 version has not been updated. It is way behind the current CM7 kernels, and I'm not sure it will even boot the current build of CM7. I've got to put alot of work into the CM7 kernel in order to get it updated. Thanks for understanding!
Click to expand...
 
He just updated it the other day...05/04 I believe. I know it still says it's outdated but then if you scroll down a little farther to the bold changes it shows that it's been updated.

That's what I'm running with g60 and it's working great!
 
G60, bravo dude!

I have to say, you've fixed a few problems I've had with CM7 for a while now and are updating this SOB like crazy haha.

If you can get video flickers off of regular portrait and enable deep sleep with wifi (I think that's impossible, something about it being required in custom ROMs, oh well) this would kick ass. Regardless, it's amazing and you're awesome :)

I do still prefer the good ol' default launcher over the almost iPhone-like 360 launcher (And it's in chinese, but I play a lot of japanese games so I'm used to interacting with stuff I don't understand), but that's probably because I had owned an iTouch prior to getting my Triumph and it feels old to me, so Android is sleek and fresh in my mind right now :D

EDIT: Thought I'd mention that this also has the best battery life I've had on my Triumph to date. I know CM7 isn't just yours, but you've been working your ass off on it and it is under your control now.

Anyways, if I'm not using wifi (Even w/ 3G enabled) I can get days and days (Literally) of idle and it'll still hold a charge (About 5% over 12 hrs idle), and if it's not sleeping and I'm doing stuff (Mainly GBA emulators, Gameloft games, etc...) I can get 9-12 hrs off my battery and it'll still have a little left for me to save.

This is without JD, some people say JD ruins CM7's battery life and I'm currently testing that.

Thanks dude!
 
Hey g60, when I build, should it still show r 0.4? I did a make clean and am trying to build again. I just wanted to know what to expect when it's done. And post in case anybody else wanted to know.
 
dsmryder said:
Hey g60, when I build, should it still show r 0.4? I did a make clean and am trying to build again. I just wanted to know what to expect when it's done. And post in case anybody else wanted to know.
Click to expand...

At this point it should show r0.5. Before you build run the

# repo sync

This pulls down all the changes I have made and then updates your local repository on your computer so you can build. If you have more questions let me know. :cool:
 
You might want to add the front camcorder force close problem to the known issues on the first post if it can't / won't be fixed.
 
Gaffadin said:
You might want to add the front camcorder force close problem to the known issues on the first post if it can't / won't be fixed.
Click to expand...

I already added it on 5/6/2012. It will be fixed, it looks like it was an update from Cynogen that broke it. I am looking into the code to see what happened, as the camera was working fine in Whyzor's final build. It's one of the March imports that caused the problem I just need to pinpoint which one.
 
You must log in or register to reply here.
Back
Top Bottom