yashsingh1/xdaforums huggingface dataset:
[Google TV General] npjohnson:
The wiki has been updated with https://review.lineageos.org/c/LineageOS/lineage_wiki/+/382062 - it is deployed, please flash the 12 bootloader image and then proceed to follow the wiki instructions again, should work fine.
[Google TV General] CollieBabaX:
Hi guys, does anyone know if this issue has been resolved?
[Google TV General] Functioner:
Yes, the fix was announced here.
[Google TV General] npjohnson:
Thank you again for helping solve this. Massive credits to @Functioner for helping work those issues out and testing.

Yeah, the devkits are at the best point they've ever been.
[Google TV General] CollieBabaX:
Very good, great work, thank you guys(y)

I will try in the next days
[Google TV General] npjohnson:
Working on Sabrina officials as well - will rely on having unlocked on 10, so likely not super useful to a ton of people, but fun for those who still have them around.
[Google TV General] kennkanniff:
Awesome developments.

I was able to find my Sabrina remote on a Radxa 0 but was unable to pair.

Saw this in the logcat:

bluetooth: assertion 'op_code == OpCode::NONE' failed - Received COMMAND_COMPLETE event with OpCode 0x2016 (LE_READ_REMOTE_FEATURES) without a waiting command(is the HAL sending commands, but not handling the events?)

Would be great to have a bluetooth remote working on the radxa 0.

Nice! Will it still suffer from Bluetooth remote issues?
[Google TV General] npjohnson:
The zero along with all other supported targets do support Bluetooth remotes, it's literally just Sabrina's remote that is the problem.

It's currently one of the holdups as to why I can't ship Sabrina lol.

Try any other remote.
[Google TV General] kennkanniff:
That's what I thought. Thank you.

Blown away by zero performance. Even prime video works; definitely wouldn't have expected that. Awesome.

Would it be possible to RTL8821CU usb driver to M5 device tree? It is supported on stock.
[Google TV General] npjohnson:
Yeah, make defconfig edits and push 21 branch on gerrit (instructions on wiki)
[Google TV General] wesdadude:
I've run into the same issue after using the builtin updater to update to 20-20240201-NIGHTLY-WADE. The device boots with WiFi toggled off and it doesn't pick up any networks when switched on.

I think I ran into a similar issue when I first installed Lineage. I have lineage-20.0-20231015-nightly-wade-signed and lineage-20.0-20231019-nightly-wade-signed in my downloads. I believe the October 19 build had the same issue. I also have the October 26 one which didn't boot at all.

I installed GApps when I first imaged.

Is there a way to roll back while keeping my apps and data?
[Google TV General] kennkanniff:
i tried mi box remotes and they did not work, a XMRM-006 and an XMRM-010. Could you point me to some generic android tv remote on amazon that is guaranteed to work?
[Google TV General] npjohnson:
confused.

I just tried both an Onn remote, and a shield TV remote. Both worked fine.
[Google TV General] kennkanniff:
Yeah me too, they both work fine on a (lineageos) phone..
[Google TV General] mmortal03:
Thanks, I was out of the loop. Mine just got the update. For reference, it now shows:

Android TV OS version 12. Firmware version 2.01.04. Security patch level November 5, 2023. Kernel version 4.9.269 (Nov 17, 2023).
[Google TV General] Big Dumb Object:
Am I correct that using an obsolete Radxa's aml-flash-tool that doesn't work on 64-bit Ubuntu/Debian is the only way to prepare Zero for LineageOS installation?

If so, where can I get the partitions images contained in aml_install_package.img to flash them one-by-one with Khadas's update tool that doesn't have such compatibility issues?
[Google TV General] npjohnson:
you're confused.

aml-flash-tool works fine on ubuntu 64 bit. It doesn't work on _arm64_ it works fine on x86_64.

Just follow the instructions, I just ran through them yesterday on the radxa0 on ubuntu 22.04 x64, worked fine.
[Google TV General] Big Dumb Object:
Yes, indeed. But in my case INSTALL.sh can't resolve the same lib32ncurses5 dependency.
[Google TV General] npjohnson:
Just install it manually
[Google TV General] Big Dumb Object:
The problem is that lib32ncurses5 is no longer in the Ubuntu/Debian repositories: only lib32ncurses6 or libncurses5. Radxa's aml-flash-tool just needs to be updated a little, but it's abandoned already.
[Google TV General] Big Dumb Object:
OK, I am edited INSTALL.sh by replacing lib32ncurses5 with lib32ncurses6, and was able to finalize installation. But now I have "Amlogic device not found", despite the lsusb command recognizing it correctly:

Bus 001 Device 003: ID 1b8e:c003 Amlogic, Inc. GX-CHIP

Maybe it's because I don't have a hardware USB 2.0, or maybe it's because I'm operating inside VM, but... There was no such an issue when reanimating dopinder.
[Google TV General] CrystalCommunication:
Mi Box remotes don't work for me either. Any other Android remote including a FireTV remote works fine.
[Google TV General] CrystalCommunication:
I just booted into recovery and sideloaded the previous build, didn't bother wiping data, no issues afaict.
[Google TV General] madman:
After having some fun with unlocking and soft bricking my dopinder, I finally was able to install the latest build of LOS lineage-20.0-20240214-nightly-dopinder-signed.zip onto it.

Its now stuck on searching for accessories page at the boot. I clicked the back/home button combo to get the remote visible but can't seem to pair it. Is this supposed to happen? I searched the threads and don't see anyone having such issue before.
[Google TV General] npjohnson:
does the remote LED show pairing?
[Google TV General] madman:
It does (with that blinking). I can see the remote popup in the list of devices as well. I tried using the power button on the dopinder to navigate the list and select it. I can see it starts pairing but never completes.
[Google TV General] npjohnson:
Strange.
[Google TV General] Big Dumb Object:
Yesterday I was able to flash aml_install_package.img (not on the first try, but eventually I got the Resetting board [OK] message). But, all I get after cycling power is black screen like with dopinder, but this time the device is undetectable with adb devices or fastboot devices. Could it be the folowing provisions from the first step of installation guide are really necessary to be followed?:
[Google TV General] npjohnson:
No, unrelated.

I don't know what you mean by the same black screen is a dopinder, you don't get video output from dopinder?
[Google TV General] Big Dumb Object:
In these two posts and a little further on. My monitor clearly recognizes the device, but all that is rendered is a blank/black screen. But this time, the recovery doesn't appear even for a moment, and I can't proceed even in CLI mode.
[Google TV General] npjohnson:
Is your monitor 1080p or 4K?
[Google TV General] Big Dumb Object:
QHD.

And is it normal that the device is invisible to ADB?
[Google TV General] madman:
It was pretty useless without the remote. So I flashed the LOS21 latest build and that had no such issue. The setup screen was completely different (like what a normal TV would do, instructions to click the buttons). Maybe something in setupwizard is weird on LOS20 in certain conditions?
[Google TV General] npjohnson:
Are you saying that you didn't get the animation on 20? It very well should have been there, did you flash Google apps on 20?
[Google TV General] madman:
Well now I feel stupid. I indeed didn't flash Google apps as its been a while I used LOS. Let me go back to LOS20 and see if things work this time. I can just sideload is right after LOS binary flash right? Or do I need to reboot the recovery (I remember on phones I had to do that sometimes).
[Google TV General] npjohnson:
Whatever the wiki says for that specific device is what you should do
[Google TV General] Big Dumb Object:
And one more question: how to completely wipe/reset Radxa Zero to factory defaults?

I'm trying to re-flash aml_install_package.img, but after ~10 attempts still no success - the process crashes at different stages every time. 🥵
[Google TV General] npjohnson:
you can just flash whatever radxa distributes.

If it fails doing that you have a system related problem.
[Google TV General] madman:
I don't know what I'm doing wrong but I can't get LOS20 to boot now on dopinder with Google Apps :(.

I went back to full stock binary with A10, upgrade its way to A12. Flashed everything as documented along with Google Apps (arm one, without booting into LOS). It gets stuck on boot animation. If I follow the same steps with LOS21 binary, things work. I did format /data as suggested in wiki as well.

Is there some log file that I can get from recovery (adb) that will help me figure out what is wrong?
[Google TV General] npjohnson:
Not really if it doesn't auto reboot.

I can maybe try locally.
[Google TV General] madman:
What do you mean when you say if it doesn't auto reboot? On the first boot after flashing everything it does auto reboot after a while and the comes back to the same stuck screen. Will there be a log file in this case? I don't think it keeps rebooting after that initial one.
[Google TV General] npjohnson:
Oh, yeah, after the failed boot go directly to recovery and enable adb then pull /sys/fs/pstore
[Google TV General] jackeagle:
Moderation Edit

Thread closed per [OP] request.

-jackeagle

Senior Moderator
[Google TV General] otttvbox502:
If you sideloaded gapps then you need to sideload gapps after update

Do not format anything just reboot

That is what worked for me
[Google TV General] npjohnson:
correct, it is now fixed to so won't happen next time as long as you flash the updated GApps
[Google TV General] _emanuel_:
@npjohnson

Hello, I would like to port the ATV to my box (dreambox one/two g12b/s922x).

I have now downloaded the linageos-20.0.

Which device do I use best to adapt

and how do i get it in the repo?

E.g. https://wiki.radxa.com/Zero/dev/LineageOS

Thank's Emanuel
[Google TV General] npjohnson:
Give me your devices specs?
[Google TV General] _emanuel_:
data:

Dreambox ONE UltraHD

Wifi + BT

BCM4356A2

linux-meson64/arch/arm64/boot/dts/amlogic/dreamone.dts at master · emanuel4you/linux-meson64

linux meson64. Contribute to emanuel4you/linux-meson64 development by creating an account on GitHub.

github.com

I've build amlogic_galileo(orginal + dreambox kernel bsp 4.9), yukawa android (mainline no audio, no vdec mpeg1/2), khadas android p9 (with dreambox kernel bsp 4.9) - all on sdcard
[Google TV General] dirt_devil:
@npjohnson

first off: i was a silent reader of the last Linage Topic and also for the Linage20 here. after some missleading i managed to flash everything for wade. it worked well. i wanna thank you and all others who are helping here a lot. Great Rom and good advices if smt isnt right. finally i needed to create an account on my own ;)

now i tried last wade official and i cant manage to change the keyboard to another language or even change the keyboard itself. in keyboard menu i cant activate another keyboard. only leanback is active.

i gave another shot for unofficial wade to flash - its the same. cant change the keyboard or keyboard language. is there something special todo?
[Google TV General] npjohnson:
Which keyboard are you trying?
[Google TV General] dirt_devil:
I just want to change the language of the keyboard. The onscreen keyboard is QWERTZ - which is fine, but if i use my usb logitech k400+ keyboard (QWERTZ layout) YZ is swapped. so in my mind i wanted to change the keyboard app (or even set/change the language of the leanback-keyboard??), but it wont let me change the used keyboard app.

//edit: wow - sometimes you get blinded somehow i guess...

when i put usb dongle in, it will come up a new entry in keyboard - physical keyboard - there u can set the language for the logitech keyboard. works like a charm.

But its still not possible to change the used on screen keyboard app?
[Google TV General] _emanuel_:
I tried https://wiki.lineageos.org/devices/wade/build but it doesn't work to build an img.

Not even with local_manifests:

<project name="TheMuppets/proprietary_vendor_amlogic_g12-common" path="vendor/amlogic/g12-common" revision="lineage-20" clone-depth="1"/>

<project name="TheMuppets/proprietary_vendor_askey_wade" path="vendor/askey/wade" revision="lineage-20" clone-depth="1"/>

emanuel@xanadu:~/lineage$ source build/envsetup.sh

emanuel@xanadu:~/lineage$ breakfast wade

In file included from build/make/core/config.mk:353:

In file included from build/make/core/envsetup.mk:352:

build/make/core/product_config.mk:228: error: Can not locate config makefile for product "lineage_wade".

14:02:19 dumpvars failed with: exit status 1

Device wade not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).

Failed to search GitHub

In file included from build/make/core/config.mk:353:

In file included from build/make/core/envsetup.mk:352:

build/make/core/product_config.mk:228: error: Can not locate config makefile for product "lineage_wade".

14:02:20 dumpvars failed with: exit status 1

In file included from build/make/core/config.mk:353:

In file included from build/make/core/envsetup.mk:352:

build/make/core/product_config.mk:228: error: Can not locate config makefile for product "lineage_wade".

14:02:22 dumpvars failed with: exit status 1

** Don't have a product spec for: 'lineage_wade'

** Do you have the right repo manifest?

emanuel@xanadu:~/lineage$
[Google TV General] npjohnson:
Are you connected to the internet when running that?
[Google TV General] _emanuel_:
Hm, I had a python ssl certificate problem. But that only became visible after I built almost the entire roomservice.xml myself. I have now patched the roomservice.py. now it works. It is currently generating the build.ninja. see my fix for ubuntu 18 LTS
[Google TV General] npjohnson:
toss that on our Gerrit - info on how to is on the wiki.

Worth reviewing there.
[Google TV General] dysoct:
Hi. So I tried out the official stock build of Android TV 12 of wade. Ever since doing so, I'm unable to get LOS 20 to boot up on this device (LOS 19 booted up and works as it should). I have repeated the installation many times following the guide but it failed everytime (it only booted to Bootloader). Attached is the logs from recovery. If this is incorrect, please guide me on where to get the proper logs. Cheers.
[Google TV General] darkknight7:
Has anyone found a version of youtubetv app where video works? I've tried about 10 different myself.
[Google TV General] dirt_devil:
i am useing STN https://xdaforums.com/t/apk-smarttubenext-android-tv.3949377/

/edit: sorry i did not see YT "TV" app. Sorry.
[Google TV General] Mogul345:
Long-time lurker here with a dopinder. I check in every so often to see the status of Widevine L1 on dopinder, as unfortunately Netflix is in use in our home.

I don't see any updates in this thread, so is it safe to assume things are still at the state they were in 19.1 - Not sure what the issue is, maybe something in the /factory partition?
[Google TV General] npjohnson:
There will be a huge announcement and a banner slapped in the OP when we fix that lol I promise, we have not yet
[Google TV General] Slimshady997:
I really hope so, I have tried each of the versions that have been released for dopinder to test it and I would be very happy to have an official and stable version.
[Google TV General] swim9988:
Hey, I've been enjoying wade, thanks again for the hard work!

Recently upgraded to LOS20, and everything is great except I can't launch anything from home screen, IE widgets from jellyfin and plex. I have to open the app and then navigate to episodes that way. Not a huge convenience, but I wanted to see if that's a known issue. Thanks.
[Google TV General] ExplosioNxACE:
Hi, Any news on the Problem with the development Boards? I'd really like Lineage OS 20 to run on my

radxa Zero
[Google TV General] bumerc:
Compiled (MindTheGapps included) and tested on GXL boards S905D and S905L, runs fine and in my view faster than ATV12L. Very good work! 👍
[Google TV General] npjohnson:
Sadly no. Some sort of DTB issue
[Google TV General] S1ngl3-x:
Last update failed on wade official. Anyone knows what is happening and what to do?

Something about verification error. I rebooted back from recovery and it still works thankfully.
[Google TV General] anly11:
I have old x96 box with s905x chipset. Is LOS 20 compatible with it?
[Google TV General] TheEnekaign:
Currently running the newest 20 (unofficial) release on Wade, and I'm running into a really weird issue. Long story short I got a new 4K TV and I'm trying to figure out why it's just showing "AndroidTV" on boot followed by a blank/black screen (no LineageOS boot splash, etc). The box will power on/show the home menu just fine when plugged into a 1080p TV (I've tested it back and forth and it's consistent).

The weird thing is that if you boot it up on a 1080p TV, then switch what TV the HDMI cable is plugged into (without powering off the box), it works fine on the 4K TV, as long as it doesn't turn off. If you do it in the opposite order (powering it on on the 4K then plugging it back into the 1080p), the black/blank screen will remain.

On either TV I can access recovery mode just fine. I've tried several different HDMI cables, different power cords, different power sources (brick vs TV vs even my laptop), even tried different home menu launchers (I was originally using FLauncher, but I set it back to the Google one), all with the same results. I haven't tried clean flashing/resetting Lineage yet (was trying to avoid that), but I can try that if need be.
[Google TV General] dorkshoei:
I just bought a radxa zero hoping to install Android based on reading https://wiki.radxa.com/Zero/dev/LineageOS I see "radxa0 - Rock Pi Radxa Zero" struck out on the 19.1 thread here also.

https://updater.oddsolutions.us/#/devices/radxa0/builds yields an error. I can't tell if building from 18.1 source is also impacted and whether there are any binary builds available?
[Google TV General] npjohnson:
The build guide for 18.1 works fine. Just sync github.com/TheMuppets/propreitary_vendor_amlogic to vendor/amlogic in the source tree. All will work fine then.
[Google TV General] dorkshoei:
Are there any pre-built 18.1 binaries? Or is building from source the only option?
[Google TV General] npjohnson:
Build from source.
[Google TV General] dorkshoei:
Thanks. I assume https://wiki.oddsolutions.us/devices/radxa0/build generalizes to 18.1 (it's a lot more detailed than the version on radxa wiki).
[Google TV General] npjohnson:
yup, just replace 20 with 18.1 and done
[Google TV General] ChriMo:
I tried to look for wade - Dynalink TV Box (4K) in Continental Europe (ebay, shop-search) but could not find it anymore. Would appreciate hints to where buy, also PM. Thx
[Google TV General] talksickisil:
It sounds like you might have to update the recovery to match the date of the build you are trying to flash.
[Google TV General] talksickisil:
Ha! I just recommended to somebody they should buy one. I should have done research before making the suggestion because you can't buy a brand new one anymore. It has me considering donating mine since I usually just use the (inferior) Google tv built into my tv.
[Google TV General] ChriMo:
Unfortunate. I really hope some producer sees the niche and releases a nice 4k device, with BT+IR remote (maybe also optional DVB-T2 receiver model) which can easily run Custom ROMs like LineageOS 20. And if I can dream hardware good enough for better games and AV1 etc. decoding - and Ethernet or external device USB connections... -_-
[Google TV General] treypop:
There are rumors of an ADT-4 coming out at some point so that might answer your wishes
[Google TV General] npjohnson:
Was supposed to be Q1 of this year but got pushed a little - ETA "Soon^TM" I'm told
[Google TV General] zweiund40:
Hi@all,

i'm trying to unlock my wade to install this on it. Did this with an other wade some time before. The box i'm trying this time now was brandnew. Unfortunately it upgraded the OS to Android 12 on first boot.

Now im stuck with 2 Problems.

First: OEM-Unlock in Developers Options is greyed so i can't activate it.

Second: Howto get back to Android 10? The Wiki says there are guides on the net, unfortunately i can't find it. Did anyone have some Informations for me howto do this or a link.

Would be great!

THX a lot!

42
[Google TV General] Charlesnasi:
Is there a way (and guide) to compile LineageOS 20/19 for an X96Air S905x3 box? Did in the past build my own CM images for OPO (Bacon), but that is a long time ago. Want to learn/start again, but don't know where to start.
[Google TV General] wyldwilly:
I just installed the 20230326 Dopinder build via the Updater and now the remote doesn't work. I've got multiple Dopinders and I confirmed that the device refuses to connect with multiple remotes. Factory reset also did not help.

When I was resetting the device, I also noticed that the Recovery was version 20230209. I thought the Updater was supposed to keep the Recovery up to date too. Any suggestions?
[Google TV General] npjohnson:
You have to toggle the switch in settings for recovery to updates alongside OS.

Also, yeah, I just checked and only dopinder, but BT is dead - debugging it now.
[Google TV General] wyldwilly:
I thought I had checked the "Recovery update switch"...I guess this is something I will try to remember to do prior to each update. Thanks for the reminder!

On a brighter note: DRM is probably still broke, so this BT issue doesn't really negatively affect the usefulness of these turds lol
[Google TV General] npjohnson:
The dopinder bluetooth issue is fixed and the build uploaded. Sorry for the inconvenience.
[Google TV General] wyldwilly:
This fixed the BT issue, thanks!

I have to ask: when is DRM going to be fixed? By now, if the problem hasn't been identified I'd like to stop wasting time and switch back to factory. On that note, has anyone reverted back to factory and how did you do this?
[Google TV General] npjohnson:
We have no idea, no ETA whatsoever.

Ask for factory, on download.ods.ninja under the firmware directory you will find a factory image for dopinder
[Google TV General] wyldwilly:
Thanks!

Please consider adding some sort of "DRM will most likely never work on this device disclaimer" on https://wiki.oddsolutions.us/devices/dopinder/
[Google TV General] wyldwilly:
Hey, I'm seeing this intermittently on Dopinder too. I wasn't going to bother posting about it since DRM is still broke on Dopinder and I'm switching back to factory...
[Google TV General] CrysisLTU:
Is there a writeup on the DRM issue? Like describing what and where is the problem, what has been tried, logs, etc etc... Info that would help other developers to narrow down, diagnose and understand the problem.
[Google TV General] npjohnson:
Just look at the logs honestly.

It's cryptic and the log is unhelpful, and you can see what we tried by looking at what worked on Wade, that's about all we've tried because there's not a ton left to do.

You can't really use older DRM stacks because they're incompatible with newer versions of Android, and the newer DRM stacks seem incompatible with dopinder's proprietary stack, it's just a mess
[Google TV General] deleoren:
Xiaomi Mi Box S 4K Android TV Box

Did I mistranslate the description? Is it compatible with this device?
[Google TV General] npjohnson:
No it is not.
[Google TV General] 1Condottiere:
I cannot find the link for downloading Lineage 19 for dopinder. The link in this thread points to 20. Also, my understanding is that 19 is the only one that works fully with DRM and all. Kindly correct me if I am wrong. Thanks for the team's work. I read the Android 12 TV specs and it seems an upgrade is actually a good thing rather than staying with 10, security issues aside.
[Google TV General] npjohnson:
Nothing has ever had DRM working on dopinder.

Software codecs kinda work but they're not ideal at all.