Related
So I've been messing around trying to see what I can get going on the froyo front and I'm running into some problems....
first off, froyo isn't a huge fan of the galaxy s hardware...in AVD, when I create the profile in terms of the captivate hardware and it is buggy even in emulation...this doesn't bode well for actual hardware use. Maybe I'm just really bad at development but I dunno...
So secondly, on the phone itself I thought i'd try to just send over the image to see if the phone would even accept it. While the bootloader seems to be fine and not too worried about accepting an image (the touchwiz 2.1) it doesn't want to accept the buggy froyo.
So i've given it some shots, but its gonna take someone or a group of people who're smarter than me to see why the bootloader isn't really unlocked and why the avd doesn't like the galaxy s hardware specifications
I brought up the possibility of not being able to run Froyo without it being officially released by Samsung first on the Phandroid forums and repeatedly was assured that it'd only be a matter of time until Froyo was released on it.
This is disappointing
Intervenient said:
I brought up the possibility of not being able to run Froyo without it being officially released by Samsung first on the Phandroid forums and repeatedly was assured that it'd only be a matter of time until Froyo was released on it.
This is disappointing
Click to expand...
Click to collapse
well it should work without it being specifically released (see aria, and every old HTC) but for some reason it's not. I'm probably just doing something wrong... i was a WM dev then an iPhone dev, I'm just learning the whole android development stuff
Read up on behold 2 development on androidforums.com and Eugene_ 373's forum on androidspin.com its very similar in structure to the galaxy s brand of phones. You can't expect Samsung phones and HTC phones to be in anyway simular. They use different file systems and partitions. So it is not a cut and paste job you need to do some heavy hacking.
psychoace said:
Read up on behold 2 development on androidforums.com and Eugene_ 373's forum on androidspin.com its very similar in structure to the galaxy s brand of phones. You can't expect Samsung phones and HTC phones to be in anyway simular. They use different file systems and partitions. So it is not a cut and paste job you need to do some heavy hacking.
Click to expand...
Click to collapse
Do you think it can be done? Will we see Froyo before Samsung releases it?
Intervenient said:
Do you think it can be done? Will we see Froyo before Samsung releases it?
Click to expand...
Click to collapse
I and pretty much everyone that has followed the behold 2 debacle on androidforums.com have major doubts but I still believe there is potential. That's as much as I can say because some people on here don't like the fact that I don't have the same blind optimism as they do.
Also here are some posts that might help
http://forum.androidspin.com/showthread.php?p=12840#post12840
http://androidforums.com/all-things-root-behold-2/
http://androidforums.com/all-things-root-behold-2/63246-dev-needed-2-1-running-behold-2-a.html
Also I still might get a captivate if some good dev work is done. I don't need froyo before Samsung releases it and most of the added function provided by hacked and rooted roms can be added on to samsung roms. I am not getting a new phone for another month so if it looks like there is a lot of dev work done to this phone by then I will stay Samsung even though it might not get gingerbread.
psychoace said:
I and pretty much everyone that has followed the behold 2 debacle on androidforums.com have major doubts but I still believe there is potential. That's as much as I can say because some people on here don't like the fact that I don't have the same blind optimism as they do.
Also here are some posts that might help
http://forum.androidspin.com/showthread.php?p=12840#post12840
http://androidforums.com/all-things-root-behold-2/
http://androidforums.com/all-things-root-behold-2/63246-dev-needed-2-1-running-behold-2-a.html
Also I still might get a captivate if some good dev work is done. I don't need froyo before Samsung releases it and most of the added function provided by hacked and rooted roms can be added on to samsung roms. I am not getting a new phone for another month so if it looks like there is a lot of dev work done to this phone by then I will stay Samsung even though it might not get gingerbread.
Click to expand...
Click to collapse
Just doing a quick Twitter search for "iphone captivate" yields 80% of the peope tweeting something along the lines of leaving their iPhone 4 for a captivate. Lets hope the Dev's share the same thoughts.
Hey I would just like to know if the Galaxy S has something. Can you go into Apps managment and look for an app called "device managment"? If it's there and at 40+ mb's then that is a recovery rom. It is a duplicate of your starting rom. You can clear it most likely to regain space but after a reboot it will come back. There is another partition on the phone that stores the rom and the phone will run a check on boot up to make sure it's there. If not then it replaces it. It can be hacked out permanently but I know the Galaxy S doesn't really have any issues about storage space.
psychoace said:
I and pretty much everyone that has followed the behold 2 debacle on androidforums.com have major doubts but I still believe there is potential. That's as much as I can say because some people on here don't like the fact that I don't have the same blind optimism as they do.
Also here are some posts that might help
http://forum.androidspin.com/showthread.php?p=12840#post12840
http://androidforums.com/all-things-root-behold-2/
http://androidforums.com/all-things-root-behold-2/63246-dev-needed-2-1-running-behold-2-a.html
Also I still might get a captivate if some good dev work is done. I don't need froyo before Samsung releases it and most of the added function provided by hacked and rooted roms can be added on to samsung roms. I am not getting a new phone for another month so if it looks like there is a lot of dev work done to this phone by then I will stay Samsung even though it might not get gingerbread.
Click to expand...
Click to collapse
Very much apperciated, and the links were helpful on how this all will go down. This greatly changes on if I'll keep my Captivate. I know you should be happy with the phone you have, not the one you'll get, but I don't think I can stomach having a phone that won't be supported come Q4.
If the galaxy phones sell well it will be supported. They do have some phones that have gone from 1.5 to 2.1. Just don't expect any haste out of there crew
The fact that there will be an official release of 2.2 is whats keeping most devs from putting time into it. I know I wouldn't want to put a lot of effort into something just to have an official release come out before development is done.
Phlip00ws6 said:
The fact that there will be an official release of 2.2 is whats keeping most devs from putting time into it. I know I wouldn't want to put a lot of effort into something just to have an official release come out before development is done.
Click to expand...
Click to collapse
true...
I was just messing around with the sdk and whatnot and thought what the hell I have a spare I might as well try
but i guess it's above my head. I'm gonna keep reading up on it though, I'm not the best coder (my expertise lies in c++) but I can surely give it a shot
Phlip00ws6 said:
The fact that there will be an official release of 2.2 is whats keeping most devs from putting time into it. I know I wouldn't want to put a lot of effort into something just to have an official release come out before development is done.
Click to expand...
Click to collapse
Tell that to Cyanogen and Avalaunchmods and Herver who are all making FroYo ROMs for the Evo.
This sucks. I was kinda looking into replacing my 9700 with the Captivate and keeping at&t and Sprint both...
Phlip00ws6 said:
The fact that there will be an official release of 2.2 is whats keeping most devs from putting time into it. I know I wouldn't want to put a lot of effort into something just to have an official release come out before development is done.
Click to expand...
Click to collapse
wrong.
See above post and also thing about the nexus one. 2.2 was released via cyanogen before it was officially released to the public.
And why would you want the official release from Samsung, which would still have the ATT junk and TW3.0, I want STOCK.
andy2na said:
wrong.
See above post and also thing about the nexus one. 2.2 was released via cyanogen before it was officially released to the public.
And why would you want the official release from Samsung, which would still have the ATT junk and TW3.0, I want STOCK.
Click to expand...
Click to collapse
Yeah being able to remove the bloatware and using launcher pro and some of the stock Android apps like music is nice but still having to leave any TouchWiz stuff there is annoying. It will be the same on the official release just with 2.2 so I don't see why there wouldn't already be development for a custom ROM for captivate based off the stock Froyo 2.2 straight from Google. In fact this reminds me that I need to keep reading up and playing around so I might be able to do something even though it would only be for future development.
I'm not as concerned about 2.2 as 3.0...
If someone can get 2.2 running on this, then it bodes well for getting 3.0 running on this as well.
TexUs said:
I'm not as concerned about 2.2 as 3.0...
If someone can get 2.2 running on this, then it bodes well for getting 3.0 running on this as well.
Click to expand...
Click to collapse
This. I'd love to see Gingerbread on this phone.
I have been into HTC bandwagon for quite some years and I've learned that every HTC device that I owned have been hacked to run on new OS that isn't designed for it. I am wondering how likely developers can homebrew their SGS from Eclair to Froyo to Gingerbread, IF Samsung never leaks or release these upgraded firmwares.
Don't get me wrong, I'm still very much in love with SGS but I just couldn't make up my mind between HTC Desire and SGS, especially in its future software upgrades.
mengsuan said:
I have been into HTC bandwagon for quite some years and I've learned that every HTC device that I owned have been hacked to run on new OS that isn't designed for it. I am wondering how likely developers can homebrew their SGS from Eclair to Froyo to Gingerbread, IF Samsung never leaks or release these upgraded firmwares.
Don't get me wrong, I'm still very much in love with SGS but I just couldn't make up my mind between HTC Desire and SGS, especially in its future software upgrades.
Click to expand...
Click to collapse
If you are looking for long-term suppor the Desire is probably bettor of since it has almost the same hardware as the Nexus One, and the roms for the nexus are pretty easily hacked onto the Desire.
If you check on the Dev section, you will see that Samsung have already leaked pre-beta copies of Froyo, and as for Gingerbread, until the specs are confirmed no-one knows if the hardware requirements are within the spec of any current phone.
As post #2 says, Desire would be a safer choice.
Even as of now, there are no available custom roms for SGS. Only mods of the existing leaks. That might change in the future, but let's comment on the current situation.
If you want quicker / faster Firmware release, pick Nexus One or HTC Desire.
Nexus One get the most latest update from Google OTA.
And HTC Desire is the little twin brother that born few months later with a very similar hardware space. + HTC Desire has few famous custom ROM writer that release nightly build firmware if you want to take the risk and challenge.
Now that SamsungFirmware has stopped the leak of beta firmware.
"Samsung NOT happy with 2.2 rom leaks for Galaxy S. We will wait for more sorry guys we dont want trouble "
http://twitter.com/SamsungFirmware/status/20208457619
I've been installing Froyo Roms coutesy of FusionRom and Froydvillain makers for a while now on my Hero. It's now time for an upgrade...
I know that Android 3.0 is coming "soon" and will supposedly be released this year - maybe with next couple of months but info is very thin on the ground.
Wondering if anyone knows if Android 3.0 devices will be released this year or is it just the Software that will be released and announced?
I'm holding out upgrading my phone and waiting for Android 3.0 but the most compelling option out at the moment is the Samsung Galaxy S. Anyone think Android 3.0 will be available on the Galaxy S or is it worth waiting until later this year to see what new hotness gets released?
I know there's not much info out there about Android 3.0 but I'm essentially asking if it's worth waiting or not?
Could be waiting for 4 months or more, can you handle that? Having said that Google are well known for just up and releasing stuff without much build up so it could be sooner than expected... personally I don't think it will be til early 2011 for 3.0 phones to be released.
btdag said:
Could be waiting for 4 months or more, can you handle that? Having said that Google are well known for just up and releasing stuff without much build up so it could be sooner than expected... personally I don't think it will be til early 2011 for 3.0 phones to be released.
Click to expand...
Click to collapse
Really? Early 2011? Damn.... I was convinced that 3.0 would be out *with* phones by the end of this year?! I can't really handle 4 months or more because my Hero is so damn slow and unstable. I love and appreciate the custom ROMs for it from the good folks at XDA but I need mo speed!
Thanks for the reply.... Only question now is finding out if the Galaxy S will get the custom ROM love that my Hero got or if I should wait for a HTC of similar (or better) spec.... I think I'm going to go for the Galaxy S because I could be waiting forever otherwise and my phone is basically a pain in the ass. I'll have a look at what's going on in the Galaxy S dev forum....
Bear in mind anything on this subject is speculation. I don't have any insider knowledge, its just my guesstimate.
btdag said:
Bear in mind anything on this subject is speculation. I don't have any insider knowledge, its just my guesstimate.
Click to expand...
Click to collapse
I appreciate that. Thing is.... What happens with Android releases usually? What's the pattern? Did 2.0 come out as software after an announcement and then a good while later the phones trickeld out? How long between the announcement and the release of SDK/dev tools etc and the the actual availablitlity of phones? I know very little is know about 3.0 - but does anyone know if it's confirmed that the *software* will be revealed/released by the end of this year or something else?
Is there a better place to ask this?
Cheers
I have heard speculation Android 3 will be for the tablets.
So if you want it, hold off on buying anything. Remember, dont buy because of what they promise. HTC promised 2.0 and 2.1 for AGES before releasing it. Custom ROMs were possible as there were leaks, but without leaks, you're essentially stuffed.
pulser_g2 said:
I have heard speculation Android 3 will be for the tablets.
So if you want it, hold off on buying anything. Remember, dont buy because of what they promise. HTC promised 2.0 and 2.1 for AGES before releasing it. Custom ROMs were possible as there were leaks, but without leaks, you're essentially stuffed.
Click to expand...
Click to collapse
I never knew that leaks make custom Roms possible...There are already custom Roms on XDA for the Galaxy S as far as I can tell. Forgive my ignorance but is it the case that Custom ROMs can only be developed from leaked official ROMs (for drivers etc)? Or can custom ROMs be developed simply from android sources? i.e. Because the Galaxy S is one of only a few android handsets from Samsung am I right in thinking that it's therefore much more difficult to, say, port Froyo to the Samsung Galaxy S unless there is an official version out there somewhere from Samgung themselves?
I LOVED messing about with new ROMs on my Hero and am currently rocking ForydVillain which is great - but the cracks in the Hero are starting to show - it's slow. In terms of ROM development - are HTC devices much more likely to get custom ROMs than Samsung phones? I don't know of any upcoming HTC handsets that rival the Samsung Galaxy S......yet!
It's such a pain because there are so many variables with Android, Handsets etc.... :-s
alsheron said:
I never knew that leaks make custom Roms possible...There are already custom Roms on XDA for the Galaxy S as far as I can tell. Forgive my ignorance but is it the case that Custom ROMs can only be developed from leaked official ROMs (for drivers etc)? Or can custom ROMs be developed simply from android sources? i.e. Because the Galaxy S is one of only a few android handsets from Samsung am I right in thinking that it's therefore much more difficult to, say, port Froyo to the Samsung Galaxy S unless there is an official version out there somewhere from Samgung themselves?
I LOVED messing about with new ROMs on my Hero and am currently rocking ForydVillain which is great - but the cracks in the Hero are starting to show - it's slow. In terms of ROM development - are HTC devices much more likely to get custom ROMs than Samsung phones? I don't know of any upcoming HTC handsets that rival the Samsung Galaxy S......yet!
It's such a pain because there are so many variables with Android, Handsets etc.... :-s
Click to expand...
Click to collapse
Hold on, you've got confused here, as I wasn't pretty clear about what I was saying. You don't need a leak to make a ROM, but a leak lets you do it before official release. What I'm saying is that there's no guarantee that HTC or samsung or motorola or whoever will release Android 3 in any expedient time. HTC took forever to bring us 2.1, and the only way we managed to get it running BEFORE official release (which was June), was to use custom ROMs based on a leak.
Without that leak, we would likely have been much further back in making ROMs, and might not have managed till the release.
You can dev from a final release just fine, but leaks are needed to do so before the ROM release.
As for building from sources, you can do so, if there's a vendor overlay available. This is how FroydVillain is built.
XDA specialised in HTC devices since 2002/2003, but is now introducing stuff like Samsung devices. I don't know how many "real" devs are on the Samsung, but I think you'll have less custom ROMs, at least initially, until a development community builds up.
pulser_g2 said:
Hold on, you've got confused here, as I wasn't pretty clear about what I was saying. You don't need a leak to make a ROM, but a leak lets you do it before official release. What I'm saying is that there's no guarantee that HTC or samsung or motorola or whoever will release Android 3 in any expedient time. HTC took forever to bring us 2.1, and the only way we managed to get it running BEFORE official release (which was June), was to use custom ROMs based on a leak.
Without that leak, we would likely have been much further back in making ROMs, and might not have managed till the release.
You can dev from a final release just fine, but leaks are needed to do so before the ROM release.
As for building from sources, you can do so, if there's a vendor overlay available. This is how FroydVillain is built.
XDA specialised in HTC devices since 2002/2003, but is now introducing stuff like Samsung devices. I don't know how many "real" devs are on the Samsung, but I think you'll have less custom ROMs, at least initially, until a development community builds up.
Click to expand...
Click to collapse
Thanks for all the info - appreciate the detail and effort and maybe I need to get out more but I find it all fascinating
By the way - Somehow I've been thinking all day - utterly convinced - that 2011 is a whole year (12 months) from now instead of just a few months from now. I even called Orange to find out when I could cancel my contract. These years are flying by.... Maybe I'm getting old... Consequently - maybe I'll hold out a few more months for 3.0...
FroydVillain is as good as it gets on the Hero at the mo and it can only get better(!)
http://www.downloadsquad.com/2010/11/05/android-2-3-gingerbread-release-november-11/
I bought the Epic to be ahead of the trend... We dont even have 2.2 yet, but 2.3 is coming out.. Who knows when that will be released for the Epic!
june 18, 2011
I upgrade phones every 6 months... so that doesnt work for me...
Plus, by that time, it will be Android 3.0 Chocolate Chip.
EvanWasHere said:
I upgrade phones every 6 months... so that doesnt work for me...
Plus, by that time, it will be Android 3.0 Chocolate Chip.
Click to expand...
Click to collapse
you mean honeycomb..lol..or icecream
anyways..google said that in the future there will be only 1 major release per year.
EvanWasHere said:
I upgrade phones every 6 months... so that doesnt work for me...
Plus, by that time, it will be Android 3.0 Chocolate Chip.
Click to expand...
Click to collapse
6 month you won't get much major progress...from the rumors all the ual cores will be coming next summer anyways..
Either way chances are you won't see Gignerbread on a phone for at least 3 month or so unless its a development phone.
that's some ****ty ass news...
I'm afraid samsung will drop support on these phones by then.
If the Nexus Two/S becomes available on Sprint (and with 4G), I'll happily dump the Epic to avoid this constant unnecessary hassle. The manufacturers and carriers are wrong, at least when it comes to me - I know what I want on a phone more than they do.
I've dealt with it on HTC and now Samsung, and I won't do it again.
razorseal said:
that's some ****ty ass news...
I'm afraid samsung will drop support on these phones by then.
Click to expand...
Click to collapse
No, that is some awesome inspiring news. The faster Gingerbread is released, the faster the Galaxy Tab gets gingerbread. The faster Galaxy Tab and other phones receive gingerbread, the faster it will be ported to our phone regardless of whether Samsung has official plans to port it or not.
vansmack said:
If the Nexus Two/S becomes available on Sprint (and with 4G), I'll happily dump the Epic to avoid this constant unnecessary hassle. The manufacturers and carriers are wrong, at least when it comes to me - I know what I want on a phone more than they do.
I've dealt with it on HTC and now Samsung, and I won't do it again.
Click to expand...
Click to collapse
You probably wont need to. The drivers for the Nexus S will probably work with our hardware and that should make porting gingerbread to the other galaxy S phones a lot easier. With a little luck we might have a working gingerbread before some of the HTC phones.
People are sooo negative about continued samsung support. If you are really APART of this community you have NOTHING to WORRY about. So unless you plan on staying stock quit complaining about froyo and gingerbread.
jbadboy2007 said:
People are sooo negative about continued samsung support. If you are really APART of this community you have NOTHING to WORRY about. So unless you plan on staying stock quit complaining about froyo and gingerbread.
Click to expand...
Click to collapse
iono if i got your statement right,,, but i'd rather have a stock build of android on my epic than one thats been made over by samsung or any company for that matter. i understand that android is open and therefore if a company wants to skin or whatever with it then that up to them. it would be nice if there was an option to where we could go the a companies site ie. samsung, htc, sony; and have an option to download a vanilla build of the current os that is out. and it dosent even have to be before they release their version of it. for example with froyo 2.2 ,,, once they start to push it out to us in the states, it would be cool if we could go to sammy's site and download an alternative vanilla build. of coarse companies might say that it will take away from the phone as far as features that they built into it or want to implement. but if im paying for a device that is 100% mine, i would atleast like to have some options with it sans root and flash.
my opinion
Its not Gingerbread, more like the source....
Gingerbread being released on the The Nexus S is great news since the Nexus S is basically just another Galaxy S minus TW. Porting Gingerbread to the Galaxy S should be very easy...
LOL
With all these tasty sounding android os names the last os update will be called Fat bastard lol. or weight watchers.
walord said:
Gingerbread being released on the The Nexus S is great news since the Nexus S is basically just another Galaxy S minus TW. Porting Gingerbread to the Galaxy S should be very easy...
Click to expand...
Click to collapse
Wait, so for the 99 percent of us that doesn't even have Froyo yet you are inspired by Gingerbread being released? May I please borrow your rose glasses???
2.3 is coming soon, Nexus 2 will be the first phone to get it and it's not expected to come out for another month. They site says it's 2.3 sdk, and 2.2 sdk came out a month and a half before nexus one got the official update
While the T959 is a well built phone with great specs, I felt like it was incomplete until 2.2 ROMs came out in November. Then, when 2.3 and the Nexus S were announced, that feeling returned.. now with Cyanogenmod7 working so well, I am in love with my Vibrant once again.
Even without any further version updates (2.4, 3.0 if possible) the phone has been improved dramatically by the work of Team Whiskey, Supercurio, Eugene, and the Cyanogenmod Team.
What keeps the Vibrant apart from all the HTC and Motorola phones when it comes to Cyanogenmod - is it a driver issue? Is it because of the Hummingbird processor?
Now that CM7 is finally working well on the Vibrant, does this mean that future Cyanogenmod versions will work on the Vibrant? Have they finally "cracked the shell" so to speak?
I am curious also as to what makes CyanogenMod different to work on for our phones vs the other ones you named.
CM is actually worse for Motorola devices as they have a locked bootloader...
On the other hand, HTC is very good about releasing source for their devices when compared to Samsung, who rarely releases source code if at all (driver source). Plus, CM started on HTCs, and with every device using similar Qualcomm hardware, i can imagine it is easier to port to newer Qualcomm-equipped HTC devices. That said, it appears that HTC is beginning to implement software to prevent rooting on newer phones like the G2, so we may see more people moving towards the more open Samsung devices.
Finally, this is explained to me. Thanks!
Why do drivers need to be recompiled for each version of Android? Do they need to be recompiled for similar releases such as 2.0 and 2.1 or 2.3 and 2.4?
I'm not exactly an expert when it comes to the Linux architecture, so take the following with a grain of salt.
Anyways, I believe it has to do with the kernel, which should contain the device drivers. Now, kernels must indeed be recompiled for every android system update; this is why a 2.1 or 2.2 kernel will not work with the newer 2.3.x roms. The problem for us is that once Samsung stops releasing kernels/roms for the SGS series, devs will no longer have a base to build off of. Hopefully devs can make use of updates/drivers from the Nexus S to keep the SGS series up to date with CM.
qtilt ......... nicely explained
oka1 said:
qtilt ......... nicely explained
Click to expand...
Click to collapse
I agree!
The main difference between CM/MIUI and the rest of the roms you see here on XDA is that CM/MIUI are built directly off of a Vanilla Froyo/Gingerbread. No extra flavorings or seasonings such as TouchWiz, HTC Sense, MotoBlur, Droid UI, etc. The use of, or misuse of, causes phones to run slower and do more work (unnecessarily) while it computes extra calculations of the UI. [EDIT]When developers BASE a rom off of a leak or pre-existing firmware it does not make it Vanilla just by removing TWiz or Sense or the rest of bloatware. Vanilla is generally the most simple a firmware can be, with no added extra-pazzaz[/EDIT]
There hasn't been a solid update to MIUI for our phone in a month, but CM has nightly builds and HOPEFULLY it has "cracked the shell," so to speak. Even if Samsung STOPS upgrading our firmware (which has already happened IMO), CyanogenMod makes their own code and develops independently without the use of previous stockpiles of code...which is why it's difficult at first to come up with their own driver source (because Samsung refuses to release ALL the sources needed). Hopefully our Vibrant is covered for the next 2.4 or 3.0 (3.1) update.
Samsung needs to continue to make money. They wouldn't if they let each phone update to the newest andros os. Not just samsung, any hardware company.
Sent from my vibrant using cyanogenmod7.
boltdidit said:
Samsung needs to continue to make money. They wouldn't if they let each phone update to the newest android os. Not just Samsung, any hardware company.
Click to expand...
Click to collapse
I disagree with this because, If Samsung released the code and people updated their phones as they liked and put different operating systems, roms as they liked. customer satisfaction would skyrocket. People would be more likely to buy new phones only from Samsung because they wanted the newest available hardware, read this as faster more flexible with more options.
but alas Samsung as with most of the manufacturers suffer from penny wise and dollar stupid syndrome and they end up being fairly low on the customer satisfaction scale another words they suck
rbcamping said:
I disagree with this because, If Samsung released the code and people updated their phones as they liked and put different operating systems, roms as they liked. customer satisfaction would skyrocket. People would be more likely to buy new phones only from Samsung because they wanted the newest available hardware, read this as faster more flexible with more options.
but alas Samsung as with most of the manufacturers suffer from penny wise and dollar stupid syndrome and they end up being fairly low on the customer satisfaction scale another words they suck
Click to expand...
Click to collapse
As a hardware company customer satisfaction is one thing and making them buy more of their products is another. If your 4,5-years old phone can still upgrade to the newest OS why would you buy a new one? So there is a balance for them to keep, their want to make their customer happy with their product but not too happy so their stay with old product forever.
That's very much why samsung was hesitated about 2.3 upgrade for the galaxy line.
The future of the device has more to do with whether or not the developers stick with the device. With the SGS being an international phone there is a better chance of this happening, and samsung has started getting better with releasing their source. As mentioned earlier HTC is making devices harder to root, for example the HTC desire CDMA with 2.2 is impossible to root and the G2 was an annoyance.
Also samsung has released multiple phones that are very close to the Vibrant such as the Nexus S and the Vibrant 4g. The Nexus S will be updated for awhile and source will be released for it, so its something though not much. The Vibrant 4g will also hopefully be updated and that will hopefully be an easy port. Also 2.4 is very similar to 2.3 so that will hopefully be an easy update for the developers.
Basically as long as we have the awesome devs that we have and we dont flame everyone that the devs get tired of working with the phone then we will have a device that will be updated and beautiful.
I want a stock style gingerbread, and I hope a touchwiz themed CM7 coming out.
vvsnail said:
I want a stock style gingerbread, and I hope a touchwiz themed CM7 coming out.
Click to expand...
Click to collapse
I believe Krylon is working on Stock, as for a Twiz themed CM7 I ask why?
bearsfan85 said:
I believe Krylon is working on Stock, as for a Twiz themed CM7 I ask why?
Click to expand...
Click to collapse
Ha, this is whats to come. CM7 hasn't arrived yet and now they want it with twiz. The ridding of twiz is part of what makes it great.
Sent from my SGH-T959
joe.kerwin said:
Ha, this is whats to come. CM7 hasn't arrived yet and now they want it with twiz. The ridding of twiz is part of what makes it great.
Sent from my SGH-T959
Click to expand...
Click to collapse
+1 agree 100%
bearsfan85 said:
The future of the device has more to do with whether or not the developers stick with the device. With the SGS being an international phone there is a better chance of this happening, and samsung has started getting better with releasing their source.
...
Basically as long as we have the awesome devs that we have and we dont flame everyone that the devs get tired of working with the phone then we will have a device that will be updated and beautiful.
Click to expand...
Click to collapse
Amen. Well stated.