Hello. I searched the forum but didn't really find an answer.
I was until 5 minutes ago with the MIUI rom. I know the last kernel I flashed was the cyanogenmod kernel (which I used with another rom...can't remember which one because I flashed 5 roms in 1 day).
I wanted today to abandon MIUI because I was having problems with the display timeout...and some other things, compatibility with applications and details were not really good for me.
So I flashed now the rcmixhd, downloaded from rom manager. What kernel should I use?
And....is a kernel independent from the rom? Will a rom not work with the proper kernel?
*deep breath*
By going through the kernel threads, reading about them, seeing what others say then choosing a few to try, add them, try them, make a decision, keep one.
Just like your radio question and your ROM question it comes down to two things:
1. Your particular hardware capabilities - Some devices like some kernels better than others.
2. What YOU want from the kernel and how much YOU think it's the best one for YOUR situation / wants / needs etc.
Only YOU can decide what one YOU like the most subject to them working ok with your particular handset (this is particularly true for overclocking).
As a rule of thumb, if you're not fussed about over-clocking or BFS vs CFS etc. then what ever kernel the ROM creator advises.
Now please, pretty please, use the link in my sig to find more in depth answers as this question has been asked too many times already.
You don't pick the kernel, the kernel picks you.
Hey there guys
I'm a dev from the i777 forum -- the AT&T Version of the i9100. My rom, ShishirROM, is based off of XWLPG Odexed -- one of the few i777 ROMs to be odexed. It revolves around having great battery life and stability, as well as being nicely polished and revolving around JKay's brilliant mod.
The page can be found here: http://forum.xda-developers.com/showthread.php?t=1505433
Okay, so I need YOUR help to port this ROM over the i9100. It should be very straight-forward, but I'll need a few beta-testers to make sure everything works as advertised. And being a i777 user, I need to know a couple of things to make sure the ROM is perfect out-of-the-box:
What are the most stable/fastest i9100 modems and kernels?
That's it for now, and I'll need some willing beta testers to PM me with:
Experience modding/testing
Ability to use adb / analyze logcats
Has plenty of backups of existing ROMs incase something goes wrong
Has plenty of time to beta-test
I can only take around 3 or 4 of the most qualified since I don't intend to have to give instructions with each package (e.g., adb push file to directory then chmod, etc.). I think this is the first time someone has tried to port an i777 ROM to the i9100, but I know it's possible and I could make the necessary changes and upload it right now, but I'll need to make sure it works first.
Thanks
Dear fellow members of Galaxy S6/Edge XDA members,
I've created this thread to step back into developing a KANGed kernel once again. I have previously worked on the Galaxy Nexus 2 years back where I had the time to work on kernel development and was thus actively involved in the forums over there. However, after nearly one year, I had to put my kernel KANGing to a stop as I have my major examinations to focus on. Now, after almost finishing everything I need for my education, I want to step back into contributing to XDA with my very best that I've learnt from the Galaxy Nexus.
Here is the link of proof:
http://forum.xda-developers.com/galaxy-nexus/development/kernel-s-k-p-r458-3-0-101-t2479983
However, I do want to voice out that I have never been correct in developing so I'll just let you guys know as well because I don't want to hide anything. I have failed my development on the kernel before when I expanded to the LG G2, and various other devices. But everything came to an end because I wanted everything to stop so that I can sort things out as I did not work on the kernel properly.
Alright, so off goes my introduction. Now I will be presenting on my goals on the kernel I will be developing for the S6.
First and foremost,
I'll implement things that I've learn though my course of studies, followed by the things the kernel users want or need.
Last but not least,
I need some testers for the kernel as I am unable to do so with my S6. (I'm currently on an F2FS setup and will be testing my kernel once I've reached the phase for implementing arter's F2FS if viable.)
Right now I need a few testers who are either on stock, or are NOT on any Note-based ROMs.
I will begin releasing the zips to all the testers in private.
All you have to do is just indicate your interest in helping me test out my kernel by posting on this thread
Thanks,
Nixholas
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!
This thread is being made by me bcuz I don't have the proper tools for rom building(slow internet, no Ubuntu, and mainly exams).
So all the devs are requested to put forth their efforts to build nougat roms which is eligible for daily usage.
The open source kernel at this page
Direct:https://redirect.viglink.com/?forma...3.letv.cn/211/25/72/lefoss/0...OpenSource.zip
Mirror:https://redirect.viglink.com/?forma...mega.nz/#!8MF23RQB!4oqmXRNJr...2Ql74Pn_p0_3WI
I have edited the kernel but not with a toolchain, so it is not working.
If we make a stable kernel by editing it, we may be able to fix camera, VoLTE, and all the problems in the nougat and marshmallow roms.
I will get a proper internet connection in a few days. And eventually install Ubuntu in my desktop. Until then keep this thread alive mates.
So I request all the devs to make a proper Nougat ROM.
Sorry if I have told something wrong.
I can help you.
I have all the tools. I will team up with you. But the vendor blobs are so old. I have checked the kernel. Very less stability for Nougat. First, let us make a stable Marshmallow rom and wait for a few more people. Looking forward to hear from you.