Where have all the Google employees gone?

17 views
Skip to first unread message

bellapariah

unread,
Oct 6, 2009, 9:49:09 PM10/6/09
to Android Discuss
Thread for developers to discuss problems with 1.6 update and effects
on ADC2. If you see other forums or articles on the issue or if you
are one of the unlucky developers affected by the the untimely 1.6
update, please post is here!

Releasing 1.6 in the middle of a contest is unacceptable. According to
the official terms and conditions:

"a. SUBMISSION OF ENTRIES: To qualify for a Prize, an "Entry" to the
Challenge consists of an original application that is written using a
version of the Android Software Development Kit ("SDK") (available at
http://developer.android.com) that validly executes on Android version
1.5. The SDK contains instructions, documentation, and all necessary
tools to enable a Participant to build an Android application."

Mine as well as many other ADC2 apps worked fine on 1.5 but started
"force closing" after the 1.6 update. Programmers were told to develop
an application for 1.5, not 1.6, and were not given the tools or
opportunity to test our apps with 1.6. In my case, I have had 95
people test my app for Round 1 judging, but 27 of those were "force
closes" due to the 1.6 update. This is because of an issue with a
Google API that was updated with 1.6. Here are links to other people
experiencing issues with the new platform, and some are for things as
simple as rotating the phone, so it is not an isolated issue.


http://groups.google.com/group/android-discuss/browse_thread/thread/7373e1f622320971/035b0786ea8528f3?hl=en#035b0786ea8528f3

http://groups.google.com/group/android-discuss/browse_thread/thread/a393540199f71516?hl=en#

http://groups.google.com/group/android-discuss/browse_thread/thread/5ff4dbce3701b73b?hl=en#

http://groups.google.com/group/android-developers/browse_thread/thread/769e382ba77c7b29/f56d1f9adc95f01d?hl=en&lnk=gst&q=adc#f56d1f9adc95f01d

http://www.google.com/support/forum/p/Android+Market/thread?tid=5d754065b064e134&hl=en

http://androidandme.com/2009/10/news/did-google-fumble-the-android-1-6-launch/

http://polyclefsoftware.blogspot.com/


One suggestion would be to remove the last 25% of reviews of every app
in the contest (the ones most likely to have been affected by 1.6
upgrades) to reduce the negative effects of the 1.6 release.

Shelby
Message has been deleted

Felipemnoa

unread,
Oct 7, 2009, 12:45:58 AM10/7/09
to android...@googlegroups.com
My app has not been getting any hits since yesterday. It used to be
getting plenty of hits before that. I have not tested it on 1.6 yet
but i can only assumed it is because of it.

On Oct 6, 2009, at 9:59 PM, bellapariah <bella...@gmail.com> wrote:

>
> What is Google just dropped the 25 lowest scores for every app? There
> would still be 75 reviews to give a relatively accurate average rating
> and it would be fair for all without giving benefits to select
> developers.
>
> On Oct 6, 6:49 pm, bellapariah <bellapar...@gmail.com> wrote:
>> Thread for developers to discuss problems with 1.6 update and effects
>> on ADC2. If you see other forums or articles on the issue or if you
>> are one of the unlucky developers affected by the the untimely 1.6
>> update, please post is here!
>>
>> Releasing 1.6 in the middle of a contest is unacceptable. According
>> to
>> the official terms and conditions:
>>
>> "a. SUBMISSION OF ENTRIES: To qualify for a Prize, an "Entry" to the
>> Challenge consists of an original application that is written using a
>> version of the Android Software Development Kit ("SDK") (available
>> athttp://developer.android.com) that validly executes on Android
>> version
>> 1.5. The SDK contains instructions, documentation, and all necessary
>> tools to enable a Participant to build an Android application."
>>
>> Mine as well as many other ADC2 apps worked fine on 1.5 but started
>> "force closing" after the 1.6 update. Programmers were told to
>> develop
>> an application for 1.5, not 1.6, and were not given the tools or
>> opportunity to test our apps with 1.6. In my case, I have had 95
>> people test my app for Round 1 judging, but 27 of those were "force
>> closes" due to the 1.6 update. This is because of an issue with a
>> Google API that was updated with 1.6. Here are links to other people
>> experiencing issues with the new platform, and some are for things as
>> simple as rotating the phone, so it is not an isolated issue.
>>
>> http://groups.google.com/group/android-discuss/browse_thread/thread/
>> 7...
>>
>> http://groups.google.com/group/android-discuss/browse_thread/thread/
>> a...
>>
>> http://groups.google.com/group/android-discuss/browse_thread/thread/
>> 5...
>>
>> http://groups.google.com/group/android-developers/browse_thread/
>> threa...
>>
>> http://www.google.com/support/forum/p/Android+Market/thread?
>> tid=5d754...
>>
>> http://androidandme.com/2009/10/news/did-google-fumble-the-
>> android-1-...

Al Sutton

unread,
Oct 7, 2009, 2:40:44 AM10/7/09
to android...@googlegroups.com
You really should subscribe to Googles Android Developers blog;

http://android-developers.blogspot.com/2009/10/adc-2-round-1-scoring-complete.html

Al.
--

* Looking for Android Apps? - Try http://andappstore.com/ *

======
Funky Android Limited is registered in England & Wales with the
company number 6741909. The registered head office is Kemp House,
152-160 City Road, London, EC1V 2NX, UK.

The views expressed in this email are those of the author and not
necessarily those of Funky Android Limited, it's associates, or it's
subsidiaries.

String

unread,
Oct 7, 2009, 3:13:43 AM10/7/09
to Android Discuss
Re: Where have all the Google employees gone?

I noticed that they all but stopped participating in Android-Discuss
right after some bonehead posted a link to a patent that JBQ had
SPECIFICALLY asked them not to. The explanation was that it's legally
dangerous for Google employees to participate in a group which
discusses patents, in case they end up infringing on one. So I suspect
we can thank that particular bonehead for removing Google folks from
this group.

String

Jean-Baptiste Queru

unread,
Oct 7, 2009, 8:38:15 AM10/7/09
to android...@googlegroups.com
Some of us are still reading (I know I'm not the only one), but ADC2
is an area that is too sensitive for "plain engineers" to make
comments about on a casual mailing list.

This is the time of the year where it's hard to dedicate much time to
mailing lists, as the focus is on finalizing phones for the holiday
shopping season.

Indeed, as you mentioned, each instance of discussions about patents
causes employees of many companies working in the general area of that
patent to feel uncomfortable and eventually leave. The case you have
in mind was especially bad.

JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, 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
warning.

bellapariah

unread,
Oct 7, 2009, 1:09:49 PM10/7/09
to Android Discuss
My app broke as a result of an Android API throwing a proactive
IllegalStateException in 1.6. While this is a good inclusion for those
developing on 1.6, it was not documented or required in 1.5, and
therefore may break 1.5 apps that have not been able to test in 1.6
and fix app for the new exception. My app has been tested for extended
periods of heavy use for 1.5 and never ran into the problem Google is
trying to safeguard against (my app runs great in 1.5 which is what we
were told to develop for) so I was unaware that the issue existed
until I was able to test it on 1.6.

From the stats my app collects, I am able to see that ~30% of the
contest graders were running 1.6 over the period of the contest.... So
I can probably assume that 30% of my end grade was lost. :(

BTW...thank you Jean-Baptiste for writing in the forum. Its good to
know that someone is at least listening to our concerns (even if they
aren't addressing them.) :)-

Shelby

On Oct 6, 6:49 pm, bellapariah <bellapar...@gmail.com> wrote:
> Thread for developers to discuss problems with 1.6 update and effects
> on ADC2. If you see other forums or articles on the issue or if you
> are one of the unlucky developers affected by the the untimely 1.6
> update, please post is here!
>
> Releasing 1.6 in the middle of a contest is unacceptable. According to
> the official terms and conditions:
>
> "a. SUBMISSION OF ENTRIES: To qualify for a Prize, an "Entry" to the
> Challenge consists of an original application that is written using a
> version of the Android Software Development Kit ("SDK") (available athttp://developer.android.com) that validly executes on Android version
> 1.5. The SDK contains instructions, documentation, and all necessary
> tools to enable a Participant to build an Android application."
>
> Mine as well as many other ADC2 apps worked fine on 1.5 but started
> "force closing" after the 1.6 update. Programmers were told to develop
> an application for 1.5, not 1.6, and were not given the tools or
> opportunity to test our apps with 1.6. In my case, I have had 95
> people test my app for Round 1 judging, but 27 of those were "force
> closes" due to the 1.6 update. This is because of an issue with a
> Google API that was updated with 1.6. Here are links to other people
> experiencing issues with the new platform, and some are for things as
> simple as rotating the phone, so it is not an isolated issue.
>
> http://groups.google.com/group/android-discuss/browse_thread/thread/7...
>
> http://groups.google.com/group/android-discuss/browse_thread/thread/a...
>
> http://groups.google.com/group/android-discuss/browse_thread/thread/5...
>
> http://groups.google.com/group/android-developers/browse_thread/threa...
>
> http://www.google.com/support/forum/p/Android+Market/thread?tid=5d754...
>
> http://androidandme.com/2009/10/news/did-google-fumble-the-android-1-...

Felipe (Noa Technologies)

unread,
Oct 8, 2009, 9:54:46 AM10/8/09
to Android Discuss
I finally figured out why my app just stopped receiving hits. The
contest is over! Congratulations to those that make it through.

On Oct 7, 12:45 am, Felipemnoa <felipem...@yahoo.com> wrote:
> My app has not been getting any hits since yesterday. It used to be  
> getting plenty of hits before that. I have not tested it on 1.6 yet  
> but i can only assumed it is because of it.
>

Thomas Jørgensen

unread,
Oct 8, 2009, 6:42:34 AM10/8/09
to Android Discuss
Hi all

After updating to 1.6 we got a force close error in our ADC2
application Gigbox. We were able to quickly fix the error and post an
update to the Android Market. Should we make it to the second round of
ADC2, then our application is limited in functionality, and it will
not be posible to judge it fairly on 1.6 devices.

We are aware that the official terms and conditions leave no options
to deal with this case. But we do hope that Google will try to address
this issue one way or another, even though there is no optimal
solution that will benefit us all.
From our point of view, the first round of ADC2 has been fair and
equal. The first round was stopped before too many handsets were
updated with 1.6. In order to make the second round fair, we think
that the optimal solution would be to allow updates to the
applications, in order to correct 1.6 related issues. New features
shouldn't be allowed.

Best regards,
Gigbox Team

Btw: Shelby, what about changing the title for this thread to be more
specific towards the ADC2 and 1.6 issues insted of Google employees?
Message has been deleted

Shelby Troxell

unread,
Oct 8, 2009, 3:12:55 PM10/8/09
to android...@googlegroups.com
Sure. The point of the title was to catch attention and try to consolidate all the conversations regarding 1.6 issues into one location since their are many threads with similar names. Also, I've been very disappointed that no one from Google will make a statement about the issue, or post in the forums in general. Sorry to hear about Gigbox. Ours was Amoeba Blackjack and is in the same situation.

Shelby

Hong

unread,
Oct 8, 2009, 3:55:39 PM10/8/09
to android...@googlegroups.com
Shelby and Thomas, can you elaborate more on the force closes issues?
Specifically, what API/methods broke from 1.5 to 1.6?

Thanks

bellapariah

unread,
Oct 9, 2009, 1:16:25 PM10/9/09
to Android Discuss
Hi Hong,

Here are the details of the 1.6 change that is causing my app to not
work properly:

2009-05-20 Jean-Baptiste Queru donut snapshot

http://android.git.kernel.org/?p=platform/frameworks/base.git;a=history;f=core/java/android/os/RemoteCallbackList.java;hb=a8675f67e33bc7337d148358783b0fd138b501ff

RemoteCallbackList.java:

http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blobdiff;f=core/java/android/os/RemoteCallbackList.java;h=584224fccc8b0959a2580a14411536855b1423cc;hp=23c0a7bf473c48c2c93f6f4d9f97881a3c1315cd;hb=a8675f67e33bc7337d148358783b0fd138b501ff;hpb=843ef36f7b96cc19ea7d2996b7c8661b41ec3452

@@ -222,7 +224,12 @@ public class RemoteCallbackList<E extends
IInterface> {

public int beginBroadcast() {
synchronized (mCallbacks) {
- final int N = mCallbacks.size();
+ if (mBroadcastCount > 0) {
+ throw new IllegalStateException(
+ "beginBroadcast() called while already in a
broadcast");
+ }
+
+ final int N = mBroadcastCount = mCallbacks.size();
if (N <= 0) {
return 0;
}

1.6 will throw this exception to let developers know if one of their
calls to beginBroadcast() was not terminated w/ a call to
finishBroadcast(). In 1.5, not calling finishBroadcast() is unchecked,
and although this is a programming mistake, my app, and probably
several others, can still operate in 1.5 without any noticeable
consequence. This sort of thing is easily seen and corrected within 5
- 10 minutes of testing on 1.6, but, of course, we weren't given the
1.6 update to test with for the contest.

Shelby

On Oct 8, 12:55 pm, Hong <lordh...@gmail.com> wrote:
> Shelby and Thomas, can you elaborate more on the force closes issues?
> Specifically, what API/methods broke from 1.5 to 1.6?
>
> Thanks
>
> On Thu, Oct 8, 2009 at 3:12 PM, Shelby Troxell <bellapar...@gmail.com>wrote:
>
>
>
> > Sure. The point of the title was to catch attention and try to consolidate
> > all the conversations regarding 1.6 issues into one location since their are
> > many threads with similar names. Also, I've been very disappointed that no
> > one from Google will make a statement about the issue, or post in the forums
> > in general. Sorry to hear about Gigbox. Ours was Amoeba Blackjack and is in
> > the same situation.
> > Shelby
>
Reply all
Reply to author
Forward
0 new messages