[KERNEL] SpeedMod Froyo [K13E HPCall VoodooSnd7 SharpnessFix STABLE]

Search This thread

hardcore

Senior Member
Sep 12, 2006
3,435
7,992
Yeah thats right.
Btw is ext4nj really as unstable as said?
On /dbdata and /cache it is definitely not safe. On /data there is moderate risk.

If you want a slight Quadrant bump then use ext4 all, ext4 mount options: faster. That will give you the same setting as Voodoo lagfix, and about 1700 Quadrant. But there is low-to-moderate risk of data loss as well.
 

corgar

Senior Member
Oct 12, 2010
1,062
118
Rome
Voice in call volume with handfree headset is fine now, set it just a bit higher and i think is perfect.

Sent from my GT-I9000 using XDA App
 

hardcore

Senior Member
Sep 12, 2006
3,435
7,992
Okay, done a bit of testing. T3.

1) Medium light bedroom, yellowish (power saving type): facing light bulb - 2nd level (what I estimate is 25% brightness). Facing away - 1st level (something like 6%). Neither m or n had this behavior, so Huge progress.

2) Outside, completely dark, yellow english lights (look up on internet or something, basically very yellow light). When walking street illuminated only by lights + cars: mostly 2nd level, sometimes switching to 3rd (which I estimate is 50%). Walking by brightly lit stores - 3rd level.

3) McDonalds (basically brightly lit room-cafe-shopping mall) - 3rd level.


Everything is great in terms of minimal brightness (I would even prefer a bit darker level 0, but I guess its a compromise). No complaints here.

Remark about 3rd level of brighness - I would say you could lower it a bit, make a bit more dark (can't remember the measurments you use, but I would say ideal is 10-20 lower).

And speed of brightness switching is also fine for me (pretty quick).
You'll be interested to know that on a scale from 0 to 300 cd, the brightness levels are:

Level 1: 10
Level 2: 40
Level 3: 90
Level 4: 160
Level 5: 300

Level 2: 40 cd is the same as stock's Level 1, and Level 300 is the maximum the screen can go.

As the brightness levels (cd) increases, the increase in actual brightness is much smaller. For example from Level 4: 160 -> Level 5: 300, the increase in visible brightness is small - smaller or similar to the increase from 10 -> 40 or 40 -> 90.
 
  • Like
Reactions: rezam

hardcore

Senior Member
Sep 12, 2006
3,435
7,992
Voice in call volume with handfree headset is fine now, set it just a bit higher and i think is perfect.

Sent from my GT-I9000 using XDA App
Alright, so you think it is still a bit soft? Do you think I should raise it just a notch more?

The reason I lowered it a bit is because I'm trying to reduce distortions from surrounding noise.
 

dupel

Senior Member
Jun 2, 2010
1,394
23
London
You'll be interested to know that on a scale from 0 to 300 cd, the brightness levels are:

Level 1: 10
Level 2: 40
Level 3: 90
Level 4: 160
Level 5: 300

Level 2: 40 cd is the same as stock's Level 1, and Level 300 is the maximum the screen can go.

As the brightness levels (cd) increases, the increase in actual brightness is much smaller. For example from Level 4: 160 -> Level 5: 300, the increase in visible brightness is small - smaller or similar to the increase from 10 -> 40 or 40 -> 90.

Just to clarify - my 25,50% is percentage of slider that sets brightness.

And thanks for explaining stuff.
 

ingineru

Senior Member
Jan 9, 2010
463
14
Something very strange happend to my phone today.
I usually do not use autobrightness that much but around 5 Pm i gave it a try, put it on auto, everything else off, 3 hours later 20 % battery lost!!! - did not touch the screen
Checked with system panel, phone did not sleep at all, i had a continuous 1% cpu ( it is 0 when phone sleeps )
Then i turned off auto brightness, waited 15 mins and i could clearly see 0% cpu..
It seems that auto brightness is eating battery despite the screen is off!!!
k12n
 

sewe

Senior Member
Jul 20, 2010
1,480
233
You mean the stock handsfree microphone level? I increased that for T3, so it should be okay again.
Yes

Alright, so you think it is still a bit soft? Do you think I should raise it just a notch more?
Yes

The reason I lowered it a bit is because I'm trying to reduce distortions from surrounding noise.
Yeah but not at the cost of voice in call volume

Yes. I guess we need just a little bit more volume.

Sent from my GT-I9000 using XDA App
+1
 

hardcore

Senior Member
Sep 12, 2006
3,435
7,992
Something very strange happend to my phone today.
I usually do not use autobrightness that much but around 5 Pm i gave it a try, put it on auto, everything else off, 3 hours later 20 % battery lost!!! - did not touch the screen
Checked with system panel, phone did not sleep at all, i had a continuous 1% cpu ( it is 0 when phone sleeps )
Then i turned off auto brightness, waited 15 mins and i could clearly see 0% cpu..
It seems that auto brightness is eating battery despite the screen is off!!!
k12n
I doubt it, I use auto brightness all the time and don't see that kind of battery drop.
And the auto brightness sensor is off when the screen is off.
And the latest version reads the auto brightness sensor 60% less often than stock.
 

asdfman

New member
Jan 1, 2011
1
0
hi,

i flashed the K12N kernel in CWM, everything was successful und running fine after the update. But then i wanted to enter CWM again and the default samsung recovery 3e appeared :eek:
Why? What happend to my CWM?

Before the flash i had the latest voodoo kernel installed

EDIT: after 2 reflashes with SGS Kernel Flasher CWM was back in K12N :)
 
Last edited:

ingineru

Senior Member
Jan 9, 2010
463
14
I doubt it, I use auto brightness all the time and don't see that kind of battery drop.
And the auto brightness sensor is off when the screen is off.
And the latest version reads the auto brightness sensor 60% less often than stock.

I also doubt it but today i barely used my phone, before 17pm system was not using cpu, after that is uses at least 1%.
At 17 the only thing i did was turning auto brightness
Hard to tell who is eating battery when it says "system"
 

melorib

Senior Member
Nov 30, 2010
3,999
455
Cascais
Sony Xperia 1 II
The lowest level is not as low now anyway, should still be comfortable.

How about checking this.

Dial *#0*# choose sensor and let me know roughly what values u see under light sensor in those conditions.

U can try moving / tilting the phone around to see how it "catches" the light.

After the test the auto brightness is disabled so u have to toggle it.

T3 still goes to min, but I chequed the sensor and it doesnt stop, always changing between 5 and 37, without moving or changing the light... :eek:
 

hardcore

Senior Member
Sep 12, 2006
3,435
7,992
K12O-T4:

Changes vs K12N:

- Auto-brightness slightly brighter in low light
- Mic volume adjustments
 

Attachments

  • speedmod-kernel-k12o-t4-500hz.zip
    6 MB · Views: 336
  • speedmod-kernel-k12o-t4-500hz-CWM.zip
    6.2 MB · Views: 828
  • Like
Reactions: sommart4428

velenoso84

Senior Member
Jul 18, 2008
256
96
sconcauteam.com
L'ho visto da lucapicci, Avrà ricompilato?

I saw it lucapicci. It will have recompiled?

LINK
Code:
Notes:
Recomended to make a backup of your data for more safety.
Disable all lagfixes before install this rom
Kernel default configuration:
Data FS: ext4
Cache FS: ext4
DbData FS: ext4
Mount option: FASTER
System FS: RFS
Tweaks ON: Kernel Scheduler - Misc Battery tweaks

Ho risolto, basta mettere i file .conf nella cartella etc della ROM
Ora mi chiedo, è possibile evitare la domanda della conversione?
Magari mettendo un altro file .conf nella cartella?
Hardcore?

Translate
I solved it, just put the files. conf in /system/etc/ folder of ROM
Now I wonder, you can avoid the question of conversion?
Maybe putting a different file .conf in folder?
Hardcore?
 

hardcore

Senior Member
Sep 12, 2006
3,435
7,992
T3 still goes to min, but I chequed the sensor and it doesnt stop, always changing between 5 and 37, without moving or changing the light... :eek:
Its normal, it fluctuates a lot. Levels below 50 are "darkness". Once you bring it into light you should see it going up to about 200 to 900 (indoors), and up to 2000 outdoors.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 525
    Hi people. This kernel aims to be fast, compatible, stable, and have good battery life. It makes our Galaxy S run the way it should.

    This kernel is for the International Galaxy S (I9000) and Bell Mobility Vibrant (I9000M)

    The SpeedMod kernel for the AT&T Captivate is available here: http://xdaforums.com/showthread.php?t=893880

    Note: Only lagfixes using EXT4 are robust. Other lagfixes run the risk of data loss on freezing, hard-reboots, or sudden power loss.

    WARNING: Before you try any lagfix, make sure that you have enough free space on your Internal SD. You should have at least more free space than data+dbdata+cache combined.

    Latest K13E (12-Apr) - Voodoo Sound v7. Lowmemorykiller fixes. Improved display sharpness using AMOLED processing mode in MDNIE. Support for voice calls through headphones. Check here for more info and downloads.

    >>> Click here for the installation procedure using Odin.

    >>> If you have questions, please read the FAQ: Frequently Asked Questions first!

    >>> What is the SpeedMod kernel?

    Latest features:

    - Compiled using codesourcery 2010.09: Faster and more battery efficient
    - The only properly working Tiny RCU implementation, thanks to Paul McKenney
    - More efficient: Removed debug logging from kernel and Android
    - Most updated version of my Enhanced Universal Lagfix fork with improved stability
    - Full Android 2.2.1 ROM compatibility

    This kernel has:

    - Based on JPX Android 2.2.1 kernel source
    - Works on all stock Froyo 2.2 and 2.2.1 ROMs and popular custom ROMs
    - 340MB RAM
    - Enhanced version of sztupy's Universal Lagfix
    - Includes neldar's BackLightNotification 2.3 from https://github.com/project-voodoo/backlightnotification/tree/master/kernel_patches/
    - Sharpness (AMOLED mode) & color fixes for the screen
    - SpeedMod: Replaced kernel jhash2 with jhash3
    - Includes my Startup Tweaks from http://xdaforums.com/showthread.php?t=813309
    - Adjusted kernel HZ value to improve smoothness
    - Uses BFQ IO scheduler by default, from http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php
    - Updated ext4 code in kernel from http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/
    - Properly working Tiny RCU for better speed and efficiency from http://android.git.kernel.org/?p=ke...it;h=9b1d82fa1611706fa7ee1505f290160a18caf95d
    - Patched lowmemorykiller for compatibility with Tiny RCU from http://android.git.kernel.org/?p=ke...ff;h=5545554aac04918ece318270d63cbfcb015577a9
    - Optimized compiler flags: -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp

    --------------------------------

    FOR BEGINNERS:

    This kernel is based on sztupy's Universal Lagfix: Lagfix and root options are accessible by booting into the Recovery Menu.

    To get the best speed, it is recommended that you enable all Tweaks from the Recovery Menu. Tweaks are under SpeedMod features. Info on Tweaks: http://xdaforums.com/showthread.php?t=813309

    How to root: http://xdaforums.com/showpost.php?p=8896862&postcount=90

    Kernel HZ value: HZ=500 is smoother, HZ=256 is Samsung default.

    --------------------------------

    Memory configs (K10J and later):

    CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=2048
    CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=4096
    CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500
    CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=12288
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=32768
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=32768
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=10240
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMD=3072

    Memory configs (K10I and earlier):

    CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=4096 *#
    CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=8192 *#
    CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500
    CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=11264 **
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=11264 **
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=30720 ##
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=30720 ##
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=1024 *#
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=6144 ^^
    CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMD=3072

    ** FIMC0/2 = Below this and 720P video recording won't work
    ## MFC0/1 = Below this and 720P video playback won't work
    *# PMEM/PMEM_GPU1/JPEG = Taken from default values for Galaxy Tab
    ^^ TEXTREAM = Too low and 3G video call stops working

    THANKS: Big thanks to sztupy for his kernel compiler VM and ULFK, lastufo for testing compiler optimizations, ykk_five for testing memory configs, and others who gave ideas or helped.

    --------------------------------

    WARNING: If you use a custom boot animation, apps like One Click Lag Fix will not work because it disables the playlogos1 script hack.

    The files with ending with -CWM are for flashing using Clockwork Recovery.
    These other zip files are for flashing with ODIN.

    --------------------------------

    About USB Mounts:

    >>> Click here to download the USB mount fixes. Latest SpeedMod versions do not need this fix. The fix is for using K12E or older with 2.2 ROMs. It fixes the problem where Internal SD mounts as a read-only drive on the PC, or if the External SD does not get mounted.

    >>> If you have questions, please read the FAQ: Frequently Asked Questions first!

    >>> CLICK HERE to DOWNLOAD the kernels.
    47
    Updated test: K12Q-T7:

    This version is unbelievably smooth!

    Android Logger (logcat) disabled by default (can be re-enabled via Tweaks).
    Kernel debug messages have been disabled.
    Fixed the super loud notifications with Voodoo Sound.

    Changes from K12P:

    - Disabled Android Logger (can be re-enabled via Tweaks)
    - Disabled all kernel debug messages for efficiency
    - Changed boot logo to I897 logo for AT&T Captivate version
    - Changed /cache to ext4nj in recommended ext4 lagfix to fix large Market downloads
    - Optional IPv6 Privacy support in Tweaks
    - Voodoo Sound v2 compatible
    - Fixed loud notification problem with headphones
    - Fixed popping / clicking noise when music and FM radio is stopped / started
    - Better FM Radio sound:
    - - Really removed the high pass filter and DRC from FM Radio (restores full bass)
    - - Turn on 4FS mode for ADC in FM Radio (smoother high frequencies)
    - - Turn on 128x oversampling for ADC and DAC in FM Radio mode
    - Adjusted volume of FM Radio and Media Playback to be similar
    - General sound quality improvements:
    - - Maximized digital mixer output to improve SNR and resolution
    - - 128x oversampling option in Voodoo Sound enabled by default
    - - Explicitly disable DRC and NG during media playback, if +1.5dB mode is NOT selected

    For those people who requested IPv6 privacy, please let me know if it works in this version.
    41
    On 12A, the battery seems better - but only marginally so - i still see Wifi using 35% on a mostly idle phone. If I remember right, the previous usage used to be around 5% - definitely single digit. Something is still wrong with wifi with JPY ROM/Modem....
    Its not the ROM or modem. I think its the new Wifi firmware. I've started a thread to collect Wifi firmware versions.

    http://xdaforums.com/showthread.php?t=885903

    In the meantime, if you want u can experiment. I've created update.zip packages to update/overwrite the wifi firmware (it's in /system/etc/wifi).

    You can try to use the older (DXJPA) wifi firmware and see how that does in terms of power.
    If you don't like it, you can put back the XXJPY wifi firmware with the other package.

    Let me know your findings, if u try it out.

    DXJPA wifi firmware is working fine with my XXJPY rom. Gonna check out the battery usage.

    FYI:
    DXJPA: Firmware version = wl0: Jun 4 2010 14:21:21 version 4.218.214.3
    XXJPY: Firmware version = wl0: Nov 16 2010 08:56:21 version 4.218.250.38
    26
    K12U was just out, but here is K13A-T1!

    Changes:
    - Single version for neutral/cold/warm color, selectable from Recovery
    - Option to disable darkest auto-brightness level, selectable from Recovery
    - Minor optimizations to brightness sensor driver

    Otherwise it is the same as K12U.
    25
    SpeedMod + Voodoo Sound test version!

    K12L-T5:

    Changes from K12K:
    - Improvements to FM Radio sound: remove Dynamic Range Compression
    - Voodoo Sound v1: FM radio bass fix, controllable headphone output via app
    - rear speaker volume +1 for media
    - light sensor polling interval changed to 2s instead of 0.5s
    (saves battery, more stable brightness levels)
    - light sensor sensitivity adjusted so that the screen doesn't turn bright so easily
    (saves battery and reduces screen burn)
    - adjustments to IO Tweak (super smooth now!)
    - changed battery level polling interval to 60 seconds, from 5 seconds

    Note that you need Supercurio's Voodoo app to adjust the headphone level. If u don't install it, the default level is the same level as K12K (+1 from Nexus S, or +3 from SGS).

    PS. The FM radio sound is really awesome after those voice filters have been removed!