文档建议反馈控制台
首页
学习
活动
专区
圈层
工具
MCP广场
文章/答案/技术大牛
发布
社区首页 >问答首页 >电池历史学家找不到终端时间

问电池历史学家找不到终端时间
EN

Stack Overflow用户
提问于 2015-12-28 04:36:54
回答 3查看 1.8K关注 0票数 3

我试图使用来自GitHub的电池历史学家Python来分析电池的使用情况，但是每次我使用脚本时生成的html显示“找不到结束时间”。

我遵循这里的步骤。

下面是生成的示例batterystats.txt文件：

代码语言：javascript
复制
Battery History:
          -2m43s770ms 100 44020302 status=not-charging health=good plug=none temp=270 volt=4339 +wifi +wifi_running +wake_lock brightness=medium phone_state=off
          -2m43s151ms 100 44020302
          -2m38s500ms 100 04020302 -wake_lock
          -2m20s496ms 100 44020302 +wake_lock
          -2m17s471ms 100 04020302 -wake_lock
          -2m13s741ms 100 04020302 temp=280
          -1m59s447ms 100 44020302 +wake_lock
          -1m56s423ms 100 04020302 -wake_lock
            -43s740ms 100 04020302 volt=4317
            -21s432ms 100 040a0302 status=full plug=usb volt=4312 +plugged

Per-PID Stats:
  PID 140 wake time: +1s55ms
  PID 601 wake time: +1s236ms
  PID 140 wake time: +13s381ms
  PID 601 wake time: +29ms
  PID 812 wake time: +555ms
  PID 939 wake time: +18ms
  PID 1241 wake time: +51ms
  PID 601 wake time: +1ms
  PID 1294 wake time: +3ms
  PID 601 wake time: +32ms
  PID 601 wake time: +7ms
  PID 1689 wake time: +103ms

Statistics since last charge:
  System starts: 0, currently on battery: false
  Time on battery: 2m 22s 369ms (0.0%) realtime, 2m 22s 369ms (0.0%) uptime
  Total run time: 21d 4h 47m 25s 154ms realtime, 3d 2h 25m 30s 738ms uptime, 
  Screen on: 0ms (0.0%), Input events: 0, Active phone call: 0ms (0.0%)
  Screen brightnesses: No activity
  Mobile total received: 0B, Total sent: 0B
  Wi-Fi total received: 249.09KB, Total sent: 18.02KB
  Total full wakelock time: 2m 22s 191ms , Total partial wakelock time: 9s 697ms 
  Signal levels: No activity
  Signal scanning time: 0ms 
  Radio types: none 2m 22s 369ms (100.0%) 0x
  Radio data uptime when unplugged: 0 ms
  Wifi on: 2m 22s 369ms (100.0%), Wifi running: 2m 22s 369ms (100.0%), Bluetooth on: 0ms (0.0%)

  Device battery use since last full charge
    Amount discharged (lower bound): 0
    Amount discharged (upper bound): 0
    Amount discharged while screen on: 0
    Amount discharged while screen off: 0

  All partial wake locks:
  Wake lock 1013 AudioMix: 9s 52ms (4 times) realtime
  Wake lock u0a8 UlrDispSvcFastWL: 166ms (2 times) realtime
  Wake lock 1000 AlarmManager: 87ms (2 times) realtime
  Wake lock u0a8 GCoreFlp: 80ms (3 times) realtime
  Wake lock 1000 NetworkStats: 78ms (1 times) realtime
  Wake lock 1000 ActivityManager-Launch: 78ms (1 times) realtime
  Wake lock u0a8 Event Log Service: 75ms (1 times) realtime
  Wake lock u0a24 AlarmManager: 32ms (1 times) realtime
  Wake lock u0a8 AlarmManager: 23ms (2 times) realtime
  Wake lock u0a43 AlarmManager: 7ms (1 times) realtime
  Wake lock u0a8 Event Log Handoff: 7ms (1 times) realtime
  Wake lock u0a8 GCM_CONN: 5ms (1 times) realtime
  Wake lock u0a8 GCM_HB_ALARM: 4ms (1 times) realtime
  Wake lock u0a23 PUSH_SERVICE_WAKE_LOCK: 3ms (1 times) realtime
  Wake lock u0a23 AlarmManager: 1ms (1 times) realtime
  Wake lock u0a8 Wakeful StateMachine: GeofencerStateMachine: 1ms (1 times) realtime

  0:
    Wi-Fi network: 632B received, 1.59KB sent
    Proc /init:
      CPU: 20ms usr + 80ms krn ; 0ms fg
    Proc ksoftirqd/0:
      CPU: 10ms usr + 0ms krn ; 0ms fg
    Proc mtk charger_hv_:
      CPU: 0ms usr + 20ms krn ; 0ms fg
    Proc vold:
      CPU: 0ms usr + 10ms krn ; 0ms fg
    Proc jbd2/mmcblk0p7-:
      CPU: 0ms usr + 20ms krn ; 0ms fg
    Proc pmic_thread_kth:
      CPU: 0ms usr + 450ms krn ; 0ms fg
    Proc kthreadd:
      CPU: 0ms usr + 10ms krn ; 0ms fg
    Proc btif_rxd:
      CPU: 10ms usr + 0ms krn ; 0ms fg
    Proc netd:
      CPU: 10ms usr + 10ms krn ; 0ms fg
    Proc mmcqd/0:
      CPU: 0ms usr + 50ms krn ; 0ms fg
    Proc kworker/u:0:
      CPU: 0ms usr + 270ms krn ; 0ms fg
    Proc kworker/u:2:
      CPU: 0ms usr + 120ms krn ; 0ms fg
    Proc kworker/0:2:
      CPU: 0ms usr + 500ms krn ; 0ms fg
    Proc zygote:
      CPU: 20ms usr + 30ms krn ; 0ms fg
    Proc flush-179:0:
      CPU: 10ms usr + 0ms krn ; 0ms fg
    Proc tx_thread:
      CPU: 0ms usr + 100ms krn ; 0ms fg
    Proc disp_clean_up_k:
      CPU: 0ms usr + 20ms krn ; 0ms fg
    Proc healthd:
      CPU: 0ms usr + 100ms krn ; 0ms fg
    Proc ueventd:
      CPU: 0ms usr + 10ms krn ; 0ms fg
    Proc bat_thread_kthr:
      CPU: 0ms usr + 520ms krn ; 0ms fg
    Proc disp_config_upd:
      CPU: 0ms usr + 440ms krn ; 0ms fg
    Proc ion_mm_heap:
      CPU: 0ms usr + 20ms krn ; 0ms fg
    Proc disp_ovl_kthrea:
      CPU: 0ms usr + 110ms krn ; 0ms fg
  1000:
    User activity: 6 other, 1 button, 1 touch
    Wake lock NetworkStats: 78ms partial (1 times) realtime
    Wake lock ActivityManager-Launch: 78ms partial (1 times) realtime
    Wake lock AlarmManager: 87ms partial (2 times) realtime
    TOTAL wake: 243ms partial realtime
    Sensor 0: 2m 22s 369ms realtime (0 times)
    Vibrator: 100ms realtime (1 times)
    Foreground activities: 129ms realtime (1 times)
    Proc com.mediatek.schpwronoff:
      CPU: 0ms usr + 10ms krn ; 0ms fg
    Proc surfaceflinger:
      CPU: 950ms usr + 1s 30ms krn ; 0ms fg
    Proc com.android.settings:
      CPU: 0ms usr + 0ms krn ; 730ms fg
    Proc system_server:
      CPU: 2s 680ms usr + 2s 230ms krn ; 0ms fg
    Proc aal:
      CPU: 60ms usr + 180ms krn ; 0ms fg
    Proc servicemanager:
      CPU: 0ms usr + 10ms krn ; 0ms fg
  1001:
    Proc com.android.phone:
      CPU: 50ms usr + 20ms krn ; 0ms fg
  1010:
    Proc wpa_supplicant:
      CPU: 10ms usr + 30ms krn ; 0ms fg
  1013:
    Wake lock AudioMix: 9s 52ms partial (4 times) realtime
    Proc mediaserver:
      CPU: 20ms usr + 30ms krn ; 0ms fg
  1023:
    Proc sdcard:
      CPU: 0ms usr + 20ms krn ; 0ms fg
  2000:
    Proc adbd:
      CPU: 110ms usr + 380ms krn ; 0ms fg
  9997:
    Proc em_svr:
      CPU: 0ms usr + 40ms krn ; 0ms fg
  u0a5:
    Proc android.process.media:
      CPU: 60ms usr + 0ms krn ; 0ms fg
    Apk com.android.providers.media:
      Service com.android.providers.media.MtpService:
        Created for: 0ms uptime
        Starts: 1, launches: 1
  u0a8:
    Wi-Fi network: 5.35KB received, 1.92KB sent
    Wake lock Wakeful StateMachine: GeofencerStateMachine: 1ms partial (1 times) realtime
    Wake lock GCoreFlp: 80ms partial (3 times) realtime
    Wake lock UlrDispSvcFastWL: 166ms partial (2 times) realtime
    Wake lock GCM_HB_ALARM: 4ms partial (1 times) realtime
    Wake lock Event Log Service: 75ms partial (1 times) realtime
    Wake lock GCM_CONN: 5ms partial (1 times) realtime
    Wake lock Event Log Handoff: 7ms partial (1 times) realtime
    Wake lock AlarmManager: 23ms partial (2 times) realtime
    TOTAL wake: 361ms partial realtime
    Proc com.google.android.gms:
      CPU: 100ms usr + 40ms krn ; 0ms fg
    Proc com.google.process.gapps:
      CPU: 180ms usr + 70ms krn ; 0ms fg
    Proc com.google.android.gms.persistent:
      CPU: 1s 130ms usr + 300ms krn ; 0ms fg
    Apk com.google.android.gms:
      2 wakeup alarms
      Service com.google.android.gms.config.ConfigService:
        Created for: 0ms uptime
        Starts: 0, launches: 1
      Service com.google.android.gms.checkin.EventLogService:
        Created for: 85ms uptime
        Starts: 1, launches: 1
      Service com.google.android.gms.gcm.http.GoogleHttpService:
        Created for: 0ms uptime
        Starts: 0, launches: 1
      Service com.google.android.location.reporting.service.DispatchingService:
        Created for: 268ms uptime
        Starts: 1, launches: 1
      Service com.google.android.gms.usagereporting.service.UsageReportingService:
        Created for: 0ms uptime
        Starts: 0, launches: 1
  u0a13:
    Proc com.android.systemui:
      CPU: 810ms usr + 300ms krn ; 0ms fg
  u0a18:
    Proc com.lenovo.safecenter.hd:
      CPU: 360ms usr + 120ms krn ; 0ms fg
  u0a19:
    Proc com.lenovo.lps.cloud.sync.row:
      CPU: 0ms usr + 0ms krn ; 0ms fg
      1 proc starts
  u0a20:
    Proc com.lenovo.lewea:
      CPU: 40ms usr + 10ms krn ; 0ms fg
    Apk com.lenovo.lewea:
      Service com.lenovo.weather.service.UpdateAppWidgetService:
        Created for: 84ms uptime
        Starts: 2, launches: 2
  u0a23:
    Wake lock AlarmManager: 1ms partial (1 times) realtime
    Wake lock PUSH_SERVICE_WAKE_LOCK: 3ms partial (1 times) realtime
    TOTAL wake: 4ms partial realtime
    Proc com.lenovo.lsf.device:
      CPU: 30ms usr + 0ms krn ; 0ms fg
  u0a24:
    Wake lock AlarmManager: 32ms partial (1 times) realtime
    Proc com.lenovo.ue.service:
      CPU: 40ms usr + 10ms krn ; 0ms fg
  u0a42:
    (nothing executed)
  u0a43:
    Wake lock AlarmManager: 7ms partial (1 times) realtime
  u0a58:
    Proc com.google.android.inputmethod.latin:
      CPU: 20ms usr + 0ms krn ; 0ms fg
  u0a65:
    (nothing executed)
  u0a74:
    Proc com.google.android.apps.plus:
      CPU: 50ms usr + 30ms krn ; 0ms fg
    Apk com.google.android.apps.plus:
      (nothing executed)
  u0a114:
    Wi-Fi network: 243.13KB received, 14.51KB sent
    Wake lock WindowManager: 2m 22s 191ms full (1 times) realtime
    Foreground activities: 2m 22s 208ms realtime (1 times)
    Proc com.devstring.imageframe:
      CPU: 6s 300ms usr + 810ms krn ; 0ms fg

Statistics since last unplugged:
  Time on battery: 2m 22s 369ms (86.9%) realtime, 2m 22s 369ms (86.9%) uptime
  Total run time: 2m 43s 811ms realtime, 2m 43s 811ms uptime, 
  Screen on: 0ms (0.0%), Input events: 0, Active phone call: 0ms (0.0%)
  Screen brightnesses: No activity
  Mobile total received: 0B, Total sent: 0B
  Wi-Fi total received: 249.09KB, Total sent: 18.02KB
  Total full wakelock time: 2m 22s 191ms , Total partial wakelock time: 9s 697ms 
  Signal levels: No activity
  Signal scanning time: 0ms 
  Radio types: none 2m 22s 369ms (100.0%) 0x
  Radio data uptime when unplugged: 0 ms
  Wifi on: 2m 22s 369ms (100.0%), Wifi running: 2m 22s 369ms (100.0%), Bluetooth on: 0ms (0.0%)

  Device is currently plugged into power
    Last discharge cycle start level: 100
    Last discharge cycle end level: 100
    Amount discharged while screen on: 0
    Amount discharged while screen off: 0

  All partial wake locks:
  Wake lock 1013 AudioMix: 9s 52ms (4 times) realtime
  Wake lock u0a8 UlrDispSvcFastWL: 166ms (2 times) realtime
  Wake lock 1000 AlarmManager: 87ms (2 times) realtime
  Wake lock u0a8 GCoreFlp: 80ms (3 times) realtime
  Wake lock 1000 NetworkStats: 78ms (1 times) realtime
  Wake lock 1000 ActivityManager-Launch: 78ms (1 times) realtime
  Wake lock u0a8 Event Log Service: 75ms (1 times) realtime
  Wake lock u0a24 AlarmManager: 32ms (1 times) realtime
  Wake lock u0a8 AlarmManager: 23ms (2 times) realtime
  Wake lock u0a43 AlarmManager: 7ms (1 times) realtime
  Wake lock u0a8 Event Log Handoff: 7ms (1 times) realtime
  Wake lock u0a8 GCM_CONN: 5ms (1 times) realtime
  Wake lock u0a8 GCM_HB_ALARM: 4ms (1 times) realtime
  Wake lock u0a23 PUSH_SERVICE_WAKE_LOCK: 3ms (1 times) realtime
  Wake lock u0a23 AlarmManager: 1ms (1 times) realtime
  Wake lock u0a8 Wakeful StateMachine: GeofencerStateMachine: 1ms (1 times) realtime

  0:
    Wi-Fi network: 632B received, 1.59KB sent
    Proc /init:
      CPU: 20ms usr + 80ms krn ; 0ms fg
    Proc ksoftirqd/0:
      CPU: 10ms usr + 0ms krn ; 0ms fg
    Proc mtk charger_hv_:
      CPU: 0ms usr + 20ms krn ; 0ms fg
    Proc vold:
      CPU: 0ms usr + 10ms krn ; 0ms fg
    Proc jbd2/mmcblk0p7-:
      CPU: 0ms usr + 20ms krn ; 0ms fg
    Proc pmic_thread_kth:
      CPU: 0ms usr + 450ms krn ; 0ms fg
    Proc kthreadd:
      CPU: 0ms usr + 10ms krn ; 0ms fg
    Proc btif_rxd:
      CPU: 10ms usr + 0ms krn ; 0ms fg
    Proc netd:
      CPU: 10ms usr + 10ms krn ; 0ms fg
    Proc mmcqd/0:
      CPU: 0ms usr + 50ms krn ; 0ms fg
    Proc kworker/u:0:
      CPU: 0ms usr + 270ms krn ; 0ms fg
    Proc kworker/u:2:
      CPU: 0ms usr + 120ms krn ; 0ms fg
    Proc kworker/0:2:
      CPU: 0ms usr + 500ms krn ; 0ms fg
    Proc zygote:
      CPU: 20ms usr + 30ms krn ; 0ms fg
    Proc flush-179:0:
      CPU: 10ms usr + 0ms krn ; 0ms fg
    Proc tx_thread:
      CPU: 0ms usr + 100ms krn ; 0ms fg
    Proc disp_clean_up_k:
      CPU: 0ms usr + 20ms krn ; 0ms fg
    Proc healthd:
      CPU: 0ms usr + 100ms krn ; 0ms fg
    Proc ueventd:
      CPU: 0ms usr + 10ms krn ; 0ms fg
    Proc bat_thread_kthr:
      CPU: 0ms usr + 520ms krn ; 0ms fg
    Proc disp_config_upd:
      CPU: 0ms usr + 440ms krn ; 0ms fg
    Proc ion_mm_heap:
      CPU: 0ms usr + 20ms krn ; 0ms fg
    Proc disp_ovl_kthrea:
      CPU: 0ms usr + 110ms krn ; 0ms fg
  1000:
    User activity: 6 other, 1 button, 1 touch
    Wake lock NetworkStats: 78ms partial (1 times) realtime
    Wake lock ActivityManager-Launch: 78ms partial (1 times) realtime
    Wake lock AlarmManager: 87ms partial (2 times) realtime
    TOTAL wake: 243ms partial realtime
    Sensor 0: 2m 22s 369ms realtime (0 times)
    Vibrator: 100ms realtime (1 times)
    Foreground activities: 129ms realtime (1 times)
    Proc com.mediatek.schpwronoff:
      CPU: 0ms usr + 10ms krn ; 0ms fg
    Proc surfaceflinger:
      CPU: 950ms usr + 1s 30ms krn ; 0ms fg
    Proc com.android.settings:
      CPU: 0ms usr + 0ms krn ; 730ms fg
    Proc system_server:
      CPU: 2s 680ms usr + 2s 230ms krn ; 0ms fg
    Proc aal:
      CPU: 60ms usr + 180ms krn ; 0ms fg
    Proc servicemanager:
      CPU: 0ms usr + 10ms krn ; 0ms fg
  1001:
    Proc com.android.phone:
      CPU: 50ms usr + 20ms krn ; 0ms fg
  1010:
    Proc wpa_supplicant:
      CPU: 10ms usr + 30ms krn ; 0ms fg
  1013:
    Wake lock AudioMix: 9s 52ms partial (4 times) realtime
    Proc mediaserver:
      CPU: 20ms usr + 30ms krn ; 0ms fg
  1023:
    Proc sdcard:
      CPU: 0ms usr + 20ms krn ; 0ms fg
  2000:
    Proc adbd:
      CPU: 110ms usr + 380ms krn ; 0ms fg
  9997:
    Proc em_svr:
      CPU: 0ms usr + 40ms krn ; 0ms fg
  u0a5:
    Proc android.process.media:
      CPU: 60ms usr + 0ms krn ; 0ms fg
    Apk com.android.providers.media:
      Service com.android.providers.media.MtpService:
        Created for: 0ms uptime
        Starts: 1, launches: 1
  u0a8:
    Wi-Fi network: 5.35KB received, 1.92KB sent
    Wake lock Wakeful StateMachine: GeofencerStateMachine: 1ms partial (1 times) realtime
    Wake lock GCoreFlp: 80ms partial (3 times) realtime
    Wake lock UlrDispSvcFastWL: 166ms partial (2 times) realtime
    Wake lock GCM_HB_ALARM: 4ms partial (1 times) realtime
    Wake lock Event Log Service: 75ms partial (1 times) realtime
    Wake lock GCM_CONN: 5ms partial (1 times) realtime
    Wake lock Event Log Handoff: 7ms partial (1 times) realtime
    Wake lock AlarmManager: 23ms partial (2 times) realtime
    TOTAL wake: 361ms partial realtime
    Proc com.google.android.gms:
      CPU: 100ms usr + 40ms krn ; 0ms fg
    Proc com.google.process.gapps:
      CPU: 180ms usr + 70ms krn ; 0ms fg
    Proc com.google.android.gms.persistent:
      CPU: 1s 130ms usr + 300ms krn ; 0ms fg
    Apk com.google.android.gms:
      2 wakeup alarms
      Service com.google.android.gms.config.ConfigService:
        Created for: 0ms uptime
        Starts: 0, launches: 1
      Service com.google.android.gms.checkin.EventLogService:
        Created for: 85ms uptime
        Starts: 1, launches: 1
      Service com.google.android.gms.gcm.http.GoogleHttpService:
        Created for: 0ms uptime
        Starts: 0, launches: 1
      Service com.google.android.location.reporting.service.DispatchingService:
        Created for: 268ms uptime
        Starts: 1, launches: 1
      Service com.google.android.gms.usagereporting.service.UsageReportingService:
        Created for: 0ms uptime
        Starts: 0, launches: 1
  u0a13:
    Proc com.android.systemui:
      CPU: 810ms usr + 300ms krn ; 0ms fg
  u0a18:
    Proc com.lenovo.safecenter.hd:
      CPU: 360ms usr + 120ms krn ; 0ms fg
  u0a19:
    Proc com.lenovo.lps.cloud.sync.row:
      CPU: 0ms usr + 0ms krn ; 0ms fg
      1 proc starts
  u0a20:
    Proc com.lenovo.lewea:
      CPU: 40ms usr + 10ms krn ; 0ms fg
    Apk com.lenovo.lewea:
      Service com.lenovo.weather.service.UpdateAppWidgetService:
        Created for: 84ms uptime
        Starts: 2, launches: 2
  u0a23:
    Wake lock AlarmManager: 1ms partial (1 times) realtime
    Wake lock PUSH_SERVICE_WAKE_LOCK: 3ms partial (1 times) realtime
    TOTAL wake: 4ms partial realtime
    Proc com.lenovo.lsf.device:
      CPU: 30ms usr + 0ms krn ; 0ms fg
  u0a24:
    Wake lock AlarmManager: 32ms partial (1 times) realtime
    Proc com.lenovo.ue.service:
      CPU: 40ms usr + 10ms krn ; 0ms fg
  u0a42:
    (nothing executed)
  u0a43:
    Wake lock AlarmManager: 7ms partial (1 times) realtime
  u0a58:
    Proc com.google.android.inputmethod.latin:
      CPU: 20ms usr + 0ms krn ; 0ms fg
  u0a65:
    (nothing executed)
  u0a74:
    Proc com.google.android.apps.plus:
      CPU: 50ms usr + 30ms krn ; 0ms fg
    Apk com.google.android.apps.plus:
      (nothing executed)
  u0a114:
    Wi-Fi network: 243.13KB received, 14.51KB sent
    Wake lock WindowManager: 2m 22s 191ms full (1 times) realtime
    Foreground activities: 2m 22s 208ms realtime (1 times)
    Proc com.devstring.imageframe:
      CPU: 6s 300ms usr + 810ms krn ; 0ms fg

命令：

代码语言：javascript
复制
 adb shell dumpsys batterystats > batterystats.txt
 python historian.py batterystats.txt > batterystats.html

batterystats.html显示找不到结束时间

我提到过在使用hisorian.py时显示“无法找到结束时间”

EDIT1

当我用不同的设备测试的时候。不会产生这样的错误。但是每次这个设备电池统计数据都没有结束时间错误。

编辑2不同版本的安卓有不同的虚拟心理格式，电池历史学家似乎与较新的版本兼容。生成图表I注释行646至649，即

代码语言：javascript
复制
#if not self._end_time:
      #print "cannot find end time"
      #sys.exit(1)

尽管这是一次黑客攻击，我的设备是Android4.4，它的电池假人不提供应用程序的电池使用，但Android5.2设备是这样做的。

android
python
adb
battery
EN

Stack Overflow用户

发布于 2016-12-21 12:37:13

虽然battery-historian.py的最新版本是使用Android，但不同版本的5.0+支持不同格式的电池统计日志。当前的historian.py在5.0+上运行良好，在下面的版本中，它会崩溃或者不会显示图表(这是在6.0上测试的)。

如果您知道python，以及如何读取电池统计文件，您可以根据您的android风格编辑代码，但这是一项耗时的任务。您也可以用另一种语言编写自己的解析器，但这就像重新发明轮子一样。

我没有尝试的一件事是克隆一个旧版本的battery-historian回购，也许如果有可用的话，它可能会适用于旧版本的安卓，这取决于回购有多老。(未测试)

更新：

从提交历史的电池史学家回购来看，我可以看到早在2014年6月就有提交，而Android ( 5.0 )开发者预览版是在2014年8月发布的，所以比Android5.0更老的版本很有可能在<5.0的设备上工作。

票数 0
EN
查看全部 3 条回答
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：

https://stackoverflow.com/questions/34487749

复制
相关文章

相似问题

领券

腾讯云开发者

扫码关注腾讯云开发者

扫码关注腾讯云开发者

领取腾讯云代金券

热门产品

热门推荐

更多推荐

Copyright © 2013 - 2026 Tencent Cloud. All Rights Reserved. 腾讯云 版权所有 

深圳市腾讯计算机系统有限公司 ICP备案/许可证号：粤B2-20090059 粤公网安备44030502008569号

腾讯云计算（北京）有限责任公司 京ICP证150476号 |  京ICP备11018762号

问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档