yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] phoenixus:
I just hitup Samsung chat...they had me try a battery pull for 30 seconds, and that did seem to help...i get consistent 18MB download speed and the signal bar appears steady
[Verizon Samsung Galaxy S III] rlarson)mn:
I had all of the issues after my Verizon update yesterday. I did a reboot as well as a battery pull waiting and then starting up with no fix. I ended up first disabling 'Caller Name ID' app then I switched from 'Global' to 'CDMA/LTE/EVDO' in the Network mode. That took care of my 4G speed issue, my battery drain issue, my 4G and WiFi on at the same time issue and my lower front face heating issue. Not sure what was up with the release but it sure did a job on my unit until I completed the above changes.

I have not been into my local Verizon store to let them know how unhappy I am about these issues but I fully intend to do so.
[Verizon Samsung Galaxy S III] cacain:
Can I Odin Back

I used Odin to unroot and go back a couple of versions so I could get the new OTA. I am not a fan of the latest OTA. So my question is can I use Odin to flash an old stock rom without being rooted and unlocked? essentially can I flash an old stock on top of the new stock?
[Verizon Samsung Galaxy S III] rlarson)mn:
I believe the answer is that question is that to do a 'flash' you need to be rooted.
[Verizon Samsung Galaxy S III] cacain:
I thought so. I was just looking for a quick and dirty solution.
[Verizon Samsung Galaxy S III] HypostaticOnion:
Pretty sure you can just Odin any file.
[Verizon Samsung Galaxy S III] rand4ll:
Where do you set these items? I looked through settings and couldnt find network mode and don't see how to disable the caller ID app...thanks.
[Verizon Samsung Galaxy S III] Elite49:
Check in Application Manager or Titanium Freeze ID.

Network Mode is in Settings, More Settings (Under Wifi and GPS stuff).
[Verizon Samsung Galaxy S III] rand4ll:
Thanks! Found the network mode setting but just got the phone and haven't rooted yet so titanium isn't mu h use yet but will keep it in mind for whwn I do. Figure I will try the phone srock for a week or so:cool:
[Verizon Samsung Galaxy S III] dweezle:
If you look in Caller ID itself, it has a remove option. It takes a bit of looking at the menu and sub menus, but eventually I got to "uninstall".
[Verizon Samsung Galaxy S III] dweezle:
I seem to be in some weird half in half out situation. I lost the LTE connection entirely. I was trying everything I could think of (3:00a.m.) and re-did Beans Odexed/rooted version of VRBMD3 plus the firmware. That's where I am now. I say that I am half and half because I don't see the multi window pull out tab. I live in a really poor LTE signal area. The reason that I think I don't have ANY LTE is because the results I see in Advanced Signal Status app. Is there another way of verifying that the LTE radio is off? How do I get back to a place where I still have LTE? Going back to I535VRBMB1 would be fine with me. I just don't know exactly the best way to do it. I am rooted and unlocked, I have Odin installed on my PC, and have TWRP as my recovery. I would love to put this giant fubah behind me.
[Verizon Samsung Galaxy S III] rlarson)mn:
1) Settings, More settings, Mobile networks,Network mode, select LTE / CDMA.

2) Settings, Application manager, All, find the 'Caller Name ID' application and select that application, then once you are in the control area of the application 'Disable' it. I also did a 'Force stop' then disabled it. I was not able to find where to uninstall it but Disabling it worked just fine for me.
[Verizon Samsung Galaxy S III] Quacker:
You can't uninstall system apps (in this case, bloatware) without rooting, but disabling will prevent it from ever running. I have it disabled and I'm getting 20mbps download speeds on 4G.

On the other hand, my battery life since the update is just awful. After a day at work with only 5-10 minutes of screen usage, I'm at 60% battery.
[Verizon Samsung Galaxy S III] Chadashcroft22:
You can this app an pretty much any other caller id app verizon has bundled into there updates. Just start the trial, stop the trial and viola your uninstall button magically appears.
[Verizon Samsung Galaxy S III] lexluthor:
Yes, I think that's the best way to disable it. There's an option right there in the program to get rid of itself. No need to disable to freeze with Titanium.
[Verizon Samsung Galaxy S III] Finn81:
How can i update my i535 from MB1 to MD3 ?
[Verizon Samsung Galaxy S III] hallstevenson:
Your phone will prompt you to do it
[Verizon Samsung Galaxy S III] Finn81:
Even with custom recovery,root,and non verizon sim?
[Verizon Samsung Galaxy S III] rlarson)mn:
Well I did not want to take the chance and do anything to active it so I just disabled it.

As far as battery length, I have noticed a reduced length with my daily useage. Generally I had between 45% and 25% remaining after a normal 16 hour day off of the charger. Now I am down to between 25% and 10% at the end of the same type of day. My 4g lte however is at a normal range that being 25,000 download and 12,500 upload speed. Thats with the disabled Caller ID app and the switch from Global network to LTE/CDMA network. I like the update with the exception of the reduced battery length. Sure am glad for this user community though other wise I would have been still hunting for what to do to fix my unit since Verizon has historically not been very helpfull in my experience.
[Verizon Samsung Galaxy S III] phoenixus:
Update #2:

I'm beginning to think the Verizon caller ID app is to blame for the issues. After I initially updated, I just disabled the app without ever opening it (through the built in disable option). I still had spotty 4G issues.

So last night, I fully removed it.

1. Undisabled app

2. Started the free trial

3. Canceled the trial

4. Dug through the menu inside the app itself to find the "remove" option and removed the app.

5. Rebooted phone

Since then, it seems my 4g connection has been way more stable.
[Verizon Samsung Galaxy S III] unclemoosh:
I am experiencing the same issue???
[Verizon Samsung Galaxy S III] pandimus:
Seems they changed the slide to call feature.
[Verizon Samsung Galaxy S III] NinCaptain:
can't wait till this is put together with hyperdrive to make rsl14

was on 13 but went back to 12 need my mobile hotspot
[Verizon Samsung Galaxy S III] dweezle:
With great care. Seriously, check out what's being posted about this update. Make sure you can get back to your pre update state. Then at least you'll have a fallback position if things go south on you
[Verizon Samsung Galaxy S III] droidgreg01:
Anyone else experience a problem when trying to crop a photo via the gallery app and instead of going to crop mode, it goes to face tagging. I have face tagging off already.

This seems to happen when two distinct (or more?) faces are present. Other pics with one person, it goes straight to crop mode.
[Verizon Samsung Galaxy S III] lakingslayer:
My wife's unrooted phone has this issue. I used the remove option in the app and it still has the issue. Going back to MB1.
[Verizon Samsung Galaxy S III] dweezle:
Droid Life

I wonder if you can be charged even after deleting the app from your phone? Ya gotta luv verizon.
[Verizon Samsung Galaxy S III] phoenixus:
Found a possible source for the battery drain.

Everyone check your maps/latitude settings. Before the update, I had only Background location reporting turned on, not sharing my location with friends.

It seems after this update, sharing location with friends on latitude was checked by default. Maps had a high keep awake time on my phone, and it seems to have dropped quite a bit after turning that off.
[Verizon Samsung Galaxy S III] DigitalMD:
You have to take into account that Samsung doesn't have full control of the final carrier releases, Verizon does. After Samsung fnishes their work, Version takes another 3 to 6 months to add/tweak/ cripple/ test/ refix/ approve/ rollout. Each carrier builds on their own specific radio/modem stuff and also adds extra apps and cripples some features. For example Version cripples Google Wallet and adds their own , usually bogus apps. So developers don;t get the source code for the radio / modem and you will not be seeing custom signal improvements. Sometimes you will see some slight tweaks to parameters in a build.prop file that may of may not make slight speed improvements, but the actual signal is controlled by the hardware and the cell carriers' firmware. It is what it is and we are stuck with what Verizon blesses us with.

For the most part, claims of speed increases by removing so called bloatware is nothing but a placebo effect. Apps you don't use can be frozen if you root, but they really don;t use any resources or slow anything down most of the time.
[Verizon Samsung Galaxy S III] lakingslayer:
I'm sure they love to do that and only a % of the people complain so they make $$. F'ers
[Verizon Samsung Galaxy S III] wijg:
I've searched through every page in this thread, as well as multiple forums in the Verizon SIII section and haven't gotten a clear answer just by reading, so I apologize if this is obvious and I'm just missing this.

The most recent OTA has completely screwed with my reception, and the best course of action that I've been able to gather is just to revert back to MB1 completely...the entire update (not just the modem/radio).

Where can I find the download for MB1 and instructions to revert back....preferably without wiping my phone completely?

Thanks!

EDIT: I should also mentioned I'm 100% stock and unrooted
[Verizon Samsung Galaxy S III] phoenixus:
Have you tried uninstalling the caller ID app (not disabling it) and doing a soft reset of your phone? I did those two things and it has seemingly helped me out.
[Verizon Samsung Galaxy S III] robcop19:
aa
[Verizon Samsung Galaxy S III] wijg:
Yes I've tried both, and after reading the "fine print" about uninstalling the caller ID app from within the app, it doesn't say uninstall from the device...just uninstall the called ID icon in the app drawer. Upon reboot after "uninstalling" it was still in my application list in settings and I had to force close/disable it again there.
[Verizon Samsung Galaxy S III] rlarson)mn:
That was my experience also. The app comes back onto the phone as you indicated. I did the same close/disable function as you did and it seems to take care of it for now. After a reboot the app stayed disabled.
[Verizon Samsung Galaxy S III] wijg:
Same here, but my reception still sucks!! Getting 3G in areas I've always had 4G in....constant switching between modes at work (where I've always had 4G), and in some places it's even switching to 1x semi-frequently when that used to be an incredibly rare occurrence, only when I walked into buildings that were complete wireless dead zones.

Battery life is down (probably on account of the reception)....just overall not impressed with this update.
[Verizon Samsung Galaxy S III] caifan:
It remained in the system/app directory no matter what I tried. I finally used Root Explorer to delete the app for good.
[Verizon Samsung Galaxy S III] jimmyUT:
Did you notice any improvement on 4g stability after using root explorer to delete the apk?

---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------

So I flashed back to mb1 radio to see if that helped. 4g went back to normal, but gps wouldnt lock at all. Now I am back on new modem, crappy 4g again but get gps locks instantly. Is there a way of flashing just the 4g modem from mb1 instead of all the firmware togeter?
[Verizon Samsung Galaxy S III] miniblue:
I read in these treads that if you change your preferred network mode to LTE/CDMA that problem went away for most.
[Verizon Samsung Galaxy S III] wijg:
I just followed the instructions in this post: http://xdaforums.com/showpost.php?p=42103230&postcount=2

At first glance things seem to be better. I'm getting 4G now in my girlfriend's house where I've only had 3G/1x over the past two days. Guess I'll know more in a couple of days but that's promising...
[Verizon Samsung Galaxy S III] ImgBurn:
ok Guys,

I Have been following the net & XDA since the

OTA. I believe its far more serious than this update.

I have 2 Sammy S3s one B1 JB v4.12 version stock rooted

second HE ICS v4.04 stock rooted. I have been having the

same issues you all are having on MD3 lately.

I Known the

Caller Name ID

is a big problem.

I dont have this app on either phone but

still have the data issues. The HE ICS phone

doesn't have the change your preferred network

mode to LTE/CDMA from Global and back setting.

The B1 JB v4.12 phone does. I find switching

LTE/CDMA to Global----Global to LTE/CDMA

when signal drops to 3G will put it back to 4G LTE.

Yea I know it doesn't make any sense but this

is VZ what does.:p

Call Verizon I Know Nothing Call Sammy what

update. :cyclops:

WoW we actually pay these Corps good money

:mad:

and this is the support & service we get WoW.

Long Past time 2 jump ship

But That's Just My Opinion. I Could Be Wrong
[Verizon Samsung Galaxy S III] dweezle:
The reason that the Snapdragon S4, dual core, processor was chosen for the U.S. version of the S3 was because it bundled the application processor, LTE radio and cellular radios all into a single package . I think previous LTE phones had a separate radio for LTE. Are the Quad core S3 phones having similar problems with reception? Theoretically, choosing the Snapdragon S4 made sense from a manufacturing standpoint. Clearly this line of questining is way beyond what I can truly understand, but I do know not to buy a vehicle during it's first year of production.

I was having 4G reception issues in areas where LTE was not entirely built out, before this update came along. Calls were often garbled, and sometimes dropped. I got my S3 in April.
[Verizon Samsung Galaxy S III] f308gt4:
Fully stock. My issues seem to happen when I turn on/off Wifi. If I have a network connection, but then turn on Wifi, the 3G or 4G icon disappears. Then, when I turn off Wifi, I get no signal, even though Mobile Data is on. But, if I toggle between Global and LTE/CDMA in the preferred network setting, this will usually then trigger the network to start working again. It sometimes starts up under Global, other times under LTE/CDMA, so the actual network preference doesn't seem to make a difference to me.

I did Disable the Caller Name ID application. Doesn't seem to affect anything.
[Verizon Samsung Galaxy S III] ImgBurn:
Like I said in my earlier post I don't

think its so much the update as it's

VZ's network. As I have not updated

my phones to MD3.
[Verizon Samsung Galaxy S III] ghodzilla5150:
I spoke with Verizon 2nd Tier support last night about the 4G issue and he basically said that the Software Engineers now know about the issue and they are working on an update. He said it may take up to 8 weeks. I was considerate with him and explained that their update borked our Radios and he agreed. He said I knew what I was talking about so he would not BS me. Hope that helps some here. They know and are working on a fix
[Verizon Samsung Galaxy S III] detonation:
I installed the update by using the full ROM and firmware in the rom forum. If I want to revert back, do I just restore my nandroid and flash the previous version of firmware? Am I correct in saying a nandroid doesn't touch the radios/firmware/etc?
[Verizon Samsung Galaxy S III] wijg:
I ended up rolling back completely to MB1 using directions in this thread: http://xdaforums.com/showthread.php?t=1974114&highlight=no-wipe

I couldn't find a modem/radio/AIO that didn't require CWM or TWRP recoveries, and lo and behold all of my 4G issues were fixed (as expected). Something is definitely borked in MB3. I don't really intend on using multi-window so I'm good with this.
[Verizon Samsung Galaxy S III] phoenixus:
Well i thought i was fixed...but apparently no.

Today my google music stream just stopped. Phone showed I still had 4g and full signal, but only the upstream arrow was lit up. Web pages wouldn't load, ect. I had to turn mobile data off to get it to use the downstream again.

Ugh.
[Verizon Samsung Galaxy S III] txkorm:
Just got off the phone with Verizon tier two and as the poster above said, they know there's an issue. I too was very professional about it and the rep was a little more giving in admittance that the issue is wide spread. She implied that the more complaints on the issue, the quicker a resolution will probably come. So, please call and let them know how wide spread the problem is.

Currently not being productive on my S3.
[Verizon Samsung Galaxy S III] chrisgriner:
I talked to a rep over the weekend in regards to a separate line issue and I brought up my current issue as seen by all posters here. The particular rep I spoke to claimed to know nothing of the issue. I kept things pretty simple and described the steps i'd taken to factory reset, blah blah blah. I also let him know that I could put my sim in my spare Galaxy Nexus and 4G operates normally. His only response was to send out a replacement. I told him I would contact Verizon this week after I decided what to do. I don't think a replacement is going to fix the issue if it comes pre-loaded with the same update. If I am lucky and it comes with an older update, I would imagine it would be fine.

Just odd that this issue is affecting certain people and not others.

I've flashed my phone back to oblivion and I only run into one scenario where 4G works. If I flash via odin back to stock 4.0.4, I can then install an old app called Phone Info (not the current market version) and force the phone to use LTE Only. By doing this LTE works and works great, but I have no phone calling capabilities as LTE is the only functioning network. If I change settings back to CDMA/LTE/EVDo, I revert to the same issue as everyone else.... 3G locked... What pisses me off the most about this is I have had no interest in upgrading to the S4, but I know for a fact if I were to do so I would not have any of the current issues. I just feel like they are screwing me and forcing me to upgrade...

On one hand I want it fixed. On the other, I'd like to see how long it takes for them to fix it. There doesn't seem to be much press about this issue. Either it is not affecting many users or people just aren't voicing their displeasure enough.

Here is a thread over at Verizon Forums if anyone wants to chime in.

https://community.verizonwireless.com/thread/799450

Also, here was a post referencing the issue on Droid-Life:

http://www.droid-life.com/2013/05/31/verizon-galaxy-s3-struggling-with-lte-after-latest-update-other-issues-too/
[Verizon Samsung Galaxy S III] gbruyn:
MB1 Radio worked for me

I flashed the MB1 Radio in CWM and 4g problems seem to be a thing of the past for me. GPS seems to be working normal as well. Will confirm later.
[Verizon Samsung Galaxy S III] sipock97:
You could always just root the phone and flash the old (MB1) firmware and wait for Verizon to come out with a fixed update. I'm probably going back to a Beanstown Rom.
[Verizon Samsung Galaxy S III] HeadlessPonch:
You did that over the MD3 OTA? Did you do the aio, or just a radio flash? Where did you get the file? (So many questions)
[Verizon Samsung Galaxy S III] sipock97:
I got zip file here. It was posted a few pages back. Been running fine for me as well after flashing the MB1

http://xdaforums.com/showthread.php?p=42180727
[Verizon Samsung Galaxy S III] HeadlessPonch:
Thanks. I went ahead and flashed the md1 firmware and didn't break anything. My gps was slow to lock the 1st time (@45secs), but that could have been partially the roof over my head on an overcast day.

<Don't ask me how I sent this>
[Verizon Samsung Galaxy S III] chrisgriner:
That's my bad. I was implying by "flashing back to oblivion" that I had tried all modem/firmware/android versions. Well, android at least between 4.0.4 and 4.1.1. Even if I flash everything back to as far back as I can go, i get the same result. I've tried MB1 all the way back to I535VRLF2 which was the modem shipped with the phone. Each flashing step, I'd test and get the same result. Maybe I have an even more messed up issue than others, but the issue stands. Nothing I do since the update will allow 4G to work, unless I do exactly as I posted above.

It almost feels as if Verizon's network knows that I am using an S3 and it is specifically denying me access or prioritizing 3G over LTE.

---------- Post added at 04:12 PM ---------- Previous post was at 04:08 PM ----------

I do wonder why that is not working for me...

I did order a new SIM. Going to try and flash back to an early version, activate the new SIM and see what happens.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If you tried every modem, I'd suggest dialing the reprovision sim code. It only works on VRALF2 or VRALG1, nothing else. It wipes your internal storage as well. Or of course, you could wait for the new sim.
[Verizon Samsung Galaxy S III] DigitalMD:
I heard that Samsung / Verizon have now pulled the OTA and will release a fixed version later, That usually means 1 day for Samsung to fix it, and 3 months for Verizon to test and approve the release
[Verizon Samsung Galaxy S III] chrisgriner:
That was actually one of my first steps when I got back to VRALF2 and 4.0.4. It still did nothing for me. I do however have an update....

My new sim came in a few minutes ago. I took my old sim out and used Odin to flash back to COMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar. Once the flash completed I started the device and verified that everything was installed correctly. Using android 4.0.4 and baseband VRLG1. Note, I kept the old SIM out of the device and powered it off after verification. I called Verizon and activated my new SIM. Once I was instructed to, I inserted the SIM and powered on the device. Even before Activation was finished my 4G LTE signal was active and in use. Activation finished and I've been able to keep 4G.

Now, I know I shouldn't but it's killing me to try it. I want to accept every OTA update available and see what happens. If what an above poster mentioned is true and they have pulled the OTA then I wont get the bad OTA. But I'm curious and want to see what happens.

Now that I know ordering a new SIM and following the procedure above works, I can always start over.
[Verizon Samsung Galaxy S III] gbruyn:
Yeah. Just flashed the radio ZIP. Not totally sure with the AIO is... but don't think I flashed that. So far so good still. Got the best of both worlds with the new update and the old radio.
[Verizon Samsung Galaxy S III] chrisgriner:
Update

So after flashing back to stock, including the modem, and activating my new SIM, everything started working. I was curious what would happen, so I pushed forward and documented what happened after each OTA update:

Stock flash COMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar --- OK

Update 1 4.0.4 VRLG7 --- OK

Update 2 4.0.4 VRLHE --- OK

Update 3 4.1.1 VRBLK3 --- OK

Update 4 4.1.2 VRBMB1 --- OK

Update 5 4.1.2 VRBLMD3 --- OK

So, after each OTA update I toggled Airplane mode on and off, and restarted the device. I never lost my 4G connection and all seems good now.

I was 99% sure that on Update 5 my device was going to lose 4G....I was wrong.

Experience over...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
InvisiblekI has started posting the all in one (aio) zip for VRBMB1 and newer modems. It includes several additional partitions not just the modem and rpm that we were always flashing from VRBLK3 and earlier.