Hi Szymon, > This will allow to pass Android properties over IPC and use them > in daemon for customization eg. Device Information or default adapter name. > > Open points: > - what properties should be read, currently I use ro.product.* as those > are present on AOSP Nexus devices, but eg. on Xperia phones there > seem to be ro.semc.product.* with more userfriendly name, so this > may vary upon devices. (eg ST18i vs Xperia Ray in model property). > Or maybe just use ro.bluetooth.* and require integrator to set those > accrodingly? I think we should take ro.bluetooth.* and fallback to ro.product.*. If some manufactures want to do something different, they can either set ro.bluetooth.* or hack the code. Nexus devices should default to something useful. We have to take that as standard location for product information. Since non of the DID details are mandatory, I prefer also that they are just not present if they are not configured in any property. Maybe BlueZ defaults for manufacturer and systemd id. > - should we also use this instead of 'Mode' passed on service init? > This would keep handling of all properities consistent but I'm fine > if we decide to keep Modes special. Do not understand the question. What do you mean. Regards Marcel -- 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
