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.
[KERNEL] valexKernel [SM-P600 | CM13/AOSP 6.x ]
- Thread starter Andmoreagain
- Start date
-
- Tags
- exynos5420 kernel lt03wifi sm-p600
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
Guys take this discussion to a new thread or PM, because this is very off topic.
Sent from my SM-P600 using Tapatalk
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.
Last edited:
@Andmoreagain:
I would very much like to test your kernel but unfortunately your sources are dead.
Can you update them please?
I would very much like to test your kernel but unfortunately your sources are dead.
Can you update them please?
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.
New builds are up for both P600 and P601!
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:
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.
Using V3 is it the last test version?
Sent from my SM-P600 using Tapatalk
Sent from my SM-P600 using Tapatalk
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.
Is there any specific tweaks that make the battery last forever?...hihihi.
It seems to be saving more battery during sleep, and as of the latest update it should also charge a bit faster.
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.
Looks good at first. Need to try more Spen. Thanks
Sent from my SM-P600 using Tapatalk
Sent from my SM-P600 using Tapatalk
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!
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.
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!
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.
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone