Peafowl Theme Maker helps you make custom themes for Huawei and Honor devices running EMUI

Theming is an integral element of Android customization. Many OEMs that ship a custom flavor of Android on their phones bundle a theming engine to let users decorate their phones as they like. Similar to MIUI and ColorOS, Huawei also offers theming functionality on its custom skin EMUI through the Themes app. The app offers a wide selection of preset themes to choose from. But what if you wanted to build your own custom theme?

If that’s what you are looking for then look no further than Peafowl Theme Maker: an app from XDA Senior Member hamzio7 that lets you create fully custom themes for any Honor and Huawei phones running EMUI 5 and above. 

With Peafowl Theme Maker, you can pick from a wide range of icon packs, wallpapers, fonts, mods, and accent colors to create truly personalized themes for your Huawei and Honor phone. You can theme the notification panel, the Settings app, the dialer app, and a bunch of system apps.   

Here’s a highlight of some of the most notable features of Peafowl Theme Maker:

• Adaptive Icon packs: Shape your icons as you like
• Lots of icon packs to choose from
• Multiple Presets: Updated Regularly
• Color picker For Apps accent Color
• Wallpapers Gallery: Updated Regularly
• Light and Dark themes
• Unlimited Customizations

Peafowl Theme Maker XDA thread

Themes created using Peafowl Theme Maker are compatible with Huawei and Honor devices running EMUI 5, EMUI 8, EMUI 9, and EMUI 10. The app is available on Google Play Store free of cost with an in-app purchase option that unlocks additional features and removes ads. 

Peafowl Theme Maker for EMUI 5.X/8.X/9.X/10.X (Free⁺, Google Play) →

 

The post Peafowl Theme Maker helps you make custom themes for Huawei and Honor devices running EMUI appeared first on xda-developers.

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

Android 11 DP3 tests letting you resize picture-in-picture windows

Earlier today, Google released Android 11 Developer Preview 3 for Pixel devices. I installed the latest build onto my Pixel 3a XL and have been documenting what I’ve found so far (a more detailed article is soon to come!) One of the more interesting new features we discovered in this release is the ability to resize picture-in-picture windows. This feature is currently in testing and is not enabled by default, however.

Google introduced picture-in-picture windows to Android smartphones in Android 8.0 Oreo. You can open a video in a picture-in-picture window in supported applications by pressing the home button or performing the home gesture when the video is playing. By default, the PiP window floats on top of the screen in the bottom right-hand corner, but the user can move the PiP window around or dismiss it by dragging it to the bottom of the screen.

In Android 11 DP2, Google added code for resizing PiP windows under the PipResizeGestureHandler class in SystemUI, but the feature was not yet functional. In Android 11 DP3, though, the ability to resize picture-in-picture windows is now fully functional after manually issuing a development command. PiP windows can be resized by touching right outside one of the four corners and then dragging outward or inward to expand or shrink the window, respectively. The aspect ratio of the window will be maintained when resizing so as to not distort the video. Here’s a demonstration of the new feature on my Pixel 3a XL running Android 11 DP3:

As you can see in the screen recording above, I launched a YouTube video into a PiP window and then enlarged the window by dragging outward near the corners. Placing your finger on the exact area where you need to initiate the resize gesture is a bit tricky, but I managed to resize the window twice in the video. We don’t know if Google plans on releasing this feature in the stable Android 11 release, but we’ll keep an eye out on it for further developments.

The post Android 11 DP3 tests letting you resize picture-in-picture windows appeared first on xda-developers.

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

Google is preparing to let you use “Live Captions” during phone calls

Google first announced its “Live Captions” accessibility feature at Google I/O 2019 last year. Using three on-device machine learning models, this feature detects English-language speech in media and generates captions automatically. The feature was first made available on the Pixel 4 but later expanded to the Pixel 3a, Pixel 3, Pixel 2, Samsung Galaxy S20, OnePlus 7T, and OnePlus 8. Since the feature launched, however, it hasn’t received any updates to its functionality. That could change soon, though, as we spotted evidence that Google will allow Live Caption to work over phone calls.

An APK teardown can often predict features that may arrive in a future update of an application, but it is possible that any of the features we mention here may not make it in a future release. This is because these features are currently unimplemented in the live build and may be pulled at any time by the developers in a future build.

In Android 11 Developer Preview 3 for the Google Pixel 4, we analyzed version 2.13.302920511 of Device Personalization Services, the application responsible for Live Captions. In it, we spotted strings that state users will be able to turn on Live Caption over a phone call.

<string name="call_confirmation_cancel">CANCEL</string>
<string name="call_confirmation_confirmation_message">Enable Live Caption over this phone call? Your use of the feature will be annonunced to others on the call.</string>
<string name="call_confirmation_dialog_name">Enable Live Caption confirmation dialog</string>
<string name="call_confirmation_enable">ENABLE</string>
<string name="call_other_side_transcription_prefix">Caller</string>
<string name="call_system_message_prefix">System</string>
<string name="call_turn_indicator_text">…</string>
<string name="call_user_typed_input_prefix">You typed</string>

Enabling the feature over a phone call will announce to all participants that the call is being transcribed into captions. An audio file will be played in the phone call, and this audio file simply says the following line:

<string name="system_message_start_call_speaking_mode">Hi, the person you’re about to speak with has call captions turned on. They’ll see captions of what you say to help them listen along.</string>

Currently, the API that Live Captions relies on, AudioPlaybackCaptureConfiguration, does not allow for capturing voice call audio. However, it’s possible that a new system-only permission added in Android 11 Developer Preview 3 will allow the feature to bypass this restriction.

---

Thanks to PNF Software for providing us a license to use JEB Decompiler, a professional-grade reverse engineering tool for Android applications.

The post Google is preparing to let you use “Live Captions” during phone calls appeared first on xda-developers.

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

Xiaomi Mi 10 Pro Unboxing and Hands-On [Video]

Late last month, Xiaomi launched its latest flagship, the Mi 10 Pro, globally. The device was originally planned to be unveiled at MWC 2020, but plans obviously changed. XDA TV‘s Max Weinbach got his hands on the Xiaomi Mi 10 Pro and shared his first impressions of the device.

Perhaps not surprising considering it’s the company’s most recent device, Max says the Mi 10 Pro is the best Xiaomi phone ever made. Everything about it from the specifications to the fit and finish is very premium. However, all of that comes at a price. The Xiaomi Mi 10 Pro is the company’s most expensive device ever as well.

Xiaomi Mi 10 XDA Forums

All things considered, Max says the phone is “fantastic.” The price is the only problem. There are plenty of flagship phones in 2020 with $1,000+ price tags. When you’re putting that much money down for a phone, the decision becomes even harder. Max will explore that more in his full review, but in the meantime, you can check out his unboxing and hands-on below.

Specification	Xiaomi Mi 10	Xiaomi Mi 10 Pro
Dimension & Weight	162.6 x 74.8 x 9 mm 208g	162.6 x 74.8 x 9 mm 208g
Display	6.67″ OLED 2340 x 1080 HDR10+ 90Hz 180Hz touch response Peak Brightness: 1120 nits Hole-punch for camera	6.67″ OLED 2340 x 1080 HDR10+ 90Hz 180Hz touch response Peak Brightness: 1200 nits Hole-punch for camera
Security	In-display fingerprint sensor Software-based face recognition	In-display fingerprint sensor Software-based face recognition
System-on-Chip	Qualcomm Snapdragon 865: 1x Kryo 585 (ARM Cortex-A77-based) Prime core @ 2.84GHz 3x Kryo 585 (ARM Cortex-A77-based) Performance core @ 2.4GHz 4x Kryo 385 (ARM Cortex A55-based) Efficiency cores @ 1.8GHz Adreno 650	Qualcomm Snapdragon 865: 1x Kryo 585 (ARM Cortex-A77-based) Prime core @ 2.84GHz 3x Kryo 585 (ARM Cortex-A77-based) Performance core @ 2.4GHz 4x Kryo 385 (ARM Cortex A55-based) Efficiency cores @ 1.8GHz Adreno 650
RAM	up to 12GB LPDDR5	up to 12GB LPDDR5
Storage	up to 256GB UFS 3.0	up to 512GB UFS 3.0
Battery & Charging	4,780 mAh 30W Fast Wired Charging 30W Fast Wireless Charging 10W Reverse Wireless Charging	4,500 mAh 50W Fast Charging 30W Fast Wireless Charging 10W Reverse Wireless Charging
Rear Camera	108MP Wide 1/1.33″, 7P lens, OIS 13MP Ultra-Wide, 123°,  f/2.4 2MP f/2.4 Macro Camera 2MP f/2.4 Depth Sensor	108MP Wide 1/1.33″ 8P Lens, OIS 20MP Ultra-wide, 117°, f/2.2, 6P Lens 12MP Portrait Lens, f/2.0 8MP Telephoto Lens with 10x Hybrid Zoom, OIS
Front Camera	20MP	20MP
Software Version	Android 10	Android 10
Connectivity	5G: SA/NSA Wi-Fi 6 USB Type-C NFC Bluetooth v5.0	5G: SA/ NSA Wi-Fi 6 USB Type-C NFC Bluetooth v5.0
Audio	Stereo speakers, Hi-Res Audio certified	Stereo speakers, Hi-Res Audio certified
Colors	Coral Green, Twilight Grey	Solstice Grey, Alpine White

The post Xiaomi Mi 10 Pro Unboxing and Hands-On [Video] appeared first on xda-developers.

from xda-developers https://ift.tt/3511hxM
via IFTTT

How to download Android 11 Developer Preview for Google Pixel and other Android devices

Google has officially kicked off the Android 11 Developer Preview program, just five months after the stable release of Android 10. They’re starting things a little earlier this year (the first Android Q beta dropped in March). If you’re curious about the next version of Android, you can download Android 11 right now for the Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, and Pixel 4 XL (the original Google Pixel and Pixel XL are not officially supported).

This page will serve as an archive for all the Android 11 developer preview/beta releases. We will keep the page updated with the latest OTAs and factory images for supported devices. You can learn how to install the Android 11 developer preview with our guide for Pixel devices here.

---

Android 11 Developer Preview 1

Device	OTA	System Image
Pixel 2	Link	Link
Pixel 2 XL	Link	Link
Pixel 3	Link	Link
Pixel 3 XL	Link	Link
Pixel 3a	Link	Link
Pixel 3a XL	Link	Link
Pixel 4	Link	Link
Pixel 4 XL	Link	Link

GSI Downloads

ARM64+GMS	Link
x86+GMS	Link

---

Android 11 Developer Preview 2

Device	OTA	System Image
Pixel 2	Link	Link
Pixel 2 XL	Link	Link
Pixel 3	Link	Link
Pixel 3 XL	Link	Link
Pixel 3a	Link	Link
Pixel 3a XL	Link	Link
Pixel 4	Link	Link
Pixel 4 XL	Link	Link

GSI Downloads

ARM64+GMS	Link
x86+GMS	Link

---

Android 11 Developer Preview 3

Device	OTA	System Image
Pixel 2	Link	Link
Pixel 2 XL	Link	Link
Pixel 3	Link	Link
Pixel 3 XL	Link	Link
Pixel 3a	Link	Link
Pixel 3a XL	Link	Link
Pixel 4	Link	Link
Pixel 4 XL	Link	Link

GSI Downloads

x86+GMS	Link
ARM64+GMS	Link
x86_64	Link
ARM64	Link

The post How to download Android 11 Developer Preview for Google Pixel and other Android devices appeared first on xda-developers.

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

Android 11 Developer Preview 3 is live with ADB Incremental support, Wireless Debugging, and more

Back in February, Google released the first Android 11 Developer Preview for Pixel smartphones (except for the 2016 Pixels). The company aimed to release two more Developer Previews before opening up the beta for non-Pixel devices. Google released the second Android 11 DP in March, and today, they’re following up with Android 11 Developer Preview 3. The third Developer Preview adds one major feature and makes a few other tweaks to existing ones introduced in earlier DPs. Here’s what has changed.

What’s new in Android 11 Developer Preview 3

App exit reasons updates

In Android 11, apps can retrieve a record of the reasons behind the most recent app deaths using the new getHistoricalProcessExitReasons method in the ActivityManager class. The new ApplicationExitInfo class details the information that apps can retrieve for their historical exit reasons, which can include factors like the system running low on memory, a native code crash, a runtime permission change, excessive resource usage, etc. These APIs have been updated in Developer Preview 3 based on developer feedback, which Google is actively seeking.

GWP-ASan heap analysis

Earlier Android 11 Developer Previews added a number of tools to help developers find and fix memory safety issues. The latest is GWP-ASan (also known by its recursive backronym “GWP-ASan Will Provide Allocation Sanity”), a “sampling allocation tool that detects heap memory errors with minimal overhead or impact on performance.” In Android 11 Developer Preview 3, GWP-ASan is enabled by default in platform binaries and system apps but developers can also enable it for their applications as well. Google recommends doing so if your app uses native code of libraries.

ADB Incremental 

Google wants to make it faster for developers to install large APKs so they’re introducing a new ADB Incremental feature. This feature can make installing large APKs (2GB+) from a PC to a phone up to 10X faster than before. In Android 11 Developer Preview 3, developers can install an incremental APK using the “adb install –incremental” command in the latest ADB binary. APKs must be signed with the new APK Signature Scheme v4 format, which generates a signature in a separate file. This feature also requires that the device support the new Incremental File System, which is currently only supported by the Pixel 4 and Pixel 4 XL. Google says that all Android 11 launch devices will support the Incremental File System and hence ADB Incremental.

Wireless Debugging

Wireless ADB is now easier than ever in Android 11 with the new “wireless debugging” option in Developer Options. We first saw this feature in Android 11 Developer Preview 2, but Google never emphasized it was there. You can currently pair your phone to a PC using the pairing code workflow, but Google says they plan to add a QR code scanning workflow in a future Android Studio release.

Wireless debugging in Android 11 under Settings > Developer options

Data access auditing updates

Finally, Google has updated the new data access auditing APIs in Android 11 Developer Preview 3. Specifically, Google has renamed several of the APIs, so make sure to update your app if you’re using any of them. A sample application can be found here. Feedback can be given here.

Download Android 11 Developer Preview 3

You can go here to see the full API diff between Android 11 DP2 and DP3, but we’ll, of course, be on the lookout for any notable changes that Google hasn’t publicized. You can read the release notes here, which we recommend doing before you download and flash the update. Lastly, be sure to go here to file any bug reports and here to discuss the latest release.

We’ll have links to download the latest system images for Google Pixel devices and Project Treble-compatible devices on this page. You can either flash the builds manually or use the Android Flash Tool to do it for you. If you don’t have a compatible device, you can run the preview build in Android Studio’s Android Emulator.

---

This is the third and final Developer Preview. There will be 2 beta releases which will include non-Pixel devices followed by the stable release sometime in Q3.For all the latest Android 11 news, bookmark this tag:

Android 11 News on XDA

The post Android 11 Developer Preview 3 is live with ADB Incremental support, Wireless Debugging, and more appeared first on xda-developers.

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

AT&T expands its low-band 5G network to 90 new markets

Remember when Sprint sued AT&T for misleading consumers with the “5G E” branding but later settled the dispute? In a cruel twist of fate, now a bunch of Sprint phones are going to lose their 5G connectivity following the merger with T-Mobile. Meanwhile, AT&T continues to expand its 5G network across the US. As a quick refresher, AT&T originally initiated the rollout last year, and later partially introduced its mmWave network last month. The carrier has now added a whopping 90 new cities under the 5G umbrella.

The list of new cities goes as follows:

• Alabama
  • 1. Franklin County
• Arkansas
  • 2. Fayetteville-Springdale
  • 3. Fort Smith
• California
  • 4. Chico
  • 5. El Dorado County
  • 6. Redding
  • 7. Sacramento
  • 8. Tehama County
  • 9. Yuba City
• Colorado
  • 10. Colorado Springs
• Connecticut
  • 11. New London-Norwich
• Florida
  • 12. Bradenton
  • 13. Dixie County
  • 14. Fort Pierce
  • 15. Hamilton County
  • 16. Hardee County
  • 17. Ocala
  • 18. Pensacola
  • 19. Sarasota
  • 20. Tampa
• Georgia
  • 21. Dawson County
  • 22. Marion County
• Idaho
  • 23. Boise City
  • 24. Boundary County
• Illinois
  • 25. Chicago
  • 26. Mason County
• Indiana
  • 27. Elkhart-Goshen
  • 28. Evansville
  • 29. Fort Wayne
  • 30. Gary
  • 31. South Bend
• Kansas
  • 32. Brown County
• Kentucky
  • 33. Fulton County
  • 34. Mason County
  • 35. Meade County
  • 36. Trimble County
• Louisiana
  • 37. Beauregard Parish
  • 38. Houma-Thibodaux
  • 39. Lake Charles
  • 40. New Orleans
  • 41. Shreveport
• Massachusetts
  • 42. Springfield
• Michigan
  • 43. Cass County
• Minnesota
  • 44. Duluth
  • 45. Le Sueur County
  • 46. St. Cloud
• Missouri
  • 47. Bates County
  • 48. Callaway County
  • 49. De Kalb County
  • 50. Joplin
  • 51. Saline County
  • 52. St. Joseph
• Montana
  • 53. Billings
  • 54. Mineral County
• New Hampshire
  • 55. Portsmouth
• New Jersey
  • 56. Vineland
• New York
  • 57. Yates County
• Ohio
  • 58. Clinton County
  • 59. Mercer County
  • 60. Morrow County
  • 61. Perry County
  • 62. Steubenville
• Oklahoma
  • 63. Grant County
• Oregon
  • 64. Clatsop County
• Pennsylvania
  • 65. Greene County
  • 66. Johnstown
  • 67. Union County
  • 68. Wayne County
  • 69. Williamsport
• Texas
  • 70. Abilene
  • 71. Beaumont
  • 72. Concho County
  • 73. Fannin County
  • 74. Lubbock
  • 75. Newton County
  • 76. Sherman-Denison
  • 77. Waco
• Virginia
  • 78. Frederick County
• Washington
  • 79. Bellingham
  • 80. Clallam County
  • 81. Ferry County
  • 82. Kittitas County
  • 83. Richland-Kennewick
  • 84. Seattle
  • 85. Tacoma
  • 86. Yakima
• West Virginia
  • 87. Monongalia County
  • 88. Parkersburg-Marietta
  • 89. Wheeling
• Wisconsin
  • 90. Madison

According to AT&T, they are covering “… more than 120 million people” with the latest expansion which is based on low-band spectrum. On the other hand, mmWave 5G, which is branded as “5G+” by AT&T, is based on ultra high-band frequencies and can offer much faster speed than low-band 5G. However, the scope of mmWave is extremely limited (you should be in very specific locations to connect properly), thus upgrading existing LTE infrastructure to low-band 5G is indeed an effective measure.

---

Source: AT&T

The post AT&T expands its low-band 5G network to 90 new markets appeared first on xda-developers.

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