Database Develop

[Kernel}[CM11][Source][WIP]Cyangenmod11 Kernel Source for Samsung Gear by Count

First of all, every credit goes to Count([email protected]). He did everything to port CM11 and its Kernel source to Gear 1.
Second, I am just a mere messenger. I am not the developer! I don't have any knowledge about building android. I just wanted to contribute to this amazing forum. If you have any question regarding complex android internal things, send them to Count himself to the email above.(Count and I are Koreans, so our English will not be good
Third, this is a development section. No noob or meaningless questions. I won't answer them(I am a student, so I don't have much time, either.).
Forth, this kernel's state is WIP(Work in progress). ANY damage or loss due to using this source is your own risk!
Fifth, this is my first time writing a thread. If I have to write something more(I heard about GNU, but not sure how it works), please kindly tell me.
Screenshots of CM11 is in attachments
I hope development of Gear 1 will rise once again with this kernel source.
Here is the Github link :
https://github.com/tyler6389/android_kernel_samsung_ls02
Enjoy
P.S. Count is working on CM12.1, too, but don't get excited. Too much issues in this moment.
https://youtu.be/rb0R_JeI6gg

[ROM][ALPHA][WIP]'DayDream' CM11 based Rom for Gear 1
A rom to test CM11 in Gear 1.
Warning! This rom is in early Alpha stage and is really laggy and unstable. Flash this at your own risk!
This is real CM11 based rom. Made by Korean developers(including Count). Looks really good.
Battery life is great, but again, this is really laggy and unstable! ANY damage or loss due to using this Rom is your own risk!
Working
Boot
Touch
Button
Not Working
Camera
Bluetooth pairing
and many thing I didn't(and doesn't want to) try.
Please don't fill this thread with nooby questions. The rom is mainly for developers who wants to build stable and fast rom.
Users can use it, but no spamming in this thread(e.g. XX doesn't work! halp!). Every feedback will be ignored unless you have a logcat or a really specific detailed explanations.
If you want development conversation, please contact Count with email(in OP).
Installation :
do a factory reset in TWRP
flash this rom
reboot(initial boot takes 5~10 minutes)
enjoy
Download :
http://sourceforge.net/projects/cou...FFICIAL-1.8-20150822-v700-Alpha1.zip/download
Thanks to :
Daydream Team
Count

Reserved

Another one in case

ddaggebi said:
First of all, every credit goes to Count([email protected]). He did everything to port CM11 and its Kernel source to Gear 1.
Second, I am just a mere messenger. I am not the developer! I don't have any knowledge about building android. I just wanted to contribute to this amazing forum. If you have any question regarding complex android internal things, send them to Count himself to the email above.(Count and I are Koreans, so our English will not be good
Third, this is a development section. No noob or meaningless questions. I won't answer them(I am a student, so I don't have much time, either.).
Forth, this kernel's state is WIP(Work in progress). ANY damage or loss due to using this source is your own risk!
Fifth, this is my first time writing a thread. If I have to write something more(I heard about GNU, but not sure how it works), please kindly tell me.
Screenshots of CM11 is in attachments
I hope development of Gear 1 will rise once again with this kernel source.
Here is the Github link :
https://github.com/tyler6389/android_kernel_samsung_ls02
Enjoy
P.S. Count is working on CM12.1, too, but don't get excited. Too much issues in this moment.
https://youtu.be/rb0R_JeI6gg
Click to expand...
Click to collapse
Great news, do you have the github source code for the cm11 and cm12?

@litan1106
Count ports CM from existing smdk4x12(exynos 4412) devices, so we don't have any sources for CM.

I flashed the cm11 apha1 for the gear, it's a bit slow but it's looking good.

litan1106 said:
I flashed the cm11 apha1 for the gear, it's a bit slow but it's looking good.
Click to expand...
Click to collapse
It is a sort of a variant of CM11. Mainly made for design.
Count said he had increased the performance by editing the Mali drivers, so hopefully it will be faster when he releases the next version.

any chance for android wear ?

ddaggebi WOW good work

atleast there is someone who is still interested in developing for our beloved galaxy gear wish looks better than the gear s2

Time to get the dust from my good ol' Galaxy Gear. First it was about time to get rid of Tizen on it. That downgrade manual here worked very well. (http://forum.xda-developers.com/showthread.php?t=2776157)
Just needed Odin 3.09 (http://androidhost.org/PVAIv) and Samsung's USB drivers (http://developer.samsung.com/technical-doc/view.do?v=T000000117) for downgrading. After this was finished and it was able to boot on the old Samsung Linux AND WITH working touchscreen, I did a reset and flashed TWRP from here with Odin: http://forum.xda-developers.com/showthread.php?t=2537338 Last part was adb sideloading this test ROM here. Of course not working at first due to missing ADB drivers. I modded these here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip with that android-winusb.inf http://pastie.org/10428849 Works really really nice. Not very useful yet, but it's SOO great to see work bein done on this old device

Wow, just wow. Almost 2 years after buying this I see that people are still developing for my watch !? and kitkat 4.4.4 (and soon lollipop it seems) means a possibility for android wear maybe ! That's cool ! Big up from France to the dev if he comes here ahah
Is there a way like with null_ rom thought to still be able to have notifications on it like with TW rom ?

This looks so sweet. Hopefully Bluetooth pairing works out soon. would really like to try this out, downloading Rom now.
Thanks for all the hard work on this to all involved

Any work still being done on this?

Wait, you can install CM11 on a gear 's? Wouldn't you lose all Bluetooth stuff?

754boy said:
Any work still being done on this?
Click to expand...
Click to collapse
Developers says he is still working on perfecting cm11 and making cm12.1. It will take some time 'cause he has many devices to develope for.

illistration said:
Wait, you can install CM11 on a gear 's? Wouldn't you lose all Bluetooth stuff?
Click to expand...
Click to collapse
Yes, as the op says bluetooth pairing does not work at the moment.

I see.

CM 12.1 For S2

Could someone educate me on what it takes to get CM 12.1 on to the S2?
I understand that you have to root, install TWRP, and flash the ROM but who actually puts together CM 12.1 rom together and makes it compatible for the S2? Is it the official CM team or a developer on this forum who takes the time and energy to put it all together?
Thank you for your help in educating me......

There is no Cyanogen for our tablet for the moment
You can check here : http://download.cyanogenmod.org/

So it is the CM Team that takes the time, energy, and resources to put it together for the S2?
I will keep an eye on the CM website and hope they put something together soon. I wish I had someway to contribute but my skill set is very limited.
Thanks

Dekan54 said:
So it is the CM Team that takes the time, energy, and resources to put it together for the S2?
I will keep an eye on the CM website and hope they put something together soon. I wish I had someway to contribute but my skill set is very limited.
Thanks
Click to expand...
Click to collapse
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.

Okay - That makes sense.... I will help test if you get to that point.

Would be nice with cm12 but probably with lots of drawbacks. Samsung won't release source code of drivers and could be problematic with exynos nor will fingerprintscanner work.

BigBot96 said:
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Click to expand...
Click to collapse
You may want to ask @eousphoros for help. He got it rolling on the the tab s I bet he could help you big time!

BigBot96 said:
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Click to expand...
Click to collapse
Good to hear someone is working on it. ?
Sent from my not-so-stock SM-T810

CM is always buggy and lots of features wont work or plain buggy. Bloat is very minimal and works quite smoothly stock. Dont blame you if you like the "fun" of constantly flashing roms and waitkng for bug fixes.

Dekan54 said:
Could someone educate me on what it takes to get CM 12.1 on to the S2?
I understand that you have to root, install TWRP, and flash the ROM but who actually puts together CM 12.1 rom together and makes it compatible for the S2? Is it the official CM team or a developer on this forum who takes the time and energy to put it all together?
Thank you for your help in educating me......
Click to expand...
Click to collapse
Hey there. As a dev myself I will explain you the difference between official CM builds (build = the ROM) and unofficial builds. Official builds are made by the pros. The guys that are in the CyanogenMod group. They know how things work and patch them due their high knowledge. They will try to update the ROM regularly and fix it as well as they can. Then there are the unofficial builds from people like me. It depends what your skills are and with what board you are working (Exynos is a pain in the ass). Not to forget what version of android your device is currently running. Unofficial builds can be buggy and could take some time to get fixed. However devs will listen to the feedback of the community too.

"S4" ROMs on "S4 Active" - possible?

For the "S4 Active" ... can I also use the ROMs that are made for the "S4" ? I don't want to get stuck with a handset which is not widely supported, but I like the thought of owning a rugged phone.
There is a ROM "Galaxy S4 (Intl)" which is a CM13
https://download.cyanogenmod.org/?device=jfltexx
but the newest "Galaxy S4 Active (Intl)" is still on CM12
https://download.cyanogenmod.org/?device=jactivelte
As I have a good offer to buy a "Galaxy S4 Active" tomorrow lunchtime, please answer quickly if you have any information about this question.
Thanks a lot
Andreas

ankade said:
For the "S4 Active" ... can I also use the ROMs that are made for the "S4" ? I don't want to get stuck with a handset which is not widely supported, but I like the thought of owning a rugged phone.
There is a ROM "Galaxy S4 (Intl)" which is a CM13
https://download.cyanogenmod.org/?device=jfltexx
but the newest "Galaxy S4 Active (Intl)" is still on CM12
https://download.cyanogenmod.org/?device=jactivelte
As I have a good offer to buy a "Galaxy S4 Active" tomorrow lunchtime, please answer quickly if you have any information about this question.
Thanks a lot
Andreas
Click to expand...
Click to collapse
The answer depends.
First thing first, it MUST NOT be the AT&T version (i537), which has basically no support. The most supported S4 Active is the LTE-A (powered by a SD800 and with alot more [ported] ROMs, but not here on XDA). But usually when you talk about S4 Active is the GT-I9525 version (jactivelte).
The S4 Active hasn't got a great development, and currently the latest working patchrom works for TW 5.0.x based ROMs. There are some CM13 Unofficial builds, which works great, and recently a dev posted even an almost completely working CM14 (Bluetooth doens't work, WiFi is a bit bugged). BTW, he also posted a patch for CM13 and CM14 both, but they must be implemented in the source code itself, and not in the final ROM, and that mean you cannot flash this patch over any S4 ROM.
I successfully finished my Ubuntu setup today, and I'm currently downloading the compressed repos of CM13 and CM14. In 2 days I should be able to sync them and compile them, this time publishing the source code. In poor words, I would be able to start to compile CM14 builds, and MAYBE finally publishing a working PatchROM for CM13/CM14, but that's not easy, and I have to deal with time because of the school. So, if you could spend something more for an S4, I advice you to buy an S4, but if the price is really well, you can think on it.
Ivan

LuckyNuke1310 said:
The answer depends.
First thing first, it MUST NOT be the AT&T version (i537), which has basically no support. The most supported S4 Active is the LTE-A (powered by a SD800 and with alot more [ported] ROMs, but not here on XDA). But usually when you talk about S4 Active is the GT-I9525 version (jactivelte).
The S4 Active hasn't got a great development, and currently the latest working patchrom works for TW 5.0.x based ROMs. There are some CM13 Unofficial builds, which works great, and recently a dev posted even an almost completely working CM14 (Bluetooth doens't work, WiFi is a bit bugged). BTW, he also posted a patch for CM13 and CM14 both, but they must be implemented in the source code itself, and not in the final ROM, and that mean you cannot flash this patch over any S4 ROM.
I successfully finished my Ubuntu setup today, and I'm currently downloading the compressed repos of CM13 and CM14. In 2 days I should be able to sync them and compile them, this time publishing the source code. In poor words, I would be able to start to compile CM14 builds, and MAYBE finally publishing a working PatchROM for CM13/CM14, but that's not easy, and I have to deal with time because of the school. So, if you could spend something more for an S4, I advice you to buy an S4, but if the price is really well, you can think on it.
Ivan
Click to expand...
Click to collapse
I don't have anything to add, I just want to say thanks for taking the time to continue development for the S4 Active. I'm sure there will be many others who appreciate your efforts.
I think if you are able, creating a patch for S4 ROMs would provide the most benefit for the community.

Devo7v said:
I don't have anything to add, I just want to say thanks for taking the time to continue development for the S4 Active. I'm sure there will be many others who appreciate your efforts.
I think if you are able, creating a patch for S4 ROMs would provide the most benefit for the community.
Click to expand...
Click to collapse
The problem is my Ubuntu setup just fu**d while repo syncing
Will try to fix the problem and continue to download tomorrow

Thanks a lot for your quick answer. I have bought the phone now, it is a "GT-i9295" (jactiveltexx, ARMv7, MSM8960, Adreno 320, 2GB).
I see in your signature: "Samsung Galaxy S4 Active, GT-I9295 : 16/2Gb, SD600, ..." Looks like that is exactly my device?
"6.0.1, Resurrection Remix 5.7.4, TWRP 3.0.2, Rooted"
Which folder on http://www.resurrectionremix.com/ is it?
I still have the original 5.0.1 ROM on it.
Is there anything I should do NOW (e.g. backup the original OS) before I start going through the whole liberation process now?
And then - where do I start?
LuckyNuke1310 - please keep up the good work! Much appreciated!
P.S.: I am happy to donate some Bitcoin when I actually start using one of your solutions.

LuckyNuke1310 said:
...
Ivan
Click to expand...
Click to collapse
I just wanted to say a huge THANK YOU, to you Ivan LuckyNuke1310 - your post helped me a lot.
I have now run a 5.1.1 Android (CM12.1 of August 2016) for quite a while, and it seems to be working well (apart from this new problem).
Actually, I was quite proud when I rooted and CM-flashed my first ever Android phone what a liberation!
So ... Happy New Year to you, and all the best. Keep us updated about your progress, please.

ankade said:
I have bought the phone now, it is a "GT-i9295"
Which folder on http://www.resurrectionremix.com/ is it?
Click to expand...
Click to collapse
Sorry if I didn't answer you before, but I didn't read the message.
However, the ROM is old now. You can however install any CM13. If you search in the tread you'll find a drive folder with some builds. Download and flash the latest one. Or download mine, I suppose it's a daily driver except for some issues.
ankade said:
I just wanted to say a huge THANK YOU, to you Ivan LuckyNuke1310 - your post helped me a lot.
I have now run a 5.1.1 Android (CM12.1 of August 2016) for quite a while, and it seems to be working well (apart from this new problem).
So ... Happy New Year to you, and all the best. Keep us updated about your progress, please.
Click to expand...
Click to collapse
Thank YOU for being part of this community

[ROM][GT-I9506][ks01lte][Unofficial LineageOS 13.0]

Here is my build of LineageOS 13.0 for the Galaxy S4 LTE A. It is based on the pure LineageOS code unless indicated otherwise.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from LineageOS. So every credit goes to the ones providing the code.
I will not and cannot make any changes to the code. The only thing I can do and will do is build the ROM.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like any custom ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (starting with the latest official Samsung firmware 5.0.1) and runs without obvious issues. Your mileage may vary.

https://www.mediafire.com/?c8q4lqh675hc97b,7dhley6dl6j9dnb
Based on LineageOS official code up to https://review.lineageos.org/154230

Which modem and boot loader can you recommend?

audianer said:
Which modem and boot loader can you recommend?
Click to expand...
Click to collapse
I flashed the latest official Samsung firmware to prepare for LineageOS 13.0

I'm trying to build the latest version, which does build without error, but upon booting gets stuck at starting the apps, i.e. just before showing the lock screen. The latest working build was from January 5th 2017 and I experienced the error first on a build of January 8th 2017. So I suspect the commit in question is one from January 6-8.
Before I'm forced to manually investigate commit-by-commit from the latest working version, does anyone know what has changed that causes this error? I was not able to get any output from adb logcat either, so I have no idea what went wrong... which is rather frustrating.

What device tree and kernel did you use?

DualJoe said:
What device tree and kernel did you use?
Click to expand...
Click to collapse
The same as the working previous build: LineageOS/android_kernel_samsung_ks01lte & LineageOS/android_device_samsung_ks01lte. As far as I can see nothing in the kernel or device tree has changed, thus it must be some incompatibility with the rest of the LineageOS code.
I just tried another build just an hour ago, same result: stuck at the final starting apps (before the vibration). I also tried reverting to a working state of the source (of January 5) by using "repo forall -c 'git checkout `git rev-list --all -n1 --before=", but that one didn't even build.
I would appreciate any help here. It's not like there were some exhaustive documentation about how to build LineageOS. And anyway, apparently building is not the issue here.

If that's still Solk2's stuff it might be very old indeed.

DualJoe said:
If that's still Solk2's stuff it might be very old indeed.
Click to expand...
Click to collapse
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)

WeirdSoup said:
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
Click to expand...
Click to collapse
Uhm... There are cm-14.1 branches too.

zardak said:
Uhm... There are cm-14.1 branches too.
Click to expand...
Click to collapse
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.

WeirdSoup said:
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
Click to expand...
Click to collapse
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone

zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
Click to expand...
Click to collapse
Oh, I'm sorry. I misstated. I mean, the "device" repo. (https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0)

zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.

zardak said:
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
Click to expand...
Click to collapse
You are absolutely right. I dont know, maybe they have reasons not to join the LineageOS team, but when I got my S4 I was rather confused with all this different versions. I mean for many devices you get unofficial builds with extra features/improvements, but for the I9506 its hard to tell the differences. However at the moment I would say the build by gugu0das is the best, but it looks like he is not going to update it anymore. So yes, it would be great to have all those talented developers out there working on the same repos.

PixelChris95 said:
So yes, it would be great to have all those talented developers out there working on the same repos.
Click to expand...
Click to collapse
I believe this is some sick "if you don't figure it out yourself, you're not supposed to know how to do it" attitude of some (most?) developers. Or another symptom of "not invented here" syndrome.
If LineageOS official builds are available I will surely not waste time to build it myself, but in the meantime I would like to be up-to-date. So still, anyone pointing me to information how to do it is very welcome.

zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
I think the same of you. It could be better for all of us to make a ROM with the best of their ROMs.

JohnMcClane1htc said:
I think the same of you.
Click to expand...
Click to collapse
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!

NeuDLi said:
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
Click to expand...
Click to collapse
If my comment has offended you, I apologize. My comment doesn't want to disparage anyone. And I recognize the effort of the developers because, although I am not, I know how difficult it must be to develop a ROM.
If my comment has offended you, I apologize. I am sorry.
I also create content in Htcmania and always share and show the sources. I only would want to say that sometimes, when finding so many ROMs based on CM, it can be difficult to decide for one or the other, since the changes between them are very subtle.
Regards

Maintaining/creating roms is usually the way people learn Linux, Android, compiling, git and such. That's why there are so many one-man projects. Once they are into it most vanish again/go over to other stuff though. Only few people keep over long time like Temasek. In the end there can't be enough roms. More options are always better than none. As long as people are posting the source code for other people to pick up they do work together already.

Bliss ROM: why closed thread and is it good?

Hi, I am looking for a new ROM for my Mi Mix and thought that the Bliss Rom looks the most promising to me.
However, the thread has been closed by the author, @heindrix and moderator @gregbradley without explanation.
Anyone knows why it is closed and if the ROM is a dead-end?
Thanks!

pzkfwg said:
Hi, I am looking for a new ROM for my Mi Mix and thought that the Bliss Rom looks the most promising to me.
However, the thread has been closed by the author, @heindrix and moderator @gregbradley without explanation.
Anyone knows why it is closed and if the ROM is a dead-end?
Thanks!
Click to expand...
Click to collapse
Hi there,
It's glad to see that somebody still wants to use the rom i maintained some times ago.
Unfortunately i've been so busy in my job, and well i've switched device to OP6T, that's why i decided to close the thread down to prevent any long wait and further disappoinment for never-ending wait.
Last time i checked the Bliss Rom source, they already updated and patched many things i've done before, so i can tell you that the source already very dependable.
All you need is another dev to cook it using Lineage Tree, and all will be good. :fingers-crossed:

Thank you so much for your answer @heindrix!
Still, even if it is not the latest source code, is your latest build stable enough to be used day-to-day? The comments look good and there does not seem to be any major bug (like the proximity sensor, for example).

pzkfwg said:
Thank you so much for your answer @heindrix!
Still, even if it is not the latest source code, is your latest build stable enough to be used day-to-day? The comments look good and there does not seem to be any major bug (like the proximity sensor, for example).
Click to expand...
Click to collapse
if i remember, the last build fairly good but can be improved. last time i've build the new update but i've deleted it and forgot to post it, lol.
i suggest you use rom build by inkypen. :fingers-crossed:

SyberiaOS I suppose? (there are at least two)

So, I actually tried first to install Bliss and it is so nice that I don't see any reason to try another one! Thanks @heindrix !
Maybe there is something I am missing about what can provide an actively maintained ROM?

pzkfwg said:
So, I actually tried first to install Bliss and it is so nice that I don't see any reason to try another one! Thanks @heindrix !
Maybe there is something I am missing about what can provide an actively maintained ROM?
Click to expand...
Click to collapse
yeah, actually the rom from Bliss Team is very nice, it's full of features, and it's still my favorite team until now.
you can learn to build the rom and maintain it, there's so many tutorial and threads and telegram groups that will help you learn how to build a rom.

heindrix said:
Hi there,
It's glad to see that somebody still wants to use the rom i maintained some times ago.
Unfortunately i've been so busy in my job, and well i've switched device to OP6T, that's why i decided to close the thread down to prevent any long wait and further disappoinment for never-ending wait.
Last time i checked the Bliss Rom source, they already updated and patched many things i've done before, so i can tell you that the source already very dependable.
All you need is another dev to cook it using Lineage Tree, and all will be good. :fingers-crossed:
Click to expand...
Click to collapse
Congrats on your new job! I know its pretty late to ask, but will you work on porting drivers for Adreno 630 now?