Related
Just one caveat: I have done searches (read: multiple).
How in the world does CyanogenMod get to all of the supported devices? All of a sudden once CM9 is released, for phones/tablets moving from CM7 to 9, does it go out to all devices or what? Does it need to get ported from the source for each and every individual device? In general, how is CM updated and how does it get out to the officially supported phones/tablets?
Cyanogenmod ROMs do indeed have to be ported to each individual device and maintained. Once a device receives official support from the Cyanogenmod team, daily changes made to the AOSP source code (tweaks and bugfixes by the various contributing devs) are automatically compiled by a "buildbot" and released at the end of each day (thus these builds are called "nightlies"). These nightly updates are then made available for download through the Cyanogenmod website and through ROM Manager. Once code updates reach a certain plateau, a "final release"-worthy balance of features and stability, the build is released separately as a "stable" build (such as CM7.1), though you can still download it from the website or from ROM Manager just as with the nightlies. CM9 will eventually receive the same treatment and be released in the form of nightlies and stable builds.
Further (highly recommended) reading can be found here: http://www.cyanogenmod.com/blog/the-current-and-future-state-of-cyanogenmod-nightlies
Has anyone seen John Connor?
so the nightlies don't have to be ported, but every major revision does?
hugabu said:
so the nightlies don't have to be ported, but every major revision does?
Click to expand...
Click to collapse
No.
"Porting" is just a word used for the process of making the rom work on any certain device.
So to answer your question, once the work of porting CM to the certain device is done, that port is used as the base for both the stable and nightly builds.
Look at the analogy of when a new phone comes out, case manufacturers create a mold to use to make their cases fit the certain phone, and that mold is used to make all kinds of cases. Same concept
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
DiegoConD said:
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
Click to expand...
Click to collapse
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
shimp208 said:
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
Click to expand...
Click to collapse
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
DiegoConD said:
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
Click to expand...
Click to collapse
The best way to start is use the ARMv6 branch of Cyanogenmod 11, replace the CM 10.1 in the previous linked build guide with cm-11.0 ("repo init -u git://github.com/androidarmv6/android.git -b cm-11.0"), and then to direct the build to use your kernel take a look at this guide on integrated kernel building with Cyanogenmod.
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Slim7 is the project name for SlimRoms based on Android 7.1.1 Nougat and offers the following original features:
Slim Navbar & Hardware key rebinding
Single tap action, long press action, double tap action!-We’ve got you covered.
Slim Actions & Chamber of secrets
Customise your device to the fullest -You’re a wizard!
SlimRecents
A Faster alternative to stock recents -Your device, your choice.
SlimLauncher
An Open source, feature filled launcher! -Make yourself at home
Status bar customisations
Clock and Date? Battery? -More fun than you can shake a stick at.
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Unofficial Downloads J500F and M - Build0.13
Unofficial Downloads J500FN - Build0.13
For information on bugs, requirements, notes and more, read the second post.
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - The source of your device's kernel.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
Can you pour me some coffee?
XDA:DevDB Information
SlimRoms Slim7 Android Nougat, ROM for the Samsung Galaxy J5
Contributors
EsromG5
Source Code: https://github.com/SlimRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader LP and Modem MM (modem mm for FM works)
Based On: Aosp, Slim
Version Information
Status: Testing
Current Beta Version: Build0.13
Beta Release Date: 2017-02-15
Created 2017-02-15
Last Updated 2017-03-04
Reserved
What works?
RIL (Calls, sms, data)
Bluetooth (also with audio)
Camcorder
Camera general (1080p works fine)
Video Playback
Dados and RIL
Wifi
Audio
Sensors
LED
Flash
Hostpot
InCall
GPS
OTG
FM (use modem MM)
What does not work?
No, you tell me
Notice:
n/a
First
Good job, waiting for FN
second ....
good job bro.. i m so lucky that I own j5f :fingers-crossed:
wooow j5 developement is skyrocking this month, i will install it when theres the proper incall audio (im not crying for fix, just sayin)
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Booted on FN, but System UI has stopped
Telepracity said:
Booted on FN, but System UI has stopped
Click to expand...
Click to collapse
Without patch?
Deleted
JosephDM said:
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Click to expand...
Click to collapse
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
EsromG5 said:
Without patch?
Click to expand...
Click to collapse
With a patch from lineage os
MM kernel
Amarius1 said:
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
Click to expand...
Click to collapse
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
I didn't mean in call audio. I meant this ROM doesn't even boot normally and they have no clue why, yet instead of trying to debug they release bunch of not working builds. Camera doesn't work and it will not work since you'd either have to use updated open source HAL or revert Nougat media changes and it won't be a surprise if I'll tell you they have no idea how to do it. The only real devs, who knew what they were doing left because their work was posted by someone else and now he's making blind commits in hope that things will magically fix themself. They won't. I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in. Don't expect any significant changes. We can't even take patches from any other msm8916 devices, because they have more advanced development and use a lot of open source projects instead of prebuilt libs like we do. Even camera in CM13 is not fully fixed because open source cam doesn't work for us and after debugging it for 3 weeks I've still didn't come up with reliable solution to make it work (only made some errors dissapear).
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
The name of the forum is XDA - DEVELOPERS, this means that it is of full use to developers, if the person does not know how to help, it just stays silent while someone else can do it. Your help in testing is much appreciated since we are trying to do something free for you, and still prefer to say things like that.
I thank you and respect your concept, but try to help instead.
Amarius1 said:
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
Click to expand...
Click to collapse
The problem with incall and other stuff is already encountered by SoUnd001, but the big problem is that we're not hitting what it does so it's not booted, you're getting errors with incall and stuff because of the patch you're installing, not because of Rom or current kernel.
NOTICE:
I'm finishing a build for J500FN, we know it may not start properly, but I want to know the result for these users. I hope the sooner I have it all working.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Considering our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
Click to expand...
Click to collapse
I think there will not be an official nougat firmware from Samsung.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
In the Skies telegram group there was confirmation for official Nougat
EsromG5 said:
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
Click to expand...
Click to collapse
FYI: ALL custom ROM are using the same hardware repo's maintained by CAF, CM(Lineage now) or AOSP. There won't be any different results. The most important repos are all the same. The fact that you don't know that and your friend's github sources show that there is nothing to be helped. You're just playing games with users pretending you could make things work. What for? In the end they will be the ones left with nothing but promises. People, who could actually do something left, because someone took their work and published it to take all the applause for it and now you're blindly trying changes hoping they would somehow fix things.
[email protected]@!3Z said:
Considering that they have built nougat from source
Click to expand...
Click to collapse
They built from the source already made by ganesh. Their own changes are blindly trying things that have no right to work in the first place. Builiding android from someone's ready sources is like walk in a park.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
Certainly not for J5 2015, maybe 2016 but it could benefit us anyway since these devices are similiar.
I'm done, Moderator will probably soon come and delete my posts since all they care about is keeping forum clean. You may consider this device dead at the moment.
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs.
Click to expand...
Click to collapse
I understand from your post that Sound001 or EsromG5 did the hard work, but its not like that.
@Nick Verse and @ganesh varma were the ones who built cm12.1 and cm13 from source. They were also working on cm14 source while they were working on cm13.
So, please edit your post and dont mislead people.
Koloses said everything.
Since Nick and Ganesh left J5 development because their project which were working on was posted by someone else, the issues of Nougat CM/AOSP based roms wont be solved.
This:
I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in.
Click to expand...
Click to collapse
Hi all,
Now that CM is dead (RIP) and official Lineage OS for the Wileyfox Swift 2 has not yet happened, i've been looking into other alternative OS's that are compatible with the Wileyfox Swift 2 [marmite].
However i'm not seeing any that are compatible for this device (Resurrection Remix, Dirty Unicorn, LineageOS (yet) and wondered if anyone has had any experience with any other custom OS's that they know are compatible?
Thanks
There are none because there is no source code for this device. You must be patient and wait until Wileyfox releases (Before the end of this month?!) the promised Android 7.1 update, and hope they also release the source code with it.
I did several modifications to stock CyanogenOS 13.1 version for myself, but I found not worth it sharing that, since we're going to receive the new update really really soon. If the update is a disaster, or they do a OnePlus (release the update on the 31st, late in the night before the end of the month, and full of bugs), I'll consider sharing it. But until then, just wait for it.
Thanks for the update. :good::good:
linuxct said:
since we're going to receive the new update really really soon.
Click to expand...
Click to collapse
I live in hope. :fingers-crossed:
linuxct said:
There are none because there is no source code for this device. You must be patient and wait until Wileyfox releases (Before the end of this month?!) the promised Android 7.1 update, and hope they also release the source code with it.
I did several modifications to stock CyanogenOS 13.1 version for myself, but I found not worth it sharing that, since we're going to receive the new update really really soon. If the update is a disaster, or they do a OnePlus (release the update on the 31st, late in the night before the end of the month, and full of bugs), I'll consider sharing it. But until then, just wait for it.
Click to expand...
Click to collapse
Thats not true there is maybe not a source code but the chips inside the device (and drivers) are also used in other devices wich are so you can make roms for this device.
There are no roms because this phone isn't used by many peaple yet or the community isnt big at the moment for this device but we can port roms from the xiaomi redmi 3s for instance
draakwars said:
Thats not true there is maybe not a source code but the chips inside the device (and drivers) are also used in other devices wich are so you can make roms for this device.
There are no roms because this phone isn't used by many peaple yet or the community isnt big at the moment for this device but we can port roms from the xiaomi redmi 3s for instance
Click to expand...
Click to collapse
WTF? Do you think that by having same CPU means we should have the very same source code? I know there's source code for the SD430 in codeaurora, and that Xiaomi released sources for land, but that doesn't mean anything. It'd require a lot of dirty and unnecessary stuff to get it working here (it's not only about the CPU, right?), and since Wileyfox is REQUIRED to release the source code (all OEMs are) we can avoid it by just waiting patiently. From there, building Lineage will be easier, but hey, if anyone wants to do the hard job, use land-m source code and try to port it, is free to do so! :laugh:
linuxct said:
Wileyfox is REQUIRED to release the source code
Click to expand...
Click to collapse
Manufacturers need to release kernel source as it's under a GPL license, but Android itself is under the Apache License 2.0 and manufacturers are not required to release any source code. In fact the vast majority of manufacturers do not release any of their internal Android code.
And having kernel source does not magically allow you to make custom ROMs. In fact you shouldn't even need the manufacturers kernel source unless they are using some obscure hardware.
flibblesan said:
Manufacturers need to release kernel source as it's under a GPL license, but Android itself is under the Apache License 2.0 and manufacturers are not required to release any source code. In fact the vast majority of manufacturers do not release any of their internal Android code.
And having kernel source does not magically allow you to make custom ROMs. In fact you shouldn't even need the manufacturers kernel source unless they are using some obscure hardware.
Click to expand...
Click to collapse
I know, but it's better having and working with it, isn't it? I know we will need to bring up a device tree, and that it's not that easy, but starting out of a good base is better than mixing sources from other phones, at least that's my opinion.
The kernel sources are already available for a long time (slowpokes?): https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937
BeYkeRYkt said:
The kernel sources are already available for a long time (slowpokes?): https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937
Click to expand...
Click to collapse
Oops. You made my day man. I swear I wasn't able to find that, I had no idea they published it already, they didn't mention it on social media, and whenever I asked them on the support chat they were like "Sorry, we don't have that".
linuxct said:
Oops. You made my day man. I swear I wasn't able to find that, I had no idea they published it already, they didn't mention it on social media, and whenever I asked them on the support chat they were like "Sorry, we don't have that".
Click to expand...
Click to collapse
Because I do not think that the public (where most users are not geeks, probably) will be interested in the post that the developers have released the source code of the kernel. Or someone beforehand, before closing Cyanogen Inc, released the source code for the kernel. And support is usually not answered to such questions, because they do not have such information.
But in any case you need the information you need to find in all available ways.
As we all know, official Android upgrades for the Nokia 6.1 Plus have ended with the Android 10 update and we will only be getting security patches going forth. However, some of us have the drive and desire to try out newer releases of Android, but we can't exactly shell out more money for a new device that will receive those updates.
Some of you might be aware that to make Android 11 (and beyond) ROMs a reality, any device needs a Device Tree and a Vendor Tree, and currently, there are no full trees for our device.
That's where I come in - again some of you might already be aware, but I have been working on full device and vendor trees for this device, with proper commit histories (flashbacks) so as to maintain order in the community. The trees are WIP, but the progress can be followed in the links below.
Device Tree
Vendor Tree
My current roadmap is as follows (I will update this list as and when I finish those things)
1. Finish the Device Tree by adding "configs," "rootdir," "ramdisk," and "symlinks"
2. Work on the Vendor Tree and pull missing blobs from the device
3. Build and test LineageOS with my trees - 31st build tested, device boots, sensors RIP
4. Maybe build other ROMs till android 11 arrives
Hoping to extend the life of this device,
Sid
Stonks
He attac,
He protec,
But most importantly
He got our bac
cocacola pepsi,
sid bhaiya sexy!
Cheers bro, I'm all for this!
Bumping the thread since I'm halfway done.
Also noticed another dev is close to releasing "source built vendor."
Dear dev, I challenge you to make your trees public.
Sid127 said:
Bumping the thread since I'm halfway done.
Also noticed another dev is close to releasing "source built vendor."
Dear dev, I challenge you to make your trees public.
Click to expand...
Click to collapse
Do it I am with you Coca Cola Pepsy developer :silly:
Moderator Information
Hello OP, I have moved this thread from Development to General as there is no ROM available yet. Please report this thread or contact me again if you have a ROM and kernel source links available, I can move this into Development section then.
Thanks.
Regarding the recent sparks of controversy and mods being involved and a certain someone posting this on their public channel -
Forgot to say few kids started doing criticism again better my answer do by your own or learn from scratch
Click to expand...
Click to collapse
I have only one response to the
message - I HAVE done it by myself and I HAVE learned from scratch, and my trees (which can be viewed by anyone) are evidence of the same. My GitHub history can be followed to see exactly HOW I learned too - my modifying Motorola (Chef) trees.
Also, one question for everyone - considering we had vendorless builds for our device since Android Pie, am I the only one who finds it suspicious that said dev built vendor sources only around the same time I did? I just would like to take a look at said Dev's work and verify.
Cheers,
Sid
Bumping thread since I finally made progress
After 31 excruciating builds, I'm abandoning my trees. My vendor repo got taken down in a DMCA notice for a proprietary library, and I just don't have the motivation to continue on my Device Tree after being seemingly stuck on a device which boots but nothing works. My tree is still gonna be up on my GitHub for anyone to refer to. As for ROMs, the Official LOS trees work great and that's what I'll be using for builds. Though I didn't finish what I started, I learned a lot and am thankful for the journey.
Cheers,
Sid
Edit: vendor repo is up again and I have removed the disputed lib
I wish you had maintained it as you've already done most of the work. What is the end node of device trees which marks its completion?
Volski_ said:
I wish you had maintained it as you've already done most of the work. What is the end node of device trees which marks its completion?
Click to expand...
Click to collapse
I will try and maintain it, but they've been abandoned for the time being... with Android R on the horizon, it didn't make much sense to spend countless hours trying to fix Android 10 trees. Device trees can be called complete when ROMs built using them are stable enough for daily use with every function working as intended.