yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] :
I can't answer that because I've never used whatsapp, its not an app I need or want.

Again, you are like me reporting third party apps misbehaving, its noting to do with CM13, but its the app I'm afraid.

My tests have confirmed that any ROM stability is SEVERELY affacted by outside factors such as mods, hacks and customizations and third party interference, such as 3rd party apps.

Also, I've have found no evidence to back up the theory that gapps can be flashed with no problems after intital boot up into android and rebooting into twtp to flash gapps, which was the main reason for my test and obviously incorrect to devs own installation instructions!

I did this because some people were insistent and claiming they could only flash gapps after first boot into android, then rebooting to twrp to flash gapps, which is totally incorrect if we follow devs instruction....

I've come off worst by risking a brand new SD card but that's a risk I took and its my own fault, I cannot blame anyone or anything other than my insistence to prove some people wrong and incorrect gapps flashing WILL cause all sorts of problems.

This test was discussed at length in the resurrection remix ROM thread.

Now my tests are done, I've tried to move back to my normal configuration of CM13, squid kernel, open gapps nano, and xposed, with the android N module.

This worked fine for around 12 hours when the strange behavior from Google related apps began.

I changed my usual open gapps package to a google minimal package and now everything is fine apart from some 3rd party apps (like Facebook and certain home launchers) refuse to work or work to begin and misbehave.

I had a twrp mount failure after my test as I was reflashing the latest CM13 nightly early last week, resulting in having to reflash the marshmallow stock ROM just to get into android, then having to reroot and reflash twrp to get back to be able to flash CM13, a time consuming and tedious process, it was when the stock ROM was installed I found I had the currupt SD card.

In conclusion, all my test taught me was not keep chopping and changing ROM/gapps, as stability is affected, and for what ever reason, open gapps pico/nano packages from 28/06 or newer cause me google app errors.

I'm not discouraging anyone to stop using open gapps or flashing mods / hacks or customizations, how one sets up their device and what they do with it is their choice.

I'm only asking people to air a little caution if they feel the need to test a theory or test a different procedure.

All I achieved is a bag full of problems just to prove a few people wrong and to show gapps must be flashed in the same twrp session as the ROM.
[E 2015 Original Android Development] vayavalla:
I'm using an old one (3.0.0r2) without problems.

Enviado desde mi Moto G 2014 mediante Tapatalk
[E 2015 Original Android Development] ayush rao:
The same experience here.... when I flash a kernel before gapps I get strange behaviour and FCs.

I use CM13, Chriszuma Kernel, Open gapps, Xposed 86, Nova launcher, ViPER4Android and a bunch of Xposed modules........
[E 2015 Original Android Development] Android_noob17:
Yea I don't understand it but the rom>Gapps>kernel order works best.
[E 2015 Original Android Development] :
NO IT DOESNT!!!!!!

I stupidly went off and reflashed CM13 in the order you guys told me.

I performed a format of data and advanced wipes in TWRP.

Flashed in this order.

CM13

A gapps minimal.

Chriszuma kernel.

Xposed v86

Moto G4 boot animation.

First boot took approx 23 mins (!!!!!)

Set up was at best slow and laggy (especially the keyboard)

Once I was past the set up screen I signed into my google account, and it was during this set up I ran into a problem I have never seen before on my moto e.

After typing in my google email, I typed my password and pressed next.

Nothing happened.

I pressed next again.

Nothing.

I pressed it a third time and met an error screen I've never seen before, it said ERROR at the top

And a message at the bottom of the screen.

Something went wrong.

Please try later.

(Next)

Pressing next did nothing, then eventually my moto e rebooted and was stuck in a continuous boot loop.

Another trial trying to get back to TRWP and reflashed AGAIN in the order suggested.

Again, it failed.

I've now tried your suggestion with another ROM (Dirty unicorns) and everything is working but my moto e is so so laggy its practically unusable [emoji26]
[E 2015 Original Android Development] Android_noob17:
I think your phone might be defective because honestly you're the only one experiencing these problems.

P.s try open Gapps nano I use that not the minimal package.
[E 2015 Original Android Development] :
How can my phone be defective????

If you read my previous posts, I told everyone that the only difference in flashing I made was installing the kernel after the ROM and before the gapps-that worked, and I was using an open gapps nano package from may, with no problems what so ever.

So phone not defective am I correct?

Today, I tried to flash CM13 in the order everyone suggested, but that caused me problems, using said open gapps, but a newer package.

It didn't work, that's why I changed gapps to a minimal package, but flashing CM13 in the order you all suggested kept failing.

So I tried another ROM that I know is stable, with a minimal package, and everything is working, just very laggy.

Now what I want to know, is why can't I flash CM13 like you all suggested? What on earth is going on? And why can I install another ROM but get a load of errors if I flash open gapps? I've tried 4 different open gapps today, and had errors with all of them, hence the gapps change.

If anyone has any other suggestions, please tell me, my moto e is working OK now, ive typed this message on it, so I don't think its about to explode or melt anytime soon.............

I'm sorry if my tone seems aggressive, its not my desire to be nasty to anyone.

I'm really really annoyed......

CM13 has always been a good solid stable driver for me, I know I have done something to mess up my usually stable device, but I have not had much luck over the past week, after finding stability I've messed that up just because I followed your friendly helpful suggestions, I'm banging my head against the wall here in England trying to work out what is going on.

The stock ROM is laggy, du is laggy, cm13 works if I don't touch anything google, or install any other apps.

It never was like this, I'm going for a nice hot bath, switch the stupid phone off and get some sleep.

Bah humbug.
[E 2015 Original Android Development] grofweg:
[MENTION=5110289]DonTin[/MENTION] can't speak for CM13, I use AICP and DU (I've 2 moto's). I used to have problems with WhatsApp on TurboRom, but both AICP and DU work fine.
[E 2015 Original Android Development] mrxtc89117:
This is a possible scenario you might be encountering. The emmc drive may be wearing out from too many flashing. These are like SSD drives where you can only write so many times. However, I don't know what the lifetime writes is.

Try and do an fstrim. It's available in the play store.
[E 2015 Original Android Development] :
Here you go......
[E 2015 Original Android Development] vayavalla:
Why don't you just try a simply clean install.

TWRP 3.0.0r2

Latest CM13

Latest Squid kernel (optional)

Latest opengapps

No Xposed or whatever

See if it's working, and then reinstall your apps

Enviado desde mi Moto G 2014 mediante Tapatalk
[E 2015 Original Android Development] mrxtc89117:
Maybe system partition too because flashing writes to that partition
[E 2015 Original Android Development] DonTin:
Thanks, I will give DU a try. Did you experience the Phone FC that is mentioned in the DU thread?
[E 2015 Original Android Development] :
Yeah, that was the procedure I was trying yesterday.

CM13/open gapps for me just is not working.

I can clean flash and install them, but during set up I'm facing f/c and error.

Here's a quick list of my problems yesterday.

1. Format data, advanced wipes, Flash CM13, open gapps nano, chriszuma kernel, xposed.

23(!) Minute boot up, set up error.

2. Format data. Clean flash CM13, open gapps nano, squid kernel r16g, xposed.

Set up error and reboot to continuous boot loop.

3. Format data, advanced wipes, flash CM13, no custom kernel, no gapps, no xposed.

Fully working.

4. Format data, advanced wipes, flash dirty unicorns 10.2, open gapps nano, chriszuma kernel, xposed, all working but device is quite laggy.

5. Format data, advanced wipes, flash dirty unicorns 10.2, open gapps nano, squid kernel and xposed.

All working great at the moment with no errors or lag.

Just looking to find a gapps package now that I can use with CM13, because CM13 will install and work (the 15/07 nightly) but as soon as I flash gapps it goes bonkers.

Edit

I flashed CM13 this morning with a google minimal package, no set up errors but back to strange errors from google apps (after they update from play store)

Gmail not syncing errors but inbox opens

Google messenger f/c

Messages that calendar has stopped.

Play store error (updated play store apk to latest now is ok)

These are the gapps I'm using.

http://xdaforums.com/showthread.php?t=3276606
[E 2015 Original Android Development] vayavalla:
Again: try without the custom kernel and Xposed

You're blaming GAPPS, and it seems Xposed or your custom kernel the problem (or both)

Enviado desde mi Moto G 2014 mediante Tapatalk
[E 2015 Original Android Development] grofweg:
[MENTION=5110289]DonTin[/MENTION] there will always be people complaining about random reboots or lag.

I"m not using xposed or other kernels, just the plain ROM, Dolby Atmos and the suggested Gapps by the developer. Second, when switching to another ROM, backup the current installation, after that factory reset and install the new ROM.

But to get back to you're question: no random reboots with both Rom's. I've experienced lag after some time, but cleaning cache and dalvik once in a while did solve that every time.
[E 2015 Original Android Development] :
I have no custom kernel or xposed installed at this time

---------- Post added at 08:42 AM ---------- Previous post was at 08:36 AM ----------

I've just flashed CM13 (less than 2 hours ago)

No mods

No custom kernel

No xposed.

Everything is working fine until the google apps update from play store, then I'm getting strange messages about gmail no syncing and google messenger has stopped (even if I'm not using said messenger)

This problem was solved by downloading a newer updated google play store from here on xda.

I just want to emphasize to you all that I'm back with a fully working system with no lag at all, once I installed the newer play store apk from the thread here on XDA that did the trick.

Again, I have no mods/or hacks/xposed or custom kernels installed at this time.

Once I had CM13 fully working, I applied said settings to the dirty unicorns ROM (10.4) and tested that, again, I have everything working great and good, so maybe the suggestion that xposed or custom kernel caused my issue is correct, but everything working great and good once more.
[E 2015 Original Android Development] :
Here we go.

All good.
[E 2015 Original Android Development] vayavalla:
Try latest opengapps

Enviado desde mi Moto G 2014 mediante Tapatalk
[E 2015 Original Android Development] :
That's my next step [emoji12]
[E 2015 Original Android Development] :
Vayavalla,

Further extensive tests this afternoon, my conclusions were.....

As you suggested, I DO NOT have any issue with any gapps, I do however face issues if I allow my installed apps to restore via google account.

I no longer sign in to my google account at set up to avoid this (tested and works) .

I DO NOT have any issue with xposed or any modules I run (only 1-the android N ify module)

Tested on several ROM's, nothing untoward to report.

I have found an issue with one of two custom kernels I have used, namely squid kernel and Chriszuma.

I had an 85 % failure rate or strange issues when flashing the Chriszuma kernel.

Repeated my tests with squid kernel, nothing to report apart from no errors or strange behaviour.

Squid kernel, open gapps nano, and xposed all working great on both CM13 and Dirty unicorns, and other roms ive tested.

Many thanks for support and advice!
[E 2015 Original Android Development] dandrumheller:
Could your custom kernel failures be related to different default governor/scheduler settings on different kernels? TBH I haven't really played around with them on this device, but in the past my LG Optimus G just absolutely not play well with certain combinations. Random reboots, lag, all kinds of weirdness. Changing governors or schedulers or both, on a given kernel, would frequently resolve all or most issues. It was trial and error to find working combinations. Others running nearly identical setups did not report the issues I had.
[E 2015 Original Android Development] :
Its entirely possible.

I like you haven't begun to mess around with the governor or scheduler yet, but flashing ChrisZuma coincided with me flashing a newer open gapps package for the first time, and to be honest, I didn't see any issues until I let my usual installed apps reinstall and my installed apps update to newer versions via google play.

So I assumed (wrongly!) That the newer gapps was suspect.

Anyway, I now know after 4 hours testing on a hot Sunday afternoon what the issue was.

Puzzled though, I've never seen my XT1524 misbehave in that way.
[E 2015 Original Android Development] dandrumheller:
If chriszuma is a continuous issue for you. It could also be the overclock causing a problem. Try clocking back to stock settings and see if that helps. My old Aria could only do one step of OC. Second step always crashed it pretty quick.
[E 2015 Original Android Development] grofweg:
Don't quote all these long pseudo interesting posts if you're commenting on a previous one. Just mention the guy. This gets really annoying. Thx.
[E 2015 Original Android Development] dandrumheller:
[MENTION=5875315]grofweg[/MENTION] was that directed at me? Didn't know since you neither quoted nor mentioned me. Didn't quote you since I didn't want to risk annoying you further. But clarity in what a response is related to is often important.
[E 2015 Original Android Development] hafiz_binshah:
My device was actually XT1526 sprint I flashed Asian version of 6.0 on my phone. After that, I flashed CM13 no my phone but SIM card is not detecting. So I tried to flash stock OS again now I'm getting his message.

(bootloader) Preflash validation failed

FAILED (remote failure)

Any solution?
[E 2015 Original Android Development] grofweg:
[MENTION=2734563]dandrumheller[/MENTION] it was a general remark. But if the content someone comments on, is in the previous post there is no reason to quote the whole post again.
[E 2015 Original Android Development] dandrumheller:
I would respectfully argue that such a blanket statement is not always true.
[E 2015 Original Android Development] grofweg:
[MENTION=2734563]dandrumheller[/MENTION] name one!

On most forums I participate it is even a forum rule.
[E 2015 Original Android Development] vayavalla:
What if while you're writing someone else writes another message?

Enviado desde mi Moto G 2014 mediante Tapatalk
[E 2015 Original Android Development] dandrumheller:
I have come across conversations where several similar discussions continue concurrently. A response could be construed to apply to more than one if not specified.

It's not worth my time to dig up examples to continue an off topic argument on etiquette with you.

I shall endeavor in the future to minimize my Willy-nilly quoting, but I prefer to err on the side of clarity.

FWIW the reply button in tapatalk auto quotes the prior post.

//end off topic//
[E 2015 Original Android Development] hafiz_binshah:
Can't flash Euro version in my Asia version flashed XT1526 Sprint any solution. I'm getting this outcome!!!

F:\OS\Android\surnia\XT1524_SURNIA_RETEU_6.0_MPI24.65-39_cid7_subsidy-DEFAULT_CFC.xml>mfastboot flash boot boot.img

target max-sparse-size: 256MB

sending 'boot' (32768 KB)...

OKAY [ 1.126s]

writing 'boot'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 1.743s
[E 2015 Original Android Development] :
I just want to point out if im using the XDA labs app, it automatically quotes the post I'm replying to.

Sorry for the off topic comment, im not wanting to upset/annoy any other users with my gapps and kernel issues any further.

---------- Post added at 08:38 PM ---------- Previous post was at 07:52 PM ----------

If you are trying to flash a stock rom, you should be posting your problem in that thread, not here.

You can try

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

Or

Here

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

Regards
[E 2015 Original Android Development] JekaPinsk:
Hey devs, I've found some proprietary qcom stuff for msm8610 board and if it could help you with developing I will be glad to share it.
[E 2015 Original Android Development] hafiz_binshah:
Thanks for pointing me to the correct direction. Actually the problem is, my sim card is not showing up after I installed asian version any solution for that? Thank you.
[E 2015 Original Android Development] :
You need to ask that question in the stock rom thread.

if your sim isnt working in the Asian stock ROM, then you must ask that question in the stock ROM thread!

I note you also tried to flash a European firmware, a different continent firmware, its possible you have now screwed up your radio and modem, by flashing the wrong firmware, maybe you need to flash modem too?

This forum is for the development of CM13 only, and i note you have used CM13 in the past, but if you are now trying to flash a stock rom, or you are having issues using the stock rom, you can't ask questions about stock ROM problems in the CM13 thread!

Please only ask questions about problems and the development of CM13 in this thread.

You are more likely to get an answer to your question and not risk having your questions deleted by forum moderators if you post your question in the correct place........
[E 2015 Original Android Development] Darale:
Hi guys, I've noticed an error with my 4g connection, apparently it doesn't support this type of connection. If i'm wrong, please tell me how can i fix it on my moto e 2015 lte xt1527
[E 2015 Original Android Development] :
Moto second gen 4lte means it supports a 4g connection, but as you are now running CM13, it doesn't.

There is something you have to flash in recovery on xt1526/xt1527 for LTE to work.

I'm using an xt1524 European device, so I dont have to do that.

I know its tedious but search back over this thread, and I'm pretty sure you will find what you need, unless someone is good enough to point you in a better direction than me!

I'm sure there's a thread for it too on moto e 2015 help........
[E 2015 Original Android Development] czarsuperstar@gmail.com:
Please help if you can. Thanks in advance. I keep getting an error ***No rule to make target ' /root/android/system/out/target/product/surnia/kernel', needed by '/root/android/system/out/target/product/surnia/boot.img' . Stop.

Make: ***Waiting for unfinished jobs....

How do I fix this. I have the kernel folder in the Motorola folder under msm8916-common
[E 2015 Original Android Development] mrxtc89117:
Will the Cyanogen Apps C-Apps work with this rom? There is one for CM13. It is a flashable zip.

https://cyngn.com/c-apps
[E 2015 Original Android Development] :
You are free to try, I did and most of them either don't install or force close, waste of time for me, but feel free to try yourself.
[E 2015 Original Android Development] mrxtc89117:
I tried but it would not flash - error 7. I think I have to mount system partition first then flash. Thanks.
[E 2015 Original Android Development] :
Same error as me, oh well.
[E 2015 Original Android Development] ElDainosor:
Try this:

>Flash first the Xposed v86, even if you don't use it

>After, flash the C-Apps and tell me if it's working.

For some reason, on XOSP i just can only install C-Apps like this so, try it out
[E 2015 Original Android Development] mrxtc89117:
I already have xposed v86 installed. It gave me an error 7 on flashing. I think it needs the system partition mounted. I will try later.
[E 2015 Original Android Development] ElDainosor:
I'll try to reflash it when i can and i'll report. idk why it gives errors, but with xposed flashable zip works. I flash it together just in case. And another thing: Maybe in a clean flash it works.

Possible cases that this flashable could work:

Clean install, flash the xposed v86 first and after the c-apps. or maybe it works on twrp 3.0.0.r2
[E 2015 Original Android Development] czarsuperstar@gmail.com:
C-Apps 13 ........

You have to flash cm 13 first! Than flash Gapps if you use them. Than flash all the mods you want and know work with cm 13, than go to mount and check system and than click install button and find C-APPS cm13 and flash than reboot and you will have it installed. Hope this helps.
[E 2015 Original Android Development] mrxtc89117:
I flashed it after mounting system partition and it works. No FC so far. Now how to uninstall some apps like email.

I now have 2 galleries and 2 calendars and email (boxer). I guess I can remove the old CM apps next time I flash a build using opengapps config.
[E 2015 Original Android Development] czarsuperstar@gmail.com:
Uninstall.....

Use system app remover on the play store.
[E 2015 Original Android Development] kumaranwade:
I did exactly as mentioned in the first post wipe cache dalvik data and installed latest nightly build(cm-13.0-20160723) everything goes well.. After rebooting im facing problem , i cant finish the setup wizard since the notification toggle comes up and close ... but no fc yet.. I dont know what to do and its all due to the next or back button not working.. Any help would be appreciated !! waiting for a reply
[E 2015 Original Android Development] :
First, why did you reboot?.

Second, did you install any gapps?

Thirdly, Did you flash gapps straight after flashing 07/23 or did you reboot first?
[E 2015 Original Android Development] kumaranwade:
Yes I flashed open gapps pico latest one just after cm zip
[E 2015 Original Android Development] pda1ey:
Process System Isn't Responding

Hi,

I just moved to cm13 from cm12 on surnia. Whenever I boot I get the above message, though it doens't happen straight after the initial ROM flash.

I get the message in safe mode, and with or without being rooted. Clearing caches etc doesn't help.

Sometimes I find that wifi won't turn on after this and I have to reboot again.

I've tried a couple of different nightly versions from the last week and have the same problem on them all. I've even tried a modified boot animation as I found a thread that blamed this.

I have adopted my sd card as internal storage, though I don't know if that would affect this.

Thanks...
[E 2015 Original Android Development] vayavalla:
Do you have your modem updated?

Have you done a clean install, without recovering the config from google or any backup?
[E 2015 Original Android Development] mrxtc89117:
Does the CM Dialer Reverse Lookup work? I've never seen a caller id come thru. Or the People Lookup I think is broken too.
[E 2015 Original Android Development] pda1ey:
Yes I updated the modem and did a clean install, though I allowed Google to reinstall some apps during the startup wizard.