yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] IronTechmonkey:
It is just to the right of the speaker, between the speaker and a sensor that is a bit larger than the LED. It can be seen if you shine a flashlight at front of the device, and you can invoke it like so: "Settings' - "Display & Lights" - "(Lights) Notification Light' - enable slide switch - tap "Dafault" or " Normal/Custom" and the light should blink... but only once so keep watching. For notifications (text messaging) it seems to blink at relatively slow intervals of 1 second each on then off etc. I can invoke it and control flash rate with Taker but only in white.. I did not test to see if the ROM's native settings can control flash rate but they should be able to do so.. Perhaps someone could give that a go. Also, I thought I saw a display LED while screen on" setting somewhere but cannot find it. Could have been a dream.
[E 2015 Original Android Development] sinnerz2000:
I'll give it a try. Display led while screen on is under display&lights>notification light on my redmi 1s cm12.1, see if you can find it there on otus.
[E 2015 Original Android Development] IronTechmonkey:
Maybe you heard the forehead slap from there --- I missed a tree but for the forest. LED with screen on works

Oh, and it is probably worth noting that I'm using a Moto E XT1511 (2015, 2nd Gen, US, 3G). For hardware specific things like this there may be variations across the different devices within the phone family sharing a ROM. Moto E is up to 10 models of which at least 4 are covered by this ROM... I supposez.
[E 2015 Original Android Development] IronTechmonkey:
Here are some issues I've been chasing in this ROM, some of which have been tested and reported in different ROMs but those bug reports don't carry over to our young and very active list of commits.

Testing on 9/12/15 otus nightly with newest (July/August 2015) CM Gapps flashed by TWRP 2.8.7r2 onto Moto E XT1511 (2015, 2nd gen, US, 3G). Note that this phone has no flash.

CAMERA MENU MESS - phantom menu item for flash appears under certain conditions. I can reliably reproduce this and have screen grabs but no logs yet. Will create Jira ticket once I have logs. This test assumes that the camera has not been run and is not in cache or recents, and that HDR is set to off.

- Open Camera app

- Tap Menu button. Bottom slide-out options include 4 items in this order Timer, Grid, HDR, Front/Back.

- Tap HDR. Now fifth icon for flash appears between HDR and Front/Back but it is greyed out and inactive.

- When HDR is tapped again, the newly appeared flash icon becomes live and now will change as tapped but of course has no effect.

- Other actions which change the state or arrangements of the icons such as switching between rear/front camera will reset the menu bar.

----------------------------------------

OTHER STUFF - I'd be interested in knowing if anyone else has experienced any of these quirks, some of which have been seen in other ROMS and which I see in Otus..

- There is no way to close expanded notification prompts while leaving notification open where tapping the notification closes something you want opened. Some notifications will expand when swiped to offer an option related to that app. In CM11/KK the expanded part of the notification could be closed by dragging down then up on the notification. The functionality to close expanded part of notification is gone and the only way to do so seems to be screen off/on by power button.

- Countdown timer runs up to 30 seconds past 0 before sounding alarm. This also occurred in CM11/KK and earlier L versions and we had a Jira ticket for it. Need to test for it more in CM12.1/L5.5.1.

- Huge pop sound switching from headset to speaker in FM radio - I mean just tapping the software switch without moving any cables or connectors. Seriously - ouch, and it seems like there would be a way to avoid this progammatically with a temporary mute. There was an FM radio commit in the 9/15/15 nightly but I don't see how that would affect these issues.
[E 2015 Original Android Development] squid2:
I see you're on a bug hunt.

Phantom Flashlight Icon - I couldn't reproduce it with the steps you described, and I've never experienced it. To be honest, I don't think many people care about this, even if it happens under some special conditions.

Notifications thing - I don't fully understand your issue, and in any case it's a CM thing, not related to any of my work. You can open a ticket with them if you really want to.

Countdown timer alarm - works perfectly for me, alarm starts at the right time

FM radio headset/speaker switch high volume burst - this is the most relevant issue you mentioned. I had never tried switching from headphones to speaker until you mentioned it here. Indeed, I consistently had a burst of very loud audio for a few hundred milliseconds when switching between the modes. This issue is specific to otus (and maybe condor, I don't have the device to check). It doesn't happen on osprey at least. Something will probably need to be done in the kernel to fix it, I've seen similar things done elsewhere for this type of issue. As to whether or not I'm going to fix it - I might look at it at some point, but it's on my backburner for now. These kinds of kernel issues can easily take a whole day to troubleshoot and fix, and I don't have time for that right now, as I have more important things to do. If you want to try digging into the kernel and fixing this yourself, you're welcome to do so and I'll appreciate it greatly, but for now, I don't have time to deal with it myself.
[E 2015 Original Android Development] IronTechmonkey:
Yep, a sort of accidental one or rather; a re-visitation of issues discovered over the past year in different CM based ROMS on a Moto AHD/MB886, in some cases during time when official bug reports could not be filed and other times with official reports investigated by devs but unresolved..

True that. Most folks wont care about this one. Still, next time a nightly has some interesting commits I'll clean flash, test in the lean ROM with no gapps or config changes and file a Jira ticket for this one. I don't know the Moto E family hardware yet (and we are up to 10 models). Does yours, or any others, have a flash for the camera? If your camera has no flash try switching camera to front and back before the other steps I suggested.

I thought all of these things would be CM issues and put none of it on your stuff. To that point this one has been in every version of CM/L12.x.x that I've tested. In the attached picture the option to disable Tasker (something I don't want to do because I have a dashboard system that uses it) becomes visible when the Tasker notification is swiped down. In CM11/KK that secondary part of the notification could be closed by swiping down and back up on the primary notification. That no longer works but is an admittedly low priority.

This bug is notoriously hard to replicate. I thought it occurred while I was testing other things but if what I saw was correct it is still there. In the past logs showed that it was happening and devs were looking at it but a reliable way to reproduce it was never found.

Just reiterating that I posted this stuff with no expectation of dumping it on you to fix. It sounds like this one is not worth a CM bug report. I'm not up to kernel tweaking yet but might use this as an excuse to explore, sez I completely noncommittally.

Thanks a bunch for the base ROM, the feedback about CM issues, and a bit of education about the FM radio.
[E 2015 Original Android Development] Dexter_S:
Finally I flashed this rom. Yes, I was being a chicken & waiting for a fully stable release. I have flashed the second official nightly. And I'm completely satisfied. No major bug whatsoever. The camera flash icon appears but nothing problematic. One thing I've noticed that GPS takes a while to lock on high accuracy. And one request for you, even if I'm not sure if it's possible. I'm from India & Motorola incorporates a service called automatic sim selection, which is rather helpful for dual sim devices. If you can include that service in any future release, will be greatly appreciated. Aside that, thank you for all your hard work.
[E 2015 Original Android Development] IronTechmonkey:
For what it is worth by reassurance, the one of Squids recent builds I tested performed as well as the 9/12 official nightly I'm now running. Thanks for confirming the flash icon bug. Even though that one seems minor now, similar hardware specific confusion in other areas could cause badness so I've got it on a list of things to test, log and report during my next clean flash.

Meanwhile there is yet another glitch or (poorly understood feature change) at this Wifi.setting here: "Settings" - "Wifi" (enable wifi)- Menu/3Dots - "Saved networks" - Menu/3dots - "Automatic Priority" - enabled

- With this set to enabled I can connect to either of my wifi routers (whichever has stronger signal?) automatically by just enabling wifi, or manually by selecting a network. - as expected..

- If I change "Automatic Priority" to disabled (remove check) I cannot connect to any "Saved" network. Tapping on them and then tapping on Connect does nothing.

- If the saved wifi connection is forgotten, then next attempt to connect, this time with manual authentication, is successful.

- After disabling and re-enabling wifi, the newly created wifi connection becomes saved can can not be connected to. :Lather, rinse repeat until...

- If "Automatic Priority" is enabled again saved networks connect automatically or manually as they should.

In CM11/KK the analogous user accessible wifi prioritization function was done without an auto-priority switch but rather by manually placing your previously connected networks in the order you prefer. It looks like something got messed up in the transition to this new method. I'm seeing this in the 9/12 nightly but there have been no wifi related commits since then that would fix this so, it can go on my clean flash test list. Is anyone else seeing this one?.

Also - Lots have folks have wished for this one http://review.cyanogenmod.org/#/c/109614/ which should be in the next post 9/16 nightly. Sweeeeeet.
[E 2015 Original Android Development] Carlos Arriaga:
model xt1511 the ROM is 100% stable, have not had any bug. everything works great job [MENTION=6485916]squid2[/MENTION]
[E 2015 Original Android Development] IronTechmonkey:
As you've declared the ROM to be 100% stable, without bugs, and with everything working I must ask;) Have you actually tested for previously reported issues or are you saying that you have not happened to notice them under normal use? The reason I ask this is because, from what has been seen of these bugs so far I believe that they would be easily reproducible on another device of the same xt1511 model type if actually tested for. The flash icon bug, confirmed on 2 devices already, clearly exists although is a minor issue. The Wifi setting issue may be a real bug with negative effect on WiFi connectivity. Have you tested for this one?
[E 2015 Original Android Development] EsromTech:
There is difference between xt1511 and xt1506?
[E 2015 Original Android Development] IronTechmonkey:
I think the XT1506 and the XT1511 are the international and US versions respectively of the same 3G model.

Moto E, (2nd Gen), 3G, XT1511 - for USA

Moto E, (2nd Gen), 3G, XT1506

There so many Moto E models (at least 10) that I compiled a model # list here: http://xdaforums.com/moto-e/general/moto-e-model-list-t3195889. There is a link to more product info there as well.
[E 2015 Original Android Development] EsromTech:
thanks for the answer...

But cm12.1 this topic serves to xt1506?
[E 2015 Original Android Development] IronTechmonkey:
Ah, it sounded like you were asking about a general difference between the 2 devices rather than about their compatibility with the ROM. Squid2 has confirmed here http://xdaforums.com/showpost.php?p=62713888&postcount=236 "it supports XT1505, XT1506, and XT1511 ". That makes sense because those are the 2015/2nd Gen/3G versions which would use similar hardware. Happy flashing :).
[E 2015 Original Android Development] sinnerz2000:
Got a first update for stock ROM on XT1506 today, seems to be just a stability and stage fright patch of only 12mb, why is it so hard for moto to update otus to 5.1?
[E 2015 Original Android Development] IronTechmonkey:
A nasty vulnerability in all versions of L was discovered or at least made more widely known this week. Something about using repeated cut and paste of text entered into the emergency calls only dialing screen to overload and gain access. I wonder if that is what Moto is patching. Do they have specific details of the update you mentioned?

As to it being hard for Moto to update...they are moving much faster now than they did while having to navigate around AT&T and other provider's failure to act in the past (and the new stock no-provider OS is lean and crisp) . Moto roll out of 5.1.1 already seems to be in the staging phase so....
[E 2015 Original Android Development] sinnerz2000:
Nope, in the release notes only stage fright was mentioned.

I'm using the XT1506 which is the one sold in India, we don't have carrier locked phones here so technically moto has no carrier restrictions here to release their updates.
[E 2015 Original Android Development] Casper1982:
Someone use this MODsound in this rom?

for xt1506 ..

http://xdaforums.com/android/apps-games/mod-dolby-atmos-t3109446/post60763157#post60763157
[E 2015 Original Android Development] IronTechmonkey:
Thanks for the explanation. It's a bit late to be addressing stagefright but at least it is being done. I have the XT1511 which is the US equivalent to yours so I'm hoping we won't be far behind the updates for yours particularly 5.1.1 when that comes along..

[EDIT] and this is why I think it is in the works https://motorola-global-portal.cust...sion/L3RpbWUvMTQ0MjUxNTYxNi9zaWQvcVozRmJKd20=. Even though I'd stay on CM it is nice to be able to go to stock in case CM hits a rough spot (like google services induced wakelocks etc) and the stock installation image that should become available can be important for those on CM to get back to stock to receive OTAs.

... and it looks like the update has indeed started to roll out to the XT1527 (2015/2ndGen/US/LTE) http://www.androidpolice.com/2015/0...e-is-getting-its-lollipop-5-1-ota-update-now/ but that was months ago...hmmmm.
[E 2015 Original Android Development] EsromTech:
Friends, analyzed the details of cm12.1, I'm about to put this rom in my xt1506, there is a known bug that is not related in post # 1?

Or is as stable as the stock 5.0.2?
[E 2015 Original Android Development] IronTechmonkey:
There are always bugs. That is sort of the point of nightly progressions and these XDA threads:). To keep up on things you can review recent thread posts and the list of commits (change log) that describe various fixes and feature changes.

Speaking for the xt1511 (US/3G) on the 9/12/15 nightly, the ROM is as stable as stock. Stock ran a bit smoother but lacked many features - for instance stock had no LED functionality even though there is an LED. CM uses the LED!
[E 2015 Original Android Development] sinnerz2000:
I really wanna flash this on my mom's phone after reading this but I'm still kinda hesitant since its not my phone. Is it possible to revert back to stock completely later without any trace in case of warranty claim?
[E 2015 Original Android Development] EsromTech:
Unfortunately you will lose your warranty, but you can go back to your stock rom yes.
[E 2015 Original Android Development] IronTechmonkey:
Aa EsromG5 said, you will loose warrantee and you can return to stock.

In more detail - Unlocking the bootloader is what voids the warrantee and cannot be hidden or undone but is needed to install a custom recovery and flash ROMs.

In general, in order to get back to stock just to use it you could restore a nandroid back-up of it (which you would certainly want to create as soon as you install custom recovery) . If you want to go back to stock to receive OTAs then you would use ADB and fastboot to flash stock recovery and stock ROM then apply the OTA. Those stock recoveries and ROM images may not be available until moto upgrades a model to L5.1 (as is the case with my xt1511).
[E 2015 Original Android Development] EsromTech:
First impressions with cm12.1 20150917:

using XT1506

Performance is amazing and certainly not lose to stock 5.0.2.

Battery has a good life, did not see differences between cm12.1 and stock in battery relationship, ie, still pays to be using the cm12.1

Camera with good quality, did not lose quality as we have in other older devices is opening up fast and exchanging photo video at the speed of stock, not to mention still have the best resources.

Applications do not lock to open and not to run them with your time, everything works fine.

RIL without any problems.

[MENTION=6485916]squid2[/MENTION] , Thank you for your excellent work and for letting our even more incredible device.
[E 2015 Original Android Development] IronTechmonkey:
[MENTION=6485916]squid2[/MENTION], While preparing for a bug test build and reviewing the changes you made before the ROM became official (you were busy, and that is surely appreciated!) I noticed this item from May 16, 2015: - "Faster WiFi network detection and connection." I'm not asking for anything here but your take on how something I just noticed relates to what you saw then --- OK, so it sometimes takes a while to connect to wifi with the connection status stalled on "obtaining IP address". If, when it is in that temporarily stalled state, I turn off the screen and turn it back on (by power button) wifi instantly connects. This has me wondering if the phone is confused about it's sleep state in re wifi and curious about what you think.... and if it is worth a jira ticket.
[E 2015 Original Android Development] squid2:
That's interesting. I'll look into it more when I get time.
[E 2015 Original Android Development] squid2:
As a percentage of times you connect, how often does it get stalled? If it happens routinely, then there's something about your setup (maybe your router) that's significantly different from mine. I also haven't heard many complaints about WiFi here. Yes, last time I tested, the average connection time for WiFi on this ROM is 15% higher than the stock ROM, and it might stall once in a while like any WiFi device does, but that is of little consequence.

I just tried it out on my device. I connected and disconnected from my home WiFi 20 times in a row, and it never stalled. It always connected within 6 seconds. Over the past 5 months, I've connected to WiFi networks more than a hundred times, and only noticed a stall/slow connection maybe 5 times. That comes out to being slow to connect under 5% of the time, and the stock ROM for otus and every other device of any kind I've ever used also stalls on WiFi connection a similar amount of times.

I did some looking through the Motorola WiFi driver to see if there were any useful patches in the Moto driver that are not in the newer CodeAurora driver I'm using, but I didn't see any.
[E 2015 Original Android Development] immy28:
Great work.

Now i am on cm latest version .

I have some req. In Other unofficial version stock camera worked . if possible stock camera work is great.
[E 2015 Original Android Development] IronTechmonkey:
Here are 2 issues for which Jira tickets have been requested. If anyone can replicate either of these issues please do got to the applicable jira ticket to vote on it or add information. In addition to the issues themselves we could use some presence there since the MotoEs don't appear in their list yet forcing the use of wrong model in list (among other things that could make reporting tricky).

Phantom menu item for flash appears under certain conditions on device with no flash.

https://jira.cyanogenmod.org/browse/NIGHTLIES-1833

Cannot connect to or manually prioritize saved wifi networks when Wifi "automatic priority" setting disabled https://jira.cyanogenmod.org/browse/NIGHTLIES-1832

[EDIT] Found a few more

-------------------

SOUND PANEL CLOSE

When the sound panel is shown there is no safe and consistent way to manually close the sound panel because items displayed "beneath" it are live, so back button will leave app, home button will go home, etc as if sound panel is not opened.

-------------------

DOUBLE TAP SATUS BAR

If not using lock screen (and maybe even then) double tap status bar to turn off display leaves the notification shade and or quick settings in unpredictable state,.sometimes leaving notification or quick settings on the display.

-------------------

Toggle torch option is present in Nav ring options even though phone has no torch.

-------------------

OTUS missing from jira

-------------------

Notification sub option.(Previously described)

-------------------

Countdown timer past zero (needs to be verified - might be fixed)

-------------------

---------- Post added at 07:30 AM ---------- Previous post was at 07:08 AM ----------

[/COLOR]

Thanks for the details and perspective. 2 things of note. 1) I'm spoiled by the fast and very consistent connection speeds I got in stock (2-4 sec) and keep all radios off and toggle wifi frequently even at home base which puts a premium on fast connection speed. 2) I have 2 routers to which I can connect (with one of the routers doing all the actual routing) and prefer one of them. This makes me wonder if the auto priority glitch might actually have caused the more serious stalls of 30 seconds (which are now occurring less). My "normal" time to connect is now about 9 seconds. For small percentages of connection attempts it might stall for up to 15 or 20 seconds or it might connect in 2 seconds. In the human scale the variability adds frustration beyond having a longer but consistent delay. Not worth a Jira ticket.

Speaking of Jira, I created a couple of tickets today for wifi auto priority and camera menu but I did not for the FM radio sound bomb because you mentioned having worked on the radio and I wanted to share with you first. It seems that he reason for the sound bomb there is because; after enabling the phone speaker and then when switching back to when the headphones, the headphone volume is jumping to max.
[E 2015 Original Android Development] IronTechmonkey:
Well, this is kind of bogus, and I am a bit confused about the proper jira "bucket" for this sort of report. I filed these under nightly - bug, but nightly bug is treated like nightly regression in that, CM Jira will only receive reports of things that were working in past nightlys and then and broke. For things that have no known good reference point it seems that a different path must be taken through Cyanogenmod - bugs so I'll resubmit them that way.

[EDIT] OK, maybe I got it right this time.

Cannot connect to or manually prioritize saved wifi networks when Wifi "automatic priority" setting disabled.

https://jira.cyanogenmod.org/browse/CYAN-6969

Phantom menu item for flash appears under certain conditions on device with no flash.

https://jira.cyanogenmod.org/browse/CYAN-6970

[EDIT2 - Goodness gravy. Those 2 were scrapped as well, and I'm still learning. At least I finally got an answer I was seeking since last year. We just cannot file jira tickets until there has been a snapshot (except for things that break between nightlies). Pardon some general venting but, in spite of many declarative and often nasty commands to properly file bugs (not coming from anyone here), with links to posts that supposedly describe the proper way... the information about the general process and limitations there-in is poor. Grrrr! Perhaps I'll work on documentation for that instead of chasing bugs until we've got a snapshot.
[E 2015 Original Android Development] Pr!mus:
tried the latest nightly.. Very stable and buttery smooth.

just one issue I had is low ringtone volume as compared to stock and low loudspeaker volume.

Can u pls fix them in the next build..

TIA
[E 2015 Original Android Development] IronTechmonkey:
Try lowering then raising the volume after you enable speaker phone to see if that improves things. If that helps, you would have to do it each time you are on a speaker-phone call.