yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Compact Android Development] lm089:
Yep, I'm running the Gapps version, that might be the cause for whatever.

Having writte my above observations I did some slight tweaking in installing a script that reduces WiFi when the phone is not in use and since then I'm down at 0.7% / hour. So this goes to show that some app must be in constant contact with its mothership (most probably some google app, there's not much more on my phone).

So I withdraw my statement and declare the opposite :p
[Xperia Z1 Compact Android Development] tramp20:
[MENTION=8036586]115ek[/MENTION]

Thanks for the new build :)

The updater of lineage-17.1-20200311-UNOFFICIAL-amami-signed does not find the new lineage-17.1-20200315-UNOFFICIAL-amami-signed.
[Xperia Z1 Compact Android Development] 115ek:
I know and I already wrote how to circumvent this. Please read the post carefully :)
[Xperia Z1 Compact Android Development] tramp20:
Sorry, excuse me, it was too early this morning.
[Xperia Z1 Compact Android Development] JIJOK:
[MENTION=8036586]115ek[/MENTION] Hi, maybe this can count as off topic, but wondering .... you said you are not using gapps, are you using microg ? or something else ?
[Xperia Z1 Compact Android Development] 115ek:
Yes. No gapps, no microg. Only essential app is FDroid. I install Aurora from there if I need anything from playstore (but I try to avoid that). Many apps from the playstore are also working without google services / microg. But there are also some known to be not working. But in that case I don't really want them on my phone.

To be honest: what do you need google services for? In most cases it's laziness/comfort I guess.
[Xperia Z1 Compact Android Development] JIJOK:
I always believed that google services were needed for all apps and the only alternative was microg, +400 mb added to my storage lol, thank you very much !!!!
[Xperia Z1 Compact Android Development] nikson7912:
when a stable build
[Xperia Z1 Compact Android Development] tramp20:
[MENTION=8036586]115ek[/MENTION]

what shall we do with lineage-17.1-20200328-UNOFFICIAL-crackling.zip?

No changelog, no OTA update .
[Xperia Z1 Compact Android Development] 115ek:
Nothing if you don't own a Wileyfox Swift aka crackling.

I'm not just building for amami ;)

Thats why the builds are sorted after the scheme "DEVICE/MAJOR_VERSION/actual zips". So for you only amami/LineageOS_17_signed is of interest.
[Xperia Z1 Compact Android Development] darkangel32:
Hej, i'm new here to XDA. I'm having a Z1C (limegreen), it's on stock. I just like the xperia phones, in special the somewhat older ones, like the Z1 (compact). Many say i should buy an iphone (used too), since their OS is supported/updated longer, but for one i don't like IOS so much, nor apple. They are rather expensive even used.

'problem' is that the Z1C (or any older xperia) that they are bound to an old android version, limiting apps to installfrom the store. I wonder then, if i would (and succeed) installing this custom android 9 or 10 ROM, are you able to install apps that require latest android versions?

Will you get most of the android 9/10 features to a Z1C? Does a Z1C with android 9 or 10 match an iphone 5s?

The Z1C can record inn 4k or 720 120fps ive read (after rooting), is this still possible with a ROM like this?

Lastly, is it hard to mod/install custom roms? Any good guides?

thx
[Xperia Z1 Compact Android Development] 115ek:
If you install an android 9 or 10 you're of course able to install apps requiring android 9 or 10.

And yes, you'll get all features of android 9 or 10 onto your Z1c. All limitations are listed in the OP. If you're fine with them - give it a shot. Your phone needs to be unlockable though. Check that first.

Regarding camera: yes, 4k is possible. But I think 720 framerate was lowered to 60fps. You'll find a list of supported modes here.

This xml is also the place where you can change it to 120 fps again if you like to.

I guess the hardest part is installing a custom recovery. Once you have that, everything is pretty straight forward. AICP and lineage 16/17 also support OTA updates so you won't have to do anything in the future. Just clicking install update and you're done. You can orient on the installation instructions here. Just use a modern TWRP instead the mentioned one.
[Xperia Z1 Compact Android Development] darkangel32:
Okej, thanks alot for the answer. Going to read into it more. Older xperia phones like the Z1/C can be found rather cheap used, it's an incredible value with people like you putting work in those devices :)
[Xperia Z1 Compact Android Development] darkangel32:
Another question, will one keep the Sony UI when installing android 9 or 10?
[Xperia Z1 Compact Android Development] 115ek:
No, of course not.

You'll get a (nearly) stock android UI like on google pixels or android one devices. Check the screenshots in the OP. And there are so many videos and screenshots out there showing how lineage looks.
[Xperia Z1 Compact Android Development] LazyT:
What's the problem, any chance to fix in the future or impossible?

My mother would like to scan this sensor but it fails. Don't know if hce is needed.

Maybe someone is using this?
[Xperia Z1 Compact Android Development] 115ek:
To be honest: I don't know how hard it is to fix. It needs research and a strong will. As I don't use it, there's no real desire from my side. But I'd be happy if someone wants to contribute :)

Anyway: I don't think you need Host Card Emulation (HCE) at all.

Maybe the problem lies somewhere else:

Has she ever used NFC successfully?

Is NFC activated? Else it won't work.

Does the app has the proper permissions to use NFC?

Was the device near enough? NFC stops working after some centimeters...
[Xperia Z1 Compact Android Development] LazyT:
Ok, thanks.

I tried it myself. It detects the sensor in the first step, but that's all. Maybe more luck with the new generation, have to wait 3 weeks...
[Xperia Z1 Compact Android Development] 115ek:
Don't give up that fast ;)

At first I'd eliminate SE problems. That can easily done by setting SE to permissive.

You need to enable adb access with root in developer settings (remember to revert that afterwards!).

Then connect your device to PC and use

adb root

and

adb shell

to jump on the device. With

getenforce

you can see the current SE state, with

setenforce 0

you'll deactivate it (permissive mode). Once done, retry the NFC connection. A reboot will reset the SE state to enforcing as it is passed as a kernel commandline parameter.

If that doesn't help create a bugreport. Reproduce your problem, then use developer options-> bugreport to create a report. Check it yourself or upload it here.
[Xperia Z1 Compact Android Development] LazyT:
Thanks, no change: one beep if the sensor is detetced, and then spinning time wheel.

For me it looks like the firmware is missing:

and then it crashes at sensor detection:

Sorry that's the wrong thread (it's unfortunately still los 16, have to update to los 17 sometimes after corona ****)... :(
[Xperia Z1 Compact Android Development] 115ek:
Well, the firmware lies under /vendor/firmware/libpn544_fw_c3.so. So what I'd do is a dumb copy and check what happens.

LOS 16 or 17 doesn't play a role here.

Get onto your device with root access, do a

mount -o rw,remount /

and a

cp /system/vendor/firmware/libpn544_fw_c3.so /system/vendor/firmware/libpn544_fw.so

and check the logs again.

Then he should at least be able to load the shared object :rolleyes:
[Xperia Z1 Compact Android Development] LazyT:
Nope, sorry:

Missing path /system/vendor/firmware?
[Xperia Z1 Compact Android Development] 115ek:
Hmm. You copied it? Or moved? We need to figure out who loads which libraries.

strings "your binary/lib"

can give some clue here. There are some other debugging tools around... strace, readelf, ldd and even more.

For me

strings libnfc.so

contains/vendor/firmware/libpn544_fw.so so I guess he tries to load it. That's why I'm a bit confused by your error. :rolleyes:

EDIT: I just grepped /system for "libpn544_fw.so" and the ouput was: Binary file app/Nfc/Nfc.apk matches Binary file lib/libnfc.so matches

But

strings lib/libnfc.so

didn't contain it.. Maybe I overlooked something.

It's like a puzzle :D
[Xperia Z1 Compact Android Development] LazyT:
I copied.

In my opinion everybody should get these errors when enabling nfc, you don't?

It has nothing to do with the app for scanning the sensor, it wasn't started at this time.

Looking in the firmware there is also "libpn544_fw_C3_1_41_SP.so", maybe this lib is missing?
[Xperia Z1 Compact Android Development] 115ek:
Yeh, I'm going to check that. However NFC works for me. Just tested my canteen ID and it worked, so I didn't look into logs so far ;)
[Xperia Z1 Compact Android Development] LazyT:
Found this, but the sed doesn't change anything. After reboot same error.

Thanks for your time... :)
[Xperia Z1 Compact Android Development] tramp20:
You should test with the new german "Personalausweis" and the https://play.google.com/store/apps/details?id=com.governikus.ausweisapp2 :)

This is the reason why I still have a Android 5.1.1 smartphone.
[Xperia Z1 Compact Android Development] LazyT:
Clean install, but camera doesn't work.

Log shows only

04-12 15:36:56.043 10158 10158 D CAM_Activity: snapdragoncamera_version: 2.02.037 (eng.schild.20200315.115212-30)
04-12 15:36:56.045 10158 10158 V CAM_Activity: Start Request Permission
04-12 15:36:56.046 1284 2461 I ActivityTaskManager: START u0 {flg=0x4000000 cmp=org.lineageos.snap/com.android.camera.PermissionsActivity} from uid 10057
04-12 15:36:56.054 10158 10158 V CAM_Activity: onCreate: Missing critical permissions.
04-12 15:36:56.225 7529 7529 V GrantPermissionsActivity: Permission grant result requestId=-3156022215227045292 callingUid=10057 callingPackage=org.lineageos.snap permission=android.permission.WRITE_EXTERNAL_STORAGE isImplicit=false result=1

All permissions granted.

OpenCamera works.

Thanks!
[Xperia Z1 Compact Android Development] 115ek:
Yeh, already did that. We need extended length support therefor. However I don't know how we can fix that. And I haven't looked deeper into it so far.

I can't reproduce this issue with a clean build of the latest 2020-03-15 version. Do you use gapps / magisk any other modifications?

Try deleting the app data under: settings->apps&notifications->camera->storage&cache->clear storage

Anyway that's strange :rolleyes:
[Xperia Z1 Compact Android Development] alfrix:
Did a clean install

Faster than lineage 14 (i was a bit out of date XD )

USB OTG works, tested with a usb drive

Microphone works ok in calls, but at a very low level on videos or audio recorder

Thank for this, stay safe
[Xperia Z1 Compact Android Development] 115ek:
New build with latest lineage sources and April ASB's is up. It'll also be shipped via OTA.
[Xperia Z1 Compact Android Development] lm089:
As always: many thanks for providing updates.

Is it just my impatience or is there possibly something wrong with the OTA feature? Made my local updater check but am told that there aren't any updates available.

No harm done, really. But I can easily wait a bit in case you would want to check things
[Xperia Z1 Compact Android Development] 115ek:
No. Actually not. I just tested it again. What build are you currently on?

Can you check the content of /system/build.prop ? You should find this line:

# OTA
lineage.updater.uri=https://raw.githubusercontent.com/115ek/OTA/lineage-17.1/amami.json

If there are still problems please get a logcat after searching for new updates and upload it here.
[Xperia Z1 Compact Android Development] lm089:
Build number says:

lineage_amami-userdebug 10 QQ2A.200305.003 eng.schild.20200311.183828

Checked build.prop:

the value was there, but the key (lineage.updater.uri=) was missing, weird.

Will try to get a Logcat, but will have to charge the battery first

=========

Solved: after editing build.prop I decided to reboot. After that OTA worked.... :eek:
[Xperia Z1 Compact Android Development] 115ek:
My fault. I remember the problem. I already wrote about it some weaks earlier ;)

Just didn't think there are still people on this old build :)

Sorry.
[Xperia Z1 Compact Android Development] lm089:
I remember having read this, then apparently forgot it right away. Never mind
[Xperia Z1 Compact Android Development] colaigor:
Hello. Im planning to use my z1c as secondary phone and i need ok rom for it. Should i go for AICP 10 or LOS 10? I see releases come out about same time so i assume they are more or less the same with different skin on top, is that right?
[Xperia Z1 Compact Android Development] 115ek:
Hardware functionality is completely same. All bugs are same. Both have OTA updates.

So yes, only difference is the look and feel. While AICP has more things to configure, Lineage is a more "clean" approach.
[Xperia Z1 Compact Android Development] jho55:
Yesterday I have read that the kernel of this rom is forked from SpiritCroc ones and they include also security patches. Also I think that you get more responses here. Also they still support older versions as long as there are new los builds. With AICP if they switch to a higher los version the older versions are not supported anymore.

But of course SpiritCrocs and any other contributors work is highly appreciated.
[Xperia Z1 Compact Android Development] SpiritCroc:
Make sure to check the weekly official builds on the AICP website :)

But probably the wrong topic to discuss here...
[Xperia Z1 Compact Android Development] tramp20:
Sorry, I was looking every day here: https://androidfilehost.com/?w=files&flid=302281

And in your thread https://xdaforums.com/sony-xperia-z...ment/rom-aicp-15-0-q10-0-amami-t4005457/page2

no single word of a new build :(

Thank you very much for developing this ROM.
[Xperia Z1 Compact Android Development] jho55:
Font in app drawer is distorted.

I have a strange problem with the font in the app drawer. Some texts under the icons are looking distorted. When I open one of the affected apps and go back to the drawer it seems to be fixed for that app. But after some open and close app drawer it appears again. Really wierd. Does anybody know hot to fix it? I could not find anything via google search.

I did a clean install. No gapps etc.

First image it looks good. After first opening app drawer I think. Second image shows the bad rendering after I open app drawer again.

https://ibb.co/tPYYv0v

https://ibb.co/jZV0HV0
[Xperia Z1 Compact Android Development] 115ek:
I also experience this issue. Even on another device. I guess it's launcher related as AICP doesn't show this behaviour.

However, I don't really know how to debug this and I consider it not being a really huge problem.

Anyway, thanks for reporting.
[Xperia Z1 Compact Android Development] jho55:
I tested it on two phones. In AICP latest weekly from today I also have this issue. I guess it is LOS related and we have to wait for a fix. Even font changing in AICP did not help. I guess there is something broken with the font renderer. It is like the cached version is broken.
[Xperia Z1 Compact Android Development] 115ek:
If someone has some minutes left: Could you take some wifi speed measurements? With and without using bluetooth. Is there any difference? And how are "settings/locations/wifi and bluetooth scanning" settings affecting the situation?

Edit: It would also be interesting if gapps are installed or not.
[Xperia Z1 Compact Android Development] lm089:
Los 17.1, with gapps Pico, using wifi @ 5Ghz. Did 4 measurements in each situation (bt on/off). Settings... was OFF at first. Result:

Absolutely no difference.

Then tested again with Settings... = ON. Again 4 measurements each

Now there were same differences:

With bt ON there was a big decrease for the upstream by ~60% in 3 of 4 cases but only ~ - 10% downstream. The 4th measurement was again like above

With bt OFF there was an upstream decrease again by ~60% in only one case,the other 3 cases were [MENTION=1412615]100%[/MENTION]. Downstream again was @ ~ - 10%
[Xperia Z1 Compact Android Development] jho55:
Los 17.1, no gapps, Wifi 2,5Ghz: Bluetooth on (no device connected) decreases the down speed significantly, upload not. Same behaviour for me like in Los 16.
[Xperia Z1 Compact Android Development] 115ek:
Thanks for you input.

I guess wifi @ 2.4 GHz interferes with BT so the datarates decrease. 5 GHz wifi should be less influenced.

The google location settings lead to wifi and bt being used although they're actually turned off. So a decrease is comprehensible.
[Xperia Z1 Compact Android Development] 115ek:
New build with latest lineage sources and May ASB's is up. It'll also be shipped via OTA.
[Xperia Z1 Compact Android Development] 115ek:
I've got good news:

Thanks to [MENTION=6614989]jason972000[/MENTION] GLONASS is usable now. Furthermore, and I guess that's even better, the GPS week rollover is no longer a problem. Timestamps are now correct.

Fixes are here and here.

If the things work as intended, they'll also get included in LOS 16 with the next update.

The new build is rolled out via OTA update.
[Xperia Z1 Compact Android Development] cbix.de:
MIDI transport

Can we please have MIDI enabled in this ROM? It's supported since Marshmellow but not enabled here. See source.android.com/devices/audio/midi#transport
[Xperia Z1 Compact Android Development] 115ek:
Well, the problem is I can't really debug nor test it. Or do you know any good method not requiring special equipment?

Besides that it should be possible. Just for reference. As far as I can see we'd need to:

enable the right kernel configs

claim MIDI support by copying the midi permission xml

write the right USB config to sysfs

Anyway - no device to test, no development. :(

Any ideas on that? Maybe it's possible to send MIDI messages from android to the connected PC or something like that. I have to admit I've got no idea of midi. :confused:
[Xperia Z1 Compact Android Development] cbix.de:
Sure, I was actually gonna write a longer article some day on this because many ROM builders don't really care about USB MIDI and audio while it's actually super easy to activate (a few kernel flags and permission XMLs) and for the people who use it (like me) it increases the device's value a lot! Also USB headsets are getting more common and they won't work unless USB audio is enabled in the kernel config.

So, here's some of the really simple ways to test:

Connect device to USB port, then tap the notification that lets you select a USB configuration (MTP, tethering, charging...). If "MIDI" shows up here, it's a good first sign.

Install apps from Phil Burk's MIDI Test Suite (he's the guy at google working hard on making Android an option for pro audio since ~ M), links to play store are in the README, or simply that repo into Android Studio to compile it yourself. If the selection dropdown in these apps says "none", Android doesn't support MIDI. If it says "----", it should.

With the MidiKeyboard and MidiScope apps from the test suite in split screen, you can test if framework internal MIDI is working

To test the USB MIDI connection, open the MidiKeyboard app, connect USB to a computer, select the USB MIDI configuration as mentioned above. "amidi -l" (on Linux) should now show the Android device as a MIDI controller, with "amidi -p hw:4,0,0 -d" (change the port to whatever amidi -l says) you can dump the output when playing with the MidiKeyboard test app as long as you change its output to USB MIDI port.

Testing BLE MIDI can be a bit harder but not really important as it should actually work out of the box as long as the framework support is active (see the developer.android.com link I posted earlier)

If you feel experimental, take 2 Android devices and connect them with each other through OTG, then on the USB client device select USB MIDI and open different apps from the test suite to send MIDI data in either direction ;)

For USB audio, you can connect a USB sound card via OTG and play sound from the phone.

I'm also still not sure if it's really just not activated by default in the LineageOS sources or if kernel builders just turn it off... Will need to investigate more into this :P At least in AOSP the MIDI support is usually more reliable than in custom ROMs.

(That said, with devices shipping with Treble and not having these kernel options enabled by default, I was having a really hard time with custom ROMs because the builders didn't touch the kernel at all :D)
[Xperia Z1 Compact Android Development] 115ek:
Hey. Thanks for your detailed information. Most people asking for features don't come up this way.

In the meantime I made some quick tests and uploaded an experimental build here. I applied these changes.

amidi -l

works as intended.

amidi -p hw:*,0,0 -d

also displayed messages sent by MIDI Keyboard.

It would be really awesome if you can do further tests. I think you're more an expert in this field ;)

Maybe you could also use real hardware devices?

Looking forward to your insights. :)
[Xperia Z1 Compact Android Development] cbix.de:
Haha, I know... To me it's just another great Open Source project and whenever I find bugs or ways to contribute I try to help out within the limits of my resources. But even though I used to build CyanogenMod and AOSP ROMs for personal use back in the days, it was easier to just post the request here ;) And thanks for regarding it and building it, I will test it ASAP! As soon as I find more time I will set up a ROM building environment again.

MIDI, in and of itself, is actually quite simple (not regarding MIDI 2.0 that came out just this year after 3 decades) on the protocol layer that's relevant to the OS. Short: if USB MIDI works with one device in sender and receiver mode, respectively, it will work with any hardware controller or synthesizer that supports the standard, so there's no need to do any crazy testing if it works with the official test suite. One popular use case is actually the Android device being used as a control surface for any software running on a computer, without the need of any drivers or proprietary protocols (hence the USB MIDI configuration). All these sensors and the touchscreen opening up more possibilities of expressive music making etc.

Update: ok I did some tests. Works: USB MIDI, OTG MIDI, OTG audio, Doesn't work: BLE MIDI? with permission error in the log:

Will test again tomorrow :D Yeeea, no. I somehow was working with an outdated version of the midi testsuite that was missing this update, a simple pull fixed it.

Audio latency is not perfect but that's nothing we can fix that easily. Low-latency process scheduling involves optimizations in many places of the kernel, drivers and framework, so it's usually some vendors doing a really good job compared to others. See this index or this benchmark for example and some audio sample apps. My tests yield 150 ms compared to 30 ms on my Galaxy S5 running LOS 16. I know all this has little to do with your ROM but you were asking for insights ?
[Xperia Z1 Compact Android Development] 115ek:
Improving this would be nice. Maybe you find some time for tinkering with it? For me it's not really a priority, but I'm definitely open for contributions. :good:
[Xperia Z1 Compact Android Development] cbix.de:
Audio isn't that much of a priority for me, either, at least currently. The Sound quality on my device isn't that amazing anyway. But like I said it's probably a lot more work to improve it and optimize it, I'll look into it whenever I get a custom kernel setup working. The MIDI part is easy to do and I'm super happy to have it now, thanks again! ?
[Xperia Z1 Compact Android Development] jan_de:
Internal SD-card not mounted on reboot

Hi,

I installed LineageOS 17 yesterday on my Xperia Z1 compact. Great to have such a modern OS on quite an old device! :)

Nevertheless I have a little problem: The internal SD-card stays unmounted while booting the OS. I get an error message like "SD card of SanDisk missing" (translated into english by myself). After manually ejecting the card and new inserting in the card slot the card is recognized and mounted.

This happens on every reboot.

Can anybody confirm this? And is there a way to avoid it?

Thanks a lot,

Jan