yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] chad0989:
I think I have a fix for the wifi issues (toggling, not tethering yet). Going to test for a day or so then I'll push.
[HTC Droid DNA] aFancyTickler:
chad have you looked into the new Radio Version 1.01.04.0300 ? i flashed it and data was being crazy. 4g stopped working and 3g takes forever to start, i put a logcat up on the bugtracker for you to take a look when you have time :P
[HTC Droid DNA] chad0989:
Can you confirm by flashing back to old radio?

Can anyone else confirm?

If so I'd rather just include the radio firmware with the build then mess with the RIL, since it's working well.
[HTC Droid DNA] aFancyTickler:
i cant confirm right now but tomarrow il definitely check if no one else checks but prior to flashing the new radio i had 2-3 bars 4g and after flashing it my 4g stopped completely and i tried rebooting like 3 times and i got the same result of no 4g. i took a logcat of it. right now im back to my sense 5 rom and my 4g is back at 3-4 bars
[HTC Droid DNA] crpalmer:
If you can reproduce the good (old radio) and bad (new radio), can you then also check the kernel version number (ideally from adb shell type cat /proc/version and if that then look in settings >> about phone)?
[HTC Droid DNA] KyJelly69:
It's 1.01.04.0308
[HTC Droid DNA] t1gartist:
it seems the radio isnt to friendly with cm10.1 but all other roms appear to be reporting faster connects and better 4g data

my experience is this i lost 1 bar of 4g data and gained faster connecting times during bootup almost instant on sense based roms i got full tower of 4g and instant sim connect and slightly faster speeds
[HTC Droid DNA] crpalmer:
The version that I was curious about was the kernel version because I wondered if the new radio might work poorly on the 1.15 source and chad merged in the 2.04 source on Sunday. Given it was so recent, I wanted to confirm that we're seeing bad behaviour on the latest source.
[HTC Droid DNA] KyJelly69:
I'm on viper 1.1.3 and the radio is working fine
[HTC Droid DNA] aFancyTickler:
The kernal says

3.4.40-g27b8ffb

david@flyhalf205 #1

sun apr 14 23:43:46 CDT 2013

My kernal on sense 5. (which has 4g working) is

3.4.10-ga02d2c6

root@abm020 #1

smp preempt

*edit* when i get home in about 4 hours lol i will flash the cm10.1 again and see if the radio still gives me issues

*ediit 2* 4g works now on the new 4/16 build.
[HTC Droid DNA] chad0989:
Pushed wifi fix. Switched to the AOSP bcmdhd code instead of HTCs.
[HTC Droid DNA] chad0989:
Got GPS working. Very easy fix. I want to a little more work on it though then I'll push.
[HTC Droid DNA] jonesin:
Might this fix native wifi access point functionality?
[HTC Droid DNA] chad0989:
No. Something else going on there
[HTC Droid DNA] jonesin:
Thanks. I'd get you a logcat but I already nuked cm for the time being. When I go back I'll provide as many bug reports as I can.
[HTC Droid DNA] stillthisguy:
I have not had any issues with the new radio and CM10.1.
[HTC Droid DNA] Bigandrewgold:
-52 dBm, holy hell. What type of speeds do you get.
[HTC Droid DNA] amit_sen:
Chad,

I think I should update the initial post.

Both GPS, audio should be in what's working list :D

Thanks once again for brilliant work :thumbup:

Sent from my HTC 'One' DNA
[HTC Droid DNA] chad0989:
There's still a couple audio issues I want to fix (voice to text etc) before I consider it fully working. I haven't pushed the GPS fix yet. Still doing some testing.
[HTC Droid DNA] dmbfan13:
Thats awesome news you got GPS working!!!! Got my fingers crossed for a working camera!! :victory:

Nice work!
[HTC Droid DNA] volfan22:
It's seriously beyond me why some of these oems don't hire guys like you Chad. You're a genius with this stuff and I think you could do much better for them than the people they have doing software now. You do this in your free time and create something better than anything they do. You're awesome!

CM10.1 Droid DNA
[HTC Droid DNA] skynet11:
They don't hire guys like Chad because most are not interested in being developer-friendly. From what I've read they make their GPL code difficult to understand on purpose and they make everything as locked down as possible. The whole purpose of OEM skins is to drive sales by providing a proprietary, difficult-to-replicate, difficult-to-bypass user experience.
[HTC Droid DNA] brennam7:
Can we please keep this on topic?
[HTC Droid DNA] chad0989:
I'll keep my day job. Haha.
[HTC Droid DNA] Stoney 666:
Bro.... On topic, please... Sheesh....

Sent from my HTC6435LVW using Xparent Cyan Tapatalk 2
[HTC Droid DNA] yutsoku:
He's the op he does what he wants in this thread lol

Brought to you by Droid DNA and Tapatalk
[HTC Droid DNA] chad0989:
Pushed GPS stuff. It's not the way I want to do it permanently but it works for now. It gets it working so that I can work on other stuff. I definitely want to eventually return to it and build our own HAL or use HTCs prebuilt HAL.
[HTC Droid DNA] munchy_cool:
First of all apologies for the OT.

Secondly, beer is on me tonight bro, hope you got it.

Thanks,

Munchy
[HTC Droid DNA] Stoney 666:
That was the joke... :)

Sent from my HTC6435LVW using Xparent Cyan Tapatalk 2
[HTC Droid DNA] azndan2:
Chad, thanks for all of your hard work. Here is a pearl milk tea on me. I am sure we will have a 100% working build with you at the helm. Have a lovely day.

Confirmation number: 1DR7468086727133M.
[HTC Droid DNA] typeriz:
Will pulling the camera frameworks from the HTC FIRST help with the camera for the DNA, as it's running stock aosp
[HTC Droid DNA] danielhall2689:
Hey Chad would the same fix that you used to get audio running for 4.2 work with 4.1.2? (for miui)
[HTC Droid DNA] chad0989:
Possibly but I haven't looked at the audio HAL in 4.1 at all so I don't know if our 4.2 HAL would be compatible.
[HTC Droid DNA] 123421342:
Adding governors, would that be on your end? Also, do you know about a possible bug where android os uses just as much or more battery than the screen(easily 120+mA for one hour of light use) and that the screen uses more battery than it really should? Other than that, this rom is amazing and I really thank you for developing it.
[HTC Droid DNA] chad0989:
Governors are for people who release kernels and the other things you mention aren't of concern right now. I'd much prefer to work on getting everything functioning before anything else. Android OS only uses 2% for me though so I don't even know what others are talking about.

If someone wants to be helpful and contribute they can find auto brightness settings that seem to work well in all lights (and are reasonable defaults) and send the table to me so I can make it the stock settings.
[HTC Droid DNA] 123421342:
One power guard shows mA usage for all apps and android os takes 44% of the entire battery, around 180mA for just 2 hours.
[HTC Droid DNA] chad0989:
I'd probably trust the OS itself over a random app...

I'm not saying that the battery life isn't reduced over stock, because it is (although I don't feel its that bad, I still get through the day and have 50% at night). I'm just saying its not a concern right now until all the hardware is working.
[HTC Droid DNA] 123421342:
I agree but the drain I'm talking about doesn't show up in system battery graph. It's called android os not android system I just wanted to let you know what's up because that explains the battery drain.
[HTC Droid DNA] chad0989:
Android OS is in the battery graph along with system.
[HTC Droid DNA] 123421342:
Mine isn't at all and you can clearly see something is going on. In inclined to believe one power because I do have significant battery drain.
[HTC Droid DNA] chad0989:
That's because it only shows things that are above 2% or so. Keep checking and you will see it eventually at 2-4%
[HTC Droid DNA] 123421342:
That may be true, but I dont think it is accurate. There is no doubt at all that something is draining the battery. One power guard shows that android os, the screen and phone idle take the most power. I havent used my phone that much over 15 hours and my screen has used 1100 mA, android os has used 700, idle has used 200. Those numbers do not make any sense. Now, either OPG is completely wrong or those things are draining absurd amounts of energy. Given that the battery life is around 8 hours less than sense+zarboz kernel, I am inclined to believe OPG is reporting accurate values. I am not saying something needs to be done immediately, I am just letting you know there might be a problem that can be fixed down the road.
[HTC Droid DNA] Dri94:
He said its not a primary concern right now. Let him continue working
[HTC Droid DNA] 123421342:
I know what he said before, but then he said OPG is showing invalid data. Again, I am not implying he needs to fix this right now, I am simply bringing it to his attention. The fact is, android os, phone idle, and the screen seem to take an absurd amount of power(and I am using the exact same settings as my other rom).
[HTC Droid DNA] tslagle13:
In support of Chad's amazing work! Getting incredible battery life on this ROM. Almost double what I was getting on sense.

Sent from my CM10.1 DNA
[HTC Droid DNA] 123421342:
So you got 30 minutes of battery life with sense? :p Why dont you post back in 15 hours.
[HTC Droid DNA] Dri94:
Well he's responded. Nothing more needs to be said
[HTC Droid DNA] 123421342:
No offense, if you arent going to contribute to the discussion don't comment on it. He rebutted my evidence without commenting on my picture that clearly shows high battery usage. I am waiting for him to answer my latest comment. Again, I just want the issue either acknowledged or explained, not fixed.
[HTC Droid DNA] rayfin:
Dude. This is a work in progress / development thread. The #1 concerns are to get all hardware working. If in fact battery is being obliterated like a whore on nickel day, things will be resolved eventually. Chad said this himself.
[HTC Droid DNA] 123421342:
I know. Part of development is getting things working. I already know Chad said he is prioritizing getting hardware working and I completely agreed with him. I just want to bug either explained(either one power guard is wrong, android is wrong, or the drain is from something else) or acknowledged as a bug because thats part of the development cycle. Thats all.
[HTC Droid DNA] munchy_cool:
there is a bug link in the builds thread, why dont you submit it as a bug and stop discussions in a dev thread, please use the build thread for that...
[HTC Droid DNA] 123421342:
Whats the point of the dev thread then? I will submit it there thanks,
[HTC Droid DNA] chad0989:
I really do appreciate that you want to help. The issue is that there are dozens of things that can be using power. I already mentioned auto brightness settings need to be adjusted. I only recently even enabled mpdecision so I don't even know if its in the posted builds. Its appears to me that android battery stats is grouping different processes into the category android os than one power guard. A statement saying your not getting the same battery life as you did on sense doesn't really help, it needs to be more specific. A bug report needs to be more like "the specific process x is causing a large drain because it is holding a wake lock indefinitely, here is a log."

I'm really not trying to come off as being a jerk about it and others shouldn't have jumped all over you when you're trying to help. We just really need more specific information to fix anything. This is a generalized bug report issue, not anyone in particular.
[HTC Droid DNA] crpalmer:
Hopefully a message with developer related content in a developer thread will not get lost in the sea of messages...

I have just spent a little time looking at bluetooth. According to the logcat, I have it loading the firmware but it still seems a fair way from working. If someone else is going to look at it or is currently looking at it, let me know and I'll pass along what I know / changes I've made.
[HTC Droid DNA] 123421342:
Thanks. Quick note about mpdecision- I saw it running when I was looking at cpu usage, thats about all I can say. I am using velis autobrightness, the same settings that I was using before CM so stock autobrightness isnt affecting me. I will do my best to get you a logcat. What do you think would be the best way to expose the underlying issue using a logcat? I really appreciate your hard work, I really dont want to come off as a jerk.
[HTC Droid DNA] chad0989:
Push it / post it up. I have the firmware loading also with flyhalfs change but I haven't gotten a chance to look at it more than that. Realistically I feel it shouldn't be too hard to get it going considering that broadcom wrote bluedroid.
[HTC Droid DNA] crpalmer:
Are you going to have some time to work on it?

The first fix was to set /system/vendor/lib in the LD_LIBRARY_PATH. That gets libbt-vendor.so loaded (was that flyhalfs change that I missed?).

I think I ended up going down a bad path for the rest that sounded useful when I wrote that post. If you want to work on it, please do! I'll poke at it a little tonight to see if I can be more useful.
[HTC Droid DNA] Flyhalf205:
I just used a symlink. But That was my fix I posted a day or two ago.
[HTC Droid DNA] crpalmer:
I was wrong yesterday when I thought it was downloading the firmware for bluetooth. The change I made for the vendor library was:

diff --git a/ramdisk/init.rc b/ramdisk/init.rc

index d3d9ae3..e1bd046 100755

--- a/ramdisk/init.rc

+++ b/ramdisk/init.rc

@@ -33,7 +33,7 @@ loglevel 3

# setup the global environment

export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin

- export LD_LIBRARY_PATH /vendor/lib:/system/lib

+ export LD_LIBRARY_PATH /system/vendor/lib:/system/lib

export ANDROID_BOOTLOGO 1

export ANDROID_ROOT /system

export ANDROID_ASSETS /system/app

It seems to hang during the transfer of the firmware. After it has hung, I need to reboot to try again. Looks like something can't handle the 3Mbps baud rate that it's setting. Even 230400 was hanging for me. Dropping it all the way down to 9600 baud seems to successfully transfer the firmware. To set that:

diff --git a/bluetooth/vnd_dlx.txt b/bluetooth/vnd_dlx.txt

index db8ba3c..f5697ba 100644

--- a/bluetooth/vnd_dlx.txt

+++ b/bluetooth/vnd_dlx.txt

@@ -6,3 +6,4 @@ BTVND_DBG = FALSE

BTHW_DBG = TRUE

VNDUSERIAL_DBG = FALSE

UPIO_DBG = FALSE

+UART_TARGET_BAUD_RATE = 460800

and then I believe that the kernel needs to be configured with HCIUART_H4 as the protocol used by bluedroid:

diff --git a/arch/arm/configs/dlx_defconfig b/arch/arm/configs/dlx_defconfig

index 63da511..ccc2f62 100644

--- a/arch/arm/configs/dlx_defconfig

+++ b/arch/arm/configs/dlx_defconfig

@@ -1115,7 +1115,12 @@ CONFIG_BT_HIDP=y

# CONFIG_BT_HCISMD is not set

# CONFIG_BT_HCIBTUSB is not set

# CONFIG_BT_HCIBTSDIO is not set

-# CONFIG_BT_HCIUART is not set

+CONFIG_BT_HCIUART=y

+CONFIG_BT_HCIUART_H4=y

+# CONFIG_BT_HCIUART_BCSP is not set

+# CONFIG_BT_HCIUART_ATH3K is not set

+# CONFIG_BT_HCIUART_LL is not set

+# CONFIG_BT_HCIUART_IBS is not set

# CONFIG_BT_HCIBCM203X is not set

# CONFIG_BT_HCIBPA10X is not set

# CONFIG_BT_MSM_SLEEP is not set

Having made these changes, it looks like bluedroid is getting itself started but then I have a mismatch between the Java state and the C state (Java thinks its disabled and bluedroid thinks it is enabled). I haven't looked at this at all, but a wild guess might be that something timed out in the very long time it takes to transfer the firmware (several minutes).
[HTC Droid DNA] 123421342:
Chad, I looked into the android os issue and it seems that one power guard calls the kernel "android os" and GSam calls it "kernel". Either way, they both show it as the larger user of power. Would you like me to post a fairly long logcat of regular use or is there anything you want me to test?
[HTC Droid DNA] chad0989:
Am I correct in assuming you're using the CAF bluetooth?
[HTC Droid DNA] crpalmer:
I was alternating between my kernel that uses CAF drivers and the CM10 kernel to see if either was happier than the other.

I ended up with 115200 as a fairly reliable speed.
[HTC Droid DNA] chad0989:
With your changes BT actually turned on completely successfully once for me. So its definitely real close. :good: I have a few changes I'm going to try, hopefully they'll get it going the rest of the way.
[HTC Droid DNA] crpalmer:
I had it turning on once too, but I couldn't get my audio headset to show up as an option to pair or let alone to actually pair with it. I just chalked it off as a fluke. Hopefully you're right that it is close and you can figure out the rest of it!
[HTC Droid DNA] chad0989:
Bluetooth is giving me a headache so I fixed some other things so that I can feel better:

Finally got rid of the prebuilt init.rc and cleaned up the init stuff a good amount

Fixed the periodic artifacting issue

Fixed the voice search function

I'll push the fixes when I finally organize everything into proper commits.
[HTC Droid DNA] chad0989:
Ha. Got Bluetooth figured out. Today is a good day. Headset audio likely doesn't work yet (haven't tried it) because I'll have to sort out the routing, but I can pair and send files.

msm_serial_hs_brcm needed to be called msm_serial_hs. Now the question is should I use the bluesleep driver I pulled over as well or not....
[HTC Droid DNA] crpalmer:
I would keep bluesleep. Worst case is that we waste a few bytes of memory.

---------- Post added at 06:59 PM ---------- Previous post was at 06:51 PM ----------

Does this also get rid of the firmware download problem? Aka, can you remove the change to limit the baud?

Ps - nice work figuring it out!
[HTC Droid DNA] chad0989:
I'm rebuilding now to try it out. I believe it should though.
[HTC Droid DNA] Upstreammiami:
So what would be left after this? Camera
[HTC Droid DNA] skynet11:
There's still the mass spectrometer - oh, wait...
[HTC Droid DNA] azhockey:
Damn, I knew this phone had it all!
[HTC Droid DNA] chad0989:
Brings me back to the days of spec lab. The funny part is that our phones are 10x more powerful than the computers all the instruments were hooked to. The NMR computer was still on Win95.

To stay on topic. With the new fix I can up the baud rate back up to 3000000 and it works great. I'm not going to get it all pushed tonight since I haven't had time to organize everything, plus I want to try a BT headset and get the audio routing for it sorted out. I'll try for tomorrow. Sorry for the delay.
[HTC Droid DNA] crpalmer:
Are you actually building bluesleep? It calls msm_hs_request_clock_off which is only in msm_serial_hs (the _bcrm version renamed that function to brcm_*).

Also, it uses msm_hs_set_mctrl and the brcm driver has their version of this function #if 0'ed out of the code.

Looking at it, it also looks like many of the changes in the brcm version of the driver involve sleep states. Given all of that, I would change my vote to be to not include it...
[HTC Droid DNA] chad0989:
I'm not using the brcm version. I moved to msm_serial_hs and bluesleep in lieu of it. You're welcome to review everything when I push it. I value your opinion so if you don't like something we'll figure out a better way.
[HTC Droid DNA] crpalmer:
That's very interesting. I'm running the Viper 1.2.0 which is based on Verizon's 2.04. If I switch to msm_serial_hs then bluetooth doesn't work at all (if I had to guess, it probably fails to download the firmware). If I remove msm_serial_hs and use on msm_serial_hs_brcm then it works fine.
[HTC Droid DNA] chad0989:
Pushed the latest changes. Voice over BT headset is not working yet. Well, I have it working but it sounds terrible right now so I need to sort that out before I push anything in regards to that. You can pair and transfer files though.
[HTC Droid DNA] 123421342:
Is MTP the only transfer protocol available to this phone?
[HTC Droid DNA] chad0989:
PTP should be supported also but I've never tried it.
[HTC Droid DNA] 123421342:
Is there any hope for mounting as a flash drive? MTP is described as an "intelligent system" but its pretty stupid when I have to open a folder just to make it load it just to see its size, it rescans all the folders if I go back to root directory, has issues copying subfolders and literally displaying certain files....
[HTC Droid DNA] chad0989:
No. Our internal storage is part of our data partition, which is formatted as ext4. It wouldn't work at all for anyone who isn't using Linux, and I would guess that is a pretty solid majority.
[HTC Droid DNA] ibsk8:
Mtp is a pita at times but it sure is nice having dual access to data and eliminates wear from mounting and unmounting a sdcard

sent via electromagnetic radiation.
[HTC Droid DNA] 123421342:
I thought"wear" was only from writing?
[HTC Droid DNA] Flyhalf205:
[MENTION=3124509]chad0989[/MENTION]

Not sure how often you sync your source. But I ran into two problems when building. I think I finally got the commits right on the cm-10.1 if you can take a look into it.

https://github.com/CM10DNA/android_kernel_htc_dlx/commit/26698ed75f868af5497b83782a78fe8244fb2a18

https://github.com/CM10DNA/android_kernel_htc_dlx/commit/37c547aa02d1a33abc9df57c02c1bea9b274e2b8

I'm still building so I am not sure if I have any errors in rom.
[HTC Droid DNA] chad0989:
Those do fix the errors. :good: I don't sync nearly as often as I should. Usually my device trees are all in disarray so if I go to sync I run into issues.
[HTC Droid DNA] TheDanimal:
Good. I synced again today and saw kernel changes. Thanks, Chad, flyhalf, crpalmer and everyone else working on this.
[HTC Droid DNA] Phaded:
I still use Win XP, and MTP won't even work... I've been using FTP
[HTC Droid DNA] chad0989:
Pushed an update for

wired

headsets

Reduced the gain on the rt5501 headset amp to what HTC sets it to in their external config (-6dB), this helps with some of the headset noise.
[HTC Droid DNA] chad0989:
Can someone get me a logcat and kmsg on the stock sense rom while making a call over BT? Thanks.
[HTC Droid DNA] munchy_cool:
Cm just pushed an audio caf branch , not sure if that helps us in some way .

sent from a red beast on sense 5
[HTC Droid DNA] chad0989:
We're already using a forked version of that repo. But it does look like they're making some of the same changes that I did to it:

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

So once some of their changes are merged we should be able to ditch our forked version and use the one in mainline.
[HTC Droid DNA] gitku:
Question on the headset gain. HTC always sounds like the gain is too far up on Bluetooth connections. My s3 sounds 10x better on calls through BT. Would the fix you implemented fix this? I assumed it was hardware since tbolt was the same way ...
[HTC Droid DNA] chad0989:
No. It doesn't affect BT.
[HTC Droid DNA] rjd584:
Does by headset audio not working include car audio/by call audio?
[HTC Droid DNA] chad0989:
[MENTION=3857343]crpalmer[/MENTION]: Ever get a chance to review the BT changes?
[HTC Droid DNA] azndan2:
Hi all,

I woke up this morning to my alarm and was able to unlock it (without seeing anything, I just swiped to the right), however, the display would not show up. The backlight would turn on but it would only be a black screen, so I was forced to reboot.

For next time, should I get a logcat, or last kmsg, or what would be the best thing for me to do to help you diagnose the problem?
[HTC Droid DNA] crpalmer:
I looked at the commits when you pushed them and they were small enough that there's nothing that I could possibly complain about with them...

I finally got a chance to build this today and see what it's really doing. It is looking good. Specifically, it looks to me like the bluesleep driver is working (when trying to make a call on the headset, it writes to /proc/bluetooth/sleep/btwrite). The bluetooth stack also seems to be working well to me. I can pair my headset and when I make a call it connects to the headset for the call and disconnects normally when the call ends.

All of which sounds like I agree with you that it sounds like an audio routing problem as everything seems to be working well aside from the fact that there is no sound.
[HTC Droid DNA] Dri94:
There is a bug report in the op. Do that, and get a logcat next time if you can