Related
http://twitter.com/TMobile/status/25942543501
"An OTA update will be announced soon. Please do not install the kies update due to some known issues." - T-Mobile USA
epakrat75 said:
http://twitter.com/TMobile/status/25942543501
"An OTA update will be announced soon. Please do not install the kies update due to some known issues." - T-Mobile USA
Click to expand...
Click to collapse
Meh, I'm happy with the update. I'll flash the new one when it comes out too, but this is running smoothly for me.
tjhart85 said:
Meh, I'm happy with the update. I'll flash the new one when it comes out too, but this is running smoothly for me.
Click to expand...
Click to collapse
Of course, it's better. However, you'll likely have to flash back to stock 2.1 JFD as I'd expect to you won't be able to update directly from JI5. Even the JI5 update forced people to do that (for example those that were on JI2 / JI4), I'd expect more of the same. There are those who have no problem doing this and that's fine. I'm just warning those who aren't / might not be.
epakrat75 said:
Of course, it's better. However, you'll likely have to flash back to stock 2.1 JFD as I'd expect to you won't be able to update directly from JI5.
Click to expand...
Click to collapse
Fine there are Odin official tmobile images over in bible sticky and take a min to flash
Yea you lose programs settings ...ect but IMO its better to start from scratch when using new updates. And not run into intermittent and compatibility issues like what seems to be going on now with allot of people
but yea this update works great no problems whats so ever for me
epakrat75 said:
Of course, it's better. However, you'll likely have to flash back to stock 2.1 JFD as I'd expect to you won't be able to update directly from JI5. Even the JI5 update forced people to do that (for example those that were on JI2 / JI4), I'd expect more of the same. There are those who have no problem doing this and that's fine. I'm just warning those who aren't / might not be.
Click to expand...
Click to collapse
Thanx, but I sorta needed that working GPS last week, not soon. Besides, "soon" is such an evasive term.
This makes me recollect the June 8th outing of a policy statement by Cole Brodman, Chief Technology Officer @ T-Mobile titled "No Phone Left Behind". It was in regards to assuring owners of the HTC Mytouch3G that they'd be receiving a Froyo update.
Nearly four months later and zip for the MT3G from Tmobile or HTC.
Maybe I'm wrong as my knowledge of timelines is from the inside of my addled head, but I do not believe T-Mobile has had a successful OTA of *ANY* Android phone in their stable this year at all. It's not the most encouraging development. (I do recall the Behold II 1.6 OTA, but it was eventually pulled for bricking phones....and led to me getting my Vibrant for free from T-Mobile before the official Vibrant launch...long story).
Granted, T-Mobile does not develop firmware, so they are at the mercy of the phone manufacturers. Still, if there's any issue that is at the core of Android angst, it is this one.
Just so I don't come across as a troll, I love my Vibrant. Compared to the Behold II I had and every other smartphone I've had it's leaps and bounds ahead of them all. I just get irritated when P.R. and "spin" get out of control...
Of course, this thread was a warning to the people who hadn't yet flashed JI5 / Kies and were still uncomfortable with doing it. Obviously, it's not people who are (already) comfortable. Knowledgeable people are certainly free to ignore and flash away.
This is BS. T-Mobile... how soon is soon? How long have we heard there would be an update to the MyTouch? I cannot and will not wait around for them to OTA anything. I will be very shocked if I get an update in the next month. I know i sound a little pessimistic but who wouldn't?
This is nonsense, installing this update does not prevent me from ODIN to any other firmware. I went directly from JI4 to JI5, so whoever said that I cannot do that is very confused.
grennis said:
This is nonsense, installing this update does not prevent me from ODIN to any other firmware. I went directly from JI4 to JI5, so whoever said that I cannot do that is very confused.
Click to expand...
Click to collapse
That's because you ODIN flashed it.
Kies looked for the JFD product code, then gave you the option to update.
Lol how ironic that they don't want you to flash the firmware because it has 'known' issues. But the firmware on it has bigger issues so hmmm
Sent from my SGH-T959 using XDA App
disturkis4u said:
Lol how ironic that they don't want you to flash the firmware because it has 'known' issues. But the firmware on it has bigger issues so hmmm
Click to expand...
Click to collapse
I can't fault T-Mobile for wanting to try to stem the tide of potentially bricked phones and clueless noobs calling in for support, though.
epakrat75 said:
I can't fault T-Mobile for wanting to try to stem the tide of potentially bricked phones and clueless noobs calling in for support, though.
Click to expand...
Click to collapse
OTA could brick it just as well. Would it be Samsungs first OTA update for Android or the first OTA ever?
mobilebone said:
OTA could brick it just as well. Would it be Samsungs first OTA update for Android or the first OTA ever?
Click to expand...
Click to collapse
True. I'd like to think the probability of bricking over OTA would be lower. Since it would be an official update they'd also likely be / feel more obligated to provide whatever support they wanted to.
mobilebone said:
OTA could brick it just as well. Would it be Samsungs first OTA update for Android or the first OTA ever?
Click to expand...
Click to collapse
Tmobile last update for the Samsung behold ii was pulled for bricking phones it can happen.
Neither Samsung nor Tmobile have a great track record with ota updates period.
Sent from my SGH-T959 using XDA App
Okay so I am running a rom on my samsung vibrant and I heard that froyo is being pushed out OTA tomorrow. What do I have to do to get back to stock so I can receive the update. Or will I even be able to receive the update.
Sent from my SGH-T959 using XDA App
Nice! good question i was wondering the same thing.
That and what if i just rooted to add the mobile ap feature
lewisealy said:
Okay so I am running a rom on my samsung vibrant and I heard that froyo is being pushed out OTA tomorrow. What do I have to do to get back to stock so I can receive the update. Or will I even be able to receive the update.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I would assume odin to stock jfd then to ji6 should be enough to receive the update. I wouldn't try and update from a custom rom (that would almost assuredly result in a softbrick). Also I wouldn't hold your breath. Wait till tomorrow to find out the truth and worst case scenario I'm sure the update will be packaged into a cwm flashable zip or odin tar file soon after release.
I asked the same question in the General section, got a few very good answers.
http://forum.xda-developers.com/showthread.php?t=922008
Bottom line, it is not safe to try to DL the OTA if our phone's somehow even are able to receive them. Some people have said if you are rooted, but have no custom ROM then you might be ok.
TJBunch1228 said:
I asked the same question in the General section, got a few very good answers.
http://forum.xda-developers.com/showthread.php?t=922008
Bottom line, it is not safe to try to DL the OTA if our phone's somehow even are able to receive them. Some people have said if you are rooted, but have no custom ROM then you might be ok.
Click to expand...
Click to collapse
Samsung sent its base 2.2 upgrade to T-Mobile in late November after stating "SOON" back in JULY (4 months is not soon folks, 4 days is SOON) and now T-mobile after being forced to speak-up that they have had it for over 7 weeks. Guess CUSTOMER angry postings got their attention to lie some more, wifi calling has been out for a very LONG time at XDA (keeping with their model not to say the specific amount of time). FIRE THIS GUY and maybe Management will wake-up, if it does not hurt, put fear in the folks deciding, they will not do anything until it effects them. If we keep protesting MAYBE heads will roll and they will stop treating customers so poorly.
Definition of "soon" (adverb) = not long after the present time; quickly. BTW, adverbs often tell when, where, why, or under what conditions something happens or happened.
I really hope they will improve the signal strength!
So if i only rooted (was about to try other roms) will i need to un-root for the update?
I read somewhere that you only need to delete a file or two on / directory to unroot, but cant find that thread... anyone know what im referring to?
Is it just me, or Samsung removed XWKE2 from Kies? Could anyone confirm that?
uskr said:
Is it just me, or Samsung removed XWKE2 from Kies? Could anyone confirm that?
Click to expand...
Click to collapse
KE2 is not on my kies aswell, they must of took it off for some reason?
Maybe a KE3 on the way
Check my thread. They confirmed to me today on the phone that the upgrade can cause serious damage to some phones so they have pulled it.
http://forum.xda-developers.com/showthread.php?p=13885491#post13885491
Although I said it was KE1, I meant KE2...
Strange indeed.
Looks like unbranded xeu guinea pigs are to receive updates quite often.
Good
Sent from my GT-I9100 using XDA Premium App
I just checked the FUS server and it's been pulled, the latest available is XWKE1.
So what kind of damage can it cause? Because I am running on KE2 already
I'm running XWKE2 too and well and it's perfect. I'm guessing it was pulled because of the compatibility issue with Orange's network. If you're worried and want to flash back to XWKE1 then the files and instructions are in a thread in Dev Forum.
Intratech said:
I'm running XWKE2 too and well and it's perfect. I'm guessing it was pulled because of the compatibility issue with Orange's network. If you're worried and want to flash back to XWKE1 then the files and instructions are in a thread in Dev Forum.
Click to expand...
Click to collapse
Not worried, just curious if it is an instant problem or one that develops in time while running KE2. I have no issues either, everything runs well and battery is ok too. Only thing that annoys me a bit is the message in Kies: "This version of the device cannot be updated", But i am sure that will go away when a new version will appear.
btw, I have an unbranded phone from clove.
I connected my phone to kies since you guys says it´s been pulled, KE2 is still availible here
Ah, no wonder. I updated yesterday and after a bit of buggering around to get Kies to see my phone it upgraded smoothly. Only later I found I had KE1 & not 2. Thanks for clearing that up, I'm not going mad after all.
yeh i upgraded to ke2 the other day and now im waiting for ke3, but i have not had any force closes or sudden shut downs.
Also my battery is doing ok, and not the best but ok i watched a 80min stream over wifi on the deadly dir655 router and i lost 16-20% so not good but not bad.
I just tried updating with Kies and XWKE2 is not there.
Maybe its only the debranded one thats not there. Maybe the o2 one is still there
I just updated my phone through Kies a few hours ago. No problems whatsoever.
Just got the new OTA, but still no Jelly Bean. I777UCLL6
IMEISV is now at version 7. No other changes I can see.
ou812bkewl said:
Just got there new OTA, but still no Jelly Bean. I777UCLL6
IMEISV is now at version 7. No other changes I can see.
Click to expand...
Click to collapse
Maybe it fixed the sod problem, one can only hope.
Sent from my Zanpakuto using Getsuga Tensho!
It looks like it updated Kies Air, and now the Facebook app won't open. I haven't noticed any other changes yet.
Hey all,
As some of you have already noted, an update is available for the Samsung Galaxy SII.
The update includes fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions. It also enhances security to protect against malware vulnerability. You will receive a notification on your phone to update.
NOTE - You must have updated to Android version 4.0 to receive notification of the new software update
From community manager on ATT forums:
http://forums.att.com/t5/Android-Di...hutting-off-in-idle-mode/td-p/3247765/page/18
What a complete waste. Sprint just pushed 4.1.2 to their gs2.
cfili said:
fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions
Click to expand...
Click to collapse
By rare, they must mean multiple times a day... hope that finally fixes the problem...
Had my hopes up for JB even though I know the phone will not get it from AT&T.
I guess it is good that they are still trying to improve the phone.
scottwood2 said:
I guess it is good that they are still tring to improve the phone.
Click to expand...
Click to collapse
There's at least as much cya and marketing motivation involved as anything else.
I previously rooted and flashed Siyah 4.3.3 which resolved my issue with the sleep of death. This seems to prevent this new update from installing as when the phone reboots it shows the Siyah boot image and then boots back into the OS, when I unlock the phone it tells me that the update failed to install. I'm not in a hurry to install an update that resolves something I've fixed through other means, but I thought I'd share for those interested.
Notmare said:
I previously rooted and flashed Siyah 4.3.3 which resolved my issue with the sleep of death. This seems to prevent this new update from installing as when the phone reboots it shows the Siyah boot image and then boots back into the OS, when I unlock the phone it tells me that the update failed to install. I'm not in a hurry to install an update that resolves something I've fixed through other means, but I thought I'd share for those interested.
Click to expand...
Click to collapse
You really shouldn't accept OTA updates unless you are 100% stock.
nimper said:
You really shouldn't accept OTA updates unless you are 100% stock.
Click to expand...
Click to collapse
You really CAN'T accept them if you remove system bloat ware or change kernels far as I know.
Hopefully it fixes the SOD problem. I was getting ready to call or go to AT&T and demand I be let out of my contract.
NBA Brawler said:
Hopefully it fixes the SOD problem. I was getting ready to call or go to AT&T and demand I be let out of my contract.
Click to expand...
Click to collapse
That's the best joke I've heard today.
cfili said:
Hey all,
As some of you have already noted, an update is available for the Samsung Galaxy SII.
The update includes fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions. It also enhances security to protect against malware vulnerability. You will receive a notification on your phone to update.
NOTE - You must have updated to Android version 4.0 to receive notification of the new software update
From community manager on ATT forums:
Link Omitted
Click to expand...
Click to collapse
This has been happening to me for the past few months, on more than "rare occassions" though. I never knew what to call it until I saw people on here refer to it as Sleep of Death. Yep, sounds about right. And it would rapidly drain my battery when it happened.
I've successfully updated, so hopefully this will take care of it. It gets VERY annoying! And all the much worse since I use my phone for my alarm, haha. I have my wife's as a backup though.
Anyone pull the modem yet?
Sent from my SGH-I777 using Tapatalk 2
I'm only a curious now, about whether this fixes the SOD. After hours on the phone with ATT and Samsung, and a few factory resets and a new phone, it was still doing it. And each time I called them about it, they'd say they were not aware of such a problem. Anyway, not an issue anymore for me, since going to Task's AOKP ROM, which got me so many better features than an ATT update ever would have - warranty or no.
The only reason why this OTA was pushed was because a ton of users were posting this issue on the ATT forums for 4 months straight. Even then ATT pushes an OTA for 4.0.4 instead of using one of the many 4.1.2 firmwares from Samsung.
c0ldburn3r said:
The only reason why this OTA was pushed was because a ton of users were posting this issue on the ATT forums for 4 months straight. Even then ATT pushes an OTA for 4.0.4 instead of using one of the many 4.1.2 firmwares from Samsung.
Click to expand...
Click to collapse
My understanding is that it is up to Samsung to produce the firmware, and because it's a carrier-branded device, I have a hard time believing that they'd do that unless instructed to.
Really? You think Samsung is the one making the decision? Its really the carrier.
Can someone pull the modem from this update? Pm or post a download link once extracted please.
Sent from my Transformer Prime TF201 using Tapatalk 2
Hi,
Search everywhere and still stuck!
This is issue that I have bee trying to solve on the 'android-rsap' forum, but am completely stuck, so by posting here I am hoping that someone can shed some light on what is going on.
Link: forum.android-rsap.com/viewtopic.php?f=32&t=871
In short, the device is a Samsung Galaxy 2 (XEU), and the bluetooth rsap functionality works fine with 4.0.4 (I9100XWLPT) but when I upgrade to 4.1.2 (I9100XWLSW) it no longer works at all. What is most weird is that it seems to be only my handset that is affected, it does not seem to be a universal issue. :roll eyes: What could be specific to my handset that stops this functionality working as it should?
I have been going back to 4.0.4 and upgraded to 4.1.2. many times now, via OTA, Kies and Odin, same result every time, sadly. 4.0.4 works every time, 4.1.2 has never worked with rsap and my car
What could be specific to my handset that stops this functionality working as it should? I have tried root'ing the handset to do more testing and to try the rsap app from Google App Store, but that has the same issue. Could some of the radio software be wrong? or?
Picture shows Kies upgrade screen and the 4.0.4 and 4.1.2 versions I am getting.
Any hints would be appreciated.
Regards,
J.
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
gastonw said:
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
Click to expand...
Click to collapse
Ok, so with an XEU handset - what version would you recommend?
realist42 said:
Ok, so with an XEU handset - what version would you recommend?
Click to expand...
Click to collapse
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
..
realist42 said:
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
Click to expand...
Click to collapse
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
realist42 said:
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
Click to expand...
Click to collapse
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Repporte Redan
king_below_my_lord said:
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
HI,
Took a little time to get the phone back in order and then to go an do the trace.
Not knowing what I am really looking for, but it strikes me that the bluetooth stack looks to just be giving up...
Regards,
J.
Hi all,
Well, today I managers to briefly borrow another S2 handset with JB on it. This other handset has the same issues that I have, so this must be something in the packaging of the Bluetooth that Samsung did - but I am guessing here.
Any clues would be appreciated, although I think I am fighting a loosing battle here... (works with an S3, so I should go and upgrade! at least chapter now that there is the S4 - but I like the form factor of the S2 better)
Regards,
J
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Well, thanks for looking anyway...
My thinking on this is now that as it works with newer cars and only the older ones that now have issues, it must be a version issue, i.e. the version of the bluetooth stack is not the one it should be. It would be interesting to know if there is a difference in the version of the bluetooth stack and the rsap daemon between the S3 (which works on JB) and the S2 (which does not). Would that tell me anything interesting?
Regards,
J.
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
djshotty said:
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
Click to expand...
Click to collapse
HI,
I was not aware of this, and are you saying this is specific to the S2, so the fact that is works with an S3 on 4.1.2 is irrelevant?
J.
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
djshotty said:
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
Click to expand...
Click to collapse
Well, my issues are with specifically with rsap, not really A2DP, but if it affects the whole stack, this could be an issue.
To illustrate: I have 2 cars, one older, one newer. With the newer car all is well, and it works at is should (as far as I know) The older car was working pretty much with out issues on 4.0.4, but refuses to work with 4.1.2. Both cars rely on rsap.
Not sure this helps, just wanted to illustrate the problem that I am trying to solve.
Regards,
J.
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
djshotty said:
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
Click to expand...
Click to collapse
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
realist42 said:
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
Click to expand...
Click to collapse
That's why I suggested you look at the forum I provided the link for, there are plenty with the 'Phone calls via Bluetooth into car stereo' issue, including myself...