Final SDK build available (84853) deadline extended to Tuesday, August 5

by YA » Mon, 14 Jul 2008 22:05:37 GMT


Sponsored Links
 Just got this message --

ADC Entrants,

We're pleased to announce that SDK build 84853 is now available on
your private download site. This will be the last build released for
ADC Round 2 and is the build that you will need to submit your final
application under.

In addition, the final ADC deadline has been extended to Tuesday,
August 5. This is the final ADC deadline.

Thanks!
Android Developer Challenge Team

-- but where is this private download site? Anyone has a link?
--~--~---------~--~----~------------~-------~--~----~



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Seni Sangrujee » Mon, 14 Jul 2008 23:16:55 GMT


 LOL, I got excited when I saw this email, but I'm guessing it was
mistakenly sent to losers. Unless now they're just taunting us for
sport.

-seni



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


Sponsored Links


Final SDK build available (84853) deadline extended to Tuesday, August 5

by plusminus » Tue, 15 Jul 2008 11:59:58 GMT


 xD




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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by plusminus » Tue, 15 Jul 2008 12:01:43 GMT


 but it says "entrants" not "finalists". Anyway it still looks like an
mistake, as I also cannot guess what they mean with "private download
site".





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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Ken Adair » Tue, 15 Jul 2008 14:07:29 GMT


 Got the same email, talk about adding fuel to the fire...






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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Ken Adair » Tue, 15 Jul 2008 14:14:13 GMT


 Wonder how many of us would have actually gotten behind Android if we
knew that they were going to only cater to the top 50. Definitely feel
betrayed....







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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Gies,Brad » Tue, 15 Jul 2008 14:58:38 GMT


  don't think it's anything to worry about, and probably a good thing in the 
long run. Google has selected a small group of very committed Android
developers to help them test the SDK and get it to a final release.

Obviously the people in the top 50 of the Challenge are those that have really
figured out Android, and their feedback will be much more valuable than the
feedback from the community at large. Narrowing the group down to them until
the final release helps to focus resources.

Personally, I have focused on design of my app, and not coding until I see the
final release, so it fits in with my plans perfectly :). Anyone doing coding
now has to expect to redo their code with every release they want their app to
run on, and I don't have the time to do that anyway.




Sincerely,

Brad Gies
-------------------------------------
NLM Software
Southfield, MI, USA
-------------------------------------

If you get today's work done today, but do it in a way that you can't possibly
get tomorrow's work done tomorrow, then you lose.



This e-mail or communication, including any attachments, is intended only for
the person or entity
to which it is addressed and may contain confidential and/or legally privileged
material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received
this message in error, please contact the sender immediately and permanently
delete all copies,
electronic or other, you may have or from your computer. Any disclosure,
copying, distribution,
reliance or use of the contents or information received in error is strictly
prohibited.
The foregoing applies even if this notice is imbedded in a message that is
forwarded or attached.

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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Ken Adair » Tue, 15 Jul 2008 15:20:18 GMT


  agree that those in the top 50 will add some very beneficial
feedback. However, I think it's silly to think those top 50 have some
superior understanding of Android. I have seen a few other
applications that didn't make it into the top 50 that were much more
complex and entertaining to boot. We don't know why Google selected
the winners they did. I'm sure there were underlying business concerns
involved and not just the complexity or quality of an application.
Obviously the winners have a leg up now and I'm sure they know much
more than the rest of us, but that's all because of Google.

Anyways, I don't think the biggest issue here is who has and doesn't
have access to the SDK. I think the main issue here is communication
or lack there of. Google embraced the development community and touted
how they were going to build this platform with the help of the
development community. Somewhere along the lines this "seemed" to
change. I say seemed because this could have always been part of
Google's strategy.

The problem is they have failed to nurture the relationship with the
development community. They have cut them off from the information
that was once flowing and left them to speculate and wonder. In
response, you are seeing many that feel cheated and betrayed. Google
can fix this before it's too late, but they need to act quickly. It's
ALL about communication.

On Jul 15, 10:58am, "Gies,Brad" <[EMAIL PROTECTED]> wrote:
--~--~---------~--~----~------------~-------~--~----~



Final SDK build available (84853) deadline extended to Tuesday, August 5

by John P. » Tue, 15 Jul 2008 15:39:52 GMT


 I got the same email.  I'm guessing that the email was intended for
ADC Round 2 entrants because
  1.  There's no need to notify the extension to others.  Sure, it's
interesting for us to know, but we don't have a *need* to know.
  2.  I'm not aware of any "private download site" either.  However,
previous posts suggest that Round 1 winners will have private access
to the latest SDK.

Of course, I could be wrong and there really is a private download
site for all entrants.

John P.




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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Michael Martin - MM Agency » Tue, 15 Jul 2008 15:39:53 GMT


 This is just for the 50 developers that made it into Round 2.

Michael Martin
Google And Blog
 http://www.googlandblog.com/ 

-----Original Message-----
From: YA [EMAIL PROTECTED] 
Sent: Monday, July 14, 2008 3:05 PM
To: Android Discuss
Subject: [android-discuss] Final SDK build available (84853) deadline
extended to Tuesday, August 5


Just got this message --

ADC Entrants,

We're pleased to announce that SDK build 84853 is now available on
your private download site. This will be the last build released for
ADC Round 2 and is the build that you will need to submit your final
application under.

In addition, the final ADC deadline has been extended to Tuesday,
August 5. This is the final ADC deadline.

Thanks!
Android Developer Challenge Team

-- but where is this private download site? Anyone has a link?




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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by hitsu_g » Tue, 15 Jul 2008 15:40:02 GMT


 I got it too. Is this a goof-up? (I didn't know I was in Round 2 - I'd
better get to work!).




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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Ken Adair » Tue, 15 Jul 2008 17:19:56 GMT


 Google can you hear us??
--~--~---------~--~----~------------~-------~--~----~



Final SDK build available (84853) deadline extended to Tuesday, August 5

by David McLaughlin (Android Advocate) » Tue, 15 Jul 2008 18:27:21 GMT


 Hi everyone,

As some pointed out, I accidentally sent the note concerning ADC Round
2 entrants to the wrong list. Sorry for the annoyance.

Thanks,
David
--~--~---------~--~----~------------~-------~--~----~



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Dan T. » Wed, 16 Jul 2008 16:55:33 GMT


 Thank you for your clarification David.

I'm just happy to hear about a "FINAL" sdk, now we (the non finalist)
know that the sdk isn't anymore in beta testing and you will be able
to release it very quickly to everyone!


I'm not an expert in communication but I think it's much more annoying
for Google and the Android team than for us...

On 15 juil, 20:27, "David McLaughlin (Android Advocate)"



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



Final SDK build available (84853) deadline extended to Tuesday, August 5

by Ken Adair » Thu, 17 Jul 2008 21:03:22 GMT


 Google's secrecy would have most likely received a much different
response should they have started out this way. The problem is when
you provide the SDK along with bundles of information to thousands of
developers, eliciting their help and feedback along the way you set a
certain level of exceptions. It is much harder to take something away
than it is to have never have given it.

I still have the utmost respect for Google and the Android team, but
this was a huge oversight on Google's part. I only hope that they
realize the stress and hardship they have put on those who have
supported them the most.

Best Regards,

Ken



Ken Adair
 http://neevo.com 

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



Other Threads

1. SIGSTKFLT from DefaultHttpClient

I run a set of AsyncTasks that are using the DefaultHttpClient to
access a server. From time to time, I'm seeing the following error,
which appears to be due to some sort of lock contention. This only
happens when I'm driving the system hard (>15 AsyncTasks at once). Is
it possible that the client is timing out waiting for a lock? Do I
need to parcel out the work in batches or is there a system setting I
can adjust to have it done for me?

01-20 17:11:26.321: INFO/dalvikvm(12090): "Binder Thread #1" prio=5
tid=6 NATIVE
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="main" sCount=1
dsCount=0 s=Y obj=0x4476a440 self=0x11e5a0
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12095 nice=0
sched=0/0 cgrp=default handle=1178872
01-20 17:11:26.321: INFO/dalvikvm(12090):   | schedstat=( 304260238
317352301 809 )
01-20 17:11:26.321: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.321: INFO/dalvikvm(12090): "Compiler" daemon prio=5
tid=5 VMWAIT
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="system" sCount=1
dsCount=0 s=N obj=0x44765348 self=0x11fb70
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12094 nice=0
sched=0/0 cgrp=default handle=1172656
01-20 17:11:26.321: INFO/dalvikvm(12090):   | schedstat=( 1851837165
854217465 10038 )
01-20 17:11:26.321: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.321: INFO/dalvikvm(12090): "JDWP" daemon prio=5 tid=4
VMWAIT
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="system" sCount=1
dsCount=0 s=N obj=0x447652a0 self=0x124880
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12093 nice=0
sched=0/0 cgrp=default handle=1172384
01-20 17:11:26.321: INFO/dalvikvm(12090):   | schedstat=( 4089356
2716063 18 )
01-20 17:11:26.321: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.321: INFO/dalvikvm(12090): "Signal Catcher" daemon
prio=5 tid=3 VMWAIT
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="system" sCount=1
dsCount=0 s=N obj=0x447651e8 self=0x125b80
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12092 nice=0
sched=0/0 cgrp=default handle=1152504
01-20 17:11:26.321: INFO/dalvikvm(12090):   | schedstat=( 518799
5676269 2 )
01-20 17:11:26.321: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.321: INFO/dalvikvm(12090): "HeapWorker" daemon prio=5
tid=2 MONITOR
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="system" sCount=1
dsCount=0 s=N obj=0x431a9d80 self=0x126f18
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12091 nice=0
sched=0/0 cgrp=default handle=1251760
01-20 17:11:26.329: INFO/dalvikvm(12090):   | schedstat=( 441986082
367523194 238 )
01-20 17:11:26.329: INFO/dalvikvm(12090):   at
org.apache.harmony.xnet.provider.jsse.OpenSSLSessionImpl.finalize(OpenSSLSessionImpl.java:~460)
01-20 17:11:26.329: INFO/dalvikvm(12090):   - waiting to lock
<0x40012550> (a java.lang.Class) held by threadid=46 (AsyncTask #37)
01-20 17:11:26.329: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.329: DEBUG/dalvikvm(12090): threadid=32: sending two
SIGSTKFLTs to threadid=2 (tid=12091) to cause de{*filter*}d dump
01-20 17:11:28.337: DEBUG/dalvikvm(12090): Sent, pausing to let
de{*filter*}d run
01-20 17:11:28.344: INFO/DEBUG(1003): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
01-20 17:11:28.344: INFO/DEBUG(1003): Build fingerprint: 'verizon/
voles/sholes/sholes:2.2.1/FRG83D/75603:user/release-keys'
01-20 17:11:28.344: INFO/DEBUG(1003): pid: 12090, tid: 12091  >>>
com.quickdroid <<<
01-20 17:11:28.344: INFO/DEBUG(1003): signal 16 (SIGSTKFLT), fault
addr 00002f3a
01-20 17:11:28.344: INFO/DEBUG(1003):  r0 fffffe00  r1 00000080  r2
00000002  r3 00000000
01-20 17:11:28.344: INFO/DEBUG(1003):  r4 002a1ac0  r5 00000002  r6
00000000  r7 000000f0
01-20 17:11:28.344: INFO/DEBUG(1003):  r8 00000002  r9 00000000  10
00126f18  fp 100ffe30
01-20 17:11:28.344: INFO/DEBUG(1003):  ip 805a24c8  sp 100ffaa0  lr
afd103bc  pc afd0eb68  cpsr 80000010
01-20 17:11:28.344: INFO/DEBUG(1003):  d0  643a64696f72646e  d1
6472656767756265
01-20 17:11:28.344: INFO/DEBUG(1003):  d2  448cf948448cf703  d3
448358184478c701
01-20 17:11:28.344: INFO/DEBUG(1003):  d4  448cf7f0448f73d0  d5
4478c758448cf948
01-20 17:11:28.352: INFO/DEBUG(1003):  d6  448132c0447a4ba0  d7
448b4a30447ba858
01-20 17:11:28.352: INFO/DEBUG(1003):  d8  0000000000000000  d9
0000000000000000
01-20 17:11:28.352: INFO/DEBUG(1003):  d10 0000000000000000  d11
0000000000000000
01-20 17:11:28.352: INFO/DEBUG(1003):  d12 0000000000000000  d13
0000000000000000
01-20 17:11:28.352: INFO/DEBUG(1003):  d14 0000000000000000  d15
0000000000000000
01-20 17:11:28.360: INFO/DEBUG(1003):  d16 000000000b0407ba  d17
3fe999999999999a
01-20 17:11:28.360: INFO/DEBUG(1003):  d18 42eccefa43de3400  d19
3fe00000000000b4
01-20 17:11:28.360: INFO/DEBUG(1003):  d20 4008000000000000  d21
3fd99a27ad32ddf5
01-20 17:11:28.360: INFO/DEBUG(1003):  d22 3fd24998d6307188  d23
3fcc7288e957b53b
01-20 17:11:28.360: INFO/DEBUG(1003):  d24 3fc74721cad6b0ed  d25
3fc39a09d078c69f
01-20 17:11:28.368: INFO/DEBUG(1003):  d26 0000000000000000  d27
0000000000000000
01-20 17:11:28.368: INFO/DEBUG(1003):  d28 0000000000000000  d29
0000000000000000
01-20 17:11:28.368: INFO/DEBUG(1003):  d30 0000000000000000  d31
0000000000000000
01-20 17:11:28.368: INFO/DEBUG(1003):  scr 80000012
01-20 17:11:28.516: INFO/DEBUG(1003):          #00  pc 0000eb68  /
system/lib/libc.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #01  pc 000103b8  /
system/lib/libc.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #02  pc 0004d096  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #03  pc 0004d856  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #04  pc 0001775c  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #05  pc 00022794  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #06  pc 00021634  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #07  pc 0005c5cc  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #08  pc 0005c7fc  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #09  pc 0005203e  /
system/lib/libdvm.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #10  pc 000520ca  /
system/lib/libdvm.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #11  pc 000525a0  /
system/lib/libdvm.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #12  pc 0004f9ec  /
system/lib/libdvm.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #13  pc 00010ed4  /
system/lib/libc.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #14  pc 000109c0  /
system/lib/libc.so
01-20 17:11:28.524: INFO/DEBUG(1003): code around pc:
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb48 0afffff7 e8bd4010
e12fff1e e1010090
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb58 e12fff1e e92d0090
e3a070f0 ef000000
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb68 e8bd0090 e12fff1e
e92d0090 e1a03002
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb78 e1a02001 e3a01000
e3a070f0 ef000000
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb88 e8bd0090 e12fff1e
e92d0090 e1a02001
01-20 17:11:28.524: INFO/DEBUG(1003): code around lr:
01-20 17:11:28.524: INFO/DEBUG(1003): afd1039c e3500000 0a00000e
e3560000 e3865002
01-20 17:11:28.524: INFO/DEBUG(1003): afd103ac 03a07080 13a07000
ea000000 ebfff9fb
01-20 17:11:28.524: INFO/DEBUG(1003): afd103bc e1a01004 e1a00005
ebfff9e2 e1a01007
01-20 17:11:28.524: INFO/DEBUG(1003): afd103cc e1a02005 e3a03000
e1560000 e1a00004
01-20 17:11:28.524: INFO/DEBUG(1003): afd103dc 1afffff5 e3a00000
e8bd87f0 ebfffc8a
01-20 17:11:28.524: INFO/DEBUG(1003): stack:
01-20 17:11:28.524: INFO/DEBUG(1003):     100ffa60  afd43724  /system/
lib/libc.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa64  10420e6c
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa68  00000001
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa6c  afd43760  /system/
lib/libc.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa70  100ffad0
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa74  4184ff88
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa78  4184ff74
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa7c  afd0be0d  /system/
lib/libc.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa80  100ffad0
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa84  4184ffa0
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa88  00000018
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa8c  afd43850  /system/
lib/libc.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa90  00126f18  [heap]
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa94  af0943ac  /system/
lib/libcrypto.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa98  df002777
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa9c  e3a070ad
01-20 17:11:28.532: INFO/DEBUG(1003): #00 100ffaa0  002a1ac0  [heap]
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffaa4  00000080
01-20 17:11:28.532: INFO/DEBUG(1003): #01 100ffaa8  002a1ab0  [heap]
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffaac  00000000
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffab0  00126f18  [heap]
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffab4  002a1ac0  [heap]
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffab8  80517000  /system/
lib/libdvm.so
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffabc  00000000
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffac0  00126f18  [heap]
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffac4  8054d099  /system/
lib/libdvm.so
01-20 17:11:29.657: INFO/DEBUG(1003): de{*filter*}d committing suicide to
free the zombie!
01-20 17:11:29.680: INFO/BootReceiver(1085): Copying /data/tombstones/
tombstone_00 to DropBox (SYSTEM_TOMBSTONE)

-- 

2. What to use for user feedback?

Hello everyone,

I'm currently providing user support through email, and I'm thinking about using
a more community-aware web solution. I've known GetSatisfaction for a long time,
never used, but always found it quite smart, although it can get a bit pricey if
you need any advanced features such as moderation.

In an Android blog post, Tim Bray does mention Google Groups, Zoho Discussions,
GetSatisfaction and UserVoice:
http://android-developers.blogspot.com/2010/10/improving-app-quality.html

Google Groups doesn't really fit the job IMO, it's not very practical from a
phone, and it's not as user-frienly as the other solutions. But even with
GetSatisfaction, I'm not sure that it's very practical on a phone.

But what do you guys use for user feedback?

Any open source web app optimized for both phone and standard browsers? Anything
with something as intuitive as the Question/Idea/Problem system in 
GetSatisfaction?

I have looked at OpenMind (RoR), but it seems a bit technical, not adequate for
an average user.

I've also considered vBulletin or similar forums, which seem quite popular,
considering the success of android forums website out there. And there is this
nice Tapatalk app, which is compatible with several forums systems, but Tapatalk
is a paid app, and that's a bit of overhead for simple user feedback.

TIA for your ideas

--
  Olivier



-- 
.

3. newbie - contact journey td sync?

4. Solved - Error install aplikSi

5. Build.SERIAL deprecated?

6. ListAdapter design advice

7. Does Any one Building Android source code in Mac