• 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]

That is what I thought, and that is exactly what I did. I even tried the "Back to Stock" route.
I am aware of the longer-than-normal first startup, but after it has been on the g60 logo for 20 minutes to an hour, I think that it isn't going to continue.

Pull the battery and wait 20 seconds. Plug back battery and boot back into CMW

wipe data/factory reset
wipe cache
wipe dalvik cache
reboot into CWM

install 60style r0.10
install gapps
install gapps talk (if u use it)
reboot

If it takes a long time to boot again. I would recommend downloading the ROM again to make sure you don't have a corrupt .zip.
 
That is what I thought, and that is exactly what I did. I even tried the "Back to Stock" route.
I am aware of the longer-than-normal first startup, but after it has been on the g60 logo for 20 minutes to an hour, I think that it isn't going to continue.

So other roms install ok?
 
So can you get rid of that Google toolbar I see on all of the cm7 screen shots? I don't really like that and I prefer to have a clock there...
 
So can you get rid of that Google toolbar I see on all of the cm7 screen shots? I don't really like that and I prefer to have a clock there...

Yeah the toolbar comes with the cynocream theme that's listed above the screenshots. You can put what you want there.
 
I have found an issue. Admittedly, I'm still on r0.07, but I haven't seen this mentioned...

My custom settings for auto backlight won't stick.

To replicate,
I went to my cm7 backlight settings, picked the one it was currently on and changed it.
Hit the save button and nothing changed.

exited all the way out, and when I went back, all the settings were on default.

Replicated several times, regardless of settings.

anybody else?
 
For some reason I think the volume bug has resurfaced for me. I'm on R0.10 but I will do a clean wipe tomorrow to see if it fixes it. Otherwise, I may have to go through my long list of apps to see what's causing it. :(


Also, the game Bloons TD 4 causes an automatic reboot when you click play. Is this an issue with the Rom or the app which the dev for that would have to fix?

Otherwise thanks for your Amazing work you've done.
 
I have found an issue. Admittedly, I'm still on r0.07, but I haven't seen this mentioned...

My custom settings for auto backlight won't stick.

To replicate,
I went to my cm7 backlight settings, picked the one it was currently on and changed it.
Hit the save button and nothing changed.

exited all the way out, and when I went back, all the settings were on default.

Replicated several times, regardless of settings.

anybody else?

I had this too. My fix was to remove the last entry (above 855) and the settings would stick.
If anyone wants to know, the lowest soft button light setting is 4, and changes with a multiple of 4. eg 4 8 12 16...
 
thanks Ryder.
That needs to be in the bug list.

I thought I was the only one. I guess we're the only tweekers.:afraid:
I had the same issue with TG;s 0.8, so I didn't care. The problem reintroduced itself when Whyzor updated the list a while back. And sense I just keept flashing over the old loads, I didn't see it untill I applied the changes. I don't know if it's inhearant to the ROM from the begining or not.
 
I thought I was the only one. I guess we're the only tweekers.:afraid:
I had the same issue with TG;s 0.8, so I didn't care. The problem reintroduced itself when Whyzor updated the list a while back. And sense I just keept flashing over the old loads, I didn't see it untill I applied the changes. I don't know if it's inhearant to the ROM from the begining or not.

I've always been rather anal with my backlight settings.
Then when aricblunc posted his custom settings I really liked the way it worked... I just tweaked mine dimmer. Whyzor instituted those into the ROM, and I haven't really messed with them since.
I really don't know when that first setting (0 , -1) came into being, but it's useless anyway.
 
Hi g60madman, first, thank you for taking an already great ROM and improving it! I noticed that sysctl is being fired off at boot, but the sysctl.conf file is empty. I have found threads in other forums for other phones running GB ROMs that have some rather interesting kernel parameter tweaks.

Code:
# try to keep at least 4MB in memory
vm.min_free_kbytes = 4096

# favor block cache
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55

# extremely favor file cache
vm.vfs_cache_pressure = 20

# reboot when OOM happens
vm.panic_on_oom = 2

# wait 5 sec before rebooting when OOM
kernel.panic = 5


# currently experimenting
kernel.shmmax = 268435456
kernel.shmall = 16777216

I've tried these on your ROM and it does initially improve performance. Over several hours the cache obviously fills and it slows things down. My thought was to set up a cron job to dump the cache periodically. Do you see anything in the above parameters which could be redundant to what you have already done?

Thanks!!!!!
 
So other roms install ok?

the other roms installed just fine.

I should probably say that I was downloading the Roms on the phone itself and moving them to the top level of the sd card. For some reason the phone will no longer connect to the computer. PC says that the device has malfunctioned (Multiple computers and USB cables), so I finally downloaded the ROM on my PC and used a card reader to put it on the SD card and the fresh install worked fine. I don't know what I was doing wrong.

Is anyone else having trouble with the USB Connection? I have tried it with and without Debugging turned on, as well as going into the root download mode (Turn on with the volume down button pressed)... nothing will connect on any computer I have tried.
 
the other roms installed just fine.

I should probably say that I was downloading the Roms on the phone itself and moving them to the top level of the sd card. For some reason the phone will no longer connect to the computer. PC says that the device has malfunctioned (Multiple computers and USB cables), so I finally downloaded the ROM on my PC and used a card reader to put it on the SD card and the fresh install worked fine. I don't know what I was doing wrong.

Is anyone else having trouble with the USB Connection? I have tried it with and without Debugging turned on, as well as going into the root download mode (Turn on with the volume down button pressed)... nothing will connect on any computer I have tried.

Edit: Might help if I read the full post :P Anyways if this also happens on the stock image I would contact VM and get a replacement :)
 
Hi g60madman, first, thank you for taking an already great ROM and improving it! I noticed that sysctl is being fired off at boot, but the sysctl.conf file is empty. I have found threads in other forums for other phones running GB ROMs that have some rather interesting kernel parameter tweaks.

Code:
# try to keep at least 4MB in memory
vm.min_free_kbytes = 4096

# favor block cache
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55

# extremely favor file cache
vm.vfs_cache_pressure = 20

# reboot when OOM happens
vm.panic_on_oom = 2

# wait 5 sec before rebooting when OOM
kernel.panic = 5


# currently experimenting
kernel.shmmax = 268435456
kernel.shmall = 16777216
I've tried these on your ROM and it does initially improve performance. Over several hours the cache obviously fills and it slows things down. My thought was to set up a cron job to dump the cache periodically. Do you see anything in the above parameters which could be redundant to what you have already done?

Thanks!!!!!

makosinski,

I will do some research on this and see if it's something to add to the phone. I need to look into it more to see if it does in fact have a positive help to the phone. Right now my focus is rewriting the device files for our phone. It's taking a lot of time as I have been really busy lately.
 
makosinski,

I will do some research on this and see if it's something to add to the phone. I need to look into it more to see if it does in fact have a positive help to the phone. Right now my focus is rewriting the device files for our phone. It's taking a lot of time as I have been really busy lately.

Is there a simple way you could post your ideas and maybe someone like me can help? I have a limited amount of time also, but I get a bunch of research done during lunch:D. I do have bu github so I can isolate any changes that I make so they don't interfier with your tests.
 
Is there a simple way you could post your ideas and maybe someone like me can help? I have a limited amount of time also, but I get a bunch of research done during lunch:D. I do have bu github so I can isolate any changes that I make so they don't interfier with your tests.

Rock it brother :D I am all for the community pitching in to lend a hand! Just like your camera fix it was a simple add in to fix. Funny thing is on the AOSP from google it has the same problem LOL. I was looking at the code just to see how they do it and their code is still the red snap.
 
Rock it brother :D I am all for the community pitching in to lend a hand! Just like your camera fix it was a simple add in to fix. Funny thing is on the AOSP from google it has the same problem LOL. I was looking at the code just to see how they do it and their code is still the red snap.

As for the camera, I think it needs a small delay to allow the camera autofocus driver time to reach "full focus" I think it gets close, but not all of the way there or the driver we have makes a bad report of it's state. If we had the source code for our drivers we could look and see what the call does. (I hope I have my terminology correct) I knew it would work, that's why I put it under the "dumb" column.

I guess, what's next? I don't have alot of programming skills, but I can read and I try to follow. Also, I can run test trials of stuff that I build with your code.

Edit: I just booted on a kernel I built with yours, and mantera's help. I didn't make any changes to the code, just built and saw if it would boot :-)
 
As for the camera, I think it needs a small delay to allow the camera autofocus driver time to reach "full focus" I think it gets close, but not all of the way there or the driver we have makes a bad report of it's state. If we had the source code for our drivers we could look and see what the call does. (I hope I have my terminology correct) I knew it would work, that's why I put it under the "dumb" column.

I guess, what's next? I don't have alot of programming skills, but I can read and I try to follow. Also, I can run test trials of stuff that I build with your code.

Edit: I just booted on a kernel I built with yours, and mantera's help. I didn't make any changes to the code, just built and saw if it would boot :-)

Check you out!! You know that is how I started trial and error. When we started the big kick for CM9 I just downloaded the code and started messing with it, trying this and that to see if it would make a difference. I am by no means a master of all this, just read, learned, applied, failed, and learned more :D It was exciting when Whyzor turned over the keys. I keep trying this and that, and what do you know? I actually have a decent ROM :rolleyes:. It helps to know a little bit of programming however I am by no means a pro. HTML, CSS, and XHTML is where I started. I then dabbled in Java Script, PHP, PERL, & XML. My big learning was with Objective C last year as I wanted to program on the iDevices.

The app I was working on was a Chess Notation solution which I planned to use in tournament play and sell. However the United States Chess Federation banned any iDevice or Android device so that stopped me dead in my tracks. So I stopped learning programming and sold all my Apple products. After that I moved to a new job which didn't supply a company cell phone. I bought the Triumph and the rest is history. So for what it's worth keep doing what your doing!

Listening to music and an email came through, looks like the volume bug maybe back. Going to have to look into the merged code I pulled into build r0.10 and see what happened...like I said trial and error :D LMAO!
 
makosinski,

I will do some research on this and see if it's something to add to the phone. I need to look into it more to see if it does in fact have a positive help to the phone. Right now my focus is rewriting the device files for our phone. It's taking a lot of time as I have been really busy lately.

Spend your time on the camera code for ICS!

Thanks
 
Spend your time on the camera code for ICS!

Thanks

LOL yeah regardless if the camera gets fixed our not I will still be rocking the CM7 development. Even though I love the
adore.gif
CM9 ROM that mantera has built, I am still going to stay true to the CM7!
 
I've recently been surprised at how much some people are diein for a cm9 camera lol

I mean it would be nice to have working but I guess I just don't get it lol

I have my cm7 g60 completely ics'ed out, well except for the font cause I just don't feel like changing it lol


But latley. The ics camera has been all most ppl wanna know

Besides the fact that it'll take awhile to be up and running, I'm curious to if they think once it is up and running that it'll work smooth

Cause from what I've been reading on how ice apparently changed it all up doesn't that mean once it actually works it'll still be bugged with focus issues and terrible resolution just like the cm7 ones had for awhile?

Or has someone already got that stuff down, and getting it to work is the only issue

Didn't mean to sidetrack, just my curiousity
Also not directing this to anyone or trying to start arguments, again just curiousity lol
 
My guess is it will still have problems. How much who knows? All we can do is wait and see. Since CM9 is more actively developed on than CM7 it's possible it might go away? However until the camera actually works it's all speculation at this point LMAO!! It's like guessing lottery numbers some one has a chance to guess right :D:D:D
 
I like that you've gotten rid of most of the bloat ...saves me time from doing it myself haha

:thumbup:



Ill +1 for this, altho i still remove other things like live wallpapers, magicsmoke wallpapers, visualization wallpapers and such, everything that has been removed saves me atleast 30 minutes anytime i do a fresh install

and normally with whats been done and what i do the rom only takes up about 85-91mb of internal memory
 
Back
Top Bottom