Our device is still running because of XDA and the developers. And this 3 year + device is still in race to taste the Marshmallow .
Let us use this thread for discussion related to it.
And all of this has become possible because of the recognized developers @JustArchi @dhiru1602 @mcgi5sr2 @Moster2 @arter97, Christian Balster (OMNI team), @forkbomb444 Haxynox team, Nameless team (Sorry, in case I missed someone)
There are 3 projects going on for getting a build of Marshmallow.(Achieved)
The Haxynox Team --- [ AOSP M is out --- Check it out ]
The Official CM --- [ The First to come --- CM 13 Thread Link ] && { It's happening, nightlies are here - Official CM-13 Download Link }
The Nameless Team --- [ It will happen ]
For the list of Marshmallow ROM's available for S3 GT-I9300, Click below:
Official CM13 : Thread Link
Official RESSURRECTION REMIX : Thread Link
Temasek's UNOFFICIAL CyanogenMod 13 : Thread Link
Official Mokee Open Source Project : Thread Link
The CyanPop 6.x.x Project : Thread Link
Minimal OS : Thread Link
Android Ice Cold Project : Thread Link
The Haxynox Team
They are the first to initialize the process of building Marshmallow for our device tree.
Developers: @mcgi5sr2 @Ivan_Meler @dexter93
You can get the latest 'M' AOSP from here : Haxynox AOSP 'M' Link
Github: Link
Official CM 13
The development process of CM 13 has just started few days back.
Developers: Simon Shields , CM team.
Gerrit Link: I9300-M-BringUp || smdk4412
Here comes the first building project of Marshmallow CM 13 :
CM 13 Thread Link
PS: No one knows who XYZ is on XDA. I searched for him on Github and came through this account of a developer ,which has the same commits as published on Official CM Gerrit.
The link of the Github is keepcalm444 and may be it is XYZ's user name.
An XDA account matched it forkbomb444 ( The email used for commit in Official CM Gerrit Review matches it .
(I am not sure about it)
The unknown developer is none other than @forkbomb444
Official Nameless Team
They have asserted that they will definitely release Marshmallow for our device.
Source : Google+ Post
Developers: @dhiru1602 , Nameless Team.
You can follow their work on the thread here : Nameless ROM Link
Google+ Community (They are active here): Nameless ROM Official Community
Gerrit: Nameless ROM Gerrit
Note: I will update any information if something new happens. I welcome you to suggest new thoughts or new information.
You're forgetting Bliss team and their maintainers and developers who are also working to bring marshmallow to our phone. They've done a wonderful job on blisspop (I can tell you myself since I've been using their ROM as a daily driver for past weeks and I have no complaints about it)
Yes forkbomb(xda) this guy is maintaining cm13 official i ask on irc(he use this nickname)
That CM "Maintainer" is just using old commits from evryone else at the list and most of the time violating authorship by just squashing commits and putting his name on it
Romflasher69 said:
You're forgetting Bliss team and their maintainers and developers who are also working to bring marshmallow to our phone. They've done a wonderful job on blisspop (I can tell you myself since I've been using their ROM as a daily driver for past weeks and I have no complaints about it)
Click to expand...
Click to collapse
I love Blisspop too! I have tried lots of ROMS. At the end, blisspop! Thanks.
Ivan_Meler said:
That CM "Maintainer" is just using old commits from evryone else at the list and most of the time violating authorship by just squashing commits and putting his name on it
Click to expand...
Click to collapse
Maybe not because he has pushed some commits of his own also.
---------- Post added at 02:44 PM ---------- Previous post was at 02:38 PM ----------
And BTW are you guys sure that we will be getting the official CM13.0? No changes in github from last 2 days.
sunny1234590 said:
Maybe not because he has pushed some commits of his own also.
---------- Post added at 02:44 PM ---------- Previous post was at 02:38 PM ----------
And BTW are you guys sure that we will be getting the official CM13.0? No changes in github from last 2 days.
Click to expand...
Click to collapse
I didnt see his own changes at all they are just changes from other devs with his name on top..
sunny1234590 said:
Maybe not because he has pushed some commits of his own also.
---------- Post added at 02:44 PM ---------- Previous post was at 02:38 PM ----------
And BTW are you guys sure that we will be getting the official CM13.0? No changes in github from last 2 days.
Click to expand...
Click to collapse
Dear Brother, building a ROM is not like a game.
Things are always not pushed directly into gerrit everyday, it is a long process than we think.
And coming to another thing, we (normal users) have very less idea about development. It is better to keep calm than raising unnecessary issues. This issue can only be solved by a proper answer from the CM developer.
Romflasher69 said:
You're forgetting Bliss team and their maintainers and developers who are also working to bring marshmallow to our phone. They've done a wonderful job on blisspop (I can tell you myself since I've been using their ROM as a daily driver for past weeks and I have no complaints about it)
Click to expand...
Click to collapse
bingkeye said:
I love Blisspop too! I have tried lots of ROMS. At the end, blisspop! Thanks.
Click to expand...
Click to collapse
I didn't forget them. I respect their work.
Blisspop along with many other projects like Resurrection Remix, Euphoria OS, crDroid and many other are dependent on Archi device tree or Nameless device tree or Haxynox tree or some other (ROM source would be from respective projects).
Correct me, if I am wrong. I would definitely add them if someone from their team are working on bringing our device tree for 'M'.
Ivan_Meler said:
I didnt see his own changes at all they are just changes from other devs with his name on top..
Click to expand...
Click to collapse
Look onto github you'll see. However, I might be wrong too.
sunny1234590 said:
Look onto github you'll see. However, I might be wrong too.
Click to expand...
Click to collapse
Once check the below post carefully.
Ivan_Meler said:
I didnt see his own changes at all they are just changes from other devs with his name on top..
Click to expand...
Click to collapse
You would get the answer you want if you understand the bold/underlined/italicized part.
RajashekarReddy.A said:
Once check the below post carefully.
You would get the answer you want if you understand the bold/underlined/italicized part.
Click to expand...
Click to collapse
Selinux M bringup commit was of which developer? Wasn't it Simon himself? :/
Romflasher69 said:
You're forgetting Bliss team and their maintainers and developers who are also working to bring marshmallow to our phone. They've done a wonderful job on blisspop (I can tell you myself since I've been using their ROM as a daily driver for past weeks and I have no complaints about it)
Click to expand...
Click to collapse
Blisspop isn't exactly the most trustable ROM source I know. They've been caught kanging (stealing others work) many times and I'm sorry to say, but Blisspop isn't going anywhere until CM, Nameless or Haxynox do something.
Yes, it's getting a slight bit political if you're wondering.
I'm just tasting the flavor of the Marshmallow in my xt1069, but I prefer the i9300 because it's better than him (in my opinion, obviously). But, a little question about the future: can i9300 smell or taste Nutella? (I'm talking about a future Android N)
Talking about the ROM's, I feel very proud because we have so many people that don't let a device of this caliber die. Since I don't have money to donate, let me give my special thanks to all of you who don't let it go down. I'm very grateful.
moisespereira01 said:
I'm just tasting the flavor of the Marshmallow in my xt1069, but I prefer the i9300 because it's better than him (in my opinion, obviously). But, a little question about the future: can i9300 smell or taste Nutella? (I'm talking about a future Android N)
Talking about the ROM's, I feel very proud because we have so many people that don't let a device of this caliber die. Since I don't have money to donate, let me give my special thanks to all of you who don't let it go down. I'm very grateful.
Click to expand...
Click to collapse
It's a broad question.
First, let us hope if we could get a usable 'M' build first.
RajashekarReddy.A said:
It's a broad question.
First, let us hope if we could get a usable 'M' build first.
Click to expand...
Click to collapse
Too early, right? But I think we have a nice hardware to get M. Will it have a better Ram management?
Ivan_Meler said:
That CM "Maintainer" is just using old commits from evryone else at the list and most of the time violating authorship by just squashing commits and putting his name on it
Click to expand...
Click to collapse
Look, while I did do that, I think you'll find that it's been fixed. I'm sorry I did that, and it won't happen again.
Now, re: using old commits: did you *really* expect me to spend hours on end doing work that's already been done? It makes a lot more sense to focus on work that hasn't been done yet, rather than trying to redo everyone's work.
Now, if you have any issues with what I'm doing, feel free to PM me
Exactly! This is what my point is. And apart from that he himself is pushing some commits of his own. Make sure you guys checks at least. Yesterday there was two new commits which are not yet merged though.
Thanks a lot Simon @forkbomb444
forkbomb444 said:
Look, while I did do that, I think you'll find that it's been fixed. I'm sorry I did that, and it won't happen again.
Now, re: using old commits: did you *really* expect me to spend hours on end doing work that's already been done? It makes a lot more sense to focus on work that hasn't been done yet, rather than trying to redo everyone's work.
Now, if you have any issues with what I'm doing, feel free to PM me
Click to expand...
Click to collapse
I'm pretty sure proper authorship is the only issue here
Gokulbalram said:
I'm pretty sure proper authorship is the only issue here
Click to expand...
Click to collapse
He did give proper authorship to developers. Check github. Anyways, just a request to all the developers please help him to get the official CM13.0 for S3 running.
Related
Not really sure where this belongs, so Mods, please feel free to move it.
Given all the changes within CyanogenMod recently, and the formation of Cyanogen as a business, what's likely to happen to the FXP team? I know Kali has already said he won't develop CM any more.
Everyone has their own views on the politics of the situation, and this isn't really about that.
Just saying, guys, that if you happened to leave CM and develop your own AOSP-based ROM, I'm sure you'd have a lot of followers
Probably OmniRom.
http://forum.xda-developers.com/forumdisplay.php?f=2601
http://forum.xda-developers.com/showthread.php?p=46423532#post46423532
Apparently the XZ is up and running.
I'm using cm10.1.3 (stable version), with one modification (softkey decreases for 32DP, has this mod here in the forum) and I am fully satisfied.
No bug's, clean, smooth and beautiful automony battery.
I recommend.
Ooh Omnirom looks interesting,
Time to sync sources while I'm at work...
Sent from my C6603 using Tapatalk
fards said:
Ooh Omnirom looks interesting,
Time to sync sources while I'm at work...
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
patiently waiting for a yuga release..time for something fresh.
ckyy said:
patiently waiting for a yuga release..time for something fresh.
Click to expand...
Click to collapse
I think there'll be official releases out very soon, but I'll have a look at it later on when I get chance and see how it builds and runs.
No point trying to build on my machine at work, it's steamdriven!
If the build works I'll post it . Surprised @pulser_g2 hasn't posted one already
Well @fards if it runs well....it'd be nice if you could put a build up for us to have a sneak peak
Sent from my C6603 using Tapatalk
Now I've had a chance to take a look at it (not built anything I'm still looking at device trees etc) I'm a bit underwhelmed.
There's more CM and less AOSP than I'd like, lots more CM.
Going to try merging Pabx brilliant Aosp with this too see if I can get anywhere.
Don't expect anything quick, if I can motivate myself to churn through it!
No rush @fards. Not exactly an obligation to do it. Thanks again.
Sent from my C6603 using Tapatalk
tbh at the moment the entire project just appears to be a fork of CM.
far too much of it for my tastes.
I'd wish they'd started with a pure aosp base.
fards said:
tbh at the moment the entire project just appears to be a fork of CM.
far too much of it for my tastes.
I'd wish they'd started with a pure aosp base.
Click to expand...
Click to collapse
Oh dear. Back to the usual aosp rom then
@ fards
omnirom started from pure AOSP as compare to cyanogemod
---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------
@ fards
omnirom started from pure AOSP as compare to cyanogemod
xZain69 said:
@ fards
omnirom started from pure AOSP as compare to cyanogemod
---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------
@ fards
omnirom started from pure AOSP as compare to cyanogemod
Click to expand...
Click to collapse
I suggest you go take a proper look at the github, then come back and say "sorry they are using mostly cm".
The apq kernel is the cm one(didn't look at the others close enough to care). Other device trees are cm. The git structure is cm.
www.github.com/omnirom
https://github.com/omnirom/android_kernel_sony_apq8064
Code:
defconfigs: debranding
We're not a part of cyanogenmod any more. Also to avoid anyone else
having to do this, let's make the names generic to facilitate cross-
project
Change-Id: I89b6626636d568b36b9979272c6099fd074840e3
That changes the name only of the cm defconfigs. THESE are Not aosp, they are cm based.
Ergo it's a cm fork.
https://github.com/omnirom/android_device_sony_qcom-common
Code:
README.md
Copyright 2013 - The CyanogenMod Project
android_device_sony_qcom-common
Sent from my C6603 using Tapatalk
fards said:
I suggest you go take a proper look at the github, then come back and say "sorry they are using mostly cm".
The apq kernel is the cm one(didn't look at the others close enough to care). Other device trees are cm. The git structure is cm.
www.github.com/omnirom
https://github.com/omnirom/android_kernel_sony_apq8064
Code:
defconfigs: debranding
We're not a part of cyanogenmod any more. Also to avoid anyone else
having to do this, let's make the names generic to facilitate cross-
project
Change-Id: I89b6626636d568b36b9979272c6099fd074840e3
That changes the name only of the cm defconfigs. THESE are Not aosp, they are cm based.
Ergo it's a cm fork.
https://github.com/omnirom/android_device_sony_qcom-common
Code:
README.md
Copyright 2013 - The CyanogenMod Project
android_device_sony_qcom-common
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
@fards : Have a word with yourself mate ;
The git structure is the defacto standard as used by every rom who hosts on github , PA/Omni/CM.
You cannot have sub directories in your user namespace on github so you cannot represent things in the same way as you would with your own git server with a gitweb/gtiles frontend
The device trees are ported from cm for convience the rest of the project uses repo's forked from AOSP or the AOSP it's self
So instead of scanning one repo's commit messages and making a conclusion. I would suggest you read the default manifest as well to see where the sources are pulled from
https://github.com/omnirom/android/blob/android-4.3/default.xml
fards said:
I suggest you go take a proper look at the github, then come back and say "sorry they are using mostly cm".
The apq kernel is the cm one(didn't look at the others close enough to care). Other device trees are cm. The git structure is cm.
www.github.com/omnirom
https://github.com/omnirom/android_kernel_sony_apq8064
Code:
defconfigs: debranding
We're not a part of cyanogenmod any more. Also to avoid anyone else
having to do this, let's make the names generic to facilitate cross-
project
Change-Id: I89b6626636d568b36b9979272c6099fd074840e3
That changes the name only of the cm defconfigs. THESE are Not aosp, they are cm based.
Ergo it's a cm fork.
https://github.com/omnirom/android_device_sony_qcom-common
Code:
README.md
Copyright 2013 - The CyanogenMod Project
android_device_sony_qcom-common
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Andrew Dodd (Entropy512) has been one of the major Sony contributor to CyanogenMod, so were a few people that are helping us on Omni. Just because one device tree has been taken off an existing CyanogenMod repository doesn't mean we are a CM fork. It would be shooting ourselves in the foot to start device trees from the ground up again.
Besides some device trees, everything else has been up from AOSP. Therefore, we're not a CM fork.
Does anyone know who are the best known recognized developer groups making Roms for the G3 (if any)?
rumors, maybes, confirmed?
I've heard cm is on it, but other than that idk
---------- Post added at 06:36 PM ---------- Previous post was at 06:24 PM ----------
Also think I they I heard dirty unicorn is working on it, and I knoe OctOS had plans to support, but I don't think they've started yet
Cm probably do a great job on this device like others but we don't know any others yet because G3 used to have a bootloader lock.
Let's hope plenty of developers jump on board now the boot Loader problem had been circumnavigated.
Apparently LiquidSmooth is being worked on.
I would love to see purity rom on this beast also.
Can't wait to get Dirty with some Dirty Unicorns :highfive:
I haven't bothered rooting because there are no roms yet. Would be interesting to know what to expect. Cm is at least something promising.
Ohh! Purity ROM on this phone will go blazing fast! Can't wait for the flood of ROMS
shadehh said:
I haven't bothered rooting because there are no roms yet. Would be interesting to know what to expect. Cm is at least something promising.
Click to expand...
Click to collapse
I'm the same shadehh regards rooting. Untill the main stream rom makers are churning out top quality stuff I'll hold on.
I'd love to see Archidroid here. Some of the finest IMHO.
i have asked on the g+ page of aicp and test builds will be made as soon as the sources are released to bump the roms
miui
Hi guys...i love to see miui offical rom also is there any news about that.
Maybe we should let'em know about bump...
reza1995live said:
Hi guys...i love to see miui offical rom also is there any news about that.
Maybe we should let'em know about bump...
Click to expand...
Click to collapse
Bump! has already gained enough publicity from some tech blogs for ROM devs to know about it. Let's wait and give Team Codefire time to release the bumping process & I'm pretty sure we'll see a couple of ROMs pop-up soon after that!
CandyKat are working on a ROM. I asked the other day https://plus.google.com/114490049576855321482/posts/CAoWbPPn2cF (scroll to the bottom).
biron_w said:
CandyKat are working on a ROM. I asked the other day https://plus.google.com/114490049576855321482/posts/CAoWbPPn2cF (scroll to the bottom).
Click to expand...
Click to collapse
Yes we are. We have a sprint build waiting to be bumped already. Working in some device trees for other variants. We are very interested in developing for this phone as a few of us on the team have it.
I'm not too bothered about custom roms but would love to see custom kernel, something like boeffla on S3, that would be awesome
Cuzz1369 said:
Yes we are. We have a sprint build waiting to be bumped already. Working in some device trees for other variants. We are very interested in developing for this phone as a few of us on the team have it.
Click to expand...
Click to collapse
Good news Hopefully you will do a build for the d855 and if you need a tester I'm more than happy to help.
Cuzz1369 said:
Yes we are. We have a sprint build waiting to be bumped already. Working in some device trees for other variants. We are very interested in developing for this phone as a few of us on the team have it.
Click to expand...
Click to collapse
Excellent news I was running CandyKat on my Nexus 4 before I upgraded to a G3 so I'll be very happy when it's available :good:
if you need a tester I'm more than happy to help.
Click to expand...
Click to collapse
I'll happily test builds as well for the D855. Anything to help get CandyKat up and running.
Cuzz1369 said:
Yes we are. We have a sprint build waiting to be bumped already. Working in some device trees for other variants. We are very interested in developing for this phone as a few of us on the team have it.
Click to expand...
Click to collapse
Thanks for your interest in creating ROMs for the G3. Seeing the increase in developer participation over the past week or so has been great. If you plan to put out any VS985 builds, I'd be happy to give them a test run.
--------------------------------------------------------
Candykat maintainer
Ville (2.15/2.16 Hboots)
M7gsm
M8 (current device)
OnePlus One (coming soon)
i9300
gsw5700 said:
I'm not too bothered about custom roms but would love to see custom kernel, something like boeffla on S3, that would be awesome
Click to expand...
Click to collapse
thats my greatest hope!!!! that kernal was amazing
Hey so they released the OxygenOS kernel source for public use.
Source : https://forums.oneplus.net/threads/oxygenos-kernel-source.296969/
Post a thanks on the official thread .
Mohdsultan said:
Hey so they released the OxygenOS kernel source for public use.
Source : https://forums.oneplus.net/threads/oxygenos-kernel-source.296969/
Post a thanks on the official thread .
Click to expand...
Click to collapse
Sure, they have to this... 'cause linux kernel source is under GPL(License), any modifications based on it are also obligated to release their source under GPL as well
Great news!!! I hope custom kernels compatible with OxygenOS will be possible at last. :good:
ivangotoy said:
Great news!!! I hope custom kernels compatible with OxygenOS will be possible at last. :good:
Click to expand...
Click to collapse
Not yet really, please see here my request to OnePlus:
https://forums.oneplus.net/threads/oxygenos-kernel-source.296969/page-4#post-10910921
Would be really great if you could help in bombarding Helen from the OnePlus OOS team with comments and request, so they quickly react.
Andi
Lord Boeffla said:
Not yet really, please see here my request to OnePlus:
https://forums.oneplus.net/threads/oxygenos-kernel-source.296969/page-4#post-10910921
Would be really great if you could help in bombarding Helen from the OnePlus OOS team with comments and request, so they quickly react.
Andi
Click to expand...
Click to collapse
doing it! I need boeffla on my oxygen!!!!
Just left a comment there myself, it would be great if we could get more people involved.
nice
Hello,
I need some members to test my Unofficial Temasek Rom 6.0.1 for HTC m9 himaul.
You can see my build HERE for OnePlus One
Since i don't have this device, i can't test it before share on XDA.
If someone is interested please leave here your comment. Be aware that this testers may know the basis about testing, i mean that, you must to have perfect knowledge about the risks and you know all necessary precautions to do this. (backup of everything that can be damaged).
Thanks in advance
Download Temasek 6.0.1 for HTC m9 (himaul) and give your feedback
FSadino said:
Download Temasek 6.0.1 for HTC m9 (himaul) and give your feedback
Click to expand...
Click to collapse
Once I have time I will. By the way, how did you get the CM source code? The last time I tried the host was down.
nirodg said:
Once I have time I will. By the way, how did you get the CM source code? The last time I tried the host was down.
Click to expand...
Click to collapse
From github,
Anything added that isnt avaible in cm?? Better battery etc.
Roobwz said:
Anything added that isnt avaible in cm?? Better battery etc.
Click to expand...
Click to collapse
Just try and give your feedback
Edit: You can see some SS and some users opinions on my OPO thread
Too many days without feedback. Project is closed
We here in lovely XDA community are welcome LineageOS and strongly eager to learn about the new features[emoji6] [emoji106]
As they said on official site : we have not started doing official builds yet.
One of the benefits of this being an open source project is that anyone can build it, but please be careful flashing builds you’ve downloaded from other sources.
We will have some more information on when weeklies (or possibly nightlies) will be starting soon.
Thanks!
LineageOS Team
Written on December 28, 2016
...........................................................
https://download.lineageos.org/
...........................................................
Update :
21/1/2017
Lineage OS official builds coming this weekend, data migration builds available for CM users.
Details here,
http://www.androidpolice.com/2017/0...end-data-migration-builds-available-cm-users/
More details, http://lineageos.org/Update-and-Build-Prep/
******************************
Good luck for our great developers with LineageOS and for all users have fun. [emoji122] [emoji122]
Looking forward to it!
Do we need a new icon/mascot for this??
If Lineage OS were to have a new mascot, it would be a young version of the current one.
Athora said:
If Lineage OS were to have a new mascot, it would be a young version of the current one.
Click to expand...
Click to collapse
I disagree. It should be one that oozes sagacity. One that clearly "owns" and completely supersedes Cyanogen
Silent reader saying Hi!
So excited with LineageOS and had to comment. looking forward to this!!!!
Waiting for new features:fingers-crossed:
one request
don't ditch CMTE
jerryshaw12 said:
Do we need a new icon/mascot for this??
Click to expand...
Click to collapse
I think CM will live just under other name.
As soon they get and tune servers there again will be nightly builds for our devices.
Welcome Lineage
Waiting for your action
Sent from my LG G3 using XDA Labs
What do you guys think? Is it gonna have themes support? Or will it be like pure vanilla (stock Android)? What are your guesses?
BTW, I just found this.
That looks great guys, looking forward to trying the new public builds for this project as soon as available.
Im no dev, but I would like to contribute for the project with a little donation... where should I head for this?
---------- Post added at 01:07 PM ---------- Previous post was at 01:03 PM ----------
Yeah they could even allow people to submit ideas... wonderful crazy things can emerge from Internet.
OslyMcOsFace anyone?
jerryshaw12 said:
Do we need a new icon/mascot for this??
Click to expand...
Click to collapse
Great to read that this project goes on ... :good:
Here commits of LineageOS which is merged.
https://review.lineageos.org/#/q/status:merged
mayanxoni said:
What do you guys think? Is it gonna have themes support? Or will it be like pure vanilla (stock Android)? What are your guesses?
BTW, I just found this.
Click to expand...
Click to collapse
I think so, because CM team didn't have enough time to build it.
Welcome LineageOS,I like your name,your logo and i wish you all the best in future.
kh34d said:
I think so, because CM team didn't have enough time to build it.
Click to expand...
Click to collapse
I'm looking forward for it to support themes.
I've never tried it before, but I'm experimenting with making a boot animation based on this logo:
http://imgur.com/a/wYgEX
I have a Blender model in the works, and I will rig it as well.
EDIT:
http://imgur.com/a/Ozyap
A sample
I will be rendering it at QHD, but I can render the animation at any needed resolution.
EDIT 2:
https://youtu.be/g91TwtYJwec
Finished animation. Didn't turn out as good as I had hoped, but was fun none the less. If anyone's interested in the source files (lossless/blend), contact me.
Good luck to the LineageOS community!
Welcome to this New (Old?) friend, LineageOS!