Sunday, October 29, 2017

The Huawei Mate 10 Duo is Held Back by Nonsensical Feature Disparities

Just why does the Huawei Mate 10 Pro omit so many "pro" features?

Early this year, while I was still reeling from the Note7 disaster, I was on the hunt for a large, powerhouse Android phone. Traditionally I have two phones I alternate between, a smaller and a larger one. Usually one of these is an iPhone and the other is a large Android since I prefer Android over iOS on a large display. The Note7 left a hole in my lineup last year though, and while it was filled with the LG V20  that phone just didn't cut it for a number of reasons, from the encumbering software to terrible light bleed. Early this year though, I was walking through my local Best Buy and saw the Huawei Mate 9.

Now Huawei is a brand that I had heard of, but never actually used outside of a very short stint with the Nexus 6P. While I admired their build materials, the 6P left a pretty bad taste in my mouth from my unit chipping around the camera bezel after a few short days, and their construction choices resulting in 'Bendgate II' and general fragility. But the Mate 9 called to me: It had minimal bezels, a large 5.9" display rivaling my old Nexus 6 in size, a dual speaker setup, a new-to-me dual camera layout, along with a massive battery. Its large display was beautiful despite its lower resolution, likely due to using IPS LCD and its RGB subpixel layout instead of the crispness-killing Pentile AMOLED that phones like the OnePlus 3 used at the same 1080p resolution. EMUI was also a solid performer delivering a smooth Android experience despite its flaws, which ultimately prevented the Mate 9 from becoming the best phone for me and my needs. So when Huawei began talking about this year's Mate 10, I was unusually excited. However, that hype quickly dissipated as Huawei announced what is likely the most confusing phone duo (or trio, if we count the Porsche edition) we have seen yet, with odd omissions from each model and terrible global availability. Where do we even start?

Huawei Mate 10 Huawei Mate 10 Pro
Display 5.9″ 2560×1440 RGBW HDR LCD Panel 6″ 2160×1080 OLED Panel
SoC Kirin 970 SoC, Mali G72 GPU Kirin 970 SoC, Mali G72 GPU
RAM 4GB 4GB/6GB
Internal Storage 64GB 128GB
MicroSD Card Slot Yes No
Rear Cameras 12MP RGB + 20MP Monochrome Camera, both f/1.6 12MP RGB + 20MP Monochrome Camera, both f/1.6
Front Camera 8MP Front Camera with an f/2.0 Aperture 8MP Front Camera with an f/2.0 Aperture
3.5mm Headphone Jack Yes No
Certification IP53 IP67
Fingerprint Scanner Yes (front) Yes
Price €699 €799

Plain Jane Mate 10

If you were hoping that the Mate 10 would be a no-frills all-out flagship like the Mate 9 was, but with 2017 hardware updates… then prepare to be disappointed. While it is an improvement over the Mate 10, it also is not the large upgrade we have come to expect from some of this year's flagships. They did see fit to upgrade to a QHD display, but it retains its 16:9 aspect ratio resulting in a wider than standard device. Some people prefer this layout and while I can see why they do, the advantages afforded by 18:9 are massive if done properly (especially when screens get this large). They also kept the 3.5mm headphone jack (thankfully!), but weren't able to add any sort of viable IP rated water resistance. The battery sticks with the Goliath 4,000mah capacity, but RAM remains at 4GB. The phone is a little narrower and considerably shorter, but Huawei ditched the aluminum unibody design for a glass back simply for eye appeal without adding any of the benefits glass brings, like the ability to have wireless charging. A note to device manufacturers: if you are going to force glass on us, at least make it so we can argue away its downsides with benefits like wireless charging. This feels a lot like the HTC U11, which is glass for the sake of being glass with all its downsides and none of the benefits. Nokia proved earlier this year that you can make an eye-catching aluminum design that is stronger and more durable. As I mentioned earlier, the Mate 10 is an improvement in many areas over the Mate 9, especially when you factor in Huawei's new AI enhanced camera system, but it is not quite the huge leap some of us may have hoped for. It's certainly not the thorough leap I expected, with some of its biggest virtues being the presence of a 3.5mm headphone jack (meaning the fact that they didn't remove a feature). While I expected a powerhouse device, most of the upgrades here are half-baked in places where there's still room for improvement, as other 2017 devices have shown. But for those of us who want a little more than the Mate 10 provides there is the Mate 10 Pro… right?


Not-So-Pro Pro

When Huawei decided to bring back the Pro version of the Mate this year, they might have forgotten exactly what "Pro" means. While the changes between the Mate 9 Pro and Mate 10 Pro are similar to the improvements seen in the standard versions, there is one critical and deal-breaking spec that Huawei bewilderingly stepped down in. Last year the Pro model had a 5.5" curved AMOLED display with a QHD resolution, this year the Pro model ships with a larger 6" 18:9 AMOLED panel but at a lower 1080p resolution. So to get this right, the standard model went from FHD to QHD, and the Pro model went from QHD to FHD. The additions of HDR support and the taller 18:9 aspect ratio do not make up for this large decrease in resolution over the standard version, it's a nonsensical step back from a device that's supposed to be the "Pro" version of a powerhouse flagship. One thing to note is that the total area of the display is a little smaller than a traditional 16:9 6" display reducing the PPI hit somewhat with the Pro landing at 402PPI — still not enough, but better. Huawei did add IP67 water resistance to the Pro but removed the 3.5mm headphone port despite this year's Pro being larger in nearly every dimension compared to last year's, which had the port. And, again, it makes us wonder just how this can possibly be the "Pro" version of the Mate 10, when it's clearly regressing in a valuable features that Pros may desire in a phone. Further, the phone still does not support MicroSD expansion like its sibling does either, but it does ship with (up to) 6GB of RAM and 128GB of internal storage, a substitute I am certainly ok with (and I'd argue this is what the regular Mate 10 should have offered in the first place). These omissions and downgrades in the "Pro" model leave me scratching my head wondering why these are even in the same family of phones, or why they are called a "standard" and "Pro" model.

"Can a Mate 10 Pro be less Mate Pro than a non-Pro Mate 10 Pro?"


…It's Just So Confusing!

Regardless of your needs or wants in a new phone you will likely find yourself straddling both devices. The Mate 10's SD card expansion, QHD display, and 3.5mm headphone port, are appealing as are the Pro's 18:9 aspect ratio, water resistance, and 6GB of RAM. Despite its older 16:9 aspect ratio, which some users may actually prefer, I feel that many users would find themselves in the standard Mate 10 camp despite its downsides (and because of its lower price tag). Unfortunately, for those of us in the US and UK at this time are left to think about what could have been, since the phone will reportedly not be making it to our shores leaving us with the unimpressive, underwhelming and likely overpriced Mate 10 Pro as our only option.


Huawei Duo Gone Wrong

Phone duos seem to be a big trend lately, with nearly all mainstream flagships being offered in two models shipping together or arriving at nearly the same period. In some of these cases like with the Galaxy S8 or 2016 Pixels, the differences are small, relegated to the display and battery size. In other cases the changes are a bit larger, like with the 2017 Pixel models, but in these cases the compromises are small enough to be ignored when taking into account that each device targets a different kind of user, particularly due to the differences in form factor. Because the Mate 10 and Mate 10 Pro have a more similar footprint, and are being targeted as a regular and improved variant instead of two sizes for two customers, the compromises in the "Pro" version stand out. Huawei did do a number of things good this year especially in terms of the camera performance, something that I personally thought was good but not great last year. They are also continuing to improve their Kirin SoC and AI offerings and look to really be a formidable foe should they ever decide to start making headway into the US market. Huawei yet again looks to be a strong force in terms of the Android market and being one of the first OEMs to ship Android Oreo on a new phone is something they should be really proud of, especially with such a heavy handed skin, and helps them stand out in a crowded space. It's frustratingly annoying that tje Mate 10 duo is so middling and that some consumers are left with one, less preferable choice between the two.

Don't get me wrong, Huawei has a very good set of phones this year. These phones look to further increase Huawei's growing numbers and put even more pressure on Apple and Samsung, who have to be worrying when and how Huawei will truly break into the very profitable US smartphone market, I just wish they released one fully featured device (a true Pro variant) or followed a more-Google approach, sharing most of the hardware and features with the exception of the size and screen aspect ratio, making choosing the right phone for you even easier. Right now, each phone features an odd set of compromises with the Mate 10 Pro being the most confusing premium variant of a premium flagship in recent memory.


What do you think about the Mate 10 and Mate 10 Pro? Which one would you choose? Let us know!



from xda-developers http://ift.tt/2xwlDO3
via IFTTT

Motorola Releases Kernel Sources for the Moto X4

At XDA-Developers, we put emphasis on kernel sources and especially the GPL that allowed Android to become what it is today. If a manufacturer fails to release kernel sources for a phone, it means that they have violated the GPLv2 license and in turn, violated the spirit of Open Source and the free nature of Android. We have seen many companies and manufacturers not release timely kernel sources, such as Xiaomi, MediaTek and others. It's a practice that goes against what we value as XDA users and Android enthusiasts, and it makes it harder for us to recommend devices from these companies.

If a manufacturer does not release kernel sources for a device, it's guaranteed that development is going to be sub-optimal, to say the least. Users can have things like customized stock ROMs, but a bug-free AOSP ROM is pretty difficult to achieve. Manufacturers modify the Android kernel to tweak device settings, enable or disable features, and so on… so unless the source code of these changes is publicly distributed, the development community for that device is crippled from the very beginning.

XDA has frequently urged them to release kernel sources on time. A manufacturer can release kernel sources for a device, but if that particular device was released a year ago then that is not going to be of much help for users of that phone — besides, the GPLv2 doesn't excuse such incredible delays. That wouldn't provide any impetus for the developer community. It also sours the relationship between the OEM and the Android community.

It is for this reason that timely releases of kernel sources are crucially important. In this regard, Motorola has done a pretty good job with timely releases at times, although they haven't had a spotless record. Most recently, the company, acquired by Lenovo in 2014, released kernel sources for the Moto G5S Plus. Now, they have released the sources for the mid-range Moto X4, a smartphone which fits between the Moto G5S Plus (budget range) and the Moto Z2 Force (which is the Motorola flagship for 2017).

Suggested Reading: US District Court Rules GNU GPL is an Enforceable Contract

This should cover both the stock and the Android One variants of the phone, as they share the same 'Payton' code name. We hope that this leads to an increase in developer interest for this device, as this will benefit users in the long run. We applaud Motorola for the (somewhat) timely release of kernel sources for the device and also hope that this good run of form continues.


Source: Github
Via: Android Police



from xda-developers http://ift.tt/2xyMKbj
via IFTTT

Developers still can’t test HDR+ through the Pixel Visual Core on Android 8.1

Just a few days back, Google released the first developer preview for Android 8.1 Oreo. The update was supposed to enable a hidden SoC on the device called the Pixel Visual Core. Developed in collaboration with Intel, this chip is dedicated exclusively to image processing. In the official blog post announcing Android 8.1 Developer Preview 1, Google stated that developers could test HDR+ processing through the Pixel Visual Core by enabling a new developer option.

Pixel Visual Core on Android 8.1 for the Google Pixel 2

Simple enough for developers to do, right? The only problem is that there is no such developer option available. Users have confirmed this on both the Google Pixel 2 and its larger counterpart the Pixel 2 XL. This video by Ron Amadeo from Ars Technica shows that the "Camera HAL HDR+" developer option is nowhere to be found:

So why is it hidden from the developer options? It appears that Google accidentally left it in as an option that can only be accessible on debug or engineering builds. Oops. Here's the evidence:

We first found the relevant strings related to the Camera HAL HDR+ option in the Settings APK.

  <string name="camera_hal_hdrplus_switch">Camera HAL HDR+</string>  <string name="camera_hal_hdrplus_toast">To apply Camera HAL HDR+ change, reboot device</string>  

Clearly, it's supposed to be a switch that you can toggle. Once you toggle it, you have to reboot for it to take effect. With the help of XDA Recognized Contributor Quinny899, we found the code responsible for this switch. In particular, this is the code that pertains to why this switch is hidden from user builds of the Android 8.1 developer preview:

Pixel Visual Core Camera HAL HDR+

Google Pixel 2 Camera HAL HDR+ Pixel Visual Core

There are multiple checks in place here before the camera HAL HDR+ option can be enabled. First, it checks against a boolean value called "config_show_camera_hal_hdrplus" which is true by default on the Pixel 2 devices (thus making it fail the first conditional). Then, it checks against a system property called "ro.build.type" and if it does not match "userdebug" or "eng" (strings for debugging or engineering builds) then the Camera HAL HDR+ won't be enabled. Finally, there's also a property value called "persist.camera.hdrplus.enable" which can be set to true to forcefully enable the option, however, there's no way to set this value unless your device is rooted (and there's no root available for the Pixel 2/2 XL yet).

Current user builds of Android 8.1 on the Pixel 2 and Pixel 2 XL fail these checks. That means there is currently no way for developers to actually test HDR+ processing through the Pixel Visual Core, as Google stated in its Android 8.1 release post. This was likely just a mistake from Google, and all it would take is an OTA or new factory images to fix.



from xda-developers http://ift.tt/2gTdUXo
via IFTTT

Saturday, October 28, 2017

Google Pixel 2 has a Hidden Easter Egg in Active Edge Settings

Google's latest flagship Pixel smartphones, the Pixel 2 and Pixel 2 XL, initially launched with Android 8.0 Oreo on board but have since received a developer preview of Android 8.1. There's a lot of subtle changes that we've documented in the release, but some changes are more hidden than others. One change we've uncovered isn't what you would really call a feature, but it's consistent with Google's habit of adding some hidden humor to Android. In the Active Edge settings screen of the Google Pixel 2 and Pixel 2 XL running Android 8.1 Developer Preview 1, there's a hidden Easter egg mini game that involves you squeezing your phone to pop bubbles.

For those of you who aren't familiar, the Pixel 2 smartphones have a feature called Active Edge that lets you squeeze the bottom half of your phone's sides to either launch Google Assistant or silence incoming calls. You can adjust the squeeze sensitivity in settings (or fine tune it with an ADB command) but apart from that there's not much in the way of customizing Active Edge, at least officially.

When we started digging into the latest Settings application on the Google Pixel 2 XL running Android 8.1, we discovered a new line related to Active Edge that we thought may be interesting. First, we discovered a new activity in Settings called "AssistGestureBubbleActivity."

  <activity android:enabled="true" android:exported="false" android:hardwareAccelerated="true" android:name="com.google.android.settings.gestures.assist.bubble.AssistGestureBubbleActivity" android:resizeableActivity="false" android:screenOrientation="portrait" android:theme="@android:style/Theme.Material"/>  

Next, we discovered a corresponding layout file for this activity:

assist_gesture_bubble_activity.xml

  <?xml version="1.0" encoding="utf-8"?>  <FrameLayout n1:layout_width="fill_parent" n1:layout_height="fill_parent"  xmlns:n1="http://ift.tt/nIICcg">  <ImageView n1:id="@id/game_view" n1:layout_width="fill_parent" n1:layout_height="fill_parent" />  <ImageView n1:id="@id/play_view" n1:layout_width="fill_parent" n1:layout_height="fill_parent" />  <TextView n1:textColor="#ffffffff" n1:gravity="end" n1:layout_gravity="top" n1:id="@id/current_score" n1:padding="12.0dip" n1:layout_width="fill_parent" n1:layout_height="wrap_content" />  </FrameLayout>  

The keywords "game_view" and "play_view" hinted at this being an easter egg of some sort. Since the activity is defined as "unexported" that means it can't be run from the command line without root, nor can it be seen from an activity launcher.

But with help from XDA Recognized Contributor Quinny899, we found out how to access this hidden easter egg. He discovered the following code:Google Pixel 2 Active Edge Easter Egg

Basically, this code is listening for repeated taps on the squeeze sensitivity setting under Active Edge settings. If the user doesn't have easter eggs disabled (via a managed profile), then the phone will launch a hidden mini game where you squeeze your phone to pop bubbles on screen.

The above video was taken by XDA Junior Member InFlames03 on their Pixel 2 XL running Android 8.1 Oreo. If you're wondering how their settings app is dark, that's because they're running the rootless Substratum theme engine with their own dark theme called Sai's Oreo Theme (which can you find out how to install here.)

I personally think the Easter egg is a bit underwhelming. Quinny899 described it as an "engineering test recycled into a game." To be fair, not every Easter egg can stack up to Android Marshmallow's FlappyDroid, but it's not like you'll be playing this game for more than a few seconds anyways.



from xda-developers http://ift.tt/2iG6oPV
via IFTTT

Android Pay Tests Notifications for All Credit Card Purchases

Android Pay, Google's contactless payment method, allows for ease of purchase of many goods and services in many countries across the world and in partnership with thousands of banks. Google offers a similar service in the form of Tez in India, and there are other contactless payment providers in various different countries. Now Google is looking to enhance their Android Pay service once more by testing notifications for all credit card purchases.

If you've ever bought anything with PayPal while the PayPal app is installed on your device, you'll know that when you purchase an item through your PayPal account that you will receive a notification saying that you paid a certain amount to whatever company it was. It's a security feature and also a pretty neat way to tell how much you paid when you purchase things in other currencies, as it will also convert it to your local currency. This is by and large a security feature, however, and Google will now be implementing it too, along with a little extra.

android pay notifications android pay notifications

Images credit: @shiruken

As can be seen in the screenshots above, not only are there some notification configurations for your purchases, but Android Pay actually shows you non-Android Pay transactions depending on the bank that you're with. This allows you to keep track of your transactions easily, and manage purchases too within the same app as you presumably may use the service when out and about. As you can see, there are quite a lot of options including loyalty and gift card notifications too, and a notification telling you that you're actually near an Android Pay supporting store! All of this should help you stay aware of how much you're spending, and keep track of how that money is being spent. It can also help you spot suspicious activity should someone get access to your credit card details. This feature does not seem to be out for everyone yet, but hopefully it'll make its way to your device soon!


Source: @shiruken



from xda-developers http://ift.tt/2gTdsZ0
via IFTTT

Chrome 63 Beta Released with Changes to Chrome Home, a New Flags Page and More

A week after the release of the stable version of Chrome 62, Google has now released Chrome 63 beta, which comes with many developer-focused changes and some user-facing UI changes. The developer-focused changes include dynamic module imports, async iterators and generators, and a Device Memory API which enables developers to see the total RAM of a user's device and tailor web content in accordance with hardware limitations.

There are also user-facing changes in this beta release. In Chrome for Android, the permission UI has been changed. Up till now, permission requests for special permissions have appeared in Chrome for Android as banners which can be dismissed at the bottom of the screen. According to Google, developers often show them without considering whether the user has the appropriate context to grant the permission. This results in "a distracting user experience, and users ignore or temporarily dismiss these permission prompts more than 90% of the time."

Google stated that in Chrome 59, it had started to address this problem by temporarily blocking a permission if the user dismisses the request three times. Now, in Chrome 63, permission requests will be presented as modal dialogs which cannot be ignored.

Chrome 63 Permisssions Dialog

The new permissions dialog on Chrome 63 (credit: credit: 9to5Google)

According to the company, this change reduces the overall number of permission prompts by 50%. It also makes users "5 times more likely to accept or deny requests, rather than temporarily dismissing or repeatedly ignoring them." To ensure users understand the permission request, Google says developers should present users with permission requests at an appropriate time, as it has found that users were 2.5 times more likely to grant permission to a site that asks for permissions with context.

Moving on, Chrome 63 includes changes to Chrome Home – Google's term for Chrome's new bottom address bar design, which Google has been developing for a while now. Google has continued to develop Chrome Home with a new Modern UI, which gave rounded corners to the address bar and other elements.

The modern UI for Chrome Home was released in Chrome 62, but it wasn't enabled by default as Chrome Home itself still isn't enabled by default. However, Android Police discovered some new flags in Chrome 63 that indicate the feature is nearly completed..

Chrome Home UI

The Welcome screen of the new Chrome Home UI (credit: Android Police)

There is also a new "You're using the new Chrome" message at the top of the overflow menu that opens a popup describing the new features, as well as a toggle to disable it.

Chrome 63 beta has a new design for the chrome://flags page. The Android version of the page doesn't look like the desktop version any longer, with larger touch targets, more white space, and a search feature, which should eliminate the necessity to use 'Find in Page' for flags.

Chrome 63 Flags

The new flags page in Chome 63 (credit: 9to5Google)

Acccording to 9to5Google, Chrome 63 is also adding site-wide audio muting with an option to mute audio for individual sites. This will be accessible in site settings; users can also choose 'Allow' or 'Block' by opening the permissions panel when tapping the green lock button. Finally, the new 'display: minimal-ui' capability will allow developers to build minimal UIs that lack action bars and other interface elements, much like Chrome Custom Tabs for Android.

Chrome 63 will arrive in the stable channel in the coming weeks.


Source: Chromium
Via: Android Police
Via: 9to5Google



from xda-developers http://ift.tt/2zUyn2F
via IFTTT

The Robin Egg Blue Honor 9 Premium is a Limited Edition Device Colour [XDA TV Interview]

If you've been paying attention to our news feed, XDA recently attended Droidcon UK 2017, where we interviewed many awesome people, including Wilkin Lee from Honor. We got to show off the "robin egg blue" model of the Honor 9 Premium, and we learned something new about the device. This variant is actually a limited edition and will likely go away at some point. "It's going to be super limited," Wilkin said in an interview with XDA, adding that it's aimed at Honor's "hardcore fans".

If you aren't familiar with the Honor 9, you can check out our overview of some of its best features! With lots to offer, this is a really great showing from the Huawei subsidiary The robin egg blue edition looks beautiful in real life, featuring a full body of glass and a unique colour that hasn't been tried by other flagship devices in the same kind of price range. The hue of blue employed here is very similar to Honor's trademark blue hue, which is used in the company logo and throughout their marketing materials. The Honor 9 may take a while to reach the USA, just like previous devices.Whether the robin egg blue device will make an appearance in the US is currently unknown though. We'll see if we can get any more information on this colour's exclusivity.

If the device's limited edition run ends and we are left with the other colours, you can still opt for gold, silver and black which should cover the majority of phone colour interests for everyone. What may prove to be a problem is the fact that in the UK, you can only buy the silver or regular blue edition. This does leave the users with less choices, but in the future Honor may release other colours.

For more Droidcon UK coverage, check out our summaries (part one and two) as well as the many interviews hitting XDA TV!


 



from xda-developers http://ift.tt/2hhP543
via IFTTT