yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] y2kadir:
just for information:

I used this rom now for up to 3,5 months. I now changed back to official oreo.

The reason is, that this rom is not stable enough for me on a320fl. randomly reboots or bootloops and main function phone is not working properly. I had big issues with phone calls, which was the main reason to change back.

I think that all other things are not the problem, but phone is only a phone if you can use it as minimum phone.

I thank mcfy for his work and also donated for that. I hope we will here some news if Android P will be available for A3 from him.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ItsMeEgar:
BUGS

SM-A320FL

BUG:

- Bluetooth can not be deactivated after it has been deactivated

moreover, there are no other Bugs
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
I started to write down my experience here:

https://xdaforums.com/samsung-a-series-2017/how-to/live-gapp-fdroid-yalp-microg-los15-1-t3839518

Is it an early stage, I am not finished, but feedback is welcome. I will try to refine it later, if I have more time.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
The issue with Yalp is not as expected the logged error with libstagefright.so - although this should be addressed too.

It is the Downloadmanager of LOS15.1. There is an option inside Yalp to use an own internal downloader - and this works.

This makes my A3 now ready for real use. Probably I need some more time to set it up completly, but now I am confident it will work. I just can hope that our dev McFy doesn't give up providing us with updates. Even if there are no big changes, so at least normal LOS and security fixed will be included.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Seems I am writing just for myself here. ;)

I just want to transfer my wifi-passwords from old to new phone - and it doesn't work. I found, that Oreo seems to store that in another file (*xml) instead of .conf. Ok, that is just annoying, but ... passwords in this xml are readable !!! Seems not to be cute. :(
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cyberbix:
Hello starbright_,

of course not ! Thanks a lot for your MicroG post in your dedicated thread. I´ll try your setup today or tomorrow and give you feedback.

Actually I´m on a beta build from McFy ( build 53 ) that fixed the dialer issues. Unfortuntately the boot stucks and boot loops after entering decryption PIN are not gone. Also the reboot after power off bug.

But (speaker)phone is working excellent now. I´m pretty sure McFy will fix that finally.

I´m also happy with battery usage, two full days from a 100% battery with average use and airplane mode during the night.

It will be ready sometime, I´m sure. Let us just be patient !
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ruffyrisco:
:good:

That is good news!! :cool: I'm back to the april build because of the heavy battery drain (less than one day) of the latest build.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
[MENTION=8727859]cyberbix[/MENTION]:

Where did you get beta builds? Are your WiFi passwords unencrypted/hashed too? (/data/misc/wifi)

Please give me feedback for the microG installation. I guess it has to be refined. I did have not much time and want to give at least some keywords.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neutron1312:
Hey [MENTION=7698739]McFy[/MENTION], a huge big up and thank you, for this release. It fixed all errors, that encountered during my daily usage. And it's super stable.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
After set up I found that this mobile doesn't have a notification LED. How strange is that?!? I didn't check this because this was part of even less expensive mobiles - one of the most important things.

Anyone knows how this can be emulated with less effort? Maybe the keys-background LED can blink.

I found for older Samsung devices a thread:

https://xdaforums.com/showthread.php?t=823922

Does our kernel supports that BLN?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] emin93:
Wow, flashed the latest image and I'm very happy about the stability & performance. Running this as a daily driver for two days now. Excellent battery life as well! Thank you for the great work!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ruffyrisco:
Strange. As I tried the latest release my phone last about 10h only.... Very heavy Bluetooth power consumption. I made a clean install but maybe a weird app is restored via my Titanium backup restore.... Maybe I should try again and be more careful what I am restoring. :confused:

Is everybody else satisfied with battery life?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] equatorius:
Does that include GSM codes (call forwarding and such)?

I used a bunch of Samsung android phones over the last ~8 years (either used them myself or bought/configured them for friends/family) and can't recall if any of them had a notification LED or if any OS (stock or custom) allowed their key-backlight to be used as such (may be there was a buggy implementation for the S4 Mini LTE with a custom CyanogenMod kernel but I never used it and I doubt it was merged into the official CM sources or even just carried over to later CM versions from the same developer).

And this specific model has AlwaysOnDisplay feature (I mean the stock firmware and some of McFy's Lineage builds have it working, at least partially) which could give you notifications. And then there is Ambient Display (just wave your hands over the phone to temporarily activate the lockscreen and check notifications).
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
As a replacement for the missed notification LED I found the NoLED app, but in fact the key-LEDs are my favour. Also this is closest to the original. Not

Right now there with McFy's ROM there is a "when device is moved it shows something". A nice feature but I don't want to move it to check for new messages. If I remember it right the "always on" feature is either still buggy or too power consuming.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] NiEb:
VoLTE and Wlan call failed (Telekom).

Switch to 3G
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Battery life seems to be acceptable (2 days of moderate useage with overnight flight mode). But it is all quite new to me.

Bluetooth show high power consumption, that has been reported before. I guess it is just a wrong value in the power_profile.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cyberbix:
Unfortunately not. The call forwarding still does not work.

Yes. An unencrypted XML with the SSID´s. Since my phone is encrypted I dot not care too much about it. Boot loops are more annyoing than that ;)

See your extra Thread. Worked like a charm.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] jediafr:
My experience.

Fisrt a big thank you for all the work and care you put into this rom.

I'll detail all the cons but i want you to know that i really appreciate this rom.

I've already installed roms on my various Nexus 7 tablets but this was the 1st time for the A320F.

1) It took me a long time to figure out how to boot on TWRP (uncheck autoreboot / after the greened "PASS" please hold Power+Home+Volume DOWN until the screen blinks THEN hold Power+Home+Volume UP).

2) After installing the rom i experienced several loops during the initial reboot.

Had to Power+Home+Volume Down to get out of it.

It happens also after a reboot from TWRP (after a full backup).

3) Many Gapps packages failed on me (i.e googplay play crashed constantly after install.

I finally managed to get open_gapps-arm-8.1-pico-20180913 to work but it left me unsure how reliable the phone is after that (neither LOS browser nor the LOS email client work afterward)...so i've decided to "degoogle" the phone by reflashing the rom and substitute every google app (it is a lot of work hence a lot of backups...).

Even there i'm experiencing some crashes (sometimes the phone reboot), placing a call

may also crash the dialer into a permanent call state if you activate the speaker whilst dialling the number.

The Battery seems to be holding well (comparing to the same usage/settings with samsung stock). I'll live with the config to see if it is stable enough for day to day.

On my 3rd day, i'll keep the rom for day to day usage even though i'm still experiencing the occasional crash (quick replying twice from the notification bar to a sms did it).

Bluetooth audio works well (been streaming music on speaker for an hour wih 2% battery drain).

After 2 two weeks with LOS 15.1, i've grown attached to many quirks...

I still experience crash (often after a clean reboot). The battery holds below average despite not having installed Google Services.

I've found that LOS' MTP implementation is fllooding my desktop with errors when connected to the usb (leading eventually to a complete shutdown of all disks operations on my linux desktop). It doesnt matter if i choose Charge only, the problem happens anyway.

cf extracts from my syslogs logs

Sep 25 22:15:42 jda-pc gvfsd[772]: Error 2: PTP Layer error 02ff: Error getting friendlyname. Sep 25 22:15:42 jda-pc gvfsd[772]: Error 2: Error 02ff: PTP I/O Error. the lines are numerous.

On comparison, the Stock rom behaviour was ok.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Can this just installed over the latest "official" release. It is just 4 days newer - is it worth?

I am new to telegram, seems very confusing to me ;)

What about notifications? Does pushservice (ringing ...) works?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] dpl_dpl:
Not possible to set custom APN

I'm unable to set a custom APN. Until recently, I used the May release without any problems (in Europe). Now I am in the US for work for two weeks and bought a SIM card which requires custom APN settings.

At first, I got always the error “Access Point Name settings not available for this user” and in particular, I couldn't add a new APN. Then I tried options that turn up when googling this error message (unfortunately I'm not allowed to post links here). In particular, I tried changing permissions in and examining the providers/telephony folders, creating a custom APN through adb, etc.

I also updated to your recent August release, to see if that helped, but I still have the same problem.

The good news is that at least the manual addition of an APN via adb makes that new entry appear in the menu, whereas when trying to add one through the phone was and is not possible. But still, it does not work :/

In this thread here and also in the links one gets when googling, it is advised to play with "*#*#4636#*#* ". But I only get a menu on "Phone information", "Usage statistics", and "WiFi information".

Can you give any advice or does anyone else have this problem? I found two unanswered posts here (search for "APN") who also had trouble manually setting an APN.

Another thought that crossed my mind is whether there is some form of region locking, but I then I think would have noticed via a lock screen, and also, I believe the A3 is supposed to unlock as soon as I have over 5min of calls in the region where it was purchased (which is definitely true).

Thanks for any hints!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cyberbix:
You can do a "dirty" install, but take care on side effects. Wiping system partition is always a good idea, but Magisk and modules has to be done again. If in doubt if a clean install with wiping data is needed, ask in the forum. I do not know to much about the dependencies.

It´s just the speakerphone problem that has been fixed. All other bugs still occur. So wait for the next release from McFy.

If it´s about quick restore of APK settings, take a look at the Magisk Module "App Data Keeper" (adk). This module can help you keeping all your settings easily. Works for me for most apps.

https://xdaforums.com/apps/magisk/magisk-module-app-data-keeper-adk-t3822278

If you mean Threema push service notification/ringing:

- Yes - using Gapps everything related to GCM push services works fine, INCLUDING Threema.

- No - using microG everything related to GCM push services works fine, EXCEPT Threema push notifications and ringing. Not even using Threema polling instead of GCM helps.

But this has nothing to do with McFy´s build, it´s a well known problem with microG and Threema. See several XDA threads regarding this issues.

Moreover, Threema often has notification problems even on stock builds with wakeup and GCM. See Threema support for issues. Often resetting the push token and disabling battery optimization for Threema helps. Has nothing to do with LOS or this build.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
As push notification (whatsapp/telegram) doesn't work without microG I did the following. Installed Magisk and from Magisk I installed Xposed, and there the Fakestore. Than I flashed nandodroid. Selfcheck is all green. I deleted Whatsapp/Telegram and installed it again. I started them, gave them permission but didn't configured it completely . But they will not be registered.

I want to restore settings with TB, but look - it doesn't find su -althoug I could give root a few other apps a few minutes (and reboots) ago.

What's wrong there?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] megacar@gmail.com:
Hi all,

using the latest build (without gapps) everything works good. Using Here Maps, GPS working fine. But there is no Location tile in quick settings and I dont see a way to add it? Every time i have to go to settings -> security and privacy -> location > on/off to toggle it. kinda annoying. Any ideas?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SnowFuhrer:
This would probably work. Just chang the word: https://www.xda-developers.com/how-...ttings-tile-toggle-on-samsung-galaxy-devices/
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cyberbix:
Nothing. Just read carefully what TB tells you ;) TB does not recognize Magisk as SU, but it works.

Tested this along with your microG setup instructions. TB works like a charm.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
After a reboot it recognises root. If it doesn't recognise it, it would not work (as I remember right).

So that step I've done. But restoring apps doesn't work: parser error.

According to TBs FAQ it is a question of "bad" busyboxes...
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cyberbix:
Try installing Magisk busybox module. Helped me with other apps needing a busybox implementation.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
If I do it again, I probably use LOS-addsu. Until now I did not need the functionality of Magisk to hide root. Did you?

Does your A3 is stable? I am wondering what did I do wrong. To bad I missed to create crash-logs.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] rofi-zone:
I agree with you. I also used this rom for some months now and I am thinking about going back to an official version. I am also using the 320FL and it's just not stable, especially with the phone calls...

I wish there would be an update which fixes this, because in all the other aspects it is a very good rom.

Thanks to mcfy!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] leo31:
for month????

i installed this rom on my phone for 30 minutes, and back to stock oreo.

very unstable, cant be my daily driver.

but [MENTION=7698739]McFy[/MENTION] did his job, better than any other.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ivlivs:
For me it is much better than stock, also been using it for months. Loudspeaker is the only major bug.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cyberbix:
I use Magisk because of the modules, not to hide root.

My A3 is almost stable except of the boot loops/boot stuck after entering decryption pin.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] steosteo:
I am having the following issues with the latest build:

- Some messenger apps do not sync in the background. Messages are only delived when the app is actively opened, although background data ist enabled for the app. I even tried deactivating battery optimization and it still delivers only when the app is manually launched.

- An automatic reboot occurs most of the time when trying to turn it off after the phone was on for some hours. The second shutdown works.

- Some built-in apps like camera and email stop working randomly and crash every time until the device is rebooted. After that, they work again.

I installed the built with the unofficial TWRP provided by McFy, as well as the pico gapps.

Any suggestions?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] macbeth1:
How to change in-call volume on this phone? Pushing the volume buttons during a call doesn't do anything and there is no appropriate option in the settings.

I may have had the same issue with the stock ROM, but I don't remember for sure.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] elteror:
I got exactly the same problems.

- I cannot open my emails, k9 mail and the email app crach

- Whatsapp is sync only when I open it

- Everything worked fine at the begining but not yet anymore...

I dont use GApps, only FDroid and Yalp

If someone know where it comes from?

Thanks!

A320FL - TWRP 3.2.1.0 - LineageOS 15.1
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Just want to share my experience moving from a LOS 14.1 mobile (another Samsung) to this 15.1.

From my experience most of my trouble is caused by usage of Titanium Backup. Beside the fact that I have not been able to transfer data of apps it seems to make the device unstable. Don't understand why, what might be the reason, but that's it.

TB even gives Parse errors recovering the backup that has been created with addsu and restored with Magisk. My conclusion -> just forget about this, do it from scratch. I spend so many hours and days, you will be faster set it up from scratch.

For a very view apps I copied the data with adb. It is of course far less comfortable, but this is only required for a limited number of apps.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] oliver.h:
great work

Hello McFy!

I would also like to share my experience with you:

Last build i used was the one from april, now i got the one from august on my a320.

=> very fast, very stable

=> i do use it with gapps pico > no troubles

=> battery consumption is much much better since the build from april!!!!

=> no more echo when calling

bugs:

=> pushing the loudspeaker button while talking on the phone crashes the image (this was also a bug in april)

=> cannot sync gmail with the default email app

=> default camera sometimes not working

=> plugging in and out the USB cable very often crashes the image

Thanx for your great work!!!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ruffyrisco:
I did a clean reinstall and now I can confirm that the battery life of the latest build is great! Much greater than of the april build. :good:

Great work, Mc Fy! :cool:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
I tried 2 messengers, WA and Telegram. The second one seems to work fine, even with micoG.

I disabled battery optimization for both. WA is noticed in microG, but not registered, Telegram not.

Nevertheless I get incoming calls with Telegram (phone wakes up from deep sleep) but not with WA.

Used the apps from Yalp (some say there is a difference between Yalp and FDroid telegram app)

Never used build-in camera-app but opencam instead. No problem so far.

It happens to me, that a boot into recovery is doing just a reboot, so maybe it is similar issue to your reboot.

After a clean install without usage of TitaniumBackup I doesn't have forced closes anymore. So for me it is stable enough for daily usage.

I can confirm that transferring data via USB seems to me not so stable at all.

---------- Post added at 07:38 AM ---------- Previous post was at 07:32 AM ----------

That doesn't help me. I am not using it anymore - get to much trouble with TB.

---------- Post added at 07:39 AM ---------- Previous post was at 07:38 AM ----------

Same here - you are not alone ;)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] steosteo:
I believe I figured out this problem concerning Whatsapp. It's about the G-app "Google Play Services". It appears that Whatsapp uses this to maintain its permanent server connection and to push messages. After I enabled background data for this app, notifications work without first launching Whatsapp. It would also explain why people have this problem without any G-apps installed.

---------- Post added at 17:48 ---------- Previous post was at 17:41 ----------

So this leaves the following issues with this rom for me:

- Automatic reboot when turning device off after it was running for some hours. Subsequent shutdown works.

- Some built-in apps like camera and email stop working randomly and then crash every time until the device is rebooted. After that, they work again.

...and the following new issues:

- Occasional bootloop that can only be fixed by forcing reset. Subsequent reboot works.

- Connecting to wifi takes up to several minutes (device connects "without internet" and drops connection again dozens of times until it finally works)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Filipe Baltazar:
The August 22nd build is very stable for me, as long as I don't use Gapps.

How do I install the full MicroG suite on this phone?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Filipe Baltazar:
Update: 85% Stable.

Install twrp, format data, flash no-verify, flash RMM-State_Bypass, flash LineageOS build, flash MindtheGapps. Done!

For root access: download Magisk manager apk, download flash file from application, reboot and flash. Done!

Battery: Amazing, maybe slightly better than Stock Oreo.

Bugs: Reboot option doesn't always work (shutdown and booting up again works perfectly fine though); overnight the front buttons stopped working (nothing that a reboot doesn't fix); performance may be on par with stock but animations will lag once in a while (trebuchet needs some tweaking).

Camera: Decent, not as good as stock. Has anyone found a way to install a Pixel camera port?

Conclusion: Stable enough for daily use as long as you don't mind rebooting maybe once a day. Not recommended for picture addicted people (seeking professional help is preferable).

Outstanding job [MENTION=7698739]McFy[/MENTION]

If the next RR or LOS is even slightly more stable than this build I'll buy you an imaginary cake. Can't wait for LOS 16.1 based builds, they match the contours of this phone.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] equatorius:
The photo related mental issues come in all shapes and sizes. My multi-function printer died last week and I am using my phone as a "poor man's scanner" since. I just can't find the strength to force myself buying a new one because I hate printers in general and these low-mid price range consumer grade machines are my sworn enemies.:eek:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Described my experiences here:

https://xdaforums.com/samsung-a-series-2017/how-to/live-gapp-fdroid-yalp-microg-los15-1-t3839518
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Maybe a stupid question:

I don't have a lockscreen yet, but want to save it with fingerprint. It seems not to work. I can only create a fingerprint with a PIN. And even after creating a fingerprint it is not possible to open the device with just the fingerprint. Is this a general issue or a current LOS problem or is just our device suffered. Do I need to encrypt the device for that? Many questions, I know ;)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
Wow, lots of fixes... Gonna try it again soon!