• 5,782,867
    REGISTERED
  • 39,828
    ONLINE NOW

Posts Tagged: Samsung Epic 4G Touch

inkeffec

Not too long ago, we brought you news about one of Samsung’s eye candy features being successfully ported to the Epic 4G Touch‘s Jelly Bean leaks FL16 and GA10. Regardless of how useless this is in terms of device functionality, one cannot brush aside the fact that a lot of work went into the porting process and reverse engineering of device specific code. The amount of work put by all the devs involved was substantial, and anyone who had followed the development thread could attest to that. Now, the challenge is complete and in order to have it installed, the only thing anyone would need to do is flash the zip file through recovery and presto! 18 shades of color are automagically added to your ROM. However, if you are here for the journey as opposed to the destination, then you might enjoy what XDA Recognized Contributor tdunham has prepared for you.

As you have seen in recent days, tdunham has been hard at work writing up and putting together guides on how to manually add your own mods to your JB ROMs on the E4GT. As stated earlier, this is a great way for anyone to learn and get dirty into the huge world of Android modding. The guide revolves around having to modify android.policy.jar and secsettings.apk, much as what was the case for the previous tutorials. However, due to the complexity of this particular mod (and the pre-requisite of having other mods before this one), the guide is a little more involved than others. Tdunham not only explains how to enable this mod, but also explains how to add up to 18 colors for the effect. Keep in mind also that the work involved in this guide involves smali edits, which has been described by many as a “spawn from hell”. So, make sure that you know what you are getting into before proceeding. There is no harm in doing a little bit of research before diving into this. You know… just in case.

Since all this is done out of your phone, there is little risk involved. However, once you are done and ready to flash your mod, make sure that you make a back up since there is a chance for messing things up and your phone going into a bootloop, which would likely force you to reflash your ROM. Again, this is a great way to get involved into coding and Android modding. Please make sure that you understand this and happy learning!

Ripple effect must already be enabled for this mod to work.
This mod is pretty complex and requires a good deal of tedious work.

You can find more information in the original thread.

Want something published in the Portal? Contact any News Writer.

tar-gz

For many people out there, ROM files are nothing but a black box full of fun and surprises awaiting to rejuvenate their devices. Depending on the phone manufacturer, you may see the ROM files in the form of zip files, which are normally flashed through recovery and are the preferred format by many devs on XDA. However, there are times where the files will not be in a recovery-flashable format, but must come packed in a different type of black box. This is the case for Samsung devices in general. More often than not, the updates from Samsung will come packaged in tar format, that can only be flashed through programs like Odin, Heimdall, and Mobile Odin. These packages contain all of the goodies that we crave, but they are slightly more complicated to crack open than regular zip files. Since we cannot always wait on a dev having the time to turn the tar files into usable ROMs or to extract things from them, XDA Recognized Contributor rwilco12 has decided to put together a guide to help people get what they want out of tar files whenever they want to.

The dev starts off by saying that one of the easiest ways to go about doing this is via dsixda’s kitchen, but since there are people out there who like more manual approaches, he has been kind enough to provide a guide that does not require said approach and can be done directly from a Windows environment. Steps are relatively simple to follow, and are required to have a few programs for your PC before getting started, namely 7-zip (or some WinZip-like utility), DiskInternals Linux Reader, and SGS2Ext4. The links for all of these have been provided in the thread, and they are all free. The process (in a nutshell) involves unpacking the tar and turning it into an image file (.img). From that point on, the .img gets turned into .ext4.img and then mounted via DiskInternals. You should then see a virtual drive on the PC, which will have this image mounted. From this point onward, you can navigate through the internal directories of the file and simply picking and choosing the files, apps, and any other goodies that you want to extract.

Again, this is a simple process that is further simplified by using a kitchen like dsixda’s (and in fact, the method itself is similar to what the kitchen does). However, getting down and dirty with not-so automated processes is one of the best possible ways to learn how to do something. Teach a man how to fish, if you will. We hope this helps those of you trying to learn proper development. Please post any feedback you may have.

I’ve received a TON of PM’s and emails asking how to do this and I’ve decided to do a write-up for everyone.

You can find more information in the original thread.

Want something published in the Portal? Contact any News Writer.

Advertisment
AOSPLock

There is no better feeling than making your own device, truly your own. The way we do this at XDA is by tweaking the daylights out of it. However, there is more to life than simply installing APKs or flashing zip files through recovery. There is a far more rewarding process in tweaking your device, and that comes from the joy of doing things oneself. If not for the eye candy pleasure provided, it is great for the sake of learning how to do something new. But, wait! Where to start? Android files are numerous, large, and require a certain skill set to master and modify, right? Well, yes, but luckily we have people like XDA Recognized Contributor tdunham who can definitely lend a hand during the learning process.

In this particular instance, the dev shared a way to enable the AOSP lockscreen on the Epic 4G Touch (running Jelly Bean leaks). Because most manufacturers like putting their own flavor on their devices, it is highly unlikely (with a few exceptions) that you will purchase a device that comes with a stock Android lock screen, and Samsung is no exception. The guide that the dev has posted will allow you to see and understand what code is used to enable the missing, infamous AOSP lockscreen to the device’s already wide arsenal of eye pleasing effects. This is particularly useful if you like the stock ROM and really don’t feel like flashing to AOSP ROMs. And again, the end result is that you get the look that you want and leave a more knowledgeable individual at the end of the process.

What are you waiting for? Get the tools needed to decompile the required files (namely android.policy.jar and secsettings.apk), put on a fresh carafe on your Mr. Coffee machine, and let your hungry curiosity take over. Remember that you will need certain tools to do this (other than coffee), so make sure that you are ready. Please share your experiences and any tricks you may have learned along the way.

nable Aosp Lockscreen with toggle in Jellybean

Credits to Mirko DDD for original guide.

You can find more information in the original thread.

Want something published on the Portal? Contact any News Writer.

powermenu

Often times, we tend to find stock ROMs for our devices boring, outdated, and more often than not, lacking tons of basic (basic for us anyway) functionality. Being who we are and our somewhat colorful history of tinkering with things, we tend to improve these stock ROMs by adding new features. The problem with this habit, pretty much ever since Android was introduced, is that the mods done for one OS tend to not work for the next. (While this was also the case for Windows Mobile, at least most mods worked well across ROMs and devices unless there was a significant version change in the OS such as going from WM5 to WM6.) So, how do we make sure that the knowledge about doing something like this remains alive and well? Simple, you teach a man how to fish, and that is exactly what XDA Recognized Contributor tdunham has done with his latest set of contributions to the site.

Adding items to the power menu has been around since the WM days, so this is not a new mod by any means. However, the way it is implemented into ROMs is often times different when jumping from OS version to OS version. In this particular case, the existing mods that could easily be found on most custom GB and ICS Roms for the Epic 4G Touch were rendered useless (the flashable mods, anyways). However, not only has tdunham provided the mods for the new JB leaks, but he has taken things a step further and decided to write a guide on how to add the code yourself! He goes into good detail as far as what lines of code need to be added where in framework-res.apk and android.policy.jar. Last but not least, the guide also shows how to remove unwanted items from the menu as well. So, if you wanted to get rid of the “take screenshot” option, now you can.

Please do keep in mind that you will need to know how to open, edit, decompile, and recompile these files in order to modify them. There are various guides throughout the site and tools that can aid you in this. If nothing else, Google is always your friend. Please leave some feedback on the thread and share what you have done so that others can learn as well.

This will allow you to have Recovery and Bootloader (download mode) right in the Power Menu selections.

You can find more information in the original thread.

Want something published in the Portal? Contact any News Writer.

inkeffec

More often than not, a new device will come out, impressing people left, right, and center with lots of eye candy, special features, and innovative concepts. Being the type of people we are, we want to have all this, but without really having to dump more cash on top of a new device. After all, not having a fancy launcher on your S4 loaded smartphone shouldn’t mean that you have to buy yet another device just to satisfy your cravings for the aforementioned eye candy, particularly when your device should be (in theory) perfectly capable of handling all you throw at it. These are the times when devs step up to the plate and do what they do best: hack the daylights out of our devices to get things going.

This is the story of a new feature lock screen effect introduced by Samsung in their 2012 line up. The TouchWiz stock lock screen for Jelly Bean ROMs can be heavily customized to allow for several features such as sensor actions, shortcut icons (a la Sense), and other visual effects such as a water ripple and an ink effect that show up upon touching the screen. Both of these are normally found in Galaxy Note 2 JB ROMs, and despite some similarities, unfortunately they are not found in their older device counterparts. As of the leaked JB ROM known as FK23 for the Epic 4G Touch, XDA Forum Member _dan was able to get the water ripple effect working by modifying several files in the framework. Taking the lead from this, and upon people requesting it (as well as sheer curiosity by others), XDA Forum Members evo3d6 and Stryke_the_Orc set out on a trip to port yet another one of those appealing visual effects, the ink effect. After advancing the work and getting things going, both of the aforementioned were almost successful in getting the effect working but were missing something. Thanks to the help from XDA Recognized Contributor tdunham and _dan, the missing pieces of the puzzle were found, and the ink effect was successfully ported over.

Installation is rather straight forward, and it is available for FL16 andg GA10 leaks of JB. Simply place the packs in your SD card and flash via recovery. The devs are continually improving this pack. For instance, the newer version is loaded with 18 colors to choose from! One word of advise though is that the ripple effect must be active in order for the ink effect to work. Remember to make a back up just in case something happens.

GA10/FL16 Stock Ink Effect Mod
(This mod is for deodexed roms only)

Ripple mod & toggle included. It won’t work without it.
Source decompiled files included. Devs use Winmerge to diff the files if you want to use this elsewhere.

You can find more information in the original thread.

Want something published in the Portal? Contact any News Writer.

COT-Cannibal-Open-Touch-Recovery-Screenshots

When there’s mention of custom recoveries for Android, ClockworkMod is one of the first names that comes to mind. In the past, we had AmonRa recovery, which still retains several faithful followers. Lately, TWRP has emerged as another excellent custom recovery that many have started to favor over CWM due to a larger feature set and killer interface.

COT (Cannibal Open Touch) is a new recovery aiming to bring some of the best features from other options in a single package. The project comes courtesy of XDA Forum Members Drew Walton (Project Head), thenameisnigel, and Sblood86.

The current feature list of COT includes:

  • Support for both Edify and Amend scripting allows flashing all ROMs
  • Theme support
  • Get out of recovery boot loops
  • Touch screen button controls
  • Compatibility with Xionia nandroid backups
  • GooManager support
  • Internal e2fsprogs for size
  • Backported “retouch binaries” patch for ICS/JB compatibility
  • Advanced Backup
  • Delete old backups
  • Persistent settings
  • User-defined backup locations
  • ADB Sideload
  • Touchscreen calibration

COT recovery v2.1 is currently available for the following devices:

Development is planned to bring COT recovery to other devices soon, starting with Galaxy Nexus, Samsung Galaxy S III and the Barnes & Noble Nook Color. You can learn more and download the appropriate recovery for your device using the links provided above.

Jelly Bean

When it comes to fixing bugs in ROMs, most users don’t care how the fixes are applied as long as they work. So it happens sometimes that fixes are released before they’re merged into the actual ROM. This provides faster relief to some bugs, and devs don’t have to rush to get things merged and re-uploaded. There is such a tweak pack for the Samsung Epic 4G Touch that fixes a couple of bugs and adds some new features.

It was released to XDA by Senior Member Exit_Only. For clarification purposes, the tweak is only available for AOSP-based ROMs. The stock, OEM-skinned Jelly Bean gets to keep its bugs for a little while longer. Here’s everything included in the tweak:

What’s included?
Library Fix for Gyroscope and Compass (Stable)
Several Scripts to increase battery life and performance (Alpha)(major wip)
GPS Modifications for better and faster GPS Lock (Alpha)(wip)
Sysctl Tweaks (Stable)
Build.prop Tweaks (Alpha)(wip)

So while the Gyroscope and Compass fixes along with the Sysctl tweaks are stable, everything else carries with it the YMMV title. Users can expect the WIP items to become more complete as new builds get released. Users have confirmed that the fixes work, so if you want to see an end to your sensor woes, this is a tweak to try.

For more info, go to the original thread.

epic41

It seems that the Sprint owners still on the Galaxy S II who did not upgrade to the HTC EVO 4G LTE or the Samsung Galaxy S3 are still due for an Android update. Just a few months ago and after MANY months of waiting and delays, Sprint and Samsung decided to release, the awaited ICS update for the Epic 4G Touch. This was received with open arms by the community, but it unfortunately came well after the announcement (and surfacing) of Google’s newest Android iteration, Jelly Bean. Being the grateful bunch that we are, the first reaction to ICS release was the expected “when are we getting Jelly Bean?” A few AOSP builds started surfacing, which are fully functional (minus a few bugs here and there), but nothing for those who want something that resemble stock.

A couple of weeks ago, XDA Recognized Contributor sextape announced that he and his team got their hands on the first official JB leak for the device, FJ05, but this was never released due to potential security issues. Shortly after, FJ10 surfaced and it was kept under the same veil as its predecessor due to similar concerns. Just a few days ago, the team decided to make it public. The ROM itself, according to some of the feedback is very, very smooth, which leads some to speculate that this build actually has Project Butter in it (however, unconfirmed). Having said that, the leak seems to be in a very early stage, as it is ridden with bugs which include random reboots, over heating, no 3G, and several other minor bugs. On top of that, the only way to flash in and out of this build is through Odin. This cannot be flashed from mobile options such as recovery or even Mobile Odin. Also, the ROM is not rooted in its current state, but several devs are working towards trying to release a rooted, more stable version of it.

Please be wary when flashing this build and make sure that you read through the feedback and recommendations in the thread. Having said this, if you decide to go forth, happy flashing!

 Hello There After much debated within our team we decided to release this for public testing!!

The official jelly bean for the epic4g touch can be found here.

You can find more information in the original thread.

Want something published in the Portal? Contact any News Writer.

Epic Touch

In most cases, a nagging issue or consistent problem is eventually fixed by our talented developers and members here at XDA. We’ve seen ends to a plethora of issues, including signal problems, slow data, redraw, and all sorts of other things. However, not all issues can be solved so quickly. Samsung Epic 4G Touch owners know this first hand, as GPS functionality has been somewhat problematic since day one. Now, members and devs are doing something about it.

The thread was started by XDA Senior Member Gamingphreek, but there have been contributions made by a number of members and developers. There hasn’t been a solution found yet, but a lot of relevant information has been gathered regarding the ongoing GPS problem. In short, the issue is that the GPS takes a very long time to find a lock, and when it does, it isn’t very accurate. This affects mostly ICS AOSP users.

So far a number of solutions have been thrown out. These include changing radios, juggling ROMs, and applying a number of popular or otherwise well known fixes. However, in the words of Thomas Edison, “I have not failed 700 times. I have not failed once. I have succeeded in proving that those 700 ways will not work. When I have eliminated the ways that will not work, I will find the way that will work.” So, it is only a matter of time before the thread begins to generate positive results for users who have GPS woes on their Epic Touch. For additional info, check out the original thread.

e4gt-stock

While running CyanogenMod on a CDMA device has many advantages, one glaring disadvantage is the ability to update your PRL (Preferred Roaming List) or data profile, which are only available via stock ROMs. Often times if you need to run a GPS fix or update your PRL, you need to backup your CM9 install, restore to a previous stock ROM, do the ROM dance, run the desired process, dance a jig, restore to CM9 install, and hope for the best. Well now you don’t, thanks to the Epic Touch CM team.

The Epic Touch CM team has put together a nice temporary ROM which boots the FF18 stock firmware from the /EMMC partition on the Samsung Epic 4G Touch without changing your current ROM. This temporary ROM allows you to do the following, and more:

  • Update Profile
  • Update PRL
  • Sprint Activation
  • Dial codes and diagnostic mode

XDA Senior Member slick_rick has put together the discussion for this process, so visit the original thread and give it a shot.

Epic Touch AOSP Goodness

For those who haven’t heard, there have been some issues with Samsung ICS leaks and brick bugs. The Samsung Epic 4G Touch was no exception to kernel- and recovery-related issues. When CM9 ROMs were were first coming out on the Epic Touch, they didn’t come with a custom recovery. To flash to a different ROM, users had to flash a Gingerbread kernel containing the proper ClockworkMod recovery, and then use that recovery to flash to a new ROM. This is because the kernel being used suffered from similar issues as the hard brick bug on other Samsung devices. Thus, it meant that trying to wipe and flash a different ROM could result in a hard brick. That problem is now solved.

XDA Recognized Developer chris41g along with XDA Senior Member FranceIsBacon are currently building AOSP-compatible kernels with patched ClockworkMod recoveries. To put it more simply, they have disabled the emmc_cap_erase, which has been identified as one of the big troublemakers in the whole brick bug debacle. The purpose of this is to allow users to flash an AOSP-based ROM, flash their kernel, and then use that recovery to flash to whatever else they want without fear of bricking their devices.

Currently, the kernels are considered to be in the testing phase. They do work and users have reported as much, but none of them are good enough for Chris41g to declare stable. On top of being for AOSP-based ROMs and having a patched recovery, the kernel also has a number of other features including:

New Schedulers
SIO
VR
New Governors
LulzActive
SmartassV2
Hotplug
Pegasusq
CWMv6
Patched eMMC
Battery Tweaks
Speed Tweaks

So if you’re running AOSP-based ICS ROM on the Epic Touch, you may want to look further. Those interested should head over to the original thread.

[Thanks goes to XDA Elite Recognized Developer Entropy512 and XDA Developer Admin / Elite Recognized Developer pulser_g2 for the consults regarding the brick bug.]

Samsung-Logo

When flashing an AOSP ROM on a CDMA phone, it’s a win-some lose-some affair. You gain the functionality that comes with a pure Android experience. However, you traditionally lose USB Modem and Diagnosis Mode on your device. For those who are unaware, USB Mode and Diagnosis Mode are accessed via codes you enter into the dialer. This is not only required to activate the phone on some networks, but also helpful in alleviating some problems like restoring your IMEI using QPST. However, for many Samsung devices, that is no longer a problem. Now, you can get all this functionality back without flashing back to a stock ROM.

XDA Senior Member autoprime has put a thread that not only gives a profound amount of information but also provides a script to make it all easier. The suggested way is to use a script manager application to apply the script. As autoprime explains:

Open script manager, browse to script files on SD card, select script, set to run as SU and hit save. Do this with both scripts. Now you can use the script manager in the Widgets section to create shortcuts on the desktop for easy access. Hopefully these scripts get built into CM10 so this method is no longer needed. You may or may not have to unplug/plugin the usb cable after new mode is set.

Also provided is a plethora of instructions. This is a huge step for the supported devices, which include:

The Epic 4G Touch was having some troubles with the script, but autoprime managed to fix it in short order. Additionally, this method will soon support other devices. So if you’ve had to flash back and forth between AOSP and stock just to use these codes and your phone is supported, it’s time for some celebration.

 

To learn more, head over to the original thread.

 

Update: Given the abuse, the link to the thread has been removed. We apologize for any inconvenience.

Nightmode

There is not much more painful to the eyes than turning on a bright display in a dark room. There are applications out there with Night Mode, but they don’t always work optimally—often eliminating colors, which makes things more difficult to read. This is a problem that the Samsung Epic 4G Touch no longer need experience.

XDA Senior Member arpruss has developed an application called GalacticNight. It requires root because it modifies the mdnie* files to adjust the colors for proper night vision. Arpruss explains the application more in depth:

I know there is ChainFire3D, which is a great app, but this is better for nightmode. ChainFire3D does nightmode by simply dropping the green and blue colors. That way of doing things can make some things invisible (e.g., some things in the UI may be pure green, and then they’ll turn black). GalacticNight, instead, properly converts RGB colors to luminosities, and then sets the red (or green or white) intensity according to the luminosity.

There are also a variety of settings based on how you want your phone to look or behave. For instance, the reverse colors mode will change everything around, so white browser backgrounds become black. Additionally, the screen remains mostly dark, which saves battery life on AMOLED devices. The initial version of the application was only compatible for Epic Touch Gingerbread, but since has been found to be working on a number of other devices.

For additional information and the up-to-date list on device compatibility, check out the original thread.

[Thanks to the_scotsman for the assistance!]

Advertisement

XDA TV: Most Recent Video

Buy/Sell on Swappa

  • Nexus 5 (Unlocked) buy | sell
  • Galaxy Note 3 (T-Mobile) buy | sell
  • HTC One M7 (Verizon) buy | sell
  • Galaxy S 5 (Unlocked) buy | sell
  • Nexus 7 2013 buy | sell
  • Swappa is the official marketplace of XDA