New G1 RC33 update

by DLaw » Sat, 14 Mar 2009 02:12:08 GMT

Sponsored Links
 Has anyone recently gotten a G1 (after the mass rollout of RC33) only
to find that it doesn't have RC33 and doesn't pull it down after
purchase?  I just got a phone 2 days ago but I'm wanting to use it for
development but it still hasn't pulled the RC33 update.  Anyone have
similar experience and how long did it take for it to finally show

Just to re-iterate I'm looking for people who bought their G1 after
the mass rollout of RC33 in February.



New G1 RC33 update

by Jean-Baptiste Queru » Sat, 14 Mar 2009 02:57:46 GMT

 It typically takes a few days for new devices to receive their first
update (if relevant). 2 days is definitely within the range of that
initial delay. One week would be unusual, but you're not at that point

If you're impatient about receiving this update, I'd suggest that
whenever possible you keep the phone plugged in in an area with good


Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further


Sponsored Links

Other Threads

1. Tell me why I should sell my iphone and buy android

Halo Bos/Bis,

Sekarang saya pakai iphone, tapi lagi napsu dengan Android. Saya mau jual
iphone dan ganti HTC Desire, tapi takut nyesel. Tolong yakinkan saya kenapa
HTC Android lebih bagus dari iphone. Kenapa HTC Android lebih worth it. Saya
cuma takut nyesel. Yang saya tau pasti, kalau soal game iphone masih lebih

Dan untuk Bos2 yang udah pernah pakai dua duanya, gimana pengalamannya?

Terima kasih.


"Indonesian Android Community [id-android]" 

2. Installing binaries on device for testing

I'm working on porting an existing C++ shared library to Android, and
I'm wondering if there's a simple, well-defined way to ask the build
system to install a set of libraries and executables from my project
onto my device for testing.  Right now I have a shared library and a
bunch of test programs that link with it, and I want to do something
similar to "make install" to test everything on the device.

Here's a glance at my thought process on this:

1) I could use "adb sync" to copy the libs and executables each time I
rebuild them, but I think this would involve copying the entire
contents of /system once, which I'd prefer to avoid.
2) I could copy the individual files to the right destinations with
"adb push", but this is tedious.
3) I could write a script to "adb push" all the files I need, but
managing the building and dependencies and path configuration and all
that... feels like it should be part of the build system.
4) ...perhaps it is part of the build system?  Something like the
"install" target for every OSS source-distributed project ever.  I
couldn't find any clues, however, grepping through the build/
directory in my Android source tree.
5) ...or maybe I would have to hack it into the build system, adding
support for something like "make devinstall-$(LOCAL_MODULE)", similar
to the clean-$(LOCAL_MODULE) targets?

The dev phone I have to work with is running Android 1.5, so I've used
the android-1.5 branch when doing "repo init".  This might be relevant
if something like this has been added in later versions of the

On a related note, if I have a single with several
LOCAL_MODULEs, is there a way to define a quick shorthand to do a
*clean* build on all those modules?  I can hack it with a one-liner
shell script, but if the build system supports something like that, it
might give me a clue about how to proceed with my first question.
(The first time I wanted to do this, I tried "mm clean", which sadly
did a "make clean" in the root directory, meaning I had to rebuild the
tree to recreate the necessary build tools and libraries.)


3. Suggestions - Study on Android development

4. Anyone Have Working Files for HelloMapView ?

5. Live stream latency

6. Binding spinner to a list of custom objects

7. cuztomized ListView