yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Try setting SElinux to permissive, and install busy box

https://play.google.com/store/apps/details?id=stericson.busybox

---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------

For now you can use the KitKat bootloader
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Thanks for reply, but i already have busybox pro installed and it is not possible to set selinux to permissive with LL kernel by ZakooZ.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Sraichvold:
Maybe I'm missing something, but since we're stuck on the white LineageOS screen with the buttons we need off the screen, there actually IS something to be fixed. Or have you been able to flash the new official build and get past the white screen? And if so, share your process, please.
[Galaxy Note 10.1 (2014 Edition) Original Android D] panyan:
I just clean flashed this rom and I an getting the white LineageOS screen and cant do anything more
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
just wait for the fix
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
You can remove the setup wizard in TWRP...
[Galaxy Note 10.1 (2014 Edition) Original Android D] stowaway:
How?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
First mount the system, then go to advanced, then file manager, then navigate to system/priv-app, click on the SetupWizard folder and delete it, then reboot
[Galaxy Note 10.1 (2014 Edition) Original Android D] stowaway:
Ok, I will try. Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Deleting the SetupWizard will cause bugs related to hardware buttons, lockscreen and settings app. I don't recommend it.

I've heard that other landscape device users have gotten around the bug by rotating the tablet to portrait. I've not tested.

What I actually recommend is: wait for a proper build
[Galaxy Note 10.1 (2014 Edition) Original Android D] stowaway:
Do you know when will be released the next build?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Monday, unless if the build fails, which it probably won't
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
My current fix for the SetupWizard is not user-friendly but if you really want to do it, it should set you up for official builds permanently.

If you don't know how to use adb, this is not for you.

0. Have a clean flashed official build where you boot to the white lineage logo. Also, have LL bootloader installed.

1. Engineering boot.img (this forces adb to be enabled and have root access even when clean flashing)

https://drive.google.com/file/d/0B_qzEVl3qv8MMFoyOUJjd1ZrMnM/view?usp=sharing

Flash that boot.img in TWRP (in the install menu select Install Image, select this boot.img, select the 'boot' partition, flash)

This is for LL bootloader, KK bootloader will not boot this.

2.

When you boot to the white LineageOS screen, connect USB cable and run these adb commands:

adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 3

This forces portrait orientation, where the buttons show up. You can then complete the setup wizard normally and when you get to the homescreen you can unlock the rotation.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
SetupWizard has been fully fixed, next official build will include the fix
[Galaxy Note 10.1 (2014 Edition) Original Android D] Xdii:
For me, these adb commands did not work but

adb shell wm size # get original display size WxH
adb shell wm size HxW # set inverted ("rotate the screen")

And undo it after the welcome screen.
[Galaxy Note 10.1 (2014 Edition) Original Android D] jefftherider:
Do you know when the new lineage version will be downloadable ?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
https://github.com/LineageOS/hudson/blob/master/lineage-build-targets
[Galaxy Note 10.1 (2014 Edition) Original Android D] Anonymous9926:
Hi im new here.

im not developer, just user.

i have a question.

can i use air command with spen button?

If i cant use it, Is there a way to use the air command? (ex. apps or root)
[Galaxy Note 10.1 (2014 Edition) Original Android D] theophile2:
No. Air Command requires stock ROM.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Anonymous9926!

This is ported air command but i've not tried it on LOS7.1 because it is at least one year old. And I believe you need note buddy and/or cm spen add-on to fully work. But as I said, I've not tested!

But the other two mentioned apps will give you the most of the spen features and a few more. And if you are willing to pay, there are some extensions for extended screenshot and other features. There are also a few other spen apps in playstore which are made to work also on non-sammy roms like air command short-cut and spen toolbox.

https://mega.nz/#!jVtxzTaB!cHO3sgz9-O-PysVrGtybVD_63ZOiOcraR2Y6HXNUsYQ

Here's the thread:

https://xdaforums.com/android/software/app-app-samsung-devices-provided-stylus-t3000448

This zip contains a few apps which also work with spen.

https://mega.nz/#!rc80EQ5K!ca8MBm-i-sCyNkJ-ej_gp3MHS34bRWGnL2grPLVvCHk

And here is the thread if you want(credits to him):

https://xdaforums.com/galaxy-note-3/themes-apps/s-pen-alternative-apps-cm-roms-t3278363

I do not know how much of it really works but it gives you an opportunity to play with it...
[Galaxy Note 10.1 (2014 Edition) Original Android D] jsonder:
Using TeamViewer Android to Android remote desktop from my Samsung to my P600 running LineageOS, I get "remote device does not accept incoming connections". Then I see an authentication error. Any one have an idea on how to make this work? Controlling my tablet from my cellphone is a useful feature. Using VNC server/client is another way but not sure what happens when my tablet goes to sleep.

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

I also get "remote device does not support screen sharing" if I use quick support. Maybe there is a better tool?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
[MENTION=4810273]ZakooZ[/MENTION], [MENTION=6227169]mosimchah[/MENTION]

There is a new nightly build is it for ll bootloader or still for kk?

Thanks in advance.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
KK bootloader but like before you can flash the LL bootloader kernel.

I'll do a proper post when I get home
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Thanks for the answer! Could you also highlight in the next post what are the advantages/disadvantages of using KK or LL bootloader with the official LineageOS builds?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The advantages are really just being able to use the updated bootloader, that and continued support from the rest of the Exynos 5420 team. In case this wasn't clear very soon you will have to be on the lollipop bootloader for all of our ROMs
[Galaxy Note 10.1 (2014 Edition) Original Android D] ^tyrant^:
Where do you get the LL bootloader to flash?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It was explained a few pages back
[Galaxy Note 10.1 (2014 Edition) Original Android D] ^tyrant^:
Found it, thanks!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
If you're on LL Bootloader i recommend to try prime kernel v.7 for LL after flashing the rom, because AdAway and spencommand is working with it.

It is also faster and has better batterylife. ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] DirkStorck:
Where to get this "prime kernel v.7"? Thanks!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Here is the thread:

https://xdaforums.com/galaxy-note-10-2014/development/kernel-prime-kernel-p601-tw-lollipop-t3456312

For LL Bootloader: https://xdaforums.com/devdb/project/dl/?id=23366
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Don't report any bugs to us if you're using a kernel that we don't support, just letting you know
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Many thanks for the quick reply.

But I have a additional question.

Is there a way to make the bootloader.img twrp flashable(flash img to bootloader partition) or do we need inevitably a pc with installed odin?

I imagine the following, extract LL-BL_img.tar to LL-BL_.img and flash via twrp img flasher to bl partition.

I think some users like me, [MENTION=5482809]DeanoD[/MENTION] and other would really appreciate such a possibility because of our limited access to a pc!
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The bootloader isn't exposed to TWRP on n1awifi so it's not possible to flash it via TWRP, now it might be possible with FlashFire, but I don't know for sure
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Flashify shou be ok too
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey mosimchah!

Do not be offended. I don't think he wants to be rude as he recommended prime-kernel in your thread and call it better. Just uncared what he says in his youthful enthusiasm.

BTW,

I don't think prime kernel is noticable faster because it is mostly based on your work only with an few minor modifications and updates and battery runtimes up to 10h are also archivable with deathly kernel.

And deathly kernel really is the best kernel I've used so far on this device.

Hey, but no matter, I'll test it also and report later if there are worthwhile benefits.

I always like to have more options because diversity is the spice of life!:good:

Edit:

Thanks again! I will try flashify/flashfire when the first LL-only-bootloader-build is up.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
New official build is out:

20170302

Fix bug where SetupWizard didn't have buttons

Lockscreen rotation setting added to Display->Rotation settings

As such, official download page has been reinstated in the first post.

Known bug added:

The tablet does not reboot into recovery when OTA updating. This is not a dangerous as the device aborts before doing any changes to the system. It will be fixed ASAP.

Bootloaders

This 20170302 build is for KK bootloader. We are finishing tests on the move to LL bootloader, and we'll remind you of how to move to LL BL when the first official build comes prepared for it.

Why move to LL bootloader?

Make it so there's no reason to rollback to KK bootloader. This helps people in stock LL.

Better compatibility with future android versions

It has updated low-level firmware such as touchscreen/s-pen.

Kernels

You are free to use whatever kernel you like, but bug reports in this thread by users using 3rd party kernels will be ignored, and should be posted in the thread of the respective kernel instead.

Sidenote: The only reason why Aircommand does not work is because the kernel is SElinux Enforcing, which is a requirement for official LineageOS. This is probably fixable though.
[Galaxy Note 10.1 (2014 Edition) Original Android D] tonio14545:
what should I do if a I already flashed the LL bootloader from page 111? I flashed that with odin and then i flashed the LL kernel but the rom wont boot. it stays on a black screen. if I odin flash kk firmware will that get rid of twrp? i cant find a kitkat BL file
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
If you're getting stuck on a black screen then odds are you're still on KK bootloader, try booting with KK kernel
[Galaxy Note 10.1 (2014 Edition) Original Android D] tonio14545:
I managed to flash the ROM by just flashing the ROM without the Ll kernel. That's weird though because I know I Odin flashed the Ll bootloader and it said it passed. Is there a way to verify what bootloader I'm on?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Run in terminal emulator: "getprop ro.bootloader"
[Galaxy Note 10.1 (2014 Edition) Original Android D] tonio14545:
It says p600UEUCNI1
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
That's kitkat
[Galaxy Note 10.1 (2014 Edition) Original Android D] Judson1975:
I just installed the new linos 14.1. Now when I reboot my tablet (galaxy note 10.1 2014) it says kernel is not seandroid enforcing
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It just means you're on the LP bootloader, nothing to worry about
[Galaxy Note 10.1 (2014 Edition) Original Android D] Judson1975:
Ok, thank you
[Galaxy Note 10.1 (2014 Edition) Original Android D] Urich24:
Hi just wondering why the speaker makes crackling noises when playing a video?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Wrong bootloader rom combi. Seems you are on LL bootloader. Install kk bootloader or wait a week untill the first build with LL bootloader is uploaded.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Rolliger_Troll:
Lockscreen

Hi folks,

I'm new on LineageOS 14.1 and came from Stock 5.1.1. Installation worked well, but when I try to wake up the device by pressing the power button nothing happens. When I try the home button, the soft keys illuminate, screen is black and then appr. 5sec later the lockscreen appears. The delay prevents the unlock. If I try too many times, the device reboots suddenly.

I'm on LL Bootloader....

Thx for your replies.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hitman1376:
Hi there and Welcome to XDA !!! :good: ... About your problem , you might need to try a Lollipop compatible kernel ( As such problems usually occur when you use an AOSP with a kernel which is incompatible with lollipop BL on a Lollipop bootloader ). Have you flashed one ? If you haven't you can use Dear Zakooz's Kernel HERE or my Prime Kernel V7 HERE . your choice on this :o . I hope it helps

Regards

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Work perfect here
[Galaxy Note 10.1 (2014 Edition) Original Android D] siralsmooth:
Strange, I originally dirty flashed, had too many issues, went full wipe/format, fresh install, and the YouTube app crashing is still persistent.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Start from scratch and wipe internal storage too.
[Galaxy Note 10.1 (2014 Edition) Original Android D] siralsmooth:
That's not gonna happen, lol. If I'm wiping everything, I'll be changing the system to the flash friendly file system, or whatever its called and going that route. I like YouTube, but its not worth that much trouble. Maybe I'll pull a logcat/crashlog and see where it errors.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
F2fs has been causing a lot of issues, I don't recommend using it
[Galaxy Note 10.1 (2014 Edition) Original Android D] DirkStorck:
It was causing issues on all my devices... And I never could feel any improvement or benefit.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Original Android D] siralsmooth:
Thanks for the heads up about F2FS, was unaware of the issues with it, always felt I was missing out by not having it.

As for my wipes in between flashing, I do a full format of the system, data, cache, and any other related partitions. Aside from what might be left on the SD card Android secure folder, it's wiped clean. No stranger to this lifestyle, been with it since 2.3 when a Single core 1ghz was amazing, lol. So I ask only when I can't nip an issue. Usually it's something small.

And KitKat bootloader, I was on AOSP 5.0 the day it dropped, still have the overview video on my YouTube channel from a few days after it dropped.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Any ns on new build?

Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
The first rule of fight club is we don't talk about fight club ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] DirkStorck:
[emoji38]

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
I didn't know there was a new mod in town
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Yeah, should come as soon as it gets built and is declared ready for release ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
G8 news

I have some issues charging and powering off.

Not charging well. Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The charging issue is kernel related, I'll give you an updated kernel zip with the fix when I get a chance.

---------- Post added at 03:48 PM ---------- Previous post was at 03:24 PM ----------

Here's the updated kernel zip, it fixes the slow charging issue, and improves the ondemand governor a bit: https://www.androidfilehost.com/?fid=312968873555003350
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Does it also have the ir blaster fix?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It has the kernel side fix, but there's also a fix in the device tree that's needed. So you'll have to wait for a new build to have ir
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
You rock man,TKZ

Lets try it

Update: Usb charging not working but with the power plug it works, now lets see the speed
[Galaxy Note 10.1 (2014 Edition) Original Android D] cswann1:
Thank you!!!!

I want to say how grateful I am for this ROM. I had actually listed my Note 10.1 2014 on eBay last week...THANK GAWD nobody met the reserve. My tablet was horrible.....so laggy and slow...and every time I did a Clash of Clans attack the game would disconnect...every time. I thought "what the heck" and checked the forums and downloaded and installed Cyanogen 14.0 and GAPS and I am delighted with the results. Smooth and fast and Clash seems to be staying connected.

Words are great....but nothing says "thank you" like dollars......donation sent...I wish I could do more.

[IMG="Thanks again"]https://cdn.meme.am/instances/59349318.jpg[/IMG]
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Boy! Did I miss this forum start up? I went from Temesek's last build to this one, which was a bit unstable, so I went to Orion from there. My stupid question is: how the "heck" can I find what my bootloader version is? AND can I flash the KK BL without the stupid computer? My laptop has odin & such but it is a slow, unreliable POS and I trust it as much as I trust trump. The pros here must have a better way. I also have a "new" smp 600 running android 5.11 and I need to root it for my wife. Like, NOW!!<vbg> ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
If while listening to music I write, or share a photo on telegram, I have audio artifacts and sometimes freezes, having to restart.
[Galaxy Note 10.1 (2014 Edition) Original Android D] gmo18t:
installed last build from yesterday on top of KK-bootloader coming from latest LineageOS 14.1 unofficial,

Dalvic, cache, system and data partitions was wiped prior to the installation.

On the TWRP flash task I included recent "Open Gapps" and the LineageOS-Exta "addonsu" as well.

Assistent was working fine along with restoring my previous Apps from Google Account.

No issues so far during the first impressions :)

- GMo -
[Galaxy Note 10.1 (2014 Edition) Original Android D] siralsmooth:
I'm on one of the December CM builds and have that every once in a while. Definitely not kernel or bootloader in my case as it's KK loader and the kernel included. I'll have a blank screen with the soft keys illuminated. Tablet won't wake up, sometimes then reboots, or if I leave it and try again it'll be okay. Definitely a random bug that still seems to have hung on since CM if its in LOS.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey siralsmooth!

Without logfiles it is most probably impossible to solve such a random issue. You guys should install Syslog or any other logcat app and take a log next time the error comes up. You can shorten the logs by deleting older parts of the files and then upload it here so that the devs are able to look into.

It's just a tip if you are interested in solving the error in future builds!
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
How do I enable navigation bar as I could in the ROM before the official release
[Galaxy Note 10.1 (2014 Edition) Original Android D] siralsmooth:
Honestly, given I'm on a now defunct build, that no longer exists, rip CM, I really wasn't too concerned with it. And logging would be great, if the issue was consistent, but if the tablet is plugged in, it won't happen. I really can't say what combo causes it either, because is happens maybe once every week or 2, but to say the logs will catch it, tough call. Really seems like it's a kernel/processor lockup from too many apps running in the background and too low of a minimum clock speed. Whatever the case, I'll be updating this thing soon enough. However, the intent of my response was to say, definitely not a combination of wrong kernel/bootloader, as suggested.
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
Just noticed something. When livedisplay is on after sunset the UI slows down. Most noticable when pulling down notifications. I tried turning off livedisplay on off several times to test it. The difference in smoothness is clearly evident.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey amitabh15,

Open deathly adiutor and go to build.prop section than add the following line at the end of the build.prop file

"qemu.hw.mainkeys" without the checkmarks and add a "0" to the second line,

now reboot once and you have on-screen navbar enabled.

This were already answered many times, try search function next time.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ericfabreu:
Google is using a staged rollout for the assistant, so very few people have it right now. You'll have to either wait for about a week or enable it using the GoogleAssistant keyword when flashing your Google Apps package. You can read about that here: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options#enable-google-assistant
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I have followed the instructions ( ro.opa.eligible_device=true & and device= pixel xl) still doesn't work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ericfabreu:
That's really weird. It isn't necessary to edit the device line, but I doubt that that's preventing it from working on your tablet. Try flashing the latest gapps package again and make sure that you have a gapps-config.txt file in the same directory with the word GoogleAssistant in it.

Is your device using a language other than English? Or do you live in a location where the assistant isn't officially supported? These two things could be preventing it from working on your tablet.

Here's a screenshot of it running on my tablet. I was waiting to see if it would show up by itself, but reflashed the latest package with the gapps-config.txt file to make sure that it was still working:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
As I've already said you can't dirty flash official over unofficial and this is the last post I write saying this.
[Galaxy Note 10.1 (2014 Edition) Original Android D] k-semler:
I tried it out earlier, and while I like it, it keeps on force restarting, and it's impossible to wake up after it's gone to sleep. Yes, I was sure to do a clean install. I wiped **everything** off of the tablet, (no OS, no anything except for bootloader and recovery), the second time, and didn't install anything beyond the minimum gapps, the OS, and the su binary. I let it go to sleep if it would have the same results, and it did. Is there something that I can do to make it stable? Could my bootloader have something to do with it? My bootloader is version P600UEUDOK1