yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Neo:
Oh? So ringtones, ui tones, and alarms are now working?

Fly's build commit is required in order to flash the rom if you're building it. Otherwise your build will not flash with anything but the recovery.img that gets built with the rom.

Are you saying that using evervolv's legacy repos means that we don't need the libhardware and audio-caf commits that are required to build the rom for the Rezound right now?

I have not tested dead battery charging whole off but I will today. Gonna be difficult to do as battery life on cm-11.0 is really good. I had maybe 2% drain overnight unplugged on the same build.
[HTC Rezound] kkozma:
Yes, in evervolv, the sound is 100% working. UI, ringtones, notification.

Evervolv's audio-caf is identical to cyanogenmods, once you apply the two commits we need, so there's no reason you couldn't put it in a local manifest and replaced CM's until they get off their asses and merge both commits we need.

EV libhardware has several audio differences between CM's modified for our build

EV libhardware_legacy has a few differences (related to wimax), but should build with CM.

Let me fire up a CM build with EV's stuff and I'll let you know.
[HTC Rezound] Neo:
Dev chat if you need any help building it out
[HTC Rezound] kkozma:
Dev chat??

Nevermind. I see it. :)

It won't build with any of evervolvs stuff except audio-caf... That said, sound is working. So I guess it was the audio_policy update to msm8660 or EV's audio-caf that fixed it. Building with CM's audio-caf now to test.
[HTC Rezound] Neo:
Days later you notice the chat lol I even gave you a medal a day or so ago in the chat
[HTC Rezound] kkozma:
LOL! I'm sorry! I don't get notifications for hangouts.. Even when I have them turned on.

Just rebooted with CM's audio caf. Sounds works fine there too. Also tried swapping our RIL out for CM's HTCQualcomm ril, and it's no better than ours.
[HTC Rezound] Snuzzo:
So I take it KK is a go if built with EV's audio?
[HTC Rezound] Flyhalf205:
[MENTION=2658396]kkozma[/MENTION] [MENTION=4203241]IAmTheOneTheyCallNeo[/MENTION] [MENTION=3419683]Snuzzo[/MENTION]

Audio works fine on CM audio-caf with the msm8660 policy update from cm gerrit review now since the following if committed to our git. https://github.com/vigor/android_de...mmit/845e603c5d3ac52f17df3c224e48d194cb169736

Still waiting on NEO to fix ril :) I will attempt to fix mass storage tonight.
[HTC Rezound] Snuzzo:
I just lunched a a CarbonRom 4.3.1 build using the CM11 branches. Installs great, will be running it over the course of the day.

EDIT

Ignore the above. It looks like it's not mounting system.
[HTC Rezound] Snuzzo:
For those who would like to use it in their 4.3.1 builds.

https://github.com/Snuzzo/packages_apps_LunarTools

Please update your vendor blobs as well

https://github.com/Snuzzo/vendor_htc_vigor/commit/cbc60b5ae97bcded1dc0a95a5718761ed81b7a54
[HTC Rezound] Neo:
Finally going to get a chance to look at it in a couple hours or so
[HTC Rezound] Snuzzo:
Along with updating your vigor.mk to include it into your product packages. Thanks! :)
[HTC Rezound] punkboyinsf:
I'm on pins and needles. This is likely the last Android version I will see developed for the Rezound. I'll be losing my grandfathered Verizon data at the beginning of December and move to T-Mobile. I think I am moving to the HTC Sensation. Found a couple on craigslist for under $100. Maybe some of you are Devs there too? Either way thanks to all of you guys for making this device shine long after big red and HTC stopped caring about us. I am still anxiously awaiting the first kitkat build!

Cheers!

:beer:
[HTC Rezound] mjones73:
Why would you be losing your data?
[HTC Rezound] AtomicFizzle:
Yeah, as long as you don't do anything to change your plan you can keep it, right? Unless I missed something?
[HTC Rezound] punkboyinsf:
the nonexistant thread

This is so not where this discussion belongs, but after this contract is up, I am told the only way to keep unlimited data is to buy a phone full price and then they will let it continue..

The other issue is I am on my parents account as an added line and she is overpaying for what she and my dad use, so I get the boot off that account regardless.. I am thinking T-Mobile looks like a good option, I have my eye on either a Sensation 4g or the Amaze which after looking at the specs is pretty sexy for a last gen (around the same gen as the Rez) phone. Both of them have Evervolv builds running kitkat already..

I will still keep up on Rez developers (such a great group) just like I still check in on OG DInc development, but since it won't be my daily driver anymore, my attention paid to nightlies and such will be on my next phone..

I should probably start spying on the threads and see the new group..

ANYWAY gonna stop ranting now cuz this is the dev thread, and my quick thanks and gratitude post that probably should not have gone there (but where else could I have said that to all of them at once) gets me into trouble for starting a carrier plan discussion in the dev thread..

( > - - < )

| |

:angel:
[HTC Rezound] desalesouche:
i sir...i have about the same error =

system/core/include/cutils/properties.h:69:41: error: call to '__property_get_too_small_error' declared with attribute error: property_get() called with too small of a buffer

make: *** [/home/jfk/CM11/out/target/product/d802/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/omx_vdec_msm8974.o] Error 1

can you explain me how you fixed? thank you...

edit: error from*here= http://xdaforums.com/showpost.php?p=47216196&postcount=846
[HTC Rezound] dlumberg:
Just dropping some camera driver research for ion here. I may take another look at this in a few days but I figured I'd post it here so I can find it again and so anyone else who may be feeling adventurous can find it.

Main Camera Drivers (ov8330)

3.0.13 kernel:

https://github.com/wiko-sources/cin...tek/custom/common/kernel/imgsensor/ov8830_raw

OptimusG kernel stock 3.4 (v4L2 driver)

https://github.com/ChangYeoun/OptimusG_Stock/tree/master/drivers/media/video/msm/sensors

FFC Drivers (mt9d015)

3.0.96 (Kernel Makefile tagged as pmem)

https://github.com/klothius/htc_pyramid_kernel_30/tree/master/drivers/media/video/msm/sensors

ION 3.0.89 (looks like it hasn't been updated with the rest of the source)

https://github.com/sultanxda/sultan-kernel-bruce-linaro3/tree/ion/drivers/media/video/msm/sensors
[HTC Rezound] VictoriousShooter:
In case the ion-surface flinger and pmem-camera is still an issue:
[HTC Rezound] _litz:
So far, camera is absolutely a no-go.

we can get the still camera to work, but camcorder ... nope. Nothing seems to work ... :(

(anyone got any ideas?)
[HTC Rezound] Neo:
Hello my fellow Rezounders! I'm on vacation until the 6th of January and hope to return refreshed and ready to fire up that rom factory once again. I hope you all have a safe trip if you're traveling and wish you and your families a very Merry Christmas!

Sent from my LG Optimus G Pro
[HTC Rezound] _litz:
So it appears at this point all obstacles have been overcome ... :)
[HTC Rezound] Snuzzo:
Sent over some performance and battery optimizations in a pull request for review. :) If i do anymore mods or cherry-picks, I'll send in another pull request. Time to work on a rom.
[HTC Rezound] desalesouche:
hi.i was in same situation.

and i could make camcorder work replacing only one file in system/lib/.....

it was = libstagefright_soft_h264enc.so

i took it from miuiv5 for my device....

so now videorecord are saved on sd BUT gallery show them black they can't be played...

hope it will help you... pictures are ok.they are saved on sd...

if you can get more progress that me please advise me.

ps: i also had to make some change to media-codecs and media-profile...

whish you good luck... :good:
[HTC Rezound] mjones73:
With the current hybrid memory builds it's working now.
[HTC Rezound] desalesouche:
can you point me to github about that build please? may be i can find a fix for my device?

thank you
[HTC Rezound] mjones73:
I think it's all in this post from litz - http://xdaforums.com/showpost.php?p=49134247&postcount=7
[HTC Rezound] Neo:
I will upload a newer build either this evening or tomorrow. Its already built and works great. Just a matter of me uploading and changing the OP in the thread
[HTC Rezound] Snuzzo:
[MENTION=2658396]kkozma[/MENTION]

Your BT fix may be able to be backported to CM9 and AOKP Milestone 6. Currently syncing CM9 to try it out.
[HTC Rezound] kkozma:
You think so? I don't even want to think about the **HOURS** of wasted time trying to figure it out and it was that simple. DOH!
[HTC Rezound] dtomlin:
Never wasted time of it leads to a solution. The work you guys have done for this phone blows my mind.
[HTC Rezound] desalesouche:
hi all can someone can help me with that video dirver bug?

W/Adreno200-EGLSUB( 121): <DequeueBuffer:420>: dequeue native buffer fail: Device or resource busy

E/BufferQueue( 121): [FramebufferSurface] dequeueBuffer: min undequeued buffer count (2) exceeded (dequeued=2 undequeudCount=1)

thank you.. :)
[HTC Rezound] Snuzzo:
So far, that wasnt it, and still have yet to figure it out. Someone else will want to look at it.
[HTC Rezound] codingninja62001:
Help

you fix the errors by reverting to those right
[HTC Rezound] Neo:
What are you trying to build?
[HTC Rezound] codingninja62001:
q

I'm trying to port to my lg optimus f6
[HTC Rezound] Neo:
Ok..

Are you trying to build a rom for your lg optimus f6? Or are you trying to pull a rom from a lg optimus g6 to the HTC Rezound?

In either case, what is the rom being used/built?
[HTC Rezound] codingninja62001:
No I'm just posting here because of the sa!e error I'm building for the f6
[HTC Rezound] Neo:
OK... I'll ask one last time before I move on to something else :)

What rom, are you trying to build for the f6?
[HTC Rezound] codingninja62001:
Oh sorry its CyanogenMod 11
[HTC Rezound] Neo:
If you would be so kind as to post your exact build/make error here in

code form

or a paste it to pastebin and link here and I will look at it for you.
[HTC Rezound] codingninja62001:
I was using my nexus 7 to ask but here it is (and im not as much as a noob as i seem)

the 2 line in the middle throw the error

hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp:7132:73: warning: passing NULL to non-pointer argument 3 of 'bool omx_vdec::omx_cmd_queue::insert_entry(unsigned int, unsigned int, unsigned int)' [-Wconversion-null]
hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp: In member function 'int omx_vdec::alloc_map_ion_memory(OMX_U32, OMX_U32, ion_allocation_data*, ion_fd_data*, int)':
hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp:7617:17: error: 'struct ion_allocation_data' has no member named 'heap_mask'
hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp:7620:17: error: 'struct ion_allocation_data' has no member named 'heap_mask'
hardware/qcom/media/mm-video-legacy/vidc/vdec/src/omx_vdec.cpp: In member function 'OMX_ERRORTYPE omx_vdec::allocate_output_headers()':
[HTC Rezound] puhleez:
OK any takers to start looking at Lollipop? Any need to or way to backport a newer kernel? Where to look for more info?
[HTC Rezound] El Schisne:
Out of curiosity, is this still with the open-source v4l2 HAL, or did you end up going back to the old HAL as you were thinking you might a couple pages ago?
[HTC Rezound] chad0989:
Open source v4l2 HAL. Huge step forward.
[HTC Rezound] chad0989:
Still photos are working now. Color is still wrong though. Panorma works also but its never ending (the little bar doesn't detect and stop it), but if you click stop it processes it fine.

No recording yet.
[HTC Rezound] SynisterWolf:
Epicly long panoramic? Awesome. I would like to see how far it can go vs rendering. :)

Sent from my iPhone...
[HTC Rezound] chad0989:
Got recording. Now to fix color and auto focus. Then write a v4l2 driver for the ffc...
[HTC Rezound] chad0989:
AF is working now.
[HTC Rezound] GrayBoltWolf:
Since Chad is a boss and is getting things working pretty fast, I thought I would post my megathread list.

-me

- heyis4horses

-SteveG12543

-bjcoenen

These are the people I have so far. Anybody else who wants to be included in the megathread, PM me.
[HTC Rezound] chad0989:
Pushed my current ION progress to a new branch (jellybean-ion). I've been pretty busy so hopefully someone else (oso?) can help out some. Maybe someone can figure out the color issue with the main cam. Right now its a bit.... purple. Don't build front cam support (mt9d015) or you'll crash on boot. I wrote a driver and its included, but it causes a crash, I think it might be a gpio thing in the board file. I need to change the way the cams are initiated/switched between.

There is some new video tearing that popped up again that I just noticed. It wasn't there a week or two ago so I might have accidentally overlapped some memory regions again when I added another heap. I'll look into it.

Edit: You need to pull the kernel, vendor, device vigor, and device-msm8660 repos or you're gonna have a bad time.
[HTC Rezound] MaulingDeOso:
On first thought, a purple or blue image is probably a bit-packing/ordering problem; I've seen it numerous times before. The tearing might not necessarily be overlapping memory--any asynchronous access can cause it, and that's one of the main points of ION. Could just as easily be missed vsync interrupts.

If I can manage, I'll look further in the next few days. I was already investigating our main board files, as they're getting dated and may be causing some problems. For instance, newer code trees are reserving space in the EBI1 region for overlays, even when on PMEM, instead of in the MDP pool, and panel initialization definitely needs to be reworked.
[HTC Rezound] chad0989:
Any luck?

I haven't gotten a chance to look at anything more yet. I've been pretty busy.
[HTC Rezound] dmeadows013:
I be looking at the trees and 4.2 when I get done with finals this Friday

Via my Google Galaxy S3 running sweet sweet Jelly Bean
[HTC Rezound] MaulingDeOso:
I'm only just getting to it now. Are you still using bruce2728's modified qcom hardware libraries with this? I could have sworn you claimed a switch back to stock a while back, but your manifest still uses them.
[HTC Rezound] chad0989:
I switched back for the ion branch. I didn't push a new manifest for it though, just the repos. I should probably do that.

On another note. I did manage to finally update the init scripts and get rid of the prebuilt init and init.rc.
[HTC Rezound] d0ppler302:
So after reading through this thread, is there a beta ROM going to be put out soon? Sounds like its working out nicely.
[HTC Rezound] jon7701:
No, from what i know JB will only be released when chad feels it is ready, and you cant put an ETA on when he feels its ready. If you want JB now you can either build it yourself or ask for it from someone who has built it for themselves. Also please dont post questions in this thread, questions should be asked in the AOSP general discussion thread in the General section.
[HTC Rezound] chad0989:
Right now its a choice between it running like crap (laggy, slow, many games are unplayable) or it running decent (about on par with CM9) but you have a purple main cam and no front cam. Its not worth it to post builds only to get flooded with dozens of comments from people who don't read that say "This runs like crap," or "I'll come back to this when the camera isn't purple, I use my camera way too much for this." If someone really wants it, they can build it. It's currently not as good as CM9 and there aren't any real advantages of running it at this moment. Despite what others try to tell you.

If I can get the main cam to not be purple I'll probably give the go ahead on the ion branch. A not working front cam isn't a deal breaker for the majority and IMO its better to have it run decent with a non working front cam then to have it run like crap with both cams working.
[HTC Rezound] GrayBoltWolf:
So you think that your ion branch runs better than the other JB repo you have, and that is the one you will probably let us post?
[HTC Rezound] chad0989:
The ion branch runs significantly better, but it has the camera issues.
[HTC Rezound] GrayBoltWolf:
I will switch over to that then.

What is the URL to the ION repo? (anyone PM me if you know)
[HTC Rezound] SynisterWolf:
Just tell everyone its a new feature "purple haze" filter on all your pictures. take that instagram. :P
[HTC Rezound] chad0989:
Took a break from the camera stuff and got CM 10.1 booting. Looks nice, actually seems to run smoother than CM10. Nothing really works right now though because the CM team hasn't put any work into msm8660 devices yet.
[HTC Rezound] kyuubi08:
Do you expect the transition to 10.1 to be easier that from cm9 because it's still jb?
[HTC Rezound] chad0989:
No idea. We'll see. Pretty much anything that's crucial is non functioning right now (no radio, no wifi, no audio, no storage). I can probably easily fix WiFi, audio (if I use the old audio stuff for now) and storage. All I can say is lets cross our fingers that we don't have to deal with another radio fiasco and its just something minor.

But like I said, CM hasn't really done any work for our platform yet, its all about the s4 devices. So hopefully support will improve soon.

Edit: Pretty sure I know what the radio issue is. Easy fix.
[HTC Rezound] MaulingDeOso:
The purple haze definitely looks like byte-order. It probably comes out of the camera driver in either the opposite endian expected or an unimplemented packing format, because the automatic post-processing for white balance/exposure has an effect on it.
[HTC Rezound] Neo:
I built it Friday and have been testing it all weekend. I noticed the video issue you spoke of as well. It appears to me that although video and hd both work, they both contain heavy tearing for the most part. Audio from those videos is seamless however so obviously something's working properly. The Rom overall feels smoother.

Any headway as to what is causing the video issue? I know you're quite busy. So much so that you upload your progress for assistance.

Oh and also, I noticed that video recording crashes and distorts and they don't play back. There also appears to be a heavy delay on camera auto focusing.

Keep up the good work brother
[HTC Rezound] dmeadows013:
Working on 4.2. Chad what did you do to get it booting?

Via my Google Galaxy S3 running sweet sweet Jelly Bean
[HTC Rezound] SynisterWolf:
Magic. Hello....

Sent from my iPhone...
[HTC Rezound] chad0989:
A lot. I managed to fry my sim though messing with radio stuff so I'm not pushing it yet.

I may need a tester whose willing to potentially fry a sim (phone will be fine but will need a new sim and a factory reset from vzw if it fries). You must be s-on and htc dev unlocked, PM me. I'm pretty sure I fixed the issue but I can't exactly take my phone to vzw twice in one day with a fried sim. Haha.
[HTC Rezound] SynisterWolf:
different store? :D
[HTC Rezound] siulmagic:
id be willing to test, but im gsm though.
[HTC Rezound] DontPushButtons:
I've still got my vzw sim and haven't canceled service yet. I'd be happy to try something out for you once I get home. If you still need someone.

Edit: Home all weekend.
[HTC Rezound] siulmagic:
chad this might be helphull to you, its about the cm10.1 progress on the doubleshot witch is also s3 based, https://plus.google.com/116264847585753827152/posts/1YRVt3xHjBJ
[HTC Rezound] kyuubi08:
Link was taken down
[HTC Rezound] siulmagic:
works fine here. try it from the desktop
[HTC Rezound] Neo:
You may have it cached. From desktop logged into my account it appears to have been removed or deleted..I'll try again in a bit though
[HTC Rezound] GrayBoltWolf:
Me too. Dead link.
[HTC Rezound] mvmacd:
it's definitely cached if it still works. quick! hit Ctrl+S and save it as html only. then upload the .html file. :good:
[HTC Rezound] chad0989:
I caught it yesterday. It has to do with them working on cm when they never even got an official ICS release. We're lucky enough to have at least gotten ICS. Really stinks for them.
[HTC Rezound] tiny4579:
Sup dudes. I thought I'd pop in and say hi. I was wondering what happened to the old inc people and from seeing this thread there are quite a few here.

Just a bit of advice on 4.2. Evervolv has msm8660 working though I don't know how well. Also, if you check my github you can see what parts came from evervolv to get it to boot. Since I'm not a Rezound user I can't do much testing but I thought I'd pop in and give some feedback. Subscribing so I can see when someone responds.
[HTC Rezound] chad0989:
Nice to see you here. I already got CM 10.1 booting a few days ago. Runs pretty nice actually, but many major things aren't working right now. Been busy so I haven't gotten a chance to work on it and waiting on a tester to do some radio testing for me.

I didn't push anything to github yet because I manged to fry my sim working on the RIL. Want to make sure I have radio working well before I push anything.
[HTC Rezound] chad0989:
I have no idea if or when the final bugs are going to be fixed, and so I stop getting messages about posting builds... you guys can do as you please. What I do know is that I'm refusing to read any of the threads. Especially when someone can't turn off their alarm in the morning, or play their favorite game, or their child's first steps didn't record... Or when we finally get the main cam working well in the ION builds, but the FFC doesn't work and everyone gets mad because it used to work in the old builds and they just don't understand why it won't in the new ones.

I'm really not trying to be a jerk about it. just want everyone to know there are still some serious issues with it and CM9 is a much better choice if you want something that's close to a true DD.
[HTC Rezound] SynisterWolf:
Fair enough. As always. Thank you :)

Sent from my iPhone...
[HTC Rezound] Neo:
Thank you and I apologize if having requested it from you has bothered you. I do not see it as you being a jerk because I know that you feel responsible for the stability of the roms seeing as how you made it possible. I will make sure my end users know not to bother you with questions related to unresolved issues and to keep it within my threads.

Thanks again
[HTC Rezound] kyuubi08:
Take pride in your work. I know without you and the other amazing developers I would not be sending this from my own JB build.
[HTC Rezound] MaulingDeOso:
Is overlay support faster? If so, it might be worthwhile to backport the hardware libs or some changes to make CM10 faster. I noticed tile rendering is no longer used or updated in favor of overlay layers, so I imagine you either disabled that or used an older qcom display set.
[HTC Rezound] A2Aegis:
Honestly, if people get upset about these type of things, they shouldn't be here in the first place. We all (should) know what we're getting into here, and what risks are involved with what we are doing. I'm just glad, and I'm sure everyone else here shares the same sentiment, that you got us to this point.
[HTC Rezound] chad0989:
I used the older display set. Its mostly just ui enhancements / refinements that smooth things out a bit. We need to finish updating the kernel before we can use the newer qcom display.
[HTC Rezound] MaulingDeOso:
AFAIK, CM didn't pull the sync point/fence API yet, and I'm not sure if they intend to. So if you use their version it will probably still work after a few changes.
[HTC Rezound] TheBr0ken:
So I am running an ion build but my device was being a pain when I tried to install the kernel ( s-on per Chad's suggestions when messing with this) so essentially I'm running an ion tree with a pre-ion kernel. Both cameras work fine, and there is no more tearing while viewing HD video from YouTube. Recording and BT is still a bust, but its running nice regardless!