Jump to content

Newest Sprint Zone


Ascertion

Recommended Posts

I just got the update. I went to the app and turned off auto-update, turned back on and then refreshed the app and it started downloading.

 

The app is much cleaner, smoother, and has a touch of Material Design. It also tells you data usage in gigabytes now. I love it!

  • Like 2
Link to comment
Share on other sites

Cool! That apk works in my Nexus 5! None of the previous ones installed successfully. The device diagnostics tool is pretty cool.

 

Unfortunately it says usage data is not supported in my device.

  • Like 1
Link to comment
Share on other sites

Cool! That apk works in my Nexus 5! None of the previous ones installed successfully. The device diagnostics tool is pretty cool.

 

Unfortunately it says usage data is not supported in my device.

I get the same thing on my Nexus 5 after side loading the apk.

Link to comment
Share on other sites

Hmm, it doesn't recognize my phone number and won't let me log in saying mdn is required as a parameter.

Interesting.  Did you have a working Sprint Zone apk on your Nexus before?  It may be the way Nexus authenticates with Sprint, since it's not an actual "Sprint" phone.

Link to comment
Share on other sites

It works with the Nexus 5 if you manually override your device and account info. You will need root.
Open this file:

/data/data/com.sprint.zone/shared_preferences/com.sprint.zone_preferences.xml

Add the following lines with the correct values:

<string name="funnyPref1">%NAI%</string>
<string name="funnyPref2">%MEID-HEX%</string>
<string name="funnyPref3">%RESELLER-ID%</string>
<string name="funnyPref4">%MSID%</string>
<string name="funnyPref5">%PRL-VERSION%</string>
<string name="funnyPref6">%MDN%</string>
<string name="funnyPref7">%MAKE%</string>
<string name="funnyPref8">%MODEL%</string>

Mine looked similar to this when I was done (real info masked):

<string name="funnyPref1">myname00@sprintpcs.com</string>
<string name="funnyPref2">0123456789ABCD</string>
<string name="funnyPref3">Sprint</string>
<string name="funnyPref4">5045551212</string>
<string name="funnyPref5">55021</string>
<string name="funnyPref6">5045551212</string>
<string name="funnyPref7">LG</string>
<string name="funnyPref8">Nexus 5</string>

I found about these settings last year by reverse-engineering an older version of the app when it didn't work out-of-the-box on my Nexus S. They seem to exist for debugging purposes and will override the (not) detected values.

  • Like 5
Link to comment
Share on other sites

It works with the Nexus 5 if you manually override your device and account info. You will need root.

Open this file:

/data/data/com.sprint.zone/shared_preferences/com.sprint.zone_preferences.xml

Add the following lines with the correct values:

<string name="funnyPref1">%NAI%</string>
<string name="funnyPref2">%MEID-HEX%</string>
<string name="funnyPref3">%RESELLER-ID%</string>
<string name="funnyPref4">%MSID%</string>
<string name="funnyPref5">%PRL-VERSION%</string>
<string name="funnyPref6">%MDN%</string>
<string name="funnyPref7">%MAKE%</string>
<string name="funnyPref8">%MODEL%</string>

Mine looked similar to this when I was done (real info masked):

<string name="funnyPref1">myname00@sprintpcs.com</string>
<string name="funnyPref2">0123456789ABCD</string>
<string name="funnyPref3">Sprint</string>
<string name="funnyPref4">5045551212</string>
<string name="funnyPref5">55021</string>
<string name="funnyPref6">5045551212</string>
<string name="funnyPref7">LG</string>
<string name="funnyPref8">Nexus 5</string>

I found about these settings last year by reverse-engineering an older version of the app when it didn't work out-of-the-box on my Nexus S. They seem to exist for debugging purposes and will override the (not) detected values.

 

Thanks! This did the trick! Also, as far as "funnyPref1" goes, each person will have to figure out their NAI, mine ended in 02 instead of 00. I used the Nexus 5 Field Test app, then Settings(view) --> Data Profile --> View.

  • Like 1
Link to comment
Share on other sites

Not working on my flagship (non spark) S4. Got a box that popped showing "Describe Error" and said "There was a problem parsing the package"

Link to comment
Share on other sites

Yup, the new update installed at 3:45 am this morning and gave me the Extra "Fun & Games" app on my Moto X. Tried opening the app but it does not work giving me an error to try later. Tried opening the Sprint Zone and same error message.

 

Uninstalled update and the "Fun & Games" went away. 

 

Disabled Sprint Zone, I really dislike bloatware.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well. 
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
    • Looks like a great place for for FWA. Many apartment dwellers only have one overpriced choice.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...