Related
Hi everyone! I've been wondering if there will be ever a port of cm or any other aosp rom to our m9+. I think sense doesnt do this device justice.
I read in some other thread that this wasnt posible due to the fact that mediatek had not release the source code-, then i stumble on to this
http://forum.xda-developers.com/meizu-mx/orig-development/helio-x10-kernel-source-code-released-t3225886
I dont know if this has anything to do with our device. But it would be nice to have an aosp ROM.
eoscylla said:
Hi everyone! I've been wondering if there will be ever a port of cm or any other aosp rom to our m9+. I think sense doesnt do this device justice.
I read in some other thread that this wasnt posible due to the fact that mediatek had not release the source code-, then i stumble on to this
http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886
I dont know if this has anything to do with our device. But it would be nice to have an aosp ROM.
Click to expand...
Click to collapse
But with this source code I would like prefer to have many features in the kernel development instead of aosp rom development.
Because I'm bored most of the times, I decided that I will try to port the cm for our p9 lite. First of all, I wanna say that I'm not a developer and my experiences with porting aren't too big (i only ported some roms from moto g to moto g 4g version and cm11 to unbranded chinese tablet). So my question is guys, do you think that it's worth trying? I read that it's pretty hard to make custom rom for devices that have chipsets like kirin, mediatek etc... But since Huawei released their kernel sources for this device I thought that it isn't a bad idea
What do you think?
there are a few guys on p8 lite forum that are trying for a while now...i think it's just to hard and we don't have experienced devs to work on our device
snapdesign said:
there are a few guys on p8 lite forum that are trying for a while now...i think it's just to hard and we don't have experienced devs to work on our device
Click to expand...
Click to collapse
Yeah, they even ported cm13 to p8 lite thats why I started thinking about it
dc239 said:
Yeah, they even ported cm13 to p8 lite thats why I started thinking about it
Click to expand...
Click to collapse
i don't think they did it... there are 3 guys that work on the same project...
I would love to see CM on this device.
It is pretty popular as well, so maybe we will see a build one day.
If somebody understands chinese, I bet it is worth to keep an eye out on their forums
Maybe it is also worth to observe the progress on the P9...
Schlengge said:
I would love to see CM on this device.
It is pretty popular as well, so maybe we will see a build one day.
If somebody understands chinese, I bet it is worth to keep an eye out on their forums
Maybe it is also worth to observe the progress on the P9...
Click to expand...
Click to collapse
I looked on the chinese forums too (our p9 lite is named huawei g9 in china) but there are only threads about twrp recovery and roms that are based on stock. I'm now taking my time to learn how cm and the other stuff works so i will try to report some progress soon hopefully
dc239 said:
Because I'm bored most of the times, I decided that I will try to port the cm for our p9 lite. First of all, I wanna say that I'm not a developer and my experiences with porting aren't too big (i only ported some roms from moto g to moto g 4g version and cm11 to unbranded chinese tablet). So my question is guys, do you think that it's worth trying? I read that it's pretty hard to make custom rom for devices that have chipsets like kirin, mediatek etc... But since Huawei released their kernel sources for this device I thought that it isn't a bad idea
What do you think?
Click to expand...
Click to collapse
We have kernel source code, and we can start building cm13,
But first we need a device tree.
My knowledge is limited to build ROMs from source, and yes i have kernel source code and cm13, but i need device tree and I don't have time to build it from scratch
lzimbrea said:
We have kernel source code, and we can start building cm13,
But first we need a device tree.
My knowledge is limited to build ROMs from source, and yes i have kernel source code and cm13, but i need device tree and I don't have time to build it from scratch
Click to expand...
Click to collapse
But we can use a device tree from p8 lite which has similar chipset (kirin 620) and then modifiy it. Correct me if i'm wrong
dc239 said:
But we can use a device tree from p8 lite which has similar chipset (kirin 620) and then modifiy it. Correct me if i'm wrong
Click to expand...
Click to collapse
As far as I know p9 lite has kirin 650 SoC, after some quick research i found that these two are different from many points... Of course you can try it but they aren't many chances of success.
Update:
I have done more research and someone was able to build and update kernel from that source. So we have a short start. At least we know that kernel source is ok
lzimbrea said:
I have done more research and someone was able to build and update kernel from that source. So we have a short start. At least we know that kernel source is ok
Click to expand...
Click to collapse
That's some good news, so the main problem for now is to build the device tree , but I don't know where to start (for now)
Hello,
I would just like to give my support to you and say that I'd really like if you could port CM to our P9 Lite! I'd contribute and donate also
Memovic said:
Hello,
I would just like to give my support to you and say that I'd really like if you could port CM to our P9 Lite! I'd contribute and donate also
Click to expand...
Click to collapse
Just to let everyone know. I planning to start working on kernel and device tree for p9 lite.
Probably I will make a new thread on development section soon. But don't expect to be a release soon... Will take a while till first build
lzimbrea said:
Just to let everyone know. I planning to start working on kernel and device tree for p9 lite.
Probably I will make a new thread on development section soon. But don't expect to be a release soon... Will take a while till first build
Click to expand...
Click to collapse
Great news and good luck. I bought this device with 2 years of payment plan, so I don't expect on buying anything new soon haha.
i talked with @XePeleato on the p8 lite section... they have made great progress... maybe he can help if you want... seems like a great guy
snapdesign said:
i talked with @XePeleato on the p8 lite section... they have made great progress... maybe he can help if you want... seems like a great guy
Click to expand...
Click to collapse
Yeah, I don't have the device but I may be able to help you out whenever I finish CM13, since then I'll have more time. By the way, don't be too excited about the kernel sources, We also have the p8 lite kernel source but many stuff is missing.
Emm,is it a bad idea to make a sort of a chat room for those working on CM for the P9 Lite?
It would go much faster if several people worked on it together instead of working separately,right?
So far I took the P8Lite device and vendor trees,replaced the blobs/sensitive stuff with the ones from the P9 Lite and edited the config files.
I tried to make the -eng build(of course,to be able to logcat broken things),yet the build info wouldn't mention the full build name in the "CM_VERSION=" section. I must've missed something I can't locate no matter how hard I try.
I also tried to build the kernel first,but it asked for the cyanogenmod_hi6250_defconfig in /arch/arm64/configs. I then "added" it(improvised by creating a copy of the stock defconfig and just renaming it),and then the build procedure asked for "hisi_cm_hi6250_debug_defconfig" in /arch/arm/configs,and I have no clue on how to get that one.
This is the first time I tried to do a thing like this,but I wanted to try,and sharing information(even the ones which appear to be useless) might help someone...
I will sync the improvized device and vendor trees when I get back home(Sunday),hopefully it will be at least a bit helpful to everyone.
It is most likely that you guys will keep ignoring me,but we surely can make it go faster if we work together.
The Marionette said:
Emm,is it a bad idea to make a sort of a chat room for those working on CM for the P9 Lite?
It would go much faster if several people worked on it together instead of working separately,right?
So far I took the P8Lite device and vendor trees,replaced the blobs/sensitive stuff with the ones from the P9 Lite and edited the config files.
I tried to make the -eng build(of course,to be able to logcat broken things),yet the build info wouldn't mention the full build name in the "CM_VERSION=" section. I must've missed something I can't locate no matter how hard I try.
I also tried to build the kernel first,but it asked for the cyanogenmod_hi6250_defconfig in /arch/arm64/configs. I then "added" it(improvised by creating a copy of the stock defconfig and just renaming it),and then the build procedure asked for "hisi_cm_hi6250_debug_defconfig" in /arch/arm/configs,and I have no clue on how to get that one.
This is the first time I tried to do a thing like this,but I wanted to try,and sharing information(even the ones which appear to be useless) might help someone...
I will sync the improvized device and vendor trees when I get back home(Sunday),hopefully it will be at least a bit helpful to everyone.
It is most likely that you guys will keep ignoring me,but we surely can make it go faster if we work together.
Click to expand...
Click to collapse
that's what i said in the p8 lite section a while back... for devs to work together... in the end they finally started a project together and made big progress... maybe a google plus page or on Hangouts...
snapdesign said:
that's what i said in the p8 lite section a while back... for devs to work together... in the end they finally started a project together and made big progress... maybe a google plus page or on Hangouts...
Click to expand...
Click to collapse
I use Hangouts to communicate with my fellow rom builders/dev.
Hangouts is pretty good for chat groups,and is easy to establish/use.
I also asked one excellent dev for help when he gets the time.
So,theoretically,we have a decent number of capable people for this endevour.
My Hangouts mail is [email protected].
Anyone who is interested in exchanging information can freely talk to me.
The Marionette said:
It is most likely that you guys will keep ignoring me,but we surely can make it go faster if we work together.
Click to expand...
Click to collapse
I'm 100% in, but i can't help you too much, cause i'm still trying to learn about the rom developing...
The Marionette said:
I use Hangouts to communicate with my fellow rom builders/dev.
Hangouts is pretty good for chat groups,and is easy to establish/use.
I also asked one excellent dev for help when he gets the time.
So,theoretically,we have a decent number of capable people for this endevour.
My Hangouts mail is [email protected].
Anyone who is interested in exchanging information can freely talk to me.
Click to expand...
Click to collapse
I may join if you like me to, but if you are focused on CM, delete vendor.mk, I completely rebuilt it to work on CM, you can't add such a high amount of blobs.
What I may suggest, is to fork the kernel (of your device) and the P8LiteDev tree, and use it as a base, but remove the blobs from vendor.mk
It would be also a good idea to deodex your rom and upload it somewhere.
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!
Why don't we have a miui 8 rom for our phone even it's available to oneplus 3
wish to use miui on op2 gonna be awesome
Wrong forum and unnecessary thread.
MIUI rom is available. Look in general section of forum.
Based On H2OS>
Link:GDrive
Wrong section,, you shouldn't post in development place,,
See general,, someone already port miui 8
is there an international MIUI rom with gapps and google framework installed? the thing with the h2os based rom is that i heats up randomly and doing small task like listening to music also heats up
use gapps pico 6.0
Thanks for getting my hopes up for nothing, moderator please move this thread.
IAM SORRY EVERY ONE THAT I POSTED in the wrong place but still no answer why we dont have miui for op2 ?
Probably because the interest is simply to low for MIUI, I for one ignore it since there's no Swedish language support in MIUI and also it's too much of an iPhone OS clone. ?
Hi XDA
As u know, xiaomi has released nougat for mi max which has exactly same hardware as our device,so it seems not to be hard to port it.
To all devs, discuss it on this thread.
Thanks to all.
Hmm.... I have no real knowledge of this, but I think there's no point in doing this. There'll be too many issues. Keep in mind that custom N ROMs don't have working camera blobs, so a ported MIUI N ROM would also have camera issues. It's possible that Xiaomi will release MIUI Nougat for our device since they'll already have a working chipset, but we'll have to wait and see.
Until Xiaomi releases for Kenzo I would definitely try out a port if someone can do it
This is a bad thread. Only thing same with the mi max is the GPU and SoC stuff, which has already been ported. Also, this is the wrong section for this.
Its of no use.pls close it.as @minz1 said
I was thinking of porting when the rom was released. Managed to downlod, extract and came to my senses.
It's pointless to waste time on that. Even if mi release nougat, i may just try to get camera blobs from it.
Rest in peace miui.