Related
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
Simply stated, we can't really list features here. There are too many and they change too frequently, and we now support a truly insane number of devices. Chances are, if you like a feature, we have it already. Seriously.
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
Both nightly and release builds are available. Please note that nightlies are for development purposes. This means that they may not work properly, may not flash, may not build for days at a time, and will probably eat your cat. If you flash these, know what you're doing, have backups, and don't complain when something happens. It's on you!
http://carbon-rom.com
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
You can also find a changelog in Settings->Carbon->About Carbon
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our G+ Community: http://community.carbon-rom.com This is where we spend the bulk of our time and the best way to reach us and other community members. We update and frequent this community far more than XDA, simply due to time constraints and the convenience of G+.
5) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Welcome to the unofficial CarbonRom thread for the NTT-DoCoMo Galaxy S III (sc-06d/d2dcm)
Make sure you have the correct device before you flash. These will not work on the i900 series.
These builds are not official because the kernel is not the standard CM kernel at this point in time. This is due to our device being a massive pain in the rear to develop for because DoCoMo likes to change things in their phones to make it "special". Thank you Dorkomo...
These builds are made by a very hard working developer by the name of @interlope. He's not part of the main Carbon team and does not receive anything from them. As a way of saying thank you for these builds we encourage you to donate to him.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=G9NQ5R43K8T8Q
If you are unable to do this, we request that you find some other way to contribute. Debugging is a very good way. Basically, we are looking for people who want to be active contributors and not just leech off others hard work.
The builds are now out of alpha and we have decided to open them up to everyone. However, to those that have and do contribute in the future I will be making modded versions of the roms with some extra goodies and such to show our appreciation. Keep checking those inboxes.
All builds are located here:
http://www.oudhitsquad.com/android/?dir=Samsung/d2dcm/carbon
The latest build (and all future builds) do not have Felica support.
If you are coming from stock there are instructions for rooting this device here:
http://forum.xda-developers.com/showthread.php?t=1895737
Bug reports
If you have a bug to report make sure you get a log of it or you will be ignored and removed from the testers list.
I won't go into the details of how to take logs. There are lots of tutorials on these forums on how to do that. However, there is a convenient app that will take the appropriate logs and upload them to wherever you like.
https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=en
Known bugs as of 08-11-13
none
Are you sure this is the right forum to post this? This is for the international version of the SIII (GT-I9300) AFAIK. Sry if I'm just not aware of any special rules...
nazfalas said:
Are you sure this is the right forum to post this? This is for the international version of the SIII (GT-I9300) AFAIK. Sry if I'm just not aware of any special rules...
Click to expand...
Click to collapse
We don't have our own forum so we piggy-back on the international s3 forum.
DroidZombie said:
We don't have our own forum so we piggy-back on the international s3 forum.
Click to expand...
Click to collapse
kk, didn't know
Check you inboxes folks the latest build just went out.
DroidZombie said:
Check you inboxes folks the latest build just went out.
Click to expand...
Click to collapse
Thank you. Can i do a dirty install or does it have to be a clean install?
dreamers123 said:
Thank you. Can i do a dirty install or does it have to be a clean install?
Click to expand...
Click to collapse
Clean. Wipe your system too.
Just cleaned installed. Everything is working great so far.
Sent from my SC-06D using Tapatalk
At the moment is the PacMan nightly van 7november flashed. To install the PAC rom there is a need to also flash GAPPS.
When I want to try the carbon rom is there a need to flash another GAPPS file?
And if its needed where can I found the correct GAPPS file.
topcads said:
At the moment is the PacMan nightly van 7november flashed. To install the PAC rom there is a need to also flash GAPPS.
When I want to try the carbon rom is there a need to flash another GAPPS file?
And if its needed where can I found the correct GAPPS file.
Click to expand...
Click to collapse
any 4.3 gapps is fine. I use slim gapps personally. They work very well with dark carbon.
Kernel
Which kernel is good for this rom? focusing on battery
Lean?Yank555? They work on the rom? anyother good?
rogerxcamargo said:
Which kernel is good for this rom? focusing on battery
Lean?Yank555? They work on the rom? anyother good?
Click to expand...
Click to collapse
At the moment there are no custom kernels for this device (read the description and make sure you have the device mentioned).
This is a Japan specific phone. If yours does not say sc-06d on the back of the device this is not the thread for you.
DroidZombie said:
Check you inboxes folks the latest build just went out.
Click to expand...
Click to collapse
So builds are 100% non-sharable now? I just wanna be clear so I don't post a link a some point and get yelled at.
Is this a request from OUDHitSquad?
Might want to put JAPAN at the front of the thread title, and move the first lines from post 2 into the 1st post so people can quickly ID this as the Japanese variant thread.
This link might be helpful to people to people (posted on the old thread). Not sure if this is what you're meaning:
http://www.oudhitsquad.com/android/?dir=Samsung/d2dcm
My back button sometimes does not response. Any Suggestion? I am running on the latest version.
Gesendet von meinem GT-I9300 mit Tapatalk
bikeaholics said:
My back button sometimes does not response. Any Suggestion? I am running on the latest version.
Gesendet von meinem GT-I9300 mit Tapatalk
Click to expand...
Click to collapse
You're in the wrong thread. Read the description very carefully
Sent from my SC-06D using Tapatalk
great day! john just made it happen. i've just sent him humble donation.
btw, if anybody wants to cook its own rom based on above i've just modded
well known old jpn cooker for this. you can fetch it from below link
https://app.box.com/s/6z2uj0svw40c5ogli677
dzebrys said:
great day! john just made it happen. i've just sent him humble donation.
btw, if anybody wants to cook its own rom based on above i've just modded
well known old jpn cooker for this. you can fetch it from below link
https://app.box.com/s/6z2uj0svw40c5ogli677
Click to expand...
Click to collapse
Please put that on the rooting thread. And be VERY careful about using it now. There have been massive changes to the kernel which may result in an unstable rom.
And to everyone else please check the second post for updates
Good day lads,
Disclaimer:
Code:
I don't know if you noticed a thread in the Q&A section that was closed by Matt. While I respect Matt's decision to close it, I find it a very relevant topic... The future of LineageOS for the P9 Lite. Please note that I do respect meticulous' wishes to charge for his work because I know how time consuming it is I wish to firmly express that I do not condone this mentality when it comes to Linux based operating systems.
I decided to make this thread with my little Dev knowledge in order to attract more devs who's willing to put in work on a stable device tree for free in spirit of community and for all to enjoy.
I do not have the Lineage source code at the moment but I will start downloading soon, I do know that I will need help and I encourage more devs/beginners to lend a hand for the benefit of us all.
Please, to begin, post links to relevant tarballs/links/downloads for development purposes, device tree and kernels, anything you've worked on so perhaps we can all work together.
Cheers
Sent from my HUAWEI VNS-L31 using Tapatalk
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Ignore it's just a critic custom rom user....[emoji12]
Hipom said:
Ignore it's just a critic custom rom user....[emoji12]
Click to expand...
Click to collapse
My words are razor sharp but honest and realistic.
Sent from my VNS-L21 using Tapatalk
Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Open source does not mean free, period.
pilgrim011 said:
On xda, it does mean free, period. People that think that they should be paid for contributing here are not welcome on XDA.
Click to expand...
Click to collapse
you are totally right
Just finish already. If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Also it should be in QA SECTION.
You start xda dev thread when you have something made already. Not just with idea.
lsander said:
If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Click to expand...
Click to collapse
This disussions are undesired here. I know a board where you can discuss that. If you want, feel free to have a look at it. This little Board is very pleased about every enlivenment. Opened a thread over there.
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Updated kernel
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Avsky0 said:
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Click to expand...
Click to collapse
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
dady000 said:
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
Click to expand...
Click to collapse
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Avsky0 said:
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Click to expand...
Click to collapse
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
dady000 said:
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
Click to expand...
Click to collapse
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Avsky0 said:
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Click to expand...
Click to collapse
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
dady000 said:
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
Click to expand...
Click to collapse
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Avsky0 said:
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Click to expand...
Click to collapse
Yeah you're right. I just checked it and I am copying Image instead of Image.gz. Seems like it's only a 'cosmetic' issue because it runs anyways.
Great news guys, my sources now compile with latest Linaro toolchain. The kernel actually barely needed any fixes, but I'm not releasing anything prebuilt yet, since I have no idea what impact on stability my hacks might have.
Screenshot
ndroid1562 said:
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Click to expand...
Click to collapse
Perhaps reading through GitHub commits, checking the code and see whether or not you're really interested. If you're using a Linux distribution which I strongly advise, learn bash scripts first - it's easy and self explanatory and from there you will get basics of directories and calling up files.
Goodluck
Sent from my HUAWEI VNS-L31 using Tapatalk
--FOR MORE INFO AND NEWS ALWAYS CHECK MY LAST REPLY!--
Thanks for understanding!
PROJECT IS ABANDONED.
Regards,
Holy ****, finally. I cant try it out for my self cause i need to leave to malta tomorrow but i can try it later
MIUI Rom, finally!!!!
I hope they fix the bug as soon as possible
Again, the ROM is NOT bootable, I need logcats from you to fix the problem, hopefully.
So don't expect this to boot.
Thanks for understanding!
Try to take a look here Logcats
I hope to have helped
Giuseppe300715 said:
Try to take a look here http://https://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
I cannot open the link. It gives me an error.
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
He meant this link https://forum.xda-developers.com/showthread.php?t=1726238
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
I just fix the connection
---------- Post added at 09:04 AM ---------- Previous post was at 08:50 AM ----------
[Universal] [Flashable] [Logcat] [Guide] So your test ROM build didn't boot
[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!
That's all I've found and that can be useful for both this Rom and others that you will develop.
Thank you, but I know how to dump logcats. I asked you if you could provide me some logcats of the rom not booting from your device and send me.
Thank you.
XTutorials said:
The ROM is compiled, but it doesn't boot and me and @AymenDe7 need logcats.
I will provide a download link, but just in google drive so not much downloads will be allowed. Bootable version (if) will be released on androidfilehost.
https://drive.google.com/open?id=0Bx9qplihpe8YVUNZRTNnSFY1bkk
Full no reject source code:
https://github.com/aymende7/XTutorials_Miui8
For now I need logcats from you.
Thanks for understanding!
Click to expand...
Click to collapse
Here's my logcat. http://www117.zippyshare.com/v/WcWK3ksX/file.html
I think there's problem with OpenGL
06-13 10:04:20.297 2468 2468 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: library "/system/lib64/egl/libGLES_mali.so" not found
06-13 10:04:20.297 2468 2468 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
Click to expand...
Click to collapse
And if you would copy libGLES_mali.so to /system/lib64/egl?
Would it work?
Thank you for your logcats. I will see what I can do.
How does it go with progress?
Should boot if you use custom kernel and copy&replace blobs
I am giving up on trying to fix that error message. I am trying to build AOSP 6 and then try again patchtom, hopefully I won't get that error.
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
haky 86 said:
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
Click to expand...
Click to collapse
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
Yeah. We have like 2 developers(one is a team) On this device. Haky and OpenKirin. And 6 "different" ROMs that all work the same, with the exception off the nougat FOMs, which have even more bugs.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
haky 86 said:
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
Click to expand...
Click to collapse
I know man, I wasn't talking about you. I was talking in general. I know you're doing god work, despite I'm not developing anything since a long time I still read forum and follow what's happening.
Like @Vinnipinni said, 2 guys and 6 "different" roms. But all working the same.
Back in times people were more likely waiting for stable CM/AOSP before compiling bunch of other distros. Now it's just mess.
I really wish I could go back to developing for android devices, especially now when I have programming knowledge and experience.
Hey, just opened a github specifically for lineage so if anyone wants to develop for the honor play and create repositories be my guest
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
In case you miss it lol :0 join in the telegram group to discuss
MODERATOR NOTICE: TELEGRAM LINKS DELETED
why need custom rom... official rom is perfect... performance is very good, battery life is very good...
Sent from my HUAWEI COR-L29 using XDA Labs
spityu85hun said:
why need custom rom... official rom is perfect... performance is very good, battery life is very good...
Click to expand...
Click to collapse
Well because you can get both of those in lineage as well as more customizations as well as nice stock android
Quantumkk123 said:
Well because you can get both of those in lineage as well as more customizations as well as nice stock android
Click to expand...
Click to collapse
Somehow... Seeing stock android feels meh...these days..
I really love emui...
Switching to stock is like a bad dream...atleast for me! :laugh:
Ok if anyone is interested i will be uploading the sources to github soon and me and another dev will be working on trying to get twrp to work as well as lineage os 15.1.... sources have not yet come for 16.1 sorry :/ so be ready to flash new stuff when bootloader unlock codes come for our devices in December
Don't have the time to upload sources yet however here is the link and if anyone can upload the sources to github for me i will be very greatful thanks http://download-c1.huawei.com/downl...oadId=99973&version=425859&siteCode=worldwide
Quantumkk123 said:
Hey, just opened a github specifically for lineage so if anyone wants to develop for the honor play and create repositories be my guest
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
https://github.com/LineageOs-Honor-Play/android_device_honor_COR-AL00
In case you miss it lol :0 join in the telegram group to discuss
MODERATOR NOTICE: TELEGRAM LINKS DELETED
Click to expand...
Click to collapse
Per the forum rules promoting social media is not allowed on XDA. This includes Telegram:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Quantumkk123 said:
Ok if anyone is interested i will be uploading the sources to github soon and me and another dev will be working on trying to get twrp to work as well as lineage os 15.1.... sources have not yet come for 16.1 sorry :/ so be ready to flash new stuff when bootloader unlock codes come for our devices in December
Click to expand...
Click to collapse
Will everyone be able to unlock the bootloader in December? Sound is interesting
kemalfadh said:
Will everyone be able to unlock the bootloader in December? Sound is interesting
Click to expand...
Click to collapse
No but xda devs / users will hopefully be able to apply for one
Quantumkk123 said:
No but xda devs / users will hopefully be able to apply for one
Click to expand...
Click to collapse
it seems unfair to some people like me who don't get permission for ubl haha:laugh::laugh:
https://github.com/ShqipLewis/Xiaomi_Kernel_OpenSource/tree/andromeda-p-oss
https://github.com/ShqipLewis/device_xiaomi_andromeda
https://github.com/ShqipLewis/vendor_xiaomi_andromeda
https://github.com/Inkypen79/device_xiaomi_andromeda
If anyone wants to build a custom rom possibly lineage i have found the trees hopefully this does help, lineage is the easiest so yeah
Current lead Dev is @Inkypen, if anyone else has any idea or wants to contribute here is the group chat
https://t.me/mimix3_5G
How I can help with this?
ZigmaInvader said:
How I can help with this?
Click to expand...
Click to collapse
honestly edit the respitory because so far they dont work i have made few files but keep in mind i literally borrowed them all from the perseus device tree since our device is pretty much identical apart from battery, if you do wanna make changes please know what your doing because i have no clue lol , and hopefully we can get this to boot ONLY edit files in the lineage path because the other paths need to be untouched okay thank you
Quantumkk123 said:
honestly edit the respitory because so far they dont work i have made few files but keep in mind i literally borrowed them all from the perseus device tree since our device is pretty much identical apart from battery, if you do wanna make changes please know what your doing because i have no clue lol , and hopefully we can get this to boot ONLY edit files in the lineage path because the other paths need to be untouched okay thank you
Click to expand...
Click to collapse
there also another difference is processor
Sorry guys I can't lie I think it's a complete mess I will be building a device tree for this device I just need A LOT of time and then I will try building some ROMs for this device reason why it will take so long is because I am learning myself and this will be the first time I am doing it hope it goes successfully for me
Hi guys! I've being making ROMs for the original Mi Mix and decided to take the plunge and get a Mix 3 5G. I've built up these skeleton trees and made LineageOS, but I haven't received my new device yet so I can't test it. It's horribly unoptimised and still has a lot of bloat from unnecessary drivers (hence the 1gb size) and I have no idea if this will even boot but here is the initial build if anyone is brave enough to install it. https://drive.google.com/open?id=1WOsXzgpdA8qTP6QWHi1gNW131dqgdDIC
This is an engineering build to help track down bugs so ADB debugging is enabled as standard. Any logs would be appreciated.
Inkypen said:
Hi guys! I've being making ROMs for the original Mi Mix and decided to take the plunge and get a Mix 3 5G. I've built up these skeleton trees and made LineageOS, but I haven't received my new device yet so I can't test it. It's horribly unoptimised and still has a lot of bloat from unnecessary drivers (hence the 1gb size) and I have no idea if this will even boot but here is the initial build if anyone is brave enough to install it. https://drive.google.com/open?id=1WOsXzgpdA8qTP6QWHi1gNW131dqgdDIC
This is an engineering build to help track down bugs so ADB debugging is enabled as standard. Any logs would be appreciated.
Click to expand...
Click to collapse
Ok I will try it aha can you send me these please because it will save me time from building another lineage device tree lol, my email is [email protected] please accept as I have ubuntu running on my pc now and I will try to fix a few things if that's okay?
Quantumkk123 said:
Ok I will try it aha can you send me these please because it will save me time from building another lineage device tree lol, my email is [email protected] please accept as I have ubuntu running on my pc now and I will try to fix a few things if that's okay?
Click to expand...
Click to collapse
I didn't realise that I didn't have link sharing on, should be ok to download now. I haven't uploaded my tree to GitHub yet, but once I do it will be available at https://github.com/Inkypen79/device_xiaomi_andromeda
Inkypen said:
I didn't realise that I didn't have link sharing on, should be ok to download now. I haven't uploaded my tree to GitHub yet, but once I do it will be available at https://github.com/Inkypen79/device_xiaomi_andromeda
Click to expand...
Click to collapse
Oh aha that's fine man , didn't realise this was android 10 good job man
Quantumkk123 said:
Oh aha that's fine man , didn't realise this was android 10 good job man
Click to expand...
Click to collapse
Don't get too excited yet lol. This LineageOS build is pie, once I know that's stable then I can move to ten. I brought up the original Mi Mix to ten so I have an idea of what's required.
Inkypen said:
Don't get too excited yet lol. This LineageOS build is pie, once I know that's stable then I can move to ten. I brought up the original Mi Mix to ten so I have an idea of what's required.
Click to expand...
Click to collapse
Lmao I realized when it said 16.0 aha that's fine tho still a lot more progress than me
I keep getting this error when trying to flash...the suggestion was to update twrp but 3.3.1-0 is the only one we have available ....
E: String resource 'zip_compatible_err' not found.
Using default value
Zip Treble compatibility error!
Invalid zip file format!
Any suggestions?
i think its my fault lemme just factory reset my phone install stock and see what happens. Yep our twrp is broken as after install it bricks whole device , and I know this isn't from the ROM because basically twrp bricked my phone from reloading to fastboot, it's very broken , but no one has been able to test that out because there hasn't been much to flash recently. Therefore @Inkypen will build some twrps for me to try and flash and see if his builds do work , fingers crossed they will
Quantumkk123 said:
i think its my fault lemme just factory reset my phone install stock and see what happens. Yep our twrp is broken as after install it bricks whole device , and I know this isn't from the ROM because basically twrp bricked my phone from reloading to fastboot, it's very broken , but no one has been able to test that out because there hasn't been much to flash recently. Therefore @Inkypen will build some twrps for me to try and flash and see if his builds do work , fingers crossed they will
Click to expand...
Click to collapse
Seems interesting. I have got mi mix 3 5g, just waiting on unlocking and will sure help it
ptlsajan said:
Seems interesting. I have got mi mix 3 5g, just waiting on unlocking and will sure help it
Click to expand...
Click to collapse
Sure there's a group chat where more info is posted there...updates etc https://t.me/mimix3_5G
I also have a mi mix 3 5g on the way, will be happy to test once i get it, thx alot for you work!
So far I have built a working version of Orange Fox recovery. Still waiting for my device to arrive, then some real work can start
https://www.androidfilehost.com/?fid=4349826312261670861
I should be getting my Mix 3 5G this week, the parcel is allegedly with my local post office already. I'd love to help out to get LineageOS working on it. I have minimum experience having flashed custom ROMs onto my current phone (Mi Max helium) as well as that of my Mrs (Mi 6 sagit), but I'd love to get more involved if possible. I don't need it to be my daily driver immediately, so I just need enough confidence in what we'll be doing here so as not to turn it into an expensive, cute brick The chassis being ceramic, it's already half way there right off the bat, but let's not get any closer please
Please generate LineageOS android 10 from Mi Mix Andromeda
ZigmaInvader said:
Please generate LineageOS android 10 from Mi Mix Andromeda
Click to expand...
Click to collapse
Join the telegram chat if you want any requests