yashsingh1/xdaforums huggingface dataset:
[Epic 4G General] Erica8123:
I did. Well I was an idiot and bricked my phone and was lucky enough to get it replaced without the $100 deposit (thank you Dustin). I planned on rooting and flashing asap until I literally was about to connect the usb cable into my pc. For now I am staying stock. I may Z4 it to get rid of some stock apps but I am taking a break from the ROM/Modem flashing and theming stuff. My new Epic is running WAY better now then my old one was on DK28. I mainly wanted flash 10 but once I got it I never used it. I thought it would be great for watching HULU in between class or when I take the bus to work but my battery life was only 4hrs and I never could fix it no matter what recommendation I tried. Now my battery lasts all day again. We will see what I do in another week or 2 though lol.
[Epic 4G General] shook187:
Did you try the "Truly Epic Rom" I was on the same boat as you, and was about to switch till I gave that ROM try....Its rocks!!! and its silky smooth!!
[Epic 4G General] youngpro83:
Yeah I hear ya!! Hopefully they will come out with the official froyo so I can actually have a decent phone with froyo that actually works without all the head aches.
[Epic 4G General] riceknight:
From what I've experienced, there really aren't any issues with DK28 that aren't already in 18. Every Rom I've tried recently (Quantum, Bonsai, Midnight) has been silky smooth and I haven't gotten any FCs, calling glitches or anything you've experienced.

I just think its odd that people blame all their problems on the build. Its understandable if everyone is having the same issues as you, but when you're the odd one out, doesn't that mean you're the one thats the problem?
[Epic 4G General] youngpro83:
Well when Im looking through the threads and Im reading the titles that people post who are experiencing the same issues as I am and many others on this site, then I would assume its the build and not just one particular person. Not to mention its a leak.....Its not even an official release so for you to sit here and claim that it is more STABLE than the STOCK BUILD or anywhere close, you sound like a fan/groupie of DK28 rather than a person who is speaking from knowledge. There are more people on this thread than me who have been experiencing more than a few issues with the "leaked" froyo. When dialing out and sometimes the call not going through or you can talk but cant hear is a KNOWN ISSUE with the "BUILD" that even the devs are curious about. Never had an issue like that on the stock BUILD. Anyways like I said F DK28. :cool:
[Epic 4G General] hazridi:
For me, Quantum 2.1 is more stable than the stock ever was. It's not fanboy speak, it's that we know what we're doing and it's pretty obvious that Froyo is much faster. Maybe Froyo doesn't work as well on older revisions of the Epic hardware, I know I got mine in December rather than when it was first released. But for me, it is much better than the crappy stock rom which is bloated with Sprint garbage.
[Epic 4G General] MedicStuder:
Do we all care about if someone flashes back. It seems like posts like this keep clutterng up the forums. It makes it really difficult to search. Who cares u went back to stock. Mod please delete thread.

Sent from my viperROM rooted ext4 epic 4g
[Epic 4G General] NYYFan325:
So what your telling me is that the pre-release version of a ROM is more buggy and less stable then a final product. Got ya.
[Epic 4G General] snowmanwithahat:
Get off his case. He's sharing his experience on DK28 vs DI18 in case some DI18 users were still on the fence as to whether or not they want to jump to a buggy 2.2.1 build. There's a lot of hate going around these forums and it's the response like what you just gave thats give people a poor outlook of our community.

Personally I've experienced both sides of the argument. I went with DK28 first and killed my gps, flashed back to DI18 and went with ACS for 3 weeks. Got sick of 2.1 and really wanted some 2.2 features back so I went with midNIGHT and a 2.3 theme.

Thanks for your thoughts OP, I share the same concerns but found some of the buggy issues of DK28 to outweigh the bugs and lack of features of DI18. I actually think its funny though because a buggy DK28 makes me want a real stable froyo build even more than being on eclair made me want a 2.2 update lol
[Epic 4G General] youngpro83:
Exactly! I have been flashing my phone since I had my Touch Pro so I know all about leaks and the benefits they bring to a hardcore phone user like myself. I enjoyed DK28 for sometime now and it seems like the more people do to it the more some things stop working. I just got to the point where I was just tired of constantly updating the ROM with the newer version because the dev "FIXED" another DK28 issue. I appreciate all of their hard work. I even donated to a few of them because they made me love my Epic again with all these new EXT4 and no journaling mods. My phone has never been so fast and snappy......But at the end of the day when I need to use my phone I dont need it to do a random reboot or even worse miss a call because the other person cant hear me which is a very common problem some users are having. Although now that I am back on the DI18.......Its hard to find all those cool mods that I have been so used to. lol. Decisions decisions.
[Epic 4G General] MedicStuder:
If he wanted to share his experience then he should have searched for one of the other threads that has already been started about this topic instead of starting yet another one.

Sent from my viperROM rooted ext4 epic 4g
[Epic 4G General] riceknight:
Way to get defensive without backing your claims. There are also much more than a few people who aren't experiencing the same problems you are. I've never even heard of the dial out bug nor experienced it in any flash. If you don't want to work to get a good beta experience, why are you even on XDA and flashing in the first place? I find that DK28 isn't perfect, but its still leaps and bounds better than stock.

You have problems? Try to get them fixed, reflash or ask some questions on the Q&A. Don't just blame it on the build. Basic rule of thumb? If majority don't have the same problem you're having, double check what you've done or reflash.
[Epic 4G General] juise:
These are Samsung builds so I don't thinks there's really a difference between a alpha/beta/RC and a final build! :D
[Epic 4G General] NYYFan325:
Riiiiiiiiiiiight

To use the OS "windows" as an analogy for you...

How do you think the bugs get found and fixed? When Vista (or any OS for this matter) was in Beta 1 / Beta 2 stage... guess what? It had MORE BUGS / glitches then the version that was released to the public. When it went to RC stage, it had less bugs then the beta. When it went to RTM (the version released to the public) it had less buts the beta and the rc.

Nothing will ever be 100% bug free, but to say you dont think there is a difference between alpha/beta/rc and final builds is very VERY naive of you.

P.S. if you were being sarcastic, my bad lol
[Epic 4G General] hazridi:
Actually MS betas don't work that way, they release betas and continue to fix the bugs they are allowed to fix and run 100000 regression scripts and if any regressions are found they actually unfix the bug and attempt a different fix for it.

Eventually they end up releasing a few release candidates and end up picking the least buggy of these to promote to RTM.

I have a number of friends who work as SDE/Ts for MS, this is how it goes.

Also -- it's very possible that an updated code branch has more bug fixes than bugs introduced on smaller projects (like Android customizations) versus something huge like Windows.
[Epic 4G General] abrognlie:
Seriously? Don't you think if the build was so perfect, Sprint would have released it by now?

Fact: There are bugs in DK28. Congrats that you aren't experiencing them.

I personally experience the calling out bug, but not the GPS bug. My accelerometer was jacked up for a while when I moved to DK28 until I found a good workaround (and no, the simple "recalibrate in the terminal method" didn't work). HOWEVER, the benefits to me are greater than the disadvantages of having these bugs in DK28.

This is a forum - the OP was sharing his experience. What kind of forum would it be if no one was able to share there personal experiences with the phone we all have?

Cut the guy some slack.
[Epic 4G General] riceknight:
So... you had a bug and you looked around and found a way to fix it. Congrats. Thats exactly what my advice was.

I've had FC problems on prior Rom flashes before. I reflashed and took my time to fix it. My phone runs smoothly now. I could just Odin DI18 and blame it all on DK28, but like most people, I took the time to get it right. If it were an OTA upgrade, you could blame it on the build, but its a Rom, so take the time to get it running and like you said yourself, there are plenty of people to help with good workarounds.

I don't understand all the pandering and hand holding thats encouraged in these forums. You encourage whining and then complain when there is so much of it. How about encouraging these same people to go out and improve their phones instead of coddling them?
[Epic 4G General] ilostmypistons:
+1 Theres so many resources and answers theres no reason to not have a sweet running,personalized non buggy phone on dk28
[Off-topic] GorislavaG:
Привет xdaforums.com! Я Горислава :D

MOD TRANSLATION: Hi xdaforums.com! I'm Gorislava
[Off-topic] the_scotsman:
Hi :)

Please post in English only or provide an English translation ;)
[Off-topic] ironman14:
Hello! Nice to meet you..
[Android Apps and Games] Carbon Molecule:
Hello everyone!

I recently got myself an Android phone and decided to dive into development. This app is what I came up with after a few days of work. It's very rough, but it appears to work.

The app lets you browse through a database of other peoples' quizzes and challenge yourself with them. If you get tired of answering trivia questions, you can make your own and upload them for others to try.

Obviously this is nowhere near finished. There are still a bunch of features I have to add (like being able to edit your quizzes once uploaded, heh) and heaps of polishing to be done. In the meantime, I would really appreciate any feedback I can get :D.

A couple of notes for anyone who's brave enough to give it a whirl: it currently requires Android 2.1+, to be able to upload a quiz you must have registered and/or logged in before going into the create quiz section, and there are no actual quizzes in the database at the time of this post (except for a test one) so whoever goes first, please be creative :p.
[Fascinate Android Development] calebv2:
hey im wondering if this would work for us or is there some porting needed and is this somthing that would help gps and if im in the wrong section please move.

http://xdaforums.com/showthread.php?t=881941
[Fascinate Android Development] lane32x:
Very interesting post indeed.

From his findings, I'm also wondering if we have Auto Rotate Screen (the accelerometers) turned off, if that hinders the ability for our GPS to accurately detect location and movement. He suggested that it goes into low-power mode when it isn't detecting movement via the sensors, but didn't say what happens if the sensors are turned off.

...I'm going to have to test this out tomorrow.
[Fascinate Android Development] wizang:
Are people still having issues with GPS on the fascinate? Since we more or less had the issue fixed I've had as good or better GPS performance than on my other smartphones.
[Fascinate Android Development] mexiken:
Da_G is a good buddy of mine, trust me, if anyone knows wtf they are talking about, it would be him....
[Fascinate Android Development] calebv2:
im just wondering if this is safe to flash to our phones or does it need to be ported to fascinate
[Fascinate Android Development] phatmhat:
yep still having issues with gps...sometimes doesn't lock. sometimes takes forever. sometimes...omgsh...it actually locks!

not reliable.
[Fascinate Android Development] hondakorn:
I applied the d101 gps fix to eb01 and my gps locks in around 20sec. Auto rotate or not my gosh never locked on eb01 without the d101 fix.
[Fascinate Android Development] grenade01:
Just tested my gps a little. Mine is locking within 5 meters in a brick building with auto rotation on or off. Not in a car currently but I took a little jog and it seemed to follow my direction and location very accurately in both.

So I guess my GPS is pretty good.

Regardless... I wanted to say thanks for reposting that because it was a really interesting read!
[Fascinate Android Development] s44:
It should just work, even though EB01 stock should just work too.

Just don't flash the AT&T-specific version...
[Fascinate Android Development] GizmoDroid:
The Fascinate doesn't seem to have the same layout concerning the gps jupiter files (I don't see them anywhere, at first glance). Either I am missing something or it's a completely different setup.

There are some settings in his /data/gps/secgps.conf (just a text configuration file) that are different than the stock fascinate file. These might be worth looking into to see if they help improve the signal without using his modified binary. You don't need to flash the file using CWM, just use adb to push a modified file (or root explorer and edit it on the phone itself).

Since this is a CDMA phone, I don't know how many people this would affect, but here is a general Android GPS tip for those who don't live in North America:

In /system/etc/gps.conf, change the address to the server that corresponds to your country:

NTP_SERVER=[COLOR="Red"]north-america[/COLOR].pool.ntp.org
[Fascinate Android Development] rmtobler:
I usually can't get an accurate lock or any lock at all unless I reboot with gps already enabled. Then I will get a good lock instantly... If I reboot the phone with gps off then I will get no signal/lock again.
[Fascinate Android Development] CrushD:
Let me share my experience with GPS on EB01, it's GREAT, you just have to turn on GPS "correctly."

If I turn on GPS using the Notification switch, GPS takes FOREVER to lock, if it even does so. Gone several minutes with no lock.

Now here's the thing, if you turn on GPS in the Settings > Location settings, I always get super fast, under 5 second GPS locks. ALWAYS. I've tried this out repeatedly over several days, and it really makes a difference. Once you turn on GPS using Settings, you can leave your phone on, reboot, whatever, and GPS will still be responsive. If you turn it off, wait a while and use the Notification switch to turn on GPS and you're trying to get a cold lock, it'll be slow again, just be sure to use the Setting option and it'll be back to being responsive.

That's my experience.
[Fascinate Android Development] 40kalkillah:
Nice observation...just worked for me too!!
[Fascinate Android Development] pwnjabi1:
By golly... He's right, although it took me about twenty seconds to lock.
[Fascinate Android Development] GizmoDroid:
Hmm... I remember this from a different android device I have. The stock power control widget for wifi would take 45 seconds longer for the network to connect then if I would go to the wifi menu and turn it on myself. I found out that there were two methods for turning on the wifi programmatically, and that some widgets used one method and the other widgets used the other.

If I remember right, the fast method changed the setting by calling the wifi menu and emulating the menu press, while the slow method attempted to power on the wifi directly.

$10 says that if you started decompiling, you'd find a similar situation here.
[Fascinate Android Development] teeharding:
Hey I found a wonderful .tar file that will help anyone trying to get to EB01. You can go from any version with root and CWM included. Hope this helps.

http://www.droidforums.net/forum/sa...roms-w-root-new-clockwork-updated-2-11-a.html

I'm just the messenger. I did nothing for this except find it. Didn't see this around here....hopefully I don't get scolded.
[Fascinate Android Development] lane32x:
This seems fairly solid. I'm already up to the newest version of SuperClean (or else I would use this), but I'm thinking I'll use this to get my friend's SGS up to speed. Can't believe This guy's got an Odin file for 3 different EB01 builds. That's pretty awesome.
[Fascinate Android Development] TheBadBen:
I've been rocking his stock deodexed Odin for a couple of days now. Great, easy package.
[Fascinate Android Development] rice247:
Of course I would see this after going back to DL09 then back up to EB01 the "long way" and setting everything back up. lol Thanks for the link. Should save me a lot of time in the future.
[Fascinate Android Development] ziggy484:
I went for the stock version for my first try with eb01, but might try the others soon. I also was surprised there was no mention of this odin option anywhere here.
[Fascinate Android Development] chronster:
I'm thinking of going with the deodexed version but if I do that, does that mean all my apps have to be deodexed in order to install them? I'm absolutely ignorant about it.
[Fascinate Android Development] RacerXFD:
This is a good way to fix the DBData issue that a lot of us are experiencing.
[Fascinate Android Development] jiggaman508:
I just got a warranty replacement today so finding this made everything so easy, thank you so much
[Fascinate Android Development] modus81:
Worked great. Very easy way to install froyo.
[Fascinate Android Development] teeharding:
Yea I agree it's so simple. Hopefully more people wanting froyo see this. Go thank this dude!
[Fascinate Android Development] chronster:
Yeah this was great. No need to transfer the rom to the sd card and use cwm. Very streamlined and the deodexed rom runs fantastic (just had to remove a few extra items, like DRM stuff)
[Fascinate Android Development] Rav20:
i keep getting an error 0 transfer failed or something like that any ideas?
[Fascinate Android Development] Rav20:
<osm> all threads completed. ( succeed 0/ failed 0)

is the error i get
[Fascinate Android Development] caal920:
Thanks for this life saver!
[Fascinate Android Development] teeharding:
Rav try re-downloading it...it's possible your file is. corrupt.
[Fascinate Android Development] Rav20:
i did that still same error, only thing i can think of is i was using a different cable than what came with the phone, going to try it again with the factor cable.
[Fascinate Android Development] eeshuz:
Trying to download via my phone. Are the links dead? Also I'm thinking it would be easy to replace sc 2.1 with 2.4 and future versions in the package?
[Fascinate Android Development] ezas:
I ran the deodexed version and then restored from titanium backup. Every thing went very smoothly. But I was getting a lot of force closes until I cleared the cache.

I also got rid of the Included swype and installed the swype beta which works much better.

The all in one package is about as ready as it gets.
[Fascinate Android Development] Rav20:
so i got the update done and everything installed now my problem is i have no internet says 3g is on but i get connections errors on any thing like FB or words with friends.

any reason why it would just all the sudden stop working
[Fascinate Android Development] huger82:
Does this still have widgets and touchwiz like in the dl30 Rom?
[Fascinate Android Development] harpdoc:
RacerXFD, can you explain more about what you mean? I assume that you're referring to the battery issues that many of us are having, but I'm not sure. I'm currently running Superclean 2.4 non-voodoo, which is working great other than fairly poor battery life. Are you suggesting that this is a potential cure? If so, could running this, then switching back to Superclean, work? (I apologize in advance if I'm in left field on this)
[Fascinate Android Development] RacerXFD:
This is in reference to the bug that is causing people to lose their stores settings and fc loops on restart.

I had issues of EB01 being corrupted. I couldn't do anything to fix but drop back down to eclair. I used an odin tar to repair the dbdata partition. Now I have a stable eb01.

Apparently, it happens occasionally to those who use voodoo.
[Fascinate Android Development] jpolzner:
I never used voodoo on my phone, but still had the corruption. I think for me it had to do with flashing EB01 with an outdated version of CWM & ROM Manager.
[Fascinate Android Development] RacerXFD:
Did this fix your problem?

I tried everything and was ready to quit.
[Fascinate Android Development] dricacho:
Wow...just Odin'd EB01 and it was up and running in no time! I wish all future ROM's would come in this way.
[Fascinate Android Development] dricacho:
Spoke too soon....

I Odin'd the EB01DB_DXC.tar and everything went smoothly. My phone was up and running in a couple of minutes. However, when I rebooted into recovery I got the Android System Recover 2E (blue). When I selected APPLY SDCARD:UPDATE.ZIP, it goes to the CWM (red) v2.5.1.x then shows:

E:Missing bitmap progress_empty

(Code -1)

E:Missing bitmap progress_fill

(Code -1)

CWM Voodoo Lagfix Recovery v2.5.1.x

Prior to Odin'ing, I had CWM (red) but was running a non-voodoo EB01 kernel. Also the system lagfix was disabled. I did download and copy the update.zip file (in the first post) into the sdcard.
[Fascinate Android Development] exnihilo:
missing the progress_empty and progress_fill bitmaps will not cause any usage problems - it just means the image files were not included in the Recovery
[Fascinate Android Development] wireless_one:
Really simplified this!! I was struggling with this even though I was a vet at WM flashing. thanks for making this that much more similar!
[Fascinate Android Development] dricacho:
Nevermind..............................
[Fascinate Android Development] bobloblaw1:
Apologies for the noobish question... I've been flashing ROMS on the Eris for quite awhile but am now upgrading to the Fascinate. Having to ask something like this is a bit embarrassing.

Basically, I've read through the FAQ threads and I understand the "long-way" to get root and custom ROMS. Is flashing the .tar files via Odin essentially a shortcut to go from stock (or any ROM) to rooted Froyo?

EDIT: Ah hmmm....seems this is the case. Would someone just confirm for me though? It would make me feel more secure about modifying my new toy =)
[Fascinate Android Development] RacerXFD:
The way to fix this is to flash the odin cwm tar I think. Not sure though.
[Fascinate Android Development] RacerXFD:
It's essentially the flashing tool from samsung. It does more than cwm. So be careful when using odin. Always use the pda option in odin. And make sure that you are flashing what was intended for your phone. If you flash a tar for a different phone, you will brick it permanently...
[Fascinate Android Development] bobloblaw1:
Great. Thanks for the clarification. Basically this is like a phone programer and while it is powerful, it is also rather dangerous if you do something wrong.

With that in mind, do you guys check MD5 or a hash prior to flashing? Is there some other protection built in to prevent a corrupted tar from turning the phone into a paper weight?
[Fascinate Android Development] rugolfer:
Does this method require the phone to be rooted? or start w/ a stack phone, and use ODIN to download a new Facinate TAR using PDA?

thansk for clarifying (I bricked a phone last week). So, going real slow ...this time.
[Fascinate Android Development] RacerXFD:
Odin doesn't require root. So real quick, here's how I would flash this.

I would flash the odin file. Then flash the cwm tar, then use cwm to flash whatever rom you wanted...

With odin, typically don't need to check md5. Odin will verify the file for you.
[Fascinate Android Development] sgtflick:
ODIN

I am having an issue! I have the samsung drivers installed, but the only way ODIN recognizes my fascinate is when the phone is on, not in download mode. I have uninstalled and reinstalled the drivers a few times and still same deal. any thoughts or suggestions? I want to update to EB01 from EA28 and am rooted. Thanks!