I was trying to use lwi_me.py but it says the app is not debuggable.
python .\lwi_me.py --daemon ..\..\..\streamline\bin\arm\gatord --32bit --lwi on --package com.package
ERROR: Package 'com.package' not debuggable
The same apk works fine on a Galaxy A10.
Some relevant info about Galaxy J2 Pro:
Android version: 7.1.1
Kernel version: 3.18.31-18635600
Should it be working?
Forgot to ask, could you advise of a low-end device in which everything works?
Forgot to mention: it is an unrooted device.
Got this on streamline:
Failed to set permissions of file on remote device:[run-as: Could not set capabilities: Operation not permitted] com.arm.streamline.deviceconn.adb.AdbSelfCleaningSession$CommandFailedException: Failed to set permissions of file on remote device:[run-as: Could not set capabilities: Operation not permitted] at com.arm.streamline.deviceconn.adb.AdbSelfCleaningSession.pushFileAndSetPermissions(AdbSelfCleaningSession.java:174) at com.arm.streamline.deviceconn.adb.AdbSelfCleaningSession.pushExecutable(AdbSelfCleaningSession.java:103) at com.arm.streamline.databrowser.AndroidDeviceGatordManager$1.lambda$0(AndroidDeviceGatordManager.java:146) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Hi Denis, We don't have a J2 Pro in-house, so we've not tested this one, but I know we had problems with other J-series devices such as the J6.The kernel version in the J-series is relatively old, so many of the improvements to Perf for CPU data access are not present (need kernel 4.3 or newer for those). There was also certainly a generation of Samsung devices around this time where "adb run-as" didn't work at all (https://issuetracker.google.com/issues/37093233#c4) which means we can't connect to any application even if debuggable. This was fixed on the high-end devices like the S7 by a firmware update for the device, but I'm not sure if the J series got that fix. If there is a firmware update for the device give that a go, it might help.
In terms of recommendations, for an entry-level device the Galaxy A10 or A20 are probably the ones we'd recommend starting with. They are new enough to have later Android versions (better tools support in the OS) and kernel versions (better CPU and OS visibility via Perf), and small enough core counts to be an "OK" proxy for older entry-level devices. (Albeit, they are Bifrost GPU architecture, not Midgard).
Our officially supported devices list (i.e. ones that we have bought and test internally) is here:
... but in general I'd expect most new devices to work.
That looks like the issue with "adb run-as" not working, which unfortunately means we don't really have a workaround, sorry.
Thanks for the detailed answer Peter!
View all questions in Graphics and Gaming forum