I would recommend that you go for a systemd drop-in file [1].
That would be something like a small snippet placed to
/etc/systemd/system/dbus-org.bluez.service/override.conf

In that file place something like
[Service]
ExecStart=
ExecStart=<new command line with your custom options>

this way you don't need to alter the upstream recipe with weird sed
hacks or similar.

This drop-in file could be packaged by any recipe or bbappend.

[1] https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html

On 29.12.20 07:48, chandra naik wrote:
> Hi
>
> After board boot up , we are editing vi
> /etc/systemd/system/dbus-org.bluez.service these file as
> ExecStart=/usr/lib/bluetooth/bluetoothd -C (here we are adding -C means
> bluetooth running in compact mode).
>
> but these is not good practice , so how we can change these service at
> compiling time itself , any idea ? main agenda is Run bluetoothd daemon
> in compatibility mode while building yocto image.
>
>
>
>