Ok I cant believe this phone doesnt do something so simple. My big question is if I am on the 2.2 update that ATT shoved out will Vlingo work for voice dialing. I have a Jawbone Icon and it wont work. Do I need to root this thing to get the ATT blocks off of it?
When did AT&T shove out 2.2? No one will know till it does come out however the video on vlingo site shows the dude using it.
Sent from my SAMSUNG-SGH-I897 using XDA App
The guy at the ATT store downloaded it for me and said it was the 2.2 update OTA to fix the gps issues people were reporting not Froyo. Sorry should have made that clearer. According to the the phone it says 2.2 not 2.1 also so WTF am I running
jpinks said:
The guy at the ATT store downloaded it for me and said it was the 2.2 update OTA to fix the gps issues people were reporting not Froyo. Sorry should have made that clearer. According to the the phone it says 2.2 not 2.1 also so WTF am I running
Click to expand...
Click to collapse
If you don't mind...scroll down from where your reading this 2.2 all the way to the bottom..What does it say for the Build Number ? Also..which AT&T store did this for you ?
Mac
jpinks said:
The guy at the ATT store downloaded it for me and said it was the 2.2 update OTA to fix the gps issues people were reporting not Froyo. Sorry should have made that clearer. According to the the phone it says 2.2 not 2.1 also so WTF am I running
Click to expand...
Click to collapse
2.2 is Froyo. If you're running 2.2 (JI6), then you're running the leaked rom, which is (in my experience) extremely buggy. We don't know yet what the official 2.2 release will be like, or what it will support. If you're having bad luck with some feature that is supported but buggy, I would flash back to JH7.
From @Samsungservice on Twitter
"DL09 OTA update available for the Fascinate! http://bit.ly/ggkwUY Please check out the PDF for details! Note: Dial *228 after update!"
Sorry, my bad. I read the acclaim and fascinate as one. The fascinate is getting an OTA right now though.
WTF??
We are the last?!
I will never own a ATT phone anymore.
Worth the extra money to get whatever you want that works.
Where does it say this is Froyo?
http://www.examiner.com/gadgets-in-...inate-gets-an-update-wait-for-froyo-continues
http://www.ubergizmo.com/2011/01/verizon-samsung-fascinate-havent-gotten-froyo-love-yet/
http://www.androidcentral.com/samsung-fascinate-mr-update-released
Enough all ready?
it's NOT froyo...
Ugghhh people really need to read before posting stuff. Knew it was going to be someone jumping the gun before I even clicked into the thread.
tjsooley said:
WTF??
We are the last?!
I will never own a ATT phone anymore.
Worth the extra money to get whatever you want that works.
Click to expand...
Click to collapse
How exactly is AT&T last when no one else in the US with a Galaxy S phone has official Froyo?
DL09 = Eclair 2.1.
That means Facinate will not get Froyo until couple months later if get one at all. Poor Facinate owners.
http://www.androidpolice.com/2011/0...pdate-to-allow-sideloading-on-select-devices/
Here come the bricks. Will you go back to stock just for a sideloading ota update when you can do this on any custom rom?
Caution swyping! Read at your own risk.
According to 99% of the threads here on XDA, if you even look at your Cappy the wrong way you run the risk of bricking it. lol
cappysw10 said:
Here come the bricks. Will you go back to stock just for a sideloading ota update when you can do this on any custom rom?
Caution swyping! Read at your own risk.
Click to expand...
Click to collapse
KonaZXIII said:
According to 99% of the threads here on XDA, if you even look at your Cappy the wrong way you run the risk of bricking it. lol
Click to expand...
Click to collapse
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Will this be rolling out to Eclair users or just Froyo? And if you're on Eclair will this OTA include the Froyo upgrade? Anyone gotten this OTA yet?
umm...? if you receive OTA updates, you will already be OTA updatED to froyo. no?
so if you are still on eclair... umm.. wait!.. why would anyone still be on eclair?
oh... im scared of flash video and voice search... lol
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
I was (mostly) being facetious there. I've been flashing and modding my phone for a while now and it has been next to impossible to hard brick.
well dont say stuff that can confuse the noobs please.
Anyone actually receive the update yet? Anyone who did, straight stock, rooted, any other notable differences?
Can we be connected via Wifi? Need to be on data network?
I just tried to see if it was available to me... nothing at 1pm in Atlanta
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
AT&T could f#@% up a wet dream. This could also be a plot to void your warranty. "You loaded an unauthorized app which caused your trouble, not our problem. Oh, btw, we'll sell you an Infuse cheap."
Caution swyping! Read at your own risk.
Can at least one post in any forum I've looked at site a source or show something more believable then one crappy blurry pic of a random computer screen. Heck why is it not even the whole screen? What is that a pic of, other then something somebody made up who was not even good enough to use photoshop?
TRusselo said:
umm...? if you receive OTA updates, you will already be OTA updatED to froyo. no?
so if you are still on eclair... umm.. wait!.. why would anyone still be on eclair?
oh... im scared of flash video and voice search... lol
Click to expand...
Click to collapse
Froyo was never rolled out OTA was it? Thought it was a Kies update.
I'm helping my extremely tech-illiterate friend with her Captivate and I want to figure out exactly what the details are of the various updates so that I don't scare her with anything
I'm from I9000-land and I flash every couple of days But I'm a bit unfamiliar with the Captivate scene.
No they tried an OTA but it ended up bricking alot of devices due to no 3 button support. To be honest if it is not a kies update I would never touch it. To many things to go wrong with OTA. But we will see. It will most likely be 2.2 update
my question is would it cause any issues on a rooted stock froyo ?
I was just on-line with the Technical Support chat via the AT&T site and I asked the rep if she could confirm that this OTA update was even available. And she replied that she doesn't even see this update for the Captivate on her system. Not sure what's true or not...
I hope it's here in time for free plants vs. zombies, May 31st! I don't want my wife to have to pay. (I already have the Amazon Appstore on mine, of course).
ScottyNuttz said:
I hope it's here in time for free plants vs. zombies, May 31st! I don't want my wife to have to pay. (I already have the Amazon Appstore on mine, of course).
Click to expand...
Click to collapse
Just grab it from the Amazon website and then once AT&T allows sideloading you can install the appstore and then install the game on your phone.
At least ATT is going in the right direction, however, they need to update all their android phones to have hsupa also then having a stock phone is not so bad but I have been able to sideload with out using a computer since getting the phone enabling non market apps since the first day on my captivate *Launch date*. I have been using HSUPA ever since I started using Custom roms after the first froyo leak was released by DG.. So nothing to really effect me at all with this news, but it is good that any future phones released will have at least this enabled..
Cheers,
Charlie
dmnall said:
At least ATT is going in the right direction, however, they need to update all their android phones to have hsupa also then having a stock phone is not so bad but I have been able to sideload with out using a computer since getting the phone enabling non market apps since the first day on my captivate *Launch date*. I have been using HSUPA ever since I started using Custom roms after the first froyo leak was released by DG.. So nothing to really effect me at all with this news, but it is good that any future phones released will have at least this enabled..
Cheers,
Charlie
Click to expand...
Click to collapse
+1
they may be late to the party but at least they deserve a lil love for moving in the right direction and at least in one regard listening to their customers. Now if they would just be smart enough to realize/admit charging for tethering is a scam and recognize the marketing bonanza "Free to Tether" would be.
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
Don't tell that to other members of the Galaxy S family. OTA updates have occasionally done worse.
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
I agree with you. At this point I'd be happy with some sort of update from Samsung/T-Mobile. Even if they just said "we're still working on it" and gave no ETA at least we'd know they hadn't forgotten about it.
If the Blaze Q whatever the hell they've decided to call it launches here in a few weeks with ICS and we still don't get the software I will be ticked.
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Sent from my Samsung Galaxy S Blaze.
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Sent from my SGH-T769 using xda app-developers app
dr4stic said:
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
Click to expand...
Click to collapse
I completely agree with you. To be honest, I am already pissed off that they still havent released it. When I got this phone, T-Mobile promised I was going to get an ICS update in July. Yeah, so much for that. At the very least they could acknowledge our presence and let us know that they havent forgotten about us
Chitown021 said:
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Click to expand...
Click to collapse
The problem is the kernel and libraries specific to our hardware. We have to have a working kernel and libraries before the rest of the rom can come.
I'm not sure why people thought the Blaze Q would've been a good thing for us because unless the hardware was identically similar (which no one had any proof that it was), the releases for that phone would've been useless for ours. The fact that it's now coming with a 720p display (I would've stayed with my Blaze 4G if it had that), and a keyboard tells me that there will be PLENTY different between the phones.
Hardware-wise, the T769 (Blaze) is EXTREMELY similar to the T989 (T-Mo SGS2). How similar you ask? In the original kernel configuration file for the T769, the options are set to build it as a T769 AND T989. There are a few ifdefs that exist purely to stop little snippets of the T989 code from taking effect.
I worked on my own time to try and hack together a kernel from the released sources for the T989 for ICS. Porting specific code from the T769 sources to try to come up with something that worked. Here's the problem: it was stressful and thankless, and at the end of it all I had a kernel that would compile and not boot. No one collected anything to help me attempt this and I was getting tired of having a non-functioning phone that pissed me off. So I ordered me a Galaxy Nexus. I received 2 in a row with screen issues and ended up returning them. I figured I would return to my efforts with the blaze, but at that point I was used to the big phone with a beautiful 720p resolution... so I shelled out the money for a GS3.
I have thought of returning and making a second attempt to port the kernel, and have actually started setting up to do just that. I think I made some mistakes my first time around, so the second time might actually work. But it is A PAIN.
chjema said:
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Click to expand...
Click to collapse
You're right, it isn't... but it's the last time I saw this community bug an outside source for something, aside from buying a couple of guys a phone
Yeah, a 720p screen would have been nice... thanks for the detailed explanation.
I still find it comical that my old HD2 is on the verge of having a fully functional JB rom but my brand new Blaze is still stuck on GB.
Honestly if I could've afforded it I would have probably gone the Nexus or S3 route but given my limited funds and needing to cover two phones (wife needed an upgrade) I thought this was the best value ($30 upgrade cost at Target).
Sent from my Samsung Galaxy S Blaze.
Yes lets please do this.
T-Mobile hasn't updated their page for a month now, and that was for the Gingerbread update they released when they could have been making headway on ICS. I can't find out how to submit any new pages, but I can see two requests for an update that were a couple months old (click on the link, then read on the right side in section "Incoming Links") source = http://support.t-mobile.com/docs/DOC-4182
I went to Samsung's page about ICS updates, and rated it "very dissatisfied," informing them they should have supplied target Year and Quarter (i.e. 2012 Q3) at the minimum, but preferably a specific month. source = http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755
Let's continue to put pressure on these assholes, or they will sweep us under the bus while they pursue development of the Samsung Galaxy Supernova 4G Touchwiz Xtra 4.1.
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Dr4stic
If you need want help, testing, anything.let me know of beer more than happy to help.. we need to get ics to this phone
Sent from my SGH-T769 using xda app-developers app
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Click to expand...
Click to collapse
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
I'll be the first to admit I've become a bit jaded because of my experiences with T-Mobile / Samsung and the Samsung Vibrant.
I heard promises about updates to that phone - they even set dates and pushed them back and back and back and finally... nothing.
If anything I think the release of the Blaze Q is a strike against us because our phones are now the "out dated" version of the Blaze and why put development hours into an "old" device.
I'm happy that I have a fully functional phone as it is now (the Vibrant never really had a fully working GPS). An update would be nice but I wouldn't lose any sleep over it because honestly, you may just be setting yourself up for a lot of sleepless nights.
Oh, and on the Vibrant Forum they started a twitter campaign #NeverAgain demanding the promised upgrade or they would never use T-mobile or Samsung again. No one listened.
I know this all sounds cynical but I've seen this show before.
Edit to add: If memory serves correctly this was also the case with the Behold on T-mobile.
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
L7ChrisL7 said:
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
Click to expand...
Click to collapse
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem.
Click to expand...
Click to collapse
What happens when more "cool new apps" are released to the market that require Android 4.0 API's or better? Chrome immediately comes to mind, and there are others with many more on the way. What happens 4 months from now when you are only 6 months into your 2 year contract and you're wondering why you can't realistically run things on your phone that has 1 gig of ram and a dual-core 1.5ghz cpu?
And honestly, btw... I had a myTouch 4G running CM7 that felt miles faster than my blaze. The samsung crapware is not only bloated, but breaks the system in a number of places. You can see this in the fact that you can't have a scrollable wallpaper, or that the system doesn't understand all the loop points in ringtones that work properly in other phones. I can't tell you how frustrated I get by an unlock and/or answer mechanism that can't track my fingers in real time like something as simple as CM7 does.
And don't get me started on the underutilisation of the video hardware.
AwesomeTurtle said:
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
Click to expand...
Click to collapse
No, this phone was released with a promise. When it was released, ICS had been out for 6 months or more, and I'm sure the OEMs had access to the system and API's well before the official release. By the time ICS is released for our phones (IF it is released for our phones), JB will have been out for several months.
This is a matter of support and broken promises. I am NOT just whining. I was sold a phone with a promise of ICS and it has NOT been delivered, and at this point the time has gone beyond reasonable.
If we don't make noise now, it WILL be forgotten and you're going to end up with a phone outdated well before it's time.
dr4stic said:
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
Click to expand...
Click to collapse
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
L7ChrisL7 said:
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
Click to expand...
Click to collapse
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
dr4stic said:
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
Click to expand...
Click to collapse
Well cant you decompile a kernel? or maybe if i get the source of both devices i can use the code to compile a new kernel... hmmm all stuff to try. but compiling a kernel takes a while i think ill update my PC first haha. Im not necessarily worried about the other drivers not working, i just want to make progress, or at least help us make a push in the right direction. Im sorry if im being too optimistic or noobish, i just want to learn what people have and havent tried, so i dont waste my time on what has already been done.
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
here's a thread we can vent at!
spartanerik said:
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
Click to expand...
Click to collapse
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
anactoraaron said:
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
Click to expand...
Click to collapse
http://support.t-mobile.com/people/tmo_erica
Try sending an email to [email protected] and ask (nicely) about a status update on the ICS update for our phone! I just sent one, and hopefully if we send enough we can get some traction