Post Reply Subscribe to Thread Email Thread

[Cube U9GT2/Window N90/Visture V2/Easypad 970] Optimizing "build.prop" ICS 4.0.3

15th March 2012, 06:00 PM |#1  
dozz01's Avatar
OP Junior Member
Thanks Meter: 55
28 posts
Join Date:Joined: Feb 2012
Discussion Thread about "build.prop" for ICS 4.0.3 related to Cube U9GT2, Window N90, Visture V2, and Easypad 970.

Table of contents:
Part 1: Original build.prop discussion "# autogenerated by"
Part 2: Original build.prop discussion "# ADDITIONAL_BUILD_PROPERTIES"
Part 3: Additional lines
Part 4: Optimizing build.prop

Part 1: Original build.prop discussion "# autogenerated by":
# begin build properties
# autogenerated by
02. 4.0.3 IML74K eng.yangyun.20120108.124417 test-keys
07. Jan  8 12:44:47 CST 2012
13. ro.product.model=CUBE U9GT 2
14. ro.product.brand=Android
16. ro.product.device=rk29sdk
17. ro.product.board=rk29sdk
18. ro.product.cpu.abi=armeabi-v7a
19. ro.product.cpu.abi2=armeabi
20. ro.product.manufacturer=unknown
21. ro.product.locale.language=en
22. ro.product.locale.region=US
23. persist.sys.timezone=Asia/Shanghai
24. ro.wifi.channels=
25. ro.board.platform=rk29
# is obsolete; use ro.product.device
# Do not try to parse or .fingerprint
27. 4.0.3 IML74K eng.yangyun.20120108.124417 test-keys
# end build properties
01. Correct code
02.-05. Correct codes + Information (Source)
06. must beginn with the correct OS Version eg. 2.3.1 or 4.0.3 but afterwards text can be added
07. unimportant; changeable
08. UTC = timezone; another timezone would be GMT; found no sources in what to change those values
09. important; changeable in: eng, user, userdebug (source)
10.-11. unimportant => changeable
12. build description; i guess it should match with 2.+27.+28.; but it is also changeable, eg. rel-keys, unsigned, ...
13.+16. important for OS and some Apps; should match with the CPU
14. Information; e.g. the carrier the software is customized for
15. Information; is integrated in fingerprint
17.-19,25-29. correct code
20. important for OS and some Apps to identify some compatibilities
21.-22. for applications to identify from which region the user is
23. unimportant; good for Firmwares to adjust the values the OS starts with; typical lines are eg.: "persist.sys.language=en"; ""; "persist.sys.timezone=Europe/Amsterdam"
24. can be adjusted to "14", but it wont probably effect smth.

Part 2: Original build.prop discussion "# ADDITIONAL_BUILD_PROPERTIES":
02. ro.config.ringtone=Rigel.ogg
03. ro.config.notification_sound=Fluorine.ogg
04. ro.config.alarm_alert=Alarm_Classic.ogg
05. ro.config.facelock=enable_facelock
06. persist.facelock.detect_cutoff=5000
07. persist.facelock.recog_cutoff=5000
08. ro.opengles.version=131072
09. wifi.interface=wlan0
10. wifi.supplicant_scan_interval=120
11. persist.sys.usb.config=mtp
12. persist.sys.strictmode.visual=false
13. dalvik.vm.jniopts=warnonly
14. ro.sf.hwrotation=270
15. ro.rk.sdcard_volume=Internal SD
16. ro.rk.external_volume=External SD
17. ro.sf.fakerotation=true
18. sys.hwc.compose_policy=6
19. rild.libargs=-d_/dev/ttyUSB1
20. ril.pppchannel=/dev/ttyUSB2
21. ril.function.dataonly=1
22. rild.libpath=/system/lib/
23. dalvik.vm.heapstartsize=8m
24. dalvik.vm.heapgrowthlimit=64m
25. dalvik.vm.heapsize=256m
27. ro.setupwizard.mode=OPTIONAL
28. dalvik.vm.dexopt-flags=m=y
30. dalvik.vm.stack-trace-file=/data/anr/traces.txt
1.-4. self explaining settings
5.-7. can be deleted when facelock ist not be used
8. OpenGL ES 2.0 code
9. correct code
10. changeable from 1 to indefinite; some issues occur if value is set to high
11.-13. correct code
14. effects the screen rotation; "270" is the best value for having the screen in portrait mode plus "auto-rotate screen" within settings activated; taking this line out results in having the screen in landscape mode plus "auto-rotate screen" within settings deactivated -> changing the screen mode here must happen over the launcher settings
15.-16. correct code; the line "ro.rk.usb_host_volume=USB Device" can be added if supported; unfortunately for now the Cube & co. Firmwares doesn't seem to support this
17. can be deleted
18. hwc stands for 3rd party hardware composer; the effects of "6" i.d.k.
19.-22. can be deleted when tablet is not used as phone
23. influences directly the overall device performance and best settings here are more important than in 24.-25.; with 1m the home screen will reload permanently and the device will restart occasionally, with 5m the home screen plus widgets should be fine but still the device will restart sometimes, the standard value 8m is already a good value; with every 1m more or less the device will use ~16MB more/less RAM; good performance value would probably be 7m, and a good stability value 10m; 12m is also acceptable
24. the size the startsize can grow; typical 2.x.x values were 32m-48m; good values for ICS are 48-64m
25. the size dalvik cache uses at max; typical values are 4 times the "heapgrowthlimit" or less
26. checking tool; when switched to "0" performance will slightly be increased(source)
-> updated to "1", because no noticeable effect with "0"
27. checking tool; when switched to "DISABLED" performance will slightly be increased
28. checking tool; when switched to "v=n,o=v" performance will slightly be increased
-> updated to =m=y, because no noticeable effect with "v=n,o=v"
29. can be deleted
30. correct code

Part 3: Additional lines:
01. debug.sf.nobootanimation=1
02. ro.config.hw_hasbootsound=false
03. pm.sleep_mode=[0-4]
04. dalvik.vm.verify-bytecode=false
05. ro.rksdk.version=RK2918_ANDROID4.0.3-SDK_V2.02_20120201
06. ro.product.version=1.0.0
01. second boot-animation wont start
02. no sound during boot process
03. causes deeper sleep; often used in 2.x.x, but i.d.k. if it still has an effect in ICS; values "0, 1, 2, 3, 4" (source, bottom of website)
04. checking tool; when switched to "false" performance will slightly be increased; but it also can negatively effect applications (source)
05.-07. some new lines from N90/Moage, but i don't know the purpose yet

Part 4: Optimizing build.prop:
# begin build properties
# autogenerated by 4.0.3 IML74K eng.fjp.20120305.172107 test-keys Jan  8 12:44:47 CST 2012
# is obsolete; use ro.product.device
# Do not try to parse or .fingerprint 4.0.3 IML74K eng.fjp.20120305.172107 test-keys
# end build properties

# ro.sf.hwrotation=270
ro.rk.sdcard_volume=Internal Storage
ro.rk.external_volume=SD Card
ro.rk.usb_host_volume=USB Device
[blank line]
If someone has some tested improvements, please do not hesitate to post them.


update 2012.03.19:
part "# autogenerated by":
- still best settings; fingerprint data were updated

- some tweaks had in long term run with more apps installed no noticeable positiv effect and were removed or changed
- date and sound lines were removed
- dalvik.vm.heap values were changed to 7m, 48m, 192m - everything else (higher or lower) destabilized the system in long term run with more apps installed
- three lines from N90/Moage were added

-> new build.prop version (v08)
Attached Files
File Type: zip - [Click for QR Code] (2.0 KB, 327 views)
Last edited by dozz01; 14th May 2012 at 04:20 PM.
The Following 4 Users Say Thank You to dozz01 For This Useful Post: [ View ]
9th April 2012, 12:19 PM |#2  
mydave1's Avatar
Senior Member
Thanks Meter: 35
198 posts
Join Date:Joined: Mar 2011
Thanks for sharing this useful info.
I don't know much about android, so I am most hesitating to comment anything.
I tried your build.prop version 08. The tablet starts up quickly. What I hoped to see if GT Motor Racing Academy Free would run, but it did not. The paid version ran fine though.

30th April 2012, 05:36 PM |#3  
Flag Banting
Thanks Meter: 2
65 posts
Join Date:Joined: Nov 2010
which line actually deal with the camera hardware?
Trying to find a solution to skype video being zoomed to the max.
7th May 2012, 05:49 PM |#4  
dozz01's Avatar
OP Junior Member
Thanks Meter: 55
28 posts
Join Date:Joined: Feb 2012
Originally Posted by areankim

which line actually deal with the camera hardware?
Trying to find a solution to skype video being zoomed to the max.

The camera in Android is difficult to adjust or to manipulate - because the drivers are embedded deep in the Android source code. The build.prop unfortunately is not able to help here.

One doable solution would be to cancel the whole zoom functionality -> through deleting certain files or code lines.
Last edited by dozz01; 8th May 2012 at 02:24 PM.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes