yashsingh1/xdaforums huggingface dataset:
[LG Optimus G (International)] Haze028:
My understanding is that they are slightly different. I thought clobber removed more, specificly kernel related items, Though I could be wrong.

Here is an example of my understanding of clean vs. clobber, maybe within android there is no difference between the two

Edit* in my experience clean alone does not clear my intermediates errors, which is why I suggested both commands. Though, even if I am right it's still redundant
[LG Optimus G (International)] ronasimi:
My 2 cents probably isn't needed, but make clobber nukes the entire build directory, and will fix errors with intermediates. Make clean just cleans the target dir. When I build CM 11 after any kernel changes it's always make clobber && cmka bacon
[LG Optimus G (International)] ShinySide:
Make clobber and make clean both delete the entire out directory.

http://wiki.cyanogenmod.org/w/Doc:_make_clean_vs_make_clobber
[LG Optimus G (International)] ronasimi:
Would anyone be willing to have a look at these three commits and tell me where I messed it up? I no longer have /storage/emulated/0 available but my internal is still accessible under /storage/emulated/legacy or /storage/emulated/sdcard0, and everything is working. I just really want to know WTH I changed that caused the difference.

Add USG OTG, optimize some EGL stuff

Optimize mount options for /system /data /cache and fixup OTG line

Add USB OTG

I suspect I'm setting something out of order, but I've been looking at this for too long to see it, if that makes sense.
[LG Optimus G (International)] ShinySide:
Take a look at this. It's for the s4 but should help ya a little

http://review.cyanogenmod.org/#/c/55941/
[LG Optimus G (International)] ronasimi:
OK guys, I'm puzzled. Something changed with CM sources yesterday and I can't get a build to go through.

I'm getting:

hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp: In member function 'int omx_vdec::secureDisplay(int)':
hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp:9382:24: error: 'class qService::IQService' has no member named 'securing'
hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp: In member function 'int omx_vdec::unsecureDisplay(int)':
hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp:9407:24: error: 'class qService::IQService' has no member named 'unsecuring'

as the error. The only commit I see on gerrit that looks close is

mm-video: vdec: display: Change in screenRefresh interface

so I tried reverting that commit and building... same error. Is it any error in CM or do I need to change something in my device tree? I made a couple of edits to my BoardConfigCommon ( Add EGL optimization to BoardConfigCommon.mk ) but I've compiled builds that worked with those changes in before.

Any insight is appreciated.

Thanks.

EDIT: I saw something that referred to changing TARGET_QCOM_DISPLAY_VARIANT := caf to TARGET_QCOM_DISPLAY_VARIANT := legacy in BoardConfig... any drawbacks or advantages to doing this?

EDIT 2: There was a commit to display-caf that I don't see on gerritt that looks like it'll fix the problem. repo sync doesn't seem to have grabbed it so I did it manually and I'll post if it fixes it.

EDIT 3: Nope, same problem

EDIT 4: I think it's because I was missing TARGET_QCOM_MEDIA_VARIANT := caf in my BoardConfig. It was building display-caf but media legacy. I'll post w/ updates. stupid caf

EDIT 5: yep, it was the TARGET_QCOM_MEDIA_VARIANT := caf line in my BoardConfig.
[LG Optimus G (International)] mathsz:
Hi,derp question :

When building xenonhd,

a few apk's do not get built. Missing rom control, bluetoothext, wallpapers and such.

Otherwise fully functional, but I'm missing "parts" of the build. Is there somewhere that it has to be defined?

cheers.
[LG Optimus G (International)] xboxfanj:
Probably in the vendor repo. Did you add your device there?
[LG Optimus G (International)] ShinySide:
Ctrl+ h and go into the repo folder/manifests/ and should be in the common.mk or common phone. Wtf it. See if their hashed out
[LG Optimus G (International)] Haze028:
Xboxfanj is right... Guessing you didn't add to vendor/xeonhd/vendorsetup.sh and vendor/xeonhd/products

Take a look there and make sure your device is added in both sports to make sure it builds a full Xeon rom
[LG Optimus G (International)] mathsz:
Wow, vendor. I never would have looked there. The folder is there, I guess I need to make a xenonhd_geeb.mk I see the dependencies to common.mk (call inherit). I looked all over device folder.

mind. Blown.

Vendor. I also see I can change the build name. That's gonna be fun. :D You know, I'm totally getting the jokes that people insert into flashable zip files or build numbers. HEHE.

big thanks
[LG Optimus G (International)] ronasimi:
So I reverted all of my changes, but I'm still missing the /storage/emulated/0 symlink. Can anyone help me out with this?
[LG Optimus G (International)] Haze028:
Not exactly sure what your issue is.. there is no 0 directory anymore? If everything is still working alright, why does it matter? sorry, just curious is all.

you still have the line in your init symlinking storage/emulated/0, so i'm not really sure why you wouldn't have it.

what rom are you building?
[LG Optimus G (International)] ronasimi:
Building CM 11.0, and I know it's a symlink but the fact that CM file manager is hard coded for /storage/emulated/0 and it's missing is driving me nuts!

EDIT: I just realized I probably haven't wiped data since 4.2 or 4.3. Is the missing emulated/0 normal for 4.4.2?
[LG Optimus G (International)] Haze028:
Trying to take a look to see if i can find anything that has changed... one thing i see is your fstab you now have barrier set to 0 where it was set to 1 before.... only just started looking... and i'm not too sure what that option even does/means
[LG Optimus G (International)] ronasimi:
It's an ext4 mount option, and it wasn't in my current build. If you look at the commit history, you'll see the original files. This just started as of 1/12 after I made the changes to fstab and init.rc for USB OTG. I reverted those changes but I'm still having the same problem... kernel and ramdisk are fresh though, so I don't understand what's going on.

barrier=<0|1(*)> This enables/disables the use of write barriers in
the jbd code. barrier=0 disables, barrier=1 enables.
This also requires an IO stack which can support
barriers, and if jbd gets an error on a barrier
write, it will disable again with a warning.
Write barriers enforce proper on-disk ordering
of journal commits, making volatile disk write caches
safe to use, at some performance penalty. If
your disks are battery-backed in one way or another,
disabling barriers may safely improve performance.

EDIT: I also wanted to add that the obb folder is on the root of my storage now for some reason

EDIT 2: well it works fine in normal mode, just not as root with CM file manager. That makes me believe it's related to this issue from CM 10.x - https://jira.cyanogenmod.org/browse/GETCM-45 but I didn't change anything else I don't think...
[LG Optimus G (International)] jblazea50:
Is there a guide to build CFXE for sprint's lg optimus g (lg970)?
[LG Optimus G (International)] Haze028:
Havn't built CFXE myself, but building is pretty much the same across most roms. This guide will lay the ground work for building any rom, just needs some extra edits for specific roms, when it comes to configuring specificly for CFXE, just look at other devices they have and how they were added mimic that using the sprint og repos
[LG Optimus G (International)] jblazea50:
After I sync repo, I am completely lost. Not sure what I need to do for device source and preparing source.

Under codefireXperiment github, there's already device_lge_ls970. I'm wondering if I can just try to build after repo sync.
[LG Optimus G (International)] Haze028:
look in your device folder is there lge/ls970 in there? if not just use the device/vendor/kernel repo that they are using for the 970 from their github.

you need the device ls970 and ls970-common, kernel and the vendor repo to build for the 970.

If you already do have those directories in your source then you should be ready to build.

looking quick at their github, you probably don't have those directories by default. Create a local manifest using their ls970 repos that i mentioned above using this guide then sync the repo again and build away
[LG Optimus G (International)] jblazea50:
after repo synced, i noticed there's folders for the following: ls970, ls970 common, kernel (folder labeled gproj, not ls970). I did not see vendor so does that mean that I should only do a local_manifest for vendor using post #2?
[LG Optimus G (International)] Haze028:
Yeah... Or you can use got clone since its only the one repo.

I suggest you Use chadoumings lge vendor or the muppets. Once you get a vendor repo you'll be set to build. Vendor repo will go in directory vendor/lge
[LG Optimus G (International)] xboxfanj:
Chad's is a bit old before the 4.4.2 drop for the N4.

Use mine here: https://github.com/xboxfanj/proprietary_vendor_lge/commits/android-4.4

EDIT: Never mind that for an ls970/gproj build. Those require their own libraries, which as Haze said are at TheMuppets.
[LG Optimus G (International)] ShinySide:
Trying to build CFX but keep hitting this error early in the build.

Have applied this "fix" http://review.cyanogenmod.org/#/c/53126/1/lib/Driver/Tools.cpp but still hittitng the error....Any body have any idea how to fix it?
[LG Optimus G (International)] Haze028:
What repos are you using for your device & device-common?
[LG Optimus G (International)] ronasimi:
Can anyone recommend a good AOSP vendor tree? I'm trying to build mahdi rom, and everything compiles fine but the bootanimation colors are off, and then I get a black/blank screen. I'm 90% sure it's just the egl blobs, but I've tried 4 different vendor trees and I've also tried using mako egl blobs but I'm getting the same problem. I'm using houstonn's kernel https://github.com/houst0nn/android_kernel_lge_geeb and houstonn's device tree https://github.com/houst0nn/device_lge_geeb (both kitkat branch) and I originally used his vendor https://github.com/houst0nn/proprietary_vendor_lge (kitkat branch). I've tried chadouming's vendor repo, as well as my cm-11.0 (and I know it's caf).
[LG Optimus G (International)] xboxfanj:
Use my trees based on Chad's. Hieu's is old
[LG Optimus G (International)] ShinySide:
I'm using all of cfx's except for the jfltetmo from cm which I matched to their i9505 s4 repo
[LG Optimus G (International)] xboxfanj:
Easiest thing you can do so you don't have to change the ROM itself is to change device:

See here: TARGET_GLOBAL_CFLAGS += -mfpu=neon-vfpv4 -mfloat-abi=softfp

TARGET_GLOBAL_CPPFLAGS += -mfpu=neon-vfpv4 -mfloat-abi=softfp

delete -vfpv4 in both lines of device/samsung/msm8960-common/BoardConfigCommon.mk so its -mfpu=neon.
[LG Optimus G (International)] ShinySide:
So that worked wonderfully. Thanks for that....Unfortunately I get so many hardware_qcom_audio-caf errors I cant even keep up with them Ahaha

Thanks alot tho for getting me past the clang issue
[LG Optimus G (International)] xboxfanj:
Then get rid of caf audio. Delete that line in one of the common boardconfigs. Aosp audio should work fine.
[LG Optimus G (International)] ronasimi:
Can anyone tell me what changes are needed to port mako kernel source to geeb? Is it as simple as doing a new defconfig or are there other changes/drivers required? I know our boards are basically identical. I'm building mahdi-rom, and I was using one of xboxfanj's kernel repos, but I get no display. Flashing mizry's ak kernel fixes it, so I've got a driver mismatch somewhere. I'd just use the ak source, but I've been told that the ak kernel is a little buggy still so if I've got to change stuff anyway I might as well start with a vanilla kernel source... right(?)
[LG Optimus G (International)] xboxfanj:
Hieu has a commit. Look on his or chads kernel. Rebase geeb on mako or something like that. There's a couple around there.
[LG Optimus G (International)] :
Trying to compile AOKP:

I have git clone'd vendor, device, and kernel. Done necessary edits in the guide, but for some reason it can't find the product spec. I am 100% sure everything is in the right place. Perhaps I cloned the wrong things. Can someone help me out?

I cloned the following:

Device

Vendor

Kernel
[LG Optimus G (International)] Haze028:
Did you complete the AOKP specific edits? Like adding your device to the aokp vendor repo?
[LG Optimus G (International)] :
Yeah. I did exactly what the guide said. I'm going to double check and make sure everything is correct with build environment since I was a little sleepy when I set it up lol
[LG Optimus G (International)] Haze028:
I'll also take a look at aokp source to see if they may have changed something in how they set up devices since i wrote this guide. **As far as I can tell, should be the same setup procedure**

Again, just make sure you've created a Name_of_device.mk for your device and add it to the androidproducts.mk file in the same dir, and that you've added your device to the vendorsetup.sh
[LG Optimus G (International)] :
I am sure I have, I even triple checked lol. Are those repo's I cloned correct?
[LG Optimus G (International)] Haze028:
You also need the gee-common repo.
[LG Optimus G (International)] :
Cloned into device/lge/geeb right?

Also do I clone the entire proprietary vendor or just the gee folder?
[LG Optimus G (International)] Haze028:
cloned into device/lge/gee-common
[LG Optimus G (International)] :
Ok that's what I have. In vendor/lge/gee though I have all of the folds from the repo, do I just need the gee one?
[LG Optimus G (International)] Haze028:
You really only need the one, but just leave them there, they cause no harm and they're already there. The vendor folder it looks for is defined in the device repo.

You should be set, looks like you have all the folders in place and the aokp edits done
[LG Optimus G (International)] :
Ok I was only missing the common one last time. Trying now, will report, thanks a lot!
[LG Optimus G (International)] :
After running lunch it ends with this:

host C: libsepol <= external/libsepol/src/avrule_block.c
HOSTCC scripts/basic/fixdep
/bin/sh: ccache: command not found
make[3]: *** [scripts/basic/fixdep] Error 127
make[2]: *** [scripts_basic] Error 2
make[2]: *** Waiting for unfinished jobs....
host C: libsepol <= external/libsepol/src/avtab.c
GEN /Volumes/android/omnirom/out/target/product/geeb/obj/KERNEL_OBJ/Makefile
make[1]: *** [sub-make] Error 2
make: *** [/Volumes/android/omnirom/out/target/product/geeb/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....
# In case value of PACKAGES is empty.
[LG Optimus G (International)] Haze028:
Look up higher in the output for the actual error
[LG Optimus G (International)] :
Fixed it, but I am still getting weird errors on the make otapackage command. It's OSX 10.9's fault. Gonna have to install ubuntu later.
[LG Optimus G (International)] Haze028:
Did you follow the Mac osx setup here
[LG Optimus G (International)] :
Yes. From the hour-ish of research I did, all I found was errors with 10.9, all saying they worked fine on 10.8. :confused:
[LG Optimus G (International)] Haze028:
Yeah. Sorry unfamiliar with Mac in general.
[LG Optimus G (International)] :
Yeah, I used to build fine for the Captivate back in the Lion days. Mavericks must've screwed it all up. I'll just try and install Ubuntu when I get a chance. Awesome guide, and thanks for the help!
[LG Optimus G (International)] xboxfanj:
If you need any help, you can add me on Hangouts (if you haven't already) xboxlover360@gmail.com

That goes for anyone.
[LG Optimus G (International)] mathsz:
Same as dvhexer. It works pretty well actually.

---------- Post added at 08:02 PM ---------- Previous post was at 08:00 PM ----------

This doesn't get said enough. You guys rock.
[LG Optimus G (International)] OMGMatrix:
I'm trying to build PA with Houst0nn's device & kernel, but I can't get the AOSPA-legacy repo to sync with his device info.

I have this in my local manifests:

<remote name="gh" fetch="github.com/" />

<project path="device/lge/geeb" name="houst0nn/device_lge_geeb" remote="gh" revision="kitkat" />

<project path="kernel/lge/geeb" name="houst0nn/android_kernel_lge_geeb" remote="gh" revision="kitkat" />

<project path="vendor/lge/gee" name="houst0nn/vendor_lge_gee" remote="gh" revision="kitkat" />

and when I repo sync after I init the AOSPA-legacy repo, I get this:

AOSPA-legacy/github.com/houst0nn/device_lge_geeb is not a valid repository name

Email support@github.com for help

fatal: remote error:

AOSPA-legacy/github.com/houst0nn/android_kernel_lge_geeb is not a valid repository name

Email support@github.com for help

fatal: remote error:

AOSPA-legacy/github.com/houst0nn/vendor_lge_gee is not a valid repository name

Email support@github.com for help

error: Cannot fetch houst0nn/device_lge_geeb

error: Cannot fetch houst0nn/android_kernel_lge_geeb

error: Cannot fetch houst0nn/vendor_lge_gee

Which makes sense, as his stuff isn't on the AOSPA-legacy directory. However, I can't get his repo to init properly. When I put the branch as jb43-legacy, as it shows on the manifest on his github, it gives me:

fatal: manifest 'default.xml' not available

fatal: remote gh already exists with different attributes

or, if I enter the branch as "kitkat", as it shows on the device pages, the repo will init, but when I try to sync it, I get:

fatal: Couldn't find remote ref refs/heads/kitkat

I'm utterly lost at this point, anyone want to tell me what I'm doing wrong?
[LG Optimus G (International)] ronasimi:
Look at your URLs. You need to fix up the manifest so it makes valid URLs
[LG Optimus G (International)] OMGMatrix:
It might just be because I'm up late, but I can't see how that doesn't make valid URLs.

Am I putting something in the wrong place? Am I leaving something out?
[LG Optimus G (International)] Haze028:
Try making your remote fetch "git://github.com/" or "https://github.com/"
[LG Optimus G (International)] OMGMatrix:
...Wow, I can't believe I missed that.

I won't have access to my home computer again until later tonight, but I'll fix that up and give it another go when I get home.
[LG Optimus G (International)] KIYOSH:
Device Source

Is it possible to get device source from that device & how
[LG Optimus G (International)] Haze028:
Sorry... Which device?
[LG Optimus G (International)] nch26:
in this step:

2. You need to know the location for your device, vendor, and kernel repos. This can be found fairly easily in the forum for your phone. Also take note of your phones codename.

For example the Optimus G is the gee and its repos can be found here https://github.com/TeamPlaceholder

What i should choose for E975?
[LG Optimus G (International)] Haze028:
Can always use cm repos. You'll need:

android_device_lge_e975

android_device_lge_gproj-common

The gproj kernel and lge vendor

Get the lge vendor repo from themuppets or xboxfan's github

Xboxfanj also has Device and kernel repos for the optimus g with lots of work done, check his github... Not sure if he has the e975 repos or not.

Hope that gets you started...
[LG Optimus G (International)] nch26:
I apreciate your quick answer. But I want to use a 100% AOSP 4.4.2 ROM.

Not CM,AOKP, Stock like nexus 4 or 5.

Is possible ?
[LG Optimus G (International)] Haze028:
Try teamplaceholder xboxfanj their repos should be aosp friendly

Other than that look at the op for Roms you can run and try their github if they list it. Namely the aosp Roms in the forum

Aosp requires a prebuilt kernel so you'll need to learn to compile a kernel separately as well. There are some good guides on this throughout xda.
[LG Optimus G (International)] xboxfanj:
My trees are very close to AOSP, but with a few performance improvements and I also made common fairly universal. There's also a couple overlays not available in AOSP, but those would error in AOSP by telling you exactly what to delete. You would also need the last two commits here and you would need to make a kernel that's AOSP + our hardware fixes. Essentially, that's where all kernels started out, but they've deviated from that. GPROJ/CM started from AOSP Nexus 4 4.2 source and added a lot of stock drivers. On the other hand, gee source is based on mako 4.4.2 with other changes, such as DT2W and other optimizations that make it different from AOSP along with the bare minimum additions from stock for the hardware, such as NFC.
[LG Optimus G (International)] KIYOSH:
Samsung Galaxy S i9000
[LG Optimus G (International)] nch26:
See your point. It seems that is more easy to build an CM OR AOKP ROM than a AOSP one.

i appreciate your guide, really. I always want create a AOSP rom. But i will start with CM or AOKP wich is more easy.

I will let you know if i have some error.

Really apreciate your help, thanks. [MENTION=4003363]xboxfanj[/MENTION] and [MENTION=4153704]Haze028[/MENTION]
[LG Optimus G (International)] nch26:
error: manifest required for this command -- please run init

Im having this error when i choose manifest.

what is wrong ?

Also, in prerequisites step, when i put the commands, i get an error.

Los siguientes paquetes tienen dependencias incumplidas:

libgl1-mesa-glx:i386 : Depende: libglapi-mesa:i386 (= 8.0.4-0ubuntu0.7)

Recomienda: libgl1-mesa-dri:i386 (>= 7.2)

E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos.

Translated to english it say "The next packages have dependent incumplement"

"You have been hold brocken packages"
[LG Optimus G (International)] Haze028:
You need to run 'repo init -u manifest -b branch'

Then do a repo sync
[LG Optimus G (International)] nch26:
But when i put the manifest and branch, like repo init -u https://github.com/CyanogenMod/android.git -b cm-11.0, the error comes. I ignore them and type repo sync ? If i do that, i have this error

Traceback (most recent call last):

File "/home/naacho/ROM/.repo/repo/main.py", line 408, in <module>

_Main(sys.argv[1:])

File "/home/naacho/ROM/.repo/repo/main.py", line 384, in _Main

result = repo._Run(argv) or 0

File "/home/naacho/ROM/.repo/repo/main.py", line 127, in _Run

copts, cargs = cmd.OptionParser.parse_args(argv)

File "/home/naacho/ROM/.repo/repo/command.py", line 67, in OptionParser

self._Options(self._optparse)

File "/home/naacho/ROM/.repo/repo/subcmds/sync.py", line 163, in _Options

self.jobs = self.manifest.default.sync_j

File "/home/naacho/ROM/.repo/repo/manifest_xml.py", line 314, in default

self._Load()

File "/home/naacho/ROM/.repo/repo/manifest_xml.py", line 354, in _Load

b = m.GetBranch(m.CurrentBranch).merge

File "/home/naacho/ROM/.repo/repo/project.py", line 590, in CurrentBranch

b = self.work_git.GetHead()

File "/home/naacho/ROM/.repo/repo/project.py", line 2265, in GetHead

raise NoManifestException(path)

error.NoManifestException: /home/naacho/ROM/.repo/manifests/.git/HEAD

naacho@ubuntu:~/ROM$
[LG Optimus G (International)] Haze028:
I'm not sure why it would be saying that... Try deleting you folder... Make a new one and run the repo init again....
[LG Optimus G (International)] ronasimi:
Just out of curiosity, what version of ubuntu are you using? and what version of python? (do a python -V)
[LG Optimus G (International)] nch26:
ubuntu 12.04 and sorry but right now i dont have ubuntu to say v of python.

---------- Post added at 12:07 AM ---------- Previous post was at 12:06 AM ----------

No luck man.. same error.
[LG Optimus G (International)] Haze028:
Did all the prerequisite packages and repo install without error?
[LG Optimus G (International)] nch26:
The second package give me an error.

Los siguientes paquetes tienen dependencias incumplidas:

libgl1-mesa-glx:i386 : Depende: libglapi-mesa:i386 (= 8.0.4-0ubuntu0.7)

Recomienda: libgl1-mesa-dri:i386 (>= 7.2)

E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos.

Translated to english it say "The next packages have dependent incumplement"

"You have been hold brocken packages"