[KERNEL][WIP] Underworld Sense Kernel v0.8 [Jul 16 2012][GINGERBREAD][SENSE]

Search This thread

pennie77

Senior Member
Mar 15, 2011
77
25
ca1ne said:
One of these days I'm going to have to look under the hood of Smurf and see what's happening in there, might save me some headaches.

Smurf try to load battery saving settings for smartassV2. Every time I tried to make any change in the script for smartassV2 it got really laggy. If you open the 45 smurf file in etc/init.d and remove the section with the govner tweaks the lag will go away after reboot.
 
  • Like
Reactions: ca1ne

Captain_Throwback

Recognized Developer
Touchscreen?

I don't know if anyone has noticed this, or if it's just me.

I seem to occasionally have issues with my touchscreen being unresponsive. My phone screen will be off, and I'll press the power button to unlock, but when I touch the screen to try and drag the ring to unlock, the screen acts as if I only tapped it, rather than the drag action. I noticed this behavior on MikG, and even on Classic using the classic kernel, which I thought was weird, since that one's mostly stock. On Classic, when I tried to drag the bar down on the lockscreen, it'll get to the bottom of the page, but it won't unlock the device. If I press the power button to screen off, and then turn it back on, usually the screen responds again.

Is it possible the kernel mods for multi-touch are somehow causing this issue? I'm running the stock kernel right now, and ever since I flashed it, I haven't had the issue. Has anyone else seen this. or is it just me? Maybe I need to try a different governor. I've mostly been using interactiveX or smartass v2, I also tried intellidemand, and it didn't seem to matter - I still had occasional unresponsiveness.

Any help you can offer is greatly appreciated. I want to confirm the stock kernel is good before flashing back to 0.4 and trying it again. Hopefully someone will have some input by then, so I know if I'm just going crazy :).

Thanks, ca1ne for the great kernels - SBC was the big thing missing from the Sense kernels, and you made it happen! :D
 
  • Like
Reactions: ca1ne

ca1ne

Retired Recognized Developer
Apr 16, 2011
802
1,385
East Coast
Quick question, are you running this on the phone or in a boot manager slot... I have unresponsiveness when using boot manager especially when sense its in the slot.. Aosp seems more responsive.
 

NaterTots

Senior Member
Feb 7, 2012
1,486
762
CT
OnePlus 5
OnePlus 7T
I have those exact same symptoms if I'm using a Sense Rom in a Boot Manager slot. The lock screen may take a second to unlock.
I also use InteractivX as my governor most times.

I just assumed it was lag due to being in a Boot Manager slot.

Naters
 

Captain_Throwback

Recognized Developer
Quick question, are you running this on the phone or in a boot manager slot... I have unresponsiveness when using boot manager especially when sense its in the slot.. Aosp seems more responsive.
I actually stopped using BootManager because I thought that might be it, but I still had the issue using only MikG on my device. But I'm beginning to think there's just an issue with my touchscreen.

ROM: MikG v3.11 w/ICS Lite Theme | Kernel: Underworld v0.4 SBC
 
Last edited:
  • Like
Reactions: ca1ne and NaterTots

buckhunter

Senior Member
Mar 1, 2011
1,379
585
mecampo said:
do you need a sleep profile for this setup?

and do we really need to do vipermod?

You dont have to use vipermod unless you want to try to lower the voltages to get more battery life. Some phones dont like much undervolt so ymmv. Just make sure you have a nand of your stable setup before playing. I never use any profiles even when using ondemand and my phone sleeps fine. Profiles are just something else running in the bg imo.
 

mecampo

Senior Member
Jan 19, 2011
179
19
Cypress, TX
You dont have to use vipermod unless you want to try to lower the voltages to get more battery life. Some phones dont like much undervolt so ymmv. Just make sure you have a nand of your stable setup before playing. I never use any profiles even when using ondemand and my phone sleeps fine. Profiles are just something else running in the bg imo.


Thanks buck, i'll leave it as is for the moment and maybe try vipermod later if i still want to stretch battery life. Is there a downside of undervolting like lags?

Sent from my PC36100 using XDA
 

stupidjerkheadface

Senior Member
Jul 29, 2011
74
30
Google Pixel 3
I actually stopped using BootManager because I thought that might be it, but I still had the issue using only MikG on my device. But I'm beginning to think there's just an issue with my touchscreen.

ROM: MikG v3.11 w/ICS Lite Theme | Kernel: Underworld v0.4 SBC

Same setup I run and I experience the same type of issue. It'll lock-up during some app operation as well. Had to pull the battery a few times. Haven't tried the stock kernel, though

Sent from my PC36100 using XDA
 
  • Like
Reactions: Captain_Throwback

debarron

Senior Member
Mar 1, 2008
429
155
Quick question, are you running this on the phone or in a boot manager slot... I have unresponsiveness when using boot manager especially when sense its in the slot.. Aosp seems more responsive.

In my experience with Boot Manager, it all depends on what SD card you have (not just class).

I had an 8g SanDisk class 4 and Sense & AOSP ROMs ran fine. I bought a PNY 16g class 10 and Sense ROMs would barely run (constantly freeze up), but AOSP were fine. I returned the PNY and got a 32g SanDisk class 4 and both run fine again.

Sent from my PC36100 using Tapatalk 2 Beta-6
 

buckhunter

Senior Member
Mar 1, 2011
1,379
585
mecampo said:
Thanks buck, i'll leave it as is for the moment and maybe try vipermod later if i still want to stretch battery life. Is there a downside of undervolting like lags?

Sent from my PC36100 using XDA

You would get lag and likely reboots. But all phones seem to act different. I flashed insanemod with vipermod and have no issues but seems some are having problems without lowering voltages. Just play around with it and try it out for a day or two and see how it goes.
 
  • Like
Reactions: ca1ne

mecampo

Senior Member
Jan 19, 2011
179
19
Cypress, TX
You would get lag and likely reboots. But all phones seem to act different. I flashed insanemod with vipermod and have no issues but seems some are having problems without lowering voltages. Just play around with it and try it out for a day or two and see how it goes.

Will do, thanks again buck

Sent from my PC36100 using XDA
 

debarron

Senior Member
Mar 1, 2008
429
155
@Captain_Throwback

Do you happen to be charging your phone when the screen stops responding. That's usually when I've seen that issue (I actually experienced it just now), I usually have to unplug my phone and turn the screen off/on for it to start working. I've seen this behavior on the stock kernel as well.

Sent from my PC36100 using Tapatalk 2 Beta-6
 

nick1313

Senior Member
Jan 14, 2011
3,230
752
Columbia
@Captain_Throwback

Do you happen to be charging your phone when the screen stops responding. That's usually when I've seen that issue (I actually experienced it just now), I usually have to unplug my phone and turn the screen off/on for it to start working. I've seen this behavior on the stock kernel as well.

Sent from my PC36100 using Tapatalk 2 Beta-6

I actually have had the same exact issue with this kernel on my phone that captain has. I've tried, oc, underclocking, different gonvernors, schedulers, etc. It happened on previous versions too, however the classic worked great for me, no lag at all on that one. I think my phone just doesn't like this one. I do know that I couldn't ever run the more aggressive nets kernels, I had the same outcome with that kernel that I have with this one.

The sbc worked great, trickle charged all night and stay at 100% like 2-3 hours after unplugging, battery dropped off at that but I think that has something to do with my setup. It's like that on no matter what kernel I use, I haven't full wiped in awhile.

BTW I'm on MikG 3.11 and my red inverted red theme I made.
 
  • Like
Reactions: Captain_Throwback

debarron

Senior Member
Mar 1, 2008
429
155
I actually have had the same exact issue with this kernel on my phone that captain has. I've tried, oc, underclocking, different gonvernors, schedulers, etc. It happened on previous versions too, however the classic worked great for me, no lag at all on that one. I think my phone just doesn't like this one. I do know that I couldn't ever run the more aggressive nets kernels, I had the same outcome with that kernel that I have with this one.

The sbc worked great, trickle charged all night and stay at 100% like 2-3 hours after unplugging, battery dropped off at that but I think that has something to do with my setup. It's like that on no matter what kernel I use, I haven't full wiped in awhile.

BTW I'm on MikG 3.11 and my red inverted red theme I made.

I'm actually on Classic kernel 1.2 using MikG 3.11 completely stock. I had the exact same thing happen to me this morn, while it was still on the charger I tried to unlock and the ring bounced like I just did a tap. Un-plugged it from the charger and turned off the screen and it worked after that. Tried turning off the screen while still plugged in, but no go.

Sent from my PC36100 using Tapatalk 2 Beta-6
 
  • Like
Reactions: nick1313

Top Liked Posts

  • There are no posts matching your filters.
  • 94
    Underworld Sense Kernel

    This is a little something I have been working on. Thank you to those who tested under the "saturday morning" thread. Hopefully I will be able to continue to improve this kernel and add in additional modifications as time goes on.

    And please remember this is a work in progress, so please let me know your results.

    What's in this Kernel

    Features

    Stock Kernel 2.6.35.10
    Patched to 2.6.35.14
    Enabled Wireless N
    Perflock Disabled
    HDMI Fix
    GPS Fix
    3 Point Touch Check
    10 Point Touch
    Audio Boosted with On/Off Toggle (default setting is on)
    Fast USB Charge with On/Off Toggle (default setting is off)
    Reduced Wifi Voltage (battery savings)
    Read Ahead Buffer Upped to 1024kb
    O/C to 1.229Ghz
    HAVS with Sysfs
    Undervolted to LEE Kernel Settings (tiamat)
    Compiler Optimizations
    Superior Battery Charging (SBC)
    Boosted Audio More
    Extend Wifi Range
    Removed CIQ (Please note - you may encounter problems if you rom has ciq in it)
    Flashlight Cutoff Reduced to 10% from 15%
    Increased GPU Memory Allocation
    CIFS (compiled as module)
    TUNS (compiled as module)
    Front Facing Camera Fix (for inverted) (should work on all gingerbread sense)
    Swap Enabled
    Fixed Hotspot for some users
    2 Way Call Record
    Memory/Scheduler tweaks
    RCU Tweaks
    LZMA Compression
    Removed Some Debug Code
    Enabled EXT4 Support (applied performance patch)
    Add ZRAM (Lzo_compress/decompress) as modules)
    Add HTC Kineto_gan support for wifi calling
    Reduce vfs_cache_pressure from 70 to 50
    Wifi is PM_FAST in standby
    Increased Min Voltages from 925 to 950

    Governors

    SmartassV2 (set as default)
    InteractiveX
    Intellidemand
    OndemandX
    Smartass
    Conservative
    Ondemand
    Userspace
    Performance
    Interactive

    Schedulers

    SIO (set as default)
    NOOP
    Deadline
    CFQ
    v(R)
    BFQ

    Instructions

    Apply with your preferred custom recovery.

    For Kernel Install
    Make sure to wipe Dalvik Cache and Cache.

    For SBC
    And make sure the phone is fully booted before plugging it in.

    For HAVS with sysfs interface
    You will be able to use Vipermod to change the voltages. To be able to save changes you will need a rom with init.d support baked in. The kernel has already been undervolted, but since everyone results vary depending on their devices, this interface will allow you to drop it lower, just like you have been able to in the AOSP roms.

    For Audio Boost to turn on and off
    Code:
    Audio Boost On
    echo 1 > /sys/kernel/audio_boost/aboost
    Audio Boost Off
    echo 0 > /sys/kernel/audio_boost/aboost
    Query Audio Boost Status
    cat /sys/kernel/audio_boost/aboost
    For USB Fast Charge to turn on and off
    The below code will toggle it in the terminal, but a cool way to turn it on and off would be to support the original dev who put this mod together, chad0989 by purchasing his widget that controls this version of usb fast charge as well as the patch version. LINK TO WIDGET
    Code:
    USB Fast Charge On
    echo 1 > /sys/kernel/fast_charge/fast_charge_usb
    USB Fast Charge Off
    echo 0 > /sys/kernel/fast_charge/fast_charge_usb
    Query USB Fast Charge Status
    cat /sys/kernel/fast_charge/fast_charge_usb
    Thanks to Capt_Throwback for finding out a reason for some of the lag complaints. It appears that the Vipermod script installs an older copy of busybox onto the phone. I have attached a copy of the vipermod install script that does not install any busybox.

    Credits

    I am grateful to all, from the developers, to the end users who
    provide the feedback and use what is created.

    More specifically (in alphabetical order) I would like to credit
    the following developers for their work.

    atyoung
    barnacles10
    cayniarb
    chad0989
    detcup4evr
    drellisdee
    faux123
    lithid
    ms79723
    netarchy
    paulmck
    TeamWin
    tiny4579
    toastcfh
    ziggy471

    Also I would like to thank 2 alpha testers who kept me going

    swagstr
    tommytomatoe

    Also I would like to thank the man who tested the front facing camera fix

    buckhunter (tested all 4 options I wanted to check) and is now almost constantly testing whatever insane thing I ask him to flash and test, lol
    sclarktay4

    And a special thanks to the following donators who gave me some diaper money for the son.

    eggsack
    Wisiwyg

    Disclaimer

    As with all things, not every variant can be accounted for. Please use at your own risk. I am not responsible for any damages/bricks/etc that may accompany use of this kernel.

    Bug Reporting

    Post a reply in this thread or pm me, and I will do my best to assist and/or correct bugs.

    Update History

    v0.8
    Enable ext4 support
    Ext4 performance patch
    Add zram (lzo_compress/decompress) as external modules
    Add HTC kineto_gan support for WiFi calling
    Reduce vfs_cache_pressure from 70 to 50
    Wifi is PM_FAST in standby
    Increase min voltages to 950 to make more universal
    Upgrade bfq to BFQ-v3r1
    Modified several of the governors
    Added no Havs versions

    v0.7
    RCU Tweaks
    rcu: repair code-duplication FIXMEs
    rcu: combine duplicate code, courtesy of CONFIG_PREEMPT_RCU
    rcu: apply TINY_PREEMPT_RCU read-side speedup to TREE_PREEMPT_RCU
    rcu: fix sparse errors in rcutorture.c
    rcu: Add tracing data to support queueing models

    use lzma instead of gzip
    removed some debugging code to clean things up

    v0.6
    Tiny_Preempt_Rcu Added (smaller footprint)
    Changed Audio boost to on/off toggle
    USB Fast Charge and on/off toggle
    Patched up to 2.6.35.14
    Tweaked SIO/VR/Deadline Schedulers
    2 Way Call Record Added per Request
    Memory/Tweaks:
    Reduce vfs_cache_pressure from 100 to 70
    SLQB Memory allocator added
    Tweak io schedulers for flash devices (deadline,sio,vr)
    Ashmem: fix deadlock when system is low on memory
    Interactive/InteractiveX fix possible divide by 0
    Some memory copy macros and functions
    Add 10 microsec delay before fetching setup_data (usb)
    Fix scaling_available_frequencies sysfs


    v0.5
    BFQ Scheduler Added
    OndemandX Governor Added
    Swap Enabled
    Fixed Hotspot for some users

    v0.4
    Fixed the front facing camera with kernel modfications

    v0.3
    Removed CIQ
    Extended Wifi Range
    Flashlight cutoff reduced to 10%
    Increased GPU memory allocation
    CIFS (compiled as module)
    TUNS (compiled as module)
    Tweaked Smartassv2
    Fixed SIO to be default scheduler (again, lol)
    Added Interactive Governor

    v0.2 - Initial Release

    v0.1 - Test Release.


    Links

    Underworld v08 HAVS, No SBC
    Underworld v08 No HAVS, No SBC
    Underworld v08 No HAVS, SBC
    Underworld v08 HAVS, No SBC


    Github
    19
    Updated OP to v08.

    Please note specifically the addition of EXT4. if you use a2sd you can type: a2sd check
    in the terminal app, and if it says EXT4 yes, then your rom and kernel now can run EXT4.

    I have also compiled some No HAVS versions for those who have difficulty running underworld
    please try these out, their voltages can not be modified, hopefully this will allow others who have
    been running classic/nitrous due to their phone's restrictions to have some fun on underworld.
    Please let me know how this version runs for you, thanks.
    18
    I think I found a flaw in many of the implementations of init.d support in sense roms..

    It almost appears that init.d only runs on first boot and then is disabled..

    Example. If I format all partitions except sdcard, flash a fresh ROM, flash my test kernel that includes a script, then boot, the script makes the changes.. If I then make changes in the script and reboot, I get no further changes..

    Example 2. I format all partitions except sdcard, flash a fresh ROM, do a first time boot, go back to recovery, flash test kernel with the script, upon next boot, no modifications are made.

    When I get time I'm going to play with the ram disk of a ROM, repackage it with the setup I found in CM7, and see if it works... If it does then we have a solution to get rid of needing to use script manager and other apks.

    though if that is true, would need the ROM devs to update their roms... Though I could make some boot.imgs for popular roms...

    So I am excited to see if this theory works..especially since the test kernel has a configurable file that let's you turn on and off audio boost, usb fast charge, governor, scheduler, etc
    18
    Updated to v0.3

    I was trying to figure out how to get the front facing camera to work before releasing, but i haven't cracked it yet, and with the updated source up to possibly a month or so out I figured I should update what I have done already... please let me know if smartassv2 behaves better now


    list of changes.

    Removed CIQ
    Extended Wifi Range
    Flashlight cutoff reduced to 10%
    Increased GPU memory allocation
    CIFS (compiled as module)
    TUNS (compiled as module)
    Tweaked Smartassv2
    Fixed SIO to be default scheduler (again, lol)
    Added Interactive Governor
    16
    Lets use this post finally

    Tips and Tricks

    1. If you are usinig V6 SuperCharger with kernel I/O tweaks. Please uninstall the I/O Scheduler tweak. Failure to do so may casue random reboots. (Thanks Kelldane)
    2. Please navigate to the system/etc folder and scroll down until you find the init.post_boot.sh file and either delete it or move it to a safe place on your sd card. More Info (Thanks Leeboy)
    3. When using smurf, do not use the battery saving settings for Smartass V2 otherwise in most cases it will generate lag on that governor. If you open the 45smurf file in etc/init.d and remove the section with the governer tweaks the lag will go away after reboot. (Thanks Pennie77)
    4. Ensure that your busybox binary is up to date. (Thanks Capt_Throwback)

    Undervolting

    havs kernel has an upper and lower range, while the normal kernel has a static range.. i pulled from my source code the havs voltages and commented after the line the original voltage.

    { 19200, 950, 950 }, // orig voltage 1050
    { 128000, 950, 975 }, // orig voltage 1050
    { 245000, 950, 975 }, // orig voltage 1050
    { 384000, 950, 975 }, // orig voltage 1050
    { 422400, 950, 975 }, // orig voltage 1050
    { 460800, 950, 975 }, // orig voltage 1050
    { 499200, 950, 1000 }, // orig voltage 1075
    { 537600, 950, 1025 }, // orig voltage 1100
    { 576000, 950, 1050 }, // orig voltage 1100
    { 614400, 950, 1075 }, // orig voltage 1125
    { 652800, 950, 1100 }, // orig voltage 1150
    { 691200, 975, 1125 }, // orig voltage 1175
    { 729600, 975, 1150 }, // orig voltage 1200
    { 768000, 975, 1175 }, // orig voltage 1200
    { 806400, 1150, 1200 }, // orig voltage 1225
    { 844800, 1175, 1225 }, // orig voltage 1250
    { 883200, 1200, 1250 }, // orig voltage 1275
    { 921600, 1200, 1275 }, // orig voltage 1300
    { 960000, 1225, 1275 }, // orig voltage 1300
    { 998400, 1225, 1275 }, // orig voltage 1300

    { 1036800, 1275, VOLTAGE_MAX }, //overclocked cpu no orig voltage
    { 1075200, 1275, VOLTAGE_MAX }, //overclocked cpu no orig voltage
    { 1113600, 1275, VOLTAGE_MAX }, //overclocked cpu no orig voltage
    { 1152000, 1300, VOLTAGE_MAX }, //overclocked cpu no orig voltage
    { 1190400, 1325, VOLTAGE_MAX }, //overclocked cpu no orig voltage
    { 1228800, 1350, VOLTAGE_MAX }, //overclocked cpu no orig voltage