Profile cover photo
Profile photo
Tor Norbye
15,197 followers
15,197 followers
About
Posts

Post has attachment
Beautiful spring morning in the bay area! #pixel2
Photo
Add a comment...

Post has shared content
One thing I haven't seen the tech press notice is that the button in Settings to check for an update actually works now. If you're running the latest Google Play Services, you shouldn't need to sideload an OTA or flash a system image just because you're impatient...

How does this interact with the Google's staged rollout of new OS releases, you ask? When a device checks in because you've specifically asked it to, we flag that this is user-initiated and so you're not subject to the usual limitations. So even if we're at 1% rollout and 1% of users already have the update, if you manually check you'll still be offered it, even though a background check at the same time wouldn't.

How does this interact with your carrier's additional restrictions? (This was a question that came up a lot in the comments.) If your carrier hasn't approved the update, their restrictions will still apply if you're on their network.

Is this only for Nexus/Pixel devices? Not exactly: it's for any device that uses Google's OTA system, and that does include some non-Nexus/Pixel devices. But, yes, this won't help you if your OEM doesn't use Google's OTA system. (But there's no reason why they shouldn't do the same in theirs, and they may already do so for all I know.)

Is this only for Oreo? No, this is a Google Play Services change. There was no platform-side component to this. (The AOSP Settings app basically sends out an intent when you go into the system update section, and if you're using Google's OTA system, Google Play Services steps up and shows its UI. In some cases it will call back into the system -- to actually apply an update, for example -- but the actual checking in with the Google OTA servers is done by Google Play Services code.)

http://www.androidpolice.com/2017/09/20/android-8-0-oreo-finally-arrives-nexus-player/
Add a comment...

Post has attachment
FYI, in Android Lint 3.0, custom lint checks can supply their own quickfixes.

Here's an example:

LintFix fix = fix().replace().pattern("(always)").with("ifRoom").build();
context.report(ISSUE, location, "Prefer \"`ifRoom`\" instead of \"`always`\"", fix);

More info:
https://groups.google.com/forum/#!topic/lint-dev/4fX01VHa-Ik
Add a comment...

Post has shared content
ADB Episode 66: Kotlin!

+Tor Norbye and I talk with +Romain Guy and +yiğit boyar about Android's new officially supported language.
Fun stuff.

http://androidbackstage.blogspot.com/2017/05/episode-66-kotlin.html
Episode 66: Kotlin!
Episode 66: Kotlin!
androidbackstage.blogspot.com
Add a comment...

Post has attachment
Critical revisions to JUnit to modernize it for 2017. My favorite slide from the Java Posse presentation at Devoxx.
Photo
Add a comment...

Post has attachment
The drought is over and she couldn't be happier about it!
Photo
Add a comment...

Post has attachment
FYI, anyone writing custom Android lint checks or anyone with advanced usage of Android lint may want to join https://groups.google.com/forum/#!forum/lint-dev
Add a comment...

Post has attachment
Do it! Do it! Do it!
PhotoPhotoPhoto
1/22/17
3 Photos - View album
Add a comment...

Post has attachment
Photo
Photo
11/12/16
2 Photos - View album
Add a comment...

Post has attachment
Android Studio 2.3 canary is now available, with many new features and fixes -- see the release notes for more:
http://tools.android.com/recent/androidstudio23canaryavailable

And here are some more details on the new lint features:
http://tools.android.com/tech-docs/lint-in-studio-2-3
Add a comment...
Wait while more posts are being loaded