yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] lgui:
Some feedbacks

Hi,

First of all, big thanks [MENTION=7698739]McFy[/MENTION] for your quality work :)

I recently acquired a A3 2017 (A320FL) to succeed my old broken S2. I've flashed it with your ROM, as my S2 was under LOS.

Since i use it for few weeks now, I can give you some feedback :

- Like some others users, I've noticed a inhabitual battery drain, both on LOS and RRemix ; after further researches, it seems that NFC is running in background somehow. I disabled it in dev options, but the battery drain was still running. The memory informations shows some abnormal percent usage compared to other services (Dev tools activated > System > Dev options > Memory > Apps launched on start > NFC Service > Tap again on nfc logo).

I've disabled the service through ADB (.adb\\ shell pm disable com.android.nfc) but there was still signs of activity after a moment or after a reboot, like if the service was reactivating himself somehow..

So i desinstalled it with ADB command (.adb\\ shell pm uninstall --user 0 com.android.nfc), and it seems now quiet... \o/

Since then battery seems to have recovered a normal drain! (min 2 days in normal use)

- Screen touch remains active during a phonecall, which ends sometimes with a uncontrolled end of the conversation...

- Camera doesn't take pictures when flash is forced active.

- Bluetooth doesn't seems to work, i simply can't turn it on. Whenever i try nothing happens and battery drops a lot until i force the stop in BT service.

- I miss the wake up on double tap fonctionnality :) it is visible on options but doesn't seems functional ? And what about the led notifications options in further releases ?

Even with these bugs i am very satisfied by this ROM :) thank you again for your work !

(and sorry for my bad english also..)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
oh crap, wrong subforum

well anyway,,,im on another rom now. BT was also not working but someone found out that if you again wipe dalvik it works again. You could try.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Asgabat:
guys how can I copy LineageOS sounds and install to regular firmware?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] lgui:
NFC

I tried with no results :( but thanks!

If somebody is interested, here is the process i followed to desinstall nfc package :

- Install ADB Fastboot for windows for example

- Plug A320FL in USB (you will need USB drivers installed)

- Activate USB debug activated in dev options + root access for adb

- In the folder (for me path is "C:\Users\YourUserName\adb-fastboot\platform-tools"), right click anywhere in the window with Shift pressed, and select "Open PowerShell window".

Use theses commands :

display connected devices

.\\adb devices

grant root access

.\\adb root

enter shell

.\\adb shell

list installed packages (to have exact name of the package)

pm list packages

uninstall nfc package for user 0 (this operation is irreversible unless your flash the ROM again)

pm uninstall --user 0 com.android.nfc
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] potyqa:
Or you can delete the NfcNci folder from /system/app with a root explorer, it's way simpler :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] +julez+:
some problems

Hi and first of all thanks for your work.

There are some smaller errors happening on my phone with this ROM, it´s not impossible that I´m just a bit dumb though.

1. My contacts disappear randomly and after every restart. I have to reimport them from the vcf file every time. Is there something I can do to stop that? The contacts are not synchronized with any app, I just want them to be saved on my device (sync is turned off).

2. One of my two registered mail accounts (yahoo, under settings -> accounts) also disappears in the same way. Maybe that could be the reason why a paid app (poweramp) cant´find that account on my phone, evenwhen it´s still showing up. (update: helped myself by using a very old version of the app)

(3. Another thing is a freezing phone right after restart. Lockscreen can´t be unlocked sometimes, it doesn´t react in any way. Not a big deal for me, just telling.)

Sorry if I´m wrong here and sorry if I´m being stupid but any help would be very much appreciated.

Thanks and have a lovely day,

Julez

Edit: Could it be an issue that I don´t have any google apps installed (google play services e.g.)? And if so, can I use contacts without google somehow?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] lgui:
Yes ! i was at first searching for a way to kill the nfc service, without uninstalling it, that's why i used terminal and i continued with it.

But you're right it's way simpler with root explorer :)

Yes, I personaly use DavDroid to sync my contacts with the native app android
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] dplasa:
Is there any chance this is going to become an OFFICIAL build with automatic updates?

Thinking about what phone to buy next... :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] y2kadir:
thx for the informations and good holidays.

but I don't know which other problems do people have with Bluetooth?? the only problem is to reactivate Bluetooth after deactivating it. so I have connected and do not turn off and two devices at same time ( jbl tune and pebble time) work without any problems.

see you next week.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cyberbix:
Not at all. Even with this workaround, I see a massive battery drain from the bluetooh process. Even with no devices connected. Take a look.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] dpl_dpl:
Thanks, wifi issues, and my MacOS instructions

Dear McFy, thanks for this wonderful work, merci beaucoup !

Today I had a small funny issue with wifi, where it would always automatically turn itself off after a few seconds. I restarted a couple of times, reset all connection settings, restarted some more, and eventually it now seems working. I can't say anything about steps to reproduce, just seemed completely random.

Also, for anyone like me, who is very inexperienced with custom ROMs, I put below some more detailed steps on how I managed to get this installed with root and Google Apps using a Mac:

1. Download four files: download the McFy's Lineage OS latest build, download Gapps for Oreo (I used "mini"), download McFy's TWRP .img , and download latest magisk zip

2. Download and install on your Mac the unofficial heimdall suite 1.4.1 for MacOS (command line only, as I had known issues with the official / front-end 1.4.0 build

3. skip everything related to Jodin3, as it had a known bug for me (although YMMV) where it would always get itself a corrupt PIT file, or it thinks it was corrupt

4. Download and install on your Mac the Samsung SmartSwitch package, which will provide the USB drivers

5. install adb on your Mac via "brew cask install android-platform-tools"

6. Enable USB debugging on your phone, restart it in download mode; Then on my Mac I had to do an adb kill-server and adb start-server to be able to see the phone

6. flash TWRP via "heimdall flash --RECOVERY recovery_a3y17lte-050318.img"

7. restart phone in recovery mode; wipe system, data, cache and dalvik cache; I also re-formatted.

7. use TWRP's sideload feature to install lineage os (first!), gapps (second!, don't restart inbetween), and magisk. While the phone is waiting in sideload mode, issue for each item, on your Mac: "adb sideload file.zip"

8. voila, you're finished, no need for Jodin3 or anything.

Thanks again McFy ! Awesome work :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] felix_d:
Thanks for the built!

Everything works fine, except for one (rather annoying) issue: I can't unlock the screen by just placing my finger on the fingerprint sensor or bei pressing the home button. If I do that, the screen just turns black (also the clock from the always-on-display disappers). To unlock the phone I have to press the press the on/off-button first and then place my finger on the sensor... this is kinda annoying as it requiers one step (and one finger) more to unlock the screen... any ideas how wo fix that?

Thanks in advance! Cheers!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Hello folks. I'm facing a little issue here.

In order to root this ROM I've flashed SuperSU (last version 2.82), but I can't see a SuperSU app, developer options only give me the "adb" root, and anyway apps that use root (f.i. ES explorer) aren't asking me for root permissions. I wonder if I'm having root at all.

Which root are you guys flashing? Previous times I flashed Addonsu (the ones you can download from LineageOS site), and also Magisk, but because I had big issues (don't know if related with root), this time I've thought of SuperSU. Also I've read some post recommending it.

Any help? Thank you.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Hmm, since you tried a lot root methods and there are no complaints by others with Magisk and others maybe something went wrong during unroot process? Did you flash the original boot.img after unroot zip and let the ROM boot once?

If that doesn't help then I would clean flash again.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Thank you [MENTION=7726355]Pat750[/MENTION]. My roots, as roots, always went fine. What I don't know is if my (totally unusual) freezing issues were related to roots or not.

Now the funny thing is, with SuperSU I can do root things. I can, for instance, open a terminal, type 'su', and there I am with the root# prompt.

What surprises me is the fact that I don't see a root app and I'm not asked for confirmation when apps take root access.

For the rest, I don't know which boot.img you mean, sorry. I've just flashed (very clean) the ROM and the SuperSU zips. None has a .img suffix.

---------- Post added at 01:20 AM ---------- Previous post was at 01:12 AM ----------

+1
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
Hmm, strange why it doesn't work with clean flash and SuperSU, I have no solution.

The boot.img is in the ROMs zip file and contains the original kernel and it should be flashed after unrooting process so there are no root leftovers.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
[MENTION=7726355]Pat750[/MENTION] Thanks for the explanation. Good to know that.

Anyway, and much that I LOVE PrivacyGuard, I'm giving up on this ROM for the Nth time: I'm facing too many issues despite all the pain I've taken in a really clean flash: NFC bug, apps misbehaving, loudspeaker low volume, playing audio files halts on earphones' volume buttons, no Whatsapp notifications...

The bad news is, there's no other alternative: either stock or McFy's. Maybe in the future, if this ROM is updated before I change phone, I can give it another try. For the moment it'll be stock.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] glycergic:
I tried to flash a stock rom for A320F (which is my phone) with odin, and it failed. A quick search brought me to thinking that it's not the right rom. Then I checked, and indeed this Lineage15.1 says A320FL, so that means I have to flash a stock rom for A320FL? Also, the ones I found were for mostly north-african countries or eastern europe. Does that matter? The phone is from western europe? Especially the russian one, does that mean it's in cyrilic?

Just hoping this won't brick the phone. I'll keep you posted.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Definitely not, that's for sure.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ArjanTel:
Expanding internal memory with SD supported?

I was wondering if this ROM supports expanding the internal memory with SD cards? It is not supported by samsung on the a3 and a5, but it is supported on the galaxy s-series.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Bug Privacy Guard read/write permission to External storage Always ask

( [MENTION=7726355]Pat750[/MENTION] I know you're going to laugh at me, but, man, I couldn't just give up! :D )

( [MENTION=7698739]McFy[/MENTION] I think you're on holiday, but this is what you asked me about.)

Hi all. I believe I've finally identified the bug that was driving me crazy about this ROM, which lies in some of the apps' permissions to read (or write) external storage. Here are the steps to reproduce:

Settings-->Security & Privacy-->Privacy Guard.

Scroll down to Whatsapp (some other apps behave the same), then press and hold.

Scroll down to Read/Write external storage and change from "Allowed" or "Ignored" to "Always ask".

CAUTION!!: make sure to also switch off "start at boot", or you'll get yourself into big trouble.

Now force-close Whatsapp, then try to launch it again.

Here's where the bug shows up (at least in my device), like this:

The system freezes and everything becomes unresponsive (except for Home and Power buttons, but to no avail). After some 30-60 seconds (the screen may first have dimmed totally, or not) the phone soft-reboots by itself and, once it boots up, everything works fine; BUT if you try to launch Whatsapp again, the process repeats over. For returning to a totally normal system, you need to change back the Privacy Guard permission to external storage that you modified: "Ignored" and "Allowed" values are fine; only "Always ask" triggers the bug.

So far, this doesn't look like a severe issue, but it is, because if you happen to change to "Always ask" the aforementioned permission for an app that is set to start at boot, then you are in deep s**t, because the device starts an infinite bootloop out of which you can't get unless you manage to boot to Recovery and, I'm afraid, wipe your data partition. (Except if you know another way of resetting Privacy Guard from Recovery, or pehaps -I didn't try this- find Whatsapp folder in Recovery file-manager and delete it.)

Therefore, even though not many people tamper with Privacy Guard permissions, guys who are concerned about privacy are likely to modify them.

I wonder if this bug belongs only to this ROM, or is LineageOS's.

[EDIT] Well, answering my own question above, it seems that the bug is not exclusive to this ROM. I've found exactly the same behavour here: https://xdaforums.com/showpost.php?p=75494487&postcount=1921. Therefore, it must be upstream. Anyway I leave the post here for the sake of information.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Pat750:
[MENTION=4222902]zogoibi[/MENTION] no, I'm not gonna lough cause I haven't used that setting that much, so this is new to me.

But I'm shaking my head how you were dealing with the ashyx situation in TWRP, but that's not for me to discuss...
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
[MENTION=7726355]Pat750[/MENTION] Oh! I said "laugh" because I've posted in this thread two or three times already that I was "giving up on this ROM".

But now I'm happy I kept at it, because knowing how the bug works, it's easy to avoid it. Now I have the working operating system I was looking forward to have in this device, and I'm a happy user. :) Actually LineageOS is a great ROM and [MENTION=7698739]McFy[/MENTION] is doing a great job.

So far, the only remaining issue (besides loudspeaker's low volume) is NFC, yet in my device (A320F Duos) it works fine as I long as I don't switch it Off, because then sometimes it doesn't switch back On until a reboot. Anyway, I've realized that many banking apps aren't happy with customized ROMs and/or rooted devices, so thereś not much use for NFC the way I'm interested in.

In any case, I suppose it would be useful if someone else could try to reproduce the Privacy Guard bug. But that's for McFy to decide.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] apelamod:
Is there phone call issues still? Last time my last version another not hear my voice
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] y2kadir:
yes with last version you will have this issue, the other side will not hear you if push the power button during call. but you have to be carefull by doing phone calls beacuse the touch display will stay active even if display is black from proximity sensor.

I thing its time for a new release from [MENTION=7698739]McFy[/MENTION] but I know its not so easy...
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] felix_d:
Anybody else facing this issue?

Or knows any solution?

Further, I can confirm the issue that during a call the display doesnt turn off and therefore it happens easily to press a button (e.g. quit the call) with your ear/cheek...
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
Hi,

I don't know if this come with this rom, or from my custom nougat rom (just a debloated rom from stock, that i have made myself..)

But i would like to flash the official oreo rom (xef), and i couldn't. My phone say : "SW REV. CHECK FAİL. DEVICE 2 BINARY 1"

Is this rom come with a much newer BL than french stock ?

Best regards.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] glycergic:
I've just reflashed the stock rom, flashed twrp 3.2.1.0 and then this rom, and I have the same issue> No apps appear to install from 3rd party source.

cfr. https://www.theandroidsoul.com/where-is-install-from-unknown-sources-option-on-android-o/

I don't know what to do now :s
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] leo31:
use odin v3.13.1 for flashing newer version of firmware, dont use v3.12.3
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] potyqa:
What happens after you turn on the "Allow apps from this source" toggle? For me it works just fine.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
Oh thanks !

I was thinking that 3.12.3 was the last one ;)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] glycergic:
There's no applications showing in this screen, so I can't toggle anything on/off !

Someone suggested reflashing, but to no avail :crying:

Oh and it was working on the stock rom. Flashed with odin 3.13.3, wiped cache / dalvik.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
Low volume bug still present?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Try to turn of AudioFX, and yes for thoses who wonder why I didn't answered or shared news it's because I am on holidays :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] leo31:
i also spent 1 day struggling with the same problem until i realize v3.12.3 is not the latest version of odin :p
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ebi02:
telegram group

hi matt

please send link group

thanks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Hi added to the thread,

https://t.me/joinchat/EjsGTkzDb8xxVCxWMZsziw
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] wogooo:
ok thanks! ill try this as soon as im on this one again
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
I think I managed to tame the beast, but I'm still experiencing random reboots and, most important, oftentimes the system doesn't want to start properly after a reboot (either spontaneous or deliberate): in these cases, sometimes it reboots again by itself after a couple of minutes, one or two times, before a successful boot; some other times it stays forever in the LineageOS bootup animation and I need to switch it off with hardware buttons; and lastly, sometimes it won't boot no matter what, and then I need to restore a backup. Wiping cache helps at times, but other times doesn't.

Another issue I've come across is battery life: "Mobile network standby" is eating up around 40% the total battery use, which is a lot.

Anybody else is facing these problems, or am I the only one in this thread?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] y2kadir:
youre not alone. but all these problems are already discussed in these 70 pages. reading is better than asking the same questions. the rom is not final and the developer is doing its best to fix these things.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Please don't lecture me. Cluttering the thread like that is as bad as asking before reading. And what makes you think I didn't read? I buy you a beer if you find the posts where the same issues I'm reporting have been "discussed". Pm me with the results. ;)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
Weird, this issues are generally reported for the Resurrection Remix rom, not lineageOS.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
I've just found quite a few reports out there about "Mobile network standby" huge battery drain in several LOS 15.1 ports. So, definitely this is not McFy's ROM bug, but upstream LineageOS 15.1.

As to the totally random freezes/reboots, I haven't found anything yet. I'll keep experimenting and report if I come up with something useful.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
Random reboots. Or boot that finish in reboot, or stay blocked at boot logo, are some of the bugs reported in RR.

Best regards.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Hey guys, McFy is back (could see new commits) :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
Is this ROM close to be officialy supported by lineageOS just like A5 and A7 2017 smartphones ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] gteck93:
BUG (A320F/DS)

*If I set Always on display(ON) option and i want to unlock with my fingerprint screen goes black and I need first to press power button and after that on fingerprint sensor to unlock and show the launcher.

*After I root Lineage my phone does not have sound.

*After root Apps force close,SystemUI force close.

*Camera flash light is lower than stock.

*Doesnt want to play videos in facebook app.

*In developer option ''Force GPU rendering'' is ON by default ,that can cause battery drain.

*Games runs slower in Lineage.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Asgabat:
I wanted to backup Whatsapp messages to the Drive but it fails every time I press backup button. Does anyone know how to overcome that?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Seagold:
Are you using modded WhatsApp like Gbwhatsapp and Yowhatsapp?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Asgabat:
no original one from Play market.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yass:
Hello [MENTION=7698739]McFy[/MENTION],

If possible, could you look into integrating WireGuard to the roms (LOS and Resurrection Remix)? Purely for optimization and battery saving while using it, heres a link to the thread on XDA: https://xdaforums.com/android/development/wireguard-rom-integration-t3711635

best regards,

yass
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Hello, i won't include it on next build because it's such a kernel mod that charter of lineage don't allow, but I could make a kernel zip for it aswell based on lineage kernel that I could give you when I release next build :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yass:
[MENTION=7698739]McFy[/MENTION], thatd be great, thanks in advance!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] GuiLG:
Flip Cover ?

Hi,

First, thank you for your wonderful works, including TWRP, installations worked like a charm on my device.

This ROM also works great so far, but I do have a question regarding flip cover. I have the Neon Flip Cover, that works with a magnet I believe to lock and unlock screen when the case is closed or opened.

I've looked around and I've read about a FlipFlap LineageOS app that is preinstalled on some device and gets activated (a new field appears in settings) when a magnet is detected.

I didn't manage to get that effect so I was wondering if you implemented this Flipflap app, and you would have any idea for a workaround ?

Cheers,

Guillaume
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] gteck93:
When is next build release?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Hello, I tried to add it but no idea if it will work, if you want a workaround you can see some apps on playstore such easycover :)

Regards