学习笔记

I just went through the logs quickly and found:
sysTid=13648 is pending for "com.android.bluetooth" sysTid=14943 .

In binder_transactions.txt, we can see that proc 14943 had several transactions pending there which includes:
pending transaction 2260438: a346f7c0 from 13601:13648 to 14943:0 code 1 flags 10 pri 0 r1 node 2229040 size 112:4 data c6c00aa4

Checking the aplog, I haven't found any significant error related to bluetooth.
But I think it's better to highlight this in your comment and inform the team who own bluetooth to take a look at this while we debugging it.


OAM-22761 OAM-16856
好吧，我知道還是有些亂…對照一下例子好了…

dvm_lock_sample: [system_server,1,ActivityManager,108,ActivityStack.java,288,-,13056,100]

(process|string)       system_server (process name)
(main|int|id)          1 (yes)
(thread|string)        ActivityManager (thread name)
(time|int|ms)          108 (lock time 單位：ms)
(file|string)          ActivityStack.java (file name)
(line|int|id)          288 (對應 file 的行數)
(ownerfile|string)     - (owner file name，- 表示和 file name 一樣)
(ownerline|int|id)     13056 (對應 owner file 的行數)
(sample_percent|int|%) 21 (lock time/500的百分比，佔用500ms以上皆為100%)



$ adb shell wm size
Physical size: 1080x1920
$ adb shell wm density
Physical density: 480
$ adb shell wm size 1080x1920
$ adb shell wm density 480



 2044  ~/workspace/
 2045  ll
 2046  cd ~/workspace/
 2047  ls
 2048  cd sofia_LTE_Android_M/
 2049  ll
 2050  cd device/intel
 2051  ll
 2052  cd sofia_lte
 2053  ll
 2054  cd ../..
 2055  repo sync -c ./
 2056  cd ..
 2057  repo sync -c -j4
 2058  cd device/intel/sofia_lte
 2059  git log .
 2060  git status
 2061  rm slti20mr6/product.mk~
 2062  rm slti20svb/product.mk~
 2063  git status
 2064  git diff
 2065  git add .
 2066  git status
 2067  git commit
 2068  git log .
 2069  git show 65859dec36e
 2070  git commit --amend --signoff
 2071  git log .
 2072  repo_intel upload .
 2073  git format-patch HEAD^
 2074  cat 0001-Add-large-resources-to-AAPT_CONFIG.patch
 2075  repo_intel start forupload .
 2076  git branch
 2077  git log .
 2078  clear
 2079  git am 0001-Add-large-resources-to-AAPT_CONFIG.patch
 2080  git log .
 2081  clear
 2082  repo_intel upload .
 2083  history


https://android.intel.com/#/c/427801/


领取的机器：
BB38053 -- Sofia3GR-MRD6S
This bug is now being tracked in the Applications Compatibility JIRA project (ACAA). You can view the progress of this bug in the ACAA project by clicking on the linked
bug above in the “Issue Links” section. If you don’t have access to ACAA please follow [this link|https://eam.intel.com/eamweb/RequestAccess/JustifyAccess.aspx?Others=FALSE&AddAccessEntitlementItemIDs=764194] to get access.

下载版本路径
https://jfstor001.jf.intel.com/artifactory/simple/irda-jf/irda-l/releases/L1R101040/cohol-userdebug/out/dist/

https://jfstor001.jf.intel.com/artifactory/otc-jf/releases/gmin-l/L1R201070/s3gr10m6s-userdebug/out/dist/

https://mcg-depot.intel.com/artifactory/cactus-absp-jf/

https://mcg-depot.intel.com/artifactory/cactus-absp-jf/llp_mr1-latest/68/s3gr10m6s/userdebug/

https://mcg-depot.intel.com/artifactory/cactus-absp/build/eng-builds/llp_mr1/PSI/weekly/2015_WW34/r2_slti20mr6/userdebug/

Index of cactus-absp/build/eng-builds/llp_mr1/PSI/weekly/2015_WW28


https://mcg-depot.intel.com/artifactory/cactus-absp-jf/build/eng-builds/master/PSI/

nexus 版本下载

https://jfstor001.jf.intel.com/artifactory/simple/otc-jf/cts/Nexus/MRA58L/

分析Log的过程
OAM-12406
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On http://crashtool.tl.intel.com/crashtoolStrutsWEB/event.do?action=display&eventId=6b4882efefeb40bb26dd
android.display- waiting to lock tid=21
{code}

  "android.display" prio=5 tid=21 Native
  | group="main" sCount=1 dsCount=0 obj=0x12e4eba0 self=0x7fbcbf43b200
  | sysTid=3195 nice=-4 cgrp=default sched=0/0 handle=0x7fbcbf4cd700
  | state=S schedstat=( 918458523 227360968 3189 ) utm=68 stm=23 core=3 HZ=100
  | stack=0x7fbcac2fb000-0x7fbcac2fd000 stackSize=1036KB
  | held mutexes=
  kernel: binder_thread_read+0x417/0xdec
  kernel: binder_ioctl+0x6ec/0x8b0
  kernel: do_vfs_ioctl+0x2f0/0x4f0
  kernel: SyS_ioctl+0x81/0xa0
  kernel: system_call_fastpath+0x16/0x1b
  native: #00 pc 000767c5  /system/lib64/libc.so (__ioctl+5)
  native: #01 pc 000ac0ca  /system/lib64/libc.so (ioctl+42)
  native: #02 pc 0003fbfe  /system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+190)
  native: #03 pc 00040688  /system/lib64/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+120)
  native: #04 pc 000408df  /system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+159)
  native: #05 pc 00037947  /system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+71)
  native: #06 pc 000dd9df  /system/lib64/libmedia.so (android::BpRemoteDisplay::dispose()+79)
  native: #07 pc 00126a41  /system/lib64/libandroid_runtime.so (???)
  native: #08 pc 0031e7c7  /data/dalvik-cache/x86_64/system@framework@boot.oat (Java_android_media_RemoteDisplay_nativeDispose__J+183)
  at android.media.RemoteDisplay.nativeDispose(Native method)
  at android.media.RemoteDisplay.dispose(RemoteDisplay.java:110)
  at android.media.RemoteDisplay.dispose(RemoteDisplay.java:89)
  at com.android.server.display.WifiDisplayController.updateConnection(WifiDisplayController.java:663)
  at com.android.server.display.WifiDisplayController.disconnect(WifiDisplayController.java:630)
  at com.android.server.display.WifiDisplayController.retryConnection(WifiDisplayController.java:644)
  at com.android.server.display.WifiDisplayController.access$3700(WifiDisplayController.java:79)
  at com.android.server.display.WifiDisplayController$20.run(WifiDisplayController.java:1043)
  at android.os.Handler.handleCallback(Handler.java:739)
  at android.os.Handler.dispatchMessage(Handler.java:95)
  at android.os.Looper.loop(Looper.java:135)
  at android.os.HandlerThread.run(HandlerThread.java:61)
  at com.android.server.ServiceThread.run(ServiceThread.java:46)
{code}
According to the following logs, we could see the BnRemoteDisplay side of the binder transaction{android::BpRemoteDisplay::dispose()}, which was 2851:4154.
{code}
08-12 18:22:49.371     0     0 I KERNEL  : [  243.527366] binder: release 3171:3195 transaction 91970 out, still active
{code}
{code}
proc 2851
  thread 4154: l 01
    incoming transaction 91970: ffff880060a73380 from 0:0 to 2851:4154 code 1 flags 10 pri -4 r1 node 77313 size 68:0 data ffffc90019280320
{code}

The BnRemoteDisplay side seemed in process MediaServer.
{code}
----- pid 2851 at 2015-08-12 18:22:11 -----
Cmd line: /system/bin/mediaserver
ABI: 'x86_64'
......
"Binder_6" sysTid=4154
  #00 pc 0000000000013392  /system/lib/libc.so
{code}

It's a deadend to me to investigate, but I found the similar crash with IMINAN-16793 and IMINAN-33617.
Please let someone senior in Media team check it. Thanks.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

LOCAL_DEX_PREOPT := false

提交bug地址
http://browser-desktop.sh.intel.com/aosp-integration/

M LTE 的版本路径
https://mcg-depot.intel.com/artifactory/cactus-absp-jf/master-latest/152/r2_slti20mr6/userdebug/

可以申请waiver
https://sites.google.com/a/intel.com/otc-android-cts/android-cts/m-waivers-and-issues?pli=1

monkey测试指令
adb shell  
monkey -p com.google.android.GoogleCamera 100000
adb shell monkey -p com.google.android.apps.plus  --throttle 50 500
日志级别 Level 1

示例 adb shell monkey -p com.htc.Weather –v -v 100

说明  提供较为详细的日志，包括每个发送到Activity的事件信息

 

日志级别 Level 2

示例 adb shell monkey -p com.htc.Weather –v -v –v 100

说明  最详细的日志，包括了测试中选中/未选中的Activity信息


adb shell am broadcast -a "action_finish"

https://buildbot.tl.intel.com/absp/builders/

 1.am启动一个activity

adb shell am start com.example.scr/.MainActivity

2.am启动一个带参数的activity

adb shell am start -n com.magcomm.touch/.TouchLetterActivity --es letter "e"

--es传递的是字符串，还有ei，el，ez等参数

-n使用包名加类名，还有a动作，c CATEGORY等

3.am发送一个广播，使用action

adb shell am broadcast -a magcomm.action.TOUCH_LETTER

adb shell am start -n com.centurysoft.fruityrobo/com.idsky.android.impl.ui.IdskySplashActivity

4.am发送一个带参数的广播，使用action

adb shell am broadcast -a magcomm.action.TOUCH_LETTER --es letter "e"

5.am启动一个服务，不带参数时默认使用包名加类名启动，参数时n，a，c

adb shell am startservice com.android.music/.MediaPlaybackService

6.关闭一个activity或者服务之类，使用包名就行

adb shell am force-stop com.magcomm.touch

aapt d badging ~/4cf1a038ad47037afa2f9d523b031460.apk | grep "version"

/home2/hongcheng/cht-stable-1a/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8/bin/x86_64-linux-android-addr2line -e /home2/hongcheng/cht-stable-1a/out/target/product/r2_cht_ffd/symbols/system/lib64/libsurfaceflinger.so 00000000000326d4

~/workspace/sofia_LTE_Android_M_R2/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.9/bin/x86_64-linux-android-addr2line -e
查看谷歌patch的路径
https://android-review.googlesource.com/#/c/113164/

http://browser-desktop.sh.intel.com/aosp-integration/

刷版本工具
http://jfumgbuild-depot.jf.intel.com/build/eng-builds/Tools/PhoneFlashTool/releases/5.1.0.0/

查询版CTS本工具
http://ppdcm.intel.com/share/Alvaro/Google_deliverables/CTS/http://ppdcm.intel.com/share/Alvaro/Google_deliverables/CTS/cts_5.1-r1/

网上查询代码路径
http://sourcebrowser.tl.intel.com:8080/source/xref/CHT51_STABLE/

提交代码路径
http://ctegerrit.sh.intel.com:8080/#/q/status:open


选择不了的权限
Enterprise Applications - Google Apps - Google Apps Account View Application(s)

adb shell getprop | grep ram

ro.config.low_ram

objdump -tT libmortargame.so | grep native_1GLESVersion

~/bin/DownloadTool/DownloadTool -c1 --erase-mode 3 --library ~/bin/DownloadTool/libDownloadTool.so  *.fls
python ACS.py -d ECS2-Android-LLP -c CAMPAIGN/SystemFunctional/M/MR_0/TR/Houdini -b myBench_usb
https://jira01.devtools.intel.com/secure/Dashboard.jspa?selectPageId=30701

Lmrl cts:
repo init -u https://android.googlesource.com/platform/manifest -b lollipop-mr1-cts-dev
repo sync -j4
lmr1:
repo init -u ssh://android.intel.com/manifests -b android/l/mr1/master
repo sync -j4


r6_legacy wiki: https://wiki.ith.intel.com/display/ANDROIDCAS/r6_legacy
repo init -u ssh://android.intel.com/a/aosp/platform/manifest -b platform/android/r6_legacy -m android-r6

 
​GOOGLE SOURCE ENV
 
https://source.android.com/source/initializing.html
 
CTS DOC
http://static.googleusercontent.com/media/source.android.com/zh-CN/us/compatibility/android-cts-manual.pdf
 
env:
http://wiki.ith.intel.com/display/CACTUS/2.1.2+-+Set+Local+Environment
 
BUG list:
https://jira01.devtools.intel.com/secure/Dashboard.jspa​​
 
 
 du -a | grep XXX
 
查找指令
 1254  git log
 1255  ls
 1256  find . -name URLConnectionTest.java
 1257  git blame ./luni/src/test/java/libcore/java/net/URLConnectionTest.java -L 100,110
 1258  git show 51e468ab
 git fotmat-patch -1

r5-stable
make flashfiles blank_flashfiles -j5 进行编译

2015.6.18任务
Sf3g_mrd5_p1_v2

5/5 Passed on SoFIA LTE B with L1l000088 :user.
Please reporter use L1l000088  retest this issue and close it.

Hardware: SoFIA LTE B
Build: https://mcg-depot.intel.com/artifactory/cactus-absp-jf/llp_mr1-latest/76/r2_slti20mr6/user/
CTS verifier: http://ppdcm.intel.com/share/Alvaro/Google_deliverables/GTS/GTS%202.1_r2/

Use Nexus 5 to co-test.
Device: Nexus 5
Build: https://dl.google.com/dl/android/aosp/hammerhead-lmy48i-factory-a38c3441.tgz
CTS verifier: https://dl.google.com/dl/android/cts/android-cts-verifier-5.1_r2-linux_x86-arm.zip

WiFi maybe not stable. Keep WiFi is always connected during test.
Test step:

    Click "GO Negotiation Responder Test" on SoFIA LTE B.
    Click "GO Negotiation Requester Test" -> "Go negotiation test (PIN)" on Nexus 5.
    Chosse SoFIA LTE device to connected. PIN will be shown on Nexus 5.
    Input the PIN to SoFIA LTE A. The dialog will be disappear.
    Click "Ok" on Nexus 5.
    "Test passed successfully." will show on Nexus 5.

Test Fail:
The device is SoFIA LTE B.