[ROM][A320FL/F/Y] LineageOS 16.0

[McFy]

I am trying to build from sources and i get the following error:


McFy told me to remove it from hardware/samsung but i do not know how to to it. Can anyone help me?

You can as well remove device/samsung/exynos7870-common/product/livedisplay.mk

 

[TheAsKo]

Latest Build

@McFy

I did clean install (except boot , so only wipe all things in TWRP) + gapps pico + magisk 19

But SafetyNet is still nt recognized and now i cannot even see Netflix in Play Store :/ (Also i think that AOD is still very low brightness)

Can you please look into this ? Except this , this ROM is only thing that keeps me from changing phone youre are really bringing life to this (older) device :3

Ty for your work

(BTW: Is there way to donate you?)

 

[McFy]

@McFy

I did clean install (except boot , so only wipe all things in TWRP) + gapps pico + magisk 19

But SafetyNet is still nt recognized and now i cannot even see Netflix in Play Store :/ (Also i think that AOD is still very low brightness)

Can you please look into this ? Except this , this ROM is only thing that keeps me from changing phone youre are really bringing life to this (older) device :3

Ty for your work

(BTW: Is there way to donate you?)

Safetynet doesn't pass because I didn't found an A3
fingerprint working yet, using some other's phone one work but it's not the proper fix so I continue to search.
AOD is on low brightness because it yet use a lot of battery.
Glad to heard this
Sure my paypal is : PayPal.me/McFy49

 

[MartinYTCZ]

I am trying to build from sources and i get the following error:

[1/1] /home/user/lin16/out/soong/.minibootstrap/minibp /home/user/lin16/out/soong/.bootstrap/build.ninja
[55/56] glob prebuilts/ndk/stl.bp
[80/80] /home/user/lin16/out/soong/.bootstrap/bin/soong_build /home/user/lin16/out/soong/build.ninja
/home/user/lin16/out/build-lineage_a3y17lte-cleanspec.ninja is missing, regenerating...
/home/user/lin16/out/build-lineage_a3y17lte.ninja is missing, regenerating...
[1037/1037] including vendor/samsung/on7xelte/Android.mk ...
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/etc/init/android.hardware.wifi@1.0-service.rc'
build/make/core/base_rules.mk:426: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/etc/init/android.hardware.wifi@1.0-service.rc'
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/etc/init/android.hardware.media.omx@1.0-service.rc'
build/make/core/base_rules.mk:426: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/etc/init/android.hardware.media.omx@1.0-service.rc'
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/etc/init/android.hardware.power@1.0-service.rc'
build/make/core/base_rules.mk:426: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/etc/init/android.hardware.power@1.0-service.rc'
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/etc/bluetooth/bt_did.conf'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/etc/bluetooth/bt_did.conf'
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/etc/bluetooth/bt_stack.conf'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/etc/bluetooth/bt_stack.conf'
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so'
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so'
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/lib/libsecril-client.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/lib/libsecril-client.so'
build/make/core/Makefile:28: warning: overriding commands for target `/home/user/lin16/out/target/product/a3y17lte/system/lib/libsensorservice.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/user/lin16/out/target/product/a3y17lte/system/lib/libsensorservice.so'
[ 99% 793/794] glob vendor/qcom/opensource/interfaces/wifi/supplicant/2.0/src
ninja: error: '/home/user/lin16/out/target/common/obj/JAVA_LIBRARIES/vendor.lineage.livedisplay-V1.0-java_intermediates/javalib.jar', needed by '/home/user/lin16/out/target/product/a3y17lte/dex_bootjars/system/framework/boot.prof', missing and no known rule to make it

McFy told me to remove it from hardware/samsung but i do not know how to to it. Can anyone help me?

Go to this Telegram group: http://t.me/a32017ot
It's the official group and you can resolve all issues with McFy there

 

[Filipe Baltazar]

Hey @McFy
Thank you for persisting with software development for this obscure phone. Really wish I could send you a hundred bucks but life finds a way of sucking us dry.
Btw, can I dirty flash from 08042019 to 10042019? or should I do a clean install?
I don't know if it's an issue with discord or the ROM but I can't input sound. Built in Voice recorder app only records static. Everything else works just fine. Battery is on par with other Lineage builds. No more crashes due to accent color changes.
Also, are Lineage sources still without an icon changer for Trebuchet on LOS16 and no shortcuts in the lock screen?
Given your increased workload with other phones and primarily LOS development on them too, do you have plans for RR 7 development on this phone and/or others?

 

[Filipe Baltazar]

What is up with the MicroG ROM? Are you trying to Google just enough without Googling the ROM with GAPPS?

 

[Foo Bar]

Try to disable always on display - I had the same problem. With AOD the battery lasts 1 day only. Without AOD it is 2 at least. This might be a problem with this rom.. I don't know.

I disabled AOD, things are lot better, thx for your answer

 

[plstanchev]

need help

guys i need some help i bought this a3 2017 yesterday from online shop should have been unlocked but my sim card VIVACOM bulgaria Three-UK does not work on any modem i try its sim locked i cant get around this , i managed to install twrp even flashed lineage before i tryed several stock firmwares that were supposed to be unbranded but im very confused all day been strugling with this my head is a mess ...i rly like this phone want to keep it can anyone sa something usefull dont know what else to do i did everything i could i believe without any success my sim is always locked

 

[nishfrog]

Big thanks for bringing Pie to my A320FL.

Has this ROM been compiled to include the FlipFlap package? (android_packages_apps_FlipFlap)

I have Samsung's Neon Flip Cover which seems to work using a magnet.
The 20190411 version of the ROM doesn't seem to detect the magnet and doesn't enable additional FlipFlap setting for it.

 

[McFy]

Hey @McFy
Thank you for persisting with software development for this obscure phone. Really wish I could send you a hundred bucks but life finds a way of sucking us dry.
Btw, can I dirty flash from 08042019 to 10042019? or should I do a clean install?
I don't know if it's an issue with discord or the ROM but I can't input sound. Built in Voice recorder app only records static. Everything else works just fine. Battery is on par with other Lineage builds. No more crashes due to accent color changes.
Also, are Lineage sources still without an icon changer for Trebuchet on LOS16 and no shortcuts in the lock screen?
Given your increased workload with other phones and primarily LOS development on them too, do you have plans for RR 7 development on this phone and/or others?

That's not a problem, I do this project for free as learning purpose and not for money even if I am really thankful to the donators
As always you can try to dirty flash but if you end having unespected bugs you must clean install.
I am still not sure to do RR but I know this is waited by some users

What is up with the MicroG ROM? Are you trying to Google just enough without Googling the ROM with GAPPS?

MicroG rom is there for people interested in the MicroG project: https://microg.org/ It doesn't have OTA added to it yet but that is not excluded to be added in the future. It have signature spoofing patch as well

guys i need some help i bought this a3 2017 yesterday from online shop should have been unlocked but my sim card VIVACOM bulgaria Three-UK does not work on any modem i try its sim locked i cant get around this , i managed to install twrp even flashed lineage before i tryed several stock firmwares that were supposed to be unbranded but im very confused all day been strugling with this my head is a mess ...i rly like this phone want to keep it can anyone sa something usefull dont know what else to do i did everything i could i believe without any success my sim is always locked

Your phone seems to be sim locked, ask the store you bought it from.

Big thanks for bringing Pie to my A320FL.

Has this ROM been compiled to include the FlipFlap package? (android_packages_apps_FlipFlap)

I have Samsung's Neon Flip Cover which seems to work using a magnet.
The 20190411 version of the ROM doesn't seem to detect the magnet and doesn't enable additional FlipFlap setting for it.

I removed FlipFlap package as far I don't have a case to try if it works, I can add it in future updates .

 

[starbright_]

MicroG rom is there for people interested in the MicroG project: https://microg.org/ It doesn't have OTA added to it yet but that is not excluded to be added in the future. It have signature spoofing patch as well

I am a fan of "degoogle" phone, so I use it too. Use nanodroid to get this. Right now I don't get notifications, nor I see apps registered for GCM (as ebay for instance). Anyone here have better experience?
Big thanks to you for the ROM. It is probably the smallest and lightest with LOS, so I hope it will have a long life!

 

[Filipe Baltazar]

I am dirty flashing as of the past few daily updates you release. Working just as well as a clean install.

Mic issues have been fixed. WiFi lock on to networks is a little bit slower than los15.1 builds. Battery is as good as 15.1 if not better. Haven't had a single crash or reboot, I'm using Magisk too. Do you know any working gcam ports?

I was thinking about using some of your work to jump start RR7 development for this phone but my computer is not powerful enough for that.

Also, are you still working on the 64bit ROM?

Thanks.

 

[cyberbix]

Anyone here have better experience?

I´m on McFys microG LOS16 from 20190412 and I do not encounter any problems with GCM or Nanodroid itself. As the documentation of Nanodroid reads, only new installed applications can be recognized for the push tokens. So if you did a dirty flash, this could be the problem. For Threema I had the same problem, but Threema allows to re-register with a new push token, that helped for me. For Threema it was also important to disable battery optimization and allow background data. Otherwise push notifications will come in delayed by a couple minutes.

Try the Push Notification Tester from Bernd Bindreiter, it allows to have a delayed delivery, so you can even test your phones sleep state behaviour. After installation it shows up as registered in microG settings app in the GCM Menu.

I use a stable Nanodroid 20190310 with customized setup through Nanodroid setup wizard. I will post details on your "Live without GApp" thread.

 

[starbright_]

I´m on McFys microG LOS16 from 20190412 ...
I use a stable Nanodroid 20190310 with customized setup through Nanodroid setup wizard. I will post details on your "Live without GApp" thread.

Hey, how cool is that - we have a microG LOS! I missed that. Many many thanks to @McFy!
I 'll just repeat my (this time clean) installation, so even wipe data. I have backuped this with "migrate"-tool, let's look how it works - whether this counts as a fresh installation or not.
Do you see any apps that are registered for push notication? Is registering at google a precondition. I am not sure whether I need this or not.
Thanks for update this thread.

---- My steps to microG (---
https://downloads.nanolx.org/NanoDroid/Stable/):
Install "migrate" or TB and create a backup
TWRP: Wipe cache, dalvic, system, data
run nanodroid-setupwizard
select: FDROID, MapsV1, init scripts, Full installation, GSMCore from nanodroid, no Backend, Yalp Store
install LOS for microG (spoofed), Magisk 18.1, microG
reboot.
check the microG-setting, enable Google registration and GCM.
First install just apps only (to get registration for GCM they have to be installed after microG)
than in a second step recover data of apps

 

[starbright_]

Wifi problem, MAC 02:00:00:00:00:00

My problem is still Wifi. With older versions it happens from time to time, mainly after a reboot, that Wifi couldn't be switched on. At that time I could get it working with Wipe Cache/Dalvik and reboot.
As I did a dirty flash, I decided to reinstall all new with a clean flash of data too and hope this issue will disappear.

To my surprise problems even get bigger. At least with the microG version 0412. I have to do 3 steps after cleaning:
Flash LOS, Magisk 18.1, microG core. Tried in in one shot, or with reboots inbetween - result was same.
The MAC shown as 02:00:00:00:00:00 as indication (or reason) that something goes wrong.
There is a lot to find about this MAC error, for instance the recommendation to reset network/BT-settings. I did this without success.
I tried several reinstallations, once with just LOS. Wifi was working than (at least this one time). But without root it is not useable for me and after flashing Magisk the MAC was again 02:00.... and Wifi couldn't be enabled.

Please guys, hope someone has a good idea what might be the reason here.

 

[cyberbix]

microG and Push Messages

Do you see any apps that are registered for push notication? Is registering at google a precondition. I am not sure whether I need this or not. Thanks for update this thread.

Yes. Every app using GCM is showed as registered in microG-Setup. And this is essential as long as I read the issues section of NanoDroid - https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md#issues - massive battery drain can happen, I´ve encountered this with Threema until I´ve re-registered the GCM-Token through the troubleshooting feature of Threema. And yes, as long as I read the documentation - without device registration GCM won´t work. You do not need an account, since GCM relys on device-id as long as I understand.

Read the "Push Messages" Section of NanoDroid carefully. Even restoring data of an app does sometimes not help - this IS the case for Threema - since the Push Token is stored in App-Data somehow. If your App does not support a manual re-register und you must rely on restored data, try to re-register from CLI:

Taken from the Issues of "Push Messages" section of https://gitlab.com/Nanolx/NanoDroid/blob/master/README.md#microg
"...when restoring the ROM from a TWRP backup GCM registration for apps is sometimes broken. You may use the following command to reset GMS settings for a given app using it's appname, or if no appname is given for all applications. Apps will re-register when launched afterwards:

nutl -r APPNAME (eg.: APPNAME = com.nianticlabs.pokemongo) or nutl -r
..."

GCM works like a charm for me, even with the long time being unusable Threema App in microG ! Threema now even works in "Battery saver" mode., what mainly reduces CPU frequency from my understanding. Battery life of the LOS-microG-20190412 is incredible !

 

[cyberbix]

Wifi problem, MAC 02:00:00:00:00:00

Please guys, hope someone has a good idea what might be the reason here.

I encounter exactly the same problems and I think McFy knows about the actual Wifi kernel problems. WiDi, Wifi Cast, WiFi direct, P2P - however you call it - is still not working in LOS 16. In LOS 15 WiDi works like a charme.

What I can say - I´ve got rid of ALL my WiFi problems after device encryption. Even the WiFi state from powering off is restored. But be careful - you MUST use the "ask for PIN" option from LOS device encryption. Otherwise it won´t work. The "fast boot" option brings the same effects.

I know this sounds funny, but I assume there is a timing problem on loading the kernel module during normal boot. The boot delay caused on an encrypted device by the PIN dialog, could be the thing that solves this. But I don´t have a clue of it and maybe this idea is complete nonsens

The WiFi problems occur in LOS 16 and in LOS 16 microG versions. No difference here (of course it should be the same kernel module)

So let´s wait for a possible solution from McFy on this....

 

[LuChaos]

Hi,

nice smooth ROM. Thx @ McFy!

On my phone with current LOS (190412) and magisk 18.1 the camera doesn't focus the real distance. Photos get blurry.

Has anyone the same problem?

 

[Filipe Baltazar]

Hi,

nice smooth ROM. Thx @ McFy!

On my phone with current LOS (190412) and magisk 18.1 the camera doesn't focus the real distance. Photos get blurry.

Has anyone the same problem?

Are you using the pre installed camera app? Don't use it, it's crap. Get the Asus camera app apk, not available on the App Store.

 

[LuChaos]

Are you using the pre installed camera app? Don't use it, it's crap. Get the Asus camera app apk, not available on the App Store.

Thank you Filipe! :highfive:

The Asus cam is tremendously better! Very good hint!
Focus is still a bit strange but OK.

Footej cam is equal bad as LOS stock cam atm.