Why such a long gap between G1 and the next Android phones?

by admin.androidsl...@googlemail.com » Mon, 27 Apr 2009 22:25:11 GMT


Sponsored Links
 Definitely more than meets the eye here. After all, if HTC had the
technology so long ago, why is it taking other handset companies so
long?

My theories :
1. The other companies are not prepared to invest money and resources
until they can see Android is looking likely to be a success
2. Some kind of exclusivity contract between T-Mobile and HTC
3. Delay of Cupcake release meaning only handsets with physical
keyboard can work with current SDK

ok so that's all I can come up with for now, but how does everyone
else explain this enigma?

After all the Android platform was launched on the premise of multiple
handsets and multiple devices.

Its kind of hard to convince your mate to buy an Android phone when
all you can show him is a brick.
--~--~---------~--~----~------------~-------~--~----~



Why such a long gap between G1 and the next Android phones?

by lbcoder » Mon, 27 Apr 2009 22:40:33 GMT


 2 is not applicable since non-tmobile/non-htc are not affected. 1 is
definitely applicable -- if its an instant flop, then its not a good
investment. 3 -- is partially applicable - it is not a particularly
complex feature and could be added on a whim as needed.

And if you bricked your phone, why would you show it off... thats like
running around with your pants down yelling out "I'm dumb". You do
know what the word 'brick' means when applied to a phone, don't you?
It means that you damaged the firmware and don't know how to fix it.



On Apr 27, 10:25am, "admin.androidsl...@googlemail.com"


--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Why such a long gap between G1 and the next Android phones?

by admin.androidsl...@googlemail.com » Mon, 27 Apr 2009 22:43:07 GMT


 Wasn't aware of the alternative 'brick' terminology.

I meant the G1 looks like a brick! Kind of like how handsets 10 years
ago did.

iPhone is stunning in comparison and believe me, looks DO matter in
this market!





--~--~---------~--~----~------------~-------~--~----~



Why such a long gap between G1 and the next Android phones?

by Mark » Tue, 28 Apr 2009 07:36:52 GMT


 FYI, A number of vendors are invseting significant resources in
developing their own Android devices, it's kept a lot of us very busy.
It just takes time to develop all the hardware, software etc. HTC did
get the G1 out the door quickly, but the new models will be more
powerful and have a lot more features, it just all takes time.

         M

On Apr 27, 7:42am, "admin.androidsl...@googlemail.com"




--~--~---------~--~----~------------~-------~--~----~



Why such a long gap between G1 and the next Android phones?

by Eric Wong (hdmp4.com) » Wed, 29 Apr 2009 06:03:45 GMT


 Mark,

I partly disagree with this. If the manufacturers are desperate, they
could simply port Android to one of their existing handsets. There is
real reason that they must invest money and resources to build a new
phone entirely, it is kinda a waste of money.

However, today, no one except a handful of China manufacturer do this.

Cheers
Eric






--~--~---------~--~----~------------~-------~--~----~



Why such a long gap between G1 and the next Android phones?

by lbcoder » Wed, 29 Apr 2009 21:20:08 GMT


 The fruity POS you mention does NOT look like anything special. Its
just a rectangular box with rounded edges/corners. Nothing special at
all. I can't imagine how you could thing that it looks
"stunning"... ???

On Apr 27, 10:42am, "admin.androidsl...@googlemail.com"




--~--~---------~--~----~------------~-------~--~----~



Why such a long gap between G1 and the next Android phones?

by Incognito » Thu, 30 Apr 2009 00:20:03 GMT


 If only your opinion were the only one that counted. 





The fruity POS you mention does NOT look like anything special. Its
just a rectangular box with rounded edges/corners. Nothing special at
all. I can't imagine how you could thing that it looks
"stunning"... ???

On Apr 27, 10:42 am, "admin.androidsl...@googlemail.com"


Wasn't aware of the alternative 'brick' terminology.

I meant the G1 looks like a brick! Kind of like how handsets 10 years
ago did.

iPhone is stunning in comparison and believe me, looks DO matter in
this market!




2 is not applicable since non-tmobile/non-htc are not affected. 1 is
definitely applicable -- if its an instant flop, then its not a good
investment. 3 -- is partially applicable - it is not a particularly
complex feature and could be added on a whim as needed.

And if you bricked your phone, why would you show it off... thats like
running around with your pants down yelling out "I'm dumb". You do
know what the word 'brick' means when applied to a phone, don't you?
It means that you damaged the firmware and don't know how to fix it.

On Apr 27, 10:25 am, "admin.androidsl...@googlemail.com"



Definitely more than meets the eye here. After all, if HTC had the
technology so long ago, why is it taking other handset companies so
long?

My theories :
1. The other companies are not prepared to invest money and resources
until they can see Android is looking likely to be a success
2. Some kind of exclusivity contract between T-Mobile and HTC
3. Delay of Cupcake release meaning only handsets with physical
keyboard can work with current SDK

ok so that's all I can come up with for now, but how does everyone
else explain this enigma?

After all the Android platform was launched on the premise of multiple
handsets and multiple devices.

Its kind of hard to convince your mate to buy an Android phone when
all you can show him is a brick.






      


--~--~---------~--~----~------------~-------~--~----~



Why such a long gap between G1 and the next Android phones?

by lbcoder » Thu, 30 Apr 2009 01:03:50 GMT


 This isn't a question of opinion. The problem is marketing, not shape.
Its that stupid picture of an apple on the back that makes the feeble-
minded think that its something special and therefore everything that
doesn't look exactly like it is "ugly" and everything that looks
*like* it is a COPY and therefore a fraud. That is the thing that
absolutely drives me nuts -- apple isn't about appearance, it isn't
about function, it isn't about performance, its about SOCIAL
CONFORMITY -- which is completely unrelated to the actual point.







--~--~---------~--~----~------------~-------~--~----~



Why such a long gap between G1 and the next Android phones?

by Incognito » Thu, 30 Apr 2009 01:11:37 GMT


 Again, opinion. I respect it though.





This isn't a question of opinion. The problem is marketing, not shape.
Its that stupid picture of an apple on the back that makes the feeble-
minded think that its something special and therefore everything that
doesn't look exactly like it is "ugly" and everything that looks
*like* it is a COPY and therefore a fraud. That is the thing that
absolutely drives me nuts -- apple isn't about appearance, it isn't
about function, it isn't about performance, its about SOCIAL
CONFORMITY -- which is completely unrelated to the actual point.



If only your opinion were the only one that counted.




The fruity POS you mention does NOT look like anything special. Its
just a rectangular box with rounded edges/corners. Nothing special at
all. I can't imagine how you could thing that it looks
"stunning"... ???

On Apr 27, 10:42 am, 



Wasn't aware of the alternative 'brick' terminology.

I meant the G1 looks like a brick! Kind of like how handsets 10 years
ago did.

iPhone is stunning in comparison and believe me, looks DO matter in
this market!




2 is not applicable since non-tmobile/non-htc are not affected. 1 is
definitely applicable -- if its an instant flop, then its not a good
investment. 3 -- is partially applicable - it is not a particularly
complex feature and could be added on a whim as needed.

And if you bricked your phone, why would you show it off... thats like
running around with your pants down yelling out "I'm dumb". You do
know what the word 'brick' means when applied to a phone, don't you?
It means that you damaged the firmware and don't know how to fix it.

On Apr 27, 10:25 am, "admin.androidsl...@googlemail.com"




Definitely more than meets the eye here. After all, if HTC had the
technology so long ago, why is it taking other handset companies so
long?

My theories :
1. The other companies are not prepared to invest money and resources
until they can see Android is looking likely to be a success
2. Some kind of exclusivity contract between T-Mobile and HTC
3. Delay of Cupcake release meaning only handsets with physical
keyboard can work with current SDK

ok so that's all I can come up with for now, but how does everyone
else explain this enigma?

After all the Android platform was launched on the premise of multiple
handsets and multiple devices.

Its kind of hard to convince your mate to buy an Android phone when
all you can show him is a brick.




      


--~--~---------~--~----~------------~-------~--~----~



Why such a long gap between G1 and the next Android phones?

by Mark » Thu, 30 Apr 2009 06:14:02 GMT


 es , I'm obviously imagining that me and a significant size
developement team are working on a new products. Sorry, my bad.

M

On Apr 28, 3:03pm, "Eric Wong (hdmp4.com)" <ericwon...@gmail.com>
wrote:
--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Pending intent not detecting onCreate

I have the following code in a static function in my application
widget:

                Intent defineIntent = new Intent(context,
ToggleIntentActivity.class);
                PendingIntent pendingIntent = PendingIntent
                                .getActivity(context, 0, defineIntent, 0);

                views.setOnClickPendingIntent(R.id.icon, pendingIntent);

                // Tell the widget manager
                appWidgetManager.updateAppWidget(appWidgetId, views);

custom activity's based on user clicks on your widgets. However even
though Logcat says Starting Activity: Intent {......} my activities on
create function never gets called!

Note my Activity is as follows:

public class ToggleIntentActivity extends Activity {
        @Override
        protected void onCreate(Bundle savedInstanceState) {
                super.onCreate(savedInstanceState);
                Log.e(QuickerCutWidgetManager.TAG, "On create");
        }
}


Any ideas?
--~--~---------~--~----~------------~-------~--~----~

2. Spry onload command

Have added a IU that is fading one image to the next with Spry at
onload.  Only getting black screen on ADP1.
--~--~---------~--~----~------------~-------~--~----~

3. Build OpenCORE outside of Android

4. upgraded to 1.5 and apps wont run

5. Regarding AbsoluteView being deprecated in 1.5

6. Status bar in screen

7. switch / if statement, efficiency question