yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] :
Im afraid i Can't agree with you, im running xposed v81 on 04/11, no issues at all, and was a dirty flash from squids unofficial 04/09 build.

Are you queuing the zips in TWRP when you flash?

Are you rebooting after flash ROM and gapps and booting back into CM13 to boot back into recovery to flash xposed? I ask that because several people have strange issues that are usually caused by flashing errors......

Please do not take that as a criticism but I just felt I would ask, I'm not perfect and make mistakes and for me, I'm having a few glitches with this 04/11 build, several apps are behaving quite strangely or taking forever to load, so this is not perfect for me either at this time!
[E 2015 Original Android Development] ijrr:
Succesfully installed this Cyanogenmod 13 in my Boot Mobile Moto E XT1526 with RingPlus service.

Steps:

- Unlocked bootloader: http://xdaforums.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748

- Installed TWRP bootloader from here: http://xdaforums.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649

- Set fsg-id to ringplus (when attempting to install CyanogenMod 13 it wil give you the command to do that, in an error message)

- Installed CyanogenMod 13.

Everything is working, including tethering.

Now I'd like to know how to switch network mode to GSM in case I want to use a GSM service abroad...
[E 2015 Original Android Development] tweak42:
I have a similar setup. Does your RingPlus plan have tethering included? Mine does not, and I'm definitely interested in trying CM13 if it can enable wifi tethering.
[E 2015 Original Android Development] ijrr:
No tethering on the plan, but able to tether using CM13.
[E 2015 Original Android Development] xtermmin:
On the stock ROM, the carrier can push a setting to disable tethering if you're not subscribed to it. CM13 does not do this, so tethering always works.
[E 2015 Original Android Development] nickpapagiorgio:
me too. i am on build 11/04. did i miss some setting to be set? i am also getting a lockscreen when an alarm goes off.
[E 2015 Original Android Development] EB20XY:
can confirm that. (lockscreen with incoming calls) :(
[E 2015 Original Android Development] js7701:
Updated to 11/4 in the meanwhile. Lockscreen issue still persists but can't reproduce it with an alarm.

Gesendet von meinem XT1524 mit Tapatalk
[E 2015 Original Android Development] vayavalla:
I'm on latest nightly and found that some apps don't connect correctly to internet while on wifi, but work well while on SIM data.

Attached a logcat, where I tried to make a sync with the Out of Milk app, while I was with the wifi ON, and didn't work, and then with the wifi OFF, and it worked.

The same app works without problems with the Wifi on my other devices.

Really great this ROM. Hope this can be fixed ;) All the rest seems great to me
[E 2015 Original Android Development] jacquelinexrose:
Brick or cm13?

originally, I had a rooted phone (MOTOE 2015 LTE) with ASOP OS. I had wiped my whole system, including the OS. I went on XDA website and followed directions to reinstall my OS using my TWRP recovery.

My current firmware is CyanogenMOD, with TWRP recovery

I installed the CM13 Nightly Version 4-10-16

I went into developer options and enabled root access. I used the root checker app, and root was properly working.

My phone was working great. better than ever and I decided to do an app and system back up in titatium backup.

The backup was 98% finished and I touched the screen. It froze and I held down the power button to reboot.

The phone never turned back on.

It reboots and gets stuck on the animation screen.

my animation is no longer cyanogenmod, but now the original android Motorola animation. does this mean my OS has been wiped again?

it will boot into the screen for the recovery option by holding down power and volume down. but when I hit recovery, TEAMWIN flashes but it wont boot into the actual recovery, and goes back into a restart back to the original animation screen. is my recovery deleted?

it wont factory reset from that screen either. it just goes back into a restart, back to the animation screen and no further. I tried to remotely wipe the phone, and it has to be connected to the internet, so that didn't work either.

my computer will not read my phone. ive tried 10 different cords.

my battery is unattachable so I let it die and restarted. same problem.

is this phone bricked?
[E 2015 Original Android Development] vayavalla:
Doesn't it connect in bootmode with the pc?

Enviado desde mi ifive_mini_3GS mediante Tapatalk
[E 2015 Original Android Development] jacquelinexrose:
it makes a connection sound but I don't see it showing up in devices. is there somewhere else to find it on the PC?

---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------

when I plug it in I noticed drive g and drive h appear, when I disconnect they disappear. when I click on either of them it says insert disk. I tried two different UBS's

that's all I can find going on
[E 2015 Original Android Development] vayavalla:
Did you install the drivers?

https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Enviado desde mi ifive_mini_3GS mediante Tapatalk
[E 2015 Original Android Development] jacquelinexrose:
okay, done.

says under "unspecified" --- "fastboot surnia s" with the icon above it

---------- Post added at 06:39 PM ---------- Previous post was at 06:32 PM ----------

when i click it, it says

model: fastboot surnia s

and everything else is unknown

--- when i click over to hardware it says this:

Name: motorola ADB Interface

Type: Android Device

device function summary:

manufacturer: motorolla

location: port_#0003.hub_#0003

device status: this device is working properly

---------- Post added at 06:45 PM ---------- Previous post was at 06:39 PM ----------

motorolla adb interface

EVENTS:

4-12 device configured (input.inf)

4-12 device started (hid usb)

4-12 device configured (null)

4-12 device deleted

4-12 device install requested

4-12 device configured (oem54.inf)

4-12 device started (winusb)

does this help?

---------- Post added at 06:47 PM ---------- Previous post was at 06:45 PM ----------

4-12 device installed (motoandroid2.inf)

---------- Post added at 07:40 PM ---------- Previous post was at 06:47 PM ----------

on my bootscreen it says status code 3. does this effect anything?

im so confused, i just need this phone to work

thank you

---------- Post added at 07:47 PM ---------- Previous post was at 07:40 PM ----------

the fastboot shows up within the motorolla device manager, but still no folders or reading on my pc devices
[E 2015 Original Android Development] :
Just want to point out that i don't have a lock screen appearing during incoming calls, or have I ever experienced this issue.

Please note this screen shot just taken of my moto e 2015 alerting me to a call from my moto e 1st gen (my work phone)

I'm on build 11/04.
[E 2015 Original Android Development] :
And just to prove no fluke, I switched off and locked the screen, and still don't get a lock screen displayed for incoming calls.
[E 2015 Original Android Development] vayavalla:
Do you have a security pattern set up? I think this only happens when you have it set to unlock your device

Enviado desde mi XT1524 mediante Tapatalk

---------- Post added at 10:17 PM ---------- Previous post was at 10:12 PM ----------

In fastboot mode you don't see any folder on Windows.

Easiest way, if you need the phone is to install an official firmware

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

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] :
I do not use an unlock pattern, so this is why I don't see the error everyone is commenting about?
[E 2015 Original Android Development] jacquelinexrose:
" How do I install firmware without recovery working and no twrp folder on my desktop
[E 2015 Original Android Development] :
Fastboot/adb
[E 2015 Original Android Development] _dud3:
I got the same issue with lock screen as mentioned above since last nightlies. Furthermore after swiping over the telephone icon on lock screen it takes at least five seconds to open the dialer with overlayed PIN pad. But that pad looks quite unusual to me (see attachment). Its in addition a little tricky to unlock as I need to click the top right corner of the accept button or else an information about how to unlock comes up in the background. Same issue when clicking on a notification on the lock screen.

My device: XT1524 Surnia, clean installed CM 13 Nightly from April 12th, 2016, after complete device reset/wipe.
[E 2015 Original Android Development] EB20XY:
So, as I understand the issue can be comfirmed.

Is it possible, that the incall-issue will be fixed in next nightly by these commits ?

http://review.cyanogenmod.org/#/c/140395/

http://review.cyanogenmod.org/#/c/140395/
[E 2015 Original Android Development] soyab0007:
will this mod work with Moto E Verizon 4g LTE?
[E 2015 Original Android Development] vayavalla:
See this post

http://xdaforums.com/moto-e-2015/general/guide-restore-moto-e-2015-stock-firmware-t3044936
[E 2015 Original Android Development] xtermmin:
No. The Verizon model cannot be bootloader unlocked.
[E 2015 Original Android Development] :
I'm puzzled.

Since I had a problem with the 05/04 build, returning to stock then returning to CM13 with squids 09/04 unofficial build, my Moto E just has not behaved itself.

Strange app behaviour, apps suddenly freezing, all sorts of problems with browser and chrome displaying blank screens. Facebook a waste of time, Facebook messenger playing all sorts of games with me.

Keyboard freezing, sound quality from front speaker is absurd, I can't even hear my phone ring now.

Lots of lag, tried various launchers, took apps off and even tried clean master.

I'm now pretty sure whatever happened last week was hardware related, I'm still on 11/04 build as my system says there's no available update at this time.

I'm pretty concerned but I'm also trying other ROMs to see if I have these problems, and so far, I'm having the exact same problems in the latest resurrection remix as i have with CM13.

I'm hoping this isn't a problem that going to mean my moto e has had it, it is only 3 months old, my other moto e (a 1st gen) is now 8 months old, running CM13 and going strong.....

Lots of testing to come, so bear with me I'll try and work out what on earth is wrong with my poor E2.

Edit

Have clean installed CM13 and Resurrection remix, no extras, just the squid kernel and gapps.

No apps installed either attempt and CM13 is completely stable, but several sudden reboots.

Clean flashed reduction remix and had several reboots during set up.

Reflashed CM13 and again, several sudden reboots after initial set up, no apps installed, just the Google apps updating, and two sudden reboots while I'm watching TV and not using the phone.
[E 2015 Original Android Development] ayush rao:
Have u wiped the system and flashed. Once I had somewhat the same issue, I solved it by just formatting the system along with the others and then flashing the ROM
[E 2015 Original Android Development] :
Yes.

Second attempt was always after formatting system/data/ect then flashing.

Seems OK right now but still having random reboots.

No apps installed.
[E 2015 Original Android Development] vayavalla:
Do you have the modem updated?

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] :
Yeah. I have the stock 6.0 modem installed
[E 2015 Original Android Development] Chuecko:
Problem with Audio FX

Hello guys. At first, sorry for my english... I have one question, about Audio FX on my Moto E with CM13. When I upgrade system, in changelogs, I see something about Audio FX, but I don't have Audio FX on my phone. Why? On CM12 Audio FX worked perfectly, and now, I don't have any equaliser :(. Thanks for help. Best regards!
[E 2015 Original Android Development] :
Audio effects was removed from this build of CM13 some builds ago. Try viper, (v4a) I use that .

Kind regards.
[E 2015 Original Android Development] Chuecko:
Thanks for fast reply. Why was removed? I tried use v4a but doesn't work -I don't see any difference in sound headphones when I used v4a. But, maybe I use bad version of viper?

is there any difference which version I use?
[E 2015 Original Android Development] nguyenquangduc2000:
I can not play anysong with format .flac. I think u should fix it
[E 2015 Original Android Development] :
I use v4a also. No issues, working fine.

---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------

A head up from squid on his squid kernel forum that some users are report file system corruption due to the Linux 4.5 f2f update, a new r16f kernel is released.

Goes a long way to explaining all my problems!
[E 2015 Original Android Development] :
A post from squid on the squid kernel

There have been reports of filesystem corruption involving the new Linux 4.6 f2fs version used in the r16d and r16e releases. This problematic f2fs version was also used in CyanogenMod 13 nightlies on April 9, 10, and 11. If you previously installed the r16d or r16e kernel, or previously installed the April 9, 10, or 11 nightlies, I would advise backing up valuable files to a non-f2fs storage volume before upgrading to this kernel version. There may be a risk of data loss when downgrading the f2fs, but it only affects some users.

This release brings back the older (Linux 4.5) f2fs. This is the same f2fs that was used from r15 to r16b. This release also brings updates to the zRAM driver.

Please accept my sincerest apologies for any data loss that may have occurred. Greater caution will be exercised before any future f2fs updates are attempted in CyanogenMod or this kernel.
[E 2015 Original Android Development] kesavvel:
Dear cm 13 devs ! Please try to Build Snapshot for 5.1.1 cm 12.1 ! we Love it a lot !!!
[E 2015 Original Android Development] EB20XY:
Had someone tested nightly from 12.4. ?

Is the incall-issue still present with the lockscreen coming up ? :confused:
[E 2015 Original Android Development] _dud3:
I did and posted the following as you might remember: ;)

There was no new nightly released yesterday. The announced changes for the upcoming release are still growing: h*t*t*p*s://w*w*w.cmxlog.c*o*m/13/surnia/ (sorry, can't post links yet) Hope it will be available tonight. :o

EDIT: Announcements still growing and growing. Guess and hope these two changes will fix lock screen issues:

h*t*t*p://review.cyanogenmod.o*r*g/#/c/140368/

h*t*t*p://review.cyanogenmod.o*r*g/#/c/140379/

Btw. any chance to see quick unlock and navigation ring customization like in CM 12.1 back in CM 13?
[E 2015 Original Android Development] Kimaly:
CM13 nightly for Moto E 2015 LTE

Nightly releases of CM13 for Moto E 2015 LTE XT1525 are buggy, and destabilise the system. Stick with CM13 from April 10, 2016, until they repair issues.

CM13 bluetooth headphones are not allowed to control default audio player, instead, they are working with some third party applications, like VLC for example.

I'm makeing a system backup, and wait for a stable CM13 release. CM13 for XT1524 is, for the moment a mess. To many restrictions, issues and bugs. Hopefully they will repair all this soon, and give us something stable and reliable like CM12.1 was and is.
[E 2015 Original Android Development] vayavalla:
buggy? I'm using latest nightly without noticeable bugs (Just the one with wifi connection that I reported earlier)

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] :
Yes, its buggy.

Very buggy.

If you are not having any problems, good for you, but don't question anyone who is doing us all a favour and reporting these things.

I, like you have an XT1524 and have not been able to use CM13 as my daily driver since the 05/04 build, I'm facing sudden and random reboots, keypad freezing, loss of speaker volume, severe lag and other strange behaviour.

I agree with people that things are not quite right with CM13 at the moment, but that's the beauty of nightly releases, one fix can break something else.......

I'm not flashing every single nightly release as I'm just trying to find a stable build to continue to use CM13 as my daily driver.

As it is its now took me four attempts to type this post because my moto e rebooted for no reason twice and the XDA app crashed/forced closed on me on my third attempt, something that's not happened before, so anyone who says these latest nightlies are buggy I would have to agree with them, however much I hate to do so.
[E 2015 Original Android Development] vayavalla:
I know that it can work good for me, and bad for others, but only saying that it's buggy doesn't help.

When something didn't work, it should be explained as accurately as possible, and, if possible, with logcat or last_kmsg. More info people gives, more likely the problem to be solved [emoji6]

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] :
I agree.

Logcats posted, problems reported, and share my problems with all here.

I've ruled out any flashing errors on my part, I've tried flashing without squid kernel, with squid kernel, with gapps, without gapps and not flashing xposed at the moment.

Yes this is a trial, there was no nightly last night and I'm on 12/04 just like you, for me, its just too many errors, I have removed what apps i had installed and that makes no difference.

I'm now flashing squids test build from a few days ago to see if that makes a difference.

Regards
[E 2015 Original Android Development] vayavalla:
Regarding your problem: how did you exactly install the ROM?

Wiped everything? Then flash ROM, GAPPS and reboot?

And there you have the problems?

Did you check that the files were correctly downloaded?

Which GAPPS you used?

Do you have your sd card as internal? .........

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] :
Up until 05/04 nightly, I was dirty flashing each update, with a wipe of dalvik/cache before rebooting, but that build is where my problems started.

After several reboots, it hung on the initial Motorola splash screen and refused to move into booting up.

Whatever I did, i could not cure this and ended up flashing the EU retail 6.0 stock ROM.

After a few days, that became so laggy it was unusable for a daily driver, so I reflashed the test build of CM13 squid posted on 09/04.

That was OK, but then I upgraded to 10/04 and had so many issues I moved back to the test build.

But 11/04 and 12/04 have displayed lots of random reboots, even when the phone is just sitting on the table.

Making a call the first attempt is always dropped but works on the second attempt.

The 11/04 and 12/04 were clean installs with full wipe of system, data and cache, queuing zips in twrp so I flash the rom, squid kernel then gapps, wipe dalvik/cache then reboot, as I have since that test build.

I assumed my dirty flashing had caused these issues but have been assured by many users its fine, but I don't dirty flash now and perform full wipes before flashing, once up and running I go to my SD card and reinstall all my apps (saved as apk files using apk extractor)

I used open gapps 08/04 nano or A gapps pico, both of these packages have never caused me any problems.

The speed, snappiness and general fluidity of earlier builds has gone, I'm left with a stuttery laggy and unstable system I can't trust or rely on at the moment.

I have a 1st gen moto e running cm13 that I use as a work phone and has been promoted to my daily driver until I can sort these issues out with my E2
[E 2015 Original Android Development] Kimaly:
I have TWRP 3.0.2, a custom logo.bin, to avoid unlocked bootloader message, gpt.bin from Motorola's Marhmalllow release for XT1524, and OpenGAPPS. I have installed CM13 and OpenGAPPS at the same time, on a clean system. After that I performed regular updates, as they apperared. I had no issues until April 12 update.

The bluetooth problem persit from the first CM13 official release for Surnia. Since then, I use VLC.

TWRP full access issue appeared after update from April 11, 2016. TWRP can not perform update correctly because of that. TWRP can not wipe partitions or update system, becasue the partitions are busy, can not be unmounted or access is prohibited.

I suspect that some restrictions to partitions access where implemented in April 10, nightly update, and thus, future updates can not be performed correctly by TWRP, resulting in a unstable system.

After the last update Google Play Store was removed from system, an I can not restore it.

I was forced to restore from ADB original firmware 5.1.1 from Motorola, and after that TWRP access to all operations was regain, and I could restore a CM13 backup made prior to April 11, nightly release, and everything is working well, except bluetooth issue.

-----------------------------

Last night, I've downgraded TWRP, from 3.0.2, to 3.0.1 and seems that solved TWRP access to partitions from recovery and update issues.

Unsolved is bluetooth headphones access to default audio player. - Still using VLC.

Access to storage and external SD card. That is an annoing behaviour of Marshmallw and CM13. Every time you need to access ypour storage from Linux or Windows, you must go in Setting - Developer - and set MTP istead charging as default. I think this could be solved in CM13 builds, by forcing MTP as default.
[E 2015 Original Android Development] mrxtc89117:
Is the CM 13 from 04/08 the most stable so far? I have CM 13 from 04/08, opengapps pico, squid kernel r16f and xposed v81. Twrp 3.0.2-r1. I have the xt1526 and queue the flash in this order.
[E 2015 Original Android Development] vayavalla:
Which recovery you use? Why don't you use latest GAPPS?

Why don't you try without these apk you have saved? Maybe one pig them is causing problems

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] :
Latest gapps give me google play / and google play services errors at set up, I've found the 08/04 package (for me) the most stable, but then someone said here for them it won't work!!!!

Recovery is TWRP 3.0.2-r1, an upgrade from 3.4.5-r2

If you read some of my previous post you will see I'm experiencing these issues with no apps installed, and I'm not flashing any custom boot animation or xposed

I reflashed the 12/04 nightly last night and I performed a "double" wipe, I wiped data, system, internal storage, rebooted TWRP and then performed another wipe of data, system and internal storage, then flashed 12/04 nightly, squid kernel r16f and open gapps nano 08/04 and since 10pm last night, I've not had any reboots, no noticeable lag, all I'm noticing as I scroll up or down the screens, the movement is not fluid and seems to hang in places, selecting my home WiFi works great (I have the 6.0 modem) and I still have the call dropping problem, but its a great improvement over the installs I performed earlier.

Edit

8am now and have installed nova launcher with no issues, and still no reboots

Incoming call alert/ringtones seem very quiet, even at full volume.
[E 2015 Original Android Development] ayush rao:
In my opinion that's the most stable build till date
[E 2015 Original Android Development] vayavalla:
Is your TWRP the one from squid?

http://xdaforums.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649