yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] tmeader:
Sorry, meant AutoRoot. But they're both basically "one click" to use as far as ease... heh.
[Samsung Epic 4G Touch] krylon360:
FWIW; the MTB/USB bug you mention isn't really a bug. It's how ICS operates. Sucks, I know, seeing as Linux HATES MTP; so I'm not real sure WHY Google even switched it.

This was 1st identified as how it's supposed to work when ICS rolled out to the NS December.
[Samsung Epic 4G Touch] leaderbuilder:
I'll be pointing many to those ;) Thanks QBking77 for the work.
[Samsung Epic 4G Touch] sfhub:
Samsung doesn't "have" to make it work exactly like Google releases it. I mean look at how many touchwiz changes there are. They aren't shy about not following the ICS blueprint exactly.

The earlier ICS builds at least had the USB Tools to allow someone to go back to USB Mass Storage mode.

I'm confident this will become a bigger issue when it hits the general masses than it is for people on XDA because on XDA people have been told how to work around it.

The reason I say this is because when they broke USB storage mode with the initial GB upgrade on LG Optimus S, lots of people were very upset. All they needed to do was install new drivers and it would have resolved their issue, yet it was still a major complaint. There were of course other issues with the update, like the phone wouldn't charge without the new drivers, and people couldn't stand the change from white status bar to dark status bar with hard to read notification icons.

There are some OSs which don't have MTP drivers builtin. There are some combinations where MTP is extremely slow when compared to mass storage mode.

Basically for some folks it will go like this, they usually take pictures and plug their phone into their computer and copy the pictures off the drive. Now they hear about this great ICS and install it. Well it looks very similar to GB, let me give it a whirl. During the course of the day, they take some pictures, get home, plug the phone in, expecting to copy the files off the phone. They get met with a USB not recognized (because of lack of drivers) or they get MTP mode, which is much slower than mass storage mode.

If one has been used to using USB Mass Storage and having their phone show up as a drive on their computer, it will be a shock when it no longer does that.

Anyway, if I were Samsung, who has to deal with the support issues for the phone, rather than Google who gets to put out whatever they deem appropriate, I would put back a method to enable Mass Storage mode. The functionality is there underneath the hoods.

Now I can see someone coming back and saying due to some DRM restrictions everything needs to go through an MTP "view" of the phone, and that might be more convincing as to why they would force MTP, but it will still be very annoying. The only other reasonable argument that can be made for MTP is that you can access the filesystem on Android and from your PC at the same time and you don't need to do a media scan when unplugging from your PC, but the loss in performance simply is not worth it.

I know I am somewhat preaching to the choir here, so don't feel this reply is directed at you, but just to voice my opinion on the issue.

On GB it defaulted to MTP mode also, but when you enabled USB Debugging, it switch to Mass Storage by default. That would be enough to keep people happy I'm sure.

Once you make it so someone has to use a 3rd-party tool to enable a basic feature you were used to using before the upgrade, it rises to pet peeve status for many folks.
[Samsung Epic 4G Touch] krylon360:
oh I agree with you 100%. I hate MTP. I remember Google stating the made the MTP switch due to DRM related stuff. But still they could have left the damn option.
[Samsung Epic 4G Touch] cob11341:
So I've heard that there is no team behind this build anymore which makes little to no bug fixes! :)
[Samsung Epic 4G Touch] wp7chris:
KRYLON360

HEY I remember the days of the Samsung Vibrant, you made that phone amazing. You and team whiskey still devvin? are you gonna come make my galaxy s2 amazing now too? lol
[Samsung Epic 4G Touch] krylon360:
No longer with TeamWhiskey. Everyone kinda went their own way. Been doing my own thing for a while now. I've had the E4GT for a month now. Just waiting on Source to drop. Me and Sombionix are working on something though for the T989 and D710.

Also working on the Nook Color CM9/AOKP Development.
[Samsung Epic 4G Touch] lickarock:
Why is everyone so convinced ff02 is a final build?
[Samsung Epic 4G Touch] MoHoGalore:
I don't think people are convinced but listening to conjecture.

Sextape only posted what he was given about ff02 being a final candidate.

So, by definition of candidate, its just an option.
[Samsung Epic 4G Touch] daniel4653:
We have a honorable source saying it was final (sex tape) he gave us the first leak for our phones so I trust him
[Samsung Epic 4G Touch] MoHoGalore:
My references to my last post.. Final is such a definitive word.. but so is candidate..

http://xdaforums.com/showpost.php?p=27065505&postcount=7446

http://xdaforums.com/showpost.php?p=27065675&postcount=7448
[Samsung Epic 4G Touch] lickarock:
L710????? Is that a typo, or have you pulled off the impossible ?
[Samsung Epic 4G Touch] sfhub:
I am not sure if FF02 is THE final, but if the reports that the Samsung development team has moved on to the next project are true, this is probably pretty close to, if not, the final version unless Dan Hesse is going to start coding.
[Samsung Epic 4G Touch] MeWarning:
Hey sfhub have you had any luck with the modified kernels not installing or running some of the apps that need sdcard? Flashed Agat's FF02 and still have it happen where I loose a bunch of apps and can't even get them to install. Haven't tried installing after pulling the sdcard yet, was about to flash back and give that a whirl.
[Samsung Epic 4G Touch] wraith404:
IF the reports are true, I know one thing about Samsung from an old Blu-Ray player I have... when they move on, they close the door and don't look back. No matter what is still broken.
[Samsung Epic 4G Touch] leaderbuilder:
...unless Dan Hesse is going to start coding. made me chuckle. :)
[Samsung Epic 4G Touch] stevetrooper:
I did the upgrade to Chrome, now available on the Play Store, it is working smoothly so far.. Keeping my fingers crossed....
[Samsung Epic 4G Touch] sfhub:
I figured out why it is giving the errors (from the mount.txt you provided), basically because vold isn't mounting .android_secure on the internal sd, but I don't know why it isn't mounting. No obvious error message is saying what is wrong, but there might be some message that might initially seem unrelated that I'm overlooking.

The main issue holding me back is I get the same behavior on my phone, even with the stock kernel, so it is hard to do before/after testing when it does the same thing all the time for me.

I was looking through the vold source code right before I went out of town so I didn't make that much progress on that end before needing to leave. Right now I can't mess with my phone that much because it is my only phone while traveling.
[Samsung Epic 4G Touch] neodorian:
Very odd...I was running FE22 and just ODINed the FF02 NODATA. for some reason (even after I update PRL and profile) it would never get off roaming. Went and ODINed just the FF02 modem to make sure nothing screwy happened to the modem but no difference. ODINed the FE22 modem and it went back to working just fine. Not sure if it's something about my hardware or something that would be fixed with a full wipe. No time to re-setup my phone again so I'm gonna stick with this for now and see how it goes. With final likely to come out some time this month I don't see any point in me wiping everything and starting from scratch just now.

As always, thanks for the conveniently packaged leaks for us to play around with!
[Samsung Epic 4G Touch] MeWarning:
Ok cool, like I said they're all apps I don't really use much so it's basically just out of curiosity for me. If it helps any I've never had any problem with Calk's ICS ROMs. His has the modified kernels with Rogue recovery and tweaks. So whatever he does differently works.

---------- Post added at 06:06 PM ---------- Previous post was at 05:20 PM ----------

On a side note there's an update out now for Chrome Beta so we should hopefully see some improvement with that.

And yes Chrome does work now!!
[Samsung Epic 4G Touch] :
This version is much smoother than FE22. I like it, especially now that chrome is fixed.

Is there a way to donate to sfhub?
[Samsung Epic 4G Touch] wraith404:
You probably know all this, but.. I only get the same behavior on the stock kernel if I bounce back and forth. I find I can fix the stock kernel by unmounting and remounting the external SD, but stock works find freshly out of a new full Odin. When I flash a new custom recovery, it will still work even through a few reboots, UNTIL I boot INTO that recovery. From that point, my apps to SD is toast. I can work around as others point out, unmounting and installing internal, remounting... but of course that means no apps moved to SD. Flash back the stock, reboot, reboot, still broken. Unmount/remount, fixed so long as I stay stock... rinse, repeat. It's as steady and predictable as the moon.

I've just given up on keeping a custom recovery for now, I flash custom to do what I need, then flash back to stock. It's slightly inconvenient, but it works.
[Samsung Epic 4G Touch] mmark27:
After lots of testing.....

FF02 = FE21

Having a hard time with Bluetooth and roaming notification bug still present.
[Samsung Epic 4G Touch] edlee:
Does anyone else notice issues with ff02 modem, i have had loss of signal twice, and i had to turn on and off airplane mode for signal to come back. I am going back to fe22 modem.
[Samsung Epic 4G Touch] daniel4653:
FF02 for me is a lot smoother than 22.

Nope just had signal sporaticly lose signal bars then come back
[Samsung Epic 4G Touch] sfhub:
That is interesting, thanks for the info.

On my phone apps to SD work when I have an external SD installed.

The issue is when I don't have an external SD installed. I informally polled some people and it seems to be split what behavior is "proper". Some people can only install to SD when an external SD is installed and some people can install to SD even without external SD installed. I'm in the former category.
[Samsung Epic 4G Touch] ReFiLL:
It does not blink at all when plugged in...Charging or fully Charged.
[Samsung Epic 4G Touch] wraith404:
I'm in that boat as well. If I unmount, or reboot without the external SD in, I will get an error "Unable to move app. not enough storage space." if I try to move any app to SD. It's really odd, because it moves them to USB, not the external. I wonder if it has to do with the presence of the external_sd folder.

EDIT: They are actually installing to external, after careful examination of free space on both as I moved apps back to phone. I swear I used to have a populated .android_secure folder on sdcard (internal SD), but now it only exists on external_sd, and it seems empty. They must be hiding the contents better in ICS.
[Samsung Epic 4G Touch] edlee:
I hate to complain, but ff02 feels still too beta for it to be final.

But I think its a good idea to release it so the issues would be found when they are reported in larger numbers.
[Samsung Epic 4G Touch] neodorian:
That's what happened to me. Modems seem to be picky on different hardware so I just chalk this up to non-final release bugs and not playing nice with my particular handset. I flashed FE22 modem and it is better. Still not as good as when I was on FE21 but you know how these things go...sometimes you have to try a few to find one that works for your setup.

Edit: Just went back to FE21 and still pretty much zero signal at all in places where I used to get passable service. I may just suck it up and do a clean install instead of the NODATA version to see if that fixes things. Not sure why it would matter but clean wipes do sometimes fix things like this when all else fails. I just hate setting everything up again and I also don't really trust Titanium to always work properly.
[Samsung Epic 4G Touch] agat63:
Are you able to move apps to sd from "manage apps" menu option?

So far I was able to move every app that has activer "move to sd" button.

I'm on my rom/kernel combo.
[Samsung Epic 4G Touch] wraith404:
Nope, once I boot into a custom recovery all apps that are on SD are inaccessible and I cannot move anything to SD - from manage apps or other means such as TiB. Once I flash stock recovery back and unmount/remount my external SD everything is fine.

Perhaps your ROM isn't susceptible to this condition, or the right conditions haven't occurred. There might be some cases where apps are being moved to USB storage instead of the external SD. One thing I'm going to try when I have some time, is an external is not present after a format of USB and full Odin. Then moving apps to SD should work and move to USB (hopefully). Once some are there, I'm curious what will happen when I reintroduce the external SD.
[Samsung Epic 4G Touch] RayTrue04:
I just installed the no data and I'm thinking about doing a hard reset. What's the best way to go about it thru recovery or would it be the same as going thru the settings menu?
[Samsung Epic 4G Touch] Esoteric68:
To be completely safe, I one-click back to EL29, install cwm through autoroot, do my data wipe/factory reset and then re-install whichever ROM I want to use.
[Samsung Epic 4G Touch] mmark27:
I've noticed that I'll go into signal loss / LOS (circle with the slash) more frequently with FF02 [more frequently meaning like 3 times since flashing FF02 -> once or twice with FE22 over the week I used it], however it does regain the signal on its own and does not require a power cycle.

Whatever they've done in the last couple leaks, they need to make the roaming switch a little less sensitive, bump that dbM up so roam kicks in a little sooner. I know there's strong VZW signals all around me, even when Sprint is extremely weak. The software needs to tell it to jump on that signal so we can make calls.

Is it possible to give these radios more power? I'd take the battery loss for the gain in signals anyday.

I am on the reset user data version of FF02
[Samsung Epic 4G Touch] wraith404:
Just do the full odin. It will be the simplest and fastest way. Stay away from factory reset in recovery and settings.

---------- Post added at 02:05 PM ---------- Previous post was at 02:03 PM ----------

Try updating PRL and Profile (Settings/System Updates) then reboot before doing anything drastic.
[Samsung Epic 4G Touch] neodorian:
Sorry, that's what I meant. I updated PRL and profile. It failed a few times but eventually it went through. Still don't get anything but roaming (if that) so yeah...I probably screwed something up by flashing the NODATA updates a few times in a row. Time to do the full ODIN and set all my crap back up again...don't want to be without a working phone since I'm heading out of town for the weekend after work.
[Samsung Epic 4G Touch] Omar04:
Its not you only I'm on roaming since yesterday too. I flashed back to EL29 and everything is okay Updated Preferred Roaming List and Profile flash to FF02 and bam back to Roaming. Also did ##72786# + Master Security Lock no dice.

---------- Post added at 02:21 PM ---------- Previous post was at 02:18 PM ----------

Don't do that! You'll possibly be visited by the ICS demons and end with a fancy paperweight.

Use the sfhub "SPH-D710.ODIN_WIPE_CACHE_DATA.exe" tool to do Factory Reset.
[Samsung Epic 4G Touch] RayTrue04:
Ugh that's a lot of work. I was trying to avoid a computer. Guess I'll wait till I get home. My phone has been acting strange for a while now b4 I even jumped to ics. Was trying to avoid a reset but I think its time...
[Samsung Epic 4G Touch] Omar04:
Use the sfhub "SPH-D710.ODIN_WIPE_CACHE_DATA.exe" tool to do Factory Reset on the ICS Leaks.;)
[Samsung Epic 4G Touch] wraith404:
One more suggestion, from sfhubs OP for this thread:

Try performing the reset, update PRL and Profile (again) and reboot. It should all re-register clean OTA via your IMIE. If that doesn't do it, next step perform the ODIN full data.

If you happen to have customized your slot index, this will reset that too. You'll have to go back to QPST and do that deal again.
[Samsung Epic 4G Touch] mmark27:
Sorry, forgot to mention, I already do this often as part of the first pass troubleshooting before coming here and posting anything.
[Samsung Epic 4G Touch] sfhub:
If you need to wipe data/factory reset in a safe manner, use the ODIN wipe tool posted earlier or use a known safe recovery like agat's repack.

The stock recovery from FF02 is unchanged from the previous few releases so it is susceptible to the EMMC superbrick bug, however, and I say big *IF* they put a fix/workaround in the kernel MMC driver then it would be safe because the kernel fix/workaround is at a lower level.

If someone would like to volunteer to test various scenarios that would really help everyone else avoid this inconvenience please let me know. I only need one volunteer intially. You really should be able to deal with a bricked phone (meaning you can get it replaced relatively easily), though at this point I believe all the operations being tested will be safe, there is always the chance the code analysis missed something.

I have a "safe" CM9 install and can put together a "safe" AOKP for people to try. Also agat's FF02 repack is confirmed safe for

1) wipe data/factory reset

2) nandroid restores (nandroid backups are always safe)

However the ROM installs "safety" status are dependent on a helper app included with the ROM install and the functions used by the install script, rather than the Recovery being safe. (I say this with a qualification, if they patched the kernel MMC driver as above, then the ROM installs will be safe regardless as long as the kernel is "safe")
[Samsung Epic 4G Touch] blackinjun:
I wonder if it could have to do with the size of the sd card or how it was formatted...

I am seeing the same thing except I now see a new directory/file on my external_SD called system data for 1343MB. The problem is I can only see this file using the program disk usage (which by the way is great for finding large files)
[Samsung Epic 4G Touch] wraith404:
I use root explorer, es explorer and storage analyser, and don't see that folder in any, so perhaps I'll give disk usage a whirl. I'm still very curious at what can force the OS to use USB vs card storage, and what is pissing it off for card storage with custom kernels. It's smells a lot like some DRM thing. I know a lot of my app data that uses SD goes to USB with no choice (like google music pinned music).. they are making if very hard to manage storage and make use of external SD cards. Hmm.. maybe I'm starting to see why some new phone models aren't even bothering with an SD slot... and I'm not liking it. At least I can still point the camera at the card DCIM folder.
[Samsung Epic 4G Touch] RayTrue04:
I wiped from the menu setting and phones fine. Won't be home till Sunday so I took the risk. There's a Sprint store a few blocks away where I'm at so I didn't care if I bricked. I moved all my internal memory to the sd card just to be safe, now i just need to move some things back to the way i had it since I formatted USB with the reset. Is that bug only from resetting from recovery? I'm a lil tempted to try and see if I brick lol
[Samsung Epic 4G Touch] Omar04:
Can hit you from both Recovery and Privacy menu. Go ahead try it ten more times to see if you really don't care. BTW before latest 3 leaks I was always performing factory reset in every leak with no break too. LOL but then When I realize that you can break also from privacy menu don't want to test my luck anymore. :D
[Samsung Epic 4G Touch] sfhub:
BTW Test Plan was posted here:

http://xdaforums.com/showthread.php?p=27124691#post27124691

Esoteric68 ran through it and more.

6 flashes of CM9a5, 3 flashes of AOKP-37, 3 wipe data/factory restores, 3 nandroid restores, 1 mostly stock FF02 flash. All successful.

This is using Agat/chris41g's FF02 CWM repack.

I think we have a good handle on things now. If you want to go through the test plan, be my guest. It would be good to confirm she doesn't have a special Super Phone immune to bricks.

ONLY flash the versions listed in the download section of the test plan.
[Samsung Epic 4G Touch] dgn_sandibalz:
I noticed after flashing ff02 i noticed phone was running about 120 degrees and battery life was non existent. I flashed back to fe21 and problems solved.
[Samsung Epic 4G Touch] weboide:
This rom feels like a step-backward to FE16 or around that. UI can be slow sometimes, apps freeze or take some time to close... I didn't see anything like that in FE22.
[Samsung Epic 4G Touch] locoboi187:
Wow first time feeling lag and lock ups. Back to CM9
[Samsung Epic 4G Touch] tstretch:
Does the Internal SDcard get wiped also?

Hello all. I've always done the No-Data option here but am considering a the Full Data wipe version.. But does all the data I have stored on the 16GB of the Internal SD card get wiped too? Not just the phone memory?

And is it the same with using sfhub's wipe tool? (SPH-D710.ODIN_WIPE_CACHE_DATA.exe)

And what about Caulkin's Format Tool - same there too?
[Samsung Epic 4G Touch] sfhub:
Internal SD is untouched by Full Data. The Full Data version clears out /cache and /data in addition to flashing the modem, kernel, and ROM.

WIPE_CACHE_DATA will *only* clear out /cache and /data. That is what I would suggest in your case. It basically does the actions that were missing from the NoData flash when compared to the Full flash.

Format All will format the ROM (/system), DATA (/data), and CACHE (/cache). There is a modified Format All which just does /data and /cache You need to have installed a custom recovery to run these (not mentioning it as an issue, just as a prerequisite)
[Samsung Epic 4G Touch] quazimodem:
I got 3511 on my run.
[Samsung Epic 4G Touch] tstretch:
Thanks so much! And a customer recovery such as CWM - that I installed using your Autoroot option - correct?
[Samsung Epic 4G Touch] sfhub:
Yes, I would suggest FF02+CWM-agat as that is what we are testing on the EMMC lockup/superbrick thread. So far the results look good, multiple wipe data/factory resets and nandroid restores without issue.

I should warn you in advance that some people have reported issues with moving apps to SD with the repack. If you don't use that feature, probably won't affect you. If it does affect you, try putting in an external SD card and it might workaround the issue.
[Samsung Epic 4G Touch] FitChicago:
I'd be thrilled if sometime might help:

I've been the FF02 full restore which I installed using the One-Click self-extractor(SPH-D710.FF02_CL663858_ROOTED-oc-sfx.exe).

It's been running great and no installation issues.

However, when I've attempted to install a different ROM, every attempt ends in abortion.

Here's what I've done:

- Flashed Stock el 26 cwm kernel via mobile Odin

- Booted into CWM

- Wiped: Data/Factory Reset, Cache, Dalvik.

- Attempted to flash the following ROMs: CM9, AOKP, Mijjz Goodness.

- Every attempt resulted in:

- Asset failed" followed by some code and then "installation aborted"

I've searched for a solution unsuccessfully, any thoughts?

Thank you so much for your help!

Sent from my Samsung Galaxy S II
[Samsung Epic 4G Touch] sfhub:
Could you give the first few words of the assert? Is about ro.product / ro.build and status 7 error?

Try flashing Calk's format_all (at the bottom of the following post) before you flash your ROM:

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