For folks willing to build from source, I have an additional commit on top of the PR (linked in the comments) that enables support for Android's constrained high speed capture mode, allowing 120fps/240fps camera streaming. Not the most useful for meetings, but enables things like capturing high frame rate mixed reality VR footage. As far as I'm aware, there's no other Android webcam app, proprietary or open source, that can do anything above 60fps.
I don't think this is possible, at least not directly. My understanding is that there's a special optimized path for CameraConstrainedHighSpeedCaptureSession recording to MediaCodec surfaces backed by a hardware encoder. If you capture to a different type of surface, the frame rate will likely drop to 60 or lower (assuming it's even allowed--I have not tested).
I'm not too familiar with image analysis, but if it's acceptable to work on lossy frames and to take a small hit to latency, you could record to a MediaCodec hardware encoder and then immediately send the output to another MediaCodec instance to decode it.
Obviously, should your wife be non-technical, you'd put that script in a file and tell her to double-click it. Or just set the whole thing up for her so it magically works.
Looks like you have quite the adb arsenal there, so maybe you have any suggestions for the two things missing from mine:
1. setting a static ADB/TCP port or automatically sending it to the PC (Android now changes it every time)
2. enabling ADB/TCP on mobile hotspot (Android complains "Please connect to WiFi")
Other than those two things, between scrcpy, KDE Connect and Waydroid, the Linux-Android integration is basically perfect and makes even the Applers jealous.
You have to do adb tcpip for wireless adb once in a usb mode per boot, I actually just use port forwarding of all pc port to localhost using ssh, I have a bash script using nmap to find ip
Is there a way to do the reverse, i.e., seeing the computer screen on an Android device?
Specifically I would love a way to use my Android device as a remote controller for PDF presentation. For now I can do this with KDE Connect but the remote controller is blind, I have no way to see the current slide on the Android device, much less to use it to annotate the slides in live.
This is particularly helpful to people using asahi linux and wanting to connect an external monitor. That can be done with something as simple as a raspberry pi.
EDIT: apparently this project help achieving the same thing on different OS but using webRTC and a browser:
This is a bit out of left field, but if you're a web developer you can use Browsersync to control a web page across multiple browsers (even on different devices). So really you "just" need a good PDF viewer on that web page.
I've been thinking a lot about this kind of use case, and I'm more and more convinced we just need better ways of handling web content on the LAN.
Like, no matter what, the UX will probably be meh just trying to mirror screens. Instead the presentation app could give you a QR code with a TLS cert in it, and you could scan it and get a secure connection to it's mobile optimized web remote UI.
We are really nowhere near using the full potential of all the devices and connectivity we have.
Unfortunately, I've become a MacOS (ARM) user recently and start to notice such small misfortunes here and there like your solution being not applicable to MacOS.
It started out as being a means to send a video feed into OBS[1], which is how I rigged the webcam input, but as the project grew, it expanded to being a way for me to spin up desktop video and audio sharing in a browser, sorta like Zoom, etc. This let me run virtual movie nights with people remotely.
Whilst it's possible to use it via the 'create a room' interface, you can also do it all via URL parameters which I found much more flexible and robust. See here[2].
You create source and recipient URLs and then it just automagically makes it all work via WebRTC. I was able to for example make a source that captured my VLC window and sent out the video and audio, and then two destination URLs which received the source video and audio, but also sent their own audio to one another. This meant we could hear and watch the movie but also talk to each other via our microphones. All within browsers.
I've got no relation to this project besides thinking it's really awesome.
I mean if you have an iPhone and thats your only Apple device this looks cool, but its kinda crazy Macbooks still ship with 1080p cameras. Not the event this month, but i think the one before that they demoedd using your iphone as camera for facetime on the desktop.
I see this argument a lot, but it’s actually a pretty complex trade off.
Screen size, target audience (1080p Zoom), cost, sensor size, and pixel size all come into play.
You can pump numbers for the sake of it on paper, but the reality is that it’s very hard to cram a good image sensor into a laptop screen in an economic way. There’s unfortunately just not enough real estate as thin as they are.
Meanwhile, phones are quite a bit thicker & cameras are a huge selling point. Plus, almost everyone has one. It makes sense that if you want higher quality video on your computer, you’d use the other device which has video higher up on the design priority list.
> There’s unfortunately just not enough real estate as thin as they are.
Darn, one piece of marketing BS getting in the way of other marketing BS. Yea, 1080p is plenty high res enough for your work meetings and family calls - but users don't really care about the thin aspect, we care about weight. Getting better key depth on laptops in exchange for a modicum of extra width is a deal I'd take any day of the week... and that'd allow far better cooling engineering and for a few more bulky components.
The webcams are for videoconferencing. It’s pretty rare for videoconferencing to support better than 1080p30. Apple is not exactly shy about using mediocre parts when it won’t make a difference.
Well there’s more you can with more resolution than transmit a bigger picture. Try the iPad camera during FaceTime. That will pan and zoom the view to keep you in focus and it’s only made possible by good resolution and a wide angle camera.
I’ve configured OBS to do this with a 4K camera with a wide angle lens I have, plugged into a laptop with a 1080p camera. Which is be better than any camera they could ever fit into a Mac due to the sensor size. I usually don’t turn this effect on because I find it’s a little distracting…
The other issue I didn’t bring up is the form factor. Phones and tablets simply have more room for a webcam than the MacBook Pro screen and I don’t actually know anybody shipping a laptop with a built-in 4K webcam. Mind you that Apple could ship a better camera with its studio display but opts not to.
Higher resolution would be a complete waste for videoconferencing. Having good pixels and a good lens is far more important than high resolution, especially for video. And resolution often comes at the cost of pixel quality. Small pixels have worse sensitivity, unless you can fit a bigger CMOS sensor.
But you’re not going to fit a really good lens on the laptop screen without an annoying bulge anyway, and for 99% of people it would be a waste to spend resources on it anyway.
Using the phone is a much better solution. People are likely to have a good camera there with an OK lens anyway.
>But you’re not going to fit a really good lens on the laptop screen without an annoying bulge anyway, and for 99% of people it would be a waste to spend resources on it anyway.
It can be done without a bulge. But designers gonna design and make something ugly. Smartphone CMOS sensors are not bigger than the usual stuff in Laptop bezels.
It's ironic that they default to using the built-in webcam for Apple Developer ID authentication, because text doesn't come out clear enough to be recognized.
Its like a 5 hour job to get something that technically works and then a 10,000 hour job to get something that works flawlessly. The Apple integration with the iphone and macbook is the most seamless setup I've seen so far but I've still gone back to just using the built in webcam because its too fiddly to put my phone up on the screen and occasionally have issues where it won't connect.
Phone as webcam just doesn't seem like a long term solution, eventually built in webcams will be cheap and good enough. And tbh I find the built in one on the macbook to be bordering on good enough once you consider how compressed and tiny the output will be on the other persons screen.
MVP to full product is definitely the bigger part of the work. In the environment of early COVID, I think an app that had some rough edges would've still been very useful. Perfect is the enemy of good and all that. Phone as webcam shouldn't exist at all (how do you even mount it?), but somehow the video and audio quality on phones is still years ahead of what's available on even high-end laptops.
Rough edge apps have been around for years. I tried one that worked in the browser and could connect to OBS on your laptop, it was just too cumbersome though.
Apple actually did come up with a good solution for mounting the phone. A small disk that connects to the iphone with magsafe and has a flip out tab that can hook on to the top of the macbook. It's surprisingly stable and nice.
I had the opposite experience. I have a personal iPhone and a work iPhone and every time my work iPhone is near my work computer, it switches to it whether I want it to or not. It drives me nuts. It's fine when I want to initiate it but the number of times I've just set my work phone down on my desk thoughtlessly and then tried to start a video meeting in Slack or Teams or Zoom only to not have video because it's using the camera pointing at my desk is too many.
Canon also released an app during lockdown to make your DSLR or mirrorless camera into a webcam too. Shocking how quick companies can do things when a global pandemic pushes them after years of odd tethering and window screen capturing mess I've had with canon before hand for live streaming.
Exactly. It's not like you suddenly have no more use for video cameras or microphones. The "king" of cheap webcams is still Logitech CX920; anything better than that starts with a separate HDMI capture card and can cost up to an order of magnitude more. Meanwhile you've had a decent camera in your phone all along.
Using a good camera for your video call is simply showing respect to the person/people you're talking with.
I disagree. The most important thing is voice. In meetings we communicate (hopefully), voice should be the top priority. I know how my colleagues look like.
That's fair, but largely unrelated. Neither webcams nor phones tend to have super high quality mics. It is best to get a standalone mic to improve quality, or even just high quality bluetooth headphones.
But the builtin camera on phones is a huge area of attention for them. They tend to be amazingly high quality to the point of being overkill as a webcam.
You disagreed, yet I've never said that audio is less important.
Even flagship smartphones don't have studio microphones with 48v phantom power, 32-bit float, pre-amp gain control, etc - that's something you'd have to invest in separately no matter what. But if you can get better video for free, why wouldn't you?
You mention that you never said audio is less important, but they never said that you did so. That doesn't mean it can't be disagreed with.
I completely disagree that good video is a sign of respect. I consider people wanting video on in the first place to be a sign of disrespect. It is rarely important for getting work done and I see it as a waste of resources.
> I completely disagree that good video is a sign of respect. I consider people wanting video on in the first place to be a sign of disrespect. It is rarely important for getting work done and I see it as a waste of resources.
I agree that video is often unnecessary for effective communication, and I too avoid it whenever it's not requested. But there are contexts in which it's great, like occasionally seeing the face of a loved one, who lives far away; or helping debug an issue with a physical object (PCB, server rack, appliance...) that you need to see to understand what's going on. Especially in the latter case, having better video quality is just objectively better, especially if you can get it essentially for free.
Too little, too late for me... I hate to be the guy having those "hot takes" or whatever, but hear me out for a sec:
I didn't get a cell phone until 2013. (Yes I used land lines until then.) It was a Nexus 4 (still love the grippy sides and sleek glass back). Every 2-3 years I traded up, all the way until Pixel 6.
Tomorrow my first iPhone will be delivered. Why? A lot of reasons, but some are:
- I can't just plug my Google phone into an external display to mirror it. Uh, hello?? DisplayPort out is explicitly disabled in the source code with no reason given: https://twitter.com/MishaalRahman/status/1189998588023234560 -- yet this works great in other phones.
- I can't access my text messages from my Android phone (without a separate app like SMS Backup & Restore) -- go ahead, try it. Yeah, do an adb backup. Maybe rooting your phone would give you access, but it's impossible otherwise AFAIK. And I think rooting your phone deletes everything in the process.
- I can't access my phone backup. It's ONLY stored on Google's servers. The only way to even get close is to restore it to a phone. This is a physical device I bought and literally am holding in my hand but can't access all the stuff on it! Did you know you can just plug in an iPhone into Windows or Macs and dump a backup to your computers? It's all right there, text messages, system settings, contacts, photos, databases, EVERYTHING (except maybe hardware-protected keys). It's amazing.
- Do I even need to mention all the Google shenanigans? We all know what I'm talking about, right? The mess of messengers... the killing of various services, the lack of support, the stronger integration with ads and tracking.
Apple's not perfect either, but I feel like it's worth a shot inside the walled garden for a bit. I like that some of these common sense things are not a problem with iOS:
- Display out.
- Accessing your own device.
- Messaging that actually makes sense.
- At least it feels like Apple cares about privacy; counterintuitively, I feel way more in control using Apple products than I do Google ones.
I switch between both every few years, on iPhone 14 ATM.
Honestly Android does a lot of things better - there's so many stupid "because Apple" things on iOS. For example it's impossible to tell the charging speed/estimated charge time, I have a lot of charging bricks between places and I can't tell if I picked an iPhone compatible fast charger/cable or not ? Or when I have Chrome/Firefox installed, highlight text and tap search the web - it takes me to Safari ? A lot of small annoyances like these where you can't do anything about it because the OS is so closed down.
Android is way more customisable, easier to side load stuff (like running GBA emulator on iPhone). Also a lot more exciting phones in the Android ecosystem (eg. Samsung flip phones)
I like the ecosystem integration with my Mac but I wouldn't say one is clearly better than the other.
Both ecosystems have their own pros and cons but I wouldn't trade my Pixel for an iPhone ever.
In fact, I recently got a refurbished iPhone 13 just to check the ecosystem out (as a mobile dev) and get a feel for things but honestly I prefer my Pixel more. There are so many things that Android does well like notifications and typing (these two stood out to me on Apple - horrible implementations really, especially the latter) that it will always remain my primary driver.
But yeah, if someone thinks that Android is not for them and Apple's walled garden is worth entering then or vice versa then whatever floats your boat, I guess.
It’s not the touch screen that’s the issue. It’s the autocorrect. And it’s not an imaginary comparison I used to have “t9” on my phone 20 years ago that was better than what maybe any phone now has. I’m pretty certain iphone was better once too. I remember being able to touch type on my iphone (yes on a touch screen it was that good)
If there’s one thing that infuriates me about the current crop of phones, it’s this. I’ve actually mostly switched to voice dictation because my iPhone touch screen sucks so much. Bring back physical keyboards!
I was a devout Android user in the early days, I've launched Android based consumer products and I still use an iPhone.
I always joke that when Android can handle a screen rotation without blanking the screen, I'll switch back: It's not about the actual blanking of course, it'll just mean they finally ripped out a design tradeoff they made for a device with 256MB of RAM and just... never fixed.
Android is full of decisions like that, like the horrible storage framework churn that randomly made a generation of devices dog slow as various terrible FUSE implementations.
Decisions that are technical, but just end up affecting user experience every day you use the device.
Every single phone in existence running Android blanks the screen.
It can be hidden by frankly disgusting animations where they do things like squish a screenshot of your current screen to hide it, but the literal UI is being tore down on every rotation.
As you can imagine that's a pain in the ass to deal with on the app side, and until relatively recently the framework did a poor job providing support for handling it all. It's a very common cause of app crashes too.
(To really get technical, apps can opt out of this... but doing so means you'd need to reimplement the entire view stack and rotation yourself, which doesn't happen for anything but video games)
I know what you're referring to but Apple made this experience worse by disabling rotation in iOS on the home screen altogether.
Of course most people don't notice because they unlock the phone with Face ID and usually don't stay on the home screen for too long, but still - if you push the home button when in horizontal mode you're presented to a rotated screen.
As for RAM: I was surprised to note that my phone has in fact 4GB of it (always thought it was 2GB), because apps get suspended all the time. It appears that at least on Android that was a sound design decision.
My several years old Samsung doesn't blank the screen.
Android indeed does tear down the activity and creates a new one with different rotation and size; but activity is not the framebuffer currently displaying. Recreating the activity does not imply blanking screen.
Some people like to play games with semantics, but I say you lose the right if you can't get the basic details right...
You're saying "activity is not the framebuffer currently displaying", which is a completely nonsensical statement. The framebuffer does not change: the Surface Flinger is bound the the framebuffer and that's not changing during a rotation.
Tearing down the activity and creating a new one is literally blanking the screen as far as the activity is concerned: removing all views on the activity surface and adding brand new ones.
If you were to look at the activity in a view debugger frame by frame you'd get... a blank screen.
You could poll the WindowManager and there's... no views.
_
There's all sorts of ugly hacks to hide that fact, but at the end of the day supporting seamless transitions across rotations is something that dates back to iOS 3.
It's an artifact of the literal first Android phone that ended up causing pain for developers and instability for end users in perpetuity. Google simply is not product driven in a way that will ever allow them to match Apple. No UX obsessed company would have allowed that mess to go on as long as it has.
While I agree, I must say that GBA emulation is a bad example here.
It’s one of the few things you can "easily" sideload on an iPhone without jailbreaking using AltStore (the emulator is named Delta, btw and it is excellent).
I will not say that AltStore is really practical to use but GBA and GameCube emulators are basically the only things you can sideload without a lot of pain (along with UTM, a virtual machine runner.
I haven't tried this for a while, but just for comparison I actually got a GBA emulator on my Samsung via play store. It's very much an Apple thing again.
> - I can't just plug my Google phone into an external display to mirror it. Uh, hello?? DisplayPort out is explicitly disabled in the source code with no reason given
This apparently changes with the Pixel 8
> - I can't access my text messages from my Android phone (without a separate app like SMS Backup & Restore) -- go ahead, try it. Yeah, do an adb backup. Maybe rooting your phone would give you access, but it's impossible otherwise AFAIK. And I think rooting your phone deletes everything in the process.
> - I can't access my phone backup. It's ONLY stored on Google's servers. The only way to even get close is to restore it to a phone. This is a physical device I bought and literally am holding in my hand but can't access all the stuff on it! Did you know you can just plug in an iPhone into Windows or Macs and dump a backup to your computers? It's all right there, text messages, system settings, contacts, photos, databases, EVERYTHING (except maybe hardware-protected keys). It's amazing.
This is not applicable for all Android phones
> - Do I even need to mention all the Google shenanigans? We all know what I'm talking about, right? The mess of messengers... the killing of various services, the lack of support, the stronger integration with ads and tracking.
No I don't, none of the dead services have impacted me, what mess of messengers? Lack of support for what?
Everybody use WhatsApp here (east of the Atlantic Ocean,) even on iPhones, because you never know which kind of phone all your friends are using. Apple and Android could stop developing their messaging apps and nobody would notice. SMSes are only for banks and spam.
Given that iMessage has 1.3 billion active monthly users, WhatsApp has 2 billion and Facebook Messenger with 3, I don’t believe they are the one living in a bubble.
Not everyone and as soon as you go to another country they are using another messenger so unless you want to never communicate with them again you will have both installed
It's the same here in Japan: everyone uses LINE messenger. SMS is pretty much never used because it's considered a privacy violation; only delivery companies and banks and the like use it (and spammers, like you said). Nobody cares about iMessage's colored bubbles.
No, in Japan, it really is everyone. All kinds of commercial entities also use LINE to communicate with customers even.
Yes, if you want to talk to people in other parts of the world, you'll need a different app for that, because different parts of the world tend to use different apps (e.g., Chinese all use WeChat, Europeans seem to use WhatsApp, etc.). If you just want to talk to people in Japan, LINE is all you need. (Taiwan too, I think)
> People in Japan who don't have foreign friends, don't do business with anyone abroad, never travel abroad, ...
FTFY
> Those people only have them to talk to you
Nah, any single one of them has many more friends outside of Japan than I have friends in Japan. People living on an island with the most powerful passport in the world love to travel, breaking news.
> because you're not in Japan and don't use LINE.
It's true for all of the world except Japan :)
> (Also, Instagram is not a messaging app. Messenger is.)
That's just false. After it's stopped being about photos, it's just a messaging app for me and countless other people who don't care about its tiktok-mimicking reels and other drivel. It's actually very decent at being just a messenger.
I've been on Android for more than a decade, and I still don't know what I'm "supposed" to be using. I have switched out that stuff for third party apps a few years back. Was a disaster zone, I'm sure it still is.
I hate to beat a dead horse but its been an issue even before Android. I had gmail in the inital invite-only launch back in 2004. They added their first real chat feature into gmail (back when gmail was the only google service you needed an account for) in 2006, 2 years before Android.
I don't even know what they call that chat-inside-gmail these days. Talk? Chat? I remember it getting merged with Hangouts eventually and then un-merged. Or was that Voice?
I was on Voice too as GrandCentral back before Google bought them. The mp3 ringback functionality which was the first feature lost in the purchase.
Ended up reminiscing a bit there but its been a crazy ride in the Google sphere.
That was google "Buzz" - a very simple XMPP based chat app, that it really wouldn't have hurt to hold on to. Last I heard it was merged into hangouts yeah, but hopefully it should still work with standalone XMPP clients ...
I don't understand the deep misguidedness of your question.
You've been on Android for decade, keep using what you've been using and you like. When did people become too dumb to choose a thing they like and started demanding socialism?
Socialism has started being adopted as a synonym for "something I don't like and/or don't understand". It would be funny if the word didn't have an existing meaning.
The sad thing is that they were in a good position with this with Google Talk. But they used extremely creative tactics to reposition themselves into a complete mess.
It has all distilled down to RCS Messages and other messenger apps so stop worrying about what Google is doing and start using whichever app your family and friends are on.
I've been using android phones since 2009 and am highly considering a switch to Apple for the next one.
Along with the reasons you state, the ecosystem is really messy. I've bought Nexus/Pixel phones for the last 10 years and continue to be bummed by their performance.
Pixel 1 XL was fantastic, but after about 2 years the camera kept failing. 3+ seconds to load, and it would commonly crash. Ultimately the battery life degraded, and the replacement battery degraded within a couple months, so I moved on.
The 3a fell out of my pocket and broke 2 months prior to the end of security updates. That was a decent phone overall, but not supported by Google as long as I would have liked.
Pixel 6 Pro has been fine so far, but my wife has been having issues with her Pixel 5. Slow performance, unreliable cellular connectivity, etc.
"Don't buy Pixel phones" could be the lesson here, but alternatives are arguably more of a security nightmare. My experience with Galaxy phones has been that they're preloaded with an incredible amount of junk that needs to be un-installed. With Pixel it's exclusively Google apps, most of which can be removed. That gives a smaller privacy and security concern than having 30 different companies with their apps pre-loaded (and possibly not removable).
> Apple's no angel either IMO, but I feel like it's worth a shot inside the walled garden for a bit.
I've hated on Apple a lot over the years and am disappointed that switching platforms seems like the best move after all these years.
I was a huge android fan until I got my first iPhone. Consequence of getting a job that trained me up for iOS development, and eventually I wanted to be able to use the apps I was building. I've never looked back.
Android will always, always have my heart for hacking, I still buy them occasionally for projects and weird esoteric shit I wanna do/try, and for game emulation and that kinda thing. But for my daily driver life manager, it's iPhone all the way. The integrations with HomeKit devices + Apple TV's make my home incredibly smart, absolutely everything is mirrored onto my Macbook and iPads (a current gen mini, and a 2017 Pro that's somehow still hanging in there despite being beat to shit every day for 6 years) without me lifting a damn finger, and when I do get around to upgrading, I plug them both in and all my shit is transferred over, and I blank the old one and send it to Apple for recycling.
Like it's cliche as hell, but it does all Just Work. Androids have caught up quite a bit in terms of power and the "slickness" that iOS got famous for, but at this point, I'm so deep into Apple's ecosystem I'd have to replace damn near every piece of electronic kit in my house to really transfer back over. And the grass just don't look that much greener over there.
Orion is nice but it works by using Safari’s extensions API under the hood. Safari does have a fairly thorough extensions API even on mobile but it’s missing things like webRequest. This is particularly a problem for the Bypass Paywalls extension because you can’t change things like referer. It’s the biggest thing I miss from android.
Yeah I have been using android for every single phone I've ever had, but I don't see the point once iOS allows sideloading. They have locked down android so much(I kind of understand why, but still) at this point that sideloading is pretty much the only difference now. So why go for android?
You can side load apps, but need a Mac or a MacOS VM and XCode. But without paying the $99/year developer program fee, apps have to be reloaded every week. I paid the $99, as I grew tired of reinstalling the tethering app or GBA/PSP emulator.
If sideloading becomes easier, that’ll be a big win in my book.
> 3+ seconds to load, and it would commonly crash.
Admittedly I haven't used Android full time (I have some Pixels for testing) since the Nexus days, but they pushed me back to iPhone when they released an update that completely destroyed the performance on my Nexus 7. Since then the growing Apple ecosystem makes it unlikely I'll change back. And that's fine. Phones are a solved problem at this point, it's really everything else where interesting work is happening.
A mess of messengers is a pain, but I'll take that over a messenger that only rich people can use, which is what you're signing up for with Apple.
A few of the things you mention sound pretty annoying, but none of them are annoying enough to make up for not being able to write code on any computer I like, and run it on mine or my friend's phone, without paying a regular subscription and submitting to a reviewer who can just say no for any reason.
The pay to write software thing is bullshit, but iPhone’s really aren’t more expensive than androids, per year.
The 5g SE (2022) is $429 (or at least $100 less if you shop carrier deals), and the CPU is current android flagship-grade.
You can get the 2020 model refurbished and unlocked at walmart.com for $70-$140. It probably has at least 2-3 more years of security updates, so the longevity is better than many new androids.
> but iPhone’s really aren’t more expensive than androids, per year.
> The 5g SE (2022) is $429
iPhone absolutely are more expensive than any other phone if you care about things other than the CPU/GPU performance.
The 5g SE has a tiny screen with archaic bezel design and still uses LCDs in an era where not giving you an OLED would be seen as a ripoff on the android market. It starts at 64gb of storage for this $429 (in France, it's actually 529 euros), my S20FE from a couple years ago which I bought at 400 euros on deals had 128gb. It has a very big, 120hz OLED screen and the finger print sensor works from underneath the screen.
For me, and many others, the phone is primarily a content consumption device. If the CPU is good enough that I don't see stutters all the time then it's good enough. I don't need my smartphone to be a laptop in the pocket. I do need a screen that I enjoy looking at and big enough that I can use it to read ebooks.
This in turns is heavily reflected in how many Apple users will splurge the big bucks to get the iPhone models that are comfortable to use despite their insane prices.
Right now, the cheapest phone Apple produces with a large screen is the iPhone 14 Plus at 969 euros.
There's a reason why the iPhone SE is the least popular of all Apple phones despite having far-more-than-good-enough hardware performance and longevity while being accessibly priced: it lacks what people actually wants out of their phone, Apple knows that and they keep the SE the way it is because they wouldn't want to cannibalize the sales of the expensive phones. If you look at any statistics, the SE is like a rounding error compared to the sales of the other iPhones.
See, a lot of people are excited about Android 14, but the S20FE is already on security update-only status... meanwhile the iPhone 13 of the same vintage just got a major OS upgrade.
And next year, when the S20FE won't even have security updates, the 13 will get another major upgrade. And probably another after that.
_
In fact, if you had bought a refurb $500 iPhone when the S20FE was announced (iPhone 11!), you'd still be getting into the new update the S20FE just missed out on.
That is how absurdly abysmal Android support it: you could have gotten a 2 year older phone and actually gained an upgrade cycle.
Also fun fact: the 2 year older iPhone 11 would also be faster than the S20 FE
I don't disagree with the update story being still a problem with Android, but iOS users tend to blow it up to a level higher than it actually is because they don't understand how Android is segmented.
You see, if Apple dropped support for your iPhone, you would never be able to ever get a browser upgrade again, since Safari's engine updates are tied to iOS itself.
Android doesn't do that. Very old phones past their prime and past the security updates support will still receive the latest Chrome with latest web standards support and security fixes for itself (though it won't stop other apps from being able to, say, exploit a privilege escalation vulnerability and other things of that vein).
You will continue to receive upgraded Messages etc.
Many of the APIs are updated independently too from the OS, through the Play Store, and because the developer community is aware of the OS update fragmentation, they also tend to target older SDKs for compatibility. So android phones are not becoming obsolete as fast as some Apple-exclusive users seem to believe from only being informed about "android doesn't get updates".
By the time my phone is truly done I will probably buy a new one because the battery will have worn out beyond my tolerance, as it always happens with these devices just as it happens on iPhones (I used to be on the iPhone camp when prices had not turned obscene, started with a 3g and ended with the 5s. No, I'm not paying $1k on a goddamn smartphone just because I prefer a bigger screen.).
To remark on not being able to get 14: it's sad, but I don't really miss it. I've never used webcams in my entire life, and the other OS level features aren't particularly important. IMHO, both iOS and Android have become mature as OSes and most of what people care about is in the app ecosystem, not what comes out of the factory.
I've launched AOSP devices professionally, so I understand how Android is segmented better than most...
You spent way too many words trying to downplay some pretty simple facts: Android OS updates are what contain most headline features lay people recognize.
GPS/Mainline cover things that are implementation details as far as they know, and don't cover the binary blobs which are the biggest reason why losing security updates in a year is going to mean the S20FE is forever an insecure device, regardless of what Mainline can deliver or what going with a custom rom does.
_
Also Android is extremely far from mature, things like Project Mainline show we haven't even settled on how far Google gets to sink the closed sourced claws of their GPS into the core of it.
I mean you've got Android 14 finally adding the APIs to properly support scrolling on high FPS displays. Android had 120hz displays years before Apple and somehow manages to screw up these basic cases because they have no unified product vision to speak of.
Maybe Android will be "mature" once Google is done with their iOS-ization of AOSP driven by crappy vendors, but for now the updates are extremely meaningful.
1) iPhone 13 is 09/2021; Galaxy S20 FE is 09/2020. One year older device.
2) System updates do not mean the same on Android and iOS. On Android, all the apps are going to be updated still. Browser, mail, chat, maps are not hostages to system update. Conversely, security-only updates on Android are perfectly fine. Most users would not see difference between major releases anyway.
You're instead referring to Google Play Services alternatives, which get updated but also don't represent the headline features that get announced with new Android releases.
> Most users would not see difference between major releases anyway
Absurd take when Google spends literal millions marketing the new features native to Android releases (not app releases, Android releases)
And in less than a year the binary blobs running half the phone in your pocket will no longer get updated, so it elevates from being a feature issue to being a security issue.
> You're instead referring to Google Play Services alternatives, which get updated but also don't represent the headline features that get announced with new Android releases.
You're assuming 1) that people need a phone that fancy in the first place, and 2) that a phone's life is up once it stops receiving updates.
The Moto G6, and that stopped receiving updates long ago, and was released in 2018 for about $100. I don't need much power, so I could easily get by with such an old, underpowered phone. I did for a while, but I did switch away because I was more phone-reliant at the time, and so an upgrade was needed. And I find the freedom of being able to install anything just from APKs, set another browser as my default, etc. as a huge value-add for Android.
And yeah, the iPhone has more security updates, but that doesn't really matter to me. I only install reputable, and mostly open source, apps on my phone so I'm not really concerned about security.
So in terms of value: there's the 2020 iPhone SE, with, say, 3 years left, for $120–$40 per year counting just the remaining years and using the current price at Walmart, or $300–$50 per year, assuming MSRP, a carrier discount of $100, and 6 years total. And the Moto G6, with just over of 5 years of life so far, and more value to me due to both the relative freedom of Android, and the fact that I'm used to and prefer Android, for $100–$20 per year. The choice seems obvious to me, for my purposes, but I can absolutely see why an iPhone is better for some people.
By the way, fun fact: the Moto G6 has FM radio built-in!
P.S. also, there's no way I'd risk becoming one of those arseholes that tries to make their whole family get iPhones so they can FaceTime, just because they can't figure out how to download another damn video calling app, despite being able to download all other apps just fine. Yes I'm looking at you, mother's half of my extended family.
> And yeah, the iPhone has more security updates, but that doesn't really matter to me. I only install reputable, and mostly open source, apps on my phone so I'm not really concerned about security.
As much as I’d love this to be a valid stance if you use the internet then you need to be keeping up with security updates. Recently there was a bug in the open source decoder for webp images, it impacted basically every device, and was being exploited in the wild via nothing but displaying an image.
... and libwebp gets statically linked into Chrome which gets updated via the Play Store even on Android devices that "don't receive security updates anymore".
I have two phones that do the exact same things for me - iPhone 14 and Pixel 7a. Screens are almost the same size. Battery life is very similar. Both are fast for the things I use them for.
iPhones typically get OS upgrades for 5 years. Pixel gets 3 years.
My iPhone cost £849 including tax, which is £170 p.a. The Pixel was £449, working out to £150 p.a. So the Pixel is £20 cheaper per year.
iPhone SE has a much smaller screen, too small to read comfortably. I don't trust refurbished phones. So these options don't matter to me. Far cheaper Android options don't matter to me either because they typically have huge quality and security issues.
For people who just keep using their phone for 5 years no matter what, Pixel would be £80 cheaper, but I think performance would no longer be on par in the later years given that the iPhone starts out with higher specs.
I'm not saying this comparison is any more correct than yours. My point is that whether or not iPhone or Android phones are cheaper depends on how people use their phones. There is no one true answer to which one is cheaper.
When you're poor you don't have the luxury of worrying about security updates, and your credit probably isn't good enough for those carrier deals. You use a phone until the battery explodes, and on that measure even the cheapest of new phones is going to outlast a refurbished anything.
Well, it sounds like you mostly have issues with Google (and Google devices).
I'm pretty happy with my Fairphone 4 on LineageOS, personally. Murena also sells some degoogled out-of-the-box with /e/. I also like having root adb access on these systems (which btw, gives you access to the sqlite sms database). Screen mirroring via DP alt mode over USB-C works out-of-the-box and you can enable Android's "desktop mode", though it's rather barebones and clearly experimental. Plus, Fairphone supports their phone for a long time, they are easy to repair, they can run mainline kernels (postmarketOS...), etc. Of course, any Android phone still depends on Google for the OS.
I'm with you on a lot of complaints regarding Google, though switching to Apple would feel like trading one evil for another: I would absolutely not describe an Apple cellphone as "mine", nor "accessing your own device" sounds like something Apple provides.
A lot of your issues come from using a Google phone (Nexus/Pixel) rather than a different brand such as Samsung. Samsung can do external display mirror over USB, or let you use your external USB monitor as a second display (wirelessly too). It has no messaging bullshit.
That said I have a Fold 4. iPhone aren't doing folding phones atm and they lock down the ecosystem so much I have zero interest.
Exactly my thoughts. The OP just seemed like they want an iPhone because they like it, not because of the excuses they posted. They are all solvable by simply picking a phone from another brand (except maybe for the messaging thing, I didn't quite understand that one).
The SafetyNet Fix module. I believe kdrag0n is the original author, but there's a popular fork on GitHub with some fixes - if you Google it you should be able to find it.
It tricks apps into thinking your phone doesn't support hardware key attestation, forcing it to fall back to basic software attestation which can easily be spoofed.
Been using it on my OnePlus 7 Pro and aside from when I had to switch to the fork, I haven't had any times where SafetyNet has stopped passing.
Only fragile ones, and those will only work until google finally flips the switch and their servers stop validating anything less than true hardware-backed attestation.
You can't patch that out when it comes to hardware attestation. The entire bootchain is authenticated and you can't spoof it because the authentication mechanism and private key are is in the on-silicon enclave. Anything that's not authorized will fail attestation. You can't patch it out because it's an allowlist. Anything less than official signed boot + OS + apps + configuration + known good hardware private key will fail.
It's about as easy as it would be for an ISP to inject code into an HTTPS page.
The only reason anything works is because Google attestation servers still return a green light for evaluationType=BASIC. Once old devices become rare enough they'll only return a positive attestation for evaluationType=HARDWARE_BACKED.
Go find try and find a single instance of anyone achieving HARDWARE_BACKED with less than a fully stock device.
They are none. No amount of Magisk magic will make it work because it's all taken out of software's hands. Bypasses at that point look like electron microscopes and micro-electronics cleanrooms.
I've been on Google phones since the first nexus, with the exception of a single Samsung before swearing them off due to bloatware and awful performance degradation, despite being twice the price of the nexus, and am finally tempted to switch to an iPhone as well.
The main things drawing me to the iPhone are:
Live voicemail - don't have to deal with my carriers awful voicemail anymore, and it's way more practical than Android's Call Screen, because the Call Screen prompt is way too tedious to sit through, unprofessional if you're being called for an interview, and they know you're there. Live voicemail I can see it, optionally answer in the middle, it gets saved after, and the other party has no idea if I'm available or not.
Apple Photo Memories - My girlfriend shows me them on her iPhone, they're cohesive and actually really enjoyable to watch, they look like they were professionally done, like what you'd pay someone to make or see an social media influencer post. Google Photo Memories look like random assortments of photos in a powerpoint presentation you made back when you were only 8.
The apple watch is also better than the google watch.
I still have to see what features I care about that I'll be losing before making the switch though. I still remember having to fight my iPod where the internal music db would always get corrupted and need to reset because I used MediaMonkey instead of iTunes since it was faster and had better transcoding and library management features.
I've been using my Samsung Galaxy S21 for two years now and don't notice any performance degradation. I feel that the bloatware you're speaking of is also minimal. It has far more features than an iPhone, e. g. Samsung DeX, which is actually quite interesting. The photo gallery app is good, I think you'd like its story feature. It has object recognition and creates small stories from pics of people, pets and certain days on which you took a few more pictures. I also like their new AI photo editor (Galaxy Enhance X). It gave me good results on overexposed pictures without me having to manually fumble around. The regular photo editor with its object eraser also comes in handy.
If possible I suggest you try one of the new Samsung Galaxy S devices.
More than decade ago, in 2011, my father had Galaxy S2 and I had Galaxy Nexus. Hardware-wise, they were comparable (Galaxy Nexus was something like Galaxy S2.1), but the former run TouchWiz and the latter vanilla Android. The latter was much more snappy, the former's performance did degrade.
Now fast-forward almost a decode. I'm using Galaxy S10 since its introduction in 2019. TouchWiz is nowhere to be found. Samsung uses OneUI nowadays, which is actually pretty cool, and I prefer it to vanilla Android. Basically, I have as good experience with it, as you described.
Caveat that you have to have a device running macOS to do this:
If you set up your Apple account to use iCloud to sync your messages, you will end up with your iMessage and text messages in the Messages app on your macOS computer. At that point the message content is easily retrieved from files on disk, should you choose to do so.
Of course you can accesss your stuff on it, just back it up with android debbugger (adb).
If you're annoyed with the search box you can disable it or flash GrapheneOS or LineageOS.
My partner is always having a hard time transferring her iPhone photos to her desktop. Finally gave up and bought iCloud storage. Apple has better integration with their peripherals though. No stupid app to use the heaphones, create other accounts etc. Their Apple Air Pods setup is just integrated in the OS. I have Sonys and absolutely hate their 4.7 star rated app, nags you to create an account and give it access to the camera in order to optimize your sound.
I remember that I was able to mirror my phone to a TV with a USB cable. It's been years since I did it so I don't know if something changed. I don't know if I ever connected my current phone. I had phones from Samsung and Sony, never Google. Maybe they have different USB ports.
I have to sympathize with their post a bit. There's no reason for it to be "a little bit of work". Google is not some indie company.
As much as I enjoy tinkering and having control over my device, sometimes I want things to just work. The Steam Deck and SteamOS are the what I consider the gold standard for this: SteamOS is very beginner friendly, but allows power users to access the Desktop mode and unlock its full potential.
I've talked about this before on HN [1]. I cannot backup my Minecraft worlds on Android 13 without paying Mojang $4 for their server to act as an intermediary to transfer files, whereas people in the "walled garden" of iOS can access it via a file manager app or plug their phone into a computer and backup the worlds.
It's a company deciding what they will and what they will not do.
If you want an all encompassing authoritarian provider, you have an option. But demanding that of everyone narrows the periphery and extinguishes the creative sparks of discovery
Vendors should embrace diversity and not line up in compliance with whoever the perceived market leader is.
This is called Error reinforcement: when a tech company makes a poor decision and their competitors copy them out of fear because they don't know it's a mistake.
The original firm sees the copycat work as evidence they were right.
See Google/Apple maps, iPhone/Android, Google/Bing etc
This leads to service degradation, feature reduction, persumptive interfaces, poor defaults, hostile interfaces, and disliked products with no alternatives because everybody is racing to clone each other feature for feature assuming that everybody else knows what they're doing
Any presumed market diversity from competition is then traded in for compliance, uniformity and conformity.
So go buy your Apple device. Expecting everyone to be like Apple (or anyone else) is offensive to the craft of innovation
Are you sure you've responded to the correct comment? Or did you misunderstand my comment?
No where did I say I want an "all encompassing authoritarian provider" or to "narrow the periphery and extinguish the creative sparks of discovery". All I asked for is my device to "just work" when I want it to. You can have have your cake and eat it as well - it is possible to be friendly towards both novice and pro users, as I demonstrated with the Steam Deck example (whether they will continue this, is a separate discussion). Things can "just work" without a company deciding what's best for me.
I used to be able to plug my phone into my laptop and copy my Minecraft files. I can't do that any more.
I own the device. I decide what I want to do with it.
I myself have faced the brunt of "error reinforcement": my phone doesn't have expandable storage, lacks a headphone jack and didn't come with a charger in the box, - all to inconvenience me and raise Google's bottom line.
If you're up for constructive criticism, please don't come off so aggressive.
Apple took the first step on almost all those feature killing things you listed and then to "keep up with the industry", the android vendors followed suit.
Products that "just work" often in practice get that attribute by only working in a proscribed way and then flat out failing in others.
Your fail case is inevitably because the just work philosophy was followed for some other imagined use case so being a tool was replaced with being an appliance.
When you try to meet the user too far you inherently compromise functionality and adaptability in exchange for narrowed convenience.
You need to take things away and remove decision points from the user in order to get to a just work state.
Then there's an actual group of users that reinforces this and classifies such things are progress.
I care a lot about a productive meaningful future and I want to push things in the right directions
Thing is, power users are a vocal minority in his industry. People like our families are the majority, and I don't want them to have to deal with quirks or troubles, but I also don't want an oligopoly controlling the space and compromising innovation, privacy, etc. in the name of "convenience" (profit).
The problem here is whether someone wants a good knife or a bunch of specialized knife like devices like cheese slicers for specialized knife functions.
The problem in technology is we presume it's Either the mandolin Or the knife and not both.
The fleeting elegance in the craft of engineering tech products is in empowering all these modalities and not the endemic narrowcasting we see plaguing the industry.
As you said, this is only a Pixel problem. Speaking of, have you tried Samsung Dex?
> Accessing your own device
Seriously? Apple basically invented the idea of not giving you full access to your "own" device. At least there's a file explorer now...
> Messaging that actually makes sense
Messaging under Apple is literally just messaging on Android plus iMessage. You still have SMS, like 50 common third-party messengers, all the Google ones, but then also this Apple-only thing. How is this better? If you want a better chat experience, look at Blackberry (yes, really!).
You do have a point regarding privacy though, as most Android devices ship with at least Google's spyware, if not also their own...
1 - HDMI cable does the trick
2 - This until recently was not a problem if you had signal.
3 - Syncthing. it costs $0.
4 - iMessage ?
You have to pick your poison, but a phone that actively forces you to update AND also blocks 3rd party apps from running AND forces proprietary cables that no other consumer device uses... seems like a nonstarter for me.
Why do you need to mirror your phone?
Why do you want to access your messages? For what purpose?
What do you need to backup besides (maybe) photos? Which is easy (drag and drop) anyway.
Sounds more like you have some kind of device dependency beyond normality.
I think when you say "why do you need to ____?" you think you're saying "what are you trying to do, and maybe there's another way to accomplish that", but what everyone hears is "you're right".
And for the record, "because it's their device, not Google's" should be as good a reason as any.
Actually I'm just wondering specifically why the need to do any of those things. Isn't the phone just fine as a standalone thing? I mean other than maybe exporting photos, videos, or sound to a more powerful and easier to use platform (such as a desktop)...
This is like asking, "why do you need a touch screen or internet on a phone in the first place? Neither are needed to make phone calls. Isn't a phone just fine as a standalone thing?"
It's not 2005 anymore, a phone has all the computing power that most people need. In fact, most laptops are just phone boards these days. It's completely reasonable to ask that your hardware not be artificially limited by the software it's running so they can sell you a separate device that does the rest of what you need.
In a perfect world, my phone is a supercomputer capable of doing everything I'll ever want in a fraction of a second. And the thing standing between my current phone and a perfect phone shouldn't be my insistence on having a separate giant desktop taking up more space than is necessary.
I do the NYT crossword on my iPhone. Not uncommonly, someone will start kibitzing over my shoulder. If there's a TV nearby, I throw the app up there, either with AirPlay or an HDMI cable. Because it's an iPhone, the app can detect that it's mirrored to a big screen and give an alternate layout for that screen; the NYT crossword app does an average job of this, giving a layout optimized for large 16:9 landscape displays. Makes two people (or ten) working on a crossword together much more pleasant.
I'm not sure if this is a weird use case or not, but given the number of iPhone apps that I have both used and written that have special handling for TV mirroring to improve user experience... it can't be /that/ rare.
I sometimes have to give presentations at a community center or church or some random venue and I just need to plug in to their TV/projector. Got my slides all ready to go. Is that asking so much?
I've been using the Camo app for over a year. Works excellent. Even supports viewing the camera over wifi. No cable necessary. It is free for a basic account. Find it here: https://reincubate.com/camo/
I liked it too, paid for it for a few months. But every so often it would start lagging by about 1000ms. Tthe only solution was to reinstall the Windows drivers. This happened with both iPhone and Android devices, and more than once, so I cancelled when they didn't have a better solution.
Droidcam is the first app in my life I paid money for. I'm not happy with it. On Linux in particular, I have to reinstall it almost every time I update the system. Every so often it doesn't connect on first attempt- so I close it, restart and then it inexplicably starts working. I would probably forgive a more serious bug, but this is just annoying and silly.
I started with Droidcam during the pandemic and switched to Iriun. Currently using it with an old iPhone SE over USB, but also used with Huawei P20 Pro. Not many features, but just works.
I used iriun a lot, a problem that I have with it is how much my Samsung phone heats up when using a higher resolution. Probably a Samsung/Android problem more than Iriun. I would love to have a phone quality camera in a regular USB webcam.
If you're willing to wait 6 months you can get the pixel 6a for ~$90 by signing up for a new line at metro by t-mobile, using the new line discount to purchase a pixel 6a while signing up (phone costs $50, first month of service costs $40) and then never renewing for a 2nd month. After 6 months, the phone should automatically carrier unlock according to a very obnoxious deal website that I'm not going to link here because of how obnoxious that site is. Make sure you activate the phone to start the 6-month timer!
AFAIK with the Nokia N900 this was possible in 2009 using gstreamer. I never actually used it to create a video device but I assume that the v4l2sink was already a thing back then. I did use it quite a few times for streaming to remote windows and OpenCV.
Only good phone I ever had. I wish things were as easy on Android devices, but somehow they almost never are.
I'd really love devices & software that try to emphasize possibility & malleability. The modern consumer systems are rigid & huge on guard rails, making sure the user has a straightforward experience.
That's a hard task, worth of respect too. But it feels like this hardline conservative outlook for software has utterly dominated what's gotten built for a long time now, with less and less computing that is interested willing or able to give power users solid ground & footing. Tech keeps increasing the distance, keeps becoming more esoteric, ironically because it keeps losing on-roads to becoming an expert or explorer if you're interested in going further.
> We don’t know how Google plans on mitigating heat issues or how it deals with the issue of potentially damaging a camera that uses optical image stabilization
I think sun sitting the phone, while its doing nothing else but charging is enough to cause concern... guess we'll see.
It's easy enough (for Google devs) to allow the battery to drop to lower charge, and only trickle-charge it. Shut down non-essential apps to keep CPU heat output to a minimum. That might help a little. Not much you can do about the sun though - maybe a liquid-cooling case that holds the phone in place?
At some point the phone shuts itself down when it gets too hot. Not ideal to use it as a dashcam, especially if it's also doing navigation and charging.
Yep, high-resolution recording while charging, streaming music, and displaying a map will quickly exceed the thermal constraints of any phone. I guess a MagSafe holder with mini sunshade and active cooling fan could help?
It would be fine for short drives, but anything longer than 10 or 15 minutes needs to have smarter handling of these larger video files, which would quickly swamp your storage. Think about using it everyday for a 30 minute commute back and forth.
This is a nice-to-have feature, but most people are going to want to be able to have their phone at hand still while on Zoom. But then again, I suppose most people have an extra phone.
What do you do with your phone on zoom? I’m not saying it’s wrong or weird. I just don’t do it and I’m curious about how other people use software/computers.
This is the sort of thing android should lean into heavily to differentiate itself from apple as I can't see apple supporting this kind of thing outside of their écosystème.
There's already a number of apps in the iOS and android ecosystems that allow this - as far as I can tell this is moving that to default in the OS rather than a third party app.
Yes. If you have an iPhone and a Mac it will just show up as a webcam device automatically.
I have found it quite useful when joining a zoom call with a group of people in a breakout room. Prop up your phone somewhere and it works like a conference room camera.
> * shortcut from off to recording video, immediately
Most Android phones will let you open the camera app with a double tap of the power button when locked, then you have to start recording manually, so it's a two step process. Sony has a dedicated camera button that opens the camera and can be configured to either take a photo or start recording immediately: https://sony-xperia-l.xphonehelp.com/en-us/camera/using-the-... (under Quick launch)
> * stop charging battery at 80% setting (no heuristics, AI, predictive BS).
Sony has that under their Battery care, you can set a custom stop percentage.
Rather than something generic, here's a scenario with made-up numbers to better explain the goal:
Charging from 80% to 100% puts more strain on the battery than charging from 60% to 80%, even though it's an addition of 20% each time.
So let's say you use about 40% of your battery daily, and charge from 60% to 100% every day, and that drops your total capacity by 10% each year. You'll have 6 years before your battery won't last a whole day.
If instead that +40% charge was going between 40% and 80%, the reduced strain might mean you only lose 5% of the total capacity each year. That would get you 8 years before your battery won't last a whole day.
Getting your battery to last longer like this also means that a year or two in, if there's a day you expect to need the full capacity, you can just turn off the limit for that day and your battery will last longer than it would have if you never limited it.
charging the phone all the way up to 100% is less efficient than just charging it to say 80&, it's not linear. That reduction in efficiency creates heat, while your phone is also already working really hard navigating, playing music, blasting the screen at high brightness (assuming you're driving at daytime). All the heat can cause your phone to start performance throttling and could cause it to overheat and shut-down, but it will also hurt your batteries longevity
I guess there are too many apps that already provide this feature, with that being said, webcam feature is only available when you plugin the usb cable into computer.
To refresh your memory, android supported external gps receivers since forever, as it also did with embedding geolocation into photos.
Iphone 3g, for example, did not support first, and supported second in an awful limited way.
I can find many more examples, but last iphone I owned was 3g.
The iPhone 3G was released in July 2008, 15 years ago.
The first EVER Android phone release was the Dream, which came out in September 2008. It had very little to do with today's Android. I was there. I know.
I've been quite disappointed trying the other thing, trying to get my Android phone to use a webcam. It seems to work in like 1/4 apps I try. It doesn't work in Chrome.
It's just so frustrating because this is such a solved problem for Linux / FreeDesktop.
If it’s anything like iphone’s continuity thing then I hope it doesn’t suck as much. It’s hard to use and the thing will constantly get turned on and off
They've been busy shoving useless software into the device to bloat it enough that we all have to keep buying faster devices every 2 years. Unplanned bloatselescence
Apple already did introduce this for iOS 1-2 years ago (assuming you have an iPhone and a Mac). I know because I’ve activated the feature by accident a few times.
I don't know why you're getting downvoted, this is a very good question that makes no sense at first.
USB-C is a complex standard, but basically, just because your connector is USB-C, doesn't guarantee what can actually go over those wires. First you have to have the connector; then your device needs to have a chipset that is capable of specific processing and protocols; and then it needs to actually implement those protocols with other things on the device. So your USB-C connector might only support USB 2.0, or 3.0, or 3.1, or 3.2, or 3.2 Gen1x2, or 3.2 Gen2x1, or 3.2 Gen2x2, and possibly PowerDelivery, and possibly video, and possibly audio, and possibly mass storage, and possibly ethernet, and possibly basically whatever feature you want.
So you have to actually look up the specs of the device you have to find out what it will actually allow you to do over that USB-C cable. I bought a USB-C phone years ago only to find out it supported virtually nothing besides USB 3.0 file transfers, and a dumb charging standard proprietary to that one vendor.
Samsung Galaxy phones do a ton of stuff over USB-C, including video out, and even DeX, where you can use the phone as a laptop.
My Oneplus 7T seems to have it but never found a use for it (its just basic screen mirroring). I think Samsung is the only one with a docking UI system (DEX) though
Huawei also has it. I used to have a P30 Pro, upgraded to a Pixel 7 Pro just now, and I was actually surprised to find it doesn't support this.
It's quite useful sometimes when I'm in a satellite office and I didn't bring a laptop, I can just plug my phone into one of the guest workplace docks and it's quite productive. Eagerly waiting for Android 14 to bring this to the Pixel.
Most Android phones don't have a good USB controller though, as it's not considered a priority. Without it you'll be restricted to the blocky MJPEG garbage with terribly downsampled chroma squeezed through the USB 2.0 connection, and get the quality equivalent to a laptop webcam.
480mbps isn't enough for good quality video? It's 3.75x the maximum bitrate of a 4K Blu Ray. It should be fine. It can't be lossless, but it should be damn high quality.
To make a point, early webcams were USB 1.0, 12Mbps maximum, and it was enough for SD-quality video. USB 2.0 is 40x faster, which, assuming similar encoding (i.e. 20 year old tech), should be more than enough for 1080p video. It should be enough to best any laptop webcam, which are usually USB2 internally, but with worse optics and without the processing power of a smartphone behind it.
Using more fancy encoding, 4k should be no problem, even with a bit of headroom for on-device encoding and low latency.
>without the processing power of a smartphone behind it.
Considering the cheapest of desktop/laptop CPUs and iGPUs are more powerful than the best mobile CPUs and GPUs, this is a problem with the encoders and video chat software involved.
The best cellphone CPU’s easily beat cheap laptops’s from a few years ago that used low end 10th gen Intel chips. They don’t have the terminal budget to quite beat today’s chips, but it’s much closer than you might expect.
That might seem unfair, but many people replace their phones far more frequently than their computers.
I meant the chip between the builtin laptop webcam and its internal USB2 connection, which is typically a tiny, dedicated IC.
Smartphones cameras are not USB2, they are, I think, directly connected to a powerful SoC. The USB2 link is for sending data to the computer after the smartphone has processed it with all the might of its main processor.
That's absolutely true but I still very much doubt it's so bad that you would exceed 480mbps even on a decent resolution stream. We're not talking multiple orders of magnitude difference. Like... if all else fails just send every frame as a separate image with a fast encoder and you've still got 1.6 megabytes for each.
Steam in-home streaming needs to be realtime too, but is very playable, and most people aren't realistically getting 480mbps out of their wifi.
4k I don't know... 1080p no problem.
Don't most phones have dedicated hardware video encoders on their SoC now anyway?
And don't forget that 480 Mbps is the line rate. Practical throughput to a device will be substantially less, especially if other devices are on the bus.
Indeed Apple CarPlay is entirely based on sending H.264 video over IP over USB 2.0 and it's very good quality with low lag. It's absolutely good enough for webcam style usage.
I was going to say something about MJPEG, but it looks like UVC supports H.264 for a decade already. I guess I was confused by the cheap USB 2.0 webcams, they mostly use MJPEG and yes it's utter trash.
Still, good webcams use USB 3.0 and no chroma subsampling, to avoid recompression and enable certain tricks. I hope the YUV 4:4:4 mode will be supported in this, for those who have the speed and want chromakeys/non-blurry reds.
The video out isn't over USB2 data but over the high speed lines that are for USB3 and alternate mode.
It should be possible to have DisplayPort output but with USB2 data. In fact, we know it is possible because the iPhone 15 does it. It has USB2 data speeds but 4K Displayport.
If you can record 1 minute of video on your phone and the resulting file has a size of less than 2GB, then you're not even close to saturating USB 2.0's effective rate of ~42MB/s (=2.5GB/min) while streaming to a pc. My phone needs 483MB/min with those settings.
Depends on what you call webcam usage I guess, people have different needs. If you want any color grading or simply have deep shadows in the frame, MJPEG will make it look really bad. If you need chroma keying, it's extremely sensitive to compression artifacts and chroma resolution. MJPEG blockiness is going to be amplified (and if you have noise then blocks will be flickering), you'll be forced to wear a hat because it will cut your hair otherwise, and the edge of anything red (skintones, your shirt) will be smudged or terribly pixelated against the green screen. More expensive webcams like the Facecam Pro have the uncompressed or really high bitrate mode for this reason.
This might be implementation dependent. MJPEG per se is not bad as you make it out to be.
Example reviews: https://www.youtube.com/watch?v=daS5RHVAl2U and many more. They all boil down to the same thing: excellent device, even with MJPEG. Obviously it's more dependent on what you use as camera, than the encoding method.
I'm talking about webcams, which have more complex use cases than unprocessed game capture. MJPEG is necessary blocky and bad at low values (shadows); if you're going to chat with friends, streaming it directly, it's probably not going to be noticeable. But if you want to look good, any raw noise or any processing will amplify the compression artifacts, especially in the dark tones, and 4:2:0 will wreck the saturated reds against the opposite background.
Take a look at this OBS forums thread I found, which is a pretty good illustration. [1] This is the best key from a cheap MJPEG webcam I've ever seen, usually it's terrible and streamers have to wear hats. The edge quality in the final picture is still bad (especially hair), and that's with unholy amount of polishing the turd he did, sacrificing latency and probably holding his breath (figuratively) to not go outside of his finely tuned setup. Especially the temporal noise reduction. Check this frame out as well [2], and pay attention to his shirt and hand - the edge is terribly pixelated, which he points out as well. And that is probably the best you can do with the crappy compressed source.
This is the reason cameras like Facecam Pro exist at all. Uncompressed YUV with full chroma resolution makes it all far easier.
> Obviously it's more dependent on what you use as camera, than the encoding method.
You can get away with a cheap camera, if you're using it indoors with controlled lighting; you can't get away with bad compression if you want to process it.
>I'm talking about webcams, which have more complex use cases than unprocessed game capture.
I am too. The HDMI capture card makes a webcam out of a DSLR/DSLM. MJPEG is not the main issue when it comes to quality.
This is still implementation dependent. MJPEG can range from 0-100 in terms of JPEG compression. Also the C920 might also use H264 which would be even worse, also same 4:2:0 issue.
I just bought my wife a new (well, refurbished) ThinkPad. I went through its BIOS menus to... well, just in case there's anything weird. Also, you know, to disable "secure" boot.
And, dear lord... there's so much Intel <three-letter-acronym> stuff that simply shouldn't be there, and some of it is even impossible to disable :( All sorts of non-consensual tracking marketed as "anti-theft" or "IT remote service support". And that's on a ThinkPad, which, at least in my memory, used to be the friendliest brand for Linux among laptops...
Anyways, back to Android. Well, last thing I want it to be is a Web cam. There's even an idiom in English "butt-dialing" that stands for accidentally calling someone w/o the caller being aware of them calling them. But, with a Web cam, and the glorious Web security, and proprietary drivers... now you'll have a chance to... broadcast butt-dial? That doesn't sound as snappy though. Let's wait for the first victim, I guess, and see how they call it.
It doesn't mean a Webcam in the sense of a camera that broadcasts to the internet, it means a USB camera you can plug into your PC (or any other device that supports standard USB cameras (UVC protocol).
Do you never plug your phone into a PC for a reason other than wanting to use it as a Web cam? Laptop users literally tape over the Web cam to prevent accidental / malicious uses of that device. Now they'd have to tape over the phone camera every time it's connected to a PC? Seriously?
If you are worried enough to cover your PC camera all the time, why aren't you worried enough to cover your phone camera all the time anyway? And are you OK to connect your phone to your potentially compromised PC with a USB cable in non-camera mode? That seems just as bad or worse.
I expect that on most phones you will have to select USB camera mode for it to work (and you'll have to tell it if you want the front or back camera), and it will probably tell you that it's working on the screen.
>And, dear lord... there's so much Intel <three-letter-acronym> stuff that simply shouldn't be there, and some of it is even impossible to disable :( All sorts of non-consensual tracking marketed as "anti-theft" or "IT remote service support". And that's on a ThinkPad, which, at least in my memory, used to be the friendliest brand for Linux among laptops...
How exactly are you gonna butt-dial with a USB webcam? Article says this feature requires a USB cable and has nothing to do with "glorious Web security".
BTW I highly doubt that toggling settings in your BIOS is going to stop this supposed non-consensual tracking. But hey, if the placebo helps you feel better
There were probably hundreds of security breaches related to Web cams. These are the devices with very shady reputation. This is why you'll see laptop users taping over them. Now every time you plug your phone into a PC you have to start worrying about your phone being used to spy on you?
> BTW I highly doubt that toggling settings in your BIOS is going to stop this supposed non-consensual tracking.
Some are known to be impossible to stop. Some can be stopped. There are, unfortunately many of those. "Anti-theft" thing can be completely disabled for example. The "IT remote support" thing cannot, but can be configured to be less malicious (somewhat, not really, but still). It's not magic what they do. It's just (intentionally) poorly documented (and poorly implemented) stuff. But there are some enthusiastic people who try to discover what this stuff is actually doing.
So, it's a fight that never ends. Eventually, enthusiasts will discover more of this stuff, take Intel to court and make them undo / allow to disable this. And then Intel will produce chips with more malicious stuff but rebranded and so on.
I happen to work for another big h/w manufacturer, so... it's business as usual.
If your threat model includes Intel IME, why did you buy an Intel laptop? There are plenty of AMD laptops available today, some are even available as a Thinkpad.
Here's a little script for streaming through your camera on obs:
get-adb-devices-list() { adb devices | grep -v "List of devices attached" | grep -v "daemon" | grep -v "^$" | grep -c . }
echo "device count: $(get-adb-devices-list)" while [ "$(get-adb-devices-list)" -eq 0 ]; do echo "Waiting for the device..." sleep 0.5 done
IP_ADDRESS=$(sudo adb shell ip addr show wlan0 | grep "192.168.." | awk -F ' ' '{print $2}' | cut -d '/' -f1)
connect-adb-tcp () { sleep 1 echo "Connect to the device...$IP_ADDRESS" && \ adb tcpip 5555 && \ sudo adb connect "$IP_ADDRESS" }
connect-adb-tcp && \ v4l2-ctl --list-devices && \ scrcpy -e --v4l2-sink=/dev/video0 --lock-video-orientation=1 -n -N &> ./log & obs