- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
vtune version : VTune Amplifier 2016 for Systems
command is : amplxe-cl --collect hotspots --target-system=android:Coolpad8750-0xc2fda1f -r d:\profile.data --target-process=com.x.androidhttpserver
the target app is lanched success , and is waiting for debug , bug vtune failed to collect data from remote android device.
message:
amplxe: Using target: android:Coolpad8750-0xc2fda1f
amplxe: Warning: Java code profiling is only available on the devices supported with the Intel Mobile Development Kit for Android. For more information, go to http://software.intel.com/mdk.
amplxe: Error: Cannot run data collection for package 'com.x.androidhttpserver'. A corrupted version of the run-as utility is detected on your Android device. For more details, see product Release Notes.
amplxe: Collection failed.
help and thx!
allen.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Allen,
What is the Android version you have on the Coolpad device?
You seems have broken "run-as" utility in the Android image which prevents debugging native applications.
Is it possible to upgrade Android version on the phone ?
Regards, Katya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ekaterina-logovskaya (Intel) wrote:
Hello Allen,
What is the Android version you have on the Coolpad device?
You seems have broken "run-as" utility in the Android image which prevents debugging native applications.
Is it possible to upgrade Android version on the phone ?
Regards, Katya
Hi Katya,
the device is Coolpad 8720L , android version is 4.3 , kernel version is 3.4.39.
I can't upgrade the android version on the phone.
the target android app is not listed in /data/system/packages.list , is this relevant ?
here is some information , FYI.
root@Coolpad8720L:/ # ls /data/data/com.intel.vtune/results/android/ -al
drwxrwxrwx shell shell 2015-10-14 16:39 tmp1zytq4
drwxrwxrwx shell shell 2015-10-14 16:40 tmpsnxv0r
root@Coolpad8720L:/ # ls /data/data/com.intel.vtune/tmp/ -al
-rw-rw-rw- shell shell 421 2015-10-14 16:40 android_r000hs.opts
drwxrwxrwx shell shell 2015-10-14 16:39 tmp1zytq4
drwxrwxrwx shell shell 2015-10-14 16:40 tmpsnxv0r
thx!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Allen,
If upgrade is not possible, please check this thread on Google side for possible workarounds in v4.3: https://code.google.com/p/android/issues/detail?id=58373
The comment #60 looks like a full workaround, though we did not check it from our side, so please follow with assumed risk: https://code.google.com/p/android/issues/detail?id=58373#c60
Regards, Katya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ekaterina-logovskaya (Intel) wrote:
Hi Allen,
If upgrade is not possible, please check this thread on Google side for possible workarounds in v4.3: https://code.google.com/p/android/issues/detail?id=58373
The comment #60 looks like a full workaround, though we did not check it from our side, so please follow with assumed risk: https://code.google.com/p/android/issues/detail?id=58373#c60
Regards, Katya
thanks for your help!
I'll check it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ekaterina-logovskaya (Intel) wrote:
Hi Allen,
If upgrade is not possible, please check this thread on Google side for possible workarounds in v4.3: https://code.google.com/p/android/issues/detail?id=58373
The comment #60 looks like a full workaround, though we did not check it from our side, so please follow with assumed risk: https://code.google.com/p/android/issues/detail?id=58373#c60
Regards, Katya
this maybe caused by bug of android 4.3. http://stackoverflow.com/questions/17219906/run-as-package-a-b-c-is-unknown-galaxy-s4-jellybean-or-android-4-3
I switched to another android device (android version : 4.04) , but the remote android vtune client seems crashed!
target - Segmentation fault
Segmentation fault
Amplifier cannot detect Android device configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Allen,
Can you please specify a bit more on the new issue:
- What is the new device HW/OS configuration? Is it rooted?
- What is the VTune analysis you try?
- To check that VTune installation is ok on the device please call couple direct commands from a host:
1. adb logcat -c <vtune install dir on host>\bin64\amplxe-androidreg.bat -package-command=install
The command should dump setup.xxx.log to bin64 dir.
2. adb logcat -d >logcat.log
We will need both setup.xxx.log and logcat.log.
Regards, Katya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SAMSUNG GT-I9082
android 4.1.2
Intel VTune Amplifier 2016 for Systems
when I switched to this device , issues above is no longer exists , but generated a new issue , vtune makes the device reboot and then vtune ouput "connection was lost"...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Allen,
We will appreciate detailed info and logs as specified below to triage the issue.
- Is the device rooted ?
- Please provide output of the command line below:
>amplxe-python.exe amplxe-runss.py --context-value-list --target-system=android:<DEVICE_NAME>
- What is the VTune analysis type you run ? Is it Basic hotspots or something else?
- Collect logcat log, and if the device is rooted - dmesg log:
- run logcat console:
- adb logcat -c
- adb logcat >_logcat.log
- run dmesg console:
- adb shell dmesg -c
- adb shell "while true; do dmesg -c; done" >dmesg.log
- run VTune analysis, and then send us the logs
- run logcat console:
Regards, Katya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. the device is rooted;
2,log is below:
C:\Program Files (x86)\IntelSWTools\VTune Amplifier 2016 for Systems\bin64>amplxe-python.exe amplxe-runss.py --context-value-list --target-system=android:41005ff297449000
INFO: Restarting the adbd daemon with root permissions.
androidBoardPlatform: capri
targetOS: Android
OS: Android
isPtraceScopeLimited: false
isTSXAvailable: false
isHTEnabled: false
LinuxRelease: 3.0.31
isPtraceAvailable: true
isGPUAnalysisAvailable: false
ETW: NA
isEtwDxSupported: no
isEtwCLRSupported: no
isPowerAnalysisAvailable: false
isPowerKernelStacksAvailable: false
isSEPDriverAvailable: false
isSEPMICDriverAvailable: false
isNMIWatchDogTimerRunning: false
CPU_NAME: ARM
CPU: ARM
platformType: 0
PMU: Unknown
referenceFrequency: 1200000000
isVTSSPPDriverAvailable: false
LinuxPerfCredentials: Kernel
LinuxPerfCapabilities: disabled:no_sep
LinuxPerfStackCapabilities: fp
isTPSSAvailable: false
isDebugFsAvailable: yes
isFtraceAccessible: yes
isIntelGFX: no
isi915EventGroupPresent: no
isMdfEtwAvailable: false
isCSwitchAvailable: yes
isFtraceIGFXAvailable: no
isFunctionTracingAvailable: no
isIowaitTracingAvailable: no
isVSyncAvailable: no
androidVersionMajor: 4
androidVersionMinor: 1
androidVersionPatch: 0
Collection return code is 0
3. What is the VTune analysis type you run ? : Basic hotspots
4. When VTune is running , the adb device will be disconnected .
ekaterina-logovskaya (Intel) wrote:
Hi Allen,
We will appreciate detailed info and logs as specified below to triage the issue.
- Is the device rooted ?
- Please provide output of the command line below:
>amplxe-python.exe amplxe-runss.py --context-value-list --target-system=android:<DEVICE_NAME>
- What is the VTune analysis type you run ? Is it Basic hotspots or something else?
- Collect logcat log, and if the device is rooted - dmesg log:
- run logcat console:
- adb logcat -c
- adb logcat >_logcat.log
- run dmesg console:
- adb shell dmesg -c
- adb shell "while true; do dmesg -c; done" >dmesg.log
- run VTune analysis, and then send us the logs
Regards, Katya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Allen,
Please start dumping the logs before VTune start, then we will be able to see what was the last message before system reboot:
- adb logcat >_logcat.log
- adb shell "while true; do dmesg -c; done" >dmesg.log
Also from the context-value list it seems the CPU is ARM, and if it's 64-bit, it's not supported either way.
Regards, Katya
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page