yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] cschmitt:
I'll take your word for it. Still something changed in 0304 and forward builds which makes them incompatible with prior builds.

That's not a big deal, as I don't plan on reverting, but it appears the stable branch is behind with respect to that same change.

Caulk it up to the nature of bouncing between nightly builds.
[One (M7) Original Android Development] Thyria:
http://pastebin.com/GTj4q7La

I just found the phone rebooted wanting me to enter the pin.
[One (M7) Original Android Development] Pard0ned:
Yeah, my installation of M4 is working fine. I did a full wipe beforehand though. And I'm running the GPE firmware as well - don't know if that makes a difference.
[One (M7) Original Android Development] tjsooley:
Same for me both dalvick and art
[One (M7) Original Android Development] PureLife90:
This may sound completely stupid.... But what is gpe firmware? I'm just now hearing about this... I'm running Viper atm but I'm keeping up on this post... I'm new to HTC but I run cyanogen on my Samsung devices... Thanks in advance
[One (M7) Original Android Development] KaZo58:
i don't know about "gpe" firmware. just flashed this one. http://xdaforums.com/showthread.php?t=2485651. no problems here on dalvik, except low volume sounds. i set to separated ringtone and notifications volume, it gets louder now. but musics/videos (multimedia sounds) are still low.

Gesendet von meinem One
[One (M7) Original Android Development] Pard0ned:
It just means I'm running the firmware that came on the HTC one Google Play edition. They're both interchangeable.

I've read some people saying it's best to have sense firmware when running sense ROMs, and to have GPE firmware when running GPE ROMs.

I took a shot that it might help with some slow-down issues that I've been having on cyanogenmod. And, at least to my eyes, it has helped.
[One (M7) Original Android Development] tiny4579:
I believe this describes it pretty well.

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-2801

It's an oversensitive rear mic and not directly the fault of speaker phone. The effect seems to be that your voice would be cancelled out. For whatever reason, I don't have that problem when I talk to people
[One (M7) Original Android Development] tiny4579:
Has anyone had any issues with Bluetooth force closes when phone audio is enabled for the car? This didn't happen to me until the second pairing.

I don't expect the developers to acknowledge it as a bug report since these are nightlies and not an milestone/RC build that JIRA is supported for. I just wanted to make sure I'm not crazy and the only one getting it. I can link a logcat but it's kind of older. I suspect the cause is still the same.

I think the other device needs to support MAP for this issue to trigger.
[One (M7) Original Android Development] pnut22r:
Has anyone noticed the media speaker volume limit is extremely high? Feels like I'm going to blow the speakers at 50%
[One (M7) Original Android Development] peestandingup:
Its a bug. You have to go into sound settings & unlink ringtone & notification alerts to control them separately.
[One (M7) Original Android Development] TheEgonSpengler:
Is it the same issue that the rear mic causes when you clamp it between your head and left shoulder covering the mic and having the other party not hear you?

Edit: mucked with it again, those issues appear separate.

The key to good audio for the moment on speaker phone is to not cover the rear mic. The front appears to not be listening. I had no issues being heard when I was mindful of that.
[One (M7) Original Android Development] xetrev:
I have a case on my phone and with the case on everything works just fine.

With the case off my calls have static in the background and you can barely hear my voice.

I am not sure which microphone the case is covering but that seems to be the issue.
[One (M7) Original Android Development] formula84:
Should be easy to see which Mic is being covered.

Bottom is to the right of the micro usb connector ( pin hole )

The rear is 1cm below the power button.
[One (M7) Original Android Development] xetrev:
The case covers both but has slits for them.
[One (M7) Original Android Development] fireforhire:
Right on time...
[One (M7) Original Android Development] xc8118:
Still experiencing GPS lock issues. Location is on and sent to high accuracy. It will localize me to a small circle but never actually lock... So turn by turn navigation won't work at all.
[One (M7) Original Android Development] tiny4579:
Sadly not much is going on or at least as much as I'd hope. Codeworkx being absent from the development wor\ld seems to be quite a detriment for this device. The primary maintainer isn't on xda much and has said so much himself. There's a lot of development for CM11 in general but quiet for the m7. There doesn't seem to be much to fix other than the outstanding issues.

Most development for CM11 is on gerrit and doesn't necessarily have thread updates. Don't assume nothing is happening though because the xda thread is quiet.

PS. I will probably stay on Sense/GPE for now.
[One (M7) Original Android Development] xetrev:
I am running GPE with xposed modules and I have everything i need functionality wise minus CM's blacklist.

It's not as buttery as CM11 but its 20x more stable and everything works.

I would use CM 10.2 but it has the broken speakerphone issue and outbound callerid display bug with google voice (its rock solid minus those two things).
[One (M7) Original Android Development] scotty2hotty1125:
I'm not sure if this is related to CM11 or if it's app related but, can anyone else stream UV movies via Flixster? It doesn't work for me. It says my device is unsupported.
[One (M7) Original Android Development] :
I don't know what disturbs some,there are fixes published for the One,see the last changelogs.

You must not forget the CM11 is still very young! It always takes a while until every ROM is stable.

And a Developer/Maintainer we need not necessarily for a thread, we can do by our/yourself

Keep patient :cool:
[One (M7) Original Android Development] cschmitt:
Just submitted my first bug fix to CM's Gerrit instance that fixs the missing notification volume slider in the Sound Volumes Settings panel.

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

Hopefully, many more to follow!
[One (M7) Original Android Development] dog77k:
Is anyone noticing random reboots the recent nightlies? I've had 3 random reboots over the last few days running 12-24. I believe one occurred in the hangouts app, and the other 2 were from sleep. Didn't notice any reboots on previous nightlies (12-20 and before).
[One (M7) Original Android Development] elherr:
Had it happen once in Hangouts. Soft booted (i.e., did not go to bootloader).
[One (M7) Original Android Development] sweetnsour:
4.4.2 is new, that's true. But looking at previous releases, CM10.2 in particular, and you can see that device-specific development was rather slow. As it is now, CM11 is actually pretty stable, and while the existing bugs are pretty big in my opinion, thankfully there's not a lot of them. Sad to see that this device is missing a maintainer, but hopefully things work out for the maintainer, whatever the reason it is that he is inactive for.

For now, I've decided to go back to GPE, but I would like to bring the following bugs to the attention of any other maintainer:

1. Trying to adjust the maximum frequency (in settings > performance) will cause the minimum frequency to be set at 1728 mhz until the phone is rebooted.

2. NFC cannot be turned off.

3. I cannot vouch for this, but audio quality on speakerphone is poor. If I have read correctly, it has something to do with the noise cancelling mic on the back of the phone.

4. I cannot vouch for this, but someone reported media volume to be very high when the ringtone and notification volumes are linked.

5. When using the front camera, the intended behavior of tapping anywhere on the screen is to focus on that area. While the camera does focus, the "focus ring" never becomes green to indicate that the camera has focused.

6. If you add quiet hours as a quicksettings toggle, I believe long-pressing on the toggle should take you to the quiet hours menu within settings. At the moment, long-pressing on that particular toggle does not do anything other than vibrate. Although I haven't checked, there may be other toggles whose long-press behavior is currently set at nothing.

Not sure if the following is a bug:

7. When receiving a call on GPE, the caller photo is partially hidden; when the call is accepted, the photo is fully revealed. If I remember correctly, when receiving a call on CM, the caller photo has a see-through gray overlay where the photo should be hidden.

I saw a post from codeworkx saying that the core CM people, some of which are the maintainers of our device, do not frequent XDA. I think it would help if we compile a list of bugs and post it on the CM forums as we cannot use jira for bugs on nightlies I believe.
[One (M7) Original Android Development] Andbanyan:
Just flashed this today and all my camera shots are coming out purple in low light. Was not a problem with the stock camera app.
[One (M7) Original Android Development] nonmindo:
Just a heads up for everyone that may not know this...

The "M" builds are actually older than the nightlies... It's explained here

Essentially:

If you want latest and greatest + possible bugs, Run nightlies only, don't use "M" releases

If you want stable-ish run "M" releases
[One (M7) Original Android Development] tiny4579:
What build were you using? The last_kmsg indicates two things: 1. the kernel was built on 1/5/14, so it's around the age of M2, 2. the modem/radio is intitiating the reboot.

I'd recommend you make sure you're on at least M3 if you want to stay stable since there were some weird bugs around December/January that were fixed by sometime in January.

If you still have issues on M3, you maybe want to check if GPE or Sense reboot to check if it's hardware related.
[One (M7) Original Android Development] intervigil:
If you get a chance, try a nightly from after today. I spent some time poking at the modem shutdown code, it appears some steps taken in the HTC kernel may have been missing.
[One (M7) Original Android Development] twped:
I installed m4 from m3 no issues for booting.

I'm on Art and sense firmware.

Looks good here.
[One (M7) Original Android Development] superleeds27:
Clean flash on 9th nightly. Phone keeps fc'ing. Lose signal, comes back within 30 seconds

Attached log: http://www.sendspace.com/file/9prgrm
[One (M7) Original Android Development] sabret00the:
Doesn't help, but on the nightly track, 20140309 works fine for me and no force closes with the phone app.
[One (M7) Original Android Development] Thyria:
[MENTION=3500210]tiny4579[/MENTION] Thank you for your help. You are awesome. I am always on the latest nightly. So the kernel shown as 1/5/2014 cant be true. Strange. Going to try first PA and then Sense. Gonna report later what's going on.
[One (M7) Original Android Development] Pard0ned:
Anyone else having problems were the profiles are reset, like back on to whatever is the first one?

Edit: turns out I had set up some triggers for connecting to a certain WiFi network. Disabled the triggers and all works fine again.
[One (M7) Original Android Development] tiny4579:
I think it is true. Thinking back on that it's probably the recovery kernel. Meaning last reboot was from recovery. This could happen if you get a soft reboot like back to the boost animation.
[One (M7) Original Android Development] superleeds27:
Another log.

Will redownload and flash again when I get home!

http://www.sendspace.com/file/q24mbn
[One (M7) Original Android Development] cschmitt:
On 0309 reboot to recovery and bootloader are working fine. Many thanks to you and [MENTION=3500210]tiny4579[/MENTION] for the work you've been doing on our device. The msm8960 kernel is shaping up.
[One (M7) Original Android Development] :
Perhaps

in your case the cause is any file corpses on SD (Kernel, etc.)

exist even after a Full Wipe.

There is a Tool that can be applied after a full wipe,

with this really all is removed,

before necessarily all the important data of the SD secure!

Via ADB you can push a ROM.zip to the SD:

adb push xxx.zip sdcard/

Or you can use the USB-OTG solution

The Tool will be published with knowledge of the creator

Good luck :)

Tool Download

Tool Thread
[One (M7) Original Android Development] tiny4579:
A simpler method is to lock and unlock the boatloader or wipe userdata from fastboot.
[One (M7) Original Android Development] superleeds27:
Re-downloaded. Clean install. Phone FC still.

Hmm...

http://pastebin.com/MhPJAqFk
[One (M7) Original Android Development] :
Many are not familiar in dealing with ADB, or can not use this method as I because Win 8.1 ;)

then just use the TWRP-Recovery & USB OTB
[One (M7) Original Android Development] tiny4579:
Weird. Can you get to the point where you can set your APN or does the phone fc appear constantly?

It almost seems like stk.apk, SIM toolkit is triggering it. Very strange. Gapps are correct right?

Also your earlier logcats I couldn't see on mobile.
[One (M7) Original Android Development] superleeds27:
Im using Banks Gapps. I know its not 'Official' but they've worked ever since ive got the phone and on the N4 before that.

Heres the log from earlier: http://pastebin.com/nr1PgeRw I could pastebin at the time.

Its strange. Phone goes through setup fine. and then eventually gets to home screen. Its from there where it randomly pops up. Sometimes i just like lose signal bars, and then other times a small SIM card like symbol replaces the signal bars for a few seconds and then signal returns!
[One (M7) Original Android Development] pavik62:
Try to wipe the contacts of the SIM card
[One (M7) Original Android Development] superleeds27:
No contacts on the Sim Card. All contacts are are on Google.
[One (M7) Original Android Development] tiny4579:
When did this start? I wonder if this is a carrier specifically issue. Cm made a few overlay changes which may be causing a problem. What is your carrier?

I'll try to remember to mention your logcats on cms HTC freenode irc channel.
[One (M7) Original Android Development] superleeds27:
Well i flashed the M4 snapshot yesterday, and it was working fine.

I thought id clean flash and go back to nightlies with it been newer code/features etc.

Im currently with EE in the UK.
[One (M7) Original Android Development] Jediritter:
Anyone can tell me why Cyanogenmod doesn't work with my new lcd display but original firmware and InsertCoin Firmware does work?
[One (M7) Original Android Development] Thyria:
Yes im going to try it. It's my last chance. PA doesnt work either.
[One (M7) Original Android Development] cschmitt:
Post a last_kmsg following boot and we'll have a look. Could be an LCD driver missing from CM that's included in stock ROM?
[One (M7) Original Android Development] Jediritter:
Here is my last_kmsg File: http://pastebin.com/QJ13keqt

From what I did read, it is a display from sharp.
[One (M7) Original Android Development] elherr:
Spontaneous reboot on nightly 0309. last_kmsg link --

http://pastebin.com/cxJyxxbF
[One (M7) Original Android Development] smoki3:
Does miracast work?

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Original Android Development] Alef_0:
Hello I would like to try Cyanogenmod. Now I'm with the originale GPE firmware 3.62. Should I stay or is it better to go to Sense firmware 4.19.401.9?
[One (M7) Original Android Development] jasalta387:
GPE firmware is reportedly working better than Sense firmware. However, there are users that just have no problems on a Sense firmware. Just try it out and see how you feel it.

I went from Sense to GPE because I will get better performance when using the speakerphone mode.
[One (M7) Original Android Development] Alef_0:
Ok tnx.

I'll try with gpe, in case of issues I will put the sense one.
[One (M7) Original Android Development] jefbuan:
does ir blaster working on latest nightly??
[One (M7) Original Android Development] Moudii:
Installed m4 snapshot, gotta say there are far less bugs than I expected after scrolling trough this thread. Guess the happy customers are the quiet ones [emoji13]
[One (M7) Original Android Development] Thyria:
Still reboots. I did a really FULL wipe, with the tool of [MENTION=4825737]Heinz Ketchup[/MENTION], replaced recovery, replaced rom; Still reboots. I'm now on the 4.4 GPE Radio. Looking if something is changing. I'm beginning to think SMS (and so, in conclusion, the radio) are the problem, because the phone rebooted yesterday in front of my eyes without a reason. I entered the PIN and then it received the SMS. Strange.
[One (M7) Original Android Development] pigr8:
upgraded from M3 to M4 on art vm, perfectly working.
[One (M7) Original Android Development] badams1:
Also updated from M3 to M4 here...using ART...and all is running perfectly. I think I have decided at this point to only update on "M" series releases...or whatever release comes along that is also supposed to be as stable. Im more interested in being able to reliably use my phone than trying out untested tweaks.

I am really enjoying CM11 at this point.
[One (M7) Original Android Development] dog77k:
Yes, it's been working since the fix in early Dec.
[One (M7) Original Android Development] Pard0ned:
I'm exactly the same. I went from m3 to m4, also using ART. It has been working perfectly for me.

Really looking forward to getting an RC release though. From the looks of m4, I'd say they're well on their way to it now.
[One (M7) Original Android Development] :
Read this before flash a M-Build
[One (M7) Original Android Development] Pard0ned:
Especially if you're on a nightly release.

Personally, I'm a tinkerer but don't want the chaos of a nightly, so I'm staying on the M releases. At least until a RC release comes along - or CM11 stable.
[One (M7) Original Android Development] sabret00the:
New nightly is out with some more M7 specific stuff. Also there's some M7 Verizon specific stuff.
[One (M7) Original Android Development] flojho01:
Hi.

On the last builds I have the problem, that the incall volume is too loud.
[One (M7) Original Android Development] alangrig:
Guys , wanna install CM11. Does video records with stereo sound?
[One (M7) Original Android Development] gr4p3s:
Does anyone else feel like the max speaker volume is much lower on m4?
[One (M7) Original Android Development] sabret00the:
Is everyone stuck on the Jellybean lockscreen or is it just me?
[One (M7) Original Android Development] Pard0ned:
What kernels are people using with CM?

Just looking to get ideas, as I haven't played with kernels on HTC phones in 2 or 3 years.☺
[One (M7) Original Android Development] Adromir:
Since yesterday i have the problem, that my prefered network always sets back to 3g or even 2g (running latest nightly)
[One (M7) Original Android Development] pigr8:
i think the proximity sensor is a bit lazy on M4, isn't it?
[One (M7) Original Android Development] Ruku1994:
Unfortunately it is as in GPE, only mono.
[One (M7) Original Android Development] oosacker:
I have snapshot-m4 installed, I like rhe added features but I noticed a few things...

1. the indicator led turns greenp at around 90% instead of 100% charge

2. rightmost icon on dock disappears when reboot

3. device gets really hot using Chrome on 3G??

4. seems to have trouble with some chargers??? (seems to think its on USB and charge slow)

Tapatalk を使用して私の One から送信
[One (M7) Original Android Development] pigr8:
1. not an issue, it's fine that way

2. nope, just you

3. nope, just you

4. use the stock charger with stock cable, it's a third party charger issue
[One (M7) Original Android Development] oosacker:
That doesn't seem right, I'm coming from stock GPE and dont remember these issues.

Tapatalk を使用して私の One から送信
[One (M7) Original Android Development] tiny4579:
1. This is standard AOSP functionality. Not an issue as the previous responder said.

2. Does it disappear when rebooting? I don't use a dock so I don't know, unless you mean the launcher dock but that sounds weird and I don't think that would be a CM issue.

3. Your phone is either running the CPU hot or draining battery fast from the app and/or 3g. This isn't ROM related either.

4. I have that issue with the m7 kernel that's in the snapshots but not with the kernel in the current nightlies.

I think there's a difference in charge mode detection code.
[One (M7) Original Android Development] oosacker:
1. OK, but I think I remember in GPE and stock it used to go green when 100% but not that important.

2. Its on the launcher, the icon disappears after reboot, seen it on CM11 on all my devices (Nexus7, G Pad etc) has this issue. I use Google Now launcher so doesn't bother me.

3. Yeah probably.

4. I used a iPhone charger (5W) and it thinks its USB. I tried a portable battery pack and it works fine. Have not tried many others yet.

BTW I use CM on Japanese mode (because Japanese characters look crap when in English mode). And I see not all the text has been translated yet (doesn't bother me though cos i can read it).
[One (M7) Original Android Development] tiny4579:
For item 1 yes that's because GPE and stock are not AOSP. Phone makers decide to make 100% the charged point for the charging indicator.
[One (M7) Original Android Development] tiny4579:
Hey guys, what's typical battery drain per hour for you over bluetooth audio? I typically get 3-5% an hour.
[One (M7) Original Android Development] tiny4579:
Jellybean? No, not me.

Sounds APN related. Can you make sure you're on the correct one?
[One (M7) Original Android Development] sabret00the:
Hmm, maybe I need to reset mine as I had custom shortcuts.

---------- Post added at 12:13 AM ---------- Previous post was at 12:11 AM ----------

Nope, it's still the Jellybean lockscreen. Hence the dots on the slider.

---------- Post added at 12:20 AM ---------- Previous post was at 12:13 AM ----------

The KitKat one looks like this
[One (M7) Original Android Development] tiny4579:
Oh yeah that. I had a duh moment. Mine's the jellybean lockscreen as well then.

Maybe the kitkat lockscreen requires the Google Now launcher. Hmm, still no go. Not sure. Maybe CM doesn't have it, but I thought I've flashed a CM11 build with the kitkat lockscreen on another device. Maybe it was an AOSP ROM on my galaxy nexus. Regardless, sorry for the confusion. I see what you're talking about now.
[One (M7) Original Android Development] Adromir:
Positive, i didnt changed them them, but already checked it. I can turn of 4G but then after a while its falling back to 3g
[One (M7) Original Android Development] Raymond Ebertt:
Need some help

I'm trying to push a theme into this ROM, but I am having permission denied when using adb remount.

I have no issues with a Sense ROM as I tested 4 ROM's today.

When I do adb devices, I get my device name. After adb remount, fails. Doing anything in adb shell gives a device not found.

I have debugging on, mounted in es file explorer, done about a dozen tutorial fixes and no success.

Any help would be greatly appreciated.
[One (M7) Original Android Development] sweetnsour:
In developer options, have you tried revoking usb debugging authorization?
[One (M7) Original Android Development] Raymond Ebertt:
I tried that a couple of times, plugged back in checked yes. I don't know know what it is but it's frustrating.

EDIT: Case closed. I sorted it out.
[One (M7) Original Android Development] Hedi86:
cm-11-20140313-NIGHTLY-m7.zip Didn't Boot after update from cm-11-20140312-NIGHTLY-m7.zip

Back to cm-11-20140312-NIGHTLY-m7.zip Boot...
[One (M7) Original Android Development] sabret00the:
Confirmed
[One (M7) Original Android Development] riverajuan:
Is there a way to use the screen lock slide together with the pin lock?

Any info or advise will be greatly appreciated

Thanks in advance