yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] steindog99:
Am I correct in understanding that at this time there is no way to get CWM Recovery onto any of these ICS builds?
[Samsung Epic 4G Touch] RainMotorsports:
There is an FD02 kernel with the Rogue version of CWM. Factory Reset can insta brick the phone permanently. Flashing roms was considered dangerous not sure if it was narrowed down yet. I have not kept up.

Best thing to do is mobile odin the el26 cwm kernel when you need to do things. The stock CWM, even stock recovery will have the issue since its a Samsung kernel issue.
[Samsung Epic 4G Touch] sfhub:
We've actually duplicated the problem with the stock Samsung ICS kernel repacked with just the unlocked recovery.

Our best guess as to the cause of the issue is a change in the ICS kernel, regarding how it handles wipes, is triggering a latent EMMC firmware bug which then renders blocks of EMMC unwritable.

We think the reason GB kernels don't exhibit the issue is they handle wipes differently and thus don't trigger the latent EMMC firmware bug.

The EMMC firmware is basically the internal controller for the EMMC and not something that can be updated with a flash.

There may be some versions of the EMMC more susceptible to this problem and the bug could lie in sections of the EMMC firmware designed to make sure flashes don't keep flashing the same blocks to reduce "wear".

This could explain the behavior where you do the same operation 4 times with no issue, then on the 5th it bricks.
[Samsung Epic 4G Touch] RainMotorsports:
I am familiar with wear leveling as well as the basics on the interface controller. I would actually be curious to see if there is anything in the area of storage the controller has access to internally that is not presented outside of vendor specific queries and commands. I assume they are able to see and write that area with jtag so there is probably nothing there. But would be interesting to see a dump before and after brick on the same phone. That is unless the combined package prevents direct access to the flash itself, unlike what I am used to.

I haven't bothered keeping up because I know you guys are on it and there is nothing I can do. I don't even have the time in the day. Keep it up guys, much better than anything I can do.
[Samsung Epic 4G Touch] sfhub:
repack done uploading now.
[Samsung Epic 4G Touch] tpapa:
I have been flashing the NODATA versions of these leaks and all data settings seem preserved except for Juice Defender which I need to re-configure each time...is that normal?
[Samsung Epic 4G Touch] jeffek:
thanks sfhub . cant wait to get home

Sent from space shuttle gs-2
[Samsung Epic 4G Touch] Sprinkster:
well i just uplugged it via the usb cable, and followed up by trying to start, and it gave me the firmwarte upgrade error encounter, and something about kies.. which i knew was bull****, i assumed it froze while doing the data reset, so i replugged it on that same screen with the error, and odin still recognized it and hit start, and it did it no problem :) reset, did the final touches and BAM, done :)

---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------

glad im not either! lol! i just did the ics update on my rooted acer iconia tablet so im glad to see this went through
[Samsung Epic 4G Touch] wraith404:
Wow, I'm going to have to remember that, I didn't know download mode could recover. I'm really curious what sfhub has to say... hint..
[Samsung Epic 4G Touch] kevmo1965:
done that 3-4 times with reboots on both devices before re-pairing the devices. Same result. Media will auto connect but not the phone profile. I've even disabled the media connection only to have it re-enabled when it re-connects.

How high is too high for Android O/S in the battery consumption? Is 40% too much? Seems like it to me.
[Samsung Epic 4G Touch] Sprinkster:
yea im proof right here, ive used odin before, and i guess you can recover :) i took it off the usb cable it was still in download mode with the bar still in the same spot, i took out the battery and tried to reset and it hit me with the error, reset again trying to go to download mode, same message, but still connected to odin and showed the blue bar on the bottom :) and it did it just fine
[Samsung Epic 4G Touch] sfhub:
You get the download mode error whenever ODIN opens the connection for the flash process but doesn't close it. It doesn't necessarily mean anything bad has happened, just that the last session didn't complete.

Just pull the battery and as you insert, press Power+VolDown. If you can get into ODIN DL mode (and you didn't flash an intl bootloader) you should be fine.

As an aside, 1 in 50 of my ODIN flashes, it'll get stuck on something for no apparent reason. factoryfs, data, or modem usually. It happens rarely, but when it does, your only choice is to press and hold the power button until it restarts or pull the battery. This will assure you of getting the failed download message because the flash session wasn't closed properly. It doesn't mean you are bricked (though if in addition to the hang, you had previously done wipe data/factory reset and triggered the EMMC /data lockup issue, then you would have a brick)
[Samsung Epic 4G Touch] fatboypup:
Comeon sfhub can we haz fe21?!
[Samsung Epic 4G Touch] wraith404:
As always, invaluable info. Thanks. I'd probably wet my pants if this happened to me before reading about it. I'd probably try the battery pull, but I'd be shaking the whole time.. but mostly for fear of my wife's reaction to me needing to pay for a new phone or TEP ;)
[Samsung Epic 4G Touch] scoobdubois:
Hello

Hello sfhub ...we all waiting for your gift get FE21 please ...
[Samsung Epic 4G Touch] darren.wlsn1:
is there any reason peeps are waiting for FE21 other than its new, not like theres any changes from leak to leak lately?
[Samsung Epic 4G Touch] neudof:
Fe21 release also = bug fixes on other roms like MIUI :-)
[Samsung Epic 4G Touch] ginjeet:
Kinda looking forward to anything past this latest. FE16 sucks battery hard on my device, went back to FE07 to wait and see.
[Samsung Epic 4G Touch] probowler2009:
Yes battery sucks on fe16. Well hopefully we will have something new tomorrow!
[Samsung Epic 4G Touch] avargas28:
I bought my E4GT used as I was using a nexus s 4g before. I didn't use much of GB but I ended up doing the one click method and my battery life is terrible. I'm guessing this goes for everyone else too. I think the battery life on my nexus s was better. Oh well.
[Samsung Epic 4G Touch] kingsway8605:
How did you find this thread lol. Flash ff18, this is old.
[Samsung Epic 4G Touch] avargas28:
I couldn't do the ICS OTA update on my phone because it was stuck on 2.3.4. Someone here just told me to use this one click thing. Im not familiar with this rooting stuff.

Please prove me wrong, please. My battery life on my phone is terrible. I have no reason to troll. Look at my post history and you'll see the trouble I went through with this phone.
[Samsung Epic 4G Touch] metayoshi:
Lol. Kingsway meant to say to use the FF18 one click. This is FE16, a month and 2 days older, hence why they are calling you a troll. Please look for sfhub's FF18 one click thread and let this thread die. Hope I helped, (if you really aren't a troll).
[Samsung Epic 4G Touch] avargas28:
Ooops, that's the one I used:

http://xdaforums.com/showthread.php?t=1765953&page=45
[Samsung Epic 4G Touch] Omar04:
I think so... also it happens with some other apps.. ie. Speedtest and others need to clear cache to function properly.
[Samsung Epic 4G Touch] sfhub:
Does Juice Defender store any data or install itself in /system? If so, that would explain it.
[Samsung Epic 4G Touch] CyberpodS2:
I have been flashing Agat63's rom over itself for like the last 4 builds and I have to do the setup every time too...

---------- Post added at 08:06 AM ---------- Previous post was at 07:59 AM ----------

Exactly... Using mobile Odin to drop to el26+cwm recovery is no harder than using quick boot. Since the roms install a new kernel anyway it seems silly to do anything else. Especially considering the possible outcome of using an ICS recovery :D
[Samsung Epic 4G Touch] lickarock:
sfhub... you're like a machine man. Flashing now.
[Samsung Epic 4G Touch] jamesey:
I steer clear of factory reset and just flash caulks format all
[Samsung Epic 4G Touch] robpet2:
wow this was fast to get the FE16 up..

quick question, would it be okay to use the no data version to flash directly over BluKuban FE10 rom ??
[Samsung Epic 4G Touch] sfhub:
My suggestion is to use the Full version.

I wouldn't use NoData over any de-odexed/custom ROM. Nothing "really bad" will happen, but you'll probably get some random FCs or might get a boot loop. Both are easily recovered from as long as you can get into ODIN DL mode.

NoData works well when you are going stock to stock.
[Samsung Epic 4G Touch] kc_exactly:
Thanks again. This just seems like the most convenient way to flash the rom. No fuss, no muss. And it makes it a snap for doing multiple devices.
[Samsung Epic 4G Touch] robpet2:
thanks for the tip..

main thing is i have to delete the dumb camera sounds after the phone boots up. I hate the camera sounds
[Samsung Epic 4G Touch] vrundmc:
Just installed...quadrant score of 3915. 4G is super fast.
[Samsung Epic 4G Touch] CyberpodS2:
I have been using the camera out of Calkulin's E4GT 2 v1.5

It is deodexed so ya gotta delete the Camera.odex for it to run, but I have not had any issues with it on Agat63's last few couple odex builds.

Just a thought.

EDIT: Or do your mods on this build and then take that Camera.apk and put in an update.zip file so you can just flash it right after the new roms?
[Samsung Epic 4G Touch] Compusmurf:
Yes, it's normal. JD has a backup and restore settings. Just use it, works well and quickly.
[Samsung Epic 4G Touch] tpapa:
Ah. Great point. Should have noticed that. Thanks for the tip!
[Samsung Epic 4G Touch] someguyatx:
Thanks for this nodata worked for from 10 to 16. Need to rollbakc my kernel though so I can flahs inverted gapps. Messed up my calendar.
[Samsung Epic 4G Touch] steindog99:
My Android OS is extremely high and battery is sucking...what's a good app to see what's using it?
[Samsung Epic 4G Touch] DevalB:
Anyone have an issue with the phone starting to lag with this build?

I have been doing a NODATA since FE07, and the phone has progressively gotten worse. I took some time off to switch to my EVO 3D to use the leaked ICS build, and it was smooth as butter. I came back to this phone with the new leak and it lagged. I had to power cycle it already twice.

Is it just me? lol
[Samsung Epic 4G Touch] blackinjun:
same here
[Samsung Epic 4G Touch] someguyatx:
Its still too early to say anything is eating battery life but here is my general get better battery life guide. Its a work in progress

Use apps like system panel lite, better battery stats and android task manager to see whats running and kill it. Don't let things like google plus, google drive, picasa, facebook, twitter autosync or don't even install those apps to begin with unless you need them then when you are done remove the app and reinstall it later.

Switch launchers to ics

Set my plain black wallpaper (attached) to background and lockscreen,

Sign out of google talk since I dont use it,

Install an app removal tool or manually get rid of

-digitalclock

-mediahub

-samsungwidget_news

-samsungwidget_programmonitor

-samsungwidget_stockclock

-samsungwidget_weatherclock

-socialhub

-socialhubwidget

-Sprintzone

-Other sprint bloatware nova, id, radio etc... can be uninstalled from applications screen

I am using agats ics theme (hopefully on fe16), beautiful widgets for my homescreen clock and weather, inverted gapps for calendar, gmail, and tapatalk and other apps are set to dark settings where available. I toggle on and off wifi, bluetooth, 4g etc when needed and off when I'm done, 3g stays on all the time unless I have horrible signal/roaming.
[Samsung Epic 4G Touch] tmeader:
You can always try the app "SystemPanel" from the Play Store. It will take a while to gather useful stats though. Gives a great detailed breakdown after it gets going.
[Samsung Epic 4G Touch] rokair:
Just an early report on older issues..

LED Notifications. Continue to work perfectly when the phone is NOT charging but continue to be ignored when the phone is charging. That includes both the the LED will not flash RED for items such as GMail and Voice Notifications and that it will not allow the custom colors from items such as Handcent SMS and TouchDown (Email application) to override the charging color. Obviously not a show stopper but these did all work on the GB ROM and were nice additions.

So far the WiFi seems more stable but really it is too early to tell for sure. Basically, I notice (as I have seen others report in previous versions) that the connection (especially at work) will drop from time to time only to be picked back up several seconds later. I have not seen this happen since I installed FE16 but again it has only been about an hour (LOL).

I cannot comment on the Bluetooth Voice Activation issue as this is not a feature that I personally use.

Otherwise I am pretty happy with this build (as well as the last couple)...with Sprint's network it is hard to judge some things from one day to the next but it so far seems that the FE16 Modem is more stable today than the FE14 Modem was yesterday but obviously that should be taken with a grain of salt.

Thanks,

Rokair
[Samsung Epic 4G Touch] MrHot2000:
wow

Wow two flashes in a single day must be my lucky day hoping it was worth it though
[Samsung Epic 4G Touch] garwynn:
OK, something has changed - stuck in bootloop after putting on FE16 and suspect it's the wi-fi config that's doing it. Had to pull the battery to get it to stop, might try putting FD26 (last that I have at work) and delete the config just so I can get past it for now.

*Edit*

Huh, pulled the battery and MicroSD card and it booted. Restart and goes right back into bootloop. At least this should give me a point where I can turn off the wi-fi and investigate further.
[Samsung Epic 4G Touch] bigpeng:
Wifi didn't work for me neither with a FE14 kernel repacked with Rogue that I got from someone too, last one that worked for me was FE10 with Rogue repack. But never got bootloops with FE14, wifi just wouldn't turn on, everything else worked.
[Samsung Epic 4G Touch] robpet2:
so far this rom is running flawless. Odin full version with data wipe, started to run slwo at first, and then it went into 6th gear.. gonna test this out today and see how it is. its taking a while to go from 99% to 100%, been there for about an hour, but thats a good sign that its making sure the battery is 100
[Samsung Epic 4G Touch] someguyatx:
I noticed the same with LED notification. I use the blink app to make the led flash blue when I get a message (so I can see it) and the notifications do not flash with blink on or off.

Wifi appears to connect faster now at work for me
[Samsung Epic 4G Touch] tmeader:
With this build (FE16) I'm getting the issue of the Data Roaming triangle repeatedly popping up all day long again while here at work (in the notification bar). I know that the late FD builds had this issue, but it seemed to have been fixed in all the FE builds until this one. Anyone else seeing this?
[Samsung Epic 4G Touch] reddragon72:
Turn off roaming then reboot and turn it back on and it should fix this issue. I had that issue on a few builds and that always fixed it. And if it still comes back just kill data roaming.
[Samsung Epic 4G Touch] garwynn:
Wi-Fi update: Found the cause and removed the line. Also updated the following thread with that information:

http://xdaforums.com/showthread.php?t=1569348

Update 11:55 am CDT:

New issue - screen fritzed out but responded by adb. Rebooted, went back into bootloop until I could disable wi-fi. Guess it's not fixed after all.
[Samsung Epic 4G Touch] qbking77:
I've got a review video uploading!
[Samsung Epic 4G Touch] losinc:
exchange

is it me or is exchange broken?
[Samsung Epic 4G Touch] robpet2:
Wifi is working fine for me. Didn't have any issues with it on fe16. I did the full Odin with data wipe.
[Samsung Epic 4G Touch] DevalB:
Works fine for me, came from FE10 no wipe
[Samsung Epic 4G Touch] umrico:
DITTO!
[Samsung Epic 4G Touch] bhsvault:
Did we see a performance boost in this build?
[Samsung Epic 4G Touch] sfhub:
The recent ones appear to lag a little initially after install, but after it settles down and you've done a couple of reboots, they behave normally again. I haven't looked at the logs, but I'm guessing something, probably some maintenance work, gets triggered on initial install.
[Samsung Epic 4G Touch] umrico:
OK, I take it back. Email is failing now. On exchange it keeps locking up. Did a clear cache and trying a reboot now...
[Samsung Epic 4G Touch] garwynn:
AnyConnect VPN client won't start properly either. I've done a few NODATA updates and I want to rule out lingering data being the problem, so I'm downloading the full package and will try that one. Maybe that will fix the problem...
[Samsung Epic 4G Touch] weboide:
So far, to me the scrolling seems much better than previous leaks.
[Samsung Epic 4G Touch] CyberpodS2:
+1 albeit on Agat63's version of FE16, this is tight!
[Samsung Epic 4G Touch] someguyatx:
Anybody got a theme for this version yet? From the comments its probably not the release but i love that blue ics look.
[Samsung Epic 4G Touch] grncherry:
VAD (Voice Activated Dialing) Update

After hours of testing I find VAD works as designed when screen is active. When phone goes into standby (screen off) or sleep mode, the bluetooth headset call button will indeed wake up the phone. This can only be accomplished by a long press on the call button, the phone wakes up and dials the last number called. This is impractical if you don't want to call the last number dialed. There is no prompt for "What do you want to do" there are no other alternatives. I have found no solution to this behavior.

Also tried VAD on the new Galaxy Nexus (running official ICS) and hands-free VAD works without a hitch. Everything functions as it should on that device.

All of these trials were done with several bluetooth headsets (Ver.2 and 3). My conclusion is that it indeed is a problem with the ICS leaks for this particular phone.This was tried with the full wipe version. :mad:
[Samsung Epic 4G Touch] ojones838:
Anytime I use gestures like swipe down or swipe across I get a blue trail going across the screen like a mouse trail. I can get rid of it by 'tapping' the screen anywhere. Anyone seeing this. Has only happened on this (FE16) Kernel. When I flashed this combo with Odin I didn't wipe data first. Did I just crater myself? :(
[Samsung Epic 4G Touch] CyberpodS2:
Not a theme, but this ROM is rock solid and has a nice theme...

http://xdaforums.com/showthread.php?t=1658622
[Samsung Epic 4G Touch] RainMotorsports:
Its a developer option go in there and turn it off
[Samsung Epic 4G Touch] sfhub:
You might have tapped "Show pointer location" in Developer options by accident.
[Samsung Epic 4G Touch] qbking77:
Got a review video up:

http://www.youtube.com/watch?v=FBdyT609t4A
[Samsung Epic 4G Touch] sfhub:
Thanks for your continued testing of this problem. I've added your latest comments to the 3rd post. Hopefully Samsung will pick it up and fix it.
[Samsung Epic 4G Touch] sfhub:
Added to video section of first post.
[Samsung Epic 4G Touch] robbyr:
With the last two builds, I have had the issue with Exchange where it will not sync unless I force it. Push or scheduled syncs only work a couple of times after reboot and then just fail.

It's all good though. I use Touchdown anyway! :D
[Samsung Epic 4G Touch] Omar04:
Do a factory reset on Recovery and all problems will go away. from time to time I get caught on boot loops after flashing a new leak and Factory reset resolve that.
[Samsung Epic 4G Touch] garwynn:
Just an FYI - I found I had quite a few problems this time doing the nodata update from FE10 to FE16. So I downloaded and ran the full package and all of the issues - including the Wi-Fi reboot loop - have gone away. Not sure what caused it, but if others are having problems you may want to consider this option as well.
[Samsung Epic 4G Touch] Omar04:
Yes we did.

This build is buttery smooth for me at the moment. at first was laggy but then *edited* (to not cause confusion or misunderstanding), do a factory reset and voila all fine and buttery smooth. also quadrant hit for first time the 4000 mark.
[Samsung Epic 4G Touch] sfhub:
Root wouldn't be causing the lagginess. The last few releases, I want to say since 4.0.4, but not sure when it started, after the initial install it is a little laggy, then after you let it sit a little and do a couple of reboots it settles down and behaves normal.
[Samsung Epic 4G Touch] kurtosterhage:
If you go to Settings > Call Settings > Voicemail Settings you get a black screen and an error saying "Unfortunately, the process com.android.phone has stopped," and when I try to set a 960x800 image as the wallpaper it is zoomed in, instead of the full size.
[Samsung Epic 4G Touch] wraith404:
Are you SURE you don't have the voicemail app disabled? I use google voice and dsable the voicemail app, and get this.. BUT if I re-enable the voicemail app, performing this action works just fine.

---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------

Hey Agate, any chance you would pull your ICS theme for FE16? I really hate this boring

TW color scheme ;)
[Samsung Epic 4G Touch] JohnCorleone:
I can confirm this as well. When I was getting phone to initiate from screen off it was by long pressing. It went straight to dialing previous number and also seemed to make my music player start playing music at the same time. I will double check it on this build tonight but it has already been confirmed thanks to the thorough testing by grncherry

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] kurtosterhage:
I'm using Google Voice, so that was the issue. Never realized that it did that before. Thanks.
[Samsung Epic 4G Touch] Omar04:
I know root does not cause lagginess. I just was telling what I always do after flashing the leaks that was why I use (I don't like to root stock ). I will edit that part to not cause any confusion or misunderstanding. ;)
[Samsung Epic 4G Touch] JohnCorleone:
OK sfhub, it took me forever to catch this. The video is blurry and shaky with poor resolution (shot while moving from my NS4G) but here is the low signal random pop up issue. You will see it about 10 seconds in. It has been around for me since LOS testing on EG30. It was never an issue in California unless I made it happen by going to a dead spot but in NYC its pretty damn annoying!!! I will catch a logcat to see if you can spot the problem since it was on the Galaxy S Sensation and our Epic Touch...

http://db.tt/k0BZNM5x
[Samsung Epic 4G Touch] CyberpodS2:
I am only looking for an opinion here, but do you think that using the Odin packages would/could have the effect of resetting said counter?
[Samsung Epic 4G Touch] sfhub:
Using the full ODIN OneClick packages would allow the USB jig to reset the counters and Triangle Away works with the ICS kernels. Other than that, just flashing the ODIN OneClick packages by themselves will not affect the counter. If the ODIN package you flash has a kernel not signed by Samsung (none of my packages, except for 2 specially marked ones) then that will increment the flash count.
[Samsung Epic 4G Touch] CyberpodS2:
When I said counter I was referring to the flash four times fine and the fifth one bricks theory you had.
[Samsung Epic 4G Touch] corwin2k:
Any one else have email fc?