yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] xetrev:
Everyone says it sounds like i am in a wind tunnel.

11/24 had some commits that might of fixed it. So far so good with that build for me.
[One (M7) Original Android Development] thegh0sts:
will see how the 11/28 nightly turns out...if there's one coming.
[One (M7) Original Android Development] iamnotkurtcobain:
Just here to say hi to [MENTION=3208754]codeworkx[/MENTION] ;). Long time no see. Cm development on the 9505 S4 without you is bad as ****. No progress and bug fixes at all. I'd like to through it against the wall and stomp on it. S4 development needs you but I know you aren't coming back. Ich versteh dich..

Gesendet von meinem SGH-M919 mit Tapatalk
[One (M7) Original Android Development] sabret00the:
He's on extended leave from development on this device too. So no development by him here for now, though he's due back next month and will no doubt appreciate your kind words.
[One (M7) Original Android Development] sweetnsour:
Don't mean to burst your bubble, but his last post (in another device forum) says he will be back Q3 of next year.
[One (M7) Original Android Development] thegh0sts:
then i wonder who is doing the development???
[One (M7) Original Android Development] sabret00the:
We've not had any device specific development for a while. Hence the outstanding rear microphone problem, no YouTube audio in call, etc. But we're lucky however to have a phone whereby the variants have largely the same hardware.
[One (M7) Original Android Development] thegh0sts:
sigh! looks like CM11 might be a ways off :(
[One (M7) Original Android Development] iamnotkurtcobain:
Q3 2014??

Gesendet von meinem SGH-M919 mit Tapatalk
[One (M7) Original Android Development] sweetnsour:
I believe so:
[One (M7) Original Android Development] thegh0sts:
i wonder who will be doing the development in the mean time?
[One (M7) Original Android Development] :
intervigil (Ethan Chen) is working hard on the m7 according to gerrit, and have done so for a long time.

A few other people are also contributing, so there are quite a few people still developing for the m7.

If you check review.cyanogenmod.org you'll see all the people contributing.
[One (M7) Original Android Development] :
Can I Signed

CM 10.2 runs perfectly on the One, and CM 11 it is just,

I do not know why some cry here = Kindergarten :rolleyes:
[One (M7) Original Android Development] scutworker:
Because it doesn't run perfectly. It runs very well and, like most people on here, I am eternally grateful for what everybody has done/is doing/will do, but there are niggles like the notification volume and people want to know if somebody is sorting it out.

Until the previous post (about Ethan and others still working on this rom), I thought it was all over, I didn't know people were still working on it.
[One (M7) Original Android Development] sabret00the:
Not being able to have a phone on loudspeaker nor resting upon your shoulder is hardly working perfectly.

I always find it baffling that guys like you exist in the nightly community, but then again you're the product of CyanogenMod as an organisation, whereby they frown on bug reports for nightlies. Much the contrary to say Firefox, whereby reporting bugs and regressions for nightlies are what actually cut their workload due to making it easier to find regression ranges and isolate causes.

As has been mentioned, Ethan Chen has been putting in work, however he's the official maintainer for either the AT&T or Verizon, I can't remember which. If the problem isn't evident in the model he's maintaining and has access to, without people discussing the issue, how is he or others supposed to know these issues exist? This is a community, we join together in our efforts to confirm issues and if it be within our skill set, fix them. If that's what German Kindergarten is like, I'd like to spend my life there.
[One (M7) Original Android Development] thegh0sts:
yeah, I am just concerned that the development might stall and that won't be good.
[One (M7) Original Android Development] LorD ClockaN:
Why don't you flash it and see for yourself?? Ain't that hard to do backup in nandroid and restore if you aren't satisfied

Don't know exactly what features because I wasn't on cm for 2 years now, but I follow their gerrit.

~~ Flowed from my HTC One ~~
[One (M7) Original Android Development] :
Thanks for the wise and kind response :silly:

exactly what I'm looking for a long time ...
[One (M7) Original Android Development] sardroid:
3107 build link: http://m7.ikbengek.be/files/cm-10.2-20130731_726-UNOFFICIAL-m7ul.zip
[One (M7) Original Android Development] kilian7th:
Is the sounds problem solved during listening to music from classical headset with the 20130731 nighly ?

Thanks a lot
[One (M7) Original Android Development] razer1224:
Many Users Reported its fixed

I will be Either on my GE ROM or CM-10.2
[One (M7) Original Android Development] johnblundon:
I'd also like to know this, it's the only pain in the @$$ bug for me so far LOL other than that it's my daily driver so far, love this ROM, super smooth!
[One (M7) Original Android Development] synthiis:
Oh wow. Thanks for blast from the past.

Just flashed 07/31 and I noticed that the google search bar on the top has a little something... hmm. different. Click on it and..

Welcome back to Froyo, *****es!
[One (M7) Original Android Development] Longun:
Daily drive on a first release, unofficial rom. Top work. Very impressed.
[One (M7) Original Android Development] Radeon1337:
Something is eating up my storage, i suspect it is my old photos, music and so on but i cant find it anywhere on my phone? Any suggestions?

I did a factory reset when installing.

Only 11gig available after installing cm 10.2 31/7-13

Edit: hidden pics

Thanks
[One (M7) Original Android Development] v1r0x:
On CM your "sdcard" is mounted to

/sdcard/0

Use a root explorer or adb shell and have a look at /sdcard. There should be all your old folders/files
[One (M7) Original Android Development] heartsaver1859:
Where can I find the latest builds?

Are there any links on the official CM page?
[One (M7) Original Android Development] cdordon:
Really? Look at the thread title. UNOFFICIAL. Look five posts before yours. The 7/31 nightly link.
[One (M7) Original Android Development] DJW6927:
Please please please please let the Bluetooth audio bug get magically fixed somehow......

Sooooo want to get back onto CM/AOSP builds. I know it only a phone and I need to get out more... but its actually starting to do my head in.
[One (M7) Original Android Development] Radeon1337:
Thanks for the tip :)

But it wasn't there.. Found it though in /mnt/shell/emulated

Also i found out that i lost root after flashing 10.2 but i fixed that with a quick dalvik wipe :)
[One (M7) Original Android Development] kilian7th:
Answer: seems to be better but everything becomes laggy and without sound when you use the keyboard :( listening to the music with a headset
[One (M7) Original Android Development] v1r0x:
Sorry, my bad. /mnt/... is what I meant ;)
[One (M7) Original Android Development] mrjaydee82:
I'm on 10/31 to give this thing a test drive...so far I'm really impressed... Anyhow I've read some having su issues..I'm on the same boat..what are you all doing to get su to work? Trying to run titanium backup
[One (M7) Original Android Development] formula84:
See next post...

---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------

Above quote is for after you get root and titanium gets hung during restore...

Below is for root issue...

Go to settings -> about -> tap build number enough times to unlock developer settings -> then back to settings -> developer options -> change root access from apps only to apps and adb. Problem solved.

BTW I think the issue is that before all of this is done and you go to superuser from settings it shows it already set to apps and adb, but developer options shows it for apps only... Is like the 2 settings are conflicting.
[One (M7) Original Android Development] kilian7th:
Seen many times on this subject...

I install last super su from chainfire--> developper options --> root access--> adp and applications, after that i was able to update super su... I restarted and it was ok.
[One (M7) Original Android Development] tonyec7:
Battery is actually amazing on this. Theres some bugs, but i can definitely live with them. Its only gonna get better anyways :)
[One (M7) Original Android Development] sabret00the:
As I said, we have three variants with maintainers for them, so we should be fine to piggyback their work to KitKat. In fact, I've just seen that Ethan Chen has been assigned to sort out the noise cancellation/loudspeaker problem for the M7UL, so fear not.
[One (M7) Original Android Development] cschmitt:
Have you opened a case for this issue in jira against the RC1 build? If not, doing so might give the issue more attention to get fixed.
[One (M7) Original Android Development] thegh0sts:
Interesting, the advanced menu is still showing even when i have the lockscreen on.
[One (M7) Original Android Development] tiny4579:
That's normal if you have security off on your lockscreen.
[One (M7) Original Android Development] thegh0sts:
errr....no, it should not show the recovery option when at the lockscreen with the advanced reboot option in the dev options on. the whole point was to stop people other than the owner from doing anything unauthorised.
[One (M7) Original Android Development] xetrev:
Still no movement on this :(
[One (M7) Original Android Development] tiny4579:
You're right but I saw a patch that changed it to show advanced options when lockscreen is not secure. Try turning on a secure lockscreen if you don't believe me.
[One (M7) Original Android Development] thegh0sts:
hmmm...ok, so you're saying that the slider type lockscreen is considered to be not secure - makes sense in a way.
[One (M7) Original Android Development] fohdeesha:
I really don't mean to be a **** here and I'm sure the few active devs we have are doing a great job, but does anyone else find it odd we own arguably the MOST popular flagship android on the market right now, yet have development so slow we don't even have a fully functional phone nearly a year into development? I can't tell you how embarrassing it is to be at a conference and asked to put my phone on speaker, and having to tell them "sorry, this $600 Android I just bought doesn't have working speaker phone"

I never thought I'd actually consider flashing back to stock on a phone this popular :/

And yes, as far as I know the speakerphone, mic volume, MMS, and other audio issues have had jira tickets open since day one of RC1. I have to agree, the novel idea of barring bug reports on nightlies just shoots you in the foot. I can't think of any respectable dev team that does this, it's quite clear it just piles up undiscovered bugs until you've already built on them for months

Here's the part where you tell me this is a dev forum, how lucky we are to have any development at all, you're a really cool guy and police the forum like a proper boy, blah blah blah. I've made numerous donations and contributions here over the years, and the dev community is nothing without end users that actually consume and report (when you let us) on your product, and in the meantime pay for your beer
[One (M7) Original Android Development] tmckenn2:
Steve kondik did do a ton of work on the m7 when some of the big bugs couldnt get worked out. i think he mainly runs an s4 but every once and awhile he will sit down and hammer out all the bugs. its because we are such a popular device that we even get that
[One (M7) Original Android Development] sweetnsour:
I somewhat agree. Really thought development, especially CM development, would be very active.

But, we have to respect the maintainers and developers. Must be difficult to balance both active rom development and daily lives (which by itself can be hard enough).

And you have to consider the situation. As far as I know, there are two parts to CM development. One is more general (as in development of CM itself). The other is more device-specific, of which our device maintainer is responsible for. The problem is, our device maintainer is inactive.

Looking at the changelog, development of CM is still ongoing, obviously. It is just the device-specific stuff that's missing, and that is why the bugs are present. I believe intervigil (Ethan Chen) is also working on the m7, but I recall him saying he doesn't have a texting plan or something of the sort, so fixing MMS would be difficult.

In the end, it's not really CM's fault. But then again it's not the maintainer's fault. Sure he is responsible for our device, but he has quite a job to fulfill, and as AFAIK it is only him (codeworkx) and intervigil (not the entire CM team) working on our device.

Sidenote: I had CM on my previous device and looked forward to flashing it on my HTC One. Couldn't live with the bugs, so I flashed a GPE rom and used GravityBox to bring back some features found in CM. Maybe it's something that you might want to look into until the bugs are ironed out.
[One (M7) Original Android Development] fohdeesha:
Well that's the thing, I REALLY respect what devs and maintainers we do have, and I'm sure they're busy working on this way more than they should be. And of course we all really appreciate that. I guess what leaves me dumbfounded is that the flagship, arguably most awesome phone on the market now has....one active dev? I'm seeing far more commits to the CM distro for my Desire, which is an ancient phone that nobody owns anymore. It's just a weird situation were in :eek:
[One (M7) Original Android Development] Chezbel:
Because the older phones have been around a long time more people have had time to gain experience working with them. For the newer phones it may take time before there are a significant group of people that both have the time and are comfortable working on them.
[One (M7) Original Android Development] mynameisjon:
You would think that now that they've incorporated and he's essentially an employee, they'd pay for a texting plan for them to fix it.

The "they're not getting paid to do this" excuse doesn't quite fly now since the maintainer in question is actually getting paid to work on CM.
[One (M7) Original Android Development] tiny4579:
Is there a source that he is employed by cyanogen? Not every cm maintainer works for cyanogen the company. So you're saying now that cm is a company they're getting paid to fix our requests? I'm not sure which aspects of the employers are covered by the company. I hope you're not trying to feel entitled.

I thought there was a fix for the mms issue. Maybe it didn't fix it or it wasn't pushed to cm10.2 and cm11 both.
[One (M7) Original Android Development] GuyInDogSuit:
MMS works fine for me, I don't know why there's any argument over it.

As for the development maintainers, someone else will come along and pick up where we left off. Intervigil was working on CM for the Amaze, and that one had bugs up the wazoo for well over a year. The One is much more stable as a daily driver in comparison. So what if it's taken a year to get this far? It's better than nothing.
[One (M7) Original Android Development] mynameisjon:
It isn't that difficult to find out that he's employed by Cyanogen. Right there on the Cyanogen page, he is picture with the team, has a photo on the page and has a job description "software engineer" who "[works] on growing our list of supported devices".

If a maintainer doesn't work for the new company, I wouldn't fault him/her for not wanting to spend money on a texting plan to test texting fixes.

I'm pointing out the following:

1. As an employee now, he does have an obligation to fix the software. It's no longer a hobby, it's now his job.

2. Since it is part of his job, it isn't too far fetched that the company should pay for a texting plan, or reimburse him for the cost he incurs from testing the fixes.

This has nothing to do with "entitled users". There isn't a "they have day jobs, they do this as a hobby" excuse anymore. If the team decided to incorporate, then it stands to reason that they should be held to the standards that we hold corporate entities and their employees.

I don't use MMS/SMS, so I'm not hankering for a fix. If it comes, it'll come. I'd much rather the rear mic issue get solved (or maybe it already has and I haven't noticed). I was just pointing out a flaw in the logic of the post that I quoted.

I have the utmost respect for developers and the work they do, but I think that if said developers are going to form a company, they should then be held to the same standards and open to the same criticism that other software companies are held to/receive.
[One (M7) Original Android Development] tiny4579:
[MENTION=2370820]mynameisjon[/MENTION],

You have valid points. For tracking purposes the bug reports need to be tracked on jira for milestone and rc builds. This has been the policy before they have gone corporate and I don't think this has changed.

This will ensure issues are addressed when possible before stable builds. Nightlies can and will have bugs. Rc builds should have few to none.

Not trying to keep an argument but niglites are as is. Hopefully the next rc will resolve the Mic issues. I haven't really noticed it much myself but I can see how it'd be annoying for speakerphone issues.
[One (M7) Original Android Development] xetrev:
the loudspeaker is a deal breaker for me. there was a patch on 11/24 that helped out but there are still issues.
[One (M7) Original Android Development] GuyInDogSuit:
If they incorporated, how are they paying their coders?
[One (M7) Original Android Development] mynameisjon:
I think those reports have been on jira no?

While I can see the logic behind not allowing bug reports in CM, when was the last time we've seen a stable release for CM? I think the last time I flashed a "stable" release was on my Nexus one.

Given the cycle of Android version updates and the general unwillingness of OEMs to provide source, imo nightlies/RCs are as good as we're going to get.
[One (M7) Original Android Development] fohdeesha:
Because it's not working fine, and only stops working when you go over 5 or 6 people in a thread.

You're probably just not popular enough to run into it :angel:
[One (M7) Original Android Development] jasalta387:
Exactly this happens to me. I thought first I should give it some time for the developers to solve it. But this issue has been since day one in CM and noticed by the community since... I'm afraid I'm forced to look for alternative ROM on my One.
[One (M7) Original Android Development] kennypow3rs:
Omni 4.4.

My comment has just closed this thread. Nothing else to see here. Move along people.
[One (M7) Original Android Development] cschmitt:
Happens with every release, CM10.2 goes quiet and there's panic. Meanwhile dev's are quietly plugging away on CM 11.0. Patience.
[One (M7) Original Android Development] gmfeny:
Lol damnnn
[One (M7) Original Android Development] GuyInDogSuit:
A few weeks ago I tried sending a message to eight people and they all got it. :confused:
[One (M7) Original Android Development] gmfeny:
Well stop buying them beers maybe that's why they can't fix anything
[One (M7) Original Android Development] fohdeesha:
It's not the sending that we're all having trouble with it's the receiving. In a group of 5 or 6 or more, I and others won't receive texts from one or more of the parties. Occasionally texts from certain parties will actually crash messaging all together when they do get received
[One (M7) Original Android Development] GuyInDogSuit:
Oh, ok. I usually get them in single-person messages, so... yeah.
[One (M7) Original Android Development] sabret00the:
It's looking like our next Nightly will be KitKat flavoured.
[One (M7) Original Android Development] cschmitt:
Exactly, it's not flat out broken but instead there are randomly blank received mms group texts. In one thread I received 2 blank messages and then the next message from the same sender came through just fine.

Plus, if I open the same thread in Textra the entire thread is readable!

Definitely a content type issue as both the stock messaging app and Textra use the common mms database and the text of the blank messages is present in the database.
[One (M7) Original Android Development] GuyInDogSuit:
Where'd you hear this?

Also, the latest build is listed as stable. It's not a nightly, snapshot or release candidate. It is simply, "stable."
[One (M7) Original Android Development] sweetnsour:
http://www.cyanogenmod.org/blog/cyanogenmod-10-2-0-release
[One (M7) Original Android Development] GuyInDogSuit:
So we should be seeing CM11 soon, from the sound of things.
[One (M7) Original Android Development] sectorek:
i hope so too! :)
[One (M7) Original Android Development] gr4p3s:
Does IR work? I have the Smart IR app but I can't get it to detect my TV or the signals from my remote control.
[One (M7) Original Android Development] metalk9:
Lol, how can this be stable when the speaker phone is still broken?
[One (M7) Original Android Development] wikie:
I would also like to Knowles?
[One (M7) Original Android Development] TheEgonSpengler:
I don't have this speaker problem. Are you dirty flashing?
[One (M7) Original Android Development] metalk9:
Read a few pages back, it's a known bug.
[One (M7) Original Android Development] thegh0sts:
must download the stable once BF4 finishes updating :p
[One (M7) Original Android Development] kennypow3rs:
Too bad on my Xbox one playing BF4 I get kicked to the dashboard 20 times a day. :(

I installed the stable to test it since the last time I was on cm was back at the beginning of Oct. They've made a lot of progress. I assumed I grabbed the stable but my ROM says theres an RC1 out?
[One (M7) Original Android Development] TheEgonSpengler:
Yes I also read the thread.

This bug is one I can't reproduce on the current versions. I just tried it again - still working on nightly Nov 28
[One (M7) Original Android Development] cschmitt:
The RC1 build is from a couple of weeks back, you're on the latest stable. The sort order in CMUpdater is jacked up and shows the RC1 build above the more recent stable release.
[One (M7) Original Android Development] jasalta387:
I'm on stable, was on 11/25. The speaker phone reproduces for me as follows: in a phone call put your One on speaker. You will hear perfectly while the other side will barely hear you.

The same happens on a Hangouts video chat.

EDIT: just played a bit again. I found out that when on speaker, the active mic is the one next to the rear camera, not on the lower side (like when having a normal conversation). Still the quality of the sound on the speakerphone mode is not that good...
[One (M7) Original Android Development] tiny4579:
I wonder if there's a jira ticket for this and if there were one prior to stable it seems serious enough not to release stable on this bug.
[One (M7) Original Android Development] sabret00the:
Add to that the fact that the rear microphone when noise cancelling cancels out your own voice when in normal calling mode and sitting on your shoulder.

https://jira.cyanogenmod.org/browse/CYAN-2801
[One (M7) Original Android Development] metalk9:
I haven't been on cm for awhile because of this bug. Volume from the mike on speaker phone was either very low, or completely distorted by static. Have just tested again on stable and while the static seems to be gone, the volume level is still unacceptably low. Incidentally, the issue is also present in the unofficial CM11 builds.
[One (M7) Original Android Development] GuyInDogSuit:
There was another nightly build but it doesn't have a whole lot of changes. Has anyone tried any of the non-CM 4.4 ROMs? I keep coming back to CM10.2 because the KitKat ROMs have bizarre issues for me like not having root even after flashing Superuser again, games force-closing, and Calendar not syncing at all.

I'm gonna give Trip N Droid another go. It's been updated quite a bit since I last tried it. Omni ROM might be a second choice.
[One (M7) Original Android Development] fohdeesha:
where are you guys seeing the build marked stable? still showing all nightlies

http://download.cyanogenmod.org/?type=nightly&device=m7ul