Jump to content

Android 4.3 Release date for sprint


z250kid

Recommended Posts

If history is any indication, at LEAST 4 months. And no one here knows. Here is a basic way to estimate. When it rolls out to the international version of the phone, add at least 2 months.

 

Sent from my SPH-L710 using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Guys just go on xda-developers website, why do you wait for the carrier to update the os?

Because, for example, the CM RILs for the Note II have been unable to properly authenticate with 4G LTE for some time.

 

Not only that, you lose access to the phone's engineering screens, as well as things like (on the Note II) the ability to write any PRL you want.

 

Custom roms are fun, but there are tradeoffs.

Link to comment
Share on other sites

Custom roms are fun, but there are tradeoffs.

 

To add to that, the obsession some have with the latest official Android release is borderline insanity.  Folks, Android 4.3 is not going to change your life.  And you are not deprived if you are still on Android 4.2.  So, as a suggestion, relax and do not worry about it.

 

AJ

  • Like 7
Link to comment
Share on other sites

To add to that, the obsession some have with the latest official Android release is borderline insanity. Folks, Android 4.3 is not going to change your life. And you are not deprived if you are still on Android 4.2. So, as a suggestion, relax and do not worry about it.

 

AJ

My life will finally have meaning when Android 4.3.1.2.1.43.2 rev b comes out!

 

Sent from my SPH-L900 using Tapatalk 2

 

 

  • Like 6
Link to comment
Share on other sites

Because, for example, the CM RILs for the Note II have been unable to properly authenticate with 4G LTE for some time.

 

Not only that, you lose access to the phone's engineering screens, as well as things like (on the Note II) the ability to write any PRL you want.

 

Custom roms are fun, but there are tradeoffs.

those are only issues if you go the aosp based rom route. There are plenty of other tw based roms that do not restrict those things. Plus CM will fix lte, it's only a matter of time. You can also have a backup of stock tw, flash it, flash your desired prl, then reflash aosp and you are good to go as far as prls go.

 

Sent from my SPH-L900 using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

To add to that, the obsession some have with the latest official Android release is borderline insanity.  Folks, Android 4.3 is not going to change your life.  And you are not deprived if you are still on Android 4.2.  So, as a suggestion, relax and do not worry about it.

 

AJ

Once upon a time Google made updates worth worrying about upgrading to. That was before android 4.0.

  • Like 1
Link to comment
Share on other sites

To add to that, the obsession some have with the latest official Android release is borderline insanity.  Folks, Android 4.3 is not going to change your life.  And you are not deprived if you are still on Android 4.2.  So, as a suggestion, relax and do not worry about it.

 

AJ

This. When my Nexus 4 finally got the OTA two days ago, I was so excited (if I wasn't busy I would have installed it manually sooner)... But once it was installed I quickly realized nothing had really changed.....

Link to comment
Share on other sites

those are only issues if you go the aosp based rom route. There are plenty of other tw based roms that do not restrict those things. Plus CM will fix lte, it's only a matter of time. You can also have a backup of stock tw, flash it, flash your desired prl, then reflash aosp and you are good to go as far as prls go.

 

Sent from my SPH-L900 using Tapatalk 4 Beta

Right, sure, I know all that... and how do you propose I "get Android 4.3" by "going to XDA developers" (you know, what the post I was replying to said) by sticking with TouchWiz? :P

 

Keeping a backup of stock isn't really an option, as it's a 5+ minute turnaround to switch roms and keep your data - not to mention you're still losing 4G. Being fixed "eventually" doesn't really make me want to use the rom "today", you know what I mean? And there's still no good replacement for engineering screens. SignalCheck Pro is getting close...

  • Like 1
Link to comment
Share on other sites

You can also have a backup of stock tw, flash it, flash your desired prl, then reflash aosp and you are good to go as far as prls go.

 

Some of you are so prone to flashing that you might have to register as sex offenders.

 

:P

 

AJ

  • Like 7
Link to comment
Share on other sites

Some of you are so prone to flashing that you might have to register as sex offenders.

 

:P

 

AJ

guilty as charged, ever since the tmobile g1 days. It allows me to have something new to tinker with without having to throw down the benjamins ;)

 

Sent from my SPH-L900 using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Because, for example, the CM RILs for the Note II have been unable to properly authenticate with 4G LTE for some time.

 

Not only that, you lose access to the phone's engineering screens, as well as things like (on the Note II) the ability to write any PRL you want.

 

Custom roms are fun, but there are tradeoffs.

This is actually do to Samsung RIL blobs they are using.  The older RIL blobs are available at xda and fix the issue (from a clean flash).  I just toss them into an CM zip i flash before I flash it.

Link to comment
Share on other sites

This is actually do to Samsung RIL blobs they are using.  The older RIL blobs are available at xda and fix the issue (from a clean flash).  I just toss them into an CM zip i flash before I flash it.

Link plz. I might try it out later. I will admit, I'm enjoying having engineering screens again.

 

I'm thinking of trying to restore "HiddenMenu.apk" to a CM-based ROM, and then using SignalCheck Pro to launch it, and see if it works. If so, engineering screens on AOSP!

Link to comment
Share on other sites

Link plz. I might try it out later. I will admit, I'm enjoying having engineering screens again.

 

I'm thinking of trying to restore "HiddenMenu.apk" to a CM-based ROM, and then using SignalCheck Pro to launch it, and see if it works. If so, engineering screens on AOSP!

 

I've been working with the maintainer on the HiddenMenu.apk for all kinds of stuff including the PRL updates, but no luck yet.

 

The RIL blobs are at http://forum.xda-developers.com/showpost.php?p=43625452&postcount=1239, if you have working LTE on AOSP, then replace these in the system\lib and fix the permissions, after a reboot you should keep LTE.  If you are on Stock, download a nightly, then edit the zip and put these in the build in system/lib.  I also toss the VVM.apk into system/app.  Then flash along with the gapps.

 

You should be golden :)

 

Scott has a pull request in to revert to these older blobs in the nightlies, but that is tied to a request for a new device and both will get processed together.

  • Like 1
Link to comment
Share on other sites

To add to that, the obsession some have with the latest official Android release is borderline insanity.  Folks, Android 4.3 is not going to change your life.  And you are not deprived if you are still on Android 4.2.  So, as a suggestion, relax and do not worry about it.

 

AJ

between the security upgrades and performance/battery improvements i'll be glad to get it on my nexus..:)

  • Like 1
Link to comment
Share on other sites

This is a great reason to upgrade to 4.3.

 

http://www.androidpolice.com/2013/07/25/app-ops-android-4-3s-hidden-app-permission-manager-control-permissions-for-individual-apps/

 

I leave the gps enabled globally.

I disabled the location access individually in many news app, makes it quicker to start the app and doesn't use the battery as much.

Link to comment
Share on other sites

After being plugged in over night, this morning I have seen a dramatic increase in speed for the Nexus7-2012.

Nice, hopefully another few nights, it will be fully useable again. The article mentions that it runs the trim once every 24 hours.

Link to comment
Share on other sites

What's wrong with the LTE on Cm?

On cm10.1, it has some type of issue that results in approx 60% of actual LTE output. What o mean is you'll get roughly 60% of the performance on LTE using cyanogen mod than you will on Touch wiz. I think it's related to the drivers that cm team patched for 4.2.2.

 

Sent from my SPH-L710 using Tapatalk 4 Beta

 

 

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 BRS/EBS 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.  — — — — — Edit: Turns out this is a spectrum swap where T-Mobile is basically giving them DoD spectrum in a bunch of markets in exchange for all of SoniqWave's BRS/EBS. SoniqWave will likely turn around and sell the DoD spectrum to AT&T whenever the FCC removes the 40MHz cap.
    • 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.
  • Recently Browsing

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