LineageOS, Current status : 16.0 Test Builds

[tdm 2,322]

Alright after all the issues, I have flashed the "official" test3 zip on my device and wiped data.  It works perfectly fine.

 

@SteffenWi have you figured out the virtual keyboard issue?  It works fine for me, from the very start when asked for a PIN on the lock screen.  I just need to press the keyboard icon on the right side of the navbar and select "Show virtual keyboard".  (I will try to make this the default in the future).

 

[mcdinner 375]

1 hour ago, tdm said:

I'm sorry for that, wiping data is usually not necessary -- even in the test stage.  It should not be necessary again.

Also wiped. But it's a good test what titanium backup is capable of. :)
Is there a wipe needed when it gets official? Signing key changes or something.

BT Audio is still broken for me.

Soft keyboard works as normal.

Edited February 1, 2020 by mcdinner

[mcdinner 375]

3 hours ago, tdm said:

Please try wiping data.

 

yep, did dthat after trying 2 times :)

Edited February 1, 2020 by mcdinner

[tdm 2,322]

1 hour ago, mcdinner said:

Also wiped. But it's a good test what titanium backup is capable of. :)
Is there a wipe needed when it gets official? Signing key changes or something.

BT Audio is still broken for me.

Soft keyboard works as normal.

Yes the signing keys change for official but there is a simple way around wiping for that.

 

I'll check BT audio again, but it's been working for me since I built the vendor image myself.

[mcdinner 375]

10 minutes ago, tdm said:

Yes the signing keys change for official but there is a simple way around wiping for that.

 

I'll check BT audio again, but it's been working for me since I built the vendor image myself.

I'll wipe again and recheck, just to be sure.
 

[tdm 2,322]

20 minutes ago, mcdinner said:

I'll wipe again and recheck, just to be sure.
 

Yeah it seems broken here also. I must have broken it yesterday, possibly with my audio prop change. I'll get that fixed and the fingerprint data fixed for Monday.

[mcdinner 375]

6 minutes ago, tdm said:

Yeah it seems broken here also. I must have broken it yesterday, possibly with my audio prop change. I'll get that fixed and the fingerprint data fixed for Monday.

Yes, no Audio and volume controls after wipe.

I also know what @SteffenWi means with the keyboard.
No keyboard in portrait mode until i go to the icon on the bottom right and enable "Show virtual keyboard" with the description "keep it on screen while physical keyboard is active".
 

[silversolver 849]

@tdm is making so much progress on this that it looks like I'll be going straight to LOS when my clack arrives. My only concern is the VoLTE switches being grayed, so needing stock to switch them on. Veri$on, ya know.....

[mcdinner 375]

24 minutes ago, silversolver said:

@tdm is making so much progress on this that it looks like I'll be going straight to LOS when my clack arrives. My only concern is the VoLTE switches being grayed, so needing stock to switch them on. Veri$on, ya know.....

you know, it comes with stock preinstalled 😉

[Polaris 423]

@silversolver It has been my experience that, regardless of the hardware/phone, LOS has those switches grayed out and just uses the provisioning of the SIM card.  Recently I helped a friend setup a LG phone (he was on the list for a Pro1 and his current phone died so he bought one for $15 on ebay to solve the problem.  I found it to be a simple and elegant solution to the longer than expected wait times of the Pro1, but anyway...) and the LG was the same way (I have done others too).  So if the mule isn't running LOS (or a version of LOS where they aren't grayed out), and the switch for VoLTE was previously flipped (with card provisioned) then it should work perfectly regardless of access to the switches.  The weird part is that the grayed out switch appears to be in the off position, but that's just an error, mistake, or whatnot.

[acoppens 45]

On 1/28/2020 at 2:17 PM, bmccrary said:

Like everyone here, thanks to @tdm very much for working on Linage for our phones.  I used to use it on my Photon Q for years and missed it when I went to the Z for the keyboard mod. 

I am having a problem with being able to make phone calls.  I can receive them fine and can also send/receive SMS/MMS.  I'm on Verizon in the US, and since this phone apparently doesn't support CDMA, VoLTE must be used.

I couldn't get it to work at all until I reflashed the stock build and turned on the Voice over LTE switch under the test screen (*#*#4636#*#*).  Then I flashed Linage test2 again and it worked much better!  The switches are grayed out on the Lineage build.

I can use a SIP account for outbound calls so I'm still going to keep using Lineage.  If I can help get the outbound calls to work I'd be happy to do whatever I can.

Is there any trade-off or downside to enabling the VoLTE switch? (If not then why is it disaled by default?

@tdm: thanks for all your hard work, loving the speed with which you're fixing LOS. Once testbuild 3 is out i think I'm ready to take the plunge.

When I'm on build 3 I'll test the cheapo usb lan adapter I have lying around like somebody asked earlier in this thread.

 

[Polaris 423]

44 minutes ago, acoppens said:

Is there any trade-off or downside to enabling the VoLTE switch? (If not then why is it disaled by default?

Well, it can't be disabled; however, in the case of Verizon, (if you could flip it off) it would then mean voice calls couldn't be placed or received over their network (since there isn't CDMA access).

Edited February 1, 2020 by Polaris

[bmccrary 39]

Just for the record, when I flashed to test3 the first time somehow my VoLTE switch got turned back off.  I had to go reflash stock again to turn it on.  No calls at all work with it off on the Linage ROM for me..  It does indeed make a difference with the Linage ROM.  I can now get incoming calls and visual voicemail on Verizon but no outgoing calls yet.

[SteffenWi 139]

8 hours ago, tdm said:

 

@SteffenWi have you figured out the virtual keyboard issue?  It works fine for me, from the very start when asked for a PIN on the lock screen.  I just need to press the keyboard icon on the right side of the navbar and select "Show virtual keyboard".  (I will try to make this the default in the future).

 

yeah found it somewhere in the settings screen. You can't get to that setting from the initialization screen though.

[Polaris 423]

2 hours ago, bmccrary said:

Just for the record, when I flashed to test3 the first time somehow my VoLTE switch got turned back off.  I had to go reflash stock again to turn it on.  No calls at all work with it off on the Linage ROM for me..  It does indeed make a difference with the Linage ROM.  I can now get incoming calls and visual voicemail on Verizon but no outgoing calls yet.

OUCH!  This is not good at all!  I have never seen this behavior, but I also haven't loaded LOS on a Pro1 (yet) either.

I wonder what would have happened if instead of reflashing stock, you just put the SIM card into another phone and flipped the switch, then returned it to the Pro1.

Edited February 2, 2020 by Polaris

[bmccrary 39]

17 hours ago, Polaris said:

OUCH!  This is not good at all!  I have never seen this behavior, but I also haven't loaded LOS on a Pro1 (yet) either.

I wonder what would have happened if instead of reflashing stock, you just put the SIM card into another phone and flipped the switch, then returned it to the Pro1.

That's a great idea and I had thought of that myself.  However, for whatever reason my mule, a Moto Z2 Play (direct from Motorola, not a Verizon one, but working on Verizon) would not enter the menu with the *#*#4636#*#* code.  However, I just checked a minute ago and lo and behold my VoLTE switch is turned off again!  Fortunately I can still get calls this time though.  So I don't know.  I'm happy to try anything if it helps anyone out.

Edited February 2, 2020 by bmccrary

[Polaris 423]

1 hour ago, bmccrary said:

However, for whatever reason my mule, a Moto Z2 Play (direct from Motorola, not a Verizon one, but working on Verizon) would not enter the menu with the *#*#4636#*#* code. 

Now that is just as odd!

 

1 hour ago, bmccrary said:

However, I just checked a minute ago and lo and behold my VoLTE switch is turned off again!  Fortunately I can still get calls this time though.  So I don't know.

This is what I was describing above as "normal" with Lineage.  The switch will be in the off position, and typically grayed out, but it will still be placing and receiving VoLTE calls.

[silversolver 849]

On 2/1/2020 at 3:23 PM, Polaris said:

@silversolver It has been my experience that, regardless of the hardware/phone, LOS has those switches grayed out and just uses the provisioning of the SIM card.  Recently I helped a friend setup a LG phone (he was on the list for a Pro1 and his current phone died so he bought one for $15 on ebay to solve the problem.  I found it to be a simple and elegant solution to the longer than expected wait times of the Pro1, but anyway...) and the LG was the same way (I have done others too).  So if the mule isn't running LOS (or a version of LOS where they aren't grayed out), and the switch for VoLTE was previously flipped (with card provisioned) then it should work perfectly regardless of access to the switches.  The weird part is that the grayed out switch appears to be in the off position, but that's just an error, mistake, or whatnot.

So the million dollar question then becomes what exactly is it that the stock ROM supports that the LOS ROMs universally ignore that causes this behavior? Obviously workarounds exist, but full functionality is better. Perhaps @tdm can comment on this, but honestly this sounds like a low-priority question, let alone project. If the entire LOS community so far has ignored this aspect of the devices, there's either a licensing issue, driver issue, or apathy issue, which is of course possible since most major networks aren't forcing the issue on VoLTE yet, so it's a whatever. However it is, I imagine it will be some time before this is addressed, and it sounds like possibly a much larger undertaking than what's being done here already, for not much reward, at least until carriers start forcing the issue generally.

[tdm 2,322]

1 hour ago, silversolver said:

So the million dollar question then becomes what exactly is it that the stock ROM supports that the LOS ROMs universally ignore that causes this behavior? Obviously workarounds exist, but full functionality is better. Perhaps @tdm can comment on this, but honestly this sounds like a low-priority question, let alone project. If the entire LOS community so far has ignored this aspect of the devices, there's either a licensing issue, driver issue, or apathy issue, which is of course possible since most major networks aren't forcing the issue on VoLTE yet, so it's a whatever. However it is, I imagine it will be some time before this is addressed, and it sounds like possibly a much larger undertaking than what's being done here already, for not much reward, at least until carriers start forcing the issue generally.

Well, a full answer to that question would be quite lengthy.  The brief overview is that there are different parts of the (cell) radio stack and certain parts are subject to vendor changes while others are not.  Generally speaking, Google and Qualcomm rarely agree on things outside basic things in the system and will implement them in different ways.  This leads to AOSP hardware support for Qualcomm devices (eg. used in Nexus/Pixel) having one set of code while the Qualcomm BSP code is different.  This is most apparent in things like advanced audio (compression, offloading) and the radio stack.  VoLTE has pieces in both of these.  Lineage tries to support both, but sometimes one implementation must be chosen or preferred over another.  Further, VoLTE is mainly used in India and when trying to use a GSM-only phone on a CMDA/LTE network.  I don't know any Lineage developers that use it, so it kind of gets neglected.  Combine these two and you have a broken and unsupported feature.

 

[mcdinner 375]

@tdm
I just recognized normal phone calls (GSM/CDMA) are broken on test3. 
I can be called or start a call but after a few seconds its just silence on my side and the other phone. After a few seconds call audio and mic is back again for a few seconds, then silence again. This goes on for a while or the silence part does not stop. Call is active all the time.

I reflashed to be sure it's not related to other stuff.
If you can confirm this, could you build a fixed img soon please? 😉 

[bmccrary 39]

13 minutes ago, mcdinner said:

@tdm
I just recognized normal phone calls (GSM/CDMA) are broken on test3. 
I can be called or start a call but after a few seconds its just silence on my side and the other phone. After a few seconds call audio and mic is back again for a few seconds, then silence again. This goes on for a while or the silence part does not stop. Call is active all the time.

I reflashed to be sure it's not related to other stuff.
If you can confirm this, could you build a fixed img soon please? 😉 

I'm having the same problem with VoLTE.  I wasn't 100% sure it was my phone as the cause as sometimes my signal isn't the best but I'm sure of it now.  What I've noticed, and this could be pure coincidence, is that whenever I have the phone up to my ear and the screen is turned off the audio stops shortly after.  When I pull the phone away and the screen turns back on the audio comes back.  The speakerphone is only playing audio out of the bottom speaker which is right by the mic so the callers complain of really bad echo if I try to use it.  Today I did out of desperation though, and the call never had any audio loss that way.  I'm not sure how the stock ROM does it but I would think you would just want to play phone audio out of the top speaker only to prevent echo.

[mcdinner 375]

1 minute ago, bmccrary said:

I'm having the same problem with VoLTE.  I wasn't 100% sure it was my phone as the cause as sometimes my signal isn't the best but I'm sure of it now.  What I've noticed, and this could be pure coincidence, is that whenever I have the phone up to my ear and the screen is turned off the audio stops shortly after.  When I pull the phone away and the screen turns back on the audio comes back.  The speakerphone is only playing audio out of the bottom speaker which is right by the mic so the callers complain of really bad echo if I try to use it.  Today I did out of desperation though, and the call never had any audio loss that way.  I'm not sure how the stock ROM does it but I would think you would just want to play phone audio out of the top speaker only to prevent echo.

YES! ♥️
It works fine until i put my hand over the sensor. It goes on , but after i lift the hand and display goes on again its silent for a while.
I can also confirm the echo and when I switch to speaker, display does not shut off and audio keeps going.
So seems to be something with display off

[VaZso 1,998]

10 minutes ago, bmccrary said:

The speakerphone is only playing audio out of the bottom speaker which is right by the mic so the callers complain of really bad echo if I try to use it.  Today I did out of desperation though, and the call never had any audio loss that way.  I'm not sure how the stock ROM does it but I would think you would just want to play phone audio out of the top speaker only to prevent echo.

In stock ROM, audio only comes from the bottom speaker in handsfree mode.

However, I have not received complains about using it despite of its position is really close to microphone.

Anyway, I would like to also hear the top speaker to be a bit louder and also farther from microphone.
Otherwise, it may be in connection with miswiring of speakers so it seems two speakers of Pro1 are interchanged which has to be solved in software.
Maybe that is the cause of only bottom speaker has audio in handsfree mode instead of top one.

[mcdinner 375]

Just now, VaZso said:

In stock ROM, audio only comes from the bottom speaker in handsfree mode.

However, I have not received complains about using it despite of its position is really close to microphone.

Anyway, I would like to also hear the top speaker to be a bit louder and also farther from microphone.
Otherwise, it may be in connection with miswiring of speakers so it seems two speakers of Pro1 are interchanged which has to be solved in software.
Maybe that is the cause of only bottom speaker has audio in handsfree mode instead of top one.

echo I had might be from bot phones in close range wile testing.

[VaZso 1,998]

Just now, mcdinner said:

echo I had might be from bot phones in close range wile testing.

That way that is acceptable. 🙂