[ROM][N5] CyanogenMod 12.1

Aber shamu[emoji1]

https://www.android-port.de/index.php?threads/6462/
[ROM] [SHAMU] [5.0.x] offiziell CM12 nightlies (05/01/15)

Jetzt ist es soweit

http://download.cyanogenmod.org/get/jenkins/97…-hammerhead.zip

Ich muss mal gestehen,
Habe heute morgen das erste mal seit.... Laaaaaangem, cm geflashed und muss echt sagen WTF!?
Wirkt wie ein sorglos Paket,.. Ohne supersu und ohne extra kernel... Alles ausser gapps enthalten yank bisher echt hammer geil!!!
Bin sonst totaler SlimRoms Fan!!!

Gibt es bei cm12 auch headsup für alle Benachrichtigungen (so wie es slim programmiert hat)?

Nein noch nicht, auch keine navbar mods

Navbar wird eh ausgeblendet...aber ich möchte headsup immer...somit brauch ich noch nicht laden. Danke dir

Fehlt mir ehrlich gesagt auch.
Und pie fehlt mir... Hoffe das kommt irgendwo sehr bald sehr schnell

Aber pie kann man doch nun wirklich leicht ersetzen mit LMT launcher, oder? Mache das immer so...

Hast du mal nen link?

Klar, die App von hier installieren
[size=14]aosp_flounder_gchild320_04+17+15.zip[/SIZE]
[APP][ROOT] LMT Launcher v2.3

Danach root-Rechte geben, aktivieren, danach mit root-Explorer unter/system in der Datei build.prop die Zeile einfügen:
qemu.hw.mainkeys=1

Danach Gerät neu starten und es läuft

Der eine oder andere kennt diese Build´s 100% aber ich wollte sie gern mal wieder "raus krammen"!

CM12 CAF myfluxi Build´s
xda
myfluxi @ xda

CM Optimized Build

Zitat

This is an untested CM optimized build. As of right now it is up to date with Cm and with 03, krait, host 4.8 and graphite optimizations. Still working on strict and why it hates me so much. Hopefully after i buy it a few drinks we will be friends again. lol

If you test it please let me know how it works.

cm-12-20150201-UNOFFICIAL-hammerhead.zip

Kurze Info. Ab heute gibt es eine Neuerung. Es werden 2 Versionen der CM12 nightly erscheinen.
Einmal hammerhead, die "normale" CM12 Nightly und zusätzlich die hammerheadCAF Version, die eben mit CAF arbeitet und auf der Arbeit von myfluxi basiert.

CM12 (reguläre, normale AOSP Version)
https://download.cyanogenmod.org/?device=hammerhead

CM12 CAF Version
https://download.cyanogenmod.org/?device=hammerheadcaf

Achtung. Obacht! Bei der heutigen, ersten CAF Version muss zwingend das updater script geändert werden. Die erste Zeile muss gelöscht werden (get assert blabla hammerheadcaf), danach lässt sie sich flashen..
https://download.cyanogenmod.org/get/jenkins/10…mmerheadcaf.zip

Zum Thema CAF hier ein Zitat von Björn Lunden, einem CM Dev.

Zitat

AOSP's support for Qualcomm devices is generally older and doesn't always take advantage of all the features and performance the hardware is capable of. Hammerhead is pretty close to AOSP in terms of kernel and features, besides the patches needed to support our userspace.
Hammerheadcaf is a much more up-to-date build, basically what happens when we treat it as any other Qualcomm device. The result is support for hardware-accelerated encryption, better audio features etc.

MAKO USERS

Gibt sicher noch mehr, vielleicht auch passendere oder bessere, Beschreibungen, wenn man länger Google bemüht. Mir reicht es.
P.S. für MultiRom Nutzer. CM12 CAF als Secondary ROM läuft. Updaterscript nicht vergessen.

EDIT zur CM12 CAF:
Synapse und die aktuellste UKM Version 3.8.1 unterstützen bereits das neue "Modell" bzw die Variante "hammerheadcaf". Bis auf Voltage, was standesgemäss von CM deaktiviert wird, kann man mit nahezu jedem Reiter in Synapse spielen - wer möchte...

Es gibt aktuell noch keinen Custom Kernel, obwohl neobuddy89 bereits eine Version für heute abend (IST) angekündigt hat.
IST = GMT +4:30h
Edith #2 Ich nutze generell SuperSU von Chainfire, aktuell die 2.46.

Edith #3 Chaos Kernel für CAF(!) Quelle

5.1 soll in der nächsten Nightly sein

global.samsungtomorrow.com

Zur Info...

Zitat

AICP/IceColdJelly
#CyanogenMod

OK, shit just got real

CM pushed staging/cm-12.1 branch
https://github.com/CyanogenMod/an…staging/cm-12.1

They did what I was afraid..
Started completely from scratch bast of CAF's 5.1 branch/source
They did exactly the same for Settings repo few days a go..

I need to think about how to proceeded with this. There are several ways to go with this:
1. Merge in AOSP's 5.1 branch and somehow resolve more than a hundred conflicts by looking at CM's source and comparing
2. Rebase from scratch of CAF like CM and cherry pick ALL that we have till now and than resolve conflicts along the way.
3. Use CM's current 12.1 branch, revert from them what we don't have (search trough 17 pages of commit history) and add our customizations to it.

I think I'll go with choice no. 3 TBH

This will take from me a lot of time and I hope I'll do it in time for Christmas.

Alles anzeigen

Für die ORUD/OKUD geschädigten ...

Zitat

[ROM] [5.1] [Daily - UNOFFICIAL][27.03] CyanogenMod 12.1 for Nexus 5

CyanogenMod 12.1 unofficial daily builds
CyanogenMod is a free, community built, aftermarket firmware distribution of Android

REMEMBER:
That for CM Team this is still a work in progress, and CM Team does not offer support to any kang build. If one day will not appear it means that source was not buildable. On early builds some things might be, and possibly will be broken - you should not have any expectations, for now we can just watch the process of rebasing into new mr1 code. I will also try to fix some things while testing

CHANGELOG:
All the source code for CyanogenMod is available in the CyanogenMod Github repo or visit out Gerrit Code Review for a up to date changelog.

DOWNLOADS:
CM12.1-hammerhead

INSTRUCTIONS:
- latest TWRP is higly recomended
- DO NOT WIPE YOUR INTERNAL STORAGE
- factory reset
- flash build
- flash gapps
- Enjoy!

Alles anzeigen

[size=14]cm-12.1-20150327-UNOFFICIAL-hammerheadcaf.zip - myfluxi CAF Build [/SIZE]

Zitat

[size=18]Cyanogenmod 12.1 Changelog[/SIZE]
The team is currently cleaning up their codebase after merging the latest AOSP release of Android 5.1 after which the nightlies will start rolling out. According to the blog post Cyanogenmod 12.1 download will become available later this week.

CM12.1 will feature many changes, the biggest one is the fact that it will be based on Google’s latest version of Android, Android 5.1 Lollipop which OTA became available to Nexus devices several weeks back.

[size=18]Cyanogenmod 12.1 Changelog (CM12.1)[/SIZE]

• CM12.1 to adhere to the Material Design guidelines of Google.
• New floating button for the CM Messaging app
• New rounded circular avatars for contacts.
• Added support for Android Wear
• FM Radio and AOSP Broswer have received UI redesigns
• CyanogenMod File Manager has received a Material UI overhaul
• new features like ZIP/RAR files and secure storage support have been added to Cyanogenmod File Manager

Cyanogen has also announced that it has removed unified builds from multiple devices since they were giving issues with NFC and other sensors in the device.

[size=18]Confirmed devices to receive CM12.1 (Cyanogenmod 12.1) nightly[/SIZE]

• Moto Maxx
• Moto G 2014
• Moto E 2014
• Samsung Galaxy Tab S 8.4
• Oppo N3
• Galaxy Note 4 Intel
• Moto X 2014
• Sony Xperia L
• Galaxy Note 4 US Cellular
• Galaxy Note 4 Spring and T-Mobile
• Galaxy Note 3 T-Mobile
• LG G3 (d850,d851,d852,d855)
• Sony Z3
• Sony Z3 Compact
• Sony Z3 Tablet
• Droid Maxx
• Nexus 6
• Nexus 9

Zitat

[size=18]All About L – Part 1[/SIZE]

It seems Lollipop is on every enthusiast’s mind these days, as OEMs have started a steady stream of OTAs. With this multipart update, we’ll look at the most common questions (minus, “what about my device?”), Android 5.1, and what’s new and improved in CyanogenMod.

Android 5.1

Let’s start with the latest and greatest Lollipop release, Android 5.1. Released in the second week of March, 5.1 has actually seen two releases – 5.1_r1 earlier in the month and 5.1_r3 just this week. The team has been plugging away at these releases, rebasing and merging like fiends. We’re not quite at the point where nightlies will cross over to being officially branded CM12.1, but as always, you are welcome to track our progress.

The CyanogenMod 12.1 (Android 5.1) source is available to sync, and up and running with few issues on various devices – including the latest developer device the Nexus 6. When you repo init the source, just point the branch to ‘staging/cm-12.1’. The staging branch is where we are making things ‘just work’ (you’ll see many patches simply labelled “Fix build”). These patches will be cleaned up prior to moving the source code over to our active mainline branches.

We’d expect another week of this cleanup before CM 12.1 nightlies start flying out the gates.

So just what can you expect in CyanogenMod 12/12.1? Let’s take a brief look now, and even more in part 2!

Oldies Materialized

One of the first items you’ll notice is the Material theme, meant to invoke a sense of ‘living document’ while you interact with your device and apps. All the sweeping animations, bold and heavy on graphic design are present, and we’ve spent some time working on revisiting core CM apps to reflect the new design guidelines.

The CM Messaging app is now sporting a floating action button (FAB) and circular avatars for your contacts, embracing the most common indicators of Material. The app is now Android Wear compliant, thanks to contributor Anthony Williams (dexlab) – allowing it to gel nicely with the latest hot Android accessory.

Browser, abandoned for the most part in AOSP, got a facelift as well, sporting a new icon and making use of Lollipop’s vector support.

The same story applies to other apps, including the FM radio app seen on some of our Qualcomm based devices. Contributor Joey Rizzoli has led the UI revamp of a lot of apps to a large degree – with icons being provided by Jovie Brett Bardoles.

But we’re not through yet!

CyanogenMod File Manager

This venerable app has been a CM staple for quite a few years now. While it too has seen the Material UI overhaul and even learned a new trick or two with zip/rar and secure storage support, its user experience (UX) isn’t the most ideal or easy to navigate. To that end, it’s the next app on our todo list, and we’d love to have your input!

So we pose to you a simple question: How would you improve the File Manager? Let us know in the comments or this linked form.

Of course, the work done on the apps side doesn’t preclude all the device support as our team is all about division of tasks. CyanogenMod’s L flavor sees us bringing support for a fair number of devices, and plenty of new ones as well (107 devices currently receive CM12 nightlies). We’ll take this moment to discuss some of the newest additions to the CM family and the devices they brought to the party!

New friends and devices

- SkrilaxCZ – bringing you the Moto Maxx (quark)

- Luk1337 – bringing you the Moto G 2014 (titan)

- Percy-g2 & Scritch007 – bringing you the Moto E 2014 (condor)

- Eousphoros – bringing you the Samsung Galaxy Tab S 8.4 (klimtwifi)

- Invisiblek & maniac103 – bringing you the Oppo N3 (n3)

- Gekkehenkie11 & Slayher – bringing you the Samsung Galaxy Note 4 Intl (trltexx)

- Crpalmer – bringing you the Moto X 2014 (victara)

- Varunchitre & FXP – bringing you the Sony Xperia L (taoshan)

- Woundtight – bringing you the Samsung Galaxy Note 4 US Cellular (trlteusc)

- Drcrimzon & Slayher – bringing you the Samsung Galaxy Note 4 Sprint and T-Mobile (trltespr,trltetmo)

- Slayher – bringing you the Samsung Galaxy Note 3 T-Mobile (hltetmo)

- Savoca, Invisiblek – bringing you the LG G3 (d850,d851,d852,d855)

- Cdesai & FXP – bringing you the Sony Z3 and Compact (z3,z3c)

- Cdesai & FXP – bringing you the Sony Z3 tablet (scorpion,scorpion_windy)

- SkrilaxCZ – bringing you the Droid Maxx (obake)

- Dhacker29 – bringing you the Nexus 6 (shamu)

- Simonsickle – bringing you the Nexus 9 (flounder)

This list is ever expanding, and we already have more maintainers coming on board to assist with additional devices – they just aren’t nightly ready yet. If your device is listed above, you now know who to thank for bringing the Lollipop experience to your device – you can find most of these folks on the usual social media networks, or stop by #cyanogenmod on Freenode IRC to say “hi”.

This is also a good point to mention that we are always on the lookout for regressions in behavior, even on nightlies. If you flash between nightlies and see something broken that was working properly before, please report it to our JIRA project category “NIGHTLIES”.

Goodbye unified, we hardly knew you

Observant readers will notice that the device variants, particularly for Samsung and Moto devices have once again been broken out into individual builds, counter to our announcement for CM11.

We are officially reverting the decision of using unified builds, as mentioned in that post, with CM12 and beyond.

We’re always conscious of build times, maintenance overhead and other common issues plaguing our contributors. The unified builds, at the time, proved to be an answer for a lot of those headaches – instead of pushing a change to 3-4 device repositories, we could make just one change. Instead of building 3-4 times, our maintainers could use one build to test across all variants. It sounded ideal, and was worth the effort.

So why the retraction? As you are all likely aware of, different carriers and regions receive updates to stock firmware at (putting it nicely) odd intervals. That means even if the device shared 95% of the same guts, the firmware wouldn’t necessarily be compliant across all the device variants. This was particularly prone to failures when looking at items like sensors and NFC. The effect snowballed, d2 and jf users will no doubt chime in here, and the overall quality of release for these unified devices fell.

We’re not ones to hold onto failed ideas, more about iteration and learning, and so we’ve reversed that prior decision. You’ll still be able to update from your CM11 unified to CM12 device variant release, but we will be abandoning the unified builds, and instead focusing on project structures that allow us to make use of ‘–common’ projects (ex. Jf-common). So, look out for jflteatt, spr, tmo and the other variants as their own builds moving forward. Motorola devices like the xt907, xt925, and xt926 share the same story and are likewise de-unified in CM12.

Next time, on All About L

This seems to be a sensible stopping point for this part of the update. Stay tuned next week as we take a feature dive into CyanogenMod 12 – including new soon-to-be favorites like Ambient Display and LiveDisplay (think f.lux like capability).

Until then, Happy Flashing!

Alles anzeigen

[size=14][ROM+KERNEL] Uber CM-12.1---HAMMERHEAD [GCC 4.8 & 4.9][/SIZE]

Zitat

This ROM is compiled w/ Uber 4.8 on the ROM side and Uber 4.9 on the kernel side. I have added a few little optimizations here and there. I will add a feature list a little later.