- 5,048,494
REGISTERED - 43,762
ONLINE NOW
August 29, 2012 By: Joseph Hindy
We recently brought you news of how to minimize visible home screen redraw on the Galaxy S III. For those who haven’t noticed this, the issue occurs when you return to the home screen and there’s a slight lag before your widgets reappear on screen. Most Android devices suffer from noticeable redraw, and now, Samsung Galaxy S I9000 have a modification aimed at reducing its occurrence.
Called SuperLauncher+, the mod forces the launcher to remain in memory, which in turns lessens the chance of visible redraw. As XDA Senior Member mnazim explains:
I was searching for ways to keep the android home launcher in memory like many applications have options when I stumbled over this MOD. This thread is to provide Super Strength Launcher+ other MODs for multiple Jelly Bean ROMs out there that suffer from Launcher redraws, Micro lags in the UI etc. due to the low RAM constraints on the GT-i9000.
Basically it is the Launcher that makes a big difference in the overall smoothness of the ROM. There was a build.prop tweak in ROMs up till GB that helped make the HOME launcher stay in memory no matter how much free RAM was available as below
The explanation continues to show that these mods were easily made on Gingerbread and prior, as forcing the launcher to remain in memory was a simple build.prop edit. After Gingerbread though, these settings were hard coded into the services.jar, which makes the mod a little more difficult to apply. Applying the mod is as easy as simply flashing a zip in recovery. Currently, the mod is only compatible with CyanogenMod 10.
For additional info, head over to the original thread.
July 25, 2012 By: Joseph Hindy
Over the last few months, we brought you news of the ASUS Transformer Prime tear down that brought a GPS fix and HTC One X hardware issue that weakens WiFi signal. Both of these hardware problems have hardware fixes, albeit at the risk of seriously damaging a device. No pain, no gain right?
Another device that’s had GPS issues is the Samsung Galaxy S I9000/9001. As it turns out, the fix for that may be hardware related as well. XDA Forum Member LEENO recently tore down the Galaxy S and postulated that the GPS disturbances had something to do with faulty hardware. LEENO explains:
Problem is caused by bad gnd conductivity between mainboard and antenna. It is conduced by conductivity rubber. This kind of rubber was used for old nokia 8210 for connect display to mainboard. It was the mayor fault for nokia 8210.
There are not one, but two ways to fix the problem. Both require some soldering skills, and both will instantly void your warranty. In other words, those giving this a try are doing so at their own risk. LEENO has provided pictures to help walk users bold enough to try this through both methods, and has reported that GPS signal has improved significantly since the mod.
To learn more, head over to the original thread.
June 14, 2012 By: Joseph Hindy
Development on the Samsung Galaxy S III has been on fire recently. That being said, development on other devices to include Galaxy S III goodies such as the new launcher, new widgets, and a certain voice assistant have been steadily making their way across XDA in the form of single mods and, in some cases, mod packs that include all of them. We brought you news of a Galaxy Nexus mod pack that brought several Galaxy S III goodness at once, and now the Samsung Galaxy S I9000 has one as well.
The mod pack for the Galaxy S is much like the one for the Galaxy Nexus and even appears to have been created by the same team of developers. Users can install this mod over top of pretty much any ICS AOSP offering, including CM9, AOKP, and SlimICS. The sole purpose is to bring the Galaxy S III-exclusive applications to the device. The pack includes many SGS III widgets and applications, as well as much of the small stuff such as sounds, icons, and wallpapers. As XDA Senior Member smalldookie states:
Bored with Stock-CM9, SlimIcs or AOKP? But you go crazy when you don’t get your nightlies day by day? You like the SGS3 style and miss some features of the stock ROMs?
The TWICS-Addon-Pack adds a bunch of stock-apps that where ported by xda-members, some SGS3 feeling with (system)-sounds and icons directly ripped from leaked frameworkres.apk/systemui.apk/systemapps of the SGS3 ROM and many more features to your phone.
The mod pack even plays nicely with the CM9 Nightlies, so if you’re a compulsive flasher, the mod pack can be re-installed every day right along with the ROM so you don’t lose any of the functionality.
Hit up the original thread for more details, full feature list, and download links.
May 27, 2012 By: Joseph Hindy
Many Android phones have random and silly bugs—nothing serious, mind you, but things that can often be annoying. One such bug is the receiving a low storage warning when you have plenty of storage space left. While it may seem like a minor inconvenience, your Android device believing it has no space left can prevent you from doing a lot of things such as downloading new apps from the Google Play Store. This is a problem that has apparently plagued Samsung Galaxy S I9000 users for awhile. Now, there’s a fix.
While the issue has been resolved in the past, this particular mod is aimed at devices running CyanogenMod. This is because CM utilizes a small, but fast flash chip to store data in /datadata. However, this partition is just 170MB in size. For many users, this is no big thing, but for those who use a lot of apps, the dreaded low notification is quite the unwelcome guest.
This is where XDA Senior Member Wendigogo comes in, bringing a fix that alleviates the problems associated with the low storage notification. The fix gives users control over where applications store their cache. For larger applications that use a lot of space, you can move it to the standard /data partition and leave the other apps where they were. This eases the burden of the tiny partition somewhat, and should stave off the low storage issue for awhile.
For additional information, visit the original thread.
May 12, 2012 By: Joseph Hindy
Getting CyanogenMod or AOKP working is a rite of passage for many Android devices, and creating a bug-free port can often be a challenge. We recently covered the updated CyanogenMod Compiler that already helps users on a variety of devices get some CM-flavored AOSP goodness. However, while the app helps users get a build to boot, debugging the new build is a whole different story.
Samsung Galaxy S I9000 developers now have a more in depth tutorial that’ll help you get everything working even more quickly thanks to XDA Senior Member Perka. The tutorial was written with the I9000 in mind, and helps new developers get past the booting stage and into the bug-squashing phase.
The tutorial starts off with the basics, and then runs users through obtaining and compiling the code for CM9. This includes downloading all the code from the various sources, getting it all put together, and of course building. What makes this tutorial unique, however, is that Perka is kind enough to add in a tutorial for cherry picking specific fixes and features for their device that have not yet been merged into the official source tree.
If you have the Samsung Galaxy S I9000 and are looking to compile and cherry pick commits on CM9, continue on to the original thread to get started.
April 22, 2012 By: Joseph Hindy
There are many facets to theming and development. Whether it’s changing out the dreaded NinePatch files to make a theme complete, adding init.d scripts to make things work better, or compiling and decompiling .apk files to make modifications, the end product is a big thing made up of little processes. The last example, compiling and decompiling .apk files is definitely among the top skills needed for good ROM development, and any aspiring developer should know how to do so. Aspiring Samsung Galaxy S I9000 developers now have a tutorial that walks readers through editing odexed framework files in a simple and unintimidating manner.
XDA Recognized Developer M_J_Nazari, with the help of a few others, has written up the tutorial for users who need to edit the odex files on a ROM on the fly, as the whole process takes place on an SD card. The process, which includes a .bat script and some ADB commands, walks the user through manually editing an odex file. The examples mainly consist of framework files and the tutorial is intended for such, so users looking to edit some framework files on the fly, including the services.jar, need only to follow the instructions. While the guide was originally intended for Samsung Galaxy S I9000 users, a few edits to the .bat file along with the universal ABD commands can help anyone on any device as well.
For more info, the full method, the download link for the script and more, check out the original thread! As usual, don’t forget to make a backup if you make edits to any framework file on a ROM you’re running, in case you mess up and need to restore.
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.
Head on over to the original thread , get the source code , and check out the official product page.
March 29, 2012 By: egzthunder1
It seems that Samsung has made quite a stir recently thanks to several recently released updates and firmware leaks (albeit they are mostly coming from carriers) to most of their lineup, going back all the way to the original Galaxy S. Thanks to the efforts of XDA Forum Member Przekret and Recognized Developer Faryaab, we now have access to the very latest firmware that was released by Samsung for the original Samsung Galaxy S. The new firmware comes loaded with a ton of updates, bug fixes, a new kernel, a new radio, and most importantly, it will update your device to 2.3.6 (officially anyways).
To make this even more juicy, Faryaab has provided, in his own thread, a method to root this firmware before you even load it up by means of the legendary CF-Root Kernel, developed by XDA Recognized Developer Chainfire. This process requires you to place your device in download mode and by means of Odin to flash the root kernel .tar to the device. It is a quick, simple process that will yield you lots of happiness.
While writing this article in order to provide you with this interesting update from Samsung, I started thinking a little bit about how you will find projects like this or like this on XDA. Now, it is not something new that developers here can and normally will be able to release an update faster than most manufacturers. After all, xda-developers has been doing this for quite some time, keeping your devices alive and up to date, regardless of what your carrier or manufacturer tells you regarding the ability to upgrade. The way I see this release by Samsung is that they are simply trying to release something new to keep the owners of this device mildly happy and content, keeping the complaints at bay. However, I just think that the technique that they are using to do this is not only wrong (both conceptually and the implementation), it is a waste of everyone’s time (including their own developers and engineers).
If you were to examine this new firmware, as stated earlier, it is a Gingerbread ROM on 2.3.6 and it is loaded with the following goodies:
Essentially, in case you have not noticed by now, they are releasing an ICS sprinkled GB ROM to try and keep the people from complaining about the lack of ICS on the device. I mean, after all, most of the eye candy, appealing features of the newer OS are there right? Unlocking your device by just looking at it, a cooler lockscreen than TouchWiz’s stock, smoother and faster transitions, and more. Your average Joe will likely be content with such an “upgrade” because they now have all that they need for their device to look “kewl;” but in terms of functionality, it is the exact same as before–=minus bug fixes and a few tweaks and improvements, of course.
Do you not think that it would have taken the same amount of time (maybe even less considering Samsung’s vast resources in terms of workforce as well as source code, drivers, etc) to make an ICS build for this as opposed to porting applications to an older OS? Hey, I have an idea! Android is Open Source, right? What if they simply used preexisting firmware such as the two ROMs referenced above, fixed the missing pieces in the kernels and libraries, and released a full ICS update? As long as proper credits are provided, they could easily use the existing ports as a base, and go from there (assuming that they don’t feel like starting the ports from scratch).
If Samsung (and other OEMs) would get out of the corporate mentality for a second, they would understood that one of the main reasons people are flocking to Android devices and Open Source software is because collaborative efforts tend to yield MUCH better results in shorter periods of time. Unlike what they would probably do to developers, we are unlikely to send you C&D letters from using and modifying code generated by our developers. Why? Because we believe in the spirit of Open Source and sharing. We are all working towards a common goal, which is to improve the technology that we normally use.
I know that they will likely say that it is the carriers who prevent them from releasing updates, as it hurts sales to update an older device to the latest OS—something that becomes a major selling point for any electronic device. But if you just wrapped up all the goodies from the next OS into an approved update, do you honestly believe that the customer will even bother into looking for a replacement device with an OS that offers, in his or her eyes anyways, the same “kewl” stuff that is present in the newer ones? If you do, then congratulations as you are successfully shooting yourself in the foot twice with the same gun because: A) You will likely piss off tech savvy people who will see through this lame attempt at preventing complaints (and hence, losing part of your customer base); and B) because you will likely ensure that the not-so savvy customer is happy enough with their current device so that they will not buy another one for a while. And in the process of accomplishing the latter, you just spent tons of money on R&D and engineers porting apps from an OS that is Open Source and has already been ported to the target device(s).
To sum things up, Samsung, HTC, et al…. We are here to try and make the best out of these devices. Help us help you. In the name of the spirit of Open Source, lets try and work together so that you make better decisions than trying to calm the public with frankenbuilds like this, which are quite frankly, a waste of everyone’s time.
You can find the original firmware thread here and Faryaab’s thread with the rooting instructions here.
Want something published in the Portal? Contact any News Writer.
[Thanks Faryaab for the tip!]
March 11, 2012 By: Joseph Hindy
Getting new software on older phones is always cause for joy. Usually, the big prize is reserved for getting a whole new version of Android—such as Ice Cream Sandwich. However, sometimes little mods from new software can be fun as well. XDA Forum Member PaWill has successfully ported the TouchWiz 4 launcher for Samsung Galaxy S I9000 users who are running select iterations of Android 4.0 Ice Cream Sandwich.
The mod is installed relatively easily thanks to a recovery-flashable update.zip. There may be bugs, so if you happen to find any, please report them so they fixed. The current change log states:
Repaired scrolling wallpaper.
Works:
SGS CM9 Build 16
SGS Onecosmic 4.2
Nexus S AOKP b27
So if you’re running any of those ICS builds, then the update.zip should work properly for you. However, it could potentially work for almost any ICS ROM. As usual, be sure to make a backup before flashing just in case anything goes wrong.
Visit the original thread for screen shots, download links, and discussion.
February 29, 2012 By: egzthunder1
All good things must come to an end, and that is life. However, we at XDA-Developers do our absolute best that our expensive devices do not fall under this category. We continuously strive to prolong and extend the shelf life of phones by adding features, apps, themes, and most importantly, by reverse engineering the daylights out of them so that they can run newer OSes unsupported by the manufacturers. Having said this, if you have an original Galaxy S (i9000), then today is your lucky day because XDA Forum Member dhiru1602 has successfully ported ICS onto this forgotten beast.
The port itself was taken directly from another port meant for the Nexus S 4G and it is currently in pre-alpha state, which means that you will likely not be rocking most features right off the bat. In fact, it probably means that at this point it is a pretty device to play with but not to use on a daily basis. Essentially, the device has no data capabilities at this point, which is likely the biggest thing, as well as no camera, or video playback. Having said that, for a pre-alpha state, this does have several things working which you would normally not see on similar level releases such as being able to make calls and send SMS, HW acceleration, BT, and a few other pluses.
If you do decide to go with this, please ensure that you understand that this is a work in progress and any and all feedback should be communicated to the dev so as to make this into a more functional port.
This is a full ROM Port based on Official Samsung Galaxy S II ICS ROM – XXLPH. It is based on swamp goblin’s port for Nexus S 4G! Thanks to him!
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer.
[Thanks Faryaab for the tip!]
February 24, 2012 By: Joseph Hindy
Getting SIM unlock can be a pain and usually requires some wacky progress using hex editors, or paying a carrier or third party to give you the code. Since paying money for something you can get free is never preferable, and a lot of people don’t even know how to properly wield a hex editor, there will always be a use for tools that do it for you.
XDA Senior Member Grooby has put together a nifty Windows application that will run the otherwise difficult method originally created by XDA Recognized Developer Odia for people who are having trouble with it. You can find the original method in its development thread. The application works only for older models of the Samsung Galaxy S II I9100, as some users report the method not working with hardware versions 1.4 or beyond. The older version of the tool will work for users carrying a Samsung Galaxy S I9000.
Development for the tool is moving forward as the tool creators are attempting to make it compatible with later hardware versions of the Samsung Galaxy S II, so if it doesn’t work for you, keep an eye out in case a fix is finally found. If you happen to have the supported hardware, you can find the download links for both the old hardware Samsung Galaxy S II and the tool for the Samsung Galaxy S along with instructions in the original thread.
February 20, 2012 By: Joseph Hindy
One of the most fun things about flashing a custom ROM is finding out about all the add ons that developers sometimes leave out of the change log. A new font, a themed keyboard, having the Facebook widget match the theme (for once). However, flashing mods and tweaks can be a pain in the behind.
Enter BroodROM Configurator. XDA Senior Member broodplank1337 has devised this nifty tool to allow users of the Samsung Galaxy S i9000 to choose their features on a ROM and installing them without needing Terminal Emulator or flashing via recovery.
The Configurator has a plethora of features, including:
Choose GPU Driver
Enable/Disable Media scanning
Choose boot animation (RC 1/2) or choose a custom one
Install extended status bar (scrollable, 14 buttons)
Install extra languages (locale app, arabian)
Choose boot sound (standard, feacore, none) or choose a custom one
Choose a GPS Server (14 Servers available)
Choose a DNS Server (5 Servers available)
Choose a APN List (Default, Cyanogenmod APN List)
Enable, Update or Disable AdBlocker (hosts file)
Wipe selected partition
Calibrate battery, Install battery tweak, Battery hints
Recover from bootloop
Turn phone off, reboot phone, reboot in recovery, reboot in download
You can also do things like pick your scheduler or even your kernel and works on XXKPS, XXKPU & XXKQ1 ROMs, even though it’s designed for specifically for BroodROM. After running the Configurator, you’re ready to go with your new set up.
If this is something you could see yourself using, you can check out the original thread for additional details, full features list and even a nifty instructional video. As usual, make a back up first, just in case something doesn’t flash right.
February 1, 2012 By: Joseph Hindy
Typically, going back to a stock ROM after flashing a mod, a theme, a script or a modded ROM can be quite a long process. Sometimes, annoyingly so, especially if you don’t have a copy of the stock ROM laying around on your Android device or your computer. In the end, you end up having to format your system, flash the stock ROM and spend the day setting your phone up again.
For those carrying the Samsung Galaxy S I9000 and running Ice Cream Sandwich, there’s an easier way. XDA Senior Member jenablinsky has released a small mod that will restore the SystemUI.apk and framework-res.apk back to stock ICS which removes all the modifications made to it. Simply flash the small, portable friendly .zip in ClockworkMod recovery and you’re back to square one with a clean slate and, as opposed to carrying around a nearly 100MB ROM in the off chance something goes wrong, you’d instead just need to carry around a measly 14KB .zip. That seems much more reasonable.
For anyone running ICS on their SGS and need it to be less of a mess, then ignore my horribly poetry and head on over to the original thread for all the download links, change logs and instructions.
YouTube
Follow
Like
Google+
