IssueTracker

[CL6-V] [GMS_15_202411][1/20] The sim card has a static complex standby time of 13.49 hours, consumes 14% of power, and consumes an average of 51.90MA, exceeding the standard 30MA
Name:
Chuanxing.Sun
Issue Description：
Nearby share calling BLE when the screen is off causes the power consumption of the mobile phone to exceed the standard
Android Platform：
Android 15
Google Play Services:
Project_15_202411__15_202411
Device:
CL6
Build Fingerprint:
TECNO/CL6-OP/TECNO-CL6:15/AP3A.240905.015.A2/001004:user/release-keys
Can pixel reproduce?
Unknown
Deadline:
2025/3/15
Involved app:
Nearby share
STEPS TO REPRODUCE: (please be specific)
On the basis of installing the overseas TOP30, install the historical anomaly APP (Hello bike, cleaner master, master booster, Max Booster, Peace Elite, Apopo, Apopo, Live Wallpaper, Microsoft Teams, water sort, roblox, com.netqin.ps, Purple File Manage, Snap Chat, Vskit, etc.), Then install other apps in the top 100 of the Google Store, update all apps before testing, and turn on all permissions and notifications of apps
B)Operation step：
1. Open the DNS communication log:
adb shell settings put global tds_dns_record_enable 1
2. Connect to a network, WiFi or data network
3. Set face unlock, fingerprint unlock, turn on GPS/BT/NFC, enable AOD mode, and enable the Dynamic Island function
4. Run all the "Overseas TOP30" applications once
5. Run the following standby app and keep it alive
Facebook, WeChat, WhatsApp, Candycrush, Facebook message, TikTok, YouTube, PUBG, Amazon, UC Browser, Camera, Album, File Management (you need to log in to your account, all keepalive apps are locked)
6. Go to DebugLogger and clean up all logs, only MobileLog and NetworkLog are enabled
7. After 6 hours of random operation of monkey, stop monkey to ensure that there is no music playing in the background.
8. Reset the bugreport log
adb shell dumpsys batterystats --reset
adb shell dumpsys batterystats --enable full-wake-history
9. Turn it on, put it in the foreground after logging in, press the power button to turn off the screen and start shaking on the tool to standby, record the current start time and battery level
10. After the standby ends, export all logs with the logExportTool_V1.1.7 or later guide log tool (standby time 12 hours)
REPRO FREQUENCY:
1/20 times
OBSERVED RESULTS:
must be google error
EXPECTED RESULTS:
No error
REPRODUCIBLE on Pixel/Nexus Devices: (Yes or No)
Unknown
ADDITIONAL INFORMATION:
Mobile logs:
02-18 22:15:04.096020 3954 4454 I NearbyMediums: Started accepting Bluetooth Classic connections for NearbySharing.
02-18 22:15:04.146671 3954 4454 I NearbyMediums: Started BLE Legacy advertising. Regular Header Advertised : false, Fast Advertised : true, AdvertisingSettings : BleAdvertisingSetting{powerLevel= LOW_POWER, isConnectable= false, isPrivateGatt= true}, isAcceptingConnection : false
02-18 22:15:04.147238 3954 4454 I NearbyMediums: Successfully started BLE advertising of size 23 for service NearbySharing, deviceToken : [ 0xa0 0xf5 ].
02-18 22:15:04.152968 3954 4454 I NearbySharing: [broadcast provider] advertising started.

Kernel logs:
02-18 23:05:30.599 <6>[32612.137276][T704926] [MTK-BT]bthost_debug_print: [bt host info] [0][BR_INQURY_SCAN : 0x00120800] [1][BR_SCAN_MODE : 0x00000002] [2][BLE_SCAN : 0x08c000e0] [3][BLE_ADV : 0x00010640] [4][BR_INQURY : 0x00000000] [5][BR_PAGE : 0x00000000] [6-16] not set
02-18 23:05:32.922 <4>[32614.460325][    C0] PM: pm_system_irq_wakeup: 139 triggered BTIF_WAKEUP_IRQ

Conclusion: Nearby share calling BLE when the screen is off