LightBlog

samedi 22 octobre 2016

How do You Think the Pixel Will Change the Android Market?

The Pixel has been announced, widely reviewed, and is now shipping to early bird customers that dove into the purchase without second thoughts. This is a device that Google intends to highly influential, putting a lot of money on the line in the process.

But while the Pixel is a big release for Android, it also comes at quite a price, residing in the uppermost bracket of the market. With such an investment on Google's part, and with so much advertising and excitement behind this product and its features, plus what Google intends to do with its brand moving forward, we must expect some market repercussion. So we ask,

How will Google's Pixel phones influence or otherwise alter the smartphone market? What do you think will happen to Android phones, in particular? Is the Pixel going to be a success, or will the enthusiasm die out or the marketing fail to do its job over time?

Let us know your thoughts in the comments down below!



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

Google Silently Removed Mentions of an “HTC Cerberus” from Pixel XL Source Code

The "Made by Google" motto represents a dramatic shift in Google's attitude towards Android. Rather than cycle through its various OEM partners to co-produce a Nexus device, Google decided to take tighter control over the entire process of designing and developing their smartphones.

These efforts have resulted in the Google Pixel and Pixel XL which have been heavily marketed as the first pair of 'true' Google phones.

But what isn't mentioned in any Pixel marketing material is the fact that the phones are actually manufactured by HTC. Google is rather adamant that they retained control over both the hardware and software for the new Pixel devices, even going so far as to plaster a large Google logo on the back of the two smartphones. HTC has been relegated to the role of an Original Design Manufacturer (ODM) rather than co-engineering the device with Google. Indeed, it would seem that the working relationship between Google and HTC is akin to that of Apple and Foxconn. What many in the industry have dubbed the 'iPhone' of the Android world is thus similar in more ways than just the price.

While Google has contracted HTC to assemble the Pixel phones, Osterloh says the approach is no different than Apple's partnership with iPhone builder Foxconn. Flip the Pixel over and you'll see "Made by Google," another tip of the hat to Apple, which has long made much of the fact that its phones are "Designed by Apple in California." Osterloh says Google will never say the Pixel is co-engineered with anyone else. He proudly proclaims, "It's ours." – Rick Osterloh, chief of Google's hardware vision, speaking to Bloomberg

This working relationship is not foreign to either party in this mix. Google's Pixel C was the first "made by Google" device – and you will find absolutely no mention of any OEM partner in any press release, nor will you find any commits from OEM engineers in its source code. On the other hand, HTC has apt experience as an ODM while previously working for the likes of Sony Ericsson among others. Yet, there is some lingering doubt about how involved HTC truly was in the development of the two Pixel phones. The existence of a previously-unnoticed commit by an HTC engineer removing all mentions of an unknown "htc_cerberus" code name (coupled with Senior Recognized Developer Jcase's observations on the Pixels' bootchain) suggests that HTC contributed in some way to the software development of the two Google Pixels.


Laying the Seeds of Doubt 

Pixel XL Teardown by iFixit

Pixel XL Teardown by iFixit

The seeds of doubt about Google's level of control over the Pixel range has existed since before the phone's release. The first semi-decent leaked photos of the Pixel lead some Android journalists to speculate that the Pixel's seemingly large bezels were due to borrowing the HTC One A9's design. However, Google's statement that the Pixels' design are not based on any current HTC device are backed up by the iFixit teardown which revealed no evidence of the phone's manufacturing origin. Therefore, there's really no evidence to deny that Google created an original design for the Pixel devices.

But back in early September, David Ruddock of AndroidPolice speculated that the relationship between HTC and Google would be more close-knit than their future marketing would let on. Jean Baptiste Su of Forbes corroborated this claim after the Pixel launch by stating that the only truly fundamental difference between the previous Nexus devices and the current crop of Pixel phones is the lack of any OEM branding. If we were to reconcile the idea that Google was solely responsible for designing the hardware with the claim from the Forbes contributor that HTC's involvement is similar to that of previous Google-OEM arrangements, then we would have to conclude that HTC would have been involved in the early software development process for the Pixel devices.


'Cerberus'

Source: Pinterest

If you've ever flashed a factory image for one of Google's Nexus devices, then you've probably seen the code name for your Nexus device. Google has given each Nexus device a code name based on a marine animal which serves as an internal moniker for the development team until the company finalizes a name. For the Pixel devices, though, it's unclear what the naming convention will be given that the sample size is so small. The Pixel C is code named 'Dragon' in AOSP (or 'Ryu' if you look on the factory image page), for instance, while the Google Pixel and Pixel XL, are code named 'sailfish' and 'marlin' respectively.

The two Pixel smartphones follow the internal naming convention for Google Nexus devices, which makes sense given the timeline of reports that the Nexus program was dead. Though we do not know when exactly Google decided to re-brand the HTC Nexus devices as Google Pixel devices, there is strong support to the notion that Pixel phones began their life as Nexus phones given the reliability of the leaks this cycle and the Pixel code names fitting the Nexus naming convention. Thus, we are assuming that, perhaps for quite a bit of time in the Pixel phones' development cycle, HTC was involved much like any other OEM was involved with the development of the Nexus devices. There is not much in the way of direct evidence left behind in the software, but circumstantial evidence from two well-known developers backs up our claim.

htccerberus

First up, XDA Recognized Developer Bumble-Bee discovered an interesting commit in Marlin's source code from the beginning of August. The commit was submitted by an HTC software engineer and it made a single, seemingly inconsequential change – removing the "htc_cerberus" label from the file_contexts file under sepolicyfile_contexts is used to bind a label to a file/directory and can be used by user-space apps. In Marlin's file_contexts file, we can see that "HTC Cerberus" was a label for one of the A/B partitions on the device. Omitting the label doesn't seem to affect anything on the device, as the first public release of the Marlin's source code shows file_contexts without the label. This is speculation on our part, but perhaps this reference to "Cerberus" is related to some internal HTC code name that we are not yet aware of, perhaps a component of the device that was planned to be used or even an unknown device. At the very least, the existence of the commit by an HTC engineer suggests some level of involvement in the software between HTC and Google.

When we first received this information, we were unsure what it could potentially represent. But looking back at a tweet by @jcase (one of the developers behind Sunshine S-Off/Unlock), we started to feel more confident about our argument.

@jcase was able to look at the bootchain, the process your smartphone uses to boot up, and determined that it was fairly similar to the bootchain from an HTC device. To be more precise, he states that "it's a standard HTC bootchain with some hardening/changes." While this claim is mostly conjecture, @jcase's experience with the bootloaders on HTC devices gives some credence to his case. Plus, the fact that the bootchain seems to be an HTC creation lines up with the idea presented earlier that the Pixel devices were originally being developed as Nexus phones.

"Made by Google"

Google aimed to capture the smartphone market by competing directly with the likes of Samsung and Apple. They've picked a perfect time to pick up the mantle of the Android smartphone representative while Samsung is recovering from its Note 7 fiasco. But we'll have to wait and see whether or not their plan to tackle the iPhone will succeed. Depending on the success of the Pixel and Pixel XL, will Google go all in on the top-down approach they only recently committed to? Or will their partners still play a more closer-role than the company is letting on?

Cerberus image source



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

Big Android BBQ Day 1

Day one of the Big Android BBQ has ended. With a turnout of around 400-500 event goers, the Android BBQ had a lot of great talks and delicious food. I was there filming for XDA TV. Here is a recap of the first day. We will have plenty more videos coming out highlighting our competitions and events so keep an eye out for that.



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

Sultanxda Bypasses New SafetyNet Unlocked Bootloader Check on Latest CM13 Builds for OP3

Google's SafetyNet has been a huge thorn in the side of anyone who wants to use Android Pay while having full control over their phones. Until recently, it has mostly been about disabling Android Pay on devices with Root, but a couple days ago, Google took it one step further — they triggering SafetyNet even on devices with unlocked bootloaders.

Thankfully, just like how Chainfire's systemless Root has temporarily bypassed the root restrictions imposed by SafetyNet a couple of times (as has topjohnwu's systemless Xposed, which is known as the open source project Magisk), Sultanxda has found a temporary patch for the unlocked bootloader issue, which he has included in his latest builds of CyanogenMod 13 for the OnePlus 3.

How it works is that SafetyNet usually checks to see if the bootloader is unlocked through the use of verified boot, a feature which has only been around in Android since KitKat, and is not yet supported by every device (a feature which has become increasingly aggressive with Android 7.0 Nougat, even blocking traditional root methods on the Pixel phones). In order to support those older phones that don't have the hardware required to support verified boot, SafetyNet fails to green if it doesn't get any response from the verified boot test.

But as the saying goes, XDA always finds a way:

In order to bypass this, Sultanxda removed support for the verified boot flag from his modified kernel, thereby preventing the bootloader from passing the flag to SafetyNet. This gives SafetyNet the same response it would expect to see from a device that doesn't support verified boot at a hardware level, and as a result SafetyNet allows the device to pass the test.

While this is not a permanent fix (and none before it have proven to be), it should allow people to bypass SafetyNet until Google finds a way to patch this security hole. Thankfully, this particular security hole looks like it could take Google a while to fix, but it is a shame to our enthusiast and developer community that Google is taking these steps in the first place.

People having root support for their own computers is standard for the Linux and macOS worlds (as is admin access for Windows personal computers, although it is not quite the same thing), and yet Google feels that we cannot be trusted with control over our own devices (not shipping with it by default, and taking steps to prevent people from using it). They act as if it is a device managed by them, rather than a device bought from them. Thankfully people like Sultanxda, Chainfire, and topjohnwu are here today to help restore the features taken from us, but what will happen in the future?

Spread the word about this patch so that others can enjoy it on their devices too!



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

vendredi 21 octobre 2016

Interview with Carl Pei from OnePlus pt2: OxygenOS, Software Updates, User Feedback, UX Criticism & More!

OnePlus entered 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 2, where Carl answers questions regarding the future of Oxygen OS, OnePlus' development process, the potential advantages (and issues) of physical sales, the hardware choices that they make, how OnePlus builds a brand, and more.


Mario Serrafero: Going back to software, OxygenOS of course. You guys have had quite a rocky history with software. The OnePlus One came with CyanogenMod 11s, right? The KitKat CyanogenMod. And then that changed and so in total you would have CyanogenMod, OxygenOS, HydrogenOS, and now this new unified platform, which of course will still be Oxygen and Hydrogen. So, you guys have had a lot of software changes, and before we go into that, I just wanted to touch on the topic of the merger of the teams. It also comes at the time where you guys are experimenting community builds and you have detailed the beta program. Is it safe to say that OnePlus is taking updates very seriously now?

Carl Pei: I think we've always taken updates very seriously. If you look at all the android brands on the market, we are probably the one with the most vocal users. And that is not lost upon us. And it's just, if you look at the OnePlus One, it wasn't our own software. OnePlus 2 was the first time we started shipping our own software. So going from 0 to 1 is kinda hard. Bringing a lot of different people from different backgrounds, different companies, it takes time for them to find common processes and ways of working. So it took a little bit of time I think. Right now the software team is getting into pretty good shape. From the cadence of our updates, from the cadence of how fast we can implement feedback. I'm pretty positive about what's going on.

We're actually really grateful towards Cyanogen, because back in the day, no one knew about us

But yeah, The OnePlus One came with Cyanogen. We're actually really grateful towards Cyanogen, because back in the day, no one knew about us and Cyanogen had a really strong following in the early adopter community, and the fact that they even considered working with us. I think looking back at least the first year was mutually beneficial. Like, we got our software, a pretty good OS for our first product, and they got pretty good hardware for when they just came out as a company. So it kinda benefited both companies.

M: I definitely understand what you're saying — that going from having someone else handle the software to just setting up a team. I know that you guys hired some of the Paranoid Android people. But going back to this, we constantly see that a lot of people felt burned with the OnePlus 2 and OnePlus X in terms of updates. And I think that's no secret. I mean you regret it as well. But with the OnePlus 3, on the positive side, OnePlus have had over… I think nine or ten firmware packages so far, counting the community builds of course. And all of those have iterated and added features. So we definitely feel that there is more of a focus towards software that also correlates with the merger of teams. But I wanted to talk about Nougat. How is that coming?

C: We're working on it for all our… sorry, so we didn't release Oxygen officially for the OnePlus One, so for the OnePlus 2 and the OnePlus 3 we're working on it. It's going to come. But I feel like I understand when users see that the OnePlus 3 is getting a lot of updates, that users of the OnePlus 2 might feel a little bit disappointed. However, I feel like we've never actually promised any… we haven't promised a support time window. We never promised the same cadence for the OnePlus 2, and it will get Nougat. It will get Nougat, and I think that's kind of delivering on what they originally bought into. Now, with the OnePlus 3, we're announcing this new beta program with a weekly and biweekly and a one to two month cadence, the internal beta and open beta. I think that as long as you don't promise something, then it's okay. But if you promise something you have to do your absolute best to try and reach it.

M: Yeah, that is good because at XDA we actually call out every time that an OEM promises an update and goes over it.

C: And you've called us out in the past, so we've learnt.

M: Yeah it's true. And again, the OnePlus X I think is the one where people felt the worst. With the whole deal with the Snapdragon 800 and 801. Not being able to get those certified Android 7.0 Nougat updates. But on the plus side, the OnePlus One and the OnePlus 2 had developer communities, the OnePlus One more so than the OnePlus 2. So yeah, OxygenOS. So, you had talked about CyanogenMod and I feel like that's actually really interesting. I hadn't thought of that — if the device hadn't launched with CyanogenMod, the whole development could have been entirely different. That early adopter community as you called it perhaps wouldn't have noticed the phone to the same extent. But something that people loved then and they love now is OxygenOS being a very lean and stock-Android approach. The early community builds kind of changed that, but you guys have rectified that you are planning on keeping this trend. How do you see OxygenOS evolving as it has to add more features and entice a broader consumer base?

C: So it's different for every kind of stage that it's in. So for the OnePlus 3 we said "Hey, what are the top things we can fix to make sure it's a good experience?" And some people might think "Hey Oxygen is just very similar to AOSP, therefore it's very easy to update!" Whereas there's actually a lot of work in ways that people don't necessarily see. Because it's not in the UX or in the framework or a deeper layer than a UX layer. So with the OnePlus 3 we focused on battery life, stability, and speed. So even like if you look at the… so now I'm running the community builds, so its maybe changed a little bit, but if look at the dialer and you close the dialer, the animation is actually different.

M: Yeah, it fades.

C: So there's a lot of small things we tweaked to either make it feel smoother or make it feel faster. The menu scrolling is a lot smoother than a lot of other stock Android products. So those are the three things we focused on, and our doze is a little bit more aggressive than the stock implementation, and in the recent update our auto brightness is a lot better than the stock implementation. So going forward what we're going to focus on with OxygenOS is to make it a more refined version of Android. So Android still has some areas that are a little bit rough around the edges compared to iOS, and that's the direction for OxygenOS going forward. Not necessarily in changing colours. We did some experiments on the community builds where colour schemes changed, and we got some pretty strong feedback. So we didn't try to push that onto our users. It was more "Hey can we do this? Let's see what people say about this." But overall it shouldn't be changing the UI. It should be adding a feature that people want. For instance, wait, when is this going out? When is this going out this one going out, because we're…

M: Sometime next week.

C: So yeah, we can talk about this. So we had a lot of requests for instance that people wanted to be able to lock their apps with their fingerprint.

M: Right, that's what you teased on twitter.

C: So that's gonna come on Monday or Tuesday. And we have other requests. but don't mention, the other things because it's in the works, like REDACTED (but safe to say, we are really excited about what was discussed). Also features that make the experience better like our long screenshots. I don't know if you've tried it, but it lets you screenshot an entire page.

M: Yeah, those are actually becoming more popular, and I love it. It's like you can't go back to having those regular screenshots after you get used to the long screenshots.

C: Also, we're in touch with Snapchat some people have said our Snapchat experience is not the best, so we're working with their team. Basically saying, "Hey, how can we make the best Snapchat experience on any Android device?" But these two examples that we can't mention right now because they're still in the works, but that's our kind of philosophy. "How can we refine android?" not "How can we change the UX for no reason just for the sake of if?" Everything we do has to have thought behind it.

M: Just to wrap up the software section, what are some software features or a decisions, perhaps about the course you've taken with the operating system, that you feel is underappreciated or doesn't have as much exposure.

C: The tweaks that people don't see, like the animation. So Pete, our CEO, he actually basically sat and tapped… Oh yes, we've worked a lot on the app launch speeds, and even the app launch animations.

M: Yeah, I measured them with DiscoMark, and they're excellent, so we definitely noticed that.

C: Pete, our CEO, has been sitting, just measuring different apps and telling the team "Hey, you must get it within this range", and they have to find like different ways of getting it under it. So these kind of hidden stories are some are some of the things that people don't know about and I think are the underappreciated things. But the way we look at it is you don't have to have people know about every little detail. And sometimes when a user uses a product, they just feel like it's an overall solid product. They can't pinpoint exactly what it is, but if it from a brand they trust, they know that a lot of work has been going on kind of behind the scenes. Just like, an example I had, when I bought my first iPad. On the iPad you have this like brightness slider you can pull out, and if you tilted your iPad, the light reflection on the dial of the slider would use your gyroscope to recalibrate and like, reflect that. When I saw that I was like "Okay, so if Apple, if they pay attention to even this, then I'm sure I'm covered for the hardware, for the software, for the cloud service, all that." That's the kind of feeling that we want to deliver.

M: I wanted to go into a couple things before we go into the hardware, and this is kind of related to hardware anyway. So, there have been AMOLED display shortages. I think you have confirmed that. And they're reportedly slowing down OnePlus 3 shipping times. In fact, just a couple weeks ago I checked, and mine would have taken a month. But at the same time, this is also a sign that there is a lot of demand that you guys couldn't account for, and I know that you produce as you see demand, and that unexpected demand kind of ultimately created this shortage in conjunction with the AMOLED shortage. So, at the very least the invite system is gone, and I know that you guys have gotten tons of flak over that before. How can how can you see OnePlus making the purchasing experience even easier and smoother for its customers? Because now you have DHL and it still takes a while… It's not as easy as going to a carrier store for example.

C: So, we have been experimenting. Like, if you look at our e-commerce experience it's been a lot better from the early days with invites. I don't know if you know about this, but the OnePlus One, when we just started shipping it, we didn't even have a UK charger. So what we did was, we went out in the market to buy the U.S. to UK converter, and we shipped a converter with every phone. I mean, the experience has gotten better over time. With the OnePlus 3 we removed the invite system. It's our first time running open sales for smartphones. We underestimated demand, and I think going forward we'll keep learning, but as you say, it's far more easy to just go to a store and pick it up. You can even… I would even rather probably ride the tube for 40 minutes to go pick something up than wait a week to get something shipped. So, we have been experimenting. We used Finland as a test market. So we launched with Elisa, the local largest operator, and kind of by accident, because we didn't do any marketing, we became the… so within Elisa, we've been the top-selling smartphone since August, and the top-selling smartphone through online sales in September too.

But of course, we don't want to keep it an accident. Now we're looking at "Hey, what are some of the things we can do to make sure that we stay number one in this market?" So with these lessons, we went to the UK. We recently launched with 02 as well. O2 is the second largest in the UK, and right now I think we just finished a really high-intensity marketing push. Like, a lot of out-of-home… like Wellington Station had a big banner with the OnePlus 3. One of my friends actually shared some photos, he was in London from from the Netherlands at a conference and he just sent me some photos from a bus station with our ad on it. So it's pretty cool, we're trying new things. What we saw with Elisa in Finland was that, even though we started selling much larger quantities in that one market, it didn't really benefit, or sorry it didn't really impact the online sales. What this means is that the experience that you get offline is like, super good, right? So you get a lot of new people who probably didn't consider you to consider you, and just buy on the spot because it is such a good experience.

M: Cool. So, now that we touched on the AMOLED part, I said I wanted to go into hardware a little bit. You've been pretty outspoken about your screen preferences, and you know, I completely agree with "AMOLED all the way", but at the same time we've heard you talk about Optic AMOLED and how it has a lot of potential going forward. Early reviews were quick to criticize the OnePlus 3 due to its colour space choices and how it ultimately resulted in inaccurately saturated colours. You guys fixed that really quickly with the sRGB mode (to your credit) but what are these Optic AMOLED advantages that we should be looking for? How does it differ from say the AMOLED of the Google Pixel and Pixel XL? Of course, every OEM tweaks their screens to a certain degree, but why do you think it is better? Because we don't have much information about that.

C: So, for the OnePlus 3, it's a concept we wanted to start talking about with OnePlus 3. And for the OnePlus 3 it was mainly just tweaks and calibrations, like tuning on the screen based on what we feel a user likes. Ultimately we just think that the way a user should judge a screen is by looking at it and saying whether or not they like it. But going forward, there are a lot of things you can do with display. You can customize the hardware driver inside of it for your specifications. You can add other technologies, like other algorithms on top of it to improve it as well. So what we wanted to do was we want users to just equate "Optic AMOLED" with "better AMOLED", and over time we will be adding more and more things to refine the display technology.

"Optic AMOLED for the OnePlus 3 was mainly just tweaks and calibrations (…) we wanted users to understand that it's getting better and better"

But we don't want to say like "Oh, the OnePlus 3 is AMOLED, and another product in the future is Optic AMOLED, and another product becomes Super Optic AMOLED." We just wanted to kind of keep the same name, but have users understand that it's getting better and better, and that it's much better than a generic AMOLED display. So, baby steps, and good stuff coming in the future.

M: Right. To be frank, I did find some of the criticisms were valid regarding the colours, the grayscale banding. I didn't find them too offensive, some people are very picky with colours, but I do feel like the sRGB mode, you guys launched it quick. It was in the review builds and I tested it, and it was like "That's it. That's really good crisis management." Better than certain OEMs lately.

C: It's "listening to feedback". And if you look at future products you'll see that, like… even the developer community, right? It wasn't that we try to cater to the developer community. It's just that we listen to a whole bunch of feedback and we also happen to also implement some of the feedback from the dev community and that's why we have things like zero-day kernel source releases; people want us to do it and we thought about it, "Okay let's do it. It's good feedback." Same with AMOLED, the first thing we said was "Hey, maybe we have missed something when it comes to displays, maybe different people have different preferences when it comes to color saturation and tuning." So this is just a matter of reacting to feedback, and that's kind of what the beta program helps us to do in a more structured way.

M: Yeah, precisely. And again, you guys have like 9 or 10 firmware builds so far and you have been reacting to feedback. Every community build fixes a ton of stuff from before, so you're right. Again, to your credit, it might have not launched with the screen that, in particular the super technical reviewers liked. If we are honest, it was specifically the technical crowd ourselves included. I don't think anyone had mentioned it until [AnandTech]. And people expect saturated colours out of AMOLED anyway.

C: There's another story behind is actually… so, you remember when we launched the OnePlus 3, lot of people were complaining about the 1080p PenTile? And back then people were saying "Hey, for VR, this is not good", right? But now when you read forums online no one is mentioning it anymore. Like no one uses their phone for VR. Now, which completely validated our decisions not go with a higher-res display, that'd cost more battery use and cause more heat.


In part 3 we will be discussing the Virtual Reality market, cameras, the future of Android, and much more. Stay tuned!



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

Swappa’s Android App Now Available on Google Play Store!

One of the choices involved in landing a good deal on a smartphone purchase is buying a used product. The idea of a second-hand good might not sound as appealing to all as purchasing directly from authorized sellers, but a surprising number of people will attest that the second hand market can often land you a very sweet bargain.

Especially when your budget is not that high, you can buy a relevant product in good condition at a fair price. The benefits extend onto the other side as well — if you have a gently used phone that is sitting in the drawer because you moved onto something better, why not get part of your investment back and give the phone a new home?

Keeping in mind such needs that often originate in large enthusiast communities such as ours, we at XDA-Developers had announced a collaboration with Swappa back in early-2013, where Swappa was listed as the official marketplace for our community. Swappa served the valuable purpose of providing a market and bringing together buyers and sellers of the same product, while still ensuring that scammers do not take innocent purchasers for a joyride. Considering the size of operations and the complexities involved in matters of money, we all can agree that they have been doing a pretty good job at it.

For a marketplace that dealt with Android smartphones in majority, there was one thing missing: an Android app. Swappa did have an Android app called Swappa Price, but as the name would imply, its primary purpose was to determine the worth of the device.

With Swappa's new marketplace app, conveniently called Swappa, users of the service can now enjoy all the benefits of the website natively on their Android smartphones. Browse through listings as a buyer or list your own phone as a seller — all of it is made easier, simpler, more accessible and more convenient by the Android app.

image-012 image-008 image-010 image-009 image-011

To download the Android app, search for Swappa on the Google Play Store (easier said than done at the moment), or follow along this link. If you prefer remaining old-school, you can still continue on using the Swappa website.



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

Xiaomi Mi 5 Gets Official CyanogenMod Support

The Xiaomi Mi 5 is the latest device to receive official CyanogenMod Support! Head on over to the thread to download the latest CM nightly for the device!



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