© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
@Simon
Regarding the battery mismatch, the HFP 1.6 specification ( section 4.33.2 AT Capabilities Re-Used from GSM 07.07 and 3GPP 27.007 ) documents that the battery level is indicated by an integer between 0 and 5. For a battery percentage of 1 or less, we indicate 0. Above 1%, we divide by 20 and add 1, giving us roughly five equal ranges in 20% increments.
If the battery display in the car has only four bars ( as opposed to five ), then it's not going to match up correctly, and the results will be skewed. I'm changing the ofono task to Incomplete.
@Uranicus
Thanks for your thorough testing! When testing non-standard images ( eg. from rc-proposed ), please attach the details image information from the command 'system-image-cli -i' ( run on the device ).
It sounds like Bluez5 improves one of the two original devices in your description ( eg. the Jabra ), however there still are some issues with it. I'll leave it up to Simon as to whether he'd like you to open a new bug for the specific re-connection failure described.
More work is needed apparently to get things working with your A3.
Also, regarding your A3, I'd be interested if it displays more bars for the phone battery level than the Seat.