yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] Steel01:
Oh, something else that should be mentioned for those interested. I recently did a revamp on how remotes and certain buttons are handled. And that was all merged today. So in the next build, the settings, search/voice assist, and netflix buttons will all work as expected.

On a related note. Opengapps had broken voice assistant for... probably ever. I hadn't noticed until I started looking at the remote buttons more closely, cause I never use voice search and don't like the idea of anything always listening. But once I realized it was broken, I looked into fixing it. And opengapps tv packages from the last couple weeks now have working voice search. If you installed before then, you'll need to flash an updated opengapps package, then it should work.

Edit: It should be noted that the older two nvidia remotes (jarvis and pepper, launched in 2015 and 2017 respectively) do not have working mic support. Friday, the 2019 triangle remote does have a working mic. The older two need a *lot* of additional magic to work, and that might never happen for Lineage or other custom roms.
[Shield Android TV Android Development] vishnu350:
Is the green light on mdarcy supposed to stay on even after it is put to sleep?
[Shield Android TV Android Development] Kladderadatsch:
yes
[Shield Android TV Android Development] Steel01:
As of right now, yes. It's something I've poked around at some, but haven't come up with a clean way to handle it yet. The darcy/mdarcy lightbar is easily accessible, but only brightness can be controlled, can't just set a mode for pulse. For some reason, my foster_e_hdd doesn't enumerate the lightbar at all, so I haven't been able to experiment with that one. And yes, foster* and *darcy have completely different hardware for the lightbar.
[Shield Android TV Android Development] Kladderadatsch:
Just wanted to give quick feedback that the Mac address issue is resolved with the build of 12/15/2021. The Mac is now correctly assigned and displayed in my router. But on the Shield under Info the 00.90.4c.00.00.00 is still displayed.
[Shield Android TV Android Development] Steel01:
Yeah, that's still expected unfortunately. No idea why tvsettings can't get the correct address. It might not get fixed on 17.1, might just defer that to 18.1/19.0 development. See if it's still a problem there.
[Shield Android TV Android Development] jesi:
Hi there.

I have 2015 pro running normal android, i can use same apps what I have in phone.

It have served me well, but it is version 7.0.

I belive it is this, can't be sure due flashed it so looooong time ago:

[ROM][Full Android Nougat for Shield TV][v.1.5] - DroidMote Support Forum

Can I get same experience (use normal phone apps) with this?:

Redirecting…

If yes, would be awesome!

Should I flash it back to androidtv from Nvidia stock recovery images, or follow LOS guides directly where I'm now with that zulu99 firmware?

(I have 2019 pro running ATV, but still have use with device what has normal android)
[Shield Android TV Android Development] Steel01:
@jesi Hmm. I'm not certain about a jump directly from N to Q. I know that twrp and the lineage recovery won't boot on the old bootloader (anything older than O/stock 7.2). So you'd probably have to flash a stock recovery image, current 8.2.3 would be fine, then flash a foster_tab build as per the Lineage wiki.

foster_tab is specifically a tablet build, not 'phone' per se. But phone apps run on tablet and vice versa, so that's more of a nit-pick than anything else. I just note that the tablet builds are less tested (it boots and basic hardware works), and very much not user friendly (you have to use a mouse or similar to interact with it), but they're there for those that still want to use them.
[Shield Android TV Android Development] jesi:
Thanks for your quick answer.

Yes, I mean 'phone", that it runs normal Android, not ATV =)

I have very little use time with ATV, but I have feeling that browser is not so handy with that, even with Airmouse.

Tested only Chrome from spoofed Aurora store, tho.
[Shield Android TV Android Development] sugarybread:
@Steel01 Couple updates on the rebooting issue:

1. I dirty flashed the latest 12/15 build and still see the reboot issue.

2. I thought it might be hardware related (since no one seems to have this issue) so I got a second mdarcy and installed a clean flash of the 12/15 build. I still saw the issue.

In both cases, I did not install opengapps and the only change I made was to go through the set up process and connect to my wifi.
[Shield Android TV Android Development] jenneh:
Gruh... I didn't even know this thread existed x.x the algorythym behind google search, really is a disservice, but more so Bing, or *shudders* YAHOOOOOO~! Anywho, hi to the OP, I am totally off-topic I apologize.. haha. I will DM if I can ever figure out what it is I am trying to do~!
[Shield Android TV Android Development] rickyray9:
Beautiful and clean, thanks so much. I did notice that I was unable to navigate the power menu on pro 2019. Is that a known issue?
[Shield Android TV Android Development] Steel01:
Yeah, the power menu on <=Q is just the tablet/mobile power menu, which only works with touch. On R+, google pushed an atv power menu that works with a controller. So once nvidia finally decides to release their Android 11 update and I finish pulling in all the updates, I'll be release either R or S, which will have an operable pop-up power menu.

In the meantime, look in settings->device->about for reboot and shutdown. Don't ask me why google put reboot there, but they did. On R+, it's moved up a layer to the device settings list.
[Shield Android TV Android Development] R!ffRaff:
lineageos say RIP to Lineage 17.1 and closed the weekly image. will there still be official or inofficial support for Lineage 17,18 or 19?

if someone needs the last image and recovery, he should save them now!
[Shield Android TV Android Development] madnerson:
Really sorry for the dumb question but I just spent hours and can't find it.

I installed the latest build lineage-17.1-20220105-nightly-mdarcy-signed.zip without any gapps.

I can't find a way to sideload the fdroid apk, I don't see a file manager or a browser.

Any help is greatly appreciated.

Update: Managed to use adb through network, the USB didn't work :(
[Shield Android TV Android Development] FigliDiGP:
Thanks. Are you sure about this ? A new one was build today.

[GUIDE] ADB Workshop and Guide for everyone

USB doesn't work for ADB ?

You can try to activate Developers Options and search for terminal.
[Shield Android TV Android Development] R!ffRaff:
Yes, unfortunately, my devices with lineage 17.1 (davinci, lux and mdarcy (shield2019pro)) have not received any updates since sunday! Once this change has been committed, then the 17.1 builds will be stopped and all support removed.

https://review.lineageos.org/c/LineageOS/hudson/+/321289

https://review.lineageos.org/c/LineageOS/hudson/+/321289/1/lineage-build-targets

since I don't know of any test image 18.x for the shield, I think that's the end, maybe. android 11 was only released in the last few days, maybe something else is needed!

lineage will move from 17.1/18.1 to 18.1/19.1
[Shield Android TV Android Development] Steel01:
Oi, stop reading too much into things. The kill 17.1 commit is queued yes, but it's not going in until 19.0 ships. Which is still a few weeks out.

There's currently no plans to ship 18.1 for foster. The plan is to do basic bringup on the new Android 11 stuff from Nvidia for 18.1, then push directly to 19.x and ship that. So there probably will be a break in builds until I finish getting the new stuff in order (nvidia hasn't even released source for stock 9.0 yet), but I hope it won't be too long.
[Shield Android TV Android Development] FigliDiGP:
Nice to read that, Steel01 !
[Shield Android TV Android Development] madnerson:
I tried making it work with 2 different machines and the device was not recognized through USB when booted. It would recognize it when in recovery.

But even then, I could not get it installed using Lineage recovery. I would get an `emmc` error when trying to wipe and every time I tried to click ADB sideload the device would just freeze and nothing would happen until powered off. I had to use TWRP recovery to be able to install LineageOS.
[Shield Android TV Android Development] FigliDiGP:
Yesterday I'm spend few hours to install LOS. A little lose of time to find the way to start in bootloader with my Foster 2015, the wiki don't cover all devices. And my USB hub with keyboard was blocking.

But the system works well, everything is quicker. And no more GApps :cool:

ADB sideloading work for me, just need a reboot after activation in Developers Options to allow my computer. Don't remember if it's working in LOS recovery.

My only problem is my physical keyboard, he's in qwerty layout and i don't find how changing layout in azerty. Escape don't work, instead I've been using Ctrl+Alt+Backspace, not very usable :cautious:

But a huge thank to the team and specially at Steel01 who's taking time to talk here (y)
[Shield Android TV Android Development] Kladderadatsch:
Would be really great if the keyboard layout could be changed.
[Shield Android TV Android Development] smoke87:
Hey, Thank you for your great work.

Could someone knows or test if SVPlayer app works on lineageos on shield?

SVPlayer (Smooth Video Project Player) is a player that add frames to videos, convert 30fps videos to +60fps, it will be great if it works on shield, because we can watch 60fps until if the video have a low fps, this software is high cpu/gpu consumer.

I've tried sideload but doesn't works on default shield tv android 11, svp team says this don't works because Shield TV android doesn't support and/or provide access to OpenCL API.

My hope is lineage supports OpenCL. So if someone who have the lineage os could test it, or knows if this is supported, I would appreciate.

Thanks in advance.

SVPlayer - watch in 60+ fps - Apps on Google Play

A video player with real-time motion interpolation (SVP, MEMC, smooth motion)

play.google.com
[Shield Android TV Android Development] FigliDiGP:
I tried but SVPlayer need Google Play Services. Sorry
[Shield Android TV Android Development] smoke87:
They have an ungoogled version.

Get – SVP – SmoothVideo Project

www.svp-team.com

Thank you.
[Shield Android TV Android Development] FigliDiGP:
Yes it's working with this version ...

"Unfortunately this device doesn't provide OpenCL support and we really need it for the frame interpolation magic."
[Shield Android TV Android Development] mrhamed:
I have 2019 pro & installed the latest build lineage-17.1-20220119-nightly-mdarcy-signed.zip without any gapps.

The Ethernet cable is connected but device does not detect it !

Any idea ?
[Shield Android TV Android Development] smoke87:
:( , but thanks for test it.
[Shield Android TV Android Development] mrhamed:
I faced with several issues on MDARCY lineage-17.1-20220119:

1) I'm using wired network connection, on every reboot the Ethernet connection lost and I have to unplug an re-plug the cable physically to fix :( any solution?!

2) WiFi network does not allow set the static IP, (my router does not configured as DHCP server.)

3) After press power button on remote control the device's green light stay on continuously. (on official nvidia rom it goes off as soon as press power button on remote control)

I have to use my external HDD with ext4 fs, so I have to use LOS because official nvidia kernel does not support ext4, please fix issue number (1) as soon as possible, Thank you developers...
[Shield Android TV Android Development] mrhamed:
temporary workround for Ethernet issue (and WiFi static address) with Magisk boot-script:

1) make a boot-script file: su touch /data/adb/post-fs-data.d/set_ip

2) su chmod +x /data/adb/post-fs-data.d/set_ip

2) put below script in file:

#!/system/bin/sh
while [ "$(getprop sys.boot_completed)" != 1 ];
do sleep 1;
done

ifconfig eth0 down
sleep 4
ifconfig eth0 192.168.0.2 netmask 255.255.255.0
route add default gw 192.168.0.1 dev eth0
ifconfig eth0 up

ifconfig wlan0 down
sleep 4
ifconfig wlan0 192.168.0.3 netmask 255.255.255.0
route add default gw 192.168.0.1 dev wlan0
ifconfig wlan0 up

Magisk boot-script ref:

Magisk/docs/guides.md at master · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Shield Android TV Android Development] Don_Pachuco:
Do you need to be rooted to use this? I have a P2571, which I think is a 2017 Pro. Is there se way to do that, now that Nvidia did the Android 11 upgrade/update? Since I am going to be swapping to an SSD, I'll technically have a failsafe with the OEM HDD.

Could use links, steps, or instructions to make it rain... 😉
[Shield Android TV Android Development] mrhamed:
lineage-17.1-20220126 issues:

1) on every reboot the Ethernet connection lost and I have to unplug an re-plug the cable physically to get connectivity.

2) WiFi network does not allow set the static IP, (my router does not configured as DHCP server.)

3) After press power button on remote control the device's green light stay on continuously. (on official nvidia rom it goes off as soon as press power button on remote control)
[Shield Android TV Android Development] Kladderadatsch:
@mrhamed Unfortunately I can't say much about your first two points, because I connect my Shield via dhcp and that works wonderfully.

Steel01 has already commented on the green light issue (post #600).
[Shield Android TV Android Development] mrhamed:
Thank you for reply, does the green light issue mean the device does not power off completely?

Other issue is: the rom does not contains default file manager(com.android.documentsui) as storage-access-permission-provider to other apps!

Can you help me to configure samba please: https://xdaforums.com/t/invite-who-...gure-use-samba-server-with-lineageos.4392839/
[Shield Android TV Android Development] Magissia:
Is there a changelog to follow known issues ? At some point it was mentioned a problem with colors exist but it is time consuming to read each posts to find if someone declare it is resolved.

If not a changelog, maybe a know issue list on first post ?
[Shield Android TV Android Development] Magissia:
Can't it be managed from the keyboard settings or linked to current system language ?
[Shield Android TV Android Development] Kladderadatsch:
That would be nice! Maybe I'm just blind or too stupid but I can not find anywhere an option to change this
[Shield Android TV Android Development] Kladderadatsch:
I noticed today with my mdarcys that they restart after a few minutes when CEC is completely disabled.

Oh and since the upgrade from 02.02.2022 my shields no longer remember the volume. After a restart, the volume is always at maximum.
[Shield Android TV Android Development] mrhamed:
I have Wi-Fi connection issue(device does not connect) with lineage-17.1-20220209, Wi-Fi access-point is not hidden... can you help?
[Shield Android TV Android Development] Kladderadatsch:
Unfortunately, I do not have a crystal ball. The best would be a logcat. But I remember that I also had problems to connect to wifi. The shield did not want to connect permanently to 5Ghz (channel 36 to 48). With channel 100 it worked. I never tried 2.4 Ghz wifi.
[Shield Android TV Android Development] mrhamed:
I can't bypass lineageos setup, how I can achieve the logcat ?!
[Shield Android TV Android Development] Skel40:
I'll try to capture the logcat for the Feb 9th 2022 build directly from LineageOS' builds page. To answer your question @mrhamed, you need to have an ethernet cable connected to your router or your computer to achieve the setup screen. Keep note that the Wifi bug is still present as I'm also experiencing the same issue too.
[Shield Android TV Android Development] Skel40:
Here's the Wifi logcat I've captured. There's a lot of package names not found after logging the bug. Take a look:
[Shield Android TV Android Development] Skel40:
The weirdest part about this Wifi bug is the setup page. As it connects to the Wifi it forces a reboot but after connecting the ethernet and getting passed the setup, the bug is still occurring and takes a while randomly until it starts to trigger a reboot on the Shield TV 2019 with the Wifi connected.

The last bit of code before it reboots is really strange.

02-13 15:02:42.524 4464 9132 V NativeCrypto: SSL shutdown failed: ssl=0x3020350f48: I/O error during system call, Software caused connection abort
02-13 15:02:42.542 4464 9132 V NativeCrypto: SSL shutdown failed: ssl=0x3079c605c8: I/O error during system call, Software caused connection abort
02-13 15:02:42.796 5793 9152 V NativeCrypto: SSL shutdown failed: ssl=0x3080246cc8: I/O error during system call, Software caused connection abort
02-13 15:02:42.850 4464 9132 V NativeCrypto: SSL shutdown failed: ssl=0x3020350c48: I/O error during system call, Software caused connection abort
02-13 15:02:42.979 11095 11095 I Finsky:background: [2] jfi.onDestroy(8): IPC-SERVER: Stopping gRPC host service...
read: unexpected EOF!
[Shield Android TV Android Development] Skel40:
Also here's the bluetooth volume bug found here with tv volume turned up with the tv and the headphones at the same time.
[Shield Android TV Android Development] Skel40:
Bluetooth Log:
[Shield Android TV Android Development] Kladderadatsch:
Hmm, I had no problems with the wifi, no reboots, nothing in the log. I connect with 5Ghz on channel 100, the other day I wanted to change the channel, but the shield lost the wifi connection all the time, so I went back to channel 100.

Reboots I have only sometimes when the hdcp handshake did not work. The solution was to turn the TV off and on again.
[Shield Android TV Android Development] Skel40:
That's so weird isn't it? According to my configuration I have 5 ghz on channel 48 and it's causing this bug. So channel 100 doesn't cause that issue on your end? I'm really hoping Lineage can look into this and fix this as I've stated in my forums last year.
[Shield Android TV Android Development] mrhamed:
Thank you for reply, off course I have an Ethernet cable connected to my router! The setup screen does not matter about that! It does not connect to my router (it seems because the router does not provide DHCP) so I stuck on setup screen :'( (event I try setup manual IP)

as my experience:

1- I restored my twrp backup 2022-02-02

2- boot up and all things works as expected

3- dirty update 2022-02-09

4- boot up and Ethernet network not connect, the OS detect the cable is disconnected, I try to unplug and re-plug Ethernet cable, but it does not work, also I tried change IP and... finally it does NOT work.

5- restore ONLY system partition with twrp backup 2022-02-02

4- boot up and all things works as expected

I didn't encounter Wi-Fi reboot (because I couldn't make connection with Wi-Fi never)

Unfortunately the ROM in buggy and unstable, and it seems the development is very slow (watch it daily: https://download.lineageos.org/mdarcy/changes) because I have external EXT4 formatted HDD I have to use this ROM anyway I don't suggest using it at least for now!
[Shield Android TV Android Development] Kladderadatsch:
So for me the Rom runs stable. For my purpose, I use it mainly with Kodi, MagentaTV and SmartTubeNext, it is perfectly sufficient.

Unfortunately Lineage 17.1 has now reached retirement.

(https://www.xda-developers.com/lineageos-17-support-dropped).

I am already quite curious when the first 19th builds appear. But I don't think that this will happen in the next weeks or months.
[Shield Android TV Android Development] mrhamed:
I have an issue:

I turned on the NSTV while the TV (LG 4k) is off, it's not full screen!

#wm size
Physical size: 1280x720

So I have to reboot NSTV while TV is turned-on to fix it.

#wm size
Physical size: 3840x2160
Override size: 1920x1080

Also, I tried to fix it with #vm size reset or #vm size 1920x1080 or #vm size 3840x2160 command but not fix
[Shield Android TV Android Development] cHECKjAM:
Had exactly the same a few times. Fixes only when reboot shield.
[Shield Android TV Android Development] FigliDiGP:
Thanks for the info. I've downloaded all the files, just in case of :)
[Shield Android TV Android Development] Steel01:
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.
[Shield Android TV Android Development] FigliDiGP:
How can we give you a features wanted list ? If is it possible of course.
[Shield Android TV Android Development] Steel01:
You can always post here. But I can't guarantee that I'll be interested in or capable of doing them.

Edit: There's also an issue tracker on cm-shield (see below) that I put known bugs into. Unfortunately, I can't open that up to the public, because spam bots started targeting my server and was creating dozens of bogus accounts a day. But if something legit is posted here, I create tickets there to try and not forget about them.

Issues · CM-Shield · GitLab

GitLab Community Edition

gitlab.incom.co
[Shield Android TV Android Development] Adromir:
Can we somehow help? Like testing builds?
[Shield Android TV Android Development] Steel01:
Last time I posted testing builds before a release circa 17.1, someone claimed I was violating gpl and the administration got bent out of shape. Even though literally everything I work on is on my cm-shield gitlab instance and my build scripts even do clean checkouts from aosp, the lineage org, and there every time. They were wanting my to post a full blasted manifest for every build or something, I still don't know who wanted what from that... I don't want to deal with that garbage, so I'm not posting builds other than links to Lineage officials.

That said, everything I do is fully publicly available. If anyone wants to run personal builds to do testing and bug reports, my scripts repo on cm-shield will build them. I can answer questions on how they work if someone is interested. People have made unofficial build threads based on cm-shield before too, which I have zero problem with as long as proper attribution is given and any changes are listed. That was more popular for the shield tablet, there were a bunch of custom unofficial releases.
[Shield Android TV Android Development] Adromir:
Ah okay, I understand you dont want to deal with that stuff. But if you need someone to test, i am here to help if I can help
[Shield Android TV Android Development] Kerpi:
Is the controller absolutely needed to install a custom rom on the Shield TV Pro?
[Shield Android TV Android Development] rchris494:
you can probably get by with a usb keyboard and mouse. turn on developer mode. turn on usb debuging. adb reboot bootloader will get you to where you can fastboot boot twrp.img (from twrp website) to adb sideload. you need a mouse to nav around in twrp.

if i remember right i think a wired usb keyboard in slot 1 holding down a+b on the keyboard will do the same getting to bootloader.
[Shield Android TV Android Development] rickyray9:
I appreciate your hard work, thank you for doing this
[Shield Android TV Android Development] Kerpi:
It worked fine with a regular usb wireless keyboards.

Thanks for the answer
[Shield Android TV Android Development] Kerpi:
Loving the new rom but the usb used for usb debug is not working with usb pen or keyboard, USB Debug is off.

Does anyone have the same issue?
[Shield Android TV Android Development] Kerpi:
(Sorry, repeated previous post.)
[Shield Android TV Android Development] SgtBean0:
I can't seem to find a working download link for my 2017 Shield TV, the link in the first post heads to https://download.lineageos.org/foster which says there are no builds available. Am I doing something wrong?