Related
Hi all,
Having a rooted Nexus one in my hand, I have been playing around with many of the custom ROMs and kernel over the past few months. (Thanks to nandroid backup)
For ROMs, I have been playing around with CM, LeoFroyo, Modaco, Kang-o-rama, ... stock FRF91 deoxed by Geo411m...etc.
For kernel, have been happy in using the intersectRaven's one dated at 0802 (stable one for me...)
Just a few days before, I have setup a Ubuntu... install the jdk 1.5; git; repo; .... and all necessary files for compiling the source from git://android.git.kernel.org/platform/manifest.git -b froyo
Getting the source and compiling are very time consuming jobs because my network speed and computer are not very fast
So, I have successful compile the source, running lunch full_passion-userdebug ; make -j4 for my dual core machine, and find the system.img
I also download and install the dsixda kitchen, based on Leo's ROM, I have replaced it with my newest compiled apps (apks..) and pngs (black status bar ) and also replace the zImage from intersectRaven's kernel into my boot.img. After flashing the ROM in recovery, I am so lucky that my phone can boot up =_= with everything very smooth and OK.
Now, I have a few questions, as a newbie developer (sincerely asking for help~)
1) How can I get the latest google apps (gapps), and where can I get it? Are there any 'source code' for gapps? How to compile them?
2) If I want to get the source again (e.g. get the newest source of browser.apk), how & what command should I use?
3) If I want to modify the system settings, that is "Settings -> About Phone", which file should I modify?
4) After I get the source of AOSP, compilied them, is it mean that I have the rom deoxed? (Because I can see system/apps/ and all apps are breaking down into apks)
5) I enjoy using good things from others (e.g. LeoParts from Leo's ROM. Can I merge it into my rom and re-distribute after that? How?)
6) Is it necessary to sign *all* apk before they can be run on the phone?
7) I use dsixda kitchen and use testsign.jar. Just want to ask will the signing expires? And is it OK to distribute the ROM using test signing?
I know I get so many questions and they are so 'newbie...'. Sincerely hope that experts in this forum can answer my questions.
Once again, thanks all the ROM / Kernel makers in motivating me to custom the AOSP ROM myself.
Many thanks for all of your help.
ardatdat said:
1) How can I get the latest google apps (gapps), and where can I get it? Are there any 'source code' for gapps? How to compile them?
Click to expand...
Click to collapse
GApps are proprietary, closed-source applications... you can get them from http://mirror.kanged.net/gapps/gapps-hdpi-20100814-signed.zip
ardatdat said:
2) If I want to get the source again (e.g. get the newest source of browser.apk), how & what command should I use?
Click to expand...
Click to collapse
repo sync and then rebuild
ardatdat said:
3) If I want to modify the system settings, that is "Settings -> About Phone", which file should I modify?
Click to expand...
Click to collapse
Change the values in build.prop in /system or system.img
ardatdat said:
4) After I get the source of AOSP, compilied them, is it mean that I have the rom deoxed? (Because I can see system/apps/ and all apps are breaking down into apks)
Click to expand...
Click to collapse
AFAIK, yes, they are de-odexed. I believe you need to odex them later if you wish.
ardatdat said:
5) I enjoy using good things from others (e.g. LeoParts from Leo's ROM. Can I merge it into my rom and re-distribute after that? How?)
Click to expand...
Click to collapse
git merge (I forgot the detailed steps), repo sync and build
ardatdat said:
6) Is it necessary to sign *all* apk before they can be run on the phone?
Click to expand...
Click to collapse
Yes, I believe this is a must.
ardatdat said:
7) I use dsixda kitchen and use testsign.jar. Just want to ask will the signing expires? And is it OK to distribute the ROM using test signing?
Click to expand...
Click to collapse
This should be fine... most, if not all, custom ROMs are signed with test keys...
Hope I've been able to help a bit, if not much... have fun building!!! Ask the ROM gurus on twitter...
Thanks, a quick question:
Will repo sync re-download all the source???
I remember I need many hours in download the -b froyo branch.
Any get latest command that only get the difference?
Also, if I only want to get a particular folder, e.g. packages/apps/Browser, what is the command? Thanks.
repo sync takes several hours the first time... but every successive sync is a delta/differential sync... depending on the number of changes in the repository, it could finish in a few minutes. I'm not sure about syncing a particular folder, I just know about syncing a particular branch (which you have done using -b). Need to look it up...
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
acerbix said:
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
Click to expand...
Click to collapse
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
+1 it's a good one and is one of my references too.
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
+1. Great recommendation. Just used it to complete my first build.
Sent from my MB860 using XDA App
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
acerbix said:
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
Click to expand...
Click to collapse
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info - trying it now.
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
acerbix said:
Thanks so much for the info - trying it now.
Click to expand...
Click to collapse
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
ghost_og said:
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
Click to expand...
Click to collapse
Oh okay - I thought I must be doing something stupid so I PM'd you last night rather than post here. So we all can get trackpad working in the kang but not device setting/lock/unlock
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
I tried replacing default.xml in .repo with the one in Atrix dev git repository, and then pulling down the code. That lead to multiple build failure, so I am assuming hte changes in the atrix dev github are not synced with the changes upstream coz vanilla cyanogenmod builds fine.
I am not even getting the "Device Settings" option that shows up in the weekly build, though the trackpad works fine. I'll try looking at the Settings.apk code to see if there is something I am missing.
cmkoj: Do you have a local_manifest.xml that works and gives you a good build? Open to sharing that?
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Right now, I'd settle for one that works for building. I manually overlay files, so that will definitely be easier
t.s.eliot said:
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
Click to expand...
Click to collapse
Lets know if you get it working I'm building too [clobber build just for the heck of it - will keep you posted]
Thanks a ton, cmkoj for all the help/pointers!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
ghost_og said:
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
Click to expand...
Click to collapse
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
acerbix said:
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
Click to expand...
Click to collapse
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
ghost_og said:
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
Click to expand...
Click to collapse
ye i forgot to mention that one lol, i thought its in the fingerprint build though. for my use i manually git cloned the vendor_motorola repo into /working_dir/vendor/ but havent had any luck. regarding the kernel afaik if you put the additional repos into your local_manifest.xml it should use the kernel from there (if one is available). but i dont really think the kernel is needed to be changed, since on my builds i had the authentec.truesuite (or whatever the process for fp is called) running, only the fp unlock/device option were missing (there is a Fingerprintsomething.apk in the vendor repo of atrix dev team that i have had pulled in and built with but it didnt work, so yes im slowly giving up (second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
as for the local_manifest.xml it should look like this http://pastebin.com/ccvVi2k9 for building the gb (that is with nav functioning fp but no unlock) if you want to get unlock to work you need to probably put in the other ones aswell (just by copying the <project path="device/motorola/olympus"
name="Atrix-Dev-Team/android_device_motorola_olympus.git"
remote="gh"
revision="gingerbread"/>
part and changing the name to appropriate and teh revision in all to fingerprint)
thanks go to fattire from the nook color forums who thought me how to make and edit these local_manifest.xml files and i used his file as a template for mine aswell.
i have to admit it im slowly sick of not being able to build one with working fp =/
Guys, see here for what directories to be pulled from atrix-dev-team github vs what to be kept in original CM7:
https://github.com/Atrix-Dev-Team/android/blob/gingerbread/default.xml
crnkoj said:
(second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
Click to expand...
Click to collapse
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
Another workaround is to add the following remote definition:
Code:
<remote name="github-https"
fetch="https://github.com/" />
Then change the project definition to:
Code:
<project path="prebuilt" name="CyanogenMod/android_prebuilt" remote="github-https"/>
Once things are back to normal, you can remove the additional remote, and restore the original manifest.
Click to expand...
Click to collapse
It was provided in the comments section here.
ghost_og said:
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
It was provided in the comments section here.
Click to expand...
Click to collapse
yes thanks, lol, i knew about the fix and had the first part of it done with changing to https, but forgot about the second part, idiot i...
anyhow i resynced and am building now on the other pc with this local manifest http://paste.pocoo.org/show/534837/
UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?
You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point
So should I take those, then make changes to suit the flex?
Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....
Try msg playfulgod and see if he will point you in the right direction
Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.
Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum
I took programming classes, and there were a few units on android.
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link
mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
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.