yashsingh1/xdaforums huggingface dataset:
[Google TV General] BTK19:
HDMI CEC volume is broken on wade official and unofficial latest version's it controls the box's volume only. Clean flash on both versions
[Google TV General] Max-E-Moose:
+1

Noticed this a couple of weeks ago. Wanted to investigate but haven't found the time.
[Google TV General] Scott Lai:
Where to get/download amlogic command line update utility?
[Google TV General] npjohnson:
Khadas utils repo on github
[Google TV General] Imonobor:
I hit my head against the wall for 2 hours straight before I was able to pair my remote with my Dynalink (wade). For anyone with the same problem, press and hold OK (the round button) and Volume minus. I had to search the manual to find that out.

Anyway, now I'm stuck on the next leg of the journey - connecting to the WiFi. It will connect to a network, but it will be stuck on "Please Wait" and then would time out with "Wifi cannot reach internet - Check your connection and try again". I've tried both my home wifi and a mobile hotspot, restarted both TV box and router, same story. Any help would be greatly appreciated!

I really hate the gapps setup process, you have no access to the settings to troubleshoot these things, and trivial things like wifi connections can't be skipped. Why?
[Google TV General] Big Dumb Object:
On my dopinder with GApps built-in, this is what I did. At first launch, I proceeded through the first two steps, pairing the remote and connecting to WiFi, then, to skip Google sign-in, executed

adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
adb shell settings put global setup_wizard_has_run 1
adb reboot

and soon ended up right on the home screen.
[Google TV General] Imonobor:
Thanks for the help, but now nothing google-related works at all, which kinda defeats the purpose of installing the gapps version, you could just get the official one without gapps.

It seems something is blocking gapps from connecting to the internet, because other apps have internet connection.

It used to work with the official LOS20 ROM + separately flashed mind the gapps on the same device and same network. Why wouldn't it work on the unofficial one with the built-in gapps?

Any ideas, anyone?
[Google TV General] CrysisLTU:
Flashed LOS, and unfortunately the remote IR setup did not survive the trip :( I guess the IR codes get wiped when pairing the remote.

One thing I noticed while on LOS - video content has a weird pastel-like blurry filter applied. I noticed this on SmartTube and Stremio, though on SmartTube by applying some dev options related to Amlogic, the filter went away.

I'm using a 1080p TV.

Has anyone observed this?
[Google TV General] Imonobor:
Solved it by flashing the official ROM with separate mind the gapps package. At first it bugged out "Due to insufficient space on /system partition", but after wiping system it installed without problems, everything is working as it should.

Is there a difference between using official+gapps, and this unofficial rom?
[Google TV General] hellerhd:
Hello,

I experience the following issue (wade, official LOS20 ROM, mindthegapps ATV, original or projectivy launcher):

Some apps are installed in their mobile version instead of their TV-version. with ATV launcher these apps are not even visible, projectivy launcher shows them as mobile apps.

I did not experience this with the original Dynalink ROM or with a xiaomi stick and its original ATV ROM. What am I doing wrong? Or is this a bug?

Thanks for any help or hint into the right direction :-)
[Google TV General] Big Dumb Object:
You should examine whether your GApps can survive OTA update or not. These builds have a flaw that prevents addon.d scripts from running correctly in certain scenarios.
[Google TV General] npjohnson:
For ATV builds? Just a few extra Google apps you can download.

And bootloader lock status spoofing.
[Google TV General] npjohnson:
No?

Official builds stuff persists fine.

It's Unofficials where they don't.
[Google TV General] npjohnson:
Appreciate it, we know the issue but we can't fix it without messing up the userspace atm.
[Google TV General] Endex:
Hi i'm new here to XDA, I was wondering where i could get help with my dopinder being stuck on lineage recovery and having no ADB or fastboot response even though i have it enabled. Basically its not recognized by my PC.

Thanks!
[Google TV General] npjohnson:
Try a different cable/USB port/computer - these devices can be finicky.
[Google TV General] Endex:
Thanks for the quick response, i've tried different usb ports and different cables, maybe my cables are all ruined or something. I'll try my other PC, hopefully i can save it.
[Google TV General] Endex:
Ok, i was able to get it working through a different power source and an otg adapter. I got a usb stick and put the recovery .zip on there and applied the update through USB. Thanks for the help tho, godspeed.
[Google TV General] dysoct:
Hi... I'm interested in trying this out. But would like to confirm few items first... is Adaptive HDR and AFR available and working on it? Thanks in advanced
[Google TV General] npjohnson:
What device?
[Google TV General] dysoct:
Sorry...missed out on that... wade
[Google TV General] fepij52921:
Trying this on Wade, from a linux device.

I get stock on this command:

fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock

Output from console:

OKAY [ 0.022s]

Finished. Total time: 0.022s

< waiting for any device >

The devices gets stock on the Branded Dynalink screen, I have to start it by unplugging it and plugging it back, after rebooting the device loads all data it previously had, so I assume it wasn´t boot-locked
[Google TV General] otttvbox502:
When updating Wade if using gapps. Had to add sideload update and then sideload gapps.

I guess no persistent gapps?

If you try update from update area.

Boots once with flashing output, then restart will not boot past lineage screen.
[Google TV General] npjohnson:
sounds like a bad download of the update?
[Google TV General] LITUATUI:
SC2 (S905X4) and S4 (S905W2 and S905Y4) use Kernel 5.4 and aren't listed as supported yet.
[Google TV General] LesterDMolester:
Okay thanks, but will they ever be supported?
[Google TV General] LITUATUI:
Maybe. You need to ask the developer.
[Google TV General] npjohnson:
Not by these trees - these SoC's aren't g12*, sm1, or gxm/l - maybe in the future once the ADT-4 drops!
[Google TV General] 7thedevil7:
After the latest official update my wade is stuck in a bootloop. How do I get more information about what went wrong?
[Google TV General] dysoct:
So I just tested this out myself. Everything is working well except HDR is Always ON (even at home screen). Is it supposed to be like this? I tried to find the toggle but couldn't find it. Is there any way to enable Adaptive HDR? Playing SDR contents from plex changes it but returning to the home screen switches it back to HDR.
[Google TV General] npjohnson:
It's a GApps issue - please redownload and re-flash gapps.
[Google TV General] 7thedevil7:
Yup, this was the issue. Thanks, my wade is working now again!

Any idea why the update also deactivated Magisk? Or was this because of re-flashing the GApps?
[Google TV General] npjohnson:
Backup tool was broken. it is fixed now.
[Google TV General] Big Dumb Object:
Is it an "architectural issue" that is caused by the "way lineage does space reservations"? From these words, I concluded that the problem affects any Amlogic device with a limited free space in /system.

Anyway, I already got my Radxa Zero 4/16GB and only waiting for the necessary accessories to be delivered from China to get it into action.
[Google TV General] npjohnson:
No, it's space reservation related.

Architectural _to the way I do unofficials_.

Space reservations are guarded and calculated so that when not WITH_GMS, the amount of space GMS takes is reserved on each partition.

Therefore when you set WITH_GMS and include GApps no space is reserved.

On 21 we have recalculated the values and redone how it is guarded so that a few MB are reserved regardless of WITH_GMS which will fix my unofficials issue with addon.d

If addon.d didn't work on officials, a device wouldn't ship.
[Google TV General] Imonobor:
I see. Would the bootloader thing cause any problems? Which apps detect it and are affected by an unlocked bootloader?

On an unrelated note, has anyone been able to get any form of Miracast working on this device? (Dynalink 4k TV box / wade)
[Google TV General] npjohnson:
Makes some banking apps work.

And no, it isn't supported as a receiver
[Google TV General] niuxxd:
My Dynalink Android TV box, running Lineage OS 20, initially connects only to a 2.5GHz Wi-Fi network upon booting up.

However, after executing the command ip l s wlan1 up, turning the Wi-Fi off and on enables the connection to a 5GHz network.

Surprisingly, despite this, the IP address is still assigned to wlan0, which appears unusual to me.

How can I configure the TV box to automatically enable and connect to a 5GHz Wi-Fi network by default?
[Google TV General] niuxxd:
When I power off my device, the Wi-Fi automatically turns off as well. I'm trying to figure out how to keep the Wi-Fi active even after using the remote to power off. I believe this is akin to executing input keyevent keyevent_power. Despite my research suggesting that setting ro.vendor.platform.wifi.suspend=false might help achieve this, unfortunately, it hasn't worked for me.
[Google TV General] darkvoid:
@npjohnson,

Has the team been able to make any progress on the Onn.tv 4K 2023 (Yoc) devices?
[Google TV General] npjohnson:
I distributed the two boxes that were given to me to Ivan, one of the forum moderators here and a developer on exynos devices, and to an omni-ROM developer that works on the needs as well.

I haven't heard anything back from them yet
[Google TV General] Tom_Neverwinter:
request to split the 2021 unofficial build and the 2023 build on the first page as it may confuse new users or people who do not know there are two builds of the device now. [add wiki information for the 2023 version]

Walmart onn 4K Box (2021)​

Walmart onn 4K Box (2023)​
[Google TV General] npjohnson:
the ODS wiki already splits it.

There is no wiki page for 2023 as there are no builds.

Will fix XDA OP.
[Google TV General] Tom_Neverwinter:
Thank you.
[Google TV General] npjohnson:
Done. Thx.
[Google TV General] hellerhd:
Hi,

Further trials suggest that there is an issue with the the correct device model in the LOS image: Spoofing the model Spoofing an android TV device via Aurora Store downloaded and installed the correct ATV versions of the apps! => Updates via play store installed the mobile versions again...

Any help from the developers possible?

Thanks again.
[Google TV General] npjohnson:
spoofing _what device_ allows that? Doesn't make sense.
[Google TV General] apropper:
Hi, as of update 20240104, hdmi cec is still broken on wade. Was no one from the team able to figure out what went wrong on 20231123?
[Google TV General] BTK19:
Its broken on wade and dopinder still
[Google TV General] bumerc:
@npjohnson

I'm trying to port the Bluetooth for my gxm board (qca9377 chip), for this I used libbt-vendor from this repository. Now there seems to be a problem with the bluetooth HAL, maybe you have an idea? Unfortunately, I don't have sufficient knowledge in this area :confused:

Logs:

libbt_vendor_log

qca_bt_log

lshal_output
[Google TV General] undroid23:
Hi, I also encounter Abort message: 'incStrongRequireStrong() called on 0xebc01050 which isn't already owned'

I'm following this commit but aside from the changes on the gx.mk that I copied on the g12.mk, I didn't understand how to apply this, should I run the extract-files.sh?

gx-common: Use libutils from VNDK32 for systemcontrol, audio and hdmi · LineageOS/android_device_amlogic_gx-common@adc08c2

* For audio.primary.amlogic.so, systemcontrol, hdmicecd * Abort message: 'incStrongRequireStrong() called on 0x7586a3a1c0 which isn't already owned' Change-Id: Ibca93bc356b81e205c77df5...

github.com

I am using a g12 device
[Google TV General] npjohnson:
What HAL has that abort message?
[Google TV General] npjohnson:
which g12 device are you using?
[Google TV General] npjohnson:
and wait, quessssstion - what vendor repo are you using? It realllllllly looks like you're on the 19.1 branch using vendor/amlogic, and not using the 20 branch (which moved to vendor_amlogic_g12-common) - is that suspicion correct?
[Google TV General] undroid23:
For the device files I am already using https://github.com/LineageOS/android_device_amlogic_g12-common lineage20 branch. For the vendor files, I got it from https://github.com/TheMuppets/proprietary_vendor_amlogic as I can't find it on the lineage github. Can you share a link to the correct repo? Thanks.
[Google TV General] npjohnson:
heheheh yeah that's why you're having pain alright.

Using the right repo will solve your issues.

For lineageos 20, each device tree now gets its own vendor repo to avoid size limits.

GitHub - TheMuppets/proprietary_vendor_amlogic_g12-common

Contribute to TheMuppets/proprietary_vendor_amlogic_g12-common development by creating an account on GitHub.

github.com

https://github.com/TheMuppets/proprietary_vendor_amlogic_deadpool

GitHub - TheMuppets/proprietary_vendor_amlogic_gx-common

Contribute to TheMuppets/proprietary_vendor_amlogic_gx-common development by creating an account on GitHub.

github.com

etc etc.

I think you just need g12-common + your device.

When you have this device fully up, if you'd like to submit it for official builds reach out to devrel(at)lineageos.org via email!
[Google TV General] undroid23:
Thank you, that fixed the incStrongRequireStrong() error. Although I got a new error no suitable EGLConfig found, do you happen to know the repo for Amlogic GLES libraries?

My GPU device is:

GPU identified as 0x2 arch 7.2.1 r0p0 status 0
[Google TV General] npjohnson:
That's not the issue you think it is, are you building 20 or 21? That error sounds like you might be building 21?
[Google TV General] undroid23:
I am building lineageOS20
[Google TV General] npjohnson:
Weird, full logcat?

And which soc is your device?
[Google TV General] undroid23:
This is amlogic s922.

Additional info, I am using kernel 4.9 from

GitHub - voodik/android_kernel_voodik_odroidg12 at lineage-20.0_odroidg12_t_64_r44

Contribute to voodik/android_kernel_voodik_odroidg12 development by creating an account on GitHub.

github.com

but my kernel config is still using g12a_defconfig.
[Google TV General] npjohnson:
If you aren't using our kernel that is probably your issue, port what you need from that guys over to ours, really you should just need to import the DTS and maybe add a variant defconfig.

Our kernel needs to match the blobs as we use the newest blobs out there for these SoC's.

Should be easy.
[Google TV General] npjohnson:
Good news for devkits users:

Y'all hit 3 big issues:

- Pairing animation is not skippable

- Skipping wifi connection to skip google account setup on ATV

- m5: USB keyboards

- m5: Can't get out of recovery

Good news, builds after today will have the first two fixed, and we have good leads on the last 2.
[Google TV General] bumerc:
@npjohnson

Hi

I managed to get the qca9377 Bluetooth and WiFi working on LOS-19.1, both working well so far.

The problem with the QCA Bluetooth on LOS-20.0 is related to Google's removal of the hci_layer modules etc.. from the Flouride Bluetooth stack. For this reason, using the bundle libbt-vendor + android.hardware.bluetoith@1.0-impl currently experiencing a bt-stack crash. I have not yet tested whether another solution might be possible here, for example as solved with the android.hardware.bluetoith@1.0.vendor on the g12a/b platform. Could you recommend anything here? Thx
[Google TV General] hellerhd:
Hello,

Thank you very much for your reaction, sorry for my late answer (little child keeps me very busy) and my less than perfect description, I am a kind of advanced novice ;-).

I try to elaborate:

System: Dynalink TV box, original Lineage wade OS, Mind the gapps ATV version.

When installing apps via google play store, some apps are installed as mobile versions, see screenshot 1)

When installing via Aurora Store and "spoofing an ATV device" (they call it this in the app, screenshot 2), these apps are installed as correct ATV versions (screenshot 3).

Updates via Google play store override this and the apps are in mobile version again (screenshot 4) and so unusable on an ATV (screenshot 5).

Any hints, help, etc? Where is the problem located? Lineage OS, Mind the Gapps? the user? My fault in doing something wrong?

(I had no issues of this kind with the original Dynalink ROM)

Thanks again!!!
[Google TV General] undroid23:
Hello,

On my lineageos20 for g12b devices, I get this error on my logcat where android.hardware.bluetooth@1.0.so is not found. I think it's because that library only exists on /system/lib and not on /vendor/lib. What should I modify so that it will be included on /vendor/lib?or how can I disable/ remove android.hardware.bluetooth@1.0-service-droidlogic from being called?

Thanks for your responses. I'm reading on AIDL and HIDL but it still is confusing.

--------- beginning of crash

01-01 00:00:14.546 3110 3110 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.bluetooth@1.0-service-droidlogic": library "android.hardware.bluetooth@1.0.so" not found: needed by main executable

01-01 00:00:14.562 2925 2925 I hwservicemanager: getTransport: Cannot find entry android.hardware.audio@7.1::IDevicesFactory/default in either framework or device VINTF manifest.

01-01 00:00:14.568 3109 3109 E LegacySupport: Could not get passthrough implementation for android.hardware.audio@7.1::IDevicesFactory/default.

01-01 00:00:14.569 2925 2925 I hwservicemanager: getTransport: Cannot find entry android.hardware.audio@7.0::IDevicesFactory/default in either framework or device VINTF manifest.

01-01 00:00:14.569 3109 3109 E LegacySupport: Could not get passthrough implementation for android.hardware.audio@7.0::IDevicesFactory/default.

01-01 00:00:14.569 2925 2925 I hwservicemanager: getTransport: Cannot find entry android.hardware.audio@6.0::IDevicesFactory/default in either framework or device VINTF manifest.

01-01 00:00:14.571 3109 3109 E LegacySupport: Could not get passthrough implementation for android.hardware.audio@6.0::IDevicesFactory/default.

01-01 00:00:14.592 3127 3127 I HidlServiceManagement: Registered android.hardware.gatekeeper@1.0::IGatekeeper/default

01-01 00:00:14.592 3127 3127 I HidlServiceManagement: Removing namespace from process name android.hardware.gatekeeper@1.0-service.software to gatekeeper@1.0-service.software.

01-01 00:00:14.620 3117 3117 W android.hardware.configstore@1.1-service: Could not find seccomp policy file at: /vendor/etc/seccomp_policy/configstore@1.1.policy
[Google TV General] npjohnson:
```

ifneq ($(BOARD_HAVE_BLUETOOTH),false)

PRODUCT_PACKAGES += \

android.hardware.bluetooth@1.0.vendor

endif``` is in g12.mk, do you have bluetooth or not?
[Google TV General] npjohnson:
I actually just went ahead and fixed hits or you - sync and it should be fine.
[Google TV General] npjohnson:
Those are harmless.
[Google TV General] ChriMo:
Still same situation. Regarding YT-Review I found only this Chinese one with no subtitles or translation to English:

Is there yet an English Review?
[Google TV General] npjohnson:
Official builds for dopinder with full hardware OMX start on Wednesday!!!!
[Google TV General] Big Dumb Object:
HOW? 😲
[Google TV General] npjohnson:
Android 12 for dopinder came out, like u previously said, those libraries alone fixed it.
[Google TV General] npjohnson:
What's funny, another thing came up and I may now be able to support Sabrina officially as well. We will see.
[Google TV General] Big Dumb Object:
It would be great if the recent apps menu could also self-fix on all devices, but that's not the case, right?
[Google TV General] npjohnson:
we're working on it.
[Google TV General] CrystalCommunication:
Hello, I just updated to the Feb 1 build on wade and it is very broken. The "androidtv" splash that appears before the LineageOS boot animation is now a terrifying mess of broken glitchy pixels, and WiFi doesn't work at all anymore.

This isn't new, but I've also never been able to get Bluetooth working on this box. The remote kinda works over IR, but it's really annoying and finnecky. Is there something I'm missing to get it to pair up properly? I actually managed to get the remote to pair after downgrading to the Jan 25 build to fix the issues mentioned above. The trick was to put the remote into pairing mode by holding Select and Vol- at the same time before going to the pairing screen.
[Google TV General] npjohnson:
Try installing stock, something sounds funny.

We haven't merged anything relevant to this device since like mid January.
[Google TV General] CrystalCommunication:
That's weird, because all I did to fix the aforementioned problems is reboot to recovery and sideload the January 25 build. Do you suppose it's possible that the problems could have been caused by a flipped bit during the upgrade process?
[Google TV General] npjohnson:
mayyyybe? That's strange though. Maybe gapps didn't persist for some reason?
[Google TV General] CrystalCommunication:
That also doesn't make sense because it did persist when I downgraded. Or at least I think it did, I didn't go out of my way to flash it again or wipe data and I didn't get any messages about GMS crashing afterwards.
[Google TV General] wyldwilly:
Just flashed lineage-20.0-20240207-nightly-dopinder-signed.zip and I can't get it to boot: the boot animation is working but the device never progresses to the initial setup. I waited for 15 mins, forced device into recovery, performed Format data / factory reset, but this did not help.
[Google TV General] npjohnson:
It seems that some users aren't starting on 12 firmware, wiki dictates it - you need to start on 12 bootloader.

You can grab this (View raw) and fastboot flash bootloader bootloader.img.

Then format user data and it should boot right up.
[Google TV General] wyldwilly:
I get the following error when I try that: FAILED (remote: 'locked device')

BTW, I did follow the wiki and ensured that I had upgraded to the 12 firmware...
[Google TV General] npjohnson:
Hahahaha.

Locked device, did you unlock your bootloader?

Sounds like you didn't. Try re-unlocking.
[Google TV General] wyldwilly:
I get the same error when I try the unlock commands.

I followed the wiki and didn't encounter any errors, except the expected one for GApps signature, so shouldn't it be unlocked from that?

I was also careful to split the following into 3 separate commands, since the chained commands usually fail for me: fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock
[Google TV General] npjohnson:
fastboot getvar unlocked

Please
[Google TV General] wyldwilly:
Here ya go!

C:\tools\android\adb>fastboot getvar unlocked

unlocked: no

Finished. Total time: 0.063s
[Google TV General] npjohnson:
Yeah, your bootloader for some reason or another is not unlocked.

You need to unlock it then flash the 12 bootloader I mentioned.
[Google TV General] wyldwilly:
Oh, I did use the following (per your previous suggestion) to restore this device back to factory: dopinder-qt.20210519-factory.zip

Device was working great with the retail OS, but now I'm wondering if I've somehow "borked the innards" by flashing too much lol
[Google TV General] wyldwilly:
lolololol
[Google TV General] wyldwilly:
I'll try taking it back to retail then. If that fails, then I assume this is yet another turd/blue smoke situation lol
[Google TV General] npjohnson:
No, nothing borked. Just need to unlock on 10, flash the new bootloader, then flash lineage.
[Google TV General] CrysisLTU:
There is some discussion here that talks about how bootloader unlocking is unavailable on Android 12 dopinder, with possible work arounds: https://xdaforums.com/t/walmart-onn-android-tv.4313411/post-89308477
[Google TV General] npjohnson:
You can always just use burn mode to unlock. I can update the instructions to do that tbh. It's a more reliable bet.