Essential Official Android Thread

Krazy

Krazy

Rifle weh taller dan palm tree
Joined
Dec 29, 2012
Messages
10,569
Reputation
1,523
Daps
30,152
Reppin
Judgement Yard
Cyanogemod wont be left behind...they will be starting on CM12 Lollipop as soon as sources drop.
Internal Memo leaked
Nightlies by December
Proper 1st stable release by January
Joy be unto you, for soon, L source will rain from the sky and thusly be upon us…It is expected that Lollipop source will hit somewhere between November 3rd and Thanksgiving. This leaves us some (or a little) remaining time with CM 11 before we all jump ship to CM 12 hotness.

The plan:
CM 11 will go into Feature Freeze at the end of the week L code becomes available. For the purposes of this post, I will use Novemeber 3rd as the example date of AOSP drop.

Timeline:
# October 31st, CM 11 M12 branching begins
# November 3rd, AOSP releases code to L – all hell breaks loose. CM 12 branches will be created for all relevant projects and AOSP code will be replicated to CM Github. See below for breakdown of CM 12 tasks.
# November 7th, CM 11 M12 released
# November 7th, CM 11 code enters Feature Freeze – all pushes to this branch after this date should be directly tied to addressing a bug or vulnerability. Device merges through DevRel will still be accepted, translations and kernel/device tree changes can continue. Feature Freeze will primarily impact CM apps and Framework – so get your features in ASAP if you have stuff waiting.
# December 1st (tentative) – Nightlies for CM 12 begin, with 50% of CM11 features ported to CM12
# January 2nd, 2015 (tentative) – M releases for CM 12 begin, with feature parity with CM11
# February 2015 – M2 and back to standard monthly releases

Items we are discussing:
1) Should we sign these builds with non test_keys?
2) Device cutoff based on specifications. We expect 512mb devices to be fine, but the issue here will be GPU and non-Kitkat binaries. Expect a hard line here drawn in the sand with respect to device support. This will not be pretty for many older generation devices (pre-ICS).
3) Death of CWM Recovery and impact
4) Unification (see Bringups below)

Items not up for debate:
1) Watering down of SELINUX protections or Encryption by default. These are base protections L is introducing and we should support these items as such. If your device fails to allow encrypting, it will not get a CM sanctioned release.

CM 12 Task list:
We will have the added resources of Inc. assisting us in this effort. As part of this, I will have a Spreadsheet and JIRA project setup to assist in coordination and non-duplication of efforts. If you see something you want to own (that is non-assigned) please feel free to take ownership of it. More on this as the date approaches. Please create a JIRA account if you don’t have one yet.

CAF will play a heavy factor here as well – expect to see a healthy amount of patches come from there in addition to AOSP.

Device bringups:
With the new Nexus devices coming online, the new and existing Nexus platforms will likely be returned to their AOSP configs and move forward from there. For other devices, you all are aware of your own items more than I.

On this note – as a lesson learned from CM11, we need to be a bit smarter when it comes to inheritance, dependencies and unification. I know this item has been in debate before, but I strongly think we should not unify GSM and CDMA variants of platforms. Further, devices that we do not own should not be added to the ‘supported’ column.

Translations:
MB is taking ownership of this and will likely make a new CM 12 project on translate.cyanogenmod.org
Click to expand...
 
Krazy

Krazy

Rifle weh taller dan palm tree
Joined
Dec 29, 2012
Messages
10,569
Reputation
1,523
Daps
30,152
Reppin
Judgement Yard
The day is finally upon us - the Gmail 5.0 APK has landed, and we have it for your (production-signed) downloading pleasure.

As we've expected since we first saw the app more than a week ago, the new Gmail is very... "material." It's got a FAB, the beautiful thread interface we've come to know and love from Inbox, and a drawer that complies with guidelines.



But Gmail's beauty isn't only skin deep - the app is holds some new features, too. The first one we noticed is of course support for corporate/exchange accounts, a capability that obviates the stock email app and promises to unite all your inboxes under one roof (unless of course you're using Inbox, which supports neither exchange nor Google Apps accounts).



There may be even more goodies hiding in the new app, but while we dig around, head to the download below to get it for yourself. Note that if you want to enable exchange support you'll need to install both of the APKs listed below.



Download
The APKs are signed by Google and upgrade your existing app. The cryptographic signatures guarantee that the files are safe to install and were not tampered with in any way. Rather than wait for Google to push the download to your devices, which can take days, download and install these just like any other APK.

File name: com.google.android.gm-5.0_(1520254)-5000600-minAPI14.apk

Version: 5.0 (1520254)

File name: com.google.android.gm.exchange-6.5-1520254-500064-minAPI14.apk

Version: 6.5-1520254

Thanks dontmindme!
Click to expand...
 
AB Ziggy

AB Ziggy

Banned
Joined
Dec 14, 2012
Messages
10,686
Reputation
-994
Daps
25,635
choc_cardigan said:
Gmail 5.0 :ohhh: do I need inbox?
Click to expand...

That depends. When I updated Gmail and went back to inbox. Inbox asked me if I wanted to transfer my Gmail app notifications to the Inbox app since you'll be getting double email notifications otherwise.
 
You must log in or register to reply here.
Top