yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] ipdev:
The issue could be GApps also.

Since you note that the July build work on it's own, would lead me to believe it might be with one of the addon.d scripts.

If GApps are not re-installing correctly after the rom flash, you will definitely get a bootloop or infinite boot.

Try installing GApps after you install the July build.

Use the same GApps package/setup you used with the June build.

Here are two ways to do a clean(ish) dirty flash.

Restore you June backup and make sure everything is working..

To be safe.

Backup what you want to save and store it off device.

Copy it to your computer, cloud storage, USB, ...

Clean(ish) dirty flash.

Keep data only.

Boot into TWRP.

Wipe system.

TWRP-> Wipe-> Advanced Wipe-> Select System then Swipe to Wipe.​

Install the July build.

Install GApps.

The same GApps build you did with you June build.​

Install Magisk.

Wipe cache(s).

TWRP-> Wipe-> Advanced Wipe-> Select Dalvik/ART Cache and Cache then Swipe to Wipe.​

Reboot to system.

Clean flash, restore data only.

Restore data from backup.

Boot into TWRP.

Wipe system and data.

TWRP-> Wipe-> Advanced Wipe-> Select System and Data then Swipe to Wipe.​

Install the July build.

Install GApps.

Install Magisk.

Restore only Data from your June TWRP backup.

Wipe cache(s).

TWRP-> Wipe-> Advanced Wipe-> Select Dalvik/ART Cache and Cache then Swipe to Wipe.​

Reboot to system.

You might have issues but, it should hopefully boot.

Issues might come from data.

Settings, user set permissions, apps and app updates are stored in data.

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Nexus 10 Android Development] ipdev:
Sometimes it takes a few battery charge cycles to get the battery manager to read the battery properly.

Full -> Discharged -> Full -> Discharged...

You run into this on most devices, especially if you upgrade the battery to a better version. ;)

Cheers. :cowboy:
[Nexus 10 Android Development] lobstapowa:
It would appear that the issue was with gapps all along!

Did the cleanish dirty flash and all appears to be well now. Thank you so much for the help @ipdev !
[Nexus 10 Android Development] ipdev:
Hi. :)

I ran out of time last night to test on Lineage 17.

My main Manta was dead with a broken rom installed. Took a while to get up to 3% battery.

Enough to due a full wipe and install Lineage 17, OpenGapps, boot into system and let charge over night.

Lineage 16

My second manta.

Running Netflix v7.107.0

No GApps. No Magisk. Just Lineage 16.

Netflix installed using adb.

adb install-multiple​

Only issue I had recently (a week or so ago) was a buffer underrun while I was using a lot of download bandwidth at the same time.

Netflix did not like streaming on Manta while I was at my downstream bandwidth cap. ;)

Second Manta (32G)

Stock partition, 787M System

twrp-3.5.2_9-0-manta

lineage-16.0-20210718-UNOFFICIAL-manta

Lineage 17

My main Manta.

Running Netflix v7.113.0 installed from PlayStore.

No issues on a quick test.

Resume playing from a different device, jumping ten seconds ahead/backwards, scrubbing though using the time bar, ...

For Magisk, I did not change anything.

I only enabled MagiskHide to hide the sensitive props (bootloader unlock, build signature, selinux, ..).

PlayStore showed certified, since I do the Magisk stuff before connecting to WiFi.

If you enable MagiskHide after connecting, Google may have scaned your device and you will need to clear PlayStore cache/data to get Certified.

Netflix was available in PlayStore to install.

Main Manta (32G)

(re)partitioned, currently 3.0G System for testing GApps.

twrp-3.5.2_9-0-manta

lineage-17.1-20210721-UNOFFICIAL-manta

open_gapps-arm-10.0-nano-20210726-UNOFFICIAL

Magisk canary debug. (v23001)

Same as stable v23 at the moment.​

I am guessing this might be causing the issue. :unsure:

Redfin (Pixel 5) is quite a bit [<- understatement] different than Manta.

Give Netflix and the other apps that gave error another try without setting props to redfin. ;)

Cheers. :cowboy:

PS.

Netflix and Google have a strange relationship.

Netflix does not need Google services to run.​

Google, being Google, wants to control every app.

If Netflix does not show in PlayStore, once Netflix is installed, Google will claim it an take over updates.

Even if your device shows as Not-certified in PlayStore.
[Nexus 10 Android Development] ma66ot87:
Thank you for this very informative reply and for your constant work. LOS 16 is running great on my Nexus and I'm so happy to have such an old device running so well.

Long story short the latest version of Netflix is running now after updating it from the mentioned 4.x version through PlayStore. But don't ask me why. Netflix has always been a pain for me when it comes to use it with rooted custom roms. There was a time where I had to google for Netflix on my LG G6 phone and basically call the app in PlayStore from the browser to install it because it would not show in PlayStore if I searched it there. It was ridiculous. I rooted correctly with Magisk and used Magisk hide cleared PlayStore cache just as I did with the Nexus. It would always show this behaviour. Until it didn't. I've never solved the mystery.

With the Nexus it might be the same case. Btw I changed the props to Pixel 5 after I tried it several times with normal configurations. This is something I did in the past with my phone when Safetynet wouldn't pass for no obvious reason. I just gave it a shot hoping it would resolve the Netflix issue. So that is not really the reason.

Anyways it works now all good.

Btw. is someone here using something else than SDMaid and Fstrim to increase performance of the Nexus? Appreciate any tweak tipps.

Thanks!
[Nexus 10 Android Development] csteinert:
A few days ago I flashed Lineage os 17.1 onto my Nexus 10. Before I had still been on Stock Android 5, so it has been a huge leap.

I would like to give huge thanks to followmsi and to those who described the required repartitioning options. I am really grateful to followmsi for creating and still updating this ROM and thereby giving more life to an old device.

To share my experience:

- everything works as expected. Having no camera / gps / brightness sensor is a small price to pay for some additional use of the table. Again, huge thanks

- the system is a bit more responsive than previous stock Android 5. This is great and makes me want to use it again.

- Web browsing is still slow but probably this has to do with the limited RAM. It's a shame that so much memory is reserved for the GPU that only 1.1GB is available to the linux kernel. But this was also the case in the late stock versions for this device. I found some old discussions about this from 2013 but no solution. I am not a kernel developer but poking around in the source code also did not yield an obvious way to reduce GPU Ram assignment. So I guess we just have to live with this. This is not meant as criticism, stock Android was the same in later versions on this device so it just must be a GPU driver thing.

- word of warning: do NOT try to enable SELinux with this ROM. I was stupid enough to try and enable it because LineageOS gives a warning if it is disabled but you should NOT use SELinux. Enabling it caused a boot loop for me. So just turn off the warning and leave SELinux alone...

This is basically it. Really a great improvement and the new ROM again makes me use the device after it had been mostly lying around for years.
[Nexus 10 Android Development] followmsi:
Lineage-17.1 - August 2021

lineage-17.1-20210809-UNOFFICIAL-manta.zip

Changes:

- Google security updates -> August 2021

- Disabled Google AVC codec to fix video on latest versions of Netflix.

- Patched framework/base to support microG

- Latest LineageOS changes for Android 10

Pls check first page for known issues.

For the "System and Cache repartitioning / Opengapps: Error 70" topic pls have a look on the first page.

Enjoy :p
[Nexus 10 Android Development] tgburgin:
Hi all,

I'm getting the following error when I try to install the latest release:

I:operation_start: 'Flashing'
Installing zip file '/sdcard/lineage-17.1-20210809-UNOFFICIAL-manta.zip'
Unmounting System...
I:Update binary zip
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
No path given to file labeling backend
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keysTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keys
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
Backup/restore is not possible. Partition is probably empty
Patching system image unconditionally...
performing update
blockimg version is 4
maximum stash entries 0
using existing stash /cache/recovery/4dd6bf24fbba9cc76c352f5c4cfaed0074be0244
/cache/recovery/last_command doesn't exist.
erasing 2188 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,227129,228864,229947,230400]
new data receiver is still available after executing all commands.
Patching system image unconditionally...script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/lineage-17.1-20210809-UNOFFICIAL-manta.zip'

Any ideas what might be the problem here? Any more information that you need?

Cheers,

Tom
[Nexus 10 Android Development] cébé:
Hi,

Could you tell me what partitioning you use? Because I change /cache and /system according to messages I saw toward pages 45/46.

At the end, I have

7 88.1MB 222MB 134MB ext4 cache

8 222MB 1481MB 1258MB ext2 system

but it's not enough. Do I have to reduce /userdata and affect space to /system?

edit : it works! I reduced the /userdata part and enlarge /system.
[Nexus 10 Android Development] csteinert:
Hi cébé

Sorry for being a bit slow to reply.

I am happy that you were able to solve things.

But still, just to share.

I did not do a manual repartitioning. Instead, I changed the partitioning by flashing the following file with TWRP:

lanchon-repit-09180102-cache=max+wipe-system=1228M-manta.zip

The download links for this are in the first post of the REPIT thread: https://xdaforums.com/t/tool-unofficial-port-repit-for-nexus-10-manta.4237189/

From there I followed the Google Drive download link and downloaded the ZIP file that I mentioned. Flashing that ZIP file did all the repartitioning as needed. After this I had no problem to flash the latest LineageOS 17.1 ROM from followmsi, the latest GApps Pico for Nexus 10, and the latest Magisk.

Probably all data is lost in the partitioning process but I did a full wipe anyways so that did not bother me.

All the best and thanks to everyone who participates in this forum. And special thanks to followmsi for the rom and ipdev for REPIT
[Nexus 10 Android Development] BlackVoltage:
Do you have a hint? I does not work for me .. everytime I try to install 17.1 via twrp ist get ERROR:7

If I do instead install old lineage 13 the same way - it seem to work.
[Nexus 10 Android Development] csteinert:
Did you check if the zip file is complete and intact?

Did you do the repartitioning first to have enough space on the system partition?

Those two things are the only stuff that I can think of... Good luck!
[Nexus 10 Android Development] BlackVoltage:
Partitioning did not work either. Told me what I should do - I tried that but out didn't make a difference ( deactivate mdt or something).

How to check file? With md5 checksum?
[Nexus 10 Android Development] csteinert:
Checking with MD5 would be the best. Or if you don't know how to compute an MD5 checksum then at least you could tryto unzip the file on your computer to see whether the unzipping works without any problems.

It is very strange that the partitioning did not work. Like I wrote recently on August 16 in this thread I simply flashed

lanchon-repit-09180102-cache=max+wipe-system=1228M-manta.zip

with TWRP which I had downloaded from here: https://drive.google.com/file/d/1mBqgJapk8Eo-vzgF0tzafZHV3atezq55/view

Inside of TWRP you should indeed disable MTP before you try to flash anything. To disable MTP you have to go to the "Mount" menu in TWRP and then in the bottom-right part of the screen there should be a button "Disable MTP". After that you can go back to the main screen, select "Install" and then flash your Zip file.

After flashing the Repit repartitioning zip (wait until it has finished!) with TWRP, I rebooted again into TWRP and then I flashed the ROM, Google Apps pico from https://opengapps.org/ for ARM + Android 10, and then the latest Magisk from https://magiskmanager.com/. These three (ROM, GApps, Magisk) can be flashed in one go. Only after the repartitioning I rebooted once.

Magisk is of course optional but it is nice to have root permissions and nice to have it in a way were it the rooting can be hidden. You can just rename the Magisk APK file from .apk to .zip and then flash it also with TWRP. This is somehow not the recommended method anymore to install Magisk but for me it worked very well.

I hope that this works and is helpful

Christian
[Nexus 10 Android Development] BlackVoltage:
Thanks for your help .. for safety I dowloaded everything again and pushed it to \sdcard\0\ via adb. I also compared md5 checksum for lineage 17.1 file (matches).

Nevertheless your same lanchon-repit*.zip file does not work for me. Again the same errors I got earlier. Please see enclosed. (Samsung Nexus 10)

EDIT: It is connected to pc but mtp is disabled and yesterday I tried as well without connection to pc. The 2nd JPG enclosed shows Error 7 when trying to install (md5 checksum compared) Lineage 17.1 ZIP.

EDIT2: I do not know if I may have encrypted that thing years ago. How could I see that and uncrypt it - if it is?
[Nexus 10 Android Development] csteinert:
Hi BlackVoltage

The only thing that I did differently was that I used a USB stick and flashed the file from there instead of pushing it into the tablet from the computer.

The so called SD card is of course also in the internal memory of the Nexus 10 so i don't know if this will create problems with the repartitioning.

If you have a USB on the go cable then you can try to mount an external USB stick in TWRP and then flash from there. If you don't have an external stick or not suitable USB OTG cable, then try to push the zip file for the repartitioning to /tmp/ maybe that will work but i haven't tried this.

Edit:sorry, I just saw in your screen shot that you already tried flashing from /tmp/ so In this case my only idea would be to flash from external USB like I did. But you would need an OTG cable or a USB stick with a micro USB connector...

Edit2: in your post you mentioned encryption. I don't know how to check for that. But one thing that you can try is too reformat not only data and cache but also the system partition. This is what I did before flashing

In the TWRP advanced settings somewhere your can say that wiping should format the file system. And then you can wipe system, data and cache, which should cause an empty file system to be created. Man maybe this will help with the flashing...
[Nexus 10 Android Development] BlackVoltage:
Well as you can see in the first picture above - I tried to install the repartition skript from/tmp/ like they recommend. Have you read it? The text also says that one resource it tries to use is busy. Seems that that is the Problem?

[I have lots of usb sticks but now adapter to plug it into micro-usb from the tablet. Did not know so far that something like that would work. So far I installed everything via sideload from adb or from internal storage.]

Don't know what to do know. Found an older howto (https://www.getdroidtips.com/lineage-os-17-google-nexus-10/#Pre-Requirements) there they say Error 7 has to do with an older twrp version. But the one I use seems to be the newest one

EDIT: Unfortunately I dont have such an OTG Cable ... or wait .. I once bought an adapter including hdmi coz of a broken diskplay glass .. maybe it works with that thing. The last minutes I tried with adb sideoload but the skript tells me that that is not supported
[Nexus 10 Android Development] csteinert:
Good luck and like I wrote in my edit please also try to format your system + data + cache partitions, this might help against existing encryption.
[Nexus 10 Android Development] BlackVoltage:
Seems with my adapter wether an usb stick nor an sd-card is recognized. Meanwhile additionaly the screen starts to flicker sometimes.

My system partition seems to be 778 (or something) MB .. seems there could be an option to change that via twrp but I did not find a way to enter the wanted size (shrinking data and expanding system. There are only buttons to "rezize" which changes nothing.. Fomarting I did various times .. does not change a thing
[Nexus 10 Android Development] csteinert:
Sorry that the adapter is not working. I am not sure what else to test.

778MB is definitely not enough - my system partition has 1.239.344 1K-blocks - so basicaly a bit more than 1.2 GB. And my cache partition hhas only 100.784 1K-blocks so probably much smaller than before.

The repartitioning inside of TWRP does not seem to work on the internal storage - it only seems to be meant for USB sticks or removable memory cards. So this function is probably not useful for what you want to do.

I don't understand why the REPIT partitioning is failing for you. I am at a loss right now.

I hope that somebody else in the thread can explain how you can do either manual partitioning or how you can flash the REPIT stuff without connecting an external USB stick.

As long as you don't get the partitioning right, I don't think there is any chance of flashing the ROM. But I really don't understand why you get "error 7" from TWRP whenever you try to flash something...

Sorry that I have no further ideas...

Edit: Just to confirm: your TWRP version is definitely not the problem. You are right that you are using the latest version. I also use 3.5.2_9-0 and had no problems with flashing. So I agree that the version of TWRP cannot be the cause of your error. But I am not sure what could be the cause...
[Nexus 10 Android Development] BlackVoltage:
Sorry what do you want to say?
[Nexus 10 Android Development] csteinert:
@BlackVoltage:

Maybe one more thought: Did you try to unmount everything in TWRP before then doing the ADB push and flashing the REPIT Zip file? I don't know if the repartitioning can work if TWRP has mounted some of the partitions.

And I directly before flashing the REPIT Zip please try to format again the system+data+cache partitions.

I understand that you have formatted repeatedly before. But if you have maybe flashed data from another ROM on the system partition in the mean time, then I don't know if the repartitioning will work.

In my case these partitions were freshly formatted and unmounted before I tried the repartitioning.

If this is not helpful then I really don't know and then I can only hope that somebody else here in the thread can share how they did the flashing without a USB stick.
[Nexus 10 Android Development] BlackVoltage:
Ok then - I tried that as well. let's hope someone else has an idea or knows what to do. Thanks for your ideas. My last idea is to install 13 again and try to find something about encryption there?!

Meanwhile I have to charge the battery lots of hours I guess. Probably it flickered coz of empty battery.
[Nexus 10 Android Development] csteinert:
I also thought that the flickering probably had to do with low power.

About the encryption:

It seems that you can see this in the Android settings.

-> Open the Android Settings

-> go to Security & Location (may also be only called "Security")

-> go to Encryption & Credentials

Within the Encryption & Credentials menu you should see an entry where it tells you whether the device is encrypted.

The exact structure of the menus may differ a bit on various Android versions.The above description is what I found for Android 8.

I am not sure where exactly the Encryption & Credentials menu is on Lineag 13 / Android 6

I hope this helps

Christian

EDIT: Within the Encryption & Credentials menu, the exact entry is called "Encryption and Credentials" or soemthing like that (at least it is called like that on Android 10). In that menu entry there is a text which tells you whether the device is encrypted or not. If you tap that menu entry then you reach a submenu where you can also encrypt or decrypt the device.

I hope that these options are also there on Android 6.
[Nexus 10 Android Development] BlackVoltage:
Found something similar. Tells me that I could encrypt after the battery is fully charged. So ...that thing is not encrypted right now.

No ideas left. Need perhaps help to repartition manually via adb or something.

Or somebody who knows another solution

Edit: Which version of twrp did you perhaps I need an older version?
[Nexus 10 Android Development] csteinert:
I am also using version 3.5.2_9-0 of TWRP (latest version), just like you.
[Nexus 10 Android Development] BlackVoltage:
Damn .. Seems we are blind there must be a solution.

Probably a very easy one - some small thing is not right. Spend about 1 day so far. Only possible coz my knee is broken and family visits grandparents.

Next day I may have spare time is wendsday after hospital.
[Nexus 10 Android Development] BlackVoltage:
I'll try this now https://github.com/Lanchon/REPIT/issues/35

Edit: looks good so far after.unmountimg /sdcard/ how discribed there manually through terminal the partition process seem to work 😃

Edit2: New Problem now ...as soom as in customized with settings apps and so and and restart - I can't login again. Pin also extremly slow .. Typing.Pin ...then nothing.

Did a wipe coz of that. But now the same a second time 😔
[Nexus 10 Android Development] csteinert:
You have to wait for a while and retry again and again. At some point it will hopefully work. I had the same problem with pattern-based lock.

The system_server process was eating lots of CPU all the time and the lock screen was hardly reacting and allowed me only to lock in after many tries.

The only thing that I could do was to disable the lock screen. When you enable passwod or pin or pattern lock then there seems to be this problem.
[Nexus 10 Android Development] BlackVoltage:
I hole that was only at first (slow install process and so on) ... Activated pin now after 2nd Boot
[Nexus 10 Android Development] csteinert:
For me the problem with the slow boot and slow unlock happened every time after I rebooted and for me the system_server process was permanently eating a full CPU core even after successful login.

For me all this was the case even after repeated reboots so i had to turn off the lock completely.

I have seen some people write (on various models, not just Nexus 10) that the slow login happens for them after every boot but nobody else had the problem with the continued high CPU usage. So maybe if you don't mind being patient after every reboot you can also keep the lock screen. I wasn't quite that lucky...
[Nexus 10 Android Development] goodflood:
My Manta is very laggy. I want to restore to stock, first. Is this the newest stock images? https://developers.google.com/android/images#mantaray 5.1.1 (LMY49J) or are there newer images?

Is this the last bootloader bootloader-manta-mantamf01?

Then, I will restore to @followmsi newest ROM and report back.
[Nexus 10 Android Development] followmsi:
Lineage-17.1 - September 2021

lineage-17.1-20210916-UNOFFICIAL-manta.zip

Changes:

- Google security updates -> September 2021

- Disabled Google AVC codec to fix video on latest versions of Netflix.

- Patched framework/base to support microG

- Latest LineageOS changes for Android 10

Pls check first page for known issues.

For the "System and Cache repartitioning / Opengapps: Error 70" topic pls have a look on the first page.

Enjoy :p