I've been hard at work on another kernel for ally.
Features:
Patched kernel from 2.6.29 to 2.6.29.6 as thats the last .29 kernel.
Android staging drivers backported from kernel .32
Backported lowmemorykiller from kernel .32
Backport of idle time code from kernel .34
Overclocked to max of 787mhz. For safety set at 600max on boot. Change with setcpu
Added deadline I/O scheduler as an option. Anticipatory is still default.
Added Interactive gov as option. Enable with setcpu. Its like a better ondemand
Ext 3 & Ext 4 supported
Ipv6 supported
Netfilter & xtables
Tun.ko for open vpn
Swap enabled
Many other changes see github.
Major changes should be:
More Battery Life
The backport of idle code from .34 is by Erasmux, it helps TREMENDOUSLY on how your phone behaves during 'idle'.
Better RAM handling
The backport of lowmemorykiller from .32 by Decad3nce, helps with the way RAM overall is handled on the device. Absolutely no more 'lost memory' situations or hiccups.
Interactive gov Advantages: + significantly more responsive to ramp cpu up when required (UI interaction) + more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu load sampling. + higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
Things to note:
Packaged in anykernel so it will not overwrite your ramdisk apps2sd people.
If using a modified ramdisk please make sure your governor is not set on performance as your battery will suffer tremendously. Script in stock ramdisk changes gov to ondemand from performance (performance is for faster booting) at each boot so check if yours is modified.
On boot/reboot it may be sluggish for 1st 30-45 seconds as this is the lowmemorykiller working to free ram. After initial 30 seconds it will be much more responsive.
Taskillers are NOT recommended as this backported lowmem killer is much more effective.
Overclocking Notes:
Not all phones can OC and can handle the same speeds. Your phone is unique. Some can go up to 787mhz stable some can only do 748mhz and some can't at all.
Overclocking must be done with setcpu. After each boot/reboot the max is set to 600mhz to keep you from getting in a boot loop with an unstable speed for your device. To change it after reboot you must move the slider in setcpu to get the overclock freq to set above 600mhz.
You can use this with my Jit libs use the Turbo4 no kernel one from Here for the jit stuff without the old kernel.
To use flash with clockwork or my recovery and wipe dalvik-cache and cache.
Thus far, Raptor seems to perform better without Turbo and OCing. Wonder if this would be different. Anyone try it yet?
Overclocking is optional. If you don't set overclocking with setcpu it stays at stock speed. The jit libs are the single most effective performance tweak available. Aside from overclocking the features/changes above are what this kernel gives you vs stock.
On another note, using memory booster I noticed that my available memory using turbo4 averages around 37%, this new kernel averages around 27%. Linpack scores are the same, but turbo4 scores much higher with quadrant. Just an observation for anyone who is wondering if they should stick with turbo4 or flash this one.
Anyone else have Wifi issues with this Kernel? My Wifi refuses to turn on with a message "Unable to start Wifi".
I flashed this over Velocity 0.3 (which was already running the Turbo4 kernel), then reapplied Turbo4 (no kernel) for Velocity, just in case it needed it again.
Poked around in the Turbo4 for Velocity zip and noticed it had a wifi module that wasn't in the default (non-velocity) Turbo4 zip. It must have been incompatible over this kernel.
After reflashing the new kernel and Turbo4 (with the non-velocity zip) wifi seems to be working fine.
Device(s): Samsung Galaxy Nexus, Asus Nexus 7, Motorola Droid 2 (previous: HTC Thunderbolt, Motorola Droid, LG
Carrier: Not Provided
Thanks: 158
Thanked 117 Times in 69 Posts
Quote:
Originally Posted by motorsport226
No problem man.
On another note, using memory booster I noticed that my available memory using turbo4 averages around 37%, this new kernel averages around 27%. Linpack scores are the same, but turbo4 scores much higher with quadrant. Just an observation for anyone who is wondering if they should stick with turbo4 or flash this one.
Turbo4 is the jit library, so you can have both. I'm not sure what you're comparing?
Device(s): Samsung Galaxy Nexus, Asus Nexus 7, Motorola Droid 2 (previous: HTC Thunderbolt, Motorola Droid, LG
Carrier: Not Provided
Thanks: 158
Thanked 117 Times in 69 Posts
As far as speed, Linpack hasn't changed but my Quadrant score went from about 475 to 500 from the old overclock kernel. Constants: 448MHz Performance, JIT libraries installed.
Quote:
Originally Posted by motorsport226
Yeah nevermind, misread the instructions.
I can seem to get the turbo4 no kernel version to download from mediafire. Anyone know anyplace else I can find it?
Device(s): Samsung Galaxy Nexus, Asus Nexus 7, Motorola Droid 2 (previous: HTC Thunderbolt, Motorola Droid, LG
Carrier: Not Provided
Thanks: 158
Thanked 117 Times in 69 Posts
Quote:
Originally Posted by motorsport226
Awesome, thanks man.
No problem. Of course, there's a lot more at play here than just speed. Responsiveness (that nice new governor from Cyanogen), and battery life (that new idler) should see boosts too. I'm excited. Thanks, drellisdee.
No problem. Of course, there's a lot more at play here than just speed. Responsiveness (that nice new governor from Cyanogen), and battery life (that new idler) should see boosts too. I'm excited. Thanks, drellisdee.
Agreed, the responsiveness boost was instantly noticeable and I'm sure battery life will improve as well. Thanks drell!
What version of .3 would I want to install using this kernel. The normal download link with the Gridlock kernel or one of these that are listed on the Velocity page:
I got a question bout over clocking... I installed the kernel and then used overclockwidget. I have it set on 729 and i keep getting kernel panic.. could this be from using the widget and not setcpu?
__________________
Live life to the fullest and never regret the past... its not worth it
What version of .3 would I want to install using this kernel. The normal download link with the Gridlock kernel or one of these that are listed on the Velocity page:
I got a question bout over clocking... I installed the kernel and then used overclockwidget. I have it set on 729 and i keep getting kernel panic.. could this be from using the widget and not setcpu?
Possible but unlikely. It's most likely that your phone cannot handle the overclock.
Overclocking is unique to each phone. Some can handle 787 with no problems, some cant OC at all.
But it's worth giving setcpu a shot, if it doesn't work you can always get a refund.
But it's worth giving setcpu a shot, if it doesn't work you can always get a refund.
That is a gooood idea... Thanks! I had it set at 729 for a few hours and it seemed to work good there but i still dont seem to be gettin any performance boost.
That is a gooood idea... Thanks! I had it set at 729 for a few hours and it seemed to work good there but i still dont seem to be gettin any performance boost.
On another note, using memory booster I noticed that my available memory using turbo4 averages around 37%, this new kernel averages around 27%. Linpack scores are the same, but turbo4 scores much higher with quadrant. Just an observation for anyone who is wondering if they should stick with turbo4 or flash this one.
In my turbo4 kernel i had a modified ramdisk that had the low mem killer levels upped very much from stock around 60mb floor I believe. Its done in init.rc btw. This one had no ramdisk so you have it at stock empty app floor of 24mb as per your ramdisk. Thats how well its holding its lower limit with .32 kernels low mem killer. And as to performance turbo4 pushed the ally all the way to its current limit. I do agree performance is a little down in quadrant but this kernel addresses some other things the ally needed like battery and memory usage while still having a noticable gain from stock performance to more round out the device in other areas too.
Last edited by getitnowmarketing; October 25th, 2010 at 11:35 PM.
It is doing better and still trying out the different scaling options. If i clock it over 729 it panics within minutes. Seems to be helping the battery some. Any suggestions on what kind of profiles/governors to set?
Best setup so far was Max 729 Min 320 with ondemand. Ive tried some of the other scaling options but havent figured out what to do with the advance settings. It always seems to work for awhile but then i will notice lag eventually. What has been working for everyone? Just curious to see how other people are tweaking and what works and doesnt.... Thanks for helping a nooob.
i flashed the new kernel but forgot to wipe both dalvik cache and cache. i ran the kernal all day and it seemed slower than the turbo4 adapted for velocity. would that problem be because i forgot to wipe the caches?
Device(s): Samsung Galaxy Nexus, Asus Nexus 7, Motorola Droid 2 (previous: HTC Thunderbolt, Motorola Droid, LG
Carrier: Not Provided
Thanks: 158
Thanked 117 Times in 69 Posts
Quote:
Originally Posted by dumbteentarget
i flashed the new kernel but forgot to wipe both dalvik cache and cache. i ran the kernal all day and it seemed slower than the turbo4 adapted for velocity. would that problem be because i forgot to wipe the caches?
You can always go back to recovery and wipe them and find out...
You can always go back to recovery and wipe them and find out...
well i already put the other kernel back on so i thot id ask on here instead of going through the trouble again but it seems like ill just do that and find out.
In my turbo4 kernel i had a modified ramdisk that had the low mem killer levels upped very much from stock around 60mb floor I believe. Its done in init.rc btw. This one had no ramdisk so you have it at stock empty app floor of 27mb as per your ramdisk. Thats how well its holding its lower limit with .32 kernels low mem killer. And as to performance turbo4 pushed the ally all the way to its current limit. I do agree performance is a little down in quadrant but this kernel addresses some other things the ally needed like battery and memory usage while still having a noticable gain from stock performance to more round out the device in other areas too.
I completely agree. Responsiveness is definitely up, and I have noticed an increase in battery life as well; and I was already getting around 40 hours average on a full charge with moderate to heavy use.
Also, the interactive governor in setcpu is performing very well, it's doing everything that you said it would, most notably being the the increased ui responsiveness.
Another amazing job drell, I appreciate all of your hard work, donation will be sent soon.
It is doing better and still trying out the different scaling options. If i clock it over 729 it panics within minutes. Seems to be helping the battery some. Any suggestions on what kind of profiles/governors to set?
Best setup so far was Max 729 Min 320 with ondemand. Ive tried some of the other scaling options but havent figured out what to do with the advance settings. It always seems to work for awhile but then i will notice lag eventually. What has been working for everyone? Just curious to see how other people are tweaking and what works and doesnt.... Thanks for helping a nooob.
I've been using the interactive gov that's new for this kernel. Haven't tweaked any advanced settings yet, just kinda been letting it do its own thing and see how it goes for the first few days.
I did notice a performance increase switching from ondemand to interactive, even with a stable 787oc, give it a shot and see if it calms things down at all. And if not then stick with 729 on interactive. I mean, it still linpacks around what, low-mid 7's on 729? Not too shabby at all.
I completely agree. Responsiveness is definitely up, and I have noticed an increase in battery life as well; and I was already getting around 40 hours average on a full charge with moderate to heavy use.
Also, the interactive governor in setcpu is performing very well, it's doing everything that you said it would, most notably being the the increased ui responsiveness.
Another amazing job drell, I appreciate all of your hard work, donation will be sent soon.
how are you getting 40 hours???? we are talking about the same phone right? LG ally? im lucky if i get 15.
how are you getting 40 hours???? we are talking about the same phone right? LG ally? im lucky if i get 15.
lol I get 8 with heavy use and 15 with moderate. Unless he has the extended battery and dosen't use GPS, E-mail, Maps, texting, talking, chatting, then I don't know how that is possible.
how are you getting 40 hours???? we are talking about the same phone right? LG ally? im lucky if i get 15.
Yep, my longest time since unplugged was around 52 hours.
You probably have the 50% bug. Go to settings>about phone>battery use>cell standby. Check what the time without a signal percentage is, if it's over 50% then its the bug.
What this means is that your phone is searching for a signal even when you already have one. This wreaks havoc on your battery.
There is a quick fix that has worked well for me: turn airplane mode on for a few minutes and turn it back off, see if the percentage starts to go down. If not, turn on airplane mode, reboot the phone and turn airplane mode off. It might take a couple tries but its never failed to work for me.
Yep, my longest time since unplugged was around 52 hours.
You probably have the 50% bug. Go to settings>about phone>battery use>cell standby. Check what the time without a signal percentage is, if it's over 50% then its the bug.
What this means is that your phone is searching for a signal even when you already have one. This wreaks havoc on your battery.
There is a quick fix that has worked well for me: turn airplane mode on for a few minutes and turn it back off, see if the percentage starts to go down. If not, turn on airplane mode, reboot the phone and turn airplane mode off. It might take a couple tries but its never failed to work for me.
Ok thanks. I'm gonna look into that right now
EDIT: I did what you said, airplane mode then restarted the phone and now its been running almost an hour and the time without a signal is around 25%. before i restarted it, it was at 85%. What is it typically at cus it seems like its just going to creep back up there. How often do u have to do the airplane mode thing to get rid of it? it doesnt seem like a one time fix.
Last edited by dumbteentarget; October 26th, 2010 at 02:06 PM.
Anyone else having a problem with the calcualtor? Using Velocity .3, Turbo 4 - no kernel and the kernel in this thread. I remember we had a similar problem with this before.
Anyone else having a problem with the calcualtor? Using Velocity .3, Turbo 4 - no kernel and the kernel in this thread. I remember we had a similar problem with this before.
I was having calculator problems before with velocity3 and turbo4 with kernel so I just deleted the calculator.apk file. There are other calculators u can download from the market.
Device(s): Samsung Galaxy Nexus, Asus Nexus 7, Motorola Droid 2 (previous: HTC Thunderbolt, Motorola Droid, LG
Carrier: Not Provided
Thanks: 158
Thanked 117 Times in 69 Posts
Quote:
Originally Posted by icon123
Anyone else having a problem with the calcualtor? Using Velocity .3, Turbo 4 - no kernel and the kernel in this thread. I remember we had a similar problem with this before.
Calculator works for me on vB with JIT4 (this one comes with a recompiled calculator.apk).
Device(s): LG Ally(For Testing), Droid Incredible(IncDoes Sense "Desire Z" v1.2)
Carrier: Not Provided
Thanks: 12
Thanked 9 Times in 7 Posts
ok so i changed the turbo4 ramdisk with the normal vzb app2sd and flashed the 2.6.29.6_GNM and now its working fast, no freezing. I will keep testing, if anyone knows why turbo4 ramdisk and 2.6.29.6_GNM was freezing let me know.
EDIT: I did what you said, airplane mode then restarted the phone and now its been running almost an hour and the time without a signal is around 25%. before i restarted it, it was at 85%. What is it typically at cus it seems like its just going to creep back up there. How often do u have to do the airplane mode thing to get rid of it? it doesnt seem like a one time fix.
Mine usually stays down as long as the phone is on the same boot. If my battery dies or I have to reboot for any reason it might start the bug again.
Just keep an eye on it and try the airplane trick until it sticks. Of course, if you live in an area with a bad signal then there might not be a fix.
[GPL] LG Ally Kernel 2.6.29.6_GNM_OC
