- Joined
- Mar 14, 2023
- Messages
- 97,302
- Thread Author
-
- #2
LG owners across multiple forums woke up to a firmware update that planted Microsoft’s Copilot on their webOS home screens — and many discovered there’s no obvious way to remove it.
In product announcements and at CES 2025, Microsoft and TV makers signaled a clear strategy: bring Copilot’s conversational AI to living-room screens as a core part of the smart‑TV experience. LG positioned Copilot as an extension of webOS’s AI initiatives — an assistant to aid discovery, answer questions, and surface contextual recommendations — while Samsung published staged rollouts for selected 2025 models. That roadmap is straightforward. What inflamed users this week was the delivery mechanism: a routine webOS over‑the‑air (FOTA) update that added a visible Copilot tile to the home screen on a number of LG sets. Owners reporting the change say the tile behaves differently from ordinary apps — the TV’s app management UI offers only the option to hide or disable Copilot, not to uninstall it. Multiple community posts and screenshots indicate the tile can reappear after a factory reset, suggesting the app may be provisioned as a privileged system component or baked into a firmware image rather than installed as a removable Content Store app.
The technical mechanics of those packaging decisions are well known in embedded platforms: system‑package installs and firmware‑baked components are common ways for OEMs to deliver deeply integrated features. The result for end users is the same — a visible, persistent feature they cannot remove through the standard UI.
There are legitimate product benefits to a conversational assistant on a TV, but the rollout matters. When new features are pushed in ways that remove or obscure user choice, the result is backlash, distrust, and potential regulatory scrutiny. OEMs and partners can — and should — address these problems quickly: provide clear uninstall or disable paths, default to privacy‑minimal settings, publish transparent update notes, and offer accessible data‑deletion controls. Those steps would protect user trust while preserving the genuine value assistants can offer on the big screen.
For owners affected today, the immediate, practical steps are modest: disable Live Plus, hide the Copilot tile, avoid account sign‑in, and consider an external streamer or network‑level blocking if you want to reduce the assistant’s surface area. Those mitigations are imperfect, and some are inconvenient, but they are the available path to reclaiming control until vendors offer a cleaner remediation.
Finally, any claims about Copilot’s telemetric behavior beyond established webOS flows should be treated as concerns rather than proven facts until verified by vendor disclosures or independent technical analysis. Users, privacy advocates, and regulators should demand that confirmation — and vendors should provide it promptly.
Source: Tom's Hardware https://www.tomshardware.com/servic...non-removable-microsoft-copilot-app-to-webos/
In product announcements and at CES 2025, Microsoft and TV makers signaled a clear strategy: bring Copilot’s conversational AI to living-room screens as a core part of the smart‑TV experience. LG positioned Copilot as an extension of webOS’s AI initiatives — an assistant to aid discovery, answer questions, and surface contextual recommendations — while Samsung published staged rollouts for selected 2025 models. That roadmap is straightforward. What inflamed users this week was the delivery mechanism: a routine webOS over‑the‑air (FOTA) update that added a visible Copilot tile to the home screen on a number of LG sets. Owners reporting the change say the tile behaves differently from ordinary apps — the TV’s app management UI offers only the option to hide or disable Copilot, not to uninstall it. Multiple community posts and screenshots indicate the tile can reappear after a factory reset, suggesting the app may be provisioned as a privileged system component or baked into a firmware image rather than installed as a removable Content Store app.The technical mechanics of those packaging decisions are well known in embedded platforms: system‑package installs and firmware‑baked components are common ways for OEMs to deliver deeply integrated features. The result for end users is the same — a visible, persistent feature they cannot remove through the standard UI.
What happened: the observable facts
Timeline and scope
- CES 2025: Microsoft and TV OEMs publicly announced Copilot integrations for select 2025 smart TVs, positioning it as a conversational helper for content discovery and contextual queries.
- Mid‑December (community reports): Multiple LG owners reported an automatic webOS update that added a Copilot tile to their home screens. Those reports spread quickly on Reddit and other forums and were picked up by tech outlets.
User-reported behavior
- Copilot appears in the home row or the AI/assistant section of webOS after an update.
- The TV’s app manager does not show an uninstall/trash icon for Copilot — users see only hide or disable options.
- In several reported cases, performing a factory reset restored the Copilot tile, indicating the component may be integrated at the system or firmware level.
Why this matters: device autonomy, privacy, and consumer expectations
Loss of control and the “bloatware” dilemma
Consumers reasonably expect optional services on purchased hardware to be removable. When an OEM treats a partner app as a system component, the device feels less like a product the owner controls and more like a platform with vendor‑imposed services. That perception fuels immediate anger because the change is visible — the tile sits where users expect their chosen streaming apps to be — and because the normal uninstall affordances are absent.Privacy and telemetry concerns
webOS already supports Automatic Content Recognition (ACR), marketed as Live Plus, which can identify on‑screen content and feed personalization and advertisement features. An assistant like Copilot is more useful when it has contextual signals about what’s playing. That combination increases the telemetry surface area (viewing habits, timestamps, potentially audio-based cues) and amplifies concerns about unseen data flows. Disabling Live Plus reduces some of those signals, but it does not remove a system‑level app. Users have been advised to toggle Live Plus off as an immediate mitigation.Commercial incentives
Embedding Copilot on TVs makes commercial sense for both OEMs and Microsoft: it’s a headline feature (feature differentiation), it increases Microsoft’s footprint across screens (ecosystem reach), and it can improve personalization that increases ad value (monetization). Those incentives are legitimate from a product and business perspective — but they clash with user expectations when the delivery removes choice.Technical explanation: how an app becomes “undeletable” on a smart TV
Two canonical mechanisms explain the behavior users report:- Privileged system package: The OEM installs the app outside the user sandbox and marks it as a system app. The settings UI commonly permits hiding or disabling, but not uninstalling. This is a standard approach for deeply integrated services or DRM components.
- Firmware‑baked component: The app is included in the firmware image installed by the FOTA update. A factory reset reinstalls that image, restoring any baked‑in components. Removing those components typically requires vendor tools or a firmware rollback — options normally unavailable to consumers.
Cross‑checking the record: vendor announcements vs. community evidence
- Vendor announcements at CES and in product messaging established intent to bring Copilot to TVs, and Samsung published availability details for selected models. These two independent reporting streams corroborate that Copilot was meant for TV platforms.
- Community evidence — screenshots, forum posts, and user reports — repeatedly documents the unexpected arrival of Copilot on LG sets and the lack of an uninstall option in app management. Those on‑the‑ground accounts are consistent across several independent threads and platforms.
- What remains unverified is an explicit LG or Microsoft technical statement saying Copilot was intentionally packaged as a non‑removable system app in a specific firmware build. Community behavior strongly suggests privileged provisioning, but vendor confirmation is the definitive proof and, at the time of reporting, absent. That distinction — observed behavior versus vendor‑confirmed packaging — is important and should be made explicit when evaluating claims.
What users are doing right now: practical mitigations
Owners who want to reduce Copilot’s presence or telemetry exposure have a limited set of practical options. Each approach has tradeoffs.Steps ranked from least to most disruptive
- Toggle Live Plus / ACR and ad personalization off. (Settings → All Settings → General → System → Additional Settings → Live Plus — wording varies by model. This reduces contextual signals but does not remove the app.
- Hide the Copilot tile and avoid signing in to Microsoft services on the TV. Hiding removes daily visibility and avoids account-based personalization.
- Keep the TV disconnected from the Internet or block telemetry domains at the router. This prevents cloud calls but disables automatic updates and may break legitimate services. Domain‑blocking requires technical skill and careful whitelisting.
- Use an external streamer (Apple TV, Roku, Amazon Fire TV, Nvidia Shield). This sidesteps the smart‑TV layer for everyday streaming and preserves a “dumb display” experience, at the cost of integrated features and convenience.
- Factory reset and test. If the app is truly firmware‑baked, reset will likely reintroduce it. Reflashing unsupported firmware is risky, voids warranties, and is not recommended for most users.
- Seek vendor support or consumer remedies. If an advertised feature was promised and then changed or if the update materially alters advertised functionality, retailers and consumer‑protection channels may be options.
Strengths and the case for Copilot on TVs
When implemented transparently and with user‑first defaults, Copilot can provide genuine user value:- Improved content discovery: A conversational assistant can search across multiple streaming services and present aggregated results, reducing friction.
- Accessibility gains: Voice navigation and contextual explanations help users with mobility or vision impairments.
- On‑screen companion content: Live cards, scene summaries, or sports statistics delivered conversationally can enrich viewing for some audiences.
Risks, tradeoffs, and red flags
- Loss of ownership control: Non‑removable system apps subvert user expectations about what they can remove from hardware they bought. That perception damages trust and can turn a differentiator into a liability.
- Telemetry expansion: An assistant that uses ACR and account signals expands the types of data collected by the TV. Without clear, persistent opt‑out controls and robust defaults, that expansion can be perceived (and may be) privacy invasive. Claims that Copilot introduced always‑on audio capture or new telemetry classes remain unverified and should be treated as concerns until independently audited.
- Opaque update practices: Firmware updates that add visible functionality without clear patch notes or opt‑out options create distrust. Vendors should publish short, discoverable update notes including removal or disable instructions for new features.
- Support and maintenance burden: System‑level integrations are harder to troubleshoot and can tie support teams to partner dependencies (e.g., account linking and cloud‑service availability).
- Regulatory exposure: In jurisdictions with strict data‑protection rules, obscured consent flows or difficult opt‑outs could attract regulatory scrutiny or consumer‑protection complaints.
What vendors should (and can) do — practical recommendations
To restore user trust and reduce regulatory risk, OEMs and partners should adopt these concrete actions:- Make Copilot optional or provide a clear uninstall path that also removes any associated telemetry artifacts. If full removal isn’t practical due to integration complexity, provide a single‑click disabled state that also severs cloud bindings until re‑enabled.
- Default to privacy‑minimal settings. ACR and ad personalization should default to off and require an explicit user opt‑in.
- Publish concise update notes with every FOTA push that adds or modifies visible features, and include a clear path to remove or disable those features.
- Provide a dedicated privacy dashboard and data‑deletion tools so users can view and purge viewing data associated with their device.
- Offer transparent documentation about what signals the assistant uses (ACR, account data, voice input) and how those signals are stored, processed, and deleted.
What’s verified — and what still needs confirmation
Verified:- Microsoft and major OEMs publicly announced Copilot on TVs at CES and in follow‑up messaging.
- Community reporting documents that some LG webOS TVs received an over‑the‑air update that added a Copilot tile which, in reported cases, lacked the normal uninstall affordance (the tile could be hidden but not deleted).
- webOS includes a Live Plus / ACR setting that can be toggled; that capability is documented in user materials.
- That Copilot introduced previously undisclosed classes of telemetry such as continuous ambient audio capture bound to Copilot. These are plausible privacy concerns but lack public, independent forensic confirmation. Treat as unverified until packet captures, telemetry disclosures, or vendor technical notes confirm specifics.
- Whether LG intentionally packaged Copilot as a non‑removable system app across all affected firmware revisions. Community tests strongly suggest privileged provisioning in some builds, but an OEM technical bulletin is the definitive confirmation.
Conclusion
The arrival of Microsoft Copilot on LG webOS sets underscores a growing tension in modern consumer electronics: vendors see software and AI as the primary battleground for differentiation and monetization, while many owners still expect meaningful control over what runs on hardware they purchased. The observable facts — a FOTA update adding Copilot to home screens and community reports that the app lacks an uninstall option — are well documented and worrying for those who value device autonomy and privacy.There are legitimate product benefits to a conversational assistant on a TV, but the rollout matters. When new features are pushed in ways that remove or obscure user choice, the result is backlash, distrust, and potential regulatory scrutiny. OEMs and partners can — and should — address these problems quickly: provide clear uninstall or disable paths, default to privacy‑minimal settings, publish transparent update notes, and offer accessible data‑deletion controls. Those steps would protect user trust while preserving the genuine value assistants can offer on the big screen.
For owners affected today, the immediate, practical steps are modest: disable Live Plus, hide the Copilot tile, avoid account sign‑in, and consider an external streamer or network‑level blocking if you want to reduce the assistant’s surface area. Those mitigations are imperfect, and some are inconvenient, but they are the available path to reclaiming control until vendors offer a cleaner remediation.
Finally, any claims about Copilot’s telemetric behavior beyond established webOS flows should be treated as concerns rather than proven facts until verified by vendor disclosures or independent technical analysis. Users, privacy advocates, and regulators should demand that confirmation — and vendors should provide it promptly.
Source: Tom's Hardware https://www.tomshardware.com/servic...non-removable-microsoft-copilot-app-to-webos/
Similar threads
- Article
- Article