• 5,730,446
    REGISTERED
  • 46,469
    ONLINE NOW

Posts Tagged: Samsung Epic 4G Touch

samsung epic 4g touch

Sprint has said that it will remove Carrier IQ on all of its devices, and is continuing to make good on that promise with the latest OTA update targeting the Samsung Epic 4G Touch, Sprint’s own version of the Galaxy S II. The new update has the version S:D710.0.5S.EL29 with the following changelog:

  • Security update
  • Dismissing multiple calendar alerts
  • Commercial Alert System (CMAS) activation

Of course, “security update” is corporate doublespeak for “Carrier IQ removed”. The update will roll out in the next 10 days, by which all eligible devices should have gotten it.

Sprint previously removed Carrier IQ on the HTC EVO 3D and, one week later, HTC EVO 4G, EVO Design 4G and Samsung Epic 4G.

If you experience any issues or have something else to share, join the discussion in the forum thread.

device20111213095149

Assuming you haven’t been living in a cave the last few months, you’ve heard about Carrier IQ—a baked-in software package that Google CEO Eric Schmidt publicly labeled a key-logger. Thanks to the diligent work of XDA Recognized Developer TrevE, we’ve brought to light some of the issues surrounding the software package several times in the past.

Luckily for us, it now seems as if OEMs and carriers are starting to understand that WE DON’T LIKE IT! Enter the EL13 leaked firmware for the Samsung Epic 4G Touch on Sprint. Using XDA Recognized Developer supercurio‘s Voodoo detector app, fellow forum member Calkulin has verified that the leaked build is indeed Carrier IQ free!

Biggest difference I see so far doing a comparison, is no CIQ libs are included anymore, so either Samsung pulled CIQ from it or hide it even more. I’ll run the detector apps to see here shortly to verify
EDIT: Seems Samsung & Sprint listened, no CIQ in this ROM

Rather than just hiding the libraries, the update seems to do away with CIQ altogether. However, let’s not get our hopes up too high just yet. While you can install EL13 on your own device, the build is still technically leaked. Furthermore, we have not a clue as to when (or even if) it will be officially released. That said, it’s mere presence shows that someone, somewhere out there is actually listening to the customers. Bravo. Now just push it out to all CIQ-ridden devices ASAP!

If you’re interested in giving this a shot on your own device, be sure to head to the original thread.

Advertisment
11x05101719

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 »

4cbb234c-5e70-ee43.jpg

Bits and pieces of Ice Cream Sandwich are everywhere, and now Samsung Epic owners can get their hands on the ICS Dialer courtesy of XDA Senior Member ssconceptz.

The XDA member has created a clone of the ICS Dialer built off the stock Contacts.apk from the Galaxy S II Epic 4G Touch. Please note that this is not a port and that your tabs will not be ICS tabs (as per the image), since this will reflect the specific ROM theme for your tabs.

The file should work on any ROM for Samsung Epic 4G Touch devices.  There are two options for installation – a simple installable app or a flashable zip.

For more information including to download the files, head on over to the application thread.

Ext4-Filesystem-Is-Closer-2

As you may recall, the Samsung Galaxy S 2 US sibblings just got launched into the wild and because we could simply not sit idle with our arms crossed, the devs in our forums have started pounding their Epic 4G Touchs with the fists of development. As you are probably aware by now, there is always a discovery process before true development can actually take place. During this time, information regarding the internals of the device is gathered until enough is in place to start doing things like rooting, installing apps, flashing Rome, radios, etc. Well, XDA Forum Moderator jerdog recently opened a thread where he describes the memory partition’s map on this device. This information seems to be crucial in the sense that without this, a flasher would simply not know what goes in which area of the device. Put in simple terms, either Heimdall or Odin need this information in order not to soft brick your device.

This information may hold other keys as well that could unlock more potential out of the device. Please take a look and see if you can do anything with this in order to help out in the development of this new offering from Samsung.

Here are the partitions for the Epic 4G Touch as identified by Heimdall. The .pit file was successfully created by odub303

This .pit file contains the partition map for the device. It tells Odin and Heimdall (another piece of flashing software, which i find to be MUCH better than Odin) where to flash the different files such as the boot.bin, sbl.bin, zimage (kernel), system, data, cache, recovery, modem, etc. Without the .pit file, Odin may not know where to flash a file, and you could end up with a soft bricked device. AFAIK, there isn’t anything we can flash yet. We need to wait for someone to take the stock Epic 4g Touch kernel and add CWM, root, su and busybox.

You can find more information in the original thread.

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

Battery_Drain

For whatever the reason, some people can simply never find what they are looking for and thus, they end up creati.g their own solutions for their problems. This was the case for XDA member xak944 whom apparently wanted to have battery stats regarding power consumption of his Epic 4G Touch. I know what you are thinking, there are tons of apps out there which could provide this information. However, the dev wanted to have one that could be used via shell. As there was none, this pushed him into researching a bit and ended up with a script to monitor the usage via shell. This will only work on the aforementioned device due to several things being hardcoded in the device itself, but according to the dev, it should be fairly easy to adapt this for others as well.

Please make sure that you have a rooted device with busybox installed. Take it for a spin and leave some feedback if you can.

 I wanted something I could run in a shell (adb) that would give me similar statistics, namely the battery discharge rate. I couldn’t find any such tools or scripts, so I wrote one.

You can find more information in the original thread.

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

No USB Host

The world of mobile technology is a rather complicated one with lots of strings and intricacies that only the most knowledgeable of business analysts could understand. I say this because for the likes of technology advocates like ourselves, sometimes decisions made up in the higher places of power of manufacturer’s companies really make no sense. However, before getting into the nitty gritty of the situation, let me take a step back and remind all of you that manufacturers know and understand the power that our user base has over their sales and that the word of a “geek” with anything related to technology could be worth far more than simply throwing money away on advertising. With this in mind, several companies of the likes of HTC and Samsung have gotten intricately closer to developer forums like xda-developers. They want to try to get better rapport with their end users but also, they recognize the power that freelance developers, hobbyists, and enthusiasts play in their business model. With this in mind, we have seen them do things like release product updates, sources, and some information that was previously not available in attempts to get, as stated earlier, closer to devs. The latest installment of good faith by Samsung came with the official release of the KI firmware, which is their first official build of 2.3.4. Happy and excited about it, our devs decided to do what they do best: dissected it and looked for bugs. XDA Recognized Developer Chainfire made a post in his own personal blog where he talks about his findings after cracking this one open.

You will find the story below, but the basic premise is that there are a few things that Samsung has either forgotten to include or deliberately excluded from this new firmware. The first one is USB host API support for third party applications, and if you are not certain what this means, it is actually rather simple when put in context. Lets assume that you used to play Need For Speed with a USB controller rather than by using the device itself. Well, you will no longer have this option as this ability of the program to interact and communicate with peripherals has been eliminated. However, the device can still use USB peripherals assuming that whatever you are trying to connect is supported by the kernel. However, if you are a dev, this is the least of your worries because they did do something else. The bootloader has also been patched to ensure that the kernel flash counter cannot be reset. This means that if you are a flash-a-holic and you are planning on being able to return your device for warranty reasons, anyone with access to this little number will know that you have flashed it numerous times if it is not 0, even if you do return everything to stock prior to the return. Last but not least, XDA Senior Moderator pulser_g2 also chipped in the discussion, letting Chainfire know that the SIP support was also completely removed from the KI firmware.

We find ourselves at a cross roads here. We certainly understand that manufacturers are, for the most part, at the mercy of “higher” powers when it comes to decision making, which would explain things like the bootloader patch. However, from a sales standpoint, there is really no reason to remove USB host API support from the kernel. This little fact leads me to believe that it was either a mistake and someone simply “forgot” to cook this in, or we have bigger issues at hand as there is really no real reason for this to be removed. So, what say you Samsung? Do you have an answer for your loyal customers? You have been doing well lately and have been addressing the developer community in a rather timely manner. You may want to consider visiting this small issue as it should be no reason to neglect putting it back in. We believe in you and that you really want to please your user base. The ball is in your court now…

 

The first official Android 2.3.4 series firmwares (KI) for the Samsung Galaxy S2 are now finally available.

Two things immediately stick out:

USB host support

Samsung has removed the USB host Android APIs from this release. The kernel is still USB host enabled, which means your memory stick (etc) will still work. However, 3rd party applications can no longer make use of USB host capabilities to communicate with peripherals through the Android APIs, so only USB devices with direct kernel support can be used.

One wonders why Samsung would remove this feature that has been present on SGS2 firmwares for months, especially since having the feature has generated a lot of good press in combination with DSLR Controller [XDA].

Bootloaders

Samsung has also modified the bootloaders (sbl specifically) to prevent use of the USB JIG to erase the custom kernel counter and warning triangle. Workarounds to remove the custom kernel warning triangle are still available (the non-JIG triangle removal method as described in the CF-Root thread [XDA] still works), but there is no workaround to reset the custom kernel flash counter.

To keep being able to reset the counter, you need to flash the new firmwares without the bootloaders, or flash old bootloaders separately (KH series bootloaders work).

Intratech has both the latest firmware with the bootloaders stripped out – as well as an old bootloader package for those who have already flashed the evil bootloaders – available in his firmware thread here [XDA].

Notes

[1] Information based on Nordic official “KI4″ Android 2.3.4 firmware

[2] It appears the Sprint version of the SGS2 (Epic 4G Touch) doesn’t even have kernel support for USB host at the moment

[3] The warning triangle mentioned is a yellow triangle that shows on screen while booting if you are running a custom kernel on your device

[4] The custom kernel counter is a counter inside the device that tracks how often you have flashed a custom kernel. It is assumed your device will not be serviced under warranty if this counter is not 0

[5] I have just been informed by pulser [villainrom] that Samsung has also actively removed SIP support from this firmware series.

You can find the original article here.

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

Thanks Chainfire for the tip!

epic 4g touch

Well, we truly gotta give it to Samsung this time as they seem to be making a turn for the better and trying to get close to developers at the same time. XDA member Korey_Nicholson just informed us that apparently the Epic 4G Touch did not get released by itself. It looks like the kernel sources (D710) are also available for download in the Samsung website. So, for all of you who were impatiently waiting to start developing custom work on this brand new device, now is your chance. Also, this goes to show all the skeptics in the crowd that even large sized companies can have their good days as well.

In any case, you will be able to download, tweak, compile, rinse, and repeat to your heart’s content. So, what are you waiting for? Go for it and if you happen to create something good, make sure that you share it with the rest of the community.

Scroll down to find D710 and have fun building those kernels!

You can find more information in the original thread.

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

Thanks Kn0wBuddy for the tip!

Epic 4G Touch Forums Added

September 13, 2011   By:

logo

Well, it looks like we are just a few days away from the official release of the Samsung Galaxy S2 family of devices here in the US. In order to celebrate this, we have started being proactive and opened the first (of a few) forums which will serve as a home for the different Galaxy S2 variants. The first one up is the much anticipated behemoth, the Epic 4G Touch for Sprint. This device sports a larger screen at a 4.5″ and much of the same flavor that the other SGS2 variants have in terms of raw power. This will come equipped with WiMax, a beautiful Exynos processor clocked at 1.2 GHz, Android 2.3.4, 8MP camera with LED flash (thank you for this),  and a few other goodies that will ensure that you get the most out of your Sprint experience.

So, if you were thinking about your next device and happen to be on Sprint, you should seriously consider this one. Reports from the European users of the SGS2 are nothing but good, so definitely something to consider. If you have one of these already and found anything interesting about the US versions, make sure that you share this with fellow members of the community.

You can visit the Epic 4G Touch home on XDA here.

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

 

 

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