LightBlog

mercredi 19 octobre 2016

Interview with Carl Pei from OnePlus pt1: OnePlus Story’s and Direction, Current Smartphone Market, Google’s Pixel Phones & More

OnePlus has made its name in the Android market by providing good-value devices that enthusiasts end up enjoying and tinkering with — so much so that their latest smartphone's sub-forum at XDA has become one of the most active ones in an impressively short time.

XDA Editor-in-Chief Mario Serrafero had a lengthy talk with Carl Pei, co-founder of OnePlus, about the direction of the company and its place in the market, its new smartphones and their take on software, software updates and the developer community. This is Part 1, where Carl answers questions regarding the ups and downs of OnePlus' product history leading up to the OnePlus 3, the vacuum left by the Note 7, Apple's influence in the market, Google's Pixel devices and more.


Mario Serrafero: How has the OnePlus 3's reception been in contrast to previous OnePlus launches?

Carl Pei: One metric that we always look at when we do product development is NPS (Net Promoter Scores): Out of a 100 people, how many would recommend it minus how many would not recommend it. The OnePlus 3 is the highest NPS product we have ever made. Our second highest is the OnePlus One actually, but the OnePlus 3 is even higher than the OnePlus One. We kind of made a comeback with the OnePlus 3.

I read the Android subreddit and the OnePlus subreddit every day. If you would have looked at the Android subreddit one year ago, whenever there was something about OnePlus, it would not have been the most positive stuff. But nowadays, all the messages are along the lines of "Next time, I am going to buy a OnePlus" or "I got a OnePlus 3. Buy it, it's awesome!". So it feels super nice.

M: That's something I wanted to touch upon, how does launching a  well-received product like that feel? How does it affect the morale of the team? The OnePlus 2 was kind of a misstep, so how do you feel about that?

C: After the OnePlus One, we thought that we were really good at our jobs. Back then, we did not attribute it to the real reasons that made the device such a success: if you look at it, most of it is timing and luck. Every company tries to release good products — no one goes on to sell a product that they don't think is a good product to a user. With the OnePlus One, we just got really lucky with our timing. There weren't a lot of great choices back then, and the product that we made was also the product that users really liked — so we kind of got lucky

"In the process of developing the OnePlus 2, we kind of forgot who our core users were"

Sometimes, if you don't have any setbacks, you tend to confuse luck with skill. So we all thought that we were really good at marketing, at product.With the OnePlus 2, what we said was "Hey, we already proved this much with the OnePlus One. For the OnePlus 2, we should go a little bit more mainstream."

We started looking at what more mainstream users wanted, instead of what our core demographic — the early adopter, wanted. Therefore, we did not include features like NFC. It made sense if you looked at the overall picture since we were going more mainstream, we did not really need to have NFC. But in the process, we kind of forgot who our core users were.

With the OnePlus 3, we decided to go back to the basics. Our internal goal was actually to redeem ourselves, so all that arrogance had disappeared. Could we use the OnePlus 3 to turn back the clock to 2014?

M: Dialing back to the OnePlus One and the market at large at that point, your company was one of the first to come out with a really impactful yet affordable flagships. Nowadays, this has become a much more common occurrence, thanks to OEMs in Asia particularly. Many of these OEMs are now entering the Western and US markets, and they have similar goals in terms of bang-per-buck, perhaps not the same execution, but they are very aggressive with their pricing strategy. How does OnePlus plan on battling these other OEMs?

C: As a company, we are very internally focused. We get asked a lot of questions: How do you see the market? What do you think about this feature that the competitor has? What do you think about their pricing strategy? What about their sales strategy and channel strategy? Most of my answers have been "I don't know", because I have been working on the OnePlus for ten hours a day and I don't get to look at the market too much. What I do think is that if you have a good product and you have a lean model like we have — we are mostly direct-to-consumer, we don't have huge teams, we don't have huge marketing budgets — when you are doing this, you can always deliver a great product at a more reasonable price. Whatever other people do, that is up to them. We believe that we need to build a brand over a very long period of time.

" The people that buy our product in the very beginning are the ones who take the greatest leap of faith, so you should respect these people the most"

You might notice that some brands like to launch with a low price and also keep on lowering the price every few months – this is something we try and avoid as much as possible because the people that buy our product in the very beginning are the ones who take the greatest leap of faith — they do not have access to all the reviews, or all of the user feedback — so you should respect these people the most. In a lot ways, we think about brand building in a different way. We have never ever wanted to be known as a cheap brand. Over time, as we have more R&D into our products – we are doing a lot of stuff with OxygenOS, we had dash charging on the OnePlus 3, we are developing some other cool stuff – we should be able to charge more for our products. But of course, this should be within a reasonable amount because we are still following a lean model for our company.

M: That is one of the things that I see discussed a lot when it comes to new OnePlus launches — is the price going to go up? And it has been going up steadily, but it is fair to say at the same time that the bang-per-buck kept up or went up. From the OnePlus 2 to the OnePlus 3, for about another $20, you get better bang-per -uck. So are you guys open to the possibility of charging more?

C: We always turn the question around: "If we did this, what would users think? If we did this, would our users like it?". Only if they like it, can we do it. A product is not just the specs — everyone has access to off-the-shelf components. It is what the vision that drives the product. Like for example, why does the volume rocker on the OnePlus 3 feel solid? That is not just coincidence — there is a lot of work that goes behind this. Just to illustrate, in industrial grade mass manufacturing, there is always some slight variance. Some times some things are a tiny bit larger, sometimes they are a tiny bit smaller. In the production line of the OnePlus 3, we separated out the slightly larger volume rockers and we matched them with the slightly larger button holes manually. The attention to detail is not something that you can read on a spec sheet, and it often gets ignored in reviews as well.

M: I have a pet peeve with buttons, so I am always quick to call out when I feel my unit's buttons are loose. The OnePlus 3 does have great buttons so I guess it is working.

C: If you really try your best to make the best product, you should be able to charge a little bit more. For example, if you have a full metal unibody build, you should be able to charge a little more than compared to a plastic build as it also costs more to produce. In the above case of buttons, it costs more time in the production line. So we don't really see it as spec-per-spec versus the price, we see it as the overall product.

M: Talking about the market and pricing, there is one recent event that can't be ignored: the Google Pixel launch. That device is where we see Google taking full control over the hardware to release a fully Google product, and they are advertising and marketing the Pixels quite a bit. However, the enthusiast community, which OnePlus also partakes in, feels somewhat abandoned by Google as Google pushed for a mass market product and ended the Nexus program. Are you surprised by their change in focus? How do you see the death of Nexus as an enthusiast device affecting the OnePlus brand?

C: We are not very sensitive to numbers. The growth and sales are the result of a good product and not the other way around. But the recent events have dramatically increased the demand for OnePlus products. But I do think the Pixel launch is interesting to us because we have always thought that in the mobile space, the company we should be looking up to and learning from is Apple. With the example of buttons was because, all the Android phones have had bad buttons. Why is this so? So we took apart all of the phones on the market, and we figured out how Apple was doing it.

"Up until now, there has not been a real Android flagship that could compete with Apple … That is why Pixel launch is very interesting to us"

They had this process in their factory, and we implemented the same process. Up until now, there has not been a real Android flagship that could compete with Apple. And eventually, if we do our jobs well then in the next years, hopefully we can beat Apple one day. That is why Pixel launch is very interesting to us, to see such a great brand like Google have a go at this and see if whether an Android product can do well and compete with Apple. And if yes, it becomes something for us to learn from.

M: Another market event that you could not have missed is the Galaxy Note 7, which left a big, scorching hole in the market. At the same time, the iPhone 7 dissuaded a lot of users by moving away from the 3.5mm headphone jack. How does the market changes with the facts that we have a new giant player in the form of Google, but at the same time, Samsung's best flagship ever literally burnt away. How do you see this as an opportunity for OnePlus?

C: We think that building a brand is not a short term thing, so you have to think very long term. [These short term opportunities] are not something we think too much about. The incidents with phone explosions, that can happen with any OEM. It could happen with us on our next product, so it should not be something that we use as an opportunity — we should use this as a reminder.

The smartphone market is one of the most competitive markets, and any day can be disrupted by someone new. What the Note 7 incident gives us is that we should always be focused on the quality of our product. We should always be looking around the corner, we are never safe. Although, we are really small, so we do not have the same perspective as Apple or Samsung. But we should never be satisfied and always have in the back of our minds that something could happen, so always be careful and always give your best.

M: On the marketing side, OnePlus has had a web-first approach traditionally. Now, we are seeing more OnePlus advertising in the real world, through sponsored content that mainstream consumers stumble upon. What is the reason behind this shift? Is it more aggressive marketing and how is it playing out?

C: It is a natural development as your company becomes more mature and your volumes get bigger, you have to reach new consumers. Something that I always think about is how much time and effort a lot of our team members have put into the OnePlus brand, which is something that is not visible to all. They work 80-hour weeks, they have been doing this for almost three years, they work weekends, they travel to the US, they travel to Europe — this amount of time and effort put into something should not be restricted to just a niche brand. We would be kind of, a little bit, ashamed of ourselves if we had this great opportunity and we could not become a major player. So we have to become a bigger player as time goes by. Up until this year, we did not have much to experiment with. This year is the first year where we started increasing our volumes, and now we have more money for marketing. So we are testing a bunch of stuff, some of it works, some of it does not.


On part 2 we will be discussing OnePlus software including Oxygen OS and software updates, as well as the future of the platform, and much more. Stay tuned!



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

Exploring Assistant, A New Voice Interface with Familiar Problems and a Bright Future

A staple of sci-fi movies and games is the inclusion of an intelligent robot that receives and executes commands with ease. As we move deeper into the 21st century, the lovable AI personalities we see on TV and in games are slowly making their way into real life in the form of our mobile assistants..

Mobile assistant technology has definitely grown in recent years, but the one mobile platform that has yet to see a true form of computer assistant is Android. Android has been at the forefront of Google search capabilities, but so far has still been missing a true take on AI assistant technology.

Earlier this summer, Google introduced its next step in mobile assistant technology, Google Assistant. The assistant was announced at Google I/Oand was showed off as the intelligent search assistant that Google has been pushing towards for years. After almost an entire summer of radio silence, the Google Assistant appeared again, this time in the form of a limited chatbot inside Google's Messaging Service, Allo. During the #madebygoogle event on October 4, it was announced that the full version of Google Assist would only be coming to Google Home and the Google Pixel Phones. This left a sour taste in many people's mouths, feeling that they had been blindsided by a sudden drop of support.

Thankfully, due to Android's tinker-friendly nature, Google Assistant found its way to the Nexus 6P (temporarily), and many other devices afterwards. The assistant was acquired through a build.prop tweak that makes the device appear as a Pixel XL, and like many of these ports it has been possible thanks to LlabTooFeR. Seeing the opportunity, plenty of us at the XDA office jumped on the chance to have the new assistant on our personal smartphones.

The following findings come from our testing using an unofficial implementation of Google Assistant, a product that is in its early stages. As such, the experience might not be working entirely as intended, and Google will iterate upon what we report.

The port is just a preview, with the Pixel and Pixel XL not being out yet. I was able to get it successfully working on my 2014 Moto X on CyanogenMod 14, Chief Editor Mario Serrafero got it on his OnePlus 3 running CyanogenMod 14, and Senior Editor Matthew Brack got it on his Huawei Mate 8 running their EMUI Marshmallow software through Xposed and an updated Android N-ify module.

jake_proof map_proof mario_proof

Ecstatic at our newfound ability to reach the latest in Google assistive technology, we put our respective assistants to the test to find out if they were as amazing as advertised. To start off, we asked what we could do, just to get a feel for what all the assistant was capable of. The assistant came back with 3 pages of suggestions, and all of the suggested searches worked out how you would expect them to, with a few kinks.

what_do

One such kink, was that you can only set a timer if the Google Clock app is installed. There was an easy work around, by simply asking it to remind you in X minutes to do a task. Another case of two actions achieving the same function disparately is making lists. When I queried make a list, I received a notice that only shopping lists are supported. When I asked it to make a shopping list, it happily made a list in my preferred notes app. Similar problems happened with volume controls, as "mute my device" would not return the same result as the more-specific "mute volume".

yetGoing through and trying to dig out what it can do outside the suggested tasks was quite fun. It's interesting, and a bit underwhelming what the search assistant is capable of doing. When trying to recreate the demo from the October 4th event, I was able to redo the entire demo, minus making a reservation. According to the assistant, that's not working just yet. Some other features were not available yet, such as asking it to read text messages (keyword being yet).

We were able to find that Assistant can modify system settings, such as WiFi, flashlights, bluetooth, and etc. Asking it to change the temperature resulted in a few odd google search results, instead of tapping into the smart home capabilities of Google. I was also having issues attempting to get the Assistant to cast different media to my Chromecast at home.

Communication was another mishap. Google Assistant had no troubles sending Texts, calling folks, or talking through Hangouts. But when we attempted to get Assist to send an Allo message, or call someone on Duo, all that was returned was a Google search for the apps, or a link to their Play Store listing, despite the apps already being installed.

Some commands were hit or miss. Mario was able to get Assistant to pull up an orchestra performance on YouTube by only mentioning key terms rather than a title, where I was unable to. The contextual searching that would recognize that I was in Maps would not work 100% of the time, and asking how far "it" was from a different location would provide directions from my location to the different location, ignoring the dropped pin sitting in Maps. It felt inconsistent, and often times did leave me wondering why it couldn't perform certain tasks as advertised. A gallery of screenshots from much of our testing of Google Assistant can be found at the end of the article.

Currently, it doesn't feel like much more than Google voice search with a facelift

The way in which one reaches Assistant is very familiar to those with a history in major mobile operation systems. To reach Google Assistant, all you have to do is hold the home button and Google will start listening. This action replaces the action used to reach Screen Search (formerly Google Now On Tap), meaning that service was partially removed. I say partially because the ability to read info on your screen for possible search queries is built into Google Assistant, with an upward swipe while on the Assist screen (made intuitive by a small preview sitting at the bottom, which is a nice touch). However, not all of Screen Search's features made it over. The two notable features that have been left behind are the ability to share one's screen and the ability to select any text on the screen. These removals put a damper on Google Assist's functionality, as those were services I used daily. Personally, I'm sad to see these features go, but I'm hopeful they will be added back as Google Assistant develops and expands.

Something that caught my attention was the response time in Assistant. Google seemed to vary the response time depending on what words it had picked up. In general, the end of most complete sentences/phrases would grant a second of time before Assistant stops listening to search. If I were to cut myself off in what seems like an awkward spot in a sentence, I would be given three seconds before Assistant stops listening and starts searching. Another issue with voice is the recognition, which was just as hit or miss as the the commands. We've written about Google's Voice Recognition before, and our sentiments from that article are mostly the same here. When it works, it works. When it doesn't, I find myself having to repeat a command multiple times for Assist to get it correctly.

aiAt the end of the day, the Assistant doesn't feel like much more than regular Google voice Search with a facelift. A lot of commands we could already use in Google Voice Search on any Android phone would react the same. And in part, it's that facelift that makes Assistant feel all the more personal and useful. The interface is structured like a conversation, and will give you suggestions as to commands that are good follow ups to results. However, this still doesn't hide the fact that Google Assist is not as smart as it advertises itself to be by putting the heft of its advertised potential in AI. I'm still not be able to ask it "what aisle is the bread on?" in a store, and it is not on par with what we expect out of such an AI search assistant.

That said, I have found myself using Google Assistant daily since enabling it on my phone. I honestly feel that the readiness and appeal have made Google appear more useful than previously. Not all of our writers who have tested out G Assist feel the same, and some haven't used it since they enabled it. Assist still suffers from many of the inconsistencies and issues we find in Google Now, and even the preview of Assistant in Allo. I also feel like the situation is similar to Google Now on Tap at launch: underwhelming at first, but in time it gained many features and much polish that ultimately brought it up to early expectations. As with most services, your milage will vary. This is ultimately a limited preview; the Pixel phones haven't arrived to us, and the functionality needs to be (and hopefully will be) expanded upon.

The facelift offers a huge improvement in operation, but it has yet to improve function. Even though this still has hints of "Beta Product" all over, it looks as if Google is heading in the right direction to bring us a full fledged personal assistant, right on our phones. In summary, I feel like this is more of a different interface for what we already have, and it also lays the foundation for much of what's to come with the Internet of Things and better service integration. It's bound to get better over time, and it might be a smart move to have the service launch only on Pixel phones at first. It is certainly not there yet, but what we've seen makes it clear that this has the potential to become an integral part of our Android experience more so than both regular voice searches, Google Now and Now on Tap.

You can check out some examples below:

bored brightness clock comm hngt list mute_1 mute_2 nav restr search_1 search_2 search_3 search_4 smrt_hm sys_set trans txt

 



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

Magisk Receives an Update to Version 8

XDA Recognized Developer topjohnwu has just pushed out a new update to Magisk. The update now adds Magisk Hide, it comes with improved SuperSU integration, and it includes support for rc script entry points that are not located in init.rc.



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

Samsung Hit With Multiple Class Action Lawsuits Over the Galaxy Note 7

We assumed this was going to happen sooner or later, and now we're seeing two different cases where Galaxy Note 7 customers have banded together and filed a class action lawsuit against the South Korean tech giant. One of these cases is taking place in the United States and currently consists of three different plaintiffs. The second case includes 38 different Galaxy Note 7 customers. Each of these cases are suing for different reasons, and it's unlikely that the lawsuits will stop here.

The lawsuit in South Korea was filed by the Harvest Law Office earlier today. The 38 different plaintiffs are seeking about $266.80 in damages over inconvenience and anxiety damages. They feel money is owed to them because of the time they had to take away from their day to visit stores for battery checks and/or trying to get replacements done. Not only this, but some are seeking damages because of the anxiety they have experienced from just having to deal with a potentially-dangerous product in their homes.

In the United States, the lawsuit has been filed by the McCuneWright law firm and the three initial plaintiffs are suing because of how Samsung handled the recall process. They were not happy with having to send in their smartphone and then wait weeks to get a replacement. They feel it is not fair for them to have to keep paying for device payment plans as well as their wireless service plans when they don't even have a smartphone to use.

The Harvest Law Office out of South Korea feels confident they will be able to win the suit thanks to the precedents that have been made due to faulty products in the past. In the US, this type of "economic injuries" lawsuits are common after faulty products have been recalled. So both feel that Samsung will be happy to settle so they can avoid this litigation surrounding the Galaxy Note 7.

Source: Motherboard



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

Galaxy Note 7 is Still a Voluntary Recall in South Korea

The issues Samsung has been having with the Galaxy Note 7 is certainly not a secret here in the United States. We've watched as the company launched a voluntary recall program for the device. Then they tried to bring enough replacements into the country so they could restart sales. But only to find out that the new shipments of the Note 7 were also having the same issue as the first batch.

During this time the FAA has made it a federal crime to bring the smartphone onto a plane, and threatens a fine of up to $179,933 and up to ten years in prison too. The issue is so bad that Samsung has even come out and said they will not attempt to refurbish the returned units and will simply find a way to "dispose" of them in an environmentally=friendly way. It's clear to most people that the Galaxy Note 7 is not a safe smartphone and that makes this new information so shocking to hear.

A Korean Galaxy Note 7 customer from the /r/Android subreddit has shown that the Galaxy Note 7 recall in South Korea is entirely optional. The person says the average person in South Korea does not know about the issues that Samsung has been having with it all over the world. Then continues to say they're still seeing the smartphone in the hands of so many people while they're riding the bus.

They tell us that they were told by both Samsung as well as the wireless carrier KT Telecom that the Galaxy Note 7 they own is perfectly fine to keep. There is still a replacement program in effect within the country, and they also have a rental service for those who are waiting for the Note 7 to be replaced, but again, they stress that it is only in place for those who "want" it.

Source: /r/Android



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

Google Pixel Uses the Hardware Crypto Engine of the Snapdragon 821

Encryption on our smartphones is more important today than it ever has been. With more government bodies trying to hack into people's personal computers, having the data that is being stored on our devices encrypted can give us the peace of mind that we deserve — at least some extra, anyway. Google has taken this seriously for a while now,  and has been requiring OEMs to enable encryption by default as long as the hardware meets a certain level of performance.

This lets customers who are spending $500+ on a smartphone know that their data is safe, while also letting handset makers continue to produce low-end and mid-range devices that are not crippled by performance issues. With Google's Nexus program, they've had encryption enabled by default for a while now.

We saw Google representatives talk about how the software solution used in the Huawei Nexus 6P was better than what Qualcomm was offering in the Snapdragon 810. So instead of offloading it to that chip, it was all handled with the CPU. This meant that there were some people who felt it was better for performance to disable forced encryption. Doing so did show an improvement when it came to benchmark numbers, but most couldn't tell the difference in real-world usage.

Now though, a Google engineer that helped to develop the Pixel and Pixel XL has shed some light on how things are working with Google's new smartphones. He says the crypto engine in the Snapdragon 820 and the Snapdragon 821 are so good, that they focused on getting it working with Android 7.0's new file-based encryption. They were able to do just that, so this means the encryption of the Pixel and Pixel XL will not use up significant CPU resources when implemented.

Source: @t_murray



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

Android SafetyNet Now Reportedly Tripped by Unlocked Bootloaders

It's Bad News Wednesday for developers and power users alike. A pleasant day was punctured by several reports coming in that a new update to Android's SafetyNet not only caused existing su hiding mechanisms to stop working (normal case scenario), but also started giving adverse results on devices which were not even rooted!

Android PayInitiating from Reddit's Nexus 6P forums, and then being echoed around at several places including the Reddit Android forums, our own Nexus 6P forums and threads for suhide and Magisk, users are finding that the latest update to SafetyNet is causing devices to fail checks if they have as an unlocked bootloader. Users have tried out different combinations of modification scenarios and masking methods, but the common factor for failure in most cases boils down to the bootloader being unlocked.

Unlocking the bootloader is the first step for unofficial modifications for most devices. If the latest SafetyNet update does indeed check for the bootloader status, this might mean the end of the days where one could run Android Pay and other SafetyNet based apps in conjunction with root and Xposed by employing masking techniques.

Magisk developer topjohnwu commented on the early situation, pointing that SafetyNet might be a lost cause after this update:

"Keep in mind, in the latest update of Safety Net that just happened in a few hours, Google seems to step up the game, and it might got to the point that no modifications are allowed, and might be impossible to bypass.

Currently on my HTC 10, no matter what I did to the boot image, even just a repack of 100% stock boot image, Safety Net will not pass under any circumstances. On the other hand, my Nexus 9 running stock Nougat seems bypass without issues, with root and modules all enabled and working fine. The boot verification might vary from one OEM to another, HTC's implementation might just be one of the first included into Safety Net, but eventually all major OEMs' method will be included, and at that time I think any Android "mod", including custom kernels, will pretty much break Safety Net. These verification should be coded deep into the bootloader, which is not that easy to crack. So the conclusion is that I will not spend that much time bypassing Safety Net in the future."

Back when suhide was released, Chainfire had predicted something along the same lines:

Ultimately, information will be provided and verified by bootloaders/TrustZone/SecureBoot/TIMA/TEE/TPM etc. (Samsung is already doing this with their KNOX/TIMA solutions). Parts of the device we cannot easily reach or patch, and thus there will come a time when these detection bypasses may no longer [be] viable.

Since the situation is still developing, things might be more complex than what they appear on the surface. We will keep our readers posted if there are new developments on the matter.



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