yashsingh1/xdaforums huggingface dataset:
[Google TV General] xJumper:
Actually I was able to use my trusty dummy Google account to sign in and then sign out of it, it seems you are able to also disable the dangerous trio, (Play Store, Services Framework and Play Services) in the apps settings essentially giving you the naked ASOP Lineage experience; I'm going to see if I can just use Aurora store/F-Droid.

I could be wrong here but doesn't the microG project just sort of "port" things over a month or three later for all the devices on the official Lineage tree? Seeing as there is official builds coming out soon, shouldn't take long before microG tree releases a carbon copy without Google'ness baked in.
[Google TV General] npjohnson:
MicroG has no ATV support. The ATV builds they have released in the past exploded in horridly broken ways lol
[Google TV General] HartmutH:
Is there a way to install F-Droid or apks?
[Google TV General] npjohnson:
Just ADB install them
[Google TV General] Big Dumb Object:
Nowadays, LOS for MicroG is only a few days behind the vanilla LOS.

For example, the first official build for Moto Edge 20 was released on September 3rd, and then we already had the MicroG build on September 7th.
[Google TV General] js8call:
Would like to install Viper4Android..any help?
[Google TV General] npjohnson:
MicroG won't build for ATV. It doesn't work.
[Google TV General] npjohnson:
Also, I solved the signing issue with Luca's help.

Builds should hopefully roll for wade/Deadpool with no GMS tomorrow.

I'll then look into tablet builds feasibility.
[Google TV General] HartmutH:
I never tried it before. It works perfect with:

adb install -f F-Droid.apk

Thank you.
[Google TV General] RiCkLaR:
What about a LOS build for the KHADAS VIM3L?

Device is already in Android mainline:

device/amlogic/yukawa-kernel/5.4/meson-sm1-khadas-vim3l.dtb

device/amlogic/yukawa-kernel/5.4/Image.lz4

device/amlogic/yukawa/bootloader/u-boot_kvim3l_ab.bin

device/amlogic/yukawa/bootloader/u-boot_kvim3l_noab.bin
[Google TV General] npjohnson:
No clue. I don't use those.
[Google TV General] rapboys16:
Is there a way to skip the initial setup?_ Doesn't find Wifi devices on the Wifi screen, I'm trying to do a quick setup but I can't. version; lineage-19.1-20220912 Device; dopinder.
[Google TV General] RiCkLaR:
I know you don't use the Yukawa bits in your builds. But what more would be needed to make a LOS build for the Khadas VIM3L? The uboot, kernel, and DTB are made available in Android's mainline repo as an Android reference board. And being that the VIM3L has the same AMLogic S905D3 SoC just like the Chromecast w/GTV, I was hoping it wouldn't be that hard to convert the Chromecast build to the VIM3L, but I admit I just noticed that the other development board LOS builds have been put on hold.
[Google TV General] Winthryth:
I have installed lineage-19.1-20220916-UNOFFICIAL-dopinder.zip on my Onn 4k using the provided guide. All went well but I can't seem to enable wifi. Anytime I go under settings and toggle wifi on, it fails to find any signals or do anything. Once I back-out of the menu and return, wifi is disbaled again. Any advice?
[Google TV General] :
Was wifi working for either of you (on the same devices) using earlier builds? It's working for me on my dopinder, but I'm using an older build. Will try installing the newest.
[Google TV General] rapboys16:
Yes, wi_fi was working in old versions.
[Google TV General] Slimshady997:
Can the buttons on the remote control of the onn tv UHD be changed?
[Google TV General] npjohnson:
Use an older build.

Testing broke stuff in that one.
[Google TV General] MonoPro9:
Hi, big thanks to you guys for building this. I was searching for this a whole while. A friend needs now the best device for this LOS 19 version. Which one would you prefer? Usecase: Apps like Tivi Mate, with Ethernet-port/Dongle - Connection. 4K and cheap. Thanks
[Google TV General] Big Dumb Object:
Currently there is only one cheap box for LOS 19 – Dynalink 4K Box. And I really doubt that anything better will appear soon. Wired interfaces can be extended with a hub and USB splitter.

Or if you don't mind paying more – Shield TV is still the best option with LOS 19 on the way.
[Google TV General] Winthryth:
Using recovery I flashed back to lineage-19.1-20220908-UNOFFICIAL-dopinder and the wifi has returned. As a side note though, whenever I ran "adb reboot bootloader" while lineage-19.1-20220916-UNOFFICIAL-dopinder was installed, my Ubuntu 22.04.1 computer couldn't find the device. Running "fastboot devices" yielded nothing and my monitor had the android tv display suggesting my device made it to the bootloader. Once lineage-19.1-20220908-UNOFFICIAL-dopinder was installed and I ran "adb reboot bootloader", fastboot found the device.

This may be unrelated to lineage-19.1-20220916-UNOFFICIAL-dopinder, but wanted to let you know.
[Google TV General] MonoPro9:
He will give that Dynalink a chance. It's really cheap and for his usercase it might be perfect. Thanks for your opinion and advise.

I'm waiting for the Shield TV since a while :D
[Google TV General] rapboys16:
We are having the same problems as you.
[Google TV General] masoodskio:
Any way to relook the dopinder boot loader after flashing back to stock?
[Google TV General] HartmutH:
I just installed lineage-19.1-20220918-nightly-wade-signed.zip. On my device it is not possible to activate WiFi. :(
[Google TV General] npjohnson:
Looking into it.
[Google TV General] MonoPro9:
Just one question about the Ethernet-Hub. Do you have tried one of these? I did some research before with the Mi Box S and it was just working with the Asix Chipset, like the Ugreen-hub.
[Google TV General] Big Dumb Object:
Bought the one from my link (USB 2.0 version), but haven't actually tried it in action yet because I'm waiting for the official release for Onn 4K. But personally, I hardly doubt it won't work.
[Google TV General] MonoPro9:
Good to know. I bought a no-name one, which was unofficially dedicated to the Amazon Fire TV Stick. I will try it and post it. It's surely the Realtek for that price.
[Google TV General] Big Dumb Object:
Yes — RTL8153 to be exact, at least in the USB 3.0 version.
[Google TV General] HartmutH:
I tried it with USB Splitter and Ethernet-Hub. Wired it is possible to connect the internet. However with WiFi it is impossible.

Any others have the same problems as me ?
[Google TV General] npjohnson:
It's known. Working on it.
[Google TV General] HartmutH:
Ah, ok. Thank you for this information and good success with debugging.
[Google TV General] Jann F:
Where can the dtb and dtbo files be found? the path mentioned in the lineage wiki is empty...

Need the dtb and dtbo for wade.
[Google TV General] BTK19:
They are in the rom zip extract them from there. but if your flashing official WiFi is broken on it
[Google TV General] Jann F:
help, this seems to have broken the fastboot and recovery...

the dtb.img also seems to only contain the string 'EMPTY'

Now the device comes up as plain amlogic device.

usb 1-2: New USB device found, idVendor=1b8e, idProduct=c003, bcdDevice= 0.07

The android still boots, but I can't access bootloader/fastboot or recovery.

Neither by holding the button while plugging in, nor via "adb reboot bootloader" or "adb reboot recovery".
[Google TV General] Jann F:
Seems like holding the button and having usb connected to a host triggers a different mode as documented here for the adt3.

Google Issue Tracker

issuetracker.google.com

Not shoving in the USB plug all the way, so only power gets connected until recovery or bootloader is booted and then shoving it in all the way leads to the expected result.
[Google TV General] MonoPro9:
Is it possible to post the Devices you did use for the Wired-Connection? I'm interested which chipset is inbuilt, for my own research.

I already have the Ugreen USB-A 3.0 Hub with the AX88179-chipset at home, but still waiting for the adapter.

Thanks in advance
[Google TV General] :
On deadpool/dopinder/wade, holding the button during pre-boot while connected to a host (that has the worldcup drivers installed) will result in a worldcup (burn mode) connection; because a button press (and hold) triggers a series of sequential checks.

If you were instead to hold the button during pre-boot with only power supplied (no host connection), a pre-boot button press (and hold) should boot the recovery partition.

Is deadpool your device? Is your os windows or linux? Do you have the worldcup burn mode drivers and command line update utility installed (here or here).

If your device can boot to the OS, it is most likely that a pre-boot usb connection is a burn mode connection if it is not a adb/fastboot (android) connection.
[Google TV General] Jann F:
It is in fact a wade, freshly unpackaged from Amazon.

I resolved my issue as written above by not connecting USB all the way, so a data connection was not made at pre-boot. Then it booted to recovery and fastboot without problems.

This should probably be noted in the LineageOS wiki, just like the passage that you have to extract the dtb and dtbo from a zip and not download it from the linked website by @npjohnson
[Google TV General] npjohnson:
Nope, dtbo and dtb will be on the mirror link next week. Just missed this week.

And interesting about "half" plugging it in, how does that work? Lol
[Google TV General] Jann F:
Thanks for your work on those devices btw!

Well the design of an USB-A connector is that the Power contacts are a bit longer than the data contacts in the plug. *shrug*
[Google TV General] HartmutH:
I use a Ugreen Hub as well but I do not know what chipset is insert.
[Google TV General] MonoPro9:
Ugreen uses the AX88179, what i've red in the most threads. A few days ago i asked a general question in the Amazon-shop, they answered immediately. This devices are well known by users with other ATV-Boxes like Xiaomi Mi Box (S), which can't connect per Ethernet while using USB-hubs with Realtek-chipsets.

Thank you HartmutH

This post will be an information for those who will face maybe problems with a hub by using Realtek-technology

Big Dumb Object or me, will post our experience with the other hubs.
[Google TV General] :
Does it work as wired in your image? Is the cable that is connected to the dynalink's micro usb port an otg cable? If so, which brand cable is it?
[Google TV General] HartmutH:
Yes, it work like you see in that image above. The cables are no name cables, lying in my cable-box for years. I do not know if it is an otg cable ...
[Google TV General] Big Dumb Object:
But the Vention's hub from my previous link is promoted as having "perfect compatibility with your Xiaomi Mi Box 3/s", and also has questions/answers confirming that statement, although it is Realtek-based.
[Google TV General] MonoPro9:
Good to know. A big problem is the lack of information for this particular Info. I already have written to at least 4-5 manufacturers/reseller/rebrander. Just Ugreen told me it immediately. The others did not have answered or still in progress.

I faced the hub-issue 2 years ago with the Mi Box S. I'm not sure if it was RTL8152 or RTL8153. It worked then with the Ugreen 3.0 hub using AX88179.

I have 2 phones, which i also want to use with the ethernet port. One of them just works with Realtek the other with Asix. But also here i do not have specific model-numbers.

Hopefully we can figure it out.

I will have 4 different devices as hub or ethernet-Adapter in use and make a small conclusion after that.
[Google TV General] xJumper:
Hey so I managed to brick two devices, first was a Dynalink Box which I successfully unbricked and flashed the first version of official Lineage OS; that device is fine except for Wifi not working, which did work when using the unofficial builds, also pairing via Bluetooth to a P6P using Graphene OS does not work, this did not work on the unofficial builds either.

The second brick I have is the Onn box, I bricked it flashing the wrong dtbo partitions. I have been able to succesfully basically get it 99% there to unbrick following the steps in this thread using burn mode, however once I flash the recovery and boot into it I cannot use my remote.

Everything is good, and I am seeing the lineage recovery that I flashed however the remote (which did work before in the OS) cannot control anything in recovery so I cannot get it to go two clicks down to Apply update via ADB or wipe/factory reset to finally flash back on OS onto the device. Anybody know a way around this? Is there a way to re-pair the remote in recovery or to a bricked device that cannot boot an OS or an alternate way to click through the menus in the recovery.
[Google TV General] MonoPro9:
I'm a newbie and not very advanced. Sorry if I do write something, what will not work but

I had some trouble before with my Mi Box S, because of loosing connection to the remote control. The only way was to use a hub, by connecting a keyboard and it worked in this case for me.
[Google TV General] BTK19:
Use the button on the side of the box
[Google TV General] HartmutH:
Did you try to use the OFF Button on your Remote Control for select something?
[Google TV General] tenfox:
Thank you once again for the work on this project.

I have switched to wade, but I hope dopinder will go official in the future. I have wade running 19.1-20220918-nightly and it is just about perfect for my use case, no tablet build needed.

Some things I have noticed that may help with wade:

1) The tree blob in 19.1-20220918-nightly is probably wrong. Using the unofficial blob worked.

2) Wifi works fine, but required some manual xml editing (see my post below for details) to remove android's mac randomizer. This is not a common need but may impact some network setups. I'm not sure if it is a limitation of android TV or lineage, but there was not a UI method to disable this feature like there is in phone/tablet builds mac randomization cannot be disabled through the UI until a connection is successfully negotiated. Problems people are experiencing with wifi are likely related either to this or #1.

3) Wade appears limited to 2 channel audio output when not using a proprietary audio stream (DD+, DTS, etc) but this is a common problem outside of premium devices such as the Cube or Shield, so probably nothing that can be fixed in software. If multichannel PCM over hdmi could be enabled, it would doubtless make wade the perfect choice for homebrew android tv.

4) Apps wanting MANAGE_EXTERNAL_STORAGE permission seem to ask appropriately, but the system appears unable to grant this. Legacy READ/WRITE permissions can be granted normally.

5) HDR. Wade really, really wants to use HDR. Even when it shouldn't and on SDR sources. Even with HDR manually disabled in Settings (I suspect this option is broken or not checked at boot), we still boot to HDR modes which then persist in apps. In fact, wade will preferentially boot to a lower resolution with display HDR support, rather than a higher resolution without display HDR support. It is possible to force SDR by manually switching to a higher resolution without HDR support, then back to lower resolutions, so the SDR modes are available, just not properly selected. I am not sure if this problem is specific to wade, or something general to lineage.

npjohnson developer of the year :)

edit: new info
[Google TV General] :
Would you expand upon this using maximum detail?
[Google TV General] tenfox:
Sure, but it requires root and some familiarity with shell. Also, you are likely aware, but this is a rare problem only for networks which filter by mac. If you are unable to see wifi networks at all, you have a different problem.

First, attempt to connect to or create a connection through the android UI to the SSID of your network. If this problem relates to you, you should be able to see your SSID but the connection will fail. That's fine, leave the failed connection there and enter shell. Then, edit:

/data/misc/apexdata/com.android.wifi/WifiConfigStore.xml

Find the code block for your SSID (it should be the only one). You are interested in the keys:

RandomizedMacAddress
MacRandomizationSetting

RandomizedMacAddress contains the randomized mac android wants to use for your SSID. You would supply this mac to your router. MacRandomizationSetting should be set to 0 (zero) to avoid re-randomization every time the interface goes up, like so:

<int name="MacRandomizationSetting" value="0" />

Reboot and you should have a persistent mac.

But wait! There is an easier way, which does not require root or shell. It turns out the UI settings are available AFTER a connection has been successfully negotiated. Provided you have access to your router settings, I would recomend you temporarily disable mac filtering on your router, connect normally, then access the wade UI Settings submenu under the active connection to disable mac randomization. You can then re-enable mac filtering on your router and supply the (now persistent or hardware stock) mac.

I have also encountered another issue which may be problematic for android TV on wade:

5) HDR. Wade really, really wants to use HDR. Even when it shouldn't and on SDR sources. Even with HDR manually disabled in Settings (I suspect this option is broken or not checked at boot), we still boot to HDR modes which then persist in apps. In fact, wade will preferentially boot to a lower resolution with display HDR support, rather than a higher resolution without display HDR support. It is possible to force SDR by manually switching to a higher resolution without HDR support, then back to lower resolutions, so the SDR modes are available, just not properly selected. I am not sure if this problem is specific to wade, or something general to lineage.
[Google TV General] npjohnson:
Thx for debugging this. GMS successfully randomized Mac, the aosp component appears to fail. I will disable Mac randomization and fix it.

What do you mean the "blob" I'm the official is wrong? What blob?
[Google TV General] tenfox:
You're very welcome. I'm delighted to have made a contribution.

dtb.img

The partition image in 19.1-20220918-nightly appears to have failed to build. It still boots, but with significantly reduced functionality. I see you have just pushed 19.1-20220925-nightly. I have not flashed this yet, but I think it has the same problem. Compare the partition from 19.1-20220908-UNOFFICIAL.
[Google TV General] RiCkLaR:
Looking at changes for 20220918 build, saw that VENDOR.PROP still has this:

ro.vendor.sdr2hdr.enable=true

I believe that is from Amlogic's source-code by default, which has been affecting other Amlogic devices for the last few years of automatically forcing SDR-to-HDR upscaling, and has somehow been migrated into these builds.

@npjohnson can we get that prop flipped to FALSE or removed from build completely?
[Google TV General] npjohnson:
Stock sets it though? Why wouldn't we.
[Google TV General] RiCkLaR:
Cause it causes problems, it would be beneficial to not have the device upscale everything to HDR when viewing SDR content; especially for people who have old HDR compatible 8-bit TV-panel's that don't actually output 10-bit color correctly, cause they will have an extremely over-saturated color palette.

The Amlogic source-code I have is for Android 9, and their supplemental vendor app DROID_SETTINGS had these activities:

com.droidlogic.tv.settings.display.sdr.SdrSettingActivity

com.droidlogic.tv.settings.display.hdr.HdrSettingActivity

And the only Amlogic device I've seen be updated to give User access to these settings activities was the the Onn.4K, but Askey only made the HdrSettingActivity available, it's where you switched it to On, Off, or Auto; it was labeled as the "HDR" setting, and made available under the Display settings options.

If somebody had the time to code all the extra settings that Amlogic makes available for the DROIDLOGIC app to access, that would be awesome, but for now I just ask that we eliminate that sdr2hdr prop.
[Google TV General] :
Is it implemented in a different way for R or higher?

Every certified device I've seen running android 11 (usually on a X4 or Y4 SoC), has this setting in display->screen resolution;
[Google TV General] tenfox:
Great find and I agree. sdr2hdr should be disabled, at least until HDR can be reliably disabled through the current Settings toggle. This should not affect actual HDR source content. See below, the culprit is probably hdr_policy.

The wade 19.1 build allows manually disabling display capabiliities (HDR, Dolby Vision, etc), but the setting appears to be ignored. Or is being overridden by the sdr2hdr check.
[Google TV General] :
Aren't some of those tied to the keystore (along with netflix mgid and drm)? For example, dolby vision can't be enabled merely by the build prop setting, right?
[Google TV General] willclein:
I've been having some difficulty installing LOS on Wade. I've followed the instructions, but when I get to "Flashing the dtb and dtbo partitions", I start having issues.

I go to the link to download both of the files; however, only the dtbo.img file is present. I read on the XDA page for the build to pull the files from the LOS zip file, so I pull the dto.img file from there.

After flashing both files and the recovery image, I try to run

fastboot reboot-recovery

which does nothing.

I also tried

fastboot reboot recovery

which did nothing.

I instead run

fastboot boot recovery.img

which boots into the recovery image.

When I go to Apply Update>Apply from ADB, adb sideload starts on the device, but when I run

adb devices

no device is detected. I also tried Advanced Settings>Enable ADB but still saw no devices connected.

I reboot into the system (which no longer has Wi-Fi due to flashing the dtb and dtbo images), and check that USB debugging is still enabled. I toggle the setting and the device indicates USB debugging is connected, but I do not get a prompt to authorize my computer and

adb devices

still shows nothing.

Does anyone have any suggestions for how to proceed or where I went wrong?
[Google TV General] tenfox:
Use dtb.img from https://github.com/ods-releases/wad...ade/lineage-19.1-20220908-UNOFFICIAL-wade.zip
[Google TV General] npjohnson:
maybe the prop does override it. I'll remove it to see.
[Google TV General] tenfox:
I believe I have a runtime fix for HDR issues. The problem is not sdr2hdr but the S905Y2 hdr_policy setting.

Tested:

1) Setting sdr2hdr false in /vendor/build.prop did not change behavior

2) Setting /sys/module/am_vecm/parameters/hdr_policy to 1 produced SDR video from SDR sources and HDR video from HDR sources.

I would recomend leaving sdr2hdr as true (this probably enables the capability, rather than forcing the upscaling) and define /sys/module/am_vecm/parameters/hdr_policy as 1. That option could eventually be addressed in Settings if the UI option is implemented.
[Google TV General] willclein:
Using that causes me to not be able to enter anything but the u-boot and fastboot modes
[Google TV General] tenfox:
You probably have stock boot and stock recovery on the device (even though you previously attempted to flash lineage recovery), or possibly have a corrupt image.

I would try, in order, flash from fastboot: 1)

un

official lineage (19.1-20220908-UNOFFICIAL) dtb.img, 2) official lineage (19.1-20220918-nightly) dtbo.img, 3) offical lineage (19.1-20220918-nightly) recovery, then fastboot reboot recovery, enable adb, reboot to recovery, format/factory reset, adb sideload.

You can probably substitute 19.1-20220925-nightly for any official files, but I have not tested that build yet.

If you still cannot boot, you likely have a different problem that will require further troubleshooting (verify you are unlocked? check cables, drivers..). As long as you can access fastboot or burn mode, you should be able to flash lineage 19 eventually when newer releases happen. Or you could always flash older dtb and dtbo to boot the stock rom still on your device or install lineage 18.
[Google TV General] npjohnson:
merged https://review.lineageos.org/c/LineageOS/android_device_amlogic_g12-common/+/339786 - I'll fix TvSettings side and revert it soon.
[Google TV General] samdsmith:
which rom is for tanix tx3 mini?anyone can tell?help plz
[Google TV General] endera:
radxa zero ?