Database Develop

[I815/P6800/P6810] CyanogenMod 9 (08/12/2012)

I've started porting CyanogenMod 9 to the Galaxy Tab 7.7. Do not flash this unless you know how to backup your data and especially unless you know how to get back to stock. If you don't already know how to do this, you might want to familiarize yourself with the process now, while the developers try to stablize CM9. I don't have time to help people unbrick their devices, and will not take responsibility for any user bricking their device, you flash this at your own risk.
If you are a developer interested in helping out with the porting effort, please PM me.
Known Issues
HDMI dongle doesn't work
Some USB keyboards aren't working
I815: CDMA and LTE isn't enabled
I815: GPS doesn't work
I815: Autobrightness is broken
Download
Google apps can be found at http://goo.im/gapps
I815 (August 15, 2012): http://goo.im/devs/ohanar/i815/cyanogenmod/cm-9-20120815-NIGHTLY-i815.zip
P6800 (August 15, 2012): http://goo.im/devs/ohanar/p6800/cyanogenmod/cm-9-20120815-NIGHTLY-p6800.zip
P6810 (August 15, 2012): http://goo.im/devs/ohanar/p6810/cyanogenmod/cm-9-20120815-NIGHTLY-p6810.zip
Old
P6810 (DP1, April 4, 2012): http://goo.gl/ANRQx (md5: 2be30aaa4aadcd3065239e16f0ca5247)
P6800 (DP1, April 5, 2012): http://goo.gl/CrwCQ (md5: f333f6aca81e1fb0f08244358e492813)
Flash
Flash from ClockworkMod Recovery, make sure to wipe data/factory reset. No whining if it eats your homework.
Build Instructions
Setup a standard CyanogenMod 9 build environment (there are plenty of tutorials on the web already on how to do this). Then
Add add the following entries to your local manifest
Code:
<project path="device/samsung/XXX"
name="ohanar/android_device_samsung_XXX"
revision="ics"
remote="github" />
<project path="device/samsung/smdk4210-tab"
name="ohanar/android_device_samsung_smdk4210-tab"
revision="ics"
remote="github" />
<project path="kernel/samsung/smdk4210-tab"
name="ohanar/android_kernel_samsung_smdk4210-tab"
revision="ics"
remote="github" />
where you replace XXX with your device (i815, p6200, p6210, p6800, p6810, or t869).
Make sure that your device is running the newest build of CyanogenMod 9 or stock ICS if your device has it.
Make sure your device is plugged in and has debugging enabled.
Run the extract-files script from your particular device tree.
Run vendor/cm/get-prebuilts
Your sources are now ready, to build run
Code:
$ . build/envsetup.sh # this sets up the build environment
$ lunch cm_XXX-userdebug # this selects your device
$ mka bacon # this builds CM
Changelog
08/08/2012
Hopefully remaining wifi issues fixed (wifi hotfix shouldn't be needed anymore)
Wifi tethering enabled (no clue if it works)
08/03/2012
LPM fixed (can now charge while off)
Camera force closes fixed
7/19/2012
P68x0: Autobrightness fixed
Bluetooth fixed (thanks to lowtraxx for pointing out where the issue was)
I815: LTE Modem's massive power drain fixed
7/15/2012
Wifi! -- for real real, not for play play
P6800: SIM Toolkit Support
Hardware-Accelerated Video (Regression in 7/10/2012)
ASOP Charging mode (still not really working)
7/10/2012
smdk4210-tab kernel
I815 build
vibration (regression in Alpha 2)
3g data on P6800 (regression in Alpha 2)
Camera (both front and back)
Regression: Hardware-accelated video (this also means no previews in the Camera)
Regression: LPM
Alpha 2
smdk4210 kernel (common kernel used in the CM9 ports for the i9100, i777, n7000, p6200, p6210, p6800, and p6810)
USB gadget support
Hardware-accelerated video
Rear facing camera (only stills for now)
Better auto brightness (values still need to be tuned)
LPM (charge while off)
Probably other stuff (been a long time since last update)
Regression: Vibrator no longer works, we now get a beep instead
Alpha 1
Upgrade wifi driver to compat-wireless-3.4-rc3-1
GPS hopefully fixed (thanks to Alan Orth)
Data Usage fixed (thanks to Alan Orth + Galaxy Tab 10.1 devs)
DP3.1
Wifi fix that sometimes works
DP3
Torch App (thanks to Alan Orth)
Fixed reboot download
Wifi partially works
Other random bugs caused by building with gcc 4.6 (now using the recommended 4.4)
DP2.1
3G/GSM fix (thanks to poisike)
DP2
Audio works!
DP1.1
Partial fix for autobrightness (gets brighter, doesn't get darker)
Phone like interface is gone
P6800: added GSM libraries, and basic 3g configuration
Credits
aorth -- set up the device tree for the GT-6200 (Tab Plus 3g), has been a great collaborator
poisike -- provided fix for 3g/gsm
teamhacksung -- set up the galaxys2 device tree, which was the basis for my tree

Nice! Hope more developers will join and sync with 6800
Sent from my GT-P6800 using XDA Premium HD app

locerra said:
Hi,
I've started working on porting CM9 to my P6810, and figured I would post here in case there were any other devs interested in assisting me, or working on a P6800 version.
Currently I have gotten to a lockscreen, but that is about it, most hardware still needs to be properly configured.
The sources:
https://github.com/ohanar/android_device_samsung_p6810
https://github.com/ohanar/android_frameworks_base
Click to expand...
Click to collapse
I'm interested in working on a P6800 version. I sent you a PM.

poisike said:
I'm interested in working on a P6800 version. I sent you a PM.
Click to expand...
Click to collapse
I have started on this, as well. Am beginning with the Note port right now. Gotten about as far as you. Please PM me, and we can hopefully collaborate.
Steve

Uh this sounds great!
Count me in for testing, don't have dev abilities.

sk806 said:
I have started on this, as well.
Click to expand...
Click to collapse
Do you have a git repo somewhere? I wouldn't mind looking through what you've done so far.

hurray!
Count me in for testing, don't have dev abilities.
waiting for first booting CM9

Wow great news! I really cant contribute anything aside from ROM testing on a regular basis as long as it does not increase any flash counters

great
great!! i may help,no rommaking experience but programming skills in java, c and android. pm meif want some help.

locerra said:
Hi,
I've started working on porting CM9 to my P6810, and figured I would post here in case there were any other devs interested in assisting me, or working on a P6800 version.
Currently I have gotten to a lockscreen, but that is about it, most hardware still needs to be properly configured.
The sources:
https://github.com/ohanar/android_device_samsung_p6810
https://github.com/ohanar/android_frameworks_base
Click to expand...
Click to collapse
Oh get it soon brothers, This TouchWiz is killing me.... I hate it....

locerra said:
Do you have a git repo somewhere? I wouldn't mind looking through what you've done so far.
Click to expand...
Click to collapse
I don't. Working a bit more on it, then I'll post and send you a link to the ROM...

sk806 said:
I don't. Working a bit more on it, then I'll post and send you a link to the ROM...
Click to expand...
Click to collapse
Ok, well let me know when you have something. In the meantime, I'm seperating out my repo into two: common stuff and P6810 specific ones. I'm rebuilding to make sure that I didn't break anything, but once that is done it should be easier to share work (assuming that all the things that I put in the common repo are indeed common ).

just having a peek at your github, (I have Gt-P6200) there's a typo in ..android_device_samsung_c210-common / c210_base.mk
AUDIO_PACKAGES is misspelled I believe.
nothing huge.

i've got a builbox and can host the nightlies if you want, we already do it for the nook and touchpad (unofficial) builds.
pm me if you're interested.

Its so nice to see the 6810 getting some love. When I first got it and came to the developers forum I was surprised that all the ROMS said 6800 only. I also will gladly help with testing.

I'm also glad to see the P6810 get some attention, especially when it's CM9/ICS.
Happy to help out with testing when you guys are ready

Ill echo the above also - awesome

chrisrotolo said:
just having a peek at your github, (I have Gt-P6200) there's a typo in ..android_device_samsung_c210-common / c210_base.mk
AUDIO_PACKAGES is misspelled I believe.
nothing huge.
Click to expand...
Click to collapse
I'm curious as to how similar the tab 7+ and 7.7 really are. If they are close enough (which my guess is that they are), then that repo could serve for both (although probably not in the present state). Are you thinking of working on CM9 for your tab?

dude this is awesome! i'll take a peek when i get the time and help out if i can.
keep up the good work!

I always say that xda is the place of wonders. Waiting patiently and deeply appreciate it!

[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

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

Lineage OS15

Any news about LOS 15 for Xiaomi Mi Mix2?
https://drive.google.com/file/d/1Xf-ULJcr0UptEutLxUFPDrcoTGVzUm3G/view?usp=sharing

I'm confused, what is that link?

yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
Its Arasthels lineage 15.1 build, does this guy have permission to issue it?

Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.

yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
I wanned to ask as well. Who merged that and who has given the shout of the link. Getting LOS15 indtalled would blow up my f...en brain right on to the ceiling for sure
---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
fbousk said:
Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.
Click to expand...
Click to collapse
Aaaah now I get it. Thank you. We'd better wait on him to say something when he feels it's ready enough.

armsar1978 said:
Any news about LOS 15 for Xiaomi Mi Mix2?
https://drive.google.com/file/d/1Xf-ULJcr0UptEutLxUFPDrcoTGVzUm3G/view?usp=sharing
Click to expand...
Click to collapse
Seriously, what's that thread ?
Is your link coming from a reliable source (in that case, make a proper OP with bugs, issues, credits, sources) ? Or did you just download a zip from github branch wich means it's a "[email protected]#!*!!#€upyourphone" ?
If it's the second case, this is really a bad joke considering people awaiting here.
If it's just a question, it's also a bad joke and not the right place to post.
Envoyé de mon MI Mix 2 en utilisant Tapatalk

yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
fbousk said:
Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.
Click to expand...
Click to collapse
Aaaah now I get it. Thank you. We'd better wait on him to say something when he feels it's ready enough.

I almost got an heart attack

So, I tried and I can confirm it's legit.

Benjimaestro said:
So, I tried and I can confirm it's legit.
Click to expand...
Click to collapse
So, it boots ? No real major issue for the moment ?
Thx

Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="vendor/xiaomi/chiron" name="LineageOS-chiron/android_vendor_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="device/xiaomi/chiron" name="LineageOS-chiron/android_device_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="kernel/xiaomi/msm8998" name="LineageOS-chiron/android_kernel_xiaomi_msm8998" remote="github" revision="chiron-oreo-8.1" />
<project path="device/qcom/common" name="LineageOS/android_device_qcom_common" remote="github" />
<project path="packages/resources/devicesettings" name="LineageOS/android_packages_resources_devicesettings" remote="github" />
<project path="packages/lineage/livedisplay" name="LineageOS/android_hardware_lineage_livedisplay" remote="github" />
</manifest>
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!

Arasthel said:
Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="vendor/xiaomi/chiron" name="LineageOS-chiron/android_vendor_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="device/xiaomi/chiron" name="LineageOS-chiron/android_device_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="kernel/xiaomi/msm8998" name="LineageOS-chiron/android_kernel_xiaomi_msm8998" remote="github" revision="chiron-oreo-8.1" />
<project path="device/qcom/common" name="LineageOS/android_device_qcom_common" remote="github" />
<project path="packages/resources/devicesettings" name="LineageOS/android_packages_resources_devicesettings" remote="github" />
<project path="packages/lineage/livedisplay" name="LineageOS/android_hardware_lineage_livedisplay" remote="github" />
</manifest>
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!
Click to expand...
Click to collapse
Thank you so much !

Wahoux said:
Thank you so much !
Click to expand...
Click to collapse
Absolutely terrific. Do I need to get thru Xiaomi 7.1 firmware or can I just switch from MIUI Oreo beta. That Is my major concern. Thanks for this beauty

enzo_cz said:
Absolutely terrific. Do I need to get thru Xiaomi 7.1 firmware or can I just switch from MIUI Oreo beta. That Is my major concern. Thanks for this beauty
Click to expand...
Click to collapse
I came from Miui Oreo, and just formated data before flashing LOS, and works fine

Wahoux said:
Thank you so much !
Click to expand...
Click to collapse
Wahoux said:
I came from Miui Oreo, and just formated data before flashing LOS, and works fine
Click to expand...
Click to collapse
Thanks man, I appreciate that

Amazing timing, my Mi Mix 2 is being delivered tomorrow, i cannot wait to play!
Thank you!

Arasthel said:
Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!
Click to expand...
Click to collapse
@Arasthel
Well, this is pretty good news ! But in an unconventional way. This thread is going to be spammed with questions about how to flash, which twrp, from what firmware do we need to come, dirty flash over LOS14, what's working, what's not and so on ...
Couldn't it be better that you start an official new thread and ask mods to merge this one as replies ?
Anyway, I was waiting for this. Great job Man ! Waiting for some more infos / procedure before flashing.
Envoyé de mon MI Mix 2 en utilisant Tapatalk

For flash, I'm coming from Oreo bêta Miui and have juste full wipe.
For me, the Best custom rom (Aosp) so far !!! No bug for the moment and buttery smooth !!!

Wahoux said:
So, it boots ? No real major issue for the moment ?
Thx
Click to expand...
Click to collapse
Boots very quickly. No major issues so far. Calls, SMS, mobile data, BT, camera, audio, performance are all good.
Input lag seems to be better than nougat.
For a sketchy looking alpha release it's VERY good.
Only issue is that the FP scanner vibrates if touched at any time, which causes the phone to vibrate. Just a minor annoyance.

Shuyin10 said:
For flash, I'm coming from Oreo bêta Miui and have juste full wipe.
For me, the Best custom rom (Aosp) so far !!! No bug for the moment and buttery smooth !!!
Click to expand...
Click to collapse
wow, thats encouraging! Great work to all involved. :good:
I've applied for unlock, just waiting for the sms, so by the time all that comes through this (or a proper thread) will have expanded a little.
I've missed tinkering with my phones, not done it since my htc one

[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?