[ROM][OFFICIAL][7.1.2][kate/kenzo] LineageOS 14.1

Search This thread
By:
Advanced…
G

GuestK00171

Guest
gitsdb said:
I have tried dozens of custom ROMs... All have bugs.. Even best of os have bugs.. But this ROM has least number of bugs.. That's my experience.. You can try all custom ROMs.. But when you want stability and battery life you will come back to lineage os.. It's that simple..:)
Click to expand...
Click to collapse

Yes..here on LOS14.1 you have no show-stoppers, no major bugs like in all Oreo-ROMs. With 14.1 my Kate works perfect...I see no reason to switch to Oreo...not one!
 
D

dskopa

New member
Apr 19, 2018
4
2
I have the kenzo version. I must do the same steps? The problem needs a clean install of Latest firmware?
 
C

corkiejp

Senior Member
Sep 27, 2012
2,045
917
Cork
www.boards.ie
pudup said:
Except this ROM has horrible battery life with it's "Phone Idle" bug ';..;'
Click to expand...
Click to collapse

pudup said:
Doesn't the stock kernel have the shutdown bug? My issue isn't gps related. Switching everything off doesn't change anything. "Phone Idle" is constantly running and drains almost as much as the screen. I'm not the only one with this issue.
Click to expand...
Click to collapse


If your phone is draining while screen off ("Phone Idle" ), I would have a look at what apps your running and see if any apps are keeping the device awake. Use Wakelock Detector [Root] for example, if your not rooted check the video description to run the app without root.
 
C

corkiejp

Senior Member
Sep 27, 2012
2,045
917
Cork
www.boards.ie
pudup said:
I get 0% drain while screen is off over night. It happens while I'm using the phone. It's a bug. There's nothing running.
Click to expand...
Click to collapse

I should have said installed apps. Apps can still run in the background, so it could be still some misbehaving app.

My "Phone Idle" is currently reporting 9h 26m and power used 190mAh. Taken off charge 10 hours.

Latest Rom 20180420, Franco Kernel #16.

What is your device reporting as battery use while Idle?
 
C

corkiejp

Senior Member
Sep 27, 2012
2,045
917
Cork
www.boards.ie
pudup said:
The "Phone idle" in the battery report screen does most of its damage I'm actually using the phone. It's currently sitting at 5 hours 125mah. Before this bug came about, phone idle would sometimes not even show up in the battery report and if it did it would be at the bottom. Now it is always 2nd place behind screen on time.

Btw what is your average SOT?
Click to expand...
Click to collapse

SOT is so relative to usage patterns. I average about five and half to six hours.

But I use the phone allot while playing games while on data (Kenzo lacking band 20).
Plus also use the phone screen off, downloading over VPN, copying files to PC over wifi, Bluetooth streaming of music etc.

Still getting a days use out of it with approx 40 to 50% battery remaining. So the idle time doesn't really concern me.

Have you tried turning of location scanning? I just checked mine and they where on.

Also, if you haven't yet, go into location settings, tap the three dots menu button to go into scanning options and turn those off.
Click to expand...
Click to collapse
 
marchelius

marchelius

Senior Member
Jun 13, 2008
93
21
3-CITY
I have installed last official version (20180420) on my RN3P Kenzo. Everything is working fine, no low battery bug, no battery drain, SOT is like on MIUI. And the best is, I have over 95k points in Antutu :) (in MIUI Global Stable was about 89k).
 
Last edited:
P

Priix

Member
Jan 27, 2018
44
6
marchelius said:
I have installed last official version (20180420) on my RN3P Kenzo. Everything is working fine, no low battery bug, no battery drain, SOT is like on MIUI. And the best is, I have over 95k points in Antutu :) (in MIUI Global Stable was about 89k).
Click to expand...
Click to collapse

So , now the phone doesn't shut off when the battery's at 15 ℅ ?
 
onliner

onliner

Senior Member
Oct 29, 2016
2,422
1,031
Lecterr said:
This is no bug...its the result of a softbriked phone...flash latest official developer MIUI per EDL and only use a official unlocked bootloader.
Click to expand...
Click to collapse

No lol, It's because of this, without that commit, devices with degraded batteries are more likely to have that problem because the battery voltages have higher fluctuations.
 
S

sampit76

Senior Member
Mar 16, 2011
109
26
Priix said:
Yep .
Thanks guys the problem doesn't exist now . Using lineage os micro G 20180420 btw .
Click to expand...
Click to collapse

Greeting mate,

Do you meant The Low Battery Shutdown bugs is gone now? (Usually around 15% + when using Camera Apps)
Did You previously experience that bug?

Because from latest Lineage BUGBASH , the problem status still = Unresolve

https://jira.lineageos.org/browse/BUGBASH-1224

Thanks for the info mate,

Best Regard
 
Last edited:
P

Priix

Member
Jan 27, 2018
44
6
sampit76 said:
Greeting mate,

Do you meant The Low Battery Shutdown bugs is gone now? (Usually around 15% + when using Camera Apps)
Did You previously experience that bug?

Because from latest Lineage BUGBASH , the problem status still = Unresolve

https://jira.lineageos.org/browse/BUGBASH-1224

Thanks for the info mate,

Best Regard
Click to expand...
Click to collapse

Yeah . for some reason , the bug doesn't happen now .
Last time I had this bug but not on lineage os , it was on viper os & back then I believe it had the same kernel as lineage os .
 
G

gitsdb

Senior Member
Dec 19, 2014
193
353
Anik1 said:
can anyone recommend any audio mod? I tried arise bt it does not work..
Click to expand...
Click to collapse

Dolby Atmos is simple easy to use and very effective.. Try it.. You want regret it.. You can Google Dolby atmos for nougat and download zip file and flash it through recovery.. It's on by default on installation..
 
  • Like
Reactions: Anik1
S

sampit76

Senior Member
Mar 16, 2011
109
26
Priix said:
Yeah . for some reason , the bug doesn't happen now .
Last time I had this bug but not on lineage os , it was on viper os & back then I believe it had the same kernel as lineage os .
Click to expand...
Click to collapse

Tried it, but Sorry the battery 15% shutdown bug is not fixed >_<
Its still there

To make this bug appear do the following :

- Phone bat 15% or below
- Location setting : High Accuracy
- Run the camera apps (Stock Camera From Lineage)

Phone will shutdown.
When you turn it back on, Battery will show around 10-13% (due to booting process)

Other said need to install custom kernel, cos its kernel related problem, e.g Radon (Already Fix here : https://github.com/Umang96/Radon-Kenzo/commit/bf0886404d06438653ae23bc9297647663dfd393 )

Hopefully the dev team will fixed this issue soon >_<
(https://jira.lineageos.org/browse/BUGBASH-1224)

I like original LineageOS, NO ROOT, custome kernel, etc

Just want to avoid the mess with nigthly/weekly Update from LineageOS

Thanks & Best Regard
 
Last edited:
You must log in or register to reply here.

Similar threads

TheStrix
  • Locked
[ROM][OFFICIAL][7.1.1][kenzo] CyanogenMod 14.1
Replies
5K
Views
836K
Art Vanderlay
Art Vanderlay
TheStrix
  • Locked
[ROM][OFFICIAL][kenzo][6.0.1] CyanogenMod 13.0
Replies
4K
Views
992K
oka1
oka1
Umang96
[KERNEL][04-02][Radon Kenzo V6.3][STABLE][CM-AOSP-MIUI]
Replies
13K
Views
2M
T
travoltas
A
ResurrectionRemix ROM 6.1.0 - Official Weeklies- 8.1.0
Replies
21K
Views
2M
Y
Ya_SG
@War_machine28
[OFFICIAL][ROM][11/10/2016][Resurrection_Remix][5.7.4][Android 6.0.1, r_72][Kenzo]
Replies
6K
Views
672K
F
firepower9966

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 484
    TheStrix
    TheStrix
    QQa2TSa.png

    The package supports both Xiaomi Redmi Note 3 (kenzo) & Xiaomi Redmi Note 3 SE (kate).

    LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance and reliability over stock Android for your device.

    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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review.


    What's working :

    • Boots
    • RIL (Calls, SMS, Data)
    • VoLTE
    • Fingerprint
    • Wi-Fi
    • Bluetooth
    • Camera
    • Camcorder
    • Video Playback
    • Audio
    • Sensors
    • Flash
    • LED
    • GPS

    Known issues:

    • You say! :D

    Instructions :
    • Download the latest build and GApps
    • Reboot to recovery
    • Flash the latest build and GApps
    • Reboot

    Downloads :
    First read this before proceeding!

    Credits :
    • @banmeifyouwant: For his kernel patches
    • @luca020400: "Me: HAALP!" He answered me
    • CyanogenMod/LineageOS Team
    • Xiaomi: For providing the Kernel Source Code

    Donations:
    You don't have to but if you want;
    Donate via PayPal: http://paypal.me/ParthBhatia/
    Donate via PayTM: http://i.imgur.com/54cQl9N.jpg (QR code)

    XDA:DevDB Information
    LineageOS 14 for kenzo, ROM for the Xiaomi Redmi Note 3

    Contributors
    TheStrix
    Source Code: https://github.com/LineageOS

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

    Version Information
    Status: Beta

    Created 2017-01-21
    Last Updated 2017-05-08
    View
    185
    TheStrix
    TheStrix
    TeamWin Recovery Project (TWRP):

    Download & support: https://xdaforums.com/redmi-note-3/development/recovery-twrp-xiaomi-redmi-note-3-t3567103

    Compatible firmware:

    Source Code:

    Device Tree(s):

    Kernel Tree:

    Vendor:
    • proprietary_vendor_xiaomi: Github (For WIP: this)
    View
    137
    TheStrix
    TheStrix
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

    Frequently Asked Questions:

    Q) ROM zip failed to flash with "assert failed" or "ERROR: 7"?
    A) Update your firmware. Read this for more.

    Q) Is VoLTE supported?
    A) Yes

    Q) Support for Vulkan API?
    A) Yes

    Q) Is Goodix FP supported?
    A) Yes

    Q) Where are Developer options?
    A) Go to Settings > About phone, and press five times on Build number.

    Q) How can I enable root access?
    A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.

    Q) I don't like superuser icon in statusbar, can I install SuperSU?
    A) Yes.

    Q) How do I update GApps? (Also useful if you have GApps related problems).
    A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + GApps. (Yes, without rebooting). Reboot.

    Q) Facing Settings -> Security force close?
    A) Update your firmware.

    Q) No audio in voice calls?
    A) Update your firmware.
    View
    83
    TheStrix
    TheStrix
    jkeskir said:
    I have Kate and FCP. Now working perfectly. No modifications.
    1. Before dirty flashing I removed old fingerprints
    2. dirty flashed May 3.rd release - > booted OK, but fingerprint scanner didn't work.
    3. Flashed ResetScreenLockV2.zip - > booted OK, fingerprint scanner working also OK.
    Firmware is quite old from January.
    Click to expand...
    Click to collapse

    Great so kate firmware is fine too with current blobs (shipped in NON-HLOS/modem)
    Thanks for confirming.

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

    If you are coming from MIUI MM build directly, all should be fine.

    So the ones having issues, fingerprint or loops, firstly clean flash the build.
    Make sure you guys are using the latest compatible firmware (simply flash latest MIUI Dev ROM and do NO modifications with firmware then)
    Some guys won't know if their fw is good to go or not, here's some info everyone should know about our device related firmwares. Explained with as simple words as possible.

    PS: Before reading further, aboot=bootloader=emmc_appsboot.mbn
    & modem=NON-HLOS

    Initially our device was released with Android LP. And there was an unofficial way to unlock bootloader. What that actually was a modified aboot you flashed first which was based on LP firmware came with initial device launch.
    Now things have been updated, RN3 got MM and yet some guys flashed old LP aboot knowingly or unknowingly.
    For e.g. 1. For unlocking bootloader unofficial hassle free way
    2. Later on, there were issues with some people having re-locked bootloader automatically when flashing the latest firmware I shared (obv it was pure miui fw zip from a miui release and not mixing of firmware).
    Why did that happen with some users at not with everyone? Simple, our RN3 bootloader, when we upgrade it from LP release to MM it re-locked BL for us automatically.
    Again, at that time, there were zips made by some users (not me) which said "this won't lock bootloader" and people flashed and thought they're good to go now. How did that zip differ from mine? It simply removed the updating of aboot from it and the zip didn't upgrade the aboot and left it as it was, means for LP aboot users it wasn't updated. And they thought MAGIC! Nope.


    So today, I added a check for modem version which checks modem version prior to flashing of ROM in recovery. All it does is it checks the string in /firmware/verinfo/ver_info.txt with the latest one available I define here.
    However there's no way it seems to check the "version" for aboot, as Xiaomi doesn't keep any such track of version in their releases for their bootloader. (Even "fastboot getvar all" for us, version-bootloader value is null)

    So with aboot, just make sure you guys flashed the MM one ever and never modified it later. If not sure re-flash the MM aboot, if it re-locks, you had been using LP one, if it don't, you're already using MM one.
    For locking case, it's hard to unlock while not on MIUI, so directly flashing miui is the better option instead of checking it that way.

    To sum it up,
    I am not going to revert the change of shipping fp firmware locally, as MIUI does the same AND YOU GUYS SHOULD BE USING COMPATIBLE FIRMWARE.

    Guys who have tried clean flashing the May 3rd build and their modem version (Check /firmware/verinfo/ver_info.txt manually) matches with
    "MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1" should go through the aboot check as it's only thing fp is dependent on, you can't verify that easily.
    Also for those whose modem version is older than that, it is possible you might be using old aboot too, I suggest such people to flash MIUI MM for once and unlock it bootloader official way, so that you're on latest aboot.
    Why? Won't be any issues with the ROM related firmware, also further updating fw via the fw zips I share won't re-lock the bootloader.

    I am adding the non-modified firmware-update zip in OP for kenzo and kate from MIUI 7.5.4. Though you don't need to update it again on new Global dev release, firmwares aren't changed that often. We just need to be on FW shipped with MIUI marshmallow update.

    Every RN3 custom ROMs user should know about this post for their own benefit. Help it spread. I'll add it in OP Post #2 as well.
    View
    72
    TheStrix
    TheStrix
    Official builds

    So, OFFICIAL builds are compiled and are available to download on lineage links!
    I suggest everyone to read the following linked post before you proceed with official build installation so that you know what you're doing!
    This post is regarding everyone should know the stuffs mentioned here: http://lineageos.org/Update-and-Build-Prep/


    Official Lineage post said:
    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.
    • Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.
    • This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
    • This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data
    • This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.
    • The process for this installation will be as follows:
      1. Install EXPERIMENTAL migration build on top of last CM/LineageOS build by me
      2. Reboot
      3. Install LineageOS weekly build
      4. Reboot
      5. Re-setup your application permissions
    Click to expand...
    Click to collapse

    Other stuffs to remember:
    • Official builds will NOT be shipping root baked into the ROM. Root will be a downloadable zip based install similar to gapps installation (only need to flash it once). [Addon isn't ready as of now, it'll be available in future, I'll let you guys know about it when that happens]
    • VoLTE indicator icon is my addition, it's not present on official ROM source (May be added in future, but it isn't present as of now. VoLTE works, but no VoLTE icon is shown, do not want posts regarding that in future so making it clear)

    OP updated with links.
    View

New posts