- Mar 22, 2012
- 41
- 18
Hi. Is anyone else having issues with MIUI release 2.12.14 on SGS2?
I keep getting an "unfortunately the process com.android.phone has stopped" error, sporadically, and when I press the report MIUI button, it lists a bunch of java stuff... "android.database.CursorIndexOutOfBoundsExceptionm: Index 3 requested, with a size of 3 at android.database.AbstractCursor.checkPosition(AbstractCursor.java:400) at android.database"... etc.
Can't tell if it's the MIUI release or an App. Haven't seen the expected flurry of complaints/bug reports here, so perhaps it is not the ROM at fault.
It's causing my phonecalls to cut out mid call, and my alarm automatically skipped to snooze after a nanosecond of alarm sound this morning, causing me to be an hour late for work.
This behaviour began from the first reboot after upgrading to 2.12.14. I tried yesterday to roll back to 2.12.7, but the same error was even more frequent as to render the phone unusable, so I;m back on 2.12.14.
I'm a bit stuck in term s of diagnosing the problem as I just moved house, have no internet at home and 3G so lousy as to be unusable. So I can only connect here from work, where I can't install apps so can't do a logcat or anything.
Hope someone can help identify the problem.
Mark
I keep getting an "unfortunately the process com.android.phone has stopped" error, sporadically, and when I press the report MIUI button, it lists a bunch of java stuff... "android.database.CursorIndexOutOfBoundsExceptionm: Index 3 requested, with a size of 3 at android.database.AbstractCursor.checkPosition(AbstractCursor.java:400) at android.database"... etc.
Can't tell if it's the MIUI release or an App. Haven't seen the expected flurry of complaints/bug reports here, so perhaps it is not the ROM at fault.
It's causing my phonecalls to cut out mid call, and my alarm automatically skipped to snooze after a nanosecond of alarm sound this morning, causing me to be an hour late for work.
This behaviour began from the first reboot after upgrading to 2.12.14. I tried yesterday to roll back to 2.12.7, but the same error was even more frequent as to render the phone unusable, so I;m back on 2.12.14.
I'm a bit stuck in term s of diagnosing the problem as I just moved house, have no internet at home and 3G so lousy as to be unusable. So I can only connect here from work, where I can't install apps so can't do a logcat or anything.
Hope someone can help identify the problem.
Mark