HMD launched its Nokia 5.1 phone globally back at the end of May. As usual, developers want to view the kernel source code to add ROMs or modify the phone. Allowing developer modification leads to a lack of device security maliciously exploitable software loopholes. HMD, releasing Nokia smartphones in Android, wants to assure buyers that its smartphones are secure. The Nokia 5.1 kernel source code has now gone live for developers who want to peak into the device.
Nokia 5.1 kernel source code: what is it?
What is the kernel source code? It refers to the software of the device, the software code responsible for memory management. The system protects kernel source code so that other programs can’t write over it. At the same time, to alter the kernel source code can enhance what is already a good experience. To utilize smartphone RAM, for example, someone can modify the code to speed up the device. Some have done this with Samsung Galaxy smartphones of the past, for example. Developers modify “Laggy” Touchwiz source code to make TouchWiz more fluid. Some said that the TouchWiz of old was too feature-rich and responsible for software lag.
In the case of the Nokia 5.1, HMD has released its kernel source code to the public. The Nokia 5.1 kernel source code includes all that is necessary in the phone’s memory management. There is some good in this for developers in that the Nokia 5.1 protects its memory, but tinkering with the phone could create some problems. Developers who’ve been at this a while are the only ones eligible to try these things.
The drawback to the Nokia 5.1 kernel source code
There is a downside for developers with the release of the Nokia 5.1 kernel source code: developers can’t tweak it or alter it right now. Currently, HMD won’t allow bootloader unlocking on its Nokia series.
Bootloader unlocking and HMD
What is bootloader unlocking? The bootloader of a smartphone lies in the phone’s boot partition. The boot partition allows the device to “reboot” or start up when one presses the power button. The bootloader tells the device what mode to boot in. If an OEM such as HMD approves of a locked bootloader, then the Nokia 5.1 will only boot in the OS HMD approves of. That is, HMD only approves of official Android system updates, so the Nokia 5.1 will only boot in Android 8.1 Oreo, for example, instead of Sailfish OS or Windows OS, or some other ROM system. HMD doesn’t allow bootloader unlocking, which means that developers cannot add ROMs and other personalized features to Nokia phones.
Why is HMD releasing the Nokia 5.1 kernel source code?
The release of the kernel source code is designed to encourage bootloader unlocking. HMD will not allow bootloader unlocking on the Nokia 5.1 and other phones. So the question becomes: why is HMD releasing the Nokia 5.1 kernel source code in the first place? The answer comes down to a mandatory requirement. HMD Global, like all other Android OEMs, is required to release their kernel source codes by GPL, or “General Public License” for Android kernels.
Android is an open-sourced platform, which means that developers and OEMs are always tweaking Android and making changes to it. The General Public License (GPL) rules state that any change made to Android, whether by smartphone manufacturer (HMD) or developer, must be shared publicly in a changelog for all to see. The GPL is designed to keep OEMs and developers accountable to others in a community where one can be challenged if something cannot be replicated or duplicated by the community. If someone makes modifications to Android software and does not report them publicly, then said changes are illegal and the developer or modifier in question is guilty of an illegal offense.
Since HMD wants to remain a legal company and, as such, eligible to sell Android-powered smartphones, then it must be willing to publish its Nokia 5.1 kernel source code for all to see. So, despite the fact that its phones are not developer-friendly, Nokia must still comply with official GPL rules to remain in good standing as an Android OEM.
Where does this leave developers?
Since the Nokia 5.1 kernel source code isn’t eligible for modification, where does this leave developers? It leaves them in the position they’ve always been in with HMD phones: imploring HMD Global to change its mind on bootloader unlocking in the future. Developers can always ask HMD to consider a change of heart on the subject.
As bleak as this sounds, there’s optimism beyond this. The Nokia 5.1 is a new phone, released about two months ago. There will come a day when the phone will no longer receive Android system updates and security patches. At that point, perhaps the security of the device won’t be such a top priority for HMD. When a device is too old for security patches, releasing it to the developer community for modification is all that remains for the device. My best advice to developers is to keep asking HMD, then ride out the newness of the Nokia 5.1 until it is too old to be secure. At that point, HMD may see no reason in releasing the source code without granting bootloader unlocking.
For now, though, developers will have to admire the kernel source code from afar with a “hands-off” approach.
You can view the Nokia 5.1 kernel source code here.
The post Nokia 5.1 kernel source code goes live appeared first on MySmartPrice.
from MySmartPrice https://ift.tt/2mKzhJs
No comments:
Post a Comment