yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] fonz93:
Hi everyone, i am currently building a weekly version (or monthly, depending on CyanogenMod fixes and patches) of CyanogenMod 12.1 for a while now, i thought i could share it with you, because falcon cm-12.1 branch is no longer supported by CyanogenMod.

I made some little modifications to the framework, the device tree and the kernel, which you cand find in the source section.

For those who don't read at those stuffs, the changes are:

- Restored Ambient Display (and tuned a bit) and MotoDoze (wake gestures etc.), since the black screens have been fixed a while ago, this feature is now working correctly here on CM12.1

- Status bar date customizations

- Ability to hide SU icon on status bar (developer settings)

- KCAL support (adjust color contrast and saturation with this app: http://downloads.codefi.re/savoca/kcal)

- Proximity check on wake (disabled by default, you can enable it in Settings/Display), prevents accidental wake ups

- Dexpreopted

- Cyanogenmod's Screencast app from cm-13.0 branch

- Kernel security fixes from cm-13.0 branch

- PowerHAL updates from cm-13.0 branch

- General device tree updates from cm-13.0 branch

- LuK1337 gently found a fix for the GPS bug that forced you to erase modemst1 and modemst2 to make GPS work, so you won't need to do that anymore

- Updated all the libraries and apk/jar's from latest 5.1 build

- Updated Adreno libraries to 5.1 (Motorola is still using 5.0 ones on their 5.1 build)

- CyanogenMod fixed the soft reboots due to strictmode violations (https://github.com/CyanogenMod/andr...mmit/1e60f9b9ae10d46d028c19c90cf0f52d40ca620a), so this fix is of course included here, but is not included in the latest public snapshot for falcon on the CyanogenMod site, so this can be a reason of switching from that snapshot to this build.

- CM12.1 branch is pretty stable right now, so you shouldn't have any major problem

DOWNLOAD

CHANGELOG [06/02/2016]

CHANGELOG [24/02/2016]

CHANGELOG [09/03/2016]

CHANGELOG [16/03/2016]

CHANGELOG [25/03/2016]

CHANGELOG [05/04/2016]

CHANGELOG [12/05/2016]

CHANGELOG [15/06/2016]

CHANGELOG [09/07/2016]

CHANGELOG [10/08/2016]

CHANGELOG [14/10/2016]

READ POST #2 IF YOU HAVE ANY TROUBLE WITH THE ROM, IF IT'S A COMMON PROBLEM, IT WILL BE THERE

CUSTOM KERNELS AND/OR XPOSED OR ANY OTHER MOD ARE HIGHLY UNSUPPORTED

Credits:

- LuK1337

- luca020400

- Gabriele M

- hurtsky

- savoca

- matmutant (for the logo xD)

- Motorola and all the CyanogenMod contributors

XDA:DevDB Information

CyanogenMod, ROM for the Moto G

Contributors

fonz93

Source Code: https://github.com/MotoG-2013

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.4.x

ROM Firmware Required: 41.18+ Bootloader version

Based On: CyanogenMod

Version Information

Status: Stable

Stable Release Date: 2016-10-14

Created 2016-01-29

Last Updated 2018-02-08
[Moto G Android Development] fonz93:
NOTE:

- Reported bugs without any useful logcat and/or Xposed installed will just be trashed

- If you flash any CM12.1 custom kernel, you must flash this package: https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing

in order to downgrade your camera blobs from 5.1 to 5.0, if you don't this, the camera won't work ***

-- If, for any reason, you decide to go back to the kernel included in this ROM, you have to install again 5.1 camera blobs, the easiest way to do that is flashing the ROM .zip.

*** I updated camera blobs from the latest Motorola factory image, a kernel update was needed in order to make camera work after updating the blobs (that's not an hack, is a regular update from Motorola), but CyanogenMod dropped CM12.1 nightlies before doing this, so any CM12.1 based kernel doesn't contain that kernel update, that's why you need to downgrade camera blobs to 5.0.

I have to remind you that installing a custom kernel will break any future support by me
[Moto G Android Development] jotacorredor:
great job! looked for something like this before moving from my snapshot 12.1 ROM which was the first custom ROM I put on this phone. Running identity crisis nowas I need to have a stable NO Root ROM for my corporate email to work but Ill be downloading this rom for sure.

slds,
[Moto G Android Development] lfuentes:
Very nice! Thanks! I missed long time is Ambient Display, so It´s back!!!

The only thing I would like to have in this rom is an option to remove the #RootSymbol in the status bar ;)
[Moto G Android Development] fonz93:
A new build with the feature you've requested is up, you can find the switch in developer settings

(Note: the build informations shows 28-01 and not 30-01, that's because i didn't make a full clean build, i just did a build on top of the old one, there was no reason to make a new clean one, because the "Hide SU icon" feature is the only thing that changed since 28-01 in the source code, so don't worry)
[Moto G Android Development] lfuentes:
Great! I´ve noticed that "inconsistency" in dates, and has no importance ;)
[Moto G Android Development] fonz93:
I've uploaded a new clean build, just to be sure it doesn't bother anyone (no difference from the previous one, it's just a clean build)
[Moto G Android Development] drgopi1234:
excellent ROM. superb thanks for cm 12.1 continue.

pls keep updating .

only one bug though I don't use that is show weather toggle not working and weather not showing in notification drawer.

thanks
[Moto G Android Development] fonz93:
It works here, i think the problem it's the location, somehow cLock doesn't take it "instantly", try to add the widget, update it and delete it, now it should work (that's what i did right now)
[Moto G Android Development] drgopi1234:
OK now it works thanks.
[Moto G Android Development] hamzaalijoiyah:
Nice rom man... keep up the good work.:)

There's a little problem here though, I have tried some CM 12.1 kernels(HurtSky and Optimus) and they seem to break camera. Is it a bug or I should be using CM 13 custom kernels instead cause I really need some features outta them ?
[Moto G Android Development] fonz93:
After updating camera blobs to 5.1, the kernel needs an extra patch too: https://github.com/fonz93/android_k...mmit/17be9afb1bd6fa1737e8365a9f959c9ad5a32e74, that patch is probably missing on every kernel made for the older versions of CM12.1 (or ROMs based on it), this because they use 5.0 camera blobs and they didn't need to merge that kernel patch, this patch is of course included on CM13, but you can't use CM13 kernels, because they use a different ramdisk and selinux policies.

The easiest way to workaround this, it's to flash 5.0 camera blobs and your preferred kernel, i have to remind you that if you flash a custom kernel, i can't give you support in case some bugs shows up, because i will not be able to reproduce or fix them.

Now, you can flash this file, to get 5.0 "camera.msm8226.so": https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing

It should fix your problem, let me know if it works. In case it doesn't, i will provide you a different package with all the 5.0 camera libraries (it will get more time).
[Moto G Android Development] hamzaalijoiyah:
Thanks man for your time and help. But installing this didn't work either. But thats not a big issue I will stick to the stock kernel.

BTW any chance you can odd those 5.1 blobs to Hurtsky or Optimus kernel. Just for curiosity !!!;)
[Moto G Android Development] fonz93:
Try again with this package (same folder link):

https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing

In the kernel part they can only add the patch i mentioned before, but then they will break compatibility for all the other 5.1.x ROMs on xda because those ROMs use old blobs, on the other hand adding 5.1 blobs in the kernel flashable .zip is possible, but can't be done, because of this:

- User "A" installs custom kernel that applied the patch and includes 5.1.x blobs in its package, it will work with all 5.1.x ROMs

- User "A" doesn't want to use that kernel anymore, he installs a different custom kernel, that one doesn't include the kernel patch, but you have 5.1.x blobs in your ROM that have been extracted with the previous kernel installation.

- The camera of user "A" is now broken, if he is not skilled enough, he won't know why and he will probably think his installation is broken, then people will start suggesting him a full wipe and a fresh install without a legit reason.

This could be done only 2 or 3 months ago, when the Lollipop developing was still active and all the developers could update their ROMs/Kernels, but with the current situation, it can't be done.

Can you mention the features you need from custom kernels? if they're not too much invasive i will consider a kernel update
[Moto G Android Development] hamzaalijoiyah:
Only the ability to change Screen Saturation and Contrast. I just like them a bit higher than normal. That's all. None of those funky advanced features.;)
[Moto G Android Development] fonz93:
Do you mean the KCAL?
[Moto G Android Development] hamzaalijoiyah:
Sorry didn't tried these before, they work with CM 12.1 custom kernels.

But anyways having those options baked in the rom (I mean kernel ofcourse) would be very nice. And thanks a lot man for your help.:good:
[Moto G Android Development] fonz93:
i've made a new kernel build with KCAL support, flash this in recovery:

https://drive.google.com/folderview?id=0B-xonQbKq2U2bW5nR3FXa1o1TDA&usp=sharing

Now, because you probably have 5.0 camera blobs in your ROM, to restore 5.1 ones, flash the whole ROM .zip, then you can flash the kernel update
[Moto G Android Development] hamzaalijoiyah:
I really am very thankful to you for this... And sorry too of course for bothering you.... :p

Its working like charm...:o
[Moto G Android Development] dhruvpaul:
Original cyanogen build has a bug...after a few hours of usage the navigation bar and the status bar get distorted! This happens only in landscape mode! Can anyone pls confirm if the same problem is there or nt in this version? I want to switch if it's not because it's very much annoying as only a reboot solves that!! Thanks.
[Moto G Android Development] Chandresh204:
how do i remove CM apps which i don't like... i use google keyboard, chrome, google calendar etc... so i would like to remove the apps that are in the package... and will they remain "removed" when i dirty flash an update?
[Moto G Android Development] Gauri:
Hi guys , i installed this rom over CM13 and now its stuck at the blue logo . I have wiped dalvik cache again but with no avail. Can you please help me as I am a newbie here .
[Moto G Android Development] Sandivisi:
a good place for you http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368 or http://xdaforums.com/oneplus-one/themes-apps/mod-divergenmod-nogoogle-project-t3313709
[Moto G Android Development] fonz93:
And didn't you think that you need to:

1) Wipe system to clean up the old gapps, which can cause most of the issues (FC etc)

2) Wipe data, because you just can't flash an older build on top of a newer one
[Moto G Android Development] fernandodojo:
Hey [MENTION=5439829]fonz93[/MENTION], thanks for your hard work. You did what no one did during lollipop development. Specially for our device. Thanks for the best and most smooth ROM ever.

Enviado de meu Moto G usando Tapatalk
[Moto G Android Development] koshikas:
+1, truly. while it's nice to keep flashing custom ROMs during development, no one makes habit of maintaining stable builds. now that Google is releasing security updates monthly it is almost a necessity. and if you want latest security you are forced to updates into less stable builds still under development, and never get to enjoy using your phone reliably. gosh I'm getting old i guess.

anyway kudos to fonz93 for doing a great job, indebted to you, keep going.
[Moto G Android Development] dhruvpaul:
Out of topic, but these options

1. Disable hw overlays

2. Force GPU rendering

3. Force 4x msaa

Pls tell the pros and cons about these features in detail!
[Moto G Android Development] Chandresh204:
i don't know if this counts as a bug or not, but there is a significant delay in connecting to the wifi after i toggle the switch... it takes a lot of time to connect to the router even when i am standing near it... didn't happen in stock or AOSP.

otherwise a rock solid and smooth ROM!! thanks for your excellent work!!
[Moto G Android Development] STR4NG3R-GUY:
[MENTION=5439829]fonz93[/MENTION] the last update have the new wifi driver?

Enviado desde mi Moto G mediante Tapatalk
[Moto G Android Development] fonz93:
I don't notice this delay, i will investigate

No, we are 5.1 here, i use 5.1 Motorola sources and blobs
[Moto G Android Development] MaKr0:
I have the same problem. (30/01/16)
[Moto G Android Development] fonz93:
I am now including in my folder (the one where you can download my CM12.1) a build of TWRP 3.0 wich slightly differs from the one in this forum, thanks to Gabriele M (which will probably be the official TWRP mantainer), the long time wait for wiping /cache and /system and the not responsive touch is fixed, i am not opening a new thread as it would be unrespectful against h2o64 that mantained the unofficial TWRP for a long time, also because once Dees_troy (TWRP developer) merges Gabriele M changes into the official falcon device tree for TWRP, i will stop mantaining my version as it would have no difference from the official build.

Note: The kernel source used to build the TWRP recovery is this: https://github.com/CyanogenMod/android_kernel_motorola_msm8226/tree/cm-13.0, so it will work on every ROM,

both Lollipop and

Marshmallow

.

Note 2: This TWRP is currently

not working

with GPE, there is a patch made by Gabriele M which shares a script that detects GPE and you lets you use the same TWRP build for both GPE and Moto variant, but i didn't test that patch so i won't include it for now.
[Moto G Android Development] fonz93:
That's the delay? https://www.youtube.com/watch?v=E1HabLnolpc&feature=youtu.be

If yes, i've always had a 10 sec delay even on stock ROM, so i didn't consider it a delay but a stock behavior, can't do anything about it.
[Moto G Android Development] himu_joy:
I like ur all works sir fonz93.

off topic: do u have any kernel for AOSP? that can make AOSP stable likee ur CM 12.1??
[Moto G Android Development] fonz93:
No
[Moto G Android Development] lowlock:
i just flash your rom and after that flash opengapps pico.

i got Google play services has stopped after boot.

i cannot open play store at all.. stuck at checking info.

any solution?
[Moto G Android Development] fonz93:
There isn't a solution for a not existent issue, you probably did something wrong during the flash process, do it once again by wiping /system and /data
[Moto G Android Development] STR4NG3R-GUY:
U dont will add optimizations flags? Or a custon toolchain like linaro?

Enviado desde mi Moto G mediante Tapatalk
[Moto G Android Development] lowlock:
i have flash 3-4 times and wiping /system and /data, the isssue is still there.

i have redownloaded the rom and gapps. nevermind then, i'm back to stock optimized.

thanks fonz.

ps:sorry for bad english.
[Moto G Android Development] Sandivisi:
[MENTION=5439829]fonz93[/MENTION]

your ROM is dexpreopted? what c-apps will work on this rom? because c-apps not dexpreopted.
[Moto G Android Development] fonz93:
That's not a problem, they will work anyway

No
[Moto G Android Development] Chandresh204:
is it possible to change the lock screen wallpaper choosing custom image and not downloading one from playstore ?
[Moto G Android Development] lowlock:
i have found the problem, it is the 27th feb gapps fault.

downloaded and the 26th feb gapps and no fc.
[Moto G Android Development] fonz93:
Unfortunately that's not something i could predict, are you sure you didn't download 6.0 gapps earlier?
[Moto G Android Development] lowlock:
lucky i dont giveup on trying. i can confirm because i still have the zip in my laptop.
[Moto G Android Development] mmxandy:
No FM radio..
[Moto G Android Development] fonz93:
What is this then?
[Moto G Android Development] himu_joy:
hahaha....:laugh:

hope u r not kidding....it has all packed...

has FM...

may be ur hardware is missing?? kidding :D
[Moto G Android Development] Gauri:
Firstly , this is a very nice rom and thank you for that.I have some queries-

1. How to change to a power menu when i press the power button to go directly to fastboot or recovery.

2.I am also experiencing the wifi 10 sec delay , can you fix it ?

3. Can we have gestures on .

Please keep in mind that I am newbie here.
[Moto G Android Development] Sandivisi:
[MENTION=5439829]fonz93[/MENTION] how to install latest SuperSU by Chainfire? just flash zip? and how about Systemless
[Moto G Android Development] hamzaalijoiyah:
Great rom so far. Whichever rom I install I keep comming back to this for its stability and smoothness. Amazing work by developer. :)

I have one feature request about Live Display, as it can automatically change the Color Output based on time of day in most CM13 based roms but in CM12.1 you have to manually toggle the "Night Mode"(at least I don't know any other way around). Any chance that you can add those changes from CM13 to this rom regarding Live Display.
[Moto G Android Development] roshan2989:
you can set it to automatic
[Moto G Android Development] fonz93:
The automatic mode works only with location enabled
[Moto G Android Development] hamzaalijoiyah:
er

Yeah, but it still misses many times.

However in CM13 you don't even need to keep the location and network on all the time. I was just asking if those changes could be merged into this rom.......:p
[Moto G Android Development] Chandresh204:
USB otg isn't working for me,,, how do I enable it?
[Moto G Android Development] fonz93:
It works here, any file explorer with otg support can read it
[Moto G Android Development] dhruvpaul:
I am on the 6/02/2016 build is it recommended to update?
[Moto G Android Development] dirty_smurf45:
In regards to testing...yes :p

This ROM has been great so far; I just flashed a couple days ago and have had no problems with it. The battery life seems great and the Ambient Display features (sweep for notification when asleep and all that good stuff) which I could only find working in the now discontinued Paranoid Android 5.1 are here which makes it even better. I'm glad I came back to CM after about a year. Thanks [MENTION=5439829]fonz93[/MENTION] and credit crew for your builds. :D
[Moto G Android Development] xBiOTeCHx:
I had the official Build from CM 12.1 and changed to this Build because of OTG (Xbox Controller) and smoothness and it's perfect.

Thx to you Fonz to upload this Build and keep it updated :D
[Moto G Android Development] Tridon:
I'm running CM13 and can't wait to switch to this ... As of now, I have a terrible battery drain. Any idea when the March security updates will be integrated ? I'm not asking for ETAs, but if it's just round the corner, I don't mind waiting rather than flashing February's build.

Keep up the good work, mate.

---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------

You might want to try out MiXplorer. Works very well with OTG. There's a thread for it right here on XDA.
[Moto G Android Development] BachuArg:
A couple of days ago I flashed 24th february build.

USB otg works perfectly here.

I'm loving the stability and battery duration of this rom!
[Moto G Android Development] cheppiroma:
How long is your best SOT?
[Moto G Android Development] NinjaFlood:
Hi there. I've using the 24th feb. build as my daily driver for 5 days now and I'm loving it. Thank you so much for making it so stable and smooth.

A couple of things I noticed:

Bugs?:

even though I can set the min CPU frec to 300mhz after a couple of minutes it resets back to the default frec. at 787mhz.

MissingFeatures?

CMFileManager can't handle compressed files (.zip, .tar, etc).

There is no way to completely deactivate navigation rings.

There is no way to replace Heads Up for good old thicker notifications.
[Moto G Android Development] fonz93:
It's normal, the PowerHAL sets the minimum cpu frequency on screen OFF at 300 mhz and on screen ON at 787 mhz, i recommend you to keep it's default value as it's the best and is the one used on stock ROM and by Qualcomm on this SOC.

"Why?"

Having 300 mhz as min frequency will only drain your battery more, because with average loads will always increase the CPU frequency to the maximum, this because 300 mhz can't handle that much load. The CPU at 787 mhz is able to do most of the work so it won't increase the frequency as often as having 300 mhz as minimum frequency.

You should ask this here: https://jira.cyanogenmod.org/secure/Dashboard.jspa

But since CM12.1 is on feature freeze (no new features, only security fixes), i don't think they will listen you.
[Moto G Android Development] raito13:
well, sorry :D

==============

i have some issue on the 24/02

features long press to skip next song doesn't work anymore after couple of days :(

so i have to reboot my device to make it work again :(

should i factory reset ? :D

because on the last update i use dirty flash :D
[Moto G Android Development] fonz93:
I use that feature with my headphones so i know it works correctly, i didn't face any problem. Are you using xposed or any other mod? Can you give me logs? Can't do anything without logs for something i can't reproduce
[Moto G Android Development] raito13:
ohh, i see. i'll try with my headset first

and yeah i don't know how to show you the log :laugh:

i never use ane mod or something :)
[Moto G Android Development] fonz93:
Headset should give the same result as the volume buttons
[Moto G Android Development] fonz93:
NEW BUILD IS UP!

Changelog:

- Android March 2016 Security Bullettin (5.1.1_r35)

- Minor kernel fixes

- Kernel security fixes

- Open source sensors HAL from cm-13.0

--- Motion sensor support

- Minor CyanogenMod fixes

- Sync with CM sources at: 09/03/2016
[Moto G Android Development] mangesh511:
[MENTION=5439829]fonz93[/MENTION] Which is recommend gapps.

tried slim/open gapps but not working
[Moto G Android Development] himu_joy:
Amazing work sir. u made all CM hater to love CM again. and such responsive and helpful person u r. i appreciate ur hard work. will report u soon if found anything.

Some Question:

--> i dont know, was there no motion sensor on our moto g ?? so now, possible to implement MOTO DISPLAY like moto e (2nd gen) ??

--> is D2W is bad for battery? if u just add this feature, then we dont need to use any 3rd kernel.
[Moto G Android Development] fonz93:
I am using open gapps, no problems here (last time i updated the gapps was like 2 weeks ago), open gapps is known to break builds sometimes due to their automatic work, try to download an older build from their github repository

Motion sensor can be either hardware (a dedicated chip) or software (it uses the accelerometer to emulate a motion sensor), in our case it's software.

Double tap to wake will surely use some battery but not that much, it depends on the implementation, too. Since we haven't hardware support, someone tried to implement it on the kernel side (software), the problem is that they have bugs and the patches are, sometimes, bad written. The best double tap to wake patch was made by Gabriele M (current cm-13.0 falcon mantainer), it works perfectly but there is one, single bug (sometimes the touch calibration fails and you get a black screen for 20 or 30 seconds) that blocks me from adding it, this ROM is made for peoples that want a stable build that can be compared to a snapshot and i can't add a patch that causes bugs, even if it happens 1 time a week.
[Moto G Android Development] portagira:
Are there important emprovements in last update?
[Moto G Android Development] himu_joy:
ok, thanks now we have motion sensor so we may have Moto Display now!!! not like ac dispaly/active display. if u know about the function on MOTO E (2nd) , "MOTO DISPLAY" so that we can forget about D2W!!

and sorry, i just giving u an idea sir...not giving u task.
[Moto G Android Development] fonz93:
Moto display actually makes use of the pickup sensor, which is differrent from the motion sensor