[ROM][Official][Weekly] LineageOS 14.1 for OnePlus 3/3T

Search This thread
By:
Advanced…
S

sonst-was

Member
Aug 16, 2015
16
2
Hi everyone,

since end of December I have a problem with my OP3 with Lineage OS 14.1. From time to time the phone eats the battery away like fresh pancakes. I noticed it the first time in the last week of december (with the nightly from December 1st or 29th). Since then I had the issue from time to time with all nightlies since then (I installed the one from January 5th, 19th and 26th).

The battery screen shows that "Android-System" and "Android OS" (or "Lineage OS") is using most of the battery, but I'm unable to see the real problem. I also tried to find the issue with Wakelock Detector but other than that my phone hasn't been in sleep the whole day I was unable to find any clues.

I've uploaded a few screenshots of the battery info of Android and Wakelock Detector here: https://imgur.com/a/bQeZE

Does anyone has the same issue or does anyone knows what I could try?

Greeting
sonst-was
 
  • Like
Reactions: Deleted member 4405529
ageback

ageback

Senior Member
Dec 3, 2011
177
41
Wuxi City
OnePlus 7
OnePlus 11R (Ace 2)
Hi @dianlujitao dear dev, I'm from China. First I want to thank you for your work on this ROM. Now I have a problem, hope you can help me.
I have two SIM cards. One is China Telecom and the other is China Mobile. When I use them together in my Oneplus 3T, then the China Telecom sim has no network signal, no matter it's in which sim card slot. If I use China Telecom sim card alone, it has network but I can use only 3G not 4G(LTE). Can you please fix the China Telecom issues?
Now I have to flash OOS to use the 2 SIM cards together without issues.
 
dianlujitao

dianlujitao

Senior Member
Jan 27, 2013
771
4,921
Xi'an
yuko.moe
ageback said:
Hi @dianlujitao dear dev, I'm from China. First I want to thank you for your work on this ROM. Now I have a problem, hope you can help me.
I have two SIM cards. One is China Telecom and the other is China Mobile. When I use them together in my Oneplus 3T, then the China Telecom sim has no network signal, no matter it's in which sim card slot. If I use China Telecom sim card alone, it has network but I can use only 3G not 4G(LTE). Can you please fix the China Telecom issues?
Now I have to flash OOS to use the 2 SIM cards together without issues.
Click to expand...
Click to collapse

You can manually set CMCC sim slot network mode to any non-CDMA ones, then CT sim should work.
 
D

Deleted member 4405529

Guest
sonst-was said:
Hi everyone,

since end of December I have a problem with my OP3 with Lineage OS 14.1. From time to time the phone eats the battery away like fresh pancakes. I noticed it the first time in the last week of december (with the nightly from December 1st or 29th). Since then I had the issue from time to time with all nightlies since then (I installed the one from January 5th, 19th and 26th).

The battery screen shows that "Android-System" and "Android OS" (or "Lineage OS") is using most of the battery, but I'm unable to see the real problem. I also tried to find the issue with Wakelock Detector but other than that my phone hasn't been in sleep the whole day I was unable to find any clues.

I've uploaded a few screenshots of the battery info of Android and Wakelock Detector here: https://imgur.com/a/bQeZE

Does anyone has the same issue or does anyone knows what I could try?

Greeting
sonst-was
Click to expand...
Click to collapse

I'm observing kernel wakelocks (mainly NETLINK, timerfd and qcom_rx_wake) increasing Screen Off Awake from formerly 2-4 % to 9% and increasing screen off bat drain from <0.5%/h to >1.3%. (For wifi always on.)

I also observed WhatsApp complaining about "waiting for internet connection" on its backups. This happens as well with "wlan always on", as with "only if connected. Mobile data is enabled, anyway. I have to toggle wifi, to continue the backup.

I highly doubt it's device tree or kernel related, because I expirienced something very similar on my chagallwifi (since this is a wifi only exynos powered device, I belive we can reasonable exclude kernel- or device tree changes): wlan_rx_wake keeps the device awake with screen off and increases idle drain from formerly 0.1% to 1%...

After checking lineage (non-kernel and non-device-tree) commits, I'm quite clueless because I havn't found anything that seems related to me. I'm not even sure if it's rom related at all, on the other hand: how can an app trigger that massive amount of kernel wake locks? Could this be caused by some app update?(BTW: I uninstalled k9 to exclude, and it can't be whatsapp, because it's not installed on chagallwifi.)

I also belive, we both are not the only ones suffering from this, because some custom kernels (like boeffla) have implemented a kernel wakelock blocker with NETLINK, timerfd and qcom_rx_wake blocked all together - why should @Lord Boeffla write a dedicated wl blocker, if those wls arn't commonly expirienced?

The question is: what the heck is triggering these?

Meanwhile I found, if I set wifi to "only if connected" the screen off drain is down to 0.6-0.8 again. I havn't tested a wl-blocker enabled kernel, because (like my suggestion with wifi settings) this is only a workaround for the symptoms, but I want to get down to the cause.
 
D

Deleted member 4405529

Guest
sonst-was said:
Interestingly I did experience this issue a few times over night where I have WiFi and mobile data disabled. I will change the WiFi setting as you suggested in the mean time and see if anything changes.
Click to expand...
Click to collapse

As stated above: this is no real solution and the drain does NOT went down to the former values.

To realy solve this, we need to know, what exactly is triggering the kernel wakelocks.
 
9Lukas5

9Lukas5

Senior Member
Dec 14, 2010
3,914
2,076
near Stuttgart
Hey guys, if I enter the about phone menu from dialer with code '*#*#4636#*#*', under the three dot menu, IMS state it says IMS not registered.

Also if I'm going to the dialer settings->call accounts->my simcard->IMS-settings com.android.phone fc's and my signal goes a way a few seconds.

Is there something with LOS and IMS service not working, or should that work fine and I have to figure out whats going on here?
L

Edit: Attached a logcat with filter for Warnings and worse
The trouble is starting with a NoSuchMethodError:

Code: 
02-04 14:57:01.339  3972  3972 E AndroidRuntime: FATAL EXCEPTION: main
02-04 14:57:01.339  3972  3972 E AndroidRuntime: Process: com.android.phone, PID: 3972
02-04 14:57:01.339  3972  3972 E AndroidRuntime: java.lang.NoSuchMethodError: No static method shallTransmitStaticImage(Landroid/content/Context;)Z in class Lorg/codeaurora/ims/utils/QtiImsExtUtils; or its super classes (declaration of 'org.codeaurora.ims.utils.QtiImsExtUtils' appears in /system/framework/telephony-common.jar)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at com.qualcomm.qti.ims.ImsSettings.displayStaticImageOptions(ImsSettings.java:202)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at com.qualcomm.qti.ims.ImsSettings.onResume(ImsSettings.java:87)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1270)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.app.Activity.performResume(Activity.java:6788)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3431)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3494)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2757)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.app.ActivityThread.-wrap12(ActivityThread.java)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1496)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:154)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6186)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
02-04 14:57:01.339  3972  3972 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)

Sent from my OnePlus3 using XDA Labs
 

Attachments

  • logcat.txt
    62.5 KB · Views: 1
Last edited:
M

mk_1996

Senior Member
Jun 26, 2016
880
564
Delhi
9Lukas5 said:
Hey guys, if I enter the about phone menu from dialer with code '*#*#4636#*#*', under the three dot menu, IMS state it says IMS not registered.

Also if I'm going to the dialer settings->call accounts->my simcard->IMS-settings com.android.phone fc's and my signal goes a way a few seconds.

Is there something with LOS and IMS service not working, or should that work fine and I have to figure out whats going on here?
L
Click to expand...
Click to collapse
If you've been dirty flashing all along,i think its time to clean flash. Maybe installing the latest nougat firmware could solve the issue.
 
  • Like
Reactions: 9Lukas5
9Lukas5

9Lukas5

Senior Member
Dec 14, 2010
3,914
2,076
near Stuttgart
mk_1996 said:
If you've been dirty flashing all along,i think its time to clean flash. Maybe installing the latest nougat firmware could solve the issue.
Click to expand...
Click to collapse

Yeah, could be time by now^^ I'm consider waiting for the official nightlies of Oreo to make a clean flash, as the ims settings is a thing, I don't need to touch on a daily base ?

L

Sent from my OnePlus3 using XDA Labs
 
Last edited:
  • Like
Reactions: mk_1996
D

drmcatchr

Senior Member
May 9, 2014
88
38
Head's up guys, trying to dirty flash the latest lineage-14.1-20180209-nightly ended up in TWRP getting stuck at patching system image unconditionally. Thankfully was able to restore, do make a backup before you flash this one. Also there is a privacy error, while trying to download from the server.

Screenshot_from_2018-02-12_00_04_56.png
 
G

gcsuri

Senior Member
Mar 23, 2007
82
9
drmcatchr said:
Head's up guys, trying to dirty flash the latest lineage-14.1-20180209-nightly ended up in TWRP getting stuck at patching system image unconditionally. Thankfully was able to restore, do make a backup before you flash this one. Also there is a privacy error, while trying to download from the server.

Screenshot_from_2018-02-12_00_04_56.png
Click to expand...
Click to collapse

Hi, check your system date and time.
 
D

devnerd

Senior Member
Oct 14, 2014
160
134
Yes that could be the issue.
Dirty flashed it on two phones since Friday and had no issues at all so far. I flashed it through the official TWRP 3.2.1-0 via sideload
 
You must log in or register to reply here.

Similar threads

A
[ROM][Pie][OFFICIAL]Resurrection Remix v7.0.2 [unified 3/3t]
Replies
17K
Views
2M
Y
YechiamTK
dianlujitao
[ROM][Official][Nightly] LineageOS 15.1 for OnePlus 3/3T
Replies
4K
Views
531K
D
dlogictech
Sultanxda
[OP3+3T][ROM+KERNEL] Unofficial LineageOS 14.1 with custom kernel [January 09, 2020]
Replies
5K
Views
737K
M
mnsiw
NevaX1
  • Poll
[EOL][ROM][3&3T][AROMA] FreedomOS 3.3 [8.0][OOS][5.0.1][STABLE][SAFETYNET &#10003;]
Replies
10K
Views
1M
L
lapirado
dianlujitao
[ROM][Official][Nightly] LineageOS 16.0 for OnePlus 3/3T
Replies
4K
Views
417K
G
getzze

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 254
    dianlujitao
    dianlujitao
    LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.​
    Code: 
    #include <std_disclaimer.h>

/*
 * Your warranty is now void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */
    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.

    Important information:
    This thread is for official LineageOS 14.1 builds for OnePlus 3/3T. The following will not be supported here:
    • Custom kernels
    • Mods
    • Xposed

    We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
    • Flashed a custom kernel
    • Installed or did mods from untrusted sources
    • Modified system files

    Known bugs:
    • Front camera is buggy, due to the buggy camera HAL Fixed by OnePlus

    Installation:
    First time flashing LineageOS 14.1 on your device, or coming from another ROM?
    1. Download the zip(s)
    2. Install a compatible Recovery (See #2 for details)
    3. Perform a nandroid backup of your current ROM (Optional)
    4. Wipe data/factory reset
    5. Flash LineageOS
    6. Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
    7. Reboot

    Source code:

    Credits:
    • LineageOS Team & Contributors
    • Code Aurora Forum
    • ......

    Download:

    XDA:DevDB Information
    LineageOS, ROM for the OnePlus 3

    Contributors
    dianlujitao, Grarak
    Source Code: https://github.com/lineageos

    ROM OS Version: 7.x Nougat

    Version Information
    Status: Nightly

    Created 2016-11-09
    Last Updated 2017-03-27
    View
    127
    dianlujitao
    dianlujitao
    Release note:
    • New builds (after 2017/1/15) uses F2FS backported from 4.10 kernel, you may meet compatibility problems such as deadlocks, if you do, flash TWRP provided in OP and choose "Wipe -> Format Data" to format(not just wipe) your /data partition, this will clean the entire /data partition, including the emulated sdcard, so don't forget to backup your data before. After that, your data partition will be formatted into ext4, if you want to keep using f2fs, just convert fs type normally in TWRP.
      [*]For oneplus3, my unofficial TWRP is recommended, as it's what I use. For 3T, TWRP 3.0.4 is recommended.
    • As of 2017/6/17, official TWRP for OnePlus 3(https://dl.twrp.me/oneplus3/) is updated with latest LineageOS kernel and OxygenOS decryption stuff, it builds against Omni 7.1.2 and supports both op3&3t, now it's the recommended recovery.
    • 20170120 build includes sdcardfs, security fixes and camera fixes&improvements, touch to focus is fixed as well, if it's still not working, clean Snap's data. BTW N kernel source is released now, I'll take days to bring up, don't ask for ETA.
    • Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution. Visit http://lineageos.org/Update-and-Build-Prep/for more details
    • Started from lineage-14.1-20170207-nightly-oneplus3-signed.zip, we provide unified builds for both 3&3T, and you need to install certain firmware to pass the TrustZone assertion. Currently they're the OxygenOS Open Beta 19/11 ones. As oneplus won't update them every time new OTAs are rolling out, firmware from other versions might also pass the assertion.

    FAQs:
    My status bar quick pulldown and notification slider are broken, why?
    See https://github.com/opengapps/opengapps/wiki/Notes-for-CMSetupWizard

    Why the builds are unified?
    Tell me the difference between OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883 and OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8, why not?
    c3vAIRA.png
    View
    65
    nadejo
    nadejo
    Latest Firmware files for oneplus3/oneplus3t -5.7.2017-
    Make a nandroid backup before you proceed
    Flash the following files using the latest official twrp to avoid any recovery related issues.
    Make sure to do a clean flash if your rom requires an updated firmware.
    Don't ever flash an oneplus3 firmware on oneplus3t or an oneplus3t firmware on oneplus3.

    Oneplus3
    Instructions only for oneplus3!
    1-clean flash is recommended.
    2-Falsh OnePlus3_OpenBeta19-FIRMWARE+MODEM-flashable.zip.
    3-Flash the latest laos nightly.
    4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.
    5-Wipe Dalvik/cache and reboot.

    Oneplus3t
    Instructions only for oneplus3t!
    1-clean flash is recommended.
    2-Flash OnePlus3T_Beta10-(4-7-17)-FIRMWARE-flashable.zip.
    3-Flash the latest laos nightly
    4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.
    5-Wipe Dalvik/cache and reboot.

    For people who rather use the oxygenos camera:
    Get OnePlusCameraV8-siankatabg.apk and OnePlusGallery-V8-siankatabg.apk

    If you have problems after flashing any custom kernels please provide a log in the thread where you got the kernel from and not here!

    Credits:
    @nvertigo67 @djsubterrain @Eliminater @kamilmirza op3t firmware
    @jamal2367 op3 firmware
    @siankatabg oos camera/gallery port
    View
    52
    dianlujitao
    dianlujitao
    Almost all former CM developers are involved in LAOS, including Steve and some kind guys who still work for cyngn, so don't worry.
    btw I won't rebrand the thread until LAOS is a thing
    View
    51
    dianlujitao
    dianlujitao
    Today I switched the kernel to the LA.UM based one, and merged patches for op3t support.
    It means, the NEXT weekly will be a unified build for both op3 and op3t.
    As we're not shipping radio images now, you may need to install the latest OOS radio images to pass the TZ assertion.
    View

New posts