yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] immy28:
Please post change log . what is in new built for .... Changed ... If possible .. :thumbup:
[E 2015 Original Android Development] Casper1982:
Changelog cyanogenmod: http://www.cmxlog.com/12.1/otus
[E 2015 Original Android Development] IronTechmonkey:
Changelog is in OP and several posts in the thread....but then someone may have been kind enough to do this basic searching for you as seems to have been the case ;)
[E 2015 Original Android Development] tarakavinash:
Speaker Volume

My Device Has Reduced Volume Suddenly After Nightly Build Sep 23 :( Any One Help Me Please

Thank You In Advance :)
[E 2015 Original Android Development] IronTechmonkey:
Reduced volume everywhere? In call? In media play? If this is occurring in calls try this:While in a call lower and then raise the volume. Sometimes it gets to a to louder volume when you do this but it only applies to calls. I've seen this behaviors in almost every Android ROM I've seen.
[E 2015 Original Android Development] tarakavinash:
I Have Got This Error In Media Play .. Ringtone Volume Also.. :(
[E 2015 Original Android Development] IronTechmonkey:
That throws my theory out the window... And I'll stay away from that nightly. Thanks!
[E 2015 Original Android Development] Krizthian:
Random Reboots:

I have come to the conclusion that this error is caused by the change in performance profile. Since reboots become more common.

Regards.
[E 2015 Original Android Development] IronTechmonkey:
I see 2 commits for profiles on 9/21 but am still on 9/19.

Did this happen in a clean flash before Gapps and other stuff was added? Also, do you have a log?
[E 2015 Original Android Development] Krizthian:
[MENTION=5119654]IronTechmonkey[/MENTION] I reverted his commits for my build of Candy5.

Morning i try to build Candy and i test how to works the revert.

Greetings.
[E 2015 Original Android Development] IronTechmonkey:
I've been testing this wifi thing and see a pattern that seems to indicate that, even if this is not a bug, it does seem to be an area where a significant optimization can be made toward faster connection times...which are much slower on this ROM than others. Here it goes:

- Assuming an existing wifi connection profile to which the phone will connect when wifi is enabled.

- If the connection is made from inside the wifi settings panel where you see the list of available networks, the connection is made nearly instantly, usually within 1 second and never more than 2 seconds. This has been the result 100% of the time across hundreds of repetitions in a week of testing.

- If the connection is made from anywhere else the connection takes the 9 seconds I reported earlier (in your case it was 6). In this case "anywhere else" includes the wifi toggle in the main Settings panel, the wifi toggle in the quick tiles, and Tasker/Secure settings shortcuts in LMT Launcher and a custom made Tasker-Scene dashboard.

- Now here is where it gets interesting. When I toggle wifi from any of those other places (from which it usually take 9 seconds) and then power off the screen and power it on the connection is made immediately. Here too, this has been the result 100% of the time across hundreds of repetitions in a week of testing.

I don't see a reason why those other toggles, particularly the native ones in Settings and QT, should not wake-up the wifi system as fast as the toggle in the WiFi list.

I'm wondering if those 6 second connection times turn into 2 second connection times if you (or anyone else) power screen off then on immediately after initiating wifi.
[E 2015 Original Android Development] immy28:
OTG support ?

If led notification work then possible OTG work !??
[E 2015 Original Android Development] IronTechmonkey:
Hardware may not support OTG. [EDIT] just dug out my old OTG cable and tested with stick-mount by chainfire but the USB stick is not seen by the device.

[EDIT2] TWRP lists a USB OTG partition. I don't know if this means there really is one but that could be a good sign.
[E 2015 Original Android Development] sagnik9:
Which is the most stable build that can be used as a daily driver at this point of time? since I have limited bandwidth, this would be really helpful
[E 2015 Original Android Development] EsromTech:
I'm using the latest 20150927, I have nothing to complain about.
[E 2015 Original Android Development] IronTechmonkey:
Prolly all about the same but that could change in a second with use of a particular feature or nightly. I've used 9/12 and 9/19 each for about a week which, except for some added features and small GUI tweaks seem about the same. I'm using them daily (very well backed up) and about to jump to 9/27.

Since this ROM is newly official we can not yet file bug reports although there are indeed bugs and potential feature additions/changes to be done, some of which are known and have lingered since CM11. On this note I have recently witnessed that the "countdown timer passes zero" persists. As yet impossible to force in tests this seems to only occur when baking potatoes or doing laundry.

If you are curious about these glitches you can review previous posts, test the described issues like the WiFi thing, and sound off on them :). I think there is a huge potential gain Wi-Fi connection speeds there (talking about time to connect rather than data rates here).

[EDIT} Apologies if I sound preachy, I'm just trying to encourage folks to test some of the known issues :)
[E 2015 Original Android Development] IronTechmonkey:
Likewise, 9/27 running OK here although all of the previously reported issues persist and wifi seems even a bit more hitchy. That first snapshot cant come too soon.
[E 2015 Original Android Development] sagnik9:
I am facing a weird issue on the 27th as well as the 28th build, messaging apps like WhatsApp or hike isn't working when I'm using my mobile data, whereas they work perfectly when I use WiFi, messages aren't getting delivered while using mobile data, any one else facing this issue?

(using mobile data I was able to download apps or browse the web, but the messenger apps aren't delivering messages when using mobile data)
[E 2015 Original Android Development] IronTechmonkey:
If this is in re sending MMS (as opposed to SMS) messages, that has always been a problematic thing, at least in the 3 years since I jumped into the droid-i-verse.

The fact that messaging over wifi works is odd because I thought that had to be offered by your provider and required functionality only available in devices where Motorola baked it in. In other words it could not be done as a software addition. Anyhoo..

Do SMS memessages send recieve OK?
[E 2015 Original Android Development] Casper1982:
Do you recommend this rom, or better to wait some more stable version? :)
[E 2015 Original Android Development] IronTechmonkey:
Test it and then you tell us ;)
[E 2015 Original Android Development] immy28:
Stock camera work with gallery.

Just set as a system apps. And do Right permission.

Hope net updates with stock camera not Google cameras.:thumbup:

Aslo can someone make miui rom !?
[E 2015 Original Android Development] IronTechmonkey:
Thanks for testing this. I really like the stock camera and would like to test this. How did you acquire and install the stock camera apk?
[E 2015 Original Android Development] immy28:
Make a folder in sys-app- make a folder as name camera and paste here stock app then set permission. Restart ... :thumbup:
[E 2015 Original Android Development] immy28:
Make miui rom bro ..

Sent from my Moto E
[E 2015 Original Android Development] sinnerz2000:
Trust me, miui on my snapdragon 400 chokes like a mother, imagine that on a snapdragon 200 device.
[E 2015 Original Android Development] IronTechmonkey:
Not sure if this is a ROM issue or a limitation of USB tethering or MS Outlook..

I cannot send email from MS Outlook 2010 on a USB tethered PC that otherwise has good Internet access through tether. This is almost certainly an Outlook/POP3 issue as it does not occur on PC in Thunderbird or on phone with same pop3 settings, or in same email accessed by IMAP in Outlook, but I'm fishing for any known email protocol or security limitations of tethering.
[E 2015 Original Android Development] immy28:
Help me guys. .

Where can i find new nightly Changelog .. What is in new version inside..

Sent from my Moto E
[E 2015 Original Android Development] Casper1982:
Here; http://www.cmxlog.com/12.1/otus
[E 2015 Original Android Development] IronTechmonkey:
Thanks again. Got it going. FCs when leaving the camera app by any method and when attempting panorama picture but works otherwise. At least the auto focus and white balance controls in the reticle work and the advanced settings are nice.
[E 2015 Original Android Development] IronTechmonkey:
10/3 nightly looking generally OK.

Camera menu phantom flash icon has been fixed.

FM Radio headphone-to speak jump to full volume persists.

Wifi still slow to connect. My workaround is to have Tasker/secure settings power the screen off and on after enabling wifi [all as part of one toggle] and; even though that process requires a 2 second pause it only takes 3-4 seconds to get connected where it still takes 8 or more seconds by native toggles.

I wonder if we'll get a snapshot this month.
[E 2015 Original Android Development] IronTechmonkey:
If someone is so lazy that they cant get the changelog from the OP even though it is one of the first and most visible links in the OP.... perhaps they should not be indulged so ;)

---------- Post added at 03:43 AM ---------- Previous post was at 03:41 AM ----------

You kids are lazy! :) I may seem like a crank but I'm a pussycat compared to what you would get for making no effort at all in more mature [meaning deeper into development] threads ;)
[E 2015 Original Android Development] sagnik9:
For some reason when I'm using mobile data I can't use the internet messaging apps like WhatsApp, messages aren't getting delivered, all the other apps are working perfectly with mobile data, I can even browse the web with mobile data

Although with WiFi everything is working perfectly even WhatsApp.

SMS is also working perfectly, can you please test using mobile data if internet messaging apps like WhatsApp is working for you?
[E 2015 Original Android Development] IronTechmonkey:
I saw your/a(?) previous report about this. Apologies for not testing then. I've never used messaging through mobile data or Wi-Fi (somewhat by personal policy about amount of data exposure) but will explore this a bit. I can say right off the bat that mobile data toggling is more cumbersome than it was in the previous CM ROMs I've tested.

At present, in this ROM not even Tasker/Secure settings can toggle mobile data, and AFIK there is only toggle out there that can do it (but it requests SU access too frequently). Considering the aforementioned, if those messaging apps enable/disable mobile data in order to send stuff perhaps that is a problem... although you say SMS works. Is SMS working through Wi-Fi and mobile data?
[E 2015 Original Android Development] IronTechmonkey:
You did not mention this. ;)

Since this is something the makers of WhatsApp disclaim you might want to check in WhatsApp specific forums to see why that is so. Perhaps you will find a potential workaround for CM. I did install WhatsApp but in order to configure would have to share more personal details than I am willing to. The only thing I can add is to try it with background data disabled if you've not already done so.

[EDIT] I've got my wifi time to connect down to 2 seconds with tasker where my normal time to connect is 8 seconds if done from the wifi toggle in the main settings page . If you don't mind my asking, how long does it take you to connect to wifi if you do so from the wifi toggle in the main settings page (not within the list of available networks)? TX.
[E 2015 Original Android Development] IronTechmonkey:
For those who use Tasker or have the programming chops to do this raw, here are some ways to 1) have faster time to connect for wifi and 2) a mobile data toggle that only requires one tap.

1) Wifi time to connect in 2 seconds (assisted by static IP assigned at router and phone although might help without static IP).

This toggle uses the wifi connection state, which is visible to Tasker, as a variable to determine if wifi should be toggled off or on and navigate within the task. After toggling wifi on it opens the wifi settings panel as an activity, then invokes the back button. Note: With that wifi settings page opened the wifi connections are much faster = the heart of this task and what could become an optimization in CM

View attachment 0wifiToggle3.txt

2) Mobile data toggle that can be invoked from Tasker shortcut.

Since the mobile data connection state can not be seen by Tasker a manually created variable is used to determine if mobile data should be toggled off or on and navigate within the task. The heart of this task are the commands "su -c svc data enable" and "su -c svc data disable". This also seems like it could be in CM.

View attachment 0dataToggle3.txt
[E 2015 Original Android Development] IronTechmonkey:
10/11/15 nightly looking generally OK. Some modest new feature additions such as volume boosted ring tones (although I don't see how to gauge their impact) and alarm clock volume setting. Also; a tweak affecting what happens when battery fully depleted while under heavy load http://review.cyanogenmod.org/#/c/110704/. That said, there are an accumulating list of unresolved bugs and features that CM has fixed or added in previous versions.

[MENTION=6485916]squid2[/MENTION] I can see you are working on a bunch of stuff (and thanks for continuing to open the droidiverse for these devices and twrp) so please consider this an offer and not an ask. I've been testing clean flashed builds at least once a week to test various things (not all in the ROM it's self). In the ROM; some of the things I'm seeing are genuine glitches and bugs and others are features that Google always leaves out and CM always puts in.. after more serious code fixes are done. I suppose that if and when otus gets an offical update to L5.1.1 things will get moving faster. Meanwhile, if you are interested in any of these glitches and feature tweaks I can test and provide details. Thanks again.
[E 2015 Original Android Development] EsromTech:
the opposite of you (I think only this of the wifi issue)

it does not take much here to make data exchange for wifi, and not to switch between networks ...

In other things, I did not get no errors so far.

[MENTION=6485916]squid2[/MENTION] I think yes would mark snapshot to otus because I do not see a serious mistake here to do a rom be unstable, thank you for your work and effort.

[MENTION=5119654]IronTechmonkey[/MENTION], you have some more bad behavior rom beyond their wifi?
[E 2015 Original Android Development] IronTechmonkey:
Please don't mistake my constructive feedback, born of intensive testing, for criticism or lack of appreciation for squid2 et al, and please know that installing a ROM and starting to use it is not a test;). Are you specifically testing for things or just observing through casual use? Perhaps you are not just testing through casual use but it is obvious that some people are just installing the ROM and declaring that "everything" works just because the installation was successfully and the small cross section of apps and features they use use are OK. The statements "everything is OK" and "nothing is wrong" are logical impossibilities in this sort of testing:).

If you are interested in seeing that some of these issues get addressed you could start with the things I've already reported here http://xdaforums.com/showpost.php?p=62912113&postcount=285. All of these have been confirmed on the XT1511 in many rounds of tests and verified in ROM only and in ROM after configuration/installation of apps. If you cannot replicate them then try harder :)jk. But seriously, in that case describe your testing process so we can compare notes and see why we get different results. At this point it becomes significant to know if we are testing the same model phone because that could also explain different results. I'm using the US/3G/XT1511 and, based on your signature and location, you are using the global/3G/XT1505. Is that correct? BTW, AFIK once CM is installed the Model # cannot be determined within the OS but if the bezel is removed there should be a slide out tag that reveals the Model # and IMEI# on the opposite side from the SIM and SD cards.

Meanwhile I'll organize a list of potential fixes and feature tweaks. If you are interested in testing for them let me know. BTW at one time the addition of the left/right cursor control arrows in the Navbar (which CM borrowed from AOKP if I remember correctly) and many of our present status bar clock options were added this way.

Totally with you about the snapshot. This ROM is solid and stable enough for that. In spite of the various potential tweaks I've not had to revert to a backup in the month I've been testing it. Once we do get a snapshot we can file Jira tickets for some of this stuff. Also, fingers crossed for an official 5.1.1 update :)
[E 2015 Original Android Development] EsromTech:
of course, I'm not confusing your tests ... they were incredible and demonstrating the total insteresse for development, and also in any way disparage our friend squid2, which is doing a great job :)

I'm interested in helping with more specific and useful tests yes help me how to do this, and we are sure that together with :good:
[E 2015 Original Android Development] IronTechmonkey:
Thanks, and apologies if I seemed irritated:). I'm glad someone else is interested :good: so I'll work on that list. I want to re-test a few things, then categorize and prioritize stuff. This may also be a good chance to see what the differences are between XT1505 and XT1511. I'll retest and document things when I flash this upcoming weekend ... unless I see any interesting commits in the change-log before then.
[E 2015 Original Android Development] EsromTech:
all right, let me know as soon as possible to help you in testing ...

only correcting, my model is xt1506 (Brazil, so sometimes my bad english)

waiting for their list, so I can assist you.
[E 2015 Original Android Development] IronTechmonkey:
Now here is something I'm quite interested in. I thought a list scrolling bounce-back I was seeing in TiBU in stock and in CM was a hardware issue but it seems to have been addressed in the software by this commit which may be in the 10/14 nightly.

http://review.cyanogenmod.org/#/c/111973/

---------- Post added at 01:16 PM ---------- Previous post was at 01:11 PM ----------

OK, you have dual SIM which is good to know because it could explain some testing differences. As to language, being a monoglot (look it up :)) I would never criticize someone who is able to communicate well in what is not their primary language:). That said, I might criticize someone who never presses the thanks button;).
[E 2015 Original Android Development] EsromTech:
Yes, I can test the differences, tell me what to do to help this test?

and thanks for praise in the language in which it is not my forte (also sometimes use google translator to help)
[E 2015 Original Android Development] IronTechmonkey:
I'm not suggesting that we test specifically to see what the are difference between models. I am just noting the fact we that there are hardware and software difference which should be kept in mind when testing for some issues. For example; if there was a possible problem with the user interface it is unlikely that a dual SIM and a single SIM device would experience that problem differently. On the other hand; if there were an issue with SIM management, the difference between single SIM and Dual SIM could be a reason why one person experiences a problem while another does not. This is just something to keep in mind.

As to the scroll bounce-back issue: I read the CM change-log for our device (http://www.cmxlog.com/12.1/otus) daily to see if there is anything worth testing or anything I want to avoid. When I checked this morning I saw the commit for the scroll bounce fix (http://review.cyanogenmod.org/#/c/111973/), which I was glad to see. I would have reported that problem earlier but I thought it was a hardware issue and not a ROM problem because it happened in stock and CM. If you've never experienced this before there is not much point in testing but if you are curious and have Titanium on your device you can try this to reproduce the issue:

- Open Titanium Backup (it may or may not occur in other other apps but it does occur in TiBU)

- Go to the Backup/Restore list.

- Remove any filters so the list is as long as possible

- Scroll to the bottom of the list,

- Scroll to the top of the list using repeated fast and long swipes to get the scroll to move fast.

- When the list reaches the top it may bounce or jump back down to somewhere in the middle of the list.

I've just verified that this is still happening so, when I next do a clean flash one I am going to try again to reproduce this issue and see if it is fixed.

[EDIT] Pardon my hackish first attempt to create a GIF from a video grab on the phone. It may be a little hard to tell in this gif but what is happening is that I'm repeatedly scrolling to the top of the list by swiping down rapidly 2 or 3 times and the list repeatedly bounces off the top and back down even though I am only scrolling in one direction. Something about the video editing and conversion to GIF sped up the animation but in real time you do have to scroll fast to reproduce this.
[E 2015 Original Android Development] EsromTech:
.... gives it occurs even with me here ..

I am using 20151012

This happened to me also using other roms based on the same sources.

in relation to dual SIM, did not see any kind of error, works both networks without any bug .... have something more specific to view on this?

I would like to know more about the wifi!
[E 2015 Original Android Development] IronTechmonkey:
Thanks for confirming the scroll- bounce. A look at the change-log that I linked to earlier shows that will be fixed in the next nightly (10/14 or 10/15).

As for the difference between Dual and Single SIM I think there has been some confusion. I'm not saying anything is wrong. I was just using it as an example of differences between device models but that has nothing to do with any specific issues at the moment.
[E 2015 Original Android Development] magdeoz:
begins the development of CM13 to otus ??

https://github.com/sultanqasim/android_kernel_motorola_otus/tree/cm-13.0

https://github.com/sultanqasim/android_device_motorola_otus/tree/cm-13.0

https://github.com/sultanqasim/android_vendor_motorola_otus/tree/cm-13.0
[E 2015 Original Android Development] squid2:
After some very heavy slash and burn style hacking, I was able to get CM13 to build for otus. It isn't yet booting though, and needs quite a bit more work. The biggest issue though is that CM13 is still very far from being ready. It doesn't even build unless you strip out all the CM out of CM, and you hack a bunch of other things to fix errors. It'll probably be a few weeks before it becomes buildable without silly hackery and is usable.