yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] starkly_raving:
Just as a rule of thumb you shouldn't report any bugs if using xposed or any other mods that effect the system partition, this includes xposed, custom kernels, performance scripts, tweaks and edits. When testing a ROM in the nightly stage test it as is...if there's a bug tracker pull your logs and submit them to JIRA or whatever the case may be. If there's not a bug tracker try to duplicate your issue and get a logcat.

Stating its simply "broken/doesn't work" will not help the developer find and resolve the

issue. The more accurate the bug reporting, the faster bugs are fixed and the faster you could have a Milestone release or even an RC.

Good format for reporting is this...

1.Device variant

2.Recovery used

3.ROM version flashed

4.Did you verify your download/MD5?

5.Was it a clean install or dirty flash.

6.Your issue plus a logcat and try to find out if its something that can be duplicated on command or if its intermittent.

7. What mods you have installed(should be none if you're testing for stability, if xposed breaks something that otherwise works the bug should be reported in the xposed thread for example.)

Not trying to sound like a lecture but this is one of the primary causes in development delays...we have to do our part and properly test and report.

:thumbup:
[E 2015 Original Android Development] IronTechmonkey:
Pardon the self quote but the possible issue with encryption wont happen with us since hardware encryption was previously disabled http://review.cyanogenmod.org/#/c/114365/. Still - good to know.

[EDIT] While on the topic of security here is a possible hole in security of pinned app mode (and subsequently the security of the lock screen).

The way some pinned apps close, in this case Dolphin browser being closed by repeated back button press, allows a brief moment where the QT panel and status bar can be accessed before the lock pattern is presented. From the notifications that consequently become accessible the system can be accessed without requiring an unlock pattern even if pinned mode is set to require unlock. Normally in pinned mode neither QT or status bar is accessible. Although in pinned mode there may be a low expectation of security because it is implied by use of pinned mode that the phone is being handed to another person, the native lock-screen camera shortcut also runs as a pinned app allowing such intrusion directly from the lock screen. This has been mentioned earlier here and at the LMT thread if. I don't expect this issue would rate very high but if there is any interest in chasing it I can test further and log it.
[E 2015 Original Android Development] Dexter_S:
This is strange.

This is a screen shot of my today's usage. After a full days use, I noticed my battery is a little bit more spent. The weird thing is I never used WiFi today or in last few days. But this graph is showing a constant on WiFi. I'm using 11/11 nightly. Not using Xposed or any mods.
[E 2015 Original Android Development] starkly_raving:
Is your WiFi actually on? Regardless if it connects or not its still scanning and that burns juice too.
[E 2015 Original Android Development] Dexter_S:
That's the first thing I checked. WiFi scanning in background is off. Never faced this problem before.
[E 2015 Original Android Development] IronTechmonkey:
Perhaps an app or unique settings combination is keeping wifi in an awake state. You could install Better Battery Stats to look into such things and check for partial wakelocks and wifi on time. You should also capture and share logs that might help isolate the issue. As to determining the root cause of the issue I am reminded of an old joke/riddle that is applicable to tech testing:

Question: "How does one build a statue of an elephant?"

Answer: "Get a block of raw material and carve away anything that does not resemble elephant."

Where "block of raw material" = clean flash, and completed "elephant sculpture" = the device after configuration and apps installation. In order to suss out the cause and or contributing factors of the wifi issue you could go back to clean flash and test wifi at various steps as you configure the device and add apps and settings changes.

It can be difficult to tell in retrospect which previous chisel strike fractured the elephant statue:).
[E 2015 Original Android Development] IronTechmonkey:
Wahooo - we've got our first otus snapshoot. It is looking good in preliminary tests and it has the November1st security patch level but I'm not sure when it was branched from the Nightlys and what if any important commits after that would have been added. It is most likely current as off 11/10/15 (the date of the November CM blog update) but may it or may not include the commit that fixed hardware backed encryption with pattern from 11/13/15. In any event, the snapshot opens the door to creating official jira ticket for bugs and potential feature additions. I'll break out the old list and test things from it against this snapshot and throw them out here for feedback.
[E 2015 Original Android Development] raghavarora1997:
Do we have to clean flash a snapshot over nightly or a dirty flash could also work?
[E 2015 Original Android Development] IronTechmonkey:
Clean flash is always more strongly recommended whenever switching between nightly and snapshot or snapshot and nightly.
[E 2015 Original Android Development] IronTechmonkey:
Ahead of the old list for jira here is a bit of an exploration of the relatively new livedisplay feature which could be better implemented, and about which there is little information about how it works.

Livedisplay shifts the color of the display towards red for night-time use depending on certain criteria but it is not well explained and IMO should be more open. Other than the one setting within live display - off/day/nigh/automatic there seems to be no user controllable criteria for enabling it* and the native %nightmode variable seems unrelated or at least disconnected from user control as it always says auto even if other livedisplay mode settings are used.

The way livedisplay seems to work is that; depending on time of year it changes shading in at least 2 increments over the course of an hour, twice a day (once in each direction: to-red and from-red), at prescribed times, contingent upon the device having at least one GPS fix since being rebooted. If the device has been rebooted livedisplay will not change automatically even if set to do so, until a gps fixed is made, although the livedisplay setting can be changed manually and quickly from a QT.

* This brings up some interesting questions about 1) user control to accommodate people for whom this feature would be nice if it could run at different times of day and 2) unannounced GPS location use.

1) As someone who has suffered ill effects to health caused by a few years of late and overnight shifts IMO it would be nice if the start and end times of red-shifted mode could be set manually because for some people "standard" daytime hours don't apply.

2) Although GPS does not get invoked automatically just to give livedisplay the information it needs it would be nice to know it is occurring beforehand and to be able to disable it so manually set times of day could be used.
[E 2015 Original Android Development] IronTechmonkey:
[EDIT] ... Total brain fart deleted. Long day... I got totally confused between clear-recents and clear-notifications which are both still the same...

As to the 11/24/15 nightly:

- *The CM build targets list shows that devices graduating to CM13 are being moved to CM13 and removed from their former spots in the CM12.1 list so I'm not doing any deep or specific testing in CM12.1 and will save that for CM13.

- The snapshot did not reach back in time as far as I had thought. There were commits as far back as 11/6 (wifi filter drop down) which did not make it into the November snapshot although the "otus: don't get stuck in charge only mode" commit from 11/5 did make it into the snapshot.

- The new wifi filter dropdown is present in this 11/24 nightly and is a nice addition if you want to restrict the view to only secure or open networks

- I dont know if the "cryptfs: Unbreak hardware-backed pattern lock + encryption" issue made it into the snapshot or even if that one means anything to us since we might not have hardware backed encryption but it is likely in the 11/24/nightly..

- Although I'm not doing much focused testing, my installation & configuration routine is fairly rigorous and the ROM seems as good as before with no major issues.
[E 2015 Original Android Development] IronTechmonkey:
flagging a possible issue in 11/24 that may be addressed in next nightly. I noticed this commit yesterday - http://review.cyanogenmod.org/#/c/121131/ - and think I saw the symptom today. Occasionally (but not always) during file write operations involving camera app or image files; the prompt to select root of SD in order to gain access pops up. Since camera2 is mentioned in that commit I assume these are related and it might be best to wait for the next nightly if anyone is considering updating now.

[EDIT] Aw heck. What an inopportune time for the build-bots to hiccup - on the cusp of a notable fix. Just before the otus CM12.1 11/25 nightly would have been generated (after osprey) there must have been a glitch because 10 contiguous builds from otus to scorpion were skipped. Although the SD write issue does not seem to be critical I'm not liking it and am eager to flash up but it'll have to wait. Oh well.
[E 2015 Original Android Development] fastman812:
Rom until now just great!!Thank you Squid!!Can some one guide me on how to solve this internal memory problem? i have install a large Real racing 3, post that nothing else can be installed. Well earlier when i was using HTC pico, i used int2ext or int2ext+ , say which had init. support. but here in this rom packages i didn't find any init. support.. Should be installed ? including busybox? kindly guide me in doing the needful to get rid of this low internal memory problem. Ps: i do have a class 10 32Gb card so partitioning on it isn't gonna be a problem.
[E 2015 Original Android Development] IronTechmonkey:
I think CM does support Init.d and startup scripts but managing it might be different than in other ROMS. The folder that supposedly indicates the presence of init.d support is present on this ROM (\system\etc\init.d). I've never used it but did once read that you may need to recompile the boot.img after making some modifications (possibly outdated information). it might be worth doing some more research on CM specific init.d and startup script management.

As to internal memory - Real Racing 3 requires almost 550MB for the basic installation and that is before considering cache space. IMO that is just too high a storage requirement for internal storage. On my fairly busy device, albeit busy with utilities and not graphic heavy games, I have over 1GB free when I have all my apps installed (over 2GB free when seldom used apps are removed with TiBU and preserved for off-line re-installation). The point being that the ROM should have room for Sim Racing 3 and many other of apps so you must have must have a lot of stuff installed or media files living in internal storage. Perhaps you could make more space by cleaning up other things or moving some items to the external SD. You could also try using TiBU to remove apps that you dont use often. Have you ever audited the amount of storage space used by different things? I found SD Maid Pro's "biggest" feature (find largest folders/files) good for this and there are probably other utilities that could do the same.
[E 2015 Original Android Development] fastman812:
Thank you [MENTION=5119654]IronTechmonkey[/MENTION], well i look into it as well. As of now i have other problems as well, random reboots and another major problem or Adaway and adfree both not working(tried changing host target as well) and adblock-plus just force closes after i have config'd it. and insight on these problems as well would surely be very helpful.
[E 2015 Original Android Development] IronTechmonkey:
Under those circumstances you might want to consider a clean flash and re-installation/restoration of your apps in stages with frequent pauses for testing. Off topic but as for ad blockers.make sure you are using only 1 host based blocker (Adaway is best IMO) and be advised that Ad-block plus has in the past taken money to let some advertisers through ;). BTW, in general using multiple utilities for the same purpose is rarely good for stability, speed or battery life.
[E 2015 Original Android Development] fastman812:
Thank you [MENTION=5119654]IronTechmonkey[/MENTION] will do a clean install. I wasn't using multiple utilities i tried them one after the another. From a long time i am using adaway, even on my old HTC pico, keen on using it as well. But as of now on this phone, the moto e,adaway didn't block any ads and that was my concern. Well i will try again after a clean installation.
[E 2015 Original Android Development] IronTechmonkey:
The write to storage issue in the 11/24 nightly has been fixed and the 11/26/15 nightly is looking OK in general.
[E 2015 Original Android Development] akka47:
I'm having force shutdowns when watching videos, specially in the Twitter app. Logcat attached.
[E 2015 Original Android Development] IronTechmonkey:
I'm a bit curious about this commit http://review.cyanogenmod.org/#/c/122052/ and where it falls in the time-line of chasing USB connection issues in CM12.1 and CM13. Will give it a test first chance I get after it hits a nightly.

[EDIT] 11/30/15 (last?) CM12.1 nightly looking OK. Commit mentioned above has been applied. After charging while

powered off power up now requires a normal 3-4 second power button press. USB connection modes normal.
[E 2015 Original Android Development] chrono_s3rge:
I have the XT1511 model and installed snapshot from 2015-11-17.

Working very well, except AudioFX starts but audio doesn't change, and USB mount won't work; either adblock plus.

[edit] restarted computer and USB still off, then switched to my pc's second USB port and now it's working LOL.
[E 2015 Original Android Development] Dexter_S:
The AdAway problem persist for me also. I don't mind because lack of ad supported apps on my phone. But I tried changing the target host to all four sources. Nothing worked.
[E 2015 Original Android Development] IronTechmonkey:
One of you is referring to adblock plus and one of you is referring to adaway. They are different products. For what it is worth I've had no problems with adaway in this ROM running any nightly - now o0n 11/30/nightly. If by any chance you are using both - that is the problem. There is a lot more about that in the adaway thread. BTW adblcok plus has sold pass-throughs to some advertisers in the past and cannot be trusted ;)

---------- Post added at 12:04 PM ---------- Previous post was at 12:00 PM ----------

/\ in re adblockers see above/\

As to USB mounting. Assuming this is the same as what was once called USB OTG, I tested that a while ago and it did not work here either. I wonder if it is even possible on this hardware. Have you ever heard of USB mount working on this device with any application or mod?
[E 2015 Original Android Development] IronTechmonkey:
When you earlier said "USB mount" were you talking about mounting USB drive to the phone or mounting across connection to PC?
[E 2015 Original Android Development] Dexter_S:
I'm talking about AdAway. I've never liked Adblock plus. Host editing is much simpler
[E 2015 Original Android Development] chrono_s3rge:
I was talking about connecting to PC, sorry for not clarifying. And for ad block, I found out about the Admin permissions in Cyanogenmod, so I'm using AdFree now and it works.
[E 2015 Original Android Development] IronTechmonkey:
I agree about host based, and thank you for indulging my curiosity. For what it is worth I've had no problems with Adaway in Cm12.1 but the permissions issues in CM13 do create problems for adaway (which can be worked around by manually remounting as rw).

---------- Post added at 04:42 PM ---------- Previous post was at 04:37 PM ----------

Thanks for clarifying. I was wondering because there have been gltiches in the past for CM12.x and the recent past for CM13 where USB to computer connection would revert to charging only and mode and could only be changed when connected to PC. In CM 12.1 this occured after charging the device while powered off but this has been fixed in recent nightlies - most completely so in the 11/30/15 nightly (which is the last CM12.1 otus).
[E 2015 Original Android Development] fastman812:
Same here, blocks ads partially only on default browser and only on some websites , also gives lots of errors.. Adfree also same scenario. i noticed that ads weren't blocked on chrome, mozilla, opera as well so had use adblock browser instead. but system ads to trouble me a lot. Ps: i did a clean installation, used Adaway once, clean wipe and reinstalled and used adfree..
[E 2015 Original Android Development] IronTechmonkey:
That may be so but it is not a ROM issue, nor is it likely to be an Adaway issue but that is something for the Adaway forum rather than this one ;).
[E 2015 Original Android Development] IamAlexD:
Now Official CyanogenMod 13 (CM13) is available For Moto E 2015 3g (Otus)

Official Download Link-->>https://download.cyanogenmod.org/?device=otus

Don't do dirty Flash if you are running any CyanogenMod ROM
[E 2015 Original Android Development] IronTechmonkey:
I suspect that many people who visit this thread know this but it cant hurt to have another post about it. That said, the link to the new XDA development thread for Otus moto E 3G CM official nightlies would also be helpful so here it is: http://xdaforums.com/moto-e-2015/orig-development/rom-cyanogenmod-13-moto-e-3g-t3260876.

Also, people should be advised that CM13 is a work in progress and M introduces some new limitations, so if you want to use a stable ROM that is a known entity you might consider using CM12.1 as a daily device and dipping in to CM13 to test and help improve the ROM.
[E 2015 Original Android Development] IamAlexD:
CM13 is in nightly so we have to wait for the final stable built.I also suggest people to use the stable 12.1.Thanks bro for this Guide. :):good:
[E 2015 Original Android Development] IronTechmonkey:
Well, although I recommend using the more thoroughly developed CM12.1 as a daily for now I am not discouraging people from trying CM13. In fact I encourage people to try it and contribute to its development, but to have a fallback and not to expect CM13/M to meet all their daily needs immediately.
[E 2015 Original Android Development] fastman812:
Random reboots have increased on my device? any help on this? or what should i do to fix it? Ps: its a clean install
[E 2015 Original Android Development] IronTechmonkey:
I'm still running the last one (11/30/15) and having no problems. 2 weeks without a single random reboot and only a few FCs when I was experimenting. It helps to confirm details of the flash, as well as what might have been done after flashing, This is a generic batch of items so dont take it personally if it mentions/asks things that you already know:

- First and foremost. No Xposed. Simple as that - rant deleted but ready;)

- Which nightly?

- Recovery used? TWRP 2.8.7 or 2.8.7r recommended.

- Clean flash: In TWRP: Wipe Factory rest, flash ROM, wipe dalvik cache and cache, flash compatible gapps, wipe dalvik cache and cache, reboot.

- Did the problem happen at the very start or later, as settings were changed and items added?

- Have you noticed a pattern in the issues, such as being around the use of a certain device feature or app?
[E 2015 Original Android Development] squid2:
December 16 Security Update

I've posted a new build with security updates. The download link is up on the first post. I'll continue to do occasional maintenance releases with security updates and minor bug fixes until CM13 is at the same level of maturity as CM12.1.

Note: This build is from the nightly cm-12.1 branch and not than the YOG7D stable branch. This is because the cm-12.1 branch is more up to date and actually more stable too I find :p
[E 2015 Original Android Development] IronTechmonkey:
Any reason SuperSU is installed in clean flashes on new device?. It's not a ROM issue as the same thing is happening when I flash the older 11/30/15 nightly. NM, apparently if superSU is enabled and disabled in the UI it gets stuck but it's full unroot cleared it after several tries. Back to native SU for testing.

[EDIT] cm-12.1-20151216-UNOFFICIAL-otus looking good with CMGaps and open Gapps.
[E 2015 Original Android Development] Panchoso4D:
Black screen after boot.

Hi, guys.

I've installed this ROM just for give it a try. Well, the installation was fine, I've also flashed OpenGApps and SuperSU zip, and all worked fine, but after I've flashed 3 zip's for Viper4Android (from http://xdaforums.com/showthread.php?p=60801910#post60801910), I've rebooted into my device and the lock screen was shown, but there were no touch response, and the screen went black (as a normal screen off, with the classical fade out). Then I've tried to turn on the screen with the power button, and the backlight turned on, but the screen was black.

If I keep pressing the power button the power options are shown, and I can select that options (here I have touch response), and if I reboot in secure mode (keeping pressing Shutdown option) it happens in the same way, but it shows the "secure mode" indicator when I turn on the screen.

I think the zip's are corrupting something.

Could you help me :crying:? tnx

PS: Sorry for my english :D
[E 2015 Original Android Development] IronTechmonkey:
You've sort of answered your own question or at least given yourself a direction within your description. The Otus CM12.1 ROM, Gapps and SuperSU are all OK, so something with all that other stuff or the process used to install and configure it caused things to break. Perhaps someone here is familiar with that stuff and can offer advise but your best bet for answers might be in the Viper's Audio threads.
[E 2015 Original Android Development] Panchoso4D:
Oh, OK, thanks mate. I'm going to Viper's thread now. Thanks :)
[E 2015 Original Android Development] india_motoe2015:
Theme crashes fixed

I logged-in to say that latest security fix you have posted seems to have fixed 'theme crashes', and it appears more stable than SNAPSHOT available from Cyanogen Otus download page.

Thank you & good work! :good:
[E 2015 Original Android Development] IronTechmonkey:
A bit late to the party on this one and have no expectation of fix but just in case others have noticed it. CM's native messaging app, when set to "Auto-enable data" for MMS, is turning mobile data off about 1-2 minutes after mobile data manually enabled, regardless of use of messaging app. Will check for the same thing in CM13.
[E 2015 Original Android Development] chrono_s3rge:
I've have a Chromecast 2015 and it works fine with my phone except screen mirroring, only audio comes from TV. I'm still using the CyanogenMod 12.1 Snapshot (2015-11-17).

By the way, wifi keeps auto disabling shortly after the screen turns off, how can I keep wifi working?