The Android L (5.0) has come out, is there any team will work on it?
Hold your horses. 5.0 hasn't even been released to the Nexus devices yet officially. We'll most likely (if we do find a way to get Lollipop) wait until CyanogenMod 12.
Android 5.0 will be official only for Moto X, G, E, and the 2013 Droids.
There might be a chance for the Luge (and therefore maybe an adapted version for the M) too, but I doubt it.
So just CM (if it stops getting worse).
Not even the sources have come out yet, and nobody would like a buggy SDK port. Just wait until CM12's ready for action (which mostly depends on the progress of CM's team).
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Related
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
pedroren said:
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
Click to expand...
Click to collapse
No one knows. We would hope so, but no one would really know. Maybe.
Sent from my Oppo Find 5
kernel-wise - the cyanogenmod team has been able to merge it with the Qualcom sources, so if Qualcom keeps it up to date (most likely yes), then that's no problem (also, nexus 4 shares a lot of the same underlying hardware: CPU/SoC, GPU... that device will get updates, which could be ported over)
http://forum.xda-developers.com/showpost.php?p=40671515&postcount=5
proprietary library-wise - maybe? sometimes, they're compatible cross-android version, sometimes not, and you have to do workarounds to make it work on the new version.... could also steal libraries from other devices (see nexus 4 again)
Once lollipop code is all modified and what have you, will the groundwork make the transition from lollipop to android m be smoother than from kitkat to lollipop? I ask because at this point once lollipop is ready, m will probably be close to release. Just curious, as I just put omni back on an old device but holding out on a custom rom for my nexus 6 and will consider omni once its ready. Its very stable. Thanks.
ryancell said:
Once lollipop code is all modified and what have you, will the groundwork make the transition from lollipop to android m be smoother than from kitkat to lollipop? I ask because at this point once lollipop is ready, m will probably be close to release. Just curious, as I just put omni back on an old device but holding out on a custom rom for my nexus 6 and will consider omni once its ready. Its very stable. Thanks.
Click to expand...
Click to collapse
Not a single clue. UI/UX improvements will hopefully require less work.
The CAF AV/native mess that has held up Omni so long would still be a problem - to the point where maxwen and myself are discussing/attempting an alternate approach. Originally I felt that it was a horrible cop-out/laziness hack, but the more I look at the utter ifdef hell that is CAF vs. AOSP frameworks/av - I think it may be just easier to have two separate frameworks/av setups kind of like we have multiple variants of hardware/qcom/[media,audio,display] - although I intend to keep frameworks/av to only two variants for as long as possible (only exception might be if MTK ever stops sucking and provides platform source - but so far instead our best bet for MTK devices is Android One, which will have some degree of AOSP support.)
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)
Since the device specs meet almost the same to Nexus 5, is it possible to build hammerhead AOSP builds (as is, or official AOSP) for our Note 3?
I was thinking since the M developer preview 3 is out, if anyone could port it for our device.
puppynaz said:
Since the device specs meet almost the same to Nexus 5, is it possible to build hammerhead AOSP builds (as is, or official AOSP) for our Note 3?
I was thinking since the M developer preview 3 is out, if anyone could port it for our device.
Click to expand...
Click to collapse
It would be still difficult, I think we should wait for Google to release M source code and then the developers work from there
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