LightBlog

dimanche 9 octobre 2016

As “Safe” Units Burn, Trust in Samsung Fades: The Recall’s Respectable Merits Have Been Tarnished

I cannot believe I am looking at my Note 7 like this again, just waiting, wondering if it could ever be another case in the news. We trusted Samsung's word, and that they had found and fixed the problem. 

Did Samsung really find out what caused the failures or was this all a massive cover up, a play to get the device back on the market faster? We gave the company a second chance, and all indicators point to that renewed trust being misplaced; now some of Samsung's strongest supporters, those who remained loyal through all of this, are having second doubts. The South Korean giant was even respected for their seemingly swift and precise action with the recall, yet public opinion is turning again with this week's new reports.


note7_blue_croppedI've been a fan of the Note 7, a big fan. I wrote an article over a month ago where I claimed that the Note 7 was a "Remarkable Phone for Life" and I stand by those words. This device is the pinnacle of design for Samsung after embarking on a journey that started with the Galaxy S6. While, the Galaxy S6, Note 5, S7 and Note 7 may resemble each other, they are more like siblings with the Note7 taking the crown in finesse. The symmetrical front and rear panels, 4th generation edge displays, and the 6th iteration of the S-Pen make the entire package class-leading.

Even the software, despite its performance issues, is the best Samsung has done to date.  My personal Note (with some major package disabling) delivers a fast and smooth-enough experience while still retaining almost all of the Note benefits. Saying the Note 7 is my favorite phone in years is not an understatement, and judging by those who waited through the first recall, I may not be alone.

But despite all of that, Samsung has made some critical errors in judgement that not only have stained the Note product line, but are now looking to affect the entire Samsung mobile division. I had my problems with the initial recall, I personally felt like there was little urgency stressed to consumers, and a single email that was lacking the urgency of future emails and carrier messages. Samsung will push advertisements to our devices for a new device, but they won't for a massive scale safety recall? But we know the story, the CPSC got involved in the US while Samsung began to "fix" the problems it had caused world-wide. Due to this the Note 7 became a household name and a topic of discussion in mainstream media news headlines all over the globe, for all the wrong reasons. But it went smoothly (relatively speaking) for a massive-scale and unprecedented recall. Aside from weird situations like craigslist purchases and those who used the loaner system, those who needed a replacement got them and the devices soon went back onto the market, and even third party sellers on Amazon and other services offered returns. Samsung even released its quarterly earning guidance and it reflected that they were relatively successful lessening the damages with an overall profit, even over last year. All looks well in the Samsung camp, job done, time to move on.

If you are familiar with a hurricane an interesting thing happens if you take a direct hit. After the strongest part of the storm passes over with the eye wall, you enter the eye of the storm. Depending on the particular storm, the eye is calm and in some cases even sunny with no rain and little wind. But there is the other side of the eye that comes just after that calm, and that is what hit us this week. First came the Southwest flight that was delayed due to a burning Note7, then a report from Korea, then Taiwan and just in the past 36 hours came two more US reports from Minnesota and Kentucky. All of this forced Samsung to issue yet another statement, one that does not directly rule out failures of replacement devices. The most troubling of all comes from the Kentucky incident where a Samsung employee reportedly accidentally texted the victim instead of his apparent superior leading to any reader to the conclusion that Samsung is not being forthright with its customers. Without a doubt, more and more reports will come forward over the next few weeks. While some may not be trustworthy, it is hardly a coincidence that these reports are rolling in worldwide just after the replacement program completed…


Samsung will introduce a phone next quarter and try to make everyone forget this situation, and millions will yet again by a Samsung device. But for those of us to face the fact of having to replace our phones a second time won't soon forget about this. The first recall was about failed hardware. But this time it is more than just a hardware failure and it is more than just replacing failed phones. This is now about trust and betrayal. Samsung assured us they found and fixed the problem, but they didn't. Samsung told us these replacement phones were safe, but they weren't. Samsung wanted us to trust them wanted us to believe our safety was their top concern, but it wasn't.

Do these issues point to a larger problem at Samsung, should Samsung be condemned due to this issue? Who knows, and it is not the job of an editorial to do so without conclusive evidence. Should you replaced your Note7? As we say in our reviews, it's also not our job to tell you which phone to get or to keep. But like we said with the first recall, if you are compelled to do so then just do it if there is a next recall or if you can return the phone. For those of you remaining on the device it will be important to consider that Samsung may not support this phone with software updates like they would other devices if a second and final recall does in fact take place. Couple that with locked bootloaders for all US variants and the situation is dicey at best (another reason why we stated we can't recommend this device to our audience, even with all of its merits). Further for those that travel, a full travel ban is now a possibility due to "safe" variants failing. It's a personal decision, but it is a important one and all of us have different priorities that will affect the outcome. Personally, I am actively looking into getting my Note 7 replaced, even though I am one of the few people within the XDA staff that thoroughly enjoys and even defends the experience it provides. I have a family with two kids and while the "odds" of my phone failing seem low, it is more a matter of broken trust at this point. It sucks too, because I really enjoyed my Note 7 and the Note line in general, and it's likely we might not see a new Note next year.



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

Homescreen Critique 05

We have another batch of awesome homescreens to go through. Taylor is here to check out user submitted homescreens to see what kind of creative geniuses hang out in the XDA community.

In the previous episode of Homescreen Critique, a lot of users were asking for a tutorial on how to recreate this look.

vlcsnap-2016-09-28-09h29m02s120-1024x576

The artist that created this homescreen has now also written up a tutorial on how to create it for yourself. Check out that post here.

hc1

Check out this homescreen here.

hc2

Check out this homescreen here.

hc3

Check out this homescreen here.

Submit your own homescreen in this thread to be featured in the next video here.



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

samedi 8 octobre 2016

T-Mobile Samsung Galaxy Note 4 Gets Unofficial Nougat

The T-Mobile Samsung Galaxy Note 4 has received a working build o Android 7.0 Nougat. Head on over to keep up with the progress on this ROM.



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

vendredi 7 octobre 2016

Pixel Phone Is All About Software

In this fresh new XDA TV video, Miles takes a close look at all the new software in the Google Pixel. During the launch event, almost no time was spent talking about the hardware on the phone. Most of the time they were pushing new software features like Google Assistant. Check out the video to see all the new software changes in the Pixel phone.



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

Why You Should Prioritize Your API Strategy Before its Design

An API can be an integral part of a mobile application or service, and they aren't something you should just throw together without thinking things through, as detailed as the results could be. While the design of your API is important, it's probably best that you think about the overall strategy first. Once that has been laid out, then you can let the design of the API fill in the gaps. Thinking about the design first can lead to a lot of wasted time and resources, so as Brandon West from ProgrammableWeb believes, one should focus on the overall strategy first.

If you start working out the details of the implementation of your API before you figure out how many dependencies it will create, then you're going about it the wrong way. There are a number of tools and frameworks available to help you build an API the optimal way, so you should utilize the tools that are available for your project before you dive in head first. You should definitely start planning some things out before you even begin.

As West's article says, a few questions you should ask yourself before you begin working on the API is how things will pan out in the long run. Think about who will write the documentation, who will support it to make sure it's running, what are your plans for if/when you have to scale it up from your product or service going viral. You'll also want to plan out who will be handling the support requests from your users, how will you monitor the latency of the API and how you can educate your sales and marketing team about the advantages your API can offer.

In the long run, it's generally better to deliver a poorly designed API that is useful to your users than a well designed API that isn't offering your users as much value. As mentioned, this decrease in value can be from high latency issues, poor support, etc. So plan out your strategy before you dive in and are unable to keep things optimized and running properly!

Read the insightful thoughts of ProgrammableWeb by clicking here!



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

Suhide Updated to Bypass SafetyNet Update

XDA Senior Recognized Developer Chainfire's suhide app has been updated to v0.54 to bypass latest SafetyNet update that broke root hiding mechanisms.



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

Amazon Offers up to a $2.5 Million Purse for a Year-Long Alexa Competition

Amazon does not mess around when it comes to their Alexa assistant. Since the company launched the Echo, they have poured a lot of money and resources into the product. We're seeing new skills added all the time, and the Echo recently surpassed 1,000 skills earlier this year for people to set it up with. Amazon is keeping the momentum rolling with a newly announced year-long competition for a socialbot.

Amazon has laid out the rules here, so be sure to check those out if you are interested. The competition started on September 28th and will be concluded sometime in November of next year. It's broken up into 8 phases and we're currently in phase 1 right now. Phase one is the participation application process so you'll want to send in your application if you plan on being part of this hackathon. Phase 1 will end on October 28th at 11:59 PM PT.

The goal here is to use the Alexa Skills Kit to create the best socialbot you can. The socialbot will need to hold a conversation for 20 minutes and the team with the best socialbot will be awarded a $500,000 cash prize. The winning team's university will also receive a $1 million research grant, thanks to Amazon, but it doesn't stop there. If the socialbot is able to hold a "coherent" and "relevant" conversation for the entire 20 minutes, then Amazon will pay up another $1 million.

This brings the total purse for the Alexa hackathon up to $2.5 million and makes it the highest paying hackathon to date. The previous record was set at $1 million and was awarded by Salesforce during Dreamforce back in 2013. Amazon will be narrowing down the participants into 10 teams and will be providing all of the technology, cash, and travel expenses that are necessary to bring them to all competition-related activities. The finals of the competition will take place at the Amazon Web Services' Re:Invent Conference next year.
Source: ProgrammableWeb



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