yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] nspot:
Attached is the output from running bugreport. I had to zip the file because the plaintext file size exceeded the forum limit for a text file.

P.S. - If anyone wants a good overview of how memory management is handled by Android, here's a good video (props to AndRS for pointing it out on his site):

http://www.youtube.com/watch?v=ITfRuRkf2TM
[Hero CDMA Android Development] tejasrichard:
Sup guys! I haven't posted in a while, but I'm still around (pretty much daily, in fact, lol). Loving the kernel, Dec. My fone no likey BFS, but I've been trying every version you put out (then switching to CFS, when the FC's become too much to handle). I was also having a horrible memory leak. I don't know if it was related to your kernel or not, but I haven't had noticed an issue since I flashed the newest and started using autokiller (at one point my available ram got as low as three megs).

One question: on the first page, post 2, you have the instruction for echoing the 768 to scaling_max_freq. I haven't had any problem with that, but should this change be permanent? Meaning, is there something I can do to keep it from reverting to 691 everytime I reboot? If not, I am assuming I could make a script to do this. something like:

#su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#echo 76800 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

If this is correct, how could I set this up to run automatically at boot?
[Hero CDMA Android Development] Decad3nce:
Try it without first.. then if you need more aggressive memory management, throw on autokiller.
[Hero CDMA Android Development] Decad3nce:
I'll have to look at it when I have some more time. It's probably nothing big. Are you able to replicate this problem every time?
[Hero CDMA Android Development] LiquidSolstice:
Alright guys, just for ****s and giggles, I decided to flash the most recent BFS kernel to Nfinite's stock rom. Performance was quite good, if I overlook the fact that the kernel broke the wifi. Either way, I'd say don't bother trying to use this on his stock-based ROMs, Zen's AnyKernel is perfect for this.
[Hero CDMA Android Development] nspot:
It's happened three times in the last 24 hours. I use the Music app a lot, so it's not EVERY time. Also, I'm not modifying lowmem using Apps2SD. I've used both AutoKiller and Apps2SD in previous kernel iterations with no issues, though.
[Hero CDMA Android Development] Decad3nce:
That might mean that I need to recompile the wlan.ko for that kernel since it shouldn't 'break' wifi.

Can you specify which one: 691 or 768?
[Hero CDMA Android Development] Decad3nce:
I'm thinking that this might just be an issue with scaling. Tried any other cpu scaling governors?
[Hero CDMA Android Development] tejasrichard:
Hey dec, any ideas on my question above?
[Hero CDMA Android Development] Decad3nce:
Make a shell script.

#! /system/bin/sh
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
echo "768000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Throw it into system/etc/init.d

Should run every boot.
[Hero CDMA Android Development] nspot:
Been using "interactive" with Stable #9. However, I've also used that governor with previous stable kernels with no issues. I'll try "ondemand" and post how that goes.
[Hero CDMA Android Development] tejasrichard:
Awesome! Thanks man!
[Hero CDMA Android Development] Decad3nce:
Also.. is it force closing? It may just be the memkiller being overly aggressive and killing the pid.

EDIT: NVM, you said phone freezes. Bahh. I'll have to look over the log you sent me. May just be a cpu peg. Note that the cgroup errors are still in this kernel and won't be resolved until we get .32; so there are still times where there's a 'spam' of events that overload. That could be where this 'freeze' comes into play.
[Hero CDMA Android Development] tejasrichard:
no go on the script. I created it in notepad++ I called it setscaling.sh

here is my code copied from notepad++:

#! /system/bin/sh
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
echo "768000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

I also tried it without the # at the beginning (tried it that way first, actually)

edit: Just tried running it manually, and it worked fine...so now, I just need to get it to run at boot.
[Hero CDMA Android Development] Los Altos:
Got a bit of a boost myself :D
[Hero CDMA Android Development] partytrikk:
regarding the newest release. my phone will only over clock up to 729 and still function. so, which version should I download? never noticed if there were 691 and 761 versions on previous releases.. must have just over looked it.
[Hero CDMA Android Development] Vandelay007:
If you like your phone at 729 then you don't want the 691, because it caps off there...if you take the other you will get what you're looking for...
[Hero CDMA Android Development] Vandelay007:
Awesome :)
[Hero CDMA Android Development] 24601:
Tried BFS for awhile but gps was spotty. Flashed latest CFS and much more stable for me. Using Collins_ph battery tweak with 768 setting and interactive governor. I also discovered more stability if autokiller was between strict and agressive so I set that manually. I stopped with the nightlies at full 81. It seemed I was getting lost (too many moving parts to reset) with the tweaks and settings each time I would flash a nightly. I believe someone earlier posted a suggestion to KISS, and I would +1 that sentiment, especially if you're a novice like me. Find a setting that allows your phone to work like a phone, and leave it there. Let the devs here do the experimenting.

Dec, it was time to donate today. Kudos on providing valuable kernels, information, and feedback.

Edit: Performance example: Using Exchange by Touchdown and K9 mail. Played 18 holes yesterday using SkyDroid for yardage. Started with 90% battery and after 4 hours still had 68% remaining. Received about 50 emails during the round, responding to about half. In previous 2.1 life, this would have killed my battery entirely.
[Hero CDMA Android Development] fifedogg:
Damn you! LoL

You beat my best of 505...I'm gonna see if I cant get a little boost myself with the new BFS Kernel...
[Hero CDMA Android Development] madeSICC:
Are you guys using jit? I got 505 on a previous kernal using it but I get about 460 with this new one with jit off.

Froyo!.... its whats for dinner.
[Hero CDMA Android Development] Vandelay007:
Yeah, I have jit on
[Hero CDMA Android Development] fifedogg:
Yup using JIT. I just got my best score ever 509 :-)

My phone gets faster and faster with these kernels...

I just wish BFS didnt give me the screen unlock lag and I would be running it every day instead of the CFS.
[Hero CDMA Android Development] madeSICC:
Do you guys use like the pro version of quad standard or something. My results screen doesn't look anything like that

Its just a blue bar

Froyo!.... its whats for dinner.
[Hero CDMA Android Development] fifedogg:
Yeah its the paid version...It just breaks down the seperate catagories by color is all.
[Hero CDMA Android Development] stricklerjosh:
I flashed the #5 stable and I am still having a few seconds of lockscreen lag. Any suggestions on which stable to use? I'm using cm6 stable and overclock with the black gold theme. GPS is very important to me so I want to keep it stable.

Thanks in advance.
[Hero CDMA Android Development] fifedogg:
I get 0 lockscreen lag on the stables...I only get lag on the BFS kernel no matter what governor I use.
[Hero CDMA Android Development] Los Altos:
Yeah JIT, needed it to get into the 500 Club. Interesting side note; my phone never runs as well with the stable kernels, its smoother and faster with BFS.
[Hero CDMA Android Development] hotaru:
which governor are you using with the stable kernels? i've found interactive seems to work best with the stable kernels and on demand seems to work best with bfs.
[Hero CDMA Android Development] Los Altos:
Didn't think about changing it, I switched to OD a couple months ago and never tried interactive again. Ill have to consider that next time.
[Hero CDMA Android Development] bso44:
Newbie here. How come there are two different links listed for each kernel? One is tagged as 768 and other is 691.
[Hero CDMA Android Development] theimpaler747:
One is capped to 691, and the other can go up to 768 for users who can handle that frequency without their phone rebooting.
[Hero CDMA Android Development] bso44:
How would you know if your phone could handle the higher frequency?
[Hero CDMA Android Development] theimpaler747:
Just try it, and if there's random reboots you know its a no go ;) Really trial and error is the only way
[Hero CDMA Android Development] bso44:
Thanks. Will do.
[Hero CDMA Android Development] danaff37:
Random reboots, or a no boot like I get. I can't even boot a 768 kernel far enough in to adb.
[Hero CDMA Android Development] theimpaler747:
Well that's because your phone can't handle 768... you'll just have to stick with the capped 691 version
[Hero CDMA Android Development] danaff37:
Thanks for rubbing it in. lol
[Hero CDMA Android Development] theimpaler747:
Lol not trying to man :p
[Hero CDMA Android Development] Fyoolie:
Yeah my phone can't handle higher than 691.. I still have the uncapped kernel but I have setCPU set to max out at 691. It's working soooooooooo fast. I even have no lag with the keyboard now!
[Hero CDMA Android Development] davec1234:
Also shouldn't use "set at boot" for set cpu until it's known what speed works. Found out the hard way :)

CM6 Android 2.2.1 Froyo Darchstar

Radio 2.42.01.04.27

*Bite me Sprint!
[Hero CDMA Android Development] danaff37:
The latest set cpu had a way to disable set at boot if you can't boot by using a file on the sdcard.
[Hero CDMA Android Development] stayclean:
Never actually tried running at 768 before, this is pretty great.
[Hero CDMA Android Development] davec1234:
Or you can simply uncheck the box before you reboot to test.

CM6 Android 2.2.1 Froyo Darchstar

Radio 2.42.01.04.27

*Bite me Sprint!
[Hero CDMA Android Development] hexskrew:
I have the stable kernel set to interactive clocked @710, but lately it's been restarting on me at least twice a day for no appropriate reason.. Logs to follow

Meh.. there is no last_kmsg file in /proc, only kmsg. I tried to post but WAAAAYYYY to many characters says the pop up...

It's ok, I am going to wipe dalvik and use the newest stable :)
[Hero CDMA Android Development] bso44:
So I just flashed the latest CFS kernel. I'm having trouble downloading anything from the market or signing into Google Talk. It just gets stuck on "Starting Download". Not sure if it's a problem on Google's end or if it's related to the new kernel.
[Hero CDMA Android Development] halrulez:
a few of us have had that problem
[Hero CDMA Android Development] bso44:
Got mine working so it must've been a problem on the Market's end.
[Hero CDMA Android Development] vashing:
I'm having serious SD card lag. With 2.1 I had no issues. It seems to take my phone several minutes after startup to load all my apps on sd and for my home launcher to function. My quadrant is scoring very poorly on I/o also. I have a class 6 SD card that was very dependable on 2.1. What could be causing this?
[Hero CDMA Android Development] Vandelay007:
It could be a couple of things...how long have you had this card for? Cards do have a "shelf life" in a way....they do go bad....also, have you tried copying your data to your computer and formatting your card and loading your data back on to it?
[Hero CDMA Android Development] vashing:
The card is only a month old. I can restore my copy of fresh 2.4 with rom manger and the lag is nonexistant. I'll try formatting, could my card still having a swap and sd-ext partition have anything to do with it?
[Hero CDMA Android Development] Brandito:
what brand is the card?

sometimes with sd cards a good "deal" can bite you in the butt. some of the lesser known brands will be mislabeled.
[Hero CDMA Android Development] vashing:
Transcend 8GB Micro SDHC Flash Card Model TS8GUSDHC6

http://www.newegg.com/Product/Product.aspx?Item=N82E16820208453&Tpk=20-208-453

I'm backing up and formatting the card now.
[Hero CDMA Android Development] BlaqkAudio:
I have the same problem, same card. CM6 seems to take a while to fully mount the SD card on boot.
[Hero CDMA Android Development] danaff37:
Yeah, it's a cm6 thing. I actually removed all my apps from sdcard and used the partition mod from fire rat because of it.
[Hero CDMA Android Development] hexskrew:
Shoot. Think that is bad, try using cm6 with a class 2 card.. As soon as one app get's copied to the card it makes your phone pretty well useless..

If you use apps2sd though instead of the built in 2.2 a2sd-like system, it should solve that problem.
[Hero CDMA Android Development] zansatsu:
#1 -BrainFuct

This experimental kernel is very smooth, I'd say smoother than the #7 Stable. I will use it for a bit and see how my Hero likes it, but so far it looks like a winner.
[Hero CDMA Android Development] Visionikz03:
yeah sorry forgot to pull it b4 i nandroided back :(... ill try the newest one u posted. Thanks Dec!!!
[Hero CDMA Android Development] Decad3nce:
see post 2
[Hero CDMA Android Development] omeganot:
Woo! Thanks for the update with all the schedulers enabled again. I'm more than happy to give the feedback, but was just confused as to where all the other schedulers went! Until I can play with this a bit and see how it does on battery (well I hope) I was just looking for the ability to swap back to a more known constant...with badass CPU frequencies. ;)

So far, I'm finding interactive to be highly useful for a screen off profile in SetCPU. Makes the lockscreen unstick much quicker, as long as my low end isn't 19MHz. I've found 122-352 to be incredibly responsive when hitting the lockscreen. Otherwise, I've found some of that screen lag to go away right now running 19-768 (or 122-768) interactive on the experimental, though I occasionally have a hiccup pulling down the notification bar. I have to fully drag it down instead of flicking it down. No test on GPS yet.
[Hero CDMA Android Development] zansatsu:
I agree with the scroll issues. Instead of being able to impart momentum on the list, I've also noticed that the lists are not easily flung. Battery life is much improved on the -brainfuct #1 kernel.

How would I go about manually selecting the governor?

I'm sure it can be done with a simple command line or editing a file (.config is it?).

No Hero gets left behind!

Sent from my FROYO HERO.
[Hero CDMA Android Development] Visionikz03:
I didn't actually leave my house yet lol but I can confirm GPS gets signal lock with BFS kernel in maps/nav nd shows my exact location... ill have to test on the way to work tomorrow to see if it holds a signal for more than a few minutes.
[Hero CDMA Android Development] Decad3nce:
See post 2 for instructions on changing the cpu governor manually.
[Hero CDMA Android Development] LifeInTheGrey:
Confirm GPS break on BFS kernel. Its a stuttered lock like on the first kernel. Also doesn't let me use Swype anymore for some reason. Its fast as hell though!

Sent with Hero juice using XDA power
[Hero CDMA Android Development] Decad3nce:
Are you on the BFS kernel or on the #8 stable?
[Hero CDMA Android Development] Decad3nce:
I'll spend some time this weekend seeing if I can prioritize gps so that it can run consistently, though it's very difficult without access to GENTLE_FAIR_SLEEPERS.
[Hero CDMA Android Development] zansatsu:
I'm on the BFS kernel.
[Hero CDMA Android Development] Decad3nce:
The lag you're experiencing is only 'visual' lag. The scheduler is actually processing stuff quicker than the system can visually interpret it.

That lag is 'ok' for some people as long as they are receiving the worthy performance gain.

Same thing is happening with stable #8, but BFQ(under my testing) really isn't giving the performance boost that I'd hoped for.

You can change the scheduler for the time being to 'deadline' which was the default in #5(which everyone seems to be having the best performance/quality with) by inputting this in shell:

(You can only change it in #8, BFS is unchangeable)

adb remount
adb shell
echo "deadline" > /sys/block/mtdblock3/queue/scheduler

This is only a temporary workaround, until I compile a kernel with it as default. Or you can just use #5 on the OP.
[Hero CDMA Android Development] Visionikz03:
Him Ill still test mine tomorrow... how long did it take b4 it started hesitating?
[Hero CDMA Android Development] LifeInTheGrey:
Right away. The hesitation is basically a solid lock on a single point, then when you're moving, the GPS doesn't recognize it. After 30 seconds or so, it gets a solid lock on your location again, but it stays at that spot. Its an endless cycle of lock and loss, rather than the constant streaming lock as it should be.
[Hero CDMA Android Development] andygu3:
Thanks for all the hard work, I've flashed the 816 kernal the last couple of days, awesome! Just flashed the 820 with uncapped 818#7, so far, incredible
[Hero CDMA Android Development] zansatsu:
Thank you very much for this. I honestly like the BFS kernel and have been trying different governors. So far, interactive is still my favorite. When the lag gets annoying I'll go stable, but I'm enjoying the quickness of the BFS kernel.
[Hero CDMA Android Development] s0be:
Based on what's included in your patch zip there, we're on BFS 0.302, which is 'old' (give or take, october 2009). The latest BFS is much much better. Have you looked at going to 0.323?
[Hero CDMA Android Development] s0be:
@Decad3nce:

try this patch instead of your current patchset.zip http://www.erley.org/bfs-323-for-heroc.diff
[Hero CDMA Android Development] nspot:
Potential broken applications?

I'm running stable#8 (ondemand governor and deadlinbe scheduler), and have run into multiple force closes with both Goggles and Shopper (when using image scanner). Maybe this ties into usage of the camera? Has anyone else had this issue?
[Hero CDMA Android Development] Decad3nce:
It's a known issue. I'm addressing it for the next release.
[Hero CDMA Android Development] cjdalessio:
Something appears to be quite wrong with the 10/12 Stable kernel and the Email app.

It connects to only one server after a reboot, then enters a frozen loop where it just eats battery and CPU cycles, slows the phone down, and goes nowhere.

Log becomes a constant churn of noise with the same two messages repeating endlessly, every so often a Heap message from dalvik.

D/dalvikvm(ID1): GC_FOR_MALLOC freed XXXX objects / XXXXXX bytes in XXXms

D/dalvikvm(ID2): GC_EXPLICIT freed XXXX objects / XXXXXX bytes in XXXms

ID1 and ID2 are, I believe, process ID's. It's consistently the same two alternating in the logs. A reboot changes the ID's, but not the problem. The number of objects and the byte size change every line.

I tried with a couple schedulers (noop, deadline for sure, I think one more) and also interactive and ondemand. Pushing back to the 10/3 release fixes it. I've bounced back and forth and see this every time, so far.

I should note that I have seen a similar issue after ~12-15 hours of mostly working when I use a BFS kernel - I have to reboot daily for email to work, but somewhere overnight it dies. I have not tried the most recent BFS due to this making the phone completely unusable.

I use Email to connect to an Enterprise Exchange server (primary account) as well as 4 IMAP accounts.
[Hero CDMA Android Development] fifedogg:
For the guys with the slow SD card issues... What Kernel are you running? I'm using a cheap ADATA Class 6 and I dont have any issues what so ever... I noticed BFS is faster when booting up and loading the SD card.
[Hero CDMA Android Development] srthimsen:
Have you tried disabling certain accounts to see if it helps the issue?

I'm using the same setup, but with only exchange running in email with no issues.
[Hero CDMA Android Development] vashing:
I was running cfs #5 then switched to #9. I just finished upgrading to BFS #13 and there is a slight improvement, but it still lags on boot. Booting with the sdcard removed seems to help.
[Hero CDMA Android Development] cjdalessio:
Not yet. I may also do a full wipe and rebuild this weekend and add stuff back bit by bit. It has been quite some time since I have.

I've been in a bit over my head at work so no time for really rooting through an issue properly. The pressure may let up a tiny bit now but we'll see.
[Hero CDMA Android Development] bso44:
Running the latest CFS at 768.

So I am getting a few random reboots (3 today) but my phone's really fast and smooth at 768. Should I just scale it down just a bit or should I flash the 691 version?

Has anybody figured out why some phones can handle 768 while others can't?

Also, what are the disadvantages to enabling JIT?
[Hero CDMA Android Development] theimpaler747:
Flash the capped version If you get random reboots, and I would test out jit... some love it others don't :)

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] Brandito:
small differences in the silicon. just like with desktop cpus, it's the luck of the draw as to whether you get one that will overclock like a dream, or one that will barely run above stock.

all depends on yields and the maturity of the manufacturing process.
[Hero CDMA Android Development] bso44:
Gotcha. I'm going to keep the uncapped kernel and see it it's any better on 748.
[Hero CDMA Android Development] theimpaler747:
It should be, let me know if you need anything else!
[Hero CDMA Android Development] Pwn3d:
What kernel gets the highest MFLOPS? Im getting about 3.7-4 with uncapped #9.

----------

My sprint hero is running FroYo, take that!
[Hero CDMA Android Development] theimpaler747:
BFS will be the fastest on the benchmarks
[Hero CDMA Android Development] Pwn3d:
Ok

----------

My sprint hero is running FroYo, take that!
[Hero CDMA Android Development] madeSICC:
I get about 5.7 with the latest bfs kernal

Froyo!.... its whats for dinner.
[Hero CDMA Android Development] theimpaler747:
Yeah, I got about 5.5 with BFS and JIT
[Hero CDMA Android Development] Pwn3d:
How?!?

Im using BFS #13 now and still getting 3.6-4.0

Can I see your ROM, kernel and all that stuff?

----------

My sprint hero is running FroYo, take that!
[Hero CDMA Android Development] theimpaler747:
Do you use set cpu or the battery tweak?
[Hero CDMA Android Development] Pwn3d:
Battery tweak cuz idk how to use set cpu

It makes my phone freeze, setcpu

----------

My sprint hero is running FroYo, take that!
[Hero CDMA Android Development] theimpaler747:
Ok, to get high scores, you'll have to modify the frequency so the max and min are the same number, like 691-691 or 768-768. I wouldn't really worry about getting a benchmark score though. They're really kind of useless
[Hero CDMA Android Development] Pwn3d:
Ok ill try :D

----------

My sprint hero is running FroYo, take that!
[Hero CDMA Android Development] theimpaler747:
Cool, let me know if you need anything else :)
[Hero CDMA Android Development] Pwn3d:
Awesome! Just got 4.2-4.3 2 times in a row :D
[Hero CDMA Android Development] theimpaler747:
Cool, nice man :D
[Hero CDMA Android Development] cjdalessio:
I did a full wipe and re-install with the very latest nightly (build 89), 9/17 gapps release, the 10-12 Stable kernel, and the rc3v2 battery script. Put all the email accounts back. I'm at 6hrs off charger and 75% left.

There's something to be said for rebuilding from the ground up now and again.

C
[Hero CDMA Android Development] Decad3nce:
Glad to hear that you have that working properly now. I was stumped looking at my recent changes. :P
[Hero CDMA Android Development] coffe34:
you know what thats what im gonna do. thanks for the friendly reminder.

should help with lag as well.