Android 13 virtualization lets Pixel 6 run Windows 11, Linux distributions
cnx-software.com
cnx-software.com
Booting, logging in, simple usage: https://twitter.com/kdrag0n/status/1493088558676017152
Playing Doom (via x86 emulation): https://twitter.com/kdrag0n/status/1493089098944237568
And Linux:
Booting various distros: https://twitter.com/kdrag0n/status/1492832966640222210
Compiling Linux 5.17-rc3 allnoconfig for arm64, on Arch: https://twitter.com/kdrag0n/status/1492833078410047488
I am also excited to see what booting multiple OSes means for the ecosystem around phh's (treble) builds, too.
Because I swear Does It Run Doom? is becoming a requirement checkbox for any new project.
Naturally I agree with you though. (Because we need DOOM running on more platforms~)
And I'd suggest Bad Apple also needs similar treatment.
https://www.theverge.com/2021/11/23/22798231/microsoft-qualc...
I honestly wonder if there's a monetary opportunity here?
(This used to read a little differently (https://i.imgur.com/yp95XxR.png - thought it would be funny) but it quickly became apparent some editing was in order. This comment will likely remain stuck at the bottom of this subthread... woops.)
I'm still working with Android 11 and compile times are driving me insane. The ritual to compile, pack and flash super.img into the device is absurd.
Do you know if there is any improvement on that side?
I don't feel like incremental AOSP builds are that slow, and I don't think it's changed much from Android 11 to 12. It's highly dependent on good hardware though, and it probably also helps that I flash individual partition images instead of building dist or target-files.
I typically only do a full flash for the first build after a sync. Afterwards I just build the pieces I'm changing and use `adb sync` to push them to the device, skipping both the step that packs the image files and the flash. The `sync` target will build just the pieces needed for an `adb sync` if you don't know exactly what you need to build; I typically use it so I don't have to even think about which pieces I'm changing when rebuilding.
So typical flow goes something like:
``` // Rebase is only needed if I have existing local changes > repo sync -j12 && repo rebase
// I don't actually use flashall, we have a tool internally that also handles bootloader upgrades, etc. > m -j && fastboot flashall
// Hack hack hack... then: > m -j sync && syncrestart ```
Where `syncrestart` is an alias for:
``` syncrestart () { adb remount && adb shell stop && sleep 3 && adb sync && adb shell start } ```
Incremental compiles while working on native code are ~10 seconds with this method. Working on framework Java code can be a couple minutes still because of the need to run metalava.
AFAIK, sync works on Linux only since it needs $ANDROID_PRODUCT_OUT. The problem is that I develop on a Windows machine (vscode with ssh extension) and my source code is on remote Linux machines (in premises), dedicated to building AOSP. Since I build at least for another 5 platforms, my working PC cannot cope with the current (and future) workload/space, so I asked to move all the source to dedicated hardware for building. Perhaps I can do it with ADB through Wifi...
I always thought sync worked with frameworks or packages, but since you mentioned "native" I guess it will also sync vendor stuff?
- LPC 2020: https://www.youtube.com/watch?v=54q6RzS9BpQ&t=10862s and https://lpc.events/event/7/contributions/780/
- KVM Forum 2020: https://mirrors.edge.kernel.org/pub/linux/kernel/people/will...
From the KVM Forum presentation: "We need a way to de-privilege third party code and provide a portable environment in which to isolate services from each other and also from the rest of Android."
From the LPC presentation:
"What do we need? We need a hypervisor that is:
1. open source
2. easy to ship and update
3. supports guest memory protection
4. trustworthy
KVM as part of GKI is a very good fit with the right extensions."
For productivity I don't want iron curtains between my applications or between application and system. Hell, it would actually be nice to be able to directly interface the hardware without all the loops.
We have a deeply flawed security model for mobile OS that relies on dogma that won't lead to additional safety. As safety issue is data exfiltration and by that standard a mobile devices are vastly more dangerous than the average work station. Comes with the nature of the device to a significant degree, but I think mobile OS have ridden of a cliff somewhere.
And now they want to push apps into a VM? Why not just buy a device per app at this point...
IMHO, it’s the fact that there’s a (basically, by default) a single market driven by (basically, by default) a single search engine to locate software. The desktop market, is largely NOT driven by a single market or search engine. With the “single market” if a malicious actor can game the search engine for even a day, they can install on (potentially) millions of devices. However, with the ‘ole distribution model, it’s much harder to game.
With scale comes new challenges and attack vectors.
This is most likely because people do not have to buy a PC every 3 years. Phones are treated as disposable items, whereas with a desktop, you can open it, clean it, change parts etc. I can even change the CPU in my laptop if I wanted to.
We can assume both as having reached steady state and that’s mostly replacement rate (not quite but almost).
Cell phones are more popular for obvious reasons: full access to internet at all times, TCO is drastically smaller across the board (upfront cheaper, cheaper internet, etc), and entire structures are built around them (many critical services go app first if not even app only).
I think you’re applying a very western bias in your analysis.
I think this may be a case of rose-colored glasses. How many PCs were and are a complete mess because Windows both is a free-for-all and is (or was) the largest attack target? Sure, we know how to keep our desktop systems sane, but most people don't.
Goggle's interests are aligned with the surveillance capitalists, Apple is either competitive (see Facebook) or ambivalent.
Apple can differentiate itself by trying to sell the security angle and hurting the surveillance of people in their app ecosystem doesn't hurt them. Comparatively, I would say Apple has a nontrivial advantage in security, though I wouldn't make a broad statement that iOS is "secure".
Or to compare against an ecosystem that has more love around here, imagine if everything that Apple runs on the T2 was instead run in a VM with an equivalent level of security. That's the goal.
What does this actually mean? Trustworthy under which circumstances, in what security model?
I'm terrified it means "unbreakable DRM in a way that is harder still for consumers to use or bypass" rather than "the code is not vulnerable to side-channel malware attacks". A lot of this could either be brilliant -- applications can't look at each other at all, unless one of a few trusted utilities such as screen-readers or keyboards, for example -- or utterly horrific from a user point of view. "Attestation" is mentioned in one of the end goals of that KVM Forum pdf, but it's unclear whether or not they mean a Qubes-like OS with the user as the hypervisor, or the user completely and utterly locked out of being the hypervisor, ever. One of these I think could be quite interesting -- especially without hardware attestation. One I think would be awful.
Part of the reason I (thoroughly break) Android's security model and run a rooted image is to have knowledge that I have control over everything in my device. It's important to me and I worry that these efforts will ultimately take that way from me.
Recently, they've also focused on using VMs to isolate parts of the system and apps: https://twitter.com/salt___doll/status/1492872311652765700
Mishaal Rahman has written a detailed post about virtualization on Android: https://blog.esper.io/android-dessert-bites-5-virtualization...
I want to treat the "old" phone as a server: 8 cores , 6 GB Ram, UPS, plenty of storage(expandable), Low power consumption , small form factor, redundant network 4/5G+Wifi, has built in screen and "keyboard" for time when you need to do debugging.
Does others experience with this kind of setup? What services are you running ?
I've been thinking about this quite seriously, and for now I see a few pain points:
- Some phones (looking at my daily driver, a Galaxy S4) do seem to allow disconnecting the battery from the charging circuit, which could lead to issues in the long run
- Ideally, you'd want to connect a USB hub over USB OTG (wired Ethernet, USB storage, real keyboard). I have yet to try charging the phone at the same time, although I think some cables enable this.
I just checked my Pixel 5 for example reports USB 3.2 (as in, that's what it's actually connecting as to a Linux host per bcdUSB)
Even ignoring USB 3, most servers should work fine when capped to 100 or 200Mbps.
It sounds nothing, but looking at Nginx logs scrolling on a tiny phone screen is so unbelievable.
I remember being able to run a rootless debian chroot (using utility called proot) on Android 9 device, but things might have changed in meantime and I don't know if it's still straightforward.
If you're looking for serious performance, though, it may not be practical.
note: I am the developer of UserLAnd.
(1)https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d...
Phones are not designed for continuous power draw (and consequent heat dissipation) - contant-use power dissipation limits are very low. The performance dips dramatically, and the constant high temperature kills the onboard flash prematurely. Same thing applies to the radios - wifi and cellular. Sustained data transfer on either of those interfaces causes issues - dropouts/disconnects/thermal reboots.
This is in addition to the fact that phones just don't have great I/O.
An external case can help to a very limited extent. I tried attaching a large PC heatsink, and it did help, but not to the extent that made the "server" any good. I just switched it out for a 50$ RPI4 and its vastly better in pretty much every way.
But there's more nasty lurking problems in this area, like that phones aren't designed to be continuously powered. They will naively try to keep the battery at or near 100% charge, which will destroy it relatively quickly, and not uncommonly in the "it's bulging and increasingly likely to burst into flames" variety. 2 years is considered a "decent run" for things like device test labs as a result (see eg the FAQ on https://github.com/DeviceFarmer/stf )
If you do your timer idea it seems like either you're going to be hitting it in the 80%+ recharge over & over & over again, which doesn't seem meaningfully different from leaving it plugged in? Or you'll be in the sub-80% quick-charge zone, which will destroy the battery even quicker.
Maybe someone here can help me understand how power draw works on Android.
I have a ZTE Z959, a Cricket device. I use the phone to take photos with Open Camera every few seconds and stitch them together to make a video with ffmpeg. (Someone told me that YouTube has no practical limit on storage and I wanted to prove that they will cap me at some point but that is a topic for another day. Basically, the tl;dr here is for my casual use, YouTube has unlimited storage).
But I digress. The point is at some point the phone's battery started swelling up which became a fire hazard. I wanted to power the phone without battery. I have a Thinkpad 65W USB type-C charger. The first challenge was easy to work around. The phone just goes on a boot loop but if I add the battery and plug in the charger, the phone boots up ok. After the phone boots, I can remove the battery and the phone stays on (provided I don't do things like use flash, my guess is flash needs more power than my charger can provide.
Can someone shed more light into this process? How does all of this work? Does all of this mean my phone is technically running from battery even when it is connected to the wall?
In the end, it really wasn't worth the hassle. Networking ports would go unresponsive when the mobile CPU on the phone would go into "deep sleep". The battery began expanding after a few months.
CPU was more than capable to do the actual processing work. I/O with the SD card was passable.
I really wish someone would invent some sort of generic battery adapter that could transform any device requiring a battery into something that can run on direct power. I really adore that old Sony Ericsson Xperia android device.
But anyways in the general case the user wants the battery to charge when they connect their phone. Not allowing the phone to run without a battery will show more clearly that there is an issue with battery connection or battery itself, than if the phone would run when connected to power without battery.
This is a non-issue since battery status (or lack thereof) is clearly shown in the UI. A more likely issue is that the battery is commonly relied on to deal with peaks in power draw, beyond what can be supplied via the USB port. This can even be an issue in many laptops.
Yes, it does the same thing on my old ZTE z959. However, the phone boot loops if I try to boot it without a battery.
The charge-discharge cycles needlessly put a lifespan on that component when I'd like to have it left on 24x7.
Same for always-powered laptops. With WFH, for 1+ year I've used my Thinkpad as a desktop, not bothering to unplug when fully charged, and now the battery doesn't hold charge for 10+ mins.
I don't know anything about how much "oomph" a dashcam needs as opposed to a smart phone or an uninterruptible power supply but I kno0w one of the bullet points in the marketing of the dashcam on my car was it uses a small capacitor as opposed to a battery and therefore it is safer to use it in a hot car.
I had a dash cam years ago that had a capacitor, and all it really was for was to make sure the camera could finish a write operation and close the video file gracefully to avoid corrupting the last segment. Cameras with batteries often can support recording even while the car is off without draining the car's battery.
IMO, the solution to the battery-in-a-hot-car problem is to have the battery be an in-line part of the power cable that can be placed in the glove box, outside the direct sunlight, rather than building it into the camera itself.
About 4 months after COVID hit and I started to WFH, the battery in my Pixel 3 started to swell because I had allowed it to basically live on the charger all day, constantly at 100% battery. Also, by that point, a 100% battery would only give me about 2 hours of screen time.
A few months ago, I got a Pixel 6 Pro, and I'm basically just charging it from a weak 500 mA USB port a couple hours each day, keeping the battery between 50-80%. I'd really like to set an 80% charge limit and just forget about it.
On my OG Motorola Droid, I once tethered my laptop to it and downloaded a torrent.
In 15 minutes, I drained 25% of the battery. IIRC, it had a ~2,000 mAh battery. That meant I was pulling 2 amps from it. This was back in 2010, when most phone chargers and USB ports were still only 500 mA.
If I had relied on USB power, it wouldn't have been able to power it.
Oh, and yes, the phone got incredibly hot during this time. I thought I was going to burn my hand when I picked it up.
Upcycle an old Android phone. Install apps for Nextcloud, Jellyfin, etc. Do a quick OAuth2 flow with your domain name provider to tunnel a subdomain directly to the app, and you have an end-to-end encrypted private cloud.
For this to work we need:
* Simpler domain name providers targeted at consumers instead of IT professionals. You shouldn't need to understand DNS records to use a domain.
* An open protocol for setting up tunnels[0].
* Nextcloud et al need to implement the protocol on their end. For open source projects 3rd parties can make wrappers.
[0]: https://forum.indiebits.io/t/toward-an-open-tunneling-protoc...
I could even imagine such a system having two different CPUs (or, more likely, different cpu performance cores in a single package) that power up/down based on wired power availability, basically just automatically getting many times faster when connected to power and not having to conserve juice on battery. Storage and memory are already fairly low power these days, and tiny. Mobile (i.e. handheld) GPUs are now powerful/efficient enough to run high-res handheld displays with all day battery life, which while probably not 4k gaming level, are more than enough to run a multimonitor desktop setup when not gaming, especially if you make the quite safe assumption that they'll have wall power to crank up the GPU whenever asked to run external displays.
I'm really excited about mobile computing over the next ten years. The Nintendo Switch and M1 iPad Pro are little glimpses into this future. I look forward to replacing the dozen computers in my lab with a single handheld device that can simultaneously virtualize many of them and conveniently multiplex several big displays between them, and come with me in my pocket when I leave.
So it is "the future" in the same way 3D TVs were: Much hype and then kinda neat, but not great.
The world doesn't exist. And it's not that much more expensive for the workplace to add the computer, and it's much more convenient to just carry our own ultraportable laptops so that we could work at coffee shops and on the planes.
But perhaps there is an use case out for parents with multiple kids who don't want to use low-powered or hand-me-down computers...
For that you want something that is ubiquitous anyways and works with everything. For samsung that was HDMI and usb (kinda works, but too many cables) a few years ago and nowadays is just a single usb c cable. Works with laptops, tablets and phones.
Counter question: Why aren't docking stations for laptops common in hotels/coffee shops/wherever? Or am just not staying in the "right" hotels? To me it just seems that the demand is pretty tiny.
Well, there is an attack called the "evil maid" attack. This attack can happen whenever your hardware is unattended for some period of time. A hotel where maids enter the room every day unattended is quite literally the scenario for this attack. Imagine the surface area for attack, where a dock gets modified, then an unsuspecting user plugs into the dock.
Not only is the demand tiny, but the liability is incredibly high for hotels.
The hardware was nice though.
- External GPUs are still pretty bad
- Tablets with cellular connectivity are if anything less well supported than before. I think this is mainly because carriers aren't really supporting the idea of one person/account having multiple "phones". Smartwatches have the same problem - I remember going to a Samsung store and they were showing off a smartwatch that had its own SIM card and cellular modem, but the staff couldn't tell me what kind of phone contract you had to have to make it work
- Small devices still mean a noticeable compromise in power. I've tried using Samsung Dex as well and it's... ok, but appreciably worse than even a netbook, even if on paper the processor/memory/etc. ought to be catching up. Laptop as primary computer only really took off once you genuinely couldn't notice any performance disadvantage compared to a desktop, at least in my friend group; I think it'll be the same with tablet and (eventually) phone/watch/ring form factors
I might be missing something about cultural differences but... why would you expect an electronics store to tell you what kind of plans your telco has?
Here in Switzerland pretty much every telco offers an additional SIM for tablets and watches, but you need to talk to the mobile operator not the electronics store ^^
Prices for just a SIM without buying a phone seem to be pretty high.
Here selling SIM-locked phones is not even legal. In most European countries it is legal, but still less common than in the US. So operators have to serve customers not buying a device from them on competitive terms.
This was true 5-10 years ago. Nowadays, nearly every mobile network regularly has offers to entice users to bring their device from a different network in exchange for a cheaper monthly plan or similar.
Another issue is that both the watch and the phone need to share a phone number if you want to leave your phone at home and answer calls and receive SMS on the watch. This isn’t standardized and only works with each watch’s supported carriers.
It’s quite possible the Samsung watches don’t rely on this system, but I’m not sure and may have also assumed it was worth asking like the GP.
Not my experience. I'm sure it depends a bit on your carrier, but on T-Mobile it was easy to order a data sim for a tablet from their website. Setting up a smart watch was even easier with eSIM, it just sets up everything for you when you pair with your phone.
(1) SIM locks exist in some countries. But they are commercial practices, not technical incompatibility.
Also Samsung is really good at adding features and then locking them down in weird ways, breaking basic features or just providing horrible user experience.
Maybe they've gotten better, but the last time I looked at reviews they were generally flaky (driver issues or incompatibilities with particular games) and had performance issues, to the point that a lower-model built-in card would often outperform a higher-model in an external enclosure. I'm sure they're coming eventually, but I haven't heard of anyone having an actually polished experience with one in day-to-day use yet.
1.) Run windows/linux distro on the go.
2.) Can play graphically demanding titles in 720P.
3.) Has a dock which supports ethernet, Mouse/Keebs, HDMI out.
4.) Can have upto 4TB internal SSD with tweaks.
Want to execute your own code? Fine! Buy a license!
That's what you're looking forward to.
1) Forwarding X11 to a desktop is easier (and all the apps run on X anyway)
2) Since it’s just Linux all the apps can run on a desktop just like the phone, all my stuff is synced with git or rsync, and if there’s something I need outside the usual folders it’s just an scp away. There’s absolutely no reason to use one particular machine over the other other than form factor and computing resources.
It just makes a lot of sense to have a decent desktop permanently plugged in that you can use without any hassle. Devices like that will kill laptops though, I know it did for me. Of course I don’t think this will happen with Android. Google is way too greedy and they’ll find a way to make it unusable.
The hardware in mobile phones needs to improve substantially for the scenario I described to be practical; there's no hardware that supports it today, but the software in TFA is a step in the direction.
(As far as I'm aware, they still do this on Pixel 6.)
I already use my laptop as a desktop when I'm at home by connecting it to a USB-C hub, which in turn connects it to my monitor, keyboard, mouse, etc. I think the smartphone as a "single device which can be used for everything" is a cool concept and definitely possible considering how powerful modern smartphones are. The limitation is software.
It is stuff like O365, Github, OneDrive, AWS etc that enable that. No plugging in, no reconfiguring devices. Moving between windows 11, android and debian everything I want is right there.
I can't see the advantage, yet, of trying to consoldate down to one device.
I think that's the point.
There's a nontrivial % of Mac Mini / MacBook / iMac sales entirely because of the need to have Mac to publish anything, even PhoneGap/Cordova projects and Safari Extensions to the Apple App Store.
The iPad Pros are on par price-wise with the Mac after you get keyboard cases etc, and on iOS they also get a huge cut of every app sold since you have to get them from the app store. They'd probably be thrilled if Macs were replaced with iPad. The can always jack up the price later.
They wouldn't have spent years neglecting the downfall of the Mac if they cared so much about that revenue.
Each Apple device has a very nice overlapping niche and a lot of consistency between them but some devices are intentionally not designed to do some tasks. iOS is fine for non power user tasks and simple automation but nothing more. For 80% of what I do that is fine so I usually go to the iPad first always. But if I want to sit down and do full on keyboard based productivity it's the MBP every time.
The iPad Pro has a very special place in my heart though. It's the most reliable and efficient machine and with the Apple Pencil it's a game changer. I love to take it with me when I go out for a weekend and will sit in a hotel, do spreadsheet, organise tasks, do some drawing, watch some streams, casual messaging and emails and even video and photo editing. But not programming!
Naturally it is somehow still a PhD topic, but imagine using Swift playgrounds with the pencil as if it was paper notebook.
I can imagine such a person finding this idea gratifying, albeit perhaps too much of a REPL for his tastes.
2. The iPad Pro already has keyboard and mouse support
3. The iPad Pro is already powerfull enough to run virtual machines via emulation, see UTM
4. The formfactor is already prooven by the success of Microsoft Surface and copies.
5. The virtualization APIs created by Apple already exist
This is just a matter of Apple having an enforced monopoly on app distribution and using that power to dictate what you should be able to use each device for.
2. Sort of. It has good keyboard support and completely different mouse support to most platforms.
3. It probably isn’t within the thermal envelope specified and the storage available.
4. Surface is horrible so I’m not sure why that’s comparable.
5. Yes they do and are exposed by macOS only.
I agree with apple. One of the reason iPads are so damn good is that they put some constraints on them to stop people doing horrible things. Virtualisation is one of those horrible things.
The iPhone was originally planned not to have any apps. I guess that would've been even better (and less horrible)?
The Surface Go with type cover is an amazing janky device. It weighs almost nothing and has the CPU power to match, but I can toss it in my backpack and have a lightweight dev environment with me all the time.
It's great because it's has no software constraints, despite all the hardware compromises. I'd ditch it in a second if the iPad could run full macOS.
2. A keyboard is a keyboard and a mouse is a mouse. Remotely or inside a VM they behave as you expect the remote/guest to behave.
3. Bullshit, the Macbook Air has the same thermal envelope
4. Horrible or not, it prooves the formfactor is viable and desired by people.
5. An arbitrary decision designed to protect market segmentation.
That is a rather emotional response. What did the horrible virtualization ever do to you?
2. Yes and no. It uses finger emulation on iOS. There is precision control if you need it but the UI is designed for fingers not pointers and switching between one and the other is jarring to say the least.
3. No it doesn't. I have one. The MBA has a much lower thermal resistance than the iPad Pro does and doesn't even get remotely as hot.
4. It proves it was sold to people, not that it is desirable for any particular tasks. You can't draw than conclusion without more data which you have not presented.
5. Not at all.
As for virtualization it is a pretty bad solution for most problem domains. It adds overhead, inefficiency, latency. At that point it is illogical to use it for devices which require low overhead, efficiency and low latency i.e. most mobile devices out there. Taking the initial post into consideration, in what insane world does it even make sense to run a full windows stack on a mobile device when the only thing that matters is the applications?
It's an insane proposition really. I don't do it on any laptops either. Same set of compromises. It barely even makes sense in the cloud either where we end up gaining cost and reduction in performance. Containers are as far as virtualization should go at this point.
So may be they never will give us Mac experience on iPad (including the shell, forking processes, compile any program which include JIT, etc.) But if they do, it is very likely it is some kind of virtualization that contain the associated risks of those freedoms.
I have a new M1 MacBook Pro with a large monitor for programming, but since I usually write using an iPad, having first class development tools for all popular langauges would be very nice.
I really don't see what this brings. Is google so lost that the only "innovation" they can bring in android is descovering that the linux kernel has support for virtualization ?
https://blog.esper.io/android-dessert-bites-5-virtualization...
Ps Firefox containers are great indeed and I use them for the same reasons. But I doubt this is the intended usecase for this. I don't see Google investing a ton of money to build something that will hurt their bottom line.
Like in the case of the Shelter app.
https://play.google.com/store/apps/details?id=net.typeblog.s...
When talking about the strategy of a successful multibillion dollar company, the most likely answer is "no".
The very short article explains at a high level:
"they’re used for things like enhancing the security of the kernel (or at least trying to) and running miscellaneous code (such as third-party code for DRM, cryptography, and other closed-source binaries) outside of the Android OS."
First Google is gonna run Fuchsia on Linux, then linux will be removed entirely.
that's what this laying the groundwork for.
Still not seeing the point?
People are either gonna love or hate it. Love because of how little space it requires or hate because the performance is gonna be worse then even the non pro versions of the surface.
I wonder when we'll be there. For sure we're not there for wireless, yet. It's unreliable, especially if you have a lot of wireless devices around.
That's the real killer feature.
A mid-range Xiaomi phone is better than the Librem 5 and costs four times less.
Also, it will receive software updates forever unlike any other phone.
not to mention, from the thread you linked:
"About 2600 L5's have been delivered, so everyone who ordered before October 2017 should have gotten their phones. Purism reportedly just got in another 1100 L5's from the factory, so when those get shipped out, that should cover the orders up to mid-2018."
I mean you can't be serious. People paid almost a grand to wait four years for a phone?
But this tiny company with no experience in smartphones did finally produce the product respecting users unlike Google or Apple. The current problems with CPU supply is not Purism's fault.
Also, the phone supports microSD up to 2 TB.
When you add the display, battery, keyboard and mouse, it's really cheap to add brains and storage and build a full laptop that can share data with your phone.
This is why most lapdocks fail - they aren't that much less expensive than a cheap laptop. This is also why, at some point, nobody was making dedicated terminals for large computers - they were as expensive to build as PCs.
"I can already achieve this with FTP/samba/whatever." Sometimes taking existing, established technology and making it easier to use is all it takes to "innovate".
Of course I have no idea how killer this particular Android feature will be. I'm just criticizing the "this is not new" argument.
They appear to be in the black.
1,369.3 (bln) Convertible senior notes, net, non-current
Who wouldn't want to borrow $1.3 billion USD interest free or close to it? We need to take a close look and try to understand these numbers instead of just seeing "negative" = "bad"; more often than not it much more nuanced than that.Microsoft OneDrive is fuckin' awful in how long it takes for a file on one system to be synced to another, even when both systems are online at the same time. It also has a habit of completely pausing syncing entirely if it reaches a file it can't read (such as a lock file).
Google Drive works well, but I find its desktop client to be resource-heavy, especially on startup. I like its integration with my Android, though.
Its current financial state is more a case of bigger vendors bundling a good enough alternative with their products AND dropbox not adding much beyond "easy to use"; than HN insight of "lol just rsync/bash/perl instead" being right all along.
This one, it's not the first VM on smartphones at all. Running a desktop OS is possible for years with comparable solutions. What makes this different from Samsung's DeX, for example?
Also there are Android based VR headsets, anh their resolutions are getting better. Think of working in a connected virtual office, running Windows applications.
I know there are some options for this, like Samsung Dex, but with this there is at least some potential for having a Windows PC in your pocket. Like Microsoft tried to do with those older Windows phones.
Yes this virtualization allows us to run windows/linux. Thats not the main goal probably. Its more to reuse packages from those stacks on your android phone, kinda like the VMware Fusion mode on a Mac, to run applications side by side, or to run things in a secure virtualized container.
Why recompile to android, when you can virtualize?
Performance?
https://arstechnica.com/gadgets/2021/11/android-12-the-ars-t...
Private Compute Core—Running AI code in a virtual machine?
We need to bring back gestural writing, with simplified letter forms. The basic tech was in production use in the mid-1990s, and there are clearly unencumbered alphabets that could be easily used for this, such as the 19th century Moon Script. Recent UI work has made Linux quite usable on touchscreens and smaller devices, but text input is way harder than it could be.
long shot here, does this make it more possible for production releases to be closer to AOSP and then run the rest on the hypervisor ? Also the future of project tremble, meaning better upgrade paths for all devices (outside of manufacturer will which is still the main issue) ?
Native as in Windows on ARM native? I held Surface Pro X in a shop and man was it disappointing.
The advantage of this approach over running Linux in a sandbox / VM is that you can administer your Android device from the Linux side, which means that you can use your existing backup strategy or other automation tools. With a USB/bluetooth keyboard, it can also work as a small PC in your pocket.
I wish that was true in the real world, looking at you Onyx.
Case in point: I had never heard about Onyx. Coincidence or causation?
I no longer use it, and instead use Magisk startup scripts to start the Linux userspace, but it remains useful as an installer.
This would be a pretty strong argument for me to move away from iOS.
Though honestly I'd probably prefer an android/ios device able to run a different operating system on the external display in all cases.
They had no idea it was for locking things down. Sure, it allows running VMs, but that doesn't change anything about it.
"I'll force A on you, but you'll get B so don't be mad."
... but this only really applies on the surface. Locking things down is the road forward in the industry anyway. That's why the Desktop OS war is long over, too. Everything will, eventually, run on everything.
We're being sold digital lockdowns as features which supposedly provide us with more freedom. In the end we'll have downloadable programs we'll rent to use, which run in a cut-for-the-purpose container, without any ability to tinker, hack, or modify. Rent or die. Don't want any of this? Fine, but you're locked out of the eco-system. Have fun enjoying what's left for you to do/use.
I wish more people knew what's coming. I don't know why they don't. I'm sure the information is out there, but apparently nobody is talking about it, thus nobody knows about it. My guess is simply that it wouldn't actually be particularly popular if people actually understood that they're just being misled.
For those rolling their eyes, considering that nowadays it's the norm to sell safety/security as beneficial, because of reasons based on fear.
Benjamin Franklin would probably be really angry about how normalized it has become to give up liberties for some false sense of security.
The unintentionally worst people are the ones who think this is all a great idea. Because security. Fact of the matter is, though, that if people had to actually know and understand what they're using and doing, we'd not be in the mess we are today.
What I mean by that is that the world apparently has this deep issue with fear of pretty much everything and humanity tries hard to make the fears less worse instead of getting rid of them by using education and getting rid of the fearmongers.
This reminds me of my friend. He insists on having his AV and cookie blocker running. He thinks that's super important. Every new site he manually blocks everything. This same guy also insists on continuously installing all kinds of stuff, and after just two months his new notebook took 20 seconds to boot. When he got it, it were two.
The worst part about this is that he's so brainwashed into believing that he really needs this, despite me being living evidence that he doesn't, that there is actually no way of educating him. The fear machine has dug too hard into him and, unless they stop, there's actually no way of getting rid of it.
Not gonna lie, I actually think this is amazing. On one hand he's extremely cautious about security, which is not unreasonable per se, on the other hand he installs all kinds of shit because he's an idiot who doesn't actually know what he's doing.
He's just doing what he's being told to do.
Amazing.
I honestly think it's even worse than that, because the status quo has made it so we don't even have the courtesy of knowing we're giving up as much as we are.
IMHO, the substance quantity of what is being lost is on the order of an entire language. "Privacy" means something totally different today than what it used to :(, and we've all but lost the very element of *pause, consider* that would be our way back to where we used to be.
I have to admit I'm looking at Europe with a bit of a wobbly mentality these days; the EU is not a panacea but the GDPR has had some really interesting ramifications, and France's position to ban GA recently (if that's what it actually was) was... well it'll be interesting to see how that goes down...
---
> The unintentionally worst people are the ones who think this is all a great idea. Because security. Fact of the matter is, though, that if people had to actually know and understand what they're using and doing, we'd not be in the mess we are today.
I wrote something a while back about end-to-end encryption that also touches on the danger of cargo-culting a "yay! security! awesome"-by-default ideology: https://news.ycombinator.com/item?id=25522220
It's not really a first-class substantial "oooh, thing" perspective, more just unimpressed grumbling about the status quo. But it's a bit of anecdata that does agree with your position.
---
> This reminds me of my friend. He insists on having his AV and cookie blocker running. He thinks that's super important. Every new site he manually blocks everything. This same guy also insists on continuously installing all kinds of stuff, and after just two months his new notebook took 20 seconds to boot. When he got it, it were two.
(This sort of thing is really interesting to me but I'm really bad at talking about it concisely. Apologies.)
A contributory perspective:
The moment I saw "Every new site he manually blocks everything." I immediately jumped to a mental reference point that might be called the "manual drive fallacy". If you give someone a bunch of knobs and settings to tweak, and the knobs and settings induce ideological changes that are not mechanically/concretely measurable, and all this happens within the context of "control" and "freedom"... in certain people, I think the brain can start going very very loopy, in a very specific way. It never gets into a state that would ever be classified as "unhinged", but it's like the brain "discovers" this alternate pathway that satisfies both our intrinsic desire for control while short-circuiting past the "proof of work" feedback loops of self-reflection, critical thinking, engagement in depth, etc that keeps that control harmonically resonant with its environment, in that unexplainable way that makes the influence meaningfully productive at both the micro and macro scale.
It's kind of like if bikeshedding were put in an infinite feedback loop and left indefinitely. Stuff just folds in on itself. Perpetual motion machine meets black hole. Meep.
I call this a "manual drive fallacy" because I personally equate the mindset you describe with having a pathological affection for "manual drive" processes.
I read a while back that the Air Force crashes many more UAVs and drones than the Army and Navy do (or at least they did a little while back) because the latter depend very heavily on autopilot, whereas the incumbent Air Force has always justified its existence by performing those processes manually. At the micro scale both approaches make sense - the Air Force exists predominantly to train amazing pilots, who are going to make mistakes; the Army/Navy exist to defend land and sea, and need unspecialized local air superiority as part of their own bigger pictures. Insights like "computers are actually way better pilots than humans" can only emerge when when a macro scale focus is introduced that is able to laterally make comparisons across verticals while maintaining sight of a bigger picture. (Reproducibly coordinating such focuses is of course the billion dollar question...)
In a similar sort of way I've come to think that there are a similar organization of internal processes and balances that happen in the individual brain that influence the "functional level" or "watermark" of insightful impact and control a given human can have. We all fundamentally want to control, and organize, and achieve cohesion. But the underlying mechanics we use to achieve that can involuntarily affect how efficient we can be overall. If mental functioning is very high, these mechanics can integrate a lot of input, and our control/organization/cohesion will be very efficient, cohesive, and resonant. If mental functioning is low, significantly less input can be integrated into executive output, and the result will be very fragmented and micromanaged.
A person that can only model the effects of control in their environment to a low level may constantly be in a state of disorientation as they continually send their mental models of their environment back to the drawing board to start again as their attempts to summarize the world around them do not integrate sufficient substance to be useful. I'm reminded of mental health advice that generally recommends to patiently remind a person having a panic attack about their environment and what's going on around them, in the hope this encourages distraction from painful mental feedback loops.
I wonder if there's a correlation between fragmented integration and an obsession with mechanical, concrete, "manual drive" processes and procedures. In much the same way there are unexplored knock-on effects from poor social engagement, I think a similar magnitude of impact may result from poor executive engagement, and perhaps one of those effects is a strong affection for tinkering with stuff that has things you can open and shut at a surface or aesthetic level.
Broadly speaking, creative coordination almost seems like a human mental attribute or quality that we imbue into the things we create. We design things according to some intrinsic sense we don't even realize we're following half the time as we simply concentrate on getting stuff done. Good design - perhaps the epitome of "10x senior engineering" we all strive to reach for - is to recognize the need to weave a sort of structured permeability into the things our ambition creates, so our creations can bend and stretch with the wind, and let others' influence in. It's really sad to see this dynamic fall apart. There really seems to be something critical about our brains' ability to "slice and dice" the input we receive, and the functioning of that underlying capacity is what sets the pace.
I've seen a couple of really bad Windows 9x/XP simulators out there that barely let you do anything beyond opening the Start menu. I've long noodled over the idea that the core motivation driving these sorts of projects stems from a sort of focus-affinity that sadly bottoms out at that predominantly aesthetic, surface-depth level of coordination, potentially coupled with nostalgia from a time when these executive handicaps had less of a perceived impact. Maybe the person wants to remember that time, but emotional processing issues make it hard to recall the memory with sufficient fidelity to achieve nostalgic closure, and some frustrated consideration about what might nip this in the bud leads to the conclusion that remaking Windows might fix the problem (coming solely from a surface or aesthetic position - not even remotely close to considering the kernel design or hardware targets). And then maybe the person realizes soon after commencing the project that even just cloning the UI is too much work and will not help them get closer to closure, and they soon give up.
I think everyone wants to express their coordinational capacity and style; and because the brain's comprehension cannot extend beyond its own limits, this capacity and style is never intrinsically wrong.
As a form of human expression and communication, I think coordination's significance is woefully undocumented. We imbue how we see the world, and the fidelity of the mesh we use to integrate our perceptions, into how we express coordination.
(Incidentally, accomplishing this in the digital realm, where we have absolutely nothing to cue off of ("here's the instruction set manual for your 5GHz calculator"), making the inventions all around us the byproduct of an ideological collective sensory deprivation tank: we cue off of our brains. This is both terrifying and inordinately interesting IMO.)
---
> The worst part about this is that he's so brainwashed into believing that he really needs this, despite me being living evidence that he doesn't, that there is actually no way of educating him. The fear machine has dug too hard into him and, unless they stop, there's actually no way of getting rid of it.
Alternative possible perspective (I could be wrong): you operate and exist outside of the scope of his cognizance of control. You don't exist. You're like the syllables of a brand name or jingle his brain just memoizes without considering.
> Not gonna lie, I actually think this is amazing. On one hand he's extremely cautious about security, which is not unreasonable per se, on the other hand he installs all kinds of shit because he's an idiot who doesn't actually know what he's doing.
(Continuing above theme) Or there just might be some totally concidental "miraculous" overlap between his actions and best practice :( and his perception of security might be uselessly broken.
> He's just doing what he's being told to do.
I actually agree here, with the caveat that "understanding is in the eye of the beholder" :v
- is this hardware or bios locked, or will there be the ability to get this functionality on eg older phones
- what are the performance characteristics here, I wonder?
I'm keen because we produce a ton of e-waste in the form of mostly useful cell phones, and it'd be cool to turn them into useful devices again. This might help enable that.
Original blog: https://blog.esper.io/android-dessert-bites-5-virtualization...
This and the videos below it should give you an idea of the performance: https://twitter.com/kdrag0n/status/1493082399520919552
Note: I am developer of UserLAnd.
And an aside: since Apple's SoCs are now much better understood thanks to the M1 and Asahi Linux project, how long until someone manages to virtualize iOS on an Android device? (though I'd rather have Android running on an iPhone tbh)
I wonder if this is because the Linux phones are really starting to shape up?