Database Info

AT&T to Push JH7 Starting Today...

*UPDATE*
Designgears has captured the OTA update and packaged it up for anyone who is having trouble with the download applying.
http://forum.xda-developers.com/showthread.php?t=790080
Software Updates and Maintainence Releases
1.09/21/2010 - Firmware Over the Air (FOTA) software update changing software version from I897UCJF6 to I897UCJH7. A 12MB download is being pushed to Samsung Captivate owners starting on 09/21/2010 and will continue Tuesday through Friday at 15K customers per day until complete. This is NOT an operating system update. This update includes the following software updates:
•Preinstalled software - QuickOffice for Android will allow users to edit various Microsoft Office documents.
•Messaging - Exchange 2003 support, MMS and other messaging enhancements.
•Voice - Improved calling experience.
•Media - media scanning time improvements.
Note:
This firmware update is not intended to resolve all device reset or freezing issues, which may be caused by:
•Corrupted files
•Device memory becoming filled and leaving insufficient room to run applications.
•Use of incompatible 3rd party applications on the Samsung Captivate.
http://www.wireless.att.com/answer-center/solutionDisplay.jsp?solutionId=KB110797
scroll to the very bottom of the link

No gps fix?
Sent from my SAMSUNG-SGH-I897 using XDA App

Mention of GPS strangely absent.

been running JH7 since it came out with SRE.
WTF is this? JH7 doesn't fix GPS nor does it come close!
(battery life is AMAZING THOUGH!)

Well, since GPS is not mentioned, I doubt this is meant as the fix for GPS issues...
But it IS a good sign that AT&T is actually working on our device, since they are releasing this FW to the public.

Very odd. They guaranteed a GPS fix by end of Sept. We already have used JH7 and it doesn't fix our GPS. I can't imagine them putting out another update before the end of September...
Is it possible that the update from AT&T will somehow include more file update or be different from the JH7 version that we have? Beyond that, I can't understand how they are finally releasing an update but NOT fixing the biggest issue. Especially since they apparently fixed it on the Vibrant and know how to fix it.

Looks like I got it. I definately have to test Exchange now. Maybe it'll work properly.

swedishcancerboi said:
Looks like I got it. I definately have to test Exchange now. Maybe it'll work properly.
Click to expand...
Click to collapse
Check the GPS....

actually, before I get too crazy, let me verify something:
I had JF6, I made a backup image using ROM Manager/Clockwork Mod. I then applied the JH7 found here, had problems (no sideloading), and restored the image. I am ASSUMING that put me back on Baseband JF6, but I don't remember checking afterwards.
Is it possible that the JH7 I have is left over from my manual update? I don't wanna lie to everything thinking I got the official push and really didn't.

swedishcancerboi said:
actually, before I get too crazy, let me verify something:
I had JF6, I made a backup image using ROM Manager/Clockwork Mod. I then applied the JH7 found here, had problems (no sideloading), and restored the image. I am ASSUMING that put me back on Baseband JF6, but I don't remember checking afterwards.
Is it possible that the JH7 I have is left over from my manual update? I don't wanna lie to everything thinking I got the official push and really didn't.
Click to expand...
Click to collapse
You can flash back to JF6...
I will do it if need be but it will have to wait until tonight.
My GPS works fine and I have none of the other issues that this is supposed to fix, so I couldn't tell you whether the update will fix those or not.

swedishcancerboi said:
Looks like I got it. I definately have to test Exchange now. Maybe it'll work properly.
Click to expand...
Click to collapse
Did you have to look for updates on your phone or was it sent auto? Were you running stock when you got it?

Rhiannon224 said:
Did you have to look for updates on your phone or was it sent auto? Were you running stock when you got it?
Click to expand...
Click to collapse
They are pushing it, but you should be able to get it if you search for updates and your phone meets the criteria...

I'm running a backup now. I'm need to test a few things. I just happened across this thread and had a quick look at my basband number and it shows JH7. I *should* be stock. But that assumes that when I restored back to my original image, it also restored JF6
I'll get back with you. I don't feel like I'd be one of the lucky ones to get the update first (unless it goes by purchase date, I did get mine early).

LOL...fail. I went to check for update, said no update and that I can not check for another 24 hours. WTF? why cant I check for updates when I want.

Noob question: Is it necessary to un-root and un-lagfix before attempting to download or install this update?
Sent from my SAMSUNG-SGH-I897 using XDA App

iceman4357 said:
LOL...fail. I went to check for update, said no update and that I can not check for another 24 hours. WTF? why cant I check for updates when I want.
Click to expand...
Click to collapse
Me too, lol, I'm already running JH7 that was leaked. According to the AT&T site they are looking at your firmware version and that's how they determine who's getting it.

Hmmm, debating if this update is even worth it. Doesn't fix GPS, and it's not Froyo

OTA update process usually takes days or weeks. It pushes in batches so that only limited number of phones will download the update so that the update server don't get overloaded. No, maunally check for update does not speed the process up at all or change your position in the queue. Basically, you have to wait for your turn.
Sooner or later someone will figure out the URL to download the update directly. Only when that happens, you can go and download the update and manually put that file to internal SD card, boot the phone into recovery mode and apply the update.
If that's too much work for you, wait for your turn.

Ikonomi said:
Noob question: Is it necessary to un-root and un-lagfix before attempting to download or install this update?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
same question here. Anyone know if I'll lose root/non-market apps if I apply this update?

One thing I did notice about the leaked version was the new YouTube app styling. I kinda liked it. Came in handy at the gas pump.

So, I'm running JI6 and I just got this notice...

So, I'm running JI6 and I just got this notice...
"AT&T is providing a free update for your phone. When asked to install the update, please select OK."
Shouldn't this only appear when running 2.1 builds?

did you install it to see what it was?

DOAlaboratories said:
did you install it to see what it was?
Click to expand...
Click to collapse
That would sure be interesting to know...thinking just the crappy JH7 update, but the hopefull in me is very curious...

I actually got the same thing today but I'm avoiding it like the plague.
No chance in hell the ATT can provide me something as amazing as cognition2.2

Heh...
So, I got the same message from AT&T as OP a few hours ago, and I just noticed a "Could not connect to the server" window. I'm guessing that by running Cog2.2 on my phone, the server won't push the update to it given that it isn't running an official build.
Oh well

I can test this later as i have flashed back to stock 2.1, after testing JI6, and experiencing issues with key apps i use on a day to day basis. but i am curious to see about this update. I mean the most harm it could do is a software related "brick" right?
Sent from my SAMSUNG-SGH-I897 using XDA App

Furthermore, it states on my JH7 build that no user data would be lost - is this an over the air Froyo? I'm running 2.1 and already did the first update for JH7, so what is this?

GarciaM25 said:
Furthermore, it states on my JH7 build that no user data would be lost - is this an over the air Froyo? I'm running 2.1 and already did the first update for JH7, so what is this?
Click to expand...
Click to collapse
You're running JH7 and got this message? Interesting...
Sent from my SAMSUNG-SGH-I897 using XDA App

CLShortFuse said:
You're running JH7 and got this message? Interesting...
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yep, and the bad news is....... I can't say what the hell the update was for considering it sat "preparing" it for a while, then failed to update, not unlike the issues others were having when putting on JH7 (mine updated right away, but my girlfriend's did not) - just tried to roll it a day forward to trick it, and it showed no update available! Will keep working on it, but there can't be just TWO of us who have seen this message when waking up this AM....

It will be the same JH7 OTA. AT&T just started sending out SMS to random Captivate owners. Nothing new. There is no way, nor AT&T cares, for AT&T to know you have updated to other firmware or not via SMS. They probably picking you out of the ppl who haven't tried to do OTA update.

Every Captivate user will receive this text message once, regardless of what version they are on. AT&T can't see what version of Android OS you are running. What they are doing is sending a text message to all users that are showing a Captivate on file in chunks. I haven't received that message yet, but even though I'm running Froyo via Cog 2.2, I'm still gonna get this message at some point.
Just ignore it unless you really want to play with their over the air update (which apparently bricks phones if you've ever altered it from stock in any way, even if you Odin back to JF6....)
Personal opinion? Ignore it. CL, continue the great work you are doing on the Jupiter.xml edits / development. I read into your posts at least every other day.
Thanks folks,
-h8

h8rift said:
Every Captivate user will receive this text message once, regardless of what version they are on. AT&T can't see what version of Android OS you are running. What they are doing is sending a text message to all users that are showing a Captivate on file in chunks. I haven't received that message yet, but even though I'm running Froyo via Cog 2.2, I'm still gonna get this message at some point.
Just ignore it unless you really want to play with their over the air update (which apparently bricks phones if you've ever altered it from stock in any way, even if you Odin back to JF6....)
Personal opinion? Ignore it. CL, continue the great work you are doing on the Jupiter.xml edits / development. I read into your posts at least every other day.
Thanks folks,
-h8
Click to expand...
Click to collapse
That's right.. this is the forced JH7 official OTA update that it detects you haven't received it.

h8rift said:
Just ignore it unless you really want to play with their over the air update (which apparently bricks phones if you've ever altered it from stock in any way, even if you Odin back to JF6....)
Click to expand...
Click to collapse
It doesn't brick the phone, it just will fail during install, that's all. So your phone will remain in the same state since nothing will have been installed.
Sent from my SAMSUNG-SGH-I897 using XDA App

himmelhauk said:
It doesn't brick the phone, it just will fail during install, that's all. So your phone will remain in the same state since nothing will have been installed.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
For most, your phone will stay in quasi state: neither JF6, not JH7. And probably will never be able to upgrade again via either OTA or Kies. You have to Odin it.
For some, it actually bricks their phone, i.e. can't boot pass the logo screen.

foxbat121 said:
For most, your phone will stay in quasi state: neither JF6, not JH7. And probably will never be able to upgrade again via either OTA or Kies. You have to Odin it.
For some, it actually bricks their phone, i.e. can't boot pass the logo screen.
Click to expand...
Click to collapse
I have heard of very few people who have bricked there phone doing the OTA Update. For almost everyone the update fails and the phone boots into you previous ROM and gives you a message that no changes have been made to your phone.
Brick is a strong word to use. Brick indicates the phone has no hope of being used again. You can almost always ODIN your phone if all else fails.

KewlRobD said:
I have heard of very few people who have bricked there phone doing the OTA Update. For almost everyone the update fails and the phone boots into you previous ROM and gives you a message that no changes have been made to your phone.
Click to expand...
Click to collapse
Actually, from what I read here, most failed update will show your phone is already at JH7 but none of the JH7 features are there. So, no, it does not boots into previous ROM.

So I called Samsung about the OTA firmware failing on my Captivate. I had to use ODIN at one point, so that's why it failed supposingly. Samsung said that there was an issue with v1 of the firmware update and there is now a v2, however Samsung couldn't tell me baseband version and they told me to call AT&T.
I called AT&T and asked them about this v2. They said that firmware I897UCJH7 has been released to fixed various bugs, some other items, and she specifically said GPS. So, I'm not sure what Samsung was meaning by v2, unless they meant this JH7 was v2 and what came on the phone out of the box was v1.
While I had AT&T on the phone I thought I'd ask about Android 2.2 and when it was going to be released. The AT&T rep said, "Hang on while I Google that for you." I was like WTH, really? This is where AT&T gets their information I guess... HA

Alot of times they google my questions. They do it for most questions that don't involve can't receive text and whatnot. Feature phone, they can help, smart phone, no way in hell.
From a phone on an app

I'm running stock 2.1 with root and I have the message. I will back up and reflash later tonight to see if I can download it and put it up for y'all. But currently, it fails the same way op described.
Sent from my SAMSUNG-SGH-I897 using XDA App

gk527 said:
So I called Samsung about the OTA firmware failing on my Captivate. I had to use ODIN at one point, so that's why it failed supposingly. Samsung said that there was an issue with v1 of the firmware update and there is now a v2, however Samsung couldn't tell me baseband version and they told me to call AT&T.
I called AT&T and asked them about this v2. They said that firmware I897UCJH7 has been released to fixed various bugs, some other items, and she specifically said GPS. So, I'm not sure what Samsung was meaning by v2, unless they meant this JH7 was v2 and what came on the phone out of the box was v1.
While I had AT&T on the phone I thought I'd ask about Android 2.2 and when it was going to be released. The AT&T rep said, "Hang on while I Google that for you." I was like WTH, really? This is where AT&T gets their information I guess... HA
Click to expand...
Click to collapse
The OTA update of JH7 is a special diff version with scripts in order to minize the download size (12 MB vs 120+MB). Obviously, the original script doesn't work very well. So, Samsung probably changed it so that it won't fail so easily. That's what Samsung means by v1 and v2. The final result, JH7, will be the same and you can easily do it via Kies Mini instead of playing Russian Roulette with OTA update.

Got an email this morning from Tec support about 2.2 being available.

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.

[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

New firmware BQG1

Anyone else get an update yesterday?

Yes, got it on mine last night. No clue what it supposedly does yet. Probably just the July security update.

The update notes said it fixed something with corporate email performance and integrated typical android security updates....took it today, i dont notice anything new.

I cannot install the update on any of my rooted phones (which isn't a huge surprise to me). However, the update has been out for a few days, and I haven't seen anything about the update here on the forum until today. I'm hoping someone posts an update method for those of us with rooted phones.

Does anyone know can we use BT firmware from S6 onto S7? I have problem connecting my car hands free system, thought no such problem with S6

BQG1 improves network speed.
Averix said:
Yes, got it on mine last night. No clue what it supposedly does yet. Probably just the July security update.
Click to expand...
Click to collapse
Got the BQG1 update on 7/29 and after stabilizing for an hour ran speed test via WiFi. I had noticed a drop to around 140Mbps on my Comcast service with the last update and couldn't figure out why. With BQG1, my downlaod speed is back up to 230Mbps and running very smooth. Don't know what VZ did, bit it works!
Hope that helps.

neyenlives said:
The update notes said it fixed something with corporate email performance and integrated typical android security updates....took it today, i don't notice anything new.
Click to expand...
Click to collapse
I wanted to give a quick update.
Following suggestions I found on a few threads here, I went ahead and updated all three of my rooted phones to firmware QH1 on Friday, and they are all still rooted.
I used ODIN to re-flash the stock firmware (using HOME-CSC to keep my apps and settings intact. I downloaded the firmware from one of the links I found here on XDA.
I then re-rooted using the procedure in the OP.
I had two issues (that I can think of):
1. A few of the settings (lock screen settings, specifically - maybe one or two others?) were cleared in the process - and I had to set them up again.
2. One of the phone (the one *I* use, of course), rooted okay, but SuperSU was missing after the reboot. Installing it from the Play store appeared to break root. So I just re-rooted it again.
Other than those issues, I think everything else went pretty smoothly.
I hope this is helpful to others.