Related
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...
Hey guys,
I'm just looking for someone to point me in the right direction. Basically, my school has this web portal logon thing called Cloudpath (formerly xpressconnect) that requires you to log on to the portal's network in order to follow the instructions in your web browser for your specific OS. The problem arises with Android. It requires you to download an app, which does all the nitty gritty certificate installation and configuration for you. However, whenever I try this on a CUSTOM ROM (LOS-based and DU), I end up in a connecting loop. I never get connected to the secured network even though the certs appear to be installed correctly. I've tried using the app and doing it manually by downloading the certs myself. This only occurs on custom nougat roms, but works on stock MM (I haven't tried MM roms, because I want nougat).
As far as I know this problem only affects this phone after I install the rom and OpenGapps. Some of my peers have LOS and have gotten it to work, so I'm the only one, and the tech staff have no idea what to do. I don't have the log file on me, but if you need it, I can post it (they're pretty long, but seem to be detailed up until the connection part which just flops between CONNECTED and DISCONNECTED).
Is this a problem with the modem or the roms themselves? I was going to wait until the nougat kernel blobs got integrated to LOS, before trying again as I don't want to use the experimental build because it's a month old now. This problem has been around since at least January of this year. If there is a non-los based nougat rom, I would be glad to try that too. otherwise, I'm at a loss and I need some direction.
Any help is appreciated!
Seeings as how all of our Nougat ROMs are a mixed bag of partial MM and part Nougat still, and all custom ROM's for the MXPE use LoS's device tree, I am thinking this is a ROM issue, probably with some binary blob we don't have yet. The kernel source just released a few weeks ago, give it time and custom ROM's will get better (we think), and if the MXPE ever gets official Nougat, we will probably have better binary blobs too.
If it works on stock Marshmallow, it obviously isn't a radio thing, because your Nougat ROM's use the same radio firmware.
I don't have much else to say, but I would try a custom Marshmallow ROM and see if it works... if it fails as well, the problem is something in the LoS core device tree and it will need some developer's special attention (good luck with that, since we are considered to have a stable device tree it takes some work to get it changed), but if it works, chances are good that once custom Nougat ROMs get updated more it will likely work.
In a last ditch effort. I tried flashing the experimental build after posting this article, and it actually works! Now, this isn't the ideal situation given that there are some bugs (that I haven't run into yet) and that this build is a month old now. But for now, I'm satisfied. I just hope these blobs get integrated to official LOS soon.
Progress on that is here: https://review.lineageos.org/#/q/project:LineageOS/android_device_motorola_clark
If there are any roms out there that are considered stable and have these implemented now, I would appreciate it, otherwise, I think I'll be set for a little while. Thanks for your help!
See: https://forum.xda-developers.com/g4/development/lineageos-unofficial-builds-h815-t3726177
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Wuddelchen said:
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Click to expand...
Click to collapse
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Bleuzen said:
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Click to expand...
Click to collapse
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Wuddelchen said:
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Click to expand...
Click to collapse
Nobody knows. The bug exists since 2017-04-30, but nothing happens. And until the bug is not fixed, we don't get new official builds.
If you want to take the time to wipe and (re)setup your device is your decision.
But if you have the time, I would recommend it, mainly because of the security updates.
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
tulen_kobi said:
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
Click to expand...
Click to collapse
No, I didn't know that
Uh, there is work going on? This is great! I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Great to her that there is still developing going on
Well, I help where I can. But I'm new to Android.
I have experience with Linux, use it every day, and now I know how to build LineageOS. I also can do Java programming.
But I never developed something with Android already. So I don't know how much I can help.
Bleuzen said:
I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Click to expand...
Click to collapse
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Exabyter said:
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Click to expand...
Click to collapse
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Bleuzen said:
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Click to expand...
Click to collapse
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Exabyter said:
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Click to expand...
Click to collapse
Yep, looks good. I already tryed Oreo but it isn't complete already. But I'm looking forward to use and recommend it as new daily driver when it's ready
Hey guys! Some very talented developers have been working on unofficial releases for a while already, and I am unsure whether to go for their takes or wait until an Official version is released. Any predictions on when this might happen? Or should I just void my warranty and go for Vache's build? Thanks!!!
I might also like this. While Motorola says they will release Oreo for Potter, they seemingly haven't provided any timetable for that. I am a bit hesitant to install a LineageOS nightly on my daily driver, but I would love having the option, especially if it turns out that Motorola botches the Oreo upgrade.
jtull89 said:
I might also like this. While Motorola says they will release Oreo for Potter, they seemingly haven't provided any timetable for that. I am a bit hesitant to install a LineageOS nightly on my daily driver, but I would love having the option, especially if it turns out that Motorola botches the Oreo upgrade.
Click to expand...
Click to collapse
I have been using Vache's/fAIyaZ 7.1.2 build for some days now. Only found one bug, Skype wouldn't manage to access the camera for video-chatting, but I found a solution for it (activating Camera 2 API from this thread: https://forum.xda-developers.com/g5-plus/themes/potentially-google-camera-port-t3684264 ). Other than that, everything works perfectly (and a lot better than the Moto built-in tracking suite they ship the phone with).
Applying an unofficial fix to an unofficial port sounds a bit problematic. Do you think it would be possible for Vache/fAlyaZ to fix this in their port somehow? Or would it be more of a gapps thing? Or neither?
It seems so insane to me that there is no official LineageOS for Potter yet? I couldn't have even imagined that it wouldn't be released quickly when I bought the Moto G5 Plus - I though it is such a popular phone, so well reviewed for the price, able to be unlocked, etc. How can it no be better supported by the LineageOS team?
Sorry to necro this thread, but Oreo has now been officially released for Potter, after seemingly forever. What are the chances of getting an official 15.1 build for Potter any time soon?
I know Vache's unofficial build is much loved on here, and I think there's a 16.0 unofficial build I've seen flowing around as well, but some of us would rather go with an official build if one is available.
Don't mean to be a d*ck, but just follow the trending topics on the forum and you'll see where everyone has flocked to. At the moment I believe there's no need to program Lineage for Pie, when we have one extremely good AOSP based version online. Install the Pie version of the system that can be shot from a bow and never look back... Vache did a great job for as long as he did it, and a couple of other contributors too, so <3 thank you
now everyone seems to be somewhere else, that's how it goes
all the previous versions and knowledge gained from them kept being passed forward to ports from the next version of Android as well, so you'd have to look at Lineage Pie. Lineage16 seems to still be too raw for Potter, which means you likely won't see any official version soon. With Pie out, everyone's efforts turn to it, so you can see also that the 15.1 thread is pretty much dead.
Hello, i was in the process of finding out how to compile Dot OS rom to share here but realized that my my computer isnt strong enough to do so. Is there anyone willing to compile the rom for those of us who would like to use it? please and thanks. Also, if asking for a rom is in violation of anything please remove this post ;D
That would be great
I am actually planning to do a personal build of DotOS, if I succeed I will share it. (this only depends on my internet connection - which is slow: I will probably buy a VPS to do so).
That great yes
I didn't see this beforehand but I'm actually compiling a build of Dot-OS 2.4 based on 8.1 oreo Right now.
By all means, if someone was planning on maintaining unofficial builds be my guest. Still, I'll post my build on this comment when it's done in an hour or so.. Made with los tree, kernel and muppets vendor.
edit: I removed my build because of some issues with system overlays
AnierinB said:
I didn't see this beforehand but I'm actually compiling a build of Dot-OS 2.4 based on 8.1 oreo Right now.
By all means, if someone was planning on maintaining unofficial builds be my guest. Still, I'll post my build on this comment when it's done in an hour or so.. Made with los tree, kernel and muppets vendor.
edit: well here is my build based on the mentioned sources https://androidfilehost.com/?w=files&flid=279723
Click to expand...
Click to collapse
I actually wasn't planning to maintain it, you are free to do so. I successfully built my own version as well, but I have some issues with DotUICenter - basically the overlays do not work.
I am trying to download your build but AFH has a temporary mirror and it's extremely slow (60 to 80KB/s). Do the overlays work on your build?
Hello Any news about rom thanks
jet-27 said:
Hello Any news about rom thanks
Click to expand...
Click to collapse
Well I've personally discontinued work due to some overlay issues that I don't have the time to look into and fix.