yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] prabhuthelegend:
hmm lets hope for the best then..

by the way i am planning to purchase motorola atrix 4g with a good deal.It's having dual core as well as nvidia tegra chipset.

Some say motorola is not a good selection compared to samsung..any thoughts on that?? sorry for the offtopic..!
[Galaxy 3 Android Development] unreal3000:
sadly, if tom3q leaves his deving on these drivers, their is no one here who can continue them. since it requires a person with a very specific skill set, their are very few who can, and probably no one in the g3/spica community. no disrespect to our other devs...u guys are awsome! but im sure even u would agree with me.... making gpu drivers requires in-depth opengl knowledge and many other things..
[Galaxy 3 Android Development] tom3q:
Don't worry yet. I'm going to do my best to convince them that I should be allowed to work on this project.
[Galaxy 3 Android Development] VinC0deur:
OpenGL ES 3 has been announced (Source: http://www.presence-pc.com/actualite/opengl-es-48374/ [French post, sorry]), if you obtain an approbation from your employer you will be work on 2 or 3 version?
[Galaxy 3 Android Development] Spitlebug:
I suppose you could make a case that we are customers. Even though I love this little phone, I'll probably be buying another Samsung phone in the very near future anyway.

Supporting customers means brand loyalty.
[Galaxy 3 Android Development] hillbeast:
I will agree that I will have no idea how to do it, mainly because I'm a Windows fagboy. I can't be bothered learning OpenGL as I see it as an inferior substitute for DirectX that doesn't work anywhere near as well, and that won't help me wanting to make drivers...

And if anyone disagrees with me, then I welcome your opinion, but I will maintain that Direct3D is on a whole different level to OGL.
[Galaxy 3 Android Development] :
Good
[Galaxy 3 Android Development] protomank:
You should check Valve's Linux blog ;)

Anyway, this WAS true until recently, as OpenGL was frozen in time and direct3D had constant updates and all innovation focus was on D3D. Lately, openGL was bought by a new group, that is pushing it forward, and some new techniques are already being implemented first on it, then later on D3D. I think D3D was superior when it was the whole directX, with joystick, keyboard, sound and all integrated. Now that it became mainly graphics, as OpenGL, I do not see any big advantages on one or other technology over the other one.
[Galaxy 3 Android Development] cdesai:
They still use exynos chips in their international devices(with exynos4412-s5e4412 being the latest, used in Galaxy S3), Qualcomm is used just for the U.S. variants due to radio restrictions, and in the cheaper phones as well.
[Galaxy 3 Android Development] tom3q:
I have an interesting counter argument: http://www.phoronix.com/scan.php?page=news_item&px=MTE1MjI . It's just for your information, as I'm not biased towards any of the interfaces if it's about desktop ones. For mobiles there is no good alternative for OpenGL ES.
[Galaxy 3 Android Development] hillbeast:
I'm referring to the budget models like the G3 or the Spica where Samsung put some effort in. Now they pump out crap like the Galaxy Ace or the Galaxy Y. The display on the Y is nasty. Terrible DPI and disgusting colours. Its no match for the G3.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] Szaby59:
I don't think Galaxy Ace is crap, only cpu is bad because only arm v6.
[Galaxy 3 Android Development] hillbeast:
It has a Qualcomm CPU which are notoriously bad. If you think our phone is bad for lack of documentation, take a look at Qualcomm.

Sent from my Serenity Galaxy S2
[Galaxy 3 Android Development] Spitlebug:
This pretty much sums up my experience with Qualcomm as well.
[Galaxy 3 Android Development] aarrun:
tom moikpop and hillbeast 1 small ques.... can u plz tell what actual gpu does our phone has? exactly what is it?
[Galaxy 3 Android Development] tom3q:
Samsung FIMG-3DSE, revision 1.5.3.
[Galaxy 3 Android Development] tom3q:
I was talking with my boss today regarding my personal open source contributions related to Samsung hardware and he told me that there shouldn't be any problems with OpenFIMG, although to be safe I will have to let him look through any changes and officially accept them before publication. Those which can potentially reveal any sensitive information will have to go through Korea, but there shouldn't be any problems.

So basically the project is still alive.
[Galaxy 3 Android Development] vivekchamoli:
Great news :) Thanks
[Galaxy 3 Android Development] andreapier:
@tom3q AND TO NO ONE ELSE

This is a great news!

I know you are busy and no one here should ask you anything but still i'll give this a try:

I really hope one day to see this phone run at his real potential, and this won't ever happen without proper complete graphic drivers.

So here is my own request: when you have time try hard to complete this project so that your big knowledge helps us in having a better phone (not less than we paid for)!

Ps: to every one that think that answering "why don't you it by yourself?": i don't know how to do it, otherwise i would have tried. Anyway, i'm studying hard linux kernel and i hope to be of help one day or another... but it is a hard task, so don't spanthe thread!

Instead, motivate tom3q with little donations!
[Galaxy 3 Android Development] tom3q:
Well, that's what the whole effort is for, to complete this project :) .
[Galaxy 3 Android Development] sarthak.killedar:
OpenGL ES 2 or 3 gonna be there? Or omly 1.1?
[Galaxy 3 Android Development] amarendar94:
Heyyy...OpenGLES 2.0 is little far I think.

OpenGLES 1.5 would be implemented first.
[Galaxy 3 Android Development] aarrun:
tom3q.... is dual (mali 400 gpu) good or (mali and opengl 2.0)?....
[Galaxy 3 Android Development] tom3q:
Hardware support is required for particular OpenGL ES versions. Our GPU supports at most OpenGL ES 2.0. For now I have plans only for complete implementation of OpenGL ES 1.1 in OpenFIMG, but OpenGL ES 2.0 isn't impossible.
[Galaxy 3 Android Development] austin266:
Can we expect any updates from ur work? @tom
[Galaxy 3 Android Development] tom3q:
Yes, but not very soon. As usual, no ETAs.

I have a series of changes planned, but I didn't have time to work on them yet.
[Galaxy 3 Android Development] andreapier:
Hey, tom3q i'd like to know if you still plan to complete the project one day or another... It has been stopped from quite a long time now...

And yes, for everyone that is going to answer "developers do develop in their free time" and stuff like this: i'm fine with no ETA. Really, no ETA is good but kindly asking for info is good to, so do not bother with such an answer.

I think tom3q and all other developers are able to answer themselves!

Thanks for taking the time to read this and answer (maybe)!
[Galaxy 3 Android Development] MicroGeek:
He said he was waiting for Samsung to confirm that he is allowed to carry out this project since he works for them. I can't remember the reason though.
[Galaxy 3 Android Development] austin266:
@tom

I think... We need some good news from u... May be an easter egg soon abt the project
[Galaxy 3 Android Development] tom3q:
Yes, I still have plans for this project. I can't say when I will have an opportunity to pursue them, though.
[Galaxy 3 Android Development] andreapier:
Great to hear this! Thanks!
[Galaxy 3 Android Development] MnauelKetnas:
Hey tom3q,

sorry for asking but is there any progress with Samsung,

any chance with confirming ?
[Galaxy 3 Android Development] tom3q:
I'm not sure I understood you correctly, but I already received green light for continuing my open source projects (I thought I already stated it). However I don't have time to work on them at the moment.
[Galaxy 3 Android Development] MnauelKetnas:
Ok thanks, perhaps I missed a post
[Galaxy 3 Android Development] sad96:
But are there any chances that we will get working 2d/3d soon? Openfimg presented in many ported roms nowadays (cm7/cm9/cm10 and based on them). And It makes them useless. Thats why most of us have to stay on old froyo...

Sent from my ASUS Transformer Pad powered by JellyBean
[Galaxy 3 Android Development] tom3q:
2D and 3D is already working in OpenFIMG version used in G3 ROMs. There are only problems with some games and several more demanding OpenGL apps, but it's definitely far from being useless and in some cases much further from being useless than with original driver (i.e. CM9 and CM10).

If several 3D games not working makes phone useless for you then you should probably change your phone to one of available high end phones or buy a portable game console.
[Galaxy 3 Android Development] sad96:
Hehe... SpeedX 3d works fine on 2.2 and without textures on cm7/9/10. The same situations with angry birds althought it's 2d game. They don't need high end devices. :confused:

Also openfimg causes problems with launcherpro.

Anyway we all hope that this project will be finished as soon as possible because not all people here can allow themselves to buy sgs3/note2/one x+ etc...:rolleyes:
[Galaxy 3 Android Development] tom3q:
I think you are not using the same OpenFIMG as me. On Spica (which has higher screen resolution and so needs more video memory) OpenFIMG can run SpeedX 3D and patched Angry birds with normal textures and there isn't any single problem with LauncherPro. There is no reason it should be any worse on G3. Maybe you should try another ROM, because not every ROM for G3 might have OpenFIMG integrated correctly.

Anyway, games aren't the goal of this project, but rather the ability to run clean Android builds and versions newer than 2.2 on this GPU (as opposed to the original driver which needs many workarounds in the ROM and cannot run Android 2.3 and newer) and this goal is already met. Another goal is reducing the CPU overhead of graphics rendering (which was huge on original driver) to the necessary minimum and this is met too. This driver can be successfully used on a daily basis, assuming that you don't want to use your (low-end) phone as a gaming console, but as a phone.
[Galaxy 3 Android Development] sad96:
Hm.. Which rom exactly? These problems presented on clear cm7..
[Galaxy 3 Android Development] tom3q:
Was it latest CM7, alpha 8.3? It may also depend on particular kernel. I don't know which one (if any) works correctly with OpenFIMG on G3, because I don't use G3 daily and I don't have time to do any tests at the moment. I guess you should talk about this with G3 ROM developers.
[Galaxy 3 Android Development] sad96:
Yes it was alpha 8.3. But G3 Rom devs say to talk with you as they don't know much about making this drivers finished.. :D:confused:
[Galaxy 3 Android Development] tom3q:
Well, it's not a driver issue, but rather incorrect integration with ROMs. I can't do anything about it at the moment.
[Galaxy 3 Android Development] sad96:
Ok. No problem. But can we hope for future work with this project?:fingers-crossed:
[Galaxy 3 Android Development] tom3q:
You can hope, but I can't guarantee any progress.

OpenFIMG is my flagship project and I'd like to add and improve many things in it, but I just might not have time to do so. (I have a full time job and also other duties, so I prefer to spend at least some of my free time relaxing, not working even more.)
[Galaxy 3 Android Development] amarendar94:
u said you said u would complete implementing opengles 1.4 features until Feb 2013

Many posts back I guess.
[Galaxy 3 Android Development] tom3q:
Yes, this was the plan, but things have changed since that time and I can't spend much time on community work.
[Galaxy 3 Android Development] MnauelKetnas:
Interesting, the Chainfire developer has a galaxy 3 too

http://xdaforums.com/member.php?u=631273

but I dont think he want to help us.
[Galaxy 3 Android Development] ak700:
He has a G3 but has something broken. Proabaly the USB connection (correct me if am wrong.) But if there is a bad flash, he can't restore and he bricks the device.
[Galaxy 3 Android Development] amarendar94:
I don't think so. May be he is always busy with high end phone and he is one of the top most developers in xda. If we receive his help we can be lucky.
[Galaxy 3 Android Development] sad96:
Please - COME BACK!

So as i understood this project is dead? And we can't expect anymore fully working FIMG 3DSE? :confused:

It's a pity. Because OpenFIMG project is presented in all ported ROMs. And so much work was put in them and now users have to use old 2.2 as they want to play games and watch videos. And all ROMs are seemed to be useless. And nobody can do anything accept you.

So please, tom3q, please go on working under this project. At least little steps, and one day you can make this phone alive with fully working 2.3+ ROMs!

We need you! :crying: I understand that you maybe be busy at work, home etc - all we are. But still..
[Galaxy 3 Android Development] tom3q:
Well, I consider the state of OpenFIMG acceptable already. Games have never been a target of this project and problems with videos you mentioned have nothing to do with OpenFIMG - there is a separate video codec hardware, for which there is simply no driver for newer ROMs (there was some work done in enabling it in CM7, but I'm not sure what happened with it).

If you still want those games so badly, there is a lot of skilled developers on xda-developers and I don't believe there is no one that could fix those remaining problems. At this time I don't have any plans for doing it myself. I have work, studies, home, my other personal projects (mostly mainline Linux support for hardware platforms I have at home), which already occupy most of my time and I'd like to still find some to rest from all of that.

I have a long term plan to add OpenGL ES 2.0 support (including a shader compiler) to OpenFIMG as a part of my Master's thesis ("Shader code generation and optimization for Samsung FIMG-3DSE GPU") and also migrate G3D module to the Direct Rendering Manager subsystem and mainline it, but this is going to take a lot of time and it shouldn't be expected earlier than in next year. I doubt someone will be still using a G3 at that time (but this is my personal project, so this is not a problem).
[Galaxy 3 Android Development] sad96:
In your status page only about 30 of 52 are done. It's just 60%. And without fully working this driver we can't expect any working textures in games. Even angry birds are mostly without them. And as i understand quality of video depends on FIMG drivers as they are base of all graphics in android. Or i'm not right? I think there should be any hardware acceleration.

I don't think there are any developers left here with g3 phone. If they are they've already made a fully working ports.

So i expect my phone die with 2.2 :)
[Galaxy 3 Android Development] tom3q:
The status page just lists implemented OpenGL ES features. They are not of equal importance. All the most important ones are already implemented. This translates to about 90% of typical usage of OpenGL ES API.

Angry Birds is not the best example here, because it has missing textures not because of an unimplemented feature, but rather because of the way of managing texture memory in OpenFIMG, which needs improvement for cases where more memory is needed than is available (Angry Birds is an example of such case).

As for video, I will repeat again, OpenFIMG is not responsible for video processing in any way. There is a dedicated set of hardware devices on S5P6442 which can do it - hardware encoder/decoder (FIMV-MFC) and video postprocessor and scaler (FIMV-PP).
[Galaxy 3 Android Development] hillbeast:
AFAIK the video playback is fully working on CM7. I don't know if it works on CM9, but it should be fully working on CM7 which is really what we should be targetting with the Galaxy 3. Not even Google wants ARMv6 phones on ICS because there's just so much more that ICS wants to do that is too much for the ARMv6 core to handle. We may have a very late ARMv6 based processor that may share a lot with the S5PV210 (The Galaxy S processor) but that doesn't change the fact the CPU is tiny. Really tiny.
[Galaxy 3 Android Development] sad96:
Yes. I agree that video works on cm7. But quallity is awfull. And also cm7 works faster than 2.2. But why is quality in cm7 worse than in 2.2?

I understand that ics+ needs more resources than our phone has. But 2.3 is much faster than 4.0+ and even 2.2.

Sent from my GT-I5800 powered by KISADWORX ROM v2.6.2
[Galaxy 3 Android Development] marcellusbe:
I don't know if it's usefull or not but here is the samsung fimg sources (for spica, probably (very) old)
[Galaxy 3 Android Development] tom3q:
With OpenFIMG in its current status, it isn't of much use. All of the hardware functionality supported by those sources is already implemented in OpenFIMG, so for learning about the hardware reading sources of OpenFIMG and available hardware documentation will be a much better choice. In addition those sources are stripped down from shader compiler (which was buggy and slow anyway), so there isn't any new information there.

OpenFIMG is mostly missing several high-level parts, like texture memory swapping (which would be made redundant after using CMA to allocate texture memory), decompression of compressed textures unsupported by the hardware and some OpenGL ES extensions, all of which don't touch the hardware too much.
[Galaxy 3 Android Development] hillbeast:
What do you mean by 'quality is awful'? Colours wrong? Pixelated? Glitchy? I don't understand.
[Galaxy 3 Android Development] sudersanmurthy:
Pixelated
[Galaxy 3 Android Development] D@rekills4:
I certainly don't see any pixelation in videos.

But I can say that the FPS at which the videos are played is quite low for 360p videos. 240p works just fine.
[Galaxy 3 Android Development] aarrun:
videos are glitchy, framerates are a bit low not as smooth as they wer in froyo, and and they are pixelated the videos dont look smooth as in froyo kinda like n smooth borders hard edges and a bit low clored. this is not a complaint plz dont take it wrongly. i have a suggestion too...... y dont we better use old sam drivers until the open fimg thingy is completely fixed. :P...
[Galaxy 3 Android Development] tom3q:
Haven't I already said that OpenFIMG is _NOT_ responsible for video playback in any way. Video is fully handled by OpenCORE or OpenMAX on Android and they use completely different hardware than the FIMG-3DSE GPU handled by OpenFIMG.

Please at least read the last page (not even several last pages, which would be even better) before posting something that has been already said to be incorrect.

OpenFIMG is used in CM7 to remove the need to replace a big part of Android graphics stack with code from Android 2.2, because the one in 2.3 relies on functionality broken in old drivers. It is even more important in further CM versions for G3, because you can't transplant graphics stack from Android 2.2 to Android 4.x, so OpenFIMG is the only way to get hardware acceleration.
[Galaxy 3 Android Development] hillbeast:
Sounds like the video is being decoded at the wrong resolution. Best bet is to not watch many videos on the Galaxy 3. It hasn't got a great video accelerator to start with.
[Galaxy 3 Android Development] Stanislaus:
Well I got very good playback on YouTube with HD enabled when I was on 8.3 with the 1GHz #888 kernel. Flash that kernel it might work.

Sent from my SG 580 powered by CM7.
[Galaxy 3 Android Development] dqsilver:
share GPU of G3 ???

:cyclops::cyclops:
[Galaxy 3 Android Development] Arjav23:
i will definitely have g3 nxt yr

Am never gonna sell it irrespective of whether i get a new phone or not

You know, G3 dev on XDA has taught mee one thing.....

Never to give up and how to make the best use of what we have

i wud hav never imagined six toggles,brightness bar,swipe to remove on Froyo (hats off to all froyo dev) and the hardwrk of marcel (Which is worth saluting)

(SORRY 4 BEING a LITTLE OFF TOPIC AND philosophical)
[Galaxy 3 Android Development] Nikhil_android:
do further development is needed such that playing games on GB ROM would become possible
[Galaxy 3 Android Development] m1trand1r:
try surfing many pages back and follow [MENTION=4117753]tom3q[/MENTION] posts and you'll know how development stands:)

Sent fom my S-II running >>SlimBean build 6.9 Unofficial (20130707) SaberMod 4.9 by fusionjack<< powered BY >>DorimanX kernel 9.34<<
[Galaxy 3 Android Development] jibeesh619:
Did you mean hardware acceleration on Spica or Galaxy3 ???

Are you getting 60 fps on galaxy 3 ?

Plz reply... :):):D
[Galaxy 3 Android Development] Benjamin_L:
You need to put on your irony glasses ;)
[Galaxy 3 Android Development] pflorin:
maybe the other devs didnt notice this thread just yet.. someone should send a prv message to capable devs for SG3 to help him with this project

there is a way to play HD games already using Chainfire3D with qualcomm driver settings but you need a kernel with OC capabilities to at least 1Ghz from what ive read.
[Galaxy 3 Android Development] ghiurtuv:
Yea this is a good idea but in my opinion the best dev is marcelusbe but he is busy with cm7 right now so when he finish he surely will help here.

Sent from my Galaxy to Terra
[Galaxy 3 Android Development] Thom47:
I gave you 10€, you need to stretch that budget and hire some developers to help you D:
[Galaxy 3 Android Development] aarrun:
i wonder y no devs still havnt responded......cozthis is the best project and the best development tht g3 cud achieve but only a single person is working.....plz help him devs......he has the best we can get......
[Galaxy 3 Android Development] Shree_Jamdar:
DEVS Please!

He is right, this is something big! A I am a noob but I think, atleast in graphics dept., this driver is going to give better performance than a CyanogenMOD or ASOP gingerbread...I don't know why., but i think so.
[Galaxy 3 Android Development] aarrun:
yup.....drivers r the most diffcult part.....and tom3q is making everything new coz samsucks drivers really r broken......so making a whole new set is the most difficult thing ever,,,,,,even porting cm7 or gingy is less compared to it.....and he is all alone wat the hell.....
[Galaxy 3 Android Development] Benjamin_L:
I really doubt that Sebastien isn't already working on it ;)
[Galaxy 3 Android Development] hillbeast:
Bumping simply to keep interest in this project and in hope some smart guy will show up and be like "MUST MAKE DRIVERS".

Really liking the look of what you've done so far, and I hope this works.
[Galaxy 3 Android Development] unreal3000:
what u have achieved is frikin AMAZING!

60fps on raging thunder 2 is better performance than the adreno 200 found on phones like galaxy 5 and some others!

and though we do have some amazing developers, correct me if im wrong but i think stuff like this requires people who specialize in drivers and related so i think

ur one of the only people who can do this!

anyway this is amazing!

if i may ask, if ur going to spend more time on the spica could u release ur current progress here?? im dieing to try this out...maybe just a beta:D

tks
[Galaxy 3 Android Development] akash.gpta:
Lol!! read through the posts again & you might see the irony in there...:p
[Galaxy 3 Android Development] cdesai:
You just didn't get it :P
[Galaxy 3 Android Development] dhirend_6d:
:D:D Man that post needs to be deleted. Many missing the sarcasm in it.
[Galaxy 3 Android Development] Thom47:
What have I done..
[Galaxy 3 Android Development] tom3q:
To clear any confusion I'm posting a bit of information about the progress.

The project was already started pretty long time ago and it's somewhat already working, providing hardware acceleration for Android UI and some simple 3D apps. More advanced applications (and games) don't yet work, because of some missing functionality. More detailed status can be found here: https://github.com/tom3q/openfimg/wiki/Status

Still, the code is being written according to the golden rule, first make clean code that works properly and then optimize it, so there is pretty much area for optimization yet.

As for Galaxy 3, support for it isn't there yet, simply because I don't have access to such phone.
[Galaxy 3 Android Development] unreal3000:
soooo... any more news?? :D