Related
Latest rumors are that 5.1.1 for Moto G 1st gen would be released by end of June. This thread is created to track news about 5.1.1 and future issues with this release .
EDIT :
Looks like we are getting the 5.1 and not 5.1.1 as thought .
India Soak test available here Link .I think it should be the same for Asia
Let's hope beacuse last year europe region get 4.4.4 at end of July...
Really ,,, a new thread for this ,,,, Discuss in 5.1 thread
Source?
Sent from my XT1033 using XDA Premium 4 mobile app
https://plus.google.com/106984013892934805292/posts/FSy8Nm7aQ3k
well no....
[email protected] said:
Really ,,, a new thread for this ,,,, Discuss in 5.1 thread
Click to expand...
Click to collapse
The 5.1 thread I see is for GPE devices..This is for non-gpe devices most of which are dual sim .
Sent from my Nexus 7 using Tapatalk
Guys, this is getting worst every time... Just wait for that update to come! I started to see my Moto G as what it actually is: a phone! Another Android version won't do your phone better... Just grab a ROM if you want something better than stock firmware... Because I bet when the OTA comes, you will get bored of it and you will go again to CM12.1, won't you?
So this thread does not make much sense here...
Going by that statement there are many such threads which don't make sense ..It would be interesting to see if Motorola offers support for slightly older devices given that the firmware is almost pure android... Besides cm 12 doesn't seem to work well with dual Sim . Let's watch for few weeks and see how things pan out.
Sent from my Nexus 7 using Tapatalk
Cool, another update rumor thread. Just what was missing on XDA...
yes, give us 5.1!
I got the xt1032-en-GB. Anybody who got their update for that one yet? For 5.0 there was a thread showing the OTA release status for all regional versions, it'd be great to have something like this as well for this release. I tapped the "check for updates" button a couple of times today, but it gave me an error saying that it cannot check for updates right now.
Whoever says that the Moto G community on XDA is the worst... it's the opposite... and we deserve our updates btw, I disagree with the statement saying that an update won't do our phones any better...after that catastrophic, bug-infested Android 5.0 release (which is not Motorola's fault) any update is more than welcome. Kitkat was supposed to make phones with low specs speedy due to reduced resource usage, so it's quite amusing that everybody keeps reporting that their phones slowed down on all post-jellybean releases. Let's see if this is finally changing again with this release - ART was supposed to speed everything up again, isn't it? (oh and CM is not an alternative...it's the Duke Nukem Forever of Android ROMs, at least on this phone (since I never tested it on any others); I've tried that self proclaimed bug-free official Moto G CM a year ago which was developed by that guy who left, but unfortunately it was a crash-prone mess)
The Costum ROMs are not better at all when it ciomes to bugs and performance and not say memory management. Motorola stock firmware with Android 5.0.2 is good with memory leak fixed the system has just 125 MB consumed and a free of 600 MB vs Costum ROM or GPE 300 MB consumed by sysem and 300 MB Free.If Motorola release Android 5.1.1 with the memory leak and memory management fixed like 5.0.2 then I would be the best Android version for Moto G till then the GPe version with xpirt mod pack is the best as I tested with battery life and performance.
and yes that memory leak is still not fixed in the AOSP branch of Android 5.1.1
I just hope that Motorola will release soon Android 5.1 not when Google is releasing Android M.
The soak test for 5.1 has begun, so expect in a while.
lifetimes said:
The soak test for 5.1 has begun, so expect in a while.
Click to expand...
Click to collapse
Source or it didn't happen.
No Idea about Moto G 1 gen.
But in India the Moto E 1 gen. gets 5.1.
MOTO E
Android 5.1, Lollipop, is now rolling out in phases.
Owners will receive a notification on their phones when they are able to update.
Click to expand...
Click to collapse
David Schuster, Motorola's Senior Director of Software Management, had recently stated on his Google+ account that most of the company's devices would skip the 5.0 update and instead jump directly to 5.1 Lollipop. According to David, the 2013 Moto X, the 2013 Moto G, the 4G Moto G and the Moto E would all be updated directly to Android 5.1 Lollipop instead of getting 5.0 first
Click to expand...
Click to collapse
Source
I've got a uk 1039 and recieved the update this morning to 5.1.
are there still people who have the xt1032 or has it become smth exotic by now? I'm still waiting for the update on mine (8GB, UK version). Getting the impression that lenovo has released too many different variants of this phone
Its rather strange . 5.1.1 is a minor update from 5.1 ,and it was released few weeks after 5.1 , with few more bug fixes . Wondering why motorola didnt jump straight to 5.1.1 for MotoG..
That happens; there were a lot of devices who have been updated to 5.0.1 even though 5.0.2 or later was already out. Including Nexus devices.
So where is 5.1 for the XT1032 now?!
Haggster66 said:
That happens; there were a lot of devices who have been updated to 5.0.1 even though 5.0.2 or later was already out. Including Nexus devices.
So where is 5.1 for the XT1032 now?!
Click to expand...
Click to collapse
There is no definitive answer if we will get it or not.
"I see a lot of questions about when/if Moto G (1st Gen) will be getting updated to 5.1. The answer is yes... we are working on it. I know you guys want dates but we have run into a few complications so as soon as timing becomes a little more clear I will post an update.
UPDATE: I will have more info on Moto E (1st Gen) next week.... "
Source:
Code:
https://plus.google.com/u/0/+DavidSchuster/posts/aRNEjUCEe77
(I am not allowed to post links)
Hello G3 users, Android 6 is finally here ! Current available KDZ list below:
LG G3 D855 30B_GLOBAL_XX , thanks to @autoprime
LG G3 D855 30B_EUR_XX , thanks to @maxou2600
LG G3 F400L 30C_KR_XX , thanks to @ishanbhatnagr96
LG G3 F400K 30D_KR_XX, thanks to @Keaganvdh
LG G3 F400S 30C_KR_XX , thanks to @ishanbhatnagr96
LG G3 D858HK 30A_HK_XX
These KDZ's are compatible with both 16 and 32 GB versions of the phone, and they can be flashed using LG Flash Tool (2014).
I recommend you to do a CSE Flash if you're going to use the flash tool from above. You can flash this coming from any previous rom.
Also, if you get the error from the attachments while flashing, have no fear and keep the phone plugged in to the pc until the flashing is complete.
The main changes in Android 6 Marshmallow for the G3 are shown here.
For the secret menu the code is *#546368#*855# , thanks to @dszymek
First impressions from @KiaTheKing are available in the video below .
@KiaTheKing was also kind enough to make a tutorial on how to root android marshmallow
in the video below.
In attachments you have some pics, happy flashing !
I wish we get marshmallow and we don't stuck with the buggy 5.0
True that?
Seems that d855 is also close to marshmallow update.
http://bg.lgworld.com/web.lgsw.member.RetrievePhoneModelList.dev
http://uk.lgworld.com/web.lgsw.member.RetrievePhoneModelList.dev
I only hope that they will learn their lesson, and 6.0 won't be as slow and bugged as 20A..20W are...
i hope the aosp team will use marshmallow sources for their roms and not kitkat as they did with lollipop.. (camera driver is still kitkat.. kernel is still kitkat updated for lollipop)
I woke up to an OTA on my Sprint device this morning. It just downloaded it, I haven't installed it. Wonder if it's an incremental update to prep for 6.0.
Edit: Looks like this is the ZVB update that combats the stagefright exploit. Is this really something I should worry about? I wouldn't open media sent from an unknown party anyway.
Both Canadian models has Android 6.0 in the drop down.
I'm excited.
Oh man, really? For the D855/D852?
This is reassuring. I'm grateful I've chosen LG to go with my smartphone. I loved how I got my Lollipop update quickly last year, and I'd love to get the Marshmallow quickly as well.
This will definitely count towards my next upgrade. Previously I was thinking about the new Moto or HTC line, now I'm deciding between a G4 or a V10!
Or you could play nice and wait for g5.
Hope it won't be buggy
Only the Korean builts listed, not D855 at the moment. Hope LG do it again, like they did last year with LP upgrade, and we get MM anytime soon, then I will definitely stick with LG for my next phone too (summer 2016)
iLHaNroID said:
Only the Korean builts listed, not D855 at the moment. Hope LG do it again, like they did last year with LP upgrade, and we get MM anytime soon, then I will definitely stick with LG for my next phone too (summer 2016)
Click to expand...
Click to collapse
look at vanko11595's post...
looks like other G3 models have the 6.0 option
Maybe tomorrow
Sent from my LG-D855 using XDA Free mobile app
I hope the Battery life is better on Mashmellow...
hopefully it will be released in the coming months. I believe the source code is already with LG they just have to put their LG UI on top of it and make some modifications. Really wish that it would be a better implementation that stock lollipop was though.
Dude i think we will get it maybe next week
Sent from my LG-D855 using XDA Free mobile app
I think we can be happy if we get the official Marshmallow this year
D855 italian
theoverfiend said:
I think we can be happy if we get the official Marshmallow this year
Click to expand...
Click to collapse
Dude why they make android 6 on supportpage ? Are you crazy i think next week will get it this phone wins so many awards to lg update will be fast.
Sent from my LG-D855 using XDA Free mobile app
Hope to see more kernel and ROM options with this release.
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-SU4TL-44
I dont understand. This git says it is for the quark 5.1.1, but the Droid Turbo was the only variant that was brought to 5.1.1. As far as I know, Moto Maxx is stuck on 5.0.2. And if the Droid Turbo does not have an unlockable bootloader, than who is this kernel meant for? Just trying to understand what it means...
IonAphis said:
I dont understand. This git says it is for the quark 5.1.1, but the Droid Turbo was the only variant that was brought to 5.1.1. As far as I know, Moto Maxx is stuck on 5.0.2. And if the Droid Turbo does not have an unlockable bootloader, than who is this kernel meant for? Just trying to understand what it means...
Click to expand...
Click to collapse
1) Droid Turbo XT1254 does NOT have 5.1.1. They only have stock 5.1 from Motorola/Verizon as far as I know. Updated in July. If there was a later OS update, I missed it.
2) It's meant for anyone who has a Quark and can use it -- like the XT1225 and XT1250 (which is identical to the XT1254 -- same FCC ID) which do NOT have locked down bootloaders.
Motorola legally has to release the source code, even though Verizon has them lock down their Quark -- the XT1254. This will help CM and others make better custom ROMs for our Quarks.
We have had 5.1.1 for MONTHS. Not from Motorola, who couldn't care less, but from CM and others who used CM sources. (Thank @Skrilax_CZ, CM team member who bought an XT1225!) We now have FOUR custom 5.1.1 ROMs. However, CM had to use 5.0.2 kernel with 5.1.1. It was Lollipop 5.1.1 with a 5.0.2. Lollipop kernel. Now they can use updated kernel sources! :good:
Skrilax_CZ said:
Meanwhile Motorola released the 5.1 kernel sources at last, so next steps will be to update the proprietaries and rebase the kernel.
Click to expand...
Click to collapse
PwrUsr said:
Hope to see more kernel and ROM options with this release.
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-SU4TL-44
Click to expand...
Click to collapse
" SU4TL-44 "
This is the kernel source for Droid Turbo' s SU4TL-44 firmware, not related to Moto Maxx.
Semseddin said:
" SU4TL-44 "
This is the kernel source for Droid Turbo' s SU4TL-44 firmware, not related to Moto Maxx.
Click to expand...
Click to collapse
It says it's kernel source for Quark.
Quark push for lollipop 5.1.1
Click to expand...
Click to collapse
We have Quarks.
There's also this XDA article, pointing to the exact same link:
Motorola Releases the 5.1.1 Kernel Source Code for the Moto Maxx
http://www.xda-developers.com/xda-e...e-5-1-1-kernel-source-code-for-the-moto-maxx/
Plus I trust this:
@Skrilax_CZ says Motorola has released the 5.1 kernel sources. He was specifically waiting for what Motorola/Verizon gave Droid Turbo users in July. Took Motorola almost 4 months to release it. I'm pretty sure this is what he's talking about.
Skrilax_CZ said:
Meanwhile Motorola released the 5.1 kernel sources at last, so next steps will be to update the proprietaries and rebase the kernel.
Click to expand...
Click to collapse
So, it is related to the Moto Maxx. It's related to all Quarks.
Down in the CM12.1 thread, he and @baybutcher27 have been discussing it in depth. See a couple of posts here:
baybutcher27 said:
@Skrilax_CZ
Have you made wifi working using cm-12.1-5.1.1 kernel tree?
I have not. I try different then you, I merge moto 5.1.1 on the top of 3.10.90, I know that folder have 5.0.2 files and that may creating a bug, but i wanna to try.
I use the existent qcacld-2.0 of CM12.1 and later update from motorola, but wifi doesn't work no matter what qcacld-2.0 I use, I did not make a ROM just a boot and flash those wifi system files that get compile with. Will try to make a ROM to see if the ROM woks but only if you manage to make it work, (make a ROM take too much time)...
The sound files need to be used are those left.tfa9890.*** form su44, I have tested it after flashing it sound is good. Su 44 doesn't have tfa9890.*** it just have left.tfa9890.***.
The wave doesn't work either(The visible red dot sensors on the device lights up but the screen not), after I flash su 44 sensors files, wave doesn't work either and the red dot sensor doesn't light up. But that may be related to the way I merge...
The rest seemed ok.
Click to expand...
Click to collapse
Skrilax_CZ said:
I'm still working on that, have not checked yet if I configured the qcacld-2.0 correctly (different from main now, taken as is from Moto's makefiles). Use the one that you compile with the kernel, but it's stipl WIP. Much of the WIP stuff isn't pushed yet, such as the sound files.
There can be some changes in the devicr tree necessary with respect to the IR sensors.
Click to expand...
Click to collapse
_____________
@baybutcher27 is the person who gave us the official Lollipop compatible TWRP for our Quarks. He also gave us first custom kernel (BHB27-Kernel for Quark, based on CM's sources but with many custom properties) and maintains two different custom 5.1.1 ROMs. And we know the talents of @Skrilax_CZ.
Will the Moto X Play get android N?
Definitely , will get android O also.
drmuruga said:
Definitely , will get android O also.
Click to expand...
Click to collapse
Are you sure? http://www.xda-developers.com/curre...o-receive-android-ns-seamless-update-feature/
bilbo75 said:
Are you sure? http://www.xda-developers.com/curre...o-receive-android-ns-seamless-update-feature/
Click to expand...
Click to collapse
When talking about marshmallow , there is more rumors about rooting at first now it is simplest one. There will be some chances for androin N for x play.without able to update android N will be a massive failure , even moto g4 released with mm this month , with nearly same specifications of moto x play , It will get android N in few months then our x play definitely will get. If official update was not given for our device, we will get cm 14 or any aosp 7.0 by our great developers. Are you see, some marshmallow features are already seen in 5.1 custom roms . and android N features multi window like already in mm ROMs , I think android N is getting features from custom mm ROMs .
drmuruga said:
When talking about marshmallow , there is more rumors about rooting at first now it is simplest one. There will be some chances for androin N for x play.without able to update android N will be a massive failure , even moto g4 released with mm this month , with nearly same specifications of moto x play , It will get android N in few months then our x play definitely will get. If official update was not given for our device, we will get cm 14 or any aosp 7.0 by our great developers. Are you see, some marshmallow features are already seen in 5.1 custom roms . and android N features multi window like already in mm ROMs , I think android N is getting features from custom mm ROMs .
Click to expand...
Click to collapse
just worried about the partition issue. It could be a big problem
bilbo75 said:
just worried about the partition issue. It could be a big problem
Click to expand...
Click to collapse
But hey, at least the silver lining on the table is that we here at XDA will find a way. We always do, don’t we?
bilbo75 said:
just worried about the partition issue. It could be a big problem
Click to expand...
Click to collapse
It's only problematic to make "seamless" update work and not update in general. The idea of "seamless" one is that your phone would download and install the update in the background and simply switched to the new system on reboot, so the whole installation process is invisible to users. We can still update to N or O, or maybe even further in a "classic" way.
bilbo75 said:
just worried about the partition issue. It could be a big problem
Click to expand...
Click to collapse
Partition issue is just for seamless background update which not even current nexus would get. So chill.
I was talking with CEO of Lenovo Slovakia and according to him, moto x play will get android N for sure
When google releses the code base for N O or whatever there will be something for the developers to work on. The stabel ota from will be probably in 2017 Q1.
Guys Motorola just released list of devices that will be officially supported for Android 7.0.Unfortunately Moto Turbo did not make into that list.Now i see no chances in future too Although Droid Turbo 2 made into that list
The Droid Turbo is still waiting on Marshmallow, let alone Nougat. Its international model, the Maxx, didn't even get MM until earlier this year. We'll probably be lucky if we get official MM at all.
Speaking of which, the Maxx isn't on the list either, which doesn't bode well. Probably going to have to wait and hope someone builds CM14 for our phone, if you want Nougat.
CM14 (Nougat) will come for Quark
cure25 said:
Guys Motorola just released list of devices that will be officially supported for Android 7.0.
Unfortunately Moto Turbo did not make into that list.
Now i see no chances in future too although Droid Turbo 2 made into that list
Click to expand...
Click to collapse
You are referring to this updated Nougat device list from Motorola:
http://motorola-blog.blogspot.co.uk/2016/10/n-is-for-nougat-android-70-is-coming-to.html
There was an earlier list 3 months ago, with more devices to be added at a "later date". Yeah, no Quark phones made the updated list.
Of course, the Droid Turbo XT1254 made the Motorola "Marshmallow" list back on October 2, 2015 but Verizon deigned not release it to Droid Turbo owners (yet or maybe ever).
Septfox said:
The Droid Turbo is still waiting on Marshmallow, let alone Nougat. Its international model, the Maxx, didn't even get MM until earlier this year. We'll probably be lucky if we get official MM at all.
Speaking of which, the Maxx isn't on the list either, which doesn't bode well. Probably going to have to wait and hope someone builds CM14 for our phone, if you want Nougat.
Click to expand...
Click to collapse
That someone is our CM dev @Skrilax_CZ, and he has already committed to that.
Quark got Lollipop before Motorola gave it to us (March 2014 vs April 2015), Marshmallow before Motorola gave it to us (February 2016 vs July 2016) and will get Nougat. He's just waiting until nightlies for any CM14 ROM starts rolling out.
20th September 2016, 12:34 AM
Skrilax_CZ said:
I usually start porting when CM14 official nightlies start. CM14 is just too unstable right now. Although since I have 2nd MAXX, I might look on it a bit earlier
Click to expand...
Click to collapse
Then, after Quark CM14 -- especially the kernel work -- other ROMs can build on that framework. We have 7 custom Marshmallow ROMs for the Quark (maybe 8 depending on how you count) -- they work on ALL Quarks, thanks to our CM dev. '
No reason we won't have just as many Nougat based ROMs.
Here's hoping that CM14 fixes the signal issues of CM13
I unlocked my bootloader (SU4TL-49) but now puzzled if I should wait for CM14 or install CM13 now...
I am new to installing a custom ROM and don't know if it is worth the time to install a soon-to-be outdated ROM.
Also, if the recommendation will be to still install now, which ROM to get. Just sick of Verizon and Motorola crap.
Thanks
a_cipher said:
I unlocked my bootloader (SU4TL-49) but now puzzled if I should wait for CM14 or install CM13 now...
I am new to installing a custom ROM and don't know if it is worth the time to install a soon-to-be outdated ROM.
Also, if the recommendation will be to still install now, which ROM to get. Just sick of Verizon and Motorola crap.
Thanks
Click to expand...
Click to collapse
Install now. CM13 (Marshmallow) was in "beta"/preview the first month. (And that "first month" for CM14 Quark ROM may not be until November.) Whereas CM12.1 (Lollipop) was rock solid. I didn't switch to a Marshmallow ROM for awhile, from CM12.1.
Go with the stable ROM (CM13) or other Marshmallow ROM for now. You can always change by end of the year.
You may even like Marshmallow Bliss or Resurrection Remix ROMs better than CM13. They seem to be the two most popular right now.
Edit: changed a word with a synonym so it would be understood without a negative connotation:
I'm typically a cyanogenmod fan and I used cm on this device since it was stable until a few weeks ago.
I'm currently rocking marshmallow Nexus experience rom, but before I go back to cm13 I'm going to try mokee.
Resurrection remix and bliss are filled with features. This is NOT a bad thing it is just features I hold little interest in and I keep finding myself just going back to cm.
Nexus experience doesn't screen cast right. Other than that it works great.
Cm13 doesn't pass Android pay or Pokemon go security checks. Rooting is NOT enough. So if you use either app my recommendation is Resurrection remix, Nexus experience or stock brazil marshmallow without volte
ALL Roms other than stock lollipop based Roms do NOT support volte (data during phone calls)
ChazzMatt and mrkhigh,
I can't thank you enough for quick and detailed responses!
Sounds great, I'll do some more reading on those roms and decide which one to get.
Thanks!
mrkhigh said:
I'm typically a cyanogenmod fan and I used cm on this device since it was stable until a few weeks ago.
I'm currently rocking marshmallow Nexus experience rom, but before I go back to cm13 I'm going to try mokee.
Resurrection remix and bliss are "bloated" with features. This is NOT a bad thing it is just features I hold little interest in and I keep finding myself just going back to cm.
Nexus experience doesn't screen cast right. Other than that it works great.
Cm13 doesn't pass Android pay or Pokemon go security checks. Rooting is NOT enough. So if you use either app my recommendation is Resurrection remix, Nexus experience or stock brazil marshmallow without volte
ALL Roms other than stock lollipop based Roms do NOT support volte (data during phone calls)
Click to expand...
Click to collapse
Bliss isn't "bloated", it has the smallest footprint of any ROM I've built or used. And it reboots in under 30 seconds, my Keurig isn't that fast. @bhb27 is constantly working on RR, and it's the most popular/downloaded ROM we have, no doubt about it.
VoLTE is something you have to sacrifice in order to use a custom ROM. bhb is trying to fix that too, but unfortunately, he lives in Brazil and is not a VZW customer.
I know that you know what you're talking about (been around long enough to see that), but to say Bliss is "bloated"...
My apologies. You took it wrong... I said it was bloated with features.... Meaning lots and lots of features.
They are features I don't use. So for me they are by definition 'bloat' but i did then say that's not a bad thing.
Probably a poor choice of words since it is often used negatively. Kinda like the word ignorant sounds bad but it would be completely correct to say "I'm ignorant in Pascal coding."
Bliss is an amazing rom. Just like cm rr and mokee.
---------- Post added at 12:47 PM ---------- Previous post was at 12:41 PM ----------
Edited statement above so nobody else would mistake what I was trying to say. It now reads filled
mrkhigh said:
My apologies. You took it wrong... I said it was bloated with features.... Meaning lots and lots of features.
They are features I don't use. So for me they are by definition 'bloat' but i did then say that's not a bad thing.
Probably a poor choice of words since it is often used negatively. Kinda like the word ignorant sounds bad but it would be completely correct to say "I'm ignorant in Pascal coding."
Bliss is an amazing rom. Just like cm rr and mokee.
---------- Post added at 12:47 PM ---------- Previous post was at 12:41 PM ----------
Edited statement above so nobody else would mistake what I was trying to say. It now reads filled
Click to expand...
Click to collapse
Words are funny like that, yes? Everyone has their own opinion when it comes to a custom ROM (good thing we have many to choose from, lol), I just misinterpreted your meaning of "bloat", so: My apologies to you as well :highfive:
mrkhigh said:
Edit: changed a word with a synonym so it would be understood without a negative connotation:
I'm typically a cyanogenmod fan and I used cm on this device since it was stable until a few weeks ago.
I'm currently rocking marshmallow Nexus experience rom, but before I go back to cm13 I'm going to try mokee.
Resurrection remix and bliss are filled with features. This is NOT a bad thing it is just features I hold little interest in and I keep finding myself just going back to cm.
Nexus experience doesn't screen cast right. Other than that it works great.
Cm13 doesn't pass Android pay or Pokemon go security checks. Rooting is NOT enough. So if you use either app my recommendation is Resurrection remix, Nexus experience or stock brazil marshmallow without volte
ALL Roms other than stock lollipop based Roms do NOT support volte (data during phone calls)
Click to expand...
Click to collapse
I've been considering leaving CM13 do I can use Android Pay and Pokemon Go(my son loves to play) which ROM do you recommend, Nexus experience or Brazilian stock? Which one is less hassle to get those apps working?
kingersj1 said:
I've been considering leaving CM13 do I can use Android Pay and Pokemon Go(my son loves to play) which ROM do you recommend, Nexus experience or Brazilian stock? Which one is less hassle to get those apps working?
Click to expand...
Click to collapse
Neither. If you want those things, you'll need to install the latest official Motorola release for your Droid Turbo, and nothing else. The latest update to SafetyNet broke the workarounds that were used in CM-based ROMS (Brazilian stock never passed SafetyNet at all, even without root or xposed installed). I think suhide might still work, but only on a stock marshmallow ROM that passes SafetyNet, and we don't have that.
EDIT: Never mind. I might be wrong about all of that. Check out Resurrection Remix. The dev has added a companion app called iSu that works as of 3 days ago for hiding root (stock CM root, do not install SuperSU), and apparently it passes safetynet.
JFYKI, I haven't tried out Bliss yet but I noticed that ROM size is 330mb for Bliss while RR is 273mb. I am quite satisfied with latest version of RR on XT1254.
The size of the system partition, if I'm not mistaken and assuming you have not manually resized it, is about 3 GB. So I'm pretty sure neither Bliss nor RR is going to fill that up anytime soon. But if you can somehow fill up that partition with mods that need over 10 times the space of the base OS, you are my hero.
The system partition is 1.94gb and I haven't ever resized the partition. With stock based ROMs, I was struggling with space on system partition. You're correct that with almost everything installed that I need, there's still 500+mb available.
kingersj1 said:
I've been considering leaving CM13 do I can use Android Pay and Pokemon Go(my son loves to play) which ROM do you recommend, Nexus experience or Brazilian stock? Which one is less hassle to get those apps working?
Click to expand...
Click to collapse
RR is your best bet. Use the iSU app and you can "keep" root
I'm currently using it due to that exact reason.
With nexus you'll have to simply "unroot" I left that ROM because face book kept locking up?!
And I would ASSUME the Brazil ROM would work out of the box since I do not believe it includes root.
Resurrection remix works just fine
Fwiw I think Brazil ROM no root would be a great choice as well. Nexus was buggy with Facebook for some reason but unrooted it passed safety net
Cm13 will NOT pass even unrooted. No idea why.
Brazilian does not play nice with Xposed...