November 24, 2012 By: Joseph Hindy

As many may have noticed, we here at XDA have spent quite a bit of time over the last couple of weeks talking about Android 4.2. It’s everywhere now, including the SDK and its release to the AOSP. So now comes the time when ROMs should start appearing. For AT&T Galaxy S II Skyrocket users, you could have one sooner than most.
XDA Senior Member sk8erwitskil released a tutorial that helps users compile the newly released revision of Jelly Bean. However, instead of making people start entirely from scratch, this tutorial is more of an add-on from the popular method to compile Android 4.1 for the Skyrocket. As sk8erwitskil explains:
Im in the process of compiling android 4.2 for the skyrocket right now. i wanted to share the changes i needed to make to get it to keep compiling.
With that said, the overall process isn’t complete yet. That means you can’t follow this and have a perfectly running ROM. However, it is fairly close to being completed, and members of the Skyrocket community have been helping figure out the problems and fixes. It shouldn’t be long before fully functional source-built Android 4.2 ROMs start churning out for the Galaxy S II Skyrocket.
For more details, or if you would like to help out, check out the original thread.
September 13, 2012 By: Joseph Hindy

One would think that after so many years, things like wakelock would be done and over with. It isn’t, however, and developers and users alike are still dealing with such problems to this day. However, as new wakelocks continue to appear, now workarounds and methods to fix them continue to are developed. The AT&T Samsung Galaxy S II Skyrocket is no exception, as there is now a way around practically every known wakelock.
The guide was written up by XDA Senior Member Jrockttu, and includes quite a bit of information. It begins by having users check their chargers, as certain charging configurations have been shown to cause wakelocks. It then talks about various software wakelocks that have been found by various XDA community members, and ends with the proclamation that all stock ROMs are lacking—something we don’t necessarily disagree with.
After everything has been identified, Jrockttu then gives users the known workarounds for each issue. In some cases it’s quite easy, such as finding out what chargers are causing the issue so one does not use them anymore. Additionally, debloating has been found to help out as well. Others are more complicated and don’t have a direct fix outside of buying a better battery or switching ROMs and hoping for the best. But hey, knowing is half the battle, right?
For more information, check out the original thread.
July 30, 2012 By: mustangtim49

Among other things, XDA is famous for its ability to help users obtain root with unprecedented efficiency. Usually, when a person makes the decision to root, the forums are both their first and last stop. Now, thanks to XDA Senior Member vincom, obtaining and removing root on the AT&T Samsung Galaxy S II Skyrocket just got a whole lot easier.
The guide is aimed at users with almost no experience with Android modification. The thread is very well laid out, with thorough and clear instructions. It also includes pictures and all necessary links to root your Skyrocket with confidence. With this guide, the steps are explained with detailed descriptions and images. There’s also a glossary section to acclimate even the greenest “noob,” and a separate guide for flashing CWM recovery.
Head over to the tutorial thread for all your Skyrocket rooting needs.
July 29, 2012 By: Joseph Hindy

Not long ago, CyanogenMod 10 was announced. Not too long later, there were preview and unofficial builds released for so many devices that XDA TV’s Jordan has spent the last two weeks talking about it. Well, following in those footsteps, unofficial AOKP Jelly Bean has been announced and released to a few Nexus devices, and has begun expanding into the non-Nexus area. Among the first non-Nexus devices to pick up AOKP Jelly bean are the HTC EVO 4G, AT&T Samsung Galaxy S II Skyrocket, and the AT&T Samsung Galaxy Note.
As should be expected by now, all three ROMs have their issues. Very few Jelly Bean ports are fully functional, but the AOKP builds have about as much working as the CM10 builds at this point. So while they may not be daily driver for most, they are definitely something to try out and have fun with. XDA Recognized Contributor Mazda, along with the rest of Team DIRT, are responsible for bringing the unofficial AOKP to the EVO 4G. They are also the ones who brought unofficial CM10 to the EVO 4G. The AT&T Skyrocket build comes from XDA Senior Member armyveterangunner29 with some help, and the AT&T Galaxy Note build comes from XDA Senior Member JamieD81.
In the list of things not working, all three ROMs cite that they have similar issues to CM10 builds on the same devices. This includes some hiccups in Google Now functionality, camera issues, some video codec issues, and other bugs. These bugs are expected to go away in later releases, so if you’re looking for something more solid, all you need to do is wait.
For additional information, check out the thread links below.
July 10, 2012 By: Joseph Hindy

One of the biggest perks of having an Android phone is the customization. Any given Android user can make any given Android phone look and behave how they want. Even without root, there are replacements for virtually any application that comes on whatever Android device you can think of. With root, the customization gets even more ridiculous. There are custom ROMs, kernels, mods, tweaks, scripts, themes, and even fixes to issues that were on the phone since launch. Where is a user to start? For AT&T Galaxy S II Skyrocket users, you can always start with AromaKoaK.
AromaKoak, or AROMA Kang of all Kangs is a set of modifications that users can choose to install on AOSP ROMs of their choice. Created by XDA Senior Member boobah204, it utilizes the popular AROMA Installer to let users pick and choose from a large number of modifications and customizations to install to their AOSP ROM. The modification pack is currently compatible with CM9, AOKP, and Chimaira flavors of AOSP. It packs a pretty impressive feature list, including:
You can change the system font, the boot animation, the transitions between screens, add sounds (hella sounds…) and a few more features. You can also flash this immediately after a new ROM and conveniently flash gapps, the agps patch by crypted, add root browser, tibu, and rom manager.. or fix permissions right away with a script from realpariah and minotauri. You flash this as many times as you want. Anytime you want to change something, just go to recovery and flash again.
Just flash this mod, pick which ones you want, and they install. To get started, head to the original thread.
April 25, 2012 By: Joseph Hindy

While many members come to XDA to flash the latest and greatest ROMs and kernels, and perhaps find a cool mod or theme, there are some members who enjoy living on the bleeding edge of development who flash just about anything from experimental leaks to radios from other devices. Of course, keeping up with all this development work means dealing with some unscheduled issues and bugs as well. While no one likes bugs, they’re kind of like puberty—eventually, it happens to everyone.
Of course, with every bug comes a fix and for those on the AT&T Samsung Skyrocket who have experimented with the a Samsung Galaxy Note radios, you may have run into a few problems that can now be fixed using not one, but three methods in a thread posted by XDA Senior Member icenight89.
The first method runs the user through manually replacing a file that would normally fix the problems. It isn’t very difficult, and really only requires users to flash back to Android 2.3.5 and a root file explorer to use, and then flashing an ICS ROM to complete. The second method runs users through a computer-connected method where ADB is used to push the proper file—called keystr—back onto the device. The third method is for when 1 and 2 don’t work, and comes in the form of a flashable update.zip file that puts the file back for you. In all instances, however, the first step is removing the Galaxy Note radio, and getting back onto the firmware intended for the Skyrocket. Apparently, the radio for the Galaxy Note has a tendency to do all sorts of things to the Skyrocket, such bypassing the lock screen and /efs corruption.
For more information on the bugs and how to fix them, visit the original thread.
March 26, 2012 By: egzthunder1

Last week, we found out that Samsung and several carriers around the world are beginning to push out ICS for the Galaxy SII line of the device. Needless to say, the first one to get hit with the update was the original, international version of the SGSII. At the same time, we also know that there have been a few devices with leaked ICS for quite some time (including the Epic 4G Touch, which seems to be getting several doses of leaks in a weekly fashion).
Thanks to XDA member SolsticeZero, we just learned that one of the device’s US variants, the SGS2 Skyrocket, was just blessed with an ICS leak. The leak named IML74K, much like any other “virgin” leak out there seems to need some work in terms of polishing. However, those who flashed this seem to be enjoying it quite a bit.
However, no decent leak is complete without a good ol’ rooting (I apologize if this offends any Australians out there). Having said that, thanks to the quick efforts by XDA Recognized Developer starskyrob, the leak can be successfully rooted. The guide seems to be extremely straight forward as there is simply a zip to be flashed via recovery and boom! Congratulations, you are rooted.
Please take it for a spin and try and report any and all bugs on this leak. Having an official build (even though it is a leak) is by far one of the best things that could have happened to the Skyrocket community, so congrats guy!
Step 1: ODIN CWM
Step 2: Flash Attached zip from recovery.
Step 3: Reboot.
You can find more information in the original thread and the rooting instructions here.
Want something published in the Portal? Contact any News Writer.