EOL [ROM][Unofficial][9.0][signed][OTA] Lineage OS 16.0 for Xperia Z1 compact

[lingowistico]

Testbuild here

Tested with a 10- and 60-minute delay. Alarm rings on time
Still remains to be seen if I'll be late for school tomorrow, my guess is I won't :good:

 

[CyanoFriend]

Streaming

Hello,

in LOS Oreo WiFi-Direct with a Sony Bravia TV from 2018 is functional.
In LOS Pie the TV is detected, but the connection hangs at "registering".
Same behavior on a Moto G5.
Any ideas?

 

[115ek]

Hello,

in LOS Oreo WiFi-Direct with a Sony Bravia TV from 2018 is functional.
In LOS Pie the TV is detected, but the connection hangs at "registering".
Same behavior on a Moto G5.
Any ideas?

Maybe it's not working

What do you think I can do without any logs and version information? Use my visionary crystal ball?
So please provide logs if you're interested in solving the problem. Or use Oreo if it works for you.

 

[lm089]

Well, I just tried a new build and the issues are gone at first sight (those I experienced with 1702 build).
Maybe you give it a try on your own (would be really nice ) If you report that it works I'll update the thread accordingly.
Testbuild here

I'll test later today. Assume I can do a dirty flash over 2019-02-17, right?

 

[115ek]

I'll test later today. Assume I can do a dirty flash over 2019-02-17, right?

Yes. But wipe /system and the cache partitions

 

[lm089]

Yes. But wipe /system and the cache partitions

I did.
First test results after letting the phone "sleep" for 30 minutes:

• alarm went off on time
• snooze action still not working as expected (see my first post on that)

I'll give it another try letting it sleep for an hour or so. Then I'll try to get some log.
Just to be sure: I've setup my phone through developer options to allow getting system logs through the ON/OFF menu.
Is it sufficient to get logs that way after snooze action failed next time? I don't have a chance to connect to adb using my work pc...

Update:
at least after an additional hour alarm now appears to go off at the desired time.
Snooze however still dows not work. Testing this and creating a log is pretty tricky, though.
I observed something else in this context:
- let the phone sleep for a while waiting for the alarm
- alarm rings and display lights showing the alarm screen >> I snooze it through hw key but don't do anything else, i.e.: display stays locked and the phone goes back to sleep after a few seconds
- after 5 minutes alarm rings again, this time display stays dark and clicking hw keys don't do anything. Clicking POWER ON just lights the display very shortly then goes dark again etc.
The same happens if I don't wait for the second alarm but click POWER ON a few minutes after I snoozed the first alarm: again display goes on for a fraction of a second then goes dark again.
I tried to capture this using catlog app. The result is pretty small so I don't know if the log really contains enough data.
Anyways I think this behaviour has something to do with the fact that the device is locked while something happens, and I don't unlock it but let it go to sleep again. Then next time something happens it does not wake up properly, and I need at least 2 attempts using POWER ON to have it properly react to button actions

 

[115ek]

I did.
First test results after letting the phone "sleep" for 30 minutes:

• alarm went off on time
• snooze action still not working as expected (see my first post on that)

I'll give it another try letting it sleep for an hour or so. Then I'll try to get some log.
Just to be sure: I've setup my phone through developer options to allow getting system logs through the ON/OFF menu.
Is it sufficient to get logs that way after snooze action failed next time? I don't have a chance to connect to adb using my work pc...

Update:
at least after an additional hour alarm now appears to go off at the desired time.
Snooze however still dows not work. Testing this and creating a log is pretty tricky, though.
I observed something else in this context:
- let the phone sleep for a while waiting for the alarm
- alarm rings and display lights showing the alarm screen >> I snooze it through hw key but don't do anything else, i.e.: display stays locked and the phone goes back to sleep after a few seconds
- after 5 minutes alarm rings again, this time display stays dark and clicking hw keys don't do anything. Clicking POWER ON just lights the display very shortly then goes dark again etc.
The same happens if I don't wait for the second alarm but click POWER ON a few minutes after I snoozed the first alarm: again display goes on for a fraction of a second then goes dark again.
I tried to capture this using catlog app. The result is pretty small so I don't know if the log really contains enough data.
Anyways I think this behaviour has something to do with the fact that the device is locked while something happens, and I don't unlock it but let it go to sleep again. Then next time something happens it does not wake up properly, and I need at least 2 attempts using POWER ON to have it properly react to button actions

I'm not able to reproduce your problem - snoozing works fine for me.
What else is installed? Magisk, exposed, other modifications?
May you try a clean installation and see if the problem persists?

 

[lm089]

I'm not able to reproduce your problem - snoozing works fine for me.

Did you try "multiple snooze"? Usually it works well the first time but on subsequent alarms.

What else is installed? Magisk, exposed, other modifications?

Magisk yes, XPosed no.
I'm back at 15.1 now; here I have a Magisk module "Sysconfig Patcher" installed which takes care of battery savings. I'm not sure whether I also installed it on the 16.0 version.
Apart from that I don't run any modifications, no custom kernel or anything.

May you try a clean installation and see if the problem persists?

I sure can, but it could take a few days.

 

[115ek]

New build
11.03.2019

• fixed alarm delay (came with new lineage sources)
• fixed some more offline / USB charging problems (thanks @SpiritCroc)
• synced LineageOS sources (security patch level March 05, 2019)

https://www.androidfilehost.com/?fid=1395089523397912978

 

[lm089]

May you try a clean installation and see if the problem persists?

I simply had to try this right away, but it's almost the same behaviour, I'm afraid.
Here's what I did:
- wiped all caches + system + data
- installed the ROM version you posted yesterday (build 20190311)
- also flashed openGapps pico (build 20190309)
- did NOT flash Magisk
- booted into system, ran basic setup but did NOT install any apps
- enabled developer mode, activated extended restart menu + terminal emulation + log addition to extended menu
- made alarm adjustments as described earlier (snooze time = 5 minutes + max snooze time = 25 minutes + set snooze through vol keys)
- camera and vol keys are NOT set to wake the phone
- enabled screen unlock through pattern, screen locks after 1 minute of inactivity
- set alarm to ring after 30 minutes then let the phone go to sleep

Result:
- when the alarm rang the first time display lit up. Pressing camera button started snooze for 5 minutes. I did NOT unlock the phone
- after 5 minutes alarm rang again, but now screen stayed OFF. Clicked camera button then Vol up, then Vol down, but alarm kept ringing. Clicked POWER ON: now this is different from before, as now screen lights up immediately, and after that I can use any of the hw keys to enter a new snooze period.
I repeated this test for 5 snooze periods with exactly the same behaviour.

Unfortunately at the moment I can't hook up the phone to a pc to get a log through adb. And I did not want to install an extra app like CatLog (meanwhile I'm back on 15.1.
Do you think you need another log? In that case I could try to grab it through developer options, if that makes sense. Just let me know

Update: just ran one more test by also enabling the other options to start snooze (shake and turn over).
Result:
screen still stays dark from 2nd snooze period onwards, and I still can't use hw keys, but shaking the phone or turning it over starts a new snooze period. So at least there's a workaround.
Still this is quite strange.
finally: sorry for repeating this in such detail but I'm still hoping that I'm not the only one experiencing this...

 

[simon-n]

I have had these alarm issues, too. You're not alone

 

[115ek]

I have had these alarm issues, too. You're not alone

You have had? Means they are gone? Issues with alarm ringing too late really should be gone with the latest build.
Or do you mean the snoozing issue I sadly also experienced?

@lm089 As far as I can tell I the problem only comes up after using the camera button to snooze. VOL + and - are working flawlessly.
It may be a problem on lineage side (need to verify this with another 16.0 device maybe) or a simple overlay thing.

Edit: Is it working with 15.1 for you?

 

[lm089]

@lm089 As far as I can tell I the problem only comes up after using the camera button to snooze. VOL + and - are working flawlessly.
It may be a problem on lineage side (need to verify this with another 16.0 device maybe) or a simple overlay thing.

Edit: Is it working with 15.1 for you?

Ok, that's an idea. Can you confirm with using the camera button then?
And: no problem at all with 15.1, nor with munjeni's 14.1 before that. That's I made it a habit to use that button (you know, it's nearly impossible to think about alternatives when the alarm goes of at 6 )

 

[simon-n]

You have had? Means they are gone? Issues with alarm ringing too late really should be gone with the latest build.
Or do you mean the snoozing issue I sadly also experienced?

@lm089 As far as I can tell I the problem only comes up after using the camera button to snooze. VOL + and - are working flawlessly.
It may be a problem on lineage side (need to verify this with another 16.0 device maybe) or a simple overlay thing.

Edit: Is it working with 15.1 for you?

I meant the overall alarm delay. Switched back to 15.1 as this issue together with decreased battery life wasn't a good match for my daily-use phone.
I'm still eager for 16, so I'll test your latest releases once there is some spare time.
Thank you very much for all your effort and please keep up the good work!

 

[lingowistico]

Terribly sorry if this question has been previously raised, but why are almost all my calls showing up as unknown in the call log? Irrespectable of whether the calls are out- or ingoing.

 

[Brozada]

Terribly sorry if this question has been previously raised, but why are almost all my calls showing up as unknown in the call log? Irrespectable of whether the calls are out- or ingoing.

Have you tried with caller ID setting in phone app, settings of your phone provider, or even trying the Google phone app just in case your settings where somehow messed?

 

[115ek]

Ok, that's an idea. Can you confirm with using the camera button then?
And: no problem at all with 15.1, nor with munjeni's 14.1 before that. That's I made it a habit to use that button (you know, it's nearly impossible to think about alternatives when the alarm goes of at 6 )

Yes. I can confirm it. I just tested with AICP 14 and it was working there. So it seems to be a lineage related thing.

Terribly sorry if this question has been previously raised, but why are almost all my calls showing up as unknown in the call log? Irrespectable of whether the calls are out- or ingoing.

That's strange. Are you able to see your contacts? I had quite a few times where I had to import .vcf twice. At first all contacts showed up - but then they were gone. A second import solved the problem. But it seems not to be related to Pie only - also on Oreo I experienced this behavior.

 

[lingowistico]

Have you tried with caller ID setting in phone app, settings of your phone provider, or even trying the Google phone app just in case your settings where somehow messed?

Yes, I've had them all on as well as off. Same thing. I'd rather not use Google's phone app. My provider settings can't be messed up cause the same sim-card works fine and shows all the non-secret numbers normally if I put in a different phone.
Or can they?

It even works on this phone but with a stock rom.

That's strange. Are you able to see your contacts? I had quite a few times where I had to import .vcf twice. At first all contacts showed up - but then they were gone. A second import solved the problem. But it seems not to be related to Pie only - also on Oreo I experienced this behavior.

Yes, I am able to see my contacts. My contacts are synced to my gmail account. You're correct this started with Oreo..

EDIT:
Tested Google Phone. The number I've dialed shows up in history as long as I hang up before there's an actual connection.
Once an audio call connection is established (ie. once I hear the other person) the call will always show up as unknown.
Wtf

 

[karamancho]

I want to use my old phone (amami) as a mp3/video player, with only LOS and no gapps.
Would this rom (being the latest LOS ver.) be suitable for that, or does anyone have something else to recommend?

 

[115ek]

I want to use my old phone (amami) as a mp3/video player, with only LOS and no gapps.
Would this rom (being the latest LOS ver.) be suitable for that, or does anyone have something else to recommend?

Yes, totally. But nevertheless I would recommend our LOS 15.1
It has got a better battery life what may be useful for your use case. In addition LOS 16 isn't really mature in my opinion (although I'm using it as daily driver).
Just test it on your own.
If you've got concerns about security: LOS 15.1 is also updated every month with the newest ASB's - only thing you won't see there are new features.

Edit:
Is aptx important for you? Currently it is not included in our LOS 15.1/16 but I thought about integrating it. Only problem: I don't have got devices to test.