I have just tried to encrypt my device with a pin and it worked as expected.
Could you maybe try again or get some logs so that we can look further into it?
Also, as Serf95 told you, it's worth a try to flash the latest stock firmware again before trying it.
We are looking into the screen lock issue. Was the GPS behaviour better from builds which are older then a week? We have merged some GPS patches.
z3c:/ # tune2fs -l /dev/block/mmcblk0p25
tune2fs 1.43.3 (04-Sep-2016)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p25
1|z3c:/ # e2fsck -f /dev/block/mmcblk0p25
e2fsck 1.43.3 (04-Sep-2016)
/dev/block/mmcblk0p25 is in use.
e2fsck: Cannot continue, aborting.
I'm coming from carbon rom 8.1.0, flashed this clean with gapps nano, but back camera is not working. Also from time to time the device freezes and no messages coming in anymore. Only a hardreset helps.
The version is the latest from november. Is it a buggy version or is it my only error?
Thanks for the help!
Ok, so I did more tests on latest LOS 17.1. What I discovered is that MMSes are working but only when mobile data is DISabled, which is super weird.Hi everyone!
About back camera problem - from my experience if is not working, in order to fix it you have to flash latest firmware using Emma and then flash recovery + rom.
And going to the main point of this post - MMSes are not working.
I tested latest build of LOS 17.1 (lineage-17.1-20201110-nightly-z3c-signed.zip) to check if it will resolve the issue (it didn't).
I decided to do the whole procedure from the grounds up, to make sure MMSes aren't working not because of my fault.
- I flashed latest firmware using emma.
- I tried sending and receiving MMSes on stock MM (success).
- I flashed twrp-3.3.1-z3c-20200212.img recovery.
- I flashed just lineage-17.1-20201110-nightly-z3c-signed.zip, without magisk and without gapps.
- I booted to system, turned on mobile data and tried to send MMS (failed to do so).
- I tried to receive MMS (also failed to do so, I only get message, that there is MMS available for download but it can't be downloaded. I is downloading forever until it stops and says that the message can't be downloaded.)
At this point I was sure it isn't my fault. I checked APN settings and took screenshots of the configuration (didn't change anything, just took ss).
I remembered that MMSes had been working before, with custom ROM on my device. I checked older versions of LOS 17.1 but they have the same issue.
I have one of an old UNOFFICIAL 16.0 build from you @NeoArian, saved on my computer. I gave it a try.
- wiped system, data, cache
- flashed twrp recommended for LOS 16.0 - twrp-3.3.1-z3c-20200212.img
- flashed lineage-16.0-20190510-UNOFFICIAL-z3c.zip, without magisk and without gapps
- booted to system, turned on mobile data
- tried sending and receiving MMSes and ........... IT WORKED ON A FIRST TRY
I checked APN setting on LOS 16 to compare them with configuration from 17.1 and they were exactly the same.
Now I am sure that MMSes are broken on LOS 17.1. Could you @NeoArian give it a look?
They were working on your unofficial builds of LOS 16, so you may know or remember how to fix it :fingers-crossed:.
Thanks in advanced.
Ok, so I did more tests on latest LOS 17.1. What I discovered is that MMSes are working but only when mobile data is DISabled, which is super weird.
- just wifi enabled - receiving/sending MMSes works (at first time I tried it with just wifi, the notification came up, that asked to grant permission for downloading MMSes via wifi. I granted it and MMS was downloaded successfully).
-just mobile data enabled - receiving/sending MMSes doesn't work at all. It is sending/receiving them until error, just how I described it in previous post.
-mobile data and wifi is enabled - receiving/sending MMSes doesn't work at all. It seams that mobile data has higher priority, so even though that wifi is working, it tries to use mobile data and fails to do so and when it fails it doesn't fall back to wifi.
-mobile data and wifi is DISabled -receiving/sending MMSes works :silly:. It is extremely weird, since it wasn't working last time i tried it with this configuration. It may be that since last time I have tried, I have given default messaging app every possible permission, disabled battery optimization, enabled unlimited data usage of mobile data and wifi and in roaming etc. After that when I try to send or receive MMS and have wifi and mobile data disabled it works. While sending/receiving MMS I can see data transfer indicator in the middle of status bar. I think that the messaging app sees, that there is no internet and since I've gave it every possible permission, it uses mobile data to send/receive MMS, even thought it wasn't enabled by hand, by me. In this scenario, mobile data must be used for sending/receiving MMSes, because there is no other option for messaging app to fall back.
So here is my thesis describing the MMS bug:
When mobile data is enabled by hand by a user, messaging app can't send/receive MMSes, even thought the internet is available. When none internet is available, messaging app enables mobile data automatically, just to receive/send MMS and then it works (mobile data isn't "turned on", it doesn't show any sign of it being enabled in QS and status bar. I know it is used only from data transfer indicator, that shows for a few seconds while MMS is being sent/downloaded). It seams that the app mistakenly tries to enable mobile data automatically, even thought it is already enabled, so it fails and stops, so at this point it never reaches the part of actual sending/receiving MMS.
With this information it should be easier to fix the issue, because now we know, how the environment must be configured for it to fail.
I would like to know if it happens to anyone else on the latest LOS 17.1 - and if it happens - I would like to know if edge cases I described in this post, check out to your situation.
So you are saying that you can have wifi turned off and mobile data turned on, at the same time and after that you can successfully receive and send MMSes - am I getting it right? I would be very glad if you could try this exact scenario for me just one more time, to make sure every possible scenario is working for you. If that's the case then good for you. I still can't receive MMSes while having mobile data turned on manuallyHello,
I have done few more tests, and after restoring default APN, I can now receive and send MMS with WiFi ON or OFF and mobile data ON or OFF
So you are saying that you can have wifi turned off and mobile data turned on, at the same time and after that you can successfully receive and send MMSes - am I getting it right? I would be very glad if you could try this exact scenario for me just one more time, to make sure every possible scenario is working for you. If that's the case then good for you. I still can't receive MMSes while having mobile data turned on manually
Hi, I tested this quickly without success. I tried 3G, it didn't help, so I went back to 4G, enabled wifi and mobile data. Then I disabled "Mobile data always active" in dev setting (I had it enabled in previous tests). After I disabled it, I could send and receive MMSes on wifi+mobile data or just mobile data, untill I've disabled wifi and mobile data. After reenabling mobile data, I again couldn't send nor receive MMSes. I think that this option in dev settings is causing problems with MMS that won't send nor receive using mobile data enabled by hand.Here are the last tests I have done (Airplane mode OFF, 4G/LTE):
- WIFI OFF / mobile data OFF : OK (sending and receiving)
- WIFI ON / mobile data OFF : OK (sending and receiving)
- WIFI OFF / mobile data ON : KO (sending and receiving) with 4G/LTE network at first time, BUT if I switch to 3G/H, it works! Could you please check by yourself with this test (1st attempt in 4G/LTE failed, then switch to 3G/H as "preferred network" and see what happen) ? try to"force stop" the SMS/MMS app before switching from 4G to 3G. Not sure if it still works after switching back to 4G (one of my attempt was OK, one other failed so I don't know what to think , I don't remember if I "forced stop" the SMS/MMS app before switching back to 4G)
- WIFI ON / mobile data ON : I don't know. Behaviour is really strange. Sometimes it works, sometimes it doesn't. I think it depends on what is the first network enabled (Wifi or Mobile data) after disabling "airplane mode".
Hope it helps.
If I can help too : about the camera stock issue : I encountered this problem too when I flashed my Z3C from scratch (while previously I have used this build with no problem). I had to flash several times (and immediately testing the camera) before stock camera works again. No idea why.
Maybe this can help.
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
I also noticed that the Assertive Display function, which worked on the stock firmware, does not work on LineageOS 17.1. Regarding brightness, I noticed that the firmware only has 255 brightness levels, while the stock firmware has 4096 levels.Hello! I am using the latest official version of LineageOS 17.1, and I noticed that the minimum screen brightness is much higher than the minimum brightness on the stock firmware. What could this be related to and will it be fixed? The same problem was on LineageOS 16 (also official builds)
Magisk 20.4 flashable zip, can be updated to the latest via the app, but it seems versions after 20.4 do not survive LOS updates. Magisk app v.22 is fine@pawloland Thanks for answering! I successfully backed up my DRM keys using "Universal (Dirtycow-based) TA Backup v2" which was very easy to do and didn't even need rooting the device prior.
*EDIT* I successfully installed this ROM now, all looking good so far. What's the recommended method to root this LineageOS ROM?
*EDIT2* Well, the enjoyment with the device only lasted for a very short while since I now discovered that SD-cards won't click-in into the Z3Cs reader. Appalling quality control at Sony, attention to detail traditionally only to their DRM systems :-( I'll try to get a replacement device from the seller, so my question above regarding how to root best is still valid.
You have a PM... For all others: there's still a microG version (only a bit older) on https://download.lineage.microg.org/z3c/Hi, it might be a bit off topic.
I just tried 17.1 on my z3c and noticed that some of my apps for work do not work on Android 10, so I wanted to go back to 16.0 but i don't have the zip file anymore. As I could not find a recent download for 16.0 I wanted to ask if someone still had recent version?
I think I had lineage-16.0-20200901-nightly-z3c-signed.zip (I think it was the last 16.0 Version) so if someone could upload it or point me to a download link it would be very appreciated.
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.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.
SecurityCustomization 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.
LongevityYour 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.
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.
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.Yes, that's right.
When Safe Start is turned on, the accelerometer does not work. Therefore, screen rotation, light sensor does not work.
fastboot flash boot boot-BTLowPower-fix-3.img