yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] MaulingDeOso:
There's two reasons it's tearing:

A: The hardware overlay, which is the normal way of outputting videos, with full hardware decoding and naturally vsync-locked blitting, isn't working. So it falls back to decoding to a framebuffer.

B: Hardware vsync is disabled. This means a thread on the client-side waits for the vsync interrupt and then blits. It is susceptible to interruption by scheduling. The non-overlay blits are hence using an inferior vsync control method.

What I presume happens in your case is that while storage is mounting many processes are i/o locked, and during that time said processes are not likely to steal context away from the thread receiving the vsync interrupt.

I've got hardware vsync working with my experimenting and it does fix tearing, but I've left other stuff broken. Once the One S C2 kernel is released, we can try to port MDP code from that, or if Chad decides to upload his 4.2 tree eventually I might try to rebase our kernel to jb_mr1_chocolate.

Additionally, CyanogenMod repositories have also backed off on full "IONization" for a few 8660 devices like the Xperia S and Galaxy Note. Therefore, I think pmem will be around for a bit longer.

To sum it up: we know what's wrong, but it's not a simple fix.
[HTC Rezound] siulmagic:
i wonder if chad has taken a look at the skyrocket, tmo sgs2, JB trees, they are both S3 devices.
[HTC Rezound] dmeadows013:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Protekk added it to gerrit, so it's supported. Also , he's working on something special
[HTC Rezound] chad0989:
Have at it. Hopefully you can make some progress. I've been ultra busy lately.

repo init -u git://github.com/Chad0989/android.git -b cm-10.1

To everyone else who pulls this:

Yes, I know camera switch and video recording is broken among other things.
[HTC Rezound] kkozma:
Has anyone been able to pull cm10.1? Mine fails at android_prebuilt. Yet another git issue???
[HTC Rezound] Neo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Shrike pulled and built successfully just a little while ago
[HTC Rezound] shrike1978:
Yea, it built just fine. As of right now, it doesn't offer anything over CM10 other than BT calling, and the cameras aren't working right yet. Most people are going to be happier on 4.1.2 or 4.0.4 for now, and I'm not going to do any serious work on it until someone works some magic on the cameras. Out of my league for sure, so I'm going to wait patiently and continue to try to help out in the areas were I don't feel completely useless. ;)
[HTC Rezound] heyis4horses:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Tried to pull but my internet decided that tonight was the night that it felt like being garbage

edit: Check that, it would appear that my internet responded to my constructive criticism and is responding accordingly. If builds aren't posted then I'll post one tomorrow if anyone would like to give it a shot
[HTC Rezound] jon7701:
I have a build already made, but im not sure if we can post it since chad hasnt said we can post 4.2 roms.
[HTC Rezound] Snuzzo:
What's the status on it Jon? What's the overall "feel"? Is it an ion or pmem build?
[HTC Rezound] shrike1978:
It's pmem. In fact, it's the same exact kernel as the CM10 pmem build, so our current pmem kernels work on it. I have Ermahgerd running on it right now.
[HTC Rezound] jon7701:
It appears to be pmem, and it feels like its smoother then CM10, but that may just be placebo effect. The FFC and rear camera works but video recording doesnt as chad has mentioned. Running for about 45 min i have had 1 cold reboot. For me its usable as a DD since i hardly use video recording. HD playback doesnt work on YouTube either.

Also since i have already taken up this space, I want to thank chad for giving us 4.2. :cool:
[HTC Rezound] heyis4horses:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I think we're allowed to post it if it wasn't restricted again. But also, I don't wanna be the one to get it wrong
[HTC Rezound] siulmagic:
i dont think chad will mind, since he dint say other wise in the post he made.
[HTC Rezound] chad0989:
Have a temp fix for camera switch until I figure out what in libcameraservice is causing the issue.
[HTC Rezound] mike85k:
Is GPS working on 10.1 for anybody else? It won't lock for me.
[HTC Rezound] siulmagic:
so i managed to grab cm10.1 from someone, so far gsm works, but seems the phone think there is no sim card, when infact there is one inserted, not sure if i got this bug from flashing over cm10(pretty sure this is not the case). good news is that signal bars are fixed, since dbm reading works for gsm now.
[HTC Rezound] shrike1978:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Same. I haven't managed to get even a single satellite. I'm gonna go outside and let it run a few minutes today.

Signal bars are working correctly in general now. CDMA/LTE weren't working right before either, but seem like they're in line with Sense now.
[HTC Rezound] siulmagic:
i see so the dbm reading was not correct in cdma also.
[HTC Rezound] chad0989:
Fixed GPS. CM10.1 seems to only have a GPS HAL for newer radio firmware that we don't have.
[HTC Rezound] kkozma:
So I just built and everything looks great so far.

Amateur hour question here. How/what needs to be modified to stop the automatic apps restore? I'd much rather rely on titanium than getting it all from the play store.

Thanks for the hard work on this Chad, really appreciate it. I'll get you a donation as soon as I can!
[HTC Rezound] shrike1978:
Don't log in to Google during initial device setup. It only triggers auto restore if you log it at that point.
[HTC Rezound] kkozma:
Yeah, I know about that, but I know in the CM10 builds it didn't download them even with signing in.

Ultimately, it's not a big deal especially with having a stop all button in the play store now, but if I decide to release a rom, that's one of the things I'd like to get rid of...
[HTC Rezound] TheBr0ken:
I'd just inform everybody to Restore their apps from Titanium before they sign into their Google Account, that should stop all market restores. I dont think you want to get rid of it as I believe when you check that option it will also keep your apps updated.
[HTC Rezound] Neo:
Mod - Delete
[HTC Rezound] Snuzzo:
Easiest way....

Don't use Titanium at all, build yourself a flashable zip to restore your apps (minus data of course).
[HTC Rezound] TheBr0ken:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Titanium apk is on my SD, no market needed ;)
[HTC Rezound] SynisterWolf:
or make a flashable zip version and just flash with gapps or after a clean install :good:

much easier than signing in. lol
[HTC Rezound] demmo86rt:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Of course, this can now be done THROUGH Titanium. :cool:

Sometimes you have to be smarter than your smartphone.
[HTC Rezound] antp121:
has anyone been able to build cm10.1? i keep erroring out... ugh :(
[HTC Rezound] Obaterista93:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I'm pretty sure Wildstang built okay.
[HTC Rezound] kkozma:
Yep. I just built earlier today and it worked fine...

FYI: Netflix doesn't work, but I found this commit here, modified it for our phone, and it definitely works now.. :)

It looks like a simple init.d script but I figured I'd hard code it in and re-build anyways..
[HTC Rezound] TheBr0ken:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Nice find
[HTC Rezound] SynisterWolf:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I don't know it this has been said yet, and I'm on tapatalk so I can't search but I found something odd but works.

Streaming YouTube on my phone in HD I started to get all messed up like normal.

When it was happening I was searching through the comments and noticed if I swipe my finger up and down at a it cleared up and if I kept doing it, it would not mess up again until I stopped.
[HTC Rezound] dplane:
The newb non dev me would say that sounds like a refresh rate/vsync issue. Though that has probably been mentioned already. Just trying to be helpful in the shadow of all this devving magic :fingers-crossed:
[HTC Rezound] brenuga:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Yeah I was watching a lot of YouTube this weekend and noticed that if you get messed up and pause it, that usually fixes it temporarily. I Don't claim to understand it.
[HTC Rezound] kkozma:
I can't get YouTube HD to play at all.

Ok. I don't know whats going on. But I SWEAR that Netflix thing I posted about above worked yesterday. Today, no dice. I don't get it.
[HTC Rezound] kkozma:
So it looks like google doesn't want to support car mode anymore...

I reverted their changes to my git and now it's working like it should. Anyone is welcome to use it.

https://github.com/vwmofo/android_frameworks_base/commit/3163da50c324ddb04a6029d018913a1ca89cf240
[HTC Rezound] a.mcdear:
I'm getting pretty bad performance overall on this build. Is anybody else experiencing this? I haven't seen another mention of it, so I'm wondering whats up with my phone..
[HTC Rezound] Snuzzo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Nice find!! You should make a revert patch for us! **rock out**

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] kkozma:
If I knew how to do that I would. LOL

I'm not very good with this github stuff, AT ALL. I couldn't even figure out how to give a decent description of my commit. HAHAHA
[HTC Rezound] shrike1978:
To really work with git well, you need to work with a local copy, commit the changes locally, and then push the changes to the remote repo when you're done. Doing it that way, you have the chance to enter very long and detailed commit messages at commit time. It also lets you work with code in a trackable and reversable way, even before you push the changes publicly. Right now, I have several kernel commits locally that are going into the next version. They won't see my public github until I release.

I may do a beginner's guide to github at some point. How to do basic stuff like clones, commits, pushes, reversions, rebases, cherry-picks, merges, etc. It's knowledge that's needed to really do Android development effectively, and it's something that I had to pick up it bit at a time.
[HTC Rezound] chad0989:
Figuring git out is more difficult than getting AOSP to boot on a rezound for the first time.
[HTC Rezound] badogg:
Lol, I seriously was taking a drink of water when I read this and it was almost a real "You owe me a new keyboard" moment.

:highfive:
[HTC Rezound] kkozma:
Yes, it's a lot harder to figure out than it should be. I wanted to punch a puppy the first time I tried to push some old commits using the windows github tool.

So, it seems I can't win here. With 4.1.2 I had near perfect audio quality with A2DP streaming but couldn't make a BT phone call. Now with 4.2.1, I can make a BT call, but the A2DP stream sounds like GARBAGE. *sigh*

I'm messing around with the bitpool and sampling rates to see if I can get some acceptable quality out of this. GRRRR.
[HTC Rezound] iHateWebOS:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I want to use git from my phone with no access to WiFi, I'm looking for a good guide on that :(
[HTC Rezound] heyis4horses:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

If you did a guide on how to work git you'd make me much more competent, or just make me fell bad because I'm just as incompetent as before but this time I can cherry pick
[HTC Rezound] LunaticSerenade:
I generally try only to lurk, but I thought I would point out this thread:

How to use Github
[HTC Rezound] heleos:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I had terrible battery life for one day, turns out my gps thought it was on, caused 7 hours of awake time :o

Guess I should be more clear, what build are you speaking of? I'm on 10.1. I know there were some early on problems with gps, but those were resolved. A reboot fixed my issue as well. Running great otherwise
[HTC Rezound] Snuzzo:
Ok ok I went ahead and did it. See attached.
[HTC Rezound] siulmagic:
hey might whant to check the vivid's cm10 git/thread, they claim having video rendering working, but they have to turn off gpu rendering.

heres the link http://xdaforums.com/showthread.php?t=2026675
[HTC Rezound] chupajr:
Slightly off-topic, here's a humorous interview with Linus Torvalds discussing Git (which he created, if anyone was not aware), and how it is pretty much only popular because it's so difficult to use that it makes the alpha geeks feel good about themselves.
[HTC Rezound] shrike1978:
Well, I disagree with that somewhat...it is the best and fastest I've ever used at managing and merging multiple branches of a project. It's amazing how good it is at resolving complex merges, and how good it is at notating where the problem is when it can't. We use it at work for that reason.
[HTC Rezound] kkozma:
Do not sync up with the repo guys. CM pushed a bunch of changes for msm8660 that break our build...

https://github.com/CyanogenMod/andr...mmit/333d0e460bc6a6579c5193438fa69560abea658f

https://github.com/CyanogenMod/andr...mmit/bbd2939c1f0733e4ff01a47c4a14e76227377022

I rollled those two back and it looks like it's building, but I clobbered so I won't know for sure for a few hours. :(
[HTC Rezound] GrayBoltWolf:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I build in 34 min. :P

But, do we know if they are going to fix anything or are we going to have to manually fix it every time?
[HTC Rezound] kkozma:
I'm sure we can make it work with their changes, but this is a bit over my head. Someone smarter than me is gonna have to look at it.

I wish I would have thought to copy the error I got. Something about an OMX lib being defined that was already defined in mm-core or something like that.
[HTC Rezound] GrayBoltWolf:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I can repo sync and try to build today and then post the error.
[HTC Rezound] chad0989:
Audio HAL works fine, been using it for ~24 hours since I saw the original commit on gerrit. I want to do some more testing first though before I get rid of the audio HAL in our tree and use the caf one. Media currently requires the new display HAL, which we can't use yet.

It is nice to see Cyanogen working to add support for the s3 now though.
[HTC Rezound] chad0989:
Got video recording/playback ~80-90% working. I can record but sometimes get a corrupted video, so I wouldn't recommend relying on it for anything important. Playback is pretty solid for HD youtube, but there's occasional tearing for all playback. Not sure about netflix since I don't have an account.

Need to do more testing / reorganizing before I push it.
[HTC Rezound] docbutts:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

If you want to test Netflix, I can let you use my account for a bit if you want. Just let me know and I'll pm you the info
[HTC Rezound] MaulingDeOso:
They now have a more obvious split in the display libs trees upstream, so I'm curious how will CyanogenMod handle it. Their CM10 version has kind of anemic compatibility, so this dilemma might actually mean less work on our end. The newest version looks to have been stripped of tile rendering, so I'm not sure it'll work well on our device.
[HTC Rezound] Neo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I thought tile rendering was disabled by default in the .prop anyway?
[HTC Rezound] MaulingDeOso:
No, it's still enabled, and the module is still built in Chad's latest tree. How necessary it is for performance after the changes made to the compositing engine is questionable, though.
[HTC Rezound] Neo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

It appears that only the first commit with regards to hardware/qcom/media needs to be reverted for a build to complete. Just verified it myself. fyi to all
[HTC Rezound] kkozma:
Yep, that's correct. The 2nd one for the new Audio HAL is fine to leave alone because we don't have anything that calls to build in those folders.

Although I will say I built with the new Audio HAL and I'm quite happy with it. I was going to post my ROM but I figured I'd wait for the a-OK from Chad on the new HAL before I do so.

*EDIT* Looks like he pushed the new Audio HAL about 30 minutes ago.
[HTC Rezound] TheBr0ken:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Doesn't look like we need to revert either of those commits

https://github.com/Chad0989/device_htc_vigor/commit/ced6427c969e81ad8a14f0358ec35890f8a60399

https://github.com/Chad0989/device_htc_vigor/commit/57e9eedb3df0e045035f1e6990c9ee0608d895ac
[HTC Rezound] shrike1978:
I still had to revert 333d0e460b from android_hardware_qcom_media.
[HTC Rezound] TheBr0ken:
yup, I must have a previously reverted it and didn't realize because I sync'd this morning and got:

build/core/base_rules.mk:133: *** hardware/qcom/media/libstagefrighthw: MODULE.TARGET.SHARED_LIBRARIES.libstagefrighthw already defined by device/htc/vigor/media/libstagefrighthw. Stop.
[HTC Rezound] kkozma:
Yep, same issue here.

I got a fresh build I'm anxious to try out, but damned work is getting in the way today! lol

---------- Post added at 11:30 AM ---------- Previous post was at 11:04 AM ----------

Work be damned! Just flashed.

HD video, Netflix, and video recorder all appear to work, although I got burned on that once before. So we'll see if it continues to work after a few minutes

Only oddity I see is the preview in video camera mode is stretched weird, but the video records normally...
[HTC Rezound] TheBr0ken:
Getting this on an AOKP 4.2 build. Any ideas?

Export includes file: development/tools/emulator/system/gps/Android.mk -- /home/thebr0ken/android/aokp/out/target/product/vigor/obj/SHARED_LIBRARIES/gps.goldfish_intermediates/export_includes

make: *** No rule to make target `/home/thebr0ken/android/aokp/out/target/product/vigor/obj/SHARED_LIBRARIES/librpc_intermediates/export_includes', needed by `/home/thebr0ken/android/aokp/out/target/product/vigor/obj/SHARED_LIBRARIES/gps.vigor_intermediates/import_includes'. Stop.

make: *** Waiting for unfinished jobs...

If I rebrunch it continues without the error. Since it looks like its for the emulator I'm not sure I care.

edit:Nope, got the error again farther down the line
[HTC Rezound] Snuzzo:
What device tree you building off of? I'm assuming Chad's jellybean tree?
[HTC Rezound] TheBr0ken:
using his cm-10.1 tree
[HTC Rezound] Snuzzo:
Try resetting back to this commit

https://github.com/Chad0989/device_htc_vigor/commit/37259b3af9fab9707a91ce51511600691d9f7745

Then cherry-pick these ones back in

https://github.com/Chad0989/device_htc_vigor/commit/ced6427c969e81ad8a14f0358ec35890f8a60399

https://github.com/Chad0989/device_htc_vigor/commit/57e9eedb3df0e045035f1e6990c9ee0608d895ac

https://github.com/Chad0989/device_htc_vigor/commit/6ea5cdaf9494525a3b8d970e6940e8366b3a34ad

See if that works out.
[HTC Rezound] TheBr0ken:
Will give it a shot

---------- Post added at 12:32 PM ---------- Previous post was at 12:08 PM ----------

Still no dice

I synced this morning and it looks as if those cherry-picks were all ready in place. I did revert the one you mentioned about Suppress EMMC wipe. Maybe somethings not right with my default.xml and its not transferring everything correctly, but you'd think it would either grab it or not. Dont think thats the issue as everything looks right to me. Im just going to clone the trees separately and try it again
[HTC Rezound] TheBr0ken:
Cloning didn't work either. My guess is that my ambitious nature got the best of me when I was removing extra devices when I created my default.xml. Maybe I removed some common files. I updated my manifest with everything. lets see if she'll build when its done syncing.

Just out of curiosity does anybody know why we are using frameworks_av from Evervolv and it also looks like we are using a forked copy of CM's frameworks_native, but I dont see any changes.

I'm just trying to get lernt.
[HTC Rezound] dlumberg:
Any ideas how to get around the display-legacy errors from the latest commits?
[HTC Rezound] shrike1978:
Quick and dirty lesson. I'm typing this as I'm diagnosing this

I'm getting this error:

It looks like it's more of the same thing we were getting with qcom/media where CM is adding generic support for msm8660 and it's conflicting with our device specific support. So, I run this:

cd hardware/qcom/display
git log

That changes to the affected directory and shows a commit log for it. (press "q" to exit the log) In that, I see one commit that stands out:

So, I revert that:

git revert cbdefbc4de03307cccc7f133db8c917e87189f1f

Press CTRL+X, then "y". After that, I go back to my repo root, and try to build again, and it appears to be working.

Those are the basic troubleshooting steps to revert a troublesome commit. Other problems might get more involved, but now that we're building, you can usually make a basic build work just through reverting a problematic commit.
[HTC Rezound] chad0989:
This is easier:

https://github.com/Chad0989/device_htc_vigor/commit/1638487cb106ba0e3f8638dc14cf795a44c5a61f
[HTC Rezound] chad0989:
https://github.com/Chad0989/device_htc_vigor/commit/19cb0380e32641a239c674e84c35422e2873264a
[HTC Rezound] wildstang83:
Got it my latest build. Works pretty good :)
[HTC Rezound] tiny4579:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Hey. That's exactly what I ended up doing for the inc a week or so ago. Which version did you pull yours from anyway? I didn't touch the cli file as it didn't seem needed.
[HTC Rezound] chad0989:
Pulled it from CM10. I was just going to add the old hostapd source to the device tree but this was easier.
[HTC Rezound] shrike1978:
Any chance of an easy fix for this one?

build/core/base_rules.mk:130: *** hardware/qcom/media/libstagefrighthw: MODULE.TARGET.SHARED_LIBRARIES.libstagefrighthw already defined by device/htc/vigor/media/libstagefrighthw. Stop.
[HTC Rezound] mjones73:
I had to revert it last night, course you're probably asking for a commit to bypass it. :)
[HTC Rezound] TheBr0ken:
Not 100% sure this will work, and cant test right now.

Following the same pattern that Chad has implemented for the other device specific files like gps, display-legacy where he inserted these lines in BoardConfig.mk:

# Display
TARGET_QCOM_DISPLAY_VARIANT := legacy

# GPS
BOARD_USES_OLD_QC_GPS := true

Couldn't we just add:

# Media
TARGET_QCOM_MEDIA_VARIANT := legacy

in there too?

then add

ifeq ($(BOARD_USES_QCOM_HARDWARE),true)
ifeq ($(TARGET_QCOM_MEDIA_VARIANT),legacy)

in /device/htc/vigor/media/Android.mk

in place of line 2:

ifneq ($(filter msm8974 msm8960 msm8660 msm7x27a msm7x30,$(TARGET_BOARD_PLATFORM)),)

and line 7:

ifneq ($(filter msm8974 msm8960 msm8660 msm7x30,$(TARGET_BOARD_PLATFORM)),)

those lines are the ones I'm assuming are causing the issues because they reference multiple boards, the same boards CM is referencing in hardware/qcom/media. Couldn't we just be stingy here too and just reference our board with TARGET_QCOM_MEDIA_VARIANT := legacy?

Or do we have to put the variant lines in each of /device/htc/vigor/media subdir-makefiles?

Just thinking out loud, I'll give it a go when I get a chance and see what if anything sticks. Only thing that I wonder, even if I get these files to build. What stops the others from building?
[HTC Rezound] chad0989:
That won't get the stuff in hardare/qcom/media to not try to build, which is the issue.
[HTC Rezound] TheBr0ken:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

That's what I was afraid of. So is it that we want parts of media from cm to build and the rest from your device specific files? Or just the device specific files and that's it? Cause couldn't you just make your manifest skip bringing media in?
[HTC Rezound] jtwebfusion:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Does anyone know if enabling "disable HD overlays" in dev options toggles a flag in the build.prop file? I'm not near a computer to diff the file.
[HTC Rezound] TheBr0ken:
It toggles

debug.sf.hw=1

1= enabled

0= disabled