yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] moralesnery:
Next build will have CDMA "no sim" error fixed, as the changelog for the next build says. Win.
[Moto G Original Android Development] Wadu436:
So I flashed that, CM12 29/03 is installing now, but I have this annoying line that just goes over the screen and distorts it there. any idea how to fix it? I had the same problem with the 23/03 nightly but then in the OS itself, now i have it in the recovery.

EDIT: Will they also keep providing CM12 nightlies when they start releasing CM12.1 Nightlies? I'm kinda dependent on Xposed for Youtube ad blocking
[Moto G Original Android Development] moralesnery:
You must update your bootloader to 41.18 using mfastboot. It has been said a number of times in the previous posts. Try also updating Philz or TWRP (whatever you have installed) to the lastest version. That should fix the flickering problems.
[Moto G Original Android Development] starkly_raving:
Offline charging isn't available for CM12 yet.
[Moto G Original Android Development] kellerman40:
About that whatsapp voice calling glitch when noone can hear you, like the mic is deaf. I have this too. A rom called blisspop has already fixed that as some claim. I also cant send videos over whatsapp, it just crashes. Im on 23march build.
[Moto G Original Android Development] hiu115:
When I call someone using the dialer, they mentioned they heard clicking sounds and were often loud enough to cover my own voice. Another problem is when using the call function from whatsapp and LINE, in which they can't hear anything on my side.
[Moto G Original Android Development] kellerman40:
I think changing some voip releated lines in build.prop should word as i've found on the internet
[Moto G Original Android Development] matmutant:
i think that formatting /system and flashing both ROM and gapps will fix ;)
[Moto G Original Android Development] Kumczak:
To anybody that is stuck at bootlogo and doesn't want to wipe storage - install CM11 first, then install CM12. I did so (without wipes between installations) and it booted up, working fine.
[Moto G Original Android Development] andromobilogy:
Well prolly a nub question but hope someone gives me an idea whats this

hashtag notification sign.

Dont know why been having it all day now.

Not sure if any connection but i belive showed up when opened ES file explorer.
[Moto G Original Android Development] Kumczak:
That means you're running an app that has root access.
[Moto G Original Android Development] Oblivionevil:
Same problem here URL: "abload.de/img/img_20150110_001619tvjgr.jpg"
[Moto G Original Android Development] toothbrush69:
Just experienced a major bug:

Was on a middle of a phone call when the phone suddenly powered off.
[Moto G Original Android Development] abhi0502:
My phone is xt1033 to gpe. But it detecting 2 sims even though I have single sim. I can do outgoing call but I can't receive calls

Problem gets solved by flashing donkey kernel. But wifi is not working as it need to update WiFi modules.

Is anybody getting this bug in xt1033 to gpe or its only me that getting this bug?
[Moto G Original Android Development] OldYellowBricks:
Latest 10/1 build? They added some multi sim changes. That might be why
[Moto G Original Android Development] abhi0502:
9/1 build but I I have converted to gpe .Gpe only support single sim
[Moto G Original Android Development] chinmaybaikar:
Does that mean Dual SIM is supported now?
[Moto G Original Android Development] xgrzenio:
not work. the same error
[Moto G Original Android Development] OldYellowBricks:
Nope. Users have reported that it still doesn't. But it's getting there
[Moto G Original Android Development] matmutant:
CM12 FAQ updated 2015/01/10

I think you are not alone wondering this,so now there's a dedicated FAQ entry about this icon :) :

[SIZE=+1]Q4: What's that # at the to right corner of my screen sometimes?[/SIZE]

This icon warns you that an app or service is currently using its granted root access, maybe your file manager or some automated actions like Greenify auto hibernate is running (in the background?)​
[Moto G Original Android Development] gearguy365:
currently i have latest CM11 nightly installed and i have CWM v6.0.4.7. is that a lollipop compatible recovery to flash CM12?

also do i need to wipe anything(data or cache or delvik) to install CM12 given my current setup?

thanks in advance
[Moto G Original Android Development] Jevinruv:
No, you can just flash the zip, and make sure you flash the lollipop gapps , and it will just be like and update :good:
[Moto G Original Android Development] Kumczak:
Regarding wipes: why dont you read the instructions or the dedicated FAQ?

Sent from my XT1032
[Moto G Original Android Development] gearguy365:
oops! i did go through the OP but somehow it slipped my mind. thanks for reminding me:p

thanks! i am sorry if these questions are answered before or for being noobish

but if flashing cm12 over cm11 doesnt affect my data

then why is it necessary to flash the gaaps given i already have all the play service and google apps installed on cm11
[Moto G Original Android Development] matmutant:
Simply because KitKat gapps are not compatible with Lollipop, so you need to flash L gapps to overwrite the older ones :)
[Moto G Original Android Development] ADr0n:
Which version of system you had before? Stock 4.4.4 or GPE? If you had GPE you should install TWRP with ext4 suport if not just install my version. :)

I installed twrp version 2.8.3.0 and I had this bug, so I install twrp 2.8.1.0 and the same error. So I back to stock 4.4 and then I installed twrp 2.8.1.0 and it works :D
[Moto G Original Android Development] xgrzenio:
I use stock 4.4.4, not GPE.
[Moto G Original Android Development] reversegear:
in build.prop find this line

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

change it to

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

Save. Reboot. Voila
[Moto G Original Android Development] hiu115:
Thanks for the reply! I'll report back soon.
[Moto G Original Android Development] Shub77:
Thanks, but did not work on my 03.19 nighlty + Optimus Kernel R16. I can hear but I can't be heard.
[Moto G Original Android Development] ncmz:
Worked like a charm on 5.1 ResurrectionRemix. Thanks.

Cheers.
[Moto G Original Android Development] maurit43:
Hello ! i want to know if cyanongenmod its stable and what bug has ti got ?
[Moto G Original Android Development] moralesnery:
Check the changelog

http://www.cmxlog.com/12/falcon
[Moto G Original Android Development] UltraMaks:
Starting from the today's build

I wonder what was the size previously?
[Moto G Original Android Development] maurit43:
I read this changelog, so.. its stable or has a lot of bug ?
[Moto G Original Android Development] starkly_raving:
Read the thread, read the commits and the change logs. Nightlies will typically always have some minor bugs until the device maintainer and CM says the build is a Milestone or Release Candidate and is basically "stable"... Keep in mind all custom firmware is in a constant beta test and a state of evolution as commits are added or there are changes to the base code/AOSP...If there are bugs, you as the end user have to decide if you can live with what doesn't work during these pre-stable releases.
[Moto G Original Android Development] moralesnery:
zRAM wasn't used in KitKat stock ROM.

Stock 5.0.2 used 168Mb for zRAM

CM12 used 128Mb until 03/29 build.

Now zRAM will have a value of 256Mb, as the Moto E 2015. Originally this patch would have increased zRAM to 512 Mb but it was a little excessive

details are here http://review.cyanogenmod.org/#/c/84259/
[Moto G Original Android Development] brchickery:
How is anyone installing the newest nightlies on the xt1031? im stuck on the build from the 21st. Gives me the bootloader error.
[Moto G Original Android Development] starkly_raving:
Bootloader issue is resolved in a commit from 3/31. I don't know if its in the 3/31 nightly the build bot pushed last night or will be in tonights.
[Moto G Original Android Development] brchickery:
Slick literally installing it right now............... Failed :( oh well maybe tomorrow. Still great news thanks!
[Moto G Original Android Development] matmutant:
Does anyone have the CDMA 41.19 bootloader to share ? so i can add it to the guide...
[Moto G Original Android Development] boros2222:
Do you guys also always get this message when flashing something in recovery?:

detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system

I converted to GPE and then back to non-GPE. Is it related to it? Shouldn't it be F2FS?

I have never gotten this message in the Kitkat's era.
[Moto G Original Android Development] sjandroiddeveloper:
Guys the screen brightness bug is still there I thought it would be gone on cm 12
[Moto G Original Android Development] Shivam Kuchhal:
system is ext4 on Motorola stock too, only data partition is f2fs. :)
[Moto G Original Android Development] boros2222:
But if it's totally ok, then why does it inform me about it all the time?

Oh, and is there a way to check the partitions file system?
[Moto G Original Android Development] sjandroiddeveloper:
I doesn't show you every time

Its a standard procedure to note everything in the recovery logs

That's it
[Moto G Original Android Development] Membrillo007:
Video issues are fixed?
[Moto G Original Android Development] sjandroiddeveloper:
Not fixed for me

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] netizenn:
Hi There

April Fools in the last Nightly

:D:D:D:D:D:D

1st scares me a hell, but then LOL
[Moto G Original Android Development] eddydc1:
What did they do? :D
[Moto G Original Android Development] tzzeri:
With Cyanogen's deal with Microsoft, I wouldn't say this is so far fetched
[Moto G Original Android Development] sjandroiddeveloper:
Does this screen really comes on 1st April nightly

And what's the deal of cyanogen with Microsoft

Sent from falcon
[Moto G Original Android Development] tzzeri:
Yes

Microsoft gave cyanogen funding, and cyanogen is going to start using microsoft services in some phones, starting with a BLU phone
[Moto G Original Android Development] vsr625:
hey guys, to prevent Google play services to kill my battery I'll usually freeze it.... but while I was using stock ROM whenever I'll freeze it and defreeze it no problem..... but now on cm whenever I freeze it and defreeze it I have to add my Google account again....... it becomes irritating..... you guys have a solution......

and I already tried to use all kinds of solutions against Google play services like greenify,amplify and many other stuff..... but only freezing has done good to me..... so guys any solution......

I even tried to hide it through minminhide but It was waking up frequently.....

and even I tried to block wake up permission from privacy guard.... but it did no good......
[Moto G Original Android Development] sjandroiddeveloper:
Same problem here

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] OldYellowBricks:
Reinstall google play services. Firstly uninstall it. Read this link to choose the one accirding to your screen DPI

www.apkmirror.com/apk/google-inc/google-play-services/
[Moto G Original Android Development] hiu115:
Do you mean the laggy videos? I just use MX Player and changed the encoder to software (S/W) encoding, it ran smooth afterwards.
[Moto G Original Android Development] vsr625:
did it work for you?
[Moto G Original Android Development] Nebulino:
Happy April Fool! New Update From Microsoft!
[Moto G Original Android Development] OldYellowBricks:
Yep. Totally stoped my wakelocks
[Moto G Original Android Development] sjandroiddeveloper:
The stock music app on cm12 closes sometimes automatically while its playing a song

And also sometimes when it closes a error appears that unfortunately audiofx has stopped

Any of you have this problems

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] tzzeri:
In privacy guard (a cm feature) you can prevent it from waking up/keeping awake the device
[Moto G Original Android Development] vsr625:
if you do that then...... Google play services will eventually start running after some time...... this might be because of an app which uses it wakes it up..... many times it's woken up by the android system......

I should add that the many apps which wakes Google play services will work correctly even without it..... so the permission changing thing is not a good idea if you really want to not have play services running in background...... unless you really need it for some apps.... like play store.....

the only thing that helps is freezing......

I'm very clear I think...
[Moto G Original Android Development] miaad:
Hi,

Do I have to perform the add on in the OP to work in dual sim XT1033 ?

Just flash the ROM with a compatible recovery with LP bootloader right ?
[Moto G Original Android Development] sjandroiddeveloper:
Just flash with a compatible recovery and wipe system, cache and dalvik before flashing

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] boros2222:
CM12 can be very laggy sometimes and it looks to be frozen. Does it occur for someone else?
[Moto G Original Android Development] brchickery:
How did you install? I have falcon xt1031 and i still cant install. Today i did get a new message i have never gotten and it said this update could harm my device but it still failed.

Still not working :(
[Moto G Original Android Development] methuselah:
http://www.xda-developers.com/google-to-acquire-xda-dev-rewards-policy-changes/

Can somebody comment on this ....XDA is purchased by google and we no longer will be able to get custom ROMs...
[Moto G Original Android Development] bogante:
April's fool.
[Moto G Original Android Development] moralesnery:
LOL
[Moto G Original Android Development] methuselah:
Well this is enough serious to be posted on XDA news?? But I am on mobile ...so am I missing something lol
[Moto G Original Android Development] bogante:
Don't believe anyting today.
[Moto G Original Android Development] sjandroiddeveloper:
What are you taking about

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] tatun_g:
I´ve just flashed the latest CM12 nightly. How long it takes the first boot?? Because is taking 10 minutes and the logo is still there...Im using twrp 1.8.6.0

:(
[Moto G Original Android Development] bogante:
With lollipop take more time than KK, cuz ART
[Moto G Original Android Development] tzzeri:
Well, then you can turn off keep awake, which I did. It's denied it twenty thousand times (no, I'm not exaggerating, that's what it says in privacy guard). If you disable it, then petty much all gapps won't work.
[Moto G Original Android Development] Orjakone:
I have a doubt, with the support Dual Sim on Android 5.1 will still have the lack of official support XT1033? or this will change?
[Moto G Original Android Development] sjandroiddeveloper:
What are you taking about dual Sim works perfectly on cm 12

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] wskelly:
If you're prevented from flashing the latest nightly due to the bootloader version, you can modify two files in the cm12 zip to get it to pass the bootloader check and flash anyway.

Extract these two files:

META-INF/com/google/android/updater-script

META-INF/com/android/metadata

Alter the files as shown in the screenshots. Put the files back in the archive in the right place.

You will see the flickering/jumping of the screen on the first boot, but this will go away (it did for me) after you turn the screen off and then on once.

Flashing a new bootloader is quite extreme and unless there is a compelling reason to do it, I would avoid it.
[Moto G Original Android Development] sjandroiddeveloper:
There's no need of this kind of heavy work

Just flash the bootloader or if your are scared then flash the whole firmware and then flash cm

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] vsr625:
Yes I too know that...... When you you that then too play services will wake up!?

This is because when you use normal apps they wake play services even if they can work correctly without play services...... That number which comes on privacy guard is only the half story..... So only freezing stops it..... I did a lot of experimenting myself before I'm telling this...... But the wakelocks will be gone if you block keep awake and wake up this doesn't man that play services won't be running in background and consume your ram!?
[Moto G Original Android Development] wskelly:
Heavy work to modify two files... Which you can do without a PC?

No. There's no *technical reason* to update the bootloader. Period.

Users should not be updating the bootloader on a consumer device unless they like owning a brick.

That assert looking for a specific bootloader should simply not be there!

I'm typing this from a Falcon with the old bootloader.

Explain the technical reason for updating it and we will actually have something to discuss.
[Moto G Original Android Development] sjandroiddeveloper:
[/COLOR]

First of all who told you it would brick your device if you updated the bootloader carefully

And second the technical reason is this that as time passes by your old bootloader will be incompatible with every form of mod you want to apply causing more serious bugs and not something you can fix by changing two line without a computer and no one's gonna help you as the obvious answer's gonna be to update your bootloader

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] wskelly:
First of all, I am still waiting for a technical reason why suddenly cm12 for Falcon requires a bootloader update. I don't see one here. There may be a reason, a good one, but I don't see it. I see something about how as time passes I'll be all alone with nobody to help me. That isn't a technical reason. Not that I'm typing this from the 4/1 nightly on my Falcon with the 0x4113 bootloader should matter.

Flickering screen on first boot might be the only reason. If so, fine. But that alone should not force anyone to update the bootloader.

Second, the only reason you can "flash" a bootloader over USB is because the *existing* bootloader provided a facility to do so.

A bad bootloader would be the *only* reason I can think of for a bricked device. The only way back from that is a low level flash, something few people outside of a lab can accomplish.

If there is a strong technical reason to update the bootloader maybe it is buried in a changelog somewhere, but it is clear you don't know where.
[Moto G Original Android Development] dysoct:
May I know the technical reason you want to stay with the old bootloader?
[Moto G Original Android Development] tzzeri:
A bad bootloader?
[Moto G Original Android Development] sjandroiddeveloper:
How to fix in what's app calling feature

I can't hear what the other person is saying

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] andogeek10:
The only technical reason is that the kennel was updated to the latest kernel source release by Motorola which causes the flickering issue on older boot loaders. The flickering can be solved easily by locking and unlocking the screen. The only problem you may face would be due to asserts which can be easily solved by editing as shown above. Hence in my opinion it's not really necessary to upgrade the boot loader as of now.
[Moto G Original Android Development] sjandroiddeveloper:
The su binaries are not updated by even in the latest builds

Sent from falcon

Press thanks if helped ?
[Moto G Original Android Development] OldYellowBricks:
The screen flickering AND basing/adding features from the stock lollipop kernel.
[Moto G Original Android Development] brchickery:
I have no problem flashing a new boot loader them problem is I cant find it! Where is the new bootloader for the boost moto g? xt1031 falcon.

Also I'm not sure what sjandroiddeveloper's problem is, but honestly I'm sure most people around here dont appreciate it.
[Moto G Original Android Development] starkly_raving:
Well when Motorola released 5.X they obviously felt a "technical" reason to update the bootloader. So that's good enough for me and if major aftermarket android developers like CM see a need to use new bootloaders I don't see why people refuse to update.
[Moto G Original Android Development] wskelly:
Yes. Because I don't have a technical reason to change it.

You can brick an Arduino with the wrong bootloader. BUT you can extract the micro and bring it back with a $30 low level programmer. (you can also use the Arduino as a programmer if you have another working micro to put in it)

You can't do this with your phone.

The bootloader is pretty simple, but it CAN brick your phone with no way back.

Thanks to a couple of guys who responded, I know it is only the screen flickering issue. I wonder why this can't be solved on the kernel side, or if there is really a bug in the old bootloader? Only an engineer from Motorola can tell us, and until we know, I want to warn everyone that this is the single most dangerous piece of software to update.

Be careful, that's it.

If you don't want to change it, you don't have to, I explained how.

I need my phone like I need my car. Bricking it isn't an option.

Updating the kernel and the OS are child's play compared with the bootloader. This should be the single biggest take away for everyone. This is why unlocking it is such a big deal for Motorola.
[Moto G Original Android Development] :
I agree. I updated and have no complaints. There is nothing to worry about as long as you don't try to downgrade. I don't get all the commotion about this, it's either stay on your current bootloader and deal with bugs due to incompatibility, or upgrade and have a better android expedience. Or you can alwaya just stick with KiKat. I know one thing though, if people don't upgrade, there will be alot of complaints about bugs in roms that will only be mentioned by those who didn't update and they will be told to deal with it or update.
[Moto G Original Android Development] starkly_raving:
Agreed, specifically going forward with 5.1. The people reporting the majority of the bugs are on the old bootloader with the 5.1 test builds we have(on the CDMA variants).
[Moto G Original Android Development] :
Right now for XT1031, all you need to do is know how to google and install an OTA zip and your bootloader is updated. Unless you don't know what your doing, there is no way to brick your phone doing this other wise Motorola would not put out an ota zip which will update the bootloader. People who don't know what they are doing should just wait untill an official update is out and do some research to find out how to install it properly in the mean time. If they can't do that, maybe they shouldn't be doing things like this with their phones anyway. If you don't know what your doing, you should expect to end up with a brick.
[Moto G Original Android Development] dr.pythagora:
Moving from cm12 to google android 5.0.2?

I am using cm 12. With the influence Microsoft may have on CM development, I am thinjing to re-install android 5.0.2.

To do so, I followed this link

http://xdaforums.com/showthread.php?t=2700502.

But when I rebooted, the phone froze at the white warning bootloader screen. Happily, it was a soft brick, so I managed to

install cwm recovery and next cm12 again.

Question:

is there a safe way to install google android 5.x on moto g xt1033?

Btw I have updated the bootloader to the latest version.
[Moto G Original Android Development] OldYellowBricks:
Lets hope for CM to revert those bootloader asserts.

But CM for samsung devices has also had a similar thing going on where ot wouldnt flash on older bootloaders
[Moto G Original Android Development] wskelly:
OTA would be the best way, agreed.

Buf, we're now talking about a couple of hours involved to flash the OTA, then again unlock, update recovery, then flash back to CM, then put everything back the way I had it.

And... I still don't understand what bugs the bootloader is possibly causing for the application software.