Help building - LeEco Le Max 2 Questions & Answers

Help building - LeEco Le Max 2 Questions & Answers

Trying to build LOS with UBER, getting this error while compiling: https://pastebin.com/pGjLaR1R
Any ideas?

KuranKaname said:
Trying to build LOS with UBER, getting this error while compiling: https://pastebin.com/pGjLaR1R
Any ideas?
Click to expand...
Click to collapse
Sorry, but what is UBER?

Related

Problem about build lineageOS from source!!!!

I'm so sorry about this thread.
Today, I tried to build this rom from source but I faced with a lot of problem because no dev do this rom so I try to it by myself.
Here is there steps I did:
download source code with repo.
- Prepare kernel: I use some guide in AOSP to build this kernel.
- Repair software binaries: Im just download it from Xperia dev.
the first big thing I got is when I use command breafast to build, I didn't not find anything about my device althought I create some folder and place the material on this as same as the guide in AOSP.
So can someone help me rewrite these code to make it work ?

max26292 said:
I'm so sorry about this thread.
Today, I tried to build this rom from source but I faced with a lot of problem because no dev do this rom so I try to it by myself.
Here is there steps I did:
download source code with repo.
- Prepare kernel: I use some guide in AOSP to build this kernel.
- Repair software binaries: Im just download it from Xperia dev.
the first big thing I got is when I use command breafast to build, I didn't not find anything about my device althought I create some folder and place the material on this as same as the guide in AOSP.
So can someone help me rewrite these code to make it work ?
Click to expand...
Click to collapse
You can use OmniROM as a source. Re-writing the sources to compile should not be a big thing. Can you share your sources?

eagleeyetom said:
You can use OmniROM as a source. Re-writing the sources to compile should not be a big thing. Can you share your sources?
Click to expand...
Click to collapse
first i Follow this guide: https://wiki.lineageos.org/devices/nicki/build
and change these thing on this step with something under this line: Prepare the device-specific code
after that I use this guide to build suzu kernel: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
And I download binaries from source: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
and I store these thing on google cloud engine, so how to share it to you?

max26292 said:
first i Follow this guide: https://wiki.lineageos.org/devices/nicki/build
and change these thing on this step with something under this line: Prepare the device-specific code
after that I use this guide to build suzu kernel: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
And I download binaries from source: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
and I store these thing on google cloud engine, so how to share it to you?
Click to expand...
Click to collapse
I recommend Github

eagleeyetom said:
I recommend Github
Click to expand...
Click to collapse
I read that limit bandwidth is 1gb per month and storage is 5gb, isn't it?
I didn't rewrite any code, just build everything from the source
https://github.com/max26292/lineageos_suzu

Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.

eagleeyetom said:
Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.
Click to expand...
Click to collapse
ok i will try :3 I read some guide but It didn't give me enough knowledge to build

eagleeyetom said:
Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.
Click to expand...
Click to collapse
I'm waiting for great News about your custom rom Projekt, Are there progresses?

rec0re said:
I'm waiting for great News about your custom rom Projekt, Are there progresses?
Click to expand...
Click to collapse
Not yet. I need to sort out my health issues first.

Have you any news about LineageOS for Xperia X?

At this time, no develop build this rom for our device

Maybe had better to wait Android O with vendor layer and LOS 15, will be much easier to update.

@eagleeyetom
As I wanted to get into android rom development/building, I started today syncing the LOS source an forking the omnirom device tree for suzu and loire-common and adapted already some stuff a little bit.
But you probably know more than me about this, so when forking the device tree, loire-commen, etc... for suzu from omnirom, there are these omni.dependencies files, I somehow don't have a plan what to do with those.
Do they need some adapting too or something else?
I would be very grateful if you could point me into the right direction what do with them.
Greetings.

SahilCrazy said:
@eagleeyetom
As I wanted to get into android rom development/building, I started today syncing the LOS source an forking the omnirom device tree for suzu and loire-common and adapted already some stuff a little bit.
But you probably know more than me about this, so when forking the device tree, loire-commen, etc... for suzu from omnirom, there are these omni.dependencies files, I somehow don't have a plan what to do with those.
Do they need some adapting too or something else?
I would be very grateful if you could point me into the right direction what do with them.
Greetings.
Click to expand...
Click to collapse
You need to clone all the repos mentioned in that file. If you are porting LOS, just leave it blank until it gets official.

eagleeyetom said:
You need to clone all the repos mentioned in that file. If you are porting LOS, just leave it blank until it gets official.
Click to expand...
Click to collapse
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
Code:
device/sony/loire-common/sepolicy/device.te:4:ERROR 'duplicate declaration of type/attribute' at token ';' on line 39737:
type trim_area_partition_device, dev_type;
type persist_block_device, dev_type;
checkpolicy: error(s) encountered while parsing configuration
/root/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /root/android/system/out/target/product/suzu/obj/ETC/sepolicy_intermediates/policy.conf
[ 28% 16734/57899] Import includes file: /root/android/system/out/target/product/suzu/obj/EXECUTABLES/init_intermediates/import_includes
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
This happens later also with init.te and tad.te, not only device.te. I tried commenting those lines out but this resulted in an error saying that theres no type declaration.

SahilCrazy said:
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
Code:
device/sony/loire-common/sepolicy/device.te:4:ERROR 'duplicate declaration of type/attribute' at token ';' on line 39737:
type trim_area_partition_device, dev_type;
type persist_block_device, dev_type;
checkpolicy: error(s) encountered while parsing configuration
/root/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /root/android/system/out/target/product/suzu/obj/ETC/sepolicy_intermediates/policy.conf
[ 28% 16734/57899] Import includes file: /root/android/system/out/target/product/suzu/obj/EXECUTABLES/init_intermediates/import_includes
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
This happens later also with init.te and tad.te, not only device.te. I tried commenting those lines out but this resulted in an error saying that theres no type declaration.
Click to expand...
Click to collapse
You can try to build permissive first and try to fix sepolicy later.

eagleeyetom said:
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
You can try to build permissive first and try to fix sepolicy later.
Click to expand...
Click to collapse
Okey, how do you build permissive? There needs to be something done in the kernel/.../security/selinux/makefile or am I wrong?

SahilCrazy said:
Okey, how do you build permissive? There needs to be something done in the kernel/.../security/selinux/makefile or am I wrong?
Click to expand...
Click to collapse
Take this line as a reference: https://github.com/OrdenKrieger/android_device_zuk_ham/blob/cm-14.1/BoardConfig.mk#L51

eagleeyetom said:
Take this line as a reference: https://github.com/OrdenKrieger/android_device_zuk_ham/blob/cm-14.1/BoardConfig.mk#L51
Click to expand...
Click to collapse
So here's the first boot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I switched the sources, I used now the repos from sonyxperiadev instead of omnirom as I kept getting the sepolicy errors even when I tried building permissive.
There are a few things that still need work, like the sim is not recognized etc.
Will release it here on xda when most of stuff is working fine.
Thanks for your great help!:good:

SahilCrazy said:
So here's the first boot:
I switched the sources, I used now the repos from sonyxperiadev instead of omnirom as I kept getting the sepolicy errors even when I tried building permissive.
There are a few things that still need work, like the sim is not recognized etc.
Will release it here on xda when most of stuff is working fine.
Thanks for your great help!:good:
Click to expand...
Click to collapse
Congratulations! I hope that you will make it stable soon

[ROM][DISCONTINUED][UNOFFICIAL][7.1.2] AOSiP 6.3

Sources
Device tree
Kernel
[ROM][UNOFFICIAL][7.1.2] AOSiP 6.3
Contributors:
Fedray, Wzedlare, CodeZero, m_vaisakh
Source Code: https://github.com/AOSiP
ROM OS Version: 7.1.2 Nougat
Version Information
Status: Stable
Current Stable Version: 6.3
Stable Release Date: 2017-09-26

Nice rom

Make this a DevDB thread.

How do you enable root? I could install magisk, apps request root but there is no pop-up. There is also no root setting in developer options... Thanks!

mrfrantastic said:
How do you enable root? I could install magisk, apps request root but there is no pop-up. There is also no root setting in developer options... Thanks!
Click to expand...
Click to collapse
Install Magisk 14, and when some app request root it should pop up. It worked when I tested.

Fedray said:
Install Magisk 14, and when some app request root it should pop up. It worked when I tested.
Click to expand...
Click to collapse
That is exactly what I did

Fedray said:
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on CAF N source. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (@xlxfoxxlx)
Paul Clark(@Dabug123)
Akhil Narang(@akhilnarang)
Sri Harsha(@srisurya95)
Sean Grondin
Support/Community:
Full support is always on the top of the list. Visit our AOSiP Google plus community for all your ROM needs. There we have all the latest links to gapps and other helpful communities. Or just stop and engage in off topic fun.
Source code:
As the name states we are open source and encourage anyone to skim through the code. However the builds we release are not to be taken apart and parted out.
AOSiP Gerrit review
AOSiP Github
AOSiP Devices Source
Downloads:
ROM
Credit/Thanks:
Mike Williams(founder and creator of AOSiP)
Google
Dirty Unicorns
AICP
ABC Rom
Screwd
Omni
Krexus
Cyanogenmod
SlimRoms
ChainFire (SuperSU)
Beanstown106
Cory Collins
Any others I may have forgotten
All our testers
Sources
Device tree
Kernel
[ROM][UNOFFICIAL][7.1.2] AOSiP 6.3
Contributors:
Fedray, Wzedlare, CodeZero, m_vaisakh
Source Code:https://github.com/AOSiP
ROM OS Version: 7.1.2 Nougat
Version Information
Status: Stable
Current Stable Version: 6.3
Stable Release Date: 2017-09-26
Click to expand...
Click to collapse
Whooooo! You did it bro!

mrfrantastic said:
That is exactly what I did
Click to expand...
Click to collapse
Have you also installed the magisk manager apk?
If you open the app you can check that magisk is installed correctly

TheFixItMan said:
Have you also installed the magisk manager apk?
If you open the app you can check that magisk is installed correctly
Click to expand...
Click to collapse
Yeah, it shows two green checkmarks, so it should theoretically work. Strange. Will see if I can fix it with an older magisk version.

mrfrantastic said:
Yeah, it shows two green checkmarks, so it should theoretically work. Strange. Will see if I can fix it with an older magisk version.
Click to expand...
Click to collapse
Clean data and cache of magisk manager
Enviado de meu Moto G5 usando Tapatalk

fernando2722 said:
Clean data and cache of magisk manager
Enviado de meu Moto G5 usando Tapatalk
Click to expand...
Click to collapse
Thank you for your time. Still facing the same problem after cleaning data and cache, sadly.

mrfrantastic said:
Thank you for your time. Still facing the same problem after cleaning data and cache, sadly.
Click to expand...
Click to collapse
Go to Magisk > Superuser and check if the apps have the root denied. Or if they appear there. Like this.
Enviado desde mi Moto G5 mediante Tapatalk

Same problem here. But I suffered it in LOS, and in AOSP extended. Root only works in ADB but not for apps. Tried everything. I think it's related to the Segmentation fault error described on LOS thread, and not all variants of Cedric are affected.
PS: if you try to get root access lots of times, eventually it will pop up the root request in Magisk and it will work, you need to do it almost 30 times.
andyro2008 said:
However the ROM seems to be affected by the same error as LineageOS. I hoped that this was not the case because it isn't based on LOS. I'm not a developer, but I guess that the problem must be in the kernel code released by Lenovo.
If you are not familiar with the problem, this is the first comment in a series that describes it: https://forum.xda-developers.com/g5...-1-moto-g5-t3611973/post73510009#post73510009
I hope it's useful. Again thanks for your work, help and time!!!!!!
Click to expand...
Click to collapse

andyro2008 said:
Same problem here. But I suffered it in LOS, and in AOSP extended. Root only works in ADB but not for apps. Tried everything. I think it's related to the Segmentation fault error described on LOS thread, and not all variants of Cedric are affected.
PS: if you try to get root access lots of times, eventually it will pop up the root request in Magisk and it will work, you need to do it almost 30 times.
Click to expand...
Click to collapse
Yeah, I feared it is part of the segmentation error. It's a pitty, really. I hope we see an update for twrp (or kernel?) which fixes this problem. Maybe with Android O it might be fixed...

mrfrantastic said:
Yeah, I feared it is part of the segmentation error. It's a pitty, really. I hope we see an update for twrp (or kernel?) which fixes this problem. Maybe with Android O it might be fixed...
Click to expand...
Click to collapse
What is your exact model? From where? Not Al variants appears to be affected.
Enviado desde mi Moto G5 mediante Tapatalk

andyro2008 said:
What is your exact model? From where? Not Al variants appears to be affected.
Enviado desde mi Moto G5 mediante Tapatalk
Click to expand...
Click to collapse
It's a ZY322584M3. Bought via Amazon marketplace in Germany (though not sure where it might originate). But this seems to get OT so maybe we could start a thread in the appropriate section

mrfrantastic said:
It's a ZY322584M3. Bought via Amazon marketplace in Germany (though not sure where it might originate). But this seems to get OT so maybe we could start a thread in the appropriate section
Click to expand...
Click to collapse
No, that was just what I wanted to know. I think only the European versions of Cedric have the problem. Mine is from UK. Let's hope the Devs find a way to fix it.
Enviado desde mi Moto G5 mediante Tapatalk

mrfrantastic said:
It's a ZY322584M3. Bought via Amazon marketplace in Germany (though not sure where it might originate). But this seems to get OT so maybe we could start a thread in the appropriate section
Click to expand...
Click to collapse
andyro2008 said:
No, that was just what I wanted to know. I think only the European versions of Cedric have the problem. Mine is from UK. Let's hope the Devs find a way to fix it.
Enviado desde mi Moto G5 mediante Tapatalk
Click to expand...
Click to collapse
I never had any problem with root. That's weird.
Enviado desde mi Moto G5 mediante Tapatalk

Fedray said:
I never had any problem with root. That's weird.
Enviado desde mi Moto G5 mediante Tapatalk
Click to expand...
Click to collapse
I assume you have the Latin American variant. I'm from Argentina too, but I'm using an UK device bought in Amazon, a weird 3gb RAM variant with removable battery and Dual SIM. So I'm thinking that something must be incompatible with our devices.
If you look at the thread of LineageOS, you will see that there are many people affected. With or without root, commands like "pm", "am, "adb backup" are causing the "segmentation fault error". These commands are used by many root applications (Flashfire, Titanium Backup, Greenify, Disable Services, NapTime, ForceDoze) so you will find lots of complains in customs ROMs related to this problems.
Asking for root access when using Magisk also causes the segfault error. I checked it by looking at the logcat. As always if one repeats many times the command or the action in question it eventually works. Every ROM except the stock one causes the problem on my device. Of course I tried everything, wiping, flashing, going back stock, starting all over again.
I you want to help us, my WhatsApp/Telegram/Gmail are available for you in your Inbox. I'm from Rosario, Argentina, so I talk Spanish way better than English. Thanks for your attention.
Enviado desde mi Moto G5 mediante Tapatalk

mrfrantastic said:
How do you enable root? I could install magisk, apps request root but there is no pop-up. There is also no root setting in developer options... Thanks!
Click to expand...
Click to collapse
Yesterday I started using AOSiP and yes, Magisk for some reason didn't install the Magisk Manager apk, that's why it didn't pop up the requests. Extract the Magisk Manager apk or download it from apkmirror, install it and then should work. Good luck!

Build successfull for Pie

Hi everyone,
I just build successfully Android 9 Pie for the X compact from the Sony repo.
I have not test it yet but it boot.
If you want to try I can give you the files.

Lots of bugs?
Some screenshot?
Is it good for daily?
Thx!

luomei said:
Lots of bugs?
Some screenshot?
Is it good for daily?
Thx!
Click to expand...
Click to collapse
It works but not for daily as Gapps aren't available yet...
I try some unofficials ones but it causes the phone not to boot

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Please give more details on whats working and whats not
Bluetooth
Wifi
Hotspot
Calling
3g/4g connectivity
Camera
Etc...

I didn't test all features but network works
I can't test it for now because I need my phone (I only have one Xperia compatible), but I'll try to test all features later this week :victory:

compilation attempt
Hi @nervousapp,
I'm attempting a build myself using the guide published by Sony recently, but I'm stuck at some errors:
system/sepolicy/Android.mk:79: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[948/948] including vendor/qcom/opensource/wlan/wcnss-service/Android.mk ...
vendor/qcom/opensource/location/loc_api/ds_api/Android.mk: error: libloc_ds_api (SHARED_LIBRARIES android-arm64) missing libloc_pla (SHARED_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
vendor/qcom/opensource/location/loc_api/ds_api/Android.mk: error: libloc_ds_api (SHARED_LIBRARIES android-arm) missing libloc_pla (SHARED_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
vendor/qcom/opensource/location/loc_api/loc_api_v02/Android.mk: error: libloc_api_v02 (SHARED_LIBRARIES android-arm64) missing libloc_pla (SHARED_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
vendor/qcom/opensource/location/loc_api/loc_api_v02/Android.mk: error: libloc_api_v02 (SHARED_LIBRARIES android-arm) missing libloc_pla (SHARED_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:833: error: exiting from previous errors.
Click to expand...
Click to collapse
If I set ALLOW_MISSING_DEPENDENCIES=true I don't get much further:
[1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
Environment variable ALLOW_MISSING_DEPENDENCIES was modified (false => true), regenerating...
No need to regenerate ninja file
ninja: error: 'kernel/sony/msm-4.9/common-kernel/kernel-dtb-kugo', needed by 'out/target/product/kugo/kernel', missing and no known rule to make it
23:43:22 ninja failed with: exit status 1
#### failed to build some targets (28 seconds) ####
Click to expand...
Click to collapse
Did you also encounter these/could you give me a pointer how to complete the compilation successfully ? (I don't want to sound stereotypical, but I think it warrants mentioning I'm on Arch (maybe something's fukcy with my environment))

harryharryharry said:
Hi @nervousapp,
I'm attempting a build myself using the guide published by Sony recently, but I'm stuck at some errors:
If I set ALLOW_MISSING_DEPENDENCIES=true I don't get much further:
Did you also encounter these/could you give me a pointer how to complete the compilation successfully ? (I don't want to sound stereotypical, but I think it warrants mentioning I'm on Arch (maybe something's fukcy with my environment))
Click to expand...
Click to collapse
You have to get the file here https://github.com/sonyxperiadev/vendor-sony-kernel and put it in kernel/sony/msm-4.9/common-kernel/ and all will be fine.
You may experienced another error, see https://talk.sonymobile.com/t5/Android-9-x-Pie/Compilation-error/td-p/1339265

I have also experienced no boot with the aosp-eng but the userdebug boot like a charm ?

Thanks for the heads up! I am building userdebug now from a xubuntu livecd because I kept getting the libloc_pla dependency error. On the livecd I'm not getting the error. So probably some environment issue on Arch, if I find a solution I'll post it here for future google passersby.

harryharryharry said:
Thanks for the heads up! I am building userdebug now from a xubuntu livecd because I kept getting the libloc_pla dependency error. On the livecd I'm not getting the error. So probably some environment issue on Arch, if I find a solution I'll post it here for future google passersby.
Click to expand...
Click to collapse
Sorry for the noob question, but what dit you choose at the following step?
Code:
source build/envsetup.sh && lunch
And another question. Which version of Ubuntu did you use for the successfull build?
Thanks a lot!

I chose option: 64. aosp_f5321-userdebug
and the livecd I compiled with is: xubuntu 18.04.1
As nervousapp already mentioned, as of yet flashing (unofficial) 9.0 gapps is not possible as it will cause a boot hang.

harryharryharry said:
I chose option: 64. aosp_f5321-userdebug
and the livecd I compiled with is: xubuntu 18.04.1
As nervousapp already mentioned, as of yet flashing (unofficial) 9.0 gapps is not possible as it will cause a boot hang.
Click to expand...
Click to collapse
Thanks for your answear.

nervousapp said:
Hi everyone,
I just build successfully Android 9 Pie for the X compact from the Sony repo.
I have not test it yet but it boot.
If you want to try I can give you the files.
Click to expand...
Click to collapse
If you want someone to comment on your build then please upload it. I guess quite many can test it.

Small update: Sony updated their guide and manifests to android-9.0.0_r6 and opengapps officially released 9.0 gapps. So I attempted another pie build to see if meanwhile the 'gapps bootloop' issue was addressed. Sadly this is not yet the case.

harryharryharry said:
Small update: Sony updated their guide and manifests to android-9.0.0_r6 and opengapps officially released 9.0 gapps. So I attempted another pie build to see if meanwhile the 'gapps bootloop' issue was addressed. Sadly this is not yet the case.
Click to expand...
Click to collapse
I build a new one also but in my case it was stuck at sony logo instead of bootloop.

Did you build userdebug or eng ? Because eng hangs on boot still.

Nope. It was userdebug.

Today I built again. This time I removed kernel files completely from both 4.4 and 4.9 folders, and synced. Build was successful. At first boots it gives an error saying device failed verification or something like that and powers off. But next time boots up. Basic things seems like working. Camera works but Video recording doesn't. WiFi works. Fingerprint sensor doesn't work. Bigger problem is gapps also doesn't work . Twrp flashes it successfully but when it boots up you see Google apps is not actually there. I couldn't see any error messages in gapps log neither. I didn't test it extensively so there may be other problems but these are the ones noticed at first glance.

Same here with the verification issue on boot, @oshmoun already reported it as a bug:
https://github.com/sonyxperiadev/bug_tracker/issues/177
Meanwhile I've been able to build omnirom 9.0 with some minor compiling-hindrances. It boots and almost everything seems to be working quite neatly! A couple of issues I've encountered thus far:
- The wifi module bcmdhd needs some firmware files placed in the correct location (they're in the process of switching kernel modules from bcmdhd to brcmfmac.)
- The video recording crash issue @maluus described also occurs on omnirom 9.0.
- The screen won't go off (this can be circumvented by switching 'Display -> Advanced -> Ambient display -> Always on' off)
(- my pet peeve: 'volume rocker next/previous track control during screen off'-feature missing)
Main plus for me is gapps can be installed to omnirom 9.0. So I'll try to make it my daily driver, report me some bugs

[ROM][Bacon][8.1][UNOFFICIAL] LineageOS 15.1 for OnePlusOne (6/12/2019)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 15.1 is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS 15.1 is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Bug reporting:
Before the report make sure that you've installed the latest build of the ROM.
Explain the bug in details and, if possible, methods to reproduce it.
For most issues, you should attach the logcat.
Random reboots? Please upload last_kmsg immediately after the kernel crash.
Note: I will only be providing builds once every month and when new security patches come in. I don't have enough time to be making them every week. Latest build provided should have the June 2019 security patches and have the build fingerprint fix included. These builds should be daily driver friendly and have nothing changed or added and they should be pure Lineage based builds. Please download the latest version of OpenGapps and flash along with the ROM to be able to use the play store and other google related services. If you want to root i recommend flashing and using Magisk 19.3. Enjoy and i hope you appreciate my pure Lineage 15.1 Unofficial builds for bacon.
Downloads:
Latest 6/12 build for Bacon is here: https://www.androidfilehost.com/?fid=6006931924117894050
ROM Download folder is here: https://www.androidfilehost.com/?w=files&flid=295452
Sources:
Device Tree: https://github.com/LineageOS/android_device_oneplus_bacon/tree/lineage-15.1
Vendor Tree #1: https://github.com/TheMuppets/proprietary_vendor_oneplus/tree/lineage-15.1
Vendor Tree #2: https://github.com/TheMuppets/proprietary_vendor_oppo/tree/lineage-15.1
Kernel: https://github.com/LineageOS/android_kernel_google_msm/tree/lineage-15.1
Manifests Tree: https://github.com/JT1510365/local_manifests/blob/lineage-15.1/bacon.xml

reserved for future use

Noob Q: So since Lineage stopped updating 15.1 in feb and started pushing 16, you can still give us updates? If im running the last version of 15.1 can i just add your zip, then TWRP install, clean caches and done?

pete3000 said:
Noob Q: So since Lineage stopped updating 15.1 in feb and started pushing 16, you can still give us updates? If im running the last version of 15.1 can i just add your zip, then TWRP install, clean caches and done?
Click to expand...
Click to collapse
Yup you don't even need to clean cache and I will be making new builds when new security patches come in so yes I will be providing updates Latest build that is out has the may security patches.
I will also be making a lineage os 13.0 build for bacon
But if you have problems I suggest you do a full wipe so wipe everything except for internal storage then install the ROM and latest opengapps nano for Oreo then magisk 19.2

Does it have the device fingerprint commit

nathsagar96 said:
Does it have the device fingerprint commit
Click to expand...
Click to collapse
Unfortunately no but you can still download Facebook and messenger from apk mirror and manually install them both and they will work if you pick the latest correct version for your device. I have no idea how to fix the fingerprint issue so if someone could help me to do that it would be great

JT1510365 said:
Unfortunately no but you can still download Facebook and messenger from apk mirror and manually install them both and they will work if you pick the latest correct version for your device. I have no idea how to fix the fingerprint issue so if someone could help me to do that it would be great
Click to expand...
Click to collapse
You can do that by editing the fingerprint in lineage_bacon.mk file

nathsagar96 said:
You can do that by editing the fingerprint in lineage_bacon.mk file
Click to expand...
Click to collapse
okay thank you i will look into it

JT1510365 said:
okay thank you i will look into it
Click to expand...
Click to collapse
Just in case the commit url
https://review.lineageos.org/c/LineageOS/android_device_oneplus_bacon/+/243112

nathsagar96 said:
Just in case the commit url
https://review.lineageos.org/c/LineageOS/android_device_oneplus_bacon/+/243112
Click to expand...
Click to collapse
Thank you i will hopefully post a new build later today with the fingerprint fix if i have time

Hello, is there a new upstream build coming?

Disrupthor said:
Hello, is there a new upstream build coming?
Click to expand...
Click to collapse
Yes i will hopefully be posting a new build sometime today just been busy with personal life thats all but i know how to fix the fingerprint issue

Disrupthor said:
Hello, is there a new upstream build coming?
Click to expand...
Click to collapse
New build has been uploaded
https://www.androidfilehost.com/?fid=6006931924117894050

i like to build with MicroG but i get this error can you help me?
============================================
[44/44] bootstrap /home/exodusnick79/LineageOS/15.1/out/soong/.minibootstrap/build.ninja.in
[4/4] /home/exodusnick79/LineageOS/15.1/out/soong/.bootstrap/bin/minibp /home/exodusnick79/LineageOS/15.1/out/soong/.bootstrap/build.ninja
[872/873] glob vendor/qcom/opensource/interfaces/wifi/*/Android.bp
[56/56] /home/exodusnick79/LineageOS/15.1/out/soong/.bootstrap/bin/soong_build /home/exodusnick79/LineageOS/15.1/out/soong/build.ninja
/home/exodusnick79/LineageOS/15.1/out/build-lineage_bacon.ninja is missing, regenerating...
[135/1089] including ./device_oneplus_bacon/Android.mk ...
build/core/base_rules.mk:238: error: device_oneplus_bacon/rootdir: MODULE.TARGET.ETC.init.bacon.rc already defined by device/oneplus/bacon/rootdir.
18:31:33 ckati failed with: exit status 1
salute
christian

Exodusnick said:
i like to build with MicroG but i get this error can you help me?
============================================
[44/44] bootstrap /home/exodusnick79/LineageOS/15.1/out/soong/.minibootstrap/build.ninja.in
[4/4] /home/exodusnick79/LineageOS/15.1/out/soong/.bootstrap/bin/minibp /home/exodusnick79/LineageOS/15.1/out/soong/.bootstrap/build.ninja
[872/873] glob vendor/qcom/opensource/interfaces/wifi/*/Android.bp
[56/56] /home/exodusnick79/LineageOS/15.1/out/soong/.bootstrap/bin/soong_build /home/exodusnick79/LineageOS/15.1/out/soong/build.ninja
/home/exodusnick79/LineageOS/15.1/out/build-lineage_bacon.ninja is missing, regenerating...
[135/1089] including ./device_oneplus_bacon/Android.mk ...
build/core/base_rules.mk:238: error: device_oneplus_bacon/rootdir: MODULE.TARGET.ETC.init.bacon.rc already defined by device/oneplus/bacon/rootdir.
18:31:33 ckati failed with: exit status 1
salute
christian
Click to expand...
Click to collapse
I have no idea pm me and will try to help you further I might be able to help you and when you pm me link all the sources you are using so I know what might be the problem

@JT1510365
I wrote you a pm.

@JT1510365 Hello, ain't there no more builds comming?

Disrupthor said:
@JT1510365 Hello, ain't there no more builds comming?
Click to expand...
Click to collapse
lineage-15.1 07.29
Latest upstream LineageOS changes with fingerprint 5.0.2 LRX22G YNG1TAS0YL
https://cloud.mail.ru/public/2Zmz/2yixUCL39

MurikBMX said:
lineage-15.1 07.29
Latest upstream LineageOS changes with fingerprint 5.0.2 LRX22G YNG1TAS0YL
https://cloud.mail.ru/public/2Zmz/2yixUCL39
Click to expand...
Click to collapse
Ok so August security patch is out. New build coming? Thanks.

Disrupthor said:
Ok so August security patch is out. New build coming? Thanks.
Click to expand...
Click to collapse
https://cloud.mail.ru/public/4BYQ/4zRnPELa4

[A13]Lineage OS 20 build makefile error.Please help me!

I am building Lineage OS 20 on an i9100.
The development environment is Ubuntu 22.04 LTS and the device source code is from @ rINanDO.
So, I am facing this problem. I have everything ready and when I type "brunch i9100" I get the error in the image.
I have tried everything and keep getting the error so I am posting this.
Please help and advice me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

yonekome said:
I am building Lineage OS 20 on an i9100.
The development environment is Ubuntu 22.04 LTS and the device source code is from rINanDO.
So, I am facing this problem. I have everything ready and when I type "brunch i9100" I get the error in the image.
I have tried everything and keep getting the error so I am posting this.
Please help and advice me.View attachment 5724229
Click to expand...
Click to collapse
Ask @rINanDO bro

Concept48 said:
Ask @rINanDO bro
Click to expand...
Click to collapse
I thought perhaps this was not an error due to his device source code, so I wrote here

yonekome said:
I am building Lineage OS 20 on an i9100.
The development environment is Ubuntu 22.04 LTS and the device source code is from @ rINanDO.
So, I am facing this problem. I have everything ready and when I type "brunch i9100" I get the error in the image.
I have tried everything and keep getting the error so I am posting this.
Please help and advice me.View attachment 5724229
Click to expand...
Click to collapse
I have the same issue when compiling Awaken A13. It's something related to clang, you should switch to clang proton. Let me know if you fixed it and how.

Nem1x said:
I have the same issue when compiling Awaken A13. It's something related to clang, you should switch to clang proton. Let me know if you fixed it and how.
Click to expand...
Click to collapse
Good job Nemix !!

yonekome said:
I thought perhaps this was not an error due to his device source code, so I wrote here
Click to expand...
Click to collapse
I fixed it by cloning Proton Clang and adding these lines to BoardConfig in device:
TARGET_KERNEL_CLANG_VERSION := proton
TARGET_KERNEL_CLANG_PATH := $(shell pwd)/prebuilts/clang/host/linux-x86/clang-proton
To clone proton clang run:
git clone --depth=1 https://github.com/kdrag0n/proton-clang.git prebuilts/clang/host/linux-x86/clang-proton

Nem1x said:
I fixed it by cloning Proton Clang and adding these lines to BoardConfig in device:
TARGET_KERNEL_CLANG_VERSION := proton
TARGET_KERNEL_CLANG_PATH := $(shell pwd)/prebuilts/clang/host/linux-x86/clang-proton
To clone proton clang run:
git clone --depth=1 https://github.com/kdrag0n/proton-clang.git prebuilts/clang/host/linux-x86/clang-proton
Click to expand...
Click to collapse
Nice bro , so soon Android 13 in the test bank

Nem1x said:
I fixed it by cloning Proton Clang and adding these lines to BoardConfig in device:
TARGET_KERNEL_CLANG_VERSION := proton
TARGET_KERNEL_CLANG_PATH := $(shell pwd)/prebuilts/clang/host/linux-x86/clang-proton
To clone proton clang run:
git clone --depth=1 https://github.com/kdrag0n/proton-clang.git prebuilts/clang/host/linux-x86/clang-proton
Click to expand...
Click to collapse
Thanks for the advice.
I have a question about a script to add to BoardConfig.
The place to add it is in my case
android/lineage/device/samsung/i9100/BoardConfig.mk
Click to expand...
Click to collapse
and
android/lineage/device/samsug/galaxys2-common/BoardCommonConfig.mk
Click to expand...
Click to collapse
at the bottom?
I ran clone proton clang command first and added the script to the above location, but the error did not go away.

Nem1x said:
TARGET_KERNEL_CLANG_VERSION := proton
TARGET_KERNEL_CLANG_PATH := $(shell pwd)/prebuilts/clang/host/linux-x86/clang-proton
Click to expand...
Click to collapse
Yeah it goes at. android/lineage/device/samsung/i9100/BoardConfig.mk
I think that it doesn't matter where you put it. Bottom of the file should work.

Nem1x said:
Yeah it goes at. android/lineage/device/samsung/i9100/BoardConfig.mk
I think that it doesn't matter where you put it. Bottom of the file should work.
Click to expand...
Click to collapse
Hmmm.
I apply them and still get an error.
I'm stumped.

Try to add these lines as well in BoardConfig:
KERNEL_LD := LD=ld.lld
TARGET_KERNEL_ADDITIONAL_FLAGS := DTC_EXT=$(shell pwd)/prebuilts/misc/linux-x86/dtc/dtc LLVM=1

Nem1x said:
Try to add these lines as well in BoardConfig:
KERNEL_LD := LD=ld.lld
TARGET_KERNEL_ADDITIONAL_FLAGS := DTC_EXT=$(shell pwd)/prebuilts/misc/linux-x86/dtc/dtc LLVM=1
Click to expand...
Click to collapse
I added them, but I get an error…

I think I found the solution.

kbuild: use HOSTLDFLAGS for single .c executables · PixelExperience-Devices/[email protected]
When compiling executables from a single .c file, the linker is also invoked. Pass the HOSTLDFLAGS like for other linker commands. Signed-off-by: Robin Jarry <[email protected]> Cc: Josh...
github.com
lavender: Disable LLVM_BINUTILS · PixelExperience-Devices/[email protected]
• LLVM is now enabled by default as google is moving away from GCC. • Kernel side patches are required and as of now our kernel isn't compaitable. • Refs- https://gerrit.pixelexperience.org/c/v...
github.com
I hope you can find paths.

Remove previous patches as well.

Nem1x said:
kbuild: use HOSTLDFLAGS for single .c executables · PixelExperience-Devices/[email protected]
When compiling executables from a single .c file, the linker is also invoked. Pass the HOSTLDFLAGS like for other linker commands. Signed-off-by: Robin Jarry <[email protected]> Cc: Josh...
github.com
lavender: Disable LLVM_BINUTILS · PixelExperience-Devices/[email protected]
• LLVM is now enabled by default as google is moving away from GCC. • Kernel side patches are required and as of now our kernel isn't compaitable. • Refs- https://gerrit.pixelexperience.org/c/v...
github.com
I hope you can find pataths.
Click to expand...
Click to collapse
It worked fine!
I added these.
~/android/lineage/kernel/samsung/smdk4412/scripts/Makefile.host
# Create executable from a single .c file
# host-csingle -> Executable
quiet_cmd_host-csingle = HOSTCC [email protected]
cmd_host-csingle = $(HOSTCC) $(hostc_flags) -o [email protected] $< \
cmd_host-csingle = $(HOSTCC) $(hostc_flags) $(HOSTLDFLAGS) -o [email protected] $< \
$(HOST_LOADLIBES) $(HOSTLOADLIBES_$(@F))
$(host-csingle): $(obj)/%: $(src)/%.c FORCE
$(call if_changed_dep,host-csingle)
Click to expand...
Click to collapse
and
~/android/lineage/device/samsung/i9100/BoardConfig.mk
# Kernel
TARGET_KERNEL_SOURCE := kernel/samsung/smdk4412
TARGET_KERNEL_LLVM_BINUTILS := false
BOARD_KERNEL_SEPARATED_DTBO := true
Click to expand...
Click to collapse
Thanks for the great support.

so did you manage to build lineage 20.0?

notnoelchannel said:
so did you manage to build lineage 20.0?
Click to expand...
Click to collapse
I did. I don't know about him.

notnoelchannel said:
so did you manage to build lineage 20.0?
Click to expand...
Click to collapse
50% complete, but new error.

Better Mobile App

welcome