-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I tried using Anbox Android emulation, but when I installed the modules using dkms using this github page, I couldn't start the binder module, and I got this output (I am copying this from syslog): Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_return' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_command' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unmap_kernel_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unmap_kernel_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unmap_user_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unmap_user_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_alloc_page_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_alloc_page_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_free_lru_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_free_lru_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_alloc_lru_end' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_alloc_lru_start' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_update_page_range' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_failed_buffer_release' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_buffer_release' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_alloc_buf' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_fd_recv' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_fd_send' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_ref_to_ref' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_ref_to_node' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_node_to_ref' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction_received' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_transaction' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_wait_for_work' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_read_done' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_write_done' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_ioctl_done' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_unlock' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_locked' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_lock' directory Jan 22 15:38:44 localhost kernel: Could not create tracefs 'binder_ioctl' directory Jan 22 15:38:44 localhost kernel: debugfs: Directory 'binder' with parent '/' already present! I then compiled my kernel with ashmem and anbox-binder support, but when I tried again, this time I didn't have the binder_linux module, as I built binder into the kernel. anbox-container-manager complained about it, when I tried starting it. Do I need to install the dkms anbox modules again after I built support for anbox-binder? Keep in mind that the only problem is with binder. Ashmem is there and is working all fine, having a proper module and everything. Installing the dkms module is most likely going to mess up ashmem. What should I do?