- All apps can read memory/pm/state in Tizen 2.4
which means that the key does not have privilege.
Thus the privilege of Tizen 3.0 needs to be changed
to public for all of apps.
Change-Id: I16fa763ebef6f920c27b1dbf76c75077e0abbf7c
Signed-off-by: Taeyoung Kim <ty317.kim@samsung.com>
<?xml version="1.0" encoding="UTF-8"?>
<vconfkeylists>
<filedef name="__VCONF_INTERNAL_PM_KEYS_H__"/>
- <vconfkey type="int32" name="memory/pm/state" value="0" gid="6514" uid="" private_spec="true" layer="memory" readPriv="http://tizen.org/privilege/display" writePriv="http://tizen.org/privilege/internal/buxton/readonly">
+ <vconfkey type="int32" name="memory/pm/state" value="0" gid="6514" uid="" private_spec="true" layer="memory" readPriv="http://tizen.org/privilege/internal/default/public" writePriv="http://tizen.org/privilege/internal/buxton/readonly">
<header>VCONFKEY_PM_STATE</header>
<creator/>
<email/>
#!/bin/bash
-/usr/bin/buxton2ctl -i -d create-int32 "memory" "memory/pm/state" "0" "http://tizen.org/privilege/display" "http://tizen.org/privilege/internal/buxton/readonly"
+/usr/bin/buxton2ctl -i -d create-int32 "memory" "memory/pm/state" "0" "http://tizen.org/privilege/internal/default/public" "http://tizen.org/privilege/internal/buxton/readonly"
/usr/bin/buxton2ctl -i -d create-int32 "memory" "memory/pm/custom_brightness_status" "0" "http://tizen.org/privilege/internal/default/platform" "http://tizen.org/privilege/internal/default/platform"