Hello Folks,
I am one of the organisers of a developer conference happening from the 24th-27th Feb in Barcelona as part of MWC. As part of the conference we have two CyanogenMod folks running a workshop showing you how to setup the tools and source code for CyanogenMod to build a new ROM. I believe this has never been done before so a great opportunity to learn how to join the CyanogenMod community.
If you are in the Barcelona area and want to come along I have a limited number of free passes to give away. If you ping me a private message telling me why you want to come along I'll let you know if there is a pass for you.
Wednesday 26th February
A Day in the Life of a CyanogenMod Developer
Room 6, Level 3, Hall M5
10:30 to 12:30 (10:30amto 12:30pm)
Speakers: Abhisek Devkota, Shane Francis; Community Manager, Device Maintainer, CyanogenMod
This exclusive workshop is an interactive CyanogenMod session for developers. Learn about the features and framework of CyanogenMod as well as understanding how the end to end development process works. This is not just an overview but you get hands on with the CyanogenMod code to make changes and build a new custom ROM so that you can become part of the CyanogenMod community.
The workshop will cover:
Bringing up your device for CyanogenMod
An overview of the features and framework of CyanogenMod
Coding a changeset feature for CyanogenMod
Uploading your code change to a gerrit instance
Compiling your code changes to generate a CyanogenMod ROM
Unfortunately as a new poster I can't post a link but if you go to wip dot org and follow the link to our WIPJam you can find out more.
Thanks, Rod.
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.
Hi All,
I would like to share the Kernel source code of Asus ZenFone-AR [ZS571KL] with XDA Community So that we can start development on this Beautiful Device.
Asus ZenFone-AR [ZS571KL] Kernel Source Code
As of Now i Did Not Found any commit History Nor the CAF tag Information . Once i get the Information OF CAF Tag i will re-base this kernel and upstream it to Latest Tag.
If any User ready for Testing Am ready to Start Development on This Device.
Credits : ASUSTeK Computer Inc for Kernel Code.
Please Feel free to use this code for Further Development .
Regards
Adi
If decide to keep the AR. I'm definitely down to help unlocking this phones potential.
Im asking you to do that really
Need it as possible as soon
If you want anything to do just tell me.
Here in this phone lots of features able to developing it
8 of giga RAM
REAL 23 MP SHOTS
TRYCAM
4K SCREEN RESOLUTION
AND MORE ADVANCED FEATURES
WE ASKED TO MAKE CLEAR ROM THAT DOES MAKE CHOICES TO INSTALL
ITS THE MOBILE DESERVE TO BE UP TO DATE IN THIS YEAR AND THE NEXT THREE YEARS LATER
REMEMBER NOTHING STILL EXPENSIVE ?
Due to many attempts and tries, WE MADE IT !
PROOF IN ATTACTMENT
Support Me:
Paypal: https://www.paypal.me/100Daisy
GOAL: Better PC, atleast not old Thinkpad
You will help but don't have money ? BECOME A TESTER
We lack of testers that have too many free time , Contact me on telegram to become tester and have latest info about rom dev for deen
Contact Me:
Telegram - @Zmianek
As we all know, official Android upgrades for the Nokia 6.1 Plus have ended with the Android 10 update and we will only be getting security patches going forth. However, some of us have the drive and desire to try out newer releases of Android, but we can't exactly shell out more money for a new device that will receive those updates.
Some of you might be aware that to make Android 11 (and beyond) ROMs a reality, any device needs a Device Tree and a Vendor Tree, and currently, there are no full trees for our device.
That's where I come in - again some of you might already be aware, but I have been working on full device and vendor trees for this device, with proper commit histories (flashbacks) so as to maintain order in the community. The trees are WIP, but the progress can be followed in the links below.
Device Tree
Vendor Tree
My current roadmap is as follows (I will update this list as and when I finish those things)
1. Finish the Device Tree by adding "configs," "rootdir," "ramdisk," and "symlinks"
2. Work on the Vendor Tree and pull missing blobs from the device
3. Build and test LineageOS with my trees - 31st build tested, device boots, sensors RIP
4. Maybe build other ROMs till android 11 arrives
Hoping to extend the life of this device,
Sid
Stonks
He attac,
He protec,
But most importantly
He got our bac
cocacola pepsi,
sid bhaiya sexy!
Cheers bro, I'm all for this!
Bumping the thread since I'm halfway done.
Also noticed another dev is close to releasing "source built vendor."
Dear dev, I challenge you to make your trees public.
Sid127 said:
Bumping the thread since I'm halfway done.
Also noticed another dev is close to releasing "source built vendor."
Dear dev, I challenge you to make your trees public.
Click to expand...
Click to collapse
Do it I am with you Coca Cola Pepsy developer :silly:
Moderator Information
Hello OP, I have moved this thread from Development to General as there is no ROM available yet. Please report this thread or contact me again if you have a ROM and kernel source links available, I can move this into Development section then.
Thanks.
Regarding the recent sparks of controversy and mods being involved and a certain someone posting this on their public channel -
Forgot to say few kids started doing criticism again better my answer do by your own or learn from scratch
Click to expand...
Click to collapse
I have only one response to the
message - I HAVE done it by myself and I HAVE learned from scratch, and my trees (which can be viewed by anyone) are evidence of the same. My GitHub history can be followed to see exactly HOW I learned too - my modifying Motorola (Chef) trees.
Also, one question for everyone - considering we had vendorless builds for our device since Android Pie, am I the only one who finds it suspicious that said dev built vendor sources only around the same time I did? I just would like to take a look at said Dev's work and verify.
Cheers,
Sid
Bumping thread since I finally made progress
After 31 excruciating builds, I'm abandoning my trees. My vendor repo got taken down in a DMCA notice for a proprietary library, and I just don't have the motivation to continue on my Device Tree after being seemingly stuck on a device which boots but nothing works. My tree is still gonna be up on my GitHub for anyone to refer to. As for ROMs, the Official LOS trees work great and that's what I'll be using for builds. Though I didn't finish what I started, I learned a lot and am thankful for the journey.
Cheers,
Sid
Edit: vendor repo is up again and I have removed the disputed lib
I wish you had maintained it as you've already done most of the work. What is the end node of device trees which marks its completion?
Volski_ said:
I wish you had maintained it as you've already done most of the work. What is the end node of device trees which marks its completion?
Click to expand...
Click to collapse
I will try and maintain it, but they've been abandoned for the time being... with Android R on the horizon, it didn't make much sense to spend countless hours trying to fix Android 10 trees. Device trees can be called complete when ROMs built using them are stable enough for daily use with every function working as intended.