Didn't face these issues so far, anyway thanks for the update
Sourceforge also gets on my nerves sometimes, when I attempt to upload - was just able to start a download (but I have canceled, as I didn't want to compete the DL), so keep trying
I am planning to switch to 17.1 in the near future (don't worry, for December, there will definitely still be LineageOS 16.0 builds) and to offer this as 2nd build variant in the mentioned thread. I would like however, after some promising tests on my end, to gather feedback also from others before following that path.
Will try later today to upload again
Glad it worked, I haven't yet re-uploaded (not at home during the day) - as said before, sourceforge in the last weeks is a p.i.t.a. ...
Do I understand correctly: You want to install unifiedNlp alongside a gapps installation?Hi @MSe1969 and @115ek, first of all thank for your work to get LineageOS on the D5503. Thank you very much.
The last days I was working on bringing UnifiedNLP to life and came to the conclusion, that it's impossible without a change in framework-res. (github.com/microg/UnifiedNlp/issues/188#issuecomment-735273440)
Would it be possible to provide me a framework-res with changes in the resources at "<string-array name="config_locationProviderPackageNames">"? Would be nice if you could add "<item>org.microg.nlp</item>" to this config-key.
The source is at github.com/LineageOS/android_frameworks_base/blob/lineage-16.0/core/res/res/values/config.xml#L171 but it seems there is some modification for the build. At least I had two values for this array on my phone.
Where would be the best place to get the change permanently in the sources? LineageOS or your repository at github.com/lin16-microg/?
Thank you very much and have a nice weekend.
Best regards
It COULD be an option, but at this time I don't want to resign from gapps pico which is the smallest package and which unfortunatly comes with google network location services. Although I could disable them I'm unable the use NetworkLocation.apk. So I have to use UnifiedNLP or use GPS only.Do I understand correctly: You want to install unifiedNlp alongside a gapps installation?
Why would you do something like this? What's the benefit?
Build variant B with microG isn't an option for you?
But what do you need gapps for what microg isn't able to do? Are there any apps that aren't working?It COULD be an option, but at this time I don't want to resign from gapps pico which is the smallest package and which unfortunatly comes with google network location services. Although I could disable them I'm unable the use NetworkLocation.apk. So I have to use UnifiedNLP or use GPS only.
Umm. But you're using gapps, don't you?Furthermore I like the idea to spread the usage of alternatives for Google, and if it is possible to get a solution by spending 3 days to look into the issues and bring them back to work it would be a welcome opportunity for me.
Yes. That may be. But I'm relatively sure this patch won't ever be accepted in lineage upstream. There already was an attempt which failed.Including the package name in the configs of LineageOS wouldn't break something BUT it would be a good starting point for further possibilities.
diff --git a/core/res/res/values/config.xml b/core/res/res/values/config.xml
index a84d23b624b..905e9dd9f67 100644
--- a/core/res/res/values/config.xml
+++ b/core/res/res/values/config.xml
@@ -1875,6 +1875,7 @@
<string-array name="config_locationProviderPackageNames" translatable="false">
<!-- The standard AOSP fused location provider -->
<item>com.android.location.fused</item>
+ <item>org.microg.nlp</item>
</string-array>
<!-- This string array can be overriden to enable test location providers initially. -->
Hello @greenflash1986, I fully agree with @115ek 's statements:I see the following options now:
- You abandon gapps usage and switch to the microg version.
- We include the patch (If it works. We'd need your confirmation therefor.) However, I don't like this approach as we would move away from a "clean" LineageOS. Once starting this, more people may/will ask for changes. I'm personally against it, but maybe wait for @MSe1969.
- You build your own image and include the patch there. Everything needed for building is available here. Maybe this is a good starting point.
Hi @greenflash1986,The last days I was working on bringing UnifiedNLP to life and came to the conclusion, that it's impossible without a change in framework-res. (github.com/microg/UnifiedNlp/issues/188#issuecomment-735273440)
Would it be possible to provide me a framework-res with changes in the resources at "<string-array name="config_locationProviderPackageNames">"? Would be nice if you could add "<item>org.microg.nlp</item>" to this config-key.
I used GAPPS for the last years except the network location provider and relied only on GPS. I did know that there was another location provider but did not had the time to work on this. So know I had some spare time and have seen that there is the possibility to use Unified beside Gapps and the challange was accepted to dig deeper in Android and figure out why it didn't work out.But what do you need gapps for what microg isn't able to do? Are there any apps that aren't working?
Yes. That may be. But I'm relatively sure this patch won't ever be accepted in lineage upstream. There already was an attempt which failed.
I did but unfortunately without success. The framework-res ended up withAnyway. I just built a lineage 17 image for you including the following patch. Could you test if it solves your problem?
<string-array name="config_locationProviderPackageNames">
<item>com.google.android.gms</item>
<item>com.android.location.fused</item>
</string-array>
I see the following options now:
- You abandon gapps usage and switch to the microg version.
- We include the patch (If it works. We'd need your confirmation therefor.) However, I don't like this approach as we would move away from a "clean" LineageOS. Once starting this, more people may/will ask for changes. [...]
- You build your own image and include the patch there. Everything needed for building [...]
I already tried that without luckHi @greenflash1986,
in addition to my last comment - there is in fact a potential solution for you, which could help to create a "flashable zip" for UnifiedNLP, which could be applied then to any ROM:
It is called "Runtime Resource Overlay (RRO)". [...]
Yes I hoped for this outcomeEDIT:
[...]
Btw: Your approach to patch the framework and sign it with your own keys of course leads to a non-booting device.
Our build is signed, so any signature mismatch will force trouble. For a good reason.
If you have Gapps / play services active, I am not sure, whether you can really run another location provider in parallel, I don't think so - you would have to deactivate play services, and then you can also switch to the microG build.
Yes, would be interesting to know, what happens in case of active play services, if that patch is applied - but at the end not really useful:
framework-res.apk in fact is individually generated during the ROM build! Its inputs come from the default values of the frameworks/base repository on the one hand side (and yes, here - a code change *could* lead to the desired result, if not overlaid), but also from overlays in device-specific repositories , [...]
So providing this apk to you is useless, it would be specific to our signed amami ROM (just in case your idea is to build a flashable zip with UnifiedNLP and the modified framework-res.apk).
As said, one would have to build a ROM with this patch included! And as @115ek said, yes, we technically could provide such a patched ROM for the amami device - this would satisfy you personally and be unique for the amami device (and we want to deliver a variant corresponding to "plain" LineageOS).
And LineageOS will not apply that patch - as mentioned by @115ek.
I think building your own ROM would be the best option for you, if you don't want to use the microG build - [...]
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
- Boot : Ok
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : only 2.4 GHz
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok (mono)
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: broken
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok
- SEPolicies : Enforcing
DownloadFollowing limitations are known:
- NFC-HCE does not work (needed for example for google pay)
- FM does not work in stereo mode (mono works fine, though)
Problems with some 5 GHz Wifi channels (can be avoided by not using autochanneling)fixed with 20190408 build- MHL does not work
- 5 GHz hotspot does not work (2.4 GHz hotspot works fine)
ANT+ does not workfixed (see FAQ)installing Magisk 19.1 prohibits entering recoveryfixed with 20190521 buildGPS gets wrong time due to GPS week rollover since 3rd November 2019 (of importance when you record GPS tracks for example).fixed with 20190611 build
This also happens on stock and several other legacy devices.
FAQ
What recovery system to use?
Please use this TWRP if you want to use OTA updates and/or encryption.
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
- Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 16.0 here and flash via TWRP
- Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Please note there is an issue starting with Magisk 19.1 which leads you to being unable to boot to recovery in any way. More info
ANT+ isn't working?
You need the 2 apps:
afterwards setting proper permissions is essential!
- ANT Radio Service (Github) / (Google play)
- ANT+ Plugin Service (Github) / (Google play)
This refers to those instructions which worked for me
- Go to Apps & Notifications -> See All Apps
- Select 'ANT Radio Service'
- Select Permissions
- Select Additional permissions
- Slide switch to allow using of ANT hardware
![]()
I've got problems AND have magisk/exposed installed
I won't support anything related to magisk/exposed/other heavily system modifying things.
If you're encountering problems please make sure you're using a clean installation (at most gapps) to verify/reproduce the issue.
SourcesYou'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Credits
- SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
- rcstar6696
- SuperLamic
- drakonizer
- AdrianDC
- munjeni: thanks for tips and tricks
- nailyk: thanks for tips and tricks
- All the other contributors on Sony msm8974 platform
- LineageOS team
Please see the OP of our (deprecated) LineageOS 15.1 thread or also here
13.12.2020
Expand for older changelogs:
- ASB Security string 2020-12-01 (this month, no kernel updates found)
- Webview updates for both builds (microG build on M87)
- microG build only: F-Droid updated to 1.10-alpha1-114
- microG build only: microG updated from upstream to 0.2.14.204215-15 (picked until 720b089)
10.11.2020
13.10.2020
- ASB Security string 2020-11-05
- Fix for CVE-2020-15999
- AOSP E-Mail widget fixed
- Webviews upodated to/within M86
- microG build only: microG - fixes in EN API and GCM
- microG build only: Replaced weak F-Droid signatures with ROM's V2 signatures
13.09.2020
- ASB Security string 2020-10-05
- microG build only: Bromite Webview on M86
- microG build only: microG 0.2.12.203315 - including "Exposure notification API" for use of Covid tracing apps
- microG build only: Additional hardening: constified JNI method tables
09.08.2020
- ASB Security string 2020-09-05
- Webviews on M85
- microG build only: Added eSpeak TTS engine (microG build variant)
12.07.2020
- ASB Security string 2020-08-05
- Webviews on M84
- microG build only: Location of firewall UI now in Network => data usage (Settings menu)
11.06.2020
- ASB Security string 2020-07-05
- microG build only: updated prebuilt microG GmsCore fom /e/ project (fixed FCM registration issues)
- microG build only: F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
- microG build only: Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6
09.05.2020
- Security string 2020-06-05
- GPS improvements / modernisation
- Enable MIDI support
- microG build only: Bromite Webview on M83
- microG build only: Netmonitor exception in SEPolicy f. "Tracker Control" app
11.04.2020
- Security string 2020-05-05
- Standard build only:System Webview on M81
- microG build only: AuroraStore updated to 3.2.8
07.03.2020
- Security string 2020-04-05
- Fix for CVE-2020-8597 (external/ppp)
- Kernel: CVE-2019-10638 siphash 128bit for IP generation
- microG build only: AuroraStore updated to 3.2.4
- microG build only: Bromite Webview on M81
19.02.2020
- Security string 2020-03-05
- System Webviews on M80
- 2nd build variant 'hardened microG build' (known from 15.1 thread) available
- microG build only: AuroraStore updated to 3.2.0
16.01.2020
- fixed DRM (we now have widevine Level 3, Netflix for example runs fine)
- fixed TWRP time bug
- added option to prevent USB gadgets working when screen locked (trust HAL)
- enabled changelog (can be accessed under /settings/system/updater/changelog)
- synced LineageOS sources (security patch level February 05, 2020)
13.12.2019
- synced LineageOS sources (security patch level January 05, 2020)
13.11.2019
- synced LineageOS sources (security patch level December 05, 2019)
19.10.2019
- fixed unreliable SMS/MMS receiving (https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/262653)
- synced LineageOS sources (security patch level November 05, 2019)
13.09.2019
- synced LineageOS sources (security patch level October 05, 2019)
12.08.2019
- bring back wifi display
- three finger screenshot gesture
- synced LineageOS sources (security patch level September 05, 2019)
07.07.2019
- fixed manual mobile network selection (once again)
- synced LineageOS sources (security patch level August 01, 2019)
03.07.2019
- synced LineageOS sources (security patch level July 05, 2019)
- fixed AudioFX effects completely (thanks @NeoArian)
10.06.2019
- start signing builds (please check this if you want to update)
- enable OTA updates (thanks @NeoArian)
21.05.2019
- synced LineageOS sources (security patch level June 05, 2019)
11.05.2019
- fixed recovery issue introduced by Magisk versions starting with 19.1 (thanks @Myself5)
08.04.2019
- synced LineageOS sources (security patch level May 05, 2019)
11.03.2019
- fixed manual mobile network selection (thanks @SpiritCroc)
- fixed problems with 5 GHz Wifi channels
- added aptX/aptXHD
- synced LineageOS sources (security patch level April 05, 2019)
17.02.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)
15.01.2019
- fixed occasional camera problems (thanks @SpiritCroc)
- various kernel patches (thanks @SpiritCroc)
- synced LineageOS sources (security patch level February 05, 2019)
04.01.2019
- fixed video playback for some applications (thanks @SpiritCroc)
- fixed offline charging (thanks @SpiritCroc)
- fixed FM radio (thanks @SpiritCroc)
- updated webview to version 71 (thanks @MSe1969)
- synced LineageOS sources
- initial release