Jump to content

metayoshi

S4GRU Premier Sponsor
  • Posts

    385
  • Joined

  • Last visited

Everything posted by metayoshi

  1. From what I know, Verizon is the only carrier that doesn't suck at Disney. Even then, their service is far from superb as well, regularly slowing down or dropping to 3G in certain areas. Back when Pokemon Go was still the hotness, anyone not on a Verizon phone needed to tether to one of our friends' phones on Verizon just to get the game to load. Otherwise, good luck doing anything over data. That being said, I can't speak for AT&T since I only know from a Sprint, T-Mobile, and Verizon point of view. This was also during Pokemon Go's peak, so there were hundreds (thousands?) of people at Disney doing it.
  2. Wow, I've seen some hearsay that it was happening on other variants, but this is just proof of their defect being more widespread than just a Sprint problem. After reading some of those things from other people, I feel we're lucky that it was Sprint thing to replace G4s for free. Other people aren't having it so easy. Sent from my LGLS991 using Tapatalk
  3. Again, use cases may differ, but this is what I'm getting with only light usage so far. I only start using my phone really heavily after 7 or 8 PM pacific time since I get off work.
  4. For anyone having battery life problems on the latest update, download an app called CPU Spy, and let it log a typical day's worth. Check the app after that day, and if you see that your CPU is in Deep Sleep is shorter than being in 384 MHz, then it means your system isn't sleeping normally. I would recommend a factory reset and see if that helps. I know it sounds annoying to do, especially if you don't have root and titanium backup to just restore everything as it was, but ultimately, that's the only thing that worked for me. My battery life was horrible on Marshmallow. I was also unfortunate that my phone got the LG HW bug and caused my phone to be stuck in a bootloop literally a week ago (I'm stock, no root, no mods whatsoever on this phone). I went into a Sprint store and got them to order a replacement, and I got my replacement this past Wednesday, the 20th. I decided to update to Marshmallow first and then do a factory reset with my new phone before re-installing all my apps. My new phone has been running much better. After charging my phone to 100% last night, My phone was left unplugged at around 1 AM, and I'm at 79% right now at around 5:30 PM. And this is considering I also have horrible signal in the office at work. So basically, I was forced into a factory reset situation due to the G4 hardware bug, but I saw a huge improvement in battery life. I happened to test the battery drain overnight with my old phone on Marshmallow, and it went from 100% down to 80% between 1 AM and 8:30 AM. On a typical day, CPU Spy showed my phone was in Deep Sleep for only an hour and the rest of the time was on 384 MHz and other CPU states. On the other hand, my new phone was still at 100% when I got up at 8:30 and only went down to 99% a few seconds after I turned on the screen. Currently, my phone is in Deep Sleep 12 and a half hours, and 384 MHz for a little under 3 hours, with the rest of the time doing work in 1440 MHz and 960 MHz. That's how a CPU Spy day should look. If you use the phone a lot, you should see the higher frequencies a lot more, but you should still see Deep Sleep more than 384 MHz. If it's at 384 MHz more than being in Deep Sleep, that means there is a lot of time spent with your phone doing nothing, but something is keeping it from sleeping.
  5. Yep, so it was this app. Android System has the same wakelock pattern (58m of a wake lock today vs 1h 11m last time I tested it), however today, I am sitting at 83% at 4:27 pm. I added that stupid Symantec VIP Access app to my greenify list, and it made my battery life go back to where it used to be. So for those that aren't experiencing good battery life on this phone, remember that all it takes is 1 badly designed app...
  6. Still looks like Android System is causing a huge wakelock. Don't know what the heck is happening. I did notice that within Android System, there's a service called IPSec Service. It looks related to VPN and other "security" services. The company I work at decided to change security policies and we now have 2 factor authentication in order to remote desktop into our work machines. I had to download a Symantec VIP Access app. They allow a push notification to be pushed onto the phone when trying to login through VPN, instead of typing the number down. Uninstalling the app is pretty much not an option, so I disabled the push notifications for that app. Hopefully it helps this time...
  7. I think i know what the main difference is. Two days ago, I read on XDA that you can get your MSL through the Basic Flasher utility they had for the LG G2. I tried it and got my MSL, but after running basic flasher, it disconnected my phone from the Sprint network. I rebooted the phone and it was able to connect to Sprint's network again, so I didn't think anything was wrong. I'm guessing something it did messed my phone up, since my battery has been abnormally draining ever since then. I'm trying the ##72786# reset network trick and hopefully that fixes it. I hope I didn't mess up something permanent.
  8. Back to battery life, it seems like my phone took a hit with the latest update. Before the update, my phone would sleep no problem. The past couple of days, my phone seems to be draining significantly in the background. I haven't installed any battery monitor apps yet to look at what is causing this, but the stock battery stats show Google Services and Android OS as my top two battery users now instead of my screen. I literally have a screen on time of 34m and my phone is at 61% battery life left. Android OS in particular has a 1h 11m wakelock on my phone. That's ridiculous. I even rebooted between yesterday and today, and it seems like the same thing is happening today.
  9. Yea. This is a pretty big well known issue, but many G4 owners have been experiencing missed taps, detecting a tap instead of a swipe, and other issues with touchscreen sensitivity. It's supposedly a software issue, and they supposedly fixed something with this update. I've been OK so far, crossing my fingers. Sent from my LGLS991 using Tapatalk
  10. By the way, I found this on XDA regarding the ZV5 update (which I got last night): #1 is probably the "Reactivation Lock Updates" I quoted from the Sprint site last time. #2 is welcoming since I definitely experienced the missed touches and other touch screen mishaps with my phone. Hopefully it's completely fixed.
  11. I also use the Google Keyboard (as well as the Google Now Launcher) as I personally like Google's look and feel since I came from a Nexus 5. My battery life is pretty good. On a good day where I'm home all day, I can manage 4-5 hours of screen on time, which is great for me as I typically only use my phone less than 2 hours a day. At work where my signal isn't the greatest, I can turn off wifi and data sync and I'm currently sitting at 85% battery life at 4:43 PM (got to work at 10 AM), which is also great for me as my Nexus 5 would be sitting at 70% or less at this point in the day.
  12. Sprint's website shows an update on July 1st, version ZV5. The site shows the update is for "Reactivation Lock updates," whatever that means. http://support.sprint.com/support/article/Find-and-update-the-software-version-on-your-LG-G4/WRNServiceAdvisory_542_GKB86631-dvc8970002prd#!/ I tried manually looking for the update, but it doesn't show up for me yet. Should be rolling out in waves as usual.
  13. I don't think you get the micro SD card anymore unless I missed it in the new promo details. And yes, activate your device first. They'll need your IMEI or ESN or whatever number they asked for (at least for the June Promo), so I think they might actually check if it's an activated device.
  14. So far, only the international EU version of the LG G4 (model H815) even has the ability to unlock the bootloader, which is the first step to gaining root. They also have TWRP support for their version of the phone as well, so they can just flash supersu and they have root already. Nobody else is close, as LG only officially released the method to unlock the bootloader for the EU international version. Read here: http://www.xda-developers.com/no-root-is-not-coming-to-the-lg-g4-just-yet/ There is a bounty thread on XDA for finding a safe method for unlocking and rooting the Verizon/AT&T variants since those are usually the two hardest versions to achieve full bootloader unlock and root. Them (AT&T/Verizon) getting it may also mean us (Sprint) getting it since they should be similar, if not easier on Sprint's side. If you want to donate money or help out yourself, or even if you just want to track the status of it, the XDA thread is here: http://forum.xda-developers.com/g4/general/bounty-root-method-exploit-bootloader-t3130989
  15. Really? I'm having the opposite experience. At home, I'm on band 41 all the time, and around work, it seems to hook onto a weak Clearwire signal as soon as I'm in range of it. I rarely see band 25 unless it's the only LTE band available. Even when I visited Boston this past weekend, I saw more b41 and b26 than b25. Sent from my LGLS991 using Tapatalk
  16. I finally received my free SD Card and extra battery after two weeks. I honestly don't know when I'll need the extra battery as I'm one of the customers happy with the current battery life, but it's definitely nice to know I have a spare. Definitely sign up for the promo if you haven't already.
  17. I find RF performance to be not much different than the Nexus 5, but I enjoyed the Nexus 5's performance. I don't know about your market, but my market has plenty of B41 now and performance is awesome on both my Nexus 5 and G4. I would say keep the Nexus 5 if all you care about is RF performance, but looking into the future, the G4 has the advantage of being compatible with the CCA/RRPP LTE bands as well has having support for CA. It also has support for WiFi calling, though I haven't used it myself.
  18. So I went ahead and finally did a factory reset. One of the first things it did after getting to the home screen was what is attached in the screenshot. Hopefully this is it. It does say "Sprint Default" on it, so I'm guessing this is what my phone was trying to do. Don't know why it errored out the first time.
  19. Noooooooo. That's what I was afraid of. Unfortunately, a stable root doesn't look like it'll happen soon, so I can't just find a .zip of the stock system and try to manually inject the APK into my /system/apps directory. I hate reinstalling all my apps, but I guess that's what it'll come to if this issue keeps happening. I was wondering when a user thread was going to be created. I simply posted here since the thread wasn't created yet, but it looks like this thread was updated. Thanks!
  20. It looks like Sprint themselves have never seen this issue before, and they just told me to troubleshoot with the Sprint Zone app. That app only has generic tips like clear app data, or clear app cache, or soft reset the phone by powering it off and taking out the battery for 10 seconds. I don't think any of those will help my issue. However, in the Settings menu of the Sprint Zone app, I found Sprint Settings -> Updates, and I unchecked that. Hopefully it stops trying to at least download the failing app now. We'll see...
  21. So it looks like it happened again this morning. This time I got a screenshot. So the error message is "Unable to install Sprint Default ." Unfortunately, it doesn't look like it's in the Play Store, and I have no idea where "Manage Packs" would be. Also, it does show the Google Now Launcher in the background, but after I click cancel, when I press the home button, it goes to the LG home screen and I have to re-set Google Now as my main launcher. Pressing Retry will retry and fail and come back to this screen. I'll be posting this to Sprint and LG to see if they know of the issue, but I'm hoping one of you guys happen to have run into this at some point, whether on this phone or another one.
  22. In my opinion, to each their own. Some people like to update, some people don't. That's fine. And to answer the question, "Why fix what isn't broken?" Major OS updates is rarely about fixing what's broken anyway. It's about getting new features, and unfortunately, that comes with bugs or useful features taken out if the developer is not smart enough to realize. Otherwise, most of the time, new OS versions come with great benefits. The update from Eclair to Froyo, for example, added their just in time compiler for better performance. Gingerbread to Ice Cream Sandwich unified the phone and tablet UIs and is essentially the major layout we see today. Jelly Bean brought Project Butter in 4.1, Android native quick settings in the notification shade in 4.2, and NAND TRIM support for performance consistency in 4.3. KitKat brought down the requirements so that lower end phones in emerging markets can run Android. Even Lollipop, with all its bugs, finalized ART, which was supposed to increase performance, and improved little things like the quick settings menu in the notification shade. In the end, it all depends on whether the owner of the device wants to upgrade or not. If you want to stay on an older firmware, that's perfectly ok. Just like how it's perfectly ok for people to upgrade if they want to. It's not really the user's fault if they run into bugs. it's on the entity providing those updates, whether that's Google, the OEM, or the network carrier. These buggy releases shouldn't be going out in the first place. Again, to this, to each their own. I'm just not comfortable opening something that's not meant to be opened, whether it's easy or not. I'm perfectly happy with upgrading to my LG G4, just like how you're perfectly happy with staying with your Nexus 5.
  23. Yeah, you do a lot of aftermarket stuff like disassembling laptops and doing thermal paste reapplication. When I build PCs, I'm a stock everything guy. I don't overclock anything or use aftermarket cooling. I'm too afraid of breaking my things even though I know other people do it.
  24. Thanks for that info. I'm definitely leaning towards the app that I uninstalled being the cause of the issue. You didn't uninstall any preloaded apps did you? I just wish I remember exactly what app(s) I touched. I don't want to factory reset my phone because I already installed all my apps and did a bunch of customizations, but it might have to come to that if I can't figure out what I did.
  25. As comfortable as I am messing with software like ROMs and using command lines (I am a firmware engineer by profession), and as comfortable as I am installing new RAM or a new HDD/SSD in a laptop or building a new desktop from scratch, I am just not comfortable popping open a phone that's not meant to be popped open by a normal consumer. That's just me. If you're fine and happy going that route, all the power to you, and I'm glad you're able to squeeze more life into the device. As I've said before, it's a great device. And even though I now have a G4, I am definitely keeping the Nexus 5 for messing around with (I already installed the Android M preview as soon as my G4 was loaded with every app I frequently use). I'm hoping the next Nexus 5 is going to be just as good for anyone going that route.
×
×
  • Create New...