yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
Hi,

I think its kernel related as well but I only have it on Chrome or the Beta Version, not on other browsers such as Dolphin. I don't think its a multitouch issue because the only touch input that's being registered is the pen on the screen, not ten fingers at once :)

Just ideas anyway, if you go back a few pages I've provided a few logs after reboot occurred. (Last ksmg and a few other things) unless you mean taking a log whilst the tab is on and working?
[Galaxy Note 10.1 (2014 Edition) Original Android D] keiany:
Excellent, I use kernel with hydronium rom for days and didn't have any problem in my ordinary works.

Thanks again
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nik_SV:
Wonderful kernel! But bluetooth keyboard on the latest build does not work. xluco, no idea how to fix it?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi again!

I use the S Pen only slightly. In my case the browser crashes probably for some other reason. I will make 2 Logcats, one with and one without browser crash and compare both. But with my modest skills I can mark most relevant rows and send the whole to xluco. For more I'm not good enough. Haha!

---------- Post added at 04:16 PM ---------- Previous post was at 03:41 PM ----------

Hi Nik_SV!

On my side my china-keyboard only works with stock kernel. Maybe we can ask Xluco for help, if he looks up which files are missing. Maybe he can help that bluetooth keyboards runs with his kernel also.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hey everyone,

Is anyone having the chrome reboot on any of the "v3" kernels?

And re: bluetooth keyboards, is it a specific keyboard or is it that no bluetooth keyboards are working?

I'm still looking into the smart scroll/stay thing, I'll try some bluetooth keyboards of my own, and hopefully drop a new version tonight :)

EDIT: also, someone was asking about adding KEXEC, turns out that the kernel already has it, it just needed enabling in the config, which I've done in V3PA4. So if anyones brave enough to test that, let me know how it goes.
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
I'm flashing the latest alpha now, will report back if I have any random reboots.

Almost flashed the wrong file. Too lazy to tidy up lol :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi xluco!

I have only the chinese keyboard, that you can clip over the screen, so that it looks like a notebook. (Backside is in black plastic leather, this also existed for the old Note10.1 and also for Nexus 7)

I can pair it over bluetooth, but when I try to write anything it is not recognized. With stock kernel it runs well also without External-Keyboard-Helper. I have tried to fix it with External-Keyboard-Helper but no luck!
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
V3-B1

SM-P600 - Download Here

SM-P601 - Download Here

Added tonnes of build optimisations (in a much more sensible and stable way than V2), a couple of big filesystem improvements (EXT4 should be much faster now and supports FIDTRIM), I was feeling generous so I added the conservative governor, SIO, ZEN, BFQ and FIOPS schedulers. Disabled verbose debugging saving 70k from the kernel size.

I also gave the OP a quick refresh, the feature list now reflects accurately V3-B1 and onwards, stock kernel has been added to the second post if anyone wants to revert at any point :)

---------

I've added a few patches to V3-B1 from [MENTION=3511708]UpInTheAir[/MENTION]'s kernel to do with how HID handles keyboards and mice, let me know if that improves anything :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Thank you will test right away but it looks file name is v1 not v3

This one is very good, no crash with chrome and S-Pen for me.

Sorry to bother with that but smartscreen is not working....

I have coo tool with graph and it looks this kernel is the best for cpu load in standby so battery life should be excellent. And very snapy.....

That's it for now
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
oops, fixed the file name :P

I'm looking into this smartscreen, smartscroll stuff... any by looking into I mean, searching other forums to see if anyones fixed it because I've no idea whats going on :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Strange as it works with stock NH3, NI1 etc...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nik_SV:
Does not work. When you connect the bluetooth keyboard tablet does not define it as an input device. My second keyboard Logitech K400 (not bluetooth) works without problems (and previous versions of kernel). Keys and touchpad are working properly.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
I am typing this with my bluetooth keyboard that works perfectly. So I think there is no issue with kernel.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nik_SV:
Very strange ... What ROM you use? My bluetooth keyboard works without problems on the stock kernel, with other devices: Asus Fonepad 7 (stock ROM KK), ZTE V9 (CM11), LG L9 ... I'll try to find another bluetooth keyboard to check ...

Which version bluetooth module of your keyboard? In my keyboard bluetooth module version 3.0.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Rom is Hydronium
[Galaxy Note 10.1 (2014 Edition) Original Android D] keiany:
I use hydronium, but my keyboard doesn't work too.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi, again!

Unfortunately still not running for me. With new stock NI1 kernel it works without issues. My china-keyboard also have only bluetooth 3.0, if this should be important.

Thanks again for V3B1!

Great work!
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
What do you mean by bluetooth 3.0? Mine is completely fine and I am sure it is a generic BT keyboard from last year and from China.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ultim:
Been using the kernel with xKat rom. Great performance and battery life so far. Thank you for your time and effort.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Enotar!

In the specs for my Keyboard stands Bluetooth 3.0.

Have on the last page described which keyboard I have.

What rom does not matter, as long as I'm on stock kernel keyboard works properly.

:confused:
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Sorry but really dont have spec on my keyboard
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Look at the datasheet from your seller. I have my from Ebay and the discription says Bluetooth 3.0.

---------- Post added at 08:48 AM ---------- Previous post was at 08:17 AM ----------

Here is a picture of my kb:

https://www.dropbox.com/s/b8ikhk46c5qxfzx/20141001_081830.jpg?dl=0

Uppss!
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
I start to have some freeze lately need to test more.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hovercraftdriver:
My keyboard paired and connected as I had to type in the generated key WITH THE KEYBOARD...but it will not function after connecting. I have the Moko keyboard/case combo

http://www.amazon.com/gp/product/B00FUUPSRU/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

EDIT*** Just installed stock kernel and I am typing on BT keyboard right now.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bab1c:
Same issue with a Sharon keyboard, connect but nothing when typing... Work with stock kernel. But i prefere Xluko one ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
So I tested another keyboard, a mini ipad cover from logitech (nice one) and it works perfectly....

Btw I verify that I have V3b1, you never know after flashing many times..... of course last beta kernel is instaled so am I lucky?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nik_SV:
In any case, the code kernel from xluco something lacking for better compatibility Bluetooth devices as it is implemented on the stock kernel.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi!

Same thing here! Connected but nothing when typing on custom kernels.

---------- Post added at 08:28 AM ---------- Previous post was at 08:02 AM ----------

Hey Nik_SV!

I think, he has a bit too much cleaned up! Hehe!

Or perhaps some things are automatically disabled when using a custom kernel, p.e. like chromecast?

I suspect the error occurs if the keyboard use older protocols than Bluetooth 4.0.

Mine has deffinitiv only BT3.0!

Maybe all the keyboard owners with the recognition error can look into the keyboard-datasheet to see which Bluetooth version is into his keyboard, to check my guess?!?
[Galaxy Note 10.1 (2014 Edition) Original Android D] edmondt:
The new beta 3 is looking good :) Question... Which tool do we use to UV and tweak the settings? :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] 22sl22:
I use Trickster Mod which works fine for me.

Not sure if synapes works yet :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] brett_day:
Hey Guys

Quick question

I am rooted, running stock 4.4.2 ROM, is this Kernel safe to use with Stock ROM? I am having major battery life issues with my P600, and I am hoping that by flashing this kernel it may fix the issue....lord knows I have tried everything else. Either way I would still like to give it a try, just need to know if all is well with this kernel and stock ROM. Thanks in advance.
[Galaxy Note 10.1 (2014 Edition) Original Android D] buhohitr:
It should work with stock rom. Also use Trickster app to lower the frequency of the cpu to further improve battery life.
[Galaxy Note 10.1 (2014 Edition) Original Android D] brett_day:
Awesome. I flashed it and so far things seem to be much better (down to 72% after 1hr 53 mins use with 49mins screen time)...that is much, much better than I have experienced since updating to KK. What do you suggest for the frequency? I have never used Trickster before, and am a little lost.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi brett_day!

Normaly I had 1h display-on-times every 10% battery life on Hyperdrive V3.1 with Xluco kernel V2A4. With Tab S port battery-term it is a bit lower, maybe 10-15% or 8-9h, because spen is always enabled or something.

The new NI1 kernel on which Xlucos kernel is based is again somewhat economical with the batterylife.

But if you realy want best battery life, disable sync, haptic feedback and take Greenify to suspend all unneeded Apps.

To modify CPU setting like freq. or volt. I use latest 3C-Toolbox app from playstore. It allows also to modify governors and sd-cache, deaktivate autostart apps and so on.

If you want all in 1 take C3 Toolbox!

If you want a small Tool take TricksterMod!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ultim:
How much you guys are undervolting?
[Galaxy Note 10.1 (2014 Edition) Original Android D] :
-75
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Yes!

Between -25 and -100mV and more, depending on the SoC quality.

-50 To -75mV should go for the most chips!

You can test some voltage settings, but don't use "apply on boot" as long as you testing!!

If you get a reboot due to severe UC, kernel starts again with normal settings.

Again I use 3C ToolBox(formerly Android Tuner), because there be the possibility to make UC profiles and many more in free version.
[Galaxy Note 10.1 (2014 Edition) Original Android D] avdaga:
Thanks a lot xluco, it appears to be the most stable kernel so far (coming from v2); spen freezes seem resolved :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] buhohitr:
Have been running this v3 since it released and no issue here either. Good job!!!
[Galaxy Note 10.1 (2014 Edition) Original Android D] buhohitr:
Is it possible to have the option to shut down 1,2 or 3 cores in your kernel??
[Galaxy Note 10.1 (2014 Edition) Original Android D] hitman1376:
Well ... so decided to make TNT ?

Dear friend ... It's a very danger work to do ... because you might get into problems with voltage level and burn you'r CPU ... but if you still want to , I think you should be able to ... but just remember to not mess up with CPU core voltages ... good luck

With best Wishes

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey buhohitr!

Maybe when Xluco has synapse support fully implemented we get the possibility to deactive multiple CPU cores, like with ExternTweaks or another kernel tweaking app.

Sometimes I dreaming of the old Siyah-Kernel times on S3 i9100 and all the things we can modify!

Too bad that no "real" kernel developer owns this tablet. :(

Unfortunately unpopular Exynos 5420!:crying:
[Galaxy Note 10.1 (2014 Edition) Original Android D] buhohitr:
Thank you for the encouragement. I used to own a Asus tf700 quad core and basically I could choose any amount of kernel I would like to use and also set cpu frequency for each cpu. If we could achieve this, it would be a milestone toward glory land...and possible gain some more hrs with the battery too!! I heard you about the Exynos...it may be a show stopper.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
I really questioning the necessity for this level of complexity. I rather get a 100% use of the exynox for complex task.

Battery life is something else.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
V3-B2

Added to the OP :)

SM-P600 - Downloads

V3-B2: Download Here - [08/10/14]

SMP-601 - Downloads

V3-B2: Download Here - [08/10/14]

Lots of SLUB improvements, NVIDIA's power efficiency patches and fixes to unaligned access.

I haven't looked at the smartscroll thing or keyboard thing yet so they're still in the same state they were in the last build.

EDIT:

Also a note that turning cores off doesn't save battery, turning cores off and on under load uses more battery than just having them on, you can tweak the governor settings though to keep them at a lower speed more of the time, that would save you more battery than turning individual cores off. It's also a bit more confusing because of the big.LITTLE architecture I think.

I did look into the 'true octa-core' patch thing that was posted in the general section, but the three patches refer to files that don't exist in this kernel, so thats a no go also.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi xluco!

Thanks again!

V3B2 works good so far!

A short Antutu test says we are now a over 40.000 points device.:p

See here:

https://www.dropbox.com/s/dtvdnmptswsep5p/Screenshot_2014-10-08-22-47-47.png?dl=0
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Great kernel. Thank you. I have a question, is your kernel comming from NI1?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Yepp! V3 based on the NI1_STOCK_KERNEL!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
Hey xluco. Once again thanks for your great releases. One request if I may: can you release a VT enabled kernel by the time V3 will reach its final version? I kinda miss Linux-Framebuffer support on your V3 kernels which is/was why I reverted to the V2 ones (despite the fact that V3 is clearly better).

I'm sure I can compile it myself but I would prefer to have a finished product, so I think the right time for a VT kernel would be when "V3 final" is released.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Not yet, the NI1 source hasn't been released yet, as soon as it is I'll merge any changes :)

Yep definitely, there will be a VT/Framebuffer stable version for 600 and 601 :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Oops!!

I think the last spliff was too fat! :eek::silly:

I've dreamed V3 is already based on the new stock NI1boot.img.

Sorry!

Hope NI1 sources comes soon, because there are many improvements.

For that the V3 is based on old ND3 sources, praise would be even more.

V3 is really fast and has good battery life.:good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
haha :P

There's probably not a lot of changes in the kernel between ND3 and NI1, its likely to just be security updates and perhaps some driver updates from 4.4.4 which I already merged in V2, but will be in V3 stable too :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] whesh:
Hello can i install this kernel with the KOT49H.P600XXUCNH3 please?

Do i need to install a new recovery?

I'm actualy on knox warantly void : 1 Will it change?

Tx
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Yep, as long as its the 600 or the 601 model it will work. You'll probably need a custom recovery like TWRP to install it, that's what I'm using anyway.

If your Knox warranty is already void it wont change that, if it isn't void, it probably will void it. :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] whesh:
Btw is "knox warantly status : 1" means it's already no more on warantly?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
I'm unsure, someone else may be better able to answer you. My tablet doesn't say "warranty status", it says "Knox Warranty Void: 1" - 1 in this case meaning 'yes', so the warranty is void.
[Galaxy Note 10.1 (2014 Edition) Original Android D] law16:
Any chance of this ever working on p605 or p607t
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
No! Probably not!:crying:

SM-P605 is a completely other device! P605/607 has a Qualcomm quad SoC.

We SM-P600 user have an Exynos 5420 octa SoC in a big/little architecture.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi whesh!

If you flash a custom recovery like TWRP on a Samsung device with the new knox-security feature, than you will lost your warranty for sure!!:(

Rooting alone does not solve the Knox Counter!! :D

The only way to get the warranty back is to change the mainboard into a new one with knox counter 0x0!!!

If you send in a rooted device with Knox-counter 0x1, Samsung wants to change at first the main board, to get back the warranty. Subsequent repair is then nothing but the new motherboard costs $250,-.

Believe me, I was so stupid and tried it.:mad:

:eek:

The next bad news!

I've reading that Google has announced to implement Knox in all Android devices in the near future. We can only hope that Google dispense on a knox-counter in every device. Otherwise, it will in future also with other manufacturers even more expensive to use a custom rom!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
Up until two months ago Samsung would respect the warranty even if Knox counter was triggered. You're the first case that i personally hear about not having his warranty respected. It is sometimes the case that Knox is triggered merely by updating your rom with another official one through Odin.

Also what about bringing your tablet to a not posting condition (deleting the bootloader) how would they even know that Knox is triggered without booting the thing? I think it's cheaper to do this than replace the whole mainboard...
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Steve!

I've experienced this year in March so!

If you send back a rooted device with custom firmware to Samsung with knox counter 0x1, then the motherboard would Replaced! Only to root your device not solves the Knox counter, so you keeping your warranty.

I was even in consumer-protection-center and have spoken with an attorney, but no chance! Fact is, flashing a custom roms, kernel or a custom recovery will void the warranty! I only know that root alone does not delete the warranty.

And Samsung can read the Knox-counter even when the tablet is dead or if you delete the boot loader!

Maybe there are exceptions, but that's just coincidence.

I even appealed and contradicted the bill! No chance, I had to pay 250 €.

Maybe it has to do with our laws here in Germany, but this is very unlikely.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
Hmm, yes probably that's all about it. You send the item directly to Samsung whilst most of the guys I know sent it back to the store they bought it from. I heard about 9 (or 10, I'm a bit unsure right now) cases where people had their knox counter triggered yet had their phone/tablet replaced no problem.

So much so it happened that I had it almost as a given that the Knox Counter is a corporate thing nothing to do with us private consumers (knox kills the warranty to a corporate phone/tablet I thought).

I don't know if it's a Germany thing or sending the item to Samsung thing (probably the 2nd) but to my experience triggering knox does not kill your warranty most often than not. Of course there are cases where having triggered knox and a damaged device match (for example an overheated device due to overclocking) in which case I would think the warranty would not be respected either.

Anyway you put me to thoughts, up until now I thought people were scared because of that message it gives you when you trigger it, but now that I have a real world example of damage caused by it, I'd probably be more careful to whom I trigger and to whom I won't.... Thanks for that.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Yeah!

It still seems unclear what exactly Samsung aims with it!

I only know one, I'll buy me as quickly no new Samsung device in the next time.:p
[Galaxy Note 10.1 (2014 Edition) Original Android D] clouds5:
How can this kernel make my device that much more responsive and fast? Thx man :) appreciate the effort, I could instantly feel the difference and I really don't think it's only placebo.
[Galaxy Note 10.1 (2014 Edition) Original Android D] buhohitr:
This kernel is a kick ass. I'm using this kernel with "Pure stock NI1 root" rom and its not just fast and smooth but my battery life is awesome. Seems like I gain more and more juice after a week. As of today, I achieved 1 day and 6hrs standby and 8:22 hrs screen on with 5% left compared to my old 10hrs standby and 4hrs screen on. I did 95% of watching HD stream movies from the internet. So yeah, wifi is working hard too. Pretty sure if I just browse the internet, I should have it for 2 days without recharge!
[Galaxy Note 10.1 (2014 Edition) Original Android D] hitman1376:
Hi there every one ...

Dear [MENTION=5529656]xluco[/MENTION] , I were working on an Ubuntu Phone ( first Ubuntu Phone and then I'll go for a Kali NetHunter and maybe MultiROM then ) for our P601 ( it should also work with the P600 ) but I need help about the kernel / TS driver ( can see what features needed here )... so , Do you think you can give me a hand ? ( I'm just stupid about the samsung kernels ... Just samsung :) ... have no problem with my Htc M7 :D ) ... also does anyone have any experience about how we can test the binary with an emulator ( on PC... Not on the Tab ... ) ? ... Thanks in advance

With Best Wishes

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Hi, yep I'll try and enable all the config stuff it needs and get back to you :)

Sorry I've been quite guys, been very busy, then I log onto my virtual machine to find out that the git files seem to have corrupted themselves, trying to fix that now!
[Galaxy Note 10.1 (2014 Edition) Original Android D] DirkStorck:
Just have ordered the tablet and gonna try this kernel next weekend....The kernel I use for my phone has its own control app...so what app do you suggest to control the kernel?

Thank you!
[Galaxy Note 10.1 (2014 Edition) Original Android D] hitman1376:
Well ...

Dear friend , this is the only kernel at the moment ... I recommend you not to play with This tablet's kernel because it usually causes unsability but if you need to , can try many apps for CPU freq management can try many apps like ' SetCPU " or " No Frills CPU " and many others ... Good luck

With Best Wishes

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Original Android D] DirkStorck:
Ok. Thank you ....than I will stay with stock values of the kernel at first :)

One question. What is with "Colour Control" and schedulers? Any advantages in playing with these?