yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi etmflde,

you always flash roms on your own risc, so don't blame anyone with utterance like (thank you!). Thank you!

First, gapps will be updated over playstore, no need to flash it every time, unless you wipe also system partition while upgrading.

Second, I have not encrypted and I would not try it unless you know your recovery is compatible and fully working with encrytion.

And twrp is able to see sdcard also some file managers like ES are able to see sdcard content. As far as I know only a few apps like TB are not able to do.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ChenZ86:
And I'm lost with that here.

Is it still needed to tweak the LL bootloader with this odin stuff or can we stay on normal LL bootloader from Stock 5.1.1.

It figuered out that the swap from KK to LL bootloader and unofficial to official is confusing me very much.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ViRuS-MaN:
i just update with trwp and it s ok but yesterday when i update with trwp my tablet crash and i need to installe 5.1.1 for after install this rom , i dont understand that but now it s ok

but some time when i start my tablet after loading my tablet crash dont now why
[Galaxy Note 10.1 (2014 Edition) Original Android D] Az Biker:
* * * Thread Cleaned * * *

A few things:

1) I seriously doubt a user who starts with "sorry my english is bad" is going to proceed to insult the dev/Rom. It is MUCH more likely he was asking if a fix was a joke because it doesn't work for him. Regardless, let's hope for the best, especially when a language barrier is present

2) Even if this user WAS intentionally being disrespectful, which is obviously a violation of Xda rules, ALL the Off-topic responses are equally in violation of Xda rules. IF a user is causing trouble, or being disrespectful, simply hit REPORT, otherwise you run the risk of being in violation just as they are.

3) rather than jumping to the conclusion that a user is being a jerk, especially when a language barrier is involved, ask for clarification of the comment/question before passing judgment, just as you would want someone else to do if your comment/question came across in a manner you didn't intend.

Let's get back to the development for this device, and stop the off-topic comments.

Your cooperation is appreciated.

tl;dr Don't jump to conclusions, be kind and ask for clarification, report violations of rules- don't engage, keep comments on development.
[Galaxy Note 10.1 (2014 Edition) Original Android D] epithetic:
Is anyone else experiencing mini stutters/hangs with brief, intermittent bursts of audio playback?

Updated to official with the recommended bootloader, and while audio playback itself works perfectly (none of the old crackling issues) I've noticed that when brief samples are being played, such as volume adjustment or touch sounds, the system itself seems to randomly stutter for a second. It seems like it's waiting for the sound to be initialised and played. One way to reproduce this is quickly lowering/raising the volume a couple times - eventually it will 'stick' and the system will hang for a fraction of a second, then the volume adjustment sound will play (correctly) with delay and everything returns to normal. I've also seen this in games, where the game will briefly hang to 'catch up' with the next sound to be played.

This does not happen when there is continuous playback - for instance doing the above while music is playing will never make the system stutter; volume control stays responsive and the audio likewise remains perfectly smooth and steady. As far as I can tell there's no difference whether AudioFX is enabled or not.
[Galaxy Note 10.1 (2014 Edition) Original Android D] k-semler:
I play GTA3 fine on my tablet, and I notice no issues at all with sound lagging, even changing radio stations rapidly while shooting the gun in the game. Now if I could fix my SD card issue, it would be awesome. (I already formatted it to EXT4 just incase it didn't support exFAT).
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
I removed the 20170309 download because all official builds should meet minimum standards of quality

The issue was related to the functionality that disables hardware buttons if the on-screen navbar is enabled in Settings->Buttons, the setup wizard crashed when trying to prompt the user if he wants on-screen or software buttons.

Next week's build should have the issue fixed - it will also bring back the "on-screen navbar" option to Settings->Buttons.

If you happen to have 20170309 and want the fix for the issue now, you can download this and flash in TWRP by selecting "Install Image" from the Install menu, selecting that file and "Boot" as the target partition
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Did anyone get Magisk with Safetynet support working on this rom? I flashed latest magiskSU 11.1, but no success with Safetynet.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Az Biker:
* * * Thread Cleaned * * *

For the second time today, users in this thread are disregarding the rules, continuing off topic comments, and ignoring the warning to simply report rude, troublesome users instead of engaging them.

If this continues after two separate warnings in the same day, infractions and account actions will be taken.

This thread may also be closed should it become a constant source of violations.

If your comment doesn't contribute to the development of the Rom, do not post it.

Do not engage rude/disrespectful users. Report them.
[Galaxy Note 10.1 (2014 Edition) Original Android D] rayik:
Thank you for posting the fix file.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Yepp, it's already reported!

We have to wait for a fix. The devs mentioned earlier their are working on a fix for that issue.

Maybe one of the next builds...:good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] k-semler:
Sweet. :) That's literally the only thing keeping this ROM from being RTM quality. Except for not being able to read and write my SD card, the ROM is actually better than Samsung RTM.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
This ROM is far from better compared to Samsung's stock! Better battery life, up to date Android, no crapware pre-installed, better performances... And since November unofficial release!

What do you mean by not being able to read/write from sdcard? I have no problem with mine.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
TB cannot backup to ext sd for example. Folders and card not writable. Appmonster too. It could be the apps who knows?

Long time issue. Doesnt bother me too much compare to all we got with this rom.
[Galaxy Note 10.1 (2014 Edition) Original Android D] jerrys0828:
I've had bluetooth issues on both Official releases. Devices are rarely show up and don't connect. In a public place with dozens of active bluetooth devices, the tablet will show none. If I toggle airplane mode on and off and then some of them may appear, but if one of those is my paired keyboard I still can't connect with it.

Bluetooth is working in other ROMs, so it doesn't seem to be HW related.

This is my only issue, this is an amazing ROM. Very stable, SD working, and overall much better performance than I was getting on stock!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Yuyiroquai:
Hi, i'm a bit lost.

in which order must i do the installation?

- Wipe all (except sd card)

- Bootloader with Odin

- Rom 20170203

- Kernel

- Gapps nano

- Root

Thanks for the rom and all the collaborators, you will give a second life to my tablet :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
That works
[Galaxy Note 10.1 (2014 Edition) Original Android D] Yuyiroquai:
Thanks for the reply and your hard work :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Try making TB a system app, that fixed it for me. You can use this to make it a system app: https://play.google.com/store/apps/details?id=de.j4velin.systemappmover
[Galaxy Note 10.1 (2014 Edition) Original Android D] jsonder:
The only thing I'll add is you need the USB drivers for the SM-P600 from Samsung: http://www.samsung.com/us/support/downloads

I used my Win 10 laptop to do this procedure with no issue. I guess I am ready now for the new OS's that are coming:cowboy:
[Galaxy Note 10.1 (2014 Edition) Original Android D] calaiou:
Hello, after two installation with problems I reinstalled this rom with another kernel and for now I have no worries, why it is not specified that it should be replaced , sorry im with google trad.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
20170302 is for KK bootloader so you can

a) flash LL bootloader then flash https://www.androidfilehost.com/?fid=529152257862703996 to make the ROM work on LL bootloader

or

b) keep kk bootloader for now and only update bootloader when the next build comes out

It's called nightly because that's what all official builds (in every device) are called right now, it's not something that I control
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Any comments for a launcher for this Rom? Was using Google now, but it was causing stability issues. Switched to a Pixel launcher and it seems to work well (and looks like my pixel phone)
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Nova launcher is great
[Galaxy Note 10.1 (2014 Edition) Original Android D] juancarlosarenasm:
Sometimes when I try to unlock it, it just takes 1 minute. Other times it restarts automatically. Is there any function I should disable to avoid this problem? like deactivate the pin-lock? Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Get a logcat for starters...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Kirzai:
Which kernel did you use? I'm having several problems that are reportedly fixed in this release - the worst of which are sound pops, intermittent crashes, and slow unlocks.
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
I went back to the latest official Samsung ROM for Lollypop 5.1.1 (installed with Odin), rooted it, installed TWRP and after that installed the 0309 LOS rom and the latest nano GApps. So far, I have absolutely no reasons to complain about this ROM.

Some very few apps are crashing and restarting some time, but I do not see this as a major issue (it might be also due to the fact that these apps are not adapted yet for Android 7.1).
[Galaxy Note 10.1 (2014 Edition) Original Android D] makimikel:
I had the same problems with the Rom 2017/03/02 until I flashed the zip of kernel post # 1291. I have 3 days without reboots, normal unlock and the tablet goes smoothy. Before the install kernel be sure that you have LL bootloader.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Having the same problem with Nova Launcher as I did with Google Now Launcher. Works for several hours then crashes repeatedly. Tried rebooting, cleaning cache and Dalvik and problem returns. No problem with Pixel Launcher. What is strange is I have been running the ROM for several weeks and the problem just showed up a couple of days ago. Will update the ROM and bootloader as soon as the LL is released and see if the problem goes away.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ChenZ86:
What is wrong with the standard LOS-Launcher Trebuchet?

I'm using it the first time with the tablet now but i like it a lot because of simple but useful features.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Anonymous9926:
Pressing the multitasking key with fingertips works normally, but there is no response when you press it with the s-pen.

Is this normal?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Kirzai:
Ok, thanks for the heads up. I'll look into this.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
You got permissive....
[Galaxy Note 10.1 (2014 Edition) Original Android D] Kirzai:
Ok, near as I can tell I'm running everything as expected.

BL_P600XXUDPL1_LL.tar.md5

kernel-n1awifi-cm-141-LL-bootloader

lineage-14.1-20170302-nightly-n1awifi-signed

open_gapps-arm-7.1-stock-20170305

addonsu-arm-signed

The only thing I'm not certain of is the TWRP version, as I couldn't find one specific to the n1awifi - I chose the lt03wifiue. Is this correct?

twrp-3.0.2-0-lt03wifiue.img

(Though I see there is a new version, 3.1.0-0, out as of last week.)

I also used a newer release of Odin (3.12.3) but I don't see that as relevant

Did I miss anything or install a wrong package somewhere?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
So.....

If Prime is using enforcing Deathly can too. We just haven't switched it for development purposes. SELinux denials are fixed device side so.......
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
No, deathly is on enforcing, and prime is on permissive for lineage. For LD deathly is on permissive too.
[Galaxy Note 10.1 (2014 Edition) Original Android D] makimikel:
I think that You're correct in package and in twrp, i have the same.
[Galaxy Note 10.1 (2014 Edition) Original Android D] calaiou:
Ok I just understand, deathly adiutor must be installed and activate on each category , for some people is not automatic to understand that it is necessary to make a modification kernel or gpu. We are not all pro like you but we are interested !!! In any case, big respect for your work , In writing I realize that I can not move the cursor to write with the s-pen, is this a known problem? On this I do not bother you anymore, google trad:crying::eek:

I spoke too fast, I reinstalled kernel prime v7, issues
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Kirzai,

try twrp from shevt it is also 3.1 and what is the best, it works¡ :good:

https://xdaforums.com/galaxy-note-1...p601-lineage-nougat-galaxy-note-10-1-t3546012

---------- Post added at 22:46 ---------- Previous post was at 22:28 ----------

Hey calaiou!

Read the first page carefully!

There is no need to set anything in Deathly Adiutor. Rom works fine with stock settings. Deathly/Kernel Adiutor is only a kernel tweaking app like EX Manager, you can use it if you want but you do not have to.

In fact, kernel tweakers are some of the most powerful tools in android world since they allow you direct access to the hardware settings.

So use it with prudence! And do not enable "set on boot" option(upper right corner switch) unless you are sure your settings are stable. If you per example OC the CPU to 2100mhz and reboot option is enabled you can run into a bootloop. So use it also with prudence.

You can "PM" me(pers. message) for some rockstable profiles I'm using if you want because this is not directly related to rom developement. You only need to copy and paste it in the related deathly adiutor folder and benefit, easy peasy...!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Expected changelog for this week's build:

Stability:
- Fixed issue where SetupWizard would crash on first boot
- Fixed issue where macloader (WiFi mac loader) would always crash
- Probably fixed issue where WiFi would drop and reconnect (never happened to me so no way to test)

'Officialization':
- Kernel now supports Lollipop bootloader by default (Kitkat bootloader won't work any more)
- The menu button now actually acts as a menu key (not a recent app switcher)
- LineageOS devices should always use the same key layout as stock ROM
- You can change the behaviour of the menu key in Settings -> Buttons -> Menu Button
- This fixes inconsistency where the s-pen would activate the Menu button but fingers would activate the Recent Apps switcher
- On-screen software buttons can now be toggled in Settings -> Buttons
- As expected by LineageOS, enabling this option disables the hardware buttons

Bug fixes:
- Probably fixed issue where voice recording quality/volume was very low
- Fixed issue where powerhal was not getting the correct kernel nodes
- Probably fixed issue where NTFS and EXFAT SDCards were not getting read
- Partly fixed issue where the ROM wasn't rebooting into recovery when OTA updating (this most likely requires a fix to the recovery too)

SELinux:
- Probably fixed issue where 3rd party apps weren't able to read S-Pen input

Battery life:
- Enable s-pen power saving mode by default (this change was lost in the major device tree rework)
- Disable kernel input boosters by default (powerhal should handle boosting)
[Galaxy Note 10.1 (2014 Edition) Original Android D] dr. killjoy:
You posted the changelog, but don't see the ROM posted in the repository. Do they only get posted on Thursdays? I apologize if this was answered somewhere else, I didn't see it. Thank you for all the hard work you put into this ROM!
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
I've tried dozens of vastly different launchers over several tablets. Nova and such were pretty good, but I always seem to gravitate back to ADW for it's ability to let ME create my own UI experience. It was stodgy at times but always rock solid Their recent revamp to vs 2.0 has only made it better.

And I am a very picky old fart as far as what I demand in a user interface with any software. Just MHO ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Yes, it's only on Thursdays
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Was trying to have a launcher similar to my phones Pixel launcher (similar / same interface)
[Galaxy Note 10.1 (2014 Edition) Original Android D] k-semler:
Will I be able to dirty flash over the existing install, or will I need to wipe and re-install?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Read my FAQ https://xdaforums.com/showpost.php?p=70320987&postcount=3
[Galaxy Note 10.1 (2014 Edition) Original Android D] ViRuS-MaN:
why it s not possible to install directelly after the tablet are download the update ???
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Our device isn't currently compatible with the Lineage ota app, it's being worked on though
[Galaxy Note 10.1 (2014 Edition) Original Android D] ViRuS-MaN:
ok i wait for it s ok , when i install the update after download i need to install superuser in the trwp , it s normal ???
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
If you want it, yes! No su in all official LOS roms, it's removed by default. You have to flash it separately and there are three options to do it, SUsuperuser, pph's/magisk or lineageSU. Choose what fit's your needs!

---------- Post added at 18:57 ---------- Previous post was at 18:42 ----------

Somebody tried to flash bootloader.tar via flash fire/flashify with success?

My USB connector seems definetely been broken and the device will not recognized, neither by Windows nor by Odin, neither in normal, download or recovery mode.

Need to buy a new one but thought be me, I should buy a new battery too. Now that we have official LOS(finally) it's worth to invest a few bucks more.

Somebody with a good source for both, battery and usb connector?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
Updated to latest build... So far, so good!

OTA is still not working, so you'll have to manually do the update.
[Galaxy Note 10.1 (2014 Edition) Original Android D] x61tab:
Got an error during the installation of the current version. Will try downloading again.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I am now going to try yesterday's release. I am moving from KK 3/3 official. I understand the directions to update the BL, but don't understand the next step. I assume that I boot to recovery and then flash the rom? Or should I flash the rom in ODIN while updating the BL? My plan is to do a "Dirty Flash" as I am moving from official 3/3 to official 3/16. Thanks.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Boot to recovery and flash the ROM.

You can dirty flash between official versions
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Make sure you are on LL bootloader and it should work!

BTW,

there is no way to flash the bootloader.tar or stock 5.1.1 incl. bootloader without Odin unless you are on stock KK/4.4.2 and update via OTA or manually using stock recovery.

Flashfire or Flashify are not able to flash files to protected partitions like the bootloader partition. [MENTION=4810273]ZakooZ[/MENTION],

Is there maybe another way to flash on protected partitions or is a new usb connector in my case unavoidable?
[Galaxy Note 10.1 (2014 Edition) Original Android D] gavilan2010:
Do the home button wake the tablet now... with the new updated.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
It's working and has always worked for me!
[Galaxy Note 10.1 (2014 Edition) Original Android D] k-semler:
Is PocketODIN an option? I have Linux on all of my machines, and as far as I know, there's no port of ODIN to linux.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
You can use heimdall instead http://glassechidna.com.au/heimdall/
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
The problem is, that my usb connector seems to be broken.

When I connect it to my pc it installs no drivers and windows says, usb connection is broken. Also odin don't see the device and there is also no debug message or connection options shown in notifications.

It only charge the battery but nothing else and then I have searched for a way to flash bootloader on samsung devices without PC/odin/heimdahl.

But Samsung has saved the bootloader to a protected partition and none of the "mobile" alternatives like FlashFire is capable to overwrite such partitions.

And before someone asks, Samsung usb driver are installed, no Kies leftovers and when I connect another device(S2, OP3) it works fine.

So it seems I really need a new connector to fix it.
[Galaxy Note 10.1 (2014 Edition) Original Android D] k-semler:
Thanks. I got it installed, but I need to get a PIT file.
[Galaxy Note 10.1 (2014 Edition) Original Android D] epithetic:
Have you tried Koush's universal adb driver?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ^tyrant^:
did a dirty flash over the	lineage-14.1-20170302 release, and when it goes to boot it just sits at a black screen.. do i need to flash a new bootloader for the	lineage-14.1-20170316-nightly release?
[Galaxy Note 10.1 (2014 Edition) Original Android D] epithetic:
Yes.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Thanks epithetic,

will try it and report later if it's working.
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
With the new ROM some of the videos in Facebook app are not properly scaled unless you go watch them in full screen mode.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Everything work with no issues. Had to add qemu.hw.mainkeys to build.prop to get the buttons back. Also like others have posted seeing "kernel is not seandroid enforcing" on boot. Had this with many rom and devices and it has never been an issue. I'm sure it scares many people that see it for the first time.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
[MENTION=4174709]ollimi1[/MENTION] I can't really offer support for your issue, I've only ever used Odin

Enable navbar in Settings->Buttons instead. The seandroid enforcing error happens in most devices, it's just indicative that you're running custom firmware.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Added a FAQ under the first post: https://xdaforums.com/showpost.php?p=71482456&postcount=2

Mostly stolen from [MENTION=6227169]mosimchah[/MENTION]
[Galaxy Note 10.1 (2014 Edition) Original Android D] Anonymous9926:
I want to share a file with my smartphone but Wi-Fi Direct is not working and only Bluetooth.

WiFi Direct is only a connection and can not use the sharing function.

Do not use Wi-Fi direct function?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Okay, need anyway a new connector, have him already on my shopping list together with a new battery. Exchange seems to be relatively easy, maybe 30 min. and lots of helpful vids on YT.

But I have to wait until the parts are here ...