yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] kkozma:
Yup. Turns out the mount points for the sdcard are different. When I pushed my latest build to the phone it went to oblivian apparently.

Reflashed this morning and my sound is now working.

FYI: swipe style typing isn't working.
[HTC Rezound] TheBr0ken:
Are you building gcc-4.6 or gcc-4.7?

Just to see if it has something to do with the edit needed to be done to LatinIME to build with gcc-4.6 (shouldn't, but who knows), you can test swype style typing with the LatinIME.apk from my gs3 cm10.2 build since it works there

https://www.dropbox.com/s/ozowcb6nyczwa5o/cm102LatinIME.apk

If you have root or Titanium Backup issues let me know. Its an easy fix
[HTC Rezound] kkozma:
Ok weird. I restored all my apps, and now gesture typing is working.

I think the GPS may not be working though. Not 100% sure on that. I'll download a gps test app from the market and see what happens.
[HTC Rezound] TheBr0ken:
yeah, bad or no gapps have been attributing to a lot of odd things too. loss of data, quick tiles not functioning properly, incoming calls going directly to VM. Odd, Odd things.

Make sure your using the latest 4.3 gapps so you don't have issues with it restoring after a dirty flash

http://goo.im/gapps/gapps-jb-20130813-signed.zip
[HTC Rezound] Neo:
Now make I'm going to make it ION :D since that has no working camera anyway
[HTC Rezound] kkozma:
Does media/music playback fwork for you guys? Pandora doesn't work and I can't play my local mp3's. Just trying to figure out if it's just me because my build is still rockin the team-hydra frameworks av and native or if it's something we need to look in to.

In the meantime, I have a build running now with the opensemc frameworks and the team hydra camera fix merged in... Will report back once it's done.
[HTC Rezound] Flyhalf205:
Make sure lpa.decode in your default.prop is set to false.

EDIT: Pandora working fine here. Make sure you pull the latest msm8660 and vigor repo from my github.
[HTC Rezound] kkozma:
I tried to set that in my default.prop but it didn't stick. New build should be done here in the next 20 or so minutes and I did a fresh repo sync so it shoud have all the latest and greatest from your github.

FYI: GPS is working fine now. Not sure what was up before.

Edit: If this build works for the camera, can someone tell me how to push all the code edits to my github? I've tried and failed miserably before. lol
[HTC Rezound] Flyhalf205:
GPS still isn't working here... What special things did you do for camera?

Yeah. I can show you how to if camera works. Pretty easy.
[HTC Rezound] kkozma:
It took a good long time, but I was able to get a GPS fix as soon as I went outside. Make sure all the location services are turned on.

For the camera, I forked frameworks_av and native from OpenSEMC and merged in https://github.com/Team-Hydra/android_frameworks_av/commit/1969f30627005a2303751294b3b805ea9ef9cb7a

It's still building, so I have no idea if it's going to work yet or not.
[HTC Rezound] Flyhalf205:
None of my camera hacks have worked. Good luck to you. Hoping yours works.

Just noticed.... The current setup...camera.default.so is not being built in system/lib/hw/camera.default.so

[MENTION=2658396]kkozma[/MENTION] We can make a hack for cm10.2...Take the camera.default.so from a cm-10.1 rom and place it it the hw folder. fix permission. reboot and IT WORKS!! haha
[HTC Rezound] kkozma:
Well, something broke something really bad.

It boots but I get stuck in an endless fc cycle of android.phone and adb doesn't work. So no freakin' clue.

Actually had to battery pull to get into recovery. *sigh*
[HTC Rezound] TheBr0ken:
gapps??

I had that issue once and it was because somehow my gapps zip got corrupt, not sure how. Downloaded a new zip and it worked. not saying this is your issue, but just an idea

---------- Post added at 12:55 PM ---------- Previous post was at 12:16 PM ----------

Nice!
[HTC Rezound] kkozma:
[MENTION=3668085]TheBr0ken[/MENTION] No gapps at all. It was a fresh build on a fresh wipe.

[MENTION=3082717]Flyhalf205[/MENTION] on the camera. NICE! lol
[HTC Rezound] Flyhalf205:
It's a hack just to get it working. MUST be removed soon. But snapchat and instagram working fine. Camera and focal makes phone freak out. I think I have an idea why it's not working from source. Will test tonight.
[HTC Rezound] kkozma:
I didn't use any gapps... I can always try again and see what happens with new gapps.

But sounds like it's all wasted effort since we have a camera hack that works good enough for me! Awesome job Fly!

So for me then I think that's pretty much it, isn't it?
[HTC Rezound] TheBr0ken:
Flashing gapps is a must. Weird crap happens when you don't
[HTC Rezound] kkozma:
Ok, here's the deal.

I just rebuilt with the team-hydra frameworks_av and native. Build was running when fly posted the hack for the camera and when it was done I didn't want to mess with starting it up again. SO. Based on some stuff I saw in the pyramid forums, all I did was rename vendor-camera.default.so to camera.default.so. Rebooted. WORKS. FFC works too except it's upside down (LOL). That being said, it did crash on me once and then said it couldn't connect to focal, but that was before I flashed my gapps. Just flashed gapps and focal has only crashed when I tried to take video...

So I think the key is that legacy qcom camera stuff from team hydra because it seems focal works fine, although for all the hype, I'm a bit disappointed witht the picture quality.

Question: Where does the camera.8660.so come from? I don't see it being prebuilt anywhere, so where ever it comes from, maybe we can change it to camera.default.so?
[HTC Rezound] Flyhalf205:
Basically the same thing I discovered a few post back....The real camera.default.so isn't being built. That camera requires that one. vendor-camera is for the camera wrapper. But camera.default.so is not being built. We need to figure out why it isn't
[HTC Rezound] kkozma:
Well, I just rebuilt with your hack. Camera seems to work just fine. Even was able to take video without a crash.

Edit: Just reverted your camera hack and cracked off another build with a quick change. It DID build a camera.default.so

Change the camera wrapper to camera.default in device/htc/msm8660-common/msm8660.mk

Flashing now to test.

---------- Post added at 04:44 PM ---------- Previous post was at 04:22 PM ----------

It did indeed build a camera.default.so but it was like half the size as the old one and it didn't work. :(
[HTC Rezound] TheBr0ken:
[MENTION=3082717]Flyhalf205[/MENTION], its not building camera wrapper at all, because of this

https://github.com/Flyhalf205/android_device_htc_msm8660-common/blob/cm-10.2/msm8660.mk#L51

change it to:

# Camera wrapper
PRODUCT_PACKAGES += \
camera.msm8660
[HTC Rezound] kkozma:
I did that, and it did in fact build it, but it is half the size of the one from the hack (9.7kb vs 16.Xkb) and it doesn't work. There's probably something else we're missing...
[HTC Rezound] Flyhalf205:
https://github.com/Flyhalf205/andro...mon/blob/cm-10.2/camerawrapper/Android.mk#L13

LOCAL_MODULE := camera.$(TARGET_BOARD_PLATFORM)
[HTC Rezound] TheBr0ken:
https://github.com/Flyhalf205/andro...-common/blob/cm-10.2/BoardConfigCommon.mk#L26

# Platform
TARGET_BOARD_PLATFORM := msm8660
[HTC Rezound] Flyhalf205:
[MENTION=3668085]TheBr0ken[/MENTION] I'm sorry for questioning you. I just realized that I did not have msm in front of the 8660. Will fix it now
[HTC Rezound] TheBr0ken:
No need to apologize, we're all good.
[HTC Rezound] Neo:
SO do we need to pull av and native from group SEMC or no?
[HTC Rezound] Flyhalf205:
Probably not. I got camera working with everything coming from CM. Hopefully tonight we can get everything straightened out. Just need that cherry-pick I linked to you on gtalk
[HTC Rezound] Neo:
Did that and added the trigger outlined in the commit to my board
[HTC Rezound] TheBr0ken:
well, here's the thing. We need commits from two different frameworks_av.

we need to define:

TARGET_QCOM_MEDIA_VARIANT:= legacy

and use OpenSEMC for:

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

and Team-Hydra for:

https://github.com/Team-Hydra/android_frameworks_av/commit/1969f30627005a2303751294b3b805ea9ef9cb7a

You may just be able to cherry-pick them, but I'm not 100% sure if there are later commits that may also go along with these.

well, since [MENTION=3082717]Flyhalf205[/MENTION] got camera working with cm's frameworks_av, then scratch the team-hydra one, But the audio one from OpenSEMC we may still need or it will include the wrong files, not sure if there are audio issues now

EDIT: Use Evervlov frameworks_av and native. They have the camera and legacy flags we need. No picks needed, but we still need to make sure we define our media variant
[HTC Rezound] kkozma:
FWIW, I think the frameworks from Team Hydra are the way to go and it's probably only a matter of time before they implement those legacy items, even though from what I can tell, we don't need them.

With the camera working now, the only thing I have left that's not right is that com.android.phone FC's after a reboot. Only one time, but it's still annoying.
[HTC Rezound] TheBr0ken:
try fixing permissions in recovery and see if that helps. did it do this before or after your apps restore?
[HTC Rezound] kkozma:
Before, after, doesn't matter.

Does it without gapps, with gapps, no user apps, and full user apps. :(

Also FYI: Camera crashed on me again when I tried to take a picture. Too bad too, looked like it was going to be a good one. Hopefully it saved it before it crapped out.
[HTC Rezound] kkozma:
Evervolv frameworks_av doesn't like something we're using...
[HTC Rezound] TheBr0ken:
It's because OpenSEMC media-legacy is missing this.

https://github.com/Evervolv/android...mmit/e9a9fd2c5c66fb39bbf4ee0e96457c8121a1db0a
[HTC Rezound] Neo:
Does that error come up before or after cross compile?
[HTC Rezound] TheBr0ken:
My .02¢, if you build with the evervolv frameworks_av and the commits for media-legacy and there is zero noticeable difference than using cm frameworks_av with letting it pull the wrong include files then I say ditch evervolv frameworks and stick with cm, especially since Flyhalf205 plans to try and merge the camera fix in av to the camera wrapper.
[HTC Rezound] Flyhalf205:
[MENTION=2658396]kkozma[/MENTION] [MENTION=3668085]TheBr0ken[/MENTION] [MENTION=4203241]IAmTheOneTheyCallNeo[/MENTION]

I think 4.3 is ready to be released. Still working on getting cherry-pick https://github.com/Team-Hydra/android_frameworks_av/commit/1969f30627005a2303751294b3b805ea9ef9cb7a into the camera wrapper. But that is all we need left.

I'll get a thread ready. Camera is working awesome on my latest build.
[HTC Rezound] kkozma:
I've got a build running right now with the evervolv frameworks with the missing files added to the opensemc media-legacy. We'll see if that fixes anything with the camera and video recording not working.

Also, I've noticed the only picture resolution I can make stick in focal is 1280x720...
[HTC Rezound] Neo:
New sync, anyone get this error?

frameworks/base/media/jni/android_media_MediaPlayer.cpp:896:13: error: 'class android::MediaPlayer' has no member named 'suspend'
if (mp->suspend() != OK) {
[HTC Rezound] kkozma:
Don't know yet! I don't think mine has gotten that far yet. I'll let you know.

*Edit: Yes. :( Seeing what I can find now. To narrow this down. Are you building straight CM or something else?
[HTC Rezound] TheBr0ken:
cherry-pick this:

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

if there are no issues with using CM's av and cherry-picking in the camera stuff, may just have to stick with that
[HTC Rezound] kkozma:
I KNEW I had seen that before! Thanks!
[HTC Rezound] TheBr0ken:
AOKP jb-mr2 (4.3) is syncing now. Lets see whats broke there....
[HTC Rezound] kkozma:
Ok, just like the issue I had with OpenSEMC's frameworks, same problem with Evervolv.

Endless cycle of FC's of phone, and system ui.
[HTC Rezound] Neo:
Same here with using Evervolv :D

Confirmed we shouldn't us it
[HTC Rezound] kkozma:
I don't want to scare anyone here, but something VERY odd just happened to my phone.. It was plugged in to the USB port of my linux machine. It locked up, and then nothing. Then it rebooted, and I got the very distinct smell of circuitry melting. We all know what it smells like.

Not really sure what happened. I pulled the battery and it did start up, but it still stinks. Something very odd is going on.

*Edit* now my camera doesn't work.

*Double Edit* Just flashed another version of my latest. I cherry picked the legacy camera stuff and media legacy stuff from evervolv into the CM framewors_av. Builds fine and my camera is now working again... AND!!! Video recording works with Focal. :D That being said. My phone still stinks.. I don't know what happened, but obviously SOMETHING let go inside it. Only time will tell what it was.
[HTC Rezound] Neo:
Mind pushing and sharing your av for us? :D
[HTC Rezound] kkozma:
If I knew how I would... You can hit me on gtalk and walk me through it if you want. Same as my username here.
[HTC Rezound] Flyhalf205:
[MENTION=2658396]kkozma[/MENTION] How clear is the video from focal? I can record and save fine on my builds. Quality isn't great at all.
[HTC Rezound] kkozma:
Well, I guess I spoke too soon. It definitely recorded one video, but now it won't again. Hmmm

Anyways, I did manage to figure out how to push that frameworks if anyone wants it.

https://github.com/vwmofo/android_frameworks_av
[HTC Rezound] kkozma:
So, I think I've got to the bottom of one of the mysteries of random reboots. I don't think they're that random.

Mine will reboot every single time I turn wifi on or off. I saw some stuff for team-hydra at the kernel level that talked about some reboots with the wifi module, but then they reverted it right away because it wouldn't boot.

Anyone with some kernel experience want to look in to that?
[HTC Rezound] Neo:
I just turned mine on and off several times on my 4.3 build just fine. I then did it about 10 times really fast. No problems over here.
[HTC Rezound] kkozma:
Yeah, it made a sucker out of me for sure. lol I tried the same thing.

I will say though that 4G/3G data would NOT pick back up no matter what I did though after I turned it off. Had to reboot to get data back without wifi.
[HTC Rezound] Neo:
I have the bad habit of flying down to the very bottom of about phone and multi clicking on Selinux by accident instead of build number and it'll put you on full lockup. Only a battery pull fixes it then
[HTC Rezound] mjh68:
I suddenly lost all data last night. Tried Airplane mode and finally just enabled Wifi since I was in a hurry. Otherwise, I hadn't had any issues and thought the build was pretty smooth.
[HTC Rezound] tmanschuette:
Did the same thing... What does that do?
[HTC Rezound] dlumberg:
SElinux = Secure Linux. It's a Linux thing where every process is run in its own sandbox as to make the system more secure as a whole. Google has enabled it in 4.3 as an added security feature to prevent malware. CM (and Google for that matter) haven't really polished it enough for primetime so it's disabled by default for now.
[HTC Rezound] Flyhalf205:
[MENTION=2658396]kkozma[/MENTION] have you tried building with team_hydra repos? I mean sync their android repo and just pull our device tree... They seem to have a good camcorder for the shooter.
[HTC Rezound] kkozma:
I can try, what all do I need to grab?

Their android

our kernel, device, msm8660 common, and vendor?

From my digging around, I think the problem with our camcorder is the new audio-caf...

FYI: Seriously awesome job on the RIL edits there. Whatever you did I think took out all of the stability issues I've had. My phone hasn't rebooted once today and it survived 4 hours at my parents house this afternoon which is a known verizon dead zone. Up until today, it would completely kill the battery trying to find a signal there.
[HTC Rezound] Flyhalf205:
Correct. :good:

and you mean instability? haha
[HTC Rezound] kkozma:
I'm going to try this: https://github.com/Team-Hydra/andro...mmit/a13f1fb879521fcbcb356dc00a2eb2343be5d49d

and part of this: https://github.com/Team-Hydra/andro...mmit/1955a94374f9b2cf02771fd68cd7b2923f5f2e7f

before I mess with all of that since it's going to take the rest of my time being awake to sync up to all their stuff.
[HTC Rezound] Flyhalf205:
I went ahead and submitted this to CM gerrit. I doubt it will get merged. But I don't see why not cause it won't effect other devices...

http://review.cyanogenmod.org/#/c/48462/
[HTC Rezound] kkozma:
No go on those kernel changes. :( Made it worse actually.

That being said, they need them because arm pie makes their camera not work at all.

Maybe we should try a build with arm pie disabled and 4.6 GCC?
[HTC Rezound] renzo.olivares:
camera libs seems to work on rezound just fine, they always do on ports, but i switch them out for stock rezound just in case
[HTC Rezound] chad0989:
Pushed a change that fixes MMS and some other radio issues
[HTC Rezound] siulmagic:
Camera hal stuff from pyramid cm10 should work, my sense3.6(witch is from the pyramid) i only had to add our chromatic_XXX.lib's/firmware files and cam would work fine, with pyramids cam libs.
[HTC Rezound] MaulingDeOso:
The currently released pmem versions work fine, albeit slowly, but we're trying to switch to ion, and existing binaries don't support it. They're still running with pmem on the Sensation. The performance loss is probably less noticeable there because the smaller screen saves a lot of work when they fall back to a brute-force copy.
[HTC Rezound] siulmagic:
I see, yea i dint realize they dont use ion, i keep forgetting 720p is a strain on our hardware. sucks there weren any more 720p s3 devices made by htc. if only we had something newer to take from, im guessing the one s wont help much? it does have a s3.
[HTC Rezound] MaulingDeOso:
The One S has an S4, so I presume you meant the One V. It was a good idea, but I just checked--no dice. It uses pmem. I guess we know why HTC neglected any Jelly Bean plans for that one. It pains me to say, but I don't think HTC intends to make the pmem->ion jump for any device. We're on our own.
[HTC Rezound] chad0989:
At least not for s3 devices. S4 devices already use it.

It boils down to the fact that HTC is lazy and doesn't do proper upgrades. They do as little as possible to make the existing code work. They only worry about the next device coming out and focus their efforts there. Existing devices are the bottom of their priority list.

What's ridiculous is that if it weren't for the proprietary camera libs, I could transition completely to ion in an hour or two. Extremely minimal work.

I have a couple other ideas though. If we can get performance where it should be, I'm more than willing to put video recording on the backburner for a bit until we get proper libs from somewhere.
[HTC Rezound] MaulingDeOso:
Looked further into the One S, and found that there is an Asian variant that has an S3, and it uses ion--the One S C2. The camera libraries aren't a drop-in replacement, though, as they seem to be a newer Qualcomm API, and I'm not sure if they'd work with our camera module, but searching through their strings reveals that they definitely have ion support compiled in.
[HTC Rezound] chad0989:
Awesome. Can you link me to a rom?

Edit: found some in the one s forum. I'll take a look when I get home later.
[HTC Rezound] siulmagic:
yes one v sorry, friken htc and there one series.
[HTC Rezound] chad0989:
Looks like it uses the v4l2 driver/HAL like the s4 devices.

The good news is is that our main camera is the same as the ville one. The bad news is that we'll likely have to write a v4l2 driver for the frontcam. That's if we can get the cam to work at all using v4l2...
[HTC Rezound] chad0989:
Got solid video playback with ION now, including HQ youtube.

I have the v4l2 drivers compiled in and the base camera stuff from one s pulled over. Now to attempt to get it to work.
[HTC Rezound] GrayBoltWolf:
You are awesome.

Let us know when you push your updates. We all are dying to try this out. :D
[HTC Rezound] Vashypooh:
Regarding encryption for the phone not working. I have found the following:

http://code.google.com/p/cyanogenmod/issues/detail?id=5678

With a potential fix being:

However, this is not working for me, (i obviously switched to using mmcblk0p35) The log shows servicemanager saying every single thing died, then the phone reboots.

Any ideas Chad? Unsure of if this is an AOSP thing or not after the post on cyans thread.
[HTC Rezound] chad0989:
So our camera doesn't have a gpio pin dedicated to powering it on and off so the kernel driver from the ville isn't completely compatible. So both camera drivers are going to need to be semi custom. This should be fun. When and if I can do it though itll be completely worth it since it'll provide a clear upgrade path and allow us to hopefully use the open source camera HAL.

As for encryption, it might be something simple. I'll have to look.
[HTC Rezound] chad0989:
Okay. Main camera is detected and can power on and off using the new V4L2 code. Now that I understand how the new unified qualcomm camera sensor module works I don't think it'll be too hard to write a v4l2 driver for the front cam.

However, I still need to work on the userspace part of it. Although the camera powers on/off etc, I'm not getting any preview. Might just be some issues with the flags set in msm8660-common. Rebuilding without them now to see how it goes.
[HTC Rezound] MaulingDeOso:
I backported the new msmfb API stuff to our tree and got it mostly working. Overlays are still very slow. I'm still not sure of the cause. Did you notice ion helping with this at all? If not, it must be a bug affecting the timing somehow.
[HTC Rezound] chad0989:
I haven't gotten a chance to play with your new tree yet, but I played with what you have up about a week ago and it was pretty slow, even with ION. I'll pull your latest at some point and try it out.

As for camera, I'm getting closer. I had to add some stuff to frameworks/av/camera to use the villec2 HAL, but it loads and finds the camera. Unfortunately still no preview, going to try a few other things. Eventually I'd like to be able to use the open source qualcomm HAL if possible. But one step at a time.

Anyone try to build 4.2 yet? Just curious if there are any major hurdles we need to overcome there to at least build and boot.

Also if someone has time, it would be great if you could try to work on updating our init scripts to work with the JB init instead of the prebuilt ICS one we're using.
[HTC Rezound] Neo:
I managed to get it to start building for about 5 seconds lol.

I initiated the repo with CM's Mr1 staging and pulled your necessary jellybean repos.

I also had to add a vigor mk and edit a few .sh files like for JB aokp.

The errors I was getting during the build process were related to "unrecognized symbols" or something like that?

I upgraded my GCC to the latest version with Linaro support and also added the Linaro 12.10 toolchain in hopes to solve the problem as googling the error indicated to possibly fix the issue. Unfortunately, That did not work. I scrapped the whole thing until CM gets their source stable.
[HTC Rezound] MaulingDeOso:
Ok, that means something is still wrong. Overlays are falling back to software, and I speculated that maybe they removed the pmem accelerated path, but I guess not. I'll have to dig into userspace for this one.

On the plus side, hardware vsync is working, which can be enabled in the msm8660 device tree. Not sure of all the benefits, but I immediately noticed that the phase beam wallpaper runs at the correct speed now. :)
[HTC Rezound] Flyhalf205:
Might be a good idea to try actually...
[HTC Rezound] kkozma:
Casual observation today concerning our camcorder issue. If you clear the gallery cache, delete thumbnails, and reboot you can record videos until the cows come home. But after you play one or view them in the gallery, that's all she wrote. Stating to think we're barking up the wrong tree trying to figure this out...

Thoughts?
[HTC Rezound] Neo:
Memory Issue? Would be funny if it was ha. That's what I said to Fly a week or so back