Related
hey guys, i am just trying tout some compiling with cm9, i synced up all the files needed and when i type lunch and choose cm_cooper it comes up with this .... Device cooper not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
i am using waylandace's repo, i have previously built cm9 with his repo before?? how can i fix this error?
t
winxuser said:
hey guys, i am just trying tout some compiling with cm9, i synced up all the files needed and when i type lunch and choose cm_cooper it comes up with this .... Device cooper not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
i am using waylandace's repo, i have previously built cm9 with his repo before?? how can i fix this error?
t
Click to expand...
Click to collapse
Try
Brunch
Cyanogen_cooper-userdebug
Brunch will automaticly build zip file to
Sent from my ST25i using xda app-developers app
ok thanks i will try it next time i boot into linux,, its weird because i have used the same device config before
There have been two submissions to CM code review (31787 here and 31039 here) that have not been merged for various reasons. The first allows for sysfs gamma control (at kernel level) and the second provides an additional menu in settings containing RGB display controls and vibration settings. At present there is no support within the CM vanilla system UI settings to modify gamma values (with or without MakoParts), though there are apps (notably Faux123's) that will provide this in concert with a kernel including a sysfs interface that allows it. These are potentially very complex adjustments and not really of interest to the majority of device users, however there does seen to be an appetite for a slimmed down alternative. I (and others) have been cherry-picking the two code commits and using init.d to provide a simple solution, though on top of that it does seem that a GUI setting method would be of value, if only to fiddle with levels prior to settling on values to include in a boot script.
Consequently, I have extended the original MakoParts (MakoParts+ if you will!) in adding a basic 6 value gamma (amplitude) control UI within the existing 'Advanced' menu.
To implement it in your own builds you will need to;
Cherry-pick the two code review commits (see above), if you haven't already (UPDATE 24/05/13 - Use Patch Set 6 for change 31039). Alternatively, you can get them from my repo here for the kernel and here for the device. This gives you the original MakoParts and the gamma support.
Cherry-pick MakoParts+
Cherry-pick hev88's commit here (UPDATED 09/07/13 - redirected link) to allow your settings to stick following reboot.
and then make.
Gamma settings will not stick following a reboot so once you've found some you like you'll need an init.d/ userinit.d script. There's a good guide on _motley's thread here though do make sure that you refer to kgamma_r. kgamma_g and kgamma_b rather than kgamma_red, kgamma_green and kgamma_blue (those are franciscofranco's interface variables I believe).
(UPDATE 04/06/2013 - Thanks to hev88 for spotting my original omission. His commit (now 3. above) will stick your settings following reboot.)
As I mentioned, gamma control can be very in-depth and this is not intended as an alternative to a full blown control app. Saying that, there is valuable reading to be done and user comments in Ngo93's thread here and tested settings in the accompanying spreadsheet (Basic tab) here
Thanks and acknowledgement to all mentioned.
Evaluation Build
I have provided a download link to a (fairly) vanilla CM10.1 build of my own including the modifications - https://www.dropbox.com/s/ebb7iteqo1ov5yn/cm-10.1-20130514-UNOFFICIAL-mako.zip
Have never CP'd from Github before. Using https://github.com/Daniel-GT/android_device_lge_mako/commit/8793e557c1acba7b7f951fced0a4eae25d28a6f4 as an example, after repo sync, would I do the following:
Code:
cd ~/cm10.1/android_device_lge_mako
git remote add https://github.com/Daniel-GT/android_device_lge_mako
git fetch
git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4
Cheers.
CMNein said:
Have never CP'd from Github before. Using https://github.com/Daniel-GT/android_device_lge_mako/commit/8793e557c1acba7b7f951fced0a4eae25d28a6f4 as an example, after repo sync, would I do the following:
Code:
cd ~/cm10.1/android_device_lge_mako
git remote add https://github.com/Daniel-GT/android_device_lge_mako
git fetch
git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4
Cheers.
Click to expand...
Click to collapse
Easiest way is;
Code:
git fetch git://github.com/Daniel-GT/android_device_lge_mako.git && git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4
As Andrew said on Google+ you could also patch with git am... if you get really stuck you could apply the following;
Code:
git apply <your-path-to-the-attached-file>/MakoPartsPLUS.patch
All should be run from a terminal opened in your source "mako" directory. Make sure you have the original MakoParts in your source already or it won't work.
Daniel_GT said:
Easiest way is;
Code:
git fetch git://github.com/Daniel-GT/android_device_lge_mako.git && git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4
As Andrew said on Google+ you could also patch with git am... if you get really stuck you could apply the following;
Code:
git apply <your-path-to-the-attached-file>/MakoPartsPLUS.patch
All should be run from a terminal opened in your source "mako" directory. Make sure you have the original MakoParts in your source already or it won't work.
Click to expand...
Click to collapse
needs rebase now to go with new patch set http://review.cyanogenmod.org/#/c/31039/
hev88 said:
needs rebase now to go with new patch set http://review.cyanogenmod.org/#/c/31039/
Click to expand...
Click to collapse
I'll look at it and review. I had thought the original commit was done with changes.
Sent from my Nexus 4 using xda app-developers app
Daniel_GT said:
I'll look at it and review. I had thought the original commit was done with changes.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. So did I. Just a name change really and dropped a few strings. I tried to mod your patch but I keep getting an error on strings.xml
Sent from my Nexus 4
hev88 said:
Yeah. So did I. Just a name change really and dropped a few strings. I tried to mod your patch but I keep getting an error on strings.xml
Sent from my Nexus 4
Click to expand...
Click to collapse
On initial inspection I can't see anything fundamentally "new" in Patch Set 7 or 8. I've asked the committer for his rationale on Gerrit. I don't think there are any conflicts with any/ all recent CM commits so you should be OK if you pick set 6 (or the commits from my repo) for the timebeing until I've looked at it properly - OP temporarily updated.
Daniel_GT said:
On initial inspection I can't see anything fundamentally "new" in Patch Set 7 or 8. I've asked the committer for his rationale on Gerrit. I don't think there are any conflicts with any/ all recent CM commits so you should be OK if you pick set 6 (or the commits from my repo) for the timebeing until I've looked at it properly - OP temporarily updated.
Click to expand...
Click to collapse
I've compared Patch Set 6 side-by-side with 7/8 and the update does nothing more than clean up a bit (which I've already done within MakoParts+), re-base (basically reference it against the current CM repo timeline, the original is from January) and change the package name and a UI heading. I'm not minded to apply the changes to MakoParts+, I see little point in doing so until the committer tells me what he had in mind other than change for changes sake, so please either;
Stick with patch 6 and disregard 7/8 entirely. This will effect the functionality of MakoParts and MakoParts+ not a jot.
Cherry-pick the original commits from my repo as before, and forget all about this.
I've attached the two diffs if anyone wants to have a look and see what I mean.
im sure its not just me but it seems you have to add some code to DeviceSettings/src/com/cyanogenmod/settings/device/Startup.java in order for settings to stick on reboot:
GammaTuningPreference.restore(context);
not sure if more is needed but i just noticed today that settings today that it doesnt stick after reboot and decided i woud take a look.
Just made a fresh build and adding that keeps your settings after a reboot.
Sent from my Nexus 4
hev88 said:
Just made a fresh build and adding that keeps your settings after a reboot.
Sent from my Nexus 4
Click to expand...
Click to collapse
Well spotted, sometimes you get so close to these things you can't see the wood for the trees. Have you added the line via a separate commit on your own repo, and are you still using the MakoParts project name (you mentioned DeviceSettings)? If so I'm happy to update the OP with a link to your work.
Sent from my Nexus 4 using Tapatalk 4 Beta
Daniel_GT said:
Well spotted, sometimes you get so close to these things you can't see the wood for the trees. Have you added the line via a separate commit on your own repo, and are you still using the MakoParts project name (you mentioned DeviceSettings)? If so I'm happy to update the OP with a link to your work.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It was a copy pasta error on my part I still use the patch you made and just now manually added the fix to survive a reboot to source code. I started to make a new patch for DeviceSettings but I got stuck on one part... I am not to great at git Lol, I got stuck on strings.xml and kinda gave up... But it is just a one line fix on top of your patch that you made.
Sent from my Nexus 4
hev88 said:
It was a copy pasta error on my part I still use the patch you made and just now added the fix to survive a reboot. I started to make a new patch for DeviceSettings but I got stuck on one part... I am not to great at git Lol, I got stuck on strings.xml and kinda gave up... But it is just a one line fix on top of your patch that you made. I can send you what I have so far later tonight or tomorrow after I finish catching up on some Dexter
Sent from my Nexus 4
Click to expand...
Click to collapse
OK Don't worry, I'll add the change as a new commit and credit you.
Sent from my Nexus 4 using Tapatalk 4 Beta
https://github.com/hev88/android_device_lge_mako/tree/cm-10.1-var1/MakoParts
i just added the one line to keep settings after reboot... im exploring right now trying to figure out how to git around here lol... but if you dont get to it anytime soon ill try to make your patch play nice with the most recent patch set on CM's gerrit... gotta start learning some time, this will be my new project on my days off. i just stomped out a bug on ubuntu so this will keep me occupied for the time being
#VinoIsEvil
OP updated.
Daniel_GT said:
OP updated.
Click to expand...
Click to collapse
sent you a pull request on github. repo works fine but it wont let me cherry-pick it my commit... might have missed something while adding commit from terminal but it builds fine
hev88 said:
sent you a pull request on github. repo works fine but it wont let me cherry-pick it my commit... might have missed something while adding commit from terminal but it builds fine
Click to expand...
Click to collapse
You have been busy! I'll have a proper look over the next few days... I don't really follow your cherry-pick problem? Are you trying to fetch from the SSH address, not the public git/ HTTPS URL?
Sent from my Nexus 4 using Tapatalk 4 Beta
Daniel_GT said:
You have been busy! I'll have a proper look over the next few days... I don't really follow your cherry-pick problem? Are you trying to fetch from the SSH address, not the public git/ HTTPS URL?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i have it the same as you do on the previous page. if i remember right it said something about cherry-pick failed no HEAD?
idk i gave up on that and just forked cm, cherry-picked latest mako parts commited it to repo edited it based on your patch and just replaced cms device repo with my in my build directory now its two less cherries i have to pick before i build. like i said im still new at this whole github deal so it could just be me not being patient
Daniel_GT said:
You have been busy! I'll have a proper look over the next few days... I don't really follow your cherry-pick problem? Are you trying to fetch from the SSH address, not the public git/ HTTPS URL?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
hev88 said:
i have it the same as you do on the previous page. if i remember right it said something about cherry-pick failed no HEAD?
idk i gave up on that and just forked cm, cherry-picked latest mako parts commited it to repo edited it based on your patch and just replaced cms device repo with my in my build directory now its two less cherries i have to pick before i build. like i said im still new at this whole github deal so it could just be me not being patient
Click to expand...
Click to collapse
Not sure if you're talking about something else but I've been cherry-picking your commit with no problem using
Code:
git fetch git://github.com/hev88/android_device_lge_mako.git && git cherry-pick 17dfcbdc60719bb0147240efcbb906f4987c95fa
I'm just wondering if there is one JB rom that has everything working. Kfazz has one that the FM radio works, but the Play Store doesn't. He has another one where the Store works but the Radio doesn't. Energic has done some interesting things with these. And somewhere in there, there is a version that some folks say the WiFi isn't working. I have installed all of them. I like bits and pieces of them all. Has anybody put all the pieces together? Alternately, is there a way that I can look at the differences between them and cherry pick out the best from each?
I hope somebody is out there to answer my plea.
pabeader said:
I'm just wondering if there is one JB rom that has everything working. Kfazz has one that the FM radio works, but the Play Store doesn't. He has another one where the Store works but the Radio doesn't. Energic has done some interesting things with these. And somewhere in there, there is a version that some folks say the WiFi isn't working. I have installed all of them. I like bits and pieces of them all. Has anybody put all the pieces together? Alternately, is there a way that I can look at the differences between them and cherry pick out the best from each?
I hope somebody is out there to answer my plea.
Click to expand...
Click to collapse
Currently there is no Jelly Bean ROM that has everything working 100% correctly, however if you wanted to you could look at each developers that created a Jelly Bean ROM github sources for that ROM and then using git and the Android build system cherry pick the commits that work and try build them in a new ROM. If each developer doesn't have a github you could also try and asking them for the repository where they store there source code.
shimp208 said:
Currently there is no Jelly Bean ROM that has everything working 100% correctly, however if you wanted to you could look at each developers that created a Jelly Bean ROM github sources for that ROM and then using git and the Android build system cherry pick the commits that work and try build them in a new ROM. If each developer doesn't have a github you could also try and asking them for the repository where they store there source code.
Click to expand...
Click to collapse
Can you give just a little more help? How do I look into the GIT? What program do i use for this?
pabeader said:
Can you give just a little more help? How do I look into the GIT? What program do i use for this?
Click to expand...
Click to collapse
You can look into each developers github (Here is Kfazz's github profile link) by finding there github profile on github by searching for it or if they have it linked on XDA by clicking on their username then select the "View GitHub profile". Use can then use github to browse each developers source repository, the main tools you will be using are Git and Repo to manipulate and cherrypick the various commits. Additionally I would recommend making sure you have acess to a Linux box or are running Linux to make building and working with the source code repository's easier. Also, I would recommend taking a look at this great guide on how to use Repo and this great guide on how to Git.
Since this has been asked a few times
Multi windows support is not in by default
You need to cherry-pick this to include it in your build
https://gerrit.omnirom.org/#/c/53/
thank you,
I added it into my p5110 build, i'll let you know if it works well.
edit:: working well
I won't lie, I plan to build Omni today as my first-ever Android build. It may go hilariously badly, it may go wonderfully. Is it in the command line that I cherry-pick that piece of code? The rest I think I can figure out myself. Thanks in advance.
dibblebill said:
Is it in the command line that I cherry-pick that piece of code?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
chasmodo said:
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
Click to expand...
Click to collapse
You probably will want to do a "repo start" first, otherwise your commit will be clobbered on sync.
e.g. from the root of the source tree:
Code:
repo start work frameworks/base
for more on repo - http://source.android.com/source/using-repo.html
Thank you both. Very helpful. It's wonderful receiving help from the developers, especially since this will be my first build
Sent from my Nexus 10
dibblebill said:
Thank you both. Very helpful. It's wonderful receiving help from the developers, especially since this will be my first build
Sent from my Nexus 10
Click to expand...
Click to collapse
For everybody there was a "first time"
chasmodo said:
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
Click to expand...
Click to collapse
When I execute this using the linked cherry pick, all I get is "fatal: Not a git repository (or any of the parent directories): .git
dibblebill said:
When I execute this using the linked cherry pick, all I get is "fatal: Not a git repository (or any of the parent directories): .git
Click to expand...
Click to collapse
you tried this mate?
Code:
git fetch [url]https://gerrit.omnirom.org/android_frameworks_base[/url] refs/changes/53/53/19 && git cherry-pick FETCH_HEAD
before that u must be inside ~/android/omni/frameworks/base if i im rigth, u get there by
Code:
cd ~/android/omni/frameworks/base
someone correct me if im wrong pls.
makkeonmies said:
you tried this mate?
Code:
git fetch [url]https://gerrit.omnirom.org/android_frameworks_base[/url] refs/changes/53/53/19 && git cherry-pick FETCH_HEAD
before that u must be inside ~/android/omni/frameworks/base if i im rigth, u get there by
Code:
cd ~/android/omni/frameworks/base
someone correct me if im wrong pls.
Click to expand...
Click to collapse
[codegit fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/53/53/19 && git cherry-pick FETCH_HEAD[/code]
Exactly as copied and pated from the cherrypick itself, yep.
I was, however, in ~/android/omni/.repo/projects/frameworks/base, though. Now I got it fixed and inserted. thanks!
on my way to being a ROM hacker/compiler, then later developer
EDIT: Will the sources for this rescync automatically when I repo sync, or will I have to also re-cherry pickk this every few days?
dibblebill said:
[codegit fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/53/53/19 && git cherry-pick FETCH_HEAD[/code]
Exactly as copied and pated from the cherrypick itself, yep.
I was, however, in ~/android/omni/.repo/projects/frameworks/base, though. Now I got it fixed and inserted. thanks!
on my way to being a ROM hacker/compiler, then later developer
EDIT: Will the sources for this rescync automatically when I repo sync, or will I have to also re-cherry pickk this every few days?
Click to expand...
Click to collapse
If you do a "repo start" before cherry-picking, repo will try to automatically rebase when syncing. It will not sync newer patchsets though.
thanks, very useful.
just to know, why isn't it yet merged ?
BENETNATH said:
thanks, very useful.
just to know, why isn't it yet merged ?
Click to expand...
Click to collapse
Because it still has a lot of bugs that need to be worked out?
Unfortunately, since Omni went public, we've had a ton of device support stuff to work with people on, so the more difficult items have temporarily stalled.
Entropy512 said:
Because it still has a lot of bugs that need to be worked out?
Unfortunately, since Omni went public, we've had a ton of device support stuff to work with people on, so the more difficult items have temporarily stalled.
Click to expand...
Click to collapse
sadly i would say.
BBQ was a great timing but people went crazy on omni, which is a good and a bad thing ^^
i've built omni for my device, with the commit, and it's nice, but currently, it's nearly strictly an AOSP, which is a bit frustrating
keep the hard work, courage to all the omni dev !
BENETNATH said:
sadly i would say.
BBQ was a great timing but people went crazy on omni, which is a good and a bad thing ^^
i've built omni for my device, with the commit, and it's nice, but currently, it's nearly strictly an AOSP, which is a bit frustrating
keep the hard work, courage to all the omni dev !
Click to expand...
Click to collapse
Yeah, I would've liked to have polished things a bit more - but the BABBQ was an opportunity we didn't want to miss.
yep,
anyway, great work. what you guys need now is to keep that alive, and to limit the time spent on bringing devices, better enhance the rom.
Rom builders will join the effort for all the rom stuff, especially as it's really easy (i've bring my device in a dozen of minutes, from a CM branch. needs polishing but works)
Does anyone have the last patch set for multiwindow the 4.3 branch? It seems like the past two weeks worth of patches were lost after the Gerrit server hard drive failure, and I just got my first build done yesterday so I'm not sure what I can cherry pick to test out multiwindow. The last comment remaining seems to imply that the last patch set was broken.
https://gerrit.omnirom.org/#/c/1510/
chasmodo said:
https://gerrit.omnirom.org/#/c/1510/
Click to expand...
Click to collapse
That's the 4.4 branch. Time to cherry-pick!
sgt. meow said:
That's the 4.4 branch. Time to cherry-pick!
Click to expand...
Click to collapse
Are you cherry picking back to 4.3 or doing a 4.4 build? Let us know how it goes! I just set up a build this weekend for my N8013 but Gerrit was down so I couldn't get multiwindow, and when it came back the Gerrit ticket was missing two weeks worth of patches as I mentioned so I was feeling like it would be risky to try to apply it.
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero
HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
- HostZero
Click to expand...
Click to collapse
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Roger That!
@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Build Fail. ? Hmm I will submit device tree tommrow for infinix
HostZero said:
Build Fail. ? Hmm I will submit device tree tommrow for infinix
Click to expand...
Click to collapse
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Great!
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Click to expand...
Click to collapse
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?
RendyAK said:
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?
Click to expand...
Click to collapse
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero
Click to expand...
Click to collapse
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.
Nonta72 said:
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.
Click to expand...
Click to collapse
Hmm anyways I have pushed the cm-13.0 device tree too I have upstremed as many files as possible.
https://github.com/d5110-devs
MSF Jarvis said:
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Click to expand...
Click to collapse
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
MSF Jarvis Seems to be compiling and i have ubuntu but.. my package is done! as tree and vendor are ready try to compile.
Here by OFFICIAL TWRP:
https://dl.twrp.me/d5110
RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Click to expand...
Click to collapse
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?
RendyAK said:
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?
Click to expand...
Click to collapse
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
OMG! You guys could provide 3.18, I have used the 3.10 which has come with STOCK 6.0 if you guys can provide MSF will update it!
- HostZero
I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.
HostZero said:
I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.
Click to expand...
Click to collapse
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
WTF! I should do again. C'mon man... I ll do later mostly not now. I will send you tree.zip better you can push it. Because my push is failing.