Hi Szymon, On Wed, Dec 18, 2013 at 01:23:40PM +0100, Szymon Janc wrote: > Hi Marcel, > > > Hi Szymon, > > > > > This is first RFC for storage format for Android daemon. > > > > > > Some highlights: > > > - storage is much simple in format than Linux daemon (no addresses in paths > > > or filenames, only 1 adapter support etc) > > > - only info that requires persistency over daemon lifetime from Framework > > > perspective is stored > > > - settings file for adapter config > > > - devices file for remote device info (groups are remote devices addresses) > > > - Android storage path is /data/misc/bluez (I've decided to not use > > > /data/misc/bluetooth to avoid any clashes as there still seems to be > > > leftovers available in Android tree eg. there are still references to that > > > directory in CTS testcases and init files of Android 4.4) > > > > I would use /data/misc/bluetooth actually. Especially since the daemon is also called bluetoothd and not bluezd. > > > > What is the impact on just using /data/misc/bluetooth and see if anything really breaks. > > OK, this will require proper chown in device init.rc (as it is set to system/system > in system/core/rootdir/init.rc), but that would be needed for /data/misc/bluez path > anyway... I wonder can we find place without need to add extra chown... like using Bluedroid configuration location? Best regards Andrei Emeltchenko -- 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
