• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

***Official Samsung Fascinate 2.2 Speculation Thread***

Status
Not open for further replies.
Quote:
Originally Posted by Foxcow
...should not have to.

^^^^^^That's the whole thing right there.



+ 1,000,000,000!

__________________
 
I personally think Verizon is mostly if not completely to blame for the delay. They have not produced any significant updates in a very long time while Samsung seems to be rolling them out regularly for other carriers. Verizon wants everyone to get frustrated with the phones they have now on contract so they will either buy an iphone or upgrade. They have us all by the teabags and there isn't anywhere for us to turn. We should not have to root our devices to get what we were promised when we made our purchase. Hating Verizon...wishing for an alternative.
 
I personally think Verizon is mostly if not completely to blame for the delay. They have not produced any significant updates in a very long time while Samsung seems to be rolling them out regularly for other carriers. Verizon wants everyone to get frustrated with the phones they have now on contract so they will either buy an iphone or upgrade. They have us all by the teabags and there isn't anywhere for us to turn. We should not have to root our devices to get what we were promised when we made our purchase. Hating Verizon...wishing for an alternative.

With AT&T purchasing T-Mobile (of course after Cingular, Edge, Altell & VZ, Nextel and Sprint, and other absorbed carriers) our alternatives are diminishing year after year after year ....
 
My Fascinate will continue to collect dust on my desk until it gets Froyo. NOW, if my Droid X gets Gingey soon, then the Fascinate never be activated by me again.
 
I've been thinking about this whole Froyo fiasco and what it's really doing to us. These are good, no...great phones (even on Eclair), but for some odd reason we always want to have the next biggest update on them. The jump from 2.1 to 2.2 wasn't huge except for flash and apps2sd in my opinion.

2.1 rooted, slightly overclocked and undervolted was the best for me...but for some reason I'm still running SC 2.2 :D
 
Whole Lotta WTF if that actually happens......I guess I made the WRONG phone choice again.

I almost got the X over the Fascinate, but the sheer size of it was kind of a daunting thing for me. Putting lack of 2.1, possible 2.3 on X and everything else aside, I still love my phone, but sometimes feel I should have gone with the X.
 
The jump from 2.1 to 2.2 wasn't huge except for flash and apps2sd in my opinion.
It came to me tonight as I watched March Madness. Verizon has been holding back these upgrades because of flash. Think about it - if everyone had Froyo, they'd have flash. All the March Madness games are streamed using flash. Think of the network traffic Verizon has avoided by stopping a number of their phones from officially getting 2.2 and flash. If my idea is right, we should be getting the upgrade in another 14 days after the NCAA Mens Final is over. One can only hope. And if it's true, then we also know who to blame.
 
I almost got the X over the Fascinate, but the sheer size of it was kind of a daunting thing for me. Putting lack of 2.1, possible 2.3 on X and everything else aside, I still love my phone, but sometimes feel I should have gone with the X.

I'm in your same boat. The Fascinate is still the better phone in the hand, and much more ergonomic to use. The camera is noticeably better, and the format support for video files is out of this world. After a simple conversion on my PC (or sometimes no conversion at all) I can throw MKV's, AVI's, MPG's, etc. on my Fascinate and catch some movie/TV action on the go.

The droid x was so blitherin' finicky. I had to carefully and specifically convert each file to set parameters with certain bit rates and with a certain container to get it to play on the X at all.

And boy, do I love videos and pictures on the Fascinate's screen. The DX was great for text - razor sharp. But the Fascinate definitely displays games, pics, and vids MUCH better.

I don't regret my decision. I chose the best phone I could, and at the time BOTH phones had 2.1 and little issues here and there. None of us knew that the DX would get so much better support from their manufacturer than the Fascinate.

That said, I still can't excuse the piss poor support Fascinate users have gotten after the fact. Even with the 2.2 leaks, I still can't truly use it as a music player in my car without having to disconnect it EVERY TIME a call comes in. We need to start a petition or even some kind of legal action over this. It's a legitimate safety concern. Every other android phone I've owned has done this just fine, and so many vehicles have aux input jacks that for this not to work right on the Fascinate is asinine in the extreme. I actually want THAT to work more than I want OTA 2.2 ... :(
 
I still can't truly use it as a music player in my car without having to disconnect it EVERY TIME a call comes in.

I'm sorry - I don't have this problem. Or maybe I just don't understand what problem you are having. I plug my phone into my car's AUX jack and it does a great job of switching from playing music to taking a phone call. Granted, I don't use the Samsung Media Player on the phone - I use WinAmp (now out of Beta and in 1.0 GA) and Slacker Radio.
 
I'm sorry - I don't have this problem. Or maybe I just don't understand what problem you are having. I plug my phone into my car's AUX jack and it does a great job of switching from playing music to taking a phone call. Granted, I don't use the Samsung Media Player on the phone - I use WinAmp (now out of Beta and in 1.0 GA) and Slacker Radio.

Whether I'm playing music or not, if I have anything plugged into the headphone jack of my phone, and a call comes in, I hear NOTHING until I unplug the headphones. The call won't come over the headphones. They can hear me, but I can't hear them on the bluetooth or the phone's speaker, or whatever is plugged into the headphone jack, whether it be a car/home stereo or headphones. And the call won't come over a connected bluetooth device. If I have my bluetooth connected, the INSTANT I pull the headphone jack out the audio comes to my bluetooth just fine. It's always been this way with every setting, ROM, OS version, kernel, radio, etc. that I've ever used. It happens even if no apps are open, no music is playing, and the phone is simply sitting there plugged into something when the call comes in.

Does your bluetooth work with something plugged in when you get a call? And is it a stereo+mic cable you're using, or just stereo minijack only?

Edit: I just tested this on my wife's brand new Fascinate. Does the same thing.
 
...I hear NOTHING until I unplug the headphones. The call won't come over the headphones. They can hear me, but I can't hear them on the bluetooth or the phone's speaker, or whatever is plugged into the headphone jack, whether it be a car/home stereo or headphones. And the call won't come over a connected bluetooth device. If I have my bluetooth connected, the INSTANT I pull the headphone jack out the audio comes to my bluetooth just fine.

I have a couple of thoughts on this:

First - In gerneral, I don't use bluetooth because of the loss of volume compared to a wired connection. In the car, I have to crank up both the phone and the car stereo to MAX volume and the volume is not sufficient for voice calls - so I stopped using it.

Second - The proper headphone or headset to use with the phone comes with a TRRS jack - that's Tip Ring Ring Sleeve. Most stereo headphone jacks are TRS (Tip Ring Sleeve). The additional ring in a TRRS plug is used to handle the mic.

This picture shows the difference between the TRRS jack that you should be using (in black) and the TRS jack (in white) that is only ok when using stereo headphone (listening only - no talk) :
images



The headset you use should have the TRRS jack, an in-line mic and a stereo ear buds like this:

images


The headset adapter I use in my car to connect my Fascinate to my Car Stereo has the TRRS jack, an in-line mic and a regular TRS stereo jack to plug into the AUX jack in my car.

If you are not using a TRRS headset that looks like that (in-line mic and stereo headphone/jack), you need to change your setup. If you try to use a commonly available TRS stereo headset/headphone jack, you will not be able to talk on the phone with that TRS jack plugged in. I would guess that this is most likely your problem.

If you are using a TRRS headset, I have a test for you to try - turn off the bluetooth and try to use the phone in the manner you choose.

I hope this helps.
 
Hobie, thank's for the tutorial on headset, I had no idea about the trrc thing.

SirKonan, I too have the problem with the output of the phone not going over the speaker when the phone is plugged into my aux stereo port. It's rather annoying. =)
 
With AT&T purchasing T-Mobile (of course after Cingular, Edge, Altell & VZ, Nextel and Sprint, and other absorbed carriers) our alternatives are diminishing year after year after year ....

A little off topic but Cingular has always been AT&T in one way or another. Cingular, formed in 2001, was a joint venture of the American landline telephone companies AT&T and BellSouth (formerly known as SBC Communications). The two companies held 60% and 40% stakes in Cingular.

And SBC has always been AT&T in one way or another.
Southwestern Bell Corporation was founded in 1983 as a Regional Bell Operating Company following the break-up of the original AT&T as a result of the United States v. AT&T antitrust suit. The company changed its name in 1995 to SBC Communications Inc. and again in 2005 to AT&T Inc. after it purchased its former parent company, AT&T Corporation.

I don't honestly believe at any point these companies weren't still AT&T they just needed to be another company to avoid anti-trust laws. Although I believe AT&T is getting dangerously close to violating those laws again.
 
A little off topic but Cingular has always been AT&T in one way or another. Cingular, formed in 2001, was a joint venture of the American landline telephone companies AT&T and BellSouth (formerly known as SBC Communications). The two companies held 60% and 40% stakes in Cingular.

And SBC has always been AT&T in one way or another.
Southwestern Bell Corporation was founded in 1983 as a Regional Bell Operating Company following the break-up of the original AT&T as a result of the United States v. AT&T antitrust suit. The company changed its name in 1995 to SBC Communications Inc. and again in 2005 to AT&T Inc. after it purchased its former parent company, AT&T Corporation.

I don't honestly believe at any point these companies weren't still AT&T they just needed to be another company to avoid anti-trust laws. Although I believe AT&T is getting dangerously close to violating those laws again.

Yep, you are correct, I fear.

And back to the sort of on topic topic, thanks for the great tutorial on the stereo minijack, but I have two things to say, neither of which are against you. I suspected that might be the case, but have no device to test it out with the right ring configuration, nor do i wish to purchase one.

1. This will be the FIRST android phone that standard stereo minijack doesn't work properly on. Normal headphones and stereo mini cables have worked on all my other android phones just fine. Now I have to buy a special cable to make this phone work? Sounds very "apple". At the very least, annoying.

2. With or without this cable, bluetooth calling likely will still not work unless disconnected, which is still a bit of a safety concern whilst driving.

The ring configuration I understand as being hardware. It's stupid, but I can forgive that, as different phones do different hardware and connection types. This is nothing new. But the bluetooth issue should clearly be fixed by software. Bluetooth is transmitted digitally to your BT headset. They need to disable the kill somehow, so that plugging something in doesn't shut off bluetooth. Plugging in headphones is most likely going to be for taking calls over them (which the samsung cannot do on regular headphones) or listening to music. If a user goes to the trouble to also pair and connect a bluetooth device, specifically NOT in stereo A2DP mode, or whatever it's called, then CLEARLY it's for taking calls. Like every other android phone I've owned, and even some non-android phones, the bluetooth headset connection should take precedent for the calls. Like I've said before, this is a piss poor "feature" that needs to be fixed, and should be fixable via software.

If there was a third party app I could buy right now that would resolve this issue (with a reasonable price) I would buy it.
 
Perhaps this has been posted (it is a long thread), but dropped by the Target the other day. Maybe they know something we don't:

F22.jpg

F2.jpg
 
wtf really? That's straight up false advertisement. I'd buy it, use it for a week, and take it back. Target would send it back to Samsung who would hopefully turn it sideways and shove it in their collective @sses.
 
It might be falsely attributed to the Fascinate, with the Fascinate name Photoshopped onto a label for another device.

I notice there is a piece of paper covering the rest of the label for some reason.
 
I am not trying to fan flames but this was just taken by my wife at our local Target. As you can see it says 2.2. My question is this, Is this ill informed marketing folk, or an early roll out by the signage department? It would be interesting to here from a lawyer about false advertising.

IMG00415-20110326-1254.jpg
 
Haha those lying bastards...maybe it's coming out incredibly soon to the point where they think they should put it on there?
 
I doubt it. A few times over the past 6 months, the Fascinate was advertised on the Verizon site as a 2.2 device.


True but this is brick and mortar, And then again they may have been and honest mistake seeing ours and US celluar's are the only ones that have not been updated.
 
Status
Not open for further replies.
Back
Top Bottom