Related
This is an invitation to all developers, compilers and testers of Moto X (2014).
We know that probably our device will not receive officially Nougat update and this is really bad, assuming that our strong Snapdragon 801 can smoothly run without any problems.
My suggestion it's to all developers and compilers from any country work together to sync AOSP from Nougat, adapt device tree and bring up our first AOSP 7.0 rom.
I know that CyanogenMod is working on CM14 for victara... But the idea is bring up pure Android. I never see any pure AOSP rom for our device and would be awesome if we have this now. CM14 maybe will delay a bit and I think that all users here want to feel Nougat experience
Some rumours at internet had saying that Snapdragon 800/801 will not have drivers for Nougat... But I know that this is possible because Nexus 5 had Snap 800 and developers already bring an functional AOSP (link: http://forum.xda-developers.com/google-nexus-5/orig-development/wip-aosp-nougat-nexus-5-t3446875 ). Our developers can check device tree from Nexus 5... See their adaptions in device tree for working Nougat and try to do the same for our Moto X. Maybe disabling Vulkan API for now and we can use same drivers and device tree of Marshmallow!
That's all guys, thanks for reading and we are really expecting an AOSP Nougat for our Moto X before CM14!
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Visi0nofExcellence2 said:
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Click to expand...
Click to collapse
I agree, we have small team of developers. And this one more objective of this post: attract more developers.
I think that Moto X doens't have too much developers because we had officially updates since Android 4.4... Numbers of people that goes to custom ROMs is really minimal, because the stock of Motorola doens't give reasons to search custom ROMs (like bloatwares or lags).
But now, we are going to road of needing custom ROMs. Now we have more reasons to search for these ROMs, because we'll probably not receive Nougat. Moto X2 XDA Forum go clog of peoples trying to got Nougat.
I hope for a "pure" aosp too, like the "fake rom" for Nexus 4.
Enviado desde mi XT1095 mediante Tapatalk
cpvm said:
I hope for a "pure" aosp too, like the "fake rom" for Nexus 4.
Enviado desde mi XT1095 mediante Tapatalk
Click to expand...
Click to collapse
Would be awesome
Pls devs we need some nougat !!!
Visi0nofExcellence2 said:
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Click to expand...
Click to collapse
Dan(Invisiblek) is working on CM14 for Victara. http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_motorola_victara+branch:cm-14.0
and our CM13 Nighly builds is very close to a Snapshot build NO BUGS for me xt1092 very stable as Snapshot build.
Yes it's true . I have been using the nightly builds of CM 13 for Victara and it runs really smoothly. I would encourage developers to work on the Nougat ROM for Victara. We will appreciate it. Thanks
I really hope to see Nougat in this phone, sadly I have no knowledge to help in development, but for sure I will test as it become usable material (its my daily phone, so would be nice that alarm at least works as expected)
We already has an bootable CM14 guys! here's link: http://forum.xda-developers.com/showpost.php?p=68555035&postcount=100
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...
Hello everyone, I know that is something almost impossible but I have tried to launch a petition to motorola / lenovo to ensure that releases least marshmallow on the fantastic moto g 2013, all you have to do is a little sign at this link:
thanks in advance to all those who will participate.
p.s. sorry for my bad english
If u would flash a custom ROM u could enjoy the taste of nougat!!!
Moto did treat Falcon very well compared to how other OEMs behave.
Jelly Bean (4.3) - KitKat (4.4.2) - KitKat (4.4.4) - Lollipop (5.0.1) - Lollipop (5.1)
And there already is a Stock Motorola Marshmallow ROM available:
[ROM][FALCON][6.0][STOCK] Identity Crisis 6
Oh man..you're still stuck with petitions while Motorola has been eaten by Lenovo..
I understand the initial hesitation for unlocking bootloader and flashing a custom rom. It is assumed that custom roms will never be as stable as stock roms and it will keep rebooting,apps crashing..and what not. .
Listen man, moto g 2013 is history long back. If you want marshmallow,unlock bootloader first, unlocking the bootloader of motorola had been one of the easiest and it has great developers. There are plenty of marshmallow roms and after I write this post, I am going to download the updated Nougat rom by @srisurya95. I have been using it since 28 Sep and its smooth,stable, never had a single random reboot or any wild battery drain. Enter the world of custom roms and forget the official support. Here's the link to the rom.
http://forum.xda-developers.com/moto-g/development/rom-aosp-oms-substratum-moto-g-t3469861
IMO moto g 2103 is the only phone which got the best update from the manufacture till date
Enough update we got already.....
Well...
Sent from my Moto G using XDA Labs
LeleStasy said:
Hello everyone, I know that is something almost impossible but I have tried to launch a petition to motorola / lenovo to ensure that releases least marshmallow on the fantastic moto g 2013, all you have to do is a little sign at this link:
thanks in advance to all those who will participate.
p.s. sorry for my bad english
Click to expand...
Click to collapse
People launch petitions for literally anything these days.
lets face it, droid turbo community is dead , nexus 5 with SD 800 have android O !
while our much powerful OG droid stuck on MM or N, and i am not talking about 25$ , it's just xda is the place were you get stuff for free , that's just sad seeing a good device feed away.
droid_ulti said:
lets face it, droid turbo community is dead , nexus 5 with SD 800 have android O !
while our much powerful OG droid stuck on MM or N, and i am not talking about 25$ , it's just xda is the place were you get stuff for free , that's just sad seeing a good device feed away.
Click to expand...
Click to collapse
I'm sorry that you failed to include that in your purchase price . That's your fault.
If Bootloader unlock is that important to you you would've researched and known the cost.
Blame Verizon -- they are the ones that locked down the Bootloader on the droid turbo. The other Quarks have free Bootloader unlock, courtesy of Motorola. Sunshine devs gave Droid Turbo bootloader unlock, so they could join the party. Without them, Droid Turbo would still not have bootloader unlock -- like the Droid Turbo 2.
The XT1250 is identical to the Droid Turbo, with all the Verizon bands, and runs on Verizon just fine. The XT1225 has more LTE and HSPA bands than the Droid Turbo XT1254.
You didn't research before buying.
Quark will also get Oreo, so I don't understand your point there. All LOS-based Quark ROMs are compatible with all Quarks.
Maybe you don't don't about the OTHER Quark forum on XDA? All the dev work is over there. And it's also for the Droid Turbo.
Sent via open market LG US998 V30/V30+
lol man , you missing the point , i don't have issue with paying 25$ in fact my droid is boot-loader unlocked right now using sunshine , the point is community is dead we don't have a variety of roms like the same era phones such as htc m8 and smasung s5 and z2/z3 nexus 5/6 etc , even my 2012 lg l3 have more roms droid turbo, the unlocking boot-loaeder and sunshine was obstacles against all this wonderful hacking and moding things we could do.
droid_ulti said:
lol man , you missing the point , i don't have issue with paying 25$ in fact my droid is boot-loader unlocked right now using sunshine , the point is community is dead we don't have a variety of roms like the same era phones such as htc m8 and smasung s5 and z2/z3 nexus 5/6 etc , even my 2012 lg l3 have more roms droid turbo, the unlocking boot-loaeder and sunshine was obstacles against all this wonderful hacking and moding things we could do.
Click to expand...
Click to collapse
You missed my point. Droid Turbo XT1254 is only one Quark of three, all of which use the exact same LOS-based ROMs.
It would be like LG G3 was divided up into three different model names. The internal name was Quark, but the global consumer name for this device was Moto Maxx -- even for the U.S. model, but Verizon demanded an "exclusive", so theirs was named "Droid Turbo". But the XT1254 exactly the same phone as the XT1250 -- just has a locked down bootloader. It wasn't exclusive in any way. Other carriers in the U.S. sold the Moto Max XT1250, which has the same FCC ID as the the Droid Turbo XT1254.
Then the XT1225 Moto Maxx was renamed Moto Turbo for India, but it's the exact same FCC ID device as the XT1225 Moto Maxx.
Droid Turbo is the only one with locked down bootloader. The others are not. So, nothing is preventing development unless you INSIST on buying the only Quark with locked down bootloader, and didn't research before buying.
That's why all the development for Quarks, including the Droid Turbo is posted in the OTHER QUARK forum. Like TWRP, custom kernels, most of the ROMs.
Your whole premise is flawed. You think people HAVE to buy Droid Turbo or nothing. No, they can buy one of the other Quarks and have free bootloader unlock.
* With XT1225 they can have more LTE and HSPA bands.
* With XT1250 they can have all the Verizon CDMA and Verizon LTE bands.
The Droid Turbo XT1254 is the least desirable of all the Quarks... But if you buy it, be sure to factor in $25 for bootloader unlock. The others have free bootloader unlock.
Sent via open market LG US998 V30/V30+
people buy the Verizon droid turbo over the other Quarks because the price and availability , being said that i think most Quark users are using xt1254 plus it is compatible with CDMA and GSM that's why the user go for xt1254 which is the most desirable,
any the phone is three years old can't people around the globe who are using xt1254 get a free unlock !
droid_ulti said:
people buy the Verizon droid turbo over the other Quarks because the price and availability , being said that i think most Quark users are using xt1254 plus it is compatible with CDMA and GSM that's why the user go for xt1254 which is the most desirable,
any the phone is three years old can't people around the globe who are using xt1254 get a free unlock !
Click to expand...
Click to collapse
Again, you have it wrong.
Why do you think the Droid Turbo is cheaper? Because you have to factor in extra $25 into the purchase price for bootloader unlock. The REAL price is $25 MORE than you paid. People who buy it have to do that -- if bootloader unlocked and root is important to them. Thus, Droid Turbo SEEMS cheaper...
If there was "free bootloader unlock", Droid Turbos would then become more expensive as the price would rise. Just like 2015 Kinzie -- Verizon Droid Turbo 2 are much cheaper because they don't have bootloader unlock, but sibling Moto X Force is more expensive because it's BETTER -- it has free bootloader unlock from Motorola.
Why do you think the other Quarks (XT1250/XT1225) are more expensive? Because they are better. Free bootloader unlock from Motorola.
Outside the U.S. CDMA is mostly useless. Most of the world detests CDMA and doesn't use it. The XT1225 has more LTE and HSPA bands than the XT1254/XT1250 and doesn't have useless CDMA.. It has 64GB storage and FREE bootloader unlock, whereas most XT1254 have 32GB storage (yes, some have 64GB but not many) and you have to pay $25 for bootloader unlock and it's sometimes not easy to do. So XT1225 is worth more money.
____
Sunshine team publicly released the vulnerability they use. Anyone that wants can code free bootloader unlock. Nothing is stopping anyone from coding and releasing it.
But you seem to be blaming the devs who are offering a solution. If there was no Sunshine, you would HAVE to buy XT1250 or XT1225 -- or another phone altogether.
The Verizon Droid Turbo 2 (Kinzie) never got bootloader unlock, so people HAVE to buy the free bootloader unlock Moto X Force (Kinzie) if they want root and custom ROMs. Tons of people would LOVE the opportunity to pay $25 to unlock their Droid Turbo 2!
Sent via open market LG US998 V30/V30+
Here's news about Oreo ROMs for Quark, and the current list of Nougat ROMs. Since you're new, you may have missed this.
https://forum.xda-developers.com/showpost.php?p=75679114&postcount=94
Oreo needs at least Kernel 4.4. To prevent false hopes, it still should be called Resurrection Remix.
It's a bit like installing Vista themes on Windows XP back in the days...
lem22 said:
Oreo needs at least Kernel 4.4. To prevent false hopes, it still should be called Resurrection Remix.
It's a bit like installing Vista themes on Windows XP back in the days...
Click to expand...
Click to collapse
SUMMARY: you're never going to have a kernel for a device which was not first released by the OEM, in this case Motorola.
________
Call the kernel Resurrection Remix? It seems you are confusing kernels with specific ROM names? Maybe you are making a joke, I'm not sure.
Once we have a compatible kernel in the LOS tree to that will run on Oreo, any ROM maintainer can package and release a ROM. @bhb27, our kernel developer also maintains Resurrection Remix ROM. But there's also LOS, crDroid, etc. All the current ROMs will probably follow to Oreo. We may even attract some new ones.
An Oreo compatible kernel is the FOUNDATION for any Oreo ROM. You need that first. But you can't just create a kernel out of thin air. You need to adapt the kernel sources the OEM (in this case Motorola) has released publicly.
_________
Here's the problem with the kernel -- and I'm not an expert on kernels, but I'll explain it the best I can.
When our former official CM dev @Skrilax_CZ started this work back in early 2015, he had to take Motorola KitKat kernel sources and adapt it to work with Lollipop CM 12.0 (March 2015) and then CM12.1 (April 2015). We had Lollipop CM custom ROM BEFORE Motorola gave us Lollipop.
Motorola did release official Lollipop, but didn't release Lollipop kernel sources until like July 2015. At that point our CM dev @Skrilax_CZ then updated the CM kernel to "Lollipop" kernel. Until then for many months, we had Lollipop ROMs running on Kitkat kernel.
WHY? Because you can't just create a kernel that will run on a phone from scratch. You have to adapt the kernel the OEM has made for it.
Then, same thing happened with Marshmallow. For awhile, we had Marshmallow ROMs running on "Lollipop" kernel. Then Motorola released Marshmallow kernel sources and now we have "Marshmallow" kernel. During this time frame (Marshmallow to Nougat) was when @bhb27 took over kernel coding duties.
Well, guess what? Marshmallow was the last firmware Motorola ever released for Quark.
Yet, we have Nougat ROMs -- running on Marshmallow kernel. (Thanks to @bhb27)
If we ever get Oreo -- it will be Oreo running on Marshmallow kernel. (Thanks to @bhb27).
So, no I'd pretty much bet you will never get Linux Kernel 4.4 running on any Quark. If you want that, you would need official OEM kernel coding -- with stock official Oreo ROM -- which is only available with currently supported hardware. XDA devs with skill give life to older devices like these 2014 phones, but there's limits to what they can do.
I have Linux kernel 4.4.63 on my LG V30 US998, but it's a new phone. LG codes that kernel. Three years from now if I still have this phone, any ROMs in running will have to be using kernel sources from LG.
Just like any Quark will need kernel sources from Motorola -- and the last available is Marshmallow kernel, circa 2016.
lem22 said:
Oreo needs at least Kernel 4.4
Click to expand...
Click to collapse
Not true. See link for LOS 15.1 for Nexus 4, Linux kernel 3.4: https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
lem22 said:
Oreo needs at least Kernel 4.4.
Click to expand...
Click to collapse
TheSt33v said:
Not true. See link for LOS 15.1 for (2012) Nexus 4, Linux kernel 3.4:
https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
Click to expand...
Click to collapse
If he actually meant that, then he's wrong. I pointed out how he was wrong in thinking that older devices running Oreo custom ROMs will ever get Linux kernel 4.4. You need OEM kernel sources for that, and most OEMs aren't going to release Oreo firmware for older phones (like our 2014 Quarks). Because they want you to buy NEW phones. So, devs have to adapt the last kernel sources they have (for Marshmallow, in this case) to work on newer OS. No one except the OEM can make a brand new 4.4.x kernel for an old device.
But I thought he meant "need" as in "want". So, it would run better or something.
Me: We need a new TV.
Wife: No, you want a new TV.
Nexus devices were very open source, so great that a 2012 phone (LG Nexus 4) has Oreo. I skipped that Nexus. I had the gen3 Galaxy Nexus and the gen5 LG Nexus 5 -- as well as the Nexus 9 tablet (which my wife still uses).
lem22 said:
Oreo needs at least Kernel 4.4.
Click to expand...
Click to collapse
For Oreo, the Quark kernel has to be adapted from Motorola Marshmallow kernel to Oreo. @bhb27 did that with Nougat, but Oreo is harder.
A while back, he posted a screenshot of Oreo booted on Quark but still not stable. When he has news he will post about it again. One of the problems is he has one phone, which is his daily phone he has to use to live and work and also doubles as his development phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TheSt33v said:
Not true. See link for LOS 15.1 for Nexus 4, Linux kernel 3.4: https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
Click to expand...
Click to collapse
LOS is LOS and afaik called "15.1" instead of "Oreo" (for good reasons). Google requires kernel 4.4* as the minimum. Therefore, Android™ Oreo® cannot have an older kernel.
I know that for example RR uses "Oreo" in the name too, but I doubt they are allowed to do so since it's a registered trademark.
* or 3.18 for older SoCs resp.
lem22 said:
LOS is LOS and afaik called "15.1" instead of "Oreo" (for good reasons). Google requires kernel 4.4 as the minimum. Therefore, Android™ Oreo® cannot have an older kernel.
Click to expand...
Click to collapse
Oreo is the name given to Android OS version 8.X. Lineage OS 15.1 is a modified fork of the latest Android Open Source Project (Android 8.1). If you install LOS 15.1 on your device and check the Android version, it will tell you 8.1.
Google's kernel requirement is for OEM's manufacturing devices that will launch with Android 8.X and is necessary (or at least preferred) to maintain Project Treble support, which is also a Google requirement for new devices. However, Treble support (and therefore Linux kernel 4.4) is not necessary for Android 8.X to function, as evidenced by all the devices that launched with older versions that were later OTA'd to 8.X and by all the devices currently running LOS 15.1 or any other rom that is a fork of the most recent AOSP.
So yes, LOS 15.1 is different than stock Android Oreo, but only in the same way that Samsung devices running 8.X, for example, are different from Oreo. It is entirely accurate and appropriate to say that all of the cases I've mentioned are running Android Oreo, and it is entirely inaccurate to say that Oreo requires Linux kernel 4.4 to function.
That's what I meant with false hopes because in the end someone might think this phone will really get Oreo.
lem22 said:
That's what I meant with false hopes because in the end someone might think this phone will really get Oreo.
Click to expand...
Click to collapse
Well assuming someone is still working on making the necessary kernel tweaks, it will get Oreo. Once someone does that, everything else is easy. But if work on that has stopped, no Oreo.
lem22 said:
That's what I meant with false hopes because in the end someone might think this phone will really get Oreo.
Click to expand...
Click to collapse
I call Android 8.1 "Oreo". Don't know about you. OREO booted on a Quark.
Did you just ignore that post and screenshot proof? You posted.right below it, so your couldn't miss it.
@bhb27 just has to get it stable.
But there's your Oreo 8.1 on kernel 3.1.
https://forum.xda-developers.com/showthread.php?p=76410082
Sent via open market LG US998 V30/V30+
ChazzMatt said:
I call Android 8.1 "Oreo". Don't know about you.
Click to expand...
Click to collapse
Like I explained, I don't, to avoid confusion. More specifically, I differentiate between Android and RR in this case.
The problem is, usually the preowned used lot of devices shipped to countries other than motorola officially operating-in. In my case, Pakistan. We are mostly unable to buy brand new devices (even if motorola did sell its flagships here) due to hefty prices we have to pay versus the income we have. 25$ might be 2hrs work in US but its almost 3 days of 8hourly shifts on a regular job in Pakistan. Another problem is (I don't know yet) if sunshine supports payments and unlocking outside USA. This caused me to stay away from Motorola as well as HTC devices because the used devices which come to Pakistan are always the verizon ones or the Lenovo's low-end crap. Mind that in Pakistan, currently Turbo 64GB as used device is being sold for 90-110$.
I do understand how OEMs & Carrier-exclusive devices are left in the abyss in terms of software support and speed of security patch arrivals as well as the effort our devs go through to adapt older sources with the newer android builds.
dark_prince said:
The problem is, usually the preowned used lot of devices shipped to countries other than motorola officially operating-in. In my case, Pakistan. We are mostly unable to buy brand new devices (even if motorola did sell its flagships here) due to hefty prices we have to pay versus the income we have. 25$ might be 2hrs work in US but its almost 3 days of 8hourly shifts on a regular job in Pakistan. Another problem is (I don't know yet) if sunshine supports payments and unlocking outside USA. This caused me to stay away from Motorola as well as HTC devices because the used devices which come to Pakistan are always the verizon ones or the Lenovo's low-end crap. Mind that in Pakistan, currently Turbo 64GB as used device is being sold for 90-110$.
I do understand how OEMs & Carrier-exclusive devices are left in the abyss in terms of software support and speed of security patch arrivals as well as the effort our devs go through to adapt older sources with the newer android builds.
Click to expand...
Click to collapse
1) If anyone wants to they can write a free app to do the same thing Sunshine does. The exploit was disclosed publicly. Find someone who knows how to code.
2) Yes Sunshine supports payments and unlocking outside the U.S.. I answered in depth about that just a few weeks ago, that there are alternate ways to pay besides PayPal. It may not be in this thread, but a similar one.
3) There are plenty of Motorola phones that have free bootloader unlock code from Motorola. The reason Pakistan gets the Verizon Motorola phone are probably because they are cheaper -- as they are less useful since have locked down bootloader. So, you have to factor that into the bootloader unlock price (if that option is available) if it's important to you... Some Verizon phones never got dev bootloader unlock.
Whereas the India 64GB Quark Moto Moto Turbo XT1225 (aka Moto Maxx XT1225) -- from the country right next door to you -- probably costs a lot more money than the U.S. Verizon Quark Droid Turbo XT1254. WHY? Not only does it have more LTE and HSPA bands (without the useless CDMA bands), it also has free bootloader unlock code from Motorola. It's the same phone model as the Droid Turbo, they are both Quarks. Just different radio bands. The cost difference is mostly the Verizon locked down bootloader, which makes it a less useful phone.
If you didn't have Sunshine then the 2014 Verizon Droid Turbo (Quark) would have no bootloader unlock, just like the 2015 Verizon Droid Turbo 2 (Kinzie) does not. For Kinzie phones, people have to buy the sibling Moto X Force instead of Droid Turbo 2, to get bootloader unlock and root. Many Droid Turbo 2 owners WISH they could use Sunshine to unlock their bootloaders!
Sent via open market LG US998 V30/V30+
What's the best, easiest way to upgrade manually from Android 7.0 to Oreo 8.1? I'm not getting OTG with 7.0, so I need to try something else without having to buy a new phone. I just spent money to have the charging port fixed, don't want to switch phones again, but need this feature. Thanks!
LearyOne said:
What's the best, easiest way to upgrade manually from Android 7.0 to Oreo 8.1? I'm not getting OTG with 7.0, so I need to try something else without having to buy a new phone. I just spent money to have the charging port fixed, don't want to switch phones again, but need this feature. Thanks!
Click to expand...
Click to collapse
Which Kinzie phone do you have, Moto X Force or Droid Turbo 2?
You can root the Moto X force and there are some custom roms but not Oreo 8.1, I don't think. You cannot root Droid Turbo 2 at all.
Neither phone got past Nougat for stock firmware.
Sent via open market LG US998 V30/V30+
Nooo!
ChazzMatt said:
Which Kinzie phone do you have, Moto X Force or Droid Turbo 2?
You can root the Moto X force and there are some custom roms but not Oreo 8.1 I don't think. You cannot root Droid Turbo 2 at all.
Neither phone got past Nougat for stock firmware.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Oh Dang!! I have the Droid Turbo 2. So when I'm on YouTube and they're showing those videos that say "How to upgrade ANY Android phone to Oreo 8.1" they're not talking about DT2? What would happen if I tried it? Has anyone done it? Just curious. I'm thinking about getting a Moto G5 Plus if I can't upgrade. This one DEFINITELY has 8.1, correct?
Thanks for your replies!
LearyOne said:
Oh Dang!! I have the Droid Turbo 2. So when I'm on YouTube and they're showing those videos that say "How to upgrade ANY Android phone to Oreo 8.1" they're not talking about DT2? What would happen if I tried it? Has anyone done it? Just curious. I'm thinking about getting a Moto G5 Plus if I can't upgrade. This one DEFINITELY has 8.1, correct?
Thanks for your replies!
Click to expand...
Click to collapse
No, if the phone can't be rooted (2015 "Kinzie" Droid Turbo 2) you can only use stock firmware.
If the phone can be rooted (2015 "Kinzie" Moto X Force), you're still dependent on what devs can and will do. The devs with the kernel skills needed to adapt last Kinzie Nougat stock kernel to run on Oreo 8.1 - - which then allows ROMs to be ported - - may wish to spend time on other devices.
The 2014 "Quark" (Droid Turbo/Moto Maxx/Moto Turbo) all have bootloader unlock and root, and they have a dev with those skills. So they have 8.1 ROMs, whikethr 2015 Kinzie phones do not.
https://forum.xda-developers.com/moto-maxx/development
All the QUARK ROMS are compatible with all Quarks.
Schooled!
ChazzMatt said:
No, if the phone can't be rooted (2015 "Kinzie" Droid Turbo 2) you can only use stock firmware.
If the phone can be rooted (2015 "Kinzie" Moto X Force), you're still dependent on what devs can and will do. The devs with the kernel skills needed to adapt last Kinzie Nougat stock kernel to run on Oreo 8.1 - - which then allows ROMs to be ported - - may wish to spend time on other devices.
The 2014 "Quark" (Droid Turbo/Moto Maxx/Moto Turbo) all have bootloader unlock and root, and they have a dev with those skills. So they have 8.1 ROMs, whikethr 2015 Kinzie phones do not.
https://forum.xda-developers.com/moto-maxx/development
All the QUARK ROMS are compatible with all Quarks.
Click to expand...
Click to collapse
Thanks for that education! I've been schooled, lol! OK, I guess I'm going for the Moto G5 Plus. I'm not happy with Nougat at all!