Related
I recently acquired a Droid turbo and was surprised by the lack if development for such a nice device. I quickly learned this was mostly due to the locked bootloader that took a while to crack. But having the Maxx with unlocked bootloader, I'm still rather surprised by how little development there seems to be for these devices. Maybe I'm spoiled as my last rooted device was a Moto G which had more ROMs than you can flash in a day, mods galore and things such as MultiROM. That leads to my question...
Now that more ROMs have rolled out and bootloader can be pretty easily be unlocked, is anyone working on MultiROM for quark? I searched around and have seen no mention of it all all for Quark devices. Is there something preventing it or do we just need someone to work on it? It's handy, especially with a phone with decent storage and a variety of ROMs.
Sorry for the lengthy post and I don't mean this as a "someone needs to make this for us" post. I'm just curious as MultiROM seems to be available on most devices these days but no mention of it for Quark.
mbj731 said:
But having the Maxx with unlocked bootloader, I'm still rather surprised by how little development there seems to be for these devices. Maybe I'm spoiled as my last rooted device was a Moto G which had more ROMs than you can flash in a day, mods galore and things such as MultiROM.
.
Click to expand...
Click to collapse
"How little development"? Your premise is faulty.
We have 9 Marshmallow ROMs, plus we had at least 5 Lollipop ROMs, and now we have a Nougat ROM before most other devices! We have a custom kernel maker -- for both Lollipop and Marshmallow -- and now that same dev is now giving us the Nougat ROM.
I've been flashing ROMs since at least 2010, have owned several Nexus devices. Plus have have configured and set up many friends' phones. I'm not a dev, but far from a newbie. I've never used MultiROM in my life and have no desire to.
However, yes we can always use more developers. Our CM dev @Skrilax_CZ got a Moto Maxx XT1225 and developed official CM for us, along with the very important kernel. Others like @bhb27 came along developed more ROMs with CM's kernel. He also developed a custom kernel and gave us official TWRP for Quark.
Except for CF's Verizon stock-based ROM, all other ROMs are based on the work of those two devs. But we do have a lot of Marshmallow ROMs, and we have one Nougat and will have more. Here's the list of current Marshmallow and Nougat ROMs. I'm not even going to bother listing Lollipop anymore -- but we had at least 5, maybe more. AICP (Marshmallow) is not mentioned since the dev never made an official thread and says he's not maintaining it anymore -- even though people keep flashing it and asking about it in his other threads (AOKP and Bliss). But that one and @iiWoodstocK's Brazilian adaptation make 9 Marshmallow ROMs for Quark. Plus of course Nougat.
There are devices like Nexus which may have more ROMs but that's a very respectable amount of development!
____________
Here's the current custom Nougat (7.x) Quark ROMs to choose from. More will be coming!
[ROM][7.X][All quark] crDroid Android
That ROM started on 7.0 right now, and is already 7.1.
Here's the current custom Marshmallow (6.0.1) Quark ROMs to choose from:
[ROM][All Quark][6.x.x]Resurrection Remix
Bliss Rom 6.4 by Team Bliss
[ROM][6.0.1][OFFICIAL][QUARK] MoKee OpenSource Project
[Rom] NEXUS EXPERIENCE 10.4 [MotoMaxx] (recently updated to Marshmallow)
AOKP - Android Open Kang Project[6.0.1][Marshmallow]
[Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL] CyanogenMod 13.0[6.0.1]
[ROM][2016-09-17][Quarks][CM 13.0 Unofficial][6.0.1] (hybrid of CM13 and Resurrection Remix)
That list is in no particular order.
_________________________
You can also install a Marshmallow stock ROM released by Motorola for the Brazilian Quark. @iiWoodstocK adapted it so it runs on ANY Quark, including the XT1254 Droid Turbo or XT1250 U.S. Moto Maxx (clone of the XT1254). It will use YOUR radio, whatever you have installed.
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
Stock 6.0.1 MPG24.107-70.2 (Brazil) for Verizon XT1254
http://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
I didn't include it in the list above, because while technically it is a custom ROM, the only "customization" was to allow it to be flashed via TWRP and to allow it to be used on ALL Quarks: XT1254/XT1250/XT1225. Otherwise, it's pure Motorola Marshmallow stock which was officially released for a Quark phone.
iiWoodstocK said:
this ROM is just factory Marshmallow with a modded build.prop. I didn't include any radio in the .zip, so it uses whatever is currently on the device. Aside from my build.prop tweaks, this ROM is even usable for Brazilian XT1225 users, but the device will say it's a Droid Turbo and contain useless CDMA build.prop lines.
Click to expand...
Click to collapse
iiWoodstocK said:
Major stock functionality that I have confirmed working as it should: Moto Display, Approach to wake, Wi-Fi, mobile data (LTE/3G), calls, etc. No Verizon VoLTE (yet). I have not tested Moto Voice as I do not use Moto Voice, but I see no reason why it wouldn't work.
Click to expand...
Click to collapse
Any questions go to those threads and ask.
ChazzMatt said:
How little development? Your premise is faulty.
We have 9 Marshmallow ROMs, plus we had at least 5 Lollipop ROMs, and now we have Nougat before most others. We have a custom kernel maker, for both Lollipop and Marshmallow and he's the one who is now giving us the Nougat ROM.
I've been flashing ROMs since at least 2010, have owned several Nexus devices. Plus have have configured and set up many friends' phones. I'm not a dev, but far from a newbie. I've never used MultiROM in my life and have no desire to.
However, yes we can always use more developers. Our CM dev @Skrilax_CZ got a Moto Maxx XT1225 and developed official CM for us, along with the very important kernel. Others like @bhb27 came along developed more ROMs with CM's kernel. He also developed a custom kernel and gave us official TWRP for Quark.
Except for CF's Verizon stock-based ROM, all other ROMs are based on the work of those two devs. But we do have a lot of Marshmallow ROMs, and we have one Nougat and will have more. Here's the list of current Marshmallow and Nougat ROMs. I'm not even going to bother listing Lollipop anymore -- but we had at least 5, maybe more. AICP (Marshmallow) is not mentioned since the dev never made an official thread and says he's not maintaining it anymore -- even though people keep flashing it and asking about it in his other threads (AOKP and Bliss). But that one and @iiWoodstocK's Brazilian adaptation make 9 Marshmallow ROMs for Quark. Plus of course Nougat.
There are devices like Nexus which may have more ROMs but that's a very respectable amount of development!
____________
Here's the current custom Nougat (7.x) Quark ROMs to choose from. More will be coming!
[ROM][7.X][All quark] crDroid Android
That ROM started on 7.0 right now, and is already 7.1.
Here's the current custom Marshmallow (6.0.1) Quark ROMs to choose from:
[ROM][All Quark][6.x.x]Resurrection Remix
Bliss Rom 6.4 by Team Bliss
[ROM][6.0.1][OFFICIAL][QUARK] MoKee OpenSource Project
[Rom] NEXUS EXPERIENCE 10.4 [MotoMaxx] (recently updated to Marshmallow)
AOKP - Android Open Kang Project[6.0.1][Marshmallow]
[Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL] CyanogenMod 13.0[6.0.1]
[ROM][2016-09-17][Quarks][CM 13.0 Unofficial][6.0.1] (hybrid of CM13 and Resurrection Remix)
That list is in no particular order.
_________________________
You can also install a Marshmallow stock ROM released by Motorola for the Brazilian Quark. @iiWoodstocK adapted it so it runs on ANY Quark, including the XT1254 Droid Turbo or XT1250 U.S. Moto Maxx (clone of the XT1254). It will use YOUR radio, whatever you have installed.
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
Stock 6.0.1 MPG24.107-70.2 (Brazil) for Verizon XT1254
http://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
I didn't include it in the list above, because while technically it is a custom ROM, the only "customization" was to allow it to be flashed via TWRP and to allow it to be used on ALL Quarks: XT1254/XT1250/XT1225. Otherwise, it's pure Motorola Marshmallow stock which was officially released for a Quark phone.
Any questions go to those threads and ask.
Click to expand...
Click to collapse
As I said, maybe I'm just used to having tons of options. I had a Moto G (falcon) for a while. It's a budget device from 2013 and they have Nougat ROMs, tons of MM and LP ROMs, MultiROM, several OS ports, custom kernels etc... I guess it makes sense that a cheaper phone will be easier to get in the hands of devs and more people will dev for them.
I'm not complaining... But the Quark section is much more quiet than I was used to with my old Falcon.
I appreciate all the work that anyone puts in to making custom ROMs etc. My main question here was inquiring on MultiROM. For someone who constantly flashes ROMs or tries different mods, kernels etc, it's awesome. Why backup/wipe/flash/setup all the time when you can seamlessly switch between ROMs? With 32 or 64gb of storage you could in theory have all 9 MM ROMs installed and boot to whichever one you felt like using at the moment. Weed out the ones you wouldn't use and have several to choose from without having to wipe/install or restore etc.
mbj731 said:
is anyone working on MultiROM for quark?
Click to expand...
Click to collapse
yes I already made Multi ROM TWRP to work on quark, I manage to install more then one ROM in the device and hit a problem when trying to load secondary ROM's have no idea how to fix so I never publish I don't see this as a major thing to spend my time on so I prefer to improve others project that works 100% and work on the bring up of Nougat for a example as I have very limited time and there is very little developer for quark that really know how to do things some things may never come to life, I my self now very little but I never stop improve my self...
So maybe some day I finish the project and make it fully work, next try will be when TWRP and MultiROM project are released official for Nougat.
bhb27 said:
yes I already made Multi ROM TWRP to work on quark, I manage to install more then one ROM in the device and hit a problem when trying to load secondary ROM's have no idea how to fix so I never publish I don't see this as a major thing to spend my time on so I prefer to improve others project that works 100% and work on the bring up of Nougat for a example as I have very limited time and there is very little developer for quark that really know how to do things some things may never come to life, I my self now very little but I never stop improve my self...
So maybe some day I finish the project and make it fully work, next try will be when TWRP and MultiROM project are released official for Nougat.
Click to expand...
Click to collapse
If I remember correctly from the moto G days, you had to have a patched kernel to work with MultiROM. I don't remember exactly what it was that was implemented within the kernel. It seems like MultiROM would be easily ported between devices since it's not specific to a particular device.. But that's only an assumption from someone who knows nothing.
I know nothing of developing, but wish I had a computer so I could try to help out.
Thanks for your work. If you have the TWRP file available, could you PM me a link?
bhb27 said:
yes I already made Multi ROM TWRP to work on quark, I manage to install more then one ROM in the device and hit a problem when trying to load secondary ROM's have no idea how to fix so I never publish I don't see this as a major thing to spend my time on so I prefer to improve others project that works 100% and work on the bring up of Nougat for a example as I have very limited time and there is very little developer for quark that really know how to do things some things may never come to life, I my self now very little but I never stop improve my self...
So maybe some day I finish the project and make it fully work, next try will be when TWRP and MultiROM project are released official for Nougat.
Click to expand...
Click to collapse
Just remembered, it was a kexec patch that the kernel needed in moto G. Not sure if that helps you any as I have no idea what it means. But pretty sure without it, you could load ROMs on the device but they wouldn't boot without the Primary ROMs kernel being kexec patched.
Here's a link to some info about porting MultiROM. I'll keep looking in to it and if I can get a PC, I'll even try to figure it all out.
https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
mbj731 said:
Just remembered, it was a kexec patch that the kernel needed in moto G. Not sure if that helps you any as I have no idea what it means. But pretty sure without it, you could load ROMs on the device but they wouldn't boot without the Primary ROMs kernel being kexec patched.
Here's a link to some info about porting MultiROM. I'll keep looking in to it and if I can get a PC, I'll even try to figure it all out.
https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
Click to expand...
Click to collapse
If I already made it I probably know all about it :silly: but of course knowing what is needed and make it fully work is another history, I know you may be excited to have it but is not my priority and will not be for some time I already do too much for this device.
bhb27 said:
If I already made it I probably know all about it :silly: but of course knowing what is needed and make it fully work is another history, I know you may be excited to have it but is not my priority and will not be for some time I already do too much for this device.
Click to expand...
Click to collapse
Oh, I understand. I wasn't pushing for you to make it. I was just pointing out a relevant thread. It seems pretty straight forward from that description as long as the device follows the guidelines of what works. But as I said, I'm no dev.
I can do without MultiROM but I don't know why people wouldn't want it or think it's not useful. For someone who loves to flash and use different ROMs it puts them one click away from multiple ROMs at boot.
Maybe I can come across a PC one of these days and tinker with it.
bhb27 said:
yes I already made Multi ROM TWRP to work on quark, I manage to install more then one ROM in the device and hit a problem when trying to load secondary ROM's have no idea how to fix so I never publish I don't see this as a major thing to spend my time on so I prefer to improve others project that works 100% and work on the bring up of Nougat for a example as I have very limited time and there is very little developer for quark that really know how to do things some things may never come to life, I my self now very little but I never stop improve my self...
So maybe some day I finish the project and make it fully work, next try will be when TWRP and MultiROM project are released official for Nougat.
Click to expand...
Click to collapse
Just an update for this post. Multi-ROM has now been released by @bhb27, plus we now have SEVEN Nougat ROMs.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=73459132&postcount=80
But as I explained in post #2, the "lack of development" for this phone was always a faulty statement. Development on this phone has been constant since the very beginning. We've had several ROMs to choose from and many tools and apps.
ChazzMatt said:
Just an update for this post. Multi-ROM has now been released by @bhb27, plus we now have SEVEN Nougat ROMs.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=73459132&postcount=80
But as I explained in post #2, the "lack of development" for this phone was always a faulty statement. Development on this phone has been constant since the very beginning. We've had several ROMs to choose from and many tools and apps.
Click to expand...
Click to collapse
Thanks Chazz
Downloading and trying...
Actually have RR Rom and i want to try the new Viper like 2nd Rom.
In a few days, i comment the result of my test.
P.S. Excuse me if i made mistakes w/english, im not so good w that.
ChazzMatt said:
Just an update for this post. Multi-ROM has now been released by @bhb27, plus we now have SEVEN Nougat ROMs.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=73459132&postcount=80
But as I explained in post #2, the "lack of development" for this phone was always a faulty statement. Development on this phone has been constant since the very beginning. We've had several ROMs to choose from and many tools and apps.
Click to expand...
Click to collapse
Thanks for the update.
The "lack of development" was already explained. There are plenty of ROMs to tinker with for the Quark and that is great... But venture in to the Moto G section and you will see just how many options there are for that device. I don't think it officially made it past KitKat and there are well over 9 Nougat ROMs, plus kernels, mods, etc for that phone and it's still kicking after 5 years or so.
It was never a knock on development of the Quark or "lack there of"....rather I was a bit surprised that there weren't more people with this phone and more devs pumping out builds like I was used to for the falcon. Not a big deal.
mbj731 said:
Thanks for the update.
The "lack of development" was already explained. There are plenty of ROMs to tinker with for the Quark and that is great... But venture in to the Moto G section and you will see just how many options there are for that device. I don't think it officially made it past KitKat and there are well over 9 Nougat ROMs, plus kernels, mods, etc for that phone and it's still kicking after 5 years or so.
It was never a knock on development of the Quark or "lack there of"....rather I was a bit surprised that there weren't more people with this phone and more devs pumping out builds like I was used to for the falcon. Not a big deal.
Click to expand...
Click to collapse
On my view "devs pumping out builds" is not always a great thing.
Some developer are only producing more without any care for quality or care to help in the improve of development, they are just using the known good recipe to build for that device from CM/LOS repos or wherever they fell is good, downloading the source give some commands and without any real development from they side producing a ROM, I know learn somethings takes time, but after some long time some developer don't ever try move from that side of just producing a ROM using others work to produce a ROM with they on changes/fixes and sharing that to others so the development can improve.
big community of developers working together trying to improve development great, great number of ROM/development projects not equal to that.
you are also trying to compara quark 2014 device to falcon 2013 device, a years of development on a much cheaper device is not far, as the cheapness will make it more available and popular, falcon was probably released on more markets then quark, and time will help to make people interested on to doing development to it, Droid Turbo 2 is another good sample of unpopular device for development.
Apparently, an OTA update has been issued to the Android One Moto X4, which added the November security patch and supposedly improved stability and camera performance of the device. Is there anyone here with the Android One variant of the Moto X4 with this update, and if so, do you feel that this update has improved anything in the two above fields/what was said to be improved in the update changelog?
Just checked, no OTA available in my location atm. Hopefully soon. *I'll let you know when it does
Android One on Project Fi. Still on Sept patch. No updates available.
I have the normal Moto x4 variant. It came with the with November security patch, and performance and camera improvements. Update was about 120 mb or so. My x4 did see a sleight increase in performance and camera. I'm in the US. I received the update a couple of days ago. I know youre asking about the one variant but the updates shouldn't be too different right?
Protect fi version here. I got an update a few days ago, the camera no longer takes 5 seconds to take a picture.
I haven't really noticed anything different otherwise, I just really really miss my lg g5 camera
Moto X4 Android One.......Got my update this evening. Stability was never really an issue, but the phone does seem smoother now. Camera is faster. Haven't had much time to take pictures so can't speak about quality. Comes with Nov 1 security patch. Small update. Took about 30 mins to complete.
crazyates said:
Android One on Project Fi. Still on Sept patch. No updates available.
Click to expand...
Click to collapse
Yesterday I didn't have it, but I just re-checked today, and I got it now.
OTA is 90.6MB.
Just checked mine, UK model (XT1900-5) and still no update =(
this may be a really dumb question but i can't find the answer anywhere... is it possible to flash the stock android one rom on a normal x4?
bombaglad said:
this may be a really dumb question but i can't find the answer anywhere... is it possible to flash the stock android one rom on a normal x4?
Click to expand...
Click to collapse
Right now it does not seem to be a port available yet, it should be done soon, like it was done quickly on the Xiaomi Mi 5X from the Mi A1, but flashing directly through fastboot, is very risky, there is a high chance that it will fail and brick your device and there is another variable to take into account, the Android One is probably using A/B partitions, which I think the regular X4 is not, so a fastboot flash is again, very risky. We're still waiting on TWRP, once that is available, hopefully custom ROMs will start flowing =D this is just a couple month old device
hugoprh said:
Right now it does not seem to be a port available yet, it should be done soon, like it was done quickly on the Xiaomi Mi 5X from the Mi A1, but flashing directly through fastboot, is very risky, there is a high chance that it will fail and brick your device and there is another variable to take into account, the Android One is probably using A/B partitions, which I think the regular X4 is not, so a fastboot flash is again, very risky. We're still waiting on TWRP, once that is available, hopefully custom ROMs will start flowing =D this is just a couple month old device
Click to expand...
Click to collapse
Actually Retail x4 is also using A/B partitioning. so there's high chaance straight up system flashing will work.
kraatus90 said:
Actually Retail x4 is also using A/B partitioning. so there's high chaance straight up system flashing will work.
Click to expand...
Click to collapse
That would be awesome, is there any images available for the Android One Version, that we can try and flash it?
hugoprh said:
That would be awesome, is there any images available for the Android One Version, that we can try and flash it?
Click to expand...
Click to collapse
Not yet unfortunately.
hugoprh said:
That would be awesome, is there any images available for the Android One Version, that we can try and flash it?
Click to expand...
Click to collapse
Several have gone the other direction and flashed retail on an A1 model. At least one has returned to a Fi image afterwards, but by using a Flashfire backup as an official copy of the Fi firmware is not available yet. Something in the currently established bootloader unlock/root process screws up the OTA process, so that's something to be aware of. It'll get fixed eventually, but it's an issue for now.
Mention best ROM in your opinion you have ever used till date on MOTO G5S PLUS
Also please try to mention XDA link for your respective ROM .
Not to sound negative or unappreciative, but literally none of them have worked for me in the USA with Sprint as my carrier. If I try to change the carrier settings to work better (or at all) with Sprint, carrier services stops working completely until I reboot. This is the same with literally all the ROMs on this site. I don't know if they're using wrong or very region specific proprietary blobs when compiling or what, but it's the same thing with all the ROMs, including popular "unofficial" ROMs like Dirty Unicorns, LineageOS, etc. It's been a very disappointing experience after upgrading to the Moto G5S Plus from the Motorola Nexus 6 where I had so many more (working) ROM options available.
So, my answer would be the stock ROM. I recently flashed back to stock, unrooted Nougat, took the Oreo update, and since there really aren't any working ROMs available for me, I didn't even bother to root again. Sprint added a free 50GB/month wifi hotspot to each phone on my account and the Camera 2 API is active in Moto's stock Oreo ROM. Those were my two main reasons for rooting, and they're no longer needed. So, I'm just running stock Oreo with Nova Launcher.
hey guys at present I'm using my a2 On Official Android One Rom With Bootloader unlock (camera2api) Enabled. Some Users Say that Android one rom is laggy And lot's of bugs. So I want You To suggest Me What Should I Do? Install A Costom rom On my device like (Pe or something else) Or Stay With Android One?
I recommend Pixel Experience CAF version. I'm currently using that since I got fed up with Android One updates. I have been on custom ROMs for quite some time actually. CAF version supports OTA so you don't have to flash it again with every update, camera2api is already enabled and there is a MIUI camera included, but you'll have to find a working GCam yourself though. I haven't actually experienced any bugs for now but people say there are few and those will be fixed in the next update.
Edit: Just to add a few reasons why I am against Android One since you wrote that some users reported issues with stock but not you yourself.
It all started with the September update(if I recall correctly, or maybe even earlier). The bug present in that update made the faster CPU cores lock up at maximum frequency if the fingerprint sensor is used which drained battery really quickly. It took them like 1-2 months to fix that one. Then came Pie update, a lot of stuff stopped working. The storage for some reason got really slow and clearing large app cache(especially Chrome cache) would freeze the device or even make it reboot. This is the issue they STILL haven't fixed.
With January 2019 update a lot of devices went into bootlops and got bricked. February update changed contrast of the display and made everything really bright, definitely brighter than it should have been. Now they fixed that issue in March update BUT the update bootloped/bricked some more devices again so they pulled it. Their updates have really become a joke, which is why I'm all for custom ROMs. Definitely more stable than stock.
Brothr can u share the link to the post or step by step process for installing custom pe rom ?
Sid.Boi said:
Brothr can u share the link to the post or step by step process for installing custom pe rom
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
If you are flashing Pixel Experience you don't need to flash GApps, the rest is the same from the guide.
Thnq brthr :good:
I thinking same idea for months, but i have problem that i follow countless guides from forum here but i fail every to get PE CAF or Havoc rom to mine A2. I have every time black screen problem on instaling TWRP i couple times flash 10.0.2 version via mi flash tool, lock and unlock bootloader etc.. currenty i am on stock 10.0.7 with open bootloader because of camera2api, but i wanna clear phone from all the mess wanna clear both slots and finally instal succesfuly PE CAF version. Can someone provide some guide how to do it?
Greetings.
I just got my Redmi Note 11 and want to flash a custom ROM on it. This is my first time flashing a custom ROM.
My main requirement in custom ROMs is to keeping the stock Pixel experience, stability, stable update frequency, though a large range of customisability features would never hurt.
After some research I think I stopped on two options: Pixel Experience and Evolution X. I would like to read your opinions and preferences between these two ROMs. What differences do they have in the following topics?:
Stability
Customisability (especially PE+ vs EvoX)
Performance
Also, Pixel Experience is supposed to give us features that are present on Pixel phones, so what Pixel features does it have that Evolution X doesn't?
P.S. Sorry for my English.
If you're gonna unlock the bootloader and flash a custom recovery anyway, you should probably check both ROMs out. You can create a backup of the first one you've installed and can always recover it if you don't like the other ROM.
Schmuppes said:
If you're gonna unlock the bootloader and flash a custom recovery anyway, you should probably check both ROMs out. You can create a backup of the first one you've installed and can always recover it if you don't like the other ROM.
Click to expand...
Click to collapse
Thanks for your opinion. I think I'll flash Pixel Experience (Normal edition) and if I notice any problems or lack of features that Evolution X has I'll migrate to Evolution X. But still I'd like to hear everyone's opinion.
Evo X
Pros:
- More customization options (See Evo X ROM for RN11 reviews on YT for more info)
Cons:
- Allegedly reported that head dev of the ROM (Hoey) adds bugs each update (A redditor pointed this out to me)
- OTA updates may not work properly if flashed via TWRP, not sure if you can get updates to work if flashed via other recoveries
Pixel Exp
Pros:
- Ability to hide navbar
- OTA works perfectly (If flashed via Pixel Exp recovery and not TWRP)
- Some features ported from MIUI ROM
Cons:
- Less customization options
note: everything is based on what I know, haven't flashed either ROM as I am still waiting for the 1 week wait time to end to unlock. I do prefer PE over Evo X
What Schumuppes pointed out is the most viable way, for you to decide for which ROM you prefer and suits you better
Alex Zander-kun said:
Evo X
Pros:
- More customization options (See Evo X ROM for RN11 reviews on YT for more info)
Cons:
- Allegedly reported that head dev of the ROM (Hoey) adds bugs each update (A redditor pointed this out to me)
- OTA updates may not work properly if flashed via TWRP, not sure if you can get updates to work if flashed via other recoveries
Pixel Exp
Pros:
- Ability to hide navbar
- OTA works perfectly (If flashed via Pixel Exp recovery and not TWRP)
- Some features ported from MIUI ROM
Cons:
- Less customization options
note: everything is based on what I know, haven't flashed either ROM as I am still waiting for the 1 week wait time to end to unlock. I do prefer PE over Evo X
What Schumuppes pointed out is the most viable way, for you to decide for which ROM you prefer and suits you better
Click to expand...
Click to collapse
Thank you. I'm also waiting to unlock the bootloader. For now I'm mostly worried about the update frequency. As both Evolution X and Pixel Experience ROMs are maintained by volunteers I'm afraid that updates may be late. Don't get me wrong, I don't blame them and both of the maintainers seem to do their job well but this feeling doesn't leave me.
What about other differences other than more customisation options in the settings? Like I know that Evolution X uses a modded version of Pixel Launcher and Camera Go as the camera while Pixel Experience uses Basic Camera. Any other differences?
Pixel exp is more stable. Evo ex have more features but also more bugs, in my experience both of them have some issue like frames drop in almost all social apps etc…. For now, I'm back in MIUI because it's the most stable for me. But try for yourself, maybe you have a different experience.
cloakzy said:
Pixel exp is more stable. Evo ex have more features but also more bugs, in my experience both of them have some issue like frames drop in almost all social apps etc…. For now, I'm back in MIUI because it's the most stable for me. But try for yourself, maybe you have a different experience.
Click to expand...
Click to collapse
Thanks again for the reply. It's funny how depending on who do I ask I get different replies. Someone says Pixel Experience is more stable, another one says the opposite.
What do you think about PixelPlusUI? Because another one said most games are laggy on Evolution X.
cloakzy said:
Pixel exp is more stable. Evo ex have more features but also more bugs, in my experience both of them have some issue like frames drop in almost all social apps etc…. For now, I'm back in MIUI because it's the most stable for me. But try for yourself, maybe you have a different experience.
Click to expand...
Click to collapse
How can one get back to Miui?
namelessshere said:
Thanks again for the reply. It's funny how depending on who do I ask I get different replies. Someone says Pixel Experience is more stable, another one says the opposite.
What do you think about PixelPlusUI? Because another one said most games are laggy on Evolution X.
Click to expand...
Click to collapse
evo x rom is a mystery box, it nails some function but lags in others. basic function such as calling ( forget vowifi and video calling , just normal calling) don't work well. After every update some weird bugs come up which are simply annoying. BB is decent and won't expect more than that (though i've experienced better in crdroid ig).
here's my suggestion:
for 4/64 variant : don't install any custom rom for now as they are just coming up rn, if you want you can try those roms without gapps. i hope with time roms will become more stable and suitable for your usage.
for 6/128 variant : sky is the limit, use any roms according for your preference. crdroid is more stable and with lesser bugs in every update. evo x is more pixel like, overall works well except the issues mentioned above. pixel experience: stock experience w/ some miui goodies.
btw i am on latest version of evox rom. hope this helps.
cheers!
adremy said:
How can one get back to Miui?
Click to expand...
Click to collapse
First, u need to download fastboot build version for your phone from this site, Site Link
then just install Mi flash tool Mi tool Link here, a video explaining how to use it Link
note : when flashing there 3 option
1- clean all -
2- save user data
3- clean and lock
I will advise u to not chose the last one because it will lock bootloader and then u will have to do all unlocking steps again, so the best option to use is the first 1
Thank you. One last question please
Are all Redmi Note 9s curtana? Cos I feel my ROM is EvoX miatoll
adremy said:
Thank you. One last question please
Are all Redmi Note 9s curtana? Cos I feel my ROM is EvoX miatoll
Click to expand...
Click to collapse
For 9s is curtana, miatoll is like a name that contain different version of the phone like pro version goes by the name of
joyeuse pro max also have different name in all this version come under the name of miatoll, so yeah for note 9s is curtana.
Here, a post I found for more detail link
Hello i tried both of them on my SPESN and for me PE is way more stable, even if a lot of bugs and lags still present i’m pretty sure that will be resolved in futures updates