yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] ijuanp03:
I am using my very old Galaxy Watch Active (yes, 1st gen) on my X30 Pro without any issue.

I have setup Samsung Pay as well and it works like a charm.

Notifications are working as well.

------

On a side note, Galaxy Buds Live is not working properly - I can't enable ANC just because of the bug where I can't enable Samsung Buds Plugin under device app & notification since that specific Samsung Plugin is missing.

I know it's NOT the X30 Pro CN ROM's fault but Samsung's. Why? Because I have my official Europe Motorola RAZR 5G and has the same issue.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] sentines:
Anyone try convert Moto x40 to moto edge 40 pro?
[General Questions and Answers] Privacydroid:
I tried installing a "virtual android phone/system" in virtualbox, for that i used blissos - https://blissos.org/

When performing the installation it always ends with the same error, i'm doing the same steps as people on youtube but for them it works..

Any help is welcome... or if you know other virtual android os'es please share them, but not things like androidprojectx86 because this one is full of google spyware.

See the error:

View attachment 5795855
[General Questions and Answers] James_Watson:
BlueStacks?
[General Questions and Answers] Privacydroid:
Seriously? i tried with 16 GB with 32 GB and 64 GB, none worked.
[General Questions and Answers] Privacydroid:
Yeah no thanks not installing that stupid spyware.
[General Questions and Answers] Privacydroid:
You can see the screenshot in my first post, that's where it fails.

I tried again right now. Used blissos 11 and followed instructions, same error.

very wired, worked now... used the stable version instead of new gpu/cpu version.. 2gb ram 16gm system.
[Google TV General] enfermo:
Thx for your time

Thx to ALL in the team
[Google TV General] instylz:
Very excited for this! Kudos to the devteam!
[Google TV General] talksickisil:
Thanks for the work you’re putting in on this. I’m going to go ahead and wait to hear what other users are thinking of this what’s good and where’s the bugs before flashing. I just don’t feel like re installing magisk and all that right now. But… I do have a 4 day weekend so… I’m probably just in denial 🤣I’m sure I’ll end up setting this up. Happy new years everyone. Let the record show we have lineage 20 android 13 on our budget boxes BEFORE 2023. Amazing.
[Google TV General] ascii79:
I tried upgrading from official 19 to 20(lineage-20.0-20221220-UNOFFICIAL-wade). Upgrade was successful. But Netflix app errors everytime it runs. Prime video was fine.

My device is wade. Sorry i wouldn't be more verbose since i have downgraded.
[Google TV General] talksickisil:
I could be wrong, but I believe the reason the build is an unofficial build is with broken widevine L1 . That is a DRM that netflix requires for their app to run correctly. I know this was what held up official builds on 19.1 for some devices.
[Google TV General] npjohnson:
Nope not on wade - L1 should work fine - I think it's _just_ Netflix because Prime Video works.
[Google TV General] talksickisil:
Interesting. Well I’m a pirate anyways 😂 🏴‍☠️… The only “official” app I use is directv stream with a friends log in from my home state. (Which keeps me able to watch all my home town nfl nba mlb games) anyways…I am going to go ahead and install this today and I’ll report back after installed.
[Google TV General] talksickisil:
All I have to say is WOW was that quick and easy. I didn’t even need to turn on my laptop. Upgrading is a breeze. I used root toolbox (I think it’s called) to flash the recovery .img without even exiting the android session. Then after rebooting recovery from that same app I verified the date it shows and confirmed it flash successfully. Then I just flashed the .zip from my usb flash drive for EXternal storage attached to OTG. I was going to wipe everything and start fresh. For whatever reason, the recovery decided to reboot after I didn’t hit any buttons for awhile. To my surprise everything migrated from 12 to 13 flawlessly with exception of magisk. I did not even have issues with my INternal storage usb drive. It’s installed but I will need to re-patch the boot img. If I do have any issues I will keep this dirty flash in mind. Thanks as always for your work. I like the file manager you added. Nice touch. Also I notice this build using about 300 mb larger than the average official highly build. Did you include more g apps or something? With this dirty flashed I won’t be able to tell anything I already had installed. Oh and also: the signature verification warning in recovery is no more. That’s excellent also.

View attachment 5797999View attachment 5798001
[Google TV General] DiogoSilva48:
Hi. Which GXL devices will be supported?
[Google TV General] npjohnson:
beast (ADT-2) is s905x

hertz (devkit) is s922x

More welcome if we get more people interested!
[Google TV General] 01520717:
I tried this build on my dopinder box and it went flawlessly. It was much simpler than the 19.1 build.

I see encrypted content still isn't playing. I did some investigation into the problem and I see something that looks like it could be causing the problem.

In logcat, I see the following:

E/OMXNodeInstance: setParameter(0xeaec3e14:amlogic.avc.decoder.awesome2.secure, OMX.google.android.index.storeMetaDataInBuffers(0x7f000002): Input:0 en=0 type=1) ERROR: BadPortIndex(0x8000101b)

That 0x8000101b error is usually caused by a bad codec, which suggests amlogic.avc.decoder.awesome.secure probably isn't compatible with the S905X2 SoC. Was it compiled for the S905Y2 and maybe that build doesn't work with the S905X2 in dopinder/sabrina?

Thanks to everyone that created this build.

Edit: I thought wade had a S905Y2 but it has the S905X2 so I guess it isn't the SoC model causing the error.
[Google TV General] wyldwilly:
I got this up and running on Dopinder. I did have to manually reboot into recovery using the side button, but otherwise the install was easier than my experience with the 19.1 build. Like the previous post, the important apps, like Netflix/Prime, are still broken. Thanks for your continued hard work!
[Google TV General] BigEmpty:
I thought Walmart, Dynalink, ADT-3 all have Y2 but google have D3. The wiki says different so I don't know what's correct.
[Google TV General] talksickisil:
I wish had some type of criticism but there has not been any new issues for me specifically since updating. So I will just reiterate thank you for bringing this forward. I know it’s not part of the rom or supported but magisk is playing very nicely with either build. And even the stock rom. It’s nice having these options!
[Google TV General] ji:
ROM works great on wade! One issue I am having is selinux errors for netflix which is triggering a compat error and DRM errors for Hulu, logs are below:

hulu: https://pastebin.com/uX6eTQEK

netflix:

12-30 16:21:11.340 7302 7302 W DefaultDispatch: type=1400 audit(0.0:78): avc: denied { read } for name="u:object_r:vendor_netflix_prop:s0" dev="tmpfs" ino=3556 scontext=u:r:untrusted_app_30:s0:c103,c256,c512,c768 tcontext=u:object_r:vendor_netflix_prop:s0 tclass=file permissive=0 app=com.netflix.ninja
12-30 16:21:11.148 7302 7302 W DefaultDispatch: type=1400 audit(0.0:77): avc: denied { read } for name="u:object_r:vendor_netflix_prop:s0" dev="tmpfs" ino=3556 scontext=u:r:untrusted_app_30:s0:c103,c256,c512,c768 tcontext=u:object_r:vendor_netflix_prop:s0 tclass=file permissive=0 app=com.netflix.ninja
[Google TV General] npjohnson:
Thanks for reporting this! Easy fix. Will be in next build.
[Google TV General] matrix200200:
What is the upgrade procedure for those coming from 19.1 ?

Also, are there still issues with wifi, I am having on 19.1?

1. Wifi disconnecting after long periods of inactivitiy.

2. Wifi config in settings missing static ip setup.
[Google TV General] wyldwilly:
I'm still having the WiFi weirdness post-upgrade... :-(

I upgraded to these:

lineage-20.0-20221220-UNOFFICIAL-dopinder.zip

lineage-20.0-20221219-recovery-dopinder.img

I followed the wiki, which is written for people coming from a retail device, even though I was upgrading from 19.1. Since the build automagically upgrades the recovery, I'm guessing it would be simpler just to boot into the 19.1 recovery and flash the ...dopinder.zip - I think manually flashing the latest recovery is unnecessary?

I would also appreciate knowing what the correct upgrade procedures are...I often feel like I'm guessing lol
[Google TV General] npjohnson:
just flash the 20 zip from recovery - that's all you need to do.
[Google TV General] dorkshoei:
I'm totally confused at this point.

There are a set of install instructions here: https://wiki.oddsolutions.us/devices/radxa0/install

And another (significantly different set) here: https://wiki.radxa.com/Zero/install/eMMC_Android which talks about "extracting .... bootloader.img ... needed later" to run Zero in fastboot mode.

The former, to me, is it's own ecosystem (totally independent of what I built) so I'm surprised it's failing to flash.

It's quite possible I should be ignoring the oddsolutions/install page. I tried it because the build instructions (from the first post in this thread - https://wiki.oddsolutions.us/devices/radxa0/build) ends with "1. recovery.img 2. lineage-20.0-20230410-UNOFFICIAL-radxa0.zip" without detailing how to install them onto a new device.

Right now 'adb devices' fails to find my device regardless of whether USB_BOOT is pressed.
[Google TV General] J_Woo:
Tried this and haven't gotten past this screen. I can flash images, get into recovery mode and so I know the flash is actually fine. Just stuck on this image even when I clear cache and do factory reset. Perplexing.
[Google TV General] npjohnson:
are you trying to build 20 right now? There'd be the issue if so, as stated in the OP, radxa and other dev kits aren't supported on 20 or 19.1

and why would adb see your device in AML burn mode? They're not compatible whatsoever... adb is for android/recovery interaction only.

All you need to do, and I can't reiterate this enough:

Sync 18.1

Sync vendor/amlogic from TheMuppets

breakfast radxa0 (it will pull the dependencies)

For good measure I'd add androidboot.selinux=permissive to the cmdline in BoardConfig.mk of device/amlogic/g12-common - but it shouldn't be needed.

Then `mka bacon aml_upgrade` - then just flash the aml_upgrade image provided like the instructions detail, then follow the rest the instructions but plugging in files from your build.
[Google TV General] dorkshoei:
Knowing of course about the requirement of git-lfs !

I'd already built the image successfully.

I assumed I could therefore just run 'mka bacon aml_upgrade' in the android directory but that of course failed with "error: vendor/lineage/build/soong/Android.bp:24:8: module "generated_kernel_includes": cmd: unknown variable'$(PATH_OVERRIDE_SOONG)'"

Rerunning breakfast radxa0 again and then re-running 'mka bacon ...' seems to work.

My point? None of this is anywhere near as obvious to a newcomer as you think it is!!

I guess a lot depends on your end-goal. I just wanted a pre-built image so I could use a radxa0/15.6" touchscreen as a PDF reading appliance for reading technical papers. I had been using a pre-built image on a rPi4 but I'd borrowed the rPi4 from another task and of course they are unobtanium so I bought a radxa0.
[Google TV General] npjohnson:
You built the image - was that image 20 or 18.1?

20 won't work - it won't boot, it won't flash.

you need to breakfast before making the target, which I literally laid out above, you did it backwards. I told you to breakfast then aka aml_upgrade bacon, which will build both targets you need.
[Google TV General] dorkshoei:
I just did what you said in post #111, I followed https://wiki.oddsolutions.us/devices/radxa0/build replacing 20.0 with 18.1

Of course that fell over because there is no mention of git-lfs.

After a few failures (and your help) I got 18.1 built.

But then how to install it.

None of this is as clear as you seem to think it is.
[Google TV General] npjohnson:
I don't think it's clear - I get it's scattered because we haven't gotten these devices to boot in 3 versions.

LFS is a "they did this last week" thing - so I haven't been able to update my wiki.

But I've helped a few people get radxa booting 18.1 so far, and they didn't have any issues with breakfast and the instructions I gave them worked.

Regardless of the useless back and forth here - the instructions I posted a few posts back will get you booting.
[Google TV General] dorkshoei:
So does `mka bacon aml_upgrade` encompass 'brunch radxa0'?

I'd already successfully built 18.1 using 'brunch radxa0' from the build instructions. $OUT contained the built recovery.img and the zip.

When I went to run 'mka bacon aml_upgrade` in the build tree it failed with 'unknown variable'$(PATH_OVERRIDE_SOONG)'"

Googling I found I might need to re-run breakfast.

So I reran 'breakfast radxa0' && `mka bacon aml_upgrade` and it's now into a long build.

I understand I'm hopefully going to end up with an "<aml_upgrade_image.img>" (as discussed in https://wiki.oddsolutions.us/devices/radxa0/install) but I'm confused about your "both targets you need" comment.
[Google TV General] npjohnson:
`aml_upgrade` and `bacon` are targets you are making.

Brunch just runs breakfast $device, then runs mka bacon.

radxa needs to build an additional target so it won't work.
[Google TV General] dorkshoei:
Ah, ok, mka is a "faster make' although from the description here I'm unsure how it's different from make -j

http://www.trcompu.com/MySmartPhone/AndroidKitchen/Breakfast-Brunch-Lunch.html

Maybe I could have just run 'mka aml_upgrade' since I'd already built the main images (and saved them).

I'm not totally grokking the "needs to build an additional target" but maybe it doesn't matter and I'll just let it finish :)

So when I'm done with this, I'm using 'aml_flash_tool.sh' per https://wiki.oddsolutions.us/devices/radxa0/install
[Google TV General] ji:
Im sorry I totally misled you there! Not sure how considering I *just* went through the same setup as you on my wade yesterday. ACTUAL button combo is OK + Vol - per https://dynalink.life/pages/howtouse
[Google TV General] npjohnson:
Yup! Make sure to try diff cables and ports if it looks up.

And while you can build the upgrade image alone, unless you build the upgrade image and bacon at the same time, when you flash the older bacon build over the newer upgrade image you might cause some issues. Depending on what day you built bacon and what was merged at that time
[Google TV General] dorkshoei:
Same error.

[100% 1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja

FAILED: out/soong/build.ninja

out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp

error: vendor/lineage/build/soong/Android.bp:24:8: module "generated_kernel_includes": cmd: unknown variable '$(PATH_OVERRIDE_SOONG)'

ninja: build stopped: subcommand failed.

20:34:13 soong bootstrap failed with: exit status 1

#### failed to build some targets (15 seconds) ####

------

Yesterday:

- I ran brunch radxa0. It succeeded, I got the lineage-18.1-xxxxx-UNOFFICIAL-radxa0.zip, and recovery.img

- then I got stuck in the rathole of trying to use aml_upgrade.img from https://download.ods.ninja/Android/firmware/radxa0/ but not inside the build tree, all in /tmp.

Tonight:

- I tried to run 'mka bacon aml_upgrade' in the above tree (unchanged) and got the above error immediately.

- so I reran 'breakfast radxa0 && mka bacon aml_upgrade' and it was building for a long while but eventually above error.

- I have a bunch of .img files in the target dir, not sure if I had them before, recovery.img was rebuilt but lineage.zip was not rebuilt and I don't see anything matching 'aml*.img'
[Google TV General] npjohnson:
run breakfast radxa0, then run mka bacon aml_upgrade - it will work - that error tells me that breakfast didn't not succeed and you're building the generic target.
[Google TV General] dorkshoei:
I already did exactly this after it failed the first time.

I'll do it again, inside typescript so there is a full log.
[Google TV General] dorkshoei:
@npjohnson I either get the PATH_OVERRIDE_SOONG error or I get the error in the code block below.

Checking, there is no u-boot.bin in device/radxa/radxa0/factory and out/target/product/radxa0/aml_upgrade_package.img does not exist.

in each case breakfast seems to run ok

99% 889/892] out/target/product/radxa0/aml_upgrade_package.img created
FAILED: out/target/product/radxa0/aml_upgrade_package.img
/bin/bash -c "(echo -e \"device/radxa/radxa0/[URL='http://factory.mk:37']factory.mk:37[/URL]: *** \\\"no u-boot.bin found in device/radxa/radxa0/factory\\\".\" 2>&1 && false ) && (mkdir -p out/target/product/radxa0/upgrade ) && (prebuilts/build-tools/linux-x86/bin/acp out/target/product/radxa0/logo.img out/target/product/radxa0/upgrade/logo.img ) && (prebuilts/build-tools/linux-x86/bin/acp device/radxa/radxa0/factory/aml_sdc_burn.ini out/target/product/radxa0/upgrade/aml_sdc_burn.ini ) && (prebuilts/build-tools/linux-x86/bin/acp device/radxa/radxa0/factory/image.cfg out/target/product/radxa0/upgrade/image.cfg ) && (prebuilts/build-tools/linux-x86/bin/acp device/radxa/radxa0/factory/platform.conf out/target/product/radxa0/upgrade/platform.conf ) && (prebuilts/build-tools/linux-x86/bin/acp out/target/product/radxa0/boot.img out/target/product/radxa0/upgrade/boot.img ) && (prebuilts/build-tools/linux-x86/bin/acp out/target/product/radxa0/recovery.img out/target/product/radxa0/upgrade/recovery.img ) && (prebuilts/build-tools/linux-x86/bin/acp out/target/product/radxa0/2ndbootloader out/target/product/radxa0/upgrade/dtb.img ) && (prebuilts/build-tools/linux-x86/bin/acp out/target/product/radxa0/dtbo.img out/target/product/radxa0/upgrade/dtbo.img ) && (prebuilts/build-tools/linux-x86/bin/acp out/target/product/radxa0/super.img out/target/product/radxa0/upgrade/super.img ) && (prebuilts/build-tools/linux-x86/bin/acp out/target/product/radxa0/vbmeta.img out/target/product/radxa0/upgrade/vbmeta.img ) && (out/host/linux-x86/bin/aml_image_packer -r out/target/product/radxa0/upgrade/image.cfg out/target/product/radxa0/upgrade/ out/target/product/radxa0/aml_upgrade_package.img ) && (rm -rf out/target/product/radxa0/upgrade )"
device/radxa/radxa0/[URL='http://factory.mk:37']factory.mk:37[/URL]: *** "no u-boot.bin found in device/radxa/radxa0/factory".
[/quote]
[Google TV General] J_Woo:
Would not work no matter what. So I wound up using an official Lineage OS build and then flashing GAPPS. Works great. I would like to try one of the unofficial builds but will wait for the next one coming. The play store is not certified in the official Lineage build + GAPPS. Is it certified in the unofficial builds?
[Google TV General] npjohnson:
https://github.com/TheMuppets/propr...blob/lineage-19.1/radxa0/radio/bootloader.img - looks like 18.1 is weird I guess, copy this file into that place.
[Google TV General] dorkshoei:
"that place". Could you be more precise?

I put it into 'device/radxa/radxa0/factory', re-ran breakfast and mka but same error.
[Google TV General] npjohnson:
You will need to name it to match, u-boot.bin
[Google TV General] dorkshoei:
ok that built but:

# ./aml-flash-tool.sh ~/android/lineage/out/target/product/radxa0/aml_upgrade_package.img

Unpacking image [OK]

Initializing ddr ........[OK]

Running u-boot [KO]
[Google TV General] npjohnson:
Try running it again?
[Google TV General] dorkshoei:
Maybe we should go back to PM? I can't imagine this long of a public troubleshooting is of any interest to 99.9% of the people reading. If I get it working I'll followup with the process.

Tried 5 times. With USB_BOOT pressed. Same failure.

As I posted before, I get past this point with the prebuilt version:

https://download.ods.ninja/Android/firmware/radxa0/aml_upgrade_package.img

./aml-flash-tool.sh /tmp/aml_upgrade_package.img

Unpacking image [OK]

Initializing ddr ........[OK]

Running u-boot ........[OK]

Create partitions [OK]

Writing device tree [OK]

Writing bootloader [OK]

Wiping data partition [OK]

Wiping cache partition [OK]

Writing boot partition [OK]

Writing dtbo partition [OK]

Writing logo partition [OK]

Writing recovery partition [OK]

Writing super partition [KO]

Oddly, before it was reliably failing @"Writing recovery partition [KO]". Now that is working but (I tried it twice) and it now fails at the subsequent step. No clue what has changed.

Feel free to reply via PM
[Google TV General] ji:
Im curious did the remote even enter pairing mode while you were on unofficial? Should've seen a flashing red light as you did on official
[Google TV General] J_Woo:
I

It was really odd. The remote functioned because I could change volume as an example. But I could not progress forward in the boot cycle no matter the key sequence. On the official build, the left/exit and then home key worked on the remote to progress in the boot cycle.
[Google TV General] ji:
I believe thats because you triggered bug report with *that* key combo lol - for future reference itll always be these two buttons to pair on a dynalink *no matter what*
[Google TV General] ji:
@npjohnson Netflix still has the Device not Optimized -14 warning but atleast doesnt error out now! Hulu still gets P-DEV320 error for that playdrm

EDIT: in other news successfully built my own wade image using PRODUCT_USE_SW_OMX=false TARGET_HAS_TEE=true WITH_GMS=true - VNDK v33 is broken however and i needed to manually patch the amlogic audio library to v32

GMS is synched using MindTheGapps, one question I have is how do your sync yours? as per https://github.com/LineageOS/android_vendor_lineage/blob/lineage-20.0/config/partner_gms.mk it looks in vendor/partner_gms-tv when mindthegapps uses a completely different scheme. to bypass i just edited the makefile to the pathing
[Google TV General] npjohnson:
partner_gms is private - can't share it - it's mainly for CTS/VTS testing.

And what about vndk33? wade is fine on 13, not sure why you'd be getting that error - also you don't need the tee or the omx flag... they're that way already for wade lol
[Google TV General] ji:
no idea - after building i was getting this error: Abort message: 'incStrongRequireStrong() called on 0xebb81ab0 which isn't already owned' which caused a tombstone - only way to get it to go away was to downgrade libutils.so from v33 to v32

and shucks! I couldnt find anywhere where those flags are set for wade lol
[Google TV General] npjohnson:
you are tracking the old proprietary_vendor_amlogic on 19.1 branch lol - you need to sync the new split repos proprietary_vendor_amlogic_g12-common & proprietary_vendor_askey_wade - that will fix that.
[Google TV General] kennkanniff:
Sabrina still useless after years, lol.
[Google TV General] J_Woo:
Google really failed on Sabrina. The OEM firmware is terrible. Apps don't close completely (need to force close frequently) so you can hear even audibly an app running in background continuing on even though you closed it. Storage fills up. Really a fail.
[Google TV General] ji:
LOL that explains why i was manually patching files for it, the only reason i got it working was because i essentially cherry picked a commit that fixed the problem in 20 off the gx device repo (https://github.com/LineageOS/androi...mmit/adc08c28311b78af00e564557600c170f78c0d44). I am more astonished I got it to boot and work as a daily driver under this 1% 19.1 99% 20.0 build

rebuilt the way as you said and now all is working! Hulu even stopped with drm errors too!
[Google TV General] npjohnson:
What's hilarious is that one of our guys internally even managed to do this somehow lol That's the only reason it came to mind and I knew what you had done