yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] fonz93:
You're right, i am a new user and i didn't even know there was a dedicated Q & A section, that's why i thought that could be useful to add that fix in the first post.

I don't know if all peoples read the installation process (i don't xD), try to add it somewhere peoples must read.

Between the known bugs maybe, as LuK did for Moto G 2014: http://xdaforums.com/moto-g-2014/orig-development/rom-cyanogenmod-12-t2993932
[Moto G Original Android Development] jonnug:
I'm having no real trouble with it.

1605 nightly, nice and smooth.

Only minor error I see is when using Waze satnav, get a Moto geofencing FC, but GPS continues to work fine.

---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------

One other thing, if you're going to try it, do the setup with no sim cards in. Some users have found it to be a bit screwy unless you do so.
[Moto G Original Android Development] UltraMaks:
Some questions about battery life

As you can see below when I put the phone into Airplane Mode (2-nd night) (for the night) it only uses 2% for 8 hours that is OK.

But, when I do not do this it drains batter much harder (1-st night)

The signal strength is ok so it should not affect much (I mean when signal is lost and found it "kills" battery)

Also as I see using WiFi is the reason why phone is losing its charge very much. Is it ok?

PS firmware - 20150612
[Moto G Original Android Development] dendi:
[MENTION=3816475]matmutant[/MENTION] bro rom is just amazing ! trust me its smooth ! only battery mate ! heavy drains ! :( sot is hardly 3 hrs mate ! and black screen ambient display problem ,, and that whatsapp call problem ( which u already have a solution to but only has to implemented by default , making changes to build line ) .. these 3 issues mate and damn ur rom is the perfect ! please do implement the whatsapp call ( build prop fix ) from next build mate ! everyone has responded its working after changing that line and also a logcat has been provided 2 pages back i guess !
[Moto G Original Android Development] luca020400:
As of now the WhatsApp fix is last thing will be added xd

I never faced ambient display black screen and the logcat is weird

And battery drain cannot be improved
[Moto G Original Android Development] objr:
1) What do you mean about saying that the logcat is weird! Tell me what's wrong and I'll make another log.

2) Changing this line in the build.prop from "true" to "false" makes every single VoIP app work perfectly in this ROM.

use.voice.path.for.pcm.voip=false

There are no negative side by changing that value in the build.prop... I always change it after I flash the latest nightly and I haven't had any problem at all!

use.voice.path.for.pcm.voip=false

Inviato dal mio Moto G utilizzando Tapatalk
[Moto G Original Android Development] luca020400:
2) changing it to false will break the mic in google hang outs for VoIP...ask me how I know lol :) unless we can do a split one true one false, not sure which would be which though.

Need more information. Get some logs from whatsapp/hangouts users on stock and see what use cases the device is selecting for both those apps. We are likely mapping incorrectly somewhere.

As of now I haven't found something useful in logs *comments*

1) Everything EVERYTHING crash
[Moto G Original Android Development] objr:
To me, hangout VoIP mic works just fine!

Anyway... Let's forget... I'll keep changing the line manually ;)

Grazie lo stesso Luca! //italianLanguage

Inviato dal mio Moto G utilizzando Tapatalk
[Moto G Original Android Development] luca020400:
Can you pm me the logcat ?

I may find something useful ...
[Moto G Original Android Development] UltraMaks:
is there a way to dump a log for the moments when Ambient Display fails?

I found the issue again yesterday, when I was unable to wake up my display neither by power button nor by moving my hand over the sensors. I also found that my display was turned on (I saw the backlight was working) but as usual pressing the power button only showed my homepage for couple of milliseconds and only for 1 time from 6-7 times of pressing the button

BTW right now I see, that while I can turn on the display by simple hand's moving I cannot call power menu by pressing power button. It's behaving just like there is no power menu at all. And only after switching on and off the display by power button for several time this power menu starts showing up normally. This is definitely a bug (seems like ambient" functions are over usual functions that are called by pressing power button).

So i wonder what if I dump a log at this moment and send it. Can it help to resolve this issue with dark display when ambient function is on?
[Moto G Original Android Development] luca020400:
I was talking about Whatsapp

I already have ambient display sod logcat ;)
[Moto G Original Android Development] UltraMaks:
I know that it was about whats up issue :) but just decided to reply to point your attention for this bug

In any case you can count on me for testing this issue as I want it to be fixed very much :)

BTW is there a way to decrease the time from automatically switching off the display to a point when it accepts "ambient" hands moving? I mean when the display just turned off automatically I have to wait for a couple of seconds to turn it on by sliding over the sensors while if I turn the display manually (power button or double click in the top corner) I can move immediately over the sensor and display is immediately powers up
[Moto G Original Android Development] luca020400:
Yes , but it got removed with pocket mode

I will try to reimplement it ;)
[Moto G Original Android Development] objr:
Yeah, sure! I'll "PM" you as soon as I can!

I'll give you a full logs about everything

included dsmg.log; event.log; main.log

and obviouslly logcat.log
[Moto G Original Android Development] dendi:
mate i think ure wrong here ! i think ! hangouts voip is working fine after changing the line in build prop .. might as well implement it thn right buddy ? after changing the line whatsapp calls , hangouts call everything working fine buddy ! why not implement and save all the hassle ?

---------- Post added at 05:28 PM ---------- Previous post was at 05:27 PM ----------

mate hangouts working for u too right ? after changing the build prop lines
[Moto G Original Android Development] objr:
As I said before., i don't have any issues after changing that build.prop to false and rebooting the device makes all the voIP apps work just FINE!!!!
[Moto G Original Android Development] luca020400:
I need a logcat ( with WhatsApp crash ) and I'll try to implement this change in nightlies ;)
[Moto G Original Android Development] objr:
You didn't understand!!

WhatsApp doesn't CRASH, only though the other person you are calling can't hear a word you are saying but only noise!

The app works... __doesn't__ crash, that's why I wonder what you can read fron the logs!!!
[Moto G Original Android Development] luca020400:
Logcat anyway [emoji14]
[Moto G Original Android Development] dendi:
there is no crash mate ! the call is working fine ! just that the other end ur voice is not audible ! sooo :P hope objr provides u with the logs u want :D
[Moto G Original Android Development] UltraMaks:
Dude, we all understand that whatsapp is not crashing. Anyway developer needs logs to see what is going on on a system level!
[Moto G Original Android Development] dendi:
did u read he prvios message by lucas ? he was like whatsapp crash logs , so was just telling him that was not the issue :P chill
[Moto G Original Android Development] matmutant:
NO.

There are two issues and he was responding to both, leading to confusion.

The whatsapp issue (that i don't care about btw) that is NOT crashing and we need a new logcat.

The black screen issue with Ambient Display where THE WHOLE DISPLAY SYSTEM is crashing : qdoverlay spams with issues, and for now we couldn't figure what is the culprit even after reading logs.
[Moto G Original Android Development] methuselah:
I try to tell whats the issue

[MENTION=3816475]matmutant[/MENTION]

Well whats app just work fine on nightlies and all other ROMs based on cm12.1 resources. But whats app calling feature is not working. Suppose if i do call then the other party, it will not hear my voice. I could hear them but they can't hear me. Well this issue is very old. Somebody figured out that by changing the value of build.prop of use.voice.path.for.pcm.voip from FALSE to TRUE or reverse it ......make everything working perfect. You just need to edit this to make VOIP apps working. This ranged from hangouts call to whatsapp calling. I Mean in all apps where the VOIP required. ATTACHED screenshot after fixing the issue.

http://droidgeeks.org/how-to-fix-whatsapp-call-no-voice-error/
[Moto G Original Android Development] sjandroiddeveloper:
You're saying the reverse of it

We have to change the property to false

Its already set to true by default

Don't provide misinformation
[Moto G Original Android Development] fonz93:
Luca asked for a logcat, you're still not providing it, we all understand that changing that .prop line will fix VoIP, but until he knows that is a device only bug he won't implement that fix, because it can be a bug at framework level or it can be fixed differently, maybe the .prop method is not the right way, even if it works, but we won't know that until you post a logcat. Stop writing all the same thing.

Edit: just because i will may need VoIP in the future, i'll post the logcat myself, but you need to learn doing logcat, because you can't keep reporting bugs without logs.

logcat (it's huge, but it contains whatsapp call log only):

http://pastebin.com/TkitEtyA
[Moto G Original Android Development] luca020400:
Finally thank you :)
[Moto G Original Android Development] thestory101:
Anyone here get device to deepsleep state ? I was on PAC man it's able to get to deepsleep. Not sure which application blocked it.

I was on 0611 and now on 0619. no deepsleep now. Weird
[Moto G Original Android Development] fonz93:
I am able to get deep sleep with 0618, did you try to use wakelock detector?
[Moto G Original Android Development] thestory101:
ah, some how now on 0619 Im able to get deepsleep now. thx so much.
[Moto G Original Android Development] jri3:
I create flashable zip to change use.voice.path.for.pcm.voip to false.

So updating on cyandelta dont have to manually edit build.prop files.

Just add in additional zip after ROM installed.

pcm-voip-false.zip - 150.27 KB
[Moto G Original Android Development] fonz93:
The Whatsapp voice calls fix will be merged soon through gerrit
[Moto G Original Android Development] Snowers96:
Source?
[Moto G Original Android Development] luca020400:
Gerrit ?
[Moto G Original Android Development] bloodhound42:
Review

Hey anyone here flashed today's nightly how's it does it run well or is it having any problems ?
[Moto G Original Android Development] bloodhound42:
[MENTION=3816475]matmutant[/MENTION]

i tested the whatsapp and hangouts video and audio call no issues after changing the build.prop line to false
[Moto G Original Android Development] Shub77:
I'm testing it, no problem so far.
[Moto G Original Android Development] wskelly:
[MENTION=5778309]luca020400[/MENTION], are you the Moto G maintainer for CM?

I notice that now *three* different bootloaders are allowed by assert. Is there a reason they are all compatible but 4113 (what I'm still using today) isn't?

Or, do we know the difference between the three that are allowed?

From the install script:

"This package supports bootloader(s): 0x4118, 0x4119, 0x411A"
[Moto G Original Android Development] luca020400:
You're on KitKat bootloader probably

If you're on LP one then I'll add support
[Moto G Original Android Development] fonz93:
4113 is KitKat

There are issues with bootloaders < 4118 and Lollipop kernels
[Moto G Original Android Development] luca020400:
Then I'm not going to support this bootloader

Update it :)
[Moto G Original Android Development] bloodhound42:
Bug

Priority notification settings or downtime settings are not found directly in settings in newest build apart from that all are cool :)

Device: Xt1033

version: CM12.1 -20150620
[Moto G Original Android Development] rasputi:
I cant enable back cyanogenmod Camera, I disable it like a month ago but now I wanted to use it again to test it but when I go to the disable apps I cant enable it again, someone knows how can I use the app again?
[Moto G Original Android Development] Shub77:
You my try third party unfrozing apps.
[Moto G Original Android Development] wskelly:
Yes, and I'm running with your 12.1 nightlies using 0x4113 just fine and have been for months. But... I have to circumvent your assert (which is also in the FAQ). This also means I can't use a tool like Cyandelta since it depends on me *not* manually modifying the zip file for it to work.

The Moto G hardware

has remained constant

since 2013. And the Moto G, like every other Android device, boots a Linux kernel. Thus, a Moto G bootloader is a Moto G bootloader. There should not be a KK or LP distinction, or?

If there *is* a distinction, I'm just asking what it is.

Thanks for your support of our device and your time.
[Moto G Original Android Development] phizi0n:
Search the thread, there's many pages of arguing about the bootloader requirement already. The TLDR summary is that mismatched kernel+bootloader causes screen flickering during boot and the devs would rather just require users to use the newer bootloaders than worry about the possibility of other unknown bugs.
[Moto G Original Android Development] wskelly:
You may need to reread those old posts and see who was involved.

The many pages of discussion AND the method to circumvent the assert are all from me.

The fact is that my original question has never been answered. Screen flicker is almost certainly introduced by the kernel (some kind of hardware init change), because early CM12 with 0x4113 never had the flicker.

The guy who introduced the assert is here and I'm asking him directly the same question I asked months ago, because I strongly believe there is no reason to mess with the bootloader on this device, and the assert is unnecessary.

(Sent from Falcon on 12.1 6/16 nightly which booted absolutely fine under the 0x4113 bootloader.)
[Moto G Original Android Development] fonz93:
Early CM12 was fine just because it was still using old KitKat stuffs (including the kernel).

You're not messing with the bootloader anyway, there's a reason if it requires 4118 bootloader and it has been explained (screen flickering with 4113), Motorola automatically updates the bootloader to that version when you update stock ROM to Lollipop, so there's no messy, is just how it has to be, so, if you still want to use this ROM, do it in the unofficial way until you update your bootloader.
[Moto G Original Android Development] bloodhound42:
can anyone confirm whether cmdownloader or delta updates works well and again should i flash gapps ?
[Moto G Original Android Development] fonz93:
You don't need to flash gapps again.

CM updates works fine.
[Moto G Original Android Development] bloodhound42:
hmm i am asking about delta updates either via cmdowloader or cyandelta
[Moto G Original Android Development] sjandroiddeveloper:
Delta updates through cyandelta or CM downloader works fine and no need to flash Gapps again
[Moto G Original Android Development] wskelly:
Why not force 0x411A as it is the largest number and must be better?
[Moto G Original Android Development] luca020400:
Every device has different bootloader

It may brick your device
[Moto G Original Android Development] wskelly:
There we go.

So why assert or "require" one of three values for ALL Moto G variants?

Better is to warn the user that their BL may not be compatible (reason?) instead of forcing the update. There are entire threads here devoted to bricked Falcons and this assert is a primary reason.
[Moto G Original Android Development] luca020400:
Reason has been explained 10^1039 times

We don't force

It's user choice to update it
[Moto G Original Android Development] wskelly:
Then remove the assert! Please!

Those who DON'T update can't use Cyandelta, and the normal flash process is more of a pain ONLY because of those lines!
[Moto G Original Android Development] luca020400:
KitKat bootloader causes unexpected bugs unrelated to rom

And I'll never revert it
[Moto G Original Android Development] wskelly:
Please point me to any discussion or bug reports on this topic. Thanks.
[Moto G Original Android Development] luca020400:
Ctrl + f ?
[Moto G Original Android Development] drgopi1234:
Is there any chance of disable sim color option in sim setting for dual sim ?

Because that color doesn't go with other theme applied only 5 color not match with theme

Or any option of providing none in color option so it catch theme color
[Moto G Original Android Development] Feche:
Screen flicker is the only bug I faced using the old bootloader.

Instead of arguing why don't you just update the damn bootloader?
[Moto G Original Android Development] wskelly:
Yeah. It is looking that way. Like most Linux/Android users I don't like being forced (which is what assert() means, agree or not) to fix things that aren't broken, especially the most critical piece of software in any embedded device.

Then I think wait, why? Certainly not because 0x4113 doesn't load the kernel like it was told to do in 2013?

It's ironic, Luca won't implement the build.prop change to fix the Whatsapp issue until he understands WHY it works (which I agree with, this is a conservative and responsible approach) ...

But literally hundreds if not thousands (this is a popular device) of people have updated the bootloader because these lines are there telling them it is REQUIRED. And the many threads for those with bricked Moto Gs are a consequence. There really isn't any other way to brick a phone.

The irrefutable truth is that only a Motorola engineer can explain the differences between 0x4113, 0x4117, etc. And to assert three possible options but NOT also assert specific hardware (?) for each option is just irresponsible.

I've been using CM since Nexus One. It is a ROM for users who don't like the restrictions in OEM ROMs. Users shouldn't need to jump through unnecessary (dangerous) hoops to install it.

This kind of nanny assert() stuff in the update script is being abused in this case, it only confuses users who want to try CM but in some cases are told to update the BL.

People should ONLY update the BL if they have a problem, and a flickering screen at first boot is not a big enough problem to assert() one of three BLs. The script should, if anything, print a warning about the potential for a flickering screen, but not abort the install!

By all accounts here, there are no known issues with 4113 and CM12.1 except the screen issue.
[Moto G Original Android Development] Shub77:
I use cm downloader, I don't have to flash gapps every time. It works very well, I prefer it over cyandelta.
[Moto G Original Android Development] WesleyMontenegro:
Fix for Camera crash?

Sent from my LGMS395
[Moto G Original Android Development] fonz93:
[MENTION=3101826]wskelly[/MENTION]

You're not going anywhere, this is not an unofficial build, this is official CyanogenMod, there are requirements for things, and screen flicker is a bug that official CyanogenMod does not tollerate, so, stop this thing here, the assert won't be removed.

Updating your bootloader to the official 41.18 one, won't brick your phone, who bricked it, it's because they didn't follow the right procedure, Motorola updates the bootloader to 41.18 with the official Lollipop update, so if you flash stock Motorola ROM you will update your bootloader to 41.18 without bricking anything, you're just making the thing bigger than what it is.

The change to the build.prop line that fixes whatsapp voice calls has been requested through gerrit the 4th of may (by luca020400), but someone reported that mic is muted on hangout after that change (this is not true, because i tested it personally), since then, they don't want to merge this fix, we've provided logcat and feedbacks about it, but the commit is there on gerrit, abandoned, not by us anyway.

Which build are you using? I haven't any camera crash
[Moto G Original Android Development] luca020400:
This discussion is pointless

We provide support for lollipop bootloader as old bootloader causes bugs

Can you understand ?

You install a Linux distro and wifi doesn't work . You're forced to change it ( unless you know how to fix it ) . Same here
[Moto G Original Android Development] Shub77:
Keep KSM disabled. (Kernal Same page Merging)
[Moto G Original Android Development] bloodhound42:
Which recovery ur using I am on twrp latest version but after downloading update its showing sorry can't apply the update please visit FAQ on website ...

Can u help me how should I do it I gave root permissions also
[Moto G Original Android Development] JoaoMarcos:
I'm having FC with Settings app in the last build.

Someone too?
[Moto G Original Android Development] Droidriven:
If nothing has been changed in settings in the new build then try the settings apk from the old one.
[Moto G Original Android Development] JoaoMarcos:
I changed the theme and the problem was solved.
[Moto G Original Android Development] wskelly:
Could someone with the updated bootloader kindly post the contents of:

/proc/cmdline ?

ES File Manager can reach it, or adb shell.

Thank you.
[Moto G Original Android Development] matmutant:
Here is mine :

console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags androidboot.write_protect=0 androidboot.emmc=true androidboot.serialno=TA92907E9M androidboot.baseband=msm androidboot.mode=normal androidboot.device=falcon androidboot.hwrev=0x83C0 androidboot.radio=0x1 androidboot.powerup_reason=0x00100000 bootreason=hardware_reset androidboot.write_protect=0 restart.download_mode=0 androidboot.fsg-id= androidboot.secure_hardware=1 androidboot.cid=0x7 androidboot.bootloader=0x4118 androidboot.carrier= mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_mot_cmi_720p_video_v2

I'm to busy to "meld" thel and seek for diff atm
[Moto G Original Android Development] gardengnome:
Recent nightly (23rd) gives me constant soft-reboot-loops. It seems to me that it crashes in the moment when radios/wifi are activated. Makes sense considering the latest changes to wifi. Restored system via nandroid.
[Moto G Original Android Development] knizmi:
Works fine for me. Both before and after setting the Wifi region.
[Moto G Original Android Development] wskelly:
Thanks [MENTION=3816475]matmutant[/MENTION]! Did not see the other thread by [MENTION=6748252]gundelgauk[/MENTION] but we are thinking the same thing. Will diff as soon as I get to a PC...
[Moto G Original Android Development] tlwhitec:
Guys, I'm afraid there's no significant difference..

$ diff -u0 bl*
--- bl4113.cmdline	2015-06-23 15:45:36.543775679 +0200
+++ bl4118.cmdline	2015-06-23 15:45:48.691775901 +0200
@@ -9 +9 @@
-androidboot.serialno=TA93008L72
+androidboot.serialno=TA92907E9M
@@ -15,2 +15,2 @@
-androidboot.powerup_reason=0x00004000
-bootreason=reboot
+androidboot.powerup_reason=0x00100000
+bootreason=hardware_reset
@@ -22 +22 @@
-androidboot.bootloader=0x4113
+androidboot.bootloader=0x4118
[Moto G Original Android Development] wskelly:
Thank you [MENTION=5290873]tlwhitec[/MENTION], the bootreason argument is interesting.

"reboot" with 0x4113

"hardware_reset" with 0x4118

The powerup_reason argument has a slightly different flag set:

bit 14 with 0x4113

bit 20 with 0x4118

When the kernel is loaded with these arguments it MAY cause the flicker? The only way to test would be to force these arguments in the kernel source, rebuild and flash only the kernel. I am nearly obsessed enough with this bull**** that I will do it.

Attached visual diff.

[MENTION=6748252]gundelgauk[/MENTION]