In Progress Calendar FC when setting future date for event

[1982Strand]

FC occurs in calendar app, during creation of event and trying to set a future time/date.

Galaxy S3 - 2.11.30 - multilang.

Tried clearing app data, wiping cache/dalvik and a clean install - all failing to resolve it.
Seems i'm not the only one, the issue is mentioned elsewhere on the forums...

W/dalvikvm( 6501): threadid=1: thread exiting with uncaught exception (group=0x40f842a0)
 
E/AndroidRuntime( 6501): FATAL EXCEPTION: main
 
E/AndroidRuntime( 6501): java.lang.NoSuchMethodError: android.widget.DatePicker.access$000
 
E/AndroidRuntime( 6501): at android.widget.DatePicker$OnDateChangeListener.onValueChange(DatePicker.java:77)
 
E/AndroidRuntime( 6501): at android.widget.NumberPicker.notifyChange(NumberPicker.java:1772)
 
E/AndroidRuntime( 6501): at android.widget.NumberPicker.setValueInternal(NumberPicker.java:1558)
 
E/AndroidRuntime( 6501): at android.widget.NumberPicker.scrollBy(NumberPicker.java:1061)
 
E/AndroidRuntime( 6501): at android.widget.NumberPicker.computeScroll(NumberPicker.java:1015)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12698)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3151)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12646)
 
E/AndroidRuntime( 6501): at android.view.View.getDisplayList(View.java:12754)
 
E/AndroidRuntime( 6501): at android.view.HardwareRenderer$GlRenderer.draw(HardwareRenderer.java:1144)
 
E/AndroidRuntime( 6501): at android.view.ViewRootImpl.draw(ViewRootImpl.java:2271)
 
E/AndroidRuntime( 6501): at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2143)
 
E/AndroidRuntime( 6501): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1954)
 
E/AndroidRuntime( 6501): at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1110)
 
E/AndroidRuntime( 6501): at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4470)
 
E/AndroidRuntime( 6501): at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
 
E/AndroidRuntime( 6501): at android.view.Choreographer.doCallbacks(Choreographer.java:555)
 
E/AndroidRuntime( 6501): at android.view.Choreographer.doFrame(Choreographer.java:525)
 
E/AndroidRuntime( 6501): at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:711)
 
E/AndroidRuntime( 6501): at android.os.Handler.handleCallback(Handler.java:615)
 
E/AndroidRuntime( 6501): at android.os.Handler.dispatchMessage(Handler.java:92)
 
E/AndroidRuntime( 6501): at android.os.Looper.loop(Looper.java:137)
 
E/AndroidRuntime( 6501): at android.app.ActivityThread.main(ActivityThread.java:4898)
 
E/AndroidRuntime( 6501): at java.lang.reflect.Method.invokeNative(Native Method)
 
E/AndroidRuntime( 6501): at java.lang.reflect.Method.invoke(Method.java:511)
 
E/AndroidRuntime( 6501): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1006)
 
E/AndroidRuntime( 6501): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:773)
 
E/AndroidRuntime( 6501): at dalvik.system.NativeStart.main(Native Method)

 

[ingbrzy]

what language..? is that issue also on English..?

 

[1982Strand]

what language..? is that issue also on English..?

Yeah also on English So guess it's regardless of language.. I bet you can re-produce it ;-)

Using danish btw..

@ my commodore 64

 

[Acid]

I dont get that on polish. I've created event on 10th Dec. Local account. No FC.
But it's my polish, not multi.


Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2

 

[1982Strand]

I dont get that on polish. I've created event on 10th Dec. Local account. No FC.
But it's my polish, not multi.


Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2

Try to change the new event and set the event time to 10th dec. 2013. Still no FC?

 

[Acid]

Did it. I've changed 10th Dec 2012 to 10th 2013. Still no FC.

Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2

 

[1982Strand]

Hmm. That's odd. But i wonder why this guy here has the exact same issue:

http://miuiandroid.com/community/threads/2-11-30.18892/page-8#post-147559

 

[Acid]

I did exactly as this guy said. I even set the very last day in calendar app: 31.12.2036. Still no FC.

Btw: does enyone know why the last year is 2036 in miui calendar?

Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2

 

[1982Strand]

Works in 2.12.7!

 

[teea]

Happy new year everyone! I'm getting this same error with 2.12.28 (htc one x). Downloaded ROM from this website. Using english language. I love this calendar, it's so nice, but can't really use it due to this annoying bug.

More details:
Tried to do it localy and using gmail calendar - same result.
It crashes (FCs) exactly when I try to choose/change day, month or year under "FROM" and "TO" fields. I can set "FROM" date by starting an event from that day choosing it from calendar interface, but if I try to change it - I'm getting a crash.
Time (hours and minutes) changing works fine.

Also I installed 2.12.28 just yesterday. Wiped cache and dalvik. Wiped it right now just in case - same issue.
And I never tried to use calendar before, but now I need to sync corporate calendar for work and I'm getting this.

Upd:
Downloaded standalone google calendar - same issue.

 

[ingbrzy]

Post logcat please...
Do you use Mayan calendar..? It already ends so it can be issue.. lol..

 

[teea]

Post logcat please...
Do you use Mayan calendar..? It already ends so it can be issue.. lol..

Haha Maybe this is an issue indeed!

Anyway, I'm sorry for not posting logcat asap. Thought it's already posted with same issue in first post.
Here is log: http://rghost.ru/42707233


It's too long (over 10000 symbols) so I couldn't post it in miuiandroid logcat page. I don't know what should I delete from it and what should I keep so I uploaded it untouched.


Upd:
Also what I noticed is that there is no other days, months and years besides nearest to todays. So for now I can see only 2nd, 3rd and 4th; Dec, Jan, Feb; 2012, 2013, 2014. If I'm trying to scroll through any of these values - there is blank space. When I'm "reaching" next day/month/year I'm getting FC.

Upd 2:
I'm trying to play around with different date & time settings - same result.

btw, sorry for my poor english :3

 

[ingbrzy]

when app has FC, press Send MIUI - MENU - COPY and post that log here... in yours logcat I cant find error...

 

[teea]

when app has FC, press Send MIUI - MENU - COPY and post that log here... in yours logcat I cant find error...

Sure! Here we go:

java.lang.NoSuchMethodError: android.widget.DatePicker.handleValueChange
at android.widget.DatePicker$OnDateChangeListener.onValueChange(DatePicker.java:77)
at android.widget.NumberPicker.notifyChange(NumberPicker.java:1750)
at android.widget.NumberPicker.setValueInternal(NumberPicker.java:1536)
at android.widget.NumberPicker.scrollBy(NumberPicker.java:1039)
at android.widget.NumberPicker.onTouchEvent(NumberPicker.java:846)
at android.view.View.dispatchTouchEvent(View.java:7197)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2181)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1916)
at android.widget.NumberPicker.dispatchTouchEvent(NumberPicker.java:903)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2187)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1930)
at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:2048)
at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1502)
at android.app.Dialog.dispatchTouchEvent(Dialog.java:749)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1996)
at android.view.View.dispatchPointerEvent(View.java:7391)
at android.view.ViewRootImpl.deliverPointerEvent(ViewRootImpl.java:3553)
at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:3482)
at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:4591)
at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:4570)
at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:4662)
at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:184)
at android.view.InputEventReceiver.nativeConsumeBatchedInputEvents(Native Method)
at android.view.InputEventReceiver.consumeBatchedInputEvents(InputEventReceiver.java:171)
at android.view.ViewRootImpl.doConsumeBatchedInput(ViewRootImpl.java:4641)
at android.view.ViewRootImpl$ConsumeBatchedInputRunnable.run(ViewRootImpl.java:4690)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
at android.view.Choreographer.doCallbacks(Choreographer.java:555)
at android.view.Choreographer.doFrame(Choreographer.java:523)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:711)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:155)
at android.app.ActivityThread.main(ActivityThread.java:5485)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1028)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:795)
at dalvik.system.NativeStart.main(Native Method)

 

[teea]

Hey again. Actually any app using same interface elements to choose date crashes. :| Even wunderlist.

 

[ingbrzy]

Its issue in framework.. We cant fix it now and have to wait for next release from MIUI China... Sorry for that...

Could you try MIUI China release if is there same issue..?

 

[teea]

Its issue in framework.. We cant fix it now and have to wait for next release from MIUI China... Sorry for that...

Could you try MIUI China release if is there same issue..?

Hi,
so you're getting same issue? Or it's only me? Or it's because of HOX version?

I might try it but first I need to get sure if I can backup all my apps settings and all my current MIUI settings. Backup from clockwork recovery does it?

 

[ingbrzy]

Hi,
so you're getting same issue? Or it's only me? Or it's because of HOX version?

I might try it but first I need to get sure if I can backup all my apps settings and all my current MIUI settings. Backup from clockwork recovery does it?

No, its only HOX version...

 

[teea]

It is quite sad.

For last few days (funny holidays) I was learning java and simple android app development. So I tested a lot of stuff including standard API datePickers, webview datePicker (that one from the browser, which gets called by <input type="date"> html5 field) and different calendarViews and so on. I found interesting thing. Some of datePickers do work fine!
For example if you edit a contact and you add a birthday field for it - datePicker dialog works perfectly for this.
But if you add an event in calendar - it force closes.
Also I noticed that datePicker dialog called by clicking an <input/> field with type="date" html5-parameter works fine too.

Most annoying thing that I decided to write an app for managing my clients (customers). I already managed to write a core: sending data directly to google servers via gdata client, adding events to the calendar: check-ins and check-outs and so on. I started to work on UI and remembered about this annoying datePicker FC

Ofc it works in emulator and I can install some other ROM, but I really like MIUI and I'm not going to switch. So I'm waiting for the fix, I hope it will come soon. Until then I guess I have to use some ugly workarounds.

Off-topic:
I can't understand how to change datePicker appearance yet. Maybe if I could force my app to use the same datePicker that contacts app use when you add a birthday... But I can't find out how to do this.

 

[teea]

Okay, I think that datePicker from contacts app is related to this path: packages/apps/Contacts/src/com/android/contacts/datepicker/DatePicker.java

And I got an idea - maybe it's possible to change default datePicker with that one from contacts app? It may fix the issue for now, but I don't know how to do it, sadly.

 

[ingbrzy]

I think it will be fixed tomorrow by MIUI China... Dont waste your time and we will see what will bring new year..

 

[teea]

I hope they will

 

[1982Strand]

It's a bug in framework2.jar (on i9300), which xiaomi fixed for I9300 at least. I think it's odd though, that the exact same bug would be present on other phones when they are already aware of it?? But then again, it's not all phones that have the bug..

Anyways, not much to do than wait until the devs fixes it, sorry..

@ my commodore 64

 

[ingbrzy]

It comes when is new phone added to JB base... Same happened to i9300...

 

[ingbrzy]

It's a bug in framework2.jar (on i9300), which xiaomi fixed for I9300 at least. I think it's odd though, that the exact same bug would be present on other phones when they are already aware of it?? But then again, it's not all phones that have the bug..

Anyways, not much to do than wait until the devs fixes it, sorry..

@ my commodore 64

is it fixed in 3.1.11...?