Jump to content

ingenium

S4GRU Premier Sponsor
  • Content count

    1,106
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by ingenium

  1. ingenium

    Pixel 2 by HTC User Thread

    Correct. No visual voicemail and no wifi calling or calling+. You can use conditional call forwarding with Google Voice though for visual voicemail. In my opinion it's better since you also get free transcriptions. Sent from my Pixel 2 XL using Tapatalk
  2. ingenium

    One Way Messaging

    Assuming there's internet, you could get a raspberry pi and code something up with Tasker/autoremote/IFTTT. Maybe have the pi have a browser full screen, with a page open that displays whatever it receives from autoremote/IFTTT. It would involve some coding/scripting on your part. Depends how comfortable you are with it, and what your requirements are for the message. Sent from my Pixel 2 XL using Tapatalk
  3. I think they've dropped support for it. You can't use an Airave 3 with it, as it will incorrectly QoS the Airave traffic and throttle it to a couple hundred KB/sec. Honestly your best bet is to flash a third party firmware to it. Merlin is pretty popular and is based on the stock firmware. OpenWRT / dd-wrt is also an option I believe, but I'm pretty sure hardware accelerated NAT isn't functional (you likely wouldn't notice anyway). Sent from my Pixel 2 XL using Tapatalk
  4. ingenium

    LG G6 to be Sprint's first HPUE-capable device

    Really? I've never had an issue getting an MSL from Sprint. I just do a chat and say something along the lines of "Hi. I factory reset my phone and now it's asking me for something called an MSL. Can you help me with that?" If a rep won't give it to you, just try again with a different one. I actually just got the MSL a couple days ago for one of my devices that's on a corporate account that I don't have access to... Took 2 tries though because I didn't have the account PIN. Sent from my Pixel 2 XL using Tapatalk
  5. So it seems there are at least 3 Sprint APNs: n.ispsn, r.ispsn, and x.ispsn. I remember seeing n.ispsn on some of my older devices. I have a hotspot from Calyx (via Mobile Citizen) that has a Sprint account that I can log into, and it's using r.ispsn. My Pixel 2 XL is using x.ispsn. Does anyone know what the difference is between them? My only guesses are that n.ispsn is "native", and r.ispsn is "reseller". Or perhaps n.ispsn is NATed via CGNAT and r.ispsn is "routed" meaning a public IP? I have confirmed that the hotspot that uses r.ispsn is assigned a public, routable IP. But that doesn't answer what x.ispsn is. My phone with x.ispsn is assigned a NATed IP.
  6. ingenium

    What is the difference between Sprint APNs?

    Do you know if you can change a device with n.ispsn to r.ispsn to get a routable IP with it? Sent from my Pixel 2 XL using Tapatalk
  7. Network Signal Guru. It's a root app that basically interfaces with the Qualcomm engineering driver to give low level modem/radio details https://play.google.com/store/apps/details?id=com.qtrun.QuickTest
  8. Interesting. Have you looked at it in NSG? If so, does it show throughput only on one of the aggregated carriers? Or does the throughput on each drop by 2/3?
  9. That site is absolutely broadcasting 3 B41 carriers, and your phone has engaged 3xCA on it. It is active and live. 3xCA speeds aren't necessarily super fast. If the site has a lot of users on it or the signal isn't that great, speeds will be slower. My home site only gets about 15 Mbps during the day on 3xCA for example. Sent from my Pixel 2 XL using Tapatalk
  10. Is 1x800 broadcasting? Sent from my Pixel 2 XL using Tapatalk
  11. That box on the bottom is "new" (ie not on other installations). It looks like a fiber ONT, I believe you can see the thin fiber strand entering it on the bottom. So I would guess this is a fiber fed one. The fact that Sprint is likely using different backhaul providers in the same area is exciting. Were you able to get engineering screenshots? Or anything showing the earfcn of it? I'm curious if it uses a different earfcn than relay fed small cells. Also, if you happen to have NSG, looking at signaling for what PLMNs are broadcast would be useful. It would tell us if a non-relay small cell could serve as a donor for other small cells or magic boxes. Sent from my Pixel 2 XL using Tapatalk
  12. ingenium

    Official Airave 3 LTE / S1000 NSC Thread

    Nope. I did for a period a while ago, but a power cycle fixed it. Sent from my Pixel 2 XL using Tapatalk
  13. ingenium

    Galaxy S9 Series user thread

    Yeah Sensorly was always the culprit when I noticed dramatically worse battery life. Somehow it seemed to reenable active background reporting (or maybe they call it passive) even when I hadn't used the app in months. Sent from my Pixel 2 XL using Tapatalk
  14. ingenium

    Official Magic Box discussion thread

    Yes, I've connected to probably 10+ in the wild. Yes, it's stored, since it doesn't rerun the initial setup. It's "sticky" and will reconnect to the same donor and same band as it was on previously. Only if this isn't found will it look for something else to connect to. Most models don't have batteries, and they behave the same. So it's stored on flash storage internally. Sent from my Pixel 2 XL using Tapatalk
  15. ingenium

    New Verizon MVNO

    Well you might be able to tell. YouTube uses different bitrates for the different resolutions. For example, if you force a video to load in 4k on a 1080p screen, it will look better than a video at 1080p from YouTube. When I upload videos to YouTube, I'll actually reencode a 1080p video as 4k for the upload, because YouTube won't degrade the quality as much as if it was 1080p (I've done side by side comparisons). So in this case, a downsampled 1080p video will look better than one that's natively at 720p. Sent from my Pixel 2 XL using Tapatalk
  16. ingenium

    Galaxy S9 Series user thread

    Facebook is known to do this. It's killed batteries for years. Sent from my Pixel 2 XL using Tapatalk
  17. ingenium

    Official Magic Box discussion thread

    My pings on my magic box are in the mid 60s usually. It got better after the latest software update, down from the 80s. It might take a couple days for the software to push to yours. Honestly, I don't really notice a difference at pings that low as long as the speed isn't slow. I can't tell when I'm on my MB, my Airave (about the same ping due to the ipsec tunnel), or the macro unless I get on b25/26 which are both congested (20ms-ish pings, but super slow, often sub megabit). What are you doing where pings of 60-80 ms are causing you noticeable problems? Also, if you're concerned about speed, run multiple speed tests back to back. Your phone is pretty aggressive at engaging CA immediately, but the magic box is "lazy" and will only engage it once there's been sustained data use for a bit. I would guess this is by design actually, so resource blocks aren't unnecessarily tied up by a high priority UE (the MB). Sent from my Pixel 2 XL using Tapatalk
  18. It isn't possible. 600 megabits is about the limit of 802.11ac in my experience. Sent from my Pixel 2 XL using Tapatalk
  19. Does it show neighbor cells from different bands? Or does it still show them as unknown? Sent from my Pixel 2 XL using Tapatalk
  20. In Pittburgh, there was only a single B25 carrier that was 10x10 (expanded G block, earfcn 8640 like in your screenshots). They recently added a contiguous 5x5 carrier just before the 10x10 carrier, and on sites where they did that, they changed the 10x10 carrier GCI endings like in your screenshot and put the new 5x5 carrier in the 00, 01, 02 slots. So my guess is your market recently got a new 5x5 carrier, and they changed the GCI endings for the existing 10x10 so that it appears as the second carrier now. Sent from my Pixel 2 XL using Tapatalk
  21. San Jose has had their GCIs revamped. A majority of sites no longer are using the hex 1450 offset between bands 25 & 26 and band 41. All 3 bands are using the same GCI base, with different endings. The old endings no longer can be used to determine the band. I saw at least one site with an "02" ending for band 41. My data is from a drive from SF to Santa Cruz, then Santa Cruz to Oakland. So I don't have all 3 sectors and all 3 bands from a single site. From the data that I do have, there doesn't seem to be a consistent pattern to the GCI endings. It is very possible though that there is a pattern (or multiple patterns limited to certain geographic areas). From my logs, I've found the following endings: B26: 02 10 0F 14 B25 (earfcn): 00 8665 01 8665 02 8665 04 8115 05 8115 09 8665 0A 8115 12 8665 13 8115 B41 (earfcn): 03 40978 04 40072 04 40978 05 40072 05 40978 06 39874 06 41374 07 39874 08 41374 0B 41176 0C 40270 0D 40270 0E 40270 Or grouped by earfcn: B25: 04 8115 05 8115 0A 8115 13 8115 00 8665 01 8665 02 8665 09 8665 12 8665 B41: 06 39874 07 39874 04 40072 05 40072 0C 40270 0D 40270 0E 40270 03 40978 04 40978 05 40978 0B 41176 06 41374 08 41374
  22. ingenium

    Google voice integration going away June 1st

    If you have Tasker, I have a profile setup that I can share with you to block calls on Hangouts and CDMA from spoofed phone numbers that aren't in my address book. Just triggers a notification saying it was blocked. I can export it as a standalone apk too if you let me know your area code and exchange. I get several spoofed spam calls a day. Sent from my Pixel 2 XL using Tapatalk
  23. ingenium

    Google voice integration going away June 1st

    Using Google Voice separately (voicemail integration with Sprint, so conditional call forwarding which will continue to work), MMS has worked for a while. At least using Hangouts. My issue with it for calls is that if I'm in an area with congested data, then calls are flakey. Sent from my Pixel 2 XL using Tapatalk
  24. Third carrier on triband sites (that use triband endings) has second carrier GCI endings. So: Non-triband: 2nd carrier - 03, 04, 05 3rd carrier - 06, 07, 08 Triband: 2nd carrier - 09, 0A, 0B 3rd carrier - 03, 04, 05 I define second carrier as the middle earfcn, and third carrier as the highest earfcn. Sent from my Pixel 2 XL using Tapatalk
  25. ingenium

    Official Airave 3 LTE / S1000 NSC Thread

    Mine has been doing that all week. GPS also goes red on the LTE side but not the CDMA side. Sent from my Pixel 2 XL using Tapatalk
×