FORUMS

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

1,722 posts
Thanks Meter: 11,080
 
By squid2, Recognized Developer on 10th December 2016, 05:19 PM
Post Reply Email Thread
LineageOS

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
The Following 49 Users Say Thank You to squid2 For This Useful Post: [ View ]
10th December 2016, 05:34 PM |#2  
Irfan_'s Avatar
Senior Member
Thanks Meter: 116
 
More
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).
The Following 2 Users Say Thank You to Irfan_ For This Useful Post: [ View ] Gift Irfan_ Ad-Free
10th December 2016, 05:46 PM |#3  
cango123's Avatar
Senior Member
Flag Karlsruhe
Thanks Meter: 216
 
More
Quote:
Originally Posted by Irfan_

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
The Following User Says Thank You to cango123 For This Useful Post: [ View ] Gift cango123 Ad-Free
10th December 2016, 06:05 PM |#4  
Irfan_'s Avatar
Senior Member
Thanks Meter: 116
 
More
where i can get the log?

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

Quote:
Originally Posted by Zokhii

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

where i can get the log?
10th December 2016, 06:30 PM |#5  
Junior Member
Thanks Meter: 2
 
More
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
10th December 2016, 06:30 PM |#6  
mykenyc's Avatar
Senior Member
Phoenix
Thanks Meter: 229
 
More
Quote:
Originally Posted by Irfan_

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
10th December 2016, 06:30 PM |#7  
Senior Member
Thanks Meter: 16
 
More
Thanks for the thread....
Was waiting for it...
The Following User Says Thank You to enter.hk For This Useful Post: [ View ] Gift enter.hk Ad-Free
10th December 2016, 06:32 PM |#8  
mykenyc's Avatar
Senior Member
Phoenix
Thanks Meter: 229
 
More
Quote:
Originally Posted by SylvieL

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.
10th December 2016, 06:34 PM |#9  
Junior Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by mykenyc

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.
10th December 2016, 06:36 PM |#10  
mykenyc's Avatar
Senior Member
Phoenix
Thanks Meter: 229
 
More
Quote:
Originally Posted by SylvieL

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.
The Following User Says Thank You to mykenyc For This Useful Post: [ View ] Gift mykenyc Ad-Free
10th December 2016, 06:38 PM |#11  
Junior Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by mykenyc

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.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes