- 4,431,003
REGISTERED - 31,708
ONLINE NOW
March 31, 2012 By: ConanTroutman
While a pretty sizeable number of devices have already been graced with nightly versions of CM9, that list just keeps on getting bigger. It seems that at some point yesterday the first nightly builds for the original Samsung Galaxy S (i9000 & i9000b) made an appearance on the CM download page.
I suspect that these nightly builds will be much sought after by a great deal of Galaxy S users. Although a semi-functional alpha version for the i9000 has been available for a while, it really was just that. There were a great deal of rather major issues still unresolved and these alpha builds hadn’t seen an update since November last year. This is also the first time that we’ve seen a version of CM9 for the i9000b.
Galaxy S users will surely be hoping that the appearance of these two new builds signals the start of regular nightly builds with much increased functionality. Unfortunately it’s a little difficult to tell which of these outstanding issues has been fixed in the new versions as there are currently no official statements on these two new builds as of yet from either the CM site or their Google+ profile.
If you are the owner of either an i9000 or the regional variant the i9000b and can’t wait to get your hands on these before a changelog appears then you can find these new nightly’s here on the CM download page.
[Thanks to duanh for the tip!]
March 27, 2012 By: PoorCollegeGuy
We’ve said it before and we’ll say it again. Developer collaborations rock. In addition to pooling together resources, collaborative development allows for multiple sets of eyes to look over any given problem. This is especially true when the problem being fixed is one is as annoying as the Low Memory Notifications on the Original Samsung Galaxy S running CyanogenMod. For those who don’t know what it is, XDA Forum Member naTrium explains:
Lot’s of people have encountered the problem where their /datadata partition fills up and then apps begin force closing. This is often confusing since there is usually a lot of space available on the internal 2GB storage partition. But these are two different partitions on cyanogenmod. The created the datadata partition on the fast internal memory so that apps would start up and run faster (i.e. less lag), but it is only about 170MB (which can’t be helped).
So, what is a CyanogenMod-toting Galaxy S to do? XDA Senior Member revthanki began to solve the problem with his script that sent the most commonly used portions of the application to the smaller, faster partition. It would then move the bulky, less used portions to the larger 2GB partition outside.
While it worked, the process revthanki created was difficult to implement. However, naTrium, with some help from CyanogenMod Team member drafnel, cleaned it up a little bit and packaged it in a convenient flashable update.zip. The script works pretty much the same, except it becomes automated on boot and and does a few other nice things such as cleaning up databases left by uninstalled applications.
For additional information on the flashable zip, head on over to the modification thread. There, you can get the basics on everything the script will do to remove those low memory notifications for good.
March 22, 2012 By: jerdog
With the recent news that the Samsung Galaxy Note i717 could be hacked to work on T-Mobile’s HSPA+ network, many inquisitive and adventurous users on XDA began to wonder if other devices could benefit as well. XDA Forum Member pwneman looked into what other Samsung devices had compatible radios and found that the Nexus S i9020a for AT&T uses its radio hardware much the same way as the Samsung Galaxy S i9000, and to a limited extent, the Samsung Captivate. Flashing the devices with the Nexus S radio image not only worked, but seemed to yield noticeable benefits (at least on the i9000).
So I found out that the Nexus S radios are indeed compatible with our device. I downloaded some of the hot radios for the Nexus S (KB3 and KF1) and opened them up and found that the Nexus S uses radios (similar to how the captivate/galaxy s uses modems). So I just renamed the radio.img from the Nexus S radios to modem.bin, placed it in an existing cm7 modem package and flashed it via CWM (ICS).
I reboot and get a constant 5 bars of signal. My signal hasn’t dropped from this 5 bars of signal in the last 10 hours (usually it fluctuates from 5 to 3 bars). HSDPA speeds are pretty fast as well. I got speeds of 560 kb/s DL at 3 bars of signal and 140 kb/s Upload. I’ve never ever gotten that high speeds.
If you fancy giving this a shot, and have taken all the necessary precautions like donning your own designer tin-foil hat, proceed to the Galaxy S thread to get started. You can also give it a try on the Captivate, however there have been reports that the 850 MHz band may not work after flashing and that connectivity may be a bit sporadic.
January 11, 2012 By: PoorCollegeGuy
There is a new ROM that’s looking to make that very exclusive “all phones must have it” list. Say hello to DianXin OS, or DX OS as it’s being referred to. As XDA Senior Member qtwrk will tell you:
i know you guys may think it looks like MIUI , but i asure you it’s totally different ROM nor MIUI-based modification.
As with MIUI, it’s based in Asia, so the ROMs available to try currently still have some translation to go through and are only available on a couple of devices. Namely, the GSM and CDMA versions of the Samsung Galaxy S.
The people who are working on it currently are the aforementioned qtwrk on the GSM model and XDA Senior Member swamp goblin, who ported it to the CDMA version from qtwrk.
So far, these are the only two phones that we could find running the OS, which is reportedly only 3 weeks old. It can be expected to start making its way around the forums as people start warming up to the idea. In 6 months we could all be saying that development is not truly active until there’s CM, MIUI and DXOS are present.
If you have a Samsung Nexus S and want to check it out, or if you just wanna see what all the fuss is about, then you can head on over to the GSM Samsung Nexus S thread found here and the CDMA Samsung Nexus S thread found here. Inside these threads you’ll find download links, discussions, installation instructions, the all-important screen shots and additional information about this potentially awesome new Android-based OS. As per the norm, these ROMs are still in beta so exercise the usual caution when flashing (making a nandroid backup, etc).
January 4, 2012 By: liwen
A Samsung spokesperson has told The Next Web that it will not bring any major updates to last year’s best-selling Galaxy S smartphone and the original Galaxy Tab, finally putting rumors of a ‘Value Pack’ update to an end.
After leaving out the Galaxy S and Tab when initially revealing its plans for ICS-updates three weeks ago, Samsung took to its Korean blog to explain that TouchWiz and other customizations would not run smoothly on the limited amount of memory available on the two older devices. Following a huge backlash, a report on a Korean website revealed that Samsung was reconsidering the move. Only a day later, another Korean website claimed that Samsung was preparing a Value Pack update, originally misunderstood to be adding ICS-specific features on top of Android 2.3 Gingerbread, but later corrected by one of our readers to be an actual Android 4.0 Ice Cream Sandwich version with some TouchWiz-specific features removed. Well, no more.
What makes this especially disappointing is that both Galaxy S and Galaxy Tab are perfectly capable of running stock, AOSP Android 4.0, as evidenced by various ports in our forums and the similarly-specced Nexus S already getting its update, thus unnecessarily obsoleting a device that isn’t even two years old. At the very least, to preserve its software differentiations, Samsung could’ve opted to go ahead with the planned TouchWiz ‘Lite’ version, similar to what HTC has done with its Gingerbread update for the HTC Desire.
But then, for a handset maker that gains absolutely nothing by providing software updates, there’s arguably little economic incentive to do so.
December 28, 2011 By: mic_888
If you own a Samsung Galaxy S and are fed up of having to check for firmware updates on Kies, XDA Senior member LuffarJoh has made a little tool to do this for you. Check FUS 2.0 checks if there is any new firmware on the FUS servers, so you don’t have to start Kies in order to find out.
The app finds your ‘Product Code’ and ‘HIDSWVER’ plus many other features and should work on any Samsung Device running Android.
For full instructions including links to the Market, head on over to the application thread.
If you have any suggestions please post in the forum thread or PM the developer.
December 28, 2011 By: liwen
Update: reader msgfromside3, who speaks Korean, pointed out that the “Value Pack” is supposed to be ICS-based, but with some features removed. So both Galaxy S and Tab will almost definitely get Android 4.0 Ice Cream Sandwich, possibly with a “lite”-version of TouchWiz.
The article also mentions that Samsung considered porting ICS plus full TouchWiz, without providing end-user support, but decided against it for fear of customer complaints.
Big thanks to msgfromside3 for the clarification!
Original article below:
After first denying, then reviewing an Ice Cream Sandwich update for the Galaxy S and Galaxy Tab, Samsung is now said to be providing a “Value Pack”, according to Korean website Daum (via Unwired View).
The value pack would presumably include some Android 4.0-like features, such as enhanced multitasking, faster web browsing, new widgets, and improved camera, but on top of Android 2.3 Gingerbread.
In the report, Samsung said that, due to the limited amount of RAM available, an Android 4.0 version wouldn’t be able to include all TouchWiz features. With previously available features removed, customers would be dissatisfied, which is why it has now instead opted for another Gingerbread update.
Of course, without being officially confirmed, take all of this with a grain of salt. However, considering Samsung’s track record with their Bada devices, this solution doesn’t seem too unlikely.
But there’s still hope, right?
December 27, 2011 By: PoorCollegeGuy
In the spirit of the now passed holiday, XDA Senior Member fuss132 has brought the Samsung Galaxy SL i9003 a little post-Christmas magic in the form of a MIUI port.
The port is working pretty well, with a very short list of things not working so far and it’s still, as fuss132 puts it,
like 70% CM7 and 30% MIUI.
So it’s not a pure MIUI release just yet and it is still in the testing stage. If you happen to check it out, the known issues are:
GPS not working
Sometimes Kernel anic (Just remove Battery and reboot)
Tethering
Hot Spots
Some Miui Apps not working: Miui Stats, Miui Settings (so CM7 Settings included)
Video recording with Camera in very bad quality
And, of course, here’s your list of things that does currently work:
Calls
SMS
HW Acc + GPU Support
Audio
Wifi
Sd Card
Of course Touchscreen
Bluetooth
Camera
Vibration
MIUI Apps: Miui Notes, Miui Music, Miui Contacts, Miui Phone, Miui Talk, Miui Browser, Miui Camera
Miui Lockscreen (Please activate it in your Device´s Settings)
So if you’re up for a little MIUI fun and you happen to own Samsung Galaxy SL i9003, then you can check out the original thread for additional information and installation instructions. If you’ve tried it and want to chime in to let us know how it’s working, feel free to do so!
December 27, 2011 By: liwen
After announcing last week that two of its most popular devices of 2010, the Galaxy S and Galaxy Tab, wouldn’t get official updates to Android 4.0, Samsung seems to be backtracking and reviewing the viability of these updates, according to MSN Korea (via The Verge).
Despite continuing to emphasize the limitations of only 512 MB RAM, Samsung is said to be working on ways to get the Ice Cream Sandwich update out to users, presumably due to negative reactions and widespread criticism.
We can only hope this turns out to be true, and will keep you updated.
December 24, 2011 By: liwen
So, you’ve been wondering why the original Galaxy S and Galaxy Tab aren’t getting Ice Cream Sandwich, like Samsung’s newer models? Why, of course: because they’re too slow. No, not for Android 4.0; the almost identically-specced Nexus S is getting its OTA as we speak.
Of course: for TouchWiz, carrier services, video calling, and, in some countries, mobile TV. Not that anyone actually cares for TouchWiz or carrier services. And, we’re not sure how an OS update is going to slow down video calling or mobile TV. I mean, either you have a front-facing camera, or you don’t. Same with TV antennas.
Anyway, hit up Samsung Tomorrow (uh, that must be Yesterday!) for the original statement in Korean, then check out one Verge user’s excellent translation. Finally, show your outrage for this decision by posting in our forum thread.
All hope is not lost: as many of you may remember, HTC also originally said they wouldn’t bring Gingerbread to the Desire, but later backtracked. Let’s hope Samsung does the same.
November 18, 2011 By: Will Verduzco
Google’s Mobile Product Manager Hugo Barra recently stated that the company had no plans to update the Nexus One to Ice Cream Sandwich, citing that the handset was simply too old to run the newer operating system. Many users felt unnecessarily abandoned, believing that a former flagship device under 2 years old could hardly be considered “too old” for updates. Having used a Nexus One as my primary device for eight months, the news made my heart sink ever so slightly.
Ironically enough, the first ICS SDK-port for the Nexus One actually had already appeared four days earlier. However, as is the case with the majority of SDK-ports, the lack of hardware acceleration made things dreadfully sluggish. Instead, AOSP builds are indeed the Droids you’re looking for.
Four days ago, we broke news of the ICS Source Code release and predicted an imminent rush of AOSP builds. We are happy to announce that not only has XDA forum member dr1337 begun the Nexus One AOSP porting effort, but several other devices have joined the tide. Thanks to the hard work by XDA forum members dizgustipated, MongooseHelix, stritfajt, jaybob413, onecosmic, Chaosz-X, and zFr3eak; the Nexus S, Droid Eris, Hero, Hero CDMA, Galaxy S I9000, Desire, and Desire HD now have their first tastes of Google’s latest treat.
Without further ado, here are the links to get started on your own device:
While none of the releases have quite the level of polish required to be made daily drivers, their mere presence just days after the source code release speaks wonders of the amazing talent housed within our development community.
If there are any other AOSP builds that I have left out, please send me a PM through the forums, and I will promptly add them to the list!
October 29, 2011 By: Sam Caplat
Ice Cream Sandwich is taking the limelight in development. Recently ported to the Nexus S, many are curious and excited to know which device is next. ASUS said their “aim is to bring the latest Android update to the Eee Pad Series.” Motorola’s Droid RAZR, Droid Bionic, and XOOM are definitely getting the update, and they will announce more “devices for ICS 6 weeks after Google releases the final version of it.” If you’re looking to get a new device soon, it’ll likely come stocked with Ice Cream Sandwich.
For those who haven’t upgraded in a while, the Samsung Galaxy S is now on the list of devices with successful Ice Cream Sandwich ports. When I say it’s successful, I mean it’s not released, in alpha, and facing a lot of work before decently working. But it’s there and still worth mentioning.
Operating system ports keep us sane, as far as I’m concerned. Google hasn’t released the retail version, and won’t until the release of their flagship device, the Galaxy Nexus, on November 17th. I know I wouldn’t be able to wait until then to try out the operating system I and millions of others waited for since Google I/O in May this year. I was so desperate to try the new iteration, I’m using the mildly buggy port for the Nexus S as my personal platform.
XDA members galnet and lttldvl, well-known MIUI developers, are heading the port to the Samsung Galaxy S, stating that they’re “taking a break from MIUI over the weekend” and “thought they’d work on trying to port ICS over to the SGS.” Work never ends for the geniuses we are lucky to have on our forums, and we thank you for taking the time to push this out. We’re all looking forward to more developments.
Sources:
KnowYourMobile
Pocket-Lint
InToMobile
August 28, 2011 By: azrienoch
A bricked phone. No JTAG. Modify hardware, upload a bootloader, and the phone lives. Pure development.
That’s what I think of the work of AdamOutler and Rebellos to breathe life into dead devices. A couple days ago, WillVerduzco wrote an article on Rebellos’ method of unbricking Hummingbird devices by uploading your very own custom bootloader to your device. A couple weeks ago, AdamOutler asked for help getting the official Samsung bootloader for Galaxy devices. Since then, the two teamed up to put Rebellos’ Resurrection Bootloader on devices modified according to AdamOutler’s UnBrickable Mod.
Now they’re finding the fun doesn’t stop at unbricking phones. They’re flashing bootloaders built for other operating systems. ”I used UnBrickable mod to install Bada OS bootloaders on my Captivate,” AdamOutler says. ”Totally bricked it. Messed up partition tables and everything. It assimilated my Captivate. I used UnBrickable mod to load up a secondary bootloader while holding the key combination, then flashed it.” He goes on, “I was worried for a bit because it would not download, but eventually we got it! It works!”
This means the months of hard work put into this project finally paid off. AdamOutler working on hardware, Rebellos working on software. Once the hardware side of development finished, Rebellos stepped in. ”You see,” AdamOutler says, “Rebellos is a developer working on a port of Android for Bada OS. He’s 18 years old, from Poland, just got his driver’s license, and he’s a badass behind the assembly language console.”
Samsung Galaxy devices normally boot using a primary bootloader to load a secondary bootloader that, in turn, loads the Linux kernel. Rebellos replaced the primary bootloader. That means they should be able to load non-Linux systems, like Windows Phone 7 or iOS. Rebellos says that will take, “tons of work in pure assembler, as they aren’t opensource.” He adds, “I’d say for SGS family you can count on Bada and any opensource OS, like Ubuntu.”
To put it clearly, the work these developers put into this project means the beginning of HD2-like development on any device with a CORTEX-A8 processor in it, including the iPhone 4 and Nexus S. And that’s exactly what AdamOutler and Rebellos plan to do. ”We basically created a whole new system for developers to use for developing and noobs to use for unbricking after playing with the big kids.” Pure development.
The developers are currently looking for bricked and broken CORTEX-A8 phone donations, such as these:
Samsung I9000 SGS
Samsung S8500 Wave
Samsung S8530 Wave II
Samsung SGH-i997 Infuse 4G
Samsung T959 Vibrant
Samsung SGH-T849 Galaxy Tab 7.0 inch
Samsung GT-P1000 Galaxy Tab
Samsung GT-i9010 Girogio Armani Galaxy
Samsung GT-i8350 Omnia 7
Google Nexus S
Apple iPhone4
If you would like to help out with this historical work, please see the development thread.
YouTube
Follow
Like
Google+
