Problem about build lineageOS from source!!!! - Sony Xperia X Questions & Answers

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

Related

[ROM] AOKP 4.2.2 - unofficial m7 builds

{
"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"
}
Device: m7 (HTC One)
All I've done is compiled sources to bring you these builds. All the heavy lifting is done over at https://github.com/htc-msm8960 - thank those guys, they are working incredibly hard to bring AOSP to this device. I think the list of developers goes something like this: h8rift, intervigil, toastcfh, deck, Flinny, Flemmard, Codeworkx, birdman
That means that any bugs that exist in other AOSP builds will probablacy exist in these builds.
Click to expand...
Click to collapse
» Installation is simple:
If coming from another ROM or another major AOKP version, wipe data in recovery
Make sure you're using the latest CWM or TWRP
Flash ROM
Flash Google Apps (GAPPS)
Reboot
Code:
May 22
- included test call audio fix
- included xxhdpi device commits
May 21
- latest AOKP sources
- latest CM m7 sources
from gerrit:
- updated ribbons
- LockScreen: Fix crash when unlocking twice
- Add transparency settings for lockscreen (2/2)
- Smooth Spinners: Makes the loading "spinner" animation smoother in non-holo apps
sorry for the delay for those who waited :)
» Check merged commits on AOKP's Gerrit
build: http://goo.im/devs/roman/aokp_m7 - my nightlies will be in this folder. I'll also probably push them through AOKPush
gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip - b7e53e96e1c8b1a1c4865bf29418c8e0
» Building AOKP for your m7
First, create file .repo/local_manifests/m7.xml with the following contents: https://gist.github.com/romanbb/5517890
repo sync
Cherry pick this: http://gerrit.aokp.co/#/c/8320/
Cherry pick this: http://gerrit.aokp.co/#/c/8159/
Cherry pick this: http://gerrit.aokp.co/#/c/8321/
Build aokp_m7:
Code:
. build/envsetup.sh && brunch aokp_m7-userdebug
» AOKP Gerrit
» AOKP on Github
» SOURCE on AOKP.co
We greatly appreciate your contribution in the form of code, or PayPal donations.
» Donation options on AOKP.co
Enjoy!
for science
Whhhhhhhat?!?!?! Awesome sauce, great to see you here Roman!!
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
eliasadrian said:
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
He's got the HTC One on T-Mobile
https://twitter.com/romanbb/status/330053433702887425
eliasadrian said:
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, Amazon hardware. I'm not going to dev so much "for" it, even though I might try... but I think I'll dev with it?
Sent from my Nexus 7 using Tapatalk HD
new build up http://goo.im/devs/roman/aokp_m7/
coming from the s3, any word on what works and what does not work?
nicksmizzle said:
coming from the s3, any word on what works and what does not work?
Click to expand...
Click to collapse
Camera doesn't work
Sent from my HTC One using xda app-developers app
Camera Bummer
Once camera works, this will be my daily driver! can hardly wait!!!:highfive:
Roman,
Good to see you around, I think something is up with AOSP with the GFX. If you download the live wallpaper below you will see it has some strange effects that do not happen on the stock rom. My Nexus 10 tablet on 4.2.2 does not have the artifacts so I do not believe this is a 4.2.2 issue with the phone but both your rom and the ALPHA for Cyanogen 10.1 both display the issue.
https://play.google.com/store/apps/details?id=com.tribok.android.livewallpaper.springtideshower.lite
Its a great wallpaper BTW but wanted to bring it to your attention because maybe something is off with the GFX driver being used? I understand that major work is done by https://github.com/htc-msm8960 but thought I would let you know if you could help pass along.
Thanks,
1WayJonny
Roman, good to have you on the one.
I sure hope you all can get the camera working....
I get this on compiling from the new .xml and instructions today
device/htc/m7-common/overlay/packages/apps/Settings/res/values/arrays.xml:8: error: Error: No resource found that matches the given name (at '^index_0' with value '@string/pulse_length_always_on').
make: *** [/home/joey/aokp/out/target/common/obj/APPS/Settings_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....
warning: no entries written for dimen/password_keyboard_height
warning: no entries written for drawable/sym_keyboard_delete_holo
any suggestions?
superg81 said:
I get this on compiling from the new .xml and instructions today
device/htc/m7-common/overlay/packages/apps/Settings/res/values/arrays.xml:8: error: Error: No resource found that matches the given name (at '^index_0' with value '@string/pulse_length_always_on').
make: *** [/home/joey/aokp/out/target/common/obj/APPS/Settings_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....
warning: no entries written for dimen/password_keyboard_height
warning: no entries written for drawable/sym_keyboard_delete_holo
any suggestions?
Click to expand...
Click to collapse
check the op. there are new build instructions. it's specifically the overlay commit that will fix that for you
Romanbb said:
check the op. there are new build instructions. it's specifically the overlay commit that will fix that for you
Click to expand...
Click to collapse
just did and get this now
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/81/8481/1 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
let me re post here
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/20/8320/4 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
superg81 said:
just did and get this now
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/81/8481/1 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
let me re post here
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/20/8320/4 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
Click to expand...
Click to collapse
in each of those dirs, you could do a "git reset --hard HEAD" to clear out any changes you may have made
Romanbb said:
in each of those dirs, you could do a "git reset --hard HEAD" to clear out any changes you may have made
Click to expand...
Click to collapse
gotcha,shall try that
did you realize 4 and 5 in op for picks are same?
superg81 said:
gotcha,shall try that
did you realize 4 and 5 in op for picks are same?
Click to expand...
Click to collapse
i did not
Romanbb said:
i did not
Click to expand...
Click to collapse
:silly:
are you guys using the tmo htc one having any issues with call audio?

The cm12.1 will be coming

Hello everyone:
This a good new ,I port cm 12.1 to a3ul and a3tl. and it`s bring up.
But it has a letter bugs to be fixed(wifi).
Screenshot:
{
"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"
}
device tree:
https://github.com/desire610-dev
kernel source:
https://github.com/desire610-dev/kernel_htc_msm8974
vendor:
https://github.com/desire610-dev/vendor_htc_a3
zihan said:
Hello everyone:
This a good new ,I port cm 12.1 to a3ul and a3tl. and it`s bring up.
But it has a letter bugs to be fixed(wifi).
Screenshot:View attachment 3662921
device tree:
https://github.com/desire610-dev
kernel source:
https://github.com/desire610-dev/kernel_htc_msm8974
vendor:
https://github.com/desire610-dev/vendor_htc_a3
Click to expand...
Click to collapse
Very cool, I saw you cloned my sources a couple of weeks ago and that you where working on the dts files a couple of days ago. I have to have another look at what you have done. I keep getting boot loops that are related to the screnn dts and driver files. Awesome to see you having some success. Great work, I'll try a build with your kernel changes tonight. I've been getting so frustrated with the dtb kernel binding errors.
PS I am quite a github noob, I was trying to work out how to mesage you from in there the other day to share a fix I had for display driver build errors but I coulndn't work out how. Is the a PM system in github.
Also I notice you are using a dpi value of 200 but when you do that it actually ends up using 213 as thats the lowest value the screen will use(atleast with the international screen) and many apps have compatibility issues with any value below 240.
thanks again
Thanks again zihan. Took a quick look at your kernel and it turns out I had been trying to fix things that didn't matter. I had mistakes in my defconfig. So I reverted my last couple of changes and fixed the defconig and now my cm12.1 boots too. Let the debugging begin.
Good job to the both of you!
Fix for wifi
zihan said:
Hello everyone:
This a good new ,I port cm 12.1 to a3ul and a3tl. and it`s bring up.
But it has a letter bugs to be fixed(wifi).
Screenshot:View attachment 3662921
device tree:
https://github.com/desire610-dev
kernel source:
https://github.com/desire610-dev/kernel_htc_msm8974
vendor:
https://github.com/desire610-dev/vendor_htc_a3
Click to expand...
Click to collapse
I just sent a pull request to update the wifi files in the cm12.1 branch of device tree . It updated firmware files that work with the updated pronto drivers in cm12.1 kernel. I accidentally committed them to the cm11 branch 1st but the reverted the changes. As I said earlier, I a GitHub noob and still working it out. My build seems to be working pretty good now so I'm going to upload a test build and start getting some bug testing feedback.
MiniBlu said:
I just sent a pull request to update the wifi files in the cm12.1 branch of device tree . It updated firmware files that work with the updated pronto drivers in cm12.1 kernel. I accidentally committed them to the cm11 branch 1st but the reverted the changes. As I said earlier, I a GitHub noob and still working it out. My build seems to be working pretty good now so I'm going to upload a test build and start getting some bug testing feedback.
Click to expand...
Click to collapse
Thanks,i will test it and merge now.Which instant communication tool do you use?
zihan said:
Thanks,i will test it and merge now.Which instant communication tool do you use?
Click to expand...
Click to collapse
The wifi was bring.Thanks.
is the WiFi bug patched? I really want to try this but first I want to know if i would have WiFi as it is important during the day. can one of you please PM me a link to a flashable zip/kernel? the links to the vendor and kernel failed to flash through TWRP (3.0.0-0) I would really appreciate the flashable zip and instructions on how to flash it. I can be a beta tester if you need but I do also have school so I would also appreciate a more stable build that wont crash every 5 minutes, but I can live with the crashing. If you do respond, Thanks! if you dont respond thats OK.
Half_Of_A_Life_Left said:
is the WiFi bug patched? I really want to try this but first I want to know if i would have WiFi as it is important during the day. can one of you please PM me a link to a flashable zip/kernel? the links to the vendor and kernel failed to flash through TWRP (3.0.0-0) I would really appreciate the flashable zip and instructions on how to flash it. I can be a beta tester if you need but I do also have school so I would also appreciate a more stable build that wont crash every 5 minutes, but I can live with the crashing. If you do respond, Thanks! if you dont respond thats OK.
Click to expand...
Click to collapse
The links in here are source files for building a rom and kernel not for flashing to a device. Yes wifi is fixed in the build I posted here.
MiniBlu said:
The links in here are source files for building a rom and kernel not for flashing to a device. Yes wifi is fixed in the build I posted here.
Click to expand...
Click to collapse
thanks!
Half_Of_A_Life_Left said:
thanks!
Click to expand...
Click to collapse
Hi, i installed this ROM in D610 with A3 VLPVT SHIP S-ON HBOOT -3.18.0.0000
but proccess installed show me:
Updating partition detals:___done
Full SELinux support is presant
MTP Enabled. Wipping Dalvik Cache
Cleaned: /data /dalvik_cache_
Formating Catche using make ext4fs
Updating partition detailsone
Instaling zip file 'ext_sd/Room_cm12
Checking /skipping MD5 no found
Updating proccess ended with signal: 11
Error installing zip file '/external_sd/Room/cm12 test room.zip
Formating cache using ext4fs
Wipping data without /data/media
Done.
..........
CM12 unoffiicial saga.zip Error: 7

[ROM][PORT][UNOFFICIAL][A6020][8.0] LineageOS 15.0

[QRCODE][/QRCODE]
{
"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 is a free, community built, aftermarket firmware distribution of Android 8.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
RIL (Calls, SMS)
Video Playback
Audio ( Record and Playback )
Sensors
Flash
FMRadio
Led
GPS
Bluethood
What's not working :
Data (soon will be fixed)?
VOLTE
Camera
Wifi
Instructions :
Download the latest build & patch and gapps
Reboot to recovery
Flash the latest build & patch and gapps
Reboot
Note :- If you face any password related issue while booting just format data via TWRP. Also this is Early Build so there might be few other issues which i'm not aware of.
Screenshots :
NOTICE :
The rom is not build from source its a ported version of los15 from ido.Dont forget to flash the patch after flasing the rom else the rom will not bootup only for first port
First port :
ROM :- LineageOS 15.0
PATCH:- Patch
Gapps :- [url]https://www.androidfilehost.com/?fid=961840155545592807[/URL]
Credits :
subha785(The Guy who booted LOS 15 First)
Highwaystar
Harry8242
LOS Team and all other Developers Who Helped
ROM OS Version: 8.0 Oreo
Version Information
Status: Alpha
Current Stable Version:
Created 2017-09-08
Last Updated 2017-09-8
Wow, very little bugs
Thanks waiting for the link
PS
Upload changes to github, so other devs can help you solving bugs
mac12m99 said:
Wow, very little bugs
Thanks waiting for the link
PS
Upload changes to github, so other devs can help you solving bugs
Click to expand...
Click to collapse
+1
Waiting patiently! Ready to test and report bugs.
A6020l36 variant
wow.. thanks a lot developer for developing android o rom for k5 plus
Is there any way to use internet on this Rom, however great work :good:
TanmaySharma said:
Is there any way to use internet on this Rom, however great work :good:
Click to expand...
Click to collapse
I will try to fix it
Thankyou Bhai
Good Job guys.
Working on it to, but you beat me to it . All the changes are available on which github repos? maybe I can help to. I just saw that @Harry8242 fixed some typo in the device tree.
Great job! But if ROM is not daily-use, no sense to install it, to try it.
I see this ROM is only port from Xiaomi Redmi 3/Pro (ido) (the same SoC)
Orginal thread
There are also [email protected]
stable released for Kenzo and also aosp 8.0
@scritch007 hi there, it's been a long time since we have seen you in the forums, being a beginner.my device tree looked pretty nasty before , now it's cleaned up and just about ready I guess, if you have the time to contribute you can check out the below github repos.
https://github.com/harry8242/android_device_lenovo_A6020/tree/lineage-15.0?files=1
https://github.com/harry8242/kernel_lenovo_msm8916
Harry8242 said:
@scritch007 hi there, it's been a long time since we have seen you in the forums, being a beginner.my device tree looked pretty nasty before , now it's cleaned up and just about ready I guess, if you have the time to contribute you can check out the below github repos.
https://github.com/harry8242/android_device_lenovo_A6020/tree/lineage-15.0?files=1
https://github.com/harry8242/kernel_lenovo_msm8916
Click to expand...
Click to collapse
Yes my laptop was too old, and I had some stuff going on in real life, so I was off, I just bought a new laptop, so it's time to play again with the phone .
I made a build with your branch of device + some patch of shreps and I, the following commits over the default lineage https://github.com/boulzordev/local_manifests/blob/lineage-15.0/repopicker.sh
And the nougat kernel.
Build doesn't boot, and doesn't even vibrate, so I have to figure out what I missed. I'm cherry picking the binder and sdcardfs changes to see it this will help. If you have an idea of what changes are mandatory for the kernel to boot, I'll happily take them
scritch007 said:
Yes my laptop was too old, and I had some stuff going on in real life, so I was off, I just bought a new laptop, so it's time to play again with the phone .
I made a build with your branch of device + some patch of shreps and I, the following commits over the default lineage https://github.com/boulzordev/local_manifests/blob/lineage-15.0/repopicker.sh
And the nougat kernel.
Build doesn't boot, and doesn't even vibrate, so I have to figure out what I missed. I'm cherry picking the binder and sdcardfs changes to see it this will help. If you have an idea of what changes are mandatory for the kernel to boot, I'll happily take them
Click to expand...
Click to collapse
Kernel is ready on my branch, the port booted with it, so something is wrong with the device tree or the hals you were using,
Harry8242 said:
Kernel is ready on my branch, the port booted with it, so something is wrong with the device tree or the hals you were using,
Click to expand...
Click to collapse
I was using nougat's kernel, so I didn't take your kernel. I'll build with that and carry on.
scritch007 said:
I was using nougat's kernel, so I didn't take your kernel. I'll build with that and carry on.
Click to expand...
Click to collapse
And also cm-14.1 hals will cause a bootloop
scritch007 said:
Good Job guys.
Working on it to, but you beat me to it . All the changes are available on which github repos? maybe I can help to. I just saw that @Harry8242 fixed some typo in the device tree.
Click to expand...
Click to collapse
Wow great to see you back buddy . Collab between you shreps and harry would be awesome :laugh:
Amazing rom good job broo
impulsar said:
Wow great to see you back buddy . Collab between you shreps and harry would be awesome :laugh:
Click to expand...
Click to collapse
It would be an early Christmas miracle
Flashed the Rom and found that Audio is not working too. And even the ear piece does not work.
Microphone also not working. But Rom looks pretty cool.

[ROM][UNOFFICIAL][dumpling] LineageOS 15.1 [AOSP][8.1][16 FEB]

{
"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 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.
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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's special about my build:
Sometimes I pick a few patches from the Lineage Gerrit before they are approved and merged into our trees.
The kernel is based on Lineage's one, but I have upstreamed with the latest patches from linux-stable, added a few things such as performance and battery tweaks, security and stability fixes, SafetyNet spoofing, additional kernel controls.... This kind of things
The device trees will also be improved overtime with various improvements from mixed sources (for example better presets, different HAL solutions and so on).
All the rest is kept as recommended in the maintainer's manifest (including the optional patches).
What's working:
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
NFC
Camera
Video Playback
Audio (Record and Playback)
Fingerprint (with gestures)
Sensors
Flash
Notification LED
SELinux
SafetyNet
What's not working:
VoLTE calls are currently not working
With February security patches, TWRP is unable to decrypt data. The only way to be able to access it is removing any lockscreen PIN or password before entering recovery. This will be addressed by the TWRP guys soon.
Instructions:
Before instaling, make sure you are running the latest Open Beta 3 firmware.
If you are unencrypted take a full backup of all your data, because this ROM enforces encryption and so you will have to format your phone.
If you are encrypted and running an AOSP ROM (8.0 or newer) you're fine. If you come from OOS (both Nougat and Oreo) take a full backup of all your data as there's currently not way to change masterkey without formatting, sorry you should be able to go ahead and flash without formatting the internal storage, just make sure to remove any screen lock before switching ROM.
Download the latest build and GApps (both links are below).
Reboot to a custom recovery (latest unified codeworkx's build works perfectly and supports masterkey3 encryption).
If you are coming from any other ROM (even LineageOS 15.0 or 15.1) wiping /data is strongly recommended
Flash the latest build and GApps.
If you want root, flash it afterwards. If you plan to use Magisk, let the first boot happen and flash it later!
Reboot and enjoy :good:
Downloads:
ROM: lineage-15.1-20180216-UNOFFICIAL-kylothow-dumpling.zip
Google Apps: OpenGapps 8.1 (UNOFFICIAL)
Reporting bugs:
Grab a logcat right after the problem has occurred (please include at least a few pages of the log, not just the last few lines, unless you know what you're doing).
If it is a random reboot, grab /proc/last_kmsg (do not bother getting a logcat unless you can get it just before the reboot, a logcat after a reboot is useless).
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log (only applies to SELinux enforcing builds).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Credits:
This is a very important note: I am NOT the original developer of the device trees I'm using. Despite I do my best to fix bugs, improve security, stabilty and the performance of the ROM, it's not thanks to me that this is up and running now.
Please, be sure to thank and donate to the developers behind the device trees.
Huge thanks and credits to the NastyAndroidDevs team (https://github.com/NastyAndroidDevs).
@amartinz: https://github.com/amartinz
@codeworkx: https://github.com/codeworkx
@jrizzoli: https://github.com/jrizzoli
@jumoog: https://github.com/jumoog
Sources:
Device Trees (Reference): LineageOS
Kernel Tree (Reference): LineageOS
Manifest (Reference): NastyAndroidDevs
Device Trees (Custom): EvilDumplings
Kernel Tree (Custom): EvilDumplings
Manifest (Custom): EvilDumplings
Announcements/News:
20 December 2017:
The official LineageOS 15.1 dumpling and cheeseburger device trees are being uploaded on LineageOS' official GitHub account.
31 December 2017:
The fist working unofficial LineageOS 15.1 builds are going live
I made all my changes to NastyAndroidDevs' sources public. See the "Sources" section in the OP.
Thanks
kylothow said:
mine
Click to expand...
Click to collapse
Thnks for your hardwork and time. ?
Thanks:good:
downloading
Will you become the official maintainer for lineage OS for the oneplus 5t in the future?
Colday96 said:
Will you become the official maintainer for lineage OS for the oneplus 5t in the future?
Click to expand...
Click to collapse
As I said in the OP, I'm not the developer behind the device trees, it's all thanks to the NastyAndroidDevs (with pretty known names, if you know CyanogenMod/Lineage) who are unifying the OnePlus 5 and 5T sources (with a common tree with most stuff); it's likely one or more of them will maintain the device.
good morning first of all thanks for putting the ROM looks very good pinta.queria know if facial recognition works to unlock with the face. Thanks and greetings
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
Great! It's finally coming to op5t
This is great news. Will we get a LOS 14.1 build then too? LOS 15 is still missing a lot of features unfortunately. It would be nice to have LOS 14.1 until things like the privacy manager and such get incorporated into LOS 15.
Nice to see this here, even if some basic features are still missing.
YAAAAASSS
CommanderROR said:
Nice to see this here, even if some basic features are still missing.
Click to expand...
Click to collapse
The biggest one is camera.
I think I should be able to fix Camera and NFC soon...
Great!
Thanks for your hard work on this.
I'd love an aosp rom on the BEA5T!!
I have a problem, when i flash the rom on twrp ive got error 7: "Rom is for dumpling, your device is: OnePlus 5T".
WTF?!
Kookitza said:
I have a problem, when i flash the rom on twrp ive got error 7: "Rom is for dumpling, your device is: OnePlus 5T".
WTF?!
Click to expand...
Click to collapse
That's because in device tree, ro.product.device property has been set as "dumpling", @kylothow , perhaps, it should be set to "OnePlus5T", the value that TWRP reads from device when the assert is checked while flashing.
EDIT:
In device tree, file BoardConfig.mk:
Code:
TARGET_OTA_ASSERT_DEVICE := [B]dumpling[/B]
...I get a little annoyed because not unified criteria about naming OP5T.
BitOBSessiOn said:
That's because in device tree, ro.product.device property has been set as "dumpling", perhaps, it should set to "OnePlus5T", the value that TWRP reads from device when the assert is checked while flashing.
Click to expand...
Click to collapse
This is something that we can change on build.prop or we should wait for the dev?
Kookitza said:
This is something that we can change on build.prop or we should wait for the dev?
Click to expand...
Click to collapse
You can unzip (or use something like mc...), edit the flashing script (META-INF/com/google/android/updater-script) delete the first two lines (assert...), repack/save zip, and try again...
BitOBSessiOn said:
You can unzip (or use something like mc...), edit the flashing script (META-INF/com/google/android/updater-script) delete the first two lines (assert...), repack/save zip, and try again...
Click to expand...
Click to collapse
Can you upload the right file (Updater-script), cause i think i messed it :/

[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

Categories

Resources