yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yeah, call me "reminder"!

And I found the reason for the heavy gpu load while charging.

It's the tiny charging animation you can see when you enable batterybar in statusbar and enable the charging animation. I mean this small running dots towards the batterybar... seems to need lots of gpu power for some reason.

While this seems to be normal behavior the heavy load of sometimes 90-100% seems not normal for such a small animation!

And if deaktivated there is immediately no load anymore!

---------- Post added at 16:34 ---------- Previous post was at 16:22 ----------

It's a well known problem and [MENTION=6227169]mosimchah[/MENTION] is already working hard to find a fix. It's only a matter of time...:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] slimjimz81:
ok, I think I may have missed something or just doing it wrong. every time I do an update it gets stuck in a boot loop after flashing. any suggestions? and great ROM by the way
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Wipe the system, cache, and dalvik cache, and then flash the ROM and beans gapps
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Been tinkering with this new build for a day now. OTA update was a bust, sticks on AICP logo. Same result with a quick wipe and a manual install with Beans minigapps. Were there major changes since last build that would cause the looping? I'm still on the fence about flashing the Prime Kernel. And I've seen several mentions of ShevT's version of TWRP and I keep getting dead links. I'm gonna try full wipe flash to get this to work since everything else has run very well so far. Anybody got a link for ShevT's TWRP?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi DeanoD.

Here you go, latest is 3.1.1.0:

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

If the dl link is still dead, take download below. I've uploaded latest twrp for you.

Did you try to install latest update manually? Try it and wipe cache, dalvik and "system" then flash rom and gapps.

Where did you get the loops?

After booting, when the device starts to allow superuser rights for some apps or before it's fully booted? If it still loops try flashing latest magisk v12 on top, it's sometimes overwritten and gets lost.

[MENTION=6227169]mosimchah[/MENTION]

Can I still use the latest kk_bl.img(5-18-17) for latest 05/25 update?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] vinayburman:
I had the same problem. Here is what I did, while stuck on logo I pressed and hold the power button as soon as tablet powered down, I pressed and held the volume up button also. Now I booted to twrp and cleaned dalvik and cache, rebooted to system and problem solved. Another thing I found is if you recharge your tablet powered down, the charging rate is much faster than recharging power on.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Just dirty flashed 5/25 build, no problems so far, feels a little tiny bit smoother.

Charging time seems normal to me, considering that Temasek's builds took 5h to charge, AICP is golden with 4h.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Yes, nothing changed kernel side
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Where did you get the loops?

After booting, when the device starts to allow superuser rights for some apps or before it's fully booted? If it still loops try flashing latest magisk v12 on top, it's sometimes overwritten and gets lost.

I was getting the AICP logo onscreen, and there it sat. I downloaded the ROM again to make sure that there was no bad files, but when I tried to flash the Prime Kernel, everything yarped it back at me. Corrupt, files md5 errors, etc. So I'm back to checking my downloads all over again. Gonna try clean flash, not sure what to do with the Prime Kernel crapping out. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] haighpaul:
Yes, I was unable to get past the logo with OTA/dirty flash. Tablet hot quite hit while it was stuck too. In the end a clean flash worked and all is fine even if it took a lot of time setting up everything again.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
You need Prime v7.4 for LL bootloader when you already installed the LL_bootloader.

I do not know when you downloaded it, but I know the kernels were exchanged for some reason.:eek: (Kk_bl_kernel was for ll_bl and vice versa):eek:

Hitman has already corrected this, but perhaps you have still caught the swapped kernels?!

If you download everything again, it should fold with a clean installation! :fingers-crossed:

---------- Post added at 09:07 ---------- Previous post was at 09:03 ----------

Hey haighpaul,

You can restore your data partition from previous backup after a clean flashing if you have one. But in front of it I would try to install latest OTA manually incl. system wipe, then flash rom and gapps again.

You can still make a clean flash if it does not work.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] haighpaul:
Thanks for the help. I did have a backup so I tried restoring just the data partition on top of a clean install. Unfortunately TWRP gave an error 'extractTarFork() process ended with error 255 during the restore. This was the same backup I used to recover from the point when dirty flashing got stuck at the AICP logo so it worked up until the new system ROM was successfully clean flashed. Very strange but looks like data partition is the issue. I'm on LL bootloader.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Maybe try a full wipe incl. data media next time you got these issues. Maybe some very old leftovers or the likes..

I've got a very similar issues when I went from Temasek's 5.1 to 6.0 and a full wipe solved it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I'm getting similar results with latest build. Heck, even TWRP itself is getting in on the total crap party. When flashing current build with a valid known working beansgapps that even gives me errors. Having props also with Prime Kernel not installing. It does seem to point to a huge conflict with data not being fully wiped. I'm afraid to go full on format until I see less error messages. Even got TWRP turning red just before reboot! Not my kind of fireworks. Will be staying with previous official build for now. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Sh..!

Unhappy to hear that, buddy!

Hopefully you can bring an older version to run.

Maybe try a full wipe/factory reset next time(incl.data media) and make sure you use ext4 as file system not f2fs.

You can see the used file system in trwp protocoll.

Maybe re-format the whole data partition, there is a repair option to change or format file systems.

:thumbs pressed:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Forked?

I'm having problems left, right and up my wahzoo! EVERY file that I have downloaded recently seem to be corrupted!

Tried to flash ShevT's TWRP and get md5 errors, corrupt file messages. I tried flashing Prime Kernel, and it is the right one, and it almost shot me out of recovery. And now, when I boot to recovery, it's behaving like it has a short circuit. Half of the screens are missing and when I try to touch the screen for input, it seems to randomly run files on it's own.

Could that be from using a 3rd-party app to boot into recovery? I just d/l a new TWRP from the link and it show the md5 wrong. I'm beginning to think I may have finally run out of luck with my note.

Should I just go for broke and reformat with a full install? Just don't understand why this is happening. Can't trust the files that I do have anymore. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Holy moly, it's getting more and more worse, man.

Try to download the files via another browser and if it not help, try download it with another device or with a PC. You can transfering the files to your ext.sdcard when they are okay and flash it from there.

I would also remove the third party app and try start into recovery via power&volume- button combi.

And I would definately do a full format to remove all old files and especially these leftovers from touchwiz. As you know, app data will not been removed by a "normal" data wipe and they can really lead into trouble when switching often between TW5.1 and latest AOSP. Transfer the necessary files (rom, gapps, twrp, kernel) to your external memory card and safe other important files there.

I've got many several issues in the past few years with different samsung devices and the internal storage(s2, s3,..) and most of the time a full wipe/format of the whole data partition was able to solve it.

Another possible reason could be the display connector, it is connected by a flatband cable which gladly unmount or get loose from time to time.

I've already fixed it by myself and it's really simple!

However, you need to open the device to verify this (There are some how-to's on youtube, search keywords: Fix blackscreen on Samsung Note10.1/p600).

But I still hope a full wipe/format of your internal storage will fix it... because the removing of the backside is very time-consuming because you have to loosen many little snap-locks.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Falloutboy2000:
So far very stable Rom - thanks again

Funny, mobile device eats most of battery?!?

I dont have... P600
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Mobile data doesn't take up any battery, it just looks like it does in that one instance
[Galaxy Note 10.1 (2014 Edition) Android Developmen] OMIGHTY1:
Cannot update

The links for all recent updates lead to a 404 error. What's up with that?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Fixed
[Galaxy Note 10.1 (2014 Edition) Android Developmen] jerrys0828:
They're working fine for me. Maybe it was a temporary issue?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Yes, it was recently fixed
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Clean Slate Works Best

After many odd error messages and being ready to call an exorcist to tame my note, I RTFM and did a full format and install. Everything I had was 100% right with what all my commentators had warned me to watch for: LP bootloader check; ext4 not f2fs; rom version check. But it just came down to some bit of trash with my data files.

Official ROM running smoothly and seems faster. Now, I have to tackle Prime Kernel, but I suspect that it will run just fine. Thanks for all the support with my ranting and raving.

;DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Yep, HAD the new build working for two days. Thought to update to Prime Kernel. Install ran smootly, no errors files good also. BUT on REBOOT KABLOOIE! It would either never advance past the AICP logo, or the screen would go dark.

Had to force recovery, and it's still going haywire, opening files refusing input. Like playing PacMan just to run two zip installs. And SOMETHING with my many wiped setup is not allowing any clean boots! I'm just parked on the previous official ROM with little hope of getting PrimeKernel installed. It DID work. It would not allow bootup at all.

Still getting the random system locking up like maybe a brick? :(:( DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
AICP so far it's a good ROM. It works fine, could be smoother but it delivers.

The only major problem I've had are some freezes while reading comics with Challenger viewer, a forced reboot is the only solution. Nevertheless, It is a keeper IMO :good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Judson1975:
I switched to aicp from lineage. I'm loving aicp. Seems more streamlined, more options, and I love magisk over supersu. Only issue I had was the preinstalled magisk 12/4 kept losing root and forcing me to full reboot to get it back. I ended up upgrading to 13/5, but it was a struggle to remove 12/4 so I could upgrade.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey Judson1975,

Disable magisk busybox before flashing updates to avoid loosing root in the future.

Short zitat from magisk thread FAQ:

Q: I am losing root randomly!

A: In some custom roms (known: LineageOS), enabling the Magisk busybox will make root unstable

If you experience root loss issue, disable busybox in MagiskManager

BTW, v13 is an android O preview and can cause instabilities. I recommend to futher use v12 untill v13 gets official/stable.

[MENTION=6227169]mosimchah[/MENTION]

Todays build works fine with 5-18-17_bl.img ...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Just about to dirty flash latest release, but just wondering if reflash magisk is mandatory.

I always flash it on every new update, but just asking if it is necessary?

Edit: I answer to myself, it is not necessary. XD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Judson1975:
I'm on aicp rom now, not lineage. And magisk 13 seems to me to be more stable than 12. 12 would randomly drop root, and if I did a hot or soft reboot, it would load without root every time.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
AICP is using the same lineage base so expect the same issues!

You should at least read the first page of a rom/kernel thread carefully to avoid missinformations. And I wonder why I have no such issues like you and there is also not a single post with such issues in the whole thread...

Disable "Busybox" and "Hide Magisk" each time you flash a rom update and it should work. And enable Hide Magisk only if you need safety net functionallity!

The only reason to re-flash magisk is when you use one of the kitkat_bootloader.img's for users of the old bootloader. In this case you'll lose magisk for some reason and magisk need's to be re-flashed.

But if so, you should have mentioned it!

---------- Post added at 10:04 ---------- Previous post was at 09:44 ----------

Yepp,

the freezes from time to time are unfortunately not fixed yet.

And to your other issues, can you still flash .tar files with Odin/PC?

If yes, you can try to flash the latest official Stock Sammy 5.1.1 Rom from sammobile website via Odin.

It includes a PIT file which means all partitions will be re-formated in the right way and you can start with a really fresh setup. You can flash latest TWRP.img.tar also with Odin to get the recovery back and start from scratch with a full wipe factory reset and install AICP and gapps again!

If that also does not help, I think you have a defect in the hardware or one of the internal connections is broken.:crying:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tim047:
Loving this Rom, thanks so much for it.

Only one question, I know there are freezes etc, but is it just me that is getting screen flickering at times? It only happens when playing games and does not happen when on charge at all. I am wondering if it could be my battery? Any thoughts?

Thanks.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hmm!

No flickering here!

But I've changed my battery by myself and had no such issues and my old battery had only 77% left than I changed it.

It sounds more like the display connector... But against that talks that the problem disappears, as soon as it hangs on the charger!

Did you experience this issues also in other roms?

In case it is the battery there are a few good how-to's on youtube, simple search for note10.1/p600 battery replacement.

It's easy but relatively time consuming, expect an hour or two..
[Galaxy Note 10.1 (2014 Edition) Android Developmen] haighpaul:
I had some screen flicker on an older version (see post 47) but its not showed up since. I wonder if the when everything crashed that time is somehow recalibrated the battery stats??
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tim047:
Thanks.

I have never had issues with this on the stock Rom, but I did have major battery issues on stock with the battery jumping from over half full to almost empty in a second, but upon a reboot it would be back to normal. I could never figure a solution to this.

On this AICP Rom I have had no issues with the battery percentage jumping at all, just the screen flickering which sometimes leads to a freeze or the tablet restarting on its own.

I have changed a battery on my Fiancees Note 10.1 (I got her on this from a Ipad and she loves this so much more) So i guess I will try changing the battery on this one as well to see if that does it. The only problem with this is actually getting a battery, its pot luck with the batteries on Ebay claiming to be new.

---------- Post added at 11:46 PM ---------- Previous post was at 11:40 PM ----------

Thanks for the reference, I had seen this post, but no one else was mentioning it so I didn't know if its a Rom issue or my tablet. I was really hoping it was a Rom issue (No offense to mosimchah) I guess I have to try an get a replacement battery now and change it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
I can find the dealer where I bought mine. I have paid 24,95€ and my new battery is actually new, see screenie below! I will post the link as soon as possible but I've to search before, Lol!

Edit:

I also had these battery jumps, but only when playing power-hungry games like RR3 or so!

One only solution was to customize the CPU/GPU throttlingpoints, (see screenies)!

I think our CPU tends to leak-currents at high temperatures, which is more or less usual for any CPU or GPU. The problem here is that the battery can not supply the required power in the long run if the chip-temperature rise above 90°C.

If I modify the settings so that the temperature remains below 70°C, no leakage currents have occurred.

You can try to set the same values like I did with deathly adiutor to avoid these battery break-ins.

With me it helped to prevent the break-ins and a positive side effect, you'll save electricity and can play longer without overheating the chip.

Edit:

This is the ebay item number: 311068963913, store is called HandyWest but unfortunately they doubled the price for some reason. I've paid 24,95€ +3,80 VAT, now they want 49,95€ with free shipping, LOL!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
No, will not be re-calibrated on reboots. You have to imagine that the battery "current" breaks down at high load, because the battery can supply only ~8-12w (C2 or C3).

Unfortunately, there are no cells, such as those installed in e-cigarettes, which can withstand 30 times the load of the nominal current(C30, Sony Konion for example).

Therefor they have really high capacity (2 cells of 4110mA).

As soon as the high load stops, the battery regenerates partially, but it needs a reboot to display the actual remaining capacity.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tim047:
I am going to try the thermal throttling and see how that goes. Thank you for the useful information. I have never touched any of the CPU or GPU controls before, never sure what option to choose, there are so many options especially with the CPU Governors etc.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Not a problem, I like to help others just as others helped me..

Here are my CPU/GPU settings and a few other tweaks that I've made. You can try it if you want and if you like it, go to the profiles section and create a profile with all the settings.

And do not forget to mark "apply on boot" option in the right upper corner.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Does anyone else notice the low volume (and relatively low quality, though that may be just the normal way, not sure) of the mic?

People have a hard time even hearing me on Skype, I basically have to shout right into the microphone for people to understand me.

Did anyone else notice this, or better still, does anyone have a solution?

On other devices, kernel or deathly adiutor had an option for setting microphone gain or something like that, but I couldn't find anything like that here...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Unfortunately no mic-gain settings currently but you can try to use a headset?

Much smaller distance between mic and mouth and headset micro is probably more sensitive too.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
[MENTION=6227169]mosimchah[/MENTION]

No weekly today for some reason?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
It's building right now http://jenkins.aicp-rom.com/job/android/36395/
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
The new build is up,

Download:

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

Full changelog:

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

KitKat bootloader build:

https://www.androidfilehost.com/?fid=817550096634776308
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Just dirty flashed the latest build, but gapps weren't persistent. Flashed gapps again I'm not able to sign in. It says there's a problem with Google servers, but login mail arrived to my security inbox.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Can confirm OTA update on this build installs smoothly with no errors showing. Makes me happy. Now, if I can only get the Prime Kernel running also, I be happy camper. But, all in good time. ;-DeanoD

---------- Post added at 05:58 PM ---------- Previous post was at 05:49 PM ----------

OT--Has anybody else been having trouble downloading and or updating apps from GP? They can't seriously be blocking rooted devices as they PROMOTE rooted apps. Does this mean I get all my money back from apps that I paid for? What kind of work arounds are there? Could be some serious class action lawsuit if this is true. "PENDING" dowloads? Looks like, feels like and smells like BS or it that just me? ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Use magisk to pass safety net, then clear the play store data and you should be fine
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
I'm still not able to log in with my Google account and just found out that now I'm not even rooted.

Guess I'll have to clean flash...

---------- Post added at 01:27 AM ---------- Previous post was at 01:17 AM ----------

Sorry for the double post. Here's the error that keeps popping up.

BTW wiping cache, dalvik and system, then te flashing everything solved the root problem, but gapps are still not working

PD I've attached the error in getting.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
`What gapps version are you using? I am running Beans gapps with no problems at all. I don't believe that Open gapps is compatible with this ROM. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
The ones on the OP. I think they're called Bean gapps mini 7.1.x 20170518.

I'm giving it some time, before starting backing up everything to clean flash.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hmm, I got no such issues!

(wiped both caches and system, flashed rom gapps works fine for me)

Do you have a working rom backup?

If yes, restore it, try to log-in google if neccessary, if it works dirty flash rom and gapps dirty again.

And wipe system too...

[MENTION=6227169]mosimchah[/MENTION]

Still random freezes/reboots! Most of the time while using the keyboard.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Vaizen:
Thanks guys for your concern. Ended up doing a clean flash and everything is fine now. The rom feels smoother even with animations set to 1x.