Given the recent source code leaks of samsung devices, is development for the devices going to be easier?
Good question. Samsung devices haven't been very developer friendly. They even removed fastboot from all their devices!
I'm surprised they allow bootloader unlock at all.
Hopefully some genius can bring back fastboot to all Samsung devices!
Related
I don't know a whole lot about how android phones work so this is probably a stupid question.
If the android operation system code is open source and available for anyone to download what's stopping people from putting pure AOSP goodness on any given phone? Is it the kernel or bootloader or what?
Fe_Man said:
I don't know a whole lot about how android phones work so this is probably a stupid question.
If the android operation system code is open source and available for anyone to download what's stopping people from putting pure AOSP goodness on any given phone? Is it the kernel or bootloader or what?
Click to expand...
Click to collapse
from my understanding it has to be completely recoded or whatever to run on the hardware of a new phone, I think Cyanogen and crew just supply the base and framework to build on... but yes its out there for anyone to try and port, typically takes a team of devs with different specialties
blazing through on my VZ Droid Charge 4G
Kernel, RIL, and potentially a number of other things.
Just like drivers has to be ported for Linux on any PC (if the company didn't already code one for it), drivers has to be ported to a pure AOSP ROM from a TouchWiz source (which is still Android-based).
Most company-applied UIs to Android are deep in the system, therefore, you can't just take some files and put it into an AOSP ROM and have it magically work (known as kanging from another ROM), but you have to write in some stuff and build it specially for AOSP before it works.
Well as you all know, Nougat just landed officially on Newer Nexuses & AOSP Source code. and unfortunately N5 wasn't "good enough" to get official google support, but we'll soon get Nougat test on our beloved N5 thanks to great Dev community supporting it.
but i was wondering the Question that title says !
though AOSP Source code is uploaded for 7.0 release , there are some binaries that i believe closed source https://developers.google.com/android/nexus/drivers#hammerhead , and i think they should be updated as well to properly work any new update on device , that's why we see binary files updated by google till now for every official update.
but as N5 is now drop-out of Official support,so google surly will not provide updated binary patches, so does hardware company (Broadcom, Qualcomm , LG ) provides these patches after official support OR our Dev do some digging even though they are closed source and finally by trial & error they fix/updates these binaries ? if it's done by Devs individually, wouldn't everyone's thought for dealing with problem might be different which ends up making some ROMs more stable on one area and others in some different area !
( PS: Well you might got it from Question it self that i'm not a proper technical person in Android and even in that matter in coding , i'm just a guy who wonder these thing & tried to find answer on google but didn't get any satisfactory so end up asking in new thread instead on QA thread so that some one like me also get to know about it also , my previous device (Samsung i9070 ), having closed source CPU (NovaThor U8500) & CPU maker drifted from business , gave insane trouble to XDA devs while porting unofficial updates, so they fed-up and drifted away to new device within months which makes me more curious about this Question, hopefully i'll get proper answer from a Dev/Experienced Member )
jineshpatel30 said:
Well as you all know, Nougat just landed officially on Newer Nexuses & AOSP Source code. and unfortunately N5 wasn't "good enough" to get official google support, but we'll soon get Nougat test on our beloved N5 thanks to great Dev community supporting it.
but i was wondering the Question that title says !
though AOSP Source code is uploaded for 7.0 release , there are some binaries that i believe closed source https://developers.google.com/android/nexus/drivers#hammerhead , and i think they should be updated as well to properly work any new update on device , that's why we see binary files updated by google till now for every official update.
but as N5 is now drop-out of Official support,so google surly will not provide updated binary patches, so does hardware company (Broadcom, Qualcomm , LG ) provides these patches after official support OR our Dev do some digging even though they are closed source and finally by trial & error they fix/updates these binaries ? if it's done by Devs individually, wouldn't everyone's thought for dealing with problem might be different which ends up making some ROMs more stable on one area and others in some different area !
( PS: Well you might got it from Question it self that i'm not a proper technical person in Android and even in that matter in coding , i'm just a guy who wonder these thing & tried to find answer on google but didn't get any satisfactory so end up asking in new thread instead on QA thread so that some one like me also get to know about it also , my previous device (Samsung i9070 ), having closed source CPU (NovaThor U8500) & CPU maker drifted from business , gave insane trouble to XDA devs while porting unofficial updates, so they fed-up and drifted away to new device within months which makes me more curious about this Question, hopefully i'll get proper answer from a Dev/Experienced Member )
Click to expand...
Click to collapse
Short answer: they don't. Either they use old binaries that still work, or they use binaries from similar devices that are updated. For example, the nougat build available here for the nexus 5 has been built on old marshmallow binaries. Only the kernel can be modified since it's open source. There is not much we can do with closed source blobs unfortunately...
So guys finally realme allow us to unlock ( it will take longer time for unlocking as they will review your application than provide a ota which includes the fastboot binary) the bootloader of our realme 2 pro. They have also released the lite version of kernel source ( have not released full kernel source code!).
Guide for bootloader unlocking-
https://c.realme.com/in/post-details/1085078965883764736
Kernel source code- https://github.com/sirwhanq/Realme-2-Pro-8.1-kernel-source
Guys share your views here after unlocking the bootloader.
Sum1992 said:
So guys finally realme allow us to unlock ( it will take longer time for unlocking as they will review your application than provide a ota which includes the fastboot binary) the bootloader of our realme 2 pro. They have also released the lite version of kernel source ( have not released full kernel source code!).
Guide for bootloader unlocking-
https://c.realme.com/in/post-details/1085078965883764736
Kernel source code- https://github.com/sirwhanq/Realme-2-Pro-8.1-kernel-source
Click to expand...
Click to collapse
What Is Full Kernel Source Code...
Oxygen OS is even better than stock android so...?
Sandeep Jakkampudi said:
What Is Full Kernel Source Code...
Click to expand...
Click to collapse
It's is mandatory for creating device tree.
I wish they should have given an easy procedure and don't have to wait to unlock our bootloader. Also i dunno know when the development will start or whether we'll get to see any custom roms. Hope the developers will take interest in this phone.
I hope to see development soon
Sumesh Kharnotia said:
I wish they should have given an easy procedure and don't have to wait to unlock our bootloader. Also i dunno know when the development will start or whether we'll get to see any custom roms. Hope the developers will take interest in this phone.
Click to expand...
Click to collapse
Yeah the procedure is lengthy and complicated! Development will start after releases of full kernel source code.
How Much Time Taken For TWRP Recovery Build...
Sum1992 said:
It's is mandatory for creating device tree.
Click to expand...
Click to collapse
So without device tree no custom roms can be built.
Then what can be done with lite kernel source?
You are a old member.
Use search option before posting.
Already there are two threads for bootloader unlock and kernel sources news and guide. Don't create duplicate threads.
https://forum.xda-developers.com/realme-2-pro/how-to/realme-2-pro-bootloader-unlock-kernal-t3890093
https://forum.xda-developers.com/realme-2-pro/how-to/unlock-bootloader-application-tutorial-t3890183
cc: @the Doctor
tech mashido said:
You are a old member.
Use search option before posting.
Already there are two threads for bootloader unlock and kernel sources news and guide. Don't create duplicate threads.
https://forum.xda-developers.com/realme-2-pro/how-to/realme-2-pro-bootloader-unlock-kernal-t3890093
https://forum.xda-developers.com/realme-2-pro/how-to/unlock-bootloader-application-tutorial-t3890183
cc: @the Doctor
Click to expand...
Click to collapse
See my thread creation time and compare it with them!
Sum1992 said:
So guys finally realme allow us to unlock ( it will take longer time for unlocking as they will review your application than provide a ota which includes the fastboot binary) the bootloader of our realme 2 pro. They have also released the lite version of kernel source ( have not released full kernel source code!).
Guide for bootloader unlocking-
https://c.realme.com/in/post-details/1085078965883764736
Kernel source code- https://github.com/sirwhanq/Realme-2-Pro-8.1-kernel-source
Click to expand...
Click to collapse
Per the sticky titled "Development Forum Rules," you may not post in this section unless you are posting your own work on a ROM, kernel, recovery, or mod.
THREAD CLOSED
This means that developers are able to build and flash their own version of Android Pie on these devices.
The Open Devices program is our way to provide access and tools to build and test your custom software on a range of Sony devices. You can access all the resources you need through our Open Devices page on Developer World. We value our open source community and welcome you to participate in our projects via GitHub. Feel free to provide feedback on further resources you may need and where we can improve.
To get started on how to build AOSP for your device, use our build guides for instructions. Please note that this software is meant for developers and can be unstable due to its early stage. As part of our Open Devices program, the project for the Xperia 10 Plus are now available via GitHub where you can contribute and take part in our open source community.
Xperia 10 Plus GitHub project
Software binaries
Source: https://developer.sony.com/posts/xperia-10-and-xperia-10-plus-added-to-sonys-open-devices-program/
Great stuff
Does anyone know about this topic?
https://forum.xda-developers.com/mi-note-10/how-to/custom-development-t4018813
In short:there are same some efforts trying to get custom Roms but nothing groundbreaking yet.
I am working on the device tree right now to compile from source. Not ready yet and don't have the device in hand right now (should arrive soon) s.o. else is trying with treble images.
nchantmnt said:
https://forum.xda-developers.com/mi-note-10/how-to/custom-development-t4018813
In short:there are same some efforts trying to get custom Roms but nothing groundbreaking yet.
I am working on the device tree right now to compile from source. Not ready yet and don't have the device in hand right now (should arrive soon) s.o. else is trying with treble images.
Click to expand...
Click to collapse
I thought device tree is something that was used to be leaked from Xiaomi
As far as I can see there is no device tree published by xiaomi for tucana (our device)
Only thing we have rn is kernel source.
But we can create device tree by ourself. There are some basic guides online. Rest is compare with existing device trees for similar devices and copy&paste.
for now I have downloaded k20 device tree, removed everything k20-specific (e. G. Popup Camera) and adapt further files for our device(s)
When my handset arrives (should be today) I can start unlock procedure (should take some time to get the code AFAIK), then I can unlock bootloader, flash custom recovery and see if I can get my device to boot properly after flashing... Then comes troubleshooting.
Right now I am expecting maybe a halfway booting device or broken/missing functionality at best. But we will see
I hope soon
The more people help together the faster we can get some Roms ?
nchantmnt said:
The more people help together the faster we can get some Roms ?
Click to expand...
Click to collapse
If you have a group for this, would you pm?
No group yet, but you still get an pm
Anyone willing to collaborate is welcome to pm me as well
I have seen this Android 9 source code. Is it helpful?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss
I thought this model would have more support and after 4 months there is no Rom. I hope that now that the price is going down more people buy it and we have more community. Thank you for what you know and develop.
ignalop1983 said:
I have seen this Android 9 source code. Is it helpful?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss
I thought this model would have more support and after 4 months there is no Rom. I hope that now that the price is going down more people buy it and we have more community. Thank you for what you know and develop.
Click to expand...
Click to collapse
Just an incomplete kernel sources, I think is useless.
https://www.xda-developers.com/poss...-fcc-certified-snapdragon-730g-penta-cameras/
There will be a lite edition soon. The only difference on hardware is number of pixels.
If its ROM is same or almost the same to current models, we should get some progress around development.
Anything new?
UtkuAblak said:
Does anyone know about this topic?
Click to expand...
Click to collapse
Please look at the existing topics first, before opening another topic!
nchantmnt said:
As far as I can see there is no device tree published by xiaomi for tucana (our device)
Only thing we have rn is kernel source.
But we can create device tree by ourself. There are some basic guides online. Rest is compare with existing device trees for similar devices and copy&paste.
for now I have downloaded k20 device tree, removed everything k20-specific (e. G. Popup Camera) and adapt further files for our device(s)
When my handset arrives (should be today) I can start unlock procedure (should take some time to get the code AFAIK), then I can unlock bootloader, flash custom recovery and see if I can get my device to boot properly after flashing... Then comes troubleshooting.
Right now I am expecting maybe a halfway booting device or broken/missing functionality at best. But we will see
Click to expand...
Click to collapse
Well, just tell me if you need help.
Same here, I am very tempted by the Note 10 but I am waiting for an aosp rom as many people complained about the stock miui rom
Any news or update on this? Would love to buy a Mi Note 10 as their prices have gone down but with the lack of development I'm kind of leaning towards the 9t even tho I'm worried about that front camera as some have had issues. I suspect not many are developing for this device because of the high price. Hopefully whoever said something up there about the Note 10 lite gets custom ROMs going with more devs
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
nchantmnt said:
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
Click to expand...
Click to collapse
yes he is working on this device.
nchantmnt said:
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
Click to expand...
Click to collapse
Awesome news! Thanks :good:
I think the development goes now straight because we have MIUI Stable based on Android 10 now.
Good luck!