Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
The silicon could go on for decades if both the modem and processor were fully documented hardware that the community can access and support in the Linux kernel.
I can run a secure and current form of Linux on 30+ year old hardware if I want to, because the hardware documentation was expected by everyone at the time even if some end users were oblivious to what this meant. The whole reason google pushes Android is because they provide a base Linux kernel that hardware manufacturers can easily slip their proprietary junk into without requiring them to add the kind of open source code needed for mainline kernel support by the community. This is the mechanism that depreciates your device. It is totally artificial and an end user exploitation by design.
It's usually not silicon on the PCB that fails, but the other electronic components (usually the capacitors) that fails first, and since they are surface mounted devices it's really difficult to solder them by hand.
There are no electrolytics in phones, and most newer phones don't even have tantalums. So long as there are no flexing stresses induced, which is nearly impossible with the way phones are constructed now, the all MLC capacitors construction has the potential to outlast any PC motherboard or laptop by a large margin.
The most critical issue is board connectors and moisture ingress. The USB-C connector or any other high pin density micro sized connector with a tiny pin pitch, and large electrical potential will fail from charge cycling and a resistance forming between pins. USB-C is particularly bad because reversing the connector doubles the number of pins on the board in a ridiculous amount of space. Just using a standard USB-C connector when ordering a prototype to be fabed at any common board house will double the price. The USB-C pin pitch is too tight for the most common fab process resolution.
The pin pitch only matters for high power application to prevent arcing, and that can also be resolved through the most modern USB-PD standard (See: USB-PD Extended Power Range, which can support up to 240w), and the electrical adjustment you have to make are all on the device side.
I don't know about the resistance forming between the pins, for low cycle applications the cheapest gold flash plating would easily last 10K plug cycles, and accounting for corrosion from hand sweat/oil/hand lotion, many companies favor going for thicker hard gold or platinum plating nowadays. (Rhodium is the absolute best, but it's just too expensive now to do at scale because they are used in catalytic converters for electric cars). USB-C lasts for many more cycles than the Micro-USB standards before it (You can read the 4 axis and wrenching test standards for mechanical testing on the USB spec) so I'm not sure what you are talking about here.
Lab tests rarely reflect the real world. I've seen several issues with Pixels that had an issue with PD failing due to moisture, corrosion, and a bridge developing at the connector.
Actually, no, the lab tests are standard with all products of all large companies, and they are usually conducted in extreme conditions, like 100% moisture at 80-90C oven for 48 hours and highly concentrated salt spray kind of extreme.
You bring up the example of Google Pixel, yeah, because it's Google, they are software people who think they can just cheap out on hardware and save a couple of cents by making it up in software. Look at the Nexus 5X and 6P, both devices had an absurd amount of quality control issues compared to the other products made by the manufacturers, and the only factor in common between them is Google.
Things change with time. The Pixel is now the most secure phone available due to its hardware encryption key verification system. It is the only phone that can run a verifiably secure bootloader and ROM on top of the same untrusted hardware situation found in all modern proprietary devices. Running a Pixel on Graphene OS is the most free and honestly liberating experience that has been available since the invention of capacitive touch technology made these handheld computers popular. The hardware build is on par with any similar device of the same price point, made in the same facilities as most devices.
Nice, good to know! And you were awesome in the Suicide Squad series
Thank you! Go see "Barbie" in theater too!