[ROM] RoyalGinger 3.0 - ckisgen - 8/3/11 - 2.3.4, Netflix, gTalk Video over 3G/4G
- Thread starter ckisgen
- Start date
setCPU QUESTIONS (AND ANSWERS!)
ok I just finished up discussing this with Faux-daddy. here's what's up:
Faux recommends not using CM settings OR setCPU .. if you do not check 'set on boot' or touch/change (don't even look, lol) any of the clock speeds in the CM settings performance menu AND you don't even install setCPU then Faux's kernel will default to his smart ass gov he built and his default 1.1gHz max 245hz min settings. He believes this is what is currently the best setup and overall balance of performance and batter life.
Now, MY personal experience is this: I've been using setCPU for a LONG time. I use these same 'default' settings that Faux's kernel defaults to if you don't change it (smart ass gov, 1.1gHz max 245hz min) and I get PHENOMENAL battery life and speed/performance. I almost never / never have kernel related issues like some people report ... for example - I posted this a few days ago using RoyalGinger v1.2 with Fauxs 2.0.6 kernel:
(pictures attached below)
My battery was still at 100% after almost 6 hours off the charger .. granted it was obviously minimal use but I had 25 mins active display on time, I remember I had sent/received a handful of texts and emails. no phone calls at that point. wifi and sync/background data were on the whole time. brightness - auto. (no gps, bluetooth, or 4g)
a few hours later - I ran some bench tests and got a 63.703 linpack score.
(for that score, i had obviously maxed out the clock speeds temporarily in order to bench but for the battery performance purposes from earlier that day and every day use, i use 1.1ghz / 245 min)
Also, right now - my battery is at 74% .. it's been off the charger for 9 1/2 hours. I've sent/received dozens of texts and emails. I've surfed the XDA app a good amount. I've also been testing the crap out of it (trying out various functions, programs, etc) AND have even made a nandroid in recovery, and flashed THREE to FOUR different revisions of Ginger 1.3 (which entails booting back up, rebooting, and the market reinstalling all the market apps, titanium to restore data, etc etc) Now battery stats the day of new flashes, etc. aren't usually what you want to hang your hat on but I test, watch, analyze, and report this stuff virtually most of the day most days of the week and this is TYPICAL performance for me ... i NEVER don't see 16-24+ hours out of a full charge even with the heaviest use I can throw at it ...
so, HERE'S THE BOTTOM LINE (for now) ON THIS:
with THIS ROM, either:
A) don't install setCPU or use/alter ANY of the settings within CM settings / performance menu and run it with faux's 'stock' settings
OR
B) do what was stated in the OP regarding setCPU with the HIGHLY recommended settings of: smartass governor , 1.1gHz - 1.2gHz max, 245hz min (enable set on boot, no profiles)
these are the ONLY two methods that have been tested and tried by our team and the people that built this ROM and the kernel that goes with it. and both work VERY well. you guys can battle it out / decide for yourselves which one of those works better FOR YOU.
THE MAIN THING I WAS TRYING TO PREVENT IN THE OP AND WHAT YOU REALLY DON'T WANT TO DO IS BE USING setCPU AND ALSO HAVE THE CM SETTINGS PERFORMANCE TUNER WORKING AT THE SAME TIME COMPETING AGAINST EACH OTHER. I'VE SEEN THIS CAUSE LOTS OF ISSUES MANY TIMES. (you can prevent this by using either option A (new option/personal preference by Faux) or B (what was in the OP instructions and what i've been using for ages and gotten very good results with)
side note - if you ARE going/want to overclock beyond 1.1 - 1.2gHz for either benchmarking or any other personal or religious reasons - i HIGHLY recommend using setCPU for this. again, just a recommendation based on experience and what i KNOW works ... i'm not even saying the other alternatives at this point DON'T work .. i'm just not going to recommend anything unless i KNOW from experience that it DOES work and keep this ROM stable and performing like it should.
ANOTHER side note, since i think it was asked a few posts above ... the built in smart ass governor (whether you use option A or B as I described above) - automatically underclocks your processor down to 245hz when your screen is OFF and also adjusts while your screen is on to use the least amount of power possible and still get the job done. So, you SHOULDN'T need ANY profiles in setCPU if you've got it on smartass gov.
AS ALWAYS - feel free to take my/our advice or not. just please don't come onto this thread and say you have random reboots or wifi that doesn't work or gps that won't lock, weird video performance, etc. and expect us to be able to do anything about it if you're going to choose NOT to follow our recommendations on what works for this stuff.
((as with many of these things - what works best for one person's phone/chip/usage/underwear size/sock color may not be what works best for someone else's ... so if you wanna experiment beyond our 'recommendations' - then make a BACKUP/nandroid with it setup how we told you to - then screw away with your hearts content (NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE BECAUSE OF ANY OF THIS! as usual) to whatever level you're comfortable with and if you don't like how it turns out - there's a very good chance, unless you did something INSANELY dumb that you will be able to just restore back to where you were and go on about your merry way))
<<we'll likely adjust the OP slightly to reflect the option of setCPU or no tuner>>
ok I just finished up discussing this with Faux-daddy. here's what's up:
Faux recommends not using CM settings OR setCPU .. if you do not check 'set on boot' or touch/change (don't even look, lol) any of the clock speeds in the CM settings performance menu AND you don't even install setCPU then Faux's kernel will default to his smart ass gov he built and his default 1.1gHz max 245hz min settings. He believes this is what is currently the best setup and overall balance of performance and batter life.
Now, MY personal experience is this: I've been using setCPU for a LONG time. I use these same 'default' settings that Faux's kernel defaults to if you don't change it (smart ass gov, 1.1gHz max 245hz min) and I get PHENOMENAL battery life and speed/performance. I almost never / never have kernel related issues like some people report ... for example - I posted this a few days ago using RoyalGinger v1.2 with Fauxs 2.0.6 kernel:
(pictures attached below)
My battery was still at 100% after almost 6 hours off the charger .. granted it was obviously minimal use but I had 25 mins active display on time, I remember I had sent/received a handful of texts and emails. no phone calls at that point. wifi and sync/background data were on the whole time. brightness - auto. (no gps, bluetooth, or 4g)
a few hours later - I ran some bench tests and got a 63.703 linpack score.
(for that score, i had obviously maxed out the clock speeds temporarily in order to bench but for the battery performance purposes from earlier that day and every day use, i use 1.1ghz / 245 min)
Also, right now - my battery is at 74% .. it's been off the charger for 9 1/2 hours. I've sent/received dozens of texts and emails. I've surfed the XDA app a good amount. I've also been testing the crap out of it (trying out various functions, programs, etc) AND have even made a nandroid in recovery, and flashed THREE to FOUR different revisions of Ginger 1.3 (which entails booting back up, rebooting, and the market reinstalling all the market apps, titanium to restore data, etc etc) Now battery stats the day of new flashes, etc. aren't usually what you want to hang your hat on but I test, watch, analyze, and report this stuff virtually most of the day most days of the week and this is TYPICAL performance for me ... i NEVER don't see 16-24+ hours out of a full charge even with the heaviest use I can throw at it ...
so, HERE'S THE BOTTOM LINE (for now) ON THIS:
with THIS ROM, either:
A) don't install setCPU or use/alter ANY of the settings within CM settings / performance menu and run it with faux's 'stock' settings
OR
B) do what was stated in the OP regarding setCPU with the HIGHLY recommended settings of: smartass governor , 1.1gHz - 1.2gHz max, 245hz min (enable set on boot, no profiles)
these are the ONLY two methods that have been tested and tried by our team and the people that built this ROM and the kernel that goes with it. and both work VERY well. you guys can battle it out / decide for yourselves which one of those works better FOR YOU.
THE MAIN THING I WAS TRYING TO PREVENT IN THE OP AND WHAT YOU REALLY DON'T WANT TO DO IS BE USING setCPU AND ALSO HAVE THE CM SETTINGS PERFORMANCE TUNER WORKING AT THE SAME TIME COMPETING AGAINST EACH OTHER. I'VE SEEN THIS CAUSE LOTS OF ISSUES MANY TIMES. (you can prevent this by using either option A (new option/personal preference by Faux) or B (what was in the OP instructions and what i've been using for ages and gotten very good results with)
side note - if you ARE going/want to overclock beyond 1.1 - 1.2gHz for either benchmarking or any other personal or religious reasons - i HIGHLY recommend using setCPU for this. again, just a recommendation based on experience and what i KNOW works ... i'm not even saying the other alternatives at this point DON'T work .. i'm just not going to recommend anything unless i KNOW from experience that it DOES work and keep this ROM stable and performing like it should.
ANOTHER side note, since i think it was asked a few posts above ... the built in smart ass governor (whether you use option A or B as I described above) - automatically underclocks your processor down to 245hz when your screen is OFF and also adjusts while your screen is on to use the least amount of power possible and still get the job done. So, you SHOULDN'T need ANY profiles in setCPU if you've got it on smartass gov.
AS ALWAYS - feel free to take my/our advice or not. just please don't come onto this thread and say you have random reboots or wifi that doesn't work or gps that won't lock, weird video performance, etc. and expect us to be able to do anything about it if you're going to choose NOT to follow our recommendations on what works for this stuff.
((as with many of these things - what works best for one person's phone/chip/usage/underwear size/sock color may not be what works best for someone else's ... so if you wanna experiment beyond our 'recommendations' - then make a BACKUP/nandroid with it setup how we told you to - then screw away with your hearts content (NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE BECAUSE OF ANY OF THIS! as usual) to whatever level you're comfortable with and if you don't like how it turns out - there's a very good chance, unless you did something INSANELY dumb that you will be able to just restore back to where you were and go on about your merry way))
<<we'll likely adjust the OP slightly to reflect the option of setCPU or no tuner>>
Last edited:
@dungtran88
So did you get this (v1.3) to work? With RoyalGinger 1.2, I could get the bluetooth to work with the Genius button, although it keeps force closing afterwards. To clarify, when I press the call button on my bluetooth headset, it would brings up the screen that I can do the voice command. Then as it dials the person I am calling, it would pops up the FC box, yet the call would go through.
But with this new v1.3, pressing the call button on my bluetooth only redials the last number. Pressing the Genius button on the phone itself would brings up the voice command screen. Strange.
Last edited:
my fault on the slight confusion on this you guys....I can see how a few of you could interpret the OP and some prior posts in differing ways like this.
read my long post above about this and it SHOULD clear up the confusion.
dang it sorry I changed the script, I for got to change the command. its
RemoveLauncher
thanks for bringing this to my attention, I totally spaced it. I will fix the OP. if that doesnt work let me know. maybe I messed something up in the code, there was a lot of lat nights working on 1.3.
Excellent, thanks man!ok I just finished up discussing this with Faux-daddy. here's what's up:
Faux recommends not using CM settings OR setCPU .. if you do not check 'set on boot' or touch/change (don't even look, lol) any of the clock speeds in the CM settings performance menu AND you don't even install setCPU then Faux's kernel will default to his smart ass gov he built and his default 1.1gHz max 245hz min settings. He believes this is what is currently the best setup and overall balance of performance and batter life.
Now, MY personal experience is this: I've been using setCPU for a LONG time. I use these same 'default' settings that Faux's kernel defaults to if you don't change it (smart ass gov, 1.1gHz max 245hz min) and I get PHENOMENAL battery life and speed/performance. I almost never / never have kernel related issues like some people report ... for example - I posted this a few days ago using RoyalGinger v1.2 with Fauxs 2.0.6 kernel:
(pictures attached below)
My battery was still at 100% after almost 6 hours off the charger .. granted it was obviously minimal use but I had 25 mins active display on time, I remember I had sent/received a handful of texts and emails. no phone calls at that point. wifi and sync/background data were on the whole time. brightness - auto. (no gps, bluetooth, or 4g)
a few hours later - I ran some bench tests and got a 63.703 linpack score.
(for that score, i had obviously maxed out the clock speeds temporarily in order to bench but for the battery performance purposes from earlier that day and every day use, i use 1.1ghz / 245 min)
Also, right now - my battery is at 74% .. it's been off the charger for 9 1/2 hours. I've sent/received dozens of texts and emails. I've surfed the XDA app a good amount. I've also been testing the crap out of it (trying out various functions, programs, etc) AND have even made a nandroid in recovery, and flashed THREE to FOUR different revisions of Ginger 1.3 (which entails booting back up, rebooting, and the market reinstalling all the market apps, titanium to restore data, etc etc) Now battery stats the day of new flashes, etc. aren't usually what you want to hang your hat on but I test, watch, analyze, and report this stuff virtually most of the day most days of the week and this is TYPICAL performance for me ... i NEVER don't see 16-24+ hours out of a full charge even with the heaviest use I can throw at it ...
so, HERE'S THE BOTTOM LINE (for now) ON THIS:
with THIS ROM, either:
A) don't install setCPU or use/alter ANY of the settings within CM settings / performance menu and run it with faux's 'stock' settings
OR
B) do what was stated in the OP regarding setCPU with the HIGHLY recommended settings of: smartass governor , 1.1gHz - 1.2gHz max, 245hz min (enable set on boot, no profiles)
these are the ONLY two methods that have been tested and tried by our team and the people that built this ROM and the kernel that goes with it. and both work VERY well. you guys can battle it out / decide for yourselves which one of those works better FOR YOU.
THE MAIN THING I WAS TRYING TO PREVENT IN THE OP AND WHAT YOU REALLY DON'T WANT TO DO IS BE USING setCPU AND ALSO HAVE THE CM SETTINGS PERFORMANCE TUNER WORKING AT THE SAME TIME COMPETING AGAINST EACH OTHER. I'VE SEEN THIS CAUSE LOTS OF ISSUES MANY TIMES. (you can prevent this by using either option A (new option/personal preference by Faux) or B (what was in the OP instructions and what i've been using for ages and gotten very good results with)
side note - if you ARE going/want to overclock beyond 1.1 - 1.2gHz for either benchmarking or any other personal or religious reasons - i HIGHLY recommend using setCPU for this. again, just a recommendation based on experience and what i KNOW works ... i'm not even saying the other alternatives at this point DON'T work .. i'm just not going to recommend anything unless i KNOW from experience that it DOES work and keep this ROM stable and performing like it should.
ANOTHER side note, since i think it was asked a few posts above ... the built in smart ass governor (whether you use option A or B as I described above) - automatically underclocks your processor down to 245hz when your screen is OFF and also adjusts while your screen is on to use the least amount of power possible and still get the job done. So, you SHOULDN'T need ANY profiles in setCPU if you've got it on smartass gov.
AS ALWAYS - feel free to take my/our advice or not. just please don't come onto this thread and say you have random reboots or wifi that doesn't work or gps that won't lock, weird video performance, etc. and expect us to be able to do anything about it if you're going to choose NOT to follow our recommendations on what works for this stuff.
((as with many of these things - what works best for one person's phone/chip/usage/underwear size/sock color may not be what works best for someone else's ... so if you wanna experiment beyond our 'recommendations' - then make a BACKUP/nandroid with it setup how we told you to - then screw away with your hearts content (NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE BECAUSE OF ANY OF THIS! as usual) to whatever level you're comfortable with and if you don't like how it turns out - there's a very good chance, unless you did something INSANELY dumb that you will be able to just restore back to where you were and go on about your merry way))
<<we'll likely adjust the OP slightly to reflect the option of setCPU or no tuner>>
[/QUOTE]
still not working, i am getting an new error see attached.
here is a screen shot
View attachment 539304
EDIT
still not working, i am getting an new error see attached.
here is a screen shot
View attachment 539304
Last edited:
also my fault, as i know i read it earlier, but i think it was in another thread now that i think of it... i have been all over the forums today reading all the goodies that are soon to come to us! so i to apologize!!!
It took me approximately 2 to 3 minutes to lock the satellites, but now it works.
Sent from my HTC Glacier using XDA App
Sent from my HTC Glacier using XDA App
So in conclusion, genius button still not function properly when bluetooth connect?
Sent from my HTC Glacier using XDA App
Correct. Otherwise, an awesome ROM. Thanks for the hard work, developers.
Good Work Ya
Running the lastest no setcpu i dont need it i dont overclock but i have to say running very nice nothing wrong with super smooth and everything working will report with battery life cause it takes more than 10 minutes to figure that out.
Running the lastest no setcpu i dont need it i dont overclock but i have to say running very nice nothing wrong with super smooth and everything working will report with battery life cause it takes more than 10 minutes to figure that out.
Hey on previous roms i was able to skip songs via volume button while the phone was in lock and had headphones on. This latest rom and the one before had it taken off. Anyone know how i can get that back?
So after 10 minutes of searching, still no GPS.
EDIT: Wait, just finished lol. Great rom guys.
EDIT: Wait, just finished lol. Great rom guys.
bout 1 minute for gps lock from standing outside.
Haven't noticed anything strange with the ROM yet. I'm trying to maintain a similar handling of my phone for 5 hours to see how it matches up to my CM7rc2 battery levels.
Don't know if this is just me but in theme chooser, the Androidian preview isn't there. I was able to select it but there wasn't a pic above the apply button.
Haven't noticed anything strange with the ROM yet. I'm trying to maintain a similar handling of my phone for 5 hours to see how it matches up to my CM7rc2 battery levels.
Don't know if this is just me but in theme chooser, the Androidian preview isn't there. I was able to select it but there wasn't a pic above the apply button.
Last edited:
just remember..right after or same day as flashing a new ROM on your phone isn't usually the best time to judge the battery life .. wear it down to as close to 1% as you can tonight and then let it charge fully tonight and test tomorrow as well
also, i haven't necessarily seen this as much with these newer/gingerbread ROMs but sometimes it still takes my phone a couple of days of normal use/charging to 'settle' in and get back to normal on battery performance (this usually has more to do with the way its reporting the battery life to you not with what's actually happening with the battery...but perception is reality naturally so i know how it is..)
New posts
-
Bluetooth headphones equalizer- Latest: BartoszBartosz1989
-
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone