yashsingh1/xdaforums huggingface dataset:
[Google TV General] bumerc:
Hi

Unfortunately not a good result. I'll try to play around with the compatibility_matrix..

Full boot log after clean install > https://katb.in/kupivahuveq

FYI: Revisions up to 13.0.0_r43 - builds work fine.

Newer revisions 13.0.0_r61 hang on init
[Google TV General] Big Dumb Object:
A little off topic, but this is the best place for this question, I suppose. Now that we have official LineageOS 20 for amlogic development boards, do these tablet-style builds support Auto Frame Rate similar to the AndroidTV builds for the TV boxes discussed here?
[Google TV General] Functioner:
I couldn't get a build to finish booting on the GXL based 805Y (onn FHD 2k stick). This was using the factory bootloader designed for android 9. Going to try again now that there is an android 10 bootloader for the onn 2k stick.
[Google TV General] npjohnson:
coolio

They actually are also Android TV.

There _are_ tablet build targets but no builds provided. You can build radxa0_tab, m5_tab, odroidc4_tab to get tablet builds. I can't make them official due to a few reasons right now.

weiiiirddd - lmk how it goes - I'll retest my GXL device.
[Google TV General] Big Dumb Object:
Do we both mean these official builds maintained by Stricted? Are these really AndroidTV? And if these builds are tablet still (as I assumed they are), do they support AFR regardless?
[Google TV General] npjohnson:
Yeah, the official builds are Android TV just like the other G12 devices, like I said there are tablet build targets you can go build yourself if you want.

I have no clue if it supports AFR, if the hardware supports it it should work fine.
[Google TV General] bumerc:
Compared to r43 - in r61 the following preloaded classes are missing:

> system/system/etc/preloaded-classes:android.security.keystore2.AndroidKeyStorePrivateKey
> system/system/etc/preloaded-classes:android.security.keystore2.AndroidKeyStorePublicKey
> system/system/etc/preloaded-classes:android.system.keystore2.KeyParameters
> system/system/etc/preloaded-classes:android.system.keystore2.OperationChallenge
> system/system/etc/preloaded-classes:[Landroid.system.keystore2.Authorization;

Are these classes no longer needed?
[Google TV General] ji:
if anyone has the zip for sti6130d350-user 12 SC 20221221 please let me know! my wade wont grab it over OTA unfortunately and dynalink hasn't biten into giving me some help
[Google TV General] Functioner:
Hopefully you know what you're doing...

h..ps://android.googleapis.com/packages/ota-api/package/5381cc9fb70457089d28294127906793fc71d588.zip
[Google TV General] matrix200200:
Stupid question, is there any place where I could see changelog for the latest dopinder release available in the OTA updates?

I generally don't like flashing, but would still want to stay up to date, if there are some important changes.
[Google TV General] npjohnson:
the unofficial only get builds when monthly security patches drop or important bug fixes, so always update.
[Google TV General] ji:
thank you! i was on the version before and OTA would not pick this one up for some reason, as soon as I flashed to it though, OTA picks up the security update after this one - guess they borked the settings on their end
[Google TV General] updater14:
...and I say hello again.

After two weeks I get my wifi/bt module for my banana pi m5:

Now I want to pair my Pixel 6 to control my banana.

But which button I've to use to confirm pairing?

SW5 short = Standby/Off

SW5 long = ask me if I want to Shutdown or Restart

SW4 = nothing

Greetings
[Google TV General] npjohnson:
probably going to need a usb keyboard
[Google TV General] updater14:
Probably not working... :-(

Before two weeks kennkannif told us that USB keyboards not working:

https://xdaforums.com/t/official-un...2-sm1-ne-family-devices.4534935/post-88747651

Nothing works over USB.
[Google TV General] npjohnson:
....

Nothing works over USB?

Have a tough time believing that absolutely nothing works over USB.
[Google TV General] updater14:
When I install the original Android Image from https://wiki.banana-pi.org/Banana_Pi_BPI-M5#Android_2

USB keyboard, usb touchscreen and other devices works great.

When I use lineageOS image I can't finish boot because there is no chance to control anything in recovery or pair a bluetooth device in normal boot up. :-(

So I'm not shure what I've to do or where my mistake is.
[Google TV General] w00cash:
I have some difficulties executing this. When I try to "burn mode" by holding the button while plugging USB cable to my PC nothing extraordinary really happens. Device just starts normally, it passes through the dynalink logo and runs as usual while beeing visible in device manager as Android Composite ADB Intereference. Is there smething I'm doing wrong? I have tried to change the duration of button holding from few seconds to 10+ to no avail. When I hold the button when USB is already plugged in it factory resets the device.

Any suggestions?
[Google TV General] kennkanniff:
How is it not clear yet that USB is not working...
[Google TV General] updater14:
Is there any chance to get USB working?

Or how I can pass these pairing screen for now?
[Google TV General] Functioner:
Does usb work at bootloader stage? For example, if bootloader is interrupted prior to booting the application image, does "usb reset" at shell prompt cause successful usb enumeration to happen (assuming that a fat32 flash drive is inserted)?

What's the value of "otg_device" env variable for u-boot?

Try hex patching the boot partition image, changing the cmdline in the header from otg_device=1 to otg_device=0.
[Google TV General] Max-E-Moose:
Have you found and installed Amlogic USB Burning Tool? The WorldCup device driver is necessary on Windows.

When entering "Burn mode" the device should stop booting while displaying a Dynalink logo. If it continues to boot then you are not entering "Burn mode" and need to try again.
[Google TV General] highwaystar_ru:
I have checked current sources with a95xf1 device tree from https://github.com/G12-Development/android_device_amlogic_a95xf1

and it boots fine from clean install. If you think it is issue with dependencies linking try to run logcat from uart console you capturing dmesg from.
[Google TV General] w00cash:
I have installed amlogic burning tool, and it displayed a prompt that the driver was installed succesfully. As a matter of fact I did everything as instrusted dozen of times. I have even did the same thing on different PC.

Regardless, my wade always behaves the same: boots into system and is visible to Windows device manager as Dynalink tv no matter how long the button is pressed.

I have no clue what I'm doing wrong. I'm very close of letting idea of installing Los go completly...😒
[Google TV General] talksickisil:
Very nice to see support on this project has expanded to the sbcs. Cheers
[Google TV General] mmortal03:
Does @npjohnson actually own a Banana Pi M5?
[Google TV General] updater14:
In recovery there is no working USB see: https://xdaforums.com/t/official-un...2-sm1-ne-family-devices.4534935/post-88751669

I just wanted to follow the instructions and install LineageOS on Banana Pi... :(

Install LineageOS on m5 | LineageOS Wiki

wiki.lineageos.org

For months, this endeavor has been doomed to failure.

I think I'll give the original Android 9 image a chance.

This is ready to use.
[Google TV General] Functioner:
Of course, the recovery uses is own bootable partition (recovery), so a patch of the otg_device value in the boot partition image would have no effect. However, for recovery it might be preferred to use device mode for usb (so as to connect to pc via adb) as opposed to host mode (so as to connect peripherals to the M5).

I have a M5 in the closet somewhere. I will dig it out and check the build. I don't have wifi/bt modules for it, but I should be able to check all of the usb ports for both boot and recovery.
[Google TV General] updater14:
That sounds great.

According to the instructions, the device must be controllable in recovery.

My USB ports work fine in the official image: https://wiki.banana-pi.org/Banana_Pi_BPI-M5#Android_2.
[Google TV General] npjohnson:
No, Stricted is the maintainer for those devices.

I have radxa0 where this all works fine.

I looked and am not sure what's up, someone will need to debug this and work through it.
[Google TV General] w00cash:
So I have finally managed to boot into burn Mode. In my case all I needed to do was to use different source od worldcup driver. Once I did that everything went smoothly.

Unfortunatly, I have came across some problems along the way, and my device is now bricked. It is bootable into burn Mode, but it never passes dynalink logo. I want to flash factory rom using amlogic burning tool, but I cannot find any source of that. The only one l can find is available here

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

download.ods.ninja

But software doesnt accept it. Does any of you guys have working img file that I can use?. For wade of course

Thanks in advance
[Google TV General] bumerc:
The only difference to the newer revision was the procedure for adding the additional packages, kernel modules, etc. In the r43, I partly got it using git clone commands, or copied it by hand. When setting up the r61, I was lazy and fetched the packages via "breakfast beast". From now on, there was no more booting, with no ulterior motive that it might be caused by this exact step. Let me guess - you used .repo manifest or git commands for this purpose?

I will check again..

thx
[Google TV General] kennkanniff:
Can I use a BT remote from another box on a radxa zero?
[Google TV General] npjohnson:
Yes.
[Google TV General] AiM2LeaRn:
i was stuck where you are at in a soft bootloop and had to reflash lineage in the meanwhile to have a working box.

im trying to figure out how to go to stock 12 as well, the older methods dont seem to work with the latest Android 12 because they made it more difficult to unlock bootloader and i THINK they prevented "rollbacks" meaning i think we have to find a stock OEM Factory android 12 flashable image which i cant find anywhere.

Does anyone by any change have a "BURN" friendly flashable version of stock factory Andorid 12 for wade (dynalink)?
[Google TV General] w00cash:
So I have managed to get this thing working. I have wade with android 12 pre installed, and it is possible to install a10 form that source that I posted the other day. There is no Antirollback policy, from my observation.

To get this done you need to update all partitions that you find in that factory firmware zip using commands

update partition x <path to partition x>

For example

update partition dtb <path to dtb. Img>

Once you are done type

Update boot recovery

In my case that helped and I finally booted into recovery, where I could perform factory reset. That brought me to fully working androidtv 10 which could be easily update to atv12 using system update tool.

Hope this would help you too.

BTW

I do not recommend installing LOS because the official installation manual is piece of crap. The main reason for this is the fact that it is automatically generated, I think.

I am stuck at trying to boot into freshly flashed los recovery. Every command that I tried simply brings me back to squere one, which is soft brick, which I need to reverse in a way I described above.

From what I found online (reddit, here, etc) people have been experiencing this for over a year now, and there is no official workaround this in a LOS instsllation manual.

You buy this device and think that it would be piece of cake to flash it, but this is not 😒
[Google TV General] npjohnson:
Curious exactly what went wrong here - Android 12 is the intended starting point - so not really sure where the struggle came in?
[Google TV General] AiM2LeaRn:
the general insructions on the linage site are very outdated if you are coming from the LATEST android 12 wade firmware as they have made it harder to unlock bootloader and now have to do it with Update.exe.

once again same happened to me, including the no serial in fastboot. you have to use UPDATE.exe tool provided in "aml-flash-tool" and flash unoock the bootloader and flash the dtb dtbo... then unplug (unpower) device... then go back into burn mode and use the command to boot to fastboot (it will throw a error but ignore it, it goes into fastboot) open fastboot and check for devices it should show and now you can continue to flash custom recovery then boot to custom recovery and then install linage.

--- this took me about 10hrs of researching and pulling my hair out and reading to figure out. i put it all in this post :) ... Dont give up w00cash, you are over half way there it sounds like, if you can get your device to detect in device manager in burn mode then you are just about less than 15 mins away from having lineage installed. if you want better instructions let me know. i can post all the files needed and instructions if you want. its the weekend, i might not be back till Monday or Tuesday.
[Google TV General] w00cash:
Hey man,

Thanks for the input.

I'm not planning to flash LOS in nearest future, but your instructions would help others immensly.

Your post proves what I said earlier: official instructions are very inaccurate.

[+]

It seems that I was really close by myself. Thanks for instructions. Maybe I will give it a try sooner than I thought.

You are the Man!
[Google TV General] npjohnson:
I'll update the instructions.
[Google TV General] AiM2LeaRn:
if i have time i will try and find and link the files needed as they are scattered all over the linage19 and lineage20 theads.
[Google TV General] ji:
and an update on the not being able to use the google home app remote on wade, looks like theres something borked with the libs since keystore as a whole isn't returning certs right for other apps as well

https://vomitb.in/ysrTRPgRT9

and keymaster startup logs (looks normal)

https://vomitb.in/h6erFZVkMM
[Google TV General] AiM2LeaRn:
the old instructions do work however the problem is you are going to have some users on the older bootloader and some on the new. so its obviously going to be 2 different set of instructions.
[Google TV General] Functioner:
Which old and new bootloaders? Different versions of the 12 bootloader, or 10 vs 12?
[Google TV General] ji:
yeah ive noticed some different things about the 12 bootloader when ive updated from 10 stock - one main thing is that the side button no longer launches recovery so that you need to use adb reboot or burnmode to get in that way now
[Google TV General] npjohnson:
No, we're just going to require in the wiki that the users update to Android 12 first, not like we don't already flash the Android 12 bootloader would you flash the lineage zip.
[Google TV General] npjohnson:
That's not an Android 12 thing, the side button only launches recovery when the data pins are not live, if the date of pins are live it launches burn room, hence the kind of tomfooler you've seen users reporting where they half plug in a cable.
[Google TV General] AiM2LeaRn:
this is already creating confusion, it doesnt matter as the bootloader can still be unlocked regardless, the steps are just slightly different, what matters is if you want the latest version of linage 20 just make sure you are on the latest FACTORY OEM OS/FIrmware PRIOR to installing linage. then you can just follow the instructions i posted above.

@npjohnson btw, thanks for all your time and effort, this rom works great and actually reproduces better picture quality than stock (in my opinion, i like the saturation, vibrant colors). i am very impressed. Linage 20 is working alot better than the 19 i had tried a few months ago, THANKS for the continued development.
[Google TV General] Functioner:
Very sorry. Please excuse the interruption. I certainly didn't intend to stoke confusion. I was just trying to understand what you were saying. It matters to me, because, as in all endeavors in life, understanding is what I'm always after.
[Google TV General] AiM2LeaRn:
@updater14 The Google Setup Wizard and Setup Remote screen can be bypassed with the following:

*** BYPASSING THE GOOGLE SETUP WIZARD ANDROID TV / GOOGLE TV ***

WHILE STILL IN RECOVERY BEFORE 1st BOOT If you want to skip only the WiFi setup part but not the rest of initial setup, execute

######## METHOD 1 #######

adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop

WHILE STILL IN RECOVERY BEFORE 1st BOOT If you want to skip entire setup and directly go to home screen, launch Shell by executing

adb shell

and then execute the command

echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop

######## METHOD 2 #######

adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
[Google TV General] AiM2LeaRn:
i think you were asking for visual difference for others to know, i found a picture:

2021 Version has Button on the Side of Device

2023 version has Button next to the HDMI (same side as HDMI)

can also may be tell people prior to flashing to check model in ADB

"adb shel" command will also show 2021 as dopinder and 2023 as YOC

2021 model uses Amlogic S905Y2

2023 model uses Amlogic S905Y4
[Google TV General] npjohnson:
2021 isn't Sabrina haha that's the Chromecast, but the button info is perfect to help users identify.

I'll put it on the wiki.
[Google TV General] updater14:
Many thanks @All for your supporting and answering.

I'm giving up on the Banana Pi.

I bought a Raspberry Pi 4B, which is now available again in Germany.

I've used the Lineage image from KonstaKANG with GApps from Nikhil.

In a very short time, I was able to do what was not possible with the Banana.

My required apps are running, touchscreen is working fine and I'm ready to use.
[Google TV General] mmortal03:
If they keep

If they still have their packaging, the easiest way might be to just ask them if it says androidtv or Google TV on the top left. :)
[Google TV General] AiM2LeaRn:
i was up well past my bed time... i fixed, i meant to say dopinder... 2021 will say dopinder and 2023 YOC
[Google TV General] BTK19:
Google reportedly won’t sell anyone Android TV’s ADT-4 developer box

Google reportedly won't sell anyone Android TV's ADT-4 developer box

Developer hardware is important for any software platform, and Android TV has been failing here for a bit. After ADT-3...

9to5google.com
[Google TV General] npjohnson:
Correct, they won't, but they told us that the box is the AML reference box, so I bought one of those.
[Google TV General] w00cash:
So I have finally decided to go with it and try installing LOS by Your instructions. Everything went easily, exactly as you described. It took me about 15 minutes to complete.

Kudos to you, bro. Keep it up!
[Google TV General] billyrich:
Hi @npjohnson ,

In the lineage os wiki it says that wade must have android 12 stock before installing los 20.

I currently have lineageos 19.1 installed on wade.

So if I wanted to do a clean install of linegeos 20.0, (so not upgrade from 19.1 to 20), I have to first go back to the stock firmware and upgrade it to have android 12 and then proceed to install lineage os 20.

Right?
[Google TV General] npjohnson:
Nope we include the firmware so you're good to just install the build + gapps if you have them!
[Google TV General] ServError:
Hey @npjohnson , thanks for all your hard work. I'm one of those folks running the unofficial rom avoiding as much google integration as I can. Is there any way to use the remote programming feature from the unofficial build on the official one?
[Google TV General] npjohnson:
Remote programming? You mean the pairing wizard?
[Google TV General] ServError:
I don't believe so. In the unofficial build there was an option somewhere to configure the remote with the IR codes of your TV so that it could power up when off, change volume, etc without relying on HDMI CEC. I don't believe there's anything similar in the official build.
[Google TV General] npjohnson:
Uh.

I include nothing like that, if it's there it is in the official build.
[Google TV General] ServError:
Interesting, I wonder if the Google packages are providing it by identifying supported hardware. Thanks for clarifying.
[Google TV General] npjohnson:
Potentially, but if that's the case we can't include it on lineage sadly :/
[Google TV General] apropper:
Hi, I'm loving the project so far. I know this is still a work in progress, I wanted to provide some info about the hdmi cec option. So for my setup, I have to go into settings/system/inputs and toggle hdmi control, the first option, off then on again to control my soundbar, otherwise I'm just controlling the sound on the box itself. Something I've noticed is when there's an update available, after downloading and installing, this option works automatically without me having to do that toggle workaround. I still have to manually toggle it again when I turn the tv off then on again but hopefully this maybe gives you some sort of clue as to how to get it working.
[Google TV General] shakazoid:
Could you post a link to the aml-flash-tool with update.exe or kindly send me a pm to with a link to download from a personal cloud or box account to get it from. I have downloaded several for windows but none with a command line interface which i presume i will need to unbrick. I need to unbrick the original ONN androidTV TIA
[Google TV General] npjohnson:
utils/aml-flash-tool/tools/windows at master · khadas/utils

Utils/Tools for development. Contribute to khadas/utils development by creating an account on GitHub.

github.com
[Google TV General] Beyond-It:
Hey

I am currently trying to build the rom for GXL (a95xf1), but probably need a bit of guideance on how to get this to build without errors. Still new to this and trying to figure out the basics, so maybe just stupid questions.

- For the device/amlogic/common I have used https://github.com/G12-Development/device_amlogic_common, but not sure if this is the right one, since I use Kernel 4.9 (https://github.com/LineageOS/android_kernel_amlogic_linux-4.9-pie.git) and this only has a branch for 5.4?

- When building it also doesn't seem to create a recovery.img. Is this something I have to build firstly before using "make aml_upgrade", as it complaining about recovery.img is missing?
[Google TV General] 7thedevil7:
Hi guys, short question:

Every time I update (I have wade on the official build), I lose root and have to re-install magisk via the recovery.

I know not to expect support for third party add-ons, but I'm curious if anybody has an idea how one would be able to preserve root through updates?

Thanks for your help!
[Google TV General] w00cash:
I don't use magisk on android tv, but on my Phone I have the same problem. The only workaround this I heard of is this:

GitHub - programminghoch10/Lygisk: Your Lie in Android

Your Lie in Android. Contribute to programminghoch10/Lygisk development by creating an account on GitHub.

github.com

I have never used it on my own, but from the description it seems that it might be the thing you are looking for.
[Google TV General] npjohnson:
Realistically the easiest way would be to `breakfast beast` to pull all the dependencies. Then put your device tree in and have it inherit gx-common and use your target to build.

Not sure what you're looking at but 4.9-pie _only has_ a 4.9 branch haha.

Known magisk issue, has been reported long ago.
[Google TV General] Beyond-It:
Seems like a bit more research helped on both of my previous questions.

Had to use this one instead https://github.com/LineageOS/android_device_amlogic_common, which also helped with generating the missing recovery.img

But maybe I should try with 'breakfast beast' instead to be sure I have all dependencies.

Now it makes the aml_upgrade_package.img and everything seems happy.

But can't seem to be able to flash it to my A95XF1. Gives me following error about dtbo.

[0x30402004]UBOOT/Partition dtbo/Initialize partition/Error result

Is there something additional that has to be changed to be able to flash it or?