Database Develop

[Q&A] Q&A Thread for Evervolv Jellybean builds

To keep the development thread clean, this thread is meant to post any questions with regards to Evervolv's Jellybean builds for your Nexus One, such as "Has issue X been solved in build Y?", or "I have a problem X. Is anybody else experience the same?". The kind users on XDA will try to answer all your questions, or point you to the relevant location to solve/address your issue.
For general discussions about the Rom, please use this thread: http://forum.xda-developers.com/showthread.php?t=1795954
Please don't forget to include as much details as possible to any questions (build number + release date, steps to reproduce the issue etc.).
Before you post a question, you should
1.) Search this thread
2.) Search the development thread: http://forum.xda-developers.com/showthread.php?t=1762790
if you can find an answer for your question.
Before you post any questions with regards to a problem you're facing, you should
1.) Search this thread
2.) Search the development thread: http://forum.xda-developers.com/showthread.php?t=1762790
3.) Search the Evervolv Code review site: http://review.evervolv.com/#/q/branch:jellybean,n,z
to check if there's already a solution that is not mentioned in OP, or if the issue was filed and/or a fix is pipelined by the developers already.
Thanks for helping to keep everything clean!

I hate to start off this thread with such a base question...but I just got a Nexus One and flashed this ROM. Wondering if anyone has a kernel suggestion to maximize smoothness...

mtmjr90 said:
I hate to start off this thread with such a base question...but I just got a Nexus One and flashed this ROM. Wondering if anyone has a kernel suggestion to maximize smoothness...
Click to expand...
Click to collapse
First off, thanks for posting to the correct thread! Now, to answer your question: Since this Rom is in a real early stage development phase, there're a few "hacks" implemented to get things running. Personally I didn't tried to flash another kernel, nor am I a kernel dev. However, to ensure functionality it might be the best choice to stay with the released kernels for the moment. I know that's not the answer you wanted, but just my 2 cents.
Edit: Especially because you were asking for "smoothness".. The Evervolv team is working to the graphic related stuff "with priority". Many libs are broken or partitially incompatible. So I think another kernel won't change anything with regards to "smoothness". But we can expect updates on that soon.

Bexton said:
First off, thanks for posting to the correct thread! Now, to answer your question: Since this Rom is in a real early stage development phase, there're a few "hacks" implemented to get things running. Personally I didn't tried to flash another kernel, nor am I a kernel dev. However, to ensure functionality it might be the best choice to stay with the released kernels for the moment. I know that's not the answer you wanted, but just my 2 cents.
Edit: Especially because you were asking for "smoothness".. The Evervolv team is working to the graphic related stuff "with priority". Many libs are broken or partitially incompatible. So I think another kernel won't change anything with regards to "smoothness". But we can expect updates on that soon.
Click to expand...
Click to collapse
Ah, thanks for the info. I got the N1 to play with and with a Galaxy Nexus as my primary device I can really feel the difference...which was of course expected I obviously haven't followed Evervolv's development in the past, just out of curiosity, how frequent are releases in general? I'm running AOKP on my GNex and they release approx every other week, so I'm hoping for something similar here.

mtmjr90 said:
Ah, thanks for the info. I got the N1 to play with and with a Galaxy Nexus as my primary device I can really feel the difference...which was of course expected I obviously haven't followed Evervolv's development in the past, just out of curiosity, how frequent are releases in general? I'm running AOKP on my GNex and they release approx every other week, so I'm hoping for something similar here.
Click to expand...
Click to collapse
Probably the best answer to get, is by looking at the release history of the Evervolv TexasIce Cream Sandwich thread (post 2 & 3): http://forum.xda-developers.com/showthread.php?p=19785288#post19785288
But don't expect weekly updates. Updates come, as Texasice think that it's worth to bump to a new build.
I didn't followed any AOKP projects.. But I know that some devs publish new builds for "every" commit they push to their repos to keep users up to date with the latest stuff. However, Evervolv is a small team of 3 devs and Texasice, who works on N1 stuff, additionally works on other devices and other stuff as well. From what I can see, he's pushing new releases when "something big" was fixed, or was improved, but not for every tiny change.
However, they build nightlies, too. So if you want, you could update every morning. But a better idea would be to follow the progress via their code review site and if you see any commit which you think you would like to have that, go ahead and grab the next nightly.
All Jellybean commits: http://review.evervolv.com/#/q/branch:jellybean,n,z
Jellybean commits that have been merged: http://review.evervolv.com/#/q/status:merged+branch:jellybean,n,z
Finally, you can find the source at GitHub and build yourself as often as you want. https://github.com/Evervolv

Lots of questions coming from me today I'm afraid... I am curious what everyone is doing to solve the Insufficient Space error. I posted a general question in the Q&A forum but I don't know if there's any particularities resulting from being on JB rather than GB (CM7).

mtmjr90 said:
Lots of questions coming from me today I'm afraid... I am curious what everyone is doing to solve the Insufficient Space error. I posted a general question in the Q&A forum but I don't know if there's any particularities resulting from being on JB rather than GB (CM7).
Click to expand...
Click to collapse
There are no peculiarities to JB that I know of. All I had to do was enter a2sd install in Terminal (after getting SU there first). I assume you already had an sd-ext partition on your SD.

Hey guys....loving the Jelly Bean experience so far!!
Real silly question here...but what do 0p1, 0p2, 0p3 mean on the nightlies. Is it just releases?
Also is there somewhere we can see what changes are made to each nightly release?
Thanks!

mothor said:
Hey guys....loving the Jelly Bean experience so far!!
Real silly question here...but what do 0p1, 0p2, 0p3 mean on the nightlies. Is it just releases?
Also is there somewhere we can see what changes are made to each nightly release?
Thanks!
Click to expand...
Click to collapse
It is version 3.0.0
p stands for pre-alpha (see it as pre-release) and the build number The JB build is just beginning TexasIce will come up hopefully soon with an alpha build once all the merging is completed

I'm coming from ICS as my daily driver, but hesitant on JB just yet.
Is the included Apps2SD working with xdata like the ICS version? I know that was an experimental feature, but it always works better for me than the normal install did.
Thanks,
-sj

I'm having serious stability issues and I just want to confirm what causing them...namely is it the ROM or perhaps a hardware issue. I've had the ROM set up and running three times now and each time (once over night, twice just having it sit around for an hour or so) it just freezes up and when I battery pull to reboot, almost all of my apps and settings have been erased. I've used the built in a2sd to move apps and dalvik to sd-ext, dunno if that could be part of the problem... Anyone else have similar issues? I'm thinking if it's not the ROM, it could be corrupt storage or something.

Is butter working in these builds?

This is more in response to your rant on the development thread than in relation to the ROM directly, but I was thinking it would possibly reduce the amount of posts about stuff not appropriate for the development thread if you could put a warning to come up when someone is writing a post for the thread asking if what they're writing is going to contribute to the development of the ROM and with links to this and the discussion thread suggesting them as more appropriate places to post. Dunno if that's possible, or if someone like you with lots of posts could suggest it as a solution to this problem that plagues so many threads?
Sent from my Nexus One using xda app-developers app

Another question which is more directly related to the ROM.
Is it possible for an option to be added to remap the soft keys? Such as remapping the search key to be a multitasking key as is in actual ICS phones?
I know I personally hardly ever use the search key but often use the multitasking features which would make it awesome to have that functionality!
Just a thought, thanks if you implement it!
Sent from my Nexus One using xda app-developers app

Just wondering when TI will release next build. Am having trouble with notifications. I have pushed all the libs but still the video playing is broken. I really don't know what bexton has fixed but p1 with all fixes was just awesome. I know TI will incorporate all those stuffs so just waitimg eagerly for a p3.
Sent from my Nexus One using Tapatalk

I don't know if it's a bug or not... sometimes screen display doesn't turn off but phone is asleep (I think). See the lockscreen but doesnt respond to touchscreen. Works fine once I wake up phone with power button. On latest nightly(7/27).
Sent from my Nexus One

seinjunkie said:
I'm coming from ICS as my daily driver, but hesitant on JB just yet.
Is the included Apps2SD working with xdata like the ICS version? I know that was an experimental feature, but it always works better for me than the normal install did.
Thanks,
-sj
Click to expand...
Click to collapse
i am using the xdata flag everything seems to work in regards to that

With smartassV2 governor the rom is faster without any reboot or similar
Has someone try it?

ironjon said:
With smartassV2 governor the rom is faster without any reboot or similar
Has someone try it?
Click to expand...
Click to collapse
Where do you change the governor? Don't see evervolv toolbox under settings. On 7/27 nightly
Sent from my Nexus One

vimitake said:
Where do you change the governor? Don't see evervolv toolbox under settings. On 7/27 nightly
Sent from my Nexus One
Click to expand...
Click to collapse
I did it with setcpu
Enviado desde mi HTC Desire usando Tapatalk 2

Lollipop for the Optimus 2x

Welcome to the official thread for the Lollipop roms for our Optimus 2x
As to start, this thread is exclusively for the developers who are interessted/working on on the Lollipop ports for our Optimus 2x
We had alredy some build like the OmniRom , CM12 and even ParanoidAndroid.
This thread is exclusively for discussions for the developers and for the testers to test the new made roms so I will update the links as the roms get made. So I am only posting here the links of the latest version, to get the versions from the past you wil need to browse throught this thread
Update 05/6/2016
Gucky did it again! New build for CyanogenMod 12.1 is up, and now with fixed camera! When I get the full list of working features and bugs, I will upload it here. Thank you Gucky for your massive help and contribution to this community. This device is very old after all, and you still find the time to tinker on it. No words really. Respect!
CM12.1 : https://sourceforge.net/projects/lg...cm-12.1-20160531-UNOFFICIAL-p990.zip/download
WARNING the Rom is still not stable, but we are close!
ParanoidAndroid: https://s.basketbuild.com/devs/Puri/p990/AOSPA(lollipop)
Take in mind that all these roms are unstable besides the CM12 rom,but it still has some major bugs which we as a group will fix.
As in all of this, stay tuned for updates

Good job my friend

Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!

um
gucky01 said:
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
Click to expand...
Click to collapse
um.......*noob mode activated.....BOOP * what you mean with manifest? lol

Could you please share your sources.
TheMysteryouse said:
Hello everyone.As you might know me from some threads where i comment some stuff.Anyways, since Lollipop was announced i was obssesed with it and my wish was that i would be the first one to make the version availble for our device.
Well i kinda did it....KINDA of course but we need some help if we wanna make it work.I call ALL of the developers for our device to work together to make it work.We are so close to get it fully booting.I made it boot to the animation and now where the help comes in use.We need some developers who can enable ADB on our device in the bootanimation.TO be honest i dont really know anything about sources and that stuff but i know some things.With the help of @tonyp and @timduru which I am the most thankfull of that gave me hope to make this.So here we go!
WARNING!!!
ONLY FOR DEVELOPERS
No one should download and flash this rom because you will get stuck in the bootanimation and will need to install previouse rom again and install everything over...blah blah blah.
Also the link to the rom is here ----> https://www.dropbox.com/s/fwhg08ux7qhtgsh/5.0 test.zip?dl=0
So if someone gets it working, please pm me in the progress. Cheers
Click to expand...
Click to collapse

TheMysteryouse said:
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Click to expand...
Click to collapse
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests

Oh
Hugo-PT said:
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Click to expand...
Click to collapse
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol

TheMysteryouse said:
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
Click to expand...
Click to collapse
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305

nope
gucky01 said:
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Click to expand...
Click to collapse
nope, didn't touch anything other than the updater script i think and the build prop because i wanted fully stock experience

I can be your tester my phone got a battery problem so im having fun with flashing roms

I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)

DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Well, it might be that he used KatKiss from timduru for the TF101 which has a Tegra 2, but still our phone uses the Tegra 2 AP20H, while the TF101 uses Tegra 2 T20. Small difference in the chipset, but still a difference. Easiest would be to port from the Galaxy R or Captivate Glide, but they too struggle with Lollipop over in their forum. Anyway, TheMysteryouse used timduru's AOSP rom, so maybe it would be easier building the whole thing from the demo CM12 sources available.

nonono
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Nope, this rom has NOTHING to do with the tegra 3 rom.I used the rom for TF101 tablet which is tegra 2 but had a cmall chipset difference.So yeah I am still trying to do some things like searching the framework sources from tony to see if he has a code in the build.prop which directly enables ADB from the boot, but cant really find it.Anyways try your best and so the others.Cheers

Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!

Any video or screenshot? xD
Sorry for nob request, but working well or not, its great to our comunity
p.s. if need tester in future, you, TheMysteryouse or DJNoXD.
Im ready for

...WoW!...That´s Good News...Thank You for All of You, Guy´s...

gucky01 said:
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Click to expand...
Click to collapse
Awesome news buddy! Lollipop on first power dual core android device! Switch to 1+ One as a primary phone for some reason but I will continue to follow and supporto you!

That is great!!! ))))))))

Ok. I have to go one step back. The rom is not ready for the testers and I'm too tired to test more. For those, who want to repeat my steps or want to finish...
I replaced the files in Mystery's rom with my own Kitkat ones. The first half, than the second. Now I could get it to finish the booting process. This steps I went on and on. So I could reduce the problem to the framework-files in "system". If you replace all of them, it boots up with some error messages.
I think we have to reduce the 40 files inside more and more to find the reason for the bootloop.
All the best to you,my friends!

Damm this is great a device from 2010 receives android L. 4years later. If I can borrow the old optimus 2x from my father then I could also look into the problems if it's not booting yet then. Till then continue your work.

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

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?