I just wanted to write up a followup review for the Asus Garminfone offered by TMobile. I recently had a chance to use my phone as a navigation tool while we were in LA. We had written directions, but did get lost (as we usually do when we take a road trip to los angeles). All we had to do was enter the address, or search for the location in the google search. All we had to do was look the location up on a map, and press "go". It was that easy. We even used the navigation to find the nearest gas station before we left LA. I liked the ease of use, and the simplicity of verbal commands. If we missed a turn, or couldn't complete the direction, the directions were simply readjusted by the GARMIN. If you don't get the phone, I at least recommend that you get a GARMIN for your vehicle. A GARMIN makes a trip so much easier.
I was chatting with someone who was on the Garminfone team regarding its cancellation and the future of the Android product, and how it seemed like a no-brainer to me... apparently the powers that be don't think that a standalone Android app would be able to compete with Google Navigation.
ReplyDeleteI guess the Google product is decent, but I cannot use it at all since I got my Garminfone. Google's product lacks the basic features necessary for a proper Navigation app. Want the 3D view and the time remaining? I haven't found a way to do that. The overhead view in Google's product is the way to see the time remaining. When you're in the 3D view, all you get is the time of arrival. That's just one of the problems I have with it.
Instant feedback for corrections, intuitive GUI, massively more diverse and complete integrated products (The "Where To" function).
Make a wrong turn in Google Nav? On my phone, it normally takes more than a block to recalculate the directions. Garmin? Usually less than 5 seconds. Want the carpool entrance in downtown Seattle? Good luck finding it in Google Nav :)
Honestly, there were two problems with the phone:
1) Implemented 1.6 firmware, when 2.1 was already released. Sure, it had the majority of the 2.1 features backported, but there were some apps that wouldn't run on it. Mostly, the consumer complaint was that the number wasn't high enough :)
2) The hardware specs were not adequate. It used the previous generation's CPU and lacked adequate RAM. This was not the fault of the developers... it was due to the batch size of the hardware being relatively small and costing too much. However, doubling the RAM (which would have future-proofed it) would not have been nearly as expensive as scrapping the whole product.
I believe there is still a glimmer of hope that Asus (who still maintains the phone for other carriers) may continue to use it in other phones, which gives the world a glimmer of hope that it may come back here some day.
And, there is community work on it now. Only two of us now, but this guy started the semi-formal documentation and porting efforts.
http://mygarminfone.blogspot.com/2011/05/so-heres-short-how-to-for-compiling.html