I am not sure why I am experiencing this problem. My phone was working fine last week, then I flashed xTHEME v1.2 on cm 4.0.4 and my phone gets stuck at the 2nd bootscreen. I wiped, then flashed 4.0.4 again and I can boot normally, but then it happened again today. Logcat below, hopefully someone can explain the error.
http://pastebin.com/f362fbdc3
Lemme know if you need more information
Code:
E/AndroidRuntime( 4678): Uncaught handler: thread android.server.ServerThread exiting due to uncaught exception
E/AndroidRuntime( 4678): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 4678): java.lang.IndexOutOfBoundsException: Invalid location 1, size is 1
E/AndroidRuntime( 4678): at java.util.ArrayList.get(ArrayList.java:353)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.readStateFromFileLocked(AppWidgetService.java:972)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.loadStateLocked(AppWidgetService.java:750)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.systemReady(AppWidgetService.java:125)
E/AndroidRuntime( 4678): at com.android.server.ServerThread.run(SystemServer.java:346)
uncaught exception there right before everything crashes.... do you have any widgets installed?
The only widgets I use are Weather Widget - Donate + addon, GPS OnOff, and tCalendar.
unknown.soul said:
The only widgets I use are Weather Widget - Donate + addon, GPS OnOff, and tCalendar.
Click to expand...
Click to collapse
Try to disable them, boot up, reenable them one by one to see whats causing it to happen. I can't see anything else in the log that could be the cause of it, but im not an expert
tCalendar seemed to be the culprit and I found out that tCalendar != tCalendarWidget. The former is not for 1.5, but according to the market description it should be compatible. Thanks for isolating the issue from that log.
unknown.soul said:
tCalendar seemed to be the culprit and I found out that tCalendar != tCalendarWidget. The former is not for 1.5, but according to the market description it should be compatible. Thanks for isolating the issue from that log.
Click to expand...
Click to collapse
no problem, glad to see you got it to work. I thought that would be an app problem to cause trouble because I used the other two on cyans exp. builds. Hadn't heard of the tcalendar app.
Thanks for providing links to the app, it makes it much more useful for someone searching for an answer to find one. Also, could you edit the thread title to include [SOLVED] ?
btw it wasnt the tcalendar widget itself, but the tcalendar app? thats weird. does it have a widget of its own packaged with the app?
It's just a name difference, tCalendar is only a widget.
Related
Anyone know what could be causing this? Appmanager Pro is crashing when I try to launch it. Only thigns on my phone are Cyan 4.25 and the navigation_update.zip.
Heres a logcat:
Code:
11-17 22:07:10.156 W/dalvikvm( 665): threadid=15: thread exiting with uncaught exception (group=0x4001e170)
11-17 22:07:10.156 E/AndroidRuntime( 665): Uncaught handler: thread Thread-9 exiting due to uncaught exception
11-17 22:07:10.166 E/AndroidRuntime( 665): java.lang.NullPointerException
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.FileUtils.getDirSize(FileUtils.java:171)
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.FileUtils.getDirSize(FileUtils.java:175)
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.AppManagerPro$ResourceLoaderThread.run(AppManagerPro.java:449)
11-17 22:07:10.196 I/Process ( 143): Sending signal. PID: 665 SIG: 3
11-17 22:07:10.196 I/dalvikvm( 665): threadid=7: reacting to signal 3
11-17 22:07:10.326 I/dalvikvm( 665): Wrote stack trace to '/data/anr/traces.txt'
11-17 22:07:10.866 D/dalvikvm( 515): GC freed 528 objects / 294640 bytes in 128ms
11-17 22:07:12.036 I/Process ( 665): Sending signal. PID: 665 SIG: 9
11-17 22:07:12.066 I/ActivityManager( 143): Process com.think_android.appmanagerpro (pid 665) has died.
11-17 22:07:12.076 I/WindowManager( 143): WIN DEATH: Window{43938b48 com.think_android.appmanagerpro/com.think_android.appmanagerpro.AppManagerPro paused=false}
11-17 22:07:12.126 W/UsageStats( 143): Unexpected resume of com.android.launcher while already resumed in com.think_android.appmanagerpro
11-17 22:07:12.156 W/InputManagerService( 143): Got RemoteException sending setActive(false) notification to pid 665 uid 10038
11-17 22:07:14.886 I/XT9IME ( 351): [finishInput]
11-17 22:07:15.216 D/dalvikvm( 192): GC freed 2925 objects / 133408 bytes in 123ms
Has it been updated for 1.6? NullPointerException usually require looking through the code to troubleshoot lol. its probably not programmed well
B-man007 said:
Has it been updated for 1.6? NullPointerException usually require looking through the code to troubleshoot lol. its probably not programmed well
Click to expand...
Click to collapse
I'm thinking it has something to do with the update_navigation.zip I flashed cause I know it did something with the build.props and whatnot. And it also worked before I flashed this.
I don't use that but how much did it modify your build.prop?
does your phone say android 2.0 or is it still showing 1.6?
B-man007 said:
I don't use that but how much did it modify your build.prop?
does your phone say android 2.0 or is it still showing 1.6?
Click to expand...
Click to collapse
I believe it changed 1-2 lines and yes my phone still shows 1.6. I just looked at my app drawer to and it shows I have 2 settings apps, odd I'm going to restart my phone see if it goes away.
I hate to say this but it's not nav....
And I don't think it's CM4.2.5.
I know this because I was fine on a fresh install until I reinstalled all my other apps. Then I started getting crashes. I think it was a combination of advanced launcher,and google voice that started the misbehavior.
Maybe it's just one of them.
My solution was...
I dropped appmanager. I loved that program, but discovered that Astro can back-up your apk's too. It just doesn't uninstall existing apks.
But... advanced task manager does have an uninstall feature, and it allows me to slap mis-behaving programs around as well as services.
The simplicity of one program, replaced by the combination of 2 more powerful programs.
But hey, what do I care....I have Apps2sd!
[email protected] said:
I hate to say this but it's not nav....
And I don't think it's CM4.2.5.
I know this because I was fine on a fresh install until I reinstalled all my other apps. Then I started getting crashes. I think it was a combination of advanced launcher,and google voice that started the misbehavior.
Maybe it's just one of them.
My solution was...
I dropped appmanager. I loved that program, but discovered that Astro can back-up your apk's too. It just doesn't uninstall existing apks.
But... advanced task manager does have an uninstall feature, and it allows me to slap mis-behaving programs around as well as services.
The simplicity of one program, replaced by the combination of 2 more powerful programs.
But hey, what do I care....I have Apps2sd!
Click to expand...
Click to collapse
I sent a email to the dev with the situation and what not. but Google voice to me never interfered before with app manager. Hopefully I get it figured out soon cause appmanager made my life alot simpler ><, I am willing to try new things but if this gets repaired it would be greater!
i have all 3 google voice..nav..and app manager pro working.. just fine on mine..
Just to clarify...
I am almost certain it's not nav because I had stopped using app manager, before even thinking of adding nav to the system.
That didn't really come out in the first post.
http://code.google.com/p/cyanogenmod/issues/detail?id=744#c0
Issue with the latest mod
did you guys try reinstalling the app? maybe it requires additional permissions after the latest rom upgrade
B-man007 said:
http://code.google.com/p/cyanogenmod/issues/detail?id=744#c0
Issue with the latest mod
did you guys try reinstalling the app? maybe it requires additional permissions after the latest rom upgrade
Click to expand...
Click to collapse
Seems like im not the only one experiencing the issues though >< I guess I'll just try out astro
had the issue also and I had it before I decided to flash the update_navigation zip file so I know its not that... it was working then it stopped after something dont know what it is... didnt have a theme nothing completely fresh install wiped everything didn't have ext partition so its something weird
I got a hold of the dev and gave him a complete catlog. He released an update on the market and problem solved!
I just ran into an interesting problem and was able to solve it, I figured I'd post it here in case anyone else runs into it.
So I got my NC on Thursday and promptly rooted it on Friday morning, everything was smooth sailing until I started installing a bunch of apps and noticed that some things were randomly failing. Specifically baffling was the "Downloads" view in the market app. I used the Log Collector app to take a look at the logs and saw some exceptions like so:
12-21 12:08:54.890 E/AndroidRuntime( 1719): java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: android.database.sqlite.SQLiteException: no such table: main.audio: , while compiling: SELECT album_art FROM album_info
12-21 12:08:54.890 E/AndroidRuntime( 1719): at android.app.ActivityThread.installProvider(ActivityThread.java)
Some snooping around revealed that there's a missing sql view in /data/data/com.android.providers.media/databases/internal.db. Sometime during NC startup some app tries to delete the view and rebuild it, but since the view was already gone it couldn't delete and therefore failed:
12-21 13:42:30.475 E/Database( 1867): Failure 1 (use DROP TABLE to delete table audio) on 0x2c50e0 when preparing 'DROP VIEW IF EXISTS audio'.
12-21 13:42:30.475 D/AndroidRuntime( 1867): Shutting down VM
12-21 13:42:30.475 W/dalvikvm( 1867): threadid=3: thread exiting with uncaught exception (group=0x4001b170)
12-21 13:42:30.475 E/AndroidRuntime( 1867): Uncaught handler: thread main exiting due to uncaught exception
12-21 13:42:30.491 E/AndroidRuntime( 1867): java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: android.database.sqlite.SQLiteException: use DROP TABLE to delete table audio: DROP VIEW IF EXISTS audio
Solution - pull internal.db off the device, create a dummy view named audio in the database (I used Sqliteman on ubuntu) and push it back to the NC.
Reboot, problem fixed. Hope someone finds some use in this writeup.
Hi guys
There's this app called buienalarm. It's really helpful, but sometimes it works and other times it causes the phone to soft reboot, crash and reboot. Events are happening in this order FYI. I have no idea what is causing this, but I used alogrec for record the logcat. Can someone tell me what's going on?
E/ ( 6050): netstack: STAT_HUB - App org.yoki.android.buienalarm isn't supported
W/dalvikvm( 1016): threadid=11: thread exiting with uncaught exception (group=0x41737658)
D/AdSDK ( 6050): ***** StartLoadContent, url=http://merlin.nakko.com/index.php?count=1&key=6&mcc=204&mnc=08&site=289&resizable=1&ua=Mozilla%2F5.0�%28Linux%3B�%3Bɷ殢❾�.3%3B�nl%3B詗�%2F12.1.A.1.205%29ʚ敹枛⨫�%2F534.30�%28KHTML%2C阩Ỹ果�%29嗪�%2F4.0㊆槶�%2F534.30&zone=1&request_counter=0&package_name=org.yoki.android.buienalarm&uid=WIFIMAC%3A00%3Aeb%3A2d%3A6c%3A79%3A96&android_id=b073a717e4807c87&bucket=%7B%7D
D/AdSDK ( 6050): ***** runWithHttpURLConnection, START HTTP EXECUTION
D/AdSDK ( 6050): ***** headerUserAgent=Buienalarm/121
D/AdSDK ( 6050): ***** runWithHttpURLConnection, END HTTP EXECUTION
E/AndroidRuntime( 1016): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 1016): java.lang.IllegalArgumentException: provider doesn't exisit: null
Another part of the log states:
I/ValueStore( 6050): Creating new value store instance
V/GCMRegistrar( 6050): Registering receiver
D/GCMRegistrar( 6050): resetting backoff for org.yoki.android.buienalarm
V/GCMRegistrar( 6050): Unregistering app org.yoki.android.buienalarm
D/dalvikvm( 6050): GC_FOR_ALLOC freed 2401K, 32% free 8577K/12496K, paused 15ms, total 16ms
Weird case you've got there.
I use Buienrader almost everyday and I have absolutly no issues.
From what I understand from the parts of the logcat it makes the system crash when loading content..
@mrjraider
You're using buienradar or buienalarm? Two different apps can you tell how I can get this back to work? Or who I should contact for this
Haha sorry, I do use both actually and also buienalarm gives no issues..
Can you recommend someone who I can contact with for this log?
I think no one because the buienalarm app hasnt been updated since january 2014
I mean who can figure out exactly what's crashing and how I can fix it
After I change some settings in module, my device immediatelly reboots. Not sure what causes this.
FATAL EXCEPTION IN SYSTEM PROCESS: XSharedPreferences-load @rovo89
I took logcat.
E/AndroidRuntime( 2683): *** FATAL EXCEPTION IN SYSTEM PROCESS: XSharedPreferences-load
E/AndroidRuntime( 2683): java.lang.IllegalArgumentException: Offset 0 / Length 0 is out of range for /data/data/com.pyler.xinstaller/shared_prefs/com.pyler.xinstaller_preferences.xml with size 2515
E/AndroidRuntime( 2683): at de.robv.android.xposed.services.BinderService.readFile(BinderService.java:130)
E/AndroidRuntime( 2683): at de.robv.android.xposed.services.BinderService.readFile(BinderService.java:93)
E/AndroidRuntime( 2683): at de.robv.android.xposed.services.BaseService.getFileInputStream(BaseService.java:131)
E/AndroidRuntime( 2683): at de.robv.android.xposed.XSharedPreferences.loadFromDiskLocked(XSharedPreferences.java:120)
E/AndroidRuntime( 2683): at de.robv.android.xposed.XSharedPreferences.access$0(XSharedPreferences.java:112)
E/AndroidRuntime( 2683): at de.robv.android.xposed.XSharedPreferences$1.run(XSharedPreferences.java:105)
Click to expand...
Click to collapse
Full log: http://tny.cz/5754f922
Maybe related, it occurs only "rarely":
Code:
W/XSharedPreferen(10796): type=1400 audit(0.0:397): avc: denied { open } for name="preferences.xml" dev="mmcblk0p30" ino=376838 scontext=u:r:system_server:s0 tcontext=u:object_r:app_data_file:s0 tclass=file
If you have quite enough hooks (=settings for them) and you change these settings (all/almost all of them) sometimes device reboots suddenly. Not good thing. Any solution?
I read in docs that "reload" may be on enforced selinux "extensive". What exactly does @rovo89 mean? Should we worry or not?"
pyler said:
I read in docs that "reload" may be on enforced selinux "extensive". What exactly does @rovo89 mean? Should we worry or not?"
Click to expand...
Click to collapse
It actually says "expensive", i.e. it needs way more resources (time, CPU ticks) in situations where the native services have to be used in order to work around SELinux restrictions. I haven't done performance tests, but I wouldn't call this function once a second or so.
How often do you call reload()? The error you posted looks like the file is read while it's being written. In the full log, four (!) errors are shown between the start of dex2oat process 2409 and it's end 284.616ms later. So it seems like you call reload() very frequently. Even with possible fixes to come, you should really avoid that. If you can't find a place to reload the settings just when they've been changed (or in a function that is called at most every few seconds), create a helper function that stores the timestamp of the last reload and only calls through to XSharedPreferences every few seconds.
I plan to make the exception messages more exact by filling them from the native side. Length = 0 is misleading here, it actually means that the whole file should be read. And also, I will either see if I can wrap some of these exceptions in IOExceptions under certain circumstances, and/or catch any Throwable while reloading files. The "Error 13" exceptions were caught properly.
Well, I have cca 30 hooks (check) and in every hook I need to check for some preference and its value. I know "reload()" is called very very often. Anyway, on < LP it is OK.
But it doesn't crash everytime, sometimes I can change even 10 prefs and everything is OK and sometimes 2 or 3 prefs reboot device. But nowdays, it became better somehow.
Yes, I can disable reloading but then reboot will be required to apply changes (atleast on LP). But anyway, I will leave it as is, since looks like only me has (had) this issue, users haven't yet told me about this "bug".
I think it's a racing condition. If your reload() happens to be executed while the settings are written, it can crash. You can't compare this to older versions, as I didn't have to go through the hoops of using native services and stuff, I could access the files directly and check whether their size and modification time is unchanged. The latter is pretty fast, using native services is obviously much more work that the device needs to execute.
It probably won't crash in the next alpha version anymore, however the error might would appear in the log.
And as I said: You could have a per-process timer that makes sure that reload() is only executed every few seconds. Doesn't solve the root cause, but reduced the likelyhood that it happens.
Could this be solved with try - catch when loading prefs?
Hi, I would create this topic in "Java for Android" section, but I can't, so I post it here.
To the issue: My app always shutdown in random time interval (mostly from few minutes to something like 20 mins). The "App stopped working" messagebox appears. Biggest problem is, I don't do anything in app (like interacting with it), and it just random shutdown by itself. Here's logcat print:
Code:
07-15 20:34:16.595 27361-27363/test.game D/dalvikvm: GC_CONCURRENT freed 141
9K, 44% free 13902K/24391K, paused 4ms+9ms, total 66ms
07-15 20:34:28.997 27361-27363/test.game D/dalvikvm: GC_CONCURRENT freed 1416K, 43% free 13903K/24391K, paused 3ms+7ms, total 56ms
07-15 20:34:29.418 27361-27361/test.game D/AndroidRuntime: Shutting down VM
07-15 20:34:29.418 27361-27361/test.game W/dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x412b52a0)
07-15 20:34:29.498 27361-27361/test.game E/AndroidRuntime: FATAL EXCEPTION: main java.lang.IllegalStateException: onMeasure() did not set the measured dimension by calling setMeasuredDimension()
at android.view.View.measure(View.java:15293)
at android.widget.RelativeLayout.measureChildHorizontal(RelativeLayout.java:617)
at android.widget.RelativeLayout.onMeasure(RelativeLayout.java:399)
at android.view.View.measure(View.java:15288)
at android.widget.RelativeLayout.measureChildHorizontal(RelativeLayout.java:617)
at android.widget.RelativeLayout.onMeasure(RelativeLayout.java:399)
at android.view.View.measure(View.java:15288)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4876)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:15288)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4876)
at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1396)
at android.widget.LinearLayout.measureVertical(LinearLayout.java:681)
at android.widget.LinearLayout.onMeasure(LinearLayout.java:574)
at android.view.View.measure(View.java:15288)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4876)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2397)
at android.view.View.measure(View.java:15288)
at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:1974)
at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1217)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1390)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1113)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4481)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
at android.view.Choreographer.doCallbacks(Choreographer.java:555)
at android.view.Choreographer.doFrame(Choreographer.java:525)
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:137)
at android.app.ActivityThread.main(ActivityThread.java:4867)
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:1007)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:774)
at dalvik.system.NativeStart.main(Native Method)
One would say, it's because I didn't write setMeasuredDimension() when overriding method onMeasure(). Also, docs say you have to write this line to your onMeasure, otherwise the IllegalStateException will be thrown (see it here).
But I don't overriding onMeasure anywhere in my whole project, so problem is not here (at least not on my side in this case).
Few things to note:
- this is full logcat log, and any of these lines ("at android. ...") doesn't link to my code, all goes to source - that means all of these links are gray
- this exception always happens only on my S3 Mini (android 4.1.2), but never happened on my old Galaxy Ace S5830i (android 2.3.6) (and yes, I tested it alot - over 20hours on old phone and app still running!).
- never happened in emulator
- there are no "view resizing" operations running in background, which could cause this exception
I would like to post some code, but I have absolutely no idea where this exception could be thrown.
If someone can help, I'd be really, really grateful. I'm lost at this point...