yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] DragonFire1024:
Alright so I have an update regarding the cameras. I don't believe they're actually broke and I don't think it's a hardware problem. I've built a couple of tests ROMs using various file replacement that I've been able to track down. What I've gathered in the past whenever a custom rom was created for this device the Nexus 10, the camera would stop working. Somehow they had managed to bypass it by activating or building the SEC camera (Samsung HAL) as opposed to camera.exynos5 (exynosX camera). Currently that's what I'm trying to do. with other fixes I have managed to sort of get the camera at least to not crash. When opening the camera app everything is accepted permissions are granted and the camera presumably turns on but there's nothing there but a black screen. I've also tried replacing library files, of the few that exist for the camera, and when I try to do so the device will no longer boot after rebooting LOL. That to me says at the very least that it's awake and working or at least powered on to an extent. So based on these hardware files, replacing them with the current source files, would essentially override the platform camera and build it as an SEC Samsung camera which in theory should fix the problem.

As for NFC I presume it is working however I do not have any way I am able to actually test it. All the toggles work everything turns on and everything turns off aside from that your guests will be as good as mine.
[Nexus 10 Android Development] Egolino:
I cannot believe you're this close to fixing the problem this device had with custom roms for years. Thank you for your hard work and keep it up! :fingers-crossed:
[Nexus 10 Android Development] DragonFire1024:
I may or may not be. It's all speculation based on what little discussions I've been able to find across the web. I don't expect most of those people are around after that long of a Time so even if they knew how to fix it they would be telling us cuz they're not here anymore. Some of them were official Linux newsletter emails that disgust a tiny tidbit like a very small commit to a patch. If you look at a couple of posts back I did post a link to one of those emails where they discussed "turning on the Samsung cameras".
[Nexus 10 Android Development] DragonFire1024:
Okay. So my experiment seems to have worked in terms of the build process. I have looked and stared at it for so long on so many different occasions I notice all the new lines of code whenever they appear or errors when they appear. As it stands the process did take and build the SEC camera modules and or libraries. I'm not sure how everyone else's experience has been with trying to get these things to build properly so I'm actually a little bit excited by just that alone. I had to go to work so I was not around in time to see that build finish, it was still going when I left.

Couple of notes. It really is the difficult at times to get a pre-built kernel to be accepted. Without adding manually an sepolicy, the pre-built kernel must also have selinux disabled or set at permissive. I got sick of various other kernels just not building properly for whatever various reasons I decided to just go ahead and use my own pre-built, with the latest version I've been distributing, and everything moved smoothly.

So I also figured out a hardware problem I had. A massive memory leak which all this time I thought was not a memory leak going on several months now. Several months ago I serviced the tower and receded the memory chips. Either I had put them in the wrong order or they were not in place properly, because when I went to add two additional chips I suddenly gained all the memory I thought was being used to dual boot Windows. So that helped a significant portion and with a proper swap file setup, most memory errors are a thing of the past now thank God. I can't believe for all these months I've sat around and told myself it couldn't possibly be a problem with the memory chips being seated improperly. If I had not added additional memory yesterday, i never would have looked at them. It really is amazing how much better things will work especially when they're connected properly. It really does feel like a new machine.
[Nexus 10 Android Development] NO_ob:
Been using the los 17.1 build i'm surprised at how well it performs considering the age of the device. Seems pretty much perfect other than the reboot when screen goes off and the occasional bit of lag
[Nexus 10 Android Development] followmsi:
Lineage-16.0 - June 2020

lineage-16.0-20200608-UNOFFICIAL-manta.zip

Changes:

- Google security updates -> June 2020

- Latest LineageOS changes

Sources:

https://github.com/followmsi/manifests/tree/manta-lineage-16.0

If Safety.net check does not work just disable and re-enable "Magisk Hide" in Magisk settings menu.

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

Enjoy :p
[Nexus 10 Android Development] dahawthorne:
Say what? I've just spent a while looking for Manta 17.1 and can't see it. No doubt my eyesight is terrible :) but could someone please give me a link? Thanks...

On a different note, I installed the new 16 without any problems at all. Since the screen & sound are so good I use my N10 mainly as a media device, and just as an experiment I tried an HEVC x265 video. Result - a two-second black-screen buzz followed by a hard reboot. Not at all surprising given the age of the hardware. I'm just mentioning it in case anyone may find the info useful.
[Nexus 10 Android Development] NO_ob:
it's in the test folder on the gdrive link
[Nexus 10 Android Development] ticky33:
Thanks for all your work on our nexus10.

And what about the new los 17.1 from yesterday ?
[Nexus 10 Android Development] dahawthorne:
I just tried a dirty flash of 17.1 over the new 16. I wiped only Dalvik & cache, then flashed 17.1, OpenGapps Pico & Magisk 20.4. Unfortunately I got only as far as the PIN screen. As soon as I entered the PIN and pressed OK, the device rebooted and has refused to start at all since then. No problem, TWRP recovered my 16 backup without problems.

A clean flash may give better results. And it's great to see a 17.1 for my final non-17.1 device - all my other Nexus devices (4, 5, 6} are already on 17.1. I may try again in a few days.
[Nexus 10 Android Development] YogiDaGr8:
System Partition not large enough.

so i installed Los 16 and tried ti install gapps but no luck the system partition was too small. i tried to delete system apps or change some of them as user apps but no use the system partition was too small even for bitgapps. i used titanium recovery for the process i mentioned above and the device was rooted using magisk. i heard that there was a custom recovery for this issue but i can't find it. someone help pls.
[Nexus 10 Android Development] dahawthorne:
I'm probably wasting my breath here - I never learn - since junior members seem incapable of reading the instructions even when they are included in the installation instructions in the first post. And once I post what I hope is a helpful reply they are never heard from again. Let's see if this attempt is any more successful. (Yes, I do find this very frustrating, but from time to time I actually do get some positive feedback, which is nice).

From the first post:

System and Cache repartitioning / Opengapps: Error 70

The current system partition is (getting) full !

You need to do repartition your system and cache partitions .. either via TWRP package or manually via shell.

It's an one time task.

...

For automatic repartitioning have a look here:

https://xdaforums.com/sho...&postcount=957

https://xdaforums.com/sho...&postcount=960

https://xdaforums.com/sho...postcount=1059
[Nexus 10 Android Development] followmsi:
Lineage-17.1 - BETA

This is a BETA/TEST version !

I did disable watchdog in kernel now - no reboot once you go into sleep mode.

No need to keep display on all the time.

Pls read here for more infos .. https://xdaforums.com/showpost.php?p=81536647&postcount=1236

No more device changes this time .. just fresh lineage sources.

For testing I have added some patches to make miracast working in android 10.

As well I have patched framework/base to support microG.

Known issues:

- GPS is not working

- Bluetooth is not working.

- NFC is not working and has been disabled completely

- Watchdog has been disabled - in case of crash/bug you may need to reboot using power button.

Again, if you play around and find another bug and system may crash - pls use power button to reset/reboot.

Because of disabled watchdog there will be no automatic reboot anymore.

lineage-17.1-20200610-UNOFFICIAL-manta.zip

Changes:

- Google security updates -> June 2020 (android-10.0.0_r37)

- KERNEL: Disabled Watchdog

- Patched framework/base to support microG

- Patched framework/base to fix freeform window moving/resizing

- Patched framework/av to bring back "wifi-display" in android 10.

- Latest LineageOS changes for Android 10

If Safety.net check does not work just disable and re-enable "Magisk Hide" in Magisk settings menu.

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

Pls test like you want .. but also - pls don't ask for next build .. or for more fixes.

Thanks for understanding !

Enjoy :p

EDIT:

It seems the system does not like the fully disabled watchdog.

Made a new test kernel and (partially) re-enabled watchdog again.

https://xdaforums.com/showpost.php?p=82808183&postcount=1282
[Nexus 10 Android Development] dahawthorne:
Unfortunately a semi-dirty flash (wipe cache/Dalvik/system but not internal or data) ends up with my previous result - I get as far as the PIN screen but no further. As before, I'll try a fully clean flash when I have time.
[Nexus 10 Android Development] NO_ob:
it might work if you delete the lock via trwp /data/system/locksettings.db. Maybe rename it to .bak or something instead of deleting it.
[Nexus 10 Android Development] ticky33:
And what about the camera ?
[Nexus 10 Android Development] dahawthorne:
I've now installed 17.1 after full wipe and format and it runs, with a repeating "Bluetooth has stopped" dialogue, but otherwise works.

Unfortunately the lag is dreadful, as much as 10 seconds between keypress and reaction. I'll keep trying tomorrow and report if it improves, but it may just be that the Nexus 10 hardware has reached end of life in terms of what it can run.

Edit: I've had to give up on this attempt because even entering a PIN to unlock the N10 was taking me about 20 seconds. I don't think the hardware is up to the job...
[Nexus 10 Android Development] DragonFire1024:
Of the few tests ROMs that I've built and that have worked, I seem to have the same issue in regards to a delay in the sound when you press the screen. Another bit of irony oh, it seems are fire tablets over in the Amazon fire tablet thread has similar issues on the same Android version and both lineage. some of the fire tablets also have a similar problem with the camera if not almost exactly the same thing and that's really kind of weird. They are two totally different devices designed, built and soul by two entirely different companies so how they would end up with the same errors or the same problems my only gases that has something to do with lineage and their code.

---------- Post added at 11:04 PM ---------- Previous post was at 11:00 PM ----------

Keep your fingers crossed. I may have fixed that problem if this build works on the tablet I will find out in the next hour or two maybe less. I've been able to locate the build files for these cameras but not the ones that are given to us in the device tree. There are the platform cameras (exynos) then there are hardware cameras (samsung). In the past and I've only found very small amounts of information on this, they've been able to enter change the code while keeping the same cameras in order to get them to turn on if they for some reason don't work.
[Nexus 10 Android Development] YogiDaGr8:
I am so disappointed in myself. I just realised. now I know. anyway, thanks for pointing it out. really shows I'm a junior member doesn't it ?
[Nexus 10 Android Development] NO_ob:
no camera

The lag went away on mine after leaving it plugged in with the screen off for a few hours after setting it up, not sure if android 10 does some background setup or something
[Nexus 10 Android Development] thepinkguy:
Thanks for this, I'm happy to be using my Nexus 10 again. Made an account just to express my gratitude.

I also formatted in addition to the advanced wipe, that seemed to make the difference when I was trying a few different solutions.

Also I had some issues installing TWRP for the first time, something like a "no command".

I followed these instructions from reddit:

And then I was able to use TWRP.
[Nexus 10 Android Development] followmsi:
Lineage-17.1 - TEST KERNEL

It seems the system does not like the fully disabled watchdog.

Made a new test kernel and (partially) re-enabled watchdog again.

manta-kernel-10-20200611.zip (inside KERNEL subfolder)

It seems newer Magisk versions do not like the kernel installer and you may loose root access.

To keep root access - just re-install Magisk.zip in TWRP - right after kernel installation

Thats all for the moment .. hope to find another time slot for Nexus 10 soon.

Cheers
[Nexus 10 Android Development] dahawthorne:
I'm afraid that even with the new kernel my device is lagging to the point that it is literally unusable. Even after leaving it on charge overnight, so full charge this morning, and several reboots to allow any background processing to apply, it still takes about 10 seconds to react to icon presses. I've backed up this installation so that I can more easily try new versions, but I've had to revert to 9, which is as snappy as normal.

Sorry for bad news...
[Nexus 10 Android Development] NO_ob:
It works quite well on mine https://www.youtube.com/watch?v=ZgpfuUxzSkk&feature=youtu.be

The youtube popout player went a bit choppy when loading web pages though.

I'm wondering if it's to do with the health of your battery or something. I put a new battery in mine like 8 months ago and haven't used the tablet much so it's basically brand new
[Nexus 10 Android Development] dahawthorne:
Interesting. No, my battery is maybe a year old and works fine. I'll just put it down to frustrating computers - sometimes they work, sometimes not; everybody's experience is different. I'll just wait for a new version in the hope that whatever is blocking my device disappears in the new ROM.
[Nexus 10 Android Development] followmsi:
Lineage-17.1 - BETA

This is a BETA/TEST version !

One very last build for the next time .. to fix Bluetooth.

GPS is more tricky and for this reason it has been disabled now.

Apps like Google Maps do not crash anymore and using google location services instead of GPS.

Known issues:

- GPS is not working and has been disabled completely

- NFC is not working and has been disabled completely

- Watchdog has been (partially) disabled - in case of crash/bug you may need to reboot using power button.

lineage-17.1-20200613-UNOFFICIAL-manta.zip

Changes:

- Bluetooth is working now.

- GPS has been disabled completely

- KERNEL: (partially) re-enabled watchdog

- Patched framework/base to support microG

- Patched framework/base to fix freeform window moving/resizing

- Patched framework/av to bring back "wifi-display" in android 10.

- Latest LineageOS changes for Android 10

If Safety.net check does not work just disable and re-enable "Magisk Hide" in Magisk settings menu.

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

Pls test like you want .. but also - pls don't ask for next build .. or for more fixes.

Thanks for understanding !

Enjoy :p
[Nexus 10 Android Development] ali.muhmut:
Same here

Mine also runs like a dog. If you run adb (enabled by default and without client authetication) do you see the system_server process running at 200% (one for each cpu) when you run htop? Mine does.
[Nexus 10 Android Development] dahawthorne:
I can't say because I'm back on 16 for the moment, but it certainly acted as if it was running at a constant 100%.
[Nexus 10 Android Development] mtbsoft.:
Just reviving my old Nexus 10 with this rom and I'm waiting for the repartition to finish - it says it "can take a very long time". Can ayone give me a hint as to how long that might take? Are we talking hours? Can I reboot in the middle and do a factory reset because it's been almost half an hour now. It says current size cache /system 528/800MB, new size 100/1228.

Thoughts?

Oh and the screen has started flickering (bright/dim - andone else seen that?
[Nexus 10 Android Development] dahawthorne:
It took me maybe 10 minutes. My screen also did a lot of flickering when I was on 17.1, but not on 16.

Nexus devices are famously hard to hard-brick, so interrupting the process if it looks stuck most likely won't be a problem.
[Nexus 10 Android Development] mtbsoft.:
Thanks mate. I did eventually (1 hour) reboot and sadly things are a bit screwed up as a result. I couldn't get into recovery at all, had to reflash twrp via fastboot.

Once I did that, I discovered that the partitions appear to be stuffed up - trying to perform a wipe and I'm getting...

Failed to mount '/cache' (Invalid argument)

Updating partition details...

Failed to mount '/system' (Invalid argument)

Failed to mount '/cache' (Invalid argument)

:

:

...done.

So I've either lost the partitions or screwed the fstab.

Any thoughts on how I can put the partitions back? I'm tempted to rerun the partition script but dubious as well.

One final complication in all this is that the battery in this thing is currently shot, so I have to charge, get through any PC stage quickly then put it back on my best charger! Ho hum.

Why do I get the horrible feeling I'm going to have to flash back to Google factory and start all over again... (sigh)!
[Nexus 10 Android Development] dahawthorne:
There's a button for that... :)

Have a look at this thread:

https://xdaforums.com/showpost.php?p=77661978&postcount=2

It's for Nexus 5, but the principle will be the same. I guess you're using TWRP 3.3.1?

https://eu.dl.twrp.me/manta/
[Nexus 10 Android Development] mtbsoft.:
Cheers, but no joy.

Been delving into parted, partitions are screwed up badly. Tried to recreate but it's not good - when I run the resize script I get...

FATAL: the new partition layout of heap 'main' requires more space than available

[ERROR 1]

Then fails. Really looks like a full restock at this point.
[Nexus 10 Android Development] jaddle:
I'm seeing the same thing with the system_server process. It's really unusable in this state, unfortunately. I've left it running for an hour or two since installing, with no change. I think I'll try one of the earlier ones though, to see how it goes!

---------- Post added at 03:46 PM ---------- Previous post was at 03:28 PM ----------

I spoke a little too soon - after a reboot, it was less consistently at 100%. Still sometimes very slow, but not all the time! Maybe I'll stick with this version for a little while longer and see what happens.
[Nexus 10 Android Development] jaddle:
system still too small for opengapps?

I resized my partitions as described, and it seems to have worked - the partition is 1.2 GB now.

Filesystem Size Used Available Use% Mounted on
tmpfs 548.8M 20.0K 548.8M 0% /dev
tmpfs 548.8M 92.0K 548.8M 0% /tmp
/dev/block/mmcblk0p9 13.1G 9.0G 4.1G 68% /sdcard
/dev/block/mmcblk0p9 13.1G 9.0G 4.1G 68% /data
/dev/block/mmcblk0p9 13.1G 9.0G 4.1G 68% /sdcard
/dev/block/mmcblk0p8 1.2G 851.5M 358.8M 70% /system_root
/dev/block/mmcblk0p8 1.2G 851.5M 358.8M 70% /system

But after installing LOS 17.1, there still isn't space to install opengapps nano!

Total System Size (KB) | 1239344
Used System Space (KB) | 871904
Current Free Space (KB) | 367440
Additional Space Required (KB) | 27148 << See Calculations Below

Is there something I've missed? Is there a way to shrink the installed system, or should I repartition again, taking some space away from data and giving it to system? All the posts I've read here suggest that 1228MB should be enough, but it doesn't seem to be the case...
[Nexus 10 Android Development] followmsi:
Current Free Space (KB) | 367440

Free space looks good !

No idea about current sizes of the different gapps packages .. Pls use "pico" version instead of "nano" version.
[Nexus 10 Android Development] followmsi:
Lineage-16.0 - July 2020

Just to let you know .. The September build will be my last 16.0 ROM for manta !

I will continue with 17.1 only .. maybe 18.0 at some point ;)

lineage-16.0-20200709-UNOFFICIAL-manta.zip

Changes:

- Google security updates -> July 2020

- Latest LineageOS changes

Sources:

https://github.com/followmsi/manifests/tree/manta-lineage-16.0

If Safety.net check does not work just disable and re-enable "Magisk Hide" in Magisk settings menu.

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

Enjoy :p
[Nexus 10 Android Development] followmsi:
Lineage-17.1 - July 2020

As written above .. I will stop to make 16.0 builds in September.

For me 17.1 works quite ok .. All my stuff is running the same way like in 16.0 .. maybe a bit snappier.

Of course, there are still some open issues .. maybe I will find the time to work on them later on.

lineage-17.1-20200709-UNOFFICIAL-manta.zip

Changes:

- Google security updates -> July 2020

- Patched framework/base to support microG

- Patched framework/base to fix freeform window moving/resizing

- Patched framework/av to bring back "wifi-display" in android 10.

- Latest LineageOS changes for Android 10

If Safety.net check does not work just disable and re-enable "Magisk Hide" in Magisk settings menu.

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

Enjoy the summer :p
[Nexus 10 Android Development] geronimoge:
And again: Thanks a lot for keeping our device alive [MENTION=5480152]followmsi[/MENTION]!
[Nexus 10 Android Development] guidol:
[MENTION=5480152]followmsi[/MENTION] I used quite a long time 16.1 and did try yesterday the 17.1, but for me its extremly lagging

(using the actual opengapps pico, Magisk 20.4 and twrp 3.3.1-0/3.4.0-0).

At some point its was a little bit faster but at the next restart/power-on is was slow again :(

Iam back on latest 16.1

Did you also notice that twrp 3.4.0-0 didnt work with 16.1? 17.1 was flashable with twrp 3.4.0-0, but when going back to 16.1 I couldnt flash it with twrp 3.4.0-0 - it doenst couldnt patch it while installing (like on my SmartPhone Note2 N7100)

On my Nexus 10 the LineageOS 16.1 is more snappy at this time than 17.1

With 17.1 I had some restarts from inside the Facebook-App.

I will make a good backup of the last version of 16.1 :)
[Nexus 10 Android Development] dahawthorne:
I'm afraid that the new version was also very laggy for me. I wiped and formatted everything and clean flashed, but on initial setup it took about 20 seconds just to change from English US to English UK, so I restored back to LoS 16. Strangely, LoS 16 works really well.
[Nexus 10 Android Development] suaksoz:
[MENTION=5480152]followmsi[/MENTION] Sir how can you use LOS 17 snappily? I've made a clean install and waited about a day but it's still like my grandmother who died a few years ago (her soul RIP ?). And it is getting worse, I'm afraid it is going to have a stroke ?
[Nexus 10 Android Development] followmsi:
Thanks for reporting ..

Quickly checked my CPU cores .. can't replicate - I don't have any core running 100% .. system_server is running smooth too.

When time is left I will have to check again.
[Nexus 10 Android Development] followmsi:
As written above .. for me and my usage 17.1 is running quite good.

I will have no more time to work on Android .. not on Nexus 10 nor on my other devices.

For the moment I will continue to build 17.1 .. last 16.0 build is September.

Hopefully somebody is able to continue building 16.0 for manta .. but not me anymore.

Thanks for understanding.