yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] holmes465:
Judging by sources from github, you already have twrp for oreo, you can put it in open access? :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] antoniodangelo:
Hi,

If i installed this rom can used ums mass storage driver ? I can't use mtp to transfer file. It's very slow !!

Sorry for my english.

Thank you for help me.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Hi guys, I today have booted oreo, you can download it at https://host.mcfy.fr I will now work on fixing bugs, Enjoy oreo !
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Hey, bluetooth show wrong battery use, I check this...

Interesting behaviour, would be glad of this :k
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
Hi,

Apparently, with a new A320FL and your last ROM (20180821 version), I experienced a lot of very slooooooooow boots (the LOS logo does not stop after few minutes, must hardware switch off the phone). Then, following boot is time comparable to my galaxy S4 with crDroid (LOS 15.1 based too). I have had a message concerning encryption of my private datas... but not sure there is a link.

How to deposit logs ? (how to get them in the phone ?)

To be positive : when my phone starts, its very stable ;)

Last : I have already flashed different phones and I spent time to get the procedure running ... and find how to unlock the bootloader of official samsung OREO Roms (not complicated at all, but if not done, boot of TWRP and LOS is impossible even following the instruction of the FP ^ ^). Maybe the procedure could be mentionned in the FP ?

EDIT :Apparently, I was using an old recovery : recovery_a3y17lte-050318.tar, instead of 3.2.3... stil the same issues for booting

EDIT 2 : Updating the recovery does not help
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Hmm... Don't know if this is a good or a bad news, because if not bluetooth, then what has been sucking my battery juice so quickly?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] gteck93:
Will be released a LOS 16 build for this phone ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
That (long boot time) happens to me too. I interrupted this (don't know whether it is finally booting). With next start everything is fine. As I a right now struggle to get microG working and make some trial and error I blamed it to that, but might be it is a general issue.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
Hi McFy,

I don't know whether it is my A320FL or not, but when I enable internet sharing via WiFi, and disable it, I can not enable the WiFi connection again.

Fabien
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ruffyrisco:
[MENTION=7698739]McFy[/MENTION], thank you so much for the new release.

I have an issue with bluetooth audio. I can connect to my car and can access the a320fl and start audio transmission but the sound is coming from the phone's internal speaker. Can anybody else confirm this behavior?

With the older releases, audio was also transmitted via bluetooth, of course, and not only the remote controls...

edit: solved

After some testing I found out: The bluetooth audio transmission didn't work on other bluetooth receivers neither. I tried several headset and bluetooth boxes. All of them can be controlled (start/stop, ff etc) but none of them with sound. The sound came always out of the internal speaker.

Then, I remembered that I use nonstandard AVRCP 1.3 because my car is not compatible with AVRCP1.4 ( not displaying media information (track titles etc)).

I switched to AVRCP 1.4 (standard) just to make sure and with 1.4 everything works. After switching back, also AVRCP 1.3 works now...
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] glycergic:
Flashed the last build, and am still having the bug that I see "No apps" in the advanced permission 'special app settings' > "Install unknown apps": No apps. Even when I enable 'show system'.

Anyone else has this bug? Is it because my model is SM-A320FL ?

Quite annoying since I can't install anything :(
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] zogoibi:
Mobile Network Standby chews up too much battery juice

Unfortunately I must correct my first impression for this last release regarding Mobile Network Standby battery use: after various cycles, I've realized that it's as high as with previous releases. Unacceptably for me. I need to recharge almost twice as often as with stock. I wonder if this happens only to some of us, or to everybody. And if only to some, what may it depend on? :confused:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] equatorius:
I like the last build overall but I am still unable to control call forwarding (A320LF, the modem crashes while executing GSM codes). :(
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
I've seen your problem is solved. But with several audio sources you might answer my question:

Assumed I have a few BT-audiosources configured in my mobile. Is it normal that after enabling bluetooth it automatically connects just to the previous used device? All others I have to connect manually.

My expectation would be, that it scans the whether there is someone that is in the (already paired) list and connects.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ruffyrisco:
The phone reacts to the actual paired bluetooth receiver. That means, in car it connects to the car system automatically. My steering wheel buttons can start the bluetooth music streaming. At home it connects to a different bluetooth box and so on... :good:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] adXiy:
I was unable to install Lineage with the original firmware, so I replace dit with one (7.0) I found on sammobile.com

Now when I try to flash my A320FL with lineage-15.1-20180821-UNOFFICIAL-a3y17lte,TWRP tells me that the ROM is incompatible with my device:

Any idea why and how to get it fixed?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
[MENTION=9412661]adXiy[/MENTION]: Did you have the latest TWRP? As this should work with a A320FL.

Another idea might to update to latest stock 8.0

---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------

So you have nothing to do but enable BT (after you once paired it, so that it is stored in the internal list)? Not select the device you want to re-pair (I am not talking about first initial pair)?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ruffyrisco:
Of course not. Just jump into your car and audio comes from the car speakers... Just go for a run in the park and take your headphones and enjoy music through your headphones without manually switching and chosing... :good:.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] adXiy:
Thank you, the problem was indeed the TWRP version (3.1 instead of the 3.2 posted here). I've been finally able to install LineageOS.

Shouldn't the A320 phone be listed on twrp.me?

Now that I've been able to install LineageOS, a few questions/remarks:

SELinux is disabled, how do I enable it?

Things seem to work well so far, I just had a crash of the camera app when switching from back to front.

Video recording doesn't work, videos are corrupt (they do not play in VLC and their durations are multiplied 50-100 times)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] paf22:
Yes it is: Here

A search for "A3" or "Samsung Galaxy A3" also works well on that page :)

It's a kind of "known bug". Try Footej Camera or Open Camera instead. ;)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] adXiy:
Thanks, how did I miss that...

The recording of videos works with Footej Comera, but the same problem occurs with Open Camera as with the stock app.

And if someone knows how to enable SELinux (see Security settings), I am still interested.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Hey,

About video record :

The recording issue is related about the omx, I am currently investigating on :) I recommand you to use footej camera for now.

About sepolicy :

If you enable it you gonna have issues about some denials, I am currently labelling all denials to switch to enforced for next build.

Quick info that I judge important to tell you:

I gonna go back to the school and by this way have a slower rythm at the beggining of this year to get more time for my school stuffs which are importants, I am sure every of you will understand this. Don't worry I am not going to forgot or stop, just making priority where it's needed, and I assume current build is okay for majority of user, I might release a quick update when I will have fully finished to fix audio bug that some have, worked with raymanfx about it and got some progress so I wish to finish a new error linked again to audio and fix/test prorpely that all is fine before send it here ;)

So about lineage 16: I gonna work on but pie isn't an update I really like for many point on the UI, I gonna do it but this is a hobby for me, respect that it's a long work and nothing is easy to do, I gonna do it just wait it without asking ETA, for now I prefer finish to fix all last issues with Oreo, a work yet almost done and that's what give me motivation !

Regards
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
I think I am speaking for majority here. A stable Oreo is much more important than a somehow working Pie. And of course we understand your priorities. Whenever we can help by testing - let us now. I am not able to cook, so I can only test releases. Maybe some update steps in between (betas) might make sense - of course not for all users here, but this is something you can decide, whether this make sense.

For me there are few reasons for using LOS. First, I get used to the features and don't like the vendor specific stuff. And second, I want to gain as much privacy and less Google than I can achieve. In this respect I go for rooting and microG as replacement for Gapps. Getting newer OS and better security updates is a another point. As this is the last build device <5" (except the Sony Compact, but even there the newest is 5"), I will stay a long time with this device.

Now my personal part. I am right now struggling a bit with instabilities and strange issues. Boot time is sometimes long, sometimes I can't download although I have connection and firewall doesn't report blocking, Forced Closes ... That might not be origin by the ROM, but by the collaboration of Rom, Magisk, Firewall and microG. Magisk is new to me and might increase complexity. Maybe I go back to addsu. I will open a separate thread for those who are interested. For me this is a edge - either it is general, or it is device specific. I can't really know. Probably I have to learn more about understanding log files...
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
Hi,

I would have a request : would it be possible to be fully compatible (patched) with DriveDroid ? (https://xdaforums.com/showthread.php?t=2196707)

Apparently, the CDRom mode is not available at the moment.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] antoniodangelo:
Hi,

I would request me too. It's possible to enabled usb mass storage function ?

It's very important for my job. Mtp is very slow to transfer files.

Thanks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
After several days of testing, this update is really successful!

I encounter only one bug, during a phone call, if it is me who hangs up, the touchscreen no longer responds, forced to restart. But I can live with it ;)

Concerning AOD, I have tried many applications in the playstore, all consume 2 to 3% of battery per hour...

For those who are only interested in notifications, the "NoLED" (com.led.notify) application is perfect, it only uses the battery when there is a notification, so the battery thanks you;)

Thank you for a job well done!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] snoopy20:
I have a serious bug manifesting, for some reason it will only boot with the USB cable attached, otherwise constant loop. As soon as the USB is unplugged it reboots. I don't get the animation just the white screen with the red selinux not enforcing then the reboot.

No problem with the battery/charging and can get into TWRP fine so looks to be ROM specific.

I haven't changed anything at all, it just began doing it.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
Could look weird but be sure is there no water/humidity inside to charger port. This could cause such behaviour, once it's totally dried it will work back normally.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] firz78:
Does it have adaptive internal storage? it is only the reason why I want custom rom on my A3.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
You have your reseon to instal a custom rom
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
I do have a serious problem. I install Fdroid and Yalp (Access zu Google Play Store without having Gapps installed).

It works fine. Once I did a reboot and as previous reported, it boots endless. Only Vol- + Power can stop it. After that it boots normal. But .. for some strange reason Yalp can load scroll throug apps (so have ethernet), but it can't download anymore.

I did reboot, wiped cache and dalvik ... the data of yalp.

Storage permission is granted, the yalp has ethernet (otherwise it can't show me details), but not download.

I have no idea what can be the reason. Not sure it deals with the ROM but it happens after the endless reboot.

Is there a way to generate some debug information?

Edit:

Sometimes I also observe, that FDROID opens and shows no data. Is a partition (data ?) gets dismounted?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
Hi McFy,

Like i said in a previous post, when i hang up the phone (myself, not from the other side), touchscreen doesn't work anymore, and the phone reboot himself after 30 secondes (but not a real reboot, i don't see the samsung logo for example).

I have take a logcat if it can help you.

No one else sees the same problem?

Best regard
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yass:
Which build are you using? Sounds like the same problem i had when i received a call whilst using headphones listening to music. That was on build from 20180517.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] TheMadScientist:
All right guys get it on topic
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
The last build (20180821). But i have forgot to tell that i'm using google dialer :/
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yass:
Have you tried with default LOS dialer? Just out of curiosity, havent used google dialer before.

Edit: Which device varient are you using by the way?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
I have a sm-a320fl ;)

Unfortunately, i can't test with the stock app which was removed during gapps installation.

After, it was not a blocking bug for me, i can live with it.

Thanks for your support.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Do you still have this problem? Me to from time to time.

Even worse that FDroid after this interrupted boot (Vol- + Power) sometimes doesn't show any data when opened. After clearing data and forced stop it works again ... ?!?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] cyberbix:
I can confirm the boot loop problem. I have it every time I power on. I´m using the 20180821 build, flashed onto an A320FL that was previously factory resetted with flashing a German DBT stock Oreo build from Sammobile. I´m using device encryption. Device is not rooted, just LOS and Gapps.

After powering on, device boots, asks for PIN and then hangs. I have to reset and try again 2-3 times, then the final boot occurs after PIN.

I encounter also sporadically reboots after powering off.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
It looks a bit different. For me it is just that the boot-logo that I see, it hangs there for minutes. After repower it seems to boot normal.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
In my post, I had forgotten to mention that I also use encryption, (locked by a pattern + fingerprints) with root and Aroma Gapps with no additionnal aps (smaller than pico ;) )

I have exactely the same behavior, exceps it hangs after asking for the pattern most often

EDIT : TWRP 3.2.3
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] equatorius:
I also experienced random sluggish performance and reboot issues (like reboot instead of shutdown and similar unexpected behavior) with 20180821. But the reboot thing is nothing new (it was like this with all the earlier builds I tried since May).

No encryption, no PIN, no fingerprint, just pattern lock (and location based smart-unlock).

Some apps started crashing or hanging and a reboot just made everything worse. Clearing /cache, /system, running fsck on /data and reinstalling lineage+gapps didn't fix it. Leaving the seemingly frozen phone alone for a while (I had to do something and forgot about it) "magically" brought it back to life (at least for now).

This behavior could be some background task hogging the system resources, except there was no notable battery drain and/or heath.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
I digged around a few hours to get latest LOS version running. But it seems to be not stable. Installed FDroid and Yalp.

That following probelm happened just with a plain LOS without gapps.

After some time (!!) FDroid comes up with no content. Clear the app data solves the problem. No idea what happened here?! If someone explains me how to create debug info, I'll do so.

Next strange thing that happens (imho not right after start). Yalp can download informations about the apps, but can't download the app. Permission to memory is given, I see even empty files in memory.

A second indenpendent (possible) issue:

I observed that some (TWRP)-Zip programs complain about a missing /vendor folder. Not sure, but creating a link in TWRP (terminal, mount system, ln -s /system/vendor /vendor) can help. Is it normal?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] JaiGlisséChef:
Hi,

By adding this in init.Target.rc.

After :

on init

add :

symlink /system/vendor /vendor

Solve problem of mount vendor path
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Barium:
I installed Lineage-15.1-20180821 for a friend on an A320FL. Only issue to report is that after ending a call on speaker mode, the Trebuchet launcher is crashing and the phone needs to be rebooted. No problem during 'normal' calls. I didn't see that anybody reported this or has the problem. Does anybody have the same issue?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] JaiGlisséChef:
The problems of sound comes from the device tree so the best is to wait for an upcoming build that solves this problem.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] gteck93:
Has been reported read carefully the thread.

Also I tested this build and I have the same problem+ when someone close the call touchscreen does not respond.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Will this be active in a state where TWRP is running? I am asking, because I do have the problem in that state.

Once "normal" bootet, that link is available - wherever it is created.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] JaiGlisséChef:
the mounting of the system/ folder is usually enough for twrp, but after boot, there is needed.

too much warning logcat for the vendor path.

And it is not present or created once boot.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] McFy:
dlopen function is here to tell that something called from a lib is missing : here on the lib libstagefright, and what's missing is a symbol, I would try to shim it or use bsp as soon it's a lib built from exynos slsi tree's. Libstagefright is a lib for camera used to convert picture/video with some codec into a file, so the error is related about OMX. I gonna figure what I can do but about way of shim since the symbol is empty I have some doubt about this problem. This part of the log is interesting, about your problem it's maybe caused by a crash of webview.

~ what happened when you recorded this log ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] JJGLive:
Can't get ACR Call Record to work. Does the ROM support call recording?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] starbright_:
Do you know Yalp? It is get apps from playstore without gapps on device. Worth to check it. ;)

I opened yalp, searched for an app (OI Filemanager), found it, read the description and the log is starting when I press the download button. Nothing happened than. If I check with the onboard filemanger I can see in /sdcard/Download/xxx.apk is in waitig queue.

Found /system/lib/libstagefright.so - so it exists.

The strange thing is, that this problem is not happened right at the beginning, but after a while. So I downloaded a few apps and the next day it doesn't work. I can't say that I installed any strange thing or changed any behaviour. Ok, afwall, but I also checked for blocking and disabled it again. But that seems not to be the reason..

If you need another log, let me know (best with detailled instruction for filtering - I am a beginner with that).
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] JaiGlisséChef:
Another problems of permission, this A3 bug almost because of that.

RAMDISK is bad (but improves), missing permission device and system (need a good SEPOLICY), and the vendor path do not even mention it...

This is my vision (from a beginner) of things wrong or not.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] y2kadir:
[MENTION=7698739]McFy[/MENTION] :

-is xiaomi doze installed in this rom to reduce battery drain?

-random reboots or hanging on boot logo is more reproduceable now due to memory problems or cpu usage? Sometimes on using any app, the phone does not react anymore and afterwards boot logo is shown and bootloop..

- also on some phone calls the known behaviours appear ( no audio of other side, not possible to hangup or redial. only reboot to Download mode and cancel helps to restart system)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] csx3:
hi, first of all thank you for your work.

i choosed this rom because on stock rom the adoptable storage solutions(use sd as internal storage) doesn't work because its disabled.

on this rom nearly everything is fine: adoptable storage, magsik root, xposed framework, phonecalls, bluetooth wlan and the rom generaly is very fast.

The only thing is the battery drain: in the battery stats bluetooth is shown with 60%, the rest like system and so on with 0-4%. But i think the display or display and other thinks are shown as bluetooth. because the display was 3 hours turned on and no display is shown in the battery stats, only the bluetooth with the 60%.

and also if i turn on flight mode i can't reactivate bluetooth.

the rest is realy fine, thanks again.

the only thing i miss is the samsung radio app

if someone knows where to find a port(not an internet radio) for lineage that would be great.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] grosbedos:
Hi,

Someone know how to install stock dialer app ? My gapps have removed that, and i would like to reinstall sotck dialer, without reflashing my phone ;)

Best regard
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] paf22:
Related to this question: Is this ROM working with microg? If we use microg instead of gapps, is the stock dialer conserved? Or is it also preserved if we use the "pico" variant of gapps?

Moreover: Can we use microg instead of gapps seamlessly? (For example: Can I install Google Maps with microg whitout bugs?)

I plan to test this build soon and will know which is the best option... :D

Thanks!