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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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