Database Users

OxygenOS is now open source

OnePlus released the source code of OOS on github. Some nice news.
https://github.com/OnePlusOSS

Hmm, interesting news, thank for info :good:

This is badass!

Great news indeed.
Let's wait for an OPX device tree and vendor blobs

The github page has a 6.0.1 branch only.
Does this mean that this is a build for the oneplus 2 only?
Or does this also mean that devs can now build a 6.0.1 based oxygen os 3 rom for oneplus x as well using this before oneplus themselves do it??

Had a closer look... It just looks like it'll build AOSP... Not O2...

Ivtake the previous post back. This is awesome! We just need to get a device tree working and we can produce an unofficial port!

Now the path clears to custom oxygenOs:highfive:
Also it may mean timely access to sources, if we ever get mm

Unfortunately , I was right earlier... It is not open source O2

@crian RJDTWO is right. Confirmed by Helen yesterday. Can you change the title, please.

Sources

I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890

Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...

rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.

I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom

rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!

rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.

Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone

rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know

Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good

rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:

Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you

any news @rrvuhpg ?

Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.

rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !

[ROM][XT16xx][7.1.0][CyanMod 14.1 [MotoG4 / G4 Plus] - Where are the BSP files?

Hello again,
Again I post here because I am denied posting in the correct spot. I suppose this silly denial will end, eventually.
I have a question for @Silesh.Nair :
In the dev thread, you tell somebody that he can build CM14.1 from source himself, using that guide:
http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
In a further post, you seem to indicate that the Moto G4 Plus build is obtained direct from the CM source repo.
I found that github repo for CM on the moto G4: https://github.com/CyanogenMod/android_device_motorola_athene
Unfortunately, the latest tag is marked CM 13 ... and there is nowhere to find the BSP files for CM 14.1.
Now, since it seems quite evident to you, but not at all for me, could you please kindly tell us where we can obtain the BSP files (device tree, vendor, kernel) for CM14.1 - Athene?
Thank you for your understanding my confusion.

You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.

Thank you
Silesh.Nair said:
You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.
Click to expand...
Click to collapse
Thank you for this snippet of information. I will look further into it.
In the world of embedded systems, when you have a generic operating system that can be used with many different hardware targets, a Board Support Package ("BSP") is the set of files that are required to build the generic OS on a specific target. For example here the BSP is all the files that are specific for the Moto G4/Plus (e.g. device tree, vendor, kernel), once you have a generic CM 14.1 distribution to start with. "BSP" refers to all the target-specific files that would not be the same on another target (i.e. a different phone).
I think this nomenclature is quite appropriate for the subject at hand.

[REFERENCE]Port any P Preview images into semi-GSI

This thread described the main steps to port a P Preview image into semi-GSI .This is only a reference that points out the key files you may need to deal with, but not a step to step guide.Also I can only lead you to make it boot,and I'm not promising anything.
Things you need to prepare:
1.An Android device with official / unofficial 8.1 Treble support and a PC.
2.P DP3 semi-GSI image(most OEM P are working with DP3)
3.A *Qualcomm OEM P Preview image you want to port.
4.Better have a recent Android kitchen.
*Seems that there's only Qualcomm based devices received official P Preview builds. I'm not sure if someone has early access to P images for Kirin processors (e.g. for Huawei Mate 10) or Exynos.
In theory ,P images can be ported between chipsets from the same vendor.(If anyone have these images feel free to share it)
Also you need to prepare for (in case)bricks,if something goes wrong.
So let's start.
Unpack P semiGSI and the ROM you want to port.
*the lib&lib64 below means there are to files you need to replace,one in lib and one in lib64 folder.
Replace /system/lib&lib64/libselinux.so from semiGSI to your port.
Look for a txt file start with ld.config in your /system/etc of port image, then replace it with /system/etc/ld.configs.txt from semiGSI.
Remove /system/etc/permissions/qti-permissions.jar
Modify /system/etc/prop.default to disable adb secure and enable all debug props for debugging.
Unpack /vendor from port, try to find out services added by OEM in manifest.xml.
The manifest can be in /vendor or /vendor/etc/vintf
Pick out all /vendor HALs related to services you found in manifest.
Basically they are located in:
/vendor/bin/hw
/vendor/etc/init
/vendor/lib&lib64/
/vendor/lib&lib64/hw
Also look for some additional files related to OEM rom.(framework, overlays etc.)
Then pack your /system into img.
Flash 8.1 vendor & P semi-GSI boot & vendor patches.
Flash your port.
Add all additional thing you found in vendor.
You need to modify your device's manifest.xml and add OEM related.
Flash FBE Disabler and permissiver to disable FBE and SELinux.
Format /data ,push adb keys into system for debug
& reboot.
If you're lucky then you can get into bootanimation.If not, try to check everything.
Use adb logcat >logcat.txt and get logs.
Open the log, search 'died' and you will get to lines near system crash. Here you need some ROM porting skills,try to find out what's going wrong.

Reserved

Some frequently bug's solutions:
'dumplicate permission : XXX'
Find the XXX permission in files in /system/etc/permissions . Delete lines for that permission.
'fail to make lockscreen ready'
Add libpuresoftkeymasterdevice.so from P semi GSI to your /system.
Reboot or black screen after enter system
(Most SDM845 ports)
Replace
/system/bin/surfaceflinger
/system/lib&lib64/libsurfaceflinger.so and libtimestats_pronto.so

Great job, OP. My question is, does this mean that in the future we may be able to trebelize most, if not all, OEM roms?

dustmalik said:
Great job, OP. My question is, does this mean that in the future we may be able to trebelize most, if not all, OEM roms?
Click to expand...
Click to collapse
The answer is ,'yes it should be'.In theory ,ported sGSI should work on the same platform ,e.g. Qcom sGSI,Exynos sGSI.But these OEM roms usually intend to specific hardware, so there may always bugs exist.As we know developers of O GSIs did a lot of hacks ,try to enable the maximum compatibility.But porting makes this not possible cuz no source code.
Also, the port I do is only on OEM without too much modification to original P, what about Samsung with their own hals and Huawei EMUI with the *** OEMINFO partition ? These roms are not possible to port in the near past,I think nor in the near future.

The problem with exynos device that is with s9+ we dont have android 8.1 vendor image.

Note: Tested not working on latest P miui of MI MIX 2S .
EDIT: Because of SELinux

fxsheep said:
Note: Tested not working on latest P miui of MI MIX 2S .
EDIT: Because of SELinux
Click to expand...
Click to collapse
did you manage to boot a miui10 GSI?

meltbanana said:
did you manage to boot a miui10 GSI?
Click to expand...
Click to collapse
No

fxsheep said:
Note: Tested not working on latest P miui of MI MIX 2S .
EDIT: Because of SELinux
Click to expand...
Click to collapse
Do you plan on porting the new HydrogenOS Beta 1 android pie for OnePlus 6?
https://forum.xda-developers.com/oneplus-6/how-to/android-pie-9-0-public-beta-version-t3829394

Surprising Update : I got leaked EMUI 9 rom of Huawei Mate 20 (powered by Kirin 980) and followed this method on a Qualcomm Trebled device. What surprised me is that I already got bootanimation ,end up with the same SELinux error when I port MIX2S MIUI P.
This may means that in the future we can even port roms between platforms ,and make real GSI.

fxsheep said:
Surprising Update : I got leaked EMUI 9 rom of Huawei Mate 20 (powered by Kirin 980) and followed this method on a Qualcomm Trebled device. What surprised me is that I already got bootanimation ,end up with the same SELinux error when I port MIX2S MIUI P.
This may means that in the future we can even port roms between platforms ,and make real GSI.
Click to expand...
Click to collapse
If anyone can give me the way to get this firmware https://www.xda-developers.com/huawei-mate-10-pro-android-p/amp/
Then I can prove it

fxsheep said:
If anyone can give me the way to get this firmware https://www.xda-developers.com/huawei-mate-10-pro-android-p/amp/
Then I can prove it
Click to expand...
Click to collapse
I think this isn't the one you want. But I hope it will help you. BTW, can you boot it on HUAWEI vndk26 devices?
http://update.hicloud.com:8180/TDS/...50/g1750/v152588/f1/full/update_full_base.zip

麦麦观 said:
I think this isn't the one you want. But I hope it will help you. BTW, can you boot it on HUAWEI vndk26 devices?
http://update.hicloud.com:8180/TDS/...50/g1750/v152588/f1/full/update_full_base.zip
Click to expand...
Click to collapse
This one isn't.In theory it can boot on vndk26 but lack selinux fixes.I don't have treble vndk26 device though.

fxsheep said:
Surprising Update : I got leaked EMUI 9 rom of Huawei Mate 20 (powered by Kirin 980) and followed this method on a Qualcomm Trebled device. What surprised me is that I already got bootanimation ,end up with the same SELinux error when I port MIX2S MIUI P.
This may means that in the future we can even port roms between platforms ,and make real GSI.
Click to expand...
Click to collapse
Do you think is it possible to port oppo color os into gsi ?

Update:This guide does not support P Release versions.i.e.If you port any P roms which is marked as "release" not "beta" by OEM then probably this won't work.It can only boot on 9.0 vendor.

Better is make script same as my cd C:\Users\MAREK\Desktop\BASE\system
echo FAZA 1 ld.config.txt
pause
COPY C:\Users\MAREK\Desktop\BASE\system\etc\ld.config.txt C:\Users\MAREK\Desktop\skrypt\BASE\system\etc\
pause
echo FAZA 2 libselinux.so
pause
COPY C:\Users\MAREK\Desktop\BASE\system\lib\libselinux.so C:\Users\MAREK\Desktop\skrypt\BASE\system\lib\
pause
COPY C:\Users\MAREK\Desktop\BASE\system\lib64\libselinux.so C:\Users\MAREK\Desktop\skrypt\BASE\system\lib64\
pause

Treble_for_klte

Guys why there is no developer here working on a treble project enable tool to our phone
Since we have a stable oreo rom and have all the libs and files in vendor to make oreo boot successfully without bugs there is a possible way to make our klte project treble i'm sure >
but i can't lonely make this project alive we need to work with our devs to make this happens
since the creation of vendor partition is not that hard thing but i'm didn't know anything about editing the kernel and the device tree to boot from new vendor partition.
Thank you if you reach that point of the thread

@phhusson i really appreciate your work for the project treble forum
Can you help me with making this thing happens ?

mhmdalsfaf said:
Guys why there is no developer here working on a treble project enable tool to our phone
Since we have a stable oreo rom and have all the libs and files in vendor to make oreo boot successfully without bugs there is a possible way to make our klte project treble i'm sure >
but i can't lonely make this project alive we need to work with our devs to make this happens
since the creation of vendor partition is not that hard thing but i'm didn't know anything about editing the kernel and the device tree to boot from new vendor partition.
Thank you if you reach that point of the thread
Click to expand...
Click to collapse
treble is not only bound to partitioning , its also a kernel version as well which we not even near it , the required kernel version is 3.18 (as the bare-minimum ) and up , the S5 is stuck at 3.4.113 so no treble for the S5.