Beiträge von AA1973

@MuggelPu kannst du noch die Donate App von Kernel Adiutor mit aufnehmen. Kostet nen Euro, ohne weitere Funktion. Der Willi Ye macht echt nen guten Job und ist extrem schnell, was (Feature) Requests u.ä. betrifft.
https://play.google.com/store/apps/det…eladiutordonate
Kannst diesen Post dann einfach löschen. Danke.

Tapatalk Beta Programm.
Voraussetzung: registrierte User in der Tapatalk Community. Dann PM an den User 'mikeo'. Genauer Inhalt kann hier eingesehen werden.
ungültiger Link

Zitat

All Users
To join the BETA testing groups:

• Private message me (@mikeo) the following info, in the following format:
  Android / iOS flag, First name, Last name, Apple ID or Google Account email address (separated by commas, no spaces)
  

  Example:
  iOS, John, Appleseed,appleseed_john@mac.com

• [COLOR=#ff0000]Android, Peter, Piper, petep@gmail.com[COLOR=#ff0000][/COLOR][/email][/COLOR]
• Then wait for the subsequent invite to activate your tester status. BETA requests will be processed every *two weeks*.
  Private Messages not sent in the above format, or repeat requests between invite cycles, [B]will be ignored.[/B]

Alles anzeigen

VIEL SPASS. Glückauf

Ist doch klein

Beim nächsten Update ist BBS wieder einsatzfähig nach dem ersten Booten.
D.h. ohne Booten des Systems, BBS aufrufen, wieder als System App installieren, rebooten und dann erst nutzen können...

Was?

Nein, nicht ganz.
755 ist rwx r-x r-x

Schmankerl...Anbei noch zwei Zip Dateien. Enthalten beide ein addon Skript für system/addon.d für BBS, die xda sowie die PlayStore Edition.

Entpackt die jeweilige Datei 90-bbsxxx.sh und kopiert sie in system/addon.d
Rechte auf 755 setzen. (755 = rwx r-x r-x)

Beim nächsten Update ist BBS wieder einsatzfähig nach dem ersten Booten.
Success
Mit dem heutigen Update getestet (xda Edition).

Ja, genau das. Wird in system/priv-app installiert und BBS ist direkt nutzbar (ohne Aktivieren und Reboot)
Chroma Thread bei XDA

Nutze diese Version
BetterBatteryStats_SystemApp_xdaedition_CWM_1.1.1.0.zip
Direkt Download
Chroma Thread bei XDA

Nein, Gapps flashe ich nicht. Werden durch system/addon.d/70-gapps.sh geschützt. Zumindest ist das der Fall, bei den PA Gapps die ich persönlich nutze (Stock PA Gapps 10/04/2015).

Persönlich flashe ich immer noch meine folgenden Zips
- busybox 1.23 SELinux full
- BetterBatteryStats CWM (für die System App)
- SuperSU (aktuell 2.48 beta)

Die ersten beiden sind persönlicher Spleen, SuoerSU finde ich gehört zu einem Flash immer dazu (also auch Spleen), auch wenn ein Backup Skript für SuperSU vorhanden ist (99-supersu.sh)

Kein Problem. Laut CM ist "dirty install" ja "upgrading normally" und genau so war es auch bei mir. Ohne Probleme.
Was ich damit meinte .... CM hat ja (wie) immer recht?!Beitrag im Thema "Erfahrungen / Bewertungen - MuM-s Trading Group - mykingzone.de Shop"
:oops::p
[Außer bei der Wahl seiner Software Partner...]

Hätte das N6 doch bloß nen Stift ..

Update 15/04 von sykopompos.
Viper4Android Users aufgepasst. Es muss die SE Policy nicht mehr auf permissive gestellt werden, es soll von Haus aus funktionieren.
"N5 build, sepolicy modified so no need to be turned permissive."

Zitat von sykopompos

Any viper 4 android users?
Google+ 5.3.0.91034052

N5 build, sepolicy modified so no need to be turned permissive. Obviously this has a updated sepolicy again so don't use it on any full boot image kernels like if you download directly from Franco.
I'll have the update the policies in my after flash for it but I got work to still do down in the policy

Flash away
:-p

Auf xda gibt es bestimmt auch Beiträge, dass Vollmond Knox getriggert hat...

Wird Knox nicht beim Flashen von unsigniertem Kernel und unsignierter Recovery getriggert?

Zitat

All About L – Part 2

Part 2 of our dive into CyanogenMod Lollipop; let’s take a look at some of the more obvious user space changes and features that you’ll see in CM 12 and 12.1.

But first…

Android 5.1

As we planned in the last blog post, the 5.1 code has officially migrated out of the staging branches and become the full fledge cm-12.1 branch. What does this mean? This means that we have fully merged in the upstream AOSP Android-5.1.0_r3 tag, implemented most (if not all) of the CM 12.0 features and begun focusing on hardware bring-up for our roster of devices. This also means that the buildbots can be switched over for CM 12.1 nightlies at any time. So what are we waiting for? We want you to ‘dirty flash’.

Dirty flashing is what some enthusiast have referred to as flashing one ROM zip on top of another. This is usually used to express that an adverse reaction (be it crashes or bootloops) would result from taking such an action.

In CM, we call this “updating normally”

The normal causes of issues when crossing across major versions of Android is not the update process itself, but usually items external to the ROM – for example ‘gapps’. In fact, Android has (for hopefully obvious reasons) mechanisms to gracefully update your settings and app databases, allowing updates between versions without loss of data – it would be insane for you to take a stock OTA update from your OEM and lose your data; that would not be a good experience.

To make sure we also retain your data on updates, Android makes use of database upgrades, modifying the tables of information that store your settings and making sure they work with what Lollipop expects. We’ve taken a lot of effort to make sure that should you jump from CM11 to 12.1 or 12.0 to 12.1, your data will stick with you. For external packages, you’ll have to update that yourself, but 12.1 is near-ready for the big leagues. Stay tuned for those nightlies to roll out soon.

So, about those user space changes and features in CyanogenMod 12/12.1? Here’s a rundown of the most immediate.

Superuser where?

Root access is one of those dividers between must-have and don’t care about in custom ROMs. CM still ships with root, disabled by default, and you can still enable root access via the Developer Options menu. However, with Lollipop, we’ve ditched the top level ‘SuperUser’ settings item of the past. Instead, root management per app has been directly incorporated into our Privacy Guard permission controls UI – treating the root app model more like the traditional app permissions model. You’ll still be prompted when an app requests root, the only functional change is where you will be looking for revoking granted access. Take a look at Settings > Privacy > Privacy Guard for these controls (long press an app in this view to see all permissions it’s requesting and manage them accordingly).

Trebuchet learns a new trick

Many folks have already decided to use Nova, Apex or even Google Now Launcher as their default home screen app. This one isn’t for you then. For those that appreciate the flexibility of our beloved Trebuchet, we’ve added a new interaction model for the all apps drawer. Trebuchet can now toggle between the traditional paged layout view of your app drawer and a new vertical layout – complete with quick scrubber to locate your needed app at a much improved pace (looking at you Uber). Find the setting in the overview drawer in Trebuchet (long press Trebuchet home screen, then slide the panel up).

What did you do to the Settings app?

Those that are coming from AOSP, stock OEM, or even CM 11 will no doubt notice that our Settings app doesn’t quite line-up with how the “normal” material Settings looks.

Our conundrum is the same as it always has been – as we pump in features and improvements, and the subsequent toggles that give you the granularity to turn them on or off – our Settings app grows and grows in submenus. Eventually, this gets to the point where, with so many people merging and incorporating features, settings for features get buried, hard to find or use.

So, we took a step back and asked ourselves what would happen if we really focused on item placement and ease of use. First, we’ve re-added the top level on/off switches to Wireless settings (WiFi, BT, etc) – reducing one click to manage these compared to AOSP.

Next, we sacrificed the length of the Settings dashboard (the main view you see when you open settings) for elevating features out of submenus – providing new more discrete groups, even separating Notification Management from features that affect the Notification Drawer (similarly for Security and Lock screen settings).

Old favorites like Navigation ring targets and Lock screen shortcuts have new configuration views with much simpler (though no less powerful) configuration.

Overall, while it may seem jarring at first, we feel this new organization is much better for both feature use and discovery. And of course, the search functionality in Settings respects all of the CM additions, so if you find yourself lost about where an item may have moved to, its only one search away.

Introducing: LiveDisplay

One part ease of use for Settings and another part massive improvement in customization capability – LiveDisplay is no doubt going to become a quick favorite among those that are critical about display calibration. Bringing together the old-school CM 7 feature of RenderFX, previously released features like sunrise enhancement and color calibration, and new functionality, LiveDisplay is our new goto for panel calibration – color temperature, automated effective times, lower power consumption, screen color and color calibration. The final result brings something akin to f.lux control to your Android device (please note that the range of controls available will vary by device hardware and what your device actually supports).

Ambient Display

Another new-to-CM feature is Ambient Display. Pioneered on the Moto X family of devices, this functionality makes use of what (in code) is referred to as Doze mode. This mode (like LiveDisplay) is hardware dependent, but allows for Moto X-like ‘breathing’ of the screen upon receiving notifications; showing you what will be waiting on your screen should you unlock it, all with minimal power consumption. Coupled with double-tap to wake and lift to wake capabilities, 12/12.1 now makes it even easier to digest your content at-a-glance, and decide if notifications are worth your time. As a note, for the privacy conscious, remember that you can restrict lock screen notifications from showing actual (potentially revealing) content via the Settings > Notification Manager > ‘When device is locked’ option (for app-by-app control, tap the ‘App notifications’ option in the same settings menu).

Nightlies, nightlies, nightlies

Yes, we hear you. CM 12.0 has now been vetted, QA tested (both by users and corporations) and is nearing a proper release. We’ll be looking at a 12.0 release sometime this month – then shifting to prepare the non-nightly release of 12.1.

Until then, Happy Flashing!

Alles anzeigen

http://www.cyanogenmod.org/blog/all-about-l-part-2

Ab sofort ist der Begriff "dirty flashing" gestrichen und wird durch "update normally" ersetzt

Update 14/04 - läuft bei mir als secondary Rom. Alles gut. Flash away

Zitat von zephiK

Do a nandroid backup before you flash. [COLOR="red"]This is a blind build on my part to fulfill Syko's shoes for maintaining hammerhead, I have not flashed the ROM as I don't own the device but it should work as I'm using the same proprietary binaries/vendor/kernel files that Syko used to build[/Color]

Chroma 04/14 hammerhead (Nexus 5) - android-5.1.0_r5 (LMY47O)
Changelog: SuperSu.zip
Download: XDA

please post back if it boots etc etc etc. I'll be around to fix any problems for nexus 5 device specific issues.

Edit: Appears to be working. Flash away! Nandroid backup just incase.

Sykopompos scheint auch wieder eingenordet zu sein. Was ein Tag am Strand ausmachen kann

Ja. Code Blue R923 z.B.

Zur Frage ob andere Kernels gehen. Ja, sofern Anykernel Methode, ohne eigene Ramdisk (volles Boot.IMG)

Zitat von sykopompos

This refers to full boot image distributions like how Franco distributes his, it does not effect anykernel methods because Franco and a few other devs pack a ramdisk in with the kernel which is where a lot of the core system processes are and things I was fixing under the hood.

I just put out a test zip for the n6 that takes the anykernel method and repacks the ramdisk with the proper files. If that is good, I'll bring it to the other devices

Steht denn im Chainfire Thread auf XDA, dass MultiRom überhaupt supported wird?

@vergilbt
Flash doch mal mit Flashify einen Kernel. Selbes Prinzip. Selbes Ergebnis. Is nicht bei Secondary Roms. Für MultiRom ist das Tool von chainfire aber auch nicht gemacht. Flashify ebenfalls nicht.