Related
What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, dexter93 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-12-12
Reserved
Changelog
20150921-1824: Changelog: Fixed recovery issues <<-- building
20150918-1152 : initial release [5.1.1_r16]
Downloads
haxynox-6.0-i9300-20151211-2331.zip 236.6MB
33aeb6e59ec686818cd4088502b75fd1
haxynox-i9300-20150921-1824.zip 208MB
MD5:130cea4633f0e9b278aeb3def6d67d08
Reserved
GApps
For Marshmallow 6.0 Roms I recommend the PICO version of OpenGapps
http://opengapps.org/
I have tested @dankoman s GApps ZERO package with this ROM and it works fine.
Here is the link
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
If you want to use anything else, please feel free to post about your experience, but be aware that if you GApps package of choice doesn't work on this AOSP rom, you'll need to convince the GApps maintainer to take a look into it. That being said I am happy to talk with any maintainer.
mcgi5sr2 said:
What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, mcgi5sr2 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-09-21
Click to expand...
Click to collapse
^
That is what we always needed. Finnaly someone made it. THANK YOU!
Is there any screen shoots? And do we need GAPPS or is it included? I will try the rom. Thanks for taking your time to make annother ROM for our old S3
@mcgi5sr2 Hey man, I really commend you for doing this. All I've seen lately is Archi, Moster, & co.'s work (Apologies to the many unmentioned) being used as "base" for other users "projects", and of course all the real work is going on at source in the aforementioned dev's repos. I feel XDA has become a really unoriginal and user- (rather than dev-) oriented place recently.
Of course, you're not radically rewriting the fundamental Android code like the PA team did with Hybrid, but with such a ***ch of a chipset* it's pretty sick that you've taken it head-on to get AOSP up.
Sorry if this was a bit aggrandizing, I've just been tired of the constant stream of Sammy ROM ports and zip kangs.
By the way, you refer to yourself: "Ivan_Meler, mcgi5sr2 and myself", I think it should be "Ivan_Meler, dexter93 and myself"?
* "If you've ever glanced upon the sources" ... you bet you ... a glance was too much, I'm scarred ...
Thread cleaned, if you think you spotted a bug please attach logfiles and/or what you tried to fix it yourself etc.
Whiskey
Forum Moderator
Excellent, thanks for creating a thread for haxynox. Better than people posting in the slim/omni thread.
Any idea on how to fix the fact im getting bootloops on this particular rom?
I waited a long time for this! Thanks to all team :highfive::highfive:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
it's pure AOSP code ... without cyanogenmod 12.1 modifications.
if i understood correctly
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.
hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply
center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?
lukewilliams418 said:
Any idea on how to fix the fact im getting bootloops on this particular rom?
Click to expand...
Click to collapse
Could you provide a little more info please?
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
No, in fact it has a lot less, but that is the point.
b0unty said:
hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply
Click to expand...
Click to collapse
The sources are all freely available, feel free to use them
lukaaa477 said:
center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?
Click to expand...
Click to collapse
see above...
myshakugan said:
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.
Click to expand...
Click to collapse
Yea,sure it does,but i mean something else.
What i mean is, is there anything specific to the device changed, eg. Ram management,performance gains,optimizations etc.
mcgi5sr2 said:
Could you provide a little more info please?
No, in fact it has a lot less, but that is the point.
The sources are all freely available, feel free to use them
see above...
Click to expand...
Click to collapse
I used the latest version of TWRP to wipe all data and then I Installed the haxynox zip file with TWRP and then it just goes in a bootloop.
Bootloop
Enviado desde mi GT-I9300 mediante Tapatalk
any fix for this bootloop???
I was thinking: since we have an unlocked bootloader and custom roms, how hard would be to port AOSP Nougat?
There is any tecnical difficulty, like kernel version, that can block us?
Not much, I would imagine.
As far as I can tell, it'd just take a dev that's interested in putting in the effort.
Yes, this counts as my "yes, please" vote for Z00T.
I am votting with yes
I was thinking about do a try and compile it straight away, but i fear i'm not experienced enough to make something bootable
I don't think that the kernel or other thing will block it, but we got a custom ROM so late and I don't think we'll have a CM14 very soon
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Jhyrachy said:
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Click to expand...
Click to collapse
Umm, thanks for your thoughts about trying to bring N, it seem you got the answer yourself
from what i look at Z00L/T source, other than some fix and caf one, they could bring N to L/T with some borrowed libs. And looking from our source, I still found some line with L/T on it, so, yes, dev may bring N to this device, just hope that libs going to work with this devices.
But as you said, a fully fledged cm13 would be useful, using RR build for 3 days, and got the problem as they says. Plus, for me, front camera isn't working (called arclib or something, front camera effect when using asus camera, it's working fine with other camera because they didn't load that lib). Constant lag when using GPS other than "gps only" (might RR only problem). etc..
Either way, I hope that you could join the team (or, is he a one man army?) maintaining this device, fixing things come first, upgrade when everything is fine. At least "ok".
I don't know about AOSP, but many say choose CM because of CM broad compatibility layer. If that's true, then AOSP might slightly harder...
or... not really.
Sent from my ASUS_Z00RD using XDA Labs
Interesting, I'm not developer but I think this is possibke, Android 7.0 supports S410, maybe CM14 will better than AOSP.
yeah i still waiting ??
Sent from my ASUS_Z00ED using Tapatalk
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
I, but it will be possible tonight because now i working , phone at home
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
i will try tomorrow ...good for this ??
Sent from my ASUS_Z00ED using Tapatalk
Some news?
waiting :victory:
Waiting for some USEFUL news.
Today I try to compile it, but do not know if I aim, because I'm not a developer and I have no experience, but I try the same, stay connected, sorry for my bad english
I can't download the sources because it me give an errore i can't compile a ROM,sorry
Still waiting for news.
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
kurnalcool said:
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
Click to expand...
Click to collapse
Hi! Could this help you in some way? I don't know how, but I hope there is something usefull. This is a link to a russian forum where CM13 for ZE500KL was first posted by his original creator. Is in russian but I think you can use google translate to read the forum http://4pda.ru/forum/index.php?showtopic=766921
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
I am planning on building a custom rom, I would want CyanogenMod 14.1, or other custom rom, but I need a small team to develop it, to get the best result possible. I think it would be fun and maybe even do some great work.
But, I have some requirements:
1. Know big part of linux(ubuntu) commands
2. Know english or my home language, I hope you see at my profile from what country I am if you talk my home language just give me a PM. But I'm happy with both of them.
3. Have a computer(lol) and maybe 2,3,4 or more GB of ram and 100GB of storage for developing
4.Have a P8 Lite to test the progress of the rom.
Please do not make hate or fun or fun of me just because this thread sounds funny.
"we" already have a team like this, OpenKirin, made by XePeleato, surdu_petru and 1 more guy, working on P9...
D1stRU3T0R said:
"we" already have a team like this, OpenKirin, made by XePeleato, surdu_petru and 1 more guy, working on P9...
Click to expand...
Click to collapse
I know, but more teams= more progress; more roms
You better join their team
Audriuskins said:
You better join their team
Click to expand...
Click to collapse
, Would be better, but I'm not still at their "skill" level. I know how to build a rom from source, but I do not use my own source code, I often use XePeleato's source, I need to learn how to build device tree, blobs, etc.
XTutorials said:
, Would be better, but I'm not still at their "skill" level. I know how to build a rom from source, but I do not use my own source code, I often use XePeleato's source, I need to learn how to build device tree, blobs, etc.
Click to expand...
Click to collapse
Then create a topic in Development and post your progress as soon as you've done anything. The community tells you if it works or not, but building for this device without experience is not that easy. I wish you the best of luck, but only using XePeleato source and adding nothing won't help at all. If you think you can fix something, just commit to their github. But you won't find a developing team over here. I would try to learn myself, but I don't have a PC that's able to do anything. Try to build things yourself, commit to their github and try to help the OpenKirin team. There nothing else to do here for you, if you're inexperienced.
XTutorials said:
3. Have a computer(lol) and maybe 2,3,4 or more GB of ram and 100GB of storage for developing
Click to expand...
Click to collapse
Just to joke a little : with only 2GB RAM & 100GB storage, you'll be able to build the whole source code of Android MM or N, in a few days
Now really, you need at least 16GB DDR3/4 and minimum 200GB storage ( preferably SSD ) , because you need to set ccache to 50GB or maybe 100GB ! If you have only 100GB and setting ccache to 50GB, with only 50GB storage free - you'll never be able to build the whole source code !
Vinnipinni said:
Then create a topic in Development and post your progress as soon as you've done anything. The community tells you if it works or not, but building for this device without experience is not that easy. I wish you the best of luck, but only using XePeleato source and adding nothing won't help at all. If you think you can fix something, just commit to their github. But you won't find a developing team over here. I would try to learn myself, but I don't have a PC that's able to do anything. Try to build things yourself, commit to their github and try to help the OpenKirin team. There nothing else to do here for you, if you're inexperienced.
Click to expand...
Click to collapse
+1
surdu_petru said:
- you need at least 16GB DDR3/4 and minimum 200GB storage ( preferably SSD ) -
Click to expand...
Click to collapse
+1, i have i7-4770k @ stock, 6gb of ram and 140gb of samsung ssd allowed to virtual machine. And first build takes about 2hr30min
I know little about Linux, but I heard that developers can use Google Cloud.
Sent from my HUAWEI CHM-TL00H using XDA Labs
Vinnipinni said:
Then create a topic in Development and post your progress as soon as you've done anything. The community tells you if it works or not, but building for this device without experience is not that easy. I wish you the best of luck, but only using XePeleato source and adding nothing won't help at all. If you think you can fix something, just commit to their github. But you won't find a developing team over here. I would try to learn myself, but I don't have a PC that's able to do anything. Try to build things yourself, commit to their github and try to help the OpenKirin team. There nothing else to do here for you, if you're inexperienced.
Click to expand...
Click to collapse
That is what I'm going to do in the next days, I need to research a lot for now and if I (god help) succeed I'll let you know.
surdu_petru said:
Just to joke a little : with only 2GB RAM & 100GB storage, you'll be able to build the whole source code of Android MM or N, in a few days
Now really, you need at least 16GB DDR3/4 and minimum 200GB storage ( preferably SSD ) , because you need to set ccache to 50GB or maybe 100GB ! If you have only 100GB and setting ccache to 50GB, with only 50GB storage free - you'll never be able to build the whole source code !
+1
Click to expand...
Click to collapse
:laugh: :laugh: I know I exaggerated, but I just use 8GB of ddr2 and a 250GB HDD, repo sync takes approximately 2 hours and building the rom somewhere like 3:45-4:30 hours
This sounds like april fools! Dude that doesn't know anything wants to spear a dev team? Maybe this is hi620softs other account? :silly::silly:
This is the thread for the unofficial builds for CM 14.1.
I'm using Nightcore500's device/kernel trees he created for LineageOS 14.1 so of course massive thanks and kudos to Nightcore500 for getting those working!! It's much easier to use another set of trees than manually convert the M8 trees to fit this phone!
Anyway this is the first build and it built. I have no idea whether it works or not as am not sure whether to test it on my only phone (!) but I think I probably will anyway! :silly:
It's attached on this post and I'll add more detail later on.
Cheers!
CM14.1 08-05-2017
A question, can you please explain why you use the source code from nightcore and open a second thread in this you also provide CM / Lineage 14.1? That makes zero sense? oO
Finusfix said:
A question, can you please explain why you use the source code from nightcore and open a second thread in this you also provide CM / Lineage 14.1? That makes zero sense? oO
Click to expand...
Click to collapse
Ha! I haven't been reading the news...
May well be. Nevertheless, you can ask first if he is not already planning to publish the ROM if he already provides the source code for it.
I would not find it at least nice when i work hard on a project and then someone takes me away.
As long as nightcore is working on Cyanogenmod and / or Lineageos it should also be his work. This is one of the first code of honor of any xda developers. (Or generally any developers)
Please be so fair.
Any other type of ROM is open for you like Resurrection Remix, dirtyunicorns and so on.
This thread only creates confusion.
Tbf Soenetsi has done a lot of work for our phone so no need to be so harsh
How does this version perform?