yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Lost Root

I tried running the OTA update with this ROM. Updater allowed me to indicate the zip file for Magisk to be added, but then would not run the install. So, I went with a quick wipe of cache and did a dirty flash, including beans gapps & Magisk 13. Everything seemed to run OK, and Magisk Manager works. But everthing else I run says that I don't have root.

What did I miss other than doing a full wipe (which I am probably overdue for)? ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] uToTMeH8:
In magisk manager open settings. Enable apps and adb. May need to restart the application or reboot.

Is anyone having issues with hangouts force closing once starting to type? I'm able to quick reply through notifications but not the app. This happens on any lineage based rom. I've tried different keyboards. I used open gapps stock, haven't tried any other package.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Thanks. This setting was already checked in MM settings. Tried it on and off and reebooted. Still no root. Redid dirty flash with cache and sytem wipes. Still no root. Will retry with last experimental release. It's no big deal, but I have rarely lost root. At least not without a different FoulUP at the same time. Just seems odd to lose root. Might also be from beta Magisk 13. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] uToTMeH8:
I didn't try the beta, so that could be it. Uninstall it then reflash magisk and try the stable app. I think I was using prime kernel too. Worth a shot
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey DeanoD,

In most cases, if you have flashed Magisk and have no root after rebooting, another reboot solves the problem! This is a known magisk issue.. Try it before trying something other...:highfive:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] sToRm//:
Did it...

- Full wipe with TWRP

- Flashed prime 7.4 LL

- Flashed ROM

- Flashed GApps

- Wiped Dalvik+Cache

- Reboot

= Holy ****! Yeah! But... ahm... no root.

- Reboot to recovery

- Flashed Magisk 13 bundle

- Reboot

= Yeah! Love it!

Absolutely perfect ROM, no bugs, no lags, all smooth! Thank you!

Camera is working (had no luck with Resurrection R) perfect with this ROM. Magisk is working good. Noooo problems so far. I am really in love! :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I ran everything the same way that you did aside from a full wipe. No matter how or when I flash the Magisk install pack, I have no root. Magisk itself runs fine and show everything working, but when I try to open superSU, it shows as not rooted. My guess is that I'm gonna have to jump in with a full wipe. SOMETHING is causing this prob. You said gapps meaning the Beans gapps from the OP? I just feel like it's something I'm missing. Like this: I've been having probs with Google Play SHOWING available updates to my installed apps, but would only show "download pending" even when I lost root! So, I searched for a newer version of Google Play and the prob was solved. Withing a few minutes ALL my updates were downloaded and installed. Sometime "thinking outside the box" means getting out of the one you are in.

Sorry for the rant and thaks for the help. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I ran the full wipe and reflashed everything. And it has gotten me back my root. Sorta. It seems that the version of superSU that Magisk installs came with a few bugs. Losing root was one of them. AFAIK the powers that be are working on a fix. But, for no I have my root back! ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] sToRm//:
I am glad to here that. Yeah, it seems to be a small bug in Magisk or with recovery. Sometimes (with other ROMs) I had to wipe twice, too. But so far no problems with this ROM. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] _nicolas_:
Hy.

First of all thanks for this role mosimchah. I am coming from stock lollipop TouchWiz and I really like your rom. I think it's a lot smoother then the official lineage rom.

I just have two questions:

* What is best method for giving apps full control of external sd. (Mounted as media not as intern) APS like Plex can't write to the ext sd card. I already looked at the permissions and I think does are fine.

* Second question is. What app of setting is best used for using the s-pen or hand writing.

Manny thanks in advance
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
I personally use squid and one note for writing
[Galaxy Note 10.1 (2014 Edition) Android Developmen] _nicolas_:
Thanks for the reply. Gonna try those apps.

Anny sugestion for SD card problem. I am going on holiday and need all the free space that is available ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Need Experts

I need help, guys. I just posted a long question about brining my wife's p600 right up to date, with THIS current ROM and all the goodies we now have. I THINK I wrongly posted it under General Help in this forum. I don't even know how to put a link to it. Point is that I found Odin runs very well on a mostly dead laptop. I have all the notes about running CFautoroot, but my brain is fussy about details. And what exactly is and where do I GET a "stock" recovery that may only be needed for a few minutes? I am asking for help or PMs if snyone can offer shortcuts to get this done. One big question is about fining the .zip file fo updating the bootloader to the LP one. Hard to find and would it work on the stock 5.11 that I start with. Sorry, I'm rambling likely OT and double-posting, but I need refreshing as it was a while since I used Odin on MY p600. It scared the crap out of me then, and THIS p600 is my WIFE'S! Seriously, she is disable and stuck to a motoized wheelchair. Her tablet is her link to the outside world. Her tablet is in the shop with battery issues and I want to update it to make her happy at last for a while. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Dear DeanoD,

To get root you need only to flash latest TWRP.tar file via Odin. I'm using the one from ShevT's LOS/RR/AICP thread for p601(it's the same for p600).

When TWRP was successfully installed reboot into recovery via longpress power button and volume+ and flash latest superuser or latest Magisk zip to get root. (it's the same procedure as to boot into fastboot mode just with the + button)

Now you have root and latest custom recovery installed.

Next step.

There are two ways to get the LP bootloader. The first one is simple to flash latest 5.1.1 stock rom.tar with Odin, it includes the LP bootloader. But it's a big file, 1,3gb and you will lost root and custom recovery! You can also use the build-in update funktion it should find the latest 5.1.1 rom but only as long as device it not rooted.

There are several helpful video's on youtube which explains how to use Odin to install a stock rom.tar on a Samsung device and also in general section here in the forums are how-to's for that.

And the second more easy way IMO is to follow the instructions on the first page. This way you don't lose root and recovery and it's much faster. There is a link in between the instruction with the latest bootloader.tar files and a detailed how to with install instruction. Very easy.

But in case you use this method you need to reboot into recovery immediately when the bootloader is installed, then full wipe(system, data, cache and dalvik cache) and flash the latest AICP rom, gapps and magisk. This is neccessary because 4.2 roms most probably wont boot with the new LL-bootloader.

You need to download these files:

- latest recovery.tar to your PC(ShevT's thread)

https://www.androidfilehost.com/?fid=817550096634769729

- latest LL_bootloader.tar to your PC

https://xdaforums.com/showpost.php?p=71355516&postcount=1247

- latest Magisk v13.beta to your sdcard(also the other files below)

https://www.xda-developers.com/new-...is-now-available-and-it-can-bypass-safetynet/

- latest AICP.zip

- latest gapps(from 1. page)

https://xdaforums.com/galaxy-note-10-2014/development/p600-pre-official-aicp-12-1-t3592449
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I'm note gonna quote all the great tips and links you posted, but you can bet your A** I'm PRINTING IT!! Thanks for all this doesn't come close to being quite enough! My wife thanks you and the ghosts of computer info lost in my memory thanks you!! ;-DeanoD -the bootloader info is the cherry on top!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] doktorknow:
The Rom works great here!!

Now AICP_OTA tells me, that an update is available (nightly_20170629). Can you explain the procedure to update the rom?

When i download the file and press the INSTALL button, the tablet restarts in TWRP and i can´t find the file anymore (i use the sd card as extended strage).

If i can finde the nightly_file, what kind of wipe do I need?

Do i have to reinstall all my apps or is the update "only" changing the system-data?

Regards,

doktorknow
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Doktorwouldliketoknow,

Download and install the new rom.zip manually. You can dirty flash it what means you don't loose any data or settings.

Download rom update, latest gapps and magisk to your sdcard(links are a few posts above)

Reboot into recovery

Backup current rom first for safety reasons!!!

Now there are two ways to do it.

Wipe cache and dalvik cache

Flash rom

Reboot

or

Wipe cache, dalvik cache and system

Flash rom, gapps and magisk

Reboot

I prefer the second way, it's not neccessary but it's more cleaner.

And sorry for the joke, but that just fit so well I could not hold back..:good:

---------- Post added at 12:16 ---------- Previous post was at 12:15 ----------

:highfive:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] doktorknow:
This works fine! Thanks for response!

Now i´m licking my wounds because of your joke:crying:

Best regards,

doktorwouldliketoknow:cool:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Haven't tested this week's build, but since previous release this ROM is golden. No freezes in my end.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] stiernacken:
I used this Rom for a while. No issues no Bugs. Great Rom, thanks for your work!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] sToRm//:
Pro tip: If you have problems with sound (crackle, scratching,...), then use Kernel Audiutor - > Sound, and activate gain function there (+ set at boot). I have gain 7,5+ on left and right speaker. Sound is good since then. :good:

---------- Post added at 06:48 PM ---------- Previous post was at 06:45 PM ----------

Absolutely. It's running so smooth. Love it! If you update to a newer version, don't forget to reinstall Play Store (if needed). I did it and my experience with actual build is: Happiness :D
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Thanks for the tip. I haven't noticed sound problems, but it's nice to know a workaround.

You sold me hehehe will dirty flash in a moment. IMHO the only thing to improve, if possible, is the charging time. As for the rest this is an excellent Rom.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] sToRm//:
I hat them when i turned music to max volume. Was terrible... ;)

Haha... Charging was a problem, too. But I have a solution. I saw there is standard input at charging (1000mAh) while screen is on. This is tooooo low... My tab said "5 hours to full charge"... Hahaha... So if you want to speed up your life, go to battery settings in Kernel Audiutor and change the maximum charging input (I did full power). Set it at boot, too. Voila, full charge changed to 1.5 hours from 5 hours. :cowboy:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Will try mate. Thanks in advance.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
"Not Seanandroid Enforcing"? or Just Not...?

Is this message still coming up for current build(l'm waiting for a better charge on unit)? And, if we are current with build, bootloader and Magisk, SHOULD this message STILL be coming up? IIRC, last info said to ignore this error message--but then, WHY IS it coming up? Ignoring I can do... but FIXING would be better, IMHO. ;-DeanoD

---------- Post added at 11:04 PM ---------- Previous post was at 10:51 PM ----------

UDATE: I have d/l all of these files to a blank microsd card ready for tablet and Odin (which IS oddly working and quite well with Windows 10 on ancient tablet--go figure!) Sadly, my wife's tablet (sp600) running a VIRGINAL install of OEM Android 5.11 from Samsung, is STILL in the shop, waiting for a new battery ordered over the holiday weekend. And, now MY tablet running last previous build, is ALSO in dire need of a new battery. Anybody have TIPS on buying a battery for an sp600 unit? Thanks. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Just found something amazing hahaha. Latest build is great, but after almost a month without freezes just had one when playing with the buttons and nav bar options and in the process I've discovered (don't know if you guys already knew) that if you use the physical buttons instead of the virtual navigation bar the Rom is 90% smoother.

Maybe it's a graphic problem with the nav bar or something, but by disabling it, the tablet is almost as smooth as my OnePlus3.

I've never liked Samsung's buttons and in general led buttons that are always on, nevertheless, the performance boost that it brings in this case is worth it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Stop posting nonsense! This is simply not possible!

You can't charge a 8220mA battery in 1.5h with a 2.1A charger, even if the full 2.1A is applied it needs at least 4+h from 0-100%.

For this(1,5h) you need a fast charger like quickcharge or dash charge for which our device is simple not compatible.

I use an 3A charger, by the way and nevertheless the maximum possible charging current at screen-off is ~1850mA, even if you turn up all battery settings(in adiutor) fully to 3000 / 2550mA.

The charging current is limited by the USB 2.0 restrictions and charge protection circuits built-in in our tablet.

If you want to know more about your battery there is an good free app called AccuBattery, try it out it will show you real meassured/estimated values not only values delivered from kernel.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Ok I'm about to clean flash the latest release as my discovery of the physical buttons apparently caused a lot more freezes, but I have to prove it entirely with a clean install and a new build.

Will report as I have some results.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Got the same freezes as before and the device also freezes on darkness or conservative governor, but I'm on KK_BL and still use the 6-21-17 kernel.img because the changelog shows no device specific changes for our device.

I've tested with and without virtual navbar it makes no difference for me but also I've completely disabled annimations.

But I've observed another issues in the latest two builds, screen flickerings from time to time, most of the time while browsing.

Apart from this issues the rom works as good as expected..:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
"Not Seanandroid Enforcing"? or Just Not...?

I know I scewed this post up from before. It happens when I post at 4:32 am with insomnia. Are we or are we not supposed to still be getting this error message at bootup. EVERYTHING is running smooth and current - ROM, bootloader, beans gapps. Why does this message still persist? It could be something totally unimportant with our device, but when it show as an error, it bugs me. Still curious. The way we should be. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] sToRm//:
Ah sorry, you misunderstood me. The battery was not empty! Had around 55% at this time. ? So it was no nonsense.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
You mean the red seandroid error? I can get rid of it but it'll make the build much bigger
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Well I'm half way over a battery cycle, BTW battery life is really good with [MENTION=4174709]ollimi1[/MENTION] smsrtmax settings. So far I've just had one random reboot, not freeze reboot. Performance with physical buttons is awesome and by tweaking the battery and power settings on deathly adiutor the battery charges at a normal speed.

I'm on LL bootloader and my recommendation for people with many reboots would be to clean flash. I'm loving this Rom it's definitely a keeper.

Either way I'll keep you posted if anything comes up.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
So I DID manage to find something totally useless! I think it looks fine just the way it is. And I'm more than happy to ignore it, too! ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
New test build,

Major changes:

All the freezes should be fixed, turns out the input boosters were the issue, disabling them didn't actually disable them properly before (credit to lineage)

download https://www.androidfilehost.com/?fid=673368273298970758

kk bootloader build https://www.androidfilehost.com/?fid=673368273298970764
[Galaxy Note 10.1 (2014 Edition) Android Developmen] doktorknow:
I updated the ROM to 20170706 and now i had three times that the tablet looses the SD-card when I´m looking a lot of picures in the galery.

But mostly I can look all the pictures without a mistake - definitly no helpful information I think...

Regards

doktorknow
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I couldn't follow the links you posted to Ollimi's specific battery settings. Could you post more details as well as any tweak settings for battery improvements with deathly auduitor. So far, this test build is running best of all with better power levels while charging on AC. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Well... In fact I didn't post any link to the settings, but you could easily go to page 14 of this thread, thee you'll find his post and settings.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey DeanoD,

this is the post mentioned above.

https://xdaforums.com/showpost.php?p=72579828&postcount=139

---------- Post added at 08:41 ---------- Previous post was at 08:22 ----------

[MENTION=6227169]mosimchah[/MENTION]!

Yeah, the freezes seems indeed fixed, hopefully it stays so! :highfive:

Unfortunately the keyboard sound input delay while typing text is still not fixed yet.

I had the hope that it hangs anyhow together .. but seems does it not!

Edit:

Two freezes yesterday:crying:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
I do not like being the game spoiler, but I got more and more freezes in the past few days, at least 5 or 6. :crying:

So touchkey/input boost seems not to be the reason herefor, unfortunately.:eek:

What still makes me wonder is that RR has no freeze issues?:confused:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Sorry to hear that. I'm the kind of guy who doesn't like answer like "no problems here" but this is the case :laugh: I clean flashed latest nightly and had one random reboot then dirty flashed the experimental build since day one and not a single problem I've had whatsoever.

Maybe a clean flash would help or perhaps it is due to the KK bootloader I doubt it, but it's the only thing I can come up with.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I'm also still getting the random lockups. They still seem to occur when I am doing rapid input with my pen. I'll see if I can grab a log file next time. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
More information please. Like, your bootloader? Dirty or clean flashed? Apps used when the freezes happened?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Sorry, I should know better than to not have the details of my install. I'm running the latest nightly, with the LP bootloader. All recent installs have been dirty flashes. As for apps that cause the lockups, nothing specifiic seems to cause the problems, ither than I was using my pen for input at the time. And "my pen" is a Wacom Bamboo Feel made specifically for this tablet. Could this be hardware related? ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
I don't think it's hardware relates nor due to the bamboo Feel. I strongly recommend you to try the latest EXPERIMENTAL build or wait for this week's compilation and do a clean flash.

People before reporting problems try to clean flash. If problems persist report them.

BTW I'm on latest experimental and I have zero issues, everything is nice and smooth, I don't like my keyboard sounding so i don't know if the sound is delayed, but couldn't care less. The S pen is fine, pressure sensitivity is also perfect. Battery life with smartmax when only readings comics, drawing and YouTube can achieve 8-9h of SoT. When my tablet is used as a streaming device, which is the common use I give to it, it usually gets to 4-5h of SoT. Also safety net passes without problems with latest magisk.

Overall this Rom is great incredible performance, good battery life and few problems.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
I also don't think it has to do with the kk_bl.img or a clean flash.

In my case it seems to have alwqys to do with the display input.

I got freezes almost ever while fast typing in some text. Sometimes in a browser window, sometimes in translater or also in my note app!

Yesterday I've clean flashed 3 roms, AICP, Paranoid and RR and the only one with no freezes so far was RR/P600.

Paranoid runs smooth and very well but after hours of using the first freeze occurs also while typing in some text.

I don't no if the display driver is from p600 or from an other, newer device but if I were a developer, I would look for incompatibilities there.

I'm also sure the click sound delay while typing text has also to do with this issues.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Here's the kitkat bootloader build for today's release

https://www.androidfilehost.com/?fid=817550096634787229

http://dwnld.aicp-rom.com/device/n1awifi/NIGHTLY/aicp_n1awifi_n-12.1-NIGHTLY-20170720.zip

by the way this should help with the spen freezes
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Love the boot animation :svetius:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Wimi_Bussard:
Fate Grand Order troubles

Sorry to bother you guys, but I ran into some troubles when trying to install Fate Grand Order. The game seems to have a pretty advanced anti root/cheat detection system, that seems to look out for a) root, b) Magisk c) probably certain ROMs, too.

(Currently installed: AICP (20th July) with Lollipop bootloader (I think, because original Samsung Lollipop ROM was installed) Previously installed: Resurrection Remix with preinstalled Magisk. I simply flashed AICP over RR and wiped system, data, cache, and dalvik cache. )

so, 1) Is this ROM rooted? I have read somewhere that it is pre-rooted with Magisk, but a random root checking app and Deathly Adiutor say "not rooted".

2) If rooted, can I safely unroot the ROM without causing problems? And how? (I have found a su removal zip file in the AICP extra settings, which one should I take?)

3) If it's not rooted, what could possibly trigger the anti root/cheat system of the game? And can I hide it?

This game is so frustrating...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
1. It's not rooted

2. See 1

3. Selinux being on permissive will trigger that, I recommend flashing magisk 13.3 to pass safety net until I change it to enforcing (probably for the next weekly build)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
If in the flash process you didn't include magisk nor superSU the ROM is not rooted. Honestly I can't think of anything that's causing the problem.