- 5,044,559
REGISTERED - 55,548
ONLINE NOW
December 19, 2012 By: Joseph Hindy
Android 4.2 AOSP ROM development is in full swing here at XDA with a plethora of devices receiving the 4.2 goods. Thankfully, there are no signs of it slowing down, as 4.2 AOSP ROMs are popping up everywhere. The latest devices to get CM10.1 are the Samsung Galaxy Note GT-N7000 and the much older original Samsung Galaxy S I9000.
XDA Recognized Contributor chasmodo released an unofficial port of CM10.1 for the Galaxy Note. This isn’t the first CM10.1 to be released, but XDA Elite Recognized Developer Entropy512 will be away for awhile and has passed the nightlies builds on to chasmodo. The ROM is in development, meaning there are things wrong with it. The list includes:
- UI: Apps like NHK are broken
- Audio: bugs, missing features
- Camera: Recording partially broken
- FM Radio: unsupported
- TV Out: unsupported, not likely to ever work (there is small hope now but not much)
- Lots of missing and yet unimplemented features
- and a lot more
It’ll likely be some time before this is fully stable. However, development is in progress and multiple devs are working on it.
XDA Recognized Developer pawitp released what is actually an official CM10.1 build for the Galaxy S. In terms of stability, the list of known issues says there are no outstanding bugs, so this actually could be a daily driver. Granted, there may be smaller issues, but the big stuff should be all taken care of. Not bad for a device that is pretty old by Android’s standards.
For additional details, check out either the Galaxy Note II thread or the Galaxy S thread.
Update: As Elite Recognized Developer Entropy512 points out, there have actually been official nightlies for the N7000 for the past few days, with the thread update coming soon! You can find the nightlies in the usual place!
August 18, 2012 By: jerdog
We recently told you about the CyanogenMod team beginning work on CM10. Now, a significant milestone has been reached: CM10 Nightlies have appeared for select devices. For those who aren’t familiar, a nightly build is an automatic build incorporating the latest changes in CM source for a device. Yesterday, CyanogenMod released the list of those devices that would be getting the first round of nightlies:
# The US SGS3 variants (AT&T, T-Mobile, Sprint)
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (Vibrant, Captivate, International, and i9000b)
# The SGS2 i9100g
# P3 and P5 tablets
That list will grow as other devices become ready and receive the blessing from their maintainers to begin nightlies. Be sure to keep your eyes open for when your device joins the list.
Update: We’ve received various reports from XDA Forum Member Scotto70 and others that the Nexus 7 build is currently nonfunctional. So if you’ve got a N7, we recommend that you hold off for the time being!
August 11, 2012 By: Haroon Q. Raja
With the release of the Jelly Bean source code to AOSP last month, we are seeing more and more of Jelly Bean ROMs ported to various Android devices. Slim Bean is the Jelly Bean variant of the popular Slim ICS ROM, and it is now available for several devices including the Samsung Vibrant, Nexus S, Galaxy Nexus (Verizon, sprint, and GSM variants), Samsung Captivate, and Samsung Galaxy S I9000.
Slim Bean’s predecessor Slim ICS has been quite popular as a very lightweight and fast AOSP-based ICS ROM, with just the right amount of tweaks and mods added to it, including some by the ROM developer and others from AOKP and CyanogenMod. With Slim Bean, XDA Recognized Contributor krarvind aims to bring the same features to Jelly Bean, while still keeping it fast and lean in the tradition of his previous work.
You can download all variants of Slim Bean ROMs from the Slim ROMs website. Below are the links to the device-specific threads for Slim Bean where you can find more details and join the discussion:
August 8, 2012 By: Joseph Hindy
Since the Jelly Bean source was released, we’ve brought you news of a very large number of official and unofficial CyanogenMod 10 ports. Now, as new releases are beginning to wind down, various developers are writing up guides to show others how to do it. One early guide on compiling Jelly Bean from source was already covered on our Portal not too long ago. Now, more device specific guides are beginning to slip through the cracks, including for the Samsung Galaxy S I9000.
Posted here by XDA Senior Member pmos69, the guide builds on existing guides that teach how to compile CM9 from source—all fully credited, of course. It starts with the very basics, including installing Ubuntu packages, Android SDK, and Java. Then, it goes through that now familiar task of installing the repository.
After the set up, pmos69 walks users through how to compile the ROM and flash it to their devices. It is a very elementary guide, but perfect for those looking to start out and want to do so on the latest version of CyanogenMod 10. Additionally, there are tips on how to update the repository. While some may want more topics explained, it is quite easy to follow for even the most novice of users.
For more information, check out the original thread.
June 19, 2012 By: Joseph Hindy
There are a lot of tool kits out there that help users modify their ROM and how it works. They can add scripts, mods and tweaks to boost anything from performance to battery life. One portion that doesn’t get as much attention is the kernel. There are a few kernel tool kits out there, although they tend to be a little more complicated than ROM based ones. Users of kernel tool kits get access to all kinds of system tweaks that you can only get with a kernel. For the Samsung Galaxy S and all of its variants, there’s a kernel tool kit that’ll help users tweak all kinds of settings.
The application is called Devil Kernel Config, and was developed by XDA Forum Member philbring. It does have a few limitations. Users must be rooted, be running ICS, and be running Devil kernel in order to get everything to work correctly. There are also a few settings that do not stay past a reboot. This is a problem that is promised to be fixed before the next release.
A few features of the application include:
RAM Settings
Toggle ZRAM/Swap
Devil Idle
Toggle Screen Off – Min/Max Frequency
While some of the features can be found in CPU control applications, a few of the settings are unique. Users of the application have also been requesting features, so there may be more to come.
For screen shots, download links, and more, visit out the application thread.
March 31, 2012 By: Conan Troutman
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: Joseph Hindy
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: Joseph Hindy
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: Joseph Hindy
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!
YouTube
Follow
Like
Google+
