crazy_vag

1 hour ago, nexuss4g said:

Still havent been able to update to Android 10 on my P3XL as it fails to install.

I've had trouble updating Chrome, but a few weeks later, Google seemed to have fixed the installer.  There's the lazy option of waiting a few more weeks in hope of installer getting fixed.

Or 2 more weeks until October security update - which might fix it.

Or 4 more weeks until Pixel 4.

On 9/21/2019 at 5:53 AM, ingenium said:

Yup! It came with the Android 10 update. Glad to have it officially supported instead of requiring a hack.

The question is, does it continue to ignore the VoLTE flag on the eNB (ie, will it work on a Magic Box or Airave), unlike other VoLTE enabled devices? I've been out of the country since it came out, so haven't been able to test.

Sent from my Pixel 3 XL using Tapatalk
 

No VoLTE on Magic Box Gold.... 

On 9/16/2019 at 8:37 AM, ingenium said:

I would love an 8GB Pixel. The question is, what 5G bands will it support? Verizon or Sprint and T-Mobile?

Sent from my Pixel 3 XL using Tapatalk
 

I'd guess it's just like early LTE days.  Where you have an AT&T LTE phone, VZ LTE phone, Sprint LTE phone and TM LTE phone... 

Just noticed that VoLTE was enabled on my Pixel 3 XL.  Haven't used it yet, but my phone no longer needs to connect to  1x + LTE... It's now just LTE or Wi-Fi.  Life's Good!

2 hours ago, ingenium said:

The eSIM works on phones purchased from Google. I'm using it on mine. The issue is that you can't migrate directly from physical SIM to eSIM on the same phone. You have to first swap to a different/old device, remove the physical SIM from your 3, and then setup the eSIM on it (select add, then select Sprint). The phone will have you sign into your Sprint account and select which line you want to use, and that's basically it.

The issue I believe is because the IMEI is already in use and tied to the physical SIM, so it won't let you swap the IMEI to eSIM while in use. By swapping to a different device first, it frees up the IMEI to be linked to your eSIM.

Sent from my Pixel 3 XL using Tapatalk
 

Makes sense.

All that code to check IMEI to prevent you from upgrading to same phone is now coming to bite us.

Sounds like best to make the eSIM jump when getting the Pixel 4.

Hopefully eSIM supported from day 1.

In random news, this morning, my Pixel 3 XL froze.  When it rebooted, it said "No SIM".  Rebooted and reinserted SIM, but no go.  Tried a co-worker's SIM and it was recognized immediately, so chatted with Sprint about activating eSIM since was getting errors in the Pixel UI.  Chat referred me to call, and operator tried a few times, but got errors on their end, so told me to go to a store.

No line, but learned Sprint only does eSIM on Pixel phones purchased from Sprint.  They won't activate eSIM Pixel phones purchased from Google, so 5 mins later I was out the door with a replacement physical SIM.

Hasn't anyone successfully activated their Pixel 3 on eSIM with a phone purchased from Google?

On 8/19/2019 at 6:48 PM, lilotimz said:

I don't recall if I mentioned it here but major updates like those above features are usually sent out each quarter so it's not ready as I last checked a few weeks and they don't expect it til at least fall at the earliest.

They've been doing field tests on the alternative backhaul mode but it requires network configurations and hw deployments out of the hands of the MB team.

Sent from my Pixel 3 using Tapatalk
 

Thanks.  Can you share what kind of updates were pushed to MB Gold boxes over the past quarters?  How do you get this info?

Have there been any comments about VoLTE or WiFi/Ethernet backhaul?  I feel like it's the missing piece for networking at my condo.

Any rumors on the MB firmware upgrade to enable LTE backhaul?  Anything on VoLTE?

On 7/2/2019 at 12:12 PM, ericwalton said:

I just got a Pixel 3 XL and couldn't activate RCS messaging, it would just stay stuck on setting up and verifying number. I activated it using eSim.

I found that there were people on Rogers having same issue. The fix is to goto Settings > Apps & Notifications >See All > Carrier Services. When you click disable it'll give you an option to restore to factory. RCS worked immediately.

Just in case anyone else runs into it.

After you "disable" it, what's next?  Do you re-enable it or leave it disabled?  

After playing around some more, I'm convinced that Wi-Fi Calling isn't provisioned correctly on my phone.  It doesn't work in Airplane Mode, it doesn't work on any WiFi network regardless of the strength.  SCP does show WiFi calling enabled, but even then calls go over 1x.  

What's more annoying is that I can't disable Wi-Fi calling service on my account without customer support for whatever reason.

1 hour ago, nexuss4g said:

Have you tried using it on Airplane mode? Service is pretty bad in my work building due to cement walls and sometimes when calling it will use regular 1X and sometimes Wifi Calling. I have it set to Mobile Preferred but notice improvement in audio call when on Wifi calling. Also, when other devices are both  on wifi calling the HD logo appears on the call and audio quality is great.

  I'm not able to make calls when connected to WiFi only (Airplane mode on).   Whether I have Mobile Preferred or Wi-Fi Preferred doesn't matter.  

Can you actually make a calls while on Airplane Mode On with your Pixel 3?? 

Are there any other ways to troubleshoot Wi-Fi calling other than contact Sprint Support where they'll likely just blame Google?  Seems like I'm not able to remove Wi-Fi calling from my account either with contact support.

Even with WiFi preferred, even when signal check pro showing WiFi calling, even when LTE/1x signal at -115db and WiFi of 70db, my Pixel 3 XL won't pick WI-FI for calls.

It used to work about 4 months ago, but no more.

It stopped working around the time when the phone started holding onto 3G instead of going to LTE.

Sometime in the last month or so, I noticed that while I do get the Wi-Fi Calling icon showing in SignalCheck Pro, all my calls still go over the mobile 1x network instead of over Wi-Fi.  This is on my Pixel 3 XL with latest updates.  Anyone else notice that?

1 minute ago, ingenium said:

Yeah I would put in an order for an Airave 4 then. Then you can put it anywhere that you have Ethernet.

Google Fiber in SF? I know they bought Webpass a while ago (microwave backhaul), did they rebrand it to Google Fiber?

Sent from my Pixel 3 XL using Tapatalk
 

It's branded as "Webpass from Google Fiber", so either term works.  

What does Airrave 4 do that MagicBox Gold doesn't? 

It frankly took way too much calling to get this.  My journey to MB gold was a long one.  I had a MB before.  To get a "Gold", I had to return the original.  I did that, and then had to call to ordered the Gold.  I called, but got sent the same non-gold again. I returned that, and then was when return went through, was told Gold is out of stock and they can't order it until it's back in stock. Called a month later, but still out of stock.  Called a month later, but nothing arrived, order never placed or was lost.  Called again, but again, nothing arrived, order was lost or never placed.  Called the 3rd time, and this time the order arrived.  Getting an Arrive 4 might take long enough that I might as well just wait for the firmware upgrade that will enable/fix Wi-Fi.

3 hours ago, ingenium said:

Won't connect to Ethernet? Yeah it's a known issue. It used to not work at all. Now it's supposedly live in a few markets, but has some issues still. On the west coast it can sometimes connect but 0 throughput on some sites. Their backend isn't ready yet.

Better to factory reset it and try for relay backhaul. The other option is to request an Airave 4 instead, since it works with wired backhaul now. Supposedly the LTE portion will broadcast at the same power as a MB. They're made by the same company and should use the same components.

Sent from my Pixel 3 XL using Tapatalk
 

I don't have a place where I get good reception and have ethernet, otherwise I'd do that.  However, I can try that as an experiment to see if it works.

In the current location with LTE backhaul, my magic box gives about .1 Mbit uplink which sometimes is 0 and times out.  The antenna feels worse than on my PIxel 3, so I'm really looking forward to using Wi-Fi which runs off of Google Fiber.

1 minute ago, ingenium said:

Wired and wifi backhaul is not working yet. Current ETA is end of June. You might have to factory reset it to get it back to relay backhaul.

Sent from my Pixel 3 XL using Tapatalk
 

Ok. I'm able to select it, but sometimes it won't connect. But even when it does, I get no service. Which is not much different than without it.

A highrise went up better my condo and the tower, so already bad service is barely working now.

I just got my MB Gold! Curious what the latest firmware that it should be running?

I'm asking since I keep getting errors connecting the backhaul to my Google WiFi router.

Without VoLTE, at some point device availability could become an issue.  Suppose VZ shuts down their EVDO network at end of 2019.  Do you think that Pixel 6 in 2021 will still support CDMA just for Sprint?  

On 4/20/2019 at 11:28 AM, ingenium said:

I just successfully switched my Pixel 3 XL to use the eSIM on Sprint. Works out of the box now. Since I already had this phone on the line, I had to swap to another phone and then swap back with the eSIM. Everything works.

Super convenient. No more having to order the correct SIM from Sprint, and I can now swap between Sprint and another carrier easily (traveling internationally, or even using another domestic carrier).

Sent from my Pixel 3 XL using Tapatalk
 

Well, presumably I'll activate my Pixel 4 on eSIM, so won't need to worry about ordering a new SIM each year like I have been for the last 4 years.

When traveling internationally, the convenience and price of Sprint's roaming plan is really hard to beat, so I don't see myself changing plans when traveling.  

Speaking of which.  I used to be able to use data for SMS, but that ability has been removed recently.  Anyone else observe that?

17 hours ago, ingenium said:

There is an adb command that you can run, without root I think, that sets what radios are affected by airplane mode. I set mine to not disable Bluetooth. Get an adb shell and run:

settings put global airplane_mode_radios cell,wifi,wimax

You can leave out wifi if you don't want it affected by airplane mode. The default list is cell,bluetooth,wifi,nfc,wimax

Sent from my Pixel 3 XL using Tapatalk
 

Good tip.  I'll try it out.

BTW, yesterday after getting off Caltrain, my phone was back in 3G.  Since streaming seemed to work, I left it as is.  About 10 mins later, I noticed my phone roaming on TMobile LTE (B2 or B4, don't recall).  Then a little bit later, my phone went back to 3G.

I don't know if there's some upgrade happening in SF or if it's on the phone side.

Days of rooting have long gone with remaining reasons to do so limited to what you mentioned above.  No longer worth the effort.

After the update, my P3 still loves 3G... ugh. Wouldn't be bad if you could reset the radio via the DATA button, but you need a full Airplane Mode cycle to get that back - and you lose music, bluetooth and tethering connections in the process.