[OFFICIAL] LineageOS 17.1 for z3c

Search This thread

nokian95ita

Senior Member
Sep 19, 2008
336
19
Good Morning, i switched to open gapps aroma and installed android auto and what i need but when i link to my car it say that there is no compatible app installed
 

tomKater

Member
Jul 29, 2014
32
6
Huawei MediaPad M5 Lite

nokian95ita

Senior Member
Sep 19, 2008
336
19
Hi,

I faced the same problem. You have to come back to the opengapps version 1/12 (https://sourceforge.net/projects/op...en_gapps-arm-10.0-aroma-20201201.zip/download). Don't know why.

Link your car with this version, and after you can update Android auto and other apps.
i switched to BitGapps only core package and after i installed mannually all that i need and it worked but the very problem is that is very very laggi and in unsuefull. do you use with z3 compact? how do it work?
 

tomKater

Member
Jul 29, 2014
32
6
Huawei MediaPad M5 Lite
i switched to BitGapps only core package and after i installed mannually all that i need and it worked but the very problem is that is very very laggi and in unsuefull. do you use with z3 compact? how do it work?
I use with Z3 compact and since the flash, I've only used it once, but I haven't noticed anything unusual. For my part, I flashed the opengapps stock version (1/12).
 

nokian95ita

Senior Member
Sep 19, 2008
336
19
I use with Z3 compact and since the flash, I've only used it once, but I haven't noticed anything unusual. For my part, I flashed the opengapps stock version (1/12).
sorry i think that my words was bad.... the smartphone work good but with android auto is very laggi, i want to use the sony beacause my mi9t is very big for me
 

tomKater

Member
Jul 29, 2014
32
6
Huawei MediaPad M5 Lite
sorry i think that my words was bad.... the smartphone work good but with android auto is very laggi, i want to use the sony beacause my mi9t is very big for me
Yes, it's was well like that I had understood : since the flash, I connected only once my phone to my car and used android auto. But for my part, I haven't noticed anything unusual, Android auto was usable as usually...
But if you never used Android auto with the sony z3c before, you have to know that it's still a little bit slow to start each time you connect your phone, but after that it's usable.
 
  • Like
Reactions: nokian95ita

nokian95ita

Senior Member
Sep 19, 2008
336
19
Yes, it's was well like that I had understood : since the flash, I connected only once my phone to my car and used android auto. But for my part, I haven't noticed anything unusual, Android auto was usable as usually...
But if you never used Android auto with the sony z3c before, you have to know that it's still a little bit slow to start each time you connect your phone, but after that it's usable.
Now it work, i deleted all data from android auto and restarted all. yes it continue to be a little slow but it can be used. thanks a lot, i like it

I have a new question: i want to remove the black bar under the keyboard, it appear beacause i have more keyboard installed

I reverted to Gapps like as say @tomKater but it doen't work good. I need to delete all data whenever i link the smartphone to the head unit. I don't have a stand alone head unit bit i use head unit reloaded. when i link the smarphone it launch android auto but after few second android auto close it self so if delete all data it work but at next connection i need to delete al data.
 
Last edited:

tomKater

Member
Jul 29, 2014
32
6
Huawei MediaPad M5 Lite
Is there any news about that? I have the same problem. No deep sleep with this ROM and this is a no-go for me.

I confirm too. I missed the post by @pawloland and it's been several days that I investigate my battery drain (it empties almost completely during the night when there is not use at all). However, my impression was that it was worse since the last updates (or maybe it's not the rom but one of my app ...).
 

oscardu13

New member
Feb 5, 2021
1
0
Hi everyone,
i'm a LOS enthousiast since a couple of years, mostly on Samsung, but let say i'm still a noob !
I've been working for the last two days on a Sony Xperia Z3 Compact.
I managed to install TWRP with fastboot, and the installation of lineage 17.1 seems to work fine, finishing with "script succeeded". The next screen asks if if want to install the TWRP app, ok, why not, then i swipe right to reboot the system and then... black screen. Not event the smal led is on. The phone is not dead, there is a vibration when i press the power button.
The only thing i can from there is connect back to fastboot, and restart twrp from there.
I had the same result with different versions of TWRP (3.0.2, 3.2.1, 3.3.0) and different roms.
Lineage 14.1 installs fine and run.
Any fast help or suggestion is very welcome !
thanks in advance
 

J_C_D

Member
Jan 30, 2012
18
12
Mannheim / Germany
I confirm too. I missed the post by @pawloland and it's been several days that I investigate my battery drain (it empties almost completely during the night when there is not use at all). However, my impression was that it was worse since the last updates (or maybe it's not the rom but one of my app ...).
I just learned something new: the problem does not occur, when BT is switched off right from system startup!
The wakelock ("BTLowPower") then only occurs when BT becomes switched on (this may be ok, I don't know), but when BT is then switched off again, the wakelock persists!
For me, that seems like a simple driver bug.

I'm curently looking up the code of bcm4339 and as far as I understand, the wakelock is only used to ensure that IRQ requests of the BT hardware are handled by the CPU instead of going to deep sleep. Seems pretty simple, but how is it possible that this wakelock persists after BT is deactivated???
EDIT: I was wrong: It is intended to prevent the device from deep sleep for 10 seconds after BT activity.

EDIT: Ok, for me the Low Power handling of this driver seems completely broken: The culprit seems to be that host_wake_isr() activates the wakelock but cancels the enter_lpm_timer which is in turn responsible to clear the wakelock. I believe that it should restart the timer instead.
But this seems not the only bug: imho, bcm_bt_lpm_exit_lpm() should re-lock the wakelock when restarting the enter_lpm_timer, which it doesn't do.
Can someone help debugging / looking through that stuff?
 
Last edited:

J_C_D

Member
Jan 30, 2012
18
12
Mannheim / Germany
@NeoArian could you please point me to the correct toolchain and kernel sources of this fw to allow me to test modifications of the BT driver?

I'm currently using the kernel sources from branch lineage-17.1 of this Repo and this cross-build toolchain, manually down-dated to a pre-clang state (my head is now at commit a4d56615040a9a42f8345c65d4877ca9b934808e).
Curiously, I had to slightly modify the kernel config (based on shinano_aries_defconfig), otherwise the kernel didn't link because of some missing netfilter module.

Now, when I flash that kernel, the device does not boot anymore, so something seems to be completely wrong here.

EDIT: My own kernel build boots now! :)

And this is what I had to do:
- use lineageos_shinano_aries_defconfig instead of shinano_aries_defconfig
- repack boot.img using zImage-dtb instead of zImage
 
Last edited:

J_C_D

Member
Jan 30, 2012
18
12
Mannheim / Germany
GOOD NEWS EVERYBODY!!!
I managed to finally fix the persistent "BTLowPower" wakelock
which caused the CPU to no longer enter Deep Sleep state and thus resulted in high battery drain once Bluetooth had been enabled! 🍻

UPDATE: I just found a much simpler solution that does the trick! The real culprit was a #ifdef in BT Power Management that was introduced by a commit in July 2019 and then has fallen into oblivion :ROFLMAO:.
Fixed! -> Version 3.
@tblr0ne , @L.Lmar : can you please also test this version?



*** TESTERS NEEDED! ***

Find attached the modified boot.img. USE AT OWN RISK!

Installation:
- reboot Z3C into Bootloader (Vol+)
- flash new boot image over current LineageOS17.1 installation using fastboot
Code:
fastboot flash boot boot-BTLowPower-fix-3.img
- reboot
Code:
fastboot reboot

NOTE for Magisk users:

After flashing the new boot image, it is required to re-install Magisk. Do this by immediately booting into TWRP after the new boot image is flashed.
Also note that you need Magisk v20.4 for this! Later versions won't work.
Anyway, you will be able to upgrade Magisk to up-to-date versions using Magisk Manager after the system has booted.

@NeoArian when everything seems ok, I will create a merge request in LineageOS/android_kernel_sony_msm8974. Is this the correct place / way to go?
 

Attachments

  • boot-BTLowPower-fix-3.img
    7.7 MB · Views: 7
Last edited:

versus2165897

New member
Feb 7, 2021
2
1
Some bugs appeared on the last 3 updates. Reflashing did not fix the problems. I have no gaps installed, root.
The problem appears when I enable Safe Start, when the device is encrypted.
1. Accelerometer sensor, autoprotect, proximity does not work.
2. When turning on the phone, a long startup before the screen where you must enter the password is displayed. Usually the first startup should be faster, asking for the password.
The problem lies somewhere in the encryption of the device, in the option Safe start.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Thanks to everyone for the really detailed testing :) I really appreciate it.
    Since yesterday (still on 18.1), I have two kernel wakelocks preventing deep sleep:
    - msm_serial_hs_dma
    - BTLowPower

    I used BBS with the adb shell settings put global hidden_api_policy 1 fix to check the wakelocks.
    Regarding the BTLowPower wakelock, @J_C_D has fixed that on lineage-17.1 recently and at this time the lineage-18.1 branch was already forked. I will make sure to include the fix for lineage-18.1 with the next update.
    3
    Good Evening!

    It's the time again, you might have already noticed that lineage 18.1 is official for some devices now. We, the sony shinano maintainers, were not sleeping and have also prepared our device for 18.1. I have uploaded a test build here: https://sourceforge.net/projects/ep...18.1/lineage-18.1-20210406-UNOFFICIAL-z3c.zip
    I would appreciate some testing/feedback on this build. There shouldn't be major issues on the test build, from my own testing it should be on-par with 17.1.
    I am optimistic that we can also achieve an official release of 18.1 for the z3c.

    All source codes can be found on the lineageos github in lineage-18.1 branches + additional patches for sony msm8974 are up on gerrit: https://review.lineageos.org/q/status:open+-is:wip

    Happy flashing!

    It's been a while since last time I did test a new Android version on this smartphone.
    First of all, I'd like to thank you all maintainers for your effort and to congratulate for the great work done with this first build of lineage 18.1.
    I did some basic testing (don't expect anything too accurate, since this is not my main device for a while) which I'll resume below:
    • Booting was fine and time is quite comparable with previous lineage versions
    • I succesfully installed a test build of OpenGapps (micro configuration of 20210130), which seems to work pretty well
    • account setup and sync works
    • WiFi working at both 2.4/5 GHz
    • Bluetooth working fine, I had no problems connecting to my bluetooth earbuds and listen to some music
    • NearbySharing is working like a charm and quite fast too
    • online charging is working at full speed (about 1800 mA with a quickcharge 3.0 wall charger)
    • MTP working
    • OTG works for both input devices (mouse, keyboard, etc..) or mass storage
    • camera is fully working (taking pictures with both front/rear cameras, taking videos, flash)
    • phone calls are working, but I believe that microphones are swapped, using the upper one as main, resulting in a low volume during calls
    • mobile data is stuck at EDGE for me, I couldn't get it to use LTE instead
    • audio is fine
    • video playback also seems to be fine (tested on youtube at 1080p)
    • chromecast works, in fact I did cast screen and youtube to a Google Nest Hub without any problem
    • the OS is overall responsive and snappy, even with gapps installed
    • screen rotation, accelerometer, gyroscope, proximity sensor, etc.. all fine
    • double tap to wake and other classic gestures are fine
    • I couldn't test hotspot since, as I said, I was stuck at 2G connection which was quite unresponsive
    • unfortunately I cannot test GPS or NFC neither
    I hope I did not forget something important.
    I'm going to keep this installed since it's really stable, so feel free to ask me for some other testing and I'll for sure try to do that as soon as I have some spare time :)
    3
    Good Evening!

    It's the time again, you might have already noticed that lineage 18.1 is official for some devices now. We, the sony shinano maintainers, were not sleeping and have also prepared our device for 18.1. I have uploaded a test build here: https://sourceforge.net/projects/ep...18.1/lineage-18.1-20210406-UNOFFICIAL-z3c.zip
    I would appreciate some testing/feedback on this build. There shouldn't be major issues on the test build, from my own testing it should be on-par with 17.1.
    I am optimistic that we can also achieve an official release of 18.1 for the z3c.

    All source codes can be found on the lineageos github in lineage-18.1 branches + additional patches for sony msm8974 are up on gerrit: https://review.lineageos.org/q/status:open+-is:wip

    Happy flashing!

    Thank you NeoArian and all other developers!
    Your LineageOS 17.1 build really revived this small phone!
    My previous experiences with installing unofficial builds were not as great as this one.
    The only things I miss compared to stock Android 6 are the camera button full press to open the camera app (which by the way starts slower than on stock Android 6), the secondary mic noise suppression (which wasn't working anymore on mine anyway) and the service tests opened with the *#*#SERVICE#*#* code.

    About this new LineageOS 18.1 (I used MindTheGapps-11.0.0-arm-20210412_124103), I didn't notice any problem compared to 17.1.
    In fact, using Migrate to restore all apps and settings, I almost thought the update didn't work since it booted like usual.

    For the other users, in addition to Migrate, I of course reinstalled Magisk, which doesn't work natively (even with the workaround of installing 20.4 first) on this new 18.1 build. The boot_patch.sh file has to be modified, I've attached a version of Magisk 22.1 with that file already modified (works at least on Z3C). NeoArian: is there any way to modify the builds so that they use init instead of init.real?

    I did some basic testing
    Pretty extensive "basic testing"!

    • phone calls are working, but I believe that microphones are swapped, using the upper one as main, resulting in a low volume during calls
    • mobile data is stuck at EDGE for me, I couldn't get it to use LTE instead
    • double tap to wake and other classic gestures are fine
    • unfortunately I cannot test GPS or NFC neither
    - Phone calls were fine on 17.1, haven't checked yet on 18.1. UPDATE: still fine on 18.1
    - LTE works here (at least band 1). I'll see if I can connect to different bands.
    I don't know if it helps, but here's what modemcaps says:
    ========================================
    Sony Xperia Z3 Compact
    Model ID : z3c
    SoC : SDM800
    Modem HW : MTP (msm)
    Modem FW : 8974-AAAAANAZQ-00112-61
    Modem Link : Generation 2 (Channel 0)
    Kernel Base : Linux 3.4.113
    Kernel Fork : gb76b4a9ae603
    Sys Version : Android 11 (armeabi-v7a)
    App Version : 2019-12-27-10 (armeabi-v7a)
    https://t.me/ru_fieldtest_modemcaps
    ========================================
    SIM Card : Single SIM
    LTE CA : Is not supported
    LTE Voice : GSM/UMTS CS Fallback
    CDMA2000 1X CS Fallback
    VoLTE
    Radios : 2G GSM
    3G UMTS
    4G LTE
    GSM Bands : B3 (1800 FDD)
    B8 (900/E FDD)
    B- (900/P FDD)
    B5 (850 FDD)
    B2 (1900 FDD)
    UMTS Bands : B1 (2100 FDD)
    B2 (1900 FDD)
    B4 (1700 FDD)
    B5 (850 FDD)
    B8 (900 FDD)
    LTE Bands : B1 (2100 FDD)
    B2 (1900 FDD)
    B3 (1800 FDD)
    B4 (2100 FDD)
    B5 (850 FDD)
    B7 (2600 FDD)
    B8 (900 FDD)
    B13 (700 FDD)
    B17 (700 FDD)
    B20 (800 FDD)

    - Double tap to wake didn't work for me on stock Android 6 (at least when on deep sleep). It seems to work now which is an improvement.
    - GPS works fine.

    I'm using it from now on, so I'll report any problem.
    3
    Good Evening!

    It's the time again, you might have already noticed that lineage 18.1 is official for some devices now. We, the sony shinano maintainers, were not sleeping and have also prepared our device for 18.1. I have uploaded a test build here: https://sourceforge.net/projects/ep...18.1/lineage-18.1-20210406-UNOFFICIAL-z3c.zip
    I would appreciate some testing/feedback on this build. There shouldn't be major issues on the test build, from my own testing it should be on-par with 17.1.
    I am optimistic that we can also achieve an official release of 18.1 for the z3c.

    All source codes can be found on the lineageos github in lineage-18.1 branches + additional patches for sony msm8974 are up on gerrit: https://review.lineageos.org/q/status:open+-is:wip

    Happy flashing!
    First thank you NeoArian and all other developers involved for your great work! I also did some short tests and found nothing which was not working. I worked with OpenGapps test build of 20210130. I tested:

    - WLAN
    - Bluethooth
    - Mobil date
    - phone call
    - Camera/Video/flash light
    - Audio and video playback
    - normal usage like my los 17.1 daily driver

    I used some configuration like i did on my los 17.1 daily driver and it looks really good! Unfortunately I cannot test GPS as my test device had an hardware problem here.

    So really fine from my side here, only the test with Magisk to root the device didn't work. But this shouldn't be related to los 18.1. Hopefully Magisk will be functional sometimes later.

    Thanks again!
    1
    Hello, I installed 18.1 yesterday (oh boy, it was hard and expensive - SIM Lock with 0 attempts) and I'm impressed. I didn't installed GApps as I can't found ARM pack (anyone help me plz 😁). I skipped LOS17.1 so I compare it to stock 6.0 and in my opinion it's noticably faster and battery lasts longer however maybe because I have no GApps.

    Tested so far
    - WiFi
    - Mobile data
    - Phone calls (calling and answering)
    - Bluetooth (sending/receiving files, earphones, Xbox gamepad, keyboard)
    - GPS (not so advanced tests, I'll test it later)
    - Camera (photos, video in front and rear cams, flashlight)
    - OTG (pendrives and mouse)
    - Screenshots
    - Receiving SMS, but not sending (inactive number)
    - Charging using microUSB and magnetic connector

    Not tested yet:
    - Hotspot
    - NFC
    - Screen recording
    - Screen mirroring

    Found some visual bugs but not sure if it's LOS or Nova Launcher in beta channel so I'll check it and give info later.

    I'm waiting for future builds for tests and hope they'll be [OFFICIAL]!
  • 10
    Good Evening!

    It's the time again, you might have already noticed that lineage 18.1 is official for some devices now. We, the sony shinano maintainers, were not sleeping and have also prepared our device for 18.1. I have uploaded a test build here: https://sourceforge.net/projects/ep...18.1/lineage-18.1-20210406-UNOFFICIAL-z3c.zip
    I would appreciate some testing/feedback on this build. There shouldn't be major issues on the test build, from my own testing it should be on-par with 17.1.
    I am optimistic that we can also achieve an official release of 18.1 for the z3c.

    All source codes can be found on the lineageos github in lineage-18.1 branches + additional patches for sony msm8974 are up on gerrit: https://review.lineageos.org/q/status:open+-is:wip

    Happy flashing!
    8
    2okPze5.png


    Introduction
    LineageOS, an open-source Android distribution, is available for several devices,
    with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
    Join us and breathe new life in your device, be it old or new.
    If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.

    Features
    Individuality
    Customization is paramount to productivity.
    That’s why LineageOS promises to push for user personalization and preference.
    Everyone is unique and your device should be too.
    Security
    Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
    Trust will help you understand the security of your device and warn you about possible threats.
    We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
    And to make your device more secure, lock everything behind an enhanced lock screen.
    Longevity
    LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.

    Installation:
    If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below.
    If you are coming from stock or other ROMs, you need to make a factory reset.
    As always, make sure to backup before installing this ROM.

    More detailed instructions at:
    Install LineageOS on z3c

    Downloads
    Download LineageOS 17.1 for Xperia Z3 Compact.
    If you prefer TWRP over Lineage recovery, you can get it here.
    Recommended Google Apps package: Open GApps (choose ARM as Platform and 10.0 as Android, use the Variant you want. Recommended nano package)

    Source code
    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.

    The device specific source code can be found in the LineageOS Github repo.
    Z3 Compact device tree
    Sony Shinano common device tree
    Sony MSM8974 common device tree
    Sony MSM8974 kernel
    The used defconfig is lineageos_shinano_aries_defconfig.

    Changelog:
    Changes for z3c

    Bug reports:
    How to submit a bug report
    LineageOS GitLab

    Donate to support development:
    Donate via PayPal to NeoArian
    Donate via PayPal to LineageOS

    XDA:DevDB Information
    LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact

    Contributors
    NeoArian
    ROM OS Version: Android 10
    ROM Kernel: Linux 3.4.x

    Version Information
    Status: Stable

    Created 2020-09-08
    Last Updated 2020-09-12
    5
    Hello @NeoArian , hello community. I'am very happy to see that the "BTLowPower" wakelock issue was fixed by @J_C_D and that it was merged into the android_kernel_sony_msm8974 repository last week. Thanks to all of you that spend your time supporting the Z3C and other older devices until now.
    5
    Yes, that's right.
    When Safe Start is turned on, the accelerometer does not work. Therefore, screen rotation, light sensor does not work.
    Thanks for the report. We were able to reproduce it and have fixed it. We will merge the fix within some days so that it will be fixed in the upcoming releases.
    Greetings, arian.
    4
    GOOD NEWS EVERYBODY!!!
    I managed to finally fix the persistent "BTLowPower" wakelock
    which caused the CPU to no longer enter Deep Sleep state and thus resulted in high battery drain once Bluetooth had been enabled! 🍻

    UPDATE: I just found a much simpler solution that does the trick! The real culprit was a #ifdef in BT Power Management that was introduced by a commit in July 2019 and then has fallen into oblivion :ROFLMAO:.
    Fixed! -> Version 3.
    @tblr0ne , @L.Lmar : can you please also test this version?



    *** TESTERS NEEDED! ***

    Find attached the modified boot.img. USE AT OWN RISK!

    Installation:
    - reboot Z3C into Bootloader (Vol+)
    - flash new boot image over current LineageOS17.1 installation using fastboot
    Code:
    fastboot flash boot boot-BTLowPower-fix-3.img
    - reboot
    Code:
    fastboot reboot

    NOTE for Magisk users:

    After flashing the new boot image, it is required to re-install Magisk. Do this by immediately booting into TWRP after the new boot image is flashed.
    Also note that you need Magisk v20.4 for this! Later versions won't work.
    Anyway, you will be able to upgrade Magisk to up-to-date versions using Magisk Manager after the system has booted.

    @NeoArian when everything seems ok, I will create a merge request in LineageOS/android_kernel_sony_msm8974. Is this the correct place / way to go?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone