[UNOFFICIAL][a3xelte][SM-A310F]Lineage OS 15.1 for A3 2016

Search This thread
By:
Advanced…
dariotr

dariotr

Recognized Developer
Mar 30, 2016
250
451
Schauenburg
Stricted said:
wat?
the device trees in the gitlab orgs are pretty much to lineage rules (that was the point on the recreating on gitlab in the first place)
why wasting time in redoing it when we have perfectly fine trees already

putting local hal clones into hardware/samsung is a bad idea (and probably wont get merged into lineage) the standard is to just copy them into the device trees
Click to expand...
Click to collapse
Yes, sorry. I deleted it just after it was posted. I wanted to write in a Galaxy S9 thread but accidently put it here.
I tried to explain the thing that one maintainer did is cloning all HALs from LineageOS that the device needs into the device tree without any important modification. He could just directly build it from LineageOS/android_hardware_samsung instead of doing that.
 
Last edited:
E

exzemat

Senior Member
Sep 16, 2013
61
11
Tested too, gapps and some hacks find in XDA
Faceunlock doesn't appear in smartlock or (with hacks) force close in launch...I read that seems to be a bug on LOS 15.1 32bit...because of faceunlock libs only available in 64bit
 
Last edited:
D

danwood76

Recognized Developer
May 23, 2015
1,409
2,307
exzemat said:
Tested too, gapps and some hacks find in XDA
Faceunlock doesn't appear in smartlock or (with hacks) force close in launch...I read that seems to be a bug on LOS 15.1 32bit...because of faceunlock libs only available in 64bit
Click to expand...
Click to collapse

Yes, Google never supported face unlock on 32 bit so it won't work.

Some people in the opengapps bug reports claimed to have fixed it but it never got merged as the reports of it working were inconclusive.
 
E

exzemat

Senior Member
Sep 16, 2013
61
11
Yes, but faceunlock works on stock rom (with twrp + opengapps) : I have tested....
Despite, stock rom is 32 bit ?
 
Last edited:
D

danwood76

Recognized Developer
May 23, 2015
1,409
2,307
Hi,

Just uploaded a new release (23/06/19).

I have added a new fix for the camera HAL which solves any remaining Snap crashes, I have also tested this with Google camera (from OpenGapps stock package) and I have not been able to crash it.

Code: 
Changes in the 23/06/2019 release:
[INDENT]camera: added new workaround to fix remaining HAL crashes (Google Camera should work now)
June Android security patch
LOS updates
[/INDENT]

Regards,
Danny
 
Last edited:
  • Like
Reactions: nuubstyle, heilbron, s3korn and 1 other person
G

Gunnlaug

Member
Jun 30, 2019
6
0
After (dirty) Update from May to June Version i can't unlock my Phone.
The Lockscreen appears, i type in the numbers to unlock. The screen gets black for some seconds and then the Lock Screen appears again.

The Volume UP Button is brocken. So any idea how to get past the lock Screen?
 
Last edited:
D

danwood76

Recognized Developer
May 23, 2015
1,409
2,307
Gunnlaug said:
After (dirty) Update from May to June Version i can't unlock my Phone.
The Lockscreen appears, i type in the numbers to unlock. The screen gets black for some seconds and then the Lock Screen appears again.

The Volume UP Button is brocken. So any idea how to get past the lock Screen?
Click to expand...
Click to collapse

Sounds strange. Do you use a different lock app or the stock LineageOS one?

You could try clearing the cache in TWRP maybe something got corrupted in the update.
 
G

Gunnlaug

Member
Jun 30, 2019
6
0
Sounds strange. Do you use a different lock app or the stock LineageOS one?
You could try clearing the cache in TWRP maybe something got corrupted in the update.
Click to expand...
Click to collapse

No, i don't use an different lock app. Just the Lineage from this Thread.
I can't get into the TWRP because my Volume UP Button ist broken.
Did you know another way to get there? Maybe without using keys.

Code: 
adb restart recovery
din't work, because adb says, the devices is not authorized. Maybe beacuse it's still locked :rolleyes:

Today i just see an failure Message for some seconds as i tried to unlock the phone. I says something like "Closing System UI". It sounds like this process got an problem and get killed.
 
D

danwood76

Recognized Developer
May 23, 2015
1,409
2,307
Gunnlaug said:
No, i don't use an different lock app. Just the Lineage from this Thread.
I can't get into the TWRP because my Volume UP Button ist broken.
Did you know another way to get there? Maybe without using keys.

Code: 
adb restart recovery
din't work, because adb says, the devices is not authorized. Maybe beacuse it's still locked :rolleyes:

Today i just see an failure Message for some seconds as i tried to unlock the phone. I says something like "Closing System UI". It sounds like this process got an problem and get killed.
Click to expand...
Click to collapse

Unfortunately without ADB your only other option is with the hardware keys. Are you able to get your phone repaired?
 
G

Gunnlaug

Member
Jun 30, 2019
6
0
At this moment i didn't know how to get the hardware keys. I read an short comment about it.
I plan to use an "Jig" to get into and start the download Mode. Normaly you need the Volume UP Button to start the Download Mode.
Flash the stock rom, get root, start recovery with an app or adb, an so on..

I think this way is faster as to learn the method with the hardware keys.
I hope this will work.
 
D

danwood76

Recognized Developer
May 23, 2015
1,409
2,307
Gunnlaug said:
At this moment i didn't know how to get the hardware keys. I read an short comment about it.
I plan to use an "Jig" to get into and start the download Mode. Normaly you need the Volume UP Button to start the Download Mode.
Flash the stock rom, get root, start recovery with an app or adb, an so on..

I think this way is faster as to learn the method with the hardware keys.
I hope this will work.
Click to expand...
Click to collapse

By hardware keys I mean the Volume, home, and power buttons.
With the volume buttons they have a little plastic pip on the physical domed switch on the flexi PCB, quite often these pips break and so you can't press the button in. However if you were to remove the button you still may be able to press the domed switch in (you need to remove the back cover of the phone but at the moment it is pretty much a brick).
 
G

Gunnlaug

Member
Jun 30, 2019
6
0
Ah ok, i misunderstood.
I had the Phone already open and there was no difference between the working and the broken Volume Key to see.
 
B

Brummbude

Member
Jun 10, 2012
44
8
Xiaomi Mi 9 SE
Hi,

Yesterday I did a clean install on my phone.
LOS_a3xelte_20190623. With nano gapps.

Everthing is running nicely. But when I did my first call and realized that the proximity sensor is not working. When starting the call the screen immediately turned black. NO change to stop the call.

I installed " Sensor Box for Android" to check the sensor. But I didnt get any reaction from the proximity sensor.

Does anyone face the same problem?

Gesendet von meinem SM-A510F mit Tapatalk
 
D

danwood76

Recognized Developer
May 23, 2015
1,409
2,307
Brummbude said:
Hi,

Yesterday I did a clean install on my phone.
LOS_a3xelte_20190623. With nano gapps.

Everthing is running nicely. But when I did my first call and realized that the proximity sensor is not working. When starting the call the screen immediately turned black. NO change to stop the call.

I installed " Sensor Box for Android" to check the sensor. But I didnt get any reaction from the proximity sensor.

Does anyone face the same problem?

Gesendet von meinem SM-A510F mit Tapatalk
Click to expand...
Click to collapse

Is the sensor dirty? Scratched screen protector?

You should be able to see the sensor change in something like aida64.
 
  • Like
Reactions: Brummbude
B

Brummbude

Member
Jun 10, 2012
44
8
Xiaomi Mi 9 SE
No scratches, no dirt. I'll check aida tonight...

Gesendet von meinem SM-A510F mit Tapatalk

---------- Post added at 07:13 AM ---------- Previous post was at 06:36 AM ----------
danwood76 said:
Is the sensor dirty? Scratched screen protector?

You should be able to see the sensor change in something like aida64.
Click to expand...
Click to collapse
Okay checked that, now. The value of proximity sensor stays at 0,0 cm all time. No matter what I'm doing.

And yes it works 2 days ago.

ANZ guess what to do.

Ragards
 
D

danwood76

Recognized Developer
May 23, 2015
1,409
2,307
Brummbude said:
No scratches, no dirt. I'll check aida tonight...

Gesendet von meinem SM-A510F mit Tapatalk

---------- Post added at 07:13 AM ---------- Previous post was at 06:36 AM ----------

Okay checked that, now. The value of proximity sensor stays at 0,0 cm all time. No matter what I'm doing.

And yes it works 2 days ago.

ANZ guess what to do.

Ragards
Click to expand...
Click to collapse

One thing I just noticed, you say you installed 23/06/19 A3 version but your signoff in your messages says SM-A510F. Do you have both an A3 and an A5 or are you just posting in the wrong thread? Or did you somehow flash the wrong version to your A5?

When you say "it works 2 days ago" is that on stock firmware?
Can you reboot your phone a couple of times and then dump the /proc/last_kmsg file (I think some people have used TWRP for this).

Regards,
Danny
 
  • Like
Reactions: Brummbude
You must log in or register to reply here.

Similar threads

G
[ROM] Lineage 15.1 for Galaxy A3 2016 [UNOFFICIAL]
Replies
444
Views
101K
RidaRida08
RidaRida08
mygalaxya
[ROM][6.0.1][DISCONTINUED] CyanogenMod 13.0 Unofficial for Samsung Galaxy A3
Replies
1K
Views
250K
J
JirTem
D
[OFFICIAL][a3xelte][SM-A310F]Lineage OS 17.1 for A3 2016
Replies
555
Views
87K
R
rusen02
G
[ROM] Lineage 15.1 for Galaxy A5 2016 [UNOFFICIAL]
Replies
421
Views
148K
M
Mousom T
D
[OFFICIAL][a3xelte][SM-A310F]Lineage OS 16.0 for A3 2016
Replies
624
Views
73K
kurtn
kurtn

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 40
    D
    danwood76
    https%3A%2F%2Fimg.xda-cdn.com%2FpcscAfEjxfDt7UPGeamYS042gKY%3D%2Fhttps%253A%252F%252Fcdn.neow.in%252Fnews%252Fimages%252Fuploaded%252F2018%252F02%252F1519557694_lineageos.jpg

    Code: 
    #include <std_disclaimer.h>
/*
 * Your warranty is now void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
 *
 */
    Introduction

    Lineage OS 15.1 for the SM-A310F is based upon the hard work of both @Stricted and I in creating new clean device trees for Exynos7580 devices. This release is a stable release build on the new device trees.

    What works
    Calls, SMS, Mobile Data
    Camera
    NFC
    WiFi
    Bluetooth
    Torch
    SELinux Enforcing​
    What doesn't work
    VoLTE (will never work on LOS)
    You tell me​
    Installation
    1. Download the latest LOS build and transfer it to your phone
    2. Install the latest TWRP (Available Here)
    3. Make a full backup (just in case something goes wrong)
    4. Do a full wipe (Cache, Dalvik Cache, Data, System)
    5. Install LOS
    6. If you are installing GApps do it at the same time (preferably in the same install queue)
    7. And finally boot, the first boot can take several minutes as it optimises all the apps

    Downloads
    Latest releases are uploaded HERE
    OpenGapps HERE
    TWRP is availableHERE
    Magisk is available HERE​
    Source
    Exynos7580 Device Trees here
    LineageOS sources here​
    Thanks
    @Stricted
    @l-0-w
    @sekil
    @alexax66
    @macs18max (BT call audio fix)
    @Borduni
    All the testers on the Discord group (https://discord.gg/bXe7dN)
    And all others who have contributed to the Exynos projects
    ​

    A special thanks to my donors
    XDA:DevDB Information
    Lineage OS 15.1 for A3 2016, ROM for the Samsung Galaxy A Series

    Contributors
    danwood76, stricted, borduni
    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.10.x
    Based On: LineageOS

    Version Information
    Status: Stable

    Created 2018-07-06
    Last Updated 2019-05-16
    View
    17
    D
    danwood76
    Changelog

    Code: 
    Changes in the 09/07/19 release:
[INDENT]July Android Security Patch
LOS updates[/INDENT]
    Older changes listed below:

    Code: 
    Changes in the 23/06/2019 release:
[INDENT]camera: added new workaround to fix remaining HAL crashes (Google Camera should work now)
June Android security patch
LOS updates
[/INDENT]
    Code: 
    Changes in the 16/05/2019 release:
[LIST]
[*]kernel: fixed non charging issue if USB is not plugged in for 20+ hours
[*]WiFI: fixed MAC address loading
[*]NFC: default to slower but more reliable firmware loading mechanism
[*]system: optimised the vfs_cache_pressure which improves FS performance and fixes most MTP issues
[*]vendor: Added missing magnetomoter configuration file
[*]vendor: Updated blobs to February security patch
[*]Android May security update
[/LIST]
    Code: 
    Changes in the 08/04/2019 release:
[LIST]
[*]kernel: CPU governor updates and fixes (improved battery life)
[*]kernel: fix issues with WiFi connections dropping randomly due to ipreachability monitor failing incorrectly
[*]APN: added correct "La Poste" entries
[*]Android April security update
[/LIST]
    Code: 
    Changes in the 10/03/2019 release:
[LIST]
[*]Kernel: Updated Android ION driver (should fix some ION crashes I have seen)
[*]Kernel: Updated Android Binder to a much more recent version (should speed up binder transactions and fix bugs)
[*]MDNIE: Fix accessibility SEPolicy so it actually works now
[*]Moved the BT calling fix into our local device tree (now building with no repo picks)
[*]Android March security update
[/LIST]
    Code: 
    Changes in the 12/02/2019 release:
[LIST]
[*]Kernel patched up to version 3.10.108 (many security and stability fixes)
[*]USB MTP stability improvements
[*]Updated vendor blobs from A310FXXU4CRH1
[*]Updated gps config to use closest NTP server (thanks [user=7377908]@Borduni[/user])
[*]Wired up MDNIE features
[*]LineageOS February security patches
[/LIST]
    Code: 
    Changes in the 25/01/2019 release:
(Clean flash suggested as large update)
[LIST]
[*]New cleaner device tree and kernel (better performance/battery)
[*]New HWC/Gralloc (much better performance/battery and smoother UI)
[*]Finally fixed the Snapchat (and others) Audio distortion issue
[*]New camera wrapper (faster flashlight turn on and better bug fixes)
[*]LOS updates
[*]Probably some other fixes I have forgotten about
[/LIST]
    Code: 
    Changes in the 12/01/2019 release:
[LIST]
[*]Faster NFC turn on
[*]Fixed camera wrapper (should not crash now)
[*]Updated WiFi driver (should improve battery usage)
[*]Fixed battery health save/restore (fixes battery level changing on reboot)
[*]January Andoird Security Patch
[/LIST]
    Code: 
    Changes in the 27/11/2018 release:
[LIST]
[*]Added fix for BT headsets/devices that use the WBS profile
[*]Added call recorder fix
[*]November LOS security update
[/LIST]
    Code: 
    Changes in the 09/11/2018 release:
[LIST]
[*]Bluetooth Call audio fixed (thanks @macs18max)
[*]Better 'cancelAutoFocus' camera fix
[*]LOS updates
[/LIST]
    Code: 
    Changes in the 14/10/2018:
[LIST]
[*]Fix network data type selection (thanks @Borduni)
[*]Properly fix encryption
[*]Switch to using OSS mobicore drivers
[*]LOS October security patches
[/LIST]
    Code: 
    Changes in the 28/09/2018 build:
[LIST]
[*]Switched back to open source power HAL
[*]Enabled more verbose camera debugging
[*]Latest LOS updates
[/LIST]
    Code: 
    Changes in the 21/09/2018 build:
[LIST]
[*]Builds now signed with a private digital key
[*]Min CPU frequency increased back to 400MHz to stop music playback issues when screen is off
[*]Issue fixed with battery max_capacity being incorrectly set during boot
[*]AGPS now pulls data over SSL
[/LIST]
    Code: 
    Changes in the 14/09/2018 build:
[LIST]
[*]Increased microphone volume of the camcorder and media recording profiles
[*]Fixed default power HAL profiles (restores performance and power saving in some modes)
[*]Fixed some default settings in the Power HAL 
[*]Updated vendor blobs to A310FXXU4CRG2 (vendor security now 30/07/2018)
[*]September Android security patch
[*]LOS updates
[/LIST]
    Code: 
    Changes in the 08/09/2018 build:
[LIST]
[*] Updated Mobicore (again) which improves battery and overall system stability
[*] Updated power profiles to latest
[*] Reapplied WiFi config update patches
[/LIST]
    Code: 
    Changes in the 30/08/2018 build:
[LIST]
[*]Cleaned and upstreamed patches to Exynos7580 project (now clean builds from upstream repos)
[*]Video recording audio gains fixed
[*]Added patch required for encryption support (should allow encryption but not tested)
[*]Disabled DT2W for now as it seems to cause quite a few issues
[*]Added LOS updates
[/LIST]
    Code: 
    Changes in the 26/08/2018 build:
[LIST]
[*]Added possible fix for low mic volumes in some apps
[*]Added fix for HAL1 camera recording in the august security update
[/LIST]
    Code: 
    Changes in the 22/08/2018 build:
[LIST]
[*]Updated PowerHAL based on latest TeamNexus source
[*]Updated RIL blobs from A310FBTU3CQL2
[*]Updated power profiles so that the "ScreenOff" profile is almost the same as the "PowerSave" profile
[*]Android August security patch level
[/LIST]
    Code: 
    Changes in the 03/08/2018 build:
[LIST]
[*]Disabled bioshock CPU governor as it really doesn't work well for common loads
[*]Fixed limiting of GPU speed in the Power HAL
[*]Created full set of power profiles (and fixed screen off profile)
[*]Fixed touch button LED state when waking up the device when they are disabled
[*]Added Double Tap to Wake setting in the display config menu (enabled by default)
[*]Updated the BCMDHD_1_77 WiFi driver from A3 2017 Oreo source (A320FLXXU2CRE3)
[*]Lots of kernel fixes (thanks again [user=5925090]@alexax66[/user])
[*]LOS Updates
[/LIST]
    Code: 
    Changes in the 29/07/2018 build:
[LIST]
[*]Created new HIDL based power HAL (thanks [user=5925090]@alexax66[/user] for his input)
[*]Lots of Kernel bug fixes
[*]Partially reverted previous camera wrapper change
[*]Updated WiFi config
[*]Updated LOS
[/LIST]
    Code: 
    Changes in the 13/07/2018 build:
[LIST]
[*]Kernel: Copy display colour correction tables from the A3 2017 to fix green tinge in low light mode
[*]Device: Updated cancel_auto_focus logic in camera wrapper to try and solve a battery drain issue
[/LIST]
    Code: 
    Changes in the 11/07/2018 build:
[LIST]
[*]Kernel: ION allocator fixes
[*]Kernel: Sync binder with latest android-4.9-Oreo
[*]Kernel: Fix CPUFREQ memory leak
[*]Kernel: Underclock min frequency to 200MHz by default (more power saving)
[*]Device: Reverted brightness tables to that of 06/06/18
[*]Device: Suppressed camera logcat output
[*]Device: Updated to July security patch release
[/LIST]
    Code: 
    Changes in the 05/07/2018 build:
[LIST]
[*]NFC wrapper added to aid in debugging issues
[*]NFC work around added for the startup issue
[*]Suppressed NFC logging output (it spews a lot of crap over logcat)
[*]Camera wrapper added to fix a couple of bugs in the HAL, some random lockups fixed, QR scanner now works (thanks [user=5368296]@sekil[/user] for the initial wrapper)
[*]Switched to the Bioshock CPU governor as this really saves battery (thanks [user=5918415]@nr23730[/user])
[*]Updated more mobicore blobs that seemd to have been missed from before
[*]Updated some GPS settings in the overlay
[*]Added updating of backlight brightness during doze to fix issues with dark notifications
[*]Added Sekils audio fix for libsec-ril.so blob
[*]Added lots of CVE patches to kernel
[*]Updated to latest LOS
[/LIST]
    Code: 
    Changes in the 26/06/2018 build:
[LIST]
[*]Added latest audio fixes (thanks to stricted)
[*]Added exynos OMX blobs from stock to fix codec issue (thanks to stricted)
[*]Modified display colour temperature and LCD brightness logic
[*]Increased call volume on speaker phone
[*]Updated mobicore to latest A310F nougat versions
[*]Updated to latest LOS
[/LIST]
    Code: 
    Changes in the 06/06/2018 build:
[LIST]
[*]Lots of kernel optimisations
[*]Interactive governor fixes (improves battery life and performance)
[*]Updated WiFi driver
[*]Fix headset microphone path
[*]Updated NFC blobs
[*]Tweaked screen auto brightness levels
[*]Lots of LineageOS fixes
[/LIST]
    View
    11
    D
    danwood76
    I am currently uploading a new release.

    Thanks in part to a patch from @macs18max we now have working Bluetooth call audio.
    I have tested this on my cheap Bluetooth headset and my TomTom satnav, both work great now!

    Changes in the 09/11/2018 release:
    • Bluetooth Call audio fixed
    • Better 'cancelAutoFocus' camera fix
    • LOS updates
    View
    11
    D
    danwood76
    Uploading a new release now (built on 14/09/2018).

    Changes:
    • Increased microphone volume of the camcorder and media recording profiles
    • Fixed default power HAL profiles (restores performance and power saving in some modes)
    • Fixed some default settings in the Power HAL
    • Updated vendor blobs to A310FXXU4CRG2 (vendor security now 30/07/2018)
    • September Android security patch
    • LOS updates
    View
    11
    D
    danwood76
    Hi,

    I am off on holiday for a week so thought I would upload a quick update before I go.

    There are only a couple of fixes:
    • Kernel: Copy display colour correction tables from the A3 2017 to fix green tinge in low light mode
    • Device: Updated cancel_auto_focus logic in camera wrapper to try and solve a battery drain issue

    I have only applied part of Sekils panel changes to my tree, it does appear to have fixed the green screen issue but I will need your feedback as I may need to add the rest of the mdnie logic in as well.

    Regards,
    Danny
    View

New posts