Tuesday, July 4, 2017

What’s Your Favorite Trend or Feature from 2017 Smartphones?

We've already seen a substantial chunk of what 2017 has to offer, and with a new year and new smartphone generations came a bunch of new trends, features, design elements and general advancements. While the core Android experience remains as strong as it was in 2016, manufacturers and Google are toying with some interesting ideas.

Bezel-less displays, squeezing features, additional screens, more dual camera setups, an emphasis on voice assistants, yet more modularity though more Moto releases and Essential, under-display fingerprint scanners (coming soon!), new screen aspect ratios — there are tons of new trends and older but recent features are also being revitalized. So we ask you,

What is your favorite trend or feature that you've seen in 2017 smartphones? How has this year been so far in terms of innovation and new, useful functionality? What features or trends make you consider upgrading from an older device?

Sound off in the comments below and join the discussion!



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

Evan Blass Leaks Device Render and Specifications of Lenovo’s Moto X4

The Moto X4 is reportedly on track to become the first non-Google handset which will work on Google's Project Fi MVNO, as reported last week. And now we have a good idea on what the next mid ranger from Lenovo under the Moto X lineup would be like, thanks to a report by Evan 'evleaks' Blass on VentureBeat.

Evan mentions that previously revealed details of the Moto X4 through unverified sources have inaccuracies in them. Evan's source for the leaks is a person with knowledge of Lenovo's plans, and evleaks' track record of leaks under his own name speaks for itself.

The Moto X4 will reportedly follow the now-typical Moto X tradition, clubbing mid-range-ish specifications with an affordable price tag yet still managing to deliver strong performance. The device will likely feature a 5.2″ FHD display, which will put it in a good spot for people looking for a more pocketable smartphone. The Moto X4 will be powered by a Qualcomm Snapdragon 630 SoC, with all eight cores clocked at 2.2GHz. The topmost storage variant will feature 4GB of RAM and 64GB of internal storage, along with microSD expandability. For its screen size, the 3,000 mAh battery should also keep most buyers content.

The Moto X4 is also said to feature a dual rear camera setup, featuring an 8MP and a 12MP camera at the back. The front camera will be a 16MP shooter for selfies. Additionally, the device will feature IP68 water and dust resistance, and will come with Android 7.1 Nougat out of the box. The fingerprint sensor on the front of the device will also be capable of recognizing simple gestures for UI navigation. The device render also incorporates what appears to be a headphone jack on the bottom left of the device.

The Moto X4 will likely make its debut in the fourth quarter of this year, right in time for the holiday shopping season. If the device stays true to the Moto X tradition, Lenovo could have a hit in their hands.


What are your thoughts on the leaked specifications of the Moto X4? Let us know in the comments below!

Source 1: VentureBeat Source 2: Twitter – Evleaks



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

Android Wear 2.0 Expected to Arrive for ZenWatch 3 This Month; ZenWatch 2 OTA Coming Next Month

Google dropped Android Wear 2.0 back in February along with two new smartwatches, the LG Watch Style and Watch Sport. At the time, Google promised that the new update would soon start rolling out to all supported hardware. Not only that, it even released a list of compatible smartwatches that would be receiving the jump to Wear 2.0. However, it was not until April that Google and OEMs finally started rolling out the new update to some of the supported devices.

While most of the supported watches have already received Android Wear 2.0 a while back, there are still some devices that have yet to get the taste of Android Wear 2.0.

The list of smartwatches that are still waiting for the Android Wear 2.0 update includes ASUS ZenWatch 3, ZenWatch 2 and Moto 360 Sport. Speaking of ZenWatch 3 & 2, the initial timeframe given by ASUS for the Wear 2.0 update was "early Q2" but it failed to deliver on the promise.

While the owners of these watches would certainly be frustrated due to the delayed rollout, it appears the wait for the update is finally going to be over — that is, unless the update gets delayed yet again.

According to details shared by official ASUS Germany Twitter account, Android Wear 2.0 for the ZenWatch 3 is currently under final software testing and should soon be rolling out to the device.

When asked about when the ZenWatch 2 will get this update, ASUS replied that the watch (WI501Q) would receive the Wear 2.0 update this month while the 1.46″ model (WI502Q) can expect the new update in August.

As for exactly when this rollout will begin, according to the ASUS Germany ZenWatch support page, the Wear 2.0 will start rolling out to the ZenWatch 3 starting July 4th.

It remains to be seen whether ASUS will be able to deliver on the timeline this time around, the OTA has certainly failed multiple "deadlines" blurted out by ASUS support accounts and users are becoming increasingly frustrated. The ZenWatch 3 was specifically marketed as a higher-end yet affordable Wear watch, and we found it quite satisfactory in our review. In any case, if you are carrying a supported ZenWatch watch, keep an eye out for the Wear 2.0 update in the coming weeks.


Source [1]: Android Police Source [2]: Reddit



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

Lead Developer of Xperia Open Source Project (XOSP) Will Cease Development

The lead developer for XOSP, XDA Recognized Developer nilac considered, had starting work on XOSP based on Android O earlier this month. However, due to certain major concerns the developer had, he made the decision to stop any development garnered towards XOSP.

XOSPApps

The XOSPApps package can easily be installed on any device regardless of the ROM the device is running. Considering this, the developer stated that XOSP wouldn't bring anything "new" and " unique" to the table when such package already provided a significant chunk of the experience.

Xperia UI

The developer is under the impression that the experience a user has while using and browsing through the applications while running XOSP can easily be re-created onto other devices with the help of tools like substratum. The lead developer had always been reluctant when questions regarding  a lack of substratum's integration into the ROM had to be answered. Spending a fair amount of time individually theming most of the XOSPApps, the reluctance was but natural.

The users

Calin Neamtu states that many users aren't as happy with XOSP as they once were, due to the fact that they now have options to have ROMs supporting themes to a much greater extent. The developer states that the users regard the Xperia experience, the UI and the exclusive package of the applications as nothing extraordinary. The lead developer quite recently published a statement onto the official Telegram channel for XOSP, which you can find below.

Full Statement

"4 Years Ago a ROM was born and that was the S+ Reborn, it was only built for the Samsung Galaxy S+ at that time but it gained a very good success and [was] afterwards ported on other devices as well.

It was that time when XOSP was born. The aim of the ROM was to [achieve] a very close Xperia feeling to the Original one by including UI elements and the most famous Xperia Apps.

I don't know if anyone of you tried porting an Xperia app in the years when we were in the Jelly Bean era but it was much more difficult to get it work on a different phone than an Xperia one.

By now almost everyone is able with some tricks to make them work cause eventually what you need are just some frameworks and the relative XML permissions.

Users nowadays are looking [for] much more in ROMs, having themes support and as many features as possible and unfortunately that's where also some developers from other ROMs are doing wrong.

You don't need to pump the ROM with as many features as possible if they're not needed. And never listen to the users because the users will only want what another ROM has and that's just makes your ROM the same as an another one.

Don't make the terrible mistake to create a ROM and then maintaining it by only picking stuff what the other ROMs got, just pick [a new feature] essentially if you need something but never too much.

XOSP fulfilled all the primary goals and even mine as well, and I will never be sad of thinking to the past of this awesome project which gave so much satisfaction to the users and great reviews.

This also gave me a certain popularity among the other great and much talented Developers, plus all the Android stuff that I learned by working on this ROM.

So with very much disappointing and pain, XOSP will never get the Android O.

I've been thinking on this very much, some of you may be knowing that I was looking for developers to join the team but that didn't go so well, but apart that there's also the whole thing about the [userbase] and what Sony is also doing because in the last years I don't know why but Sony appears to be decided to continue on a more and more AOSPish interface leaving XOSP with pretty much a simple UI which can be archived with a simple Substratum theme.

XOSP brought up a very different style in comparison to many ROMs but not just by the UI but also by the way of doing things.

Maybe I wasn't luck enough to find some more people for the development but this time I think the users decided to go with the other ROMs.

For all those who are sad or maybe disappointed by this decision don't even think that I am fine with this cause I am not.

I'll continue to work on my own just not on XOSP and maybe I'll find a new home if someone needs a dedicated person in the team.

I really doubt someone will ever continue something on XOSP cause if I didn't find enough people to give a hand with the development it's highly improbable that someone will continue from state where I'll leave the ROM in September cause support for Nougat will be continued until September, after that no more builds will be done.

Sorry guys but I just feel this is the right way to end this, I kept the development [alive] as much as I could but this cannot be maintained anymore." — Nilac


Have you ever tried XOSP? Let us know about your experience in the comments.



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

Monday, July 3, 2017

Meizu Pro 7 Live Image Leaks Point Towards a Secondary Color Display on the Back

The mobile market sees cutthroat competition from all quarters, making it difficult for OEMs to stand above the crowd. There's only so much differentiation one can bring to a phone's design, so these OEMs have to explore unconventional features and sometimes quirky gimmicks to get their phones noticed.

Meizu will reportedly be doing something similar with its next set of devices in the "Pro" lineup. The Meizu Pro 7 and the Meizu Pro 7 Plus will reportedly feature not only a dual rear camera setup, but also a secondary color display on the back of the device.

The small secondary display will be housed below the dual rear camera. At first, leaks pointed that this display could be an e-ink display very much like the Yotaphone, just smaller. But new leaks of the device showcase color display functionality which would not be possible with an e-ink display.

One of the leaks pictures the secondary display displaying a full copy of the front display, while another shows the device running a Pac Man game on the back. Rumors point that the display technology on the secondary display would be LCD and not AMOLED, though we will have to wait on the official launch to state the same with complete confidence. An upgrade from e-ink to LCD would enhance the usefulness of the display, but this would presumably come at the cost of precious battery life.

As far as specifications are concerned, the Meizu Pro 7 will likely sport a 5.2″ FHD display while the Plus variant will go for 5.5″ or even higher. Leaks point to a MediaTek Helio X30 powering the brains of the devices. The rear cameras are rumored to be 12MP sensors, Sony IMX386 and Sony IMX286. The front camera will be a 16MP shooter.

Pricing on the base variant of the Meizu Pro 7 is expected around CNY 2,799 ($412) and is expected to go as high as CNY 3,299 ($486) for the topmost variants. On the other hand, the Meizu Pro 7 Plus is expected to range between CNY 3,299 ($486) to CNY 3,799 ($560).


What are your thoughts on such secondary color display setup? Would this be a defining feature of the device, or will it be just another fancy gimmick? Let us know your thoughts in the comments below!

Source 1: GizChina Source 2: MyDrivers



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

I Was Wrong about the U11: HTC’s Latest Flagship Can be a Remarkable Phone

Just over 4 years ago, I had finally upgraded to what I felt was the next level of Android smartphones, the HTC One, which would later get the M7 moniker. It was premium, solid, and felt expensive, unlike my Galaxy Nexus which was everything other than that.

I kept that phone for a year going from HTC Sense to the Google Play Edition software. HTC not only made a premium phone, but they also made it decently open. Unlike many other manufacturers HTC did not lock down their phone's bootloader, leaving it unlockable in a practice that remains until this day; even offering their warranty to unlocked phones. Somewhere along the way, HTC lost its way and after the excellent (yet arguably iterative) One M8 they fell further by offering dozens of cheap devices, and their premium devices were always behind the times. The M8, like the M7 before it, was class leading and award winning and felt like it was a few minute changes from perfection; however what came next derailed the entire company. The M9 showcased their inability to accept change that the "UltraPixel" was bust, that their design was getting dated due to the rest of the market finally catching up to to their metal construction, and enthusiast hopes clinging to what were ultimately false renders resulted in the perfect storm that hastened their spiral into demise, with both their reputation and finances tanking with no precedent.

There was a glimmer of hope early last year with the HTC 10. While the design was reserved, it was easy to love and adopted many of the improved features that their competitors had for a generation now, like a QHD display and much better optics. Unfortunately, HTC launched up against the Galaxy S7, a phone that appealed to the masses and left little to hate. Following the HTC 10 and in what seemed to be an ill fated and late attempt to capitalize on the market gap left by the Note7, HTC then launched the U Ultra, its dual displayed monster. Unfortunately, the U Ultra was not the phone HTC needed by carrying an extreme cost, large size, poor battery, and limited market reach. Along with with the U Ultra came word that we would not be seeing a successor to the ultimately unimpactful 10 and that the U Ultra would be HTC's 2017 flagship, leaving fans of HTC let down. Surprisingly though, HTC did have another flagship up its sleeve, and while it is more like a smaller and more-developed twin of the U Ultra, it is also the spiritual successor to the 10 (in part signalled by the otherwise-redundant '11' in its name). I finally decided to pick up a U11, after being disappointed with what the OnePlus 5 had to offer, and over the next few weeks I will be writing a few pieces on it, with a decidedly XDA flair.

If are looking for a comprehensive review of the phone, for now we would recommend you look towards some of the other excellent reviews that have been published. I want to focus on what the U11 can be instead what it currently is, because quite frankly, while the hardware package is compelling and the phone has immense potential, the software leaves a lot to be desired despite HTC's relative competence in this space.


The Sense lockscreen is dated in 2017

While it is undeniable that HTC's Sense software is among the lightest weight and best-performing interfaces (the U11 is class-leading in this regard), that speed is mostly relegated to the main interface, and does not fully apply to HTC's home sourced applications. It starts with the horribly outdated and laggy lockscreen, for example. It was back in 2011 that HTC introduced lockscreen shortcuts to Sense, a novel concept to Android that AOSP would go on to adopt in a less intrusive manner. However, Android has changed a lot since 2011's Gingerbread, Sense has not. While there is benefit in this design it now encroaches on the utility of the Android lockscreen by reducing the amount of available space and slimming the amount of viewable notifications to 2 while compressed, and about 4 to 5 when expanded. I am someone who likes to do a lot of notification checking and replying from my lockscreen, and having a limited amount of quick preview space flanked by the icons below and clock/weather widget up top makes you run out of space quickly. This is compounded by HTC's reliance on forcing additional undismissable notifications when music is playing, when night mode is enabled, when WiFi Calling is ongoing… you get the picture.If you are a "power user", the HTC lockscreen and ongoing notification mess might just drive you mad. However, as enthusiasts know, this is a fixable annoyance and if you are willing to put in a little work, it becomes a total non-issue.

The next thing that feels dated about Sense is the primary color pallette for the UI. Sense is still dependent on the stock AOSP color theme which when compared to the light UI of LG and Samsung, and the dark grey and blue UI of the Pixel is not only old, but also subjectively dingy and ugly. HTC does claim to have a theme manager, but it is more of a joke when compared to other offerings allowing minor customizations to the few included applications that you likely will replace anyways. Dialer withstanding, there is not another single application I use on a regular basis that benefits from this theming. Basically, you are stuck with that feels like a forgotten interface that is straight out of 2014. There are also a few other oddities like the camera UI that lags horribly when launched, the odd animation stutters that show up when expanding notifications on the lockscreen, and the fact that HTC removed the custom DPI setting from Developer Settings, seemingly to hide the fact that the camera is poorly coded and cannot adapt to a new scaling. The whole software package makes the U11's inside feel old and dated that does not have the eye-appeal of its competitors, and this is in stark contrast to the hardware which feels rejuvenated and fresh, even if it too is a bit recycled. Those of us regular readers of XDA know that there are theming engines that work with most Android builds like Substratum, and just like the lockscreen issue this theming mess looks to be fixable as well.


I mentioned earlier that I am going to focus on what the HTC U11 can be, because nearly all of those issues stated above can be fixed with some time, root, and ROMs from our developer community — in fact I have already started crafting a more-refined user experience for myself. While there are a few things that flashing a ROM cannot fix, the U11 also brings a lot of greatness to the table. Fragility be damned, the phone looks spectacular and is one of the best-feeling phones I have used in a long time. It has great speakers, and the USonic "gimmick" is the real deal, it sounds fantastic, and almost makes up for the lack of the 3.5mm port. Outside of what feels like the odd animation glitch, the performance of this phone is top notch and makes my Galaxy S8 feel like a mid-ranger in comparison, especially when scrolling through well-coded applications.

Despite its smallish size, the 3,000mAh battery paired with more-efficient components has enough to get you through a day – if just barely – and includes all the fast charging tech you would expect. While Edge Sense and the lack of the 3.5mm port are attempts at class-departing features, the U11 delivers a no frills smartphone experience without throwing useless things your way — that is, gimmicks can easily be ignored, and most annoyances can be swiftly worked around. Unfortunately though, there are some flaws I have found that are not easily fixed. I have found the camera to be a little slow in its default HDR Auto mode and HTC still is missing 1080p60, the screen does not sport the best viewing angles, and no matter how hard you try, the phone will not grow a 3.5mm port.

All-in-all though, the U11 is a fantastic phone, and I do not use that word lightly. We can only hope that it does not continue the HTC 10's legacy of being one of the best phones that many have already forgotten about. On the surface, the U11 takes much of what makes the Google Pixel XL a great phone and improves on nearly every aspect of it while being more affordable. I will be putting that to the test as I begin to root and run custom ROMs from our forums, and as I get to see if I can effectively nail the perfect user experience for my needs.



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

Motorola’s Latest Moto Mod Features a 360-Degree Camera

Motorola's Moto Mod system for the Moto Z lineup has continued to grow and mature ever since its initial debut in September of last year, and thanks to a tweet that was sent out earlier this morning by Evan Blass, we now have a good look at an upcoming 360-degree camera Moto Mod (shown above).

The new Moto Mod was recently launched at an event that Motorola held over in Ghana, West Africa. There's currently no word on pricing or availability for the Mod outside of Ghana, but considering the popularity of 360-degree photography/videography around the world, we'd be surprised if this didn't make an appearance in other markets where Moto Mods and the Moto Z lineup is already available. The Moto Mod uses the same 16-pin connector we saw in Moto Z devices, and should be compatible with both current and future Moto Z devices like Motorola promised back when the original devices launched.

The Essential Phone and its 360 camera attachment

As for the Moto Mod itself, the setup looks fairly simple. The 360-degree camera sits on top above the cutout for the primary rear camera on Moto Z phones, and the main body for the Moto Mod features a white color with a perforated design throughout. The body does appear to be made out of plastic, and the Motorola logo in the middle below that rear camera cutout looks slightly recessed and almost as if it could be a physical button. It's not currently confirmed as to whether or not this is the case, but it'd be a smart use of space for letting people take photos and videos without having to mess with their phone's display.

When talking about modular 360-degree camera attachments for smartphones, it's hard not to draw comparisons to Andy Rubin's Essential Phone and its 360-degree camera. Both Essential and Motorola have their own unique take on how modular attachments should work on smartphones, and although it's far too early to determine which 360-degree camera will be the best, it'll certainly be an interesting comparison to see once each one is released to the general public.


Via: Evan Blass



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