app power consumption hw5

HW 5 App power profiling

資工組陳顥文

P76034305

Requirement• 上次的作業是請大家對 mobile device 上的 components 進行耗電量的測試，接下來希望大家選定一個 APP 去進行耗電量分析。此工作請分為兩部分進行 :

• 利用 APP 行為去預估分析其耗電量。• 實際測試其耗電量。

• 實驗步驟如下 :• 規劃 APP 使用動作與流程，以重複實驗。• 建置設計兩種不同的使用環境，包含 Android 系統的狀態以及是否允許其他 Activity 或者

services 同時進行 ?• 分析此兩種使用環境下的耗電量差異為何 ?• 比較預估方式與實測的耗電量差距並分析其原因。

• 當手機的耗電量達到低臨界值時，系統該如何因應 ?• 將無用的 service 停掉 ?• 將 components 停掉 ?• 強制關閉部分 APP?• 置之不理 ?....etc

Device• Sony Z Ultra C6833 LTE version with official 4.4.4 ROM• 2.20GHz Qualcomm Snapdragon 800• Elpida LPDDR2 RAM• 6.4” 1080*1920• Daily use application load and run.

General Setting• Not turn on Airplane mode.• Not limit CPU.• Keep Location, Bluetooth, WiFi, Cellular on.• Allow all background service active.

Scenario• Scenario A• IN DOOR WIFI (Home)• OUT DOOR Cellular+GPS Place A (NCKU)• OUT DOOR Cellular+GPS Place B (Taipei MRT)

• Scenario B• IN DOOR WIFI (Home)• OUT DOOR Cellular+GPS Place A (NCKU)• OUT DOOR Cellular+GPS Place B (Taipei MRT)

Scenario• Scenario C• OUT DOOR Cellular+GPS Place A (NCKU)

Scenario A steps1. 桌面打開 FB 點右上角檢視通知隨便點入檢視任 3 通知2. 切換到訊息畫面，找任一人對談話來回各 10 句， 4 個貼圖3. 切換到社團畫面4. 切換到 USER 自己的畫面，並點及相片，選擇有你在內的相片任一張放大檢視5. 退出到自己的畫面，發一則文字近況，並且標地標6. 結束• 估計 5 分鐘內完成

IN-DOOR WIFI CONNECT Scenario A HOME

IN-DOOR WIFI CONNECT Scenario A HOME• FB won’t using in physic GPS to locate real location.(guess due to WIFI

location provide enough precision).• Min lid, disable auto brightness.

• Simulate normal using FB at home.

IN-DOOR WIFI CONNECT Scenario A Estimate HOME

假設歷時 5 分鐘平均耗電流(mA)

執行時間佔總時間比例

平均值行時間耗電量

CPU FULL LOAD -1000 10% -100CPU 3C LOAD -800 20% -160CPU 2C LOAD -600 50% -300CPU 1C LOAD -400 20% -80CPU TOTAL AVG -640

比例WIFI ACTIVE 包含 MIN MONITOR -500 50% -250

預估總時間 ( 秒 ) 300

預估平均消耗電流 -890mA

IN-DOOR WIFI CONNECT Scenario A Real HOME

實際狀況實際時間第一次測試平均 -659.429 5 min 12 sec

第二次測試平均 -739.090 4 min 46 sec

第三次測試平均 -708.973 4 min 32 sec

實際平均 -702.497

IN-DOOR WIFI CONNECT Scenario A HOMEGuess reason

• Estimate error rate: 26.7%

• Cause estimating CPU usage percent too high.• CPU hardly getting full load(2.15Ghz).• Most time CPU usage around 50~60%.

OUT-DOOR CELLULAR CONNECT Scenario A NCKU

OUT-DOOR CELLULAR CONNECT Scenario A NCKU• FB will seen not using GPS in 打卡 & Message sending.• Using cellular network with variable signal strength condition.• 58%, -98dBm @ NCKU Success middle area.

• Max lid, disable auto brightness.

OUT-DOOR CELLULAR CONNECT Scenario A NCKU Estimate




執行時間佔總時間比例平均執行時間耗電量

CPU FULL LOAD -1000 5% -50CPU 3C LOAD -800 10% -80CPU 2C LOAD -600 30% -180CPU 1C LOAD -400 55% -220CPU TOTAL AVG 　 100% -530

　　　　　　　　MAX MONITOR LID -400 100% -400

Cellular -500 40% -200

OUT-DOOR CELLULAR CONNECT Scenario A NCKU Real


第二次測試平均 -1204.964724 3 min 46 sec

第三次測試平均 -1163.484078 3 min 49 sec

實際平均 -1171.911115 　

OUT-DOOR CELLULAR CONNECT Scenario A NCKU Guess reason


• More accurate estimate CPU usage.

OUT-DOOR CELLULAR CONNECT Scenario A Taipei Q-Station

OUT-DOOR CELLULAR CONNECT Scenario A Taipei Q-Station• FB will using GPS in 打卡 & Message sending.• Using cellular network with variable signal strength condition.• 86%, -79dBm @ Taipei Q-Station 2F.


OUT-DOOR CELLULAR CONNECT Scenario A Taipei Q-Station Estimate





CPU FULL LOAD -1000 5% -50CPU 3C LOAD -800 10% -80CPU 2C LOAD -600 30% -180CPU 1C LOAD -400 55% -220CPU TOTAL AVG 　 100% -530　　　　GPS -500 10% -50MAX MONITOR LID -400 100% -400Cellular -500 40% -200

OUT-DOOR CELLULAR CONNECT Scenario A Taipei Q-Station Real


第二次測試平均 -1266.342114 3 min 41 sec

第三次測試平均 -1302.819672 3 min 18 sec

實際平均 -1275.273314 　

OUT-DOOR CELLULAR CONNECT Scenario A Taipei Q-Station Guess reason


• CPU average usage increase.• More GPS consume.• RF IC need more compute to anti-interference??

Scenario B steps1. 打開 FB2. 點選已經 PO 在自己 FB 塗鴉牆上的 1 分鐘影片，音量中等，接耳機3. 打卡並上傳 3 張照片。4. 分享 3 張照片給一位好友。5. 聊天 10 句， 4 則訊息。6. 結束• 預計 5 分鐘完成

IN-DOOR WIFI CONNECT Scenario B HOME

IN-DOOR WIFI CONNECT Scenario B• FB won’t using in physic GPS to locate real location.(guess due to WIFI

location provide enough precision).• Min lid, disable auto brightness.

• Simulate entertainment using FB at home.

IN-DOOR WIFI CONNECT Scenario B Estimate HOME


執行時間佔總時間比例

平均值行時間耗電量

CPU FULL LOAD -1000 0% 0CPU 3C LOAD -800 10% -80CPU 2C LOAD -600 60% -360CPU 1C LOAD -400 30% -120CPU TOTAL AVG 　　 -560

比例WIFI ACTIVE 包含 MIN MONITOR -500 50% -250



IN-DOOR WIFI CONNECT Scenario B Real HOME


第二次測試平均 -737.5024394 3 min 15 sec

第三次測試平均 -754.0005818 2 min 44 sec

實際平均 -755.2194717

IN-DOOR WIFI CONNECT Scenario B HOMEGuess reason


• More accurate estimate CPU usage.

OUT-DOOR CELLULAR CONNECT Scenario B NCKU

OUT-DOOR CELLULAR CONNECT Scenario B NCKU• FB will seen not using GPS in 打卡 & Message sending.• Using cellular network with variable signal strength condition.• 58%, -98dBm @ NCKU Success middle area.


• Simulate entertainment using FB at outdoor.

OUT-DOOR CELLULAR CONNECT Scenario B NCKU Estimate





CPU FULL LOAD -1000 0% 0CPU 3C LOAD -800 10% -80CPU 2C LOAD -600 30% -180CPU 1C LOAD -400 60% -240CPU TOTAL AVG 　 100% -500　　　　　　　　MAX MONITOR LID -400 100% -400

Cellular -500 40% -200

OUT-DOOR CELLULAR CONNECT Scenario B NCKU Real



第三次測試平均 -1155.352031 4 min 52 sec

實際平均 -1143.368324 　

OUT-DOOR CELLULAR CONNECT Scenario B NCKU Guess reason


• More accurate estimate CPU usage.• Guess there have hardware video decode.

OUT-DOOR CELLULAR CONNECT Scenario B Taipei Q-Station

OUT-DOOR CELLULAR CONNECT Scenario B Taipei Q-Station• FB will using GPS in 打卡 & Message sending.• Using cellular network with variable signal strength condition.• 58%, -98dBm @ NCKU Success middle area.


• Simulate entertainment using FB at general public area.

OUT-DOOR CELLULAR CONNECT Scenario B Taipei Q-Station Estimate





CPU FULL LOAD -1000 0% 0CPU 3C LOAD -800 10% -80CPU 2C LOAD -600 30% -180CPU 1C LOAD -400 60% -240CPU TOTAL AVG 　 100% -500　　　　　　　　MAX MONITOR LID -400 100% -400

Cellular -500 40% -200

OUT-DOOR CELLULAR CONNECT Scenario B Taipei Q-Station Real



第三次測試平均 -1289.8889 3 min 36 sec

實際平均 -1243.946138 　

OUT-DOOR CELLULAR CONNECT Scenario B Taipei Q-Station Guess reason


• CPU average usage increase.• RF IC need more compute to anti-interference??

Scenario C steps1. 打開 FB2. 點選已經 PO 在自己 FB 塗鴉牆上的 1 分鐘 20 秒影片，音量中等，接耳機，分別切換測試一般畫質 /HD 畫質。3. 結束• 預計 2 分鐘完成

OUT-DOOR CELLULAR CONNECT Scenario C NCKU

OUT-DOOR CELLULAR CONNECT Scenario C NCKU• See different consumption in different video quality.(Real Data only)• Low Quality:• AVG Current(mA): -870.4692 • CPU Usage: 49.84375%

• High Quality:• AVG Current(mA): -943.8936944• CPU Usage: 52.40625%

• Cause by more network traffic or video decode?

SCNARIO A INDOOR

SCNARIO A NCKU

SCNARIO A TAIPEI

SCNARIO B INDOOR

SCNARIO B NCKU

SCNARIO B TAIPEI

SCNARIO C NCKU LQ

SCNARIO C NCKU HQ

-1400

-1200

-1000

-800

-600

-400

-200

0

-702.497682005495

-1171.91111530336-1275.27331435679

-755.219471717172

-1143.36832394558-1243.94613809524

-870.4692-943.8936944

-890

-1130-1180

-810

-1100-1100

Real comsuption

Real Estimate

SCNARIO A INDOOR

SCNARIO A NCKU

SCNARIO A TAIPEI

SCNARIO B INDOOR

SCNARIO B NCKU

SCNARIO B TAIPEI

-15%

-10%

-5%

0%

5%

10%

15%

20%

25%

30%

27%

-4%

-7%

7%

-4% -12%

Error Rate

Adopt a measure when low battery capacity • Disable non-system service, stay only system necessary service.• Disable GPU 3D rendering in Desktop manager.• Disable animation transition effect.• Disable GPS, Mobile Data, WIFI, BT, NFC, but keep cellular on.• Disable G-Sensor(for Monitor rotator)• Disable Light-Sensor(for Auto brightness adjust)• Mini Monitor lid.• Limit CPU Speed, limit active core.

Graceful implement battery saver method1. 到達臨界前 ( 例如 25%)2. 開始記錄開過的前景 ACTIVITY3. 到達 20% 時，再比對一下誰的執行時間最長4. 判斷執行 App 名稱 -> 預先已經有 DB （節省其他能源消耗）5. DB 告訴系統節電措施，目標 APP 最少需要什麼硬體（例如地圖要 GPS, 網路）6. 關閉目標 APP 需要硬體以外的硬體。

從電量 25% 開始，紀錄每個 APP 使用時間 T, 以及每個硬體的消耗電量 E(ex. CPU 使用率 )

決定每個硬體的最高電量使用 Esave參考某 APP 過去五分鐘加權 E'(app) = (5*E1+4*E2+3*E3+2*E4+E5) / 15 加權 T'(app) = (5*T1+4*T2+3*T3+2*T4+T5) / 15 Tsum = sum(T')得出某 APP 的使用比重 X(app) = T'(app)/Tsum又 C*( sum(E'(app)*X(app) )) = Esave(CPU)計算常數 C最後限制某 APP 的 CPU 最高電量使用為 E'(app)*X(app)*C

About this slide• Author: Nathaniel Chen• Email: [email protected]

• Last update time:2015/04/23 0043 v1.1

mailto:[email protected]

app power consumption hw5

Technology