yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] garwynn:
Have seen this for many builds now - thought it was the "Download All Files" causing. Maybe not...?

And FYI - some might not be happy with this - but I'm hoping Sprint cancels OTA until the eMMC bug is addressed. It's serious enough that while people want OTA it should wait.
[Samsung Epic 4G Touch] metayoshi:
I actually agree with you. While I'm happy with staying on FE07 (which, in my opinion, was the most stable they got so far), I just hope they fix that major issue before releasing OTA.
[Samsung Epic 4G Touch] jamesey:
Yes, same here on fe10
[Samsung Epic 4G Touch] jamesey:
Hmm... Even a slow person can see the brightness bug. Just uncheck auto and within a few hours it will go back on auto. Some of the other bugs need closer attention.
[Samsung Epic 4G Touch] bonniedarby:
Yes. I cancelled downloads on FE10, FE14, and FE16 and all of them gave me force closes.
[Samsung Epic 4G Touch] jamesey:
I suppose it's smarter to get a sgs3 with quite similar hardware to what I have? No thx I'd rather wait a couple of more months and get the phone that will lead the next generation of Android phones.
[Samsung Epic 4G Touch] steindog99:
I was getting FCs with Email.apk on FE16, so I just did a factory reset from within and now everything runs great and my battery life is pretty damn good. I also just tried canceling a download and didn't get an FC. It paused for a second, and I thought it was about to, but then it just went back to normal...

I know none of us like doing it, but maybe try a factory reset from within the ROM...
[Samsung Epic 4G Touch] Esoteric68:
Tabula Rasa is my motto. Even though it means a little bit of work re-installing apps/settings/accounts, etc I often do a full wipe and reset before installing a new build or ROM and I very rarely experience any of the bugs people list. I've set up/reformatted/changed enough PCs in my life to know it's always best to start with a clean slate.
[Samsung Epic 4G Touch] thirdcoastraised:
Never on Auto brightness, and my screen stays the same, but thanks for the childish manner of speaking. It's been well stated numerous times that different phones experience different things relating to bugs and such, hence the reason for multiple testers before ota, didn't say it didn't exist, merely stated that I have only experienced the one bug mentioned concerning gallery...:beer: cheers to ya patna!

Sent using my Epic(ly) AMAZING SPH-D710 on the sometimes network Rocking Blu Kuban 1.0.3.3
[Samsung Epic 4G Touch] graffix31:
I'm not on a stock ROM using the blue kuban but have never one had auto brightness turn back on on me. Always use the status bar slide to adjust. Been running ics for weeks now with various build.
[Samsung Epic 4G Touch] thirdcoastraised:
Maybe you're just "too slow" of a person to catch it...just sayin...lol!

Sent using my Epic(ly) AMAZING SPH-D710 on the sometimes network Rocking Blu Kuban 1.0.3.3
[Samsung Epic 4G Touch] thirdcoastraised:
Yes, cause the current Nexus devices are so superior to the others right? The Gnex came packed with ICS and has already received patch updates, Nexus S 4G also has received 2 updates now, and spec wise, both phones are a step backwards from gs2, so it's totally logical to assume that the next "Google experience" nexus devices will "lead the next generation". Fact is the only benefit the Nexus phones come with is that they get to be the Guinea pigs to work out all the flaws so that much like now, when Jellybean is released to the REAL Super phones, it won't be as buggy as the smart phone nexus version

Sent using my Epic(ly) AMAZING SPH-D710 on the sometimes network Rocking Blu Kuban 1.0.3.3
[Samsung Epic 4G Touch] Esoteric68:
+1 to this

I've referenced this before, and I really should find the post to actually reference, but sfhub did a great write up not too long ago about this very thing and I've said it myself, you can have two items come off the very same assembly line that behave like two completely different devices.

People need to chill with the pissy attitude just because someone comments that they don't see a particular bug. Personally I agree with garwynn on the emmc bug needing to be fixed before they release OTA but that's the only real bug I think is worthy of holding up the release.

I've followed a pattern with people who constantly report minor bugs while everyone around them is experiencing almost flawless performance and that is most of those people refuse to do a complete wipe before installing.

I'm fond of Rujelus' attitude with his ROMs, and that is "if you don't do a complete wipe then I don't care if you have problems" (I'm paraphrasing but you get the gist lol)
[Samsung Epic 4G Touch] taylortr:
Try turning off auto brightness in the browser as well as settings. That works for me to keep it disabled. Had that problem at one point on og epic.
[Samsung Epic 4G Touch] thirdcoastraised:
+1, Esoteric, and Thanks as well. Like you, guess I am just used to the Rujelus attitude of if you didn't flash completely clean, then expect the same bugs to keep bugging you!

The emmc bug most definitely needs to be fixed prior to OTA, but if I understood the article posted last night, the code had been written and was in place already for testing, just wasn't currently available to us yet, but there's no way I could see Samsung letting something of that caliber go to Sprint as an official release. That sadly would be suicide on their part.

As for bugs "reappearing" in builds 3-4 builds later and on different versions of ICS all together, I have to say, most likely you're right Esoteric, either they didn't follow the OP directions when they flashed and do a complete wipe prior, whether it be that time or any previous time since that bug first appeared, or, again, they didn't follow directions and they restored data from a different ROM, or in some cases even a different setup altogether such as AOSP or AOKP data being restored on Blu Kuban which, again restating what sfhub and numerous others have stated previously, will not only restore bugs that weren't there prior to that action, but also increase the risk of a hard brick by about 125%!

Long story short, if you are a ROM bouncer, then either stop downloading so many apps, or, each time you flash a new ROM, be prepared to start over again with whatever apps you have, or risk the brick. Seriously, if you don't want to wipe all every time, either find a ROM and stay put, or quit flashing altogether until the OTA comes out...
[Samsung Epic 4G Touch] someguyatx:
The funny thing is that the general public expects a flawless transition and upgrade. Whether Joe sixpack has 5 apps or 500 and regardless of the build date and revision of the phone the ideal experience would be everything working just like before with new features added. So while it does muddy the waters to keep data its what really happens with the ota. People like us can restore their phone from scratch in 20 minutes but it would take a week for everyone else. My guess is an early june ota release, pulling this info straight from my arse.
[Samsung Epic 4G Touch] thirdcoastraised:
+1 and lmmfao! I'm thinking within the next couple of weeks, which would put us in early June, but again, who really knows? Testing continues tonight, now going into hours 36-48 depending on tester, which is longer than any other tests have run, so we are definitely closer, and no, it is not fe16 that's being tested, just a side note there, so, we'll see what I'm able to learn tomorrow, for now, it's off to sit and watch monitors for a few hours, oh, and watch for that Blu Kuban 1.0.3.4 release....lol

Sent using my Epic(ly) AMAZING SPH-D710 on the sometimes network Rocking Blu Kuban 1.0.3.3
[Samsung Epic 4G Touch] Esoteric68:
+1000! lol

And excellent point about people wanting flawless. We've discussed it before and people tend to have short memories about patches and updates being released to tidy up the lingering minor bugs on previous OTAs.

Frankly I'm jazzed by all the releases, even if their frequency has left me with the patience of a 4 year old. lol

To the people consistently dealing with ICS bugs I'd seriously suggest sitting tight on GB (watch out for the lingering bugs in that one) and let others try out the leaks and OTA before you jump over. And when you do jump, please do a complete wipe to get a better read on whether or not a bug is real or just related to a cluttered system.
[Samsung Epic 4G Touch] garwynn:
The article on XDA's news section just covers what we went over on the thread here and in the Note forum. Unconfirmed that Sprint knows and I would rather they know before going OTA than facing it after, which is what happened to the global Note.

I've got someone to call on Monday and explain what we found. Hopefully they will listen or Samsung will release the patch. At this point I just want to see it fixed for as many as possible as soon as possible. At least we have a good idea how to avoid it...
[Samsung Epic 4G Touch] probowler2009:
Ok the battery level sucks on this thing I just lost 13% just using Facebook! Now I know it can't be using that much battery to look at my news feed.
[Samsung Epic 4G Touch] slick4mitch:
^^ This right here is truth ... I just tried it and it does in fact turns your auto brightness on if you have it off, good find and for that sir you got my thanks! ;)
[Samsung Epic 4G Touch] revamper:
I'd say we still have a long wait for OTA. I've had nothing but bugs and random reboots with fresh installs. This update is going to be pushed to hundreds of thousands of phones. There's not much room for error. I'm completely content in the meantime with GB.
[Samsung Epic 4G Touch] hypersonicx:
I also was having crazy battery drains and this was coming from a fresh install everything wiped...

I just went back to GB. Good ole stable perfect GB...
[Samsung Epic 4G Touch] RainMotorsports:
Meh I had a 31 hour day on CM9 A4 yesterday following my day off. Normal for ICS on this phone with light usage tons of standby. But I have not been on a single build of anything for quite some time to experience it.

I swear other than the occasional build and one freak night of sleep I have never had better or worse battery life for a given situation between GB and ICS and stock or custom. 5 to 8 hours of Heavy, 8 to 14 of moderate, 21 to 31 of light/standby.
[Samsung Epic 4G Touch] jamesey:
I've installed every build. Once upgraded to 4.0.4 some old bugs definitely came back. I always do full wipe before testing. Why is it so hard to understand that an older ROM was used as a base? We also got some new bugs. FD26 was just about finished. I'd expect the same from 4.0.4 before ota is pushed. Bugs are here whether you choose to notice or not it's up to you.

I consider exchange fc and random reboots as major bugs.
[Samsung Epic 4G Touch] RainMotorsports:
Its called a regression of course. Now a "Force Close" is not a bug, its an event. So just because your are getting ANR's and FC's from an app on one build and it gets fixed and it comes back does not make it the same bug. But its possible to fix a bug and then move on to another fix that causes the same issue again.
[Samsung Epic 4G Touch] jamesey:
I wasn't referring to any of the fc as old bugs. Those are new ones. Like the profile fc or the cancel dl fc those are new.

People just get impatient for source. I've said many times 4.0.3 would never be official, but nobody wanted to listen. People thought we'd be the only Android device on that version lol. There was obviously a big reason other devices were delayed that version update. Yet we were going to get it hehe
[Samsung Epic 4G Touch] probowler2009:
I am now starting to see a better battery life. My question is when we flash these new builds, does it take the phone time to settle in?
[Samsung Epic 4G Touch] abusedcloth:
For sure, any ROM takes time to settle.

Im not sure what every one has been complaining about with this build. Very minor issues and great battery life. I saw someone commented Facebook drained the battery, Facebook will drain any battery, that app is terrible.
[Samsung Epic 4G Touch] metayoshi:
Ahh, I didn't realize the browser had its own brightness setting. Thanks for the heads up.
[Samsung Epic 4G Touch] TrayLunch:
My tablet runs on 4.0.3 just fine. So we wouldn't be the only "device."
[Samsung Epic 4G Touch] probowler2009:
So who thinks we will have a new building tomorrow?
[Samsung Epic 4G Touch] fatboypup:
Me
[Samsung Epic 4G Touch] jamesey:
Wise guy I meant phones ;)
[Samsung Epic 4G Touch] jamesey:
So true. I just add a bookmark widget to my home screen for Facebook.com
[Samsung Epic 4G Touch] winfan:
Any word about what's to come? How did testing go and was this Samsung or sprint testing? Should we expect a new rdf tomorrow?
[Samsung Epic 4G Touch] kc_exactly:
I think we are still in beta. They are testing and we are out of alpha.
[Samsung Epic 4G Touch] TrayLunch:
W3rd
[Samsung Epic 4G Touch] reddragon72:
Testing went good. Though my leak said they may do a build today he wont be getting anything till tomorrow. He won't know more until then.
[Samsung Epic 4G Touch] TrayLunch:
That's at least some progress being reported, and though I'm sure it won't satisfy those that are chomping at the bit for an ota release, I, for one, am glad to hear the news. All of these rapid fire releases have been a bit frustrating for me. Seems like I'm flashing to the latest update 2-3 times a week. Don't get me wrong, I'm happy to have them, but we all seem to be putting ourselves through self-inflicted hell just trying to stay on the latest and greatest. Hopefully, as it has been reported, the people working on the official release have their ear to the ground, and every major issue we find is addressed. If that is true, none of this has been in vein and that makes me happy to play even a minuscule supporting role in the grand scheme of things.
[Samsung Epic 4G Touch] DirkBelig:
How is grabbing unfinished software not meant for general use "the latest and greatest"? It's like eating raw cookie dough (not that it's a bad thing), then reaching into the oven several times during the baking process to scoop out half-baked (literally) mushy blobs, popping them in your mouth and complaining that your tongue got burned and your Bluetooth isn't connecting. It's not Sprint's or Samsung's fault that you're flashing 2-3 times per week and/or are having troubles. You aren't supposed to be using any of this stuff until they shove the OTA down to your phone like all the other civilians who think XDA refers to a former district attorney.
[Samsung Epic 4G Touch] scarmon25:
Lullz
[Samsung Epic 4G Touch] DevalB:
If this was Reddit, you'd get all the upvotes buddy...great post.
[Samsung Epic 4G Touch] TrayLunch:
To answer your first question: It's the latest build of ICS. Though it's still beta, how is it not the "latest and greatest" build of ICS?

As far as the rest:

Thank you for reiterating my point for me. We are basically free beta testers for Google/Android. We do all of this to ourselves. If you see what we're doing as complaining rather than reporting, that's your hang up. If no one "complains" about what they find, it won't get fixed. I don't see anyone pointing blame anywhere, and they shouldn't. Especially not at Samsung or Sprint... unless it's a bloatware problem.

Can't a person show appreciation for a progress report without someone getting butt-hurt over a difference of opinion on phrasing or terminology anymore? Lighten up a little.
[Samsung Epic 4G Touch] veritasaequita:
Lmao.....that sir, is an epic line! Definitely sig worthy!
[Samsung Epic 4G Touch] BluesRulez:
ok so this is my first post on the site.

I have been following this thread for a month now waiting for the ICS OTA update just like everyone else. But lately I have seen people getting angry over small things and bugs trying custom roms which is just annoying..

People who want to test out custom roms made their choice and people who decided to stay on 2.3.6 made theirs.. Why can't we all just chill out and let Sprint+Samsung work out the bugs?

Btw the noob video is awesome. :)
[Samsung Epic 4G Touch] Dchibro:
Lol! Epic post.
[Samsung Epic 4G Touch] scarmon25:
Agreed. You have two choices.

1: Ride the cutting edge of software and deal with some bugs and annoyances.

2: Stay on the current OEM released builds ( in this case Android 2.3.6 ) and have stability and minimal issues.

If you want to go with the first option then keep in mind.

Reporting/mentioning bugs in a " Didn't know if it had been mentioned but this and that doesn't seem to be working " kind of tone/text is kick ass.

Saying things like " This build sucks ass and it is horrible and my phone just slapped me in the face for flashing this ****, Samsung you suck and I want it Nao! " is generally never a good way to go about it.

Just throwing out my thoughts on it. #informative
[Samsung Epic 4G Touch] thirdcoastraised:
So, testing is 100% complete, bugs are minor, exchange email is reported but only on 5% of devices, therefore NOT A PRIORITY as far as fixing before OTA, because of the fact that you do not have to accept ota. With gs3 quickly approaching, there will likely be 1 final build prior to ota, and exchange will be addressed, however will likely be remedied in a patch update later, much like it was with the nexus s 4g.

Sent using my Epic(ly) AMAZING SPH-D710 on the sometimes network Rocking Blu Kuban 1.0.3.3
[Samsung Epic 4G Touch] donsh00tmesanta:
How are you certain?

What will be the ota build number
[Samsung Epic 4G Touch] brooksyx:
Lets hope your right :p
[Samsung Epic 4G Touch] master acehole:
i just hate how people are complaining we are getting the ota in time and they ***** when they find a small bug on a LEAKED rom and the fact that we are lucky to see so many leaks and see if there is progression or not so it is annoying that people will still complain some people like myself love the stability of gb and can wait for ota and sadly the people will never be calm ><
[Samsung Epic 4G Touch] Esoteric68:
You can please some of the people some of the time but you can't please all the people all the time.
[Samsung Epic 4G Touch] reddragon72:
That is essentially what I got from my contact. Tomorrow will be the next build and testing will go for 2 days. After that if no major bugs are found then OTA that build. So the OTA could be FE22 if all goes well. That's if we even see the build, the one from Friday was not published either.
[Samsung Epic 4G Touch] crzchn:
We are all assholes.
[Samsung Epic 4G Touch] winfan:
If FE22 is the OTA build, when would sprint look to release it? Any idea?
[Samsung Epic 4G Touch] garwynn:
@thirdcoastraised, @reddragon72,

Did either of your contacts happen to mention if they were made aware of the eMMC bug yet? And if so has it been patched? Still holding out that they might catch this before it goes OTA...
[Samsung Epic 4G Touch] ArgyleDX:
Wow. If this is true this is a pretty Epic fail for Samsung and Sprint. How are they going to prevent people who need EAS from updating, are they going to have a gigantic notice before you accept the OTA that says "HEY THIS BREAKS YOUR EMAIL DO NOT UPDATE"? (It should be noted that if you use the stock email client and put in a Hotmail address, it seems to automatically configure it as an EAS account, so everyone using Hotmail will have broken email if they update...)

IMHO FE16 is way too buggy to release as an OTA, but I have no insight into whatever Samsung and Sprint are about to do.
[Samsung Epic 4G Touch] ajonesma:
I'm really hoping the OTA comes out very soon!
[Samsung Epic 4G Touch] kasper19:
Screw the OTA.I just want source
[Samsung Epic 4G Touch] Esoteric68:
I could see another rdf dropping but I'd be shocked if we're at the OTA stage. Although stranger things have happened I suppose.
[Samsung Epic 4G Touch] winfan:
If you saw the post after this one (you quoted), you will see that FE16 will NOT be the OTA build that will be released. They have actually worked on an FE18 and now talks of a FE22 build which have not been published by Samsung/Sprint. I hope this clears up your confusion.
[Samsung Epic 4G Touch] ArgyleDX:
Right, post I was replying to is saying that the current builds being tested DO NOT fix the EAS issue which has been present since FE10 or so, all I am saying that preparing an OTA with this bug in it is surprising to me. He claims it only affects "5%" of devices but I see a lot of people commenting that Exchange email is broken for them and very few confirmations that it is working on current builds (which to be fair is par for the course, people don't post when stuff works, only when things break). The justification for releasing a broken OTA with "well, if you need Exchange email, don't update" rings hollow to me, because it sounds like a customer support nightmare - the average person is not following what is going on here, so how would they know they should avoid updating their phone if they need to receive email on it? (And when they update and their email stops working, what should the average person do - take it into the Sprint store so they can wipe their phone and put EL29 on it? The average person would be pissed at having to deal with that...)
[Samsung Epic 4G Touch] kc_exactly:
Sprint test for a week before they release an OTA. So, if it came tomorrow we wouldn't get the OTA sometime between this and next weekend.

BTW, people from Texas know their Samsung stuff. People from KC know their Sprint stuff. And people from Cupertino know how to control sheep. That is just a tidbit of trivia for you all.

Samsung:

http://g.co/maps/yyyw7

Sprint:

http://g.co/maps/mqqe4

Apple:

http://g.co/maps/hqrh6

Look at the maps if you don't believe me.
[Samsung Epic 4G Touch] animal7296:
Thank you for that info. It was extremely informative. :p
[Samsung Epic 4G Touch] donsh00tmesanta:
I think the 5% mentioned are here on xda remember not everyone who have one of these phones comes here thus noone else is affeged :p
[Samsung Epic 4G Touch] winfan:
Id agree it would be a CS nightmare and not good for business. I think the bigger question to ask is what was the test population? I would hope they picked a decent sample size for the test and then you will know the real business impact for them. "5%" could be a very small issue, but then again all of this could be fixed before the OTA in the next build which means you have nothing to worry about. At worst case, they will issue a maintenance update to fix it. An OTA is not supposed to be bug free, otherwise you would never get an official OTA release. This is why there are updates to phones / tablets.

KC - Thank you for the info. I thought they were further along than still testing for another week since they said they will test for 2 days. Then again wasn't sure if that was Sprint testing or Samsung testing. I am doubting it is Samsung testing. Just a feeling... what are your thoughts? Reddragon?
[Samsung Epic 4G Touch] kc_exactly:
I don't know if sprint is testing. I know Samsung was though.
[Samsung Epic 4G Touch] winfan:
Yes I was aware of this as well. I thought reddragon was mentioning it was Sprint who was testing? Not sure if I misread his posts or not?
[Samsung Epic 4G Touch] jamesey:
Fd26 was light years ahead of fe16. Bugs are plentiful. 4.0.4 build is still in it's infancy and I'd rather wait more builds until it's right.
[Samsung Epic 4G Touch] kc_exactly:
No one looked at the maps. :(
[Samsung Epic 4G Touch] Omar04:
I do look at the maps. But I wonder what we are supposed to see or notice? :confused:
[Samsung Epic 4G Touch] kc_exactly:
I think you have to do it from the desktop.
[Samsung Epic 4G Touch] andrewqueen:
I saw the last one was a guy flicking the Google van off
[Samsung Epic 4G Touch] ilostmypistons:
No wonder I couldn't figure out what the heck the secret choose was
[Samsung Epic 4G Touch] leaderbuilder:
Thats a 'double' funny.
[Samsung Epic 4G Touch] xCovErtWolFx757:
So just wondering. When is Google going to work on chrome beta because I haven't seen an update in ages and it still doesn't work
[Samsung Epic 4G Touch] JohnCorleone:
Hopefully someone posts a stock deodexed FE22.;):D

Sent from my SPH-D710 using Xparent Blue Tapatalk 2