Database Develop

Ext2/Ext3

sup peeps
im just wondering whats the diffrence between Ext2 and Ext3 and also could 1 or the other cause a coma/hanging issue on a hero rom if you have or dont have the right "Ext" so let me kno thx people

if you have cyanogen's recovery image go into the recovery console and type
Code:
upgrade_fs
reboot
ext3 has journaling which is a good thing. just do it.

wow....you didnt answer my question and i alrdy have ext3 answering my question just might help me with my coma problem so ya

RanT476 said:
wow....you didnt answer my question and i alrdy have ext3 answering my question just might help me with my coma problem so ya
Click to expand...
Click to collapse
i answered half of it. the coma issue, afaik, is related to a kernal panic. the last time i knew of the coma issue being present was in the use of unionfs and AUFS for apps2sd, but that has since been replaced by bind mounts and symlinks.

afaik? and how can i look at my log to see if the kernal is panicing whats the command for adb so i can see what the hell is going on so i can post it or something

RanT476 said:
afaik? and how can i look at my log to see if the kernal is panicing whats the command for adb so i can see what the hell is going on so i can post it or something
Click to expand...
Click to collapse
AFAIK = As Far As I Know
to check your log, #logcat

D/AndroidRuntime( 1911):
D/AndroidRuntime( 1911): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1911): CheckJNI is OFF
W/dalvikvm( 1911): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1911): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1911): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1911): VM cleaning up
D/dalvikvm( 1911): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1911): JNI_CreateJavaVM failed
E/AndroidRuntime( 1911): JNI_CreateJavaVM failed
D/AndroidRuntime( 1912):
D/AndroidRuntime( 1912): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1912): CheckJNI is OFF
W/dalvikvm( 1912): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1912): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1912): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1912): VM cleaning up
D/dalvikvm( 1912): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1912): JNI_CreateJavaVM failed
E/AndroidRuntime( 1912): JNI_CreateJavaVM failed
D/AndroidRuntime( 1913):
D/AndroidRuntime( 1913): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1913): CheckJNI is OFF
W/dalvikvm( 1913): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1913): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1913): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1913): VM cleaning up
D/dalvikvm( 1913): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1913): JNI_CreateJavaVM failed
E/AndroidRuntime( 1913): JNI_CreateJavaVM failed
D/AndroidRuntime( 1914):
D/AndroidRuntime( 1914): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1914): CheckJNI is OFF
W/dalvikvm( 1914): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1914): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1914): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1914): VM cleaning up
D/dalvikvm( 1914): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1914): JNI_CreateJavaVM failed
E/AndroidRuntime( 1914): JNI_CreateJavaVM failed
D/AndroidRuntime( 1915):
D/AndroidRuntime( 1915): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1915): CheckJNI is OFF
W/dalvikvm( 1915): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1915): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1915): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1915): VM cleaning up
D/dalvikvm( 1915): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1915): JNI_CreateJavaVM failed
E/AndroidRuntime( 1915): JNI_CreateJavaVM failed
D/AndroidRuntime( 1916):
D/AndroidRuntime( 1916): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1916): CheckJNI is OFF
W/dalvikvm( 1916): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1916): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1916): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1916): VM cleaning up
D/dalvikvm( 1916): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1916): JNI_CreateJavaVM failed
E/AndroidRuntime( 1916): JNI_CreateJavaVM failed
D/AndroidRuntime( 1917):
D/AndroidRuntime( 1917): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1917): CheckJNI is OFF
W/dalvikvm( 1917): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1917): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1917): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1917): VM cleaning up
D/dalvikvm( 1917): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1917): JNI_CreateJavaVM failed
E/AndroidRuntime( 1917): JNI_CreateJavaVM failed
D/AndroidRuntime( 1918):
D/AndroidRuntime( 1918): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1918): CheckJNI is OFF
W/dalvikvm( 1918): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1918): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1918): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1918): VM cleaning up
D/dalvikvm( 1918): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1918): JNI_CreateJavaVM failed
E/AndroidRuntime( 1918): JNI_CreateJavaVM failed
D/AndroidRuntime( 1919):
D/AndroidRuntime( 1919): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1919): CheckJNI is OFF
W/dalvikvm( 1919): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1919): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1919): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1919): VM cleaning up
D/dalvikvm( 1919): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1919): JNI_CreateJavaVM failed
E/AndroidRuntime( 1919): JNI_CreateJavaVM failed
D/AndroidRuntime( 1920):
D/AndroidRuntime( 1920): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1920): CheckJNI is OFF
W/dalvikvm( 1920): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1920): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1920): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1920): VM cleaning up
D/dalvikvm( 1920): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1920): JNI_CreateJavaVM failed
E/AndroidRuntime( 1920): JNI_CreateJavaVM failed
D/AndroidRuntime( 1921):
D/AndroidRuntime( 1921): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1921): CheckJNI is OFF
W/dalvikvm( 1921): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1921): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1921): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1921): VM cleaning up
D/dalvikvm( 1921): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1921): JNI_CreateJavaVM failed
E/AndroidRuntime( 1921): JNI_CreateJavaVM failed
D/AndroidRuntime( 1922):
D/AndroidRuntime( 1922): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1922): CheckJNI is OFF
W/dalvikvm( 1922): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1922): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1922): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1922): VM cleaning up
D/dalvikvm( 1922): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1922): JNI_CreateJavaVM failed
E/AndroidRuntime( 1922): JNI_CreateJavaVM failed
D/AndroidRuntime( 1923):
D/AndroidRuntime( 1923): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1923): CheckJNI is OFF
W/dalvikvm( 1923): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1923): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1923): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1923): VM cleaning up
D/dalvikvm( 1923): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1923): JNI_CreateJavaVM failed
E/AndroidRuntime( 1923): JNI_CreateJavaVM failed
D/AndroidRuntime( 1926):
D/AndroidRuntime( 1926): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1926): CheckJNI is OFF
W/dalvikvm( 1926): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1926): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1926): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1926): VM cleaning up
D/dalvikvm( 1926): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1926): JNI_CreateJavaVM failed
E/AndroidRuntime( 1926): JNI_CreateJavaVM failed
D/AndroidRuntime( 1927):
D/AndroidRuntime( 1927): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1927): CheckJNI is OFF
W/dalvikvm( 1927): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1927): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1927): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1927): VM cleaning up
D/dalvikvm( 1927): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1927): JNI_CreateJavaVM failed
E/AndroidRuntime( 1927): JNI_CreateJavaVM failed
D/AndroidRuntime( 1928):
D/AndroidRuntime( 1928): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1928): CheckJNI is OFF
W/dalvikvm( 1928): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1928): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1928): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1928): VM cleaning up
D/dalvikvm( 1928): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1928): JNI_CreateJavaVM failed
E/AndroidRuntime( 1928): JNI_CreateJavaVM failed
D/AndroidRuntime( 1929):
D/AndroidRuntime( 1929): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1929): CheckJNI is OFF
W/dalvikvm( 1929): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1929): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1929): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1929): VM cleaning up
D/dalvikvm( 1929): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1929): JNI_CreateJavaVM failed
E/AndroidRuntime( 1929): JNI_CreateJavaVM failed
D/AndroidRuntime( 1930):
D/AndroidRuntime( 1930): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
wow...umm yea i gatta look that over but if you see nething odd before me let me kno i kno that fail aint good but im ganna delete java rite now

RanT476 said:
wow...umm yea i gatta look that over but if you see nething odd before me let me kno i kno that fail aint good but im ganna delete java rite now
Click to expand...
Click to collapse
What good is deleting Java going to do? :-S
RanT476 said:
wow....you didnt answer my question and i alrdy have ext3 answering my question just might help me with my coma problem so ya
Click to expand...
Click to collapse
wow....you're giving the guy stick for not answering your *whole* question? This isn't a f*cking call centre...
Anyway, back to your question: ext3 is pretty much the preffered filesystem for all ROMs, it's more efficient than ext2 because as david said, it uses journalling and it's probably more stable than ext4 because it's been out longer. So changing your filesystem won't help with kp's.

i see so i need a dev to look at this log is what your saying and no im not getting at him he was being a **** by bypassing my question like a **** so he deserves the **** comments he got from me(pause) but neway thx for answering my question

RanT476 said:
he was being a **** by bypassing my question like a **** so he deserves the **** comments he got from me(pause) but neway thx for answering my question
Click to expand...
Click to collapse
Maybe he didn't know the answer?! Why do people have to be so damn hostile? He's volenteerting his free time, answeres one of your questions and get's called a ****, nice!

"David1171 - i answered half of it." sounded kinda dickish to me but if u aint mean it that way no harm done misunderstanding is all i guess

RanT476 said:
"David1171 - i answered half of it." sounded kinda dickish to me but if u aint mean it that way no harm done misunderstanding is all i guess
Click to expand...
Click to collapse
always post your code with the code tags.
right now your the one that looks dickish. Someone tried to help you out, someone who is surrounded by noobs who ask stupid questions, yet he still takes time to try and help you out. Your question looked like one of them, as there are a lot of threads with that information around here. If you don't like the information given, don't say anything negative and ask for additional clarification.
As for your logcat, it seems to have the same crash over and over. Reflash your rom. you probably didnt wipe, and it looks like you have corrupted files

RanT476 said:
"David1171 - i answered half of it." sounded kinda dickish to me but if u aint mean it that way no harm done misunderstanding is all i guess
Click to expand...
Click to collapse
look at how many of my posts have helped people and how much time i have helped people root their phones, partition, other things they didn't understand and now do because i took the time to help them understand, i have been trying all night to help Z҉A҉L҉G҉O̚̕̚ to get his theme to fit within the confines of the hard spl so people that are afraid to flash the 1.33.2005 spl can use it with all the extras as well.
i misread your initial question and answer what i knew how to answer. i guess partial answer have never helped anyone reach their goal. maybe in the future we should all decide never to answer a question unless we know every single part of the answer with a clear and thought out thesis on how we reached our answer.
you should post your logcat in the thread for the rom you are using, there is a much bigger chance that the dev will see it in there then they will here where you are asking people who don't have all of the answers.
also thank you adriank.

WOW
Wrecking Crew needs to spend some time here obviously. HOLY SH*T! Adrian cursed TWICE in this thread!!!!!!!!!!! wow RanT, you must have hit one of his buttons real good and btw I would have posted the same thing david did as I don't know the answer to your second question either.
<3 david
sorry Adrian, I'm no pedo

i love how people feel they can attack me but w/e and i did post the "logcat" in the roms thread so no worries there and ill press buttons all i want if i feel im being smart mouthed just cause i asked as you said a "noob question" it cant be that noob if even you dont have the answer to the question so it will be returned back to u im not a bad dude but you can take w/e i say how ever you want go to the corner and cry if u want makes no diffrence to me and yea thx for attempting to help and u can curse all u want dude lol i get to laugh u look like a idiot and if u dont kno answers to questions just say you dont kno instead of making it seem like u dont see it or dont wanna answer it or w/e it may be
and yes i did wipe and redo just to make sure something stupid wasnt causeing this so i partitioned 4 gig transcend class 6 micro sdhc card
wiped my phone
redid my partitions
fat32 0 3400 3.4gigs
ext3(it was ext2 before the upgrade) 3400 3900 500megs
linux-swap 3900 3964 64megs
upgrade_fs
reboot recovery
wipe again
flashed rom
so i dnt see the problem redownloaded the rom did it all over again so i dnt kno

42....42.....424242..
42....42.............42..
424242.....424242..
........42.....42.........
........42.....424242..

try clearing your dalvik cache

whats the command i had it in my gmail but i erased it awhile back by accident....so ya tell me how and ill do it rite now

RanT476 said:
....so ya tell me how and ill do it rite now
Click to expand...
Click to collapse
Good luck. This is a community forum. We don't have anything to gain from helping people like you so most people ask when they need information. Anyways, here's your answer.
http://tinyurl.com/nxl9fr

lol im the bad guy ill just agree with you i dnt care enuff to carry this pointless bs of a insult u just threw at me, "people like you" funny how im the bad guy i ask a question and people cant answer it than i get called a noob lol but ok im the bad guy im wrong ill agree with you and GL to you too dude

[Q] Problem acceding exchange contacts in my ANDROID

Hello,
I need somo help with a problem i am experiencing in my ANDORID 2.2
phone.
I have an exchange account in my phone (Samsung Galaxy S) and when i
go to contacts sometimes i get a force close warning due to an android
process.acore failure. I am not using any external app, just the
ANDORID O.S 2.2
I ve tried in other phones and same happens.
Looking into the logs the failure ends with a " 05-29 18:39:15.129 W/
ActivityManager( 2469): Force finishing activity
com.android.contacts/
com.sec.android.app.contacts.PhoneBookTopMenuActivity
Here i show a chain of logs :
05-29 18:39:15.066 D/AndroidRuntime( 3023): Shutting down VM
05-29 18:39:15.066 W/dalvikvm( 3023): threadid=1: thread exiting with uncaught exception (group=0x4001d7d0)
05-29 18:39:15.105 E/AndroidRuntime( 3023): FATAL EXCEPTION: main
05-29 18:39:15.105 E/AndroidRuntime( 3023): java.lang.RuntimeException: Unable to resume activity {com.android.contacts/com.android.contacts.ViewContactActivity}: java.lang.IllegalStateException: Couldn't init cursor window
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3128)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.app.LocalActivityManager.moveToState(LocalActivityManager.java:138)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.app.LocalActivityManager.startActivity(LocalActivityManager.java:339)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.sec.android.touchwiz.widget.TwTabHost$IntentContentStrategy.getContentView(TwTabHost.java:1617)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.sec.android.touchwiz.widget.TwTabHost.setCurrentTab(TwTabHost.java:949)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.sec.android.touchwiz.widget.TwTabHost.addTab(TwTabHost.java:607)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.sec.android.app.contacts.PhoneBookDetailTabActivity.setupInfoTab(PhoneBookDetailTabActivity.java:632)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.sec.android.app.contacts.PhoneBookDetailTabActivity.access$800(PhoneBookDetailTabActivity.java:41)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.sec.android.app.contacts.PhoneBookDetailTabActivity$QueryHandler.onQueryComplete(PhoneBookDetailTabActivity.java:457)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.os.Handler.dispatchMessage(Handler.java:99)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.os.Looper.loop(Looper.java:123)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.app.ActivityThread.main(ActivityThread.java:4627)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at java.lang.reflect.Method.invokeNative(Native Method)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at java.lang.reflect.Method.invoke(Method.java:521)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:871)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:629)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at dalvik.system.NativeStart.main(Native Method)
05-29 18:39:15.105 E/AndroidRuntime( 3023): Caused by: java.lang.IllegalStateException: Couldn't init cursor window
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.database.CursorWindow.native_init(Native Method)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.database.CursorWindow.<init>(CursorWindow.java:73)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:280)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:266)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.android.providers.contacts.ContactsProvider2.query(ContactsProvider2.java:5876)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.content.ContentProvider$Transport.query(ContentProvider.java:163)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.content.ContentResolver.query(ContentResolver.java:245)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.provider.ContactsContract$Contacts.lookupContact(ContactsContract.java:954)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.android.contacts.ViewContactActivity.startEntityQuery(ViewContactActivity.java:833)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at com.android.contacts.ViewContactActivity.onResume(ViewContactActivity.java:444)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1149)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.app.Activity.performResume(Activity.java:3823)
05-29 18:39:15.105 E/AndroidRuntime( 3023): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3118)
05-29 18:39:15.105 E/AndroidRuntime( 3023): ... 17 more
05-29 18:39:15.125 W/ActivityManager( 2469): Force finishing activity com.android.contacts/com.sec.android.app.contacts.PhoneBookDetailTabActivity
05-29 18:39:15.129 I/ ( 2469): dumpmesg > /data/log/dumpstate_app_error.log
05-29 18:39:15.129 W/ActivityManager( 2469): Force finishing activity com.android.contacts/com.sec.android.app.contacts.PhoneBookTopMenuActivity
05-29 18:39:15.176 I/dumpstate( 4099): begin
05-29 18:39:17.626 W/PowerManagerService( 2469): Timer 0x7->0x3|0x0
05-29 18:39:17.626 I/PowerManagerService( 2469): Ulight 7->3|0
05-29 18:39:18.055 I/AudioHardwareALSA( 2364): Output standby called!!. Turn off PCM device.
05-29 18:39:18.258 D/BatteryService( 2469): update start
....
Could someone tell me why is this issue happening and what could i do
to avoid it?
More information: I have 1400 contacts in the phone and the
configuration is to sync every hour
I am new here so excuse me if i am not giving the correct information
or i am not publishing it in the right place,
All information would be great
Thanks in advance
Aquilino López

Contacts not opening

Somebody please help me, im using Helly Bean 4.2 built of 02 December.... and everytime i try to open the Contacts App, it FC and i don't know why... Here is the logcat
Sorry for my english, i'm Mexican
Logcat
Code:
I/ActivityManager( 397): START u0 {act=android.intent.action.MAIN cat=[android.
intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.contacts/.activities.Pe
opleActivity bnds=[120,700][240,772]} from pid 611
I/ActivityManager( 397): Start proc com.android.contacts for activity com.andro
id.contacts/.activities.PeopleActivity: pid=32628 uid=10001 gids={50001, 3003, 1
015, 1028}
E/dalvikvm(32628): Dex cache directory isn't writable: /data/dalvik-cache
I/dalvikvm(32628): Unable to open or create cache for /system/app/Contacts.apk (
/data/dalvik-cache/[email protected]@[email protected])
D/AndroidRuntime(32628): Shutting down VM
W/dalvikvm(32628): threadid=1: thread exiting with uncaught exception (group=0x4
0d37930)
E/AndroidRuntime(32628): FATAL EXCEPTION: main
E/AndroidRuntime(32628): java.lang.RuntimeException: Unable to instantiate appli
cation com.android.contacts.ContactsApplication: java.lang.ClassNotFoundExceptio
n: Didn't find class "com.android.contacts.ContactsApplication" on path: /system
/app/Contacts.apk
E/AndroidRuntime(32628): at android.app.LoadedApk.makeApplication(LoadedA
pk.java:504)
E/AndroidRuntime(32628): at android.app.ActivityThread.handleBindApplicat
ion(ActivityThread.java:4516)
E/AndroidRuntime(32628): at android.app.ActivityThread.access$1300(Activi
tyThread.java:150)
E/AndroidRuntime(32628): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1304)
E/AndroidRuntime(32628): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime(32628): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(32628): at android.app.ActivityThread.main(ActivityThrea
d.java:5191)
E/AndroidRuntime(32628): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime(32628): at java.lang.reflect.Method.invoke(Method.java:5
11)
E/AndroidRuntime(32628): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:795)
E/AndroidRuntime(32628): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:562)
E/AndroidRuntime(32628): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(32628): Caused by: java.lang.ClassNotFoundException: Didn't fin
d class "com.android.contacts.ContactsApplication" on path: /system/app/Contacts
.apk
E/AndroidRuntime(32628): at dalvik.system.BaseDexClassLoader.findClass(Ba
seDexClassLoader.java:65)
E/AndroidRuntime(32628): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:501)
E/AndroidRuntime(32628): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:461)
E/AndroidRuntime(32628): at android.app.Instrumentation.newApplication(In
strumentation.java:968)
E/AndroidRuntime(32628): at android.app.LoadedApk.makeApplication(LoadedA
pk.java:499)
E/AndroidRuntime(32628): ... 11 more
W/ActivityManager( 397): Force finishing activity com.android.contacts/.activ
ities.PeopleActivity
D/dalvikvm( 397): GC_CONCURRENT freed 1949K, 20% free 15713K/19616K, paused 9ms
+18ms, total 196ms
W/ActivityManager( 397): Activity pause timeout for ActivityRecord{41897848 u0
com.android.contacts/.activities.PeopleActivity}
W/ActivityManager( 397): Activity destroy timeout for ActivityRecord{41897848 u
0 com.android.contacts/.activities.PeopleActivity}

Camera FC Xperia Z1

I have a rooted Z1 on .257 firmware.
Everything was fine, until SUDDENTLY (I didn't install ANYTHING) the camera (AR effects, videocamera, anything...) Just won't show and FC.
It seems to me a problem with permissions, as i logcated the whole event.
This is the cut of the event when i start the camera.
Code:
D/dalvikvm( 1135): GC_CONCURRENT freed 39K, 17% free 38637K/46248K, paused 2ms+1
ms, total 15ms
D/dalvikvm( 7366): Trying to load lib /data/app-lib/SemcCameraUI/libblurviewfind
er.so 0x4211f510
D/dalvikvm( 7366): Added shared lib /data/app-lib/SemcCameraUI/libblurviewfinder
.so 0x4211f510
D/dalvikvm( 7366): No JNI_OnLoad found in /data/app-lib/SemcCameraUI/libblurview
finder.so 0x4211f510, skipping init
D/AndroidRuntime( 7366): Shutting down VM
W/dalvikvm( 7366): threadid=1: thread exiting with uncaught exception (group=0x4
1e33ae0)
W/ContextImpl( 917): Calling a method in the system process without a qualified
user: android.app.ContextImpl.sendOrderedBroadcast:1105 com.android.internal.po
licy.impl.PhoneWindowManager.cancelSemcCameraApplication:4403 com.android.intern
al.policy.impl.PhoneWindowManager.interceptCameraKeyEvent:4190 com.android.inter
nal.policy.impl.PhoneWindowManager.interceptKeyBeforeQueueing:4039 com.android.s
erver.wm.InputMonitor.interceptKeyBeforeQueueing:342
E/AndroidRuntime( 7366): FATAL EXCEPTION: main
E/AndroidRuntime( 7366): java.lang.RuntimeException: Unable to resume activity {
com.sonyericsson.android.camera/com.sonyericsson.android.camera.fastcapturing.Fa
stCapturingActivity}: java.lang.RuntimeException: Fail to get camera info
E/AndroidRuntime( 7366): at android.app.ActivityThread.performResumeActiv
ity(ActivityThread.java:2795)
E/AndroidRuntime( 7366): at android.app.ActivityThread.handleResumeActivi
ty(ActivityThread.java:2824)
E/AndroidRuntime( 7366): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2279)
E/AndroidRuntime( 7366): at android.app.ActivityThread.access$600(Activit
yThread.java:150)
E/AndroidRuntime( 7366): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1276)
E/AndroidRuntime( 7366): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 7366): at android.os.Looper.loop(Looper.java:213)
E/AndroidRuntime( 7366): at android.app.ActivityThread.main(ActivityThrea
d.java:5153)
E/AndroidRuntime( 7366): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 7366): at java.lang.reflect.Method.invoke(Method.java:5
11)
E/AndroidRuntime( 7366): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:797)
E/AndroidRuntime( 7366): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:564)
E/AndroidRuntime( 7366): at de.robv.android.xposed.XposedBridge.main(Xpos
edBridge.java:126)
E/AndroidRuntime( 7366): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 7366): Caused by: java.lang.RuntimeException: Fail to get came
ra info
E/AndroidRuntime( 7366): at android.hardware.Camera._getCameraInfo(Native
Method)
E/AndroidRuntime( 7366): at android.hardware.Camera.getCameraInfo(Camera.
java:209)
E/AndroidRuntime( 7366): at com.sonyericsson.cameracommon.utility.StaticC
onfigurationUtil.<init>(StaticConfigurationUtil.java:43)
E/AndroidRuntime( 7366): at com.sonyericsson.cameracommon.utility.StaticC
onfigurationUtil.isForceSound(StaticConfigurationUtil.java:72)
E/AndroidRuntime( 7366): at com.sonyericsson.android.camera.ExtendedActiv
ity.onResume(ExtendedActivity.java:301)
E/AndroidRuntime( 7366): at com.sonyericsson.android.camera.fastcapturing
.FastCapturingActivity.onResume(FastCapturingActivity.java:356)
E/AndroidRuntime( 7366): at android.app.Instrumentation.callActivityOnRes
ume(Instrumentation.java:1185)
E/AndroidRuntime( 7366): at android.app.Activity.performResume(Activity.j
ava:5182)
E/AndroidRuntime( 7366): at android.app.ActivityThread.performResumeActiv
ity(ActivityThread.java:2785)
E/AndroidRuntime( 7366): ... 13 more
W/ActivityManager( 917): Force finishing activity com.sonyericsson.android.ca
mera/.fastcapturing.FastCapturingActivity
D/dalvikvm( 917): GC_FOR_ALLOC freed 1824K, 21% free 41328K/52020K, paused 64ms
, total 66ms
W/ActivityManager( 917): Force finishing activity com.android.settings/.SubSe
ttings
D/dalvikvm( 917): GC_FOR_ALLOC freed 40K, 19% free 42383K/52020K, paused 77ms,
total 77ms
I/dalvikvm-heap( 917): Grow heap (frag case) to 44.657MB for 2536936-byte alloc
ation
I/CrashMonitor( 6525): CrashMonitorServiceBroadcastReceiver: Forwarding intent:
android.intent.action.DROPBOX_ENTRY_ADDED tag: system_app_crash
I/CrashMonitor( 6525): CrashMonitorService: Service started...
D/dalvikvm( 6539): Trying to load lib /data/app-lib/bootinfo/libMiscTaAccessor.s
o 0x42123c08
D/dalvikvm( 6539): Shared lib '/data/app-lib/bootinfo/libMiscTaAccessor.so' alre
ady loaded in same CL 0x42123c08
W/ProcessStats( 917): Skipping unknown process pid 7387
W/ProcessStats( 917): Skipping unknown process pid 7390
D/StatusBar.NetworkController( 1135): refreshViews: Data not connected!! Set no
data type icon / Roaming
D/StatusBar.NetworkController( 1135): refreshViews: Data not connected!! Set no
data type icon / Roaming
D/android.widget.GridLayout( 1135): vertical constraints: y1-y0>=246, y2-y1>=245
, y2-y0<=490 are inconsistent; permanently removing: y2-y0<=490.
D/StatusBar.NetworkController( 1135): refreshViews: Data not connected!! Set no
data type icon / Roaming
D/StatusBar.NetworkController( 1135): refreshViews: Data not connected!! Set no
data type icon / Roaming
W/ActivityManager( 917): Activity pause timeout for ActivityRecord{43cd23e0 u0
com.sonyericsson.android.camera/.fastcapturing.FastCapturingActivity}
D/dalvikvm( 5243): GC_FOR_ALLOC freed 2898K, 9% free 58312K/64068K, paused 28ms,
total 28ms
I/dalvikvm-heap( 5243): Grow heap (frag case) to 65.649MB for 8294416-byte alloc
ation
D/dalvikvm( 5243): GC_CONCURRENT freed 3087K, 13% free 63325K/72172K, paused 2ms
+4ms, total 32ms
I/CrashMonitor( 6525): CrashMonitorService: action: android.intent.action.DROPBO
X_ENTRY_ADDED
I/CrashMonitor( 6525): CrashMonitorService: Service stopped...
Sorry for formatting, but it comes right out the windows console.
Also, i see
Code:
W/ContextImpl( 5243): Calling a method in the system process without a qualified
user: android.app.ContextImpl.sendBroadcast:1076 de.robv.android.xposed.XposedB
ridge.invokeOriginalMethodNative:-2 de.robv.android.xposed.XposedBridge.handleHo
okedMethod:547 android.app.ContextImpl.sendBroadcast:-2 android.content.ContextW
rapper.sendBroadcast:338
because I'm using Xposed framework. Can be it that breaks?
ROM is odexed.
If someone has the same issue or knows how to resolve, post here.
Thank you!

Reinstall rom...
Wysłane z mojego C6903 przy użyciu Tapatalka

Vaith said:
Reinstall rom...
Wysłane z mojego C6903 przy użyciu Tapatalka
Click to expand...
Click to collapse
Wow, so good and complete answer!

I have xposed on an odexed rom so its not that
Try clearing data in camera common app
if that does not work clear data in all camera apps

gregbradley said:
I have xposed on an odexed rom so its not that
Try clearing data in camera common app
if that does not work clear data in all camera apps
Click to expand...
Click to collapse
Tried that too... no luck... =/

[Q] Low on RAM due to lots of app_process instances.

I have a RAZR i with the standard UK 4.1.2 ROM. Sometimes I've had low memory problems or periods where the battery runs down unexpectedly. I recently started experiencing severe memory shortage after running with data disabled and poked around a bit. What I discovered was a large number of app_process instances taking 8M each.
From what I can tell, I should not see these. Android runs this process but it loads Java code into itself and changes personality. So while there's plenty of app_process instances running, they don't show up as such when you do a ps.
I found this out the hard way running killall app_process :/
But I can use this to kill off any of these "zombie" app_process instances: ps | grep app_process | busybox awk '{print $2}' | xargs kill
Running with data disabled seems to make these happen fairly reliably. Made me suspect something was being spawned to look for something on the network but failed due to a lack of data and then... got stuck instead of exiting?
I've disabled a few things on this ROM before. I think ModemStats or similar was a problem once before (chewing up CPU).
Has anyone seen this?
Is there something I can capture that would help diagnose the cause (I've heard of a logcat? maybe ps output?).

a1291762 said:
...Is there something I can capture that would help diagnose the cause (I've heard of a logcat? maybe ps output?).
Click to expand...
Click to collapse
sure, setup ADB and plug your device with a micro-usb cable on pc. Now you can logcat and also grep your favorit process.
Did you try limiting your backgroundprocesses under Developer-Options > backgroundprocess-limit ?
I use all the time a limit of 4 processes and have no memory problems (fyi: it will fall back to standard-setting after reboot)

Use the app Greenify to hibernate the apps you dont use daily
Enviado desde mi XT890 mediante Tapatalk

So... Greenify and limiting background "apps" can't help here because app_process isn't an app, it's a system process.
And it seems logcat isn't very useful when run after-the-fact? Oh it seems you can't run it except as root from Android 4.1 onwards. I've now got catlog recording so maybe next time I'll get something useful - assuming my SD card doesn't fill up first.
And of course now that I'm trying to _look_ at the problem, it's happening less frequently >:|

Amm app process are services, with the greenify app kills the services.....
If you havent root, well, remove the task on recent app list, force detention of the apps manually, and so on
Enviado desde mi XT890 mediante Tapatalk

Please don't spread misinformation. app_process is a system process. It is not even visible at the Android layer. Every app starts as an app_process instance. Greenify cannot even see it, let alone control it.

The good news is I have a logcat. The bad news is it's a 37Mb file and both the system ui and logcat app died due to lack of memory. I have second logcat fr when I noticed but the end of the first one if probably more useful. Having trouble reading the file on my phone. Will investigate more when I get home tonight.

bug2go is evil???
So app_process is AndroidRuntime. I see various AndroidRuntime START messages. Looks like normal starting of apps. Until 16:24 on 03-22.
Code:
03-22 03:30:04.822 D/AndroidRuntime(29699): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:35:03.670 D/AndroidRuntime(31593): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:35:03.670 D/AndroidRuntime(31592): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:38:03.542 D/AndroidRuntime(31650): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:38:03.552 D/AndroidRuntime(31651): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:23:10.850 D/AndroidRuntime( 1024): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:23:10.850 D/AndroidRuntime( 1025): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:41:29.170 D/AndroidRuntime( 2245): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:27:38.730 D/AndroidRuntime( 4879): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:41:39.630 D/AndroidRuntime( 5729): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:41:39.630 D/AndroidRuntime( 5730): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:30.350 D/AndroidRuntime( 6042): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:35.710 D/AndroidRuntime( 6064): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:35.910 D/AndroidRuntime( 6074): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.050 D/AndroidRuntime( 6079): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.320 D/AndroidRuntime( 6098): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.340 D/AndroidRuntime( 6087): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.400 D/AndroidRuntime( 6102): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.620 D/AndroidRuntime( 6105): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.690 D/AndroidRuntime( 6111): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.860 D/AndroidRuntime( 6133): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.950 D/AndroidRuntime( 6136): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
...
03-22 16:24:48.350 D/AndroidRuntime( 6650): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.350 D/AndroidRuntime( 6654): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.530 D/AndroidRuntime( 6744): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.610 D/AndroidRuntime( 6670): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
Something is running com.android.am.Am over and over again.
Code:
2014-03-20-08-45-47.txt|417176| 03-22 16:24:38.060 D/AndroidRuntime( 6111): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417215| 03-22 16:24:38.380 D/AndroidRuntime( 6133): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417216| 03-22 16:24:38.410 D/AndroidRuntime( 6136): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417225| 03-22 16:24:38.620 D/AndroidRuntime( 6140): Calling main entry com.android.commands.am.Am
Am seems to be an android tool to run shell commands. What's being run?
Code:
03-22 16:24:48.440 D/su ( 6756): su invoked.
03-22 16:24:48.440 D/su ( 6756): Allowing shell.
03-22 16:24:48.440 D/su ( 6756): 2000 /system/xbin/su executing 0 showmap using binary showmap : showmap 129
03-22 16:24:48.440 E/su ( 6756): exec failed with 2: No such file or directory
Hm... Running a binary that doesn't exist lots and lots of times? That can't be a coincidence. Looks like app_process doesn't properly clean up in this case.
But what is causing all this in the first place? I found this.
Code:
03-22 16:24:29.600 I/bug2go-bugreport( 6037): bugreport started
03-22 16:24:29.610 I/bug2go-bugreport( 6037): reportId=2014-03-22_16-24-29.000+1000
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Available space in /storage/sdcard0/bug2go is 1227 MB
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Required space is 50
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Storing report to /storage/sdcard0/bug2go/[email protected]_16-24-29.000+1000
...
03-22 16:24:30.690 W/ActivityManager( 384): Unable to start service Intent { act=motorola.intent.action.BUG2GO.BUGREPORT.START typ=text/plain (has extras) }: not found
Now that's odd. The bug2go apk is something I had previously removed. But the 2 bug2go binaries in /system/bin were still there. I can't see what triggered this (unless it's that last line, some kind of period attempt to run the now-missing bug2go app). Scrolling up in the logs I see... nothing but wifi scanning. My phone was suspended at the time so nothing was happening.
I've removed the bug2go binaries from /system/bin. That seems to be the source of the problem so maybe that'll fix things?

I also got a log after I noticed my phone was bad. It shows the last showmap error.
Code:
03-22 16:25:33.300 D/su (8732): su invoked.
03-22 16:25:33.300 D/su (8732): Allowing shell.
03-22 16:25:33.300 D/su (8732): 2000 /system/xbin/su executing 0 showmap using binary showmap : showmap 28103
03-22 16:25:33.300 E/su (8732): exec failed with 2: No such file or directory
And then, bug2go either gives up or finishes.
Code:
03-22 16:26:16.850 I/dumpstate(6054): done
03-22 16:26:16.850 I/bug2go-bugreport(6037): Dropping from root user to log user
So that at least explains why the phone doesn't ground to a permanent halt and why I can kill off these processes and have the phone continue to work.
Aha! It's actually dumpstate that causes the bug. It's run by bug2go but also by 'adb bugreport'. It tries to run showmap on... each running process? But since I don't have that binary, it leaves behind all the app_process instances. I ran 'adb bugreport' just now and it caused my phone to reboot!
So removing the bug2go binaries should stop this from being a problem but I'm kind of stumped as to why I have 'dumpstate' but not 'showmap' on my phone...