yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] ChriZz12:
Dear developer,

Can you please compile the lollipop version of your kernel for the galaxy s captivate? i managed to port some roms from the i9000 forums to my captivate, i used a lollipop kernel from my device's forums and it works fine, but when i try to flash a kernel from the i9000 my phone's rotation will not work right, sound and keys also won't work right. I just need a better kernel so my device can work a bit smoother. Thank you for understanding.
[Galaxy S I9000 Android Development] Audiracecar90:
u cant flash kernel of i9000 to ur device. the problem occurs due to kernel support so if u want to make good and smooth rom means try to port Arom or full advance both are good:)
[Galaxy S I9000 Android Development] Coldwindofnowhere:
I will give it a try, but since i don't own this device, i wont be able to test anything.

[MENTION=6943544]ChriZz12[/MENTION] here it is :

http://www102.zippyshare.com/v/A0XQogE3/file.html
[Galaxy S I9000 Android Development] ChriZz12:
Thank you very much sir! I appreciate what you have done. This kernel works great on my device :) .
[Galaxy S I9000 Android Development] falconscrest123:
[MENTION=6794010]Coldwindofnowhere[/MENTION] as you know ive been trying to build a kernel for my device. I have built countless boot images, but all of them compile without any errors. However, all those boot images results in either a boot loop or a bricked device. If you take some time to guide me in the right direction that would be really helpfully. Sorry for spamming your thread but i really need help
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Well i don't know how to help you tbh ....

Make sure to read this, lots of useful stuff there.

Download all the needed dependencies for your device and then execute in the following order :

. build/envsetup.sh
breakfast galaxysmtd
mka bootimage
[Galaxy S I9000 Android Development] udhy:
Could you port this kernel for cm13 with CMA technology?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Unless you are a developer and want it for debug, i'm not sure if it's a good idea to use CMA kernel in it's state ... as stated a few posts above, it's not really stable and unfinished. So if some of you want to try it for CM i'll post a build but be warned that it won't be a stable as the usual kernel.
[Galaxy S I9000 Android Development] jupiter5700:
Coldwindofnowhere , it is possible to add Call Recording feature to this wonderfull kernel?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Have you tried this app : https://play.google.com/store/apps/details?id=com.nll.acr ?
[Galaxy S I9000 Android Development] udhy:
Hi,I am using latest 5.1kernel unfortunately I could not able to play 720p video.

I set big memory default
[Galaxy S I9000 Android Development] Coldwindofnowhere:
What rom are you using ? What media player ? Which Bigmem mode ?
[Galaxy S I9000 Android Development] udhy:
Omni 5.1 ROm ,system media player, 'default' bigmem mode
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Have you tried to reboot, to make sure that bigmem is enable and try again ? Also, was it working with older kernel releases ?
[Galaxy S I9000 Android Development] udhy:
OK ,I'll try
[Galaxy S I9000 Android Development] artyfarty:
dear developer

I've tried to install your 6.0.1 kernel to this rom. the rom is AOSP / OMNI

I have the encryption error when the rom finish his boot. The only way is to reset the phone, but there is no way to boot the rom completely.

thanks.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Well as far as i know this rom isn't aosp based. About your issue, i will try to take a look at it, have you tried the same kernel with sooti's omni builds ?

Note that i tested this kernel with my own personal omni 6.0 builds so there might be something different in the rom you're using.
[Galaxy S I9000 Android Development] artyfarty:
tried only with this rom.

another guy have the same problem.

thanks for the support.
[Galaxy S I9000 Android Development] nanico:
Can you compile same kernel for GT-P1000?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
No, i don't want to compile for other versions than 5.1.1
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Strange, i haven't got any error during the build ... i'll try again next week
[Galaxy S I9000 Android Development] althafvly:
Or can you add battery life extender in 5.1.1
[Galaxy S I9000 Android Development] Coldwindofnowhere:
I will see, if it's not too difficult to implement, i will try

Edit: seems kinda easy to add, i'll give it a try tonight
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Guys, it's working : http://www63.zippyshare.com/v/MWrjPI07/file.html

Tell me if you have any issues

PS: OP updated
[Galaxy S I9000 Android Development] althafvly:
Vibrant or s?

---------- Post added at 04:08 AM ---------- Previous post was at 04:06 AM ----------

And what working.. I didnt :what:get it
[Galaxy S I9000 Android Development] Coldwindofnowhere:
BLX is working and this build is for S
[Galaxy S I9000 Android Development] althafvly:
Working

You are working so fast in the kernal

...

You have a great future . good luck:thumbup:

---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------

Also add more future :)
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Am i the only who cannot archive higher CPU frequency than 1200 mhz without having reboots on 5.1.1 ?

I think i found out why (if some dev is curious) :

From /arch/arm/mach-s5pv210/cpufreq.c

static struct cpufreq_frequency_table s5pv210_freq_table[] = {
{OC0, 1400*1000},
{OC1, 1300*1000},
{OC2, 1200*1000},
{OC3, 1100*1000},
{L0, 1000*1000},
{L1, 800*1000},
{L2, 400*1000},
{L3, 200*1000},
{L4, 100*1000},
{0, CPUFREQ_TABLE_END},
};

static struct regulator *arm_regulator;
static struct regulator *internal_regulator;

struct s5pv210_dvs_conf {
unsigned long	arm_volt; /* uV */
unsigned long	int_volt; /* uV */
};

#ifdef CONFIG_DVFS_LIMIT
static unsigned int g_dvfs_high_lock_token = 0;
static unsigned int g_dvfs_high_lock_limit = 6;
static unsigned int g_dvfslockval[DVFS_LOCK_TOKEN_NUM];
//static DEFINE_MUTEX(dvfs_high_lock);
#endif
const unsigned long arm_volt_max = ARMVOLTMAX;
const unsigned long int_volt_max = INTVOLTMAX;

static struct s5pv210_dvs_conf dvs_conf[] = {
[OC3] = { /* 1.4GHz */
.arm_volt = DVSARM0,
.int_volt = DVSINT0,
},
[OC2] = { /* 1.3GHz */
.arm_volt = DVSARM1,
.int_volt = DVSINT0,
},
[OC1] = { /* 1.2GHz */
.arm_volt = DVSARM2,
.int_volt = DVSINT1,
},
[OC0] = { /* 1.1GHz */
.arm_volt = DVSARM3,
.int_volt = DVSINT1,
},
[L0] = { /* 1.0GHz */
.arm_volt = DVSARM4,
.int_volt = DVSINT2,
},
[L1] = { /* 800MHz */
.arm_volt = DVSARM5,
.int_volt = DVSINT2,
},
[L2] = { /* 400MHz */
.arm_volt = DVSARM6,
.int_volt = DVSINT2
},
[L3] = { /* 200MHz */
.arm_volt = DVSARM7,
.int_volt = DVSINT2,
},
[L4] = { /* 100MHz */
.arm_volt = DVSARM7,
.int_volt = DVSINT3,
},
};

{OC0, 1400*1000},

{OC3, 1100*1000},

[OC0] = { /* 1.1GHz */

[OC3] = { /* 1.4GHz */

What ????? :eek:

I've just reversed all the values and i'm currently running at 1400 mhz without any problem
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, very interesting.... Looks like you might be on to something there.

You can look at https://gerrit.omnirom.org/#/c/8133/ for where that code appeared.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Working on live OC right now

Edit : i can reach 1596 mhz (not really stable unless you go crazy with voltages)
[Galaxy S I9000 Android Development] MatteoB92:
1512mhz seems interesting on our device, I could be interested into testing

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S I9000 Android Development] Coldwindofnowhere:
You can even get more, 1512mhz is "only" 108% OC. I'll send you a test version in an hour or so but don't play too much with live OC, it can fry your device instantly :angel:
[Galaxy S I9000 Android Development] MatteoB92:
What I remember from Semaphore times is that my device doesn't swallow liveOC, maybe with your kernel things are changed.

But what do you mean with 'fry'? A reboot doesn't recover the situation?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Um i'm gonna give you an example: with my device i cannot go higher than 113% OC, if i put 130% OC my device will reboot (hopefully) but if i do this too much it can damage the hardware. Of course if you have a bit of common sense there won't be any problem ^
[Galaxy S I9000 Android Development] Trainer_H:
I have the same problem. my phone is not stable if i use a higher freq than 1200MHz.

Do you change the code in the new kernel?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Yeah download the test build (in the original post) and tell me if it's working for you
[Galaxy S I9000 Android Development] MatteoB92:
Obviously I think that someone could not start from the top, I'll test step by step.

What do you use to ensure phone is stable?

113% is 1582, not bad considering also RAM and GPU go faster due to the liveOC!

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Um any benchmark should be ok, also 720p video decoding is really CPU intensive too. Also, take a look at the temp, if it's > 50 degrees, you should let cool down a bit the phone
[Galaxy S I9000 Android Development] Trainer_H:
Thank you. i test it, and for now i don't get any problem.

Do you also want to add CMA?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Yes i would be a nice feature but i have no clue how to implement it
[Galaxy S I9000 Android Development] Coldwindofnowhere:
nevermind, solved
[Galaxy S I9000 Android Development] Trainer_H:
In the test build it works for me. Now i can usw 1,4GHz.

Tanks
[Galaxy S I9000 Android Development] fathi48:
Hi Coldwindofnowhere, after change the OC you should off and then on DevilTools to show the correct frequencies

sorry my bad English
[Galaxy S I9000 Android Development] phil_greg2001:
Hello all,

For me it's stable to 1,2Ghz :(

Many thanks Coldwindofnowhere.

:cowboy:
[Galaxy S I9000 Android Development] Trainer_H:
Do you try the test build?
[Galaxy S I9000 Android Development] phil_greg2001:
Yes, Kernel_CV :cyclops:
[Galaxy S I9000 Android Development] fathi48:
in 1.4Ghz the phone restart in the implementation of some software

I use kernel_CV

Many thanks Coldwindofnowhere.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
You should try to tweak the voltages a bit. Phone are usually reacting differently when it comes to overclocking: for example, i'm running at 1.4Ghz for 4 days and i haven't a single reboot (with daily usuage)

edit : was it working with the old kernel ?

[MENTION=3110786]phil_greg2001[/MENTION] & [MENTION=5192638]fathi48[/MENTION] try modifing the voltages like that :

ARM Voltages

1400 mV // 1400 MHz

1375 mV // 1300 MHz

1350 mV // 1200 MHz

1300 mV // 1100 MHz

1275 mV // 1000 MHz

1200 mV // 800 MHz

if it's still not working try to tweak the INT voltages but be gentle because it's really sensitive
[Galaxy S I9000 Android Development] althafvly:
Lollipop uses battery a lot. Anyway to get a good battery backup?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Um it's kinda off topic but yeah if you want to save your battery, decrease your cpu frequency, try to add more udervolting and unistall apps you don't need. You can also check what's draining your battery by installing BetterBatteryStats
[Galaxy S I9000 Android Development] phil_greg2001:
It doesn't work for my phone when I push to 1,3Ghz... The phone reboot :crying:

Thanks Man :cowboy:
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Um try to decrease INT voltage of the 1300 mhz step to 1175 mV instead of 2000 mV.

By the way have you already sucessfully oc your phone to 1300 mhz with another rom/ kernel ?
[Galaxy S I9000 Android Development] (°_o):
[MENTION=6794010]Coldwindofnowhere[/MENTION] The 1400Mhz not getting overclocked on liveoc happens on different oc values in my testing.
[Galaxy S I9000 Android Development] phil_greg2001:
I never have sucessfully OC upper 1,2Ghz... :(
[Galaxy S I9000 Android Development] althafvly:
Can I enable fast charge in 5.0.2. With root?

---------- Post added at 11:50 AM ---------- Previous post was at 11:45 AM ----------

Or can u add only fastcharge in 5.0.2 ?.

It will be great. Coz I am using RR. modified it . good performance. stock ram other
[Galaxy S I9000 Android Development] Coldwindofnowhere:
No , i already answered you, i don't want to modify the 5.0.2 kernel
[Galaxy S I9000 Android Development] phil_greg2001:
Hi Coldwindofnowhere,

Is it possible to add the patch for InCallUi like this :

http://xdaforums.com/showpost.php?p=62951784&postcount=14

or this

http://review.cyanogenmod.org/#/c/57224/

:cool:
[Galaxy S I9000 Android Development] Coldwindofnowhere:
If you have not successfully OC with devil or glitch kernel i guess you have no luck: it should be hardware related issue
[Galaxy S I9000 Android Development] phil_greg2001:
:crying::crying::crying:
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Sure, i'll give it a try asap

I'm happy to announce you that all of these are already included i the latest onmi source ^^
[Galaxy S I9000 Android Development] jupiter5700:
It will be nice if you also try to add bigmem values 2 and 3 (408 and 440mb) from devil kernel!:)
[Galaxy S I9000 Android Development] fathi48:
Hi Coldwindofnowhere, your latest rom (2015.10.14) works fine for me

Thank you
[Galaxy S I9000 Android Development] Coldwindofnowhere:
New build coming soon with the following changes :

- O3 optimizations

- VR I/O scheduler

- Live OC support

- Touchwake

- BLN

- 408 and 440mb bigmem values

I will update the link in the OP and be warned, some bugs are still present

Link up : http://www43.zippyshare.com/v/Mgzh5R4r/file.html
[Galaxy S I9000 Android Development] jupiter5700:
Wow! Cool features list! I wil try this kernel some later, thank you!:cowboy:
[Galaxy S I9000 Android Development] phil_greg2001:
Really great kernel !!!

I have 399 Mo RAM :)

Have you put in the incallui patch ?

Many thanks.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
This is completely normal. Go to /sys/kernel/bigmem/enable and modify the value to:

0, for no bigmem

1, for XLmem (398 mb)

2, for bigmem (407 mb) breaks 720p

3, for max ram (430 - 440 mb) breaks camera

And no i haven't because it's already included in the Omni rom :p
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, do you want me to edit DeviceSettings to have the options for each one? (Or you could probably do it, its fairly simple).

Would require re-building the entire ROM.

Currently the toggle will enable XLmem and XLmem only
[Galaxy S I9000 Android Development] VENESOLANITO:
no wonrking for me on CodeRom 5.1.1 :confused: :(
[Galaxy S I9000 Android Development] jupiter5700:
I think that DevilTools will cood switch mem properly.Link to DevilTools thread.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Yes, if you find the time to do it, it would be awesome and about rebuilding the rom it's not a problem .
[Galaxy S I9000 Android Development] Coldwindofnowhere:
I don't see where is your problem, even if you have errors in twrp (these are not kernel related) you're running the latest version of the kernel
[Galaxy S I9000 Android Development] phil_greg2001:
I cannot set "2" in the enable file with text editor or with DevilTools :eek:

Have you any idea ?

:cool:
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Run these commands in a terminal emulator :

su
echo 2 > /sys/kernel/bigmem/enable

If it's still not working then i don't know. Anybody else is experiencing the same issue ?
[Galaxy S I9000 Android Development] phil_greg2001:
I try asap but when I modify with Devitools, I select 3, for max ram (430 - 440 mb) breaks camera, it works :eek:

:cowboy:

---------- Post added at 02:29 PM ---------- Previous post was at 01:39 PM ----------

It doesn't work :crying:
[Galaxy S I9000 Android Development] xc-racer99:
Alright, change is uploaded here. Haven't tested compiling it myself, but there shouldn't be any reason why it won't work.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Many thanks, i will try to make a build tonight

Edit: rom building right now, btw i have successfully added voodoo colours to the kernel
[Galaxy S I9000 Android Development] Trainer_H:
If you finished the upload, please share the link.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Man it takes up to 600 min to build a rom with o3 optimizations (considering i'm cleaning the output and ccache at each build) ,so be a little patient.

Edit: New build is up ! I will create a new thread soon
[Galaxy S I9000 Android Development] Trainer_H:
which Kernel Version is include in the new Rom from 16.10?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
The latest one, Kernel_VC.zip with voodoo colour included
[Galaxy S I9000 Android Development] althafvly:
Is the 440mb works?? And it will break camera??
[Galaxy S I9000 Android Development] Coldwindofnowhere:
yes for both
[Galaxy S I9000 Android Development] Trainer_H:
your rom has a small bug. If you try to restart to recovery, it restarts normal without showing TWRP.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Yeah i'm aware of it, it's rebooting into system instead of into recovery if you choose 430mb of ram ... FIXED i will upload a build tomorrow
[Galaxy S I9000 Android Development] xc-racer99:
Alright, think I found it (haven't tested as I don't have an i9000 but a T959P)

In /usr/galaxysmtd_initramfs_files/init, you have

if busybox test -e /cache/.startrecovery || \
busybox grep -q bootmode=2 /proc/cmdline || # normal mode
busybox grep -q bootmode=5 /proc/cmdline || # xl mem
busybox grep -q bootmode=9 /proc/cmdline || # big mem
busybox grep -q bootmode=13 /proc/cmdline; then # no cam

whereas you should have

if busybox test -e /cache/.startrecovery || \
busybox grep -q bootmode=2 /proc/cmdline || \# normal mode
busybox grep -q bootmode=5 /proc/cmdline || \# xl mem
busybox grep -q bootmode=9 /proc/cmdline || \# big mem
busybox grep -q bootmode=13 /proc/cmdline; then # no cam

With slashes at the end of each line which then tells it to read as one line as opposed to individual lines.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Um it might be this, i'll try to make a build asap also, i've found something else :

// Only write bootmode when less than 10 to prevent confusion with watchdog
// reboot (0xee = 238)
if (bootmode < 10) {
size += sprintf(new_command_line + size, " bootmode=%d", bootmode);
}

since 11 & 13 > 10 it might be this too
[Galaxy S I9000 Android Development] xc-racer99:
Good point. However, is reboot to recovery totally broken or only when in certain modes (ie works in bigmem but not in nocam)?

Edit: Maybe there's multiple problems. If you look at https://github.com/DerTeufel/samsung-kernel-aries/blob/cm-10.2/arch/arm/mach-s5pv210/mach-aries.c (Devil kernel) you can see that the limit has been increased to 15 from 10.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
The problem was only present in nocam mode, i've increased the bootmode limit and now it seems to work on my device. I will still try to add the slashes tomorrow to see if it changes anything. So yeah i guess the issue is solved, i will upload a build tomorrow. Many thanks for your help man :)
[Galaxy S I9000 Android Development] yah7733:
why I get 426 mb . ?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Give me the output of dumpsys meminfo (enter this command in a terminal with root privileges) please
[Galaxy S I9000 Android Development] (°_o):
Is anyone else having rendering issues on Bigmem 3..?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
What do you mean by rendering issue ? can you attach a screenshot ?
[Galaxy S I9000 Android Development] yah7733:
sorry . dont what to do .thank
[Galaxy S I9000 Android Development] (°_o):
Hmm . it only happens during boot .. blue/pinkscribbled lines... so cant take screenshot....

also sometimes after.... boot

and mine also show 426 mb... i will upload the output soon...
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Um strange, and it's only happening i the nocam mode right ? I already had the same kind of issue but it was because of live OC (bus speed was too high). The thing i don't understand is that the 3rd bigmem mode only sets to 0 kB the mem allocated to the camera driver, normally this won't affect the video driver .

Also thanks, for taking the time to upload the output ^^ I'm getting 437 mB of ram on my device with the same kernel version so without any log i can't understand why some people get 426 mB
[Galaxy S I9000 Android Development] fathi48:
Voltage control in performance setting of this room not working on the other hand when you change voltage and press apply values bottom nothing happens

Sorry my bad English
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Use NSTools or DevilTools to modify the voltages
[Galaxy S I9000 Android Development] (°_o):
Yes only in no cam mode. I havent set OC.

Output of dumpsys meminfo

http://paste.omnirom org/view/b28311d1
[Galaxy S I9000 Android Development] Coldwindofnowhere:
For the rendering issue, i think this is related to voodoo colors, try this :

- download and install Voodoo Sound v3.1.2.2.apk

- go to screen RGB multipliers

- hit the reset button

- reboot

If you still have the issue then it's something else
[Galaxy S I9000 Android Development] (°_o):
Maybe because 436812/1024 =426.57...

I will try that. .
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Yep sorry xD About the screen issue, my screen was flickering too when all the RGB values were maxed out
[Galaxy S I9000 Android Development] (°_o):
1000 or 1024 units.. always confusing...

mine only happens during boot.. in Samsung logo ... not a problem tho.. i rarely restart my device...

and how bout adding OTG, is it possybul?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Well if it's only during the boot it's not that annoying, but give a try to change voodoo colors setting, it might help.

And for the OTG, i will see if it's possible

Edit : it seems to be already enabled

CONFIG_USB_S3C_OTG_HOST=y
CONFIG_USB_DWC_OTG=y

But i don't know if it's working properly

https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/commit/b8c357a7bb54facee780f7367ab429ca932761ee
[Galaxy S I9000 Android Development] althafvly:
Can you add tweaks like mackay kernal. Coz it gives good battery life for device

If possible
[Galaxy S I9000 Android Development] jupiter5700:
Coldwindofnowhere

It will be great if you try to revert TV-out support!
[Galaxy S I9000 Android Development] xc-racer99:
Unless things have changed recently, you will need to follow the instructions at http://xdaforums.com/showthread.php?t=1450298 to get OTG working.

With regards to TV-Out, its not the kernel that's the issue but its the userspace. The proprietary blobs for it use functions that have since been removed from android. Adding these back in require a lot of work (but should be doable if one knows how).
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Yeah but as [MENTION=5414656]xc-racer99[/MENTION] stated, it's way too much work for a (pointless imo) feature
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Can you be a bit more precise please ? i don't think there is/are feature(s) that magically gives you more battery life. LP roms are way more battery consuming than KK ones, i think it's the main problem.
[Galaxy S I9000 Android Development] MatteoB92:
If anyone could help you it would be a great thing (also I if anyone teach me), I and jupiter aren't the only ones to request that feature :)

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S I9000 Android Development] Coldwindofnowhere:
I know right but as you can see the dev scene on the i9000 is kinda dead currently :( I'm just a student so i'm not the most experinced developper and i don't have a lot a free time. Of course if some dev want to help me, it will be a pleasure for me to work with him :)