[23-Sep-2011][Kernel][Patch] Lagfree and Smoothass governors - Galaxy Tab Android Development

Hi fellows!
I have been building a kernel for P1000L/N based on Overcome v3.3.1 Kernel.
Additionally, I added to my version two new governors: lagfree and smoothass.
Here are the description of each one:
Lagfree governor
'lagfree' - this driver is rather similar to the 'ondemand'
governor both in its source code and its purpose, the difference is
its optimization for better suitability in a battery powered
environment. The frequency is gracefully increased and decreased
rather than jumping to 100% when speed is required.
Smoothass governor
'smoothass' - Slightly more aggressive smartass
I'm uploading here the .patch to add this both governors to P1000 kernel tree.
This patch was maid to be applied on top of Overcome v3.3.1 kernel, but anyone with some knowledge about diff/patch should be able add the both governors in your kernels.
If you want to check my kernel tree, visit my github account:
https://github.com/ronisbr
Just for information, lagfree is my default governor now
23-Sep-2011
I did some modifications in the patch to make it more compatible with different kernels. If you want to try to patch your tree, download .zip attached here, decompress, go into your kernel directory and type:
patch -p1 < (Folder you decompressed the .zip file)/ronan-P1000-lagfree-smoothass-20110923.patch
Thanks!
Ronan

Reserved......

is it for GT-P1000 too? Or GT-P1000L/N only?

ayong chia said:
is it for GT-P1000 too? Or GT-P1000L/N only?
Click to expand...
Click to collapse
The kernel I'm working on is just for P1000L/N.
But the patch that I attached here should work on every P1000 kernel. Actually, if it was applied right, it should work on every android kernel (2.6.35 version at least).
Thanks,
Ronan

Ronis_BR said:
The kernel I'm working on is just for P1000L/N.
But the patch that I attached here should work on every P1000 kernel. Actually, if it was applied right, it should work on every android kernel (2.6.35 version at least).
Thanks,
Ronan
Click to expand...
Click to collapse
How do you apply it? Do I have to do any compiling first or is it a patch that can be flashed via recovery?

where do i apply this patch?

0vermind said:
How do you apply it? Do I have to do any compiling first or is it a patch that can be flashed via recovery?
Click to expand...
Click to collapse
This patch needs to be applied to the kernel source code.
After, you need to recompile your kernel and flash it.
Thanks,
Ronan

dizgustipated said:
where do i apply this patch?
Click to expand...
Click to collapse
Well, if you are using overcome kernel or something similar, you should go into your kernel directory and type:
patch -p1 < ronan-P1000-lagfree-smoothass-20110922.patch
But it is very unlikely that you will do it without problems since I have generated this patch from my own kernel. So, the best thing to do, is to open the .patch file, analyse it, and apply the changes manually.
If you want, post your kernel somewhere and I'll send the specific patch for your kernel.
Thanks,
Ronan

Related

[05-Nov-2011][Kernel][GB][P1000L/N] Ronan's Gingerbread Kernel

Hi fellows!
As some of you have seen in Humberto's P1000L/N Gingerbread thread, I'm building a Gingerbread kernel for these devices.
At the beginning, I thought that I'll just port the Overcome kernel to ours devices and I'll never touch on these files again.
But it turns out that it shouldn't be like that. So, to avoid mess with Humberto's thread, I decided to begin a new one.
Here are the current features of my Kernel, which was initially based on Overcome v3.3.1 kernel:
Main Features of latest stable version (20111029)
Kernel 2.6.35.14
Lagfree governor
Smoothass governor
SmartassV2 governor
BFQ IO scheduler version 2 (revision 1)
Conservative, Ondemand, Performance, Powersave, and Userspace governors from 3.1 kernel tree
Built with 2011.03 toolchain
TV SUPPORT (P1000L only)! (it is available if you flash the recently leaked P1000L gingerbread version: http://forum.xda-developers.com/showpost.php?p=17993125&postcount=355)
10-points multitouch driver
File Systems support: RFS/EXT{2,3,4}
Overclock (@1.6GHz) with these steps: 1.6ghz, 1.5ghz, 1.4ghz, 1.3ghz, 1.2ghz, 1ghz, 800mhz, 600mhz, 400mhz, 200mhz, 100mhz
Undervoltage
Touchscreen Undervolted (from 3.3V to 2.1V)
RAM Undervolted (1.8V to 1.7V)
ADC Unvervolted (3.3V to 3.0V)
Voodoo Sound v10
Built in CIFS/TUN/SlowWork support
Stochastic Fair Blue (SFB) Network Scheduler
V(R) Schedule, but SIO set as default.
Autogroup Scheduler
Asynchronous I/O Enabled (AIO)
Backlight Notifications
Humberos' Initramfs 20111102
Features that needed to be test (I'll appreciate any help):
BLN has problems
I'll appreciate any help or feedback!!
Link for download the latest stable version:
http://www.mediafire.com/?9ug8n71vgc5ik7u
md5sum zImage
0fce8943c0b950c05e0d5163cf662460 zImage
Source code:
https://github.com/ronisbr/GT-P1000LN-GB-Kernel
I would like to thanks:
The Overcome project
jdkoreclipse
koxudaxi
Humberos
Thanks,
Ronan
Changelog
20111105 UNSTABLE (http://www.mediafire.com/?13g5330zs209qn1)
md5sum zImage
21248e6f24a54a99947b248c33cad7b2 zImage
This is an UNSTABLE kernel, and we are expecting some functionality breakage! Again, some patches that I applied hasn't been tested in any other GT kernel yet...
Use tiny-shmem instead of full shmem implementation
Tiny shmem is an alternative implementation of shmem filesystem that uses RAMFS code instead TMPFS. It should be suitable for small system which doesn't have swap and doesn't need the advanced features that the full implementation has, e.g. the size limit control. By removing these unnecessary features, tiny-shmem should increase the performance.
For Galaxy TAB, swap isn't used and size limit isn't a necessary feature, so tiny-shmem should work well.
But it is just my guess! I really need help to test it...
Many performance tweaks in low killer memory
It should make memory manager better.
Enable CPU-supported unaligned access
Enable the option CONFIG_ALLOW_CPU_ALIGNMENT, since the Galaxy Tab P1000 has a Cortex-A8 based CPU.
Advanced ARM processors, such as the Cortex series and ARMv7-based CPUS are capable of performing unaligned accesses for many types of memory accesses. Typically, using a cpu-based alignment fixup is faster than doing such a fixup in software. For best performance on advanced CPUs.​
20111029 STABLE (http://www.mediafire.com/?9ug8n71vgc5ik7u)
This version was made stable on 05-Nov-2011, since there weren't any bug reports.
md5sum zImage
0fce8943c0b950c05e0d5163cf662460 zImage
At this point, I decided to add more aggressive updates in my kernel.
I have searched the others gingerbread kernels for devices like GT to verify if there is anything that can be used here.
Conclusion: I found tons of things that can make our experience and overall stability better.
For this first time, I just added some of them and I'm willing you to test it and report anything weird that you find.
Update initramfs from Humberto's kernel
Update initramfs from Humberto's kernel. It now has:
- CwM recovery v5.1.2.6
- New su binary v3.0
Thanks to Humberos
Erase memory pages when they are freed
Should improve memory handle.
Thanks to renaudallard.
net: wireless: bcm4329: compile wifi driver with Os flag
Add -Os GCC optimization flag to compile wifi driver.
This approach was used in Galaxy S kernel, so it should be fine
in GT-P1000 also.
Thanks to zachariasmaladroit.
ashmem improvements
ashmem: fix deadlock when system is low on memory
ashmem: Add cache flush routines to ashmem (zachariasmaladroit)
cpuidle: menu: fixed wrapping timers at 4.294 seconds
If everything goes fine, I'm planning to add more and more patches at each update.
This way, it would be much easier to track possible regressions.​
20111026 (http://www.mediafire.com/?7fv630kp5bu15ev)
Using 2011.03 toolchain again
It turns out that the problems regarding random reboots with 2011.03 toolchain is being caused by samsung modemctl driver. For some reason, it isn't compatible with the newer toolchain, so the solution was avoid the driver building and use a binary version that was built with 2009q03 toolchain.
After this, the new kernel built with 2011.03 toolchain doesn't appear to have the random reboots and problems of the old version.
Thanks to alterbridge86 and chib_cr!​
20111025 (http://www.mediafire.com/?931h2ev795faztf)
Revert to 2009q3 toolchain
When the kernel was built with 2011.03 toolchain, some users are having random reboots, e.g. when the USB was plugged the TAB rebooted.
Thanks chib_cr!​
20111024 (http://www.mediafire.com/?o8be3gs8dfb609u)
I want to thanks alterbridge86 and the Overcome project. Basically, every change was taken from his tree.
Tweak IO schedulers for flash based devices
Should bring some improvements.
ARM: dma-mapping: free allocated page if unable to map (Russell King)
Should kill some process getting stuck and holding the CPU from entering deep sleep, which result in battery drain.
Update smartass governor to version 2 (erasmux)
New version of smartass governor.
Tweak touchscreen sensitivity
Touchscreen sensitivity is improved.
Add compatibility for 2011.03 toolchain
This kernel is being built with 2011.03 toolchain, which should bring some improvements.
Update BFQ IO scheduler to version 2 (revision 1)
Thanks to koxudaxi​
20111006 (http://www.mediafire.com/?ahqucc9h5vwgo8j)
Don't check module magic (by Koxudaxi)
This fix some boot loop issues after build the kernel under certain conditions.
Set Kernel version to 2.6.35.14
It turns out that Overcome kernel has already applied all kernel's patches up to 2.6.35.14, so the correct version was set in Makefile.​
20111005 (http://www.mediafire.com/?zm5t2w82feqtjuy)
Change RAM voltage from 1.8V to 1.7V
Fix BLN
Although, it still has issues.
Change ADC voltage from 3.3V to 3.0V
Change LCD voltage from 3.3V to 2.1V
10-points multitouch driver
samsung_modemctl is being built now
Overcome kernel is using a pre-built samsung_modemctl driver, because it is avoiding kernel to be built correctly. Here, this issue doesn't happen, so this change was reverted.​
20110923 (http://www.mediafire.com/?2e0565sc1sgqmqr)
Update governors set from 3.1 kernel tree
The following governors were updated using Linux 3.1 kernel
tree:
Conservative
Ondemand
Performance
Powersave
Userspace
​
20110916 (http://www.mediafire.com/?98y1xe2hhu1mrtr)
Added lagfree governor
Thanks to jdkoreclipse.
Added smoothass governor
Thanks to jdkoreclipse.​
20110909 (http://www.mediafire.com/?92d7sz9e7niuz2z)
Initial commit
Overcome Gingerbread Kernel v3.3.1 with Samsung's
P1000L/N Gingerbread Kernel patches.​
Reserved......
Downloading...
I'll give it a try!
chib_cr said:
Downloading...
I'll give it a try!
Click to expand...
Click to collapse
Thanks
Tell me what do you think (remember it is a Gingerbread kernel for P1000L/N devices!).
I'm looking for feedback, specially about the new governors...
Works great!
Can't set clock to 1600 Mhz (freezes), but at 1500Mhz it scores 2505 on Quadrant!!
So far smoothass working well...
Tested for about 10 min, so can't tell you much...
BTW: I',m running stock 2.3.3
Install
How to install this file to tab?
Spyma said:
How to install this file to tab?
Click to expand...
Click to collapse
If you have a P1000L/N tab with Gingerbread, you just need to restart it in download mode, unzip the file, and flash with heimdall:
heimdall flash --kernel zImage
But BE CAREFUL, if you don't know what you are doing, you can brick your tab!
ok thanks.
Just for your information, I have just build a kernel with swap support.
To test it, I created a swap partition on my sdcard.
It is working. Although, I haven't seen any improvements...
When I open too many programs (like 8), android memory manager still force-kill the apps, while I'm expecting that the programs should be transfer to swap memory and, just when it is full, that a program should be force killed.
Well, if anyone wants, I can upload a kernel with swap support, but, at this time, I think it is useless...
Ronis_BR said:
If you have a P1000L/N tab
Click to expand...
Click to collapse
I tried to find out the different models and how they equate to one another but Google sends me to everything but which is which model. I have according to my devices "about" a GT-P1000. But, how do I know which model is the L or N? Just to give you more info, I am using the T-Mobile flavor with the modem swap program with Kratos currently flashed.
Hi fellow,
P1000L/N are latin model, if you are using Overcome Kratos with default kernel, you probably have a P1000 device and my kernel isn't compatible.
But you can check it under configurations / about ... (the last menu option), it should have as model number GT-P1000.
Thanks,
Ronan
Hi fellows!!
I have just tested the recently leaked gingerbread version with my kernel and everything is working flawlessly, including TV!
I'll post more details...
Ronan
Ronis_BR said:
Hi fellows!!
I have just tested the recently leaked gingerbread version with my kernel and everything is working flawlessly, including TV!
I'll post more details...
Ronan
Click to expand...
Click to collapse
A leaked GB version for L/N or just L?
If it has TV support I think it is for the L version. But which is the GB version? 2.3.3, 2.3.4 or 2.3.5?
If ti is something better than 2.3.4 I'll try it on my P1000N.
hi could you post de tv app?
davioxx said:
hi could you post de tv app?
Click to expand...
Click to collapse
Just the TV app won't work. You will need the entire ROM and P1000L model.
santroph said:
A leaked GB version for L/N or just L?
If it has TV support I think it is for the L version. But which is the GB version? 2.3.3, 2.3.4 or 2.3.5?
If ti is something better than 2.3.4 I'll try it on my P1000N.
Click to expand...
Click to collapse
No, it is 2.3.3. Basically, it is P1000N version with TV support Nothing more...
Which voltage settings are you guys using ?
Sent from my GT-P1000L using xda premium
Tks, Ronis. Running your kernel for a few days now, all good. Using smoothass, smartass and lagfree, up to 1300 stable, -50mV on 1300 and -25 on the rest.
Cheers.
- Tapatalk - SGT-P1000N - Overcome Kratos -
Running this kernel as well, no issues so far! Thanks!
Sent from my GT-P1000L using Tapatalk

TF300T kernel source repository

https://github.com/untermensch/asus_kernels
getting started with building kernels:
http://source.android.com/source/building-kernels.html
I started with the source from the ASUS website and the Linux 3.1.10 source from
kernel.org and made a some patches for the various directories, created a new git
repository and made a commit after each patch is applied to the Linux 3.1.10
kernel source tree. So now you can browse the changes made to the Linux 3.1.10
source to make it into a kernel for the TF300T.
update 11-21-2012:
add cifs, md4 modules
update 10-27-2012:
add data2sd support
uncap sd card DTR
add DUB-E100 revision C dev id
update 10-11-2012:
add zram support
add zram swap
add init.d
add OC kernel for the TF300TL, TF300TG
update 10-05-2012:
fix exFat mounting
revert MosChip MCS7830 driver
update 10-04-2012:
NTFS R/W via ntfs-3g
noauto_da_alloc added to fstab.cardhu
updated MosChip MCS7830 driver
added GPU overclock to 520Mhz from Motly-git
added user voltage control from Motly-git
possible I/O latency tweek
update 10-02-2012:
NTFS mount fail fixed (read only)
all I/O scheduler's included
support for MosChip MCS7830 based Ethernet adapters added
attached is the current snapshot of the repository.
changes:
debug stuff removed
OC to 1.6GHz
simple I/O scheduler as default
pegasuq governor added
zcache and cleancache enabled
CWM flash-able
Great move... lets see if someone dedicates some time to this wonderful gadget
Sent from Chanook 300 using Tapatalk 2
I'm running the source built kernel now and it appears that all the devices work
you may want to start a dev.. go ahead
untermensch said:
I'm running the source built kernel now and it appears that all the devices work
Click to expand...
Click to collapse
Hi !
..also I compiled the 10.4.2.9 kernel source code , and seems to be stable and no issue !
:good:
I have somme issue with dock keyboard ...as soon as it is connected = frequent reboot in any JB rom ( stock or custom !)
I hope this latest update 10.4.2.13 to resolve this ! :good:
untermensch said:
https://github.com/untermensch/tf300t_kernel
I started with the source from the ASUS website and the Linux 3.1.10 source from
kernel.org and made a some patches for the various directories, created a new git
repository and made a commit after each patch is applied to the Linux 3.1.10
kernel source tree. So now you can browse the changes made to the Linux 3.1.10
source to make it into a kernel for the TF300T.
Click to expand...
Click to collapse
Thanks for your work.
Could you tell me why would be beneficial to port Linux 3.1.10 to the TF300?
Valantur said:
Thanks for your work.
Could you tell me why would be beneficial to port Linux 3.1.10 to the TF300?
Click to expand...
Click to collapse
the official ASUS kernel source is based on 3.1.10 so I am not porting anything, I am using
github to display the differences between the source released by ASUS and the base Linux
3.1.10 source it was built from. I do believe that the repository would be helpful to port to
a newer kernel, after the patches have been applied it is basically the ASUS source, but I
did fix a few things so it would build.
applied patch for the 10.4.2.13 kernel source
untermensch said:
applied patch for the 10.4.2.13 kernel source
Click to expand...
Click to collapse
Good .. that should fix the reboot issue which afaik occurs if you have a SD inserted in the dock
Sent using The Beast via Tapatalk 2
CPU over clocking to 1.6Ghz pushed to the repository
add
Code:
CONFIG_TEGRA_OC=y
to your .config
and remove
Code:
CONFIG_TEGRA_EDP_EXACT_FREQ=y
from your .config
or make xconfig and tick the TF300T Over Clocking check box
well that is nice. Can you post your OC Kernel for us?
mikaole said:
well that is nice. Can you post your OC Kernel for us?
Click to expand...
Click to collapse
here is the kernel plus the modules that go into /system/lib/modules
see this post for install instructions
http://forum.xda-developers.com/showpost.php?p=31944448&postcount=34
Thx, but Kernel is not flashable
untermensch said:
here is the kernel plus the modules that go into /system/lib/modules
Click to expand...
Click to collapse
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
stevtec86 said:
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
Click to expand...
Click to collapse
normally you just flash the kernel in Recovery and you can copy the modules with root explorer. But flashing the Kernel fails in TWRP.
nothing I do will ever be "flashable" because people are stupid and will flash anything on to
any device.
install the kernel vi fastboot
Code:
fastboot flash boot kernel.blob
modules are optional install via adb while in recovery
Code:
adb shell sh -c "rm -fr /system/lib/modules/*"
then cd into the directory with the modules
Code:
adb push ./ /system/lib/modules
stevtec86 said:
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
Click to expand...
Click to collapse
this is a 10.4.2.13 kernel, the ram disk is stock. I'm sure if you request it
the dev for your kernel will merge the overclocking changes so you can
have OC to.
thx, just saw the blob myself. Its already done
Works fine here. Big THX
untermensch said:
this is a 10.4.2.13 kernel, the ram disk is stock. I'm sure if you request it
the dev for your kernel will merge the overclocking changes so you can
have OC to.
Click to expand...
Click to collapse
Two other questions:
1 - I have the TERP recovery, is that a problem?
2 - OC frequencies can be selected?
1. no problem at all, have TWRP, too
2- Yes can be selected in the OC app like set CPU or Antutu Master

<DISCONTINUED>[SC-02B][CM-10.1_PATCH]Howto install I9000 CM-10.1 ROM to GS1 NTT Japan

<DISCONTINUED>[SC-02B][CM-10.1_PATCH]Howto install I9000 CM-10.1 ROM to GS1 NTT Japan
WARNING!! For SC-02B Galaxy S1 NTT-Docomo Japan only...
Basically this patch is original work by HiroyukiIkezoe (hiikezoe) on his kernel. I just apply his codes & try to compile it.
Since I don't know how to unpack & repack boot.img on cm-10.1, I use stratosk ramdisk with some modification to suite my needs. I failed to clone & fork it, maybe because too big, so I download it as zip file, make some changes & push it to github with smaller size.
First install from stock rom:
A. Install CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.zip with odin. Read about how to get odin and using it from
SC-02B Root, Latest Firmware, CWM & Compatible ROMs by IparryU
B. Edit build.prop file from root explorer or similar function, change SC-02B to GT-I9000
before:
Code:
ro.product.model=SC-02B
ro.product.name=SC-02B
ro.product.device=SC-02B
ro.product.board=SC-02B
ro.build.product=SC-02B
after
Code:
ro.product.model=GT-I9000
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.build.product=GT-I9000
C. Get a CM-10.1 rom & install instruction from [NIGHTLY][ROM][4.2.2] CyanogenMod 10.1 for Samsung Galaxy S thread.
D. Download & install LL1 Modem
E. Download & install this 3 files:
1. Kernel: nutest_sc02b-mMdD.zip or stock/mackay/semaphore unofficial ports from Download Link
2. LL1 GPS and RIL binaries
3. JB_BigMem_26-aug-12.zip by kasper_h
F. Reboot and go to Settings > Wireless & Networks > More... > Mobile networks > Network operators & Choose automatically
G. Edit build.prop file from
Code:
ro.telephony.ril_class=SamsungExynos3RIL
to
Code:
ro.telephony.ril_class=RIL
H. Reboot your device.
Click to expand...
Click to collapse
Update or install any CM-10.1 based rom:
1. Read the rom thread for download info & install guide, like step C. Don't install rom with original partition, since the kernel didn't support it!
2. Repeat E, F, G & H steps.
Click to expand...
Click to collapse
Troubleshoot:
For baseband unknown, no network and data not connected try this steps:
- Turn off data.
- Turn on Airplane Mode from setting menu.
- Reboot.
- Wait 1-2 minutes after bootanimation end, then turn off Airplane Mode.
Known Bugs:
1. Airplane Mode on-off toggle often not work.
2. GPS takes too long time before lock with poor accuracy.
3. Charging when phone switched off didn't show the battery indicator correctly. Read this for detail. Fixed in 20130606 release and after.
Unofficial Kernel Ports:
I add various kernel based on i9000 version, read about the feature or change logs on it's original thread but don't report any bugs (except you can prove it happened in original version)!!!
>> Stock cm-10.1 kernel
file: cm-10.1-sc02b-kernel-yyyymmdd.zip
Finally (May 2013) I found proper way to unpack stock kernel using this kernel-repack and repack again using a part of script from here
It's not real stock, but I think close enough to the origin. You may need revert the bigmem patch by install this if you have problem with video capture/playback function.
sc02b changes: stock-cm branch
>> Semaphore kernel ("s" variant only)
file: Semaphore_JB_<version>sj.zip
info: original thread
sc02b changes: sema branch
>> Mackay kernel ("vc" flavour only)
file: Mackay_kernel_<version>_VC-sc02b.zip
info: original thread
sc02b changes: mackay branch
>> Devil kernel *obsolete*
info: helly bean rom thread since no separate thread for devil kernel on cm-10.1
sc02b changes: devil branch
Click to expand...
Click to collapse
Various Modem:
If latest (LL1) didn't make you happy, read about older modem in this post
Credits:
pawitp
hiikezoe
stratosk
kasper_h
derteufel1980
danielsanchez
iparryu
all epic4g, nexus s/s4g & i9000 variants kernel devs
all sc-02b tester & users
Source:
- kernel
- ramdisk
- ramdisk for semaphore
Alright..about our suggestion on editing kyapa's kernel..so that we can have bigger ram..any comment?.ive just backread our old thread and you said there that you have build kyapa for our stock LC04..how is that?.as i remembered the ram of kyapa is about 490 (i suppose)..is it the tweaks that kyapa applied on the kl4?.is it possible for us to have that on our LC04?.thank you..such a good man.
Nutest change logs
Build 20130705
Additional changes compared to stock cm-10.1:
- SC-02B patch by Hiikezoe
- Sync to linux-3.0.y kernel stable and (sometimes) patched with 3.0.y-rc1 stable review
- Sync to android-3.0 aosp kernel common
- Live OC by Ezekeel^ with 110 max value
- Selective LiveOC^ from Lynx/Devil kernel
- Deep Idle^ by Ezekeel (on by default)
- Add 1.32GHz oc step from Mathkid
- Custom Voltage^ by Ezekeel
- Remove most debug info (Stratosk)
- 8 CPU governors: Userspace, Conservative, Ondemand, Interactive (default), Smartass2, Lagfree, Lazy and Wheatley
- 6 I/O Schedulers: Noop, Deadline, CFQ, ROW (default), SIO and FIOPS from mackay kernel
- 397 MB available RAM (need BIGMEM patch)
- Voodoo Color^^ from Mackay/Devil kernel
- Mackay TWRP 2.5.0.0 (blue)
- Modified ramdisk based on stable CM-10.1.0
- Compiled with Linaro 13.06
- some other changes (O3, ZCACHE, etc...)
^ = set with nstools
^^ = set with Voodoo Sound
Full logs and source:
nutest branch
ramdisk-sc02b
if u want to increase ur ram do an exchange.
btw is the bigmem a ram tweak?
Sent from my GT-I9000 using Tapatalk 2
didhiy said:
ram is 398mb on this build, think I can't get higher than that
Click to expand...
Click to collapse
oh i see..its a new kernel..thanks..about the Big Mem?.I have a semaphore manager and it has a big mem already..is that ok?.or instead flash it?
sir didhiy the kernel you posted here is a new one or still the december 31 build??
greedisgood99999 said:
oh i see..its a new kernel..thanks..about the Big Mem?.I have a semaphore manager and it has a big mem already..is that ok?.or instead flash it?
Click to expand...
Click to collapse
only 398mb ram available, no option to switch between memory size like semaphore kernel
archrae said:
sir didhiy the kernel you posted here is a new one or still the december 31 build??
Click to expand...
Click to collapse
this is a new build, kernel updated to latest 3.0.58
its nice that our ram increases at 15mb. thanks didhiy. and and the creator of bigmem.
Sent from my GT-I9000 using Tapatalk 2
thanks didhiy for ur help and all those who contributed in getting our old sweetheart sg1 so far lol any upgrades on better battery life....
kma221 said:
thanks didhiy for ur help and all those who contributed in getting our old sweetheart sg1 so far lol any upgrades on better battery life....
Click to expand...
Click to collapse
well, since we came straight from gb stock rom... the battery life seems really shocking compared to it
I guess it all happened to all i9000 variants. I have epic4g with cm-10.1 too & battery life is equal to sc-02b
Edit:
Seems this commit fix battery drain problem
Modify battery variables
Click to expand...
Click to collapse
I was wondering if there was a way to get ram like kyapa's kernel but have a deeper look in the ram with an app called memory info and swapcheck I realized...
t10mod3
total ram-504mb
swap total-160mb
didhiy's kernel
total ram-408mb
swap total-0mb
since swap memory is available if we get space on sd card I think didhiy's kernel got more ram than t10mod3, am I right!?
u can check it by your self with this app!
thanks for the good work and updates in this kernel didhiy!
eternalcrewthiago said:
I was wondering if there was a way to get ram like kyapa's kernel but have a deeper look in the ram with an app called memory info and swapcheck I realized...
t10mod3
total ram-504mb
swap total-160mb
didhiy's kernel
total ram-408mb
swap total-0mb
since swap memory is available if we get space on sd card I think didhiy's kernel got more ram than t10mod3, am I right!?
u can check it by your self with this app!
thanks for the good work and updates in this kernel didhiy!
Click to expand...
Click to collapse
wow. i hope didhiy can work on this stuff. hope he can do a swap of lots of memory.
Sent from my GT-I9000 using Tapatalk 2
eternalcrewthiago said:
I was wondering if there was a way to get ram like kyapa's kernel but have a deeper look in the ram with an app called memory info and swapcheck I realized...
t10mod3
total ram-504mb
swap total-160mb
didhiy's kernel
total ram-408mb
swap total-0mb
since swap memory is available if we get space on sd card I think didhiy's kernel got more ram than t10mod3, am I right!?
u can check it by your self with this app!
thanks for the good work and updates in this kernel didhiy!
Click to expand...
Click to collapse
can you refer me to the kernel source? I knew kyapa kernel based on talon kernel, but not that much ram as I remember
about swap, I decide to disable it I already push all my work to github so everyone can test another config to try
semaphore kernel thread have useful guide to build a kernel, I used it as reference.
didhiy said:
can you refer me to the kernel source? I knew kyapa kernel based on talon kernel, but not that much ram as I remember
about swap, I decide to disable it I already push all my work to github so everyone can test another config to try
semaphore kernel thread have useful guide to build a kernel, I used it as reference.
Click to expand...
Click to collapse
galaxy s forum
http://galaxy.anddo.net/phpBB3/viewtopic.php?f=2&t=101&sid=560d97818f7435bd20ebc4391ea32ffc
Talonの最新版ソースを元にSC-02B用に手を加えたものです。
odinで焼き終わったあと再起動が2~3度繰り返され、EXT4へのコンバートが始まると思います。
また専用アプリもT101シリーズで動作するように変更してあります。(こちらはカーネルを焼けば自動的にインストールされます)
Superuser.apkはマーケットよりダウンロードしてください。
Superuserをインストールしたあとbusyboxなども入れるなら入れてください。
その後再起動で、zram反映されます。
その他は試行錯誤してみてください。
ソースは
https://github.com/kyapa/linux_gt-i9000-gb
にあります。
the last url is the source!
that's the one I knew I've a build for LC4 stock with that source, but never check the ram size.
maybe something similar on devil kernel which use all camera memory to reach bigger ram
I've plan to build semaphore, mackay & devil kernel for sc-02b...
semaphore already done & works, will post it later
didhiy said:
that's the one I knew I've a build for LC4 stock with that source, but never check the ram size.
maybe something similar on devil kernel which use all camera memory to reach bigger ram
I've plan to build semaphore, mackay & devil kernel for sc-02b...
semaphore already done & works, will post it later
Click to expand...
Click to collapse
we just ready to test and use next ones too!!thanks
didhiy said:
that's the one I knew I've a build for LC4 stock with that source, but never check the ram size.
maybe something similar on devil kernel which use all camera memory to reach bigger ram
I've plan to build semaphore, mackay & devil kernel for sc-02b...
semaphore already done & works, will post it later
Click to expand...
Click to collapse
damn. ur making another miracle bro. thank u. will be glad to see whats new.
u combine them. now thats what ive been waiting for.
Sent from my GT-I9000 using Tapatalk 2
@didhiy
can u please add the gingerbread phone apk contacts and messaging apk to this jellybean rom it was great or could u pls give some guidance how to do it thanks
how to have that 408 RAM?.how to swap?.can anyone help me?
here is semaphore kernel for sc-02b
http://dl.dropbox.com/u/820341/Semaphore_JB_2.9.5.zip
note: don't report any bugs to semaphore thread!!!
this is unofficial build, if something goes wrong or some feature didn't works, it might be my fault...

[KERNEL][5.1.1/6.0.0][GCC 5.3] Omni kernel (06/03/2016)

Overview: ​
This is a custom kernel based on Omni sources for our legendary i9000. This is only for 5.1.1/6.0.1 roms and no other version of android will be suppported
It works on any Omni based 5.1.1/6.0.1 rom.
>The zip you will download is flashable via recovery.
>> Use devil kernel manager or NStools to edit the kernel settings.
Features : ​- Multiple CPU governors (lulzactive, smartassV2, wheatley, lagfree, ondemandX)
- Tweaked smartassV2
- BFQ, Zen, VR & SIOPLUS I/O schedulers added
- Tweaked VR
- New TCP algorithms (westwood is default)
- Bigmem, up to 430mb
- CMA (MM only for now)
- Kernel compressed with XZ
- Compressed initramfs
- Dynamic page writeback
- Dynamic Fsync
- Custom ARM & INT voltages
- Voltages fixed for more stable OC
- Selectable GPU OC (not working properly for now)
- Fast charge
- BLX
- Live OC
- FULL O3 optimisations
- Call volume hack
- Touchwake
- BLN
- Zram
- Swap / Zram optimisations
- LMK tweaks
- SLQB memory allocator
- NEON optimized crypto routines
- Voodoo color
- SquashFS support (module)
- EXfat support (module)
- 720p patched bigmem libs
- Built from the latest Omni source
- Built using custom Cortex-A8 optimized UBERTC 5.3 toolchain of @Cl3Kener
Todo:​- Backport more things from higher linux versions and fix remaining conflicts ...
- Fix GPU OC ... Well we have live OC, not worth the time i guess.
- Make CGROUP_TIMER_SLACK work
- GPU driver to DDK [email protected]
- Make a better (and more fancy) updater script
- Fixing the remaining issues [...]
What I wont do : ​- Enable TV out
- Upgrade linux version
- Add useless CPU governors or I/O schedulers
- make your phone as fast as a i9500
Please use it at your own risk! I am not responsible for any damage that may occur to your device.
Download :
Latest android 5.1.1 kernel :
Kernel_ION.zip MD5 : 2060f96fbffc98a1f2fae9108066b69a
http://www50.zippyshare.com/v/zVr8YvZ4/file.html
Latest android 6.0.1 kernel :
Kernel_CMAEXP.zip MD5 : 236f89a961b559c666a1c064aaccd728
http://www43.zippyshare.com/v/Yxm6WDuA/file.html
Old versions :
https://mega.nz/#F!3x5VTbiQ!87aMOGoDBuQZmiELhKlUkQ
Thanks:
@humberos
@DerTeufel1980
@kasper_h
@Alberto96
@Ezekeel
@xc-racer99, for his help on setting up my Github
@(°_o)
Anyone else who helped me
Source Code:
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries
Custom built UBERTC with A8 optimisations : https://bitbucket.org/Coldwindofnowhere/
XDA:DevDB Information
Omni kernel, Kernel for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99
Version Information
Status: Beta
Created 2015-10-02
Last Updated 2016-03-06
>If you like my work, hitting the thanks button won't hurt you<​
good luck
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
idCyber said:
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61937705
Gesendet von meinem SM-G900F mit Tapatalk
idCyber said:
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
If you can , that would be great if you test if on different 5.1.1 roms and tell me if it works or not
Coldwindofnowhere said:
If you can , that would be great if you test if on different 5.1.1 roms and tell me if it works or not
Click to expand...
Click to collapse
This kernel works with Code rom 5.1.1 the latest build and mostly everything work perfectly. However, to test this i ported it to my good old vibrant. The only issue is since Im guessing devil kernel manager doesnt support vibrant cant seem to change any values in devil. Thanks for building this kernel
falconscrest123 said:
This kernel works with Code rom 5.1.1 the latest build and mostly everything work perfectly. However, to test this i ported it to my good old vibrant. The only issue is since Im guessing devil kernel manager doesnt support vibrant cant seem to change any values in devil. Thanks for building this kernel
Click to expand...
Click to collapse
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
xc-racer99 said:
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
Click to expand...
Click to collapse
I didnt use the source code to do anything just replaced the boot image with that of vibrant and it seemed to boot up just fine and i could switch between smartass v2, and other addition. the only thing cant change the bigmem option over xl. It was just random since i have no clue how to build stuff.
falconscrest123 said:
I didnt use the source code to do anything just replaced the boot image with that of vibrant and it seemed to boot up just fine and i could switch between smartass v2, and other addition. the only thing cant change the bigmem option over xl. It was just random since i have no clue how to build stuff.
Click to expand...
Click to collapse
Ah, ok. I could be wrong, but I think if you replaced the boot.img with one from the Vibrant, then you're not even using the kernel from here. Weird that you still had the smartassv2 option...
If I'm wrong, someone please correct me
431mb ram possible??
xc-racer99 said:
Ah, ok. I could be wrong, but I think if you replaced the boot.img with one from the Vibrant, then you're not even using the kernel from here. Weird that you still had the smartassv2 option...
If I'm wrong, someone please correct me
Click to expand...
Click to collapse
Im not sure either because i have all govenors mentioned above while i can tweak everyone of them using kernel aditor apk and plus i can also toggle fast charge which wasnt present in omni rom for the vibrant. I have uploaded some screenshots and it is from code rom.
xc-racer99 said:
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
Click to expand...
Click to collapse
Sure, i'll set a github soon, but trust me there are only minimal changes to the origianl code (even if adding liveOC seems harder since i only got build errors xD).
Btw i won't build anything this week, i'm busy with exams.
Github is up !
Coldwindofnowhere said:
Could someone help me to setup my github please ? (PM me)
Click to expand...
Click to collapse
Check your PM, let me know if you need more help.
Hey.
I tested it on 5.0.2 . stuck on bootanimation. Better mention that its for 5.1.1 .
Can you add support or please tweak it for 5.0.2
Now iam using RR lp 5.0.2
I removed some apps. And it have the same apps like omni. Its works faster than ever. Working theme engine. Only removed music and added apollo.
Has anyone have a bug where when you call someone the speaker mode work fine but the audio stops working when you turn off speaker mode
I had no problem with original omni kernel any fix because this is an awesome kernel
falconscrest123 said:
Has anyone have a bug where when you call someone the speaker mode work fine but the audio stops working when you turn off speaker mode
I had no problem with original omni kernel any fix because this is an awesome kernel
Click to expand...
Click to collapse
That's weird, i haven't changed anything concerning the audio in the kernel. You're using it on a vibrant right ? This might be the problem. I'm gonna try to reproduce this bug on my i9000 and see ....
Edit: try this http://www42.zippyshare.com/v/aZ6XgBlE/file.html
DO NOT FLASH, IT DOESN'T WORK (except if you want to give me a log or if you're really curious)
Any feedback on the vibrant version ?
Coldwindofnowhere said:
Any feedback on the vibrant version ?
Click to expand...
Click to collapse
The kernel didnt even flash no errors nothing whenever i flashed via twrp it would instantaneously reboot to recovery. Thanks again for atleast trying to fix the issue.
Coldwindofnowhere said:
Any feedback on the vibrant version ?
Click to expand...
Click to collapse
Bro. Can you add fast charge and the governers in omni kernal 5.0.2. Please
Thanks

Kernel with exfat support and mtkcamera for Dirty Unicorns 6.0.1

Dirty Unicorns 6.0.1 is probably the best marshmallow rom for amami so far , although it has some problems: camera app cannot take pictures at 20.7mp, and exfat-formated sdcard is not supported.
So I made a kernel to fix these problems. You can flash with twrp or flashfire.
Kernel_Amami_AOSP_6_20160709.zip contains aosp kernel built with exfat-nofuse and some other features, as well as other executables or libraries needed to identify and mount exfat(vold , blkid etc.) This may work with other aosp 6.0.1 based roms, but I never tried by myself.
2016.06.18 : I ported some features from other kernels like M5 kernel. Features included:
1. Various cpufreq governors, hotplug drivers and i/o schedulers
2. KCAL color control by @savoca
3. Faux Sound Control V3
4. CPU/GPU OC & UV
5. Vibrator intensity control
6. Ultra-ksm
7. Kexec-hardboot
8. Dynamic Fsync 1.2
9. Mac80211 injection patch and HID patch for keyboard support
10. Sysfs interface to Enable / Disable CRC on the data blocks
11. Exfat and Paragon NTFS(UFSD)
12. Zram
13. Merge upstream patches up to 3.10.102
MtkCamera.zip contains camera app from Mediatek devices with lollipop. It can take 20.7mp photos(3936 x 5248) and has some useful features like visual effects and qrcode scanner.
Modified kernel source : https://github.com/KuronekoDungeon/android_kernel_sony_msm
Download : https://drive.google.com/folderview?id=0B-DoK6BdpB2fZEZ5eG5NcnhYNFU&usp=sharing
If you're interested, Myself5 is willing to release M5 for Amami, but needs a maintainer, since he doesn't have a Z1c anymore. Maybe you can work with him on M5 for AOSP...
levone1 said:
If you're interested, Myself5 is willing to release M5 for Amami, but needs a maintainer, since he doesn't have a Z1c anymore. Maybe you can work with him on M5 for AOSP...
Click to expand...
Click to collapse
Is he working on a 3.10.9x kernel ?
maz-1 said:
Is he working on a 3.10.9x kernel ?
Click to expand...
Click to collapse
This is from main thread latest version...
levone1 said:
This is from main thread latest version...
Click to expand...
Click to collapse
cool, I guess I will be a tester then.
maz-1 said:
cool, I guess I will be a tester then.
Click to expand...
Click to collapse
He did say that testers won't really help. Without a device of his own, he'll need a maintainer.
levone1 said:
He did say that testers won't really help. Without a device of his own, he'll need a maintainer.
Click to expand...
Click to collapse
Well, I mean I will build, test and submit fixes if possible. But I'm afraid I don't have the time and knowledge to take over all the maintenance. Any other volunteers?
maz-1 said:
Well, I mean I will build, test and submit fixes if possible. But I'm afraid I don't have the time and knowledge to take over all the maintenance. Any other volunteers?
Click to expand...
Click to collapse
maybe we can jointly maintain ?
CLINTZ9 said:
maybe we can jointly maintain ?
Click to expand...
Click to collapse
Sounds good.
maz-1 said:
Sounds good.
Click to expand...
Click to collapse
cool !
CLINTZ9 said:
cool !
Click to expand...
Click to collapse
I've already ported a bunch of features to aosp kernel, just check out the commit history.
What left to be done : GPU governors, A few hotplug drivers/cpufreq governors not ported(hotplug : alucard , mako , intelliplug , cpufreq : HYPER, OndemandPlus, Nightmare , ElementalX, maybe more) , some of these features need to be modifeid or abandoned.
maz-1 said:
I've already ported a bunch of features to aosp kernel, just check out the commit history.
What left to be done : GPU governors, A few hotplug drivers/cpufreq governors not ported(hotplug : alucard , mako , intelliplug , cpufreq : HYPER, OndemandPlus, Nightmare , ElementalX, maybe more) , some of these features need to be modifeid or abandoned.
Click to expand...
Click to collapse
Hi, I install this, work well, but camera still laggy . What do you think, how else you can improve the image processing? The picture was much too sharp ... but it's better than before.
And...you can also add in your kernel any functions like as KryptonianKernel or AdvancedKernel
John.D.. said:
Hi, I install this, work well, but camera still laggy . What do you think, how else you can improve the image processing? The picture was much too sharp ... but it's better than before.
And...you can also add in your kernel any functions like as KryptonianKernel or AdvancedKernel
Click to expand...
Click to collapse
Laggy camera is a driver issue, just wait until sony updates software binaries for amami.
Hmm, why you delete MTKCamera? You have another app for taking photo in 21mp?)
MTKCamera cannot use frontcam. I think @SpiritCroc will try to add 20.7mp option to SnapdragonCamera, so wait for a new release.
maz-1 said:
MTKCamera cannot use frontcam. I think @SpiritCroc will try to add 20.7mp option to SnapdragonCamera, so wait for a new release.
Click to expand...
Click to collapse
I already added it, will probably be in next weekly
maz-1 said:
I've already ported a bunch of features to aosp kernel, just check out the commit history.
What left to be done : GPU governors, A few hotplug drivers/cpufreq governors not ported(hotplug : alucard , mako , intelliplug , cpufreq : HYPER, OndemandPlus, Nightmare , ElementalX, maybe more) , some of these features need to be modifeid or abandoned.
Click to expand...
Click to collapse
check your whatsapp inbox
What's 'jhead exif fix' file in your Gdrive link?
levone1 said:
What's 'jhead exif fix' file in your Gdrive link?
Click to expand...
Click to collapse
libjhead with this patch :
https://gist.github.com/updateing/2b58ebd4a8c75780443f28f514e9bb39
Photos token by Android N may contain wrong exif infomation and cause app crash on marshmallow/lollipop.
need help - CPU GOVs and frequencies
Hi,
first of all thanks for the kernel! I'm just migrated from RR Lollipop to MM DU ROM (today to the build of 17. June). I have strange issues with the kernel.
I can not change the CPU govs. More critical: The minimum CPU frequency is shown to be 1.8 GHz. Whatever I try, I cannot get the values gov/freq to stick.
Always when I reopen an tuning app, the settings are reverted.
Root seems to work fine. Also tried to disable SE-linux via terminal ("setenforce 0"). The same.
(Combinations I tried: kernel audiutor, performance control, system tuner... also on DU (3. june) + kernel (5. june)
Can somebody help me out?
Who can permanently adjust the CPU settings on DU with/without this kernel?
Thanks in advance!

Categories

Resources