Project Fi - What Magic Hardware Allows Carrier Switching?


Question

Project Fi lists the Pixel, Nexus 5X and Nexus 6P as the only compatible phones with their auto network-switching system, and the FAQ and many reviews state that these phones have special radios:




These devices are the first smartphones that support our network of
networks. They work with the Project Fi SIM card, which supports
multiple cellular networks, and have a state-of-the-art cellular radio
tuned to work across network types.




However, in the iFixit teardowns they don't have any unique hardware. iFixit says that the Nexus devices use the Qualcomm WTR3925 LTE Transceiver, same as several other phones, while the Pixel uses WTR3925 as well as the Qualcomm WTR4905 LTE RF transceiver. All of these radios are used in several other phones, so why don't those devices support carrier aggregation?



I found this Qualcomm article from 2014 talking about carrier aggregation radios and they appear to be widespread:



https://www.qualcomm.com/news/releases/2014/09/10/qualcomm-extends-benefits-lte-and-carrier-aggregation-entry-level



Can the hardware be enabled in software in other devices?


Answer

FWIR, the Project Fi SIM contains the two separate carrier profiles (separate USIM applications with their own IMSIs that obtain the lease for one carrier or another) which are selected by some undisclosed means, as noted here (there is some theorization that this could be done by software on the baseband processor or possibly the SIM card itself, and as likely as not actually a combination of those things together with the Project Fi Tycho App.) The Active carrier USIM can be manually switched using proprietary dialer codes, but at the end of the day you have something in the form of software making a selection in the same way you might find on a dual SIM device (which is not a new concept).



The WTR3925 LTE Transciever is certainly key to being able to handle Carrier Aggregation but since the signal gets processed by the baseband and the actual selection of one carrier over another is being handled by software, it would be easy enough to assume that the unique thing about the Google Devices has more to do with proprietary code than anything else.



As far as enabling the ability to use a project fi sim in another device, it has been reported that while it will work with similar hardware profiles in terms of recognizing the SIM card, it still will only recognize the currently active carrier profile and as the specifics of the switching mechanism is not openly documented at the moment it would have to be switched manually or by attempting to implement a unique selection algorithm written to the spec of the PFi SIM.


Topics


2D Engines   3D Engines   9-Patch   Action Bars   Activities   ADB   Advertisements   Analytics   Animations   ANR   AOP   API   APK   APT   Architecture   Audio   Autocomplete   Background Processing   Backward Compatibility   Badges   Bar Codes   Benchmarking   Bitmaps   Bluetooth   Blur Effects   Bread Crumbs   BRMS   Browser Extensions   Build Systems   Bundles   Buttons   Caching   Camera   Canvas   Cards   Carousels   Changelog   Checkboxes   Cloud Storages   Color Analysis   Color Pickers   Colors   Comet/Push   Compass Sensors   Conferences   Content Providers   Continuous Integration   Crash Reports   Credit Cards   Credits   CSV   Curl/Flip   Data Binding   Data Generators   Data Structures   Database   Database Browsers   Date &   Debugging   Decompilers   Deep Links   Dependency Injections   Design   Design Patterns   Dex   Dialogs   Distributed Computing   Distribution Platforms   Download Managers   Drawables   Emoji   Emulators   EPUB   Equalizers &   Event Buses   Exception Handling   Face Recognition   Feedback &   File System   File/Directory   Fingerprint   Floating Action   Fonts   Forms   Fragments   FRP   FSM   Functional Programming   Gamepads   Games   Geocaching   Gestures   GIF   Glow Pad   Gradle Plugins   Graphics   Grid Views   Highlighting   HTML   HTTP Mocking   Icons   IDE   IDE Plugins   Image Croppers   Image Loaders   Image Pickers   Image Processing   Image Views   Instrumentation   Intents   Job Schedulers   JSON   Keyboard   Kotlin   Layouts   Library Demos   List View   List Views   Localization   Location   Lock Patterns   Logcat   Logging   Mails   Maps   Markdown   Mathematics   Maven Plugins   MBaaS   Media   Menus   Messaging   MIME   Mobile Web   Native Image   Navigation   NDK   Networking   NFC   NoSQL   Number Pickers   OAuth   Object Mocking   OCR Engines   OpenGL   ORM   Other Pickers   Parallax List   Parcelables   Particle Systems   Password Inputs   PDF   Permissions   Physics Engines   Platforms   Plugin Frameworks   Preferences   Progress Indicators   ProGuard   Properties   Protocol Buffer   Pull To   Purchases   Push/Pull   QR Codes   Quick Return   Radio Buttons   Range Bars   Ratings   Recycler Views   Resources   REST   Ripple Effects   RSS   Screenshots   Scripting   Scroll Views   SDK   Search Inputs   Security   Sensors   Services   Showcase Views   Signatures   Sliding Panels   Snackbars   SOAP   Social Networks   Spannable   Spinners   Splash Screens   SSH   Static Analysis   Status Bars   Styling   SVG   System   Tags   Task Managers   TDD &   Template Engines   Testing   Testing Tools   Text Formatting   Text Views   Text Watchers   Text-to   Toasts   Toolkits For   Tools   Tooltips   Trainings   TV   Twitter   Updaters   USB   User Stories   Utils   Validation   Video   View Adapters   View Pagers   Views   Watch Face   Wearable Data   Wearables   Weather   Web Tools   Web Views   WebRTC   WebSockets   Wheel Widgets   Wi-Fi   Widgets   Windows   Wizards   XML   XMPP   YAML   ZIP Codes