Database Develop

[i9001]Q about porting B2G

Hey guys!
Im new to rom development/porting but I have some experiences in development/linux in general, so I tried to port B2G to my i9001 using
h t t p s:// wiki.mozilla.org/B2G/Porting (I really like the idea of B2G).
I ran into some questions during the process:
Clone B2G repo,Create local backup of the original Android system - piece of cake
Add new device in config.sh
seems not to hard
default.xml
i took the s2 config and changed simply
<project path="device/samsung/galaxys2" name="android-device-galaxys2" remote="b2g" revision="master" />
<project path="hardware/broadcom/wlan" name="platform/hardware/broadcom/wlan" />
to
<project path="device/samsung/galaxysplus" name="android-device-galaxysplus" remote="b2g" revision="master" />
Create configuration tree for new device
I found most files on arcos github-page.
h t t p s://github.com/arco/android_device_samsung_ariesve
I couldnt figure out where to get the sources for the kernel (or get a working boot.img for this project).
The canges in the init.rc (init.qcom.rc I guess) are pretty self-explanatory. Editing the flash.sh is also pretty straight, since s2 tools should work here (I hope).
I hope somebody can help me here

Hey I figured out that Id only need a boot.img that would work with arcos files so I extracted mine (CM9 alpha 5). Seems to work but Im really not sure if I should flash it. Anything else I need to do? Does this affect my recovery? Any help would be great!
Resource:
h t t p://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

Could somebody please move this to the i9001 dev-section? I dont want to spam 10 times just to be able to repost there.

i need 5 more messages so ill spam here

spam spam spam

asdasd

happy spamming

last

[ROM] [WIP] Unofficial CM12.1 for the p880

Hey guys
I guess you already know the drill It's more-less the same as we did on CM11, but Adam77Root isn't actively developing for the device anymore and also Demetris isn't working on this project anymore. I am pretty busy lately myself, which is why you shouldn't expect any miracles soon.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, and we will most likely merge it happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let us know about it before you release it and give credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
You tell me
Possibly more
Working:
Everything else ​
Now, the most important part:
Download
All builds can be found on my goo.im account:
CM12
CM12.1
Please note that goo.im is currently having issues, which is why the latest builds are available from the devDB downloads tab.
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[ROM] [WIP] Unofficial CM12.1 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf, Adam77Root, sunsettrack4
Source Code: https://github.com/P880-dev/android_kernel_lge_x3/tree/cm-12.0
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-11-09
Last Updated 2015-04-06

Reserved
I have used the following local_manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- p880 specific stuff -->
<project name="P880-dev/android_device_lge_p880" path="device/lge/p880" remote="github" revision="cm-12.0" />
<project name="P880-dev/android_kernel_lge_x3" path="kernel/lge/x3" remote="github" revision="cm-12.0" />
<project path="vendor/lge" name="P880-dev/proprietary_vendor_lge" revision="cm-12.0" />
<remove-project path="device/asus/fugu" name="device/asus/fugu" groups="device,fugu" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/fugu-kernel" name="device/asus/fugu-kernel" groups="device,fugu" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/grouper" name="device/asus/grouper" groups="device,grouper" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/tilapia" name="device/asus/tilapia" groups="device,grouper" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/htc/flounder" name="device/htc/flounder" groups="device,flounder" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/htc/flounder-kernel" name="device/htc/flounder-kernel" groups="device,flounder" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/moto/shamu" name="device/moto/shamu" groups="device,shamu" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/moto/shamu-kernel" name="device/moto/shamu-kernel" groups="device,shamu" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/samsung/manta" name="device/samsung/manta" groups="device,manta" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
</manifest>
if you run into some errors, just remove the according "remove-project" line and you should be fine

Thank you!
Thank you @laufersteppenwolf, @Demetris for all your efforts! I'll build it later, and try to help you with logs and anything else i can do, as much as i can! Keep up, mates, brilliant job!

Thanks man! I will go download sources now!

SurfaceFlinger problem again...
SurfaceFlinger will initialize failed with our old blobs on the hacked framework native,and it will crash with n7 blobs as well.
edited:
n7 2012 factory image leaked.
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz

Tim_Pan said:
SurfaceFlinger problem again...
SurfaceFlinger will initialize failed with our old blobs on the hacked framework native,and it will crash with n7 blobs as well.
edited:
n7 2012 factory image leaked.
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
Click to expand...
Click to collapse
SF issues should be gone, is you've got the latest sources. It was related to SELinux, which is why I completely killed it via kernel for now
Also, I highly doubt that you're gonna have much success using the stock blobs (which is why I'm not even gonna try)

I wil try building when I get home

Any News?

If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.

iSWORD14 said:
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
Click to expand...
Click to collapse
Yeah good idea.

fritzcola said:
Any News?
Click to expand...
Click to collapse
Not really haven't got much free time lately to test...
iSWORD14 said:
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
Click to expand...
Click to collapse
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.

laufersteppenwolf said:
Not really haven't got much free time lately to test...
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
Click to expand...
Click to collapse
No Problem
Keep up the great work.
Im sure you are going to fix it soon.:good:

laufersteppenwolf said:
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
Click to expand...
Click to collapse
You can put a warning next to the link. I think someone did something similar with an HTC sense port IIRC.
Anyway, if you prefer not to share it in public, I'd appreciate it if you can PM it to me.

If anyone get a bootable Build, can he upload it!!
Thx

fritzcola said:
If anyone get a bootable Build, can he upload it!!
Thx
Click to expand...
Click to collapse
Help us to achieve that

If i could of course i would but im sure i cant help you. My skills are very little

iSWORD14 said:
You can put a warning next to the link. I think someone did something similar with an HTC sense port IIRC.
Anyway, if you prefer not to share it in public, I'd appreciate it if you can PM it to me.
Click to expand...
Click to collapse
Well, some may do that, but I am not like that I have seen just too many things happen to phones just because people didn't read and just downloaded something with the name of their device on it.
fritzcola said:
If anyone get a bootable Build, can he upload it!!
Thx
Click to expand...
Click to collapse
The same thing as last time is going to happen: As soon as we've got a halfway working build, it will be released. Until then, there won't be a public release.
And I also ask anyone to please not publically post a build until it doesn't properly work (and by properly I mean the important things like network, audio, ... )
Alright, a general update on the situation:
SF issues are gone and we've got a boonanimation. But ATM, we are bootlooping due to audio issues.
The problem is, I have no idea what exactly is causing the issues, as the logs do not specify it (it's literally being shown as <unknown>). I was hoping that fixing the AudioWrappers would at least resolve the bootloop, but no dice.
If you want to look into it yourself, logcat and a strace from mediaserver is located HERE
Thanks to @LGaljo for the logs

News?

Busaton said:
News?
Click to expand...
Click to collapse
Dont think so

There are no news, because we keep everything private and deliberately not telling anything about the progress that have been made. :beer:

Can you guess what is this?

328 <project path="frameworks/opt/telephony" name="CyanogenMod/android_frameworks_opt_telephony" groups="pdk" />
312 <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" groups="pdk" /
178 <project path="external/libexif" name="platform/external/libexif" groups="pdk-cw-fs,pdk-fs" remote="aosp" />
what is this? More "advanced" users will know

XTutorials said:
328 <project path="frameworks/opt/telephony" name="CyanogenMod/android_frameworks_opt_telephony" groups="pdk" />
312 <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" groups="pdk" /
178 <project path="external/libexif" name="platform/external/libexif" groups="pdk-cw-fs,pdk-fs" remote="aosp" />
what is this? More "advanced" users will know
Click to expand...
Click to collapse
Are you trying to build LineageOS/Cyanogenmod ? I guess you have errors where projects are conflicting.

For me, Problem was caused because XePeleatos external/libexif and 2 others you mentioned had same path= as lineageos's manifest. It helped when i removed those 3 lines from .repo/manifest.xml

Audriuskins said:
Are you trying to build LineageOS/Cyanogenmod ? I guess you have errors where projects are conflicting.
Click to expand...
Click to collapse
Yes, I am in state of building a custom rom, had some "same path" error at the .repo/manifest.xml file

Vika__ said:
For me, Problem was caused because XePeleatos external/libexif and 2 others you mentioned had same path= as lineageos's manifest. It helped when i removed those 3 lines from .repo/manifest.xml
Click to expand...
Click to collapse
lol, had same isssue, have you build a custom rom?

XTutorials said:
lol, had same isssue, have you build a custom rom?
Click to expand...
Click to collapse
I build just for my own fun

Vika__ said:
I build just for my own fun
Click to expand...
Click to collapse
And you succeded?

XTutorials said:
And you succeded?
Click to expand...
Click to collapse
I left lineage 14 since i trust its development on people who know whats doing and i moved to lineage 13. First build atm going and i don't think it's gonna boot

[MODULE][MAGISK] Google Photos Unlimited FULL RESOLUTION Upload

THIS MODULE ENABLES UNLIMITED FULL RESOLUTION UPLOAD IN GOOGLE PHOTOS
REPORTS SAY IT DOESN'T WORK
Update 3 – Uploads May Still Count Against Drive Storage
We’re hearing reports that this trick was discovered by the team over at OpenGapps a few months back and was quietly patched by Google already. In that case, applying this trick will still result in uploaded photos to apply against your Google Drive storage (ie. it doesn’t work). We haven’t confirmed this ourselves, but if/when we do we will update the above tutorial.
Click to expand...
Click to collapse
Update 4 – Google Photos Unlimited Storage Not Working, Pixel Wallpapers Still Work
I have confirmed that photos uploaded in “original quality” using this trick still count against your Drive storage. My Drive shows that I uploaded 0.2GBs of photos and videos from yesterday. This means that the trick was patched, likely when it was discovered by the people over at OpenGapps. It’s strange that this trick somehow still triggers Google Photos into showing you the original quality onboarding message, though.
Click to expand...
Click to collapse
Code:
Thread will be updated to look nicer. Atm I was in a hurry to post this for everyone to use
FLASH IN RECOVERY, FLASHING THROUGH MAGISK MANAGER ISN'T WORKING ​

What about photos already uploaded?
Inviato dal mio Nexus 6P utilizzando Tapatalk
---------- Post added at 10:33 ---------- Previous post was at 10:28 ----------
dariomrk said:
THIS MODULE ENABLES UNLIMITED FULL RESOLUTION UPLOAD IN GOOGLE PHOTOS
Code:
Thread will be updated to look nicer. Atm I was in a hurry to post this for everyone to use
Click to expand...
Click to collapse
Install fails on Magisk Manager 5.3.0 (on MagiskSu v14)
Inviato dal mio Nexus 6P utilizzando Tapatalk

Helpful module will try to install this on my S6
Sent from my SM-G920F using Tapatalk

CyberZeus1977 said:
What about photos already uploaded?
Inviato dal mio Nexus 6P utilizzando Tapatalk
---------- Post added at 10:33 ---------- Previous post was at 10:28 ----------
THIS MODULE ENABLES UNLIMITED FULL RESOLUTION UPLOAD IN GOOGLE PHOTOS
Install fails on Magisk Manager 5.3.0 (on MagiskSu v14)
Inviato dal mio Nexus 6P utilizzando Tapatalk
Click to expand...
Click to collapse
Works if you Install it via Recovery.

Does this module makes every app think that my phone is Pixel?

Shished said:
Does this module makes every app think that my phone is Pixel?
Click to expand...
Click to collapse
Yes... Could anybody make a module that only adds the nexus.xml?

Simeonico said:
Yes... Could anybody make a module that only adds the nexus.xml?
Click to expand...
Click to collapse
There you go
https://drive.google.com/open?id=0B35Q-_-S5yi-SENWYkNyTU1JX3M

Does this module edit build.prop and change device name to Pixel 2 XL ?
Sent from my Nexus 6 using XDA Labs

StaticBlaze said:
There you go
https://drive.google.com/open?id=0B35Q-_-S5yi-SENWYkNyTU1JX3M
Click to expand...
Click to collapse
Thank. This module works and does not changed the device name.

Edit: I will upload my module without Pixel 2 XL build.prop later as an alternative (just the nexus.xml)

dariomrk said:
Edit: I will upload my module without Pixel 2 XL build.prop later as an alternative (just the nexus.xml)
Click to expand...
Click to collapse
Thanks for the awesome module! I was able to modify the system.prop, in the common folder, to match my device. Seemed to do the trick.

Will not work!
https://www.xda-developers.com/enable-google-photos-unlimited-storage/amp/
Update 3 – Uploads May Still Count Against Drive Storage
We’re hearing reports that this trick was discovered by the team over at OpenGapps a few months back and was quietly patched by Google already. In that case, applying this trick will still result in uploaded photos to apply against your Google Drive storage (ie. it doesn’t work). We haven’t confirmed this ourselves, but if/when we do we will update the above tutorial.
Click to expand...
Click to collapse
Update 4 – Google Photos Unlimited Storage Not Working, Pixel Wallpapers Still Work
I have confirmed that photos uploaded in “original quality” using this trick still count against your Drive storage. My Drive shows that I uploaded 0.2GBs of photos and videos from yesterday. This means that the trick was patched, likely when it was discovered by the people over at OpenGapps. It’s strange that this trick somehow still triggers Google Photos into showing you the original quality onboarding message, though.
Click to expand...
Click to collapse

zpower said:
Will not work!
https://www.xda-developers.com/enable-google-photos-unlimited-storage/amp/
Click to expand...
Click to collapse
Thanks for the info

Not sure where else to put this, but if you just want the wallpapers, you only need the following in the XML (which I named google_wallpapers_2017.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<config>
<feature name="com.google.android.feature.PIXEL_EXPERIENCE" />
</config>
This is meant for the unlimited Google Photos (now patched, xml named google_unlimited_photos.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<config>
<feature name="com.google.android.apps.photos.NEXUS_PRELOAD" />
<feature name="com.google.android.apps.photos.nexus_preload" />
</config>
You do not need any of this:
Code:
<!-- Enable Zero Touch Provisioning support for 2016 and newer Nexus devices. -->
<feature name="com.google.android.feature.ZERO_TOUCH" />
<!-- Allow Google unbundled tethering entitlement app in background -->
<allow-in-power-save package="com.google.android.tetheringentitlement" />
<!-- Allow ssr detector service in background -->
<allow-in-power-save package="com.google.SSRestartDetector" />
<!-- Allow ramdump uploader service in background -->
<allow-in-power-save package="com.android.ramdump" />
<!-- These are telephony components that need to run in the background -->
<allow-in-power-save package="com.qualcomm.atfwd" />
<allow-in-power-save package="com.qualcomm.embms" />
<allow-in-power-save package="com.qualcomm.qti.telephonyservice" />
<allow-in-power-save package="com.qulacomm.qcrilmsgtunnel" />
<allow-in-power-save package="com.qualcomm.qti.ims" />
<allow-in-power-save package="com.qualcomm.qti.radioconfiginterface" />

i will try it later but let me thanx, it might be the best module for me if it works

It works for me, just flashed through twrp nothing else

StaticBlaze said:
There you go
https://drive.google.com/open?id=0B35Q-_-S5yi-SENWYkNyTU1JX3M
Click to expand...
Click to collapse
Thank you!!!!!
Enviado desde mi ONEPLUS A5000 mediante Tapatalk

chazarss said:
It works for me, just flashed through twrp nothing else
Click to expand...
Click to collapse
Read the article i post above

SpasilliumNexus said:
Not sure where else to put this, but if you just want the wallpapers, you only need the following in the XML (which I named google_wallpapers_2017.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<config>
<feature name="com.google.android.feature.PIXEL_EXPERIENCE" />
</config>
This is meant for the unlimited Google Photos (now patched, xml named google_unlimited_photos.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<config>
<feature name="com.google.android.apps.photos.NEXUS_PRELOAD" />
<feature name="com.google.android.apps.photos.nexus_preload" />
</config>
You do not need any of this:
Code:
<!-- Enable Zero Touch Provisioning support for 2016 and newer Nexus devices. -->
<feature name="com.google.android.feature.ZERO_TOUCH" />
<!-- Allow Google unbundled tethering entitlement app in background -->
<allow-in-power-save package="com.google.android.tetheringentitlement" />
<!-- Allow ssr detector service in background -->
<allow-in-power-save package="com.google.SSRestartDetector" />
<!-- Allow ramdump uploader service in background -->
<allow-in-power-save package="com.android.ramdump" />
<!-- These are telephony components that need to run in the background -->
<allow-in-power-save package="com.qualcomm.atfwd" />
<allow-in-power-save package="com.qualcomm.embms" />
<allow-in-power-save package="com.qualcomm.qti.telephonyservice" />
<allow-in-power-save package="com.qulacomm.qcrilmsgtunnel" />
<allow-in-power-save package="com.qualcomm.qti.ims" />
<allow-in-power-save package="com.qualcomm.qti.radioconfiginterface" />
Click to expand...
Click to collapse
Somebody should make a new thread for a "Pixel Wallpapers Enabler" module.

How to see whether the wallpapers of pixel are enabled or nor???
Sent from my Redmi Note 4 using Tapatalk

[ROM] [Unofficial] Lilly's "Yet another LOS 18.0"

Hello, ladies, gentlemen and non-booleans!
Since I prefer building my own ROMs for various reasons, especially when the device tree source isn't made public, I have now finally gotten a LineageOS 18.0 build together.
"But there's already a build there!"
Fair point, but the sources of the device tree and kernel aren't public anywhere, to my knowleadge.
While I'm nowhere near as much of an open source fanatic as to demand all the source everywhere, it doesn't feel right either.
So since I've got a habit of having my own builds so I myself decide when I get an update, I decided to spin one up and at the same time provide a workaround for others who want to build their own versions.
So, what did I do? Voodoo? Other black magic? No!
I looked at crDroid's Github and the source tree seemed to be largely compatible with the LOS build system customisations.
They seem to often be working pretty closely with LOS build conventions.
They even specifically host a kernel there that has got an Android 11 branch!
And with that, we come to the sources used section:
Sources used:
Xiaomi-common
device
Kernel
So, how would you get your own private builds?
Do a repo sync as normal, then put into
.repo/local_manifests/roomservice.xml the following:
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/tissot" name="crdroidandroid/android_device_xiaomi_xiaomi" remote="github" revision="11.0" />
<project path="kernel/xiaomi/msm8953" name="crdroidandroid/android_kernel_xiaomi_tissot" remote="github" revision="11.0" />
<project path="vendor/xiaomi/" name="crdroidandroid/proprietary_vendor_xiaomi" remote="github" revision="11.0-tissot" />
<project path="device/xiaomi/msm8953-common" name="crdroidandroid/android_device_xiaomi_msm8953-common-tissot" remote="github" revision="11.0" />
</manifest>
Do another sync and you're going to have everything you need downloaded. From there it's the usual procedure for builds.
"So, Lilly, that's all well and good, but why upload yet another LOS build?"
Because I've got itchy fingers and while I'm definetely not qualified myself to improve the device tree myself, you could profit from my addiction to doing builds quite frequently and get the latest feature changes pretty quickly.
Aside from that, I also plan on integrating Opengapps into the builds using their build system plugin. I didn't do it right away because last time there were some errors I couldn't figure out and I wanted a build right now.
Another thing I want to get working is having LuciferKernel preinstalled in the overclocked variant, because that overclock is definitely helping performance in my experience. Keep that in mind before installing. If you've got gripes about overclocking and I get the kernel to work (last in tree compilation resulted in an unbootable kernel) you're going to be stuck on the first vanilla version.
All in all, it's just sharing something what I use and trying to fill a tiny niche.
Do keep in mind that I'm definetely not a complete wizard and not an Android ROM developer. I just about know how to build a ROM and how to manipulate it here and there. I provide no support aside from "this build is borked, could you try again?".
That said, here's the download link:
ROM Downloads - Google Drive
drive.google.com
The first build hasn't been tested yet so do not expect to plug and play. I'm in the process of flashing it as I type this. MAKE BACKUPS!
Right, that should just about cover everything. Cheers!

Update: So far it's not booting and throwing up a couple of errors in the logcat. Hm.
I'll examine it a bit tomorrow.

Another update: Flashed crDroid and the same opengapps I used for my LOS build and now it's failing to boot in a similar manner... Weird.

Another update: It boots without that borked opengapps package.

Here's some proof that it boots successfully!

_I did a derp_
I noticed I had synced LOS 18 instead of 18.1
I just finished syncing the other branch and a new build will follow. Should be directly upgradable.

crdroid is based on Lineage os & since it's identical in many ways it shares many stuff well lineage os maintainer(aka maintainer of Pixel experience) abhinav gupta is handling it there are some stuffs & some (he preferes to open sources after he goes official for his device) that's how it works on last update he did it with pixel experience but since it's likely near dead his primary focus is on Lineage os thus until tissot doesn't recieve official Lineage os 18.1 he won't release his stuff publically
since you are using my stuff i still suggest to wait for him to do release it
Regards

murtaza1326 said:
crdroid is based on Lineage os & since it's identical in many ways it shares many stuff well lineage os maintainer(aka maintainer of Pixel experience) abhinav gupta is handling it there are some stuffs & some (he preferes to open sources after he goes official for his device) that's how it works on last update he did it with pixel experience but since it's likely near dead his primary focus is on Lineage os thus until tissot doesn't recieve official Lineage os 18.1 he won't release his stuff publically
since you are using my stuff i still suggest to wait for him to do release it
Regards
Click to expand...
Click to collapse
I don't quite see why I shouldn't make my own builds. It's not like I'm not being transparent about my intentions or to what extent I can work on a ROM.
It's just that I want to build my own builds and I can't do that when people don't do upload their sources. May I ask what you're getting at?

lillywho said:
I don't quite see why I shouldn't make my own builds. It's not like I'm not being transparent about my intentions or to what extent I can work on a ROM.
It's just that I want to build my own builds and I can't do that when people don't do upload their sources. May I ask what you're getting at?
Click to expand...
Click to collapse
i never said that you should not make your own builds but it device side source stuff take reasonable amount of time & hardwork they put about it
imagine you are one of dt maintainers & you publically share your work & people will use it before even waiting for you & giving you first chance (happens alot here)
thus he does this until they get green flag to do so from source side he won't do it
also if i decided to keep my stuff private literally no rom execept abhinav's & sooti (aosp gsi)
would exist for this device (i bet)
you are free to use any of my trees & stuff & make builds but please don't hop over multiple roms (like a mad person) (happens in our community alot)
there are more rom on telegram built by BBots (but they don't regularly update those)
if this is just a personal build & you are not going to update it in feature just don't share it
thanks & regards

What is the current situation?