I have done some tests. It looks like expected. If i update from LOS 16 to 17.1 the MAC always changes. If i wipe /data before the MAC keeps the same. But with wiping data an update makes no sense.... So something on data results in that problem, but i don't know what. Any ideas?
[OFFICIAL] LineageOS 17.1 for z3c
- Thread starter NeoArian
- Start date
I have done some tests. It looks like expected. If i update from LOS 16 to 17.1 the MAC always changes. If i wipe /data before the MAC keeps the same. But with wiping data an update makes no sense.... So something on data results in that problem, but i don't know what. Any ideas?
Solution found. I removed the folder /data/vendor (after backup) within twrp. While rebooting this folder is automatically recreated. Now the MAC keeps the same.
So ... how to install LOS updates? It made a note that an update is avaiable. I download it (around 480MB), select install and it informs me it will reboot into Recovery to install it. So it reboots, does some stuff and then i'm, in TWRP ... and now what? What does it expect me to do? Reboot to system just brings me back to TWRP. Fo i have to do a Factory Reset?
Sorry if these questions are stupid, but it really isn't straight forward for some people (stupid ones like me).
And now the Google Apps are gone :-/
Sorry if these questions are stupid, but it really isn't straight forward for some people (stupid ones like me).
And now the Google Apps are gone :-/
Last edited:
It should boot to TWRP, automatically flash update zip and boot to system, all without any user input. If it didn't, then you most probably have wrong twrp flashed. Please flash the one in the first post and try again. This updater process is just automated dirty flashing of downloaded zip, so gapps and data won't be removed.
But i did: I have TWRP 3.3.1-0 from the link in this sentence: "If you prefer TWRP over Lineage recovery, you can get it here."
Then maybe you have initially flashed the zip incorrectly (didn't fully wipe partitions and/or didn't format them before flashing)? I don't really know what could be the issue here other than the things I already mentioned. Last possible but very unlikely couse of the problem could be corrupted zip after downloading or this particular build is just faulty, after merging some changes done to lineage's sources. To confirm or bust this hypothesis you would need to start over from flashing twrp from first post, wipe all partitions and format them accordingly, flash last working for you los, and then install update through updater in setting app. If it fails again and you stay in twrp, please copy the twrp logs, so I (if the problem is some step you overlooked) or most likely @NeoArian (if it is broken build) can help you.
Hi all
I'm currently on the concept software I think is MM 6.0
Im trying to figure out if switching to this new OS worth the effort or not.
I'm looking for a reliable and fast os, actually mine is getting slower, probably because of the three years without a factory reset.
I really need an advice, I'm still using my z3c as main smartphone because of his compact dimensions and I'm trying to give him a second chance with this os.
I'm currently on the concept software I think is MM 6.0
Im trying to figure out if switching to this new OS worth the effort or not.
I'm looking for a reliable and fast os, actually mine is getting slower, probably because of the three years without a factory reset.
I really need an advice, I'm still using my z3c as main smartphone because of his compact dimensions and I'm trying to give him a second chance with this os.
Hi Everybody,
Big problems of sound in the last build flashed today (lineage-17.1-20201013-nightly-z3c-signed.zip). No notification, no music, no ringing. No sound too when I plugged an earphone.
When a call comes in, micro is on mute and unable to unmute. Not possible to hear the caller too.
Seems to be related with the last build because I flashed the 3 october build again. With this build I have sound (but phone is not usable unfortunately).
Is there anyone else in the same situation ?
Big problems of sound in the last build flashed today (lineage-17.1-20201013-nightly-z3c-signed.zip). No notification, no music, no ringing. No sound too when I plugged an earphone.
When a call comes in, micro is on mute and unable to unmute. Not possible to hear the caller too.
Seems to be related with the last build because I flashed the 3 october build again. With this build I have sound (but phone is not usable unfortunately).
Is there anyone else in the same situation ?
Last edited:
Same here. I don't really use the z3c as a daily driver, but I don't remember this issue in previous builds.
Same here. Reverted back to the version from 06.10. which is working without any problems.
Interesting. Can you tell me what you did exactly? I flashed 0610 with twrp too but after reboot I couldn't unlock my phone...
I also flashed 0610 with twrp over 1310 and wiped cache/ dalvik. Nothing more. And it worked afterwards.
Unable to unlock phone
Hello,
I have the same problems like tomKater. After flashing to 1310 build there where sound issues (no sound at all during phone call and playing music etc.). After flashing back to 0610 with TWRP and wiping cache/dalvik I was able to unlock my phone with SIM-Pin but not with number-based unlock code. Screen went black after correct PIN-input and shows the Dial-Pad again. Any Ideas to break this unlock-Pin loop?! Nevertheless this is a great ROM - thanks to NeoArian.
Hello,
I have the same problems like tomKater. After flashing to 1310 build there where sound issues (no sound at all during phone call and playing music etc.). After flashing back to 0610 with TWRP and wiping cache/dalvik I was able to unlock my phone with SIM-Pin but not with number-based unlock code. Screen went black after correct PIN-input and shows the Dial-Pad again. Any Ideas to break this unlock-Pin loop?! Nevertheless this is a great ROM - thanks to NeoArian.
May be thats the difference. I use only sim code, no additional screen lock. This worked with 0610 after rollback.
Sound problem after flashing the 10th October build
Exactly the same problem of sound for me after flashing the 10th October build.
Any idea of what we can do to ? Just come back to the 3rd October build ?
Thank you for you help
Exactly the same problem of sound for me after flashing the 10th October build.
Any idea of what we can do to ? Just come back to the 3rd October build ?
Thank you for you help
I´ve updated again to 1310 build from 0610 build. Afterwards unlocking with unlock-code works again but the sound issues occured again. Trying to remove unlock screen-code and than flash back to 0610.
I tried too this steps :
- Flash in 1310 build
- disable lock screen
- Flash in 0610
=> still doesn't work. I swipe to unlock the phone and black screen. So at this moment I'm back in 1310 build and use a bluetooth headset for calls (this is the only way to communicate). I hope that there will be a fix very soon because it's my daily driver ...
Same problem, after upgrading to the latest build no sound at all.
Downgrading to the October 6th build fixed all issues.
Downgrading to the October 6th build fixed all issues.
Same behaviour with disabled lock-screen after downgrad like tomKater described in his post. But also bluetooth headset is not working in 1310 build after reflash.
You are right. On my side, music is ok with bluetooth headset. I thought that calls would work too but they don't.
Very annoying.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4Thanks to everyone for the really detailed testing I really appreciate it.
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
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?
Pretty extensive "basic testing"!
- 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
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!1Hello, 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]!1Since 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. -
10Good 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
Introduction
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
Security
Longevity
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-1255
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.4GOOD 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.
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
- rebootCode:fastboot flash boot boot-BTLowPower-fix-3.img
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