Jump to content

SVDO and ESMR 800


koiulpoi

Recommended Posts

So, I have a question for those who know more than I do.

 

If a device has SVLTE, will it be able to connect to 1X on ESMR 800 simultaneously with LTE on PCS G-Block 1900?

 

If a device has SVDO, will it be able to connect to 1X on ESMR 800 simultaneously with EV-DO on PCS 1900?

 

Lastly, if a device lacks SVDO, will it be able to connect to 1X on ESMR 800 simultaneously with EV-DO on PCS 1900? If not, and in an area without LTE but with 800 (could happen due to coverage gaps or lack of full builds), will such devices be stuck on 1X for data if not fully on PCS?

 

I ask because, using a certain engineered PRL by a certain Digiblur, using my Note II (no SVDO, yes SVLTE), I was able to (seemingly) do 1X 800+LTE 1900, but not 1X 800+EV-DO 1900, and I'm curious about what the average customer experience will be.

Link to comment
Share on other sites

Yes, the answer basically to all of the above is yes.

 

Remember that, when VZW first deployed EV-DO, it did so exclusively as EV-DO 1900. Yet, much of its network is/was CDMA1X 850. And that was long before any SVDO devices became widely available. But devices had no problem operating on VZW's dual band CDMA1X 850 + EV-DO 1900 network.

 

AJ

  • Like 1
Link to comment
Share on other sites

So, I have a question for those who know more than I do.

 

If a device has SVLTE, will it be able to connect to 1X on ESMR 800 simultaneously with LTE on PCS G-Block 1900?

 

If a device has SVDO, will it be able to connect to 1X on ESMR 800 simultaneously with EV-DO on PCS 1900?

 

Lastly, if a device lacks SVDO, will it be able to connect to 1X on ESMR 800 simultaneously with EV-DO on PCS 1900? If not, and in an area without LTE but with 800 (could happen due to coverage gaps or lack of full builds), will such devices be stuck on 1X for data if not fully on PCS?

 

I ask because, using a certain engineered PRL by a certain Digiblur, using my Note II (no SVDO, yes SVLTE), I was able to (seemingly) do 1X 800+LTE 1900, but not 1X 800+EV-DO 1900, and I'm curious about what the average customer experience will be.

 

The answer to all your questions should be yes. You cannot run data on both EVDO and LTE at the same time. Your phone will not ever be connected to both EVDO and LTE simultaneously. However, it will still monitor EVDO when connected to LTE. That way it can reconnect and handoff quickly and easily when needed.

 

I have had a CDMA 800 and EVDO connection before.

 

Robert via Nexus 7 with Tapatalk HD

  • Like 1
Link to comment
Share on other sites

I don't believe the band has anything do with it. It's all about the technology used. EVDO and 1X share the same transmission path.

 

To quote AJ's article:

 

Besides the incorporation of GSM/GPRS/EDGE 850/1900 and W-CDMA/HSPA 1900 capabilities, the most notable feature of the Note 2 is the lack of SVDO capability. That absence appears to be related to the inclusion of W-CDMA/HSPA, which coexists on a transmit path with LTE. In typical SVDO capable handsets, CDMA1X/EV-DO has one transmit path, but EV-DO has a second possible transmit path that it shares with LTE. That is not the case with the Note 2, as can be seen in the antenna locations and simultaneous transmission paths diagrams:

 

http://s4gru.com/index.php?/blog/1/entry-327-samsung-galaxy-note-2-big-enough-for-everything-except-svdo/

  • Like 1
Link to comment
Share on other sites

I don't believe the band has anything do with it. It's all about the technology used. EVDO and 1X share the same transmission path.

 

And what you will see on non SVDO devices is a bounce back and forth between CDMA1X and EV-DO every few seconds. On most networks, CDMA1X is configured for a slot cycle index 2, which equates to a sleep/wake cycle every 5.12 seconds. The idle device will sleep, then wake every 5.12 seconds, and that is why the engineering screen will update your RSSI and Ec/Io every 5.12 seconds. While the CDMA1X side is asleep the EV-DO side will wake, and I cannot recall if I am thinking of my EVO 4G or my Samsung A900 flip phone, but some CDMA1X engineering screens will show the periodic flip between CDMA1X and EV-DO carrier channels.

 

AJ

  • Like 1
Link to comment
Share on other sites

 

And what you will see on non SVDO devices is a bounce back and forth between CDMA1X and EV-DO every few seconds. On most networks, CDMA1X is configured for a slot cycle index 2, which equates to a sleep/wake cycle every 5.12 seconds. The idle device will sleep, then wake every 5.12 seconds, and that is why the engineering screen will update your RSSI and Ec/Io every 5.12 seconds. While the CDMA1X side is asleep the EV-DO side will wake, and I cannot recall if I am thinking of my EVO 4G or my Samsung A900 flip phone, but some CDMA1X engineering screens will show the periodic flip between CDMA1X and EV-DO carrier channels.

 

AJ

 

Every so many minutes I watch my iPhone switch back to 1x then back to 3G. Pretty seamless and doesn't affect my data that I never notice it.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

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

    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 
    • One more SCP beta rolling out.. includes more bugfixes and minor improvements. Pending any major issues with this version, it will be released to the public within a few days. Thanks for all the help and feedback!
    • Passed by the former Sprint site at 1184 60th St in Brooklyn last week and noticed T-Mobile took down all of the Sprint equipment but it looked like they installed some new cabinets so conversion is likely in progress.
  • Recently Browsing

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