Constant shut down of LG V50 when using certain features - LG V50 ThinQ Questions & Answers

Hi everyone, so like the title of the thread suggest. My LG V50 (SKT model) gets shut down everytime I on the Wifi function, use the gallery app made by LG (the google photos app works fine), music app by LG (the google play music works fine too) as well as the file manager app on the phone. Whenever I click on them my phone will automatically shut down after a few seconds and I have to manually on it back up. May I know what is the issue with my phone? I've tried to flash some LG official roms using LG UP but the issue seems to be consistent...Thank you very much for reading this and I hope any of you will be able to let me know the potential issues that my phone might have.

Related

[Q] Any Moto G (LTE) owners who got problems with spotify?

So I just got my new Moto G (the one with LTE and a microsd card reader) and spotify just won't work with it!
When I start it the screen is the spotify grey background but with the settings tab to the left. However I cannot press anyhting or use the app at all. The phone is on android 4.4.3 and I'm using the latest Spotify Music app.
Sometimes I can get into the app and play a song but after a short while it stops and freezez up and only a reboot can fix it. Open the recent view and killing the app never works. I must reboot it in order to use the phone at all. I have cleared all the caches serveral times and installed and uninstalled it.
Also now I'm not able to play any music at all the app crashes constantley.
Just wondering if there is anyone else having these problems on the moto g and the moto g lte version? Seems very odd, never experienced this problem on any android phone before.
I own a Moto G LTE too and Spotify works fine on it. Maybe you are experiencing a microsd issue (did you insert it correctly? At which class does it belong to?). Try to remove it from the phone and then try to open spotify again.

[Completed] [Q] Restore 3G service to TextNow Moto G 1st gen?

So I've had this refurb 1st gen Moto G CDMA from TextNow for around 6 months now.
This morning I went to check my texts and notices that the screen was sitting at the blue motorola pearl.
It would occasionally restart and halt at a black screen after the blue pearl, or restart and the boot animation would be severely corrupted. Sometimes it would make it to Android but it would be incredibly unstable with random services and apps crashing for no apparent reason. I have never tried to root it, flash a custom ROM to it, or anything of the sort.
However, did come with an unlocked bootloader.
The only app I've ever installed to it was Facebook Messenger.
Figuring that the phone was bricked and after reading plenty of tutorials from this forum I decided to flash Cyanogenmod 11 to it (12.1 would not work because the bootloader was an incompatible version) using TWRP.
It worked, well mostly anyway. Upon start up I noticed that it would not connect to my carrier. WiFi works fine, it just won't connect to 3G for anything.
I've read that updating Profile and PRL will fix this but I can't find the option or it doesn't exist.
I feel like I may have missed something or messed up a file somewhere on my phone.
On top of that, com.android.systemui keeps crashing if I let the screen go to sleep.
Does anyone have any idea on how to restore 3G service to a TextNow device and stop systemui from crashing?
Hi,
Thanks for using XDA Assist Kindly post here Moto G Help and Troubleshooting so that experts using your device can help in better way
Good Luck!
Thread Closed.

Original Shield Tablet Freezes When Connected to WiFi

Hi there!
I've contacted nvidia regarding this issue (reps seems oblivious) and posted it on their official forums to no avail, so I'll try and give it a shot here.
Basically whenever my tablet connects to WiFi after being disconnected for some time (a few hours to a few days), the tablet freezes when it downloads notifications. The freezes can be minimal (like a 5 second freeze) or be quiet substantial (it can lock up for as long as 10 mins). Once all notifications are downloaded and displayed, the tablet then performs like a charm. I even got my tablet replaced from nvidia and it has the same problem as the one I sent in. Uninstalling Facebook and Facebook Messenger improves performance drastically, but when my tablet checks for notifications it freezes still freezes for a few seconds (with Facebook installed, it could lock up for 10 mins and crash the launcher multiple times). Running on max performance did nothing. I'm really curious if this is a hardware or software issue since some people doesn't seem to have this problem.
I'm running on nvidia's stock firmware (4.2) unrooted.
So here is my question. Have any of you guys experienced this problem? Were you able to solve it? How did you solve it (did a custom rom solve this)?
The main reason why I haven't installed a custom rom yet is because I use the stylus frequently and I use the touch-block feature in nvidia's stock roms and couldn't find ports of it.
Here is a video of the issue. (youtube.com/watch?v=cJrUPV7mY6s) Now there are a lot of widgets on the video, but I assure you removing all of them does nothing. I tried.
Facebook Messenger. That says it all. What other apps have you running in the background?
This definitely sounds like a software issue to me.
Maybe you're being hijacked. Who knows.
I've had this same issues since I got the tablet (K1). System reset, no non-Google apps. Happens regardless of FW; I'm on the latest update. Don't be quick to blame the OP.
Basically, every time the tablet gets a new network connection, the system hangs and becomes unresponsive for 10 seconds to 2 minutes at a time. It's obvious that it's updating all the apps' network requests. However, the thread priority should make the system hang. I've only seen this issue on the K1; never on any other Android device. Either they're using a custom network stack, or they've messed with networking priorities.
I'm on the latest update
Click to expand...
Click to collapse
Of Facebook Messenger? Or OS? Or all apps?
Either way, it makes no matter no such issues on Lollipop. I am just saying.

Here WeGo non Samsung phone

So it seems that the Here wego maps/navigation app is not available for the s3 if you aren't using a Samsung phone. (I happen to use an LG v20)
Has anyone found a way to side load the app? Or what is the best alternative maps application for the s3?
Ok I found a way around the issue for anyone watching this thread... It's a little crazy and not for everyone.... I happen to have a Samsung Galaxy S7 as a work phone... I connected my S3 to that phone, where it installed HERE by default.... I then backed up the watch to my samsung account and then reconnected the watch to my LG V20 and restored the backup which included HERE.... Boom.... Problem solved
That's strange.. I got my S3 R-760 back in October 2017 from the UK. Immediately paired to a Sony Z5 and has been like that ever since, even after the ROM updates. One of the first things I did was to install HERE. Can't remember how exactly but it wans't a hassle so I assume straight from the watch or the store. I guess it has been removed after I installed it. Using it now as a standalone, no connection to the phone is required, just direct connection to the internet via wifi or hotspot. Of course I do not have the convenience of using it through the phone which could make it easier to search etc, but it is good enough.
Nice workaround you found, but for those that do not have the option of a Samsung phone, this thread could help: https://forum.xda-developers.com/gear-s3/help/wego-t3724511/page3
Hmm - I downloaded from Google onto my OnePlus 5T, installed on watch from Gear store and that was it.
UK / stock OnePlus 5T

Phone functionality intermittently lost after upgrading to P

If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.

Categories

Resources