Related
I have a rooted g1 with cyanogen 4.2.5 and gmail keeps stopping unexpectedly and then it ask me to force close...just started today any ideas on what i can do?
welcome
Welcome to my world
I have same problem except my gmail automaticly forecloses on me so yeah no clu yet
Gmail Force Closing
Same thing here no clue why ??? and cant seem to find help.
yeah thats what i mean it doesnt even let me open at all
did you try flashing the adp image and flashing cyan on top?
mine works only regular.. i cant add no kinda theme work to it!! succs!
I have this problem too. This is a serious issue. I've tried reverting to old nandroid backups, wiping, everything- the problem still persists though.
What other mods have you guys tried that could possibly be contributing? I tried the Navigation in Maps and Stericson's lockscreen, but it really should not make a difference since I tried with a wipe and still have the Force Close issue.
B-man007 said:
did you try flashing the adp image and flashing cyan on top?
Click to expand...
Click to collapse
I did try this. Still doesn't work.
I just searched and found this:
http://forum.xda-developers.com/showthread.php?p=4958016#post4958016
Trying it as I type this. It looks like I don't have Gmail Storage as an app anymore, don't know why. I'm going to update to ADP, then Cyanogen4.2.5 again and try clearing the cache from there.
Proxin said:
I have this problem too. This is a serious issue. I've tried reverting to old nandroid backups, wiping, everything- the problem still persists though.
What other mods have you guys tried that could possibly be contributing? I tried the Navigation in Maps and Stericson's lockscreen, but it really should not make a difference since I tried with a wipe and still have the Force Close issue.
I did try this. Still doesn't work.
Click to expand...
Click to collapse
Can you guys pull a logcat? I had this same problem with the themes out now ( i flashed my template and then cyans rom, everything worked fine after that for me)
Maybe they didn't port them to 4.2.5 right
EDIT: If you tried an older version of Stericsons lockscreen (as in the one that was the first 4.2.5) , it probably caused the error. I'm 90% sure thats the reason it happened in the first place.
B-man007 said:
Can you guys pull a logcat? I had this same problem with the themes out now ( i flashed my template and then cyans rom, everything worked fine after that for me)
Maybe they didn't port them to 4.2.5 right
EDIT: If you tried an older version of Stericsons lockscreen (as in the one that was the first 4.2.5) , it probably caused the error. I'm 90% sure thats the reason it happened in the first place.
Click to expand...
Click to collapse
So how can it be fixed, then? New lockscreen?
That doesn't make much sense to me because I have wiped on multiple versions that didn't include the lockscreen, and it still didn't work.
Proxin said:
So how can it be fixed, then? New lockscreen?
That doesn't make much sense to me because I have wiped on multiple versions that didn't include the lockscreen, and it still didn't work.
Click to expand...
Click to collapse
Well it would be easier to find whats wrong if you provided a logcat. Lots of things can cause it
B-man007 said:
Well it would be easier to find whats wrong if you provided a logcat. Lots of things can cause it
Click to expand...
Click to collapse
I'll try to get you one. It usually just keeps moving for me so I can never really copy it--
Scratch that. I just tried the devphone-to-CM4.2.5 and a wipe, and got Gmail working.
I'm going to try restoring my data with Backup for Root Users and see if the problem persists after it's restored.
The problem's not there anymore. I wonder what happened.
D/dalvikvm( 234): GC freed 4310 objects / 215352 bytes in 127ms
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.androi
d.gm/.ConversationListActivityGmail }
I/ActivityManager( 144): Start proc com.google.android.gm for activity com.goog
le.android.gm/.ConversationListActivityGmail: pid=736 uid=10036 gids={3003}
I/ActivityThread( 736): Publishing provider com.google.android.gm.attachmentspr
eviews: com.google.android.gm.AttachmentPreviewProvider
I/ActivityThread( 736): Publishing provider com.google.android.gmail.Suggestion
Provider: com.google.android.gm.SuggestionsProvider
I/ActivityThread( 736): Publishing provider com.google.android.gm.status: com.g
oogle.android.gm.SenderStatusProvider
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x2800000 cmp=com.google.android
.gm/.ConversationListActivity }
V/Gmail ( 736): onCreate(), id=com.google.android.gm.ConversationListActivity
@43679d08
I/ActivityManager( 144): Starting activity: Intent { flg=0x2000000 cmp=com.goog
le.android.gm/.WaitActivity (has extras) }
I/ActivityManager( 144): Displayed activity com.google.android.gm/.Conversation
ListActivity: 88 ms (total 539 ms)
W/InputManagerService( 144): Starting input on non-focused client com.android.i
[email protected] 0 (uid=10036 pid=736)
W/InputManagerService( 144): Client not active, ignoring focus gain of: com.and
[email protected] 37082a0
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
m.android.internal.view.IInputMethodClient$Stub$Pr [email protected]
D/ForecastProvider( 510): query() with uri=content://com.androidapps.widget.wea
ther2/appwidgets/5
D/ForecastProvider( 510): query() with uri=content://com.androidapps.widget.wea
ther2/appwidgets/5
D/dalvikvm( 510): GC freed 853 objects / 448232 bytes in 80ms
I/ActivityManager( 144): Process com.google.android.gm (pid 736) has died.
D/dalvikvm( 234): GC freed 3207 objects / 163008 bytes in 132ms
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/
.Launcher }
I/ActivityManager( 144): Starting activity: Intent { act=android.settings.SETTI
NGS flg=0x10200000 cmp=com.android.settings/.Settings }
I/ActivityManager( 144): Starting activity: Intent { cmp=com.android.providers.
subscribedfeeds/com.android.settings.SyncSettings }
W/InputManagerService( 144): Starting input on non-focused client android.view.
[email protected] (uid=1000 pid=144)
W/InputManagerService( 144): Client not active, ignoring focus gain of: android
[email protected]
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
m.android.internal.view.IInputMethodClient$Stub$Pr [email protected]
I/ActivityManager( 144): Starting activity: Intent { cmp=com.android.providers.
subscribedfeeds/com.android.settings.SyncSettings }
W/InputManagerService( 144): Starting input on non-focused client android.view.
[email protected] (uid=1000 pid=144)
W/InputManagerService( 144): Client not active, ignoring focus gain of: android
[email protected]
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
m.android.internal.view.IInputMethodClient$Stub$Pr [email protected]
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/
.Launcher }
W/InputManagerService( 144): Starting input on non-focused client com.android.i
[email protected] 8 (uid=1000 pid=699)
Please post logcats in CODE tags. it makes it easier to read
are you sure this is where the crash is happening? i dont see any thrown exceptions
yup this is what happen everytime i opened gmail..and open seting?data sync..both just close..
Please post logcats in CODE tags. it makes it easier to read
Click to expand...
Click to collapse
how do i do that?
D/dalvikvm( 510): GC freed 853 objects / 448232 bytes in 80ms
I/ActivityManager( 144): Process com.google.android.gm (pid 736) has died.
I/ActivityManager( 144): Starting activity: Intent { act=android.settings.SETTI
NGS flg=0x10200000 cmp=com.android.settings/.Settings }
I/ActivityManager( 144): Starting activity: Intent { cmp=com.android.providers.
subscribedfeeds/com.android.settings.SyncSettings }
heres a new log cat with lucks turn theme!
same issue here after using luckys turn thems on cm 4.2.5
well mine is on EVERY theme i try to install... marks theme..dark theme...lucks theme.. so i know its more my phone!
Ive got the same problem here, running 4.2.5
Did I read correctly, that you can flash the devphone 1.6, then to 4.2.5, as if you were coming from a lower grade version of CyanogenMod?
Kinda need my Gmail app, the stock generic email app works in a pinch, but isn't as flexible at all.
I reverted back to Cyan 4.2.5 after trying out Android 2.0 Stock Sapphire theme, performance wasn't all that great. Now my gmail wont launch. Did a backup, wipe and and applied 4.2.5 again still getting force close on launching gmail.
jasallis3 said:
Ive got the same problem here, running 4.2.5
Did I read correctly, that you can flash the devphone 1.6, then to 4.2.5, as if you were coming from a lower grade version of CyanogenMod?
Kinda need my Gmail app, the stock generic email app works in a pinch, but isn't as flexible at all.
Click to expand...
Click to collapse
Yes thats correct
@mekoche, try the above, or flash my template and then flash cyan on top
Update:
I just happened to try this again with no SIM in the phone, using wifi, and the browser worked perfectly. I even had an email from last night stuck in the outbox, and it went right out. So, what is it about the SIM card that is preventing the browser, Gmail app, and maybe more, from connecting? I get data for the widgets, apps, suggested search, etc. As soon as I put the SIM in, all data to and from the browser & Gmail stalls out. What is it about having a SIM card in place that is killing connectivity to selected apps?
So, I've flashed a bunch of different ROMs and I simply can't get the web browser to function. At all. It just times out, period. Everything but the browser itself works fine. I posted this thread [XDA-Developers] about three months ago before I gave up and bought another phone. This is still bugging me though, and I want to learn how to fix it. I don't want to re-post all the troubleshooting steps again from the other post, so I've got the logcat and a screenshot of the browser. What am I missing?
Here's the logcat copy, it's also a an attachment below:
__________________________________________________________________
I/ActivityManager( 355): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.android.browser/.BrowserActivity }
I/ActivityThread( 1613): Publishing provider contacts;com.android.contacts: com.android.providers.contacts.ContactsProvider2
I/ActivityManager( 355): Start proc com.android.browser for activity com.android.browser/.BrowserActivity: pid=1622 uid=10023 gids={3003, 1015, 1003}
I/ActivityThread( 1622): Publishing provider browser: com.android.browser.BrowserProvider
D/dalvikvm( 1613): GC freed 3240 objects / 245584 bytes in 278ms
W/ContactAggregator( 1613): No more aggregation requests
W/TabControl( 1622): Fail in restoreState, load home page.
I/ActivityManager( 355): Displayed activity com.android.browser/.BrowserActivity: 2424 ms (total 25427 ms)
I/WindowManager( 355): WIN DEATH: Window{43f7faf0 com.android.settings/com.android.settings.ApplicationSettings paused=false}
I/ActivityManager( 355): Process com.android.settings (pid 1309) has died.
I/WindowManager( 355): WIN DEATH: Window{43d9fb20 com.android.settings/com.android.settings.ManageApplications paused=false}
I/ActivityManager( 355): Low Memory: No more background processes.
I/ActivityThread( 1613): Publishing provider call_log: com.android.providers.contacts.CallLogProvider
D/Gmail ( 569): MailProvider.query: content://gmail-ls/labels/[email protected]/(null, null)
D/skia ( 355): purging 167K from font cache [16 entries]
D/dalvikvm( 355): GC freed 5859 objects / 258664 bytes in 919ms
I/ActivityManager( 355): Process android.process.acore (pid 1613) has died.
I/ActivityManager( 355): Low Memory: No more background processes.
D/dalvikvm( 569): GC freed 494 objects / 22544 bytes in 529ms
D/dalvikvm( 549): GC freed 1171 objects / 47768 bytes in 353ms
D/dalvikvm( 634): GC freed 186 objects / 7680 bytes in 447ms
D/skia ( 545): purging 68K from font cache [9 entries]
D/dalvikvm( 545): GC freed 789 objects / 35576 bytes in 987ms
D/dalvikvm( 792): GC freed 34 objects / 1200 bytes in 881ms
D/GpsLocationProvider( 355): NetworkThread out of wake loop
D/GpsXtraDownloader( 355): Downloading XTRA data from http://xtra1.gpsonextra.net/xtra.bin
I/ActivityManager( 355): Start proc com.levelup.beautifulwidgets for broadcast com.levelup.beautifulwidgets/.HomeWidget14: pid=1641 uid=10045 gids={3003, 3002, 3001, 1015, 1003}
D/WifiService( 355): ACTION_BATTERY_CHANGED pluggedType: 2
I/power ( 355): *** set_screen_state 0
D/WifiService( 355): ACTION_SCREEN_OFF
D/SurfaceFlinger( 355): About to give-up screen, flinger = 0x11f140
I/power ( 355): *** set_screen_state 1
D/WifiService( 355): ACTION_SCREEN_ON
D/SurfaceFlinger( 355): Screen about to return, flinger = 0x11f140
D/GpsXtraDownloader( 355): error java.net.SocketTimeoutException: Socket is not connected
D/dalvikvm( 355): threadid=119 wakeup: interrupted
D/GpsXtraDownloader( 355): Downloading XTRA data from http://xtra2.gpsonextra.net/xtra.bin
E/browser ( 1622): onReceivedError -6 http://www.google.com/m The connection to the server was unsuccessful.
D/dalvikvm( 1622): GC freed 7289 objects / 285672 bytes in 104ms
W/dalvikvm( 1622): JNI WARNING: DeleteLocalRef(0x43c204e8) failed to find entry (valid=1)
W/ActivityManager( 355): Activity idle timeout for HistoryRecord{43f74fe0 com.android.browser/.BrowserActivity}
D/GpsXtraDownloader( 355): error java.net.SocketTimeoutException: Socket is not connected
D/dalvikvm( 355): threadid=119 wakeup: interrupted
D/GpsXtraDownloader( 355): Downloading XTRA data from http://xtra3.gpsonextra.net/xtra.bin
D/GpsXtraDownloader( 355): error java.net.SocketTimeoutException: Socket is not connected
D/dalvikvm( 355): threadid=119 wakeup: interrupted
D/GpsLocationProvider( 355): NetworkThread wait for 299998ms
D/dalvikvm( 792): GC freed 4 objects / 152 bytes in 1693ms
I/ActivityManager( 355): Start proc com.android.settings for broadcast com.android.settings/.widget.SettingsAppWidgetProvider: pid=1651 uid=1000 gids={3003, 3002, 3001}
I/ActivityManager( 355): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.fede.launcher/.Launcher }
W/InputManagerService( 355): Starting input on non-focused client [email protected] (uid=10023 pid=1622)
I/ActivityManager( 355): Process com.levelup.beautifulwidgets (pid 1641) has died.
I/ActivityManager( 355): Start proc com.levelup.beautifulwidgets for broadcast com.levelup.beautifulwidgets/.HomeWidget14: pid=1657 uid=10045 gids={3003, 3002, 3001, 1015, 1003}
I/ActivityManager( 355): Process com.android.settings (pid 1651) has died.
D/dalvikvm( 545): GC freed 3603 objects / 312392 bytes in 109ms
I/ActivityManager( 355): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.term/.Term }
I/ActivityManager( 355): Start proc com.android.term for activity com.android.term/.Term: pid=1663 uid=10004 gids={}
E/Term ( 1663): onCreate
D/dalvikvm( 1663): Trying to load lib /system/lib/libterm.so 0x43bf4338
D/dalvikvm( 1663): Added shared lib /system/lib/libterm.so 0x43bf4338
I/Exec ( 1663): JNI_OnLoad
I/Term ( 1663): waiting for: 1669
Weird problem -> weird idea and possible solution!
Perhaps you have some kind of NAND error in the memory area where the browser app lies. This may sound kind of random, especially as it happens with different ROMs, but: I guess when installing a Rom, everything goes alphabetically. This means that the *a*pps folder goes first. It contais *b*rowser.apk which is installed as the third or 4th app. So it will be roughly in the same position for *any* Rom (Except the newer ones that contain ADWLauncher.apk).
You could try the following:
1) Install a ROM of your choice, best one of those that didn't work (just to test the theory...)
2) extract the browser.apk from the rom zip to /data/myapp/browser.apk on the phone
3) delete the original browser.apk in /system/app
4) create a symlink on the new browser.apk with 'ln -s /system/app/browser.apk /data/myapp/browser.apk'
5) Cross fingers and surf to google.com to see what happens
Plan B to test this: Install CM6 RC3 which contains ADWLauncher. If there is an error in your nand it should now affect the launcher instead of the browser, as the launcher is quite big...
€: If this really is the problem, you could use a custom version of Firerats MTD Patch to move your system partition a few MB so the defective area is not used anymore. It would cost you a few mb nand space, but everything should be fine then.
Thanks for the reply, mblaster. It looks like I edited my post as you were typing the reply.
For some reason, the one thing I never tried was using the phone with no SIM. I pulled the SIM out of my G1 and gave up in disgust again (this problem has been plaguing me for 3+ months now...). I put it in my new phone, and left the new one to charge. I powered the G1 back on, SIM removed, just for the heck of it.
Everything works perfectly with no SIM! Except I'm stuck using wifi, no calls or mobile data, obviously. I'm smart enough to guess this is an important clue, but not smart enough to identify and correct the root cause. I'll keep searching until I get it, or someone points out what is wrong.
I suspect this has something to do with the Google apps add-on, too. I can't get any ROMs to a stable boot if I flash the ROM and Google add-on zips together. I have to get the ROM loaded and running, then flash an older version of the add-ons to get my market & Gmail, etc. If I don't do it that way, I can't even get through the initial sign in, even to press the "skip" button to do it later. It's error after error until I just pull the battery. Not singling out any ROM in particular here, I've tried dozens of variations.
I hope this SIM clue is what helps me figure out what's wrong. I don't have a clue about the NAND on the phone, and I'd like to know how to check it's integrity, or flash a known good copy again in case it's become corrupted. Way over my head now, I'm going to read some more and search again.
Tiznom said:
...
I hope this SIM clue is what helps me figure out what's wrong. I don't have a clue about the NAND on the phone, and I'd like to know how to check it's integrity, or flash a known good copy again in case it's become corrupted. Way over my head now, I'm going to read some more and search again.
Click to expand...
Click to collapse
The NAND is the physical memory of your phone, like a harddisk on your computer. One way to check for errors could be to copy some files to your device and back and check if they are still the same.
You could e.g. "adb shell md5sum /system/app/browser.apk" (or any other file) and then compare it with an md5sum calculated from the browser.apk extracted from the .zip of the flashed rom file on your pc (need to get some extra software for that as windows can't do it out of the box).
If the numbers differ, there is definitely something wrong. Don't know if there is a better way to test this.
Still this does not explain why it works without a sim card, but this could be coincidence.
€: If you suspect the google addon, you can easily try to flash a rom without a google addon and see if everything works properly.
It's the Google add-ons somehow. I'm having all kinds of problems with Google sites reloading very quickly, and I don't have a clue how to correct it. I started out troubleshooting the phone and now it's worse. I've pulled the battery out of the G1 again and now I can use Google sites in my desktop browser fine.
I'll try comparing the md5 sums and see what I get. I'm using Ubuntu and I learned how to do it from troubleshooting the ROMs.
I think I'm looking at something I will never solve. I bought a second Android phone that I won't dare experiment with until I get all this sorted out. It's never been rooted and everything on it works perfectly. While I like the idea of rooting and experimenting, I still need a phone that will actually work. Plus, I can always revert the G1 to the stock un-rooted 1.6 ROM, it works fine. As soon as I try rooting, I get nothing but problem after problem.
I had this problem with my Magic on CM 5.0.8. It was the default APN settings that was causing the problem for me. I just manually added the essential APN settings and it worked. I'm on 2degrees mobile in New Zealand. This only happened with this sim, worked fine with a vodafone one.
Hello,
I'm on xwjvb with cf-root and I have a strange bug: if I open the gallery, check some photos and then press the home button, touchwiz restart. I mean all widgets are repaint and application list needs a reload. Does anybody experience the same bug?
thanx
Tested = no.
Suggest factory reset .
jje
after further investigation, it happens only after this event:
Code:
D/dalvikvm(19706): GC_EXTERNAL_ALLOC freed 35K, 51% free 3527K/7175K, external 2
1313K/23361K, paused 23ms
I/ActivityManager( 482): Process com.levelup.beautifulwidgets (pid 20149) has d
ied.
I/ActivityManager( 482): Low Memory: No more background processes.
I/WindowManager( 482): WIN DEATH: Window{40a455d0 com.sec.android.app.twlaunche
r/com.sec.android.app.twlauncher.Launcher paused=false}
I/ActivityManager( 482): Process com.sec.android.app.twlauncher (pid 19887) has
died.
I/ActivityManager( 482): Low Memory: No more background processes.
It seems that some pictures in the gallery cause too much memory pressure and that all background processes are killed.
ok->it only happens if I uncheck the "RAM: Min-free" option in the cf-root tweaks app. When checked, the luncher is never killed. =>wrong it happens even when the option is checked. I tried a factory reset but it doesn't help.
Am I really the only one experiencing toucwhiz restart like this:
"I/ActivityManager( 459): Process com.sec.android.app.twlauncher (pid 19786) has
died."
I've read on other forums that gingerbread is more aggressive in terms of memory management than froyo. I've never seen such things in froyo. Only since I've flashed xwjvb. Maybe it's because it's not yet the official release?
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
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...