Related
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard team!
Downloads:
TWRP Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Fixed partition table
Code updates from TWRP, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0
Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/twrp.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/twrp.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------
I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources.
Anyway, it would be appreciated if you report bugs here, so that I can check them!
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
EB20XY said:
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
Click to expand...
Click to collapse
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
negativman said:
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
Click to expand...
Click to collapse
Don't understand. What are you meaning?
mackief said:
Don't understand. What are you meaning?
Click to expand...
Click to collapse
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
negativman said:
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
Click to expand...
Click to collapse
OK. I'll check!
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
mackief said:
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Click to expand...
Click to collapse
what is exactly is the difference for kitkat ? Are the partitions different ?
EB20XY said:
what is exactly is the difference for kitkat ? Are the partitions different ?
Click to expand...
Click to collapse
Nope. At recovery-level, the biggest differencies are in the binary commands, then in Edify scripts.
Nothing relevant, but if you wanna flash a KitKat rom, you HAVE to use a 'KitKat' recovery!
mackief said:
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
Click to expand...
Click to collapse
And where can I download it? Discovered the mistake about which I spoke to you?
negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
It should be a still-working-on broken feature by team.
It's a early recovery port, as the team is still making its own modifies on 4.4 code.
BTW, today I should release newer build
negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
Ok, I was wrong. That's an issue caused by the fact that TWRP doesn't support fstab v2 - the partition table - and, as our device tree is using this version of table, TWRP didn't load our partition and couldn't backup anything.
Just released new build of CWM.
Changelog:
Fixed partition table
Code updates from TWRP, Google
Follow us on Google+, Facebook & Twitter!
Cheers.
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Adam77Root said:
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Click to expand...
Click to collapse
Actually, they're based on 4.4 . No new features, nothing new.
Then, my device tree with CM9 has nothing to do with these recoveries; of course I'll add kernel sources and so on.
---------- Post added at 08:57 PM ---------- Previous post was at 08:46 PM ----------
Just updated OP and sources. Thanks for the report.
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
laufersteppenwolf said:
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
Click to expand...
Click to collapse
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
mackief said:
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
Click to expand...
Click to collapse
You know, that's exactly the problem/difficulty of being a mod in his own section
I personally do not have a problem with it, but if someone wants to, he can see it as spamming, which could get you in trouble some time.
So I usually try to avoid such situations as soon as possible
So all in all it's your call. I have no problem giving you access to my thread, so we both can keep on deving on it, but it would be less work for both of us if we'd share it. (which I actually could use ATM )
So you tell me what you want to do
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. and on our Gerrit CarbonDev Gerrit.
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
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
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 website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
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 website. Carbon FAQ
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) 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?
Find out here:
Carbon Team
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!
Reserved
Also Reserved
Locksreen > see through option unchecked but I can still see the wallpaper through lockscreen ?
p.s no missed call auto responder seems to be working ?
orangzeb said:
Locksreen > see through option unchecked but I can still see the wallpaper through lockscreen ?
p.s no missed call auto responder seems to be working ?
Click to expand...
Click to collapse
Did you dirty flash?
I noticed the same issue with lockscreen, option was unchecked but it was enabled. I went into the settings for it, enabled/disable and it works as expected... try that.
As for missed call auto responder, I'm not sure what that is...
This ROM is great, I'm on 01/31 nightly and is working great. Thanks!
Gimmie a break, gimmie break, break me off a piece of that kitkat bar!
Good to see it's own thread. The jb one was getting confusing.
I'm currently on 2/3 nightly with aaarghhh's 1/31 cm11 kernel. So far so good.
KK launcher seems to use more battery than the other one included. Is the "ok google" listening enabled the reason? Im guessing having pocket mode on activates the sensor too..
Sent from my MB886 using Tapatalk
Which version of Arrrghhh's should I use? CM11 or AOSP?
mmapcpro said:
Which version of Arrrghhh's should I use? CM11 or AOSP?
Click to expand...
Click to collapse
I assume you mean my kernel, and CM...
Confusing, I spose I should remove the AOSP kernel It's only for pure vanilla AOSP. Most custom ROM's will use the CM kernel.
arrrghhh said:
I assume you mean my kernel, and CM...
Confusing, I spose I should remove the AOSP kernel It's only for pure vanilla AOSP. Most custom ROM's will use the CM kernel.
Click to expand...
Click to collapse
Nah, but something in Carbon's OP could mention "Use the custom CM-11 kernels, not the AOSP ones". Then we'll be able to laugh at people for not reading.
/Nooooooooooo. They're all gonna laugh at you
//But Mom....
/Nooooooooooo
///Anyone else have that CD back in the early 90's?
/Tell your friend Veronica, it's time for Hanukkah
/Drink some Gin and Tonica, and smoke some marijunikkah
skeevydude said:
Nah, but something in Carbon's OP could mention "Use the custom CM-11 kernels, not the AOSP ones". Then we'll be able to laugh at people for not reading.
/Nooooooooooo. They're all gonna laugh at you
//But Mom....
/Nooooooooooo
///Anyone else have that CD back in the early 90's?
/Tell your friend Veronica, it's time for Hanukkah
/Drink some Gin and Tonica, and smoke some marijunikkah
Click to expand...
Click to collapse
Hey goat! One of my favorite albums! He certainly doesn't make it like he used to.
Btw... Carbon rocks! I've used both nightlys with Arrrghhh's kernel and am very impressed.
Sent from my MB886 using Tapatalk
Nice ROM!
It blanked my voicemail which I was able to get from ATT and type in so voicemail works.
However I notice in about/status that for my phone number it says "unknown".
I think my phone has to be re-provisioned but on phone to ATT and so far they don't know anything about it.(EDIT: I hung up and will ignore it - see following posts)
EDIT phone IS able to receive calls to my number. Is this going to happen every time I flash carbon?(EDIT yes. no prob.)
I can't find "Developer Options" for debugging, in the settings menu. And the Device Tunables is blank.
KrisM22 said:
Nice ROM!
It blanked my voicemail which I was able to get from ATT and type in so voicemail works.
However I notice in about/status that for my phone number it says "unknown".
I think my phone has to be re-provisioned but on phone to ATT and so far they don't know anything about it.
EDIT phone IS able to receive calls to my number. Is this going to happen every time I flash carbon?
Click to expand...
Click to collapse
Probably every time you flash a rom that's CM10.2 or 4.3+.
mmapcpro said:
I can't find "Developer Options" for debugging, in the settings menu. And the Device Tunables is blank.
Click to expand...
Click to collapse
There is no device tunables for this device.
Developer Options is just like CM buddy.... click build # several times (7?).
mmapcpro said:
I can't find "Developer Options" for debugging, in the settings menu. And the Device Tunables is blank.
Click to expand...
Click to collapse
click "build number" 4 times
EDIT - sorry - DUPE - blush
mmapcpro said:
I can't find "Developer Options" for debugging, in the settings menu. And the Device Tunables is blank.
Click to expand...
Click to collapse
Go to About Phone and tap Build Number 7 times. That enables Developer Options.
I don't think we have any Device Tunables. Checking the sources and/or Arrrghhh can confirm that.
EDIT:
Well, damn, three posts in under a minute. Doesn't get much better than that.
skeevydude said:
Probably every time you flash a rom that's CM10.2 or 4.3+.
Click to expand...
Click to collapse
so do they have to re-provision it?
skeevydude said:
Well, damn, three posts in under a minute. Doesn't get much better than that.
Click to expand...
Click to collapse
lol. Seems this forum is now more active
KrisM22 said:
so do they have to re-provision it?
Click to expand...
Click to collapse
I dunno, that hasn't worked in a while and I'm not sure if anybody is even working on that. Everything works as it should -- those fields are more visual/for reference than anything.
---------- Post added at 12:28 PM ---------- Previous post was at 12:28 PM ----------
arrrghhh said:
lol. Seems this forum is now more active
Click to expand...
Click to collapse
Because this is the best rom as of late.
Hey guys
In memory of a very dear friend who passed away yesterday, I am starting this thread and a new era for our x3.
CM has pushed their CM13 branches yesterday, which means it's time for a new project. This time, though, I will be all by myself.
Please do not expect any miracles soon, as the M sources still need to settle a bit before we can even hope for a halfway working build.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, which we will most likely merge happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let me/us know about it before you release it and give proper credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
Most likely everything
Working:
Most likely nothing
Now, the most important part:
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[DEV] [WIP] Unofficial CM13 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-10-06
Last Updated 2015-10-06
Reserved
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
I will pay you, just please make final ROM for 4X, with everything working as it shoud be! That would be awesome!
Wysłane z mojego LG-P880 przy użyciu Tapatalka
I will pay you too. I would like when I will be to have the final ROM fo 4x. Thanks
Make it working relibly and responsively, and I will pay you too. You deserve it!
I don't mind if it takes months to achieve it. Just make it at some point, and I'll be happy!
Can't wait !!!
ps. i'm sorry for your friend
laufersteppenwolf said:
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
Click to expand...
Click to collapse
I'm also waiting for complete bringup tried for daily driver... failed. If you need help just send me message on hangouts/mail
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
SHM said:
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
Click to expand...
Click to collapse
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Some days ago is builded a cm13 ZIP, but it doesnt even pass bootloader.
Here are my commits for device tree. I disabled most likely everthong what causes building errors like Audio and CameraWrapper.
Here are my commits https://github.com/lenzwagner/android_device_lge_p880/commits/cm-13.0
@laufersteppenwolf will be on IRC the next evenings. Hope you'll be there too.
---------- Post added at 07:45 PM ---------- Previous post was at 07:40 PM ----------
laufersteppenwolf said:
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Click to expand...
Click to collapse
They fixed it some days ago.
Look here:
1. http://review.cyanogenmod.org/114239
2. http://review.cyanogenmod.org/114277
3. http://review.cyanogenmod.org/112338
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
laufersteppenwolf said:
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
Click to expand...
Click to collapse
If you find time, i'm on IRC atm
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
edit: eh, those commits have already been merged so problem still persists.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
fritzcola said:
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
Click to expand...
Click to collapse
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
SHM said:
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
Click to expand...
Click to collapse
Weird cause i just compiled a build with no errors.
fritzcola said:
Weird cause i just compiled a build with no errors.
Click to expand...
Click to collapse
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
fritzcola said:
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
Click to expand...
Click to collapse
No sir I am not. For another device, forgive me if that caused any confusion. My initial post on here was with regards to ffmpeg. A hunt for an unofficial build on xda brought up a few links and so wanted to make contact with the dev(s) to see if they had the same problem and/or fix so I may compare and possibly adapt if applicable my previous outcome. As for my current issue I do not expect any answer or results from here since its completely off topic from this device. I merely shared it in response with no intention or expectations for a solution. . I did take a look at your repo and saw ffmpeg is obsolete so I removed it from my tree as well since it was most definitely causing my builds to break.
@jcadduono - http://forum.xda-developers.com/showpost.php?p=68223333&postcount=5
sources: https://github.com/jcadduono/android...e_zte_ailsa_ii
kernel: https://github.com/jcadduono/android...mmits/twrp-6.0
@Unjustified Dev
TWRP: https://github.com/TeamRegular/android_device_zte_ailsa_ii
A user on the Chinese ZTE forums has created a github with the Axon 7 kernel code in it based on the A2017U B18 kernel dump.
http://www.myzte.cn/thread-272111-1-2.html
https://github.com/snowwolf725/ZTE_Axon7
TeutonJon78 said:
A user on the Chinese ZTE forums has created a github with the Axon 7 kernel code in it. Seems based off of the A2017U kernel dump.
http://www.myzte.cn/thread-272111-1-2.html
https://github.com/snowwolf725/ZTE_Axon7
Click to expand...
Click to collapse
ZTE have the kernel uploaded. (been up for quiet a while now)
http://opensource.ztedevice.com/
Under smartphone - ZTE A2017U
DrakenFX said:
ZTE have the kernel uploaded. (been up for quiet a while now)
www.opensource.zte.com
Under smartphone - ZTE A2017U
Click to expand...
Click to collapse
Yes, I've had since then. However, this is all github'ed, compile tested, and ready for forking.
We also have @jcadduono device tree and kernel posted from his TWRP work: http://forum.xda-developers.com/showpost.php?p=68195475&postcount=17
anks329 said:
We also have @jcadduono device tree and kernel posted from his TWRP work: http://forum.xda-developers.com/showpost.php?p=68195475&postcount=17
Click to expand...
Click to collapse
Indeed, I recommend folks clone this:
https://github.com/jcadduono/android_kernel_zte_msm8996/commits/stock-6.0
It's merged into CAF and allows future CAF merges without any issues. I updated it just the other day. Very clean kernel from ZTE, I've been really impressed.
From my stock-6.0 branch you can just run ./build.sh to compile a Image.gz and ./dtbgen.sh is automatically run after build to create a dtb.img.
I dont recommend using Image.gz-dtb as dtb building was not correctly set up by ZTE and I haven't bothered fixing it. Separated dtb.img works great though.
DEFCONFIG=zte_defconfig
DEVICE_DEFCONFIG=device_ailsa_ii
Otherwise you can use opensource-caf branch which is pure ZTE with no build modifications or scripts from me.
As for flashing kernels you build, check out LazyFlasher installer at:
https://github.com/jcadduono/lazyflasher
It will dynamically replace kernel image and dtb, and has a folder to put patch shell scripts. dm verity and forced encryption disabling already included as an example. Supports LZ4, Gzip, Bzip2, and LZO so far. Readme has more info. Avoids the need to constantly update ramdisks, and other branches have examples of things like SuperSU policy mod.
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Thanks a lot for all the info!
@TeutonJon78 Maybe it would be beneficial to add these infos to the OP?
So...now we have two competing TWRP/device tree setups. @jcadduono and @Unjustified Dev it might make sense to keep them similar as make sure there aren't competing versions running around and making support harder.
Edit: I also updated the title of the thread to reference a more generic change -- just listing all known github resources.
grujildo said:
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Click to expand...
Click to collapse
Well first of all you need the cellphone but it is heavily back-ordered, you can pre-order it now and you might or might not get it on 09/09/16.
I pre-ordered a month ago so I'll get my Gray Axon 7 on monday 08/22/16 (already have the tracking number), I would be willing to sacrifice it (selling it to you) if you want it, for the full price of course ($400 plus shipping). No means to sell anything, I'm not here to sell phones BUT if it is for a developer I'll do it and sacrifice a couple more weeks of wait time. All for the team.
grujildo said:
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Click to expand...
Click to collapse
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
This would be the best place to start learning Rom building.
Jose-MXL said:
Well first of all you need the cellphone but it is heavily back-ordered, you can pre-order it now and you might or might not get it on 09/09/16.
I pre-ordered a month ago so I'll get my Gray Axon 7 on monday 08/22/16 (already have the tracking number), I would be willing to sacrifice it (selling it to you) if you want it, for the full price of course ($400 plus shipping). No means to sell anything, I'm not here to sell phones BUT if it is for a developer I'll do it and sacrifice a couple more weeks of wait time. All for the team.
Click to expand...
Click to collapse
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Recon Freak said:
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
This would be the best place to start learning Rom building.
Click to expand...
Click to collapse
Hey thanks Recon Freak. Are you going to start developing for this phone? Who are the developers that want to be involved porting CM for the Axon 7.
It would be great to have a master dev on porting ROMs and lp him with the process. Otherwise are there any devs interested on porting CM to this phone?
Thanks.
grujildo said:
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Hey thanks Recon Freak. Are you going to start developing for this phone? Who are the developers that want to be involved porting CM for the Axon 7.
It would be great to have a master dev on porting ROMs and lp him with the process. Otherwise are there any devs interested on porting CM to this phone?
Thanks.
Click to expand...
Click to collapse
I wish I had the time and skilz. I can build roms and tweak stuff, but that's it. I know the processes but time and knowledge are not on a 44 year old father of two's side. Tree development is best left to the young and knowledgable.
grujildo said:
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
Click to expand...
Click to collapse
I just ordered one yesterday and it will arrive 8/25, but seems that they are already out of stock by now... 1 to 2 months is the status now
Recon Freak said:
I wish I had the time and skilz. I can build roms and tweak stuff, but that's it. I know the processes but time and knowledge are not on a 44 year old father of two's side. Tree development is best left to the young and knowledgable.
Click to expand...
Click to collapse
Nice, If I managed to get the phone early I will tell you and we'll be able to port CM for sure
---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------
Gachmuret said:
I just ordered one yesterday and it will arrive 8/25, but seems that they are already out of stock by now... 1 to 2 months is the status now
Click to expand...
Click to collapse
Yes ****, I just saw. Anyone know another way to get the phone?
grujildo said:
Nice, If I managed to get the phone early I will tell you and we'll be able to port CM for sure
---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------
Yes ****, I just saw. Anyone know another way to get the phone?
Click to expand...
Click to collapse
There is some on Ebay right at the $400 mark, that's how I planned to sell you mine in case you wanted it.
I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance
I have a G5S but it's my daily phone too...
Please someone be brave
My mother is using my g5s, I will post it on telegram group
Just for curiosity: How did you manage to port this ROM for G5S?
wiktorek140 said:
I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance
Click to expand...
Click to collapse
Hi, can you talk with @rssxda1 on telegram?
Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it
Mutcholoko said:
Just for curiosity: How did you manage to port this ROM for G5S?
Click to expand...
Click to collapse
And I didn't port for now. I just build rom for montana, and need someone for test it. I will name it "porting" when at least it boot
wiktorek140 said:
Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it
Click to expand...
Click to collapse
Super cool. I always wanted to learn how to do it.
I actually understand the process itself, but I can't understand this binaries and kernel part. Do you recommend any place to learn this?
wiktorek140 said:
Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it
Click to expand...
Click to collapse
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
wiktorek140 said:
And I didn't port for now. I just build rom for montana, and need someone for test it. I will name it "porting" when at least it boot
Click to expand...
Click to collapse
if you install an cedric build and an montana arm64 kernel, it will boot BTW. camera and sensors will be broken, but because motosh is initialized, sensors won't prevent the device from booting
KalilDev said:
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
if you install an cedric build and an montana arm64 kernel, it will boot BTW. camera and sensors will be broken, but because motosh is initialized, sensors won't prevent the device from booting
Click to expand...
Click to collapse
But i just ask about someone who will test it not how to fix something what i dont know it even work. And device tree from motorola-common don't even compile for me(wifi errors that something missing- i can't find solution)
Solved. My build dont even boot xD
Maybe next time
wiktorek140 said:
Solved. My build dont even boot xD
Maybe next time
Click to expand...
Click to collapse
Bad
I volunteer
wiktorek140 said:
I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance
Click to expand...
Click to collapse
Give the link of the rom I happy ? to try in my phone ? now
Because I looking for 64 bit rom for moto g5s device
Send me the link I volunteer
KalilDev said:
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
Click to expand...
Click to collapse
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?
Kamin4ri said:
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?
Click to expand...
Click to collapse
I think it require only files from /vendor to make camera work( i dont see any device specific file in /system), i have stock oreo too so i have all required files, and later i can push to github what i achieved
Kamin4ri said:
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?
Click to expand...
Click to collapse
i have montana stock for ages now. i have a montana vendor set up too.
KalilDev said:
i have montana stock for ages now. i have a montana vendor set up too.
Click to expand...
Click to collapse
Hmm, have u pushed it to github or it is a redo branch on motorola common?
Today will be new build, testers needed again