yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Blash85:
The updater of the installer version isn't configurable, it should automatically download all stable version, and snapshots are considered like that.
[One (M7) Original Android Development] tiny4579:
Oh you mean the cm installer separate from the Rom? No I don't have any experience with that. The in Rom updater supports what you need though.
[One (M7) Original Android Development] Xyleme:
I'm running Omnirom but got almost the same bug (and used to have it on cm10). When calling with loudspeaker on, the person on the other end hear me but with a lot of noise (like if i was in a car with full open windows on the highway...).

Something that work is to edit build.prop and change the item "persist.audio.handset.mic" from "digital" to "analog" and then reboot !

You'll have to do that every time you flash a new nightly. That work for me on omnirom.

(I'm not a developper, just found that tip somewhere on xda. in CM10 thread maybe...)
[One (M7) Original Android Development] tiny4579:
Did you update your firmware? I hear it helps with the issue.
[One (M7) Original Android Development] ullasmanju:
Yea , same thing happened to me also . Also i got a lot of trebuchet force closes at first .
[One (M7) Original Android Development] Xyleme:
I'm on that firmware :

(bootloader) version-main: 4.06.1540.2

D'you think I should update to that one : 4.19.401.8 ?
[One (M7) Original Android Development] tiny4579:
Either that or the GPE firmware. That is the dev edition firmware you have. Did it have an adsp.img in it?
[One (M7) Original Android Development] jasalta387:
this one has the adsp.img http://xdaforums.com/showpost.php?p=43192909&postcount=3 It's based on latest GPE firmware. Be aware of a ROM re-flash after the RUU flash.

I have the firmware given in that post and even though I claimed the speakerphone issues were gone, I have to say that this is not completely true. Sometimes it runs fine, some other times not at all.
[One (M7) Original Android Development] Glamsen:
Battery life on 0902 is really bad for me, bit more than half day, after clean flash. Any better with m3?
[One (M7) Original Android Development] tiny4579:
Cm sucks with battery in general on this device. I've never had great battery and it might be partially due to the max frequency bias as compared to sense/GPE. But I keep coming back for one reason or another since I miss cm.
[One (M7) Original Android Development] parabelumm:
For me cm11M3 battery life perfect.
[One (M7) Original Android Development] xero110:
I'm also getting very good battery life out of CM. I'm running n3ocort3x's kernel though. I use 81-1566MHz with smartmax.
[One (M7) Original Android Development] dave328:
Anyone have the Uber app working on this ROM? Love CM and features but UBER keeps crashing on app startup
[One (M7) Original Android Development] question.com:
Looks like booting into recovery is broken again. It was fine using the snapshot.
[One (M7) Original Android Development] xero110:
Works for me on 2-12.

Is there a way of getting the overflow option back, for removing the 3 dot menu? Early CM11 and CM10.2 had this option and now it's gone. I'll be happy if there was anyway to not show the 3 dot menu. Maybe some mod or app can do this?
[One (M7) Original Android Development] Spoofy:
Trickster Mod should help you with this.
[One (M7) Original Android Development] xero110:
Just tried and does not work. I guess I'm stuck with it. Did CM build the 3 dot menu into some Apps, like the browser and text messaging? From what I have found it can be built into apps.
[One (M7) Original Android Development] InterFace86:
The veryvery maximum screen time i get is 3h with conservative. When using ondemand then max 2,5h.

I dunno what u guy are doing or what u are turning off to get 4-6h but i guess it means turning everything off what makes a smartphone to be a smartphone. I use alot of internet overall and fb/g+ and fb messenger alot for example.

I never ever have had uptime 24h. I usualy charge my phe full atleast two times a day because of this 2-3h screentime. I must say that cm11 gives more than original rom yes but still not enough
[One (M7) Original Android Development] pigr8:
around 4h screen-on and 20h standby is average on mine.
[One (M7) Original Android Development] Glamsen:
Wow that's impressive... I notice Android os and system is not even appearing in your top list... Might have a bug then?
[One (M7) Original Android Development] InterFace86:
Btw is there a real life difference between 3.62 and 4.19 firmware? I tried to install 4 but cant. Was written that i need soff but couldnt do that (cave me unsecure kernel error or something) so im soff and cant update newest firmware.
[One (M7) Original Android Development] tiny4579:
This is a weird one. It's not CM building something into apps. I believe some apps seem to implement the 3 dot differently where some are hidden when there's a menu button and others are not. To be consistent, I think all apps that have an overflow should either show or hide the 3 dot menu when a menu action is assigned.

I think this happened either when CM merged a change related to AOSP further cancelling support of the menu key or when the option to use default home mappings disappeared.

On another topic, is anyone having issues with the bluetooth audio volumes restoring to incorrect volumes in an audio stream? For me, the only way around it sometimes is to go to the next track (new stream) or advance and go back to this track. I have a Honda Accord 2013 with a HandsFreeLink bluetooth carkit.
[One (M7) Original Android Development] pigr8:
Fine for me, as i said ~4h screen for a full charge and nice standby.
[One (M7) Original Android Development] pigr8:
you are s-off and you cant update firmware using fastboot? this is really strange :S
[One (M7) Original Android Development] sweetnsour:
I believe the issue since CM10 is that the quality is bad. Right now, it's not working altogether (unless this is related to, if not the same as, the bug you are referring to).
[One (M7) Original Android Development] xero110:
Well, I hope they bring it back. I never liked the 3 dot menu and it would be nice to have the option to disable it. Outside of that and the LTE tile not working, everything is great.
[One (M7) Original Android Development] dave328:
Should I asK this somewhere else? I have tried a different kernel as well without luck. Running latest CM rom Snapshot m3
[One (M7) Original Android Development] InterFace86:
Bah. I was sleepy. I wanted to write that im rooted and cant update firmware - why? Or soff is really needed? Then why i cant soff with cm11?
[One (M7) Original Android Development] cvtrial:
May be a stupid question, but I seem to remember that CM used to have "Cyanogenmod settings" in earlier versions?

What I actually miss from these settings is the possibility to change number of rows/columns of apps in app drawer. I can't seem to find the possibility in the newest version (cm-11-20140212-NIGHTLY-m7.zip)
[One (M7) Original Android Development] sabret00the:
You'll find those settings within the app drawers individual settings. Settings => Home => [Your launcher] Settings Icon

---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------

You need S-OFF to change your firmware AFAIK, but I could be wrong.

---------- Post added at 05:37 PM ---------- Previous post was at 05:26 PM ----------

As of KitKat, Google decided to force the 3 Dot menu to show, for a while CyanogenMod decided to undo this change, I now believe they're just going with it,

---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------

Did you enter RUU mode? That's the only way to flash new firmware. You need to type

fastboot oem rebootRUU

from the bootloader and you'll then get a black HTC screen.

---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------

Uber is working for me on the latest Nightly on ART so should definitely be working on M3, try to clear data and if the worse comes to the worst, reinstall.
[One (M7) Original Android Development] dave328:
[/COLOR]

Uber is working for me on the latest Nightly on ART so should definitely be working on M3, try to clear data and if the worse comes to the worst, reinstall.[/QUOTE]

Thanks for the reply, I have tried uninstalling and clearing data several times. It has not worked at all since I went to CM11. I have wiped the device completely and installed the newest nightlies and still no go. What can I do to go about troubleshooting?
[One (M7) Original Android Development] twped:
You need to be soff to install firmware from GPE. However if/when htc releases a new firmware you should be able to update that one with a-on.

I expect New firmware from htc when the sense 6.0 (KitKat) is released.
[One (M7) Original Android Development] Glamsen:
I have a weird bug. My home key is not working properly anymore, appears, that it's always pressed, cause when I touch it once, the reaction is the second touch action (menu) going back to start screen is not possible anymore.... Any ideas? Flashed new firmware today, but not sure it appeared right after
[One (M7) Original Android Development] Ke11ett:
There's a xposed module that enables it.
[One (M7) Original Android Development] xero110:
I tested the one that was pasted in the portal today. It seems to work for most things, but not the browser. I would prefer a native method though. Xposed breaks a few things for me.
[One (M7) Original Android Development] cvtrial:
Seems like they won't give me the goods... I'll try reflashing ROM and gapps in a while.. Can live with it for now! :P
[One (M7) Original Android Development] InterFace86:
Strange is that i still cant use ART with Ingress broot mod. Wont launch - tho some say it works with ART.
[One (M7) Original Android Development] trjlive:
Yes you need s-off to flash different firmwares, unless you are completely stock and accept the OTA updates. In order to run Rumrunner to gain s-off, you must be running a Sense-based ROM as close to stock as possible. No custom ROMs, no AOSP-based, etc. This is because Rumrunner uses functionality in the Sense kernel to do its magic. This is why it doesn't work with CM. I would recommend using the latest RUU for your device/carrier and flashing it back to stock. Then run Rumrunner to gain s-off, and then you can restore your custom recovery and ROM and flash different firmwares.
[One (M7) Original Android Development] InterFace86:
Well i got S-OFF with cyanogenmod 11 today with firewater :) installed 4.19 firmware - everything works.
[One (M7) Original Android Development] trjlive:
Glad to hear you got it working. I haven't used Firewater so I wasn't aware it worked with CM-based ROMs as well. Good to know though. :)
[One (M7) Original Android Development] parabelumm:
updates appears for M3 whoo knows ?? or do I have to install nightlies? THANKS.
[One (M7) Original Android Development] bl4ckb1rd:
simply check here

http://download.cyanogenmod.org/?device=m7&type=snapshot

only M3 so all nightlys are newer and can also have new bugs inside...
[One (M7) Original Android Development] riverajuan:
Can any one explain the difference between snapshop and nightlys?

Thanks in advance
[One (M7) Original Android Development] tiny4579:
Nightlies are based on the latest code in github and may be unstable and sometimes may not even boot.

A snapshot build is done approximately monthly and usually does not contain many major bugs. Think of it like a milestone. With this latest M3 snapshot build, the device tree was based off the state before the kernel was switched so it's relatively bug free.
[One (M7) Original Android Development] riverajuan:
Thank you for taking the time to explain the difference it is really appreciated
[One (M7) Original Android Development] twped:
With snapshot M3 Music through the internal speaker using Google Play Music app is sounds horrible.

Using other music apps it is ok.

Anyone the same?
[One (M7) Original Android Development] pigr8:
fine here.
[One (M7) Original Android Development] lotte67890:
Running cm 10.2.1 I was not able to become S-off with firewater but rumrunner worked fine!

Bootloader was 1.54.
[One (M7) Original Android Development] Robpollard:
Neither firewater nor rumrunner are working for me.

Rumrunner tells me that it won't work with the cm framework/kernel and firewater is being stuck at "chugging".

I'm s-on with devunlock/root on hboot 1.54 with HTC_001 and PN0710000 and at CM M3 nightly currently

Does anybody have an idea what I have to do to get s-off running?

I've followed the manuals correctly and know my way around adb, but nothing will work :(
[One (M7) Original Android Development] sabret00the:
Anyone else finding the proximity sensor is ****ty again? I'm getting a lot of face action.
[One (M7) Original Android Development] Robpollard:
I've managed to get S-OFF by flashing Mikes ARHD and then running rumrunner again :)

What do I have to flash to get the newest firmware/radio for my device? I'm having trouble finding it; a pointer would be much appreciated.

CID: HTC__102, PN0710000
[One (M7) Original Android Development] subarudroid:
Here is what I think to be the most comprehensive guide. Read three times before attempting.

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

[2014.02.08][GUIDE] [MOD] GSM Firmware Flashing & Hboots red warning gone
[One (M7) Original Android Development] qixiixiq:
default google account

I find that my default google account on CM keeps changing. i have tried to delete the accounts and dont want to do a hard reset. I read somewhere that in older android versions renaming of accounts.db in data/system would mimic the initial phone setup but that doesnt seem to work in later versions of Android.

If there is any way to tweak files in the file system or utilize command line to get this done or even find an app in the market i would really appreciate it.

If the CM team could add improved management of accounts withing the Android framework that would really be awesome.

Thanks
[One (M7) Original Android Development] Robpollard:
Thank you so much [MENTION=4138937]subarudroid[/MENTION]! I've flashed the newest fw without any issues, very awesome.

I've just one problem left:

Headphones are not being recognised! I have no clue and I've been searching for ages for a solution. 5 dollars via paypal if anyone can solve this problem.

It's like that: If I plug them in, they aren't recognised. However, if I reboot and leave them in, they are recognised! But after I plug them out, the phone speakers aren't working anymore :( -> Which means I can't take/make calls, as I won't hear the other person.

The problem occurred after I've unlocked the phone 2 months ago and on every rom I've flashed it has been the same (though I've been mostly on CM11). I've upgraded to the newest radio now too; the problem is persisting. There's a workaround via the app SoundAbout which lets me decide manually which of the two the app should choose, which clearly indicates it's not a hardware issue.

Again: 5$ for the one who makes my phone recognise (and de-recognise) my headphones again! :)
[One (M7) Original Android Development] sabret00the:
Sounds like a hardware issue.
[One (M7) Original Android Development] ageva:
Follow the steps below:

1. Do a Nandriod backup

2. install the GE ROM (http://xdaforums.com/showthread.php?t=2358781) or any Sense RUU you prefer.

if the issue still exist, you have hardware problem. if not, something with the CM was messed up so better do a clean install (just run the CM Installer)
[One (M7) Original Android Development] psychomaniac189:
I'm on 0126 and its ****. Jammed like 4 numbers when talking on the phone. Its hit or miss.
[One (M7) Original Android Development] strickyy:
Can someone throw me a link to the latest GPE firmware?
[One (M7) Original Android Development] sabret00the:
Here you go: http://xdaforums.com/showpost.php?p=43192909&postcount=3
[One (M7) Original Android Development] psychomaniac189:
I know I always mention this, but ant way to fix the screen on bug? Different kernel or something?
[One (M7) Original Android Development] ullasmanju:
It didn't happen in M3 for me , but it sometimes does in nightly . changing kernels haven't been a fix to me
[One (M7) Original Android Development] :
Interesting and important Articles
[One (M7) Original Android Development] subarudroid:
Well this is a first.... Guess its time for a clean install.
[One (M7) Original Android Development] snachez:
is any one able to advise if the lag/delay on pressing power and screen wake is still present in latest snapshot ? And, any issues with speakphone volume ? TIA :highfive:
[One (M7) Original Android Development] Ciebiada:
I am on a yesterday's daily build and the lag is still present. However, it is not as severe as it was a week or two ago when I tried CM last time.

However I have a question to you guys. I am checking on CM once every couple of weeks, by flashing daily builds, and things get broken or fixed, and that is cool. But every since I remember the in call volume (normally, through the ear piece) was way too loud on the lowest setting. It is specific to CM as the volume is considerably lower on the stock images (be it SENSE or GPE).

Does anyone know how can I tweak that to my needs? TIA.
[One (M7) Original Android Development] Spoofy:
There are no wake issues on M3 (latest snapshot) only on the nighlies which use a different kernel.
[One (M7) Original Android Development] jasalta387:
Some people report that switching to a GPE firmware (not ROM) would solve the issue.
[One (M7) Original Android Development] Ciebiada:
Thanks, I will research that but I am pretty sure I am on GPE firmware (used GPE RUU before flashing custom roms).
[One (M7) Original Android Development] adyscorpius:
Switching to GPE solved mic issues, not in call speaker volume issues.
[One (M7) Original Android Development] psychomaniac189:
Play some music with Google play music app, go to your home screen, (have long press home set to open Google play) long press the home button. BOOM! Google play music is now super loud. Why? Is this a bug?
[One (M7) Original Android Development] cschmitt:
It's a known issue: https://jira.cyanogenmod.org/browse/CYAN-2554 that occurs when the TFA amps initialize after boot. Accessing Google Now or placing/receiving a phone call initialize TFA's and then voice remains louder until next reboot.

I've worked around it by hitting Google Now once after reboot and adjusting music volume level for post TFA initialized levels.
[One (M7) Original Android Development] fireforhire:
It doesnt solve mic issues
[One (M7) Original Android Development] dseries60:
Try setting handset.mic = analog in the build.prop

I can't remember the full setting, but setting it to analog will most likely have a positive effect.
[One (M7) Original Android Development] zanexlol:
So, you can essentially install this over any rom? As as long as they're 442 and w/e.

And considering the first page: has someone's phone been damaged by this thing?
[One (M7) Original Android Development] bl4ckb1rd:
You mean

persist.audio.handset.mic=analog

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] Spoofy:
It works but my in call volume is now super loud, is that normal?

Ouch... Is still ringing!
[One (M7) Original Android Development] zanexlol:
Yeah, that made very little sense to me.
[One (M7) Original Android Development] butcher211:
Hello,

are there Known issues missing in this page? http://wiki.cyanogenmod.org/w/Known_Issues_page_for_m7

Is this a complete list?
[One (M7) Original Android Development] XxJibblesxX:
Is there a version out yet that doesnt have the screen-on delay? Thats what is stopping this rom from being my daily driver
[One (M7) Original Android Development] tiny4579:
M3 and any build prior to 1/27.
[One (M7) Original Android Development] sabret00the:
Been meaning to ask this for ages, is everyone stuck using the Jellybean lockscreen?

Also ART users, do you encounter system lockup during notifications? Particularly when updating apps?
[One (M7) Original Android Development] XxJibblesxX:
I've been experiencing weird freezes and lockups and I'm using dalvik in the same situation. Also the phone starts pressing things and doing things by itself. Really weird
[One (M7) Original Android Development] riverajuan:
How is battery life on this ROM?
[One (M7) Original Android Development] XxJibblesxX:
Battery life is great
[One (M7) Original Android Development] pigr8:
3h 25 screen on, 1h 52 talk time, 2 email push + whatsapp, official cm11 M3 trimmed down and stock kernel.
[One (M7) Original Android Development] tiny4579:
The screen wake delay appears to be fixed with the latest merged commits and open commits for the msm8960 kernel.

I'm curious if the 2/20 nightly has it fixed as well.
[One (M7) Original Android Development] cschmitt:
Did a build with 59943 only, didn't seem to help wake delay.

Did a build with the 4 open commits from early AM in msm8960, does seems to improve the wake delay; it's down to 150 to 250mS, similar to the m7 kernel.
[One (M7) Original Android Development] tiny4579:
I think that is the same delay from stock so we may not see any better than that.

EDIT: The commits are merged so we'll see these improvements in the next nightly.
[One (M7) Original Android Development] cschmitt:
Agreed, I can definitely live with it.

Reboot to recovery & bootloader from power menu are still acting up on the new kernel, just reboots to CM.
[One (M7) Original Android Development] pavik62:
Just a question:

Have you not noticed that in build.prop on Alarm - ro.config.alarm_alert = Alarm_Classic.ogg. But there is no Alarm_Classic.ogg?

You can fix this?
[One (M7) Original Android Development] intervigil:
Can you get a last kmsg? I'm unable to reproduce this, I just rebooted to bootloader and recovery just fine.
[One (M7) Original Android Development] tiny4579:
I think this is a recovery related issue. It doesn't happen on the CWM-based philz recovery for me. Maybe with TWRP.

Nevermind, you said bootloader as well. It still could be recovery related. Try with the official CWM unless you're already using it.
[One (M7) Original Android Development] cschmitt:
last_kmsg after power menu - reboot - recovery. (Device rebooted, HTC splash, CM splash, booted to CM.)
[One (M7) Original Android Development] cschmitt:
Not sure about that, all I have to do is switch back to m7 kernel and the issue goes away.

I use TWRP, just for giggles flashed CWM 6.0.4.6, not change. Still reboot directly into CM.

Edit: Interesting: Reboot to recovery from Titanium Backup or Flashify still work fine, maybe they perform the reboot using a different mechanism than the Power menu?

Edit2: Flash cm-11-20140220-NIGHTLY-m7, still reboots in CM instead of recovery.
[One (M7) Original Android Development] tiny4579:
Nope, I didn't catch this earlier. But I don't think this is causing a problem. CM defaults to Hassium according to the config and it seems to pick up that alarm when setting a new alarm, so I don't see an issue here.
[One (M7) Original Android Development] daverdfw:
So its starting to look like the CM builds are pretty stable now? Any really glaring issues? Also battery life that the user earlier posted on M3 looks really nice.
[One (M7) Original Android Development] KaZo58:
to Edit2: just flash it again :< and it'll work. i'm doing this for over 2 weeks. i'm on CWM 6.0.4.6 Touch.

my edit: eww nope doesn't work anymore. booting into recovery with adb works fine.

(before flashing todays build, i updated the firmware from 4.19.1540.4 to 4.19.401.8)

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] intervigil:
This is a last_kmsg from rebooting into recovery? It shows the modem has crashed and the phone restarts itself due to the modem subsystem crashing.