Hate Display Notches? Hide the Notch for Free with “Nacho Notch—Notch Hider!”

Although the Apple iPhone X gets all of the blame for Android phones with notches, it was actually the Essential Phone that first implemented the controversial display notch. This year, we're seeing many smartphone makers pursuing the display notch. The ASUS Zenfone 5/5Z, the rumored LG G7, the Huawei P20, and the OnePlus 6 are all either rumored or are confirmed to have notches. Only Samsung and Xiaomi have bucked the trend so far with their flagship devices, the Samsung Galaxy S9 and the Xiaomi Mi Mix 2S respectively. If you're looking to buy a new phone this year, there's a good chance it may have a notch, but fret not, there's a way to hide the notch for free! Introducing "Nacho Notch—Notch Hider!"

This is a free app developed by XDA Forum Moderator Zacharee1 and it only has one purpose: hiding the display notch. The way it works is simple: it draws an entirely black overlay above the status bar but below the other status bar elements. That way, the status bar background is black but the notification icons, clock, and other status bar icons are still visible on top. The overlay also automatically hides itself when you switch your phone to landscape mode, so it won't cover up part of the status bar accidentally.

The app is implemented as a quick settings tile. Just add the tile to your quick setting tiles and you can quickly toggle the notch on/off. No need to waste space in your app drawer with an app that only has a single function!

Admittedly, this isn't a novel idea. The rumored LG G7 was seen having such a feature, and the Huawei P20 is confirmed to have such a feature. Clearly, these companies recognized that not everyone will be happy with their design decision, so they have opted to allow users to hide the notch by darkening the status bar area.

What hiding the notch looks like on the Huawei P20

And that's exactly what "Nacho Notch—Notch Hider" does! You just need to install the app, make sure it has the ability to "draw over other apps" so it can hide the notch (if you install it from the Play Store, you won't have to worry about that), and be on your way! The app needs a persistent notification so Android doesn't kill it in the background, but it's easy to hide the notification so it doesn't get in your way (just long-press on the notification and hide it!) Try it out and let us know how it goes!

Install Nacho Notch—Notch Hider from the Google Play Store

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

EMUI 8.0 Beta on the Honor 7X

The EMUI 8.0 Beta for the Honor 7X has pushed to phones of users who are participating in the beta program. This update brings Android Oreo to the 7X, which has become an international best seller on Amazon.

This update brings some new EMUI features to the 7X along with everything you can expect in an Oreo update. Some of these new features include updated icons, new settings layout, AR lens, and floating nav bar.

EMUI 8.0 Homescreen

EMUI 8.0 App Drawer

Picture in Picture Mode

Google Feed Toggle in Home Settings

Floating Nav Bar Toggle

AR Lens

So far the beta is running very smoothly and even has some significant performance improvements. Benchmarks across the board are providing higher scores with Oreo.

Check out the forums to follow the developments of the Beta.

Honor 7X Forums Learn More About the Honor 7X

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

Verizon is reportedly planning to launch a Palm-branded Android phone

It's interesting to see old phone brands that died down in popularity years ago have a revival, with BlackBerry and Nokia being two of the most famous examples here. These two smartphone brands are owned by different companies, TCL and HMD Global respectively. They are also experiencing contrasting reception in the smartphone market as sales of BlackBerry-branded devices are much lower than sales of Nokia-branded devices.

Palm is another old brand which has experienced a lot of success in the past, as the company pioneered PDA devices back in the 1990s. It also launched webOS to compete with Android and iOS, but the venture was not successful. The company was sold to HP in 2010, with webOS rights being sold to LG in 2013. TCL acquired the rights to the Palm name back in 2015.

Last year, a TCL executive confirmed that the company was planning to launch Palm-branded smartphones in 2018. Now, Android Police states the current plan is that at least one such device will be launching on U.S. carrier Verizon Wireless in the second half of 2018. The phone will be powered by Android, but apart from that, nothing is known about its specifications.

Android Police notes that Verizon has been a long-time partner of Palm. The carrier had sold most of Palm's webOS phones, including the Pre 2. It also intended to carry the Palm 3, but HP canceled the phone before it could be released in the US.

As of now, it's unknown whether the Palm-branded Android phone will have a normal slate touchscreen form factor or something different (such as a slider having a hardware QWERTY keyboard). TCL's recent BlackBerry-branded phones haven't been a huge hit recently, but that doesn't mean that Palm-branded phones will receive the same reception. It all depends on how well the phone is executed in the market. On a different note, it's worth noting that the legacy of webOS lives on in gesture navigation, which is starting to become popular in some Android phones.

We expect to learn more about the upcoming phone in the coming months.

---

Source: Android Police

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

AT&T LG V30 now receiving Android Oreo with LG V30S ThinQ’s AI features

LG's flagship smartphone is the V30 series, and despite poor financial showings causing a shift in the company's business strategy, LG is still chugging along with new smartphone releases and software upgrades for its existing devices. The LG V30S ThinQ is the company's latest offering which brings LG's Vision AI and Voice AI features to a slightly higher-end LG V30 model. LG promised to bring these AI features to the V30 in the upcoming Oreo update, and it appears that the company is keeping its promise. After rolling out to the Verizon model, the AT&T LG V30 Android Oreo update is now rolling out according to users on our forums.

Credits: XDA Senior Member jschramm

The update brings the March security patch to the device and interestingly we're told that the boot splash screen shows the device model as the V30S ThinQ. Besides all of the usual Android 8.0 Oreo features such as picture-in-picture mode, notification channels and snoozing, Autofill API, and smart text selection, the AI features are there as promised. For instance, the new "AI Cam" mode in the camera app lets you identify images, scan QR codes, change scene modes automatically, and more.

There's still no word on when the Android 8.1 Oreo update will roll out, unfortunately. The Oreo update is supposed to bring ARCore support for the V30, so if you've received the update do let us know if the augmented reality platform works on your device. You can download ARCore from the Play Store below if your device is marked as supported.

ARCore (Free, Google Play) →

Note: I personally think that the LG V30S ThinQ is a ridiculous name, and that the term "AI" has been bludgeoned to death by every smartphone manufacturer on the planet.

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

Wear OS Developer Preview brings Android P platform features, now available for Huawei Watch 2

Google's wearable operating system hasn't been a huge success so far. When it launched in 2014, there was a lot of hype around wearables, and we saw plenty of manufacturers release Android Wear-powered smartwatches. In the years since, however, we have seen a decline in interest by vendors in building new smartwatches for Google's wearable operating system. To help combat this, Android Wear was re-branded as "Wear OS by Google" a few weeks ago. Now, the first Android P-based Wear OS Developer Preview has been launched, bringing Android P platform features to wearables.

Updated system images on the official Android Emulator are now available. Users can manually download and flash a system image for the Huawei Watch 2 Bluetooth and Huawei Watch 2 Classic Bluetooth. Google states that this initial release is intended only for developers and is not intended for daily or consumer use. As such, it's only available via manual download and flashing.

The first Wear OS by Google Developer Preview brings restrictions related to non-SDK methods and fields. Android P has started restricting access to non-SDK methods and fields to improve app compatibility. Google states that developers should make plans to migrate away from them. The company also wants developers to let it know if there is no public equivalent for a particular use case.

Since the start of the year, Wear OS has switched to a dark UI system theme with a dark/black background for the notifications stream and system launcher. Now, the dark UI system theme is the default in order to make it easier to glance at wear apps. Google advises developers to check the accessibility of their app's UI after this change.

In another change, apps will no longer be allowed to run in the background unless the watch is on the charger. This will be done to improve power. Google states that developers should note Wear OS is "going further" with Android's app standby feature than some other form factors. The exceptions to this include watch faces and applications the user has currently selected. The company adds that this feature will be rolled out gradually in the developer preview and developers should remove background services in their apps.

Finally, Wear OS developer preview turns off Bluetooth, Wi-Fi, and cellular radios when the watch is detected to be off the body for an extended period of time to improve power. This feature will be rolled out gradually as well, so it may not be immediately visible. Developers can disable this feature via ADB if it causes challenges to their development process. Also, the device will no longer connect to Wi-Fi when disconnected to Bluetooth for the same purpose of improving power. The exceptions to this include if an app is requesting a high bandwidth network or if the watch is on the charger.

Google states that it expects to provide several updates to this preview before the final production release. Users are also advised to refer to the release notes for known issues before downloading and flashing their device.

---

Source: Google

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

Chrome OS prepares to support ARCore for augmented reality apps

ARCore, Google's augmented reality development platform for Android, is software-based. Unlike the Mountain View company's ill-fated Project Tango, it doesn't require special hardware or sensors in order to map the depth of surroundings and project digital objects onto real-world surfaces. As a result, it's compatible with a growing range of devices. (ARCore for All, an open source project, even gets ARCore up and running on technically "unsupported" devices like the OnePlus 3T.) Now, Google appears to be preparing to bring ARCore to a new platform: Chrome OS.

A new commit in the Chromium Gerrit, the code review website for Google Chrome and Chrome OS, explicitly mentions a refactor to add "support [for] ARCore." Specifically, it describes a process for creating ARCore devices through WebXR API, a web framework for virtual reality (VR) and AR content (and the successor to WebVR). XRSessionCreationOptions provides a session description for a subsequent XRSession object, which acts as a middleman for XR hardware components such as orientation sensors and cameras, providing features such as polling the device pose, getting information about the environment, and rendering images.

Support in Chrome OS probably isn't intended for Chromebooks in laptop form factors, as you might well imagine. Unlike Snapchat's Lens technology and Facebook's Camera Effects and AR Studio tools, ARCore can't track facial features or model head movements; it uses a combination of motion tracking, flat surface detection, and light estimation to anchor virtual objects to vertical and horizontal planes. For that reason, ARCore is likely bound for Chrome OS devices with tablet form factors such as the Acer Chromebook Tab 10, which was announced this week, and the rumored Samsung Nautilus detachable Chromebook.

In fact, a comment left on another commit adding a new Chrome OS device with the code name "Atlas" hints at ARCore support for Chrome OS tablets.

In any case, support for the augmented reality platform in Chrome OS dovetails with the impending addition of native video recording (using MediaRecorder APIs and HW VEA) to the platform, a commit for which we uncovered in January. And it's yet another blurring of the lines between Android and Chrome OS. Recently, Google introduced Android-inspired features such as a touch-friendly launcher, lock screen notifications, the Google Assistant, and a split-screen mode to the browser-based operating system.

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

Google is finally fixing an issue that bricked some Pixel 2 devices with Android 8.1 Oreo update

Every month, Google releases a new security patch update for support Nexus and Pixel devices. You have the option to either wait for the OTA update or to manually flash the update via fastboot. Shortly after the release of the Google Pixel 2 and Pixel 2 XL, Google released the first Android 8.1 Oreo Developer Preview. Rather than wait for the OTA to roll out, some people decided to flash the factory image for the release. After all, if it works for security patch updates it should be fine to do so for major OS upgrades, right? Unfortunately, some users of the Google Pixel 2 quickly discovered that flashing the update via fastboot was a mistake. Flashing the Android 8.1 Oreo Developer Preview caused some users' devices to be soft-bricked, and now, 5 months after this incident, Google is finally putting in place checks to ensure this doesn't happen again.

Back in October, some tech journalists such as Ron Amadeo from ArsTechnica, Steven Hall from 9to5Google, and our very own Daniel Marchena discovered that their phones were not properly flashing the Oreo 8.1 factory images. For some users, this caused their device to no longer boot. After a few hours, Google caught wind of the issue and temporarily pulled the factory images. Besides a vague mention of an issue with the bootloader, not many details were shared about what was going on. Two fixes for the issue involved updating the fastboot binary on the PC and/or to extract the factory image and flash every partition manually.

But now we know exactly what caused the problem, and what Google is doing to fix it. In a new commit to the Android Open Source Project (AOSP), Google acknowledges that the Android 8.1 Oreo release for the Pixel 2 was "a bit of a disaster" because users with an outdated version of fastboot would "blindly flash too few partitions." This is what caused the early Pixel 2 bricks, apparently. The commit adds a new feature to the fastboot protocol that lets a text file specify when a device has a partition that must be flashed too, which should hopefully prevent another situation like this occurring again.

So that's the end of the Pixel 2 failed update saga. There was never anything wrong with the factory image themselves, but rather people using outdated fastboot binaries. Lesson learned: update your files before you try flashing a new OS upgrade over fastboot!

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