Database Info

[KERNEL] Undervolt driver for the stock HTC kernel for EVO 4G and others (2.6.32.15)

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

[KERNEL] [GPL] MixUp - Overclock/Undervolt (11/10/2010 - Taco Madness!)

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..

The Autogroup Thread for Sense kernels

As there has been much discussion about this I thought I'd start a thread and try and get this worked out properly.
http://www.phoronix.com/scan.php?page=article&item=linux_2637_video&num=1
This 200 line patch is a subject of debate on here, some people claiming it will make a difference, some claiming it won't. Personally I don't think it will. So lets put this to bed.
A backport of this patch is available here -:
http://mirror.couttstech.com/android/bravo/kernel/taskgroup-2.6.38-backport-2.6.32.patch
Any kernel devs willing to try this are most welcome
I have built a kernel with this patch applied, that is available here -:
http://mirror.couttstech.com/[email protected]_CMBattFix_AUTOGROUP_CFQ.zip
Now, this kernel works fine for me, however, some people have reported blank screen problems. I have recompiled and re-uploaded, so if anyone could test that would be great.
Currently I am getting between 1500 and just under 1600 in quadrant with this kernel. I get slightly higher with a BFS/BFQ version on the same kernel. It does feel smooth, but so does the BFS version.
So if anyone can help test this, it would be appreciated.
*****NOTE***** I do not accept any responsibility for any damage this kernel may cause to your device.

I guess one can't see any big difference, because this patch is about Linux Desktop Machines. Their hardware and system architecture is just too different to really compare it. It might have a real effect on a desktop.

I tried your kernel. When the screen is off. I turn it on and it hang .The top of the screen have a white line and i can't do anything. back to the other kernel is ok.

Why do you think your bench score should increase?! As i understood it the patch only increases the responsivness under heavy load. So to test it, one should get the cpu to 100% load and then see if other apps/screen transition/etc are more responsive.
Well even if this patch helps then I wonder if this is still needed. I don't compile stuff or encode videos in background on my phone ;-) . Can't really think off many situations when I would have a heavy cpu load in background. Or do you compile stuff on your phone with 64 jobs while watching some vids (like in the vid of the article)?

What cpu gobernor are you using? With smartass i get a black screen, may be with other there isnt problem.
Br.
Sent from my HTC Desire

yukkio said:
What cpu gobernor are you using? With smartass i get a black screen, may be with other there isnt problem.
Br.
Sent from my HTC Desire
Click to expand...
Click to collapse
Interactive
I've been running autogroup kernel all day no with no problems.
Just changed back to BFS

melethron said:
Why do you think your bench score should increase?! As i understood it the patch only increases the responsivness under heavy load. So to test it, one should get the cpu to 100% load and then see if other apps/screen transition/etc are more responsive.
Well even if this patch helps then I wonder if this is still needed. I don't compile stuff or encode videos in background on my phone ;-) . Can't really think off many situations when I would have a heavy cpu load in background. Or do you compile stuff on your phone with 64 jobs while watching some vids (like in the vid of the article)?
Click to expand...
Click to collapse
I don't think bench should increase, and agree with everything you have said, this patch should make no difference. But some are adament that it does, hence this thread

The problem is (if I understood the patch right) that the automated taskgroup thing is based on tty. Android don't use a tty so first we need something like that Implement automated per session task groups. That should behave better (need to test it but I think it will). Maybe this is the problem and it solves the blank screen problem.

Benee said:
The problem is (if I understood the patch right) that the automated taskgroup thing is based on tty. Android don't use a tty so first we need something like that Implement automated per session task groups. That should behave better (need to test it but I think it will). Maybe this is the problem and it solves the blank screen problem.
Click to expand...
Click to collapse
Ah, excellent, I'll have a good look at that. Thanks!
Not sure about the black screen problem as I don't experience it.
Sent from my HTC Desire using XDA App

coutts99 said:
Interactive
I've been running autogroup kernel all day no with no problems.
Just changed back to BFS
Click to expand...
Click to collapse
May be the problem is the cpu governor. I will probe with interactive.
Br.
Edit: same thing, black windows.
Is it your desire slcd or amoled? Mine amoled.
Sent from my HTC Desire

yukkio said:
May be the problem is the cpu governor. I will probe with interactive.
Br.
Edit: same thing, black windows.
Is it your desire slcd or amoled? Mine amoled.
Sent from my HTC Desire
Click to expand...
Click to collapse
I'm also getting the black screen issue, a white strip at the top, and a bunch of green pixels at the bottom, but the phone is still funtioning, because when i press the volume buttons the phone responds with an audio tone and when i keep on pressing the volume down button the phone vibrates signaling vibrate only...

[Q] No audio from video recordings...maybe ROM related? [SOLVED]

Update-Solutions added
This thread kinda rambles, and covers a couple different issues.
I'll try to summarize the solutions to each to time and eliminate extra reading for those who might end up here later.
Issue #1: My Mesmerize was not recording sound with videos
Solution: Go into Voodoo Sound Control app (download from market if you don't have it) and under [recording profile], select "Original". Solved!
Issue #2: I was having various minor issues that sounded as thought they might be fixed by flashing a new kernel.
scarmon25 suggested that I try out OTB-Reloaded. He was right, this is a great kernel! It allows overclocking and undervolting at the same time. I'm hoping this will give me both better performance and greater battery life.
Solution: Backup everything (Nandroid and TiBackup suggested), Flash the new kernel from recovery (you can use ROM manager to boot into Clockwork Mod Recovery) and reboot.
I'm not about to get into a discussion of backups, recovery, flashing, which kernel you need, etc... This is just a plug/endorsement for the OTB-reloaded kernel, period.
Issue #3: At some point while updating to 2.2 Froyo and flashing new kernels, ROMs, etc... my home screen started rotating along with my apps. I could turn rotation on/off from the notification tray, but that disabled it for apps also.
Solution: It was pointed out by add144 that it's the home screen launcher that controls home screen rotation.
I'm running LauncherPro, be he mentioned that most other launchers (ADW, GO Launcher, etc...) also have the ability to allow or lock home screen rotation.
In my case (LauncherPro), here's the process for locking your homescreen rotation while still allowing auto-rotation in other apps:
1) From home screen, go to Menu (button) -> Preferences
2) Select Behavior Settings
3) Uncheck "Enable Auto-rotation"
4) Done!
I hope this summary saves someone some time and fruitless searching.
Cheers!
-Mike
----Original message follows---
Hi all,
I apologize for this question being a bit light on useful details, but my memory isn't so great.
I have a Mez, running 2.2 Froyo (updated from USCC), a custom ROM (I think), and a custom kernel (not sure which one).
I know that sounds insane, but there was a time a while back when I was flashing different things trying to find something that worked to my liking, and honestly just can't remember what combination I settled on.
It doesn't help that I'm still fuzzy on the whole ROM vs Kernel thing.
Anyway, here's the issue...
The videos I record on the phone have no sound.
You can hear a little background hiss, but no actual sound from the mic.
I can't remember if it worked before I updated to 2.2, but I suspect it did or I think I'd have noticed it before.
I guess I could flash everything back to stock and see if that fixes it, but I'd REALLY rather not do that, since it would take me so long to get it back sorted.
Is there a way to figure out exactly what I currently have installed on the phone?
Also, can anyone think of things I can do to troubleshoot the no audio issue?
Thanks in advance,
-Mike

This sounds like a issue I had on one of the earlier voodoo kernels. The fix was to download the voodoo control appear from the market and set recording preset to normal. This was fixed in the later releases of voodoo. Do you know which kernel your are on. That would help us narrow it down for you.
Edit. If you download the cpu spy app from the market you can pull your info up and see which kernel your on. It won't say exactly which one but should have the authors name in it so we can know which one your on to an extent.
Sent from my SCH-I500 using XDA Premium App

Thanks for the quick reply scarmon.
I checked my voodoo sound options (already had the app) and I don't have a 'normal' recording preset.
My choices are:
Original
Balanced (new default) - with DRC
High Sensitivity - with DRC
Loud Environment - with DRC
I assume this means I have one of the newer versions of voodoo sound?
I'll get that cpu spy app and see what it says about my kernel.
Thanks!
-Mike

Elmojo said:
Thanks for the quick reply scarmon.
I checked my voodoo sound options (already had the app) and I don't have a 'normal' recording preset.
My choices are:
Original
Balanced (new default) - with DRC
High Sensitivity - with DRC
Loud Environment - with DRC
I assume this means I have one of the newer versions of voodoo sound?
I'll get that cpu spy app and see what it says about my kernel.
Thanks!
-Mike
Click to expand...
Click to collapse
Use original

Switched to Original, audio works now, thanks!
I wonder why the "new" profiles don't work?
Is it a limitation of this phone or a problem with voodoo?

The newer voodoo kernels have that issue fixed. I believe it was just a issue with the first few ec10 voodoo kernels. May wanna try one of the new OTB or imnuts kernels. The recording works on those as I have tried both.
Sent from my SCH-I500 using XDA Premium App

scarmon25 said:
The newer voodoo kernels have that issue fixed. I believe it was just a issue with the first few ec10 voodoo kernels. May wanna try one of the new OTB or imnuts kernels. The recording works on those as I have tried both.
Click to expand...
Click to collapse
Good to know, thanks.
Is updating to one of those kernels you mentioned a simple 'boot to recovery and flash zip from SD card' or something more?
Here's a screenshot of my current kernel info from cpu spy...
Does that help any? I don't recognize that author.
EDIT: That OTB kernel sounds really interesting.
Please refer to my above question about the simplicity or complexity of flashing that kernel over the one I have now.

Yeah u flash in CWM. If your on voodoo and 2.2 then you shouldn't have any issues. If u go with OTB make sure to get the voltage control app. So u can adjust it. Just go easy on the over clock and undervolting till u see how your phone reacts. If u go with OTB let me know and I will post my settings. Been running them for a while and they seem pretty stable.
Edit. Switched to PC to correct my spelling.
Sent from my SCH-I500 using XDA Premium App

The above is what I'd try first. If you still find that you're having issues even with a new kernel, I'd consider flashing a new ROM as well.

scarmon25 said:
If u go with OTB let me know and I will post my settings. Been running them for a while and they seem pretty stable.
Click to expand...
Click to collapse
I'll be flashing OTB shortly and would love to get your settings.
Thanks!
-Mike

K, This is what I have been running and it seems pretty stable for me. Keep in mind each phone is different and yours may not respond as well, or it may do even better then mine. I would suggest using the apply for now option in voltage control for a few days and once you know there good, you can apply at boot. Also nemisses included and great feature in CWM that allows you to remove boot settings in the event that you set something at boot and it doesn't work. You will get this once you flash the OTB v1.3 kernel. This will update CWM and the feature is under the advanced section of CWM if you need it. Here's the settings I have been using.
For the Scheduler I use BFQ
I set the Max Clock to 1200mhz
I have the following step and voltage drops enabled
200 mhz -100
400 mhz -100
600 mhz -75
800 mhz -75
1000 mhz -75
1200 mhz -50
With theses settings I am getting about a day of moderate use from my battery and great performance. You may play around with it and may get better results. Hope this helps.

OTB 1.3?
The thread I was watching only goes to v1.2 for OTB-reloaded.
What am I missing?
I also noticed that is was technically a Fascinate kernel, is that a problem?

It works on the mesmerize too. That's what I'm on. There should be a link in the OP that's has v 1.3. Its he second link at the bottom of the OP
Sent from my SCH-I500 using XDA Premium App

Okay, I think I see the issue.
I was looking at this thread, whereas I think you're referring to this thread, right?
What's the difference between those 2 kernels, other than the OTB version?

one is Touch wiz and one is AOSP. If you are on stock Froyo you need touchwiz. AOSP will not work on stock ROM. You posted in the right one for OTB. This is the one you need for Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1011626
The 1.3 link is towards the bottom of the first post.

scarmon25 said:
one is Touch wiz and one is AOSP. If you are on stock Froyo you need touchwiz. AOSP will not work on stock ROM. You posted in the right one for OTB. This is the one you need for Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1011626
The 1.3 link is towards the bottom of the first post.
Click to expand...
Click to collapse
I don't think I'm on stock froyo, though.
As far as I can tell, I'm running SuperFrankenClean 0.292.
I base this on the files I found on my SD card while I was moving some stuff around just now.
In any case, it sounds like the touchwiz kernel is the one I need.
I'm downloading it now and will flash in a few.
Let me know if it looks like I'm about to frag something and I'll wait.
-Mike
OOPS! That should be SuperFrankenClean 2.9.2 ROM and EC10_ulv_voodoo kernel....I think.
Does that change anything?

Wait. Let me pull that ROM and I can tell you.
K this is showing to be used with touchwiz based kernels so u should be good to go.
Sent from my SCH-I500 using XDA Premium App

Yeah your good man flash away. As long as its a touch wizard kernel you good to go. If u used the one I linked u too then u will be fine.
Sent from my SCH-I500 using XDA Premium App

Awesome, flashing now....
If you hear a scream, it means it didn't work. lol
-Mike

Well I'm here all night so if it does go wrong we will fix it. But honestly you shouldn't have any issues
Sent from my SCH-I500 using XDA Premium App

Franco Kernel vs Stock?

I am debating on whether to buy the pro version and flash Franco's Kernel for my Nexus 5 and 7 (2013). I just want to know what I bits of extra I can really do with it.. And if its worth it. I'm more worried about stability than anything I guess. I don't want to run into little issues whether it be audio, video, whatever it may be. Also I have never flashed a kernel or another ROM, I've always stuck with stock. I am running 4.4.2 right now utilizing Gravity Box and Wanam Kit, and a few other modules. Any input would be greatly appreciated. If this thread has been done before, my apologies. I am a brand new forum user, never really get on the computer.
Sent from my Nexus 5 using Tapatalk

wardawgmalvicious said:
I am debating on whether to buy the pro version and flash Franco's Kernel for my Nexus 5 and 7 (2013). I just want to know what I bits of extra I can really do with it.. And if its worth it. I'm more worried about stability than anything I guess. I don't want to run into little issues whether it be audio, video, whatever it may be. Also I have never flashed a kernel or another ROM, I've always stuck with stock. I am running 4.4.2 right now utilizing Gravity Box and Wanam Kit, and a few other modules. Any input would be greatly appreciated. If this thread has been done before, my apologies. I am a brand new forum user, never really get on the computer.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well to be honest the stock kernel allready is very good, the only downsides of it are batterylife/screenontime and colors are not very vibrant. These 2 aspects are substantialy better with Franco kernel. Screenontime and batterylife is improved by at least 50% or more for some (check out the Franco thread). Also you can raise the speaker/mic/in-call volume as you wish and load a color profile for better and more vibrant colors.

if you want stability stick with stock

gee2012 said:
Well to be honest the stock kernel allready is very good, the only downsides of it are batterylife/screenontime and colors are not very vibrant. These 2 issues are substantialy better with Franco kernel. Screenontime and batterylife is improved by at least 50% or more for some (check out the Franco thread). Also you can raise the speaker/mic/in-call volume as you wish and load a color profile for better and more vibrant colors.
Click to expand...
Click to collapse
I have been getting fantastic battery life with my setup now, I just leave brightness at auto, and from my bit of research, that seems to be the big culprit of battery life. I'm always looking to improve my phone in terms of performance and cosmetic, keeps me busy at negative 60 out here in North Dakota lol.
But 50% overall more battery life?! That's pretty friggin good. Would definitely pay for it for that kind of power.
I'm also assuming based on your post that the color control is not for LED control but the screen itself. Any idea if the Xposed LED module works well? I know its off topic just a quick question.
Not sure about the volumes, I usually don't mess with call volumes, but I'll look into it more.
Thanks for your post! Also please post the link to the Franco Thread.
Sent from my Nexus 5 using Tapatalk

wardawgmalvicious said:
I have been getting fantastic battery life with my setup now, I just leave brightness at auto, and from my bit of research, that seems to be the big culprit of battery life. I'm always looking to improve my phone in terms of performance and cosmetic, keeps me busy at negative 60 out here in North Dakota lol.
But 50% overall more battery life?! That's pretty friggin good. Would definitely pay for it for that kind of power.
I'm also assuming based on your post that the color control is not for LED control but the screen itself. Any idea if the Xposed LED module works well? I know its off topic just a quick question.
Not sure about the volumes, I usually don't mess with call volumes, but I'll look into it more.
Thanks for your post! Also please post the link to the Franco Thread.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
If you are having trouble making a decision... just flash the kernel with fastboot and give it a test run. Can the free version of FKU auto flash? I'm not sure, you would have to investigate.
If you decide you like it (and the updates that go along with it), then maybe consider buying the app.
But yes, screen on time is better with FK due to the way the clock speeds scale. A lot better. Even with the stock settings, though I find even those to be a bit aggressive.

wardawgmalvicious said:
I have been getting fantastic battery life with my setup now, I just leave brightness at auto, and from my bit of research, that seems to be the big culprit of battery life. I'm always looking to improve my phone in terms of performance and cosmetic, keeps me busy at negative 60 out here in North Dakota lol.
But 50% overall more battery life?! That's pretty friggin good. Would definitely pay for it for that kind of power.
I'm also assuming based on your post that the color control is not for LED control but the screen itself. Any idea if the Xposed LED module works well? I know its off topic just a quick question.
Not sure about the volumes, I usually don't mess with call volumes, but I'll look into it more.
Thanks for your post! Also please post the link to the Franco Thread.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Most users report a screenontime of about 5-7 hours while stock is about 3,5 hours. Don`t know about the Xposed module but color controll in the Franco kernel updater app is realy good and there are various preloaded settings available. Link thread http://forum.xda-developers.com/showthread.php?t=2508284. Backup your current kernel in the FKU before you flash a Franco kernel, so you can restore it if need be.

Aerowinder said:
If you are having trouble making a decision... just flash the kernel with fastboot and give it a test run. Can the free version of FKU auto flash? I'm not sure, you would have to investigate.
If you decide you like it (and the updates that go along with it), then maybe consider buying the app.
But yes, screen on time is better with FK due to the way the clock speeds scale. A lot better. Even with the stock settings, though I find even those to be a bit aggressive.
Click to expand...
Click to collapse
I believe you can, I'll look into when I get home.
So do you underclock or undervolt? I don't know the differences between the two, my apologies. If I do get Franco I think I will just leave it at the stock settings it comes with before I make any changes, still got learning to do. Thank you for sharing your knowledge!
Sent from my Nexus 5 using Tapatalk

gee2012 said:
Most users report a screenontime of about 5-7 hours while stock is about 3,5 hours. Don`t know about the Xposed module but color controll in the Franco kernel updater app is realy good and there are various preloaded settings available. Link thread http://forum.xda-developers.com/showthread.php?t=2508284. Backup your current kernel in the FKU before you flash a Franco kernel, so you can restore it if need be.
Click to expand...
Click to collapse
That's pretty awesome, definitely gonna try it out. I have a backup somewhere on my device, I think in Flashify, but I'll make another, can never hurt lol.
And thanks for the thread and all the other info!
Sent from my Nexus 5 using Tapatalk

Stick with stock for at least long enough to give yourself a baseline to judge other ROMs/kernels against.

Wakamatsu said:
Stick with stock for at least long enough to give yourself a baseline to judge other ROMs/kernels against.
Click to expand...
Click to collapse
I've had my Nexus 5 for roughly 2 months now I think, are you saying I should wait it out or do more research first? It is very scary for me lol. I'm always afraid to be making major internal changes without some form of consultation and research.
Sent from my Nexus 5 using Tapatalk

Also quick question, I don't need to back anything else up correct? Flashing a kernel does not mess with anything else does it?
Sent from my Nexus 5 using Tapatalk

wardawgmalvicious said:
I've had my Nexus 5 for roughly 2 months now I think, are you saying I should wait it out or do more research first? It is very scary for me lol. I'm always afraid to be making major internal changes without some form of consultation and research.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I wouldn`t mess with the kernel settings like UV/OC besides color and sound optimisations. The stock settings are allready good enough for most users, only xperienced users should do that imo.
---------- Post added at 06:21 AM ---------- Previous post was at 06:18 AM ----------
wardawgmalvicious said:
Also quick question, I don't need to back anything else up correct? Flashing a kernel does not mess with anything else does it?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No, flashing kernels or recovery`s don`t wipe data.

gee2012 said:
I wouldn`t mess with the kernel settings like UV/OC besides color and sound optimisations. The stock settings are allready good enough for most users, only xperienced users should do that imo.
Click to expand...
Click to collapse
That's what I'll do then, what kind of sound optimizations are there? Just the mic volume and whatnot? Or are there some for playing music, I have poweramp and use that equalizer, so just wondering.
Sent from my Nexus 5 using Tapatalk

wardawgmalvicious said:
That's what I'll do then, what kind of sound optimizations are there? Just the mic volume and whatnot? Or are there some for playing music, I have poweramp and use that equalizer, so just wondering.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can only raise the volume levels (no EQ settings), this should not interfere with PowerAmp.

gee2012 said:
You can only raise the volume levels (no EQ settings), this should not interfere with PowerAmp.
Click to expand...
Click to collapse
Alright guess I'll just have to carefully play around with a bit. Thanks for your help!
Sent from my Nexus 5 using Tapatalk

gee2012 said:
You can only raise the volume levels (no EQ settings), this should not interfere with PowerAmp.
Click to expand...
Click to collapse
Oh last question, do you know of any stability issues with Franco Kernel? That is my number one concern, so just checking with you real quick before I go with it finally.
Sent from my Nexus 5 using Tapatalk

wardawgmalvicious said:
Oh last question, do you know of any stability issues with Franco Kernel? That is my number one concern, so just checking with you real quick before I go with it finally.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I haven`t had FC`s when i used the kernel, most issues of users we`re caused by undervolting too much.

gee2012 said:
I haven`t had FC`s when i used the kernel, most issues of users we`re caused by undervolting too much.
Click to expand...
Click to collapse
Alright sounds good! I'll let you know how it goes!
Sent from my Nexus 5 using Tapatalk

wardawgmalvicious said:
Alright sounds good! I'll let you know how it goes!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oke, good luck and enjoy

gee2012 said:
Oke, good luck and enjoy
Click to expand...
Click to collapse
OK maybe a stupid question, should I use auto flash or flash via recovery?
Sent from my Nexus 5 using Tapatalk