Rooted devices
Help - I received this error when launching Compassly
Why you get this message
We run a security check every time you launch the Compassly app on a mobile device, to make sure that it is secure and can run Compassly safely.
If the app detects that your device is not secure, it will not let you proceed in case your account or other important information is endangered.
How come I’m only seeing it now? I’ve had this device for ages
Seeing this error might come as a surprise and it may be the first time that you have seen this message despite running lots of other apps on your device. Most apps do not run this level of security check on a device, so it isn’t unusual for you to first see it when attempting to open Compassly.
This is relatively rare - we have thousands of Compassly users, but only a few dozen have hit this issue. However, in all cases where users have raised this warning to us, it has led to them either increasing the security of their devices (e.g. disabling developer mode) or changing to a more secure device.
Why is this an issue?
When the security mode is lower on a mobile device, it can allow malicious software to run in the background that can bypass the defences that mobile devices normally have.
For example, “keylogger” software may be able to capture everything you type on the device keyboard. This means your username and password can be easily captured and used by someone else.
Your Android or iOS devices have security controls that stop that happening and mobile devices are normally very secure, but these can’t protect you if the security controls have been disabled.
What is the cause?
There are three main reasons why you might get this message:
- Your device is in Developer mode
- Your device is not recognised as secure
- Your device has been “Rooted” or “Jailbroken”
Unfortunately it isn’t possible to automatically know which of these reasons may have triggered the message, so it can only be figured out by working through the possible options. However, the most common scenario is that the device is in Developer mode - the others are less likely and harder to fix.
What can I do to fix it?
Try to turn off Developer Mode
If you have a fairly standard device (Pixel, Samsung, OnePlus) then the most likely cause is that your device is running in Developer Mode.
How this looks and the way to turn this off can vary by device, but we have illustrated it here on a Google Pixel 5:
Under the Settings menu on your phone, you should see a Systems option. Towards the bottom, you may see “Developer options”, and then under that there should be a simple option to turn off Developer options.
If you do not see “Developer options” then your device is unlikely to have developer mode on.
Check if your device is one that is not recognised as secure
Some devices are able to run Android but are not generally recognised as secure because of how the manufacturer has setup Android (this does not affect iPhones or iPads).
This will not be the case with the mainstream phone brands (Pixel, Samsung, OnePlus) but can happen with some of the Chinese brands - in particular Huawei, but potentially Xiaomi too.
There is wider context to this, including concerns about these manufacturers not being used as part of UK infrastructure.
https://www.ncsc.gov.uk/information/huawei-advice-what-you-need-to-know
https://www.gov.uk/government/news/huawei-legal-notices-issued
Compassly is not supported on such devices.
Jailbroken or rooted devices
This is where a device is effectively hacked to run in a way that is outside the control of how the manufacturer of the operating system (Google and Apple) intended it to work. There are some reasons for doing this, for example to allow very niche software to run, but it is very rare.
It is not easy to do this to a device, so you should know if you’ve done this to your device. It could be possible that you have bought a second-hand device that was previously jailbroken or rooted.
Fixing a jailbroken or rooted device is not easy or may not be possible - the device is no longer covered under the manufacturer’s warranty and they are under no obligation to help you fix it.
I still can’t fix it
You can still run the web application - but we would not recommend it
If you are not able to install the app, you can still run Compassly without installing the app - go to:
We do not recommend running Compassly if your device is not secure.
The issues that Compassly detected will still be present, and you may be compromising your and others security by using Compassly this way. This option is only really appropriate if you have a legitimate reason for running the device in developer mode.
Note that Compassly detects the issue, but this isn’t a specific Compassly issue
It’s important to emphasise that Compassly is using an industry-standard set of security tools to identify how secure your device is. This is not a specific issue with Compassly or the fact that it is not compatible with your device - Compassly has wide-ranging mobile device compatibility.
Instead it’s the fact that your device has been detected as not secure and therefore it is sensible and safer for Compassly not to run on it.
If your device triggers a warning in these tools, it is likely to be a wider indication of a less secure setup that you may want to resolve more generally.
We cannot offer direct technical support
Ensuring a mobile device is secure is beyond the scope of technical support we are able to offer - in many cases there will not be much we can do to support anyway.
You are welcome to Contact us to ask further questions, but please be aware that any support will be on a best-endeavours basis.
Further background information
What is developer mode?
Mobile devices are designed to be controlled and secure digital devices - it’s part of the reason you very rarely hear about mobile phones being hit by viruses, getting hacked or suffering from malware. But these controls also restrict some of the features that software developers often need to help develop their software, and therefore they can be disabled by putting the device into “Developer mode”. This makes the device more useful for software developers, but it also makes it more vulnerable to malicious attacks.
You normally need to do something quite deliberate to put your phone into developer mode, but it may have been done for you by a technical support team, friend or colleague.
Why might your device not be recognised as secure?
Some mobile devices come with a less secure operating system by default, or are just not recognised as secure by the third-party tools that detect how secure the environment is.
What is rooting and jailbreaking?
Rooting and jailbreaking are processes used to gain more control over your mobile devices, such as smartphones and tablets.
Rooting is a term used for Android devices, while jailbreaking refers to Apple devices (iPhones, iPads). Both processes allow you to access and modify parts of the device's software that are usually restricted by the manufacturer. This lets you customise your device, remove unwanted apps, and install new features that might not be available through official channels.
Think of it like having a key to a locked door in your house. Rooting and jailbreaking give you that key, so you can explore and change things in your device that were previously off-limits.
However, there are risks involved. By unlocking your device, you could potentially make it less secure, as it becomes more vulnerable to malware or hacking. Additionally, rooting or jailbreaking might void your device's warranty, meaning the manufacturer won't provide support if you encounter problems.
In summary, rooting and jailbreaking give you more control over your mobile device, but they also come with potential risks and consequences.