Skip to main content

Android Q Beta 4 released with final developer APIs

What you need to know

  • On June 5, 2019, Google started pushing Android Q Beta 4.
  • The final APIs are here for developers.
  • It includes the June 2019 security patch.

Following up on Android Q Beta 3 which was released last month during Google I/O, Beta 4 is now being pushed out.

As expected, Beta 4 is a relatively small update compared to the change between Beta 2 and Beta 3. The main difference this time around is that Android Q is now at API Level 29. In other words, developers can do their final compatibility tests for apps to make sure everything will work a-OK when the final build is released in August.

In regards to user-facing changes, it looks like Google is further refining how the new gesture navigation system works. As you can see in the GIF that Google shared on its blog post, the navigation bar at the bottom of the screen is now wider, making it easier to achieve the various gestures, and also disappears when you're on the home screen — further mimicking gestures on iOS.

What's interesting, however, is that these changes aren't actually present in Beta 4. Maybe this is something we'll see in Beta 5 or the final build? We'll let you know as we learn more.

Beta 4 includes the latest June 2019 security patch, and when you update, it'll change your phone's build number to QPP4.190502.018.

If you're already enrolled in the Android Q beta and have a phone running Beta 3, you'll receive an over-the-air update to download and install Beta 4. If you're not currently enrolled but want to go ahead and grab the new software, we've got instructions on how to do so.

Android Q: Everything you need to know!

Joe Maring was a Senior Editor for Android Central between 2017 and 2021. You can reach him on Twitter at @JoeMaring1.

  • Stable enough to use for the daily driver yet?
  • I would say so...but I have been using beta since day one on my phone.
  • Gesture only based Navigation must never become mandatory, so it is good to see it's optional and something you must enable. Lol, I could only imagine the frustration of both expert and novice users of Android if gestures were on by default. I do not deny many will like gestures. Gesture nav will make accessibility easier for some with disabilities, but harder for others. I think of gestures as unnecessary and a battery drain, having sensors on always waiting to identify nav choices. Ie. Like having Bluetooth on when you don't need it on.
    I have a plethora of gesture choices on my phone already, and I disabled all of it, along with Google Assistant (no thanks to the hot mic to Google). But I'll never argue choice isn't a bad thing... If gestures are for you, then you could not be happier. My phone won't get Q.. What is impressive about Q are further refinements to app and online privacy.
  • Does Google Pay work on this build? I hear there were issues on the last one.