Official Mi Kernel Source - Redmi 9C Guides, News, & Discussion

I didn't see any post about kernel release, so I am posting one here.
GitHub - MiCode/Xiaomi_Kernel_OpenSource at dandelion-q-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
I hope this phone gets some developer love now.

ssm14293 said:
I didn't see any post about kernel release, so I am posting one here.
GitHub - MiCode/Xiaomi_Kernel_OpenSource at dandelion-q-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
I hope this phone gets some developer love now.
Click to expand...
Click to collapse
This kernel is not compile.

Related

Need Clarification with Forking AOSP in github

So a bunch of friends and I want to try to write a custom ROM from AOSP for Galaxy Nexus (toro). One thing we were thinking about was syncing all our code via github.
We will create our own repo so that we can make sure all our code is in sync.
One thing we looked at was github.com/android
Should we just fork all the repo's from the github.com/android page? We understand that it doesn't make sense to download everything from AOSP and upload via github.
Any help clarifying if we should fork or mirror repo's and what repo's specifically so we can get started.
msg04 said:
So a bunch of friends and I want to try to write a custom ROM from AOSP for Galaxy Nexus (toro). One thing we were thinking about was syncing all our code via github.
We will create our own repo so that we can make sure all our code is in sync.
One thing we looked at was github.com/android
Should we just fork all the repo's from the github.com/android page? We understand that it doesn't make sense to download everything from AOSP and upload via github.
Any help clarifying if we should fork or mirror repo's and what repo's specifically so we can get started.
Click to expand...
Click to collapse
Forking would be the polite thing to do because then the other developer's changes would be logged and tracked in your code. As too which ones that totally depends on what you are wanting to change. I would however suggest just forking the ones you plan on modifying and syncing the rest from the AOSP Github.
You don't always have to "fork" in the traditional sense. As long as you keep the previous commits it will be good taste. If you are only working on a jellybean rom, you can create a repo on github. Clone that repo. Then you can pull only the jellybean aosp branch into the one you created. You can do the same for every other project you add into your repo and before you know it, you saved a ton of bandwidth by only syncing one branch instead of tracking all branches. just my two cents.

[Q] creating and updating device tree

i am very much interested in compiling cm from sources . If a device(running 2.3) is not officially supported by cm so no device tree is found in github also..i want to learn how to make a device tree and vendor tree from scrach please guide me .aim fully prepared to spend my free time n this

[HELP] Device Request MOKEE OPEN SOURCE

Hello friends, I am writing so that together we will achieve something that will benefit us all.
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Click to expand...
Click to collapse
Source: official website of "Mokee open source" in the section about
This ROM is very good, delivers great performance gains on our devices, I personally used in my previous smartphone (Galaxy S2 i9100) and if not for spoiling that I still continue to use thanks to Mokee.
So now, this group has developed a community Mokee google plus (which I can not give the link, and that despite much I visit this forum for years, recently dared to enroll today, and rules are rules) You can find this easily by typing in google "open source community Mokee google plus".
In the section "Device request" please discuss who want open source Mokee for Xiaomi Redmi Note 2 and maybe if we are many, we consider and develop this excellent ROM for the device.
I and several others already did, but the more the merrier.
Cheers
I think that to create an open source rom, you should have access to the full mtk sources and model drivers, which is not the case.
gnazio said:
I think that to create an open source rom, you should have access to the full mtk sources and model drivers, which is not the case.
Click to expand...
Click to collapse
but a lots of device very rigorous with his privacy code have mokee (like Sony), maybe with something port from other device or other method, but i'm not expert, thanks for comment
Obviously the more the better.
If they are fully working!
I remember using the Mokee ROM on my galaxy s2 skyrocket. Brilliant ROM i hope we can get one for the Redmi Note 2.

[DISCUSSION] CM 13 Development for Sony Xperia M4 Aqua

Has anyone tried picking up on the work tonystark has done in the past regarding CM 13? It seems to me that he made some good progress but he has been MIA since April.
Feel free to use this thread for anything regarding CyanogenMod development.
Currently, nobody has focused more on to that side of things but as we have full Marshmallow binaries, it will be much easier to develop and continue tonystark's progress. Also, it would be helpful if you would add a discussion tag as this thread will most likely be used for the development of CyanogenMod!
G15C said:
Currently, nobody has focused more on to that side of things but as we have full Marshmallow binaries, it will be much easier to develop and continue tonystark's progress. Also, it would be helpful if you would add a discussion tag as this thread will most likely be used for the development of CyanogenMod!
Click to expand...
Click to collapse
Sure , it's done
I could try compiling CyanogenMod with tonystark's sources on Github but I do not own the device anymore, so I would need testers
G15C said:
I could try compiling CyanogenMod with tonystark's sources on Github but I do not own the device anymore, so I would need testers
Click to expand...
Click to collapse
I could test it out when you compile
Good, i will keep you updated with what I have managed to do
I've omnified the tonystark's cm13 sources but I don't have time to deal with the lot of compiling issues, so if is there a developer with experience in Omnirom, feel free to use my sources or contact me
dani020110 said:
I've omnified the tonystark's cm13 sources but I don't have time to deal with the lot of compiling issues, so if is there a developer with experience in Omnirom, feel free to use my sources or contact me
Click to expand...
Click to collapse
Any link to your sources or a way I could get hold of them? I am currently having some issues with compiling his sources
G15C said:
Any link to your sources or a way I could get hold of them? I am currently having some issues with compiling his sources
Click to expand...
Click to collapse
Click on my name—>Github account
Is there any Chance that there will be a official cyanogenmod 14 for m4 aqua dual??

Kernel source code released!

Hi,
I found out today that Xiaomi released the Kernel source code for this device, and you may find it at the following address:
GitHub - MiCode/Xiaomi_Kernel_OpenSource at lancelot-q-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
Hold your horses!
It's too early to speak about custom ROMs, this information is mostly useful for developers. Let's cross our fingers and hope for the best in the meanwhile.
Cheers!
Do you think sir redmi 9 community is large enough to have custom roms?
marxcs said:
Do you think sir redmi 9 community is large enough to have custom roms?
Click to expand...
Click to collapse
Only time will tell
marxcs said:
Do you think sir redmi 9 community is large enough to have custom roms?
Click to expand...
Click to collapse
It's only a matter of time. Watch this forum: https://forum.xda-developers.com/f/redmi-9-roms-kernels-recoveries-other-develop.11175/
marxcs said:
Do you think sir redmi 9 community is large enough to have custom roms?
Click to expand...
Click to collapse
Yes and already we made custom kernal
Hope we will get many "real" custom ROMs for this device soon
Congratulations to the redmi 9 community, this phone really need custom roms as that will tell helio G80 real potential. Xiaomi has really great phone but miui heavy skin ruin it to the ground
Me too
JulianXhokaxhiu said:
Hi,
I found out today that Xiaomi released the Kernel source code for this device, and you may find it at the following address:
GitHub - MiCode/Xiaomi_Kernel_OpenSource at lancelot-q-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
Hold your horses!
It's too early to speak about custom ROMs, this information is mostly useful for developers. Let's cross our fingers and hope for the best in the meanwhile.
Cheers!
Click to expand...
Click to collapse
Thanks for updating us. I find it very useful.

Categories

Resources