LightBlog

lundi 3 octobre 2016

Opinion: The LG V20 Offers One of the Best Year-on-Year Improvements of 2016

On September 6, LG unveiled their latest flagship device, the V20. A few months back we wrote about the V20, discussing how important this device is for LG. Given LG's declining sales and increasingly lackluster offerings, many were hoping LG would provide a solid flagship option with this device.

Now that the V20 has been officially announced, and has been making its rounds in the blogosphere, we can see if it is the device LG needs. The V20 was presented as being the device to "trim the fat" from devices past. During the launch event, LG stated that they listened to customer feedback while designing the V20, and used the feedback when deciding what features to keep and remove. It is important to note that this is not the XDA LG V20 review, and there won't be a review for the time being given none of our in-depth reviewers currently have a V20. This article is meant to be a reflection on the released specs, features and UX improvements of the V20, how it is different from the rest of LG's flagships and how it improves upon the V10. Most importantly, we'll look at what makes the V20 an improvement over the V10 to see if LG stayed true to its word.

"In developing the V20, we looked at the consumers who are fan of the V series. We wanted to really examine what they liked about it, what they needed — and so we looked at popular aspects of it, and we built upon [them]. So you get more of everything you love, and less of everything you didn't need."

Frank Lee

LG_Article_3Starting off we'll look at the changes from the V10 to the V20. The most obvious is the decision to move from a rubberized back to a metal back. This will add to the premium feel of the device, and has done so without leaving the MIL-STD-810G certification behind. Having a metal back this time around will eliminate the peeling issues many V10 owners faced, myself included. It does not appear to be the same faux metal that was found in the G5 as well, meaning there is no false sense of premium.

Seeing a return from the G5 instead of the V10 is the set of dual rear cameras. The dual cameras were introduced on the V10 in the form of front facing cameras, and served a similar purpose as those on the G5's back. The main shooter acts like a regular camera, and the second camera is used to increase the range on the optical zoom. The V10 introduced manual controls for video, aimed to cater to content creators looking to make the best movies possible. The V20 sees the return of manual video controls, with the same amount of control offered in the V10.

For what seems like the first time ever, LG released a phone in the second half of the year with an up to date Android Version right out of the box. Last year's V10 was launched with Android Lollipop, a month or so after the release of Android Marshmallow. This year, the V20 is releasing with the most current version of the OS. This is something that is a rarity in the Flagship-level world sometimes even in Q4. Samsung, Motorola, Sony, LG, and many others usually wait until months later to release devices on the latest platform. Another OEM that has done this is HTC with their A9 offering, which fell just short of the 'flagship' category, and also on its promises of receiving timely updates. Until now each version of Android is debuted on a Nexus device, this year the device to debut Android Nougat is the LG V20.

v20nogat2Not only being up to date, the software seems to break the mold of LG UX of years past. This year LG has focused on marketing the features of Android Nougat, instead of promoting their UX suite. Google has even used the LG V20 to showcase some of Android Nougat's new features, as well as promoting it on the Android Nougat website. The V20 also debuted one of Google's new features: In Apps Search, which will use Google to search through your apps for information.

Something LG built on from the V10 to the V20 is the audio. The V20 is the first phone to feature a 32-bit Hi-Fi Quad DAC. This means that any Audio coming from high-quality devices will sound significantly better than most other phones, as the phone is able to drive more-premium headphones. The V10 DAC was very highly praised, and current impressions from the blogosphere are showing that the V20 outperforms the V10 in headphone quality. The speakers on the V10 were very lackluster, and the majority of early users of the V20 have claimed that the speakers perform much better.

LG also boasts a robust HD Audio Recording ability as part of the "built with the storytellers in mind" theme of the device. The V20 has beefed up the microphones, allowing for 15 extra decibels of audio intake over the V10. The V20 now also includes a feature packed audio recording app to take full control of its three microphones, something not available on the V10. Previous LG phones have gotten a bad rap for having lackluster microphone performance, but so far impressions from various owners of the V20 have shown that said tend is over. This phone is being heavily marketed to content creators, and it appears that it can live up to its promise of extraordinary capturing abilities.

v10screen

The V10's second screen had lots of potential, and the V20 builds upon it.

The V20 may have plenty in common with the G5, but it still holds plenty in common with it's older brother the V10. For starters, the touted Second Screen has made a return. This was a huge talking point on the V10, and came with quite a bit of backlash. It was written off quite early for causing display light bleeding issues, alongside claims of being a 'gimmick' for only offering redundant functionality.

I've used the V10's second screen for the better part of a year, and have found a new level of functionality most week long reviews overlooked. As it stands, the way in which I use my V10 is completely different than how I use any other Android phone. I utilize the features offered on the second screen in a way that allows me to rarely interact with the navigation bar. Setting a shortcut to my launcher in the app shortcuts screen negates the need for a home button, and the recent tasks screen negates the need for a recents button.

Quick contacts and music controls eliminate the need for me to have to leave whatever I'm doing to text a friend or change songs. The V20 added onto this functionality, this time around all notifications are going through the Second Screen, and interacting with them will open the Quick Reply Feature of Android Nougat. The quick settings widget that was only available when the V10's screen was off is now available at any time when the V20 is powered on. It also seems that it is now possible to place shortcut widgets on the apps shortcut panel, with Google In Apps search being the main example.

removableback

The V20 also retains LG's signature feature (and a rare breed these days), a removable battery. Up until now, there hasn't been a flagship phone with a metal removable back — metal bodies and removable backs were deemed incompatible. The G5 showed that it was possible to have a metal phone with a removable battery, but through a pop out slot on the bottom of the phone. Poor build quality with the G5's pop out slot showed that it was an unsuccessful attempt, and the device ultimately failed to sell its modularity. The slot rarely sat flush with the phone, and provided an awkward experience for changing batteries. The V20's take at a metal phone with a removable battery shows that sometimes the classic approach is the best, even if it takes plenty of engineering to bring it up to speed with current trends.

While all the features and additions are great, this isn't everything that is needed to produce a hit phone. Marketing plays a huge factor in how a phone is sold, and so far LG has been dropping the ball on marketing the V20. The launch event was streamed through Facebook, and was announced the day before Apple's iPhone 7 announcement. LG has announced phones months ahead of launch before, but planning the day before a large competitor's announcement is peculiar. It could be reasoned that LG was attempting to topple the hype behind the new iPhone, however it appears to not have worked with many consumers almost flat out forgetting the V20 was launched. On top of that, no one knew when the phone would officially launch, with multiple dates going around as to when you can even order the phone. This issue with early announcements and delayed releases has hurt many products before, including LG's G5.

This marketing hiccup will surely hinder the V20 sales, but an unfortunate recall of another top OEM flagship will certainly help. We wrote on how this OEM's recall will leave a gap to be filled by other OEMs, discussing the gravity in which the recall is affecting their brand. The V20 appears to be a worthy successor to last year's V10, improving on what was needed, and not making sacrifices to get there. It's a no holds barred, flagship-level device that sports a robust amount of features not available anywhere else. It doesn't come with the latest Snapdragon 821 processor, nor the the most RAM, but it's another phone designed for life that improves upon its predecessor in every way that counts, with no compromises sticking out like a sore thumb. LG will need to strike a homerun with this device if they hope to pull mobile sales back from a continuous decline. But by the looks of it, this phone has the punch it takes… now it's just a matter of seeing where LG takes it.

Check out XDA's LG V20 Forums! >>



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

Win an Honor 8: 4GB RAM, Dual-Camera, Premium Design

We're back with another Honor 8 contest, and like before, it's open to all countries! You can enter the contest in numerous ways. Each point you earn is considered an entry, so the more points you earn, the higher your chances are of winning. As a reminder, the Honor 8 is the current flagship from Honor and sports dual-cameras, USB Type-C with fast-charging, a Kirin 950 CPU with 4GB RAM, and a 5.2″ 1080p display. We will pick the winner around during the week of October 17. Good luck!

Win a New Honor 8!

  Honor 8 XDA Review   Honor 8 Forums

  Win Stuff from Honor



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

Facebook Announces Messenger Lite For Older Devices and Emerging Markets

Facebook just announced Facebook Messenger Lite, a new low-resource version of Facebook Messenger (much to the disdain of the developers of Lite Messenger for Facebook), joining Facebook Lite in their portfolio.

Facebook Lite LogoFacebook Messenger Lite is a cut down version of Facebook Messenger, weighing in at under 10 MB. It is designed to be fast to download (even on slower data connections) and fast to open, and includes many of the basic Facebook Messenger features like "messaging, sending and receiving photos and links, and receiving stickers." However no mention was made in the announcement of calling, location sharing, read receipts, or various other features, some of which have likely been cut in order to get down to the smaller APK size that they are targeting. Facebook also made extensive mention of how Facebook Messenger Lite was designed with a focus on slow and unreliable network connections, and how it will help expand Facebook Messenger into markets that it previously couldn't reach.

David Marcus, Facebook's VP of Messaging Products, stated that Messenger Lite was created "for people, who still own older Android devices (think 2009-2011) that have less available 'disk' space, memory, and lower performing CPUs, and that often run on lower bandwidth connections", rather than for people buying current entry-level phones. Back when dual core processors were just starting to hit the market, batteries were commonly around 1400 mAh, Samsung hitting the 1 GHz mark was considered impressive, and many phones were shipping with storage amounts measured in Megabytes. Phones like the Motorola Droid, the HTC Desire, and the Samsung Galaxy S II. Technology has changed substantially since then, and it can be easy to forget how different those devices were from current flagship phones like the Moto Z Force, the HTC 10, or the Samsung Galaxy Note 7 if you haven't seen them in a while, but there are still people out there that use older devices, and Facebook wants to see those people using their communication platform.

Facebook Messenger Lite

Facebook is aware of the reputation that Facebook Messenger has as being a bit of a resource hog, and were very careful in their launch announcement to avoid undercutting their full Facebook Messenger offering. While having people on Messenger Lite is nice for Facebook, they would prefer that people use the full Messenger offering to avoid splintering which parts of the userbase can use which features with each other. They know that there is a risk of people switching from Facebook Messenger to Facebook Messenger Lite, especially as many people have been asking for improvements in Facebook Messenger's resource usage for quite a while now (which was redoubled by Facebook's removal of messaging functionality from the mobile website earlier this year), and are stressing that Facebook Messenger Lite is targeted for early smartphones, the likes of which are becoming increasingly rare in the Western world. As a result, Facebook may decide to permanently keep country restrictions on Messenger Lite similarly to what they are currently doing with Facebook Lite.

Facebook Messenger Lite will be initially launching in Kenya, Tunisia, Malaysia, Sri Lanka, and Venezuela, with promises of more countries being added shortly. It will be interesting to see what countries Facebook Messenger Lite comes to, and what steps Facebook takes to promote it there. Messenger Lite looks like it could be a solid product, but Facebook will need to take some steps to advertise it if they want people to actually use it (although their methods with Facebook Lite seem to have been fairly successful, with it reaching a couple hundred million installs already).

It also will likely only launch on Android, as there are limited numbers of smartphones on other OSes in developing markets (although many companies like Samsung, Microsoft, Apple, and Mozilla have been attempting to make inroads into the market), and Facebook extensively mentioned Android in their announcement.

What are your thoughts on Facebook's strategy of Lite apps? Do you think it is a wasted effort with early smartphones being on their way out? Or is it a smart strategy to target markets that Facebook Messenger cannot reach, especially for something social where every user matters? Let us know in the comments below!



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

Xiaomi Brings the Redmi 3S+ to India via Retail Stores

Xiaomi has been very impressive in their push to increase their online presence. For a long time, buying a smartphone online from Xiaomi was the only official way you could get one of their smartphones or tablets. There have always been unofficial resellers here and there, but the company's flash sales were the only official channel they had and they did this to keep inventory costs down as low as possible.

Then, we started to see Xiaomi branch out a little and sell their products in their own Mi.com webstore as well as 3rd-party websites like Flipkart and Amazon. It had become clear that while the flash sale method works when a device is first released, they could sell much more by expanding their online presence. Online retailers like Flipkart and Amazon have done well for the Chinese electronics maker, but now they're looking for even more retail outlets.

The company just announced they will be building 1,000 of their own brick and mortar retail locations by 2020, but they're also looking to tap into other physical retail stores. It looks like the Redmi 3S+ will be Xiaomi's first smartphone to hit physical retail stores in India. The device was first released back in June of this year and offers reasonable hardware specs for the price Xiaomi sells it for.

You can buy the Redmi 3S+ in India, but it will be available exclusively through the company's retail partners. Xiaomi is advertising a number of their partners in the announcement tweet, but doesn't include them all. So, if you're a frequent Sangeetha, Poorvika, Big C, StoreKing, or Just Buy Live shopper, then you will start to see the Redmi 3S+ on their store shelves. The twitter announcement also mentions it will be available at "other leading retail stores," but doesn't announce the names of those other retail stores.

Source: @RedmiIndia



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

New Pixel and Pixel XL Details Emerge as Preorder Pages go Live

There's been a number of Google Pixel and Pixel XL leaks over the weekend and most seem to reassure us of things we've already heard in rumors. And throughout these leaks, we've learned a couple of new things that hadn't been talked about before. There have been official renders leaked from multiple retailers who accidentally pressed the publish button too early. Which is interesting to have seen happen when even Google isn't scheduled to announce them until tomorrow.

First, we learned that Google Pixel and Pixel XL customers will be able to store unlimited "full resolution" images in Photos instead of being limited by the amount of storage you have on your Google account. We also see there will be a "Smart Storage" feature that will automatically free up storage on your phone so you're never told about being out of storage because of the photos and videos you have on your device.

Live Cases will be available for both the Pixel and the Pixel XL so users can use images from Google Earth and Google Trends to personalize their devices. But what will likely excite even more people is the new leak that suggests the Pixel and Pixel XL will be available in 32GB and 128GB variants. This leak comes from a photo that was allegedly taken from the Telstra system. This photo also shows the 2 color options that will be available at launch (Quite Black and Very Silver). There's no mention of the rumored Really Blue in the Telstra system though.

Nexus fans have been begging for Google to sell 128GB variants of their devices for years but the Mountain View search giant hasn't offered them barring the Nexus 6P. It's interesting to see that a 64GB version isn't shown in this leak, and it makes us curious how much the 128GB version will cost since the base model of the Google Pixel is rumored to be priced at $650 here in the United States. In any case, we'll likely learn tomorrow!

Source: Ausdroid



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

dimanche 2 octobre 2016

“Working As Intended” – An Exploration into Android’s Accessibility Lag

The beauty of Android lies in the many different ways that third-party applications can interact with the system. Password manager apps such as LastPass provide the ability to automatically feed relevant username/password data to almost any login screen. Text Aide allows you to significantly shorten your time texting your friends by allowing you to create text expansion macros. Native Clipboard decreases the hassle involved with frequently switching between apps to copy large amounts of text by allowing you to double-tap any input field to bring up a clipboard. Who can forget Greenify, perhaps the #1 most recommended app by enthusiasts, which keeps rogue background apps in check and can thus enhances battery life? Finally, albeit less familiar with most users, there's AutoInput – a Tasker plug-in designed to automate screen taps, text input, swipe gestures, and much more. These apps all serve vastly different use cases, but each of these apps rely on a very misunderstood part of core Android functionality: Accessibility.

To the average Android user, it might seem odd that many of these amazing features utilized by your favorite app are controlled by a setting under the accessibility submenu. Making an app accessible is typically supposed to mean that an Android app is usable to a person with disabilities. So why in the world do LastPass, Native Clipboard, Text Aide, Greenify, or AutoInput have an accessibility service? Furthermore, why does enabling an accessibility service seem to cause so much UI lag? It doesn't seem to matter what version of Android you're on – whether it be Android 5.0 Lollipop or Android 7.0 Nougat – because the lag caused by certain accessibility services can affect your experience. A simple solution to this problem is to merely disable accessibility services you might have enabled – but in doing so, we lose so much useful functionality. Another solution is to petition Google to "fix" Android's accessibility lag, but Google claims that Android Accessibility is working as intended. We've spoken to a few developers intimately familiar with accessibility services and have researched how the functionality works, and we're here to test that claim: is Android's accessibility lag a bug or is it a feature?


Understanding Android Accessibility

As you might imagine by the name, Accessibility is mostly intended for developers to provide additional functionality for any users with disabilities. Indeed, a quick peek over on the official documentation pages for Accessibility reveals that Google has a pretty narrow view on what kinds of services should be provided by Accessibility Services.

Many Android users have different abilities that require them to interact with their Android devices in different ways. These include users who have visual, physical or age-related limitations that prevent them from fully seeing or using a touchscreen, and users with hearing loss who may not be able to perceive audible information and alerts.

Android provides accessibility features and services for helping these users navigate their devices more easily, including text-to-speech, haptic feedback, gesture navigation, trackball and directional-pad navigation.

Google's TalkBack, which comes pre-installed on every Android phone, is a great example of what the 'typical' Accessibility Service is supposed to be like. Voice Access takes accessibility a step further and allows for almost complete control of your phone using only your voice. But the fact that Google intended Accessibility Services to be used in this manner does not prevent developers from implementing them in whatever way they want – and that's exactly what developers have done. It's exactly because of the way that Accessibility works that makes the feature incredibly useful to users with or without disabilities.

Voice Access on Android - UI Navigation Voice Access on Android - Text Input

To simplify things a bit, here's a basic rundown of how Android's Accessibility works. A developer creates an Accessibility Service that subscribes to various Accessibility Events that are sent by the system to the Service depending on whether or not certain criteria are met. When all Services are disabled under Settings –> Accessibility, Android does not collect or send any Accessibility Events. But when the user starts enabling Accessibility Services, Android will begin monitoring and collecting only those Accessibility Events that the Accessibility Service requests. For example, an Accessibility Service that subscribes to the Accessibility Event TYPE_WINDOW_CONTENT_CHANGED will be notified by the system every single time that a change in the current window occurs. Another Accessibility Event called TYPE_VIEW_CLICKED fires off every single time the user clicks on a button of some kind.

Android Accessibility Demonstration. In this video, I've enabled the app Tasker to monitor for changes in the Window title. This requires enabling Tasker's Accessibility Service. You can replicate this by creating a new profile in Tasker with the 'Event' context set to 'Variable Set' and choosing %WIN as the variable to monitor. In total, this approximately 1 minute video captured 107 changes in the current Window.

These kinds of Accessibility Events occur with great frequency during normal user interaction. So imagine what happens when a user enables multiple Accessibility Services that request high frequency Accessibility Events be fired off. That's right – lag. To mitigate this, developers can more narrowly define what kinds of Accessibility Events their Service should react to and in what context, such as the ability to limit the Service to only react when in certain apps or to limit the polling period between Events. But other than that the amount of overhead generated by an Accessibility Service is dependent mostly on what kinds of Accessibility Events it subscribes to. In essence, not every Accessibility Service will cause lag. A single Accessibility Service that requires a high frequency Event may cause lag, especially if said Service is coupled with another Service that requires another high frequency Event to be monitored.


Diving Deep into Accessibility with APK Teardowns

As you could tell from the video posted above, an Accessibility Service that monitors for changes in the window content can result in fairly noticeable changes in UI performance due to the sheer amount of captured Accessibility Events fired off by the system. However it's quite difficult to determine exactly how much overhead is caused by a particular Accessibility Service. Monitoring LogCat will generally get you nowhere, as Accessibility Events are only printed to LogCat if the developer of the Accessibility Service chooses to do so. Thankfully, the daddy of all Android Accessibility Services, AutoInput, does exactly that. And the LogCat output is exactly as messy as you would imagine.

AutoInput's Accessibility Service AutoInput Tasker Plugin AutoInput Window Monitor AutoInput LogCat Output

AutoInput doesn't hide the truth from us. The overhead caused by the app can be quite enormous depending on what Events you monitor. But this overhead is necessary for the app to function. In order for AutoInput to intercept every key press, every screen gesture, every UI update, and every button press, it needs to monitor the respective Accessibility Events. Without these Events, AutoInput cannot hook into the system and provide the almost unlimited UI automation that it currently allows for. Thus, all of AutoInput's functions make perfect sense within the context of Accessibility. But for other apps, we need to look a bit deeper to understand how their Accessibility Services are handled.

An Accessibility Service's attributes are defined in an XML resource file within the APK. Therefore, we can perform an APK teardown on an app with an Accessibility Service to figure out the Service's attributes. Each app functions differently, so I will try to explain how their Service's attributes relates to the specific function it performs.

Native Clipboard

native-clipboard

Native Clipboard is my go-to when it comes to clipboard managers. If you are looking for a highly customizable clipboard manager, Native Clipboard is a pretty great app. It even has an Xposed Module component to allow you to long-press on the 'Paste' button to bring up the clipboard manager! Unfortunately, if you don't have access to the Xposed Framework (such as every user on Nougat) then you'll have to settle for enabling the Accessibility Service which will allow you to double-tap on any text input to bring up the clipboard manager. Here's what that entails.

  <?xml version="1.0" encoding="utf-8"?>  <accessibility-service android:description="@string/access_decs"  android:accessibilityEventTypes="typeViewClicked|typeViewFocused|typeViewLongClicked|typeWindowStateChanged"  android:accessibilityFeedbackType="feedbackGeneric"  android:notificationTimeout="100"  android:accessibilityFlags="flagReportViewIds|flagRetrieveInteractiveWindows"  android:canRetrieveWindowContent="true"  xmlns:android="http://ift.tt/nIICcg" />  

Native Clipboard's Accessibility Service requests firing off an Accessibility Event each and every time that a view is clicked, long-clicked, focused, or if there is a change in the window state. Without having access to the source code, I cannot say exactly how Native Clipboard works, but it's likely that Native Clipboard waits for the Window state to indicate that the soft keyboard is currently open, and then it monitors for taps on the input field. The app has a polling period of 100ms, so that is definitely quick enough to react basically immediately to changes in the soft keyboard visibility as well as double taps. This could result in some UI overhead whenever the user is using the soft keyboard to type any text, potentially resulting in lag.

Greenify

greenify

Next up is everyone's favorite battery saver, Greenify. Greenify uses Accessibility Events to power its non-root functions.

  <?xml version="1.0" encoding="utf-8"?>  <accessibility-service android:description="@string/accessibility_service_description"   android:settingsActivity="com.oasisfeng.greenify.accessibility.AccessibilitySettings"   android:accessibilityEventTypes="typeAnnouncement|typeNotificationStateChanged|typeWindowStateChanged"   android:accessibilityFeedbackType="feedbackGeneric" android:notificationTimeout="0"   android:accessibilityFlags="flagReportViewIds"   android:canRetrieveWindowContent="true"  xmlns:android="http://ift.tt/nIICcg" />  

It uses changes in the Window State to determine when the phone's screen has turned off, and it requires that you delay the lock screen activation by changing an option in security settings. Greenify will also receive Events of type Announcement or Notification State changed, the latter which is unnecessary on Android 5.0+ devices thanks to the Notification Access feature. It will, however, still receive these events regardless of that fact. Greenify should not cause much overhead by itself, but the possibility remains.

Nova Launcher

nova-launcher

Probably the most popular third-party launcher app on the market, Nova Launcher is an excellent example of an app using an Accessibility Service with minimal to no overhead. The only reason for the Service's existence is to aid certain devices in performing gestures.

  <?xml version="1.0" encoding="utf-8"?>  <accessibility-service android:description="@string/accessibility_service_description"   android:accessibilityEventTypes=""   android:packageNames="com.teslacoilsw.launcher"   android:accessibilityFeedbackType=""   android:notificationTimeout="10000"   android:canRetrieveWindowContent="false"  xmlns:android="http://ift.tt/nIICcg" />  

As you can see, there is no Accessibility Event defined in the XML file. All that is mentioned is the name of a package – Nova Launcher. What happens here is a workaround for certain devices for which Nova Launcher's gestures do not work. This service will provide Nova Launcher all Accessibility Events fired off from only within Nova Launcher. It sounds odd, but it's apparently a way to fix Nova's homescreen gestures if your device doesn't work with them. Since this only requests Events from Nova itself, the Service poses very little overhead.

LastPass

lastpass

Finally, perhaps the most infamous Accessibility Service which causes lag (probably due to its immense popularity) – LastPass. The issue of lag within LastPass is so noticeable that the company has an official FAQ page describing the issue. As the FAQ states, there is nothing you can do about the lag except to disable the Service. Why does LastPass's Service seem so egregious when it comes to lag? Let's take a look at the Service's attributes.

  <?xml version="1.0" encoding="utf-8"?>  <accessibility-service android:description="@string/accessibility_service_description"   android:accessibilityEventTypes="typeViewFocused|typeWindowContentChanged"   android:accessibilityFeedbackType="feedbackGeneric"   android:notificationTimeout="200"   android:accessibilityFlags="flagReportViewIds"   android:canRetrieveWindowContent="true"   android:canRequestEnhancedWebAccessibility="true"  xmlns:android="http://ift.tt/nIICcg" />  

The truth is, there's nothing really out of the ordinary with LastPass's Service. It only requests two Event types to monitor – TYPE_VIEW_FOCUSED and TYPE_WINDOW_CONTENT_CHANGED. It does this because it needs to know when an app/webpage's content changed/comes into focus, and then it retrieves the current window content to look for any password input fields. But since the service constantly does this on two extremely frequently firing Accessibility Events, it results in lag. That's the unfortunate truth.


Living with the Lag

When we first read that Google was closing bug reports about Accessibility lag because the feature was "working as intended", we were just as perplexed and upset as many of you. But rather than accept the explanation at face value, we decided to look into the matter ourselves to determine the truth. So when the Googler on the bug report page said this:

Hi this issue is persistent over Android releases, Also there will always be an additional lag when an accessibility service is enabled. That's because the device, in addition to the standard UI, is providing a lot of information to accessibility services so they can provide an alternative user experience to those users.

We have come to understand why this is intended behavior. Apps that use Accessibility Services in a manner that was unintended by Google will always incur some performance overhead; this cost is simply necessary to provide Services with the plethora of information that Android Accessibility fires off in the background. Android's lag with Accessibility Services is not a bug, but a feature. A feature that we will have to live with unless the entire system is reworked, and I cannot imagine how that would be done to accommodate so many different feature sets from so many different apps.

At the very least, the LastPass developers would not take this sitting down. Their developers have worked with the Chromium developers to optimize accessibility support, perhaps by enabling LastPass support through the use of APIs rather than enabling an Accessibility Service. Optimizing around the overhead incurred by Accessibility Services is one possibility, but as many developers have implicitly noted on the Chromium forums, it's simply a bandaid that won't resolve the fact that unintended uses of Accessibility Services may result in lag.


Special thanks to the developer of AutoInput, joaomgcd, for answering many of my questions regarding Accessibility!



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

BlackBerry DTEK60 Spotted Online; Looks Like a Rebranded TCL 950

BlackBerry's recent decision to license manufacturing and focus on software meant that they would not be developing and manufacturing any of their future phones from that point forth. Their last device, the DTEK50, was a rebranded Alcatel Idol 4. So when images of the DTEK60 surfaced, the likeliness to the TCL 950 could not be ignored.

The images of the upcoming DTEK60 come to us courtesy of Evan 'evleaks' Blass and CrackBerry Editor Bla1ze. The phone's exterior seem all too similar to a phone recently released by TCL (known better in the western world by the name Alcatel) — the TCL 950.

Blackberry DTEK60

There are no specs provided along with the images, but since the TCL 950 is out, we can speculate on what we can expect to see on the upcoming DTEK60 since there is a good chance that BlackBerry's newest device is nothing but a rebrand with perhaps a small spec change here and there. The display on the TCL 950 is a 5.5″ FHD AMOLED display. Inside, there is a Qualcomm Snapdragon 820 SoC, along with 4GB of RAM and 64GB of storage along with expandability up to 128GB. The phone bears a 3,000 mAh battery with Quick Charge 3.0 support, and a USB Type-C port. The device also sports a convenience key on the side. The camera setup involves a 21MP Sony IMX230 with f/2.2 on the rear and a 8MP shooter with f/2.2 on the front.

The DTEK60 might deviate from the TCL 950 on the screen resolution, as the BlackBerry device has been rumored to sport a QHD display. Further, there could be changes on the storage and expandability front, but the rest of the spec is likely to remain intact, including the Snapdragon 820 SoC.

Blackberry DTEK60 Blackberry DTEK60

A listing for the DTEK60 also popped up at NCIX, a Canadian online retailer. The quoted price of the device is 699 CAD, which comes out to ~$533. The price is likely to be adjusted on a per-market basis, but this should give us a good starting point for expectations. The BlackBerry DTEK60 is not official yet, so we would still advise to take everything with a pinch of salt.

What are your thoughts on the BlackBerry DTEK60 so far? Let us know in the comments below!



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