Surface Pro and Screen Rotation Issue

February 17, 2013 10:10 by docbliny 

I was having the rather irritating issue with my Surface Pro where I’d hop on the train for my morning or afternoon commute, and the screen wouldn’t rotate (change the orientation) when I was trying to read with my Kindle app. What made it frustrating was that it’d start working again when I arrived. I read the troubleshooting document and then contacted Microsoft support and they weren’t able to reproduce the issue. This morning, I finally figured out what was going on.

More...


Putting Nexus Q in Debug Mode

July 1, 2012 13:28 by docbliny 

Here’s a really quick introduction on turning on debug mode for the Nexus Q.

Requirements

  • Micro AB USB cable (careful with that connector!)
  • An Android device with the Nexus Q application installed
    • You may need an Android tablet, see Troubleshooting below.

Instructions

  1. On your Android device, turn on USB debugging in the device settings.
    • Go to Settings, and then scroll down to Developer Options.
    • Slide Developer options to ON.
    • Check USB debugging.
  2. Set up the Nexus Q on your network by installing the Nexus Q application on an Android device.
  3. Start the application, and then select your Nexus Q device.
  4. Select Advanced.
  5. Under USB debugging, move to slider to ON.
  6. Go back to the previous screen.
  7. Plug on end of the USB cable into the Nexus Q and the other into your computer.

Troubleshooting

  • If you can’t see the USB debugging option in the Nexus Q application, You will need to turn on USB debugging in the Android device settings first (not the Q application, the main device settings control panel).
    • I could only see this option on the Nexus 7 tablet, not on my Nexus Galaxy phone. The Nexus 7 had the USB debugging turn on in the main settings by default. Thanks to Ryan Warner for figuring this out.

Screenshots

Turn on USB debuggingNexus 7 with debugGalaxy Nexus without debug


Google Asus Nexus 7

June 28, 2012 22:35 by docbliny 

I know I bashed Google after last year’s Android tablet release of the Samsung Galaxy Tab, and I still stand behind that. In fact, the situation got worse. I ended up having to use the Android developer kit to reset the device every few weeks after it got stuck in an infinite boot loop. This was made worse by the fact that I’d bought a case and keyboard dock for the tablet, and I effectively had a brick on my hands. Though, it must be said that the Google IO units were prerelease specimens with custom firmware for developers.

In any case, things look much brighter this year. The Asus-built Nexus 7 is a solid unit and Android 4.1 addresses my main concern, namely the smoothness of the user experience. I’ve only had a chance to play around with it for a day, but it’s night and day compared to other Android devices I’ve used in the past. I’d even go so far as to extend that to the Samsung Nexus Galaxy that was handed out, too (but I' haven’t been able to use it as a phone yet since I don’t have a micro SIM to mini SIM adapter).

Now if there was only a public SDK for the Nexus Q so I could add it to my home automation system…


Samsung Galaxy Tab 10.1 and Android #FAIL update

July 8, 2011 08:23 by docbliny 

In a previous post, I gave my impressions on Android on tablets based on my experience with the pre-release Samsung Galaxy Tab 10.1 with Android 3.0. The final version has come out, along with the all-important Android 3.1 update. So how do things look now?

  • The time zone issue has been resolved. I can now set the time and date without formatting the device.
  • The word “phone” has been cleaned out, and I see “tablet” as expected.
  • The worst Chrome rendering issues have been resolved.

Unfortunately, the worst problem, jumpy and unresponsive scrolling, still exists. This is of course a comparison against iOS, but the different is substantial. On iOS you don’t even notice you’re scrolling. On the Galaxy Tab, it’s like turning pages in a book that are slightly stuck together: irritating.


Where Google and Android #fail

May 15, 2011 11:39 by docbliny 

Google handed out a stack of Samsung Galaxy Tab 10.1 tablets at Google I/O 2011, and just like last year, I’m not impressed with Android. I got my first iPhone from a contest, and I’ve never been a fan of iTunes, but iOS is so much more user-friendly and refined. The experience has improved from my tests with last year’s Evo giveaway (wow, what a dud), but still not there. Here are some of the highlights:

  • If you set “Network preferred” (or similar) to allow the device to set the time/time zone automatically during the initial setup, YOU CANNOT change the time zone manually without a factory reset!?!
  • The device has a dual core processor, yet scrolling is less-than-refined and touch input seems slow, or at least not as responsive as iOS.
  • Tablet-specific: The OS states “phone” in many places. For example, when you hold the power button, you get a “Phone options” dialog. I know I saw similar wording elsewhere, too.
  • The device has two cameras, microphones, and such, and yet there is no Google Voice application available!
  • Chrome has horrendous rendering issues when you scroll longer pages. I need to zoom in/out to get it to render the rest of the page.

Yes, yes. The device isn’t even on sale yet, but these issues seem to have more to do with the Android OS than the device.

The best feature so far has been the cloud/Google account integration for backing up settings (all the apps I’d installed got automatically reinstalled after the factory reset to get the damn clock to show the right time), syncing with Chrome and other Google services.