I know that the device is based on x86, but I've read a few sources say that it can handle ARM just fine. I'm trying to run GTA: Chinatown Wars, but it crashes every time I try to launch it. When I read the logcat, it says that it crashes with this error:
Code:
java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app/com.rockstargames.gtactw-1/lib/arm/libCTW.so" has unexpected e_machine: 40
From what I gather, it seems like there's something wrong with the ARM translator. What baffles me even more is that the game is in the Play Store on the Nexus Player, so, in theory it should work.
Has anyone encountered any similar errors with other ARM-specific apps on the stock ROM?
Related
I have been trying to get Firefox mobile working on my NST (1.2.1) rooted w NookManager.
You can see my progress so far here: http://forum.xda-developers.com/showthread.php?t=1809768
Trying to get beyond version 4.0b2, I get "ABI mismatch from package file" errors. 4.0b3pre builds install through 12-2-2010. The 4.0b3pre from 12-3-2010 is the first to fail with the ABI mismatch.
Versions up to but not including 10.0.5esr are supposed to run on ARMv7 w
Android 2.1. Firefox wants 512 MB of memory though.
Swapper2 made 4.0b1 run better, but doesn't get me past this brick wall.
A very helpful tech over at mozilla suggests that the problem is that builds from that one forward "makes our APK package specify armeabi-v7a".
It is possible to make a build without that change according to him. Is anyone here set up to do that?
Or, is there a hack that might be done in the rooted NST to make it compatible with that requirement?
Despite having OpenJDK 6 (openjdk-6-jre 6b27-1.12.7-2) installed and in use. I get the “<E>”s which break compilation; removing them, compilation succeeds, but that leads to other problems with the resulting image. Certain applications will crash with this error:
java.lang.NoSuchMethodError: no method with name='add' signature='(Ljava/util/EZ' in class Ljava/util/HashSet
(No other JDKs are installed; all relevant /etc/alternatives symlinks are pointing to the right files.)
What are you building?
Sent from my Nexus 4 using Tapatalk
SMillerNL said:
What are you building?
Click to expand...
Click to collapse
CM11.
(I've altered the title, but I couldn't do so immediately.)
Got this via IRC:
<Tortel> openjdk may still have issues with CM11.0
<Tortel> I know that it broke the build initially
<Turl> Tortel: they were fixed though
<Turl> unless someone broke it last week or so, OpenJDK 7 was working ok
Click to expand...
Click to collapse
I'll give that a try later.
Okay: results are in, regarding this <E> problem, for building.
FAIL: OpenJDK 6 and 7 (as found in Debian testing). I aborted the builds as soon as I saw that the problem was present.
WORKS: Oracle Java 7 JDK.
As for whether I get some apps crashing due to unresolved symbols, I've yet to find out.
Hi folks,
Has anybody actually tried running Ubuntu Desktop on Note 3 either through "Linux on Android" or dual booting?
If so, were you able to run Unity or any other desktop environment?
And finally performace, is it good enough to work in say LibreOffice without much pain?
still not for note 3 yet
This is what I found on Linux on Android site, regarding Note 3 9005:
Mknod permission denied
Had to gut the bootscript and recreate without all the checks
Essentially the new bootscript contains no checks just the commands and is around 35 lines long.
Running the new bootscript still causes mknod permission denied, however, if you open the bootscript in a text editor copy all and paste into the terminal and execute line by line, you get into the chrooted environment.
Tested : ubuntu 13.04 , 13.10 large
What works:
Ssh server
Apt-get
Nano
Ping
Traceroute
And a lot of terminal stuff
What does not:
Mc : garbled
Vnc : dbus error
Aircrack-ng : no monitoring mode
Installing another graphical environment: install fails , due to 2 package errors
Ultimately moderately useful but mc is a real loss.
Click to expand...
Click to collapse
According to this: http://forum.xda-developers.com/showpost.php?p=48265575&postcount=1887
Ubuntu should work on Note 3 without the problems described above.
I wonder about performance though, does this solution allow Ubuntu to utilize all four cores and available RAM or run it as a single process under Android.
zandaqo said:
Hi folks,
Has anybody actually tried running Ubuntu Desktop on Note 3 either through "Linux on Android" or dual booting?
Click to expand...
Click to collapse
I would do it like I did with the tf101 and the tf201 but honestly I am not keen on triggering knox
As for capability, when booted natively there will be some things that won't work right at first due to qDSP signed binaries needing to be uploaded to hexagon. Capability wise though it should be fine, with 3GB ram and an S800 it should outperform the TF201 at pretty much every task under linux.
lilstevie said:
I would do it like I did with the tf101 and the tf201 but honestly I am not keen on triggering knox
Click to expand...
Click to collapse
If we manage to root without triggering knox, I guess we can also run "Linux on Android" without triggering it. Though installing natively is out of question in this case.
Phoenix os for x86 v2.1.0released. In this version we enhance the hardware compatibility, including: sound card, network adapter, etc. And we add smart casting for Strike of Kings.
Update Details
- Keyboard mapping updates to version 2.5 with smart casting for Strike of Kings.
- The bug that window size won't be saved after restart has been fixed.
- Enhance the hardware compatibility, including: sound card, network adapter, etc.
- "Start Phoenix system" shortcut supports legacy boot now.
- Optimize the Phoenix OS downloader.
Link: http://bbs.phoenixstudio.org/en/showthread.php?tid=6511
Download:
EXE
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.179.32bit.exe
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.175.64bit.exe
https://mega.nz/#!MH4ijZRK!NiRZaFlM54tsNrufmtEhel6oKnWbd_QjNOYauCrRtcM
https://mega.nz/#!JOxVyZrL!c2gL9s9TrTYEMUvJQoCbpXQ_x49GcSsaPY74w6DQa2w
ISO
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.179.32bit.iso
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.175.64bit.iso
https://mega.nz/#!ADQjgRhZ!tC19m6UKuiG1waOHBuypepqkXz3qnMNnF-DF2EMPNKg
https://mega.nz/#!9SIEnboR!GTn3nnW1KlhtZ7XkI98T7Tsaljin8OmZGBqMhhAcm-4
What is the minimum hardware to run Phoenix OS 2.1?
I have an EEE PC 1201ha, does it work?
Specification
Intel® Atom ™ CPU Z520 - 1.33 GHz, 1 core, Hyper-Threading, SSE2, SSE3, SSSE3
Intel® Poulsbo US15W Chipset
RAM DDR2 SO-DIMM 2GB
SSD GOLDENFIR, model T650-60GB
@arielbw install to USB stick and test.
Currently there is no compatibility database, nor no one is working on one.
EEE PC are usually the most well supported Android-x86 devices, so everything should work fine.
EDIT:
Your hardware is enough to make Phoenix OS run.
On 32-bit version, Google Play doesn't work properly. Trying to update Google Play Services, it says that it can't be installed (Error code: -501). Haven't tested the 64-bit version yet, but I can guess it will be the same
@meanhacker are you manually trying to update GMS or it's automatic pop-up?
If manual, why even update?
Vioner said:
@meanhacker are you manually trying to update GMS or it's automatic pop-up?
If manual, why even update?
Click to expand...
Click to collapse
I'm trying to play Bombsquad which requires Google Play Services to be up to date. When I open up Bombsquad, it tell me that Google Play Services needs to be updated. I click OK, and then it takes me to the Google Play Store. Then, I click Update. It's not manual, but it prevents me from doing certain things.
I'm having the same problem.
Just installed the x64 version and I cant even open chrome because it needs google play services updated.
Even tried downloading the apk, but it wont install...
Maheidem said:
I'm having the same problem.
Just installed the x64 version and I cant even open chrome because it needs google play services updated.
Even tried downloading the apk, but it wont install...
Click to expand...
Click to collapse
Yeah I had the same issue until I solved it. Have a look here
Problem on the screen - eee pc 1201ha
Vioner said:
@arielbw install to USB stick and test.
Currently there is no compatibility database, nor no one is working on one.
EEE PC are usually the most well supported Android-x86 devices, so everything should work fine.
EDIT:
Your hardware is enough to make Phoenix OS run.
Click to expand...
Click to collapse
Phoenix OS v2.1.1.190_x86 installed.
Now I have a problem on the screen, an image is duplicated and a bit distorted.
Can someone help me?
Image in the link below
imgur.com/a/DLety
I also installed android-x86-4.0-r1-eeepc.iso. It worked without presenting problems on the screen.
arielbw said:
Phoenix OS v2.1.1.190_x86 installed.
Now I have a problem on the screen, an image is duplicated and a bit distorted.
Can someone help me?
Image in the link below
imgur.com/a/DLety
I also installed android-x86-4.0-r1-eeepc.iso. It worked without presenting problems on the screen.
Click to expand...
Click to collapse
Your integrated graphics might be the issue. I looked up the specs of your laptop:
https://www.asus.com/Laptops/Eee_PC_1201HA_Seashell/specifications/
http://ark.intel.com/products/35444/Intel-SCH-US15W
I actually had something similar to this on my OSMC splash screen (Kodi build on the raspberry pi). I found a post about it here. Have a look and I think you will probably need to let Phoenix OS know your native screen resolution. I think that's why it's distorting like that.
Well, it worked! Thanks!
Meu processador intel® celerom M 430 1.73 ghz roda qual versao do phoenix os ?
I've been having a hard time finding my way around the camera situation on LOS. I've been reading a few threads, somewhere people suggest that it's not possible to port it because it needs to be baked into the ROM. In other situations people seem to refer to the now deprecated oyx-fi module for Magisk.
I tried tinkering around, i unpacked the OTA image and tried to push OnePlusCamera to /system/system_ext/priv-app as it's configured on the stock firmware but besides running out of space (partition has 29MB left and the app itself is over 130MB in size) adb disable-verity made the phone unstable and lead to the Qualcomm Crash Dump screen within a minute or two. Pushing libsnpe_dsp_v66_domains_v2_skel.so alone apparently wasn't enough either to do the magic. I thought about setting a softlink but since the phone would crash, i gave up on that method since i don't know how deal with such issues.
Based on a logs from a normal install i would assume that some services/applications might be missing that are essential for OPCam to work. One of the errors being:
Code:
[08-05 13:11:18.371 4892:4892 E/CameraActivity]
getRequiredPermissions() - failed
android.content.pm.PackageManager$NameNotFoundException: com.oneplus.camera.CAMERA_SERVICE
at android.app.ApplicationPackageManager.getPermissionInfo(ApplicationPackageManager.java:375)
at com.oneplus.camera.CameraActivity.getRequiredPermissions(CameraActivity.kt:2255)
at com.oneplus.camera.CameraActivity.requestRequiredPermissions(CameraActivity.kt:4200)
at com.oneplus.camera.CameraActivity.onResume(CameraActivity.kt:3679)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1456)
at android.app.Activity.performResume(Activity.java:8129)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4428)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4470)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
I tried installing OnePlusCameraService.apk but it resulted in the issue below.
Code:
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.oneplus.camera.service has no signatures that match those in shared user android.uid.system; ignoring!]
If anyone would fancy to have a look at the logcat output to hint me in a direction, that would be much appreciated. My knowledge around android is pretty poor and googling only does so much. All I'm doing is trial and error .... The reason for all this is because I'd prefer to get the stock camera working, with vendor sources, as i have little trust in the random apks and configs that people upload to whatever platform and it would be to sad not to be able to use the otherwise pretty good camera.
Thanks in advance for help
@chandu dyavanapelli can help you out perhaps