yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] zlazaar:
No, use another launcher.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] veekay:
Have there been any changes with the low charging power with any of the newer builds?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Ur_strom:
Great ROM, works fine for me and runs stable.

Nice work!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] deepu458:
hi OP [MENTION=8258181]8224Freak[/MENTION],

First i would like thank u for all the gr8 work u put on this. I recently came to know that LOS has dropped official support for all Nougat Devices. So in regards to this will there be any chance of you bringing an update for this device with any other rom? Would you be ok to share some thoughts about the future of this ROM?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Has anyone tried latest builds? I've seen that there are still nightlies being uploaded.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] jeffrey268:
sure thing running 08-03-2019 built with magisk and xposed, havent had any problems so far!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pn1fon1:
Hi, has anyone found a way to speed up charging in the latest builds? The battery tweaking section in deathly auditor is missing those options. In fact deathly auditor is no longer available on Google play anymore. Is there a way to force deathly auditor to show all options? Any help would be appreciated. Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] louvass:
I always had the same complaint with these builds, plus the lack of screen real estate on home screen. I went back to latest stock or try the marshmallow Rom up here. I don't feel there is much differences in the latest versions of android, just my opinion.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pn1fon1:
Well I had to install prime kernel to tweak battery options and adw launcher to customize home screen.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Ditto on the usage of ADW as a home launcher. I've used it for ages and I find that it works fantastically with this build. As for current builds, I've found this RR version to be the best as far as just how configurable it really is. I use it as a daily driver on two out of three tabs that I tend to.

;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] 22sl22:
If there's anyone else still using this tablet here's a few tips since I have never had flashing issues/bootloop issues:

Firstly make sure you have the latest TWRP since official is outdated, use the one from ShevT rom thread in this forum, it says for P601 but it works for P600 too.

Make sure you have the latest lollipop bootloader, first post is outdated latest bootloader is P600UBSDSB1 you can make this yourself (No need to reflash rom) or I can provide the separate bootloader file if anyone's interested.

Use the smallest gapps package you can find

Use greenify or anything similar to stop background apps slowing down the device, this is simply due to age and how old this tablet is by now
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pn1fon1:
Did you have any issues with battery charging?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pn1fon1:
Hi there. If it isn't too much trouble post a link to the latest bootloader as mentioned. My bootloader is P600XXUDQA1. Also did you encounter any charging issues with latest builds since the battery tweaking options in deathly auditor vanished. I flashed recently 20190306 built and the charging was very slow about 4-5% per hour. Flashed prime kernel to solve it with deathly auditor. Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] 22sl22:
Hi,

That bootloader should be OK since it's lollipop but I like to keep things updated in any case.

Charging has been slow, I would say around 10% an hour roughly but it doesn't bother me as I just charge it over night and get pretty good sot (around 5-6 hours).

Latest bootloader is here: https://drive.google.com/open?id=1EfstLSQPg8Kqe74zSwQFJQTnIESEyB8D

Recommended Odin: https://drive.google.com/open?id=12eil4En76V_qJqrzbykfXg46qkbwrSP4

Disclaimer: This is a bootloader file, proceed with caution if you do not follow instructions you could end up bricking your tablet

1) Power off your device completely first then boot to download mode (don't reboot to bootloader from power menu)

2) Start Odin as Admin and load bootloader file into the 'BL' also make sure to untick auto reboot

3) Ensure that your device is connected properly and shows blue colour above 'IDCOM'

4) Press START and wait for the process to finish, it will flash green

5) Reboot the device manually
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pn1fon1:
Hi everyone. I tried today connecting a physical keyboard to the tablet and failed. I successfully connected it to my phone so the keyboard is working. Can anyone verify that can connect a physical keyboard to tablet please?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RXT00:
If you or anyone else wants the deathly features back and a permissive kernel without using the old prime kernel, you can just extract the boot.img from the unofficial lineage 14.1 which uses the official deathly kernel and flash it in TWRP.

I'm not sure what's new but that kernel is still being updated, and I'm using it with the latest RR right now and it's working great.

P.S. If you're using Magisk, make sure to reflash it after you flash the boot.img
[Galaxy Note 10.1 (2014 Edition) Android Developmen] asdf002:
Cannot update my BL with your file.

figured it out, had to use key sequence to get into download mode to flash vs the twrp download mode way
[Galaxy Note 10.1 (2014 Edition) Android Developmen] haighpaul:
I know it's not always practical to do this but, for me, charging is much quicker when the tablet has been fully powered off.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pn1fon1:
Hello everybody, I've noticed that deathly auditor is no longer available in google playstore. I had to download it from elsewhere and I don't know if it's the latest version. Can anyone please inform me which version is the latest?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] veekay:
I've only ever seen version 1.0
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
System Sound Gone?

It seems that no matter what I do with current builds, I no longer have any access to even basic sounds. Alarms only vibrate even though they are not set to. And even trying Viper4Android, I might get sound access for a short time only. Otherwise, it's quiet as a tomb. I get only random responses when trying voice commandss in Google. Does anybody know of a "kickstart command" to re-initialize sounds on my tablet? Thanks. ;-Deano D
[Galaxy Note 10.1 (2014 Edition) Android Developmen] deepu458:
I had this kind of troubles when i use Viber and Google Duo app on the tab with RR. After using the above mentioned apps the system sounds will all be gone and until i reboot the device the sounds wont came back. Seems like there is an issue with sounds from chat or video calling based apps like Viber, Google Duo, Line, etc
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Can anybody suggest a way to simply reset my default sytem settings without a full system wipe? I've seen several suggestions mentioning accessing bootloader settings, but not on samsung devices. AFAIK, there is nothing wrong with my hardware, but my software is telling my sounds to mute. I have some diagnostic apps, but they don't offer fixes other than "sound settings are inactive". The "best" online solutions seem to all be YouTube videos that tell me how to "fix" the problem WITH NO SOUND! Sorta like an ad in the paper about reading lessons for the illiterate....?

;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
System Sound Gone? -Fixed!

My digging into our deep config setting finally found the culprit Just one buried random setting that was well hidden:

a default setting for the system was for HEADPHONE output!

Now, I just need to find out why one of my tablets is still refusing to fully flash any builds newer than Nov15th of last year. My other two tabs are both fine and on current RR Builds. The ONLY thing that was different was that I had tested other Lineage ROMS on the stubborn spare tab. So, I see it as some artifact from the Lineage installs is the source of the prob.

All newer build flashes end up in Boot screen loops of death.

Any suggestions, Frank. I'm stumped. At least for now.

;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Bracher:
Very urgent

Sorry but I don't know and don't found out where to activate signature proofing. Sorrry but I'm not used to RR...

Excuse my bad English I meant signature spoofing - it has to be enabled somewhere but I did not find out where

I have Signature spoofing enabled for microG but am unable to activate it for Pay Store (Phonesky)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
[MENTION=8258181]8224Freak[/MENTION] thx v much for keeping this going & all your hard work
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pn1fon1:
Hello to everyone still using this rom. I would very much appreciate if someone could help me with something. I've tried connecting a physical keyboard but the device does not recognize it. I tried a full wipe today but still the same. Could someone please try to attach a physical keyboard to his device and verify that? I need to know whether it is a rom issue or something is up with my configuration. Thanks in advance
[Galaxy Note 10.1 (2014 Edition) Android Developmen] snipersquad8:
I have just installed this ROM, so far it is looking good.

I am only using this to control Plex and act as a glorified TV remote (because it is Wifi only Android won't disconnect from Wifi on standby like it does on my cell phones)

The ROM is great in my current use case, but reading the thread I see all this about SPen not working without Magisk and the battery being painfully slow to charge.

So my question is this: what is the latest version of Magisk I can install at this point? The last mention of this was several months ago, so I want to make sure I don't ruin my fresh install.

And for the battery issue, is the solution still to grab a boot.img from an old LOS build? Or is the new build based on a better kernel with an adaptive governor?

Thank you all in advance
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
Personally I use the latest Magisk v19. as for the battery TBH I don't really have an issue with it. I would recommend using greenify & amplify with magisk xposed, it works gr8. didn't know there was a way to get the spen to work on this rom, perhaps u could elaborate on which magisk module you mean. I've tried Los cr droid & I keep coming back to this one.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] deepu458:
Hi OP & Everyone,

Thanks for continuing build support for this tab model, appreciate that. I mainly use this tab for video calling purposes with my parents abroad. generally i use apps like Whatsapp, Skype Lite, Viber, Google Duo app and with all these apps on this ROM i have 2 audio related issues like cant hear them loudly and at the other end my parents cant hear me properly. So is there any setting or magisk mod or anything i can tweak to make this work properly. Please help
[Galaxy Note 10.1 (2014 Edition) Android Developmen] asdf002:
Hey I had this problem too. My issue was related to the bootloader. I was flashing the correct bootloader but it wasn't sticking. Had to manually go in to download mode (power+up+home) vs going to download mode through power menu and flash the bootloader and then the new roms worked. Look at post #346.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] echohack:
Someone had thrown this tablet at the dump station, I was quick to grab it. Only thing broken was the tip of the pen, I was stunned by humanity for a bit. Been running this rom for 6 hours now and only one small bug I found was accessing magisk manager through the system settings panel causing a crash. Easily avoided by going to the app itself. Only remaining thing is to see how long the battery will last.

Thanks for giving us this.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Need Image File -I Think.

Thanks for the great info here. I've bascally come to a similar conclusion regarding the boot loop probs. I narrowed it down to something in the LOS build that causes it, as only one of my three tabs has the bl issue. And that was the ONLY one of them that had the LOS on it at one time! So, when I re-flashed current RR builds, they wouldn't "take" as you said.

I followed your link an re-read everything from it. But, my issue now is that my laptop has an only semi-functioning Odin barely working. While it DOES sometimes execute commands, it often does not show the proper output to indicate that the actually worked. I am aware of the need to use the keyed input commands for getting "deeper" into recovery, so I was tinkering with different builds to fix the ongoing bootloops.

IIRC correctly, a bootloader image file CAN be flashed in recovery, but I have no idea how to get that file from the .tar image in your link. Would that even work? Please core if I am wrong on this, but you give me hope that I can finally update my "loopy" tablet up to this current RR build.

;-DeanoD

-someone asked about connecting physical keyboards, and I have used several BT units with no probs. My fav is one from Indigogo that looks like an old type type writer. Other ones from Wish, work too.

-the other mention about lack on pen input puzzles me as mine all work fine on three tabs. I bought the Spen Command app and run it as well. Can't recall who I got if from right now.

-D2
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
[TQUOTE=asdf002;79549456]Hey I had this problem too. My issue was related to the bootloader. I was flashing the correct bootloader but it wasn't sticking. Had to manually go in to download mode (power+up+home) vs going to download mode through power menu and flash the bootloader and then the new roms worked. Look at post #346.

Thanks for the help with my bootloopy issue. It took me a while to beat my old laptop into running Odin to do the flash of the bootloader. The flash was successful,. but it made no diff for the bootloop. Now I am still stuck on a RR build from Nov of last year. When I try to flash anything newer, it all ends with the endless RR screen animation. Sorry it took so long to post, as I had a health scare a week or so ago. So, I am still in search of a fix for this mess. Tried, full wipes, format, and still I am stuck. Thanks again for the help. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] louvass:
If you have Odin running than get the latest stock rom and try flashing that not just the bootloader. Flashing the stock always get me out of these types of issues

Thanks for the help with my bootloopy issue. It took me a while to beat my old laptop into running Odin to do the flash of the bootloader. The flash was successful,. but it made no diff for the bootloop. Now I am still stuck on a RR build from Nov of last year. When I try to flash anything newer, it all ends with the endless RR screen animation. Sorry it took so long to post, as I had a health scare a week or so ago. So, I am still in search of a fix for this mess. Tried, full wipes, format, and still I am stuck. Thanks again for the help. ;-DeanoD[/QUOTE]
[Galaxy Note 10.1 (2014 Edition) Android Developmen] blazzer12:
Link for "Deathly Adiutor" on play store is broken. Please check.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ypple:
Thank you. It's wonderful!!

But I have a question. I always thought sm-p600's text is too small.

Especially a keyboard app I use, It's key-text is too small to identify. What's odd is that only a sign texts on each keys are small but the other texts on menu, setting and so on are fine.

Same app on my friend's sm-t700 is just fine though.

Both device has same resolution and same density you know.

So I guess there's some different text size setting in the system.

Can I import sm-t700's system text size setting on my sm-p600?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] JDuc:
Hey all! It's been a ling time since I've messed with flashing any of my devices. I am looking to update my note to a more recent version of Android but I'm running into issues.

Note 10.1 2014 - SM-P600 - wifi - Samsung EXYNOS5420, ARMv7 processor rev 3 - Universal 5420

Every time I try to flash a ROM via TWRP I get an error 7: Updater process ended with ERROR: 7

I rooted via CF-Auto-Root-lt03wifiue-lt03wifiue-smp600.

Installed TWRP Recovery - I've tried the latest (3.3.1.0) as well as 3.0.1.0 after reading a post where someone said you needed that version (it didn't change anything).

I've tried LineageOS-14.1-20199615, 2019518, and 2019511. I've tried RR-N-v5.8.5-20190613-n1awifi-Luis as well.

Because I don't have much to lose if I brick this tablet I was trying anything I could find in an attempt to learn, so I tried flashing a new kernel: Prime_N_V8.0_LL_P600_AMohseni76 but it just gets stuck in a boot loop after that. I can still get into TWRP so I'm pretty sure I can fix it...maybe....

I've factory reset and cleared the cache numerous times via TWRP, both before attempting to flash and after attempting to flash.

I'm sure it's just something simple that I'm not aware of since I haven't worked in this works in a very long time.

I do get the Recovery is not SEAndroid Enforcing, and after flashing the new kernel I get the Kernel is not SEANdroid enforcing. Am I right in my understanding that these lines show up any time you aren't running the stock stuff, so it's not something to worry about or try and resolve?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] louvass:
Are you using the newest version of TWRP?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] JDuc:
Yes: Installed TWRP Recovery - I've tried the latest (3.3.1.0) as well as 3.0.1.0 after reading a post where someone said you needed that version (it didn't change anything).
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
You're on the wrong Samsung bootloader. Flash to latest lollipop bootloader.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] louvass:
I would flash a stock rom through Odin to get totally back to stock. I don't ever flash a bootloader. Use Samfirm to download the latest rom, it's the fastest way to download it. There are links here just search for samfirm.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] JDuc:
Here's a rather newbie question: I'm trying to flash a rom so that I can update and run newer versions of apps. Won't flashing a lollipop bootloader interfere with that?

Thanks for taking some time to respond. I appreciate it.

---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------

Just so that I can make sure I understand completely: Are you suggesting that I flash back to stock to start over and then try and flash an updated ROM from there? Or just flash back to stock and run with it since I clearly don't know what I'm doing. :D
[Galaxy Note 10.1 (2014 Edition) Android Developmen] louvass:
Yes go back to factory using odin, search it here and it will explain how to do it. Or I can help you if you need Just private message me and I can send you some docs.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] JDuc:
I'm flashed back to factory. I'd still like to be on a newer version though. Should I just go through that process again for another rom? Lineage OS?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] louvass:
Sure install TWRP through Odin then boot to TWRP do a manual wipe of everything but you SD card. Be sure to have your Rom on the sd card before you wrote everything. See what happens.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Hey mate,

to avoid that issue you have to flash open gapps in a second pass. Reboot your device after flashing the rom, let it start and then reboot into recovery and flash open gapps (pico or nano version).

Then it works, but you have to change the language etc. manually.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] vincebay:
I thought it was mandatory to flash Gapps in same time than ROM to avoid any big issues later no ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Normally it is recommended, but it works in the way i described, because i did the same.

Trust me, that is the only solution. No issues here!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Jornwitt:
When you get the crash popup. Click on it to close it and immediately after, swipe down the status bar to go into settings. It takes some practice. Connect to your WiFi and then it works.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] vincebay:
Thanks for the tip, will try it if I get opportunity !*Right now I installed an other ROM*based on Lineageos and it works well so far :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
You should track the device trees from lineage https://github.com/LineageOS/android_device_samsung_n1awifi

https://github.com/LineageOS/android_device_samsung_exynos5420-common

The n1awifi tree in github.com/exynos5420 is outdated
[Galaxy Note 10.1 (2014 Edition) Android Developmen] 8224Freak:
Thank you ! I have change the sourcetree.

Frank
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Whoa!

Finally my favorite rom!

Good progress in rom development these days.. :good::good::good:

Many thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
The latest two builds don't flashing magisk automatically. Was it removed?

And also Safetynet isn't working anymore....
[Galaxy Note 10.1 (2014 Edition) Android Developmen] 8224Freak:
yes, magisk was removed from the rr sources. i have no information about this. Please install after flashing the rom with twrp. https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

i think today the rom s not compatible with Safetynet. See https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Galaxy Note 10.1 (2014 Edition) Android Developmen] 8224Freak:
i have fix the magisk issue. Some changes in the buildscript for rr.

in the next builds (from 05/21/2017) i will including magisk to the ROMs.

Cu Frank
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Ok, thanks. But on OP3 with RR N i have no issues with Safetynet.

Waiting for the next builds :D

update: Safetynet is working again on latest build!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] marcfon:
Is somebody else experiencing severe screen flickering in app that do more intensive graphic work? I did a full clean install of the 20170520 build and running LL bootloader.

But before updating to this rom I was running a January build of LineageOS and the flickering issue there was a lot less present. So could the flickering be cause by a kernel setting or something related to that?

Some stories online point to a faulty battery (connector). I still need to double check this.

Thanks!

Update

So I checked the battery connector like was mentioned in other posts and tightened it. It seems the the flickering is gone for now...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Latest 05/21, *edit 05/22 release works link a charme on kk_bootloder(Prime v7.4_kk), fast as heck and buttery smooth!:highfive:

And for those with lookscreen/quick settings weather issues, you need to change weather provider from openweathermap to yahoo.

It's changed for some reason...:rolleyes:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] 8224Freak:
I have enable autorotate lockscreen for T700/T705/T800/T805/P600 on my builds. Changes comming on 05/24/2017.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Are there any advantages in using KK bootloader instead of MM? Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yepp, you don't need to flash Prime_kk_kernels or kk_bl.img's each time when you upgrade to LL bootloader. Otherwise you need to flash above mentioned solutions to get it working with the old bootloader.