yashsingh1/xdaforums huggingface dataset:
[Vibrant General] xriderx66:
Id rather not.

They don't have drivers for half the things that make this phone a smartphone.

Also can u post a link to their facebook thing? Id like to see it too.
[Vibrant General] Segnaro:
This lol. All the 2.2 roms depended on Samsung's leaks as a base to have full functionality. :cool:
[Vibrant General] Dougefresh91:
This would be exciting if we had received 2.2 back in September, when it was promised. Samsung is a joke, but we all know that already.
[Vibrant General] Bernardos70:
Where? http://www.facebook.com/SamsungMobile?v=wall

I don't see it. And if it is true, I'm guessing it'd take til June of 2011 to get it in the Galaxy S. Which then would be delayed to July, then August, then September.....

I really think Samsung does it on purpose. I've gone through so many scenarios as to why they are delaying FroYo for so long, and I just cannot reason it. I am certain it is on purpose. Why? That's the one million dollar question. Could it be to sell more Nexus S'? Could be. But no one knows for sure except Samsung...

I just don't see how a company as big as Samsung can't devote the manpower to put this thing together and up and running months ago.
[Vibrant General] PaiPiePia:
Because Samsung never have to made products that needs long term commitmenets. They make TV, Monitors, and Flash Disks, and dumb phones which were all sales are final kind of product; as long as there are no large manufacturer defect, it's pretty much end of support - minus some lemons.

They did have the omnia series, but they develop the OS in house, but was also slow as hell to push out updates. That's the only counter argument I foresee.

Overall, Samsung is just very bad at software, kind of like Sony before PS3.
[Vibrant General] iynfynity:
Tip! Only believe what Google says!
[Vibrant General] mindaika:
According to Samsung, we will have 2.2 by the end of September.
[Vibrant General] justlovejoy:
wow! we all have this phone and are apart of this site. doesnt that stand for something? like the people who have this phone and know nothing of the mods or roms here really do love this phone. they might not be enjoying the luxuries that we have but they are content. besides if i can enjoy gingerbread on this phone before i upgrade it to something newer in the future, cool! if not i will enjoy all of the spectacular work that has been shared by the devs of this community!
[Vibrant General] rsfaze:
what year did they say 2013? As others have stated Samsung has failed to deliver on 2.2 I think 2 or 3 times now and keep pushing it back.

Why would anyone have any faith that they are going to release 2.3 when they can't even get 2.2 out?
[Vibrant General] ikevinnyii:
lol imagine if samsung gave us straight 2.3 and skipped froyo
[Vibrant General] xriderx66:
if i was samsung i'd do that.

Froyo is just known to everyone now, theres hundreds of roms that have Froyo, might as well go on to Gingerbread.
[Vibrant General] SiL3nTKiLL:
lol we willl NEVER get updates on time
[Vibrant General] kolyan:
yep. froyo is history and it didnt really help speed up Galaxy. need Gingerbread, JIT optimization, and etx4.

does Froyo delay has anything to do with Ginger.......hopefully, but i doubt Samsung is that smart and we only gonna get Froyo in a month maybe.....
[Vibrant General] xriderx66:
I know they wont just remove froyo out of galaxy s thing.

They're probably done with froyo and won't be tweaking or anything, and its just waiting on a computer to be released to all, but Samsung is waiting to do something, probably a advertisement move which will make them money.

So far, Apple has given me more customer support than Samsung.

Tmobile is doing great, replaced my phone 3 times, no questions asked.

Samsung is just pissing me off.

I'm ashamed to have a Samsung TV, Samsung Microwave, Samsung Stereo, Samsung Camera, Samsung Phone.

They make good products, but it feels like after they sell a million of that specific product, their done, and want to make something else without supporting that device.

P.S. a thought just came in my mind, what if my Microwave was updateable over OTA? Android... on a microwave.
[Vibrant General] DaSmittyman:
why do people care? you are more than likely joinning xda to root and rom the hell out of your phone. Who cares what updates come down from Samsung besides the leak that help the devs lol
[Vibrant General] kolyan:
that is true.....but it still pisses me off that Samsung missed dead line 3-4 times now. and while there are lots of people here on XDA, there are more people that just waiting for OTA update.

but all we need now is Gingerbread leak, I dont even know if its possible to port Ginger from NS due to the lack of drivers....
[Vibrant General] rsfaze:
because they have failed to meet the deadlines they have set for 2.2.

What is so hard to understand about that? If you don't care, it's easy don't comment about it and move on to another topic that YOU care about.
[Vibrant General] DaSmittyman:
than if thats the case get a new phone and don't support samsung:D
[Vibrant General] xriderx66:
there are currently: 494,063 active members on XDA, and not just for Galaxy S.

and not even all of them are flashing ROMS.

There are approx.: over 3 Million GALAXY S devices out there.

494,063/3,000,000

Yeah. can you see why we want these updates? theres a LOT more people that aren't rooted.
[Vibrant General] N8ter:
Any advertisement move, especially on the internet, will be met with hordes of people complaining about issues and poor support.

Even the Sales Reps in the stores aren't on Samsung's side, trying to sell people other phones so they have fewer people to deal with, who incidentally turn into complainers about these devices. The reps are also now openly admitting that there are "lots of issues" with phones like the Vibrant (in T-Mobile stores here - been to all 3).

Well, Apple releases their updates without having the carriers severely hamper the process. Microsoft will have a smooth experience when it comes to updating Windows phones, and Nokia should not have any issues updating their Nokia phones, either.

WebOS and Android are the only modern smartphone OSes these days which will be hampered by these issues going forward. That's a factorable disadvantage when you consider the competition are in the process of changing the public's expectations IRT how smartphone OS/firmware updates are to be handled.

In a year or two, I do not see Android's model working to well for consumers because people simply aren't willing to spend that much cash on a phone every year just to get an OS upgrade, unless the carrier is letting them upgrade with a contract extention (I think Sprint does this - you can extend a year every year and get a new phone at subsidized pricing).

T-Mobile has no choice.

Samsung is not you first line of support unless you buy the phone directly from Samsung. That's not an odd thing. If you get a new PC with OEM Windows on it, you call the manufacturer (OEM) for support, not Microsoft.

Problem isn't the hardware. Its' the software. They should have just contracted SPB to make their UI skin (like Fujitsu recently did) and not tried to use that Retarded File System (RFS).

Untrue. Lots of people join XDA to get the latest news as fast as possible. Knowing about leaked ROMs is good not only for people who root, but also for people who don't, because it lets them know how far along an update is, and allows them to know of any improvements in the stock software prior to its release. There is no other website that has this type of information for so many different devices in one place than XDA.

There are General Forums for those of us who just generally use the phone, and there are dev forums for those of you who like to hack around in it.

But I missed the Welcome Email where the MODs told me I should delete my account if I don't plan to mod my phone. That's ludicrous, and, TBQH... a pretty damn stupid thing to say.
[Vibrant General] N8ter:
How about you jut buy them all phones, since it is such an inconvenience to be "forced" to read their threads.

Or simply stop trolling people who are posting rather civil replies in a General Thread in the General Forum.

Want to talk about Dev'ing? There's a Venue for that. It's called a Development Forum and judging from your posts you should not have any issues finding your way there.

Ciao.

P.S. BTW, Most Android phones have the same issues. Some OEMs are faster than others, but there is still a lag that is too great IRT getting updates. The only way to avoid this is to use a Dev Phone, and Nexus S is pretty fail compared to i9k and US Variants. No one is gonna downgrade their phone to use an ugly as hell stock phone with a bunch of features removed and many of the same issues being reported (and then some).
[Vibrant General] Evilspawn:
Another useless thread!!! Stop cluttering the forums!!! Search before posting!!! There's tons of threads about this rubbish already...
[Vibrant General] xriderx66:
Thanks for your view on this, and i have to say, i completely agree on that. haha.

and i LOL'd at the end, the mods used to PM saying delete your account if you wont mod your phone? haha...
[Vibrant General] cervantesjc:
Ill just wait a little, TheDudesAndroid is about to port CyanogenMod to the vibrant, cyanogen himself has ported 2.3 to the g2 meaning that CyanogenMod with gingerbread is around the corner.
[Vibrant General] xriderx66:
Another useless post!!! Stop cluttering the forums!!! If you dont like the topic of the thread don't post!!! There's too many posts like yours which serve no purpose...
[Vibrant General] rsfaze:
he has been porting this for about 2 months now... keep waiting
[Vibrant General] N8ter:
No. They didn't.

But many posters here seem to think we (or, people like me) "don't belong here" if we do not root and hack up our phones.

Also, to ammend my post to the person who said don't support Samsung.

Samsung is supported by the Carriers. The Carriers buy the phones and sell them to us.

The only people who can "stop supporting Samsung" are Google and the Carriers - buy yanking licenses or not stocking Samsung phones.

If you think replacing a phone that was bought from them before we even bought it from the carrier will change anything, then I don't know what to say... "Get Real."

Perhaps not buying them in the future will make the carriers change, since they won't be selling Samsung's hardware, but I don't see that happening.

Even when devices have glaring issues, there are always a few fanbois on forums like these fillibustering others and telling prospective buyers that the device is "perfect."

Cause that screen is so good, ya know...
[Vibrant General] rsfaze:
I won't be buying **** with Samsung's name on it, but for now they already got my money :(
[Vibrant General] Only Loki:
I've said it once and I'll say it again, You guys don't know the factors that is causing the releases to get pushed back, Samsung has Five phones that are more different than they are the same that is expecting simultaneous upgrades to an operationg system that upgrades faster than the normal development cycle. I Doubt Sammy has the relationship with Google that HTC and Motorola has. They also aren't the only android using company that don't upgrade on schedule if at all (Sony anyone?) I bet they put in a bid for the nexus 2 so they could develope that type of relationship.

In addition to the people saying they aren't going to give us updates, where do you think these leakds are coming from, do you think they keep a staff of devs around just to tease us with works in progress, that never plan on getting released.

To the the people who think windows phone 7 will be updated take a look a MS's track record or ask an HD2 owner who was promised an automatic WP7 upgrade until the phone sold like hotcakes and ms changed their minds
[Vibrant General] N8ter:
HD2 isn't a WP7 device, and Microsoft never promised an automatic upgrade (provide a quote, don't embarass yourself).

The HD2 has absolutely nothing to do with WP7 dates, and Windows Mobile updates have absolutely nothing to do with WP7 updates.

Don't know how you could make any less sense than you did with that.

P.S. I had an HD2. I was never promised an update, and certainly didn't expect one.
[Vibrant General] anthonys2r:
We will get 2.3 when 3.0 has been out for 3 months.
[Vibrant General] mmalott:
Honestly, I really wanted not to root or do anything to the phone. But the nagging lag, lack of gps, and no updates pushed me to root and flash. I'm not a huge fan of touchwiz but could have lived with it if the phone wasn't riddled with issues. Point being is that with the Galaxy series I feel like theyre digging their own grave with people who know and putting off the customers that dont.
[Vibrant General] rsfaze:
I agree we may not fully understand the obstacles but one would think Samsung does, and keeping that in mind why give us release dates for Froyo when THEY know they won't be able to meet them?

things that make you go hmmmm :)
[Vibrant General] down8:
Your logic is flawed.

People don't replace their TVs every 2 years (or less). They expect those to work properly, with all things listed on the box at Best Buy, on day one.

Phones (especially smart phones) are were mfgs get leeway, b/c ppl turn them over so quickly. And they get to take turns pointing fingers back and forth with the operators.

-bZj
[Vibrant General] N8ter:
TVs don't need firmware updates, and aren't sold on contracts.

His point is valid when comparing the way those different devices are supported by the manufacturers.

If you're TV doesn't work right you just take it back, or the manufacturer recalls it. Requirements don't really change down the road from the purchase of a television or ice box.

Phones are different. Requirements can change later and bugs that weren't apparent to the user at purchase can lie hidden until then. Software issues on phones can be fixed with firmware updates and most consumers expect manufacturers to fix those.

Maybe you purchase a device not wanting any support, but most people who spend this much on a device do it with the understanding that they will be supported if the device is later found to be defective or deficient in one form or fashion (of course IRT the advertised/guaranteed functionality).
[Vibrant General] anilo:
Wow! 5 pages and over 40 posts and no mention of a faulty carrier!?!?!

I am not trying to defend Samsung since their product shouldn't have had the GPS and lag issues in the first place, however, we should be fair to them when it comes to Froyo upgrade since they released it in other countries.

What does this tell us? IMHO,this is the marketing strategy of the carrier(s) rather than the manufacturer. Samsung has sold the most Android phones in the world. I am not really believing that they are holding 2.2 update just to sell Nexus S. It's stupid T-Mobile (for Vibrant) who is not sending us the updates. They are the greedy ones and want to sell more MyTouch's and G2's, before making our phones an equivalent of Nexus S.

My 2 cents...
[Vibrant General] lexluthor:
No way.

You either have to believe it's primarily Samsung's fault OR that it's Sprint's, AT&T's, T-Mobile's AND Verizon's fault.

Odds are not on your side with that logic.
[Vibrant General] :
And Bell. I mean, I'm sure that once T-Mobile et al. get their hands on the Samsung release 2.2, they will **** it up further, but it's pretty unlikely that Samsung passed the update to the carriers and all the carriers colluded to hold the update indefinitely.
[Vibrant General] Blown 89:
People care because their phones aren't working properly and flashing ROMs is a pain in the ass that customers shouldn't have to go through to get a functioning device.
[Vibrant General] fenixnr:
Nexus S is here! Samsung has announced the release of the first smartphone to feature the new Google Android 2.3 OS. Nexus S will be available in the U.S. and U.K. later this month. Check out the details here: http://bit.ly/eteCXQ

Thats all I see about 2.3, LEARN TO READ, this doesn't state all phones will get it, just the Nexus S
[Vibrant General] ndwgs:
LMAO!!

Besides, I agree, just keep flashing, and give up on waiting....

Sent from the helm of darkness called, the "Vibrant Galaxy"... Using the XDA App!
[Vibrant General] ndwgs:
Nice...

I'll start making that project! Porting now!!!

Sent from the helm of darkness called, the "Vibrant Galaxy"... Using the XDA App!
[Vibrant General] eortizr:
Vibrant will have 2.3 fully functional when cows fly, c'mon we don't even have CM6.
[Vibrant General] nomadrider123:
well now I guess I always tellppl google is your friend :D
[Android Software/Hacking General [Developers Only]] The5ickne55:
Trying to transfer over set cpu profiles, angry birds saves (lol), and my gentle alarm, how can I easily save the settings for a painless transfer?

I know titanium back up creates a back up, but how can I reinstall everything once I get the new phone?
[myTouch 3G, Magic General] geolemon:
Magic stuck on "htc magic" boot screen after Engineering SPL... and bad Nandroid, ugh

Please help, I'm stuck on a boot screen, compounded by an apparently bad Nandroid backup :(

I just got a Rogers Magic so I can get 3G on AT&T. (couldn't with my T-mo G1) Rooted it, installed the RA-Sapphire recovery and took two Nandroid backups (one with, one without Ext)

Here was my starting point:

SAPPHIRE PVT 32A SHIP S-ON H

HBOOT- 1.76.0010 (SAPP50000)

CPLD-12

RADIO- 6.35.10.18

Plan was to install Cyanogen 6.1.0 (like my G1). This requires that I downgrade the radio, and I was planning on using RadioSwitcher tool to make life simpler.

The tool requires an engineering SPL be installed, and points to this Magic SPL Hboot collection thread

I've downloaded and/or tried (in this order):

Stock: 1.76.0010 (as noted above)

Engineering SPL 1.33.2010 (from the SPL collection thread the tool instructions pointed to)

1.76.2007 SPL (from the Cyanogen Wiki on Magic 32A with 6.35 radio)

Engineering SPL 1.33.2009 (from the SPL collection thread the tool instructions are pointed to)

So when I tried using the tool to switch the radio to a Radio_HTC_PVT_32A_3.22.20.17 [supplied], I got these results:

Stock 1.76.0010 - tool won't update radio without an engineering SPL. Device boots up no problem.

Engineering 1.33.2010 - tool uses Fastboot, I see progress bar, then screen goes black and tool reports "Radio update: FAILURE". Device now won't boot, hangs on "htc magic" boot screen.

Tried to restore - Nandroid restore issue noted below.

Engineering 1.76.2007 - same progress bar/black screen, update "FAILURE", and device won't boot.

Engineering 1.33.2009 - same progress bar/black screen, update "FAILURE", and device won't boot.

(I tried posting on that Radioswitcher thread but it's locked or closed or I'm just not able to post on it.)

I don't feel comfortable randomly trying SPL's, especially as I'm guessing there's simply a lack of understanding on my part as to which SPL is compatible with my current phone/radio. I'm hoping someone here can help with that.

Currently, this is how the phone sits:

SAPPHIRE PVT 32A SHIP S-ON H

HBOOT- 1.33.2009 (SAPP50000)

CPLD-12

RADIO- 6.35.10.18

...not able to boot, not able to restore:

I can get into recovery, but it's also testing me:

When I try to flash anything from SD, I get "E: can't mount SDCARD:" If I select "USB-MS Toggle" then disable it and come back, then it appears to work - but doesn't give me warm and fuzzies.

Nandroid restore - either backup gives "Error: run 'nandroid-mobile.sh restore' via adb!"

That really makes me uncomfortable and puts me a bit out of my comfort zone - I was counting on the Nandroid backup as my safety net... never had any issues with my G1 and Clockworkmod recovery. :huh:

Thankfully, I have the trusty G1 I can plug my SIM card into to use as a phone... :o

But I really need to get this working or it's a lot of money, and hopes, down the drain.

Help - please! :confused:
[myTouch 3G, Magic General] geolemon:
I used this guide to root my phone to begin with - I see there's an engineering SPL option in there also.

Although I said I wasn't going to try pot-shot SPL attempts, this was part of the rooting process I followed originally, and someone suggested that I try that one.

I can't boot my phone so I couldn't follow that process exactly, but I extracted the SPL file from that zip file and put it on the SD card using my PC, then booted into recovery to flash that Eng SPL...

...and still the Magic won't boot up. I can't tell if this is even any different than the previous SPL - or rather if the problem preventing boot is a problem, if it's tied to the SPL (numerous SPL-swaps would seem to indicate no?) and if it's different.

Now I'm here:

SAPPHIRE PVT 32A SHIP S-ON H

HBOOT- 1.76.2007 (SAPP50000)

CPLD-12

RADIO- 6.35.10.18
[myTouch 3G, Magic General] mumilover:
Stop...you have an eng spl... Thats all what you need!

You are working the BLIND...

For every spl there are matching radios...

For the 1.76.2007 spl, you can use any 6.35 radio for magic.

For the 1.33.20xx(xx can be 04,05,10) you can use 3.22 radios.

All the above are eng spl, which basically gives extends read/write permissions.

With the eng you can flash what ever partition you want, e.g. system, radio or recovery.

The reason you can't boot is that you have **** up your system.... That we can fix easy :0)

Radio/spl **** ups -> not to so easy to fix.

You have a good combo now, let's get you a good system.

First, you need to flash a different recovery to make sure it works with the 6.35 radio.

Download my fastboot commander tool (magic version, check my signature) and it will do it for you the easy way.

When you have the tool, go to magic 32A tab.

There you can find two buttons, one for 6.35 radio combo a.k.a new radio.

You also find one for 3.22 radio a.k.a. old radio.

The tool will flash an entire combo of radio, spl and recovery that matches :0)

so... this what you have to do, choose 1 and only 1:

1) use the tool to flash "new" combo, reboot into recovery and flash any rom that is for the new radio (6.35). Check out the development sections for roms.

2) use the tool to flash "old" combo, reboot into recovery and flash any rom that is for the old radio (3.22). E.g. cyanogenmod from this page:

http://wiki.cyanogenmod.com/index.php?title=Latest_version#MagicCM6

Remember to flash the EBI 1 kernel or else the system will not boot.

The gapps (at the buttom of the page) are optional but recommend :0)

Good luck, and stop working the BLIND!
[myTouch 3G, Magic General] geolemon:
Sounds good...

Should I expect that after flashing the "old" images, that I'd be able to boot my phone into the stock OS again (1.5 with Sense)?

Or should I just skip that [if that's not a good test] and just proceed with loading the Cyanogen ROM?

Very much appreciated, and thanks again.

Also, one thing I'm concerned with - I've seen some notes along the way that the Magic requires a custom Kernel to install Cyanogen... I'm not sure what the Kernel really even is. Do you have any insight into that?

http://wiki.cyanogenmod.com/index.php?title=How_to_build_a_kernel_port_for_CM6

I've got the 32A - but those instructions are hardly 'download this file and flash':

"If you want to build a EBI1 kernel port package to get it to run on a 32A Magic (with 288 MB total RAM), or a phone with the 3.xxx radio such as the Rogers 32A Magic and Rogers Dream, then you can follow the instructions below:"

...and those instructions are long, and most intimidatingly - vague (much is implied, not all explicitly stated).

Yikes...