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!
Related
*** THIS IS EXPERIMENTAL ***
Thanks to toastcfh, maejrep, AssassinsLament, Estimated Prophet, Cicatrize, joeykrim, geyes30, kpkimmel and all the others from the kernel & display cap threads who have been working tirelessly, and continue to do so. This isn't over until we can find the real cap! But I think this avenue has progressed enough for it to have its own thread, if only to give hope, since we now know both Epson and Novatek panels physically can do it!
What Doesn't Work
Nothing. Now based on the official kernel with everything working.
About This Kernel
This is just a dirty hack. We haven't yet figured out where the real cap in framerate is coming from. But until we do, this is the best we have. At least it shows the display itself can handle a higher framerate and isn't physically incapable like HTC would have us believe.
Novatek panels can now get up to 46fps pretty reliably. Run fps2d a few times.
Stdev depends on system activity. If you're going to be judging stdev, DON'T measure it immediately after booting, set your CPU throttle mode to "performance", be sure to run fps2d several times, then average those stdev numbers in your head.
The changes are now immediately applied upon boot. There is no need to cycle your display anymore.
This kernel has support for overclocking/underclocking, up to 1.119 MHz. Also includes my own undervolting and overvolting for higher speeds to increase stability.
You can get dramatically tighter stdev numbers by setting your CPU governor to "performance" in SetCPU. It seems scaling really messes with the framerate. Obviously this will drain your battery faster, as your CPU will constantly be running at full speed. Set it back to "ondemand" if you don't need it.
Some people are reporting their touchscreen grounding issues have been cured.
Support to change the T2 value on the fly [thanks to maejrep]
Support for 5 simultaneous touch points! Use Dotty (in the Market) to see it in action. It'd be cool if someone would make a simple app to demonstrate what can be done with more than the mere 2 points we are used to. People have suggested new lock types, security locks, ways to rotate things, etc. [thanks to maejrep]
Some hardware fails to accept 5 points, so a fail-safe has been added to default back to 2 points for some EVOs
AssassinsLament has created an awesome app to provide an easy way for people to change their T2 timing. Check out his app here: http://forum.xda-developers.com/showthread.php?t=716659 [thanks to AssassinsLament]
Changes to display timings are now sticky until rebooted (w/ the above app, or set manually)
What's New
v5.1.1: Using the official kernel. We've lost some fps, but we've gained camera, video, 4G, etc. 46fps is now average.
v5.1.1: Expanded user-modifiable timing settings. Change at your own risk.
v5.1.1: Audio patched [thanks Geniusdog254 and KERKEDAGAIN]
Instructions
Do a nandroid backup, and flash this over pretty much any ROM. If you have problems, you can just flash a stock boot.img again. There should never be any need to wipe anything.
IMPORTANT: This will only work with the stock bcm4329.ko! Using the newer files and flashing this kernel will result in wifi being unable to start, and vice versa. To correct this, you'll need to flash over the correct wifi files.
Changing Timing Settings
You can use the following commands from adb shell to temporarily change timing on the fly. Do it while your screen is on.
Set: echo NUMBER > /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Check: cat /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Parameters:
t2 - 245 to 1023 [Default Eclair: 437, Froyo: 432]
t3 - 0 to 7 [Default Eclair: 1, Froyo: 0]
fte - 0 to 879 [Default Eclair: 35, Froyo: 60] (Frame Tearing Effect, change this if you have tearing problems)
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Note: Certain things like the camera still don't work, since our Froyo ROMs aren't official.
Flashable ZIP - WiFi-N + 4G for all custom kernels based on toastcfh's GoDmOdE kernel (compatible with v5.2+)
Flashable ZIP - WiFi-N + 4G for stock/custom kernels (compatible with v5.1 and below)
Flashable ZIP - WiFi-N + 4G for the OTA kernel (NOT compatible with the kernel in this post)
*** REMEMBER! No one here is responsible if you damage your phone! ***
See the Evo, Droid X and Nexus One benchmarked together here: http://androidspin.com/2010/06/25/droid-x-vs-htc-evo-vs-google-nexus-one-in-benchmark-face-off
Want NenaMark1? It usually doesn't show in the Market, so get it here: http://nena.se/downloads.html
Awesome, just flashed and it is soo smooth, thank you devs.
This works great for me.
Not really related to this but my phone locks up when I change the cpu frequency with setcpu. EDIT: (How do I overvolt the phone?)
Oh and yes I do get 50hz.
Is there 2.2 support or no
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Nope I wish there was. Droid X skin + 50hz would be very cool.
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Second this question..I'm loving the EvolutionX froyo rom and would be sweet to get this baby on board with froyo.
Does this work for Epson panels too?
This works great. Touchscreen SEEMS a bit more responsive in in multitouch vis test. Grounding issue is nowhere near as bad, but still there. If you pull the same trick that everyone is doing to test grounding problem, you won't notice it at first, and very rarely will it stop sensing you finger all together, but it definitely does cut out for an instant every now and then, and I had it drop visibility where it normally does a few times for a split second.
Epic delete
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Can you zip your modified files and post them too? Source would be nice
sweteg said:
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Click to expand...
Click to collapse
This thread was made to avoid the clutter from the Godmode thread.
Thanks for the excellent dev work!
You might want to add to the first post that this kernel breaks 4G. it will turn on but not able to find any network.
Other than that, works as described
The device feels so much smoother!
Great work! I get 52 in fps2d, 680 in quadrant, and 51 in gears. I can't wait until this is completely fixed but I'm loving it and the undervolt and oc patches are awesome additions.
automatic brightness still does not work with this kernel though. At least not for me. Is it possible I have a different light sensor as no custom kernel has worked with auto brightness yet and other reports say it works just fine.
Also... fps2d spikes into 99 fps and at one point I watched it flash past 100
Definetly works
Installed the kernel and got over 50 fps on my nova panel i have hardware config 002 it runs much much smoother thanks devs for the hard work.
wow this kernel is insane, I mean FPS hack and overclock hack without force closes...wow is all I can say. Used the OC widget and it detects the oc clocks quickly.
Man if this kernel makes it to Froyo..Evo will be truly evil
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Mrtankjump said:
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Click to expand...
Click to collapse
My Evo has an Epson panel so I can't use this fix but, my understanding was that this method didn't cause the tearing like we saw from Toast's custom kernel on Epson displays, so your problem might be something else and not necessarily the fps cap being raised.
Thanks for the kernel, but I still have one big problem- my battery still will not charge with this kernel installed. It will only charge when I turn off the EVO and turn it back on. But as soon as I unplug and replug it in, it will look like it charges for 5 seconds, then the orange light shuts off and it stops charging. I've enclosed a dump of my dmesg. Can someone please take a look at this?
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.
Hi. The following kernel is presented to you by
vorkKernel Team:
- kiljacken
- Benee
Click to expand...
Click to collapse
This kernel is for Cyanogenmod (and in theory any other CM based rom). *Could* be incompatible with latest kangs or nightlies (after a kernel update from CM team). No support for sense...
New vorkKernel Twitter Bot: Here
First I wanted to thank Thalamus for his awesome base kernel - Thanks man . Than I wanted to thank the CM Team for the awesome developement work. Without you guys the Desire weren't such a great device.
Features:
Oc to 1113 Mhz
toggable AVS via app or flags (Credits to dzo and thalamus for avs)
Default IO-Sched is Deadline with a special flash storage tweak
Slub allocator
Tiny-Rcu
BFS Cpu Sched
compiled with a tweaked toolchain (base linaro gcc)
overall compiler optimizations
flags! (more below in the flag section)
A App for easy downloading and configuring. Credits to kiljacken!
Click to expand...
Click to collapse
The standard part:
I'm not responsible for melted phones or something like that...
Click to expand...
Click to collapse
And the source code here.
Download (Market)
Credits to kiljacken for this awesome app! You need OI File Manager for the app (Comes with CM)!
(and if you refuse to use the app - or the app is refusing to work with you: here)
Only change something, if you want to enable OC - No need to touch anything else (like govenors, schedulers)
What are flags and how can I use them?
I recommend to use the App kiljacken made, because it's super easy for you guys. If you not want to use the app *sadpanda* then you can click this link. This is the file the app is fetching to generate the UI.
The layout is following:
Available for following device/Element style (more below)/the flag you need to add/Flag name in App/Description for general Flag/Choice name in app/actual value you need to add after flag name
If the last two points are added you first enter the flag name and than the value. For example: density230
You connect the flags with a: -
Example: -camera-ring ...
The script is configured to detect flags after vorkKernel-VERSIONNUMBER. So you can add some flags after this.
Element style
c = Checkbox
l = List you can choose things from
e = you can enter your own value
Click to expand...
Click to collapse
Error Reporting Guide
Start with rebooting, if that doesn't help, reflash CM and then the kernel, and check again. If you're using the updater app (make sure you have the latest version), use the error report function (and describe what you're problem is). If you're not using the app, then post what flags you are using, along with what your problem is.
Click to expand...
Click to collapse
Additionally I just want to point out that I'm not doing this as a fulltime job, so don't expect daily updates or something like that. I will try to fix a problem as fast as possible but in some cases it can take a while.
If you want to support me you can sign up on dropbox via my referral link or just push this nice thanks button .. If you want to donate you can donate to thalamus or the cm team something. I'm learning C and linux and vorkKernel is my learning project and it is a hobby for me. Anyway if you still want to support a poor student, I have a link above my avatar
Thanks to:
the whole CM Team
thalamus (for base kernel and being totally awesome)
Erasmux
All guys that made pull request and contributed in any possible way
Donators to our project (app or kiljacken's donate link)
the android community
and a very big thanks to b3ndech0 for his buildbox.
Thanks! Will test it soon.!
Did you tested it with Defrost 4.1? Get random reboots with his kernels hope your will solve this!
I run it with cm. And df and cm are nearly the same so maybe it will work for you. (My desire don't like high oc so this slight oc could fix your problems)
I'm using opendesire 4.0.15 and the wifi doesn't work with this kernel. When i try to activate wifi, it says "Error" in the menu. If I try a full wipe will it help?
Oh, and what's the difference between havs and svs kernels (i installed havs, it was first on the list)? Now if it's a "when you ask this you really shouldn't be here" type of question, I apologize for spamming...
Thanks a lot Desire ftw
Sent from my HTC Desire using XDA App
Benee said:
I run it with cm. And df and cm are nearly the same so maybe it will work for you. (My desire don't like high oc so this slight oc could fix your problems)
Click to expand...
Click to collapse
Ah thanks .... oc was not the problem i dont use OC ;-) because i need SetCPU for it. Is this the same with your Kernel? Do i need SetCPU?
Will look into the wifi issue when I'm at a PC again. And SVS (static voltage scaling) is the standard to set the Mhz and HAVS is a method from intersectraven which mixes SVS and AVS (AVS uses the temperature of the cpu to set the clock). HAVS uses slight less battery.
Hope I managed it to explain this good enough.
xtcislove said:
Ah thanks .... oc was not the problem i dont use OC ;-) because i need SetCPU for it. Is this the same with your Kernel? Do i need SetCPU?
Click to expand...
Click to collapse
I don't use it and don't see a reason for using it, because the max voltage from standard max clock (1275mv) to the oc (1113 Mhz) (1275mv) is the same.
it is work for opendesire?
I'm sure this was asked above this post, however, I'm confused if I should use SetCPU with this Kernel, or it automatically sets it at 1.1GHz? Would I still need SetCPU to increase the frequency?
First I pulled the release because I forget to add the wifi module. Will upload it tomorrow again. Then fully working.
Then no need for setcpu. The Kernel will set the clock itself (max 1113 Mhz).
Both Kernals work with OpenDesire 4.0.17 (experimental) but I had problems with ADW Launcher f/c Launcher Pro/Zeam/GDE and Stock Launcher seem fine. Notice Wi-Fi so no further testing. Will be interesting to see what if any affect HAVS has on battery with OD as this does give good life already. Used to use PAYS Rom with HAVS and that made big difference to batt so we will see. Look forward to tomorrow.
Thanks for your contribution to Desire and good luck.
please
pls add exact values for uv and axi.
make aversion with cfq.
fixed Wifi now
bongmaster2 said:
pls add exact values for uv and axi.
make aversion with cfq.
Click to expand...
Click to collapse
What extra values? and why cfq? BFQ runs bette imo
kfasheldon said:
Both Kernals work with OpenDesire 4.0.17 (experimental) but I had problems with ADW Launcher f/c Launcher Pro/Zeam/GDE and Stock Launcher seem fine.
Click to expand...
Click to collapse
Thanks. Will look into the ADW Problem
How is batterie drain with this Kernel? Now use Defrost with svs 1113mhz and Batterie drain is big, bigger than the OD Kernel with the same MHz.
I'm using the HAVS one mainly and I'm quite satisfied with the Battery. But hard to tell because it variates thru different usage and settings (like Display brightness)
Benee said:
What extra values? and why cfq? BFQ runs bette imo
Click to expand...
Click to collapse
the values for axi bus speed. how much mhz at which processor frequency. and the millivolt values for every processor frequency. just 2 tables for comparism with other kernels.
bongmaster2 said:
the values for axi bus speed. how much mhz at which processor frequency. and the millivolt values for every processor frequency. just 2 tables for comparism with other kernels.
Click to expand...
Click to collapse
acpuclock-scorpion line 68
The batterie drain with auto brightness and much Internet use. Compared to svs kernel from Defrost 4.1a with svs 1113mhz.
So, who has cajones that clank?
Current things of interest:
- Overclock up to 1.6ghz [Use a tool such as Setcpu to overclock]
- 2.6.36.4 kernel base
- CIFS included
- TUN built-in
- NTFS support
- Voodoo Sound
All sources can be found on my github (see signature)
These are designed to be flashed via clockwork, or you can flash them via Shinzul's Kernel Manager (Available on the android market)
Disclaimer: You flash these at your own risk, and assume any and all potential consequences, including (but not limited to), loss of data, meltdown of your device, world destruction, injury of assorted puppies, spoiling of your glass of milk, revocation of chocolate privileges...etc. In all seriousness, it's an experimental kernel, so treat it as such, and enjoy.
Overclocking disclaimer: Overclocking is never guaranteed to be stable (that's simply common sense). If an overclock speed is not stable, your device may not be able to handle it and you should try a lower speed.
BE SAFE!!! MAKE A NANDROID BEFORE FLASHING SO YOU HAVE SOMETHING TO FALL BACK ON
Current version: Netformer 1.6 (For Honeycomb 3.2) [Also available in Kernel Manager, from the Android Market]
Netformer 1.6
Tested with Prime 1.7
md5sum
3223bb177a86434837f5fe8630315a7d netformer-1.6-signed.zip
Code:
Changelog:
Revision 1.6:
- Updated for Honeycomb 3.2
- Due to some rather large changes by ASUS in the kernel, the tap-to-click disabler app currently will not function in this latest kernel. If it is possible to bring the functionality back, it shall be done.
Revision 1.5:
- Updated to support android 3.1
- Added Voodoo Sound
*Your quadrant epeen may not be quite so large (though they may be more accurate) due to some bug fixes from upstream, if there is room for improvement, it will be explored*
Revision 1.4r2:
- Fix a bug causing wifi to break when the tablet sleeps
Revision 1.4:
- Add SLQB memory allocator
- Set timer to 1000hz
- Add 1.504 and 1.6ghz frequency steps
- Add preliminary toggle interface to allow tap-to-click to be disabled (See OP for a nice gui front-end for the toggle, courtesy of vividboarder)
Revision 1.3:
- Assorted bugfixes, including a possible fix for a bug that could lead a cpu core to 'forget' it's speed policy and wander out of sync
Revision 1.2:
- Power regulator bug fixes that may address the "SoD" issue experienced even by users on the stock kernel
(technically not actually a sleep of death)
Revision 1.1:
- Adjusted voltage levels for stability
- Added NTFS support
- Assorted bugfixes
Reserving this post as well
Can't wait! overclock kernel for TF101, im constantly pressing F5 on your github.
Edit:
I just flashed the kernel, setcpu to 1400, omgash its so fast i think i traveled back in time which makes me the first poster in this thread of awesomeness!
i see the OP says it is designed to be flashed in cwm, i was under the impression that kernels had to be flashed as a blob through adb. is that no longer the case?
Crimton said:
i see the OP says it is designed to be flashed in cwm, i was under the impression that kernels had to be flashed as a blob through adb. is that no longer the case?
Click to expand...
Click to collapse
Oh it's still flashed as a blob, but it's made clockwork friendly
netarchy is developing for the Transformer? Thank you based god! Just made my TF worth rooting. Looking forward to some netarchy toastmod for Evo like love! Still running your kernel on my Evo.
netarchy said:
Oh it's still flashed as a blob, but it's made clockwork friendly
Click to expand...
Click to collapse
thats great so i just flash as i normally would. could you post the stock kernel in a cwm friendly zip in case we would want to revert?
Done. Overclocked to 1.4 GHZ ..... To easy
Sent from my Transformer TF101 using Tapatalk
My fav evo kernel maker now on the transformer........hell yea!!!!!!!!
awesome in disguise? i liked more than eats the pie
kernel is running great at 1.2 1.4 had a few lock ups but ita great to see a great kernel dev on the tf!!! thank you! Q do you know what they did in the xoom kernel to run netflix maybe you can duplicate!!! I will help any way i can! thanksx again
1.4 no lockups youtube 720p & 1080p smooth
Sent from my Transformer TF101 using Tapatalk
Thank you sir - running fantastically @ 1.2GHz
I will test 1.4 tomorrow.
sent from a device using an app
@crimton ... love your avatar pic.
Finally the Youtube app is usable. Great work.
this is great! Thanks for the hard work.
friggin awesome!!!!! Running netarchy on my evo and on my tf....friggin awesome!!!!
1.4 ghz running like a champ!
I'll wait a little longer, but I'm glad to see kernel development picking up thanks netarchy.
P.S. on stock kernel what is the lowest freq the transformer goes to?