yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] KaZo58:
download latest nightly from https://download.cyanogenmod.org/?device=m7 and put it in ur device folder cmupdater. go back into cyanogenmod updater and you will see the downloaded zip. hf.

after 10-11 months usage, i realized last night my camera has red tints. -.- check out my screenshot. is this fixed in sense rom? or do i need to send to service? will my phone get replaced? on some photos red tints are a little bit visible.

Gesendet von meinem One
[One (M7) Original Android Development] turtle13:
Yeah, I re-paired it countless times trying to track down what was going on. Does it with Apollo and Poweramp. Running 4/9.
[One (M7) Original Android Development] elherr:
Looks like CM Updater is working again.

---------- Post added at 04:57 AM ---------- Previous post was at 04:52 AM ----------

Is it heat related?

When my phone is warm, the camera has purple tints. From what I have read, this is a hardware issue with camera and associated heatsink, and is not correctable in software.
[One (M7) Original Android Development] badams1:
Hello,

I am currently running the M4 snapshot..and it works great. I typically only update on "M" releases at this point as I'm more interested in stability than experimenting. I've read conflicting posts from the last few pages about the M5 release...some saying it works fine...others saying buttons are laggy and that the kernel switch that was made isn't as responsive.

Which leads me to my question. From anyone who has ran both of these M releases, am I better off sticking with M4 and see what M6 looks like or is the M5 actually fine and I could update to it with no issues. Again...M4 is running perfectly for me, and I don't want update if I am going to loose any performance or stability.

Thanks in advance for any of your opinions.

BA
[One (M7) Original Android Development] tiny4579:
Does a reboot fix it? I wonder if something changed code wise since it was working flawlessly for me earlier. I seem to have that only one successful metadata per boot issue.
[One (M7) Original Android Development] turtle13:
Nope, only wiping dalvik and cache brings it back. I am thinking when i get back from chicago on sunday I am going to downgrade my firmware and see if that has any effect.

logical line of troubleshooting

worked fine on GPE

went to CM11 and updated to newest firmware

reflash clean = nothing

wipe dalvik and cache = works shortly

only really leaves the firmware and radio to troubleshoot.
[One (M7) Original Android Development] tiny4579:
It's probably a combination of the bluetooth stack in CM11 with certain head units.

CM11 is in a constant state of flux so weird stuff can happen and metadata didn't work in CM10.1 but worked in CM10.2. This is also the first time AOSP had decent metadata support that was broken by CM changes, and it's odd that there's little movement to fix this.

While not an essential feature, it's one that I've come to enjoy having, so I hate when it's working inconsistently.

The action from here would be to open a JIRA ticket on M5, but with the weird issues I'm not sure if the CM folk could even reproduce it.

If only we could get them to completely remove the AVRCP 1.5 support. Few users I think could even utilize it and it's what started the metadata mess in CM11.

Can you see if it's an issue in M5? You should be able to dirty flash if you're coming from recent nightlies. There was one bluetooth change I noticed within the last 10 days and it may, but not likely be related. I remember metadata working flawless until about a week ago.
[One (M7) Original Android Development] dseries60:
M5 is running fine for me. Using tbalden's CM Kernel and have great battery life. No issues to report.
[One (M7) Original Android Development] cschmitt:
I've noticed that since the custom lockscreen wallpaper commits on the 10th that the Play Music album art gets stuck as the lockscreen wallpaper until a reboot.
[One (M7) Original Android Development] tiny4579:
Except that kernel is way out of date so remember that if you run into issues in the future.
[One (M7) Original Android Development] tiny4579:
I've noticed that too. I think you can manually reset the lock screen wallpaper and back to clear the problem.
[One (M7) Original Android Development] dseries60:
Thanks tiny, your right. I really like the home2wake feature better than s2w, etc. None of the other kernels offer it. I believe tbalden is working to get it current.
[One (M7) Original Android Development] YouLaxy:
I can report my buttons became very slow after going from pre-M5 nightly to the latest one. That sucks.
[One (M7) Original Android Development] KaZo58:
nope it's not heat related.
[One (M7) Original Android Development] elherr:
Anyone else having occasional wifi disconnects on latest nightly(ies)? All other devices on WAP are not having any problems, but at odd times my One will not re-authenticate. Logcat spits out "CTRL-EVENT-DISCONNECTED reason 2" after three attempts. Disabling/re-enabling wifi has same indications. Key nogotiation does not complete. WAP running OpenWRT and using WPA2 CCMP(AES).

Rebooting phone clears the problem.
[One (M7) Original Android Development] Leebert225:
I see this as well, running today's nightly and the last one.
[One (M7) Original Android Development] tiny4579:
Does it actually show a disconnect or just stops working? I'm not noticing that issue. I believe I'm running WPA2 as well.

I didn't see any device specific changes to break wifi. There were some sepolicy changes that have some impact on wifi but I don't think we use that firmware.

This is what I mean: http://review.cyanogenmod.org/#/c/62212/
[One (M7) Original Android Development] elherr:
It disconnects and falls back to cell data. It will intermittently try to reconnect to WAP but fail key negotiation (according to phone). From what I see, WAP seems to think that negotiation completes.

This does not happen very often but *has* happened enough to be noticeable. Perhaps once per week.

OpenWRT logs show constant auth/association/de-auth.

2014-04-11T16:01:15-05:00 wap-1.nebula.lan hostapd: wlan0: STA e8:99:c4:93:0e:2b IEEE 802.11: authenticated
2014-04-11T16:01:15-05:00 wap-1.nebula.lan hostapd: wlan0: STA e8:99:c4:93:0e:2b IEEE 802.11: associated (aid 4)
2014-04-11T16:01:24-05:00 wap-1.nebula.lan hostapd: wlan0: STA e8:99:c4:93:0e:2b IEEE 802.11: deauthenticated due to local deauth request

Next time it happens I'll muck around with phone wlan interface in shell before rebooting...
[One (M7) Original Android Development] sevenalive:
Song data did show up for me randomly today. I did update to the nightly made this week. However today (didn't update it), no song info again.
[One (M7) Original Android Development] afiqq:
im currently using 4.19.401.9 Firmware and its fairly good although LTE connection sometimes drops.

Just want to know whats the recommended/optimum firmware to use right now with the M5 snapshot?
[One (M7) Original Android Development] sabret00the:
Anyone noticed that the dialog for no needing to do a network search is gingerbread styled.
[One (M7) Original Android Development] elherr:
Looks like 0412 theming changes makes Xposed unhappy. I had to select "Disabled resource hooks" in Xposed settings for it to run.
[One (M7) Original Android Development] cschmitt:
My setup :

Radio: 4T.24.3218.09 (latest from AT&T 4.18.502.7, since I'm on AT&T network)

Hboot: GPE 1.54.0000 (Aug 19, 2013) , from 3.07.1700.1 firmware, because it's still unlockable via 'fastboot oem unlock'

Splash1.nb0: custom dark version.

Everything else (dsp, sbl, tz, rpm, etc.) from 4.18.502.7 firmware.
[One (M7) Original Android Development] Jediritter:
Is there any special kernel or app I do need to use the IR functionality with CM 11 ?
[One (M7) Original Android Development] tiny4579:
Kernel no. For the app try smart remote by color tiger apps. It isn't free though.
[One (M7) Original Android Development] kala123:
What kernel is the best whit this rom?
[One (M7) Original Android Development] Jediritter:
Thanks, working perfect for all my systems :)
[One (M7) Original Android Development] KaZo58:
try "Sense TV" official HTC app. it should work.

Gesendet von meinem One
[One (M7) Original Android Development] erto90:
someone tried to use htc one max camera libs to see if flash-assist to focus works?

Because this lack drive me crazy
[One (M7) Original Android Development] tiny4579:
It requires the sense 5.5 or 6 camera app. Libs alone won't make a difference here and those libs probably won't work with cm anyway.
[One (M7) Original Android Development] erto90:
ok but why every damn also low end phone got this function in cm except ours?

If htc release 4.4.2 source, we will be able to have that function?
[One (M7) Original Android Development] itdemo:
Loving this ROM! (for the most part)

Running the latest milestone build: M5.

However, I am getting a weird problem with the YouTube app. When watching videos, the audio and video stutter and sound all distorted.

Has anyone else had this behaviour?

If so, did you fix it?

If not, what version of the ROM are you running? I presumed the milestone would be quite stable but, if the latest nightlies are better, please let me know.

Cheers!

Gavin

EDIT: Updated to latest nightly, seems to be fixed and it's all running very smoothly.
[One (M7) Original Android Development] Aarush:
Hello guys, I unlocked and rooted my friend's HTC one and installed this ROM on it. According to her its awesome but there's a weird thing going on, whenever I shake the device, the screen goes off (locks, with the animation too). It's weird, she didn't alter any settings on it and I couldn't find an option that might have enabled this sort of a thing.

Any help would be appreciated. Thanks! :)
[One (M7) Original Android Development] pavik62:
You flashed sided kernel? Get boot.img from zip with ROM.
[One (M7) Original Android Development] Aarush:
Yes, i flashed STi kernel, okay I'll flash that one and report back, thanks! :)
[One (M7) Original Android Development] vv91xv:
Sound quality is good? Thx
[One (M7) Original Android Development] tiny4579:
I don't know the answer to this. None of the devices I've used ever had the flash feature. And what sort of source are you talking about?

It's alright. Bluetooth audio playback stutters sometimes.
[One (M7) Original Android Development] KaZo58:
14/04 is not good. soft reboots occurs after installing/deinstalling apps.

Gesendet von meinem One
[One (M7) Original Android Development] tiny4579:
Interesting since there were only two changes from the previous nightly according to http://www.cmxlog.com/11/m7
[One (M7) Original Android Development] question.com:
Anyone having issues with dash clock? Don't know if something changes in the build that's causing it to crash nonstop. It doesn't populate all the widgets then crashes
[One (M7) Original Android Development] Floyd_Flivercod:
Nice battery stats on the 4/13 build today. 1 hr 45 min screen on. Bluetooth was the only service not active all day.
[One (M7) Original Android Development] sabret00the:
Rear microphone is still overzealous. Cover it while you're on the phone and your voice is effected. Loudspeaker still sucks too. So for whatever reason, there's a definite issue with the rear microphone.

I'm also still seeing the haptic feedback stuttering.

The proximity sensor is still doing a poor job.

Memory management isn't working correctly. As demonstrated by the fact the most recent app is often missing. (open app, go to home screen, open recent apps versus open app, go to home screen, open app drawer)

Anyway, all of these are long standing issues that seem to be getting ignored, it's a shame.

EDIT: I'm not saying that they need to be fixed. I'm not acting that entitled, but it would be nice to have them acknowledged. Whether it's a case of them being fixed eventually or of too low priority to fix, either is fine. But there should be enough respect from CyanogenMod to actually engage with the community enough to acknowledge that there are issues.
[One (M7) Original Android Development] vbauer86:
What about camera?

is it still blurry in lowlight?
[One (M7) Original Android Development] KillerBeaver:
It bugs me that the torch app falls asleep too.
[One (M7) Original Android Development] kraze1994:
Just upgraded to cm-11-20140405 Snapshot and it appears the camera just forces closes itself upon boot. Anyone seeing the same?
[One (M7) Original Android Development] NitroOxid:
Guys. I understand there is no make of custom solutions for flashlights?

I need a flashlight that will work when the display is off. Desired me and others a custom - does not work. Is there a solution?
[One (M7) Original Android Development] elherr:
This is working again with the latest nightlies (was broken with CM11 nightlies for a time), and works for me with screen off.

https://play.google.com/store/apps/details?id=com.devuni.flashlight

*Edit: LED will shut off for about a secord when display shuts off but will come back on...
[One (M7) Original Android Development] NitroOxid:
I use Cyandelta, and I just used it this app! But does not work .. I'll try to put the firmware without Cyandelta. Strange.

core teaMsevenAOSP

EDIT: I reinstalled, flashlight does not work, only the standard.

EDIT2: WORK!!! On stock CM kernel.
[One (M7) Original Android Development] intervigil:
I'm thinking the microphone issue people are experiencing seems to be subjective, or I have a very high tolerance for bad quality audio.

I have not heard anything about the haptic feedback. What issue is this?

Proximity sensor performance seems to vary from device to device. Some people have reported that the sensor is basically non-functional, others have reported no issues.

I have not heard anything about memory management.

I'm not sure what you mean when you say CyanogenMod should have enough respect, but for me personally, I simply do not frequent XDA, nor do I plan to do so more than perhaps once or twice a month.

You can file bug reports using JIRA (but only against stable and M builds), however those are also taken care of on an ad-hoc basis, subject to maintainer schedule.

Easiest way to get into actual contact with people is to use IRC.

Try the #cm-htc, or the main #cyanogenmod or #cyanogenmod-dev channels.
[One (M7) Original Android Development] fireforhire:
I don't think its subjective when every person I speak to on speaker phone continually says "what", " I can't hear you". Cm on this phone is utter garbage.
[One (M7) Original Android Development] sabret00the:
How often do you have someone call you using an M7 running CyanogenMod? As I've stated, the simple test is to get them to speak normally and then to get them to speak while covering the rear microphone.

If you're typing and you have haptic feedback enabled on your keyboard, the haptic feedback will stick for around a second occasionally.

Well in that case, can we sort out some sort of testing? Perhaps we'll be able to get an idea or how far spread the problem is and what batch numbers are effected.

I've raised the issue for a long time.

The system that CyanogenMod employ is broken. I implore CyanogenMod as an organisation to take a look at the method that Mozilla employ. Alpha (Nightly) testers are first class citizens and thus able to file bug reports and provide regression ranges. Mozilla are able to test different things on different days ensuring that by the time of beta (M) releases, they're shipping the best product possible.

I fully understand that this device is behind the curve given the maintainer issues but a closer working relationship with the community and welcoming patches from casual developers would be a way to lighten the workload and expedite the process to stable releases. Every OEM at this point has released 4.2.2 while CyanogenMod, particularly on the M7 continues to have basic issues. Take for example the audio stutter as the device locks after a phone call, another thing that simply isn't on the radar of you guys.

CyanogenMod has taken a Google approach to testers but without their resources, the Mozilla result is a much better fit. How would it not be in the best interests of CyanogenMod to be able to test five different configurations of say the proximity sensor or the loudspeaker in a week and get as wide a feedback as you have nightly testers on hand as opposed to one configuration per month and hoping for the best?

There needs to be a better way than what is currently employed, especially as currently I personally have people asking me "have CyanogenMod still not fixed that? It's been months". If more people are needed on JIRA to triage bug reports, believe in the community, people will step forward. Personally I'd love it if CyanogenMod could leverage us, the community to it's full advantage and thus place itself in a position where it could make a yearly commitment to bring the top three flagships to stable before they're replaced (i.e. the M8 is released).
[One (M7) Original Android Development] KaZo58:
Everything will end soon. M7 is ~1 year old and most of us will switch again (don't tell me u'll use it 2+ more years.) and this devices support will lack. There will be updates, but not so much device related updates. It'll take too much time to fix it all. now i have random soft reboots again. especially after installing/updating one or more apps. and yes the most important function !microphone! isnt working well. i have to call 2-3 times till it works. and explain them about bug on my phone..

Gesendet von meinem One
[One (M7) Original Android Development] cschmitt:
The speakerphone mic issue is subjective in the sense that people who rely on speakerphone say it's broken and those of us (like me) who rarely use it, except to listen to voice mail, say it works fine. My testing shows that only the rear microphone is used for speakerphone, so depending on how you hold the phone it's easy to cover the mic in a way that it doesn't pickup correctly and the remote party cannot hear you. It's flaky, at best.

Proximity sensor work fine on my device (screen goes off with my hand about 2" from the sensor), by I remember a bunch of tweaking on 10.2 because the correct values vary among devices and their sensitivity.

Haptic feedback does occasionally stutter since the switch to msm8960 kernel. I only have it enabled for hardware keys, but those that have it enabled for keyboard use notice the stutter more frequently.

Also, since msm8960 kernel the notification LED sometimes get stuck on solid amber vs flashing, unlocking the device gets it flashing again.

As for support, until M5 the stable builds were based on m7 kernel, so it wasn't possible to report these msm8960 bugs on JIRA.

Also, I'd say that it would make sense to frequent XDA more often if you are a device maintainer because 99% of the casual CM users are going to come to these forums to report bugs and resolve issues, most will never open a bug on JIRA or hop on the IRC channel.

I agree with [MENTION=3958023]sabret00the[/MENTION] regarding the development model for CM, it has worked in the past but there's much room for improvement if CM wants to make a move to a widely used product. A wide tester base that includes many casual users is key, so there needs to be a (user friendly) mechanism for those users to report issues on incremental builds. Maybe that means abandoning nightlies for weekly builds that are more stable and feature targeted so that users can report issues.

Maybe an app built into CM to report issues directly from the device, uploading logcat and last_kmsg and other state that's helpful to debugging the issues.

We do appreciate the work you and other's have put into CM on m7 to bring it to this point, but I'm sure you can see the frustration that exists from long standing issues which are known to the user base but the maintainers aren't aware of or have the appearance of being ignored.
[One (M7) Original Android Development] elherr:
Might the speakerphone issues be due to the rear mic change HTC was forced into by Nokia? I think HTC was able to use their existing stock of dual membrane mic's and then switched to a new model.

Might the difference in microphone characteristics be the reason some people are having speakerphone issues and some are not? Is there any way to detect microphone model in log -- or by serial number? I think I have the dual membrane mic as I purchased the Developer Edition early on -- but am not certain.
[One (M7) Original Android Development] cschmitt:
Mine is any early device as well, manufactured 2013-04-20. There's a thread that outlines checking build date from serial number here, although I don't know exactly when the mic part was switched out.
[One (M7) Original Android Development] elherr:
Serial prefix on mine is FA34N -- so 04/23/2013. I believe HTC was still installing the STM dual membrane mic's at that time, as it was around that date the news broke regarding the court decision.

I've spent a fair amount of time searching for an answer and it looks like no one knows when they stopped using that mic. I'm guessing it depended on when they ran out of stock at a given factory.
[One (M7) Original Android Development] elherr:
FYI. Google Camera has been released to Play.

https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera
[One (M7) Original Android Development] jlongrc:
I'm still having the issue where playing audio through auxiliary cord causes the device to inexplicably freeze. I saw a previous entry about issues with receiving calls when auxiliary was plugged in, but I can't produce any evidence that that is causing the problem. I have successfully received calls in this state.

Anyway, it will freeze the screen in its current state, even if locked (dark screen in this case). I have no way to continue use without doing a soft reset AND booting into recovery to do system reboot from there.

It doesn't automatically do this any time I use auxiliary cable, just at what seems to be random intervals that might be hours apart.

Note: using 4/15 nightly; persistent issue over a month or so of updates.
[One (M7) Original Android Development] tiny4579:
Hey peoples with speakerphone issues,

Try out this build and see if speakerphone and camcorder pickup are improved.

http://goo.im/devs/tiny4579//m7/cm11.0/cm-11-20140417-UNOFFICIAL-m7.zip
[One (M7) Original Android Development] sabret00the:
Only 101mb?
[One (M7) Original Android Development] :
4 me 207mb :cowboy:
[One (M7) Original Android Development] sabret00the:
Would I be correct in saying you're using the normal microphone instead of the rear microphone? There's a ton of reverb and stuff.

---------- Post added at 10:54 AM ---------- Previous post was at 10:54 AM ----------

Thanks, redownloaded.
[One (M7) Original Android Development] sirholm:
Works perfect, been missing this ;)
[One (M7) Original Android Development] tiny4579:
It's only using the primary mic in this build instead of both so no echo cancellation.
[One (M7) Original Android Development] alangrig:
So guys, I've installed Google Camera and enabled second mic in video recording. Now seems it's finally stereo.

Video record with mono audio:

https://docs.google.com/file/d/0B0ShSS7ttaI8Q2wxdFZhOWJhU1E/edit?usp=docslist_api

Enabled second mic (stereo audio):

https://docs.google.com/file/d/0B0ShSS7ttaI8N3lJLWdVcGN0ZzA/edit?usp=docslist_api
[One (M7) Original Android Development] cell30:
I've started losing my Voice+ icon on dirty flashes. It remains set to whatever I had it set to prior to flashing, however. I can (usually) get the icon back by pushing the apk. Any idea on why it's disappearing in the first place and/or how to prevent it, apart from not dirty flashing? Are the Voice+ settings accessible from anywhere other than the icon?
[One (M7) Original Android Development] elherr:
Crash/spontaneous reboot on 0416 whilst attempting to place call via Bluetooth head unit in car (Parrot Asteroid).

last_kmsg --

https://db.tt/XzmfPMfr