yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] peestandingup:
I've noticed an extended camera settings now (it may have been there before but never noticed it) where you can set the camera quality. Seems there's a few options for upping the quality "superfine" & also "100% jpeg". I dont know if there's any real difference in those two, but upon testing the "100% jpeg" option produces larger file sizes just FYI for anyone curious.

How that translates in actual quality of the real world isn't known yet.
[One (M7) Original Android Development] mawxzz:
googleplay missing from the last nightly ?
[One (M7) Original Android Development] tiny4579:
Google apps are not part of cm builds. Your issue is probably gapps related. Which one did you flash?
[One (M7) Original Android Development] mawxzz:
i flashed the last one,

it used to work on the 24 nightly update

but after 25 i can't find the googleplay store on my phone,

everything else with gaps working fine

just downloaded play store apk, install it, and it works fine :)
[One (M7) Original Android Development] mawxzz:
try go to settings then sound

click on volumes , and uncheck link ringtone & notifications volumes,

then rise the notification sound, it works for me :)
[One (M7) Original Android Development] peestandingup:
Thanks! That seems to have work. Looks like the linking of ringtone & notification volume isn't working in these nightlies.

Yep. Just got one. Its a soft reboot.
[One (M7) Original Android Development] Ciebiada:
The front facing camera shoots upside down when video calling through hangouts, but works fine in camera app. Can you guys confirm?
[One (M7) Original Android Development] robt772000:
What's everyone's opinion of the speaker sound? I'm finding distorsion at full volume. Is it as loud as a gpe/sense ROM?
[One (M7) Original Android Development] tiny4579:
I'm able to talk on speakerphone normally with CM10.2. If I had an issue, I wouldn't have been wondering why people have this problem. I talked at a normal volume through speaker phone and the call went through normally. I've tested the other scenario as well. I had the phone on my shoulder and they could still hear me. I also had my hand near the rear mic and the other person could still hear me.

Maybe it's a calibration problem similar to the proximity sensor issue from the earlier CM days.
[One (M7) Original Android Development] xetrev:
What 10.2 version?

Try this. Take an incoming call or place a call and hit speaker as soon as you can and see if that triggers it.

I had a friend try stable and he has the same issue
[One (M7) Original Android Development] cschmitt:
I've found the speakerphone to be decent in later 10.2 builds and all 11.0 builds, although I don't use it more than a couple times a week because it's difficult to be on speaker with conference calls for work. My One is on latest GPE firmware and is one of the earliest ATT phones, got it on launch day. Is it possible that DSP firmware or the microphone hardware has some effect on how well it works?
[One (M7) Original Android Development] sabret00the:
Are you running the M7ul?
[One (M7) Original Android Development] xetrev:
I have tried every 4.4 aosp and speaker is broken in everyone except gpe/sense.
[One (M7) Original Android Development] sabret00the:
It's broken for me too. In fact a lot people have confirmed it broken than working.

Fundamental features of a phone should be considered critical bugs, but we have no maintainer to fix them.

If in fact it's a problem on other ROMs, it's likely to be a driver/HAL issue and those ROMs are likely using the CM parts to power our device.
[One (M7) Original Android Development] tiny4579:
I am on stable. I called my brother and put him on speaker as soon as he answered and he could still hear me. What channel were you trying to reach the maintainers on? The HTC channel or the general CM dev one?

I don't blame you for being frustrated and I'm glad you're trying to help fix it and not just complaining.

This wasn't an issue forever was it? Like it started during the development phase before stable released but wasn't a problem say in October?
[One (M7) Original Android Development] xetrev:
mdmowers fix got put in on 11/24 and that helped out but there still is an issue. Prior to that it was broken in any of the November builds.

I can't speak to October builds because I was running evita then.

I talked to intervigil and he said he will look at it in a week or so when he gets back home. He has an idea of what the problem is already.
[One (M7) Original Android Development] :
For me the Speaker Phones/Micro during a call are working well,all the Time,

25/Nightly - Stock Kernel, before flashing the ROM i do a Full Wipe.
[One (M7) Original Android Development] xetrev:
were you talking to someone or just listening to a voicemail?
[One (M7) Original Android Development] pnut22r:
Is there a recommended firmware to run with this?
[One (M7) Original Android Development] formula84:
What is you issue with speaker phone, is it the speaker or mic quality?
[One (M7) Original Android Development] Sinistersky:
but is it merged with 2/20? :D
[One (M7) Original Android Development] psychomaniac189:
You prolly already know this, but the screen on delay in the latest nightly is GONE! 20140221.zip
[One (M7) Original Android Development] cschmitt:
It is last_kmsg from attempt to reboot into recovery. I think that's the issue, modem is crashing when it's attempting to reboot into recovery, so it simply reboots.

Here are two last_kmsg, one from m7 kernel which shows a graceful shutdown/restart to recovery sequence, and one from msm8960 with modem crash, kernel panic, and reboot.

Only difference in building with m7 vs msm8960 kernel.

Modem is 4A.23.3263.28, recovery is TWRP 2.6.3.4.
[One (M7) Original Android Development] Hedi86:
2102 didn't Boot...

2002 Boot

wait for 2202 ^^
[One (M7) Original Android Development] elherr:
It's booting for me. HBoot 1.44.0000
[One (M7) Original Android Development] tiny4579:
Logcat would help. For me it was an audioflinger crash. I flashed a manual build this morning but nothing changed since the nightly to cause this. It in theory should work for everyone or no one. Not working for some and not others. That is weird.
[One (M7) Original Android Development] leo_cheng:
can I use the M7 rom for my att htc one? there is still no Milestone 3 on att htc one version?
[One (M7) Original Android Development] tiny4579:
The gsm devices have been combined hence the m7 name now instead of m7ul. So yes. And there won't be a milestone 3 for att since m7 is now for all gsm.
[One (M7) Original Android Development] sabret00the:
So 21 wouldn't boot and there doesn't seem to be any blackouts in 22

---------- Post added at 09:58 AM ---------- Previous post was at 09:17 AM ----------

Is it just me or does updating a keyboard disable it?
[One (M7) Original Android Development] flojho01:
Had the same problem. A clean install resolves it.
[One (M7) Original Android Development] Hedi86:
20142020 - Boots with ART

20142022 - Boot with Dalvic

20142022 - Don't Boot with ART

All test with a clean install
[One (M7) Original Android Development] XxJibblesxX:
Yep i had the same problem. ART didnt work with 20140222 but im using it dalvik as a daily driver and its great :highfive:
[One (M7) Original Android Development] tiny4579:
I had a modem crash at random this morning.

Is there anything that can be done about these modem crashes?
[One (M7) Original Android Development] tiny4579:
This is what broke ART:

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

And this should fix it:

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

Also, to those with issues with 2/21, I didn't see any changes that would have fixed it in 2/22.
[One (M7) Original Android Development] tiny4579:
This seems to be the cause of my bootloops on recent builds from the current repo:

E/MonoPipe( 1133): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
F/libc ( 1133): Fatal signal 7 (SIGBUS) at 0x00000007 (code=1), thread 1133 (mediaserver)
I/DEBUG ( 198): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 198): Build fingerprint: 'htc/m7_google/m7:4.4.2/KOT49H.H1/288144:user/release-keys'
I/DEBUG ( 198): Revision: '128'
I/DEBUG ( 198): pid: 1133, tid: 1133, name: mediaserver >>> /system/bin/mediaserver <<<
I/DEBUG ( 198): signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 00000007

It happens during the starting up apps phase of the boot and won't go past it.
[One (M7) Original Android Development] sronweb:
I'm considering to buy the dual sim version of HTC One. It is this rom compatible with it? Thanks
[One (M7) Original Android Development] AJ:
what happened to fonts , Arabic language fonts became very tiny , english seems ok
[One (M7) Original Android Development] and234:
Man, i'm done with Cyanogenmod! :mad: Was great to be among you guys
[One (M7) Original Android Development] biglo:
I gave up a long time ago as well. There never seems to be a real stable version until a new version of android is released and nobody even wants it anymore because its still has glitches. Seems like cyanogenmod has now turned into a nightly/beta rom only now.
[One (M7) Original Android Development] tiny4579:
This phone has been the trickiest to get audio right that I've used and the active maintainers don't use xda that much. Also I know Intervigil also supports multiple other devices. I keep trying cm but might have to wait till near cm11 final to make it a daily.

There aren't that many major issues right now but enough to make it not suitable for all. They're called nightlies for a reason. And m2 is pretty reliable, just has some minor issues.
[One (M7) Original Android Development] sabret00the:
Anyone else seeing dropped calls?
[One (M7) Original Android Development] Spoofy:
Whats wrong with M3? I've been using it as a daily driver with no issues.
[One (M7) Original Android Development] sabret00the:
I see WiFi AP WPA2 doesn't work. That's another for the list.

Anyone tested the latest build with ART?
[One (M7) Original Android Development] tiny4579:
It still has Bluetooth streaming issues. Occasionally the audio will start at a quiet volume and won't fix itself until the next track. I can't think of anything else other than not as good battery life. It's not bad as Dar as builds go. I'd been spoiled by stuff working on my galaxy nexus without issue.

Oh and there's the avrcp 1.3 not working. That's common to all devices though.
[One (M7) Original Android Development] tiny4579:
But tethering works with regular wpa right?

The art fix was merged after the 2/2 nightly according to cmxlog. Not sure it made it in yet.
[One (M7) Original Android Development] qixiixiq:
BT issues

Bluetooth streaming seems to work perfectly fine for me on the 2/21 build. The only bluetooth issue ive been having is that when i turn on bluetooth via the phone after i turn on the headset the call audio is directed to the phone speakers even though the BT connection indicator on the status bar shows a connected device.

If i turn BT on on the phone and then turn on the headset all calls work fine.

As a sidenote when initiating calls via the ok google hotword the phone power cycles just before the dialer opens.
[One (M7) Original Android Development] tiny4579:
For me it's just the volume problem.

I leave BT on all the time since I have a pebble watch so I don't see that problem and I only use my car for BT calls.
[One (M7) Original Android Development] tjsooley:
FYI swithcing to art causes a boot loop.

P.S. I know art is not supported just a fyi to people thinking of trying it.
[One (M7) Original Android Development] tiny4579:
It's been broken for a few days. It should work again in the next nightly.
[One (M7) Original Android Development] sabret00the:
All sounds ceased to function earlier. I was forced to reboot to restore it.
[One (M7) Original Android Development] PureLife90:
Somebody had mentioned that art will be fixed on next nightly. Somebody test this by any chance?
[One (M7) Original Android Development] tiny4579:
The next nightly isn't out yet. Only if you self build can you test it as the change was just merged today. It was I who said this literally two posts before yours.
[One (M7) Original Android Development] PureLife90:
What kernel is everybody using or recommend?
[One (M7) Original Android Development] sabret00the:
Anybody noticing freezing when playing the game Fives? It doesn't happen on another device.

Also my spellchecker seems to have stopped working.

Last but not least and slightly off topic, anyone noticed a problem with their USB port?
[One (M7) Original Android Development] tjsooley:
Just tried on newest nightly and no ART still broken
[One (M7) Original Android Development] sabret00the:
The ART fix was definitely included. Guess the problem is a little deeper.
[One (M7) Original Android Development] frogger72:
Hmmm.. I'm back in business on ART , Feb 25th nightly.
[One (M7) Original Android Development] question.com:
I don't have any issues steaming via bluetooth. I steam daily at the gym via headphones and I'm my car through my head unit
[One (M7) Original Android Development] Sinistersky:
is ti just me or is ART really fast? :o also, is there a way for me to get swipe to unlock, or tap to unlock on the current kernel, original kernel?
[One (M7) Original Android Development] DarkRazorZ:
It is a lot faster and more responsive to me than dalvik. Also can confirm ART is working in the latest nightly.
[One (M7) Original Android Development] fireforhire:
Speakerphone still broken?
[One (M7) Original Android Development] sabret00the:
I flashed the GPE firmware and that mitigated the problem. There's a few issues like mic volume being too low, oh and a crackling issue (which is solved by muting and unmuting the mic) but it's certainly usable. AFAIK it's still absolutely broken with Sense firmware though.
[One (M7) Original Android Development] tiny4579:
Hey, can you try the m7ul philz recovery (latest build) and see if it has the same issue with the msm8960 kernel? It uses the stock HTC kernel so I wonder if this would make any difference. It's worth a shot at least.
[One (M7) Original Android Development] cschmitt:
I'm fairly certain its a kernel and not a recovery issue.

As an example, I've been building TWRP 2.6.3.4 as my recovery and have experimented with building it using the m7 vs msm8960 kernel.

If built with m7 kernel it works fine, but if built with msm8960 kernel -- boot into TWRP, and select Reboot - Recovery it does the same thing, crashes and boots into OS (instead of back into recovery.)

With CM, I've tried my home built TWRP, stock TWRP 2.6.3.4, stock CWM 6.0.4.6, and it makes no difference. If I'm on CM with the msm8960 kernel reboot recovery fails, but on any build using the m7 kernel it works every time.

Honestly, I'm tired of messing with it and am sticking with the m7 kernel. The msm8960 kernel has issues with reboot recovery and bootloader, and a weird brightness issue on wake (screen is dim and gradually brightens over a few seconds), but at least the wake lag has been fixed. The m7 kernel seems to be much more stable, which is probably why M3 is built with it.
[One (M7) Original Android Development] tiny4579:
In case anyone wants to try, here is a build with an attempted fix for the speakerphone issue that some are seeing.

http://goo.im/devs/tiny4579/m7/cm11.0/cm-11-20140226-UNOFFICIAL-m7.zip
[One (M7) Original Android Development] gr4p3s:
Ever since the "fix" for volume button wake a month or so ago, I haven't been able to get it to work. **** the fix, please revert it.
[One (M7) Original Android Development] tiny4579:
Even though the fix does the same exact thing as manually setting it, you think this is the issue. Has this been broken with the m7 or just the new kernel?

And try this, double tap vol button and it seems to work more reliably. I doubt this being the fix but rather a picky device not wanting to wake up reliably with volume wake.

But that's not what you wanted to hear.

I'll have to try a test build with this reverted when I have more energy, maybe tomorrow. Unless someone else wants to try. All the fix does is write a value to /sys/keyboard/vol_wakeup at boot which is the same thing as setting in init.d or manually, so a quick ramdisk update to remove that would revert this "fix".
[One (M7) Original Android Development] gr4p3s:
Volume to wake didn't work in the nightlies before M3, then worked on M3, and now it doesn't work (my first nightly since M3). So I assume it has to do with the kernel.

I've tried changing /sys/keyboard/vol_wakeup to 0 then to 1 to see if that might work (used to do thine fore the "fix"), but I can't even change it to 0. No matter what, it stays 1 (even if I toggle the option in Settings - Buttons).
[One (M7) Original Android Development] PureLife90:
the only problem i saw was when i was using Ventrilo on my phone and had my headphones in, the audio still played through the speakerphone and i couldnt hear them through the headphones. seems to be that the headphones are broken period because they could barely hear me. i know for a fact that it's not the headphones because i switched back to stock and they could hear me just fine and i could hear them just fine when i had the same headphones plugged into the phone... maybe this is just something i'm doing wrong... if i could get some input on it that would be greatly appreciated. thank you in advance :)
[One (M7) Original Android Development] sectorek:
Yesterday I flashed CM11. Everything is working great except one thing. When I want to send MMS 'mobile data' is not turning automatically ON, I have to turn it manually. Any idea why?
[One (M7) Original Android Development] sabret00the:
That's always been the case with AOSP hasn't it?
[One (M7) Original Android Development] sectorek:
DUNNO! MMS messaging was working OK on early CM 10.2 version if I'm not mistaken.
[One (M7) Original Android Development] pechano:
I use Textra for messaging and it has an option to automatically turn on data whenever you want to send an MMS. I will say that it works about 90% of the time. So I can maybe recommend getting a texting app that supports it. That's what did it for me at least.
[One (M7) Original Android Development] dc66:
Blocked without ROM/zip on phone

Hi

I am new with HTC One. Had CMx.x many months on Galaxy S2.

I wnated to install CM 11 on my m7 and ended up with only having TWRP 2.6.3.4, but without any OS nor zip file on the internal sdcard.

How can I install CM11.zip on the m7? In recovery mode, adb is not working (no device listed). Only fastboot is working. Is there a way to copy CM11.zip on the phone using fastboot?

I have searched within many threads. The only thing I found was about flashing boot.img (from CM11.zip) using fastboot. But this did not bring me further.

Thanks for the support
[One (M7) Original Android Development] Xyleme:
You can try to flash it from a USB stick using an OTG cable.

Last time I did a format of my SD card and did not manage to sideload the rom using adb... Still don't know why. But I know I manage to flash with TWRP and OTG cable.
[One (M7) Original Android Development] dc66:
Thanks. I do not have such a cable... Any other idea?

Is it normal that adb is not working in recovery mode or do I have another issue somewhere?
[One (M7) Original Android Development] Xyleme:
Lol, same for me...

Last time as I was stuck on recovery, sideload not working, I ran to a shop to buy such a cable (6€ at the supermarket here in france)...

Don't have any other trick to help you...
[One (M7) Original Android Development] tiny4579:
What OS are you running? In Windows it's usually driver related. In Linux and maybe OSX (I don't have OSX), it sounds related to udev.
[One (M7) Original Android Development] dc66:
Windows 8
[One (M7) Original Android Development] sabret00the:
Is the call waiting notification not working on all CyanogenMod or is it just our device? It states "call waiting" while in a call but not while dialing. Which is sadly the most important one.
[One (M7) Original Android Development] radzuky:
That's a driver issue. Reinstall drivers for your phone in Windows. ADB works in recovery. ADB Push feature has been my best friend for so long.
[One (M7) Original Android Development] dc66:
Thanks. Tried to resinstall, but still not working... Do you have a link to the exact driver I should install for W8.1?
[One (M7) Original Android Development] radzuky:
Weird, I just installed this http://xdaforums.com/showthread.php?p=42407269 in to my computer at work. It's a new computer so I have never connected my phone to it. After the installation I ADB in to my phone and worked. So, I "ADB Reboot Recovery" and it rebooted to recovery. Than I "ADB devices" and it showed my phone.

I am running Windows 7 64bit. I did not install any driver except ADB/Fastboot from the link provided. I don't know what else to say.
[One (M7) Original Android Development] sectorek:
Cheers man, but still when you want to receive MMS you have to turn on Mobile Data :( so it's solving only 50% of my problem...
[One (M7) Original Android Development] qixiixiq:
art vs dalvik

I was just wondering if anyone has run benchmarks to compare art and dalvik - as of now art is running smoothly but I was curious about how they really compare.
[One (M7) Original Android Development] sabret00the:
Go to AndroidPolice.com
[One (M7) Original Android Development] dc66:
Thanks, but still having issue...

In fastboot mode, the phone is recognized as an "Android USB Devices" and fastboot is working properly. But in TWRP mode, the phone is not recognized properly anymore by Windows (listed in other devices). So it is a kind of driver issue, but only in recovery mode... Any idea? I will anyway try to find an USB OTG cable.
[One (M7) Original Android Development] dc66:
Finally got it to work... I tried reinstalling, manually pointing to the the right drivers (extracted them manually) until phone was also correctly seen by Windows, also in TWRP mode and not only in fastboot mode. Still not fully sure what/why it did not work properly without those manipulations.

Thanks all for your support!
[One (M7) Original Android Development] qixiixiq:
On a side note, after enabling ART I stopped getting notifications from gmail until I cleared app data. I had to clear app data from a number of apps to get them to stop acting quirky after the switch.
[One (M7) Original Android Development] tibere86:
Which camera are people using with CM11? Google's or CM11? I saw a bunch of camera commits a few days ago.
[One (M7) Original Android Development] sabret00the:
I'm getting a tremendous amount of restarts. Seems to happen when receiving a call.
[One (M7) Original Android Development] :
Me 2 :(

Today I installed since a long Time CM11 ( 20140227 ), i do an absolutely clean Flash,

i am getting a tremendous amount of restarts while configuration of the System...
[One (M7) Original Android Development] Spoofy:
A simple build.prop edit fixes it.

---------- Post added at 09:15 AM ---------- Previous post was at 09:11 AM ----------

Do you know if it was working in M3?
[One (M7) Original Android Development] tiny4579:
I believe it was. It was just a week ago where art was broken and m3 was built about two weeks ago on the stable branch.
[One (M7) Original Android Development] KaZo58:
is there cm11's own camera app or it's just google's stock camera app? i have Android 4.4.2 Camera v2.0.002 (937116-30).

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] Spoofy:
So far so good, using teamseven CPUQUIET kernel & TWRP recovery.

0 day Gapps from http://xdaforums.com/showthread.php?t=2397942