yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] keithwired:
I'm uploading the ROM to my google drive and I'll share the link when it's done.
[HTC Droid DNA] gillim74:
Moto x libs caused camera to not function
[HTC Droid DNA] keithwired:
https://drive.google.com/file/d/0B_14HUC7F6nPVzJ3SDFsYUlOOTg/edit?usp=sharing

ROM rehost for anyone that wants it
[HTC Droid DNA] gillim74:
Does your camera function?
[HTC Droid DNA] zawata:
id like to say im pretty good at dealing with build errors(im probably at average) but i cant work on this now

got too much to do though i can try

if you figure out the errors are you looking to be a maintainer? because by all means go right ahead if you want too
[HTC Droid DNA] danjull:
Not necessarily, mainly just playing around to help out. If no one else will do it, I'll probably compile it now and then to keep it up to date.
[HTC Droid DNA] crpalmer:
This sounds to me like the -caf repositories are out of date. The change that is breaking this build was made a long time ago. I would recommend using the CM repos instead for these.
[HTC Droid DNA] zawata:
I always use the CM repos just after i get a big error with something

and i think i got further with a second build

but failed on another kernel error

how do i override the .repo/local_manifests/roomservice.xml

omni keeps sticking its nose in my business and insisting that i use it's kernel instead of CM's

this is a question for everyone btw not just palmer

EDIT:

think i got it

the roomservice.xml os built from the omni.dependencies file, so i just modify the repo's it syncs from to get the CM repos instead

can anyone tell me im right? this seems to have worked so far
[HTC Droid DNA] danjull:
Yeah. You got it.

I finished a build, not booting though. Gets stuck at the HTC screen :mad: Omni's kernel is a little behind, so I'm using cm's. Just about everything else that's available is omni sourced. Amit pointed out that there's another qcom branch that's more up to date. Swap to it and it'll get you past the caf errors.

Ran a clobber and a fresh brunch and we'll see how it goes this time around. I've actually remembered to include the vendor files this time, so that's not the problem.
[HTC Droid DNA] zawata:
Mmmmm fresh brunch

Always the best

I just added to my local manifest to exclude omni's -caf repos and use CM's instead

I'm currently building and haven't errored out yet

I'm starting to hate omni more and more with this build process

EDIT:

hmmm

unable to open /home/zach/android.Omni/system/out/target/common/obj/JAVA_LIBRARIES/framework-base_intermediates/src/core/java/android/content/pm/IPackageManager.java for write
[HTC Droid DNA] danjull:
So after making clobber and a fresh build, I'm getting caf errors again. WTF?! I didn't change anything. Omni's got a mind of it's own!
[HTC Droid DNA] zawata:
yeah i know, im using CM's kernel and its still giving me trouble

heres what i did for the -caf errors

in your local_manifest

<project path="hardware/qcom/audio-caf" name="CyanogenMod/android_hardware_qcom_audio-caf" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/display-caf" name="CyanogenMod/android_hardware_qcom_display-caf" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/media-caf" name="CyanogenMod/android_hardware_qcom_media-caf" remote="github" revision="cm-11.0" />

<remove-project name="android_hardware_qcom_media-caf" />
<remove-project name="android_hardware_qcom_display-caf" />
<remove-project name="android_hardware_qcom_audio-caf" />

any idea about this one?

the missing file is under the frameworks/base and its supposed to be compiled into the out directory i guess but its not in out directory

unable to open /home/zach/android.Omni/system/out/target/common/obj/JAVA_LIBRARIES/framework-base_intermediates/src/core/java/android/content/pm/IPackageManager.java for write

EDIT: changed the error, has nothing to do with the kernel

EDIT2: got another similar error from the same place, i think omni also has a messed up frameworks/base directory

im gonna full resync it, and if that doesnt work go CM
[HTC Droid DNA] crpalmer:
[MENTION=5285997]zawata[/MENTION], modules failing to build is an error that is ignored. that's probably not why your build failed.
[HTC Droid DNA] amit_sen:
Wishing everyone a very Happy New Year :beer:

On a good note i have just bought a new laptop, will be receiving it during weekend ;)

G2 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TF300T
[HTC Droid DNA] zawata:
yeah i figured, i changed the error because i remembered that happening during slimkat

no i found the actual error and fixed it

what happened was about 150 lines of warnings, the error then it began to compile the kernel, spit out those errors(/warning) then it quit so it confused me a bit

happy new years right back at you :D

by buildbox you mean like a dedicated build server?(never heard of a build box, just did a quick google search)

EDIT: boy do i love challenges, i think im getting closer to a successful build

5 build errors down

? to go :D
[HTC Droid DNA] danjull:
I think omni is the precursor to skynet and it has a mind of it's own. An evil mind. How can I compile a build, not change anything at all, and fail the next run through. It's changing at will just to get on your nerves.
[HTC Droid DNA] zawata:
i could definitly see that

it was developed by all the greatest devs why shouldnt it have artificial intelligence

ill bet it was chainfire o_O

now for a rational solution:

im pretty sure the build process is almost psuedo random in the way it compiles, or so it seems

theres probably just many different errors

i kept getting errors about AIDL not finding or being able to open files that were clearly there so i changed repos for frameworks/base to CM's and then got errors about missing definitions from frameworks/native so i added that too, then got more errors that should have already been patched by CM, but i dont where they were patched so i had to revert back to omni's repos and im waiting to see where it fails

its almost like watching a progress bar get to about 80% then omni coming up, breaking it half, saying "Go F*ck Yourself"(completely straight faced) and walking away

then the next build only gets to 10% before failing...and then you die a little inside

EDIT: haha youll never guess what error i just got

device/htc/dlx/overlay/frameworks/base/core/res/res/values/config.xml:222: error: Resource at config_hotswapCapable appears in overlay but not in the base package; use <add-resource> to add.
device/htc/dlx/overlay/frameworks/base/core/res/res/values/config.xml:225: error: Resource at config_deviceHasVariableButtonBrightness appears in overlay but not in the base package; use <add-resource> to add.
device/htc/dlx/overlay/frameworks/base/core/res/res/values/config.xml:228: error: Resource at config_enableTorch appears in overlay but not in the base package; use <add-resource> to add.

i could have swore i did that but i guess not lol

EDIT2:

well i think i passed all the system errors, im now getting app errors...73 of them

http://pastebin.com/UVHrMsuD

the bad news is a repo sync didnt help it,

its only two apps: Email, and Cell Broadcast Reciever
[HTC Droid DNA] armydog13:
Thought you were going to post a line that said, "Go F*ck yourself." Lol
[HTC Droid DNA] zawata:
lol nope. describeing the build process of omnirom

i think those 3 words sum it up pretty well
[HTC Droid DNA] armydog13:
When you said, "you'll never guess what error I just got" I thought maybe it had finally given you that error line, sort of like Google now Easter eggs.
[HTC Droid DNA] danjull:
Got another completed build. Not booting :mad:
[HTC Droid DNA] zawata:
haha oh my god i wish that would just be awesome

[MENTION=3721563]danjull[/MENTION] i finally got a build too, ill check its boot status

you getting a logcat for it?

EDIT: yeah didnt boot

on the bright side i got a logcat

- waiting for device -

-_-

i did however get the /proc/last_kmesg

now if only i could read it...
[HTC Droid DNA] crpalmer:
Nothing to read in the last_kmsg. The only useful information is that there is most likely a process that keeps dieing and then getting restarted. Most likely one of the critical services (binder, systerm service, etc.) is crashing. You really need a logcat.
[HTC Droid DNA] danjull:
I'm nuking it and starting over from scratch.
[HTC Droid DNA] zawata:
Damn...well thanks anyway [MENTION=3721563]danjull[/MENTION] yeah I think that's pretty much the only option at this point

I think Im gonna start looking around on Omni's website and the forums and such
[HTC Droid DNA] danjull:
Erased everything. Started over from scratch. Synced Omni, replaced cafs and kernel with CM source, added TheMuppets' vendor tree, and CM's dlx device tree which I altered to fit Omni. Completed a build, no boot. I've looked at my device tree a thousand times, and I can't see anything wrong. I think I've stared myself blind on it, so I could probably not spot a mistake at this point. So, if anyone would like to look at my device tree, please do. -->Link<--
[HTC Droid DNA] zawata:
Why are you using slims m7 kernel and SoC configs?

---------- Post added at 08:10 AM ---------- Previous post was at 07:55 AM ----------

http://docs.omnirom.org/Main_Page

This page might help
[HTC Droid DNA] crpalmer:
You need a logcat.
[HTC Droid DNA] zawata:
there only one problem with that

something happens with the kernel and it doesnt want to give us a logcat, mine just says -waiting for device-(meaning the ADBD is never started) and im pretty sure the samething is happening to [MENTION=3721563]danjull[/MENTION]

but if it isnt...then for god sakes man give us a logcat!!!
[HTC Droid DNA] danjull:
Yeah, I've checked Omni's wiki out.

I had slimrom on my computer, so I did a local reference to that in my local manifest for the kernel, caf, etc. to cut down on sync time. Tried cm too.

I'll try again to get a log cat today. But since it won't really boot, I'm not sure it's gonna happen. Since it won't even get started I assume it's something with the kernel not getting along with omni. The size of the output file seems reasonable. Amit's ROM was close enough to my zip file. Mine's actually a little bigger.
[HTC Droid DNA] zawata:
When I was doing slimkat the ability to give logs was pretty random, even if wouldn't boot

You may be able to get a logcat even if it doesn't though I couldn't

Idt the sizes will be an issue, we aren't forgetting anything

How do you do a local reference? I've been wondering that
[HTC Droid DNA] danjull:
When you do the first repo init, add "--reference=~/android/SlimRom" or whatever directory you've got the local source in.

I swapped back to all additional source coming from cm. I'll try to get a log when I get home from work.
[HTC Droid DNA] zawata:
alright sounds good

i just finish a hot steaming sync so ill modify my device tree and start a build

i might use some pieces of your device tree because im lazy, such as the omni.mk
[HTC Droid DNA] danjull:
Knock yourself out. Whatever it takes to iron this thing out. I just feel like there's something obvious we're not seeing. I never really ran omni for long. I'm just taking this personally at this point ;)
[HTC Droid DNA] zawata:
Yeah its more than just a romjob(lol)

Its personal :mad:

Its probably(almost definitely) not the device tree that's messed up

I remember reading somewhere that PAC requires a custom kernel because of the super high amount of customizations that it contains

What if omni is the same way?

Maybe we should try to fix the m7 kernel because if it was truly broken then the m7 wouldn't have a build now would it?
[HTC Droid DNA] jamiethemorris:
Fwiw, crpalmers kernel doesn't work on the existing omni build last time I checked. So I think you're on to something. Just like custom kernels don't work on PAC unless they're specifically made to (it was this way on my nexus 7 at least). For PAC I believe it was because there were so many customizations that they had to have 2 ramdisks. So it's probably something similar with omni.
[HTC Droid DNA] zawata:
yeah i read that in a development thread in some samsung forum and it was quite recent cuz the OP was talking about porting over cm11.0 and working out the bugs

im gonna start on it tonight

hey [MENTION=3721563]danjull[/MENTION] i found the commit that throws -caf errors for us

b76501d

turns out it "corrects" that error but actually causes it

heres the commit that it reverted

cdf08c0

the "correction commit" is wrong, i dont know how to use git or repo very well so you should revert his revert

also using the omnirom -caf directories may help us out
[HTC Droid DNA] danjull:
Yeah, the m7 people are saying they're using unmodified m7 kernel from omni. Just ran another build and I got a bunch of recovery errors. New errors just pop up at will. :eek:

---------- Post added at 06:46 AM ---------- Previous post was at 05:47 AM ----------

Ah! I'm doing another complete sync to get all omni source back. I'll revert it as soon as it gets done and see where it gets us.
[HTC Droid DNA] crpalmer:
Personally, I would give up on omnirom. If you ignore that advice then I think you're stuck trying to make their m7 kernel and qcom repos work.

I don't know what their officially supported devices look like, but their QCOM / M7 looks like they have frozen themselves at an old point in time and aren't moving forward. This means that if you use the CM version of the qcom repos then it will likely be horribly mismatched with the frameworks/ code. Similarly for the kernel.

If you get it to build using their kernel and our device tree then I suspect that at a minimum USB-OTG, WiFi and netflix (Smooth Streaming) won't work right.

If you really want to continue working on it, my guess as to why it's not booting and not giving you adb acesss would be that they do not have SELinux support working right. You can try adding:

androidboot.selinux=permissive

to the define

BOARD_KERNEL_CMDLINE

in BoardConfig.mk to disable SELinux.
[HTC Droid DNA] zawata:
Ouch, that may just help

Or possibly give up,

The qcom repos just seem to get worse with each sync

And its just getting harder

I think I might just get the cm kernel and try to fix the repos

I'm only getting 5 errors from the -caf repos and they're all the same error at different points in the same file

I can try the selinux thing you suggested but I would have to fix the -car errors first

Its the same errors as in my previous post but undoing the revert didn't fix it just the same error with a new name

I'll look at it later to see if I can find the problem but I also gotta update slim and aokp today and that's about 9 hours of building
[HTC Droid DNA] crpalmer:
Are you using ccache? 9 hours is a lot of building. I can do a clean build of CM11 in about 15 minutes with "normal" updates to it (nothing that changes the builds scripts, for example). If you are using ccache, make sure that you have it configured to use enough disk space to accommodate the number of ROMs that you are routinely building.
[HTC Droid DNA] zawata:
no im not using ccache though i probably should

i got loads of HD space to use

how much would you reccommend for 3 roms?(3 is my limit maybe 4 but thats a longshot)

do i have to set it up individually for each rom

i also dont have the fastest computer

8gbram

2core 2.7ghtz processor

its about 5-6 years old but runs like a trooper

i have about 500gb HD but 250 partitioned for ubuntu 13.10

with those specs its about 4 hours per rom

so usually i start a build then play xbox for a while or sleep and hope it doesnt error out

---------- Post added at 09:59 PM ---------- Previous post was at 09:57 PM ----------

yeah i tried to undo that revert and it threw out the same error, so im gonna trace the call back through the files and see exactly what it wants

then ill release the information here

so in your words we should be using the omni kernel?

also look at what palmer was saying about SElinux that may just be the answer to our prayers...or the final straw...

EDIT:

searching my entire code base for the word "entropysel" to find where exactly its defined

its used quite a bit in the files of the directory that throws the error but there is no definition

it also ranges between being used as entropysel and longentropysel but only one file throws errors

EDIT2: output of my searching:

http://pastebin.com/zzJu9Jfd

the only i modified was:

./hardware/qcom/media-caf/mm-video/vidc/venc/src/video_encoder_device.cpp

so as it turns out, the latest commit should be correct

EDIT: i found it!!!!!!!!!(i think)

take a look at this

./hardware/qcom/media-caf/mm-video/vidc/venc/inc/video_encoder_device_copper.h:108:1

struct msm_venc_capability{
unsigned long	codec_types;
unsigned long	maxframe_width;
unsigned long	maxframe_height;
unsigned long	maxtarget_bitrate;
unsigned long	maxframe_rate;
unsigned long	input_formats;
unsigned char	dvs;
};

struct msm_venc_entropycfg{
unsigned longentropysel;
unsigned long	cabacmodel;
};

spaces were forgotten between "long" and "entropysel"

im gonna see what this fixes
[HTC Droid DNA] crpalmer:
[MENTION=5285997]zawata[/MENTION], install ccache ,set the environment variable CCACHE=1 and then tell ccache to use a reasonably large size (say 50 GB) of storage (man ccache will tell you how to configure it). Then build a ROM. Then do a clean build of the same ROM (to make sure it really worked) and then look at the ccache stats and it will tell you how much storage that took. Multiply that by the number of ROMs and then add some buffer space (when things change it will add extra data to the cache ).
[HTC Droid DNA] zawata:
well when i followed the rom build guide(on CM wiki) it installs ccache and tells you how to use it, i dont know why i didnt

i followed the google ccache specifications(exactly what you stated) and i started a clean build of slimkat(today is update day) it looks to be almost done so thanks, if you didnt point that out i would probably have a much more difficult time doing this

i hate compilling libart libllvm and everything related to chromium

EDIT: takes 10.6gb for a complete build of slimkat so i think about 50gb would be good

[MENTION=3721563]danjull[/MENTION]

just found the point when it was compiling the file i changed and it didnt error out

change the code im my last message to look like this

struct msm_venc_entropycfg{
unsigned [COLOR="Lime"]long [/COLOR]longentropysel;
unsigned long	cabacmodel;
};

and dont change anything else

its what worked for me

i errored out just past that point in display-caf

im onto doing that error next

error: 'struct mdp_buf_sync' has no member named 'retire_fen_fd'

EDIT: fixed it

./kernel/htc/m7/include/linux/msm_mdp.h:572:

struct mdp_buf_sync {
uint32_t flags;
uint32_t acq_fen_fd_cnt;
int *acq_fen_fd;
int *rel_fen_fd;
[COLOR="Lime"] int *retire_fen_fd;[/COLOR]
};

EDIT3:

i got another error:

CC kernel/elfcore.o
CC kernel/irq_work.o
CC kernel/cpu_pm.o
CC kernel/time.o
CHK kernel/config_data.h
UPD kernel/config_data.h
CC kernel/configs.o
LD kernel/built-in.o
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/zach/android.Omni/system/kernel/htc/m7'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....

is that even an error message...how do you fix that? it just says error 2

EDIT4: ...god do i hate the android compiler its sooo misleading

i found another(actual) error about 800 terminal lines before it:

/home/zach/android.Omni/system/kernel/htc/m7/arch/arm/mach-msm/board-monarudo.c:3207:2: error: unknown field 'poll_ms' specified in initializer
/home/zach/android.Omni/system/kernel/htc/m7/arch/arm/mach-msm/board-monarudo.c:3207:2: warning: excess elements in struct initializer [enabled by default]
error, forbidden warning: board-monarudo.c:3207
make[3]: *** [arch/arm/mach-msm/board-monarudo.o] Error 1
make[2]: *** [arch/arm/mach-msm] Error 2
make[2]: *** Waiting for unfinished jobs....

considering thats monrudo board file, i can just substitue the same file from CM right?(half rhetorical question)

EDIT5: (should probably go to bed soon)

fixed

./kernel/htc/m7/include/linux/msm_thermal.h:17:

struct msm_thermal_data {
uint32_t sensor_id;
[COLOR="Lime"] uint32_t poll_ms;
uint32_t limit_temp;
uint32_t temp_hysteresis;
uint32_t limit_freq;[/COLOR]
};

EDIT6: god the number of errors in this is just hilarious(in a bad, not funny way)

EDIT7: about 4 more errors i had to fix that i didnt list

got a build with all the OMNI stuff instead of CM

its 4AM here, i gotta go to a meeting in 3 hours

the things i do for XDA...this damn thing better f***ing boot

EDIT8:

...
[HTC Droid DNA] kformeck:
We really appreciate the hard work dude. It's obvious that you are extremely dedicated to bringing top quality ROMs to this device that you are willing to sacrifice your own sleep for this community..

On another note, I have found that taking a day or two away from things like this will definitely help. I've had bugs that I could not seem to fix for the life of me on a Friday; I go home and come back on Monday to find that the bug was something that was sitting right there in front of me the whole time.

Give your brain some rest man.
[HTC Droid DNA] zawata:
dedicated towards bringing roms to the DNA - yes :)

dedicated toward showing omni who the real boss is? - your damn right

yeah, i wasnt really tired lol

i went to sleep at 4 woke up at 7 and went "lol nope" slept for another 45 minutes,

iwas about an hour late but i didnt miss anything important it all started like 10 minutes after i got there

if this bug is staring me right in the face then it must have like an invisibility cloak or something

the only thing i can see right now is that the OMNIrom M7 kernel isnt optimized for use on both the m7 and the DNA but even then im not sure

that that would even prevent logcat access

maybe your right, ill just take a few days off gotta start preparing for college

got my acceptance letter over the weekend :D

i also got a 6k yearly scholarship based upon my grades :D

[MENTION=3866229]amit_sen[/MENTION] - yeah thats right im bring you back the DNA for a bit lol

is there anything special you had to do for building omni?

Use any of the CM repos? kernel modifications? did it just build straight away or did you have to fix all the errors?

this is really starting to hurt
[HTC Droid DNA] orangechoochoo:
Congrats on the acceptance and scholarship!

You have your whole life ahead of you (70+ years) the hardest part is figuring out a profession. When I was your age I thought I would be a cop but I ended up being a lawyer, so be ready for change and going through a bunch of self reflection. But once you put your mind to something make sure you give 100% no matter what it is. Determination and perseverance is what makes people.
[HTC Droid DNA] zawata:
thanks :)

i havent completely commited myself to anyone thing yet but i applied with my major set as robotic engineering

its always facinated me and ive been doing robotics club for 4 years now(this year im in charge of visual target tracking and distance measurement with a kinect) and ive loved every minute of it

i also figure robotics is a new, not well explored frontier that might be booming in 5 years

cop to lawyer? wow thats quite a difference in education how do you make a practically last minute decision like that?
[HTC Droid DNA] orangechoochoo:
Robotics engineering sounds really cool. Sometimes I wish I had multiple lives so I could try all the different majors I was interested in such as physics, chemistry, history, biology, medicine, etc.

As far as turning from cop to lawyer, I was too young to enter the academy because of age restrictions on guns, so I went to community college to pass time away, then I got interested with the FBI so I got my bachelor's, but then I got interested in law so I went to law school. Now I want to learn how to develop Android. In ten years I could be doing something completely different.

Time flies, but there's also enough time to do a lot of things.