yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] gGabi:
STweaks is still buggy for me, but not completely.

Everything sticks except SCREEN ->>>>>> and whatever tabs comes after it... :(

Backup profile workaround is not working anymore.

Also, YouTube fc's on each boot, but not with CM kernel.

EDIT: Configured STweaks again and reboot, everything sticks now. I'll test more and report.

EDIT 2: I did cleared YT data, reinstall, reboot between uninstall-install. I also fix permissions after kernel upgrade. No luck
[Galaxy S II Android Development] Nos_20:
For YouTube try uninstalling it and reinstalling it from Play.

That worked for me

Sent from my GT-i9100
[Galaxy S II Android Development] issy_i:
Hi everyone.

Dori could you take a Look and check if Battery profile act normal and Good to use? i think its broken for months and i've used it allot but sins 7.42 not anymore. i dont trust it
[Galaxy S II Android Development] fr3quency:
Seeing this, why not release a test kernel with the r3p2?
[Galaxy S II Android Development] JokerAce:
I used the values and it is working fine.

I was tuning it while on battery (i.e. charging removed), and I realize that changes made to the "CHRG TOUCH TRESHOLD E" makes the scrolling work as should. If I change that value to too low, it becomes slow. Weird thing is, tuning the "charging" than the "batt" threshold causes the scrolling to work properly :confused::confused:
[Galaxy S II Android Development] djsky2011:
I think 42 is just perfect, super smooth, just right on stock based ROM :)
[Galaxy S II Android Development] ArchenzeEL:
Touch Screen Delay 9.19

My touch Screen config is MXT224E

changes to any of the values in both places have no effect for me.

i am experiencing a touch delay and scrolling is vry difficult. i even have to enter my pattern lock slowly so that all the dots can register properly.

nevermind. i sloved the problem. reset Stweaks. changer charge thres. wipe dalvik
[Galaxy S II Android Development] manan001:
i updated to 8.18 .. touch sencitivity very very poor.. activated slide2wake but not working. and phone hangs on startup...

for now.

---------- Post added at 10:49 AM ---------- Previous post was at 10:40 AM ----------

it works perfect dori.... awsome.. please set default for next release.. dont forget.

http://db.tt/wGDbe4Xa
[Galaxy S II Android Development] dorimanx:
so its reversed? i will check that and tune to best found values.

Sent from my GT-I9100
[Galaxy S II Android Development] JokerAce:
Not sure if I understand reversed correctly, but what I am getting at is, it seems that CHRG threshold controls BATT threshold. Best found values seems to be the ones Big_bum provided. I have guided one complaint to that, and he hasn't complained.
[Galaxy S II Android Development] bogdan1980:
yes, Charge touch threshold e to 40/42 makes the scroll work normal. If i only change that, scroll is ok, but touch feeling is not so smooth. I have 2 sg2 and play with them in the same time, one use dorimanx 8.14( both E versions)

But, if we use settings from those 2 pictures, with 50/12/42/47,feelling is better then set only Charge touch threshold e.

So, its better to change all to this: 50/12/42/47. At least this is my felling.
[Galaxy S II Android Development] manan001:
We need to have thos implemeted as sometimes stweak resets then this big problem to re tune
[Galaxy S II Android Development] dorimanx:
RootBox! new nightly by Kroz

http://d-h.st/fRO
[Galaxy S II Android Development] dorimanx:
DONE!

https://github.com/dorimanx/initramfs3/commit/b87e10d8775fdc2716ea9387ecbe0f77145011a2
[Galaxy S II Android Development] jgcaap:
I choose this setting 50 / 12 / 45/46 I think is the perfect for scrolling to the E version
[Galaxy S II Android Development] djsky2011:
This is the perfect config for the E version, but as JokerAce said the changes to touch are made in charging rather than on battery
[Galaxy S II Android Development] m1trand1r:
cloning 1st rom to 2nd rom & downloading rootbox again....;):highfive:

Sent fom my S-II running >>SlimBean build 5.2 WEEKLIES: D << :D powered with DorimanX kernel v. >>9.18<<
[Galaxy S II Android Development] The-Captain:
This is a developer thread, searching is a must.

Don't get lazy and just post again when the answer can already be found....

Expect it to be deleted if you do so.

OP, let us know on stuff you want cleaned :good:
[Galaxy S II Android Development] dorimanx:
News update!!!

Kernels 8.19 + 9.19 online!

Bugs fixed and new updates added :)

new updates to ARM and Freezer from DEV Francisco Franco!

Change Log:

*Fixed and tuned MX224E touch screen + default STweaks settings.

*Increased the dirty_ratio/background_ratio to 70/35 to speed up ROM operations using free RAM, now we have good RAM manager code, so no problem.

*Ported updates to ARM, Freezer, BLOCK, TIMER, and to ondemand + hyper.

Now deep sleep should be good, as kernel will wakeup less during deep sleep, and save more power.

have fun and report about BUGS, and how mx224e touch screen works!

Thanks :)
[Galaxy S II Android Development] eskriminal:
churning them out mate! keep up the amazing work
[Galaxy S II Android Development] eskriminal:
not that long, not a problem

try flashing the zip codeworkx made of the blobs
[Galaxy S II Android Development] silentcontrole:
I think we will have new Mali drivers on the next release :)
[Galaxy S II Android Development] socekin:
Unchecked the LED on touch , but when I touch the screen intermittently, the LED always ON.

ROM: slimrom

kernel:the latest version
[Galaxy S II Android Development] HardCorePawn:
Hey Dori... thanks for the advice... I figured it out... as it turns out, it is not related to the fstab at all... was all related to recovery.rc (aka the init.rc used for recovery)...

mine had a Product ID of 6860... and was missing the mass_storage function part... Once I modified the product ID, it started correctly identifying as GT-i9100 in device manager (instead of MTP)...

I also had to make some mods to my BoardCommonConfig.mk

mine had "lun0" hardcoded, so it would share the internal SDcard on lun0... then try and share the external SDCard on "/sys/devices/platform/s3c-usbgadget/gadget/lun0/file", which it did successfully, but it seems the s3c-usbgadget device/driver doesn't work, so it would end up with only internal SDCard mounted correctly... :silly:

with the %d, it creates:

/sys/class/android_usb/android0/f_mass_storage/lun0/file

and

/sys/class/android_usb/android0/f_mass_storage/lun1/file

and both Ext and Int SDCards are now available! :victory:

Thanks again for your time... and good luck with the kernel... I know a lot of the Slim ROM guys are using your kernel for the awesome features that you've added (dual mounting in UMS mode, BLN, OC/UV etc.) :good: saves me having to learn kernel hacking ;) :D

ps. just as a heads-up... it seems that we have merged the updated MALI libraries from codeworkx into Slim ROM, so no doubt there will be all sorts of posts here and in the SlimBean thread that Slim and/or DorimanX kernel are not working properly together... :rolleyes:

so, I apologise in advance! :p
[Galaxy S II Android Development] pakhei123:
Please add ntfs mount so that no app is needed for mounting ntfs usb or drives:thumbup:
[Galaxy S II Android Development] leo2589:
Excuse me for the useless post but I want to congratulate with the D-Team..

The 9.18 and the first 9.19 had some problems expecially freeze lag and with profiles..

But from yesterday the last 9.19 is working very fine on my omega 4.2.2 aokp.. Everything is ok.. And the touch feels better.. And Stweaks gets opened faster respect past versions..

Good work D-Team.. :thumbup::D

And thanks for your free time to give us the "most advanced kernel in the world!" :D

Sent from Tapatalked JB GT~i91x10²​

​
[Galaxy S II Android Development] Prasad:
I'm seeing "*New updated GPU driver (mali update 3)" in the last text box from OP. However, that seems to come under

"More to be added later.

22/7/12 time 19:00

Kernel 1.0 -> 5.2"

Not sure if it's a todo listing or it's already there in the latest release?

Btw, this is the first time I've used the kernel with PAC ROM and am supremely impressed with the noticeable boost in responsiveness overall.. Thanks for a job well done! :)
[Galaxy S II Android Development] AntonioTrindade:
Lockups continue

I've been experiencing lockups since 9.14.

Now this lockup was with 9.19. Looking at the last_kmsg file (attached) I see the message "<3>mmc0: Timeout waiting for hardware interrupt."

Perhaps the lockups have something to do with this.

Cheers
[Galaxy S II Android Development] sancho55:
try 8.xx ? That solved lockups for me.
[Galaxy S II Android Development] AntonioTrindade:
Installed 8.19... Lets see if works!

Thanks!
[Galaxy S II Android Development] spankymo:
had several freezes while running 9.19 today. attached the last_kmsg and dmsg logs that I was able to gather. these were right after the freeze while I was trying to wake the phone (from deep sleep). I hope it helps.
[Galaxy S II Android Development] AntonioTrindade:
8.19 also hangs!

I has a couple of hangs with 8.19 also.

Here is the latest kernel log.

Thanks
[Galaxy S II Android Development] dorimanx:
News update!

Kernels 8.20 and 9.20 online.

For me stable 2 days 2 nights, so who stuck all the time, stop messing with config, and update you ROMS.

i am using ROOTBOX 18/05/13 by Kroz and it's PERFECT.

all the logs i see here, dont contain any kernel errors, so it's something else.

Change Log:

*Voku ported 3.0.78 update from main stream.

*Alucard updated and tuned the nightmare gov. (more options to tweak)

*I have ported update to kernel main build code and module code. from 3.10.y kernel.

kernel is stable and sleeping and waking, no overheats or sods/lags

i use performance profiles as is.

have fun.

try to ask for questions in Q&A tread, not here.

i read every post, every day.
[Galaxy S II Android Development] Prasad:
Thanks a ton, mate! Really appreciate your work... Gonna test this right away. :) I take it you've included Mali V3 drivers from CM10.1 mainline as well?
[Galaxy S II Android Development] AntonioTrindade:
Lockups in 9.14+

I think I found the cause of the lockups I've been experiencing.

I just changed the awake I/O governor to ZEN and the standby/sleep I/O governor to NOOP and, so far, no lockups.

It looks like the ROW I/O governor was the culprit.

As far as I could tell, a few minutes before the phone locked either the SYS CPU% was 100% or both the SIRQ and IO CPU% were at 100%.

Just a tip for all those that, like me, are having these hick-ups.

Just before I did this change, I completely wiped my phone and reinstalled everything, but it did not solve anything.

Cheers

EDIT: Even with this change the behavior remains the same. The phone is now unresponsive, although I can still access it using ADB.

EDIT 2: It's completely hung now.
[Galaxy S II Android Development] jgcaap:
Do you have vpll on?
[Galaxy S II Android Development] AntonioTrindade:
No. It's off.

All my tests were done with the default STweaks profile.

---------- Post added at 11:34 AM ---------- Previous post was at 11:11 AM ----------

After further tests I think I narrowed down the problem.

The 100% I/O and SIRQ CPU usage appear right after this kernel message:

<0>pm_wd_timeout: PM watchdog timeout: 30 seconds
<0>stack:
<4>Backtrace:
<3>[B]mmc0: Timeout waiting for hardware interrupt.[/B]
<7>mshci: ============== REGISTER DUMP ==============
<7>mshci: MSHCI_CTRL: 0x00000010
<7>mshci: MSHCI_PWREN: 0x00000001
<7>mshci: MSHCI_CLKDIV: 0x00000001
<7>mshci: MSHCI_CLKSRC: 0x00000000
<7>mshci: MSHCI_CLKENA: 0x00000001
<7>mshci: MSHCI_TMOUT: 0xffffffff
<7>mshci: MSHCI_CTYPE: 0x00010000
<7>mshci: MSHCI_BLKSIZ: 0x00000200
<7>mshci: MSHCI_BYTCNT: 0x00001000
<7>mshci: MSHCI_INTMSK: 0x0000bfce
<7>mshci: MSHCI_CMDARG: 0x00000008
<7>mshci: MSHCI_CMD: 0x00002157
<7>mshci: MSHCI_MINTSTS: 0x00000000
<7>mshci: MSHCI_RINTSTS: 0x00000030
<7>mshci: MSHCI_STATUS: 0x0000b906
<7>mshci: MSHCI_FIFOTH: 0x300f0010
<7>mshci: MSHCI_CDETECT: 0x00000001
<7>mshci: MSHCI_WRTPRT: 0x00000001
<7>mshci: MSHCI_GPIO: 0x00000000
<7>mshci: MSHCI_TCBCNT: 0x00000800
<7>mshci: MSHCI_TBBCNT: 0x00001000
<7>mshci: MSHCI_DEBNCE: 0x000fffff
<7>mshci: MSHCI_USRID: 0xffffffff
<7>mshci: MSHCI_VERID: 0x5342230a
<7>mshci: MSHCI_HCON: 0x00e424c1
<7>mshci: MSHCI_UHS_REG: 0x00010000
<7>mshci: MSHCI_BMOD: 0x00000382
<7>mshci: MSHCI_PLDMND: 0x00000000
<7>mshci: MSHCI_DBADDR: 0x64578000
<7>mshci: MSHCI_IDSTS: 0x00000000
<7>mshci: MSHCI_IDINTEN: 0x00000000
<7>mshci: MSHCI_DSCADDR: 0x64578000
<7>mshci: MSHCI_BUFADDR: 0x00000000
<7>mshci: MSHCI_WAKEUPCON: 0x00000000
<7>mshci: MSHCI_CLOCKCON: 0x00000000
<7>mshci: MSHCI_FIFODAT: 0x31303201
<7>mshci: ===========================================

After a while I get this in dmesg:

<3>INFO: rcu_preempt self-detected stall on CPU { 0} (t=60000 jiffies g=64254 c=64253 q=84876)
<6>Backtrace for cpu 0 (current):
<4>Backtrace: frame pointer underflow
<6>
<6>sending IPI to all other CPUs:
<4>IPI backtrace for cpu 1
<4>
<4>Pid: 0, comm: swapper/1
<4>CPU: 1 Tainted: G W (3.1.0-R78-Siyah-Dorimanx-V9.20-JB-CM-AOKP-SGII-PWR-CORE #1)
<4>PC is at exynos4_enter_idle+0x34/0x16c
<4>LR is at __getnstimeofday+0x3c/0x130
<4>pc : [<c0addd0c>] lr : [<c0b28dc8>] psr: 600d0013
<4>sp : e4065f98 ip : 519b4d3c fp : 00000000
<4>r10: c0fec398 r9 : 412fc091 r8 : c1296784
<4>r7 : 00000001 r6 : e4064000 r5 : 00000000 r4 : c1296db8
<4>r3 : 0002761e r2 : 009d8791 r1 : 519b4d3c r0 : dbaca785
<4>Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
<4>Control: 10c5387d Table: 4f8e404a DAC: 00000015
[Galaxy S II Android Development] ArchenzeEL:
RootBox 4.0 Stable Build Release

http://goo.im/devs/RootBox/RootBox_i9100_jb/RootBox-JB-i9100-V4.0.zip
[Galaxy S II Android Development] AntonioTrindade:
After further testing I managed to have a stable phone for more than a few hours.

Here's what I did in STweaks:

- Sleep CPU governor: zzmoove (in the default profile, it is ondemand);

- Awake I/O Scheduler: ZEN

- Sleep I/O Scheduler: NOOP

You can try different settings, but I'd stay away from the ondemand CPU governor and ROW I/O scheduler.

Hope this helps
[Galaxy S II Android Development] jgcaap:
thanks for this discovery lets hope we sort the hang once and for all. is so anoying sometimes -_- lol
[Galaxy S II Android Development] AntonioTrindade:
UPDATE: With these settings I haven't had any problem since I last applied them. Looks like I can point the finger at either the ROW I/O scheduler or the on demand CPU governor or both... :D
[Galaxy S II Android Development] DerBobo:
I use deadline as awake IO and noop as sleep. As gov I use interactive as awake and conservative as sleep and I've no problens at all on 9.20. So may be guys ROW s a factir of issues you have.

Signature:

Device: Galaxy SII i9100

ROM: SlimBean 4.2.2. build 5.5Weekly

Kernel: DorimanX 9.20

Modem: XXMS2
[Galaxy S II Android Development] :
Hey dori,

Just thought it'd let you know

http://xdaforums.com/showthread.php?p=41682716

I don't know if this will be of any help to you, i sure hope so :D
[Galaxy S II Android Development] dorimanx:
good info, we can use some parts, and give big thanks to codeworks and team :)

thanks for alert.

Sent from my GT-I9100
[Galaxy S II Android Development] dorimanx:
Thanks for support.

At morning i will do some more changes, and release new version, i have found some problems.

but for many, they not a problem, but for some = stuck cpu.

Sent from my GT-I9100
[Galaxy S II Android Development] AntonioTrindade:
That's one of the reasons why I love this kernel. The developer is always ready to solve our problems! :D

Keep it up, Dori! :good:
[Galaxy S II Android Development] 089man:
Version. 19 works perfectly.

The. 20 here not work... Phone freezes at all time.

I9100 Tapatalk 2, Rom1 Rootbox / Rom2 Slim, Kernel Dorimanx
[Galaxy S II Android Development] ArchenzeEL:
RootbBox 4.0 + Dorimanx Kernel 9.20 Benchmarks

This is my benchmark with default profile + small changes.

there is no doubt that performance profile will give higher benchmarks.

its really smooth at 2D UI drawing but for many 2D/3D games (eg. Daddy was a Thief) there is slight stutter moving between animations where screen is not being used( touched). my explanation is because of the dramatic CPU/GPU scaling.

Using default profile with :

CPU OC = 1.4Ghz

GPU:

VPLL

108-160-267-330-440 mhz @ 850,900,950,1100,1200/+50 mV

No VPLL

160-200-267-267-400 mhz @ 900,950,1000,1050,1150/+50 mv

Gives a much better real time Performance than benchmark.
[Galaxy S II Android Development] livefortoday:
I just had a spontaneous reboot :)
[Galaxy S II Android Development] myszonokr:
Dormianx 8.20, profile battery, changed as above plus Awake governor Pegasusq. and i have Black screen times to time - Hard reset can alive my phone.

Log atached.
[Galaxy S II Android Development] DF1E:
This Kernel is very fast and have good battery live but today i got some SODs :(
[Galaxy S II Android Development] tenchi0205:
This is the same thing happen to me too...
[Galaxy S II Android Development] JokerAce:
May I request users with SODs and throttled CPU etc, to stop posting as it has been acknowledged. Leave the thread for development post (e.g. Logcats) At my sig, you can find one way to assist in development.

Otherwise, you may be inclined to talk here with no restriction.

[Kernel][ICS/JB]Dorimanx Q&A / Discussion thread | Non-development posts
[Galaxy S II Android Development] AntonioTrindade:
dalvik-cache on /preload

I made a "mod" to my phone:

In recovery:

umount /dev/block/mmcblk0p12
mount /dev/block/mmcblk0p12 /preload
mount /data
cd /data/dalvik-cache
rm -rf *
cd ..
rmdir dalvik-cache
mkdir /preload/dalvik-cache
cd /data
ln -sf /preload/dalvik-cache /data/dalvik-cache

Basically, I put dalvik-cache on the /preload partition to save space on the /data partition.

This is incompatible with dual booting because the /preload partition is used as the second ROM's /system partition.

However, for those, like me, that do not use dual booting, IMHO, is very useful.

It survives ROM flash and kernel flash as long as you do not full wipe your phone.

My suggestion to you, Dori, is: would it be possible to make this an official option? Either by creating a symlink on /data or mountint the /dev/block/mmcblk0p12 partition directly on /data/dalvik-cache?

It would be great for all of us who are heavy users and do not dual boot.

Thanks!
[Galaxy S II Android Development] dorimanx:
sorry people, i have worked all day, at my job, and made updates to kernel in brakes, so now i am testing it, if all will be ok, then will be online tomorrow.

Sent from my GT-I9100
[Galaxy S II Android Development] nicola1989:
no problem keep your time :D
[Galaxy S II Android Development] biker14:
Bluetooth and SOD

Hi Dori, first of all, awesome work!

I just have one small issue with your kernel, for a few versions now : when I connect the phone to my car, sometimes, not always, I get a SOD on the phone, and the only way I can get it back is to remove the battery. Seems to me that it happens more often if I have already the bluetooth on and start the car, then if I turn the car on and then turn the BT on the phone on, like this it doesn't seem to give me so many issues.

I'm on Slim weekly 5.5 and your kernel 9.20.

Attached the logcat.

thanks for your support!
[Galaxy S II Android Development] dorimanx:
News update!!!

New Kernels 8.21 and 9.21 are ONLINE!

I have found some errors in both builds and fixed them.

Also we now have the latest WIFI driver from SG4 device source tree

Modded by CodeWorks and Me :)

Wifi ver: 1.61.47 (massive update)

we had : 1.28.19

Need to test is HARD... (it's works good for me)

Change Log:

*Pulled updates to main kernel code from 3.10.y kernel.

*Pulled new WIFI driver from SG4 Source + my mods to save power.

*Alucard tuned/fixed/added updates to Nightmare Gov.

*I have removed Interactive CPU GOV from system, it's was unstable.

*I have added code fix to all active CPU govs, that improve stability and performance

*I have removed some old hacks to allow new code to work as should.

*I have cleaned logs from debug alerts, (need more work on some more cleaning)

*Upgraded LINARO to 13.4 GCC 4.7.3 kernel builder.

*Merged lost Sammy functions to video drivers and UMP from SAMMY kernel and from older code from backups.

Video working great and Smooth! even little more FPS on heavy load.

*Tuned Kernel flags optimization, removed dangerous mods. better safe than stuck! (and little less score on bench apps) but you will not see the difference.

*I have found not matching code in 8.XX branch, that exist in 9.XX branch,

seems i missed update, i have merged all that needed, this should restore stability.

OK, time to TEST and report good/bad news.

Thanks for waiting and supporting us. :)

have fun!
[Galaxy S II Android Development] nimasl:
oh yes! Im sorry

please help me I have wifi bug !
[Galaxy S II Android Development] dorimanx:
i have bug in my toilet, do you know what is it?

Sent from my GT-I9100
[Galaxy S II Android Development] nimasl:
:D

sorry!

Im on Omega V20.1 with your 8.21 kernel! last versions was very nice and doesnt have any problem with wifi or something! with this kernel wifi turns on but when it scan it doesnt find any network to connect to them! I sent the debug file in my last post!I think it is from the sg4 wifi driver.you know better!

when I wont to instal I cleaned Int. + wipe dalwik catch + kernel wipe and after that I flashed the kernel.I cleaned wifi lease from STweaks too!

I tested another versions and I didnt hav any problem.so!?
[Galaxy S II Android Development] big_bum:
Kill it with Raid Max!

Ontopic: I'm using a custom kernel on my PC, and since compiling takes a long time, I made a script inspired from your kernel-update-check script from initramfs, which downloads and installs a *deb from this site.

Why I'm saying this? Because I have an idea.

We could modify the kernel-check to make it automcatically download the kernel from one of your sites, so that a user could download the kernel direcly from Stweaks.

Anyway, here is my script for PCs. Basically it compares the version available from that site with the version installed on the computer. If it finds something new, it downloads them.

@nimasl, how about you post this in the non-dev thread? You will have more luck there. The link is in my sig.
[Galaxy S II Android Development] livefortoday:
had 2 freezes with 9.21, normal use

default profile , default settings

changes: bln, mic sound, ad block - only

the log's format is a mess, strange characters every where.

errors:

- failed to suspend noirq: error -11

- Device power.0 failed to suspend noirq: error )11

- Device alarm failed to suspend: error -16

I hope this helps....
[Galaxy S II Android Development] djsky2011:
No freezes for me so far under some serious heavy use, what ROM are u using?
[Galaxy S II Android Development] leo2589:
Hi D-team... Amazing the new 9.21.. Fast and quick..

But one user on my Italian forum has found a bug: the init d scripts doesn't work.. I have tested it with init.d universal free from market with and without the option flagged in stweaks under other tab..

Here are the app : https://play.google.com/store/apps/details?id=com.androguide.universal.init.d

But with this app activated the scripts run at the reboot...

I am on omega v12 aokp 4.2.2

Others users check the problem on 8.21 and Sammy Rom or Original Firmware and the init.d scirpts work.. It seems a problem only for 9.21 and AOKP/AOSP/CM

Sent from Tapatalked JB GT~i91x10²​

​
[Galaxy S II Android Development] manan001:
hi dori with 8.21 on stock allience v8 no freeze.. super fast and excellent battery.. it seems anothr mile stone..
[Galaxy S II Android Development] big_bum:
Hmm, you are right.

I've just made a simple script which writes a file on sdcard, put it in init.d, chmodded it, restarted the phone and the file wasn't there after reboot. The script works fine when manually executed.

The init.d worked last time I tested it. (a long time ago) That's odd.

PS: I'm on RootboxV4.
[Galaxy S II Android Development] iamtheng:
Testing now! :D

Tnx DORI!