I don't think we want a huge number of system properties - there are lots of
other ways to pass info around and I think many of our use cases are abuses
of the system properties mechanism. If you really need more system
properties, you can certainly do this on your builds.
R
On Wed, Aug 25,
If we try to store more than this we can not set the value.
In my phone it is already reached this value, so not able to set the
vlaues.
Hm, not sure what's holding still..
you can debug bionic with gdb/lauterbach(its native library only)/or trace
prints,
On Thu, Aug 26, 2010 at 9:13 PM,
Hi Rober/Deva R
If I comment some of the existing properties in system.prop I am able
to set the value, otherwise not. Why this behavior and how to deal
with this?
Thanks
Gururaja B O
On Aug 19, 9:35 am, guru guru.nav...@gmail.com wrote:
Why I asked this question is when i enable wifi, dhcpcd
Do you mean you can change the value of an existing property but cannot
create a new one?
That seems odd.
What device/build?
R
On Wed, Aug 25, 2010 at 3:36 AM, guru guru.nav...@gmail.com wrote:
Hi Rober/Deva R
If I comment some of the existing properties in system.prop I am able
to set
(repost from other thread).,
probably the size limit on properities field is blocking.. see
http://git.omapzoom.org/?p=platform/system/core.git;a=blob;f=libcutils/properties.c;hb=refs/heads/p-froyo#l59
The size limits are
#define PROP_NAME_MAX 32
#define PROP_VALUE_MAX 92
Hi Deva R/ rgeenwalt
I doubled the values of below macros
#define PA_COUNT_MAX 247*2
#define PA_INFO_START 1024*2
#define PA_SIZE 32768*2
static workspace pa_workspace;
static prop_info *pa_info_array;
extern prop_area *__system_property_area__;
static int init_property_area(void)
Why I asked this question is when i enable wifi, dhcpcd is not setting
system properties like
A)
dhcp.etho.ipaddress
dhcp.eth0.mask
dhcp.eth0.gateway
dhcp.eth0.leasetime
dhcp.eth0.server
but setting onlly
B)
dhcp.eth0.dns1
dhcp.eth0.dns2
dhcp.eth0.dns3
I tried to set above (A) using setprop
