[ROM][7.1.2][OFFICIAL] LineageOS 14.1

Search This thread

TobiPeter

Senior Member
that's exactly the point, there can't be a delay when there is no ETA ;)

That's not true.

There was a rule (more or less).
New versions were released in November.
Now it's February.
That's a delay in my eyes.

But that wasn't my point at all.


I just wanted to know, why there are no official LOS 15 versions until yet.

And if you don't know it, it's okay, but I would appreciate it, if you would say that and we could end this useless discussion.
Thanks.
 
  • Like
Reactions: TeeHoang

GabiCS

Member
Jan 15, 2013
34
14
Bucharest
You mean our Moto Z won't get official LS15.1 until Moto officially release 8.0?

There have been soak tests for official 8.0 in south america before christmas and a week ago I read that the rollout had reached Australia.

I think that was deemed a hoax because the original website didn't publish a verifiable source, the moto reps on the moto forum had no idea about that australian rollout, february security patch was launched and another soak started on 05.02.2018
 
  • Like
Reactions: TeeHoang

sharukins

Senior Member
Jun 15, 2011
476
165
I think that was deemed a hoax because the original website didn't publish a verifiable source, the moto reps on the moto forum had no idea about that australian rollout, february security patch was launched and another soak started on 05.02.2018

Yeah, ccording to the comments below the article no one received the update yet. But they say the X4 get's oreo first anyway, I got that wrong.
I wouldn't necessarily count launching another monthly security update as hint for a delay of a new version. There's probably two different teams working on that and from a corporate perspective it's probably better to have the monthly security update and a new version ready at the same time than to have none of both because for some reason the update got delayed. But if there's another soak test that started a week ago then it'll take problably another month anyway.
Do you by any chance have the source for the february soak test?
 

GabiCS

Member
Jan 15, 2013
34
14
Bucharest
Yeah, ccording to the comments below the article no one received the update yet. But they say the X4 get's oreo first anyway, I got that wrong.
I wouldn't necessarily count launching another monthly security update as hint for a delay of a new version. There's probably two different teams working on that and from a corporate perspective it's probably better to have the monthly security update and a new version ready at the same time than to have none of both because for some reason the update got delayed. But if there's another soak test that started a week ago then it'll take problably another month anyway.
Do you by any chance have the source for the february soak test?

I mentioned the security patch update as an evidence that oreo isn't rolling out using logics as why would they push security patches and software upgrades simultaneously when they could've pushed oreo with february security patch. Get it? And for the source of the soak test there is this post on reddit: https://www.reddit.com/r/Moto_Z/comments/7vfkvm/soak_test_android_8_has_begun_for_moto_z_droid/ And that is enough offtopic on this los thread...
 

sharukins

Senior Member
Jun 15, 2011
476
165
I mentioned the security patch update as an evidence that oreo isn't rolling out using logics as why would they push security patches and software upgrades simultaneously when they could've pushed oreo with february security patch. Get it? And for the source of the soak test there is this post on reddit: https://www.reddit.com/r/Moto_Z/comments/7vfkvm/soak_test_android_8_has_begun_for_moto_z_droid/ And that is enough offtopic on this los thread...

woah there, no need to feel attacked by any means. I was just pointing out that your logic isn't necessarily the only on to be considered.
And the soak test started a week ago is for the Z droid, so the US only versions and therefore applies to US only. I don't see why this means by any way that the update is not happening in another region of the world, as lenovo has done regional updates ever since. But you''re right more than enough offtopic on this LOS thread :fingers-crossed:
 

Calkulin

Recognized Developer
Sep 3, 2008
1,647
9,109
Samsung Galaxy S21+
Based on @erfanoabdi's commit to fix VoIP audio on LOS 15, I found which path in the mixer_paths.xml was causing the issue on LOS 14.1. I made a flashable zip to fix it or if you want to fix it manually, open mixer_paths.xml from /system/etc and make this change

Code:
[U]old[/U]
<ctl name="Voip_Tx Mixer SLIM_0_TX_Voip" value="0" />

[U]new[/U]
<ctl name="Voip_Tx Mixer SLIM_0_TX_Voip" value="1" />
 

Attachments

  • Calkulin's_LineageOS_14.1_VoIP_Audio_Fix.zip
    181.6 KB · Views: 43
  • Like
Reactions: TeeHoang

stef_nix

Member
Nov 12, 2016
11
1
Based on @erfanoabdi's commit to fix VoIP audio on LOS 15, I found which path in the mixer_paths.xml was causing the issue on LOS 14.1. I made a flashable zip to fix it or if you want to fix it manually, open mixer_paths.xml from /system/etc and make this change

Code:
[U]old[/U]
<ctl name="Voip_Tx Mixer SLIM_0_TX_Voip" value="0" />

[U]new[/U]
<ctl name="Voip_Tx Mixer SLIM_0_TX_Voip" value="1" />

I'm wondering why this isn't part of the 14.1 Nightlies. I can finally justify using LineageOS. Thanks!
 
  • Like
Reactions: Achilles Etimone

erfanoabdi

Recognized Developer
Jan 3, 2015
1,019
3,175
Tehran
erfanoabdi.github.io
Based on @erfanoabdi's commit to fix VoIP audio on LOS 15, I found which path in the mixer_paths.xml was causing the issue on LOS 14.1. I made a flashable zip to fix it or if you want to fix it manually, open mixer_paths.xml from /system/etc and make this change



I'm wondering why this isn't part of the 14.1 Nightlies. I can finally justify using LineageOS. Thanks!
What if you change this prop to false?
https://github.com/LineageOS/android_device_motorola_griffin/blob/cm-14.1/system.prop#L45

Without touching anything else
 
  • Like
Reactions: Achilles Etimone

Top Liked Posts

  • There are no posts matching your filters.
  • 40
    https%3A%2F%2Fimg.xda-cdn.com%2FkyxRsPr6u1Vy5sOBsyaCfk9XV7E%3D%2Fhttps%253A%252F%252Fs19.postimg.org%252Fvbiad1tq7%252Fhttp_i_imgur_com_f2g_AFBe.png

    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.
    *
    * I am 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 me for messing up your device, I 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.

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


    Broken:

    • Moto Mods

    Download Link
    Changelog

    Installation:
    • Reboot to recovery
    • Format /system, /data and /cache
    • Install LineageOS zip
    • Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
    • Install [optional] su addon

    Sources:


    XDA:DevDB Information
    LineageOS 14.1, ROM for the Moto Z

    Contributors
    vache, erfanoabdi
    Source Code: https://github.com/LineageOS/

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.0.x
    ROM Firmware Required: Unlocked bootloader, TWRP

    Version Information
    Status: Beta
    Beta Release Date: 2017-01-28

    Created 2017-01-28
    Last Updated 2017-06-02
    9
    Just to let you know, i started the process to go official. Do not ask for ETA ;)
    6
    So, no new release cause of that in-call volume bug. Spend hours to find what's going wrong, without any results atm.

    I'll try more for one or two days before sharing a new release.


    What's new for next build:

    -Kernel rebase and updated from CAF
    -Audio Mod fix
    -Add projector app for related Mod
    -Mods Platform version fix
    -Sync GPS HAL with CAF
    -Sync IPACM with CAF
    -Fix "Hand Wave" wakeup toggle in Gestures
    -Hopefully in-call volume fix (Edit: Fixed)
    4
    Update

    Do we have this build? (RETBR + Mods)

    Grab the last version here : lineage-14.1-20170206-UNOFFICIAL-griffin.zip

    Changelog :
    • Kernel sources synced with CAF
    • Sync with LOS sources
    • Added back Mods apps
    • Some fixes for Mods service (try and report with logs please)
    • Enforced SELinux
    • Include fix for RETBR