ingenium

Yeah 3xCA has been live on the Pixel. It was pushed as a profile update mid-May. It's just that SF doesn't have many sites with 3 carriers, though it seems that's been changing. Check the last post I made in the SF thread to see the ones found so far. There are likely more by now, assuming that wasn't just a trial period. Sent from my Pixel XL using Tapatalk

I think any address that shows B41 coverage on their map qualifies. I put in my address in Berkeley (a block from a B41 site with excellent coverage throughout the house) and it qualifies. I think they're doing this because they can't predict indoor coverage, so they're assuming if you're asking for a MB, you prob need one. Sent from my Pixel XL using Tapatalk

Depends on your layout. My house long (townhouse) and is 4 stories, and I have my 540 on the 3rd floor in the back (macro is maybe 0.4 miles away, line of sight minus a brick wall, but between sectors). MB relay signal is -94. It reaches all but the far corner of the basement. I expect the 545 to reach there. I get about 15 mbps per carrier down (2xCA = 30 Mbps, it just takes a second for the relay to engage it). Upload is 15-17 Mbps ish. If it's in a room, I suggest trying to aim it so it points out the door towards the main part of the house. Mine is aimed to go down the hallway, which I'm sure helps. Also curious, what software version is it running? It may take 24+ hours to update to the newest version. Sent from my Pixel XL using Tapatalk

There's no backlight? And not color? The screen on the 540 is very poor with regards to touch sensitivity. And it's pretty bright and always on. Sent from my Pixel XL using Tapatalk

Interesting. The exterior design is noticeably different from the 540 model. Vents moved to the bottom. Looks a bit thinner too. Still using the same pink foam for packaging lol. Sent from my Pixel XL using Tapatalk

Which brings up an interesting point, what is the MNC/MCC in such a case? Will the MB broadcast multiple providers? Will it be random based on which one the MB decides to use (assuming the donor broadcasts multiple)? Sent from my Pixel XL using Tapatalk

No they cannot. They require a macro class donor. Sent from my Pixel XL using Tapatalk

Those errors are from enabling the root earfcn method in SCP I believe. They're unrelated to calling plus. Sent from my Pixel XL using Tapatalk

I did. It seems they were batch sent at 1:15pm eastern time. Sent from my Pixel XL using Tapatalk

Actually I just tried using them and it seems to work now! Maybe there was some other reason I had to stop using them... I had the tasks built, but had commented out using the intents in favor of using the manual root method, so there must have been a reason... I'll switch back and see if I can figure out what it is. I'm trying to reduce my reliance on needing root for things, and this is a step in the right direction. Too bad there's not a way that I'm aware of to query the current status of the Background Service option without root (necessary for a simple toggle switch). You could probably respond with an intent upon receiving a query intent http://tasker.dinglisch.net/userguide/en/intents.html though I know that's probably a lot of work for a feature few would use. If I wrote the code to handle this and respond to it and debug it, would you consider trying to add it to see if it works? I wrote a Tasker plugin a few years ago that acted as a middle man, relaying intents between Tasker and another app (that app required a certain permission to use its intents, which Tasker didn't request. My plugin requested them and proxied the intents). So I could probably pull a lot of the code from there. Sent from my Pixel XL using Tapatalk

Yes it should work. It's not tied to any specific site, just basically factory reset it and go through the config process in the new location if you move it. The MB I currently have previously belonged to a Sprint RF engineer in Texas. It integrated into the network in Pittsburgh just fine using the correct EARFCN. That being said, there is still some kind of flag on my MB that is allowing it to get beta software updates. I'm currently on 15.15.10.113 (pushed early this month), while the latest official build is 15.15.10.63. I previously was updated to 15.15.10.93 the day after I set it up in May, so the flag is definitely still present. Sent from my Pixel XL using Tapatalk

While you're doing updates, if you have any time can you take a look at the intents you added for me for Tasker? They never quite worked right, so I've still been using my root method to edit SCP's config file each time and force kill it. If I remember correctly you have intents to enable and disable logging and location, and something else? Ideally I'd like one to enable/disable the background service, and one to gracefully exit. I keep the background service off unless I'm driving/traveling, so having these two would make it easier to automate. Sent from my Pixel XL using Tapatalk

Just got the call approving me for a MB. They approved it for the address on the account rather than the address I applied with. The account address barely gets B26 and 1x800, not even B25, yet it somehow qualified [emoji23]. Had them update it to the address where I'll actually be using it. I had the same issue the first time they opened applications; they only saw the account address not the application address. So for anyone getting denied, make sure you verify that they're using the right one. Estimated delivery is "6 weeks to fall, based on how early you applied", and they'll send an email before shipping it. Sent from my Pixel XL using Tapatalk

TM-4, that's interesting. I don't think Sprint uses that, or at least I've never seen it. Sent from my Pixel XL using Tapatalk

Hmm the B25 one must be stale data, since it's using the G block. Sprint has that nationwide. Sent from my Pixel XL using Tapatalk

B25 is a superset of B2, the only difference I believe being B25 adds the PCS G block. I think SCP just identifies it based on earfcn or gci, so it's likely a bug. Unless ATT started advertising their B2 as B25. Sent from my Pixel XL using Tapatalk

SCP does not show CA status at all. It shows which carrier is the PCC only. For 3xCA you have the PCC (primary carrier, which is used for upload) and 2 SCCs. The PCC is essentially random to load balance between them. Sent from my Pixel XL using Tapatalk

Nexus / Pixel devices don't have wifi calling. So it's not an option. In many cities the density is fine for VoLTE. I'll go months without dropping LTE. It would be nice to at least have the option. Sent from my Pixel XL using Tapatalk

People keep saying this, but in my experience it's horrendous. It's been the case for years, Galaxy S4 (1x800 only when that was prioritized in the PRL, 1x1900 was fine), Nexus 6, 6P, and Pixel XL. It seems to be I'm mostly in congested areas, in more rural areas or at night it's usually fine. I think CDMA carriers are overloaded with voice calls, and quality goes to shit to handle more calls. With the refarming it's just gotten worse to the point I use Hangouts for calls now. I can't understand a word the other person says during peak usage, it's all garbled. For this reason I can't wait for VoLTE. Their CDMA network is useless to me for voice calls in its current state. Sent from my Pixel XL using Tapatalk

Some carriers in other countries do it. I was just in Indonesia and had a SIM with Telkomsel. They have a different data bucket for midnight-7am (and different ones for LTE vs non-LTE) to encourage bulk usage in off-peak times. It's a new policy, because 2 years ago they didn't do this (nor did they really have much LTE deployed... whereas now it's solid coverage). Was perfect for me to do Google Photos picture and video backups. Sent from my Pixel XL using Tapatalk

Possible bug, this is showing as 10x10 second carrier, and I think it's just first carrier based on the earfcn. Also, it looks like second B25 carrier is showing in Pittsburgh with 08 GCI ending. It's not 10x10 though, only the first carrier is. I couldn't get a screenshot with valid earfcn data though, it kept kicking me off as soon as I connected. EDIT: Actually, I just realized the GCI is the same for each of these... but TAC and PCIs differ. And the GCI isn't in Pittsburgh's range. Could be a weird issue of persistent bad data...

Probably not load balancing correctly off of B41. They don't anticipate B41 being over capacity I don't think. And even so, B25/26 probably wouldn't last very long if they were actively moving people to it because B41 was overloaded. Sent from my Pixel XL using Tapatalk

Where at? Was it near a Sprint store? The one in Berkeley has a MB. And I saw one in NYC also with a MB. Sent from my Pixel XL using Tapatalk

Roaming in Indonesia is now XL (Excelcom), HSPA+ max (ie no LTE). Surprising since XL is apparently a primarily LTE network from the quick research I did. My bf's phone (Nexus 6P, with Open World, profile update done 2 weeks ago before leaving) will not roam here though. It just says emergency calls only. XL does not show up in the network list, just the MNC MCC combination for it. When I select it, it gives an error about the SIM being incapable of registering on the network. It's possible it requires a newer SIM than the one Sprint uses for the 6P? My Pixel is using the BYOD SIM and works fine. EDIT: Screenshot showing the 6P refusing to connect to all networks Sprint roams with, Indosat and 510 11 (XL)

No, since it's pay per MB I didn't do any speed tests. It was quick though. The airport has a DAS, and I was just there for a layover, so I can't speak to coverage and speed outside of there. Also LTE roaming in Singapore (screenshot below) and Cambodia. Sent from my Pixel XL using Tapatalk