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:
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:
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.
April 3, 2012 By: Adam Outler
Heimdall Suite, an Open-Source Cross-Platform set of tools designed to flash firmware to Samsung devices, has received an incremental update to version 1.3.2. This latest update supports Galaxy S II GT-I9100, Galaxy Player, Captivate, Vibrant, Fascinate, Mesmerize, Epic 4G, Galaxy S 4G, Infuse 4G, GT-I9000T, Galaxy Tab (7 and 10.1 inches) and of course the Galaxy S GT-i9000. If your Samsung device is not listed here, testing is required.
Heimdall has always been a favorite among kernel developers and those who frequently flash the latest kernels because no flashable update.zip or Odin packaging is required. A Heimdall user can simply put their device into Download Mode, and click a button to flash a new zImage directly. XDA Recognized Developer Benjamin Dobell‘s latest release improves compatibility with Loke (the flash receiver on the device) and expands comparability to several new devices.
In the words of the developer:
Version 1.3.2 addresses some compatibility issues with several devices i.e. the Galaxy Player 5.0 and Galaxy S II. In particular the “Failed to confirm end of file transfer sequence!” error should no longer occur under regular use. This was fixed by mapping a previously unknown protocol parameter, which I’ve now called “chip identifier”, to information in a device’s PIT file. A big thanks goes out to XDA developers user ambrice, who helped identify the cause of the issue.
January 22, 2012 By: Joseph Hindy
Ice Cream Sandwich might be taking its time rolling out to phones that don’t have a Nexus branding, but that hasn’t stopped Team ICSSGS from delivering their namesake, ICS for the Samsung Galaxy lineup.
They began their work nearly 2 months ago in November with the release of ICS on the Samsung Captivate and has been a solid run of bug fixing and new releases that brings us up to their Samsung Vibrant release just a few days ago, with a little ICS goodness for the Samsung Galaxy S i9000 folks in-between.
The builds themselves are incredibly stable and have very few, if any, issues with no custom themes or proprietary applications. The team has expressly stated:
We did not add any modifications unless they were absolutely required to make it work correctly.
This makes this the cleanest vanilla experience for the supported phones to date and provides options for those who want to give AOSP Android a shot.
For those who’d like to give their pure, unadulterated ICS AOSP builds a try, they have their work up for the original Samsung Galaxy S line of phones. You can check out their Samsung Captivate build here, their Samsung Galaxy S i9000 build here and, just freshly released, their Samsung Vibrant build here.
Ice Cream Sandwich ports are highly sought after, given the hype and price of the phone that runs it. However, providing there is support behind development, there is every chance you can run it on your device. This article is here to list the current ICS ports on our most popular forums and their individual stages in progress. Should your device not be listed below, you can always visit your device’s development forum on XDA and search for any ROMs listed with “Ice Cream Sandwich”. Check out our list! READ ON »
August 25, 2011 By: Will Verduzco
How would you like to create your own bootloader? Sounds a bit daunting, no? Aside from the inherent “cool factor,” having this ability could get your device out of some tough spots that would otherwise require the use of JTAG.
Thanks to the work of a team lead by XDA Recognized Developer Rebellos, this is now possible for Samsung S5PC110-based (read: Hummingbird) devices. Since there are quite a few Hummingbird-powered devices roaming about XDA, this can prove quite useful for when ODIN is not enough or if your JTAG pins are nonfunctional.
In the words of the developer:
What is it?
Info how to bypass secure booting mechanism built in S5PC110 CPU’s iROM on lowest level and create code loadable even with totally damaged bootloader, without use of JTAG.
Okay, how useful is it?
I’ve got no clue, it all depends on you. Our main target, which is almost done, is ability to revive any hard-bricked hardware built on S5PC110 without use of JTAG (for eg. when JTAG pads had been damaged)
In order to get started, venture forth to the original thread.
[Thanks AdamOutler for the tip!]
For those of you who haven’t made the leap to Gingerbread, for whatever reason but would really like to have WiFi calling on your Android device, check out XDA Senior Member Segnaro‘s latest work.
The XDA member, after spending many hours trying to get WiFi calling working on the Samsung Vibrant running Android 2.2.1 has finally succeeded! You’ll need to flash using CWM, and note that the mod was tested on the BiWinning 3.0 ROM.
The XDA member notes that you should test both WiFi calls and Normal calls are working and that WiFi calling does not force close.
Fore more information and to download the zip, head on over to the forum thread.
Forgetting about setting proper permissions when pushing a custom framework can lead to some nasty problems on your Android phone as discovered by XDA forum member birgertime.
To avoid this in future, the XDA member has written a script to fix this in a flashable zip. Upon every boot, the script will scan /system/app, /system/framework and /data/app and set the proper permissions for all the files in those locations.
Note that after flashing the script, you may still be required to use adb to set the correct permissions in order for the script to work on every boot.
If you are interested in the actual script, the dev has also provided the code. For more information and to download the script, head on over to the forum thread.
If seeing your MMS’s in your Vibrant call log annoys you, XDA forum member Br1cK’d has posted a ‘How To’ on stopping them appearing.
Based upon two other threads on fixing call logs by XDA members eury23 and Mammon88, the XDA dev has written a detailed tutorial on how to take the LogsProvider.apk from you ROM and decompile with apkmanager or a similar program.
You’ll need to navigate and edit the corresponding LogsProvider.smali file and then recompile being sure to delete the classes.dex.
For the detailed steps, head on over to the tutorial thread. Requires knowledge of apkmanager or apktool to decompile apk files.
If you have a Samsung Vibrant device, this may be of your interest. XDA member connexion2005 compiled a great thread containing links to how to´s on video. Topics such as how to flash, backup and restore, how to soft UN-Brick any Galaxy S, how to enter recovery and download Mode, rooting, networking, and reviews.
No doubt a great thread to have in mind if you want to modify your device. Please say thanks or leave your comments.
Originally posted by connexion2005
[VIDEO] Samsung Vibrant Video How-To Thread
This thread will serve as the OFFICIAL thread for all of my How-To tutorials for everything VIBRANT. Keep an eye out as I’m developing new videos on a daily basis. This will just be known as the central repository for all video tutorial links. Please post requests you’d like to see as well and if I’m capable, I’ll create them.
SIDE NOTE: There are many different ways and methods to do a number of the steps in my videos. I know this. I am illustrating what I feel is the easiest and most simplistic way to perform the steps to achieve the goal at hand. Constructive criticism is appreciated but remember, the target audience is a user who has no clue about how to complete the solution. Filler is included along with detailed info about steps to educate the user as well as instruct he or she.
Please consider donating as all of my work is non-profit and I do it for XDA and Android enthusiasts alike. I would have greatly appreciated these videos when I was a newbie and I’m sure you will to. Donation button is in my AVATAR to the left
Continue to the original thread.
XDA member jmerchant informed us earlier today that there is something coming. Something that will hit all Vibrant users in the “happy” spot. Well, that last sentence came out wrong, but basically this will make them really happy. After months of speculations and complaints against Samsung and T-Mobile, it seems that the version of the Galaxy S will finally get a taste of Froyo… not just a port, but rather the full fledged official stock ROM. Vibrant users have been screaming for this pretty much since the release of the device as this OS release is supposed to come loaded with fixes to ensure that these devices perform in the way they were advertised to do so. As a little background, the device has had several issues including major lag, GPS issues, speed problems, and much more. As with any carrier/manufacturer update that we have seen coming out of every single player in the smartphone industry, the new update will likely come with new locks in place, to prevent rooting and such. To that I say, “developers…. start your engines!”
Do you think that this is happening for real? or maybe this is just an unfounded rumor like the many that have surfaced in the past. Leave us your thoughts and more importantly, let us know if you get the update.
You can find more information in the discussion thread.
Want something published in the Portal? Contact any News Writer.
So you’ve got a Vibrant and you’re running FroYo, but you want to add a few more apps, tweak some settings, change launchers and all in one ROM.
Why not try out a new tool by XDA forum member birgertime? It’s a customisation tool for the Vibrant (currently for Windows only) and should work with any FroYo Vibrant ROM.
In order for the app to run, you must have Java installed. It’s a case of clicking through the tabs and selecting the options that you require. The app will generate a zip which you can copy to your SD card and flash with ClockWorkMod.
birgertime states that eventually the tool will work properly on Linux and OS X too. The program currently does have a large file size since it includes every single program – this may be optimised in the future so that the programs can be downloaded from the internet to make the utility much smaller.
The app is in alpha, and for more information including more screenshots and download link, head on over to the application thread.