yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] IndyRoadie:
Not really the same thing. I want the option to set a Volume button to be able to Wake the phone, not just set a button to Answer calls..
[HTC Droid DNA] mcsplatt:
It's there, at the bottom of the button settings
[HTC Droid DNA] Swantexan:
Look at the bottom of the screenshot, it shows the volume to wake settings.
[HTC Droid DNA] IndyRoadie:
:eek:

Well, don't I feel stupid? Yes, yes I do.. lol

Thanks!
[HTC Droid DNA] Jaredsburrows:
Did you use the latest 12/20 ROM?

All I really want is bluetooth audio to work with my car! Everything else works great for me.
[HTC Droid DNA] robertmoore208:
One thing I myself noticed and not sure if its mentioned, if I don't add my bluetooth connection to the trusted lockscreen settings, it lasts quite a while longer before I have audio issues , like 10 to 15 min longer .. And I just reset everything for another 10 to 15 min. Not a huge but usually long enough to get where I'm going . maybe this can help someone out , maybe not
[HTC Droid DNA] ncd_x:
I installed it a couple of days ago, but posted here later. For me that was still the best build and at times I am tempted to go back to it. Almost everything worked well. Bluetooth in calls, in car through an aftermarket adapter, nothing crashed.

The newer builds have resulted in some instability - perhaps ti is because I have been dirty flashing (but i dirty flashed with the Dec 8 one as well). Today my phone randomly rebooted in the middle of a call and the bluetooth stops working in the middle of a call...
[HTC Droid DNA] zosimov21:
Anyone else not seeing app wigets with this ROM? Can't find settings for them. Using different launcher and beta gapps. Any help appreciated.
[HTC Droid DNA] santod040:
Well, you didn't say what launcher you're using, but that is what determines how you would access widgets.

They're either in the app drawer, or accessible when you long press the home screen.
[HTC Droid DNA] TweakedSystems:
Did you installs Gapps? install form main screen...
[HTC Droid DNA] zosimov21:
Thanks for the replies, I was using google now launcher and I hate that white background. My widgets menu was not showing. So I have a stock Android 5 launcher from my tablet. I just exported it and reinstalled the launcher APK 5.0.2-1649326 to my phone, and back in business. :good:
[HTC Droid DNA] fl00b:
Anyone else seeing abnormally high battery usage by Bluetooth service by just having it on and not connected to a bluetooth device? Took my phone off the charger at 100% and played with it for 12 minutes browsing the internet, installing and reconfiguring some apps, and generally getting everything set up again after updating, etc. Battery was down to 92% already and battery stats shows number 1 culprit as being Bluetooth.
[HTC Droid DNA] fl00b:
Charged back up to 100% and turned off bluetooth. 18 minutes later after light web browsing and a 5 minute phone call and I'm at 99%. Definitely the bluetooth service's fault but no idea why it's draining the battery like that. Any ideas?
[HTC Droid DNA] santod040:
UPDATED!~

Unofficial CM12 dlx 12-24-14 is now in the OP!

Happy Holidays!

See CM Gerrit for changes
[HTC Droid DNA] ncd_x:
I see this higher than expected bluetooth drain as well. Not sure if the phone supports the 4.0 LE, but still didn't expect 25-30% drain overnight with bluetooth connected. Haven't checked what the usage was with bluetooth enabled but not connected.

I am also seeing higher drain with cellular/LTE. Simple browsing results in about 1% decrease per min. But at least we have battery % indicator now, so we can measure such usage. It may have been true of earlier builds as well, we just didn't have a way to measure it.
[HTC Droid DNA] neelgangrade:
yes i have used the latest one !! have to wiped down everything !! but seems like i have to go back to GPE !! 4.4.4 ! :confused:
[HTC Droid DNA] TweakedSystems:
Sorry :( but this build is back to having the Bluetooth issues again.. Freezes my players FCs.. At least I Backed up the previous one.. :)
[HTC Droid DNA] IcyAgitator:
What kind of BT issues? I use JawBone and Motorola Stereo BT headset, no issues to report.
[HTC Droid DNA] icesteve:
I get phone audio using my cars Bluetooth, but not navigation or music. That's the only problem I've had with Bluetooth.

Thanks for the great work on this!
[HTC Droid DNA] TweakedSystems:
LG HBS700 not working ? Big JamBox not working But it works With my OBD2 adapter Dashcommand ?
[HTC Droid DNA] ncd_x:
My experience with this latest Dec 24 build has been better. The bluetooth issues I was seeing in the previous build seem to be fixed. Bluetooth in call is working again and the phone app is much more stable. I have the Motorola bluetooth headset.
[HTC Droid DNA] IronMonkeyL255:
I am still seeing bluetooth issues myself. It connects to my car fine, but when I try to open Pandora app, no music every plays. It just keeps going to the next song when it finishes buffering. When I give up and turn Bluetooth off, it throws up a Bluetooth Share error. The Pandora app works fine any other time, and it worked mostly fine (only issues I had were when trying to make a call with music playing) on the 10/19 build, but 10/20 and 10/24 seem to have the same issue.

Overall, aside from this issue the ROM seems quite stable compared to the early CM11 builds for our phones.
[HTC Droid DNA] Jaredsburrows:
I am seeing similar. I have verified that the SoundCloud and Google Play Music apps do not work with bluetooth in my car but Youtube does! This is with the latest build 12/24/2014, dirt flashed.
[HTC Droid DNA] Phibernaut:
Anyone having any luck putting up a wifi hotspot? I've tried different apps, etc. It appears to go up on occasion but nothing sees it.
[HTC Droid DNA] mcsplatt:
I have, op has a terminal script to run and then the native hotspot works fine. Plus once you use it, it adds it to the qs.
[HTC Droid DNA] Phibernaut:
Admittedly, I am an idiot. Thank you - I see it now.
[HTC Droid DNA] mcsplatt:
Knowing is half the battle.

From a fellow idiot.
[HTC Droid DNA] TweakedSystems:
Wifi Hotspot seems to be working fine for me...
[HTC Droid DNA] Phibernaut:
Thanks for the screen grabs. It looks to be an issue with the jamiethemorris kernel. Flashing NuK3rn3l made it functional (at least on a clean install). Now to restore my backup and see if NuK3rn3l still does the trick...

EDIT: Yep, that worked. Thanks!
[HTC Droid DNA] milnosaurus:
I'm in the same boat, I get a "couldn't play the stream you requested" or "couldn't play the track you requested" in play music, both with sync in my car and my bluebuds X headphones. It does pass the song info to my car though, I saw that pop up and was hopeful it would work but no dice!
[HTC Droid DNA] santod040:
UPDATED!~

OP updated with Unofficial CM12 dlx 12-29-14

All changes on CM Gerrit

Plus a few local adjustments made for BT. (hopefully they help)
[HTC Droid DNA] TweakedSystems:
:victory: First proggy I tried? Yep Bluetooth...Working with music programs! :victory: Outstanding! No issues as of now.. Appreciate all of the effort you have put into this ROM.
[HTC Droid DNA] EChondo:
First of all, thank you santod and the team for all of your hard work behind these ROM's. However, I do have a few issues that are minor, but they do annoy/worry me.

1. The row of buttons will stay lit if it gets touched after locking the device or putting it in sleep. Also rarely the buttons will light up a 10-20 seconds after the device has been locked and the buttons haven't been touched. I have semi-fixed this by turning off every option in the "Buttons" menu except for the "Recents" button, I have the long press set to open the "Recent Apps Switcher" menu, just like how the stock ROM works and functions. This only fixes the first part if the buttons get pressed accidentally, but this doesn't fix the buttons randomly lighting up after 10-20 seconds.

2. The Settings menu seems to be rather sluggish, there are delays when navigating through it where I'll be too quick for the phone and have to slow down, which wasn't a problem at all in past ROM's I've used. This isn't apparent in the app drawer nor in apps themselves.

I haven't updated to your 12-29 build yet, but I am using the Nuk3rn3l you've recommended. Sorry if this has been brought up before in this thread, I haven't had the time to sift through all 23 pages yet :P
[HTC Droid DNA] santod040:
The lights are due to ambient display.

If you don't like the effect, it's under display settings, turn it off.
[HTC Droid DNA] Jaredsburrows:
Soundcloud works for me in the Car now with Bluetooth!
[HTC Droid DNA] azgoofball:
help

Hey guys, I just tried to install the CM12 following the instructions and when i rebooted for the first time, the phone got stuck on the initial flash screen. I just hang there. I've wiped the phone and tried several times with no luck. I also tried to reinstall my old rom (ViperDNA) with no success. Can anyone help me out? I can get in and out of TWRP and fastboot but that's it.. :(

here's a little info on what's active on the phone in the bootloader:

unlocked - S-ON

Hboot - 1.33.0001

Radio - 1.00.00.1023_3

TWRP 2.8.3
[HTC Droid DNA] santod040:
You are s-on.

So after you flash a rom, you will need to fastboot the boot.img from whatever rom zip you are flashing.

So flash rom and gapps if flashing aosp.

Take the boot.img out of the rom zip.

Then in fastboot:

fastboot flash boot boot.img
[HTC Droid DNA] azgoofball:
Ok, let me try that. Thank you santod040!
[HTC Droid DNA] thenaut:
Use clockwork. That's in the Instructions by the way
[HTC Droid DNA] iHateWebOS:
Read the OP. It's not in the instructions by the way. I'm pretty sure recommended recovery to use is TWRP. I've been using 2.8.3.0(latest) with no issues, but some users have better luck with 2.7.x.x versions.
[HTC Droid DNA] thenaut:
You are absolutely right, and I apologize for my blunt rudeness. I got this thread confused with another.

For what its worth, I couldn't get this to boot using TWRP, only clockwork. That was weeks ago on an older version so maybe its different now.
[HTC Droid DNA] TweakedSystems:
Agree

I just noticed I have a (star) in the status bar..Don't know how I did this,but how do I get rid of it? THX
[HTC Droid DNA] danjull:
You got interruptions turned on. Go to Sounds & Notifications -> interruptions and change the "when calls and notifications arrive" setting. Should be the first one.
[HTC Droid DNA] IronMonkeyL255:
Everything seems to be working for me. Had a minor glitch that it was trying to launch another music program when it connected to bluetooth (specifically, the Music program which would then proceed to startle the crap out of me by playing my ringtone). When this happened and I launched Pandora, it seemed to lock up the bluetooth. When I would turn off bluetooth to try to get it working again, it would crash bluetooth share. Disabling the Music program seems to have fixed it. Oddly enough I couldn't freeze it in titanium backup, and had to disable it in the settings app menu.....
[HTC Droid DNA] therreid:
I shelved my Galaxy S5 yesterday and dusted off the old DNA to try this yesterday. I updated TWRP to 2.8.3 and then flashed. So far all is working great. I have not had any problems. The only issues are the same ones that caused me to shelve the DNA. Terrible battery life after the stock KitKat update and the lack of storage since we have no ability to add a micro -SD. I don't like the S5, but will probably get stuck going back to it because of the two issues. I sure wish HTC would come out with a phone with access to the battery and an SD slot...... In the meantime this is a great ROM and would be fine for my daily driver.
[HTC Droid DNA] therreid:
Update.....occasional issues with blue tooth reconnecting to my car audio streaming Pandora. Also, sound will cut in and out occasionally. A reboot of the phone corrects this. Not huge issues.....still loving Lolipop.
[HTC Droid DNA] IronMonkeyL255:
I was just coming to post this. It launched Play Music one time on connecting, but not every time. Every time I have troubles reconnecting, Bluetooth Share crashes when I turn off bluetooth. A reboot corrects it every time.
[HTC Droid DNA] Gr8Jeepin:
I'm having the exact same issues running the liquid smooth ROM.
[HTC Droid DNA] ncd_x:
Help - Stuck in a restart loop!

I don't know what happened overnight, but this morning I woke up to my DNA stuck in a restart loop. Everything was working fine until last night. I did not change/update anything...

I can boot to recovery, so I wiped and re-installed the build again, but it just won't boot. Keeps going to the white screen with HTC logo, then the Cyanogen logo and back to htc logo...

How can I fix this?
[HTC Droid DNA] Izzmit:
Check your google apps version, make sure its lollipop.

Also, dont reinstall your CM12 ROM file. get a new one, make sure its not corrupted.
[HTC Droid DNA] ncd_x:
Thanks for the quick response. How do I check the GApps version given that the phone just won't boot. Any way to do it from recovery? I wonder why it would go kaput all of a sudden when it was working fine until yesterday.

Also, the only build I have on the phone is this one. Do you know how to connect the phone to the PC while it is in recovery? Or do I have to go to fastboot and then use ADB?
[HTC Droid DNA] mcsplatt:
Not sure about checking gapps version,but you should be able to use adb sideload in recovery to flash ROM and gapps zips.
[HTC Droid DNA] TweakedSystems:
Are you able to boot into recovery? (power off) power + volume key down at the same time... Just do the Advance Wipe > (Dalvik cache, cache,data,system) should work..use PA Gapps posted on the first page...
[HTC Droid DNA] ncd_x:
I tried the sideload feature, but it does not workfor me. It stays stuck at the prompt "starting adb sideload feature" and adb does not detect the device.

Strangely, when i am in fastboot, the device is detected.

Any other ideas? How do I get the ROM.zip to the device to install it through recovery?

Or, do I have to go back to RUU install back to factory stock? I see random reboots, so it seems like the SD card may have gotten corrupted, how can I reset everything and then install a new ROM that is not on the device?

Thanks
[HTC Droid DNA] TweakedSystems:
Found this link :) worth a shot good luck.. http://androidflagship.com/3217-fix-damaged-bricked-android-device
[HTC Droid DNA] ncd_x:
Yes, I am able to boot into recovery, but that is pretty much the only thing that works. I wiped everything using advanced wipe and re-installed the only ROM that is on the phone, but it keeps rebooting. Sometimes, the screen shows up with garbled display, but it boots right after that.

Could it be a hardware problem with the sdcard? Factory Reset is looking pretty tempting right now. Or maybe try to get stock recovery on and the stock ROM for the device.
[HTC Droid DNA] mcsplatt:
These are the steps i would take:

First see if there's an md5 check in recovery for your ROM and make sure that's legit.

wipe everything (sys, data, cache, dalvik) and reinstall ROM and gapps. If that don't work, try a fresh recovery via fastboot, wipe everything again and reinstall ROM and gapps. If that don't work, factory reset, wipe again, and reinstall ROM and gapps. If that don't work, something is borked.
[HTC Droid DNA] iHateWebOS:
Side load feature was iffy for me as well on all the newer twerp recoveries. Using the restart adb command while booted into twrp fixed the issue for me and I was then able to side load. "Sudo restart adb" if your on an Ubuntu based Linux distro. Not really sure if windows is the same
[HTC Droid DNA] ncd_x:
Unfortunately no md5 check for the ROM, while installing it bypasses that check.

I have wiped everything including the system and the factory reset. But boot looping continues.

Now, I want to get a different ROM on this phone to see if that helps, but unfortunately I am unable to do so. Sideload did not work (perhaps because ADB did not recognize my device). So, if I am somehow able to get adb to recognize my device and push a different ROM that I could install, I could move forward in my troubleshooting.

When connected to the computer (windows 7) while in recovery, I do see a device in the device driver, but it is a yellow warning sign with no device driver for it. I have the latest HTC Sync installed (and then uninstalled Sync part of it to just have the drivers). But no avail. I think if I can get those drivers from somewhere I could get adb to recognize my device and then push a different ROM.

Would anyone know where to get the Recovery mode drivers for Droid DNA? In the fastboot mode, the device is recognized, but I cannot push anything to the device.
[HTC Droid DNA] santod040:
Garbled display sounds like you don't have the appropriate firmware to run this rom.

You need to be on the latest kitkat firmware which includes the latest hboot as well as radios, etc,..

You can find the firmware here.

Then to push a rom to the phone, I use Twrp:

Mount > System(check it)

Open a terminal on the PC with the zip file you want to push, in your adb/fastboot directory.

adb push nameoffile.zip /sdcard/

(Replace nameoffile.zip with actual filename)

You will find the file on your device to flash in recovery when it's done pushing.

I did not see if you were s-off or not either and if you tried fastboot flash boot boot.img if you are s-on.
[HTC Droid DNA] ncd_x:
Thanks a ton - it is great to hear from the Dev himself.

I am s-off and supercid. I also have the latest firmware 4.09

I tried doing the mount system and then the adb push, but the problem remains the same - "error: device not found"

adb cannot find my device, only fastboot can.

---------- Post added at 07:22 AM ---------- Previous post was at 07:18 AM ----------

This ROM was running all fine and dandy until yesterday (it's a lovely ROM), when I went to bed. Then in the morning I found it in the bootloop mode without ever having updated anything.

I have been on this ROM for over a month and updated the builds regularly - each build an improvement over the previous. And then this. I am planning to put your LiquidSmooth ROM on it, (if I can get the ROM over to the device).
[HTC Droid DNA] ncd_x:
My problem got resolved automatically, inexplicably...

I just wanted to share an update, my phone got out of the bootloop problem and booted into the Os.

Here is what happened:

1. I did all the wiping and reinstalling yesterday - no luck.

2. Also went looking for a new substitute phone on swappa. Threw some disapproving glances at my Droid DNA. Sighs too.

3. Finally, late at night, got tired, shut the phone down completely ("Shut Down" from Recovery) and went to sleep.

4. In the morning, got up and thought I might give it one last try, almost sure it won't work.

5. Magically, the phone booted up to the OS screen and stayed there. I left it alone for 15 minutes (just to not interfere with any startup process) and then tried to use it. Still kept working.

6. It could probably have kept working, but I quickly connected it to the computer, the internal storage showed up. Copied the Stock and LiquidSmooth ROMs to it along with GApps.

7. Installed LiquidSmooth ROM on it and restarted, booted right up.

So far it is working (need emoticon for fingers crossed)

I am not sure what fixed it. It went bad automatically during the night and the next night it got fixed automatically. If I was to venture a guess, maybe step 3. helped. Otherwise, it was definitely 2.
[HTC Droid DNA] mcsplatt:
[MENTION=769275]ncd_x[/MENTION] sounds like you might need an exorcist or shaman or something
[HTC Droid DNA] ncd_x:
Haha! It is quite possible [MENTION=1272062]santod[/MENTION] performed a remote exorcism. He does care a lot about his ROMs.
[HTC Droid DNA] santod040:
UPDATED!~

OP updated with Unofficial CM12 dlx 01-05-15

See CM Gerrit for changes

I have now set SE Linux to Enforcing mode.

It has been set to Permissive in my previous Dlx builds for various reasons.

But seeing how CM will be posting them set to Enforcing, I want to finish up my builds this way, now that it's all working as intended.

If you need it set to Permissive for such things as Titanium Backup or some other various root apps that require it, you can do so using this app.

I also suggest a clean install, or you may have issues that are due to the Permission changes.(including but not limited to camera issues, of which I have none)
[HTC Droid DNA] psyrius:
Issue flashing - zip changed

I've been using the 12/19/14 CM12 ROM and am absolutely loving it so far. I have had I think 1 FC but other than that has literally been the smoothest ROM I've used in a long time. Feels so great to get these updates for my DNA, and am thankful us users are not forgotten about. That said, I'm attempting to flash the updated 1/5/15 ROM posted this morning, and it fails immediately (thankfully it's at the mount portion and it dies right away so nothing is in an unstable

state).

The new ROM has the following contents:

matt@gir:~/Downloads/cm-test/META-INF/com/google/android$ grep by-name *

updater-script:mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");

updater-script:mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", "");

updater-script:block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

updater-script:mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");

updater-script:mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");

updater-script:package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

Which is where the TWRP fails (trying to mount /system at /dev/block/platform/msm_sdcc.1/by-name/system)

I looked at the 12/29 zip file, which has the following contents:

matt@gir:~/Downloads/cm-test-old/META-INF/com/google/android$ grep mmc *

Binary file update-binary matches

updater-script:mount("ext4", "EMMC", "/dev/block/mmcblk0p32", "/system", "");

updater-script:mount("ext4", "EMMC", "/dev/block/mmcblk0p34", "/data", "");

updater-script:block_image_update("/dev/block/mmcblk0p32", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

updater-script:mount("ext4", "EMMC", "/dev/block/mmcblk0p32", "/system", "");

updater-script:mount("ext4", "EMMC", "/dev/block/mmcblk0p32", "/system", "");

updater-script:package_extract_file("boot.img", "/dev/block/mmcblk0p19");

Is this intended?

Regards,

Matt
[HTC Droid DNA] santod040:
Yes, "by-name" mounting is the better and newer way of doing things, rather then using block names.

You will just need to update to a Twrp version that supports "by-name" mounting.

The one I am using is older but was from MdMower and does have by-name mount support.

The latest official version should have by-name mount support as well.

MdMowers 2.7.1.2 has always worked well for me and can be found here. Link
[HTC Droid DNA] TweakedSystems:
one major problem... Everything seems to working fine..except my signal constantly keeps dropping :( i have 3 bars but when I go to make a call,it just drops all together... message says unable to connect NO SERVICE
[HTC Droid DNA] santod040:
Let the Nightlies begin....
[HTC Droid DNA] Supashawn:
By "clean install" do you mean total wipe and install via side load or... Just don't dirty flash?
[HTC Droid DNA] santod040:
I just meant not to dirty flash.

No need to wipe internal storage, just system, data, cache, and dalvik.
[HTC Droid DNA] psyrius:
Santod, thank you. I upgraded my TWRP from fastboot and it installed perfectly. I also did a dirty flash over the 12/29 build and have had 0 issues so far. Again, I have to tell you, fantastic job on this ROM!
[HTC Droid DNA] loveuhp:
when calling, screen off but Touch using normally. [MENTION=1331268]santod040[/MENTION]
[HTC Droid DNA] robertmoore208:
Anyone having strange issues with setting alarms?? Flashing icons , freezing , and notifications popping in and out in status bar?? Really odd