Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

Android Auto Bug Leaves Foldable Phone Owners Stuck Opening Devices to Call

Дата публикации: 11-10-2026 14:52:14

A persistent Android Auto bug prevents outgoing calls from closed clamshell foldables like Motorola Razr and Samsung Z Flip models when using Gemini. Incoming calls work fine, but drivers must open devices to connect, undermining hands-free safety. Google and Motorola investigate with no fix yet.

Основное содержимое страницы с новостью.

Drivers who own clamshell foldables now face an awkward choice in their cars. Keep the phone closed for convenience. Or open it to make a call through Android Auto. The bug blocks outgoing calls when the device stays folded. Incoming calls work without issue.

Reports first surfaced months ago but gained attention in late September. Users on Reddit, Google forums and Motorola support threads described the same frustrating experience. They issue a voice command. Gemini announces the call. Nothing connects. A prompt appears. Flip open to continue.

The problem hits Motorola Razr Ultra models, including the 2025 and 2026 versions running Android 16. Samsung Galaxy Z Flip 7 owners have reported similar trouble. Android Authority broke the story on Sept. 29, 2026, noting the issue affects multiple clamshell devices. Both Google and Motorola confirmed they are gathering details from affected users.

But here’s what makes the timing notable. Many pinpoint the changeover from Google Assistant to Gemini as the trigger. Calls worked fine before. The switch brought new problems. One Reddit user said the error started exactly when Gemini took over. Another reported the same on a Galaxy Z Flip 7 back in April. Engadget covered the reports on Oct. 10, highlighting how Gemini appears central to the breakdown.

Reverting to the old assistant once fixed the calls. That option vanished. Google completed the removal of Google Assistant from Android on Sept. 28. 9to5Google reported the timing. The workaround disappeared just as more users encountered the bug. Now they depend on Gemini. The assistant talks a good game but fails to complete the connection while the phone stays shut.

Why does the fold state matter? Clamshell designs promise quick access via the outer display. Drivers expect to stay focused on the road. Voice commands through Android Auto should support that. Instead the system demands the main screen. Opening the phone in a vehicle risks scratches or damage. Both Samsung and Motorola advise against leaving foldables open during drives.

The bug doesn’t break Android Auto entirely. Navigation continues. Music plays. Incoming calls ring through. Only outgoing voice-initiated calls fail in the closed position. Gemini confirms the contact. The interface shows activity. The actual phone call never starts. Open the device. Repeat the command. Success follows immediately.

Motorola responded to forum posts within days in some cases. Company representatives asked for device details, software versions and steps to reproduce. Google offered similar outreach. No root cause has been disclosed. No patch timeline exists. As of Oct. 11, the issue lingers. A Telset.id report published today restated the complaints from Indonesian users, confirming the pattern holds across regions.

Industry watchers see this as part of broader integration pains. Gemini brings advanced language abilities. Yet basic functions tied to hardware states expose gaps. Foldables add complexity with their dual-screen logic and sensor inputs. Android Auto must interpret whether the device can handle telephony without the primary display active. Something in that handoff now fails.

Owners adapted in the short term. Some place calls before starting the engine. Others keep a foldable partially open in a cradle, against manufacturer guidance. A few switched to Bluetooth calling outside Android Auto. None of these feel ideal for a system built around hands-free safety.

Google’s push to make Gemini the default assistant accelerated this year. The change aimed to deliver smarter responses and better context awareness. For most users it delivers. On foldables paired with car systems, the transition uncovered an edge case. One that matters during drives when every second counts.

Android Central noted on Oct. 1 that the problem had been gaining traction for weeks. Their coverage emphasized that both companies remain actively engaged. Forum threads continue to grow with new reports. Users share screenshots of the exact error message and Gemini’s spoken confirmation that never materializes into a dial tone.

The situation reveals limits in how software teams test emerging form factors. Foldables still represent a smaller slice of the market. Their unique behaviors don’t always surface in standard test suites. Combine that with a major assistant overhaul and a vehicle integration layer. The result is a bug that feels obvious in hindsight yet slipped through.

Fixes could arrive through an Android Auto update, a Gemini server-side change or a system patch for specific foldable models. Until then drivers improvise. They open the phone. They accept the compromise. Or they avoid voice calling altogether while the device stays compact.

That last choice undercuts one of the strongest arguments for these devices. The ability to handle quick tasks without unfolding. For business users making hands-free calls during commutes, the bug creates real friction. Safety advocates worry about divided attention as drivers fumble with their phones mid-trip.

Google has built a reputation for rapid response to Android Auto complaints. Past connectivity and compatibility issues often saw updates within weeks. Motorola similarly engages its community on Razr-specific problems. Expectations remain high for a targeted solution soon. Yet the involvement of Gemini adds layers. Any change must preserve the new assistant’s capabilities while restoring reliable calling.

Recent X posts echo the frustration. Users tag both companies and share videos of the failed attempts. The conversation stays technical. No panic. Just irritation that a basic function broke. One post from early October captured it simply. The phone connects. The command is understood. The call dies silently.

Automakers have embraced Android Auto for its broad compatibility. This episode tests that trust. Owners of premium foldables expect polished experiences. A prompt to open the device while driving feels like a step backward to an earlier era of flip phones that demanded manual intervention.

The bug stands as a reminder. Hardware innovation outpaces software validation at times. Gemini represents the future of interaction. But that future must still handle the physical realities of today’s devices. Closed or open. In a pocket, on a dash, or connected to a car.

Until the patch lands, the practical advice stays straightforward. Test calls while stationary. Keep the phone open if voice dialing is essential. Watch for updates from Google and Motorola. The companies know the scope. Affected owners hope the fix comes before the problem spreads to more models and more drivers on the road.

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Google aware of Android Auto bug that blocks calls if your foldable phone is closed015.2230-09-2026
2 Closed foldables cause Android Auto calls to fail: Moto and Google are investigating 06.9401-10-2026
3Google Tests Gemini Calling Feature That Talks to Businesses for You06.9725-09-2026
4У пользователей складных Samsung Galaxy Fold начал сбоить YouTube07.0928-09-2026
5Pixel 11 starts testing ‘Call for Me’ to have Gemini phone on your behalf022.624-09-2026
6Arriva “Call for me”, la nuova funzione di Gemini Intelligence esclusiva dei Pixel 1108.5624-09-2026
7Gemini AI Dials In: Pixel’s Voice Assistant Now Makes Real Calls for You05.8426-09-2026
8Google’s Guided Vision Turns Gemini Live Into a Conversational Guide for Blind and Low-Vision Users013.3402-10-2026
9 Android 17 QPR2 Beta 6 is rolling out: unexpected reboots and kernel crash fixes lead the way 015.9225-09-2026
10How One Android Automation Workflow Freed Hours of Screen Time08.6811-10-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 10.4. Источник: www.webpronews.com.