yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sstassin:
Ty, but where are this thread rom images for our A3 Phone ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] aelfinn:
They are exactly where the OP says they are: https://download.lineageos.org/a3xelte
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sstassin:
Waouuu... ty
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
:laugh: I updated the A5 and A3 at the same time and messed up the unofficial link. (I am currently one handed ;) )
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Still very efficient with one hand though :good:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mobb_Deep73:
Just updated to the latest nightly (with 2 hands) and it's working again :).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
FapFapFap
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Nope, it did not -- I'm on the Aug 23 build now and it is still there.

These screenshots I've attached here present today's night (CEST), and I had all the apps closed in the recent apps switcher before leaving the phone idle for this night.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I would guess that it is related to a Magisk module or app that you have installed as I cannot reproduce your symptoms.

To narrow down the cause you would need to do a clean install and add your apps/modules back one at a time until you fail to get deep sleep.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Just to be sure:

Actually running 20190811 version.

Should I first update to latest unofficial, then flash migration+latest nightly?

Or can I directly flash migration zip over 20190811 ?

Thanks again for much appreciated work!

Tim
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
No need to update the unofficial first. Migration + official is fine.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
Could you probably send me your BBS dump. Probably we can narrow it down to an app we have both installed. I've not installed Magisk.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Thanks for the heads up. Has anyone tried this rom on A3?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Im just switched to a3 and this for daily driver.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Dhalsim43:
Please, what's the architecture to be used with Gaps for this device ? arm64 ? The wiki is unclear for me, it shows :

Architecture CPU: arm64

Android: arm
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sstassin:
Hi all....

Sorry if my question... is really a "newbie" question... but this is the first time i saw our SM-A310F in the official Lineage OS builds https://download.lineageos.org/a3xelte .... it's a so emotional for me :crying::crying::crying:

What is the main difference/advantages between this XDA thread unofficial releases... and the official Lineage release ???

PS : while writing... i have a special feeling that mu question will appear as the "most noob question of this thread since a while :) "" ...

Regards from Toulouse \ France
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Main change from user point of view: the updates are OTA now, and the microG fork started building as well.

---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------

The wiki is clear. Maybe open GApps is unclear. GApps must match android version.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sstassin:
Thank [MENTION=8031265]kurtn[/MENTION] for this info, do you mean :

OTA is now also in the unofficial release ?

what is microG ? (Micro GApps is also included) ?

Sorry if my english understanding is not enought good :eek::eek::eek::eek:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
To update unofficial, you will alwas have tp download and flash manually.

MicroG is an open source alternative to GApps. Open GApps micro is something completely different. Forget my talk about microG, if you are happy with GApps. And GApps will never be included in any official lineageOS.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
Thank you!

First let me say thank you for doing this, danwood76 and co-contributors! Bringing new life to my phone is much appreciated!

I'm using the build from 26 march and I have similar problems with charging. Sometimes when the phone is connected to the charger/ computer it doesn't charge. I have noticed that when connecting the usb-cable sometimes it shows the battery percentage and 'charging' (this is when it charges). Other times it just reads 'charging' but nothing happens. Unplugging the charger from the electric outlet and wait for the 'charging notice' to go away before plugging it back in seems to do the trick so this is not really an issue (just gonna leave it here for others with similar problems).

I'm experiencing the exact opposite :) I know the software is supposed to learn my preference of choice but so far it hasn't figured out that I don't want to be staring into a car headlight when going to bed. I will give it time (again I'm using the build from 26th of march).

Again thank you danwood76 and fellow co-contributors!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Uploading a small update now.

Change list:

Fixed a bug that was stopping proper debugging of the reboot issue

Added a further optimisation of the CPU governor

Pulled all changes from the latest LOS 16 sources
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Hi!! Congratulations, and thanks for your amazing work!!

I have your ROM installed since yesterday, and it works fine (using MindTheGapps). I have detected only one littel problem: my phone experimented two reboots when I was not using it (one of them when I was sleeping, when the phone was in "flight mode").

Xxx
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lawliet80:
He is working on it, the problem should be fixed soon ;)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Thanks!! That's the only problem I have seen, but the ROM is awesome!!

So, when the new version is finished, how can I do to update it without flashing my phone?? Is there any way to do it? It is a little bit uncomfortable to flash the phone, and re-install apps, sign in, etc...

Thanks a lot!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] iindeec:
Hi. You could always just wipe cache/dalvik and flash full image. That way you'll not lose anything. Full wipe usually required for big changes or if something acting up.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

All you do is download the zip and then flash in TWRP. There is no need to wipe caches, that just lengthens the boot process.

All apps and settings are retained, this is exactly how I update during testing.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Danisp:
It's possible to fix hardware composer ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes it is possible, it is not a high priority issue as it runs fine without it.

Unfortunately I need some free time to debug it properly which i don't have at the moment.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Wiltoncandido:
[MENTION=6707196]danwood76[/MENTION] the first compilation was practically stable for me to upgrade to the latest version, now the phone reboots itself. How to get back to the first version without having to delete everything?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You can simply flash the old one over the top as the only real changes were kernel related. I believe I have fixed the issue in my current kernel code and will be uploading a release later with my fix included if you want to wait.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Wiltoncandido:
Yes I will wait is the time that I return from work. thank you :Boa:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Update incoming.

Change list:

kernel: Fixed NULL pointer de-reference in CPU governor (should fix reboot bug)

Android April security patch
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Wiltoncandido:
Perfect this new update runs perfect, a doubt can I use the google camera app? and what it affects?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Rapimist:
Bazı Problemler;

1-Cihaz Kendi Kendine Bazen Kapanıp Açılıyor

2-Cihazın Maximum Ses Ayarı Orjinale Göre Çok Az

3-Müzik Çalar, Dosyalar, Gibi ROM ile Gelen Uygulamalar Çok Eski Görünüşlü

4-Arayüz Çok Sade Görünüyor Biraz Daha Modern Olmalı
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
That's great.

Google camera will have the same issues as previously, it will probably lock up the camera hal at some point.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
1 - Try the latest release, the reboot issues should be fixed

2 - Not sure what you mean, seems loud enough to me?

3 & 4 - That is the LOS design, if you don't like it don't use it
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] pluescho:
Thank you so much! No more issues. Great work. :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Wiltoncandido:
[MENTION=6707196]danwood76[/MENTION] What is missing for LOS16 to be official?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
We have quite a few hacks that need fixing properly in the graphics stack.

And around 5 patches from gerrit. Much closer than when Oreo was released though. :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sstassin:
But, i was thinking than the "unofficial" rom we are talking on this thread have more differences with the Lineage Official One'S ?

SM-A310F specific optimisation's

maybe Some other Tweak's

I am right ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
All these optimisations are included in official. That's why there are so many different official builds. One for a specific device or a small group of very similar devices.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
There is no difference between the official and unofficial in terms of stability/performance. The main difference is you get faster security patches and updates via ota.

It is still Stricted and my device trees and kernel.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Hi,

It appears that my non-working-deep-sleep problem had been caused by 'ViPER4Android FX' (installed as a Magisk module; I haven't checked if the problem still exists when it is installed not via Magisk, i.e. not as a module)

'zRAM/SWAP Manager' Magisk module.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] exzemat:
Hello,

My wife use this rom (last unofficial and now official) with duo ( Google visio).

Seems like echo : i ear myself (I don't have this problem with other). Maybe problem due to the proximity betwen micro and speacher?

Don't have echo with normal (phone) communication ...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Hi [MENTION=6707196]danwood76[/MENTION], I've been using your rom for 2 days now and all I can say is that it's truly amazing compared to stock nougat.

The downside for me (the only one really) is that it has unfortunately the same bug that I've always had with Lineageos builds, the device going black and irresponsive for a good while when making (or receiving) calls. Though you can carry on your conversation, there's no way to get back the display, or ending a call or even turning off the device.

Here's the procedure I followed to install this rom on my A3-2016 SM-A310F (A310FXXU3CQL3)

-In TWRP flashed twrp-3.3.0-0-a3xelte.img then reboot in recovery

-Wiped Dalvik, Cache and Data

-Flashed lineage-16.0-20190818-UNOFFICIAL-signed-a3xelte and in same queue open_gapps-arm-9.0-pico-20190823

-Reboot and setting the device as usual, restoring only my Google account contacts and settings

-Flashed lineage-migration-official then lineage-16.0-20190826-nightly-a3xelte-signed and reboot to system

-Finally, flashed addonsu-16.0-arm-signed

Maybe I missed something along the route with Lineageos? Please tell me how I can help solve the issue as I really want to use this rom as daily driver.

As always, many thanks for your dedicated contribution.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sounds like a faulty proximity sensor. Does the sensor work in stock?

You can test the sensor output using aida64, it is located next to the speaker at the top of the phone.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Hi [MENTION=6707196]danwood76[/MENTION], thanks for your quick reply.

Aida64 says, if that's the reading you hinted to, TMD3700 Proximity 0,0 cm (There's also a TMD3700 Light 0,0 Lux). Is this faulty?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Could be a faulty sensor. Have you had the screen replaced or have a cracked screen?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Yes, you're probably right, the faulty proximity sensor could be the source of the problem. Last summer I dropped the device in sea water and had to have the screen replaced. I noticed that some time after that, screen would go off unexpectedly now and then and wouldn't allow to do anything to the point I have to turn off the device but at that time, I suspected some lock/unlock app I was using to spare the home button and after getting rid of all that the problem was gone.

On stock, I do have that screen going black during a call when I put the device to my ear and I have to press the home button to get the screen back and hang up. But on Lineageos, the problem is more pronounced and there's no way to rapidly revive the screen after a call (when the phone is held against the ear) .

Anyway, talking to myself, I'll see if the screen won't go black while holding the phone before me, just to be sure that it's a hardware problem. Thanks again for your time [MENTION=6707196]danwood76[/MENTION]
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Settings/system/buttons/power button/end call
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Thanks for reminding me of that setting, it works but the problem is still there. Even with the phone in my hand before me, as soon as I press OK to make a call, the screen goes black . Proximity sensor has nothing to do with it, the problem is elsewhere, any other suggestion?

Ofc, it's out of topic, I'm just asking around this thread maybe someone else experienced same issue or would come with a working suggestion.

Thanks and regards.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
With my s4 mini i had this issue several times. It was easily solved by tearing down the phone till i had the proximity senor in my hand. Removed the dust. Screwed everything together and voila

S**ty new phones are not screwed, but glued.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Um... I've just applied an OTA update (the Aug 29 one, updating from the Aug 26 one) and the phone got stuck at the boot logo (not the boot animation). So I then formatted cache and dalvik but it is still stuck there. Im afraid I will loose my data. What to do now?

PS I guess I'll just go with a yet another clean install.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Have you installed anything that modifies the /system partition?

Anyway you can reset it without losing data.

Wipe just the system partition and then reinstall the ota manually and reinstall Magisk, gapps, etc that you had installed at the same time.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Thanks for a quick reply, that's exactly what I've just done except wiping the System beforehands, and it did wonders! (didnt have to reflash magisk or gapps)

And no, I dont think that anything had modified the System partition then
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] s3korn:
[MENTION=6707196]danwood76[/MENTION]

I tried to install the official 16 coming from your 15.1 build. Unfortunately, it doesn't work.

Please let me know how I have to proceed.

Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Did you flash the migration zip? It is a couple of pages back in this thread.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] s3korn:
Yes I have tried also with immigration zip coming from 15.1.

LOS boot logo is running for around one - two minutes, screen goes dark and it's rebooting into TWRP 3.3. recovery.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Did you also update opengapps and Magisk?

Best thing to try, wipe system and caches. Flash latest Los, opengapps pie, and Magisk. And reboot.

Did you make a backup? A clean flash might be your only option if the above doesn't work.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] s3korn:
The gapps zip was faulty. Nothing to do with your ROM!

I think I'm now on official, OTA works. Do you know why are every day new version about 400 MB is available?

The only two things annoying me are the white colour behind the smaller app icons compare to 15.1 cause using black ui

and the system don't remember my lower auto brightness setting, after sometime it's jumps up to 60-80%.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You get daily builds on lineageos. But you don't need to update that often. Setting it to check weekly or monthly is best.

You can change the icon shape I think in the trebuchet settings (press and hold on an empty area on the home screen).

The auto brightness will take a while to work out your usage. Just keep setting it to how you want it and eventually you won't need to touch it anymore.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ganeshpaudel:
help me to install lineage os 16 on my samsung A3 2016

I was tried flash lineage os for my samsung galaxy A3 2016. everything is right till flash zip file but when reboot stuck on lineage starting logo. please kindly help me to guide for lunching lineage on galaxy A3 2016.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Hi [MENTION=6707196]danwood76[/MENTION], my screen going black and irresponsive as soon as I hit OK is still there this time with WhatsApp. While talking goes well, I can't make a video call or start camera or share an attachment. Proximity sensor isn't involved as the device is laid flat on the table or held in held and not to the ear. What's your guess? Using the power button to end a call when on phone isn't a great deal (though I'd miss the loudspeaker feature) but I don't want to go back to stock nougat because of WhatsApp that I use a lot with family.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
What twrp do you use? What was installed before? What did you wipe? How long did you wait with lineageOS logo animation?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
WhatsApp calling still uses proximity sensor.

If you are getting a black screen at other odd times then maybe you have a bad display?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Check you are running the latest baseband (modem firmware). You can do this by installing the latest stock Nougat for your region.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Thanks for the reply but I mean to say that I don't have any issue at all either with display, or phone or WhatsApp on stock nougat. It's just that I'd be happy to upgrade to Android 9. Improvement not regression! :D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Well it sounds like you have a faulty sensor. Getting the hardware fixed would be the easiest solution.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
Security problem?

Hello Danny,

from version 20190811 the apps that use XMLHttpRequest end with error:

"...from origin 'file://' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."

Obviously with other Android, updated with security patches August 1, 2019, the problem is not there. possible that no one else has the same problem?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It looks like there was a bug introduced in Chrome near the start of August that causes this error. Make sure all of your apps are up to date.

Which other devices running Pie have you tested with?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
security problem?

The applications are up to date, the device is Huawei p20 lite 9.1 emui build 208. Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
[SOLVED] Security problem?

You are right Danny, the problem was due to the WebView engine ... changing it from Android 76.0.3809.111 to Chrome 76.0.3809.132 (in developer options -> webview implementation) the apps work regularly. Thanks Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Muhammad Nuruzzaman Syam:
Cannot delete images stored on the SD card from the gallery application

I deleted the image from the gallery and the image is gone, but after the device restarts the image appears again

The image can be erased if I delete it from the File application, it does not appear again after restarting the device.

What is wrong?

How to solve it?

Has anyone experienced anything like this too?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Alicee3:
Fixed it myself a month ago, anyway thanks for making this great, stable ROM.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Hi Danny,

Just updated to 9/9 microG build. AudioFX has vanished. I've seen the commit to make audioFX optional in device configuration. So why did you decide to eliminate audioFX in a3 2016? And can you recommend a method to get a systemwide equaliser?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Audio FX didn't really do much for us so it got disabled. Some people have installed audio mods in Magisk, not sure if any of them have an equaliser?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Ok, I'll get viper magisk module.

P.S.: there are many decisions to make. I did the following:

- latest stable magisk and manager

- Viper Legacy module

- (press volume button twice in installer to get a + or -)

- new Version

- Original version

- Install as system app

- killall yes

It installed 2.5.0.5 and works for me.

... And the setup survives OTA updates.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
I'm on lineage-16.0-20190908-nightly-a3xelte-signed.zip and just now the Battery Manager again (I clear the Restricted apps list after each flash) asked me to restrict Android Keyboard (AOSP) version 9 com.android.inputmethod.latin. This has been a kind request of the Battery Manager for as long as I can remember / have used this beautiful build.

This is not an issue nor is it really problem ... also this is probably not the correct place to post this.. I just thought I'd place this side note somewhere if anyone would like to look at it .. it's more an "Am I alone in this world?"

[MENTION=6707196]danwood76[/MENTION] goes on 'vacation' and the build is suddenly official.. WOHOO!! :highfive::fingers-crossed::victory:

---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------

A few months back, around the time that I first added Magisk to my install queue, I ran in to the problem of not being able to delete my pictures. I 'removed' the pictures from within Gallery but after next restart the same pictures would still be there but they were nowhere to be found in my DCIM folder on my phone nor the SD card. Changing camera storage settings from SD to internal did nothing.

After some digging around, I used storage analysis in SD Maid eu.thedarken.sdm, I noticed that my 'invincible' pictures had fled to a folder no longer used by the camera ie. the camera had started using another folder for new photos. Moving all old photos and videos to the new folder solved the hick up and has not caused any problems since with the Gallery.

All the best
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I hope my future vacations are more fun :laugh: