Database Info

At&t Message

*note I am posting in my BIL's account because I am on his computer*
I am currently running the original leaked FROYO rom that was posted here. Today I got a message from at&t saying they were providing a free update to my phone....
Got any ideas what this might be?.... I had already installed jh7 before...

Yeah, this happens... They sent that out with the last update for 2.1, and if you bought your phone sometime afterwards, you'll eventually get a (few) texts about it...
When Froyo is released, I'm sure you'll hear all about it, so don't worry about that text.

I've just learned to ignore that text message, I figure if Froyo comes out for the Captivate I'll probably read about it somewhere else first.

I got the same message from ATT
Froyo 2.2 Rooted I897UCJ16
In my case there was a time where I saw a sync Icon next to the Wifi Icon on top right which was bit unusual I thought. However when I pulled the tab to see what it was, nothing showed up but icon remained.
The text came from 1111487602 and it came to my SIM Card Phone # directly which a puretalk prepaid sim

malicenfz said:
I've just learned to ignore that text message, I figure if Froyo comes out for the Captivate I'll probably read about it somewhere else first.
Click to expand...
Click to collapse
Just as I am learning to ignore the daily new thread posting about it.

polarbee said:
Just as I am learning to ignore the daily new thread posting about it.
Click to expand...
Click to collapse
Haha!
Sent from my SAMSUNG-SGH-I897 using XDA App

Yup So have I lol. I have blacklisted the number cause I got it 4 times in the same day and I was like Yeah ok....Not gonna happen lol.
Thread closed

[Q] disappointment after disappointment

First off I would like to say hi and thanks to everyone on here, this forum rocks! But I honestly feel my Mesmerize has been a bigger disappointment to me than my Behold I had with T-Mobile! I switched to US Cellular and this phone cause they have better coverage where I live, and I wanted a phone I could customize so i wouldn't have the same thing as everyone else lol. I did the 2.2 update as soon as it released, toyed around with some of the other firmwares on here and what not before it was available, but started having the problem where my phone wouldn't notify me of incoming calls. So i used the files on here to go back to 2.1 using Odin and rooted for future possibilities, I receive every call now. But onto my questions lol, I was wondering if anyone on here has found a way to fix the incoming call problem on 2.2 that i had? How can I get voodoo onto my phone the way it is right now? I have tried every way described on here and through searching, keep finding dead links, phone will not update zip from sdcard on reboot, have tried numerous files that way! If you guys could post some links that would help me out with my problems, to files, and what not, that would be greatly appreciated. Sorry for the long winded post, just tired of searching everywhere and not getting anywhere, thanks!

Honestly, there *is* a thread that covers what you're after; it's bde's How to Customize your Mesmerize thread found Here. I should probably get on him to update the "First get Stock Froyo on your phone" link, because it does have an old link last time I checked. That's about the only one that I know of, every other link works.
Above all, make sure to always wipe your cache (any "Wipe ..." option you can find, one is under Advanced, except for Battery Cache) once you get Clockwork Mod (CWM) Red Recovery installed before you flash a ROM. It really does make things flash better, fewer FCs, and so on. There are times when you can get away without it, but in that event it's best to assume things will be glitchy unless they aren't. From the brief information you gave, I'd suspect that's what happened to your phone.
Best advice anyone here will give you: Read read read. Following that, read some more. Some people can only learn by doing, sure, but become as intimately familiar with the processes and terms as you can.
I suspect I'll do this a lot, but check out the Glossary in my signature, and read through the whole post. It should give you all the little "this goes here, but doesn't work there" kinds of pointers you need, all in one place.
Good luck! Hopefully from here on out, you can really enjoy your Mesmerize, and welcome to the forums!

Hi, thanks for the reply. I do need to read through the glossary post you put up a little more thoroughly, just kinda glanced so far LOL. I also have checked out that link as well, but honestly I won't go back to froyo, not worth the missing calls to me when my phone is how I make a living at the moment. Just mostly interested in finding a lagfix and the voodoo sound for 2.1.
Sent from my SCH-I500 using XDA App

mikef509 said:
Hi, thanks for the reply. I do need to read through the glossary post you put up a little more thoroughly, just kinda glanced so far LOL. I also have checked out that link as well, but honestly I won't go back to froyo, not worth the missing calls to me when my phone is how I make a living at the moment. Just mostly interested in finding a lagfix and the voodoo sound for 2.1.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Missing calls has never been a problem with froyo as far as I'm concerned. Uscc did realease their official version not long ago, getting 2.2 by that means should be flawless.
Sent from my SCH-I500 using XDA App

The US Cellular froyo upgrade is what i used and had all the problems with not being notified of my incoming calls, its a very well known problem from what I have found out by searching on google, took my 4-5 times of calling me before my phone rang, and he is with US Cellular as well
Sent from my SCH-I500 using XDA App

As a quick note, the missed calls thing is actually a Samsung issue that is known and is/was an issue on both 2.1 and 2.2 that is being worked on and a new firmware release is coming soon from what I have seen. I'm hoping to have more on that soon.
Sent from my SCH-I500

HTC Customer Support Fail

Before the MR2 update came out I sent their customer support an email complaining about the random reboots and data connectivity being crap and about gingerbread and they gave me the typical generic answer we are aware of the issue and working on giving thunderbolt owners gingerbread soon and they were sorry for the problems with my reboots. So far since the MR2 update I have had no reboots and my data connectivity has been better but after hearing the Droid Incredible 2 got gingerbread today and the fact this phone came out after the thunderbolt I sent them another email in regards to this and the fact we have heard litterally nothing on their end about any status with the gingerbread update or when we could possibly see it and they responded
The Thunderbolt update is available to be pulled to the device. To pull the update go to Menu> Settings> System updates> Firmware update. If you are unable to update the device please wait for the FOTA update.
Sorry for the inconvenience.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number xxxxxxxxxxxxxx.
Sincerely,
Brian
HTC
He was refering to the MR2 that just came out, nothing about my question on gingerbread or how the Incredible 2 got it before the thunderbolt. Fail

smh I didnt know Droid Incredible 2 came out after the TB. Smh its like htc or Verizon dont give a **** about this phone

Perhaps you would have gotten satisfaction if your message was properly punctuated, clearly written, and presented in some organized fashion?

My message to them was accurate, and clear and I pretty much asked them about gingerbread and how the Incredible 2 was able to get it before thunderbolt when the incredible 2 came out after the thunderbolt. I also mentioned how they haven't mentioned anything in regards to the thunderbolt or given us at least a status update. From other forums I've read they just give the standard We are excited about the Operating System 2.3 Gingerbread update coming for Android, and while HTC will definitely have some phones running this Operating System, we do not have a specific time but it will be soon and what I posted was the response I got back from them.

What does it matter? #FOOL
Sent from my ADR6400L using XDA Premium App

bob miller said:
My message to them was accurate, and clear and I pretty much asked them about gingerbread and how the Incredible 2 was able to get it before thunderbolt when the incredible 2 came out after the thunderbolt. I also mentioned how they haven't mentioned anything in regards to the thunderbolt or given us at least a status update. From other forums I've read they just give the standard We are excited about the Operating System 2.3 Gingerbread update coming for Android, and while HTC will definitely have some phones running this Operating System, we do not have a specific time but it will be soon and what I posted was the response I got back from them.
Click to expand...
Click to collapse
Ah, I see. I assumed that your OP was verbatim. I couldn't really read it, as it had one period for about 15 different sentence fragments.
As a beleaguered technical support engineer, I had sympathy and could understand how some core points would have been ignored.
Not intended as flamebait. Your response above was more digestible.

brisdaddy1207 said:
What does it matter? #FOOL
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
And this contributed what exactly to this conversation? and you do realized this is a forum and not twitter?

[Q] voice search bug but no OTA update yet

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

Update?

I have a wifi only Xoom and it is Rooted. My question to you is, since it is rooted I obviously cannot be updated via OTA, it keeps showing up that I need to update. I cannot turn off automatic update when I go to about then update. Its really no big deal tbh, but it is really flipping annoying and just keeps coming back...
I would really appreciate some feed back and hope someone knows how to fix my problem. Thanks XDA!!!
Sent from my Xoom using xda premium

Assuming you have CWM installed, you could follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1575393
Install the update via CWM and get to 4.0.4 that way...... Ok, its not inhibiting the update notification per-se, but gets you on the latest stock build and keeps your rooted status.....

I would also suggest you check out voodoo root saver on the market. Its supposed to let your root survive an ota update.

Nickitt said:
I have a wifi only Xoom and it is Rooted. My question to you is, since it is rooted I obviously cannot be updated via OTA, it keeps showing up that I need to update. I cannot turn off automatic update when I go to about then update. Its really no big deal tbh, but it is really flipping annoying and just keeps coming back...
I would really appreciate some feed back and hope someone knows how to fix my problem. Thanks XDA!!!
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Make sure you read the "General" and "Android Dev" sections also - don't just ask a question in "Q&A". As stated in post #2, there is an existing (though only about 1 day old) solution - and it worked quite well for me.
Good luck.

willysp said:
Make sure you read the "General" and "Android Dev" sections also - don't just ask a question in "Q&A". As stated in post #2, there is an existing (though only about 1 day old) solution - and it worked quite well for me.
Good luck.
Click to expand...
Click to collapse
Well mister, how about you go ahead and post that sweet little HTML so I may click on it and square this away eh?
Or, it would be amazing if someone can just simply tell me which process to freeze. Cannot find a damn process with the word "update" in it to freeze.
IDGAF about a damn update, like I said, I am CONTENT with everything I have on my XOOM right now. Simply need to find the "process name" to freeze..
Sorry to be short, but I am pissed off, aggravated and personally am about to throw this in the Hudson river.

Nickitt said:
Well mister, how about you go ahead and post that sweet little HTML so I may click on it and square this away eh?
Or, it would be amazing if someone can just simply tell me which process to freeze. Cannot find a damn process with the word "update" in it to freeze.
IDGAF about a damn update, like I said, I am CONTENT with everything I have on my XOOM right now. Simply need to find the "process name" to freeze..
Sorry to be short, but I am pissed off, aggravated and personally am about to throw this in the Hudson river.
Click to expand...
Click to collapse
I thought from your first post that you wanted to be able to update and stay rooted. I referenced the "sweet HTML" already in post #2 as a way to update and stay rooted.