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.
Related
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
Here is my build of lollipop for the T800. it's useable in so far as being able to see what it's like.
It has been posted in here because it is not ready for prime time and I figured others might want to have a look. It has bugs and doesn't fully work so might not be suitable for daily use, but you decide
How to Install
Download zip to phone
Reboot to recovery
Flash CM12 zip
Flash gapps
Reboot
The first reboot may take a while so be patient.
Known Issues
Some slight graphical issues
Camera gives an error after each picture, just reopen to use use again.
Hardware keys aren't disabled if you use on-screen keys (but they are dimmed)
Video/Movies/Youtube won't play
Download Link
lonespeaker version (10th Dec) -- https://mega.co.nz/#!4ckg0BwB!AhpucIfXJ6P-Y1z7mxQgKkWzHVg4dEhkwiVEUvM3gyA
barracuda7 version -- http://forum.xda-developers.com/showpost.php?p=57300243&postcount=22
You can use any gapps but I use these ones -- https://s.basketbuild.com/gapps
Source Code
My CM12 Repo -- https://github.com/lonespeaker?tab=repositories
CyanogenMod -- https://github.com/CyanogenMod
Thanks and Credits
Thanks to @crpalmer (https://github.com/crpalmer) for the picassowifi files without whom this would not be possible.
Thanks to @Barracuda77777 (https://github.com/barracuda7), @eousphoros (https://github.com/eousphoros) for providing help and fixes here and on github.
// end
Changelog
Thanks to @Barracuda77777 - Post #22 contains an alternative version that he is working on.
http://forum.xda-developers.com/showpost.php?p=57300243&postcount=22
10th Dec
Camera is now working! But.... there is an error after you take a picture, so you need to reopen the camera app to take another picture, but at least you can take a picture!
Updated to CM12 sources 10th Dec 15:00 GMT.
7th Dec
Recents button now works. If you enable onscreen buttons, then the hardware buttons still work, albeit with the backlight on them turned off.
The sdcard seems to work, I had to reformat mine to get it recognised.
Wifi is now working thanks to barracuda7
Hoping T700/8.4 is not far behind. Can't test, but great job anyways. [emoji2]
Awesome job buddy!
hhairplane said:
Hoping T700/8.4 is not far behind. Can't test, but great job anyways. [emoji2]
Click to expand...
Click to collapse
T700 got it first check original development. Great work lone speaker on getting lollipop to the t800.
Looking forward to it !!! Great job !
Having more of a nightmare trying to work out how to use git and github to put my changes up there lol
My work is based off @crpalmer excellent work and with some not too big changes but I'd like to fork his work and then push my changes to keep his credits, but I'm having a nightmare
lonespeaker said:
Having more of a nightmare trying to work out how to use git and github to put my changes up there lol
My work is based off @crpalmer excellent work and with some not too big changes but I'd like to fork his work and then push my changes to keep his credits, but I'm having a nightmare
Click to expand...
Click to collapse
I fixed WIFI, Uploading now
Barracuda77777 said:
I fixed WIFI, Uploading now
Click to expand...
Click to collapse
excellent, how did you do it?
This is looking great! Awesome work. I realise its a very early build but hows the speed of it?
lonespeaker said:
excellent, how did you do it?
Click to expand...
Click to collapse
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Barracuda77777 said:
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Click to expand...
Click to collapse
I've been playing with ones from various places and no luck so Im so glad you figured it out. I will fork to my git and then try and work out how to add my own fixes to that fork and maybe be able to contribute this time lol
lonespeaker said:
I've been playing with ones from various places and no luck so Im so glad you figured it out. I will fork to my git and then try and work out how to add my own fixes to that fork and maybe be able to contribute this time lol
Click to expand...
Click to collapse
do you mind if I post my rom in this thread?
Barracuda77777 said:
do you mind if I post my rom in this thread?
Click to expand...
Click to collapse
No not at all, go for it
i
lonespeaker said:
No not at all, go for it
Click to expand...
Click to collapse
thank you
here is the build with WIFI working:
cm-12-20141206-UNOFFICIAL-chagallwifi.zip
here is the link to the vendor files
Also, like lonespeaker, l have borrowed heavily from @crpalmer to get this rom up and going, please thank him and also if you wish to donate to him that would be great, without him there would have been no LP rom yet
Barracuda77777 said:
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Click to expand...
Click to collapse
Always the blobs. Some day maybe we will get source for some of this stuff.
Would a build be possible for 805 as well?
Which gapps should I use...can you point me to it? Thanks
naomile said:
Which gapps should I use...can you point me to it? Thanks
Click to expand...
Click to collapse
Im pretty sure you need to use the lollipop gapps since cm12 is lollipop. http://highonandroid.com/android-apps/download-android-5-0-lollipop-gapps/
This is very promising . fun to give it a go. Thankyou for you hard work guys. As said in the OP not ready for daily driver yet. One thing I noticed as I could at the moment its all about smoothing out the bugs. The recents apps button doesn't work. (Although I did select in options to double press home button to bring up recent apps to get around it. On screen buttons disabled
Hello XDA,
As all of you may know there is a 4G LTE version of the Moto G 2nd Generation, better known under the model number XT1072 and XT1079. Unfortunately almost all ROMs are created for the titan. While the titan ROMs boot just fine because of the almost exact HW, when installing those ROMS we don't get 4G and the speakers and earpeace, especially while calling, get unusable.
So instead of sitting on my butt and asking LUK to develop a 4G patch, can anyone guide me ? I know how to setup the SDK and know the theory about compiling from source but have never done it. Do we have to recompile something or can I just replace certain files with some other files from the (one and only) CM12.1 port for the THEA ?
This must be doable I think.
soulaiman said:
Hello XDA,
As all of you may know there is a 4G LTE version of the Moto G 2nd Generation, better known under the model number XT1072 and XT1079. Unfortunately almost all ROMs are created for the titan. While the titan ROMs boot just fine because of the almost exact HW, when installing those ROMS we don't get 4G and the speakers and earpeace, especially while calling, get unusable.
So instead of sitting on my butt and asking LUK to develop a 4G patch, can anyone guide me ? I know how to setup the SDK and know the theory about compiling from source but have never done it. Do we have to recompile something or can I just replace certain files with some other files from the (one and only) CM12.1 port for the THEA ?
This must be doable I think.
Click to expand...
Click to collapse
It's easy but I'm not going to help in dirty ports. Build roms from source instead, this is my recommendation.
If you want to learn how to build roms from source I can help you but you'll need to have Linux machine to do that.
LuK1337 said:
It's easy but I'm not going to help in dirty ports. Build roms from source instead, this is my recommendation.
If you want to learn how to build roms from source I can help you but you'll need to have Linux machine to do that.
Click to expand...
Click to collapse
Thanks for the reply Luk, I also think that building from source is the same. I have followed many, many guides but somehow the part where I have to point to the thea specific HW blobs fails. The extract-files.sh points to ./../../$VENDOR/msm8226-common/setup-makefiles.sh [email protected] wich I understand is the motorola folder in the WORKING_DIRECTORY. Somehow I can't find the right repo on github to point it at.
Sorry for the noobish Q... There is a first time for everything.
EDIT: I wanted to say that I think that porting from source is better, not the same.
soulaiman said:
Thanks for the reply Luk, I also think that building from source is the same. I have followed many, many guides but somehow the part where I have to point to the thea specific HW blobs fails. The extract-files.sh points to ./../../$VENDOR/msm8226-common/setup-makefiles.sh [email protected] wich I understand is the motorola folder in the WORKING_DIRECTORY. Somehow I can't find the right repo on github to point it at.
Sorry for the noobish Q... There is a first time for everything.
EDIT: I wanted to say that I think that porting from source is better, not the same.
Click to expand...
Click to collapse
You could use blobs from TheMuppets instead: https://github.com/TheMuppets/proprietary_vendor_motorola
LuK1337 said:
You could use blobs from TheMuppets instead: https://github.com/TheMuppets/proprietary_vendor_motorola
Click to expand...
Click to collapse
Thanks !!
I was really confused and got the CM12 branch instead the first time. Lol now I feel like a noob haha (wich I am when it comes to developing).
Will post here if I have any Questions/errors (that google can't help me with).
:good:
soulaiman said:
Thanks !!
I was really confused and got the CM12 branch instead the first time. Lol now I feel like a noob haha (wich I am when it comes to developing).
Will post here if I have any Questions/errors (that google can't help me with).
:good:
Click to expand...
Click to collapse
Also don't use git clone manually, make your local_manifests xml instead.
LuK1337 said:
Also don't use git clone manually, make your local_manifests xml instead.
Click to expand...
Click to collapse
Oh okay, I will look into that in a minute.
Now I got an issue that really got my head hurting... When I do the lunch command, my Moto G isn't in the list of devices... What Am I doing wrong ?
I have got a directory called thea in WORKING_DIRECTORY/device/moto/thea
I have got also an old thea directory (cm12.1) in WORKING_DIRECTORY/thea and WORKING_DIRECTORY/thea2
All the blobs from TheMuppits repo are in de device/moto/thea dir
All the poperiatary blobs are also in the XT907 dir...
I've done the
Code:
cd /device/moto/thea
init android-5.1.1_rx
repo sync
and let it finish without errors.
Once I get over this I will be good to go.
Oh, and thanks for sharing the knowledge !
soulaiman said:
Oh okay, I will look into that in a minute.
Now I got an issue that really got my head hurting... When I do the lunch command, my Moto G isn't in the list of devices... What Am I doing wrong ?
I have got a directory called thea in WORKING_DIRECTORY/device/moto/thea
I have got also an old thea directory (cm12.1) in WORKING_DIRECTORY/thea and WORKING_DIRECTORY/thea2
All the blobs from TheMuppits repo are in de device/moto/thea dir
All the poperiatary blobs are also in the XT907 dir...
I've done the
Code:
cd /device/moto/thea
init android-5.1.1_rx
repo sync
and let it finish without errors.
Once I get over this I will be good to go.
Oh, and thanks for sharing the knowledge !
Click to expand...
Click to collapse
Your directories are bit off, it should be looking like this.
CM/device/motorola/msm8226-common
CM/device/motorola/thea
CM/device/qcom/sepolicy
CM/device/qcom/common
CM/kernel/mototola/msm8226
CM/vendor/motorola
Don't forget about rest of CM source :3
LuK1337 said:
Your directories are bit off, it should be looking like this.
CM/device/motorola/msm8226-common
CM/device/motorola/thea
CM/device/qcom/sepolicy
CM/device/qcom/common
CM/kernel/mototola/msm8226
CM/vendor/motorola
Don't forget about rest of CM source :3
Click to expand...
Click to collapse
Oh okay got ya. Do I have to do some kind of refresh command when I touch the folders ?
soulaiman said:
Oh okay got ya. Do I have to do some kind of refresh command when I touch the folders ?
Click to expand...
Click to collapse
If you're building CM then all you have to do is to get vendor, do envsetup.sh and just brunch thea.
LuK1337 said:
If you're building CM then all you have to do is to get vendor, do envsetup.sh and just brunch thea.
Click to expand...
Click to collapse
I'm trying to build an AOSP build like yours to learn. I'm following this guide:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I guess it is similar in steps as what you described ?
Even with all the files in the correct directories when I exec the lunch command it doesn't list the moto G. See screenshot.
soulaiman said:
I'm trying to build an AOSP build like yours to learn. I'm following this guide:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I guess it is similar in steps as what you described ?
Even with all the files in the correct directories when I exec the lunch command it doesn't list the moto G. See screenshot.
Click to expand...
Click to collapse
You won't get clean AOSP to build, also u messed up directories as you put vendor in device.
If you have hangouts you can add me ( https://plus.google.com/108108436166506337243 ) so I could help you live.
LuK1337 said:
You won't get clean AOSP to build, also u messed up directories as you put vendor in device.
If you have hangouts you can add me ( https://plus.google.com/108108436166506337243 ) so I could help you live.
Click to expand...
Click to collapse
Thanks for all the help man, really appreciate it !
Yeah stupid fault of my part. Will try it.
About Hangouts: My hangouts app allways FC's on me so that will be for another day. I'll add you asap ! Thanks!
Also it is 1:45AM here so
soulaiman said:
Thanks for all the help man, really appreciate it !
Yeah stupid fault of my part. Will try it.
About Hangouts: My hangouts app allways FC's on me so that will be for another day. I'll add you asap ! Thanks!
Also it is 1:45AM here so [emoji14]
Click to expand...
Click to collapse
K, I'm in the same time zone fyi.
Hey, as alot of us know many people have left this phone and moved on to the cooler more exciting phones. and are busy with life.....id like to request a guide for the ones that would like to make some creation and learn how to build...for the love of this phone ^-^and that have some knowledge atleast
Xendrix said:
Hey, as alot of us know many people have left this phone and moved on to the cooler more exciting phones. and are busy with life.....id like to request a guide for the ones that would like to make some creation and learn how to build...for the love of this phone ^-^and that have some knowledge atleast
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:
denny.hell said:
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:
Click to expand...
Click to collapse
Ok cool i just pulled that same guide up, ill try it out and see where i get!
Sent from my iPhone using Tapatalk
Xendrix said:
Ok cool i just pulled that same guide up, ill try it out and see where i get!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you need help with the rejects just ask. I'm sure I could spare some time to help out
denny.hell said:
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:
Click to expand...
Click to collapse
That was really not all that great of an instruction on how to get started with rom building because for 1 unless you have a really super fast computer trying to do that in a VMWARE is going to take forever because the first compile and build takes hours upon hours I'm not kidding when I said you needed to download the entire CyanogenMod or AOSP source code and apparently from all the changes people have made its up over 13GB which is huge mind you the first build is going to give quite a few errors which you'll need to fix by going into your github and making changes to the specific file that needs changing and then repo sync or just change it on your local computer first then push it to github.. You did fork the device tree to your own github right? Then you have to download the device tree source to your local pc in order to even begin building anything. They also need to be in the correct spot by the way or the build is gonna throw an error that it can't find / or so and so doesn't exist.. By the way the 3 device tree files you're gonna need are "Device, Vendor and Kernel.."..
https://wiki.cyanogenmod.org/w/Development
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
MrMike2182 said:
That was really not all that great of an instruction on how to get started with rom building because for 1 unless you have a really super fast computer trying to do that in a VMWARE is going to take forever because the first compile and build takes hours upon hours I'm not kidding when I said you needed to download the entire CyanogenMod or AOSP source code and apparently from all the changes people have made its up over 13GB which is huge mind you the first build is going to give quite a few errors which you'll need to fix by going into your github and making changes to the specific file that needs changing and then repo sync or just change it on your local computer first then push it to github.. You did fork the device tree to your own github right? Then you have to download the device tree source to your local pc in order to even begin building anything. They also need to be in the correct spot by the way or the build is gonna throw an error that it can't find / or so and so doesn't exist.. By the way the 3 device tree files you're gonna need are "Device, Vendor and Kernel.."..
https://wiki.cyanogenmod.org/w/Development
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Click to expand...
Click to collapse
Yes, everything you said is correct. I was only giving him a starting point. I know that porting, in this case patching, is a lot more easier than building, if done properly. If he wants to build and to learn a lot of stuff I personally advice him to follow your advice.
But in the end it's up to him. At least now he has two starting points. :highfive:
denny.hell said:
Yes, everything you said is correct. I was only giving him a starting point. I know that porting, in this case patching, is a lot more easier than building, if done properly. If he wants to build and to learn a lot of stuff I personally advice him to follow your advice.
But in the end it's up to him. At least now he has two starting points. :highfive:
Click to expand...
Click to collapse
That's true, 2 starting points is better than none.. I don't necessarily like "patching" others work because you never really know how they made it or if it has problems which is why I just start from scratch.
Yes starting from scratch was initially what i wanted but i looked around on XDA university for a week and that helped get me to learn about setting up Vm, installing android sdk through terminal ETC and repo init repo sync, downloading repositories and other source codes.....BUT my thing is wanting to learn how patch errors and need more on hands experience for setting up build environment
Sent from my iPhone using Tapatalk
Hello, everyone.
I noticed, there are many custom roms, but not that many for the SM-T505. Is it because it's newly released, or are there other reasons?
Yes, this is a new device and many people are probably waiting for the Black Friday/Cyber Monday deals to grab one. I just grabbed one for $150 on Amazon, a steal compared to something like a Fire tablet IMO. This is a low-end tablet, so there won't be as much focus on it as say a flagship phone. But thankfully it's already been unlocked and rooted, so the next step will be to get TWRP on it, and then custom ROM development can start to pick up on it. Don't expect any updates before the end of the year for custom ROMs though, it will likely take time to have TWRP up and running on it, but I am hopeful that we will see good things on this tablet in 2021
Without kernel sources it won't happen. See https://opensource.samsung.com/uploadSearch?searchValue=sm-t505 and https://opensource.samsung.com/uploadSearch?searchValue=sm-t500.
You can request them on that page. I did it a few times but no response so far.
paziusss said:
Without kernel sources it won't happen. See https://opensource.samsung.com/uploadSearch?searchValue=sm-t505 and https://opensource.samsung.com/uploadSearch?searchValue=sm-t500.
You can request them on that page. I did it a few times but no response so far.
Click to expand...
Click to collapse
Interesting... is it just me or is there no button to start an inquiry?
EDIT: Found it... just posted an Inquiry.
Watching!! I just bought the T500.
jlang11 said:
Watching!! I just bought the T500.
Click to expand...
Click to collapse
Just got an answer from Samsung, but don't get to excited. It was just an automated answer, that they received my inquiry. So stay tuned...
https://opensource.samsung.com/uploadSearch?searchValue=t500 gives you a 514mb file with kernel and vencor files.
Maybe both 505 and 500 are similiar enough to get you started
Sources are available: https://opensource.samsung.com/uploadSearch?searchValue=sm-t500
They include a toolchain in kernel tree, broken KConfigs and a lot of junk. I will try to clean a bit a mess and update a lean kernel tree to github
paziusss said:
Sources are available: https://opensource.samsung.com/uploadSearch?searchValue=sm-t500
They include a toolchain in kernel tree, broken KConfigs and a lot of junk. I will try to clean a bit a mess and update a lean kernel tree to github
Click to expand...
Click to collapse
Will you also do a diff against the upstream version so we can see what they changed?
selemine said:
Will you also do a diff against the upstream version so we can see what they changed?
Click to expand...
Click to collapse
Sure, but I'm going to remove the toolchain from the kernel tree since the beginning. It takes About 1GB alone and I don't want to have it on git refs because it will still take a lot of space even if removed.
The rest of changes will be available on github.
paziusss said:
Sure, but I'm going to remove the toolchain from the kernel tree since the beginning. It takes About 1GB alone and I don't want to have it on git refs because it will still take a lot of space even if removed.
The rest of changes will be available on github.
Click to expand...
Click to collapse
It's been a long time, since i took up building custom roms and forgot about it for a while... if the kernel is cleansed from all the BS no one needs, that would be awesome.
There are a lot of small changes to comments and changes of 2 characters in a line. Wonder if they backported stuff there.
Kernel of the SM-T505 was just released...
If this is of any relevance, the download is 'just' 200MB... i wonder why.
The Platform Archive is mostly identical, just a few text files with notes and copyright were missing.
The Kernel Package as well, just small changes to netfilter and
a new defconfig file.
Defconfig for both devices also is more or less the same
gta4lwifi_eur_open_defconfig is missing one line compared to gta4l_eur_open_defconfig
CONFIG_SAMSUNG_FREECESS=y
Guess the difference comes from the toolchain mentioned above.
@paziusss
How far have you come?
Would be great if we had something clean to start a twrp and easier rooting
selemine said:
@paziusss
How far have you come?
Would be great if we had something clean to start a twrp and easier rooting
Click to expand...
Click to collapse
Sorry, I have a very bad internet connection (uplink it is ~50-100KiB/s)
I created the repo a month ago: https://github.com/pazos/android_kernel_samsung_gta4lwifi
,tried to push and failed. Never tried again until now, but it is still failing.
So, if somebody is nice enough to dump the contents of the SM-T500 kernel in a github repo, I can fork and submit the patches without having to upload the whole thing myself.
paziusss said:
Sorry, I have a very bad internet connection (uplink it is ~50-100KiB/s)
I created the repo a month ago: https://github.com/pazos/android_kernel_samsung_gta4lwifi
,tried to push and failed. Never tried again until now, but it is still failing.
So, if somebody is nice enough to dump the contents of the SM-T500 kernel in a github repo, I can fork and submit the patches without having to upload the whole thing myself.
Click to expand...
Click to collapse
Here you go
jayzarry84 said:
Here you go
Click to expand...
Click to collapse
Thank you! It helped.
I had to apply the patch manually, so everything is in a single commit, but should be easy for others to understand what each chunk of code does.
Here you go: https://github.com/pazos/android_kernel_samsung_gta4lwifi
paziusss said:
Thank you! It helped.
I had to apply the patch manually, so everything is in a single commit, but should be easy for others to understand what each chunk of code does.
Here you go: https://github.com/pazos/android_kernel_samsung_gta4lwifi
Click to expand...
Click to collapse
Just realized I didn't upload the Platform folder contents. It's uploading as we speak
jayzarry84 said:
Just realized I didn't upload the Platform folder contents. It's uploading as we speak
Click to expand...
Click to collapse
I really have to ask, can i use this to build a custom rom for the SM-T505 as well?