Oh my god, I thought I pressed that button, but I only disabled "Choose colors automatically" instead *facepalm*, thanks though!
After installing version 11, it is not possible to return to android 10. I installed stock firmware, tried to put 17.1, but the phone just restarts, freezes, etc. I tried various combinations all day, only 18.1 works. For what reason did it happen? Yes, I also changed the TWRP versions. Without success.
I did everything except this step. I just did the wipe, then installed 17.1 LOS. I will do as you wrote, thank you very much for the detailed explanation.- Boot TWRP.
- Advanced - ADB Sideload. Tick the checkboxes and swipe.
- Sideload the LOS rom (adb sideload <LOS zipfile>)
- Sideload OpenGapps if you want them (ARM64, 10.0, whatever variant you want) (adb sideload <OpenGapps zipfile>). You'll have to enable ADB sideloading in TWRP again before flashing.
- Reboot phone to Android. Hopefully it works now. Do whatever configuration you want. Restore backups. Install SD card again.
Same problem here,date and time is always the time from the first start after flashing, changes about one minute later when phone has fully booted.Has anyone else faced issues where the phone shows the wrong date/time on startup?
On a fresh boot, the time is 9:58am on Saturday 18 September. It stays like this for approx 15 seconds until it finally updates to the current time (using network sync).
However, if I keep the phone on airplane mode, the time stays wrong until I disable airplane mode.
I'm wondering if this is a bug
I'll update this post if and when I have more information.
- with the most recent version of the ROM (I'll try with last month's version as well)
- with the GApps package I'm using (I'm using the mini package which replaces stock clock with google clock)
Update 1: Reflashed the September ROM with a smaller GApps package (micro instead of mini) and date/time issue still shows up. So GApps and the Google Clock isn't to blame. I'll try August ROM and see what happens.
Update 2: Flashed the August ROM and the datetime issue still persists.
Update 3: I'm attaching steps on how to reproduce this and I'd be really interested to see if anyone else is able to reproduce this:
- Make sure your phone's time is currently normal/correct
- Put phone into airplane mode
- Reboot phone
- Time should now be wrong on startup
- Disable airplane mode, time should now be updated once network connectivity is back
I uploaded the new versions. If you could give the 18.1 a try and check if safetynet passes it would be great. If it does not send me the output of `adb shell getprop` and I'll rebuild with a fix as required.Excellent! I'd be happy to test both Casting and Safetynet for the October version of 18.1 for you. Sounds like I may be re-flashing August anyway if I can't get this worked out, so its not like I'm risking much Shouldn't be a problem to dirty-flash a version with an earlier build date, right? I wouldn't think TWRP would care.
(Feel free to send me an email or DM with your beta version of October 18.1, if you don't want to release the untested verion publically yet @Flamefire and I'll test Safetynet immediately)
I don't have a chromecast to test and no idea where to start looking for the issue... Is there anything in the logcat that may hint at the issue? Maybe compare the output for the working and broken version to see if that turns up anything.After updating to the September 18th version of 18.1 I've found that Chromecast no longer works on this device. The Cast device search works correctly but hangs upon actually trying to connect. Tried with an original release Chromecast and a Chromecast Ultra, and they both exhibit the same issue. It was working on the August 11th version of 18.1.
Can anyone reproduce this issue? Is Casting working for you on the September 18th version of 17.1 @Flamefire ? In any other situation, I would just downgrade, but my retinas are very grateful that the Sony logo is dimmed on the phone's startup now and I don't know if I can go back lol
No only 17.1. Basically building with the same compiler as 18.1 which has better optimizations (3 versions difference) and found a few bugs through that...
I'm using an XZ1C with 17.1 myself and am keeping that updated as much as possible. This includes security patches and kernel patches and updates. I also included some stuff I need for myself (e.g. the SafetyNet fix w/o Magisk to use GooglePay) But I'm not really doing any development, e.g. adding new features beyond that.