yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] DaRkSkYxP:
Basically you have to unlock the bootloader and then follow the instructions on the mtk-client page. Make sure to make a backup first and to install the magisk version listed. Afterwards you have to update magisk a couple of times. I have not gotten viper4android or James dsp to work yet. Also just to mention magisk no longer has an online repo to download from. I will put links below. This software should work for a lot of other devices that have mtk processors as long as the bootloader can be unlocked. For a long time I gave up on rooting this phone because I couldn't find a stock rom / boot.img for it. Another thing to mention is that you may have to change the extension of the boot image file around from .bin to .img and vice versa. Also the latest usbdev driver crashed my windows 10 but installing the version before the latest didn't crash my windows 11 install. I just did all this about 2 days ago so I am still finding issues that need to be worked on. I am not a software developer by any means. So far I have not gotten any audio mods to work but I have had issues with them on many devices. I can confirm that the backup and restore of apps and their data work on the 2 U307AS that I have. Getting the latest magisk alpha image to stick seems to not be working with the direct install method. It doesn't look like we can use magisk unless it is the alpha version. I have not tried patching the latest magisk into the boot.img and then flashing it with mtk-client yet. Another note (lots of them, lol) is I didn't know where the mtk-client program was looking for the patched boot.bin when it came to the part about flashing with an empty vmeta whatever file. I ran the command anyways which gave the error about the missing boot.bin file but it did do the empty vbmeta flash so I just flashed the patched boot.bin with the mtk-client gui afterwards. Hopefully no one hosed their windows os because I failed to mention the issue with the usbdev driver.

GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool

MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.

github.com

GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it

A module manager for Magisk because the official app dropped support for it - Fox2Code/FoxMagiskModuleManager

github.com
[Android Q&A, Help & Troubleshooting] DaRkSkYxP:
Yes
[Android Q&A, Help & Troubleshooting] Tigerevo:
Yup I redid one today 4-5-23 and root and no dm verity issue and network unlocked.
[Shield Tablet Original Android Development] npjohnson:
Google Project Tango Tablet

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

[/CENTER]

Introduction:

This is the Unofficial Lineage OS 16.0 thread for the Google Project Tango Tablet, codename yellowstone.

How to Install:

Please follow the instructions on our Unofficial ODS Wiki page here.

If you don't follow these instructions, please don't expect support here. We also don't support 3rd party add-ons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.

Known Issues:

Camera's and flashlight don't and likely won't ever work due to incompatibilities in proprietary binaries.

Due to the fact the cameras are broken, the ATAP/Tango apps will crash upon opening.

USB Tethering is broken for _some_ people.

SELinux is permissive (if you're a developer, you can help on this one!)

Download:

npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps/Pixel goodies.

Add-ons (WeatherProviders/AddonSU packages

How to go back to stock:

Follow the ODS Wiki Guide here here starting at step two, except instead of downloading/using `yellowstone_pie_psci.zip`, use yellowstone_kitkat_stock.zip

XDA:DevDB Information

[UNOFFICIAL] LineageOS 16.0 for the Project Tango Tablet (ATAP), ROM for the Nvidia Shield Tablet

Contributors

npjohnson, ryanbg, steel01

Source Code: https://github.com/LineageOS/android_device_google_yellowstone

ROM OS Version: 9.x Pie

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Latest Stock KitKat

Version Information

Status: Stable

Created 2020-10-16

Last Updated 2020-10-16
[Shield Tablet Original Android Development] Oswald Boelcke:
Thread closed on request of OP @npjohnson

Regards

Oswald Boelcke
[Shield Tablet Original Android Development] npjohnson:
Mod Edit

Duplicate thread, please visit the original one: https://xdaforums.com/shield-tablet...ageos-16-0-project-tango-tablet-atap-t4177577
[Wing, P4350 General] phony:
I am using aserg windows mobile 6.1 rom and I have noticed a creeping problem. As time goes on, I can only seem to run 1 substantial program at a time.

For instance, if I try to run any of these programs in tandem:

HTC audio manager or Windows Media Player

Mundu mobile messenger

Opera

Internet explorer

Dictionary software

Outlook mail (sms/email)

Skype

the program in the background always closes. This is especially annoying when for instance I am listening to music and I get an email or sms, I go to check it and my music player just closes. Same if I try to browse the web and listen to music or check an sms, It is very annoying.

What causes this function in windows mobile and how do I turn it off?

As for memory, when I start I have 13-14 megs free memory. Any of these programs take an absolute MAXIMUM of 4-5 megs at peak usage. I should be able to run at least 2 together without a problem, and if another one does nto have enough memory, it shoudl just say so and not start, but not close out other programs...

I also have about 4-5 megs of free storage space on the phone.

any ideas on this one?
[Wing, P4350 General] phony:
It seems as time goes on, I can't seem to run any more than 1 program simultaneously...
[Wing, P4350 General] Kar98:
Reduce the amount of file space your browser have allotted for cache files and history.
[Wing, P4350 General] phony:
My browser cache for both Opera and PIE are both pointed at the storage card which has about 500megs free. This problem occurs even if I am running any programs though, not just browsers...
[Wing, P4350 General] ivanmmj:
It's either the memory shortage (which some of those programs can actually take much more than 4 or 5 mb to run.) Or you have it set to close on tap, within the task manager/x-button, instead of close on hold.
[Wing, P4350 General] phony:
I use batterystatus, and it is set to tap and hold X to close, but I never use the X, I simply go to the start menu and open another program, then when I try to switch back to the other program, it is closed already.

How do I check if it is a memory problem?

For instance, if I run HTC audio manager, then get a message, I click reply, then after about 3 seconds into my reply HTC audio manager closes.

is there any way I can "force" the programs to stay open? Even if I were to launch a new program and it does not have enough memory, it woudl just not open rather than closing an existing open program...
[Wing, P4350 General] DarrenUtd:
To me, it sounds like you are running out of RAM, and programs that were running in the background are automatically closed. I'm not affiliated with Windows Mobile and hence not an expert, but I believe this (closing previously open programs rather than the new one) is the expected behavior in WM. Imagine getting a phone call and the phone app not opening since there's not enough memory because the OS didn't automatically close background programs...

I don't know of a way of changing the memory management behavior, but maybe someone else here does? I'd argue that you wouldn't want to anyway.

I'd suggest that you DO use the X button to close programs, otherwise I guarantee you will run out of memory and things will close automatically anyway. The difference is you won't have any say in what gets closed at that point. I added programs that I don't want to close with the X button (like Live Messenger) to the exclusive programs list in the Task Manager.

Second, I'd suggest you take any steps you can to increase your original pool of memory.
[Wing, P4350 General] phony:
Darren, I understand your point, but it seems as if I have plenty of memory, and I can only run 1 program at a time. I don't mind so much the behaviour, it is just at the point of being ridiculous when I can only run 1 program at a time.

So you think that starting with 13-14 megs of free memory is not enough? How would I go about increasing this original pool of memory?

Also, even it I use the X button to close programs, that does not solve my problem anyways, whichever program is not in the foreground seems to close by itself anyway...
[Wing, P4350 General] DarrenUtd:
phony, I understand your frustration. I have had low memory problems myself, and I know that programs running in the background will close when that happens. That's why when I read your post it sounded like a memory issue to me.

I ended up tweaking a few things to try to get more free memory, like not running certain processes or services automatically at startup. I'm not sure if it is relevant to the ROM you are running, but see http://xdaforums.com/showthread.php?t=312312.
[Wing, P4350 General] live4nothing:
This is definitely a memory problem. When the free program memory is lower than about 1MB (don't remember the exact number), the WIndows Mobile will send a WM_HIBERNATE to all the running program to release all the possible resources. If the memory goes lower, it will broadcast another message called WM_CLOSE to close all the background apps to release more memory. The only reason for apps that close on themselve is either low on mem or there are some apps in the background (maybe a virus) sending WM_CLOSE every now and then. To be honest, to have less than 15 megs of ram to start with is NEVER enough. Try to change the pool size if you don't like any of the great roms here. Hope this help.
[Shield Tablet Original Android Development] npjohnson:
Google Project Tango Tablet

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Unofficial Lineage OS 16.0 thread for the Google Project Tango Tablet, codename yellowstone.

How to Install:

Please follow the instructions on our Unofficial ODS Wiki page here.

If you don't follow these instructions, please don't expect support here. You NEED to flash the PSCI firmware via the process described in the wiki above, or you run a significant chance of bricking your device.

We also don't support 3rd party add-ons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.

Known Issues:

Camera's and flashlight don't and likely won't ever work due to incompatibilities in proprietary binaries.

Due to the fact the cameras are broken, the ATAP/Tango apps will crash upon opening.

USB Tethering is broken for some people.

SELinux is permissive (if you're a developer, you can help on this one!)

Downloads:

npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps/Pixel goodies.

Add-ons (WeatherProviders/AddonSU packages

How to build yourself:

Follow the ODS Wiki Guide here here, except just after running

. build/envsetup.sh

run

repopick -f 279494

then proceed as described.

Returning to Stock:

Follow the ODS Wiki Guide here here starting at step two, except instead of downloading/using `yellowstone_pie_psci.zip`, use yellowstone_kitkat_stock.zip

XDA:DevDB Information

[UNOFFICIAL] LineageOS 16.0 for the Project Tango Tablet (ATAP), ROM for the Nvidia Shield Tablet

Contributors

npjohnson, ryanbg, steel01

Source Code: https://github.com/LineageOS/android_device_google_yellowstone

ROM OS Version: 9.x Pie

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Latest Stock KitKat

Version Information

Status: Stable

Created 2020-10-16

Last Updated 2020-10-16
[Shield Tablet Original Android Development] xaxxelous:
Thanks!

Could be me, but it looks like the links to the add-ons are 404. These should work, right?

https://download.lineageos.org/extras
[Shield Tablet Original Android Development] ShapeShifter499:
I wanted to ask, what exactly needed changing to the bootloader stuff that allows newer custom ROMs to boot? I'm legitimately curious and I would like to know if those modifications basically open it up so that it all lands on the OS side for getting stuff like cameras working in the future if that's even possible.

---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------

The link provided is working for me but I don't see why you couldn't use those extras. Just make sure to grab the ones for LineageOS 16.0. But [MENTION=5848265]npjohnson[/MENTION] please correct me if I'm wrong.

EDIT: The main link works to the list of extras downloads but none of the extra downloads on the page work.
[Shield Tablet Original Android Development] ShapeShifter499:
there is an issue with the script.

[ransu@Y40-80 yellowstone_pie_psci]$ ./flash.sh

Nvflash 4.13.0000 started

unknown command: --g

[ransu@Y40-80 yellowstone_pie_psci]$

there appears to be a typo. The last part of the command seems to be --go Got it working here

---------- Post added 17th October 2020 at 12:15 AM ---------- Previous post was 16th October 2020 at 11:48 PM ----------

Unless I'm wrong there's also a typo on the wiki page you made.

Lines like:

With the device powered off, hold Volume Down + <kbd+ Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select

Should probably be like:

With the device powered off, hold Volume Down + Volume Up + Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
[Shield Tablet Original Android Development] ShapeShifter499:
Well I did some testing and for the most part the tablet works better than it's ever had. Before I had an issue with it powering off with a "dead battery" but flashing a full charged battery icon after powering off. That issue has gone away now.

Thank you and anyone who has helped bring this ROM to life, it's really amazing to see newer software working so well on these old tablets. I honestly didn't think it would ever happen.
[Shield Tablet Original Android Development] npjohnson:
Fixed.

Fixed.

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 [MENTION=766721]ryanbg[/MENTION] -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 :)

Fixed.

Yeah, that was an old bootloader bug. Plus we swapped to newer battery graphics to match Lineage branding :cool:

Also, not responding to anyone in specific, just noting, I also added instructions to build at home to the OP!
[Shield Tablet Original Android Development] ShapeShifter499:
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 [MENTION=766721]ryanbg[/MENTION] for putting all the work in.
[Shield Tablet Original Android Development] ShapeShifter499:
So I have a new issue. My IMEI is blank and my sim card doesn't work. I had this sim working before on stock firmware, service through t-mobile

---------- Post added at 02:46 AM ---------- Previous post was at 02:25 AM ----------

I redownload the zip and the script inside still has an issue for Linux

[ransu@Y40-80 yellowstone_pie_psci]$ ./flash.sh

Nvflash 4.13.0000 started

unknown command: --g

[ransu@Y40-80 yellowstone_pie_psci]$
[Shield Tablet Original Android Development] npjohnson:
This is weird... I use t-mobile on yellowstone - and it works fine. Can you get me logs?
[Shield Tablet Original Android Development] ShapeShifter499:
I was able to use the package you uploaded to revert to kitkat stock and confirmed the t-mobile sim works with this tablet. It just doesn't work on the latest build you have.

This is from a fresh reinstall. Installed are the LineageOS Recovery (lineage-16.0-20201009-recovery-yellowstone.img), the LineageOS 16.0 main build (lineage-16.0-20201009-UNOFFICIAL-yellowstone.zip), and the LineageOS SuperSU add on (addonsu-16.0-arm-signed.zip). I grabbed a logcat from first boot, I tried to use the option to use the cellular network which failed and I skipped all google sign in so I could try toggling cellular network in the settings.

Logcat: https://gist.github.com/ShapeShifter499/51f14342a14416a44ed1fdec27c071cc

Here is one more logcat, taken after first boot. I toggled the "Airplane mode" in settings to no avail, SIM was still not detected and no network connection was made over cellular.

Logcat: https://gist.github.com/ShapeShifter499/856e638f29e33f1aac156ca19dc2c790
[Shield Tablet Original Android Development] npjohnson:
Dmesg as well pls
[Shield Tablet Original Android Development] ShapeShifter499:
Here is a dmesg

https://gist.github.com/ShapeShifter499/1912a442e3887df9458fa7d6a73828ee
[Shield Tablet Original Android Development] thew-tab:
I tried to install the recovery listed in the downloads page. It failed and said-- FAILED (remote: (InvalidSize)) I copy and pasted the name of the file, so that should have been ok. Not sure what I did wrong, and ideas would be helpful.
[Shield Tablet Original Android Development] npjohnson:
Sounds like you didn't repartition yet...
[Shield Tablet Original Android Development] thew-tab:
I didn't seek anything in the wiki about how to partition, unless I completely missed, thanks for the quick response.
[Shield Tablet Original Android Development] npjohnson:
It's literally the first several pages of the wiki.

The PSCI firmware package.
[Shield Tablet Original Android Development] ShapeShifter499:
[MENTION=5848265]npjohnson[/MENTION] If I wanted to fork some of the repos to do my own edits, tests, and maybe port a different ROM to get working. Which of the repos contain the latest accepted edits? The LineageOS github ones or the ones on your own github? I figure at least I would get the proprietary blobs from your github or the last ROM.

Also got any ideas about the SIM card issue? I suspect this error I see in the dmesg is it but I don't know for sure "init: Could not find service hosting interface android.hardware.radio@1.0::IRadio/slot1" which led me to this https://stackoverflow.com/questions...nterface-android-hardware-radio-config1-0irad
[Shield Tablet Original Android Development] npjohnson:
SIM is now fixed. And that error by proxy. Yes, just use lineage.dependencies to trace dependencies, all on lineageos org, and vendor is on themuppets as always.

17.1 doesn't boot at all, but that's a tegra t124 wide chipset issue - graphics crashes and panics the device. 16.0 is near to perfect.

Okay, this was an issue on my end - I fixed it, newest build via OTA fixes it.
[Shield Tablet Original Android Development] ShapeShifter499:
Perfect, I can now connect to LTE, though I only seem to ever get slow H or H+ connections over T-Mobile. Same as on Stock. Probably the old cellular chipset to blame.

I do see two other issues but I don't know how fixable they are.

1) Charging over USB micro-B barely works when booted in. It doesn't like to draw much current. As example, one of my power banks shuts off when this tablet is plugged in to it. Another being that it seems to discharge when plugged into a USB wall wart rated at 5V 2A. I know with some devices it was possible to change the kernel to force a higher charge rate or temporarily toggle it. Does anyone happen to know if that's possible here?

2) 1080p videos work amazing when they are under 60FPS, 60FPS videos will studer but not slow down the system. Videos 1080p 30FPS play perfectly. 60FPS videos also play perfectly if they are under 1080p of quality.

I don't expect it to play anything higher than 1080p in quality but I wonder why the 60FPS is the limit for 1080p when 30FPS seems smooth.
[Shield Tablet Original Android Development] npjohnson:
It's not older chipset -- it's missing bands :/ - unfixable

1. Charging can't be fixed. The regulators are MESSED UP, and it is charging the best it possibly can. The dock quick-charges it safely. - Working as intended

2. Totally expected, older hardware, and the app may be using software rendering instead of hardware - the top result for "1080p 60fps" on youtube plays fine.
[Shield Tablet Original Android Development] ShapeShifter499:
So with 1. it's probably dangerous to try to mess with the code to force any higher charging though the USB Micro-B over the Dock adapter.

With 2. I am using the Youtube app but 1080p60 plays like it is less than 30FPS. While the rest of the app/system behaves normally. Maybe I need to force it in developer options.
[Shield Tablet Original Android Development] Maxtorete:
Should I install Lineage OS from recovery after installing PSCI firmware?

There is a note in pre-installation instructions that confused me:
[Shield Tablet Original Android Development] Bazathoth:
100% bricked

followed all commands ran ./flash.sh fixed the typo --go

everything seemed to go smoothly until the end

file not found: persist.img

failed executing command 2147483647 NvError 0x4

command failure/warning: create failed

left hanging on forced recovery turned off device to restart and it is just a black screen with no indication of power, tried holding all 3 buttons vol+vol- power, nothing happens literally a paper weight

---------- Post added at 08:52 PM ---------- Previous post was at 08:43 PM ----------

Rebooted PC as Linux gave no indication a device was attached booted windows and windows tells me apx device attached , still blank screen.....usb gives device connected chime letting me know something is connected when unplugged/ plugged in
[Shield Tablet Original Android Development] npjohnson:
You didn't read the instructions -- they detail pulling the persist image and it's backup beforehand. It may now be fairly impossible to recover the contents of your persist image.

Nor are you bricked. You're in forced recovery still. I'll share my backup yellowstone's persist images to be nice, but I'm unsure the ramifications of this, if you drop them in that folder, rename them to persist.img and persistbk.img, and hold all the buttons until windows beeps as if the device power cycled, then run the script again, all will be good.

Edit: removed my persist imagew
[Shield Tablet Original Android Development] npjohnson:
Yes you should - that note is just saying that it will boot you into an older firmware, and that you need to flash the newest via recovery to get on the track that can OTA update.
[Shield Tablet Original Android Development] Bazathoth:
i did read the instructions, and i have both of those persist images in the folder, still got that error but it just hung on after. it didnt reboot into OS,and wasn't sure what happened like i said it just seemed "off" i downloaded yours and i'll replace and try that. so thanks, its not a huge deal i have 2 of them and that one was just sitting around unused for the last year or so.but i didnt want to try again with the other one, so i'll give it a try and let you know how goes
[Shield Tablet Original Android Development] npjohnson:
If you have yours, don't use mine. Ensure the files are correctly named and permissioned or try them on windows.

Don't use mine unless you don't have yours.