LineageOS, Current status : 16.0 Test Builds

[RoThe 5]

4 hours ago, paul said:

1. The hotspot does not start if the Wi-Fi is on. When I try to power on it it self power offs and it does not start, it concludes a generic "error";

I realized that today, too. If wifi is on and I try to turn on hotspot, it will turn itself off again with said "error".

However, when I turn off wifi first and then turn on hotspot it works. I tried connecting with my laptop, no problem, had internet access.
Then when I turn on wifi again, the hotspot will turn off.
I am still running Test 9 at this moment I will flash test10 and report back again.

EDIT: also works for me in test10

A few days ago I reported issues with my earspeaker, I was able to resolve that problem. A few days before I dropped my phone (not from high and on a not too hard surface), I couldn't see any scratch or damage on my device back then. Apparently though the plastic behind the screen in the top left corner popped out a bit. After I "clicked" it in again, the speaker problems were gone :) 

Edited March 10, 2020 by RoThe

[david 929]

4 hours ago, Craig said:

I've also used this feature on PQ to sign into public wifi and share it with other devices, so I tried it now, and yep not working. 

Are you saying you were able have your phone be both a wifi client and wifi hotspot at the same time?  I didn't even know that was possible.  I thought the radio couldn't function in both capacities simultaneously.  It has never allowed that for me on my past phones.  I just tried it on a spare Pixel 1 (no sim card) with Android 10, and it acts the same as my older phones -- when the hotspot is turned on, the wifi turns off.

[EskeRahn 5,460]

4 hours ago, tdm said:

Possibly this commit?  I got it from another device while I was trying to get things working, and then I deleted it when I saw that 1+5/5t does not have it.  I am not sure if it should be present or not.

Thanks. Well I have no idea. And do not know how to check, sorry.

[tdm 2,322]

Got the FM radio fixed (listening to it now).  Will push that up and do a new build soon.

 

If anyone is interested in details...

 

The first problem is that the AOSP "FMRadio" package is broken and not used, there is a QCOM "FM2" package that is used instead.  I've noted this before.  Second, there are some libraries that must be specified to be built which I was missing.  Thirdly, there is a library that seems to be in the open source code but explicitly set to not build without the BSP for some reason so that needs to go into the proprietary blob list.  Fourthly, was missing a required property, "vendor.bluetooth.soc=cherokee" (I had mistakenly set vendor.qcom.bluetooth.soc).

 

EDIT: both vendor.bluetooth.soc and vendor.qcom.bluetooth.soc appear to be used in various places, so I guess both need to be set.  Yay consistency...

Edited March 10, 2020 by tdm

[3zet 100]

Hi, there is any chance and if, when ROM will be able to run apps which are looking for safetycheck option? I don't know too much about Android and it's forks so sorry for stupid questions. 

Edited March 10, 2020 by 3zet

[tdm 2,322]

31 minutes ago, 3zet said:

Hi, there is any chance and if, when ROM will be able to run apps which are looking for safetycheck option? I don't know too much about Android and it's forks so sorry for stupid questions. 

Lineage by default will not.  Folks typically use magisk for this.

[tdm 2,322]

test11 is up.  The only change is fixing FM radio.

 

[wilhelmfitzpatrick 47]

Does the "register your device with Google" thing have any impact on SafetyNet, or is that something different? https://www.google.com/android/uncertified/?pli=1

[tdm 2,322]

1 minute ago, wilhelmfitzpatrick said:

Does the "register your device with Google" thing have any impact on SafetyNet, or is that something different? https://www.google.com/android/uncertified/?pli=1

That is for when play services detects that your device is not registered, eg. the build fingerprint does not match any registered/approved devices. Basically when Google didn't get their money from certification. Lineage will be registered, as it uses the stock fingerprint. So that is not needed.

 

[EskeRahn 5,460]

37 minutes ago, tdm said:

test11 is up.  The only change is fixing FM radio.

And the FM works too. Thanks. 😎

[mcdinner 375]

I can confirm crackling audio is gone on dialpad tones :)

[Polaris 423]

In the "Custom restrictions" menu there are notification options when the screen is off and when the screen in on.  However, in LineageOS they don't appear to work.  Or at least don't appear to behave as they did in the stock ROM.  For instance, if I select "Don't turn on screen" under "When the screen is off," it still turns on the screen when a notification event happens (such as an incoming text message).  For the time being I don't have removed all security locks (fingerprint, pin, pattern, etc.) and am just using a simple swipe.  However, this means that when an incoming text arrives the screen turns on and anyone near the phone can read the text message.  It does this even if the "Behavior" under Notifications is set changed to something other than "Make sound and pop on screen."

Can anyone confirm these options are broken? 

[auvo.salmi 135]

Haven't tested those options too much, but also have noticed that there's some parts not working in notifications. Notification led is basically working, but looks like it doesn't trigger every time, so it doesn't blink with every notification. And I don't mean different apps, but for example some whatsapp messages trigger notification led blink and some others not. Also some messages trigger notification to lockscreen while some others don't. Can't see any pattern in this either.

Also looks like Android has the stupid way to dismiss email notifications when you have email widget in use. I had the same problem in stock though. But I use K9 mail and K9 mail widget (made by other company than k9). The system dismisses email notifications as soon the widget app refreshes and notifies new messages. Blah, so stupid.. It didn't happen in Maemo or Sailfish though..

[EskeRahn 5,460]

On 3/10/2020 at 4:02 PM, EskeRahn said:

Just curious, why are the options in LiveDisplay reduced with Test10 compared to Test8?

(do not recall how it was on Test9)

A little more on LiveDisplay. The options displayed is the same for Test9,10 and 11.

There is another minor (new) issue from Test10:

In the notification area, pressing and holding the A in a square fails to launch LiveDisplay (It works with both Test8 and Test9, but NOT on neither test10 nor test11) It understand that it is supposed to do something, and collapses the notifications, but no launch.

 

[EskeRahn 5,460]

Slight update to the helper-script, removing a few clicks, and make it more suited for 80 char width

Assuming the needed files are saved in a LineageOS sub dir, so change as needed.

@ECHO off
if %1.==. goto :EOF
ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power)
adb reboot bootloader
pause
fastboot flash boot_a LineageOS\lineage-16.0-pro1-test%1-boot.img
fastboot --set-active=a
REM fastboot reboot recovery    does not work, so do manually:
ECHO * Roll down to "Recovery Mode" with VolDown, and press Power to select.
ECHO * Await recovery boot. Select "Apply update", "Apply from ADB" for main flash
pause
adb sideload LineageOS\lineage-16.0-pro1-test%1.zip
TimeOut 5 /nobreak>nul
adb reboot recovery
ECHO * Await recovery boot. Select "Apply update", "Apply from ADB" to add Gapps
pause
adb sideload LineageOS\MindTheGapps-9.0.0-arm64-20190615_031441.zip
TimeOut 5 /nobreak>nul
adb reboot
ECHO **DONE** Should now boot into LineageOS Test%1

With output like this

[auvo.salmi 135]

On 11/29/2019 at 8:20 PM, tdm said:

It works for me.  Is anyone else having issues?

files.nwwn.com should have address 144.91.102.195.  I switched servers in the last few days but DNS should have been updated some time ago.

 

EDIT: reproduced the issue, investigating.

EDIT: the issue seems to be IPv6.

EDIT: fixed, new IPv6 address should propagate within an hour.

 

I was going to flash newest, but can't get to files.nwwm.com. Or even ping it. So looks like there's some issues again?

[PVx 10]

9 hours ago, EskeRahn said:

Slight update to the helper-script, removing a few clicks, and make it more suited for 80 char width

I created a Linux shell script version of it, maybe it will be useful for someone (I'm not sure if read -p is POSIX compatible, but should work in most shells):

#! /bin/sh

[ x"$1" = x ] && echo "Argument needed" && exit
ver="$1"

echo "* Wait for boot to bootloader to finish (or do manually holding VolDown+Power)"
adb reboot bootloader
read -p "(Enter to continue)" a

fastboot flash boot_a LineageOS/lineage-16.0-pro1-test"$ver"-boot.img
fastboot --set-active=a
# fastboot reboot recovery does not work, so do manually:
read -p "Roll down to recovery boot with VolDown, and press Power to select. (Enter to continue)" a
read -p '* Await recovery boot. Select "Apply update", "Apply from ADB" for main flash (Enter)' a

adb sideload LineageOS/lineage-16.0-pro1-test"$ver".zip
echo "Waiting 5 sec to finish"
sleep 5

adb reboot recovery
read -p '* Await recovery boot. Select "Apply update", "Apply from ADB" to add Gapps (Enter)' a

adb sideload LineageOS/MindTheGapps-9.0.0-arm64-20190615_031441.zip
echo "Waiting 5 sec to finish"
sleep 5

adb reboot
echo "**DONE** Should now boot into LineageOS Test$ver"

 

[tdm 2,322]

Quick update:

 

@EskeRahn I'll add LiveDisplay back for the next build.

 

@auvo.salmi something happened with my DNS and it lost all the IPv6 entries.  I have restored them and it should be working again.

 

I asked about gapps persistence in Lineage Slack and the answer was that gapps persistence only works for OTA on A/B devices, not with sideload.  This is because nobody has been able to figure out get it working with sideload.  So, as you are surely aware by now, gapps needs to be flashed after updating.  I'll try to fix this soon.  But this won't be a problem after it goes official because updates will be via OTA.

 

I'm currently working on selinux rules.  Hopefully it won't take too long to get enforcing mode working.  After that is done, there isn't much standing in the way of official builds.

 

Finally, Seattle is in full coronoavirus mode.  Kids are out of school for at least two weeks starting today and most people are working remote.  I'm not sure how much time I'll have for working on the Pro1 over the next few weeks, so expect my work to slow down for a while.

 

[Hook 3,022]

14 minutes ago, tdm said:

Quick update:

 

@EskeRahn I'll add LiveDisplay back for the next build.

 

@auvo.salmi something happened with my DNS and it lost all the IPv6 entries.  I have restored them and it should be working again.

 

I asked about gapps persistence in Lineage Slack and the answer was that gapps persistence only works for OTA on A/B devices, not with sideload.  This is because nobody has been able to figure out get it working with sideload.  So, as you are surely aware by now, gapps needs to be flashed after updating.  I'll try to fix this soon.  But this won't be a problem after it goes official because updates will be via OTA.

 

I'm currently working on selinux rules.  Hopefully it won't take too long to get enforcing mode working.  After that is done, there isn't much standing in the way of official builds.

 

Finally, Seattle is in full coronoavirus mode.  Kids are out of school for at least two weeks starting today and most people are working remote.  I'm not sure how much time I'll have for working on the Pro1 over the next few weeks, so expect my work to slow down for a while.

 

Thank you for everything you are doing.  I'm probably going to root stock so I can do a Titanium backup and then wipe and try Lineage.  It is amazing to have this kind of support  for our phones and your hard work is so appreciated.  I also appreciate that you are going to put together an AOKP build.  I can't wait.

But, for now, take care and do what you need to do for your family.  I have family in Seattle myself.

I just sent you a six pack to get you though.  😉

[spam71 55]

1 hour ago, Hook said:

I'm probably going to root stock so I can do a Titanium backup and then wipe and try Lineage.

I tested both official and LOS for quite a long time. Right now LOS is much better, has great support, has less issues, is fast and at least as stable, as official build. 

Good job tdm! Thanks to your work this phone gets almost perfect. Because what would be a great hardware with poor software? The answer is stock Pro1. 

Thank you very much. If there is a way to repay you for your work somehow (ie paypal account), please let us know, because at least me, I'd be glad to offer some money as donation for your effort. 

[tdm 2,322]

3 minutes ago, spam71 said:

I tested both official and LOS for quite a long time. Right now LOS is much better, has great support, has less issues, is fast and at least as stable, as official build. 

Good job tdm! Thanks to your work this phone gets almost perfect. Because what would be a great hardware with poor software? The answer is stock Pro1. 

Thank you very much. If there is a way to repay you for your work somehow (ie paypal account), please let us know, because at least me, I'd be glad to offer some money as donation for your effort. 

Thank you.  🙂

 

For paypal please see here:
https://community.fxtec.com/topic/2509-lineageos-current-status-160-test-builds/page/19/?tab=comments#comment-44659

[tdm 2,322]

My initial AOKP build won't boot.  I swear, this device has given me trouble every single step of the way.  I've never seen any device cause more trouble in my 6 years of doing custom ROMs.

 

[RoThe 5]

On 3/12/2020 at 3:32 AM, EskeRahn said:

Slight update to the helper-script, removing a few clicks, and make it more suited for 80 char width

@ECHO off
if %1.==. goto :EOF
ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power)
adb reboot bootloader
pause
fastboot flash boot_a LineageOS\lineage-16.0-pro1-test%1-boot.img
fastboot --set-active=a
REM fastboot reboot recovery    does not work, so do manually:
ECHO * Roll down to recovery boot with VolDown, and press Power to select.
ECHO * Await recovery boot. Select "Apply update", "Apply from ADB" for main flash
pause
adb sideload LineageOS\lineage-16.0-pro1-test%1.zip
TimeOut 5 /nobreak>null
adb reboot recovery
ECHO * Await recovery boot. Select "Apply update", "Apply from ADB" to add Gapps
pause
adb sideload LineageOS\MindTheGapps-9.0.0-arm64-20190615_031441.zip
TimeOut 5 /nobreak>null
adb reboot
ECHO **DONE** Should now boot into LineageOS Test%1

 

When I look at your script I'm getting a bit confused about the flashing process and slots.
From what I knew, when I have A/B slots, I should flash Lineage while slot A is active, because it will always flash to the inactive slot.

When I read the instructions on the download page though there seems no necessity to switch to slot a just for updating / dirty flashing the rom.
In the script you change to slot_a though.
Also, with every new test build, also the version of the boot image changes, what changes there? Is it even necessary to flash it when I perform just an update?
Seeing your script it confuses me even more because, IF flashing boot image is only necessary coming from another rom, why shouldn't a wipe/factory reset be performed?

I hope someone could clear that up for me, thank you 🙂

[Polaris 423]

11 hours ago, tdm said:

My initial AOKP build won't boot.  I swear, this device has given me trouble every single step of the way.  I've never seen any device cause more trouble in my 6 years of doing custom ROMs.

 

Gee, why does this not surprise me?!  Right, nothing seems to have been easy.  Thanks again for all your hard work. 🍺🍺🍺

[EskeRahn 5,460]

2 hours ago, RoThe said:

When I look at your script I'm getting a bit confused about the flashing process and slots.
From what I knew, when I have A/B slots, I should flash Lineage while slot A is active, because it will always flash to the inactive slot.

When I read the instructions on the download page though there seems no necessity to switch to slot a just for updating / dirty flashing the rom.
In the script you change to slot_a though.
Also, with every new test build, also the version of the boot image changes, what changes there? Is it even necessary to flash it when I perform just an update?
Seeing your script it confuses me even more because, IF flashing boot image is only necessary coming from another rom, why shouldn't a wipe/factory reset be performed?

I hope someone could clear that up for me, thank you 🙂

The script is just an automatised version of the process @tdm described here. I have compared the boot-images, and they are binary different (I do not know why).

(I could have added some echo-text of optionally wiping user data before the first main sideload, to be used when switching from stock, or when you do NOT want an upgrade - e.g. a downgrade from test10 to test9 would require a wipe)