Can any devlpr make some other rom like flyme, colour os, untill the Volte bugs solved in cm..that ll b great
Why don't you do it instead? There's a lot of resources on the internet that can get you started in no time.
If i know how to make rom from sources, i would started the work...if u know how to make thn ur gud to go..
All the Devs doing this stuff in their free time so take what has been released or make a ROM by yourself.
If you don't know how to make a ROM, head over to the library and the Internet, get books and stuff and learn the java programming language.
Additionally learn the "edify" language for setting up the updater-script etc. which is needed for proper recovery flashing.
So long...
I don't think the VOLTE bug is a motivator for any dev to develop an entirely new ROM.
They'd rather focus their efforts in squashing that bug and make a stable CM based ROM, which in my opinion is the best an Android can get.
from Moto™ G⁴ Plus (XT1643)
1chrome said:
I don't think the VOLTE bug is a motivator for any dev to develop an entirely new ROM.
They'd rather focus their efforts in squashing that bug and make a stable CM based ROM, which in my opinion is the best an Android can get.
from Moto™ G⁴ Plus (XT1643)
Click to expand...
Click to collapse
Yeah, I agree.
Plus PAC-rom is already in development, which takes the best from the best. So stay put, trust the devs and start contributing by testing of on-going ROMs.
PS
Resurrection Remix here and Beanstalk here are also in development.
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!
whats the difference between the two maintainer and builder?
there are a lot of nougat roms but they are all not official...as far as i understand because there ie no maintainer. but there are builder. so whats the difference.
almost every s model including the minis have official nougat
Maintainer is a developer, somebody that actually knows programming and also has some experience with it. He or she is the one that fixes device specific bugs.
A builder is just that, somebody that builds the ROMs. Anyone can build a ROM, it doesn't require any programming knowledge.
And there are various guides on how to do it too, you only need a Linux system with decent performance, otherwise it might take some hours only to build one ROM zip.
The Maintainer job is purely a voluntary one. So somebody has to volunteer to become the Lineage maintainer for the S4. But this is not all. He or she also needs to be accepted by the Lineage team, because they don't just take anyone. You need some experience for it.
Another reason we have no official Nougat is because there are still some bugs (such as the reboot bug) and the Lineage team doesn't accept that from what I heard. Oh, and they want cleaner code too.
So yeah, I don't know if he will have any official Nougat any time soon, if ever.
But just because we don't have official Nougat doesn't mean we don't have developers. We still have some people that do some developing for the S4.
Nougat kernel sources by hridayhs but no android n build yet https://github.com/HridayHS/android_kernel_xiaomi_msm8937/tree/cm-14.1?files=1
Please developers start building nougat builds we are lacking behind
porting device to n isnt that easy kernel needs to be patched to 3,18,31 you need blobs and tree
MIUI forum is full of those stupid polls.. please don't start with it on xda
uselles pos like miui forum to many poll but no rom
keep up up guys
True... It makes no difference... :/
That's what I m saying hriday hs created a kernel source for andriod nougat that is branch cm 14.1 see main post for link of kernel source
I agree with the stupid poll bit. I don't know if these people lie in their bed thinking up these foolish polls. They should find something useful to occupy themselves.
If you think a developer will just see the poll and think "Hey it's true, I should make a Nougat ROM" you're thinking something in the wrong way. Please stop, this is not the MIUI forum.
"We are lacking behind" ... dude this is not a race.
Remember they are normal people with work and other duties, asking them for work on Nougat ROMs using this passive-agressive way will only make them angry. Contribute in a more useful way like donating money, asking for help to other devs, or learning to make a device tree + compile source code.
If you want stable nougat rom then please donate this guy: https://forum.xda-developers.com/xiaomi-redmi-3s/how-to/moving-to-red-mi-3s-t3572896
yeah
This news wasn't spreading as fast as it should.
Project Treble is now available for the OP5T. Some talented developers have been working on getting it to work. The OP5T has an unused partition of about 1.7GB that can be used as a vendor partition and allow our devices to be Treble compatible.
See the thread below for more info in the Project Treble section of our Forums.
It looks like the easiest way to to this as the moment is to flash the latest Mokee. There is a trebelizer.zip available as well, which should then allow you to flash any GSI or "Generic System Image", essentially a ROM for Treble-compatible devices. In theory, any GSI should work with any Treble-compatible device.
https://forum.xda-developers.com/pr...opment/discussion-guide-oneplus-5-5t-t3776358
https://forum.xda-developers.com/oneplus-5t/how-to/mokee-rom-brought-project-treble-t3776107
https://www.xda-developers.com/oneplus-5-oneplus-5t-project-treble
MOD NOTICE:
Rather than duplicating discussions in the forum, let's use the threads linked above.
THREAD CLOSED
You do realize there's already a thread about this, right?
https://r.tapatalk.com/shareLink?ur...share_tid=3776107&share_fid=3793&share_type=t
Sent from my ONEPLUS A5010 using Tapatalk