HTC One Max flaunts fingerprint scanner in new unofficial pic
Although everybody loves a good old-fashioned spill of information preceding a glamorous smartphone unveiling, you have to admit it’s become a little annoying to know every single detail beforehand. It just spoils all the fun and excitement, don’t you think?
Take the HTC One Max. With a good couple of weeks away from its formal intro, I already know this fellow like the back of my hand. I’ve seen it showcased in stills and even a short video clip (though you can’t really see anything there) and I’ve heard so many things about its spec sheet that I almost can’t stand repeating over and over again “Full HD panel, Snapdragon 800 CPU, 3,200 mAh battery”.
But praise Odin, the folks over at ePrice have earlier today come forward with a new One Max photo that’s bound to fuel a controversy. The giant shows off its sexy back in this new pic next to the other two members of the One family, but for the first time it sports a little something, something beneath the rear snapper.
In all likelihood, the thingamajig there is a fingerprint scanner, which could be a first for a mainstream smartphone. Notice I’ve said “mainstream”, because Pantech’s Vega LTE-A already rocks fingerprint recognition technology, being unlikely to ever leave Asia however.
Don’t know if you remember, but when the always well-informed @evleaks revealed what looked like a press photo of the device, he was also quick to point out we were dealing with “non-final artwork”. That may well explain why there was no fingerprint scanner or anything else to stand out. Of course, there’s no guarantee the latest design is “final”, which is fine by me as it allows for a little mystery to remain intact ahead of the likely IFA unveiling.
The bad news in all this is that ePrice says the HTC One Max will not become commercially available until “late October”. Oh, come on, HTC, don’t botch up this launch too. Do you really not remember how pissed everybody was when the One was delayed and then again and again and again?