4 ms·

Seems to me like this impacts not only Pixel devices but all Android devices? Patch was to AOSP: https://github.com/aosp-mirror/platform_frameworks_base/commit

Seems to me like this impacts not only Pixel devices but all Android devices? Patch was to AOSP: https://github.com/aosp-mirror/platform_frameworks_base/commit/ecbed81c3a331f2f0458923cc7e744c85ece96da https://github.com/aosp-mirror/platform_frameworks_base/comm... I don't have a locked SIM handy, but can someone please test on their non-Pixel device and confirm?

Semaphor 4y ago
Not testing it right now, but my understanding is, that the issue is technically for every device, but the specific condition (putting the lockscreen on top of the secure screen stack right before `.dismiss()`-ing) is a Pixel software bug.
izacus 4y ago
Thing is, most phone manufacturers will customize the lockscreen quite a bit, so it's possible (but not necessary!) it affects others.
- notRobot 4y ago
  Yeah, agreed. I wonder if it affects LineageOS, which I run.
  - rex_lupi 4y ago
    It does.
    - notRobot 4y ago
      Oh no. Do you have a source?
      - rex_lupi 4y ago
        Tried
- octagonal 4y ago
  I don't think many phone OEMs will actually take the effort to muck around in the lock screen mechanisms.
  - izacus 4y ago
    That's pretty much the first thing every single one of them does to differentiate the phone.
alanning 4y ago
One of the commenters on the blog post stated that the bypass did not work on their Samsung device.
- djvdorp 4y ago
  That's also confirmed by SamMobile: https://www.sammobile.com/news/nasty-vulnerability-shows-galaxy-phones-can-be-safer-than-google-pixels/ https://www.sammobile.com/news/nasty-vulnerability-shows-gal...