The issue is that all persistent settings are maintained by the runtime. Audioflinger comes up before the runtime, and native code doesn't have any way to query the runtime for those persistent settings.
This is not really an issue unless you try to do something with audio before the runtime has completed booting. On Nov 14, 2:25 pm, "pavan savoy" <[EMAIL PROTECTED]> wrote: > Hi, > > While going through the android source, audioFlinger.cpp, I see that there > is a FIXME: which says that routing configurations such as ROUTE_SPEAKERS, > ROUTE_EARPIECE should come from settings, while its been hard-coded > currently. > So what does that mean ? I cannot try out a HS/HFP now ? > Shouldn't ROUTE_BLUETOOTH also be a part of MODE_IN_CALL ? > > Am I thinking straight or ROUTE_BLUETOOTH is something totally different ? > If so please point me in that direction. > > Thanks & Regards, > Pavan Savoy. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
