Database Users

[KERNEL][KK4][1/28/11] Corn Kernel v7.06 from Source (OC, BLN, Voodoo Sound, etc.)!

Update: New version 7.06 (UCKK4) from Samsung I897 source code.
UCKK4 kernel with Voodoo sound and color, BLN, 1200 mhz overclock, custom CwM 5, init.d, root, custom boot animation support, fully working nandroid, rfs/ext2/ext4 formatting, multiple tweak options and more!
No more Voodoo lagfix. Reformatting functions are contained in a new custom-modified CwM Recovery. Ext4, Ext2, and RFS formatting options are available for /system, /data, /dbdata, and /cache together and individually. Su / Superuser installation is available from within Recovery for un-rooted ROMs. Kernel tweaks are also available from within Recovery, as well as support for init.d scripts and sysctl.conf.
You can flash this over any supported partition scheme. Select OC, scaling governor, i/o scheduler, etc. in Recovery. Download BLN app from Market to control BLN, Voodoo Control app to adjust sound and color, and Voltage Control for under-volting (not recommended unless you know what you're doing). Please do not use Tegrak for this... the frequency table in this kernel is of a different design than that in Talon, Semaphore, etc.
--- IMPORTANT ---
Click to expand...
Click to collapse
Please consider this somewhat experimental. It was a major pain to track down and piece together the missing parts of the source code, and should be considered a work in progress. Version 6.03 (repackaged stock kernel) is still available and reliable.
You might want to back-up and remove any shell scripts you have in your /system/etc/init.d folder until you have flashed this and can verify that they
are compatible and/or needed.
NEW - NEW - NEW: Version 7.0A is for those who have experienced reboots or want a basically stock kernel with BLN, Voodoo Sound, SIO and SmartassV2. No overclocking, Voodoo Color, TinyRCU, advanced ext4 driver, or other code modifications... just straight Samsung code. If you want overclocking, use Tegrak loadable module (paid version?) to provide that.
Please use this guide for reporting problems
Change Log
Click to expand...
Click to collapse
Version 7.06
- Added Low Memory Killer and SD Card Read-ahead selection in Recovery
- Increased scheduler latency values slightly for better (?) stability
- Simplified SCSI and Procfs drivers for better (?) stability
- Restored MMC driver to 100% stock code. Previous modified version suspected as cause of reboot problem for some users.
- General code clean-up and debugging
Version 7.05
- Fixed Wifi (again)
Version 7.04
- Compiled with Linaro 12-2011 toolchain (optimizations make kernel even faster)
- Updated Tiny RCU
- Fixed IpSec key retention
- Fixed Superuser permissions to satisfy Tibu
Version 7.03
- Fixed hinkey RFS from version 7.02
- Back to Tiny RCU
- Added full L2TP / IpSec network support
- Overclock is now off by default... enable in Recovery
Version 7.02
- Added Voodoo Color
- Reverted to stock tree rcu from tiny rcu
- Reduced scheduler latency and other tweaks
Version 7.01
- Built from UCKK4 kernel source.
- Added Voodoo sound, BLN, and 1200 mhz overclock.
- Added several scaling governors, including interactive and smartassV2
- Switched to Tiny RCU and updated ext4 driver code
- Wifi working
Version 7.0A
- Built from unmodified UCKK4 kernel source.
- Added Voodoo sound and BLN.
- Added SmartassV2 scaling governor and SIO i/o scheduler.
Download Links
Click to expand...
Click to collapse
7.06 (UCKK4 from Source Code)
> Odin flashable version HERE
> CWM flashable version HERE
(CWM flash version has init.d scripts to zip-align apps and "vacuum" your
databases once a week. First boot might take a bit longer than usual.)
===================================
7.0A (UCKK4 from Source Code - Baseline version)
Try this if the other 7.0x versions cause problems
> Odin flashable version HERE
> CWM flashable version HERE
===================================
7.05 (UCKK4 from Source Code)
> Odin flashable version HERE
> CWM flashable version HERE
7.04 (UCKK4 from Source Code)
-- Pulled --
7.03 (UCKK4 from Source Code)
> Odin flashable version HERE
> CWM flashable version HERE
7.02 (UCKK4 from Source Code)
-- Pulled --
7.01 (UCKK4 from Source Code)
> Odin flashable version HERE
> CWM flashable version HERE
Useful Reference Material
Click to expand...
Click to collapse
Compiling the UCKK4 source
Android Optimization Tips - i9000 by pikachu01
Captivate General Info and Links
SGS General Info and Links
How to isolate and fix battery drain
Previous Version (repackaged stock kernel)
Click to expand...
Click to collapse
6.03 (UCKK4)
> Odin flashable version HERE or HERE
> CWM flashable version HERE or HERE
Previous Version (Voodoo-lagfix)
Click to expand...
Click to collapse
3.07 - With Superuser Installer (provides root):
> Odin flashable version HERE
> CWM flashable version HERE
(CWM version has sample sysctl.conf and init.d scripts.)
-----------------------------------------------------------
3.07 Without Superuser Installer (if you are already rooted):
> Odin flashable version HERE
> CWM flashable version HERE
(CWM version has sample sysctl.conf and init.d scripts.)
Acknowledgments
Click to expand...
Click to collapse
Thanks to existz (Talon), xcaliburinhand (GB I9000), pikachu01 (Tweaks), mialwe (Midnight I9000), supercurio (Voodoo), glitch (Glitch) for code samples and ideas

You already have a thread open containing this.
Wandering why the need to open a new one ?
Anyways good job.

Please help me!
Can't enter Download Mode, Recovery Mode and Stuck at AT&T Logo. AT&T Logo after insert battery and can't do anything else!
Help me

hiepgia said:
Please help me!
Can't enter Download Mode, Recovery Mode and Stuck at AT&T Logo. AT&T Logo after insert battery and can't do anything else!
Help me
Click to expand...
Click to collapse
Have you flashed the version that was updated about 20 minutes ago? Earlier version was broken.

So is this one working with no bootloops?

mtcarey said:
Have you flashed the version that was updated about 20 minutes ago? Earlier version was broken.
Click to expand...
Click to collapse
You should mention that this kernel will not work with ki2 roms.....
so others dont go flashing it and getting bootloops.
---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------
Kyuta Syuko said:
So is this one working with no bootloops?
Click to expand...
Click to collapse
So i heard from one of my testers, only for ki1 tho

but why i can't enter download mode?

hiepgia said:
but why i can't enter download mode?
Click to expand...
Click to collapse
Start Odin, pull the battery, reinsert it, hold vol up/vol down together (don't touch power button) and plug in your usb cable. Should enter download mode.

hiepgia said:
but why i can't enter download mode?
Click to expand...
Click to collapse
i apply unbrickable mod and give my phone back
//It's ok! Now downloading... new firmware

hiepgia said:
but why i can't enter download mode?
Click to expand...
Click to collapse
You should be able to.
If you have gb bootloaders then;
remove the battery
put it back
plug in the usb cable while holding both volume buttons.

LOSTLOGIC89 said:
So i heard from one of my testers, only for ki1 tho
Click to expand...
Click to collapse
Ah sucks I'm working on a KI2 kernel was wanting to gut this one and see what he changed.

Kyuta Syuko said:
Ah sucks I'm working on a KI2 kernel was wanting to gut this one and see what he changed.
Click to expand...
Click to collapse
You should, you might make it work for ki2.
Good luck

Kyuta Syuko said:
Ah sucks I'm working on a KI2 kernel was wanting to gut this one and see what he changed.
Click to expand...
Click to collapse
There is no reason in general that it shouldn't work with KI2 ROM.... I'm going to install Fasty IIIV1.1 now and try it out.

LOSTLOGIC89 said:
You should, you might make it work for ki2.
Good luck
Click to expand...
Click to collapse
Thanks. Like I said in the other thread I'm currently compiling Voodoo from scratch and it's taking a LONG time... Working on my dated laptop. 1.6Ghz Celeron M 380 w/1G DDR2... Hopefully with this job I'll be able to get something with at least a Dual Core. A Quad Core would be nice though.

Kyuta Syuko said:
Thanks. Like I said in the other thread I'm currently compiling Voodoo from scratch and it's taking a LONG time... Working on my dated laptop. 1.6Ghz Celeron M 380 w/1G DDR2... Hopefully with this job I'll be able to get something with at least a Dual Core. A Quad Core would be nice though.
Click to expand...
Click to collapse
Good luck!

mtcarey said:
There is no reason in general that it shouldn't work with KI2 ROM.... I'm going to install Fasty IIIV1.1 now and try it out.
Click to expand...
Click to collapse
Please report back, thanks
Kyuta Syuko said:
Thanks. Like I said in the other thread I'm currently compiling Voodoo from scratch and it's taking a LONG time... Working on my dated laptop. 1.6Ghz Celeron M 380 w/1G DDR2... Hopefully with this job I'll be able to get something with at least a Dual Core. A Quad Core would be nice though.
Click to expand...
Click to collapse
Good luck and i know it sucks with such a laptop

I suppose I should also state that I'm trying to get ALL of Voodoo to work and not just the EXT4... Something I'm sure quite a few would like to see. Though I don't know much about Voodoo so we'll see how far I can get...

msprag13 said:
Tried the newer kernel and it bootlooped again. This time though I did not have to reflash pinnacle, just Odin Boog kh3 kernel and reboot and all was fine
Are the files in /voodoo/log helpful for this? There are a lot of log files. One for each bootloop attempt.
Side note: where does the phone get time stamps from during bootup as the time stamps on the log files are incorrect.
Click to expand...
Click to collapse
Moved this here from old thread
Sent from my SAMSUNG-SGH-I897 using xda premium

Kyuta Syuko said:
I suppose I should also state that I'm trying to get ALL of Voodoo to work and not just the EXT4... Something I'm sure quite a few would like to see. Though I don't know much about Voodoo so we'll see how far I can get...
Click to expand...
Click to collapse
I wondered about that... the ext4 part of Voodoo is just a bunch of shell scripts. I couldn't figure-out what you were compiling!

msprag13 said:
Moved this here from old thread
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Can you attach the (zipped) log files or send them to me? Thanks.

RR 3.0.9 ROM: link to a MALI Patch (fix memory leak + new kernels)

As an quite user here in the forum, it is not allowed for me to share things in the development section.
Just want share a link, which patches RR 3.0.9 with the latest MALI drivers. Therefore for all people which can not wait for an update of rr 3.0.9 it is quite fine: memory leak fixed (had been very annoying because my phone got frozen after 3 days without reboot) and enables you to use the latest dorimax kernels >7.0 (fine battery + speed)
Found the patch in an german forum:
http://www.android-hilfe.de/custom-...ma-ota-resurrection-remix-jb-3-0-9-a-162.html
the patch itself can be downloaded under the link (thank the user rush85 in that other forum):
https://docs.google.com/open?id=0BzvcR7D2Mt5KQ1JLMXJDQmFzNkk
1) I flashed over rr 3.0.9.
2) wiped dalvic. wiped extweakts profiles in cwm
3) flashed dorimax 7.3 (mali)
4) to be sure, wiped again dalvic & extweaks profile again
5) reboot
and ready to go!
--> Much faster + reliable (memory fixed) + nice powersave
http://forum.xda-developers.com/images/smilies/good.gif

a personal question & comment
by the way a question:
does anybody knows how to directly get access to the developer thread?
I have not much time to post. But I'm a heavy linux user on my 3 desktop PCs since over 6 years. Know much about linux kernel tweaks, debugging and android.
But also one critic to S2 users:
I've followed the Galaxy ACE threads for the last year and must say, that there the "developer threads" are much cleaner! No noop with "how can I flash this" or "where do I find this and that" is disturbing the replies of testing by the community for clean feedback & input for the developer(s).
- Sorry for that, but the people should just post relevant things there to make it easy for the serious testers and developers.

So after this patch ,can i flash parandroid 2.21 which ri8 now does not support dual booting in siyah ???

no. that patch is only for the ressurection Rom in Version 3.0.9.
it has nothing do with other ROMs or versions. you would break it.
I don't know who actually developed that patch. but it is working fine. next RR ROM after 3.0.9 will nevertheless have the Mali driver patches included, as the sources will be updated.
so in summary: just for the impatient waiting users of RR ROM.
Sent from my GT-P6810 using xda app-developers app

and just one thing I forgot in the first post: run also fix permissions in cwm after flashing the patch and kernel.
whilst waiting for a new RR release,
I'm now very happy with the performance and battery life of my s2! just bought ot 10 days ago to substitute my good old samsung ace 1.

Some hints for optimizing your s2
Just for because I want to know the experience of other people:
Did anybody tried that mali patch?
I'm running it since the first post here. My tips for an excellent battery life with good performance:
Remember I'm using the combination of RR 3.0.9 + mali patches + Dorimanx Kernel 7.3 (need the mali patches)
Make use of the extweaks settings to undervolt GPU (800 mV is ok for mine at low frequencies) and enable some sleeper mechanisms. I undervolt the CPU with the app cputuner (for all frequencies -50 mV; otherwise unstable for me). Because I'm a lazy person I automatically adjust the brightness via lightsensors (Velis Auto brightness app works fine; but also eats some small cpu time).
My extweak profile:
secondcore=hotplug
cpustepcount=15
scaling_max_freq=1200000
scaling_min_freq=200000
smooth_level0=14
scaling_governor=HYPER
load_l1=25
load_h0=42
min_rq=2
load_rq=20
rate=100
freq_min=700000
GENTLE_FAIR_SLEEPERS=on
ARCH_POWER=on
cpu_undervolting=+0
enable_mask=3
sched_mc_power_savings=0
busfreq_up_threshold=25
scaling_max_suspend_freq=600000
scaling_min_suspend_freq=200000
deep_sleep=ondemand
standby_freq=200000
mali_touch_boost_level=2
GPUFREQ1=62
GPUFREQ2=160
GPUFREQ3=200
GPUFREQ4=267
GPUVOLT1=800
GPUVOLT2=900
GPUVOLT3=950
GPUVOLT4=1000
GPUTHRESHOLD1UP=60
GPUTHRESHOLD2DOWN=50
GPUTHRESHOLD2UP=80
GPUTHRESHOLD3DOWN=75
GPUTHRESHOLD3UP=85
GPUTHRESHOLD4DOWN=80
mov_hysti=4
min_bl=40
min_gamma=1
max_gamma=24
power_reduce=on
user_mode=on
user_cb=127
user_cr=127
user_gamma_adjust=0
pwm_val=50
tsp_touch_freq=600000
tsp_slide2wake=off
mdnie_shortcut_enabled=off
negative_tweak=1
TOUCHSCREEN1=50
TOUCHSCREEN2=40
TOUCHSCREEN3=12
TOUCHSCREEN4=53
TOUCHSCREEN5=38
TOUCHSCREEN6=44
soundgasm_hp=0
sound_volume1=0
sound_volume2=0
sound_volume3=0
gesture_tweak=off
enabled=off
bln_switch=2
enabled_charging=off
notification_timeout=600000
bln_reset_notification=0
bln_charging_notification=0
bln_check_battery=6
led_timeout=off
tsp_flash_timeout=off
led_fadeout=off
touchkey_brightness=2750
logger=off
adb_mode=0
bootmenu_enabled=1
supplicant_scan_interval=360
zramtweaks=4
gpsregion=No_GPS_Zone_changes
scheduler=sio
usb_mode=mass_storage-adb
default_stats=on
chargecurrent=2
install_root=on
cortexbrain_background_process=1
cortexbrain_auto_tweak_brightness=off
cortexbrain_auto_tweak_wifi=off
android_logger=auto
cortexbrain_firewall=off
cortexbrain_tcp=on
cortexbrain_cpu=on
cortexbrain_memory=on
cortexbrain_battery=on
cortexbrain_extra_battery=on
cortexbrain_system=on
cortexbrain_kernel_tweaks=on
cortexbrain_io=on
For improving deep sleep times:
[A] Additionally I found out that it is really wothfull to get a baseband matching RIL modem configuration to get over 95% deep sleep. A good tool to check/correct this is:
"GetRIL"
I deactivated also "fast dormancy" (I'm on O2 in germany) with the App:
"Fast Dormancy Toggle i9300"
[A] and really did the trick to get a high amount of deep sleep for me. Without I had just approx. 75% and now up to 98% in G2 mode.
Playstore Issues due dpi change:
If you get problems with app compability in playstore after you changed the dpi in build.prop, I recommend to search for the "multi dpi playstore" replacement here in XDA.
Last thing which is interessting: no use to lower the CPU >200 MHz. Why with a clockfrequency of 200 MHz the equinox CPU is at the best rate of calculation speed / powerconsumption. Therefore lower frequencies: lower energy but more time to finish tasks --> worse than 200 MHz.
An really good and technical/scientific investigation with hardware measurements of voltages and power consumptions is given in a german forum FACTS and MEASSUREMENTS agains wild speculations:
http://www.android-hilfe.de/samsung...80670-info-akkuverbraucher-des-galaxy-s2.html

Nice post, I will try this out and give some feedback. I'm still on rr 3.0.8 and dormanx 5.82 but I want to update
Sent from my GT-I9100 using Tapatalk 2

GNUDroid said:
As an quite user here in the forum, it is not allowed for me to share things in the development section.
Just want share a link, which patches RR 3.0.9 with the latest MALI drivers. Therefore for all people which can not wait for an update of rr 3.0.9 it is quite fine: memory leak fixed (had been very annoying because my phone got frozen after 3 days without reboot) and enables you to use the latest dorimax kernels >7.0 (fine battery + speed)
Found the patch in an german forum:
http://www.android-hilfe.de/custom-...ma-ota-resurrection-remix-jb-3-0-9-a-162.html
the patch itself can be downloaded under the link (thank the user rush85 in that other forum):
https://docs.google.com/open?id=0BzvcR7D2Mt5KQ1JLMXJDQmFzNkk
1) I flashed over rr 3.0.9.
2) wiped dalvic. wiped extweakts profiles in cwm
3) flashed dorimax 7.3 (mali)
4) to be sure, wiped again dalvic & extweaks profile again
5) reboot
and ready to go!
--> Much faster + reliable (memory fixed) + nice powersave
http://forum.xda-developers.com/images/smilies/good.gif
Click to expand...
Click to collapse
I see this link but it isnt a flashable zip! How can i use this?
Thx and sorry for my poor english!

Hitman_911 said:
I see this link but it isnt a flashable zip! How can i use this?
Thx and sorry for my poor english!
Click to expand...
Click to collapse
click on file then download

I download the zip file. But I don´t know it is the cwm flashable or flash via Odin?

Unexist6969 said:
click on file then download
Click to expand...
Click to collapse
I only see multiple files but no zip file.
Can you send me in email?

psychotic14 said:
I download the zip file. But I don´t know it is the cwm flashable or flash via Odin?
Click to expand...
Click to collapse
If it's a zip file then flash through Cwm
---------- Post added at 10:17 AM ---------- Previous post was at 10:05 AM ----------
Hitman_911 said:
I only see multiple files but no zip file.
Can you send me in email?
Click to expand...
Click to collapse
What are you browsing with? I had the same problem, but it is probably the browsers you are using. Are you using stock android browser? I used opera mini browser, and the page loads quite differently and gives you an option to download the zip file.

hi everybody. sorry hat i did not replied for a long time.
yes hat mali patch Form a Google drive must be downloaded by click in 'Datei' and then hit something linke download AS ZIP. unfortunately that forum is in German.... also the nice poeweconsumption measurements I posted a link for. maybe someone has the time to make it a viable in English for everybody.
you can flash the malipatch zip over a installed rr 3.0.9 by cwm. don't miss the wiping steps and fix permissions.
At the Moment I am on RR 3.0.9 + mal patch + dorimanx 7.4. a perfect combination for me.
by the way. I always activate in the developer options the 'disable hw overlay'.
feels smoother for me.
so let us hope that the next RR release will have the Mali patches inside. .... but until that release I already enjoy this combination. - until now no reboot had been necessary due to the old memory leak seems to be gone.
Sent from my GT-P6810 using xda app-developers app

Nice job

Nick ZA said:
If it's a zip file then flash through Cwm
---------- Post added at 10:17 AM ---------- Previous post was at 10:05 AM ----------
What are you browsing with? I had the same problem, but it is probably the browsers you are using. Are you using stock android browser? I used opera mini browser, and the page loads quite differently and gives you an option to download the zip file.
Click to expand...
Click to collapse
I try stock browser, firefox and now opera mini but same result.

GNUDroid said:
by the way a question:
does anybody knows how to directly get access to the developer thread?
I have not much time to post. But I'm a heavy linux user on my 3 desktop PCs since over 6 years. Know much about linux kernel tweaks, debugging and android.
But also one critic to S2 users:
I've followed the Galaxy ACE threads for the last year and must say, that there the "developer threads" are much cleaner! No noop with "how can I flash this" or "where do I find this and that" is disturbing the replies of testing by the community for clean feedback & input for the developer(s).
- Sorry for that, but the people should just post relevant things there to make it easy for the serious testers and developers.
Click to expand...
Click to collapse
I similarly have much to share at times, but I guess you just have to post to post. It might explain why there are lots of irrelevant comments.
About your critic to S2 users, my guess is that the S2 is a lot more popular and hence you would have a lot more people asking questions. The upside is you have more developers making awesome stuff on it.
OH and about the patch, will try that later.

Again: How to download
Hitman_911 said:
I try stock browser, firefox and now opera mini but same result.
Click to expand...
Click to collapse
Call me old fashioned, but with things like firmware, roms and updates (not inly for a mobile, but other devices) I don't trust wireless. I always download serious things by desktop pc. There the download is quite fine with any browser. I used firefox. there is a screenshot attached.
But maybe this patch for 3.0.9 is not necessary, as we may get a new RR version this week. ? Let us hope the developer has some time after the the milestone release of the AOSP team is ready.

nice work!
can't wait for the next RR update

GNUDroid said:
Call me old fashioned, but with things like firmware, roms and updates (not inly for a mobile, but other devices) I don't trust wireless. I always download serious things by desktop pc. There the download is quite fine with any browser. I used firefox. there is a screenshot attached.
But maybe this patch for 3.0.9 is not necessary, as we may get a new RR version this week. ? Let us hope the developer has some time after the the milestone release of the AOSP team is ready.
Click to expand...
Click to collapse
Finaly success! Downloaded it! Install the google drive app and done!

[Kernel 3.0.xx][ROM]CM 10.1[4.2.2]for GT-P1000[GSM/N/L/C]

Some good news for the good old G-Tab! Cdesai, koxudaxi, humberos have finished debugging the 3. kernel for now. I've made one new build yet (it was posted from OsitKP, because i've not enough posts for yet). This build is here. Help our great developers to enhance the kernel and test it.
Some details to the build: build number: 4.2.2 JDQ39E, kernel: 3.0.70.
All Thanks to alroger for his tutorials, to cdesai, humberos , angel666, koxudaxi, pawitp, jt1134, sbradymobile etc.
Sorry for my bad english.

First results on testing the kernel:
1. Charge works only when Tab is off
2. Some Advanced settings don't work
3. No USB connection to PC
4. Wi-Fi works
5. BT works partially, just like with 2.x kernel
For those who wants to try the new kernel for GT-P1000 I've attached two CWM zips with 3.x and 2.x (for rollback) kernels

OsitKP said:
First results on testing the kernel:
1. Charge works only when Tab is off
2. Some Advanced settings don't work
3. No USB connection to PC
4. Wi-Fi works
5. BT ....
For those who wants to try the new kernel for GT-P1000 I've attached two CWM zips with 3.x and 2.x (for rollback) kernels
Click to expand...
Click to collapse
6. Sound is ok, also with headphones, bt headphones not tested.
7. Voodoo works not?
8. Monitor colors are different than before
9. Power consumption seems better then before:good:
10. Some users report that vibration works not (with me also)

Are you saying that tab doesn't charge when on?
Sent from my GT-P1000 using xda app-developers app

adi6262 said:
Are you saying that tab doesn't charge when on?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
It seems like the tab consumed to much power if the tab is on... I'm not sure, but i think galaxy s has or had similar problem... Probably the new kernel from alroger ( 3.0.74) fix it.
Alroger has reported that external sd is not mounted and tab has no usb yet. I have these bugs too..

Alroger has made its own build yet with kernel 3.0.74 and humberos fixed furthermore the bugs.

storm31 said:
Alroger has made its own build yet with kernel 3.0.74 and humberos fixed furthermore the bugs.
Click to expand...
Click to collapse
For my P1000 this kernel is much better:
Charge works now
Tab connects to PC by USB
It seems to me that tab now isn't as hot as yesterday with 3.0.70 kernel.
Emmc is mounted, but once after some gaming I saw it unmounted.

OsitKP said:
For my P1000 this kernel is much better:
Charge works now
Tab connects to PC by USB
It seems to me that tab now isn't as hot as yesterday with 3.0.70 kernel.
Emmc is mounted, but once after some gaming I saw it unmounted.
Click to expand...
Click to collapse
Humberto has commited now 3.0.75 and fixed yesterday vabrations. I try to compile today later the kernel

3.0.75 kernel for P1000
storm31 has compiled new kernel - 3.0.75.
Have not tested too much, but charge and emmc mounting works. As well as connection to PC. Youcan try attached recovery zip for P1000.
Warning!
The kernel contains broken recovery. To rollback you have to flash previous kernel via Heimdall or make a full restock.

Help meee
OsitKP said:
storm31 has compiled new kernel - 3.0.75.
Have not tested too much, but charge and emmc mounting works. As well as connection to PC. Youcan try attached recovery zip for P1000.
Warning!
The kernel contains broken recovery. To rollback you have to flash previous kernel via Heimdall or make a full restock.
Click to expand...
Click to collapse
hai @OsitKP,, i have already installed your kernel 3.0.75 but why the emmc cannot mounting?? can you help me?? can you give step for installation in my GT-P1000 europe

agus.suginantra said:
hai @OsitKP,, i have already installed your kernel 3.0.75 but why the emmc cannot mounting?? can you help me?? can you give step for installation in my GT-P1000 europe
Click to expand...
Click to collapse
I made no special steps for emmc mounting. The only thing I can assume is I've flashed last ROM (with 2.6.35 kernel) after restock. While last kernel was installed from CWM. By the way last ROM i use was compiled by storm31 who as well compiled 3.0.75 kernel (it's not mine!).

agus.suginantra said:
hai @OsitKP,, i have already installed your kernel 3.0.75 but why the emmc cannot mounting?? can you help me?? can you give step for installation in my GT-P1000 europe
Click to expand...
Click to collapse
My emmc cannot mount also. OsitKP has one build with same old components, i have one mit newer components. It is possible that they have one or more bugs. We must wait for humberos, he is the "big man" by kernel developing. I would like to mention that the kernel 3.0.xx is very experimental. The next bad thing is that recovery seems to be brocken

3.0.75 kernel compiled by storm31
CWM zip, now with working recovery.
As for emmc it is my fault (I meant usial work. But when connected to PC it's not mounted).
Vibration and display colors are not fixed yet.
And charge is very weak.

new p1 kernel:
Thanks a lot to humberos!

kmesg and kmsg for humberos:

storm31 said:
kmesg and kmsg for humberos:
Click to expand...
Click to collapse
This files are incomplete. T_T
Please, can you try to get them again.
Thanks!

humberos said:
This files are incomplete. T_T
Please, can you try to get them again.
Thanks!
Click to expand...
Click to collapse
Sorry, I noticed it too late.

dmesg:

kmsg:
i'm not sure if it complete, but it was very hard to copy the flying text from the shell to a text file
I unfortunately could not create a text file.
Sorry if it was to long
Bye

storm31 said:
new p1 kernel:
Thanks a lot to humberos!
Click to expand...
Click to collapse
CWM version of the p1 kernel.

lollipop/kitkat versions of Low Lying Fruit Kernel (LLFK) for N915T

(6/30/15) Newest LLFK for T-Mobile Note EDGE N915T Lollipop.
Now has TCP congestion control options with default TCP Westwood
This version is flashable using TWRP.
Features:
SELinux=Permissive option
init.d support
adbd insecure
TCP congestion controls: TCP options include Westwood, cubic, reno among others: default is Westwood
Modifications that need to be made when using LLFK kernel
1)In build.prop set
ro.securestorage.support=false
2)For those that use AllShare Cast you will need to do two things.
First, add the following line at the end of build.prop
wlan.wfd.hdcp=disable
second, you need to have the Xposed module Wanum Xposed installed. In Wanum select "security hacks" then check box of Fake system status
Download link:
https://www.dropbox.com/s/6bg9l8qqcmmh83x/llfk_permissive_initd_adbd_tcp_lpop.zip?dl=0
Check below for other information that might come in handy and good luck!
(06/11/15)New Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (lollipop)
I've added adb insecure to kernel. This gives you root access to modify /system on phone from a pc
Features:
SELinux = Permissive option
init.d support
adb insecure
download link
https://www.dropbox.com/s/kr7xb22449p497w/llfk_permissive_initd_adbd_lpop.zip?dl=0
(06/10/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T)
Two new flashable kernels. One for Lollipop the other for Kitkat.
Lollipop: This new version has init.d support so, for example, you can write scripts that run on boot up. (more below).
Features:
SELinux = Permissive option
init.d support
https://www.dropbox.com/s/k8w423ecoj1covs/llfk_permissive_initd_lpop.zip?dl=0
Kitkat:This version now has TCP congestion control options available (e.g. Westwood)
Features:
SELinux = Permissive option
init.d support
adb insecure (allows you to have r/w access to phone's /system from you pc)
TCP congestion control options
Thanks to JT man for testing
https://www.dropbox.com/s/jbifzsuztb73wpg/llfk_permissive_initd_adbd_tcp_kkat.zip?dl=0
Example of init.d script to automatically set SELinux=permissive given here
https://forums.oneplus.net/threads/how-to-selinux-permissive.314120/
couple notes on how-to-selinux-permissive
1)You only need have permissions of /sys/fs/selinux/enforce set to 644
2)Make sure permission of init.d script is 775
One more thing, knox based warnings can be silenced using wanum.
(05/27/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T) running Lollipop.
For those that miss having SELinux=Permissive on their T-mobile Note Edge running lollipop, here is a kernel
that supports this setting. The kernel is based on the Tmobile Note Edge Lollipop source code. The only thing that was
changed was a setting in the kernel's Makefile to allow the user to choose whether they want to have SELinux=Permissive
as described for the previous Kitkat version of LLFK below.
NOTE: This time around, the kernel is packaged as a zip file than can be directly flashed in recovery.
But before I go any further I need to give credit to @TEKHD for providing a zipped
version of the T-Mobile kernel I could modify and, in addition, for testing it.
Please buy him a well deserved cup of coffee!
Once you have flashed the kernel and rebooted you are ready to set SELinux=permissive by opening a terminal and typing
su
and
setenforce 0
To check it worked, go to settings > About device and you should see, under SE for Android status, that it is now set to Permissive.
An alternative way to change the setting with this kernel is to use the apk SeLinuxModeChanger. Unfortunately this apk is no longer
available at the play store but you can still download it from the F-Droid site.
https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
A third option would be to set up an init.d script if your rom permits it.
I must admit, at the time of this writing, I'm still on KitKat and have yet to try this on my phone. I'll be checking out lollipop soon
but till then, let me know if/how it works. If successful I'll start adding a few more low lying fruit I've picked!
Remember to do a full nandroid back-up before trying this so your phone can return to its original state before trying llfk if needed.
The usual disclaimer applies!
Good Luck!
lollipop LLFK download link:
WAIT! Only one person has tried this version and although it worked for him, I still consider it beta at best. You have been warned!
WAIT! WAIT! One more thing: You need to do the following otherwise you may experience problems with WIFI:
Download the apk BuildProp Editor and use it to set
ro.securestorage.support=false (thanks @TEKHD for checking this)
WAIT! WAIT! WAIT! May be an issue with private mode not working (see http://forum.xda-developers.com/showpost.php?p=61033627&postcount=109 ). I did not have this problem on kitkit. I am unable to test till next week so if someone can check it out that would be great.
http://www.4shared.com/zip/Z8g1u3FHba/llfk_permissive_lpop.html
dropbox link
https://www.dropbox.com/s/ud84t2fc3n9sqdg/llfk_permissive_lpop.zip?dl=0
Below only applies to the KitKat version.
(04/07/15) Update:
Well, I had a little time and decided to add a feature to LLFK. So for now it has the following three capabilities.
1)Allows you to set SELinux = Permissive
2)adb insecure
3)init.d support
Here is the link for the tar file. (follow same instructions given below to install via ODIN):
http://www.4shared.com/archive/2PepSJcPce/llfk_permissive_initd_adbtar.html
Let me know if/how it works...
New features:
The kernel is now adb insecure. This was accomplished by replacing the adbd file in ramdisk with one due to @freeza. Big thanks to him (as in buy him a cup of coffee!) for giving me permission to use it. With adb insecure you can now remount system as r/w from your pc which can come in handy at times.
The kernel has init.d support (Allows you to run scripts from boot) by modifying the ramdisk using the instructions in STEP 1 (Making kernel ready) of the following post
http://forum.xda-developers.com/showthread.php?t=2287540
So this part is done for LLFK
For it to work, the user still needs to make some minor modifications (add a file and create a directory) in their rom. To do this, please follow all 4 parts of STEP 2 (Making Rom Ready) in the same post.
Once you have completed STEP 2 you are ready to try some scripts.
You can search the Internet for init.d scripts to try.
For example there are some init.d scripts in the later half of the following post to give you an idea.
http://en.miui.com/thread-5685-1-1.html
If folks can experiment to see what scripts work I will make a list and post it here.
Seems to work OK on Hyperdrive and Lab Rats (let me know otherwise).
CAVEAT: When testing whether init.d support was successfully implemented I had tried some scripts (like echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb; ) that should have modified some kernel settings at boot up. But as it turns out there are a set of scripts that run after boot up that supersede these settings. These scripts are in the file /etc/init.qcom.post_boot.sh. (some other neat stuff to play around with in there!) If you want those scripts to not take effect you can simply comment them out and then your init.d scripts will work.
The usual disclaimer and Good Luck
Original post 1/30/15
**********************************************************************************************************************************************************************
Hi. I thought I'd give out this kernel which allows one to set SELinux=permissive for a rooted T-Mobile Note Edge with base NK3. This setting is needed if you would like to run Linux on Android and, I believe Viper4Android if you are so inclined, as well as some other specialized apps (for future reference, let me know what apps you use that need this setting). Once you have loaded this kernel you can use the app SELinuxModeChanger, found in the play store, to set SELinux=Permissive and back to Enforcing. Note, this setting is maintained until you change it back in the app (rebooting will not change the setting). Anyways, what I am providing is a gzipped tar file that you can download, gunzip and then load on your phone using ODIN (version 3.07 worked fine for me, goes in PDA). Remember, this kernel is ONLY for the T-Mobile N915T NK3 rom. Actually, I have only tested it on the Lab Rats rom so hopefully it will work on other roms for T-Moble N915T with NK3 base.
As most folks like to have a name for their kernel I've decided to call this the "Low Lying Fruit Kernel" (LLFK) because it only has a minor change made to it. Indeed this kernel is about as low as it goes (lol) as not a single line of code is changed. I only changed an option in the Makefile from true to false. Details are given at the following github site.
https://github.com/mscion/Permissive-Kernel-N915T-EDGE/
Anyways, I've been using this kernel for over 10 days with no problems, but, of course , for those that try LLFK, the usual warnings apply! I am not responisble for anything that happens to your device as a conseqence of
using this kernel. Indeed you have to be crazy to try it as I have zero experience at this! You also might want to read this before you try setting SELinux=permissive:
http://en.wikipedia.org/wiki/Security-Enhanced_Linux
One more thing, while my preference is that an experienced dev make a kernel worthy of the N915T EDGE, I am open to suggestions to make some more modifications assuming the request are somewhat consistent with the philosophy of LLFK.
Thanks to @jimmydene84 for boot.img and @deeznutz1977 for testing!
Don't forget to do a full back up! Good luck!
Kernel Download link: For SELinux=Permissve option only
http://www.4shared.com/archive/oH5fE053ba/llfk_permissivetar.html

Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?

VenpaCasa said:
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
Click to expand...
Click to collapse
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...

Awesome @mscion

deeznutz1977 said:
Awesome @mscion
Click to expand...
Click to collapse
Thanks! What would be even more awesome is if someone tries it and it works! lol.

I'll flash it now kind sir

mscion said:
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Click to expand...
Click to collapse
Omg dude if ur really serious, hell yeah I'm willing to test. I'm extremely greatful n lost for words right now. Thanks so much for just attempting ?? at least. Made my day lol

deeznutz1977 said:
I'll flash it now kind sir
Click to expand...
Click to collapse
I hope you mean Odin it! Drum roll please....

mscion said:
I hope you mean Odin it! Drum roll please....
Click to expand...
Click to collapse
kernel is not se android enforcing

@mscion you still had to use the selinux changer app correct?

deeznutz1977 said:
kernel is not se android enforcing
Click to expand...
Click to collapse
Hi @deeznutz1977. Depending on rom, I think when you boot up you will get that message. Please check in settings > about device and see what SE for android is showing. For now I have pulled the kernel because I unwittingly used the boot.img from lab rats rom to pack in my zImage file that allows permissive setting, cause I thought it was not modded. I am currently waiting to hear from @jimmydene84...

deeznutz1977 said:
@mscion you still had to use the selinux changer app correct?
Click to expand...
Click to collapse
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...

mscion said:
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
Click to expand...
Click to collapse
Stock deodexed. And sorry about not reading the op. Don't you know that all of the cool people don't read ops
Sent from my SM-N915T using Tapatalk

@mscion I asked jimmydene to pm you ...

deeznutz1977 said:
@mscion I asked jimmydene to pm you ...
Click to expand...
Click to collapse
Thanks very much! We're all good. I'm putting the link back up shortly.

Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.

VenpaCasa said:
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
Click to expand...
Click to collapse
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)

mscion said:
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
Click to expand...
Click to collapse
Honestly your awesome. I was starting to regret my purchase too. I'll assume you weren't asking me if it's ok but if you were, yeah that's fine. I'm actually any using that ROM
EDIT: Just saw your edit n thanks (to both) that's so awesome! I owe you guys!

When ubr done are you going to post here or a new thread?

VenpaCasa said:
When ubr done are you going to post here or a new thread?
Click to expand...
Click to collapse
Just pm'd you with link. If it works I'll post it in this thread.

BLN aktivate under CM12.1, it works

Excuse my bad English.
With the Kernel DorimanX b11.0 b012 now BLN have brought to works again.
I use CM12.1 official, while I proceeded as follows:
- Create a backup from the rom first.
- Under "/system/lib/hw" I have the "lights.exynos4.so" swapped from CM11.
- Because the lights.xxxx.so under CM11 have a different file name "lights.msm7x27.so" so it must be renamed in "lights.exynos4.so".
- set file permissions to 644
- reboot the rom
- Install STweaks and activate BLN. Now BLN should be work.
-------------------------------edit 19.10.15
I have the file from my second mobile phone Samsung GTS5830.
On it the phone is the rom "cm-11-20150912-UNOFFICIAL-cooper.zip; CyanogenMod 11 [Linaro]" installed.
http://forum.xda-developers.com/galaxy-ace/s5830-develop/rom-cyanogenmod-11-t3194339
The need file called under CM11 "lights.msm7x27.so"
But I can not upload the file. I don’t have the permission here.
With this file BLN and BLNWW works for me.
--------------------------------edit 20.10.15
With the changed file, the screen brightness can not be changed, unfortunately.
-------------------------------edit 20.10.15
I have found a *.so with the BLN works and the brightness control of the display functions.
The file is from image "decuro_GALAXYS2_4.8.8_4.1.zip Jelly Bean"
I uploaded the file under http://filehorst.de/d/bfwjFnoe
Delete under "/system/ lib/hw" the original file and add the new "lights.exynos4.so".
Set file permissions to 644
So far, I could not detect any error with the file.

charlie8104 said:
Excuse my bad English.
With the Kernel DorimanX b11.0 b012 now BLN have brought to works again.
I use CM12.1 official, while I proceeded as follows:
- Create a backup from the rom first.
- Under "/system/lib/hw" I have the "lights.exynos4.so" swapped from CM11.
- Because the lights.xxxx.so under CM11 have a different file name "lights.msm7x27.so" so it must be renamed in "lights.exynos4.so".
- set file permissions to 644
- reboot the rom
- Install STweaks and activate BLN. Now BLN should be work.
Click to expand...
Click to collapse
@charlie8104 Which "lights.msm7x27.so" you are talking about i just downloaded the cm11 snapshot12 and the file name you specified is same as the file name in cm12.1
If you have that file plz upload here
Have u tested this??

If this is the cause of the problem, it shouldn't be too hard to implement to the kernel. :good:
Thanks, gsstudios

Thanks for edit i will try it out
EDIT: BLN worked but m not able to control screen brightness it always stay high
EDIT: It works now..Thanks Man

charlie8104 said:
Excuse my bad English.
With the Kernel DorimanX b11.0 b012 now BLN have brought to works again.
I use CM12.1 official, ...
-------------------------------edit 20.10.15
I have found a *.so with the BLN works and the brightness control of the display functions.
The file is from image "decuro_GALAXYS2_4.8.8_4.1.zip Jelly Bean"
I uploaded the file under http://filehorst.de/d/bfwjFnoe
Delete under "/system/ lib/hw" the original file and add the new "lights.exynos4.so".
Set file permissions to 644
So far, I could not detect any error with the file.
Click to expand...
Click to collapse
Don't worry about your English!
Thank you for not only providing your solution here once, but for even keeping your OP up to date with improved versions after issues got reported. @gsstudios might cherry-pick here to implement BLN in his DorimanX kernel again, if it proves to work without further issues.
So once more, thank you for investigating on that.

Hi Guys,
I have the two lights.exynos4.so compared. In the * .so that I use an entry for BLN is included.
Line 5 in the lights.exynos4.so with BLN function.
------------------------------
#####################################[############################################################################################################################################################__aeabi_unwind_cpp_pr0#strcmp#pthread_once#malloc#memset#init_globals#free#open#sprintf#write#close#__android_log_print#__errno#__stack_chk_fail#__stack_chk_guard#pthread_mutex_lock#pthread_mutex_unlock#load_settings#fopen#fgetc#fclose#load_module_type#fread#pthread_mutex_init#NOTIFICATION_FILE_BLN#NOTIFICATION_FILE_CM#PANEL_FILE#BUTTON_FILE#HMI#__cxa_finalize#__dso_handle#__INIT_ARRAY__#__FINI_ARRAY__#__exidx_end#__exidx_start#__data_start#_edata#__bss_start#__bss_start__#_bss_end__#__bss_end__#__end__#_end#_stack#liblog.so#libc.so#libstdc++.so#libm.so#lights.exynos4###################################################### #######
------------------------------
The entry "NOTIFICATION_FILE_BLN" is completely missing in the original CM12.1 File.
The BLN entry would probably take place before the decompiled File Android Image is constructed.

Hi all, can't get this to work, is it that I need DorimanX kernel to do it? I thought you could do it with the stock CM12.1 kernel.

You need DorimanX.
Stock doesn't support BLN at all.

can someone attach the .so file? i can't seem to properly access the uploader's site...
:good:

souler456 said:
can someone attach the .so file? i can't seem to properly access the uploader's site...
:good:
Click to expand...
Click to collapse
@souler456
Hope this will help
EDIT: Check if it's working for you or not? Don't know why it's not working for me

sonupm said:
@souler456
Hope this will help
EDIT: Check if it's working for you or not? Don't know why it's not working for me
Click to expand...
Click to collapse
Yep. Working on my side. You changed permissions?
:good:

souler456 said:
Yep. Working on my side. You changed permissions?
:good:
Click to expand...
Click to collapse
Yes It work 1st time then I disabled capacitive buttons light and enabled it again after that BLN stopped working

sonupm said:
Yes It work 1st time then I disabled capacitive buttons light and enabled it again after that BLN stopped working
Click to expand...
Click to collapse
Try deactivate/active your BLN settings in Stweaks/Synapse...
:good:

souler456 said:
Try deactivate/active your BLN settings in Stweaks/Synapse...
:good:
Click to expand...
Click to collapse
Leave it. I don't use it anyways just wanted to help you and its working for you then no probs here:good:
You are on DU 9.8 Right ?? and I am on cm12.1 with Dorimanx by gsstudios. So I think this problem is kernel specific

I can make the updater script for dorimanx kernel to automate this process so we all have working BLN. Although I don't see it as a final solution, it works.
gsstudios
Edit: Got BLN working on kernel install. BLN will be fixed in next build
Edit 2: Now it isn't working
Edit 3: Now it works Seems like kernel reflash did the trick

@gsstudios
Same procedure like back then, when I tested successfully and your tests failed. So nothing much changed.

the.gangster said:
@gsstudios
Same procedure like back then, when I tested successfully and your tests failed. So nothing much changed.
Click to expand...
Click to collapse
Did you mean this method or last time when I 'attempted' to fix it? Because I'm now using this method to make BLN work on DorimanX. Last time I did the wrong thing and nothing would have happened.
gsstudios
Here is my commit which does pretty much the same thing as what the OP said but automated in the script: https://github.com/gsstudios/Dorima...mmit/d9432c3d87e26c09d6bad03ecdc22015ea4a9638

gsstudios said:
Did you mean this method or last time when I 'attempted' to fix it? Because I'm now using this method to make BLN work on DorimanX. Last time I did the wrong thing and nothing would have happened
Click to expand...
Click to collapse
I was referring to post #5 in here followed by these in the DorimanX-thread:
http://forum.xda-developers.com/showthread.php?p=63379702
http://forum.xda-developers.com/showthread.php?p=63438826
http://forum.xda-developers.com/showthread.php?p=63715347
and below. All in October.

the.gangster said:
I was referring to post #5 in here followed by these in the DorimanX-thread:
http://forum.xda-developers.com/showthread.php?p=63379702
http://forum.xda-developers.com/showthread.php?p=63438826
http://forum.xda-developers.com/showthread.php?p=63715347
and below. All in October.
Click to expand...
Click to collapse
Oh, that was my silly mistake. Wasn't clear enough I wasn't trying to use the fix back then, instead I was being a noob and replacing the file included in the kernel when I should have updated the script to replace the original file on the ROM. TL;DR, I replaced the Kernel lights.exynos4.so instead of ROM lights.exynos4.so :laugh: I am certain next build will have BLN fix

LoL
now I finally understand why our tests led to completely different results.