platform_external_parameter-framework/Android.mk, branch pie-release-2 Unnamed repository; edit this file 'description' to name the repository. Rename libicuuc-host/libicui18n-host to libicuuc/libicui18n 2016-09-12T21:35:05+00:00 Dan Willemsen dwillemsen@google.com 2016-09-12T21:35:05+00:00 18cf6a72ebdbc22e47061bc151f9cf0b4024e013 These modules can be named the same between the target and host libraries, which simplifies references to them, particularly in Soong. To prevent accidentally loading the system copy of the library, we still rename the installed name to be libicu*-host.so. But modules do not need to know that in order to build against them. Change-Id: Idd3082aacc6c78a7a1490d6861a2c530fba1e3e1 
These modules can be named the same between the target and host
libraries, which simplifies references to them, particularly in
Soong.

To prevent accidentally loading the system copy of the library,
we still rename the installed name to be libicu*-host.so. But
modules do not need to know that in order to build against them.

Change-Id: Idd3082aacc6c78a7a1490d6861a2c530fba1e3e1
parameter-framework: Fix incremental build issue 2016-03-29T15:59:46+00:00 Di Folco, Neil neil.di.folco@intel.com 2016-03-23T17:59:46+00:00 c599aa5fada664c56f4330a0e05af4e54971534f Fix incremental build issue where libremote-processor was not rebuilt when changing the networking mode support. This can cause a crash at runtime when starting the AudioPolicyEngine. Change-Id: I3b4fc0924eb9f891b8e06690ac23bdd3f2055291 Signed-off-by: Di Folco, Neil <neil.di.folco@intel.com> 
Fix incremental build issue where libremote-processor
was not rebuilt when changing the networking mode support.

This can cause a crash at runtime when starting the AudioPolicyEngine.

Change-Id: I3b4fc0924eb9f891b8e06690ac23bdd3f2055291
Signed-off-by: Di Folco, Neil <neil.di.folco@intel.com>
parameter-framework: integrate v3.2.4 within Android environment 2016-03-05T01:54:33+00:00 François Gaffie francois.gaffie@intel.com 2016-02-17T07:04:43+00:00 481587bdf35ee618daf7d0d55aeba9023052ad36 This patch makes the integration of the new PFW v3.2.4 within Android by adding the required makefile, required license file, required header files. Bug: 22887211 Change-Id: I2b02af30b0540e72b1fab0c7250076cb55630af3 Signed-off-by: François Gaffie <francois.gaffie@intel.com> 
This patch makes the integration of the new PFW v3.2.4 within
Android by adding the required makefile, required license file,
required header files.

Bug: 22887211

Change-Id: I2b02af30b0540e72b1fab0c7250076cb55630af3
Signed-off-by: François Gaffie <francois.gaffie@intel.com>
parameter-framework: Drop of github upstream version v3.2.4 2016-03-05T01:42:09+00:00 François Gaffie francois.gaffie@intel.com 2016-02-17T09:58:44+00:00 9368eea42a1afb01dd44110582f997115b50e742 Main features are: -Networking code may now be opted-out (for android build: no socket opened for user build) -Get rid of python prebuild for XML generation Bug: 22887211 Change-Id: Ieee49b439f694f14ce48c23127d34622691397ef Signed-off-by: François Gaffie <francois.gaffie@intel.com> Signed-off-by: David Wagner <david.wagner@intel.com> 
Main features are:
-Networking code may now be opted-out
     (for android build: no socket opened for user build)
-Get rid of python prebuild for XML generation

Bug: 22887211

Change-Id: Ieee49b439f694f14ce48c23127d34622691397ef
Signed-off-by: François Gaffie <francois.gaffie@intel.com>
Signed-off-by: David Wagner <david.wagner@intel.com>
parameter-framework: allow to use custom parameter manager 2016-02-25T19:47:31+00:00 François Gaffie francois.gaffie@intel.com 2016-02-16T12:53:19+00:00 0efdadfc1eacc7271c8f854a8a610fdc2cc66102 Android build system prevents from having the same module target refered in more than one makefile. Some platform may need to use a custom parameter manager version than the aosp version of the PFW. This patch inhibits the AOSP PFW if USE_CUSTOM_PARAMETER_MANAGER is set to true. Change-Id: Ifc56ef44b2b3928329fc59e7984bef4959453419 Signed-off-by: François Gaffie <francois.gaffie@intel.com> 
Android build system prevents from having the same module
target refered in more than one makefile. Some platform may need to use
a custom parameter manager version than the aosp version of the PFW.
This patch inhibits the AOSP PFW if USE_CUSTOM_PARAMETER_MANAGER is
set to true.

Change-Id: Ifc56ef44b2b3928329fc59e7984bef4959453419
Signed-off-by: François Gaffie <francois.gaffie@intel.com>
stlport library is needed for versions of Android before M 2015-08-14T18:11:14+00:00 Zhengyin Qian qianzy@google.com 2015-08-14T18:11:14+00:00 531c26be6445110360042f1c94952fbcb76d4971 Conditionally include it based on the Android version Change-Id: I4b17e3c0f61a6fd2b0b1e48ed1efe16e0a446dfc 
Conditionally include it based on the Android version

Change-Id: I4b17e3c0f61a6fd2b0b1e48ed1efe16e0a446dfc
Exclude from Mac build. 2015-06-09T22:20:36+00:00 Ying Wang wangying@google.com 2015-06-09T22:20:36+00:00 0a3edf7907ec2e91b6b3a64f46fb55c7c00a01c4 The code doesn't build on Mac. Temporarily exclude this project from Mac builld. Bug: 21669400 Bug: 21734546 Change-Id: I68278d69803219dadd27487ed06c52d77a5a9833 
The code doesn't build on Mac.
Temporarily exclude this project from Mac builld.

Bug: 21669400
Bug: 21734546
Change-Id: I68278d69803219dadd27487ed06c52d77a5a9833
parameter-framework: initial commit 2011-09-08T13:18:29+00:00 Patrick Benavoli patrickx.benavoli@intel.com 2011-08-31T09:23:23+00:00 68a912857707864bbaaff9808717813105072a6e BZ: 6081 Parameter-framework is still-under-development, Intel proprietary, multi-platform (standard C++, for now only linux, no dependency on Android) software that allows system-wide parameter management. It relies on a number of configurations files, from which it knows how / when to hand out settings towards the hardware (subsystems) at runtime. 3 kinds of configuration files are used: - Structure description files indicating the actual parameter structure, types, min/max values, data representation. - Configurable domain description file containing the actual distribution of parameters over different domains, that is, different set of configurations, each of which being dynamically activated based on selection criteria rules that are themselves configurable. Configurable domains file contain the tuned settings along the tuning process, that is during the period where the system is being tuned. - Binary settings file used to store the settings when the tuning process is complete. Changing any of those files causes no recompilation of the framework. This project is based on a open plugin architecture allowing any kind of subsystems to be handled, whatever their respective Endianness. It fully relies on the platform SW to provide it with with the kowledge of exisitng selection criteria (selected device, current mode), as well as change events that occuring on them, thus triggering the application of corresponding configuration settings wherever appropriate. It supports handling mutliple parameter classes (Audio, Energy management) through TCP/IP interface. For now tuning commands can be sent to parameter-framework instances through a command-line utility, via adb over USB or via ethernet/WIFI. Change-Id: If7709c464db118f367f953e0824f49cce9fd0402 Orig-Change-Id: I7842e8808a4cfc0c615e0365e6d02101971ae2dc Signed-off-by: Patrick Benavoli <patrickx.benavoli@intel.com> Reviewed-on: http://android.intel.com:8080/16877 Reviewed-by: Mahe, Erwan <erwan.mahe@intel.com> Tested-by: Barthes, FabienX <fabienx.barthes@intel.com> Reviewed-by: buildbot <buildbot@intel.com> Tested-by: buildbot <buildbot@intel.com> 
BZ: 6081

Parameter-framework is still-under-development, Intel proprietary,
multi-platform (standard C++, for now only linux, no dependency on
Android) software that allows system-wide parameter management. It
relies on a number of configurations files, from which it knows how
/ when to hand out settings towards the hardware (subsystems) at
runtime.
3 kinds of configuration files are used:
- Structure description files indicating the actual parameter
structure, types, min/max values, data representation.
- Configurable domain description file containing the actual
distribution of parameters over different domains, that is, different
set of configurations, each of which being dynamically activated
based on selection criteria rules that are themselves configurable.
Configurable domains file contain the tuned settings along the tuning
process, that is during the period where the system is being tuned.
- Binary settings file used to store the settings when the tuning
process is complete.

Changing any of those files causes no recompilation of the framework.
This project is based on a open plugin architecture allowing any kind
of subsystems to be handled, whatever their respective Endianness.
It fully relies on the platform SW to provide it with with the
kowledge of exisitng selection criteria (selected device, current
mode), as well as change events that occuring on them, thus
triggering the application of corresponding configuration settings
wherever appropriate.
It supports handling mutliple parameter classes (Audio, Energy
management) through TCP/IP interface.
For now tuning commands can be sent to parameter-framework instances
through a command-line utility, via adb over USB or via ethernet/WIFI.

Change-Id: If7709c464db118f367f953e0824f49cce9fd0402
Orig-Change-Id: I7842e8808a4cfc0c615e0365e6d02101971ae2dc
Signed-off-by: Patrick Benavoli <patrickx.benavoli@intel.com>
Reviewed-on: http://android.intel.com:8080/16877
Reviewed-by: Mahe, Erwan <erwan.mahe@intel.com>
Tested-by: Barthes, FabienX <fabienx.barthes@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>