I know that there are a lot of threads for compiling cm for many other phones but are there any dev available to make a guide for our beloved S4 i9500. The more people compiling cm for this device would be better and possibility of more bug fixes if we learn enough to do that. Been reading up a lot on this but was still wondering if a build guide can be posted please.
Hey man did u manage to get the tutorial coz im looking for it too and i have managed to download android 4.4 Supernexus source but i need help as well compiling for the Gt - I9500
I am NOT a developer!
I am a Systems Administrator, and I have built a 4.2 before using ubuntu 14.04, with a SGS2 i9100.
I have attempted in the past to ask for a device tree so I could build my own pure AOSP, and no one was able to help me.
SO, I now have my hands on a S4, and I want to put 5.0 on it.
I can create the build environment. either the windows version or the ubuntu version.
What I would like to know is which ROM would provide me a bit of instructions on how to use and build their ROM.
I'm looking for a ROM as close to AOSP as possible.
Preferably without any CyanogenMod builds, but I hightly doubt that is possible.
Seems everyone is using them for some reason.
I've been going to the ROM's section and I see no instructions on how to BUILD the rom.
Sure, I see their Github, but no info in what environment its been build in.
Can someone assist in helping find a ROM, so I can contribute to this community once I get the feel for it?
thank you!
You can try building cm to understand the basis, then move to aosp
Hello all.
Like the title says, I am trying to compile my first kernel.
I really like the CM11 i9505 nightly kernel, but it would be amazing in my world if it also had voltage/overclock/and gov additions.
It is my understanding that if I compile the kernel myself adding these features would be easy as they mostly exist in a single file that I could copy from similar kernels.
I have been trying to build my first build environment, but it seems that I am failing in amazing ways by trying to follow the CM guides on the their wiki. :crying:
I have an i3 dell 6420 laptop with Ubuntu (installed and functional) that I am dedicating to this effort, but I seem to need spoon feeding on this first attempt.
Does any one have a good step by step guide that I could follow for building the CM11 kernel?
Failing that does anyone have the time to chat in a live state on a weekend or late evening to help build this?
Of course if someone has a CM11 nightly kernel with the added features, I wouldn't object to using that and not reinventing the wheel.
Wrong section,
Ask a forum moderator (any one) to move your thread to the developer only section(of this subfroum)[emoji6]
Sent from my GT-I9505 using Tapatalk
He could just read the kernel tutorials in the android or chef central sections
Hello,
I'm happy to announce that I'm working on a port of MiUI 7 for our Motorola Moto X 2013 ("ghost").
Some people might already know that someone already made this port which of course it's true, you can see it here. The problem is that this ROM is no longer available for download and it had issues like it wasn't using the latest CyanogenMod 11 ROM and the Stagefright bug wasn't patched. Furthermore, the original author seems to be no longer present on XDA.
I'm using this tutorial in order to make the port. After a lot of days of tries and restart, I managed to compile a fully working and updated CyanogenMod 11 ROM that can be used as a base and I've started to fix some of the rejects caused by the PatchROM.
In order for this port to see the light, I would like some contributions from the community, I'm not an Android expert, it's my first port and I have other projects and real life stuff that gets in my way. So if you wish to help me, all you need to do is clone this repository, fix the rejects (one commit per reject please) and make a pull request. Of course, you will be in the credits.
Thank you for your interest and the support in this project.
Link?
I have been doing the same with lollipop CM
MIUI lollipop
Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!