>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, Robert Greenwalt <[email protected]>wrote:

> 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, 2010 at 9:18 PM, Gururaj BO <[email protected]> wrote:
>
>> 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)
>>
>> file vi system/core/init/property_service.c
>>
>> to increase memory allocated to system property. Then it is working fine.
>> What Information I got is currently max 247 system properties we can store.
>> 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.
>>
>> So if we can increase this shared memory allocated to system property then
>> we can store more system properties.
>>
>> Thanks
>> Gururaja B O
>>
>>
>> On Thu, Aug 26, 2010 at 2:07 AM, Deva R <[email protected]> wrote:
>>
>>> (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
>>>
>>>
>>> <http://git.omapzoom.org/?p=platform/system/core.git;a=blob;f=libcutils/properties.c;hb=refs/heads/p-froyo#l59>and
>>> You can increase the size limit in bionic
>>>
>>> http://git.omapzoom.org/?p=platform/bionic.git;a=blob;f=libc/include/sys/system_properties.h;hb=p-froyo#l38
>>>
>>>
>>>
>>> On Wed, Aug 25, 2010 at 10:15 PM, Robert Greenwalt <
>>> [email protected]> wrote:
>>>
>>>> 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 <[email protected]> wrote:
>>>>
>>>>> 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 <[email protected]> wrote:
>>>>> > 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 but it is not setting the
>>>>> > properties.
>>>>> >
>>>>> > is there any permission problem with this?
>>>>> >
>>>>> > Thanks
>>>>> > Gururaja B O
>>>>> >
>>>>> > On Aug 18, 11:22 pm, Robert Greenwalt <[email protected]> wrote:
>>>>> >
>>>>> > > Perhaps - the '#' suggests root, but I know my adb shell doesn't
>>>>> start as
>>>>> > > root and I've been burned before with this same issue because of
>>>>> that.
>>>>> > >  Trying it doesn't hurt.  If that's not it I don't know why setprop
>>>>> isn't
>>>>> > > working.
>>>>> >
>>>>> > > R
>>>>> >
>>>>> > > On Wed, Aug 18, 2010 at 10:55 AM, Deva R <[email protected]>
>>>>> wrote:
>>>>> > > > >try 'su' first
>>>>> > > > Isnt this android console terminal,  by default have root access?
>>>>> >
>>>>> > > > >How to make this to set the value?
>>>>> > > > Not sure whats wrong, btw tried on my froyo setup, it worked like
>>>>> below
>>>>> > > > just after boot.,
>>>>> >
>>>>> > > > # getprop net.eth0.dns1
>>>>> >
>>>>> > > > #  setprop net.eth0.dns1 9
>>>>> > > > # getprop net.eth0.dns1
>>>>> > > > 9
>>>>> > > > #
>>>>> > > > #
>>>>> >
>>>>> > > > On Wed, Aug 18, 2010 at 8:32 PM, Robert Greenwalt <
>>>>> [email protected]>wrote:
>>>>> >
>>>>> > > >> try 'su' first
>>>>> >
>>>>> > > >> R
>>>>> >
>>>>> > > >> On Wed, Aug 18, 2010 at 6:56 AM, guru <[email protected]>
>>>>> wrote:
>>>>> >
>>>>> > > >>> Hi all
>>>>> >
>>>>> > > >>> I am trying to set system property so some value. like
>>>>> >
>>>>> > > >>> # setprop net.eth0.dns1 9
>>>>> > > >>> # getprop net.eth0.dns1
>>>>> >
>>>>> > > >>> #
>>>>> >
>>>>> > > >>> if i follow above steps it is not setting system property. what
>>>>> may be
>>>>> > > >>> the reason for this?
>>>>> >
>>>>> > > >>> How to make this to set the value?
>>>>> >
>>>>> > > >>> Thanks
>>>>> > > >>> Gururaja
>>>>> >
>>>>> > > >>> --
>>>>> > > >>> unsubscribe: 
>>>>> > > >>> [email protected]<android-porting%[email protected]>
>>>>> <android-porting%[email protected]<android-porting%[email protected]>
>>>>> >
>>>>> > > >>> website:http://groups.google.com/group/android-porting
>>>>> >
>>>>> > > >>  --
>>>>> > > >> unsubscribe: 
>>>>> > > >> [email protected]<android-porting%[email protected]>
>>>>> <android-porting%[email protected]<android-porting%[email protected]>
>>>>> >
>>>>> > > >> website:http://groups.google.com/group/android-porting
>>>>>
>>>>> --
>>>>> unsubscribe: 
>>>>> [email protected]<android-porting%[email protected]>
>>>>> website: http://groups.google.com/group/android-porting
>>>>>
>>>>
>>>>  --
>>>> unsubscribe: 
>>>> [email protected]<android-porting%[email protected]>
>>>> website: http://groups.google.com/group/android-porting
>>>>
>>>
>>>
>>
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to