Google is working on letting you resize picture-in-picture windows in Android 11

Android 8.0 Oreo introduced picture-in-picture mode to Android smartphones. This feature allows you to watch videos in a small, floating window while you’re using other applications. It’s also useful for navigation so you can respond to messages or look something up on the Internet without missing what’s next on your route. As smartphones have become larger and larger, especially with the introduction of foldable devices, picture-in-picture windows have remained the same size. In Android 11, though, Google may be introducing a way for users to resize picture-in-picture windows.

Picture-in-picture (PIP) mode in Android 11. I opened a YouTube video and then performed the home gesture (a tap of the home button also works) to open the video in a PIP window.

OEMs can set the default edge insets (how far from the screen edge the PIP window first appears), the default screen width and height percentages, the default aspect ratio, the default gravity (the corner of the display where the PIP window starts), and the snap behavior (where the PIP window moves after the user lets go). However, most OEMs don’t touch the default values in AOSP, and they usually don’t modify or extend the functionality of PIP windows. Since AOSP doesn’t provide a way for users to resize PIP windows, OEMs don’t, either. That could change with the introduction of a new class called PipResizeGestureHandler in the SystemUI of Android 11 Developer Preview 2.

This new class is responsible for checking for gesture events within a touch region around the left, right, top, or bottom edge of the picture-in-picture window. The user will be able to drag the PIP window to resize it, though the aspect ratio of the window won’t be changed. At the moment, there doesn’t seem to be a limit on how large the PIP window can become through resizing. Resizing a PIP window in this way seems similar to resizing freeform multi-windows, with the exception of the aspect ratio not being enforced for freeform windows.

The PipResizeGestureHandler class is part of com.android.systemui rather than com.google.android.systemui, so this change to picture-in-picture mode functionality should be reflected in AOSP Android 11 as well as Android 11 on the Google Pixel. Since the class is under com.android.systemui.pip.phone and not com.android.systemui.pip.tv, this feature is most likely intended for phones and not Android TV. However, I wasn’t able to activate this new feature on my Pixel 3a XL, so I can’t confirm if it’s working yet. I’ll be exploring the code more in this and subsequent preview releases to see if I can get it working, though.

Android 11 News on XDA

The post Google is working on letting you resize picture-in-picture windows in Android 11 appeared first on xda-developers.

from xda-developers https://ift.tt/3a3vMVA
via IFTTT

Android 11’s revamped screen recorder may soon support recording internal audio

The first few Android 10 Developer Previews had a barebones screen recorder in SystemUI, but the feature was inaccessible to users at release. With the first Android 11 Developer Preview, however, the screen recorder became accessible from a Quick Settings tile. Now in Android 11 Developer Preview 2, the screen recorder has a revamped UI that informs the user about the possibility of recording sensitive info and lets the user choose if they want to record audio from the microphone and/or show taps on the screen. However, there’s currently no way to record the audio that’s playing back on the device, but that could change in a future preview release.

Left to right: Screen Record Quick Setting tile, Screen Record dropdown options, new Screen Record countdown, and new Screen Record status bar indicator.

New strings have been added to SystemUI in Android 11 pertaining to the Screen Record function. These strings suggest you’ll be able to record “sound from your device, like music, calls, and ringtones.”

<string name="screenrecord_device_audio_and_mic_label">Device audio and microphone</string>
<string name="screenrecord_device_audio_description">Sound from your device, like music, calls, and ringtones</string>
<string name="screenrecord_device_audio_label">Device audio</string>

This text is currently not visible in the Screen Record feature, and there is no indication of the ability to record internal device audio in any of the three classes responsible for screen recording in Android 11: RecordingController, RecordingService, and ScreenRecordDialog. Android 10 made it possible for applications to record the audio from other applications with the AudioPlaybackCapture API. In fact, there are already third-party applications on the Google Play Store that take advantage of this API to let you capture the video and audio from your device. I tested the revamped Screen Recorder feature in Android 11 DP2 just to be sure it didn’t support recording internal audio, and it sadly still only supports recording audio from the microphone. To test for yourself, try starting a screen recording and then open a video in Google Photos while talking aloud—if you can hear yourself talking over the video in the screen recording, then it’s most likely recording audio from just the microphone. I, of course, compared this result against the third-party app I mentioned that uses the API.

Assuming Google does allow you to record internal device audio in a future Android 11 preview, I’m not so sure it’ll actually be that useful. While apps that target Android 10 default to allowing their audio to be captured by apps using the AudioPlaybackCapture API, apps that target Android 9 Pie have to opt-in by enabling the allowAudioPlaybackCapture flag in their Manifest file. Audio can also only be captured if it’s declared as type media, game, or unknown. System applications, such as SystemUI, are also able to record audio from apps even if their audio capture policy is set to ALLOW_CAPTURE_BY_SYSTEM, but they aren’t also allowed to save the audio if this is the case.

Since Screen Record is contained as part of “com.android.systemui” and not “com.google.android.systemui,” that means this feature is likely going to become part of AOSP. Thus, devices from other smartphone makers should be able to enjoy this feature once they upgrade to Android 11, unless of course the OEM already has a comparable or better screen recorder. A lot of OEM screen recorders let you change the resolution, bitrate, and frame rate of the recording, so Google’s is still pretty barebones even if they add the ability to record the internal device audio.

The post Android 11’s revamped screen recorder may soon support recording internal audio appeared first on xda-developers.

from xda-developers https://ift.tt/2w9Obl9
via IFTTT

Android 11 DP2 hints at supporting multi-device media output and switching audio to/from wired headsets

With the release of the Galaxy S8, Samsung introduced the Dual Audio feature to allow users to stream Bluetooth audio to two connected Bluetooth devices. Every flagship Galaxy S, Galaxy Note, and Galaxy Tab device has supported Dual Audio since the Galaxy S8, but the ability to stream audio to multiple Bluetooth devices is missing on the vast majority of Android devices out there, with the exception of a handful of phones from Motorola, HMD Global, and TCL that use Tempow’s technology. A common misconception is that this feature is enabled by Bluetooth 5.0, but many Android devices these days support Bluetooth 5.0 and can’t stream media to multiple devices. Android 9 Pie added support for connecting to up to 5 Bluetooth devices at the same time, and now it seems that Android 11 may add support for choosing multiple devices to stream media to. What’s more, it seems that Google is also adding the ability to change the media output to or from the currently connected wired audio device.

In Android 11, you can currently switch media output between 2 or more connected Bluetooth devices, but you can’t choose multiple devices to stream to simultaneously.

While looking at SettingsGoogle in the latest preview build, we spotted new strings beginning with the title “media_output_group” that seemingly suggest you’ll be able to select multiple audio devices to output to. One string mentions “casting,” which you may initially associate with the Google Cast protocol, but we don’t believe this feature is related to Google Cast. That’s because the existing “media_output” strings pertain to the ability to change the media output from one connected Bluetooth device to another; this feature is already accessible in the volume panel UI provided by a Slice or through Settings > Sound, as shown in the screenshot above. Second, Google Cast is controlled by Google Play Services and not by SettingsGoogle, which is the application that I found these strings in. Third, “cast” can also generically refer to streaming audio to connected Bluetooth devices, especially to Bluetooth speakers.

<string name="media_output_group">Group</string>
<string name="media_output_group_panel_multiple_devices_summary">%1$d devices selected</string>
<string name="media_output_group_panel_single_device_summary">1 device selected</string>
<string name="media_output_group_panel_title">Add outputs</string>
<string name="media_output_panel_stop_casting_button">Stop casting</string>

We also spotted a new string titled “media_transfer_wired_device_name” that suggests you’ll be able to select a currently connected wired headset (either via the USB Type-C port or 3.5mm headphone jack) to output media to. It’s unclear if the addition of this new transfer target will allow users to play audio through the device’s speakers while a wired headset is connected, as some OEMs let you do, or if this feature will simply let you swap media output to or from a wired headset while also connected to a Bluetooth audio device.

<string name="media_transfer_wired_device_name">Wired audio device</string>

We tested both features on our Pixel devices running Android 11 Developer Preview 2 to see if they were working. The multi-device media output did not work on a Pixel 4 XL, while the wired headset media transfer did not work on a Pixel 3a XL with a Type-C headset and a 3.5mm headset with and without a connected Bluetooth device. Besides the new strings, we didn’t find the corresponding code for either feature in the decompiled Settings app, so these features seem to be unfinished. We don’t know if it’s possible for the multi-device media output feature to be supported on any existing Pixel devices or if it’ll require changes to the Bluetooth stack and/or hardware that may show up in a future Pixel device. We also don’t know if these features are intended solely for Pixels even though the strings are in SettingsGoogle; we’ll likely find out if it’s a generic Android 11 feature when Google publishes the source code in a few months.

The post Android 11 DP2 hints at supporting multi-device media output and switching audio to/from wired headsets appeared first on xda-developers.

from xda-developers https://ift.tt/2QtWe37
via IFTTT

Google temporarily pauses Chrome and Chrome OS updates to prioritize security

It’s no surprise anymore that the coronavirus (COVID-19) pandemic is having a huge impact on nearly everything. In the technology space alone, we’ve seen major events get canceled, product launches pushed back, and the effects of changing working conditions. The next thing being affected by adjusted work schedules is Chrome and Chrome OS updates.

Due to adjusted work schedules, we’re pausing upcoming Chrome & Chrome OS releases. Our goal is to ensure they continue to be stable, secure, & reliable for anyone who depends on them. We’ll prioritize updates related to security, which will be included in Chrome 80. Stay tuned.

— Chrome Developers (@ChromiumDev) March 18, 2020

Chrome Developers shared the news on Twitter. Due to adjusted work schedules, they are pausing upcoming Chrome and Chrome OS releases. Google wants to make sure the releases remain stable, secure, and reliable. They plan on prioritizing updates related to security, which will be coming to Chrome 80.

While this may be disappointing to those who look forward to new features, it’s really for the best. There are a lot of people who work on Chrome who are adjusting to new working conditions. Pausing the releases will give everyone more time to react to issues and make fixes. A lot of people are relying on browsers to work from home right now, making the stability of Chrome and Chrome OS even more important. No timeline was given for the resuming of releases.

The post Google temporarily pauses Chrome and Chrome OS updates to prioritize security appeared first on xda-developers.

from xda-developers https://ift.tt/3dbDiji
via IFTTT

Android 11 Developer Preview 2: All the changes we’ve found so far!

Google has released the second Developer Preview for Android 11. You can download it on your Google Pixel device right now. We’ve been digging through Android 11 Developer Preview 2 and compiling all the new features and changes we’ve found so far. Check out the list below!

More Android 11 News

Notification History in Settings, shortcut in drawer

We wrote about the beginnings of a new Notification History section in the first Android 11 preview and now there is more to check out. The Notification History is actually visible in the Settings and there is a shortcut to this screen at the bottom of the notification shade.

“Require eyes to be open” for Face Unlock

The first Pixel 4 leaks showed the Face Unlock UI with an option to “require eyes to be open.” That wasn’t present on the phone at launch, but it looks like it’s finally here. The toggle is present in the Face Unlock settings.

“Manage Conversations” option in Settings

 

The first Android 11 preview brought a new “Conversations” section to the notification shade. Now, there is a “Manage Conversations” section in Settings > Notifications. This is for controlling which apps appear in the Conversations area.

Pixel Wallpaper picker gets a facelift

Google’s Pixel Wallpaper app has received a nice little facelift. The current wallpaper is displayed in a big preview at the top of the screen. The categories for the wallpaper choices are now displayed with square thumbnails with the names centered on top.

Pixel Themes prepares for clock face customization

Google has been tinkering with custom clock faces in Pixel Themes for a while and they are moving closer in Android 11 DP2. There is a new “clock” section for customization, but you can’t change anything yet. Baby steps.

New Screen Recorder UI

The first Android 11 preview added a screen recorder Quick Toggle and now the UI has been updated. It’s now a floating dialog with toggles to Record Audio and Show Touches on Screen.

“Tap to Restart” to make apps fit aspect ratio

Some apps don’t scale properly to the tall aspect ratios on newer devices. If an app isn’t scaled correctly, a new pop-up gives you the option to restart the app and make it full screen.

Wireless ADB debugging

It has been in the works for a while and it looks like Android 11 is finally getting wireless ADB. We first wrote about this back in October and now we can see it in the Android 11 settings. Users can pair a device with a QR code or a pairing code.

New IPSec VPN

There are new IPSec options available when you’re setting up a VPN. IPSec is a way to encrypt packets to be used within the VPN. It’s another standard people can use.

New “Allow from lock screen” option for accessibility volume key shortcut

There is a new toggle in the Accessibility settings to allow the user to access the volume key shortcut from the lock screen. The user can press both volume keys for 3 seconds to start an accessibility feature.

AOSP files app being replaced by Files by Google

It looks like Google is preparing to replace the old AOSP files app with Files by Google. You can access the old files app by going to Settings > Storage. Also, the “Other Storage” option in Files by Google is new. This allows users to access cloud storage providers (like Google Drive). The AOSP files app could do this and Google is using the API for Files by Google.

ANGLE preferences are back

ANGLE is a Chrome project that allows users to run WebGL and OpenGL ES content on the native APIs of any platform. Android 11 DP2 brings back the ANGLE Preferences in the Developer Options settings.

New “Enhanced Connectivity” toggle

We found a toggle for “Enhanced Connectivity” in the developer options. It says “Enables the Enhanced Connectivity” feature, but we’re not sure what that actually does yet.

New “HD audio” toggle for Bluetooth audio

Similar to Enhanced Connectivity, there’s a new toggle for “HD Audio” for Bluetooth audio. Connecting a Bluetooth audio device enables the toggle. Turning it off set the Bluetooth Audio codec to SBC, while turning it on set the codec to AAC (higher quality).

New “waterfall” and “punch hole” cutouts

“Punch Hole” and “Waterfall” have been added to the list of Display cutouts. You can mimic how these would look on your device.

Here are photos showing the new cutouts on the Pixel 3a XL pic.twitter.com/m5pyViBMg6

— Mishaal Rahman (@MishaalRahman) March 18, 2020

---

Thanks to XDA Recognized Developers Quinny899 and luca020400 for helping us find some of these features, and for providing some of the screenshots.

The post Android 11 Developer Preview 2: All the changes we’ve found so far! appeared first on xda-developers.

from xda-developers https://ift.tt/2UkNDR9
via IFTTT

Android 11 DP2 reveals Google is adding call recording support for dialer apps

The ability to record a phone call is vital for many users who conduct business over a voice call. It can also be really useful for anyone involved in legal, insurance, or medical matters. However, it isn’t easy for most users to record phone calls on Android. While some OEMs provide call recording functionality in their dialer applications, not every OEM makes this feature available. Third-party applications used to be able to record phone calls using roundabout methods, but Android 9 Pie made it completely impossible for third-party apps to record phone calls, at least without root access. Last year, Google said they were considering adding a call recording API in a future Android version, and it looks like that may finally be happening in Android 11.

Earlier today, Google released Android 11 Developer Preview 2. While digging into the new framework changes, we spotted a new permission called “ACCESS_CALL_AUDIO” with the protection level “appop” or “signature.” The “appop” permission, interestingly, can actually be granted to non-system applications, unlike the “signature” permission which requires the app to be signed by the OEM. Digging deeper, we spotted new strings that describe this permission in a bit more detail. According to one string, this permission can only be granted to the default dialer application, and it allows for the app to “record or play audio in telephony calls.”

<permission android.label="@string/permlab_accessCallAudio" android:description="@string/permdesc_accessCallAudio" android:name="android.permission.ACCESS_CALL_AUDIO" android:protectionLevel="appop|signature"/>
<string name="permdesc_accessCallAudio">Allows this app, when assigned as default dialer application, to record or play audio in telephony calls.</string>
<string name="permlab_accessCallAudio">Record or play audio in telephony calls</string>

We’re excited to see the possible introduction of call recording support for third-party dialer applications in Android 11. Google is finally adding call recording support for Pixel devices in the Google Phone app, but most devices can’t use the Pixel’s dialer app. With this change, users on devices that don’t have call recording support in the stock dialer app will be able to download a different dialer app from the Google Play Store to record their phone calls.

The post Android 11 DP2 reveals Google is adding call recording support for dialer apps appeared first on xda-developers.

from xda-developers https://ift.tt/2xHjV19
via IFTTT

Android 11 DP2 reveals work on “Quick Control” shortcuts in the Power Menu

When Google released Android 11 Developer Preview 1 last month, we spotted a new feature that we believed would transform the long-press power menu into a control center for home automation shortcuts. Now with the release of Android 11 Developer Preview 2, we managed to get this feature partially working.

Friend of the Portal and Recognized Developer Quinny899 shared the following two screenshots with us after flashing the latest Android 11 preview build on his Pixel 2 XL. After analyzing the framework and SystemUI last month, he developed an application that could hook into the new, in-development API. His app did not work last month, but it is now partially working in this release.

As you can see, he surfaced a new shortcut that appears in a “Quick Controls” section in the power menu. The power menu itself is revamped, with the tiles moving to the top of the screen, leaving a lot of room for quick controls. There’s also a menu button that, when tapped, opens the “add controls” activity that lets you select which apps’ shortcuts you want shown in the power menu. It is unclear where the new “Quick Access Wallet” feature will fit into this new power menu design.

Google hasn’t officially unveiled this new feature yet, but from our previous analysis, we believe that Google will reserve this space for home automation shortcuts. We found a list of “valid device types” in the Controls service in framework.jar that lists devices such as fans, coffee makers, AC units, curtains, and more that might be controllable from this UI. App developers will likely need to add support for this API to surface controls for their smart home appliances. We may hear more about this API during the virtual Google I/O 2020 event, assuming it doesn’t get postponed like Cloud Next 2020.

The post Android 11 DP2 reveals work on “Quick Control” shortcuts in the Power Menu appeared first on xda-developers.

from xda-developers https://ift.tt/3dcIIub
via IFTTT