yashsingh1/xdaforums huggingface dataset:
[Epic 4G General] HeXeD:
Well.. Samsung definitely said all of the US Galaxy S phones would have froyo by the end of the year and never really used to word "hand it off to our partners". I'm not sure though how it all went down, but I'm pretty sure the DK28 version they released to sprint wasn't really ready for prime time. If every other provider received Froyo for their Galaxy S phones, then I would have to say it is all Sprint's fault, but Samsung seemed to certainly have a delay of some sort...

..but that was my point in another one of my responses was, if Samsung was finished by December, that doesn't mean the providers would have everything ready to roll the second they received it from Samsung. I don't know if we are ever going to get the true story but that really doesn't matter now.
[Epic 4G General] imtjnotu:
Finally we will get a fully working cm6 or 7...and full roms ith custom kernels...thank god I've wated agessss
[Epic 4G General] imtjnotu:
Actually it was promied in september
[Epic 4G General] aleph23:
Haha! I said I was leaving if we didn't get source. Looks like that guy who wanted to trade his evo will have to find someone else... Lol tv out?
[Epic 4G General] imwillzillla:
Agreed, froyo is probably on its way, the damage is done. The rest is hair splitting such as me saying froyo was promised in october and getting jumped on by a pink hat ho said "no its not october but by the end of september" lol I guess the twitter trending topics and countless frustrated customers were all wrong but pink hat has it all under control.

Anyway, feb 21st which happens to be on my birthday will be a very busy day and while I'm all for being frustrated over froyo or lack thereof but this update gives the basic expectations from a stock android phone such as flash and hopefully more stability
[Epic 4G General] HeXeD:
Awwwww cmon DQ, where is that source I asked for? I find it funny when people start so much drama about something that they were totally wrong about, and then they can't admit it. I would feel pretty foolish if I kept starting all kinds of drama over a tweet that was never meant for the US in the first place. The funny thing is you probably searched and searched for your precious promise from Samsung and never found it.. cause it never happened.

BTW.. pink hat refers to a chick that wears the pink version of team gear, and doesnt know crap about the team they root for (yeah I just looked that up). The funny thing is, I happen to know a whole lot more about this than you do... seeing that you didn't know what a source file was and what it is used for, and weren't able to get your facts straight regarding the UNITED KINGDOM getting froyo in october/november. Don't worry DQ, you still got your pride.
[Epic 4G General] ungovernable1977:
Pink hat ho??? really no clue what youre talking about there... even if it wasnt me, curious as to what the hell it means... sounds kinda funny...kinda.

re the dates, heres how I remember things, and I am ok with being wrong mind you, just what I know.... around launch, rumor, and sales pitch was end of september, more of a sprint thing, then soon after, Samsung promised by end of year, to deliver to carriers, which supposedly did happen in Oct, hence most non-US versions being updated. then we see all these SPRINT builds.... the ones before DK28. DK28 came from google code, not sure who worked on that last, but if it went back to samsung, there better be a better reason than rooting protection, or bloat, or again, back on Sprint. Then SPRINT leaks internal doc saying 26th... doesnt happen, SPRINT pulls it... see a pattern? my point was just that the carriers seem to be the common issue here, not just that samsung made all these different phones.

as for your last statement... Happy Birthday, not sure whether you are happy to get an update or not. Yes we all know pressure should be kept both on Samsung and sprint to ensure it never happens again, but assuming its good, enjoy the damn update
[Epic 4G General] wynand32:
What's this webOS update model you're referring to? I can tell you, as a former webOS user, waiting for updates to hit one carrier or another was just as much of a frustration as waiting for Froyo has been (maybe not quite so long, but long enough). Palm was, and HP will likely be, just as much at the mercy of carriers. And given the recent no-webOS-for-legacy-devices debacle, I don't think anyone here would like Samsung to follow in HP's footsteps.

Regarding Apple, we'll have to see if Verizon allows Apple quite so much flexibility as did AT&T. Maybe they will, and good on them if they do, but it still remains to be seen.
[Epic 4G General] HeXeD:
Nope.. it wasn't. If by "it" you mean the froyo update for US carrier versions, That tweet for September was the UK version (SamsungmobileUK) and had nothing to do with US. Then in October it finally released but was pulled quickly due to "issues" and released again in November.. for UK folks. For the US carriers, it was specifically said in the launch party that Samsung was going to get froyo on all US carrier versions by the end of the year (at the launch it was ATT, Verizon, Tmo, and Sprint).

If you are referring to the fact that the Epic 4G came out on August 31st and Sprint said it would be arriving "shortly after release", and your definition of shortly is within the month, then yes, SPRINT said it would be coming in September. I know they didn't say September, but their reps were telling everyone and their grandmother that Froyo was shortly behind the release. To me, 5 months down the road is not "shortly" but it's all a moot point now with the official release around the corner.
[Epic 4G General] ungovernable1977:
HOLY CRAP! I forgot that was a samsung UK tweet! lol.... oh and while trying to find pink hat, and stumbled across white hat, someone who wears a white hat in winter... where I come from its the rich, douchey, typically white preps who thought they were 'Gs'. But that was the 90s....
[Epic 4G General] HeXeD:
yeah, I already explained it in one of my last posts but a pink hat is basically some chick that gets all decked out to go to a sporting event in their team's "pink" gear which is the outfits for chicks with the team emblem on them. Basically the type of person that says they are big fans of the sport and their team, but don't know anything about the team, or the sport really, and ends up spending all their time not paying attention to the game and talking on their cell phone.

...yeah it doesn't make sense. Obviously a term he learned from a NBA or NFL forum and never learned how to use it right.
[Epic 4G General] imwillzillla:
My bad, it is called "pink hat" the whole pink hat ho was a typo which is due to the samsung keyboard issues. but I guess well say that's sprints fault

Pink hat is a Boston red sox term thing which describes fairweather fans who swear up and down they are the biggest red sox fan but couldn't tell you the starting rotation.

They are blind to anything red sox good or bad.

A good example of a pink hat would be someone who is dating a huge sports fan but has no interest in it. But when they are around their friends they act like they know every stat.Which describes some Perfectly. Nothing wrong with being tired of complainers but to act as if Epic owners have nothing to be annoyed over is ridiculous. And now I kind of understand as I'm tired of complaining about it already.

Thank you very much for the birtbday wishes
[Epic 4G General] dr_gibberish:
Can we declare this thread officially and totally derailed, killing all aboard?

Mods?.... someone?.... Please put it out of its misery... cough cough... sputter...
[Epic 4G General] murso74:
could someone explain to me why having froyo source code gets us closer to CM7? i thought CM7 was gingerbread. do i not understand this stuff at all? i'm a sad stupid little monkey with this stuff
[Epic 4G General] inimitableac:
Team Viper Dev has a kernel compiled and working hopefully we'll get it soon
[Epic 4G General] AproSamurai:
Ahhh don't insult yourself.:)

Eclair to Froyo was an update of firmware that was a largish leap so many properties of Froyo like JIT and AOT(not sure about this one, I think I have the wrong compiler name) could not be built off the eclair source for a devices architecture because it wasn't there. From Froyo to Gingerbread isn't such a big leap, plus they also have the Nexus S to fill in Samsung Blanks. So they have a large portion of GB in Froyo so they just need to port over specific portions and ideally we'd have Gingerbread.

Hopefully that wasn't too cluttered and it helped you, I apologize if it was though.
[Epic 4G General] lviv73:
Man,if youre saying that DK28 was finished product that Samsung gave to Sprint then we have a big problem!

DK28 is so laggy and slow that if we took all devs from xda and put them together they could not emprove it.Yeah Bonsai/Viper and others did a great job imroving it but there is only so much they could do with DK28.

For all ya that say "Bonsai Ext4 is silky smooth"-its not and never will be because its from DK28(im using latest Bonsai right now).

All you have to do is compare any DK28 rom to Syndicate-now thats smooth!No lags,smooth transitions,smooth browser scroling(and no it has nothing to do with flash).Syndicate is rfs and DI18 based,imagine Syndicate with Ext4!

What im saying is this:If DK28 is a finished 2.2 then it should be at least as smooth as DI18 Syndicate but its way slower,more laggy and buggy.

So if Samsung just gonna say "Fck it,we just gonna release DK28 as finished product-its good enough"-it might be good enough for some but not for me!If thats the case then i will just go back to Syndicate and wait for Cyanogen and MIUI to come out.

From what I heard about buggy Vibrant's 2.2 ota update-i would not be surprised if Samsung pulled some **** like releasing DK28 with newer date stamp on it as finished product.
[Epic 4G General] ungovernable1977:
by no means did I say DK28 was a final product, my speculation was only that Samsung had passed on to the carriers what they had in Oct, but it really does not matter, because I was replying to an incorrect statement that we were promised Froyo by end of year, when someone then reminded me that that was a twitter (when does this crap count as official anyways??? Girls passing notes in class...) from Samsung Mobile UK... i.e. does not apply to us... but these are all just rumors, tweets, and other such unreliable crap. I am just postulating that people would rather blame a manufacturer than the carriers, or at least not call it equal since we will never know what really transpired. I personally think people are more personally invested in their carrier, they get attached, best reception in their area, etc. so they dont want to admit to themselves they are paying these people monthly, so blame the manufacturer and walk away.
[Epic 4G General] Kif420:
Space docking
[Epic 4G General] ghostrid3r:
sad part is a lot of these "myspace/twitter/blogs" folks taking other people's brain farts they tweet/blog about as being a fact/official statement.
[Epic 4G General] imwillzillla:
Very true. Perhaps that's where the disconnect is. But can't blame the reader when compnies actually tweet and blog to get their info out?
[Epic 4G General] bondosho:
If bugs can't be squashed, delays happen. Would you rather have something released that hardly works, or something that is finished, and out of beta? I realize that it won't be perfect, but it will be better than if it was rushed and released at the end of the year. If people are basing this on whether to buy another Samsung product, you guys may as well never buy any sort of software or hardware again. I'll give you that they may have wanted to be a bit more vocal about it, but come on people, it's a phone. If you have nothing to do but complain about software for a mobile phone, you may want to re-evaluate your priorities, and your life in general.
[Epic 4G General] snowmanwithahat:
Did anyone actually notice it will be 2.2.1 on 2\21 ? ... did they plan this from the start?
[Epic 4G General] iSaint:
someone predicted that like 3 months ago 8/
[Epic 4G General] gophergun:
The ideas are that Samsung shouldn't have modified Android so dramatically, they should have had these bugs worked out by launch, had more programmers on staff, etc. HTC and Samsung are working with the same source. The disparity in OS releases between those two (2 vs. 6 months) is inexplicable and unreasonable. Whatever problems they ran into are obviously not inherent with computers based on that evidence. On top of that, this "just a phone" argument ignores that they're not just phones anymore - they're fully fledged computers, 1GHz processors, web browsers and all. And on the computers we've all spent $250 on, plus thousands over the life of the contract, they won't do the things we want them to - not for any technical reason, just corporate beaurocracy and poor coding.

Personally, I think if this is just a phone to anyone, they've been severely duped by the salesman as to what kind of device they need.
[Epic 4G General] djcslice:
HTC has been developing android for quite a bit longer then Samsung. Basically for the past 3 years, HTC has solely been focusing on android and have a lot of in-house kinks worked out. Samsung definitely dropped the ball but you cant expect perfection out of the box. Also, CDMA is much harder to develop on Android than GSM.
[Epic 4G General] muyoso:
First of all, Samsung built 2 seperate updates in that six months. Sprint rejected the first one because of z4root.

Second of all, the Evo update is not that impressive. HTC uses the same damn hardware for every phone it builds, so it can port drivers without any hassle. And don't forget that HTC built the Nexus One which was the reference platform for Froyo and also used ridiculously similar hardware to the Evo 8 months before the Evo got Froyo and they released the HTC incredible on Verizon over a month before the Evo with the EXACT same hardware save for 4g. Samsung had to build every driver from scratch for every component.

You are way off base.
[Epic 4G General] gophergun:
T

Do you have a source for the first claim? As for the second, the differences between the Evo and Nexus seem similar to the Epic and Galaxy S - CDMA/WIMAX radio, FFC...there's the keyboard, but driver-wise that's cake. I know we've got a different audio chipset, dunno about the Evo's. Evo's got a different screen than the Nexus, of course. Samsung does a very similar thing, having built umpteen variations on the basic Galaxy S hardware over the past year. They may have had to build them from scratch, but that was done by what, June? It doesn't come close to accounting for the time disparity.
[Epic 4G General] muyoso:
The source for my claim is that we are getting 2.2.1 and basically the only fix 2.2.1 offers is that its no longer rootable by z4root. And Galaxy S devices internationally did get 2.2 on time in November and later got updated to 2.2.1 in January.

As for the rest, HTC uses Qualcomm SoC's for every phone. You cannot argue that creating drivers for an entirely new SoC, which is what Samsung had to do, is the same as HTC porting drivers from one revision of a Qualcomm SoC to a slightly newer revision, over the course of 8 months.
[Epic 4G General] aleph23:
I believe his argument was that Samsung uses the same drivers too, just like HTC, even if they're not all Qualcomm. Aside from gsm v cdma, all galaxy s phones (& there are a lot of them) already have updates, including to gingerbread. The Epic doesn't need to have it's own drivers rewritten for the hardware that it shares with the rest of the line.

On top of that, any corporation the size of Samsung could have put a couple more programmers on the project. It seriously seems like it's just been one guy's side project.
[Epic 4G General] gophergun:
Patching a security hole just doesn't take that kind of time, and shouldn't require a complete overhaul. If Samsung had 2.2 done, patching the changes from 2.2.1 would be extraordinarily simple. There's no evidence Samsung ever submitted a finished 2.2(.1 or not) to Sprint before now. The person above me clarified the second point well.
[General Questions and Answers] arm_chair:
Hi,

Apologies if this has been answered before elsewhere.

I have been trying to use Atools to install Android on a HTC Pola100 (Touchcruise) PDA using options HARET & FROYO with system.img and data.img files in order to protect other content on my SD card.

The help page was quite informative except for where to obtain compatible haret.exe and androidinstall.tar files but I found ones on the internet dated 28/01/2010 and 24/4/2010 respectively.

The install process starts running (has a penguin image if that helps), but produces dozens of messages (which scroll off the screen too quickly to read and I haven't found a log file) before finally hanging.

The final messages are:

/init: line 334 :mount_opt: not found

sh: 2: unknown operand

found boot parameter for system

system on sd partition

e2fsck 1.38 (30-JUN-2005)

e2fsck: while determining whether /dev/block/mmcblk0p2 is mounted

e2fsck: while trying to open /dev/block/mmcblk0p2

possibly non-existent or swap device?

e2fsck: mount: mounting /dev/block/mmcblk0p2 on /system failed. no such device or address

failed to mount/system

I thought it might be a problem with my SD card, so I reformatted it and tried again with the same result.

Also tried the partitioned install, but it failed to create the partitions.
[General Questions and Answers] arm_chair:
have now found an alternative install process that works
[General Questions and Answers] Hrqls:
alternative

hi,

i am trying to install an android version on my htc touch cruise

i am getting the same results

i tried the froyo install from :

http://xdaforums.com/archive/index.php/t-1055266.html

what alternative did you use ?
[General Questions and Answers] francodapalermo:
change rom
[General Questions and Answers] Hrqls:
what do you mean by 'change rom' ?

i would like to install android (any version) on my htc touch cruise with the hardware as it has right now
[Captivate General] seivad17:
Does anyone know what controls the ability to click on the address links in the "where" section of the calendar? Cognition is the only rom that does this. I've tried pulling the touchwizcalendar.apk and tochwizcalendarprovider.apk from cognition and putting it on other roms but still no address links. Although, I am able to click on phone #'s that are put in the description area, still nothing for addresses.

Just to clarify, I'm trying to find out how to add the ability to the calendar that when an address is put in the "where" field it automatically becomes a link that will launch maps and do a search for that address. -Thanks in advance
[Captivate General] edtonn:
+1 This is one of the very very few features I miss from the Blackberry world. Any ideas?
[Captivate General] seivad17:
Yea, I know it's possible because it's working on the cognition rom. The question is how do we transfer the ability to other roms.
[Captivate General] cappysw10:
http://androidforums.com/samsung-captivate/130030-location-not-clickable-calendar-widget.html
[Captivate General] seivad17:
Thanks but that's not quite what I'm looking for. There seems to be a way to get this functionality into the touchwiz calendar.
[Captivate General] bravomail:
Gemini Calendar or Touch Calendar

Gemini Calendar or Touch Calendar. They both work.

I have the same issues with Galaxy ROMs.

Biggest complain - cannot dial conference bridge codes easily. I'm making manual change in the calendar to have "800CALLME;CODE" and then Copy-Paste to dialer.
[Captivate General] Ben753:
Any progress?

Have you had any luck finding a way to add this functionality to the samsung calendar? I am having the same issue with the galaxy s2 and keen to try to work out how to fix it. am assuming the touchwiz calendar is similar on the two devices.
[Captivate General] nakedninja42:
I think that is a feature only on the ATT stock systems which the Cognition ROM closely resembles. I wish I could have this feature but I have never seen it working on any 2.2.1 I9000 ROMS or the newer 2.3.3 I9000 ROMS.

If anyone finds a solution, that would be awesome!
[Captivate General] Ben753:
Just to check, are you saying it was an AT&T app separate from the Samsung touchwiz ones on most of their phones?
[Captivate General] nakedninja42:
not really sure. I know that its still a samsung touchwiz app, but it for some reason it only worked when i was on Cog. Im no Dev or anything like that, just an observation I made while flashing
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] cardboardman:
Hi,

I recently upgraded to an HTC HD2 that I bought on eBay. It was an O2 phone that had been unlocked so I could use it on Orange. When I picked it up, SMS messaging was working fine, unfortunately, a dodgy app meant I had to do a hard reset and since then I can't send or receive text messages.

I've checked that the message centre number is correct. I found it in 2 different places but it's the same in both (which is the number that Orange provided).

Any help would be much appreciated.

Thanks,
[HD2 Android Q&A, Help & Troubleshooting and Genera] chazperx:
Hi:

I just got my Telstra HD2, and am very excited about installing Android on it but don't know which one to install. I also have a HTC Pure which I am also running Android on.

On the Pure, I boot into Windows 6x and then start another program called Haret something or another, and I then have Android.

I am looking for the same functionality on my HD2. I will basically use the HD2 Android for apps, and the HD2 Windows for Calls/Contacts/Calender, so I need to be able to switch back and forth via rebooting or some other way in an easy fashion.

Any links, suggestions would be greatly appreciated...and thank you in advance!

Chaz
[HD2 Android Q&A, Help & Troubleshooting and Genera] jellywobbles:
Before I switched to a NAND build I used this:- http://xdaforums.com/showthread.php?t=870518

Check the forums - it's all a matter of taste! They're all good!

Hope this helps ;)
[HD2 Android Q&A, Help & Troubleshooting and Genera] guinhill:
If you want a Nand build to chose from, see this list [17 FEB]HD2 NAND BIBLE [roms][kernels][mods]

I aggree with jellywobbles on the SD build, it's sollid and fast.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Azerox:
The stuff in my SIG will work great :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] xirokx:
Dont hesitate and install the Hyperdroid GBX 5.0

Its by far superior to the rest in terms of speed, smoothness and unlike the others the creator actually helps you resolve your probs

cheers...
[HD2 Android Q&A, Help & Troubleshooting and Genera] zarathustrax:
If you still want winmo, you must use a SD build... look in the SD development section for SD builds. It will work the same way with haret.exe, but you must also run clrcad first, then haret.exe.
[HD2 Android Q&A, Help & Troubleshooting and Genera] invisiblebm:
Hi if you want android with sense use this:

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

Fast ,stable and nice.
[HD2 Android Q&A, Help & Troubleshooting and Genera] pairojn:
I use MDJs_CyanogenMod7_v.2.6_NAND_A2SD+.

http://www.youtube.com/watch?v=91mnfufny-Q

and follow step by step here.

http://xdaforums.com/showthread.php?t=893948
[HD2 Android Q&A, Help & Troubleshooting and Genera] jellywobbles:
Without doubt the best NAND ROM for the HTC HD2 you can get. That's the good news - bad news its has been removed from XDA due to GPL issues, so you'll have to hunt for it!

Be interesting to see just how long the links you posted stay here! ;) No doubt a mod will edit your post & remove them! :(

Tick Tock Tick Tock Tick Tock ............... :eek:
[HD2 Android Q&A, Help & Troubleshooting and Genera] feloccio:
Skink Clean Desire

I prefer the Sense UI. Basically the dhd and dz builds are great and have the new sense but i couldnt find a rom that was stable and ready for daily use.

Now i use the Skink Clean Desire 1.2.

Its fast, stable and battery-friendly, what more would you want?