Forget Bending, Nexus 6P May Have Speaker Defect

UPDATE November 5, 2015: Several people are reporting this issue on Reddit and XDA(The XDA link provides several links into Reddit covering this issue.)

While Bendgate 2.0 haunts the headlines, Speakergate continues to gain attention, and many people are growing concerned that this is a widespread issue. Below is my original post, before I was able to locate other people having the same issue. It’s time for Google to acknowledge Speakergate and address it.

I received my Nexus 6P on November 3rd, and by the end of the day I was printing out a UPS label to return it to Google.

I ordered the 64GB variant in aluminum on November 2nd along with a $34.99 case, and was not expecting to receive it until the 13th of November or later, so you can imagine my amazement when Google emailed me a tracking number on the evening of the 2nd. I had ponied up $18.99 for overnight shipping, but skimped on buying Nexus Protect, as replacing a cracked screen would cost less than the $79 deductible + the $89 purchase of the Nexus Protect coverage. When my phone arrived on the 3rd, I was excited to set it up, but I was taken aback by how much time it took to install a 49 MB OS update – close to 45 minutes!

I’ll spare you a review, as the internet is choking on them. It’s a great device, what can I say?

But, I noticed the one of the front facing speakers was much louder than the other. The earpiece speaker, to be exact. I played back a few videos and moved the phone this way and that, rotating it and moving it back and forth around my face, from ear to ear. Nope, it definitely wasn’t my hearing that was impaired, the bottom speaker was a whisper compared to the top one.

I searched the internet for any complaints about this, but the nets came back empty, so I contacted Google. The nice lady on the phone informed me that she had actually dealt with the same issue two weeks prior, and that she had spoken with the manufacturer to determine if this was a design flaw or just a defective unit. It was determined to be a defective phone.

The nice lady on the phone expressed concern about this speaker problem being more widespread than just a handful of units. I agreed with her that it would indeed be unfortunate.

The OS has no feature to balance the audio channels for the dual speakers, so there was no workaround to this annoying problem.

After having me do the mandatory reset on the phone, the nice lady said I could trade it in or get a refund. A trade in would entail a $584 hold on my bank account, which is $584 I don’t have to be held, so I opted to just mail it back for a refund.

I have to say that I am disappointed, because I truly loved the phone. I am also extremely hesitant to purchase this device a second time – I’m already out $34.99 on the case, and a further $18.99 for shipping. At this point, I have not yet decided if I wish to risk a repeat of this ordeal in a couple of weeks when the refund finally hits my bank account.

Advertisements
Forget Bending, Nexus 6P May Have Speaker Defect

Native NFC wallet arriving with Windows 10? A beta app exists, so maybe.

A slide showing how tap to pay will function on Windows 10 phones.
A slide showing how tap to pay will function on Windows 10 phones.

A recent story revealed that Windows 10 on phones will be receiving an overhaul for NFC transactions. The Secure Element in SIM cards from some carriers will continue to be supported, but users will no longer be forced to use such a SIM in order to use NFC payment terminals.

Microsoft will be implementing something call Host Card Emulation with Windows 10 on phones. Google added support for HCE in Android 4.4, removing a carrier requirement that phones be equipped was a Secure Element or an Enhanced SIM. HEC supports credit, debit, loyalty cards, smart cards, and transit passes. Essentially any card which can be read via NFC can be emulated by software, without special SIM cards needing to be present in the device.

There are no details as to how this will be implemented however. The above slide indicates that the native Wallet will function on its own (as it was supposed to have done in 2012 with Windows Phone 8) while also supporting the non-existent third party payment apps, such as CurrentC (which uses a QR code system rather than NFC) or Apple Pay, should it ever expand from Apple devices.

Unless Microsoft fully implements their own solution, all of this means nothing, aside from the requirement that consumers are able to obtain a special SIM card which most carriers around the globe do not use, nor do they have any intention of adding it unless they have to in order to support a new iPhone. Microsoft will not hand just anyone the APIs for creating an NFC wallet, only select partners receive that access.

Further adding to my initial confusion is this video, which appears to show a third party app on a Lumia 1520 being used for tap to pay. At first glance at least.

Wait… Let us take a closer look.

An app called zNFCPayments is seen running on Windows 10 for phones.
An app called zNFCPayments is seen running on Windows 10 for phones.

zNFCPayments? What on Earth is this? If you have used Windows 10 Technical Preview, the first few builds had an app called zStore, which is now labeled as Store (beta). This means Microsoft is not only overhauling the APIs in the OS and adding HCE, it is also building an app, which may be included in a future Tech Preview build on the phone side.

However, it’s possible that carriers will derail this, making it an app that only some have access to, but not others, much like the Google Wallet debacle played out until Google bought SoftCard (and snatched away the only Windows Phone app for making NFC payments). We should know more about this soon.

Native NFC wallet arriving with Windows 10? A beta app exists, so maybe.

Windows 10 ROMs for Android handsets could be the perfect Trojan horse for Microsoft.

Microsoft and the world’s third largest smartphone manufacturer, Xiaomi, have announced an upcoming program which will allow current owners of the Mi 4, which runs Android KitKat, to try Windows 10 on their handsets via a ROM which will replace Android. Microsoft will be running this program independently of Xiaomi, which implies that other phones from other companies could be on Microsoft’s conversion list.

Microsoft did not announce that the ROM will be available to more than one specific phone, but it is impossible for me to imagine this ROM staying put for long. Hackers will get this ROM into any phone with similar hardware pretty quickly I imagine. Microsoft and OEMs can already drop the OS onto Android phones (HTC M8), so this move shouldn’t come as a real surprise.

But what if Microsoft itself releases a generic ROM for Android users to flash onto their handsets? The Galaxy S6 and S6 Edge are off the table due to the Samsung CPU, but the LG Flex 2 and HTC One M9 could run the ROM with ease, as could basically any other Qualcomm based handset. This opens up a whole new user base for Microsoft.

Releasing a ROM for most Android handsets has several implications, not the least of which being that anyone who flashes this onto their phones will be voiding their warranty and potentially losing support for custom hardware features, such as fingerprint scanners and heart rate monitors.

On the flipside, many modding enthusiasts would likely leap at the chance to put Windows on their Android phone, and people feeling disheartened with Android could leap to Microsoft’s OS while keeping their existing handset.

Microsoft could also buy flagships in bulk and flash Windows 10 onto them itself and sell the phones in its own stores, or offer free conversion services for select phones.

Cyanogenmod likely won’t be happy with this news, but I imagine Google is even more upset. Here is Microsoft, with its scrappy third place OS, already sneaking itself onto Android phones with Office, OneDrive and a host of other apps, soon including Cortana, making a play to grab the entire phone away from Google. It could go nowhere, or it could be a very clever move to steal more market share from Google.

Windows 10 ROMs for Android handsets could be the perfect Trojan horse for Microsoft.

Google and Pebble troll Windows Phone users.

CaptureIf you use a Windows Phone, you were trolled today. Twice.

Imagine, if you will, Microsoft suddenly yanking Minecraft from Google’s Play Store. They offer no public explanation, the apps are just gone and there’s no refund either. It’s a $10 app! This would be Microsoft saying, “Fuck you too, Google.”

Okay, this isn’t going to happen, ever. But something similar it is about to happen on the Windows Phone Store, with Google playing the role of the dick waving lunatic.

softcard

Google hates Microsoft. They hate Windows Phone even more. Their refusal to allow Microsoft to make an official Youtube app, and refusing the write one themselves, is the finest example of this. They don’t mind trolling Windows Phone users.

This week, Google, realizing that Apple Pay is a threat, bought the “technology” behind Softcard, an NFC wallet app for Android and Windows Phone, which only debuted in late 2014. Google is wasting no time rolling that infrastructure into its existing Wallet app, which is available on both Android and iOS. Softcard, as a company, still exists, but just what it’s doing is anyones guess at this point.

It was revealed today, as part of that sell off, that Softcard will be removing its app from the Windows Phone Store and also from the Play Store, because the best of the app and its backend are being merged into Google Wallet. This isn’t an issue for Android users, as carriers will now stop blocking Google Wallet as part of the deal, and the iOS app will benefit from these new additions as well.

On the Windows side however, this is a major middle finger. Getting the Softcard app already involved several hurdles. You have to have an Enhanced SIM. You also need a third-party app installed on the phone to act as the NFC wallet.

Microsoft’s native Wallet app has technically supported NFC payments since the launch of Windows Phone 8 in 2012, but it’s never been implemented because Microsoft saw the carriers blocking Google Wallet when it appeared on the scene. Microsoft opted to wait for Softcard, which didn’t arrive until late 2014.

In fact, other NFC wallet apps, like Google Wallet, Apple Pay, and CurrentC could function on Windows Phone, but those apps are not coming. Softcard, made by the carriers, was the only option for American users.

Once the Softcard app is gone, Windows Phone users will once again be without an NFC wallet solution. They won’t be tapping to pay for the foreseeable future. With the success of Apple Pay, perhaps Microsoft will just raise its middle finger to the carriers on this one and build out its existing Wallet app to support NFC. We can only hope.

Pebble

But, the trolling didn’t stop there. Several people, myself included, reported that a Pebble app may be coming to Windows Phone. This was hours before the Softcard announcement, so technically, Pebble got the first and last lulz of the day.

Shortly after the Softcard announcement, Daniel Rubino published a bombshell of a story on Windows Central. It’s really a must read. He reported that Microsoft wrote an app for Pebble, with Pebble’s blessing. Not just an app, but they wanted to partner with Pebble just like they have recently done with Fitbit. There are Fitbit bands in every Microsoft Store, on their webstore, and Fitbit bands are even being given away with Lumia phones.

Imagine the surge in publicity the already moderately known Pebble would get. Their watches would be on TV, at AT&T, in Microsoft’s stores.

Microsoft was even offering to update and maintain the Pebble app, on their own dime, like they already do for Facebook’s app on Windows Phone. Mark Zuckerberg likes Microsoft though. He likes them a lot. Microsoft even invested an obscene amount of money into Facebook back when it was basically just another wouldbe Myspace killer. Facebook had no qualms with Microsoft doing as they wished with the Facebook app on Windows Phone.CaptureSo, Pebble was going to get the Fitbit and the Facebook treatment from Microsoft. How could they say no? All Microsoft wanted some preferential treatment, so maybe some Pebble updates and apps arrive on Windows Phone first. No big deal.

Pebble said no. Pebble said no even when Microsoft’s own CEO asked Pebble’s CEO, Eric Migicovsky, to enter into this partnership. Eric Migicovsky does not like Microsoft, but he does believe that there must be three smartwatch platforms.

a361fd85680fccb17de65c13aa3e73bd_original

Minecraft creator, Notch, and Steve Jobs, made it cool to hate Microsoft, and now some people are all too happy to stick it to the software giant.

Microsoft poured thousands of dollars into the Pebble endeavour, only to walk in on Pebble dick riding Apple and Google.

And it’s only safe to assume that Microsoft went through similar hoops to woo Snapchat onto the platform, only the catch Snapchat in the act of dick riding too. At least Nokia was able to drag Vine and a beta version of Instagram to the maligned OS.

Need some salve? Ello, that plucky upstart that had everyone talking last September, has expressed interest in making a Windows Phone app. Yeah, I just trolled some of you, sorry.

More trolling.

Oh yes, there’s more. Several media outlets, including Yahoo! have been loudly pounding the nails into the Windows Phone coffin over the last two days, and some even have latched onto Windows 10, declaring the mobile version of the OS dead on arrival, even though it’s hardly a beta yet. Windows Phone just can’t catch a break. Not from the media, and not from dick riding CEOs. And standing between Microsoft and the hail of bullets? Windows Phone users.

Google and Pebble troll Windows Phone users.

Could Cortana come to CyanogenMod?

Cortana reminds me to not burn a pizza in the oven.
Cortana thoughtfully reminds me to not burn the pizza in the oven.

News broke earlier this month that CyanogenMod has met with Microsoft, seeking an investment to further their vision of an Android totally devoid of Google services, installed by OEM on devices. $70 million is the figure I’ve seen reported. But, with Microsoft itself developing a plethora of Android apps, including a lockscreen, why wouldn’t they attach a rider to their investment, insisting that their apps and services be on the platform? It makes a lot of sense.

So, let’s say Office, Outlook, OneDrive, and Skype are installed by default, or maybe they are placed prominently in the app store. I know, it’s not as exciting now as it would have been in 2013, so, let’s hit pause.

When Microsoft unveiled Cortana while showing off Windows Phone 8.1, they hinted that she might arrive on other platforms too. And arrive she has. She made her PC debut in January, on the Windows 10 Technical Preview. We can safely assume she will also touchdown on the Xbox One later this year, perhaps in October or November. Sony has nothing like Cortana in its stable, so this will serve to further differentiate the two consoles.

Microsoft has also never precluded iOS or Android. iOS wouldn’t make much sense, because she would be a second class citizen; an app to be launched, a better Bing app. Android would allow her to be almost a first class citizen however. If Google allowed a Cortana app to be included in the Play Store however, she likely wouldn’t be able to totally replace Google Now, thus she’d have a quasi-Cortana experience. She could toggle your wifi, send an email, set reminders, and maybe even add and remove things from Google Calendar, but you won’t be invoking her by saying “Hey, Cortana” nor will she integrate fully with the OS. She also won’t be automatically reminding you to pick up the dry cleaning next time you are near the laundry service.

Okay, unpause that CyanogenMod story now, because this is where both threads cross; Microsoft could build a Cortana experience which replicates the experience on its own platforms for CyanogenMod.

Google Now could be completely replaced by Cortana in CyanogenMod, because the goal of the CyanogenMod team is to make a better Android. An Android which has rid itself of Google’s multiple apps and services. Microsoft has already shown that it’s more than willing to build apps for Android, so this really is not far fetched. And with Cyanogen holding out the hat, Microsoft can probably get away with insisting that Bing is the default search engine, Outlook the default mail app, and Cortana be baked into the OS, ready to be enabled by the user, as it is on Windows Phone. I could even see a small team at Microsoft being devoted to just that.

So, when do I think this could materialize? I would guess that after Windows 10 is a year old, Microsoft would feel comfortable bringing Cortana to third-party platforms like CyanogenMod, which pose no real threat to their handset business for now. Perhaps we will hear news of this sooner, but I don’t think Microsoft wants to announce that Cortana is on CyanogenMod before the first Windows 10 commercials hit the airwaves.

Could Cortana come to CyanogenMod?