Hi Petri, On Thu, Dec 1, 2016 at 11:12 PM, Petri Gynther <pgynther@xxxxxxxxxx> wrote: > However, in this case, I think this handling is correct. > load_gatt_db() showed "No cache for LEFQAU", so BlueZ has to > re-discover everything from the device over BLE. > But, since the device disconnected in the middle of discovery, BlueZ > couldn't fully populate the GATT DB and has to clean it. > If the device didn't disconnect so quickly, this would have most likely worked. > >> But I do agree that we should not reset the db if that was populated >> already, so I will try to fix that. > > Yes, once BlueZ does not reset the GATT DB on failed reconnects, this > problem will be solved. Please check if everything is alright when using upstream, it should clear the database anymore if we get an early disconnect. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
