Google Hands Frontier AI Tools to 200 European Scientists in Bid to Close Compute Gap

BRUSSELS — Google DeepMind and Google Cloud just handed a select group of European researchers the keys to some of the tech giant’s most powerful artificial intelligence systems. The move comes with $3 million in compute credits. It targets up to 200 scientists chosen by the European Commission.

The announcement landed Tuesday at an AI summit in Dublin. It aligns with the EU’s push to boost homegrown scientific work through artificial intelligence. But it also highlights a persistent sore point: many researchers on the continent lack the massive processing power needed to run the latest models.

Google’s official blog post lays out the details. The company will grant direct access to frontier models. These include AlphaFold 3 for protein structures. WeatherNext handles advanced forecasting. AlphaGenome targets DNA analysis. AlphaEvolve and AlphaEarth Foundations round out the list.

Maureen Costello, vice president for the UK, Ireland and Sub-Saharan Africa at Google Cloud, authored the post. She frames the pledge as direct support for the European Union’s AI for Science agenda. The tools flow through the Resource for AI Science in Europe, or RAISE. That program exists to shrink the compute divide that sometimes holds back continental teams.

Short and simple. Researchers get both the models and the cloud credits to run them. Split evenly, the money equals roughly $15,000 per person. Not a fortune in AI terms. Enough, though, to test ideas that would otherwise stall.

Yet the timing carries weight. Europe has poured resources into its own AI infrastructure. The Horizon Europe program commits €600 million to expand computational access for scientists and startups. It promises dedicated time on AI Gigafactories. Annual investments in AI research are set to double past €3 billion. Data curation efforts aim to fill gaps that models need to thrive.

Unite.AI reported on these parallel EU steps. They show Brussels wants self-reliance. Google’s offer doesn’t replace that. It supplements it. The American company positions itself as a partner. Critics might see dependence. Proponents argue speed matters more than origin when breakthroughs hang in the balance.

Consider AlphaFold. Earlier versions already transformed biology. Nearly 190,000 UK researchers alone tapped similar tools to probe crop resilience, antimicrobial resistance and other puzzles. The new AlphaFold 3 promises even sharper predictions of molecular interactions. Drug discovery could accelerate. So could materials science.

WeatherNext targets another urgent domain. Extreme weather events grow more frequent. Accurate, rapid forecasts save lives and money. European meteorologists armed with these systems might spot patterns hidden from traditional models. The same logic applies to genomics and earth systems modeling.

But. Access remains selective. The Commission picks the winners. Not Google. That buffer aims to keep choices merit-based and free of commercial bias. Still, it funnels some of the world’s most advanced proprietary technology through a public process. The implications stretch beyond any single grant.

Reuters noted the announcement coincides with fresh calls for tighter AI oversight. Its coverage points to a letter signed by roughly 400 researchers from 34 countries, including Geoffrey Hinton and Yoshua Bengio. They want an international body to set containment standards and require reporting of security incidents involving advanced models.

The tension is real. Industry offers tools that promise faster science. Regulators and ethicists worry about unchecked power, data privacy and unintended consequences. Europe feels this pull acutely. It champions both innovation and strict rules. The AI Act stands as testament.

Google’s move echoes its recent UK partnership. There, DeepMind pledged priority access to similar models for British scientists. It even plans an automated laboratory focused on materials science. The European pledge broadens the geographic reach. It signals the company sees strategic value in embedding its technology across the EU’s research fabric.

Compute remains the bottleneck. Frontier models demand graphics processing units by the thousands. Training runs cost millions. Inference, while cheaper, still scales poorly for ambitious simulations. The $3 million helps. It won’t level the field against labs backed by hyperscalers or sovereign funds. It buys time. It buys experiments.

And results could come quickly. Past AI applications in science delivered surprises. Protein folding went from decades-long challenges to near-instant predictions. Similar leaps in climate modeling or genetic interpretation aren’t fantasy. They require the right data, the right questions and enough cycles to iterate.

European science carries a proud history. From quantum mechanics to the World Wide Web, the continent shaped modern understanding. Yet in the current AI wave, it sometimes appears a step behind the U.S. and China. Initiatives like RAISE, combined with private offers, seek to change that equation.

Success depends on execution. Selected teams must integrate these tools into existing workflows. They need training. They need to avoid the trap of treating AI as a black box. Transparency in how models reach conclusions will matter for peer review and regulatory acceptance.

Google, for its part, gains goodwill. It collects indirect feedback on model performance in diverse scientific settings. It strengthens ties with policymakers. And it demonstrates that its technology serves public goals — a useful narrative as scrutiny intensifies.

The broader picture includes competitors. NVIDIA recently highlighted 35 new AI supercomputers across Europe. Those systems deliver exaflops of performance for climate science, healthcare and clean energy. They run on different software stacks. Yet the hardware race and the model race intersect. Researchers will mix and match where they can.

So the Google pledge fits into a mosaic. Public money builds infrastructure. Private firms supply specialized models. Scientists stand in the middle, hoping the combination yields discoveries that justify the investment.

Whether $3 million and selective access prove transformative remains to be seen. Early wins in weather prediction or molecular design could quiet skeptics. Persistent gaps in compute or data quality could reinforce them. Either way, the announcement marks another concrete step in AI’s migration from tech labs into the heart of European science.

One thing is clear. The tools are here. The researchers are coming. The experiments will follow. Outcomes will shape not just publications but policy, industry and perhaps even climate resilience across the continent.

from WebProNews https://ift.tt/ya1cWUf

Linus Torvalds Turns to AI to Untangle Obscure Kernel Code, Surfaces Bugs Lurking Since 2013

Linus Torvalds has long urged developers to reach for modern tools when code grows too tangled to follow. This past weekend he took his own advice. In a Git tag labeled assoc-array-fixes, the Linux creator described using large language model tools to clarify a patch he found impenetrable. The result? Confirmation of one reported defect and the discovery of three more. All four trace back to the library’s original 2013 introduction.

“Nils Ollrogge reported a bug in the assoc_array library and had a patch to fix it too, but that code was too obscure for me to follow, so I did what I preach: use modern LLM tools to help make sense of it all,” Torvalds wrote in the tag message. Phoronix first reported the development on October 12, 2026.

The work produced an LLM-assisted branch. It splits several larger, harder-to-read functions into smaller pieces. Readability drove the changes. Clarity came first. Then a user-space test harness ran against the revised code. It verified Ollrogge’s bug. And it exposed three additional problems that had persisted undetected for over a decade.

The assoc_array library and its hidden complexity

Developers rely on assoc_array for efficient lookups in the kernel. The generic associative array stores objects referenced by index keys of varying lengths. It supports iteration, insertion, deletion and destruction without forcing objects to embed linkage data. That design choice lets one object sit in multiple arrays at once. Clever. But the implementation packs subtlety into every layer.

Internally the structure builds a tree of 16-pointer nodes. Each level indexes on nibbles drawn from the key, much like a radix tree. Shortcuts prune paths through chains of single-occupancy nodes. Nodes even stash leaf pointers in spare slots to avoid extra allocations until a node fills. The official kernel documentation details these mechanics. The code that realizes them grew dense. Functions ballooned. Logic twisted across multiple levels of indirection. Torvalds, who maintains final say on what enters the kernel, hit a wall.

Ollrogge’s report arrived with a proposed fix. The patch alone proved insufficient. Without clear understanding of the surrounding functions, Torvalds could not judge its correctness or side effects. So he turned to LLM assistance. The models helped break apart the monolithic routines. Smaller functions emerged. Each handled a tighter scope. The refactored code became something a human could trace step by step.

But Torvalds did not stop at refactoring. He demanded verification. A test harness compiled to run in user space exercised the library outside the kernel’s constraints. That choice mattered. It allowed rapid iteration without reboot cycles or risk of system instability. The harness confirmed the original bug. Then it kept going. Three more defects surfaced. Each dated to the very first commit that brought assoc_array into the kernel in 2013.

Kernel observers noted the timing. The tag appeared alongside delayed release candidate work for Linux 7.3. Torvalds rarely hosts topic branches in his personal tree. Their presence signals active experimentation. The assoc-array-fixes tag points to patches not yet merged into mainline. They will likely head to the 7.4 merge window once reviewed further. NeoTeo covered the same events on October 13, 2026, confirming the patches remain outside master as of that date.

This episode follows days after another AI-assisted effort from Torvalds. He employed Anthropic’s Claude Code to draft patches and a test program aimed at tripling small-read throughput in the page cache. That work carries the branch name noref-filemap-read-with-llm. The suffix itself acknowledges the tool. Torvalds has grown more open about these experiments. He promotes LLMs as aids for comprehension, not replacements for human judgment.

Community reaction on X mixed appreciation with caution. One developer highlighted the user-space harness as the real win. “The part that matters,” they posted. Others saw validation for applying AI to legacy codebases. “Use it to understand complicated legacy code, make the logic easier to follow and build tests around it,” another wrote. Finding bugs dormant since 2013 underscored the value. But questions remain about how widely such methods will scale inside the strict review culture of kernel development.

The assoc_array fixes illustrate a practical pattern. LLMs excel at explaining dense logic. They can suggest decompositions that humans might overlook under time pressure. Yet the final authority stays with maintainers. Torvalds ran the tests himself. He evaluated the output. The models suggested. He decided. That sequence matters. It keeps accountability intact even as tools grow more capable.

Kernel history shows similar libraries accumulate complexity over time. What begins as elegant abstraction gains edge cases, performance tweaks and architecture-specific paths. The 2013 commit planted the seed. Subsequent patches layered on top. By 2026 the functions had become opaque to even their most experienced reader. Torvalds’ action may encourage others to revisit long-ignored corners of the codebase with fresh analytical help.

Whether these specific fixes alter performance or memory behavior remains unstated in the tag. The emphasis stayed on correctness and readability. Four bugs fixed. Code easier to audit. A test harness now exists for future validation. Small steps. But in a project measured in decades, removing defects from foundational libraries carries weight.

Torvalds continues to speak publicly about AI’s role. His experiments signal acceptance at the highest level of Linux maintenance. Other maintainers watch closely. Some already experiment with similar assistants for their subsystems. The assoc-array case offers a concrete template: identify impenetrable code, apply LLM to restructure for clarity, test exhaustively in user space, then integrate only after human review.

The patches sit ready. The kernel community will examine them in coming weeks. If accepted, they will ship in a future release. And the next time an obscure bug report lands, developers may remember how the project’s leader responded. He reached for the tools he had preached. The code grew clearer. Latent errors finally saw daylight. Progress, one clarified function at a time.

from WebProNews https://ift.tt/zvX6gQ3

Agentic AI Exposes Data Debt as Critical Operational Risk: Time for Governance Overhaul

Agentic AI systems now operate with a degree of independence that exposes weaknesses hidden inside corporate data environments for years. Where human teams once reviewed outputs, caught inconsistencies, and applied judgment before any action took place, autonomous agents move directly from retrieval to decision to execution. The result is that accumulated data debt, long tolerated as a background cost of doing business, has transformed into immediate operational risk capable of triggering financial loss, compliance violations, or reputational damage at machine speed.

Data debt appears in many forms across large organizations. Metric definitions drift between departments. Customer records contain conflicting addresses or status codes. Policy documents sit in outdated repositories while newer versions circulate in emails or shared drives. Ownership of critical data assets remains unclear, so no single team feels accountable when problems surface. For a decade or more, these issues stayed manageable because people served as the final filter. Analysts noticed anomalies, managers asked clarifying questions, and governance committees met periodically to resolve disputes. That buffer has begun to disappear.

When an agentic system receives a request to optimize working capital, for example, it may pull data from the ERP, the CRM, a data lake, and several external market feeds. If those sources define “current liabilities” differently, the agent will still choose a path and act on it, perhaps by initiating vendor payments, adjusting inventory orders, or triggering treasury transfers. The absence of a human pause means errors compound before anyone notices. A single misrouted instruction can affect cash positions, supplier relationships, or regulatory reports within minutes.

Chief data officers now confront what amounts to an action-readiness gap rather than a pure artificial intelligence challenge. Traditional data quality programs that focus on accuracy, completeness, and timeliness remain necessary, yet they fall short when agents require explicit instructions about permissible uses, escalation paths, and conditions under which actions must halt. Without those layered controls, even high-quality data can produce harmful outcomes once placed inside an autonomous loop.

Consider a common scenario in financial services. An agent tasked with customer onboarding might retrieve identity data from multiple legacy systems that use different matching rules. One system flags an address change as high risk; another treats it as routine. A human compliance officer would reconcile the discrepancy and document the rationale. An agent without clear decision boundaries might approve the account, expose the bank to fraud, or reject a legitimate client and invite regulatory scrutiny. The data itself may be factually correct in each silo, but the lack of unified governance turns it into a liability.

Similar patterns appear in supply chain operations, healthcare record management, and human resources. Agents that schedule maintenance, adjust pricing, or route patient referrals depend on consistent definitions of terms such as “critical,” “eligible,” or “approved.” When those definitions exist only in tribal knowledge or conflicting policy documents, the systems improvise. The improvisation may look logical to the model but violate contractual terms, safety standards, or internal controls that were never translated into machine-readable rules.

The shift from passive analytics to active agents therefore demands a corresponding evolution in data governance. Organizations must move beyond scoring data sets for quality and begin certifying them for autonomous consumption. This involves creating explicit usage policies that specify which agents may access which domains, under what conditions, and with what override capabilities. It also requires mapping data ownership at a granular level so that accountability follows every automated action back to a responsible individual or team.

Some companies have started building what amount to digital contracts for data. These contracts record not only the source and freshness of a record but also the business rules that govern its application, the approval workflows that authorize changes, and the kill switches that can suspend downstream processes if anomalies appear. When an agent queries a certified data product, it receives both the value and the accompanying policy envelope. If the policy envelope contains contradictions or expired approvals, the agent is programmed to stop and escalate rather than proceed.

Implementing this level of control at enterprise scale presents real difficulties. Many legacy systems were built before anyone imagined autonomous digital workers. Their interfaces lack the metadata layers needed to convey intent or constraint. Integration layers that once served simple reporting needs now must support real-time policy enforcement and audit trails that survive across hybrid cloud environments. The technical work is substantial, yet the cultural and organizational changes may prove even harder.

Data teams accustomed to operating as service providers must now act as risk partners to every line of business that plans to deploy agents. They need to participate in product design sessions, not merely receive requirements after the fact. Business leaders must accept that data readiness will constrain their automation ambitions until foundational issues are resolved. This mutual accountability rarely existed when the primary output of data initiatives was a dashboard or a monthly report.

Executives who treat agentic AI as simply the next wave of productivity tools risk repeating mistakes made during earlier digital transformations. Many organizations rushed to adopt cloud analytics platforms without first rationalizing their master data or establishing clear ownership. The platforms delivered faster queries, yet underlying inconsistencies persisted and sometimes grew worse. With agents, the margin for such tolerance shrinks dramatically because the systems act rather than inform.

Forward-looking CDOs are therefore reframing their roadmaps around three core capabilities. First, they focus on making data not only clean but also interpretable by machines with embedded context and provenance. Second, they establish governance that travels with the data, so policies remain attached regardless of where an agent routes the information. Third, they design visible control surfaces that allow humans to monitor, pause, or redirect autonomous processes before small errors cascade into major incidents.

One global manufacturer recently completed an audit of its product master data ahead of deploying agents for demand planning and procurement. The audit revealed that more than 40 percent of active SKUs carried conflicting attributes between the ERP and the product lifecycle management system. Rather than simply correcting the records, the company created a reconciliation service that agents must query before taking action. The service returns both the best available data and a confidence score tied to governance metadata. If the score falls below a threshold, the agent must request human review. This approach slowed initial automation but prevented widespread ordering errors that could have disrupted supplier contracts worth hundreds of millions.

In parallel, the same manufacturer introduced machine-readable policy documents linked to every major data domain. These documents specify, for instance, that inventory adjustments above a certain value require finance approval and cannot be executed on weekends when control teams are offline. Agents attempting to violate those rules receive a structured refusal rather than an opportunity to find workarounds. The policy layer effectively restores some of the human buffer while preserving speed for routine tasks.

The transition also raises questions about liability and regulatory expectations. Auditors and regulators increasingly ask whether organizations can demonstrate that automated decisions rest on governed data and approved processes. Simply showing that source systems are accurate is no longer enough. Leaders must prove that the entire chain from data ingestion to action includes controls that prevent foreseeable harm. This standard mirrors concepts already established in areas such as model risk management, yet it now applies to a far broader set of systems.

Legal teams have begun drafting clauses that address data debt in contracts with AI vendors. These clauses require suppliers to disclose how their agents handle inconsistent inputs and to maintain audit logs that trace every decision back to specific data assets and policy versions. Procurement organizations that once focused on cost and functionality now treat governance readiness as a non-negotiable selection criterion.

None of these measures eliminate data debt overnight. Decades of accumulated inconsistency cannot be resolved with a single project or platform. Instead, organizations are adopting incremental strategies that prioritize the data domains most likely to be consumed by agents in the near term. Finance, customer master, product, and compliance data typically rise to the top of the list because they sit at the center of high-value autonomous workflows.

Progress requires sustained investment and visible executive support. Boards that once approved data initiatives based on promised efficiency gains must now also understand the downside risks of moving too quickly. The conversation shifts from “how fast can we automate” to “how safely can we automate given our current data foundation.”

The arrival of agentic systems therefore serves as a forcing function for long-deferred cleanup work. Companies that treat the moment as an opportunity to modernize their information backbone will gain a lasting advantage. Those that attempt to paper over existing problems with additional layers of AI risk amplifying the very issues they hope to escape.

Success depends on recognizing that data readiness for autonomous action rests on more than quality scores or governance committees. It requires clear, enforceable rules that travel with the data, ownership models that scale to machine speed, and control mechanisms that allow human intervention without destroying the benefits of automation. Only when those elements align can organizations confidently deploy agents across critical processes without turning yesterday’s data debt into tomorrow’s operational crisis.

from WebProNews https://ift.tt/t4MpfkQ

Two Sigma Interns Finish Early, Forcing Quant Giant to Redefine Entry-Level Talent

Two Sigma’s summer interns didn’t just meet expectations in 2026. They shattered them.

A majority of the 82 math-heavy recruits wrapped core assignments weeks ahead of prior years. They then tackled extra stretch goals. The $80 billion quant fund’s head of talent acquisition points to one clear driver: widespread AI adoption among the group. Business Insider first detailed the shift on Oct. 12.

Evan Anger, who leads talent efforts at the firm, watched the pattern unfold across engineering and financial modeling projects. Productivity jumped. So did the firm’s standards. “AI has raised expectations for the depth and contribution an intern can achieve in their few months on the job,” Anger told the publication.

Short. Direct. The old playbook no longer fits.

Two Sigma has long treated its internship as a primary talent pipeline. More than 200 current employees started there. Eight now serve as managing directors. The program feeds a workforce of roughly 1,700. Yet this summer’s results forced a reassessment. Technical fundamentals still matter. Deeply. But something else now carries equal weight.

Anger put it plainly. “We are still looking for people who understand what’s going on under the hood.” He added a warning. “If you have AI build something and you don’t understand it, that’s not good.”

But the gains from AI tools leveled capabilities that once separated candidates. Coding speed. Mathematical fluency. Those edges narrowed. In response, recruiters now probe harder for judgment and communication. They examine how interns direct AI systems. How they explain outputs to colleagues. How they translate machine results into business decisions.

Productivity Gains Reshape Expectations Across Quant Finance

The acceleration wasn’t isolated to Two Sigma. Similar patterns appear elsewhere. Chip equipment maker Applied Materials expects to double sales without doubling staff, crediting AI for product development and quality tasks. CEO Gary Dickerson made the projection in a Bloomberg interview published the same day as the Two Sigma coverage.

Broader hiring data tells a parallel story. Global tech employers maintain steady hiring intentions into late 2026. Yet they rank communication, collaboration and professionalism above most technical abilities. AI modeling sits high on technical lists. Human judgment ranks higher overall, according to a September report from Experis cited by the Financial Times.

Workday’s analysis of job postings shows basic AI skills demand dropped 25% after peaking early this year. Demand for building and engineering AI systems climbed 51% over the same stretch. Companies want builders. Not just users. The Financial Times covered those findings on Oct. 5.

Two Sigma interns split time between software engineering challenges and quantitative modeling. Many used large language models to debug, generate code and explore data patterns faster than predecessors. One intern described the shift in a Two Sigma video. They once resisted AI. Now they delegate routine debugging and focus on higher-order strategy. The firm shared insights from that discussion on its site.

Yet reliance on AI demands oversight. Interns must spot hallucinations. They correct drift. They frame precise prompts that align with financial reality. Anger sees this as quasi-management. Entry-level staff now coordinate with an AI “colleague” much like managers direct teams. The skill appears earlier in careers.

Future recruits will face questions about AI interaction. Recruiters want examples. Specific ones. How did you catch an error? How did you explain a model output to a skeptical stakeholder? How did you decide when to override the tool?

And the bar rises for depth. A project that once took an entire summer now finishes by mid-July. The remaining weeks bring opportunities to extend models, test new datasets or integrate findings into production systems. Stretch goals become standard. Average performance looks different.

Two Sigma still demands strong foundations in computer science, statistics or physics. Its 2027 AI Research Scientist internship posting lists requirements for Python mastery, TensorFlow or PyTorch experience, and preferably PhD-level work with noisy data. The listing appears on Harvard’s career site and others.

But pure technical prowess no longer suffices. Candidates must demonstrate they can steer AI without becoming captive to it. They must communicate complex results clearly. They must exercise judgment when models produce plausible but flawed outputs.

This evolution mirrors pressures across quantitative finance. Funds compete for talent that combines machine scale with human insight. Those who treat AI as a co-pilot gain speed. Those who treat it as a crutch fall behind.

Two Sigma’s leadership views the internship as preparation for exactly that environment. Interns receive real problems. They gain access to production tools. They present findings to senior researchers. The summer now compresses more learning into 10 weeks.

Other organizations report comparable compression. A supply chain study from The Hackett Group, highlighted by the Financial Times on Oct. 12, shows AI adopters cut forecast error up to 52% and staffing needs 15% to 24%. Productivity compounds. Headcount does not.

So Two Sigma adjusts. Its campus teams now weigh collaboration with AI alongside traditional metrics. They look for evidence of critical evaluation. Clear articulation. The ability to direct digital agents toward meaningful outcomes.

The change doesn’t diminish technical training. It builds on it. Strong coders who also master AI direction create asymmetric advantage. They finish faster. They contribute more. They signal readiness for full-time roles.

Anger expects the pattern to continue. Next year’s class may arrive with even greater AI fluency. The firm will likely raise expectations again. The cycle accelerates.

Yet the core principle holds. Understanding remains non-negotiable. Tools amplify. They do not replace. Interns who grasp this balance stand out. Those who don’t, even with flawless code, risk falling short.

Two Sigma’s experience offers a window into wider industry adjustment. Quant funds, banks and tech groups all feel the pressure. AI compresses timelines. It elevates soft skills that once matured over years. Organizations that adapt recruitment now will capture the best talent. Those that cling to old criteria may watch top candidates slip away.

The 2026 cohort proved the point. Early finishes. Extra contributions. Clearer signals of long-term potential. The bar moved. Two Sigma responded. Others will follow.

from WebProNews https://ift.tt/EVjnAmF

Google’s Latest Gemini Live UI Tweaks Signal Deeper Voice Mode Ambitions

Google keeps refining Gemini Live. The conversational voice feature first launched with promise of natural back-and-forth exchanges. Now an APK teardown shows the company testing another interface update. This one brings a fresh waveform animation and a dedicated speaker control.

The redesign surfaces in Google app version 17.65.17. Android Authority spotted it first. Testers activated the hidden code to reveal a work-in-progress screen. The bottom area now hosts a redesigned waveform. It pulses differently from previous versions. Up top, near the right corner, sits a speaker icon. Tap it and Gemini should stop talking. No need to adjust phone volume or hunt through settings.

But this early build feels stripped down. Video sharing and screen sharing buttons are absent. The prototype doesn’t respond to voice queries yet. Still, the direction looks clear. Google wants cleaner controls for voice output. Users often mute the AI mid-conversation. A direct button makes that simpler. One less friction point.

This change fits a longer pattern. Over the past year Google has repeatedly altered how Gemini Live appears. Earlier tests ditched the full-screen takeover. The mode now runs inside the main Gemini chat view. A pill-shaped container holds the waveform. Camera and mic controls flank it. Responses appear on screen as the conversation flows. Android Authority first detailed those shifts in April.

And the updates haven’t stopped. Neural Expressive styling arrived later. It added glowing effects, colorful dots, and softer shapes to overlays and Live screens. Floating widgets became circular. Icons slimmed down. The visual language grew more dynamic. Yet functionality kept expanding too.

Google rolled out Guided Vision in early October. The feature turns Gemini Live into a conversational visual assistant for blind and low-vision users. Share your camera feed. Gemini describes surroundings, offers proactive cues, and answers follow-up questions. It was built with input from the accessibility community and Aira. Real-time prompts help center the camera. “Pan slowly to the right” or “tilt downward” come naturally through voice. The Google Blog outlined the launch on October 1.

Model upgrades arrived around the same period. Gemini 3.8 Live and its Extended Thinking variant boosted reasoning speed and tool use. Background task execution no longer breaks conversation flow. The system handles 97 languages with automatic detection. Live Avatar adds synchronized video personas for enterprise deployments. These capabilities, announced in September by Google DeepMind, raise the bar for what a voice interface must support.

So the latest UI test arrives against this backdrop. The waveform change isn’t cosmetic alone. It pairs with a control that directly addresses a common pain. Lowering system volume to silence Gemini disrupts other audio. A dedicated mute fixes that. Early code suggests the speaker button targets voice output specifically.

Observers note the build remains incomplete. Missing buttons could return. Future versions might layer in the neural styling seen elsewhere. Integration with recent model improvements seems likely. Users already expect Live to handle camera input, screen context, and complex tasks without dropping context.

Google has stayed quiet on timing. No official comment accompanies the teardown. History shows these code discoveries often precede releases by weeks or months. The company continues to iterate quickly. Previous redesigns reached beta testers within months of first leaks.

Competitive pressure plays a role. OpenAI’s voice mode in ChatGPT and other assistants push similar natural dialogue. Google counters with deeper Android integration, camera access, and now accessibility tools like Guided Vision. The speaker icon fits this practical focus. Make voice mode usable in more situations. Reduce interruptions to daily phone use.

Look closer at the waveform itself. Earlier designs used simpler pulsing bars. The new animation appears more fluid. It may better reflect speech patterns or model activity. Exact visuals remain limited to demo videos in the teardown report. They show movement but no live responses. Still, the shift signals attention to detail in an area users stare at during every conversation.

Broader Gemini app changes provide context. Sidebar updates, Discover tabs, and thinking response sheets have appeared in other teardowns. The Live interface evolves alongside them. Nothing stays static. Each adjustment aims to make the AI feel less like a separate app and more like an always-available partner.

The speaker control could prove especially valuable during longer sessions. Planning a trip, debugging code, or simply chatting. Quick muting without volume tweaks keeps the experience smooth. Pair it with Guided Vision for users who rely on voice descriptions of the physical world. The combination points toward more inclusive, less intrusive AI.

Of course, teardowns come with disclaimers. Features spotted in code don’t always ship. Elements can change or disappear entirely. This redesign might look different by release. Buttons could reappear. Animation styles may receive further polish. Yet the core ideas — updated visual feedback and independent voice controls — address real user feedback.

Industry watchers on X reacted quickly to the Android Authority report. Many highlighted the mute button as overdue. Others speculated on ties to upcoming model features. The conversation reflects growing maturity around voice AI. Early excitement about natural talk has given way to demands for practical controls and accessibility.

Google’s pace suggests more updates soon. The company already ships new voices, memory access, and app integrations for Live. Visual understanding keeps improving. Each layer adds complexity to the interface. Clean, intuitive design becomes even more necessary.

This latest glimpse offers a narrow window into that work. A new waveform. A speaker icon. Small pieces. But they hint at larger goals. Make Gemini Live the default way many interact with AI on Android. Fluid enough for everyday use. Powerful enough for demanding tasks. And controllable without hassle.

Expect further refinements. The pattern holds. Code appears. Testers enable it. Feedback rolls in. Polish follows. Then rollout. For now, the speaker button stands out. Simple. Direct. And potentially quite useful.

from WebProNews https://ift.tt/43q1BuD

Motorola’s Bold Flagship Gamble: Why the Signature 27 Might Finally Deliver on Longevity

Motorola once dominated the cellphone business. Then it faded. Now the company, owned by Lenovo, wants back in the premium Android fray with a phone built to last. The Signature 27 arrives with hardware that matches top rivals and a seven-year software promise that once seemed unthinkable from the brand.

Yet one veteran reviewer looked at the specs, weighed the company’s track record, and chose to pass. Her reasons cut to the heart of Motorola’s uneven history with updates, regional availability, and consumer trust. And they matter more than ever as flagship prices climb past $1,000.

The original Motorola Signature launched early in 2026 to strong early praise for its slim design, capable cameras, and near-stock Android experience. Android Central called it the best camera and software package the company had produced in years. Reviewers highlighted the 6.8-inch LTPO display, triple 50-megapixel sensors, and clean Hello UI. But the device skipped the US market entirely, limiting its reach.

That decision stung North American fans who had watched Motorola focus on foldables like the Razr line while ceding slab flagships to Samsung and Google. “We heard you, we heard media, we heard analysts, and I’ll be honest, we even heard from a lot of customers in North America,” Nicole Hagen, executive director of global product marketing at Motorola, told Android Headlines. The response is the Signature 27.

Announced at Qualcomm’s Snapdragon Summit in September 2026, the new model brings meaningful upgrades. It runs the Snapdragon 8 Elite Extreme Gen 6, one of the first phones to use the chip. A 200-megapixel periscope telephoto lens replaces the 50-megapixel unit on the predecessor, promising stronger zoom performance up to 100x with AI assistance. The main sensor is now a 50MP Sony LYTIA 910. Cooling gets an ArcticMesh system with diamond-infused thermal gel and a larger vapor chamber.

Audio marks another first. The Signature 27 is Motorola’s initial handset tuned by Bang & Olufsen under a new multi-year partnership. Colors include PANTONE Coal Smoke and Capulet Olive. It ships with Android 17 and Google Gemini integration for on-device AI tasks.

Most significant remains the support pledge. Seven years of OS upgrades and security patches from global launch. That matches Google and Samsung on their top devices. It positions the phone as a longer-term investment in a segment where many handsets feel obsolete after three years.

But Irene Okpanachi at Android Police isn’t buying in just yet. She praises the hardware as “incredible.” Then she walks away. The headline says it all: the very qualities that make the phone appealing also highlight Motorola’s spotty past.

Her skepticism rests on broken promises. The Moto Z4 launched with one major update commitment yet delivered poorly. More recent devices have improved, with the Edge 60 Pro and Edge 50 Fusion receiving Android 16 in September 2025 and the Signature series plus Razr models getting Android 17 in October 2026. Two solid rollouts, she notes, do not wipe out a longer pattern.

Support has always been a weak spot for Motorola flagships sold in developing markets. Many buyers there treat phones as shorter-term tools. The company has sometimes tailored update cadences accordingly. Okpanachi worries the Signature 27 could follow if sales volumes or user bases in certain regions prove too small to justify full-term maintenance. GrapheneOS users already represent a niche; what happens if broader support wavers?

Real-world evidence fuels the doubt. A follow-up review at 91mobiles revisited the first Signature months after launch. The device still ran the January 2026 security patch with no major updates delivered. That lag for a phone advertised with seven years of support raised immediate questions about execution. Eight months later the software felt dated compared with newer Motorola models.

Regional inconsistencies compound the problem. Motorola’s update policies have varied across websites, with some listings promising different timeframes for the same device. The EU’s regulatory database has shown longer windows than the company’s own support pages in certain cases. Such confusion erodes confidence even before a buyer unboxes the phone.

Availability adds another layer. The first Signature stayed out of the US, pushing American buyers toward carrier-specific Edge models or Razr foldables. The Signature 27 changes that. It reaches North America in November 2026, according to reports from PhoneArena and 9to5Google. Motorola confirmed the move after hearing direct feedback from disappointed customers who had even imported the prior model.

That reversal signals responsiveness. Yet it also underscores past missteps. For years Motorola treated the US as a foldables-first market while global buyers in India, Europe, and Latin America received the slab flagships. Pricing for the original started around €999. The successor is expected higher, though exact US figures remain undisclosed. Early India sales put the first Signature at roughly Rs 55,000 after discounts.

Camera ambitions stand out on paper. The 200MP telephoto should excel at distant subjects and concert shots. Motorola pairs it with a Video Enhancement Engine that analyzes scenes in real time to adjust tones. Sample images have not yet surfaced widely, leaving performance an open question until reviews arrive. Early hands-on reports from the India Mobile Congress in October praised the overall build but withheld final judgments on image quality.

Battery life and charging details stayed under wraps in initial announcements. Okpanachi waits for confirmation before committing. She points out that flagship endurance often determines daily satisfaction more than headline specs.

Enterprise interest could grow if the seven-year commitment holds. Longer support suits business deployments where devices stay in service far beyond typical consumer cycles. Motorola has not detailed specific management features for the US market, but the policy alone may open doors.

Competitive pressure has clearly influenced the strategy. Samsung and Google now set the standard at seven years for their premium and many midrange models. Motorola can no longer compete on hardware alone. The Signature 27 represents an attempt to match that standard while adding distinctive camera and audio touches.

Whether the company follows through will decide its credibility. Past Edge and Razr devices received far shorter windows, sometimes two or three OS updates. The Signature line appears to mark a deliberate split. Motorola has tied the new naming convention — using the last two digits of the launch year — to a promise of consistent flagship treatment.

Analysts and buyers will watch the first update cadence closely. If the Signature 27 receives timely Android 18, 19, and beyond, skepticism may ease. Delays or regional carve-outs could reinforce old doubts. The pressure, as one writer noted, is what shapes the outcome.

Recent coverage shows growing optimism mixed with caution. Gizmochina highlighted the Snapdragon platform, advanced cooling, and B&O audio during the device’s showcase at India Mobile Congress. No full pricing or final availability dates emerged, but global rollout continues as planned.

Okpanachi’s piece captures the tension perfectly. The hardware tempts. The history warns. For a company that built its reputation on innovative phones decades ago, restoring faith in software support may prove the hardest upgrade of all.

Consumers now hold longer expectations. They pay premium prices and want devices that remain secure and capable years later. Motorola says it listened. The Signature 27 will test whether that message translated into sustained action.

from WebProNews https://ift.tt/UyOM6jr

Twilio CEO Jeff Lawson’s ‘I’ Test: How Pronoun Use Reveals Top Talent

Twilio CEO Jeff Lawson has built a reputation for an unusual approach to hiring top talent. During interviews that stretch across a full meal, he pays close attention to one particular word. If a candidate repeats it too often, the conversation ends without an offer. The word is “I.”

Lawson described his method in a recent conversation covered by Fortune magazine. He explained that the dinner setting removes the formality of an office and lets him observe how someone interacts over time. A 45-minute meal provides enough space to watch body language, listen to stories, and gauge genuine curiosity about the business. What stands out most to him is the balance between self-reference and outward focus. Candidates who constantly circle back to their own achievements, using “I” as the subject of nearly every sentence, signal that they may struggle to put the team or the customer first.

This preference reflects a broader philosophy at Twilio, the cloud communications platform known for powering SMS notifications, voice calls, and authentication flows for companies around the world. Lawson believes successful employees succeed by solving problems that matter to others rather than by collecting personal wins. When someone talks mostly about what “I built,” “I shipped,” or “I led,” the CEO starts to wonder whether that person will collaborate effectively or simply chase individual credit.

The dinner interview format itself carries practical advantages. Lawson chooses restaurants that encourage relaxed conversation, often spots with good lighting and comfortable seating. He arrives early, orders something simple, and lets the candidate pick the table. From the moment the menu appears, he watches how decisions get made. Does the person ask about the server’s recommendations? Do they show interest in the chef’s background? These small signals hint at larger patterns of curiosity and respect for expertise.

Once the food arrives, the real evaluation begins. Lawson steers the discussion toward real challenges Twilio has faced or hypothetical scenarios the company might encounter. He listens for how often the candidate frames answers around their solo contributions instead of the collective effort that produced results. A healthy mix of “we” and “I” feels natural to him. An overwhelming number of “I” statements raises a red flag.

Lawson’s stance stems from years of observing team dynamics inside fast-growing technology organizations. Early in his career he noticed that the most effective engineers and product leaders rarely led with personal pronouns. They described projects by naming the problems they solved, the customers they served, and the colleagues who helped them succeed. That pattern repeated across multiple companies until it became a reliable predictor of cultural fit.

At Twilio, this hiring filter supports a specific kind of culture. The company operates in a competitive space where developers expect reliable APIs, clear documentation, and responsive support. Employees who focus outward tend to anticipate customer needs more accurately. They notice when an integration breaks for a small business in another country or when a pricing model confuses a large enterprise. Those observations lead to product improvements that strengthen the entire platform.

The CEO does not reject every candidate who slips into first-person language. Occasional use of “I” is normal and even necessary when describing specific responsibilities. What concerns him is repetition that crowds out any mention of teammates, mentors, or end users. He has passed on otherwise impressive applicants because their stories felt like solo hero narratives rather than chapters in a larger book.

Lawson’s approach aligns with research on effective leadership that emphasizes collective intelligence over individual brilliance. Psychological studies have shown that groups perform better when members feel their contributions are noticed and valued. Leaders who constantly highlight their own role can unintentionally suppress that sense of shared ownership. By screening for pronoun balance during dinner, Lawson tries to identify people who will naturally reinforce a collaborative environment.

The dinner setting also reveals how candidates handle ambiguity. Menus present dozens of choices with incomplete information about ingredients, preparation time, and portion size. Watching someone navigate those decisions offers a low-stakes preview of how they might approach product trade-offs or engineering prioritization. Lawson pays attention to whether the person seeks input from others at the table or decides unilaterally. Both styles have their place, but consistent self-focus often predicts trouble in cross-functional roles.

Some candidates prepare for traditional interviews by memorizing their greatest hits and framing every story around personal impact. They arrive armed with metrics that begin with “I increased revenue by…” or “I reduced latency to…” Lawson appreciates results but wants to hear how those outcomes connected to broader goals. He asks follow-up questions that invite reflection on what others contributed or what surprised the team along the way. When those prompts still produce monologues centered on the self, he mentally moves on.

The 45-minute window is deliberate. It is long enough to move past surface-level pleasantries yet short enough to maintain focus. By the time dessert menus appear, Lawson usually has a clear impression. He has learned that the quality of questions a candidate asks often matters more than the quality of answers they give. Someone who inquires about Twilio’s biggest obstacles, the competitive threats on the horizon, or the experiences of current employees demonstrates genuine interest. Those questions tend to come naturally to people who think in terms of “we” rather than “I.”

Lawson acknowledges that his method is subjective. Not every role at Twilio requires the same level of collaboration. A specialized researcher working alone on cryptographic protocols might succeed with a different balance of pronouns than a customer success manager who interacts with dozens of clients each week. Still, the core principle remains: the company advances when employees direct their energy toward shared objectives.

This hiring practice has influenced how other leaders at Twilio conduct interviews. Many now incorporate meals or extended informal settings into their processes. They report that the shift in environment changes the tone of conversation and uncovers dimensions of personality that conference-room meetings rarely reveal. The added time also allows candidates to relax and show more authentic versions of themselves.

Critics might argue that judging someone by pronoun frequency feels arbitrary or even unfair. Lawson counters that the word “I” functions as a proxy for deeper attitudes about teamwork, customer obsession, and intellectual humility. He compares it to body language or tone of voice—subtle signals that experienced interviewers learn to read. Over time, the pattern has proven reliable enough that he continues using it.

Twilio’s growth from startup to public company offers supporting evidence. The organization maintains a reputation for strong engineering culture while scaling to serve millions of developers. Many of the executives who helped build the platform still speak about their work in terms of collective achievement. They credit open-source communities, beta testers, and frontline support staff for insights that shaped major features. That consistent message reinforces the cultural norm Lawson looks for during dinners.

Candidates who clear the “I” test often display other positive traits. They tend to listen more carefully, ask sharper questions, and demonstrate awareness of how their potential role fits into larger systems. They talk about learning from failure rather than avoiding it. They mention specific colleagues who challenged their thinking or expanded their perspective. These details paint a picture of someone who will strengthen the team rather than simply occupy a seat.

Lawson does not pretend his method is perfect. He admits to occasional misses and keeps refining the questions he asks. Yet the core idea remains constant: great teammates talk about problems, solutions, and people, not just themselves. In a business where success depends on thousands of developers choosing to build on your platform, that outward orientation matters.

The dinner interview has become something of a legend inside Twilio. New employees sometimes hear stories about the CEO’s unusual filter and wonder whether they would have passed. Many discover that the same principle applies to performance reviews, strategy discussions, and even casual Slack threads. The company rewards those who frame their work in terms of collective progress.

For job seekers hoping to impress Lawson or leaders who share his perspective, the advice is straightforward. Prepare stories that highlight collaboration. Practice describing achievements by naming the contributions of others. Focus questions on the company’s challenges rather than personal opportunities. Treat the meal as a chance to learn rather than a stage for self-promotion. Most of all, let genuine curiosity guide the conversation. When that happens, the word “I” naturally finds its proper, limited place.

Lawson’s method offers a reminder that culture is built one decision at a time, including decisions made over appetizers and entrees. By paying attention to language patterns that reveal values, he tries to ensure that every new hire strengthens the shared sense of purpose that has driven Twilio forward. In an industry where talent wars never end, a simple pronoun can speak volumes about whether someone belongs.

from WebProNews https://ift.tt/0imleYD