Jump to content

First dual mode (FD-LTE/TD-LTE) phone launched in Hong Kong

Thomas L.

Recommended Posts

This article is already a month old, but I never saw it posted here, and I thought it would interest people, as it shows how imperfect the technology still is that will be required for Sprint to integrate Clearwire's 2.6ghz TD-LTE into their handsets. The ZTE Grand Era runs on China Mobile's TD-LTE and FD-LTE ('regular' LTE) networks, but to switch between the two, you currently have to reboot the phone. It's also interesting to see the difference in performance between the FD-LTE and TD-LTE network.



Link to comment
Share on other sites

My buddy had an LG Revolution, one of Verizon's first LTE phones and it had to reboot when switching from EVDO to LTE. It was very annoying when he was checking to see if LTE was deployed in Lansing yet. The LTE on that phone was a battery killer, it was terrible. Almost as bad as the Wimax chipset on the OG Evo

Link to comment
Share on other sites

I doubt that the ZTE handset is a particularly relevant frame of reference. This is just speculation on my part, but I bet that FDD and TDD are on separate basebands and that at least one is not a Qualcomm chipset.




I actually thought about that after I posted it and did research about ZTE's LTE products - they don't produce a single dual-mode chip, just separate TDD and FDD LTE chipsets.. Hopefully that's the case!

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.

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

    • What devices should do, and what they actually do, are two very different things! As you've probably heard me mention countless times, many of those screens get information in a proprietary manner directly from the modem; apps like SignalCheck can only get what the OS is reporting. I did find your earlier reports, and as I guessed, the OS was reporting valid signal strength. I will try to figure out a solution.
    • Service mode shows the SIM as having no service, so I would think the device should report that. I believe I sent a diagnostic report a little while back—can you check to see if you have it?
    • Interesting, that doesn't happen on my P7. Can you send me a diagnostic report the next time you see that please? Hopefully the phone isn't actually reporting the -115, that will be tricky.
    • Hey Mike—another dual SIM bug. If one SIM loses service, it doesn’t disappear from the app.  I’ve seen this a couple times—my Dish SIM will lose service (confirmed in service mode), but SCP won’t stop displaying -115 or so. And it logs a data point at that signal every time the location updates.  Along the same lines, I have a custom trigger set up for 313340 (Dish), and the custom trigger keeps firing when this is happening. 
    • TLDR: not really 😂 With dual SIM, initially I was struggling to keep the info from each SIM separate but updating properly. I figured out how to get each to update without negatively impacting the other SIM's process.. which caused those processes to run on separate threads. On some devices (notably your e5 Play), the OS doesn't like the separate threads updating the UI. But it was only a very small subset of devices. And at first, the crash reports gave the correct crash reason but it was pointing to unrelated parts of the code. Once I cleaned up some other bugs, the crash reports pointed me directly to what I needed.
  • Recently Browsing

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