yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] HumanCaviar:
Clean boot and enabled westwood, thanks my friend!

Almost forgot to ask, whats the deal with the power suspend option? Does it play well with UV? (Currently running at -60mv)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
It should do, I'm not undervolting on my note ATM but I've been running a kernel with powersusped on my nexus 5 with between -75 and -150mv for a few weeks now and it all seems fine :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] HumanCaviar:
Cool, I'll give it a try.

I know benchmarks are a bit subjective, especially Antutu, but here's some data:

Device:

SM-P600

Rom:

xKat v2.0

Kernel:

Xluco Kernel v0.10t3 (kernel flashed, wiped cache & d.cache, caches allowed to settle, several clean reboots)

Kernel Settings: (set with Faux123 - all not mentioned = stock/default)

CPU:

Max Clock: 1.90 ghz

Min Clock: 250 mhz

Voltage: -60mv UV Global

I/O:

eMMC Scheduler: Deadline

eMMC Readahead: 1024KB

eMMC Entropy: OFF

SDCard Scheduler: Deadline

SDCard Readahead: 1024KB

SDCard Entropy: OFF

RAM:

Clear VFS Cache After Boot: ON

Auto FS Writeback Delay Mode: ON

MISC:

TCP Congestion Protocol: Westwood

Antutu Benchmarks: (nothing else running, reboots between runs)

36274

35488

34735

35544

Antutu Benchmark Average: 35510
[Galaxy Note 10.1 (2014 Edition) Original Android D] lightlance7:
My bluetooth keyboard stops working when I use this kernel, anyone know a fix?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Sorry for the delay with 0.10 guys, I'm migrating to a new system in between decorating and college :eek:

I've decided 0.10 will actually be V1.0, so I'm trying to give this as much time as it needs but expect 1.0 RC1 either tonight or tomorrow :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] sdfgsteve:
xKat 2.1. That's that hard bit with all this, is it a kernel issue or a ROM issue?
[Galaxy Note 10.1 (2014 Edition) Original Android D] golfinggino:
I have tried the latest updates and I have issues with all the latest ones being the tablet freezes I've gone back to the .8 version it's seems to work the best on my tablet
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
RC1 Here!

~360 commits :D logs very very much appreciated!
[Galaxy Note 10.1 (2014 Edition) Original Android D] golfinggino:
just flashed the latest update and it is running well - i had issues with all the updates since .8 but this one seems to be working and also seems quite a bit quicker - thanks for the update !
[Galaxy Note 10.1 (2014 Edition) Original Android D] Eastern89:
Really smooth :)

Log attached :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] robherc:
I just upgraded to 1.0RC1 from 0.10t3 and am using it with the ★★xKat v3.0★★ rom. I am not sure if it is the kernel or the rom but I had the tablet freeze twice with 0.10t3 whilst using the spen. Anyways the main reason I used your kernel instead of the one included in Kat V3 was that SELinux was stuck in enforcing mode, however with your kernel on my machine it is disabled completely. Do you know how I could enable it with this kernel?

Thank you very much;

AmonX

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

Posted by proxy, as AmonX doesn't yet have enough XDA forum posts to post in Development threads.

-Robherc

-------------------------------------------------------------------------------------------------------------------------------------------------------
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
while at that question, i just want a stock kernel that has selinux disabled. is this possible?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Try: setenforce 1 in terminal emulator
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Completely disabled or just set to permissive?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Right guys...

I've been running variations of RC1 for 5 days.. absolutely no issues re: wifi, random reboots, etc. I am running a stock rom.

Everyone who's posted that they're having problems of that nature seems to be running XKAT.

This is neither the kernels fault or the roms fault, I think it's just that something between them both is conflicting, as in the post a few pages back.

If you are running stock rom and are having these issues I desperately need to know, and preferably with logs attached.

If you're having these problems and are running XKAT then I don't really know what I can do for you, short of looking through logs, as I'm not willing to install a custom rom for testing purposes.

Thanks guys :highfive:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
i believe permissive is sufficient. my only objective is to run linux using either complete linux installer or linux deploy.

sorry i just read the requirements that it needs loop devices support. not sure if selinux permissive is also required, but any chance you could get it work would be awesome :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
i'm coming from stock rom and kernel.

just flashed rc1. wifi is disabled again ro.securestorage.support=true

no random reboots so far. i'll let this thing run for a while longer and report back.

how do i capture logs for you?

edit: antutu x reported 34600, 34524
[Galaxy Note 10.1 (2014 Edition) Original Android D] robherc:
SELinux permissive is absolutely required for running Linux on your android device using the CompleteLinuxInstaller app from the LinuxOnAndroid project, as we use scripts that are run as root to load the lop device that mounts your image; SELinux set to "enforcing" blocks all scripts from being run as root.

---------- Post added at 06:44 PM ---------- Previous post was at 05:58 PM ----------

From terminal emulator, run the following commands (root permissions should likely help, but shouldn't be required).

dmesg > /sdcard/dmesg.log
logcat -f /sdcard/logcat.log
cp /proc/last_kmesg /sdcard/last_kmsg.log

then you can zip the log files together into one .zip or .tar.gz file & post it in here.
[Galaxy Note 10.1 (2014 Edition) Original Android D] tincmulc:
I still have the stuck on 650MHz bug on RC1. After exams this week I will try to debug it some more (find out what exactly triggers it). The steps to reproduce it for me are: use the device normally (but don't reboot). After a few hours the frequency will not go above 650MHz(using a monitoring tool like cool tool to monitor live cpu frequency). The device also can't enter deep sleep anymore, but I can't find what is keeping it awake (wakelock detector doesn't show anything unusual).

I'm using Hashcheck-Hybrid-v2 ROM. I have confirmed that it doesn't happen with the stock kernel and that it does happen on this kernel's default settings.

I also can't really give you any logs since I don't really know when it happens and by the time I notice it the information is no longer in the log. I will try to get some more information when I have more time. Until then I would like at least someone else to confirm the bug or debunk it by telling me that after 12+ hours of uptime they can still reach 1900 MHz and show me there is a problem on my end.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
The app 'syslog' does all the work of capturng logs / zipping them :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Not seeing it myself, but I'll look into what I can do :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] tincmulc:
Thanks for that, now I know it's something on my end.

Just to be sure, how much screen on time do you have there? I don't get the bug in standby.

I'll install a stock rom during the weekend and see if it fixes it. Maybe my old 4.3 bootloader has something to do with all of this.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Not very much screen on time at all haha, maybe thats why I'm not seeing it
[Galaxy Note 10.1 (2014 Edition) Original Android D] :
Mine never goes in deep sleep, strange? :confused:
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
****tingpiss, device just rebooted.. everything wiped. **** this.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
For what it's worth. I haven't experienced any unexpected reboots so far, but antutu reported a new low of 17690. Let me know how else to help you.
[Galaxy Note 10.1 (2014 Edition) Original Android D] injola:
I put the spen inside an empty ball-point pen so that it fits my hand better. So it is never inserted. I wonder if there is a software switch to turn off wacom pressure sensitivity. I don't see it in the power saving menu. It would be nice if it would turn on automatically with Lecturenotes or something like that.
[Galaxy Note 10.1 (2014 Edition) Original Android D] tincmulc:
With samsung DVFS disabled I still get stuck on 650MHz. A link to an old log (before the dvfs disable): https://www.dropbox.com/s/desp8e523ncrbcz/2014-05-14_11.39.zip
[Galaxy Note 10.1 (2014 Edition) Original Android D] loll:
Hello GuyZ

Titou if u want test this :

you have to edit the build.prop and add this line ro.config.tima=0

But for me i dont know why the wifi dont turn off even if i applied always off when screen off ...

I had to download an apps for that ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] halaszk88:
[MENTION=5529656]xluco[/MENTION]

Add this lines into your ramdisk init file:

prepareKnox () {

BP="/system/build.prop"

if grep -q ro.config.tima=1 $BP; then

sed -i "s/ro.config.tima=1/ro.config.tima=0/g" $BP

fi

APKS="KNOXAgent.apk KNOXAgent.odex KnoxAttestationAgent.apk KnoxAttestationAgent.odex KNOXStore.apk KNOXStore.odex KNOXStub.apk ContainerAgent.apk ContainerAgent.odex KLMSAgent.apk KLMSAgent.odex ContainerEventsRelayManager.apk ContainerEventsRelayManager.odex"

for APK in $APKS; do

if [ -f /system/app/$APK ]; then

rm /system/app/$APK

fi

done

}

Samsung knox and tima service cause error under custom kernel. This script remove these and TAB works perfectly. My Note 3 kernel works perfectly with this lines.

See my ramdisk :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Thanks! I had the first bit but I'll add the apks bit :D Unfortunately I travel for college so I won't be home until friday. Hopefully with this and a few reverts I made to the kernel the other day it should finally, finally be stable.

Edit:

Is it worth adding something like:

else echo "ro.config.tima=0" >> /system/build.prop

into the tima bit, or would that be unnecessary?
[Galaxy Note 10.1 (2014 Edition) Original Android D] :
Yes it works. Thanks:thumbup:
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Theres a line to add that to your build.prop in /sbin/xcore.sh, this tells me that the scipt isnt executing, so youve inadvertantly helped me fix that :P haha
[Galaxy Note 10.1 (2014 Edition) Original Android D] halaszk88:
sed -i "s/ro.config.tima=1/ro.config.tima=0/g" --> it is owerwrite tima value 1->0 with linux sed command.

This script not fully working your sh script, because sh script not use early 'init". Rebase your ramdisk INIT mechanism and working perfectly after it.

See my ramdisk how I do it.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Wow... Following halaszk's info from a couple of posts ago (removing those apks and tima=1.. RC1 is running amazingly, not a single little niggle on my end :) probably a good idea for everyone running this kernel to do the same, and I'll implement it by default in RC2 tonight
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
RC2 added to the OP

http://d-h.st/tzd

Just stability stuff and removed GPU OC for now seeing as it doesnt really work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
Thanks xluco. I just flashed to rc2. Here's my report:

1. FC on "Samsung KNOX" on every restart. Dirty removal? Still seeing "KLMS Agent", "KNOX", "KNOX Store" in Application Manager

2. Can rotate to either portrait orientations but not 180° landscape i.e. upside down

3. Feeling a lot more buttery smooth now than on rc1. Antutu still reports only 32k+...still somehow much lower than stock.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Eastern89:
How much do you make in antutu stock ? 32k is a fine score ? :0

Xluco , it flies now :D my tablet never felt this smooth :D

Gpu oc is still too unstable ? :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
I usually hit at least 35k on stock. See http://xdaforums.com/showthread.php?p=52471950

There were others who also hit 35k with xluco's kernel...but not me obviously :( http://xdaforums.com/showthread.php?p=52473946

http://xdaforums.com/showthread.php?p=52322410
[Galaxy Note 10.1 (2014 Edition) Original Android D] halaszk88:
What was the problem of GPU OC?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
I couldn't get it to go over 600mhz, despite everything saying it should be reaching 733. Ill re-add it after v1, I just didnt want to slap a 'stable' sticker on something I can't seem to achieve on my device :) The "time_in_state" thing would say that 733mhz was being reached but someone mentioned a while ago that TIS reporting seemed to be broken.. it might have been you, I dont remember, so I don't know what to think haha

edit: I didnt mean to make it seem like I was suggesting your code didnt work btw, just whatever I've done to it :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
hmm, it doesn't seem like my bootscript is being executed, which is weird because I'm doing exactly the same thing on my nexus 5 and it works without a hitch :/

EDIT: To fix the knox / FC stuff, execute /sbin/xboot.sh manually :) I'm working on it as we speak
[Galaxy Note 10.1 (2014 Edition) Original Android D] halaszk88:
Tested GPU OC without disabled touchwiz DVFS? I compared base mali source with this device and my N3 kernel source and it is not differ from my source. I think if your GPU not go over 533Mhz, TWDVFS apk cause error with its idiot algorithm and it can block OC freq etc etc
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
I was using the wanam xposed module to disable DVFS, tried it on and off, and also with boost mode on/off, it didnt seem to go over 600mhz.. is there another way I should be disabling DVFS?
[Galaxy Note 10.1 (2014 Edition) Original Android D] tincmulc:
RC2 fixed the 650MHz bug.
[Galaxy Note 10.1 (2014 Edition) Original Android D] :
Last release is great. Undervolt -100mv with no issue:thumbup:
[Galaxy Note 10.1 (2014 Edition) Original Android D] vprasinos:
Xcat 3.0 with RC2. Never seen this tablet perform so fluid. Its almost identical to note 3. Pure butter! Thanks xluco!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Can not wait to get back my P600 from Samsung. A day before you start with xluco-kernel my tab was broken and now has cost 249, - €uro for root / knoxcounter 0x1. Grrr!!!

Watch your thread since test 0.1, really good job, hope soon to thoroughly test if mine is back. The development for our p600 was great in the last few weeks! Thank you
[Galaxy Note 10.1 (2014 Edition) Original Android D] halaszk88:
I use this xpoosed module to disable TWDVFS:

https://play.google.com/store/apps/details?id=ma.wanam.dvfs

See my screenshot, GPU working fine with OC

For more optimization, I unlocked 933MHz of memory clock and N3 very monster and smooth phone. (see pictures)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
RC3 added to the OP

http://d-h.st/ODD

Again just stability stuff.

If everything goes smoothly with this one it's likely ill just rename the zip and call it stable so if you notice any bugs please let me know :) thanks guys.

EDIT: I enabled something in the config called "samsung_product_ship" - "set up product for shipping"... it doesn't actually seem to have done anything that I can see, but psychologically I feel better for having it :P If anyone actually knows what it does please let me know!
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Already made a new branch for post-V1, this will be the first thing I'll add back :) thanks for all the help!

At least this way stable will be ready to flash by the time you get your device back :D

Thanks mate, glad its running well :)

I forgot I could even undervolt I've been so busy!

Good stuff! I think I must have changed something when I was messing with overclocking versions and versions ago. RC2 reverted all that :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
It seems that despite executing that script (with root permissions by root explorer), the apps still cannot be removed. I have yet to manually remove the apk from /system/app though

By the way, I just experienced a hang on the tablet so I had to force a reset. Attached log if it helps.

Edit: sorry didn't notice rc3 is already released! You're too fast haha. This post is based on rc2
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Thanks for the logs, though last_kmsg.log seems to be corrupted :/ Let me know if you get the same problem with RC3 though :)

I tried to do the sensible thing and not delete the knox apps completely, didn't want to presume that people just wanted them totally wiped, so I tried to copy them to a backup folder on the sdcard... didn't work.. so they're now getting nuked during flash haha
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
just flashed rc3:

1. /sbin/xboot.sh didn't seem to have executed properly (or at all?) on my end. the listed apks are not moved to /sdcard/xluco_kernel/knox_backup and there's no such directories created in the /sdcard. i'm really confused here.

2. tested antutu twice. first score 22,918, second score 26,957

3. i still cannot flip my landscape orientation 180°. is this a kernel limitation?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
What rom are you running? Rotation sh OK uldnt be effected at all, im able to rotate 180 on stock rom.

Antutu / benchmarks in general are beyond useless, run 5 times = get 5 wildly different results.

Can yout check the permissions of xboot.sh, should be 0777 and if youve got terminal emulator can you try running the script in that and see if it produces any errors on your device? Thanks, appreciate all the feedback, stable is getting closer by the second :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Out of curiosity seeing as xkat and this kernel dont play nicely together, could someone send me the xkat build.prop and any init.d scripts that come with it? Thanks :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
permissions were on 646 :/ changed to 777 and executed the script. backup directory was created but apks were not removed lol. attached output from terminal.

i'm on stock too. i'll check my xposed modules later to see if anything is conflicting. thanks for your quick response and looking forward to next release!
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Thats really weird, it should get set to 777 as part of the updater script when flashing :S hmm
[Galaxy Note 10.1 (2014 Edition) Original Android D] injola:
starting to build

Hi Xluco. Some of us are interested in a kernel that only has selinux permissive.

http://xdaforums.com/showthread.php?p=52769826

If I download the kitkat source (maybe an entire build environment) from samsung, and build, do I get an exact copy of the stock kitkat kernel?... or at least something close? Is it fairly straightforward? What I would want is a boring, but stable kernel. My laptop runs debian unstable, if that makes a difference.

I have built many kernels, but its more complicated every time. I guess the huge blob you get from samsung has the cross-compiling thing really solid?... In 1995 there were so few config options, you could easily examine them all; and email the ide driver author for help, etc. These days, its like restaurants in NYC, they add them faster than you can read them.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hey :)

The download from samsung doesn't come with the cross-compiler.

git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6 (this is the stock cross compiler)

I read the other thread.. This is the first samsung device I've owned.. SELinux isn't disabled in this kernel, it's there and set to permissive mode... however I have reason to believe KNOX and SELinux are somehow intertwined and you can't run a custom kernel stably without disabling knox and therefor completely disabling SELinux :( .. but I'll look into it for you :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] injola:
Thanks! I really thought I read somewhere that the stock kitkat kernel on this device has selinux enabled but not set to permissive mode. Does not mean its true. What we really want is to install linux. I wonder if disabling KNOX would be enough.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Well.. that was easier than I thought :P Stock kernel, SELinux in permissive mode and Knox removed: d-h.st/Qcs
[Galaxy Note 10.1 (2014 Edition) Original Android D] injola:
Awesome! Thanks for the trouble. I flashed it. I'll try to install linux...
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Give me 2 mins mate, i made a small derp in the ramdisk, uploading new version as we speak
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
RC4 added to OP

some extra CFLAGS, SELinux fix and scripts should now run as normal

V1-RC4: Download Here - [19/05/14]
[Galaxy Note 10.1 (2014 Edition) Original Android D] injola:
Hmmm. Not sure what that is about.... I am installing debian right now. The problems I had before are gone. But, if there's a problem

with the last kernel, I'll flash the next as soon as I can.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Its not so much a problem, just the rom cant see SELinux's status properly.. http://d-h.st/ziH fixes that. I just commented out a line I shouldn't have. Probably wont cause a problem but for stabilities sake try the new one :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] troemer:
Very nice work :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] injola:
Installed. Thank you. This really removed a roadblock.
[Galaxy Note 10.1 (2014 Edition) Original Android D] OMIGHTY1:
Compatibility

I installed PurePerformancesX, while having xKat 3.0 installed. After installing the rom and mod, I installed the kernel (or somewhere around that order.) After installing the kernel, my device started crashing and restarting itself. Any ideas as to why this might happen?
[Galaxy Note 10.1 (2014 Edition) Original Android D] nrage23:
PureperformanceX is nothing but trouble.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
just flashed to rc4:

1. no more FC from knox. the knox apps seem to be cleaned up by the script. but i do notice there are still KnoxVpnServices.apk and KnoxVpnServices.odex in /system/app. are these safe to remove too?

2. fyi noticed that xboot.sh permissions set to 646

3. tablet shut itself down after running antutu for the second time. log attached
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
I agree with nrage23, scripts like that, in general are nothing but trouble.. lots of build.prop tweaks pulled from the gingerbread days and not specific to any device.

use the PurePerformance uninstaller, clear cache/dalvik, reflash this kernel then fix permissions and the problems should be gone :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Yep you can remove those if you're not using a VPN, I'm not so I've not tested the effect of trying to connect to one with those apps removed.

I honestly have no idea what to do about the permissions :/

ive set it to 777 on my computer before zipping it, "set_perm(0, 0, 0777, "/sbin/xboot.sh");" is in the updater-script, and chmod 777 /sbin/xboot.sh; is in init.rc.. excuse me while I bash my face against my desk :P
[Galaxy Note 10.1 (2014 Edition) Original Android D] ionflux:
me too :p i guess it's no issue as long as the script eventually does its work!