I would like to thank all the testers who were brave enough to flash my kernel. Please be advised that I do not own any Transformer device (well I used to own a TF101 before it's ICS days till my boys ended its life early) and so I relied heavily on the testers. Please click on the DONATE TO ME button if you appreciate my work.
BIG THANKS to my wife for allowing me to do this work Big thanks to all the testers too. Thanks to the donation of Blackwidowman (first donation), shaolin95, Stuart P, Jack S it's greatly appreciated
A Backup is a must and you should be knowledgable on Restoring your device, NVflash knowledge is recommended.
----------------------------
Update 11/9/2012
Asus Governor fix
1.8 ghz
http://dl.dropbox.com/u/92981926/ClemsynTFUniversalStock.zip
1.7 ghz
http://dl.dropbox.com/u/92981926/ClemsynTFUniversalStock1.7ver4.zip
1.6 ghz
http://dl.dropbox.com/u/92981926/ClemsynTFUniversalStock1.6ver4.zip
If you like my work, Please Donate. Thanks
--------------------------------------------------
Update 11/5/2012
Releasing this Kernel out of beta. We have 3 kernels. 1.8ghz, 1.7ghz and 1.6 ghz all with 650 gpu.
1.8 ghz
http://dl.dropbox.com/u/92981926/clemsynTF300prime1.8650GPUver20.zip
1.7 ghz
http://dl.dropbox.com/u/92981926/clemsynTF300prime1.7650GPUver20.zip
1.6 ghz
http://dl.dropbox.com/u/92981926/clemsynTF300prime1.6650GPUver20.zip
LMK how it goes
If you like my work, Please do not hesitate to click DONATE TO ME button and reward my HARD WORK and add to my Transformer fund Any donation is greatly appreciated.
---------------------------------------------------------
Update 11/4/2012
Only for Stock Based ROMS
Changes
1. Locked max speed at 1700
2. init.d support
3. Fsync Control
4. DPI hack
Here is the link
http://dl.dropbox.com/u/92981926/clemsynTF700ver10GPU650VC.zip
LMK how it goes.
----------------------------------------
This kernel is based of TF700t 4.1.1 and is not compatible with any CM10 version of kernel. So only Stock BASED Roms. Here are the specs.
1. Overclocked to 1.8 ghz with 1350mv
2. GPU at 650 at 1350mv
3. Undervolting is implemented
Here is the link
http://dl.dropbox.com/u/92981926/clemsynTFUniversalver5GPU650VC.zip
This is still in beta so Please LMK how it goes and dmesg via Pastebin is greatly appreciated. THANKS!!
THIS KERNEL IS SET TO BOOT AT 1.8ghz so it will not work on All TF201. Only great batches of Tegra 3
If you like my work, Please click on the Donate Button, Thanks
Source: https://www.dropbox.com/s/pjqd2b1edn6fiwu/tfcombofinal.zip
I would love to test this if for JB. PM me o know! I have been trying all the JB builds trying to get the most stable in the KB dock and have all features enabled. Even the best seems to randomly reboot every now and then. Its still fun to mess with all the options and builds!
corey113888 said:
I would love to test this if for JB. PM me o know! I have been trying all the JB builds trying to get the most stable in the KB dock and have all features enabled. Even the best seems to randomly reboot every now and then. Its still fun to mess with all the options and builds!
Click to expand...
Click to collapse
Hello corey113888! Have you tried the new Baked JB that Craig put out yesterday? I installed and set lock delay in settings to 15 seconds after screen blank and so far I have not had a reboot in the dock!
Subsonic44 said:
Hello corey113888! Have you tried the new Baked JB that Craig put out yesterday? I installed and set lock delay in settings to 15 seconds after screen blank and so far I have not had a reboot in the dock!
Click to expand...
Click to collapse
Cool. I am installing that one now. I guess TWRP does not support mounting micro SD card formatted NTFS. I cant seem to get recovery to see it. Otherwise I would be rocking it already. I use a wireless mouse to. It has a USB receiver and I did not know if it might be causing the reboots.
corey113888 said:
I would love to test this if for JB. PM me o know! I have been trying all the JB builds trying to get the most stable in the KB dock and have all features enabled. Even the best seems to randomly reboot every now and then. Its still fun to mess with all the options and builds!
Click to expand...
Click to collapse
We got it to boot in Androwook and ClearROM This kernel is not based on _motley but on asus 10.4.4.18 which is JB. I also built one for CM10.
corey113888 said:
Cool. I am installing that one now. I guess TWRP does not support mounting micro SD card formatted NTFS. I cant seem to get recovery to see it. Otherwise I would be rocking it already. I use a wireless mouse to. It has a USB receiver and I did not know if it might be causing the reboots.
Click to expand...
Click to collapse
I also have a wireless mouse with the usb receiver. That plus an sd card in my dock. I've tried taking everything out of dock and still would get sod's and reboots. In my case it always happens when the screen times out. In the baked settings you can delay the lock for a settable amount of time and since I delayed the lock, I've not had a problem!
cool, where do I download the kernel?
corey113888 said:
cool, where do I download the kernel?
Click to expand...
Click to collapse
I didn't download any special kernel. Just using what was in the rom. I did flash the tweaks and disabled journaling.
The Prime really takes off with this, I have both a Infinity and a Prime and the Prime handles graphics MUCH better due to the higher
screen resolution of the Infinity. Thanks for this, almost like a new device.
I will figure out how to pull dmesg to post. But I don't think I ever tried to overclock that high. Regardless, I'll donate when you post a working kernel. I'm very excited for a new kernel for this device. I think we could really use it. Thank you.
Update:
1. Some testers able to boot with my 1.8ghz 650gpu on stock ROM and kernel modified for stock ROM, some can't boot. Some are unstable at 1.8ghz
2. Same as above CM10 rom with CM10 kernel but wifi is not working at all
Beta kernel released
Will be trying this on Androwook 1.3. My Prime already flies with the Cleankernel but 1.8gh is irresistible. Will post back with how it goes.
EDIT: Flashed fine. Unstable running benchmarks at max OC and is now bootlooping.
clemsyn said:
Update:
1. Some testers able to boot with my 1.8ghz 650gpu on stock ROM and kernel modified for stock ROM, some can't boot. Some are unstable at 1.8ghz
2. Same as above CM10 rom with CM10 kernel but wifi is not working at all
Beta kernel released
Click to expand...
Click to collapse
I tested kernel and it booted fine but resets when running bench marks. Also i tried down clocking it to 1.4 or 1.5 but even though i have it set to top out at those speeds it was still running up to 1.8 and running at top speed(1.8) the tablet began running real warm so i restored my backup to flash my previous kernel so i dont dmg my device before you get this all worked out for us.
Running this on hairy bean 1.3 in the KB dock and all is well so far.
Can we get SIO scheduler? or an i compile one and add it
kix08 said:
I tested kernel and it booted fine but resets when running bench marks. Also i tried down clocking it to 1.4 or 1.5 but even though i have it set to top out at those speeds it was still running up to 1.8 and running at top speed(1.8) the tablet began running real warm so i restored my backup to flash my previous kernel so i dont dmg my device before you get this all worked out for us.
Click to expand...
Click to collapse
Same here. Runs smooth until some heavy CPU stuff is going on, then reset. I guess, my Prime isn't up for 1,8GHz, but I really like the overall performance of that kernel. Any chance to restrict the maximum frequency to 1,7 or 1,6GHz?
Regards,
Kashban
I used the clymsyn-blades kernel for the longest time on my TF101 before I traded it in for my prime. Definitely going to be using this one.
Question though, do the battery saver/medium performance/high performance buttons work with this kernel?
I tried to give this a whirl, but as I suspected, it overwrote my data2sd installation (so I restored my nandroid)...
Anyone knowledgeable able to merge the two together?
I just installed with with Androwook 1.3 JB and Quadrant is reporting max speed as 1300Mhz only and I cannot get it to go even past 1.2Ghz no matter what mode I try.
Anyone else having this problem?
Are the engery options still working with your kernel? I dont want to run it @1800 all the time...
Boots at 1800 but system tuner or something puts it to 1400. then I had random reboots and went back to clean kernel.
What file controls the GPU speed?
Related
hi there
i am a noob i just brought vibrant previously using htc hero...
i tried to flash bionix and bionix fusion with the new 1.2 ghz oc...
phone works well except when i play games like asphalt, neocore my phone freezes then i have to remove the battery and insert again...
what could be the problem
i am using J12 RADIO....
PLEASE HELP ....
VIBRANT IS 100% AN IPHONE KILLER ... LOVE IT....
mine does the same thing not really sure why yet but if your using setcpu just put the speed at 1000 on both the proformance is unnoticable
Thegreat520 said:
mine does the same thing not really sure why yet but if your using setcpu just put the speed at 1000 on both the proformance is unnoticable
Click to expand...
Click to collapse
i had kept setcpu max 1000 and min 200 still it freezes when running heavy graphics games
Your phone might not play nice with that kernel. Try flashing core 1.0 instead and see if that helps.
Yes, not all phones are stable when overclocked. Use the stock kernel and you should be fine.
Chalup said:
Yes, not all phones are stable when overclocked. Use the stock kernel and you should be fine.
Click to expand...
Click to collapse
^^^ this, but I'm sure you knew that since it says so every where.
My phone runs great at 1.2Ghz with JAC's XMOD Voodoo kernel, but locks up constantly with Core, OCed or not. Try swapping kernels, but don't give up on the OC yet.
I'm having the same exact issue, mine will just lock up for no reason sometimes as well. I'm not sure what it is, I kind of feel like it's the rom. I had problems originally with fusion to begin with. Maybe I'm not doing a proper procedure to install it?
Is it because I'm wiping and going straight to fusion? Please anyone else are you having this issue, I'm getting frustrated and feel my phone is slightly useless like this. I HATE stock.
Edit: Setcpu doesn't let me set to 1000 with Core 1.2Ghz, I can only get 1000 if I use Core 1.0Ghz (obviously). Again though, same issue regardless.
Core is still in beta status and not all the bugs have been worked out yet. The issue the OP is having has been mentioned before in the Core thread in the Dev section and on the TeamWhiskey.com forums as well.
OP: To alleviate the freezing issue you're having, flash the 1.0GHz CoreV1 instead of the 1.2GHz CoreV1
~SB
Title says a helluva lot ;-)
READ THIS WHOLE POST AND THE WHOLE POST AFTER IT!
Features:
All steps undervolted about 25%. Should be stable still
The table is currently 300, 600, 950mhz until I can make it scale more than 3 steps.
The voltage for 950Mhz is less than at stock for 800Mhz, so you should see better battery life even though we're overclocked.
Display flicker fixed (or at least toned down, it can't be completely eliminated with the LED backlighting)
Scheduler tweaks backported from later kernel versions
Some governor tweaks of my own for responsiveness
To install this, just flash the zip in ClockworkMod. This shouldn't harm your device, but I make no promises. I trust it enough to run it on my device, if that means anything to y'all. I also attached a zip to flash back to the stock kernel (..but why would you break my heart by doing so..? ;P).
Next Up:
I REALLY want to get 1Ghz+ working, and my code is sound (I'm sure of that) but it won't boot on my device. I think I just need to find the right voltage, or I could have a bad die for OC'ing. This is the first thing I will work on.
Maybe the interactive CPU governor
Look into the 2-point touch limitation
Source:
Source is available on my GitHub at https://github.com/geniusdog254/Quickie
I will not flat out ask for donations, however I do appreciate them. So if you're feeling generous or appreciate my work then it would help me out a lot if you could donate. I have my game Reflex-A-Tron on the Market for $1 if you'd like to donate like that, or there is a link under my name on the left side to donate, and one in my signature. The one on the left and in my signature is to donate via PayPal. Any amount is appreciated, but please don't feel obligated.
You can contact me here via PM, on Twitter @geniusdog254, or email me at [email protected]. Email or Twitter is the preferred method, because I really despise the XDA PM system.
Disclaimer:
If this breaks your Nook, kills your family/pets, or starts global thermonuclear war, do not blame me. You have been warned. If you break your device and blame me, I will point at you and laugh.
Changelog:
1-11-11 - Screamer:
Overclock to 950Mhz. Still chokes at 1Ghz, which tells me it's probably my device. 950 is stable.
Temp sensor drivers. Thanks to the Nookie FroYo guys!
Updated to 2.6.29.6.
Scheduling tweaks from 2.6.31.
Code idle time from 2.6.34.
Scaling fixed. Now scales properly between all 3 CPU levels. Adding more than 3 makes it choke for some reason. I'll look into it.
Test version set at 1Ghz added. Just because it doesn't work for me doesn't mean it won't work for you. Don't get your hopes up though, I've tried making it work every way from Sunday
Notes:
Screen WILL be unresponsive immediately after a boot. Just lock the device for several seconds, unlock it, and all will be fine until another reboot. I blame B&N, it happens with all custom kernels.
Yes, I know there are more versions of this kernel than there are Windows Vista. The middle one is the recommended one. If your Nook can't run at 950Mhz (crashing often, or just won't boot) try the one with the 900mhz tag. If you wanna try and push it higher, try the 1Ghz one. Be warned: very little success is reported with the 1Ghz kernel. The top level of these chips seems to be right around ~925-975Mhz. Very few devices will be able to hit 1Ghz.
You should probably wipe your cache partition after flashing this. You won't lose anything, and many people are reporting that it makes things more stable at the higher freqs for them.
MD5 Sums:
stock-1.0.1-kernel.zip — 78ccf8ab0cd35b988cc9a81bd8bbc310
quickie-1ghz-test.zip — 7076a88cae2229910478e698c0e19435
quickie-screamer.zip — 22e8c2cc21e42cca1d18377a92b49540
quickie-900mhz.zip — 40362515da86cb4baea37b0bc6358feb
Wow thanks so much for this. Gotta try it out!
wow very nice! going to have to give this a shot!
Awesome! But is it compatible with nookie froyo (2.2) or the stock BN (2.1)?
Update: It boots Nookie Froyo but powers off immediately after booting. I am looking forward to the release of the 2.6.32 version of your work. Keep up the good work!
Sent from Nook Color (Nookie Froyo microSd optional)
runhopskipjump said:
Awesome! But is it compatible with nookie froyo (2.2) or the stock BN (2.1)?
Sent from Nook Color (Nookie Froyo on emmc)
Click to expand...
Click to collapse
Just stock 2.1.
With the Nookie FroYo, it wouldn't flash the kernel to the SD for boot, plus (at least on th Epic) a 2.6.29 kernel won't boot on FroYo, it needs 2.6.32 or higher
Glad to have you part of the nook color family. You did awesome work on the Epic4G.
Looking forward to more great stuff from you.
Thanks
Sent from my LogicPD Zoom2 using Tapatalk
Loss of touch sensitivity
I loaded up the new kernel via Clockwork and all went smoothly with the install. I noticed immediately that my touch sensitivity has decreased. I now have to press and hold just about as long as you would press and hold to bring up a context menu or something. If I don't do that, my touch is ignored and not registered.
Interestingly enough, when I type an email on the keyboard, it recognizes my typing very quickly. No apparent loss of sensitivity when I'm using the keyboard. I wonder why and how that is???
I guess I need to recalibrate the screen again to regain sensitivity.
I did notice that Castle Crashers frame-rate has improved a good bit with the overclock. It's a noticeable and welcome difference.
Angry birds was a bit annoying to play with the loss of screen sensitivity.
Edit: I alleviated the loss of touch sensitivity by installing the LCDDensity app from the Android Marketplace and selecting a density of 200.
Tried to install via clockwork and I keep getting errors unable to install. an I missing something?
sent from my nookcolor using the xda app
Got it working with clockwork update... thanks!
Flashed. Am loving it, seems much snappier, and the keyboard response at 900mhzz is much improved. Keep up the good work!
NC overcklock
Hi,
Last month I made some tests with overcloking /undervolting. I was able to push the NC at 1.15GHz, with a little voltage tweaking. 1Ghz was achieved without voltage tuning. The smartreflex technology adjusts automaticaly the OPP voltages to minimize the power consumption. Maybe the L3 speed can be increased to 200 Mhz by setting DPLL at 400MHz (in u-boot).
Occip (working for 2.6.32 NC kernel)
deitiphobia said:
I loaded up the new kernel via Clockwork and all went smoothly with the install. I noticed immediately that my touch sensitivity has decreased. I now have to press and hold just about as long as you would press and hold to bring up a context menu or something. If I don't do that, my touch is ignored and not registered.
Interestingly enough, when I type an email on the keyboard, it recognizes my typing very quickly. No apparent loss of sensitivity when I'm using the keyboard. I wonder why and how that is???
I guess I need to recalibrate the screen again to regain sensitivity.
I did notice that Castle Crashers frame-rate has improved a good bit with the overclock. It's a noticeable and welcome difference.
Angry birds was a bit annoying to play with the loss of screen sensitivity.
Edit: I alleviated the loss of touch sensitivity by installing the LCDDensity app from the Android Marketplace and selecting a density of 200.
Click to expand...
Click to collapse
me too, seems touch for a while(XXms) take effect, less then that screen acts like nothing touch it. this drived me mad when using Gellery, switch pictures give terrible feeling.
i think this relay to the clock scaling, i will check this out using SetCPU.
thanks for your work!
Amazing work with the kernal. I flashed and changed density to 200 in Root Explorer /system/build.prop and it works great.
Also in Spare parts I change both animations to Fast instead of defaults.
occip said:
Hi,
Last month I made some tests with overcloking /undervolting. I was able to push the NC at 1.15GHz, with a little voltage tweaking. 1Ghz was achieved without voltage tuning. The smartreflex technology adjusts automaticaly the OPP voltages to minimize the power consumption. Maybe the L3 speed can be increased to 200 Mhz by setting DPLL at 400MHz (in u-boot).
Occip (working for 2.6.32 NC kernel)
Click to expand...
Click to collapse
Can you add me in GTalk? [email protected]
I have some stuff I'd like to ask about. How did you do the OC? Did you change the actual clock in u-boot so everything scales up? Or did you add more VDD_OPP* steps. I used some of the code I saw before for the Droid's 3430 chipset, using the OPP steps. The stock kernel has steps built in for up to 1.2Ghz, but if I enable them I can't make it boot, at least on my device.
I can't figure out the voltages either, probably because I fail at hex. If I understood that, it would help me a lot.
sugwacee said:
me too, seems touch for a while(XXms) take effect, less then that screen acts like nothing touch it. this drived me mad when using Gellery, switch pictures give terrible feeling.
i think this relay to the clock scaling, i will check this out using SetCPU.
thanks for your work!
Click to expand...
Click to collapse
Hrrm. It sounds like the CPU scaling is staying low, because I see absolutely no change in the touch sensitivity, and I didn't touch any of the code related to it. Try setting the CPU Governor to OnDemand or Performance in SetCPU if it isn't set there already.
Geniusdog254 said:
Can you add me in GTalk? [email protected]
I have some stuff I'd like to ask about. How did you do the OC? Did you change the actual clock in u-boot so everything scales up? Or did you add more VDD_OPP* steps. I used some of the code I saw before for the Droid's 3430 chipset, using the OPP steps. The stock kernel has steps built in for up to 1.2Ghz, but if I enable them I can't make it boot, at least on my device.
I can't figure out the voltages either, probably because I fail at hex. If I understood that, it would help me a lot.
Click to expand...
Click to collapse
diff is available http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Overclock_.5B100.25_untested_on_this_system.5D
occip said:
diff is available http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Overclock_.5B100.25_untested_on_this_system.5D
Click to expand...
Click to collapse
Odd. That's exactly what I've done (with a couple diff voltages) but it won't boot on my Nook. I guess I just got a bad die. Can you explain the voltage values? I know how to increase/decrease the hex number, but how does it correlate to the actual voltage? Like how is 0x38 = 1.35V in a stock kernel?
Definitely going to try this out. Thanks for the work. I'll report back with comments/questions/concerns.
nrune said:
Tried to install via clockwork and I keep getting errors unable to install. an I missing something?
sent from my nookcolor using the xda app
Click to expand...
Click to collapse
+1 I am getting the same. It installs half way then stops with a big exclamation mark, asks me to shut down and restart. I would love to try this. Any ideas?
EDIT: OK got it. CWM updated to 3005 and now it can go into recovery was on 3002 which did not.
This is very much appreciated.
Be expecting some monies so you can buy some candy in the near future.
keep up the good work.
Thanks!
[KERNEL][CM7][Froyo] Dalingrin's OC kernel w/fixed IO perf (quadrant) & 1.2Ghz test
Disclaimer: As always, flash at your own risk.
Background
So, recently there has been alot of debate over why quadrant (and to some extent, system performance) was lower with the OC kernel, as compared to the stock CM7 kernel. (http://forum.xda-developers.com/showthread.php?t=1002504) As part of my examining the problem, i went looking for a solution. Starting from the first OC CM7 kernel, i would run quadrant and see how the performance fared. I finally found the issue appeared in the 3-08a kernel; using that, i rolled back changes until i found the commit remove to fix the issue. Specifically, it seems to be somewhere in the 2.6.29.6 update: https://github.com/dalingrin/nook_kernel/commits/gingerbread-exp
In short, using his source, i have compiled a kernel with fixed I/O performance, and all his other tweaks (interactive gov, etc).
So, I want to make this clear; this is still dalingrin's kernel; in no way do i wish to take credit for his work. But, while he is out, work must go on, right?
Information
Who is this kernel for?
eMMC Froyo and CM7 users
Will this work on SD cards?
It may if you manually replace you uImage, but i cannot guarantee it (since i cannot test it)
Is everything working in this release?
everything like bluetooth and dsp should still be just fine (you may have to do a few hard shutdowns/reboots to kick on BT, like normal).
Kernel Links -3/25/10
OC kernels (up to 1100Mhz, Interactive gov, BT and DSP):
Regular
http://www.mediafire.com/?k00ruvyulf01y64
Extra network features (PPP, etc)
http://www.mediafire.com/?i9h76wn483tk16v
OC kernel (up to 1190Mhz, Interactive gov, BT and DSP):
http://www.mediafire.com/?v6d2jpzaynvchde
For those having problems setting this speed in the CM7 performance settings, give setCPU a try, but don't use profiles. Using set CPU, i am able to get my system stable at 1190, where the CM7 manager instantly locks up.
Feedback
After flashing, please make note of OVERALL system response. The dip in quadrant scores prompted the fix, but i feel that the system is overall better; I would like some more input if others are seeing this as well.
Any and all feedback is welcome, and I will do what i can for support...
Great job man, you and dalingrin both!
Ran 3 quadrant tests on newest nightly (#30)
1. 1856
2. 1700 even
3. Whopping 2030!
Can you be more specific about which network features are in the second choice ?
Thanks !!
ADude said:
Can you be more specific about which network features are in the second choice ?
Thanks !!
Click to expand...
Click to collapse
Um....truth is, i am really not too familiar with it, but looking a the diff between the two configs:
# Core Netfilter Configuration
# IP: Netfilter Configuration
# CONFIG_TUN
# CONFIG_PPP
I am trying out the net kernel again, to see if it is better than the last time i tried it..
Edit: Its looking better than the last time i tried it. Launcher pro hangs for a but on startup, but so far so good after that.
Just started using CM7 last night (w/bottom keys mod, so the nightly is from a few revisions back), but just installed this kernel (the regular version, w/out the Net adds, which I don't need), wiped cache & Dalvik, rebooted, set OC to 1100 and "performance" in CyangenMod Settings and now getting 1918 Quad score...vs. 1372 on the stock kernel with no OC.
I can definitely live with that score...great work to you and dalingrin!!
Thanks for taking care of this while I am gone. Much appreciated.
The update to *.6 is not necessary anyway.
When I get back I will revert the *.6 update and compile some of the netfilter/iptables and tun as modules as this seems to be more compatible than compiling them directly into the kernel.
Madcat, kudos to you. This is perceptibly faster.
great work!
so is this a 2.6.29.5 kernel then?
WOW, scrolling through XDA forum is much smoother than it used to be.
Tried on SDcard, installed by copying uImage to Boot. Reboots to EMMC when trying to load desktop. Back to CM7 stock. I guess I'll wait. Thanks though!
Homer
Can I have the config file for the first? I'm going to play with the kernel a bit.
EDIT: I'm just going to keep my big mouth shut for a while. I hoped it was just a bug with quadrant, but I flashed your kernel just now. There is a huge difference in interactivity. I was playing with the app drawer yesterday and couldn't get it to be smooth with "labels fade in" turned on and a 1000ms or so time on the animation for the app drawer. Now it's perfect every time.
GOOD JOB!
I love Open Source.
Will try this in some minutes. (Nook charging)
Ok, tested it. My scores below.
** QUADRANT SCORES **
Before update, 1100mhz: ~700
After update, 800mhz: ~1500
Now, 1100mhz: 1920
**********************
Awesome!
Just flashed it on mine and seems silky smooth to me. Not real sure there is a big difference, but it is not worse at least. Seems better to me.. Good job Madcat!!
Waiting anxiously for Dalingrin to return to his lab and see what else he can whip up for us..
nice!
i'm getting the same numbers as others (~1800) now. haven't really tested for overall smoothness yet.
will this kernel ever get a nookie version?
cowballz69 said:
will this kernel ever get a nookie version?
Click to expand...
Click to collapse
I have to admit - i said CM7 only, since that is all i have to test it on. If you do want to try it, you don't really risk anything; if it doesn't work, simply reboot to recovery and flash your last working kernel again.
As it is, i haven't really given a good look at what might be different between versions, so i can't give much advice on why it would/wouldn't work on Froyo.
Homer_S_xda said:
Tried on SDcard, installed by copying uImage to Boot. Reboots to EMMC when trying to load desktop. Back to CM7 stock. I guess I'll wait. Thanks though!
Homer
Click to expand...
Click to collapse
Got the same issue with the Net feature kernel. However the other one works fine. Got 1918 Quadrant on SD Card with OC 1100 GHz + interactive gov.
So I guess CM7 performance on SD is not too bad compared to eMMC
@Divine_Madcat : Could you look into the problem of the Net features kernel with SD Card booting? It run into eMMC after the bootanimation.
Thanks much for your work, an action is much better than thousand words !!
I tried both of these from SD card. The non-net features version boots but posted some terrible #s for me (<700 Quadrant and ~6-7 Linpack); the net features version doesn't boot. Is there something special I need to do with the first kernel to see the benefits? I checked and was clocked to 1.1GHz in CM settings.
victle said:
@Divine_Madcat : Could you look into the problem of the Net features kernel with SD Card booting? It run into eMMC after the bootanimation.
Thanks much for your work, an action is much better than thousand words !!
Click to expand...
Click to collapse
Ill be happy to take a look, but can't promise anything right away.
SCWells72 said:
I tried both of these from SD card. The non-net features version boots but posted some terrible #s for me (<700 Quadrant and ~6-7 Linpack); the net features version doesn't boot. Is there something special I need to do with the first kernel to see the benefits? I checked and was clocked to 1.1GHz in CM settings.
Click to expand...
Click to collapse
hmmmm.. that doesn't sound right at all. May i ask which nightly you are using? Right now, i am on nightly 27, and haven't seen anything like that (in my case, it either works, or just boot loops, if i set the clock too high).
AOSP Kernels for HTC's 8x50, 7x30, and 8x60 Devices
Also available for the Motorola Xoom
Tiamat kernels are designed for use on all ROMs that are built from the AOSP source code. This includes ROMs built from MIUI, CyanogenMod, and others.
Tiamat receives no support for use with ROMs based on HTC's Sense - use at your own risk.
Click to expand...
Click to collapse
Tiamat Kernels
You can find full details about Tiamat Kernels at our website. The site is up and running and serves as a more centralized location to get updates, downloads, and changelogs for all Tiamat Kernels. There is no forum or Registration, it’s just a more convenient way to keep things organized as we work to add support for more devices.
Click to expand...
Click to collapse
Support
Join the Tiamat Kernel developers on IRC at irc.freenode.net, #tiamat. Support and questions are generally handled faster there than the forums. You can easily join via webchat here.
Click to expand...
Click to collapse
Special Thanks to:
toastcfh, slayher and the CyanogenMod team for the base kernels and everything else they do for the Android community
bcnice20 for generally being awesome
TeamWin for also generally being awesome
netarchy, chad0989, cuviper, and invisiblek for some great code
intersectRaven and redstar3894 for the Mjolnir compiler
JasonK75 for updating threads
Click to expand...
Click to collapse
Quick Links
Click to expand...
Click to collapse
8x50 Changelog
8x60 Changelog
7x30 Changelog
Downloads
FAQ
Source Code
reserved for later
This kernel has been around for the Inc and the Evo. Now I'm bringing it to the N1 and the Desire!!
Great stuff, always nice to have more kernel choices
MOD : Can you post only Nexus One kernel on your post please (more readable)
Had been having some wifi issues this past week using cm7 nightly along with various kernels. Wifi was frequently dropping or just very slow. Spent most of Sunday screwing with my home network which seems stable now. I think comcast must have been doing something. however, my phone wifi was still poor. installed this kernel last night and so far phone is performing as it should on wifi. the difference was immediate. not sure whats going on. cant comment on battery life yet, but it's looking very good through this mornings use. Thank you!
allofusjw said:
Had been having some wifi issues this past week using cm7 nightly along with various kernels. Wifi was frequently dropping or just very slow. Spent most of Sunday screwing with my home network which seems stable now. I think comcast must have been doing something. however, my phone wifi was still poor. installed this kernel last night and so far phone is performing as it should on wifi. the difference was immediate. not sure whats going on. cant comment on battery life yet, but it's looking very good through this mornings use. Thank you!
Click to expand...
Click to collapse
I'm glad it's working for you, but that is strange... The only change I make to wifi from CM is undervolting it. And now that I think about it, I may have forgotten to bring that tweak over to the n1 and desire...
Can you summarize how your kernel differs from the others (CM, pershoot, wildmonks, redstar).
mr_raider said:
Can you summarize how your kernel differs from the others (CM, pershoot, wildmonks, redstar).
Click to expand...
Click to collapse
Versus the main CM kernel, this has unrestricted overclocking, HAVS, smartass, undervotling, sysfs interface and several other tweaks/improvements. I don't have a N1 and honestly dont know anything about the other kernels out there for it. The kernel started on the Inc and Evo, mostly around MIUI, and I was asked by a few people to bring it over to the N1 and Desire, so I figured I would post it up for everyone.
Hi all,
Been running this since 0800 this morning (its now 1800) no problems at all.
Can't say its faster or better on the battery for sure but its certainly no worse than CM stock.
Whats the smartass govenor? Just the same as on demand as it seems to replace it?
Oh, just one thing, although it has the option (in SetCPU) to go down to 128mhz, I've not seen it go lower than 245mhz which makes me wonder if its clocking down to 128 with the screen off.
Anyone else?
bryanchapman9999 said:
Hi all,
Been running this since 0800 this morning (its now 1800) no problems at all.
Can't say its faster or better on the battery for sure but its certainly no worse than CM stock.
Whats the smartass govenor? Just the same as on demand as it seems to replace it?
Oh, just one thing, although it has the option (in SetCPU) to go down to 128mhz, I've not seen it go lower than 245mhz which makes me wonder if its clocking down to 128 with the screen off.
Anyone else?
Click to expand...
Click to collapse
The on demand governor was removed to force the default to smartass (the default is usually set to on demand by the ramdisk and is not affected by setting the default in the kenrel), but the two are not similar. Smartass was built off the interactive governor.
As for the 128Mhz floor - that is something finicky about the smartass governor. It should drop to 128 on any other governor though.
Smartass Governor shows real potential...thanks for this!
what about the wonk?
From what I gather the wonk is due to something in CM7 kernel. I also noticed that it is absent from stock 2.3.3 and also absent from AOSP builds.
Has anyone tried CM7 with this kernel?
thanks for the N1 kernel.
I'll try ASAP.
I will try this kernel now, thanks for posting. New kernel cooks are always welcomed.
After about 18 hrs on this kernel, the results are pleasing.
Extremely stable on the Smartass Governor, which is surprising because I've had friends compile me kernels incorporating this governor, and the end result = unusable.
Battery life seems fantastic so far.
Clocked 128-998. No profiles.
Thank you again for this kernel.
Results on N1
I have been running this kernel for 24hrs at 128/1228 and it's been running great with smartass selected on my AT&T N1. I tried going even higher than 1228 but that causes it to crash immediately (I'm surprised it can even handle 1228.) Linpack is a little low at 23 compared to other kernels that can get up to 40. Quadrant also comes up behind at only 1051.
tried going at the highest setting & it crashed my N1 , BACK TO RESDTAR'S kernel .
Been using the kernel for a few hours, Kernel seems stable but definatly doesnt feel snappy.
phewizzo said:
Been using the kernel for a few hours, Kernel seems stable but definatly doesnt feel snappy.
Click to expand...
Click to collapse
same here, got some freeze
btw oc at 1267 without any crash
I found a solution to fix the Doom kernel reboots for those who are unable to download stock roms from HTC (Rogers Customers). Requires CWM Recovery.
1. Download stock kernel here - http://www.box.com/s/7dc3bf2adc9e2f05b717
2. Unzip archive
3. Move Zip file to SD card
4. Reboot into bootloader fastboot reboot-bootloader
5. Flash the img file fastboot flash boot name.img
6. Go into CWM and install the zip.
This solved my problem, hopefully it works for you guys too.
This should work on ALL devices not just Rogers
it doesn't actually solve the kernel issues...
your just replacing him.
i still think his kernel has a lot more potential than the stock.
It fixed my issue.
I care more about having a functional tablet than a kernel that may have more potential but is buggy as hell.
i agree. and i'm running the stock as well.. just wished the doomlord one would work as well.
Hi there,
Noob user here.
I got HTC JetStream from previous owner with doomlord Kernel on it.
Tablet is constantly crashing for no logical reason which leads me to believe that the kernel is causing this issue.
I would like to flash back to the stock kernel only as my device (Rogers) is running a stock image.
I am having difficulties to follow your instructions.
Wold somebody be so kind to post more detailed process steps to complete this kernel flashing back to stock.
Thank you very much.
I had the same random reboots using Doom's kernel until i overclocked it to the maximum. It's been almost 2 weeks since i experienced any reboots....
Sent from my Inspire 4G using xda premium
could you be more specific?
did you set both the minimum and the maximum to the maximum?
did u change the voltage?
Yes I changed the min & max all the way to max.. not sure if it will have some long term effects on my tablet, but it's been working great for a while now.
Sent from my HTC PG09410 using xda premium
lol... so the "solution" to the DooM kernel reboots is to not use the DooM kernel. Brilliant.
If I find some time this weekend, I'll try maxing out the O/C though and see how it goes, as I do find the DooM kernel snappier, even at stock speeds.
craig0r said:
lol... so the "solution" to the DooM kernel reboots is to not use the DooM kernel. Brilliant.
If I find some time this weekend, I'll try maxing out the O/C though and see how it goes, as I do find the DooM kernel snappier, even at stock speeds.
Click to expand...
Click to collapse
You do realize that by doing that you are running your kernel at max speed constantly which means additional heat, stress and wear on all systems?
ATT Intruder said:
You do realize that by doing that you are running your kernel at max speed constantly which means additional heat, stress and wear on all systems?
Click to expand...
Click to collapse
No, it won't run at max speed constantly unless I set the governor to "performance" mode. In "interactive" mode, which I believe is the default, it will still clock the CPU at its minimum value until the tablet needs more CPU resources, such as when scrolling, loading a webpage, playing a game, etc.
But yes, I'm aware of the risks of overclocking. I've overclocked every HTC device I've had very few problems (my One XL has exhibited some bootloops, so I've stopped O/C'ing it.)
craig0r said:
No, it won't run at max speed constantly unless I set the governor to "performance" mode. In "interactive" mode, which I believe is the default, it will still clock the CPU at its minimum value until the tablet needs more CPU resources, such as when scrolling, loading a webpage, playing a game, etc.
But yes, I'm aware of the risks of overclocking. I've overclocked every HTC device I've had very few problems (my One XL has exhibited some bootloops, so I've stopped O/C'ing it.)
Click to expand...
Click to collapse
I'm running 1.83 ghz ondemand with also the lowest setting for the min freq setting. I will increase it to 1.944ghz ondemand as the max setting and increase my min setting to 756Mhz on deadline, and see if the reboots stop, otherwise I will have to install the stock kernal.
I am just wondering if I install the stock kernel on top of my OziMood rom, if this will cause Rom problems?
Any thoughts on this?
globalgpj said:
I'm running 1.83 ghz ondemand with also the lowest setting for the min freq setting. I will increase it to 1.944ghz ondemand as the max setting and increase my min setting to 756Mhz on deadline, and see if the reboots stop, otherwise I will have to install the stock kernal.
I am just wondering if I install the stock kernel on top of my OziMood rom, if this will cause Rom problems?
Any thoughts on this?
Click to expand...
Click to collapse
I have mine on max: 1.62 ghz , min: 594 onDemand and it hasn't crashed in two or three days. So we'll see. Now to answer your question, if you want to flash back to stock on that Rom you'll have to install the stock WiFi modules from recovery. After that everything should work normally.
AlexFG said:
I have mine on max: 1.62 ghz , min: 594 onDemand and it hasn't crashed in two or three days. So we'll see. Now to answer your question, if you want to flash back to stock on that Rom you'll have to install the stock WiFi modules from recovery. After that everything should work normally.
Click to expand...
Click to collapse
Thanks for that.
So far, I haven't had anymore reboots.
Increasing the minimum seems helpful.
I get plenty of battery life, so I am really happy about this for now.
Just a quick update.
I've been running 1.944 GHz as my high setting and 756 GHz as my low setting for some time now and I have to say, no reboots, no lag, super fast and stable.
Sent from my HTC Jetsream using xda premium
Nice, I'll try those frequencies on mine. Thanks for sharing.
Sent from my Galaxy Nexus using xda app-developers app