FAQ
TL;DR: On Philips PUS6412 TVs, voice search often works only ~24 hours after a factory reset; “These voice searches are a disaster.” Troubleshoot with resets, USB mics, Bluetooth off, and phone‑app workarounds. For PUS6412 owners facing mic buttons that trigger search but capture nothing. [Elektroda, wroblex, post #18377100]
Why it matters: It helps you quickly recover voice control on Philips Android TVs without risky firmware hacks.
Quick Facts
- The bundled 49PUS6412 remote lacks a voice button; owners add third‑party remotes. [Elektroda, 20614hdi, post #18376319]
- Reported firmware when failures began: TPM171E_R.107.001.101.002 on PUS6412. [Elektroda, _Trolk_, post #18421989]
- Factory reset restores voice search briefly, typically for about 24 hours. [Elektroda, wroblex, post #18377100]
- Android TV Remote and Philips TV Remote apps deliver working voice commands. [Elektroda, _Trolk_, post #18443014]
- Keeping Bluetooth off improved USB‑mic reliability; unplug and replug restores function later. [Elektroda, _Trolk_, post #18460648]
Why did voice search stop working on my Philips PUS6412?
Voice search often fails after background updates to the TV's software components. One owner noticed the Google Play interface changed despite disabled updates. After that, the mic prompt appears but nothing is captured. This pattern points to software-side regression, not hardware failure. [Elektroda, wroblex, post #18377100]
Will a factory reset fix the issue long-term?
Factory reset brings voice search back, but only temporarily. It can stop again after the TV is powered off for several dozen minutes. That makes reset a short-term remedy, not a lasting fix. [Elektroda, Trolk, #18425446]
Can I roll back the TV firmware to a stable version?
A rollback path is unclear in the thread. Loading the March 2019 package did not restore voice input. Disabling the Play Store also made no difference. No reliable download link for older firmware was shared. [Elektroda, Trolk, #18425446]
Is there a quick workaround to use voice search?
Yes. Use the Android TV Remote or Philips TV Remote mobile apps. Their microphone buttons send working voice input to the TV. This avoids the broken on-remote capture path. [Elektroda, Trolk, #18443014]
How do I pair my Bluetooth remote with the PUS6412?
Follow these steps to pair a remote.
- On TV: Settings > Network > Remote control > Pair remote.
- Hold the remote's PAIR button for 3 seconds.
- Confirm the on-screen pairing prompt to finish. [Elektroda, Ania18, post #19585205]
Does turning Bluetooth off help microphone reliability?
One user reinstalled the TV, kept Bluetooth off, and then connected Wi‑Fi. With a USB mic, voice search worked for days. Later, unplugging and replugging the microphone restored it when it failed. This points to Bluetooth interference or conflicts. [Elektroda, Trolk, #18460648]
Will a low-cost USB mic work with this TV?
A budget USB lapel mic worked when plugged directly into the TV. The cited unit cost about PLN 19.82. The remote model did not matter in that setup. Trigger voice input using on-screen microphone icons. [Elektroda, Trolk, #18465720]
How do I trigger voice input correctly on this Android TV?
Enter the smart screen and select the microphone icon in the top left. Or press the microphone icon within supported app search fields. The physical Search button during live TV only opens a text keyboard, not voice. Use the on-screen mic for voice capture. [Elektroda, Trolk, #18465720]
Why does the TV tell me to "Press the microphone and start talking" but ignore me?
This happens after updates on affected PUS6412 sets. The interface shows the prompt but captures no audio. As one owner said, "It only shows 'Press the microphone and start talking' and nothing." The behavior indicates a software-side break in the audio path. [Elektroda, wroblex, post #18377100]
Does disabling the Play Store stop the issue?
No. Disabling the Play Store provided no improvement in voice search reliability. The microphone still stopped after a short usage window. Focus on pairing, USB mics, or app workarounds instead. [Elektroda, Trolk, #18425446]
Is flashing software from another Philips model safe?
A forum user warned against it due to hardware differences. Cross‑flashing can brick the TV and block recovery. Stick to model‑specific packages only. Avoid risky firmware experiments for this issue. [Elektroda, Trolk, #18438727]
My third‑party remote's mic triggers search but captures no audio. Is it incompatible?
That pattern matches what others saw with aftermarket remotes. The TV recognizes the button and opens search, but hears nothing. The same remote worked when connected to a laptop. That suggests TV‑side compatibility limitations for its microphone stream. [Elektroda, 20614hdi, post #18376319]
After a while or power off, voice search dies again. Any quick fix?
If you use a USB mic, unplug and reconnect it. Users report this immediately restores voice capture. It removes the need for repeated factory resets. Keep Bluetooth off if the issue recurs. [Elektroda, Trolk, #18460648]
Is this limited to the 49‑inch version?
No. A 55PUS6412/12 owner reported identical voice search failures. That widens the scope to the PUS6412 family. Expect similar behavior across sizes. [Elektroda, wroblex, post #18377100]
Will disabling updates prevent recurrence?
Unlikely. One owner disabled firmware and app updates in the store. The store UI still changed, and microphone failures returned. Background components probably still update despite those settings. [Elektroda, wroblex, post #18377100]
