[UNOFFICIAL] LineageOS 16.0 for the Project Tango Tablet (ATAP)

Search This thread

akw701

Member
Mar 26, 2016
17
4
Lehre
HP Touchpad
Huawei Mate 8
Did somebody try the lineage-16.0-20211009-UNOFFICIAL-yellowstone.zip build.
After the second reboot, the first worked seemingly well, the boot process stops after displaying the first lineage logo parts.
The battery symbol that is displayed after pushing the power buttom again, always displays a full battery, something that occured seldom before.
pushing volume + and - and power to get into recovery does not work.
Any idea what to try to get it into recovery mode?
 

npjohnson

Recognized Developer
Did somebody try the lineage-16.0-20211009-UNOFFICIAL-yellowstone.zip build.
After the second reboot, the first worked seemingly well, the boot process stops after displaying the first lineage logo parts.
The battery symbol that is displayed after pushing the power buttom again, always displays a full battery, something that occured seldom before.
pushing volume + and - and power to get into recovery does not work.
Any idea what to try to get it into recovery mode?
hold all the buttons to reset it. But yeah it works, I updated my ys myself to that build.
 

akw701

Member
Mar 26, 2016
17
4
Lehre
HP Touchpad
Huawei Mate 8
hold all the buttons to reset it. But yeah it works, I updated my ys myself to that build.
Did this for several times.Battery symbol showed always 100%. After approx. one hour of repeated tries the symbol changed to empty battery. I charged the tablet in the dock. The next morning the boot of lineage worked perfectly.
So for me the main issue remains, that the power managment is not working properly.
Right now it still shows 100% even after one hour of continous use.... I expect the tablet to switch off all of all of a sudden.
Did you work on the power management lately?
 

npjohnson

Recognized Developer
Did this for several times.Battery symbol showed always 100%. After approx. one hour of repeated tries the symbol changed to empty battery. I charged the tablet in the dock. The next morning the boot of lineage worked perfectly.
So for me the main issue remains, that the power managment is not working properly.
Right now it still shows 100% even after one hour of continous use.... I expect the tablet to switch off all of all of a sudden.
Did you work on the power management lately?
Sounds like your device is having some issues with the fuel-gauge sensor - my tablet with YouTube open just ticked down to 90% over the course of 40 min watching videos.
 

jjmcousineau

Member
Jul 31, 2013
9
5
Hello, I recently found a bunch of these tablets at work and have been trying to get them running again using lineage. I have followed everything I can find and I am running into the error 7 because I have not repartitioned.

I see previous mentions from someone with this exact problem and that instructions for this process is on the wiki but I cannot for the life of me find reference to partion, repartition psci etc on that wiki.

Any and all help is appreciated.
 

npjohnson

Recognized Developer
Hello, I recently found a bunch of these tablets at work and have been trying to get them running again using lineage. I have followed everything I can find and I am running into the error 7 because I have not repartitioned.

I see previous mentions from someone with this exact problem and that instructions for this process is on the wiki but I cannot for the life of me find reference to partion, repartition psci etc on that wiki.

Any and all help is appreciated.
 

jjmcousineau

Member
Jul 31, 2013
9
5
I have tried towel root multiple times on 2 different tangos and on multiple different wifi networks but all I get is please make sure you are connected to the internet. After that I attempted to find other root methods but none seemed trustworthy. If anyone has some idea what I might be able to do it would be appreciated.

*edited a typo
 

npjohnson

Recognized Developer
I have tried towel root multiple times on 2 different tangos and on multiple different wifi networks but all I get is please make sure you are connected to the internet. After that I attempted to find other root methods but none seemed trustworthy. If anyone has some idea what I might be able to do it would be appreciated.

*edited a typo
towelroot works - are you getting it from the official site?
Is there any reason you can't use Magisk? Maybe install TWRP 3.2.1 then flash Magisk from recovery.
magisk doesn't support 4.4
 

akw701

Member
Mar 26, 2016
17
4
Lehre
HP Touchpad
Huawei Mate 8
I have tried towel root multiple times on 2 different tangos and on multiple different wifi networks but all I get is please make sure you are connected to the internet. After that I attempted to find other root methods but none seemed trustworthy. If anyone has some idea what I might be able to do it would be appreciated.

*edited a typo
I had the same problem and could only sove it by rolling back to kitkat and trying a different superuser approach. I described it here:

With the exception of my powermanagement it works very very well, thanks to npjohnson!
 
  • Like
Reactions: npjohnson

jjmcousineau

Member
Jul 31, 2013
9
5
towelroot works - are you getting it from the official site?

magisk doesn't support 4.4
Yeah I just followed the link from the wiki. I was doing this at work and I was on the wifi there and also tethered to my cell (in case firewall rules were blocking). I may try bringing it home to try that, is there a way to test connection with whatever it's phoning home to?
 

xaxxelous

Senior Member
Jul 16, 2016
72
17
Sonora
LG V30
LG V40
I've spent all day with it and can't get tr to work either. Same error about ensuring I'm connected to the internet, but I'm also having some WiFi issues. I can connect to the internet and do a speed test most times, log into Google and open the play store, but anytime I try to download an app my WiFi symbol disappears and I get a no connection error.

Might not want to troubleshoot that since I don't need persist images, but if I did I would go to LOS 14.1 with TWRP 3.2.1 and Magisk. From there I'd follow the LOS 16 wiki. Thats how I got both my Tangos to 16 in the first place.

Edit, update: I connected a USB ethernet adapter to my dock, turned off Wi-Fi, and made sure I was connected to the internet by downloading a large file. While the file was downloading I tried towelroot and still got the same error, fwiw.
 
Last edited:

jjmcousineau

Member
Jul 31, 2013
9
5
I've spent all day with it and can't get tr to work either. Same error about ensuring I'm connected to the internet, but I'm also having some WiFi issues. I can connect to the internet and do a speed test most times, log into Google and open the play store, but anytime I try to download an app my WiFi symbol disappears and I get a no connection error.

Might not want to troubleshoot that since I don't need persist images, but if I did I would go to LOS 14.1 with TWRP 3.2.1 and Magisk. From there I'd follow the LOS 16 wiki. Thats how I got both my Tangos to 16 in the first place.
Is LOS 14 good enough to get GApps working? I just want to use this as a stationary clock/media device as I have a few docks also.
 

akw701

Member
Mar 26, 2016
17
4
Lehre
HP Touchpad
Huawei Mate 8
I think the SU is the solution. If the Super User is installed Here is how it worked for me:
I had TWRP installed first. From there I followed the thread instructions. Worked like charm. With TWRP I installed the the 14.1 rom from highwaystar_ru. No problems so far. Then I saw npjohnsons Lineage 16 and wanted to Upgrade. But being a beginner I stumbled into several pitfalls with ADB (Tablett was in recovery, but it needs to be booted into the normal system) The towelroot Su from the instructions did not work. Thought I had to roll back to kitkat. Got the Rom from the link in the TWRP thread. But next pitfall, I installed it into micro sd card folder. Did work when I shifted everything to the internal memory Backup folder. Being back on kitkat I tried towelroot again to gain SU access. No success either. But I got lucky with "SupersSU v2.82 SR5 Beta" from droidfilehost.com page.
With SU applied, knowledge that for Adb commands the tablet had to be normally booted, I followed the instructions for Lineage OS and succeeded in installing.
 

drarbo1

Member
Feb 4, 2019
18
3
Hey y'all. Admittedly, I'm not the sharpest knife in the drawer, but I have rooted my Shield tablet and re-imaged them, took Unix for the NAS class for FAA, so I may be knowledgeable enough to be dangerous. I wanted to make double sure reading the wiki instructions. My Yellowstone tablets are still Kitkat and I'm going to follow the "Update to a newer vendor firmware version" instructions first, then proceed to the "Installation" instructions, and ignore the "build yourself" and "update to newer and higher version" instructions. Am I correct in my assumption? Thank you
 

npjohnson

Recognized Developer
Hey y'all. Admittedly, I'm not the sharpest knife in the drawer, but I have rooted my Shield tablet and re-imaged them, took Unix for the NAS class for FAA, so I may be knowledgeable enough to be dangerous. I wanted to make double sure reading the wiki instructions. My Yellowstone tablets are still Kitkat and I'm going to follow the "Update to a newer vendor firmware version" instructions first, then proceed to the "Installation" instructions, and ignore the "build yourself" and "update to newer and higher version" instructions. Am I correct in my assumption? Thank you
yes
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    may i ask two questions about the dec 16th build?
    1- charging by USB MICRO stops working after installing this update. what changed in the update?(weirdness part, if plugged into a QCS 3.0, starting from a cold boot, it charges for the short boot moment then stops just as the LINEAGE logo transitions to home screen. -- wont charge when off, and wont charge when on, only this short window from boot)
    2-under display , themes, the green color if selected, turns everything blue?
    I will look into this. The drivers for the charger and the external connector (dock charging component) were written for 3.4, and the driver is SUPER hacky. I had to port it to 3.10, but it really needs a clean rewrite to play nicely. The tablet has a pretty high power budget and often the MicroUSB port might not be able to provide enough amperage while the device is in use. The NVidia charging code is somewhat cryptic and it takes a while to reverse what is actually going on. There's some odd behavior with the interrupts handling switching between USB and the dock for charging. Inside the charging IC there is a switch to enable 12V input (charging via dock), and sometimes this can get into an inconsistent state. There's technically TWO batteries wired together as one battery that requires a higher voltage (~8V) than say your typical battery which is usually running at 3.7V.

    Part of the problem is that in order to use 3.10 effectively (Secure Storage, some DRM stuff, etc...), we need ARM PSCI support (especially if we look beyond 3.10 in the future). TN8 (Shield Tablet) received this while Yellowstone was still stuck on Trusted Foundations TEE. There's a handful of binaries that use some of the newer TOS functionality as well.

    I had to kang the TN8 early bootloader (nvtboot) in order to load the newer PSCI-compatible TOS (TrustZone image) according to the newer mechanism (Yellowstone OEM bootloader doesn't support this loading mechanism). One problem is that the TN8 early bootloader doesn't support the charging or battery ICs on the Yellowstone, so the chips come up from boot in an inconsistent state that needs to be cleaned up by the kernel.

    I did come across a more recent TOS image that was released for Yellowstone that fixes some of the off-mode charging and standby/sleep charging, but it still doesn't address loading the PSCI TOS image correctly. I had to reverse engineer both bootloaders and do some patches to make it play nicely with the newer kernel as well. It may be possible to embed the TOS loading code into the Yellowstone early bootloader, but this is extremely tedious and time consuming and requires extensive testing.

    I did start writing the PSCI code from scratch in assembley for their PSCI implementation so I could have u-boot replace the early stage bootloader, but it requires a significant amount of effort and intimate knowledge of the hardware. I simply don't have the time to do so.

    I took a hiatus from programming about a year ago because I had spent about 18 months working on this device non-stop and other security research work and burned out. It wasn't fun for me anymore and I didn't have as much time. I will have a bit more time now and the will is returning so I am hoping to pick up where I left off.
    2
    Many thanks, the November Version works again very well!!!

    Regards
    Send from my freshly updated Project Tango Tablet
    1
    And to answer the question - It's a hybrid of tn8's (Shield Tablet) nvboot and a heavily disassembled/reassembled applications bootloader to support the newer TLK/Secure World and PSCI kernel from tn8, allowing us to use kernel 3.10 from nv-tegra as opposed to 3.4 from Google. Much cleaner, must snappier, plus it lets us use Shield Tablet proprietary files for graphics, etc. which has an official Nougat release, which is way easier to work with than KitKat blobs from stock. We split out and use as many tn8 blobs as we can, and yellowstone stock where we need to.

    It was designed almost entirely by @ryanbg -he's a legend, and one of the big reasons this device got anything more than cm-14.1 - I did most of the Android-side bringup (which was rough), but his work on kernel and firmware enabled it :)

    I was looking into it seeing if maybe I could help. I had been looking at the tos.img alone thinking that was it. But wow man I probably would have never gotten to the bootloader like that. Thank you and @ryanbg for putting all the work in.
    1
    I'm using this : https://updater.oddsolutions.us/yellowstone#/devices/shieldtablet/builds
    And this topic is in Shield Tablet.
    Is it a bug from the new XDA ?
    Project Tango has no forums of it's own, so we are using Shield Tablets as a home for now.

    Additionally, the shiledtablet builds you linked are unsupported test builds - there will be no support provided for those.
    1
    may i ask two questions about the dec 16th build?
    1- charging by USB MICRO stops working after installing this update. what changed in the update?(weirdness part, if plugged into a QCS 3.0, starting from a cold boot, it charges for the short boot moment then stops just as the LINEAGE logo transitions to home screen. -- wont charge when off, and wont charge when on, only this short window from boot)
    2-under display , themes, the green color if selected, turns everything blue?