Bei mir funktioniert der Kalender.
Android L (Developer Preview) für das Nexus 5 (flashbare .zip)
-
-
komisch,
der will mein Google Konto nicht;) -
Hehe
Gesendet von meinem Nexus 5 mit Tapatalk
-
Bei mir läuft er
-
nix zu machen.hab mein Google Konto entfernt,wieder eingerichtet.......
aber Nö er will einfach nicht der elende Kalender.
Auch in der synchronisation taucht er erst gar nicht bei mir auf -
komisch,
der will mein Google Konto nicht;)
Meist ganz einfach, das beim installieren deines Google Kontos er keinen Kalender mit in die Synchronisation aufnimmt... Installiere den Google Kalender aus dem store zusätzlich und er nimmt die Synchronisation mit auf... Danach kannst den instandsetzen wieder löschen... -
nix zu machen.hab mein Google Konto entfernt,wieder eingerichtet.......
aber Nö er will einfach nicht der elende Kalender.
Auch in der synchronisation taucht er erst gar nicht bei mir auf
Probiere meine Variante, ehrlich... -
Danke dir,dann versuch ich das mal
Na siehe da es hat funktioniert.
Danke dir,na wieder was dazu gelernt:smirking::sneaky: -
Wenn du eine der Lautstärke Tasten gedrückt hast kommt:
Keine, Wichtig, Alle
Da drück mal keine.Gesendet von meinem Nexus 5 mit Tapatalk
Ja aber dann bekomme ich gar keine Benachrichtigungen, aber das will ich ja, ich will nur nicht, dass es vibriert.Gesendet von meinem Nexus 5
-
Simple APP, um mit Volume das N5 aufzuwecken, solange es noch keine Option dazu gibt
https://play.google.com/store/apps/det…app.powervolume
Edit: zur was es soll, hält aber mein Telefon vom schlafen ab
-
Gefällt mir eigentlich auch ganz gut. Und soweit wie ich sehe laufen auch meine ganzen Apps.
-
Schwere Geburt wars.
Gesendet von meinem Nexus 5 mit Tapatalk
-
-
Yep meine apps laufen auch alle.
War noch nie von einer Stockrom so begeistert. Bleibt erst ein!al drauf. -
100% meine Meinung!!
Fehlt nur noch xposed! Dann wäre es nahezu perfekt.Gesendet von meinem Nexus 5 mit Tapatalk
-
Gerade von Chainfire auf g+ veröffentlicht.
ZitatAlles anzeigenOn LPX13D, SELinux, and root
As promised, here are some more details about the current situation.
Why it breaks
Google has really put some effort into better securing Android, and we've seen a lot of SELinux related commits to the AOSP tree over the past months. There is some disconnect between the AOSP tree and actual L preview builds, some things from AOSP are not in the L preview build, and vice versa. Ultimately, it's a pretty good bet these things will mostly align, though.
On most devices and firmwares, SuperSU's daemon is started by the install-recovery.sh service script that runs at system boot time, as user root with the init context. This is what the daemon needs to function.
Recently, they've started requiring all started services to run in their own SELinux context, instead of init. Developers and security guys following AOSP have known this was coming; AOSP builds have been logging complaints about this specific service not having its own context for a while now.
Now this script runs as root, but as the install_recovery context, which breaks SuperSU's operation, as it is a very restrictive context.
In the last AOSP build I have tried (a few weeks old), there were a fair number of other holes that we could use to launch the daemon. At first glance(!), it seems those have all been closed. An impressive feat by the guys working on this, if it proves true.
How to fix it
To fix root, all that really had to be done was ensure the daemon's startup script is run at boot as the root user with the init context.
There are multiple ways to do this, but unfortunately for now it seems that it does require a modified kernel package (changing the ramdisk).
In the modified kernel packages I've posted for the Nexus 5 and Nexus 7, the daemon's startup is fixed by commenting out the line in init.rc that forces the install-recovery.sh script to run as the install_recovery context, so now it runs as init again, and all is well.
Repercussions
As stated above, it seems for now that modifications to the kernel package are required to have root, we cannot attain it with only modifications to the system partition.
Combine that with a locked bootloader (and optionally dm-verity) and a device becomes nigh unrootable - exactly as intended by the security guys.
Exploit-based roots are already harder to do thanks to SELinux, and now because of the kernel requirements for persistent root, these exploits will need to be run at every boot. Exploits that make the system unstable (as many do) are thus out as well.
Of course, this is all dependent on OEMs implementing everything exactly right. If a certain OEM doesn't protect one of their services correctly, then we can leverage that to launch the daemon without kernel modifications. While I'm fairly certain this will be the case for a bunch of devices and firmwares, especially the earlier L firmwares, this is not something you should expect or base decisions on. It is now thus more important than ever to buy unlocked devices if you want root.
It might also mean that every firmware update will require re-rooting, and OTA survival mode will be broken. For many (but far from all) devices we can probably automate patching the kernel package right in the SuperSU installer ZIP. We can try to keep it relatively easy, but updating stock firmwares while maintaining root is probably not going to work as easy and fast as it did until now.
Apps need updates
Unsurprisingly, with a new major Android release, apps will need updates. None more so than apps that go beyond the Android API, as root apps do, but even some non-root apps will be affected by the security changes.
As one example, someone posted in the SuperSU thread of a kernel flashing app that didn't work. From the logcat you could see that it was looking for partitions in /dev/block from its normal non-root user and non-init context. That used to be possible, but now it is restricted: normal apps no longer have read access there.
The solution for that app is actually quite simple: list the /dev/block contents using root instead. But simple solution or not, the app will still need to be updated.
By far most root apps should be updateable for L without too much issue. There are indeed exceptions that will need some special care, but those are rare.
Permissive vs enforcing
The kernel packages I posted for the Nexus 5 and 7 LPX13D firmware keep SELinux mostly set to enforcing. I say mostly, because SuperSU actually switches a small part of the system to permissive, so apps calling su can do most things without much interference. The details on this are lengthy (yes, your apps will be able to modify policies as well if needed, which should be rare), and I will document these for other developers after L retail release, assuming it will all still work at that time.
Alternatively, you can set the whole system to permissive or otherwise disable SELinux. There are other kernel packages released that indeed do this. The advantage here is that it instantly fixes some apps' issues, as the SELinux based restrictions have all gone the way of the dodo. The disadvantage here is that you've just shut down a major part of the security system of the device.
Some would argue that a device with an unlocked bootloader, root, encrypted modem firmwares of which nobody really knows what they're doing, etc, is inherently insecure, and thus disabling SELinux doesn't make much difference.
I personally disagree with this. While I do agree that these things weaken security down from the ideal level, I would still not disable more security features than I absolutely need to. Just because you cannot eliminate all attack vectors, is no reason to just completely give up on defending against them.
It is of course your own choice if you want to run a permissive system or not. I will strive to keep everything working in enforcing mode though, and I hope other root app developers will do the same - as stated earlier in the post, I believe this is still possible.
(everything in this post is subject to change for retail L release, obviously)
Quelle:
https://plus.google.com/11351731947742…sts/VxjfYJnZAXP -
Mir fehlt irgendwie eine Anzeige des Akkus in % oder habe ich da was übersehen?
-
-
Geht bei euch google maps? Meines gibt fc
-
Ja läuft. Allerdings kann ich über Tapatalk keine Bilder als Anhang einfügen.
Edit:
Sehe gerade das Route erstellen bzw das beginnen der Navigation einen FC verursacht!
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!