Related
People asked why I don't have dev threads here, so here's one. I'm friendly, just try to read the dev chatter and tweak stuff.
Quick and dirty version of a kernel 100% working with setcpu for throttling. No overclock yet.
Also has MemKiller configured fairly aggressively.
More info:
http://forum.xda-developers.com/showthread.php?t=622666
or full details:
http://developer.android.com/index.html?utm_campaign=en&utm_source=en-ha-na-us-bk&utm_medium=ha
New info:
I've created a ROM Cooker dev pack. This includes the full boot image from Gumbo 1.5c (assembled as boot.img and the unassembled individual files), the kernel zImage and wlan.ko, example scripts and the tools and instructions to edit and reassemble the boot image. Feel free to PM me for my email address for quicker contact if you're using this to develop.
http://www.4shared.com/file/217067115/893ad466/GumboKernel-DevPkg.html
I'm leaving everything up below, but I'm leaving changes to work with other ROMs to the respective devs. I'm still happy to discuss though. Devs note - the kernel and memory killer is very easy to incorporate into your ROM. The above should be all you need, but I'm happy to assist. We're all in this together
Please keep this thread about the kernel. Questions/comments about Gumbo ROM 1.5c should be directed here:
http://forum.xda-developers.com/showthread.php?p=5573162#post5573162
-------------------------------------------------------------------------------------------------------
Download
http://www.4shared.com/file/211795037/24ce727/GK-031-signed.html
http://brandsaturate.com/android/GK-031-signed.zip
http://biggz.dontexist.com:14725/ROMs/GK-0.31-signed.zip
Download a version with less agressive settings Thanks PikkonX
http://forum.xda-developers.com/showpost.php?p=5506779&postcount=68
Download for AOSP builds:
http://www.4shared.com/file/212540959/f11d93c/GK-031_AOSP16-signed.html
Download for 2.1 Heroc ROM
http://www.4shared.com/file/212681068/a732792c/GK-031-21_heroc-signed.html
Built using MCR 2.x inits (for dirty hack of ram managment changes, plan to build universal init to work for all popular ROMs).
Kernel built with debugging and HTC performance lock stripped for full wake ramp up support. i.e. works 100% with setcpu.
No compcache, as I think there may be issues with our kernel and compcache as is, and I think the performance lock may have been causing it. Only fight one bug at a time.
If you need a great how to thread to get started building a kernel there's one here, http://forum.xda-developers.com/showthread.php?t=622916
This kernel is in update.zip format, flash like any ROM.
Work's 100% with Gumbo ROM and MCR 2.x provided MoDaCo custom kernel was not flashed.
Expected to work with stock.
Would love a FRESH ROM tester to try, so any bugs and source can get to flipz for his kernel project, as well as my init in this project.
*update*
Reported working:
Fresh ROM 1.1
Fresh ROM 1.1 (no wipe)
Fresh ROM 1.1 with MCK (no wipe)
TTG 1.6
TTG 1.6 (no wipe)
TTG 1.6 + MCK (no wipe)
MCR 2.x (from kitchen) (no wipe)
MoDaCO 1.2
AOSP 1.6 *
AOSP 2.0.1 *
2.1v1.8_heroc *
*be sure to DL the correct version
david279 has found great battery life using the msm7k governor. See his post HERE. Thanks David!
Usual applies. Be sure to backup. Wipe may be needed, YMMV. Myself and several other testers have went through all dev versions with no wipe, as well as a final wipe and reflash and saw no difference.
Credit to coolbho3000 here on xda for advice with HTC throttling. He's also the dev of SetCPU and his app is indispensable with this kernel IMO. Best buck I've spent at the Market for the donate version. SEE POST 82 BEFORE ASKING SETCPU QUESTIONS PLEASE
Let's roll our own community kernel.
SOURCE CODE FOR KERNEL AND ROM
Note to devs - there are no kernel source changes. It's all in the build options, and the .config is available. I included the full source in the tar because as much as I *****ed about HTC holding it back I had better comply 110%. I've made an alternate zip of just the .config, the built kernel, the wlan.ko, and the disassembled ROM available HERE
How to configure Android's internal memory killer:
http://forum.xda-developers.com/showthread.php?t=622666
Full Details @ Android Dev
http://developer.android.com/index.html?utm_campaign=en&utm_source=en-ha-na-us-bk&utm_medium=ha
Download Gumbo Kernel Beta: http://www.4shared.com/file/211795037/24ce727/GK-031-signed.html
intx's super awesome hosted mirror: http://brandsaturate.com/android/GK-031-signed.zip
Gumbo Kernel Source(includes boot image and ramdisk): http://www.4shared.com/file/21188278...es-031tar.html
ill test it im running fresh 1.1
edit:HERE is the link to it
Thanks for the links guys!
Good luck with the tests.
Downloaded and flashed over gumbo 1.5b ... could tell a differance right away... going to use it for a day or so and report back
Good deal. Running it as is out of the box should have you as fast as it gets without overclocking. Let's hope the battery likes it
so far looks like its playing nice with Fresh 1.1 I did it with a fresh flash of 1.1 as I already had MoDaCo's kernel on there.
Need some free RAM numbers and some setcpu testers.
My experiences
~45 Mb increase in free RAM as reported by systray (free in market)
Setcpu changes the governor, enforces the min and max of the sliders, and cpu correctly ramps back up when using on demand. Don't enable setcpu to run at boot. Like most other widgets the widget needs reset at boot.
So far so good with fresh.1.1
Testing under Fresh 1.1 that had Modacos kernel, and it seems faster to me
using Systray It says 81mb free... is that much? I have not checked before this.
just wanted to see if it would flash over MoDaCo 1.2 and seems to have flashed over it flawlessly with fresh 1.1
So, I already had systray installed and I can tell you that with this kernel it is dramatically better. I just went through my app drawer and literally opened EVERYTHING and couldn't get it to dip below 79. That is freakin awesome.
I just installed setcpu , so ill get back to you on that one.
so using the command "free" in ADB the numbers are as follows
stock Fresh 1.1 2460
after kernel update 4188
in the free column
Source up in second post.
Enjoy
Also, gbhil, love the kernel. Prefer it over MCK
What sort of data do you need from setpcu? I have it installed, set to performance and I can tell an immediate difference. I obviously can't comment on battery yet, but this bad boy is freakin fast.
By the way... since you've implemented the low memory thing....does that mean we don't need to use any task killers ? That would be pointless and redundant, right? Loving the kernel so far.
gomorrah said:
What sort of data do you need from setpcu? I have it installed, set to performance and I can tell an immediate difference. I obviously can't comment on battery yet, but this bad boy is freakin fast.
Click to expand...
Click to collapse
That's the first thing I wanted to hear, as thats going to be the thing people want most lol.
Set your sliders to 480 max 245 min
select performance and refresh, cpu speed should be 480
select powersave or msm7k and refresh, cpu speed should be 245 (ewww) lol
Select ondemand and refresh, cpu should be 480. It will ramp down to 245 when sleeping, and now it will ramp back to 480 when you wake it up.
I've been using ondemand @528 max 245 min, without tweaking the ondemand parameters in setcpu. It's nice to finally have a working way to scale the cpu to your own prefs.
@everybody - thanks for the reports.
alexthearmo said:
By the way... since you've implemented the low memory thing....does that mean we don't need to use any task killers ? That would be pointless and redundant, right? Loving the kernel so far.
Click to expand...
Click to collapse
Correct. No longer a need for task killers.
Woohoo I can post links now.
wow def a major difference in speed with setcpu great job ghbil
Would it work with TTG Rom?
NOTICES: If you are noticing abnormally high battery drain and/or uptime, and you've updated to PRI 1.90, it has come to my attention
that this PRI has been problematic for a number of people, often resulting in large uptimes and/or poor battery life.
This issue affects people regardless of whether or not they are using a custom kernel
Downgrading your PRI and NV to 1.77 has been reported to resolve this issue.
You can find all PRI and NV versions by clicking here.
Due to troubling reports of battery issues possibly caused by the SBC battery charger modification, it is worth mentioning that by using any SBC build, you
fully assume any and all potential risks that the SBC modification may pose.
"netarchy-toastmod" is a kernel originally based on the GoDmOdE sources (Courtesy of Toast) integrating my work on fixing the fps for the Epson panels, and as of version 3.6.1, also integrating a fix for the Nova panels that does not require the use of Evo switch or manually setting any registers, etc, courtesy of work done by AssassinsLament (Well done on the nova fix). Special thanks needs to go out as well to Cyanogen and the cyanogen mod team, as a number of bugfixes and updates to the kernel in recent revisions have been ported over from cyanogen mod to enhance the overall netarchy-toastmod experience.
Click to expand...
Click to collapse
So what's in the kernel?
- Overclocking Support
- HDMwIn (As of 4.3.4)
- Audio gain tweaks (read: make it louder!)
- Fps Fixes
- tun.ko for openvpn users
- CIFS support (as of 4.2.2)
- BFS (in select builds)
- BFQ (in select builds)
- HAVS (as of 4.1.9)
- Assorted fixes/tweaks (that are sadly too numerous to list here)
- An army of rabid naked bunnies
Click to expand...
Click to collapse
The zipalign script in the kernel's modified inits is based on code in the Damage Control rom, and extended to check more places for apps.
The Dalvik code in the inits is courtesy of Ninpo/Hacre from the VillainRom team (over in the HTC Hero forums).
Click to expand...
Click to collapse
mroneeyedboh has written a handy little kernel starter guide with a lot of general information about custom kernels and various terms you might see flying around (such as cfs/bfs, havs/nohavs, etc).
You can view this guide Here
Click to expand...
Click to collapse
Current Revision: Stable: 4.3.1 - For Froyo Sense roms | Beta: 4.3.4
Click to expand...
Click to collapse
A note on multitouch:
Some of you may have used my 5point multitouch test builds with success, others with failure. Research has shown that the Evo's contain at least 2 different versions of the touch sensor, one of which does not support 5point multitouch (but it DOES support 3point). You can check which sensor you have using adb by issuing the following command: "adb shell cat /sys/android_touch/vendor" and examining the result. If your result is ATMEL_x0080_x0016, your phone can support 5point. If your result is ATMEL_x004F_x0016, your phone will only support up to 3point.
Click to expand...
Click to collapse
Disclaimer:
While these builds have been deemed generally safe, it is not feasible to account for all possible combinations of custom roms and uses,
custom roms may experience some breakage depending on how some features are set up, as these builds are not aimed at any one particular rom.
As such your mileage may vary, use these at your own risk.
Click to expand...
Click to collapse
2.2 Kernels (THESE WILL NOT WORK ON 2.1 ROMS):
These have only been tested against the rooted HTC 2.2 stock rom, they *may* work on the various custom 2.2 roms,
but this is NOT guaranteed. MAKE A NANDROID BACKUP JUST IN CASE!
Click to expand...
Click to collapse
If you get force closes on the camera, go to Menu -> Settings -> Applications -> Manage Applications -> All -> Camera -> clear data.
Click to expand...
Click to collapse
-----------------------------
2.6.32-based Kernels:
Click to expand...
Click to collapse
Beta Testing Builds
When making a post about any issues concerning beta builds, please include ALL of the
following information if possible:
1. Which kernel build(s) (ie; bfs/cfs havs/nohavs etc) are you using with the issue?
2. What Rom are you using?
3. If known, what OTA base is your rom using (ie; is it based on 3.29, 3.30, 3.70, etc)?
4. Does the issue persist if you go back to a stable kernel build?
5. The issue being experienced (obviously ;D)
4.3x:
To clear up some confusion that is apparently being spread around,
4.3x builds do in fact work on all current evo models, not just the newest model.
4.3.4:
--CFS builds--
No SBC:
4.3.4-cfs-nohavs-noUV-nosbc (No Undervolting)
4.3.4-cfs-nohavs-suv-nosbc (Static Undervolting)
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-nosbc (More Aggressive HAVS)
SBC: Use sbc builds at your own risk.
4.3.4-cfs-nohavs-noUV-sbc (No Undervolting)
4.3.4-cfs-nohavs-suv-sbc (Static Undervolting)
4.3.4-cfs-havs-less-sbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-sbc (More Aggressive HAVS)
For older beta builds click here.
---------------------------------------
Stable Kernels:
Universal Builds:
4.3.1:
--CFS builds--
No SBC:
netarchy-toastmod-cfs-havs-nosbc-universal
netarchy-toastmod-cfs-nohavs-nosbc-universal
--BFS builds--
No SBC:
netarchy-toastmod-bfs-havs-nosbc-universal
netarchy-toastmod-bfs-nohavs-nosbc-universal
These use Koush's anykernel for installation and should theoretically work on -any- rom.
*note* This is designed to be flashed over a phone that already has a working kernel of some kind flashed,
whether it's a stock kernel, or another custom kernel. In other words, if you can currently boot up your phone into whatever rom you have, this should work. ;D
The universal kernel also does not contain the tweak scripts of the normal build (ie; zipalign on boot and the dalvik tweak), it's intended to be a universally compatible kernel.
This also happens to mean the universal builds will probably work on CM
For older builds click here.
-------------
FAQ:
Code:
Havs: Hybrid Adaptive Voltage Scaling, basically tries to undervolt as much as possible to conserve power, but adapts to things like cpu load and temperature.
No Havs: Static voltage scaling, every cpu speed pulls a specific amount of power from the battery, no variation
CFS: http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Q: Do I need to be rooted to use this kernel?
A: Yes, you need to be rooted, preferably a full root with nand unlock,
Q: How do I flash this kernel?
A: Copy the zip to your sdcard, and flash it from recovery mode
Q: My phone is suddenly unstable after using this kernel and I experience
weird things like reboots or other bugs
A: Are you overclocking? Try lowering the max speed of your overclock.
If the problems stop, you were overclocking too hard. If not,
please include the following information when reporting issues:
1. Your Baseband
2. What rom you're using
3. Your software number
4. Your panel type (Nova or Epson)
5. A Description of what's happening
Q: Why can I only overclock to 1152mhz? (In builds prior to 4.1.x)
A: Frequencies above 1152 have repeatedly turned out to be unstable for
a large percentage of users, so they have been removed to
eliminate the temptation to use them (and then complain because
they are unstable ;D).
Q: Does this kernel work with 2.2 (Froyo) roms?
A: The "Froyoized" kernels do
Q: Will this kernel work with my custom rom?
A: Maybe. The general population build of the kernel should work with
*most* custom roms, but as each custom rom can have it's own
customizations, your mileage may vary. In some cases, particularly
when a lot of customizations are in the rom's ramdisk, the kernel
must be repackaged with the ramdisk from the custom rom to be compatible.
Release notes:
Code:
Notes for Revision 4.3.4
- HDMwIn support added, you still need to download the free HDMwIn app
from the android market to use HDMI mirroring
- Timer tick set to 1000hz
- Unnecessary extra debugging turned off for public builds, should result in a small speed boost
Notes for Revision 4.3.2
- Wimax code updated, 4g should behave a bit better
- SD card read ahead fixed, higher class SD cards should
have an easier time reaching their potential speeds
Notes for Revision 4.3.1
- Screen tearing issues on sense roms should be fixed
Notes for Revision 4.3
- Camera drivers updated to support phones with the newer camera sensors
- ms79723's SBC v7 mod integrated for enhanced battery charging
- Misc speed tweaks/optimizations
Notes for Revision 4.2.2
- Kernel updated to 2.6.32.27
- Conservative set as default governor again
- Conservative governor defaults tweaked
- Less aggressive build has even more relaxed undervolting to aid those with REALLY picky phones
Notes for Revision 4.2.1
- Kernel updated from a 2.6.32.15 to 2.6.32.25
- Interactive governor added and tentatively set as default in some test builds
- Smartass governor added and tentatively set as default in some test builds
- Added BFS 357 smartass builds
Notes for Revision 4.1.9.1
- HAVS has made a return, this should help improve battery life by automatically dynamically undervolting the cpu when possible
Notes for Revision 4.1.8
- Added the BFQ I/O scheduler
- Split out kernel editions, now users have a choice between a CFS or a BFS kernel, if you don't like one, try the other ;D
- Enabled shadow writes on the gpu, which may result in better performance in opengl applications
Notes for Revision 4.1.7
- Add BFS to the kernel
- Allocate more memory to the gpu, this may result in better performance in opengl applications
- A rabid naked bunny vampire has materialized under your bed. Be afraid.
Notes for Revision 4.1.6
- Users with touchscreen issues should find their touchscreen is no longer as responsive as a stereotypical wife on her 10th anniversary
Notes for Revision 4.1.5
- Banished HAVS into the fiery pits of hell for now due to its inability to remain stable with any attempts to overclock. I'll be working on this on the side for possible future re-inclusion
- Clock frequency table remains opened up, with static undervolting in place
- Thanks to l33tlinuxh4x0r for being a guinea pig and helping test this build
Notes for Revision 4.1.4
- The beast responsible for the ridiculous overclocking instability at *any* speed beyond stock has been severely beaten and castrated by rabid naked bunnies (without anesthetic)
- Update scripts redone in the interests of making sure people who have had issues flashing the kernel in the past can do so
- The conservative governor has had some more tweaks to give it better out of the box performance, but you are free to set ondemand as your governor in setcpu if you wish. (If you want to migrate to ondemand you'll also need to set it as the governor in your setcpu profiles)
- The clock frequency table is fully opened up (re-detect frequencies in setcpu to see them) As always your mileage in overclocking may vary, but for some perspective, I ran 1152 through many loops of neocore and quadrant just fine.
Notes for Revision 4.1.3
- The ondemand governor is enabled as an option (switch to it in setcpu if you want to use it, remember you'll have to update your profiles to use it as well).
The default currently remains conservative to have a balance between performance and battery.
- The small segment of users getting bootloops due to the undervolting being too aggressive should be able to boot the kernel now (though if it persists the undervolting can still be adjusted)
Notes for Revision 4.1.2
- All frequencies above 1152 should now be properly visible/usable in setcpu (You may need to re-detect speeds in setcpu first)
Notes for Revision 4.1.1
- Hot on the heels of 4.1.0, a minor versioning fix ;D (4.1.0 reports itself as 4.0.3)
Notes for Revision 4.1.0
- Adapted HAVS for the evo, this may improve battery life by allowing the cpu to run at lower voltages when possible
- The overclocking range has expanded to allow attempting to clock above 1152, Remember that overclocking is unpredictable and potentially unstable by nature, if you encounter problems overclocking, lower the speed.
- Some threshold adjustments to the conservative governor in the interest of improving performance without obliterating battery
- Wired tethering should theoretically work, however if there are problems with the app, an alternative is azilink for wired tethering
Notes for Revision 4.0.3a
- An experiment of sorts, changing from the ondemand speed governor to the conservative governor (with some tweaks), in the interests of keeping good performance with less impact to battery life.
- Rewritten update scripts to hopefully alleviate the small number of people who seem to be having a problem flashing the kernel
Notes for Revision 4.0.2:
- People having stability issues with overclocking to 1152 *may* find it is a bit more stable (your mileage may vary)
Notes for Revision 4.0.1:
- Speed range should now allow underclocking to 128mhz (You may need to re-detect frequencies in setcpu)
- The Nova panel T2 register should be changeable again (for you Evo Switch/Novareq users)
Notes for Revision 4.0:
- Updated to the latest HTC released kernel sources (2.6.32)
- Camera should now be working properly
- HDMI output should be working in Froyo again
Notes for 3.7.8b-Froyoized
- Camera should no longer take dark snapshots when using the flash, the monster responsible has been severely beaten with a twig.
Notes for 3.7.8-Froyoized
- Camera app should no longer crash when changing from 5:3 widescreen to 4:3 standard ratio
- Camera app should properly allow 720p video recording and playback
- Japanese researchers have begun construction on a mecha-rabid naked bunny, codenamed: Bunnytron.
Notes for 3.7.7-Froyoized
- Re-integrate zipalign check and Dalvik cache tweak from the 2.1 line
- Some adjustments made to bluetooth-specific audio tweaks to combat distortion
- Audio adjustments to combat background noise overpowering the voice on the other end of a call
- Set version tag correctly (har har!)
- Super-mutant rabid naked bunny successfully created in lab conditions, however it disintegrates upon exposure to reality.
Notes for 3.7.6c-Froyoized
- SDcards with ext partitions added on should now cease confusing Froyo and allow the card to be mounted properly (Special thanks to Ninpo for directing me to the fix)
Notes for 3.7.6b-Froyoized
- Touchscreen adjustments, this may fix those who had touchscreen issues with 3.7.6
Notes for 3.7.6-Froyoized:
- Compatibility with the leaked 2.2 ota (and probably other 2.2-based roms)
- Working Camera (Limited to 3megapixels) EDIT: Reports indicate it claims 3mp but actually functions at 8mp
- Fps fix (of course ;D)
- Wireless Tether is reported as working with this as well
- 4g is confirmed as working
Notes for 3.7.5:
- Toned back audio boost tweaks a little to address distortion issues
- Updated gpu code for some 3d speed improvements
- Prevented the horde of mutant hairy toe-monsters from spreading toejam
all over the thread.
Notes for 3.7.4:
- Updated bluetooth code, courtesy of cyanogenmod
(You may have to re-pair your bluetooth devices)
- A new audio boost tweak has been applied
(This should not have the issues of the previous audio boost)
- Fixed an issue that would cause some Nova users to mysteriously
revert to 30fps. (Bad nova! no cookie!)
- Successfully avoided maiming any sabretooth'd tiger-striped cows
during the production of this update.
Notes for 3.7.3c:
- Some more tweaks to default performance (when not using setcpu/overclock widget)
Notes for 3.7.3b
- Killed that damn bug monster that decided yet again to sneak into one of my builds. Bad monster! No cookie.
Notes for 3.7.3:
- Adjusted the behavior of the speed scaling governor to give better performance out of the box for people that don't use setcpu or overclock widget
- Made adjustments to the general population build in the interests of making it compatible with Apps2SD by request.(Damage control users should have already been unaffected)
Notes for 3.7.2a
- Gave the monster holding wifi and 4g hostage a spanking (read: wifi/4g should be fixed)
Notes for 3.7.2
- Tweaked Nova settings in the interests of making sure everyone with a nova panel benefits from the fps fix
Notes for 3.7.1:
- Kernel should now have 100% more working HDMI output, no really, we mean it this time!
Notes for 3.7:
- HDMI output should now work in conjunction with boosted Nova/Epson fps
- tun.ko is now included by default for VPN users
Notes for 3.6.4:
- Behold, the return of 5point multitouch! This build should now automatically enable 5point multitouch for all phones that can support it. If the phone does not support 5point, it will default to 3point.
Notes for 3.6.3:
-Removed problematic audio boost patch that was giving issues with bluetooth
-Adjusted overclocking frequency tables to remove some problematic frequencies (Yes I know a small selection of you are going to be disappointed with the lowered cap, but I felt that the problems were more important at this time.)
-Evo switch ideally should not be required for decent framerates on Nova panels, but if users desire, by popular request, they can now use Evo Switch to tweak their T2 register [U]without[/U] it resetting after a screen cycle
-Default T2 value adjusted to 370, AssassinsLament believes this to present a good balance between out of the box performance and compatibility
-No fluffy pink bunnies were harmed in the making of this build
Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?
Awesome, I have a Novatek. /facedesk.
jerryparid said:
Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?
Click to expand...
Click to collapse
Should be flashable with either Clockwork or Amon Ra. Theoretically it might work on Froyo, but I've only tested it on Eclair.
This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.
mattrb said:
This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.
Click to expand...
Click to collapse
Yes the camera works on this in 2.1
Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?
VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
me too. I am going to wait till things cool down a bit and bother HTC for another phone.
jerryparid said:
Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?
Click to expand...
Click to collapse
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...
imaxreed said:
me too. I am going to wait till things cool down a bit and bother HTC for another phone.
Click to expand...
Click to collapse
umm? http://forum.xda-developers.com/showthread.php?t=711964
Best kernel on my epson screen. I like how i can overclock as well
jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Thanks. I have seen that thread a hundred times but never entered it. The FPS doesn't bother me too much I am going to mess with this tomorrow i have the day off thank you.
jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Yeah i'd love to see this fix for nova
netarchy said:
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...
Click to expand...
Click to collapse
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.
jerryparid said:
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.
Click to expand...
Click to collapse
Hrmm, is it glaringly obvious in any particular app? I'd like to see if I can reproduce the experience myself.
My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.
krazyflipj said:
My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.
Click to expand...
Click to collapse
Trying it out now, no problems with youtube for me.
Tearing doesn't seem as bad as I remember, but still bothersome.
when i seen this, i jumped into the air with my fist up like a touchdown at the superbowl.
flashing in juuusssst a second..
VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
same !!!!
This is a no-frills, lean, clean Froyo AOSP machine.
Thanks:
Giant_Rider and Capychimp for the collaboration, klothius for the dalvik-cache script, dferreira for his AOSP source, Fightspit for the battery indicator and Carz for his kernel source.
Sources:
Froyo AOSP
Kernel
Battery Mod
Email.apk
Not Working:
Camera
Includes:
Google apps
Optimizations
Custom hosts file
Swap (requires swap partition)
Apps2SD (requires ext partition)
JIT
Cache on Cache
Renice
Highly OC'd kernel
Launcher Pro
Customizations:
Apps2SD and Swap are enabled on boot but you need the required partition structure. Jit is enabled out of the box. Kernel OC is set at 352MHz (under volted) when idle and 652MHz under load. You can use SetCPU to change the scaling, the scaling range is currently 122-748 MHz.
** Warning **
Typical behavior of an unstable device at high clock speeds are random reboots, black screen of death, and the phone not waking up.
Rom:
Recommended to do a full wipe first including dalvik-cache and sd ext, unless an update is specified "no-wipe".
Fusebox v1.3
*No-Wipe Update*
- New kernel compile (smaller and cleaner)
- Replaced custom hosts file with stock file (was causing battery drain errors in some programs that use a certain implementation of ads).
Fusebox v1.2
*No-Wipe Update*
- Includes updates from v1.1
- New kernel compile (2.6.34.2)
- Changed the default CPU scaling governor to interactive
Fusebox v1.1
*No-Wipe Update*
- New kernel compile
- Updated Brut maps
- Updated Google apps
Fusebox v1.0
*Full Rom*
- New Froyo AOSP base
- Email.apk that works with Exchange
- Addded ES File Explorer
- Updated LauncherPro
- Added latest kernel compile
- Moved default cpu frequencies to init.d
- Added script to clear app cache
- Memory tweaks
Fusebox v0.5
*No-Wipe Update*
- New kernel compile
- Default 352 min CPU speed (reported to fix wake issue for some people)
- Added afflaq's Email.apk to fix Exchange (thx lodewj)
Fusebox v0.4
*No-Wipe Update*
- Added missing speech lib
- Tweaked internal memory management
- Adjusted default clock speeds
Fusebox v0.3
*Full Rom*
- New kernel compile
Fusebox v0.2
*Full Rom*
- New kernel compile
Fusebox v0.1
*Full Rom*
- Initial release.
Themes:
*Updated: For Rom v1.0 Only*
These are flashable updates you apply over the base rom.
Stock White
White with circular battery with % (Fixed)
Black with circular battery with % (Fixed)
Screens:
does anything not work? camera/BT/etc?
EDIT: nvm you edited your post
zeotrope said:
does anything not work? camera/BT/etc?
EDIT: nvm you edited your post
Click to expand...
Click to collapse
Just camera as far as I know right now.
fast rom but have one issue, when phone locks i cant get it unlocked, the screen stays black and no response on buttons. noticed that games not getting laggy when touching screen, had that issue with all other roms for new radio. tried to check out new froyo rider to compare, but its looping while booting so i tried only this rom. sorry for english if its poor
bartasrex said:
fast rom but have one issue, when phone locks i cant get it unlocked, the screen stays black and no response on buttons. noticed that games not getting laggy when touching screen, had that issue with all other roms for new radio. tried to check out new froyo rider to compare, but its looping while booting so i tried only this rom. sorry for english if its poor
Click to expand...
Click to collapse
That's typical of the device not being stable at the clock speed, is still at the default clocks? I may have to bump down the speed if this is an issue.
Switch33 said:
That's typical of the device not being stable at the clock speed, is still at the default clocks? I may have to bump down the speed if this is an issue.
Click to expand...
Click to collapse
yes its on defoult clocks. just managed to flash froyorider rom, as far as i have checked its not freezing while locking the phone, clocks and kernel are the same so maby the problem is somewhere else
bartasrex said:
yes its on defoult clocks. just managed to flash froyorider rom, as far as i have checked its not freezing while locking the phone, clocks and kernel are the same so maby the problem is somewhere else
Click to expand...
Click to collapse
Ok keep me posted, I have only noticed that behavior over 700MHz on my device...
Switch33 said:
Ok keep me posted, I have only noticed that behavior over 700MHz on my device...
Click to expand...
Click to collapse
i think its my device, cause the same just happened with froyorider
bartasrex said:
i think its my device, cause the same just happened with froyorider
Click to expand...
Click to collapse
Hmm ok, you can try installing setcpu and bump it down a notch, if it turns out to be a common problem then I'll adjust the default kernel frequencies.
@Switch33
does it have multilanguage support? (need dutch belgium ).
I was actually working on my own but now that you made one, the need for making one myself is pretty much gone
btw, I would clock it a little bit lower by default and use setcpu to bump it some higher if the phone handle's it
thnx for your work!! keep it up
P.s. got a small request. Don't know if you compiled the kernel from source, but if you do, could you use the slub alocater instead of slab? (if that isn't already the case) ^_^
edit:
some questions:
undervolted?
JIT ?
renice init scripts?
edit2:
Allready compiling carz12 kernel as we speak with slub instead of slab.
Will upload it later today and share it.
if it works well, I will repost it with a lot of kernel debugging disabled. I saw that the cm source that Carz uses has ktimes and stuff enabled. disabling this stuff shoud shaves off a little bit in boot time. I hope that this will apply to our phones as well. I do this stuff for embedded devices (routers) with a x86 base (amd/NS geode cpu's). But I have little to no experience on arm based devices.
thanks it realy fast and nice
also i have set CPU and i changed it to
max 576000
min 245760
its now working great and verry fast
ROM is unstable for me; used SetCPU to lower the clock speeds and it still has trouble waking from sleep or unlocking. Very annoying to say the least since the ROM is great when it's properly working.
EDIT: Rebooted phone and now a new problem -- all my downloaded applications are corrupted. I can not access any of them, just the default apps that came with the app. They do not show up in my app drawer but they show up in my Manage App. settings and they just appear as a 0kb with their system name on the side, not even the application name; seems like a reboot fixes this though.
Can those with problems try this kernel please.
http://gwww.multiupload.com/L6F13CDQYD
Just flash from recovery
download link is broken or filevo has some issues with their servers
lodewj said:
@Switch33
does it have multilanguage support? (need dutch belgium ).
I was actually working on my own but now that you made one, the need for making one myself is pretty much gone
btw, I would clock it a little bit lower by default and use setcpu to bump it some higher if the phone handle's it
thnx for your work!! keep it up
P.s. got a small request. Don't know if you compiled the kernel from source, but if you do, could you use the slub alocater instead of slab? (if that isn't already the case) ^_^
edit:
some questions:
undervolted?
JIT ?
renice init scripts?
edit2:
Allready compiling carz12 kernel as we speak with slub instead of slab.
Will upload it later today and share it.
if it works well, I will repost it with a lot of kernel debugging disabled. I saw that the cm source that Carz uses has ktimes and stuff enabled. disabling this stuff shoud shaves off a little bit in boot time. I hope that this will apply to our phones as well. I do this stuff for embedded devices (routers) with a x86 base (amd/NS geode cpu's). But I have little to no experience on arm based devices.
Click to expand...
Click to collapse
Thanks for the suggestions, I'll take a look at those today. The kernel is undervolted below 384 MHz, JiT is enabled out of the box and includes renice scripts as well as others.
hol17 said:
ROM is unstable for me; used SetCPU to lower the clock speeds and it still has trouble waking from sleep or unlocking. Very annoying to say the least since the ROM is great when it's properly working.
EDIT: Rebooted phone and now a new problem -- all my downloaded applications are corrupted. I can not access any of them, just the default apps that came with the app. They do not show up in my app drawer but they show up in my Manage App. settings and they just appear as a 0kb with their system name on the side, not even the application name; seems like a reboot fixes this though.
Click to expand...
Click to collapse
Do you have an ext partition on your sd card?
who know the "clock + weather" app is?
itenno said:
who know the "clock + weather" app is?
Click to expand...
Click to collapse
Beautiful Widgets 'smaller home'
Switch33, would you mind forging dutch language support in there? (belgium)
It may be netherlands as well ....
I'll send your fresh pina colada while I'll send carz12's as well
lodewj said:
Switch33, would you mind forging dutch language support in there? (belgium)
It may be netherlands as well ....
I'll send your fresh pina colada while I'll send carz12's as well
Click to expand...
Click to collapse
I'll look into multi-language this weekend, long weekend in canada should be able to get some stuff done.
I DO NOT have an HTC Evo, but would LOVE to have one for development, and am saving for one. Bear with me until then I just wanted to say thank you to the few who have donated. I am almost there, any help is appreciated!!! I plan to have my HTC Evo fairly soon
DO NOT FORGET TO READ THE ENTIRE POST ON MY SITE, THERE IS IMPORTANT INFO
THIS KERNEL IS BUILT FOR SENSE ROMS 2.2+
So, it's finally here. It is nowhere near its finished state, or perfect, but I want to get all the bugs reported and taken care of. A BIG shoutout to @toastcfh and @cyanogen for all their work on the .34 kernel for the Evo, without them, this would have been impossible. The .34 branch introduces some nice speed increases along with a few other things. As of now, it does not have HAVS or BFS, but these will soon be implemented. IT IS CURRENTLY BETA. I know this will change however.
Bugs:
* There are some graphical glitches, these will get worked out
* As a result of these glitches, the touchscreen can be wonky
Code:
Also, a little info on HAVS and AVS:
The purpose of HAVS is to minimize the power used by the CPU by determining
and setting the optimal voltage. At the same time, the maximum voltage by
which HAVS can scale to is fixed to a specified voltage depending on the
CPU frequency in order to prevent scaling to a higher voltage than what is
normally used at a specified voltage. The optimal voltage is actively determined
for each frequency and temperature. HAVS actively adjusts the CPU voltage as the
CPU frequency and temperature changes.
ENJOY!
Credits: Cyanogen, ToastCFH for ALL his work on the .34 branch, Netarchy (epson fps panel fix), ffolkes - all for bits of their code (see changelog), Koush for his any kernel .zip, AssasinsLaminent (nova fix), and most importantly, HTC for their kernel source
Download:
As you would expect, I am not responsible for anything that happens to your device
If you like my work follow me on Twitter:
CFS Changelog
Kernel #1
- First kernel release
- Built for sense ROMs
- All things backported you would need:
* WiFi
* Bluetooth
* Wimax (4G)
* Touchscreen
- Noticeable speed increase from .32
- Overclock capable up to 1.113Ghz
- Undervolted for LONGER BATTERY LIFE
- FPS unlocked
- Touchpanel fixes
- All cpu governors included
- OpenVPN support built into the kernel
- All modules compiled that I always include
- New BCM wireless module with combo scan
- Much much more I need to add, it's a first kernel release!
downloading
Thank king
Sent from my PC36100
DL and installing on VirusROM Sense 1.0..
flashing now, thanks King!
THunDA said:
flashing now, thanks King!
Click to expand...
Click to collapse
no problem
All bugs will be worked out over time
Just flashed, and its doin' great! Thanks
this is a kernel based on the new release??? sorry for the question
alcangel64 said:
this is a kernel based on the new release??? sorry for the question
Click to expand...
Click to collapse
kingklick said:
The .34 branch introduces some nice speed increases along with a few other things.
Click to expand...
Click to collapse
unless .34 =/= .34, then yes
Severe over sensitivity in screen touch for me. Just scrolling down app list launched 4 apps in one swipe. impossible to type or even swipe between homescreens. Hw rev 2 novatec panel here. Also some minor screen issues where lines of black would appear. Can't wait for next kernel to try again....
Sent from my PC36100 using XDA App
gtkansan said:
Severe over sensitivity in screen touch for me. Just scrolling down app list launched 4 apps in one swipe. impossible to type or even swipe between homescreens. Hw rev 2 novatec panel here. Also some minor screen issues where lines of black would appear. Can't wait for next kernel to try again....
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
same issue, scrolling acting weird and launches apps when i scroll ;(
Joker022 said:
Just flashed, and its doin' great! Thanks
Click to expand...
Click to collapse
Good. I'm guessing u have an epson screen?
Sent from my HTC Desire using XDA App
Same issues... nova screen hw rev 2... oversensative.. can't type or do normal functions. You can tell its a lot faster than .32 versions...
Yep...severe issues on nova screens. Sounds promising but if you have a nova screen hold off for the next revision unless you would like to help log the bugs for him
Sent from my EVO, the true iPhone killer!
zergburger said:
unless .34 =/= .34, then yes
Click to expand...
Click to collapse
I think he was talking about the new release as in the kernel in 3.28 OTA update which is still a .32 kernel.
I'm having the same screen issues as the above posters with an Epson screen...
I have a Epson Screen. I run the Burn Droid rom.
Same as others reported, severe touch screen over sensitivity, was barely able to slide down to unlock. opened at least four differnent sections in settings and changed a few settings all while swiping downwards.
Quite a few graphical glitches.
been good last couple hours.. epson. nice work as always
downloading... will report back!
This is the restarted thread of my ICS Kernel
-
Codename Harmony
Current features are the following (more will follow) :
EVERY firmware avaiable is supported ! This means you can use my kernel on every ASUS-based roms like Revolver, Frozn or ARHD, but also on AOKP, CM9 Nightlies, Megatron, EOS, CNA, TEAMGUMMY, and all other AOSP-based roms out there.
Full 3G support on roms which support 3G
Stable Overclock up to 1.6 GHz
Stable GPU - Overclock ! -- Better 2D and 3D performance !
This is a HV (HighVoltage) Kernel. This means voltages are increased, but I use lower voltages than guevor does.
Extended File System support : Full CIFS, JFS, XFS, NTFS and REISERFS Support inbuilt in the kernel - no need for modules !
Added back missing powersave governor. This is nothing useful other than setting up profiles in setcpu, powersave governor for "screen off" profile does make much sense here.
Added Deadline I/O Scheduler for fancy testing.
Added Simple I/O Scheduler for ultimate I/O performance.
Readahead tweak for massive I/O performance boost.
Added minmax, wheatly, intellidemand, lagfree, smartassv2 governors.
That's it for now. You shall know I'm always open for user's request and will do my best to implement things from your wishlist if others and I do approve.
Changelog
Code:
[COLOR=Red][B]#FINAL[/B][/COLOR]
[LIST]
[*]Governor improvements - SmartAssv2 fully fixed !
[*]VooDoo sound added
[*]Countless overall improvements and code updates
[*][B]Remember : [/B]Downloads are now at my GITHUB !
[/LIST]
[COLOR=Red][B]UNIVERSE - Branch :[/B][/COLOR]
[LIST]
[*]Revision 1 (rev01) : Added support for all roms avaiable to our beloved transformers. WiFi should work on all versions now, including CM9 Nightlies, which was a huge hassle. 3G support is now added for use with roms, that support 3G ! Kernel Modules like NTFS, CIFS, File Systems, etc. are now all inbuilt, so you don't need to insmod anything. That's why my update.zps are so small - There are hardly any modules to copy over to system. Only NTFS automount is missing on CM9 for now, as it's a bit more complex, but it will be fixed in Revision 2; all other versions should work.
[/LIST]
[LIST]
[*]Revision 3 (rev03) : Improved overall stability, fixed misformed memory management, 3g enabled on all versions now, aosp kernel uses slightly lower voltage than asus one.
[/LIST]
[COLOR=Red][B]RELEASE - CANDIDATE Branch[/B][/COLOR]
[LIST]
[*]RC1 :
Completely recoded from scratch.
Based on 9.2.2.6 Asus Kernel Source.
Yet the biggest fixes to governors ever made by me.
Intellidemand governor fully fixed, smartassv2 is now somewhere near-stable.
Fixes to clocks and voltages, no more freeze at 1.2 GHZ.
FINALLY, GPU overclocking ! (--> stable !)
Tweaked SIO scheduler, now working perfectly on our device.
Readahead tweak for massive I/O performance boost.
Added in new CIFS and NTFS modules directly integrated into the kernel.
Revamped the updater script; more eye candy over here.
Other small changes and fixes to asus code.
[*]RC2 :
Recoded the voltage table, giving more juice to the gpu unit, raised read ahead value. Added CIFS and XFS modules kernel-builtin, will release the modules seperately for you to insmod once I rebuild with CIFS and etc. modular. IMPORTANT : IF THE KERNEL DOESN'T BOOT, HOLD DOWN POWER UNTIL IT REBOOTS. IF IT STILL DOESN'T BOOT, DO THE SAME AGAIN. IT WILL BOOT, TRUST ME.
[/LIST]
[COLOR=Red][B] BETA - Branch :[/B][/COLOR]
[LIST]
[*]BETA5 : initial public upload, after +- 20 hours of testing.
[*]BETA6 : added hotplug governor, added simple I/O scheduler,improved governors and cpu driver + deep sleep code.
[*]BETA7 : removed hotplug governor, caused me and the kernel headaches. Fully fixed the minmax governor, you should choose it as it delivers the best battery life at maximum performance. Lowered voltages, improved battery life and optimized sleep codes once again to get the maximun out of our battery life. Changed kernel versioning system, because of this build number has started at #0 again, is now #2 on BETA7. Also I added some suspending code, you should have no more deep sleep /RR with my kernel from BETA7 on.
[*]BETA8 : Using a new kernel config that fixes the random hangings. Excluded the 'smartassv2' governor for now, will include again in BETA 9, when it's fixed again. Improved SIO I/O scheduler, fixes to cpufreq and block.
[*]BETA-X : Massive fixes to governors, added some new (wheatly, lag free, intellidemand). Optimised voltages, increased frequency bus on overclock. Massive improvements on stability, more reliable in all situations. Improvements on battery life.
[/LIST]
CREDITS
I want to thank everyone who supported and helped me.
marcellusbe
dharam_maniar (formerly dharamG3)
guevor
hillbeast
All my testers, but especially scottyf79 (Gummy and AOKP Tester), cholywell (AOKP tester), ajohn117 (3G Tester) !
DOWNLOADS
NEWEST DOWNLOADS ALWAYS AT GITHUB
giving the kernel a run out now......smartassv2 with noop is blazing for web browsing! works pretty awesome with smartass and deadline aswell.
tried to change to interactive with noop and the tf locked up and i had to force a reboot......il see if i have logcat and post it up.
Will this work with AOKP? I think build 38 switched to the nl80211 wifi driver and the wifi won't work on custom kernels.
scottyf79 said:
giving the kernel a run out now......smartassv2 with noop is blazing for web browsing! works pretty awesome with smartass and deadline aswell.
tried to change to interactive with noop and the tf locked up and i had to force a reboot......il see if i have logcat and post it up.
Click to expand...
Click to collapse
Yeah, I encountered this as well, but I couldn't see any kernel panic in this, might be something else.
My next goal ist to port the linux 3.4 kernel, as they already included android source code in the mainline branch. Thsi would take the kernel to the next level.
But most of my worktime still goes into this kernel
cholywell said:
Will this work with AOKP? I think build 38 switched to the nl80211 wifi driver and the wifi won't work on custom kernels.
Click to expand...
Click to collapse
You're absolutely right. Everything will work fine except for wifi. If more users want this, I will make a aokp version with different wifi driver.
I think a CM9 AOKP version would be very popular. I don't think there any custom kernels for those roms and all the ones based off them.
+1.......the Cm9 builds like Skank etc could do with some loving
scottyf79 said:
+1.......the Cm9 builds like Skank etc could do with some loving
Click to expand...
Click to collapse
Did you try some cm9 rom with my kernel ?
I'm not aware of them having changed the wifi driver to something other than bcmhd...ko , in other wirds, asus stock.
Correct me if I'm wrong.
I'm on a trip the next days, so I will be able to continue work on this kernel let's say.. next tuesday if everything goes well. Just tell me which wifi driver to use and I will compile it
ok ive just tried Skang (cm9) and Gummy (aosp/cm9) with the kernel and neither connect to wifi. also when i tried to change the cpu speed with the baked in cpu controller i found they auto reverted back to 1000mhz with interactive and would not stick on 1200mhz or the selected guvenor.
I'll ask the respective devs what may be required to fix.
thanks for the work..i'm not going to test it due to stocked tf before assistance centre sending,but when i'll receive back my tablet,i'd love to be able to try this kernel...for my taste,i'd love to see wheatley governor inside..for me it's a very efficent governor.think about that mate.cheers and keep up the hard work!
A little update in the meantime : Beta6 is ready, added fully working sio-scheduler and hotplug governor. There is a bug because of which hotplug gov is rebooting instantly after being woken up from deep sleep.
More changes are :
Improved smartassv2 governor, working almost perfectly now !
Improved minmax governor. Ths does now work, but actually needs some further love from me, I think.
Will update the thread next week, along with Beta7.
Beta6 currently avaiable at : http://db.tt/XSK0na2Y
What about version for AOKP? All kernel brake wifi on b38
Seems like I miss my own deadline. Beta7 will be avaiable in a few minutes.
Random governor lockup while changing in setcpu or nofrills etc. should be fixed now.
I also improved all governors balancing and fully fixed the minmax governor.
Added sio scheduler to get the best I/O performance possible.
I will have a look on an AOKP and CM9 version with enhanced wifi drivers next week. Stay tuned !
Hi and thanks for your work.
Here's my experience with BETA7
TF101 b50, always docked with microsd always inserted
rom: revolver 4 rc2, kernel: harmony beta7
I tried your kernel after a long time using guevor's v20, because v20 gave me SOD after 3-4 days of normal operation.
I just wiped cache and dalvik, and then flashed beta7. It seemed to work smooth enough - had some stuttering in Modern Combat3, but that went away after a few minutes of playing.
The major problem was that it just RR while i was in a fring video call. Talking, as usual and then just bam! speakers started making this weird clicking noise for 1-2 seconds, video froze, and my tablet rebooted. This never happened before - i actually didn't have the RR problem even on stock rom+kernel.
I decided to test it overnight, only to wake up and see it rebooted again. It wasn't charging, it was only docked.
The good thing was that battery consumption was good ~1% per hour, with wi-fi on. It goes into deep-sleep, but also, before it does that, it does some random wake-ups.
So here's a summary of MY experience with BETA7 kernel
PRO's:
- no SOD
- good battery life (~1%/hour with wi-fi on, in deep sleep)
CON's:
- Random Reboots
- some random wake-ups
- some stuttering in 3d apps that seems to be loading-related
I'll be going back to guevor's, but i'll definitely keep an eye on this one.
Sorry, i didn't think of saving any kernel logs...
Keep up the good work!
Kernel based on Asus 9.2.2.4 ?
Hi,
is your kernel based on the Asus 9.2.2.4 stock kernel?
Because I've a TF101G 3G model and this the only kernel wich is stable (for about a week no RR or SOD's at all) on this tablet version while using Wifi and 3G functionalities.
BTW I'm using ARHD 3.3.1_3G rom.
I would like overclock it but this is not supported which the stock kernel.
Many thanks in advange.
zdalin2003 said:
Hi and thanks for your work.
Here's my experience with BETA7
TF101 b50, always docked with microsd always inserted
rom: revolver 4 rc2, kernel: harmony beta7
I tried your kernel after a long time using guevor's v20, because v20 gave me SOD after 3-4 days of normal operation.
I just wiped cache and dalvik, and then flashed beta7. It seemed to work smooth enough - had some stuttering in Modern Combat3, but that went away after a few minutes of playing.
The major problem was that it just RR while i was in a fring video call. Talking, as usual and then just bam! speakers started making this weird clicking noise for 1-2 seconds, video froze, and my tablet rebooted. This never happened before - i actually didn't have the RR problem even on stock rom+kernel.
I decided to test it overnight, only to wake up and see it rebooted again. It wasn't charging, it was only docked.
The good thing was that battery consumption was good ~1% per hour, with wi-fi on. It goes into deep-sleep, but also, before it does that, it does some random wake-ups.
So here's a summary of MY experience with BETA7 kernel
PRO's:
- no SOD
- good battery life (~1%/hour with wi-fi on, in deep sleep)
CON's:
- Random Reboots
- some random wake-ups
- some stuttering in 3d apps that seems to be loading-related
I'll be going back to guevor's, but i'll definitely keep an eye on this one.
Sorry, i didn't think of saving any kernel logs...
Keep up the good work!
Click to expand...
Click to collapse
Random reboots are definately rom - related, try ARHD rom, has been the bost rom ever for our transformer, I always put my trust in it. Revolver is halfway abandoned, outdated and not frequently updated.
Random wake-ups are rom related, too. I do not encounter any of your errors, sorry.
Maybe if you could get me a kernel message (kmsg, google it) , I could help you.
antond57 said:
Hi,
is your kernel based on the Asus 9.2.2.4 stock kernel?
Because I've a TF101G 3G model and this the only kernel wich is stable (for about a week no RR or SOD's at all) on this tablet version while using Wifi and 3G functionalities.
BTW I'm using ARHD 3.3.1_3G rom.
I would like overclock it but this is not supported which the stock kernel.
Many thanks in advange.
Click to expand...
Click to collapse
Kernel is based on 9.2.1.24 . I haven't found any newer source on the asus site, but you may redirect me to it, then I will use it.