FAQ Android Overview
Device specific requirements
Some manufacturers and models have device-specific settings. These settings must be made to ensure that the Kisi App works correctly! Please click on one of the following manufacturer links to learn more. Depending on the model and Android version, names (menu items) may vary.
Checklist: App does not work (anymore)
If the Kisi App does not comply with time limits correctly or does not work as expected, the following checklist will help you to find the problem:
1.) Please take the child device yourself and start the Kisi App. Is the counted time for today displayed correctly? (screenshot). It is important that you check this yourself (i.e. in person!) on the children's device to rule out possible manipulation or malfunctions.
2.) Check directly on the children's device whether the date and time are set correctly. A correct date is required for the Kisi App to function correctly. In case of manipulation you should lock the settings and activate the manipulation protection (see chapter settings). Also check on the device whether there is enough free memory available. On many devices there is also an item "Device maintenance" under the app settings, which can delete unnecessary files. If there is very little memory (less than 500 MB) left on the device, delete individual apps. The entire Android system always needs some free memory to work properly.
3.) Check the child device for active battery saving programs. Recently, the battery saving programs have been one of the main reasons for "dropouts" of the Kisi app. Manufacturers of cell phones and tablets are increasingly delivering radical battery saving programs with factory settings. You must ensure that the Kisi App is excluded from these battery saving programs. The settings for this vary slightly from device to device. Most of the time you will find a list of apps under the menu item Battery and there you can also specify that an app may always run in standby mode or you can assign special settings to it. In the following you will find links to some manufacturer-specific adjustments: Blackview, Huawei/Honor, Motorola, Nokia, Samsung, Ulefon, Wiko, Xiaomi
4.) Check if the synchronization from the Web Portal works. To do this, call up the Web Portal and block any app (select app under Apps and set to Blocked). Is this lock implemented on the child device after 2-3 minutes? Check whether the device also reacts correctly to a short test limit. To do this, set a short daily limit in the Web Portal under Total Limit and check the display directly on the child device after a sync. Is the remaining time displayed correctly? (screenshot). If this does not work, please uninstall the app and then reload it from PlayStore. For how to save existing settings, please refer to the Uninstallation chapter.
5.) Finally, restart the device and check if locked apps are actually still locked and the total time in the app is correctly increased every minute. This is the only way to make sure that a battery saving program from 3.) does not block the app again.
If the app used to work correctly and now suddenly doesn't work anymore, uninstalling and reinstalling it from PlayStore may help. In this case, however, it is important that the app is uninstalled correctly before reinstalling. Please refer to the Uninstallation chapter for instructions. chapter (where you can also learn how to save your settings).
Our customer service is of course available to answer any further questions you may have. When contacting us, please specify the child device (model/manufacturer) and the Android version you are using.
Time counting wrong
There are several ways to count the times on Android. Android itself provides an interface, but it does not always provide correct data. For this reason we currently still rely on our own counting method: We check the current foreground app every 10 seconds. If this app is still the same as 10 seconds ago, we increase the app count by the mentioned 10 seconds.
In the following cases no time is counted:
- the screen of the app is switched off
- the device is on the lock screen
- an always allowed or bonus app with the option counter STOP is running
Counted too much time? The app also counts the time when the device is only (unlocked) on the home screen and there is no app currently in the foreground. There have also been individual cases where the notifications from an app have caused miscounts. If it only affects one specific app at a time, you could try to disable the notifications for that app.
Not enough time counted? In some cases, the parental control may count less time than the child actually spent on the device. Background information: On Android devices, Parental Control works as a service in the background, which runs independently of the currently selected app and counts the times. However (in contrast to Windows) the Android operating system itself can pause such services at any time. This can happen especially if another app is using a lot of memory or CPU load and the device is about to crash. This is often the case with very graphics-intensive games. Unfortunately there is no real antidote (except maybe using a more powerful device). By the way, the service is continued by Android itself as soon as the "critical" system state is no longer present (from this point on, the time is counted up). Against this background it is quite possible that a game is counted shorter than it actually ran.
Does the manual sync from the Web Portal not work? Does the phone no longer synchronize automatically? Is the date of the last sync "too old"? Check directly on the child device to see if the parental control app is still installed. Check if the device has an Internet connection and click on the "Manual Sync" button in the app:
Can a synchronization be triggered this way? If it works, check if there is enough memory left on the device and delete unneeded apps or other files if necessary. If nothing works, you can and should uninstall the app once and then reinstall it from PlayStore.
Starting with Android version 5.x it is possible to manage multiple users. However, this function is not supported by all device manufacturers. If you can and want to use multiple users on one device, please note the following instructions: The app must be installed and set up separately on each user account. When setting up the app, assign a meaningful device name such as "Samsung Max", "Samsung Paula" instead of just "Samsung Tablet". This makes it easier to distinguish the devices later in the Web Portal. In the Web Portal, individual users are treated like different devices. As with Windows Child Control, only one license is required per device.
Please note that Child Control blocks user switching by default. In the Web Portal under Settings -> Security Mobile Device, set the option Lock settings to "None" if you want to manage different users. If the app's mode of operation is bypassed by creating new users or the guest user, the following procedure very often (not on all devices) helps: Create a new user account for the child from the main account (often called "owner"). Then secure the main account with a password known only to you. From now on the child will use the newly created account (only the main/owner account has the right to create additional accounts). The user can be changed directly from the notification bar on some devices. However, you can usually disable this in the device settings. If you are about to buy a new smartphone, you can avoid the multi-user problem by choosing a manufacturer that does not offer user management. This is the case with almost all Samsung devices, for example.
No screenshots from Android 10?
Unfortunately, the use of the screenshot feature is no longer available starting with Android 10. The reason for this is the following: To get a screenshot from an Android device, the user's consent has always been required. Up to and including Android 9, a checkbox "do not ask any more" could be ticked during the approval process and thus the approval could be saved. Google has removed this checkbox from Android 10 on for security reasons. This means that every screenshot on the child device would be asked for permission from Android. Since this procedure does not make sense, we have deactivated the screenshot function in the web portal from Android 10 on.
Does the app always need internet?
Child Control settings can be made centrally via our Web Portal. But what happens if the child device does not have Internet? For example, if it was deactivated by the flight mode or if there is no WLAN? In this case all your previously set limits will be kept on the device. The app uses a database directly on the device, which is independent of an internet connection. Only changes made afterwards and the transfer of the usage logs to the web portal requires an Internet connection on the child device again. However, no data is lost: As soon as the child device is connected again, all data since the last time is transferred to the web portal and any changes to the limits are transferred from the web portal to the device.
If and when the last time data was exchanged between the device and the Web Portal can be seen directly in the Web Portal on the start page and under Sync -> Time last sync. In this context, please note the special case of daily e-mail reports: For example, the child cell phone is used for one hour until 17:00 today. From 17:00 on, child switches on the flight mode and plays for another hour afterwards. Then the cell phone is put away by the child. Because of the activated flight mode the web portal only knows the count until 17h. The e-mail report goes out the next morning and shows one hour. As soon as the cell phone has however again an Internet connection, the time after 17:00 is "added" and the times increase accordingly.
System time incorrect?
The Child Control app depends on the date and time as well as the time zone being set correctly on the child device. This is necessary to ensure that time limits function correctly and that lockout periods are observed. Manipulating the date is a popular trick for kids to circumvent the app. If Child Control detects a "wrong" system date or time, a corresponding warning message is displayed in the Web Portal.
If manipulation protection is activated (currently only available for Android), the child device is also completely locked and can only be unlocked again with the parent password. Even if changes to the date are 90% due to the kids: even bad batteries and defective hardware can in some cases lead to a malfunction of the system time.
On Android devices, the app protects against changing the system time when the user interface is activated. Unfortunately this protection does not work 100% on all devices. You can lock the settings to fix this problem. You can also activate the manipulation protection mentioned above: If a wrong date is detected by the app, the device is locked and can only be unlocked with your password. Attention! In this case no app is accessible anymore.
Remember that an incorrect system time can lead to strange reports, possibly even in the future (if the date has been presented). We recommend to reset times if the system date is wrong. Important! The message is not automatically hidden, even if the date may be correct again. This way you can recognize a manipulation even later. If the date on the child device is correct, you can hide the message with the "x" in the upper right corner.
Android device rights
In order to work properly, some access rights to the Android system are necessary. Normally you have already set these rights when installing the app. As soon as Child Control is installed, access to these system rights are protected with your password. Nevertheless, it can happen that an access right has been deactivated (consciously or unconsciously) again. In this case you will receive a warning message in the Web Portal. In this case, activate the required access right manually via the settings of the child phone or tablet. In detail, the following access rights are necessary:
Device administrator (Security -> Device administrators): When installing Child Control, you have specified that the app is entered as Android device administrator. This setting prevents the app from being easily uninstalled. We have implemented various security measures to ensure that the device administrator is not deactivated. In some cases, however, it is still possible that a child manages to disable this feature. If a clarifying conversation doesn't help (some parents sometimes switch to physical parental control in such a case), there is still the possibility to lock the settings on the device completely. To do so, log in to the Web Portal and select Settings -> Security -> "Settings all locked". If the settings are locked, the call to the device administrator will be blocked one level before. However, it is no longer possible to change WLANs, ringtones etc. when the settings are locked.
Accessibility services (Security -> User help or input help): These are necessary for the web filter in the chrome to work properly. The subsequent activation of operation/entry help differs from device to device. If the operating aids often deactivate themselves during operation, this is usually due to some activated battery saving options or other energy saving modes. Make sure in the settings of your device that no battery optimization is applied to Child Control.
Usage stats (Security -> Access usage stats): This setting is required so that Child Control can recognize and (temporarily) limit the titles and names of other apps.
Display over other apps: This right is needed to display the Child Control block screen over some other active apps.
Unfortunately, not all device manufacturers follow the names and positions in the settings described above. If you are not able to reactivate the corresponding access right yourself, the settings can always be (re-)activated by uninstalling and reinstalling the app. You may also contact us with your device data (manufacturer/model/android version). We will gladly help you to set the access rights manually.
If a locating of the device fails repeatedly although the mobile device is switched on and online, please check the different permissions for the standard query directly on the mobile device. The procedure for subsequent activation of the GPS function can be found in chapter GPS (Android).
If the location is permanently off by a few hundred meters to a few kilometers, the following procedure has helped other customers: Take the child's device and open there Settings -> Apps -> Child Control -> Permissions -> Location. Deactivate location permission for Child Control and then re-enable it again. Check if the location is more accurate then.
Token missing error
The error "400 - Token missing" during GPS tracking means that the mobile device could not yet successfully obtain an FCM (Google Firebase Messaging) ID number from the Google server. This ID is required by the app during a manual sync or a location query via GPS. Often the problem solves itself within 1-2 days. If not, you could try to uninstall and reinstall the app. If the problem still persists after that, check if the current Google PlayServices are installed and up to date.
Update required notification
Child Control is updated by us regularly, i.e. new versions are released in certain intervals. Here we correct errors or add new functions. It is important that the latest version is always installed on the children's devices. Normally you do not need to do anything else for this. If you have not disabled the updates in the Google PlayStore, the children's device will automatically perform the app updates. This works even if you have locked the PlayStore in Child Control.
Always allow certain apps
You can always allow certain apps in Child Control (even if the time has already expired). You can also specify apps where the total counter stops. It is also possible to set bonus times for certain desired apps (e.g. learning programs). The necessary settings for this can be found in the section Apps -> Allowed Plus.
Special case audio apps (e.g. Spotify)
Audio apps are a special case in terms of time counting, since the corresponding app does not necessarily have to be in the foreground. The audio control can also be operated via the Android notification bar or the lock screen. Unfortunately, it is not technically possible to detect this. If an audio playback is running and the device total limit (or a device block time) is reached, the audio playback stops. This can be manually restarted, but it should stop automatically after 10 seconds at the latest. Unfortunately, this only works with a total limit, not with an individual app limit of the music app. If you do not want the sound to stop when the limit expires, select the corresponding setting under Settings -> Android Options. A time limit of the actual audio app (as long as it is running in the background) is unfortunately not possible.