If your Android device has an unlocked bootloader, it’s undeniable the usefulness of having a custom kernel on your device. With no release of Linux Kernel version 3.4 from Samsung as of yet, it’s great to see developers on XDA all contributing to make this possible for a mid-range Samsung device, the Galaxy S Plus GT-i9001.
The mastermind behind this creation is XDA Senior Member educk, who rebased support for the i9001 on the 3.4 kernel baseline, ahead of a release from Samsung. The kernel is still in the alpha stage of development with improvements and features such as:
Standard functions of the i9001 such as the camera, Wi-Fi, 3G and calls are reported to still be working with no bugs and faults as of now.
Accepting contributions from the development community, educk has done and is doing a remarkable job with this project for the Android community. Make sure to head over to the original thread for more details and discussions.
December 19, 2012 By: Former Writer
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.
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!
December 5, 2012 By: Former Writer
Over the last couple of weeks, we’ve been bringing you news of mskip’s toolkits making it to the Nexus 4 and the Nexus 10. It’s a popular and well known toolkit with extensive features. There is a second toolkit making its way around to Nexus devices, known as Wug’s Nexus Root Toolkit. We brought you news that it was released for the Nexus 7. Now, it’s available for the Samsung Nexus S and Nexus S 4G, the Nexus 4, and the Nexus 10.
XDA Recognized Developer WugFresh has been busy this month. The toolkit has made to five different Nexus devices in just a few weeks. The core features of the toolkit are the same for all releases, and include:
This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, and quick tools utilities. All the latest Android builds and Nexus devices are now officially supported, including the new Nexus 10, Nexus 4, and 3G Nexus 7 (with full 4.2.0 support).
The premise of this toolkit is to make rooting easy and provide a few extra features like installing applications and pushing files. For those looking for a root-bringing toolkit, you should give them a shot.
November 28, 2012 By: Former Writer
The last time we brought you news about the Samsung Galaxy S I9001, it was to tell you that CyanogenMod 10 had been ported. Since then, the CM10 efforts for the device have been taken over by XDA Senior Member ivendor. Since then, AOSP development for the Galaxy S I9001 has been a veritable frenzy. With AOSP-built ROMs flying all over the place, and even some fun ROM ports.
The release of CM10 for the device in turn made ports like AOKP and PACman possible. The Galaxy S I9001 now has both. XDA Senior Member camcory has released the increasingly popular PACman ROM, and XDA Senior Member crybert took care of AOKP. Both ROMs work pretty well but users are reporting their quirks.
For AOKP, some users are reporting that the GPS isn’t functioning properly, the internal memory isn’t being recognized properly, and some random rebooting problems. For PACman, users are reporting unusually high RAM usage along with some graphical glitches in areas like landscape multitasking. The ROMs do work for the most part, so don’t let a few bugs scare you away.
The big port that is being worked on is the also increasingly popular FlymeOS. This is thanks to XDA Forum Member sc4les. The ROM seems to have many more major issues. The list of things not working includes:
browser (webview error, seems pretty common for custom roms. will be fixed soon. well it starts already)
network settings (3g works fine, so do calling and sms)
there are some graphical glitches, but only in some places
email (cant view emails due to webview error I think)
the resolution for the launcher doesnt work 100%
So that isn’t daily driver material just yet, but progress is being made. This is a shining example of the kinds of fun things developers can do once a solid AOSP-based ROM appears.
October 27, 2012 By: Former Writer
Kernel releases can mean great things. This often comes in the form of new features, such as new schedulers or overclocking. Some help save battery life, others help performance, and some still offer improved stability. Some are just awesome at face value. The Samsung Galaxy S Plus now has a 3.0.x kernel.
XDA Senior Member ivendor, along with support from XDA Recognized Developer arco68, have released the 3.0.x kernel for the Galaxy S Plus. It’s currently for developers only. It was released for the purpose of working out the kinks and making it perfect. The current list of what’s working and what isn’t includes:
-3G & Calls
And not working:
Not working list:
– Both Cameras
– Digital Compass
That’s not too bad for a build released solely for development at this time. There are also some issues with display and USB, which are listed as partially working. Ivendor opened up the repository for this kernel, so anyone can submit a patch or fix. While there are test builds, it is recommended that end users wait until a stable release comes out to run it on a permanent basis.
To learn more, check out the original thread.
Floating Touch is a rather unique and impressive feature that was initially introduced by Sony on the Xperia Sola. It basically allows the user to “touch the screen without touching the screen.” Hovering your finger over the screen, the device interprets this as a touch. This is done by making use of the sensitive capacitive touch panels found on modern smartphones.
Initially developed for interaction with a specific set of live wallpapers, the technology has been ported to interact with the complete user interfaces of the Xperia Sola and Samsung Galaxy SL. Now, we can add the Samsung Galaxy S Plus to this growing list.
Having read the news on the Galaxy SL port, XDA Forum Member matorno1 has done some investigating and has managed to port floating touch to the Galaxy S Plus. As with the previous device ports, things may be a little finicky, and using it will require some practice. Some basic settings adjustments have also been suggested by atorno1 that require some trial and error. Just make sure you don’t go too far with these adjustments and end up completely disabling screen touches!
If you want to try out floating touch on your Galaxy S Plus, head over to the modification thread.
The last time we brought you news about TWRP, it was to announce that TWRP 2.2.2 had been released. It had fixed a lot of bugs from the initial release of TWRP 2.2 and added a few new features. Very recently, TWRP has been updated again to version 2.3.
There were a whole bunch of awesome improvements with TWRP 2.2 and a lot of unique and brand new features as well. TWRP 2.3 promises no less. The official change log includes:
Rebased onto AOSP Jelly Bean source code
Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
ADB sideload functionality from AOSP is included in 2.3, see this link for more info
Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
Faster boot times
Added charging indicator while in recovery (only updates once every 60 seconds)
Additionally, XDA Recognized Developer Dees_Troy has reported that there is now support for spaces in backup names. Before, if you added a space to the name of a backup, it would not restore. Now users can use whatever naming convention they want.
One of the biggest changes, though, is all of the TWRP being rewritten in C++ and its move to recovery API 3 instead of API 2. With the code rewrite, it will allow TWRP to update more quickly and with more stability. With the API 3 change, it means that some flashable zip files may stop working because the developer needs to update the update-binary. If you don’t want to wait for the developer, or the developer has ceased working on the project, you can find one to use on TWRP’s official website. To install the latest TWRP, you can use the Goomanager application. Simply open the application, hit menu, and install open recovery.
If you want to check out the latest TWRP recovery for your device, check one of the links below.
You may have heard of floating touch before. It actually comes stock on the Sony Xperia Sola for certain functions. With a little mod work, developers were able to floating touch working as a full fledged feature. As it turns out, the Sola isn’t the only device capable of floating touch. Now, the Samsung Galaxy SL can as well.
Essentially, shriomman took the earlier method and identified the parts that needed to be changed for floating touch to work. In fact, it only takes two lines in terminal, which means you’ll need Terminal Emulator to use the method. After you enter everything in, you’ll be able to use your touch screen without actually touching your touch screen.
In theory, this is very cool because that means the Sola isn’t the only device that is capable of this. In fact, since it really only involves modifying touchscreen sensitivity, all devices should be capable of this in some form. In practice, however, it really can’t be used for day to day activities. According to shriomman, navigation can be hard at times and basic tasks like texting can be a pain. It’s still definitely something fun to try.
For more information and a proof-of-concept video, check out the original thread.
October 9, 2012 By: Former Writer
It’s quite common for a hacked phone to not play nicely with OEM software created to interface with the devices. Notable examples include HTC Sync and Samsung Kies. When a phone is rooted and running custom firmware, these services may not read the phone properly and may not recognize the device as one that needs an update. In rare cases, they don’t even recognize the connected device as supported. Samsung Galaxy S Blaze 4G owners have been having a problem with Kies recently, and now there is a fix.
Okay, to call it a fix may be stretching it. XDA Forum Member jparnell8839 has figured out that Kies won’t recognize the phone on any stock firmware after UVLB7. So if you’re running something that came after that and want the next official update, you will run into an error where Kies claims the phone isn’t compatible with their software upgrade service. Says jparnell8839:
Finally, I thought “hmmm, it still says custom binary when im in download mode, even though I’m stock with stock recovery” so I went to sammobile and got the pre-july 16th image (UVLB7) and flashed just the tar.md5 file (no pit) made sure repartition wasnt checked, etc. in Odin
upon reboot, Kies immediately recognized there was a firmware update and pushed me up to UVLF4 (flash counter is at 4 btw). When it rebooted to download mode from Kies, it said Samsung Official binary this time
In order to be more helpful, jparnell8839 has uploaded the firmware that was used to fix this problem for others to download and use. With it, stock users can upgrade to the next update easily. For more information, go to the original thread.
September 28, 2012 By: Former Writer
Not too long ago, we brought you the wonderful news that the original Samsung Galaxy S variants got official CM10. Unfortunately, there were a few versions that were left out, including the Samsung Galaxy S Plus I9001.
The first push to get AOSP Jelly Bean of any kind began with this thread which is currently maintained by XDA Forum Member demon434. It helped give the community a place to troubleshoot issues and test preliminary builds. Now, XDA Senior Member Doomsday94 has released an unofficial preview build of CyanogenMod 10.
The build is a little shaky, hence why it is called a preview. There are a number of things working, to include:
Video (sometimes youtube crashes)
Receiving and making calls
USB mass storage
HW accelerated gui
HW accelerated video
60% project butter
And here are the things not working:
full butter experience
many other things
As you can expect, this is definitely not daily driver material just yet. However, it provides Galaxy S Plus users with a base from which to proceed and a known number of bugs to squash. It may not be long until there is a more stable version for users to flash.
For more information, check out the original thread.
September 15, 2012 By: Former Writer
When a device is first rooted, it usually doesn’t take very long for a custom recovery to appear as well. In many cases, root and recovery are released simultaneously. Of course, sometimes it takes a little longer than usual to get something working on a device and thus users may have root but no easy way to install things like custom ROMs, custom kernels, or modifications that could make the device even better. For Samsung Galaxy S Advance owners, after a long, long wait, you now have a custom recovery.
XDA Forum Member diego-ch, along with the help of other developers, has released a kernel that also packs the latest TeamWin Recovery Project recovery on it. As with most Samsung devices, the way to install the kernel is through either Odin or Heimdall. A word of warning: Installing the kernel will increase your flash counter. Aside from having a functional custom recovery, the kernel also adds CIFS support. If you’re a Galaxy S Advance owner and you’ve been looking to flash some easily, check out the original thread.
[Thanks to XDA Recognized Contributor varun.chitre15 for the tip!]
September 4, 2012 By: jerdog
For those who love to receive updates to their mobile devices, the Telus, Bell and Rogers versions of the Samsung Galaxy S III (SGS-I747M) are currently getting a maintenance OTA update from Samsung.
The update purportedly brings improved stability, bug fixes, better battery life, and screen brightness adjustments available via the notification bar. The baseband is I747MVLLH1 with the OS Build being IMM76D.I747MVLALH1 (Android 4.0.4). There is currently no word on if the AT&T version will be receiving an OTA or not.
For those currently running a stock, unrooted ROM you should be receiving an OTA notification, but if not you can always check manually via Settings > About Device > Software Update. If you are running a rooted ROM then you will need to wait for a developer to package the update for you.
Head on over to the discussion thread to chime in or follow for the latest notifications.
August 29, 2012 By: Former Writer
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.