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

lnhs2007 said:
I'm actually quite unfamiliar with this thing called undervolting. I thought I was pretty experienced in the a android world, from a user standpoint, but ever since joining this forum I've seen a lot of talk of undervolting, which I've never heard of. I'm fairly familiar with changing CPU frequenicies, under/overclocking... could somebody please explain to me what undervolting is, how do I do it, and what's the benefit of it? Much appreciated!
Click to expand...


Undervolting is basically where you tell your phone to use a lower voltage from your battery for different CPU clock speeds. In theory it is supposed to make your battery last longer because you're not pulling as much voltage from it. However, you have to have a ROM and/or Kernel that supports undervolting and an app that will allow you to change the voltage values for each CPU frequency.
 
... And that app would be:
I feel like most people here use setcpu. I use System Tuner Pro, personally.

I always drop all frequencies by 50mv (two clicks) and drop my lowest freq (61 mhz) to 800mv, since that's where my device spends the most time. I haven't spent allot of time trying to tweak each frequency voltage to the absolute lowest stable setting and these settings have never rebooted on me, and it's quick to apply every time.

You'll know if you went too low because you'll see your device spontaneously reboot.

All devices are different and your mileage may vary.

edit,
my clockspeed is set to 61 mhz-1.5ghz.
The less you over clock, the more you can under volt. Said another way, you can go lower voltage in the lower clockspeeds than you can in the upper speeds.

edit again,
add no frills CPU control to the app list, I know there's more...
 
thangfish said:
... And that app would be:
I feel like most people here use setcpu. I use System Tuner Pro, personally.

I always drop all frequencies by 50mv (two clicks) and drop my lowest freq (61 mhz) to 800mv, since that's where my device spends the most time. I haven't spent allot of time trying to tweak each frequency voltage to the absolute lowest stable setting and these settings have never rebooted on me, and it's quick to apply every time.

You'll know if you went too low because you'll see your device spontaneously reboot.

All devices are different and your mileage may vary.

edit,
my clockspeed is set to 61 mhz-1.5ghz.
The less you over clock, the more you can under volt. Said another way, you can go lower voltage in the lower clockspeeds than you can in the upper speeds.
Click to expand...

IncrediControl is another undervolting app that I have used. I don't bother with undervolting anymore though because I didn't see any significant benefit. Make sure, however, that with any undervolting app that you uncheck the "Apply on boot" box while you're testing different voltages.
This is because if you set one too low or too high your phone will usually freeze and re-boot. As long as you have that box unchecked, when the phone re-boots it will be reset to the default voltage settings. Otherwise it will re-boot with the settings you programed and freeze/re-boot again & again & again.

If you get stuck in that situation you have to factory reset your phone and re-flash the ROM.
 
thangfish said:
... or flash a default voltage table in CWM.

Tag team with grey .:D
Click to expand...

Yeah, that too. Hey thang, do you have a source for voltage tables for our phone? I asked several months ago when things were just getting started for this phone but nobody had anything then.

Oh... Tag, you're it. :-P
 
samhande said:
Bysdz, did you use the default settings for the Light Sensor Filter and Screen Dim Level or did you set your own custom levels. I too have issues using the screen in bright light. Typically it will respond if I wait but often the lock screen will take over before the sensors react. BTW these controls are located at Settings>CM Settings>Display>Automatic Backlight>Enabled and Screen Dim Level.
Click to expand...
I didn't mess with any of the settings, til I read your post, I just checked the boxes. But after thinking about it, I just changed the sample interval to 0.5 seconds instead of 1 second. I have no custom settings enabled. It kinda makes sense cause sometimes it would take about a second. So, the difference in time for it to change was probably because of when in the interval the phone woke up, but that is pure speculation.
 
Going back to the problem that I have with video freezing...
I installed CM9 and have the same problems. Looks like it something in the code or drivers that CM7 and CM9 share.
 
G60 what are the major fixes/changes you are working on for the next release? Like what doesn't work that you are trying to fix?

MikeRL where is this faq you speak of?
 
corance said:
thanks! Other than hdmi are there any major fixes in the next one cause I'm not too worried about hdmi.
Click to expand...
Cannot make any guarantees, but mainly stuff that mysteriously broke when syncing with mainline CM7. This includes the camera (yes, the stupid thing broke again! What wonderful luck we seem to have!
banghead.gif
Good news is that's definitely not going to be an issue on the next release. g60 is dedicated to not having it break. Also on the todo list is the automatic brightness bug, and then the video flicker bug. At least, from what I know, we can safely assume that no builds are coming out with a broken camera anytime soon! The auto brightness bug and video flicker bug may or may not be fixed in the next release, but at least I can confirm that they are targets for the next release. Seeing as g60madman will be extremely busy with his job for two weeks, we may not see a release for a little while. Please bear with us while he commits to the code and his life (ha ha code puns!) and tests, and I test and look for bugs, as well as drastically expand the documentation. I will have plenty of free time soon, seeing as I'm graduating. This gives me the time I need to make the next release perfected with documentation and not simply idiot-proof, but also have documentation that helps the experienced user and newbie alike. What I am likely to do is create a list of ways that the phone could be bricked, and how to avoid these issues. Although I cannot prevent a hardware defect/malfunction, I can prevent PEBKAC errors! Although everyone has to go through a n00b phase (myself included), I am going to do my best to make the information in the next FAQ as well-organized, detailed, and easy-to-follow as possible. I have no clue of an ETA, and DO NOT EXPECT ONE, OR EVEN BELIEVE WITH 100% CERTAINTY WHAT I'M ABOUT TO SAY! If I had to guess, however, the next release, at the earliest, will come after June 8th.
 
Don't consider this a bug as I have flashed over my old builds multiple times but...

Today my unlock button on the top right side of the phone was not functioning correctly. It acted like I was long pressing it, when in reality, I just tapped it. I would have to press it multiple times for it to lock the screen etc. However, I did a battery pull and boom, no more problems. Could this be a sign of hardware problems or is it just a misc. problem due to flashing over old builds? I have r0.9 now.

Loving this rom with Zeam launcher BTW! Sure hope my unlock button isn't wearing out... This rom is the only thing keeping me from switching to Evo 4! Keep up the excellent work, thanks!
 
Thanks MikeL that's all I wanted to know. No rush. I think quality is better than quantity. if it takes twice as long for the next one to come out but it's three times as good...I'm cool with that. It will be my first one so the fewer bugs the better.
 
Just Infectiou said:
Don't consider this a bug as I have flashed over my old builds multiple times but...

Today my unlock button on the top right side of the phone was not functioning correctly. It acted like I was long pressing it, when in reality, I just tapped it. I would have to press it multiple times for it to lock the screen etc. However, I did a battery pull and boom, no more problems. Could this be a sign of hardware problems or is it just a misc. problem due to flashing over old builds? I have r0.9 now.

Loving this rom with Zeam launcher BTW! Sure hope my unlock button isn't wearing out... This rom is the only thing keeping me from switching to Evo 4! Keep up the excellent work, thanks!
Click to expand...

I've noticed that if I wash my hands the screen would be compleately unresponsive. I've had some shmoots on my hand and the phone would act like I was multi touching it.
The issue could be your hands had some stuff on them faking the press.
 
My phone is rather prone to having soft controls activate when the phone is in my pocket or purse if I've neglected to hit the Lock button. Odd that sometimes the screen wants to ignore an actual finger but will be triggered by pockets. :)
 
Seanette said:
My phone is rather prone to having soft controls activate when the phone is in my pocket or purse if I've neglected to hit the Lock button. Odd that sometimes the screen wants to ignore an actual finger but will be triggered by pockets. :)
Click to expand...

When the screen comes on there is a 250mS delay before the phone will respond to the touch inputs. And as for me, I have my phone set to delay the lock for 15 seconds so I have my oppsy moments. Also, handcent (my default mms) has a feature to turn on the screen when it receives a text. Other apps may have that feature and would make it prone to those issues.
 
Is anyone having high-end games reboot the phone? Since this last update (r0.9), Temple Run and new levels of Where's The Water? reboot the phone.
 
What commit broke the camera this time. Looking at g60's camera repo he hasn't merged in any upstream changes since his last build. He's made some commits but they wasn't upstream cm7 merges.

Edit: just checked the cm camera repo on the gingerbread commits and the only one that's been made was one to update porteguese translations and he hasn't pulled that one in so I don't think it was an upstream change that broke the camera.
 
PatrickD88 said:
Is anyone having high-end games reboot the phone? Since this last update (r0.9), Temple Run and new levels of Where's The Water? reboot the phone.
Click to expand...

I tried to install "Cross Me" from Amazon (it was the freebie of the day and looked interesting), and it kept rebooting my phone. I thought I'd just gotten a bad download of the game.

Don't know how relevant that is, since I'm still on r0.6. :)
 
PatrickD88 said:
Is anyone having high-end games reboot the phone? Since this last update (r0.9), Temple Run and new levels of Where's The Water? reboot the phone.
Click to expand...
Just came here to post about Temple Run.

My daughter had been badgering me to get it for a while but the Android version was only just released.

The first time I ran it my phone rebooted, and the second time I ran it immediately following the reboot it popped up an error message but once I clicked that off the game ran perfectly.

I just went to run it again and again it rebooted, but once the reboot was finished I was able to run it by clicking the error off and playing as normal.

Googling the error I found this:

xda-developers - View Single Post - [Rom][Pitch Black](TabletUİ)[AOKP-B36][20/05]Resurrection Remix ics v1.9.1[4.0.4]

which shows someone else having the same error and the same issue on the Samsung Galaxy S2.

I suspect it's more an error with the app than anything else, since it's so new.

(Edit) I have emailed the developer. We'll see if anything comes of it.
 
OK, the game situation is getting weird. I just tried Double Talk (which has worked fine on this ROM previously, IIRC) and my phone rebooted while the game was loading, as Cross Me did.
 
You must log in or register to reply here.
Back
Top Bottom