yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] followmsi:
Some heating is normal .. depends on your heating.

Not sure if we can improve your situation.

Maybe some apps going crazy .. you did test clean full install ?

There are no other kernels .. except you make a new one :)
[Nexus 10 Android Development] followmsi:
Lineage-15.1 - February 2019

https://review.lineageos.org/q/topic:"O_asb_2019-02"

lineage-15.1-20190213-UNOFFICIAL-manta.zip

Changes:

- Google Security updates -> February 2019

- Latest LineageOS changes

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

Enjoy :p
[Nexus 10 Android Development] xrad:
Thank you once more [MENTION=5480152]followmsi[/MENTION] for your efforts!

So my battery was dying, randomly shutting down the device. I bought a replacement, installing it was quite easy. But here's the thing: while the battery seems to work, its capacity is always reported as 100%. (everybody, please spare me the obvious jokes :p) I check the ds2784 fuelgauge and the culprit might be that the current is always reported as 0:

/sys/devices/w1_bus_master1/32-000841866efe/ds2784-fuelgauge/power_supply/ds2784-fuelgauge # cat voltage_now
3952774
/sys/devices/w1_bus_master1/32-000841866efe/ds2784-fuelgauge/power_supply/ds2784-fuelgauge # cat current_now
0

There could be an electrical problem, I don't know yet.

But I read a bit in the datasheets of the ds2784 and there is an EEPROM with factory/calibration data. I'm wondering - does Android have a way to read/write/re-init this information? How could I find out if it's somehow gone bad? Neither TWRP nor Android have i2c tools included. Any idea?

Edit: I just checked my dmesg logs and found a ton of "Division by zero in kernel." errors. Looking at drivers/power/ds2784_fuelgauge.c in the kernel I see a few division operations where a value is divided b the contents of the DS2784_REG_RSNSP register - which is the value in the EEPROM defining the sense resistor used to measure the current! Now these are all educated guesses, but I could be on to something here.

Does https://github.com/followmsi/android_kernel_samsung_manta contain a working build script?
[Nexus 10 Android Development] followmsi:
No changes since 2013 .. but maybe you find the culprit.

Sorry .. old build scripts, not tested.

Just set GCC 4.8 or 4.9 as toolchain and your compilation should work.

https://android.googlesource.com/pl...rm/arm-eabi-4.8/+/refs/tags/android-8.1.0_r61

https://android.googlesource.com/pl...androideabi-4.9/+/refs/tags/android-9.0.0_r31

Pls let me know your results ..

Cheers
[Nexus 10 Android Development] xrad:
Will do.

How do you build the kernel though?
[Nexus 10 Android Development] xrad:
[MENTION=5480152]followmsi[/MENTION] As you indicated the buildscript included in your kernel is ancient. It seems to be straight from some other dev's desk, including references to his home dir. It seems to rely on AnyKernel2, but it looks like a dead end. If you have a minute it would be nice if you could post some build instructions, or point me to them if I was too stupid to find them.

As for the issue at hand: I refitted the old battery and the system was able to display charging current. So I think there's something fishy with the replacement battery and I'll probably just return it. No need to waste more time on this. I'll just have to see how long I can put up with the fading battery or find a new source.

Does anyone around here have some experience with replacement batteries for the N10? What to I have to pay attention for? The one I got seemed fine from what was printed on it, but clearly it's not working.
[Nexus 10 Android Development] :
Good experience made with this eBay seller and his battery for my Nexus 10, now working for a year or so: https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.de/ulk/itm/123487031006
[Nexus 10 Android Development] xrad:
Thanks. I had bought this one. From the pics I'd say it's identical to yours. The part I actually received hat a black connector though, so I reckon it's not exactly the same after all. FWIW, I received another one first which did not work at all; the device didn't even power up. I guess there is very little quality control applied to the production process, so you have to expect a high dropout rate. Could very well be that a third sample from that vendor would work. I'll now return the items and try another source.
[Nexus 10 Android Development] followmsi:
In case you still want to build your own kernel ..

#!/bin/bash

cd /full-path-to/android_kernel_samsung_manta/
make clean
make mrproper
echo "clean !"

export ARCH=arm

export CROSS_COMPILE=/full-path-to/arm-linux-androideabi-4.9/bin/arm-linux-androideabi-

make followmsi_defconfig

make -j8

exit 0

good luck with your battery replacement/issue !

Cheers
[Nexus 10 Android Development] xrad:
Thanks I might actually do that. These bare kernel compile commands are staight-forward, But from past custom kernel experiments on other devices I recall that I need a small build environment/RAM disk to create a boot.img. Or is that no longer the case?
[Nexus 10 Android Development] followmsi:
Yes .. still required.

Use lazyflasher or anykernel for installing kernel binary.

Unzip my latest kernel and just replace image file and rezip.

Flash via twrp.

This way you only replace kernel binary and not ramdisk.

https://drive.google.com/drive/mobi...tTSnbGglhc?usp=drive_open&sort=13&direction=a

Good luck !
[Nexus 10 Android Development] xrad:
Just to report back on this. I have now installed this battery (German vendor) and it seems to work fine. It was even pre-charged to 40% which was a pleasant surprise. It charged fine and seems to hold power very well. I'm very happy with it.
[Nexus 10 Android Development] TiggaZ:
Is the 16.0 release ready enough as a daily driver or makes the HWC issue it unusable with the broken icons?

I am currently on a older 14.0 version and wonder if I should try the 15.0 or the 16.0 release.

Thanks for the help and keep up the good work.
[Nexus 10 Android Development] rogers11:
I use the 15.1 version and the only thing missing for me is the Camera feature. No other problems.
[Nexus 10 Android Development] james-h:
Some time ago, [MENTION=8470938]gvh1234[/MENTION] mentioned a problem in this thread with wake on sleep. I've seen the same problem with a recent build.

Had a (quick) look and found probable root cause & a workaround.

Here it is, in case others are facing the same problem:

There's a bug with Expanded Desktop in LOS 15.1

Bug triggers when:

Settings > Display > Advanced > Expanded Desktop is set to global ON

Device goes to sleep (either through timeout or through user tapping the power button).

Device display is now unresponsive to the usual wake-up inputs.

Simple workaround is: avoid using global ON for Expanded Desktop. Enable Expanded Desktop for individual apps.

There's mention of the same problem on the LineageOS Gerrit site (See Bruno Martins' post of Dec 03 2018, under item 230016 - "Implement expanded desktop feature". I don't have ability to post links).

As a bit more detail, when the bug is triggered, Android OS remains active & is available via adb. A repeating loop of logcat entries is generated. The relevant line reads "E WindowManager: Performed 6 layouts in a row. Skipping".

I saw the problem with a fresh ROM build, using followmsi's manta-lineage-15.1 repo source and built a couple of days ago. It was a clean build with no source code changes made.

Thanks [MENTION=5480152]followmsi[/MENTION] for keeping my cherished Nexus-10 happy.

This is my first post - so please shoot me down gently.
[Nexus 10 Android Development] followmsi:
Thanks for your (first) post, your investigation and the workaround.

Enjoy your weekend !
[Nexus 10 Android Development] followmsi:
Just take backup of data and have try yourself ..
[Nexus 10 Android Development] dimonjj:
How to instal lineage 16 after manta-Classic_Pie_02-2019_AOSP_9.0.0_r31_followmsi.zip?

Error 7
[Nexus 10 Android Development] followmsi:
Error 7 means old twrp version

Error 70 means no space left on system

Good luck !
[Nexus 10 Android Development] geronimoge:
First of all, thanks a lot for keeping our mantas alive.

Is it possible, that Magisk 18 isn't working with your lineage v15.1 and v16.0? If so, which version should I choose?

And it would be great, if post #1059 for repartitioning could be linked in OP. It helped me a lot getting the process done.

Thanks!
[Nexus 10 Android Development] IOtacle:
No problems here with 15.1 and Magisk 18.1 / M-Manager 7.0.0
[Nexus 10 Android Development] piit79:
What seems to be the problem?

Sent from my OnePlus 6T with a rubbish gimmicky bloody annoying unreliable in-display fingerprint reader using Tapatalk
[Nexus 10 Android Development] geronimoge:
After installing the root check failed.

Probably because Magisk Manager wasn't installed automatically with flashing Magisk.

After flashing Magisk v18.0 and installing Making Manager manually as second step everything is working fine.

I wasn't used to that since until this time the Manager was installed with flashing Magisk automatically.
[Nexus 10 Android Development] followmsi:
Have added #1059 to OP ..

https://xdaforums.com/showpost.php?p=78219279&postcount=1059
[Nexus 10 Android Development] asianmulder:
i'm on lineage-16. I want to revert to stock lollipop as looking to sell my nexus 10. L16 was great but limited by camera support and photos app not working as a consequence. Device not rooted but has latest version of TWRP installed. Having trouble finding stock ZIP to flash via TWRP. Failing that, how can I revert back to Lollipop? Also what about the partition that has been resized?

I have the stock rom from the google DB but it is not flashable via TWRP.
[Nexus 10 Android Development] piit79:
Just flash the stock ROM from Google in fastboot, that's the best way to revert to stock.

The resized partition shouldn't matter. There will just be some spare space in the system partition at the expense of smaller cache.

Sent from my OnePlus 6T with a rubbish gimmicky bloody annoying unreliable in-display fingerprint reader using Tapatalk
[Nexus 10 Android Development] james-h:
I've done exactly this recently, when I was experimenting with followmsi LOS 15.1 build. I rolled back to Lollipop a few times as part of my experiments.

The important thing for me was to realise TWRP would not work with the Google stock ROM images. Using 'fastboot' command-line tool was the answer. This worked well.

The Google factory ROMs are still available to download for manta/Nexus-10. They come packaged as a zip file. You unzip this file, then you should see a script file (.bat for Windows, .sh for Linux). Connect your device, then open a terminal and run the script with your device connected. The script wipes everything on the device (including the bootloader) & flashes all partitions.

Also - recommend you make sure your battery is fully charged (as you really don't want to lose power partway through flashing the bootloader).
[Nexus 10 Android Development] asianmulder:
Noob question...the device need to be in recovery mode?
[Nexus 10 Android Development] james-h:
...and fairly-noob answer:

"Recovery mode" means the device has been booted using the operating system installed to the Recovery partition. TWRP is an example of this & is installed to the Recovery partition.

You need to be in Bootloader mode for fastboot.

You get into Bootloader mode with Nexus-10 by holding down Power + Vol-up + Vol-down all at the same time. Wait a few seconds until the device buzzes. Wait another couple of secs, then Bootloader screen appears.

Bootloader is a very simple system, used to load either Recovery or main System (e.g. LineageOS or Lollipop).

Once in Bootloader mode, you can connect device to PC and send fastboot commands.
[Nexus 10 Android Development] asianmulder:
Many thanks. Once i did this from the ADB folder via fastboot, i think it has worked. Initially just had the "no command" icon on screen but that seems to have disappeared and now seems to be booting up!
[Nexus 10 Android Development] james-h:
Good to hear.

The "no command" icon is displayed by the factory Recovery system. It is quite basic when compared to TWRP.

So I guess your Recovery partition has been updated with factory Recovery system.

This is good & what you'd expect with a successful re-flash back to stock.

With the next step, I also found it took quite a long time for first boot into Lollipop System. Think it took a few minutes to get to the screen where Android updates itself. Just keep waiting. With the charger plugged in...!
[Nexus 10 Android Development] asianmulder:
The above...exactly what happend! Shame as I loved the tablet. Have a Samsung Tab S3 but no match for the N10 in terms of love for it! If only the camera worked on the Lineage ROMS, i'd have stuck with it.

Thanks again dude.
[Nexus 10 Android Development] TiggaZ:
Just to answer my question and maybe give advise to others.

No, for me it is not ready as a daily driver.

Black home screen is no problem. Working with no icons is managable but very ugly.

But the show stoppers are bad battery time (no deep sleep), some video apps like Twitch are not working and the system feels a bit slugish on some apps like Firefox.

But thank you so much for your dedicated work :good:.

I will return to 15.1 and try 16.0 some time in the future.
[Nexus 10 Android Development] thomorph:
Hi,

Can I use audio kernel on lineage 13?

Thanks
[Nexus 10 Android Development] followmsi:
Pls test yourself .. no idea if it's working.
[Nexus 10 Android Development] followmsi:
March 2019 ..

lineage-16.0-20190308-UNOFFICIAL-manta.zip

Changes:

- Google security updates -> March 2019

- Latest LineageOS changes

Sources:

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

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-15.1 - March 2019

https://review.lineageos.org/q/topic:"O_asb_2019-03"

lineage-15.1-20190310-UNOFFICIAL-manta.zip

Changes:

- Google Security updates -> March 2019

- Latest LineageOS changes

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

Enjoy :p
[Nexus 10 Android Development] raposso:
Selinux

Is there a way to activate in a Per ant way SELinux

Regards
[Nexus 10 Android Development] pjotrski1000:
I installed lineage-16.0-20190308, repartitioned, installed pico gapps. Everything working as expected. Cool, my old Nexus 10 with new life! :)

I would like to note that the 'icon issue' with this build only appeared after installing Magisk (from recovery) + Magisk manager. Has anyone else noticed this?

By the way, I just noticed changing the shape of the icons under 'home settings' made them visible again (first only the icon labels were visible). FYI
[Nexus 10 Android Development] urartu99:
I was using lineage-14.1 for almost a year now and it is working very well.

No battery drains, freezes, reboots. Very happy with it. The only issue is the IMDB app which crashes because of some conflict with the hardware.

I wonder if it makes any sense to upgrade to v 15 or 16. Any thoughts?
[Nexus 10 Android Development] stunned:
15 is very stable for me and much better than 14 was when I tried that, but 14 might have improved since. I was mainly using Omni in Nougat days
[Nexus 10 Android Development] urartu99:
Thanks for the recommendation.

Can I ask you for a favor? Can you install IMDB and run few trailers. Does your N10 reboot as well? If not, then I would definitely upgrade to v15! Thanks.
[Nexus 10 Android Development] xrad:
I'm running 15 here, too. Very stable, very recommendable. FWIW: Occasionally it does crash in video apps, but it has always done that, on any system I ever installed. It's probably a bug in the blobs or even the video hardware and seems to be dependent on specifics of the video mode or encoding. It never crashes with Netflix or Amazon video or MX player, but it quite predictably with Eurosport player. Again, I don't think this is related to this ROM, video has always been a bit of a hit and miss on this device.
[Nexus 10 Android Development] stunned:
There is some specific episodes in Netflix that are very likely to crash. Some episode of Sword art online for example was sure thing to crash, but it is very rare. But other than that it is very stable. IMDB showed couple times some artifacts in video that I find related to crashes, but it didn't crash with couple videos I tried.

Eurosportplayer is sure crashing a lot. Finnish broadcasting company YLE has setting for its player to use Exo or native video player and native is stable, Exo always crashes.
[Nexus 10 Android Development] pottendo:
Hi,

I'm using LOS16-190308. Form time to time I need VNC to control a RPi. Since a few weeks connecting the app (VNC Viewer) to the RPi crashes my N10 to a reboot.

I tried reinstall (system and app) and cache/data wipes, but no success.

Can anyone confirm a workng VNC setup with your N10?

Thx for any response, pottendo
[Nexus 10 Android Development] followmsi:
April 2019 ..

lineage-16.0-20190404-UNOFFICIAL-manta.zip

Changes:

- Google security updates -> April 2019

- Latest LineageOS changes

Sources:

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

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-15.1 - April 2019

https://review.lineageos.org/q/topic:"O_asb_2019-04"

lineage-15.1-20190407-UNOFFICIAL-manta.zip

Changes:

- Google Security updates -> April 2019

- Latest LineageOS changes

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

Enjoy :p
[Nexus 10 Android Development] purple patch:
Thanks very much for keeping this up to date. Just got Nexus 10 (I'm using it as a IOT wall display). V16 runs great and your clear instructions made it a breeze to flash. Cheers.
[Nexus 10 Android Development] pottendo:
Hi,

the crash is reproducible also in LOS16 190407 on my N10. :confused:

Pls. try the VNC Viewer app and make quick check (you don't even need a VNC server, just connect to some IP and see if the tablet reboots or runs into a timeout).

Thanx in advance, pottendo
[Nexus 10 Android Development] followmsi:
Confirmed... Kernel crash.

Most probably this crash should have happen on lineage-15.1 too .. Not sure about Nougat.

Did you test on older lineage versions too ?

If the problem is new in Pie we may find the related change/sources.

If it's an "old" problem, like described a few threads above, we will not be able to solve it.

Right now I have no more time left to work on manta .. (Android in general).

Not sure when I will be able to look into this issue.

Cheers
[Nexus 10 Android Development] pottendo:
Hi,

Will check. It did work earlier this year and for sure on LOS 16 (Pie). So there's a chance, it can be found.

Will revert back to feb or jan releases for a check.

Bye pottendo
[Nexus 10 Android Development] dabanhfreak:
Hi, I was about to flash, but the md5sum check revealed different values, downloaded twice on both tablet and PC.
[Nexus 10 Android Development] xrad:
Checks out fine for me:

$ md5 lineage-15.1-20190407-UNOFFICIAL-manta.zip
MD5 (lineage-15.1-20190407-UNOFFICIAL-manta.zip) = c1e00384475591ce7badbef28f2f5499
$ cat lineage-15.1-20190407-UNOFFICIAL-manta.zip.md5sum
c1e00384475591ce7badbef28f2f5499 lineage-15.1-20190407-UNOFFICIAL-manta.zip

$ md5 lineage-16.0-20190407-UNOFFICIAL-manta.zip
MD5 (lineage-16.0-20190407-UNOFFICIAL-manta.zip) = ac0ceef51ce34bff20a75dfa5903084f
$ cat lineage-16.0-20190407-UNOFFICIAL-manta.zip.md5sum
ac0ceef51ce34bff20a75dfa5903084f lineage-16.0-20190407-UNOFFICIAL-manta.zip
[Nexus 10 Android Development] followmsi:
If you are root ..

setenforce 1 - wil activate selinux (enforcing)

setenforce 0 - will disable selinux ( permissive - default value )

This settings are not persistent .. if you reboot you are back to permissive anyway.

You may face very strange issues when switching to enforcing selinux.

Hope this helps ..
[Nexus 10 Android Development] dabanhfreak:
Here's mine.
[Nexus 10 Android Development] pottendo:
Hi, tried with Jan and Feb releases (also with gapps from these months) and now VNC is crashing the tablet.

So I conclude, that the bug is now triggered, because today's 'VNC Viewer' App (or other lowlevel libraries) has changed somehow. So it might be, that also LOS 15 releases are affected(now).

Maybe someone here with LOS15 active can give it a try - feedback would be very much appreciated.

Thanx, pottendo
[Nexus 10 Android Development] pottendo:
Hi.

just to let you know, I've now tested MultiVNC and it works fairly well on my N10 for my purpose. :fingers-crossed:

bye, pottendo
[Nexus 10 Android Development] goodflood:
There are reports of TWRP 3.3.0-0 failing on devices. My manta got bricked, when I tried to use the TWRP install method. See more of my ticket on github here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1446. So be aware!

EDIT: Anyone know what I can do to get back to TWRP twrp-3.2.3-0-manta.img or get back into system? ADB devices does not show anything.

EDIT2:

So, after researching the TWRP MANTA forum, I share the frustration of user: aheeejd...

<FRUSTRATION> "WTF and this blows" (and a few other four letter words of my own : ) </FRUSTRATION>

PROBLEM: https://xdaforums.com/showpost.php?p=66195748&postcount=653

He was able to fix it using WUGS Toolkit

WUGS TOOLKIT: https://xdaforums.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452

which asks to flash an older MANTA recovery

SOLUTION: https://xdaforums.com/showpost.php?p=65352407&postcount=643

which I did; then, I updated the TWRP to latest working and flashed [MENTION=5480152]followmsi[/MENTION] latest manta ROM

https://xdaforums.com/nexus-10/development/rom-lineage-14-1-20170216-unofficial-t3557735

So, this has happened at least once before in 2016... [not trying to piss anyone off]. I will be careful next time~!
[Nexus 10 Android Development] xrad:
You're probably aware, but to explicitly state this: flashing TWRP requires the device to be in bootloader mode where you operate it using the "fastboot" tool - not "adb". In Bootloader mode it is expected that "adb devices" does not list anything. You can start the device in bootloader mode using Vol-Up+Vol-Down+Power.

Also, probably too late to be really useful to you: you can try a TWRP without flashing using "fastboot boot twrp.img", also from bootloader mode.
[Nexus 10 Android Development] followmsi:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1446#issuecomment-486139886
[Nexus 10 Android Development] guidol:
I hadnt any problem with 3.3.0-0 on my

- Nexus 10

- Samsung SM-T900 (12.2" Tablet)

- Samsung GT-N7100 (Smartphone)
[Nexus 10 Android Development] goodflood:
[MENTION=3630898]guidol[/MENTION] No, apparently I ran into a problem flashing it via TWRP itself. There is a possibility of what [MENTION=5480152]followmsi[/MENTION] said... I might have flashed it to the boot partition. Maybe I did, the buttons are next to each other. The other possibility is that the underlying code might point in the wrong place (boot, recovery) and I don't want to go reproducing and experimenting; so, I left the issue as is. I will be extra careful next time!
[Nexus 10 Android Development] followmsi:
Just flash TWRP recovery.img onto boot partition - for testing !

You should get the same problem like before.

Now you know how to fix it again. :)

Cheers