Android based on Intel and not ARM support?

[labba]

Hi,
I have the iRazor that is runing an Intel CPU and not ARM and currently can't run the application at all...

is there going to be a support of this type of architecture ?

Thanks,
LaBBa.

[[Unknown]]

I think what we need most right now is someone who has three things:

* One of these devices.
* A compiler that can build for the device.
* A bit of time to debug and try it.

-[Unknown]

[VIRGIN KLM]

I think what we need most right now is someone who has three things:

* One of these devices.
* A compiler that can build for the device.
* A bit of time to debug and try it.

-[Unknown]

Just a quick stop to tell you that you can actualy skip the "One of these devices" requirement since you can do the tests on Android x86 builds, specificaly build 20130228 and ReleaseNote 4.0-RC2 (the later has an optional ARM translator too, simmilar to what Intel Android phones have). I'm currently using it on an OLD pc for mostly web browsing and it seems to work exactly the same as Androids with Intel CPUS (also noticed that on GooglePlay, without the ARM translator, it lists only the apps that have Intel CPU support!)

Just pick a USB stick you don't use anymore and do a live USB:
https://code.google.com/p/android-x86/downloads/list

[livisor]

I think what we need most right now is someone who has three things:

* One of these devices.
* A compiler that can build for the device.
* A bit of time to debug and try it.

-[Unknown]

Just a quick stop to tell you that you can actualy skip the "One of these devices" requirement since you can do the tests on Android x86 builds, specificaly build 20130228 and ReleaseNote 4.0-RC2 (the later has an optional ARM translator too, simmilar to what Intel Android phones have). I'm currently using it on an OLD pc for mostly web browsing and it seems to work exactly the same as Androids with Intel CPUS (also noticed that on GooglePlay, without the ARM translator, it lists only the apps that have Intel CPU support!)

Just pick a USB stick you don't use anymore and do a live USB:
https://code.google.com/p/android-x86/downloads/list

I'm not sure I got this right,I can pick an old usb memory stick and install android on it to run on any pc with usb port?

[Sankareaftw]

Hi,
I have the iRazor that is runing an Intel CPU and not ARM and currently can't run the application at all...

is there going to be a support of this type of architecture ?

Thanks,
LaBBa.

Honestly as rude as it is to say you'll most likely need a new phone regardless of whether or not someone builds for intel cpu anyways im using Qualcomm MSM8960L Snapdragon on 4g lg motion and it still isnt the best out there regardless of whether you like it or not your best bet is to get a new phone although google searches cant seem to find the irazor and keep sending me to razors for shaving so i have no clue lol but if it is a phone honestly your really cant expect any sort of intel based thing to come through for you in anyway possible cause atm im also running a compaq presario cq56 which is terrible at most things so intel based things unless you plan on throwing lots of money down the drain are certainly useless but if you have money to spend intel is the way to go

[xsacha]

We had a guy with an Intel-based phone on here before and he said the ARM version runs fine on his x86 processor because Intel emulates ARM apps by default.

[VIRGIN KLM]

I'm not sure I got this right,I can pick an old usb memory stick and install android on it to run on any pc with usb port?

Yep did it already. The builds are based on the versions of Android that is used on phones that are Intel based, just ported to PC. You can do the Android x86 tests there without the need of a phone that supports it, the only problem is that it will be really faster than any phone out there so it will be a bit easy to monitor what's fast and what's not to monitor stuff that go slow. Any developer that considers to work again on Android x86 support just Install those builds on a USB flashdrive you don't use anymore. If you have any problems and I can help, I'm here!

[fischfrosch]

PPSSPP works fine with Motorola Razr I

[Djokk]

On my ZTE Grand X In with Intel doesn't work.

[YaPeL]

I think what we need most right now is someone who has three things:

* One of these devices.
* A compiler that can build for the device.
* A bit of time to debug and try it.

-[Unknown]

* I have a Razr I
* I managed to build the x86 version for android
* Don't have much time (like close to 0), I guess now I have to build a debug version and then run gdb to see where it explodes right? Any help on building the debug version would save me some precious time.

[[Unknown]]

I don't know much about Android, but you probably want to change android/jni/Android.mk:

From:
LOCAL_CFLAGS := -O2 -fsigned-char -ffast-math -Wall -Wno-multichar -Wno-psabi

To:
LOCAL_CFLAGS := -Og -g -fsigned-char -ffast-math -Wall -Wno-multichar -Wno-psabi

Or if -Og doesn't work, -O0 or w/e.

And then same here:

LOCAL_CFLAGS := -DUSE_PROFILER -DGL_GLEXT_PROTOTYPES -DUSING_GLES2 -O2 -fsigned-char -Wall -Wno-multichar -Wno-psabi -Wno-unused-variable -fno-strict-aliasing -ffast-math

etc. At that point it should be doable to debug I think, and I've seen people post stack traces, but I don't know how it's done unfortunately.

-[Unknown]

[YaPeL]

I don't know much about Android, but you probably want to change android/jni/Android.mk:

From:
LOCAL_CFLAGS := -O2 -fsigned-char -ffast-math -Wall -Wno-multichar -Wno-psabi

To:
LOCAL_CFLAGS := -Og -g -fsigned-char -ffast-math -Wall -Wno-multichar -Wno-psabi

Or if -Og doesn't work, -O0 or w/e.

And then same here:

LOCAL_CFLAGS := -DUSE_PROFILER -DGL_GLEXT_PROTOTYPES -DUSING_GLES2 -O2 -fsigned-char -Wall -Wno-multichar -Wno-psabi -Wno-unused-variable -fno-strict-aliasing -ffast-math

etc. At that point it should be doable to debug I think, and I've seen people post stack traces, but I don't know how it's done unfortunately.

-[Unknown]

Thanks, I'll give it a shot, however the ndk-build help from android says something quit different
http://pastebin.com/jBvSMyzU

But I don't know where to put that options.

[YaPeL]

well I try with ndk-gdb but I get this odd error:
/home/japel/android-ndk-r8e/./build/core/add-application.mk:128: Android NDK: WARNING: APP_PLATFORM android-9 is larger than android:minSdkVersion 8 in ./AndroidManifest.xml
jni/Android.mk:261: *** Android NDK: Aborting. . Alto.
ERROR: The device does not support the application's targetted CPU ABIs!
Device supports: x86 armeabi-v7a
Package supports: Android NDK:

and for launching it I just used this script:

"./ndk-gdb --adb="path to my adb bla bla" --start --project="path to the ppsspp project"

[[Unknown]]

Hmm, so it's saying that the device supports x86, but the package doesn't?

Did you revert this change?

https://github.com/hrydgard/ppsspp/commi...f74d18e166

Also see:
http://software.intel.com/en-us/articles...plications
http://software.intel.com/en-us/articles...plications

Maybe it's because of the API level? Apparently only 9 or higher is supported for x86, per:
http://developer.android.com/tools/sdk/n...orm-compat

-[Unknown]

[YaPeL]

Hmm, so it's saying that the device supports x86, but the package doesn't?

Did you revert this change?

https://github.com/hrydgard/ppsspp/commi...f74d18e166

Also see:
http://software.intel.com/en-us/articles...plications
http://software.intel.com/en-us/articles...plications

Maybe it's because of the API level? Apparently only 9 or higher is supported for x86, per:
http://developer.android.com/tools/sdk/n...orm-compat

-[Unknown]

The api level fixed the warning, but, the warning was just that :p

it seems its having issues with this 2 import lines on Android.mk line 261:

$(call import-module,libzip)
$(call import-module,native)

If I remove those 2 lines it goes a little bit further but then I get this:

ERROR: Non-debuggable application installed on the target device.
Please re-install the debuggable version!

Of course I deleted my old app with the new one.
Only places I added to be "debuggable" are on the ab.sh script:

cp -r ../flash0 assets
cp -r ../lang assets
NDK_MODULE_PATH=..:../native/ext $NDK/ndk-build -j3 NDK_DEBUG=1 TARGET_PLATFORM=android-9 - $*

and bin/AndroidManifest.xml :

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="org.ppsspp.ppsspp"
android:versionCode="76"
android:versionName="0.7.6"
android:debuggable="True"
android:installLocation="auto" >
blabla
</manifest>

after that added an empty space on PpssppActivity.java, and export bla bla.

edit: mm thinking about it, the second error may be due to the removal of $(call import-module,native), since inspecting the app shows no traces of gdb on it.