Sunday, April 27, 2014

Why Doesn't Wired Headset Remote Buttons Work on Android?

There seems to be some confusion on wired headsets for Android, as in "why doesn't the remote control" work? Something similar to this:

You can find this in most discount stores, for price of somewhere like $5 to $10 if you buy cheap ones, or they can go for $100+ if you go for fancy brand like Dr. Dre Beatz. But that little microphone bud has like 3 buttons (or maybe just 1). 

And they do NOT work on Android. Wonder why? 

Because that's covered by an Apple patent. Really. Granted in 2011. 

Apple could have been gracious and let everybody use that design, and every cheap headphone maker already do, but no. Apple back then was like "NO YOU CAN'T!"

So Android ended up with a different headphone plug design. The plugs are identical, but the signals passed along are different enough so that the Apple headset won't work on Android plugs... and vice versa.

But there is hope!

Tuesday, April 1, 2014

KitKat Journey Cut Short Due to Tethering Issues

I found myself using WiFi Hotspot (i.e. Wireless tether) more and more often as I got a tablet (Kindle HDX 7 inch) and it's WiFi only. I've hacked it so it runs both Amazon AND Google Play (thanks to XDA developers) but I need WiFi.

And for that, SlimKat failed to deliver. It's not their fault... Google changed KitKat's WiFi tether to make it more carrier friendly. I tried an Xposed module that supposedly fixes this, but I can't get it to work.

So it's back to Jelly Bean for me... at least for now.

Wednesday, March 26, 2014


Motorola's Droid Bionic had always been much of a bastard child. it was announced, then retracted, then relaunched, only to be replaced a few months later by the RAZR line. And officially it's too old to receive Kitkat, i.e. Android 4.4. Final update it got was Jelly Bean... 4.1.2.

But don't let that discourage you. There are ways.

My phone was already tweaked to the max, with Cyanogen Mod 10 and all the CPU tweaks I can find. And with extended battery I last most of the day, but when CM10 is getting bogged down, a new start is needed, and thus entered... SlimKat, one of the handful KitKat ports for "Targa" (that's the internal name used by motorola).

My phone is already rooted, and safestraped with rom slots already setup. I did have to delete some stuff to make room for another ROM slot (each takes about 3.5GB), but that's not that difficult with apps like DiskUsage. Before that, I made sure I made a fresh nandroid backup of my latest CM10 setup (so if I have to go back I can)

Installing SlimKat turned out to take longer than it should due to my flaky USB port. I have a proper USB2 cable (AmazonBasics) but when I go USB mode and try to transfer 2 GB of stuff it just quit in the middle, the port goes bing-bong (disconnect and reconnect sound from Windows), and copy failed. I must have spend 4 hours trying different ports and different cables (3 each, in various combos)  I ended up using my alternate transfer: WiFi Explorer.

After making sure all the MD5 matches, the ROM's flashed into the slot and boot commenced, and everything looks good. Had to set up Google again, but it's not a huge deal.

I wasted another 3 hours when I can't install any third party apps. Turns out my battery-bar overlay blocks installs. (WHA?!)  Took me 3 hours to figure it out. Yeah.

Now it's working, and it'll take me another day or two to tweak it back to the way I had it.
Enhanced by Zemanta