Database Info

[Q] is MoKee any good?

Hi there
I will shortly be joining either the custom rom user world or bricked phone world. :silly:
I am absolutely new to the topic and would love some advice from you all.
My phone is stock ICS and I want to switch to a ROM which is very stable and fast.
Earlier i was thinking of going for PA or Cyanogen but neither seem to officially support Motorola Atrix 2. :crying:
MoKee is the only distribution which apparently has official support for my phone.
I was wondering if there is any other ROM which officially supports Atrix 2?
How good is MoKee? Would you recommend this ROM to a newbie? From what i know, Cyanogen seems to be the easiest to install.
Also, can someone list the steps to installing Mokee?
I read the content at http://forum.xda-developers.com/showthread.php?t=2305303
but for a 1st time newb all that seems very intimidating.
thank you
Rishav

Rishav Sharan said:
I was wondering if there is any other ROM which officially supports Atrix 2?
Click to expand...
Click to collapse
All of new ROM's for our Atrix2 are fast and most of them are stable (depends on user )
& Even though CM 11 is not official for our phone, but currently it is the most stable and all bug fixed rom for our A2
(I am not saying Mokee or other ROMs are not stable, but at this stage CM 11 has all bug fixed and I am sure Mokee & other will incorporate it soon :fingers-crossed: )
Also all ROM's have same procedure to install, so all ROM's are easy to install (Thanks to BMM)
You can follow steps in that link or check this video tutorial for using BMM
"Axxiom Kat" also has official support to our device.
It doesn't matters (at least for this device) whether the ROM has official support or not, our device has a team of some Recognized Contributors and A2EPT (Atrix 2 edison porting team) which keep the ROM up to date as like it is an official ROM :victory:
So dont worry flash any ROM you want :highfive:

sameerm02 said:
All of new ROM's for our Atrix2 are fast and most of them are stable (depends on user )
& Even though CM 11 is not official for our phone, but currently it is the most stable and all bug fixed rom for our A2
(I am not saying Mokee or other ROMs are not stable, but at this stage CM 11 has all bug fixed and I am sure Mokee & other will incorporate it soon :fingers-crossed: )
Also all ROM's have same procedure to install, so all ROM's are easy to install (Thanks to BMM)
You can follow steps in that link or check this video tutorial for using BMM
"Axxiom Kat" also has official support to our device.
It doesn't matters (at least for this device) whether the ROM has official support or not, our device has a team of some Recognized Contributors and A2EPT (Atrix 2 edison porting team) which keep the ROM up to date as like it is an official ROM :victory:
So dont worry flash any ROM you want :highfive:
Click to expand...
Click to collapse
Thanks Sameer!
Guess CM11 is the best bet for me.
Btw, what is the kernel update?
Would you recommend me to go for a custom kernel now? or is it something i should attempt only when i have the hang of modding?

Rishav Sharan said:
Thanks Sameer!
Guess CM11 is the best bet for me.
Btw, what is the kernel update?
Would you recommend me to go for a custom kernel now? or is it something i should attempt only when i have the hang of modding?
Click to expand...
Click to collapse
All rom's have inbuilt custom kernel (kexec kernel), if you wanna try overclocking your device you can use JBX kernel
JBX can be flashed after ROM installtion.
But for a newbie like you dont flash it yet, first try some ROM's; when you get used to it then try JBX.
And if this helps you, dont say thanks press Thanks button below the post !!
And we have separate Q&A section for question and answers
Please dont post questions here in general section

MoKee is bug free and gps works berry good

Mokee is stable and you can try SlimKat as well

Slimkat worked best for me as far as battery life, but cm11 was best overall
atrix 2 cm11

Which Lollipop ROM is better??

I just wanted to try the lollipop experience and i dont know which rom is better. Im between the anerik ROM (maybe with pink kernel or donkey kang) and experience 9.0.2
Have you tried anyone?? What about performance and battery life? Any fc? Random reboot?? I would like to flash any but I don't know which one. Dt2w is also important for me.
Anyone who could help me thanks a lott

I own moto g xt1033 dual sim phone currently running crDroid rom latest kitkat version. As per my experience, the custom version of lollypop android for our phone is just under development with few or many bugs yet to be fixed. I don't know cause I haven't tried any till date but there are many custom roms based on cm12 in the development thread, however, with some bugs on them. If you've tried xperience.cyanogen rom, 4.4 version then you'll know that they have the best audio quality and battery backup plus high performance. According to their last update in their Facebook page, they are developing cm12 for moto g. So, I'm waiting for their release.

Wait... the actuals roms of lollipop are buggy. Stay on 4.4.4 and be happy!

nicohs103 said:
Wait... the actuals roms of lollipop are buggy. Stay on 4.4.4 and be happy!
Click to expand...
Click to collapse
I suppose this is not up2date anymore? I'm still on 4.4.4 and looking for stable Lollipop ROMs. Any recommendations?

MrFista said:
I suppose this is not up2date anymore? I'm still on 4.4.4 and looking for stable Lollipop ROMs. Any recommendations?
Click to expand...
Click to collapse
I've been using xperience ROM for awhile now and I haven't had any problems, you could try it out

dustcollector69 said:
I've been using xperience ROM for awhile now and I haven't had any problems, you could try it out
Click to expand...
Click to collapse
I can only find this one which isn't Lollipop.

MrFista said:
I can only find this one which isn't Lollipop.
Click to expand...
Click to collapse
this is the one im talking about
http://forum.xda-developers.com/moto-g/orig-development/rom-xperience-9-0-0-t2952466

Reflashing; 6.x ROM (which) or 7.x ROM (which)?

Im currently on stock 6.x but my phone is getting pretty full and bugs out sometimes so I think its about time I do a fresh flash.
Is it possible to do a nandroid backup to a NAS server? A 64GB nandroid backup to a already full phone is kind of hard.
Next, I can either go 6.x or 7.x
7's notification style and doze battery life optimizations seems nice. Automatic system updates using another partition also seem good but I imagine that can only be used on Pixel.
6.x I imagine though is more stable.
So which ROM?

I personally like Android nougat more than M. Also, i find it stable enough for daily driver. I have been switching between various Nougat ROMs to find out which i like more. I am finally settled with Cm 14.1 nightlies for now.

RESURRECTION REMIX [5.8.0]
Awesome ROM with tons of customization.

RazerSharp said:
RESURRECTION REMIX [5.8.0]
Awesome ROM with tons of customization.
Click to expand...
Click to collapse
Resucrrection is way to bloated/heavy. Im sure our phone can take it but.

Looking for a Marshy? Sultans is your best bet. Simple. Stable. Clean. Reliable.

I tested almost all nougat roms. I'm stuck with legend right now, for me seems the most balanced and without serious bugs.

What about jgcaap's rom? Isn't it any good?
Official Nightly vs Jcaap vs Resurrection Remix, which is the best?

Thank you for threads like this - you can't ask in a particular ROM's thread about other ROMs... I tried the "unofficial" (CAF) 7.1.1 Ressurection Remix and I've had problems with the screen going black, doesn't mean anyone else will. So, I'm also looking for which 7.1.1 ROM to try next and want other's opinions because I just don't have time to try ALL of them myself, full wipe, install all the apps and data again, setup everything... For a day or two then on to the next over and over, but I do try to try at least a few.
The ONLY reason why I don't want 7.1.1 for certain right now is no Xposed for it yet. But, perhaps I can live without Xposed for a while as long as I have: root, adblock, privacy guard, profiles...
I'm thinking to try the "Official" 7.1.1 Resurrection Remix next? Opinions?

I recommend jgcaap's CM14.1. It's been very fast and stable with good battery life for me. He's also busy implementing Sultan's camera blobs, so camera quality is also going to be nice. Try it out for yourself, you won't regret it!

Which nougat ROM has the best battery life and the smartbar/fling navbar features?
I'm not giving up Xposed without that navbar LOL

Oh, didn't remember that Xposed isn't avalaible for 7.x yet.
Forget it. 6.x based ROMs then.

Any other NON CM based recommendations?

riahc3 said:
Any other NON CM based recommendations?
Click to expand...
Click to collapse
Purenexus

C4SCA said:
Purenexus
Click to expand...
Click to collapse
I'm having issues finding the ROM that works best for me too. I've had to resort to cm ROMs because I can't find an aosp based MM ROM that has the latest security patches. There's so few of them too . I'm currently on jgcaaps cm13 running lightning caf v50 color. Its pretty stable, but I can't for the life of me figure out why the darn thing bootloops immediately after setting selinux to enforcing. I've always set it to enforcing for security reasons in the past, and had no issues. Jgcaaps cm13 I think has the best camera hal of all the ROMs because its using color os. Not caf, sultan, or cyanogenmod (I don't even know how people consider cm hal usable).
For 7.1.1 I've tried some of the ROMs but they're missing way too many features IMO. The camera hal is one (most are using cm or caf, meh) the only 7.1.1 ROM I know of that possibly has color os hal is jgcaaps cm14. Another thing is xposed. I don't like to give google full permission over my entire system to record and do as they please, therefore I use microg. The only thing is to get micro g working, you need to have a ROM that either supports fake signatures in the developer options (ROM maintainer has to implement this, its not too hard) or an xposed module to force fake signatures. I haven't come across a single ROM here that has micro g support so I'm forced to use xposed. On top of that I use the xprivacy xposed module which is miles better at protecting your privacy than privacy guard or appops.
So yeah personally I think jgcaaps cm13 ROM is the best we have right now for MM roms. All the other MM ROMs haven't been updated with security patches in quite a while from my experience. If you don't use micro g or xposed then I would recommend jgcaaps cm14 for the color os hal, but I havent checked out his ROM in a while. I wish there was still some development on MM for our oneplus one because it seems I'm stuck between choosing discontinued MM ROMs for features + stability or actively maintained ROM with bugs + less features. I've been working on finding out how to merge security patches in to discontinued ROMs because of this. But I don't have much time in my life right now sadly.

ThunderThighs said:
I haven't come across a single ROM here that has micro g support so I'm forced to use xposed.
Click to expand...
Click to collapse
danieldmm's TugaPower ROM has microG support out of the box and there's no need to install it as a system app. HAL is still CM but it is updated very frequently (I think it supports delta OTA updates) and has latest security patches too. Had absolutely no bugs for me when I used it last time :good:

Moto Maxx running some roms of nexus 6

Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
https://youtu.be/RxoNMuIPQbw

jaaa1976 said:
Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
Click to expand...
Click to collapse
Thanks bro...

I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.

vinydasilveira said:
I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.
Click to expand...
Click to collapse
You really have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
moto maxx (xt1225) running rom stock of nexus 6. totally unstable. stock 7.1.1
*Kernel AOSP - Quark (This is merely @bhb27 LOS kernel or his standalone, there is NO such thing as "Kernel AOSP -Quark")
*Stock 7.1.1
Click to expand...
Click to collapse
Why would we want to run something like that (unstable Nougat ROM) on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our Quark phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the Quark custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the Quark custom ROMs actually use the SAME kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that YouTube post means is someone took @bhb27 kernel code and managed to horribly port a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the Quark kernel.
The reason why "stock" ROMs are not done are because they are boring. You wouldn't have the LED notification for instance that @bhb27 created, nor all the options present in Revolution Remix and crDroid. Even @calsurferpunk's LOS ROM is more of a hybrid -- LOS + some of the more popular options in RR. We already HAVE up to date 7.x Nougat ROMs. And they run well. How many more do you want?
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
What people WANT are Oreo ROMs. The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.

ChazzMatt said:
You have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
Why would we want to run something like that on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the custom ROMs use the same kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that post means is someone took @bhb27 kernel code and managed to horribly run a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the right kernel.
The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
Click to expand...
Click to collapse
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.

vinydasilveira said:
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.
Click to expand...
Click to collapse
It's about the kernel. The kernel is the foundation of all ROMs. You notice the YouTube video is merely a Nexus 6 NOUGAT ROM that doesn't run well on Quark. Because we have Nougat compatible kernel right now.
@bhb27 actually said he is using some of the Nexus 6 stuff for CLUES to adapt the Quark kernel for Oreo. But it's not easy. Until you have a compatible kernel, no Oreo ROMs will run on Quark. @bhb27 has actually gotten Oreo Resurrection Remix to run on Quark. Have you not seen the screenshots? But at this point it's still unstable.
Once you have a kernel, you can have 100 Oreo ROMs on Quark in a week -- if you find 100 people willing to port the ROMs. It's almost plug and play (for dev maintainers who have those skills). This is why we have had so many "drive by" ROMs dropped into this forum and then those people walk away without ever updating them. They were taking advantage of @bhb27's kernel work. Take ROM, plug in kernel, done. But they never stuck around to keep them updated, or even test them thoroughly, and some didn't even own a Quark phone. One of them even used @bhb27's advanced standalone kernel (not his LOS stock kernel) in their ROM without his permission, so it made their ROM seem better than the other ROMs. It's the same kernel anyone can download and install themselves, but @bhb27 wants you to install that one yourself as it's more complex. He doesn't want it installed as a default kernel -- he doesn't include it in his own ROMs.
He's working on an Oreo-compatible kernel but while everything about Moto Nexus 6 is open source (thanks to Google), it's not the same with Moto Quark. Yeah, even LG Nexus 4 has Oreo, but again, it's totally open source so easier to adapt.

Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.

about the video posted on my channel, I just made a joke at home. I know the limitations, I know the hardware is different. it was only a joke of those who do not have much knowledge, but search knowledge, the kernel used is a custom ROM 7.1.1, I did not say that the kernel is stock 7.1.1.
I admire the work of the developers, when I use a custom ROM, I can imagine how much work it has done to make it functional with few bugs. :good:
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
bhb27 said:
Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.
Click to expand...
Click to collapse
perfect explanation... I admire your work

What Stock-based ROM are you still using (2018)?

Just got a spare Z3, and since this device has been quite inactive on developments and such, the most preferred route is to stay stock for stability.
Now, I looked on our Android Development section and there seems to have a couple of stock-based ROMs which are good, and now, even in 2018, I was wondering what stock-based ROMs you guys are still using?
Any bias comments are welcome as long as it's spoken through experience. Also, a combination of Stock-based ROM a Custom Kernel would be nice to hear as well, if you use those.
Thanks guys for noticing~
:good:

Ever heard of OFFICIALLY supported
I use carbon Rom. It's supported officially.
And TWRP 3.2.1.0
Use gapps or mindthegapps
Updated weekly before. Now it's monthly.
No bugs, stable!!
0 problems in 2018
With that firmware & hardware

Stefan.xda said:
I use carbon Rom. It's supported officially.
And TWRP 3.2.1.0
Use gapps or mindthegapps
Updated weekly before. Now it's monthly.
No bugs, stable!!
0 problems in 2018
With that firmware & hardware
Click to expand...
Click to collapse
Any ways to use cyberian camera on carbon oreo? Right now im using existenz on my z3c, everything is ok and it has tones of customizations i can recommend for z3 too. But the best rom for battery is still slimm rom. Whatever lets turn back to my question, only because it is not possible use cyberian cam on carbon oreo i will go for carbon nougat with xperia ui. Can you share your experience with snapdragon camera if you use oreo version?

i have djust used the default camera app that came preinstalled with the rom. as 3rd party apps arent as good as stock. And its really good enough.
and i dont like to use outdated roms still on 6.0 M
im a crazy chronic updater.

Ömer said:
Any ways to use cyberian camera on carbon oreo? Right now im using existenz on my z3c, everything is ok and it has tones of customizations i can recommend for z3 too. But the best rom for battery is still slimm rom. Whatever lets turn back to my question, only because it is not possible use cyberian cam on carbon oreo i will go for carbon nougat with xperia ui. Can you share your experience with snapdragon camera if you use oreo version?
Click to expand...
Click to collapse
search in the Carbon or Omni Thread, someone posted magisk Modules for this
There should also be a guide in there for (regular) flashing this.

Antiallergiker said:
search in the Carbon or Omni Thread, someone posted magisk Modules for this
There should also be a guide in there for (regular) flashing this.
Click to expand...
Click to collapse
I can do whatever you want if you can find that page im looking for it for 3 months i beg you

Ömer said:
I can do whatever you want if you can find that page im looking for it for 3 months i beg you
Click to expand...
Click to collapse
I uploaded all Modules, the original ones got deleted.
Here ya go: https://www110.zippyshare.com/v/Tax6KimL/file.html
This was the original Post