LG K10 problems


Recommended Posts

I have been using the K10 for around 3 months and have been plagued with issues since I started using it. Lately I have been plagued with horrible battery life, I even bought a new battery to check (no change), and the biggest problem I am having is 2 issues: #1)I have my Asus Zenwatch paired to it and randomly the phone loses it (I get the pairing request message) and #2) I use an app for our local bus transit to pay fares, and lately it seems to loose the fact that it is logged in and I have to go through the whole 2fa to login again (takes around a min or so) and I am not aware of the issue until I attempt to use it. I really have no idea what is wrong with the phone and since I can not figure out what is causing the issues I can not fix them. Does anybody have any ideas what to do?

Link to comment
https://www.neowin.net/forum/topic/1346196-lg-k10-problems/
Share on other sites

I've had problems on and off with Android Wear 2.0 disconnects using another phones so the Zen Watch issue may NOT be your K10. Since my wife and I got the Wear 2.0 update, we have had way more disconnects/re-pairing prompts than before.  We use different phones, with different versions of Android. My watch is an LG G Watch R and hers is a Moto 360 2nd gen. The only thing in common is Wear 2.0 so that's likely the issue with the watch. As for the bus app, can't say but that sounds like a bad app update. 

 

As for the battery, one thing you can do is start the phone in safe mode and watch your battery usage. I don't know what version of Android you are running so that will factor in. Doze in 6.0 wasn't too bad. Got better in 7.0. In safe mode with the phone in standby, you shouldn't see drastic battery drops. If you do, its the phone. If you do not, then you have a bad app (or two or several) that aren't sleeping correctly.  Check your awake time in the battery stats. Ideally it will match closely to your screen time. If you have a lot of 'awake' time that doesn't correspond to screen time, you have a bad app. 

 

Now finding the bad apps can be tricky without rooting your phone. Best is to run your phone as normal and when you see that awake time sticking, start killing apps (force stop) one at a time and wait/watch.   

1 minute ago, Zag L. said:

I've had problems on and off with Android Wear 2.0 disconnects using another phones so the Zen Watch issue may NOT be your K10. Since my wife and I got the Wear 2.0 update, we have had way more disconnects/re-pairing prompts than before.  We use different phones, with different versions of Android. My watch is an LG G Watch R and hers is a Moto 360 2nd gen. The only thing in common is Wear 2.0 so that's likely the issue with the watch. As for the bus app, can't say but that sounds like a bad app update. 

 

As for the battery, one thing you can do is start the phone in safe mode and watch your battery usage. I don't know what version of Android you are running so that will factor in. Doze in 6.0 wasn't too bad. Got better in 7.0. In safe mode with the phone in standby, you shouldn't see drastic battery drops. If you do, its the phone. If you do not, then you have a bad app (or two or several) that aren't sleeping correctly.  Check your awake time in the battery stats. Ideally it will match closely to your screen time. If you have a lot of 'awake' time that doesn't correspond to screen time, you have a bad app. 

 

Now finding the bad apps can be tricky without rooting your phone. Best is to run your phone as normal and when you see that awake time sticking, start killing apps (force stop) one at a time and wait/watch.   

The phone is running Android 7.0.

Is Doze an app? As far as rooting the phone, I have tried but can not seem to do it.

Doze is the sleep system in the OS. If you are on 7.0, Doze (sleep) should be very easy to see on that battery monitor. I'd not root at this point as its probably not needed - at least yet. When I let me phone sit for any period of time with the screen off, the battery monitor should almost be a flat line. If yours isn't, test in safe mode for 30 minutes or so to see if you get that flat battery consumption line.  Remember, you need to just let it sit idle with the screen off. If you get that flat battery line in safe mode, you definitely have a rouge app with bad wake events. If you do not get that flat consumption line in safe mode, your phone does have some issue. 

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • In the boot options in the UEFI is set to legacy or CMS? It needs to be set to UEFI if it's not already.
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      467
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!