yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] D@rekills4:
I am a complete noob at this project....

Just wanted to know if this project has not been completed or if there are still a few things left....

If yes which ones?
[Galaxy 3 Android Development] sharukins:
take a look at the wiki:

http://github.com/tom3q/openfimg/wiki/Status

there's still a lot of work to be done, but openFIMG is already quite stable and can be used for everyday ROM's.

but don't expect HDgames to work
[Galaxy 3 Android Development] tom3q:
Well, maybe there is something wrong with the package for CM7 or CM7 itself.
[Galaxy 3 Android Development] Halco:
tom3q, i have a nooby question ^^

Is this lib can be use on Froyo ? Could we take the lib from CM9 ?

Thanks in advance

EDIT : Oops, didn't see the "Edit" on the first post. Seems to be worked only on CM9 ?
[Galaxy 3 Android Development] moikop:
OpenFIMG works in Froyo, Gingerbread and ICS (and possibly in next releases too). All you need is the userspace module and a kernel with support for it.
[Galaxy 3 Android Development] tom3q:
And a clean Android graphics rendering path without any "fixes" by Samsung, like their surfaceflinger or gralloc binaries.
[Galaxy 3 Android Development] Halco:
Oh .. And hum.. What is the userspace module ? ^^' (i think that the latest version of G3Mod support it i'm right ?)

---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------

So it will dont work on a stock Froyo ROM, is that what u mean ?
[Galaxy 3 Android Development] tom3q:
It might work, but Samsung's libs are likely to cause stability and performance problems.
[Galaxy 3 Android Development] sharukins:
so how is the bugfixing going? :D

will there be a "major" update after bugs are fixed?
[Galaxy 3 Android Development] Halco:
OK Thanks tom3q :)
[Galaxy 3 Android Development] Arakmar:
I tried a while ago in Froyo and it worked just fine. (with tom3q's gralloc though)
[Galaxy 3 Android Development] TearsDontFalls:
Do you have any kernel source or sth for that?
[Galaxy 3 Android Development] Arakmar:
The kernel I posted a while ago (ics24) should work with Froyo too.

Sources are here : https://github.com/Arakmar/G3MOD
[Galaxy 3 Android Development] dhirend_6d:
What about CM7?? Yes?? With new Tom s FIMG?? Please say yes.;)
[Galaxy 3 Android Development] alen1901:
This kernel works with cm7 but i didnt try with openFIMG.

Sent from my GT-I5800
[Galaxy 3 Android Development] tom3q:
I have two minor comments about your version of g3d for OpenFIMG:

- removing "#define DEBUG" at the top is enough to silence dev_dbg, it's a conditional macro, so you don't need to comment out the code to disable it

- currently there is no power domain gating involved so power consumption in some cases may be higher than required; originally runtime pm subsystem was responsible for it, but your kernel is probably too old to support it correctly, so you should think about implementing it similarly to Samsung's g3d module using s5p6442_pwrgate_config and clk_enable/disable and removing all the remaining parts of generic runtime pm from the code.
[Galaxy 3 Android Development] Arakmar:
Ok thanks, I'll look on that.

---------- Post added at 11:20 PM ---------- Previous post was at 11:17 PM ----------

It works with Froyo, CM7 and CM9 not matter if it's OpenFIMG or Samsung's FIMG because the correct module is dynamically loaded.
[Galaxy 3 Android Development] ajay.d96:
does our phone reach totoal score in quadrant more than 1000 points, if so whats the maximum ??

plz provide prior information :confused:

no one to tell me?
[Galaxy 3 Android Development] harkan89:
Quadrant scores really don't mean a thing bro.. There are ways to easily "cheat" quadrant into showing high scores.. Its just the actual performance of the phone that matters.. The one you feel.. And from what I've seen.. It keeps getting better.. Oh and in case you wanted to know.. I've got upto 837 on quadrant and running CM7 alpha 7.1 with.. I think it was Arakmar's kernel.. Either that or the default CM7 kernel by marcellusbe..
[Galaxy 3 Android Development] Sergiales:
Is there any way tu use this driver in froyo?
[Galaxy 3 Android Development] sharukins:
lol, look at arakmars post, three posts before yours

with his kernel toms driver works with every version of android, which is in use at the moment.
[Galaxy 3 Android Development] tom3q:
You can also look at older version of my module which was written for old 2.6.29/2.6.32 kernels and used Samsung's domain gating API:

https://github.com/tom3q/openfimg/b...a4db3071ca2497662122c76/modules/g3d/s3c_g3d.c

I'm not sure if this version was fully correct, but the part responsible for power management (clock, domain and idle timer) should be fine.

EDIT: Despite the possibility of running OpenFIMG with old kernels currently, I still recommend you to consider upgrading your kernel to something reasonable, as I plan to completely rework the kernel interface and move there some of the code running currently in userspace for more efficient context, memory and power management, possibly using the kernel Direct Rendering Manager subsystem, which may not provide the needed functionality in your kernel version.
[Galaxy 3 Android Development] sharukins:
so you mean that G3 will need a later kernel version like 3.0?
[Galaxy 3 Android Development] tom3q:
I might be able to add some compatibility layer, but I can't assure that, because it might turn out to require too much effort. So basically in some forward point of time a newer kernel might become a requirement.
[Galaxy 3 Android Development] sharukins:
well there was a port of 2.6.35 but don't know what happened to it. hope some devs will be able to do a port
[Galaxy 3 Android Development] kylandomos:
I don't think 2.6.35 would be enough as Tom3q' Kernel is based on a Pure 3.0
[Galaxy 3 Android Development] sharukins:
but a kernel port of 3.0 would be easier if the devs already ported 2.6.35
[Galaxy 3 Android Development] tom3q:
Well, it's even possible that 3.0 might be not enough. First I'm waiting for CMA (Contiguous Memory Allocator) to be merged into mainline and this probably won't happen before 3.4, so those changes won't happen before that, plus I will have to wait for Google to upgrade Android kernel to a version with CMA and then upgrade my kernel for Spica to this version.

I just noted that there will be some point in future when compatibility with old kernels might be removed, it's still pretty distant, but this makes pretty good amount of time to work on a kernel upgrade for G3.

As a side note, there is already some support for s5p64xx in mainline, not sure how much, though.
[Galaxy 3 Android Development] kylandomos:
What deserve CMA ? More performance ?

And how much work do you thing it would be needed for port it to 3.X kernel .

Even if our 2.6.32 work in ICS ? Will there be any Improvement ? Like when spica got 2.6.32 ?
[Galaxy 3 Android Development] cdesai:
Well yea, the mainline kernel does have support for s5p64x0, but we dont have a mtd driver yet for our SoC - so someone will first need to make/port one first

On a side note ,I've ported mtd to my galaxy tab (p1-close to Aries), but it just gets stuck on the framebuffer console - do you think it might be stopping the boot as the driver itself is OK - layout also checked.

Sent from my fingerz 2 ur eyez
[Galaxy 3 Android Development] tom3q:
I would risk saying that S5P644x has either the same controller as S3C6410 or S5PC1xx/S5PVxxx. Both types already have drivers.

What does the console say?

EDIT: After a bit of research I confirmed that it's exactly the same OneNAND controller as in S5PC1xx. (See: http://lists.denx.de/pipermail/u-boot/2010-March/069132.html)
[Galaxy 3 Android Development] cdesai:
Nice find there sir! :)

I dont have access to it as i dont have that setup - a friend of mine helped me for getting logs

One strange this is that i had added code to log to sd (in stage1 init) - but i find no logs on the sd

https://github.com/sgt7/p1000-kernel-cm9/blob/mtd/usr/galaxytab_initramfs_files/init#L9

I'll try disabling framebuffer console when i get to a linux box, but i dont think that should afffect this.

EDIT : yea, disabling it did the trick ;)
[Galaxy 3 Android Development] unreal3000:
so we could just use mtd drivers of an s5pc1XX device? sgs?
[Galaxy 3 Android Development] cdesai:
Yea, so we can use the driver from the mainline Samsung kernel (linux-samsung @ kernel.org), but we'ld also need to make a layout file

Something like this :

https://github.com/sgt7/p1000-kernel-cm9/blob/mtd/drivers/mtd/onenand/samsung_p1.h

The first two partitions are the most important as they need to be the exact same size as Samsung set in their FSR drivers, else the bootloader wont be able to communicate with the kernel - rest can be changed

Once moikop gets UART setup, he can just log a normal boot and we'll get the layouts, then some real work can begin! :D
[Galaxy 3 Android Development] unreal3000:
dont forget...we dont even know if it will work on ours like it works on the spica... anyone ripped apart our phone and found serial or somthing?

---------- Post added at 02:20 PM ---------- Previous post was at 02:17 PM ----------

tom3q, how much time did it take to port the first kernel to spica?? and did u face any difficulties? is it fully functional as of now?
[Galaxy 3 Android Development] cdesai:
yea, AFAIK moikop did tell me something about it - we do have a way to get the output, just need the proper setup for that

yes i know tom3q would have a better answer, still i'ld like to say something on this

The mainline Samsung Linux kernel tree does have support for our SoC, so we'ld need to add our board specific code to the kernel (arch/arm/mach-blah/*apollo.c are some examples)

And as talked about earlier, we'ld need to port MTD first (to our current kernel), as the closed-source Samsung FSR module doesnt load on anything else than 2.6.32.9

From what i know, tom3q has done a lot more with the spica 3.0 kernel - https://github.com/tom3q/spica-3.0/wiki

BTW, enjoy a free thanks, clicked by mistake.
[Galaxy 3 Android Development] tom3q:
Yes, my work on the kernel for Spica should be rather considered as bringing up the whole platform from scratch, as support for s3c6410 in the mainline is pretty weak, without most of the features important for mobile devices, like domain gating, advanced clock gating, high resolution timers, sleep mode gpio settings etc., so I had to implement all of them myself.

Also all the drivers for Spica's hardware in original kernel were useless, because of their very bad quality, so things like touchscreen, lcd, battery have completely new drivers in my kernel.

How much time did it take? Hmm, it started with Android kernel 2.6.38 as a base and was first publicly released with 3.0, so should be this time period, about half a year. Still, I was also working on several other things in the meantime (including OpenFIMG), I had several breaks, due to other duties and I was the only person working on it, while I'm generally pretty busy, so my free time can be often somewhat limited.
[Galaxy 3 Android Development] moikop:
There's no need to rip the phone apart... our Galaxy 3 has a FSA9480 chip (Same as in Galaxy S, Galaxy Spica and many other Samsung phones). What we don't have are the resistor values in it's driver header. But since Spica and S have the same values...
[Galaxy 3 Android Development] tom3q:
AFAIK resistor values are defined by the chip, not the driver or particular phone design, although with Samsung everything's possible, like serial lines connected to audio port of the FSA chip or something similar.
[Galaxy 3 Android Development] unreal3000:
hmmm...saw the link... we could use the camera and bt drivers that marcellusbe has developed for ours rite?
[Galaxy 3 Android Development] tom3q:
For camera, you should be able to use the s5p-fimc driver from the mainline and probably my driver for s5k4ca sensor for Spica as it uses the same sensor as G3 (the driver itself is based on the driver from G3 sources).

There are also s5p-jpeg and s5p-g2d drivers present in mainline tree which should be compatible with S5P64xx. s5p-mfc is compatible only with MFC v5.1 found in high-end chips and completely different from MFC v1.0 present in S5P64xx and S3C64xx.

Bluetooth doesn't need any specific driver in kernel, just some helper routines, like power control.
[Galaxy 3 Android Development] unreal3000:
are ur camera drivers complete? like marcellusbe's camera drivers on his cm7 port have black and white preview and no video recording....are u saying that we could just use yours?
[Galaxy 3 Android Development] tom3q:
s5p-fimc is complete, s5k4ca should be too, but I couldn't test it yet, because I'm still working on libcamera compatible with them (s3c-fimc, in my case, which is s5p-fimc modified for s3c6410). Of course those drivers are for new kernels. (Newer means better in this case, because s5p support is being improved actively.)
[Galaxy 3 Android Development] unreal3000:
sry....im not really sure if its the kernel driver problem or somthing else in cm7...
[Galaxy 3 Android Development] Piraze91:
So if i understand, if someone port the kernel to the v3 we will have a best compatibily with openfimg, so more perfs and it can make work some problems like camera,...

Sorry for my bad english :)
[Galaxy 3 Android Development] hillbeast:
Thanks for pointing that out. I just checked myself and you are right, there is an interrupt. Well I wish you good luck on developing a good driver as if we can get the same level of performance as the Spica at least, I will give you money.
[Galaxy 3 Android Development] Skele Drew:
I'm interested in being a part of this...
[Galaxy 3 Android Development] mpbm23:
One question.Do we know in what speed the gpu clock runs?I see in the documents that the maximum is 133mhz.

If it is running on lower clock speed ,overclocking will be possible?
[Galaxy 3 Android Development] marcellusbe:
I beleive it is 166Mhz on G3 and it could be overclocked to 180-190Mhz. At 200Mhz, there are artifacts on the screen on many device I think.

It will be possible with the next fugumod kernel bleedingedge "ultra".
[Galaxy 3 Android Development] tom3q:
Feel free to mail/PM me with any questions.

On s3c6410 it's supposed to run at 133 MHz, i.e. AHB bus clock. Not sure how it is on s5p6442, but probably very similar.
[Galaxy 3 Android Development] marcellusbe:
Well, without full s5p6442 spec from samsung, and with my very limited knowledge about soc, I am maybe wrong. I noticed that MPLL is @166Mhz

<6>S5P64XX: HCLKD0=166.0MHz, HCLKD1=166.0MHz, PCLKD0=83.0MHz, PCLKD1=83.0MHz
<6>mout_apll: source is fout_apll (1), rate is 667000000
<6>mout_epll: source is fout_epll (1), rate is 48000000
<6>mout_mpll: source is mpll (1), rate is 166000000
<6>mout_d0: source is mout_mpll (0), rate is 166000000
<6>mout_d1: source is mout_mpll (0), rate is 166000000
<6>mout_d0sync: source is mout_d0 (0), rate is 166000000
<6>mout_d1sync: source is mout_d1 (0), rate is 166000000

and

in the setting_clocks function, g2d.clk is linked to mpll.

clk_set_parent(&clk_g2d.clk, &clk_mout_mpll.clk);
[Galaxy 3 Android Development] tom3q:
In case of Spica and similar phones, AHB clock is generated synchronously to APLL and MPLL is unused (it can be generated from MPLL in asynchronous mode, but it's not the case here) and G3D clock is driven by AHB. G2D clock is a different thing in s3c6410. No idea about s5p6442.

Anyway, looking at the quoted log, it seems like HCLK is running at 166 MHz, so probably this is it, because HCLK is the clock of AHB bus.
[Galaxy 3 Android Development] marcellusbe:
Ok... so there is a dividor somewhere to have ~133Mhz x 6 = ~800Mhz ..

This can be done on the s5p6442 : HD0CLK could be sync to APLL and HD1CLK stay as it is (at 166Mhz because timers, hrt ... are linked to HD1).

But it seems that overclocking HD0CLK improves 2D/3D rendering (a bit).
[Galaxy 3 Android Development] Skele Drew:
I will after I've digested your attachment tonight.
[Galaxy 3 Android Development] snowcloud:
Hey guys i checked quadrant score and found that g3 has best 2D graphic score in all android handsets.

It is even better than SGS.

But its 3D graphics score is worst in all handsets, even htc magic has better score.
[Galaxy 3 Android Development] dilzo:
Is it even possible to OC the gpu?
[Galaxy 3 Android Development] deskjeti:
Yes in the theory...

But there is no gpu OC for any device.

But there is a GPU OC in development for a device (don´t know for which device)
[Galaxy 3 Android Development] tom3q:
Let's see how much we can get by using optimized drivers first. The original ones from Samsung are really bad, if you look at their leaked sources (to the point that writing new from scratch is easier than fixing them).
[Galaxy 3 Android Development] Rapier07:
Lol... SAMSUCK!
[Galaxy 3 Android Development] unreal3000:
hey guys!

im happy to help and i would like to be a tester!

im fully aware of risk and any damage is only my problem.

so pls sign me up as a tester! tks!
[Galaxy 3 Android Development] tom3q:
I think it's a bit too early for mass tests, but when we get something usable, there will be a public test version.

By the way, it's impossible to damage any hardware by this, it's just like running an application on the phone.
[Galaxy 3 Android Development] unreal3000:
no prob!

but if u need any alpha testing or stress testing do sign me uP!
[Galaxy 3 Android Development] pflorin:
im just imagining this working and with the coming portation of cyanogenmod gingerbread haha f34r th3 31337 samsung galaxy 3
[Galaxy 3 Android Development] mohitgalaxy3:
Any updates???
[Galaxy 3 Android Development] tom3q:
I don't think any quick results should be expected, because I'm the only person working on this project at the moment and I also have a second project, which is more important for me.

I just posted the information here to make people know that such project exists and for people who might be interested in joining it.
[Galaxy 3 Android Development] sharukins:
at some point in the future (maybe kernel 3.4) we will have to port a later kernel because older ones won't be supported by openFIMG anymore. there are already several drivers ported and included in the mainline kernel which will make porting much easiert.
[Galaxy 3 Android Development] KSLevel11:
Devs, could you create the thread which could contain all update.zips, kernels etc with OpenFimg?

Currently, at CM7 thread, ICS thread etc., there are a little mess with links etc.

But, it's only suggestion :)
[Galaxy 3 Android Development] Piraze91:
Thanks, so now we use just some parts of openfimg not all
[Galaxy 3 Android Development] rysi3k:
Where can I find revert zip from openfimg? because in 'cut the rope. I have black screen...
[Galaxy 3 Android Development] tanmoyc:
integrating

HI ,

Can i integrate FIMG 3DSE IN froyo and which kernal contains the graphic rendering module i heard it is present in cm7 and cm9 and akram kernel please help me sir I am using indroid v6 updated it myself (updated system app and kickass kernal and removed supercharger script and add RamHack with kernal G3MOD 2.4.1.
[Galaxy 3 Android Development] sharukins:
try the latest version of openFIMG, cut the rope is running fine on my phone with openFIMG
[Galaxy 3 Android Development] Sergiales:
how can i do it?

Edit: I am in Froyo
[Galaxy 3 Android Development] sharukins:
are you on CM7?

the you should try kyrillos update:

http://xdaforums.com/showpost.php?p=22782297&postcount=500
[Galaxy 3 Android Development] tanmoyc:
hi

I found this zip which can revert FIMG
[Galaxy 3 Android Development] tom3q:
Just pushed two bug fixes to the repository:

- fixed rendering of surfaces with width!=stride (e.g. camera menu)

- fixed a crash when clearing color and depth buffers with scissor width set to less than surface width
[Galaxy 3 Android Development] KSLevel11:
Which Rom you use? Could you share me link with this update?

Edit: I found it ;)
[Galaxy 3 Android Development] sharukins:
I'm using ICS, which already has latest version

for CM7 kyrillos provided and update here:

http://xdaforums.com/showpost.php?p=22782297&postcount=500
[Galaxy 3 Android Development] KSLevel11:
Ok. Thanks. :)

BTW. Is there similar update for froyo? Or any way to use this drivers at 2.2?
[Galaxy 3 Android Development] lebidou:
Hi,

I just built it to test on CM7 and the camera menu doesn't look fixed ! :confused:

EDIT: Ok my bad, it did fix it, sorry.
[Galaxy 3 Android Development] tom3q:
Well, it must be fixed now (at least I don't see any reason why it could be not). Please check whether there aren't any errors on your side.
[Galaxy 3 Android Development] marcellusbe:
it's fixed. good work.
[Galaxy 3 Android Development] unreal3000:
is this the update which increases parformance a bit? which u mentioned a while back?
[Galaxy 3 Android Development] tom3q:
Yes, some of the related changes are there (in fact they have been already since 23rd Feb.). One feature is missing yet, but it should already give some performance boost.
[Galaxy 3 Android Development] ChrisTK:
Hi i am using cm 7 i have to do something else before installing kyrilos open fimg drivers for cm7?
[Galaxy 3 Android Development] alen1901:
Nope. Just apply from recovery, when phone boots up, restart it again. In his update are fimg drivers and related kernel.

Sent from my GT-I5800
[Galaxy 3 Android Development] sonijd:
Froyo

Hi All,

Does this work for froyo...can anyone provide an update.zip for Froyo...Please...Thanks in advance...
[Galaxy 3 Android Development] dogg':
No.

Wysłane z mojego GT-I5800 za pomocą Tapatalk
[Galaxy 3 Android Development] tom3q:
I've got a G3 now (thanks to the donator, I'm not sure if he wants to be named), so I might be able to help with kernel porting and test OpenFIMG on G3 ROMs and do any necessary improvements.
[Galaxy 3 Android Development] moikop:
Awesome. Thanks donator!

You've got the uart jig there? Can you test it? (I'm not getting any output.. not [X]BL, nor kernel) :confused:
[Galaxy 3 Android Development] Piraze91:
Yeahh the work will be faster ! thank you tom3q for your work for our galaxy 3

Envoyé depuis Cyanogenmod 9 build 4
[Galaxy 3 Android Development] tom3q:
Yep, I've got the cable I used for Spica and a level converter based on FT232R. I guess it should work for G3 too.

Btw. Does G3 use the same broken design with single kernel both for recovery and normal boot mode? Also is there some unused space in flash memory? I'm going to add dual kernel and kernel from SD support (at a cost of 0,5-1,0 seconds longer boot) to Spica by using u-boot instead of zImage flashed to main kernel partition and storing real kernels on an unused partition, maybe this could work on G3 too?

Also if you could gather all the information on G3 you've got, it would save me from doing full research on internals of this phone.
[Galaxy 3 Android Development] cdesai:
Yes, bml5 is the only one - same broken design

And I've heard stl9 is unused, not sure though

I've posted a service manual in the general section here, that might help

Sent from my fingerz 2 ur eyez
[Galaxy 3 Android Development] unreal3000:
THANK U DONATOR! wow.....cant wait for the awsome deving u did on spica ba ported on g3 (if possible).......

yes, it uses same kernel for booting and recovery. and yes i think in past research we did find unused flash memory (not sure about it though)....

as far as info of the internal, there really isnt much...it is based on the s5p6440-

http://www.samsung.com/global/busin...ct/application/detail?productId=7114&iaId=835

there really isnt any other info, only service manuals....no dev boards based on it....

for hardware info, look here-

http://xdaforums.com/showthread.php?t=1156243

tks dharam, there is phone specific hw info...
[Galaxy 3 Android Development] andreapier:
This is awesome!

It is not to hurry, but after you are done with openfimg i suggest to start porting 3.x kernel so that our phone is perfectly aligned with spica.

Thank you so much!
[Galaxy 3 Android Development] dogg':
Thank you very much donator. :) :D