yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A6 Themes, Apps, and Mods] hasel17:
You may notice that Dolby Atmos in Galaxy A6/A6+ only can be turned on when you plug your headphone/earphone in to your phone. But, I just flash the Galaxy S8 Exynos Dolby Atmos audio mod to make the Dolby Atmos can be turned on with speaker, and it works with our device too!

Note :

You must be rooted and have TWRP installed.

Seems like this mod just for Galaxy A6. Cause the Dolby Atmos files contain audio libs. You can try just installing the SoundAlive (DWYOR and please reply if that works with A6+)

Steps :

Uninstall SoundAlive with ES/Link2SD/Root Explorer/Any system application remover.

Reboot. After home screen show up, reboot to recovery.

Flash "Dolby_Installer_1.xx.zip" and "SoundAlive_8.0.21.zip"

Reboot. Then enable Dolby Atmos. Enjoy!

Download link (from original thread) : https://xdaforums.com/galaxy-s8/themes/audio-dolby-atmos-s9-t3810359

Credits :

-ImbaWind

-xpirt
[Samsung Galaxy A6 Themes, Apps, and Mods] ariber14:
has anyone found a way to install viper4android or xhifi with dolby atmos on a6 and a6plus?i tried all the zip packages with no luck.
[Samsung Galaxy A6 Themes, Apps, and Mods] an-_-dro:
for viper, choose from magisk module... there's magisk module for viper/xhifi
[Samsung Galaxy A6 Themes, Apps, and Mods] ariber14:
I installed it.i open it but the driver wont work.

The only mod audio i managed to make it work it was

jdsp_v1.8. It worked fine but the sound was no netter than dolby atmos that the phone allready has preinstalled. Someone with more knowledge could help us with v4a. Last year i had a a5 galaxy and i used arise deuteronomy v4a and i worked great. Nut on a6plus its useless:rolleyes:
[Samsung Galaxy A6 Themes, Apps, and Mods] an-_-dro:
strange..viper work flawless.. even when still using rooted odexed oreo..
[Samsung Galaxy A6 Themes, Apps, and Mods] ariber14:
i made it work. unistalling adaptsound with titanium backup didn't work. so i had to wipe the app.then i installed viper fx and it works great!!!
[Samsung Galaxy A6 Themes, Apps, and Mods] micmaze99:
Dolby atmos came standard oem stock with virtually all of the galaxy s9 features on the galaxy a6 2018 phone (at&t flavor) sold here in the states, but with an exynos processor oddly enough.... But with a 32gb rom & 3gb ram, it is virtually a xerox of the s9. Your choice.... S9 retail $799. A6 retail $409. Hmmm, tough choice for the same cell, give or take one at half the price. The at&t a6 has the total biometric system, bixby, sd expansion to 256gb, superamoled, all... And i mean all of their features are tit for tat. The selfie cam even has a flash! Different to say the absolute least. The a6+ goes even further out there. The a7 & a9 seem to be placed bets on how exactly many cameras one can place on 1 cell. U will see. Everyone needs to try the galaxy a6. It's a treat,!
[Samsung Galaxy A6 Themes, Apps, and Mods] hasel17:
All Samsung phones with Samsung Experience 9.0 came with Dolby Atmos built-in. But, it just works from audio jack except for Galaxy S9/+&Note9. So this mod makes the Dolby Atmos works with speaker too.
[Samsung Galaxy A6 Themes, Apps, and Mods] josemaesra:
If the A6 only has 1 speaker for multimedia ... this should be called "Mono Atmos"?

or does this mod make the call speaker also work for multimedia?

Thank you.
[Samsung Galaxy A6 Themes, Apps, and Mods] hasel17:
1. Dolby Atmos not makes phone to be stereo. It is just sound processor to make the sound more good.

2. No. It doesn't. There is no point in Galaxy A6 to make the handset speaker as a multimedia speaker. Since the multimedia speaker is in the right top side of the phone. Near the handset speaker. You won't get any stereo experience. Even if we make the handset speaker as multimedia speaker too to make it as front-firing speaker, We will barely hear it. The sound will not loud enough compared to the multimedia speaker.
[Samsung Galaxy A6 Themes, Apps, and Mods] josemaesra:
All right,

we're going to try it,

Thank you :good:
[Samsung Galaxy Note 9 Questions & Answers] CodeFox:
Just a quick question. I can't seem to get GSI's to boot on my note 9. Had no problems running any pie based GSI on my s9 plus. Is there a specific vendor I need to use on the note 9 for treble?

Any help would be appreciated :)
[Samsung Galaxy Note 9 Questions & Answers] TheUndertaker21:
I run them fine

Get arm 64 version? Aonly
[Samsung Galaxy Note 9 Questions & Answers] CodeFox:
Yeah that's what I've got same as on the s9. Trying to run pixel experience p but I get stuck at Sammy bootloop. Wasn't sure if it could be a vendor issue but as far as I remember vendor didn't matter on the s9.
[Samsung Galaxy Note 9 Questions & Answers] TheUndertaker21:
Flash the dev base rom then flash the gsi after wiping
[Samsung Galaxy Note 9 Questions & Answers] CodeFox:
Got it working in the end. Not sure what was going on. Appreciate the help :)
[Samsung Galaxy Note 9 Questions & Answers] XenonAndroid:
Heyy,

I've tried flashing the same Android P GSI. I also get a bootloop on reboot, can you please share how you fixed it.

Regards,

Anthony.C
[Samsung Galaxy Note 9 Questions & Answers] Xshooter726:
Does anyone know which treble roms are stable?

Wish RRemix worked but it has a strange low brightness bug. :(
[Samsung Galaxy Note 9 Questions & Answers] that_same_guy:
What I understood so far

did you find anything that works?

I tried Lineage, RRemix and OmniRom. all were working fine but all had the same brightness bug, stock camera also flickers & green screens when taking video, I dont remember on which rom.

I also tried pixel experience, the brightness was stuck on high, better than nothing, so if you want to use it you can give it a shot.

From [MENTION=9034316]Dil3mm4[/MENTION] on his GSI rom built

From [MENTION=1915408]phhusson[/MENTION] comment on note 9 brightness bug issue

if you are not a noob like me, you might find the files to flash on his github, since it looks like fixed, just waiting on his next rom release for these roms..

Reporting Bugs to [MENTION=1915408]phhusson[/MENTION] will help, probably least we can do, he mentioned creating Issue here

I will also do myself after testing more.

thing is the more people use it and report bugs, I believe it'll be a smoother experience for people who flash GSI roms later on the note9, and a great thanks to [MENTION=1915408]phhusson[/MENTION], redoing samsungs lousy work. he deserves a huge thanks from the community.
[Samsung Galaxy Note 9 Questions & Answers] that_same_guy:
Actually today I tried one more ROM, it from the same dev phhusson, here is the link

not only it is Android 9, it is stable enough to be used as a daily driver, I moved to it, Didnt want to post until I was sure.

So everything works, wifi, BT, hotspot, Sim, SD, Brightness Control, Mic, The Spen works as a mouse, HDMI, Fingerprints ..etc

what I found is buggy:

- the camera app(green flicker): you can use a third party camera app

- when you open the camera in Messaging to attach something.

One drawback to consider is Android P doesnt support Xposed yet. back to waiting for xposed support! =(

in fact I might keep using this, until Lineage OS 15.1 GSI gets fixed.
[Samsung Galaxy Note 9 Questions & Answers] Xshooter726:
I have not. I've tried all the roms you've tried with the same results. I don't really have much time to tinker with roms now a days due to work but maybe some time next week I'll start a bounty to spark things up. The hardware on the Note 9 is just begging to be tampered with lol and it being the first Note with Treble Support really is "The Next Big Thing" :victory:
[Samsung Galaxy Note 9 Questions & Answers] tsoureki:
These roms run both Exynos and Snapdragon models?
[MX Player] alexdedalus:
I have installed mx player 1.5, because my device is small capacity, so I need exactly the codec package (mxplayer codec 1.5 VFP ARMV6), but I could not find it on the official website. Thanks if you can help!

My email: alexdedalus@hotmail.com
[Sony Xperia XA2 Questions & Answers] pianogamer5:
Hey all, I got my XA2 a couple months ago and have been really enjoying it. Right out the box, I flashed LineageOS and the phone's been operating mostly fine for a while, with the exception of OTA updates. For a while, attempting to install a zip to slot B was causing problems with the modem, and after a certain point it was hanging on the Lineage boot screen.

I wanted seamless updates to work, so I tried something I thought would work. Using the unofficial FlashTool, I flashed the official Sony 12.9 ROM (July patch, I think?) hoping to OTA to the current 13.38 ROM and "reset" the B partitions to their stock state. However, the built-in Software Update kept saying I was up-to-date, and Xperia Companion on my laptop said it couldn't check for updates. So, I tried another route of using the official Sony Flash Tool "Emma." I saw two updates, so I flashed the older one (4.01 I think) and it worked fine. Then I used Fastboot to switch active partitions to the B slot and flashed the newer version (5.29 I think). I noticed the active slot had been changed back to A, so I set it to B and Fastboot rebooted. This is where I experienced problems.

Upon trying to power up the device, I see the LED flash green briefly, and nothing happens on screen. Upon plugging the device in with either volume key pressed, attempting to recover the device, I get the same thing with the flashing LED, except it does this repeatedly, and thus am unable to boot into Fastboot or Flash Mode. Am I screwed? It's not too terrible as I have other devices I can use, although now I essentially have a $300 paperweight...
[Sony Xperia XA2 Questions & Answers] :
If you are linux try to check dmesg when plugging into pc, in windows check device manager.

However, due to the fact its doing something at green led and abl/xbl is what sets led red I suspect there is an issue booting off emmc or something.

You could also check the serial log if you want to be sure of the isssue.

EDIT: try plugging into USB with the power key pressed

See if that does anything

If not, try plugging in with volume up pressed
[Sony Xperia XA2 Questions & Answers] andyrtr:
Did you manage to recover your phone again? It seems mine went broken now the same way.

I had flashed some Oreo based firmware (50.1.A.13.123) probably to Slot A to be able to OEM unlock it and remove the branding and bring it back to Oreo from Pie. Then unlocked bootloader and followed the LOS flashing guide and flashed LOS to Slot a. After rebooting TWRP it hang in a casual bootloop. Maybe there was a Pie based Firmware flashed to Slot B. I've tried to reflash original Oreo firmware to Slot A again and now I can't manage to get into flashmode or fastboot mode. Even forced shotdown or reboot with holding Power+VolUp and 2 minutes way won't work it seems. Linux cosole doesn't report anything using dmesg here.

Any idea? What do you mean how to check serial console - the phone one or pc?
[Xiaomi Mi Mix 2 Questions & Answers] veitograf:
hey guys,

i just installed the modded google camera app and set it to be the default camera app. however when double tapping volume down, it still opens miui camera. i even tried to freeze miui camera with tb and now nothing happens, when double tapping volume down.

anyone know if there is a way to get this working?
[Xiaomi Mi Mix 2 Questions & Answers] rr111:
No, I think it always open MIUI camera.
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
Hi all!

Starting a new thread to make things more clear to all. We need help. Please, review this thread from page 4:

https://xdaforums.com/mi-a2-lite/development/developers-kernel-source-code-available-t3835130/page4

I'm working in a port of LineageOS 16 to mi a2 lite (daisy).

Thanks to [MENTION=4170684]LazyT[/MENTION] [MENTION=4985023]hossman[/MENTION] and [MENTION=5332744]davze[/MENTION] for their help.

UPDATE:

At the moment we have a device tree and blobs. Uploaded to github.

Not flashed and tested by me yet.

Device:

https://github.com/robotusr/device_xiaomi_daisy (100% uploaded)

&

https://github.com/robotusr/device_x...msm8953-common (100% uploaded)

Proprietary files:

https://github.com/robotusr/propriet...r_xiaomi_daisy (100% uploaded)

&

https://github.com/robotusr/propriet...msm8953-common (100% uploaded)

File local_manifests/roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="robotusr/device_xiaomi_daisy" path="device/xiaomi/daisy" remote="github" />
<project name="robotusr/device_xiaomi_msm8953-common" path="device/xiaomi/msm8953-common" remote="github" />
<project name="robotusr/proprietary_vendor_xiaomi" path="vendor/xiaomi/daisy" remote="github" />
<project name="robotusr/proprietary_vendor_xiaomi_msm8953-common" path="vendor/xiaomi/msm8953-common" remote="github" />
</manifest>

Steps to build:

-Init LineageOS repo with repo init -u https://github.com/LineageOS/android.git -b lineage-16.0

-repo sync

-Create roomservice file at local_manifests/roomservice.xml

-repo sync (this downloads all daisy device and proprietary files (also for msmscommon))

-Run . build/envsetup.sh

-Because we are bulding an unsupported device with Android 8.1 sources (at the moment), and there are some errors about LOCAL_SDK_VERSION (seems to be mandatory in Android 9) and some dependencies.

Edit file build/make/core/sdk_check.mk (make a backup first to use the original file in future builds).

Modify line whitelisted_modules :=

With this:

whitelisted_modules := framework-res__auto_generated_rro SystemUI__auto_generated_rro Bluetooth__auto_generated_rro Settings__auto_generated_rro

-export ALLOW_MISSING_DEPENDENCIES=TRUE

-lunch lineage_daisy-eng

-brunch daisy

Please, tell me if it builds ok for you.

Best regards,

Daniel
[Xiaomi Mi A2 Lite Questions & Answers] iforgotmylogin:
This is very promising.

Thank you all for the hard work <3
[Xiaomi Mi A2 Lite Questions & Answers] alcopsy:
Thanks but need good twrp for that...
[Xiaomi Mi A2 Lite Questions & Answers] monojp:
Hey there,

if you need repos created on lineageos GitHub or other help just ask them via IRC. Luk made changes in the exchange repo for me for 15.1, I recommend him :)
[Xiaomi Mi A2 Lite Questions & Answers] mestesso_1:
Hy, can we use pixelrom as source ?
[Xiaomi Mi A2 Lite Questions & Answers] LazyT:
[MENTION=9394408]robotusr[/MENTION]

No sorry, I'm not working on it - only tried to help with your questions. ;)
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
Great! I'll try to contact Luk. Thanks!

Well, you helped me a lot!
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
Mounting vendor.img to create proprietary-files.txt is the only solution I've found. generate-blob-lists.sh script doesn't works.

Also I've change make files from cm to lineage (updated post #1)

Vendorimg contents:

drwxr-xr-x. 11 0 2000 4096 dic 31 2008 app
drwxr-xr-x. 4 0 2000 8192 dic 31 2008 bin
-rw-------. 1 0 0 3382 dic 31 2008 build.prop
-rw-r--r--. 1 0 0 1886 dic 31 2008 compatibility_matrix.xml
-rw-------. 1 0 0 614 dic 31 2008 default.prop
drwxr-xr-x. 19 0 2000 4096 dic 31 2008 etc
drwxr-xr-x. 3 0 2000 4096 dic 31 2008 firmware
drwxr-xr-x. 2 0 2000 4096 dic 31 2008 framework
drwxr-xr-x. 11 0 2000 114688 dic 31 2008 lib
drwxr-xr-x. 7 0 2000 12288 dic 31 2008 lib64
drwx------. 2 0 0 16384 dic 31 2008 lost+found
-rw-r--r--. 1 0 0 22941 dic 31 2008 manifest.xml
drwxr-xr-x. 2 0 2000 4096 dic 31 2008 media
drwxr-xr-x. 4 0 2000 4096 dic 31 2008 overlay
drwxr-xr-x. 11 0 2000 4096 dic 31 2008 package
drwxr-xr-x. 3 0 2000 4096 dic 31 2008 radio
drwxr-xr-x. 5 0 2000 4096 dic 31 2008 rfs
drwxr-xr-x. 2 0 2000 4096 dic 31 2008 speccfg
-rw-r--r--. 1 0 0 15446 dic 31 2008 ueventd.rc

This is the audio acdb section I've put in propietary-files.txt at the moment:

# Audio ACDB
vendor/etc/acdbdata/QRD/QRD_Bluetooth_cal.acdb
vendor/etc/acdbdata/QRD/QRD_General_cal.acdb
vendor/etc/acdbdata/QRD/QRD_Global_cal.acdb
vendor/etc/acdbdata/QRD/QRD_Handset_cal.acdb
vendor/etc/acdbdata/QRD/QRD_Hdmi_cal.acdb
vendor/etc/acdbdata/QRD/QRD_Headset_cal.acdb
vendor/etc/acdbdata/QRD/QRD_Speaker_cal.acdb
vendor/etc/acdbdata/adsp_avs_config.acdb
vendor/etc/acdbdata/QRD/QRD_workspaceFile.qwsp

Info from etc/acdbdata (oem rom):

etc/acdbdata/:
adsp_avs_config.acdb
MTP
QRD

etc/acdbdata/MTP:
msm8953-tasha-snd-card
MTP_Bluetooth_cal.acdb
MTP_General_cal.acdb
MTP_Global_cal.acdb
MTP_Handset_cal.acdb
MTP_Hdmi_cal.acdb
MTP_Headset_cal.acdb
MTP_Speaker_cal.acdb
MTP_workspaceFile.qwsp

etc/acdbdata/MTP/msm8953-tasha-snd-card:
MTP_WCD9335_Bluetooth_cal.acdb
MTP_WCD9335_General_cal.acdb
MTP_WCD9335_Global_cal.acdb
MTP_WCD9335_Handset_cal.acdb
MTP_WCD9335_Hdmi_cal.acdb
MTP_WCD9335_Headset_cal.acdb
MTP_WCD9335_Speaker_cal.acdb
MTP_WCD9335_workspaceFile.qwsp

etc/acdbdata/QRD:
QRD_Bluetooth_cal.acdb
QRD_General_cal.acdb
QRD_Global_cal.acdb
QRD_Handset_cal.acdb
QRD_Hdmi_cal.acdb
QRD_Headset_cal.acdb
QRD_Speaker_cal.acdb
QRD_workspaceFile.qwsp

I'm creating propietary-files.txt by hand. Please, be patient...

Regards,

Daniel.
[Xiaomi Mi A2 Lite Questions & Answers] vod_:
greet ,good luck guys
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
It's not necessary to flash system.img (at the moment) using fastboot.

Obviously, we need a custom recovery to make rom backups and to flash other partitions.

I'm not a developer. Just learning to port a rom to my device.

Regards,

Daniel
[Xiaomi Mi A2 Lite Questions & Answers] foudroid:
We have to wait working TWRP ! TWRP by TWRPbuilder is not working, perhaps they should fix it.or we have to wait !that A/B partition make the devellopement not easy !
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
I agree with you, but building a new device tree has nothing to do with that (partially).

Building a new device tree is useful to porting roms, not only for a recovery. I'm focused on getting an optimised system.img for our device.

This is the hard work.

Kernel's sources for daisy are out and these files are useful to build a custom recovery.

But I repeat, I'm not an expert and, of course, not a developer.

Regards,
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
Some progress.

I don't need to use extract-files.sh because I have all vendor files (extracted from vendor.img and system.img).

Just tested to make clean && make clobber

breakfast daisy

and always the same. roomservice.xml pointing to my new device repo in git doesn't works. Also tested with local_manifest.xml (I think it's deprecated).

Always build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_daisy".

and

Repository for daisy not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.

The way to get breakfast working is to upload all of my files to LineageOS git as device_xxxxxxxxxx

I'm thinking that another repository like themuppets in the past, doesn't works for Lineage. But I don't know why.

I've asked for help in LineageOS irc and an answer was:

xD

This doesn't helps
[Xiaomi Mi A2 Lite Questions & Answers] wertus33333:
did you try to directly lunch "lineage_daisy-eng"? and (even if it sounds dumb and u controlled this already 20 times) all your device makefiles are in the correct location? You could also add daisy in a vendorsetup.sh in device tree and execute ". build/envsetup.sh" again (should see daisy in lunch menu then).

Don't worry, thats the usual answer u get when asking some "devs" for help with android...
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
All mk files are in path and vendorsetup.sh too. envsetup includes vendorsetup.sh from device/xiaomi/daisy.

Lunch "lineage_daisy-eng", breakfast daisy, breakfast lineage_daisy fails with the same error.

Thanks!
[Xiaomi Mi A2 Lite Questions & Answers] wertus33333:
Hmm... I am building oreo at the moment so i'm not sure if P builds the same way. You declared lineage_daisy in lineage.mk? like this:

device/xiaomi/daisy/lineage.mk:

PRODUCT_NAME := lineage_daisy
BOARD_VENDOR := Xiaomi

PRODUCT_GMS_CLIENTID_BASE := android-xiaomi
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
Hi these are my files:

lineage.mk

# Inherit some common lineage stuff.
$(call inherit-product, vendor/lineage/config/common_full_phone.mk)
# Inherit device configuration
$(call inherit-product, device/xiaomi/daisy/full_daisy.mk)

## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := daisy
PRODUCT_NAME := lineage_daisy
BOARD_VENDOR := Xiaomi
PRODUCT_BRAND := xiaomi
PRODUCT_MODEL := daisy
PRODUCT_MANUFACTURER := xiaomi

full_daisy.mk

# Copyright (C) 2017 The LineageOS Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

# Inherit from those products. Most specific first.
$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)

# Inherit from daisy_sprout device
$(call inherit-product, device/xiaomi/daisy/device.mk)

# Device identifier. This must come after all inclusions
TARGET_VENDOR := xiaomi
PRODUCT_DEVICE := daisy
PRODUCT_NAME := lineage_daisy
PRODUCT_BRAND := xiaomi
PRODUCT_MODEL := Mi A2 Lite
PRODUCT_MANUFACTURER := xiaomi

vendorsetup.sh

add_lunch_combo lineage_daisy-eng

lineage.dependencies

{
"repository": "android_device_xiaomi_msm8953-common",
"target_path": "device/xiaomi/msm8953-common"
}
]
[Xiaomi Mi A2 Lite Questions & Answers] wertus33333:
Here is my daisy los15 tree, it is building at the moment but not sure if it works in the end (maybe this helps you to adapt) also mind the comments i put in the fields above ;)

edit: It does NOT work yet xD
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
Thanks thanks thanks!

I'll try it today.

Best regards!
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
Finally I have managed to extract blobs. It's not possible to extract all files without root, but I really have this files from vendor.img. Copied manually to directory structure and now I'll try to compile all.

Thanks guys!

[MENTION=7730830]wertus33333[/MENTION]

Have you setup any roomservice.xml or local_manifest.xml file to lunch? I'm getting same error

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_daisy".
[Xiaomi Mi A2 Lite Questions & Answers] wertus33333:
no, i downloaded everything manually (git clone..) if the makefiles are correct and in the right place it should find the device... always lunch the device with "lunch lineage_daisy-eng". Otherwise no idea, i'm also quite noob with those things (built and adjustet some roms and kernels with help of github commits but that's it)
[Xiaomi Mi A2 Lite Questions & Answers] LazyT:
Looking through other device trees all have lineage_codename.mk not only lineage.mk.

So maybe it looks for lineage_daisy.mk and can't find it?
[Xiaomi Mi A2 Lite Questions & Answers] robotusr:
Yes, I've modfied name to lineage_daisy.mk but same error.

Also, I've added again vendorsetup.sh