3 ms·
The Mediatek platforms, at least in their early days, were relatively open. The flash utility, which ran off a ROM in the SoC, meant that you could backup and r
by userbinator 4y ago
The Mediatek platforms, at least in their early days, were relatively open. The flash utility, which ran off a ROM in the SoC, meant that you could backup and restore the complete state of the device, effectively making them unbrickable. They didn't even seem to have any form of secure boot. Plenty of documentation (only available as leaked, but they didn't care much about stopping that) available if you knew where to look. Huge numbers of devices made with the same platform/reference design, and a correspondingly large (but unfortunately Chinese only) community around them. They were probably the closest to being a "standard Android device" for a while; of course, in the Western world they were mainly shunned due to their low cost and performance, while the lack of (user-hostile) security features was used as a further means of discouraging others away from them.
- commoner 4y agoUnfortunately, the current situation is quite different. MediaTek does not release kernel sources to the public, while Qualcomm does. https://www.xda-developers.com/mediatek-source-code-release-no-plans/ https://www.xda-developers.com/mediatek-source-code-release-... Device manufacturers are obligated to release kernel sources to end users to comply with GPLv2, but many do not, and Qualcomm's source code releases make supporting Snapdragon-based devices a little bit easier for ROM developers. It's a shame, since the Dimensity 9000 performs better than the Snapdragon 8 Gen 1.
- userbinator 4y agoMTK source code is(was?) available from the actual device manufacturer. I can't say for Qualcomm in particular but from what I've seen in the past, open-source releases are not at all a good substitute for the actual documentation, which tends to be heavily guarded.