Well, it is quite hard for third-party developer to figure out how to work with the driver because of the large number of handsets available around the market and each variant has it's own drivers even if they are being powered by the same SoC. Those drivers are just out of tree and too hard to be put back into mainline without efforts.
They won't release the code because they don't think it's profitable. When people could update their devices and keep them longer, manufacturers will have a reduction on sales on their phones. It's all about money.
Yes, but even if they have common specs, the source code are still varies because they are being modified by "Google first, then SoC OEM, then manufacturer" stack.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hmm but would it be that hard to monitor how it operates and figure out drivers?
Also once there is momentum, OEMs might release drivers if they see the scope. Currently they aren’t doing just because there is no action.
There are many website where ARM specs are made open by individual contributors.
Well, it is quite hard for third-party developer to figure out how to work with the driver because of the large number of handsets available around the market and each variant has it's own drivers even if they are being powered by the same SoC. Those drivers are just out of tree and too hard to be put back into mainline without efforts.
They won't release the code because they don't think it's profitable. When people could update their devices and keep them longer, manufacturers will have a reduction on sales on their phones. It's all about money.
Yes, but even if they have common specs, the source code are still varies because they are being modified by "Google first, then SoC OEM, then manufacturer" stack.