Dear all,
On our Samsung Galaxy Tabs (mix of Android 2.2 and 3.2) when we get to a
date widget e.g Date of Birth when we input a date of birth then swipe
forward to the next page then swipe back to the previous Date of Birth page
we notice that the date will have changed, the month will have changed but
the year will have stayed the same (current year). For example if am on the
date of birth page the default DOB is todays date. I then change this to
06 JUN 1980, swipe forward, swipe back and I find that it reads 06 JUN 2012
.The year reverts back to the current year. The workaround is that
whenever we are on a date of birth widget if our target year is 1980, we
first input 1979 and use the plus button above the year to get to 1980 or
input 1981 then use the minus button above the year to get 1980 then when
we swipe to move forward and swipe back to double check it has retained the
correct date of birth we see that it does. So currently we keep getting
loads of people who are born on the year of interview (erroneously) simply
due to this and the tediousness of the workaround. Anyone else experienced
a similar thing?
I confirm that this behavior is also present in 12 RC2(1008).
Tumaini, try this shorter workaround: instead of pressing the plus, then
the minus button afterwards (or the other way around) just touch another
field (if you're changing year for example, touch the month or day) which
seems to send a trigger to save the change as well.
Hope this helps while this bug is being fixed.
···
On Wednesday, June 13, 2012, Tumaini Kilimba wrote:
Dear all,
On our Samsung Galaxy Tabs (mix of Android 2.2 and 3.2) when we get to a
date widget e.g Date of Birth when we input a date of birth then swipe
forward to the next page then swipe back to the previous Date of Birth page
we notice that the date will have changed, the month will have changed but
the year will have stayed the same (current year). For example if am on the
date of birth page the default DOB is todays date. I then change this to
06 JUN 1980, swipe forward, swipe back and I find that it reads 06 JUN 2012
.The year reverts back to the current year. The workaround is that
whenever we are on a date of birth widget if our target year is 1980, we
first input 1979 and use the plus button above the year to get to 1980 or
input 1981 then use the minus button above the year to get 1980 then when
we swipe to move forward and swipe back to double check it has retained the
correct date of birth we see that it does. So currently we keep getting
loads of people who are born on the year of interview (erroneously) simply
due to this and the tediousness of the workaround. Anyone else experienced
a similar thing?
Do you know if this has been raised as an issue yet, officially?
···
On Wed, Jun 13, 2012 at 12:56 PM, ゴー・ニコライ wrote:
I confirm that this behavior is also present in 12 RC2(1008).
Tumaini, try this shorter workaround: instead of pressing the plus, then
the minus button afterwards (or the other way around) just touch another
field (if you're changing year for example, touch the month or day) which
seems to send a trigger to save the change as well.
Hope this helps while this bug is being fixed.
On Wednesday, June 13, 2012, Tumaini Kilimba wrote:
Dear all,
On our Samsung Galaxy Tabs (mix of Android 2.2 and 3.2) when we get to a
date widget e.g Date of Birth when we input a date of birth then swipe
forward to the next page then swipe back to the previous Date of Birth page
we notice that the date will have changed, the month will have changed but
the year will have stayed the same (current year). For example if am on the
date of birth page the default DOB is todays date. I then change this to
06 JUN 1980, swipe forward, swipe back and I find that it reads 06 JUN 2012
.The year reverts back to the current year. The workaround is that
whenever we are on a date of birth widget if our target year is 1980, we
first input 1979 and use the plus button above the year to get to 1980 or
input 1981 then use the minus button above the year to get 1980 then when
we swipe to move forward and swipe back to double check it has retained the
correct date of birth we see that it does. So currently we keep getting
loads of people who are born on the year of interview (erroneously) simply
due to this and the tediousness of the workaround. Anyone else experienced
a similar thing?