Last Update Opportunity! LG to Permanently Shut Down Smartphone Servers
For many, LG is now just a manufacturer of TVs and household appliances. However, it was once considered a traditional company in the mobile phone and smartphone market. The South Koreans were not afraid of innovations and wild experiments (see LG Wing in the picture). Nevertheless, LG never really established itself in the global market. Four years ago, it discontinued its struggling smartphone division but promised continued updates. Now, even that is coming to an end.
The company will shut down its update servers on June 30, 2025, as reported by 'Android Authority.' In a press release on the South Korean support site, LG announced the discontinuation of Over-the-Air (OTA) updates, Update Center, and LG Bridge. In the future, users will no longer be able to download or install Android updates for their smartphones.
Despite the withdrawal from the smartphone market, the company made an update promise in 2021 for a range of then-current models. Premium devices like the Velvet, Wing, and V60S were to receive three version updates, and mid-range devices like the Stylo were to receive two years of version updates.
These models have not received new Android versions or security patches since 2023. However, LG's update servers remain online so users can still install the last available updates.
But that will also end as of the deadline, as LG will completely shut down the update servers. LG advises users to install the latest available software version on their devices before the deadline is reached.
Those who miss this opportunity will have to forgo updates entirely in the future. The shutdown also affects the PC software LG Bridge. This application was used not only for installing software updates but also for backing up and restoring data on LG smartphones.
The decision is not surprising. It is rather remarkable that LG offered software support for its last models for so long after exiting the smartphone race. Updates have always been a sore point in LG's history — and one of the many reasons why customers turned away from the company.
LG never firmly established itself in the smartphone market. Although it had a global market share of more than five percent in 2014 (source: Statista), ahead of HTC and Sony, growing competition from China — Xiaomi and Oppo — put increasing pressure on the company. It last claimed seven percent of the U.S. market in 2021 (source: Statista). By that time, the decision to exit the smartphone business had already been made.
The post Last Update Opportunity! LG to Permanently Shut Down Smartphone Servers appeared first on TECHBOOK.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Yahoo
26 minutes ago
- Yahoo
Google failed to warn 10 million of Turkey earthquake
Google has admitted its earthquake early warning system failed to accurately alert people during Turkey's deadly quake of 2023. Ten million people within 98 miles of the epicentre could have been sent Google's highest level alert - giving up to 35 seconds of warning to find safety. Instead, only 469 "Take Action" warnings were sent out for the first 7.8 magnitude quake. Google told the BBC half a million people were sent a lower level warning, which is designed for "light shaking", and does not alert users in the same prominent way. The tech giant previously told the BBC the system had "performed well". The system works on Android devices, which make up more than 70% of the phones in Turkey. More than 55,000 people died when two major earthquakes hit south-east Turkey on 6 February 2023, more than 100,000 were injured. Many were asleep in buildings that collapsed around them when the tremors hit. Google's early warning system was in place and live on the day of the quakes – however it underestimated how strong the earthquakes were. "We continue to improve the system based on what we learn in each earthquake", a Google spokesperson said. How it works Google's system, named Android Earthquake Alerts (AEA), is able to detect shaking from a vast number of mobile phones that use the Android operating system. Because earthquakes move relatively slowly through the earth, a warning can then be sent out. Google's most serious warning is called "Take Action", which sets off a loud alarm on a user's phone - overriding a Do Not Disturb setting - and covering their screen. This is the warning that is supposed to be sent to people when stronger shaking is detected that could threaten human life. AEA also has a less serious "Be Aware" warning, designed to inform users of potential lighter shaking - a warning that does not override a device on Do Not Disturb. The Take Action alert was especially important in Turkey due to the catastrophic shaking and because the first earthquake struck at 04:17, when many users would have been asleep. Only the more serious alert would have woken them. In the months after the earthquake the BBC wanted to speak to users who had been given this warning - initially with aims to showcase the effectiveness of the technology. But despite speaking to people in towns and cities across the zone impacted by the earthquake, over a period of months, we couldn't find anyone who had received a more serious Take Action notification before the quake struck. We published our findings later that year. 'Limitations' Google researchers have written in the Science journal details of what went wrong, citing "limitations to the detection algorithms". For the first earthquake, the system estimated the shaking at between 4.5 and 4.9 on the moment magnitude scale (MMS) when it was actually a 7.8. A second large earthquake later that day was also underestimated, with the system this time sending Take Action alerts to 8,158 phones and Be Aware alerts to just under four million users. After the earthquake Google's researchers changed the algorithm, and simulated the first earthquake again. This time, the system generated 10 million Take Action alerts to those at most risk – and a further 67 million Be Aware alerts to those living further away from the epicentre "Every earthquake early warning system grapples with the same challenge - tuning algorithms for large magnitude events," Google told the BBC. But Elizabeth Reddy, assistant professor at Colorado School of Mines, says it is concerning it took more than two years to get this information. "I'm really frustrated that it took so long," she said "We're not talking about a little event - people died - and we didn't see a performance of this warning in the way we would like." Google says the system is supposed to be supplementary and is not a replacement for national systems. However some scientists worry countries are placing too much faith in tech that has not been fully tested. "I think being very transparent about how well it works is absolutely critical," Harold Tobin, director of the Pacific Northwest Seismic Network, told the BBC. "Would some places make the calculation that Google's doing it, so we don't have to?" Google researchers say post-event analysis has better improved the system - and AEA has pushed out alerts in 98 countries. The BBC has asked Google how AEA performed during the 2025 earthquake in Myanmar, but has yet to receive a response. How a grieving mother exposed the truth of Turkey's deadly earthquake Beverley man remembers family lost in Turkey quake Sign up for our Tech Decoded newsletter to follow the world's top tech stories and trends. Outside the UK? Sign up here.
Android Authority
an hour ago
- Android Authority
Samsung may be killing bootloader unlocking on all phones with One UI 8
Joe Maring / Android Authority TL;DR Samsung appears to be disabling bootloader unlocking in One UI 8 on more devices than before. Previously, only US models lacked the OEM Unlock toggle, but the restriction now seems to be spreading to global models as well. A contributor on XDA Developers discovered that Samsung is likely stripping out the necessary code to unlock bootloaders entirely. Samsung might be quietly locking down its phones even more tightly with the One UI 8 update. A new report from an XDA Developers contributor reveals that Samsung appears to be removing the ability to unlock the bootloader on more devices, including international versions that previously supported it. Samsung phones in the US already lack the 'OEM Unlocking' toggle in Developer Options, effectively preventing users from unlocking the bootloader and installing custom ROMs. But now, it looks like that restriction could apply globally. What's changed? The contributor, salvo_giangri, discovered that Samsung has added a line to the device's bootloader configuration: This line tells the Android system whether the device is allowed to unlock the bootloader. If it's set to 1, the Settings app won't even show the OEM Unlock option, which is the first step in unlocking a phone. In the latest One UI 8 firmware, this line is present even on non-US devices, indicating that the restriction is no longer region-specific. We checked and can confirm that our non-US Galaxy Z Fold 7 does not have the 'OEM Unlocking' toggle in Developer Options. Some folks think this could be a mistake on Samsung's part. However, those running the One UI 8 beta build also report that the option is missing from their devices. Unlocking the bootloader is essential for enthusiasts and developers who want to install custom ROMs or kernels, gain full root access to their devices, or further customize their phones. If you're someone who loves customizing your phone or values the freedom to tinker with Android, then this is a significant step back from Samsung. Anyone planning to update to One UI 8 or buy a new Samsung device running Android 16 should know that this restriction may apply to their devices. That said, we'll reach out to Samsung for an official confirmation on the matter. For now, the bootloader on your current Samsung devices that are not running One UI 8 should still be unlockable, but with new updates and devices, that may no longer be the case.
Android Authority
2 hours ago
- Android Authority
Google says it's working to fix voice commands for your smart lights
Lil Katz / Android Authority TL;DR Google has acknowledged a bug affecting voice commands for smart lights. The company says it is aware of the issue and will share an update soon. Many users say they can still control lights via the Google Home app, but not through Assistant voice commands. Google has confirmed it's investigating a bug preventing users from controlling their smart lights through Google Assistant voice commands. We first reported on the issue over the weekend, as user complaints have continued to pile up on Reddit and Google's support forums in recent days. Android Authority's Rita El Khoury also experienced the problem firsthand, noting that her Nest Audio speaker stopped responding to voice commands to turn off the lights. In a comment posted on Reddit, the official Google Nest account has now addressed the problem: We're aware of an issue with using voice commands to control some lights. We'll share an update as soon as possible, thanks for your patience. While Google hasn't provided a timeline for a fix, it's clear the issue is more than a small glitch. Affected users report various problems, including Google not recognizing light groups, turning off the wrong lights, or responding with silence when given commands like 'Hey Google, turn off the lights.' Most users say the lights can still be controlled via the Google Home app, suggesting that the issue lies specifically with Assistant voice functionality. Some users have found workarounds, such as syncing devices again or removing and re-adding their lighting services, but results vary. 'I had this problem too. I saw someone else post a fix earlier today (Google must have done something that messed things up). You just need to reconnect the service you use for your lights. Go to Google Home app, click the + button to add a new device. Go to the works with Google section and reconnect any of the services you use for the lights. That should work… Maybe,' a user noted on Reddit. However, this may not be an easy fix for those who have multiple lights connected throughout their home. The bug comes at a difficult time for Google's smart home ecosystem, which has been under increased scrutiny from users citing reliability issues. Google has also promised major improvements to the platform in the fall. Until then, users will have to wait for an official fix for this particular problem related to voice commands for connected lights or rely on manual controls as a workaround.
