Over the last couple of years we've been seeing a slow trend building up where smartphone OEMs are removing the 3.5mm headphone port. Apple said it took "courage" for them to do it, so that they could fit fit in the Taptic Engine for better haptic feedback. Google made fun of last year's iPhone with Pixel ads as it highlighted they were keeping the 3.5mm headphone port. They changed their mind with the Pixel 2 and the Pixel 2 XL while Razer just launched the Razer Phone and chose not to include one either.
The removal of the 3.5mm headphone port has started many heated debates throughout the community. Those who have been using Bluetooth for years generally don't seem to mind the transition because they quit using it long ago. Those who have yet to make the switch often cite pricing, convenience and/or audio quality as their reasons for sticking with wired headphones. This trend seems to keep going and it may not be stopping anytime soon.
Razer made headlines with the Razer Phone this month and its 120Hz display — they're targeting gamers with this phone, but anyone who enjoys a smooth Android experience will likely appreciate the device. However, they decided to not include a 3.5mm headphone port and this made a segment of the community instantly look elsewhere for their next purchase. The CEO of Razer, Min-Liang Tan, recently went on Facebook to explain their decision to not include this audio port.
According to their engineers, they were able to increase the battery size by ~500mAh thanks to the removal of this port. Not only that, but they were also able to offer audiophile quality sound with the dedicated 24-Bit THX Certified DAC adapter. The team felt this was a fair compromise to make and they believe it offers the best of both worlds to their customers. While it doesn't correct what many felt was an unnecessary compromise in functionality (even after this explanation), it's interesting to learn what factors went into weighting this decision.
Source: Min-Liang Tan
from xda-developers http://ift.tt/2AaNCqz
via IFTTT
No comments:
Post a Comment