Related
Got a rooted stock 5.1.1 with Xposed Nexus 6 right now.
I am wondering whether or not its worth it to install Android 6.0 because Xposed for Android 6.0 is out. Nothing that Android 6.0 offers is enticing to me.
Can anyone post a link to what google has done in terms of security for Android 6.0? There are 3 android 6.0 files right now in the firmware site.
Android 6.0 is so incremental that everything featurewise it offers can already be done with xposed or 3rd party apps. The only open question is security.
I really dont want to flash and lose my stuff to this. Battery life with my current setup is fine for me.
Battery life is a lot better as it goes into "Doze" mode when inactive. I'm sure there's more . It's also a bigger pain to root than before.
Friends,
The work on Cyanogen OS/MOD 12.1 seems to be stopped.
Developers are working hard on Cyanogen OS/MOD 13.
So lets discuss about Cyanogen OS/MOD 13.
Add your suggestions, which we want in Cyanogen OS/MOD 13.
www .cmxlog. com/12.1/ham
www .cmxlog. com/13/ham
Why there are no changelogs ? last 2 Nigthlys came without any information.
Because developers are moved towards canogenmod 13
Hope next week we get CM13 Nightly`s on our devices
I think I will never buy again a Cyanogen OS phone. Cyanogen OS with MS crap and lame updates. Old S3 get CM13, ZUK Z1 still not get CyanogenMod 13 :/
Note 5 get Android 6, S6 get it and even Huawei roll Android 6 out... Huawei xD
Klanac89 said:
I think I will never buy again a Cyanogen OS phone. Cyanogen OS with MS crap and lame updates. Old S3 get CM13, ZUK Z1 still not get CyanogenMod 13 :/
Note 5 get Android 6, S6 get it and even Huawei roll Android 6 out... Huawei xD
Click to expand...
Click to collapse
The s3 has long been in the market, others (s6, etc) cost more than double
Enviado desde mi Z1 mediante Tapatalk
Don't worry. As long as I and JoaoPaulo are around you guys will have the latest Android versions.
Just get our unofficial CM13 build.
It has everything but the fingerprint reader working and even that one is only a matter of time until we get it working.
Klanac89 said:
I think I will never buy again a Cyanogen OS phone. Cyanogen OS with MS crap and lame updates. Old S3 get CM13, ZUK Z1 still not get CyanogenMod 13 :/
Note 5 get Android 6, S6 get it and even Huawei roll Android 6 out... Huawei xD
Click to expand...
Click to collapse
LOL! Typical for people like you. Go ahead, don't buy. Would you rather like to get constant updates with tons of bugs, or just stable and working OS.
And watch your language here.
Also Huawei is one of the greatest players on the market... You obiviously do not know a thing and all you do is rage on xda.
(Huawei made some ofNEXUS devices also. Would Google let Nexus line to someone stupid?)
Maybe it's your first Cyanogen OS phone but I use CM already for 5 years (CyanogenMod). Huawei got 200 devices, Cyanogen 4-5 and no-cyanogen-phones get CM13 Cyanogen is just clean Android, nothing special like MIUI with ton of tools.
If you can't wait for updates just start building for yourself? So do I. That's one of the opportunities you have with our Zuk Z1. At least everything is working as it should with Cyanogen Mod on it. I had a lot of phones in the past which had Cyanogen Mod but a lot of features wasn't working anymore.
Klanac89 said:
Maybe it's your first Cyanogen OS phone but I use CM already for 5 years (CyanogenMod). Huawei got 200 devices, Cyanogen 4-5 and no-cyanogen-phones get CM13 Cyanogen is just clean Android, nothing special like MIUI with ton of tools.
Click to expand...
Click to collapse
CyanogenMod and CyanogenOS aren't same.
Also, they have scheduled it way before. There was already information when Cyanogen OS 13.1 is coming to this phone before you could buy it. So please just be careful and don't whine about update. Everyone would rather like good and stable update over some quick and buggy update. And only most of premium devices are getting update now , not this price range.
YoolaCro said:
CyanogenMod and CyanogenOS aren't same.
Also, they have scheduled it way before. There was already information when Cyanogen OS 13.1 is coming to this phone before you could buy it. So please just be careful and don't whine about update. Everyone would rather like good and stable update over some quick and buggy update. And only most of premium devices are getting update now , not this price range.
Click to expand...
Click to collapse
100% True.
To that guy that was talking without knowing anything:
CM13 was scheduled for ZUK Z1 way before i get it, and i get this device like one month ago, but they are working on it offline for sure. They prefer to get a fully working ROM to a device than give it a full buggy one. Me and @MrColdbird just could not wait more until they release their source, and i came from a nexus device (pretty sure you know that i downgraded from android 6.0 to 5.1.1 when swap devices), and we decided to work on 6.0 to give users an early experience of CM13, because we can't handle 5.1.1 anymore.
We made a almost full bringup of 6.0 devtree and kernel, and we made a port from a completely different CAF branch, in about 15 days, imagine in what time can CM do it, as they are maintaining this device. Even CM for Nexus Line and OPO (their big son), have bugs on SystemUI and other things, do you think they will even consider about making builds to another phones?
I think almost android users prefer a 100% working device with less features, than a device with newest Software and filled you bugs.
So are u still arguing?
If you don't like CM devices, just don't SPAM our threads like you have reasons to do so.
Go SPAM your device thread, and leave us alone.
Best Regards,
João Paulo
JoaoPaulo said:
100% True.
To that guy that was talking without knowing anything:
CM13 was scheduled for ZUK Z1 way before i get it, and i get this device like one month ago, but they are working on it offline for sure. They prefer to get a fully working ROM to a device than give it a full buggy one. Me and @MrColdbird just could not wait more until they release their source, and i came from a nexus device (pretty sure you know that i downgraded from android 6.0 to 5.1.1 when swap devices), and we decided to work on 6.0 to give users an early experience of CM13, because we can't handle 5.1.1 anymore.
We made a almost full bringup of 6.0 devtree and kernel, and we made a port from a completely different CAF branch, in about 15 days, imagine in what time can CM do it, as they are maintaining this device. Even CM for Nexus Line and OPO (their big son), have bugs on SystemUI and other things, do you think they will even consider about making builds to another phones?
I think almost android users prefer a 100% working device with less features, than a device with newest Software and filled you bugs.
So are u still arguing?
If you don't like CM devices, just don't SPAM our threads like you have reasons to do so.
Go SPAM your device thread, and leave us alone.
Best Regards,
João Paulo
Click to expand...
Click to collapse
Well said bro...we are waiting for your updates for the fingerprint, please never mind what others are saying we know you guys are doing a very good job for our ZUK Z1.
Ramshu97 said:
Well said bro...we are waiting for your updates for the fingerprint, please never mind what others are saying we know you guys are doing a very good job for our ZUK Z1.
Click to expand...
Click to collapse
Yes you have mentioned in detailed, hope he understood, while you preparing, pls consider the following things as my request,
1. Full screen caller dial, existing like in Cos 11
2.Camera like ZUI or Color OS camera which can use only in OPO & OPPO
---------- Post added at 01:17 PM ---------- Previous post was at 01:17 PM ----------
JoaoPaulo said:
100% True.
To that guy that was talking without knowing anything:
CM13 was scheduled for ZUK Z1 way before i get it, and i get this device like one month ago, but they are working on it offline for sure. They prefer to get a fully working ROM to a device than give it a full buggy one. Me and @MrColdbird just could not wait more until they release their source, and i came from a nexus device (pretty sure you know that i downgraded from android 6.0 to 5.1.1 when swap devices), and we decided to work on 6.0 to give users an early experience of CM13, because we can't handle 5.1.1 anymore.
We made a almost full bringup of 6.0 devtree and kernel, and we made a port from a completely different CAF branch, in about 15 days, imagine in what time can CM do it, as they are maintaining this device. Even CM for Nexus Line and OPO (their big son), have bugs on SystemUI and other things, do you think they will even consider about making builds to another phones?
I think almost android users prefer a 100% working device with less features, than a device with newest Software and filled you bugs.
So are u still arguing?
If you don't like CM devices, just don't SPAM our threads like you have reasons to do so.
Go SPAM your device thread, and leave us alone.
Best Regards,
João Paulo
Click to expand...
Click to collapse
Yes you have mentioned in detailed, hope he understood, while you preparing, pls consider the following things as my request,
1. Full screen caller dial, existing like in Cos 11
2.Camera like ZUI or Color OS camera which can use only in OPO & OPPO
Some news ?
Klanac89 said:
I think I will never buy again a Cyanogen OS phone. Cyanogen OS with MS crap and lame updates. Old S3 get CM13, ZUK Z1 still not get CyanogenMod 13 :/
Note 5 get Android 6, S6 get it and even Huawei roll Android 6 out... Huawei xD
Click to expand...
Click to collapse
I'm new to this Cyanogen/CM and don't know how Cyanogen updates their phones, but from their page at /support it doesn't look like any of their phones got version marshmallow. Are they reliable with updates? I'm wondering how long will Z1 be supported.
we will wait
i see right now all waiting 6.0 and cm 13
me too and im one from those dont know any thing about flashing but i thank u guys for ur work
and i wait the 6.0 for my zuk
and i want to be helpful
if u want any thing to do with my phone to test or somthing i will do
iam Arabian user for the cm 12.1 now
its very good
waiting ur updates soon as possible
If you are fine without a fingerprint reader for now then you can just run the unofficial CM13. JoaoPaulo will implement the fingerprint reader later in January.
Hey, I really would like to test your CM13 build. You wrote, that it is important to backup the persist-partition, if we want to change back to CM12.1. Can I do this with the 'partition backup & restore' app? And just restore the perisist partition after reflashing CM12.1? Or is it included, when I make nandroid-backup via TWRP? Thank you very much!
Gesendet von meinem Z1 mit Tapatalk
bjoerniko said:
Hey, I really would like to test your CM13 build. You wrote, that it is important to backup the persist-partition, if we want to change back to CM12.1. Can I do this with the 'partition backup & restore' app? And just restore the perisist partition after reflashing CM12.1? Or is it included, when I make nandroid-backup via TWRP? Thank you very much!
Gesendet von meinem Z1 mit Tapatalk
Click to expand...
Click to collapse
You can back it up in a root terminal via the following command.
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img
And no, it's not part of a nandroid backup. But yes, any mean of backing up and restoring partitions should (theoretically) work.
Although I'm not entirely sure that restoring the partition in a running Android OS is possible as the partition might be mounted at the time. Restoring it via fastboot or TWRP will work though.
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.
I have the SM-T713 running stock nougat 7.0. The tablet does everything I need it to do just fine. I have flashed Lineage OS 14.1 on a phone that was stuck at 6.0 and it's a nice stable ROM with a lot of features I don't really need. I'm torn between leaving my S2 alone (and hoping it gets 8.0 sometime in the future) and flashing Lineage to get rid of the Samsung bloatware (though it doesn't really interfere with anything I do.) I don't really need the Lineage custom features but it would be nice to have my S2 and my phone (Moto G3) look the same.
I'm soliciting any and all opinions on the flash or not flash dilemma. A valid response would include "if it ain't broke, don't fix it." If anyone has flashed their S2 with Lineage and would like to comment (pro or con), that would be great too.
Just go and look around the thread. read the post if got any problem to the current build. if you satisfied with it then flash away. if not just stay with samsung. Use Nova Launcher or apex and find the same theme for your phone as well. what use flashing a not ready custom rom. And If you find it solid for daily driver why not?
Hey there. i have a s20 fe 5g (snapdragon, model SM-G781B), galaxy s8 (exynos), ans galaxy tab A 7.0 2016. Right now I managed to install Android 13 (Lineage OS 20 + NikGapps + Magisk for safetynet) on my backup s8 aswell I managed to flash Lineage os 14 (Android 7, along with Gapps) on my galaxy tab A. Im wondering to do the same about my S20 FE 5G since its support is unfortunately about to end. Thought of flashing TurboUI after i would unlock my device but just want to confirm its safe before doing so. What you guys think? Many thanks.
MrTaffy said:
Hey there. i have a s20 fe 5g (snapdragon, model SM-G781B), galaxy s8 (exynos), ans galaxy tab A 7.0 2016. Right now I managed to install Android 13 (Lineage OS 20 + NikGapps + Magisk for safetynet) on my backup s8 aswell I managed to flash Lineage os 14 (Android 7, along with Gapps) on my galaxy tab A. Im wondering to do the same about my S20 FE 5G since its support is unfortunately about to end. Thought of flashing TurboUI after i would unlock my device but just want to confirm its safe before doing so. What you guys think? Many thanks.
Click to expand...
Click to collapse
Hello
This will depend on what use you will give it.
Apparently you are not interested in any of the OneUi customization layer, nor Samsung Dex.
Personally, I am not interested in lineageOS or any rom that is not based on OneUi.
well with many errors, be fighting with incompatibility.
you will find GSI, Lineageos, etc.
I preferred stock rom with modified kernel, androd 13 will not stop working in 2023,2024,2025, etc.
I don't see the importance of moving to an invented and beta system for the team, at least at present.
You will find among the best options:
*stock,root,kernel(bandit,klimbo,etc)
*Turboui v4
*GSI.
mezacorleehone said:
Hello
This will depend on what use you will give it.
Apparently you are not interested in any of the OneUi customization layer, nor Samsung Dex.
Personally, I am not interested in lineageOS or any rom that is not based on OneUi.
well with many errors, be fighting with incompatibility.
you will find GSI, Lineageos, etc.
I preferred stock rom with modified kernel, androd 13 will not stop working in 2023,2024,2025, etc.
I don't see the importance of moving to an invented and beta system for the team, at least at present.
You will find among the best options:
*stock,root,kernel(bandit,klimbo,etc)
*Turboui v4
*GSI.
Click to expand...
Click to collapse
Rn my S20 FE 5G is at binary 5. I dont care about rollbacking because i do like the latest verisons and have no use to move onto earlier versions. I just wonder if binary 5 would only limit me to this android 13 one ui 5.1 (like if i couldnt install an android 13 or even a future android 14 rom only because of binary 5). Would it be safe to switch to a custom rom that has the same patch and the same android version without binary 5 doing mess there (like i want to install the latest turboUI at one ui 5.1 may patch, is that possible?)
Rn the device is at may security update, I hope it solved this problem so I could safely move to custom rom without further issues. If I had screwed please let me know as possible to I could reconsider before doing so avoiding further damage. And yeah I have checked OEM unlock and it appears so i believe no issues should occur, just should factory reset (among with removing samsung and google accounts before doing so), enable debugging and oem unlock, go to download mode and then unlock bootloader, and then flash twrp and then whatever i think so.
And yeah I prefer one UI over stock android however the latest custom one ui version for s8 was only one ui 2.5 (hades rom) and no one even dares to make a new one for it, is just dead there. I felt urged to install android 13 so i had no choice but to flash LineageOS 20 (along with nikgapps and magisk). Meanwhile the S9 can get even one ui 5.1 ported via noble rom. I wish something would be done despite being 3 years already since.
But still I won't have prob flashing kernels instead of custom roms if so. Thank you very much.
Alright, just managed to install TurboUI without issues and against all odds.
I was worried because the new binary would mess there but still I managed to do it without issues, and I feel grateful for it
Speechless.
I can't appeal your urges to desperately switch roms.
reading the previous thing you wrote, I have nothing more to say.
If you have errors in the future, please go to the appropriate channels, (turboui, gsi tem, etc.)
Thus, avoid publications due to user errors without investigating before installing.
excellent day.
mezacorleehone said:
Speechless.
I can't appeal your urges to desperately switch roms.
reading the previous thing you wrote, I have nothing more to say.
If you have errors in the future, please go to the appropriate channels, (turboui, gsi tem, etc.)
Thus, avoid publications due to user errors without investigating before installing.
excellent day.
Click to expand...
Click to collapse
Alright, have to admit, learnt the hard way
there is SEVERE lack of custom roms there. The lineage OS cant mix with gapps and the custom one ui rom drains battery faster. I had no choice to revert to stock rom. I downloaded its firmware of april patch. Flashed it using Odin and it worked successfully!
You can call me an idiot for the rest of my life as you wish, i had should considered before doing so. Anyways I feel grateful for restoring its rom. But anyways if I would need safetynet I would welcome myself to do so.
I should learn more before installing these stupid roms. Maybe i will continue flashing on S8 but i wont longer flash on S20 FE since that incident. (And noice, the software firmware not matching, aka red message on bot disappear!)
If you have any suggestions youre welcome to tell me so, sorry for not beliving you at first. I should owe you everything
Have a nice night, ig, and I should learn much from that
I understand your inspiration to improve performance.
I've been doing this from symbian (nokia, sony ericcson, palm, blackberry, ios)
current times are not the same.
we are with more powerful processors.
larger and faster ram memories.
Over the years it took me to understand that it is currently not necessary to change the rom.
Example: you are with a s20 FE android 13, it is a completely current system, recently released last December.
I would not have to go to lineageOs, why?
Why did android 14 come out for lineageOs?
I'll have to break down my s20, of course not.
Seeking to get the most out of Oneui with a kernel that exploits its characteristics and without system bugs, seems to me to be a more suitable option.
When it is 2026 or 2027 see GSI options would be a good option.
repeat again, it is a personal thought, for so long I learned, to free myself from stress and constant mistakes.
mezacorleehone said:
I understand your inspiration to improve performance.
I've been doing this from symbian (nokia, sony ericcson, palm, blackberry, ios)
current times are not the same.
we are with more powerful processors.
larger and faster ram memories.
Over the years it took me to understand that it is currently not necessary to change the rom.
Example: you are with a s20 FE android 13, it is a completely current system, recently released last December.
I would not have to go to lineageOs, why?
Why did android 14 come out for lineageOs?
I'll have to break down my s20, of course not.
Seeking to get the most out of Oneui with a kernel that exploits its characteristics and without system bugs, seems to me to be a more suitable option.
When it is 2026 or 2027 see GSI options would be a good option.
repeat again, it is a personal thought, for so long I learned, to free myself from stress and constant mistakes.
Click to expand...
Click to collapse
Alright, just finished relocking my bootloader. Yeah, no more software updates but I can still download them online, and they are security updates so i guess not really a big loss because no more OS updates (One ui 5.1 is final!). Still I HAVE to learn from this incident onwards, maybe on 3 years whenever the device would be too old like the s8 only then i would reconsider doing so. But for now I would stay with this stock rom and I would keep updating it time to time as needed. Everyone makes mistakes anyways. And yeah bank apps continue to work despite device not being play certified, so I guess no root and safetynet would be required. Still, Im very sorry for now trusting you, and I would from now reconsider what Im doing. Lets hope it wont happen even again, peace
Edit: Also managed to get OTA updates and play certification back after relocking it, noice, updating to may patch shortly after recovering my data
MrTaffy said:
Alright, just finished relocking my bootloader. Yeah, no more software updates but I can still download them online, and they are security updates so i guess not really a big loss because no more OS updates (One ui 5.1 is final!). Still I HAVE to learn from this incident onwards, maybe on 3 years whenever the device would be too old like the s8 only then i would reconsider doing so. But for now I would stay with this stock rom and I would keep updating it time to time as needed. Everyone makes mistakes anyways. And yeah bank apps continue to work despite device not being play certified, so I guess no root and safetynet would be required. Still, Im very sorry for now trusting you, and I would from now reconsider what Im doing. Lets hope it wont happen even again, peace
Edit: Also managed to get OTA updates and play certification back after relocking it, noice, updating to may patch shortly after recovering my data
Click to expand...
Click to collapse
I understand
my team is a:
G781B Oneui 5.1 patch February binary 4.
I'm in stock, recovery, no encryption, root, kernel Klimbo or bandit.
I am more than satisfied.
a kernel that delivers power, overclock, etc.
For games it is plenty, for daily use it is wonderful.
Sorry if my previous translation sounds harsh.
Only that I currently install several roms, kernels, graphic drivers, etc.
they only cause bugs.
If you are looking for something stable I recommend stock and what I mention.
greetings.
In banking matters, there are modules for magisk, they worked for me.
mezacorleehone said:
I understand
my team is a:
G781B Oneui 5.1 patch February binary 4.
I'm in stock, recovery, no encryption, root, kernel Klimbo or bandit.
I am more than satisfied.
a kernel that delivers power, overclock, etc.
For games it is plenty, for daily use it is wonderful.
Sorry if my previous translation sounds harsh.
Only that I currently install several roms, kernels, graphic drivers, etc.
they only cause bugs.
If you are looking for something stable I recommend stock and what I mention.
greetings.
In banking matters, there are modules for magisk, they worked for me.
Click to expand...
Click to collapse
Yeah as I relocked my bootloader play certification and ota updates came back
No longer trusting those BS roms, only losers would do so. That rom has drained me much battery and only let me charge at 3W (Yeah I have charger with display, and this occured in real life!)?! What a BS rom tbh! The only positive point I managed to find was the Google feed, but who would burn their battery away just for google feed?! After reflashing stock rom much better!
Very important thing to consider if you even think about flashing a custom rom on your S20 FE 5G. DONT DO IT, YOU WOULD REGRET IT SHORTLY.
I have unlocked bootloader and OEM root.
Even so, I get updates that obviously I will not update.
The last strong update was 5.1 in February. We will not have 6.0, there is no point in updating.
I can go back from android 13 to 12 and 11. Is it necessary? No, but I have the option.
greetings.
mezacorleehone said:
I have unlocked bootloader and OEM root.
Even so, I get updates that obviously I will not update.
The last strong update was 5.1 in February. We will not have 6.0, there is no point in updating.
I can go back from android 13 to 12 and 11. Is it necessary? No, but I have the option.
greetings.
Click to expand...
Click to collapse
In the end security updates should protect us from any kind of exploits, including dangerous ones
But as the devices continues to discontinue (I mean, from october 2023 will start Quarterly updates and year later fully discontinued, the point would of course rise again. But until this happens the custom roms have a chance to delelop as time is going, and if there wont be atleast 1 GOOD custom rom, whats the point to attempt to flash a human managed ROM just to later report bugs to them, impacting your daily basis and ect?
After the last security update on about 2024 I believe custom roms would have chance to rise again, just like it was with the S8. S8 ROMs are better than the S20 FE 5G's ones. I need this time to let the custom roms develop, and once they are developed enough I would reconsider on installing one.
Until then, good luck
MrTaffy said:
In the end security updates should protect us from any kind of exploits, including dangerous ones
But as the devices continues to discontinue (I mean, from october 2023 will start Quarterly updates and year later fully discontinued, the point would of course rise again. But until this happens the custom roms have a chance to delelop as time is going, and if there wont be atleast 1 GOOD custom rom, whats the point to attempt to flash a human managed ROM just to later report bugs to them, impacting your daily basis and ect?
After the last security update on about 2024 I believe custom roms would have chance to rise again, just like it was with the S8. S8 ROMs are better than the S20 FE 5G's ones. I need this time to let the custom roms develop, and once they are developed enough I would reconsider on installing one.
Until then, good luck
Click to expand...
Click to collapse
I understand you.
The people who have the time to try the roms are appreciated and they are the ones who help the development.
in 2018 i had s9 snapdragon 845.
I was on oneui 2.5 android 10.
in your case you acquired s9 exynos. a jewel to know that note 10 lite would carry android 12 and 13.
They gave me an A7 2017, said note 10 lite managed to port oneui 2.5 android 10 (official was in 8.0 oreo)
I'm assuming your s9 runs android 13.
only that samsung Dex and iris lose or am I wrong?
Anyway, for day-to-day use, having the s9 with android 13 is great.
Yes, the roms for the s8 will be better, because the years have passed and the project is more mature.
mezacorleehone said:
I understand you.
The people who have the time to try the roms are appreciated and they are the ones who help the development.
in 2018 i had s9 snapdragon 845.
I was on oneui 2.5 android 10.
in your case you acquired s9 exynos. a jewel to know that note 10 lite would carry android 12 and 13.
They gave me an A7 2017, said note 10 lite managed to port oneui 2.5 android 10 (official was in 8.0 oreo)
I'm assuming your s9 runs android 13.
only that samsung Dex and iris lose or am I wrong?
Anyway, for day-to-day use, having the s9 with android 13 is great.
Yes, the roms for the s8 will be better, because the years have passed and the project is more mature.
Click to expand...
Click to collapse
I never had a s9 but I have a s8. The only problem with the S8 was that its latest One UI Rom is only maxed at One Ui 2.5 (Android 10, Hades ROM). Thats the only main one UI port available. You want to upgrade software? flash lineageOS then! Pretty dissapointing S8 only supports One UI 2.5 max meanwhile S9 supports one ui 5 max. And note 10 lite doesnt have as many custom roms as the S9. So just like the s8 got locked at one ui 2.5, the s9 would also lock at one ui 5? and after getting locked would the s9 users be forced to install stock android, just like on the case of the S8 users which the same happened to them earlier?
MrTaffy said:
I never had a s9 but I have a s8. The only problem with the S8 was that its latest One UI Rom is only maxed at One Ui 2.5 (Android 10, Hades ROM). Thats the only main one UI port available. You want to upgrade software? flash lineageOS then! Pretty dissapointing S8 only supports One UI 2.5 max meanwhile S9 supports one ui 5 max. And note 10 lite doesnt have as many custom roms as the S9. So just like the s8 got locked at one ui 2.5, the s9 would also lock at one ui 5? and after getting locked would the s9 users be forced to install stock android, just like on the case of the S8 users which the same happened to to earlier?
Click to expand...
Click to collapse
In the case of the s8 it is to be in 2.5 with android 10.
is a candidate for lineageos or gsi.
the exynos s9 will have up to oneui 5.1 ported from note 10 lite.
remember that originally it would be in 2.5 android 10.
you can still live with the s9 with note lite size on android13.
or at best go to s20 fe
Alright, an update after a while
Managed to successfully resolve the issue with Samsung health not working: I have installed a patched version and it's working like new. Just to note I shouldn't update it in any case. The only question is if it would sync with the watch. I mean it already can sync with the account, but I would to test it with the watch too. If everything is going fine I have no prob returning to Samsung. The fact I even didn't had to root to install modules only to patch this issue was wonderfull.
About secure folder and Samsung pass I don't care anymore about them and I had barely used them too, and I have no issue leaving them alone. Instead of secure folder I can use Google photo's safe to store my naughty photos, and about Samsung pass I can use Google passwords instead. Galaxy wearable has worked from day 1 since the issue no matter the incident.
This is a big lesson for my ass, and I shall be smart before doing naughty things like this again. Kids, please learn from me and don't be a stupid guy like me.