[ROM] [OFFICIAL] LineageOS for the Shield Android TV

Search This thread
I have read that the default rom on the shield has some restrictions on what can be installed from the play store does this Lineage remove that?

Does this work on the latest model I dont know what the codename is for it.
You can install LineageOS on the 2015, 2017 or the 2019 version.
I personally do not use the Playstore. But there are plenty of alternatives to install apps without restrictions on the Shield. E.g. Aurora Store, Aptoide or via adb.
You just have to keep in mind that many apps are not optimized for AndroidTV. In this case you need a mouse and keyboard to control them optimally. Or you can try the tab version of LineageOS.
 

Steel01

Recognized Developer
Dec 14, 2008
1,348
2,897
One last question I have a basic PlayStation controller could I use that, the instructions for installing Lineage mentions the official shield controller.
A playstation controller likely will not work for controlling the bootloader or recovery. I've not tested to know for certain it does not work, however. Nvidia's docs only mention the shield controllers and a keyboard as supported in the bootloader.
Playstation controllers should work on Lineage atv normally, however. A DS3 will work wired, (pairing a ds3 for wireless is painful, no matter where you use it). A DS4 works wirelessly, I've used that for steam in home streaming recently. I don't have keylayouts for DS5, nor do I have one to test with. So that would probably pair, but the button mapping would be wrong. For the tablet/mobile Lineage target, I don't think the ps keymappings are installed, so they probably won't work right. I should probably figure out how to add those.
 
  • Like
Reactions: Not_Rich

maathimself

Member
Oct 23, 2015
13
2
Samsung Galaxy Tab S6 Lite
I have tried to install this on 2017 shield. I am able to boot but after reboot the remote is disconnected. Also, when I connect the keyboard and mouse and try to go into settings to pair the remote again, every settings option takes me to the wireless networks page. I have tried reinstalling, wiping system partition and reinstalling, flash twrp and reinstalled. I was able to disable wireless, reboot then when I assigned a name for the device I was able to navigate to the other settings option but after reenabling wireless and rebooting I was no longer able to get settings back. Any ideas? Let me know if you need any details from me.
 

Steel01

Recognized Developer
Dec 14, 2008
1,348
2,897
Unfortunately, this is a known issue with pepper, the 2017 remote. I have not been able to figure out why it does this. Other remotes, such as the triangle 2019 remote do not have this problem.

This keyboard thing is not something I've heard before, though. Has anyone else seen something like that? Pretty sure others have used a keyboard recently and not had such trouble. Not certain what difference could cause this. I will note that atv is not designed to work with a mouse, keyboard only would work better.
 
The instructions for booting recovery mention this

With the device powered off, plug the included Shield controller into the USB-A port on the back of the device. Next, hold the A button and B button while plugging the device into power, continue until a menu is displayed. Tap the Y button until “Boot recovery kernel” is selected. Now, press the A button to select this option.

Has anyone found a way of using a regular wired keyboard instead of the official controller, sorry I am very new to this
 
Last edited:

dcarvil

Senior Member
Apr 20, 2016
674
374
The instructions for booting recovery mention this

With the device powered off, plug the included Shield controller into the USB-A port on the back of the device. Next, hold the A button and B button while plugging the device into power, continue until a menu is displayed. Tap the Y button until “Boot recovery kernel” is selected. Now, press the A button to select this option.

Has anyone found a way of using a regular wired keyboard instead of the official controller, sorry I am very new to this

Yes, I was able to do it using a regular keyboard. I used a wireless keyboard, but wired should also work. As I recall, you just use the A and B keys on the keyboard. It was a year ago, so I don't remember the details. The timing is tricky, and it took many attempts to get it to work. There are instructions somewhere on the nVidia site. Sorry, I don't remember where I found them.

I may be remembering it wrong, but I think it worked only when the shield had been powered off. Another way to get into recovery mode is "adb reboot recovery".
 
Last edited:

FigliDiGP

Member
Apr 10, 2020
22
5
Steel01: Another big thank for your work. All is working fine for me.

Another way to get into recovery mode is "adb reboot recovery".
Or more simple, you have the advanced reboot menu who offer the possibility.
This keyboard thing is not something I've heard before, though. Has anyone else seen something like that?
I use USB keyboard all the time. For 17.1, 18.1 and i don't have any problem. Except the layout we can't change (for azerty in my case).
 

fonicmaxxim

New member
Feb 2, 2023
3
1
Thank you for this, easy to install and seems to work great thus far (and way smoother than stock!).

I got two questions:
1) Did someone figure out how to change the layout for USB keyboards? There seems to be no menu option for that.
2) Is there a way to use the infrared sender of the NVIDIA Shield TV Pro 2019 remote? On stock, I was able to use IR to control my old Sony receiver.
 
Last edited:

sgcko7

Senior Member
Apr 28, 2010
383
87
Čadca
Hello all,

I have LineageOS on my Nvidia Shield TV 2017. So far almost all is working better then expecting. Just two minor issues.
1. When connected to any bluetooth audio devices like bluetooth headphones or speaker there is sound shuttering. This was not an issue with OG Android. Anyone else have this issue? Any way to solve this? PS: Controllers are working fine.
2. Due to Android 11 my emulator PPSSP - PSP cannot access storage. I have on another android TV running android 11 SlimboxOS but there ppsspp was able to access storage. Any ideas how to solve?

My shield TV main purpose is media consumption Kodi, Netflix, Youtube, *****ute etc. So solving that annoying sound issue would be great. Thanks in advance.
 
Hello all,

I have LineageOS on my Nvidia Shield TV 2017. So far almost all is working better then expecting. Just two minor issues.
1. When connected to any bluetooth audio devices like bluetooth headphones or speaker there is sound shuttering. This was not an issue with OG Android. Anyone else have this issue? Any way to solve this? PS: Controllers are working fine.
2. Due to Android 11 my emulator PPSSP - PSP cannot access storage. I have on another android TV running android 11 SlimboxOS but there ppsspp was able to access storage. Any ideas how to solve?

My shield TV main purpose is media consumption Kodi, Netflix, Youtube, *****ute etc. So solving that annoying sound issue would be great. Thanks in advance.
I also had problems with Bluetooth. However, only with one box. After a Bluetooth update to version 1.1 in LineageOS last year, they were gone. The sound no longer stuttered.
To access your memory you need the `addon-docsui-18.1-signed.zip`.
You have to search in the previous posts. @Steel01 has linked it. Then install this .zip with twrp.
 
Last edited:
  • Love
Reactions: sgcko7

sgcko7

Senior Member
Apr 28, 2010
383
87
Čadca
I also had problems with Bluetooth. However, only with one box. After a Bluetooth update to version 1.1 in LineageOS last year, they were gone. The sound no longer stuttered. Now with Kodi 20 the sound stutters unfortunately again with this box. No idea what is going on there.
To access your memory you need the `addon-docsui-18.1-signed.zip`.
You have to search in the previous posts. @Steel01 has linked it. Then install this .zip with twrp.
So this addon-docsui-18.1-signed.zip should fix the issue?
 

sgcko7

Senior Member
Apr 28, 2010
383
87
Čadca
I also had problems with Bluetooth. However, only with one box. After a Bluetooth update to version 1.1 in LineageOS last year, they were gone. The sound no longer stuttered. Now with Kodi 20 the sound stutters unfortunately again with this box. No idea what is going on there.
To access your memory you need the `addon-docsui-18.1-signed.zip`.
You have to search in the previous posts. @Steel01 has linked it. Then install this .zip with twrp.
Addon is working. Now I can access my storage. Great!!!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

    Instructions :
    • Download the latest build and gapps
    • Reboot to recovery
    • Flash the latest build and gapps
    • Reboot
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed or Magisk
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console_ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
     
    Did you--
    wipe:
     restore with titanium backup:
    reboot after having the issue:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    XDA:DevDB Information
    LineageOS for the Shield Android TV, ROM for the nVidia Shield Android TV

    Contributors
    Steel01
    Source Code: https://github.com/LineageOS/android_device_nvidia_foster

    ROM OS Version: 10.0 Q
    ROM Kernel: Linux 4.9.x

    Version Information
    Status:
    Stable
    Current Stable Version: 17.1

    Created 2017-07-06
    Last Updated 2021-10-15
    9
    So, working on pulling in the updates from the stock oreo release. Finally getting a few things to work that either haven't for a while or never did in the first place.

    1. Geforce Now is working again, like the login screen actually displays something again. (and on a side note, I'm liking some things I'm seeing) Right now, I'm having to hack a piece of it due to the shield hub app not fully supporting Android 8.1. I've contacted Nvidia and am hopeful they will release proper support in the Hub app so I won't have to actually push said hack official.
    2. Did someone say 4K? Second only to support for the original wireless controllers, this has bugged me for a while. Well, this wait is finally over. With the blobs from Oreo, 4k finally 'just works'. No weird broken stuff anymore. Now, switching between a 1080p and 4k display without wiping seems to do odd scaling atm, but at least it's not completely broken like previous releases were.
    3. So, this isn't complete yet, not by a long shot. And who know if once I do get it working whether it'll be suitable for official builds. But that thing I mentioned last point? Support for the wifi-direct controllers? Yeah, Nvidia actually released some of the major pieces that were missing for that. I'm fairly close to making it work, but haven't quite got all the pieces together yet. Once I get all the rest of the stuff stable and pushed up for official builds, I'm going to dive back into this and hopefully *finally* crack this nut.

    So yeah, I'm working on cleaning this all up and doing stability tests. I'm hoping to finish clean up this weekend and spend the next week sanity testing with intentions to release for builds a week from Monday. 'Course, life (tm) can always happen, but things are looking fairly up for this device. Look forward to further updates.
    9
    Work has started on foster/mdarcy 18.1. It's running fairly well. Waiting on the next Linux4Tegra major release to hopefully give usable git history for pieces of the kernel. That should be out later this month. Sepolicy also needs some *major* work, I'm starting that today. Once 18.1 is in good shape, the plan is still to shift to working on 19.0, polish it up, and ship that. It's not going to ship in the next couple weeks, but I sincerely hope that it won't take more than two months. But as always, #stuffcanhappen.

    TL;DR: work is still ongoing.
    7
    Been a while since I posted here, so small info dump update.

    Nvidia has officially released Pie as Shield Experience 8.0.0. The recovery images are available, but no source yet. I've done some analysis of the recovery images and things look fairly positive. The new graphics stack is in better shape than the one from 7.2.x, though I still haven't got it to boot to launcher yet. Once the source release is out, I'll be able to finish importing everything and hopefully a lot of the stuff I've worked on over the last year will 'just work'. But I have no indication of how long it's going to take to get said source release.
    6
    So, Stock Oreo is getting a staggered rollout. Once I get my hands on a copy (haven't been able to get an ota link yet and recovery images and aosp code isn't out yet), I'll start work on it. Initial report is that twrp doesn't boot on the new bootloader, so this is gonna be a fun transition. Queue the troubles with shieldtablet M all over again. ><