yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] _litz:
Hmm ... no audio in this build ... :(

E/AudioTrack( 531): Could not get audio output for stream type 1

E/SoundPool( 531): Error creating AudioTrack
[HTC Rezound] REV3NT3CH:
what recovery are you flashing with. i keep getting a failure on flash install with twrp

Edit: there error for it is

set_metadata_recursive: some changes failed

E: Error executing updater binary in zip
[HTC Rezound] _litz:
Oh, it was a dozen or so pages back ... it's a brand new CWM compile.

edit : http://d-h.st/8FW

This thing is weird ... sdcard0, sdcard1, *and* external_sd ...
[HTC Rezound] REV3NT3CH:
ahhh sweet thanks alot bud
[HTC Rezound] Flyhalf205:
Hopefully I can fix the recovery issue sdcard issue tonight. I would really love to be able to port a new touch version but can't find a device similar to port.
[HTC Rezound] kkozma:
There is a HUGE QCOM commit for frameworks/av that is still being worked on for Omnirom. A similar commit was mentioned in one of them we needed to fix audio-caf. I'm pretty sure it will button up our audio issues.

https://gerrit.omnirom.org/#/c/1685/

Speaking of odd audio issues. Anyone else notice that volume doesn't do a damned thing? It's all or nada.
[HTC Rezound] desalesouche:
hi sir i have quite the same error while compiling cm 11 for huawei u8800pro but for the hardware/qcom/audio-caf/msm7x30/audio_policy_hal.cpp:

mau i ask you if you have an idea about the fix ?or any advice? thank you..

here a pastebin of errors.

http://pastebin.com/4uCYDxDR

thank you .
[HTC Rezound] kkozma:
I grepped my old 10.2 source...

vwmofo@AndroidBuild:~/android/ExpMofo/frameworks/native$ grep -iR "BOARD_EGL_NEEDS_LEGACY_FB"

include/gui/SurfaceComposerClient.h:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

include/gui/SurfaceComposerClient.h:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

include/gui/ISurfaceComposer.h:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

include/gui/ISurfaceComposer.h:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/Android.mk:ifeq ($(BOARD_EGL_NEEDS_LEGACY_FB),true)

services/surfaceflinger/Android.mk: LOCAL_CFLAGS += -DBOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/SurfaceFlinger.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/SurfaceFlinger.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/SurfaceFlinger.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/SurfaceFlinger.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/SurfaceFlinger.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/SurfaceFlinger.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/SurfaceFlinger.h:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/SurfaceFlinger.h:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

libs/gui/Android.mk:ifeq ($(BOARD_EGL_NEEDS_LEGACY_FB),true)

libs/gui/Android.mk: LOCAL_CFLAGS += -DBOARD_EGL_NEEDS_LEGACY_FB

libs/gui/ISurfaceComposer.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

libs/gui/ISurfaceComposer.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

libs/gui/SurfaceComposerClient.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

libs/gui/SurfaceComposerClient.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

libs/gui/SurfaceComposerClient.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

It's all over the place in frameworks/native.

This is my cm 11 branch

vwmofo@AndroidBuild:~/android/MofoROM-4.4/frameworks/native$ grep -iR "BOARD_EGL_NEEDS_LEGACY_FB"

services/surfaceflinger/Android.mk:ifeq ($(BOARD_EGL_NEEDS_LEGACY_FB),true)

services/surfaceflinger/Android.mk: LOCAL_CFLAGS += -DBOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/DisplayDevice.cpp:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/DisplayDevice.cpp: #ifndef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/Android.mk~:ifeq ($(BOARD_EGL_NEEDS_LEGACY_FB),true)

services/surfaceflinger/Android.mk~: LOCAL_CFLAGS += -DBOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/DisplayDevice.cpp~:#ifdef BOARD_EGL_NEEDS_LEGACY_FB

services/surfaceflinger/DisplayDevice.cpp~: #ifndef BOARD_EGL_NEEDS_LEGACY_FB

.git/rr-cache/e0a7cfa642835da13959cef4b1965554fbbda3fd/preimage:ifeq ($(BOARD_EGL_NEEDS_LEGACY_FB),true)

.git/rr-cache/e0a7cfa642835da13959cef4b1965554fbbda3fd/preimage: LOCAL_CFLAGS += -DBOARD_EGL_NEEDS_LEGACY_FB

grep: .git/svn: No such file or directory

Looks like we have some work to do.
[HTC Rezound] _litz:
Ok, for those who want to build, here's the latest "what you have to tweak" to get it to work for my build :

1) repo init -b cm-11.0 -u git://github.com/vigor/android.git

2) execute the following:

pushd .repo
sed -i "s/sync-c=\"true\"//g" manifest.xml
popd

3) repo sync -j16

4) edit device/htc/vigor/overlay/packages/apps/Settings/res/values/arrays.xml and comment every <string-array> element

5) grab http://www.litz.org/android/frameworks_native-diff.patch and git apply it in frameworks/native

6) get prebuilts

7) apply the following cyanogenmod cherrypicks : 53023, 53072, 53073, 53074, 53166, 53165, 53186

and build!
[HTC Rezound] kkozma:
Should be the same thing I linked to in the post you quoted me on...
[HTC Rezound] _litz:
How odd ... that comes from CyanogenMod, too ... why wouldn't they just carry the 10.2 version into 11 ?

I wonder if there are patches in the github from 10.2 that we can apply forward into 11 and save a good chunk of time?
[HTC Rezound] REV3NT3CH:
cant mount usb mass storage in rom....also upon pressing home to get the zoomed out desktop the settings option doesnt work...also if your a gsm user global mode doesnt work...still reads as verizon and doesnt connect to gsm network nor is their any apn options...also audio works for me just fine
[HTC Rezound] _litz:
If you dig around some more, it's very obvious that most of what makes "CM" "CM" isn't yet into the source tree for cm11.

Lots and lots of stuff is missing.
[HTC Rezound] kkozma:
Yes, a lot of it is straight aosp. I'm going to work on the ril later tonight or tomorrow...
[HTC Rezound] Flyhalf205:
Which display legacy did you use to get the Rom to run so fast? I finally got my build booted and here is my list of cherry picks.

https://docs.google.com/document/d/1poV30FSTs3GNREbGPzuzuOJfCwQX8MCKIvzw7wdj32A/edit?usp=sharing
[HTC Rezound] _litz:
On mine I added "selinix=0" to the kernel cmdline.

Interestingly enough, that ran fast as lightning.

Then the project in vigor was changed to selinux:permissive ...

that gives bunches of declined msgs in logcat, and a slow-as-molasses UI

this despite the fact the permissive should allow everything.
[HTC Rezound] Flyhalf205:
Crap I forgot a kernel commit regarding selinux. Which hopefully cleans up selinux for good
[HTC Rezound] _litz:
Which one is that?

---------- Post added at 10:37 PM ---------- Previous post was at 10:31 PM ----------

Also, I noticed you left patch 53073 out of your cherrypick list ... is that one not needed?
[HTC Rezound] _litz:
hmmmmpf ... broke something.

Now I get : Timed out waiting for hw vsync; faking it from surfaceflinger ...

Each msg causes the UI to pause for 1 second. :(

Too late tonight to mess with it, if anyone wants to try, the build to replicate is basically repo sync, blank the array.xml, and pull all the cherrypicks listed in flyhalf's post.
[HTC Rezound] desalesouche:
hi all, someone told me that 4.3 binaries can't be used with kitkat? is that true?and if true what to do?
[HTC Rezound] Flyhalf205:
Did what you said above but it's still as you say "slow-as-molasses UI"
[HTC Rezound] Snuzzo:
if it helps any, I just pushed source from the DNA to my git. Didnt really have time to look at anything though.
[HTC Rezound] chad0989:
Not making much progress with the v4l2 camera / HAL anymore. Everything seems to be detected and I'm not really getting any errors, but still not working so I'm not really sure where to go with it.. Going to see if I can build the old HAL with ION support. Hopefully I can come up with something.
[HTC Rezound] MaulingDeOso:
Code Aurora just dumped a pile of commits onto jb_chocolate. Just days after I backported most of the same. There's also a couple of new API features that I have a feeling might make getting to 4.2 slightly more difficult.
[HTC Rezound] chad0989:
Can someone get me a logcat of their boot and then opening the camera + taking a photo? Thanks.
[HTC Rezound] kd-:
As requested... https://privatepaste.com/f12dab0096
[HTC Rezound] live2die:
and this is mine

edit: im on aokp jb
[HTC Rezound] GrayBoltWolf:
ATTENTION BUILD PEOPLE:

If there is anybody else who wants to post their CM10 kang, please PM me so I can get preparations made for a CM10 megathread.

I am in no way saying that we are allowed to post builds, but I just want to make sure we don't have 10 different versions of the same ROM floating around when Chad lets us post.

So, if you know you will want to post your build in the development section, PM me so I can get a list of people who get a spot in the megathread.
[HTC Rezound] chad0989:
Okay so I *think* whats going on is that the camera is being registered as /dev/video1 but the HAL is trying to connect to /dev/video0. Not really sure why though.

Anyone have an s4 device (one s, inc 4g) that can check some things for me?
[HTC Rezound] siulmagic:
i imagine an sgs3 wouldent help right?
[HTC Rezound] live2die:
i can get a htc one x（wcdma） and a htc one st（cdma，only available in China），both are native s4 devices，how can i be of any help?
[HTC Rezound] Snuzzo:
Long fetch, might be able to get access to an HOX+.
[HTC Rezound] Argumentation:
I don't know if this will help, but I have my rooted DNA in my hand that I can check whatever you need. :good:
[HTC Rezound] antp121:
RAZR m probably wouldn't help eh?
[HTC Rezound] chad0989:
Can you get me a logcat of it booting and taking a picture (the one s preferably but I can try to work with anything)? Even better if you can get the log with CM10.

Also for any of the devices can can someone take a look and see how many video devices they have. They should be listed as /dev/video0, /dev/video1...

I'm curious because I have two devices registered, but only one camera enabled and of course the HAL is trying to use the wrong one.
[HTC Rezound] live2die:
this is the logcat from htc one sc, the cdma phone of htc one s in China and only in China, hope this can be of some help, and im so glad i can help:fingers-crossed:

oh, its from the stock sense 4.1 rom. there is no dev develping this phone by far, so it has no cm 10 yet
[HTC Rezound] chad0989:
Can you get the logcat as it boots?

Connect the phone,

./adb logcat (it should say waiting for device)

Then turn it on and wait.

If you did that then its taking too long for adb to start unfortunately (i've noticed this with sense roms).

A dmesg as soon as you can adb in as its booting and right after opening the cam and taking a picture would be helpful too.

Also how many video devices do you have listed (e.g. /dev/video0, /dev/video1...)
[HTC Rezound] Argumentation:
I'll get the log in a sec, but I have 5 video devices under /dev, 0, 1, 100, 2, and 3. :good:

EDIT - Logs attached.
[HTC Rezound] live2die:
http://logcat.miui.us/1686001

here is the logcat of htc one s by xkonni（developer of htc one s forum here and its with his cm 10 rom），ill make mine as soon as i get off work，my timezone is GMT +8. and sorry for my being a noob that i cant even make a useful logcat:(

edit: there is no video device in /dev folder of my wife's htc one sc:confused: can it be in other folders?
[HTC Rezound] wlmeng11:
Edit: Doesn't seem to work consistently, but you can still try if you want.

So apparently the slow GPS issues are the same as on cm9.

Replace /system/etc/gps.conf with the one from the patch for cm9.

http://db.tt/yFtACYGt

Edit:

It still doesn't work perfectly, but it seems to be better than with the previous gps.conf

Also, don't forget to chmod 644 it, and backing up the old one is a good idea.
[HTC Rezound] chad0989:
Woohoo. Just got a preview to come up! Color calibration isn't correct and there are some errors but its definite progress.
[HTC Rezound] johnnyslt:
Is SDCard working?
[HTC Rezound] _litz:
Not sure what you mean by "binaries", but if you mean gapps, yes - you have to use gapps for each specific android version (4.2, 4.3, 4.4, etc).

---------- Post added at 11:35 AM ---------- Previous post was at 11:12 AM ----------

Something is still seriously messed up ... we're back to turtle-ui ...

Must be something else; with the current changes selinux is disabled, so no permissions errors.

But there is that new message :

W/SurfaceFlinger( 142): Timed out waiting for hw vsync; faking it

For some reason, our hardware sync is now dead ... :(
[HTC Rezound] Flyhalf205:
[MENTION=4317549]_litz[/MENTION]

I just threw this commit here. https://github.com/vigor/android_de...mmit/b74da760675e760a5ce4560e5a5ebb84e2f3aa14

TARGET_RUNNING_WITHOUT_SYNC_FRAMEWORK := true

johnnyslt had this commit on his github.

We seriously need a 3.4 kernel. Wouldn't be having so many problems here.
[HTC Rezound] Neo:
[MENTION=3419683]Snuzzo[/MENTION] poke poke
[HTC Rezound] kkozma:
Did you guys switch back to our old display-legacy repo? I don't see this one in there anymore... https://github.com/CyanogenMOD-11-Legacy/hardware_qcom_display-legacy

Also it looks like they changed a few things yesterday because they're using it for msm7x30 so hopefully it doesn't mess up our build... If it does, I forked it and we can easily revert their change.

Sorry guys, I haven't had any time to mess with this stuff today, I should have some time to screw around with it tonight and tomorrow.
[HTC Rezound] Flyhalf205:
I switched back to the old legacy. I didn't see much difference honestly. But It will be an easy fix to change it back to 8x60 devices.
[HTC Rezound] _litz:
Ohhhh ... that might be the cause of turtle-speed ... I was getting the fast speeds on the other repo

lemme plop it back in and rebuild and see what happens.
[HTC Rezound] Jonman409:
Typo: s/selinix/selinux/

---------- Post added at 01:05 PM ---------- Previous post was at 12:58 PM ----------

The other day I checked out the jb_2.6 branch from CodeAurora and fixed the errors to build MSM8660. Almost all of the MSM media drivers require ION now so disabling ION would probably be more trouble than it's worth. I added basic vigor definitions I haven't had time to build a CM 10.2 ION build and then flash the kernel to see what initializes and what doesn't.

It at least builds now. I'm not sure if that's the target branch for KitKat but would probably be a good way to determine what's needed to get 3.4 booting.

https://github.com/JB1tz/vigor_aosp_kernel
[HTC Rezound] _litz:
Ok, switching back to the other repo restores proper speed.

Place the following in .repo/local_manifests as local_manifest.xml :

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project path="hardware/qcom/display-legacy" name="vigor/android_hardware_qcom_display-legacy" >
<project path="hardware/qcom/display-legacy" name="CyanogenMOD-11-Legacy/hardware_qcom_display-legacy" branch="cm11" />
</manifest>

---------- Post added at 01:48 PM ---------- Previous post was at 01:44 PM ----------

And now, we have a new loop that's causing undo load ...

I/auditd ( 1841): Starting up
E/auditd ( 1841): Failed on audit_set_pid with error: Protocol not supported

Most likely that's caused by all the selinux disabling
[HTC Rezound] Flyhalf205:
[MENTION=4317549]_litz[/MENTION]

You have audit disabled right? https://github.com/vigor/vigor_aosp_kernel/commit/f844c0c69768a385f64d044a61c9f68841b4fcc2
[HTC Rezound] _litz:
verified in git log :

commit f844c0c69768a385f64d044a61c9f68841b4fcc2
Author: David Hays <dhays90@gmail.com>
Date: Tue Nov 5 23:35:20 2013 -0600

Revert "defconfig: enable SELinux"

This reverts commit https://github.com/Flyhalf205/vigor_aosp_kernel/commit/a

Change-Id: Id275d73db56ef35c06a13708b2af737d4bac098b

It's auditd itself, the daemon is still being built and is trying to run.
[HTC Rezound] Jonman409:
This commit disabled the audit support:

https://github.com/vigor/vigor_aosp_kernel/commit/f844c0c69768a385f64d044a61c9f68841b4fcc2

You can re-enable AUDIT and just disable SECURITY_SELINUX.

Edit: Sniped
[HTC Rezound] _litz:
Might have to try this, see where it leads.

For now, removed the auditd binary, and we'll see what happens

Edit: that fixes the auditd errors but it's still stuck in something during boot

---------- Post added at 02:20 PM ---------- Previous post was at 01:59 PM ----------

Aha!

Reverting the revert of enabling selinux ... and adding "selinux=0" to the kernel cmdline restores normal boot.

edit : well, kinda ... it finishes booting then locks up on the "Enable USB Storage" screen.

---------- Post added at 02:48 PM ---------- Previous post was at 02:20 PM ----------

edit #2 : auditd errors are happening in 10.2 as well
[HTC Rezound] Snuzzo:
Just built with AOSP 4.6 arm-eabi, testing on my 9/29 ION build of Carbon. No boot. Unable to pull a last kmsg.
[HTC Rezound] Jonman409:
Cool, thanks for trying. Right now I just fixed the compile errors and created the vigor stub. I'll check the initialization from the current kernel against the CodeAurora. I'll keep playing with it.

Do you know if there's a way to go back to dev unlocked to allow 'fastboot boot zimage'?
[HTC Rezound] _litz:
I have a suspicion that disabling selinux at the kernel level is not the way to go ...

I think it's intertwined too much with stuff in the OS. Just seeing lots of issues when it's removed.

---------- Post added at 04:23 PM ---------- Previous post was at 04:02 PM ----------

Yep, had to revert the selinux revert in 10.2 ... was throwing an auditd error every second in log, which meant the phone never entered deep sleep (kept trying to start/restart auditd endlessly)

Trying to get 11 to do permissive now, too ... (atm, can't get the darned thing to complete a boot)
[HTC Rezound] kkozma:
What all have you changed?

I've got a few hours to mess around so I was going to try to see if I could get the RIL working a little better.
[HTC Rezound] Snuzzo:
Vinylfreaks patched 2.27 or JB's 2.25 hboot. Both work with the latest radios.
[HTC Rezound] _litz:
At the moment, I'm working off a vanilla repo sync .... then :

pushd kernel/htc/vigor-3.0

git revert --no-edit f844c0c69768a385f64d044a61c9f68841b4fcc2

popd

add "androidboot.selinux=permissive" to BOARD_KERNEL_CMDLINE in BoardConfig.mk

and pick the following cherrypicks:

# frameworks/av

getcherrypick 53186

getcherrypick 53324

# frameworks/native

getcherrypick 53161

getcherrypick 52994

getcherrypick 53162

getcherrypick 53163

getcherrypick 53164

# hardware/libhardware

getcherrypick 53072

# hardware/libhardware_legacy

getcherrypick 53074

getcherrypick 53165

getcherrypick 53073

# hardware/qcom/audio-caf

getcherrypick 53166

getcherrypick 53023
[HTC Rezound] kkozma:
I don't see how this could cause a no boot situtation, but did you add BOARD_HAVE_PRE_KITKAT_AUDIO_BLOB=true to one of the board config files?

Edit: Are you guys on hangouts? I use the same username [MENTION=5499064]gmail.com[/MENTION]. Might be easier to discuss in a chat than on a message board.
[HTC Rezound] _litz:
Ugh ... you know, I added the 53224 cherrypick which enables that, then didn't add the config line.

We should probably do a g+ circle for cm11 dev stuff.
[HTC Rezound] pioneersohpioneers:
I didn't want to clutter this thread w/ non-dev talk, but i'm having fun watching the progress unfold! don't take it to a chat!

or do... just keep up the great work!
[HTC Rezound] jon7701:
If they use G+ though it could help them gain progress even faster and they would be able to directly share information instead of refreshing their browser for it. Anyways good work guys, I tried to build cm11 but i kept getting a certificate error every time i would try "repo init -u git://github.com/vigor/android.git -b cm-11.0" if anyone knows how to fix it i would appreciate it.
[HTC Rezound] _litz:
*sigh* ... this is like taking a step forwards, and then a leap back.

*if* I get it to complete a boot, it freezes on the first UI screen (USB storage if plugged in, welcome to CyanogenMod if not) ... have to pull battery to recovery, and then it never boots again. Just spinning circle forever (and no logcat).

This is frustrating. Two days ago, we had a perfect boot, and usable UI, now nothing.
[HTC Rezound] kkozma:
You shouldn't have to worry about a certificate at all. You can try setting up the shared keys. Just google it up, can't remember how to do it off the top of my head.

---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------

Mine's rockin' up a build now. I did the exact same things you did but I didn't revert the SELINUX commit and I didn't add that line.

Will report back in a few. If it doesn't work, it's likely something CM pushed since yesterday, Those guys have very little regard for testing if their code breaks legacy devices. Happens ALL the time.
[HTC Rezound] _litz:
You have a working boot?? Or you're building now ... If latter, I'm interested to see if you see the same thing.
[HTC Rezound] kkozma:
It;s building now. Sorry, should have been more specific.
[HTC Rezound] _litz:
It's definitely sound that's killing it. Rebuilt the rom with sound = dummy (instead of caf) and it booted right up.
[HTC Rezound] kkozma:
ORLY? Hmmm. Well, mine's STILL not freakin' done. I'd really like to know what the heck takes 4.4 so long to build. It's not THAT much different in all honesty.
[HTC Rezound] _litz:
Takes me 45mins from dead clean ... 10.2 takes 18 minutes.

---------- Post added at 07:04 PM ---------- Previous post was at 07:02 PM ----------

Also, with sound disabled, I get perfect run out of permissive selinux (so there probably isn't a need to try and disable it completely, esp. since that seems to just make auditd freak out)
[HTC Rezound] kkozma:
18 minutes?! Jeeze! What kind of machine is that?

I just noticed something. CWM does NOT charge. Just realized my battery doesn't have enough juice to flash the rom I just waited an hour and 20 minutes for.

*Edit: same results as you. Booted up and crashed...
[HTC Rezound] _litz:
I got tired of waiting for 2-3 hours for cm9 to build for the touchpad, so I built a build box.

(8x)

vendor_id : GenuineIntel

cpu family : 6

model : 42

model name : Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz

Disable your audio, and do a new build, it should boot right up.

Make sure you've reverted the selinux revert, and added the kernel cmdline option.

I think we should run w/out audio for the time being (at least until that issue can be cornered) and work on sdcard and ril stuff.

Seems like a lot of the rest of it is working ... touch screen works, it sleeps properly, wifi works, all kinds of good stuff.
[HTC Rezound] kkozma:
I'm going to try one more thing before I give up on the audio again...

I have a AMD FX6300 which I just bought a month ago. 8GB ram... I think my hard drive is really slowing it down though...
[HTC Rezound] _litz:
Finally found an app that worked .... this should whet a few appetites ...

---------- Post added at 07:49 PM ---------- Previous post was at 07:44 PM ----------

Two things you MUST do ...

1) enable ccache and set its size to 8gb

2) buy another 8gb of memory

You'll see your build times drop by 50% at least.

This is my "make" script ...

cd ~/Android/cm11.0-rezound
TOP="~/Android/cm11.0-rezound"; export TOP
source build/envsetup.sh
export USE_CCACHE=1
export CCACHE_DIR="/home/litz/.ccache_cm11.0-rezound"
ccache --max-size=8G # needed for first run only

make clobber
time brunch vigor 2>&1 | tee build.log
[HTC Rezound] kkozma:
Does the browser work? When I had it booting yesterday, the browser would open but then go directly to a black screen.

---------- Post added at 07:55 PM ---------- Previous post was at 07:49 PM ----------

Ok, I just rebuilt with *ONLY* these commits.

Booted right up and the sounds works as good as it did before...

So it's got to be something in one of these that breaks it.

^^^ I'm going to go through these one at a time till it breaks.
[HTC Rezound] Neo:
On for this however you never respond on a timely manner hahaha usually it's a few days later <_<
[HTC Rezound] kkozma:
You know. I use google talk. For whatever reason when you guys use the web interface in G+, I NEVER get the messages.