[9] LineageOS 16.0 for z3c

Status
Not open for further replies.
Search This thread

Mr.Tom_Tom

Senior Member
  • Feb 16, 2008
    146
    177
    Munich
    Wait what, I had some success yesterday evening with this, now the volume in the top speaker changes significant more but I didn't push the build yet XD

    @NeoArian did you find a general solution for that? So far I looked at the mixer_paths config files (found no issue there) and started to look at the msm8974 kernel audio driver. Now I wanted to dig into that a bit deeper but then saw your post here. I can also do some A/B tests today if you like.
     

    dhemker

    Member
    Mar 23, 2017
    49
    136
    I tested the new build. When starting a call, call volume can indeed be adjusted from low to max. When turning loudspeaker on and then off again, call volume stays at maximum and can't be adjusted anymore. Furthermore, the sound is still kind of crackling. In contrast, in call sound quality from early August build was crystal clear. Is it possible to record call logs or stuff to isolate the bug/misconfiguration?

    Dennis
     
    • Like
    Reactions: Mr.Tom_Tom

    Mr.Tom_Tom

    Senior Member
  • Feb 16, 2008
    146
    177
    Munich
    Testing FMRadio & Call Volume

    I have upload a new build. [...] Please test call volume and FM Radio because my headphone jack is broken. Thank you
    FMRadio not working for me, when connecting a headphone a notice (toast) appears with something like "Currently not available".
    LogCat excerpt:
    Code:
    10-27 02:16:49.209   382  5329 D audio_hw_primary: start_output_stream: enter: stream(0xabc2f180)usecase(1: low-latency-playback) devices(0x4)
    10-27 02:16:49.209   382  5329 D audio_hw_primary: start_output_stream: enter: usecase(1: low-latency-playback) devices(0x4)
    10-27 02:16:49.209   382  5329 D audio_hw_extn: audio_extn_get_anc_enabled: anc_enabled:0
    10-27 02:16:49.209   382  5329 D audio_hw_primary: select_devices: out_snd_device(4: headphones-regulation) in_snd_device(0: )
    10-27 02:16:49.209   382  5329 W msm8974_platform: Codec backend bitwidth 16, samplerate 48000
    10-27 02:16:49.209   382  5329 D hardware_info: hw_info_append_hw_type : device_name = headphones-regulation
    10-27 02:16:49.209   382  5329 I msm8974_platform: platform_send_audio_calibration: sending audio calibration for snd_device(4) acdb_id(10)
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 10, path =  0
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> send_adm_topology
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> send_asm_topology
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> send_audtable
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> send_audvoltable
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
    10-27 02:16:49.209   382  5329 D ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL
    10-27 02:16:49.209   382  5329 D audio_route: Apply path: headphones-regulation
    10-27 02:16:49.212   654  3872 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.fmradio/.FmMainActivity bnds=[23,884][191,1062]} from uid 10021
    10-27 02:16:49.219   382  5329 D audio_route: Apply path: low-latency-playback
    10-27 02:16:49.222   382  5329 D audio_hw_primary: select_devices: done
    10-27 02:16:49.258  6460  6460 W ActivityThread: handleWindowVisibility: no activity for token [email protected]
    10-27 02:16:49.307  6460  6460 D FmMainActivity: refreshStationUI, set station value null when it is first time
    10-27 02:16:49.314  6460  6460 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1531 android.content.ContextWrapper.startService:664 com.android.fmradio.FmMainActivity.onStart:647 android.app.Instrumentation.callActivityOnStart:1391 android.app.Activity.performStart:7165
    10-27 02:16:49.316  6460  6460 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1611 android.content.ContextWrapper.bindService:698 com.android.fmradio.FmMainActivity.onStart:653 android.app.Instrumentation.callActivityOnStart:1391 android.app.Activity.performStart:7165
    10-27 02:16:49.321  6460  6460 D FmMainActivity: onResume, mService is null
    10-27 02:16:49.340  6460  6486 D FmService: onAudioPatchListUpdate, not power up
    10-27 02:16:49.341   382   503 D AudioPolicyManagerCustom: setForceUse() usage 1, config 0, mPhoneState 0
    10-27 02:16:49.359   382   637 D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=4
    10-27 02:16:49.364   382   637 D audio_hw_extn: audio_extn_get_anc_enabled: anc_enabled:0
    10-27 02:16:49.364   382   637 D audio_hw_extn: audio_extn_set_anc_parameters: anc_enabled:0
    10-27 02:16:49.368   382  6669 D audio_hw_primary: adev_open_input_stream: enter: sample_rate(44100) channel_mask(0xc) devices(0x80002000)        stream_handle(0xac333ce0) io_handle(78) source(1998)
    10-27 02:16:49.369   382  7757 I AudioFlinger: AudioFlinger's thread 0xa9383fc0 tid=7757 ready to run
    10-27 02:16:49.369   382  7757 D audio_hw_primary: in_standby: enter: stream (0xac333ce0) usecase(17: audio-record)
    10-27 02:16:49.372   382  7757 D audio_hw_primary: in_standby: enter: stream (0xac333ce0) usecase(17: audio-record)
    10-27 02:16:49.375   382  6668 I AudioPolicyManagerCustom: setting force DEEP buffer now
    10-27 02:16:49.376   382  6668 D AudioFlinger: Client defaulted notificationFrames to 1178 for frameCount 3536
    10-27 02:16:49.377  6460  6460 W AudioTrack: Use of stream types is deprecated for operations other than volume control
    10-27 02:16:49.377  6460  6460 W AudioTrack: See the documentation of AudioTrack() for what to use instead with android.media.AudioAttributes to qualify your playback use case
    10-27 02:16:49.385  6460  6485 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    10-27 02:16:49.386  6460  6485 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
    10-27 02:16:49.388  6460  6460 D FmService: onReceive, action = android.intent.action.HEADSET_PLUG / command = null
    10-27 02:16:49.388  6460  6460 D FmService: onReceive, mIsServiceInited is false
    10-27 02:16:49.393  6460  7754 W AudioManager: Use of stream types is deprecated for operations other than volume control
    10-27 02:16:49.393  6460  7754 W AudioManager: See the documentation of requestAudioFocus() for what to use instead with android.media.AudioAttributes to qualify your playback use case
    10-27 02:16:49.393   654  4113 I MediaFocusControl: requestAudioFocus() from uid/pid 1000/6460 [email protected][email protected] callingPack=com.android.fmradio req=1 flags=0x0 sdk=23
    10-27 02:16:49.394  6460  7754 I         : androidFmRadioRxGetState, state
    10-27 02:16:49.394  6460  7754 I         : androidFmRadioRxStart. LowFreq 87500, HighFreq 108000, DefaultFreq 100000, grid 100.
    10-27 02:16:49.394  6460  7754 E         : No matching library found in path /system/lib/
    10-27 02:16:49.394  6460  7754 E         : vendor registration failed
    10-27 02:16:49.394  6460  7754 I         : androidFmRadioThrowException, java/io/IOException ('IO Exception') @ hardware/broadcom/fm/libfmjni/android_fm.cpp 724 (androidFmRadioStart)
    10-27 02:16:49.410  6460  6460 D FmMainActivity: mHandler.handleMessage, what = 9,hashcode:109581418
    10-27 02:16:49.410  6460  6460 D FmMainActivity: refreshStationUI, set station value null when it is first time
    10-27 02:16:49.428   654   700 I ActivityManager: Displayed com.android.fmradio/.FmMainActivity: +202ms
    10-27 02:16:49.435  6460  6485 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    10-27 02:16:49.435  6460  6485 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
    10-27 02:16:49.580   350   389 W SurfaceFlinger: Attempting to set client state on removed layer: Splash Screen com.android.fmradio#0
    10-27 02:16:49.580   350   389 W SurfaceFlinger: Attempting to destroy on removed layer: Splash Screen com.android.fmradio#0
    10-27 02:16:51.454   654  3960 W NotificationService: Toast already killed. pkg=com.android.fmradio [email protected]
    10-27 02:16:51.964   350   389 W SurfaceFlinger: Attempting to destroy on removed layer: 58906c9 Toast#0
    10-27 02:16:52.416   382   637 D audio_hw_primary: out_standby: enter: stream (0xabc2f180) usecase(1: low-latency-playback)
    10-27 02:16:52.537   382   637 D hardware_info: hw_info_append_hw_type : device_name = headphones-regulation
    10-27 02:16:54.862   324   324 W ice     : type=1400 audit(0.0:835): avc: denied { read } for name="type" dev="sysfs" ino=19662 scontext=u:r:hal_health_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0
    10-27 02:16:54.866   324   324 W ice     : type=1400 audit(0.0:836): avc: denied { read } for name="type" dev="sysfs" ino=10736 scontext=u:r:hal_health_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0
    10-27 02:16:54.892   325   325 D lights.msm8974: led [solid] = ffffff00
    10-27 02:16:56.224   382  5329 D audio_hw_primary: start_output_stream: enter: stream(0xabc2f180)usecase(1: low-latency-playback) devices(0x4)
    10-27 02:16:56.225   382  5329 D audio_hw_primary: start_output_stream: enter: usecase(1: low-latency-playback) devices(0x4)
    10-27 02:16:56.225   382  5329 D audio_hw_extn: audio_extn_get_anc_enabled: anc_enabled:0
    10-27 02:16:56.225   382  5329 D audio_hw_primary: select_devices: out_snd_device(4: headphones-regulation) in_snd_device(0: )
    10-27 02:16:56.225   382  5329 W msm8974_platform: Codec backend bitwidth 16, samplerate 48000
    10-27 02:16:56.225   382  5329 D hardware_info: hw_info_append_hw_type : device_name = headphones-regulation
    10-27 02:16:56.225   382  5329 I msm8974_platform: platform_send_audio_calibration: sending audio calibration for snd_device(4) acdb_id(10)
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 10, path =  0
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> send_adm_topology
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> send_asm_topology
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> send_audtable
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> send_audvoltable
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
    10-27 02:16:56.225   382  5329 D ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL
    10-27 02:16:56.225   382  5329 D audio_route: Apply path: headphones-regulation
    10-27 02:16:56.239   382  5329 D audio_route: Apply path: low-latency-playback
    10-27 02:16:56.240   382  5329 D audio_hw_primary: select_devices: done
    10-27 02:16:56.279  6460  6485 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    10-27 02:16:56.281  6460  6485 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
    10-27 02:16:59.436   382   637 D audio_hw_primary: out_standby: enter: stream (0xabc2f180) usecase(1: low-latency-playback)
    10-27 02:16:59.575   382   637 D hardware_info: hw_info_append_hw_type : device_name = headphones-regulation
    Note the "E : No matching library found in path /system/lib/"

    Call volume
    Still not working correctly I guess. I confirm what Dennis (@dhemker) wrote earlier.
    Tried to get some insights with LogCat: https://pastebin.com/evLZcK6x
    dmesg excerpt (this was a second try, so the timestamps are not in sync): https://pastebin.com/2UfwRVfA

    And here's how the same device behaves on CarbonRom (latest Oreo build): https://pastebin.com/v6236UMj
    Volume is lower during earpiece mode, and switching between the modes works smoothly.

    Hope that helps to get a understanding what might be misconfigured.
     
    Last edited:

    liberteus

    Senior Member
    Jan 17, 2009
    93
    12
    You should just flash my twrp-3.3.1-0.4 from post #2 as described there (fastboot flash recovery twrp.img). You just have to be in fastboot mode, it doesn't matter on which ROM you were previously. After you flashed it you can hold power and volume down button from powered off device to boot into twrp. If you can't flash it with fastboot somehow I would need the output from your Terminal if possible.
    Good luck!

    I understand the procedure, and that's what I tried to do to not avail. I always received "remote dtb" error message using fastboot, and in the end I somehow managed to softbrick the z3c (I pushed latest LOS16 removing the 1st line checking for the phone version using total commander on the phone, flashing with 3.2.3).

    I found a ftf that worked (tried 4 different ones), and then flashed 3.3.1-0.4 and LOS16. Everything works but coming from CR6.1 it's not a trivial issue, searching the forum I found out I'm not the only one. Not saying you're to blame, just saying that it's not just "flash and move on".

    tl;dr
    flash an old ftf version that works (boot to android, enable adbm reboot to bootloader), then flash twrp using fastboot, install LOS16 at the same time and phew you're done.

    THANKS EVERYBODY :D
     

    sabotage154

    Senior Member
    Apr 24, 2011
    113
    7
    Hy, i am on holidays and don't have my z3c with me. But I just did a small test on my Xiaomi Mi 6 running LineageOS 17 and it works together with NordVPN as intended. When I enable the block connection without VPN and disconnect my VPN the network is unavailable.
    So it's definitely not broken on all Custom ROMs. After my holidays (hope they won't end too soon :p) I will check it on my z3c and try to debug if needed.

    hi neo. i see a new version was released for this on 102619. i just wanted to followup with you on the block vnp feature and see if you were able to recreate the issue on your z3c. if you recall i mentioned that the android block vpn wasnt killing the connection when the vpn dropped or was closed. i experienced the same issue on los16 and los17. thank you for this.
     

    NeoArian

    Recognized Developer
  • Nov 25, 2017
    1,242
    2,790
    Sony Xperia Z2
    Sony Xperia Z3 Compact

    Xcl4m4t10n

    Senior Member
    Jan 25, 2017
    53
    5
    Starting with your phone powered off, hold both the power and the volume down buttons. When your phone vibrates (as if it was being turned on), release the power button. Some 5 seconds later, release the volume down button. TWRP should come up.

    Sent from my Xperia Z5 Compact using XDA Labs

    OFC that's not the problem :D.
     

    hchauvet

    New member
    Oct 29, 2019
    3
    1
    I tested the new build. When starting a call, call volume can indeed be adjusted from low to max. When turning loudspeaker on and then off again, call volume stays at maximum and can't be adjusted anymore. Furthermore, the sound is still kind of crackling. In contrast, in call sound quality from early August build was crystal clear. Is it possible to record call logs or stuff to isolate the bug/misconfiguration?

    Dennis

    I have the same bug, the call volume is very loud and the sound is crackling (the bug is still present with the last build of 20191028). I forgot to test the radio on the last build sorry but it was not working on the previous one.
    I've try with the CarbonROM CR-7.0 and I have the same bug.

    Thanks for developing this ROM :good:
     

    Mr.Tom_Tom

    Senior Member
  • Feb 16, 2008
    146
    177
    Munich
    Thanks @Mr.Tom_Tom for the log, the problem should be fixed now.

    Just tested this build (lineage-16.0-20191028-UNOFFICIAL-z3c.zip) but still FM not working for me (same error message), and earpiece volume in calls is still quite high.

    Anything I could help with?

    That simple workaround was what I used together with your ArianK16a/android_hardware_broadcom_fm repo to enable the FMRadio in LOS17 for the Z3.
     

    Xcl4m4t10n

    Senior Member
    Jan 25, 2017
    53
    5
    Yeah the fix wasn't included yet. GPS works fine.

    Then why it works perfectly on stock rom and, after installing LineageOS, it stop finding me on maps? In fact:

    - Wiped everything.
    - Installed stock rom.
    - Tried GPS. Working fine.
    - Right after that flashed this ROM (the last build).
    - GPS is not working.
     

    NeoArian

    Recognized Developer
  • Nov 25, 2017
    1,242
    2,790
    Sony Xperia Z2
    Sony Xperia Z3 Compact
    Then why it works perfectly on stock rom and, after installing LineageOS, it stop finding me on maps?
    Am I god? Honestly what do people imagine what projects like this are... If something in this completely free open source project does not work for you go fix it and push it to the Gerrit server or keep it for yourself, you are not forced to publish your code, like we do, of course. If you are not able to do this on your own you could friendly ask for help and provide as much information as possible about your problem and steps to reproduce. And if you did this still noone is forced to fix it for you. So please keep this in mind and rather create a proper report so that people can help you IF THEY ARE IN THE MOOD TO DO SO.

    Edit: thanks for adding information to your post. How have you tested GPS? I tried SatStat from FDroid and it connects to GPS satellites fine, also gets a fix.
     
    Last edited:

    Xcl4m4t10n

    Senior Member
    Jan 25, 2017
    53
    5
    Am I god? Honestly what do people imagine what projects like this are... If something in this completely free open source project does not work for you go fix it and push it to the Gerrit server or keep it for yourself, you are not forced to publish your code, like we do, of course. If you are not able to do this on your own you could friendly ask for help and provide as much information as possible about your problem and steps to reproduce. And if you did this still noone is forced to fix it for you. So please keep this in mind and rather create a proper report so that people can help you IF THEY ARE IN THE MOOD TO DO SO.

    Edit: thanks for adding information to your post. How have you tested GPS? I tried SatStat from FDroid and it connects to GPS satellites fine, also gets a fix.

    IDK in what mood did you read my question but it seems you read it a really bad mood. I was just asking a question, I am not demanding anything. Precisly what I am doing is assking friendly for help. You surely to need to calm down mate...

    Anyway I was trying exactly SatSat right now and, in the map tab, it shows nothing. I click on my location button and still nothing but a blue background.
     

    NeoArian

    Recognized Developer
  • Nov 25, 2017
    1,242
    2,790
    Sony Xperia Z2
    Sony Xperia Z3 Compact
    IDK in what mood did you read my question but it seems you read it a really bad mood. I was just asking a question, I am not demanding anything. Precisly what I am doing is assking friendly for help. You surely to need to calm down mate...
    Well no. I was in a pretty good mood, i just returned from sports after i received the mail from xda with your "friendly" question (go read it again, if that's friendly in your opinion i can't help you). Apart from that i don't understand why you recommend me to calm down. I don't see how i was not calm in my reply. I'd still recommend you to rethink the way you talk to me currently but in general people doing something volunteer.

    Anyway I was trying exactly SatSat right now and, in the map tab, it shows nothing. I click on my location button and still nothing but a blue background.
    Well that still doesn't help as you can probably imagine. As i said it works for me. You could get a logcat and share it so we can find out if something crashes.
     

    tomKater

    Member
    Jul 29, 2014
    32
    6
    Huawei MediaPad M5 Lite
    Honestly what do people imagine what projects like this are...

    Once again, thank you for spending time and providing us with these rom's.
    Everyone knows (or should know) that adapting a custom rom is not easy and obviously we can not expect everything to work perfectly as on an (old) stock rom.
    It's already a feat to be able to have this stability with one of the latest version of android on our Z3C...
     

    Xcl4m4t10n

    Senior Member
    Jan 25, 2017
    53
    5
    Yes, whatever. After installing gApps (mini) GPS works again both in google maps and in the browser. Maybe that gives you any kind of hints or maybe I was doing something wrong (in Z5C without gapps and using official lineageos there where no need of gaps to run everything).
     
    Status
    Not open for further replies.

    Top Liked Posts

    • There are no posts matching your filters.
    • 57
      0aSPzXe.png

      Code:
      /*
       * 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.
       */
      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.

      Images
      Here are some Screenshots of this ROM.
      bOQ82bf.png

      DNrD93e.jpg

      8RZsTTU.jpg

      APeLLBj.png

      OGSBS0p.png

      i9Bs8wZ.png

      yDNON6C.png

      dysZUA3.jpg

      nIOSrmT.png

      Rpr8xvm.png


      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 instructions
      Prerequisites:
      • Unlocked Sony Xperia Z3 Compact
      • Fastboot drivers to install TWRP
      • Micro-USB Cable to connect your phone to your computer
      Install:
      1. Reboot to TWRP. *
      2. Wipe cache, dalvik cache, data and system.
      3. Format data to get rid of encryption.
      4. Install ROM.
      5. Install 9.0 Gapps for ARM. **
      * recommended TWRP: Post #2
      ** optional

      Update:
      • Get the latest build
      • Boot into TWRP
      • Flash the downloaded build
      • Reboot, if you don't wipe system backuptool will handle to reapply your modifications, for example: GApps.

      Changelog
      Code:
      Changelog 2019-10-07
      * Fixed offmode charging at Wall chargers (previously bright screen)
      * Fixed offmode charging at computers (previously reboot loop)

      Old Changelogs

      Code:
      Changelog 2019-10-06
      * Fixed camera for everyone
      * Set media volume steps to 25 and voice call volume steps to 7
      * Actually use our cache partition, previously we were using a link to /data/cache instead of mounting the cache partition as /cache
      * Cleanup of rootdir scripts
      Code:
      Changelog 2019-08-28
      * Rolled fingerprint back to Sony's 5.1.1 fingerprint
       -> safetynet CTS check works again
      * Set original shipping API level to KitKat
      * Minor cleaning
      Code:
      Changelog 2019-08-14
      * Singificantly improved GPS
      * August Android Security Bulletin
      * Cleaned, script generated vendor
      Code:
      Changelog 2019-08-05
      * Attempt to fix ANT+
      * Added settings to control the camera button
      Code:
      Changelog 2019-07-08
      * July Android Security Bulletin
      * Rebased Linux 3.4.113 Kernel
      -> Solved video recording lags with Snap
      Code:
      Changelog 2019-06-15
      * Fixed Audio problems
      * LED Notifications work again
      * Manual Network selection fixed
      Code:
      Changelog 2019-06-07
      * June Android security Bulletin
      * LED seems to work with notifications now
      * 4.0 Audio HAL -> NO, this does NOT fix our problems :/
      Code:
      Changelog 2019-05-10
      * Enforcing sepolicy
      * Fixed sensors
      * Fixed FM Radio
      * Fixed EXFat, sdfat and vfat
      * Camera works fine
      * May Android Security Bulletin
      * Sound seems fixed - Maximum Volume still decreases still after a few seconds when using internal speakers
      Code:
      Changelog 2019-05-06
      * Fixed AudioFX
      * Fixed Camera
      Code:
      Changelog 2019-04-24
      * Fixed Notification LED
      Code:
      Changelog 2019-02-19
      * Fixed GPS
      * Fixed Video Playback
      Code:
      Changelog 2019-01-09
      * Fixed Bluetooth


      Downloads
      Download the ROM

      Sources
      DEVICE:
      https://github.com/z3c-pie/device_sony_z3c
      https://github.com/z3c-pie/device_sony_msm8974-common
      https://github.com/z3c-pie/device_sony_shinano-common

      KERNEL:
      https://github.com/z3c-pie/kernel_sony_msm8974

      Addons
      OpenGapps
      Magisk
      SU-Addon

      Thanks
      Whole LineageOS Team for this amazing ROM
      @rcstar6696
      @Myself5
      @drakonizer
      @tomascus
      @koron393
      @nailyk
      @SpiritCroc
      I hope I haven't forgot anyone :)

      Bugs
      WHAT'S BROKEN
      • 4K Video recording doesn't work in stock camera, but works for example in OpenCamera.
      • You tell me.


      FAQ
      Q: Why i can't reboot into the recovery from advanced reboot?
      A: Because you have installed Magisk 19.1 which breaks it. Keep up to date here: https://github.com/topjohnwu/Magisk/issues/1418
      - fixed by @Myself5 since 2019.05.20

      XDA:DevDB Information
      [9] LineageOS 16.0 for z3c, ROM for the Sony Xperia Z3 Compact

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

      ROM OS Version: 9.x Pie
      ROM Kernel: Linux 3.4.x

      Version Information
      Status: Stable
      Current Stable Version: lineage-16-20190510
      Stable Release Date: 2019-05-10

      Created 2019-01-05
      Last Updated 2019-10-10
      14
      Good evening, i guess it's time to share an Android 10 build.

      It is uploading to: https://sourceforge.net/projects/ephedraceae/files/z3c/testing/

      currently bluetooth doesn't work.
      Huge thanks to @koron393 who updated the camera shim to Q sources that fast.

      I wouldn't recommend to use it yet if you actually use your phone, there could be some bugs but it's a great proof of concept for now :D

      Have fun tasting Android 10 on z3c!
      13
      Good evening everyone!

      So i have been doing this LineageOS 16 for Z3 Compact since the 5th of january and it's already more then the half of a year. I think it's time to say thank you to you all. Working on this device is so much fun (it repressed my Xiaomi Mi 6 in my spare time) and also the communication is working just great through XDA at this point. Thanks that you help with testing, contribute with fixing bugs or just listing them or even donating some money to me. We really have a community here i enjoy to work with :) I have spent too many nights while doing stuff here but i never regretted it or had the feeling it wasn't worth.
      I hope that we can continue this project in future and keep this five years old device alive as long as possible. This also motivates me to get a new screen for my 2nd device. I guess i will go with the one @StarGeneral shared.
      In the near future i will also sharea new twrp compiled within an android-9.0 environment as already mentioned here: https://forum.xda-developers.com/showpost.php?p=79892993&postcount=3
      Right now i am stuck on the decryption but i am pretty optimistic that we can get this work, apart from this it seems to work fine. If anyone wants to look at the minimal tree, here it is: https://github.com/z3c-pie/twrp_device_sony_z3c

      However i can tell that there won't be any updates within the next two weeks because i am going on holidays finally :)

      Have a nice time
      13
      Short update about Android 10/LineageOS 17 for Xperia Z3 Compact: Bluetooth and the camera after a reboot has been fixed. I will go through a checklist tomorrow and see about remaining problems, it seems pretty good already so I guess that I can share another build tomorrow.
      Good night!
      11
      TWRP 3.3.1 for our z3c out of an Android 9.0 environment!

      Changes:
      Code:
      3.3.1-0.4-z3c
      * Fixed fastboot boot
      * Added bootlogo
      * Dropped TWRP App

      Code:
      3.3.1-0.3-z3c
      * Fixed encryption when security patch level doesn't match the recovery's
       - [url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/411862532c247aea2c7b48d52aa596b40305e9ea[/url]

      Code:
      3.3.1-0.2-z3c
      * Added a script to handle the CPU
       -> increased the battery life significant ([url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/63f864068ad2f17ae2f1202b4edc311d74e2803d[/url])

      Code:
      3.3.1-0.1-z3c
      * Fixed time
      * Further Clean up's

      Code:
      3.3.1-0-z3c
      * Switched from Android 6.0 to Android 9.0 environment
      * Completely reworked tree
      * Working decryption


      The latest build is attached to this post.
      Old builds are available here: https://sourceforge.net/projects/ephedraceae/files/z3c/twrp/
      Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-9.0

      How to install this build:
      • Rename the downloaded twrp image to twrp.img
      • Reboot to fastboot by holding volume up while connecting your device to your computer
      • Open a terminal and move to the directory with TWRP in it
      • Type
        Code:
        fastboot flash recovery twrp.img
      • Boot into TWRP while the device is powered off press the power and volume down button

      Feel free to ask questions or give feedback about TWRP here .

      Have a nice day!

      Additional information about the recovery on this device:
      First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0

      To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.

      According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
      However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm

      So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.

      I hope i presented it clearly and in the right way,
      Have a nice day!

      EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
    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