yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] m1trand1r:
cf3d works for me and it helps in most games..but in some games not...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sent from Galaxy

Hercolubus Rom v2.0

powered by

Latest g3mod kernel by Arakmar-07.04.2012.zip

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Galaxy 3 Android Development] TheCreat:
No, it should work fine without any wipe.
[Galaxy 3 Android Development] Aced443:
Hey :)

Does it work with Froyo?
[Galaxy 3 Android Development] i_rnb:
NOPE. :/
[Galaxy 3 Android Development] Aced443:
Why doesn't it work with Froyo?
[Galaxy 3 Android Development] eeshlikhith:
There are no ROMs in froyo that support it and there is no developer who wishes to make it work on it either.
[Galaxy 3 Android Development] tom3q:
Because Froyo ROMs are broken with Samsung's stuff.
[Galaxy 3 Android Development] prabhuthelegend:
Hello Tom,

just a request..dev hillbeast is trying to get the MTD driver working for galaxy 3 in his kyorakernal thread and facing a bit of problems..whole idea is to make the kernel 3 porting for our galaxy 3..since you have already ported the same for Spica ..could you please help him for what might be the best way to do that..

and again its a request when you will be free :) great going with openfimg :)
[Galaxy 3 Android Development] Halco:
I think they already "cooperate" on this :p
[Galaxy 3 Android Development] prabhuthelegend:
oh..I don't know that..anyways thanks for the info :)
[Galaxy 3 Android Development] Halco:
hillbeast, marcel, tom, moikop, dharam, apollo (and others sorry for dont mention the name) are the best dev for our phone so dont worry, they collaborate each others :)

Send from my Galaxy 3 Naos with Tapatalk 2
[Galaxy 3 Android Development] hillbeast:
We do communicate behind the scenes, and as you see in the Kyorakernel thread, moikop gives me a hand quite a lot. When I get really stumped I come to tom3q seeing he has experience in kernel porting.
[Galaxy 3 Android Development] prabhuthelegend:
yeah..seeing no posts from tom on your kernel thread made me to think he was unaware..anyways just got to know there is something called Private message ;)

all the best for the kernel porting then ..you are awesome :)
[Galaxy 3 Android Development] hillbeast:
Yeah don't worry. We usually do it in private message to make it more direct and also if we are working on something we know people will get all over excited about like a magical new feature that may or may not work. Better in those cases to not make it public because if it doesn't work then at least people won't cry we didn't make it work.
[Galaxy 3 Android Development] Sparx75:
Hey Tom :), any chance of upgrading to OpenGL ES 2? Probably is a stupid question, but as you know, we all desperately want to use Instagram xD.
[Galaxy 3 Android Development] tom3q:
Plus, we don't get questions about ETA and so.

I don't have such plans at the moment, unless someone makes a shader compiler for FIMG-3DSE.

Btw. What is instagram? (Just kidding, but I don't understand how something like this can be popular.)
[Galaxy 3 Android Development] TheCreat:
Finally someone who agrees with me on that. Thank God there are still sane people out there :rolleyes:

Swyped on my Galaxy 3
[Galaxy 3 Android Development] max5800:
That makes 3 of us...
[Galaxy 3 Android Development] sharukins:
so now this thread is here for everyone who wants to tell us that he/she isn't using instagramm?

back to topic guys...
[Galaxy 3 Android Development] Sparx75:
Haha Sorry for going off topic guys. Keep up the Good Work Tom :). You Pwn.

Oh and I found a few alternatives to Instagram, so I'll make do :P.
[Galaxy 3 Android Development] Gurjot95:
Just use Lightbox till we have a working Instagram.
[Galaxy 3 Android Development] m1trand1r:
c'mon don't spam please:)...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sent from Galaxy

Hercolubus Rom v 2.0

powered by

G3mod by Arakmar 12/04/2012.zip

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Galaxy 3 Android Development] Gurjot95:
I was just trying to end the off topic by naming the alternative so people will stop demanding to tom3q till a working one is found. Thought it was helpful.
[Galaxy 3 Android Development] austin266:
@tom3q

hi mate

howz ur work going

i haven't seen any updates in this thread for some days

i feared of that u r leaving this project

we r so glad abt ur work

can u give me the link of ur github
[Galaxy 3 Android Development] Piraze91:
The link is on the first post.
[Galaxy 3 Android Development] tom3q:
Also in my signature.

I'm focused on rewriting camera support for Spica at the moment (sensor driver, camera interface driver, jpeg codec driver, libcamera), so there are no updates to OpenFIMG at the moment. However, G3 uses the same sensor chip and very similar camera interface and jpeg codec, so it will be possible to reuse exactly the same code in future 3.x kernel for G3.
[Galaxy 3 Android Development] Spitlebug:
Why the Spica may I ask?

Sent from my GT-I5800
[Galaxy 3 Android Development] tom3q:
Because it's my primary development platform. Don't forget that it's the platform, which OpenFIMG started with.
[Galaxy 3 Android Development] Spitlebug:
That makes sense. Are you running FROYO on your Spica?
[Galaxy 3 Android Development] EdisDee:
i think tomq3 is using ics :) with kernel 3
[Galaxy 3 Android Development] unreal3000:
tom3q, just a suggestion....

wouldnt it be better to abandon spica as use g3 as main development platform? as g3 would be classified as the successor of the spica?

or would it be easier to dev on the spica and then port to the g3?
[Galaxy 3 Android Development] eeshlikhith:
I doubt theres something being easy when it comes to deving... but afaik there is not much work done on G3 so i guess its better to go on with spica.

BTW IDK why but i feel your post felt a bit selfish to the G3 community (no offence) just saying.
[Galaxy 3 Android Development] i_rnb:
yeah .. that wld b better , but quite obvs he s gonna say no.. :P he jst cant stop deving a device for the sake of its succesor ..
[Galaxy 3 Android Development] sharukins:
with that reason in mind, he should abandon the G3, too and go for the Galaxy ace plus :D
[Galaxy 3 Android Development] hillbeast:
The thing is, it would be like me. Sure I have a Galaxy S2 but I don't develop for it because its my main phone. tom3q probably still devs for the Spica because he already started on it and therefore its a project for him to get it going great. He won't abandon his project just because there's a different thing to work on.
[Galaxy 3 Android Development] tom3q:
Spica and G3 are very similar. As you can see with OpenFIMG, G3 can also benefit from development for Spica. Once a modern (and clean) kernel gets ported for G3 (or rather all the existing parts put together), I will be able to put there many of the things I've got currently in my Spica-3.0 kernel, including rewritten camera support, which I mentioned already in my previous post.

Another thing is that it's easier for me to develop for Spica, because I already have a clean kernel (spica-3.0) and ROM (my CM7 for Spica) base, which guarantee no interferences from any old and broken Samsung's stuff and allow me to implement everything based on current APIs and in proper and generic way.

Btw. I wouldn't call G3 a successor of Spica. Although some of the hardware is refreshed a bit and there is more RAM (which is a great benefit), the screen of Spica (320x480) still beats G3 (240x400) and more hardware keys (especially accept/disconnect) are a good advantage. So those phones should be rather compared as two similar models from the same range.
[Galaxy 3 Android Development] unreal3000:
no prob!

but still i think the g3 was atleast intended to be a successor , even if it just a tiny upgrade to the spica :P

anyways goodluck! just amazing performance from fimg-3dse!
[Galaxy 3 Android Development] eeshlikhith:
BTW isn't it possible to simply make a wrapper like thing for these libraries to make the old froyo libs to work on ICS and GB just the way the Camera lib wrappers are made so camera works?
[Galaxy 3 Android Development] tom3q:
Wrappers aren't the best way to run things.
[Galaxy 3 Android Development] eeshlikhith:
http://oss.sgi.com/cgi-bin/cvsweb.cgi/projects/ogl-sample/main/gfx/lib/opengl/include/

was googling out of boredom and noticed a lighting.h and thought it could be of help for you?
[Galaxy 3 Android Development] tom3q:
The only thing missing to implement next features in OpenFIMG is a bit of time to spend on designing the implementation and coding it. I have hardware documentation and OpenGL ES specification, that's all I need to develop the project.

Btw. The link you posted is to a software-based implementation of desktop OpenGL version. OpenFIMG is implementing the mobile version of OpenGL (OpenGL ES) on top of a hardware graphics processing unit.
[Galaxy 3 Android Development] hillbeast:
Another off-topic question for tom3q: do you think that the cause of no output on UART when we try to boot newer kernels could be related to the USB switch chip? I have read posts from the likes of Adam Outler saying that the USB switch chip doesn't get initialised until a wee bit into the Sbl and as a result they have to grab UART internally so they can debug the bootloader, but I was thinking maybe the same thing is happening here with the USB switch chip getting reset and it no longer outputs.

Think this could be the case? If so do you reckon I should try grabbing the internal UART?
[Galaxy 3 Android Development] tom3q:
I didn't have any problems with the UART on Spica. If Sbl initializes it (and it does, because you get output from Sbl through UART), then it will work fine until something (a driver or GPIO initialization code) resets (by asserting reset GPIO pin if such is present) or reconfigures it (for manual switching for example, but all the drivers I have seen use automatic switching, where the chip itself recognizes what is plugged and connects proper pins).
[Galaxy 3 Android Development] hillbeast:
Hmm okay. The problem happens right as the kernel has finished extracting and begins booting. It is clearly reading the kernel from the flash correct because the Uncompressing Linux code is in the kernel itself, so the kernel obviously dies at early init. Even if I am not using the code made specifically for the phone itself, it should still at least be giving some form of output to where it would kernel panic. The code I am trying right now is the last version with S5P6442 support (2.6.39.4) but I still cannot understand why there isn't even a peep about anything. Could it be a lack of machine initialisation code? How did you start with porting 3.0 (or any new code)? Did you start from scratch and work out kinks as you went along or did you port drivers first then test?
[Galaxy 3 Android Development] tom3q:
Do you have early serial console enabled in kernel config?

My kernel for Spica was done from scratch, based on mainline sources which had some basic support for S3C6410. I started with adding machine definitions to mach-s3c6410 and some basic mach-gt_i5700.c just to start the kernel and get some output from it. The only problem I recall was with mach-type hardcoded to SMDK6410 in Sbl, so additional head-gt_i5700.S was needed in arch/arm/boot/compressed to replace it with proper mach type very early, but without it the kernel still printed a message about incorrect mach-type.

After getting basic bootup to work I proceeded with rest of the drivers, one by one, porting (or writing from scrach, but not using any old sources from original kernels as they are useless) and testing each one.
[Galaxy 3 Android Development] kyrillos13:
@tom3q, do you plan to code a bit those days and update OPEN-FIMG?

PS: Ah just saw the first-post date. It was 31/05/2011 so happy one year universary for a project that is making this phone a better phone:)
[Galaxy 3 Android Development] tom3q:
Not until I become a bit less busy. However, this should happen in some reasonable (but indefinite) time.

EDIT: Btw. OpenFIMG is also my thesis, so I plan to make it fully cover the OpenGL ES 1.1 specification till Feb. 2013, when I'll be defending it.
[Galaxy 3 Android Development] sharukins:
I just wanted to get this thread back on top and aks if you're still busy tom ;)

I'd love to see an update of this driver, really appreciate your work!
[Galaxy 3 Android Development] prabhuthelegend:
+1 to that...:D
[Galaxy 3 Android Development] tom3q:
Well, I'm now taking a break after the exams till the end of this week, then I'm going to finish my libcamera implementation for the 3.x kernel (for Spica currently and later also for G3) and will see what to do after that, 3.x kernel for G3 or something for OpenFIMG.
[Galaxy 3 Android Development] protomank:
I really hope you get the 3.X kernel to boot on G3, so that ICS development can be bring back from the dead (I'm using ICS and it is worth the effort, much better than 2.3 even with lots of parts not working). :cyclops:
[Galaxy 3 Android Development] alen1901:
And it will help port jelly bean, which is much more optimised and smoother, faster, it will work better than ics. ;)

Sent from SpeedMachine i9023
[Galaxy 3 Android Development] szewc1:
There will not be ICS and definetely not JB for our phone. We have no datasheets, source code nor even official ROM for already 2 years old Gingerbread (which wouldn't change much). Our phone is kind of conglomeration of Samsung's spare low end parts, that are everyting but popular.

New kernel, hardware video encoding/decoding/acceleration + camera, bluetooth, gps and so on. We didn't get official CM7 (marcellusbe - hail unto thee), and even phones like Motorola Droid X won't see CM9.

So start saving money and next time buy a popular device with developers' wide support.
[Galaxy 3 Android Development] alen1901:
Thats why there are google and samsung phones. ;)

Sent from SpeedMachine i9023
[Galaxy 3 Android Development] tom3q:
You must be definitely right. Ahh, wait... What is this? http://xdaforums.com/showthread.php?t=1374691
[Galaxy 3 Android Development] szewc1:
You both know what I mean. We are already driving a car with 3 wheels and low fuel, and there is nothing on the horizon that looks like changing it.

Thanks Tomek for all your work, sometimes I regret choosing G3 over Spica.
[Galaxy 3 Android Development] tom3q:
Not really. Spica is the phone which can't run ICS properly, because it lacks RAM and has an ancient (and buggy) RIL implementation from Android 2.1. Maybe JB for G3 would be a bit of an overkill, but ICS should work pretty fine on this phone. The only field where G3 is behind Spica is screen resolution (and maybe hardware keys, but they're just convenient, not a must), all the rest is the same or better.

One thing is true, though. G3 isn't a phone designed to run modern versions of Android and will never give such user experience as phones from higher-end, so if you can afford a phone with ARMv7, OpenGL ES 2.0 GPU and HDPI screen then it will be a far better choice than G3, running any version of Android.
[Galaxy 3 Android Development] protomank:
A nice preview of what COULD BE ICS on our phone. I used this for a week, it IS NICE, beautiful and fast; but lack of hardware support makes really bad to daily use. No barcode scan, no location servies throught wifi and mobile network, incomplete video drivers, no working camera... :mad:

If Samsung released datasheet or open-source drivers for all G3 hardware, ICS/JB will come true, but reality, is that there is no way - and see, I'm not even complaining, I've returned to 2.2 and I'm happy with it - it is just that the effort is SO BIG that most developers find it is not worth the work after a while (and who can blame them? I sute can't). :cyclops:

But we can make a lesson from it: my next phone will be a google one or HTC (for what I know, their support for open-source is great) and I will not only avoid companies that do not support open Android development, I will keep asking them to do so.
[Galaxy 3 Android Development] tom3q:
Hmm, first of all, I don't know why so many people think there are no datasheets for G3. I have almost all datasheets for G3 hardware and I found all of them in the Internet. The only missing datasheet is for the main SoC (S5P6442), but there are several other SoCs which share much with the SoC of G3 and their datasheets are available (S3C6410, S5PC100, S5PC110, S5PV210).

As for HTC, their open source support isn't better than Samsung, if not worse. Samsung phones are the most open ones after the Nexus line.
[Galaxy 3 Android Development] raja4sure:
Well ....i must say one thing..that when the real work of kernel 3.x begins for G3....every questions will surely turn into answers of their own & surely the expectation of users will go high.....

But the thing is it has not started yet...because of lack of free time of our Devs (Hillbeast, tom3q & moikop)....don't know about Marcel in this case.:cowboy:

the only fear is that......the devs are moving onto new phones as the day passes.......:confused:

we have already lost .....Dharam(moved to S2), arakmar(Moved to Xperia S), Apollo......:(
[Galaxy 3 Android Development] hillbeast:
I don't know why people think HTC are amazing for open source. HTC is terrible, mainly for the hypocrisy they create. They go on about being open source yet they lock the bootloader down. They say they will unlock it for people yet some can't get it unlocked. They try to say that at least most can get it unlocked yet they shouldn't lock it in the first place as there is no need. They use Qualcomm parts which (if you think Samsung are bad then think again) have absolutely no datasheets available at all.

HTC are terrible. If you want open phones, look at Samsung devices powered by an Exynos or OMAP processor.
[Galaxy 3 Android Development] sharukins:
sry if this is a stupid question but why is there an CM version for almost every HTC phone but only for few Samsung phones?
[Galaxy 3 Android Development] hillbeast:
Because there is only like 5 HTC phones compared to the 300 Samsung phones. (exaggeration)
[Galaxy 3 Android Development] sharukins:
but there are like CM versions for about 16 different (I don't know if they really differ that strong) htc phones while for samsung there are versions for 6 (plus the Nexus ones) o_O
[Galaxy 3 Android Development] tom3q:
First of all, don't count official CM versions. There are unofficial ones for almost all Samsung phones and they didn't get upstream simply because it isn't worth all the effort required to do so.

Another thing is that porting ROMs is dependent on how clean the hw/sw design is in given phone. HTC uses all the standard solutions that were introduced with first Android phones without any strange complications (as opposed to Samsung with some of their phones), making porting a ROM just a matter of creating a board configuration and compiling it.
[Galaxy 3 Android Development] moikop:
you'd have to ask the mainteiners... but one thing is for sure: it's not because htc is open source.

the three most open-sourced vendors are the Nexus line, Samsung and (maybe?) lg.

the problem with samsung isn't that they do no release datasheets (they have released more than htc and motorola together for sure), but that their code sucks.
[Galaxy 3 Android Development] tom3q:
Yes, that's the point. Although it seems like they are constantly improving their code quality, especially looking at the code for their latest Exynos SoC series.
[Galaxy 3 Android Development] hillbeast:
Kernel 3.0 on the Galaxy S2 (I'm not sure if Samsung did it or if Team Hacksung did it) works quite well. It is moving away from so much of Samsungs proprietary crap. There are still some things that confuse me like the fact the phone has a recovery partition yet it's not used, but it does show they are improving. The S3 actually does use the recovery partition.

Yes HTC has more of their phones on CM, but I sitll maintain that there are more Samsung phones than HTC devices, and most HTC devices are similar to each other. They always use Qualcomm chips for starters, so that limits the amount of chipsets to develop for. Samsung use Exynos, OMAP, and Qualcomm.

I wouldn't take an HTC phone even if I was given it. I'd sell it and buy another Android. I just cannot tolerate the hypocrisy of HTC. Samsung, LG, or Sony are the best. I can't say much of Motorola because I don't see much from them lately.
[Galaxy 3 Android Development] andreapier:
I don't want to look like rude but i think it is now clear that samsung is better than htc fron an openess point of view... now let's start some real development here and in 3.x kernel please! At least, this is what i'd like to see!
[Galaxy 3 Android Development] protomank:
For my part, I've read on some news site (osnews or gizmodo, can't recall exactly witch one) that HTC was open-sourcing all their drivers for Android.

Looks like that was a false statement and I am glad (but also sad) to know so; thank you for the info.
[Galaxy 3 Android Development] amarendar94:
@Tom3q

Every GB,ICS,JB rom for g3 need ur drivers. BUT.........

The To do list and status pages for

OpenFIMG haven't been updated

since the end of March. More

importantly, there haven't been any Git commits since the end of April.

[Request]

We need an UPDATE atleast now sir......tnx.
[Galaxy 3 Android Development] tom3q:
Hmm? I'm not sure what are you talking about. Last Git commit is dated to 17 days ago. Last update of Todo wiki page was on 19th July.

Still, no updates means that currently I don't have anything interesting to show, which, in turn, means that I'm either busy with something different (it's the case currently) or I'm working on something big that will be published after I finish it (was the case several time before). You don't have to ask for updates, as I won't give any until the work moves on and there is some achievement.

At the moment I'm holding any public releases until I get an approval from my employer (Samsung Poland R&D Center) that I'm allowed to continue my work on this project and publish new code.
[Galaxy 3 Android Development] amarendar94:
I am sorry Tom. I din't check ur status page. I just saw about your project status in phoronix.com and I jumped into this forum.

Sorry.......sorry......sorry.........TOM
[Galaxy 3 Android Development] prabhuthelegend:
Since OpenFIMG is an opensource project and part of your thesis too, may i ask why is the approval needed from Samsung Tom ?

If they say no then we may have to revert back to Samsung FIMG drivers:crying: which we are not ready as openfimg has all the potential to be a great graphics driver..

:o
[Galaxy 3 Android Development] tom3q:
Well, FIMG-3DSE is an intellectual property of Samsung and I can't publish any information about it without approval. Source code is also a kind of information about the hardware. Of course the code published before my employment at Samsung isn't affected.

However I will do everything possible to get such approval, so let's hope for the best. If not, someone still can take the project over and finish it.
[Galaxy 3 Android Development] sarthak.killedar:
There will be no one to take over your project for OpenFIMG as you can see how many developers know about Graphics Driver Development, and the most awaited thing is OpenGL ES 2.0 for our phone as only about 9% Android user phone runs OpenGL ES 1.1 now. So, I hope for the best and hope you continue your work in the same way as you do.
[Galaxy 3 Android Development] TearsDontFalls:
If you are working at samsung, so do you also know if we should expect some official updates for our g3(some said gb is coming)???
[Galaxy 3 Android Development] tom3q:
I don't have access to this kind of information (even if I had, I wouldn't be able to reveal it), but (personally) I don't think that there will be any official update for G3. There is JB already and there are newer (and more expensive) phones waiting for updates.
[Galaxy 3 Android Development] hillbeast:
The Galaxy 3 was deprecated over a year ago. There will be no further updates at all. Don't sit in vain hope. Samsung replaced all the good phones with S3C and S5P chips with **** Qualcomm ones.

Sent from my Serenity Galaxy S2