yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] crpalmer:
Sent via PM. If someone else is doing development and would like to have the logcats, let me know and I'll send you a link as well.
[HTC Droid DNA] azndan2:
Will a logcat taken after a reboot provide info for what happened prior to the reboot?
[HTC Droid DNA] pio_masaki:
No the buffer is cleared for a logcat.

Tapatalked from my HTC DNA
[HTC Droid DNA] azndan2:
So what would be the best way to help troubleshoot a freeze and then manual reboot of the phone?
[HTC Droid DNA] crpalmer:
After reboot, grab /proc/last_kmsg.
[HTC Droid DNA] crpalmer:
[MENTION=3124509]chad0989[/MENTION], have you considered pulling

arch/arm/mach-msm/qdsp6v2

from CAF? I just barely started looking at it this morning but then ran out of time.
[HTC Droid DNA] chad0989:
I haven't looked at it too much yet either.
[HTC Droid DNA] KyJelly69:
I remember someone posting about some surprising similarity between the DNA and the find 5. Will the open source project be helpful for us? http://www.xda-developers.com/android/oppo-find-5-receiving-open-source-project-love/
[HTC Droid DNA] jeremy46er:
Yeah drewx2 was the one that mentioned the similarities, I believe he had both phones.
[HTC Droid DNA] chad0989:
It won't help us in terms of what we're having issues with. They use the qcom BT that is part of the SoC which won't help us with the BT audio issues. And I still haven't even looked at camera but HTC loves to jack up the camera so our best bet is to work with the htc one guys on that.

As for BT audio, I have it partially working, I get output but it sounds compressed and like the gain is too high. The input (mic) however, is not working yet.
[HTC Droid DNA] skynet11:
The Oppo Find 5 camera uses a Sony ExmorRS sensor, so it's quite different from the one on the DNA.
[HTC Droid DNA] t1gartist:
as for camera this is the first error caused

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

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

E/HAL ( 210): Cannot load library: soinfo_link_image(linker.cpp:1673): could not load library "libmmcamera_interface2.so" needed by "camera.msm8960.so"; caused by load_library(linker.cpp:771): library "libmmcamera_interface2.so" not found

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

thats the first place to start right?
[HTC Droid DNA] volfan22:
I have a question for you chad. This might be totally out in left field but I'm curious. [MENTION=1615671]Zarboz[/MENTION] is working on porting over the Facebook rom, which is just aosp with the launcher on top of it. I realize it is 4.1 but if he got camera working on that, would that help getting the camera working on this whatsoever? Anything we could use from that?

CM10.1 Droid DNA
[HTC Droid DNA] munchy_cool:
maybe this will help

aosp on international one - http://xdaforums.com/showthread.php?t=2261664

https://github.com/nocoast
[HTC Droid DNA] jonesin:
the international has the octa so i may be mistaken but i dont think it will
[HTC Droid DNA] munchy_cool:
Well they have builds for Att and tmo one as well , also it's the s4 which is different

sent from a red beast on sense 5
[HTC Droid DNA] skynet11:
You're talking about the HTC One here, aren't you? Exynos processors (including the Octa) run on Samsung’s devices, not HTC's. Also, all versions of the HTC One run on the Snapdragon 600 as opposed to the Snapdragon S4 Pro (though the two chipsets are *almost* identical).
[HTC Droid DNA] ML417:
I keep seeing everyone making suggestions on what would help, I would like to remind you all that the most helpful devices out there are the ones with the same hardware, not necessarily software. Our phone has a processor that isn't found in a lot of other phones which is why it's been so difficult for our devs.
[HTC Droid DNA] t1gartist:
yes but the S4 in the I9505 series have damn near the same features well sense over touchwiz but damn near same software processors are identical besides the 1.9ghz speedsa over 1.5 ghz cam is diff gpu is same adreno 320
[HTC Droid DNA] beaups:
It's not the same processor. Similar, yes. But not the same.
[HTC Droid DNA] Bigandrewgold:
Just because they both have Qualcomm processors doesnt mean they have the same processor.
[HTC Droid DNA] skynet11:
The DNA has a Snapdragon S4 Pro, whereas the Galaxy S IV (i9505) has its immediate successor, the Snapdragon 600. As Bigandrewgold said, they're different ;)

---------- Post added at 04:44 AM ---------- Previous post was at 04:31 AM ----------

This couldn't be farther from the truth. First of all, the Snapdragon S4 Pro is on a whole bunch of devices: the Xperia Z, the Xperia ZL, the Nexus 4, the Optimus G, the Butterfly and the Oppo Find 5, just to name a few.

Second of all, the processor isn't necessarily the problem. After all, it was obviously no problem for the Nexus 4. It seems to me that the main hurdles lie with HTC's HAL (hardware abstraction layer), the middleware between the hardware and Android/Sense.

For example, as far as I know, the camera issue isn't related to the processor. As it stands now, the camera needs the Sense-based drivers in order to function. As I understand it, in order to replace the Sense drivers with AOSP counterparts, you basically have to rewrite the software from scratch.
[HTC Droid DNA] Phaded:
Exactly this. ^^

Now can we please stop with theories... If you know what you're doing, please help the work in progress. If not, stop cluttering a DEV thread with nonsense.

Seeing as how I have now done the same thing, I will report myself to get the thread cleaned.
[HTC Droid DNA] TheDanimal:
This. A discussion thread should be started instead.
[HTC Droid DNA] chad0989:
Moved to the CAF audio HAL in mainline CM now that its compatible. Still trying to sort out why BT audio isn't sounding right.

It also looks like the One guys are working pretty hard on the camera HAL which we should most likely be able to utilize with no (most likely) or minimal modifications.
[HTC Droid DNA] 123421342:
I have no first-hand knowledge, but the droid incredible has 95% functioning CM10.1(cant record videos). I think the everevolv team is responsible for making the device tree, so is there a way someone can look at that code for a reference or something? Obviously it will be different but hey, camera works for the most part on that device.
[HTC Droid DNA] chad0989:
Don't build with apq8064-common yet.
[HTC Droid DNA] chad0989:
Okay. I have everything sorted out with the CAF audio HAL in mainline now (excluding BT). I'll push some updates tomorrow.
[HTC Droid DNA] chad0989:
Everyone can sync and build now.
[HTC Droid DNA] chad0989:
Hmm. Apparently there's a butterfly 4.2 leak. Maybe I can pull some useful stuff from it.
[HTC Droid DNA] 123421342:
Would be useful thanks for your hard work!
[HTC Droid DNA] jonesin:
Hey torch is functional on the PAC build don't know what that might mean to development for you Chad but I saw you mentioning that it would most likely start working when camera became operational so maybe there is something to be gained
[HTC Droid DNA] chad0989:
That's because I switched it to not use the camera HAL.

https://github.com/CM10DNA/android_device_htc_dlx/commit/1a85f56527e2ccb318bb7cd0e323d9c93cd1ec3c

Haven't done anything regarding camera. I'm still scratching my head as to why BT audio doesn't work the way it should. Codeworkx appears to be working hard on camera on the One though so hopefully we'll have something soon.
[HTC Droid DNA] munchy_cool:
:)

https://plus.google.com/111398485184813224730/posts/7zpFdAFGGGQ
[HTC Droid DNA] Epic 4g:
If I didn't reach my limit with the thanks button you would have another thanks from me. So I will make it a point to thank you tomorrow my good sir.

THANKS!!!!! You made my day with that post. lol
[HTC Droid DNA] jonesin:
chad also worth mentioning IMHO is that PAC buit from your tree also allows wifi tether(from the market) to function which i was not able to duplicate in aokp or cm... wifi ap was still non functional and foxfi failed as well. I dont know that this is a focus of yours at all but i know many users appreciate the functionality(for me its necessary) if that might provide any insite into where the issue stems from/a fix then great! but figured i'd share... if i can provide anymore info lemme know
[HTC Droid DNA] chad0989:
Woohoo, working camera
[HTC Droid DNA] jonesin:
sweet lord baby jayzuz:highfive:
[HTC Droid DNA] amit_sen:
Here comes the MONEY :D
[HTC Droid DNA] munchy_cool:
both front and rear if I may ask?
[HTC Droid DNA] chad0989:
Rear works fine. Front crashes and prevents switching back. So I'm not pushing anything until I work that out.
[HTC Droid DNA] tslagle13:
You're awesome chad!!

Sent from my CM10.1 DNA
[HTC Droid DNA] volfan22:
Guys we need to get a fund together and get this guy some beer for the next few months! You are the freaking man!

CM10.1 Droid DNA
[HTC Droid DNA] munchy_cool:
want me to start a thread in General :D
[HTC Droid DNA] jonesin:
Don't forget this guy...

https://plus.google.com/111398485184...ts/7zpFdAFGGGQ
[HTC Droid DNA] afazel:
Does the working camera take advantage of HTC's ImageSense chip, or is that left out in CM?
[HTC Droid DNA] volfan22:
I'm on my phone. That won't show up for some reason. It just gives an error.

CM10.1 Droid DNA
[HTC Droid DNA] chad0989:
I bet that was it for sure. I renamed some of the init scripts when I pulled them into the tree so it built a functional boot.img. I fixed it from my phone and updated. Hopefully if everyone re syncs and rebuilds the bootimage it should be good now.
[HTC Droid DNA] EmericanX:
Lol. I over looked the /sdcard/0 issue but got back going last night. Could've just used a different phone for the time being but the DNA is my favorite of the bunch. I figured it would be something simple in ramdisk but needed to get to sleep lol... I'll make the adjustments you found and take another look tonight.

---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------

You're supposed to be out of town! Lol..
[HTC Droid DNA] Flyhalf205:
Always working even out of town lol..

But anyways. In the Jellybean branch you modified the init.target.rc but we don't have a init.dlx.usb.rc. We do have a init.usb.rc... Even if we did rename this...the init.rc calls for init.usb.rc so in the end we are good? I just confused myself typing this so I hope it makes sense. haha
[HTC Droid DNA] chad0989:
Yeah. That was an mistake but I couldnt easily revert it from my phone. After I edited the other one I clicked on the jb branch, saw your last commit and thought I had deleted the line by accident. You can just revert it if you want.
[HTC Droid DNA] t1gartist:
what cxommands are you using after make finishes compiling i tried breakfast but no go and by no means trying to be funny im just not sure where you build file is for the dna as everyone seems to have a different location for something
[HTC Droid DNA] chad0989:
. build/envsetup.sh

brunch dlx
[HTC Droid DNA] EmericanX:
Got adb. With boot animation. But "adv devices" yeilds "blahblahblah : offline" lol.. pulled a kernel log once it could get adb shell via recovery and its over and over adb service already running" or something along those lines.. anyone ever seen this?
[HTC Droid DNA] djh816:
sounds like stuck on rsa authentication (new to 4.2). could try just disabling it for now ro.adb.secure 0

More info for anyone interested: http://stackoverflow.com/questions/15225991/android-4-2-2-rsa-disabling
[HTC Droid DNA] EmericanX:
that was definitely the ticket to initial adb issues. As of right now you'll get adb during first boot but after that you'll need to wipe data for it to even register the device again. I'm headed out for the night but I pulled logcats and kernel log if anyone wants to poke around...

Logcat is ---> PasteBIN

kmsg is ---> PasteBIN

FYI: as of right now display is definitely working. It is not recovering once it times out but will stay on as long as time out is not reached. Phone calls out but there is no audio currently. LTE is also functional.
[HTC Droid DNA] crpalmer:
I spent a little time working to figure out how to get the display back on.

Since adb in cm-10.1 was annoying for testing, I started out by working with my normal Viper 1.1.3 system. I pulled chad's commit into my kernel and experienced the same problem with. The following commit makes the display turn back on when running under viper:

https://github.com/crpalmer/android_kernel_htc_dlx/commit/03a49612fe2fc3c73ff11b58c0f915960de3cb9a

but when I put it into cm-10.1, the display_on function doesn't appear to be called and it doesn't work. I haven't spent any time looking into why, but I wanted to share the commit in case someone else wants to look at the display code. It will be much more pleasant working on other issues when the screen timeout doesn't force you to reboot...
[HTC Droid DNA] chad0989:
display_on doesn't exist in the mako FB, only lcd_on/off. I noted the display issue but haven't gotten a chance to remedy it. I just got home so hopefully I'll have some time in the next couple days.
[HTC Droid DNA] drewX2:
I thought I would give some tips for you guys.

For starters, the init files are way off. Much of getting it booting right and having things work properly after you get it to the UI have to do with this. Regarding libs/binaries, it's true that many of mako libs and binaries can be used, but you need to utilize more of the DNA. For wifi/bluetooth, I am not sure using your current method will work as the DNA doesn't use qualcomm's hardware/implementation (I was unable, but you might); the DNA has a gpio conflict as seen in kernel source (board-monarudo.c) therefore HTC created a work around for it. Even if you did get it working, I don't know that bluetooth would ever work.
[HTC Droid DNA] chad0989:
It turned out it was just the storage path not being exported that was preventing it from fully booting. I actually just fixed it earlier today and pushed something an hour or two ago. I'm working on cleaning up the init scripts / permission and moving them inline with the mako so we can ditch the prebuilt init.rc. I'm probably also going to ditch msm8960-common as we don't have much in common with them other than a couple scripts and pull everything into one tree.

Wifi and bluetooth utilize the same chip (broadcom) much like on the rezound and some other HTC devices. But honestly, I haven't even taken a look at them at all though as my next focus is audio.
[HTC Droid DNA] drewX2:
I forgot to mention that about msm8960-common. I had initially written that in my post, but I was on my phone and it died on me, so had to retype it. I only use it as its inline with CM's git, but everything about it is different (which is why I was told way back by some CM/MSM8960 devs why they werent interested in working on DNA at the present time; they said it screwed up their tree)

I thought the same about wifi (I know its broadcom), here is HTC's implementation (I have not seen this for any other boards as they don't have this issue). HTC also mentions somewhere in kernel source (cant recall) that they use WCNSS as a wrapper

#if 1 /* Temp solution to turn on sleep clock, remove this after GPIO conflict is resolved */
if (system_rev >= XC) {
pm_config.direction = PM_GPIO_DIR_OUT;
pm_config.output_buffer = PM_GPIO_OUT_BUF_CMOS;
pm_config.output_value = 0;
pm_config.pull = PM_GPIO_PULL_NO;
pm_config.vin_sel = PM_GPIO_VIN_S4;
pm_config.out_strength = PM_GPIO_STRENGTH_LOW;
pm_config.function = PM_GPIO_FUNC_1;
pm_config.inv_int_pol = 0;
pm_config.disable_pin = 0;
pm8xxx_gpio_config(PM8921_GPIO_PM_TO_SYS(PMGPIO(BCM4330_SLEEP_CLK_XC)), &pm_config);
mdelay(50);
}
#endif

And for audio, I havent had the chance to test it, but it loads for me, finds outputs, and sets volume levels on outputs. I could not get it to do the same with CM10
[HTC Droid DNA] crpalmer:
As far as I can tell, it really needs to have the operations split between lcd_on and display_on. display_on is called much later in the power-up sequence. I just sent you a pull request that does this and successfully turns the display back on.
[HTC Droid DNA] chad0989:
Merged :good:
[HTC Droid DNA] chad0989:
I have some changes I'll push later tonight. Mostly cleaning up and the start of some reorganization along with fixing adb.

You will need to update to the latest platform tools for it to work properly.

Major things that need to be addressed (probably incomplete) if everyone wants to just pick something and work on that:

Audio

MTP storage

Wifi

Bluetooth

I haven't checked but I'm willing to bet these need work also:

Camera

GPS (might be pretty easy)
[HTC Droid DNA] 123421342:
Can you suggest a good starting point for any of these? I would love to help if I can.
[HTC Droid DNA] t1gartist:
if audio start with getting alsa to talk with the kernel then on to the routing and then audio flinger
[HTC Droid DNA] chad0989:
Pushed the changes. In regards to adb:

You must update to the latest platform-tools. We're using adb secure (as it's default in 4.2.2) and only the latest version of adb supports it.

It will not function on first boot as its not enabled by default (since you need to accept the key), you must enable developer settings and then enable adb.

When you plug your phone in and try to adb to it for the first time it will display a key you have to accept for adb to function.
[HTC Droid DNA] amit_sen:
+1

I think he is talking about elite dev codeworkx.

He is the one who got camera working for ONE.

Chad himself said that we might get lucky if One camera is working. Seems like that ;)
[HTC Droid DNA] volfan22:
Oh I see. I was just saying anyways. Him or Chad or both of them should definitely get some reward. These guys are amazing!

CM10.1 Droid DNA
[HTC Droid DNA] psychologyok:
Just want to post that changing the orientation of the phone while in Youtube frequently crashes making you have to force reset. Haven't seen that reported yet so thought I would pass it along.
[HTC Droid DNA] ibsk8:
Issue #12, line 5 in the bug reports. It's been a known issue since the beginning. Check the OP.

sent via electromagnetic radiation.
[HTC Droid DNA] EmericanX:
Fix for previously mentioned bug: don't rotate phone while watching YouTube. ;) Lol.. JK man!

[MENTION=220657]chad[/MENTION]... keep up the great work man! I know I've been hit or miss and haven't contributed a thing to the build but I've been periodically checking in.. I've got a build for the RAZR HD that will hopefully be put to bed this weekend. So I'll get your latest source synced and go from there.
[HTC Droid DNA] chad0989:
Can someone do me a favor and get me a logcat in the stock sense rom of taking some photos, switching to the ffc, and taking a photo, and back? Thanks. Trying to figure out what parameter is messing us up here with the FFC. It works in aftermarket apps so it must be something the stock app is trying to use.
[HTC Droid DNA] sabbotage:
I don't know if this will help because I'm on the sense 5 port from the HTC One, but I opened the camera and snapped a pic, switched to front facing and snapped a pic, then switched back to rear camera and snapped another pic. Hope this helps!
[HTC Droid DNA] munchy_cool:
on newts sense 5
[HTC Droid DNA] armydog13:
"logcat.txt": https://skydrive.live.com/redir?resid=D51876F0A0877B10!219&authkey=!ALiup-UcAVX5mrg

"logcat_events.txt": https://skydrive.live.com/redir?resid=D51876F0A0877B10!220&authkey=!ALnmzbQ_lQrmYPM
[HTC Droid DNA] munchy_cool:
[MENTION=3124509]chad0989[/MENTION]

Not a dev here but maybe these help

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

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

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

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

Source - http://10.1.cmxlog.com/?device=m7
[HTC Droid DNA] djh816:
if cam on m7 is working we may very well have a fix :D if not, I heard 4.2.2 for the butterfly leaked a couple days ago so maybe someone could grab it from that (the One has a different camera than the DNA/Butterfly but maybe same control chipset)
[HTC Droid DNA] sabbotage:
The camera is already working. He's just trying to fix the crash when switching from FFC to rear camera.
[HTC Droid DNA] MrIcky:
I've got beer money waiting for the devs once a fully working build is available. Amazing progress gentlemen!
[HTC Droid DNA] chad0989:
Camera switch is fixed. Now there is a gallery freeze when you take a picture with the FFC though. I think it has something to do with post processing. I'll push the current tree now.

Please do not flood this thread with "I get a crash when I take a picture with the FFC," or "it works with this other app."

I'm aware of these things.
[HTC Droid DNA] rohitece06:
Any word on audio through BT?
[HTC Droid DNA] uppon2:
I'm sure he would have mentioned it if there was. Great job on the camera. I tried for days to get the camera to work on CM9 for the SGS 2
[HTC Droid DNA] chad0989:
I might get rid of the camera wrapper for now. I'm not sure we need it. The params the one guys are setting with it don't seem to affect us (they actually seem to have broken Flyhalfs latest build he posted). That and I think I'm going to try using the libs from the 4.2 leak. If you guys are running the broken build you can rename system/lib/hw/vendor-camera.msm8960.so to camera.msm8960.so and reboot. This removes the wrapper.
[HTC Droid DNA] rayfin:
And delete the existing camera.msm8960.so? as both camera.msm8960.so and vendor-camera.msm8960.so exist.

I renamed camera.msm8960.so to camera.msm8960.so.back and renamed vendor-camera.msm8960.so to camera.msm8960.so. I was able to take 1 picture, at 2.5MP, now when I open up camera, I just see black, then it eventually FCs.

EDIT: Reboot, was able to take over 20 pics before the above happened again. Grabbing logcat.

EDIT 2: I've been taking Front and Rear camera pics of 8 minutes. I can't get it to go black or force close. Very odd. Seems everything is working great with the camera. My previous issue must be an intermittent bug? I'll keep checking. Thanks again Chad.
[HTC Droid DNA] 123421342:
Broken as in not working at all? I can take pictures fine just at 3.8MP and no video.
[HTC Droid DNA] chad0989:
Pushed some new radio libs from the 4.2 leak and switched to HTCQualcommRIL since the new libs are compatible with the recent changes.
[HTC Droid DNA] crpalmer:
I was actually wondering if you'd looked much at the leak. I took a quick peek this afternoon, and my uneducated guesses were that HTC had managed to get a 4.2.2 with the bluez drivers and with the same wlan driver as our stock kernel. Did you look at those at all?
[HTC Droid DNA] chad0989:
I'm starting to look at stuff one by one. I was pretty bummed to see that they're still using bluez. I'd like to try to use as much as I can. It looks like it's built from jb_2.5 caf. Next I'm going to see if I can update our kernel and use the adreno blobs and cam libs also.
[HTC Droid DNA] themikeyan:
How much will the leak help with blue tooth audio? And being extremely new to this, how can I help?

Thanks as always
[HTC Droid DNA] crpalmer:
Probably not much. The leak is based on the same Bluetooth as the 4.1 stock ROM. Up to this point, chad has been working to get the newer bluedroid drovers working.
[HTC Droid DNA] crpalmer:
[MENTION=3124509]chad0989[/MENTION]

Man, you're a very low key guy.... You might have fixed bluetooth audio (but not voice calls) and you don't even say a word...

Last nights commits made BT audio work on at least my Jaybird headphones and my Jambox speakers.
[HTC Droid DNA] JWhetstone02:
When you say bt audio... or the whole bt audio issue in general for CM10.1

Is this just voice calls over bt or any audio over bt?

could I sync my phone with my car's system and play music but not get voice calls?