Author Topic: Beta Testing Has Begun!  (Read 959198 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #405 on: May 06, 2012, 04:08:28 PM »
1.With gles plugin you can't disable tribuffer opt, which causes graphical glitches and on rare occasions ocarina crashes.

Tribuffer opt is no longer an option in gles2n64 (having it as a run-time option instead of hard-coded causes slowdowns on many devices).  Unfortunately, this was a decision between the lesser of two evils.  I'll release an alternate version of the video plug-in with tribuffer turned off, and folks can import it.

Auto-frameskip doesnt work in every game & manually set frameskip doesnt work properly (not related to rc, just in general, they dont work in 1.8.2 either.).
I think autoframeskip worked with android 2.2, but now with gingerbread it doesn't.

Frameskip seems to behave differently depending on the device.  This is definitely one area that will need work in the future.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #406 on: May 06, 2012, 10:35:30 PM »
I've decided the app is at a good point to release an official update.

Mupen64Plus, AE v1.9 (6 May 2012)  (commit c24bee74fb)

I also published it to the Play Store (hopefully no more crazies will try and take it down again).  I had to give it a new package name in the manifest (paulscode.android.mupen64plusae), since the original one is still suspended.  If you run into any problems, let me know and I'll correct them right away.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline rubejb

  • bit
  • Posts: 1
    • View Profile
Re: Beta Testing Has Begun!
« Reply #407 on: May 07, 2012, 09:02:59 AM »
I've decided the app is at a good point to release an official update.

newbielink:http://www.paulscode.com/source/Mupen64Plus-AE/06MAY2012/Mupen64Plus-AE.apk [nonactive] (6 May 2012)  ( newbielink:https://github.com/paulscode/mupen64plus-ae/commit/c24bee74fbf90476be0650cf85f083e54337ae28 [nonactive])

I also published it to the Play Store (hopefully no more crazies will try and take it down again).  I had to give it a new package name in the manifest (paulscode.android.mupen64plusae), since the original one is still suspended.  If you run into any problems, let me know and I'll correct them right away.

Very cool, glad to see it's back on the Play Store.  However, is there a free Play version available?  It's not that I'm complaining about a dollar, but I've already purchased the donate version before the Play Store mess occurred.  I also realize that you can get it for free from the site, but it's much easier to have it update through the Store.

Thanks for the awesome emulator!

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #408 on: May 07, 2012, 02:49:36 PM »
I've decided not to post another free version, for a couple reasons.

The first reason is that I do not want to be a target for people like Brad Geng who see an ad-free app as an insurmountable competition for their ad revenues, causing them to take drastic measures to removed their competition, like the bogus DMCA claim.  I'm taking note of the fact that N64 4 Droid has remained unscathed through this whole mess, by simply publishing the app and not worrying about anyone else.

The second reason I'm not posting a free version to the Play Store is because if Brad does decide to submit another bogus DMCA claim (which seems highly likely to me from what I know about him), I'd rather have only one more app "in violation of Google policy" than two more of them.  The process appears to be completely automated, so there is no way to show a live person at Google with more common sense than a computer that I've not broken any rules, and that the DMCA complaint is not even legal in the first place.  I don't know how many strikes Google gives folks before banning their account (I already have 3), and I've heard that once you are banned, it is almost impossible to stay off Google's radar (they will keep banning all future accounts, not just the original one).  Since I plan to make a living off selling apps in the future, I'd rather not tempt fate any more than I already am by posting this app once again.

On that note, if the app is pulled from Google Play again, I will not be re-listing it or any other emulator in the future.  In that case, I'll switch to Slideme or another less popular alternative, and just use Google Play for my future commercial apps.  In the unlikely event that Google does somehow come to their senses and decides to unsuspend my original 3 apps, then I'll update the original free version and remove the other two that have now been merged into the current app.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #409 on: May 07, 2012, 06:02:21 PM »
There are still some bugs I missed (bound to happen on a big update like this), so I'll get to fixing them ASAP.  The main one I want to fix is the Xperia Play touchpad issue.  This is a verbose test that should help me track it down:

Mupen64Plus, AE TEST

I also fixed some issues caused by the new package name, and increased the analog stick redraw rate a tad since the jerkiness looked pretty bad on lower-density screens.

--EDIT-- Oops, small typo caused crashes in some menu screens.  Fixed now (same link above)
« Last Edit: May 07, 2012, 06:20:36 PM by Paul »
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #410 on: May 07, 2012, 07:53:56 PM »
I released a minor update (posted to Google Play also), containing some important bug-fixes:

Mupen64Plus, AE v1.9.2 (7 May 2012) (commit fdbd52e8ec)
« Last Edit: May 07, 2012, 08:18:15 PM by Paul »
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline mmxii

  • int
  • **
  • Posts: 76
    • View Profile
Re: Beta Testing Has Begun!
« Reply #411 on: May 08, 2012, 07:03:25 PM »
Wow! Seeing about 2 fps higher on every game. Very nice. It plays all the games I really care about phenomenally! Whats in store for future builds? I hope Rumble Pak and dual core boost, not that I need either one, but it would be nice to see lol
Device: Asus Nexus 7 16 GB
CPU: nVidia Tegra 3 1.6 GHz quad core
GPU: ULP GeForce 512 MHz
RAM: 1 GB
Screen res: 800x1200
ROM/Kernel: (AOSP) Bugless Beast Halloween Build (Android 4.1.2) / faux123 011 Ultimate Edition Max

Offline Lioncash

  • Developer
  • byte
  • *****
  • Posts: 29
    • View Profile
Re: Beta Testing Has Begun!
« Reply #412 on: May 08, 2012, 07:45:16 PM »
Whats in store for future builds?

Hopefully a better rice plugin.

I've been working on it a lot. I just finished pushing changes I made to the github repo.

Adds more ucode for some games (Mario 64, Perfect Dark, Diddy Kong Racing, etc).

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #413 on: May 08, 2012, 08:42:52 PM »
Here is a test for folks to run to see how rice does now with Lioncash's changes:

Mupen64Plus, AE TEST
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Kris

  • Developer
  • int
  • *****
  • Posts: 91
    • View Profile
Re: Beta Testing Has Begun!
« Reply #414 on: May 08, 2012, 09:03:59 PM »
I'll have to take a closer look I'm not sure what's new and what's just been moved around. The titles mentioned were already supported but there was some references to Star Wars SOTE which has problems but some have been playing it anyway.

It's nice have some of the code tidied up but I haven't made my mind up about all the changes. I'm interested to see what becomes of this update.

Offline Mofade103

  • byte
  • *
  • Posts: 24
    • View Profile
Re: Beta Testing Has Begun!
« Reply #415 on: May 08, 2012, 09:15:06 PM »
I'm getting force closed
devices LG Optimus S & Samsung Galaxy S3

Offline Lioncash

  • Developer
  • byte
  • *****
  • Posts: 29
    • View Profile
Re: Beta Testing Has Begun!
« Reply #416 on: May 08, 2012, 09:40:39 PM »
I'm getting force closed

That's really odd. I did a full rebuild of the library to see if it was something that snuck through the last build. But everything is still working for me.

Offline Mofade103

  • byte
  • *
  • Posts: 24
    • View Profile
Re: Beta Testing Has Begun!
« Reply #417 on: May 08, 2012, 09:42:16 PM »
I'm getting force closed

That's really odd. I did a full rebuild of the library to see if it was something that snuck through the last build. But everything is still working for me.

I can post log
devices LG Optimus S & Samsung Galaxy S3

Offline Lioncash

  • Developer
  • byte
  • *****
  • Posts: 29
    • View Profile
Re: Beta Testing Has Begun!
« Reply #418 on: May 08, 2012, 09:50:22 PM »
I'm getting force closed

That's really odd. I did a full rebuild of the library to see if it was something that snuck through the last build. But everything is still working for me.

I can post log

Sure, anything that helps is always nice.

Offline Mofade103

  • byte
  • *
  • Posts: 24
    • View Profile
Re: Beta Testing Has Begun!
« Reply #419 on: May 08, 2012, 09:52:32 PM »
--------- beginning of /dev/log/system
W/InputManagerService(  110): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@45dc0a90
--------- beginning of /dev/log/main
I/WindowManager(  110): home key test1= 1
D/WindowManager(  110): Home Key Test : false : false
I/WindowManager(  110): home key test1= 1
D/WindowManager(  110): Home Key Test : false : false
I/WindowManager(  110): home key test1= 1
D/WindowManager(  110): Home Key Test : false : false
I/WindowManager(  110): home key test1= 1
D/WindowManager(  110): Home Key Test : false : false
D/dalvikvm(  110): GC_EXTERNAL_ALLOC freed 11734 objects / 621152 bytes in 186ms
I/WindowManager(  110): home key test1= 1
D/WindowManager(  110): Home Key Test : false : false
I/WindowManager(  110): home key test1= 1
D/WindowManager(  110): Home Key Test : false : false
D/StatusBar(  110): DISABLE_EXPAND: yes
I/ActivityManager(  110): Starting activity: Intent { act=android.intent.action.MAIN flg=0x10100000 cmp=paulscode.android.mupen64plusae.test/paulscode.android.mupen64plusae.MainActivity }
I/ActivityManager(  110): Start proc paulscode.android.mupen64plusae.test for activity paulscode.android.mupen64plusae.test/paulscode.android.mupen64plusae.MainActivity: pid=8791 uid=10114 gids={3003, 1015}
I/ActivityManager(  110): Start proc com.mhuang.overclocking for service com.mhuang.overclocking/.ProfilesService: pid=8795 uid=10084 gids={1015}
W/InputManagerService(  110): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@45da3f20
I/WindowManager(  110): Setting rotation to 1, animFlags=1
I/ActivityManager(  110): Config changed: { scale=1.0 imsi=310/120 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=18 uiMode=17 seq=50}
D/PhoneApp(  211): updateProximitySensorMode: state = IDLE
D/PhoneApp(  211): updateProximitySensorMode: lock already released.
I/MainActivity( 8791): libSDL: Starting data downloader
I/MainActivity( 8791): libSDL: Starting downloader
V/DataDir Check( 8791): Globals.PackageName set to 'paulscode.android.mupen64plusae.test'
V/DataDir Check( 8791): Globals.LibsDir set to '/data/data/paulscode.android.mupen64plusae.test'
V/DataDir Check( 8791): Globals.StorageDir set to '/mnt/sdcard'
V/DataDir Check( 8791): Globals.DataDir set to '/mnt/sdcard/Android/data/paulscode.android.mupen64plusae.test'
I/ActivityManager(  110): Displayed activity paulscode.android.mupen64plusae.test/paulscode.android.mupen64plusae.MainActivity: 455 ms (total 455 ms)
I/global  ( 8791): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
W/dalvikvm( 8791): Unable to resolve superclass of Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay; (12)
W/dalvikvm( 8791): Link of class 'Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay;' failed
E/dalvikvm( 8791): Could not find class 'paulscode.android.mupen64plusae.GameActivityXperiaPlay', referenced from method paulscode.android.mupen64plusae.MenuActivity.onListItemClick
W/dalvikvm( 8791): VFY: unable to resolve const-class 178 (Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay;) in Lpaulscode/android/mupen64plusae/MenuActivity;
D/dalvikvm( 8791): VFY: replacing opcode 0x1c at 0x0091
D/dalvikvm( 8791): VFY: dead code 0x0093-0095 in Lpaulscode/android/mupen64plusae/MenuActivity;.onListItemClick (Landroid/widget/ListView;Landroid/view/View;IJ)V
I/global  ( 8791): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
E/su      ( 8809): sudb - Opening database
E/su      ( 8809): sudb - Database opened
E/su      ( 8809): sudb - Database closed
D/su      ( 8809): 10084 com.mhuang.overclocking executing 0 /system/bin/sh using shell /system/bin/sh : sh
I/ActivityManager(  110): Start proc com.noshufou.android.su for broadcast com.noshufou.android.su/.SuResultReceiver: pid=8811 uid=10075 gids={3003, 1015}
I/global  ( 8791): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
I/ActivityThread( 8811): Publishing provider com.noshufou.android.su.provider: com.noshufou.android.su.provider.PermissionsProvider
D/dalvikvm( 8791): GC_FOR_MALLOC freed 4268 objects / 303552 bytes in 173ms
I/global  ( 8791): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
I/global  ( 8791): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
I/global  ( 8791): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
I/ActivityManager(  110): Starting activity: Intent { flg=0x24000000 cmp=paulscode.android.mupen64plusae.test/paulscode.android.mupen64plusae.MenuActivity }
I/WindowManager(  110): Setting rotation to 0, animFlags=1
I/ActivityManager(  110): Config changed: { scale=1.0 imsi=310/120 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=1 layout=18 uiMode=17 seq=51}
D/PhoneApp(  211): updateProximitySensorMode: state = IDLE
D/PhoneApp(  211): updateProximitySensorMode: lock already released.
W/IInputConnectionWrapper( 8756): showStatusIcon on inactive InputConnection
D/dalvikvm( 8795): Trying to load lib /data/data/com.mhuang.overclocking/lib/libsetcpu-native.so 0x45819328
I/ActivityManager(  110): Displayed activity paulscode.android.mupen64plusae.test/paulscode.android.mupen64plusae.MenuActivity: 158 ms (total 158 ms)
D/dalvikvm( 8795): Added shared lib /data/data/com.mhuang.overclocking/lib/libsetcpu-native.so 0x45819328
D/dalvikvm( 8795): No JNI_OnLoad found in /data/data/com.mhuang.overclocking/lib/libsetcpu-native.so 0x45819328, skipping init
W/dalvikvm( 8791): Unable to resolve superclass of Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay; (12)
W/dalvikvm( 8791): Link of class 'Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay;' failed
E/dalvikvm( 8791): Could not find class 'paulscode.android.mupen64plusae.GameActivityXperiaPlay', referenced from method paulscode.android.mupen64plusae.FileChooserActivity.onFileClick
W/dalvikvm( 8791): VFY: unable to resolve const-class 178 (Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay;) in Lpaulscode/android/mupen64plusae/FileChooserActivity;
D/dalvikvm( 8791): VFY: replacing opcode 0x1c at 0x0065
D/dalvikvm( 8791): VFY: dead code 0x0067-0069 in Lpaulscode/android/mupen64plusae/FileChooserActivity;.onFileClick (Lpaulscode/android/mupen64plusae/MenuOption;)V
I/ActivityManager(  110): Starting activity: Intent { flg=0x24000000 cmp=paulscode.android.mupen64plusae.test/paulscode.android.mupen64plusae.FileChooserActivity }
I/ActivityManager(  110): Displayed activity paulscode.android.mupen64plusae.test/paulscode.android.mupen64plusae.FileChooserActivity: 132 ms (total 132 ms)
D/dalvikvm(  110): GC_EXPLICIT freed 8612 objects / 418968 bytes in 230ms
W/dalvikvm( 8791): Unable to resolve superclass of Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay; (12)
W/dalvikvm( 8791): Link of class 'Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay;' failed
W/dalvikvm( 8791): Unable to resolve superclass of Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay; (12)
W/dalvikvm( 8791): Link of class 'Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay;' failed
W/dalvikvm( 8791): Unable to resolve superclass of Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay; (12)
W/dalvikvm( 8791): Link of class 'Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay;' failed
I/dalvikvm( 8791): Could not find method paulscode.android.mupen64plusae.GameActivityXperiaPlay.sendCommand, referenced from method paulscode.android.mupen64plusae.GameActivityCommon.setActivityTitle
W/dalvikvm( 8791): VFY: unable to resolve virtual method 491: Lpaulscode/android/mupen64plusae/GameActivityXperiaPlay;.sendCommand (ILjava/lang/Object;)V
D/dalvikvm( 8791): VFY: replacing opcode 0x6e at 0x0007
V/GameActivityCommon( 8791): Loading native library 'SDL'
D/dalvikvm( 8791): Trying to load lib /data/data/paulscode.android.mupen64plusae.test/lib/libSDL.so 0x458196c0
D/dalvikvm( 8791): Added shared lib /data/data/paulscode.android.mupen64plusae.test/lib/libSDL.so 0x458196c0
V/GameActivityCommon( 8791): Loading native library 'core'
D/dalvikvm( 8791): Trying to load lib /data/data/paulscode.android.mupen64plusae.test/lib/libcore.so 0x458196c0
D/dalvikvm( 8791): Added shared lib /data/data/paulscode.android.mupen64plusae.test/lib/libcore.so 0x458196c0
D/dalvikvm( 8791): No JNI_OnLoad found in /data/data/paulscode.android.mupen64plusae.test/lib/libcore.so 0x458196c0, skipping init
V/GameActivityCommon( 8791): Loading native library 'front-end'
D/dalvikvm( 8791): Trying to load lib /data/data/paulscode.android.mupen64plusae.test/lib/libfront-end.so 0x458196c0
D/dalvikvm( 8791): Added shared lib /data/data/paulscode.android.mupen64plusae.test/lib/libfront-end.so 0x458196c0
I/ActivityManager(  110): Starting activity: Intent { flg=0x24000000 cmp=paulscode.android.mupen64plusae.test/paulscode.android.mupen64plusae.GameActivity }
I/WindowManager(  110): Setting rotation to 1, animFlags=1
I/ActivityManager(  110): Config changed: { scale=1.0 imsi=310/120 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=18 uiMode=17 seq=52}
D/PhoneApp(  211): updateProximitySensorMode: state = IDLE
D/PhoneApp(  211): updateProximitySensorMode: lock already released.
E/dalvikvm( 8791): Could not find class 'android.app.Notification$Builder', referenced from method paulscode.android.mupen64plusae.GameActivity.onCreate
W/dalvikvm( 8791): VFY: unable to resolve new-instance 13 (Landroid/app/Notification$Builder;) in Lpaulscode/android/mupen64plusae/GameActivity;
D/dalvikvm( 8791): VFY: replacing opcode 0x22 at 0x0051
D/dalvikvm( 8791): VFY: dead code 0x0053-0431 in Lpaulscode/android/mupen64plusae/GameActivity;.onCreate (Landroid/os/Bundle;)V
D/AndroidRuntime( 8791): Shutting down VM
W/dalvikvm( 8791): threadid=1: thread exiting with uncaught exception (group=0x40020950)
E/AndroidRuntime( 8791): FATAL EXCEPTION: main
E/AndroidRuntime( 8791): java.lang.NoClassDefF
devices LG Optimus S & Samsung Galaxy S3