-
@CaptainTalon Thanks for trying. What did you do with waydroid? I could install it, and it started it (takes an eternity to come up though), but I only tried the web browser. I think the biggest problem is the limited memory of the device.
-
@k.nacke That will be the reason. 2Gb and less is not enough to run the system and Waydroid on any UT device.
-
@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.
