Ok so please forgive my noobness here but I'm dying to ask a few questions... I have been an android fan for years and always had lots of options for my phones, and now that I am switching phones I would like to help out more. I see that development is going slow on this phone and had a few questions...
What would it take to port over some roms from say the galaxy s (I'm thinking possibly CM7 or MIUI)? What is the closest phone to ours if not the galaxy?
If the kernel is open source (https://opensource.samsung.com) then is over/underclocking possible with much effort?
Is all I need to build a functioning rom available from the android sdk and the samsung open source website? (I understand this is no easy task, just wondering if I need more than this)
FM transmitter... I hear this phone has a FM transmitter, is this true? Oh man what I wouldn't give to get this working. I would love to hear any opinions/suggestions/comments on this subject as this interests me most.
I'm sorry once again for all the questions, I am looking forward to helping out however possible.
I suggest you look up the wiki's on cyanogenmod on building. You'll need some sorta POSIX environment (ie.. linux or OS X). Here's the one I used:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II_(AT%26T):_Compile_CyanogenMod_(Linux)
The SGS family largely uses samsung components (CPU's, GPU's, etc). The Blaze uses the qualcomm snapdragon stuff. The blaze is using the msm8660 arch, which isn't really present in the cm7 sources. The only thing kinda there is the sgs2 for at&t (skyrocket). Finding other examples using similar hardware has not been easy for me. The audio subsystems for sgs2 seems to be yamaha based, where as ours isn't. You'll want to be VERY careful to make sure all the partitions are set up properly in your work as otherwise you may end up wiping the radio or other supporting partitions, and that would be very, very bad. And etc... etc... etc...
It would help to have a working knowledge of unix/linux. You'll definitely want to root your phone (obviously) and install busybox so you have a decent toolset to go poking around the OS.
I wish you luck and I hope this helped!
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
Oh, forgot about the Kernel.
The kernel itself is always open source (legally required). The changes and binary blobs for drivers aren't.
You apparently tweak the kernel seperately from a cm7 build. OC and UV are about playing with the timings inside the CPU and is not for the feint of heart. My understanding is that there is a whole series of equations and calculations you use to arrive to the frequency table for such things. Since other hardware uses our CPU, that's probably the place to start looking... i.e... the EVO 3D.
Thanks for quick reply! I currently dual boot ubuntu/win7 and have a small working knowledge of linux, so hopefully that helps there. I will start messing around with the phone in another week or so when my schedule allows, but will gladly help beta test until then! Please feel free to hit me up when you need something tested
Also, since you are the hardware man.... what about that FM transmitter? Is that only a receiver or is it a combo? I personally have never seen a FM transmitter in a phone and would love to have one.
dr4stic said:
The SGS family largely uses samsung components (CPU's, GPU's, etc). The Blaze uses the qualcomm snapdragon stuff. The blaze is using the msm8660 arch, which isn't really present in the cm7 sources. The only thing kinda there is the sgs2 for at&t (skyrocket). Finding other examples using similar hardware has not been easy for me. The audio subsystems for sgs2 seems to be yamaha based, where as ours isn't. You'll want to be VERY careful to make sure all the partitions are set up properly in your work as otherwise you may end up wiping the radio or other supporting partitions, and that would be very, very bad. And etc... etc... etc...
Click to expand...
Click to collapse
As far as being close to the Blaze, what about the Galaxy Note? It has a msm8660 while the Blaze has a msm8260. Both have the adreno 220 gpu, same ram, and release around the same time. I see there is a larger screen and a different camera, is there something we can use there?
I only ask as I ran across this thread: http://forum.xda-developers.com/showthread.php?t=1573568 and was wondering if maybe this phone would be the place to start a port.
Related
The current situation with the Dream and missing drivers have made me think about the importance of open drivers also for embedded devices like phones. Anyone using the combo Ati card + a distro that upgrades Xorg or kernel more often than Debian stable (whics is most of them) have felt the urge to curse closed source drivers to the deepest levels of hell. Now the same **** hits the fans for G1 owners.
Even though tis post is not about Ati, I must say in their defense that they have released specs, which is great.
Qualomm however, has not released anything whatsoever when it comes to source or specs, as far as I can understand. I have been stalking enough development efforts on embedded devices to know that this is common practise from hardware vendors - and extremely annoying for any geek wanting to do some heavy development for them.
And now i finally reach the question, which has already been mentioned in the title: Is there any device, released or upcoming, that features a SoC with opensourced drivers and firmware for all components? If not (and guess it is so, unfortunately), is anyone better than the others?
Of the many phones/MIDs/ARM gadgets I evaluated before I got my Vogue, the only ones I saw that had even remotely open OpenGL drivers were based on TI's OMAP3 SoC or had a PowerVR SGX GPU. Unfortunately, none of the OMAP3/PowerVR devices I saw were cheap (OpenPandora, AI Touchbook, BeagleBoard, Nokia N900, etc.) enough for me. That, and I saw what happened with the TouchBook's OpenGL ES library, which apparently wasn't allowed to be distributed outside of TI's SDK - but I haven't been following that. I also saw that the Samsung S3C6410, used in the cheap made-in-China SmartQ5 and Q7 MIDs, has open enough specs for writing a driver, but no one has stepped up to write one yet. Aside from OpenGL, though, an OMAP3/4 based phone would be perfectly open... except there aren't many consumer OMAP3 phones I really wish reverse-engineering or converting the Qualcomm/ATI libhgl.so for "real" Linux wasn't next to impossible/illegal - if doing it was easy, you'd have an OpenGL ES library for Debian on the Dream by now. I would reverse engineer it if I had the resources, unfortunately I'm unsure how legal it would be to do that.
EDIT: as far as phones (as opposed to the non-phones I was talking about), the most open right now seems to be Qualcomm - not counting Marvell PXA or other feature-poor (opposite of feature-rich ) SoCs - as contradictory as that may seem. If you haven't guessed by now, I'm basing everything on OpenGL drivers, since as far as other hardware goes, I don't have much expertise. Also, I haven't looked hard enough to find any Freescale- or other ARM SoC-based phones, and I don't know of any Android phones (shipped with android, not ported by third-party developers) that DON'T use Qualcomm chips. For the moment, it seems you must pay a premium for openness.
Well, thank for an insightfull reply anyway.
The N900 is definitely on my watch-list, but yeah, it sure is a bit expensive. Then again, it IS cheaper than the N1, So it isn't that bad.
As for the legality, it really shouldn't be legal NOT to give out open drivers for hardware when you sell it to consumers. They should have a legal right to have it!
But seriously, these outdated qualcomm chips in most HTC phones is no competitor to Snapdragon or Tegra, so who do they think they are fooling when they keep the drivers closed for "competitive reasons". Thats pretty much what they all us as an excuse.
Sad to hear about the "free" Touchbook fate though. I had high hopes for it, but if that is the stance they're taking now, I'm glad i didn't buy it myself.
Soooomewheeereee over the rainbooooow, coooode iiiiiiiiis freeeeeee (likeinfreespeechnotfreebeer) Soooomewheeeeree over...
In paradise there is no binary blobs in any code running on any of my devices.
Acer has just released the "Acer Liquid kernel source code". http://www.acer.co.uk/acer/service....tx1g.c2att92=122&ctx1.att21k=1&CRC=2980211862 Liquid support under Document tab.
Hope that everything is there.
The GeeksPhone One is an open source Android device running on the MSM7225 processor, and worth checking out.
http://www.geeksphone.com/en/
The samsung moment uses the Samsung S3C6410 processor .... whitch is used in otehr windows mobile devices and i do belive samsung has a sdk advable but im not sure
I don´t know it exactly but shouldn´t be the OpenMoko a true opensource phone?
Isn't the Droid pretty decent? Doesn't Motorola even release the drivers for the hardware as open source here: https://opensource.motorola.com/sf/sfmain/do/home
The Moment has the same problem the SmartQ 5/7 have, unless Samsung released source code for the Android OpenGL drivers behind my back. That still wouldn't cover running Debian, sadly - I was hoping I could run Debian if I got one, but I know it won't be 3D-accelerated even if Debian does run. The Motorola Droid has pretty much the same SoC as the N900 and friends, hence the same PowerVR driver problems. IIRC, the SGX drivers are only partially open - I think most of the source code is available, but I remember hearing somewhere that there were redistribution problems. The infamous Intel GMA500 IGP (which was actually designed - and manufactured I think - by PowerVR) still suffers from poor-quality closed drivers, and Intel still hasn't done anything about it, pointing fingers at PowerVR for who knows what reason. I've come to a conclusion: hardware companies don't care about the consumer anymore
What's the status of this these days?
- how open are the n900 drivers?
The Nexus and i9000 both have a thing where the modem reads the CPU so that's as far as the reliant project goes.
Geeks phone is pretty cool but has binary blobs.
I remember reading about another project to make a phone like the Geeksphone but being prepared for compromise to achieve full openness. But I forget the name of the project. Anyone know what its called?
I'm really hoping there's a cheap Chinese phone out there that one can really own from driver level up now.
Hey everyone. Last year you might remember hearing about the new Sidekick running a custom tailored version of NetBSD. Not being a fan of the Sidekick, I could really care less. But I still was intrigued by the fact that it runs NetBSD.
After a lot of Googling I noticed that there really are *no* projects out there for getting any type of BSD operating system running on mobile devices. I'm very curious about this for I've been a huge fan of all BSD distributions because their stability and speed. I mostly use these operating systems for server purposes of course, but anyone who has the time to make it a rock solid desktop OS can definitely make it happen. I've even installed NetBSD on computers with as little as 16mb of RAM running a Pentium 133mhz CPU and it runs very well. Which makes me think that it would definitely be a nice fit for a mobile device. After all, the iPhone runs an ARM variant of the Darwin kernel, which is based off FreeBSD.
Now of course an idea like this would require a boat load of work. Mostly with the bootloader and driver support for things like GSM, CDMA, WiFi, etc, hardware. But luckily as you may already know, the kernel has support for a huge range of architectures including ARM.
I know it sounds farfetched and might even sound retarded to a lot of you out there. "Why the hell would anyone want to do that? Linux is already doing the job just fine". But then again, why the hell not?
I would love to hear some input from the pros out there. I'm curious to know about the obstacles that I may face. Most importantly, I'd like to hear your opinions. At the least, I'd like to know if there is some kind of general bootloader out there, similar to HaRET that could boot another kernel other than Linux.
Thanks for your time.
project members
Hey guys, I'm going to begin cross compiling a custom NetBSD kernel for the ARM architecture and test it out a little with some emulation. I would love to get some help with the bootloader.
How have you been getting along with that?
Are you interested in creating a complete Net/Free BSD version of a mobile phone OS?
Get back to me when you have time
Sorry for offtop, but it's theme really interesting for me. Does anyone have any ideas how to do it?
I'm interested in this man, PM me if you want to compare knowledge
+1
I already posted this in the Nexus dev forum, and I hate to clutter the boards, but I know that there are a bunch of talented devs here that may not see it on those forums. If we can bust the 30fps cap for good, and get the GPU overclocked, then we could see some serious gaming performance out of our Snapdragon devices.
I'm sure we all heard about being able to overclock the GPU on some of the old MSM devices, but the Snapdragon handles the graphics chip in a different way. The goal of this thread is to try and overclock the GPU on Snapdragon devices as well.
There is nothing GPU related in acpuclock-scorpion.c (the Snapdragon cpu clock settings) at least for setting gpu clock speed as far as I can tell.
In board-mahimahi.c (Nexus board file) and board-supersonic.c (Evo board file) there is some kgsl init code, but so far as I can tell it isn't setting the clock there, instead it seems to be pointing to PWR_RAIL_GRP_CLK to set the clock in both devices. It defines the variable in each of those files but I'm not sure where that variable is set, since it doesn't seem to be in any of the other board files as far as I can tell. I could be completely off here too though.
In drivers/video/msm/gpu/kgsl/kgsl.c there is a method called kgsl_clk_enable that seems to be called whenever the GPU is enabled. It looks like this:
Code:
/* the hw and clk enable/disable funcs must be either called from softirq or
* with mutex held */
static void kgsl_clk_enable(void)
{
//clk_set_rate(kgsl_driver.ebi1_clk, 128000000);
clk_set_rate(kgsl_driver.ebi1_clk, 245000000); // Looks like it sets the GPU clock, right? Wrong.
clk_enable(kgsl_driver.imem_clk); // Enable the clock
clk_enable(kgsl_driver.grp_clk); // Enable another clock, but why?
}
The line that's been commented out is the original value, I replaced it with my value on the line below it in a failed attempt to overclock it. Probably a stupid effort on my part, I doubt it's that simple, but it was worth a shot. The comments at the end of the line are also my additions.
According to the clk.h files in the standard linux kernel, clk_set_rate is obviously a method to set the clock rate. The first variable is a struct that tells it which clock to set, and the second variable is a long value that is the rate you want it set at. Is it setting the right clock there for Snapdragon chips? Or is it only the clock for older chips?
I'm in way over my head with this source, I'm but a lowly Java dev, but I really wanna solve this. Can anyone with a little more experience than me throw in a little more info? Sorry if it doesn't make much sense, if it isn't clear just ask me & I'll try to explain a little more.
Regards,
Jesse C.
EDIT: Okay I did a little more digging and those kgsl settings should work for QSD8x50 chips. In the config file, under Drivers, Graphics Support, it allows you to enable 3D accelleration for QSD8x50 & MSM7x27 chips. The tag for that is CONFIG_MSM_KGSL_MMU. If you check in kgsl.c it checks to see if that is enabled in the config, and if it is then it compiles and uses kgsl.c & all of the kgsl code. That tells me that the clock is either not being set, or the wrong clock is being set. I'm adding some debug code right now so I can see in dmesg what code is actually being run.
Dude I have no idea how to do this but bump and best of luck
Sent from my PC36100 using XDA App
Isn't this Helping ? http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=blobdiff;f=arch/arm/mach-msm/clock-7x00.c;h=ef178abfcd46cf78dd47962d75298691f887ebf2;hp=d68fea09d1996daeff99365ced9785d65b1cb001;hb=23ff83048726252bc785699fc749a3e364a3bdb0;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
It looks like here he sets the clock writel(grp,MSM_CLK_CTL_BASE+0x84); 0x84
And here is the Orginal topic http://forum.xda-developers.com/showthread.php?t=697673..
fstluxe said:
Isn't this Helping ? http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=blobdiff;f=arch/arm/mach-msm/clock-7x00.c;h=ef178abfcd46cf78dd47962d75298691f887ebf2;hp=d68fea09d1996daeff99365ced9785d65b1cb001;hb=23ff83048726252bc785699fc749a3e364a3bdb0;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
It looks like here he sets the clock writel(grp,MSM_CLK_CTL_BASE+0x84); 0x84
And here is the Orginal topic http://forum.xda-developers.com/showthread.php?t=697673..
Click to expand...
Click to collapse
Yeah I saw that, but that won't work for us, because it is for one of the old MSM7500 chips instead of the new QSD chips we have in Snapdragon devices.
I am working on a few things now and I recommend you check the Nexus forum since that thread is a lot more active.
Geniusdog254 said:
Yeah I saw that, but that won't work for us, because it is for one of the old MSM7500 chips instead of the new QSD chips we have in Snapdragon devices.
I am working on a few things now and I recommend you check the Nexus forum since that thread is a lot more active.
Click to expand...
Click to collapse
okey, But as far as I know that code is not standard... Becouse the Vugue msm7500 device is originally WM device.. so the Smart dzo managed this custom code.
I wil follow the nexus form .. This is Damn interesting !
i wish you guys the best of luck..wish i could help..i love xda..lol
I'm going to bump this, would be nice if more people were working on this.
Man... I absolutely love my phone. It really sux that this even needs to be asked. This device is so much more capable and I cannot understand why HTC would cripple it so badly. Look at the Samsung galaxy s or the Droid x. Or even a more similar phone like the nexus or incredible. They all stomp this phone when it comes to anything graphics wise even if it is just swiping home screens. It makes me sad. Lol
I love how it makes you sad, but you still lol. Lol (correctly placed)
This is big but first let's get a true cap fix!
Sent from my Evo 4G
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
jigglywiggly said:
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
Click to expand...
Click to collapse
I'm thinking this is also one of those things awaiting source. Even the overclocked kernals make my phone reset so I'm waiting for a more stable release myself. Since you're still posting here does that mean you decided to keep your evo?
psych2l said:
I'm thinking this is also one of those things awaiting source. Even the overclocked kernals make my phone reset so I'm waiting for a more stable release myself. Since you're still posting here does that mean you decided to keep your evo?
Click to expand...
Click to collapse
I don't know, yet I am in deep havoc lol. I activated my phone on the 20th. I have till 13th of July to pay my bill, so don't know.
I mean the locked bootloader of the Droid X is kind of lame. Also on the Evo, I have a 10$ discount because of the IO conference... unlimited texts too, and I bought two batteries for it with a charger(for 10$ lol, and they actually last a long time 1500ma, I put the 2 extras in my wallet)
Also I think I can upgrade my phone right away already if I read things right, so if Sprint gets an awesome phone I can upgrade to that whenever.
Verizon is more expensive, but I like how they let me do a 1 year contract. The Droid X is also nicer, I mean it has a better camera, and the mic quality when taking videos isn't piss, hopefully someone fixes that. It also has a real graphics card.
So yeah, it's hard to decide. A better phone, vs saving me some money. Though I plan to attend the IO conference once again. I'm still porting my distrubuted prime client onto Android, hopefully it will be high performance. So it's not like I just go there for a phone ^^. Hell I didn't even know about the phones till they said "Where do you want the Droid delivered" I lol'd. Though my time is limited, summer classes at UC Berkeley are tough : /
jigglywiggly said:
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
Click to expand...
Click to collapse
Yep, looks like til we get the kernel in our hands they're tied.
Also what's the point of overclocking if their is still a limit on FPS..
Eventually this will be the next thing on our todo list
some of the source for the OpenGL ES GPU core was announced as being released today
Qualcomm releases open-source 3D Snapdragon driver
http://www.androidcentral.com/qualcomm-releases-open-source-3d-snapdragon-driver
havent looked at it yet, but im sure in the very least this should at least help shed some more light on overclocking the GPU and add another piece to the puzzle!
git location -
https://www.codeaurora.org/gitweb/q...b819424af4be;hb=refs/heads/android-msm-2.6.32
topdnbass said:
Yep, looks like til we get the kernel in our hands they're tied.
Also what's the point of overclocking if their is still a limit on FPS..
Eventually this will be the next thing on our todo list
Click to expand...
Click to collapse
There isn't really a fps cap with the novatek kernel hack. It made the display much smoother for me and I am using it on EvolutionX. So beast.
Good news about the drivers, maybe we can actually see some overclocking now.
I want this to happen!
Nova runs pretty well on the Evo. Gameloft updated it recently.
I would just like for iphone ports to run well.
I hear the Palm Pixi has the same GPU. It is clocked at 190mhz. What about the Evo?
patelkedar91 said:
I hear the Palm Pixi has the same GPU. It is clocked at 190mhz. What about the Evo?
Click to expand...
Click to collapse
The Pixi doesn't have the same GPU, it has one of the low/mid-range MSM7227 (I think thats the model?) chips. It's similar as it's one of Qualcomms latest gen chips, but it is NOT a Snapdragon so it's different.
Also, the Snapdragon GPU's on HTC devices are clocked as follows:
GRP_CLK: The actual graphics clock, 256mhz
IMEM_CLK: The gpu memory clock, 256mhz
EBI1_CLK: As best I can tell, the bus that the GPU is on is EBI1, this is the clock for it, 128mhz
If you want more info, look here: http://forum.xda-developers.com/showthread.php?t=710850 since that thread is a lot more active, but please don't clutter it, there's actual devving going on there
Thanks for the info. I just wonder how they're going to get 3d games to work on the Pixi then... weird.
It was announced that the Pixi would get 3d gaming with the 1.4.5 update.
Much better (Y)
http://forum.xda-developers.com/and...ck-overclocking-tuning-snapdragon-s1-t2883708
I tried looking for this, but wasnt able to get any hits.
Is the hardware between the SGS and SGS II so different that a stock rom of the SGSII cannot be used as a basis for an SGS rom?
krook1 said:
I tried looking for this, but wasnt able to get any hits.
Is the hardware between the SGS and SGS II so different that a stock rom of the SGSII cannot be used as a basis for an SGS rom?
Click to expand...
Click to collapse
They are totally different phones. different modems, cpu, screen, memory, size, chips, basically every way phones can be different. No way a transfer of a ROM between the two would work.
There is a 2.3.3 ROM that has some of the apps and features of the SGSII called SimplyGalaxyII i think, look in the dev section. THat is the closest we will get.
little8020 said:
There is a 2.3.3 ROM that has some of the apps and features of the SGSII called SimplyGalaxyII i think, look in the dev section. THat is the closest we will get.
Click to expand...
Click to collapse
Yep - http://forum.xda-developers.com/showthread.php?t=1076724 This as about as close as you will get for now.
Thank you.
I was hoping that there was some way based on the sources shared (by Samsung) that a kernel could be built for the Cappy. But it looks like there too many differences to be able to take advantage of the fixes that they've put in.
krook1 said:
Thank you.
I was hoping that there was some way based on the sources shared (by Samsung) that a kernel could be built for the Cappy. But it looks like there too many differences to be able to take advantage of the fixes that they've put in.
Click to expand...
Click to collapse
Do you use the same drivers on your computer for all ati cards just because their built by Ati?
Sent from my SGH-I897 using XDA App
bobtukin said:
Do you use the same drivers on your computer for all ati cards just because their built by Ati?
Click to expand...
Click to collapse
Actually yes. ATI calls their driver package catalyst you and download the same one no matter what ati card you are using.
Drivers are written with various choices in mind (I've written/modified a few myself).
Sometimes vendors create a family of "devices" that can be handled by the same driver. This is either controlled by compile time switches or even run time detection.
At other times, the vendor may develop a brand new hw architecture on a new device, and it may not be worth it to plumb an existing driver with code that runs across multiple device families.
Driver binaries will require device, target CPU arch and kernel APIs to be very close/exact match to be used across systems. Post #2 clarifies that this is not the case.
I did not have knowledge of the devices on the SGS II, and hence the OP: if they differ a lot.
So is the SGSII the next big development platform? That's what I'm hoping, as I'll probably get one come August, assuming they are out.
Just for arguments sake, lets say by some miracle we could get an sgs 2 rom on a cappy. How would it run? It would be expecting a dual core 1.2 ghz not a single 1 ghz, and double the ram. I doubt it would run at all.
krook1 said:
I tried looking for this, but wasnt able to get any hits.
Is the hardware between the SGS and SGS II so different that a stock rom of the SGSII cannot be used as a basis for an SGS rom?
Click to expand...
Click to collapse
Yes, the hardware is so different that ROMs designed for the GS2 will NEVER work on the GS1. Doesn't mean little parts here and there (like TW4 for example) can't be ported from one to the other, but as far as how the ROMs work at the driver level, it isn't possible to port the entire OS base.
</end>
neubauej said:
Just for arguments sake, lets say by some miracle we could get an sgs 2 rom on a cappy. How would it run? It would be expecting a dual core 1.2 ghz not a single 1 ghz, and double the ram. I doubt it would run at all.
Click to expand...
Click to collapse
Touchwiz 4 has already been ported and it runs fine, that's all you're going to get from that rom.
I am posting here as I am not allowed to do so in development subforum.
Anyway, I am the developer of the OpenFIMG project (formerly GLES6410), which is aiming to provide proper OpenGL support on devices with FIMG 3DSE 3D engine, found in S3C6410, S5PC100 and probably also in S5P6442. The project is in a pretty advanced state as it is already capable of running Android 2.3 with hardware acceleration. Still many OpenGL extensions and some core features (like lighting) are still missing. More info can be found here: https://github.com/tom3q/openfimg/wiki.
It is very likely (and almost confirmed) that the SoC used in Galaxy 3 (S5P6442) contains the same GPU as the one in S3C6410, which is the chip inside Galaxy Spica and similar phones, at least basing on what Quadrant and GLbenchmark show and on GL libraries supposed to be dumped from Galaxy 3.
What I am trying to say is that my project may also be useful on Galaxy 3, but I am the only developer working on it and I am doing it in my free time, so it does not progress as fast as one may expect. In other words, I am looking for some other developers interested in this project.
If you are interested, then do not hesitate to drop me a PM.
Mod EDIT : moving this to development
EDIT: Attached some documents about FIMG 3DSE (based on S3C6410 documentation and my reverse engineering)
EDIT: The project has been successfully used on G3. Builds of ICS for G3 use OpenFIMG as primary graphics driver currently and there are update packages for CM7.
Very interesting .. I send you PM.
Galaxy 3 has no GPU.
mpbm23 said:
Galaxy 3 has no GPU.
Click to expand...
Click to collapse
Based on what?
All my sources state that it has exactly the same FIMG 3DSE rev. 1.5 as in S3C6410.
Based on the fact that no site says that the I5800 has a GPU and that graphics on games are really laggy.
Unless you are not talking about a discrete GPU.
No mobile phone contains a discrete GPU. All of them are embedded inside some SoC chip, some are better (SGX, Adreno), some are worse (FIMG 3DSE).
It is exactly the same as with Spica and similar phones. Games are laggy because the hardware is not a speed daemon and the performance is even more impacted by really _broken_ drivers.
Then why nobody write that it has GPU like all the other phones like Galaxy S ,Nexus S etc?
mpbm23 said:
Then why nobody write that it has GPU like all the other phones like Galaxy S ,Nexus S etc?
Click to expand...
Click to collapse
Because it is a low end phone, software support for this GPU is very bad and the GPU itself is not a speed daemon.
tom3q said:
Because it is a low end phone, software support for this GPU is very bad and the GPU itself is not a speed daemon.
Click to expand...
Click to collapse
Okay..so your project involves developing real good drivers so that even the g3 low end gpu can perform better, right?
Sent from the 3rd Galaxy !
Yes. Of course, it will not work on par with Adreno 200 or similar GPUs, but should at least work a bit better. The main target is to run Android 2.3 (and future versions, which will not work will original drivers, because of missing extensions) with full hardware acceleration and without bugs found in Samsung drivers.
Hmmm.. Nice .. Good luck with your project.. One of our devs marcellusbe is working on porting CM7 to G3.. This would surely help him ..
Sent from the 3rd Galaxy !
cool... if so this is gonna make new benchmark .. pun intended ... best of luck man.... I had thought of throwing this phone a long time back but you guys always give hopes... and ofcourse result..
Wow interesting!
This should be moved to dev section I have sent a PM to haree
Cool. So what can others help with?
Too interesting
I'ld like to help with whatever i can
I'll back you up in spirit, sorry,i know nothing about programming
VERY intresting!
and yes the galaxy 3 does have a gpu and yes it has been confirmed (or atleast i heard) that it has this gpu..cant wait to see the outcome!
Actually, I will need some people who would compile, test and eventually fix the code for Galaxy 3, because the only phone with this GPU I have is a Galaxy Spica (i5700) and there may be some subtle differences between them. (Especially in the kernel part, where kernel modules may require changing of some addresses or some other fragments of code.)
Preferably, I would like someone to help me with the project, but I understand this is not an easy task, so not everyone can apply.
I don't mind being a tester
Edit: also will we be able to play gameloft games and nfs shift?
Sent from my GT-I5800 using XDA App
dilzo said:
I don't mind being a tester
Click to expand...
Click to collapse
Nice, thanks.
However, you have to understand that it is not a simple drop-in replacement of standard GL libs. This project replaces the whole graphics subsystem of the phone, including some kernel modules and this makes testing a bit more complicated as it needs pretty big modification of the phone software.
If it is not a problem for you then ok.
dilzo said:
Edit: also will we be able to play gameloft games and nfs shift?
Click to expand...
Click to collapse
It all depends if all the extensions required by these games will get implemented. Also, there may be some problems with screen resolution of Galaxy 3, which is a not standard one. I cannot give any claims regarding the performance as the real performance of this hardware is unknown.