Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About viddypiddy

  • Rank

Profile Information

  • Your Current Device(s)
    Nexus One, Galaxy Nexus
  1. Yeah, thanks for that tip. Seems like the Google+-app which is added when selecting it in the kitchen messes up when upgrading it from Market to a newer version? If i unticked the Google+-app in the kitchen, and just installed it from Market it worked.
  2. Reporting a strange issue. I've been flashing between this ROM and Stock 4.0.2 several times now, and its 100% consistent; Issue: Google+ Messenger crashes when trying to view an already existing conversation. It does not happen when Stock 4.0.1 is installed (with fastboot) But it happens 100% of the cases when MCR is flashed with CWM both with and without wipe from Stock. Any clues? logcat; E/gcomm_native( 1428): [static bool GCommNativeWrapperPeer::StaticInitialize(JNIEnv*, _jclass*, _jobject*) gcomm_native_wrapper.cpp(659) 4014c488] Could not locate method: onMeetingUrlsResponse (Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V D/AndroidRuntime( 1428): Shutting down VM W/dalvikvm( 1428): threadid=1: thread exiting with uncaught exception (group=0x40a791f8) E/AndroidRuntime( 1428): FATAL EXCEPTION: main E/AndroidRuntime( 1428): java.lang.NoSuchMethodError: no method with name='onMeetingUrlsResponse' signature='(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V' in class Lcom/google/android/apps/plus/hangout/GCommNativeWrapper; E/AndroidRuntime( 1428): at com.google.android.apps.plus.hangout.GCommNativeWrapper.nativeStaticInitialize(Native Method) E/AndroidRuntime( 1428): at com.google.android.apps.plus.hangout.GCommApp.<init>(GCommApp.java:323) E/AndroidRuntime( 1428): at com.google.android.apps.plus.hangout.GCommApp.getOrCreateInstance(GCommApp.java:367) E/AndroidRuntime( 1428): at com.google.android.apps.plus.phone.ConversationActivity.onCreate(ConversationActivity.java:175) E/AndroidRuntime( 1428): at android.app.Activity.performCreate(Activity.java:4465) E/AndroidRuntime( 1428): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1049) E/AndroidRuntime( 1428): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1919) E/AndroidRuntime( 1428): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1980) E/AndroidRuntime( 1428): at android.app.ActivityThread.access$600(ActivityThread.java:122) E/AndroidRuntime( 1428): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1146) E/AndroidRuntime( 1428): at android.os.Handler.dispatchMessage(Handler.java:99) E/AndroidRuntime( 1428): at android.os.Looper.loop(Looper.java:137) E/AndroidRuntime( 1428): at android.app.ActivityThread.main(ActivityThread.java:4340) E/AndroidRuntime( 1428): at java.lang.reflect.Method.invokeNative(NativeMethod) E/AndroidRuntime( 1428): at java.lang.reflect.Method.invoke(Method.java:511) E/AndroidRuntime( 1428): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784) E/AndroidRuntime( 1428): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551) E/AndroidRuntime( 1428): at dalvik.system.NativeStart.main(Native Method) W/ActivityManager( 233): Force finishing activity com.google.android.apps.plus/.phone.ConversationActivity W/ActivityManager( 233): Force finishing activity com.google.android.apps.plus/.phone.ConversationListActivity
  3. Anyone using the Mail app with Exchange against a server which has a "need encryption"-policy? I'm all for all the other policy-stuff, but the encryption demand is just pure annoying. Mostly because Clockworkmod recovery isn't able to mount /data, and since /data/media is /sdcard on this phone i can't even do a nandroid backup. In the past some people have "hacked" the ROMs/Apps in some way to remove the encryption demand. Can this be implemented? Or does anyone know how i can turn it off? or if CWM Recovery can mount encrypted partitions, please do tell how ;) Edit; So right now i cant even flash this ROM, i'm even struggling removing the encryption. Factory Reset seems to do nothing.. o_O Edit 2; Had to use fastboot-to-factory to actually get rid of the encryption. Running latest MCR now, but wth is this; W/DownloadManager( 618): Downloads data dir: /data/data/com.android.providers.downloads/cache is running low on space. space available (in bytes): 5436401
  4. Seems like it had something to do with how i was baking the ROM, i went through all the baking options again and reflashed Gr5 and it was solved. No wipe needed.
  5. I just noticed today that i can't turn off my phone the usual way. Holding down the power-button does nothing except make the phone semi-reboot (seems like the UI restarts, mediascanner starts again etc.) I was expecting the power off menu :i Anyone else seen this kind of behaviour?
  6. Tried it now. Would be better with the normal Google lock-screen tho since it has the silent toggle, but this is the next best thing! The samsung one is just pure useless Thanks for the tip.
  7. All in all i'm really happy with the ROM. Atleast the parts i have tested during daily use. The only thing I'm still really unhappy about is the HORRIBLE Samsung lock screen. The one where you "drag" the entire screen outside the screen to unlock. I might be missing something, hence im asking. Is there any way to get rid of this? Change to default aosp-lockscreen or similar? The kitchen has tons of options, so i'm not eliminating the option that i'm missing it somewhere. If its not there, anyone know of a patch/fix? When using CM7 i was using the "Quick unlock" and the "hide unlock screen"-options, so it just took me directly to the PIN-code entry. So just skipping the lockscreen alltogether is also a good option. What do you think, Paul? Anything you could hack into the kitchen? ;-)
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.