Android Tipps
Android Tipps vom 21.09.2018 um 12:56 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 11:39 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 11:13 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 10:52 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 10:46 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 10:06 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 09:55 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 08:56 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 08:44 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 21.09.2018 um 08:20 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 18:23 Uhr | Quelle feedproxy.google.com
Posted by Jason Woloz and Mayank Jain, Android Security & Privacy Team
Our Android and Play security reward programs help us work with top researchers from around the world to improve Android ecosystem security every day. Thank you to all the amazing researchers who submitted vulnerability reports.
In the ASR program's third year, we received over 470 qualifying vulnerability reports from researchers and the average pay per researcher jumped by 23%. To date, the ASR program has rewarded researchers with over $3M, paying out roughly $1M per year.
Here are some of the highlights from the Android Security Rewards program's third year:
As part of our ongoing commitment to security we regularly update our programs and policies based on ecosystem feedback. We also updated our severity guidelines for evaluating the impact of reported security vulnerabilities against the Android platform.
In October 2017, we rolled out the Google Play Security Reward Program to encourage security research into popular Android apps available on Google Play. So far, researchers have reported over 30 vulnerabilities through the program, earning a combined bounty amount of over $100K.
If undetected, these vulnerabilities could have potentially led to elevation of privilege, access to sensitive data and remote code execution on devices.
In addition to rewarding for vulnerabilities, we continue to work with the broad and diverse Android ecosystem to protect users from issues reported through our program. We collaborate with manufacturers to ensure that these issues are fixed on their devices through monthly security updates. Over 250 device models have a majority of their deployed devices running a security update from the last 90 days. This table shows the models with a majority of deployed devices running a security update from the last three months:
| Manufacturer | Device |
| ANS | L50 |
| Asus | ZenFone 5Z (ZS620KL/ZS621KL), ZenFone Max Plus M1 (ZB570TL), ZenFone 4 Pro (ZS551KL), ZenFone 5 (ZE620KL), ZenFone Max M1 (ZB555KL), ZenFone 4 (ZE554KL), ZenFone 4 Selfie Pro (ZD552KL), ZenFone 3 (ZE552KL), ZenFone 3 Zoom (ZE553KL), ZenFone 3 (ZE520KL), ZenFone 3 Deluxe (ZS570KL), ZenFone 4 Selfie (ZD553KL), ZenFone Live L1 (ZA550KL), ZenFone 5 Lite (ZC600KL), ZenFone 3s Max (ZC521TL) |
| BlackBerry | BlackBerry MOTION, BlackBerry KEY2 |
| Blu | Grand XL LTE, Vivo ONE, R2_3G, Grand_M2, BLU STUDIO J8 LTE |
| bq | Aquaris V Plus, Aquaris V, Aquaris U2 Lite, Aquaris U2, Aquaris X, Aquaris X2, Aquaris X Pro, Aquaris U Plus, Aquaris X5 Plus, Aquaris U lite, Aquaris U |
| Docomo | F-04K, F-05J, F-03H |
| Essential Products | PH-1 |
| Fujitsu | F-01K |
| General Mobile | GM8, GM8 Go |
| Pixel 2 XL, Pixel 2, Pixel XL, Pixel | |
| HTC | U12+, HTC U11+ |
| Huawei | Honor Note10, nova 3, nova 3i, Huawei Nova 3I, 荣耀9i, 华为G9青春版, Honor Play, G9青春版, P20 Pro, Honor V9, huawei nova 2, P20 lite, Honor 10, Honor 8 Pro, Honor 6X, Honor 9, nova 3e, P20, PORSCHE DESIGN HUAWEI Mate RS, FRD-L02, HUAWEI Y9 2018, Huawei Nova 2, Honor View 10, HUAWEI P20 Lite, Mate 9 Pro, Nexus 6P, HUAWEI Y5 2018, Honor V10, Mate 10 Pro, Mate 9, Honor 9, Lite, 荣耀9青春版, nova 2i, HUAWEI nova 2 Plus, P10 lite, nova 青春版本, FIG-LX1, HUAWEI G Elite Plus, HUAWEI Y7 2018, Honor 7S, HUAWEI P smart, P10, Honor 7C, 荣耀8青春版, HUAWEI Y7 Prime 2018, P10 Plus, 荣耀畅玩7X, HUAWEI Y6 2018, Mate 10 lite, Honor 7A, P9 Plus, 华为畅享8, honor 6x, HUAWEI P9 lite mini, HUAWEI GR5 2017, Mate 10 |
| Itel | P13 |
| Kyocera | X3 |
| Lanix | Alpha_950, Ilium X520 |
| Lava | Z61, Z50 |
| LGE | LG Q7+, LG G7 ThinQ, LG Stylo 4, LG K30, V30+, LG V35 ThinQ, Stylo 2 V, LG K20 V, ZONE4, LG Q7, DM-01K, Nexus 5X, LG K9, LG K11 |
| Motorola | Moto Z Play Droid, moto g(6) plus, Moto Z Droid, Moto X (4), Moto G Plus (5th Gen), Moto Z (2) Force, Moto G (5S) Plus, Moto G (5) Plus, moto g(6) play, Moto G (5S), moto e5 play, moto e(5) play, moto e(5) cruise, Moto E4, Moto Z Play, Moto G (5th Gen) |
| Nokia | Nokia 8, Nokia 7 plus, Nokia 6.1, Nokia 8 Sirocco, Nokia X6, Nokia 3.1 |
| OnePlus | OnePlus 6, OnePlus5T, OnePlus3T, OnePlus5, OnePlus3 |
| Oppo | CPH1803, CPH1821, CPH1837, CPH1835, CPH1819, CPH1719, CPH1613, CPH1609, CPH1715, CPH1861, CPH1831, CPH1801, CPH1859, A83, R9s Plus |
| Positivo | Twist, Twist Mini |
| Samsung | Galaxy A8 Star, Galaxy J7 Star, Galaxy Jean, Galaxy On6, Galaxy Note9, Galaxy J3 V, Galaxy A9 Star, Galaxy J7 V, Galaxy S8 Active, Galaxy Wide3, Galaxy J3 Eclipse, Galaxy S9+, Galaxy S9, Galaxy A9 Star Lite, Galaxy J7 Refine, Galaxy J7 Max, Galaxy Wide2, Galaxy J7(2017), Galaxy S8+, Galaxy S8, Galaxy A3(2017), Galaxy Note8, Galaxy A8+(2018), Galaxy J3 Top, Galaxy J3 Emerge, Galaxy On Nxt, Galaxy J3 Achieve, Galaxy A5(2017), Galaxy J2(2016), Galaxy J7 Pop, Galaxy A6, Galaxy J7 Pro, Galaxy A6 Plus, Galaxy Grand Prime Pro, Galaxy J2 (2018), Galaxy S6 Active, Galaxy A8(2018), Galaxy J3 Pop, Galaxy J3 Mission, Galaxy S6 edge+, Galaxy Note Fan Edition, Galaxy J7 Prime, Galaxy A5(2016) |
| Sharp | シンプルスマホ４, AQUOS sense plus (SH-M07), AQUOS R2 SH-03K, X4, AQUOS R SH-03J, AQUOS R2 SHV42, X1, AQUOS sense lite (SH-M05) |
| Sony | Xperia XZ2 Premium, Xperia XZ2 Compact, Xperia XA2, Xperia XA2 Ultra, Xperia XZ1 Compact, Xperia XZ2, Xperia XZ Premium, Xperia XZ1, Xperia L2, Xperia X |
| Tecno | F1, CAMON I Ace |
| Vestel | Vestel Z20 |
| Vivo | vivo 1805, vivo 1803, V9 6GB, Y71, vivo 1802, vivo Y85A, vivo 1726, vivo 1723, V9, vivo 1808, vivo 1727, vivo 1724, vivo X9s Plus, Y55s, vivo 1725, Y66, vivo 1714, 1609, 1601 |
| Vodafone | Vodafone Smart N9 |
| Xiaomi | Mi A2, Mi A2 Lite, MI 8, MI 8 SE, MIX 2S, Redmi 6Pro, Redmi Note 5 Pro, Redmi Note 5, Mi A1, Redmi S2, MI MAX 2, MI 6X |
| ZTE | BLADE A6 MAX |
Thank you to everyone internally and externally who helped make Android safer and stronger in the past year. Together, we made a huge investment in security research that helps Android users everywhere. If you want to get involved to make next year even better, check out our detailed program rules. For tips on how to submit complete reports, see Bug Hunter University.
WeiterlesenAndroid Tipps vom 20.09.2018 um 16:34 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 16:27 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 16:18 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 14:30 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 11:05 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 09:51 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 08:33 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 07:58 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 20.09.2018 um 07:41 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 20:55 Uhr | Quelle addictivetips.com
Snapchat lets you share both images and videos. It has special lenses that work only with videos i.e., the animated ones and it has a neat loop feature that will automatically play your video on repeat. In a recent update, Snapchat has added a new loop feature that allows users to loop only a portion […]
Read How To Loop Videos With Bounce On Snapchat by Fatima Wahab on AddictiveTips - Tech tips to make you smarter
WeiterlesenAndroid Tipps vom 19.09.2018 um 16:47 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 16:33 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 16:25 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 14:18 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 13:44 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 13:42 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 11:39 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 11:07 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 10:30 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 08:38 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 19.09.2018 um 08:23 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 18.09.2018 um 19:50 Uhr | Quelle feedproxy.google.com
Posted by Jingyu Shi, Developer Advocate, Partner Devrel
This is the second in a series of blog posts in which outline strategies and guidance in Android with regard to power.
Notifications are a powerful channel you can use to keep your app's users connected and updated. Android provides Notification APIs to create and post notifications on the device, but quite often these notifications are triggered by external events and sent to your app from your app server.
In this blog post, we'll explain when and how to generate these remote notifications to provide timely updates to users and minimize battery drain.
We recommend using Firebase Cloud Messaging (FCM) to send remote notifications to Android devices. FCM is a free, cross-platform messaging solution that reliably delivers hundreds of billions of messages per day. It is primarily used to send remote notifications and to notify client applications that data is available to sync. If you still use Google Cloud Messaging (GCM) or the C2DM library , both of which are deprecated, it's time to upgrade to FCM!
There are two types of FCM messages you can choose from:
You can set the priority to either high or normal on the data messages. You can find out more about FCM messages and message handling in this blog post on Firebase Blog.
FCM is optimized to work with Android power management features. Using the appropriate message priority and type helps you reach your users in a timely manner, and also helps save their battery. Learn more about power management features in this blog post: "Moar Power in P and the future".
All of the notifications that you send should be well-structured and actionable, as well as provide timely and relevant information to your users. We recommend that you follow these notification guidelines, and avoid spamming your users. No one wants to be distracted by irrelevant or poorly-structured notifications. If your app behaves like this, your users may block the notifications or even uninstall your app.
The When not to use a notification section of the Material Design documentation for notifications highlights cases where you should not send your user a notification. For example, a common use case for a normal priority FCM Data Message is to tell the app when there's content ready for sync, which requires no user interaction. The sync should happen quietly in the background, with no need for a notification, and you can use the WorkManager1 or JobScheduler API to schedule the sync.
If you are sending remote notifications, you should always post the notification as soon as possible upon receiving the FCM message. Adding any additional network requests before posting a notification will lead to delayed notifications for some of your users. When not handled properly, the notifications might not be seen at all, see the "avoid background service" section below.
⚠️ Avoid adding any additional network requests before posting a notification
Also keep in mind that, depending on the state of the device, user actions, and app behavior, one or many power saving features could be restricting your app's background work. As a result, your app's jobs and alarms might be delayed, and its ability to access the network might be restricted.
For all of these reasons, to ensure timely delivery of the notification, you should always show the notification promptly when the FCM message is received, before any other work like network fetch or scheduling jobs.
To post a notification upon the receipt of an FCM message, you should include all the data needed for the notification in the FCM message payload.
The same applies to data sync--we recommend that your app send as much data as possible in the FCM payload and, if needed, load the remainder of the data when the app opens. On a well-performing network, there's a good chance that the data will be synced by the time the user opens the app so the spinner won't be shown to the user. If network connectivity is not good, a notification will be sent to the user with the content in the FCM payload to inform the user in a timely manner. The user can then open the app to load all the data.
You can also encrypt FCM messages end-to-end using libraries like Capillary. The image below shows a general flow of how to handle FCM messages.
As convenient as FCM message payload is, it comes with a 4KB maximum limit. If you need to send a rich notification with an image attachment, or you want to improve your user experience by keeping your app in sync with media content, you may need more than the 4KB payload limit. For this, we recommend using FCM messages in combination with the WorkManager 1 or JobScheduler API.
If you need to post a rich notification, we recommend posting the notification first, with some of the content in the FCM message. Then schedule a job to fetch the remainder of the content. Once the job is finished, update the notification if it is still active. For example, you can include a thumbnail or preview of the content in the FCM payload and post it in the notification first. Then schedule a job to fetch the rest of the media files. Be aware that if you've scheduled jobs from the FCM message handler, it is possible that when the user launches the app, the scheduled job won't have finished yet. You should handle this case gracefully.
In short, use the data in the FCM message payload to post a notification and keep your app content updated first. If you still need more data, then schedule jobs with APIs like WorkManager 1 or JobScheduler API.
One common pitfall is using a background service to fetch data in the FCM message handler, since background service will be stopped by the system per recent changes to Google Play Policy (Starting late 2018, Google Play will require a minimum target API level ).
Android 9 Pie will also impose background execution limits when battery saver is on. Starting a background service will lead to IllegalStateException from a normal priority FCM message. High priority messages do grant you a short whitelist window that allows you to start a background service. However, starting a background service with a network call will put the service at risk of getting terminated by the system, because the short execution window is only intended to be used for posting a notification.
You should avoid using background services but use WorkManager 1 or JobScheduler API instead to perform operations in the background.
Android 6 Marshmallow introduced Doze. FCM is optimized to work with Doze, and you can use high priority FCM messages to notify your users immediately. In Doze mode, normal priority messages are deferred to a maintenance window. This enables the system to save battery when a device is idle, but still ensure users receive time-critical notifications. Consider an instant messaging app that sends users messages from friends or incoming phone calls or a home monitoring app sends users alarm notifications. These are some of the acceptable examples where you can use high priority FCM messages.
In addition, Android 9 Pie introduced App Standby Buckets and App Restrictions.
The table below shows how various power-management features affect message delivery behaviors.
| High priority message delivery | Normal priority message delivery | |
| App in Foreground | Immediate, unless app is restricted (see below) | Immediate, unless app is restricted (see below) |
| App in Background | ||
| Device in Doze (M+) and Doze "on the go" (N+) | Immediate | Deferred until maintenance window |
| App Standby Buckets (P+) | May be restricted | No restriction |
| App Restrictions (P+) | All messages dropped (see below) | All messages dropped (see below) |
| Battery Saver | No restriction | No restriction |
★ Note: Starting January 2019, App Restrictions (in Battery Setting) will include restrictions on FCM messages. You can find out if your app is in the restricted state with the isBackgroundRestricted API. Once your app is in the restricted state, no FCM messages will be delivered to the app at all. This will apply to both high and normal priority FCM messages and when app is in either foreground or background.
App Standby Buckets impose different levels of restrictions based on the app's standby bucket. Based on which bucket your app belongs to, there might be a cap for the number of high priority messages you are allowed to send per day. Once you reach the cap, any subsequent high priority messages will be downgraded to normal priority. See more details in the power management restrictions.
High priority FCM messages are designed to send remote notifications or trigger actions that involve user interactions. As long as you always use high priority messages for these purposes, your high priority messages will be delivered immediately and remote notifications will be displayed without delay. In addition, when a notification from a high priority message causes a user to open your app, the app gets promoted to the active bucket, which exempts it from FCM caps. The example below shows an instant messaging app moving to the active bucket after the user taps on a notification triggered by a high priority FCM message.
However, if you use high priority messages to send notifications to the blocked notification channels or tasks which do not involve user interactions, you will run the risk of wasting the high priority messages allocated in your app's bucket. Once reaching the cap, you won't be able to send urgent notifications anymore.
In summary, you should only use high priority FCM messages to deliver immediate, time-critical notifications to users. Doing so will ensure these messages and subsequent high priority messages reach your users without getting downgraded. You should use normal priority messages to trigger events that do not require immediate execution, such as a notification that is not time-sensitive or a data sync in the background.
We highly recommend that you test your apps under all of the power management features mentioned above. To learn more about handling FCM messages on Android in your code, visit the Firebase blog.
Thank you for helping move the ecosystem forward, making better Android apps, and saving users' batteries!
Acknowledgements: This blog posts is in joint collaboration with FCM and Android teams.
1 WorkManager is the recommended solution for background processing once it's stable.
WeiterlesenAndroid Tipps vom 18.09.2018 um 16:26 Uhr | Quelle com-magazin.de
WeiterlesenAndroid Tipps vom 18.09.2018 um 15:37 Uhr | Quelle com-magazin.de
Weiterlesen
Nächste 2 Seite | 
Letzte Seite
Startseite (6)
Why Attackers Are Using C# For Post-PowerShell Attacks (6)
[Release] DXVK 0.80 (5)
Neue Gezeitenkraft-Tests mit deutschen Turbinen in Kanada (5)
Exploits (5)
Eight New Technologies That Are Changing Video Production (4)
DEF CON 26 - Ladar Levison, hon1nbo - Booby Trapping Boxes (4)
Critical Vulnerability Found in Cisco Video Surveillance Manager (4)
Update: pecheck.py Version 0.7.4 (4)
Top 5 Security issue with Near Field Communication NFC Technology (4)
Nachrichten (113)
Reverse Engineering (113)
Android Tipps (80)
Downloads (79)
Hacking (76)
PoC (56)
Windows Tipps (50)
Hannover 96 gegen Borussia Dortmund: Online im Live-Stream oder im TV schauen (44)
Video (44)
Malware / Trojaner / Viren (41)
