yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
look into "general" section, there are some threads about stock roms. But you have updated ota, so I think you already have kitkat bootloader. But to be sure you take the right steps to update and root your beloved tablet, you can follow this how-to:

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

There you'll found all what you need to get all working. In the last step install Hyperdrive rsl1. Later you can change the kernel, but don't forget to wipe cache and dalvik. It's protects you for troubleshooting.

I think this is what you are looking for.:cool:
[Galaxy Note 10.1 (2014 Edition) Original Android D] avdaga:
Ever since the beginning i had freeze issues with this kernel, most likely because my device cannot handle the OC. After reducing the gpu freq to 667, the freezes rarely happen anymore, but still do occur every now and then. Also, the gpu clock does not stick after a reboot.

So i checked the voltages and apparently the voltage for 600 and 667 mhz is the same. However, as soon as i modify the file, it gets overwritten by borked values:

Default:

100 775000
177 775000
266 812500
350 862500
420 912500
480 950000
533 987500
600 1012500
667 1012500
733 1037500

After any change:

100 100
177 775000
266 177
350 775000
420 266
480 812500
533 350
600 862500
667 420
733 912500

Does anyone experience similar issues and/or know how to solve it, or is it a bug in xluco 1.7? Are you guys using tools to change the gpu freq/voltage? The ones i know do not work with this kernel.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi!

I've the same issues with 1.7 and before that in 1.6!

Random reboots in browser (mostly in Chrome) and random freezes in Youtube and also in games like RealReacing3.

We all are waiting for synapse control, what comes with stable 2.0, how xluco says.

At the moment I use AndroidTuner app to modify the CPU settings and voltages and for monitoring kernel-data and other things. The second tool I use is TricksterMod, but here's not anything working too.

Waiting for stable 2.0 and synapse support, but xluco has a lot of work, so I think, we need another week or 2 patience.

I only have energysafemode enabled, because the temps goes to high with 1.9ghz and overclocked gpu. Sometimes it goes over 90°C! With 1,4ghz and and -50mV undervolted I get temperatures round about 70-75°C, but higher framerates on the gpu side as with stock kernel.

This is my middleway while I wait for stable 2.0.

[MENTION=2682152]enotar[/MENTION]

Have you get what you need and is Hyperdrive working with xluco 1.7 now?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
How are you editing the file? Two column files like that have to be changed by a script and can't be edited directly or weird problems happen.

#!/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;

I didn't want to post this because inevitably somebody will write an init.d script with faulty voltages and not be able to boot their device, but the correct syntax for setting the GPU voltage with a script / terminal emulator is:

echo "775000, 775000 .... (voltages from lowest to highest)... 1037500" > /sys/devices/system/cpu/cpu0/cpufreq/GPU_volt_table;

Let me know if you're still having problems and I'll look into it :)

Wow, temps shouldn't be getting that high! I'll look into that right away
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Done, I am with Hyperdrive now 2.0 give me SOD so I went back to 1.7. This looks perfect.No SOD, no crash, reboot etc.. all is fine. Thank you

---------- Post added at 08:05 AM ---------- Previous post was at 08:00 AM ----------

Where is energysafe?what soft you use to change kernel parameters?

Thank you
[Galaxy Note 10.1 (2014 Edition) Original Android D] avdaga:
Thanks for the quick response! :) This explains indeed why the result was as it was; The frequencies were interpreted as voltages, luckily they were by far lower.

By the way, do NOT put the commas in-between, it will result in negative values.

For completeness, my init.d script is now:

#!/system/bin/sh
# GPU tweaks
echo 100 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_gpu
echo 667 > /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)
echo "775000 775000 812500 862500 912500 950000 987500 1012500 1017500 1037500" > /sys/devices/system/cpu/cpu0/cpufreq/GPU_volt_table

So the voltage for 667 Mhz is increased by 5mv, and if needed I will increase it a bit more. Not sure why it was identical to the 600MHz by default, you might want to reconsider that in the next release :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Oops, you're right, I didn't even notice I'd put a comma haha, I'm having a good tidy up of all the sources at the minute so i'll definitely bump the 667 voltage for the next release :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Yes, it's very high, but I get that high temperatures only under gaming-load(without energysafemode) with RR3 or another heavy game. On "desktop" I have normal temperatures between 40 and 60°.

---------- Post added at 09:34 AM ---------- Previous post was at 09:18 AM ----------

Energysafemode you find in settings> general and scroll down to energysafemode switch. There you find 3 settings about!

And to modify CPU/kernel settings I use AndroidTuner App from Playstore in free version. Is a powerfull tool, that give you much informations for whats going on on your tablet. You can place multiple widgets on homescreen with temps, clockspeed, used ram and so on... Test it out, you'll like it.

Till xluco get Synape App working it is the best compromise for me.:D
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Dont have this energysafemode in settings/general and scrolling down.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hähh?! Can not be! There must be a switch for CPU ernergy saving in settings and in the notification bar, if you have a Note 10.1 P600.

Please look carefully and do not spam the forum with useless questions.

Ok?
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Is it power saving mode?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Yepp!
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Ok thank you
[Galaxy Note 10.1 (2014 Edition) Original Android D] killer8297:
is it possible to include the xpad.ko kernel module to make the xbox controller work?

I would greatly appreciate it!
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
V2 Alpha 3..4..5.. what are we up to?

Sorry guys, I just really don't have time to work on this at the minute, hopefully I'll have a bit of free time to get lots done next week

http://d-h.st/pMp

PLEASE, PLEASE make sure you run /sbin/xboot.sh if /sdcard/xluco_kernel/logs.txt doesn't show that its been run - it fixes A LOT of instability!!

Added to V2A3 :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
Awesome, thanks so much. Gonna flash in a bit. Will report back with feedback :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] killer8297:
THANK YOU SOOO MUCH!

I can confirm that the xbox 360 controller works with p600!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Koserman:
Flashed! Trying it out meow :D
[Galaxy Note 10.1 (2014 Edition) Original Android D] allan1313:
Forgive my ignorance, how does one go about doing this?
[Galaxy Note 10.1 (2014 Edition) Original Android D] freearcher:
please make one kernel to P605.......
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
No problem so far
[Galaxy Note 10.1 (2014 Edition) Original Android D] Koserman:
Had my first reboot while trying to post that I had no random reboots, lol! It's tied to using the stylus in chrome when hovering over a link. Don't think it's kernel related but I figured I'd post it here

Download SManager, navigate to /sbin, click on xboot, click on "su" and "boot" icons, click run...and I think that's it
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi!

Do not work with smanager. See screenshot!

[IMG="screenshot smanager"]https://mega.co.nz/#!OYdmzABb!pWTLc6nHSFlTLpWebdF_nyoBAVpVnWj7vXywSYKuPJ4[/IMG]
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
See here!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ykkfive:
hi

wanted to discuss with u an issue about your kernel source but found that u do not want to receive pm

mind to send me a pm if u have read this reply pls?

thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hey, sorry I didn't realize I had to turn PMs on haha, you should be able to pm me now :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] amrdia:
Bro can you add fast charge support ?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ykkfive:
pm sent, just in case u didnt set the pm notification

thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
+1 I got the exact same output when I tried to run the script
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
yep seems theres a small error with the random number thing, shouldn't affect the rest of the script though, I'll fix it up this weekend :)

I've also had a reboot in chrome with the pen out, no idea whats causing that but ill look into it
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Xluco!

At the moment I have no reboots with Chrome and spen here with V2A3! Neither plug nor unplug caused reboot.

I think this is caused by Chrome,I had random reboots with Chrome in each rom now and then.

For me V2A3 works perfect till now, fast and snappy!

Great work!

I have 25.000+ in Quadrant. :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
Hi xluco. We are still waiting for a stable kernel for p601. Please do something

iPhone 'den Tapatalk aracılığı ile gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] ElAguila:
+1 to this.
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
[MENTION=5529656]xluco[/MENTION]

Here is another log. Random reboot occurs whenever I use the S Pen with google chrome beta or the normal google chrome with the latest Alpha version as well as the latest stable version. P600 model, here's the logs :good:

https://www.dropbox.com/s/2ntjyauq3rb9i6d/2014-08-22_18.02.zip

Sent from my Note 10.1 2014
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hi guys, sorry I've not been around in a few days, been really busy and then to top it all off my virtual machine went kaput and I lost everything, so I've spent a few days getting everything back in order. V2 Alpha 4 will be up later today and that will be the last of the alphas, beta will focus on squashing the last few niggles and adding Synapse support finally!

Then V2 Stable - which I will use as a base for the p601 version. Once p601 V2 is ready we can focus on the future :) What do you guys wanna see and I'll try my best!

It's coming, hopefully V2 will be stable by the end of next week then p601 will get my full attention

Thank you verrrry much! The log pointed to something in the cpu scheduler, tbh I couldn't pinpoint the problem exactly, but I've only made once change to the piece of code it pointed to recently, so I reverted it and hopefully that should be fixed :)

Fastcharge

Someone mentioned fastcharge but I forgot to press quote :P ... I'll look into it
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
[MENTION=5529656]xluco[/MENTION] thanks for the reply.

The only thing I need is the S Pen reboot bug fixed, I'll be sure to test the new Alpha when it comes out. One quick thing, have you ever thought of registering with Dev host so its easier to see all the previous files, new Alphas etc. Just a thought....
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Why didn't I think of that :P http://d-h.st/users/xluco
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Version 2 Alpha 4

http://d-h.st/73f

General fixes here there and everywhere... hopefully the bootscript should run all by itself now thanks to some changes I nabbed from [MENTION=3292224]franciscofranco[/MENTION].

For those asking for fast charge: This release has Halaszk's battery charger control, and I boosted the USB max current limit to the same as AC, (300mA to 700mA), I've tested it and it seems to be working but I haven't tested it for a long period of time obviously, so keep any eye on it for now.. don't want anyone's devices exploding. I'll look into the porting the actual fast charge mod for our device this week :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
Lol good to see :)

Just flashed the latest alpha, everything seems good so far. Don't want too jinx it but I think the S Pen reboots are gone, thanks for the update :good:

Sent from my Note 10.1 2014
[Galaxy Note 10.1 (2014 Edition) Original Android D] mikep2323:
So I flashed newest version of kernal and was getting android system (UID) is granted superuser permissions toast 12 times every minute. I flashed version 1.7 and it doesn't do that.Is anyone else experiencing this? Also anyone know how to fix so it stops. Thanks

I even reflashed fixed permissions and cleared dalvik cache and cache and I still get the problem. I went back again to older version and that doesnt happen.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
+1

same toasts here!
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
+2 I get this as well.

Also, [MENTION=5529656]xluco[/MENTION]

Random reboots with S Pen are not gone as it turns out. Random reboots still occur when using Chrome or Chrome Beta

Here's the logs:

https://drive.google.com/file/d/0B35dv8DCRfo-RFlGT3FWdXZtMm8/edit?usp=sharing
[Galaxy Note 10.1 (2014 Edition) Original Android D] redbaron:
Lot of "Android System [UID] has been granted ...." after kernel install

Hello

I installed this kernel version 2.0 alpha 4 on stock rooted ROM CNF1, wiped cache and dalvik. After boot I get lot of notifications from SuperSU "Android System [UID] has been granted root privileges for interactive shell".

Whats that?

And one question additionally, is there any app to control added functions of this kernel?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi!

We all have that issue with v2a4! Take 1.0 (stable) or 1.6beta (most powerfull for me) for now until xluco has fixed it.

With 2.0 beta we will get synapse support to control all kernel-features.

Is only a matter of time!

For now take android tuner app for cpu controls like undervolting.

Hope that help (press thanks)

:good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ykkfive:
first, I have to say I don own a note 10.1 2014 (anymore), but I ve been studying xluco's kernel for a week or two

for the su toast problem:

- 12 toast popups in a min means either 5 seconds for each popup or 1 followed by 1. this could be likely due to a script is running in the background which will be triggered every 5 seconds, or there r 12 commands will be executed per min

so if it is the case, you can

1 check the script, probably resides in the init.d directory, and see what the script does (may be called by an app also say in order to perform some tunings) , or

2 disable the popup in supersu for related apps

anyway, just my 2 cents and I cant tell if it is the real problem since, as I mentioned, I dont own one, and perhaps the problem has nothing to do with what I mentioned

so, good luck and hope this helps
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Jeah! I agree! Thinking somewhat in shboot-script is running all the time instead of just once. xluco want to go safe, that shboot runs, perhaps he meant it too well. For now I went back to 1.7 and waiting for the next release, because I do not want to meddle in shboot-script.:p
[Galaxy Note 10.1 (2014 Edition) Original Android D] ykkfive:
cool, glad to know u found the cause

i dono what it is the purpose for the script but should be trying to maintain something, perhaps stability

i believe some ppl here are technical enough to fine tune it, may be u can ask for somebody's help or wait for xluco

good luck
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
hey guys, I had notifications turned off in SuperSU so I didn't notice but its probably the part in "init.xluco.sh" that changes the priority of SystemUI and stuff, I'm out atm so if someone can try erasing those parts and see if it stops that'd be v. helpful :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Linux Test Image

Virtual Terminal / Framebuffer Support - DEV Image

http://d-h.st/RMB

This is a kernel image based on a slightly modified version of V2A4 that includes Virtual Terminal (CONFIG_VT) and Framebuffer Console (CONFIG_FRAMEBUFFER_CONSOLE) support.

This is for those who asked for it, to hopefully improve their experience installing Linux distos via LinuxDeploy etc.

Please, please, please don't install this unless you need it, it doesn't do/improve anything if you don't know what it's for.

The image will take 3-5 minutes to boot, it will appear like its stuck on the "Galaxy Note..." logo, but it's not, just be patient.

VT is compiled into the kernel, FRAMEBUFFER_CONSOLE and its components are compiled as modules found in "/lib/modules/" as compiling them into the kernel caused bootloops.

in your terminal emulator:

$ su
# mount - rw,remount /
# chmod 0777 /lib/modules/*
# insmod lib/modules/fbcon.ko - and the rest, or whatever combination you're going to use
# mount -o ro,remount /

Let me know if it works as I'm not currently using linuxdeploy or anything like that :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Is there anyway to fix smartscroll When I install sto k kernel it works.

Thank you very much
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nik_SV:
Install this kernel on the P601. Program APKTool for Android began to work on this kernel! But ... does not work external bluetooth keyboard. The tablet gives notification "Connected bluetooth keyboard", but pressing a key does not give any result.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Berth666:
no problems here with a logitech bluetooth keyboard
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nik_SV:
Do you use a kernel for SM-P601?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nik_SV:
Flashed V1-STABLE (for SM-P600). External bluetooth keyboard is also defined, but does not work. Keyboard from China (no Name). But on many devices and firmware worked without problems ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Nik_SV!

I own too a china keyboard and since I upgrade to 4.4.2 it don't works. It is the one you can click over the display to safe the display from damages. I ask the seller about this issue, but till today I get no answer.

I think this 15 bucks are gone! Hehe!:confused::p
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nik_SV:
ollimi1,

My keyboard is normal works. I flashed stock kernel, and the keyboard works without problems.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
Again you forgot p601 users xluco :)

iPhone 'den Tapatalk aracılığı ile gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
Just fount out!

Many thanks, I will try it out when I will first find some time. Also I would be interested to know the exact procedure you followed to avoid the bootloops as I'm trying to compile a similar kernel (with full VT support) for note 12.2 . Again many thanks;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Nik_SV!

I've the same china-keyboard like you. I'll give it a try with stock kernel! Did you use External Keyboard helper or get it working without that app? Would be nice if my 20bucks was not wasted.

Thanks for the tipp!:good:

10 minutes and a flash later...

Yeah! It works again! Thanks!

Seems xluco have to changed some files in his kernel that cause the issues with our keyboard. With 1.7 it paired indeed, but lost the connection 1 second later.
[Galaxy Note 10.1 (2014 Edition) Original Android D] avdaga:
This does not appear to resolve the matter as the changes are gone after reboot..
[Galaxy Note 10.1 (2014 Edition) Original Android D] BillBunyip:
I tried the test1 version on P601 device, SELinux is gone (from about device), but still don't have ntfs support (well when I mount ntfs usb it says they are blank).

Should test1 build work (in which case I will look at other possible causes), or do I have to wait for you to finish v2 for 601? Is there a log file I can look at to identify the issue? log.txt just has 2 post reboot entries - redundant busybox binary removed from sbin, ro.config.knox =0 and ro.config.tima=0 for each.

Really looking forward to getting ntfs support on this device, many thanks for your efforts.

Cheers
[Galaxy Note 10.1 (2014 Edition) Original Android D] mali76:
Yes xluco we are waiting for your support for p601

iPhone 'den Tapatalk aracılığı ile gönderildi
[Galaxy Note 10.1 (2014 Edition) Original Android D] avdaga:
Just had first freeze with spen in v2a4
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
Stating the obvious won't help, we already know about the reboots. What the dev needs is logs so he knows how to fix it. Download the app Syslog, then after the random reboot take the log and upload :good:

https://play.google.com/store/apps/details?id=com.tortel.syslog

Sent from my Note 10.1 2014
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hello is there anybody out there?

So much hard work in real life?!

Or is the tread dead?

Pray for a little holiday for all our friend xluco in order to get 2.0 stable with Synapse support even in this year. ;)

please not feel compelled!

Just a bit fun to breath something life into the tread...
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hola, sorry guys I'm just really busy atm. I'm also climbing a mountain tomorrow, having surgery on Monday and my course starts again on Tuesday :silly: . I was hoping to have the kernel stable for then as it's what I use to make notes in class but it doesn't look like I'm going to be getting my few quiet hours that I wanted.

So I'm going to go full steam for the next few hours to get the superuser notification thing fixed at least, expect that tonight.

I promise, promise, promise that synapse will be at least partially working by the end of this week, and if it isn't then may Odin's wrath be upon me.

In other news though, a number of people have forked the kernel on github so hopefully you wont have to put up with me being painfully slow for long and we might just get some real devs working on some amazing kernels :highfive: hooray.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey, hey!

Sounds good! Hope you will get it as you think!

Little off topic, but

break a leg for your climbing session.

Where do you want to climbing? Scottish highlands?

Envy you for it and wish you beautiful weather and much success.

:good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
V2B2 / V2B2-VCFB

Notification thing is fixed... I'd done something stupid in the ramdisk :P

Added the Tab S boot animation, just because.

Re-added -funsafe-loop-optimizations, again, just because.

V2B2: Download

This is the ordinary kernel [the one you want].

V2B2-VTFB: Download

This is probably not what you want. This is the one with Virtual Terminal and Framebuffer stuff - again its gonna take a looong time to boot so be patient. Framebuffer modules are now located in "/system/lib/modules".

We're climbing Scafell, whether that's classed as a mountain I dunno :P
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Works well

Smartscroll doesnt work as in stock.

Thank you