If you are interested in getting a Galaxy S from Bell, DO NOT buy it. That device has a known issue with corrupted internal memory and ended up into a brick.
I own a Samsung Captivate and it has been great. My gf's Bell i9000m, is a total disaster. The internal memory got corrupted a night and Bell replaced it with a new one. A few weeks after, the screen was dead as one color no longer show up. Bell sent it out on repair.
Bell/Samsung released an update to 2.2 a few days ago, and 3 days after, they pulled it back due to the same internal memory corruption issues. Since then, Bell and Samsung wasn't saying anything about that. http://www.examiner.com/technolo ... ernal-storage-fried
The question everyone has now is that why is this internal memory issue only happen on the i9000m and not the other Galaxy S devices??? This problem is a wide spread issues, and so far there are a lot of people (200 or so reported) with dead phones. http://forum.xda-developers.com/showthread.php?t=868569
Until Samsung get their stuff straighten out, I don't suggest buying the Bell's Galaxy S. Go get the Rogers Captivate or pick one up from the US.
You have to give Samsung credit for selling over 9.3M of Galaxy S globally, in S Korea... Samsung's sales is ahead of Apple. They are aiming 10M by the end of the year.
i own a captivate.. really great. i upgraded to android 2.2 ... installed voodoo lag fix and overclocked to 1.2Ghz.. it is fast as hell! iphone can't compare
Lagfix is a way of using ext4 as the file system to speed up read/write process. Overclock is the ability to run the CPU at 1.2Ghz in exchange of shorter battery life.
I have not seen a need to overclock as the unit is already very fast after the lagfix and the battery will not last even 24 hours.
You should be looking at custom ROM, that will get rid of all the Samsung and Rogers bloat.
You can check the label under the battery, it will have 4 digits on the label like 0710, 0810, 0910, 1010 or somthing along that line, if your model is 1010 (Oct 2010) built, the SD card issue is fixed.
發表於 2010-12-22 01:53
| 
