volumes
The discovery in December last year, of code in AOSP which would have supported a fingerprint sensor on the Nexus 6, saw many bemoan the missing component. In an interview with The Telegeraph, former Motorola CEO Dennis Woodside has confirmed the Nexus 6 was indeed supposed to carry one in the dimple on the rear, and spoke about why it wasn’t included.

Woodside, who is now the CEO of Dropbox, was quite frank about why the fingerprint reader wasn’t included, saying :

The secret behind that is that it was supposed to be fingerprint recognition, and Apple bought the best supplier. So the second best supplier was the only one available to everyone else in the industry and they weren’t there yet,

It’s also interesting to point out that he goes on to say that it “wouldn’t have made that big a difference”.

The removal of code for fingerprint support was quite late stage, indicating that it will very likely make an appearance in the next version of Android: Android M, which we should start learning about at Google I/O this year. With more than a year to refine the technology, it should be quite refined by the time Google does show off their fingerprint reading software and integration.

Source: Telegraph.co.uk.
Via: Engadget.
3 Comments
newest
oldest most voted
Inline Feedbacks
View all comments
Duncan_J
Duncan_J
5 years ago

Slightly off topic, I’m guessing this years Android update will a point increase and we will keep the lollipop name. the only reason I see Google would switch from lollipop so soon is if they feel they the lollipop name has become synonymous with bugs and flaws, otherwise I think they will run with for another year. Jelly bean did the same thing.

Biscuit
Biscuit
Reply to  Duncan_J
5 years ago

You’re so far off the mark. Keeping the lollipop name would not match the pattern at all. Yes, it’ll probably be a point release, but the name will still change to something with an M. Happens every time.

Duncan_J
Duncan_J
Reply to  Biscuit
5 years ago

I’ve looked back at my version history, and Yes I was wrong. the long Jelly Bean cycle was when the upgrades moved from July ish to October ish so JB got a longer run.