yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] squid2:
In the past, sensor issues have usually been due to incorrect firmware versions or SELinux issues. There is a script that is supposed to install the correct sensor hub firmware on bootup.

I had updated the sensor hub firmware around a month ago when I had upgraded the kernel. ROMs that don't include the sensor hub firmware script can end up with mismatched sensor hub firmware.

First, reboot your phone so that your old logs get cleared.

Open an adb root shell, and run the following command:

stml0xx getversion

Let me know which version number showed up.

Next, try manually invoking the sensor hub firmware script from the root shell:

/system/etc/init.mmi.stml0xx.sh

Check if the sensors start working after this.

Report back the output of this script.

Finally, in an adb shell, run the following command and share the output

dmesg | grep avc
[E 2015 Original Android Development] Krizthian:
[MENTION=6485916]squid2[/MENTION] Thanks for your hard work in "otus" :D.

Waiting for the official builds :D.

Greetings and many thanks.
[E 2015 Original Android Development] squid2:
August 24 Release

Today's release adds LED notification support. Say thanks to [MENTION=3445372]scritch007[/MENTION] for figuring this out on surnia. I also fixed an issue where the sensor hub firmware upgrade/downgrade script wasn't working when run automatically during the boot process. The correct sensor hub firmware will now be automatically installed on bootup.
[E 2015 Original Android Development] Carlos Arriaga:
in the last build, the LED is working perfectly, zero problems with youtube, and until the moment have not had many problems with BT. but still it fails sometimes, doing great work. lucky for what follows, and hopefully soon have CM12.1 and official
[E 2015 Original Android Development] Casper1982:
The latest version is stable or has reboots?

I can not find the right gapps, someone would give me the link?
[E 2015 Original Android Development] Nirbhay2:
In the latest build i.e 24 August build i m unable to get init.d support. In earlier builds its working like a charm
[E 2015 Original Android Development] squid2:
August 28 Release

Today's build includes cherry picked patches from CodeAurora to improve reliability and security. As always, it also has the latest updates to CyanogenMod. The download is up on the first post.

There is one minor issue with headphone detection that has always been present on this ROM. If you boot up with headphones plugged in, the headphones are not detected until you unplug them and plug them back in. This issue started to bug me enough to look into it. Hopefully I'll have it fixed soon.
[E 2015 Original Android Development] squid2:
Headphone Detection Fix

I've fixed the issue that was causing headphones plugged in at boot time to not be detected. For those interested, this is the commit that fixed it. I don't feel like uploading an entirely new ROM build for this one tiny change, so instead I'm offering the fix as a kernel zip. You can flash this zip over my last build (August 28th) to solve the headphone detection at boot time issue. This fix will be integrated into the kernel for the next full build, so it won't be needed in the future. It's just an interim fix for the impatient.

This zip should work on any otus custom ROM (not just CM). If you encounter FM radio issues after flashing this when running something other than my latest CM build, mount /system as RW and delete /system/etc/init.qcom.fm.sh
[E 2015 Original Android Development] squid2:
Official Support

I've now sent a formal request to CyanogenMod to have official support for this device added. I hope to hear from them soon. I've come to an agreement with the maintainers for condor (first gen Moto E) to share a common kernel. Official builds will use a patched version of the condor kernel that adds support for otus and includes security fixes backported to Linux 3.4.42. I will continue to maintain the newer 3.4.108 kernel presently used here for those who want the latest kernel.org patches and as a base for custom kernel developers.
[E 2015 Original Android Development] sagnik9:
Thanks for your efforts!

I am facing problem with bluetooth

and battery drainage issues, on stock i used to get a SOT of around 4.5 hours, with the same usage it has come down to 3.5 hours of SOT

will you please look into this?
[E 2015 Original Android Development] squid2:
I'm aware of an issue where Bluetooth fails to turn on sometimes when the phone has been left running for a few days. The workaround is to reboot the device. I'll be looking into a solution.

With regards to battery life, I've had excellent performance myself, with 6-7 hours SOT. There isn't much I can do about battery life, but you can try reducing the display brightness and using a more conservative CPU governor.
[E 2015 Original Android Development] sagnik9:
One more a bit irrelevant question, I have been using Condor for the past 1 year, I have recently switched to Otus, I have noticed slight lags here and there with Otus, is it because of Android Lollipop or is it's hardware not powerful enough to run Lollipop smoothly(the performance of Condor with KitKat was liquid smooth overall)
[E 2015 Original Android Development] Krizthian:
[MENTION=6485916]squid2[/MENTION] Thanks for your great work, i waiting for the official Nightlies :).

Greetings.
[E 2015 Original Android Development] india_motoe2015:
Toast notification changed?

Hello,

28-Aug build is working as expected so far. A minor quirk though - did they change toast-notifications in current CM release? I use Xtoast xposed-module, and after installing latest release I am experiencing smaller toast-notification-icon as compared with how it was handled earlier.

Additionally, now that official support is almost a given, do I follow this thread or do I have to switch to official CM threads to get updates etc.?

Great work! :good:
[E 2015 Original Android Development] squid2:
Yes, the toast notifications changed in the last release. They added icons to CM's standard toast messages.

I'll keep this thread updated and it will probably be a couple weeks before official support begins.
[E 2015 Original Android Development] india_motoe2015:
Another small query - When official CM support arrives, do I wipe everything & clean-install or will it be seamless transfer over to the official ROM? I'd hate to lose settings on all the apps & redo system config.
[E 2015 Original Android Development] nickleby:
Hi! Just a question. With this ROM can I record videos at 720p? I know that the stock MotoE2 3G does not allow to record video in 720p, but is this a software limitation or hardware? Even when the processor is different to the 4G version (200 vs 410), the Snapdragon 200 is capable of recording at 720p.
[E 2015 Original Android Development] squid2:
The CPU is capable of 720p recording, but I don't know if the camera sensor is. The Motorola libraries to interface with the camera limit video recording to 480p, same as stock.
[E 2015 Original Android Development] squid2:
September 1 Release

I'm quite pleased with today's release. It's my final push to iron out all remaining bugs before support is made official. In addition to the boot-time headphone detection fix from a couple days ago, I also did some fiddling with Bluetooth. I switched to using Kernel.org's Bluetooth implementation in the kernel and I removed a library that seemed to be causing trouble. In my limited testing, Bluetooth appears to be working well now, but I'll need a few days of testing to be sure of this. I recommend wiping /system before installing this release for some fixes to take effect. You will have to reflash gapps and any mods after installing the ROM when you wipe /system.
[E 2015 Original Android Development] india_motoe2015:
CPU too high?

Hi,

I installed 01-Sep release. However, I must mention that I did NOT wipe '/system' partition as recommended. After wiping dalvik/cache, the sytem acts strange. The behaviour is similar to computers when CPU is maxed-out at 100% - namely, I can't quickly open app-drawer, recents window take time to appear, SuperSU app permissions are delayed etc.

The behaviour presents itself for 30-40 seconds after wiping dalvik/cache, and resolves later on.

Additionally, I wanted to know when CM official support arrives, do I have to clean-wipe & reset everything or can I carry it over seamlessly?
[E 2015 Original Android Development] nickleby:
Yeah, they're probably different. The 3G variant carries a Samsung S5K5E2 sensor (according to the debug info in the camera app), I don't know which one uses the 4G model since I don't own one to verify. Although even when they are different, the S5K5E2 sensor is able to record video in HD. :confused:
[E 2015 Original Android Development] squid2:
If you don't wipe /system, Bluetooth might act up, but that's about it. Whenever you do an upgrade, it will be slow for the first minute of operation after bootup, during which it does various cleanup and upgrade operations in the background. After the first minute, it should be smooth.

As for official CM, once nightlies begin, you should be able to carry over your settings and avoid a clean install. If you encounter issues, a clean install is recommended, but it shouldn't be required when upgrading to nightlies once they become available.
[E 2015 Original Android Development] tarakavinash:
[IMG="Camera Not Working"]https://d2getw.bn1302.livefilestore.com/y3pO42IX2M4QURPol8IJ7f7su4myRSOvHNerrug8ag43kv0A6odGYUVIYjvTF9crfWPwLW7I0tgq6_GI1dDwb3DIVNpfK3_rGkCfVFqZp7oigIXfaeb0wWci3X3j0bEiVtSeRZ7OwWlV2v0bgqO6kgAkhmqDhsgB0c_dvaDvQ66VDk/Screenshot_2015-09-01-21-18-45.png[/IMG]

With September 1 Update Camera Has Stopped Working Sir.. Please Check It
[E 2015 Original Android Development] squid2:
Heh, you're right, it is broken. Something in CyanogenMod must have broken it temporarily. I'll post a new build with the camera fixed soon.
[E 2015 Original Android Development] Pr!mus:
hi,

I flashed the Sep 1 build and getting can't connect to camera error.

Tried the google camera and the CM camera app.

Camera is working in CRdroid rom.

Plz help
[E 2015 Original Android Development] Rm77:
Bluetooth works fine but camera seems to be broken. And everything else is working as it should.
[E 2015 Original Android Development] squid2:
September 3 Release

This build fixes the camera regression in the last build. Everything should work reliably in this build.
[E 2015 Original Android Development] tarakavinash:
Phone Restarts

Camera Is Working Absolutely Fine With This Update. But Phone Restarts While Listening Music Mainly & While Receiving Calls Few Times.. And Sensor Doesn't Work Properly While I'm Receiving Calls Screen Doesn't Turn On For Few Seconds It Works. Please Check My Problems Sir.. Give Me A Solution.

Thank You..
[E 2015 Original Android Development] squid2:
Next time you get a random reboot, after it reboots, please capture /proc/last_kmsg over adb and share the log here.
[E 2015 Original Android Development] Pr!mus:
Same with me ..

otherwise the rom is AESOMME.. :):D
[E 2015 Original Android Development] Casper1982:
Which version is more stable? please...
[E 2015 Original Android Development] Rm77:
I'm using the latest build and i find it to be the most stable
[E 2015 Original Android Development] tarakavinash:
Hey.. After The Sep 3 Update Phone Works Absoultely Fine No Reboots & Sensor Working Is Also Perfect

Thank You Sir..
[E 2015 Original Android Development] squid2:
September 5 Release

The highlight of this build is improved memory management. I increased the size of the zRAM and added in Qualcomm's adaptive low memory killer. These changes will allow you to do more before encountering low memory situations, will reduce the frequency of low memory events through more proactive cleanup, and make low memory cleanups more graceful.

In addition to the memory management improvements, I also cleaned up some vendor blobs, and adjusted the auto brightness curves. I found that in earlier builds, with auto brightness, the display was still too bright in dark environments, and not bright enough in moderate lighting. To fix this, I lowered the minimum brightness level and adjusted the calibration curve so that the auto brightness is reasonable in all conditions.

While not essential, I recommend wiping /system before installing this release. That will clean out cruft from older versions that has been removed. You won't lose any apps or settings by doing this, it will just clean up defunct bits from the ROM. After wiping /system, you will need to reinstall both the ROM and gapps.

As always, the download is up on the first post.
[E 2015 Original Android Development] Casper1982:
Has anyone tried this rom the kernel "BeliveKernel" SaberMod ...?

Works well ...?

http://xdaforums.com/moto-e-2015/orig-development/kernel-belivekernel-belive-power-t3180055

Thanks...
[E 2015 Original Android Development] tarakavinash:
How to Do Wiping / System ? It Will Remove All Apps As Factory Reset ? Please Say How to do.. Thanks
[E 2015 Original Android Development] india_motoe2015:
1. You have to have TWRP / CWM installed (which is a given if you are installing Custom ROM).

2. Boot into recovery.

3. Choose wipe - advanced wipe - select 'system' - swipe to confirm.

4. Make sure you wipe '/system' _BEFORE_ you install ROM.

5. Install latest ROM as usual along with G-Apps & Xposed-framework etc.

6. Done.

Edit 1 - As squid2 said in his post wiping '/system' won't affect your settings / apps. I had apprehensions as well, but I grew a pair & wiped '/system' after squid2's latest post & I didn't lose any app/settings.
[E 2015 Original Android Development] Krizthian:
Have you thought recoverys for carrying more otus? For example port PhilzTouch

Have you thought about that?

Greetings.
[E 2015 Original Android Development] squid2:
I'm satisfied with TWRP, but feel free to port any recovery you are interested in.
[E 2015 Original Android Development] sagnik9:
I have not downloaded the last 2 builds, how stable is the latest build and how is the performance?

actually I'm out of town so it ll be really helpful if someone who's using the latest build could update me with this, then I'll try the latest build(excitement!), otherwise I'll wait till I return home to try the builds
[E 2015 Original Android Development] PseudoDev:
Well, the latest build is the most stable one of all the updates posted till now.

Found absolutely no bugs. Even issues with random reboots have seem to be gone. In short, its perfect. [emoji1] [emoji1]
[E 2015 Original Android Development] Manish_Sky:
Yes i have been using Believe Kernel R03. Its working good on CPU interactive.

Battery saving and good performance.
[E 2015 Original Android Development] Casper1982:
Thanks for answering Bro!!! :good:
[E 2015 Original Android Development] FedeHolyGhost:
I had this rom since June, now my phone bricked after the battery died the other day, now it only turns on to fastboot and says " failed to validate boot image " and i can't flash any stock rom at the moment. I have the xt1511 otus 3g version of Latin America. I even tried with my own and correct stock rom and it doesn't work.

I always get FAILED<remote failure> using any command, always starting with oem fb_mode_set
[E 2015 Original Android Development] IronTechmonkey:
Whew, I looks like I finally found the ROM that should be compatible with Moto EXT1511 (2nd Gen, US, 3G) and I thank you for it. A question: Why do you recommend CM gapps instead of others. Normally I use http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368.

Thanks again for working on this device.
[E 2015 Original Android Development] squid2:
I only recommend CM gapps as a sane default. I've tried TK gapps and they work well too. At one point, I had issues with Euroskank/BaNkS gapps, so I know that some gapps misbehave on this ROM. Any gapps compatible with the latest CM nightlies should work fine.
[E 2015 Original Android Development] IronTechmonkey:
Thanks (out of official ones- it's been busy day :)). It does not surprise be that Euroskank/Banks has problems (although it was solid in other scenarios). .Thanks for the details. Can you also confirm that this ROM can be installed on XT1511 (2nd Gen, US 3G)?
[E 2015 Original Android Development] squid2:
Yes, it supports XT1505, XT1506, and XT1511.
[E 2015 Original Android Development] IronTechmonkey:
Great. I'm being extra careful having realized how lucky I just was to survive flashing various incompatible recoveries and ROMS.that were not clearly labeled. Deep breath, coffee, then flashing and testing your stuff - Thanks!
[E 2015 Original Android Development] IronTechmonkey:
I Installed cm-12.1-20150905-UNOFFICIAL-otus with CM gapps-5.1-arm-2015-07-17-13-29 on Moto E XT1511 via twrp-otus-2.8.7-r2.img. It runs quite well apart from a few sticking points. Please don't consider any of this feedback "asks". I know some of it is just shaking a fist a a Google and CM colored sky scarred by the ongoing war between those 2 titans. The feedback may also serve to shake out one or 2 things that are genuine ROM issues. If there is anything that genuinely seems to merit more testing and logs please say so.

- Compared to stock, Wifi is hitchy. It does not connect as quickly and sometimes stalls while "obtaining IP address". Sometimes it does not connect until the main Wifi settings page is opened, although that could be placebo wherein it takes so long to connect I start doing other things. Once connected performance is good but getting connected is much smoother and more predictable in stock.

- Cannot connect to either of 2 routers by Wifi when a certain new and deeply buried Wifi setting is changed. If "Settings" - "Wifi" - "Menu (3 dots)" .- "Saved networks" - 'Menu (3 dots)" - "Automatic priority" is disabled the device wont connect to wifi. It indicates that the connection is saved but does not respond when "connect" is tapped. This might be an actual bug. If this behavior is by design I'm really curious about why.

- The notification shade and quick tile animations seem to stutter a little compared to stock. It should be noted that in spite of, or perhaps because of, a severe lack of features in the stock ROM and the absence of Provider bloat, the stock ROM for this phone (XT1511) performs quite well and the GUI experience is a bit better on stock than in CM.

- TTS, voice typing, handwriting and google translate had troubles seemingly with the state of the Google App, which I fixed by scouring out tho Google system components left by Gapps and reinstalled those apps and the Google search app from play store and all was well there.

- Although Better Battery Stats has been having fits with Lollipop since the beginning, for some reason, on this ROM, Better Batter Stats has an additional issue where it is not recording partial wakelock statistics. This is bad. After this wave of testing, monitoring battery usage and looking for wakelocks is the next thing (but at least there is Wakelock detector).

- FM Radio A-OK and with nicer features and navigation than stock.

- Issue with screen-on delay on incoming call is not occurring.

- The Stock Moto camera for this phone is much nicer than the CM one IMO. Maybe there is a way to port it.

- As ever, the dark theme option in Messaging cracks me up by doing still nothing but still being present.

Thanks for the ROM and the coaching yesterday!
[E 2015 Original Android Development] Casper1982:
Any Update?
[E 2015 Original Android Development] squid2:
We're going official!

https://github.com/CyanogenMod/android_device_motorola_otus

https://github.com/CyanogenMod/android_kernel_motorola_otus

https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-12.1/otus
[E 2015 Original Android Development] Carlos Arriaga:
wooo Thanks [MENTION=6485916]squid2[/MENTION] good work :laugh::good::D:D
[E 2015 Original Android Development] magdeoz:
first official nightly! thanks Squid

https://download.cyanogenmod.org/?device=otus
[E 2015 Original Android Development] TechnoAnder:
Yes, good work [MENTION=6485916]squid2[/MENTION].
[E 2015 Original Android Development] squid2:
Indeed, official nightlies are now available. For those who are upgrading from unofficial to official builds, it might be a good idea to wipe /system before flashing the new official CM12.1 and reflashing gapps. Wiping /system is probably not required, but it's a good idea whenever you go through a significant change. This won't affect any of your data, all your apps and settings will be left as is.
[E 2015 Original Android Development] Rm77:
Thank you for your work

Big thank you to squid. We have this Rom just because of you.
[E 2015 Original Android Development] Casper1982:
WOW, amazing... thanks bro!!!
[E 2015 Original Android Development] Krizthian:
Thanks for all, [MENTION=6485916]squid2[/MENTION].

Regards.
[E 2015 Original Android Development] tarakavinash:
Official Update !! :D Thanks a lot broo because of u :)
[E 2015 Original Android Development] IronTechmonkey:
cm-12.1-20150912-NIGHTLY-otus-recovery.img with gapps-5.1-arm-2015-07-17-13-29.zip clean flashed with twrp-otus-2.8.7-r2.img on Moto E XT1511 looking generally OK. Digging into a few things including a phantom camera flash setting (flash not applicable to XT151) which seemed to appear during interaction with parallel items in that menu group. Prolly just a first time setup thing

Also, in certain apps scrolling and button presses seem wonky. In TiBU some scrolling jumps through list wildly and bounces off of top of list and back down automatically - a trippy effect even AOKP menu settings would be proud to have:). Could be hardware but not sure.

All hail [MENTION=6485916]squid2[/MENTION], maintainers, et al!
[E 2015 Original Android Development] sinnerz2000:
Now that it's official I'm guessing everything is stable? Sorry I haven't followed updates on this as it was pretty buggy the last time I checked, could anyone guide me to update from stock 5.0 ROM to this? I've never flashed custom roms on a locked bootloader device before.
[E 2015 Original Android Development] sagnik9:
hey [MENTION=6485916]squid2[/MENTION] thanks for the hard work!

just one request, can you please add the link to Otus's CM changelog in the Main Post?

Anybody using todays's Build? how's your experience?
[E 2015 Original Android Development] Casper1982:
+1

Need changelog!!! :good:
[E 2015 Original Android Development] magdeoz:
Here is it http://www.cmxlog.com/12.1/otus
[E 2015 Original Android Development] IronTechmonkey:
You should specify what day you mean by "today's" since time zones come into play. I'm running the first nightly (reported a few posts back), and it seems ok, except for a few small bugs. More details and Jira tickets for those later.

With that in mind, the change logs would come in handy. Will flash up to 9/13 nightly after more testing.

...or you could flash it and tell is how it went ;).

---------- Post added at 12:02 PM ---------- Previous post was at 11:56 AM ----------

Thanks. Not a lot to test for in 9/13 nightly except persistence of LED through lock screen if set to enable LED on with display on, and something about audio. Might be more of a matter of testing to see if previous known goods break as a result of those minor tweaks... in other words I'll wait till there is more meat on the bone before flashing newer version. Meanwhile - trying to finds a way around BBS issues in this ROM (and perhaps all CM ROMS).

.. and speaking of LED's I did not know this stripped down model of a phone had one but there it is.
[E 2015 Original Android Development] sinnerz2000:
Where is the led? [emoji15]