yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] PRGUY85:
I tested for 1-2 days and can't. As I see it, this is basically stripped down CM7. The CPU settings it has as default were more battery intensive than the ones I used on CM7. So, unless he did something else to the ROM to improve battery life, I don't see how it can be much better.
[Hero CDMA Android Development] mkeyslehman:
As this uses the CM7 kernal, I would expect CM7 battery / performance. CPU adjustments can be made under Settings > Advanced Settings > Performance > CPU Settings. Lower your max_freq to increase battery life; our stock max_freq is 524Mhz (as a point of comparison). I would leave the min_freq @ 264Mhz as the next step down (176) is way too low. CM7 governors don't stay locked at the min_freq when sleeping, which means the processor will ramp up if the CPU load is too high. On my phone (OnDemand with min_freq set at 264), even with nothing installed (not even GApps) it kept scaling up, back down, and up again when sleeping.

*Edit* - I know everyone's phones operate differently, but per my phone and experience, using the SmartAss governor with a min_freq of 19Mhz results in the lowest CPU operating freq while sleeping. The same trick does

not

work with any other governor; setting the min_freq too low means the phone will always be above the load requirement and will never step down, resulting in a phone that always operates at max_freq (effectively the "performance" governor).
[Hero CDMA Android Development] ch1naski:
Thanks for the info.

π

sent from GB hero.
[Hero CDMA Android Development] someonenewhere:
I'm impressed with this ROM! Good job!

Sent from my HERO200 running GB 2.3.4!
[Hero CDMA Android Development] PRGUY85:
Yes smartass at 19mhz with screen off means lag on music players right?

So, if I've been running 518/19 OnDemand with no problem, it means when phone is sleeping, its actually higher? Could explain that I don't notice better battery life. What would be the best battery saving mode/settings then?
[Hero CDMA Android Development] mkeyslehman:
Dynamic governors (such as OnDemand) poll the processor at a predefined rate to determine if, based on the current load, the processor can throttle up or down. CM7 is built for performance, and thusly the governors are set to throttle up quickly. Your phone is physically incapable of running anything at 19Mhz, so using a dynamic governor that never throttles down does absolutely no good. Instead, try the Performance governor which will never poll the CPU and always runs at max_freq.

SmartAss is a dynamic governor that is a more conservative approach to the Interactive governor. By setting a lower min_freq, you're requesting lower step up / step down values, so it stays lower when possible. The slower a dynamic processor ramps up, the laggier your experience. I believe SmartAss is also the only CM7 governor that locks the max_freq when the phone sleeps at 352Mhz, which is too low to play your music uninterrupted.
[Hero CDMA Android Development] PRGUY85:
So what so you suggest for best battery performance without compromising experience? Thanks for the info man. Very informative.
[Hero CDMA Android Development] il Duce:
False

Why would anyone want to run at max CPU?

True (but it's when the screen is off, not just sleeping), it also locks your screen on min to 518

False, most people play fine at 264 min on smartass, and literally everybody can play music (streaming or sdcard) at 352 min 352 max.

Ondemand 176-691, IMHO.
[Hero CDMA Android Development] PRGUY85:
So OnDemand over Smartass or Interactive?
[Hero CDMA Android Development] PRGUY85:
And why would that give better battery performance than 518/19 Ondemand
[Hero CDMA Android Development] PRGUY85:
For example, my phone shows to be running 66% of the time during the three hours since I unplugged it. I haven't used it for more than 5 minutes int those three hours. Partial wake usage shows nothing running for more than 7 minutes. So what gives? I'm Already at 85%with no usage and using Ondemand 518/19 after battery calibration.

And I started using Autokiller set at aggressive but have seen no improvements so far.
[Hero CDMA Android Development] Tibson:
Stop setting the min higher than the max and you'll notice a world of difference.
[Hero CDMA Android Development] PRGUY85:
.........

I refer to 518 Max- 19 Min. I thought that was self-explanatory.
[Hero CDMA Android Development] mkeyslehman:
From a purely literal standpoint, yes your phone can run @ 19Mhz. But it will take hours to do anything. And from a governor standpoint, your CPU load will

always

be above up_threshold. Even a min_freq of 176 is really too low for our phones; they'll clock that low for a bit, but up_threshold will (nearly immediately) be met and your phone will clock right back up to max_freq. Feel free to put your phone to sleep and then cat scaling_cur_freq; I'll predict you'll see your max_freq reported more than 50% even with the most basic, minimalistic setup using OnDemand with a min_freq of 176. The more active apps you have, the greater % of the time your phone is running full throttle.

Move min_freq to 19Mhz and you're running at max_freq 100% of the time as up_threshold will

always

be met.

I was taking the assumption from the previous post that the music player would be in use and that they had experienced choppy playback using the SmartAss governor. I was also taking the assumption that they would continue using their existing max_freq value of 518. Sorry for trying to make suggestions based on the existing thread conversation. ;) If you're running your CPU at full throttle anyways (see above), I'd suggest you choose the governor that doesn't use additional CPU cycles sampling the current load.

SmartAss is the governor to use for battery efficiency. But if you play music and it's choppy, try Performance with a max_freq of 518, 576 or even 480. Or you could manually switch between the two if you feel like messing with it. If you prefer OnDemand, set the min_freq to at least 264 so that up_threshold won't be met as often and your phone has a better chance to stay clocked down.
[Hero CDMA Android Development] PRGUY85:
Loving the info I'm getting out of both your replies.

I thought leaving 19mhz as min would be best for when phone wasn't in use, screen off. Did what you say also apply to screen off conditions?
[Hero CDMA Android Development] abadasstanker69:
All this info is awesome. This rom has out performed all other gb roms on my phone. Now that I know how to set my CPU governor it's working even better. I'm set at 276 min and 710 Max. 768 breaks my GPS for some odd reason ...anyway thanks for the info guys
[Hero CDMA Android Development] il Duce:
Really on the gps? Or does your phone always reboot at high freq? I wonder if thats the answer to the elusive gps reboot issue...
[Hero CDMA Android Development] PRGUY85:
So with all that has been learned, I'm guessing Smartass governor is better for battery life compared to OnDemand right? If so, can you use same min-max on Smartass (ex.518/264) or do you need something higher?
[Hero CDMA Android Development] PRGUY85:
Already noticing sluggish performance with 518/264 OnDemand which proves the point that with 518/19 I was always running at 518.
[Hero CDMA Android Development] il Duce:
Honestly it depends on each user and how they use their phone. In theory yes, because it caps the screen off max to 352. To the second part of your statement I don't quite get your question. If you used 264-518, it would run locked at 518 with the screen on and 264-352 with the screen off - does that help?
[Hero CDMA Android Development] PRGUY85:
So with OnDemand, the phone may be higher than 264 when Screen is off then?
[Hero CDMA Android Development] il Duce:
Yes sometimes, it would be able to scale to whatever you max is set to.
[Hero CDMA Android Development] kushdeck:
1.2r is up! I have spent so much time on the ns4g, i was neglecting my other phones :P Please help support this project, check out a few sponsors site's when downloading.

[size=+1]*Official thread and ALL Downloads*[/size]

[size=+1]*Issue Tracker*[/size]

[size=+1]*Changlog*[/size]

I hope you all enjoy.

-deck
[Hero CDMA Android Development] Freeport36:
bad download...

I downloaded and went to install after the appropriate steps and the install failed saying "can't open .zip (bad)...

Help?
[Hero CDMA Android Development] ehusidic:
I downloaded mine it worked well. Try to download it again? Or maybe format your sd card ive had that problem before.

On another note. How do you work the slide status bar brightness control? Ive been trying to figure it out but have no idea how to get it to work.

EDIT: Nevermind I figured it out. You have to touch one end of the status bar til the pull down menu appears then slide your finger across the bar.
[Hero CDMA Android Development] abadasstanker69:
Dude this is an outstanding release! Thanks for the added effort involved in bringing this across multiple platforms as well. That's the type of **** that put xda on the map. Drach and aosp and all the guys who made a name for themselves did it by doing exactly the same thing you are doing now. We really appreciate all you guys.
[Hero CDMA Android Development] Drunkpilot:
I finally get to give this a try today. Thanks for the great banter regarding governors, I found it very interesting.

I am wondering how that same conversation would work for schedulers that could be used for this kernel as well.

Thanks for getting this going.

Flashing IS a gateway drug!
[Hero CDMA Android Development] PRGUY85:
Yea, I'm still trying to decide on the best CPU settings still. Trying Smartass 518/264 at the moment.

Also do you guys think Autokiller improves battery life in this ROM or any other CM7based ROm?
[Hero CDMA Android Development] buddha95023:
Is data working on roaming with this rom?

using the nightlies and were i live i roam but im not getting data looking for another rom to try hows this rom working for you
[Hero CDMA Android Development] PRGUY85:
Something is keeping my phone running 60-70% of the time since I unplugged it from charger. I haven't used it for more than 10 minutes in 3-4 hours. Partial Wake usage shows nothing keeping it awake...ideas?
[Hero CDMA Android Development] laie1472:
Have you tried disabling Mobil data if you have it running??? Or if you have automatic sync on have you tried to uncheck that??

#Root/Hack-Mod_Always*
[Hero CDMA Android Development] PRGUY85:
Hmmm this is different. I always have those ON and battery doesn't drop that quickly. 20% loss in 3 hours barely using it? Something's up.
[Hero CDMA Android Development] laie1472:
Try running it with them unchecked and see how it works. Or just wipe cache and dav-cache and see if that might help.

#Root/Hack-Mod_Always*
[Hero CDMA Android Development] macp10181:
This Rom is awesome! Great battery life and very smooth. GPS also locks quickly. Deck rules!

Sent from my Hero with gingerbread action.
[Hero CDMA Android Development] btaylor545:
Deck great job lovin this rom this just became my daily. Running smooth as hell so far no probs except launcher pro can't stay loaded after a while but had same prob with cm7 and aosp I think it has something to do with my apps on my sdcard. but other than that this rom is great!
[Hero CDMA Android Development] il Duce:
Ok this might not work but it might so try it. In your build prop add this line:

ro.HOME_APP_ADJ=1
[Hero CDMA Android Development] bravo1565:
Would I need a full wipe to flash update
[Hero CDMA Android Development] bravo1565:
OK I know I need full wipe but download keeps saying unsuccessful tried like a dozens time
[Hero CDMA Android Development] cbarth3:
If we are updating from a previous version should we wipe and flash like the first post directions?

By the way I just want to say thank you for your work as this is the first time I have actually wanted to run anything other than a 2.1 sense rom. Works great
[Hero CDMA Android Development] bravo1565:
This update is great thanks for the hard work but how do you get the sliding task bar to work I've trying but don't see any difference
[Hero CDMA Android Development] btaylor545:
Thanks iL Duce that worked GREAT and what a difference now this rom is working perfect Thanks!
[Hero CDMA Android Development] btaylor545:
Press and hold the status bar till the date shows up then slide left and right instead of down. Sometimesh its a little slow also make sure the option is checked
[Hero CDMA Android Development] abadasstanker69:
Just some extra info. I recalibrated my battery after flashing this rom and it went from 100% to total shutdown after 3 hours and 11 minutes of talking the entire time. My governor is 264-710 in case you're wondering. That's what I got on the factory 2.1 rom. Just thought I'd share the info. I noticed a significant change for the WORSE since I updated the prl. I assume it's due to the fact that I drop reception down to 1x and evdo more frequently. This is NOT due to the rom in any way and is due to my geographic location (Memphis TN) I'm sure. I just thought I should mention that as well. I'm currently recharging the battery to test battery temps with extreme web usage. Not because I think it will be an issue, but I'm kinda curious. Anyway, sorry to cram up the thread with useless facts but I thought maybe the dev would appreciate feedback regarding these things. Thanks again for all the work man!
[Hero CDMA Android Development] PRGUY85:
Thanks for the info. I noticed that after updating PRL 2-3 weeks ago, reception in my house has dropped a bit as well.
[Hero CDMA Android Development] abadasstanker69:
I thought it may have something to do with the implementation of 4g in Memphis but I can't find anything from sprint to confirm it. Just a thought ...
[Hero CDMA Android Development] griffincash:
How could updating your prl change your reception unless you are constantly roaming?

Also I'm on twenty hours of light to moderate usage with 52% battery. No tweaks
[Hero CDMA Android Development] PRGUY85:
Don't really know, although on my room and the place I work at, my phone signal is dismal.

I wiped and flashed the latest release, was doing calibration yesterday. It lasted 22 hours or so, with light to moderate usage. I have done no tweaks to the stock CPU settings the ROM came with. Maybe I could lower the max frequency from 691 to below 600s to squeeze more battery. Let's see how it performs when I turn it on after recalibration, its currently charging to 100 again.
[Hero CDMA Android Development] btaylor545:
Just noticed this little glitch dunno if anyone else is having this prob but everytime I restart I have to log in to facebook and twitter apps and resync anyone else having this problem?
[Hero CDMA Android Development] wampuscat:
Anybody running sumpin other than the cm kernel. Won't be loading this till tomorrow but on cm 7 I loaded a deca kernel and it gave me a better experience than what came with it
[Hero CDMA Android Development] cbarth3:
Just did a reboot and my twitter sync was gone. Had to relogin but the twitter app saved my settings.

What other kernels can we use for this rom?
[Hero CDMA Android Development] wampuscat:
I'll look on my girls hero tomorrow and see which one it was I had on it with cm 7.0.3.1. I'm pretty sure it was called decafunked. I can't remember, I stay mostly in the EVO forums now. But I'm running the same kernel on decks EVO Rom that I had on 7.0.3.1 so it should run just as smooth
[Hero CDMA Android Development] ch1naski:
Decafuct. there are a few versions of it for heroc.
[Hero CDMA Android Development] Drunkpilot:
If you don't mind some camera glitches once in a while, you might want to try some s0be #5. It is a 2.35 instead of a 2.29 and once it warms up, it runs pretty well. I end up using it on everything- even when I recently went back to cm6.2 a while ago. It looks like aosp might be working on perfecting it even further now. Make a nandroid before you flash and you can always go back. I like Deca's #589 uncapped as well. That is I'd your probe can handle going over 691. There is a capped version as well I believe.

Flashing IS a gateway drug!
[Hero CDMA Android Development] wampuscat:
Thanks for the info. I s/l that sobe #5. She'll run 768 mhz all day long. Thought bout trying that 806 I saw maloney cooked up.
[Hero CDMA Android Development] Tengis:
My phone is stuck at the flash screen. I had no issues besides the Google Apps zip you provided... I downloaded a different one. I let it sit on the flash screen for about 20 minutes.
[Hero CDMA Android Development] mtnchkn:
Compared to AOSP Froyo (0.9.9.2)? 710? Firerat?

Aside from the great discussion about governors and kernels, I didn't see in this thread where the performance/usability of this ROM was compared to something else?

So, how is the performance/usability relative to another ROM? I have been running AOSP's Froyo build for some time and find it extremely stable with good battery. Any comparison to that would be great.

Also, my phone is one of those which can't take speeds above 691 (excuse the 710 reference which I think is still too high for my phone) which means any ROM with OC baked in won't load. I assume since this is based off CM it should be held at 691, but if someone could confirm that would be great. Otherwise I have DecaFunct 12-22-2010-691 laying around I can flash when I flash the ROM (I think this is #5, but definitely works with my phone).

Lastly, if running Firerat, does 100 2 seem to work good for everyone?

Thanks for the apparently great build.
[Hero CDMA Android Development] androidnoob111:
just downloaded will flash shortly and let u know how it goes.. loving all the roms to choose from..
[Hero CDMA Android Development] macp10181:
I can only speak to the performance and reliability, and compared to AOSP froyo this Rom seems alot smoother and faster. I haven't noticed the Rom bogging down after a while needing a reboot. Battery life is great, with moderate use I am getting over 24 hours.

Sent from my Hero with gingerbread action.

Edit: IMHO ;-)
[Hero CDMA Android Development] PRGUY85:
Yea only thing that kills my battery is music streaming from Music Beta/Rdio/Pandora.
[Hero CDMA Android Development] jadenj5:
What's the chance of this getting to the optimus s?
[Hero CDMA Android Development] il Duce:
/me is not trying to SPAM :( sorry deck..... anyway, aospCMod look on xda optimus V, works on opt S, update 5-31, peace. NO MORE SPAM!
[Hero CDMA Android Development] kushdeck:
1.2t is up! Many many many fixes. Please help support this project, check out a few sponsors site's when downloading. I need some testing!

[size=+1]*Official thread and ALL Downloads*[/size]

[size=+1]*Issue Tracker*[/size]

[size=+1]*Changelog*[/size]

I hope you all enjoy.

-deck
[Hero CDMA Android Development] mtnchkn:
Install with Firerat

Just flashed this ROM last night after going back to a stock ROM for a PRL update.

Steps (use Darch's 1.7):

- change mtdpartmap.txt to mtd 110 5

- wipe all

- flash Firerat custom recovery

- wipe all again

- abd reboot recovery (though apparently a battery pull and home+end reboot would have done the trick)

- flash ROM zip

- flash gapps (had to use 2011325 since I was getting an error with the gapps-hero-20110522)

- flash Firerat boot

- reboot

If I did this again, before reboot I would apply s0be's fix prior to restart since I lost all of my synced data on google servers (apps and bookmarks).

adb shell (or ./adb depending on your OS)
# su
# mkdir /cache/download
# chown system:cache /cache/download
# chmod ug+rwx /cache/download
# chmod a+x /cache/download

Using these partitions, total space on internal storage was 344 MB.

2 questions/comments:

1) When updating to newer version of this ROM, definitely wipe and re-flash everything?

2) I can't say its faster than AOSP 0.9.9.2 but it is fairly stable (sometimes keyboard doesn't display properly or screen just goes black when navigating settings menus) and the eye candy is great (though running LauncherPro).
[Hero CDMA Android Development] bravo1565:
I flashed the latest update and it seems alot quicker and more responsive great job
[Hero CDMA Android Development] cheyennemtn:
Go SMS 'can't disable default incoming messages'

Flashed last week. Very nice. More responsive and very few lockups. Not sure if its a Gingerbread general issue, default messaging tic I'm missing or just me, I'm using Go SMS and have disabled all my default message popups but still getting default popup when receiving a message.
[Hero CDMA Android Development] DJB628:
KDeck, one thing that seems to be happening on AOSP and your Rom version also is when we use Golf GPS apps, and the screen times out, we get constant reboots, you think you might have a solution for this issue ?
[Hero CDMA Android Development] ch1naski:
I have heard that it doesn't happen on CM7. Don't know for sure, I haven't flashed any cm thing other than aospcmod, personally.

Deck is next next, tho. : p

nandroids are for sissies.

sent from GB hero.
[Hero CDMA Android Development] DJB628:
I had heard the same thing and posted that on the AOSP thread, but after some research I have a few try it and they got the reboot when the screen went to sleep also and one is saying he didn't, so the jurry is still out, but I do know that it does not happen on the Froyo Rom on those Golf GPS apps
[Hero CDMA Android Development] cbarth3:
What version of firerat are you using?
[Hero CDMA Android Development] chocmatic:
Gapps doesn't install properly. it says "system/app/booksphone.apk is missing" Anyone else having this issue
[Hero CDMA Android Development] momoceio:
I did the same setup and I'm using 1.5.8

http://www.mediafire.com/?lifib6a9ptj5j#1pcwmbdd9kqpc,1
[Hero CDMA Android Development] mtnchkn:
I have been using 1.5.8, and just learned something fun. Using this version if you specify 18 (or greater I believe) for the cache size you don't have to use the market fix. I just installed 1.2t and changed by values to

mtdpart 128 18

but since I didn't know about the 18 being significant, still ran the fix from adb shell before first start.

For reference, using gapps-gb-20110325 (from aosp thread since the ones here don't work for me, probably my recovery image), this is what my partition setup looks like:

# df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.4M 32.0K 95.4M 0% /dev
tmpfs 95.4M 0 95.4M 0% /mnt/asec
tmpfs 95.4M 0 95.4M 0% /mnt/obb
/dev/block/mtdblock3 128.0M 108.1M 19.9M 84% /system
/dev/block/mtdblock5 313.5M 143.6M 169.9M 46% /data
/dev/block/mtdblock4 18.0M 1.1M 16.9M 6% /cache
/dev/block/mtdblock5 313.5M 143.6M 169.9M 46% /cache/download
/dev/block/vold/179:1
1.9G 1.2G 667.3M 66% /mnt/sdcard
/dev/block/vold/179:1
1.9G 1.2G 667.3M 66% /mnt/secure/asec

So you can see 128 18 is a bit overkill, but it works.
[Hero CDMA Android Development] mtnchkn:
GB Keyboard issues on 1.2r and 1.2t in landscape

Sorry to post twice, but I didn't want this issue to get lost in another post. Using 1.2r and 1.2t, I notice that when the keyboard is in landscape all the keys on the bottom row except for the space bar don't respond to touch well (e.g., I have to hit them multiple times) whereas keys immediately above work fine. I don't notice this behavior when in portrait.

Not sure if this issue is specific to this ROM or not, and I will get around to filing it as an issue soon.
[Hero CDMA Android Development] cbarth3:
df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 95.4M 32.0K 95.4M 0% /dev

tmpfs 95.4M 0 95.4M 0% /mnt/asec

tmpfs 95.4M 0 95.4M 0% /mnt/obb

/dev/block/mtdblock3 110.0M 109.1M 964.0K 99% /system

/dev/block/mtdblock5 344.5M 62.2M 282.3M 18% /data

/dev/block/mmcblk0p2 457.4M 8.0M 424.9M 2% /sd-ext

/dev/block/mmcblk0p2 457.4M 8.0M 424.9M 2% /cache

/dev/block/mtdblock4 5.0M 1.1M 3.9M 23% /dev/cache

/dev/block/vold/179:1

14.4G 8.6G 5.8G 60% /mnt/sdcard

/dev/block/vold/179:1

14.4G 8.6G 5.8G 60% /mnt/secure/asec

I used version 1.56 with the settings of 110 5
[Hero CDMA Android Development] ch1naski:
You might want to use 1.5.8, and up your system to something with a tad bit more wiggle room, maybe 112, and cache at between 15-20. Eliminates any d/l issues (market, etc.)

Edit: nvm, someone already said it. /me needs to pay attention.

nandroids are for sissies.

sent from GB hero.