My phone has v2.19.0 of the official Lucid app. I was running some battery usage test on my phone overnight last night for my Garmin watch app (and its companion Android app), and I (and Claude) noticed that the official app used something like 50x more battery than my app overnight, even though I had my app polling extra frequently while the car was charging over night.
I had Claude take a look at the overnight batterystats (via ADB) of the official Lucid app and this is what it found. This was since the phone was charged to 100% then I unplugged it and went to bed at 1am. The car was charging between ~1am and 8:30am, then the battery stats were checked at 9:11am.
This is what Claude found from the the official app:
Overnight (8 h 16 min on battery) it used 10.9 mAh, which is 50 times Orbit's (my app) 0.217 mAh.
I'm fairly certain my phone wasn't in BLE range of the car, but perhaps the official app also kicks up the scanning frequency (of the BLE key link) when the car is charging like I have my app doing?
My app doesn't do any Bluetooth scanning, so I suspect that's a large part of why I didn't use much battery overnight, even with my app querying the Lucid API every 30s and pushing the the watch any time it saw a change in data (approx every minute while charging).
Anyway, I just thought that would be some interesting information for those who car about the geeky side of things.
I had Claude take a look at the overnight batterystats (via ADB) of the official Lucid app and this is what it found. This was since the phone was charged to 100% then I unplugged it and went to bed at 1am. The car was charging between ~1am and 8:30am, then the battery stats were checked at 9:11am.
This is what Claude found from the the official app:
Overnight (8 h 16 min on battery) it used 10.9 mAh, which is 50 times Orbit's (my app) 0.217 mAh.
- Bluetooth scanning: it scanned continuously for the whole 8 h 16 min and got 44,120 scan results. Android marks it as an unoptimized scan running for 8 h 9 min. This is what keeps the phone awake and accounts for most of the 10.9 mAh. It's the app's digital-key and beacon feature.
- ScanJob (the beacon library): it ran 677 times, held a partial wake lock for 53 min, and ran 1 h 57 min in total.
- Network: it sent 45 MB and received 9 MB over Wi-Fi, which is 92,000 packets sent. It also runs an analytics flush job about 360 times.
- Wakeups: 315 alarm wakeups and 104 Wi-Fi wakeups.
I'm fairly certain my phone wasn't in BLE range of the car, but perhaps the official app also kicks up the scanning frequency (of the BLE key link) when the car is charging like I have my app doing?
My app doesn't do any Bluetooth scanning, so I suspect that's a large part of why I didn't use much battery overnight, even with my app querying the Lucid API every 30s and pushing the the watch any time it saw a change in data (approx every minute while charging).
Anyway, I just thought that would be some interesting information for those who car about the geeky side of things.