IN CAR: Battery levels not shared via bluetooth for in car experience

[Dave Morley]

STEPS:
Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance)

1. Connect the DUT to the car
2. On the display panel the battery always shows full

EXPECTED:
I expect to see the actual level of the battery on the device

ACTUAL:
The display always shows the battery at 100% I assume the default if no info is available.

VERSIONS:
current build number: 71
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-07-28 18:01:08
version version: 71
version ubuntu: 20150728
version device: 20150709-8965e37
version custom: 20150716-819-8-42

MODIFICATIONS:
Installation of silo19 for in car bt fix

[Simon Fels (morphis)]

The cause for this is that with the deprecation of HAL we also dropped battery query support from BlueZ and never brought it back. We need to interface BlueZ correct with upowerd so we can send out the correct battery level.

[Simon Fels (morphis)]

See https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/bluez/wily/view/head:/audio/telephony-ofono.c#L1346 for details.

[Simon Fels (morphis)]

This will be implemented as part of the ongoing BlueZ 5 porting work.

[Tony Espy (awe)]

Here's the associated pull-request ( currently under-review ):

https://github.com/rilmodem/ofono/pull/214

[Uranicus (matthias.ritter)]

I have an interesting finding about the battery status in the car.

I am on:
current build number: 222
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-01-06 19:35:20
version version: 222
version ubuntu: 20160106
version device: 20151216-378d4f3
version custom: 20151111--36-46-vivid

In this rc-proposed version and also the version before (January, 5th) I have once the real battery status of the phone shown in the car and after a restart of the car (not the phone) I have the indication of a full battery level.

I have two SIM cards in my phone but the second SIM card is locked (I have not entered the PIN code).

I have attached sys.log and dbus.log of today. I have changed to the lastest rc-proposed today at 19:35 h ish and after this there was the occasion that the real battery status was shown in the car and after I re-started the car again (after a short break) the display in the car showed a full battery level.

[Uranicus (matthias.ritter)]

Attachement to my report.

[Tony Espy (awe)]

@Matthias

So what you're saying is that you see the correct battery level displayed in your car the first time after you connect the phone and car, and then after you restart the car, the battery level is just shown as full? Once this happens, does the battery level displayed ever change or does it continually read as full after the car restart?

I recently made some improvement to the way the battery level is monitored, however these changes have no yet landed in our proposed images. I'll discuss with my team and see if we can land this before the deadline for OTA9.

[Uranicus (matthias.ritter)]

@Tony

Today I was able to monitor and track the issues with the battery indicator of my car.

I am on:

current build number: 242
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-01-26 07:13:53
version version: 242
version ubuntu: 20160126
version device: 20160108-efc96d8
version custom: 20160111-926-36--vivid

This evening I had once a correct battery indication of my in car display (Seat Alhambra 2013 model). Then after a restart of the car I had again a full battery (eventhough the battery was <50%). Then I restarted the car several times without success. I have also turned off / on bluetooth without success.

Only a restart of the phone led to the result that the battery index showed again the correct result.

In the syslog I have:

Jan 26 18:53:39 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,2,0,2\r\n\r\nOK\r\n
Jan 26 20:31:46 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,2,0,5\r\n\r\nOK\r\n
Jan 26 20:33:44 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,2,0,5\r\n\r\nOK\r\n
Jan 26 20:34:59 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,2,0,5\r\n\r\nOK\r\n
Jan 26 20:36:02 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,3,0,5\r\n\r\nOK\r\n
Jan 26 20:38:13 ubuntu-phablet ofonod[1992]: Server: > \r\n+CIND: 1,0,0,0,5,0,2\r\n\r\nOK\r\n

where "2" is the correct battery index. I have restarted the phone between 20:36 h and 20:38 h (indicator switches from 5 -> 2). Between the reconnects on 20:31 h, ... 20:36 h I have stopped and restarted the car (pulled the key and waited for some seconds) and once turned off / on bluetooth via GUI of system settings.

I have attached the log files for your information to trace down this issue.

Matthias / Uranicus

[Pat McGowan (pat-mcgowan)]

reopening until we close the issues noted

[Tony Espy (awe)]

Based on comment #8 and discussion with the product team, I've changed the ofono tasks back to 'Confirmed' as it seems there's more work to do.

[Uranicus (matthias.ritter)]

Do you need any additional input from me?

I have changed my phone to OTA-9 (stable channel) today and I have experienced the same issue there.

Please let me know if you need something to be tested in this area.

Matthias

[Tony Espy (awe)]

@Uranicus

Right now I think we have enough information. We'll let you know if we need more...

Hopefully we can get this squared away for OTA10.

Thanks for your patience...

[Uranicus (matthias.ritter)]

Best success!

[Pat McGowan (pat-mcgowan)]

no progress moving to backlog

[Daniel van Vugt (vanvugt)]

Reduced priority for Ubuntu Touch bugs.

[Daniel van Vugt (vanvugt)]

Ubuntu Touch is no longer supported.