yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] EmericanX:
I'm making a bit of progress on the camera... at this point the service is at least starting but quickly stopping..

I/cm ( 293): ____ _ _ ____ _ _ ____ ____ ____ _ _ _ _ ____ ___

I/cm ( 295): | \_/ |__| |\ | | | | __ |___ |\ | |\/| | | | \

I/cm ( 298): |___ | | | | \| |__| |__] |___ | \| | | |__| |__/

I/cm ( 305): Welcome to Android 4.2.2 / CyanogenMod-10.1-20130319-UNOFFICIAL-dlx

I/mediaserver( 215): ServiceManager: 0x4208ced8

I/AudioFlinger( 215): Using default 3000 mSec as standby time.

E/MediaPlayerFactory( 215): Failed to open FACTORY_LIB Error : Cannot load library: load_library(linker.cpp:747): library "libdashplayer.so" not found

I/CameraService( 215): CameraService started (pid=215)

E/HAL ( 215): load: module=/system/lib/hw/camera.msm8960.so

E/HAL ( 215): Cannot load library: soinfo_relocate(linker.cpp:989): cannot locate symbol "_ZN7android21SurfaceComposerClient15getDisplayWidthEi" referenced by "camera.msm8960.so"...

E/CameraService( 215): Could not load camera HAL module

I/AudioPolicyManagerBase( 215): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf

D/AudioHardwareALSA( 215): hw_get_module(ALSA_HARDWARE_MODULE_ID) returned err 0

I/Adreno200-EGL( 205): <eglInitialize:269>: EGL 1.4 QUALCOMM build: Nondeterministic AU_full_mako_PARTNER-ANDROID/JB-MR1-DEV_CL2961380_release_AU (CL2961380)

I/Adreno200-EGL( 205): Build Date: 12/10/12 Mon

I/Adreno200-EGL( 205): Local Branch:

I/Adreno200-EGL( 205): Remote Branch: m/partner-android/jb-mr1-dev

anyone have an idea? I've made the fault BOLD in the logcat paste... The only info I can find on this is that it would be found in libandroid_runtime.so... I think I've got all other libs loading now.
[HTC Droid DNA] chad0989:
I just pushed it to the main branch. I figure it it'll be easy enough to revert if we run into issues down the road.

A lib that contains that symbol is missing. The camera HAL is trying to load the lib and access it but it can't find it.
[HTC Droid DNA] chad0989:
I just got stuck in roaming playing with the radio. It persisted in sense also. I flashed the stock signed recovery and did a factory reset from hboot and it fixed it. Odd that it didn't fix it for you.
[HTC Droid DNA] Flyhalf205:
I'll try it again. You did factory reset with sense installed? After doing a factory reset in HBOOT it actually made my phone not detect a sim card at all

......Just factory reset HBOOT Still Roaming :(
[HTC Droid DNA] EmericanX:
Its in /frameworks/native/libs/gui/SurfaceComposerClient. By the looks of it the current camera.msm8960.so isn't playing nice. But I'll take another shot at it tomorrow. Has anyone tried to build qcom camera.msm8960 from source vs the prebuilt? I'm just curious if it would be more up to date vs what is currently prebuilt in vendor.
[HTC Droid DNA] chad0989:
Flashed a sense rom. It persisted. So I went into fastboot, flashed this recovery:

http://http://chad0989.dyndns.org/dlx_recovery_signed.img

./fastboot flash recovery dlx_recovery_signed.img

Then went back into the bootloader and chose factory reset
[HTC Droid DNA] chad0989:
I'm hoping to be able to build the HAL from source. Haven't even began to look at it though. Camera is generally pretty low on my priority list. You should give it a try.

Now that the major core features are working (adb and storage) I'm going to start looking at audio again. I think its mostly a routing issue.
[HTC Droid DNA] Flyhalf205:
I'm building as we speak.

Still no luck. Sense stock rom. stock recovery. I just don't understand. Did your recovery bootloop a few times when performing the factory reset?

and the link doesn't work you provided but I have a original one i think.
[HTC Droid DNA] azhockey:
I'm pretty sure I'm in the same boat as you. I lost radio too. Well, mostly, it became terribly unreliable and just plain unusable. Thirty seconds of service and then gone for hours. Luckily I was still under warranty so I reset my boot flag and have a new DNA on the way.
[HTC Droid DNA] crpalmer:
chad0989,

Why did you patch up to 3.4.27? I would have expected you to either not do any upstream linux versions or to do them all?

It's probably too late because you probably don't want to deal with the merge conflicts again, but I find it's much easier to work with the source in the future if you had done the merge as:

git merge --strategy=ours v3.4.10

git merge v3.4.11

...

as it preserves all the commits and then later on you can use things like git blame to see the real commit that changes were made in.

I'm a little nervous about the USB change. There are at least a couple of places where there are HTC added blocks (look for SSD_RIL) that look like they might be pretty important. Specifically, they put work on different work queues are two things that I saw.

Last and definitely least, you committed two .orig files in there. I was going to send a pull request but it's probably easier to just remove them yourself...
[HTC Droid DNA] chad0989:
I pulled many of the changes from the 3.4 evita project and they had patched up to 3.4.27 so it was easier to patch up real quick to minimize all the conflicts. I was mostly looking for a quick fix to see if that's where our issue was. I do see where there could be a problem though.

Ideally I think it would be best to just pull over and fix up for the CAF gadget drivers and leave everything else as is. What are your thoughts on that?

And thanks for the tip. Some day I hope to actually fully understand git. Its definitely a complex piece of software.
[HTC Droid DNA] chad0989:
Sorry. Here's the link:

http://chad0989.dyndns.org/dlx_recovery_signed.img

It did not loop at all. It went the restoring/update screen then restarted the phone.
[HTC Droid DNA] djh816:
Would love to try to build but with the couple of you guys having radio issues I think I will wait to make sure haha.
[HTC Droid DNA] chad0989:
Precisely why I dont post builds. Could you imagine the backlash if some random people's phones got messed up.
[HTC Droid DNA] djh816:
people do seem to ignore all disclaimers here. -_-
[HTC Droid DNA] Flyhalf205:
Thanks but still boot loops a few times and roaming persist and can't find sim. Guess back to the Rezound for me :( but at least I can still help :)

I am guessing that a few files might not have been configured correctly and with me being s-off screwed up the phone maybe.
[HTC Droid DNA] chad0989:
Ah. S-off. Possibly hosed whatever partition the factory reset image is stored on. Someone with a jtag can restore it I bet. Might cost 50 bucks but it would be worth it. Did you try taking it to Verizon? Tell them you know someone who had a similar issue and they did a "master reset" and it fixed it. My guess is they have an eeprom image they can flash. It worked on my rez.

This is why I don't s-off and preach against it of there is dev unlock. So easy to screw things up. Did you try going back s on, flashing the stock recovery then factory resetting?
[HTC Droid DNA] EmericanX:
Where are instructions for s-on? Lol. I'm new to HTC and jumped on s-off only to realize after how easy it would be to hose something while testing. I'd prefer to be s-on especially this early on..
[HTC Droid DNA] Flyhalf205:
MUST be completely stock! Do the RUU. And in fastboot... fastboot oem writesecureflag 3

I did this with my Rezound and it bricked but I was able to unbrick it with the unbrick method. But I was back to s-on though after unbrick.. I will be trying this out on my DNA tonight.

I'll be taking my DNA to Verizon and trying a new sim. But as of right now. I am in roaming and can't detect any sim card. So idk where to go. I guess jtag is the only solution unless Verizon has that eeprom flasher

Oh Chad. In master kernel branch. I have upstream to the latest version a few days ago. if you want to take a look for future upstreams.
[HTC Droid DNA] EmericanX:
Ok. So just follow the guide to restore to stock. Once stock stock fastboot oem... Do I need to relock as well?
[HTC Droid DNA] Flyhalf205:
Not sure. Here is a small guide. http://xdaforums.com/showthread.php?t=1612937 But looks like you just need stock signed HBOOT and that it.
[HTC Droid DNA] EmericanX:
Ill have to take a look at that in a little while. I should still be on the stock h-boot. Didnt really see the need in the engineering h-boot so never flashed it.
[HTC Droid DNA] crpalmer:
I am assuming that we need to update at least the android gadget to work with CM10.1. If not, then ignore everything else... The short version is that I think there isn't a great option.

I get nervous when we start taking random subsets of the code because it is very risky to miss important "unrelated" changes. I would rather update all the gadgets rather than just android. That sounds safer. But there is overlap in the gadgets and OTG and it looks like the OTG driver might be a real PITA to upgrade. If you do

git grep CONFIG_USB_OTG

either before or after your commit, there is code spread all over the USB driver related to that and I'm afraid we'd end up with a haphazard mix of HTC code and non-HTC code. So, I feel like it might be safer to update all the usb code at once. But then the risk here is that we are losing HTC changes that are important. Based on the amount of extra debugging added by HTC, I think that they had to work very hard to fix problems that they were experiencing prior to launch. This could mean that we are going to end up with lots of subtle problems 6 months from now that really suck to try to find and fix.

But, overall, it feels safer to update all the USB code rather than just part of it. Especially given that (I assume) you've proven that it appears to at least superficially work for some of the gadgets.
[HTC Droid DNA] .torrented:
really all you need to do is make sure you have the 1.33.0001 hboot then fastboot oem writesecureflag 3

sorry for the OT'ness wont happen again
[HTC Droid DNA] djh816:
I returned mine with S-On haha (early one had radio issues). As a rule of thumb you should really say to never do that unless fully stock. Don't want any user's forced into S-On for good either.
[HTC Droid DNA] drewX2:
I apologize for not following your thread, but I read someone had bricked, so I was just curious and found this post going back through. Nonetheless, I did not use HTC's implementation for wifi. It is a driver built from source. I'll look into fixing it for you if I get around to it. Not sure where you all are, but I am taking some time off since there are others working on CM10.1
[HTC Droid DNA] Flyhalf205:
No one is bricked "yet". My radio partition is screwed i believe so.
[HTC Droid DNA] djh816:
Also, people need to stop with these "donations means you need to work on it" claims. Don't donate the money if you expect anything back for it. Donate because you like the developers work and want to encourage it.
[HTC Droid DNA] 123421342:
I really think that all the cm projects should be integrated especially since there has been a lot of different progress between them.
[HTC Droid DNA] djh816:
They are. There are different gits for different people (working on their own things) but when a fix is make it generally gets put into the others.
[HTC Droid DNA] 123421342:
They are in chads but drews is not and he has a more working version. I don't think it makes sense to keep these two separate.
[HTC Droid DNA] Stoney 666:
So should all sense devs work together? Should all miui devs work together? How about kernel devs, should all of them work together? Just let them do what they do... Don't worry about how they work on it or who they work with... The op says [DEV] on the title, so the invite to devs is there to put in their $0.02... It don't say [user nonsense]....

Sent from my HTC6435LVW using Xparent Cyan Tapatalk 2
[HTC Droid DNA] orb3000:
On topic

Ok all, please lets keep on topic and with respect
[HTC Droid DNA] 123421342:
I can see your point but it does not apply here. CM is uncharted territory for this phone while sense roms have a solid foundation. It makes sense for people to consolidate until there is a solid foundation.
[HTC Droid DNA] EmericanX:
Why someone is or isnt working with another really isnt a discussion thats worth having here. The source has been made available via github@cm10dna for others to pull and work on towards a common goal. If someone wants to pitch in there is a means of doing so while working on the same page as others... This thread was created for a forum to communicate about the project. Lets try to keep it on track and not get stuck on why someone may or may not be working with another.

@flyhalf.. im gonna attempt s-on tonight and continue from there... how did building camera.msm8960 from source go the other night?
[HTC Droid DNA] 123421342:
What I'm saying is drew s source is not available for 10.1 and I think that is counterproductive to our goal when we basically have two different trees. I'm not saying people should not branch off. I'm saying not building and contributing to one tree is not productive.
[HTC Droid DNA] Flyhalf205:
I found no change. I would still like you to build it in case you figure something out also. Tonight ill be rebuilding my build box so not much time to test.
[HTC Droid DNA] munchy_cool:
with no offense but can we please keep it on topic, a mod has already warned and we do not want the thread to be shut down or a dev leaving because of constant off topic, maybe the devs are subscribed to he thread and every reply sends a notification email and they expect some progress only to find off topic discussion going on.

Thanks.
[HTC Droid DNA] crpalmer:
Chad, what exactly did you do when you bulk updated the USB drivers? What repo is it from and how did you do the bulk update?
[HTC Droid DNA] chad0989:
https://github.com/Flemmard/htc8960-3.4/commit/5ff512e7f3a4f81ec411e45a723e430ad55ce95b

It already was a bulk update. I just pulled the commit as a patch and fixed it up to build.

I'll probably just revert back to the HTC implementation for now. Like I said, both seemed to work fine, at least for adb and mtp. Not sure if we'll need to change anything for usb tethering or otg down the road though.
[HTC Droid DNA] crpalmer:
Okay, that makes sense. The code wasn't matching up with the current CAF and I was trying to figure out what I was actually looking at.

If you didn't end up needing to do the update for adb (I thought you had needed to?), I would vote to revert that and the v3.4.27 for now. I'll even volunteer to do the linux updating if you want to redo that in the future if we want (I would definitely want to once everything is stable).
[HTC Droid DNA] EmericanX:
and @flyhalf.. Thanks! I was already running the proper hboot so a simple fastboot command and I'm back to s-on and still on Sense 5"IE: my DD while kinks with this are being worked out"

BTW @Flyhalf.. when you say no change what did logcat say? I'm doing another build now which should be building camera.msm8960 from source.. but I never seem to get it right the first time so we'll see. lol
[HTC Droid DNA] Flyhalf205:
Honestly I couldn't tell you. That was a while a go. I am syncing my git back up after redoing my build box. But make sure in vendor you don't copy the prebuilt camera.msm8960. I've been debating on how I want to destroy my DNA after the whole sim card issue.
[HTC Droid DNA] myfishbear:
you should ask the dev Hashcode cuz he did some crazy stuff to get data workin on the razr/d4 cm official builds. i know hes a moto dev but he may be able to give u a hint...https://twitter.com/Hashcode0f
[HTC Droid DNA] EmericanX:
Lol...

E/mm-camera( 212): mm_camera_query: open '/dev/msm_camera/video_msm' failed. err='No such file or directory'

this is where we are with source build camera.msm8960.so

btw.. who borked data?? lol. I'm stuck in roaming now. I haven't gone back to a sense build yet to see if it makes a difference

---------- Post added at 11:03 PM ---------- Previous post was at 11:02 PM ----------

Data was actually working.. something since my last sync didn't play well though.
[HTC Droid DNA] Flyhalf205:
Welcome to my world....

Does /dev/msm_camera/video_msm even exist?
[HTC Droid DNA] EmericanX:
nope... just config0
[HTC Droid DNA] chad0989:
Its one of my last couple commits that borked data. I have to figure out and revert it. You'll have to flash the stock signed recovery and factory reset from hboot to get it back.
[HTC Droid DNA] EmericanX:
Already done. I s-on'd before I flashed the latest. I had to flash the stock recovery & boot.img.. once I did that a factory reset did indeed get me back up and running.

BTW: @Flyhalf.. I hadn't seen you mention you flashed the stock boot.img as well.. so it something you could try to see if that helps you out. Actually my device wouldn't even boot after the first bootloop. hung at the animation.
[HTC Droid DNA] chad0989:
Fixed WiFi. It was just missing the calibration files, I thought I had them in the tree the whole time but apparently I didn't.

Also reverted the usb stuff and the commit that was causing the roaming issue.

Edit: Now I rebuilt and it stopped working. Odd.

Edit2: Nevermind, it was just a permissions thing. Fixed again.
[HTC Droid DNA] Flyhalf205:
Congrats. I've added the boot animation commit. Do you know why it's not copying or if it is copying it's getting over written by the 480 size.
[HTC Droid DNA] chad0989:
I think the size has to be specified differently. I'm going to try something and if it works I'll push it tomorrow.
[HTC Droid DNA] drewX2:
Keep up the work. I'm not sure where you're at in the build, but if there is something you need help on, let me know.

Did you get video working completely? I used CAF files, but after working on the Oppo Find 5, I found that their kernel source is nearly identical to CAF source, which would make it a cleaner build. Also, it is a 1080p device. Might be worthwhile in looking at the kernel source. I have it on my github @ https://github.com/drewx2/Find5-Kernel-Source
[HTC Droid DNA] chad0989:
Updated list of what is working and good places to start with things that aren't.

Currently working:

Display

Data (3g/4g)

WiFi

adb

MTP

Sensors (compass, gyro etc)

Vibration

LEDs

Not working:

Audio (I think its a routing issue but haven't had more then a couple minutes a day the last week). This is the biggest hurdle right now.

Bluetooth - Need to get bluedroid to load the firmware and it should work.

GPS - I think this can be fixed pretty easily using the updated CAF HAL

Camera - lowest on my list so I haven't even thought about looking at it but one can maybe use the 8960 or mako HAL as a base. There's most likely some vendor libs we're missing too.

If you'd like to help out pick something and post that you're working on it and your current progress.
[HTC Droid DNA] 123421342:
Drewx2 is making good progress on audio in his CM10 git. He wrote/found a bunch of code to get libcsd-client working since that is apparently required for this phone.
[HTC Droid DNA] chad0989:
The lib already loads and works with 10.1.
[HTC Droid DNA] Flyhalf205:
I'll try to work on bluetooth if I can get CM-10.1 to fully boot. I'm having more phone issues.
[HTC Droid DNA] chad0989:
You ever get the roaming issue sorted out?

What's the booting issue?
[HTC Droid DNA] drewX2:
Shouldn't be too hard to get it working in CM10.1. Just modification of headers and a couple of files.
[HTC Droid DNA] Flyhalf205:
Got the booting issue solved. Roaming issue not sorted out yet. I am probably going to look into jtag. But my upgrade is in 4-5 months. My Rezound still works great. So idk yet. lol Oh and the phone can't detect a sim card
[HTC Droid DNA] EmericanX:
I think to send to them for jtag repair is only like $50.. imo well worth it! If you decide to upgrade after the 4-5 month period you could sell the dna and easily recoupe the repair cost.
[HTC Droid DNA] Flyhalf205:
I saw some htc-3.4 and htc-3.4-caf branches at

https://github.com/htc-msm8960/android_device_htc_msm8960-common

and

https://github.com/htc-msm8960/android_kernel_htc_msm8960

Not sure if it will help us out. Has a few different configs, include files than the standard msm8960 branches.

EDIT: OMG REZOUND PROBLEMS NOW :(
[HTC Droid DNA] drewX2:
I spoke with those devs early on in development, they were the ones who told me that support for our phone wasn't in their plans as it was too different from their own.

Most likely, these branches are similar to what we have been doing with merging changes to their own kernel. (e.g. how I merge changes from CAF back to the original DNA kernel source).

I have 3 separate CAF builds atm (unmodified, one is 4.1 and the others are 4.2 based). They actually build complete for me. I can upload to my github if you think that will help you all.
[HTC Droid DNA] chad0989:
I have audio 'essentially' working, in that it initializes and wants to work, but there is a routing issue that is causing it to use the wrong output. Right now I'm getting:

<6>[ 79.087074] c0 519 [AUD] snd_soc_core: soc_dpcm_be_dai_startup:open BE Slimbus Playback
<6>[ 79.087105] c0 519 [AUD] snd_soc_core: soc_pcm_open: pcm open Slimbus Playback

Whereas it should be opening and using MI2S Playback (as our ext speaker uses MI2S). Just need to find where the hangup is.

I might hack it for now to make Slimbus -> MI2S just to see if I get output, but we need to sort out where the core issue is.

Edit: I believe the earpiece speaker uses Slimbus, and I'm not getting output from that either. But that could be attributed to it not using the right input device also.
[HTC Droid DNA] chad0989:
It can't hurt. The more everyone has to browse through at the better off we all are. Plus it would be pretty awesome for everyone to work on a pure CAF build at some point.
[HTC Droid DNA] drewX2:
I'll start syncing them.

The strangest thing happened just now for me...

While building for the Oppo Find 5. I accidently copied over the DNA kernel AND Modules. Everything worked except my touchscreen wouldnt respond to input (but it was working); it also booted to OS. Not sure why it worked so well... I wonder if it would work the other way around.
[HTC Droid DNA] idkwhothatis123:
I'm going to be That guy. Audio from the vol rockers work?
[HTC Droid DNA] chad0989:
I think I may have a good idea as to what's going on with the audio routing. I'm probably going to have to fork the mako HAL and do some modifications though. Hopefully what I'm thinking will work.
[HTC Droid DNA] chad0989:
And I've got audio :D

It needs some work still but I get output from adjusting the volume.
[HTC Droid DNA] 123421342:
Awesome job keep it up! What did you do to get it working?
[HTC Droid DNA] chad0989:
It wasn't being correctly detected as a fusion3 device and so some parameters weren't being set. This also caused the incorrect correct configuration file (routing info) to be used. Even then the config we actually use is modified from that (we use Fusion3_DMIC).

There are still some issues because our config has some alternative use cases that I believe are used as the primary outputs in sense but aren't found in the AOSP HAL. I need to either add these cases and have them used in various scenarios, or modify the config to route things properly with the existing cases. The tricky part is going to be sorting through all the routing info and find what is actually used for what and when.
[HTC Droid DNA] drewX2:
Before I pass out...one last thing... I just double checked and purposely flashed my HTC DNA kernel to my Oppo Find 5 again. EVERYTHING works. Calls, sounds, wifi, everything.... even my camera!

I wonder if it works in reverse...

Who would of thought that would work...A little typo on my script and I find something new :)
[HTC Droid DNA] Imacellist:
So there is working audio on cm10.1? Are you going to create a thread for builds since you aren't posting them here?
[HTC Droid DNA] idkwhothatis123:
Iiiiiiiinteresting. So I could flash an oppo find 5 build, then the DNA cm kernel, and it may work. Hmm. If only I wasn't out.