yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] Knuxyl:
Just flashed this with latest build and tvmini opengapps and everythings working, except bluetooth gamepad pairing.

The 8bitdo sn30 pro gamepad worked 100% with stock firmware with the controller in switch mode, but lineageos cannot even properly pair with bluetooth. during pairing, controller will just shut off.

Here is what it's doing

Android Mode on controller - Pairs, but pairing window does not go away and there is no input on shield

Switch Mode on controller - Does not pair 75% of time and shuts controller off during pairing screen, no input on shield

X-Input (Windows) Mode on controller - Pairs and works, but star button does not work and double press home button doesn't open recents. The star button worked as settings button

I ran a 3DMark (slingshot extreme), difference is negligible

Stock (With a ton of apps installed) = 3912

LineageOS Post Install = 4013

Interface is the newest google launcher type. I don't care either way about this. Nvidia went lazy route instead of updating entire ecosystem updated the launcher to fool public into thinking they're still maintaning this product. Since there's no competition, there's no motivation for them to really do anything.

If yall could get the same controller compatibility as the stock firmware that would be amazing. Thanks so much for all the work done on this, I've been waiting for years.
[Shield Android TV Android Development] brick00444:
I want to try this but I installed Lineage on an Onn box and one of my go to apps (Channels dvr) didn't work on it. Has anyone tried the Channels app on this build?
[Shield Android TV Android Development] Knuxyl:
After a couple of days of using this on my 2019 pro here is what doesn't work

Menu button (hamburger icon) on any controller/gamepad

Recents (double click home button) on any controller/gamepad

AI Upscaling (this should not be expected anyways, it's proprietary nvidia code)

If I remember correctly, reading through the requirements to get a build marked as official something simple as the 3 primary buttons used to navigate working correctly is a primary consideration. I'm confused as to how this build was allowed in, this is clearly not usable in it's current form. No multitasking and no way to enter settings without exiting your current app makes this completely unusable. I thought at first it was because I was using my gamepad but even using the stock controller has the same problems. Other than the very debilitating input issues everything else seems to work flawlessly.

I would not recommend this to anyone until these input issues are addressed.
[Shield Android TV Android Development] npjohnson:
Alright, allow me to respond:

Menu button - it's in progress, even just merged a KeyInterceptor for ATV devices recently.

Recents - Google has disabled and enabled this on ATV repeatedly over it's lifetime - in the case of Android 10, we haven't gone to the effort to re-enable it when, even the generic AOSP TV targets don't!

AI upscaling - proprietary as hell - if someone gets it working, I applaud them, truly.

Charter: - this meets charter in it's entirety. Not being able to overlay settings over the current app is not at all a "required feature" - you can still use all of settings, and multitasking on a TV device? idk, my Nexus Player builds haven't had that for... years, and no one has ever brought it up.

This meets charter, and it perfectly stable usable.

Now, do we plan to make the settings button work? Yes.

Will we probably enable recents once the UI works again? Probably.
[Shield Android TV Android Development] Knuxyl:
thanks for the reply and thanks for the work yall have done.

the page i read said the build has to work like or better than stock, regardless of what other devices are doing, but i understand the issue with recents on android 10. i didn't know that. im just frustrated because i expected this to work better than stock because it's official but it is lacking in what i consider basic navigation that stock has, regardless of why. it's a hassle getting this thing out and flashing it and now i have to go back to stock.

nvidia has lazy developers, it's amazing someone not getting paid has had more development into their product more than they have. im excited to see these features implemented, or maybe updated to android 11 where recents has been reimplemented (if it has)?
[Shield Android TV Android Development] npjohnson:
Charter doesn't really say any of that - it has specific requirements of support. Which we meet.

Android 11 has the same recents issue atm sadly. But we're working on it.
[Shield Android TV Android Development] nprev420:
Just flashed 12-01-21 build for mdarcy, (no GAPPS) first custom ROM on my shield. Am I blind, or are there no lineage custom ROM settings? Display settings? The display goes outside borders of the TV and I need to adjust it like "overscan" on the Nvidia rom. Also no IR setup either?
[Shield Android TV Android Development] TektTheGeek:
Got lineage running on my 2017 foster. The only issue I am having is that Bluetooth stops working after a restart. Just curious if this issue has been fixed. Keep up the good work!
[Shield Android TV Android Development] Steel01:
That's news to me. The remotes can sometimes take a while to reconnect, but I've had the exact same reconnect lag on stock, so I don't consider that a regression. Might even be the remote itself. Is that the issue or something else?
[Shield Android TV Android Development] TektTheGeek:
No. The issue is that Bluetooth doesn't ever pair again after a restart. I've tried reinstalling several times, but still having the same issue
[Shield Android TV Android Development] Steel01:
When you say 'pair', you mean the remote paired during first boot doesn't reconnect after a reboot? Or new accessories can't be paired? Or both.

I've not seen this issue fwiw, nor have I heard such reports from testers, so I need as much information as possible.
[Shield Android TV Android Development] TektTheGeek:
Both to be exact
[Shield Android TV Android Development] Steel01:
Can you get logs when this issue is happening? Go to pairing with a wired controller, try to pair something, back out of pairing, then get logcat and dmesg.
[Shield Android TV Android Development] TektTheGeek:
Will do. Will get back to you
[Shield Android TV Android Development] Steel01:
@TektTheGeek Did you install the atv or tablet/mobile build?
[Shield Android TV Android Development] TektTheGeek:
The latest ATV from the lineageos site
[Shield Android TV Android Development] Steel01:
This is really weird. It's trying to open contacts, which of course doesn't exist on atv. But that's crashing bluetooth.

12-05 19:01:35.342 23395 23395 E AndroidRuntime: java.lang.RuntimeException: Unable to start service com.android.bluetooth.pbap.BluetoothPbapService@5a603e2 with Intent { cmp=com.android.bluetooth/.pbap.BluetoothPbapService (has extras) }: java.lang.SecurityException: Failed to find provider com.android.contacts for user 0; expected to find a valid ContentProvider for this authority

12-05 19:01:35.342 23395 23395 E AndroidRuntime: Caused by: java.lang.SecurityException: Failed to find provider com.android.contacts for user 0; expected to find a valid ContentProvider for this authority

What are you pairing on first boot? Anything more than the remote that was bundled with the device?
[Shield Android TV Android Development] TektTheGeek:
I did see that in the log. I am using Logitech k600 keyboard in Bluetooth mode
[Shield Android TV Android Development] crnkoj:
Check 2 posts up
[Shield Android TV Android Development] m00m00:
That's for the heads up regarding the commands in the post you pointed out. I have been trying to complete the commands successfully but unfortunately I have not had any success. Have you tried this yourself and if so did it work for you? Everytime I try the commands I always receive a "FAIL-NO-IFNAME-MATCH" error either the interface does not exist or the interface is busy. Even if I enter "wpa_cli" and then run "p2p_find" the command instantly returns a FAIL. I checked online and discovered that "iw list" shows the supported modes which this driver offers (P2P-client, P2P-GO, P2P-device) the only thing that was suggested was the following

Start "wpa_supplicant" then "wpa_cli" then run "p2p_find" to confirm the discover of p2p devices however that command returns FAIL immediately. After searching and discovering other things I am still unable to connect my controller via the terminal.

Is this build specific? Any help would be appreciated.
[Shield Android TV Android Development] Steel01:
The p2p interface probably isn't getting created. I need to swap out a config file for wpa_supplicant, but I've been loathe to do so cause I'd have to track it manually then, instead of just pulling it from upstream. I've been kinda busy lately, but I'll look into getting that change merged in soonish. If you want to change it manually, look at /system/etc/wifi/wpa_supplicant_overlay.conf and /data/misc/wifi/wpa_supplicant.conf. In *both*, change p2p_disabled from 1 to 0 and reboot. The instructions in that post *should* work then. Do note said change will be lost next time you run a Lineage update.
[Shield Android TV Android Development] m00m00:
Thanks for the information I got it to work. It is a bit of a pain but at least the option to do so is available. Thanks.
[Shield Android TV Android Development] savagepagan:
Does this OS give us full access to the Google Play Store apps or is it restricted like the stock OS?
[Shield Android TV Android Development] Matt17000:
It's an android tv release, so only android tv apps
[Shield Android TV Android Development] eried1:
What are the benefits of replacing stock with LOS?
[Shield Android TV Android Development] Matt17000:
I don't see any benefits... You lose all nvidia stuff, gamestream, nvidia games, the ootb compatibility with the controller....

If someone can tell me something about LOS i'll take it !
[Shield Android TV Android Development] lupick:
Wrong post

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Shield Android TV Android Development] efegue:
I've tried this ROM, but couldn't get past the wireless step, it wouldn't connect to any wireless network I had and It didn't have an option to skip it...

Any news when you might have Oreo builds of Android TV? Thanks!
[Shield Android TV Android Development] barkop:
Hi,

is there any way to use the full play store on shield tv?

is it possible to use lineageos for shield tablet on my shield tv to get full play store?

regards
[Shield Android TV Android Development] ancapgamer:
Just wanna say thanks for working on this - I don't trust official manufacturer firmwares as much as I do fully open-source ones, so it's nice to have other options, even if they don't always come with all the original features. Once Gen-1 controller compatibility becomes a thing, I'll definitely switch to this (or once I cobble together enough spare funds to purchase a new Bluetooth controller) - in the meantime, has anyone tested Netflix on this build? Since the ATV is the main entertainment hub for my whole family, my wife and kids would kill me if I replaced the OS and lost us our Netflix access.
[Shield Android TV Android Development] vaderyeh:
There is a cheap evo vr bluetooth controller out there that I purchased from wally world, $19.99 plus tax. Its a pain to pair but after you pair it it works great!
[Shield Android TV Android Development] ThrillerAtPlay:
I just purchased a brand new nVidia Shield TV 2017 (darcy) but could not install LineageOS either. I attempted to sideload the latest weekly of foster (I didn't realize I had a darcy until I later was at the adb shell) but there was an error that flashed on the screen too quickly to write down. I am pretty sure it was the standard error status 7. It took me a while to figure out how to use TWRP without a touch screen and because I have not seen the instructions posted already, here are the steps I took in using a Linux machine connected to the USB port furthest away with an male-male USB a-a cable:

Required

USB A->A (Male-to-Male) cable.

computer with fastboot and adb installed

Prep

Download TWRP

Download LineageOS

Connected one end of USB cable the second USB port on the nVidia Shield TV and the other to the computer.

Boot nVidia Sheild TV into fastboot

## I am on Linux so you may need to remove "sudo"
$> sudo fastboot oem unlock
$> sudo fastboot flash recovery twrp-3.1.1-1-foster.img

## Now you should be at the TWRP welcome screen
$> adb shell twrp remountrw
$> adb shell twrp sideload

$> sudo adb sideload lineage-14.1-xxxxxx-nightly-foster-signed.zip

EDIT: I posted the error and work around in post #63
[Shield Android TV Android Development] vaderyeh:
Last update fixed play movies. Can someone confirm Netflix viewing, I do not have an active Netflix account.
[Shield Android TV Android Development] Zorro12345654321:
Hello there,

I'm on the latest nightly 2017-11-07. Everything is working like a charm but DAZN (SportStreaming). I can't see any picture I can only hear the sound. Can you please have a look into this?

Thanks in advance and please let me know if you need any logs or some more informations.
[Shield Android TV Android Development] janneriiki:
I had the exact same issue a week ago. Have you got confirmation whether Foster build will work on Darcy by sideloading LOS? I flashed through twrp normally and was stuck at bootscreen. Would love to try Lineage on my Shield tv
[Shield Android TV Android Development] ThrillerAtPlay:
It would not complete the sideload. It errored out almost immediately.
[Shield Android TV Android Development] Steel01:
? Sideload outright failed? That shouldn't happen... I can't even do proper bootloader checks, so the only thing that should outright fail is if the wrong zip gets flashed. That or the wrong twrp version. Can you paste the error?

On Darcy, yeah. This is the weirdest bug I've seen to date. My unofficial builds work perfect, but any official builds fail. I've yet to figure out why, but I'm taking another shot at it tonight. If I can't figure anything out, I'll upload an unofficial build to at least have something out that boots.

On Netflix, last I checked, it 'works'. I was getting a gray bar down the right side, though. And haven't had time to go try and track down what exactly is happening there. Do note that Netflix still has to be sideloaded since the company started requiring safetynet checks for their app to show in the play store.

Edit:

Oooooopppppsssss... Okay, so I accidentally prevented the new foster builds from installing on darcy. Which is kinda a good thing atm since they don't boot. >< Once I get it booting again, I'll fix that.
[Shield Android TV Android Development] vaderyeh:
11-15-17 build seems to break play movies again:(
[Shield Android TV Android Development] Steel01:
Hmm. Now that's something I can't test. Don't have a bt keyboard of any sort. Can you try pairing only the nvidia remote, reboot, and see if stuff still works? If so, pair the keyboard and reboot, see if it breaks at that point. To narrow down what's specifically breaking.
[Shield Android TV Android Development] TektTheGeek:
Will definitely try this tomorrow and report back to you the results
[Shield Android TV Android Development] TektTheGeek:
Hey. So I realized that the issue was that after I rooted with Magisk, I went in with a package manager and removed com.android.contacts assuming it wasn't needed! My apologies. Everything is working fine after a reinstall.
[Shield Android TV Android Development] Steel01:
I just updated the opening post to explicitly call out magisk. Bug reports are NOT VALID if magisk has been installed.
[Shield Android TV Android Development] Kladderadatsch:
First of all a huge thanks for these builds!

I flashed latest official ones for mdarcy (file and recovery). Despite some minor bugs for my case on the whole good to use in everyday life . I know that I am not allowed to report errors because I rooted with Magisk.

So, but now briefly to my problem. I own two mdarcy which were both flashed. Since then, both have the same macaddress, which of course leads to problems in my home network. Is there a way to change the macaddress permanently? I tried it with busybox, but it didn't work.

I also tried to flash official twrp instead of the lineage recovery. This works but unfortunately twrp does not recognize any memory on my mdarcy. It always shows only 0mb. Does anyone know the problem?

Kind regards
[Shield Android TV Android Development] Steel01:
I can't know for certain that this issue isn't caused by magisk or a module. So unless the issue can be reproduced on a clean install, it can't be considered an official report.

That said, I can give a couple pointers on how the mac addresses work on tegra devices. There's a partition named FCT that gets mounted at /mnt/vendor/factory. In there are two text files with the mac addresses for wifi and bluetooth respectively. Those are set by the factory and should not be modified. But you can check to see what those values are.

Also, I just checked on one of my units and the wifi mac address does look wrong. Vendor should 00:04:4b, but it isn't. So there might well be an issue with how the wifi mac gets read. Most likely sepolicy related. Yay...

Edit: I just looked into this more. If I look in settings->device->about->status, the mac address is reported as 00:90:4c:11:22:33, which I believe is a broadcom default mac. But if I run ifconfig via adb, it reports 00:04:4b:xx:yy:zz, which is correct. And if I look at my router, it shows the 00:04:4b mac as what's connected. So... at least on my device, there's only a cosmetic issue. Which shouldn't be a thing, but it's less bad that actually using a bogus default mac.
[Shield Android TV Android Development] Kladderadatsch:
Hello @Steel01, thank you for your quick reply. Sorry I was a little unclear. It is about the wlan0 mac address. Under status, with ifconfig or in the router, it always shows me the same mac address(00:90:4c:00:00:00). But under /mnt/vendor/factory the mac address is 48:B0:2D:xx:yy:zz.
[Shield Android TV Android Development] Steel01:
As a side note, I find it interesting that nvidia switched mac vendor mid cycle. My mdarcy has 00:04:4b:xx:yy:zz on factory. But 48:b0:2d is also registered to nvidia, so *shrugs*.

On a better note, I did reproduce the issue when I pulled out my mdarcy. So apparently bcm sdio wifi is fine, but bcm pcie is broken. Meaning only mdarcy and sif (and maybe porg as I have it set up) would see this problem.

Yeah... thanks nvidia customized copy of cypress-fmac. Unfortunately, I don't quite see how this is getting lost. It's acting like the os has overridden the mac addr, but I don't know why. Will give it another look soon.
[Shield Android TV Android Development] cHECKjAM:
Anyone else with a logitech harmony hub remotes find that the "power off" actually never powers off the shield?

Also is there a way to "adopt storage" by connecting a harddrive to the 2017 pro shield , to have the internal storage increased? same way as you can with original shield.. ?
[Shield Android TV Android Development] sugarybread:
First of all, I want to thank you Steel01 for all the hard work you're putting into this project. This is currently the only option for a Google-less Android TV box experience so thank you for that.

I'm seeing constant crash and reboots on a freshly installed lineage mdarcy.

LineageOS version: lineage-17.1-20211208-nightly
LineageOS Download url: lineage-17.1-20211208-nightly-mdarcy-signed.zip
Gapps version: None installed

Wiped: Yes
Restore with titanium backup: No
Reboot after having the issue: Yes

I freshly installed the lasted nightly build using the instructions here. I have no apps installed, no magisk, and no xposed. This is a completely fresh install.

During the set up process, I will see intermittent reboots. If I go quickly enough, I am able to get through the set up process without a reboot. Once set up, if I stay on the home screen, there isn't any issue. But once I start navigating the settings menu or using an app, it will eventually reboot. Right before it crashes, I'll see a notification that the wifi is no longer connected so I suspected it's a wifi issue. I was able to get the ramoops logs after two separate reboots.

ramoops1 - https://pastebin.com/hA7KR9C4

ramoops2 - https://pastebin.com/SgqMeLdP

Update: the reboots stopped happening after I enabled the wifi scanning location setting. (I had disabled it as part of the setup)

Update2: the reboots have started again. Wifi scanning is still enabled.
[Shield Android TV Android Development] Steel01:
There's supposed to be, but I've seen reports that it doesn't work. I never use adopted storage myself, and haven't gotten around to testing on one of my test units.

@sugarybread That makes... no sense. Disabling wifi location causes the driver to crash? I'll make a note of that, but don't even know where to start with that one.
[Shield Android TV Android Development] sugarybread:
So not sure if the crashes/reboots are due to the wifi scanning or not. It crashes now whether is on or off. Consistently though, right before it crashes, I see a notification stating that Wi-Fi is not connected. Then it freezes up before rebooting.

Not sure if the ramoops have any relevant info but I can provide more after a reboot if they help.

Update: Looks like a temporary "fix" is to disable and re-enable the Wifi after a reboot. If I don't do that after a reboot, lineage will crash and reboot on its own after a few seconds. If I do, no more reboots.
[Shield Android TV Android Development] Kladderadatsch:
I also installed the version `lineage-17.1-20211208-nightly-mdarcy-signed.zip` but unlike @sugarybread no crashes or reboots. Nevertheless I also had problems with the wifi connection. After a reboot it was unfortunately no longer automatically established.

Since I block everything Google-like in the network with Pihole, I always get the message `No Internet` under Android because the Captive Portal Check is blocked. To stop the check I always execute the command: `settings put global captive_portal_mode 0`. Since then, the automatic reconnection of the wifi connection works after a reboot.
[Shield Android TV Android Development] Steel01:
@Kladderadatsch I found the issue with mac addresses on mdarcy. The fix will be in the next official build later this week. The captive portal stuff is a bit outside of normal usage. If it's not something most people will encounter and there's a known workaround for those that explicitly choose to do so, then I'm going to say it's working as intended.

I'm not certain if the mac address change fixes @sugarybread or not. I'm going to guess not, but it'll be worth another test when the next build happens. It sounds like it's related to some of the nvidia modifications to the brcmfmac driver, though. If it persists, I at least have an idea of the scope of the problem, if not exactly what it is.
[Shield Android TV Android Development] sugarybread:
I'll try the next build and let you know if the issue persists. In the meantime, since the shield doesn't need to reboot in normal operation, the disabling and enabling WiFi tricks works for now.

Let me know if I can help by providing any kind of logs.