Database Users

Developing Discussion | ROM & Kernel Dev./Port.

Hi Everybody
after some weeks Trying developing ROM's and Kernels i almost Give up... the kernel developing to MTK SoC is too much different compared to qualcomm SoC's (To me at least...) after compile more than 10 kernels to Run at my phone i only get Bluetooth and Radio FM not working with random reboots annoying frequently... but a real modifications to get this phone more smooth usage fail every time...(if you only compile the original source kernel it will run exactly like original kernel...)
I'm too n0#b alone to get everything running at developing process(kernel or ROM dev.).. at qualcomm phones(Xperia Acro S and Xperia L), i get more things running correctly with much more help from others Developers... but not released anything because it will be more from the same as others releases...
so if anyone here have more knowledge about that developing process things i have the Kernel Source and ROM platform to our phone...
---
i already try make CM12.1 run too.. but don't boot =#.. and if get work soon will be too much unstable to release, like my kernels =#
i will try port CM12.1 from @fire855 using that tutorial
the other possibility is try make compile the CM12.1 using our sources with modification from this ROM
but i will need help to make it compile right =#
so.. i will like have a discussion about that process with you guys... if anyone have some experience to help our phone have more custom's things to don't be locked with Original stuff/performance only.. if anyone have a useful guide, video or tutorial to compile anything to MTK SoC's it will be great too :highfive:

I appreciate your effort! I don't know much about MTK personally, but there is a thread on 4pda about porting CM 12.1 to MTK processors.
http://4pda.ru/forum/index.php?showtopic=671898
Sent from my VIVO AIR using Tapatalk

Ilxaot said:
I appreciate your effort! I don't know much about MTK personally, but there is a thread on 4pda about porting CM 12.1 to MTK processors.
http://4pda.ru/forum/index.php?showtopic=671898
Sent from my VIVO AIR using Tapatalk
Click to expand...
Click to collapse
already started try port CM12.1 ... but will not work too much things... almost every sensor will not work because that cross-firmwareOS port (CM Modules Drivers have a different compilation process =#) what i can do is try upgrade our source kernel using other MT6592 Sources to can compile the CM12 to our device... but again i will need find Module Updates drivers(blob) from other phones sources... =#
and my status with that right know is fixing a lot of errors while i compiling the kernel... i don't reach the inHouse ROM Compilation to than can get more Errors on logs to fix to release a simple Almost "stable" rom to how want test if it works properly to everyone... but don't push me to get that finished.. i work everyday and when i have time i try my best to develop that :highfive:
and release a unstable ROM/kernel is a wrong because maybe can brick someone phone because my errors (ramdisk modifications, and partition table map when installing the rom)... or we can wait BLU release the Lollipop with Hope because on twitter( @ UKkazam) tell me about no lollipop updates to this phone =#

i Tweeted to [@ KazamUK] asking they about lollipop updates and receive two replays... One say about newer updates to fix bugs on OS but not about lollipop and other saying "unfortunately, not upgrades to newer Android versions will be released"... otherwise [@ BLU_Products] Replay this "Please stay tuned on our social media for future updates, thanks!"... so... we have a faith about BLU brings Lollipop to our device? i don't have sure but with lucky it will happens :highfive:
...
and the porting CM12.1 ROM don't worked with me... bootloop =# and CatLog is extremely confuse =#

Kernel source link not working

I have an opportunity to make a PORT CM12 for BLU VIVO AIR in two days. A neighbor of mine bought a VIVO AIR and I will do whatever is necessary to get the ROM on the device.
I helped the BLU VIVO IV the users to have CM12. But as the device was not mine, so I could not fix some bugs. In the same epoch I talked to a BVA User and helped the kernel issue. He had given me feedback in relation to not have phone signal and not be able to replace the IMEI. But as I had no time, and the phone in my hands, the CM12 ROM stood with him.
Currently, it is quite possible that after CM12 MT6592 to be 95% stable in most of these devices Socs, the VIVO AIR may also have.
Once I have the device in hands, I'll let you guys know if CM12 can be available for all users VIVO AIR.
But if anyone know a actually already exist a ROM CM12 for VIVO AIR and clones.... Let me know...??

That would be awesome and I'm sure as me a lot of users are going to be happy about it
Sent from my REVIVED VIVO AIR using XDA mobile app

Kernel Source Code Discussion

Honor 7 (PLK-L01) Kernel Source Code Discussion​
Hello, honorable Honor 7 users , I hope you all are using this device to the fullest, now I'm starting this thread to discuss about the kernel source code for our beloved device. There are a lot of benefits from it.
1. We can create a master tree for our device.
2. After creating the tree we can create various branches of different custom ROMs, so that we can compile them from it.
3. We can add different CPU Govereners to our device to unleash its better performance, or better stability.
4. ETC. ETC.
There are still more benefits from the kernel source code.

Having The Honor 7 Kernel Source Codes Is Extremely Important For Development
Thank you for posting about that.
Indeed having the Android kernel source codes of (Huawei Honor 7 - PLK-L01) will help a lot in the development and porting process.
I am going to contact Huawei support team today to see when they are willing to share the source codes.
For anyone who is interested in this, please reply to this post and try to contact them too pointing your interest in having them.
This would be the most important step towards having custom ROMs on this amazing device.
Special thanks for "DigiGoon" to bring that up. :good:

Source Code
Yes, absolutely right @kenshiwara we can create custom ROMs and can tweak them to make this device even more better.
So guys, if more and more people will demand for the source code from Huawei then more closer we will get to have a custom ROM out of it, and I think that this device will gain much popularity after the company releases it worldwide, so we will get more and more developers working on it on different ROMs, but for that we need kernel source, so please contact Huawei for the same it's for our good only.

its funny,
I sent a email to them, on Monday asking the same thing (no reply thought) and was going to start a post about it , guess i was beaten to it
I really like this device, and would be a shame if not customs roms are available
phoenix
edit:
created a petition online, please sign it and add it to the 1st post:
htt p://ww w.ipetitions.com/petition/honor-7-source-code
(I cant post link outside XDA, delete the space)
ps: if anyone has any other ideas for the description, just tell me

themegaphoenix said:
its funny,
I sent a email to them, on Monday asking the same thing (no reply thought) and was going to start a post about it , guess i was beaten to it
I really like this device, and would be a shame if not customs roms are available
phoenix
edit:
created a petition online, please sign it and add it to the 1st post:
htt p://ww w.ipetitions.com/petition/honor-7-source-code
(I cant post link outside XDA, delete the space)
ps: if anyone has any other ideas for the description, just tell me
Click to expand...
Click to collapse
A petition will make zero difference. Honor UK and EU staff are well aware that they need to provide GPL code but they have to wait for the software team in China to provide the files. No point hassling them on social media etc as it won't make the code magically appear.
And even if we had kernel source it does not mean that custom ROMs will appear!
If you expected to be able to run custom ROMs then I'm sorry but you bought the wrong device.

flibblesan said:
A petition will make zero difference. Honor UK and EU staff are well aware that they need to provide GPL code but they have to wait for the software team in China to provide the files. No point hassling them on social media etc as it won't make the code magically appear.
And even if we had kernel source it does not mean that custom ROMs will appear!
If you expected to be able to run custom ROMs then I'm sorry but you bought the wrong device.
Click to expand...
Click to collapse
Having the source can mean that developers can make custom ROMs and flash it through twrp. I get your point that there is a lack of developers for this device, but I would like to mess around with the source, and see if I can create a ROM (only ported mtk ROMs in the past and modify some files in the past, which would require some learning)
And I didn't buy this device for custom ROMs, but it would be nice to have some

flibblesan said:
A petition will make zero difference. Honor UK and EU staff are well aware that they need to provide GPL code but they have to wait for the software team in China to provide the files. No point hassling them on social media etc as it won't make the code magically appear.
And even if we had kernel source it does not mean that custom ROMs will appear!
If you expected to be able to run custom ROMs then I'm sorry but you bought the wrong device.
Click to expand...
Click to collapse
As, I said earlier, with kernel source we can create tree, and out of the master tree we can create branches for various custom ROMs, and well in past I have made a ROM without kernel source, and made a tree for my other device(XOLO Play T1000), and successfully flashed via TWRP, it was having problems with network, wifi, so didn't made it to xda so, I think after having the source code we can create something

themegaphoenix said:
its funny,
I sent a email to them, on Monday asking the same thing (no reply thought) and was going to start a post about it , guess i was beaten to it
I really like this device, and would be a shame if not customs roms are available
phoenix
created a petition online, please sign it and add it to the 1st post
Click to expand...
Click to collapse
Thank you for supporting this thread and creating a petition as well. I have signed your newly created petition a moment ago.
As we said before, having the Android kernel source codes will massively help in the porting and development process.
It is within the development cycles of Huawei to release the source codes at a certain stage. Let's hope though, that they can release them soon.

It's annoying me that Huawei are still unable to respect the GPL by releasing kernel source on time whenever there has been a firmware update. It's even more annoying for my friends that work for Huawei in the UK who are pretty passionate about the devices and eager to help the community out but are sadly at the mercy of the Chinese office that are reluctant to provide any source. I really don't understand why they are being like this, since they have recently been supportive of Cyanogenmon on some devices as well as the Nexus 6P.
What possible reason could Huawei have for witholding the code for the Honor 7? I'm starting to wonder if Huawei have incorporated code into the kernel that isn't compatible with the GPL or is completely closed source.

flibblesan said:
It's annoying me that Huawei are still unable to respect the GPL by releasing kernel source on time whenever there has been a firmware update. It's even more annoying for my friends that work for Huawei in the UK who are pretty passionate about the devices and eager to help the community out but are sadly at the mercy of the Chinese office that are reluctant to provide any source. I really don't understand why they are being like this, since they have recently been supportive of Cyanogenmon on some devices as well as the Nexus 6P.
What possible reason could Huawei have for witholding the code for the Honor 7? I'm starting to wonder if Huawei have incorporated code into the kernel that isn't compatible with the GPL or is completely closed source.
Click to expand...
Click to collapse
Even then, they should have made an statement about it, but what would stop them to lie about it?
They could also broke some patents with the phone, so they are trying to cover it up by not releasing the code

flibblesan said:
What possible reason could Huawei have for witholding the code for the Honor 7? I'm starting to wonder if Huawei have incorporated code into the kernel that isn't compatible with the GPL or is completely closed source.
Click to expand...
Click to collapse
Whole AOSP is under GPL so i think they should release it

I signed it too. Let us home Huawei will release the source code, but like flibblesan said, I have my doubts about a quick release

AmitJordy said:
I signed it too. Let us home Huawei will release the source code, but like flibblesan said, I have my doubts about a quick release
Click to expand...
Click to collapse
Well, they replied to my tweet, and I think it will be out soon (**EXCITED)
You can check it HERE

flibblesan said:
It's annoying me that Huawei are still unable to respect the GPL by releasing kernel source on time whenever there has been a firmware update. It's even more annoying for my friends that work for Huawei in the UK who are pretty passionate about the devices and eager to help the community out but are sadly at the mercy of the Chinese office that are reluctant to provide any source. I really don't understand why they are being like this, since they have recently been supportive of Cyanogenmon on some devices as well as the Nexus 6P.
What possible reason could Huawei have for witholding the code for the Honor 7? I'm starting to wonder if Huawei have incorporated code into the kernel that isn't compatible with the GPL or is completely closed source.
Click to expand...
Click to collapse
Thank you for your comment and for your supporting this topic.
As they had released the source codes for Honor 6, there is no reason for them to not share the codes of Honor 7. As @DigiGoon have stated, they replied to his tweet already and never denied the idea or his request.
It would be nice if anyone who is interested in having the source codes and supporting the developers who are willing to work on porting ROMs for this device to comment on that tweet, share it and like it. :laugh:

kenshiwara said:
Thank you for your comment and for your supporting this topic.
As they had released the source codes for Honor 6, there is no reason for them to not share the codes of Honor 7. As @DigiGoon have stated, they replied to his tweet already and never denied the idea or his request.
It would be nice if anyone who is interested in having the source codes and supporting the developers who are willing to work on porting ROMs for this device to comment on that tweet, share it and like it. :laugh:
Click to expand...
Click to collapse
Yes, throw it everywhere so that more users will know about it, and new developers emerges out of somewhere, hopefully we will get the source code soon

sgned the petition...has huawei released source code for any other of their phones?
seen the answer to my question...doh!!

sheridan2000 said:
sgned the petition...has huawei released source code for any other of their phones?
Click to expand...
Click to collapse
Thank you very much for doing that! :good:
Yes, Huawei supports the open source community. They had released most of their previous Android kernel source codes including Honor 6 in the past.
Hopefully it is just a matter of time before they release the codes of honor 7. We are very excited to start working on a ROM.

Signed from by side too but I don't have any hope of any release...

beber75 said:
Signed from by side too but I don't have any hope of any release...
Click to expand...
Click to collapse
Thank you very much for your support! As they released the source codes of the previous model, there is no logical reason for them not to release them for this one.
They do respect the open source community and hopefully they will release soon.
Have faith and stay optimistic about it

I've bought this phone today, i really hope Huawei provide source code for Custom ROM.
And I've already signed the petition
Edit : Huawei doesn't provide any CPU source code, just EMUI source code...

Need help wrapping my head around building AOSP for HTC One M9

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!

MIUI Patchrom

Hello, can someone try this tutorial to port MIUI rom? I have not got unlocked bootloader, so I can not try it. If there will be someone interest in this. Try it, please.
https://www.youtube.com/playlist?list=PLzVhswXRAfBs6OBcJs3FIN9dMOxlpLfGu
Thank you.

pazdy0017 said:
Hello, can someone try this tutorial to port MIUI rom? I have not got unlocked bootloader, so I can not try it. If there will be someone interest in this. Try it, please.
https://www.youtube.com/playlist?list=PLzVhswXRAfBs6OBcJs3FIN9dMOxlpLfGu
Thank you.
Click to expand...
Click to collapse
Wrong SECTION. You should have posted this in Questions & Answers

It is probably almost impossible:
1 ) We need clear AOSP as a base because if not there will be so freaking much bugs to resolve that it is not worth it
2 ) MIUI require special porting way for diferent socs there are diferent sources for snapdragon, diferent for mediatek but did not see any for our kirin
3 ) It need a lot of testing reainstalling so there need to be someone who can live without his p9 Lite
4 ) There is needed someone who knows how linux works and someone who know good miui rom
5 ) Maybe it would be possible with AOSP as a base but we dont have it and it is hard to port clear aosp so will not even sit with this
6 ) You have stock EMUI which is similar you dont need MIUI
7 ) I dont have actually time to even put linux in virtual machine so wont do this
8 ) This thread is in wrong section so need to be moved to q&a but I think I answered you question
9 ) Even if it is possible you will not even try this because you have locked bootloader. So if you will unlock it to install rom so why not to unlock it now and build it on your own? Just learn how to do this. For me on my old phone it did get a week to have a booting rom. But there was clear AOSP. Here I dont know will be longer so go ahead and good luck
OK changed my mind. Will try to build based on cm13 but nothing to promise and dont know when will find some time so dont expect anything

Thank you for your post

Requirement of Paranoid Android Rom (AOSPA) for Moto G4 Plus

Hello everyone, the Paranoid Android (AOSPA) team has released their much awaited nougat 7.1.2 build for a handful of devices. Is it possible for the developers to port the rom to our Moto G4 Plus? If so, when can we expect to receive an official AOSPA rom for our device i.e Moto G4 Plus? Thanks in advance to the developers.

Athene is a pretty popular choice around ROMing. (LineageOS has 20795 installs on Athene) I would at least expect an unofficial build made by someone. Let's just hope they release an official build for Athene.

I have come to know that the team officially doesn't provide support for too many devices except Oneplus, Oppo, Pixel and the Nexus ones. So the chance of getting an official build is less. So in that case we have to look for an unofficial build.

Just wondering is there any update on Aospa for athene, official or unofficial?
:good:

Maybe this mean something. I dont know.

https://androidfilehost.com/?fid=745425885120754372
Anyone try this yet? I'm a bit hesitant and backups are a hassle

Ytim08 said:
https://androidfilehost.com/?fid=745425885120754372
Anyone try this yet? I'm a bit hesitant and backups are a hassle
Click to expand...
Click to collapse
Bootloop.

drmuruga said:
Bootloop.
Click to expand...
Click to collapse
Oh ok

AOSPA sources are public right?

Need help in porting
Hey friends I am porting PA for our device and I am facing a problem......when the rom goes to bootanimation it crashes due to libsurfaceflinger.........My guess is I am missing something in my hardware folder.....anyways the full log is attached below....Plz help https://drive.google.com/open?id=0B-...3V6M0xfdVF3YzA

Ripudamankaushik said:
Hey friends I am porting PA for our device and I am facing a problem......when the rom goes to bootanimation it crashes due to libsurfaceflinger.........My guess is I am missing something in my hardware folder.....anyways the full log is attached below....Plz help https://drive.google.com/open?id=0B-...3V6M0xfdVF3YzA
Click to expand...
Click to collapse
I would ask this question on Paranoid Android's Google+ page. https://plus.google.com/communities/112514149478109338346

reCoded said:
I would ask this question on Paranoid Android's Google+ page. https://plus.google.com/communities/112514149478109338346
Click to expand...
Click to collapse
Well I already did.........also I think its a device specific issue.....maybe our phone need some extra vendor libs or something

Hey everyone! So i fixed the problem with the surfaceflinger......now the only problem I have is with mm-pp-daemon....libqservice.so missing.........Is there anyone generous enough to help me with this bcz I m still holdin on to hope that we might be able to make it work .......anyway here is a partial logcat
https://hastebin.com/udadiwugig.coffeescript