Database Users

Not another Froyo Post..

This isn't a rant or anything, or I won't try to make it one. But I just came across on Android Central that the Droid is getting 2.2.1.
Now this is just so depressing already that we have a phone that's been out for about 5 months now and haven't seen Froyo (only in Unoffical leaked builds). The Droid has been out far longer, I know that. But Samsung is really dragging their feet. Froyo offically, when it comes out, better knock our ****ing socks off or it was a waste of time to wait for them to deliver.
I'm just saying, this just makes Samsung look that much worse.
http://www.androidcentral.com/leaked-android-221-motorola-droid-frg83

so you complain about our leaked ROMs by posting about another phones LEAKED ROM?
Dude... just flash froyo. They are daily drivers and quit posting the same stuff.

The leaked FroYo build is knocking my socks off...
Just sayin'

s15274n said:
so you complain about our leaked ROMs by posting about another phones LEAKED ROM?
Dude... just flash froyo. They are daily drivers and quit posting the same stuff.
Click to expand...
Click to collapse
I didn't mean to bash or knock it. There's nothing wrong with the builds, it'd be nice to have an official build though I guess..

Okay, but is it not ironic you started your non-rant post stating that the Droid was getting 2.1.1 and how it looks bad for Samsung, but you completely ignored the fact it ALSO was a leaked build?
Just let it die..

s15274n said:
Okay, but is it not ironic you started your non-rant post stating that the Droid was getting 2.1.1 and how it looks bad for Samsung, but you completely ignored the fact it ALSO was a leaked build?
Just let it die..
Click to expand...
Click to collapse
K, I'm done.

presence06 said:
The Droid has been out far longer, I know that. But Samsung is really dragging their feet. Froyo offically, when it comes out, better knock our ****ing socks off or it was a waste of time to wait for them to deliver.
Click to expand...
Click to collapse
There's really no debate that Samsung is WAY behind here. Yes. the Droid has been out way longer, but the Incredible and Droid X haven't and they've gotten Froyo a long time ago. Incredible got it around 8/30 and X around 9/21.
Assuming that Samsung does get it out this year, that puts them anywhere from 2-4 months behind the competition, depending on when they do finally release it.
That's really bad. Sure they didn't promise 2.2 at any particular time, but that doesn't mean I don't factor it in when making my next phone purchase. I hope everyone does. If not, it'll give the manufactures even more reason to withhold updates in the future and try to push new phones instead.

Just heard from Cyanogen's twitter that CM6 is finished for the G2. I'm sure the new my touch isn't far behind.
Depressing
Sent from my SGH-T959 using XDA App

s15274n said:
Okay, but is it not ironic you started your non-rant post stating that the Droid was getting 2.1.1 and how it looks bad for Samsung, but you completely ignored the fact it ALSO was a leaked build?
Just let it die..
Click to expand...
Click to collapse
Yeah, but you seem to be ignoring the fact that the Droid already HAS an official Froyo, and the leaked build is a second generation update.
The Vibrant does NOT have an official build, and the way it's going, the Droid X may have Gingerbread before we get an official Froyo build.
How can you even begin to defend Samsung?

Yes, it is "just" another Froyo post. +1 Ignore!
~SB

Geez, people, of course Samsung is going to be behind. Motorola's and HTC's phones all have the same OMAP and Snapdragon cores they've used from the first Droid and Nexus One. No wonder they've all gone to Froyo before Samsung.
How many phones used the Hummingbird before the Galaxy S line? None. But I'll bet you that future updates will come faster now they've got Froyo figured out.
Sent from my SGH-T959 using XDA App

Kubernetes said:
Geez, people, of course Samsung is going to be behind. Motorola's and HTC's phones all have the same OMAP and Snapdragon cores they've used from the first Droid and Nexus One. No wonder they've all gone to Froyo before Samsung.
How many phones used the Hummingbird before the Galaxy S line? None. But I'll bet you that future updates will come faster now they've got Froyo figured out.
Click to expand...
Click to collapse
LOL....
Strange reasoning, since Samsung developed the chip themselves, so they should know it better. Plus, they've had a long time to figure Froyo out. And still haven't, officially.

MacGuy2006 said:
LOL....
Strange reasoning, since Samsung developed the chip themselves, so they should know it better. Plus, they've had a long time to figure Froyo out. And still haven't, officially.
Click to expand...
Click to collapse
Designing the chip and modifying the software to work with the hardware are two different things. Just because you know the hardware, doesn't mean it's easy to make the software work with it nicely.

Only thing wrong with these threads is they are always full of hearsay. Rarely anyone states fact, just opinion. Who says sammy is holding it back? The leak came from tmo right? this pessimistic view is what makes ppl always have that "omg I have froyo & I hate it, its not perfect.... I want gingerbread" mentality. Life lesson, you'll never be happy with this attitude.
I, myself, try to look at the recent events of the "rumoured nexus s" that engadget posted pics. If this does happen to grace the GS community think of how fast, far, & easily we may make it to 2.3! Im no tech & I may be way off, but id like to think that this would give us the OPEN "NEXUS" development base we'd need to achieve that level of vanilla android base w/ drivers, code & hopefully working gps ;j (minus the new chipset, obviously).
Just be glad that we do have devs who do what they can & hope that sammy doesn't do anything else to screw us. I will be hoping (but not holding my breathe) for a nexus $ gingerbread port.

DKYang said:
Designing the chip and modifying the software to work with the hardware are two different things. Just because you know the hardware, doesn't mean it's easy to make the software work with it nicely.
Click to expand...
Click to collapse
Exactly. Remember that Froyo was actually built for the Snapdragon, whereas most of the GS hardware is unlike that seen in other previous phones.
Sent from my SGH-T959 using XDA App

If theres a leaked froyo it means Samsung has fine their part. Its up to tmo to push it out.
--
Sent from Vibrant ~ XDA App

DKYang said:
Designing the chip and modifying the software to work with the hardware are two different things. Just because you know the hardware, doesn't mean it's easy to make the software work with it nicely.
Click to expand...
Click to collapse
Apple doesn't seem to have any problems with doing this. Samsung is way bigger. They should have their crap together
Sent from my SGH-T959 using XDA App

Tempestrs4 said:
Apple doesn't seem to have any problems with doing this. Samsung is way bigger. They should have their crap together
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yey but we get to modify the crap out of one of the fastest phones with one of the best screens, and do whatever we want with it, thanks to some great sharing devs, to a device that's almost un- brickable.
Now thats fun!
Apple crapple, great form and simply reliable yet unbendable device to buy all things Apple dollars via only iTunes. No thanks. I'll take what Samsung doesn't have together.
Yes I've complained before but now I have learned a bit more and I have Froyo.
Sent from my SGH-T959 Obsidian V2 Froyo (for now) using the XDA App

How come none of the people that rant about not having an official Froyo release remember that 1. we have they best hardware of any phone out, I can't recall how many times I've heard owners of other phones complain that they've run out of room for their apps because they only have 2gb internal storage, and 2. this site is XDA Developers not XDA stock software release news. If you want to rant about the official release go over to the T-Mobile or Samsung forums and do it.
Sent from my SGH-T959 running Obsidian V2 w/ Froyo Core 1.2ghz using XDA App

12paq said:
Yey but we get to modify the crap out of one of the fastest phones with one of the best screens, and do whatever we want with it, thanks to some great sharing devs, to a device that's almost un- brickable.
Now thats fun!
Apple crapple, great form and simply reliable yet unbendable device to buy all things Apple dollars via only iTunes. No thanks. I'll take what Samsung doesn't have together.
Yes I've complained before but now I have learned a bit more and I have Froyo.
Sent from my SGH-T959 Obsidian V2 Froyo (for now) using the XDA App
Click to expand...
Click to collapse
The devs have no choice but to share. Voiding warranties is uncool for many of us.
Sent from my SGH-T959 using XDA App

[Q] Does anyone think it's worth it.....

to switch from a vibrant to a nexus s? It seems like it's roughly the same phone with some changes like the ffc and curved screen, but running vanilla android 2.3 should make updates come early and often.

Personally, it's going to be hard for me to decide until concrete specs for the Nexus S come out. So far I've seen two sets of specs, which would pretty much make the decision for me:
Set 1:
This is the set thats similar to the Galaxy S. Single core processor, 5MP camera, etc
Set 2:
This set is supposedly similar to the "Galaxy S 2". Dual core processor, 8MP camera, etc.
If it's a marginally different Galaxy S, I'll probably stick to my Vibrant. But if the dual-core version of the specs is correct, I think I'd probably switch.

khulsey said:
to switch from a vibrant to a nexus s? It seems like it's roughly the same phone with some changes like the ffc and curved screen, but running vanilla android 2.3 should make updates come early and often.
Click to expand...
Click to collapse
For me, it really depends on two things:
1) Will the location hardware work better? I'm sick of the crummy GPS/compass on the Vibrant, and I'm certainly not going to upgrade to another phone that has the same problems.
2) Will we ever get a full-from-AOSP build for the Vibrant (e.g. Cyanogenmod)? If we can run AOSP, we don't have to wait for table scraps from Samsung before we can upgrade, and the Nexus S's software advantage is mitigated.
If the Nexus S's GPS isn't a substantial improvement, I'll skip it and live with the Vibrant until something better shows up (or, by that time, something like the MyTouch 4G will probably be running CM, so that's another option).

Ilmoran said:
Personally, it's going to be hard for me to decide until concrete specs for the Nexus S come out. So far I've seen two sets of specs, which would pretty much make the decision for me:
Set 1:
This is the set thats similar to the Galaxy S. Single core processor, 5MP camera, etc
Set 2:
This set is supposedly similar to the "Galaxy S 2". Dual core processor, 8MP camera, etc.
If it's a marginally different Galaxy S, I'll probably stick to my Vibrant. But if the dual-core version of the specs is correct, I think I'd probably switch.
Click to expand...
Click to collapse
same is see it as well, probably no need to update if its basically the same phone with a front camera,
does anyone know and estimated release date? ive googled and found 11/14, obviously that didnt happen lol

JeremyNT said:
2) Will we ever get a full-from-AOSP build for the Vibrant (e.g. Cyanogenmod)? If we can run AOSP, we don't have to wait for table scraps from Samsung before we can upgrade, and the Nexus S's software advantage is mitigated.
If the Nexus S's GPS isn't a substantial improvement, I'll skip it and live with the Vibrant until something better shows up (or, by that time, something like the MyTouch 4G will probably be running CM, so that's another option).
Click to expand...
Click to collapse
Just FYI - getting a full form AOSP build for the vibrant will not mitigate the software advantage. What we need are the source drivers for every version of android.
We already have AOSP for the vibrant but they're based on leaked sources. Once the 2.2 source drivers drop we'll be able to do what we want but will then have to wait for the 2.3 source drivers to drop as well. We'll always be a couple of steps behind.
Now if the source drivers for the galaxy s 2 work for our phones then it wouldn't even matter, we'd practically get updates at the same time.
MyTouch 4G is already running cyanogen mod, just a matter of time now before they release it publicly.

the nexus s looks like a fisher price toy
i'll probably stick with the vibrant as long as the devs keep cranking out these great ROMs. the good thing about the nexus s is that we might get the code more optimized for the hummingbirds. i'm never going to use a FFC camera anyway, so i'm quite content with the vibrant

jrizk07 said:
Just FYI - getting a full form AOSP build for the vibrant will not mitigate the software advantage. What we need are the source drivers for every version of android.
We already have AOSP for the vibrant but they're based on leaked sources. Once the 2.2 source drivers drop we'll be able to do what we want but will then have to wait for the 2.3 source drivers to drop as well. We'll always be a couple of steps behind.
Now if the source drivers for the galaxy s 2 work for our phones then it wouldn't even matter, we'd practically get updates at the same time.
MyTouch 4G is already running cyanogen mod, just a matter of time now before they release it publicly.
Click to expand...
Click to collapse
See, I don't understand why that's the case. If we have the source code for GPS drivers in current kernels (we do, don't we?), we should be able to integrate it with later kernel source trees. It's work, and it's a bit above my pay grade, but it's not like it's impossible.
Now if all Samsung is giving us is blobs (as with RFS, which does remain a problem) that's a different matter, but that's not how I understood the situation.

JeremyNT said:
See, I don't understand why that's the case. If we have the source code for GPS drivers in current kernels (we do, don't we?), we should be able to integrate it with later kernel source trees. It's work, and it's a bit above my pay grade, but it's not like it's impossible.
Now if all Samsung is giving us is blobs (as with RFS, which does remain a problem) that's a different matter, but that's not how I understood the situation.
Click to expand...
Click to collapse
You're right about having the GPS drivers in current 2.1 kernels. We don't have sources for 2.2 besides the leaked ones which are unofficial.
Then again the GPS issue is a software issue, not a driver issue.
Just hang tight and once the official source drivers get released you'll see how fast things start getting developed.
Hopefully the new nexus s will have similar drivers to ours.

Get it for the rearranged soft keys
Sent from my SGH-T959 using XDA App

khulsey said:
to switch from a vibrant to a nexus s? It seems like it's roughly the same phone with some changes like the ffc and curved screen, but running vanilla android 2.3 should make updates come early and often.
Click to expand...
Click to collapse
if its dual core:yes
if its single core:no

khulsey said:
to switch from a vibrant to a nexus s? It seems like it's roughly the same phone with some changes like the ffc and curved screen, but running vanilla android 2.3 should make updates come early and often.
Click to expand...
Click to collapse
i'm only able to get a new phone once every 2 years. though i want to, i cant.
if it still has lag like the current galaxy s models, then definitely not, regardless of hardware

I'll buy ur vibrant and u can buy ur nexus for much cheaper
Sent from my SGH-T959 using XDA App

Nexus S and Vibrant

I still think vibrant is better than nexus s besides 2.3!!
still the same 16gb, no sd card, no 720p, nfc is just a receiver only (i read somewhere)
http://androidapproved.com/item/nexus-s-vs-galaxy-s-vs-nexus-one/

me keeping my vibrant

I know everyone is going to beat this topic to death. Is there any reason to grab the nexus if you have a vibrant. Is there anything besides the FFC.

As long as there are drivers available for the BT/WIFI/GPS, there is no need to get the Nexus S if you have a Vibrant. The rom will be ported to us anyway.

intruda119 said:
I know everyone is going to beat this topic to death. Is there any reason to grab the nexus if you have a vibrant. Is there anything besides the FFC.
Click to expand...
Click to collapse
there is flash. there is 2.3 and there will be future updates as well. i also think it looks much better then Vibrant.

richiehd said:
As long as there are drivers available for the BT/WIFI/GPS, there is no need to get the Nexus S if you have a Vibrant. The rom will be ported to us anyway.
Click to expand...
Click to collapse
the question is when ? It took a long time and very buggy releases from Galaxy S Froyo until finally Vibrant leaks started to come out. When do you think they will leak 2.3......even 2.2 is not out yet.....
so porting from Nexus S might not be as easy as it looks......

kolyan said:
there is flash. there is 2.3 and there will be future updates as well. i also think it looks much better then Vibrant.
Click to expand...
Click to collapse
I agree with the Nexus does look better then the vibrants iphone look. Dont we have flash on vibrant or am I missing something. And soon as the Chefs around here get a smell of 2.3 it wont be long until its on vibrant.
Is the cpu any faster? Adding ffc mod to Vibrant makes it a Nexus right?

Camera flash..i think he means.

intruda119 said:
I agree with the Nexus does look better then the vibrants iphone look. Dont we have flash on vibrant or am I missing something. And soon as the Chefs around here get a smell of 2.3 it wont be long until its on vibrant.
Is the cpu any faster? Adding ffc mod to Vibrant makes it a Nexus right?
Click to expand...
Click to collapse
Camera flash we dont have. 2.1 also does not have Adobe Flash, only 2.2. They also added NFC which is useless to most, SAMOLED class is curved (which i think is cool), FFC is there, 3.0 bluetooth was taken out and replaced with 2.1....no biggy here. Everything else is the same.
Onces I play with it in store, i will know for sure if i want it. I hate how Vibrant feels in hand, if Nexus S is the same, then no go.....

The point of the Nexus S is that it a bare bones Android phone. Meaning there is little in the way of Samsung and T-mobile, or other carriers. This means ideally that as soon as Google releases an update it should be realitively quick to get it to Nexus S. As opposed to the Vibrant that we are still waiting on amn official release. My understanding anyway I could be wrong.

Well I'm getting one just to have a working GPS at the least... I hope to god they've rectified that train wreck.

dinan said:
Well I'm getting one just to have a working GPS at the least... I hope to god they've rectified that train wreck.
Click to expand...
Click to collapse
dont know about that...... hardware should be the same. only time will tell.
ps. NS also lacks SD Card slot.....

If only for the support, I agree. I wonder, will it support at&t frequencies?
Sent from my SGH-T959 using XDA App

Cant use my 32 gig sd card full of videos and music. Humm, thats a deal breaker. Plus no dual core cpu? No 720P? pffft.
But it is the new test phone, so it will always have the latest and greatest. I still dont have a real Cyanogen 6.x for my vibrant.

I see no compelling reason to go from a Galaxy S to the Nexus S. FFC is useless to me and can be added anyway. Camera flash is no big deal. First crack at the Google software is the big seller, but that's mostly just geek cred not particularly useful. I'm happy with the modified ROMS on the Vibrant. Lack of SD card hurts the Nexus. NFC will be useless for a while.
However if I didn't already have a Galaxy S I'd be looking at the Nexus S if only to get a working GPS... presumably. Have to wait for some real world reviews.

Personally I dont need a ffc or a flash, my sister has an evo and she uses her ffc maybe twice a month. I almost never use the camera in dim light conditions plus the night vision on the vibrant is good enough. Similar 1ghz processor, 512ram, no sd card is killing me!! eventually 2.3 will be ported to vibrant just a matter of time!!
ps gps issue has been addressed in almost every rom in the dev section.

kolyan said:
the question is when ? It took a long time and very buggy releases from Galaxy S Froyo until finally Vibrant leaks started to come out. When do you think they will leak 2.3......even 2.2 is not out yet.....
so porting from Nexus S might not be as easy as it looks......
Click to expand...
Click to collapse
It's not "easy" but easier than you're making it sound. Your comparison is irrelevant. The reason froyo took so long to port over was differences in the device we were porting from, and once the JK2 froyo build leaked, it was running near perfect on the vibrant the same day. 2.3 is out and released already and the device we'd be porting it from has an almost identical setup and also is compatible with the T-mobile network from the get go etc etc. I'd say there's gonna be some sort of working port by the end of the year without a doubt.

On the google page about the Nexus S it said that it featured wifi hotspot without additional fees from carriers. If the Nexus S is ported to the vibrant any chance that feature could be included too?

joe.kerwin said:
It's not "easy" but easier than you're making it sound. Your comparison is irrelevant. The reason froyo took so long to port over was differences in the device we were porting from, and once the JK2 froyo build leaked, it was running near perfect on the vibrant the same day. 2.3 is out and released already and the device we'd be porting it from has an almost identical setup and also is compatible with the T-mobile network from the get go etc etc. I'd say there's gonna be some sort of working port by the end of the year without a doubt.
Click to expand...
Click to collapse
How is Galaxy S different from Vibrant vs Nexus S different from Vibrant ?
port from Galaxy S was never working 100% until Vibrant Froyo (JK2) leaked. GPS wasnt working, all buttons were messed up, 3.5mm jack wasnt fully functional...etc. and 2.3 Vibrant leak is NOT coming in near future or most likely EVER.

people are speculating that it may be difficult to port 2.3 over to vibrant si,ply be cause it uses iNAND flash memory but IDK im no developer
have to wait and see when its released
Also specs might be very similar but we dont know on how similar the hardware is...drivers could still be incompatible with galaxy S hardware
I wouldn't expect to see samsung release 2.3 for galaxy S line of phones IMO they probably have some sort of deal with google to exclusively have 2.3 on nexus S and google would lose sales if galaxy S got 2.3 as an OTA

Full in depth Nexus S review.

Nexus S gets a small preview?
http://www.engadget.com/2010/11/11/nexus-s-for-t-mobile-gets-brief-best-buy-mobile-nod-there-and-g/
Well, this was rather unexpected. Earlier today, Best Buy Mobile published a humble (if not incomplete) ad for the "Nexus S for T-Mobile," touting both its "pure Google" experience (i.e. vanilla Android) and holiday availability exclusively from Best Buy. It's gone now, saved only by the grace of Google cache. To be honest, all we can do is speculate beyond that. An anonymous tipster to RadioAndroid pegged the Nexus S name late last month and claimed it would feature Android 2.3 Gingerbread, a 4-inch Super AMOLED screen, and a Hummingbird processor. TechCrunch later described a Samsung-borne "Nexus Two" that has since been delayed due to some serious hardware issue. Is this a placeholder from the online devs? Does / did the S stand for Samsung, or something else entirely? And most importantly, is this presumed follow-up to Nexus One actually coming out, or did you just get your hopes up for nothing?
Click to expand...
Click to collapse

I am not out to give people more hope than necessary but I think that google releasing this phone as sheep in galaxy clothing is the best news galaxy owners could get. Development of the hummingbird platform, gingerbread...... Huge opportunities here
Sent from my GT-I9000 using Tapatalk

http://www.engadget.com/2010/11/11/is-this-the-nexus-s/
An update!

Now it only remains to be seen how similar the hardware on this bad-boy is to the Galaxy S's that we already have for the inevitable rom-porting. With any luck we'll be rolling in Gingerbread before we know it.

http://www.engadget.com/2010/11/11/is-this-the-nexus-s/
Now on the web flyer, looks pretty vanilla to me!

Engadget is on fire!!
http://www.engadget.com/2010/11/11/google-nexus-s-is-the-samsung-gt-i9020/

This is nice. Like a dream come true!
http://www.engadget.com/2010/11/11/this-is-the-nexus-s/

Again!"
http://www.engadget.com/2010/11/11/this-is-the-nexus-s/

Thank God for 30 day return policies. Goodbye vibrant, hello Nexus S
Sent from my Nexus One using XDA App

Now the cynic in me is starting to feel that Samsung may be deliberately crippling Galaxy S performance to make the Nexus S look even more beastly when it comes out and make people want to buy it.

Intratech said:
Now the cynic in me is starting to feel that Samsung may be deliberately crippling Galaxy S performance to make the Nexus S look even more beastly when it comes out and make people want to buy it.
Click to expand...
Click to collapse
Well, basically, Android was built and optimised for Nexus One, it surely is not performing to it's maximum on the hardware of Samsung. The hardware of SGS is realy good, but the OS is not (yet) optimised for it.
But if you built and optimise the OS around this hardware, i'm pretty sure it'll fly! (and it'll give optimised OS to samsung's users as well)

Anyone know the specs
Sent from my HTC Glacier using XDA App

t1mman said:
Well, basically, Android was built and optimised for Nexus One, it surely is not performing to it's maximum on the hardware of Samsung. The hardware of SGS is realy good, but the OS is not (yet) optimised for it.
But if you built and optimise the OS around this hardware, i'm pretty sure it'll fly! (and it'll give optimised OS to samsung's users as well)
Click to expand...
Click to collapse
Have you seen what CyanogenMOD are doing and the performance they are getting with an unoptimised, incomplete, Android 2.2.1 ROM on the Galaxy S using RFS file system? They put the Samsung software development team to shame.

Now post me a link to a Gingerbread ROM I can slap on my Captivate ASAP.

Intratech said:
Have you seen what CyanogenMOD are doing and the performance they are getting with an unoptimised, incomplete, Android 2.2.1 ROM on the Galaxy S using RFS file system? They put the Samsung software development team to shame.
Click to expand...
Click to collapse
CyanogenMOD are putting every dev team to a shame!

Now the cynic in me is starting to feel that Samsung may be deliberately crippling Galaxy S performance to make the Nexus S look even more beastly when it comes out and make people want to buy it.
Click to expand...
Click to collapse
Not really dude. This will be a low-volume device compared to the "regular" Galaxy S line.
Looking at some of those pics, there's quite a bit of internal differences. No visible SD card slot, for one, and a different battery (with power connectors on the left instead of top of the phone). That makes me wonder how much the rest of the internal hardware differs.
It's also bulkier at the bottom than an I9000, and looks to have antenna leads on the battery cover (like the Captivate), though those might be DTV leads instead.

http://www.engadget.com/2010/11/11/this-is-the-nexus-s/
Confirmed
Sent from my GT-I9000 using XDA App

nCoder said:
http://www.engadget.com/2010/11/11/this-is-the-nexus-s/
Confirmed
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Nothing is confirmed if not from Samsung or Google
Update: We contacted Google for comment and were told that the company doesn't comment on rumors or speculation -- the usual drill.
Click to expand...
Click to collapse
But still, it looks good so far!

Intratech said:
Now the cynic in me is starting to feel that Samsung may be deliberately crippling Galaxy S performance to make the Nexus S look even more beastly when it comes out and make people want to buy it.
Click to expand...
Click to collapse
i agree ....they are not fixing the filesystem lag issue because they are already thinking of future sales of new models, they want to keep it crippled, typical samsung.
on another note i much prefer the samsung's touchwiz additions to stock android, the apps are better (calendar for example) and there are more built in apps.
if only not for the lag

t1mman said:
Nothing is confirmed if not from Samsung or Google
But still, it looks good so far!
Click to expand...
Click to collapse
What looks good? I believe you don't mean that stretched Nokia 5800XM...

Nexus S on Galaxy S [i9000] feat Supercurio

http://forum.xda-developers.com/showthread.php?t=877800
The dude has it working.
The dude abides.
Cheers
Edit:
He has pushed the latest initramfs : https://github.com/project-voodoo/nsonsgs-initramfs
Not flashable with Odin Yet.. He will do that tomorrow.
Galaxy S with Nexus S kernel - Booting Nexus S Android Gingerbread
Videos are here:
http://www.youtube.com/supercurioxda

There are like two more other threads about this. Wrong section as well.
It's cool that it's ported but it is far from being a daily driver.

Nice to keep us updated as this is the only forum I check for anything vibrant.
Sent from my SGH-T959 using Tapatalk

i think this is the right spot for this but the thing is it's only a headsup for what might be to come. looking forward to what our mods are going to be like though so...
whhooopity doo

I'd love to go ahead and just install this. But it'll prolly cause a myriad of problems on my non i-9000 phone :'(

Is it really THAT hard to dev on samsung devices? Im super greatful for all the great roms that the devs have for us, but im seeing reports all over of stable gingerbread ports to multiple devices, heck even the CLIQ has a gingerbread port before the devices which the Ns is based on.
Sent from my SGH-T959 using XDA App

nonmindo said:
Is it really THAT hard to dev on samsung devices? Im super greatful for all the great roms that the devs have for us, but im seeing reports all over of stable gingerbread ports to multiple devices, heck even the CLIQ has a gingerbread port before the devices which the Ns is based on.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I was just thinking the same thing. The HD2 has it running already with only GPS broken, Built from nexus s source.

nonmindo said:
Is it really THAT hard to dev on samsung devices? Im super greatful for all the great roms that the devs have for us, but im seeing reports all over of stable gingerbread ports to multiple devices, heck even the CLIQ has a gingerbread port before the devices which the Ns is based on.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
what ? point me one working port. You can port Gingerbread to anything you what but nothing is gonna work except the OS

Just give it time. The nexus s is the best thing to happen to us galaxy s users. The nexus s has the same cpu as the galaxy s no? That is a Huge step in the right direction.
I believe in our developers. Its not easy I'm sure, but with patience and respect I'm confident in their ability to deliver us some awesome work.
Sent from my SGH-T959

kolyan said:
what ? point me one working port. You can port Gingerbread to anything you what but nothing is gonna work except the OS
Click to expand...
Click to collapse
you said just one
http://www.xda-developers.com/android/gingerbread-ported-to-htc-hd2/

it is simple,,, SGS 'Developers' are not that good....,, we do not even have a fully functional CM6,,, what will you expect...

rsfaze said:
you said just one
http://www.xda-developers.com/android/gingerbread-ported-to-htc-hd2/
Click to expand...
Click to collapse
this is a bit different i guess. its ported from Nexus One leak or something and hardware is the same. NS and Galaxy have many differences in hardware.

eortizr said:
it is simple,,, SGS 'Developers' are not that good....,, we do not even have a fully functional CM6,,, what will you expect...
Click to expand...
Click to collapse
don't complain if you aren't going to help by developing either.. they all do this for free and not asking people to pay for their hard work.

Did anyone take the i9000 first release out for a test drive on the Vibrant?

zephiK said:
don't complain if you aren't going to help by developing either.. they all do this for free and not asking people to pay for their hard work.
Click to expand...
Click to collapse
The problem is most of the "Developers" aren't Developers at all. They're themers and modders.
The reason why there aren't so many good developers for Galaxy S is because the hardware varies too much across the variants (pun unintended).
You can pretty much just think of them as different phones alltogether, because having the same SoC isn't really that much of a biggie. Different phones from different manufacturers can have the same SoC, but that doesn't mean the ROMs will gracefully port from one device to another.
The HD2 is an outliner, because it uses a popular SoC and the phone was released quite a bit before a slew of Android phones were released using similar SoCs (that, and HTC based later phones on similar hardware). It made the ROMs easy to port to that phone, and it made sure the system ran with acceptible performance (due to Google developing on similar hardware).

N8ter said:
The problem is most of the "Developers" aren't Developers at all. They're themers and modders.
The reason why there aren't so many good developers for Galaxy S is because the hardware varies too much across the variants (pun unintended).
You can pretty much just think of them as different phones alltogether, because having the same SoC isn't really that much of a biggie. Different phones from different manufacturers can have the same SoC, but that doesn't mean the ROMs will gracefully port from one device to another.
The HD2 is an outliner, because it uses a popular SoC and the phone was released quite a bit before a slew of Android phones were released using similar SoCs (that, and HTC based later phones on similar hardware). It made the ROMs easy to port to that phone, and it made sure the system ran with acceptible performance (due to Google developing on similar hardware).
Click to expand...
Click to collapse
+1............