Comments on: DEXT, BACKFLIP & QUENCH video demo http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/ Canadian Mobile Phone News & Reviews - Cell phones and Accessories Fri, 25 May 2012 23:59:34 +0000 hourly 1 http://wordpress.org/?v= By: Raymond http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-59232 Raymond Fri, 16 Jul 2010 17:39:38 +0000 http://mobilesyrup.com/?p=19787#comment-59232 this is under the featured contest section but i dont see any where i can win this phone, putting my name in just in case.. haha this is under the featured contest section but i dont see any where i can win this phone, putting my name in just in case.. haha

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: m http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-51823 m Tue, 01 Jun 2010 15:17:03 +0000 http://mobilesyrup.com/?p=19787#comment-51823 JK, the incentive to OEM is more devices sold... if the market hysteria of having the latest version of Android (without having any idea of what it actually means... - to your point) is what sells devices, then that's what sells... JK, the incentive to OEM is more devices sold… if the market hysteria of having the latest version of Android (without having any idea of what it actually means… – to your point) is what sells devices, then that’s what sells…

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: Wade http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-49910 Wade Fri, 14 May 2010 06:36:31 +0000 http://mobilesyrup.com/?p=19787#comment-49910 The Dext looks remarkably like the Moto Cliq from T-Mobile. Looks nice, feels nice, works well when it works, and has a new batch of known issues each week. I still would love to win one. The Dext looks remarkably like the Moto Cliq from T-Mobile. Looks nice, feels nice, works well when it works, and has a new batch of known issues each week. I still would love to win one.

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: JW http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-49573 JW Fri, 07 May 2010 15:19:31 +0000 http://mobilesyrup.com/?p=19787#comment-49573 Will it be possible to wipe the Dext and install a more recent and "plain-jane" (not MOTOBLUR) Android version? (I am new to this) Will it be possible to wipe the Dext and install a more recent and “plain-jane” (not MOTOBLUR) Android version?

(I am new to this)

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: Don http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-47682 Don Tue, 20 Apr 2010 16:39:47 +0000 http://mobilesyrup.com/?p=19787#comment-47682 This sucks. Can't we get one good Android phone on Bell. And I really don't want to spend $600 on a Nexus One. This sucks. Can’t we get one good Android phone on Bell. And I really don’t want to spend $600 on a Nexus One.

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: Alex F http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-46415 Alex F Fri, 09 Apr 2010 14:49:38 +0000 http://mobilesyrup.com/?p=19787#comment-46415 Oh crap! Ian you were at the launch and I didn't even get to introduce myself. I should have been reading name tags more carefully. Oh crap! Ian you were at the launch and I didn’t even get to introduce myself.
I should have been reading name tags more carefully.

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: JK http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-46409 JK Fri, 09 Apr 2010 13:24:03 +0000 http://mobilesyrup.com/?p=19787#comment-46409 However, there is no real reason to not release on current OS, unless the OEM is taking advantage of a bigger countries code release and saving on the R&D costs. My dialogue above only suggests the OEMs resistance to upgrade in a timely manner. However, there is no real reason to not release on current OS, unless the OEM is taking advantage of a bigger countries code release and saving on the R&D costs. My dialogue above only suggests the OEMs resistance to upgrade in a timely manner.

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: JK http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-46384 JK Thu, 08 Apr 2010 20:32:17 +0000 http://mobilesyrup.com/?p=19787#comment-46384 As someone in the industry I am often interested to understand why compare 1.5 and 1.6, it sounds like an arbitrary issue. I am not sure the upgrades in donut are that noticable and it really depends on the price points in determining the functional utility to pricing curve, it is only sad if you overpay. The major issue is that upgradeability of Android seems impaired on all OEM vendors which in my line of thinking points to a fundamental breakdown in business model between the OEM, Carrier and OS provider as there is no incentive to stay current for the OEM. My reccomendation to carriers and Google would be to separate the radio code from the application stack in a modular way that would remove the need for carriers/OEMs to re-write/re-certify the new code. This would mean users could update independant of the certification process at google.com and OEMs wouldn't be wasting additional money/engineering resources on non-revenue generating activity. Remember with Android OEMs don't make additional money the longer you use the device, they only create brand loyalty (unlike RIM/Apple who get additional Cash Flow). Only Carriers and Google get paid with Android on an ongoing basis. Therefore it is an agency incentive issue that needs to be systematically resolved for the Device manufacturer to invest. Thoughts? As someone in the industry I am often interested to understand why compare 1.5 and 1.6, it sounds like an arbitrary issue. I am not sure the upgrades in donut are that noticable and it really depends on the price points in determining the functional utility to pricing curve, it is only sad if you overpay.

The major issue is that upgradeability of Android seems impaired on all OEM vendors which in my line of thinking points to a fundamental breakdown in business model between the OEM, Carrier and OS provider as there is no incentive to stay current for the OEM.

My reccomendation to carriers and Google would be to separate the radio code from the application stack in a modular way that would remove the need for carriers/OEMs to re-write/re-certify the new code. This would mean users could update independant of the certification process at google.com and OEMs wouldn’t be wasting additional money/engineering resources on non-revenue generating activity.

Remember with Android OEMs don’t make additional money the longer you use the device, they only create brand loyalty (unlike RIM/Apple who get additional Cash Flow). Only Carriers and Google get paid with Android on an ongoing basis. Therefore it is an agency incentive issue that needs to be systematically resolved for the Device manufacturer to invest.

Thoughts?

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: Erik Berkun-Drevnig http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-46382 Erik Berkun-Drevnig Thu, 08 Apr 2010 19:24:22 +0000 http://mobilesyrup.com/?p=19787#comment-46382 ROFL not even 1.6 ROFL not even 1.6

Like or Dislike: Thumb up 0 Thumb down 0

]]> By: theninjasquad http://mobilesyrup.com/2010/04/08/motorola-dext-backflip-and-quench-video-demo/#comment-46381 theninjasquad Thu, 08 Apr 2010 19:11:00 +0000 http://mobilesyrup.com/?p=19787#comment-46381 Companies should be embarrassed to be launching new Android phones with v1.5 nowadays. That's just sad. Companies should be embarrassed to be launching new Android phones with v1.5 nowadays. That’s just sad.

Like or Dislike: Thumb up 0 Thumb down 0

]]>