Jump to content

LuisBOSS302

Recommended Posts

OK guys, my G3 started getting the "unable to connect to proxy server" error yesterday. It'll happen randomly and when it does, I have zero internet connections. A reboot will fix it until it happens again.

 

Has anybody figured out what is causing this or how to fix it?

 

Sent from my LG G3 using Tapatalk

  • Like 1
Link to comment
Share on other sites

OK guys, my G3 started getting the "unable to connect to proxy server" error yesterday. It'll happen randomly and when it does, I have zero internet connections. A reboot will fix it until it happens again.

 

Has anybody figured out what is causing this or how to fix it?

 

Sent from my LG G3 using Tapatalk

sucks big time I know. Since I did the clear cache and factory reset for the third time it hasn't done it, but battery life is horrible still.
  • Like 1
Link to comment
Share on other sites

is it just with sprint data or does it do with wifi to???

 

mine gets squirrely on occasion with texts, as does the wifes G2....

Does it with everything, even WiFi. It is driving me insane.

 

While I love lollipop, it is proven to be buggy as hell, at least LG's implementation of it. Ugh.

 

As soon as I can root this shit, I'm going as stock android L as I can get.

 

Sent from my LG G3 using Tapatalk

Link to comment
Share on other sites

Just flash the rooted image. I don't know that you will see a way to hack root under 5.0 , it's a lot more secure. You will probably have to flash kitkat, root and twrp that, then flash the 5.0.1 rooted image .

  • Like 1
Link to comment
Share on other sites

Just flash the rooted image. I don't know that you will see a way to hack root under 5.0 , it's a lot more secure. You will probably have to flash kitkat, root and twrp that, then flash the 5.0.1 rooted image .

This is what I was afraid of. :sadface:

 

Sent from my LG G3 using Tapatalk

Link to comment
Share on other sites

Rooted running 5.0.1 debloated. Sounds like LG needs to brush up on their OTAs. Glad I don't ever do stock. 4 months of it was bad enough waiting for root after release day. With the level of savvy in this community I often wonder why any one of you run stock. Rooting is all but idiot proof, and with a stock TOT file and a computer, nothing can stop you but hardware failure which root is not going to cause unless you mess with the CPU.

 

And Coors is correct. 4.4.2 ZV4 is the only rootable version. ZV6 and ZV8 cannot be rooted and likely never will be.

 

Sprint needs to hurry up with VoLTE and Carrier Aggregation. Although LTE in Denver area is pretty good minus Highlands Ranch.

Link to comment
Share on other sites

Rooted running 5.0.1 debloated. Sounds like LG needs to brush up on their OTAs. Glad I don't ever do stock. 4 months of it was bad enough waiting for root after release day. With the level of savvy in this community I often wonder why any one of you run stock. Rooting is all but idiot proof, and with a stock TOT file and a computer, nothing can stop you but hardware failure which root is not going to cause unless you mess with the CPU.

 

And Coors is correct. 4.4.2 ZV4 is the only rootable version. ZV6 and ZV8 cannot be rooted and likely never will be.

 

Sprint needs to hurry up with VoLTE and Carrier Aggregation. Although LTE in Denver area is pretty good minus Highlands Ranch.

You're absolutely correct.

 

My fear isn't rooting, it is the endless customization and availability of different Roms, which makes choosing the correct one difficult for somebody that doesn't follow this stuff everyday. It is slightly overwhelming.

 

I just want a bone stock Android L ROM that I can tweak from there, rooted obviously.

 

Sent from my LG G3 using Tapatalk

Link to comment
Share on other sites

The Sprint data optimizer is number three for battery use.

I am seeing this as well. At first I figured they turned it back on with the update, but even after turning it off I still see this.
Link to comment
Share on other sites

The Sprint data optimizer is number three for battery use.

I am seeing this as well. At first I figured they turned it back on with the update, but even after turning it off I still see this.

Yup. I disabled it and am still seeing it running.

 

Sent from my LG G3 using Tapatalk

Link to comment
Share on other sites

So when I have my screen on full brightness and play a video I recorded from the camera it dims my video. But if I play a YouTube video at full brightness it plays just fine. This started since Lollipop. Has anybody else experienced this?

Link to comment
Share on other sites

You're absolutely correct.

 

My fear isn't rooting, it is the endless customization and availability of different Roms, which makes choosing the correct one difficult for somebody that doesn't follow this stuff everyday. It is slightly overwhelming.

 

I just want a bone stock Android L ROM that I can tweak from there, rooted obviously.

 

Sent from my LG G3 using Tapatalk

AOSP has a long way to go to be stable on this. IMO stock is best for now, until all the major bugs get worked out of AOSP. It's actually been about a month since I checked in on it tho too.

 

Personally Im just waiting for our awesome theme guy to theme up the stock L rom and I'll be happy. I've always prefered AOSP based ROMs to anything stock, until this phone. There is no speed difference anymore and LG doesn't add a whole lot to their stock roms so they are pretty aospish anyway.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...