LightBlog

jeudi 1 décembre 2016

OP3 Nougat Beta Impressions: OnePlus Scales Back to Stock Android for a Sweet Breath of OxygenOS

When I first reviewed the OnePlus 3, I had plenty of positives to sing about the device's software UI and the resulting user experience. OnePlus had accomplished a truly-lightweight ROM that enhanced the UI in meaningful ways, while leaving the core of Android alone.

This was one of my favorite parts of OxygenOS, and the user experience for OnePlus 3 users running stable builds hasn't changed much in this regard. The software package is smooth and offers few compromises as well as a healthy amount of customization; it feels thought-out and reserved in a comfortable way. But things change in the realm of software and companies try new things – which we should encourage, with proper feedback – which led to the creation of OnePlus' "community builds" (essentially a beta program), where the company was free to experiment with the device's software without impacting the UX of those that liked that original OxygenOS experience. OnePlus has turned its track record around when it comes to updates starting with the OnePlus 3, and they have been listening closely to feedback — so it was a surprise when users found that the community builds actually changed much of the original OxygenOS, and not always for the better.

While the OnePlus 3's software was almost invariably praised by reviews and users alike, some internal changes meant that the software development model that created OxygenOS had to be reformed. Essentially, OnePlus realized it was impractical to keep two separate software development teams working on two disparate ROMs – Oxygen and Hydrogen – so the company decided to merge these teams and unify the underlying framework to consolidate the experience and provide faster software updates. We have written about the perceptible increase in support with this new device, but the early community builds showed a drastic change in the user interface and the introduction of a slightly-altered design language (incorporating more transparencies, blurs, etc). HydrogenOS itself was admittedly very different, and we did see some influences like those seen in Chinese ROMs in the community builds. Proportion changed, accent colors were altered, and the UI tried to imitate Nougat in some places like the notification shade. This software eventually made it to the OnePlus 3T as the main firmware.

A Taste of Nougat

Yesterday we saw the release of the Nougat Open Beta 8 for the OnePlus 3, meaning users finally got to try out the OxygenOS vision for Android 7.0 (and not 7.1). When I personally saw the forum announcement, my immediate doubt was whether the OnePlus 3 would leave Stock Nougat alone – an update which I consider the best refinement yet – or if the community builds' design language would make its way to the beta. Luckily, my concerns were quickly eased and the Nougat Beta 8 actually has a very tasteful implementation of Nougat, and certainly better than the OxygenOS found in the OnePlus 3T in my opinion.

OP3T OP3 (MM) OP3T OP3 (MM) OP3T OP3 (MM) OP3T OP3 (MM) OP3T OP3 (MM) OP3T OP3 (MM)

Above you can see a gallery comparing some basic elements of the old Oxygen OS and the OP3T's version, and below you can compare the latter with the Nougat build. As you can see, the proportions are different almost everywhere, given the OnePlus 3T's firmware had a rather shoddy imitation of Nougat elements. Much of what makes Nougat great is left untouched, although there are some noticeable changes here and there, namely in the accent color and theme options. But the default theme's accent changes are pretty pleasing, I think, and the blue motif reminds me of the Pixel XL's UI more than the OxygenOS I grew used to. With the light and dark themes, you can still change the accent (the color options are fine) but I still wish OnePlus would let us customize that while using the default theme, and that they'd let us choose the green accent of Stock Android as well.

OP3T OP3 (Nougat) OP3T OP3 (Nougat) OP3T OP3 (Nougat) OP3T OP3 (Nougat)

The user experience of the Nougat beta is also quite satisfactory in general, I found. First, though, let's take the bugs and inconsistencies I've experienced out of the way. The setup process was abnormally laggy, but the device settled in after a while; however, I ran into a black screen crash not even an hour in, and a few hours later I also experienced a full device freeze. Since then, though, I haven't had any instability issues. There are also some software oversights, such as the Nougat settings sidemenu not being properly theme on the System UI tuner (interestingly enough, it becomes stock-ish green), and the software keys can initiate multi-window (recents longpress) but the software keys cannot — and there is no option in the keys customization to allow for it yet. I've also seen more launcher redraws than I'd like, and while not a bug, I wish the volume bar behavior would allow me to set "vibrate" by turning the volume all the way down. Mind you, these are only a few clear issues out of many, many bugs that people have encountered, and your mileage might vary.

"[Beta 8] feels like the good old OxygenOS philosophy but on a Nougat base, and that's just what OxygenOS needed"

I expected these kinds of issues given that this is a beta, after all — in fact, some of those problems were present in early CM14 builds as well. Moving onto the good, though, OxygenOS running on top of Android Nougat is very well-executed: OnePlus brought all of the best features over, including the app locker and the new gestures, while still keeping everything that's new tidy and unobtrusive.

And this is perhaps the best part of the experience: this feels like the good old OxygenOS philosophy but on a Nougat base, nothing less and nothing more, and that is just what OxygenOS needed. Many features from Android Nougat further enhance the OnePlus 3's user experience and general philosophy, too. For example, multi-window is arguably an enthusiast feature, and at the very least it's something Android enthusiasts have wanted implemented on Stock Android for quite a while. The OnePlus 3 is an enthusiast device if there ever was one, so it's great to finally see the feature implemented on OxygenOS. Furthermore, the fact that the OnePlus 3 has the option for capacitive keys means that multi-window is further enhanced by maximizing the amount of screen available for the two applications.

Beta 8 effortlessly merges the best of Android Nougat with Oxygen features

screenshot_20161201-123539And this is made even better with the inclusion of DPI scaling courtesy of 7.0 — regular OxygenOS had to have its DPI adjusted through adb or build.prop edits, and this would often result in some UI elements not being scaled properly or outright breaking. To the side you can find an example of the OnePlus 3T's toggles becoming left-biased under a non-stock, manually-adjusted DPI.

The better notifications, cleaner toggles, and other Nougat additions are the icing on top. It's also fair to recognize that OnePlus had made it a staple of its software model to implement upcoming features on current software; the OnePlus 2, for example, had permission controls and other Marshmallow features, and the OnePlus 3 also touted some functional improvements like a reworked Doze mode. But if I must be frank, I am glad that such features eventually get replaced by the proper Android implementation. Ultimately, OxygenOS Beta 8 feels very effortless in its merger of Nougat and Oxygen features.


I've only had 24 hours with the new beta build, so I can't comment on battery life yet. Performance, too, would take a while to analyze, but do know that the touch firmware is the same as the OP3T's (thanks to u/JakeChambersOy for letting me know). A OnePlus representative also told me they have been looking into improving touch latency before the controversy broke loose, which is reassuring if true. So far, though, the experience has been fast and smooth, and it's worth noting that clean flashing it, or if wiping after, will grant you the F2FS improvements we took a look at yesterday.

There will be bugs, and rolling back to Marshmallow is not straightforward

Overall, this is a solid beta for what looks to be a very solid future update. I can't quite say it's daily driver material given I have experienced a couple of crashes and annoying bugs, but I do think it's something worth trying… However, rolling back to Marshmallow is not a straight-forward process at the moment and it involves flashing a custom build of Android Marshmallow, which you have to request by contacting customer support. Before flashing the build, do read a guide and people's opinions on the forums and check out the bugs and feedback that the community is offering.

It's comforting to know that many of the community build's UI modifications are being rolled back in favor of Nougat's aesthetics, but it does make me wonder why they went through that trouble if that UI only saw official stable debut on the OnePlus 3T. Perhaps it's because we've heard that the OnePlus 3T won't receive its Nougat beta until after the OnePlus 3's testing period is done, but in the end and like we originally stated, OnePlus 3 owners get to experience the OxygenOS Nougat builds before those getting the upgraded hardware. I just hope that there is no bait and switch with these beta builds, and that the refined user experience that we see is what we ultimately get, only with the extra polish it deserves.

Check Out XDA's OnePlus 3 Forum >>



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

Sony begins Nougat roll-out for Xperia XZ and X Performance while Huawei unveils their update plans

While Google Nexus and Pixel owners have been relishing in sweet Nougat-y goodness for the past few months, most users on other smartphones have been patiently – and eagerly – awaiting the promised Android 7.0 Nougat update for their device.

Some companies pounced on the initial Nougat hype and rushed out of the gate with announcements for which devices they will be bringing up to date. Sony, for instance, announced their Nougat plans back in August. The company promised support for the following 11 devices:

A little over 3 months after the announcement, Sony is finally delivering on its promise. The company has just announced its Android 7.0 Nougat update for the Xperia XZ and Xperia X Performance. Rolling out to these two devices starting today, the Nougat update will bring support for Android's Multi-Window, better battery life thanks to an improved doze mode, manual camera settings for the X Performance, and a Google Now-integrated launcher.


Huawei's Plans for Android Nougat

Not one to be left out of the update game, Huawei has also unwrapped their plans for several of their flagship devices. Android 7.0 Nougat will roll out to Huawei devices with EMUI 5.0 on board sometime during Q1 2017. The company has promised to bring Android Nougat to the following devices:

The update will first roll out to the Huawei Mate 8 and Huawei P9, followed by other devices. Unlike the Nougat update for other OEMs, such as the recent OnePlus 3 Nougat update with OxygenOS, we already have a fairly good idea of what the Nougat update for Huawei devices will entail. Nougat for the Mate 8 has previously leaked, official beta testing has begun on the Honor 8, and our upcoming month-long Huawei Mate 9 review should paint a pretty good picture of what you can expect for the EMUI v5 software experience.


Source: Sony

Source: GSMArena



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

Meizu Officially Announces the Pro 6 Plus and M3X running on Flyme 6

Chinese Android smartphone manufacturer Meizu has had a rather busy week, to say the least.

The company just announced two new smartphones, a big update to their OEM skin, and their plans for which devices will be getting the Flyme 6 update. We've heard whispers about the existence of the following two smartphones for quite some time, but Meizu has finally made it official. The Meizu Pro 6 Plus and the Meizu M3X will be joining the Meizu line-up as the first two devices running on Flyme OS version 6.

The Meizu Pro 6 Plus has a metal unibody build with the Samsung Exynos 8890 SoC. For reference, this is the same chip found in the Exynos variant of the Samsung Galaxy S7 and Galaxy S7 Edge. The Pro 6 Plus will ship in two variants – a 64GB storage model with an underclocked CPU and a 128GB storage model clocked a little higher. Both variants will sport 4GBs of RAM, a 5.7″ Super AMOLED 1440p display, a 5MP, f/2.0 front camera, a 12MP 1/2.9" Sony IMX386 Exmor RS sensor with 1.25µm f/2.0 rear camera, and a 3,400mAh capacity battery.

The Meizu M3X is a mid-range device with its MediaTek Helio P20 SoC, a 5.5″ 1080p Sharp TDDI LCD display with "2.5D" curved glass, a 5MP front-facing camera, a 12MP 1.25 μm f/2.0 Sony camera on the rear, 3GBs of RAM, 32GBs of internal storage, and a 3,200mAh capacity battery.

Both the Pro 6 Plus and the M3X will feature the company's updated mTouch 2.1 fingerprint scanner along with their mCharge fast charging technology that promises to charge 40% in 30 minutes thanks to its 18W charger. In addition, both of these new smartphones will be running on Meizu's latest Flyme OS version 6 OEM skin that is built on top of Android 6.0 Marshmallow. Meizu has also announced their plans for which devices will receive the Flyme 6 update. So if you have any of the following, you should look forward to an OTA update over the coming months

Source 1: AnandTech Source 2: FoneArena

Source 3: @MEIZU



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

Google Pixel Owners Report Another Issue with the Camera

Although many have praised the camera prowess on the new Google Pixel and Pixel XL, some owners haven't had the best of luck with their photo-taking experience.

The camera has been a major selling point for the Google Pixel phones. Google has been touting the DxOMark camera rating in its marketing materials before the phones were even launched. Many Android smartphone publications, including our own, have lavished praise on the camera performance of the two Google Pixel devices. Sadly, some users have been having quite different experiences.

Right around launch, we started to see reports from users experiencing a mysterious lens flare/halo effect appearing in their photos. This lens flare/halo effect isn't present in all photos and seemingly depends entirely on what the user is taking a picture of. Google has already acknowledged this issue's existence and said they would work on a software update to eliminate the lens flare issue.

But, this lens flare isn't the only issue users have been reporting with the camera experience on the Google Pixel/Pixel XL. Users posting on the Google's Pixel User Community have been reporting a strange issue involving the viewfinder of the camera application itself. Seemingly at random times, people are seeing strange pink and purple lines appearing within the app's viewfinder. Furthermore, taking a photo will result in the camera capturing these pink and purple lines in the photo itself, which means the issue may go beyond a bug within the Google Camera app itself.

This issue was first reported towards the end of October, and throughout all of November more and more reports have been flooding in from users within the Pixel User Community saying they are experiencing the same issue. Many have speculated the cause behind this strange bug, but an explanation has yet to confirm the true source. Fortunately, Google has responded to the thread with assurances that they are aware of and are actively investigating the issue. The company has marked the bug as a high priority and will report back in the future with further details.

Source: Google Product Forums



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

MediaTek Announces the Helio X23 and Helio X27

After unveiling their flagship SoC, the 10nm-based Helio X30, earlier in September, MediaTek has announced two other upgrades in the Helio family: the MediaTek Helio X23 and the MediaTek Helio X27. The new Helio SoCs upgrade the overall performance, camera quality and power consumption of the SoC family.

The aim here is to improve the user experience along with offering a range of performance options for OEMs for their product differentiation needs.
Both the MediatTek Helio X23 and the X27 continue along MediaTek's Tri-Cluster Deca-Core architecture on a 20nm process, with cluster setups of 2x Cortex-A72 + 4x Cortex-A53 + 4x Cortex-A53, which is similar to the previously released Helio X20 and X25. The differences manifest themselves in the various clock speeds of the clusters, the clock speeds of the GPU and the presence of what MediaTek is calling "EnergySmart Screen" feature.

As the number would imply, the X27 takes over the X25 as the currently highest-end SoC in the X20 Series, while the X23 offers an improvement over the X20 in clock speeds. Further, the Helio X27 also leads the pack in the GPU, with a slight increase in speed of the Mali-T880 MP4 from 850MHz in the X25 to 875MHz. The table below better encapsulates the differences in the SoCs:

MediaTek Helio X27, MediaTek Helio X23

MediaTek is claiming best in-class performance and power consumption with the new SoCs, with overall processing improvement of more than 20% and "significant" increases in Web browsing and application launching speeds. The SoCs also support dual camera photography with MediaTek's upgraded Imagiq ISP (Image Signal-Processing) solution, which MediaTek claims is the first ISP to integrate color and mono cameras and depth-of-field applications into a single ISP.

With regards to MiraVision EnergySmart Screen technology, this is a power-saving tech which modifies the display parameters based on the on-screen content and ambient lighting, claiming up to 25% reduction in display power consumption while maintaining the best visual experience possible. It will be interesting to see this technology in practice through competent OEMs on good displays and experience the quality tradeoff (or as MediaTek claims, the lack of tradeoff).

The press release provided by MediaTek does not mention any timeline for the SoCs, but assures that smartphones powered by these new SoCs will be available soon.

What are your thoughts on the newest additions to the X20 series? Let us know in the comments below!



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

Netflix Brings Offline Downloads for Mobile Devices

For years, fans of the most popular video streaming service, Netflix, have been clamoring for offline playback support.

We've seen this feature included with competitor services such as Amazon Prime Video for well over a year now. Even other competitors like Starz and now YouTube Red offer the ability to download video content onto a mobile device so users can play their favorite media back at a later time when they are without Internet access. Netflix resisted this trend initially, but eventually caved and recognized that users in many parts of the world simply do not have access to the Internet everywhere they go. Thus, the company launched an offline playback feature – but only for select markets. Yesterday though, Netflix officially launched its offline viewing feature worldwide for Android and iOS smartphones and tablets.

For iOS users, you must be running version 8.0 or higher whereas Android users will need to be on Android 4.4.2 KitKat or higher. As long as you're on a compatible version of Android or iOS and have updated to the latest version of the Netflix application, you can download select TV shows and movies for offline playback. You'll simply need to look for the download button located on the details page of a TV show or movie.

At this time, unfortunately, not every title on the service supports offline playback. Although more movies and TV shows are promised to support offline playback in the future, right now we're told you can download many of the most popular shows such as Orange Is the New Black, Narcos, House of Cards, Stranger Things, Unbreakable Kimmy Schmidt, Master of None, and The Crown right now. Next Wednesday, other titles like Breaking Bad, Supernatural, The Office, The Flash, Minions, Kung Fu Panda 3, and Home will be made available, with more to presumably follow.

Source: Netflix Media Center



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

Fitbit Reportedly Buying Pebble For $40 Million

Fitness wearables and smartwatches share a lot of their use cases, to the point where one encompasses the other. Most smartwatches come with fitness tracking as one of their features, and a few fitness wearables also seek to integrate smart services into their functionality. The end result is that both of these categories end up competing for the same spot on your wrist, and some might not survive the competition.

You might have heard of Pebble before. Pebble is one of the most influential campaigns on Kickstarter, with the original Pebble campaign taking over $10 Million in funding for its $100,000 goal, the Pebble Time getting over $20 Million for its $500,000 goal, and the Pebble 2 campaign getting over $12 Million in funding for its $1 Million goal. With all of this money pouring in, one might get the impression that all was smooth sailing. But the picture was not as rosy, as Pebble had to lay off around 25% of its employees in March this year. The company also had to resort to debt funding and loans, according to Techcrunch.

Amidst all of these tough decisions, new reports coming in from The Information [subscription needed] and confirmed by Techcrunch, point that wearable giant Fitbit is nearing a deal to purchase Pebble. The Information mentions that the acquisition involves a "small amount", but Techcrunch goes on to mention a sum between $34 and $40 Million for Pebble, "barely covering their debts". The acquisition deal will see Pebble and its products closed down over time, with Fitbit acquiing the compny's assets including intellectual property and software.

This deal is not the first one that Pebble received. Watch maker Citizen expressed interest in purchasing Pebble for $740 Million in 2015, while Intel made an offer of $70 Million before the launch of Pebble 2. Pebble's CEO turned down both offers.

Spokesperson from Fitbit declined to comment on rumors and speculation, while Pebble is yet to respond to the request to comment from Techcrunch.

What are your thoughts on this acquisition deal? Let us know in the comments below!



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