yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] TheBr0ken:
selinux is not required for cm-10.2/4.3 and not your no-boot issue. Unless you want to start seeing a bunch of audit messages when it does eventually boot, I wouldn't mess with it untill its filly implemented. Does the boot animation come on? If you have it plugged in while its trying to boot, does the battery LED come on? If using TWRP, copy the recovery log to sd and it should tell you if it cant mount /system. If you are trying to use TWRP's file manager to browse /system and only see /bin you need to go to mounts and mount /system to view it, because it doesnt mount for viewing by default.

for selinux I'd create a second deconfig and just merge everything to that and modify the second one with selinux policies to test. this way you can still have a functioning non-selinux kernel untill the bugs are worked out. you can then add have_selinux flags to choose between the two, like this for the kernel:

TARGET_KERNEL_VARIANT_CONFIG := vigor_defconfig
-ifeq ($(HAVE_SELINUX),true)
TARGET_KERNEL_SELINUX_CONFIG := vigorselinux_defconfig
-endif

and this to copy your policies:

# SELinux
ifeq ($(HAVE_SELINUX),true)
BOARD_SEPOLICY_DIRS += \
device/htc/vigor/sepolicy

BOARD_SEPOLICY_UNION += \

just dont add HAVE_SELINUX=true anywhere in the device tree. leave it out and then you could brunch as normal for non-selinux and run "export HAVE_SELINUX=true" before you brunch to set the global flag to build with selinux
[HTC Rezound] kkozma:
I can see everything in recovery. But to answer your questions, no. No bootimage, nothing. It flashes the HTC splash screen, goes dark for about 30 seconds, and reboots back to recovery.
[HTC Rezound] Flyhalf205:
I took BOARD_WANTS_EMMC_BOOT := true out of the BoardConfig.mk in device git and the phone never rebooted back to recovery. Just stayed at black screen with no logcat still. I say I am sure that the /system isn't being mounted is because in the log you posted, a few system bin files can't be found. And if /system was being mounted. You wouldn't get cannont find /system/bin when trying a logcat.
[HTC Rezound] TheBr0ken:
Another thing about selinux. Nobody, and I mean nobody is running with it besides maybe straight aosp 4.3, maybe. It's not fully implemented yet to cm. Just cause the policies are in place doesn't mean it's using it. All it will do is shut the selinux audit up. If you enforce it your device will become unusable, and you'd have to wipe and reflash. Just FYI, so your not chasing ghosts
[HTC Rezound] dlumberg:
What's the original method for getting around the refcount in APM? I tried this one but they've changed AudioPolicyManagerBase.cpp since that commit and it didn't get me around it.

also anyone try this yet?
[HTC Rezound] Snuzzo:
[MENTION=3082717]Flyhalf205[/MENTION]

This could be the reason why were not mounting system as it may require a kernel patch for SELinux, it means the rom isn't able to boot, which labels it down to 1 of 2 things, ramdisk or kernel or combination. Ive not been keeping up on these things as I am literally burnt out. I will still maintain my kernel through upstream patches but as far as mods, I doubt there will be any changes.
[HTC Rezound] Flyhalf205:
Well the pyramid got their system to finally mount. It was in the ramdisk which is where I figured it was. But from what I am reading with the guy. It still doesn't boot. But it is progress. I'll try to make the same modifications today.
[HTC Rezound] kkozma:
I saw that post this morning too, did he commit his changes anywhere? FWIW going by the above comments, they are trying to use SELinux so if that won't work, maybe just the change to the ramdisk will do it for us.
[HTC Rezound] Flyhalf205:
This was the only thing I could pull. It doesn't look right at all.

https://www.dropbox.com/s/kqayptfxa3ww3yz/dmesg.txt

[MENTION=2658396]kkozma[/MENTION] You want to try building with this commit and my stock kernel without selinux? https://github.com/Flyhalf205/device_htc_vigor/commit/bb0e82a9761353eb1286122ebbb51272a8d3d0bc
[HTC Rezound] kkozma:
Sure, but I clobbered before so it's going to take a while. My build machine is pretty ancient. Takes about 3 hours.
[HTC Rezound] GrayBoltWolf:
If I knew anything about git besides initializing a repo I would do it for you. I build in ~20 min.
[HTC Rezound] dlumberg:
If you're pointed at Flyhalf then it's just "repo sync" :)
[HTC Rezound] Flyhalf205:
That's all I know too. Ha. But if you want to build and do trial and errors and log errors would be great help. If you get the time to do so.
[HTC Rezound] kkozma:
Holy poop! 20 minutes!??!!

Seriously though. What are your specs? I'd like to upgrade my build machine and I'd be happy with anything under an hour.
[HTC Rezound] TheBr0ken:
Do you have ccache enabled? Takes me 200 minutes without and 60 minutes with it enabled on a clobber. Most important is processor and HD, I'm looking into a cheap ssd, which will hopefully cut my build times in half
[HTC Rezound] GrayBoltWolf:
Just a 3570K overclocked to 4.4 GHz. And I guess the 7200 RPM HDD helps a bit also.

I'll see if I can get it working.
[HTC Rezound] poppy22:
I translated CM-10.2 when it came to such a mistake, I know how to solve.

[MENTION=3082717]Flyhalf205[/MENTION] [MENTION=2658396]kkozma[/MENTION]

target SharedLib: libandroid_runtime (/home/poppy/cm2/out/target/product/villec2/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so)
frameworks/av/media/libstagefright/AwesomePlayer.cpp:1012: error: undefined reference to 'android::LPAPlayer::mObjectsAlive'
frameworks/av/media/libstagefright/AwesomePlayer.cpp:1084: error: undefined reference to 'android::LPAPlayer::LPAPlayer(android::sp<android::MediaPlayerBase::AudioSink> const&, bool&, android::AwesomePlayer*)'
frameworks/av/media/libstagefright/AwesomePlayer.cpp:1685: error: undefined reference to 'android::LPAPlayer::mObjectsAlive'
collect2: error: ld returned 1 exit status
make: *** [/home/poppy/cm2/out/target/product/villec2/obj/SHARED_LIBRARIES/libstagefright_intermediates/LINKED/libstagefright.so] Error 1
make: *** Waiting unfinished tasks....
[HTC Rezound] kkozma:
No dice. kmsg attached.
[HTC Rezound] GrayBoltWolf:
I got this far. It can't find the manifest in your 10.2 branch.
[HTC Rezound] Flyhalf205:
Well dang. That commit does indeed mount the partitions correctly. You can tell by booting into the recoverg.IMG that it creates during brunch. Good way of checking. So I really don't know
[HTC Rezound] kkozma:
Well, you know. Now that I think of it, I did dirty flash it so maybe that's why. I'll try again.
[HTC Rezound] dlumberg:
With your selinux build, did you add ro.build.selinux=1 to build.prop?

I noticed that there's an init.d script for selinux by default.
[HTC Rezound] kkozma:
No, sure didn't.

Also just tried to flash again with a clean wipe. No dice. Same as before.

This is from my last_kmsg

[ 2.960968] EXT4-fs (mmcblk0p29): mounted filesystem with ordered data mode. Opts: data=ordered,noauto_da_alloc
[ 2.987487] EXT4-fs (mmcblk0p35): mounted filesystem with ordered data mode. Opts: data=ordered,noauto_da_alloc
[ 3.015563] EXT4-fs (mmcblk0p36): mounted filesystem with ordered data mode. Opts: data=ordered,noauto_da_alloc
[ 3.073760] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: data=ordered,noauto_da_alloc

fstab.vigor

/dev/block/mmcblk0p22	/boot emmc	defaults	defaults
/dev/block/mmcblk0p23	/recovery	emmc	defaults	defaults

/dev/block/mmcblk0p29	/system	ext4	rw,data=ordered,noauto_da_alloc	wait
/dev/block/mmcblk0p35	/data	ext4	noatime,nosuid,nodev,data=ordered,noauto_da_alloc	wait,encryptable=footer
/dev/block/mmcblk0p36	/cache	ext4	noatime,nosuid,nodev,data=ordered,noauto_da_alloc	wait
/dev/block/mmcblk0p30	/devlog	ext4	noatime,nosuid,nodev,data=ordered,noauto_da_alloc	wait

It's definitely mounting the filsystems, but it's not working right obviously. I also noticed it's not mounting boot or recovery. Maybe there's a clue there?
[HTC Rezound] dlumberg:
This could be important, from the last_kmesg a few posts back:

[ 2.865997] Warning: unable to open an initial console.
[ 2.867950] Freeing init memory: 252K
[ 2.871673] SELinux: Could not mount selinuxfs: No such device
[HTC Rezound] wlmeng11:
What command, who's tree; give more info

Flyhalf's manifest should point to all of his own repos.

Some basic Git:

git clone

git pull

git push

git log

git branch

git checkout

git merge

git add

git commit

git diff

git status

git rm

git mv

git remote add

Some less-basic Git:

git cherry-pick

git rebase

git bisect

git submodule

Most of the commands do what they sound like. The official website has some good documentation (http://git-scm.com/), otherwise search Google/Stack Overflow for anything not in the docs.
[HTC Rezound] TheBr0ken:
well it looks like you can take all the selinux stuff I said earlier and throw it in the trash. While its not needed for 4.3, It looks like cm, with a lot of its recent commits is making it a necessity to build cm. Although the warning is still out there, that unless its verified fully functional I'd wait before you enforce the policies, cause if there is an error then it will deny access. My last gs3 build still had denied logs for settings and frameworks and a few other core items. Since I have not enforced these policies I have no issues. Just FYI
[HTC Rezound] GrayBoltWolf:
I get the error when intitalizing his cm10.2 branch.
[HTC Rezound] wlmeng11:
repo init -u git://github.com/Flyhalf205/android.git -b cm-10.2

This fails?
[HTC Rezound] kkozma:
To do this you'd put setenforce=0 someplace in the init.rc, right?
[HTC Rezound] dlumberg:
From: http://m.androidcentral.com/android-43-and-beyond-root-going-away-stock-roms

interesting

---------- Post added at 01:25 AM ---------- Previous post was at 01:22 AM ----------

setenforce 0

In init.rc

According to : http://selinuxproject.org/page/SEAndroid
[HTC Rezound] TheBr0ken:
Check out the last item listed in about screen

There you can enable it. I'd suggest running adb shell su 0 setenforce 1 vs adding an init script. The terminal command enforces it, but it will not persist on reboot
[HTC Rezound] kkozma:
Well, I officially give up on 4.3 for the Rezound. :( Sorry guys.

I don't understand it. I've gone over absolutely everything for similar devices to ours that boot and it's just not happening. Someone a whole lot smarter than me is going to need to figure this out.
[HTC Rezound] AtomicFizzle:
Okay, back to working on getting the camera working in ION instead? ;)
[HTC Rezound] Flyhalf205:
One day maybe. I given up right now. Hopefully soon though. Could be our dated libs and egl and kernel. Just old legacy phone.
[HTC Rezound] Flyhalf205:
Well I knew it wouldn't be too long. I may have some good news tonight or tomorrow some time regarding 4.3
[HTC Rezound] Neo:
Guess it's time I take a break from my toolchain madness and try to help get this thing going ;)
[HTC Rezound] mjones73:
Gotta love this community. :)
[HTC Rezound] Emmanuel U:
What error are you guys receiving? I may be able to help as I'm working on getting this to my device too
[HTC Rezound] Neo:
Just a matter of no boot ani and boot. We have splash screen and that's it. (for now ;) )

I did however run into a build error with LatinIME earlier for a call to inline.. It was set to -Werror on inlines but I got past it a while ago.

Oh, there was also 1 Audio error I ran into but fly helped me past it with a cm cherry pick to hardware

EDIT: I'm getting installs so it's not long before I flash and see if it boots
[HTC Rezound] Emmanuel U:
alrighty well let me know if any help is need, I'm available
[HTC Rezound] Neo:
CM-10.2 (Android 4.3) Booted

Ok so.. firstly, if it wasn't for flyhalf's suspicion with the toolchain and for the audio fix he gave me from cm, I never would have known how to get this to boot. So thanks Flyhalf!

Right off the bat, the boot animation is extremely flickery. like a strobe effect which probably sums it up best. Once in the rom, I got 1 random reboot but it has been running fine since then with no reboots.

The screen strobing is constant in rom and when it actually stops, simply touching the screen causes it to strobe again lol.

There is no data. Most likely ril related.

Wifi, bluetooth, native tethering all work.

Sd card and internal sd card mount just fine. My print screens however defaulted to internal sd which I thought was interesting. I do have access to my pics in gallery which are both on sd and internal so that's good.

Camera doesn't work right now as shown in the image above (application not installed message)

From what I can tell, it generally feels pretty fast and snappy compared to cm-10.1 for a stock rom.

All sounds and haptic work just fine

Keyboard works just fine

There is a new app in the app drawer called "Focal" but it force closes when you touch the focal option inside of it due to no presence of camera.

That's all for now folks! Progress is progress.

-Neo
[HTC Rezound] TheBr0ken:
This part right here is what I like out of the whole thing. 4.3 was eventual. If screenshots default to internal sd, this means it is now primary!
[HTC Rezound] kkozma:
Kickass! Now the real fun starts. Getting it stable. lol
[HTC Rezound] REV3NT3CH:
I dont know if it helps camera wise but i read a comment someone had left about installing the 4.3 camera app a weird way from system/app but i wonder if built into the rom that method could work....ill take a gander around and see what i find...i also have linux on my machine loaded with all sorts of tools and goodies to help out
[HTC Rezound] Neo:
my little work arounds that need some cleaning up (but I'm out of time) are pushed to my git. cm-10.2 branches for build and device. I basically forced the use of the 4.6 toolchain (and not the ref that gets synced with the 10.2 repo, the ref from the cm-10.1 sync).

Fly figured it out today when another msm8660 device got boot by switching to the 4.6 chain.
[HTC Rezound] Flyhalf205:
I'm glad that internal and external storage works. Was my biggest concern.

The RIL will be an easy fix what it looks like. I'll get some time tomorrow to deal with it. I've told neo how to if his current build fails.

Camera not sure. Haven't looked into it. Could be the camera wrapper needs updating.

Graphic issues should be pretty easy if the problem is what im thinking.
[HTC Rezound] kkozma:
Very awesome guys!
[HTC Rezound] REV3NT3CH:
again i dunno if it helps but i dug this up.

http://galaxy-note2.wonderhowto.com...msung-galaxy-note-2-no-root-required-0147690/ and http://xdaforums.com/showthread.php?t=2340858

also in the second link i provided there is a comment if you scroll down by rickoslyder that had an issue with the app not installed error and found a workaround....i hope this helps
[HTC Rezound] Emmanuel U:
Nice job on getting it booting, do you happen to have your device tree uploaded some where?
[HTC Rezound] dlumberg:
Focal is the new CM OSS camera from Project Nemesis. I'm glad to see that they've included it already, would be nice to see that working on Rez.
[HTC Rezound] TheBr0ken:
Just use http://github.com/Flyhalf205 tree and force kernel to compile with 4.6 GCC

You will get a bad ril, so unless you have a stock recovery....

---------- Post added at 07:52 PM ---------- Previous post was at 07:48 PM ----------

It's glitchy on supported devices, but pretty cool regardless
[HTC Rezound] Neo:
What TheBr0ken said. Flashing it in it's current condition kills your data and not a flash to sense and back will help you. You have to flash a stock recovery, factory reset from bootloader, then you should be good. I have this if anyone needs it to get data back.

As far as building is concerned, just need to delete all the current 4.6 chains in prebuilts, clone in the specific ref 4.6 toolchain versions from cm-10.1, add a target to BoardConfig.mk in device, and that should do it.

I of course went overkill and added an additional target to build/core/config and deleted the 4.7 chains just to be sure I was building off 4.6 :D
[HTC Rezound] Flyhalf205:
They use a bit different RIL setup than we do [MENTION=4203241]IAmTheOneTheyCallNeo[/MENTION] So they shouldn't have a RIL problem once they get it booted.

[MENTION=4193353]xmc wildchild22[/MENTION] what is your current progress. I've been keeping an eye out on JellybeanDS github.
[HTC Rezound] Emmanuel U:
http://xdaforums.com/showpost.php?p=44472938&postcount=346

I've fixed avc errors, hwcompser errors etc. Now I have some stuff to do in the EGL
[HTC Rezound] Flyhalf205:
[MENTION=2658396]kkozma[/MENTION] [MENTION=3419683]Snuzzo[/MENTION] [MENTION=4803670]iHateWebOS[/MENTION]

Know anything about kernels? Right now whoever syncs with my repo. It should build with 1 or 2 cherry-picks you have to throw in. It should boot. Has severe strobe/flicker display. I figured it was the display panel being too high. We'll have to go out and find out what kernel experts think.
[HTC Rezound] kkozma:
Only thing I can really help with is debugging code. I don't pretend to understand how all of this works together! lol

I cracked out a few builds today and I also noticed that sound doesn't work either. In fact it's as if there's no sound device present at all on my phone.

Per the screen flicker, here's the corresponding entries from the logcat on my phone.

I know I remember early on messing with the code in hardwarecomposer.cpp and gralloc.c. Wonder if our clue is in there somewhere?
[HTC Rezound] REV3NT3CH:
I keep on getting fetch errors in terminal. Would like to help but this keeps getting in my way
[HTC Rezound] Neo:
I had sound output just fine on my build. Wonder what changed
[HTC Rezound] Flyhalf205:
Lots has in the audio-caf...
[HTC Rezound] TheBr0ken:
Revert this commit. Your not building with gcc-4.7 and shouldn't need this.

https://github.com/Flyhalf205/andro...mmit/8a20462547e83d602f4fbe3fead7581fa289445a
[HTC Rezound] Flyhalf205:
https://github.com/Flyhalf205/andro...mmit/a3be5e1b0b6a64f56879ccc3912e864d32f44bbd

If you disable TARGET_DISABLE_ARM_PIE := true you should be able to build with 4.7 GCC and boot.
[HTC Rezound] TheBr0ken:
No, you don't disable it. You need to enable it to build with 4.7 and boot. It's already disabled
[HTC Rezound] Neo:
He meant disable the disabler. # out the disable line. <_< technicality lol
[HTC Rezound] kkozma:
disable the disabler. nice.

FYI everyone: It will not build unless you revert this commit... https://github.com/Flyhalf205/device_htc_vigor/commit/f06ec6789a88e6de0eb2de343a211c8b31bef7c5
[HTC Rezound] Flyhalf205:
Thanks for heads up. I'll fix that later.
[HTC Rezound] TheBr0ken:
I know, just being a pain :p
[HTC Rezound] Snuzzo:
Try using the newer himax. You may lose boot ani but it could possibly correct it. Other than that it could potentially be an mp4/vidc issue. Similar thing i/zarboz/ihatwebos was experiencing with getting the cameras working on Sense4+, i believe once that is corrected should start working on rebasing the kernel off 3.4.10 villec2. I stepped out of the scene due to personal reasons and it taking up too much of time, plus I'm somewhat burnt out.
[HTC Rezound] Neo:
The latest CM-4.2 source now requires you to specify a Target CPU Variant during the build process. Based on TheBr0ken's suggestion, I'm going to specify our target cpu variant as "scorpion" and build later.

https://github.com/IAmTheOneTheyCal...mmit/e5bcc5c537c24757c8afca9a0991239929de127f

EDIT: Just realized Fly figured this out 19 hours ago and went with Scorpion himself hahaha. So I guess my commit is not necessary.
[HTC Rezound] TheBr0ken:
This was done for the pyramid a 3 or 4 days ago, that's where I saw it. I'm sure Fly got it from there too, They are definitely on top of their stuff.
[HTC Rezound] kkozma:
I found some stuff from a few other repos and I'm happy to report it fixes the flickering strobe effect. :D WOOOOT!

Swap out display-legacy with: https://github.com/OpenSEMC/android_hardware_qcom_display-legacy

Swap out media-legacy with: https://github.com/OpenSEMC/android_hardware_qcom_media-legacy

Now, we need to figure out:

camera

sound

and the phone app keeps fc-ing.

*edit* going to try their audo-caf too and see if that fixes audio.
[HTC Rezound] kkozma:
So it's not the caf I don't think. Tried the old one and it still doesnt't work

my errors when trying to play a sound

*edit* sound could very well be a big derp on my part. Rebuilding now. Will report back later. lol

*edit part ducks* Won't build now. Bunch of new issues
[HTC Rezound] TheBr0ken:
To fix your new errors

http://review.cyanogenmod.org/#/c/47711/

and if you encounter them:

http://review.cyanogenmod.org/#/c/47238/

http://review.cyanogenmod.org/#/c/47233/

and Check out Team-Hydra to fix your camera.
[HTC Rezound] TheBr0ken:
May want to add;

TARGET_QCOM_MEDIA_VARIANT:= caf

to device boardconfig.mk (since audio and display are defined there).
[HTC Rezound] kkozma:
This won't work because we need media-legacy.
[HTC Rezound] TheBr0ken:
Ha!, forgot that, Then you need to add

TARGET_QCOM_MEDIA_VARIANT:= legacy

And you really cant use CM frameworks, because they reference either media, or media-caf for include files

https://github.com/CyanogenMod/android_frameworks_av/commit/e45891f3fd811ae000890c27b122931b10321f81

no mention of legacy. You'll need :

https://github.com/OpenSEMC/android_frameworks_av/commit/d4fed2bbf8d768e0279f374567744be62d0190d0

those are examples, so use their media-legacy, display-legacy, frameworks av possibly native too, but I havent looked at that
[HTC Rezound] kkozma:
Yeah, I've got a build going now with the team-hydra frameworks_av and native...

They don't have the legacy stuff in them either, but what they do have is what I think is the camera fix... If it works, I'll fork the OpenSEMC frameworks_av and merge in the team hyrdra camera stuff.

In the meantime, IDK what's going on, but my machine is RIDICULOUS slow right now and I think it's stemming from something on this website. Everytime I visited xda yesterday from work my computer was flagged as trying to make an internal attack on our network.
[HTC Rezound] TheBr0ken:
The camera fix is there, but there may still be issues with the ffc, unless they recently fixed that. So for now you'll have to revert back to using a mirror for selfies.
[HTC Rezound] kkozma:
LOL! I have never once used the FFC on my phone.
[HTC Rezound] TheBr0ken:
Only time I've ever used it is when someone says it crashes the phone. The 5 year old in me, obviously has to check.

---------- Post added at 08:31 PM ---------- Previous post was at 08:23 PM ----------

I'm thinking you may have to use OpenSEMC's av for the media stuff and cherry-pick https://github.com/Team-Hydra/android_frameworks_av/commit/1969f30627005a2303751294b3b805ea9ef9cb7a

Think the camera stuff may be easier to pick that digging for media-legacy stuff
[HTC Rezound] kkozma:
Well, their camera fix doesn't work for this phone. :(
[HTC Rezound] TheBr0ken:
Did you make sure you looked at their msm8660-common and pyramid repos and pull their camera changes?
[HTC Rezound] kkozma:
No, sure didn't think to look there.

I'm callin' it a night tonight. I'll look into it tomorrow if someone else hasn't done it by then.
[HTC Rezound] cj360:
Could you specify what fixed the -Werror on inlines? I'm getting the exact same error just with another device building 4.3.
[HTC Rezound] TheBr0ken:
Remove -Werror from here -> https://github.com/CyanogenMod/andr...tinIME/blob/cm-10.2/native/jni/Android.mk#L30
[HTC Rezound] Flyhalf205:
Or remove lines 33-37...

Been really busy past few days and next couple of days. Good job on the flicker part [MENTION=2658396]kkozma[/MENTION]

I've had to use my HTC Thunderbolt today. My Rezound won't pass the white HTC screen or if it does. Turns itself off after several minutes.

[MENTION=2658396]kkozma[/MENTION] my audio works in my builds?
[HTC Rezound] Flyhalf205:
That actually might be possible to port https://github.com/Team-Hydra/android_frameworks_av/commit/1969f30627005a2303751294b3b805ea9ef9cb7 into the camera wrapper found in the msm8660 repo.
[HTC Rezound] Flyhalf205:
This link is confidential :D

http://goo.gl/Y4qqpQ

About 201.8 MB...Looks like everything but camera is working. Been pushing a lot of things to my git.