It seems that some official ROMs (I think) are up for Open Source here
Link: https://www.lg.com/global/support/opensource/opensourceList?types=NAME&search=p769
Think it'd be possible to modify and create a lightweight distribution out of this? i.e. replace LG bloat with better optimized stuff etc
steventechno said:
It seems that some official ROMs (I think) are up for Open Source here
Link: https://www.lg.com/global/support/opensource/opensourceList?types=NAME&search=p769
Think it'd be possible to modify and create a lightweight distribution out of this? i.e. replace LG bloat with better optimized stuff etc
Click to expand...
Click to collapse
Only if you're bootloader is unlocked. The x-loader is not included in the source code as it's LK and LK is NOT open source.
Lamesauce
shinobisoft said:
Only if you're bootloader is unlocked. The x-loader is not included in the source code as it's LK and LK is NOT open source.
Click to expand...
Click to collapse
Gah that sucks too much. then what's the point of even releasing the source anyways?
Related
Android is based on linux!
Linux is all about open source!
If we cant have root acess, whats the point??
What did this have to do with closed source? + open source != root still, right?
confused abt this thread
brodos123 said:
Android is based on linux!
Linux is all about open source!
If we cant have root acess, whats the point??
Click to expand...
Click to collapse
If your a referring to that the manufactures aren't to happy about root access i believe it is a matter of profit, to be honest. If you have complete control over your phone and can install new systems, etc. whenever you want, it will be harder for them to sell new phones. It's plain business
But this is how I understand it - not sure whether it is true.
Okay so I'm currently downloading this 'Opensource_Update4.zip' file from Opensource, which I assume is the Official Kernel?
Just a few quick questions that I'd appreciate your help with guys:
1. Am I correct in what I just said above?
2. If so, do I just flash the file through ODIN?
3. Will this wipe my phone back to factory settings?
4. Will this affect my device being rooted?
Thanks in advance
New_World_Order said:
1. Am I correct in what I just said above?
Click to expand...
Click to collapse
No.
New_World_Order said:
2. If so, do I just flash the file through ODIN?
Click to expand...
Click to collapse
Again: no.
New_World_Order said:
3. Will this wipe my phone back to factory settings?
Click to expand...
Click to collapse
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
VAXXi said:
No.
Again: no.
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
Click to expand...
Click to collapse
Woaaaaaah I need a huge slap.
Would you be so kind as to explain please? :$
Sent from my GT-I9100 using XDA
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
VAXXi said:
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
Click to expand...
Click to collapse
Hahahaa okay thanks...
I think I'll just leave it alone! :')
Sent from my GT-I9100 using XDA
Hi guys,
I went to check for the HTC DX source code on htcdev.com, and saw there were around 31 sources, but they're are all CRC's...
Could anyone please explain to me, what is a CRC? I tried googling it, but it didn't really help.
Sent from my HTC Desire X using xda premium
kernel source
Lloir said:
kernel source
Click to expand...
Click to collapse
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
infernal77 said:
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
Click to expand...
Click to collapse
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Yasir Javed Ansari said:
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks, Yasir, I know lli0r made a device and vendor tree, but he said the vendor tree might be incomplete. He tried to make us a CM9 but hasn't got the device itself. I also read you can extract the files from a running device, but for that you need extract-files.sh or proprietary-files.sh, which isn't in there. I'm sure I can google and find one of those files from another device and try to run them on mine, but they're probably device-specific as well. And there isn't one of those files in lli0r's github. I checked that I'm sorry, I am ompletely new to Android, let alone building roms, but I love to just experiment a bit
Btw, when are you getting your Desire X ?
So, after destroying a tremendous amount of data and a whole lot of wait, I finally synced the whole OmniROM 6.0 source code via repo. Now I want to compile it for my device XOLO BLACK (Codename: BLACK) so, can somebody tell me how I can and what am I gonna need (I mean files, like vendor files, kernel etc.)?
Also, how can I extract its device tree? Because it's not available online.
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
zelendel said:
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
Click to expand...
Click to collapse
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
NutVolt said:
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
Click to expand...
Click to collapse
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
zelendel said:
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
Click to expand...
Click to collapse
I know it's gonna take long but if I can't even start then I'll feel very bad, all the hard work I've done to just fetch the source.
Anyway, how can I make a device tree? Can you teach me?
Hey,
I'm planning on buying this phone and I looked at Sony open devices project and saw that this phone was there but I could not see any vendor image corresponding to this phone.
Is it a problem for compiling and using AOSP?
Alex2008Ex said:
Hey,
I'm planning on buying this phone and I looked at Sony open devices project and saw that this phone was there but I could not see any vendor image corresponding to this phone.
Is it a problem for compiling and using AOSP?
Click to expand...
Click to collapse
Hey there, there's a oem partition for vendor proprietary blobs on SODP. The rest is OSS code inside vendor partition. Alternatively, you can get a stock rom OSS archive to see the /vendor content of your device on a defined release
fastbooking said:
Hey there, there's a oem partition for vendor proprietary blobs on SODP. The rest is OSS code inside vendor partition. Alternatively, you can get a stock rom OSS archive to see the /vendor content of your device on a defined release
Click to expand...
Click to collapse
Where did you find the oem partition on SODP? I can't find it here because there is nothing that refers to nagara or 5.10 kernel. Can you give me the link please I am new to Sony Xperia things.
Alex2008Ex said:
Where did you find the oem partition on SODP? I can't find it there because there is nothing that refers to nagara or 5.10 kernel. Can you give me the link please I am new to Sony Xperia things.
Click to expand...
Click to collapse
You just linked me the OEM partition link, nagara will be uploaded fairly soon here, as for kernel it's on sonyxperiadev github, there's the Sodp kernel and copyleft-kernel which is stock kernel sauce
fastbooking said:
You just linked me the OEM partition link, nagara will be uploaded fairly soon here, as for kernel it's on sonyxperiadev github, there's the Sodp kernel and copyleft-kernel which is stock kernel sauce
Click to expand...
Click to collapse
Ok thanks.
The only question now is will there be any problem when using AOSP without oem partition? Or will it just not boot
Alex2008Ex said:
Ok thanks.
The only question now is will there be any problem when using AOSP without oem partition? Or will it just not boot
Click to expand...
Click to collapse
It won't boot without this OEM partition
fastbooking said:
It won't boot without this OEM partition
Click to expand...
Click to collapse
Sad. Also this oem partition website hasn't been updated since July...
Alex2008Ex said:
Sad. Also this oem partition website hasn't been updated since July...
Click to expand...
Click to collapse
And why would it need an update ? If ain't broke...
I just received my Xperia and noticed that Sony uploaded the image on December 23rd
fastbooking said:
And why would it need an update ? If ain't broke...
Click to expand...
Click to collapse
There is so much broke on this actually. Seen the GitHub Issue Site of the SODP? lol
Anyways. Wanted to share this since it also builds aosp with sodp Trees:
GitHub - DEV-ICE-SOFTWARE-TECHNOLOGIES/DIOS
Contribute to DEV-ICE-SOFTWARE-TECHNOLOGIES/DIOS development by creating an account on GitHub.
github.com
Threads and ROMs coming soon.
Miustone said:
There is so much broke on this actually. Seen the GitHub Issue Site of the SODP? lol
Anyways. Wanted to share this since it also builds aosp with sodp Trees:
GitHub - DEV-ICE-SOFTWARE-TECHNOLOGIES/DIOS
Contribute to DEV-ICE-SOFTWARE-TECHNOLOGIES/DIOS development by creating an account on GitHub.
github.com
Threads and ROMs coming soon.
Click to expand...
Click to collapse
Hey, does this builds other ROMs or only aosp?