yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
Many reasons for that.

One is you do not have a VT_Enabled kernel installed (what version of Android are you running?)

Secondly you didn't run step 3.5 (if you're on Lollipop)

Thirdly you didn't extract the Config Files Folder (it's named "Linux") to the root of your tablet.

Which of those is it?

Like I said, even if you miss one step it does not work. Re-trace your steps *exactly* and it will work if you're on Samsung...
[Galaxy Note 10.1 (2014 Edition) General] danerrickcuba@gmail.com:
I'm running 5.1.1(maybe my kernel it's not VT enabled, and what's this though)

I ran step 3.5 successfully

The Linux folder it's on root sdcard, that's why copying xorg.conf command work

Everything actually ran well, I'm feeling that my kernel it's not vt enabled, I'm using p605!

Thanks for helping!

<<<New World Order (NWO)>>>
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
Yeah like I said you have to run the full guide, you can't jump steps and expect it will work.

Please re-read the "preparations" part.

I write clearly there that this guide is for P600. In fact that's what it reads

" Non-P600 guys should find equivalent kernel on their own (or compile one for their own usage)."

To make it run to P605 you'd have to find a VT_Enabled kernel... I'm sorry.

Thanks for trying though
[Galaxy Note 10.1 (2014 Edition) General] franzli:
In preparation for one day finally trying the framebuffer option, I am trying to compile a kernel with VT enabled. I have sort of figured out the basics, I hope, but I must be doing something wrong as my tablet doesn't boot with my modified kernel. In fact, even if I just compile my source without modification I get the same effect, so there must be something I am doing wrong.

I don't mean to hijack this thread, so let me know if you'd rather I open something separate [MENTION=3241008]Stevethegreat[/MENTION].

But I figured, since this method requires a specific kernel, questions about how to produce such a kernel are somewhat relevant, and maybe you have a quick hint for me.

I have tried [MENTION=4144316]joshndroid[/MENTION]'s source for temasek's CM12.1 (https://github.com/Joshndroid/android_kernel_samsung_lt03wifi/tree/cm-12.1), and as toolchains I have tried arm-eabi-4.6 and arm-cortex-linux-gnueabi-linaro_5.2-2015.11-2.

One specific question I have, is whether the choice of toolchain could be the problem? If so, could anyone recommend me which one to use/where to get it?

I am also not sure if my method of producing the zip for installation is ok: Essentially, I borrowed the zip from valexKernel and repackaged it with my newly compiled zImage file.

I will be trying out the new CM13 temasek from [MENTION=4144316]joshndroid[/MENTION], and might give compiling that kernel another try. But if anyone's got a hint as to what I'm doing wrong, I'm eager to learn!

Oh, and this is the output I get when running "make cyanogenmod_lt03wifi_defconfig", which I figure might be related - unfortunately, I don't know what values these options SHOULD get.
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
[MENTION=2431278]franzli[/MENTION]: That's alright by me. In fact if you successfully compile and boot a VT kernel for CM12.1 I'd be happy to include it on this thread.

As for the actual compilation, I think you should better ask kernel guys or joshndroid who actually maintains the CM roms. Compiling kernels is not my strong suite and I mostly employed [MENTION=5529656]xluco[/MENTION] 's help when I'd compiled the KitKat VT kernel. My understanding though (for what's worth) is that you're better off using the same compiler options as the ones that joshndroid uses (same flags, same setup). My experience that's the least buggy way to do it.

Lastly (if I understood it well) you have not tried my solution yet. If so, I'd suggest trying it first (nandroid backup your tablet, install stock Samsung -Kitkat is preferable- and follow my guide).

The only reason that I'm saying that is because this attempt is a work in progress and in need of many more fixes, sadly I lack the time to research them, so seeing for yourself if this solution fits your needs -I think- would be a good idea before starting to learn kernel compiling.

Just my two cents.
[Galaxy Note 10.1 (2014 Edition) General] franzli:
Thanks, yes I assume it would be best to try and ask [MENTION=4144316]joshndroid[/MENTION].

Yes, I haven't tried your solution yet mainly because the two brief times I tried the stock ROM, it seemed to restrict me in ways I wasn't comfortable (wasn't able to mount ext4 on external SD, couldn't set DPI and I guess some other stuff - probably works if you modify the whole thing, but with CM I got them out of the box) and I wasn't a fan of the Touchwiz interface in general. Since I'm relatively ok with the XSDL xserver version, my need for linux wasn't so big as to make me have a stock ROM. I'm still curious as to how the framebuffer option works, but only if I can get it to work on my CM system. Plus, it'd be nice to learn at least a little bit of basic kernel compiling, even if it ends up not working for me ;)

On a slightly different note, but relevant to Linux on Android, one of my main issues with my XSDL setup is the (lack of) mapping of the WIndows keys on my bluetooth keyboard. Android maps them as META_LEFT and META_RIGHT, as I have been able to figure out, but they directly trigger Google Now, so there's no way I can use them in Linux. I have found out how to change the mapping in Android, but mapping the keys 125 and 126 to SUPER_L or SUPER_R in /system/usr/keylayouts/generic.kl just breaks the keyboard (i.e. doesn't take input anymore). I can probably map them to something else that's free in Android and try to find a way to map that onto SUPER again - not sure if I can do it, and certainly quite cumbersome.

is there a way to get Windows keys mapped correctly into Linux with your method [MENTION=3241008]Stevethegreat[/MENTION]? Are they recognised normally as Super keys?
[Galaxy Note 10.1 (2014 Edition) General] priccis:
Tried your guide yesterday without luck in Lollipop. First I followed the mini-guide without success. Then tried with the first one and managed to get through it. One difference is that I used this command instead the one you provide at 3).

Everything great until step 11) LinuxCanvas + volume up. White screen... (tried pressing home)

I can SSH into it. Installed VNC and connected from computer. The OS is running.

I do have VT enabled kernel.

Any idea?

Edit: Running in LinuxDeploy I get blacksceen and this output:
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
The quick guide does not work on lollipop (first sentence of my first post), the main guide too if you don't follow all the steps and the preparatuon exactly. Retrace your steps.

If I were to think of a reason , either you gave no root permission to user android (step 3.5) or the image was not installed completely (step 2d)
[Galaxy Note 10.1 (2014 Edition) General] priccis:
The user android does have root permission, and followed your guide step by step.

When I run "startx" in Privilege Terminal I get the attached errors log, and when I run in Linux deploy now I get this error:

Note that Xorg.conf in /etc/X11 is the correct one (supplied by you)

In VNC runs fine.
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
Have you followed the "preparations guide?" (extracted Linux folder to the root directory?)

Honestly the only thing I can think off is that the image was not installed correctly. I refollowed my guide it worked, in both KitKat and Lollipop (I typically check it half a dozen of times before releasing a guide anyway).

Lastly I hope you're running P600, because small differences on other variants may be enough to make the guide non-operable.

If nothing else works, Remove Linuxdeploy ENV (settings -> Remove ENV) and just follow steps 2 , 3 and 3.5 and try to run it from LinuxDeploy (Start -> OK) ... do you get any image?
[Galaxy Note 10.1 (2014 Edition) General] priccis:
Yes, I followed every step you wrote. P600 with xluco kernel VT enbled (WiFi passwords bug).

Tried removing, updating ENV, debug mode. Tried everything (vnc doesn't work anymore)

Just deleted Linux.img to try from the beginning.

Will update.

Ps: Your guide is great, it is easy to follow and clear. I'm doing something wrong.

Update:

Started from the beginning. Reinstalled every app. Deleted the old Linux folder (from recovery, it said protected file). Put it back again.

Opened LinuxCanvas, pressed volume UP, then 'menu' key and the desktop appeared! I couldn't move the cursor with SPen, it was irresponsible. Tried killing and starting again, but LinuxCanvas didn't work. Rebooted, nothing.

Will investigate.

I can't even make vnc work now. I give up for today
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
Ooops just saw it (sorry). Yeah input events are taken directly from the kernel so everything works as if you had a dual boot linux installed. If you read the last part of my guide/tutorial you'd see that's one of the primary reasons that I chose this over XSDL, it's dozens of times faster and more responsive for typing. Unlike XServer XSDL which runs on top of android and uses the android stack for most things "my" solution runs directly on top of the kernel, so you have the exact same result as dual booting without actually dual booting (neat huh?). Of course we have many of the same problems to solve too (3D acceleration for one)...

Lastly, I understand you willingness to learn kenel compiling, but trying my guide first (to see if it fits you) would be an 1-2 hours endeavor at most (including nandroiding back to your setup after finishing). At least that's what I do before learning a new skill (see if I could actual have an immediate practical use of it), anyway whatever you do be my guest.

[MENTION=5754112]priccis[/MENTION]: I just saw that as well. If you followed my guide you shouldn't be able to VNC, I purposefully cut the VNC server so that to install an X Server. Have you done that? ( step 2b -> Select Components).

You can't move the mouse and the s-pen because their xorg.conf configurations are missing or are showing to the wrong event. Try not to to have them connected while rebooting (connect them after boot, in short follow step 1 + explanation).

To be fair I'm kind of perplexed why it didn't work for you, it's 15 steps (including the preparation), so there must not be many ways to do it wrong...

As for deleting the Linux Folder, again it's included in the guide too. It's Step 2 from my second post. I know it's a bit long to the tooth, but I think I have thought for most/all of the ways things can go wrong. The only way to not work is if one does not follow the steps exactly.
[Galaxy Note 10.1 (2014 Edition) General] franzli:
I finally got a round to try and compile a kernel with CONFIG_VT enabled for CM13.0, in particular, temasek's unofficial version - though I suspect it might work for plain CM13 as well. I'm attaching it in case anyone else wants to give it a try - in principle, it seems to be working, although I'm having some problems (see below).

I've got a few interesting problems, although I suppose it's probably one underlying problem. Like [MENTION=5754112]priccis[/MENTION], I cannot start the framebuffer from inside Linux Deploy - that is, I kind of can, but I get a black screen and the Linux Deploy console has several lines from the Xserver starting, the crucial one being as for [MENTION=5754112]priccis[/MENTION]: no screens found. (Ok, currently I don't get that message anymore, but still only black screen.)

With your Linux Canvas app, amazingly I managed to "boot" into my XFCE desktop and I can see that the framebuffer method seems indeed way more responsive than the xserver-app one. Unfortunately, there's the major problem that the screen flickers like mad between white and my linux desktop. So unfortunately not really usable in this state. I hope this is a problem that's easy to solve as I'd be eager to really compare the framebuffer and xserver methods.

After closing Linux Canvas, and actually even after stopping the chroot in linux deploy (the volume down button to un-chroot didn't seem to work), I got a flickering of my linux desktop over what I was seeing in Android. Initially it was large bits on the screen, then only in the status bar. Now it has totally stopped. So something seems to be going wrong with the framebuffer at some point.

Any pointers as to how I could solve this would be welcome! For the moment, I'll have to setup my system again for independent reasons, but will have a look again when I next get a chance.
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
My guide is for Samsung Roms. In Samsung Roms once LinuxDeploy takes the upper hand of the framebuffer it never let's it go unless and until you'd stop the chroot environment and/or give focus to an android app.

In CM -I suspect- things are different where both Android and chroot fight for dominance in equal terms. The solution (so that to stop the flickering) most possibly is to completely stop the android stack ("adb shell stop") and *then* start linuxdeploy ("...bin/linuxdeploy start") ... unfortunately that's not a method I'm willing to support as it completely kills the point of having linux on Android as I envisioned it in this guide (having it side by side , instead of actually killing Android beneath).

There is probably a work around which is going to allow that to happen without having to kill the android stack, but that's the solution to my issue "2" which as I have said I have very little time to investigate.

It's not that I don't want to support CM13 either, it's merely that it is very much is a work in progress and IMO not a daily driver, so there may still a lot of issues to be solved with the Rom before even attempting running Linux on top in a stable manner. Good luck with your attempts though, if you manage to make it run (probably by stopping the android framebuffer) I would link to your method in my main post.

BTW , have you followed my guide? If not you have not followed the step 2b, maybe that's why you're getting the flickering (force refresh framebuffer must be off). You can also try my quick guide for faster results...
[Galaxy Note 10.1 (2014 Edition) General] franzli:
Sorry, just realised I never replied to your final question. I gave up on trying to make it run on CM for the time being, as the Xserver setup sort of works for me. For the record, as far as I remember I had followed all of your instructions as far as aplicable (I've got my linux image installed on SD card, so some things are a bit different). I had to revert to Stock ROM now because I got a great bluetooth keyboard which inexplicably lags on all CM variants that I've tried on a number of Android devices (but not on AOSP or Samsung Stock).

Anyway, this may provide me with an opportunity to finally try out your framebuffer method for Linux, to actually compare what works better for my workflow. Will report back with impressions when I et to do that!

Right now, I've only got a brief question, which may stem from my ignorance with respect to stock ROM. Currently, I'm still running on XSDL xserver, but that shouldn't make a difference here. Essentially, I cannot use sudo in Linux, but when I try something like "sudo apt-get update" I get the following:

sudo: PERM_ROOT: setresuid(0, -1, -1): Permission denied
sudo: unable to initialize policy plugin

From what I could figure out on meefik's github, it's got to do with selinux being set to permissive. As I've never had this problem before, I'm not sure if there's something I need to do differently on stock ROM. I have flashed xluco's final kernel for stock 5.1.1, which should allow switiching to selinux permissive. And in Kernel Adiutor I have installed the selinux plugin and set selinux to permissive there. Still, I cannot use sudo in Linux, which is a bit annoying. There is a workaround which involves starting the linux container via a terminal emulator from Android as root (su; /data/data/.../linuxdeploy shell), but it's rather uncomfortable having to jump through all those hoops when you're already in the Linux chroot and have a nice console right in front of you...

Does anyone have a solution for this or can you tell me what I'm doing wrong? I kind of suspect that KNOX might play some role in this, but since I've never really used stock ROM, I'm not sure what role it plays.

PS: Sorry, just figured out it's actually already in your guide! A bit spooky to run as root by default, but alright...
[Galaxy Note 10.1 (2014 Edition) General] franzli:
Two brief questions:

1) I had a crash using the S-Pen xluco's final Z1 kernel. Could that be because of an instability of the kernel? s the kernel linked in this thread older and/or more stable?

2) A clarification question regarding the location for your scripts in steps 5-7 because I've got a slightly different setup than yours - not installed on the internal memory but an image file on the sd card for space reasons (texlive takes up quite a lot of space). Are these scripts called from inside the linux chroot or from Android? Do they need to be placed in a folder called Linux in the internal memory, or in a folder called Linux in the home folder of the Linux chroot?

Many thanks, quite curious to try this...

New: Ok, I flashed the kernel linked in this thread, hopefully it's going to be stabler.

I copied the xorg.conf into the linxudeploy directory as per the first step, but didn't do the steps in 5-7 yet because I'm not sure which are the right locations - and they seem not to be strictly essential to get everything started.

Now after a couple of tries, I got the desktop loading, not sure why, but it doesn't seem to start most of the time. I had to close and restart the canvas app a couple of times before getting there. Now, unfortunately, neither my bluetooth keyboard+mouse nor the s-pen allowed me to move the mouse or do any input (I understand the touchscreen doesn't work anyway for now). Not sure what the problem might be. DO I need to reconfigure something in the xorg.conf, or could it be the "Input device" setting in Linux deploy? That is currently set to /dev/input/event0

Any advice anyone? The higher resolution did look kind of nice, but won't help me much if I cannot input anything ;)

Also, I'll have to see if I can adapt to not multitasking with Android - without having been able to try it properly yet, the need to essentially restart the linux desktop every time I go over to android might be a bit of a hassle in actual use. But I'd hope to actually try it out properly before deciding on what works better for me (proper resolution and possibly being able to do proper scrolling with the middle mouse button on my Thinkpad bluetooth keyboard would seem nice...)
[Galaxy Note 10.1 (2014 Edition) General] diabl0w:
attempting this now... I know I am late to the party. I just got finished attempting my first time but by the end both linux canvas and linux deploy would give me completely blank screens. I think one issue is that I was using the latest linux deploy so commands such as the first one I had to use /data/data/ru.meefik.linuxdeploy/linux/share instead of /data/data/ru.meefik.linuxdeploy/files/share but I am sure there were also some other incompatabilities. I also tried the quick install post 4 method using the same linux deploy you did this time (1.5.6), but linux deploy gave me an error during install that it couldnt make an ext4 image... not sure why

[MENTION=3241008]Stevethegreat[/MENTION]
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
Yeah, linux deploy continuously change paths that's why I'm recommending using the one that I did in my guide (any other will probably not work). The reason it couldn't make an ext4 image is most probably because the path for it was not correct. Try using the one I'm giving in the guide.
[Galaxy Note 10.1 (2014 Edition) General] diabl0w:
when it couldnt make the ext4 i was using the same version that you were... however i found the solution. i ran in debug mode and found that since I was using his old linux deploy (the one you use) but using his new busybox (from the playstore) , the old linux deploy was trying to use a -t argument with mk2fs that is no longer supported by the newest busybox versions. the fix was to install 1.24.1 from https://github.com/meefik/busybox/releases

EDIT: woohooo! the quick install works... at least now i know it works I have more motivation to go through the long process again

EDIT2: spoke a little too soon... no response to spen input but at least im seeing the desktop

EDIT3: following full install procedure in post #1 and spen cursor control is working! everything seems to be working great except one major issue -- I am assuming to type we would use the Florence virtual keyboard but when I select that from the start menu my device freezes and then crashes and reboots... seems like a kernel issue. I may compile a kernel that is completely stock with VT commits as xluco kernels have tend to be very unstable for me in the past
[Galaxy Note 10.1 (2014 Edition) General] panyan:
this is an exciting and novel project - i like it :)
[Galaxy Note 10.1 (2014 Edition) General] diabl0w:
created a stock kernel with VT enabled but florence virtual keyboard still causes device to crash

EDIT: working now! i think i might not have changed the OS to wheezy so I installed whatever debian flavor was default on accident. Installed the proper distribution and now everything is g2g! thank you so much for the detailed guide! there is no way I would have been able to do it without that
[Galaxy Note 10.1 (2014 Edition) General] Stevethegreat:
Thanks for the heads up. Haven't had the chance to update the guide for almost a year now. I'll try to do so shortly given your notes. For the time being I'll add to the guide a link to the older busybox version and an up-to-date VT kernel (if you don't mind sending it to me given that my compiling machine is out-of-service).

Once Official LineAge OS gets more stable (and I'll turn it into my daily driver), I'll update the guide to support Android v7 ... that way we'd get support for 3 major android versions (Kitkat, Lollipop, Nougat) which IMO would be enough for most people.

Again, thanks for taking the time to see my guide after so much time.

edit: BTW the quick guide didn't work (probably) because it only works with Samsung KitKat, if you ran Lollipop it is not compatible. The reason is simple, there were some unresolved issues with root and Lollipop (ie ones that I had no time to get into), so you have to run as root at all times on Lollipop.

I do write quite clearly that the quick guide is only compatible with Kitkat though...
[Galaxy Note 10.1 (2014 Edition) General] aznsephyi:
This man Steve(thegreat) should be StevetheLegend
[Galaxy Note 10.1 (2014 Edition) General] diabl0w:
for the record I was performing this all on KitKat (using stockyROM which is stock kitkat without all the bloatware) so I am not sure why the quick install didnt have a responsive spen. So that being being said the kernel that I compiled is also KitKat. I will upload it here anyway since it will be more stable than xluco's (it is merely stock with VT enabled) so some people may prefer ... disclaimer: im not really a developer i merely followed many tutorials and studied patches to produce this kernel so flash at your own risk, although i dont anticipate there being any issues
[Galaxy Note 10.1 (2014 Edition) General] RazorBlisS:
Is this useful if I'd like to use Linux drawing apps with the wacom pen? Or is it not worth it over the Sketchbook Draw and Paint?

As this is the only reason I'm considering installing the app in the first place