samedi 24 juin 2017

Source: Pixel 2 ‘walleye’ and ‘taimen’ Specifications Revealed

The Pixel and Pixel XL were highly anticipated devices, but ultimately they were primarily a first-generation, introductory release for Google, and though they weren’t wholly-spectacular, we regarded them a “foundational release“. What was and remains really exciting, however, is what can be built upon said foundations.

Not long ago, we saw buzz surrounding references to upcoming Pixel devices in AOSP — publications with sources informed on the matter went on to report about the existence of three Pixel devices, respectively equipped with a small screen, a large screen, and of course… an even larger screen. Sadly, the in-between device is said to be cancelled according to Android Police’s sources. That leaves us with “walleye” and “taimen”, the smaller and largest device respectively. A recent report found references to what could be the smaller and bigger Pixel successor in HTC U11 files, but according to 9to5google’s sources, the larger Pixel is actually an LG device, which is consistent with reports earlier this year that suggested LG was a likely candidate for a 2017 Pixel phone, something that was reinforced by a bug report not too long ago.

XDA-Developers has obtained information about both upcoming Google devices, which we’ll detail below, from a source familiar with the matter that spent time with at least one of these phones. We are confident in the validity of the details presented below, given the source’s track record, and since these are seemingly-finalized hardware specifications and features, it’s unlikely that they’ll be subject to change.


Taimen

The larger device coming from Google this year will feature a 5.99-inch display with a 1440p OLED panel provided by LG, which isn’t extraordinary given that earlier this year, Reuters reported about Google investing into LG’s display division for their next phone. The phone will sport a smaller bezel than what we saw in the original Pixel XL, and there is a 128GB storage model, though it might not be the only configuration. The device will indeed pack the expected Snapdragon 835 processor (with the big cluster clocked at the reference 2.45GHz frequency, unlike the original Pixel’s lower frequency in the Snapdragon 821-AB) alongside 4GB of RAM. The back is similar to last year’s with a two-tone glass and metal finish, though the glass window is located near the top and no longer encloses the fingerprint scanner. The device should feature a single camera with dual LED flash.


Walleye

The smaller Pixel device will feature a familiar 4.97-inch display with FHD resolution. While the design remains “almost identical” to last year’s smaller Pixel, with similarly large bezels surrounding the display, Google is planning to include stereo speakers at the expense of the 3.5mm headphone jack, which we are told will not be present in this iteration. The phone will also feature a Snapdragon 835 with 4GB of RAM, and there is a 64GB of storage option, making this one of the few small display handsets with premium specifications.


Pixel vs. Nexus Imprint

An interesting detail we’ve learned about is that the pre-production software our source became familiar with on taimen used the name “Nexus Imprint” when referring to the device’s fingerprint scanner, while walleye’s settings referred to it as “Pixel Imprint”. We don’t know whether this is indicative of a Nexus return, though LG has produced several Nexus devices in the past, and these devices don’t seem to be quite as similar as the Pixel and Pixel XL did. However, this might be something that’ll be addressed in the future, and we have no way of knowing whether it means anything beyond a place-holder or left-over name that’ll be changed as development progresses.


That’s all we’ve learned so far, but we’ll be sure to keep you updated on any new details we get a hold of or any reports that surface on the web. For more Pixel news, stay tuned to the XDA Portal!



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

SultanXDA’s Unofficial LineageOS 14.1 Lands on the OnePlus One

The OnePlus One is a classic. While the phone has not reached the levels of community excellence that vintage devices like the HTC HD2 did, it is seemingly on track to accomplish that status. The OnePlus One is among one of the few modern Android devices that balances specifications with a very strong developer community presence that refuses to let the phone die.

If you are still rocking the OnePlus One in 2017 and rely on the community work to run your phone, there’s some good news coming your way. XDA Recognized Developer Sultanxda has finally updated his unofficial LineageOS ROM to Android 7.1 Nougat.

Sultanxda is recognized as one of the pioneers of development on the OnePlus One, and especially credited towards unleashing the latent camera capabilities on the device. His work began with unlocking 1080p video recording on the front camera on the OnePlus One, and then moving it up to 1440p. He also brought 4K video recording capabilities to the device on OxygenOS. So Sultanxda’s work is well respected in the OnePlus community in XDA and outside too.

Sultanxda’s unofficial LineageOS 14.1 based on Android 7.1.2 Nougat features his custom kernel and camera HAL, similar to previous iterations of his ROM. This allows the OnePlus One to record slow-mo videos as well as timelapses at 1080p 60fps. There’s also 4K video recording capabilities in his ROM. The ROM does feature OxygenOS’s camera libraries with 4K camcorder support through his custom HAL, as this fixes a few issues with Cyanogen/Lineage’s camera libraries.

Since this is the first release, there is no OMS support yet in the ROM as implied in the thread.

For downloads, installation instructions and more information on the features, head on over to the Unofficial LineageOS 14.1 forum thread.

Have you flashed the ROM on your OnePlus One? Have you tried any of Sultanxda’s work in the past? Let us know your experiences in the comments below!



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

You Can Finally Send Any File Through WhatsApp

One of the greatest WhatsApp features is file sharing. With a few simple steps, you can share documents with your friends. WhatsApp is finally rolling out a feature that allows sending any file type, including archives and media files. The rollout is limited and slow, but if you’re lucky, you might already be able to share your files.

Until now, WhatsApp allowed sharing such files as csv, doc, docx, pdf, ppt, pptx, rtf, txt, xls, xlsx and similar. The list of supported files was very limited and didn’t include any media files. Now, the company is reportedly rolling out the enhanced sharing feature to all its users. While this is great news, please note that the maximum size of the share is 128 MB for iOS, 100 MB for Android and 64 MB for a Web client. Those limits are pretty low, but WhatsApp may (or may not) increase them.

WhatsApp is experimenting with this feature only with some users at the moment. If it works for you, you’re fortunate. Otherwise, you can find similar functionality is available in the open-source alternative Telegram.

Let us know if the feature works for you already. This is a server side update, so you don’t have to download the latest beta. You can obtain WhatsApp from the Google Play Store or by visiting the official website.


Source: WABetaInfo Get WhatsApp for Android



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

Android O Introducing an Animated Clock Icon, Soon Available in Custom Launchers

Google might be about to launch a new feature in Android O — Chris Lacy, who is the author of highly regarded Action Launcher, discovered that the Clock application would have an animated icon in launchers.

According to the developer, the Pixel Launcher will soon support the animated clock icon for the Google Clock app. Similar features were added a few years ago for the Google Calendar, but this one would obviously update a bit differently. The clock icon requires a much shorter interval, and Google found a way to implement it.

Chris Lacy discovered the following lines in the AndroidManifest.xml file of the Google Clock app.

AndroidManifest.xml

<meta-data 
  android:name="com.google.android.apps.nexuslauncher.LEVEL_PER_TICK_ICON_ROUND" 
  android:resource="@mipmap/launcher_clock"/>
<meta-data 
  android:name="com.google.android.apps.nexuslauncher.HOUR_LAYER_INDEX 
  android:value="1"/>
<meta-data 
  android:name="com.google.android.apps.nexuslauncher.MINUTE_LAYER_INDEX"
  android:value="2"/>
<meta-data 
  android:name="com.google.android.apps.nexuslauncher.SECOND_LAYER_INDEX"
  android:value="3"/>
<meta-data 
  android:name="com.google.android.apps.nexuslauncher.DEFAULT_HOUR" 
  android:value="10"/>
<meta-data 
  android:name="com.google.android.apps.nexuslauncher.DEFAULT_MINUTE" 
  android:value="10"/>
<meta-data 
  android:name="com.google.android.apps.nexuslauncher.DEFAULT_SECOND" 
  android:value="30"/>

The APK contains the following images:

Of course, those elements combine to make an animated clock icon! This feature will be implemented and available in Action Launcher starting on version 25.0, which has been released. Additionally, the animated clock will be available as a standalone widget.

Animated clock icons are nothing new in the mobile world. This feature was available in early versions of Apple’s iOS, and Google needed a few years to introduce this feature to Android. It’s not a big thing, but it’s one step closer to make Android more consistent and beautiful. Moreover, the animated clock face should soon find its way to third party clock applications.

Hopefully, most of the currently-available launchers will have this feature. If you crave to have it on your device now, head over to the Google Play and get Action Launcher.


Source: The Blerg



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

OnePlus Gets TWRP and Root

Earlier this week, OnePlus finally released the OnePlus 5 smartphone. It has also published the sources needed to develop for it, so it is only a matter of time before developers get on board.

Developers didn’t have to wait long to create a working recovery as XDA Senior Member xdvs23 provided a testing version of TWRP 3.1.1. By flashing a Magisk or SuperSU ZIP file, you should successfully obtain root access. Head over to the thread for details or simply grab the recovery image. Just remember to unlock your bootloader first.


Get the TWRP recovery for OnePlus 5



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

Honor 9 Now Available for Pre-order in the UK for £379.99

Huawei’s sub-brand Honor officially announced its newest flagship, the Honor 9, just earlier this month. Up until now, the smartphone was only available in its home country China but now the company is bringing its flagship to other markets as well.

If you’re residing in the UK, you can now pre-order the Honor 9. The device is available for pre-order from Amazon UK for a starting price of £379.99 — only the blue color option is available for pre-order at the moment. Not all variants of the Honor 9 are available for pre-order right now, though; the one with 4GB of RAM and 64GB storage is the only variant you can pre-order on Amazon UK at the moment. It’s not clear at the time being if the higher specced variants of Honor 9 (6GB RAM and/or 128GB storage) will also be available in the UK later on or they’re restricted to select markets only.

The Honor 9 is a successor to last year’s Honor 8. The latest flagship from Honor features a 5.15-inch Full HD display, an in-house Kirin 960 SoC, 20MP + 12MP dual rear cameras and 12MP front camera, 3,100 mAh non-removable battery, a rear-mounted fingerprint sensor and comes running Android 7.0 out-of-the-box, with EMUI 5.1 on top.

For the time being, Amazon listing of the device isn’t showing the estimated shipping date, however, you can expect the pre-orders to start shipping out soon after the Honor 9’s Europe launch — which will likely take place on June 27 in Berlin.

Source: Amazon UK Via: Android Authority



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

vendredi 23 juin 2017

Bixby Found a Niche in a Crowded Space, but a Late Entrance Strains its Potential

When Samsung announced the Galaxy S8, it felt as if they were as excited to announce the new Bixby application as they were the device itself.

They added a button on S8 that exists only to serve the Bixby mission, chased down methods to remap that key, and they even had a PR stint with major mainstream tech sites to advertise their new tech. To say that it must have been a major disappointment to Samsung management that the full Bixby experience was not ready at launch would be an understatement. While a form of Bixby did launch with the phone, it is not until now, nearly 3 months later, that we get our full look at the full Bixby package, with the activation of Bixby Voice. We wouldn’t blame you at all for claiming Virtual Assistant overload on Android, because there is an overload of sorts.

Ironically enough, the Galaxy S8, shipping with 2 assistants, is only mid-pack allowing the HTC U11 to take the crown for “how much personalized assistant software can we throw on a single piece of hardware”. With nearly all Google phones shipping with the semi-matured Assistant, some OEMs are forcing their own hands and adding things like the HTC Sense Companion, and Samsung’s Bixby. Add to this the ever growing Amazon Alexa and Microsoft Cortana and the playing field gets crowded.


Getting Lost in the Crowd

Announced last year, Google’s Assistant is built off of the Google Knowledge graph and Google Now, further enhanced with what were the buds of an easier and more powerful third party integration, home automation controls, and a more conversational element. Earlier this year, Google made it so that the Google Assistant would be available on all new Android phones as well as all Nougat and Marshmallow devices; provided you were in a supporting country. With it though came fragmentation. Actions that could be done through the Google Home device could not be done on the phone. Similarly, queries that the Allo application version could do also could not be done through the core phone application. This led to a largely disjointed service where you were never quite sure if what you wanted to do was actually available through the method you wanted to accomplish it through. But hey, this is Google… we are used to this by now. Fortunately though, Google has made a lot of progress over the last few months making the Assistant more useful and powerful, but its biggest claim to fame is its accuracy boasting near human levels of effective natural language processing in its specific tasks. Google’s ability to not only understand what you are asking, but also the context in which it is asked is almost uncanny and it is amplified with many users keeping a majority of their content in some sort of Google-backed, and Google accessible holding cell. This is something that the two other large players, Amazon’s Alexa and Samsung’s Bixby, simply cannot match.

Just last month, rumors swirled that the real reason Bixby was delayed past the launch of the S8 was because it was having trouble understanding spoken word, and more importantly all the nuances it has. This is particularly troubling when you figure that Samsung has pushed their admittedly-terrible S-Voice service for years, but yet could not get enough data for a passable service at launch. Somewhere in the middle is where we find Amazon’s service and Microsoft. Both of these services are available on nearly any phone, but Alexa takes it a step farther with native integration with specific phones like the Huawei Mate 9 and the HTC U11. The thing about both of these services is that you cannot have them be the default assistant with a wake word, and they are handicapped in terms of full potential since in most cases they are not able to access the system level options that Google and Bixby bring to the table. In most scenarios, to use Alexa or Cortana you have to make a dedicated effort and first launch the service, which really calls into question if using the voice assistant at that point was even beneficial.


Trying to Stand Out

This brings us finally to Bixby and in particular what sets it apart. Obviously being that Bixby is system level, it brings a level of control that only Google can attain, and in some ways it can makes the Google Assistant look like last year’s tech. At its core Bixby is just another assistant that surfaces things it already knows about you by your demographic, browsing history, and so-on, and makes it look like magic while calling it AI. Beneath that though is what Samsung has really been working on all this time, a service that not only can fetch things for you, but can also do things for you. First there is the standard, but hardly working in the beta, “what’s the weather”, “how’s my favorite sports team doing”, or “how old is the president”. But on top of that is integrations into first party and third party applications. Some examples of what Bixby can do is make Facebook and Instagram posts simply by voice and navigating into settings menus and different application layers. Instead of simply saying “Open YouTube” and having the application launch, you can ask it to navigate to your YouTube channel. The application will open, and then navigate to your desired location. Deeper level integration into applications like this is something that we really have not seen from a developer so far and shows a lot of promise, but it also has some pitfalls.

Anyone who used a Galaxy device prior to the Nougat update knows that Samsung’s multi-window was severely limited. Application developers had to modify their applications to work with Samsung’s implementation or it simply would not be available, without modifications. While this was remedied by root, it was still a problem and pitfall that Bixby looks to be walking head on into as well. Samsung is known for its poor support of software and fragmentation of their platforms and developers simply did not flock to supporting Samsung’s Multi-window. Similarly, Bixby appears to require that developers to support it through a supplied, but not yet ready API. Further, you have to be a user of Samsung’s core applications which are quite hit and miss, so things like the Google Calendar and GMail app are out. until and if they are updated. This stands to severely hinder the support of Bixby for much more than core applications, and in some of those cases the Google Assistant does just as well. While Bixby is still in beta it has some flaws that show that it may have not even been ready for this stage with issues ranging from not understanding simple basic queries like “will it rain tonight”, to surfacing the wrong data in response to a question. It also is slow, and for those of us used to Google’s blazing fast responses this will make Bixby feel like more of a chore than a true assistant.

Having an assistant that makes things more of a chore by not understanding our request, not being capable of carrying out our request, or having to be launched before use, really hinders the growth of the service. How much of this will be fixed through future upgrades is unknown, but we can speculate that they will because of the push Samsung is making to have this be the premiere Voice Assistant for its users. Personally, outside of some limited use cases I have not found voice assistants to be particularly helpful, with many of the tasks I can do by voice are just as easily carried out manually. While interesting, Bixby’s integration into applications is not particularly deep and most of which can be carried out singlehandedly on the device itself faster and with better accuracy or precision.


Implementation Potentially Realized

However, this application integration is where Bixby may be able to carve itself a nice cozy niche; helping people who cannot carry things out manually, or easily. While expanded accessibility services are an aide to those to need to make use of them, Bixby’s ability to dive deep into applications and carry out tasks beyond the simple tap, tap tap, stands to serve as a massive help. For some, doing things like posting photos to Facebook is a daunting task, but being able to ask Bixby to post my photos from today to Facebook make this task simple and help to remove a barrier some may face every single day. Samsung’s accessibility services are already top notch, but Bixby can launch this forward into what was once impossible, or required dozens of steps and a lot of time. However, Samsung still needs users and developers to fully support and embrace Bixby to make this happen and that will be a difficult task. Samsung is still marketing this as an assistant for all users, and while that is true, its real potential may lie in doing what others cannot, for those who cannot.

For the past 2+ months, S8 users have had a fairly useless button on the side of their phones, making it the butt of jokes across the industry. By the time Bixby Voice rolls out, and it still may not even be a full service then, we could be looking at 3-6 months into the phone’s cycle. By then many users may have simply stopped caring or just used the built-in Google Assistant, which may not be quite as diverse in its abilities, but excels at the things it can do. And that is kind of the state of Voice Assistants on Android right now. There is a lot of competition, and a lot of excellent ideas, but they all have to cross the major hurdle that is Google.

Bixby is built off of what we already have, a so-called personalized assistant that tries to predictively provide the information or tools that we need by using information we have already provided it. Likewise Bixby Voice enters an already crowded space, where talking to our phones is great for the simple things but not so much beyond that. Where Bixby Voice stands apart though is the “beyond that”, the area where our voice assistant is not only in tune with us, but also in tune with our device and the applications and services we use beyond toggling the flashlight. But Samsung needs developer support, and they need it bad. They also need more users, more data, and support for more countries and languages, and this is going to be a near impossible hurdle to climb. Google Assistant, Cortana, and Amazon’s Alexa, all started by doing a few simple things and perfecting those while slowly expanding. Samsung is instead jumping into the pool head first with ambition, throwing caution to the wind, like it so often does. It has found success in this method in the past even if it is a little hit and miss. For instance we now recognize Samsung for the near perfecting of the dual edge Infinity display, but lest we forget there was once the Galaxy Round. Bixby’s reputation is already tarnished by its flubbed launch, and stands to see even more tarnishing if they cannot manage to lock down these everyday functions voice assistant users rely on. But the first step has been taken, the product is in the hands of a few users, now Samsung needs fine tune what it is already providing and unfortunately focus back on selling it to the users. Until then though, there really isn’t any reason for most users to switch from what they are already using as a voice assistant; if they are even using one in the first place.


What do you think of Bixby so far? Let us know in the comments below!



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