Apps deliberately refusing to work on modded devices: Difference between revisions

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{Cite web |last= |first=Vision |title=Apps&Games need PI |url=https://xdaforums.com/t/apps-games-need-pi-list.4677050/ |website=XDA Forum}}</ref>  

Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016-08-03}}</ref>: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.  

The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*remove all bloatware

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples<ref name=":0" />==

*Netflix

*Twitter/X

*Twilio Authy Authenticator<br />

[[Category:Common terms]]