Quantcast
Jump to content

  • Join Today, It's Simple and FREE!

    Register now to gain access to our webOS user support forum. Once registered and logged in, you will be able to post a user to user support request topic to this site or reply to existing topics posted by other users. You can also take part in our other webOS user forums. You'll be able to customize your profile, receive reputation points, while also communicating with other members via your own private inbox, plus much more!

  • 0
ChilinMichael

55UH6030 Crashing/Rebooting

Question

Have a couple of days old 55UH6030, love the picture, etc, all seems to work well except seemingly a few times while watching Netflix (webOS app), the TV freezes and then fully reboots (You see the light turn on for it being off, then starts back up again).  Any ideas?

Share this post


Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0

That's interesting, have you tried removing and reinstalling the Netflix app? Does it happen with any other apps?

Share this post


Link to post
Share on other sites


  • 0

I ended up factory resetting the TV as per LG support chat, no dice.  Still crashes in Netflix, also Amazon Prime video and Google Play video.  They are now sending a tech to repair the unit stating this shouldn't happen. 

Share this post


Link to post
Share on other sites
  • 0

Hi guys,

there hasn't been much movement on that topic for some time, but I just recently bought a 55UH625V and see similar issues.
The TV itself and WebOS is pretty nice (thats why i bought the thing in the first place), even though webOS UI is rather laggy.

But the really annoying thing are these random freeze/reboot actions. It randomly crashes in different apps (netflix, amazon, ...) even when watching DVB-T2 content (but i assume that DVB-T2 is also just implemented as app in the system) ...

My TV is on the latest available firmware since i set it up. Given the fact that this doesn't only happen in one particular app i'd expect the problem being located in the OS layer ...
are there any log data a user can access in order to identify the problem?

cheers

Share this post


Link to post
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×