-
@k.nacke I created a 1GB swapfile but Waydroid still did not work. I also installed Waydroid using Waydroid Helper. Will try to make a bigger swapfile. (approx. 4GB) Hopefully it works.
-
complains something about not finding device sensors.
I'll check as soon as I get my next kernel change working.
-
@k.nacke Ok will be waiting

Edit: Also there is no directory called binderfs in /dev which is needed for waydroid to work -
I just installed this and it works great except I have a crackling sound from the speakers and headphones when I'm listening to anything. The speakers were fine with android.
-
@neonmodder123 I can reproduce the hang, which is good.
I think there is no binderfs in the kernel 4.9 - simply too old for that. -
Latest build has the following updates:
- Now building Noble
- Waydroid working again
- Fixed some typos in the udev rules
Annoyingly, the missing letters seems to be worse on Noble. I did not yet find a way to fix that.
Have fun,
Kai -
@k.nacke You have Waydroid working on this low RAM device?
-
@MrT10001 Waydroid starts. I opened all pre-installed apps, took a selfie, install F-Droid via the browser, installed Fossify Gallery from there, and viewed the photo. At this level, it works.
I did not try any serious Android app. There was a notable delay between pressing the button in the camera app and the photo being taken. I did not run other UT apps parallel. It does not feel like a lot of fun (like Android on this device), but it runs. -
@k.nacke im buys these days but anyways im biack into this thing if you need anything for me to test i can do it
-
Happy New Year!
I hit the 1GB upload limit in GitLab, therefore there were no build for some time. The images in the
artifacts.zipfile are nowbzip2compressed, which brings me under the upload limit again. (I did not yet update the install instructions.)I made the following changes:
- I disabled a bunch of options which collects performance data and/or collect debug data
- The kernel is now built as optimized for performance, and tuned for Cortex A53
- I turned the met driver ("MediaTek Embedded Technology") into an option, and turned it of. The met driver collects data which requires mostly proprietary tools to read
- I fixed all warnings from the device tree compiler
I also spent a lot of time trying to get a 4.19 kernel to run. So far with no result - it boots but then crashes. The motivation here is that
systemdrequires at least a 4.15 kernel to support all features.Have fun,
Kai