101–110 of 115 posts
Earlier quoted context omitted.
Option 1: DRM concerns (exploiting the "analog hole" on digital level, or HDCP restrictions - how deep is HDCP actually enforced in Android?) Option 2: Privacy (call recorders come to mind - unrelated: does anyone know of a working call recorder?)
I can record calls on iOS
Any dibs on what it's going to be named? An obvious one is "Oreo", but that's trademarked. "Oatmeal cookie" is the only O dessert I can think of that isn't.
Earlier quoted context omitted.
I liked my 5x, until the fingerprint recognition suddenly disappeared. Literally disappeared from all settings this week after a restart. Have to restore or something equally tedious.
I liked my 5X until it died from the bootloop issue 1mo out of warranty. Happened to at least two other co-workers and burned me enough to swear off Google phones. I'm not going to drop $700 on something that might last less than a year. OnePlus 3T got my money instead.
Earlier quoted context omitted.
Option 2 seems weird since I'm pretty sure Google Voice lets you record calls.
> Option 2 seems weird since I'm pretty sure Google Voice lets you record calls. Only inbound calls, not outbound, and that's by design - it's to ensure both parties consent (since there's no way for Google to know whether the call falls under one-party or two-party consent laws).
Earlier quoted context omitted.
> Option 2 seems weird since I'm pretty sure Google Voice lets you record calls. Only inbound calls, not outbound, and that's by design - it's to ensure both parties consent (since there's no way for Google to know whether the call falls under one-party or two-party consent laws).
What does inbound vs outbound have to do with consent?
It's not actually foolproof if you sit down and think about the edge cases, but that's the rationale behind it. It's a decision driven by the legal team, not the product or engineering ones.
Earlier quoted context omitted.
It can't help that Google hasn't released a phone comparable in spirit to the Galaxy Nexus, Nexus 4 and Nexus 5 phones. We're talking about phones that have a practical size, reasonably good specs, and a $300-$400 price tag. The Nexus 6 and 6P were impractically sized for many users. Even the 5X was too large. The Pixel's sizing is perhaps more tolerable, but the price tag is much too high. People hanging on to a Nex…
Also the Pixel updates are still held back by phone companies. If they cared about updates or security they would update their phones directly like Apple.
Earlier quoted context omitted.
Until then, I guess I'll continue targeting API 16. I started targeting API 19 (4.4, KitKat) over a year ago and have never looked back. That encompasses the vast bulk of Android users (>85%) and encompasses almost all of the significant developer improvements. Even using the absolute latest fun such as multiple windows is an absolute breeze from the development side, regardless of many users not supporting it yet. A…
> 85% you are ignoring your own effect on that. The fact that every developer moved to API 19+ is why most users gave up and spent another $400~600 on a new unneeded phone. And thanks to that, no manufacturer will ever support the latest release on a month old phone, because they now know people will just buy a new one.
At some point the market will settle as the pad market did, however right now the lack of pressure on vendors to support upgrades is also a reflection of a user base that is accustomed to constantly upgrading (better cameras, processors, storage, etc).
Earlier quoted context omitted.
And neither of the two seems to have a defined minimum list of services like Bluetooth has via its profiles. Seems Google is leaving it up to the app devs to come up with services, to expect a whole lot of silos to sprout, balkanizing the system. On that note, i seem to recall Mozilla tried to build something similar into their Firefox for Android at some point. But i can't relocate it now because i can't recall what…
FlyWeb? https://flyweb.github.io/
Earlier quoted context omitted.
What does inbound vs outbound have to do with consent?
When you start recording a call, it plays a brief message (e.g. "this call is now being recorded"). If it's an outbound call, you could start recording before the other person has actually picked up. If it's inbound, they "know" that the other person will hear the message. It's not actually foolproof if you sit down and think about the edge cases, but that's the rationale behind it. It's a decision driven by the lega…
Where would this meaningless feature-cripling make sense?
Earlier quoted context omitted.
When you start recording a call, it plays a brief message (e.g. "this call is now being recorded"). If it's an outbound call, you could start recording before the other person has actually picked up. If it's inbound, they "know" that the other person will hear the message. It's not actually foolproof if you sit down and think about the edge cases, but that's the rationale behind it. It's a decision driven by the lega…
Are there any major jurisdictions where this is actually a requirement? I was under the impression that a) it makes no sense, anyone could use an external recorder, and more importantly b) when you are talking with someone, you don't have an expectation of privacy from the person you are talking with? Where would this meaningless feature-cripling make sense?
For starters, twelve states in the US, including California: https://en.wikipedia.org/wiki/Telephone_recording_laws#Unite...
And telecom companies (Google acting in the role of a telecom company in this case) have certain responsibilities and liabilities if they facilitate illegal recordings.