yashsingh1/xdaforums huggingface dataset:
[Sprint HTC One (M7)] dsp4774:
Oh yes, definitely aware on that. I'm doing full wipes here, including /data/media and /system. Looks like the install is working as expected for stock, so if I find that settings aren't sticking, I'm returning this thing.
[Sprint HTC One (M7)] SikYou:
Yea, probably not a bad idea. My One experience has been awesome so far. Rooted, flashed CM10.1, S-Off, customized bootloader all within 1 hour of owning the device and all without a hitch. Amazing devs working this bad boy. Hope the return to stock helps in some way.
[Sprint HTC One (M7)] XaoSilentrzk:
Is there a way to stop your internal SD from being screwed up flashing AOSP? I want to flash CMX, but that issue keeps putting me off

Sent from my HTCONE
[Sprint HTC One (M7)] SikYou:
Its not an "issue" necessarily and your internal SD does not get "screwed up". There is a change in the file structure in Android 4.2.2 so its different than the structure on stock. When you switch over your SD content is there and it is all in the "right" place; the right place just happens to be a different place on Android 4.2.2

To the best of my knowledge there is no way to avoid the changed file structure other than avoid Android 4.2.2
[Sprint HTC One (M7)] ace586:
Any further updates? Reverted to 7/8 after the issues the past few days. Safe to go back to the newest nightlies? Also, any progress on Bluetooth yet? None of the "fixes" seemed to do anything for me.
[Sprint HTC One (M7)] cornelious2:
If the md5 is the same redownloading is pointless
[Sprint HTC One (M7)] chickenfarmer:
I'm on the newest nightly (7/15) and I can confirm that voice, SMS, MMS, 3G and LTE all work well.
[Sprint HTC One (M7)] erethangbagel:
How about bluetooth audio? Having the in call and music streaming work in the car would be sawwweeeeeeet!
[Sprint HTC One (M7)] Phyxs1us:
I haven't checked on the in call audio (although I seem to remember it working in a previous build) but music streaming works.
[Sprint HTC One (M7)] Embluss:
Loving the 7/15 build. Everything seems to be working. One thing I'm wondering - is there a way to get the hardware buttons set up like Sense? I really miss that setup. I can't find a way to set a home button double tap or back button long press action.
[Sprint HTC One (M7)] SikYou:
Settings>system>hardware keys
[Sprint HTC One (M7)] Embluss:
Is there a setting for back button and/or double tap? I just see menu and home long presses atm.
[Sprint HTC One (M7)] flukeSG2:
Don't suppose the dock has been fixed so it works in landscape mode now?
[Sprint HTC One (M7)] Embluss:
Still borked. Didn't notice till you mentioned it.
[Sprint HTC One (M7)] ace586:
Made the jump and updated. My problem is that it still randomly disconnects, and I have to reset Bluetooth on either the car or the phone. Haven't tried to make a call in a while, but a few days ago the recipient claimed they could only hear static. If it can't hold a connection with the headset device, I'm guessing it's still borked.

Haven't taken an incoming call because it keeps disconnecting from the car...

TL;DR: Bluetooth is still utterly useless.
[Sprint HTC One (M7)] erethangbagel:
This was exactly what I wasn't hoping for. Can anybody else confirm that they are having the same issues? Part of me hopes that this is an issue with whatever you are connecting with. Of course, that would be no bueno for you, so the other part of me hopes that's not the case.
[Sprint HTC One (M7)] gmfeny:
I know this has been mentioned but it is a problem. WiFi won't connect to routers with WEP. Changing it to anything else isn't possible bc it's my jobs wireless and it's not a problem on all cm10 devices bc my nexus 10, nexus 7 work fine on it.
[Sprint HTC One (M7)] rougegoat:
Any word on a Wallet fix? I don't pop into the IRC unless I have something to say, so I'm completely unaware of whether they're addressing this or not. It's kind of frustrating to have a supported device on a supported carrier tell me that I can't use it due to unsupported network/device.
[Sprint HTC One (M7)] david279:
Change the device name to HTC one and install modoco toolkit and it works. Google wallet that is...matter of fact I got it working on PA too.
[Sprint HTC One (M7)] rougegoat:
Modoco is an add on. I'm talking about in CM. There is a significant difference between the two.
[Sprint HTC One (M7)] ronnyv21:
I upgraded to the 7/15 build and I noticed a dramatic increase in battery life. I usually have about 10% at the end of the day I had about 43%. Did anyone else notice this?
[Sprint HTC One (M7)] david279:
Right now theres no way your gonna be able to get it running without it. It will just give you the not for your service provided error and never start up. BTW I have used wallet in CM 10.1 and PA.

---------- Post added at 03:09 PM ---------- Previous post was at 03:05 PM ----------

More info here

http://xdaforums.com/showthread.php?t=2340880
[Sprint HTC One (M7)] atroph:
I mentioned that issue a few posts back.

I did some further testing and found these results:

Network setup:

4 WRT54G routers loaded with DD-WRT with 128-bit WEP (will now be know as G routers) all the same SSID etc...

1 MI424WR-GEN3 from Verizon FIOS stock firmware (will now be known as N router) different SSID from the G routers

I have zero connectivity issues connecting to ANY of my G routers using 128-bit WEP

For the N router any WEP settings (64 or 128 bit) will not connect

If I change to anything other than WEP connectivity is fine. Currently it is configure as WPA2/AES
[Sprint HTC One (M7)] rougegoat:
If you'll notice, I commented heavily in that thread. The last post in it was more than two weeks ago, which is a long time in terms of development.
[Sprint HTC One (M7)] Satava:
N doesn't use wep. That's your problem. Try wpa2 for N
[Sprint HTC One (M7)] atroph:
No that is not my problem. It should still associate at 54megs...

All devices on my network worked fine with the N router in "compatability mode" with WEP-128 encryption. This phone is the only one that didn't want to play nice. So it is either CM or the router. I would venture to guess that is CM related since a simple google search shows that multiple platforms have issues connecting to WEP networks for some reason or another.
[Sprint HTC One (M7)] Satava:
If the phone has an N adaptor it will only connect via proper N configuration. Its a CyanogenMod thing not allowing N adaptors to connect to backwards G mode. Use WPA, profit.
[Sprint HTC One (M7)] atroph:
That breaks backwards compatibility, thus does not follow the standard == not correct. It shouldn't matter what type of chip is inside the phone.

I have a few devices that don't support WPA for some reason or another. So if I only had the MI424WR-GEN3 I must configure it to WPA2/AES for it to work with this device? I don't think so.
[Sprint HTC One (M7)] david279:
Wep is broke. I don't think it's gonna get fixed any time soon.
[Sprint HTC One (M7)] afteromega:
Home2 Shortcut on the Play Store lets you assign a program or shortcut to double tap home. You can also set a quick home -> back press to a shortcut too (for example i have double tap home as google now and quick press home then back to set a certain profile from llama). Does add a slight delay depending on what double tap speed you choose though.
[Sprint HTC One (M7)] Satava:
If you have an N antenna and want it to function properly, it needs to be set to WPA. That's the standard. Compatibility mode sets the N network to 2.4ghz band G mode. N will not connect without WPA. If both devices are backwards compatible they connect as a G masked as N. The link speed of the connection isn't related to the security protocol. It's based on the connection protocol and on the number of antennas bound for the link (if N). 802.11n is a protected mode that tries to avoid interference from G and B bands. Coexistence mode is a known issue with 802.11n, and running a router with that setup will typically cause headaches unless you're very lucky with the devices connecting and the router itself.

I too have compatibility issues with older devices not playing nicely with N. Old Nintendo DS, older Canon WiFi Printer, and a few others. My solution was simple, I have a Linksys-Cisco E3000 with two antennas, One set to N 5ghz only, WPA, other set to B/G 2.4ghz WEP. It's virtually a Greenfield within a single device.

I think the issue is the phone sees an N and assumes it's N, even though it's functioning as a G. It probably doesn't help that the phone's chipset is an 802.11ac which in itself is one I don't fully understand yet.

If you have a G antenna (not compatibility mode) WEP might work, at least it did for me on two different cm10.1 devices at a friend's house with an older Linksys router.

Just wait till 802.11ac goes mainstream. That's gonna be a logistical nightmare lol.

TL:DR. If you use an N router, Use WPA. If you use a G router WEP should be ok.
[Sprint HTC One (M7)] rfryar:
Nightlies or special builds?

Sorry for this question, but I have looked back a number of pages in this thread with out an answer.

I am coming from an HTC EVO LTE and deck has an amazing cynaogenmod build that has solved a number of issues recently including random radio drops. 7-16-2013 build.

For the HTC One I installed the 5-13 build from page one and it suffers from the random radio drops that the HTC Evo LTE used to have.

I am wondering what the latest build is? Should I be installing nightlies or is there another more hidden build I should be looking for to get the latest and greatest build for this device?

Thanks for entertaining the n00b question from me.

Rick
[Sprint HTC One (M7)] DatDude123:
Nightlies. The link is in the OP. I'm still on 7-15 because I'm lazy. Others may be using certain nightlies where certain things worked that they needed.

D
[Sprint HTC One (M7)] mqguitar:
I just installed the latest nightly. I was wondering how do i make home button so that double tap home is recent apps and holding home is google now. I tried in hardware keys but that option is not available. Unless there is a way to launch both that I do not know about
[Sprint HTC One (M7)] Gatortribe:
Came here just to say Netflix and Pandora are working like normal once again. Feels good to be on the latests builds again! Although my MMS is still not sending.
[Sprint HTC One (M7)] dxdisaster:
I'm having the exact same SoD issue as described by dsp4774, anyone else?
[Sprint HTC One (M7)] dsp4774:
I had to stay on the stock ROM to actually use the phone. It seems that not enough people are experiencing the issue to consider it an issue as of yet.

It's quite possible that the process of starting from an early nightly and regular flashing of newer ones resolved the issue for many people, but that in no way solves the issue at large.

I would ask someone, anyone willing, really, with a device that is working with a recent nightly to back, do a full wipe (including system), flash, and report. If someone has done that and is not experiencing this issue, then it's probably going to be time to break out the logcats. And do I have logcats...
[Sprint HTC One (M7)] chickenfarmer:
I keep up with the nighties pretty well, but I do a full wipe and flash about once a week and I haven't experienced any of the issues you described.
[Sprint HTC One (M7)] dsp4774:
This is just a sanity check:

*** TAMPERED ***

*** UNLOCKED ***

M7_WLS PVT SHIP S-ON RH

HBOOT-1.44.0000

RADIO-1.00.20.0315

OpenDSP-v26.120.274.0202

eMMC-boot

May 8 2013,16:30:08:-1

Recovery: TWRP 2.5.0.0

Boot to recovery...

Wipe

Swipe to Factory Reset - Done

Back

Advanced Wipe

System - checked

Swipe to Wipe

Home

Install

cm-10.1.20130718-NIGHTLY-m7spr.zip

Add More Zips

gapps-jb-20130301-signed.zip

Swipe to Confirm Flash

Wipe cache/dalvik

Swipe to Wipe

Back

Reboot System

Next phase...

Start

Skip

Skip anyway

Yes

.. [MENTION=652814]gmail[/MENTION].com

******

-right arrow-

OK

-right arrow-

-right arrow-

...almost got to click the finish button that time, but not quite. Screen shut off and stayed that way again. Have to hard reboot to go through the cycle again and again and again.

If anyone else experiences the same thing, we should combine our voices at this point. A solution is out there!
[Sprint HTC One (M7)] chickenfarmer:
That's really weird... Have you tried CWM by any chance? I know a lot of people use TWRP, but I've always had success with CWM and sometimes changing recoveries can fix weird issues.
[Sprint HTC One (M7)] dxdisaster:
I've had the issue both before and after S-OFF, but in any case:

moonshine S-OFF

M7_WLS PVT SHIP S-OFF RH

HBOOT-1.44.4444

RADIO-1.00.20.0315

OpenDSP-v26.120.274.0202

eMMC-boot

May 8 2013,16:30:08:-1

TWRP 2.5.0.0

Advanced Wipe -> Dalvik/Cache/Data/System

Install -> cm-10.1-20130715-NIGHTLY-m7spr.zip (also tested with zip from OP, cm-10.1-20130513-UNOFFICIAL-m7wls.zip, no difference)

No gapps (tested with and without, happens either way)

Reboot to System

Goes strait to homescreen on boot, everything works fine (data, wifi, camera, etc.).

Manually lock phone. When trying to wake, the screen either does not come on, shows a blank screen with the backlight lit or shows the lockscreen scrolling. Sometimes it would crash while waking, sometimes it wouldn't.

For anyone who can make sense out of them, here are multiple logcats from right after sleeping and trying to bring it out from sleep.
[Sprint HTC One (M7)] dsp4774:
I just tried with CWM and had the same results.
[Sprint HTC One (M7)] blakejohnson86:
Any chance either of you two have an MHL cable that you could use to see if it's just the phone's display that turns off?
[Sprint HTC One (M7)] dsp4774:
I've got one at home, I believe. I do know that things will sometimes continue to run while the screen remains blank, as the logcat file will continue to grow. Ultimately, it does stop. I can try to test with MHL tonight as I'm not even going to bother turning this phone on again unless it's for testing or resolution.
[Sprint HTC One (M7)] a13xemz:
Hi just wanted to jump into the group of people experiencing the freeze issue! Happens mainly in chrome
[Sprint HTC One (M7)] dsp4774:
Well this is telling:

I/PowerManagerService(13202): Waking up from sleep...
I/keystore( 214): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
I/keystore( 214): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
D/SurfaceFlinger(13159): Screen acquired, type=0 flinger=0x4134b318
D/qdhwcomposer(13159): hwc_blank: Unblanking display: 0
I/keystore( 214): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
D/qdhwcomposer(13159): hwc_blank: Done unblanking display: 0
D/Surface (13202): Excessive delay in unblankDisplay() while turning screen on: 532ms
D/AccelerometerListener(13465): enable(false)
I/WindowManager(13202): Lock screen displayed!
I/keystore( 214): uid: 1000 action: z -> 7 state: 3 -> 3 retry: 4
I/InputDispatcher(13202): Application is not responding: Window{41dcf728 u0 Keyguard}. It has been 5006.0ms since event, 5005.7ms since wait started. Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
[Sprint HTC One (M7)] JPhantom95:
Somewhere between the 7/2 and 7/15 nightlies, the ability to remove the widget pages from the lockscreen got added! I never used them, so no more annoying flashing on the sides of the screen while unlocking my device!
[Sprint HTC One (M7)] dsp4774:
I spent my evening searching the house for the old MHL adapter. It isn't transmitting video or audio through it, on two different receiving devices.

Does MHL work for anyone else? I feel like I'm getting farther from a solution now.
[Sprint HTC One (M7)] blakejohnson86:
I use a Monoprice MHL with it myself. Works well.
[Sprint HTC One (M7)] dsp4774:
I have no idea the brand. I should clarify though--the MHL adapter does work. I've got a Galaxy Nexus here that we connected to it and it was all peaches and gravy. The HTC One went into landscape mode, but the side buttons (like the app drawer) were not responsive on the device so it could only scroll around the main screens, and it was definitely not sending signal to the HDMI receivers.

Something is either very different about the hardware, or partitions, or something I haven't been able to come up with. I don't do enough of this kind of development to be able to sort this one out on my own.

If we can keep suggestions coming, I'll keep trying things out. This phone is my business phone, but is not critical at this time for usage. I would like nothing more than to solve this mystery, especially for the handful of others that are sharing this issue.
[Sprint HTC One (M7)] snake4812:
I feel so stupid for buying this phone, I just can't believe it seems like we will never get a stable CM. I am on the verge of going back to my Epic 4G touch because I'm so sick of Sense.

Unbelievable
[Sprint HTC One (M7)] HTC_M7:
I love sense 5. CM is very stable for the ONE. Its been running awsome compared to the e4gt. The one actually has normal battery life. What issues have u been having??
[Sprint HTC One (M7)] blakejohnson86:
To be fair, I would have to say you are being overly critical. Coming from an Evo 3D, which _never_ had a stable CM port, I just used the unofficial ones that were stable enough for everyday use. Also, I have to say that Sense on the One looks a lot better than what it use to look like.

The way you are complaining here sounds like you are paying the CM developers to get it working on your phone. They can only develop for the equipment they have. If you want to return your nice phone because you are not willing to wait for the bugs to be fixed, you probably should not be using CM anyway. Especially a non-stable build.

Please, nobody wants to listen to people rant. If you have anything useful for development or to help others with this build, then feel free. Don't waste other people's time.
[Sprint HTC One (M7)] HTC_M7:
Btw to those that are seeing issues with screen wake heres you ish

11:19:24.552 Debug qdhwcomposer 211 hwc_blank: Done unblanking display: 0

11:19:24.552 Debug Surface 653 Excessive delay in unblankDisplay() while turning screen on: 518ms

Your having issues with qdhwcomposer. Most likely it needs to be updated in sources or its prolly fixed in nightlies as nightlies have been great lately. If u know what ur doing try pulling hwcomposers maybe from other aosp but just a guess. Thats the log.
[Sprint HTC One (M7)] gmfeny:
Lol...
[Sprint HTC One (M7)] dsp4774:
I've been using the latest CM nightlies--are there other, more up-to-date nightlies I would want to know about? So far, everything based on AOSP has had this issue for me.
[Sprint HTC One (M7)] dsp4774:
Ok, good morning, and here we go!

https://jira.cyanogenmod.org/browse/CYAN-1734

I will try to update here if I get updates about this in my inbox. Until then...

---------- Post added at 11:30 AM ---------- Previous post was at 10:30 AM ----------

Ick, sorry to reply to myself in the thread. I forgot that they don't take bug requests on nightlies. If I can't report this as a bug, and I can't solve it myself, then there's nothing left to be done.

But you know, I am really bothered that they won't take a bug report on a nightly. How else are we supposed to help with the development? Is CM starting to be a bit too walled off?
[Sprint HTC One (M7)] atroph:
I wonder if there are subtle difference in the hardware with the devices that are stable, and the devices that are not. Obviously the code is the same between the two if we are using the latest nightlies.

So that leaves two things left.

1. Hardware - possibly a different memory chip, different batch, etc...

2. Custom apps - This one is important. For the folks that are having the SoD issue they must be on a completely clean install (ROM and gapps) with no other custom apps, launchers, etc, installed. If SoD persists then see 1.

There was an issue with the Motorola Photon a while back. Some would OC to 1.4 GHz fine and some would only be stable at 1.3GHz. Turns out that there were two different memory chips used in the phone and that was causing the issue. Both RAM chip configurations would be fine at stock 1.0GHz but once you turned up the clock the differences would then become apparent.

cat /sys/ram/info would give us the chip identifier in gingerbread. Not sure how to do it in JB.
[Sprint HTC One (M7)] Gatortribe:
On the 7/19 build my One got very hot (127°F/53°C) and the battery began dropping 3x faster than normal. I had to shut it off due to the heat, the back hurt to touch. Anyone else having this problem?
[Sprint HTC One (M7)] chickenfarmer:
Did you try going back to an older nightly? And did it fix the problem?
[Sprint HTC One (M7)] Gatortribe:
I haven't. I'm seeing if it was a one time thing first, but my phone is warm at the moment so I most likely will revert.
[Sprint HTC One (M7)] JPhantom95:
On the 7/15 nightly my phone is having a hard time finding me. It knows my general location but always marks me as far from where I actually am. Is anyone else experiencing this problem? I'm going to go back to stock and get a GPS lock to try and remedy this.

EDIT: It's happening even on stock. Something must be screwed up with my nearest cell tower.
[Sprint HTC One (M7)] a13xemz:
I had the same problem 3 times with different phones ... Your battery is fried

While it still works I recommended you put it on stock relock s-on and call HTC ... Unless u want to wait for it to not even boot
[Sprint HTC One (M7)] javi_06:
Not necessarily. Same happened to me. Went back to a sense rom and battery is back to normal. Try that before you assume the worst.
[Sprint HTC One (M7)] flukeSG2:
Anyone else find the changes made the the proximity sensor a while back to be annoying? It seems if I move the phone 2mm away from my ear now the screen turns on. Not only does the screen turn on, but because I press my ear to the phone it opens up apps on my home screen, like my alarm clock or the stop watch feature. I think it's way to sensitive. In fact, I don't know why anything was ever changed about it, it seemed perfect before these changes where made.
[Sprint HTC One (M7)] :
Are you being serious? The nightlies are perfectly fine to run as a daily driver.
[Sprint HTC One (M7)] ggoomani:
I guess everybody can have variety of experiences depending on individual preferences in setting up the phone. But I have had good luck with new nightlies for past 2 months as daily driver.
[Sprint HTC One (M7)] ace586:
I think I may have partially figured out the issues with Bluetooth. It seems like the Bluetooth connection cuts out whenever the phone loses network connectivity. If I'm driving in an area that consistently has 4 bars, I have no issues. However, the second the display drops to 0, I'm back to no Bluetooth connection. I know there was an issue with switching between wifi and cell service which was supposedly fixed in an earlier nightly (and I remember experiencing that issue as well, since my phone is still in range of my home wifi when I start my car), and I wonder if this is another aspect of the same issue.

Any thoughts or experiences on this?
[Sprint HTC One (M7)] Embluss:
So Cyanogenmod posted a teaser for something big. Very mysterious, though. "A New Challenger Appears, A New Nemesis Appears"" http://feedly.com/k/13LXpYz

That's an Android Police piece on it. Anyone got a clue?
[Sprint HTC One (M7)] rougegoat:
They've never taken bug reports on nightlies as there is no code review on each nightly(as opposed to Monthlies, RC, and full releases) and there are expected to be bugs in nightlies. Most of the time they're already aware of what is happening in the nightlies and the next one is already fixing it. The nightlies just update too often for bug reports to be useful.

It's hard to say that by doing the exact same thing they've been doing for quite a while that they're suddenly becoming walled off.
[Sprint HTC One (M7)] dsp4774:
Never said the walled off bit was sudden. Really don't care about that.

I think if there was awareness about a bug that rendered a device useless it would probably be addressed pretty quickly. I don't think they are aware of this, and without a way to file a bug, how do we tell them? How do we help instead of banter impotently in a xda thread?
[Sprint HTC One (M7)] SikYou:
Landscape dock fixed! Thanks to whom ever committed that change.