Related
You see, I am having this problem where MMS's sent by someone to someone else are coming from my number and I called T-Mobile's G1 Support Dept and they want to sent me an OTA, but they need me to go into my settings and give them the exact firmware version I read there. Problem is I am jailbroken, so I didn't want to give them that, so I said I was on my cell and did not have another phone around I could use to call them back (which was actually true). So I have the following three questions:
1) Is anybody experiencing the same problem as me? Feel free to comment here or in the original post on HoFo.
2) What does the official build description read? I want to give them that one instead when I call back.
3) If I am jailbroken, is it OK to receive OTA's from T-Mobile? Will I even receive them? Will they install successfully? Will my jailbreak break?
Thanks a lot in advance!
more info needed
if you changed your phone to use the developer keyset (ie: JF's androidmod + modded rc 30), you should be fine even if they send it to you it wouldn't install because your phone now wants updates signed with the dev keys not the REAL tmob/htc keys...
I doubt it would fix your problem anyway, could somebody be "spoofing" the messages with "your caller id info" there are websites that will do this for txt, mms & even voice calls, that would be my guess.
Every once in a while the sms msg centers will just wig out and do wacky stuff from time to time, I have had messages show up hours and even days after they were sent, somebody the otherday msg'd me saying I had sent them a text, I hadn't (i checked sent msgs folder) so who knows it could have been just an anomolly.
bhang
this occurred shortly after the initial launch of the G1. some suggested wiping the phone, but not sure if that fixed the issue. maybe you could reinstall jf's RC30 and then wipe and then restore your info.... might help?
bhang said:
if you changed your phone to use the developer keyset (ie: JF's androidmod + modded rc 30), you should be fine even if they send it to you it wouldn't install because your phone now wants updates signed with the dev keys not the REAL tmob/htc keys...
Click to expand...
Click to collapse
I think that's what I did, so I guess I won't be calling TMo back and I guess I'll have to live with this for now, having people I don't know message me weekly asking, "Who's this?" I just need to make sure I don't send anything compromising if I sent MMS's. *LOL*
bhang said:
I doubt it would fix your problem anyway, could somebody be "spoofing" the messages with "your caller id info" there are websites that will do this for txt, mms & even voice calls, that would be my guess.
Click to expand...
Click to collapse
Not at all. In both cases, the people asking who I was because they received a picture from my number confirmed they know the person who sent it to them and they did nothing special to send those messages, just use the native Messaging application.
bhang said:
somebody the otherday msg'd me saying I had sent them a text, I hadn't (i checked sent msgs folder) so who knows it could have been just an anomolly.
Click to expand...
Click to collapse
This sounds exactly like what I have been experiencing, only I have only seen it happen with MMS's, not SMS's.
korndub said:
this occurred shortly after the initial launch of the G1. some suggested wiping the phone, but not sure if that fixed the issue. maybe you could reinstall jf's RC30 and then wipe and then restore your info.... might help?
Click to expand...
Click to collapse
I never saw reports of this before. Guess I missed them. See my response above. I will just wait and see what happens. Most likely, this is TMo screwing up and once enough people complain and TMo realizes the liability they have in their hands, they will move and fix this. Besides, I just saw in one of the threads that we should be able to install Cupcake, so I will explore that or wait for the next jailbreak update.
this was happening to me as well and it happened to be my father's iphone account weird, but yes i get really scared when i send my gf stuff now lol from my gmail account. i grabbed his phone to make sure he didn't see anything and just make sure it addressed to the right person when you send lol
i also input my contact into and when my father texts me (yes he just learned), the sender is my email address....odd
idk how to change it....
hbguy
I insist. 611 from your G1 and complain. T-Mobile needs to get the pressure to move enough resources to address this.
This same thing has been happening to me. I am using an iPhone with SwirlyMMS. I did notice that when people responded to me with a MMS asking me "Who is this?", according to my.t-mobile.com my texts were originating from India or Russia, but were from people's real cell phone numbers in the US. I know this, because one of the numbers in question called me and they were from NYC.
this has happend to my girlfriend a few months back and she has a tmo sidekick 3. Also, about 8 months ago my roomate was getting phone calls from all over the U.S. from people trying to reach other peole after about 10 phone calls i called his phone from mine (tmo wing at the time) and it went to someone else. I then hung up and tried a few minutes later and it went to someone different. He called t-mobile and they said they havnt recieved any other complaints and told him to restart his phone. He did, it did nothing. but over the next few days it seemed to fix itself, of t-mobile had found the problem. But back to the mms, My girlfriend now owns a G1 and just a few days ago i sent her a picture of my dog and it said it came from someone else. we both have G1's mine has root hers does not so i dont think it has anything to do with your phone.
this happened to my wife and I right around x-mas and it only lasted a few days. she relied to a text I sent and it went to NY, 'cause they called back and told us where they were from... and they had t-mobile. It quit after a couple of days and haven't had a problem with it since then.
http://www.engadget.com/2010/09/22/samsung-captivate-gets-gps-fix-other-galaxy-s-versions-wait-pat/
"An update to improve the Samsung Captivate's GPS performance is now available. Captivate customers will receive a notification on their device that an update is available and will simply need to download the file to update their phone. The updates will be pushed to customers' devices over the next few weeks.
The update for the Captivate will also improve additional device functions, such as media scanning time, add the full version of Quickoffice and address Microsoft Exchange 2003 policy support."
Fingers crossed, that this already hasn't been leaked, torn apart, and found useless...
Its probably the JH7 OTA that they started rolling out yesterday, not a new separate fix...has anyone that received the OTA updated noticed any difference on the GPS?
I saw a few ppl that got the update say the GPS is the same as before.
I wouldn't trust Engadget for anything GPS related. They botched Galaxy S reviews so many time on the GPS topic:
1. They said GPS works just fine when they review Captivate and Vibrant.
2. They said all you need to do to fix the GPS is just turn on the 'Use Wireless Networks' in Location and Security settings because Samsung told them so.
3. They said EPIC 4G has GPS all fixed out of box, again because Samsung told them so.
4. Now, again, they claim the latest JH7 update fixes GPS because, again, Samsung told them so. Never mind AT&T itself never mentioned any GPS fixes in its release notes.
Yea, I re-read the update discription that was posted on a couple of other android sites, and it sounds just like the JH7 ...
Damn
I am downloading and updating now.. will see.
Yes, they are wrong again. Well, I wouldn't put the blame on them 100%, since I believe that letter came from Samsung PR (who know nothing tbh).
andy2na said:
Yes, they are wrong again. Well, I wouldn't put the blame on them 100%, since I believe that letter came from Samsung PR (who know nothing tbh).
Click to expand...
Click to collapse
Yes, it is bad jounalism. What happens to 'trust but verify'?
Yea, I read the same quote on a couple of different sites outside of engadget...
ipxnsv said:
I am downloading and updating now.. will see.
Click to expand...
Click to collapse
I just downloaded and updated then said "Update is failed." Is this because I'm rooted?
Engadget does suck. All those aggregate tech sites suck at everything, but stealing good sites articles.
I am happy about quick office though. I really hope custom roms don't rip it out as bloat.
This site is claiming that the update DOES fix the gps, and has video:
http://www.careace.net/2010/09/21/s...te-being-rolled-out-this-week-starting-today/
I'm not rooted, am stock and update failed. Won't resume either, says no firmware to update if I try that.... so it may be something wrong with the update.....
compuguy1088 said:
This site is claiming that the update DOES fix the gps, and has video comparing before and after:
http://www.careace.net/2010/09/21/s...te-being-rolled-out-this-week-starting-today/
Click to expand...
Click to collapse
The site says they are doing more testing and update the results by 2PM. The video only shows a GPS location fix by standing still, not driving around. My JH7 can do that w/o problem either but when driving, it is all over the place.
What is the csc version after the update?
I have had jh7 for over a week, it is an improvement but not a fix
Sent from my SAMSUNG-SGH-I897 using XDA App
To be honest, my GPS was working when I first got it.
And yes, it is jh7. Which has bad ass GPS when I use it.
klloyd said:
I'm not rooted, am stock and update failed. Won't resume either, says no firmware to update if I try that.... so it may be something wrong with the update.....
Click to expand...
Click to collapse
I unrooted to give it another shot and just learned of the "check once/24hrs" deal. Bull****! Thanks ATT
I am downloading now. It is taking quite a while (out in the wilds of KS we only get EDGE speeds). Does anyone know if this will work if I am rooted? I didn't un-root, and the last time I did a backup was Saturday. I suppose I won't lose much if it craps out.
mine is stuck at "Communication in progress" it just loads....
If anybody has successfully done the OTA update, can they please post the stock JH&GPS settings from the LBSTEstMode menu?
Has anyone tried Keis?
I have email both Samsung and ATT along with live chatin with both also. Email responces for both Samsung and ATT have been the same both times to an extent. What i did learn was with the live chat. ATT's live chat although pretty much the same as the email. The tec i talked to couldn't tell me when but he did shead some light on something which i didn't know. According to the tec ATT really doesn't have anything to do with the release and update. Here i thought from everything i have been reading it's been ATT draging their feet thats not the case. So Got a responce from Samsung asking pretty much the same thing i did in the ATT email. Asked when the 2.2 android update would be out. Coarse got back the same as i normaly did stating their working on bringing the best experence with the upgrade and download that they can. So it's coming. What i also did was added how the ATT tec said ATT doesn't have anything to do with the release and when it will be out. Samsung didn't correct me about this. So send all emails to Samsung maybe they will get tired of all the questions and be able to give us a time frame.
The response you got from Samsung is the same they have been throwing out for months. The AT&T reps are trained to always say it is not their fault.
Think what you want, but Samsung passed Froyo build to AT&T a while back, and AT&T is sitting on it. We have a Beta from October to prove that - it has all the ATT&T bloatware.
Unless you talk to a manager that knows about software releases (not a customer service person) you will only get canned responses.
Like every topic of this nature that has been posted and what the person above me said most of the people you talk to make it up as they go. At&t us the culprit behind the laggy release but of course they will tell you otherwise. What is the difference between a rogers and att phone that makes it samsungs fault?
Sent from my SAMSUNG-SGH-I897 using XDA App
MagillaGorillaX said:
I have email both Samsung and ATT along with live chatin with both also. Email responces for both Samsung and ATT have been the same both times to an extent. What i did learn was with the live chat. ATT's live chat although pretty much the same as the email. The tec i talked to couldn't tell me when but he did shead some light on something which i didn't know. According to the tec ATT really doesn't have anything to do with the release and update. Here i thought from everything i have been reading it's been ATT draging their feet thats not the case. So Got a responce from Samsung asking pretty much the same thing i did in the ATT email. Asked when the 2.2 android update would be out. Coarse got back the same as i normaly did stating their working on bringing the best experence with the upgrade and download that they can. So it's coming. What i also did was added how the ATT tec said ATT doesn't have anything to do with the release and when it will be out. Samsung didn't correct me about this. So send all emails to Samsung maybe they will get tired of all the questions and be able to give us a time frame.
Click to expand...
Click to collapse
Process =
1. Samsung readies firmware and gives to the carrier. ATT likely has had the firmware in hand since late November (the same time samsung gave it to T-mobile).
2. generally takes carrier 2-3 months to customize the firmware/test/lockdown features/install their bloatware etc. ATT definitely holding it back at this point but i think it will arrive sooner rather than later. I would say Verizon and ATT both got their firmware at same time as t-mobile they have just taken longer to finalize the update for the push. In ATT's case i would suggest it all hinges on them trying to lockdown the native MobileAP feature so you have to use their App with paid tethering.
2 cents.
10 char
Thread reported for lock because of no useful information.
flashman2002 said:
Thread reported for lock because of no useful information.
Click to expand...
Click to collapse
Seriously. What's not unhelpful is out of date.
IT is getting increasingly galling at this point. I love how when you write to Samsung and ask, they say they can't provide an answer because it would lead to speculation and inaccurate information. But of course it's exactly yhe opposite that is actually true...
There is zero point to speculating/complaining about the lack of an official Froyo update. I'm not saying I don't sympathize, just that it's non-productive.
Samsung won't speculate because AT&T is sitting on this... here is more proof:
http://www.wireless.att.com/answer-...ncharset=UTF-8&solutionId=KB115196&isSrch=Yes
The title says it all "Send, Receive, or Delete a Picture, Audio or Video Message (MMS) with the Samsung Captivate (i897) with Android 2.2"
And Samsung's tweets to me confirm it... when pressed - they specifically said 2.2 had not been released to "Captivate Users".
I have always maintained that AT&T is sitting on the release. Why, I am not sure, but the fact that numerous support pages reference 2.2 indicates that they geared up to push it out a while ago - that means stable builds have been available or they would not have made support pages that have very specific screen shots.
I sent them an email a couple of days ago explaining crap thats going on with the phone and how Froyo 2.2 would from what i understand fix most of the problems etc etc. I just wanted to try again to find out about a date. Well i got an email back from tec. upport saying they are glad to announce that the 2.2 update IS available and to call their 800 number for help if i had problems installing. but clicking on the link just brings me to the old FAQ page that they took down. Come on Samsung get a freaking clue. I don't understand why they would send this out and not be true?????
(so maybe things will be rolling out today then because after rereading email i noticed their central time which is 3 hours behind me. So right now my time there still closed) Fingers crossed
Ok so just got of the phone with Samsung. Acording to them and the information they have in their office Froyo 2.2 IS OUT but because theres a problem with the site we don't can't download it yet lol Samsung needs to really get an Fing clue.
I'm pretty sure you need to install that with Kies Mini if it is, indeed, available.
JRd1st said:
I'm pretty sure you need to install that with Kies Mini if it is, indeed, available.
Click to expand...
Click to collapse
Nothing showing up on Kies Mini eather. So again am hoping that things will start rolling out as soon as they open at 9 central time.
I saw another post at AT&T official forum about multiple Samsung reps claim the 2.2 for Froyo is avialable and directed to the same link. Looks like Samsung already trained or released information about Captivate 2.2 release internally, a bit prematurally. So, it seems our UCKB1 ROM will be the official ROM after all. It is just waiting for AT&T to give the final nod.
<--- not holding his breath... Plus, the more I think about it, at this point... What's the point? I mean, 2.2 is rapidly aging and I'm not aware of any newly released devices coming out with 2.1 anymore - They've all got 2.2, which means that 2.3 is the next step.... and with the excellent development we already have, running stable 2.2 is already a reality! I want the update just so the companies are held to their promises, but as for an official 2.2; I'm not going back to ATT bloatware and half ass GPS.
Tried OTA update and it just hung......
I tired to go into media hub yesterday just to see if i missed it being fixed and it hung on checking for update. Checked phone for OTA and it also hung on checking for update. funny thing is about 4 days ago everything was working just fine. Im about to get on the phone with ATT and ***** about the email and when samsung opens and nothing happenes today will be on the phone *****ing about sending false emails to people.
So basically Samsung has just changed the lies from "It will be out soon" to "It's out now but you can't have it"! Way to go Samsung!
UCKB1 has a working media hub. If I were you I'd just install that. It'll probably end up being the official build anyhow.
Bunch of crap Samsung is. wow.....
Just got done talking to live support. what a joke. i have a dam email saying it's out. if you call and talk to someone they say all the info they have says it's out but live says its not and gives you the say crap as before about no info right now. Someone over there needs to get their head out of their ass and get a CLUE.
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?
Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.
The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box
ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S
3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.
I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.
I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny