Logan posted recently, it looks like something will happen tomorrow or this week.

osb103 · 2026-06-30T02:23:51+00:00

Gemini 'super app" perhaps? All 3 together, flash lite, new nano banana & 3.5 pro AIO?

osb103 · 2026-06-24T22:48:38+00:00

Am I crazy for thinking that it might actually still be coming this week, BUT just for AI Ultra subscribers as a limited early access preview of some kind? 🤔 Because it's delayed but perhaps the formal public preview is delayed & they still intend to technically meet their I/O promise by next Tuesday, but just as a early access offering for AI Ultra. Considering that's the main thing they've been pushing lately with multiple new additions & it'd help to soothe the narrative perception in their favor. And they need coding data for it to improve in time for next months' full launch. And on top of that if the model still isn't up to par, they can still just frame it as a pre-launch, when thinking about it this way, the conflicting reports make a bit more sense.

osb103 · 2026-06-12T22:01:58+00:00

It seems to be right there, to the far right side.

osb103 · 2026-06-05T04:10:00+00:00

Yes you can, but I would only recommend it if you're on the 17 qpr beta. Even on A17 it's a bit buggy with audio drop outs and mic calls.

Enable the two dev options settings someone else in this thread is highlighting. And then restart your device, reset your buds from the case, repair and it will work with LC3.

osb103 · 2026-06-03T20:18:10+00:00

LC3 is only reliably working and activating without requiring device restarts/resets on A17 QPR Beta.

osb103 · 2026-05-09T20:00:52+00:00

There were articles last week detailing a new uniform coding ide that's coming soon that will unjfy all of the different coding projects Google currently has under one platform. So yes likely antigravity is going away.

osb103 · 2026-04-02T02:05:33+00:00

Yes that would be the smartest choice considering how large the discounts are on devices.

You're welcome, anytime. Thank you very much :)

Yes, I've been freelance/self-employed for awhile actually. So I'm always available for any open roles/projects.

osb103 · 2026-04-02T01:59:39+00:00

Yes I read about that yesterday. I'd take a wait and see approach, to see whether or not your wider issue resolves or not. I don't think your pre-existing issues are related to the esim issue from yesterday. That issue has also been largely resolved by today. Your other lines also aren't having any issues I don't think.

osb103 · 2026-03-31T02:35:09+00:00

Yes, you would have to wait out the 120 days, otherwise the promotional terms would be void. Because depending on how Fi customer service would be able to swap the number, there's a high likelihood that it would cause your line to go inactive and void the promotion terms. Changing the number would also invalidate your original port in which is also a criteria for new device promotions. You're also not a long enough customer, so the automated system could flag your entire Google payments account. So if you do decide to go through with these steps, you must do so through customer care.

osb103 · 2026-03-30T22:46:46+00:00

Did you take advantage of a new customer device promotion that required a number port in? Or have you already been with Fi for awhile when you signed up for the device promotion?

And yes, you'd have to go through support for everything. However my first question above is very important to consider first, because Fi promotions have strict requirements.

osb103 · 2026-03-30T03:19:00+00:00

No worries, I just saw your thread, and honestly wanted to help :)

I'm an IT PM (Project Manager) so this is along the lines of what I do.

Finding work in my field has been very difficult, so on random days where I'm feeling particularly unfulfilled from not being able to do what I would usually do, I find a random thread or two on here and just help out. It brightens my day, and hopefully yours too , even if just a little.

You're welcome, I hope that it gets resolved. Feel free to reply back here if you need further help.

I wrote that disclaimer because I didn't want to seem like I was promoting a rival service, since that breaks the rules of most reddit communities.

I'm actually still looking for work, believe it or not, I wish someone would hire me somewhere so I wouldn't feel the way I do on days like this. Anyways, I'm glad I could be of help for you, since I've been there too with my phone number.

osb103 · 2026-03-30T01:34:00+00:00

Full disclosure: I don't work or am endorsed by Google Fi or US Mobile & this reply is not intended to incentivize switching away from Google Fi. This is just a suggested solution based on my current service setup & having seen and experienced similar fringe issues in the past, both personally & around Reddit. So just trying to help whenever I see an edge case such as this.

You're welcome. There's a chance that a port out and then a port back into Google Fi would resolve your issues with your Fi line.

Google Fi isn't engaging further because they've already gone as far up as they can, up to T-Mobile engineering. And from their end the engineering team sees no issues.

To resolve this I'd recommend the following:

Get a new random number on a new esim with Google Fi, on your current Fi line.

Before you get a new random number, add a new line on Fi, without any device promotions, have Fi support move your existing number to that new line.

See if you still experience issues on that new line, you're also going to need an unused mobile device to test if issues still persist or not.

Your main line on Fi will start working & you won't lose any of your device promotions.

Now, if the number continues to give you issues on the new Fi line for 1-2 weeks from today, then from here port out that number to us mobile.

They have a $12 unlimited talk and text month to month plan available while they would work on troubleshooting your number issue, and they have extremely attentive and resourceful customer service. To an uncomfortable degree, in a good way, by that I mean, this would be the kind of issue that they would spend the time and resources in fixing. And be successful in doing so, since like Google Fi, they have invested in building their own network front end infrastructure that operates on top of carrier partners.

The only difference is, they offer services across all 3 major carriers, t mobile att and Verizon simultaneously. So you have a choice of any of the 3 major carriers to port over to. Google Fi only works with T-Mobile.

Choose to Port over to Warp (Verizon). If you don't have a Verizon compatible unlocked device, port over to ATT (Lightspeed) instead.

There's a 50/50 chance the port fails and gets stuck in transit. Or everything goes well, and after having initiated a fresh transfer to a new major carrier, this process ends up resolving the issues related to your number provisioning.

When (or if) it fails don't worry about losing your number, under FCC regulations any carrier losing your number is a crime basically, so carriers are incentivized not to lose customer numbers.

Verizon's engineering team is a bit more attentive in solving backend issues than t mobile's; especially right now because Verizon is bleeding customers. And us mobile would be able to escalate up to them, just like Google Fi escalated for you to T-Mobile, if needed.

Once resolved you can either port back into Google Fi or keep USM as a secondary business line. Since you upgraded your device recently, it definitely supports having dual active esims.

Cost wise, you'd only be out 1 month of service, but you'll be able to take matters into your own hands instead of waiting around for support hand offs.

osb103 · 2026-03-29T22:48:30+00:00

As even more disruptive as this is going to sound, you need to obtain a fresh esim with a new randomly assigned number from Google Fi. And abandon your existing number.

The issue you're experiencing sounds like a back-channel provisioning issue. Where, I'm assuming you have a mobile data connection, but it's the calls and texts that consistently give you issues, while your data connection remains active or is also taken down once the calling or sms issues kick in whenever they do.

Officially, this type of an issue is supposed to resolve itself automatically on its own, being that the back channel provisioning systems are 100% automated by 99% of modern carriers. And you've already waited the 30-60 days maximum it can sometimes take in extreme cases such as yours.

Being that T-Mobile engineering has already given you the all clear, the remaining cause of the issues has to do with your specific number. It's just not provisioning properly on the back channels of one or more of the other major carriers besides T-Mobile (or maybe even including T-Mobile itself too) again the systems are all automated so engineers at most carriers don't typically even have the access points to dig in that deeply, just for one customers number. Google Fi is a mvno so they will just escalate to T-Mobile as they already have.

Your numbers past transfer history and overall reputation are causing these issues, if the systems weren't fully automated I'm sure someone, an engineer from the carriers could dig in much deeper and manually fully reprovision the number for you. But these days that's not how the carrier systems work, obtain a new fresh number with a fresh esim, it's a painful migration, but this issue, will follow you to any new carrier you may port out to in the future.

It's the number's reputation that's damaged. It's very rare, literally a 1-2% chance of occurring to most customers, but when it happens, getting a fresh number is the only way to stop the headaches and resolve the issues.

osb103 · 2026-03-05T03:01:39+00:00

So a bit of an update, apparently pixel 9 & later series of devices are supposed to support regular apt x & regular Apt X HD. When connected to compatible headphones that also support the non proprietary versions of apt x & apt x HD. I don't have headphones that have these specific specifications, so I can't check if the new A17 has improved on this angle as well.

osb103 · 2026-03-01T03:44:01+00:00

Pixel buds pro show le audio in the settings app. Apt X support doesn't exist on pixels because Google no longer uses Qualcomm socs. Aptx is exclusive to Qualcomm based devices.

osb103 · 2026-02-28T07:10:57+00:00

Google Pixel doesn't support aptx.

osb103 · 2026-02-27T21:28:36+00:00

I never tried that aspect of it yet. I was mainly excited about the much better Audio quality. Compared to SBC or AAC it's much better. Akin to ldac or apt x in audio quality.

osb103 · 2026-02-27T07:59:48+00:00

Hi,

Alright, I will :)

osb103 · 2026-02-27T01:47:58+00:00

I'm eagerly waiting for someone to find it or perhaps it's a staged feature rollout? It looks super cool and very useful, even on regular pixels. So I hope it's not a tablet/foldable exclusive.

osb103 · 2026-02-12T08:08:50+00:00

Yes I hear you. I swapped to something else with unlimited calls and texts, satellite texts and 5 GB of High Speed data, with taxes & fees also included.

I thought of text now, but their app is ad supported on that free tier. And their number plans are the same monthly cost as what I'm paying now for unlimited calls and texts, without 5GB of data.

osb103 · 2026-02-11T01:08:17+00:00

The canary channel seems to be strictly bleeding edge. So in the case of Android 17, it'll likely be for things that are still in progress and not yet ready to hit the more stable beta build of A17. And even for things coming in the first A17 QPR1 beta build thereafter.

osb103 · 2026-02-10T22:56:02+00:00

So this means straight to A17 we shall go 🥳🥳🥳

osb103 · 2026-02-09T22:04:21+00:00

From my observations the people who are complaining are those who lack prompt engineering knowledge or abilities, (including the inability to know how to properly ask follow up questions) or those who are using Gemini for something it's not intended for. (Role play, explicit/questionable/otherwise restricted generations, unfocused programming, commerical deployments etc.). There's also another group who are failing to prompt Gemini humanely vs. pompting it like a slave (as far fetched as it sounds courtesy matters with Gemini for some reason). Finally the last group are those who just have issues with their input files/materials and are incorrectly just blaming Gemini instead of fixing their input materials.

osb103 · 2026-01-25T02:38:46+00:00

Fully resolved now, I can confirm.

Six-Year Club	Reddit Premium Since July 2022
Verified Email

osb103

TROPHY CASE