With BAIlogger configurable events (SMS, MMS, Calls, WIFI, Bluetooth, NFC, External power, Docking station, USB devices, USB debugging, Application manager, ...) can be logged automatically. All data is stored just in a local database (no broadcasts in a cloud etc.). If available also the current geoposition will be stored for each event. So it is for example possible to check at any time when and where you received a particular call. For this purpose, you can either simply display just the corresponding address or the location in a map.
Furthermore, you can configure whether at all and/or after how many days old protocol entries should be deleted automatically. Similarly, the execution of this app can be protected by a password and a fingerprint (basic protection against unwanted execution, but this does not lead to an encrypted database). The app (monitoring the events to be logged) can be started automatically during system startup or manually.
To activate/deactivate Bluetooth, a multi-click of the Power button can be configured. And it is also possible to define a timeout for Bluetooth. If within the specified period no Bluetooth connection is established, the Bluetooth service is automatically deactivated again.
If the used Android device does not support notification reminders, this can be done by BAIlogger. In the app settings you can define a period after which you will be reminded about open notifications (with an audio alarm) by playing this alarm again.
You can also define additional actions which will be executed if the used device will be connected/disconnected to a power supply or to a computer.
The list of logged events can be filtered by event types (SMS, MMS, Call, Bluetooth, Mobile data, ...) and/or by entries with or without geopositions. Whether a geoposition exists for a specific event can be recognized by a place marker icon for this event. By supporting the FastScroll property also huge lists can be quickly and easily scrolled through.
Widgets are provided to switch on/off WIFI, Location services, NFC, Bluetooth and/or Mobile data.
Additional features will follow ....
To be able to monitor the different events BAIlogger requires many permissions (even if a user does not use individual functions). We guarantee that these permissions are only used for the purposes described here and all data is stored only localy. In case that you distrust you can revoke individual permissions after installation (e.g. using XPrivacy).
This app requires at least Android 4 and is available as BAIlogger and also in a free, limited version as BAIloggerFree.
Start at boot time
Specifies whether BAIlogger will be automatically started during system startup. If this is disabled the app must be started manually after every reboot, otherwise no events will be logged.
Specifies whether BAIlogger will get root permissions. This is for example required to toggle NFC or Mobile Data directy (without any additional user interaction).
Disable NFC at boot time
Specifies whether whether NFC should automatically be disabled at boot time.
Show toggle buttons
Specifies whether toggle buttons to en-/disable Bluetooth, GPS, mobile data, NFC and WIFI should be shown. The corresponding button will also indicate the actual state.
Protocol font size
Specifies the font size of the protocol list entries.
Specifies the time (in minutes) after which you will be reminded about any open notification (with an audio alarm). After the time has expired the audio alarm will be played again and the period will restart again...
Indicates the max. count of days how long logged events will be stored. Events that are older than the specified period will be automatically deleted. If this parameter is set to 0 then the messages are never deleted automatically.
Here you can configure whether enabling the installation from 'Unknown sources' should be disabled again after the an installation has been completed or after a timeout has been expired.
This feature will be activated by specifying a timeout (in seconds) greater the 0 seconds. If this feature is enable, you will be prompted to turn it off again after the next installation/update of an app or after the specified timeout has been expired.
Here you can configure whether the Bluetooth service will be started/stopped by pressing the power button multiple times. If Click count is set to 0, this option is disabled. The parameter Click delay is used to configure the max. delay between two successive clicks.
The recognition of a multi click (and turning the Bluetooth service on/off) will be indicated by a vibration.
Using the parameter Timeout a period can be defined, after which the Bluetooth service is switched off again in the case that within this period no connection to a paired device has been established. If Timeout is specified as 0 the timeout is disabled.
This defines whether the Location services should be used at all (whether a geoposition should be stored with the logged events). The parameters Min. time interval and Min. distance can be used to configure the update frequency of the geoposition data. Lower values for this parameters will result in a better accuracy but will also require more energy. The default values should be a good compromise.
If no events to be logged occur over a longer period it is clear that also no geopositions will be stored. For such cases you can configure an Auto timer. This one will log empty pseudo events, if within the specified period no event occurs but geopositions are available.
Using the parameter Maps URL you can optionally specify an URL (Google Maps, OpenStreetMap, ...) to be used to show a geoposition. After a longer touch on a log entry (with geoposition) a menu is displayed, on which you can let show the corresponding geoposition in a map. For this the URL provided here will be used.
Here you can configure whether further actions should be executed when connecting/disconnecting the device with a computer or a power adapter.
It is possible to turn Bluetooth on/off (after connecting/disconnecting the device with an external power supply or a computer). If this option is selected then Bluetooth will be enabled for a short period (for 60 or (if defined) Timeout seconds) after a USB connection has been established. If no already paired device does connect within this period Bluetooth will be disabled again. Otherwise Bluetooth remains switched on until all connections were stopped. If the USB connection still exists at this time the timeout does start again.
Additionaly it is possible to automatically display the Developer options (only when connected/disconnected to a computer). The Developer options can be used to enable/disable USB debugging, what could be required for a computer connection, but should not be permanently turned on.
Here you can configure which events should be monitored and logged.
Execution of BAIlogger (viewing the log list, changing the settings) can be protected by specifying a password. Specifying a password will not result in a encrypted database. If a password is defined, it must be entered on each start of this app will be started (also if 'Start at boot time' is defined). By pressing the Back or Home button the app does not exit but will just be moved to the background. The password will only be polled again if the app was left using the 'Exit' menu.If a password has been set and corresponding hardware is available (min. Android 6.x), a fingerprint authentication is also possible.
BAIbreaker is a simple, amusing and stressless game with which we have tested the cross-platform programming for different mobile operating system some time ago.
The playing field consists of an array of balls in 5 different colors. By clicking two or more same colored and ajacent balls they are first selected and then removed from the matrix. The more balls at once are removed the more points (n * (n - 1)) the player gets credited. The aim of the game is to remove a maximum number of balls (all) and/or to collect as many points as possible (the time required does not matter). The count of balls (both horizontally and vertically) can be configured. The size of the balls is adjusted according to the defined number of balls. You can configure up to 4 different players, with an own game statistic for each one.
This app requires NO permissions and so it can't access any private data and can't submit any data.
With ttySendXMS you can use your Android device as a GSM modem with SendXMS. For many Android devices there are no drivers available to use the device as a GSM modem. If you install ttySendXMS on the Android device you can configure this device in SendXMS as a GSM modem with AtOverEthernet for sending and receiving SMS.
In the device definition in sendxms.cfg you should define your Android device like:
[Device] DeviceType=GSM 07.05 AtOverEthernet=TCP Address=127.0.0.1 18016 Reset=ATZ Init=ATQ0E1V1 S18=1234 Escape= Hangup=ATH
If you connect the device via USB ( as in the above example) you can forward the used TCP port (from the used computer to the Android device) using the command 'adb forward tcp:18016 tcp:18016'.
Preconditions for using ttySendXMS are an Android 4 device, the installation of the Xposed Frameworks (Xposed Installer) and because of that also root access. After the installation you have to activate ttySendXMS in Xposed as a module.
To install an app please select - if avaliable and with an active internet connection - and follow the given instructions.
In case that the requested app is not available on Google play you first have to enable 'installation from Unknown sources' on your Android device (and please turn it off again after the installation). Depending on the used Android version you will find this option in the setup menu (eg. under Settings - General - Security). After enabeling the installation from unknown sources you can simply download the app directly to your device or you install the .apk file using a computer with a command like 'adb install <app>.apk'.
Feedback and/or constructive suggestions/reviews will be gratefully received.