[android-developers] Re: Where have all the Google employees gone?
Hi Dianne, can you elaborate on that? What exactly has changed? How do you determine what is in the foreground? Is the 5% distributed equally among the background apps? And it only means that there is a 5% cap for the background apps if there is actually a foreground thread asking for juice right? Great to see work in that area! A bit unrelated, but do you see work in the are of the Dalvik VM, e.g. gc? Is the Donut VM the same as in Android 1.1? On Wed, Oct 7, 2009 at 6:23 AM, Dianne Hackborn wrote: > On Tue, Oct 6, 2009 at 9:13 PM, Maps.Huge.Info (Maps API Guru) < > cor...@gmail.com> wrote: > >> The new market app shows the screen shots that can be uploaded, so >> it's a nice update. There seems to be a lot of small changes and (this >> could be my imagination) the phone seems to run faster an smoother. >> > > There was a bunch of work done on thread scheduling to ensure that all > background apps together couldn't use more than a small fraction (I believe > we ended up with 5%) of the time that the foreground threads want. It makes > a big difference for example when background syncs are running. > > Glad it's noticeable. :) > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
Yes, we've got the same kind of issue in our app. For the records, here is the problem and the solution. The problem lies in the Camera.startPreview : an error is reported in logcat : E/CameraService( 554): registerBuffers failed with status -38 followed by an exception : java.lang.RuntimeException: startPreview failed The problem is solved by changing the surface holder type : mHolder.setType(SurfaceHolder.SURFACE_TYPE_PUSH_BUFFERS); On 1.5, commenting this line just hides the camera preview from the surface (we don't want it to display directly, we only use it to access to the video frame buffer), but does not crash. Spocky --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
Hi Dianne,
We did intensive testing on 1.5 and never had a problem with it. The change
is definitely good for those developing on 1.6, but it never caused problems
on 1.5 so it is difficult to know the issue exists without the ability to
test on 1.6 (and there wouldn't have been an issue if the platform hadn't
been updated in the middle of a contest). It would be fine if we could
update our ADC2 submission, but we can't and the terms and conditions state
we are developing an app that works on 1.5 (not 1.6), which ours does.
Shelby
On Fri, Oct 9, 2009 at 10:32 AM, Dianne Hackborn wrote:
> Yep I put in that change, and all it did was make it guaranteed the app
> would crash instead of sometimes crashing.
>
>
> On Fri, Oct 9, 2009 at 10:09 AM, bellapariah wrote:
>
>>
>> Hi Brian,
>>
>> I am looking at the usage data from my server which includes how many
>> people signed up for an account as well as how many games they played
>> (my app is not available in the market yet so anyone that signs up for
>> an account should be an ADC2 tester). My final numbers were 102
>> testers, 29 of which were force-quits due to 1.6 upgrade. (so around
>> 30% of testers were using 1.6)
>>
>> Also, here is the change made to 1.6 that is causing my app to not
>> work properly if anyones interested:
>>
>> 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> 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 (cut and paste typo in my
>> case), 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, 1:58 pm, Brian Wright wrote:
>> > How did you determine you had " 95 people test my app for Round 1
>> > judging, but 27 of those were "force closes" due to the 1.6 update. "
>> >
>> > I have not been told anything? Where is this data?
>> >
>> > On Oct 6, 8:48 pm, bellapariah 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."
>> >
>> > > My App 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
>> > > discussing the 1.6 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://group
[android-developers] Re: Where have all the Google employees gone?
Yep I put in that change, and all it did was make it guaranteed the app
would crash instead of sometimes crashing.
On Fri, Oct 9, 2009 at 10:09 AM, bellapariah wrote:
>
> Hi Brian,
>
> I am looking at the usage data from my server which includes how many
> people signed up for an account as well as how many games they played
> (my app is not available in the market yet so anyone that signs up for
> an account should be an ADC2 tester). My final numbers were 102
> testers, 29 of which were force-quits due to 1.6 upgrade. (so around
> 30% of testers were using 1.6)
>
> Also, here is the change made to 1.6 that is causing my app to not
> work properly if anyones interested:
>
> 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 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 (cut and paste typo in my
> case), 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, 1:58 pm, Brian Wright wrote:
> > How did you determine you had " 95 people test my app for Round 1
> > judging, but 27 of those were "force closes" due to the 1.6 update. "
> >
> > I have not been told anything? Where is this data?
> >
> > On Oct 6, 8:48 pm, bellapariah 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."
> >
> > > My App 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
> > > discussing the 1.6 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-.
> ..
> >
> > >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.
> >
> > > How many others were affected? Any solutions to fix the problem?
> >
> > > Shelby
> >
>
--
Dianne Hackborn
Android framework engineer
hack...@android.com
Note: please don't send private
[android-developers] Re: Where have all the Google employees gone?
Hi Brian,
I am looking at the usage data from my server which includes how many
people signed up for an account as well as how many games they played
(my app is not available in the market yet so anyone that signs up for
an account should be an ADC2 tester). My final numbers were 102
testers, 29 of which were force-quits due to 1.6 upgrade. (so around
30% of testers were using 1.6)
Also, here is the change made to 1.6 that is causing my app to not
work properly if anyones interested:
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 {
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 (cut and paste typo in my
case), 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, 1:58 pm, Brian Wright wrote:
> How did you determine you had " 95 people test my app for Round 1
> judging, but 27 of those were "force closes" due to the 1.6 update. "
>
> I have not been told anything? Where is this data?
>
> On Oct 6, 8:48 pm, bellapariah 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."
>
> > My App 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
> > discussing the 1.6 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-...
>
> >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.
>
> > How many others were affected? Any solutions to fix the problem?
>
> > Shelby
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
Please don't confuse me with the facts. Rud On Oct 9, 12:06 am, Shawn Brown wrote: > On Fri, Oct 9, 2009 at 1:45 PM, Rud wrote: > > > My web site got hit by 68 people looking at my game page. Since the > > only reference, pretty much, to the site is on the game I am assuming > > around that many people tested it. > > > Hopefully I'm not being overly optimistic thinking they liked it > > otherwise they would not have bothered to visit the site. > > Hello? Anyone there? > > maybe 100 people reviewed it and 2 people liked it and they each told > 34 friends whom they know like similar things. > > You can't conclude anything other than somebody likes it!!! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
On Fri, Oct 9, 2009 at 1:45 PM, Rud wrote: > > My web site got hit by 68 people looking at my game page. Since the > only reference, pretty much, to the site is on the game I am assuming > around that many people tested it. > > Hopefully I'm not being overly optimistic thinking they liked it > otherwise they would not have bothered to visit the site. Hello? Anyone there? maybe 100 people reviewed it and 2 people liked it and they each told 34 friends whom they know like similar things. You can't conclude anything other than somebody likes it!!! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
My web site got hit by 68 people looking at my game page. Since the
only reference, pretty much, to the site is on the game I am assuming
around that many people tested it.
Hopefully I'm not being overly optimistic thinking they liked it
otherwise they would not have bothered to visit the site.
Rud
On Oct 8, 3:58 pm, Brian Wright wrote:
> How did you determine you had " 95 people test my app for Round 1
> judging, but 27 of those were "force closes" due to the 1.6 update. "
>
> I have not been told anything? Where is this data?
>
> On Oct 6, 8:48 pm, bellapariah 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."
>
> > My App 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
> > discussing the 1.6 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-...
>
> >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.
>
> > How many others were affected? Any solutions to fix the problem?
>
> > Shelby- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
I had: Radar Now: 109 What Zip Code: 99 I know this because my app communicates with our server and leaves behind important information like version. If I had known that OS version would matter, I would have transmitted that as well. Google has been mum about the contest, which is probably what they should be doing. -John Coryat "Radar Now!" "What Zip Code?" --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
Well, there are subtle differences that can break an app that don't
expect them. Like this:
http://groups.google.com/group/android-developers/browse_thread/thread/3f97829b6260ead3
On Oct 6, 7:57 pm, niko20 wrote:
> What API's are you guys using that just going from 1.5 to 1.6 broke
> stuff? I would think 1.6 would have been properly back-compatible...
>
> On Oct 6, 8:58 pm, bellapariah 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:48 pm, bellapariah 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."
>
> > > My App 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
> > > discussing the 1.6 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-...
>
> > >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.
>
> > > How many others were affected? Any solutions to fix the problem?
>
> > > Shelby
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
How did you determine you had " 95 people test my app for Round 1
judging, but 27 of those were "force closes" due to the 1.6 update. "
I have not been told anything? Where is this data?
On Oct 6, 8:48 pm, bellapariah 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."
>
> My App 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
> discussing the 1.6 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-...
>
> 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.
>
> How many others were affected? Any solutions to fix the problem?
>
> Shelby
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
If that's the case, the algorithm for computing required buffer must be WAY off. On a three minute video that takes about 1.5 - 2 minutes to download on a particular EDGE connection (i.e., download speed is faster than realtime playback), playback doesn't begin until about 2 minutes after download was initiated. On Oct 8, 1:24 pm, Marco Nelissen wrote: > Donut (1.6) shipped with OpenCore 2.x, whereas previously we were > using OpenCore 1.x. > From your description is sounds like opencore 2 is more aggressive > about buffering on slow connections, to avoid running out of data at > the end. > > > > On Thu, Oct 8, 2009 at 9:09 AM, dadical wrote: > > > Dianne is there any chance that such threading changes would affect > > the playback of media in a VideoView? I've noticed that since 1.6, > > when I'm on a low-bandwidth connection (e.g., EDGE) videos being > > loaded over HTTP start playing, but then pause until the file is > > pretty much completely downloaded, at which point playback continues. > > Code is pretty straightforward: > > > mVideoView.setVideoURI(pResult); > > final MediaController lMediaController = new MediaController > > (IntroVideoActivity.this); > > mVideoView.setMediaController(lMediaController); > > lMediaController.show(0); > > mVideoView.setKeepScreenOn(true); > > mVideoView.requestFocus(); > > mVideoView.start(); > > > Dave > > > On Oct 7, 12:23 am, Dianne Hackborn wrote: > >> On Tue, Oct 6, 2009 at 9:13 PM, Maps.Huge.Info (Maps API Guru) < > > >> cor...@gmail.com> wrote: > >> > The new market app shows the screen shots that can be uploaded, so > >> > it's a nice update. There seems to be a lot of small changes and (this > >> > could be my imagination) the phone seems to run faster an smoother. > > >> There was a bunch of work done on thread scheduling to ensure that all > >> background apps together couldn't use more than a small fraction (I believe > >> we ended up with 5%) of the time that the foreground threads want. It > >> makes > >> a big difference for example when background syncs are running. > > >> Glad it's noticeable. :) > > >> -- > >> Dianne Hackborn > >> Android framework engineer > >> hack...@android.com > > >> Note: please don't send private questions to me, as I don't have time to > >> provide private support, and so won't reply to such e-mails. All such > >> questions should be posted on public forums, where I and others can see and > >> answer them.- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
Donut (1.6) shipped with OpenCore 2.x, whereas previously we were using OpenCore 1.x. >From your description is sounds like opencore 2 is more aggressive about buffering on slow connections, to avoid running out of data at the end. On Thu, Oct 8, 2009 at 9:09 AM, dadical wrote: > > Dianne is there any chance that such threading changes would affect > the playback of media in a VideoView? I've noticed that since 1.6, > when I'm on a low-bandwidth connection (e.g., EDGE) videos being > loaded over HTTP start playing, but then pause until the file is > pretty much completely downloaded, at which point playback continues. > Code is pretty straightforward: > > mVideoView.setVideoURI(pResult); > final MediaController lMediaController = new MediaController > (IntroVideoActivity.this); > mVideoView.setMediaController(lMediaController); > lMediaController.show(0); > mVideoView.setKeepScreenOn(true); > mVideoView.requestFocus(); > mVideoView.start(); > > Dave > > On Oct 7, 12:23 am, Dianne Hackborn wrote: >> On Tue, Oct 6, 2009 at 9:13 PM, Maps.Huge.Info (Maps API Guru) < >> >> cor...@gmail.com> wrote: >> > The new market app shows the screen shots that can be uploaded, so >> > it's a nice update. There seems to be a lot of small changes and (this >> > could be my imagination) the phone seems to run faster an smoother. >> >> There was a bunch of work done on thread scheduling to ensure that all >> background apps together couldn't use more than a small fraction (I believe >> we ended up with 5%) of the time that the foreground threads want. It makes >> a big difference for example when background syncs are running. >> >> Glad it's noticeable. :) >> >> -- >> Dianne Hackborn >> Android framework engineer >> hack...@android.com >> >> Note: please don't send private questions to me, as I don't have time to >> provide private support, and so won't reply to such e-mails. All such >> questions should be posted on public forums, where I and others can see and >> answer them. > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
It's a thread you've set to the background scheduling level with Process.setThreadPriority(). AsyncTask may do this for you. Do you have problems with the YouTube app? On Thu, Oct 8, 2009 at 10:04 AM, dadical wrote: > > So what exactly is the definition of a background thread vs. a > foreground thread? > > I failed to mention that my video view is being invoked from an > AsyncTask's onPostExecute method, which SHOULD afaik be running on the > UI thread.That being said, I'm assuming that the VideoView > actually loads its media specified by the videoUri property on a > separate thead, as it performs playback while it's loading. My initial > guess was that something fairly dramatic changed in the VideoView's > "required buffer" algorithm. When I saw you mention the changes to > the threading policies in Android it seemed like that might be a > candidate as well. > > > > On Oct 8, 12:34 pm, Dianne Hackborn wrote: > > Not that I know of. All of those threads should be in the foreground. > > > > > > > > > > > > On Thu, Oct 8, 2009 at 9:09 AM, dadical wrote: > > > > > Dianne is there any chance that such threading changes would affect > > > the playback of media in a VideoView? I've noticed that since 1.6, > > > when I'm on a low-bandwidth connection (e.g., EDGE) videos being > > > loaded over HTTP start playing, but then pause until the file is > > > pretty much completely downloaded, at which point playback continues. > > > Code is pretty straightforward: > > > > > mVideoView.setVideoURI(pResult); > > > final MediaController lMediaController = new MediaController > > > (IntroVideoActivity.this); > > > mVideoView.setMediaController(lMediaController); > > > lMediaController.show(0); > > > mVideoView.setKeepScreenOn(true); > > > mVideoView.requestFocus(); > > > mVideoView.start(); > > > > > Dave > > > > > On Oct 7, 12:23 am, Dianne Hackborn wrote: > > > > On Tue, Oct 6, 2009 at 9:13 PM, Maps.Huge.Info (Maps API Guru) < > > > > > > cor...@gmail.com> wrote: > > > > > The new market app shows the screen shots that can be uploaded, so > > > > > it's a nice update. There seems to be a lot of small changes and > (this > > > > > could be my imagination) the phone seems to run faster an smoother. > > > > > > There was a bunch of work done on thread scheduling to ensure that > all > > > > background apps together couldn't use more than a small fraction (I > > > believe > > > > we ended up with 5%) of the time that the foreground threads want. > It > > > makes > > > > a big difference for example when background syncs are running. > > > > > > Glad it's noticeable. :) > > > > > > -- > > > > Dianne Hackborn > > > > Android framework engineer > > > > hack...@android.com > > > > > > Note: please don't send private questions to me, as I don't have time > to > > > > provide private support, and so won't reply to such e-mails. All > such > > > > questions should be posted on public forums, where I and others can > see > > > and > > > > answer them. > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them.- Hide quoted text - > > > > - Show quoted text - > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
So what exactly is the definition of a background thread vs. a foreground thread? I failed to mention that my video view is being invoked from an AsyncTask's onPostExecute method, which SHOULD afaik be running on the UI thread.That being said, I'm assuming that the VideoView actually loads its media specified by the videoUri property on a separate thead, as it performs playback while it's loading. My initial guess was that something fairly dramatic changed in the VideoView's "required buffer" algorithm. When I saw you mention the changes to the threading policies in Android it seemed like that might be a candidate as well. On Oct 8, 12:34 pm, Dianne Hackborn wrote: > Not that I know of. All of those threads should be in the foreground. > > > > > > On Thu, Oct 8, 2009 at 9:09 AM, dadical wrote: > > > Dianne is there any chance that such threading changes would affect > > the playback of media in a VideoView? I've noticed that since 1.6, > > when I'm on a low-bandwidth connection (e.g., EDGE) videos being > > loaded over HTTP start playing, but then pause until the file is > > pretty much completely downloaded, at which point playback continues. > > Code is pretty straightforward: > > > mVideoView.setVideoURI(pResult); > > final MediaController lMediaController = new MediaController > > (IntroVideoActivity.this); > > mVideoView.setMediaController(lMediaController); > > lMediaController.show(0); > > mVideoView.setKeepScreenOn(true); > > mVideoView.requestFocus(); > > mVideoView.start(); > > > Dave > > > On Oct 7, 12:23 am, Dianne Hackborn wrote: > > > On Tue, Oct 6, 2009 at 9:13 PM, Maps.Huge.Info (Maps API Guru) < > > > > cor...@gmail.com> wrote: > > > > The new market app shows the screen shots that can be uploaded, so > > > > it's a nice update. There seems to be a lot of small changes and (this > > > > could be my imagination) the phone seems to run faster an smoother. > > > > There was a bunch of work done on thread scheduling to ensure that all > > > background apps together couldn't use more than a small fraction (I > > believe > > > we ended up with 5%) of the time that the foreground threads want. It > > makes > > > a big difference for example when background syncs are running. > > > > Glad it's noticeable. :) > > > > -- > > > Dianne Hackborn > > > Android framework engineer > > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > > provide private support, and so won't reply to such e-mails. All such > > > questions should be posted on public forums, where I and others can see > > and > > > answer them. > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them.- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
Not that I know of. All of those threads should be in the foreground. On Thu, Oct 8, 2009 at 9:09 AM, dadical wrote: > > Dianne is there any chance that such threading changes would affect > the playback of media in a VideoView? I've noticed that since 1.6, > when I'm on a low-bandwidth connection (e.g., EDGE) videos being > loaded over HTTP start playing, but then pause until the file is > pretty much completely downloaded, at which point playback continues. > Code is pretty straightforward: > > mVideoView.setVideoURI(pResult); > final MediaController lMediaController = new MediaController > (IntroVideoActivity.this); > mVideoView.setMediaController(lMediaController); > lMediaController.show(0); > mVideoView.setKeepScreenOn(true); > mVideoView.requestFocus(); > mVideoView.start(); > > Dave > > On Oct 7, 12:23 am, Dianne Hackborn wrote: > > On Tue, Oct 6, 2009 at 9:13 PM, Maps.Huge.Info (Maps API Guru) < > > > > cor...@gmail.com> wrote: > > > The new market app shows the screen shots that can be uploaded, so > > > it's a nice update. There seems to be a lot of small changes and (this > > > could be my imagination) the phone seems to run faster an smoother. > > > > There was a bunch of work done on thread scheduling to ensure that all > > background apps together couldn't use more than a small fraction (I > believe > > we ended up with 5%) of the time that the foreground threads want. It > makes > > a big difference for example when background syncs are running. > > > > Glad it's noticeable. :) > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
Dianne is there any chance that such threading changes would affect the playback of media in a VideoView? I've noticed that since 1.6, when I'm on a low-bandwidth connection (e.g., EDGE) videos being loaded over HTTP start playing, but then pause until the file is pretty much completely downloaded, at which point playback continues. Code is pretty straightforward: mVideoView.setVideoURI(pResult); final MediaController lMediaController = new MediaController (IntroVideoActivity.this); mVideoView.setMediaController(lMediaController); lMediaController.show(0); mVideoView.setKeepScreenOn(true); mVideoView.requestFocus(); mVideoView.start(); Dave On Oct 7, 12:23 am, Dianne Hackborn wrote: > On Tue, Oct 6, 2009 at 9:13 PM, Maps.Huge.Info (Maps API Guru) < > > cor...@gmail.com> wrote: > > The new market app shows the screen shots that can be uploaded, so > > it's a nice update. There seems to be a lot of small changes and (this > > could be my imagination) the phone seems to run faster an smoother. > > There was a bunch of work done on thread scheduling to ensure that all > background apps together couldn't use more than a small fraction (I believe > we ended up with 5%) of the time that the foreground threads want. It makes > a big difference for example when background syncs are running. > > Glad it's noticeable. :) > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
I'm going to shamelessly admit that I'm new to it. Have been using for just over two months. My env. is ubuntu ( the latest version). I use Eclipse the latest version too. I could not get hold of a G1 device, since the sellers on ebay are screwing me up big time ( just unimaginable, and it is not the main point of discussion, but Google store ran out of dev. device - Oh, great :-(. On 1.5 v3 I did not have problem with the ADT, emulator etc. Compiling, testing on emulator, debugging, going to shell thru tty, everything was fine. On 1.6 I've so many problems that I can not possibly put it up here. Sometime I guess, bad address when I try to launch. If I change something, and build the console does not put the strings. Sometime the new does not get updated, if the emulator is active, I've to shell into it to do rm *.apk or such. Same projects sometime flags for java error, I go kill the R. file, try to muck with the build properties and src priorities... I mentioned briefly before that it seems like it is now bloated. Sorry, but that is what I've been observing. -pro --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
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. :(
Shelby
On Oct 6, 7:57 pm, niko20 wrote:
> What API's are you guys using that just going from 1.5 to 1.6 broke
> stuff? I would think 1.6 would have been properly back-compatible...
>
> On Oct 6, 8:58 pm, bellapariah 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:48 pm, bellapariah 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."
>
> > > My App 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
> > > discussing the 1.6 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-...
>
> > >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.
>
> > > How many others were affected? Any solutions to fix the problem?
>
> > > Shelby
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
On Tue, Oct 6, 2009 at 9:13 PM, Maps.Huge.Info (Maps API Guru) < cor...@gmail.com> wrote: > The new market app shows the screen shots that can be uploaded, so > it's a nice update. There seems to be a lot of small changes and (this > could be my imagination) the phone seems to run faster an smoother. > There was a bunch of work done on thread scheduling to ensure that all background apps together couldn't use more than a small fraction (I believe we ended up with 5%) of the time that the foreground threads want. It makes a big difference for example when background syncs are running. Glad it's noticeable. :) -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
1.6 is out. It's been pushed to T-Mobile users (at least in the US)
and is available as an official download for the Google ION directly
from the HTC site. I just updated my device to 1.6 and thankfully, my
apps still run.
The new market app shows the screen shots that can be uploaded, so
it's a nice update. There seems to be a lot of small changes and (this
could be my imagination) the phone seems to run faster an smoother.
-John Coryat
"Radar Now!"
"What Zip Code?"
On Oct 6, 10:02 pm, niko20 wrote:
> Also, I don't think 1.6 is officially out as a image update/download.
> I think if people are using it they are using an unofficial compiled
> ROM. This may be the real problem.
>
> On Oct 6, 9:57 pm, niko20 wrote:
>
> > What API's are you guys using that just going from 1.5 to 1.6 broke
> > stuff? I would think 1.6 would have been properly back-compatible...
>
> > On Oct 6, 8:58 pm, bellapariah 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:48 pm, bellapariah 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."
>
> > > > My App 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
> > > > discussing the 1.6 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-...
>
> > > >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.
>
> > > > How many others were affected? Any solutions to fix the problem?
>
> > > > Shelby
>
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
My G1 downloaded and installed 1.6 today. My ADC2 game was installed
and runs fine under 1.6. It uses the sensors, GPS, trackball and does
graphics. Not being holier than thou about this; just mentioning it in
conjunction with saying the 1.6 is downloading.
Rud
http://www.mysticlakesoftware.com
On Oct 6, 10:02 pm, niko20 wrote:
> Also, I don't think 1.6 is officially out as a image update/download.
> I think if people are using it they are using an unofficial compiled
> ROM. This may be the real problem.
>
> On Oct 6, 9:57 pm, niko20 wrote:
>
>
>
> > What API's are you guys using that just going from 1.5 to 1.6 broke
> > stuff? I would think 1.6 would have been properly back-compatible...
>
> > On Oct 6, 8:58 pm, bellapariah 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:48 pm, bellapariah 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."
>
> > > > My App 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
> > > > discussing the 1.6 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-...
>
> > > >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.
>
> > > > How many others were affected? Any solutions to fix the problem?
>
> > > > Shelby- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
Also, I don't think 1.6 is officially out as a image update/download.
I think if people are using it they are using an unofficial compiled
ROM. This may be the real problem.
On Oct 6, 9:57 pm, niko20 wrote:
> What API's are you guys using that just going from 1.5 to 1.6 broke
> stuff? I would think 1.6 would have been properly back-compatible...
>
> On Oct 6, 8:58 pm, bellapariah 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:48 pm, bellapariah 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."
>
> > > My App 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
> > > discussing the 1.6 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-...
>
> > >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.
>
> > > How many others were affected? Any solutions to fix the problem?
>
> > > Shelby
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
What API's are you guys using that just going from 1.5 to 1.6 broke
stuff? I would think 1.6 would have been properly back-compatible...
On Oct 6, 8:58 pm, bellapariah 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:48 pm, bellapariah 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."
>
> > My App 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
> > discussing the 1.6 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-...
>
> >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.
>
> > How many others were affected? Any solutions to fix the problem?
>
> > Shelby
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Where have all the Google employees gone?
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:48 pm, bellapariah 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."
>
> My App 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
> discussing the 1.6 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-...
>
> 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.
>
> How many others were affected? Any solutions to fix the problem?
>
> Shelby
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
