Android idatabase
#Android idatabase update#
Pre-installed apps often have elevated permissions that are pre-granted at the platform level. One area where the team wants to explore much further is how pre-installed apps perform within the context of security and user privacy. The older approach did not consider other aspects of device security, so the current approach attempts to take a much more holistic look at overall device security. The old approach had a few limitations, as it focused heavily on assessing whether a device was susceptible to known vulnerabilities or not. Back in 2015 when a similar initiative was undertaken, the team had measured the security of Android devices and given them a score out of 10. The Android Device Security Database tries to fix this in a way.
#Android idatabase update#
For instance, Samsung has been doing very well in terms of providing security updates to its existing portfolio of devices, like the Galaxy S10, Galaxy Z Flip, Galaxy A50, Galaxy Note 10 series, Galaxy A70, and the Galaxy S20 series-but there are still so many more devices left to assess and a larger security update progress chart is also missing to provide historical context. And because of the huge variety of smartphones released and the innumerable updates to them over the years, collecting and quantifying this data is also a gargantuan task. Security updates aren’t a metric that a marketing department can easily “ sell” to most end consumers for future smartphones, so performance in this area remains lacking. Smartphone after-sale support is still centered around the limits of Android version updates and device repairs-and overall device security is not given much importance. The talk brings up the issue of how smartphone OEMs currently have little in terms of motivation and quantifiable incentive to provide quick and relevant security updates across their smartphone portfolio.