MagneFire

Apparently there is also https://github.com/mer-hybris/bluebinder that creates a virtual HCI devices and bridges data and events to the Android binder. This is available for Android bases 8 and up. We...

> > Apparently there is also https://github.com/mer-hybris/bluebinder that creates a virtual HCI devices and bridges data and events to the Android binder. This is available for Android bases 8 and...

> Any news regarding this issue? Nope, last time I checked the proposed idea of using `bluebinder` won't work since `mooneye` doesn't use the `/dev/hwbinder` interface. This means there's work...

We probably shouldn't close this just yet as the 'solution' hasn't been tested.

While it's definitely possible to have such a mode it requires changes to the kernel and launcher. Implementing this in a well structured way is the challenge here. I've attached...

Thanks for reporting this issue! We've seen this in the past on other watches as well. Which makes me think that we should implement an intermediate 'charging' phase to our...

`mmcblkop32` is the userdata partition. Without this you won't have a functioning AsteroidOS watch. The boot script just tries to mount the userdata partition using an `auto` type: https://github.com/AsteroidOS/meta-asteroid/blob/971762769951f621cfdc5682cb0b2af8232cbab3/recipes-core/initrdscripts/initramfs-scripts-android/init.sh#L83

This issue is worth an update since I also did some digging into this specific issue a while back. ## Background I think some background is needed since `swift` (Asus...

Can you try an do the real install again? It looks like this issue may be cause by probably two things: - Rootfs might be corrupted. Reflash asteroid-image-lenok.ext4 and check...

Can you clarify how you solved it?