[OUTDATED] [Dev] Android 2.3 Gingerbread for Samsung Spica i5700 [SOURCE]

**LeshaK** · 12-29-2010, 08:56 PM

My first 'working' version of Android 2.3 for i5700
https://github.com/organizations/SamdroidMod

How to get source:

Code:

repo init -u git://github.com/SamdroidMod/android.git -b gingerbread
repo sync

How to build

Code:

. build/envsetup.sh
choosecombo

1
1
spica
eng

Code:

make

First BIG Problem - Display, can't use 3D drivers (fimg)

**nebkat** · 12-29-2010, 11:10 PM

Is the display problem related to this Issue 3 - gles6410 - Gingerbread's black screen - Project Hosting on Google Code ?

**mik_os** · 12-29-2010, 11:19 PM

Yes. I create issue there because probably tom3q's driver is the only which we can use for gingerbread.

**tom3q** · 12-30-2010, 03:14 PM

There was a suggestion on my project site (I believe that it was by mik_os) that Gingerbread works correctly with my 2D drivers - gralloc, copybit, g2d kernel module and kernel patches. May be worth trying to provide some basic graphics acceleration on 2.3.

**LeshaK** · 12-30-2010, 03:17 PM

Originally Posted by nebkat

Is the display problem related to this Issue 3 - gles6410 - Gingerbread's black screen - Project Hosting on Google Code ?

yes, but with gralloc, copybit and "0 0 android" in egl.cfg
1. very slow
2. sometimes display turn off and need to switch off/on the phone

**tom3q** · 12-30-2010, 03:29 PM

Originally Posted by LeshaK

yes, but with gralloc, copybit and "0 0 android" in egl.cfg
1. very slow
2. sometimes display turn off and need to switch off/on the phone

Point 1 should not be the case. On 2.2 UI is usually faster than on 3D drivers (considering that my drivers are installed correctly).
Point 2 seems strange, I have never experienced similar issues with my drivers (I use them on my phone instead of the broken Samsung drivers).

**LeshaK** · 12-30-2010, 06:00 PM

Originally Posted by tom3q

Point 2 seems strange, I have never experienced similar issues with my drivers (I use them on my phone instead of the broken Samsung drivers).

I think problem not in your driver or in driver from samsung,
after display turn off - top

Code:

User 8%, System 91%, IOW 0%, IRQ 0%
User 67 + Nice 0 + Sys 748 + Idle 0 + IOW 0 + IRQ 0 + SIRQ 0 = 815

  PID CPU% S  #THR     VSS     RSS PCY UID      Name
 1992  78% S     5  22452K   4668K  fg media    /system/bin/mediaserver
 2001  11% S    46 136212K  34620K  fg system   system_server
 1993   1% R     3   3888K    676K  fg root     /system/bin/netd
 1895   1% R     1   1256K    580K  fg bluetoot /system/bin/dbus-daemon
 1888   1% R     3   3916K    700K  fg root     /system/bin/vold
 2299   0% R     1    908K    380K  fg root     top

**tom3q** · 12-30-2010, 06:05 PM

Still, it shows 91% CPU usage in kernel mode.
There is a bug in framebuffer driver (in kernel) which seems to turn off the screen and crash when something is trying to change the video mode. Maybe it is related?