[ROM][OFFICIAL][surnia] LineageOS 14.1 for Moto E LTE

squid2 · Dec 10, 2016 at 5:19 PM

This is our port of LineageOS 14.1 to the 2015 Moto E LTE (surnia). LineageOS is effectively a continuation of the CyanogenMod project. This ROM should run reliably, provided you are running a modem from 5.1 or newer.

Changelog:
CMXLog official nightly changelog

Downloads:
Official weekly builds
Lineage su addon

XDA:DevDB Information
LineageOS 14.1 for Moto E LTE, ROM for the Moto E 2015

Contributors
squid2, Alberto97, scritch007
Source Code: https://github.com/LineageOS

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x

Version Information
Status: Nightly

Created 2016-12-10
Last Updated 2017-01-26

Irfan_ · Dec 10, 2016

i'm on cm14.1-20161209 buid,there is a bug,when i receive a call data connection gets off and i cant't turn it on untill i restart my phone (surnia xt1521,operator jio 4g).

cango123 · Dec 10, 2016

Irfan_ said:
i'm on cm14.1-20161209 buid,there is a bug,when i receive a call data connection gets off and i cant't turn it on untill i restart my phone (surnia xt1521,operator jio 4g).

Grab a log - otherwise - it didn't happen
Devs are not wizards

Irfan_ · Dec 10, 2016 at 6:05 PM

where i can get the log

?

---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------

Zokhii said:
Grab a log - otherwise - it didn't happen
Devs are not wizards

where i can get the log?

SylvieL · Dec 10, 2016

I just updated from 13.0-20161122-NIGHTLY to 14.1-20161210-NIGHTLY on my Motorola Moto E 2015 LTE (surnia). Unfortunately, com.android.phone keeps crashing now, and I can't unlock my SIM card (it simply says "SIM PIN operation failed!").

There's a lot of logs, so it's hard to tell where the issue lies exactly, but this crash happens basically every second so it seems relevant:

Code:

12-10 19:15:14.869  4210  4210 E AndroidRuntime: FATAL EXCEPTION: main
12-10 19:15:14.869  4210  4210 E AndroidRuntime: Process: com.android.phone, PID: 4210
12-10 19:15:14.869  4210  4210 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) } in com.qualcomm.ims.vt.LowBatteryHandler$1
@17ba168
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1132)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:751)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:95)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:154)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6126)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
12-10 19:15:14.869  4210  4210 E AndroidRuntime: Caused by: java.lang.SecurityException: getImsPhoneId: Neither user 1001 nor current process has android.permission.READ_PHONE_STATE.
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.app.ContextImpl.enforce(ContextImpl.java:1585)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1617)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.content.ContextWrapper.enforceCallingOrSelfPermission(ContextWrapper.java:707)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at org.codeaurora.ims.QtiImsExt.onGetImsPhoneId(QtiImsExt.java:89)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at org.codeaurora.ims.QtiImsExtBase$QtiImsExtBinder.getImsPhoneId(QtiImsExtBase.java:97)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at org.codeaurora.ims.QtiImsExtManager.getImsPhoneId(QtiImsExtManager.java:167)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at org.codeaurora.ims.utils.QtiImsExtUtils.getImsPhoneId(QtiImsExtUtils.java:260)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at org.codeaurora.ims.utils.QtiImsExtUtils.getConfigForDefaultImsPhoneId(QtiImsExtUtils.java:229)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at org.codeaurora.ims.utils.QtiImsExtUtils.isCarrierConfigEnabled(QtiImsExtUtils.java:205)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at org.codeaurora.ims.utils.QtiImsExtUtils.allowVideoCallsInLowBattery(QtiImsExtUtils.java:216)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at com.qualcomm.ims.vt.LowBatteryHandler$1.onReceive(LowBatteryHandler.java:97)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1122)
12-10 19:15:14.869  4210  4210 E AndroidRuntime:        ... 7 more
12-10 19:15:14.875  1169  2142 W ActivityManager: Process com.android.phone has crashed too many times: killing!
12-10 19:15:14.923   278   278 I ServiceManager: service 'sip' died
12-10 19:15:14.923   278   278 I ServiceManager: service 'simphonebook' died
12-10 19:15:14.923   278   278 I ServiceManager: service 'iphonesubinfo' died
12-10 19:15:14.923   278   278 I ServiceManager: service 'isms' died
12-10 19:15:14.923   278   278 I ServiceManager: service 'phone' died
12-10 19:15:14.923   278   278 I ServiceManager: service 'carrier_config' died
12-10 19:15:14.923   278   278 I ServiceManager: service 'ims' died
12-10 19:15:14.923   278   278 I ServiceManager: service 'qti.ims.ext' died
12-10 19:15:14.923   278   278 I ServiceManager: service 'isub' died
12-10 19:15:14.923  4337  4452 I ActivityThread: Removing dead content provider:[email protected]
12-10 19:15:14.924  1169  1947 D ConnectivityService: unregisterNetworkFactory for PhoneSwitcherNetworkRequstListener
12-10 19:15:14.924  1169  1947 D ConnectivityService: unregisterNetworkFactory for TelephonyNetworkFactory[0]
12-10 19:15:14.926  1169  3094 I ActivityManager: Process com.android.phone (pid 4210) has died

mykenyc · Dec 10, 2016 at 6:30 PM

Irfan_ said:
where i can get the log?

---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------

where i can get the log?

Google how to make a logcat

enter.hk · Nov 6, 2015 124 16 0

Thanks for the thread....
Was waiting for it...

mykenyc · Dec 10, 2016 at 6:32 PM

SylvieL said:
I just updated from CyanogenMod 13.0-20161122-NIGHTLY to 14.1-20161210-NIGHTLY on my Motorola Moto E 2015 LTE (surnia). Unfortunately, com.android.phone keeps crashing new, and I can't unlock my SIM card (it simply says "SIM PIN operation failed!").

There's a lot of logs, so it's hard to tell where the issue lies exactly, but this crash happens basically every second so it seems relevant:

Did you do a clean install or direct update? It requires a clean install.

SylvieL · Sep 1, 2015 29 2 0

mykenyc said:
Did you do a clean install or direct update? It requires a clean install.

I did do a direct install because that's what CM Updater did. I'll try a factory reset.

mykenyc · Dec 10, 2016 at 6:36 PM

SylvieL said:
I did do a direct install because that's what CM Updater did. I'll try a factory reset.

I would suggest a clean install as in re-downloading open gapps and cyanogen.

SylvieL · Sep 1, 2015 29 2 0

mykenyc said:
I would suggest a clean install as in re-downloading open gapps and cyanogen.

I don't use Gapps so I guess a factory reset is the only thing left then.

Edit: Someone else tried this already and they seem to still be getting the crash.

Aniruddhagupte11 · Dec 10, 2016

Irfan_ said:
i'm on cm14.1-20161209 buid,there is a bug,when i receive a call data connection gets off and i cant't turn it on untill i restart my phone (surnia xt1521,operator jio 4g).

This is because VoLTE is not implemented completely yet.I am facing same problem with same rom on xt1521. So i am using aicp_surnia_n-12.1-NIGHTLY-20161208 version and it works fine and VoLTE is also working. or wait for new versions of CM14.1.

Badrikesh · Dec 10, 2016 at 7:30 PM

SD card problem

How to resolve this issue. Facing this issue everytime whenever I select sd card. Same thing happens in root access mode.

mykenyc · Dec 10, 2016 at 7:48 PM

Badrikesh said:
How to resolve this issue. Facing this issue everytime whenever I select sd card. Same thing happens in root access mode.

See if the issue persist using another file manager like amaze. Also check the permissions.

squid2 · Dec 10, 2016 at 10:24 PM

Issue switching to mobile data after being on WiFi

If mobile data fails to activate after you've been using WiFi for a while, please read this post on the osprey thread: http://forum.xda-developers.com/showpost.php?p=70027645&postcount=1672

AndersCF · Dec 10, 2016 at 10:26 PM

For some reason the Wifi is not working, even with a completely clean install. Also, Squid Kernel is not compatible for me? Battery also seems to drain quickly on this build. Clean experience otherwise though...

VenomMOD · Dec 10, 2016 at 10:32 PM

AndersCF said:
For some reason the Wifi is not working, even with a completely clean install. Also, Squid Kernel is not compatible for me? Battery also seems to drain quickly on this build. Clean experience otherwise though...

There's no squid kernel for Nougat yet. Try reflashing CM14.1 to see if WiFi starts working again. It works fine for me.

AndersCF · Dec 10, 2016 at 10:42 PM

VenomMOD said:
There's no squid kernel for Nougat yet. Try reflashing CM14.1 to see if WiFi starts working again. It works fine for me.

Tried flashing over the existing install and wipe flash/dalvik. It works now.

Sid32 · Feb 8, 2015 324 173 0

Anyone else having an issue with the cLock widget when you click on the weather the popup text is black?

josefojusti40 · Dec 11, 2016

Audio volume is very low

First my english is very bad but i'll try to say the most important

.

1. Thank you , your work with this room is amazing, now all the process is very smooth, now my moto e surnia is very fast ,im so glad for that reasons, the updates from the playstore now are faster , very!

THE BIG PROBLEM FOR ME

The volumen is very low , my friend has the same device with marshmallow official and the volumen is the same level if you compare with the official room android lollipop.

But the problem appears with this room (7.1) the volumen is no the same any more.

I got to compare the same device between moto e surnia marshmallow vs moto e surnia nougat (7.1) and the level volume from marshmallow is bether.

PLEASE FIX THIS PROBLEM BECAUSE A LOT OFS USERS LOVE SPOTIFY WITH A GOOD HEADPHONES BUT THIS PROBLEM ES VERY IMPORTANT FOR US.

About the moto radio, to be honest the best app to listen radio offline is from moto. and with this room is impossible to use the moto radio app , it says this app ( radio moto) is not compatible.

[ROM][OFFICIAL][surnia] LineageOS 14.1 for Moto E LTE

Recognized Developer

Senior Member

Senior Member

Senior Member

Member

Elite Member

Senior Member

Elite Member

Member

Elite Member

Member

Senior Member

Senior Member

Attachments

Elite Member

Recognized Developer

Member

Senior Member

Member

Senior Member

Member