yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] cheppiroma:
Really looking forward to this.. Thanks master Fonz ?
[Moto G Android Development] mangesh511:
nice rom.really smooth.no fc.

thanks [MENTION=5439829]fonz93[/MENTION]
[Moto G Android Development] dhruvpaul:
How to test the motion sensor feature? I flashed the zip successfully!! Thanks.
[Moto G Android Development] fonz93:
https://play.google.com/store/apps/details?id=asd.vector.sensor
[Moto G Android Development] Chandresh204:
Moto e 2nd gen has same sensors as moto g but it has moto display and moto actions.... Can't it be ported for moto g ?
[Moto G Android Development] fonz93:
Moto actions and moto display are closed source and depend on motorola framework, they can't be ported, also, moto display without a pickup sensor works exactly like ambient display, so why would someone port it?
[Moto G Android Development] Chandresh204:
Has anyone faced any issues with the sound rattling/distortion, I mean the speaker rattles randomly and then gets back to normal?
[Moto G Android Development] Chandresh204:
can i install supersu or is their no need of one? because with system mod i am getting error in solid explorer that unable to mount /system whenever i am trying to change the permissions

edit: the notifications are hidden even when the phone is unlocked. i have enabled hide sensetive notifications when screen is locked. notifications work normally wheni have disabled that option but now everybody can view my notifications even when the screen is locked. Any solutions [MENTION=5439829]fonz93[/MENTION] ?
[Moto G Android Development] jxnitro:
I can confirm this issue with 9/3.
[Moto G Android Development] de.rach29:
Awesome...wait new update...
[Moto G Android Development] fonz93:
CyanogenMod did some changes there, they probably messed up something, once they fix it, i'll make a new build

Edit: The fix have been included the 10th march but i've made the build the 9th, i will upload a new build ASAP
[Moto G Android Development] Mister Muscle:
this rom best for now 5.1 :good:
[Moto G Android Development] case-sensitive:
I just flashed this on my xt1028, previously running stock rooted 4.4.2 (I did update the bootloader first). The 03092016 image flashed properly and I could sign into google play/calendar/contact, but hangout didi not work --- it kept complaining that it could not connect to the server. I wiped data/cache etc, flashed again and got the same error. When I restored the 4.4.2 rooted image hangout worked again.

Other than this issue the rom works just fine. Any suggestion on how to fix this? THANKS!
[Moto G Android Development] cheppiroma:
Dear master fonz. i found some error in TWRP. When i try flashing a marshmallow cust rom, it keeps saying:

Is there anything did i do wrong? Thanks for helping ;)
[Moto G Android Development] zax1962:
In the latest firmware on March 9, an error occurs when the phone is disconnected from the PC (USB) on the phone screen pops up a notice of low battery, even if the charge is 75%!
[Moto G Android Development] fonz93:
I didn't experience any of this, check your cable/battery

It works fine here, you probably failed a flash (force-rebooted with power button while flashing or something similar) and that's the result, try to reboot into recovery again and do a wipe /system, if it doesn't solve you have to flash via fastboot the stock Motorola ROM, then you can flash TWRP and custom ROMs again
[Moto G Android Development] dhruvpaul:
When is the fixed build coming? I am facing problems with this build, whenever I reboot my phone it optimises 2-3apps then switches to the screen!! What's the problem? Thanks for ur support.
[Moto G Android Development] fonz93:
NEW BUILD IS UP!

Changelog:

- SysUI: Fix hiding sensitive notification behavior

- Minor CM fixes

- Sync with CM sources at: 16/03/2016

This is not a common issue, please give me a logcat of your boot stage
[Moto G Android Development] jxnitro:
Dirty flashed, no issues here.
[Moto G Android Development] dhruvpaul:
Logcat via which app?
[Moto G Android Development] fonz93:
Catlog is fine
[Moto G Android Development] Sandivisi:
Catlog too old, use MatLog for better ui :highfive:

https://play.google.com/store/apps/details?id=com.pluscubed.matlog
[Moto G Android Development] dhruvpaul:
When nd how to take ?
[Moto G Android Development] fonz93:
Just after the boot open the app and save the .txt, then post it here
[Moto G Android Development] fernandodojo:
Fonz, brow thanks again for the awesome job. Well, I would like to know if there's anything you can do about the mobile radio active bug. Both cm and Google claimed to have fixed, but that bug occurs at least twice a day. Since is a lollipop bug, have in mind that on marshmallow rarely happens. So, there's anything you can do or myself?

Because every night before sleep I have to force stop whatsapp and apps like that and activate plain mode.

Thanks again[emoji106]

Enviado de meu Moto G usando Tapatalk
[Moto G Android Development] dhruvpaul:
Here's the logcat! Sry for zip coz xda didn't allow the size limit for uploading a .txt.
[Moto G Android Development] fonz93:
It seems that the dalvik cache for ThemeChooser and Screencast it's corrupted, did you already try to do a wipe dalvik-cache?
[Moto G Android Development] portagira:
Are the changes important from 24-02 build?
[Moto G Android Development] dhruvpaul:
Yes, what should I do?
[Moto G Android Development] fonz93:
I've just read again the log and i found that you are using xposed, that is messing up with the dalvik:

03-20 06:43:48.418 I/dex2oat (899): Using '/system/priv-app/ThemeChooser/arm/ThemeChooser.odex.gz.xposed' instead of file descriptor

03-20 06:43:49.279 I/dex2oat (909): Using '/system/priv-app/Screencast/arm/Screencast.odex.gz.xposed' instead of file descriptor

Just to be clear, i don't accept any bug report with Xposed installed.

Anyway, removing Xposed, installing again the ROM .zip and wiping the dalvik cache again should fix your issue

This case is just an example of why CyanogenMod doesn't accept bug reports with Xposed installed.
[Moto G Android Development] dhruvpaul:
Ok but you don't have to be like them!
[Moto G Android Development] fonz93:
Why? Bug reports with xposed installed are just a waste of time for the developer and for the user, because the bug is caused by xposed, i can't reproduce it and there is no bug in the source code. So anything i try is a waste of my free time. Also, reporting those strange unexistent (unexistent because they're not caused by the ROM) bugs will probably prevent some users from installing the ROM, so tell me a good reason of why should i support Xposed
[Moto G Android Development] methuselah:
Well no dev of any ROM support xpsoed. Xposed is the biggest loophole in security too. So when you flash custom Roms you are almost pretty much filled with what xposed can offer.... Most of the stuff the ROM owner also told. Have a clean flash
[Moto G Android Development] phpbb3:
The point is that any flashable mod makes changes from the code provided by the developer. So in cases where the mod could be involved, it is no longer a fault on the part of the ROM developer, or the mod developer (unless the mod dev offers support of that ROM), its your fault. You put [MENTION=5439829]fonz93[/MENTION]'s code with [MENTION=4419114]rovo89[/MENTION]'s, and its a combination that too few people have to provide full support. There are only so many hours in a day.
[Moto G Android Development] celikbasm:
[MENTION=5910917]dhruvpaul[/MENTION], you can dirty flash ROM for update, without breaking functionality. (at least that worked for me for every update.)

1. Note, what you have installed before flashing. (Xposed, gapps, any other patches etc.)

2. Go to recovery, and wipe, system, cache, dalvik.

3. Flash ROM.

4. Flash gapps, xposed, any other patches

5. Let it reboot. And make a coffee for waiting time. :)

6. Enjoy.

these instructions should be fix your problem.
[Moto G Android Development] fonz93:
If you recently experienced drain issues, it's because the motion sensor was preventing the phone from entering in deep sleep, the bug has been adressed by Gabriele M and i can backport the patch from cm-13.0, as soon as i can i will post a new build with the fix, sorry for that.
[Moto G Android Development] portagira:
[MENTION=5439829]fonz93[/MENTION] can't you make a zip patch and not a new version of the entire rom?
[Moto G Android Development] aldanopolis:
I think that's not possible, because he made changes in sources, and need to build from scratch, isn't only a few apps changes, is whole rom

Enviado desde mi Moto G mediante Tapatalk
[Moto G Android Development] cheppiroma:
Don't think have that issue master.. Seems very good here..
[Moto G Android Development] fonz93:
The issue seems to appear randomly

It is possible, but users that don't read the thread etc.. won't flash it or will ask if they have to, so to avoid any future problem i'll just post a new build
[Moto G Android Development] portagira:
Can't you upload both things?
[Moto G Android Development] fonz93:
sent you a PM with the link of the kernel only

I will upload new entire build in an hour.
[Moto G Android Development] fonz93:
NEW BUILD IS UP!

Changelog:

- Fixed a kernel bug that would prevent the device from going into deep sleep

- Minor CM fixes

- Sync with CM sources at: 25/03/2016
[Moto G Android Development] irvanid:
Thx for the update op!

Can i dirty flash it?
[Moto G Android Development] fonz93:
Yes
[Moto G Android Development] sebastiandg7:
You did it again bro! Thank you a lot!
[Moto G Android Development] himu_joy:
sometime's I wonder how cool a person can be!!! also u r stable like ur rom.

yah, I read all of ur post and learning new things everyday.

Lot of thanks for loving our Falcon, master.
[Moto G Android Development] Pepinos3:
awesome rom thx
[Moto G Android Development] ismail0100:
I am using with hurtsky.

q1: Why flash oto close only 5 sec

q2: Why camera doesn't work without any reason? Yes it working earlier.

is it all about kernel? I didnt test it. Before ask :)
[Moto G Android Development] fonz93:
1) i didn't understand your question

2) read post #2
[Moto G Android Development] ismail0100:
Q1 flashlight working only 5 second then it close.
[Moto G Android Development] fonz93:
It's probably related to the question 2, tell me if it's fixed once you follow the procedure in post #2
[Moto G Android Development] ismail0100:
yea really do. Sorry my eng is very bad so i didn't read first and second post.

is it stable? yes.;

any important bug? no

any important not working app? no

Then u can install it.

This my rules :)
[Moto G Android Development] Xperis:
Strange issue , The flashlight works perfects for me in the 16/03 build.

Maybe a Kernel problem?

Enviado desde mi Moto G mediante Tapatalk
[Moto G Android Development] fonz93:
It was related to the kernel, but there is a specific reason for that, easily fixable following the procedure described in the post #2
[Moto G Android Development] Xperis:
That is true , sure the problem is kernel/blobs.

Enviado desde mi Moto G mediante Tapatalk
[Moto G Android Development] portagira:
Best ROM i ever tried. No lags, no FC, solid like a rock! Thank you [MENTION=5439829]fonz93[/MENTION] !
[Moto G Android Development] NinjaFlood:
Resize partitions

Hi, Fonz93! Is there any way to manually shrink cache and system partitions in order to increase the size of data?

Thanks in advance!

Partition Logs:

/data | /dev/block/mmcblk0p36 | Size: 5653MB Used: 1235MB Free: 2049MB Backup Size: 1235MB

/cache | /dev/block/mmcblk0p33 | Size: 651MB Used: 14MB Free: 637MB Backup Size: 14MB

/system | /dev/block/mmcblk0p34 | Size: 960MB Used: 541MB Free: 419MB Backup Size: 541MB
[Moto G Android Development] fonz93:
Not if you don't want to brick
[Moto G Android Development] cheppiroma:
Thanks master fonz.. This ROM is rock solid, perfecto, very stable for daily driver. Love it very mucho.. Hope you update it always
[Moto G Android Development] :
What is the difference between balanced and efficiency battery mode. I mean with power save and performance its obvious, but I am not sure about efficiency...
[Moto G Android Development] fonz93:
Efficiency (POWERSAVE_BIAS in the source code), is less faster into increasing the frequency, because it has a minimum required load higher than Balanced, also, the hi_speed_freq is 787200 instead of 1 Ghz, this means that it will stay on 787200 most of the times during average usage (1 Ghz with balanced), min frequency on screen on is a bit lower too.
[Moto G Android Development] Xperis:
Someone is having issue with the RAM/Speed in the last build? (25/03)

Or is only my imagination?

Enviado desde mi Moto G mediante Tapatalk
[Moto G Android Development] dhruvpaul:
Yeah me too
[Moto G Android Development] adinkwok:
I highly advise that you stay away from modifying partition sizes. It will potentially lead to uncharted errors and of course, the possible brick.
[Moto G Android Development] fonz93:
Sorry to ear that but i didn't change anything in the source code that could affect the RAM or the speed of the device, you must check your apps
[Moto G Android Development] kingnick:
Thanks for the ROM fonz93, it's obvious that you put a lot of effort into it.

I have an XT1033, I was using lost101's Retail Asia 5.1 Stock ROM (Optimized) v1.0 (XT1033_Retail_Asia_51_Optimized_v1.0.zip) and I flashed to your 25/3 build using TWRP 3.0.0.0-2. I formatted the internal memory partition, copied 25/3 build and OpenGApps 1 April 2016 to the internal memory then formatted the cache, data and system partitions before flashing the 25/3 build then OpenGApps.

Wireless at anything other than close range on the 25/3 seems to perform worse than various stock and custom stock 5.1 ROMs I have used. Excessive buffering on files that played back fine on various 5.1 ROMs I have used.

IIRC Cyanogenmod 12.1 was using an older and inferior wireless driver than stock 5.1, specifically the driver and/or settings used by Cyanogenmod 12.1 resulted in worse performance at range. Any idea if that it still the case?

MX Player video was out of sync with audio when I used it the first time playing a file stored on internal storage. Could there be an unknown issue with Adreno libraries 5.1 and the Moto G?

MX Player seems to be working OK since that initial sync issue.
[Moto G Android Development] fonz93:
I don't know about the wi-fi, the drivers and the binaries are the ones Motorola that gave us, what it can differ are some open source drivers that we build from source and we can't do differently.

I am aware about that issue you described with MX player, it will be fixed in the next update, i will post it as soon as april security updates come up.
[Moto G Android Development] kingnick:
Thanks for the prompt reply.

I suspected as much. I doubt it will make any difference but I will use mfastboot and go back to stock 5.1 then try flashing 25/3 again.

Awesome. I only noticed it the one time but I watch Japanese only audio anime so audio has to be really out for me to notice it.
[Moto G Android Development] fonz93:
NEW BUILD IS UP!

CHANGELOG:

- Fixed a problem with the streaming of videos, where the audio was not synced with video

- Removed the motion sensor support, it is not fully stable and it has no really use on Lollipop, so to avoid any issue

that we had and we are having on cm-13.0, i removed it.

- Kernel security fixes

- Minor CyanogenMod fixes

- April security fixes

- Sync with CM sources at: 05/04/2016

UNOFFICIAL TWRP support by me is ended, the latest official TWRP is working fine so i don't need to keep my project up
[Moto G Android Development] fernandodojo:
Hey [MENTION=745436]Fonz[/MENTION] the skip link on thanks button not workink, and thanks anyway for keeping cm12.1 project alive.
[Moto G Android Development] Mister Muscle:
I love this ROM So Much :)
[Moto G Android Development] fonz93:
Maybe it's due to adblock? Or their site was not temporary working, thanks anyway
[Moto G Android Development] portagira:
To update only needs flash over 25/03 build without wipes?
[Moto G Android Development] fonz93:
Exactly
[Moto G Android Development] sebastiandg7:
Thanks again man.
[Moto G Android Development] dhruvpaul:
The ram management is slowing down, what values for the lmk are in this build?
[Moto G Android Development] fonz93:
The same that have always been, exactly identical from the official cm12.1
[Moto G Android Development] Klirioth:
Thanks fonz93 for the rom. I am downloading the rom, I am tired of using marshmallow.
[Moto G Android Development] Klirioth:
Fonz93. Do you think you can change the camera for the snapdragon camera?
[Moto G Android Development] celikbasm:
Last build's RAM management is terrible. Lots of freezes and memory leaks. I've roll back to 0325 build. If [MENTION=5439829]fonz93[/MENTION] didn't changed anything like said, seems the problem is latest CM sources.
[Moto G Android Development] fonz93:
CM didn't change anything, they just merged AOSP security patches.

I don't think it's a ROM problem, i'd rather suggest you to check your app's, this is still a 1 gb RAM device. Rolling back to 25th march build did not fix your issue, because the issue doesn't exist, RAM management problems do not just appear and disappear randomly without changing anything related to it in the source code, this is something that the users need to understand so that we can save you from saying some of those false sentences.
[Moto G Android Development] Pepinos3:
Perform a clean installation, without a single problem, best ROm :good:
[Moto G Android Development] celikbasm:
I've rolled back and freezes and RAM issues gone, that's what I said. I meant no offences to either cm or your ROM. Maybe need to check the changelog. I'm using same apps without any problem with previous build and I'm happy with that, maybe someone notice issues like me and I suggested to roll back. I experienced even phone app crashed after pressed dial button and this issue is also gone with previous build. I still think that something wrong with latest build. At least for my configuration of apps.
[Moto G Android Development] fonz93:
Why didn't you post a logcat? I am tired of repeating it, do you think i am a magician that i can fix bug without having them? Atleast explain how do you get it.

Anyway, i can assure you that there isn't anything wrong with the latest build, even the dialer crash you mentioned is not present here, also, i would like to know if you are using any mod (custom kernel, xposed etc).

I will say this again, anything in the source code changed that can bring the bugs you mentioned, the last build is totally fine, i am tired to read those types of random bug reports from peoples that don't read the source code (that is totally fine, but don't give those sentences then, i was unexperienced too once, so it's not that you can't learn), this happens every day on the cm13 thread (peoples reporting bad battery and good battery with the same build... Without knowing that in the source code there wasn't anything that changed to increase/decrease the battery life)
[Moto G Android Development] celikbasm:
Yes, I'm using xposed, and everything is working fine with previous build. I didn't changed anything, only updated rom to latest, and had problems and slowing downs after update. Maybe it's only me or maybe other users experienced same. My aim is share the generally experienced issues about latest ROM, if you say it's fine for you, than it's fine for you. Don't take on your own. You're doing great job and thank you for developing for falcon. I will wait another build to test it with my configuration.
[Moto G Android Development] fonz93:
Don't bother reporting any bug reports if you keep it installed.

I am not saying it's fine for me, but seriously how can you keep saying what are you saying? i will write this the last time: THE SOURCE CODE TALKS, no changes have been made that could cause this, so any further issue is caused by you, the bugs doesn't just bring in randomly, there always is a reason, you have to accept that, everyone should.

Guys, you have to stop acting like that, that's referred to everyone, you can't just report the first bug you get here, you have to investigate before reporting, if any change has not been made in the source code, how can the ROM be the problem?

1) I'd like to remind you that reporting bugs having Xposed installed is just misrespectful, every time you make a bug report with Xposed you are just wasting my time, because that giant hack is the cause of most of the bugs (and more the modules you install on it) you've reported (we have many proofs on this section and who knows how many here on xda).

2) It's clearily stated that any bug report without any useful logcat will be trashed, i can accept a reproduce step too, but reporting it and running away on an older build or a different ROM without firstly giving some logs, is just useless, don't bother reporting it then.
[Moto G Android Development] Eurofighter_ty:
[MENTION=5439829]fonz93[/MENTION]

Any chance for hardware encryption ?
[Moto G Android Development] koshikas:
sorry, iphone territory
[Moto G Android Development] fonz93:
This device does not support hardware encryption
[Moto G Android Development] Mister Muscle:
what best custom rom best for this rom ? include feature dt2w ? :laugh:
[Moto G Android Development] Ænimal:
Edit: deleted (wrong thread)

You mean kernel..?
[Moto G Android Development] methuselah:
go with stock, if you want that functionality that bad flash hurtssky
[Moto G Android Development] shrey04:
umm just to make it complete can u change the build date ??

not a bug but i just wanted to make that change i dont have any idea about making these builds or roms ,The Build date mentioned is [mar 5 apr 2016,08.24.05, CEST] its neither mar nor april ! and is the security patch level really april 1 2016 coz even stock moto doesn't has that.. its only till march as of yet! but anyway i'm using your build works totally fine.... but just a way to change that build date???
[Moto G Android Development] fonz93:
"mar" stays for "martedì" that is the italian translation for "tuesday" (i am italian so my build machine writes the date in italian)

Stock is using an older source code, i am using CyanogenMod one, that is up to date with Google sources (that releases a new security patch the first week of the month)
[Moto G Android Development] sebastiandg7:
That means update?
[Moto G Android Development] fonz93:
May security patches didn't come out yet
[Moto G Android Development] T4t4nk4881988:
hi,sometimes when using usb tethering the phone switch to 2g and doesn't work properly and if disable-enable again the 3g signal back to work as before.can you help?thanks
[Moto G Android Development] fonz93:
It's not happening here, can you give me a logcat?
[Moto G Android Development] DoctorStrange96:
About camera blobs on custom kernels.

Will reverting this commit work? (Essentially, we're gonna revert a revert xD)
[Moto G Android Development] fonz93:
Yes, reverting that commit will make the kernel use the previously reverted patch, that means you will need 5.1 blobs
[Moto G Android Development] dhruvpaul:
I am using the latest build but recently after this update I am facing camera problems like "can't connect to camera" can u tell why is this happening?
[Moto G Android Development] DoctorStrange96:
Deleted

---------- Post added at 23:55 ---------- Previous post was at 22:56 ----------

Are you using a custom kernel? Then please read the OP. The solution for your problem may be there.
[Moto G Android Development] dhruvpaul:
No I'm nt using custom
[Moto G Android Development] fonz93:
It's not the first time i say that and it is stated in OP too, REPORTING BUG WITHOUT ANY USEFUL LOG

IS USELESS

Since my camera is working perfectly and i can't reproduce the bug, post a logcat and a kernel log, also describe more accurately the bug, does it happen everytime you open the camera? (are you using the stock one?), is it appening on rear or front camera or both? does the torch work? (using the quick tile), does rebooting fix the issue temporarily?

thanks :D