robi101012981
Senior Member
Because in this world it exists multiple countries, not only China
Because in this world it exists multiple countries, not only China
Alright, so what I did for theThanks for the great work!
I still have a question though, as the two repos(device tree and vendor) are removed, is there any way to create the device tree myself?(I was thinking of utilizing the files Sony provided on openxperiadev but I don't know where to start since I'm pretty much a complete noob to this) Or where should I start if I were to port a Lineage based rom?
Thanks in advance
device
and vendor
repos, is create a sony.xml file under ./local_manifests and set the contents to<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github-sony" fetch="https://github.com/" />
<project path="device/sony/edo-comon" name="Mirenk/android_device_sony_edo-common" groups="device" remote="github-sony" revision="lineage-18.1" />
<project path="device/sony/pdx206" name="Mirenk/android_device_sony_pdx206" groups="device" remote="github-sony" revision="lineage-18.1" />
<project path="vendor/sony/pdx206" name="hellobbn/android_vendor_sony_pdx203" groups="vendor" remote="github-sony" revision="lineage-18.1" />
</manifest>
vendor
is coming from a PDX203 repo (which is the Xperia 1 II), so it'll need a good number of modifications to work for our phone (PDX206). I've done a bunch of massaging to it, but have not had much luck grabbing the required files from the phone with extract-files.sh
yet...proprietary-files.txt
and looking for refs in pdx206-vendor.mk
, which is just a copy of pdx203-vendor.mk
that i did a sed s/203/206/g
on) for a proper build from an adb shell
and grab them and place them in the proper dirs by hand. I'll create a fork on my GH and push my mods later on today in case it's of any help to you.I thought about porting the pdx203 device tree since those two devices share a large portion pf hardware but I was doubtful it would be as simple as doing a literal find&substitute from 203 to 206 lol, at least more work has to be done to adapt for the differences between the two, for instance the 120hz display. I really appreciate your answer as it proves the concept is somewhat workable.Alright, so what I did for thedevice
andvendor
repos, is create a sony.xml file under ./local_manifests and set the contents to
XML:<?xml version="1.0" encoding="UTF-8"?> <manifest> <remote name="github-sony" fetch="https://github.com/" /> <project path="device/sony/edo-comon" name="Mirenk/android_device_sony_edo-common" groups="device" remote="github-sony" revision="lineage-18.1" /> <project path="device/sony/pdx206" name="Mirenk/android_device_sony_pdx206" groups="device" remote="github-sony" revision="lineage-18.1" /> <project path="vendor/sony/pdx206" name="hellobbn/android_vendor_sony_pdx203" groups="vendor" remote="github-sony" revision="lineage-18.1" /> </manifest>
You'll notice that thevendor
is coming from a PDX203 repo (which is the Xperia 1 II), so it'll need a good number of modifications to work for our phone (PDX206). I've done a bunch of massaging to it, but have not had much luck grabbing the required files from the phone withextract-files.sh
yet...
My next tact is to find all the files that I think it needs (scrapingproprietary-files.txt
and looking for refs inpdx206-vendor.mk
, which is just a copy ofpdx203-vendor.mk
that i did ased s/203/206/g
on) for a proper build from anadb shell
and grab them and place them in the proper dirs by hand. I'll create a fork on my GH and push my mods later on today in case it's of any help to you.
I thought about porting the pdx203 device tree since those two devices share a large portion pf hardware but I was doubtful it would be as simple as doing a literal find&substitute from 203 to 206 lol, at least more work has to be done to adapt for the differences between the two, for instance the 120hz display. I really appreciate your answer as it proves the concept is somewhat workable.
Meanwhile I accidentally found the previous maintainer (EggOxygen) when searching on another forum (Coolapk) and had a nice conversation with him and learned the whole edo platform thing. That surely cleared things up.
Anyways I saw the new repo on your GH page. It seemed to be completed and ready for use. Can I compile with this or does I require any furthur modifications? Or is there anything I can do to help improve it? I would be more than happy to contribute, as soom as I get the grasp of all this![]()
Oh I see. I checked yesturday and the repo by Mirenk wasn't there. It's still nice that someone took the effort for us though.Oh, these are not my repos. I just got a link from someone else on these boards, which I used to fill in some of the dirs.
I'll fork and update them as soon as I have something to contribute.
Read the post again, for LTE you need to boot to stock firmware before flashing the ROM otherwise it will not work.Alright I flashed Pixel Experience and it works well and looks great but I don't have LTE connectivity anymore
Please help!
The post talks about Voice Over LTE, not LTE proper! And what does it actually mean to boot to stock? Boot before the "flash product.img" step?! Please clarify, thank you.Read the post again, for LTE you need to boot to stock firmware before flashing the ROM otherwise it will not work.
LineageOS 18.1 - Android 11 - Vendor 11
MEGA (20210316 New Update)
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
// reboot to fastbootd
fastboot reboot fastboot
// flash it
fastboot set_active a
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
// earse userdata
fastboot erase userdata
RROS is more feature rich, but has a higher overhead so it depends on what you value. For my case, RR lasts me plenty long and I love having features so its my go to.
Alright, so what I did for theThanks for the great work!
I still have a question though, as the two repos(device tree and vendor) are removed, is there any way to create the device tree myself?(I was thinking of utilizing the files Sony provided on openxperiadev but I don't know where to start since I'm pretty much a complete noob to this) Or where should I start if I were to port a Lineage based rom?
Thanks in advance
device
and vendor
repos, is create a sony.xml file under ./local_manifests and set the contents to<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github-sony" fetch="https://github.com/" />
<project path="device/sony/edo-comon" name="Mirenk/android_device_sony_edo-common" groups="device" remote="github-sony" revision="lineage-18.1" />
<project path="device/sony/pdx206" name="Mirenk/android_device_sony_pdx206" groups="device" remote="github-sony" revision="lineage-18.1" />
<project path="vendor/sony/pdx206" name="hellobbn/android_vendor_sony_pdx203" groups="vendor" remote="github-sony" revision="lineage-18.1" />
</manifest>
vendor
is coming from a PDX203 repo (which is the Xperia 1 II), so it'll need a good number of modifications to work for our phone (PDX206). I've done a bunch of massaging to it, but have not had much luck grabbing the required files from the phone with extract-files.sh
yet...proprietary-files.txt
and looking for refs in pdx206-vendor.mk
, which is just a copy of pdx203-vendor.mk
that i did a sed s/203/206/g
on) for a proper build from an adb shell
and grab them and place them in the proper dirs by hand. I'll create a fork on my GH and push my mods later on today in case it's of any help to you.I thought about porting the pdx203 device tree since those two devices share a large portion pf hardware but I was doubtful it would be as simple as doing a literal find&substitute from 203 to 206 lol, at least more work has to be done to adapt for the differences between the two, for instance the 120hz display. I really appreciate your answer as it proves the concept is somewhat workable.
Meanwhile I accidentally found the previous maintainer (EggOxygen) when searching on another forum (Coolapk) and had a nice conversation with him and learned the whole edo platform thing. That surely cleared things up.
Anyways I saw the new repo on your GH page. It seemed to be completed and ready for use. Can I compile with this or does I require any furthur modifications? Or is there anything I can do to help improve it? I would be more than happy to contribute, as soom as I get the grasp of all this![]()