yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
TTL?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Wahffle:
I managed to stop this problem by disabling root access. Have you tried that?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Open gapps pico
[Galaxy Note 10.1 (2014 Edition) Original Android D] steveman29:
I have the latest version installed but microphone is not working!!! It should have been fixed in the previous version according to description. Am I doing something wrong?
[Galaxy Note 10.1 (2014 Edition) Original Android D] steveman29:
Yes I did a full wipe and then I flashed it.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey steveman29!

Try it again and wipe system also...

Have you tested with several apps that mic really not work?(Skype, .....)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
I have trouble with mic too, it works but audio is too low
[Galaxy Note 10.1 (2014 Edition) Original Android D] angus242:
I have Assistant working with screen on. I used Open Gapps Aroma (removed all CM products) and used this app:

https://play.google.com/store/apps/details?id=com.trivisionzero.getassistant

The old version of Get Assistant used to change your device name to "Pixel XL". In the newest version, I don't think it does (or maybe gives you a choice).
[Galaxy Note 10.1 (2014 Edition) Original Android D] uwdus:
I just upgraded from CM to LineageOS (latest version) by formatting data, system, internal storage to have a clean system.

Everything is fine but I can't find anything in settings to activate soft keys?

Another one (but was already on CM 14): I paired a Microsoft Bluetooth mouse. Even though pairing was no problem, the mouse doesn't do anything (in Bluetooth device options it is activated as input device)

Any ideas? Thanks :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi uwdus,

To enable navbar add the following line at the end of build.prop file (using DeathlyAdiutor)

Qemu.hw.mainkeys = 0

and reboot once. Voilá! Navbar! :good:

You can also make it more consistent and paste it into build.system but for this you need to browse the last few pages. [MENTION=6227169]mosimchah[/MENTION] posted a useful how-to if I remember correctly but a few pages back! In this case, it remains so long until you wipe the system partition.
[Galaxy Note 10.1 (2014 Edition) Original Android D] C0BRA01:
You do not need to download the stock ROM, the 2nd link you posted has a stock ROM in it with the KitKat bootloader. and his procedure re-partitions the devices internal storage. This was a big improvement even over the stock KitKat ROM. Save yourself time, downloading the stock ROM is a waste of time. Only download the repair zip that's posted in the 2nd link. Follow his guidelines, and only use the files in his zip file. Worked beautifully on my P600. Took care of the sound, and video issues better than just stock. Make sure you do a clean install after that, no nandroid restores.
[Galaxy Note 10.1 (2014 Edition) Original Android D] uwdus:
Thanks a lot for your detailed answer :) I did everything like you said but after rebooting there are still no soft keys :confused: I rebooted, then I tried powering off and turning back on but no success. The entry I made Qemu.hw.mainkeys = 0 shows up in the build.prop though.

BTW: Where is Little Colorado in Germany? ;)

[EDIT] Made it!!! The entry is case sensitive qemu.hw.mainkeys = 0 did the job :) Thanks again for the great help :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The build is almost done ? http://jenkins.exynos5420.com/job/2. LineageOS 14.1 Build/target=n1awifi/15/

Get it from here when it's finished http://download.exynos5420.com/LineageOS-14.1/n1awifi/

Edit: it's at 88% http://jenkins.exynos5420.com/job/2. LineageOS 14.1 Build/target=n1awifi/15/console

94%

99%
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The build is finished,

Mini changelog:

-I think root was removed so flash SuperSU

-Synced lineage sources

-Added qemu.hw.mainkeys=1 to the build.prop so if you want to enable the navbar just change that to zero

-Improved Samsung doze

-Updated the boot animation

Note: this build has not been tested by humans yet so make a nandroid backup before flashing, just in case

http://download.exynos5420.com/LineageOS-14.1/n1awifi/lineage-14.1-20170124-UNOFFICIAL-n1awifi.zip
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
I can confirm that root is no more present in latest build...

And the rom is not as fluid and smooth as it was before.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey COBRA01!

Both are the same repair roms. I've only stored it on my Mega cloud to give others a faster download option because the link inside the how-to is really slow.

---------- Post added at 13:23 ---------- Previous post was at 13:07 ----------

Upps,

it just copied and inserted and overlooked it was capitalized...

BTW,

Little Colorado is a tiny little secret village somewhere in germany, where smoking good stuff is legal, but it is so small you will not find it on any map. This is the same as with Asterix and Obelix, except we use magical steam and no magic drinks, Lol!:cool::cool::cool:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
First post has been updated with the new downloads page: http://download.exynos5420.com/LineageOS-14.1/n1awifi/
[Galaxy Note 10.1 (2014 Edition) Original Android D] muhgi:
Can you add the removal of root and the suggestion to flash SuperSU at least to the changelog on page 1? I'd suggest putting it someplace else there as well, as I think most people are going to expect a custom image to already have root.

Is there a reason root was removed, especially since Deathly Aduitor needs it for some stuff?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Root was removed in mainline LineageOS, it was their decision not ours.

As to why they did it: it improves security (and allows pokemon go to run...?)

We can re-enable but I believe the team has decided not to(?) We might in the future, in the meantime flashing SuperSU is not hard.
[Galaxy Note 10.1 (2014 Edition) Original Android D] uwdus:
SEHR interessant, ich werde Augen und Ohren offen halten ;) Sorry for Offtopic!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Cool34000!

Latest release is as smooth as the latest, at least for me. :p

Wait a moment after reboot from recovery until all background processes are completed and the CPU load drops... maybe 2-3 minutes then test again.

If you still have problems, it must be another issue, but it is not the ROM.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
I just found out that window animation in dev options was reset to default (by ROM update?)

After changing these 3 settings back to 0.5 and a reboot, it feels less laggy!
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Dirty flash here and all is fine
[Galaxy Note 10.1 (2014 Edition) Original Android D] jsonder:
No. Mic and playback audio does not work for Skype. I provided a log file 2 weeks ago. I was able to get headset playback audio working but not the builtin speaker on my SM-P600

---------- Post added at 06:38 AM ---------- Previous post was at 06:19 AM ----------

jsonder63
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Spontaneous shutdown when running KODI file scan on an SMB drive

I have updated yesterday to the latest version (clean install from Samsung 5.1.1) and so far I had no time to test everything. One thing I have noticed (like many others here) is that root is not missing, so a lot of apps are now completely useless: I am not so happy that Deathly Adiutor, GSam Battery Monitor extension, any proper backup app that works on rooted devices, TWRP Manager, BusyBox Pro are not working any longer. I am really unhappy that I cannot restore my Titanium Backup - since there is no root, the app does not start.

The worse I could see so far was that while running the file scan on KODI (files are stored on an SMB drive) the tablet shut down (on the old 5.1.1, KODI was working perfectly)

I will try today to test more apps and see how it goes...
[Galaxy Note 10.1 (2014 Edition) Original Android D] sylvainXDA:
Think you should try more... Kodi is working fine here! Iam also streaming from a samba share.

And as for root :Why not use supersu till the lineageos Team will release the root tool??

"We will NOT be shipping root baked into the ROM.

Root will be a downloadable zip based install similar to gapps installation (only need to flash it once)"

Gesendet von meinem 2014818 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
Dude, relax about the root. I only just started using the built in root of CM a few weeks ago and now I'll go back to flashing SuperSU as usual.
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Thanks, dude! :D I completely forgot about the flashing option. :o

---------- Post added at 01:20 PM ---------- Previous post was at 01:10 PM ----------

Thanks for the suggestion to flash SuperSU. It worked like a charm.

Comming back to Kodi, what to try more??? Which version of Kodi are you using? 17 RC3 or some older version? Did you try to scan multiple sources in parallel? Is the samba drive password protected? How many files did you scan? In the order of hundreds, thousands, tens of thousands?

In my case, the scan/Kodi crashed after it was scanning for several hours already (I went to bed after two hours and Kodi was still scanning so I cannot say precisely what happened). The strange thing is the fact that the tablet shut down (it did not automatically restart); could it be that the processor protected itself from overheating?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
You should probably clean flash then, or at least try wiping the system, cache, and dalvik cache and then flashing the ROM, Gapps, and SuperSU, that'll fix most issues related to dirty flashing, but if it still does not work then you need to clean flash
[Galaxy Note 10.1 (2014 Edition) Original Android D] ChenZ86:
You said you updated from 5.1.1. Did you go back to KitKat Bootloader like recommended?

When not: try that.
[Galaxy Note 10.1 (2014 Edition) Original Android D] papatasos91:
I cleaned flash latest and the previous build and still no mic! Any solution to this issue?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Florian_96:
I just cheke with the latest LineageOS Build from yesterday..

Still no bluetooth.

The new Liquideath build from yesterday works.

I downgraded to stock 4.4 FW following the instructions posted here.. no luck.. It seems to be working for other people.. so either I am doing something different while flashing or I do have different hardware. Is there any bluttooth diagnostic app or things I could do on the command line?

Best regards

Florian
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
AudioFX has been fixed, it should be in the next weekly build
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
Official Lineage!!!

Will this thread switch to official?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
That's for the QCOM variants, don't flash it!!!

We can only get official lineage if we can get SElinux stable on enforcing mode
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
hell, I had not noticed!! :eek:

So LTE version has SELinux working in enforcing??

Anyway I wouldn't flash it xD I prefer this unofficial, appreciate your work ??
[Galaxy Note 10.1 (2014 Edition) Original Android D] Vasishtha:
I'm really satisfied with the update to lineageOS, great work :)

Can anyone tell me how to disable the soft keys and or the home button?

I tried setting Qemu.hw.mainkeys to 0, it enabled my navigation bar however the soft keys are still active.

In Liquid death I can easily disable them in the button settings page. But in lineage I can only disable my recents button.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
To disable the keys you would have to add a "#" in front of the keys in this file: /system/usr/keylayout/sec_touchscreen.kl , the menu key is "key 139" and the back key is "key 158" then reboot

https://github.com/exynos5420/andro.../cm-14.1/configs/keylayout/sec_touchscreen.kl

Example:

# key 139 APP_SWITCH VIRTUAL
[Galaxy Note 10.1 (2014 Edition) Original Android D] epithetic:
I think they suggested adding a note to this extent to the OP, since people updating from previous (CM) builds might not know. I certainly didn't and was confused for a second until I Searched The Thread™ (since the dev option is still there, just disabled). As you said though, not a big deal.

Since it's been brought up, I can confirm the issue with certain text input fields not working properly with the pen; the chat input line in Hangouts is one example. Tapping it with the pen moves the cursor and can select things but does not open the input method (if you open it by tapping it with your finger instead, the actual text entry works fine with the pen).

One other oddity I've noticed with the current build is that I don't get any volume adjustment sounds, regardless of whether I have them enabled or disabled in settings. Audio itself seems noticeably better, and the option to boost it in the auditor is excellent.

All in all, fantastic update to LineageOS, everything else seems to be working smoothly and without any issue.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Vasishtha:
Thank you very much, worked like a charm!

Offtopic :

Expansive desktop or the navigation bar, lets split screen bug. App content of the left app(or lower App depending on rotation) gets shifted up /down (does not happen with all apps, but all app menu's do get shifted)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Added to downloads the LineageOS su (root) download: https://download.lineageos.org/extras
[Galaxy Note 10.1 (2014 Edition) Original Android D] ttocskcaj:
Audio clicks and glitches

I'm having issues with audio glitching and clicking. I'm pretty sure I have the KitKat bootloader already as it had stock KitKat installed before flashing.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey ttocskcaj!

This means by far not you are automaticly with KK bootloader! When even "once" a stock 5.1 Sammy update was installed you have LP bootloader even if you go back to another rom. You can check your bootloader with multiple apps. Read at least the last three or four pages and you will find all what you need, include how-to and repair firmware.:good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
Just did a clean install of the latest build, very smooth. Flipboard still has the closing issue for me.

Also, I bought Deathly Adiutor a while back, can I get rid of the free one somehow?
[Galaxy Note 10.1 (2014 Edition) Original Android D] DaveUK:
If you use titanium backup I freeze the pre installed version then install the paid version afterwards.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
I do use Titanium. Both are currently installed. I guess I can freeze the free one.
[Galaxy Note 10.1 (2014 Edition) Original Android D] NanDroider:
Maybe somebody can help me: I'm flashing the latest root tool from lineageOS site via TWRP (3.0.2.0) But no root. Now I wanna give latest SuperSU a try.

Is their anything special about flashing lineageOS-root? (Recovery --> Install --> Choose root-zip --> restart)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
Aftet flashing LOS's root zip, you simply need to go in devtools to enable it...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
This will work like the built in zip of recent times which I've been using and now I use this add on.

You need to enable developer options to enable the root access.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Since latest 2017.01.27 build viper4Android is not able anymore to install the audiodriver.:(

*update:

Forget it! The following version of viper4android is working fine:

https://www.androidfilehost.com/?fid=385035244224409796
[Galaxy Note 10.1 (2014 Edition) Original Android D] x61tab:
Any reason why its taking ages to download files using this ROM? What usually takes less than a minute to download is now taking 25+ minutes. Also, its taking me over 8 hours to charge the devices, with this ROM, from 49% to 93% ( what usually takes 2-3 hours to go from empty to full).
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
So, the video scalling issue has been fixed! Until a new build is made with the fix simply put the file that I linked into system/lib and set the permissions to 644 rw-r-r

And reboot

https://drive.google.com/file/d/0B_qzEVl3qv8MSXZlSmQzeFBPMDg/view?usp=drive_web

Majority of the credit for the fix goes to [MENTION=4925642]tincho5588[/MENTION] and [MENTION=4810273]ZakooZ[/MENTION]
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey x61tab!

I can not confirm neither the one nor the other.

All works almost perfect, now incl. video playback! :cool:

Check Deathly Adiutor> battery settings!

If you want a nice charging boost try maxing-out all entries like on the screenie below.:good:

And about download speed, it is usually depending on the server where the files are hosted or to your DSL contract.

Maybe try to change the wifi channel of your router or try the 5ghz band if available or, if this also not help, try to set another country code and reboot once.

In /system/etc/wifi there are one file called:

nvram_net.txt

Change "ccode=GB" to "ccode=US" or "ccode=all" and add "regrev=5".
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
I noticed very poor download speed when battery saver is enabled. Disabling it restores network speed
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
After going back to to KK bootloader and a new installation of the latest LineageOS zip, I can confirm that Kodi works fine. I could not restore my former Titanium backup (for a reason I cannot understand, the Titanium refused to see all apps in the backup and I had to reinstall again all apps from scratch).

Few problems I still see:

- No constant WiFi performance or WiFi management: I have 6 Wifi networks (thick walls), 3 on 2.4 GHz and 3 on 5 GHz and sometimes, when scanning for an WiFi network. the tablet refuses to "see" all of them or it "insists" on staying on a certain network even if I try to manually select a different one. After a reset, everything works fine for a while and then it starts again the same: "sees" only 2 or 3 of the 6 networks (some on 2.4, others on 5 GHz), sticks on only one network, no manual selection is allowed. Any idea?

- embedded videos on Facebook apps are "zoomed in". For each one, I need to lock the tab, and unlock it in order to see it correctly. Is there a solution for this?

- charging is very slow (using the same charger I was using with with Samsung stock ROM). I am afraid to play with DA settings because I am thinking that boosting there the settings might damage the battery on long term.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
To fix the zooming issue put the file that I linked into system/lib and set the permissions to 644 rw-r-r

And reboot

https://drive.google.com/file/d/0B_qzEVl3qv8MSXZlSmQzeFBPMDg/view?usp=drive_web, this should be fixed on the next build. Also, messing with the power settings on DA is perfectly fine as long as you don't go above 2550, personally I won't let it go above 2200
[Galaxy Note 10.1 (2014 Edition) Original Android D] hackurb:
Can you explain how to set that permissions exactly.i have searched for it but went over my head.i am usingvES explorer for root directory but dont know what 644 is or do things you said would fix my youtube videos to going out of frame. :(
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Thanks for the link, but i tested deathly kernel with latest cm 13 build by ZakooZ and by joshndroid and both roms stuck at boot with deathly kernel by mosimchah.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
Same Issue.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
That's because the ROM build is too old. Not much I can do about that
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
Well, hopefully Zakooz can update his kernel in his cm13 to reflect the updates that deathly offers.

Perhaps he's only working on CM14 though.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
- The deathly kernel is different for CM13 and CM14. They handle SEPolicy differently so each probably only works with the corresponding ROM version.

- The deathly CM13 kernel uses different GPU drivers which requires new GPU blobs. That's why it doesn't boot on my 0821 ROM.

If you want to use the latest CM13 deathly kernel with my 0821 ROM, you need to manually copy these files in recovery after flashing my ROM:

https://github.com/exynos5420/propr...-common/proprietary/vendor/lib/libmalicore.bc

to system/vendor/lib/libmalicore.bc

https://github.com/exynos5420/propr...on/proprietary/vendor/lib/egl/libGLES_mali.so

to system/vendor/lib/egl/libGLES_mali.so

I'm no longer supporting my CM13 because I don't have the disk space to keep both source codes at once and because joshndroid is working on his CM13.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I gave them the cm13 deathly kernel, that's the one that didn't work with your cm13 build.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
This method resulted in bootloop or blank screen after clean flash of 0821 ROM. Thanks for the response though
[Galaxy Note 10.1 (2014 Edition) Original Android D] ammarr:
Doesn't joshndroid's CM13 already have the dealthy kernel? See screenshot
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
Indeed it does, although not fully up to date. I enjoy Zakooz cm13 though. I can't get the updated kernels to flash on either.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Right, even with the new vendor files the device doesn't boot with latest deathly kernel.... damn.

I am tired of restoring the system from my slow sd card, so i will stay on cm 14 for now, because of the much better performance and battery life and i hope it will be updated soon with the ir blaster fix.

Big thanks for that nice rom, ZakooZ.:)
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
Well, back to our regularly scheduled thread ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] risant:
is the camera working now?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Nope, not fully!

It opens and shows a preview but is not able to safe the pics to sdcard.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Thanks M.,

no need to build an unofficial release, at least for me, Lol!

If it's possible, I will try to install it by myself by copying gello.apk to system_apps, create a gello folder(drwxr-xr-x) and give it proper permissions(-rw-r-r--). But maybe I will stay with cm14 because of it's awesome battery life, Lol! :cool:

(See below:

Darkness governor, 150-1900mhz, no issues)
[Galaxy Note 10.1 (2014 Edition) Original Android D] sarceneaux:
What issues did you have with running this on a LP BL? I bought my tablet with LP on it already. There are some things I can live without that some consider must have...

I may have to let the devs do their things for a bit to see if anyone can make it work for us but I was really hoping to put this version on my tablet and be done flashing
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
BTW Netflix working good.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey sarceneaux,

With lollipop bootloader you will get some weird issues like crackling sounds and other ...

You have to flash a kitkat release in order to get kitkat bootloader.

Here is an easy how-to:

http://xdaforums.com/galaxy-note-10...cial-build-t2980604/post65631142#post65631142