yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
It could be that the updater-script sets the permissions properly, runs the script, then when the device boots /sbin gets its permissions set again.

I've tweaked a few things and I'm not using:

run_program("/sbin/busybox", "chmod", "0777", "/sbin/xboot.sh");

run_program("/sbin/busybox", "script", "/sbin/xboot.sh");

just to be sure :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] suzook:
I hate to keep harping on color/gama controls. But will we ever have this? I knkw it was mentioned it is now in the kernel, but how do we go about changing it? Thanks again for all the hard work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
echo 4 > /sys/class/misc/mdnie/hook_control/scr_black_red;
echo 4 > /sys/class/misc/mdnie/hook_control/scr_black_green;
echo 4 > /sys/class/misc/mdnie/hook_control/scr_black_blue;

Thats what I've found so far.. maybe look into Halaszk88's note 3 thread for more info, personally I'm not too fussed about the screen so I've not been paying that much attention to it. If you find anything out let us all know :D
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
EDIT: another new feature is that wacom QoS is also changeable

# Wacom QoS
echo 1600000 > /sys/module/wacom_i2c/parameters/qos_wacom_cpu_freq_level_1;
echo 650000 > /sys/module/wacom_i2c/parameters/qos_wacom_cpu_freq_level_2;
echo 650000 > /sys/module/wacom_i2c/parameters/qos_wacom_cpu_freq_level_3;
echo 400000 > /sys/module/wacom_i2c/parameters/qos_wacom_int_freq_level_1;
echo 222000 > /sys/module/wacom_i2c/parameters/qos_wacom_int_freq_level_2;
echo 222000 > /sys/module/wacom_i2c/parameters/qos_wacom_int_freq_level_3;
echo 800000 > /sys/module/wacom_i2c/parameters/qos_wacom_mif_freq_level_1;
echo 400000 > /sys/module/wacom_i2c/parameters/qos_wacom_mif_freq_level_2;
echo 400000 > /sys/module/wacom_i2c/parameters/qos_wacom_mif_freq_level_3;

Though again I have no idea what that does
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
RC5 added to the OP

https://mega.co.nz/#!RBdCWCaA!Sc4yWio_GS7KfAjXwyaLKnT_b3A1ZOv1hKtz0m5qy-0

if this isn't stable, god knows what is

apologies if mega links are inconvenient, d-h.st was being offside
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
v1 STABLE

V1 - STABLE added to the OP!

I'm bored of RCs now, the kernel is stable enough to be a daily driver for now. xboot.sh running at boot is a bit temperamental, so if you're having any problems make sure you run /sbin/xboot.sh manually!

Stable - Download

V1-STABLE: Download Here - [24/05/14]

V1-STABLE: Mega Mirror - [24/05/14]

If sdcard/xluco_kernel/logs.txt doesn't show xboot.sh as being run, please run /sbin/xboot.sh manually!

Over 325 commits since v9, check github for complete changelog.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hpblze:
Multitouch

Multitouch fix

Since you are working on the kernel , I just want to request if you can fix the multitouch issue in kitkat

It was fixed in jelly bean a while back but has returned in most Kitkat firmwares . As of now this one for kitkat EUCND2 is better for multitouch as I extracted the boot.img and flashed it .

Can you look into the multitouch issue in the kernel and incorporate in yours ..

It would be awesome !

The issue

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

The solution for Jellybean

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

Can you fix it for Kitkat ....
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
Xluco Wè are waiting p601 kernel

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
so please give him the time he needs. ask him is okay, but please do not push him:rolleyes:. he also has a life outside of xda!
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
You'll be waiting a long time.

EDIT:

Sorry that was a bit snappy :P As I discovered when trying to put together Permissive Kernel for the 601 and 605... unlike the 600, the 601 and 605 have different variants in themselves, each with different ramdisks and defconfig files.. some even require different versions of mkbootimg to put the flashable image together. Unfortunately, a) I don't have the time or mental capacity to keep track of all that stuff, b) its of no real benefit to me seeing as I don't have the device :P
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
I flashed succesfully it is now permissive but phone feature has gone

iPhone 'den Tapatalk aracılığı ile gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Because you flashed the 600 version on your 601... 600 doesn't have the drivers / kernel features to support a phone
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
You are right. So without flashing this kernel,isnt there a way to enable permissive selinux mode. I just want to use ntfs drives

iPhone 'den Tapatalk aracılığı ile gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
If you are rooted try typing:

su

setenforce 0

Into terminal emulator
[Galaxy Note 10.1 (2014 Edition) Original Android D] Grykonmon:
Super more stable than before with xKat 3.0, no wifi problems or crashes (pardon me my bad english) thank you!
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
I'd love to, but without knowing exactly what changed in that kernel, I dont know what to change in this kernel :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
Hi xluco. As the owner of the request for p605 international version, I'm willing to give a hand. I did compile kernels a few times in the past for my linux desktop. In fact I don't even have a windows system now.

I also understand from partition layouts a little bit, fiddled with them when trying to root the Homesync.

FYI, we are desperate of a kernel for selinux permissive as the Samsung kernels don't let "setenforce 0" to do anything. It's useless.

So I'd say if you can maybe upload your stuff or tools and maybe could comment a bit on methodology or steps to compile, I could try give a hand at least for p605.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hey :) everything I use is on my github - github.com/xluco. Except the linaro toolchain which is here - https://github.com/UBERUTILS/linaro-arm-eabi-4.10

It not really a problem of compiling its that theres the 605, 605K, 605L, 605S, 605V and 605M.... cba making a kernel for each.
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
OK, appreciate if I need to do any specific Magic (ie to disable selinux, or pick some kernel Config or specific mkbootimg) , but I will start checking your repository ASAP.

I asked Samsung if lt03eur is the right codename or not for my lt03lte, no response yet...

---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------

Btw the others are pretty specific devices for specific operators, the international model is lt03lte which is in use in many parts of the world so hopefully it can get a bit more attention of yours :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Nothing in the kernel needs to change, just init.rc and default.prop in the ramdisk and the updater-script in the build stuff needs to delete Knox from system/app

EDIT: I do normally disable the other security things that aren't used in the kernel config though, like apparmor and tomoyo, to save space and avoid any conflicts :) You can also choose to disable SELinux completely if you want
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
This might be a stupid question but how are people making roms for this device when there are no rom sources?
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
Rom business is different. Rom are available to download in binary form from sammobile site or from a dump from the device itself. They can use existing kernel from device, updated Rom files, mix and match them, etc...
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Ah that's what I thought, so they're not being compiled from source, just editing files in the binary?
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
Definitely not compiling from source. However the apk contain some Java code if I understand well and some resources, so these can be modified to have custom stuff, settings, skins themes etc. Of course they are also very talented guys since putting these together in a working way is also a tough job.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
thanks :) i get it now
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
So can Wè disable selinux by modifying init.rc or default.prop or something else?

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
Btw I managed to compile the kernel yesterday but did not have time to create boot.img to flash it yet.

Is it possible to just use stock ramdisk without making any change, since this kernel is also stock sources?

Also it was not possible to use linaro tool chain as it gave some warning which then got treated as an error. Disabling -Wall from the compile flags fixed it but then I had other error at lzop stage. So I reverted to normal toolchain and it got compiled with some warnings and produced the zImage.

---------- Post added at 06:27 AM ---------- Previous post was at 06:25 AM ----------

Hayır, it won't work in my view as selinux seems to be locked at kernel level. If we could set it permissive from ramdisk we could theoretically disable it also from running system. But I can give it a try if the kernel I compiled works.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
Hı fastguy we are waiting your permissive kernel

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hey, thats great news :) you can use the stock ramdisk but SELinux will still be enabled if you do (unless you've completely disabled it in the kernel config, in which case its a good idea to remove all mention of it from init.rc).

Don't remove -Wall, remove -werror & -Werror-implicit-function-declaration instead :)

The most common cause of error with linaro is the /arch/arm/boot/compressed/Makefile ... make these changes and it might compile: https://github.com/Xluco/kernel_smp600/commit/c30cc1b8970b91f3ab04083751154f6b1a0fa765

You will probably need to add "ccflags-y := -O2" to the top of /net/netfilter/Makefile as well

:D Hope that works, let me know
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
Thanks, I'll try that, but I'm now stuck into a bigger problem. The images I create don't boot the system. It either gets stuck in the Note 10.1 2014 boot logo, staying there forever or goes to download mode after displaying it.

I tried to just unpack the boot.img and re-pack it with same zImage and ramdisk, it does not boot. Very strange. I need to fix this first.

I'm not actually using your mkbootimg but others that I found in the net, I even compiled one from source trying to change base address, ramdisk address, etc.

here's what I get when unpacking:

unmkbootimg version 1.2 - Mikael Q Kuisma <kuisma@ping.se>

Kernel size 7536872

Kernel address 0x8000

Ramdisk size 1375263

Ramdisk address 0x2000000

Secondary size 0

Secondary address 0xf00000

Kernel tags address 0x1e00000

Flash page size 2048

Board name is ""

Command line "console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F"

*** WARNING ****

This image is built using NON-standard mkbootimg!

OFF_KERNEL_ADDR is 0xFE208100

OFF_RAMDISK_ADDR is 0x00200100

OFF_SECOND_ADDR is 0xFF100100

Please modify mkbootimg.c using the above values to build your image.

****************

Extracting kernel to file zImage ...

Extracting root filesystem to file initramfs.cpio.gz ...

All done.

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

To recompile this image, use:

mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x1dfff00 --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F' -o new_boot.img

---------- Post added at 01:10 PM ---------- Previous post was at 12:46 PM ----------

I may have found a clue. Looks like Snapdragon 800 needs a different mkbootimg command named mkboot. I got it from the guys for note3:

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

the clue is here: http://xdaforums.com/showpost.php?p=46229656&postcount=7

I tried to unpack existing boot.img and repack it, flashed it, now it boots! but it got a message that selinux is not enforcing, however, it is. (and i did nothing, so i did not understand why this message appears on the boot logo top left corner like it does in the recovery boot)
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
Come on friend, you will succeed

iPhone 'den Tapatalk aracılığı ile gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
Looks like I did, I replaced the zImage with the one I built, and it worked! witih selinux permissive! (I guess I removed selinux support when compiling this, but I can't be sure).

Anyway, now I lost Wifi. So probably I compiled Verizon version, i'll try with the international one, and then MEA one, let's see. There's hope!
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
Good luck go on

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi

---------- Post added at 02:53 PM ---------- Previous post was at 02:49 PM ----------

By the way if you succeed will it also work for p601?

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
No, as this is for P605, totally different CPU architecture (Exynos vs. Snapdragon). P601 would need more info and its sources, boot.img, etc. If I manage to disable selinux on this, we can theoretically do it for P601 as well, thanks to xluco's guidance.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Great news man! Re: the wifi thing.. did you do the secure storage thing in build.prop?
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
Nope, it came to my mind after I deleted all working files of that build. So now I'm trying to get something that works, selinux included, and then disable stuff.

How did you precisely achieve the selinux disable stuff? Did you disable it from kernel? What did you enable instead if you disabled it in kernel? There are some options there like AppArmor, etc.

Did you somehow make it just selectable to Permissive? If yes, how.

Also you said remove selinux stuff from the init.rc I saw just a line in the beginning that enables it and debugfs, then the remaining seems to be just setting permissions. Also there's one last entry at the daemons section. Did you remove all these?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Its more to do with KNOX on these devices I think, I've not changed anything to do with SELinux in the kernel. All you have to do to get it into permissive mode is "setenforce 0" in the terminal... but to get that to work, you have to remove all the knox apps and containers, set "persist.security.ams.enforcing=0", "ro.config.knox=0" and "ro.config.tima=0". And that should be it really :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] lightofhonor:
Got a shutdown when trying to run Antutu on V1.0 on XKat 3.0. Not a restart lol didnt know it could do that!
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
I couldn't find "persist.security.ams.enforcing=0" value. Where is it? And how to remove the Containers?

SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] Joey121215:
I'm curious, is there a way to force the A15 processor to always be in use when the screens on?
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
I checked now. This is in default.prop inside the ramdisk. You can also do it if you have a Linux computer using the tools mkbootimg found in xluco github and ubmkbootimg tool from xda (search in Google it will appear)

But I could not find ro.confix.knox=0 so I put it in default.prop as well. I found the ro.config.tima=1 in the build.prop and set it to 0.

Let's see now...
[Galaxy Note 10.1 (2014 Edition) Original Android D] fastguy:
Nope, whatever I did, I could not manage to get it to work only with those parameters in the ramdisk default.prop and system build.prop. I always get enforcing and cant' set it Permissive. Are you sure you did not change anything in the kernel itself?

I tried with a zImage I compiled, and indeed this is giving me Permissive. It looses the Wifi but can fix it with securestorage line in the build.prop. I can also set selinux back and forth. Now the issue is, I can't remember what were the kernel parameters I used :) So I will need to re-build it and test.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
v1.1 added to the OP

http://d-h.st/G67

pick bd36ff7 Fix warnings and compilation errors with gcc 4.8
pick b115ac4 CPU unaligned access path[francofransico]
pick acf16f9 Disabled Gentle Fair Sleepers
pick 86d841c cpufreq: Memory leak with sysfs when stats table are freed
pick 85ea6ff fix some warnings
pick 12e6921 Additional memset fix for gcc 4.8
pick c4b5725 CRYPTO: Fix more AES build errors Building a multi-arch kernel results in:
pick 289ab47 fs: Use BUG_ON() instead of BUG()
pick b1378b4 Kconfig(s) changes
pick cd1473c CFLAG / LDFLAG Extravaganza
pick ba1c5d3 [B]Add UKSM 1.2.2 and replace KSM[/B]
pick 293aa93 Revert "screen hooks for powersuspend"
pick e77ea3d Revert "kernel/power/powersuspend: new PM kernel driver for Android w/o early _suspend v1.4 (Yank555.lu)"
pick 431aad2 Revert "kernel/power/powersuspend: LCD screen on/off hooks (Yank555.lu)"
pick 0f09e9a Revert "kernel/power/powersuspend: new PM kernel driver for Android w/o early_suspend v1.2 (Yank555.lu)"
pick 3fffa52 Revert "kernel/power/powersuspend: new PM kernel driver for Android w/o early_suspend v1.1 (Yank555.lu)"
pick b957212 Revert "kernel/power/powersuspend: new PM kernel driver for Android w/o early_suspend (faux123)"

Main changes are: intoduce UKSM, removed the powersuspend driver and introduced lots and lots of CFLAGS/LDFLAGS fromJustArchi

I think I figured out why the boot script doesnt run, and I think its because samsung uses a custom init binary that blocks shell scripts being run at boot... but I could be wrong. So as ever, if you have any problems, run /sbin/xboot.sh manually first before complaining :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] mustbepbs:
Anyone else getting weird artifacts in Chrome while watching full screen videos? The screen tweaks out and garbles up.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Not happening to me, but it could be something to do with the new CFLAGS, I'll look into it
[Galaxy Note 10.1 (2014 Edition) Original Android D] Koserman:
I haven't had any disturbances with video yet, tried about 6 different ones. I'm on xKat 3.1 if that helps any.

Also, I haven't had any random reboots! Thank you sir for the awesome kernel!
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
good stuff man :D

I've reverted a couple of the CFLAGS I applied anyway just to be safe.

Working on adding halaszk's OC to the kernel stuff tonight!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Finally, got my Note10 back yesterday! With a new motherboard with knox counter 0x0... Baaam!! 250 bucks damned rip-off! To this day I don't know what was really broken!

**** happens?

Have tested it and all seems okay, but it comes back with Android 4.3.

So I have just odined it to 4.4.2 U.S., than odined TWRP and then flash UXProject V3 and -you were right- your first stable kernel from sdcard. Everything went smoothly, no problems. sh.boot runs from start up and now the Note10 is as it should be. You have really done a good job and I expect big things in the future.

Will test the stability in a game session with Real Racing 3.

I have TricksterMod app installed to check a few things, but can you recommend a tool to read the GPU / CPU values?

Thanks for your hard work and i will report if a have any trouble :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey xluco

After 1 hours gaming I had 93 ° C, so it is a good idea to put the CPU in Energy Safe Mode! Limited only the A15 / 9 performance, GPU stays at max., But temps goes down to only 76 ° C! Seems the A15 cores are a little bit hotheaded ;)

I've try to under volt the CPU and use Android Tuner for it. What tool you use for it?

I've modify the Voltages with AT, but after this the energy saving mode do not works properly. But I can so UC with AT too, so there is no real trouble.

I'm looking for a tool to modify the GPU! Do you now a good one or is it only possible with a script (terminal app) at the moment?

After a few more hours of testing I have the Following results:

UC at 1.4 ghz and UV to -0.50 v I have gaming temps from 70 ° C.

GPU furthermore clocks at max.,

so there is a better gaming performance possible with your awesome kernel.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hey :)

There was a little tool posted a dozen or so pages back called MaliStatus that will help you read what the GPU is doing. As for changing anything I just use scripts but that's not very user friendly, I'm working on some GPU stuff for 1.2 so I'll post that and a little script too soon :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hey mate. I'm trying to unlock 933 MIF and need a hand please :)

What do I need to change the "1050000" to on line 138? and what do I need to change line 154 too? Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Okay, thanks! Download MaliStatus and will have look...

Can't wait for the next great features ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
v1.2

v1.2 added to the OP

http://d-h.st/xGl

Main changes include - GPU OC to 733MHz, MIF frequency increased to 933Mhz, GPU / MIF / INT Voltage control!

pick 77d3522 revert some CFLAGS
pick eb32f27 move to sabermod toolchain
pick 04c2ddc MALI GPU OC / Voltage stuff from Halaszk
pick 8463e50 GPU OC tweak
pick 6e2a962 devfreq: Add Exynos 5420 MIF voltage control TNX Andreilux for this
pick 07fc664 devfreq: Add Exynos 5420 INT voltage control TNX Andreilux for this
pick a676651 INT/MIF fix
pick 1ef1fba EXYNOS5420 MIF: unlocked 933MHz Memory clock from 800MHz (not OC, only unlock Samsung locked freq step) (@halaszk)
pick f25daef Fix for compiling error:
pick 0accfef v1.2 / defconfig

As promised a few posts ago, here is a little script to help you control some of the new features in 1.2:

#!/system/bin/sh
# GPU tweaks
echo 100 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_gpu;
echo 733 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq_gpu;

# GPU Power Policy (demand, always_on, coarse_demand)
echo "demand" > /sys/devices/platform/mali.0/power_policy;

# Set GPU voltages (not recommended unless you know what you're doing)
# @ /sys/devices/system/cpu/cpu0/cpufreq/GPU_volt_table;

# Set INT voltages (not recommended unless you know what you're doing)
# @ /sys/devices/platform/exynos5-busfreq-int/devfreq/exynos5-busfreq-int/volt_table;

# Set MIF voltages (not recommended unless you know what you're doing)
# @ /sys/devices/platform/exynos5-busfreq-mif/devfreq/exynos5-busfreq-mif/volt_table;

Big, big thanks to halaszk again!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Thanks for 1.2 and also to Halaszk!

I will test 1.2 and post here how it works for me.

---------- Post added at 08:38 AM ---------- Previous post was at 07:50 AM ----------

Okay! On my side are no problems. 733mhz step works, get 9300 gpu score on antutu. Will test it now with real racing, but I must UC the cpu because the A15 cores. (My last cpu died due to hard gaming temparatures, but with no OC on stock kernel and CleanROM 2.0 :(

Hope the 733MHz run not too hot in game play.

Will test it carefully and give a feedback.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hmm, the max temperature should be 115c at that point the cpu should UC itself to about 600mhz I think... its something really low. Ill look into using some different settings on 1.3 :)