yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] theimpaler747:
Should I still use set cpu with the interactive governor? Thanks

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] theimpaler747:
Oh and sorry for all the questions, but is this still a uv kernal? My phone seems to be getting hotter than before at the same frequencies.

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] Decad3nce:
The vdd's are dropped in the frequency table, so yes, it's "undervolted."

Though, according to the acpublahblah.c: vdd(voltage) can be increased to keep system stability. So I don't recommend keeping your phone at too high of a freq with an oc app.
[Hero CDMA Android Development] theimpaler747:
Ok cool thanks for the answers, and keep up the awesome work!

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] loumatrix:
Hi,

Can someone compile the original kernel for cm6 rc1 into an update.zip?

I made a nandbackup but I dont want to have to customise my phone everytime.
[Hero CDMA Android Development] incorrect:
mount -t debugfs none /sys/kernel/debug
echo "NORMALIZED_SLEEPER" > /sys/kernel/debug/sched_features
echo "NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features

maybe i'm missing something but wouldn't echo'ing NEW_FAIR_SLEEPERS overwrite NORMALIZED_SLEEPER when you pipe with a >
[Hero CDMA Android Development] Androidious:
Uncapped Kernel #7 8/18 version

Hmm, I don't know if it's just me or what, but when I installed this latest kernel, it felt like the phone wasn't as snappy as it was when I used the original 8/15 kernel you first put out for everyone when RC1 was made public. Maybe it's just me I dunno, but I tried the same build (8/18) using both different kernels, and still feel like the 8/15 #7 is snappier than 8/18

What could that be the cause of? Am I Just nutz?!?! LoL

Either way, however you slice it, you've done a grrrreat job with these kernels Decad3nce :D

Keep up tha great stuff you, Darch and the rest of the team (even the testers) do!
[Hero CDMA Android Development] The Mac:
The audio issue on 2.1 is more prevelent than i first thought. phone rings only half the time, and same with notifications. I wonder if this is related to that old audio bug from months ago...
[Hero CDMA Android Development] theimpaler747:
Just reflash the rom without wiping and it will restore the original kernal

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] nspot:
Trouble flashing wlan.ko

Hi all. I'm running the latest experimental. I've tried pushing the new file while running adbd as root, but I guess the filesystem is read-only. This may be a newb question, but how do I circumvent that issue?

EDIT: After a moment of dumbfoundedness, I realized that I could reboot into recovery and push the file.
[Hero CDMA Android Development] The Mac:
you flash it from recovery...put it in the root of the SD card...
[Hero CDMA Android Development] nspot:
Maybe I was unclear; I was referring to copying the new "wlan.ko" to my phone. Anyways, after successfully pushing the new copy, Wi-Fi is still not functioning. Any ideas?
[Hero CDMA Android Development] Rivas123:
Just flashed stable #7 hope battery drain gets fixed on Rc1 or I'm really going to have to drop back to 2.1.

Sent From A Froyo Using Hero
[Hero CDMA Android Development] The Mac:
sorry, i misunderstood...#7 stable has the new wlan.ko already in it. it fixed mine...
[Hero CDMA Android Development] The Mac:
after some empirical testing, it appears as though when something calls audio, the thread doesn't wake up in time allot. affects, audio selection, ringers, notification audio, and file playback...
[Hero CDMA Android Development] ssolomon:
I have been on CM6 for some time now and the performance has been great. I just upgraded to RC1 and added this kernel and now the phone is very laggy. Am I needing to do something else or set a config somewhere to improve performance? If not then is there a way to remove the kernel and revert to the stock RC1 kernel?
[Hero CDMA Android Development] obsanity:
I was using them :(

I don't agree with not having the lowest frequency. It saves a tone of battery when in deep sleep. My hero can stay at the same battery reading for hours just because I'm not touching it.

This makes it use the CPU much more (19Mhz to 245Mhz makes a huge difference). Please maintain all frequencies available.
[Hero CDMA Android Development] Sodikop:
shouldn't that be "C:\...\tools>adb push ramzswap.ko /system/lib/modules" ?
[Hero CDMA Android Development] fifedogg:
I disagree. My phone does just as well with 352 than it did with 245mhz on the battery life. My phone became very unstable when it ever hit 19 mhz or even 128. My phone would miss calls when I had the settings that low.
[Hero CDMA Android Development] Btaz:
I'm using 9/28 and haven't noticed any real issues. Lag from time to time, but so did my stock Hero. I'm wondering if any lag is due to most of my programs being on the SD Card, which I can live with fine. I get great scores and GPS locks quickly! Keep up the great work.
[Hero CDMA Android Development] obsanity:
Well, you can use the battery tweak or set CPU to limit it in any way you want. All I'm saying is that my phone does better battery life with it being able to drop it that low.
[Hero CDMA Android Development] infernosoft:
Overclocking crashes my phone

So I'm running the adnan@Decad3nce #11 BFS (Uncapped) and whenever I try to overclock (using setCPU or OC widget) my phone completely freezes and reboots.

Can anyone help me out with why this is happening? Do I have the wrong kernel? Thanks!

Also, I OC to 768 when this happens.
[Hero CDMA Android Development] fifedogg:
I would try and lower your mhz to around 710 and see if this takes care of it. Does this also happen with the stable kernel?

My device was having issues only when i was using Setcpu so I stopped using it. I now use Overclock Widget without issues.
[Hero CDMA Android Development] roadster92:
Been using bfs #11 for 3 days, gps sticking issue still there when using navigation, i noticed this release has lags overall compared to previous release. Other than that everything is fine. Thanks
[Hero CDMA Android Development] Vandelay007:
Are you using setcpu in your setup? If so, was having a similar problem till I changed it from on demand to interactive - so I thought I would pass that info along in case it helps someone...
[Hero CDMA Android Development] Sodikop:
Try the GPS Status work-around for that.

Download "GPS Status" from the market and under Settings>GPS & Sensors>Manage A-GPS State, "Reset" and then "Download". This will reset your internal sensor and then download GPS locate information.

When you first download and run the program it now tries to download the data as well. Though going through the above steps should ensure it "sticks".

This fixed my issues and I now get GPS locks within a few seconds. Also seems to be more accurate then stock was "back-in-the-day".
[Hero CDMA Android Development] theimpaler747:
+1 interactive should NOT be used with any BFS kernels.
[Hero CDMA Android Development] infernosoft:
710 works great! Is that as far up as I can go, you think? And I never tried it with the stable kernel, so I'm not sure.
[Hero CDMA Android Development] roadster92:
I have been using gps status for a long time, i am not having lock problem, the problem is during navigation gps did not update simutanously. During navigation it will stuck at one position for 2 to minutes then update after that. This happen again today during my one hour driving (before driving and using nav, i did gps reset and download agps data, i also have gps status download new data daily)
[Hero CDMA Android Development] theimpaler747:
Most likely... some phones just won't handle higher.
[Hero CDMA Android Development] roadster92:
Nope, i dont use any oc widget and yes i am using ondemand governor.
[Hero CDMA Android Development] fifedogg:
Why is that? My device seems to have less lag when I use interactive.
[Hero CDMA Android Development] theimpaler747:
It's the way that BFS uses and kills off background applications I believe... Interactive may make BFS slower and less able to do that.
[Hero CDMA Android Development] uf20wop:
i use overclock widget

should i switch to setcpu? and if so, what setting works best?
[Hero CDMA Android Development] theimpaler747:
I would do this:

Screen on: 710-691

Screen off: 354-245

Governor: On demand

Let me know if you need anything else!
[Hero CDMA Android Development] madeSICC:
Should on demand be used for screen off as well? I've been using powersave with good results. But if you play Pandora or music, when the screen shuts off it makes the music really choppy, so I've just been disabling it when I listen to anything

Froyo!.... its whats for dinner.
[Hero CDMA Android Development] theimpaler747:
I use on demand screen off with great results :D
[Hero CDMA Android Development] madeSICC:
Do you ever get music skip while the screen is off?

Froyo!.... its whats for dinner.
[Hero CDMA Android Development] ruizma:
my trackball wont light up with these kernels... help please
[Hero CDMA Android Development] madeSICC:
I wish mine wouldn't light up. I hate how bright it is.

Froyo!.... its whats for dinner.
[Hero CDMA Android Development] ruizma:
Haha, so you dont know how to fix it?
[Hero CDMA Android Development] madeSICC:
Haha no I don't. Sorry for my point less post. But there have been a few people with that same issue post in here. Check back a few pages and you might find the answer.

Froyo!.... its whats for dinner.
[Hero CDMA Android Development] ruizma:
Searched forums, rebooted.... nothing..... also pinch to zoom drags incredibly.... is that normal??? using Fresh 2.4.0...
[Hero CDMA Android Development] someonenewhere:
these kernells suck ass! they've made my phone slugish..
[Hero CDMA Android Development] Decad3nce:
Cool story bro. That sucks. Move along.
[Hero CDMA Android Development] someonenewhere:
dude...I'm not trying to be an ass or anything....but they eat up too much memory ....
[Hero CDMA Android Development] dirkyd3rk:
damn dude that's kinda harsh, u got alot of nerve bro id like to see you start a thread and cook a kernel that actually boots but if my guess is right u prolly cant since ur posting on here flaming someones work *kids say the darndest things* :-)

Sent from my HERO200 using the XDA mobile application powered by Tapatalk
[Hero CDMA Android Development] someonenewhere:
wasn't trying to be harsh, just fed up that i can't fix my problem....i appreciates every dev's work from theme devs to kernel devs......

if I had the time to learn how to cook a kernel I would, but I dont.
[Hero CDMA Android Development] METHOD1911:
That's so funny Dec lol
[Hero CDMA Android Development] brokentoaster24:
Hahahahaha
[Hero CDMA Android Development] CrashV2010:
Go ghetto somewhere else..... READ< SEARCH < OH< YOU FINDS WHATS YOU WANT, I talk like this.....

EDIT : NOTS !!!!
[Hero CDMA Android Development] Captainkrtek:
Keep it clean in here guys, everybody has an opinion, doesn't mean you have to share it
[Hero CDMA Android Development] Decad3nce:
Grab the lights.c from CM6 in /system/lib/hw/ and then push it to the same place in Fresh 2.4.0

Pinch to zoom shouldn't lag. Get me a logcat/dmesg/kmsg while recreating the problem. Also depends on how you have everything set up.
[Hero CDMA Android Development] Decad3nce:
GPS is 'jumpy' with BFS because, well, this is a hacked together BFS that's patched in since there's no official patch from ck for .29.

I've tried numerous things, and this is about as close as 'stable' as I can get it with GPS.

Reasons you may end up low on RAM:

You're running JIT, turn it off. (The dalvikvm isn't optimized for our device, and turning on JIT just emphasizes the problems and only gives gain at the beginning of use, bogging down to an absolute crawl towards longer uptime)

You have a lot of widgets, they hog RAM consistently

You have an app that has a memory leak(Gallery 3D had a memory leak for the longest time in CM6)

The ROM itself has a memory leak(This is possible, especially with CM nightlies)

You're using a bad i/o scheduler for the way that you USE your phone. Read up on the different i/o schedulers, find out which one suits you the best.

How can you circumvent this:

I run 11 widgets on 2 screens(win 7 phone layout) with LP+(see below) but I consistently ALWAYS have 40mb free RAM.

HOW? I watch what I install, check how my phone behaves prior/after

I use autokiller and set it to aggressive

I use the BFS kernel and keep my i/o scheduler at deadline and set my cpu governor at ondemand(I'm not bothered by slight lockscreen delay)

I recently started using compcache for extra RAM gain(my sdcard is going to hate me)

I ALWAYS use the DDMS(dalvik debug monitor service) to check for anything holding wakelock or for anything allocating too much memory whenever my phone gets sluggish.

Simply, educate yourself of WHY your phone may be acting sluggish before blaming it on a kernel I spent TOO much time on patching for no benefit other than i wanted better performance and no one else would give it to me, so I did it myself.

And please, next time, have some kind of supporting evidence that backs up "my phone is sluggish.'

IE:

DDMS showing bad allocation stemming from something in the kernel

A logcat of a failed subsys(mostly to motivate me to work on .34)

A dmesg showing spams/errors

A kernel panic/error spam shown in a kmsg(I fixed all these, multiple times)

Hopefully this will help.

EDIT:

ALSO, if you're having low memory problems on the BFS kernel, set the rr_interval higher(default is 1 on the kernel, regular BFS usually sets to 6)

Where n = number.

adb remount
adb shell
echo "n" > /proc/sys/kernel/rr_interval
[Hero CDMA Android Development] theimpaler747:
Wont that higher rr break gps?

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] chiill:
I'm getting familiar with SetCPU. When you say "Screen on" do mean the one of the "Charging/Full" or "Battery" options?
[Hero CDMA Android Development] urwrstfear:
I have been using the bfs kernels since cm6 came out. And I have always thought my phone was running great. i started trying out the new lcd density program and couldnt get it to stay without rebooting. nothing but problems. my iheart radio would always fc.

bad battery life etc. then to make a last ditch effort to try to get the lcd density to work i wiped everything and installed cm6 again but this time i didnt load the bfs kernel. now everything works great. my lcd density has been 140 for days now, havent had a fc at all. and my phone is running wAaaaaay faster. my girl had the same setup and after using my phone she wanted hers redone and s been praising how good its running with the stock kernel. so any of you peeps who have probpems on your hero using the bfs kernels try just using the cm6 how it comes it might help ya. im not dissing these kernels, it just seems some phonez dont like them.
[Hero CDMA Android Development] Decad3nce:
Your phone just may not be able to handle >691mhz

Regardless, I loaded LCD Density changer app thingy on my phone, set it to 140. I'll have it run for a few days and see whats up. Thanks.
[Hero CDMA Android Development] theimpaler747:
Just the main screen profile :)
[Hero CDMA Android Development] urwrstfear:
nah it always ran great with the cm and sense roms at 710 and 768. but i didnt start using the bfs kernels til cm6 stable. its wierd how everyonea phone acts different with different stuff. no 2 phones act the same it seems like.

also i found that slideit keyboard stays at 160 resolution when you change in lcd density changer. some people cant take the smaller keys with thw lower settings. ive heard others will too.
[Hero CDMA Android Development] someonenewhere:
Thanks for the support..wasn't trying to slam your work at all. I was just upset with the fact that I couldn't fix the problem at all. But with this new info you just gave me my phone came back to life and I did turn on JIT and then turned it off again, but the problem was still there.

I'm also running Autokiller and the memory just seems to leak real fast, last night it went down as far as 4mb's of memory. I only have 3-4 widgets running, so I don't think the widgets are the problem at all.
[Hero CDMA Android Development] rodcpierce:
I just changed my rr from 1 to 6, and gps is working just fine.
[Hero CDMA Android Development] theimpaler747:
Is it any faster?
[Hero CDMA Android Development] Decad3nce:
You won't see a difference right away.. you'll see it after a bit of uptime. Trust me, you're better off without it on.
[Hero CDMA Android Development] rodcpierce:
I honestly cant answer that, as im on a fresh flash. Just tried it to see if it broke the GPS or not.
[Hero CDMA Android Development] theimpaler747:
Alright cool :D
[Hero CDMA Android Development] Jon.StatiK:
I'm using the 9/28 stable kernel and I'm unable to get GPS to lock for days now. I've tried GPS Assist and it got nothing. I knew GPS was an issue for BFS kernels but stable? Tips or ideas?

Thanks
[Hero CDMA Android Development] infernosoft:
It'll sound like a pain in the ass, but this link did it for me.
[Hero CDMA Android Development] theimpaler747:
You could do the long method:

Make a nandroid

Wipe, and flash Fresh Rom 2.4.0

Boot up Fresh

Open up maps

Get a gps lock for about 2 minutes

Nandroid back to CM6, and GPS should work :)

If you try it, let me know how it goes, it's worked for everyone who's done it so far :D
[Hero CDMA Android Development] Decad3nce:
Answer
[Hero CDMA Android Development] infernosoft:
More info on this is provided in the link I just posted right above it. (Not trying to sound mean, just pointing you the original source of the article).

I just tried doing this a couple days ago. I didn't nandroid restore anything, just wiped and reinstalled cyanogenmod after using the fresh fix. I even installed Sprint Nav in cyanogenmod to see if that helps every now and then.

But according to the forum link, the problem is solved after updating your PRL.

Good luck!
[Hero CDMA Android Development] Jon.StatiK:
Hahaha

Thanks Decad3nce, seriously. I know search could have worked but searching for "gps" in this thread seems like an all out nightmare to me.
[Hero CDMA Android Development] theimpaler747:
I was typing as you posted :p And no offense taken.
[Hero CDMA Android Development] 24601:
Was having the same issue with BFS #11. I did a full wipe, then flashed the 9-30-10 (full 74) nightly, reinstalled #11, and have had reliable gps ever since. Did not have to run the GPS Status fix.
[Hero CDMA Android Development] danaff37:
The lcd density app is crap, I just changed it in build.prop to 140 and 5 rows in launcher pro, and I love it. Makes me feel like I have a new better resolution phone. And I feel like interactive runs smoother on my phone even with bfs. I tried changing it back to on demand for a couple of days, and went back. Auto killer on optimum. 5 screens, tons of widgets, no lag or issue. And a long as I don't run a lwp, even the 3d drawer works smooth.
[Hero CDMA Android Development] urwrstfear:
I love our phones at 140.
[Hero CDMA Android Development] theimpaler747:
I know, I use 140 and it's really great, feels like a new phone :)
[Hero CDMA Android Development] madeSICC:
When I changed the density to 140 my phone got really laggy. Ran a quadrant score and it was down to 402. Set it back to stock and uninstalled and it went back up to 450s. My phone didn't like LCD density. But it was nice being able to fit all those apps on one screen without being squished

Froyo!.... its whats for dinner.
[Hero CDMA Android Development] theimpaler747:
That's odd that speed would decrease.... perhaps it was your graphics quadrant score went down?
[Hero CDMA Android Development] urwrstfear:
Ya I never saw any decrease in speed at all using different densities.
[Hero CDMA Android Development] urwrstfear:
Also there is a thread for the LCD density app in the aps and theme section. The dev is really good about helping with any problems you have.
[Hero CDMA Android Development] LifeInTheGrey:
Well done on the LCD changer tip. I was running quadrant scores of exactly 412 (on the last four occasions, very weird), and after changing LCD density to 140 it jumped to 425. More importantly, the phone feels smoother and the spacing more appropriate. I only have the hero for another month, but all this goodness is making it hard to say goodbye ...
[Hero CDMA Android Development] theimpaler747:
I know, I may upgrade to the evo as well, but the hero has just progressed so much!
[Hero CDMA Android Development] Rivas123:
I was just talking about this to my friends. I might stick with the Hero for a bit longer. Idk about the whole other year on the contract but who knows. I've fallin love with this phone all over again.
[Hero CDMA Android Development] theimpaler747:
I know, the hero has grown so much thanks to this community!!!
[Hero CDMA Android Development] Sodikop:
#12 BFS

Ramzswap built-in <----THIS :D

/\.....Nice, just in time for my new SD card :)

Thanks Deca! You Rock!
[Hero CDMA Android Development] theimpaler747:
I see that, very cool!!! Great work deca! :D
[Hero CDMA Android Development] t12icky0:
ive noticed(and i have done this in 5 reboots)...my ADW launcher Force closes after reboot once i click the Menu button in the middle. It only shows like 4 apps(all 5 times) then shows Force close. i force close it and then it loads back up like normal. Phone is also VERY VERY slow loading up compared to your other kernels. it took autostart root over 1 minute after restart to get permission compared to like 10-15 seconds compared to the other kernels also.

GPS did lock on pretty good this time also..not sure if its because right before i flashed i did the agps download data or if this kernel just kicked ass for GPS but i got a lock within about 3 seconds(a huge improvement). i was usually getting a lock around 2-5 minutes with the other kernels without the agps data download.

Im using the newest stable #6
[Hero CDMA Android Development] madeSICC:
Just flashed uncapped #12, Upon the first boot none of my apps on my sd loaded and when i selected one of them it caused adw to forceclose, after it restarted it loaded everything up fine and its running really smooth.
[Hero CDMA Android Development] Decad3nce:
I'm running the same kernel, wipe dalvik. It hasn't been slower for me at all. :/

Wipe dalvik.
[Hero CDMA Android Development] chefthomas99:
How do you make it to be 140?
[Hero CDMA Android Development] MrSpradlen:
Noob question, what is dalvik and how do u wipe it?
[Hero CDMA Android Development] theimpaler747:
Edit your build.prop with root explorer, change the 160 value to 140 :D
[Hero CDMA Android Development] chefthomas99:
Worked perfectly thank you!
[Hero CDMA Android Development] riggsandroid:
depends on your recovery
[Hero CDMA Android Development] stayclean:
Changing the density can, and will, change/mess up some app icons (such as NYTimes, rom manager, some others), so watch out.
[Hero CDMA Android Development] rhotondm:
When changing the density is it only recommended for the bfs kernels? I went back to the stable ones so I can have more reliable GPS for navigation. Is there any other settings that need to be changed once u change the density?

Sent from my Hero running CM6 Froyo.
[Hero CDMA Android Development] theimpaler747:
You can do it with either kernel :D
[Hero CDMA Android Development] halrulez:
If you mind. How do I do this ¿ What do I use to edit it¿ Can I do this from my phone or do I have to do it from my pc. I see 3 lines that say 160 what ones do I ned to change?

Sent from my FroYoed Hero
[Hero CDMA Android Development] theimpaler747:
Change the bottom 2 from 160 to 140
[Hero CDMA Android Development] halrulez:
Thanks bro gunna try now

Sent from my FroYoed Hero
[Hero CDMA Android Development] theimpaler747:
No problem, let me know how it goes.