Someone compiled an x86 port of Valve's Lepton compatibility layer, its still a work in progress but is working for a few Android utility apps that I wanted on Linux.
I'd argue Lepton is potentially better than waydroid due to:
- podman containers, so no root required
- no awkward file permission issues
- per-app lepton containers are possible, for additional sandboxing
Its definitely still a WIP though, needs more refinement and improvements before I'd consider recommending it to regular nontechnical users.
Yeah, I'm surprised at how well its working for my handful of Android apps right now.
In my opinion, one of the biggest limitations right now is that it requires Steam as a dependency because it uses the same `Steam Play` compatibility infrastructure as Proton.
lepton shows up as another option in the compatibility tools dropdown in Steam, so you can use different versions of lepton for different apps too. So one day, we can maybe see something like Proton GE but for Android apps.
But it should be possible to eventually break that steam dependency, umu-launcher already does it for Proton-based gaming.
I certainly know that feeling:) But I do think there's a lot of value in another implementation, especially since you've already done some cool new things like the web version
did you try the ones in the demo or uploaded your own? (if you tried the demo one you can try refreshing once cuz apparently it fixed the issue in my friends browser)
but yeah its still very early to run our daily complex apps, demo only has fdroid ones that i tested to work somewhat
Vibe coded it last month because I got tired of dealing with AVDs for quickly testing Android app development on my Linux desktop. It's been working extremely well for my needs.
Interestingly I was looking at what options there are (long time waydroud, but its stalled).
Created a gist that has my table I did earlier in the week. I do quite like both droidloom and innkeeper (thanks for posting, I had missed it earlier).
What is the use case for this? Waydroid works rather well on Linux desktops, and on a cell phone you do want actual Android as it has considerably better power and app management than a Linux distro.
tbh i feel like there are was differences between these two, for one,
- winedroid is just a translation layer vs a contrainer
- also since this is fully written in rust it can be ran in browser easily, this is very impt cuz i love browser, and i want to just run my fav android apps like a website
- third is its just a fun to mess around and to see whats possible haha
Since it's a translation layer and not a container, could it run where the emulator can't? I timed the Android emulator on a CI server without hardware virtualization: 13.5 minutes to the first screen. Coding agents in cloud sandboxes have the same problem. Is running headless in a sandbox like that a goal, or is the browser the main target?
Linux phones having ready access to a large app repository. Developers won’t have to recompile to provide their service, users wont rue missing a google controlled phone. Maybe in future, we may have more choices.
Calculator wants me to upload a file? Files crashes on start for a pointer issue? And wine? I am a bit confused what this is. It is an emator, or compatibility layer? In a mobile browser the buttons are aligned properly so I can not open about (Vivaldi).
I have a bunch of apk files I've backed up over the years (humble bundle games, fdoid apk saves, exported ones from an older phone), but I couldn't get any of them to work.
> also thinking of rendering the back button (like we had in old days before the one small bottom bar)
This still exists in Android though it isn't the default. The first thing I do with any new Android phone is switch on "Buttons" instead of "Swipe gestures" in the OS Navigation bar settings.
For what it's worth, I think on real android, if you plug in a keyboard then the Escape key is equivalent to the back button. I'm not 100% sure of that, though.
Does anyone see if this properly implements security like apps being unable to read the filesystem without being granted permission? I didn't see security mentioned in the architecture documentation.
it doesnt actually do that well rn, infact the apps can read data of other apps as well, first i want to implemeent the most basic primitives then will add better sandboxing
freaky thing can see my whole phone !
opens the phone file system when tapping the 'not android' bat logo, and the apps I opened from there stay as cached processes when everything else is closed, browser cache cleared, but have to close everything manualy, so just like opening apps directly
Someone compiled an x86 port of Valve's Lepton compatibility layer, its still a work in progress but is working for a few Android utility apps that I wanted on Linux.
I'd argue Lepton is potentially better than waydroid due to:
- podman containers, so no root required
- no awkward file permission issues
- per-app lepton containers are possible, for additional sandboxing
Its definitely still a WIP though, needs more refinement and improvements before I'd consider recommending it to regular nontechnical users.
https://github.com/pjohno/lepton-x86_64
Oh, that's excellent; I thought lepton was just a slightly extended waydroid but that's notably different in a good way.
Yeah, I'm surprised at how well its working for my handful of Android apps right now.
In my opinion, one of the biggest limitations right now is that it requires Steam as a dependency because it uses the same `Steam Play` compatibility infrastructure as Proton.
lepton shows up as another option in the compatibility tools dropdown in Steam, so you can use different versions of lepton for different apps too. So one day, we can maybe see something like Proton GE but for Android apps.
But it should be possible to eventually break that steam dependency, umu-launcher already does it for Proton-based gaming.
https://github.com/Open-Wine-Components/umu-launcher
I've been running with Waydroid. Full compatibility so far!
Winedroid name would be more suited for a compatibility layer to run Windows programs on Android, not the other way around.
I agree, this is confusing. Also, "run apps without Android". Pretty much any OS can run applications.
Title on this thread and the website both read "run Android apps without Android".
Reality: all these names suck. It could be called Android compatibility wrapper for Linux, but that's too long.
I'd be interested in a comparison with waydroid and https://gitlab.com/android_translation_layer/android_transla... (which this seems to somewhat resemble in approach)
yes i found out about this after a huge chunk of winedroid was implemented, then wondered if i should just fork (but then chose to not do it)
I certainly know that feeling:) But I do think there's a lot of value in another implementation, especially since you've already done some cool new things like the web version
After clicking around the Weather app, I got this:
yup my friend had the same issue, can you see if refreshing once fixes it (cuz his was fixed)?
Still reproducible if you try to drag from left to right.
yup will fix, thanks for the finding
In Firefox Android it looks like lots of clicks and esp. swipes all trigger this error.
Couldn't launch a single app
'While executing DEX method dex file' etc etc
did you try the ones in the demo or uploaded your own? (if you tried the demo one you can try refreshing once cuz apparently it fixed the issue in my friends browser)
but yeah its still very early to run our daily complex apps, demo only has fdroid ones that i tested to work somewhat
not a single apk I tried worked with this.. every time some errors popped up but the app never loaded.
How's it compare to droidloom: https://github.com/denialwm/droidloom
Oh, another one! Now we need a 5 way comparison between
* droidloom
* Valve's lepton
* android_translation_layer
* waydroid
* winedroid
Here's another (mine): https://github.com/sargunv/innkeeper
Vibe coded it last month because I got tired of dealing with AVDs for quickly testing Android app development on my Linux desktop. It's been working extremely well for my needs.
Interestingly I was looking at what options there are (long time waydroud, but its stalled).
Created a gist that has my table I did earlier in the week. I do quite like both droidloom and innkeeper (thanks for posting, I had missed it earlier).
https://gist.github.com/mestadler/e4c53bbc3ddf03a4beecaac331...
What is the use case for this? Waydroid works rather well on Linux desktops, and on a cell phone you do want actual Android as it has considerably better power and app management than a Linux distro.
tbh i feel like there are was differences between these two, for one,
- winedroid is just a translation layer vs a contrainer
- also since this is fully written in rust it can be ran in browser easily, this is very impt cuz i love browser, and i want to just run my fav android apps like a website
- third is its just a fun to mess around and to see whats possible haha
Since it's a translation layer and not a container, could it run where the emulator can't? I timed the Android emulator on a CI server without hardware virtualization: 13.5 minutes to the first screen. Coding agents in cloud sandboxes have the same problem. Is running headless in a sandbox like that a goal, or is the browser the main target?
I would hope for it it to be lighter weight (don't need to install a full Android image), easier to sandbox well, and maybe faster
yup the current runtime is just 12 mbs, and it can already run a few apps thats crazy
faster is kinda hard cuz android is optimized by thousands of devs for decades atp, so itll be hard to beat it in perf, hopeful tho haha
> What is the use case for this?
Linux phones having ready access to a large app repository. Developers won’t have to recompile to provide their service, users wont rue missing a google controlled phone. Maybe in future, we may have more choices.
Calculator wants me to upload a file? Files crashes on start for a pointer issue? And wine? I am a bit confused what this is. It is an emator, or compatibility layer? In a mobile browser the buttons are aligned properly so I can not open about (Vivaldi).
I have a bunch of apk files I've backed up over the years (humble bundle games, fdoid apk saves, exported ones from an older phone), but I couldn't get any of them to work.
Seems like a neat project, though!
How does this work? Does it have NDK and Linux syscall support or only the Dalvik (Java) part?
I tried to run NewPipe apk but did not work :c
https://newpipe.net/
Ahh.. Then freetube (if it's about watching YT)
Reading the comments here the sentiment seems to be "IDK what it does or if it works but I'll upvote it"
How do you hit the back button? Like, the physical button / system soft button / edge gesture thing?
not added yet, gonna add it soon, im thinking two different ways:
* cmd + backspace will act as back * also thinking of rendering the back button (like we had in old days before the one small bottom bar)
> also thinking of rendering the back button (like we had in old days before the one small bottom bar)
This still exists in Android though it isn't the default. The first thing I do with any new Android phone is switch on "Buttons" instead of "Swipe gestures" in the OS Navigation bar settings.
For what it's worth, I think on real android, if you plug in a keyboard then the Escape key is equivalent to the back button. I'm not 100% sure of that, though.
The demo apps work, but what are the limitations? Will all apps work?
> Will all apps work?
No.
> Very early development. Some apps and workflows run; compatibility is limited. Expect missing APIs and broken apps.
thought this would be an interesting experiment, posting here if someone wanna check this out
I blame shit like this for why people think Androids have bad UI.
This is really cool.
Does anyone see if this properly implements security like apps being unable to read the filesystem without being granted permission? I didn't see security mentioned in the architecture documentation.
it doesnt actually do that well rn, infact the apps can read data of other apps as well, first i want to implemeent the most basic primitives then will add better sandboxing
freaky thing can see my whole phone ! opens the phone file system when tapping the 'not android' bat logo, and the apps I opened from there stay as cached processes when everything else is closed, browser cache cleared, but have to close everything manualy, so just like opening apps directly
> freaky thing can see my whole phone ! opens the phone file system when tapping the 'not android' bat logo
haha it's just input for apk file if you wanna try your apk so its opening your phones file selector
yes its not the best implementation cuz it's meant to be a tech demo than something thats usable practically