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
dsimonse

Wireless connect to internet

Question

Hi,

 

I bought a LG 55LB730V and I connected it via ASUS RT-N56U to the internet. Both devices has the latest SW release i.e. TV: 04.30.16, ASUS: 3.0.0.4.376_1665.

The network gets connected according to the Advanced settings but I'm not able to surf. And using the Smartshare on my PC works very random and secondwise.

 

LG-store reports not connected to the internet.

 

Any suggestions?

 

Dennis

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts



  • 0

if your neighbour's on same wifi channel as your wifi router it could be causing interference and forcing the connection to drop.

 

The best thing would be downloading this to a laptop > http://nutsaboutnets.com/netsurveyor-wifi-scanner/   and walk around the house,  it will display every wifi router it picks up and tells you which channels are available.

 

you would just need to login via a webpage to your router to change to a clear wifi channel - any kind of interference will cause a connection to keep dropping just like you outlined.

 

----------

 

The next choice would be buying HomePlugs, they plug into the electricity and then into your tv - they don't use wifi so you won't get any interference.  

Share this post


Link to post
Share on other sites
  • 0

Hi,

 

I tried to move to channel 2 and 3 (2.4Ghz) and there I get some internet connection, but very unstable. I even swiched to 5Ghz and got a little more improvements, but still very unstable.

The ASUS used to be a good performing router but now I get this unstable connection.

Still believe ther's something miss-matching btw the router and the TV.

 

//Dennis

Share this post


Link to post
Share on other sites
  • 0

Had the same problem on a new LG WebOs TV, which connected OK to the wifi router but no internet access.  Not much help from the LG support (Denmark) who blamed the router (which works fine with every other one of the twenty other devices connected to it, including smart-tvs, droid and iphone, pc, iot gadgets...).

SOLVED by:

Settings - Network - advanced

Uncheck automatic

Change the DNS  server from the default (automatic, identical to the router IP, 192.168.1.1) to one of the DNS servers suggested in http://www.snaphow.com/4402/list-of-top-4-alternative-dns-servers-to-your-isp/.  The openDNS server 208.67.222.222 worked fine for me.

 

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

  • Similar Forum Topics

    • [pivotCE]LuneOS November Stable Release: Doppio

      The very long wait is over #LuneOS and #webOS fans! We’re finally back with a new release called “Doppio” which we believe will be a milestone in terms of developments and the way forward! So you’re wondering what we’ve been up to for the past year? Well, actually a whole lot to be honest! We have upgraded the bluetooth stack from BlueZ4 to BlueZ5 which required quite some work to the kernels. This has been successfully completed for the Nexus 4 (Mako) and Nexus 5 (Hammerhead); unfortunately to date we haven’t been able to get this to work on the Touchpad (4G) (Tenderloin). We have been working closely together with the Halium project and have made further integrations between LuneOS and Halium reducing duplication between the projects and using a single source where possible. This all to be more easily integrated, and to facilitate ports to newer devices. We have upstreamed our kernel patches (mainly to fix GCC 5/6/7/8 compatibility) to Halium so we can use a shared kernel for our targets. Talking about new devices we’ve been working on: Since Google dropped the (budget) Nexus line and launched the (premium) Pixel line, we’ve been looking for other targets that are easily available, budget friendly and have good community support. We quickly ended up with Xiaomi which makes phones with decent specs, unlockable bootloader (the process is a bit tedious, but it’s do-able) and the phones give very good value for money. This has resulted in us independently working on 3 different Xiaomi devices being the RedMi Note 4x (Mido), RedMi 5 (Rosy) and Mi A1 (Tissot).  These are all Aarch64 devices using the Snapdragon 625 chipset. We didn’t have any Aarch64 devices before and also they are based upon Halium 7.1 (Android 7.1) while all our previous targets were based upon Halium 5.1 (Android 5.1), so this brought a whole bunch of new challenges. There are still a few rough edges, but audio, sensors, wifi and bluetooth are now working. There was also quite some porting work done for some of the other Halium supported targets such as the OnePlus X (onyx), Google/Huawei Nexus 6P (angler) and Motorola G4 (athene). These are currently in various stages of development, whereby OnePlus X is the most mature. The Xiaomi Mi A1 is a strategic device for us which we chose in cooperation with LG to work on to get LuneOS working and also as a target for LG’s webOS OSE (Open Source Edition). LG’s release of webOS OSE came as a surprise to us, however it has great potential. Though the initial release of webOS OSE was very limited and therefore limited use case for people not being very familiar with webOS, it does offer a lot of potential for us. webOS OSE is basically 5 years of development of the core webOS bits since Open webOS was released. It has been deployed in millions of LG TV’s since and offers great improvements in terms of reliability and functionality. The big downside however is that there’s no record of the changes between Open webOS and webOS OSE, so this is making the migration a bit more challenging. Early June the LuneOS team met with LG in Paris to discuss collaboration between our teams. As a result of this we have chosen the Xiaomi A1 as a device to port LuneOS to. This is now at a level similar to our other targets. After this release we will therefore focus on migrating our Open webOS components to the updated components provided by webOS OSE. This will bring quite some challenges and hurdles along the way, however we’re positive that we can complete this migration and it will bring a lot of improvements in terms of code quality, stability, functionality and reducing the need for maintaining a lot of these components ourselves since we can share a common codebase with LG’s webOS OSE going forward. LG has a very clear vision in mind for webOS. Since the initial release in March, a roadmap has been published and LG has pushed out 4 releases since the original release of webOS OSE. The following items on our to-do list will be where we focus next: Migration of Open webOS components to the newer webOS OSE components. Make the VirtualBox image work with a newer MESA. Migrate to Yocto Sumo/Thud release. Messaging improvements. Camera improvements. Fix known issues on the various targets. Bring back official support for Touchpad 4G (current build works on Touchpad 4G but only WiFi). Known issues: Node-SQLite3 is currently not working. Components using Node-SQLite3 have switched to an alternative storage method for now. Focus bug on input fields. You can work around this by hiding the virtual keyboard and pressing the input again. Random issue with virtual keyboard not showing on Aarch64 devices. Changelog Applications: Settings: Add QML variant, enable manual time and date in Setings. org.webosports.cdav: Add CLEANBROKEN User Interface: luna-{sysmgr,sysmgr-common,appmanager,next}, mediaindexer: fix build with Qt 5.11. luna-{webappmanager,qml-launcher} org.webosports.app.{browser,firstuse}: fix build with Qt 5.11. luna-next-cardshell: add runtime dependency on qtmultimedia-qmlplugins, luneos-components. luneos-components: drop build time dependency on qtwebengine, switch to Mer’s bluezqt System Level: luna-next: Add config for onyx, Add QT_OPENGL_NO_BGRA and remove QT_ENABLE_GLYPH_CACHE_WORKAROUND android-gadget-setup: fix functionfs test android-tools: fix compatibility with adb 5.1.1 android-tools-conf: Fix the machine check, Don’t patch script for tenderloin base-files: provide a common fstab for all LuneOS devices bluez: switch from bluez4 to bluez5 bluez5: Fix patch so it will work for RaspberryPi3, make firmware search case insensitive connman: Add connman-tools, connman-tests and connman-wait-online, Update to 1.35 distro: luneos: switch release name to Doppio environment.conf: Add QT_ENABLE_GLYPH_CACHE_WORKAROUND=1 fingerterm: Update to upstream and drop patch, use LiberationMono font funyahoo-plusplus: Bump SRCREV https-everywhere: Bump SRCREV hunspell-dictionaries: Update to latest version imaccountvalidator, imlibpurpleservice: Drop unsupported protocols initramfs-boot-android: add A/B partition support, boot into built-in recovery when no skip_initramfs, get Halium’s init script from GitHub, improve panic scenario in init.sh, use /userdata instead of /android/userdata, Various fixes to init.sh kf5bluezqt-mer: fix package content with empty QT_DIR_NAME libconnman-qt5: fix initial value of “connected” property libhybris, qtbase: don’t use += together with _append libhybris: Bump SRCREV, Set –enable-arch=arm64 for aarch64, Drop –with-default-hybris-ld-library-path and bump SRCREV libpbnjson: use Unix Makefils OECMAKE_GENERATOR lsb: fix luneos-version content luna-(web)appmanager: use /etc/luna-next/qtwebengine.conf luna-init, luna-sysmgr: Bump SRCREV and adjust file installs luna-init: Fix incorrect {, Install CustomerCareNumber.txt and cust-preferences.txt luna-prefs-data: Bump PV to be in sync with luna-prefs luna-sysmgr: Cleanup recipe luna-sysmgr-conf, nyx-modules: fix rosy values, Add initial files for athene and onyx target, Cleanup recipe and fixup defaultPreferences-platform.txt luna-universalsearchmgr: inherit webos_systemd luna-webappmanager: bump SRCREV luneos.inc, connman: Build & deploy VPN plugins luneos: inherit remove-libtool luneos: update SANITY_TESTED_DISTROS luneos-dev-image: tell Halium to mount rootfs rw luneos-emulator-appliance: update a bit luneos-features, connman: Add support for NFC using neard luneui-example-image: add few more packages, add more packages for testing, add vboxguestdrivers, v86d, add very small (fast to build) test image maliit-framework-qt5: set XDG_RUNTIME_DIR in conf file meta*: enable gbm meta-webos-ports: Add configuration files for Tissot, Update classes with info from webOS OSE mido, tissot: Fix path for CHARGER_AC_SYSFS_PATH mido: Initial configuration files mobile-broadband-provider-info: Bump SRCREV mojomail: bump SRCREV to fix build with boost-1.67.0, Switch back to webOS-ports/master branch nemo-qml-plugin-dbus: Update to latest version from upstream, fix package content with empty QT_DIR_NAME node-sqlite3: Bump version nyx-conf: do not let keys module watch over the touchpanel nyx-modules: Fix devices names in cmake files ofono: Update to latest version from upstream and enable Python 3 tests onyx: Enable power button packagegroup-luneos-development: include QML settings app packagegroup-luneos-extended: add android-kernel-bootimg, Add qtconnectivity, Add WIP targets and more documentation, Build bluez5 for all targets, include libpci for qemux86, move android-kernel-bootimg phonesim: Fix build with empty QT_DIR_NAME, refresh patches with devtool, update to latest revision from git pidgin-sipe: backport a patch to fix build with gcc8 pulseaudio-distro-conf: Add support for Xiaomi A1 (tissot), Add webos-system.pa for mido target pulseaudio-modules-droid: bump to 10.0.73, refresh patches with devtool, remove tenderloin CFLAGS purple-skypeweb: Bump SRCREV python-tz-native: Update to 2017.2, Fix typo in SRC_URI qt5: upgrade to 5.11, upgrade to 5.11.1 qt5-qpa-hwcomposer-plugin: fix package content with empty QT_DIR_NAME, hwcomposer_backend.h: Fix cast from ‘void*’ to ‘unsigned int’, remove tenderloin CFLAGS qtbase: Add patch to fix quirks with newer Adreno GPU’s, refresh patches, remove TLS patch on Halium 7.1 targets, temporary fix for SIGBUS crash on Android devices qtlocation: refresh patch qtscenegraph-adaptation: Bump SRCREV qtsensors-sensorfw-plugin: fix build with empty QT_DIR_NAME qtvideo-node: fix package content with empty QT_DIR_NAME qtwayland: add qwayland-server-surface-extension.h, wayland-surface-extension-server-protocol.h to sync.profile, bring QWaylandExtendedSurface back for luna-next, drop patch applied in 5.9.3, refresh patches for 5.11.2 qtwebengine: add libpci to RDEPENDS, Drop patch for libEGL and libGLES2, fix filename in SRC_URI, Fix patch for additionalFeatures, refresh patches, Remove PalmServiceBridge, replace EXTRA_QMAKEVARS_CONFIGURE with PACKAGECONFIG, squash a few of chromium patches for easier maintenance recipes: drop unnecessary FILES_${PN}-dbg variables, use oe.utils.conditional instead of deprecated base_conditional sensorfw: Bump SRCREV and drop patches now merged upstream voicecall: Update to latest version from upstream webos-systemd-services: Drop installation of luna universalsearchmgr.service android-headers: Add headers for Halium-7.1, common recipe for Halium-5.1 headers, make it possible to tweak android-config.h per machine, Use Halium Headers android-headers-halium: set preferred version android-headers-tenderloin: fix patches to match Halium’s android-kernel-bootimg: dedicated recipe for creating boot.img, minimal support for A/B partitions android-system: Add missing groups, also mount /persist when it exists, cleanup old hal-hybris overlay code, don’t manage ramdisk unpacking, fix lifecycle of lxc container, Remove installation of non-existing files, simplify usage of Halium, start sensorfwd after android container, use pre-start.sh from Halium, wait a bit for the sensors to be ready android-system-image: use system.img directly, Change wop into luneos, convert the sparse image if needed, create /userdata, Update halium bits to halium version numbers base-files: use system.img directly android-tools: remove, since now in meta-oe base-files,android-system: Android partitions are now mounted by Halium’s initrd base-files: add /system/lib64 in LD_LIBRARY_PATH hammerhead, mako: Add NFC as machine feature
      Include android-kernel-bootimg for each MACHINE that needs it initramfs-android-image: make it possible to add content libhybris: provide also virtual/mesa and set PREFERRED_PROVIDER for all android devices linux-lg-{mako,hammerhead},linux-hp-tenderloin: backport 2 changes to fix build with gcc8 mako, hammerhead: Use upstream kernels which now have our patches included mako: Fix the kernel build meta-*: set PREFERRED_PROVIDER for libgl and libgbm for all android devices meta-{asus,hp,huawei,lg,motorola,oneplus,xiaomi}: remove fstab overload meta-android: initramfs-android-recovery: add inc, remove leftover from android-tools removal meta-hp: migrate tenderloin to use Halium’s init meta-oneplus: Fixes for onyx target to make build work meta-smartphone: Add meta-huawei layer with Angler target, udev-extraconf: Uniform naming scheme for device udev rules and update udev rules meta-xiaomi: add initial support for rosy (Redmi 5), Get image for Tissot building, Initial work for Xiaomi A1 (tissot), mido fix persist partition number in fstab, mido use correct wlan module name, tissot: add initramfs-android-recovery, tissot: enable permissive SELinux, tissot: ignore other parameters from bootloader, tissot: switch to cm-14.1 kernel to fix wifi Migrate LuneOS targeted machines to using android-kernel-image systemd-machine-units: fix bluetooth for hammerhead, fix bluetooth for mako The usual 1. Sign up for the bug tracker 2. Get involved and 3. Join the mailing list Download and Install Feel free to download the updated builds to get started. Tenderloin, Mako, Hammerhead and Tissot remain our focus for now, but the emulator, Mido & Rosy work too. Please note that in order to use the latest stable builds Nexus 4 (Mako) and Nexus 5 (Hammerhead) you need to flash the CM 12.1 images first using CWM/TWRP. In order to do so, you might be required to do a “factory reset” or at least “wipe cache”. CWM/TWRP will indicate when this is needed. After successfully flashing CM 12.1, make sure to boot it at least once before going back to CWM/TWRP to flash the latest LuneOS image! We have provided links to CM 12.1 for these 3 images on our device pages below. Installation instructions for TouchPad (Tenderloin), Nexus 4 (Mako), Nexus 5 (Hammerhead) and Emulator are on the wiki. And remember we don’t do timelines. Don’t forget to contact us with any questions and feel free to join the discussion on the webOS Nation forums. Catch us on Twitter @webosports on IRC: Freenode:#webos-ports or email [email protected] We will see you shortly again with a new release! Picture Credit: Chevanon. Cropped & flipped. Text added. Related posts: LuneOS July Stable Release: Cortado LuneOS February Stable Release: Chai Latte LuneOS September Stable Release: Decaf View the full article

      By pivotCE, in pivotCE News

      • 0 replies
      • 93 views
    • Question: Super slow internet (WiFi) when streaming

      Hi, I recently bought an LG UK6500PLA TV (my first LG), but I have a difficult time streaming content (Wifi connected), e.g. Netflix series is streaming in low resolution.  The router is only 10 feet away from TV (but ethernet is not an option) and uses a 5GH frequency range. I have tried making a speed test at fast.com, for both the TV (through the Webbrowser) and for my laptop and iPhone. The speed test for TV showed 2.5 Mbps and my laptop and iPhone showed 110 Mbps. Can there really be such a big difference? I am starting to wonder if this might be a warranty issue? Do any of you guys have experience with bad Wifi reception on your LG TV or have any suggestions on how to fix it?    Br, Nick

      By NickL, in LG webOS Smart TV Questions

      • Awaiting best answer
      • 0 votes
      • 5 answers
    • webOS 4.0 confirmed within iOS and Android App Release Notes

      Thanks to @Peter Alexander and @SSM we have confirmation of webOS 4.0 compatibility within the release notes and information listed for their respective apps in the below topic.   We've confirmed the iOS version changes:   We've also confirmed Android: Both version updated were added this week. We are waiting for an official webOS 4.0 press release from LG and additional information on what models are supported.

      By Alex, in LG webOS Smart TV Discussion

        
      • 3 replies
      • 6,350 views
    • Network connection issues. LG Content store doesn't connect.

      I did a refresh of my LG TV 3 days ago. Sold the old LG 47" 3D LED TV and bought new 55" LG Super UltraHD TV with WebOS. I believe, the biggest con of this new TV is WebOS. Its totally frustrating. Sorry for WebOS fans. It isn't that smart and functional they way it looks. The problem I having since 3 days and being a network engineer, I am unable to solve a network issue myself which is even more frustrating for me. Ok, let me explain the issue. The TV when installed was connected to LAN cable to my router which has direct internet connection. The TV works and none of the apps were working. Basically TV wasn't able to connect to internet via apps. If i open web browser, it was working fine with all webpages showing correctly. I'll skip the part of contacting LG support which was useless. All troubleshooting steps like resetting, formatting, changing time zone, location, region was done but no luck. Finally I connected the TV via mobile hotspot and it just worked which gave me the clue that some ports are being blocked by my ISP or router. My internet setup is this way. Internet cable from ISP -> ISP Modem (can do NAT and work as router) - WiFi Router (NAT, DHCP, etc) -> all LAN clients. I put my LG TV in DMZ, opened all ports, etc but no luck. Then I converted my ISP modem as router and connected the LG TV directly to it and it started working..!!! My WiFi Router is TP-Link Archer C7 and I was using stock firmware. Thought it was creating issues and I installed DD-WRT, Open-WRT but no luck at all. The apps which were installed in TV when TV was connected directly to modem are still working fine. Youtube, Plex, Netflix, etc all are working but when I open LG Content Store, it just refuses to load. I am not sure what wrong my TP-Link router is doing. There is something wrong with the LG TV content store. If it requires to open ports, then I would like to know which ones. Sorry for the long port, may be my frustration of 3 days with no luck.!!  

      By akhil7j, in LG webOS Smart TV Discussion

        
      • 3 replies
      • 789 views
    • Question: Cant watch internet programmes

      Every time i try to watch netfilix or any other prigrammes on my smart tv. It restarts saying its going to  free space but still dont let me watch the app

      By Maxwell loxley, in LG webOS Smart TV App Questions

      • Awaiting best answer
      • 0 votes
      • 0 answers


×