Database Info

[DISCONTINUED][ROM]CyanogenMod 7 for Micromax a60 [COMPILED FROM SOURCES]

Welcome to CyanogenMod 7 For Micromax​
Congrats Guys its the first CyanogenMod rom ever for ANY micromax device means Micromax A60 got the first CM7 compiled from sources ever!~!
Cheers!
This is fully compiled from CyanogenMod 7 sources!
Thanks [email protected] for helping me a lot....
This is build #1 so dont expect every thing working
Me and Keyur are working on CM7 to get a stable build for Micromax a60..
so please dont ask for ETAs please , we are working.
Working -
Project Closed!
Not Working -
Project Closed
How to show support.
1 Show your support by hitting thanks and providing us logcats
2 Post replies here so we can see you are interested
3 By helping us in fixing bugs...
Download Section-
​Direct download link.​
How to install-
1 Download it
2 Place in SD
3 WIPE DATA (most imp)
4 Flash Rom
5 Reboot.
Please help me with logcat... (type in terminal-)
Code:
su
logcat>sdcard/log.txt
let it complete then upload log.txt from SD
Dont spam this Thread...Dont mirror my work...

bro the download link not working

WTF ! No Replies

Well just wanted throw a shout here.
I want to ask why P350 repo is used to do this? It is as same as performing a binary port with lots of data payload.

varun.chitre15 said:
Well just wanted throw a shout here.
I want to ask why P350 repo is used to do this? It is as same as performing a binary port with lots of data payload.
Click to expand...
Click to collapse
hehe lol it is not binary port p350 is having same chipset as a60 namely msm7x27 and it is nearly same device so device config is ported to a60 !! first understand what is device config and what is compiled from source. can you tell me in what sense it is binary port ! device folder is open source ! checkout on my github : github.com/keyur2maru you gotta need to check boardconfig then you will know what is compiled from source first understand and then reply Regards , Keyur maru

rom2maru said:
hehe lol it is not binary port p350 is having same chipset as a60 namely msm7x27 and it is nearly same device so device config is ported to a60 !! first understand what is device config and what is compiled from source. can you tell me in what sense it is binary port ! device folder is open source ! checkout on my github : github.com/keyur2maru you gotta need to check boardconfig then you will know what is compiled from source first understand and then reply Regards , Keyur maru
Click to expand...
Click to collapse
Oh well don't tell that to me.
Same chipset doesn't mean that you just sync it from someones repo and build it?
Some common sense is needed to be used, you should have recommended him to build from CyanogenMod sources instead of pimping yours, and help him configure from scratch.
If this is the matter(and extent of your knowledge) why don't you mention what things you modified in the source in order to adapt for Micromax A60?

heehee lol first open my device config and check everything is modded ! for a60 and yeah you replied Rohan that Im copying ron stuff hehe !!
CM7 is Really Done by Drap and Pax0r not by Ron G
and about copying who said im copying I was the man for cm9 and checkout device config it is like written from scratch only checkout nothing is there related to p350 and if similar hardware is there ! it is ofcourse that we will port that device config to work with our device it is like RMCC ( LGE DeVICES MAINTAINER ) also do the same It is No need to write full from scratch i think you need to learn more not me
---------- Post added at 02:15 PM ---------- Previous post was at 02:12 PM ----------
and we are not having having full source of cm7 it is only device config and source is synced from cm repo i think you need to learn more rather than me
---------- Post added at 02:21 PM ---------- Previous post was at 02:15 PM ----------
varun.chitre15 said:
Well just wanted throw a shout here.
I want to ask why P350 repo is used to do this? It is as same as performing a binary port with lots of data payload.
Click to expand...
Click to collapse
who said you p350 repo is used LOL :cyclops::highfive: and it is not repo it is device config :fingers-crossed:

rom2maru said:
heehee lol first open my device config and check everything is modded ! for a60 and yeah you replied Rohan that Im copying ron stuff hehe !!
CM7 is Really Done by Drap and Pax0r not by Ron G
and about copying who said im copying I was the man for cm9 and checkout device config it is like written from scratch only checkout nothing is there related to p350 and if similar hardware is there ! it is ofcourse that we will port that device config to work with our device it is like RMCC ( LGE DeVICES MAINTAINER ) also do the same It is No need to write full from scratch i think you need to learn more not me
---------- Post added at 02:15 PM ---------- Previous post was at 02:12 PM ----------
and we are not having having full source of cm7 it is only device config and source is synced from cm repo i think you need to learn more rather than me
---------- Post added at 02:21 PM ---------- Previous post was at 02:15 PM ----------
who said you p350 repo is used LOL :cyclops::highfive: and it is not repo it is device config :fingers-crossed:
Click to expand...
Click to collapse
This is where the noobish step was taken.
Boardconfig is meant to be constructed from scratch by analyzing the kernel configuration(Don't keep on shooting device specs are same)
Device specs doesn't mean you can grab the device configuration from it.
The location from where the source is synced doesn't matter(provided that its unmodded) but the Configuration matters a lot. Compiler analyses the configuration and readily modifies the source code and initializes compilation.
And this is why major functions are not working in your buid.
I saw your github repo of A60 and as it is a initial commit I cannot see what configurations you changed.
Can you mention here the modified lines?
And for "you need to learn more than me"
I would say no one is perfect, I agree that I have no experience in building a ROM from source(as I lack a good network connection) but that doesn't mean I have no knowledge in it. And for that statement you may receive a infraction from a XDA moderator These are fundamental aspects which are needed to be understood before proceeding with a build.

See bro I don't wanna fight but just i want to say that it is my own work it is not copied if you don't understand what are changes done how can you say im copying I don't fight It is my Own work Not any copied one
---------- Post added at 02:50 PM ---------- Previous post was at 02:48 PM ----------
and if you want to see edits just have a view at boardconfig can check nothing is related to p350 i just want to prove that it is my official work and not copied work and about i said
You need to learn more rather than me
I said that because you're statement is totally wrong ! i know im right so i said that

rom2maru said:
See bro I don't wanna fight but just i want to say that it is my own work it is not copied if you don't understand what are changes done how can you say im copying I don't fight It is my Own work Not any copied one
Click to expand...
Click to collapse
I don't have anything to do with if you copied or didn't.
But the approach Guided by you to Rohan is way tedious and will end both of you with nasty unremovable bugs which will point to binary port again!
You know this very well configurations play a vital role and are meant to be constructed from scratch instead of base them on other device
Yes you can use it for reference, but not use it for compilation as it contains device specific configurations.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
rom2maru said:
and if you want to see edits just have a view at boardconfig can check nothing is related to p350 i just want to prove that it is my official work and not copied work and about i said
You need to learn more rather than me
I said that because you're statement is totally wrong ! i know im right so i said that
Click to expand...
Click to collapse
What should I do with boardconfig? To see what's changed I need commits with those changes.
And how was I wrong?
Prove it pls.

See bro I don't think i should recieve infraction and about fixes it is not like in the first build we will get everything working even steve kondik will not able to do this our first aim was to get it booted and then fix bugs and about fixing bugs that are not fixed in rom ! they are fixed in device folder ! and about my way even RMCC do the same to get cm7 or cm9 on any new lge devices ! it is not written from base ! and check device folder most things are written from base and edited boardconfig and fixes will be done by adding new lines removing unnedded lines and all !
---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------
varun.chitre15 said:
I don't have anything to do with if you copied or didn't.
But the approach Guided by you to Rohan is way tedious and will end both of you with nasty unremovable bugs which will point to binary port again!
You know this very well configurations play a vital role and are meant to be constructed from scratch instead of base them on other device
Yes you can use it for reference, but not use it for compilation as it contains device specific configurations.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
What should I do with boardconfig? To see what's changed I need commits with those changes.
And how was I wrong?
Prove it pls.
Click to expand...
Click to collapse
just compare p350 boardconfig from cyanogenmod repo and compare with my a60 boardconfig and even compare whole device tree everything is changed and edited and that's the way we get cm7 or cm9 on new device and about p350. our cm7 main dev drap also ported p500 device config

Alright! I will see what's done and send a pull request too if needed
Good luck!

Thanks Bro See I Don't wanna fight !
I Just wanna Prove that I was Right And If you want further Proof Wait i will first fork p350 repo and then do edits in further commits so you can see commits and check what's edited As right now im busy in releasing my ics weekly #1 for p350 and did i got infraction i think i should not

Good to see cm7 for a60 ! Congrats guys
Sent from my ZTE_U N720 using xda premium

GB 2.3.7 port to karbonn A1
Hey friends i have successfully ported a rom based on racer rom on my Karbonn A1 or Zte N721 or Zte Racer or MMX A60 all have same specifications .the base ROM is racers ROM based on CM 7 . If i flashed it as it is it does not boot earlier. Then i used android kitchen porting tool . Now the rom the booting on my device but the issue is that My WiFi, Bluetooth and No service with sim. Idnt understand whats the problem is i guess it is dude to drivers but i dnt know how to change them.I need suggestions so that i can start working further .
here is the link to ported rom .
http://www.mediafire.com/download.php?4pzwnb6pbbw5pym

I was wondering if you guys would be as much helpful in making a CM based ROM for Micromax A57, which is a simple midrange model. But we have got a large community of users, and small-time developers. It would be awesome to see CM booting up in our phone Please help us

jyothisthaliath said:
I was wondering if you guys would be as much helpful in making a CM based ROM for Micromax A57, which is a simple midrange model. But we have got a large community of users, and small-time developers. It would be awesome to see CM booting up in our phone Please help us
Click to expand...
Click to collapse
haha..i am the ROHAN in facebook and the CEO of geekyzz.blogspot.in....remember me?

forever king said:
haha..i am the ROHAN in facebook and the CEO of geekyzz.blogspot.in....remember me?
Click to expand...
Click to collapse
Ofcourse I do My buddy Adhithya speaks highly of you

jyothisthaliath said:
Ofcourse I do My buddy Adhithya speaks highly of you
Click to expand...
Click to collapse
who is he?

Is This Project Alive????

WIP* ( port) Linage OS LG Stylo 2 plus

Development is dead. Please delete..

Rmontoya83 said:
Good news I have a working Linage OS 13 build for the lg stylo 2 Plus GSM. Thought it was bug free still has some issues though . My PC took a dump I have the sources saved on my hard drive I will have a new PC on Feb 6 and will release the Rom For Free probably with in a few days from then. As I'm almost done porting a working lineage OS 14 for the device.
I will update the device tree on Github So I can get help from other devs to trouble shoot these issues better and collaborate works. I will also include a working recovery with the Rom for free . I am doing this in my free time so please be patient .
I will keep you posted ?
Any people interested in helping let me know.
Click to expand...
Click to collapse
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT

cragains said:
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT
Click to expand...
Click to collapse
You can downgrade your firmware .

Nice work let me know when the source is up at github , i may be able to help

I'm so anxious I can't wait to get my new PC! I will be compiling a lot faster. You guys are going to like this lineage OS port. Hang in there

Any screenshots?
I'm interested in this also

Pelegius22 said:
Any screenshots?
I'm interested in this also
Click to expand...
Click to collapse
Not at the moment I had the backlight on my display burn out . had to flash the stock rom back for warranty purposes and for some reason every time I try and back up via twrp the data gets corrupted.
So the only place I have a working Rom is stored on a hard drive and I get my PC back on the 6th this month so it will be up soon.

Twrp link

Rmontoya83 said:
You can downgrade your firmware .
Click to expand...
Click to collapse
No PC right now, I moved across the state, and left my PC.
Can't down grade
LG Stylo 2 PLUS
TWRP no ROOT

Got the new laptop up and running building starts tommorrow.

All souces are downloaded . I will start building the device tree tonight hopefully by end of week myself and @messi2050 will have a working lineage OS build for the ph2n. I stood up all night working on the list of proprietary files need for the build.
Now comes the hard work of adding all the required blobs to get it all functional please be patient. As we are doing this in out free time. Once the device tree is all setup it will be a lot easier to port other roms to this device such as omni aokp DU and so much more. I chose a 13 build as I'm new to this and its a lot easier to port a Rom that has many components that are stable with the version.
If you appreciate our work buy us a cup of coffee. Or hit the thanks button for the Devs working on this build .
Thanks to all the xda community.

We should work on a changelog concerning drivers for cheaper models like my tmousa k550.

(((Poll )))) custom kernel with more governors and overclock or stock kernel?

Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom kernel with more governors and overclock! Let me know if you need me to test, I have MetroPCS variant. Thank you also for your time and development for this amazing device!

Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom all the way.
I am sending this to you in hopes of curing my boredom...

Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.

we need all the help we can get
Giminji said:
Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.
Click to expand...
Click to collapse
@messi2050
has one repository done for device /device
i have the other kernel/
i am working on the blobs using @JackpotClavin utility tool to pull all the blobs needed for the build. once we have a stable tree we can work on building other roms.

Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
https://github.com/RichieRich83
@messi2050
You rock brother.

Rmontoya83 said:
Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
URL deleted I am too new.
@messi2050
You rock brother.
Click to expand...
Click to collapse
Both you and Messi are doing amazing things. When this is done, both of you are getting a cup of java (I couldn't resist Java instead of Joe or Coffee). I downloaded the jackpotcalvindonkey thing yesterday, did the make on it, but didn't get it out.
Btw, your github shows no public repos.

Well that was quick

Poco F1, android r (11), running a GKI kernel (linux kernel 5.4)

I found this on youtube not sure if its real or not
https://www.youtube.com/watch?v=-SRqxkMpeMc
Poco F1, running a GKI kernel, and device specific modules loaded separately.
Video by Sumit Semwal
Additional Details:
* Xiaomi Pocof1 (beryllium) device config is hosted at:
https://github.com/pundiramit/device-...
* GKI (android-5.4.17) Image.gz and kernel modules are copied from
device/linaro/dragonboard-kernel project, built as part of the Android
CI.
* Kernel source for prebuilt vendor kernel modules (panel, labibb
regulator) and DTB is hosted at:
https://github.com/pundiramit/linux/t...
* Adreno firmware binaries are copied from stock PocoF1 images.

Yes, it's real. Don't be fooled by the Android R in About Phone - that's just what it says when you're running an AOSP master build. That's not what's important. What's more important is what they've done with the kernel.

https://www.google.com/amp/s/arstec...inline-linux-kernel-support-in-android/?amp=1
Tom Gall, the director of the Linaro Consumer Group, showed off a Xiaomi Poco F1 actually running the mainline Linux kernel under the usual Android OS. Gall told the audience, "There are major, major props to be given to the Google Kernel Team in particular for getting their code upstream so that we can boot devices with a mainline kernel
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
good job brother for for trying to bring it to masses.

Repo's are gone :'(
Anybody get a clone of the second repo at least? PM or post, please!
This is well documented now on AOSP but the work done here would save a lot of time.

CosmicDan said:
Repo's are gone :'(
Anybody get a clone of the second repo at least? PM or post, please!
This is well documented now on AOSP but the work done here would save a lot of time.
Click to expand...
Click to collapse
GitHub - pundiramit/linux
Contribute to pundiramit/linux development by creating an account on GitHub.
github.com

D1stRU3T0R said:
GitHub - pundiramit/linux
Contribute to pundiramit/linux development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Ah thank you, there was only an extra t on the second URL - typo.
This is awesome. Hopefully more 845 devices get the GKI treatment so we can experiment with different modules from other devices that get more love/attention from OEM's

[UNOFFICIAL][ROM][10.0/9.0] LineageOS 17.1/16.0 [violet][Q/PIE]

Introduction
A spinoff thread from the previously-supported-official thread by Atman.
This thread will contain my unofficial builds for violet. On the 16.0 version, the only real fix (so far...) have been the fingerprint scanner sepolicy denials. I aim to do monthly/bimonthly builds to keep up to date with security patches, as so far I haven't encountered any other issues (let me know).
On the 17.1 version, I have slowly figured out how to make it work, but it is highly experimental.
The 16.0 ROM is stable (I use it as my daily driver).
If you find any bugs, please do take screenshots, give a way for me to replicate it on my device, and send a logcat. If you're super smart, use a logcat and filter for the keyword so I don't have to do even more digging
Please don't tell me to use PE/Mokee commits.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Flash instructions
Same as usual:
Reboot to fastboot and flash recovery with fastboot (You have to use the TWRP linked below. Other versions likely won't boot.)
Reboot to recovery TWRP
Wipe to format data, wipe again to wipe system and cache (not necessary if you're updating, only if you're switching ROMs)
Flash firmware (ADB sideload) (this step is dated. The newer builds have a higher target firmware so you should try to flash without the firmware first, then flash the firmware if the ROM doesn't work.)
Flash the ROM (sideload)
Flash GApps, Magisk, etc. as necessary
Done
Downloads (16.0) (STABLE)
Firmware (Dated firwmare)
Recovery (TWRP)
11-Jun-2021 build (with 05-May-2021 security patch), and MD5 Digest
For previous builds see below
Downloads (17.1)
Here's the 17.1 ROM. Here's the md5 hash. It has the March security patch.
It currently does not boot. If you would like to try and help with development, flash the ROM, and then flash the Chinese Q firmware on top of it (this can be downloaded from xiaomifirmwareupdater). Be warned that there is a risk that the newest android keymaster may re-encrypt your device, which in the worst case may require you to format data and/or reflash recovery and/or flash a fastboot MIUI rom. So, it's a bit risky, but likely won't be an issue.
Credits, Sources, etc.
Too many to mention. Atman Shah for getting this device supported earlier last year. ThE_MarD (Marc Bougoin) for other help. Various other names I've seen - Bruno Martins, Weikai Kong, Wang Han... all of the Lineage dev team. I'm sure I'm missing many people who have been involved in the project. I am new, and very much a latecomer to all of this.
Device Tree: https://gitlab.com/mzha/android_device_xiaomi_violet
Kernel Tree: https://gitlab.com/mzha/android_kernel_xiaomi_violet
Other things see my gitlab: https://gitlab.com/mzha
A telegram group to discuss development for 16.0/17.1: t.me/lineageos_violet
Previous builds
07-Nov-2020 (incl. Oct-2020 security patch), with 07-Nov-2020 MD5 Hash
13-Jul-2020 (incl. Jul-2020 security patch), with 13-Jul-2020 MD5 Hash
11-May-2020 (incl. May-2020 security patch), with 11-May-2020 MD5 Hash

Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?

e2vinay said:
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
Click to expand...
Click to collapse
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time

hcnulma said:
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
Click to expand...
Click to collapse
That's great
by any chance will you consider adding signature spoofing support? that would be really great. it would help many users go for microG instead of gapps
I completely understand you're starter.
great work. good luck.
Thank you

e2vinay said:
will you consider adding signature spoofing support?
Click to expand...
Click to collapse
No, but there are a few alternatives:
Merge the changes from this RFC and build it
Download the spoofer from https://download.lineage.microg.org/violet/, or get the (ed)Xposed module, or other possibilities...

Will be official Lineage Os?

Can we expect los 17 soon?

himanshu fulmali said:
Can we expect los 17 soon?
Click to expand...
Click to collapse
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.

Heyyo @hcnulma good to see you got your thread up and going!
As for 17.1? You can work with your current kernel and cherry-pick the fixes that other maintainers of violet are using and same for the device tree and vendor blobs.
As an example, LeEco msm8996 devives are using kernel source code from Marshmallow just rebased on a CAF Q Tag for our kernel since we never got anything newer...
Even once Xiaomi release their kernel source code for Android 10? It would probably take quite a bit of work to shave it down to what you specifically need and then importing it on top of a fresh CAF tag for the kernel or even more work to try and inplement it into uour current kernel.
To get official builds of LOS 16.0 going again for violet you would need to show that you are capable of fixing any major bugs that arise as well.
https://wiki.lineageos.org/submitting_device.html
anywho, hope this information helps bud!

hcnulma said:
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Click to expand...
Click to collapse
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom

Thank you. If he is stable enough I will use it to build RR PIE

Zjh0094 said:
Thank you. If he is stable enough I will use it to build RR PIE
Click to expand...
Click to collapse
It's definitely stable...
prajwal2001 said:
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Click to expand...
Click to collapse
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.

Request to create group for discussion in Telegram

hcnulma said:
It's definitely stable...
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
as every ROM uses the same device tree
and you won't be making pe instead of lineage as the same device tree and kernel are used in every Q ROM except EvoX which uses crimson kernel

hcnulma said:
It's definitely stable...
Click to expand...
Click to collapse
Thanks. I will use it as my benchmark to build RR pie.
---------- Post added 15th February 2020 at 12:03 AM ---------- Previous post was 14th February 2020 at 11:57 PM ----------
hcnulma said:
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
/quick/la/msm-4.14

prajwal2001 said:
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
Click to expand...
Click to collapse
It is precisely the device tree that I'm worried about. From experience, PE has a lot of platform-specific stuff that Lineage doesn't (and the same the other way), and also from trying to figure out the fix to 16.0 I realised there's a lot of context/definition differences between the two device trees. I'd still give it a look, but I suspect it might be easier to just modify the current 16.0 device tree.
RupeshRN said:
Request to create group for discussion in Telegram
Click to expand...
Click to collapse
https://t.me/lineageos_violet.
Zjh0094 said:
/quick/la/msm-4.14
Click to expand...
Click to collapse
Yeah I already figured it was msm-4.14. Have already cloned it but am also considering cherrypicking changes that other devs have done to their kernel trees from 16.0 -> 17.1 as opposed to starting with the CAF kernel. A work in progress.

Sir I'm noob but mokee dev released android 10 and i think mokee and los are pretty same, will he not help you if you contact him?

An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.

An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.

Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Here's the 17.1 ROM. Here's the md5 hash. Needless to say, it's very experimental, not stable in the least (expect to get past boot maybe 70% of the time) - I'm getting very mixed results when experimenting myself. Nevertheless, try it out, see what you get. Install it the same way as usual. Keen to get as many eyes on this as possible

Will there be a Custom Rom?

Does anyone know about this topic?

https://forum.xda-developers.com/mi-note-10/how-to/custom-development-t4018813
In short:there are same some efforts trying to get custom Roms but nothing groundbreaking yet.
I am working on the device tree right now to compile from source. Not ready yet and don't have the device in hand right now (should arrive soon) s.o. else is trying with treble images.

nchantmnt said:
https://forum.xda-developers.com/mi-note-10/how-to/custom-development-t4018813
In short:there are same some efforts trying to get custom Roms but nothing groundbreaking yet.
I am working on the device tree right now to compile from source. Not ready yet and don't have the device in hand right now (should arrive soon) s.o. else is trying with treble images.
Click to expand...
Click to collapse
I thought device tree is something that was used to be leaked from Xiaomi

As far as I can see there is no device tree published by xiaomi for tucana (our device)
Only thing we have rn is kernel source.
But we can create device tree by ourself. There are some basic guides online. Rest is compare with existing device trees for similar devices and copy&paste.
for now I have downloaded k20 device tree, removed everything k20-specific (e. G. Popup Camera) and adapt further files for our device(s)
When my handset arrives (should be today) I can start unlock procedure (should take some time to get the code AFAIK), then I can unlock bootloader, flash custom recovery and see if I can get my device to boot properly after flashing... Then comes troubleshooting.
Right now I am expecting maybe a halfway booting device or broken/missing functionality at best. But we will see

I hope soon

The more people help together the faster we can get some Roms ?

nchantmnt said:
The more people help together the faster we can get some Roms ?
Click to expand...
Click to collapse
If you have a group for this, would you pm?

No group yet, but you still get an pm
Anyone willing to collaborate is welcome to pm me as well

I have seen this Android 9 source code. Is it helpful?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss
I thought this model would have more support and after 4 months there is no Rom. I hope that now that the price is going down more people buy it and we have more community. Thank you for what you know and develop.

ignalop1983 said:
I have seen this Android 9 source code. Is it helpful?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss
I thought this model would have more support and after 4 months there is no Rom. I hope that now that the price is going down more people buy it and we have more community. Thank you for what you know and develop.
Click to expand...
Click to collapse
Just an incomplete kernel sources, I think is useless.

https://www.xda-developers.com/poss...-fcc-certified-snapdragon-730g-penta-cameras/
There will be a lite edition soon. The only difference on hardware is number of pixels.
If its ROM is same or almost the same to current models, we should get some progress around development.

Anything new?

UtkuAblak said:
Does anyone know about this topic?
Click to expand...
Click to collapse
Please look at the existing topics first, before opening another topic!

nchantmnt said:
As far as I can see there is no device tree published by xiaomi for tucana (our device)
Only thing we have rn is kernel source.
But we can create device tree by ourself. There are some basic guides online. Rest is compare with existing device trees for similar devices and copy&paste.
for now I have downloaded k20 device tree, removed everything k20-specific (e. G. Popup Camera) and adapt further files for our device(s)
When my handset arrives (should be today) I can start unlock procedure (should take some time to get the code AFAIK), then I can unlock bootloader, flash custom recovery and see if I can get my device to boot properly after flashing... Then comes troubleshooting.
Right now I am expecting maybe a halfway booting device or broken/missing functionality at best. But we will see
Click to expand...
Click to collapse
Well, just tell me if you need help.

Same here, I am very tempted by the Note 10 but I am waiting for an aosp rom as many people complained about the stock miui rom

Any news or update on this? Would love to buy a Mi Note 10 as their prices have gone down but with the lack of development I'm kind of leaning towards the 9t even tho I'm worried about that front camera as some have had issues. I suspect not many are developing for this device because of the high price. Hopefully whoever said something up there about the Note 10 lite gets custom ROMs going with more devs

I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).

nchantmnt said:
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
Click to expand...
Click to collapse
yes he is working on this device.

nchantmnt said:
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
Click to expand...
Click to collapse
Awesome news! Thanks :good:

I think the development goes now straight because we have MIUI Stable based on Android 10 now.
Good luck!