Samsung introduced the dedicated Bixby button with the Galaxy S8 and even though fans haven’t grown to love it, the company has made it a permanent fixture on its flagship smartphones since then. The Galaxy Note 9 has it as well. If you’re not content with permanently disabling Bixby, you can get rid of the handset’s Bixby button by just pulling it out.
Get rid of the Galaxy Note 9’s Bixby button
Many users have permanently disabled Bixby on their devices and are irked by Samsung’s decision to not allow the button to be remapped. So they have a button on their device that serves no purpose.
YouTuber JerryRigEverything put the Galaxy Note 9 through his trademark durability test and it passed with flying colors. It’s impressively durable and can’t even be flexed with bare hands so there’s little chance of it bending or cracking under pressure. That’s $1,000 well spent if durability is something that you value in a device.
However, an interesting observation is made in the video. The Bixby button is actually removable and it can be pulled off if the right amount of force is applied. This is actually true for every single button on the handset.
It’s pertinent to mention here that these buttons are securely held in place. You don’t have to worry about them randomly falling off even if you drop your device. It’s only when deliberate force is applied to pry the button will it come off.
If you’re particularly bothered by the Bixby button then you may opt for this extreme step. Do keep in mind that you would then be left with a gap on the left frame. It may also affect the efficacy of the handset’s water resistance so this is certainly not recommended.
Pre-orders for the Galaxy Note 9 have been open since last week. Samsung will release the handset in several markets across the globe on August 24. It will then continue to release the device in additional markets in the weeks to come.
The post Want to get rid of the Galaxy Note 9’s Bixby button? Just pull it out appeared first on SamMobile.
from SamMobile https://ift.tt/2PqkBfR
via IFTTT
0 comments: