DUNIA ANDROID

UPDATE: Galaxy Note with Sony Bravia Engine Demo


the Gallery Sony Bravia Engine mod for SGN N7000 will be available later tonite HKT. this mod makes it possible to render images with Sony Bravia Engine's implementation, which increases the sharpness, contrast, levels and so forth of the images and produces better outputs

it is based on the newest Android 2.3.6 rom N7000XXLC1, which should be compatible for ex-XXLC1 roms also. and wallpaper rendering is added as well into this mod

Samsung Gallery3D Original	Samsung Gallery3D with Sony Bravia Engine

more screenshots will be added later


note that this is not the one which regarded as fake and was shipped with almost every roms before in the SGS2 and other forums. for those who in doubt or want to know how and why my mod works but not others that simply tell u to edit the prop files, read my post about this issue below and u will have a totally different conclusion:
is Sony Bravia Engine really working with SGS2 and other Android devices?


for reference, please refer to my previous posts below about the Sony Bravia Engine Gallery3D demo for SGS2:
SGS2 Gallery3D with Sony Bravia Engine previews
SGS2 wallpaper Sony Bravia Engine demo
SGS2 ICS 4.0.3 Sony Bravia Engine demo
more Bravia Engine screenshots marked with differences

Samsung Galaxy S2 Gallery3D with Sony Bravia Engine, obvious differences are marked in red circles for easy comparison

Samsung Gallery3D Original	Samsung Gallery3D with Sony Bravia Engine

references:
SGS2 ICS 4.0.3 Sony Bravia Engine demo with wallpaper rendering available
now with wallpaper enhancements - SGS2 wallpaper Sony Bravia Engine demo
SGS2 Gallery Sony Bravia Engine demo

UPDATE4: more Bravia Engine screenshots marked with differences

UPDATE3: SGS2 ICS 4.0.3 Sony Bravia Engine demo with wallpaper rendering available

UPDATE2: now with wallpaper enhancements - SGS2 wallpaper Sony Bravia Engine demo

UPDATE: SGS2 Gallery Sony Bravia Engine demo


see the differences with Sony Bravia Engine turned on in Samsung Galaxy S2 I9100 with default gallery (Gallery3D.apk). for those who believed Sony Bravia Engine can only be run on Sonys device but not others, you can still say that this is not a "100% port" and i will not argue with you. however, you must admit that it can be run on a SGS2 too


EDIT: these screenshots were made on 15 Dec 2011, but for some reasons the publish date was postponed. there is no schedule for resuming the development yet, until a row with one of the forum is resolved.

also note that the images on the left are identical to those on the rigth hand side (except the bottom one), indicating the outputs from Samsung Gallery3D with Sony Bravia Engine and SonyEricsson Gallery3D are indifferent

Samsung Gallery3D with Sony Bravia Engine	SonyEricsson Gallery3D
click here to view the original file
click here to view the original file
click here to view the original file

Samsung Gallary3D - a closer look (1/2 scale)
without Sony Bravia Engine	with Sony Bravia Engine
click here to view in full size (800x480)

UPDATE3: more Bravia Engine screenshots marked with differences

UPDATE2: more screenshots here SGS2 Gallery3D with Sony Bravia Engine previews

UPDATE3: SGS2 Gallery Sony Bravia Engine demo

UPDATE: it now works with stock gallery IT WORKS!! Sony Bravia Engine and Samsung Galaxy S2 with stock Gallery3D



hi all,

after i mistakenly reported the Sony Bravia Engine worked with SGS2 before, i decided to test if the Bravia Engine can be used on Galaxy S2 myself from the beginning

after spending a whole day in dealing with the files and dependencies, i think i have found something finally and yielded the following results :

1 - the Gallery3D (SemcGallery3D.apk) from X10 works together with the stock one




2 - the library file libswiqibmpcnv.so is loaded after the SE Gallary is launced, and fuser shows the libswiqibmpcnv.so is being used by the SE Gallary




3 - the be_photo is loaded by the libswiqibmpcnv.so when a photo is selected in the SE Gallery. and if it is removed, libswiqibmpcnv.so reports an error




and finally, the outputs for two HD images found on the internet from stock Samsung Gallery3D.apk and SonyEricsson SemcGallery3D.apk with be_photo loaded, taken by screen capture

Samsung Gallery3D	SonyEricsson Gallery3D
click here to view the original file
click here to view the original file

to be continued ... :D

recently, LG Optimus x2 has a new TV ad showing the phone takes only 4.6 seconds to load Yahoo HK main page. I surfed their website and found they have another claiming that it takes 7.6 seconds (average result via wifi) to load aastock.com (Traditional Chinese version) and ready for challenge. so i did some tests on my Galaxy S ...


DISCLAIMER:
- the data/results stated below are for reference only, and it is NOT supposed/assumed to be used for any other comparisons by any means, and does NOT represent any standard
- the data/results obtained may varies depending on a lot of uncontrollable factors
- the results were obtained with a non-stock and modified Galaxy S ROM I9000XWJS8, without overclocking
- the wifi link speed used for the test was 65Mbps, via a 100M broadband
- all caching, including proxy server cache were disabled (not including ISP's cache server, if any)
- the tests were taken on 03 April 2011 2045-2200 HKT


according to Optimus x2's website, i cleared all browser cache, and i even killed the browser process (not by closing it, but killed the application actually)

test 1: browser process retained, cache cleared, flash enabled, tested for 5 times as LG's
a/. loading www.aastocks.com/tc/default.aspx
Optimus x2: 7.6 seconds (quoted from their website)
my Galaxy S: max ~6.x seconds, min ~5 seconds, average ~5.x seconds

b/. loading hk.yahoo.com/?m=1
Optimus x2: 4.6 seconds (quoted from their tv ad)
my Galaxy S: max ~4 seconds, min ~3 seconds, average ~3.x seconds


test 2: started a new browser process (old process killed), cache cleared, flash enabled, tested for 5 times as LG's
a/. loading www.aastocks.com/tc/default.aspx
Optimus x2: 7.6 seconds (quoted from their website)
my Galaxy S: max ~7 seconds, min ~5.x seconds, average ~6.x seconds

b/. loading hk.yahoo.com?m=1
Optimus x2: 4.6 seconds (quoted from their tv ad)
my Galaxy S: max ~5 seconds, min ~4 seconds, average ~4.x seconds


test 3: browser process retained, cache cleared, flash enabled, computed with stop watch by lifehacker.com
a/. loading http://cache.lifehacker.com/assets/resources/stopwatch.php?u=http://www.aastocks.com/tc/default.aspx
my Galaxy S: 4.773 seconds


b/. loading http://cache.lifehacker.com/assets/resources/stopwatch.php?u=http://hk.yahoo.com/?m=1
my Galaxy S: 2.555 seconds



test 4: browser process retained, cache cleared, flash enabled, computed with stop watch by numion.com
a/. loading http://numion.com/stopwatch/Start.html?Url=http://www.aastocks.com/tc/default.aspx
my Galaxy S: 6.265 seconds


b/. loading http://numion.com/stopwatch/Start.html?Url=http://hk.yahoo.com?m=1
my Galaxy S: 3.11 seconds



conclusion? no need to conclude ...

it's been released a few days ago. when compared with the previous beta version, which was quite good in feature wise but not performance wise, it is a "more complete version". some benchmarks also show that the performance of Fennec is better than the stock Android browser


check it out at Mozilla official site for mobile

installed jve modem (extracted from official ginger beta rom I9000XWJV1) to my 2.2.1 rom, i found that the signal is stronger then jpy. also, i got more satellities found even in indoors than before and the battery consumption is about the same

just performed a few tests and the results are record breaking (my records for own mod)
no overclock, stock cpu frequency

performed some tests days before and I would like to share the results with all of you. the result was as expected (my expectation)

the test was conducted on /dbdata, using dd to read and write, and with different slice_sync and slice_async values.
According to lwn.net:
- slice_sync: How many msec a sync disk slice lasts
- slice_async: How many msec an async disk slice lasts

in froyo, the default value for slice_sync is 97, and slice_async is 39. while in eclair, they are 100 and 40 respectively.

and, the results were obtained by the average value under different file systems as below:
write: dd if=/dev/zero of=/dbdata/test count=25000 (using default bs=512)
read: dd if=/dbdata/test of=/dev/null

test1: default slice_sync (97), slice_async (39)
ext2 w=0.3563576, r=0.2172932
ext4 w=1.7057048, r=0.1286368
ext2 on ext4 w=0.2786272, r=0.1360666
ext2 on ext4 noatime nodiratime w=0.279215, r=0.124138
ext4 on ext2 w=0.4299866, r=0.1277804

test2: slice_sync (50), slice_async (20)
ext2 w=0.3883144,r=0.2209398
ext4 - omitted
ext2 on ext4 w=0.2743988,r=0.1343098
ext4 on ext2 w=0.4350612,r=0.2513572

test3: slice_sync (500), slice_async (200)
ext2 w=0.4159796, r=0.40419
ext4 - omitted
ext2 on ext4 - omitted
ext4 on ext2 w=0.4252074, r=0.2614818

obviously, the fastest one was ext2 on top of ext4, with only insignificant impact with noatime and nodiratime options (i cant believe it). this combination of file systems performed well as expected since while ext2 do somewhat like "blind read/write", the ext4 will hold the data b4 commit (PLS, pls dont argue ext2 and ext4 with me and that's why i described them very roughly... )


actually this was just for my own leasure but i think it may be useful to u guys as well so i decided to post it here for your ref


more info

after playing with Andriod for a month, I found a way to speed up the Android system by creating loop devices, no data2sd required
no more lags, smooth scrolling/zooming in and out in default browser with a web page contains more than 170 images, much faster cache for browser, market and other apps retrieval and listing

here's how:
- create an empty file with dd (i chose -b 4096 -m 1)
- mount it to loopx and format it with ext2 (busybox)
- create mount points and create links, eg
mount -o rw,noatime,nodiratime /dev/loop0 /dbdata/dbdataimage
then mv files and folders to /dbdata/dbdatimage
so, instead of reading /dbdata/databases/com.1.2.3, it will be linked to /dbdata/dbdataimage/databases/com.1.2.3
- finally write a script to mount them on boot by replacing playlogos1

simply speaking, is to run on an ext2 file block in rfs, and that's all for the trick!!


WARNING:
- i did it for /cache, /dbdata and /data only
- empty files, folders, and sym links will be deleted by the system under /cache
- dont reboot the phone when u've temporarily moved /dbdata/databases to a slow partition like /data


personally, i moved /data/data and /data/dalvik-cache to /dbdata and moved browser and market cache files to /cache

it's not for the benchmark only, instead, it has very good effects on ur phone's io

for the loop device:
busybox mknod /dev/loop0 b 7 0
busybox losetup /dev/loop0 /dbdata/dbdata.img
busybox mkfs.ext2 /dev/loop0
then mount it

and, here's my mount output:

rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check= no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check= no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check= no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/loop0 /dbdata/dbdata1 ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop2 /cache/cache1 ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop2 /cache/market ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop2 /cache/browser ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0102,dmask=0002,allow_utime=0020,codepage=cp4 37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0000,dmask=0000,allow_utime=0022,codepage=cp4 37,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0


- no need to deal with /data
- the major thing is /dbdata/databases
- it wont have impact when u connect it to ur pc/kies since kies only deal with /sdcard and /sdcard/sd only, which both r out of my concern
- to see the improvement, simply do a dd and u'll see the difference



what suprised me is that, i found in one of the taiwan's forum, ppl called it "Hong Kong's Lag Fix" (香港版卡三爽)

more info (chinese)






more info