yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] helltrum:
unofficial cm12 run good for me but when i flash official nightlies i get stuck on HTC screen, i updated TWRP to 2.8.4, i updated my radio and hboot to be safe, and redownloaded and triple-checked MD5 codes, and still get stuck on HTC screen, it hangs for about 10 minutes then reboots to the HTC screen should I RUU?

EDIT: it booted and runs fine after a full wipe (internal memory) after flashing. Booting to recovery leads to the same issue until i perform a full wipe again, small issue, great rom!
[HTC Droid DNA] billywilly:
Screwed

This is cool but I can't make it work on a fully updated and non Rooted dna right? I searched the threads and they mentioned "if you updated then this method for rooting won't work for you". OK well is there a method that will work?
[HTC Droid DNA] JeromeLeung:
I believe you need a custom recovery like twrp installed to flash a custom ROM. Try using rumrunner or firewater to S-OFF your DNA so that you can install a custom recovery. After that, you should be able to flash this ROM or any other one just fine.
[HTC Droid DNA] stillthisguy:
This is awesome, thanks for all the work. Anyone else not getting the tap and pay option with Google Wallet?
[HTC Droid DNA] stillthisguy:
Texting has been hit or miss, but mostly miss. Have to airplane mode then back it will send one. Then try to send another text it will fail, airplane mode again then it will send.
[HTC Droid DNA] thenaut:
I haven't experienced this. Are you on the latest firmware? Which nightly are you on?
[HTC Droid DNA] stillthisguy:
Phone was on 4.2.2, used rumrunner to unlock and s-off. Flashed 01/19 CM12 yesterday. Had the issue, so I flashed the 4.09 radio, but still persisted. Flashed the 01/20 CM12 through the CMUpdater this morning, still have the issue.
[HTC Droid DNA] JeromeLeung:
Texting has been on point for me. I wonder what's causing this issue for you
[HTC Droid DNA] stillthisguy:
Not sure, I will probably try and flash 01/20 fresh since I seem to be the only one. Any one else use google wallet, has tap to pay never worked for the DNA? Been a long time since I used this phone.
[HTC Droid DNA] thenaut:
The thread where you got the radio, make sure you updated the firmware as well. I'm not saying that's the problem but it may help.
[HTC Droid DNA] stillthisguy:
Would seem strange that hboot would affect this, but I will give it a shot.

---------- Post added at 03:42 PM ---------- Previous post was at 03:27 PM ----------

Didn't help, I am going to DFR first then clean flash if I am still having issues. Seriously no one uses GW?
[HTC Droid DNA] thenaut:
I don't know what those abbreviations mean. Maybe try flashing an older nightly?
[HTC Droid DNA] stillthisguy:
It was supposed to be FDR - Factory Data Reset. That gave me systemui force closes, so I just clean flashed 01/19 again, but still having the issue. I will try an older nightly. GW- google wallet.

---------- Post added at 05:03 PM ---------- Previous post was at 04:14 PM ----------

So the hboot and radio I updated to, from 3.06 to 4.09.605.1. The 4.09.605.1 was not the newest, as I just found 4.09.605.5 and it had a newer radio as well. Just flashed that, and the 01/20 nightly clean. I will report back.
[HTC Droid DNA] jwalkinc:
1-19 Nightly

Just wanted to say that the 1-19 Nightly has been working awesome all day. I had the blank screen during call problem that seemed to crop up on any AOSP Rom. Found the Rezound Proximity fix on another thread and it is working perfectly now.

Other than trying to get my contacts to sync with Facebook profile pics (probably the only Sense feature I miss), the only issue I seem to have is with the overall volume of the speaker when getting a text , ringer, or other sound. It seems lower in output. A minor annoyance and one I suspect is easily fixed.
[HTC Droid DNA] stillthisguy:
Not sure what is wrong with this phone. I have clean flashed 01/14 through 01/20. Send text, it goes through, send another but won't go through until I airplane mode and back. Then can't send another after that until airplane mode again. Tried Google Messenger as well, with the same result. I didn't figure it would matter, but worth a shot. Also, 01/20 the systemui force close when the phone boots to setup wizard. Guess I will find another ROM to use and hope for better results.
[HTC Droid DNA] iHateWebOS:
1/20 build sysui force close for me 2, but skipped set up wizard and all is well. Lots of features added in the 1/20 build.
[HTC Droid DNA] JeromeLeung:
Try haxsync from the play store to sync fb pictures with contacts
[HTC Droid DNA] jwalkinc:
I used to use that

But thought it wasn't working anymore, for some reason. I will give it a go. Thanks!
[HTC Droid DNA] msignor:
Great release. A few flashes and complete wipes later and I have two issues.

- unable to activate the Google keyboard. Getting a FC when I go into input types in settings.

- Bluetooth pairs to Polk speakers, no audio in spotify.

Running the 1/20 build
[HTC Droid DNA] thenaut:
The 1/21 build fixed the google keyboard issue for me.
[HTC Droid DNA] HokieCoder:
This has happened for me, seemingly randomly, using my truck's BT connection and Google Play Music. Resolved the issue quickly by disconnecting the BT connection and reconnecting. Then audio played fine. Does this work for you? EDIT: Ever since I dirty flashed the 1/21 nightly over the 1/11 nightly the BT connection has been only ~10% successful in playing audio. Only once, with a pair of BT headphones, was I able to get it to play audio continuously, but that was also right after a reboot. Have tried it other times and when I start a new song (with Google Play Music) I'll hear a few blips of the audio, but then nothing. GPM keeps on playing, but there is no audio through the speaker nor the BT device.

Anybody else using the stock browser? Two things I hate about it so far: 1.) On the tabs switcher, there is no more "Home" button. If I am on any web page, I have no idea how to get to my Home page using the UI, even though there is still a setting for it in the browser settings. 2.) When loading a page, there doesn't seem to be any UI indication for how much of the page has been loaded. In CM11 there was a blue progress bar under the address bar, but in CM12 it is just a gray bar that, if it is showing progress, isn't contrasted well enough to see what the progress is.
[HTC Droid DNA] IcyAgitator:
Anyway to make the ringer, in-call, and speaker volumes louder? Im using the LolliViper modded with selinux permissive. Hardly a difference.

**Update** i uninstalled viper audio and flashed eXtremeBeats v3. No distortion, volumes & sounds are louder and clear.
[HTC Droid DNA] mobitote:
Dunno if its a bug or not ... But, I was on a call and had to make a quick internet search and my call screen started flashing blue. I did not enable strict mode in dev options. Thot I'd mention incase its a bug or just some new cm12 thing ... "U know pay attention to SO on the phone -- Get off p-hub" :)

---------- Post added at 11:45 PM ---------- Previous post was at 11:35 PM ----------

Also on cm11, there was the option to see what connected tothe phone via portable hotspot. Is that a feature that is being considered in cm12? + as an added bonus it would be especially helpful to add the ability to block any connections.
[HTC Droid DNA] IcyAgitator:
Is it ok to dirty flash the nightly builds?
[HTC Droid DNA] iHateWebOS:
I have with no issues
[HTC Droid DNA] neelgangrade:
Nightly 23rd Jan daily driver

its 99.99 % bug free ! used it for like 2 days, GPS locks in instant, sound quality fantastic, battery is remarkably increased, getting a day full on wifi !

games running fast and smooth, no call issues, nothing !

absolutely fantastic ! :good:

for those who wanna use 5.0.2 as a daily driver, i think u know where to move on !

(i found a small glitch effect which is not even noticeable while sliding from call to recents to contacts, contacts flick for slightest second, though it doesnt affect anything, may be its me)
[HTC Droid DNA] bolus14:
Installed today and so far everything is running without issue, only thing I ran into was I had to install TWRP instead of using CWM, I kept getting a mount error in CWM. SMS, calls, GPS and apper to work with no problems at all. I don't use BT for anything so I can't comment on any of that functionality.
[HTC Droid DNA] msignor:
As mentioned prior, as of 1/22 the google keyboard (input types in general) are working.

Bluetooth is still not working regardless of device that I pair to.

If anyone else is interested, the WiFi feather works great, haven't tested USB teather yet.
[HTC Droid DNA] Hussainally:
Bro can u direct me to extreme beats v3 link please ..appreciate it
[HTC Droid DNA] IcyAgitator:
http://xdaforums.com/showthread.php?t=2634729
[HTC Droid DNA] JeromeLeung:
Extremebeats broke maps for me. Just a warning
[HTC Droid DNA] Hussainally:
Any good recommended kernel for this rom ..I need USB fast charge and to underclock
[HTC Droid DNA] JeromeLeung:
Maybe give [MENTION=5053434]jamiethemorris[/MENTION] ' kernel a try http://xdaforums.com/showthread.php?p=49827024
[HTC Droid DNA] IcyAgitator:
I don't use Google maps. But thanks for the info.
[HTC Droid DNA] JWings:
I am currently running CM-12-20150128-NIGHTLY-dlx and am having issues with Wifi and Bluetooth. From what I've read, it sounds like I will need to roll back to CM-12-20150108-NIGHTLY-dlx to fix my Wifi. Is this true? If so, where can I download it. I have gone to downloads.cyanogenmod.org and they have a link for it - but it's broken. :(

Please help!

Thanks!

JWings
[HTC Droid DNA] Hussainally:
Bro wipe and reinstall ..I am on 28th..its running perfect ..no WiFi or data issues
[HTC Droid DNA] therreid:
How is the Bluetooth working?
[HTC Droid DNA] JWings:
Wiping and re-flashing resolved my Wifi issue. I will test bluetooth tomorrow.

Thanks for the suggestion Hussainally.
[HTC Droid DNA] Hussainally:
Hotspot still doesn't work for me though

---------- Post added at 05:57 AM ---------- Previous post was at 05:57 AM ----------

Bluetooth works fine
[HTC Droid DNA] RBB_2012:
I'm on the 01-26 nightly and hotspot works with CM kernel. Not sure if this is helpful, but the hotspot is broken when using the jamiethemorris kernel.
[HTC Droid DNA] Hussainally:
Tks for the heads up ..I am rocking his kernel ..u may be right
[HTC Droid DNA] HokieCoder:
95% of my Bluetooth issues have been fixed as of the 01/28 nightly. However, I do notice that sometimes the audio skips for a really short interval (few hundred milliseconds), and it seems completely random. But the good news is that it will connect AND play audio now! I have tested with several devices and have had no problems except for the random skips. Have no issues with WiFi either, although I have not yet tested the WiFi Hotspot.
[HTC Droid DNA] iHateWebOS:
Native WiFi tether works with stock kernel only. If you need hotspot then don't use Jamie's kernel until he updates his source.

Edit: oops, this was already posted [emoji15]
[HTC Droid DNA] DarkMD:
Any way to get fast charge on stock CM kernel?
[HTC Droid DNA] mobitote:
Quick question, I have been using SuperSu after I updated to cm12 because titanium backup was not playing nice with cm12's superuser. Are there any plans to make superuser on cm12 more permissive like superSu or are am I going about it all wrong?

It gets old having to reinstall supersu with each nightly ... BTW, love cm12!!!
[HTC Droid DNA] JeromeLeung:
That's bizarre, I don't have superuser at all... Just supersu
[HTC Droid DNA] compuw22c:
Any solution to the wifi issue other than a wipe? Trying to help a friend over the phone (I know...I know...)

Things I know:

BT Works

Wifi mac address in about phone is unavailable

When trying to turn it on, button gets stuck

Any help would be GREATLY appreciated
[HTC Droid DNA] HokieCoder:
Spoke too soon. I am now on the 01/31 nightly and I have discovered that switching between BT devices causes issues. For instance, in the morning I'll connect my phone to my BT speaker at home while I get ready for work. But when I get in my car, my DNA will connect to the car's BT, but I will only hear a split second of the music from GPM. Any amount of disconnecting, pulling the power on my car's BT, turning off/on my phone's BT, etc. won't fix the problem. Only a reboot of my phone will. Same goes from successfully connecting to my car's BT then trying to connect to another device. Not sure why this is happening. However, I have NOT experience the audio skip problem in 01/30 or 01/31.
[HTC Droid DNA] dot45:
I'm in the same boat, but unlimited data so I've been ignoring the problem.

looking at the logicat:

Unable to open connection to supplicant on "/data/system/wpa_supplicant/wlan0": Permission denied

it doesn't seem happy trying to load.
[HTC Droid DNA] HokieCoder:
For the second time now I have seen the pound sign (#) show up in my status bar (see attached image). I have never seen this before and I don't know what I am doing to trigger it. I've tried Google-ing what it is, but I haven't found any mention of it so far. Anyone know what it means?

[IMG="Status Bar"]http://i.imgur.com/l07339d.png[/IMG]

Also, for anyone who is following, I am still having the BT playback problems when switching between BT devices on the 02/03 nightly. A reboot is still required to allow playback to work with the 2nd device.
[HTC Droid DNA] danjull:
Should be super user related. Try going in to cm's super user and toggling it off and on.
[HTC Droid DNA] thenaut:
Its definitely superuser. I've been sideloading it, as it hasn't been updating for me.
[HTC Droid DNA] HokieCoder:
Thanks for the info/suggestions, guys. After some more Google-ing I found that superuser is now built in to CM12 and settings for it are available through Privacy Guard (Settings -> Privacy -> Privacy Guard). After digging around I found, in the Advanced settings for Privacy Guard, that you can see all of the apps that have requested root access. In my case, I had ES File Explorer and Terminal listed. However, ES File Explorer was still listed as "running" (in terms of root access), even though I had switched off root access in the app, closed the app, and even force stopped it. Still, CM thought it was still using root access, hence why the pound sign is still in my status bar. Rebooting made the icon go away. I'm now flashing the 02/04 nightly, so I'll report back after more testing. Could be that it is either a bug in ES File Explorer or CM in terms of how root access is being reported.

EDIT: So far my testing has confirmed my theory. Whenever I "su" in the terminal app, it'll show in the Privacy Guard information that superuser access was granted at a certain time, but it doesn't report as "running" since I exited the su command prompt. However, with ES File Explorer, it seems Privacy Guard never gets the memo that it has stopped using superuser access, even though it can no longer do root-level things. I'm going to see if there is somewhere I can post at Cyanogenmod to find out if this is a CM problem or an ES File Explorer problem.

I also found this CM forum thread about the pound sign. Based on what was said there, I hope there is a future option in the works to "kill root access" for any app that is currently using it. At least that would allow me to remove the icon once ES File Explorer is done with root.
[HTC Droid DNA] DarkMD:
When i have trickster mod (or any app that use root) in the background i get that icon, but when i close all the running apps it go away

Sorry for my bad english
[HTC Droid DNA] mobitote:
What recovery are ppl using?
[HTC Droid DNA] neelgangrade:
any stable nightly after 23th jan 2015 ?

i am on 23rd jan nightly ! and its completely working fine, 99.99 % bug free :D

battery works fine, and everything else too, like bluetooth, gps, wifi !

any other major changes after that !! :cool:
[HTC Droid DNA] Drunkula:
Just installed the 0206 nightly. Looking great so far! I hope this ROM works out for me.
[HTC Droid DNA] Drunkula:
Follow-up:

So far all but one item is not working. Sadly wireless charging is NOT working.

EDIT:

Never mind. Loose connection on the charger!
[HTC Droid DNA] Gr8Jeepin:
Have the connectivity issues with Bluetooth been resolved?
[HTC Droid DNA] Drunkula:
I haven't tried an earpiece but it paired easily with the BT adapter in my car (was able to clear a check-engine code no problem).
[HTC Droid DNA] datoe:
[MENTION=4453465]Drunkula[/MENTION], will you please elaborate on how you clear a check engine code through BT? Was that thru an app? Thx.
[HTC Droid DNA] Drunkula:
The app is called Torque Lite. I bought a Bluetooth elm327 adapter from Amazon. There are many different brands and models.

EDIT:

Torque Lite

ELM327 adapter

The adapter I got costs a little more. There are smaller and cheaper ones but I wanted a proven good one. Also paired to my bt earpiece no problem. Audio was a bit noisy but this earpiece is an old piece o' crap.
[HTC Droid DNA] HokieCoder:
Up through the 2/7 nightly I was still experiencing the issue. But now with the 2/8 it seems I can switch between BT devices with no playback problems whatsoever. Love those CM devs! :good:

EDIT: I am still on the 2/8 nightly and this morning I went to play music through my truck's BT. The connection was successful, as usual, but no audio was played. So it seems that I got lucky with the 3 devices I tested yesterday and that the BT audio playback problem still exists, at least for me.
[HTC Droid DNA] nola5712:
my other phone bit the dust and I had this DNA hanging around...

Flashed this through 2.07 TWRP, and it's an amazing ROM so far. But I am having an issue which begs a separate question. On incoming calls the caller sometimes can't hear me and I can't hear them. On outgoing calls it's every call. But all alerts and ringtones, volume rocker, YouTube, everything plays fine out of the speaker. So my question is, are there 2 different speakers in this phone? One for alerts and one for in call? I thought I remembered seeing a fix for another HTC phone having this problem that worked for another ours but can't find it. Has anyone else experienced this, or have any ideas?

I'm going to reflash maybe with a different GAPPS? and see what happens. Thanks for the ROM though because I am loving everything else :)
[HTC Droid DNA] HokieCoder:
Did you mean TWRP v2.7.X.X? v2.07 or something similar, I don't think, ever existed for the DLX. Anyways, did you dirty flash from another ROM or do a clean flash? And there are two speakers on the phone: one is the "handset earpiece" (what you use during a private call) and the other is the loudspeaker (that you would typically play music over). But for what you mean, no, there is only one speaker. Have you checked that your in-call volume is always at max (or close to it) when you are experiencing the problem? Maybe something is setting the in-call volume low at random times.

Finally, as far as I know, GApps has nothing to do with the phone/dialer app. In other words, the phone/dialer app comes with the ROM, not GApps.
[HTC Droid DNA] nola5712:
Thanks for the reply man. I did replace the screen today too, but the fact that all other sounds are working makes me think I didn't damage anything. Have you heard of anything else causing something like this? I didn't think to check the volume in call because I didn't think by default it'd be muted or anything like that. Plus there isn't even ringing on my end when I call, but the people I called definitely got the call... Ugh..

---------- Post added at 11:58 PM ---------- Previous post was at 11:53 PM ----------

Can I seriously not edit posts here? How have I never noticed that... Either way, I didn't answer your questions. I guess it's the version of TWRP that you're referring to, because honestly I'm not too sure. And No I didn't dirty flash. Wiped all data, then flashed rom, then gapps. Everything else works perfect which is why I'm so confused :(
[HTC Droid DNA] HokieCoder:
Well, since you've done hardware changes to the phone I think it would hard to say because there is no telling what may have happened with the physical connections in the phone. Not trying to say you did mess up your phone, just saying it's a possibility. I've never heard of someone having your problem, so I'm afraid I can't help much further. What I would try is upgrading your TWRP to the latest image (TWRP for DLX), doing a full factory data reset (after backing up, of course), and reinstalling the latest nightly. If that still causes you issues, try flashing back to stock and see if you still experience the same problems. If you do, then it means there is some kind of hardware problem. If everything works fine on stock, then it means your particular phone doesn't like something about the CM12 nightlies. But as for myself, I haven't had any call/speaker issues with these nightlies.
[HTC Droid DNA] nola5712:
Thanks again for the reply man. I just finished a complete factory reset (including wiping my sd card while in recovery by accident [dammit motorola spoiled me on always having an out], resulting in a lengthy adb learning process...). But still, the person I'm calling can hear me, but I can't hear them. I don't hear ringing when I place the call. And all other sounds, anything coming from the speaker works. I'm so beyond frustrated, and ready to go buy a new phone at retail cost just so I can keep my unlimited data, and youtube my destruction of this device...

---------- Post added at 02:53 AM ---------- Previous post was at 02:49 AM ----------

And I know the ultimate test will be trying it on a stock rom, but between installing the screen and now this, I've been at it since 7am on my only day off. My brain is telling me to break this thing into a million pieces at this point... And quite honestly I don't even remember how to bring this phone back to stock. That would be another 1-2 hours of reading before I would even attempt...
[HTC Droid DNA] JeromeLeung:
Somewhere here [MENTION=1331268]santod040[/MENTION] has a really nice thread for stock. If not in this forum then maybe in android development.

As for your earpiece not functioning, the same thing happened to my brother's DNA when he busted the screen and I replaced it for him. If I remember correctly, it was me rushing to close the phone back up and forgetting to fully connect one of the ribbons or cables that caused it. Hopefully you're as lucky as him to not have a broken part. Good luck!
[HTC Droid DNA] nola5712:
Hey thanks for the reply. I'll have to check out the stock rom when I get a chance. Being fairly new to TWRP, is there a way to "dual boot" from different rom slots like Safestrap for Motorolas? So that I wouldn't have to wipe the current install of CM12?

Also thanks for the suggestion on a cable/ribbon being disconnected. But if that were the case wouldn't all other sounds be disabled as well? You don't by any chance remember which one was disconnected do you? Thanks again for the reply, and suggestions.

---------- Post added at 06:23 PM ---------- Previous post was at 06:13 PM ----------

EDIT: oh holy crap, I just read another XDA post that said when you buy a new DNA screen/housing the ear speaker is not included. And I definitely didn't move anything from the old screen/housing to the new one....didn't even cross my mind to check as I wouldn't think the speaker would be attached there. When I get home I will check the broken screen to see if it's still in there. Hopefully that's all it will take! :D
[HTC Droid DNA] HokieCoder:
There are two different speakers, like I mentioned before. The one that isn't working for you, the handset earpiece speaker, is the one you hear the phone conversations through when using the phone normally, located in the red mesh bar at the top of the front screen. The other one, which you can play music through or hear system sounds through when the volume is turned up, is located on the back of the phone near the bottom and is covered with black mesh. That's why you can hear notifications, ringtones, music, etc., but you can't hear those on the other end of the phone calls. Hopefully for you it is that you didn't move the speaker over with the new screen and it'll be a relatively easy fix!