yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Themes and Apps] Izzm:
how can i change the sort order in HTC Album?

first image in preview is the last in explorer and so on

i would like to have it sorted upwards
[Tilt, TyTN II, MDA Vario III Themes and Apps] sonus:
You probably have an old build of HTC Album. The stock build on my HTC Touch Cruise zoomz very easily (via touch screen and jog dial). I once tried an XDA build, but found that gestures would often cause rotation when I wanted to zoom, and zoom when I wanted to rotate.

As for videos, HTC album does preview them, but when you click on it, it opens them in Windows Media Player. Is this the behavior that you experience?

You could try the new HTC album floating around from the Opal/Manilla 2D.
[Samsung Galaxy S10+ Guides, News, & Discussion] tazin_dium:
Hello everyone,

I have rooted my S10+ using Magisk manager and stock samsung SW. but now when Samsung releases security patches every month, how do I install them on my phone while preserving root and user data?

so I follow the same workflow as initial root, but with HOME_CSC?

or do I follow do magisk uninstall-OTA update-Magisk reinstall method?

if I missing something obvious, please excuse me. This is my first time.
[Samsung Galaxy S10+ Guides, News, & Discussion] PlutoDelic:
You rooted the stock rom, so to update:

1. Reflash the new release through odin

2. Reflash TWRP

3. Reflash magisk.

Not sure if sideloading update.zip would work, as i havent tried it.

Might be better off with a Stock based Custom Rom.
[Samsung Galaxy S10+ Guides, News, & Discussion] tazin_dium:
Ok so for any one who run into same situation like mine, I did the update to latest sock FW and ti was quite straight forward.

1. Download new stock FW using Frija

2. Transfer the new AP file to phone and patch using Magisk.

3. ADB pull the patched tar file.

4. Flash this tar file as AP along with BL, CP and HOME_CSC.

Update complete.
[Xperia Z1 Compact Android Development] 115ek:
reserved
[Xperia Z1 Compact Android Development] 115ek:
Thanks @koron393 camera is working now :)
[Xperia Z1 Compact Android Development] 115ek:
New build is up.

08.12.2020

fixed screenlock

Furthermore I updated the manifest and build instructions - just in case someone wants to build from source.

It would be nice if you can share your experiences, so that we can complete the status list.
[Xperia Z1 Compact Android Development] jho55:
I have already mentioned it in the 17.1 thread but I think it is also good to post it here:

The bad font rendering from 17.1 is gone in this build.

https://xdaforums.com/showpost.php?p=82417295&postcount=91
[Xperia Z1 Compact Android Development] tramp20:
I will wait until I can find and download GAPPS.
[Xperia Z1 Compact Android Development] koron393:
BiTGApps

https://xdaforums.com/t/custom-gapps-bitgapps-for-android.4012165/
[Xperia Z1 Compact Android Development] tramp20:
I tried already this link but they have server problems since 9 days :-(

MOD EDIT: Link Removed

Perhaps someone can upload these GAPPS to Onedrive, DropBox or GoogleDrive.
[Xperia Z1 Compact Android Development] koron393:
Search the xda thread carefully!:)
[Xperia Z1 Compact Android Development] tramp20:
Thanks.

This one?

https://xdaforums.com/t/custom-gapps-bitgapps-for-android.4012165/post-84094855
[Xperia Z1 Compact Android Development] 115ek:
New build is up:

Lineage 18.0 -> Lineage 18.1 (android-11.0.0_r17 -> android-11.0.0_r19)
[Xperia Z1 Compact Android Development] -FancyUsername-:
I will share a few first experiences with the build of 19.12.20:

- GPS and compass seem to work (Google Maps constantly crashes, Waze does show the right location and the compass moves when I move the phone. But I can't say for sure if it's maybe just using other sensors and Wifi for that)

- FM Radio : yes (can't judge the quality)

- Microphone : yes

- bluetooth audio : yes

- NFC : greyed out in the control center

Other:

- runs pretty fast for such an early version actually that was a lie, because it runs pretty fast for any version

- once got stuck on the Sony logo, which was fixed by holding power + volume up

- when I used the restart option from the power off menu, when it turned back on it was really slow and the screen flickered slightly. that happened just once though, so probably nothing to worry about
[Xperia Z1 Compact Android Development] tramp20:
@115ek

thank you for this new ROM.

1. I have only installed BitGAPPS, but in the settings of Play Store I see "device is not certified".

Of course I deleted memory and cache of Play Store (was updated already) and Play Services.

2. Long pressing the power button does not show sreenshot, only power off and restart.

3. Restart to Recovery goes to Lineage Recovery and not to TWRP. How to change this?

I had already flashed TWRP again in fastboot mode.

It seems that TWRP has gone :-(
[Xperia Z1 Compact Android Development] tramp20:
Has someone successfully installed/flashed Magisk 21.1 and when yes how?

I can flash it without errors but nothing is really installed, no Magisk framework and no Manager :-(
[Xperia Z1 Compact Android Development] 115ek:
The google certification algorithm changes from time to time and your phone can be classified as "not certified" at any point of time. I'm no gapps user, so unfortunately I can't give any tips here nor know what consequences this certification state really has.

That's a lineage framework thing and most likely will change in the future.

That's also a thing forced by lineage. During the setup wizard you'll now be asked if you want to update the recovery. Don't check this box if you want to keep TWRP. Else you'll end up with lineage recovery.

I hadn't had a look into magisk yet. I'm just using root over adb for development purposes. Going to check that if I find some time.
[Xperia Z1 Compact Android Development] tramp20:
@115ek,

thank you for all answers.

To lineage recovery : I found this already after some tries, this check box should not be pre-activated.

I saved the TWRP recovery.log after installing the latest Magisk-v21.2.zip.

But nothing is really installed, no Magisk framework and no Magisk Manager :-(

Perhaps you see something in this logfile.
[Xperia Z1 Compact Android Development] tramp20:
@115ek,

I need a stock boot.img of the Z1c to patch it with the Magisk Manager.

All my tries failed: the ROM is always booting fine but neither Magisk nor Magisk Manager are installed.

This is happening with all Magisk >v20.4.

Every boot.img in the Lineage and AICP ROMs are different. Which one can I use?

I have TWRP backups from Android 5.1.1 but I don't know how to extract the boot.img.

Edit:

In the meantime I could extract the kernel.elf from the original firmware tft and convert this file with Android Image Kitchen to a boot.img. But this is ~ 2 MB bigger than yours in your ROM.
[Xperia Z1 Compact Android Development] 115ek:
New Build is up:

using snap camera now (instead of camera2)

fixed NFC (thanks @AdrianDC)

Not a the first sight, unfortunately.

Earlier versions work fine?

None. The kernel needs one specific commit, pre-11 kernels don't have. Else it won't boot.

Besides that, you'd have to add a androidboot.selinux=permissive to the kernel command-line as this 11 build is still permissive.
[Xperia Z1 Compact Android Development] tramp20:
Yes, all up to 20.4.

The same problem exist with lineage 17.1.

A happy new year to all and thanks for the builds.
[Xperia Z1 Compact Android Development] tramp20:
You could try to delete the directory /data/credmgr and reboot!

I
[Xperia Z1 Compact Android Development] gibar7:
I'm having an issue with echoes for the other part when using loud speaker for the call. It looks that echo cancellation is not working. Anyone hitting the same problem?
[Xperia Z1 Compact Android Development] 115ek:
I'm not using speaker mode at all so I didn't notice it on my own. However, I think you're not the only one who hit that problem.

Something came to my mind directly https://github.com/lin18-microG/android_device_sony_rhine-common/blob/lineage-18.1/system.prop#L3

These props are definitely outdated.

I'll have a look into that topic in the next time.
[Xperia Z1 Compact Android Development] ArgenAbdimajitov20:
Hello, I have been using this rom for a week now, I noticed two errors:

1)Very often, video recording with a stock camera does not work, and it works on another application.

2)The status bar in dark mode takes on a black theme, while everything else is dark.

I apologize for my english.
[Xperia Z1 Compact Android Development] MSe1969:
New builds with January 2022 ASB patches

Hi all,

new builds with the January '22 ASB patches (Security String 2022-01-05) are available and should be offered already as OTA update through the Updater app:

A. Standard LineageOS 18.1 build

https://sourceforge.net/projects/lin18/files/amami/LineageOS_18_signed/lineage-18.1-20220122-UNOFFICIAL-signed-amami.zip/download

B. Pre-installed microG build variant with additional security patches

https://sourceforge.net/projects/lin18/files/amami/LineageOS_18_signed/lineage-18.1-20220122-UNOFFICIAL-microG-signed-amami.zip/download

@115ek - please update OP/Changelog

Happy flashing, regards, M.
[Xperia Z1 Compact Android Development] micke1989:
Hi all,

I tried to install this ROM today, but I only get "Signal: 7" errors. I have the latest TWRP (twrp-3.4.0-1-amami.img) and have tried the two latest releases with the same result.

Another intresting detail is that after I've attempted to install, I can no longer find my SD card in TWRP. After poking in the mount menu, I managed to get it back so I could save the logs.

I did fail to install TWRP on my first attempt (possibly due to bad USB drivers on my Ryzen system), but I managed to recover the phone with Emma on a different computer - so I ought to have the latest firmware.

Does anyone know where it went wrong and how I can get it to work? I have attached the log file from TWRP.

Spoiler content hidden.

/Mikael
[Xperia Z1 Compact Android Development] 115ek:
How did you install the twrp? What was installed before? A sony stock firmware?

To exclude issues with the sdcard itself I'd recommend flashing with adb sideload. To be sure, completely remove the sdcard.

You need adb installed on your host PC.

You need the lineage zip on your host PC.

Boot into TWRP recovery.

Connect your phone via USB.

Enter sideload mode in twrp (Advanced -> ADB Sideload)

On your PC run

adb sideload /path/to/zip/on/PC
[Xperia Z1 Compact Android Development] micke1989:
I tried adb sideload, but when it reached 47% it stopped - twice. Some googling suggested that this was just a bug and that it had actually succeded, since it also reported "no errors". I tried to install gapps, but it failed....

So I started exploring your comment about issues with the SD card, and managed to find the old one I used when I flashed my old HTC Sensation (so I knew it had at least worked once for flashing). With that one the flashing succeded, but gapps still failed. It turned out that I had downloaded the arm64 version. So once I got the correct one it all worked fine, and I have now probably flashed the rom correctly 3 times without knowing it...

Thanks a lot for your help!
[Xperia Z1 Compact Android Development] 115ek:
Yeah, adb only shows the progress for uploading the firmware to the device. The actual installation progress on the target itself is not shown as progress. So you just have to wait until the sideload command finishes.

Anyway - nice to hear that you had success. :)

Concerning the sd card: You could reformat it and give it another try. But if there are further issues you should probably just throw it away and get a new one.
[Xperia Z1 Compact Android Development] cris3:
Hello, I write about the lineage version 16, I have a problem with whattapp, that is, it allows me to send a single photo, but if I prey and send several together, even a piu different users, some photos send them and others not, some appears the clock as when they have not left, and sometimes app crashes in sending the group of photos, I reinstalled whattapp but without things having changed, is there a solution? Thank you
[Xperia Z1 Compact Android Development] 115ek:
Sorry, but lineageOS 16 is no longer supported by us. Please use the latest version (18.1).
[Xperia Z1 Compact Android Development] MSe1969:
February 2022 ASB

Hi all,

when you have a closer look at the LineageOS 18.1 ASB 02.2022 topic, you will notice, that all patches were already part of last January build. Hence for this month, there won't be any new builds. Stay tuned for next month.

Cheers, M.
[Xperia Z1 Compact Android Development] Dystinato:
Hi,

Recently I installed this ROM on my Z1 Compact and prior to the install, I made a full OTA update of the original ROM. I used the installation instructions from the 15.1 thread and everything went smooth except for launching TWRP with hardware buttons, I had to use "fastboot boot twrp.img" to launch it.

After updating I am sadly no longer able to make stable phone calls. I have attached a logcat which has been cut down to a period in which I made a call which was interrupted after 20-30 seconds. After the interrupt, the phone could no longer find any network and after a short period I was prompted for a pin to unlock SIM. After network was re-established, I called again and was interrupted again after 20-30 seconds, but this time the network was re-established without typing a pin after about 10-20 seconds.

I hope someone can help me fix this issue.. :)

EDIT: Could not attach text file, attached ZIP instead..
[Xperia Z1 Compact Android Development] 115ek:
That sounds like you do not have the latest bootloader and/or somehow the TWRP installation was not successful. Maybe check https://xdaforums.com/t/recovery-testing-amami-twrp-3-2-1.3759450/ for details (the twrp is deprecated, but the first post could still have same helpful information for you).

Thanks for the log. That is the first step to get something fixed. And indeed - I can see multiple crashes of the rild (radio interface layer daemon). If that service is not working as intended you'll definitely end up with a non-functional call/sms/mobile data functionality.

I'll have a look in the next time.
[Xperia Z1 Compact Android Development] 115ek:
It took longer than expected but I finally got the stock audio HAL working (at least some sound is working). On the shinano platform (Z3/Z3c) which is also 8974 based, the developers switched back to use sony's audio HAL instead of an opensource one. The reason for that is, that in the open source audio HAL we can't easily enable "fluence" - the active echo cancellation technology of qualcomm. However, sony implemented something similar on their own and that's what we can get with the stock HAL.

I uploaded a testbuild here: https://sourceforge.net/projects/li...FICIAL-amami-signed_audiotest_v1.zip/download

This is only intended for testers (standard build only)! Before merging anything into the "stable" builds I'd like some other persons to test it.

You can also install it via the inbuilt updater if you set some property:

adb root
adb shell setprop lineage.updater.uri https://raw.githubusercontent.com/lin18-microG/OTA/testing/amami.json

Then it should show up in the updater. After installation, the updater url will point to the stable lineage-18.1 channel again.

For now it seems system sounds and fm radio are broken. But maybe someone could test if the echo cancellation works better now. And if there are further problems.

If you feel like a tester and are on the standard build (not microg!) feel free to share your experiences.
[Xperia Z1 Compact Android Development] traegr:
Hi all, so I have the LineageOS 17.1 that stopped updating after Jan 2021 and I somehow never got round to flashing any more updates. I noticed that recently i keep getting a notification that my Seedvault is backing up and it's been going on daily for a week now. I guess maybe it's just time to upgrade once and for all...

1) Is it ok to dirty flash when upgrading from 17.1 to 18.1? I use this as my daily driver so there's a bunch of apps and data i'd rather keep. What do I have to untick for a dirty flash?

2)) I currently have gApps pico, do I have to flash that again after flashing the new version of the OS?

3) I probably need to install TWRP again. Isn't 3.6.0 the latest version or should I use the link on the first page?

Thanks in advance!
[Xperia Z1 Compact Android Development] 115ek:
Yes, dirty flashing is possible easily if both the following things apply:

you do not switch the buildtype (e.g. staying on "standard" version)

your phone is not encrypted

Please check the upgrade instructions in this posts. It should clarify what has to be done, also in case your device should be encrypted. https://xdaforums.com/t/eol-rom-uno...eria-z1-compact.4007983/page-22#post-85414427

Taking a backup of course always makes sense.

Dirty flashing basically means you only wipe /system and the caches. It does NOT touch /data in any way.

Yes. Directly after flashing the new lineage (without any reboot!) you have to flash the new gapps package. You need to use a gapps package for Android 11 arm architecture.

There is no need to install a newer TWRP (there is no 3.6.0 for our device which I'm aware of).

Just stick to this one: https://xdaforums.com/t/recovery-unofficial-amami-twrp-3-4-0.3960699/
[Xperia Z1 Compact Android Development] traegr:
Yeah it's just a standard build without encryption. And I have to remember to uncheck the box for 'update recovery', otherwise I'd lose my TWRP again lol

Thanks for clarifying the dirty flash. Some threads suggest not wiping anything at all, some only the caches so it's good to know I should wipe /system too.

Yeah I got confused by the TWRP versions and even Gapps arm (arm vs arm64) architectures for different devices so my bad! (I'm trying to flash a Samsung A5 too but z1C is both less complicated and more well-maintained imho).

Thank you so much again for your efforts and prompt support!
[Xperia Z1 Compact Android Development] 115ek:
Well. To be precise: you do not need it here, because when installing an update package the following code is run to flash the system partition:

block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");

See META-INF/com/google/android/updater-script for details (if you unzip the update package).

That basically means the image is flashed block-based so it doesn't matter what was on the partition before. Depending on your updater script it could however be required to wipe /system (e.g. when the installation is just unpacking a zip or something like that).

For more infos check out: https://source.android.com/devices/tech/ota/nonab/block

EDIT: But wiping /system also doesn't hurt. ;)
[Xperia Z1 Compact Android Development] Dystinato:
Thank you for your reply! :) Since I cannot find anyone else with the same issue, it is probably not very common. Du you think it could be related to a bad installation or maybe an issue with the carrier? Would it make sense to use the Sony Flash Tool to flash a stock ROM and then start over again?

Bonus info: Sometimes I do not get any notification when a text message / SMS is received (nothing on screen, no sound and no blinking LED). The notification is first given when I enter the Messaging app, probably also related to the RILD.
[Xperia Z1 Compact Android Development] 115ek:
You should definitely be on latest stock firmware. Else weird things may happen.

It could also be some problem with the SIM card itself or some hardware problem.

But at first make sure to be on latest sony firmware before any further investigation.
[Xperia Z1 Compact Android Development] gibar7:
I gave it a try, but, unfortunately, the issue with echo still persists even with that testbuild. Anyway, thanks for looking into this at all!
[Xperia Z1 Compact Android Development] traegr:
So I followed all the steps, placed the zip files in an external sd and flashed through TWRP and it was succesful. Then I tried to reboot, it went to the sim lock page and before I could key the code in, the screen shut down and went back to the Lineage loading screen, and it repeated a few times before I manage to quickly key in my code and then it showed my usual background wallpaper with the words 'Phone is starting...' with a progress bar underneath, then it shuts down again and loops back to the Lineage loading screen. It's just keeps looping like that until I shut the phone down (using the very short time window when it's showing 'Phone is starting...' to press on the power button and use the power off function).

Then I waited a bit and switched it on and the same thing repeats. So now I've shut it down again.

And then I went back into the TWRP Recovery and tried to reboot the system from there. Then there was a weird overlay of both the Lineage loading screen and the "Phone is starting' text. Then it goes into a loop again and the screen is now hung on ''Phone is starting..." with a black background and my status bars at the top and navigation buttons at the bottom visible before it goes blank and repeats again.

What have I done wrong? Thanks in advance.
[Xperia Z1 Compact Android Development] traegr:
Ok, so I thought of reinstalling using adb sideload and I also received this same problem of 47% stop. Does your comment mean that it still succeeded since on the phone it says 'adb sideload complete' successful. But does that mean it received only 47% successfully?

I did have a problem with installing fastboot (though adb worked) and through some youtube troubleshooting got the fastboot working

EDIT: I tried reinstalling by putting the zip files in root storage of the phone and again flash is successful but rebooting is not... So it's not the SD card problem. Is it because I have very little space left in internal memory (about 1,08GB left)? But I thought wiping the system would allow the new one space.

EDIT2: Tried again this morning to bootup and decide to wait longer, next thing it boots... into TWRP even though it was a normal boot from the power button

EDIT3: I restored the backup to the previous firmware from an external SD card and it boots up but now my SD card is listed as corrupted and when I try to set to portable storage (as it always was) it prompts me to format it (saying it needs to be "formatted to store apps, files and media" which is the identical warning to setting up as phone storage which I don't want to do and it pops up no matter which option I choose) so I decided to leave it for now (I also have a copy of its contents on my PC). Booting into Recovery still shows TWRP so at least that was not overwritten (it had the Lineage custom recovery previously) and SD card as external SD
[Xperia Z1 Compact Android Development] jurkoman:
Hello, i bought an Xperia Z1 compact from ebay, unlocked bootloader and tested with latest stable LOS 17.1 build.

Rom is working very good.

One weird thing i experienced with, i cant see that blue screen with shaking call on incoming calls, only status bar and navbar. Option for receive incoming call is going to quick settings and answer there.

I saw this also on latest stable LOS 16.0 build.

Because (maybe?):

Proximity/light sensor on my Z1c is working for adjusting brightness, but screen turns off (completely black) after answering an call. Option for turning on screen in call is push power button or camera button longer.

Device had installed latest SW .236

Maybe past user changed display and broked up an sensor. Idk

Question is - that incoming calls screen - it is also related to proximity/light sensor like in-call or it is software problem if it doesnt show properly? Someone experienced with similar problem?
[Xperia Z1 Compact Android Development] 115ek:
Hmm. I'll have another look when time permits.

No idea. To be honest: Your description is a bit unclear to me. I'd say the easiest solution would be a clean flash here.

17.1 is no longer supported. Please use 18.1.

No idea. I can't really understand your problem.