Search results

it is the recommended specs by Google. it's been years compiling on anything less than 16 has cause out of memory issues

vmmem is the process that you care about in wsl 2. concerning restarting jack servers check documentation, you'll find it on Google. I would not recommend compiling on less than 32GB of RAM

is this in wsl 2.0? the setup seems odd. I do not recognize the device nor the source that it seems to be attempting to fetch. If you check soong and other logs in out/ dir you will probably find more details in there about what's happening.

making your own unofficial builds is not compatible with running the official builds

wsl was introduced in windows 10

WSL 2.0 is OUT, build all the droids! Hi all, Microsoft just released the Windows 10 May 2020 update. But the bigger news is that it comes with WSL2. The TLDR of it is that Windows now has a Linux kernel bundled with it and that's game changing. And what that means for us is out of the box /...

https://forum.xda-developers.com/showpost.php?p=80287033&postcount=519

did you read the warnings in my guide? Do NOT use mnt, it will likely result in failures. it is telling you that it's permission denied. it doesn't have read and/or write permissions to that folder.

thanks for all the info :) I'll make sure to link to your post when I update the OP. wsl 2 is out but only on insider previews. I'm waiting for it to be released on regular update channels with update 20H1 since I don't like using insider previews on my personal machine.

the error is the illegal instruction. I've already shown you that android 9 / lineage-16.0 is not supported officially supported on h815 and this is not a device support page. additionally, wsl 2.0 will likely resolve most of these kinds of issues since there Windows will be shipping a real...

this is not a device support thread, sorry I can't help you there. you'll probably find more help on the threads for your device.

this is easy to find on Google. you're creating a file if the file doesn't exist already and adding lines to it. you can do that with any editor out there whether through terminal or GUI. pick one you like and stick to it. on Ubuntu I use nano if the edits are simple

I've already said it's not supported and gave you the github link. You can only build older versions. I only supported lineage-15.1 and 16.0 anyways on wsl 1.0. I will attempt to support 17.0 on wsl 2.0 if it requires any changes (supposedly should not)

I am not supporting lineage 17 on wsl 1.0. once wsl 2 releases I will update the front page with the new instructions even though it should build out of the box

at that point you probably can follow all the steps from repo sync onward

thanks :) appreciate wsl 2 should not require to follow the directions I gave in the front page. only wsl1. I'll update my instructions when wsl2 is fully released with the next Windows update (sometime in the first half of this year)

https://github.com/LineageOS/android_device_lge_h815 there is no official lineage-16.0 branch sorry there may exist unofficial branches for your device. you'd have to setup a roomservice.xml under .repo/local_manifests to fetch them from GitHub but I can't recommend it. In any case, welcome to...

you are correct. those are the available options. I've already announced I was not going to spend the effort supporting android 10 (lineage 17) on wsl 1.0

I can't find any official repositories referencing rpi3. I can't help much in this case

what's the device codename?

has it ever been officially supported by LineageOS. I've never heard of pi support

the nsjconf stuff seems to be talking about root. could it be that it says that because you're running as root user and not a normal user? I've never seen this when I run lunch and such. the actual errors that matter are Can not locate config makefile for product "lineage_crosshatch". that's...

https://github.com/LineageOS/android_device_google_crosshatch

your environment seems odd. I haven't seen cmdline::logparams lines before nor microsoft standard in HOST_OS_EXTRA. is this wsl 2.0?

I haven't tried yet with 2.0. have run out of disk space. I am waiting to upgrade my computer before tinkering with it again, but as I have said before it should work out of the box. are you sure you installed all the required packages? some have reported that they were able to successfully...

I don't support Android 10 and I don't think I will given that WSL2.0 should not require any patches. I recommend you install WSL2.0

what version are you building? you should not pick that commit since it is already merged

Probably. Check the directory of that module for a makefile. If there's is one and you've setup the environment with envsetup.sh, run mm in the directory to build that module.

I haven't tried with docker. Docker on windows has been annoying to me given the use of hyper-v. what do you mean by docker resetting?

don't know what anyrom is

if you check https://github.com/LineageOS you'll find if they have a v1awifi tree (might be outdated and not sure it has the 16.0 branch). concerning vendor, yes.

WSL 2 announcement https://devblogs.microsoft.com/commandline/announcing-wsl-2/ I'm on the insider previews, so will test based on the LineageOS build guide and see if it works out of the box (aka without my commits) in June.

building 15.1 apparently. please refer to the link in the first post

did you check the most thanked posts?

maybe add this one too? https://github.com/TheMuppets/proprietary_vendor_oppo if you read your error it says it vendor/oppo/msm8974-common does not exist

If you search around you'll find screenshots in the thread. Concerning the windows store, it is the recommended way. If you get the setup working another way then good for you but don't expect support from me in that case.

Yes

Read the warnings on the original post

Follow the steps?

Does it build on Ubuntu? If so, there's no reason why it wouldn't

https://review.lineageos.org/q/project:LineageOS%252Fandroid_device_oneplus_oneplus3+branch:lineage-16.0

repo sync and breakfast (at least, on first execution) steps should get the device tree (should automatically add it to roomservice). TheMuppets is for vendor blobs (which if not correctly synced will cause breakfast to fail). Copying and pasting is a bad idea. I'd start over if you're doing that

https://github.com/LineageOS/android_device_huawei_angler all the .mk files are makefiles

repopick should be included if you source build/envsetup.sh. try running the command after that and you'll need -t to pick by topic from gerrit

running breakfast should just work if you followed the steps correctly, should not need to edit anything except roomservice to add muppets. it looks like you're complicating your life a lot when it should be simple and if it isn't it is probably just not ready . anyways this is a device specific...

I already showed you the work that is being done on the device tree (see the gerrit link). you need to repopick it if you want to use it in your builds while it isn't merged officially

you need to sync again in step 13 after adding your vendor to roomservice.xml for breakfast to work. if your vendor folder has huawei/angler then it should work fine. the point of syncing muppets is to not have to extract proprietary blobs

https://review.lineageos.org/q/topic:%22angler-p%22+(status:open%20OR%20status:merged also, are you sure you have the vendor folders from TheMuppets too?

Not sure I'm understanding the situation here. Have you checked Gerrit for angler?