yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] fireforhire:
No, broken speaker phone, barley usable Bluetooth for ADP are just two deal breakers for me.

CM on this phone is complete garbage. The M8 is out, and something as basic as speaker phone is still broken?
[One (M7) Original Android Development] twped:
I use it as a daily driver. Bluetooth works perfectly actually speakerphone I rarely use so that's not a deal breaker for me.

All in all very good I think.
[One (M7) Original Android Development] tiny4579:
Agreed for the most part. Bluetooth a2dp works fine, but AVRCP, particularly metadata, is a bit erratic with my car unit.

There are a couple Bluetooth patches merged in the 4/25 nightly that I'd like to try.

Speakerphone isn't perfect since there are still people with issues, but I've had zero issues with speakerphone

CM isn't quite as smooth as it should be on a phone as fast as the m7 is.
[One (M7) Original Android Development] cschmitt:
It's my daily driver as well, has been for nearly a year.

Sound quality of music played via speakers suffers, but Viper4Android takes care of that. Bluetooth playback is fine, skips occasionally, no big deal. Don't use speakerphone, always handset or headset, so a non-issue. I haven't experienced the other issues mentioned on the wiki.

Even with a few bugs, I stick with CM because of features like themes, quiet hours, customizable notification LED, split notification and ringtone volume, and the many other CM tweaks. Also enjoy doing my own builds and including my own tweaks and enhancements.
[One (M7) Original Android Development] ZaneChua:
How customizable can the notification LED be when there are only 3 colors. >:(
[One (M7) Original Android Development] cschmitt:
3?, there's only 2: green and amber. But it can be set per application to a specific color based on it's importance (at least that's how I use it.)
[One (M7) Original Android Development] ZaneChua:
I thought there was green, amber and red? My imagination?
[One (M7) Original Android Development] adyscorpius:
Speakerphone works sort of fine. You need to hold it closer and point the main mic towards your mouth to make it loud and clear. Yes it doesn't work like a conference phone might work. Bluetooth suffers only with certain implementations but then that is the case without almost every aosp ROM for all phones. Its a grey area I think.
[One (M7) Original Android Development] HjasToneC:
I love cyanogenmod, but somehow this rom drains battery really quickly in standby.

Not only that, the charging speed is noticeably slow...

I've tried both m5 and the nighties, yet I achieve the same result...

Any helps please?
[One (M7) Original Android Development] elherr:
It seems like you bandy the word 'garbage' around quite a bit. While CM11 on the One still needs a bit of work, it is quite usable. By 'ADP' I assume you mean A2DP? It works quite well for me connecting to Miccus Home RTX for streaming music to my stereo. No problems.

eherr@singularity:~$ adb shell logcat -v time | grep A2DP
04-25 17:25:22.637 D/LocalBluetoothProfileManager(32565): Adding local A2DP profile
04-25 17:25:26.651 D/CachedBluetoothDevice(32565): Command sent successfully:CONNECT Address:00:1A:7D:39:08:ED Profile:A2DP
04-25 17:25:26.761 D/LocalBluetoothProfileManager(32565): A2DP state change 0 -> 1
04-25 17:25:26.761 D/CachedBluetoothDevice(32565): onProfileStateChanged: profile A2DP newProfileState 1
04-25 17:25:29.674 D/LocalBluetoothProfileManager(32565): A2DP state change 1 -> 2
04-25 17:25:29.674 D/CachedBluetoothDevice(32565): onProfileStateChanged: profile A2DP newProfileState 2
04-25 17:25:29.684 D/A2dpStateMachine( 1836): A2DP Playing state : device: 00:1A:7D:39:08:ED State:10->11
04-25 17:26:21.144 D/A2dpStateMachine( 1836): A2DP Playing state : device: 00:1A:7D:39:08:ED State:11->10
04-25 17:27:24.776 D/A2dpStateMachine( 1836): A2DP Playing state : device: 00:1A:7D:39:08:ED State:10->11
04-25 17:27:25.186 D/A2dpStateMachine( 1836): A2DP Playing state : device: 00:1A:7D:39:08:ED State:11->10
04-25 17:31:46.041 D/A2dpStateMachine( 1836): A2DP Playing state : device: 00:1A:7D:39:08:ED State:10->11
04-25 17:31:52.427 D/A2dpStateMachine( 1836): A2DP Playing state : device: 00:1A:7D:39:08:ED State:11->10

If you are having problems with Bluetooth, you should think about posting a log instead of posting the word 'garbage' over and over again. CM11 is, after all, still a work in progress.
[One (M7) Original Android Development] tiny4579:
How fast is the fast drain and how slow is the slow charging?

What is draining battery according to bettrrbatterystats, gsm, or wakelock detector? In order for us to help you, we need more information.

You should get 800-1000ma charging rate over a.c. maybe your charger is recognized as a USB charger.
[One (M7) Original Android Development] question.com:
Same here. I steam Bluetooth at the gym for 3 hours and in my car. Never have an issue.
[One (M7) Original Android Development] twped:
I had the same problem for months. I tried to locate it using better battery status but it would never show the true offender. I also used system panel and it would many times show 30-35% processor usage with high CPU load at about 1200mhz but no process was shown to be active. Very frustrating.

Have to say I also had greenify installed and active but no effect.

I ended up with factory reset and reload all apps from scratch 2 days ago.

I have not had any problems so far since. Greenify is not installed. Great battery life and no hidden processes taking up CPU.

... My 2 cents.
[One (M7) Original Android Development] Floyd_Flivercod:
Uninstall the Google crap and you will notice EXTREME battery savings. Hangouts & Now are HOGS and it is not the ROM. I had the same issue until I did this.
[One (M7) Original Android Development] HjasToneC:
So are you recommending factory reset than wipe??
[One (M7) Original Android Development] twped:
Not recommending but that helped me. Most likely because I could not find the offending application.

And I tried to deinstall a lot first without success.
[One (M7) Original Android Development] Eddster3000:
I have made a return to CM ROM after quite a while on Sense ROMs and everything is fine except the clock function.

Does anyone have and solution to "unfortunately, Clock has stopped" ? 25/04 and 27/04 nightly

Totally clean install, wiped absolutely everything!, Using 3.62.1700.1 firmware, no TB app restore, cleared cache and data of Clock and cLock. No MODS what-so-ever, have Dirty Flashed ROM again.

Did a Google search and tried a solution using Terminal Emulator but no luck, If it has been mentioned in the thread before please point me in the right direction.

I don't fancy doing yet another clean install!

EDIT: ended up doing the clean install that I was hoping I didn't have to do and my previous issue is resolved .. just goes to show that the extra effort sorts out the little things!

EDIT 2: found out that it is [*/X/H/M/*] Gem Flat [xIC-MACIx] Theme that is making my clock issue. I have switched back to System Theme and all good. Might need to advise the Dev of the theme but worked out that it isn't the ROM. Seems like I did the re-install for naught GRRRRR!
[One (M7) Original Android Development] pavik62:
Yes. The same problem. Just me "stopped SystemUI" I replaced from from 04.25. SustemUI.apk. Now all is well
[One (M7) Original Android Development] :
From what date is the replaced / new SystemUI.apk :confused:
[One (M7) Original Android Development] tiny4579:
I don't recommend swapping out apks like that, especially systemui. It connects with the framework. You can create new issues doing that. It could be a bad download as I haven't run into any force close issues dirty flashing.
[One (M7) Original Android Development] KaZo58:
on top (notification/quicksetting) left, an analog clock would be nicer instead of smallsized numbers.

Gesendet von meinem One
[One (M7) Original Android Development] tiny4579:
I disagree. An analog clock would not fit well there at all and still be legible, and it's a horrible detour from the rest of the interface. The current digital time at least matches the regular status bar clock.
[One (M7) Original Android Development] sabret00the:
Is there a mod to do what the One Plus One does and switch between capacitive and on screen buttons?
[One (M7) Original Android Development] cschmitt:
It can be done by setting qemu.hw.mainkeys=0 in build.prop to enable nav keys and then disabling capacitive keys in /system/usr/keylayout/synaptics-rmi-touchscreen.kl by commenting out both lines with a #.
[One (M7) Original Android Development] KaZo58:
ignore me. theme is broken. :D

Gesendet von meinem One
[One (M7) Original Android Development] tiny4579:
There's a patch on gerrit that allows toggling it via the but it was only done in testing so it won't make it mainstream in this device, mainly because the soft keys are quite visible.
[One (M7) Original Android Development] elherr:
Wifi died again this morning. Unable to see any wireless access points. On nightly 0427.

Log:

04-28 07:56:01.027 I/wpa_supplicant( 754): wlan0: CTRL-EVENT-DISCONNECTED bssid=64:66:b3:94:4b:08 reason=2
04-28 07:56:01.027 I/wpa_supplicant( 754): wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
04-28 07:56:01.027 I/wpa_supplicant( 754): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Hefeweizen" auth_failures=23 duration=120

dmesg:

<6>[38959.235534] mmc0: mmc_start_bkops: raw_bkops_status=0x1, from_exception=0
<6>[38959.241302] mmc0: mmc_start_bkops: Starting bkops

This appears to happen when I charge phone overnight and battery reaches full charge. The only actions I have found that clear the problem are toggling airplane mode or rebooting.

I've disabled wifi optimization in settings to see if that is related...
[One (M7) Original Android Development] jukiewalsh:
+1
[One (M7) Original Android Development] qkall:
http://xdaforums.com/showthread.php?t=2236121&page=142

teamseven's is considered pretty good (extra features with trickstermod app - including s2w, p2w, dt2w and making the htc logo a button). However, the OP of said thread has gotten busy with life and other projects and it isn't as active as it once was. Although, to be honest, as long as there isn't any major changes in the vanilla kernel it should work fine. I've recently switched back to Cyanogenmod so i haven't installed the teamseven kernel yet. but if memory serves, smartass_esp sometimes has issues with waking from deep sleep so i would stick with smartass/interactive.
[One (M7) Original Android Development] tiny4579:
Problem with custom kernels and cm is that it can lose sync with cm and caf and possibly have major issues.
[One (M7) Original Android Development] fenstre:
Instructions for compiling CM?

I found two sets of instructions for compiling CyanogenMod, but one had references to CM10.2, and the other was even older. I couldn't get a successful build with either. Are there any working instructions? (I'd like to build on OSX, but I can build at home if Linux is preferred).
[One (M7) Original Android Development] Pons:
Not sure where you looked, but the official site is normally the best spot.

http://wiki.cyanogenmod.org/w/Build_for_m7
[One (M7) Original Android Development] cschmitt:
In addition to the offical CM guide, I've found these helpful for understanding repo, gerrit, envsetup, getting adb up and running.

http://xdaforums.com/showthread.php?t=2302780

http://z1gackly.wordpress.com/2012/11/11/how-to-use-repo-github-git-and-gerrit/

http://wiki.cyanogenmod.org/w/Envsetup_help

http://source.android.com/source/using-repo.html

http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk

The official CM guide doesn't discuss updating Make or Python. I'm building on Ubuntu 12.04 LTS and found the Python 2.7.3 works fine but needed to update to make 3.82.
[One (M7) Original Android Development] KaZo58:
Today's build is broken. no service.

after pressing "mobile networks" there are 2 choices. ???
[One (M7) Original Android Development] elherr:
Today's is working for me on T-Mobile in the United States. I'm guessing the separate items are to support multi-SIM phones perhaps?
[One (M7) Original Android Development] KaZo58:
hmm flashed back to 28/04 build. so there are separate items too. didn't notice earlier lol. something changed maybe or it's just my device?

i'll wait for tomorrows build then.
[One (M7) Original Android Development] KillerBeaver:
I have the separate menus but I still have service.
[One (M7) Original Android Development] qkall:
i'm not seeing that issue...
[One (M7) Original Android Development] Alex740il:
Haven't followed AOSP development for a while. Is BT phone and music streaming working properly? Also, has screen wake issue been resolve? Also hows is the camera? Please don't reply "just flash and try it", I don't have time to flash and play around now as I used to... Thanks!
[One (M7) Original Android Development] taylor.fowler:
[MENTION=2150078]KaZo58[/MENTION] logcat -b radio would be helpful for diagnosing that.
[One (M7) Original Android Development] KaZo58:
well flashed it for 3rd time now it works :confused:
[One (M7) Original Android Development] twped:
Working fine here
[One (M7) Original Android Development] tiny4579:
The two selections are due to mobile data settings working for both regular and dual SIM. The top one is what you want unless you want multi SIM.
[One (M7) Original Android Development] cschmitt:
A programming note regarding the upcoming 0501 nightly:

http://wiki.cyanogenmod.org/w/HTC_fstab_updates

A recovery update will be required.
[One (M7) Original Android Development] elherr:
Wow. Thank you! Even with your timely warning, I am sure there will be a number of people using intemperate language after attempting to update.
[One (M7) Original Android Development] twped:
So where can we get it?
[One (M7) Original Android Development] :
There are links to the recoveries on that page

http://wiki.cyanogenmod.org/w/HTC_fstab_updates
[One (M7) Original Android Development] :
Thank you for the important Hint :good:

I'll adjust the OP (# 1) accordingly!
[One (M7) Original Android Development] question.com:
Of course I tried to flash before coming here. Lol.
[One (M7) Original Android Development] subarudroid:
This should be attached to OP:

Recovery Update

Beginning with nightly 20140501, several HTC devices are being transitioned to a new fstab layout. This will not affect your data. This change requires*kernel support*in recovery for CyanogenMod packages to install. Your current recovery is almost guaranteed to not support this change, yet... welcome to bleeding edge!

Affected devices include:

evita - HTC One XLfireball - HTC Droid Incredible 4G LTEjewel - HTC EVO 4G LTEm4 - HTC One Minim7 - HTC One [GSM]m7spr - HTC One [Sprint]m7vzw - HTC One [Verizon]ville - HTC One S

A note to jewel and ville users: This is not the /data/media transition. That change is still being ruled out because there is simply no migration path that preserves data.

All of these recoveries are backwards compatible.

ClockworkMod 6.0.4.8 recoveries*have been built to support this change for the above devices. HTC One (AT&T), HTC One (T-Mobile), and HTC One (non-US GSM) can safely use the recovery entitled "HTC One".

Unofficial TWRP 2.7.0.8 recoveries*have also been generated for these devices. You'll find source code linked on all of those pages. Encourage your favorite recovery maintainer to incorporate "block: by-name" support into their recovery kernels! If there is something drastically wrong with any of these recoveries, please leave a note on*this wiki's discussion page. If a recovery works well for you, you are welcome to share it (and reduce the burden on that poor little web server!).

TeamWin has been notified of the change and the next official recoveries should contain the necessary support.

Troubleshooting

If booting into TWRP 2.7.0.8 causes the TeamWin logo to repeatedly flash without ever reaching the home screen:

Reboot your device to Android: either hold power until the device turns off or use*adb rebootDelete the settings file/sdcard/TWRP/.twrpsReboot back to recovery
[One (M7) Original Android Development] elherr:
Flashed CWM 6.0.4.8 and nightly 0501. It works. Rebooting into CWM 6.0.4.8 seems to take a bit more time, but that might just be my perception.
[One (M7) Original Android Development] :
[MENTION=4138937]subarudroid[/MENTION] (#1477)

take a look 2 Post behind u (#1475) ;)
[One (M7) Original Android Development] subarudroid:
Yes sir. Perhaps that link or the quote from that link. You're doing a great job on this thread HeinzKetchup. Just putting in my two cents :)
[One (M7) Original Android Development] nhugh406:
is anyone having issues with the Play store on the 0501 nightly? the connection keeps timing out.

I've reflashed (clean), cleared app data (play store), removed/readded my google account, wiped cache. nothing... i've flashed the standard 4.4 gapps.

thoughts?
[One (M7) Original Android Development] intervigil:
Just out of curiosity are any users experiencing UI lockups?
[One (M7) Original Android Development] :
No problems here on latest nightly (05/01).
[One (M7) Original Android Development] Trinition:
UI Lockups

I had been experiencing a few anomolies. I was running a nightly from around 4/28 or so (I can't check now because I'm mid-update):

Random freezes in a variety of apps

Homescreen/Launcher rotating to landscape (it never used to do that!)

Car mode spontaneously enabled

Now I happened to flash that nightly the same day I briefly dropped my phone in water. Not sure if my anomolies were from the water, or from the nightly.

---------- Post added at 01:54 PM ---------- Previous post was at 01:50 PM ----------

I flashed CWM 6.0.4.8 Touch first (while running the 20140428 nightly). I rebooted into recovery afterwards to verify it was correct. All looked good.

Then I booted normally, downloaded the 20140501 nightly through the CyanogenMod Updater, and told it to flash.

I'm now sitting at the flash screen with a progress bar that halts at about 20%. The Android Guy is still there with the spinning geometric shape in his belly. This is going on for 10 minutes now.

Uh oh

Any ideas?

UPDATE

RESOLVED! I just set it aside while I did some other things and, when I got back to my phone, it had finished and was rebooting. My GApps were gone (usually they're preserved), but I'm re-flashing those now.
[One (M7) Original Android Development] tiny4579:
Not lockups per se but it does occassionally feel a bit sluggish. Are you checking if turning on barriers could be triggering this?

EDIT: I checked the Gerrit commits. I guess you mean OOM related issues some were seeing.
[One (M7) Original Android Development] tiny4579:
I've seen occasional Play Store issues but I don't think it's related to any particular ROM builds. I've had it probably at least once on every device. If not even a clean flash helps it could be an issue with the Google servers.
[One (M7) Original Android Development] Leebert225:
Voice Dialer

Im seeing the voice dialer pop up again when using the 3.5mm input on today's build. Saw this happen a month or so ago too.
[One (M7) Original Android Development] twped:
How did d you flash the .bin recovery file?
[One (M7) Original Android Development] tiny4579:
Why do you have a .bin file? It's a .img. Check the OP as it has a notice about the new format and links to both TWRP and CWM.

For CWM, you need to download 6.0.4.8 for the general HTC One device (m7, not m7ul, m7att or m7tmo).

For TWRP, make sure you get version 2.7.0.8 for m7.
[One (M7) Original Android Development] twped:
Yes correct its an .img file. My bad.

So how do you install that?
[One (M7) Original Android Development] tiny4579:
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
[One (M7) Original Android Development] twped:
Sorry for being a **** but why couldn't this recovery part if the latest nightly?
[One (M7) Original Android Development] :
[MENTION=5063524]twped[/MENTION]

Flash the recovery with this Tool it is very simple :cowboy:
[One (M7) Original Android Development] twped:
Just what I needed. Thanks a bunch...
[One (M7) Original Android Development] tiny4579:
Roms never include recovery. Plus the nightly needs the updated recovery so you can actually flash it. Plus this is Android. People like different recoveries.

Glad the above tool works.
[One (M7) Original Android Development] sabret00the:
Yes. When the status bar updates, everything locks.
[One (M7) Original Android Development] Trinition:
I used Flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify
[One (M7) Original Android Development] qkall:
So I would take this with a grain of salt but... All I did was delete /twrp/. Twrp flash new recovery via romtoolbox and flashed new rom... I didn't unencrypt although I should of
[One (M7) Original Android Development] cschmitt:
I don't believe anything changed for m7 regarding encryption in the 0501 build, so you're fine.
[One (M7) Original Android Development] fenstre:
Good news: those instructions are more current than the last time I looked.

Medium news: I had to "rm ~/.repoconfig -r" to get rid of a GPG error that was preventing me from pulling some update ("public key not found" error, for key 692B382C).

But to actually get it to build,

I know you already solved this problem, but I'm posting for the sake of others--I had to add an extra entry to .repo/local_manifests/roomservice.xml:

<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-11.0" />

Did I need to manually add this because I had an old .repo directory (I wanted to keep the old blobs from when I built CM10.1), or is this just a hidden bit of lore that can't legally be added to the instructions? And what's the deal with "TheMuppets", anyway?
[One (M7) Original Android Development] gorgo80:
Just a question, 2,7,0,8 is not official not exist on theres homepage http://teamw.in/project/twrp2

So I google and found this, do you think this will work on the htc-one?

http://xdaforums.com/showthread.php?p=52348582

edit, I found this link instead :D http://mdmower.cmphys.com/twrp-m7/ from the wiki page at CM11, http://wiki.cyanogenmod.org/w/HTC_fstab_updates
[One (M7) Original Android Development] Pons:
I personally change my room service to m7.xml that way I can keep track of which device it is. Then other snazzy-device.xml if I'm working on others. Just a personal preference.

And The Muppets contain all the proprietary blobs for the devices. You can either set them up the way you did by adding to a local manifest (preferred because it stays in sync whenever CM updates it) or you can run the vendor setup script if you're already running a recent CM build.

Tl;Dr yes you needed to add that.
[One (M7) Original Android Development] tiny4579:
2.7.0.8 isn't an official build. The teamwin team was notified that an update would be needed though. That's why it's not on the TWRP page and why you had to go to an alternate link for the download. Also, that wiki page you linked has a goo.im download if that one is bogged down.

[MENTION=4513061]cschmitt[/MENTION],

These look good for us for Bluetooth audio stuttering:

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

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