yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Not yet, but I plan on adding support for P601 as well. :)

In other news: I have resolved the bootloop issue. When the kernel is installed in such a way that only the kernel itself is replaced instead of the entire boot partition, the ROM will not bootloop. I assume it's because the boot partitions differ slightly depending on the ROM such as that a Temasek boot.img won't work with BrokenOS etc.

This here should work regardless of the ROM in question. Tested and working normally on BrokenOS: https://drive.google.com/file/d/0B7Ui4IHpV48JV0Q5el91X3ljVXc/view?usp=sharing
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
So this would be good to go flashing on Temasek's?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Yes
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
Running your kernel. Antutu score puts it about 200 points less than the stock Temasek kernel.

It feels snappy though, I'll continue running it to see what happens.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
That may well be. I did the Antutu benchmark twice and got some very different results each time. The second time it outperformed stock. I guess these benchmark apps aren't all that reliable in the end.

You can also try tweaking some settings with Kernel Aduitor or a similar app. I have KSM turned on with its default settings and LMK set to very aggressive. Then I'm also finishing up and testing the next release which includes all the custom IO schedulers, BFQ being my personal recommendation (I'm actually surprised it hasn't been mainlined yet).
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
I'm mirroring your settings now. What's funny is I'm trying to see if the Note 10.1 2014 works as my note taking device for college. I was using Windows tablets before and dual booting Android-x86. I'm kind of spoiled after running Android natively on Core i3/i5/i7; it's just so smooth and fast on those processors.

Only reason I'm trying to use the Note 10.1 2014 is because the size/weight is absolutely perfect.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stevethegreat:
[MENTION=4979112]dimex[/MENTION]: Core i's come with the notable downside of added weight and low(er) battery life. I was just using Xperia Tablet Z4 and I can confidently say that we already are there (a tablet as smooth as a laptop only with a fraction of its weight) but in our tablets a lot of it eclipsed -sadly- by the bad drivers on one hand (lack of documentation from Samsung's part), lack of optimized software (if you're using TW rom) and of course the hardware itself is 2 years old already...

Anyway, back on topic: [MENTION=5617466]Andmoreagain[/MENTION]: Are you still working on 8 core support? Especially now that you've got the switcher and power management to work? Or there are more pressing issues currently? I think there are boards (like ODROID-XU2) running Exynos 5420 with fully functioning core migration...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
True, but an active digitizer is a requirement of mine. The Note 10.1 seems to be the only option on the Android front with one. If there wasn't AOSP ROMS for this thing, I would've never purchased one.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
The Nvidia shield has one.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
Way too small for actual note-taking, and if you have any experience with pennable tablets, the Shield's capabilities fall right on par with Synaptics, which is crap. Technically the Shield doesn't even incorporate active digitizer technology.

Only true options are Note 10.1 / 12.2 / Wacom Companion
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Guys take this discussion to a new thread or PM, because this is very off topic.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Yes I am. However, even though the switcher will probably work with the 3.4 kernel there is still a problem with device tree support. In order for this to work properly I would have to rebase the kernel on either the ChromiumOS 3.8 branch or continue my work with the 3.13 branch based on Linaro Stable Kernel.

I've been experimenting with both and I kind-of managed to merge in 3.8's support for the exynos5420 platform, but device tree support was still too messed up and gave me some werrors that I just couldn't resolve. It particularly had to do with the clock drivers and the CCI driver as DT support is just too incomplete in 3.4. Otherwise the board files and drivers compiled just fine.

Since I've already begun adding necessary support to the 3.13 branch I think I'll just stick with that one. I'm just searching for a developer that would be willing to port over the display driver since that's the biggest hindrance here and I'm not skilled enough to do it myself.

I'm not using the upstream MCPM code in my main release yet, though I did figure out a way to add partial support for it with the stock switcher at some point. Thanks to my terrible organizing skills I just can't remember if I actually kept this implementation on a separate branch or if I accidentally discarded it somehow. I'm gonna try and see if I can do it again so I can test it. If all goes well then it will be included in the next release.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SamsungGalaxySamsung:
Thanks for all the hard work!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] calj17:
Please do it for p601

Enviado de meu SM-P601 usando Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stevethegreat:
[MENTION=5617466]Andmoreagain[/MENTION]:

I would very much like to test your kernel but unfortunately your sources are dead.

Can you update them please?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Yeah sorry, I renamed the repo. Been busy with school over the past weeks but I'll update the links right away and post a new build sometime in the coming days.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
New builds are up for both P600 and P601!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pictorul20:
Man, you are the best. the only thing we-re missing is overclock support. In rest, i cant complain at all u really did a great job.Keep up, you're awesome :highfive:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Yeah works well on temasek's rom
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
I've come across a bug that causes the device to freeze up after a while of using the s-pen (sorry bout that). I haven't found out the cause yet, but it will be fixed in the next update. Otherwise, everything seems to be working as it should.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Using V3 is it the last test version?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Not really, there's just this one s-pen bug that needs to be resolved. I'll post a patched version as soon as I get to the bottom of it.

Until then, as long as you don't use the s-pen a lot then there's no harm in using v3. If you must use the s-pen I'd suggest going back to latest v2.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] buhohitr:
Is there any specific tweaks that make the battery last forever?...hihihi.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
It seems to be saving more battery during sleep, and as of the latest update it should also charge a bit faster.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Also, updated with a potential fix for the s-pen bug. So far so good, but one can never be sure lol. As always, let me know if you guys encounter some buggy behavior so it can be fixed ASAP.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Looks good at first. Need to try more Spen. Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Well, at least I managed to complete a drawing in ArtFlow without a freeze so I'd say this issue is more or less resolved. Before it would freeze up after only drawing a couple of lines.

​

I still don't know what was actually causing it, just that it had to do with the upstream "namespaces" patches. I'll probably apply them later on and test them one by one to find out which one of them is the actual culprit. Maybe it's a simple matter of a missing include of uidgid.h in some of the wacom files, I don't know...

Anyway, I'll be stepping into a more experimental territory now. Now that a relatively large part of the kernel has been updated to Linux 3.7+ I want to see if the Mali GPU drivers can be updated to r6p0-02rel0. That's the version that's present in the ChromeOS 3.8 kernel and it's very possible that the chromebook's platform support for Mali T6xx also works for our tablet since they both use the exynos5420. Only one way to find out! :p

On a side note, I'm also trying to see if it's possible to get the open source GPU drivers to work. I've already managed to cross-compile libdrm_exynos with the ndk, and now I'm doing some work on the Lima driver for supporting GLES, EGL, etc. based on a port someone made for the Odroid-XU3. I think it would be pretty cool having an open source alternative on android for Exynos/Mali, just like Freedreno for Adreno GPUs. DRM/Lima isn't really complete yet, but at least the source code is out there and can be improved as long as someone is willing to put some effort into it.

I'll let you all know how this eventually goes :cyclops:

====== UPDATE ======

The new Mali kernel drivers compile now, but it seems like ARM haven't provided the corresponding userspace libs on their website. In other words, this update is not of much use at the moment. I sent them some feedback though and requested the correct libs. Hopefully they will make them available sooner or later.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Hmm, the s-pen is still causing occasional freezes so this is not just because of the user namespace. It's not as frequent as before though but I remember these sorts of freezes occasionally happening with stock kernels/ROMs as well. Maybe it's just that Samsung's drivers are poorly written, I don't know. It's very hard to tell what's causing this since I haven't made any changes to the wacom/spen drivers, and both logcat and dmesg aren't being very helpful either. :eek:

Although this isn't as much of an issue in v3.1, it still irritates me to the bone. I'll find a solution or die trying, so I guess I'm off then to compile a build with every single debug option enabled lol. I won't be making another release until this buggy behavior has been fixed for good.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Can you describe what freeze, spen, windows or tablet and you have to reboot? Could it be framework issue?

Yeah.... got the same.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] r4yN:
I was wondering... since you're having problems with HMP/GTS (f*ck samsung and their lack of support), maybe In-Kernel-Switcher (CPU migration) is the way to go?

Looking at the wikipedia-entry on the big.little architecture, IKS appears to be a simpler approach (with 4 virtual cores and per-core switching). It might not be as powerful as GTS (you're still limited to 4 cores max), but it should be a lot more power efficient than the current cluster-switching (with per-core switching, independent core frequencies and the ability to shut down unused cores)

IKS is said to be part of the Linux 3.11 / 3.13 kernel and iirc you said you were backporting linux 3.13 features, so maybe it's worth a try?

https://en.m.wikipedia.org/wiki/ARM_big.LITTLE

(i could be totally wrong on this, I'm not a developer)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Maybe stupid question but does this mean we are currently not using 8 cores? ?☺
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Right
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Hm didn't notice that ? is this because of this kernel or general problem of AOSP? ?☺
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
You have only been using four cores alternating even on TW. AOSP developers are trying to fix this.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Thanks for the info ? and the work ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tarasque174:
I tried this on Temasec ROM and I like it better then the stock kernel. Tab feels quicker and more responsive now. Battery life seems to be better also. Been running it for 2 days now.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mikmock:
No issues with rubber tipped stylus

Before you go into Bug Mode I would like to chime-in & advise that I once removed the s-pen just to see what it looked like, stuck it back in & never touched it since. Recently I began using a standard type rubber tipped stylus for basically checking little boxes and keyboard accuracy & have never had an issue what-so-ever, of coarse i have absolutly no artistic talent when it comes to drawing so this maybe of no importance to the issue.

Additionally...

IMHO your work on the Valex kernel is outstanding :good::good::good: and its compatability with Temasek is most excellent (excluding the drawing issue which i too would believe falls more on a Samsung driver issue than your kernel). Hopfully you will squash the s-pen bug quickly & be able to concentrate on the Linux/kernel mods. :)

Good luck in bugland, thanks for your awesome kernel work & where is your "Donate" link? (you will surely need beverages while hunting) ;)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
It must have something to do with the memory management (mm) updates. It's basically on par with Linux 3.7 at the moment, though a few things are still in 3.4 territory. I'm going to try to sync mm and arch/arm/mm completely with 3.7 and see if that fixes the issue. Otherwise I'll just have to hard reset the branch to an earlier point in history and do more frequent testing between the cherry-picks and merges.

The whole area of memory management is probably the most sensitive part of the kernel when it comes to making changes to it, but then again these are all mainline commits. It's a bit strange how it's only affecting the wacom/s-pen input drivers. Most likely the culprit is just one single commit that needs to be reverted lol.

Unfortunately I don't have much time to maintain my kernel at the moment since I just started my first semester at uni (multimedia) but I'll fix this as soon as I find the time to go through this.

As for a donation button, I should definitely arrange that. For those who are hungry for true octa support then I'm also working on a bare-bone kernel project based on Android's 3.14 kernel branch (gonna try migrating to 3.18 later on since it has better support for our SoC). I've pulled in most of the core drivers needed for booting, but porting over the LCD display driver is posing an issue because it's a territory that I'm simply not familiar with. A co-worker just got me in contact with a programmer who's willing to take a look at it but he expects some payment in return.

The ultimate goal for the new kernel is also utilizing its multiplatform support. That way, the same kernel image could be successfully flashed on literally any Exynos5420-based device. Maybe I should just start a new thread for this and cross-post it over at the Tab S/Note Pro/Note 3 forums as well...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Sounds like a plan?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Also this: https://bitbucket.org/sigma-1/valexkernel-lt03wifi/commits/branch/V4-dev

I was testing out a small MCPM/octa core hack last night from the 3.8 ChromeOS kernel where I appended to the zImage a minimalistic dt blob describing only the eight cores and the CCI. It boots into a black screen and gets no further than that.

One thing I noticed by looking at the 3.4 exynos5410-smdk5410.dts file was that it also contained some i2c nodes, which I left out in my exynos5420-universal5420.dts. The display and touchscreen are connected via i2c so maybe that's the reason for the display not working correctly once it got past the bootloader. I'm going to throw together a more comprehensive dts and dtsi files to see if they make any difference. Even though the device drivers don't have OF/ DT support, the i2c's themselves seem to support it and maybe they even rely on it if the build is configured with DT support.

At least the DT blob compiled this time. Last time I tried something similar the dt compiler just came up with some weird syntax error.

Maybe this is something worth exploring a bit further, or maybe I should just move on and put my entire focus on my 3.14 development tree once I've fixed the s-pen/mm issue with valexKernel.

Backporting is generally easier than forward-porting, but if I'm going to spend more time on this whole MCPM nonsense I'll probably end up in a mental institution haha!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Regarding this, if we are going for a full board-file-to-device-tree migration and a newer kernel version there are some things that need to be taken into account as far as Android itself goes, and it has mostly to do with the GPU userspace drivers.

On one hand we have these: https://github.com/sigma-1/libdrm_exynos

But libdrm is not enough for full open source GPU support. There used to be a project trying to accomplish full hw acceleration with Mali GPUs but I'm not exactly sure if it's still operational.

On the other hand there are the proprietary drivers from ARM, but they haven't really provided any userspace drivers for Android on their website, only the fbdev/X11 variants for Exynos 5 dev boards running standard Linux distros.

The kernelspace drivers are hard to integrate properly but the version currently implemented in my 3.14 tree is r4p0 and it has platform support for exynos5420 (Arndale Octa) thanks to the Linaro guys. The userspace drivers are still missing though so that's something that needs to be resolved.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] legolas93:
Hi. I've just bought P600 and i'm waiting for it to arrive.

Yours seems a really interesting work. :)

Maybe i will try to help you.

(Mmm..No, as now I don't think i can port the LCD driver :p eheh)

But i've got some questions:

- V3 is based on v2.0 - RC2 or v2.0 - MCPM-testing? If it based on v2.0 - MCPM-testing, are stability issues solved?

- V2 is good for SPEN? Maybe i can help you in finding the commit that need to be reverted..

And the last one for now:

I read that you are trying with Linux 3.14. seems we cannot use stock Mali driver. Is this correct?

Seems a bit of a problem.. Did you do another test with MCPM/octa core hack from 3.8 with i2c bits added?

PS: Which ROM are you testing your kernel with?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Any way to have Fsync off? Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Koserman:
Your kernel is running flawlessly on Temasek's V16.2. Thank you very much!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Nevermind

---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------

The latest version is 17.0
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Koserman:
I haven't updated to the latest version which is why I specified what version I was on.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Kpod:
Not bad. I'm running latest Temasek, found CM great but something was royally messed with sketchbook pro performance. So not wanting to go back to stock, I tried out this kernel. Profit! Can't wait to see what else is coming downstream.

Here are my benchmark results, close.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Has anyone tested Temasek 17.6, on f2fs formated partitions, with Valex kernel 3.1 on p600?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tarasque174:
Not yet but I'm about to flash the new update from Teamsec
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
I do run 16.7 with this kernel on f2fs and all great for now
[Galaxy Note 10.1 (2014 Edition) Android Developmen] arses:
Hey guys,

Can I flash this kernel over my original 4.4.2 rom ?

Thanks in advance

HTC ONE ULTIM8
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
No, I would not do that. You have 4.2.2 and I guess touchwiz. This is for 5.1 AOSP.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stevethegreat:
Interesting.... I get an error trying to compile the "crc32" file

I find it interesting because back in the day (I think it was v2 of your kernel) I could compile it with no issues or warnings.

I've used both the toolchains you have on offer and my own. They both give me the same failure...

edit: False Alarm. I reverted to Ubuntu 14 and suddenly everything worked. Ubuntu 15 has a looot of work ahead of it...

BTW thanks for your great work my good sir :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
[MENTION=2451335]arses[/MENTION]!

Nope, take Xluco's kernel instead. It is for touchwiz roms and works amazing!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] buhohitr:
Hi , can we have a kernel for LP 5.1.1?? Thanks.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
LOL. This is for AOSP 5.1.1 already.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
[MENTION=5617466]Andmoreagain[/MENTION] Hi, are you planing to update your kernel or release a new kernel that works with cm13?

Thank you! Really like your kernel!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
I'll be doing a complete overhaul of my kernel at some point. My old crapple laptop just can't handle builds anymore and my PC got flooded with water in December because of some idiotic cannabis-growing accident on the floor above my workplace lol. Built a new one recently though, just haven't had any spare time for haxing around with the kernel yet. Been too busy with other things in my life. I'll get around to it sooner or later though. Sorry bout the wait.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Hi, thanks! No problem! take your time....everything is still in early stages...don't wanna say that the ROM can't be used. It can be used perfectly! :D
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
No problem. Nice to hear that you are still there. I don't know if you already seen that, but joshndroid is releasing CM 13 builds. It would be great if you maybe could release a kernel for CM 13 or maybe support him because we still have to fight with this damn spen bug. A second problem is, that we have no stable TW 5.1.1 kernel with permissive rights. I think you have the skills to release one simple stock kernel with permissive rights without much efforts. If you find time to do that, it would be really great. Otherwise no problem. I only wanted to mention this because we have not much developers anymore for this.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirtyOldDagger:
I flashed the latest version using twrp on sm-p601 but after the device logo appeared. I get I black screen and I go back to the device lolgo again .
[Galaxy Note 10.1 (2014 Edition) Android Developmen] hitman1376:
Dear Friend , What ROM are you using ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirtyOldDagger:
Using official Indian Rom5.1.1
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
This will not work on stock.