Removing support for android 1.5/1.6?

hey all,

according to http://developer.android.com/resources/dashboard/platform-versions.html,
there are very few android 1.5/1.6 devices (~3%) accessing the android
market.

we've always supported older devices on odk collect, but dropping that
support would allow us to move a bit faster. is there anyone out there
still using android 1.5/1.6 devices?

yaw

We're not doing anything with 1.5/1.6 and have no plans to. My
suggestion would be to push the most recent version of ODK Collect that
supports 1.5/1.6 into a maintenance branch and continue to support it
for a while with bug fixes, etc. but future development shouldn't really
worry about 1.5/1.6.

Those who are interested can always take a stab at backporting
enhancements to the maintenance branch.

Just my 2 cents,

Matt

··· -- Matt Adams Radical Dynamic www.radicaldynamic.com

Yes we have a pile of g1s on 1.6

hey all,

according to
http://developer.android.com/resources/dashboard/platform-versions.html,

··· On Sep 30, 2011 4:34 PM, "Yaw Anokwa" wrote: > there are very few android 1.5/1.6 devices (~3%) accessing the android > market. > > we've always supported older devices on odk collect, but dropping that > support would allow us to move a bit faster. is there anyone out there > still using android 1.5/1.6 devices? > > yaw > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en

Yep,

A fleet of G1s with 1.6 in the field ..

··· On Sep 30, 4:52 pm, Matt Adams wrote: > We're not doing anything with 1.5/1.6 and have no plans to. My > suggestion would be to push the most recent version of ODK Collect that > supports 1.5/1.6 into a maintenance branch and continue to support it > for a while with bug fixes, etc. but future development shouldn't really > worry about 1.5/1.6. > > Those who are interested can always take a stab at backporting > enhancements to the maintenance branch. > > Just my 2 cents, > > Matt > -- > Matt Adams > Radical Dynamicwww.radicaldynamic.com

ok, thanks for the feedback all. we haven't decided, but i think 1.1.7
will likely be our last build with support for 1.5/1.6.

··· On Sat, Oct 1, 2011 at 07:24, Adam Calo wrote: > Yep, > > A fleet of G1s with 1.6 in the field .. > > On Sep 30, 4:52 pm, Matt Adams wrote: >> We're not doing anything with 1.5/1.6 and have no plans to. My >> suggestion would be to push the most recent version of ODK Collect that >> supports 1.5/1.6 into a maintenance branch and continue to support it >> for a while with bug fixes, etc. but future development shouldn't really >> worry about 1.5/1.6. >> >> Those who are interested can always take a stab at backporting >> enhancements to the maintenance branch. >> >> Just my 2 cents, >> >> Matt >> -- >> Matt Adams >> Radical Dynamicwww.radicaldynamic.com > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

Just a curious programmer's question for some Android veterans: what
kinds of things make it hard to support 1.6? I have no doubt that it
/is/ hard, just curious which bits. The only thing I have experience
with is the status bar icons, which are totally different in 2.x. Oh,
and background processes. What else??

··· On 1 October 2011 10:48, Yaw Anokwa wrote: > ok, thanks for the feedback all. we haven't decided, but i think 1.1.7 > will likely be our last build with support for 1.5/1.6. > > On Sat, Oct 1, 2011 at 07:24, Adam Calo wrote: >> Yep, >> >> A fleet of G1s with 1.6 in the field .. >> >> On Sep 30, 4:52 pm, Matt Adams wrote: >>> We're not doing anything with 1.5/1.6 and have no plans to. My >>> suggestion would be to push the most recent version of ODK Collect that >>> supports 1.5/1.6 into a maintenance branch and continue to support it >>> for a while with bug fixes, etc. but future development shouldn't really >>> worry about 1.5/1.6. >>> >>> Those who are interested can always take a stab at backporting >>> enhancements to the maintenance branch. >>> >>> Just my 2 cents, >>> >>> Matt >>> -- >>> Matt Adams >>> Radical Dynamicwww.radicaldynamic.com >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

how we do image capture, managed dialogs, and date picker are
essentially messy workarounds for bugs in 1.5/1.6. see


for an example.

there are also other apis (google auth, push notifications, download
manager, etc) that are only available in later versions of android.
that's really the more important thing. to do the exciting things for
users (i.e. auto-syncing forms and data), we need to use the new apis.

··· On Sat, Oct 1, 2011 at 08:44, Thomas Smyth wrote: > Just a curious programmer's question for some Android veterans: what > kinds of things make it hard to support 1.6? I have no doubt that it > /is/ hard, just curious which bits. The only thing I have experience > with is the status bar icons, which are totally different in 2.x. Oh, > and background processes. What else?? > > On 1 October 2011 10:48, Yaw Anokwa wrote: >> ok, thanks for the feedback all. we haven't decided, but i think 1.1.7 >> will likely be our last build with support for 1.5/1.6. >> >> On Sat, Oct 1, 2011 at 07:24, Adam Calo wrote: >>> Yep, >>> >>> A fleet of G1s with 1.6 in the field .. >>> >>> On Sep 30, 4:52 pm, Matt Adams wrote: >>>> We're not doing anything with 1.5/1.6 and have no plans to. My >>>> suggestion would be to push the most recent version of ODK Collect that >>>> supports 1.5/1.6 into a maintenance branch and continue to support it >>>> for a while with bug fixes, etc. but future development shouldn't really >>>> worry about 1.5/1.6. >>>> >>>> Those who are interested can always take a stab at backporting >>>> enhancements to the maintenance branch. >>>> >>>> Just my 2 cents, >>>> >>>> Matt >>>> -- >>>> Matt Adams >>>> Radical Dynamicwww.radicaldynamic.com >>> >>> -- >>> Post: opendatakit@googlegroups.com >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>> Options: http://groups.google.com/group/opendatakit?hl=en >>> >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

I see. Well I like the other person's suggestion that you maintain
basic support for a 1.6 compatible branch and press on with the more
exciting stuff in the main line.

Is there much of a diff between 1.5 and 1.6 in terms of coding
headaches? I would think removing support for 1.5 would be less
controversial since pretty much any device with 1.5 could be brought
up to 1.6 without too much trouble (we could even provide howtos for
this...)

··· On 3 October 2011 00:08, Yaw Anokwa wrote: > how we do image capture, managed dialogs, and date picker are > essentially messy workarounds for bugs in 1.5/1.6. see > http://stackoverflow.com/questions/1910608/android-action-image-capture-intent/1932268#1932268 > for an example. > > there are also other apis (google auth, push notifications, download > manager, etc) that are only available in later versions of android. > that's really the more important thing. to do the exciting things for > users (i.e. auto-syncing forms and data), we need to use the new apis. > > On Sat, Oct 1, 2011 at 08:44, Thomas Smyth wrote: >> Just a curious programmer's question for some Android veterans: what >> kinds of things make it hard to support 1.6? I have no doubt that it >> /is/ hard, just curious which bits. The only thing I have experience >> with is the status bar icons, which are totally different in 2.x. Oh, >> and background processes. What else?? >> >> On 1 October 2011 10:48, Yaw Anokwa wrote: >>> ok, thanks for the feedback all. we haven't decided, but i think 1.1.7 >>> will likely be our last build with support for 1.5/1.6. >>> >>> On Sat, Oct 1, 2011 at 07:24, Adam Calo wrote: >>>> Yep, >>>> >>>> A fleet of G1s with 1.6 in the field .. >>>> >>>> On Sep 30, 4:52 pm, Matt Adams wrote: >>>>> We're not doing anything with 1.5/1.6 and have no plans to. My >>>>> suggestion would be to push the most recent version of ODK Collect that >>>>> supports 1.5/1.6 into a maintenance branch and continue to support it >>>>> for a while with bug fixes, etc. but future development shouldn't really >>>>> worry about 1.5/1.6. >>>>> >>>>> Those who are interested can always take a stab at backporting >>>>> enhancements to the maintenance branch. >>>>> >>>>> Just my 2 cents, >>>>> >>>>> Matt >>>>> -- >>>>> Matt Adams >>>>> Radical Dynamicwww.radicaldynamic.com >>>> >>>> -- >>>> Post: opendatakit@googlegroups.com >>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>> >>> >>> -- >>> Post: opendatakit@googlegroups.com >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>> Options: http://groups.google.com/group/opendatakit?hl=en >>> >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

1.5/1.6 are very similar, so not much is gained by removing support
for 1.5. anyway, i think we'll stop 1.5/1.6 support after this release
and go from there.

··· On Mon, Oct 3, 2011 at 06:11, Thomas Smyth wrote: > I see. Well I like the other person's suggestion that you maintain > basic support for a 1.6 compatible branch and press on with the more > exciting stuff in the main line. > > Is there much of a diff between 1.5 and 1.6 in terms of coding > headaches? I would think removing support for 1.5 would be less > controversial since pretty much any device with 1.5 could be brought > up to 1.6 without too much trouble (we could even provide howtos for > this...) > > On 3 October 2011 00:08, Yaw Anokwa wrote: >> how we do image capture, managed dialogs, and date picker are >> essentially messy workarounds for bugs in 1.5/1.6. see >> http://stackoverflow.com/questions/1910608/android-action-image-capture-intent/1932268#1932268 >> for an example. >> >> there are also other apis (google auth, push notifications, download >> manager, etc) that are only available in later versions of android. >> that's really the more important thing. to do the exciting things for >> users (i.e. auto-syncing forms and data), we need to use the new apis. >> >> On Sat, Oct 1, 2011 at 08:44, Thomas Smyth wrote: >>> Just a curious programmer's question for some Android veterans: what >>> kinds of things make it hard to support 1.6? I have no doubt that it >>> /is/ hard, just curious which bits. The only thing I have experience >>> with is the status bar icons, which are totally different in 2.x. Oh, >>> and background processes. What else?? >>> >>> On 1 October 2011 10:48, Yaw Anokwa wrote: >>>> ok, thanks for the feedback all. we haven't decided, but i think 1.1.7 >>>> will likely be our last build with support for 1.5/1.6. >>>> >>>> On Sat, Oct 1, 2011 at 07:24, Adam Calo wrote: >>>>> Yep, >>>>> >>>>> A fleet of G1s with 1.6 in the field .. >>>>> >>>>> On Sep 30, 4:52 pm, Matt Adams wrote: >>>>>> We're not doing anything with 1.5/1.6 and have no plans to. My >>>>>> suggestion would be to push the most recent version of ODK Collect that >>>>>> supports 1.5/1.6 into a maintenance branch and continue to support it >>>>>> for a while with bug fixes, etc. but future development shouldn't really >>>>>> worry about 1.5/1.6. >>>>>> >>>>>> Those who are interested can always take a stab at backporting >>>>>> enhancements to the maintenance branch. >>>>>> >>>>>> Just my 2 cents, >>>>>> >>>>>> Matt >>>>>> -- >>>>>> Matt Adams >>>>>> Radical Dynamicwww.radicaldynamic.com >>>>> >>>>> -- >>>>> Post: opendatakit@googlegroups.com >>>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>>> >>>> >>>> -- >>>> Post: opendatakit@googlegroups.com >>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>> >>> >>> -- >>> Post: opendatakit@googlegroups.com >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>> Options: http://groups.google.com/group/opendatakit?hl=en >>> >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

I would be up for perhaps upgrading all our G1s to some version of
2.x. But last time I tried that with Cyanogen, it was so slow. Perhaps
there are better images out there now. We have the advantage of being
able to strip out almost all the extraneous apps and all (don't need
gmail, calendar, etc.)

Has anyone had better luck than me on this?

··· On 3 October 2011 09:15, Yaw Anokwa wrote: > 1.5/1.6 are very similar, so not much is gained by removing support > for 1.5. anyway, i think we'll stop 1.5/1.6 support after this release > and go from there. > > On Mon, Oct 3, 2011 at 06:11, Thomas Smyth wrote: >> I see. Well I like the other person's suggestion that you maintain >> basic support for a 1.6 compatible branch and press on with the more >> exciting stuff in the main line. >> >> Is there much of a diff between 1.5 and 1.6 in terms of coding >> headaches? I would think removing support for 1.5 would be less >> controversial since pretty much any device with 1.5 could be brought >> up to 1.6 without too much trouble (we could even provide howtos for >> this...) >> >> On 3 October 2011 00:08, Yaw Anokwa wrote: >>> how we do image capture, managed dialogs, and date picker are >>> essentially messy workarounds for bugs in 1.5/1.6. see >>> http://stackoverflow.com/questions/1910608/android-action-image-capture-intent/1932268#1932268 >>> for an example. >>> >>> there are also other apis (google auth, push notifications, download >>> manager, etc) that are only available in later versions of android. >>> that's really the more important thing. to do the exciting things for >>> users (i.e. auto-syncing forms and data), we need to use the new apis. >>> >>> On Sat, Oct 1, 2011 at 08:44, Thomas Smyth wrote: >>>> Just a curious programmer's question for some Android veterans: what >>>> kinds of things make it hard to support 1.6? I have no doubt that it >>>> /is/ hard, just curious which bits. The only thing I have experience >>>> with is the status bar icons, which are totally different in 2.x. Oh, >>>> and background processes. What else?? >>>> >>>> On 1 October 2011 10:48, Yaw Anokwa wrote: >>>>> ok, thanks for the feedback all. we haven't decided, but i think 1.1.7 >>>>> will likely be our last build with support for 1.5/1.6. >>>>> >>>>> On Sat, Oct 1, 2011 at 07:24, Adam Calo wrote: >>>>>> Yep, >>>>>> >>>>>> A fleet of G1s with 1.6 in the field .. >>>>>> >>>>>> On Sep 30, 4:52 pm, Matt Adams wrote: >>>>>>> We're not doing anything with 1.5/1.6 and have no plans to. My >>>>>>> suggestion would be to push the most recent version of ODK Collect that >>>>>>> supports 1.5/1.6 into a maintenance branch and continue to support it >>>>>>> for a while with bug fixes, etc. but future development shouldn't really >>>>>>> worry about 1.5/1.6. >>>>>>> >>>>>>> Those who are interested can always take a stab at backporting >>>>>>> enhancements to the maintenance branch. >>>>>>> >>>>>>> Just my 2 cents, >>>>>>> >>>>>>> Matt >>>>>>> -- >>>>>>> Matt Adams >>>>>>> Radical Dynamicwww.radicaldynamic.com >>>>>> >>>>>> -- >>>>>> Post: opendatakit@googlegroups.com >>>>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>>>> >>>>> >>>>> -- >>>>> Post: opendatakit@googlegroups.com >>>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>>> >>>> >>>> -- >>>> Post: opendatakit@googlegroups.com >>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>> >>> >>> -- >>> Post: opendatakit@googlegroups.com >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>> Options: http://groups.google.com/group/opendatakit?hl=en >>> >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

http://forum.xda-developers.com/showthread.php?t=1079194 suggests that
froyo by lazlo is the best of the g1 roms. try that one...

··· On Mon, Oct 3, 2011 at 06:19, Thomas Smyth wrote: > I would be up for perhaps upgrading all our G1s to some version of > 2.x. But last time I tried that with Cyanogen, it was so slow. Perhaps > there are better images out there now. We have the advantage of being > able to strip out almost all the extraneous apps and all (don't need > gmail, calendar, etc.) > > Has anyone had better luck than me on this? > > > On 3 October 2011 09:15, Yaw Anokwa wrote: >> 1.5/1.6 are very similar, so not much is gained by removing support >> for 1.5. anyway, i think we'll stop 1.5/1.6 support after this release >> and go from there. >> >> On Mon, Oct 3, 2011 at 06:11, Thomas Smyth wrote: >>> I see. Well I like the other person's suggestion that you maintain >>> basic support for a 1.6 compatible branch and press on with the more >>> exciting stuff in the main line. >>> >>> Is there much of a diff between 1.5 and 1.6 in terms of coding >>> headaches? I would think removing support for 1.5 would be less >>> controversial since pretty much any device with 1.5 could be brought >>> up to 1.6 without too much trouble (we could even provide howtos for >>> this...) >>> >>> On 3 October 2011 00:08, Yaw Anokwa wrote: >>>> how we do image capture, managed dialogs, and date picker are >>>> essentially messy workarounds for bugs in 1.5/1.6. see >>>> http://stackoverflow.com/questions/1910608/android-action-image-capture-intent/1932268#1932268 >>>> for an example. >>>> >>>> there are also other apis (google auth, push notifications, download >>>> manager, etc) that are only available in later versions of android. >>>> that's really the more important thing. to do the exciting things for >>>> users (i.e. auto-syncing forms and data), we need to use the new apis. >>>> >>>> On Sat, Oct 1, 2011 at 08:44, Thomas Smyth wrote: >>>>> Just a curious programmer's question for some Android veterans: what >>>>> kinds of things make it hard to support 1.6? I have no doubt that it >>>>> /is/ hard, just curious which bits. The only thing I have experience >>>>> with is the status bar icons, which are totally different in 2.x. Oh, >>>>> and background processes. What else?? >>>>> >>>>> On 1 October 2011 10:48, Yaw Anokwa wrote: >>>>>> ok, thanks for the feedback all. we haven't decided, but i think 1.1.7 >>>>>> will likely be our last build with support for 1.5/1.6. >>>>>> >>>>>> On Sat, Oct 1, 2011 at 07:24, Adam Calo wrote: >>>>>>> Yep, >>>>>>> >>>>>>> A fleet of G1s with 1.6 in the field .. >>>>>>> >>>>>>> On Sep 30, 4:52 pm, Matt Adams wrote: >>>>>>>> We're not doing anything with 1.5/1.6 and have no plans to. My >>>>>>>> suggestion would be to push the most recent version of ODK Collect that >>>>>>>> supports 1.5/1.6 into a maintenance branch and continue to support it >>>>>>>> for a while with bug fixes, etc. but future development shouldn't really >>>>>>>> worry about 1.5/1.6. >>>>>>>> >>>>>>>> Those who are interested can always take a stab at backporting >>>>>>>> enhancements to the maintenance branch. >>>>>>>> >>>>>>>> Just my 2 cents, >>>>>>>> >>>>>>>> Matt >>>>>>>> -- >>>>>>>> Matt Adams >>>>>>>> Radical Dynamicwww.radicaldynamic.com >>>>>>> >>>>>>> -- >>>>>>> Post: opendatakit@googlegroups.com >>>>>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>>>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>>>>> >>>>>> >>>>>> -- >>>>>> Post: opendatakit@googlegroups.com >>>>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>>>> >>>>> >>>>> -- >>>>> Post: opendatakit@googlegroups.com >>>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>>> >>>> >>>> -- >>>> Post: opendatakit@googlegroups.com >>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>>> Options: http://groups.google.com/group/opendatakit?hl=en >>>> >>> >>> -- >>> Post: opendatakit@googlegroups.com >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>> Options: http://groups.google.com/group/opendatakit?hl=en >>> >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >