This release includes â/e/ on WayDroidâ. WayDroid is a new popular Anbox alternative and we have ported /e/ 10 to it, along with making a tool to manage it. So, in addition to the PWAs from the /e/ web store, you can now use Android or /e/ apps with native performance (unlike Anbox) from the /e/ store as well in Ubuntu Web. After installing the ISO, you can just launch the â/e/ on WayDroidâ app from the launcher and follow the steps. Youâll need a real machine (not a VM) for WayDroid to work.
Any issues with Ubuntu Web 20.04.2 not booting on some UEFI machines should now be fixed in 20.04.3.
Although Waydroid is quite stable now, occassional issues can be fixed by restarting it from the â/e/ on Waydroidâ tool available in the Ubuntu Web ISO. Note that since WayDroid doesnât support Nvidia for obvious reasons, if you have an Nvidia GPU, youâll either need to use the iGPU if your CPU has one or use software-rendering (which might make things slow). Also, WayDroid doesnât work on live sessions at the moment.
To install a wapp from the Open Web Store, download it to your system. Then search for âRun a fileâ in the application launcher, select the downloaded file and click âOKâ. After authentication, the app will be successfully installed.
/e/ Cloud Services integration out-of-the-box. In the near future, weâll be working towards tighter integration with the /e/ App Store.
Experimental Android app support out-of-the-box (using Anbox, with all of its parts re-packaged as DEBs). Note that Android App Support may not work properly in the LiveCD or a virtual machine, but should work fine in the installed system. Also, you might have to disable Secure Boot to get Anbox to work.
Ubuntu Web uses Wayland by default. Also, it uses Adapta as the GTK theme and Papirus as the icon theme.
Weâll constantly be pushing over-the-air updates for any bug-fixes or improvements, based on the feedback received.
I have an Asus flip c100p arm based chromebook. Please advise. Iâd also pay anyone to make a USB drive that could install this on my Asus flip c100p.
Hi @Branedy and @eric-standlee, your requirements look to be the same. Unfortunately, neither Ubuntu nor Armbian supports ARM Chromebooks, so this might have to wait a bit. Iâll be releasing a Raspberry Pi 4 variant first.
It is meant to be a privacy-focused, open source alternative to Chrome OS.
It booted to the login screen in 2 seconds - in a clean boot for me.
Thanks for this suggestion. Although wapps use Firefox at the moment, Iâll be pushing out an over-the-air update so that the browser is user-repleaceable.
The packages and source code are available in Launchpad, GitHub and Gitlab.
@wiertelus Sure, Iâll write a blog post, although you can find the necessary information in the wikis of the wadk repository in GitHub.
Honestly thereâs even no need of this as we can manually put such apps in normal ubuntu using gnome-web or chromium. And it works better than this as it opens them in dedicated window and not as new tabs.
Here are some of the issues:
Open in tabs. Seriously? Atleast have a dedicated window for each app.
What happens when someone uninstalls Firefox? System breaks? Or it works with any default browser?
Oh and also, GNOME isnât the best choice for a web based distro. Something light like lxqt or xfce would be better.
Honestly Rudra, no hard feelings but it would be better if you put your energy to improving whatâs already there(unity 8, other ubuntu flavours, etc) and not trying to invent stuff from skimmed versions of Ubuntu with different UIs.
I am seeing many of my ChromeBoxeâs and ChromeBookâs unfortunately getting chucked into the bin because there isnât an alternative that can be put on them due to their chip structure and ChromeOS is no longer letting them update. Thereâs a lot of pi stuff out there, if your gonna focus on a ChromeOS replacement - please make it work on my ASUS ChromeBox, Samsung ChromeBook, etc⊠those are the devices that will suck this up like honey.
And for the folks saying thereâs no need for this, I disagree whole heartily - a simple drop in install ChromeOS replacement for ChromeBoxâs and ChromeBookâs is very needed - lots of hardware is getting chucked thats still useful.
Please keep up the great work, and focus on your base - ChromeOS! Thanks for your work.
I totally think thereâs need for something like this. It is good stuff and Iâd love to see how this evolves, hopefully picks up community support and evolves into a full alternative.
Other folks point out that there are alternatives but I donât see how the existence of other options means that you shouldnât create another one in the first place. Iâve tried Neverware CloudReady without being able to pass from the boot screen, UbuntuWeb just boot up and run without effort.
Raman, these are not just shortcuts or web-links, but a format that Iâve proposed to package web-apps for the desktop. The wapps Iâve included in the ISO are just some examples, but it can be used to package offline web-apps too. The real potential of it will be realised once Iâve done a full integration with /e/ apps.
Hope you understand that Firefox does not support SSBs (site-specific-browsers) at the moment. Although I would not prefer Chromium-based browsers, based on the feedback received from the community, I might switch to Brave browser to give pure SSB experience.
Someone has already suggested making the browser user-configurable, and I totally agree and will be doing that.
I think many people on this thread have already answered your question. To add to that, we want to make Ubuntu Web Remix completely detached from Google, which is why we are working with /e/ as the main alternative to Google.
Iâd used XFCE and KDE (since itâs gotten lighter in the last few years) for Ubuntu Web before finally zeroing in on GNOME3. FYI Iâve stripped down GNOME3 completely and it gave me the same performance as the former DEs on a 2GB RAM VM. In fact, it boots to the login screen in just 2 seconds - in a clean boot for me, as has also been reported by many users.
Raman, Iâm sure youâve heard of Cub Linux. I was fascinated by the idea of it (like many others) even after it was discontinued. In fact, I even managed to find some old ISOs of it online. So, Iâm trying to work on that idea. But I understand if you donât like it. Obviously, I canât force you to like it, but I guess this is what is the beauty of Linux. You take what you like and ignore what you donât.
Firefox supports SSBs (isolated ones infact, ICE from peppermint does that)
Yeah I have heard of cub linux and even used it. It is nice to see the interest in bringing it back to life. But this webapp packaging with only a couple of bash scripts doesnât seem that good idea to me. Anyone can just mess with the scripts and install unwanted stuff. Many users donât like installing stuff from github using scripts for this very reason.
Also Cub linux was in the days when you couldnât add webapps using browsers. Now you can, so it kills the point of cub linux. One can just install a lightweight distro and use brave/chromium /gnome-web to install webapps and use it as a chromebook.
And about GNOME, no matter how much you clean it, it still is more resource hungry by design. This setup got a 700-800 MB idle usage on a fresh boot on hardware and thatâs not light. Lubuntu uses 400MB idle. thatâs what is light. You should really consider lxqt and xfce again.
Also, agreed. Take what you like and ignore what you donât. peace.
I donât agree there, @The_LoudSpeaker. FIrefoxâs own support of SSBâs is very experimental and buggy at the moment. I had initially used that and had seen the issues, which is why I had to remove it. Peppermint Ice is just a few lines of CSS hacks. You can easily find what they do for Firefox âSSBsâ in here, which is why I chose not to use it: https://github.com/peppermintos/ice/blob/master/usr/bin/ice-firefox
Iâm already running a Twitter poll to switch to Brave Broswer for now, since many people do not wish to wait for Mozilla to implement true SSB support in Firefox.
Most Windows people (since this project is not aimed at only the Linuxians) are unfamiliar with installing apps using package managers (even GUI ones). Even if we explain the security benefits, they usually continue downloading their usual MSI installers. We need to cater to that group of people as well. Also, eventually, we would be using â/e/ App Storeâ and things would be more streamlined.
Doesnât this apply to Chrome OS as well?
It is great that you have tested Ubuntu Web. In my testing on a 2GB RAM virtual machine, the RAM usage was about 600-700 MB and the virtual machine booted up in 2 seconds in a clean boot. To be honest, although GNOME wasnât my first choice, but besides decent performance, it also had an elegance which many would expect from a Chrome OS competitor. LXQT isnât really useable for the Windows guys (the trend of menu navigation is no longer modern), nor is it comparable to Chrome OS in my opinion. Although I personally like Lubuntu, Iâm not sure how comfortable Windows users would be with it.
Booted fine on a Panasonic Toughbook CF-52, 4GB w SSD - seemed a little sluggish starting, but in the end ran very well. I personally use a ChromeBOX as my work desktop, now that I can run Linux Apps - there is very little (maybe 1%) of things I cannot do on this ChromeBox - it supports dual monitors, and as we migrate to more web based/cloud based services and apps, I can manage it all on the Box. Having to dump them every 4 - 5 years when the hardware still works is a bit of a bummer - but reality. I have deployed 15 - 20 ChromeBoxs/Books in my environment - and the users love em. Quick to boot easy to use. Biggest downfall is printing since Google dumped cloud print. The main use for ChromeOS devices in my org is basic web browsing and remote desktop. Your distro would work perfect for that - and I could see installing this on the few Linux desktops I have installed in places where I want to hinder fiddlers. But at this point it seems to be a regular desktop/laptop OS replacement - not necessarily a ChromeOS replacement (maybe what the_loudspeaker is leaning toward, with way more detail than I would have as an end user). To be a ChromeOS replacement, needs to be installed on Chrome devices. Would love to see this project make it there. That being said after booting your distro on this tough book, adding xfreerdp was possible and ran great, would drop into my environment - if it worked on the Chromedevices I have. Great work, and thanks for your efforts. For me personally in my environment (as an end user non techy IT guy), as long as it runs and isnât a sluggish web browser - this looks and âfeelsâ great and covers all my bases - once I can install it on ChromeDevices. I get that devices should be replaced about every 5 years, but some of those older devices can be moved into less critical places (shop floors etcâŠ) and this would be great for that. Thanks again.
I think the PBP community would love to see something like chromeOS but privacy focused and not built on Chrome.