Hi, If you care about latency, which I think should, don't get properties one by one, instead use ObjectManager once the service is loaded, cache the values and just watch PropertiesChanged signals.
On Fri, Dec 5, 2014 at 10:01 AM, Zheng, Wu <[email protected]> wrote: > Hi Bluetooth-Frwk guys, > > Some modification of Bluetooth-Frwk (in Tizen branch) are needed to fix the > TIzen Common issues. > The related bugs need to be fixed to match some time points. > > Therefore, the following patches have been submitted. > https://review.tizen.org/gerrit/#/c/30969/ > https://review.tizen.org/gerrit/#/c/30970/ > https://review.tizen.org/gerrit/#/c/30968/ > https://review.tizen.org/gerrit/#/c/30971/ > > Not make sure that the related patches will impact on the other platform. > > If it is, " __TIZEN_MOBILE__ " is needed to be added to keep old source code > match the related platform. > > If not, it will be accepted to match TIzen Common and fix the related bugs. > > Some suggestions? > > Best Regards > Zheng Wu > >>-----Original Message----- >>From: Dev [mailto:[email protected]] On Behalf Of >>[email protected] >>Sent: Monday, December 1, 2014 8:43 PM >>To: [email protected] >>Subject: [Dev] bluetooth-frwk changes >> >>Hi all, >> >>I'm working on fixing bluetooth related bugs for the M14.4 IVI release. >> >>To do so, I found few limitations/constraints in bluetooth-frwk, I'd like to >>change: >> >>- bt-service daemon automatically enables bluetooth. >> --> I would like to keep bluetooth state as it is and align accordingly >> vconf bt >>status key. >> >>- in each bluetooth CAPI call, bt adapter state is checked. Currently CAPI >>directly >>checks the status over Bluez property. >> --> I would like to make this check in bt-service. By this way, bt-service >> can be >>launched by dbus activation (when checking bt state at bt init phase for >>instance). >> >>The main goal here is to clean up tizen bluetooth crosswalk extension >>intialization in fixing IVI bluetooth bugs. >>In addition it will unify initialization phase in case of NTB or >>bluetooth-frwk >>component. >> >>Does someone see a problem with this approach ? >> >>Thanks and regards, >>Corentin >> >> >>_______________________________________________ >>Dev mailing list >>[email protected] >>https://lists.tizen.org/listinfo/dev > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
