yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] Elvesofdarkness:
[KERNEL][OC]FIXED force Close on phonecall and lock on wifi tether stop

I have been using this kernel for a few days now and not one fc except one that has nothing to do with the kernel and more to do with jit. It was the xda app usually won't work to good with jit but all I get is a fc when I open sometimes then runs great. I guess I've been lucky and jit is stable enough for daily use and getting 5.3mflops on linpack. Thanks for the kernel

-------------------------------------

Sent via the XDA Tapatalk App
[Hero CDMA Android Development] Androidious:
Damn man, that's just insane!!! I cannot get my phone above 2.97 mflops for the life of me. Is there anything you think I could do to make it a lil faster?

My setup is stated in my signature area, thanks man.
[Hero CDMA Android Development] Androidious:
:confused:

That is just plain crazy! How can anyone justify spending triple the price of a piece of hardware that in like a few months, is going to be outdated by something bigger and better?!

:confused:

I just wish I had that kind of money to just use up without no regrets, LoL!
[Hero CDMA Android Development] troyboytn:
lol Even if I had that kind of money to throw out the window, I wouldnt be stupid enough to do so. Especially on hardware that is already coming apart.
[Hero CDMA Android Development] roadster92:
I was the one check the Ramdisk between 2.08.1 and 2.09.1. There are very similar (minor differences) but should not affect anythings. The only differences that I found was in this ramdisk's init.heroc.rc

This is the addition that DC 2.09.1 Ramdisk's init.heroc.rc does not have:

" # Permissions for Liblights.

chown system system /sys/class/leds/green/brightness

chown system system /sys/class/leds/green/blink

chown system system /sys/class/leds/amber/brightness

chown system system /sys/class/leds/amber/blink

chown system system /sys/class/leds/red/brightness

chown system system /sys/class/leds/red/blink

chown system system /sys/class/leds/blue/brightness

chown system system /sys/class/leds/blue/blink

chown system system /sys/class/leds/jogball-backlight/brightness

chown system system /sys/class/leds/jogball-backlight/color

chown system system /sys/class/leds/jogball-backlight/period

chown system system /sys/class/leds/button-backlight/brightness

chown system system /sys/class/leds/lcd-backlight/brightness

# enable the GPS

setprop ro.ril.def.agps.mode 2

# Power Management

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 245000

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 710400

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand

setprop ro.ril.fast.dormancy.rule 1

setprop ro.ril.fast.dormancy.timeout 2

# for enabling EVDO Data-quietcblongs

on property:persist.sys.country=us

start echofor3

service echofor3 /system/xbin/echo3

oneshot

but I don't think it is affect anythings either. I have test a fresh installation of DC 2.09.1 > go through setup > Reboot and Flash the Kernel in the first Post for DC 2.09.1. Everything is normal and work flawlessly so far. Confirmed Wifi Tether work properly (no shut down problem). Phone call FC or random FC = NONE ( I have not experienced any even using Fresh Toast Kernel # 89 with BFS ) .

However there is one issue that I encountered:

* When I flashed this kernel on top of the previous OC + 2.09.1 with everything installed, I exprienced a very slow boot up time..It's practically crawling through boot process (it's look like the phone was booting at a very low CPU clock) It took like 20 minutes or more to get completely done with booting. I suspected that because my OC widget was set to auto start at boot using the previous setting from the old OC kernel. After boot, I use OC widget and auto detect again and saved using the same setting as previous and reboot. This time it gone through less than 5 minutes.

I don't think there are any bugs in the DC ROM, I believed that for those that use the Set CPU or OC widget, they need to reset the setting to default or completely remove the apps + data before flashing this update. After that they can re-setup the SetCPU or OC widget.

:)
[Hero CDMA Android Development] BAttitude7689:
right now im running fresh 2.1.2 and kernal #89 by toast and its overclocked and always running at 710mhz and i do not use an overclock app (setCPU or overclock widget) if i flash this kernal, will it act the same way as what i have now and always run at 710mhz and not have to use an overclock app.
[Hero CDMA Android Development] urushiol:
Indeed... default is 710 :D
[Hero CDMA Android Development] markus_del_marko:
I wanna use this kernel but the lockscreen lag is a deal breaker for me! Im sorta regretting selling my evo and coming back to the hero. I never realized how slow this phone is. :(
[Hero CDMA Android Development] urushiol:
I would be interested in seeing if the AOSP synaptics driver works better with the vanilla lock, go here

http://www.4shared.com/dir/xpW1Jbuy/sharing.html

and find the vUV (not vUV2) you want download it, and see if it is better or worse. I suspect that it will be worse.
[Hero CDMA Android Development] Chrizmas:
I am running Aloysius 2.1.2 which has the vanilla lock along with the Damage Control vUV kernel and there is a very slight lag, maybe a half second or so, before allowing unlock. It's not really noticable to me and seems to be the fastest setup I have personally run so far using the vanilla lock. My wife's hero running ruu 2.1 sprint has a slight lag before allowing unlock as well. I would suggest to try the vUV or vUV2 kernel as the battery life benefits are well worth it. And if you find that you don't like it you can always restore the nandroid backup. :)
[Hero CDMA Android Development] markus_del_marko:
thanks but i may just wait for another solution then.
[Hero CDMA Android Development] Noblesse:
I'm on Fresh 2.3.3 using the vUV 2/710Mhz with no FMK. I thought my phone was fast before, when I ran Aloysius 2.1 OC & vUV 1, but this thing is Lambo quick. The dialer comes up almost instantly, no lock lag. And im only OC at 614, I don't kno bout you guys but I'm impressed. Hope it stays that way and doesn't overheat. *Knock on wood* Thanks everybody who worked on this.
[Hero CDMA Android Development] vita10gy:
Thanks for the response, I'm trying the Stock RUU. Seems ok. I think I figured out what my problem was, and it's pretty stupid. I'm using titanium to restore some things, except it looks like it had trouble setting the custom ring tone. Instead of defaulting to something when t can't find it, the phone just crashes. Just got a FC, set a ringtone to one of the stock options, and was able to get a phone call.

I'm simultaneously hoping this is the problem, and will be pissed if that's all it is. Though, I did try calling after restoring these things last night and all was fine. Problem didn't present itself until half a day later, so we'll see. (And obviously it started as a problem before anything happened with the ringtone/restoring/etc)
[Hero CDMA Android Development] vashing:
I'm running the 710 mhz kernel. I also am using setcpu to down clock based on battery percent, if that matters.
[Hero CDMA Android Development] Outer Marker:
Some phones don't take an undervolt very well. Every chip is different as I know from years of PC overclocking. In fact, undervolting affects stability more than overvolting to an extent.

With that said, the vUV 2 kernels work for me on nfinite's stock ROM, but I can only give lukewarm feedback at this point. I frequently conference call with my phone and initiating 3-ways calls is ridiculous. Half the time I drop the first call, and when I have to dial the ext of the second party, it takes 9-10 seconds for each digit to register!

Don't even get me started on receiving a calendar reminder from Exchange active sync while on a phone call. When that happens, I get such a pop sound in my ear that I almost **** myself the first time it happened. I've tried the non UV kernels and they all work great, so I know it has to be something with the undervolt and my phone in particular.

Any chance of a standard voltage kernels at 710 or 768 with HTC synaptics?
[Hero CDMA Android Development] fifedogg:
So far the vUV 2 kernel is working great for me. I noticed when I play homerun battle 3d my phone doesnt get quite as hot as it did before. I've only been using the kernel for half a day but so far so good. I also noticed it doesnt get quite as hot when on a phone call...
[Hero CDMA Android Development] urushiol:
the v4 kernels are for you. I need to rezip them in working FMK and non-FMK versions. but they should function the way they are.
[Hero CDMA Android Development] Outer Marker:
Perfect. I thought to try the V4 ones, but this statement scared me:

**BUGS FOUND IN FREE MEMORY TWEAK VERSION OF V4, RECOMMEND YOU USE vUV KERNEL INSTEAD**

Frankly, I'm not bothered about the FMT, I found the 691 V4 version with no FMT to be simply perfect. Then I got greedy and wanted 710 or 768. Maybe I'll just wait for your zips. Thanks, you're very kind!
[Hero CDMA Android Development] foolforfood:
The 691. 710, and 768 versions only relate to their stock speed, but if you install something like Overclock Widget (I prefer it over SetCPU) Then you can overclock it as you desire, it works great. Hope this helps you.
[Hero CDMA Android Development] Outer Marker:
Totally forgot about that *minor* detail. I thank you, kind sir!
[Hero CDMA Android Development] foolforfood:
My pleasure, as much help as I've gotten on these forums, I hope I can offer a little back now and again.
[Hero CDMA Android Development] Chrizmas:
Just upgraded to vUV2 on Aloysius 2.1.2 OC and can report I now have zero lag on unlock screen. Could just be my imagination but the phone seems to switch between screens faster as well, although the benchmarks are identical to original vUV.

Huge thanks to all of those involved with making this kernel possible!
[Hero CDMA Android Development] fwhite42:
Using the vUV2 w/FM on Fresh 2.3.3 with overclock widget and so far everything seems to be going fine. Not enough utilization to know for sure yet on temps, but overall performance seems solid.

I know this isn't the thread for overclocking helper app (oc widget or setcpu) discussion, so if someone with more experience with those tools than me (which would be just about anyone who knows much about them) would like to PM me with some tips and/or preferred settings guidance, I'd very much appreciate it. Thanks!
[Hero CDMA Android Development] markus_del_marko:
im running the rooted stock sprint rom and i don't have sense installed , what is the best kernel to use that won't cause lockscreen lag?
[Hero CDMA Android Development] urushiol:
To honest vUV 2 should be the best, you could try one of the vUV one that I linked you too earlier.

vUV 2 and v4 have the same touch screen driver. It will only work with a HTC rom, which you are running.

vUV has ( if i understand correctly), a hacked version of the HTC touch screen driver, so that it would receive touch input on an AOSP rom, not build off an HTC rom.

I loaded vanilla lock and ADW launcher on my phone (I'm using honeybun.v2, build off the sprint 2.1 RUU) and using the vUV 2 kernel i have virtually 0 lockscreen lag, and 0 screen change lag.

Why not just press Menu+menu to unlock? then it doesn't mater if theres lockscreen lag =).
[Hero CDMA Android Development] chrish03:
Thanks for making this. It does noticeably speed up the phone, no more lag on the lockscreen or dialer etc.... One problem I have is it seems there is a memory leak of some sort. I am using Fresh 2.33 and when the phone boots up it has around 50-60 mb of free ram. Within 20 minutes or so of using the phone it drops itself into the low teens in mb of available ram and starts to lock up. I was using the previous 710 undervolt kernal without any issues except for a little lag sometimes. Any suggestions?
[Hero CDMA Android Development] urushiol:
Which version are you using for fresh, there are 6 different vUV 2 flashables compatible with fresh. I need to know the exact one your using because its possible I typoed in the freememkiller settings on one of the zips.

Did you use the ModuleRemover.zip first? If you didn't, the go into recovery, run the remover, then relfash the kernel.

Are you you using autokiller?
[Hero CDMA Android Development] chrish03:
Yes I used the Module remover first. The zip I flashed for fresh was Standard_vUV2_710.zip.
[Hero CDMA Android Development] urushiol:
I'll bust open that one and see if I typoed. You might be on the edge of being stable, perhaps getting a hung application that starts eating memory.

Try the standard 691 with freememkiller tweak, or 710 with freememkiller tweak in the meantime =)
[Hero CDMA Android Development] chrish03:
Ok, I reflashed using the 710 with memory tweak and it started to do the same thing again. I forgot to answer the other question, I am using autokiller set to aggressive.
[Hero CDMA Android Development] dopedroid:
Just an update from my earlier post a couple pages ago, i no longer get the random lockups/hanging on my home screens. I think it was due to the fact that i was running launcherpro and have the SenseUI kernel. Such a rookie mistake. Phone is running beautifully now. I think I'm finally satisfied since I'm not eligible for an upgrade anytime soon.

i did clock it and its only at 2.8 mflops though.

again, great job on this one. phone is definitely flying now and i havent had any random reboots either. :)
[Hero CDMA Android Development] gizmosears:
I had the same problems with the new kernel with memory going to the teens and slowing. Went back to the last kernel available and is back to having 70-75mb available.
[Hero CDMA Android Development] darchstar:
thats probably an issue with the new lowmemkiller mods i made into the kernel. if u guys can just get me a general logcat and dmesg, i could probably help you all out
[Hero CDMA Android Development] c00ller:
Eh? Why does it matter what launcher you're using as long as the ROM is Sense based?

So what did you do to make your phone run beautifully? Did you stop using LauncherPro? Or did you switch to a different kernel?
[Hero CDMA Android Development] urushiol:
Im going to change the thread name as I can see how this is causing confusion. You can use this kernel with whatever launcher you want, and it shouldn't cause a problem. But the ones with htc synaptics driver have to be used on HTC based rom, not AOSP based rom.
[Hero CDMA Android Development] dopedroid:
i might have worded that kind of weirdly myself. the ROM I'm on is sense based so i chose the htc synaptics driver kernel. that itself fixed my freezing issues. i genuinely thought it was because i was using a different launcher. now switching back to the stock launcher, i have had no issues besides the phone getting pretty warm during web browsing/light to medium use. but i can live with that.
[Hero CDMA Android Development] chrish03:
I'm kind of a noob. How do I get a logcat or dmesg? Thanks for the offer of help.
[Hero CDMA Android Development] Noblesse:
Is Autokiller gonna cause a lag? I was using the Spare parts mod with AK, using the first 710 vUV/No FMK, When I flashed the new UV today, I posted it was fast but now it's kinda laggy. I wonder what would cause it to lock up, I doubt it's my SetCPU profiles. Any ideas? I dont wanna play Russian Roulette with Kernels.
[Hero CDMA Android Development] cephraim:
I had switched to Standard_uV2_710_M on nfinite (after running the moduleremover) and thought it was great. But, then things slowed down a lot. Switched back to V4_710 and everything is great again.

Think I should try the Standard_uv2_710 without mem management?
[Hero CDMA Android Development] MrGreg:
I was using vUV2 with Fresh 2.3.3, but I feel like it isn't running as well...had a few reboots, randomly got stuck in a boot loop. Are you going to repackage Fresh21_v4_710_M.zip with fixes to the ramdisk and freememkiller tweak, or should I just continue using it? Thanks a million!
[Hero CDMA Android Development] urushiol:
I am going to, it will be a few days till i get to it, lot's of stuff going on in my life atm.

@Darchstar, is there anyway I can get the current vUV2 kernel to work properly via settings in the ramdisk? It's weird because everyone I know using it on Nfinitefx45 stock rom, zenheroXF, fresh, etc has reported problems, while I'm using honeybun which uses the gumbo.sh to make changes to the freememkiller settings at boot and I have experienced 0 problems, no memory leaks, nothing. I have been using it since you posted the link to the zImage too, made tons of calls, web browsing, texting, gps , wifi, I have put it through its paces.

Let me know!
[Hero CDMA Android Development] BlaqkAudio:
I flashed vUV2 710 w/ freemem and I'm having 0 problems. Works great
[Hero CDMA Android Development] fczeuner:
I'm using the old 710m v4. Its butter smooth. The new uv kernels were too laggy for me .
[Hero CDMA Android Development] Sodikop:
This may be a stupid question but I ran into a similar problem, did you run the module-remover ZIP first? I forgot to and just flashed the new kernel, had boot loops and FC's galore. Ran the module remover and reflashed, good as new...24 hours and counting :cool:
[Hero CDMA Android Development] jrodrigu07:
Also wanted to report in on the new uv2 w/ mem kernel:

Rom: Fresh 2.3.3

Kernel: 710 with memtest

SetCPU: Yes (profiles also)

Result: Starts up fine and stays nice and fast for a couple of hours (usually 2), after that, however, it'll bring the OS to a standstill (cant test further as it'll take 2 minutes between button presses before it registers)

Went back the original UV kernel - zero issues (outside of the boot screen lag). Will try 710 regular (no mem) and see how it does, later
[Hero CDMA Android Development] sh4nk:
Im currently running Aloyisus 2.1 LWP/OC, but am experiencing a ton of lag with the OC. So, I'm going to flash the non-OC version. I am curious if one of the versions of this kernel will work with the ROM, as I would like to be able to OC it a little bit, and be able to use a built in auto killer. Is there a version of this kernel that will work for me?
[Hero CDMA Android Development] chrish03:
Use the v4 kernel for damage. I switched from Fresh back to Aloysius, and am using that kernel with no issues.
[Hero CDMA Android Development] sh4nk:
Thanks for the info! :-)
[Hero CDMA Android Development] Visionikz03:
I had an "android.process.phone" FC on the V4 Damage Control 710mHz kernel this evening... funny how these kernels were supposed to fix that lol... if someone can tell me how to run a logcat id be happy to post wat happened when it FC'd?
[Hero CDMA Android Development] MrGreg:
I didn't run the module remover, but I did a full wipe and re-flash...
[Hero CDMA Android Development] elessarelfstar:
What ROM are you using? I was using Fresh 2.3.3 and tried both uv2 691 (with and without mem tweak) and it would run incredible for a couple of hours then grind to a halt. both times I used to the remover zip. I'm now using HuneyBun and it works well, but I'm not near as happy with it as I was with Fresh.

So, are you using HoneyBun, or one of the other ones that everyone is having so much trouble with?
[Hero CDMA Android Development] markus_del_marko:
ive tried every version of this kernel and i cannot for the life of me get rid of the annoying lockscreen lag. :(
[Hero CDMA Android Development] Visionikz03:
It comes with the territory... they state the issue the lock screen lag in the change log...
[Hero CDMA Android Development] bimmer95:
Damn, UV and UV2 both break tun.ko from this thread, http://xdaforums.com/showthread.php?t=708627&highlight=tun.ko It still works with v4, but that doesn't seems to run as smooth as UV2. Anyway to fix that? I need tun.ko for VPNing in to my ASAs at the office.
[Hero CDMA Android Development] urushiol:
does darchdroid 2.7 or the froyo RC0/RC1 have a tun.ko? if so i bet it will work.
[Hero CDMA Android Development] bimmer95:
Well I tried a Froyo based tun.ko and it wouldn't work either. Looks like a new tun.ko has to be compiled from the UV2 kernel source code, not sure where to get that though.
[Hero CDMA Android Development] elessarelfstar:
I know that some have had major issues with UV2 with Fresh and some other Roms. I was too, in terms of it running great and then slowing to a crawl after a couple of hours. After trying HoneyBun and the UV2 kernel for it (worked well) I decided to see if HoneyBun would work on Fresh 2.3.3.

I flashed last night at abotu 12am and its 11:18am right now. So far after 11 hours it's still running well. If it ends up having the same problems I'll update. But so far flashing the Huneybun UV2 on Fresh 2.3.3 seems to be working.

Update: 36hrs and looking good.
[Hero CDMA Android Development] jrodrigu07:
good tip.... so far, so good
[Hero CDMA Android Development] primerib:
Does thefree memory tweak use more battery than one with out it. Specifically the under volted kernels?
[Hero CDMA Android Development] bycoo222:
Can there be a 537 version please I can't boot on that high a clock please I need a 537 version
[Hero CDMA Android Development] secbrad:
I have been using the 710 freemem for more than two days on 2.3.3 and it has been running awesome. I did have a problem with it though when I tried to OC it with SetCPU. It worked good for a while and then go to garbage so I removed it, ran the mod remover again, reflashed the same kernel and it has been running awesome again for about a day and a half since.
[Hero CDMA Android Development] Outer Marker:
I've been running some different overclock kernels and now my testing is complete. Due to all my testing, I need to start fresh with nfinite's stock ROM. Do I need to use the module remover before I flash back to a stock kernel?

Also, when using the module remover, I've been flashing the remover, then the ROM.zip. I asume that's the procedure, or do I need to reboot after flashing the module remover?
[Hero CDMA Android Development] azr6:
So maybe it is just me but I have been running this now for a few days. Everything is real fast (keyboard lag still sucks ass on this phone) but I don't know if it is just me or not but the battery life does not seem to be better. It actually seems to die much quicker and this is with light use. (basically just sending a fex texts).
[Hero CDMA Android Development] fwhite42:
If this helps the DEVs at all, I too was having problems when running OC Widget with different screen on/screen off settings, but now that I'm running in "simple" mode with only one option (min 245760, max 768000) I'm having no problems at all.

Obviously, would prefer to do separate ranges for screen on and screen off, but everything works in this mode and I've got no noticeable lag at any point (waking up, unlocking, after prolonged use, etc.).

Info in my sig is accurate for what ROM/Kernel combination.
[Hero CDMA Android Development] chromiumleaf:
You might be having problems with your phone not sleeping. In Settings->About Phone->Battery look and see what the Up time vs. Awake time is. If these numbers are the same, then your phone is not sleeping and that's what could be making your battery drain quicker.
[Hero CDMA Android Development] azr6:
Ya I checked that first thing and it looks like the phone is failing asleep ok.
[Hero CDMA Android Development] chromiumleaf:
Ok, then look in your Battery usage information. First check Settings->About Phone->Battery->Battery usage and see if any of those values that come up have a really high percentage.

Then type in *#*#4636#*#* and check Battery usage information there too. Browse through all those menus and see if any of the values in there are really really high percentages.

This will hopefully point to what is using up so much battery.

If everything there looks normal (in other words, no huge percentages or values on anything), then maybe just try re-flashing another kernel or whole ROM altogether. I remember once I had sleep/battery issues and all I did was re-flash the same ROM and it went away for me.