[Moto G Android Development] afickinger:
I had the same problems as you - "unstable wifi", "apps closing suddenly" and "high battery consumption", with the last build Resurrection Remix (RR-P-v7.0.1-20190324).

A few times, I had to reinstall the ROM because it made the screen freeze after registering a password (the last thing I do after installing a ROM, because I don´t want to put the password everytime I reboot the phone to set things up...), and I lost access to the phone.

You know what worked for me?

Switching from the Trebuchet Launcher (that comes with the ROM) to CPL Launcher.

One of the times I was re-reinstalling the ROM after the screen froze on lockscreen, I decided to uninstall Trebuchet and switch to CPL Launcher because I like it more(!). Imediatelly, the phone became more fluid, the wifi more stable and the screen didn´t freeze after password registry.

Why don´t you try that and see it if works for you?

- install CPL Launcher

- set CPL launcher as a default app

- uninstall Trebuchet (uninstall as a system app)

- reboot the phone

(after you uninstall Trebuchet, you may see messages like "Trebuchet stoppped", "Problem with Trebuchet", "You f** Trebuchet, wtf??!!" - just kidding - just reboot the phone and messages will disappear as CPL will become your new default launcher).

Hope it works for you as it did for me... =)

p.s.: my problem with music audio on earphone came before switching launchers. Just for the record...

---------- Post added at 12:45 AM ---------- Previous post was at 12:39 AM ----------

It´s true. It´s an old device. But there´s something about programmed obsolence that really annoys me... doesn´t annoy you?

At the same time it´s like "I dare you to keep up, you old Moto G!"

...and Moto G and the Custom ROM developers (!!!) keep surprising me.

Think of it that way.

---------- Post added at 01:09 AM ---------- Previous post was at 12:45 AM ----------

Thank you for your answer, InstantAli3n (haha, I like the name). As I said, I am a new user here and new to many things (eventhough this is not the first time using Custom ROMs - I´ve been doing it for three years)... Somethings that are obvious to you, aren´t to me. I don´t know what "ubfuscation" is (!). I´ll find out and maybe will use it next time...

And I guess the problem you´re having with camera and audio is totally related to what I have. I hope it will be fixed!

I´ll put the letters that come on my "hastebin" links, so the developers can access the logs...

I did 3 tests (for comparison purposes, since the audio behavior changes when the earphone is connected or not during reboot).

Important Info (I guess...):

1 - My phone is Moto G XT1033 (falcon).

2 - My earphone is new and works well with other devices.

3 - Earphone audio works fine with Whatsapp audio and Youtube audio.

4 - I tested different music player apps and all have problem delivering audio to the earphone (the music app that comes with Resurrection Remix Rom, Pulsar, VLC, Stellio, Pi). The app I used to perform the bug test was Pulsar.

3 - I did a new clean install of the ROM for the bug test, to prevent inteferences from other apps.

4 - I kept Airplane Mode ON at all times, during the tests.

Test 1: Boot with earphone CONNECTED. Started music app with the earphone ON. The music was playing OK, and I interrupted the audio 3 times (stop for 5s, play again for 5s - for 3 times) to test if, at some point, earphone would stop working. The earphone had no problem playing the music.

Log: ewururecad.pl (on hastebin)

Test 2: Boot with earphone DISCONNECTED. Started music with earphone OFF. Inserted earphone after 10s of music. After the earphone was inserted, audio stopped, eventhough music continued to play (mute).

Log: huciriqugi.pl (on hastebin)

Test 3: I wanted to test continuous audio after rebooting with earphone CONNECTED (on the first test, I interrupted the audio 3 times...). Eventhough I rebooted phone with earphone ON, the music audio stopped millisseconds after I push play. (Again, the music continued to play, muted). Maybe will be interesting to see what was different from the first test - because the earphone was ON during reboot at both tests (the first test and this one).

Log: wawuxepide.pl (on hastebin)

There is one other bug I noticed. I didn´t make a log on this issue, but I thought it was worth mentioning now... The 3G/4G connection is very (very!) poor.

I´ll do the tests and post the logs on this one later...