>>33151367Any PG/G/entoomen here?
I have a problem regarding this game, maybe my phone, probably my wireless carrier particularly in areas of high population(not excess like a concert but normal nyc midtown)
I have a galaxy s7 edge. I have an SD card and my internal storage is only 61% full.
When I was grinding in midtown the last two evenings of the event. My game crashed every 3-5 minutes (no exaggeration). I have Verizon and had full 4g LTE connection - not saying i was getting that bandwidth.
I tried everything. From puttin my galaxy on maximum performance mode and turning off the in-game battery saver mode to the opposite (battery saver etc) and everything i could think of in between.
I walked around the block once to get more pokeballs and my game crashed 10 times - i counted. It took 10 min cause i stopped to pair go-tcha but i believe it would have crashed 10 times in the 5min walk.
I had a go plus (gotcha) connected which was mandatory for the event, which ofc needed to be reconnected after every crash.
I also wear a fit bit which at one point i disconnected
>more context Outside of this extremely populated pokemon go hotspot the game works "fine". Still crashes a few times an hour but livable. And crahses when it overheats. I know it's not the GOAT phone but it's certainly capable of handling this game
Also, my gf has an iPhone 6s with AT&T and was using the go-tcha and was with me both nights for hours. Her game crashed twice an hour maybe more but NOTHING like i was experiencing the 15-20+ crashes an hour
What do you think is/was causing the constant crashing those two nights? Server overload? Cellular packet traffic jam(or w/e) on verizon's part?
And is there anything I can do about it? Any suggestions? I was already going to trade in my phone for an s8 but it seems like fucking Verizon throttling the bandwith and niantics servers choking to death due to it. Im no expert though