Beiträge von MuggelPu
- 
					
 - 
					
 - 
					
Huuuui .... Wasn mit El Google los? :spaced:
ZitatNews >>
https://plus.google.com/+AndroidAuthority/posts/3hwRMF7VXVbDownload und Infos >>
downloadable API reference package - 
					
SUPPORT THA KÜNSTLER!!! :moustach:
"Überraschung?! "
Zum reinhören - das ganze Album! >>
https://www.youtube.com/playlist?list=…Fn2-LKgSmOTkSA5
Info >>
http://www.laut.de/Degenhardt/Alben/Terror-22-98969
http://www.laut.de/Degenhardt - 
					
[size=14]
Android N Developer Preview 2 online..Google Changelog[/SIZE]
ZitatAlles anzeigen[size=14]What’s new:[/size][size=14][/SIZE]
Last month’s Developer Preview introduced a host of new features, like Multi-window, bundled notifications and more. This preview builds on those and includes a few new ones:- Vulkan: Vulkan is a new 3D rendering API which we’ve helped to develop as a member of Khronos, geared at providing explicit, low-overhead GPU (Graphics Processor Unit) control to developers and offers a significant boost in performance for draw-call heavy applications. Vulkan’s reduction of CPU overhead allows some synthetic benchmarks to see as much as 10 times the draw-call throughput on a single core as compared to OpenGL ES. Combined with a threading-friendly API design which allows multiple cores to be used in parallel with high efficiency, this offers a significant boost in performance for draw-call heavy applications. With Android N, we’ve made Vulkan a part of the platform; you can try it out on supported devices running Developer Preview 2. Read more here.
- Launcher shortcuts: Now, apps can define shortcuts which users can expose in the launcher to help them perform actions quicker. These shortcuts contain an Intent into specific points within your app (like sending a message to your best friend, navigating home in a mapping app, or playing the next episode of a TV show in a media app).
An application can publish shortcuts withShortcutManager.setDynamicShortcuts(List) andShortcutManager.addDynamicShortcut(ShortcutInfo), and launchers can be expected to show 3-5 shortcuts for a given app. 
- Emoji Unicode 9 support: We are introducing a new emoji design for people emoji that moves away from our generic look in favor of a more human-looking design. If you’re a keyboard or messaging app developer, you should start incorporating these emoji into your apps. The update also introduces support for skin tone variations and Unicode 9 glyphs, like the bacon, selfie and face palm. You can dynamically check for the new emoji characters using Paint.hasGlyph().
 
 - Launcher shortcuts: Now, apps can define shortcuts which users can expose in the launcher to help them perform actions quicker. These shortcuts contain an Intent into specific points within your app (like sending a message to your best friend, navigating home in a mapping app, or playing the next episode of a TV show in a media app).
 
New human emoji
New activity emoji
API changes:
This update includes API changes as we continue to refine features such as multi-window support (you can now specify a separate minimum height and minimum width for an activity), notifications, and others. For details, take a look at the diff reports available in the downloadable API reference package.
- Bug fixes: We’ve resolved a number of issues throughout the system, including these fixes for issues that you’ve reported through the public issue tracker. Please continue to let us know what you find and follow along with the known issues here.
 
downloadable API reference packageAndroidPolice Changelog ([size=14]android-n-preview-1 to android-n-preview-2 AOSP[/SIZE])
http://www.androidpolice.com/android_aosp_c…tm_source=1-2-2Download
[size=14]downloadable API reference package[/SIZE]
 - Vulkan: Vulkan is a new 3D rendering API which we’ve helped to develop as a member of Khronos, geared at providing explicit, low-overhead GPU (Graphics Processor Unit) control to developers and offers a significant boost in performance for draw-call heavy applications. Vulkan’s reduction of CPU overhead allows some synthetic benchmarks to see as much as 10 times the draw-call throughput on a single core as compared to OpenGL ES. Combined with a threading-friendly API design which allows multiple cores to be used in parallel with high efficiency, this offers a significant boost in performance for draw-call heavy applications. With Android N, we’ve made Vulkan a part of the platform; you can try it out on supported devices running Developer Preview 2. Read more here.
 - 
					
Volantis - MOB30D - vendor.img
https://drive.google.com/file/d/0BxBzjt…iew?usp=sharing - 
					
 - 
					
 - 
					
Immer mehr Theme Devs unterstützen Arcus... Meine Begeisterung ebbt nicht ab.

Ausprobieren lohnt sich...
Hier gibt es die App » » https://www.android-port.de/themen/cm-them…e-4#post-153561
Ich habe aktuell grad Deep Darkness Variante "ACORN" installiert » »
 - 
					
 - 
					
The Keules ftw :moustach:
» » Menschen « « nun auch mit Update & trotzdem fehlerhaft...
ZitatAlles anzeigenMenschen sind die Geilsten
Es ist überall das Gleiche
Weiße woll'n gern braun sein aber Schwarze find'n se scheiße
Wir sind die besten (woohoo)
Wir sind unglaublich (woohoo)
Nichts ist unmöglich (woohoo)
Me-Me-Me-Menschen sind der Hit
Wir sind die besten die es gibt!
Wir sind sexy (woohoo)
Weil wir's uns wert sind (woohoo)
Don't call it Schnitzel (woohoo)
Me-Me-Me-Menschen sind der Hit
Wir sind die besten die es gibt!Externer Inhalt www.youtube.comInhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt. - 
					
 - 
					
 - 
					
UPDATE!!!!
April security update
Download:
ElementalX-N9-4.10Changes:
-April security update
-update installerKernel
 - 
					
Bugfix Update >> 3.0.2-0
Zitat#TWRP 3.0.2-0 is out. This is only a bugfix release. Head over to https://twrp.me to download the latest.
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
Zeitplan und Updates - 
					
Japs bin auch begeistert... Und wg Beta Status noch net eingepflegt

 - 
					
 - 
					
 - 
					
[size=14]
[/SIZE]
[size=14]
Hier eine kleine Sammlung / Zusammenfassung der Infos /Links zum Android N Beta Programm ...[COLOR=#ff0000]Aktuell >>[/COLOR][/SIZE]
[size=14]Developer Preview 1[/SIZE]
[size=14]Date: March 2016
Builds: NPC56P, NPC56R, updated: NPC56W, NPC56X
Emulator support: x86 & ARM (32/64-bit)
Google Play services: 8.4[/SIZE]
[size=14]
Nexus 9
"volantis" volantis-npc56x-preview-5c323abd.tgz
MD5: 474a13915e22d683cab5cf59ed868157
SHA-1: 5c323abdec121b2f07fdabaa3d70d12106e450ad
Nexus 9G
"volantisg" volantisg-npc56x-preview-41ae398c.tgz
MD5: 5a145a546a4a9f68c2b8e2624cf9832b
SHA-1: 41ae398c30536a2d96b04d61b9ef97a043bf59cf
[/SIZE]ZitatAlles anzeigen[size=14]Timeline & updates[/SIZE]
[size=14]
The N Developer Preview runs from 9 March 2016 until the final Android N public release to AOSP and OEMs, planned for Q3 2016.At key development milestones, we’ll deliver updates for your development and testing environment. In general you can expect an update each month (4 to 6 week interval). The milestones are listed below.
[/SIZE]- [size=14]Preview 1 (initial release, alpha)[/SIZE]
 - [size=14]Preview 2 (incremental update, beta)[/SIZE]
 - [size=14]Preview 3 (incremental update, beta)[/SIZE]
 - [size=14]Preview 4 (final APIs and official SDK, Play publishing)[/SIZE]
 - [size=14]Preview 5 (near-final system images for final testing)[/SIZE]
 - [size=14]Final release to AOSP and ecosystem[/SIZE]
 
[size=14]Each update includes SDK tools, preview system images, emulators, reference documentation, and API diffs.The first three preview milestones provide an early test and development environment that help you identify compatibility issues in your current apps and plan migration or feature work needed to target the new platform. This is the priority period in which to give us your feedback on features and APIs and file compatibility issues — for all of these, please use the issue tracker. You can expect some API changes across these updates.
At previews 4 and 5 you’ll have access to the final N APIs and SDK to develop with, as well as near-final system images to test system behaviors and features. Android N will provide a standard API level at this time. You can begin final compatibility testing of your legacy apps and refine any new code that is using the N APIs or features.
Also starting in preview 4, you’ll be able to publish apps to devices running Android N at the official API level, such as consumer devices that have opted into the Android Beta program. You can publish into the Google Play alpha and beta channels first, so you can test your apps with Android Beta consumers before distributing broadly on the store.
As you test and develop on Android N, we strongly recommend keeping your development environment up-to-date as preview updates are released. To make the process easier, you can enroll your test devices in the Android Beta program and get updates over-the-air (OTA) at each milestone. Alternatively, updated preview images are available that you download and flash manually.
We’ll notify you when preview updates are available via the Android Developers Blog, as well as this site and theAndroid N Developer Community.
[/SIZE]
[size=14]Support and Release Notes[/SIZE]
[size=14]Two primary support channels are available to you when developing and testing with the Android N Developer Preview: Please file bugs at Android Developers Blog for device-specific, system, and Google App bugs. For issues in other apps, please contact the developer directly.To discuss issues or ideas with other developers working with Android N, join the Developer Preview Google+ community.
[/SIZE]
[size=14]General advisories[/SIZE]
[size=14]This Developer Preview release is for app developers only and is designed for use in compatibility testing and early development only. Please be aware of these general notes about the release:
[/SIZE]- [size=14]This release has various stability and performance issues on all devices that make it not suitable for daily use on phone or tablet, especially for non-developers.[/SIZE]
 - [size=14]System and app performance is known to be periodically slow / janky, and device may become occasionally unresponsive. These problems may become more acute with prolonged use.[/SIZE]
 - [size=14]Battery life may be regressed in this release for screen-on and screen-off use cases.[/SIZE]
 - [size=14]Some apps may not function normally on Developer Preview 1. This includes Google’s apps as well as other apps.[/SIZE]
 - [size=14]This early build is not Compatibility Test Suite (CTS) approved. Apps that depend on CTS approved builds (Android Pay for example) won’t work.[/SIZE]
 - [size=14]This preview release supports the following devices: Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Nexus Player, and Pixel C, as well as General Mobile 4G (Android One).[/SIZE]
 
[size=14]Set up a hardware device[/SIZE]
[size=14]The N Developer Preview offers system updates for a range of hardware devices that you can use for testing your app, from phones to tablets and TV.If you have access to a supported device, you can update it to a Developer Preview milestone build in one of these ways:
[/SIZE]- [size=14]Enroll the device in automatic OTA system updates through the Android Beta Program. Once enrolled, your device will receive regular over-the-air (OTA) updates of all milestone builds in the N Developer Preview. This approach is recommended because it lets you seamlessly transition from your current environment through the various releases of the N Developer Preview.[/SIZE]
 - [size=14]Download a Developer Preview system image and flash the device. OTA updates are not provided automatically for devices that you flash manually, but you can enroll those devices in Android Beta Program to get OTA updates.[/SIZE]
 
[size=14]Enroll the device in automatic OTA updates[/SIZE]
[size=14]If you have access to a supported device (see the list in the Downloads table), you can receive over-the-air updates to preview versions of Android by enrolling that device in the Android Beta Program. These updates are automatically downloaded and will update your device just like official system updates.You can un-enroll a device at any time. The device will receive an OTA update to the most recent production version of Android available for that device (for example, Android 6.0 Marshmallow). The update requires a full device reset, so user data on the device will be removed. Make sure to back up important data before un-enrolling a device.
For more information and to enroll your device, see the Android Beta Program web site.
Note: Un-enrolling requires a full device reset. Back up important data first.
[/SIZE]
[size=14]Flashing a device manually[/SIZE]
[size=14]At any time you can download the latest Developer Preview system image and manually flash it to your device. See the table below to download the system image for your test device. Manually flashing a device is useful if you need precise control over the test environment or need to reinstall frequently, such as for automated testing.Installing a system image on a device removes all data from the device, so you should back up your data first.
After you back up your device data and download the system image below that matches your device, follow the instructions at http://developers.google.com/android to flash the image onto your device.
Manually flashed system images do not automatically receive OTA updates to later Developer Preview milestone builds. Make sure to keep your environment up-to-date and flash a new system image at each Developer Preview milestone.
If you decide you want to get OTA updates after manually flashing a device, all you need to do is enroll the device in the Android Beta Program. You can enroll the device at any time to receive the next Preview update over the air.
[/SIZE]
[size=14]Uninstalling the Preview from a device[/SIZE]
[size=14]If you want to uninstall the preview from a device, you can do so in one of these ways:
[/SIZE]- [size=14]Obtain a factory spec system image and then manually flash it to the device.
- For Nexus devices and Pixel C devices, see the Factory Images for Nexus Devices page for downloads.
 - For other devices, please contact the device manufacturer directly. Alternatively, if the device is supported in the Android Beta Program, you can enroll the device in the program and then un-enroll it (see below).
 
[/SIZE]
 - [size=14]Un-enroll the device from Android Beta Program. If the device is enrolled in the Android Beta Program, regardless of device, you can simply un-enroll it from the program.
The device will receive an OTA update to the most recent production version of Android available for that device (for example, Android 6.0 Marshmallow). The update requires a full device reset, so user data on the device will be removed. Make sure to back up important data before un-enrolling a device.[/SIZE] 
[size=14]Note: Uninstalling a Developer Preview system image prior to the end of the program requires a full device reset and removes all user data on the device.[/SIZE]
[size=14]
Nexus 9[/SIZE]- [size=14]Nexus 9 devices may not start after receiving an over-the-air (OTA) update via the Android Beta Program. To recover from this issue, you can try to manually install the OTA image. For more information, see Applying a Device OTA Image.[/SIZE]
 
[size=14]
Note: If you manually install a preview system image on a device, that device will not receive additional over-the-air updates (either production or preview). If you want to update a device with a new preview system image, you must perform another manual installation.[/SIZE]
[size=14]ZitatAlles anzeigen
[size=14]Wie funktioniert das Android-Betaprogramm?[/SIZE]
[size=14]Das Android-Betaprogramm bietet Entwicklern eine Möglichkeit, Vorveröffentlichungen von Android-Versionen zu testen. Das Programm richtet sich derzeit an Entwickler und ist nicht für das primäre Gerät geeignet (siehe bekannte Probleme).Geräte, die für das Programm angemeldet werden, erhalten ein OTA-Update ("over-the-air") auf die aktuelle Betaversion von Android N. Die Updates, die du im Rahmen dieses Programms erhältst, sind nicht stabile Vorveröffentlichungen und können Fehler enthalten, die sich auf dein Gerät auswirken.
Du kannst nach der Veröffentlichung von Version N im Android-Betaprogramm angemeldet bleiben, um eine Vorschau von zukünftigen Android N-MRs (Maintenance Releases, Wartungsversionen) zu erhalten. In diesem Fall erhältst du automatisch ein OTA-Update auf Vorveröffentlichungen der MRs, sobald sie verfügbar werden. Am Ende des Programms erhältst du reguläre öffentliche Updates.
Du kannst dich jederzeit aus dem Programm abmelden und zur stabilen öffentlichen Version von Android zurückkehren. Hinweis: Wenn du dich abmeldest, während auf deinem Gerät eine Betaversion von Android ausgeführt wird, werden alle Nutzerdaten auf dem Gerät gelöscht.
[/SIZE]
[size=14]Welche Geräte sind berechtigt?[/SIZE]- [size=14]Nexus 6, Nexus 9, Nexus 5X, Nexus 6P, Nexus Player[/SIZE]
 - [size=14]Pixel C[/SIZE]
 - [size=14]Allgemeine 4G-Mobilgeräte (Android One)[/SIZE]
 
[size=14]Berechtigte Geräte, die du mit deinem Google-Konto als primärer Nutzer angemeldet hast, werden auf dieser Seite aufgeführt. Wenn du eine Liste der Konten auf deinem Gerät aufrufen möchtest, navigiere zu "Einstellungen" > "Konten" > "Google".Alle Geräte, die in Google Play ausgeblendet wurden, werden auf dieser Seite nicht angezeigt (du kannst dies http://aufplay.google.com/settings überprüfen).
[/SIZE]
[size=14]Wann erhalte ich Updates?[/SIZE]
[size=14]Du erhältst bis zum öffentlichen Start von Android N alle 4 bis 6 Wochen ein Vorschau-Update (weitere Informationen findest du unterZeitplan und Updates).Updates can take up to 24 hours to arrive after opting in. If it has been longer, make sure your device is connected to the internet, and navigate to Settings > About > System updates and check for updates. Note that if you manually flashed Android N on your device by downloading the image from developer.android.com you won’t receive OTA updates automatically, unless that device is also opted-in to the Android Beta Program on this page.
[/SIZE]
[size=14]Wie kann ich überprüfen, ob ich eine Betaversion von Android ausführe?[/SIZE]
[size=14]Hierfür hast du zwei Möglichkeiten:
[/SIZE]- [size=14]Navigiere zu "Einstellungen" > "Info" > "Build-Nummer". Wenn die Build-Nummer mit "NP" beginnt, wird eine Betaversion von Android N ausgeführt.[/SIZE]
 - [size=14]Starte das Gerät neu. Du siehst eine Meldung mit dem Hinweis, dass auf deinem Gerät eine Betaversion von Android ausgeführt wird.[/SIZE]
 
[size=14]Wie kann ich zu einer öffentlichen Android-Version zurückkehren?[/SIZE]
[size=14]Suche auf dieser Seite das Gerät, das du abmelden möchtest, und klicke auf "Gerät abmelden". Kurz darauf wird ein OTA-Update an dein Gerät gesendet, mit dem alle Nutzerdaten gelöscht werden und die aktuelle stabile öffentliche Android-Version installiert wird. Sichere vor der Abmeldung alle Daten. Alle nicht gesicherten Daten gehen verloren.[/SIZE][/SIZE]
[size=14]Downloads & Quellen:[/SIZE]
[size=14]Zeitplan und Updates
Applying a Device OTA Image
Applying a Device OTA Image
Applying a Device OTA Image
Zeitplan und Updates
https://plus.google.com/communities/106765800802768335079[/SIZE]
 - 
					
Auch hier ganz viel Liebe & OP pflege :moustach:
Neue Links zu CM13 Themes / Apps / Commus...Vorschläge, Screenshots & anderes gesabbel
 Bitte hier entlang >> https://www.android-port.de/themen/cm-theme-smalltalk.6810/PS
Eine App jibbet noch die ich "noch" nicht einpflege, euch aber nicht vorenthalten möchte >>
dashboard. (CM13) // ★ ROOT
INFO & MOAR"Klick mich! Ich bin ein Spoiler..."
dashboard. (CM13) // ★ ROOT
https://play.google.com/store/apps/det…ojekt.dashboard
vorgestellt
ungültiger LinkZitatAlles anzeigenPLEASE READ!!!!!
ROOT IS 100% REQUIRED FOR THIS APP! I CAN'T STRESS THIS ENOUGH!
we challanged ourselves to reinvent the wheel, so we created an app to house all our tweaks in an all-in-one package.this isn't some children's app, if you don't read properly and don't follow the steps properly (e.g. not soft rebooting by pressing the red text button after completion, don't come crying to me because all I will do is tell you to read and if you didn't read, it's your loss)
this app comes with:
- color switcher for cdt themes (pre-commit: patch will break Battery Stats in Settings, clear theme cache on theme utilities tab on your cdt theme)- contextual header swapper for all themes (injection into apk so you can set up a couple of headers on several themes to change between.
- theme utilities to restart or rebuild your themes
Current CONFIRMED Supported ROMs:
- AICP, Bliss, CM (no contextual headers), DU, Screw'd, PureNexus and Resurrection Remix.Color Switcher (cdt themes ONLY)
The first time using the switcher it is recommended to NOT clear your Theme Cache.
After picking a color and seeing my lame pickup lines, restart SystemUI on a cdt theme applied.
BY USING THIS ON A CDT THEME, YOU WILL BREAK BATTERY STATS due to a problem with exposing the battery stats fragment on CyanogenMod, until a couple of commit themers start working together to reach a conclusion on this, you can always just rebuild theme cache to remove this problem
 We are working on this proactively!Contextual Header Swapper
If you are looking to edit someone else's theme (non-cdt), make sure you know the package identifier of the third party theme e.g. "com.kohlewrrk.radius" and type it in. You get options for image selection and cropping. After that, it is REQUIRED to do a soft reboot.
If after soft rebooting you don't get anything changed, do it again with AUTOCLEAR SYSTEMUI CACHE on the theme enabled and soft reboot (at most twice). This will hardcode your drawables into the base apk, and you can patch up another theme apk if you want for example another version of Radius with Arcus.ATTENTION: Finally, Color Picker works off the cache thus hotswapping is allowed, but when you modify the header, the cache is destroyed, so you must soft reboot...THEN pick a color.