|
|
|
|
|
by DanielHB
408 days ago
|
|
Just to add one more thing to your point, if embedded devs work really hard and make the code work faster/better all reward you get is an _even_ more underpowered chip for the next version. Hardware procurement is cut-throat, sometimes they have mandates to reduce component costs and the procurement people WILL reach them. Often procurement > product in the power dynamics so no matter how bad the product gets those people still do it because the software gets the blame for bad product, not procurement who forced a bad chip to be used. The infotainment is usually the #1 chip to be cut down because it is often the single most expensive electronics part in the system that can be "easily" swapped for a different part. |
|
For years now, Samsung has used a 'virtual proximity sensor' in everything but their premium stuff. Sensors like that are a few cents. Degrading the entire experience on the phone for a few cents cost savings. Say you do that for 25 components, saving 4 cents each. You've now saved $1 on a BoM of $100-$200, whilst making the whole experience of your product feel a lot worse.