yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] IronTechmonkey:
I couldn't resist testing for the scroll bounce-back fix. It is indeed fixed in 10/14 nightly, which is good although certain other scrolling issues persist such as taps occasionally invoking scroll. Still, considering how much time I spend in TiBU it is a nice fix. As to the ROM in general, it is still solidly functional and stable but the list of if minor issues does continue to grow. By way of example, but asking for no testing or dev focus*:

Portrait sized Quick Settings in landscape mode while status bar is in proper landscape. I don't know if this is an accepted limitation. I doubled back to a nandroid backup to confirm It occurs in previous otus nightly but not in previous iterations of CM12 that I've tested.

At maximum native font size = 130%, which is the same as Accessibility Setting for large text, certain elements run off screen. Although large font sizes are often not accommodated in OS development, where it is called an accessibility feature there should be higher priority on making the text fit. There is an existing jira ticket for this but I cannot keep it alive as they wont yet receive any reports for this ROM (except in difference between consecutive nightlys).

*Unfortunately with the focus turning towards M, the generational cross-section of CM12.1 and Moto E Otus may never be as complete as the CM11 or CM12.x ROMs for the MSM8960 of Moto devices. I'm hoping that when this speeding forward skips Lolliflop, that Marshmallow (what a not reassuring name for any product - except marshmallows;)) is a soft landing. Could be a good thing that dev is turning that way in spite of the things that could still be fixed or optimized in CM12.1 (My wifi time to connect is under 2 seconds now). Thanks [MENTION=6485916]squid2[/MENTION] for working on M and L.
[E 2015 Original Android Development] squid2:
More CM13 Progress

I took the okhttp.jar from CM12.1 and I was able to make it boot! It's very far from being usable, but this proves that CM13 can be made to run on this device.

[IMG="CM13 Screenshot on otus"]http://i.imgur.com/NbPtdFY.png[/IMG]
[E 2015 Original Android Development] -FuFu-:
nice :) first step done

and thanks for all your work on this device
[E 2015 Original Android Development] squid2:
CM13 Preview Build

I've had a few people ask for a preview build of CM13, so here you have one: http://www.mediafire.com/download/2ibn5sdzf8bzd76/cm-13-20151017-HACKED-otus.zip

I've labeled the zip as "HACKED" because it uses a hand-modified boot image (CM12.1/CM13 hybrid) to make it boot. It might take longer than usual to flash using TWRP, and it will take a while to boot up the first time. You won't see the "Android is optimizing apps" screen, it will stay at the boot animation the whole time till it's done odexing everything. Don't worry if it seems to be stuck at the boot animation, give it 10 minutes before you give up (it usually boots up in less time, but be patient).

This is a premature build, and most things are broken. Don't tell me that things are broken, I'm not looking for testers at this time, this just an early preview for your own disappointment.

What works: booting, display, wifi

What's broken: RIL, FM radio, camera, MotoDoze, external SD card, everything else

Once again, I warn you that this is a very premature build. Don't flash it unless you don't care about having a working device and are only curious about Android 6.

Also, if you are interested in building yourself, you can take a look at necessary cherry-picks here: https://gist.github.com/sultanqasim/22bca9f7bca4d067b12b

This list is changing by the hour, and may be out of date by the time you look at it, but it's just there for your reference.
[E 2015 Original Android Development] Carlos Arriaga:
Woooo ?? great, downloading thanks [MENTION=6485916]squid2[/MENTION]
[E 2015 Original Android Development] IronTechmonkey:
While testing LMT Launcher's ISAS and while creating some custom OGG alarm clock specific ring-tones I found a few more issues/oddities, which I'll mention in spite of the newfound interest in M *.

Tap=Swipe

A single tap with almost no slide or roll is occasionally interpreted as upward swipe of substantial length. To test for this: Enable "Pointer location Screen overlay showing current touch data" in Developer options, then scroll around in apps where this behavior might be seen. I notice it most in sub windows of Tasker and Total commander, as well as other native activities and installed apps. When the issue occurs with the touch data enabled, a single tap will generate an upward line up to 40% of display height emanating from the tap spot, sort of like a little digital upward lightning bolt, indicating a swipe that never really occurred.

.

Media Scanner Causing Duplicate Instances of Custom Alarm OGG Files.

When placing custom alarm ring-tone OGG files with proper permissions in /system/media/audio/alarms they are seen instantly by the alarm app, then after the device scans for media (such as at OS start) duplicate instances of the items appear even there is only one of each file on the entire device. In CM11 and earlier CM12 for a different device, MP3 files placed in the SD card ringtone directory could be selected and previewed in alarm app without requiring this workaround. Note: This is the only apparent way to add custom alarm ringtone files that can be properly previewed when selected in the Alarm app, which cannot be done when media is selected as music in the native alarm app. Previous iterations of CM allowed the Alarm clock to select MP3s as ring-tones with audible preview.

*

[MENTION=6485916]squid2[/MENTION], Would you be amenable to splitting this thread (where the reference to CM official indicates CM12.1) into separate threads for Otus official CM12.1 and Otus unofficial M/CM13. Doing this would keep feedback and opinions about each from distracting from the other. In particular, now that we have an official CM Otus ROM (thanks to you! :)) it would be a shame to have interest in improving the official CM21.1 ROM drowned out by the enthusiasm for M. It may actually be XDA SOP to create separate threads, and whether or not that is a rule most ROM threads do split at such junctures because it is better for both the maturing ROM and the experimental ROM. It also frees up devs to work on new projects while users tweak lower priority stuff in old one;). If you are willing to do this I'd be glad to provide any grunt or leg work needed to maintain the CM12.1 official thread.
[E 2015 Original Android Development] squid2:
Yes, I plan to make a separate thread for CM13 soon to avoid confusion and distraction. I will continue to maintain CM12.1 for this device as long as required till CM13 is stable.
[E 2015 Original Android Development] Manish_Sky:
That's a good news. You are doing a good work. But i am really curious to know when will it be available (not asking the fully stable version but a considerable one. Dont tell me about premature version)
[E 2015 Original Android Development] IronTechmonkey:
Asking for ETAs may be against XDA rules and is generally frowned upon in Dev forums. Following such a request by stating " Dont tell me about premature version" could come across as rude and a failure to understand the progression of development. I'm not speaking for squid2 or anyone else in particular but keep that stuff in mind. Also, squid2 has done a bit of a magic to get M working at all, and clearly states that it is experimental. The whole point is that it is in an early state of development which is a lot better than none.

It is as if someone just discovered that logs can be used to move heavy objects and you are asking when the wheel will be invented :).
[E 2015 Original Android Development] Manish_Sky:
Well thats a good example. And honestly i didn't know about it i am sorry. And neither i wanted to be rude brother. I think i just asked directly im sorry.

And i'll keep in mind.
[E 2015 Original Android Development] IronTechmonkey:
Groovalicious. Also, I've been providing a lot of feedback without logs, which I'm doing intentionally so there is less perception of an "ask", but I'm glad to test deeper and provide phone details and logs for anything you might be working on in Otus. I'll be staying on CM12.1 as I'm doing all this on my primary and only device (gulp) but once there is a body of evidence indicating that it is safe to flash back and forth between L and M and restore nandroid backups across both I'll dabble in that as well. Grazie mille!.
[E 2015 Original Android Development] ashesshubham:
Guys i hace moto e 2015 otud ... I unlocked bootloder nd also install twrp nd when i start flashing cm 12.1 stuck on patching system unconditionaly every time it stuck on patching system unconditionaly o use clean install wiping all thing but it nothing happen pls tell solution

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

My mobile moto e otus 3g nd stuck on patching system uncontionally what ido i also done full wipe nd same result pls tell my phone model no is XT1506
[E 2015 Original Android Development] IronTechmonkey:
That message is sometimes associated with a corrupted ROM download and I've seen notes that associate it with improper bootloader unlocking, but if you've got TWRP installed the bootloader should be unlocked. The simplest thing to try first is to re-download the ROM file from a different device, then put it on the SD card then install it from there with TWRP.

If that does not work then it makes sense to confirm a few things.

- Do you see the bootloader unlocked warning when you power up the device?

- Can you connect to the device by USB from a computer and reboot it using ADB, or in this case more likely mfastboot?

- What version of TWRP are you using (TWRP version is in upper right corner of TWRP main screen) and is it the exact same one that is linked to in the original post of this thead (which is TWRP 2.8.7 or 2.8.7r2 for 3G/Otus - not the one for LTE/surnia)?.

- Have you confirmed that you can backup and restore successfully with TWRP?

- When you wipe are you doing factory reset only (no playing with partitions and other things)?
[E 2015 Original Android Development] ashesshubham:
Bro every thing is right i m using twrp 2.8.6 test 5 nd i use full wipe nd backup successful restore i downloaded zip 2 times from offical site ..what i do brom nd i not connect throght pc..

Nd yes bootloader successfully unlocked with waring message.. Tell me bro what i do
[E 2015 Original Android Development] IronTechmonkey:
I am more like dad than "bro";). If you don't have access to a computer then how did you unlock bootloader and flash recovery?
[E 2015 Original Android Development] ashesshubham:
I used pc for unlocking bootloader and nd flashing recovery pls help people dont make stupid pj,s..
[E 2015 Original Android Development] IronTechmonkey:
I made no joke. That was friendly advise and good help that you got. If you don't appreciate that someone took the time to research your problem for you and give you an answer then you are welcome to seek help elsewhere. Good luck.
[E 2015 Original Android Development] Dexter_S:
I recently flashed the October 17th build. And although I usually flash the Open Gapps Pico build, this time I opted for the micro build. This includes play store, services, framework, calendar & Gmail. But after that I am facing force close issue for AOSP Android keyboard. I use SwiftKey, so I didn't notice it right away. But today I switched to Android Keyboard & the FC issue started. And the ANR messages are persistent. I have to freeze the damn thing. I flashed the zip again,in vain.
[E 2015 Original Android Development] IronTechmonkey:
I clean flash a new nightly once a week (presently on 10/14/15), always using the CM Gapps (CGapps rather than open Gapps) which is linked to and recommended in the OP of this thread, and have had not problems with keyboard. To isolate any potential Gapps issues... does this issue occur after a clean flash of just the ROM? Beyond that , does it occur when the recommended Gapps is flashed onto the ROM and tested before installing other apps? Side note: At first I was hesitant to use the CM gapps, concerned that it would contain too much google bloat, but it was a pleasant surprise to find that it is it is quite minimal, like the now -defunct lean and mean PA Gapps offerings for KitKat were.

[EDIT] clarifying reference to Gapps above and adding a question: Does the Gapps package you used by any chance include Google keyboard? If it is pico or nano I would expect not but wonder.
[E 2015 Original Android Development] india_motoe2015:
Are you sure?

I am venturing a guess here that your device is more likely a 4g (Surnia) device & not 3g (Otus) device. Given you are stuck on 'patching system unconditionally' even after clean wipe, successful re-download etc. this is the conclusion I have arrived at.

Please re-check the box the device came in to verify if it's actually a 3G device, if not visit the appropriate 4G device thread on XDA.
[E 2015 Original Android Development] IronTechmonkey:
Thanks for chipping in with this answer. (I would have got to it if the poster of the question was not resisting any suggestion that the wrong resources were being used;)). It is not surprising that people mistakenly user surnia resources for otus and vice versa for 2 particular reasons:

1) Some of the Moto E resources at XDA and elsewhere do not clearly indicate which branch (Surnia or Otus) the available resource is for, and none of them properly list model #s. In particular, a popular bootloader unlock resource external to XDA actually mentions otus but directs people to surnia resources on XDA where a lack of clarity does nothing to correct the unintentional misdirection.

also...

2) Once CM is installed (or when the device is stuck with no functional OS) there is no way to determine the exact model # in the OS although...if you remove the bezel there is a pull-out paper tag on the opposite side of the SIM/SD slots which shows the model #, IMEI and SN.

Also, there is this list of model #s which can help people match the proper resources with their device. http://xdaforums.com/moto-e/general/moto-e-model-list-t3195889.
[E 2015 Original Android Development] squid2:
There is one other way (outside the OS):

If you go into fastboot mode and from the bootloader menu select "Barcodes", it will show you the device model number, manufacturing date, serial number, and IMEI.
[E 2015 Original Android Development] IronTechmonkey:
D'oh. Considering how many Dell service tags I've had to get from system BIOS I should have figured that out. Grazzie mille.
[E 2015 Original Android Development] Dexter_S:
No, I did a dirty flash. Actually I only did a clean flash the first time. After that all subsequent installs were done using a dirty flash. Actually I have always used Open Gapps, thus still using them. And even CM wiki links to them. I did not encounter any issue before this. And about the keyboard, no this micro build does not include the Google Keyboard. The Calendar & Gmail app replaces the stock calendar & mail. And extra is Google Search (Now). But not the keyboard. I also thought about that and searched the whole system directory & in TiBU. I do not know. I will be downloading a new build in a few days & I'm gonna do a clean install. Let's see if the problem persist. I will be also testing both the open Gapps & CM Gapps.
[E 2015 Original Android Development] IronTechmonkey:
Sounds like it is not a Gapps thing, and thanks for the incidental indicator that open Gapps works... and that micro has gmail and gcalendar (which i have banished so I wont use that one). I'm not quick to blame dirty flashing which is actually what CM recommends over spans of a few days or less although the one time I dirty flashed, something or other did not work properly and the universe ceased to make no sense so now I clean flash... which I'm presently doing with 10/21 nightly to test a tweak that supposedly makes autobrightness more responsive... and therefore should be monitored for additional resource use/battery drain.
[E 2015 Original Android Development] india_motoe2015:
Force clossure on latest nightly

I have been experiencing FC on PlayStore on latest (19-Oct) nightly as well. After fresh installation (wiping '/system' before installing latest nightly & OpenGapps) I get 'Unfortunately Google Service has stopped.' message on booting. This occurs one time, after fresh installation. Subsequent reboots do NOT produce this message. However, PlayStore functionality is affected in my experience. PlayStore acts 'iffy', as in sometimes it will FC when trying to update apps & other times it will work as expected.

If anyone has any idea how to resolve this issue, do post..

Additional info - I use OpenGapps package. Yes, I have re-downloaded both, OpenGapps as well as the Nightly, to no avail.
[E 2015 Original Android Development] IronTechmonkey:
On second thought... considering the various feedback, which so far has these problems following OpenGapps and not CGapps, it might be worth trying an installation with CGapps even if just as a disposable control test. I'm 12 hours into a test of cleaned flashed 10/21/15 nightly with CGapps on XT1511 and having no issues. Had no issues in same ROM/Gapps combo with 10/14/15 nightly either. After flashing 10/21 and CGapps, when I updated the local Google app through the Playstore, a Play Services update was offered but not forced (required to use Google app but not required for installation) and I accepted it. Also, I notice that Deltadroid's gapps folded in a Play Store update yesterday. In the past I've seen older Gapps packages get outpaced by Google's frequent services updates and reach a point where automatic updates to G services, which usually occur immediately after build, failed and a play services/play store update had to be applied manually. Perhaps, after this recent round of google updates such a boundary was crossed, affecting the ability to update G services with openGapps but not CGapps. Just a wild guess without comparative tests and logs but food for thought.
[E 2015 Original Android Development] Dexter_S:
I try to depend on Google Apps as less as possible. But I'm a Gmail user & I'm a suckere for the label feature. I thought of downloading the Aroma installer but that is just too big. The auto brightness is still messy. The live display just changes the color tone. But suddenly my brightness will go up and I have to manually decrease it. Let's see if this build have fixed this issue.

---------- Post added at 08:27 PM ---------- Previous post was at 08:20 PM ----------

Actually this is one of the reason I use Open Gapps. Open Gapps is updated regularly like the Nightly updates. And sometimes the play store or play services installed by it more updated than provided by play store in India. This I literally tested. I noted down the updated play service version through play store before flashing the latest Gapps. Now that can be a problem, especially in India where the updates come at different pace than US.

---------- Post added at 08:36 PM ---------- Previous post was at 08:27 PM ----------

Which build of Open Gapps do you use? I have noticed that going bigger than the Micro build sometimes causes FC issue. Especially if you install Google+ as system app. I can not figure out why. And about the play store, did you wipe the cache partition during flash? If not, try doing that. Not dalvik but only cache.
[E 2015 Original Android Development] IronTechmonkey:
I prefer as a minimal a Google presences as possible too, which is why I use lean Gapps packages which allow me to install the Google search app, Gmail, and other things as user apps instead of system apps which in turn gives more flexibility to backup/restore with TiBU (I use no cloud/on-line services of any kind for backups, email or settings). There is only one option for CGapps which is gapps-5.1-arm-2015-07-17-13-29.zip. IMO and in my usage scenario, having to let the services update is worth having a very minimal Gmail presence over which I have greater control (but no illusions of total control or privacy). Although frequent updates are nice and can help get over some hurdles, each one experiences less test repetitions than an older package so there is a trade off there between having to update/maybe even being unable to VS having newest items in a less well used and tested package. I'm sure if I run into a wall with CGapps I'll try openGapps and go as lean as possible. The primary reason to have apps folded into the Gapps package is supposedly that they take up less user space than if installed as user apps but that was negligible in my case so I opted for greater control and an more minimal google presence. BTW When I used Gmail I used "labels" heavily but I'm old school and call them folders :). A bunch more on autobrighness later.
[E 2015 Original Android Development] IronTechmonkey:
auto-brightness

As to auto brightness; although it is now a bit more responsive it is still a mess Here is some history of auto-brightness and how I'm testing it http://xdaforums.com/showpost.php?p=63405905&postcount=4631

Here are some additional details about the latest tweak:

- With the 10/20/15 tweak auto-brightness now responds quicker but dives deeper even in moderate light. As I am writing this it is adjusting too frequently and deeply for the constant lighting it is in. Under a bank of long multi-bulb fluorescent light fixtures spaced 4 feet apart in all directions, even a slight change in orientation of the phone results in a large change in brightness and it stays too dark too much of the time; and this is coming from someone who's default brightness value is 4%! One problem seems to have been replaced by another. I can see an attempt to achieve lower average brightness over time and faster response somewhere in this tweak but the result is "just turrible" (to qoute The Round Mound Of Rebound).

- The 10/20/15 tweak seems to have dropped the lower limit used by auto brightness back down to 1% or even lower. The native brightness slider in Quick Tiles hits a minimum of 5/255 (about 2%) but the lowest value being used with auto-brightness enabled is noticeably lower - probably approaching an absolute minimum less than 1%. Since, with auto-brightness enabled, the system incorrectly reports the previous manually set brightness into variable I cannot get a # for this but teh effect is quite noticeable. Also, those lower values are used in much brighter ambient light than before. I kind of like that but expect most people would not.

- An often overlooked aspect of testing anything involving brightness or proximity sensors, especially pertinent when sudden changes are occurring; Make sure no finger or object is covering the sensor. I've found that when I hold the phone in my left hand my thumb occasionally covers the light sensor but made sure that was not a factor in testing. Now I do that intentionally at times. I once read a post about how someone's dialer screen kept shutting off because they were covering a sensor.with a finger. Unlikely but worth considering.
[E 2015 Original Android Development] india_motoe2015:
I use Open-Gapps-Pico version, and I have not had FC issues (with exact same tweaks / settings) on previous Nightlies. I think my previous Nightly was 15th-Oct, I am not too sure.

In my previous post I said I received the error 'Unable to connect to Google Play services' only on first boot after fresh installation/upgrade. However, the error pops-up every time I reboot (on hard-reboot, not just UI restart).

I always wipe cache+Dalvik after each new installation, but the error persists. Also I do not use any google service, absolutely none, other than Play Store & have disabled/froze as many as I can at system level, which worked fine before upgrading to latest nightly.

More info - plugging-in as well as removing charger pin also brings up 'Unfortunately, Google Play Services has stopped.' pop-up. So I am not sure whether OpenGapps are at fault or whether it's CM.