This is based off the latest Samsung kernel source (DI18) with some of my tweaks. Overclock to 1.2Ghz @ 1.25V is maximum. That is 50mV LESS than the voltage given in a stock kernel for 1Ghz!
This kernel is UNBELIEVABLY fast! Average Linpack scores of 9.5+ mflops & Quadrant scores of ~950-1050.
Battery life is great on this beast. Yesterday I ran it all day starting around 8AM, and I didn't hit low battery until 10PM. Thats the furthest I've ever gone, and almost double stock.
Just flash the zip in recovery. I have had no issues with this kernel, nor have any of my testers. This kernel is already included in AOSP Magic & Tha Boss ROM v.2 or above (it was actually made special for Tha Boss at the request of it's maker @KyleCole90). If you're running one of those ROMs you don't need to flash this, unless I release a new version here.
Use SetCPU to set the clock. You'll have to re-do the autodetect (press Menu, Choose Device, Autodetect) for it to decide the new speeds, and you may have to do it a few times. Also, if you flash a different kernel, or update then you'll have to re-detect as well.
Props to @Decad3nce for the BFQ patch from his Hero kernel, @Supercurio for his Voodoo Color mod for the i9000 I just ported it to Epic, Skeeterslint for helping me solve a problem with my ramdisk, @KingKlick92 for a baseline of safe values for voltages from his Vibrant kernel, @Herver for the conservative tweaks, and to Unhelpful on the Captivate forum for his helpful (*rimshot*) source for his Captivate overclock kernel.
If you have any questions or problems (shouldn't be any ) then Twitter me or email me. Also, I don't ask for donations, but if you're feeling generous and you like my work please check out my apps on the Market or send me a donation via the Paypal Donate link in my signature.
-------------------------------------------------------------------------------
Root Issues On Some ROMs:
There are some root issues on some ROMs due to the fact that they still use the old JoeyKrim root. It was never intended to be a permanent root method. Once we got kernel root it became moot. I recommend you ask your ROM dev to fix this, instead of complaining to me
Here's how to fix it if your ROM dev doesn't (just run this from a shell/command prompt, you must have ADB set up):
Code:
adb shell
remountrw
rm /system/bin/playlogo
rm /system/bin/jk-su
mv /system/bin/playlogo-orig /system/bin/playlogo
-------------------------------------------------------------------------------
Changelog:
MixUp-20101110-1036 -- Released 11/10/2010 10:37PM CST:
Added Smartass governor. Still beta. Not default, but available. Similar to interactive, but more responsive & better battery supposedly. Thanks to a dev in the Hero forums whose name I can't remember.
CIFS support
VooDoo Sound support. Still beta.
1.3Ghz & 1.6Ghz OC!
Light & CPU tweaks from Devin
Several more small tweaks I can't remember
This version is beta! I have NOT tested this one at all! I'm running FroYo atm, and I can't test this kernel since it isn't .32. Let me know of any (probably a few) bugs.
MixUp-20101024-847 -- Released 10/24/2010 8:47PM CST:
Switched back to conservative scheduler by default. Interactive is still there, but not default. It'll get set to default when someone fixes interactive.
Patched up to 2.6.29.6 (thanks @Nullghost)
Various scheduler tweaks, backported from newer versions
New BusyBox version
Back camera tweaks, sharpness & saturation upped a notch. I think its better, but if you disagree then take them down a notch in camera settings.
Front cam tweaks. Samsung -- People != blobbish vampires. Sharpness & color upped. No more pale blobs of Play-Doh.
RNDIS! Finally! DevinXTreme got this one goin.
Speaking of Devin, this is now a collab between him & I, with some (credited) kanging from @Nullghost
Optical sensor tweaks. I know, I know, they keep coming. It's good, I promise. I think I FINALLY fixed it.
IMPORTANT! Calibrate your battery after flashing this kernel, else it will decrease! To calibrate, charge your phone all the way (or insert a full battery), wipe battery stats in Clockwork, let it drain to ZERO, plug it in and charge to FULL! Do NOT put in a full battery after the discharge. Your battery should really improve after this.
MixUp-20101017-855 -- Released 10/17/2010 10:05PM CST:
New CPU tables again. Alleviate radio sleep issues. Anything left is just DI18's fault
Actually capped at 1Ghz at boot now, just change with the OC program of your choice
No more no-voodoo version. Voodoo is brightness issue free now, and its too much hassle to maintain two kernels. It may return eventually if I get around to integrating it to my config
Interactive CPU governor added & set as default. Ondemand still available as are the rest.
Fixed lots of config errors, depriving you of EXT4 & BFQ
More optimization for Cortex-A8
MixUp-20101005-809 -- Released 10/5/2010 8:09PM CST:
New CPU Tables (MOAR BATTERYZ!!11!)
More conservative tweaks from Herver (BATTERYZ!!!)
Updated to DI18 sources
New ramdisk
Limited to 1Ghz until changed in setcpu now, better battery by default & more stable for some users. Just up it in SetCPU if you want OCing
Tweaked minimum brightness levels
Screen doesn't fall to minimum brightness automatically until 1% battery now. Used to be 5%. You're welcome
I left up the old DG27 kernel for people who haven't yet upgraded to DI18, just in case the DI18 one causes issues for them
MixUp-20100926-323 -- Released 9/26/2010 3:55PM CST:
Switched to BFQ scheduler. See here for details.
Tweaks to the default Conservative governor. Scales up sooner to avoid hangups and scales down sooner to save battery
Added the Voodoo Color option (thanks @Supercurio for creating it, I just ported it to Epic). There are some issues with it as described at the link. If you don't like it, use the one without it instead of complaining, kthx
Fixed root issues finally, if you experience them you still have the JoeyKrim exploit installed. Bad user.
Undervolted 50 more mV across the board, battery life on this beast is amazing
Added Superuser Permissions app (thanks for the help, Skeeterslint)
adbd now runs as root by default. That means "adb shell" drops you straight to # instead of $
EXT3/EXT4 FS support included in kernel. Do with it what you will.
Changed to a different floating point emulation method that *may* yield better performance
NEON support in the kernel
MixUp-20100921-655 -- Released 9/21/2010 6:55PM CST:
Added Clockwork & ROM Manager support.
Judging from the reports I've heard and things I've seen, I'ma call this one Stoopid Fast. Just cuz it sounds cool
MixUp-20100920-630 -- Released 9/20/2010 6:30PM CST:
adbd now runs as root. This allows adb push to /system. It also enables adb remount to remount /system to RW or RO, but there is something missing from the ROMs that don't allow adb remount yet. I'm working on it.
Small tweaks to voltage table (I think) so possible better battery life on this one, but don't hold me to that. I'll be fine tuning them later on some more.
-------------------------------------------------------------------------------
Source:
My source is now on GitHub.
Stock DI18 Samsung kernel branch here. This is for beginning kernel devs. It's totally stock. Feel free to fork this or download the tree to start your own kernel base.
MixUp VooDoo is here. This has all my changes applied and I will push all my changes to it.
I did not have time to upload my source for the non VooDoo kernel today, I have the local repo done, but I only have access to a high speed connection when I go into town, and I didn't have time to upload this one while I had access. Really though, if you want the source for a non-Voodoo kernel its identical to this, just change the "drivers/video/samsung/s3cfb_tl2796.c" and "drivers/video/samsung/s3cfb_mdnie.c" files with the ones from the stock repo. Everything else is identical.
For devs wondering how I made ADBD run as root, I'm sure you already know how to do this, but if not do the following. Go to your ramdisk, open up default.prop, and then:
Change ro.secure=1 to ro.secure=0
Change ro.debuggable=0 to ro.debuggable=1
Change persist.service.adb.enable=0 to persist.service.adb.enable=1
Then recompile. That's it.
-------------------------------------------------------------------------------
And just to protect me:
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
Overclock kernels carry an inherent risk. You're pushing your hardware further than it's meant to go. Everything should be safe, and I've tested it myself and I trust it on my phone. But that doesn't mean it's perfect.
If *you* screw up and blame me, I will point at you and laugh. Deal with it.
i think i'll wait a bit to see if this is safe to flash
If I flash this kernel will I get those black screens like I did with Heros rom?
Sent from my SPH-D700 using Tapatalk
plmiller0905 said:
If I flash this kernel will I get those black screens like I did with Heros rom?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I don't notice them, but if you got them on his ROM you may well see them here too since its the same kernel. I recommend you set it on OnDemand scheduler with SetCPU instead of Conservative or whatever the default is
Geniusdog254 said:
I don't notice them, but if you got them on his ROM you may well see them here too since its the same kernel. I recommend you set it on OnDemand scheduler with SetCPU instead of Conservative or whatever the default is
Click to expand...
Click to collapse
Ok sounds good...what about having to hurry up and put the phone to sleep on the intial startup to stop the bootloops, do I have to do the same for this kernel as well?
Sent from my SPH-D700 using Tapatalk
plmiller0905 said:
Ok sounds good...what about having to hurry up and put the phone to sleep on the intial startup to stop the bootloops, do I have to do the same for this kernel as well?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Probably. I've gotten away without doing it, but the last couple boots I've had to. I'll build my own kernel later today and see if that fixes it. Just gotta download the Samsung source and set up a build environment for this instead of my Evo
Geniusdog254 said:
Probably. I've gotten away without doing it, but the last couple boots I've had to. I'll build my own kernel later today and see if that fixes it. Just gotta download the Samsung source and set up a build environment for this instead of my Evo
Click to expand...
Click to collapse
Ok I'll wait to flash this then cause trying to hurry up and put the phone into sleep mode at startup is hell. I'll be looking forward to your kernel and thanks for your hard work.
Sent from my SPH-D700 using Tapatalk
This kernel boot loops your phone. Even with a battery pull. I suggest flashing back to the stock kernel with Odin3.
casual864 said:
This kernel boot loops your phone. Even with a battery pull. I suggest flashing back to the stock kernel with Odin3.
Click to expand...
Click to collapse
are you putting it to sleep as soon as it boots??
Good so far thanx for posting it
BopChie said:
are you putting it to sleep as soon as it boots??
Click to expand...
Click to collapse
Even if I do that, whenever I put the phone to sleep it won't turn back on. Forcing me to do a battery pull.
casual864 said:
Even if I do that, whenever I put the phone to sleep it won't turn back on. Forcing me to do a battery pull.
Click to expand...
Click to collapse
Hmm did you put SetCPU at Set on Boot? I've seen that cause issues before. I know that it's working fine for me, although I occasionally have to do the instant-sleep trick on boot, but not always.
I know that it works for me, and it's reported working in the og. Grimey Goods thread as long as you do the instant-sleep. YMMV
so i dont set setcpu on boot or i do?
evoguyfhp said:
so i dont set setcpu on boot or i do?
Click to expand...
Click to collapse
You can give it a shot. I have it set on boot and it works for me but it's caused problems in the past if you set weird freqs. YMMV
Just posted a new version. Yes, I actually compiled this one
Let me know how it works. I'm going to bed. It's late here. I'll check feedback in the morning and respond to them tomorrow after class.
Enjoy
Geniusdog254 said:
Just posted a new version. Yes, I actually compiled this one
Let me know how it works. I'm going to bed. It's late here. I'll check feedback in the morning and respond to them tomorrow after class.
Enjoy
Click to expand...
Click to collapse
changelog?
[email protected] said:
changelog?
Click to expand...
Click to collapse
See OP. No more issues on boot (don't worry about locking and unlocking as soon as it boots anymore) and no wake issues. To make sure you have no wake issues, use the "ondemand" governor. That's the only one I've tested with. Can't guarantee that on conservative or powersave or any of the others. You can change them in SetCPU
Got It.. D'Oh..
PlankLongBeard said:
Only thing I ask for is a update.zip for returning to stock DI07 Kernal. After that all is well.. (BTW.. Thats for the Just In Case) Makes it Easier!
Click to expand...
Click to collapse
clockwork backup?
BopChie said:
clockwork backup?
Click to expand...
Click to collapse
Yeah, will be doing so, I forgot..
Related
This kernel module allows you to run any stock HTC Froyo kernel with lowered CPU voltages. Reducing voltage decreases power consumption by the CPU, thus lowering heat and increasing battery life.
INSTALL:
You need root or an unrestricted recovery image (e.g ClockworkMod) to install this. The default settings decrease voltage by 75-100 mV which seems stable on my device (HTC Desire) and is reported to be fine on the EVO. Just download the attached file and select it from recovery or ROM Manager.
I've built "update.zip" files for the EVO 4G with Linux kernel versions 2.6.32.15-g746f4f0, 2.6.32.15-ge2fb08e, and 2.6.32.15-g59b9e50. You can check your kernel version in Settings->About phone->Software information.
Other HTC devices running Froyo are supported. If you have a different device, please give me the full version number and I can add an update.zip for it.
Full details and source are in the original thread in the Desire forum:
[KERNEL] Undervolt driver for the stock HTC kernel for Desire and others (2.6.32.15)
Update, 2010-11-22: Added driver for 2.6.32.15-ge2fb08e.
Update, 2010-11-23: Added driver for 2.6.32.15-g59b9e50.
recant: love this idea when trying to keep this stock
Sounds like it would go well with Fresh's new rom.
ericwgarza1 said:
Sounds like it would go well with Fresh's new rom.
Click to expand...
Click to collapse
+ 1 on that I agree
sweet I like. Does it change the kernel version?
Too weak... funny considering there is more work involved in setting this up than most linux guys even do on a pc... let alone a phone.
tatnai said:
what's this here? sounds like an add on for those too weak at heart to flash a modded kernel. will likely find some friends, strong work.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
tatnai said:
what's this here? sounds like an add on for those too weak at heart to flash a modded kernel. will likely find some friends, strong work.
Click to expand...
Click to collapse
Maybe not. I run the netarchy kernel but don't OC because it seems to crash at random times. I use it because the battery life is better than stock.
I'll revert to a clean back-up and give this a try just for giggles.
I would like to see some results.
I say that because I have tried a few havs roms and get worse battery life.
I think what a lot of people don't realize unless they are heavily into overocking is that microadjustments just dont have much effect there needs to be some substantial drops to really have any effect on battery and heat.
I realize that this is no desktop or laptop cpu, and that this cpu is based off such low voltages but such minor voltage adjustments, 80-100mv just arent going to have the desired effect unless that equates to a "substantial" voltage drop.
Not to mention the fact that most of you are going to overclock your phone without the faintest idea that doing so, even with a lower cpu voltage, will still cause worse battery life. This is a fact.. to argue it is futile. Its the nature of the beast.. do some reading and find out for yourself.
You can overcome some things by using on demand overclocking but you have to do extensive testing to find the sweet spot.
fr4nk1yn said:
Maybe not. I run the netarchy kernel but don't OC because it seems to crash at random times. I use it because the battery life is better than stock.
I'll revert to a clean back-up and give this a try just for giggles.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Nice work. I'm not interested in oc'ing, nor flashing a custom kernel. I may give this a go after a few others check in w/ results. I just want to know that it's stable.
I went to your other thread and saw the source. Clever solution, nice work. I really do like that you wrote a device to /proc that does a little more than report the frequencies back. This will make it very easy to write some scripts, or even a UI, that lets me tweak the settings. Hopefully I have some time to work on that in the upcoming weekends.
Will take a look at this first chance I get. Trying to finish my battery logger since everything available now doesn't log exactly what I want to know. Kudos.
Does this make HAVS obsolete ?
iscaela said:
This kernel module allows you to run any stock HTC Froyo kernel with lowered CPU voltages. Reducing voltage decreases power consumption by the CPU, thus lowering heat and increasing battery life.
INSTALL:
You need root or an unrestricted recovery image (e.g ClockworkMod) to install this. The default settings decrease voltage by 75-100 mV which seems stable on my device (HTC Desire) and is reported to be fine on the EVO. Just download the attached file and select it from recovery or ROM Manager.
I've built "update.zip" file for the EVO with Linux kernel version 2.6.32.15-g746f4f0. You can check your kernel version in Settings->About phone->Software information.
Other HTC devices running Froyo are supported. If you have a different device, please give me the full version number and I can add an update.zip for it.
Full details and source are in the original thread in the Desire forum:
[KERNEL] Undervolt driver for the stock HTC kernel for Desire and others (2.6.32.15)
Click to expand...
Click to collapse
Undervolting meaning only when screens off or on and off ?
I installed and will get the best battery life yet. Better than when I was with King and other kernels....thanks!!!
Anyone have any results from flashing this yet? How is battery life? Any stability issues?
look4wisdom said:
Anyone have any results from flashing this yet? How is battery life? Any stability issues?
Click to expand...
Click to collapse
No stability issues and it seems to help on battery a little bit but I really can't tell a big deference. I was expecting for it to help out more. Thanks anyways OP for the share
i did say those little microvoltages aint gunna make any difference.
plus if you try to overclock you just cancelled any lowered voltages and actually cause higher power draw than stock mhz at stock voltages.
higher mhz equals higher power draw whether you have it undervolted or not.
you have to make a signifigant drop in voltage to make any difference at all. let alone if you try and overclock.
not trying to dog the guy who discovered this i am just sing plain and simple math, heat, and electronic voltages.
Sent from my PC36100 using XDA App
question there a some diference between this kernel and the once from King and Net, talking about battery life and performance
juancaperez2000 said:
question there a some diference between this kernel and the once from King and Net, talking about battery life and performance
Click to expand...
Click to collapse
This isn't a kernel its just a couple of files that go with the kernel. One file for initial boot ect/initd and a .ko file that goes in system/lib/module folder.
I have an Evo, [email protected] #11. I would like to try it. Please build an update.zip to support it.
Cheers.
snovvman said:
I have an Evo, [email protected] #11. I would like to try it. Please build an update.zip to support it.
Cheers.
Click to expand...
Click to collapse
OP
Sent from my EViO + PURE= PURE Baked EViO
this kernel is based of of the newest .34 kernel in the latest cm6 nightly
I've included Intersect Ravens exact Havs modifications will probably add bfs here soon too.
Overclockable up to 1.13 ghz
Conservative cpu gov. is enabled by default as it seems to run best with the .34 kernel for me anyway.
BFS 318 is included in the BFS kernel also brought back ondemand cpu scaling in BFS version
Before flashing its best to disable setcpu in superuser permissions then reenable it after flashing..
Downloads
http://bit.ly/cwbP9H v1.0 bfs & non-bfs
Mirrors
http://bit.ly/bDaKeA v1.0 bfs version
Kernel Source http://github.com/bcnice20/supersonic-2.6.34
I'd like to thank toast maejrep and cyanogen for all there hardwork in getting a .34 kernel on the evo.
netarchy for all his fps tweaks
intersectraven for his HAVS modifications
if i left anybody out just ask ill add..
I take it this is for CM6 roms?
INteresting...
yes this is for cm6 roms but it should work just as kingklicks sense kernel does with the graphical glitches and all but it should boot havent tried yet though
YAY! Booting now
Just flashed and having the black screen issue right away, probably going to nandroid back..
TheMike1 said:
Just flashed and having the black screen issue right away, probably going to nandroid back..
Click to expand...
Click to collapse
did you disable setcpu in superuser permissions before flashing and are you on cm6
bcnice20 said:
did you disable setcpu in superuser permissions before flashing and are you on cm6
Click to expand...
Click to collapse
CM6: Yes.
Disable SetCPU prior to flash: No.
Is that known to cause this issue? I did notice it on KingKlick after a while and decided to do a fresh wipe and install of CM6 9/18 nightly because I was annoyed by it.
Prior to that I ran several iterations of Snap w/o disabling SetCPU and was fine.
TheMike1 said:
CM6: Yes.
Disable SetCPU prior to flash: No.
Is that known to cause this issue? I did notice it on KingKlick after a while and decided to do a fresh wipe and install of CM6 9/18 nightly because I was annoyed by it.
Prior to that I ran several iterations of Snap w/o disabling SetCPU and was fine.
Click to expand...
Click to collapse
well i removed a couple of cpu governors and changed the default govenor to conservative so that may cause problems with setcpu so disabling then reenabling should help with that problem
BFS version should be out very soon to
TheMike1 said:
CM6: Yes.
Disable SetCPU prior to flash: No.
Is that known to cause this issue? I did notice it on KingKlick after a while and decided to do a fresh wipe and install of CM6 9/18 nightly because I was annoyed by it.
Prior to that I ran several iterations of Snap w/o disabling SetCPU and was fine.
Click to expand...
Click to collapse
Ok bud, disabled SetCPU and just flashed again, let's see how this goes
Ok, flashed, no black screen problem now
Was surprised to see PowerSaver, Conservative, Performance only!
fps2d seems to be getting an average of 52/53 with 5+ StdDev on conservative. Stock CM6 OnDemand was getting 54fps with ~2 StdDev. Not sure what tweaks were made but seems from my VERY INEXPERIENCED eye as if Conservative jumps around a bit more than I am used to..
This is still the first iteration of this kernel and It is exciting to see yet another kernel in the mix to keep things interesting.
Thanks for your work bcnice I might play with this for a little bit more to see the battery life, how long have you been running it?
eit: ran a couple more iterations, again from my novice, unintelligent, inexperienced eye it seems to be less consistent and to jump around a bit more, I don't know just an observation from looking at how it reacts. Again thank you for the hard work it is VERY APPRECIATED!
55/2.79
54/3.48
54/4.49
54/3.0
TheMike1 said:
Ok, flashed, no black screen problem now
Was surprised to see PowerSaver, Conservative, Performance only!
fps2d seems to be getting an average of 52/53 with 5+ StdDev on conservative. Stock CM6 OnDemand was getting 54fps with ~2 StdDev. Not sure what tweaks were made but seems from my VERY INEXPERIENCED eye as if Conservative jumps around a bit more than I am used to..
This is still the first iteration of this kernel and It is exciting to see yet another kernel in the mix to keep things interesting.
Thanks for your work bcnice I might play with this for a little bit more to see the battery life, how long have you been running it?
eit: ran a couple more iterations, again from my novice, unintelligent, inexperienced eye it seems to be less consistent and to jump around a bit more, I don't know just an observation from looking at how it reacts. Again thank you for the hard work it is VERY APPRECIATED!
55/2.79
54/3.48
54/4.49
54/3.0
Click to expand...
Click to collapse
conservative seems to get better battery life and i havent seen any real time reason not to use it over ondemand and interactive is a bit buggy i can throw them back in there if its preffered though
dont forget ive yet to add BFS =)
bcnice20 said:
conservative seems to get better battery life and i havent seen any real time reason not to use it over ondemand and interactive is a bit buggy i can throw them back in there if its preffered though
dont forget ive yet to add BFS =)
Click to expand...
Click to collapse
I have seen some nice results with tweaked OnDemand, not sure what your thoughts are on that?
I am excited to add BFS, I am surprised this thread doesnt have more attention, Id be happy to hang out and let you know what I am experienceing with the Kernel. I will also love to flash the BFS version. Would love to see some more people in here flashing this!!!!
Would love to try it. Just got latest nightly running with snap Turbo and I am loving it. I will stay tuned to the thread tho.
Bfs version compiling now will have it uploaded soon sry for the wait
BFS version up put ondemand CPU scaling back in there too
No go with sense virus rom, gave me screen tweaks.. It was worth a shot tho thanks for the work
Sent from my phone... I think useing Tapatalk?
luckylui said:
No go with sense virus rom, gave me screen tweaks.. It was worth a shot tho thanks for the work
Sent from my phone... I think useing Tapatalk?
Click to expand...
Click to collapse
This is meant for cm6 roms I really have no clue as to how to fix the screen issues. With sense yet.....
I will flash the bfs tomorrow things have been good so far with the original
bcnice, the file sharing site is blocked at my work, can you link it up on another site?
PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Link to bcnice20's 1.5ghz kernel: http://forum.xda-developers.com/showthread.php?t=941728
If that doesn't work, try flashing over his 1.8ghz kernel(This is what worked for me, bcnice, if you want me to take down this link just let me know.) - http://thebcblends.com/shift/kernels/Sense-1.8ghz-bfq-test1.zip
Table of contents:
Intro
Features/what this includes
Why it's labeled unstable
Disclaimer
Latest kernels
Instructions for using swap
Governor exlainations
Governor strategies
Recommended apps
Locating cpu% Eaters && other negative items towards battery life
FAQ!
Changelog
Stable/safe voltage kernels
Notes
Source
Credits
Intro: I'm scaryghoul.
What this includes
Swap
BFQ I/o scheduler
Extreme undervolt
Overclocked & underclocked values
HW3D enabled
Sleepers disabled
Smartass governor
New Scary governor!
Tweaked conservative governor
and much more(All of bcnice20's kernel)
Why it's labeled unstable: So I don't get people poking me in the eyes with spoons if/when it freezes up. It actually works quite well, but since I heavily undervolted an undervolted kernel, it is bound to not be 100% stable(It is about 90% stable =P)
Disclaimer: What everyone else puts in kernel threads, about me not being responsible, ect.
Latest kernels
The voltages of the superUV will not work for everyone, if they don't work for you, then try the builds labeled stable
Recommended speeds 245-800mhz or 245-1ghz on scary governor && no setcpu profiles
Scarykernel 1.8 suv - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Suv.zip
Scarykernel 1.8 stable undervolt - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Instructions for using swap
For a swapfile do something like this.
dd if=/dev/zero of=$Swapfile bs=1048576 count=$Size
Where $Swapfile is the location of the file you want, and $Size is the amount of mb for swap you want to use.
Then type
mkswap $Path
swapon $Path
Replacing $Path/$Size with your own values of course, so if I wanted 20mb of swap I'd execute the commands
dd if=/dev/zero of=/sdcard/swapfile bs=1048576 count=20
mkswap /sdcard/swapfile
swapon /sdcard/swapfile
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/smartass-governor-info ) - "is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Governor strategies
Conservative - Upthreshold 85, downthreshold 60
Smartass - Sleep max 245760Hz, Ramp up at 384000Hz at a time, up threshold 90, downthreshold 60
Scary - Upthreshold 80, down threshold 45, sleep max 245760Hz, sleep min, 122880Hz
Recommended apps =)
Zdbox - Great toolbox app, just don't let it run in your notifications bar, it's a cpu eater
Setcpu/Nofrills - Apps that help manage your cpu/profiles/ect.(I don't use them but they're pretty okay)
Perfect system or Elixer widgets - Widgets that monitor battery, current, cpu%, cpu speed, and more(Great for battery guru's)
Adw ex - Smoothest/fasted/lightest ratio in a launcher I've seen so far, and least cpu intensive(for me that's a big thing so the cpu scales less)
Colorize widgets - Great widgets to replace the lpp ones for those converting to other launchers.
AppMonster(pro or free) - Great backup utility, automatically backs up all apps.(I like it better than TB)
GPS Status - Great application for finding satalites near you and helping get a quick lock.
Any go dev team app - Great dev team, all their apps are worth looking at.
Frequently asked questions
Question: My phone is boot looping/not booting on the released suv, what do I do?
Answer: Your phone cannot handle the super undervolted values, you will need to flash the stable undervolted kernel
Question: My phone is running slow on the batterysave or scary governors, what do I do?
Answer: Set your minimum speed higher, those governors spend a lot of time at the lowest values
Question: How do I flash this?
Answer: You probably shouldn't be flashing one of my kernels if you don't know how(Mine are unstable =P)
Question: I'm not getting the amazing battery life/benchmark scores that others are getting
Answer: Well, every device is different, so you may not be able to score as high as some others, but you should get close at least, and the battery completely depends on usage patterns
Question: My phone can't clock to 1.8ghz, or some of the other higher values but does fine on the lower ones
Answer: Every device is different and not all can handle the same speeds/voltages, you are probably better off staying away from the higher speeds, I enabled the speeds but hope that you all are mature enough to handle them
Locating cpu% eating applications.
When in ADB shell type the following
top |grep app
Then look for items with high amounts of cpu% while the phone is idle.
Changelog
v1.8 - Initial kernel release for sense
Safe voltage kernels
v1.8
Scarykernel 1.8 stable - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Notes:
No I can't take the overclock any higher, I think everyone who's had a chance to take a crack at this source has tried, and going any higher seizes up after a few seconds.
Here is the source code for this build. I'll try to maintain it, I have a lot of kernel sources, but this will always be the latest release code, unless I state otherwise.
https://github.com/Scaryghoul
Credits: bcnice20 - For 99.8% of his kernel source.
Dogejcr/Preludedrew - For helping me get my laptop setup for kernel compiling.
Testers - For flashing this even though it says unstable :-X
JoesephMother - For helping me unlock the new lower clock values && other kernel related matters =)
x99percent - I used his middle clock speeds between the 3xx->7xx values as a base(edited voltages) as well as used his smartass source.
I see nobody else has chimed in on this kernel yet.. I will install Mikshift tomorrow and report my findings.
Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk
Yeah both versions don't work on mine.
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk
ozzie1p said:
Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you flash over bcnice20's kernel?
PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Thanks for clarifying that, I took down the links until we can get this working on several devices.
ozzie1p said:
Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you try both of them over bcnice20's 1.5ghz? Not everyone can handle the suv one.
edit: Links back up! I need some testers to try the fix at the top.
Ya, I flashed right over the top of bc's. Ill try these new ones.
Sent from my PG06100 using Tapatalk
Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..
PaulB007 said:
Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..
Click to expand...
Click to collapse
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<
Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk
Scaryghoul said:
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<
Click to expand...
Click to collapse
Whats the suspected culprit?
ozzie1p said:
Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
PaulB007 said:
Whats the suspected culprit?
Click to expand...
Click to collapse
I don't know so much for the freezes, but I believe that the booting has to do with me using my old voltages, and sense handling things differently than aosp >.<
I'll redo the voltage table later.
Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.
notsointeresting said:
Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.
Click to expand...
Click to collapse
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
Ah ok that sucks was really hoping for it but I understand thanks for the fast reply
Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
The ndk from google's web site has the toolchains needed to build gb kernel in it. The dl isn't terribly huge.
Sent from my PG06100 using XDA Premium App
For the people that want overclocking, here is your chance. I took my standard voodoo kernel, and put in the stuff needed to overclock it. Thanks to nemesis2all and his OTB kernel from the Fascinate for the code needed to get this to work. Also, use extreme caution when using the higher clock speeds. The stock "max" voltage for the CPU is 1300mv, and 1500MHz and 1600MHz are both at 1500mv, so it's heavily over-volted at the top end. By default, the system will boot to 1000MHz and you need to set the speeds you want in Voltage Control App. I don't personally use this because I think overclocking is useless, so any bug reports need as much information as possible, or they will be dismissed and not looked into at all. If you run into an issue with the system locking up, odds are that you have undervolted to much for a given clock speed. Other than that, you're on your own. Same FAQ applies as the regular PBJ kernel, so look there until I get a chance to post it here as well.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0808
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB Storage in recovery
0730
Updated CWM binary
Custom boot animation support
0709
Voodoo Sound V10
0615
Overclocking - Use Voltage Control App to adjust clocks and voltages
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Smooth out boot animation
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.
FAQ Placeholder
2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts
Undervolted and running ok so far.
Sent from my SCH-I510 using XDA App
Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
ZeppelinJ0 said:
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.
will2live said:
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.
Click to expand...
Click to collapse
Well it's definitely enabled. I just must have set the CPU settings poorly because this thing is crawling right now, I can't even scroll through the app drawer!
I've been trying to CWM back to the other PBJ kernels however my phone hangs on reboot, I'm guessing because those need to be flashed with Odin.
asenduk said:
2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts
Click to expand...
Click to collapse
I wish I knew what I was doing wrong.. running at 1.4 and my quadrant scores are exactly the same.... not that it really matters but still...
imnuts said:
. I don't personally use this because I think overclocking is useless.
Click to expand...
Click to collapse
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.
das7771 said:
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.
Click to expand...
Click to collapse
Use a program like CPUSpy that shows you the clock speed stats of your phone. >75% of the time, it will likely be in 400MHz or less, this probably approaches >90% if you say 800MHz or less, especially if you are not a heavy user. At that point, why overclock your phone? To get the overclocking stable, you need increase voltages across the board, and despite undervolting, you'll never get the same power usage as you can with a non-overclocked kernel as some of the voltage changes you can't revert. My opinion is that while overclocking can smooth some stuff out, for most day-to-day usage, it has no practical benefits and only causes more battery drain than you would otherwise have. Given how precious battery life is these days, why knowing make your battery drain faster?
it's funny you say that becuase i noticed with ludeboy's kernel that when overclocking system panel very rarely showed my phone running over the stock speed. Usually it was as you stated some where around 800mhz..I understand what your saying...Thanks for the quick response.
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Backup SD and app data b/c crashing/freezing can corrupt files.
Edit: Also keep Voltage Scheduler Remover on your phone just in case.
1600
1500
1400
1300 -0
1000 -25
800 -50
400 -75
200 -100
100 -150
"interactive" was unstable a couple kernels ago so I haven't tried it.
suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
Potentially, yes, but you may lose stability.
Awesomeness
I love it. I can deal with a slightly shortened battery life. I wanted to OC because a lot of the more intense games don't run as smooth as I would like. With OC, its all butter. Thanks!! I have mine set at 1400, and it really didn't improve my quadrant scores, but there's a noticeable decrease in lag going from one app to another.
suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
You would see better battery life at stock clock speeds if you just used the standard (ie. not overclocked) kernel I built.
Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
I'm on board with not thinking it's necessary - though I can see how the tinkerers and speed demons would love it. (And all the more power to them, literally)
I don't know imnuts, I always noticed when I forced the phone into a higher overclock it always seemed quite a bit snapier.
Keep it on conservative. Interactive is buggy.
ZeppelinJ0 said:
Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse
underscored said:
Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
Click to expand...
Click to collapse
This will remain separate from the standard kernel most likely. I will see if I can build off of this source without overclocking and have it work, though I don't know if it will. I want to keep them separate for stability and battery life reasons.
WildKernel
As some of you may know, I've been working on a custom kernel for ICS/JB and its about done (for a first release).
Also I was previously planning on a beta testing for a selected few, but I released I won't have enough time to be hosting testing sessions, so how about this. The kernel is know free to use for the public, but all I ask is that your report and compare. I'd like to see if there's improvement or loss between the A6 kernel and this (battery, performance, etc.). Also please report anything good and bad so that I know what to keep and what not to keep for a final release. This also helps me push out fixes faster when presented with lots of information.
Current kernel features include: (If feature begins with a * then check below for more information)
Universal kernel compatible with all AOSP (NOT SENSE) ICS & JB roms
rebased to CAF (custom) Linux 3.0.39 kernel
Optimized Built in Low-memory killer w/ Fugeswap (as seen in the v6 Supercharger)
Optimized ram usage/handling (Swap & Zram)
Increased Wi-fi connectivity range
*Low & High power Wi-fi scaling steps
*Badass Governor
Lazy Governor
Imported Snapdragon optimizations used by the Sensation (Thanks Romanbb)
Lagfree Governor
Fast charging for unknowns and when plugged in to computers
HIGHLY Tweaked for the perfect battery life and performance
Bluetooth code from CAF
V(R), simple, deadline, noop, and CFQ I/O schedulers
*Ondemand & Intelli(gent)demand Governor
Stable Undervolting of the CPU
increased SDcard readahead speed
Tweaked Flashlight
Added more clock steps to the GPU for compatibility with low power browsing and GPU OC @ 320 mhz
Please wipe cache and dalvik cache
I dont suggest using SetCPU as it may cause bugs such as reboots, use CM or AOKP's built in cpu speed feature
Download Universal flasher for ICS and JBhttp://www.mediafire.com/download.php?q9bhv68k8dvai13
(Flashable for S-ON coming tomorrow when I have time)
You may find my source hosted @ Github
More information:
Badass Governor: This governor has built in profiling (like used in SetCPU but not as battery & Ram consuming). This is also the default and highly recommended governor. This governor features a 3 phase system CPU profiling system. This will change your CPU speed based on usage. This saves a lot of power as your speed doesn't just keep at one clock no matter how much your using you phone. A similiar profiling system is also used for the GPU and such.
Ondemand and Intellidemand Governor: Intellidemand is based off the Ondemand governor but features a 2 phase CPU profiling system with some added tweaks. Ondemand also now has early suspend support for low power browsing to save battery.
Wi-fi Low and High power scaling steps: This is a feature that will determine whether to use High or low power voltages on the Wi-fi chip to save battery. eg: Wi-fi will be turned to low power when idle or screen off. Wifi will be turned to high power when actively in use or in progress of a download. Take note that high power wi-fi voltage isn't necessarily "High" power but more of just "Stock HTC" power.
View all public kernel releases
Changelog:
Code:
[B]Sep 3 - ver003[/B]
1. Bluetooth updates upstream
2. Downgrade to linux Kernel v3.0.39 with custom libs to *really* fix lag
3. Badass back to default governor as the most stable
4. More LMK tweaks
[B]Sep 2 - ver002[/B]
1. Implemented USB forced fast charge v3.1
2. Downgrade to linux Kernel v3.0.40 to fix lag
3. Ondemand tweaks, early suspend updates, and is now default governor because of balance of stababilty, battery, and speed.
4. LMK tweaks
5. Updates to bluetooth from CAF (more battery saving and stable)
6. Updates to scheds from faux
7. mpdec ready but disabled until stabalized
8. A lot of improvements since ver001
Thanks:
TeamDS
Strapped365
faux123
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
reserved for James (He'll be supplying statistics such as battery reports, cpu logs, benchmarks etc.)
Post statistics and they will be copied here
Nice
Hastily spouted for your befuddlement
Awesome. Hope this fixes the battery drain problem from the A6 kernel.
Sweet. Will test tonight.
Il test this but not until Saturday morning will I have solid feedback
I'm going to have to use both Ankers plus my stock battery for tomorrow as I have school, then a football game, then a roadtrip so I will definitely take shots and post back with great contrasts I'm sure
Thanks XMC
::Respect::
---------- Post added at 10:02 PM ---------- Previous post was at 09:31 PM ----------
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Sorry wild, can't get it booting. Been trying forever. I'll redownload again when I get home.
P.s: it boots, but it goes right into a reboot after I hit homescreen. I don't think I can use alogcat to pull one, so I'll have to wait till I get back to my computer. Perhaps a dmesg a well.
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Riyal said:
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Click to expand...
Click to collapse
Hey maybe even if xmc your planning on doing a sense one... Maybe if no offense allow Riyal access to those things as you might learn from his enhancements to a sense kernal and such... Also additional development for DS
:what:
::Respect::
well im on my computer. the error (though im no expert) seems to be here
if you need the full logcat let me know and i'll try grab it again. that's the error going on right when the homescreen gets laggy on boot, right before it reboots.
i don't know if this is important to you, but this is what i get in logcat right before reboot
I'm sure i followed directions. I hope I'm not doing something wrong.
Edit: yep. Definitely not an expert. So it stopped rebooting after I unchecked "set on boot" under performance. Will be reporting back.
CoNsPiRiSiZe said:
Il test this but not until Saturday morning will I have solid feedback
I'm going to have to use both Ankers plus my stock battery for tomorrow as I have school, then a football game, then a roadtrip so I will definitely take shots and post back with great contrasts I'm sure
Thanks XMC
::Respect::
---------- Post added at 10:02 PM ---------- Previous post was at 09:31 PM ----------
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Click to expand...
Click to collapse
I flashable for S-ONs will come soon sorry
Riyal said:
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Click to expand...
Click to collapse
to be honest I hate sense and I doubt I'll be developing anytthing for it anytime soon.
Riyal, i'm open source so feel free to do whatever you wish. If you need help with me pointing out specific commits lemme know
ekoee said:
well im on my computer. the error (though im no expert) seems to be here
if you need the full logcat let me know and i'll try grab it again. that's the error going on right when the homescreen gets laggy on boot, right before it reboots.
i don't know if this is important to you, but this is what i get in logcat right before reboot
I'm sure i followed directions. I hope I'm not doing something wrong.
Edit: yep. Definitely not an expert. So it stopped rebooting after I unchecked "set on boot" under performance. Will be reporting back.
Click to expand...
Click to collapse
are you using setcpu?
No, I'm running cm 9.1.0. Under settings > performance > cpu settings or whatever it is, if you have set on boot checked, the phone runs funny. I unchecked it in a desperate attempt to figure out what's going on, and it's been pretty stable ever since.
xmc wildchild22 said:
reserved for James
Click to expand...
Click to collapse
LMAO! :laugh: You GO James!!! :good:
CoNsPiRiSiZe said:
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Click to expand...
Click to collapse
Can't we just extract the zImage from the universal kernel flasher, rename it boot.img, and flash? I thought they were analogous...
Edit: I tried it. Didn't work. "Boot Magic check failed". Guess I was thinking of Samsung devices. Bummer, I really wanted to try this.
Ok after a 10 minute self lesson on kernel kitchen I managed to compile a boot.img. Booted right up but I had nofrills with an "apply on boot" setting which screwed me over. Severe lag. I managed to access that app in slow motion and deselect the apply on boot nonsense. Now we are in business
Don't forget to uncheck all governor apply on boot settings before flashing! Also, on first boot go to a view CPU frequency place on your phone so you can wait until the phone settles before rebooting/doing stuff. Takes a little longer than you would expect.
So far the performance seems good, I'll report back on battery life later.
Edit: 3 consecutive reboots during 3 consecutive calls. Switching back to 3.0.30 (A5) for now. Since I didn't flash this officially I'd take this experience with a grain of salt but it is similar to what ekoee is reporting so IDK.
Hi xmc! Not that I question the knowledge of the senior htc community developers here but this battery issue I am facing with ROMs like virtuous is already nagging me out.
Now compiled yours and shocked that it also has the battery bug.(The not going to 100% bug)
So I decided to really look up the battery driver carefully awhile ago and noticed something strange in it. I noticed this days ago and thought this was ok but thought I would stand up and ask today.
In
arch/arm/mach-msm/htc_battery_8x60.c
htc_batt_get_battery_info
Could you tell me why calculation of battery is like this?
htc_batt_update->batt_current = htc_batt_info.rep.batt_current - htc_batt_info.rep.batt_discharg_current;
Click to expand...
Click to collapse
instead of this?
htc_batt_update->batt_current = htc_batt_info.rep.batt_current;
Click to expand...
Click to collapse
Seems like the batt_discharg_current is making my battery report less than the real value so I'd like to know why is the calculation like that?
I'm sorry for asking but I think you're the only developer on doubleshot who is approachable enough for me to ask to.
Riyal said:
Hi xmc! Not that I question the knowledge of the senior htc community developers here but this battery issue I am facing with ROMs like virtuous is already nagging me out.
Now compiled yours and shocked that it also has the battery bug.(The not going to 100% bug)
So I decided to really look up the battery driver carefully awhile ago and noticed something strange in it. I noticed this days ago and thought this was ok but thought I would stand up and ask today.
In
arch/arm/mach-msm/htc_battery_8x60.c
htc_batt_get_battery_info
Could you tell me why calculation of battery is like this?
instead of this?
Seems like the batt_discharg_current is making my battery report less than the real value so I'd like to know why is the calculation like that?
I'm sorry for asking but I think you're the only developer on doubleshot who is approachable enough for me to ask to.
Click to expand...
Click to collapse
I'll take a look once I get home. Lol and just to be clear, i'm not the only dev for the DS. We got Blue6IX, jeffakajeff, strapped365, tbalden, Riyal , kornyone, and nbetcher. (Dont kick my a$$ if I skipped your name )
Flashed this with a fresh install of your JB ROM. Phone is really laggy when waking from screen off for a few seconds but then its ok. I'll look more in to this but thats what I'm seeing so far.
Flashing over CM 9.1 now, will test it out and report back with results. Really hope this takes care of the battery drain issue in 9.1.
xmc wildchild22 said:
I'll take a look once I get home. Lol and just to be clear, i'm not the only dev for the DS. We got Blue6IX, jeffakajeff, strapped365, tbalden, Riyal , kornyone, and nbetcher. (Dont kick my a$$ if I skipped your name )
Click to expand...
Click to collapse
Lol! If I were a dev here I wouldn't have asked you this woot now I'm an ass kicker :highfive: