« previous next »
Pages: 1 ... 12 13 [14] 15 16 ... 57

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

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #195 on: February 12, 2012, 02:05:27 PM »
It may be a different debug signature, since I built it on a different computer.  Does it work if you uninstall the previous one?

If that still has the low-res icon, give this one a try (changed the android target to the Xperia Play specifically):

Xperia Play Test 4
Logged
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 #196 on: February 12, 2012, 02:16:48 PM »
Ok, fixed the package name problem.  See if this one still has the low-res icon:

Xperia Play Test 5
Logged
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 Epic_bubble

  • long
  • ***
  • Posts: 235
    • View Profile
Re: Beta Testing Has Begun!
« Reply #197 on: February 12, 2012, 02:19:15 PM »
Quote from: Paul on February 12, 2012, 02:16:48 PM
Ok, fixed the package name problem.  See if this one still has the low-res icon:

Xperia Play Test 5

Still low res. What I did was put the high res logo in both drawable and drawable-hdpi. I know thats probably not the correct way to do it but it hasent caused any issues  on my xperia play and since all xperia play's have the same screen res there is nothing to worry about really. :P
Logged
Device: Xperia play
CPU: Qualcomm 1 GHz Scorpion (Snapdragon)
GPU: Adreno 205
RAM: 512 MB
Screen res: 854 ? 480
ROM: stock android 2.3.4 rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #198 on: February 12, 2012, 02:20:06 PM »
Ok, I'll give that a shot.
Logged
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 #199 on: February 12, 2012, 02:28:56 PM »
With the logo in hi dpi folder as well:
Xperia Play Test 6
Logged
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 Epic_bubble

  • long
  • ***
  • Posts: 235
    • View Profile
Re: Beta Testing Has Begun!
« Reply #200 on: February 12, 2012, 03:25:28 PM »
----------
id: 1 or "android-4"
     Name: Android 1.6
     Type: Platform
     API level: 4
     Revision: 3
     Skins: HVGA, QVGA, WVGA800 (default), WVGA854
     ABIs : armeabi
----------
id: 2 or "android-5"
     Name: Android 2.0
     Type: Platform
     API level: 5
     Revision: 1
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WVGA800 (default), WVGA854
     ABIs : armeabi
----------
id: 3 or "android-6"
     Name: Android 2.0.1
     Type: Platform
     API level: 6
     Revision: 1
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WVGA800 (default), WVGA854
     ABIs : armeabi
----------
id: 4 or "android-7"
     Name: Android 2.1
     Type: Platform
     API level: 7
     Revision: 3
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WVGA800 (default), WVGA854
     ABIs : armeabi
----------
id: 5 or "android-8"
     Name: Android 2.2
     Type: Platform
     API level: 8
     Revision: 3
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WVGA800 (default), WVGA854
     ABIs : armeabi
----------
id: 6 or "android-9"
     Name: Android 2.3.1
     Type: Platform
     API level: 9
     Revision: 2
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WVGA800 (default), WVGA854
     ABIs : armeabi
----------
id: 7 or "android-10"
     Name: Android 2.3.3
     Type: Platform
     API level: 10
     Revision: 2
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WVGA800 (default), WVGA854
     ABIs : armeabi
----------
id: 8 or "Google Inc.:Google APIs:10"
     Name: Google APIs
     Type: Add-On
     Vendor: Google Inc.
     Revision: 2
     Description: Android + Google APIs
     Based on Android 2.3.3 (API level 10)
     Libraries:
      * com.android.future.usb.accessory (usb.jar)
          API for USB Accessories
      * com.google.android.maps (maps.jar)
          API for Google Maps
     Skins: WVGA854, WQVGA400, HVGA, WQVGA432, WVGA800 (default), QVGA
     ABIs : armeabi
----------
id: 9 or "KYOCERA Corporation:DTS Add-On:10"
     Name: DTS Add-On
     Type: Add-On
     Vendor: KYOCERA Corporation
     Revision: 1
     Description: DTS Add-On
     Based on Android 2.3.3 (API level 10)
     Libraries:
      * com.kyocera.dualscreen (dualscreen.jar)
          Dual Screen optional platform library
     Skins: DTS400 (default), WVGA854, WQVGA400, HVGA, DTS800, WQVGA432, WVGA800, QVGA
     ABIs : armeabi
----------
id: 10 or "android-11"
     Name: Android 3.0
     Type: Platform
     API level: 11
     Revision: 2
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 11 or "Google Inc.:Google APIs:11"
     Name: Google APIs
     Type: Add-On
     Vendor: Google Inc.
     Revision: 1
     Description: Android + Google APIs
     Based on Android 3.0 (API level 11)
     Libraries:
      * com.google.android.maps (maps.jar)
          API for Google Maps
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 12 or "android-12"
     Name: Android 3.1
     Type: Platform
     API level: 12
     Revision: 3
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 13 or "Google Inc.:Google APIs:12"
     Name: Google APIs
     Type: Add-On
     Vendor: Google Inc.
     Revision: 1
     Description: Android + Google APIs
     Based on Android 3.1 (API level 12)
     Libraries:
      * com.android.future.usb.accessory (usb.jar)
          API for USB Accessories
      * com.google.android.maps (maps.jar)
          API for Google Maps
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 14 or "android-13"
     Name: Android 3.2
     Type: Platform
     API level: 13
     Revision: 1
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 15 or "Google Inc.:Google APIs:13"
     Name: Google APIs
     Type: Add-On
     Vendor: Google Inc.
     Revision: 1
     Description: Android + Google APIs
     Based on Android 3.2 (API level 13)
     Libraries:
      * com.android.future.usb.accessory (usb.jar)
          API for USB Accessories
      * com.google.android.maps (maps.jar)
          API for Google Maps
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 16 or "android-14"
     Name: Android 4.0
     Type: Platform
     API level: 14
     Revision: 3
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800
     ABIs : armeabi-v7a
----------
id: 17 or "android-15"
     Name: Android 4.0.3
     Type: Platform
     API level: 15
     Revision: 1
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800
     ABIs : armeabi-v7a
Logged
Device: Xperia play
CPU: Qualcomm 1 GHz Scorpion (Snapdragon)
GPU: Adreno 205
RAM: 512 MB
Screen res: 854 ? 480
ROM: stock android 2.3.4 rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #201 on: February 12, 2012, 09:28:54 PM »
Anyone notice Mario 64 running worse since the update?  I changed the compiler options which provided a very small improvement on my phone, but could have had a negative impact on other devices.  If so, I can change it back.  I just noticed one comment from an Xperia Play user that said Mario was running poorly, so wanted to see if that is happening to everyone.

The other thing that is different since the last update is the Tribuffer Optimization, which is disabled by default (gles2n64 video settings).  I don't notice any difference on my phone with it enabled or disabled, but maybe it affects other devices.  Could I get some feedback on whether tribuffer optimization enabled/ disabled has a noticeable affect on anyone's device?

I'm trying to get a feel for which of these two changed (if not both of them) might have had a negative effect on the Xperia Play (and possibly other devices.
Logged
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 Epic_bubble

  • long
  • ***
  • Posts: 235
    • View Profile
Re: Beta Testing Has Begun!
« Reply #202 on: February 13, 2012, 05:09:50 AM »
If there is a change in speed then it is very minimal. Changing the tribuffer option doesn't seem to do very much either.

It might be a good idea to get xperia64 to test this too since the US model is slightly different to the UK model. The US one uses stock gingerbread while the UK one uses sony erricsons custom interface.
Logged
Device: Xperia play
CPU: Qualcomm 1 GHz Scorpion (Snapdragon)
GPU: Adreno 205
RAM: 512 MB
Screen res: 854 ? 480
ROM: stock android 2.3.4 rooted

Offline redx1423

  • bit
  • Posts: 1
    • View Profile
Re: Beta Testing Has Begun!
« Reply #203 on: February 15, 2012, 09:54:47 AM »
The newer update force Closes on my Samsung admire when i Start a Game
Logged

Offline Brock

  • byte
  • *
  • Posts: 27
    • View Profile
Re: Beta Testing Has Begun!
« Reply #204 on: February 15, 2012, 06:22:32 PM »
Quote from: Paul on February 12, 2012, 09:28:54 PM
Anyone notice Mario 64 running worse since the update?  I changed the compiler options which provided a very small improvement on my phone, but could have had a negative impact on other devices.  If so, I can change it back.  I just noticed one comment from an Xperia Play user that said Mario was running poorly, so wanted to see if that is happening to everyone.

The other thing that is different since the last update is the Tribuffer Optimization, which is disabled by default (gles2n64 video settings).  I don't notice any difference on my phone with it enabled or disabled, but maybe it affects other devices.  Could I get some feedback on whether tribuffer optimization enabled/ disabled has a noticeable affect on anyone's device?

I'm trying to get a feel for which of these two changed (if not both of them) might have had a negative effect on the Xperia Play (and possibly other devices.

I have noticed that on my phone, it runs way slower since the recent updates.
LG Optimus One/T
Logged
Device: Samsung Galaxy S2
CPU: 1.5 GHz Dual Core  Snapdragon S3
RAM: 1GB
Resolution: 800 x 480
Rom: 4.1.2 Jelly Bean Stock

Device: Mach Speed Trio Stealth G2
CPU: 1.5 GHz Dual Core ARM Cortex-A9
RAM: 1GB DDR3
Resolution: 800x480
Rom: 4.0.4 ICS Stock

Device: Mach Speed Trio
CPU: 1.2 GHz Boxchip A13
RAM: 512MB DDR3
Resolution: 480x272
Rom: 4.0.4 ICS Stock

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #205 on: February 15, 2012, 06:29:27 PM »
I believe I've tracked down the cause for the slowdown.  I'll have an update available shortly (just need to do a little testing first to make sure I didn't break anything)
Logged
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 Brock

  • byte
  • *
  • Posts: 27
    • View Profile
Re: Beta Testing Has Begun!
« Reply #206 on: February 15, 2012, 06:36:12 PM »
Quote from: Paul on February 15, 2012, 06:29:27 PM
I believe I've tracked down the cause for the slowdown.  I'll have an update available shortly (just need to do a little testing first to make sure I didn't break anything)

Cool, thanks Paul! :-D
Logged
Device: Samsung Galaxy S2
CPU: 1.5 GHz Dual Core  Snapdragon S3
RAM: 1GB
Resolution: 800 x 480
Rom: 4.1.2 Jelly Bean Stock

Device: Mach Speed Trio Stealth G2
CPU: 1.5 GHz Dual Core ARM Cortex-A9
RAM: 1GB DDR3
Resolution: 800x480
Rom: 4.0.4 ICS Stock

Device: Mach Speed Trio
CPU: 1.2 GHz Boxchip A13
RAM: 512MB DDR3
Resolution: 480x272
Rom: 4.0.4 ICS Stock

Offline Tsudeily

  • bit
  • Posts: 9
    • View Profile
Re: Beta Testing Has Begun!
« Reply #207 on: February 17, 2012, 06:02:45 AM »
Looking forward to getting this. I'm switching to Android as soon a check arrives. :D This emulator seems to have the best reviews out of the available n64s for Android.

Silly question for now xD... I have seen that other n64 emulators offer a rumble feature with the device vibrating.. Does this one offer that?
« Last Edit: February 17, 2012, 06:05:27 AM by Tsudeily »
Logged

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Beta Testing Has Begun!
« Reply #208 on: February 17, 2012, 01:40:25 PM »
No Rumble yet.  This will be added soon (should be fairly easy, just have to make the connection through JNI).
Logged
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 Tsudeily

  • bit
  • Posts: 9
    • View Profile
Re: Beta Testing Has Begun!
« Reply #209 on: February 17, 2012, 03:02:12 PM »
Awesome. Thanks for the reply. :D

Quote from: Paul on February 17, 2012, 01:40:25 PM
No Rumble yet.  This will be added soon (should be fairly easy, just have to make the connection through JNI).
Logged
Pages: 1 ... 12 13 [14] 15 16 ... 57
« previous next »