• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble]

Search This thread

Bernique

Senior Member
Apr 25, 2010
108
16
Paris
Hi,

I found that every once in a while the camera app would tell me that it cannot talk to the camera and to restart my phone.
If that happens my battery consumption is going up. (I just didnt really need the camera.

The steeper slope started when i got the message and it got less steep again after i did the reboot.

Not a biggy... if that helps to improve the rom... ;-)
This issue was described for CRDoid, see solution in second post about Fix Camera stuck: here
 

subbamaggus

Member
Oct 21, 2021
28
2
near frankfurt
I tried the kill camera. And it seems to fix it.
Not a nice solition.... but thats fine for me.

for a couple of days now.... i have a pretty bad battery drain.
Basically like 5-6% per hour. With no usage.

Betterbattery stats show that the phone does not go to sleep. "Awake screen off".

I couldnt find a spot where to put that here in the forum.

I cleared the cache for a couple of google apps. Like play/service/gms.

It is pretty anoying. Since i know that this rom can do a lot better .

Does anyone have another idea?


i found this:
so i turned off AOD.
I will keep you posted...

so i did a test:
let the phone sit there for a while with and without "Always On Display" (AOD).

Result is, that the Current is ~16mA (0,7percent per hour, almost 100% deep sleep) vs ~60mA (2,6 percent per hour, 97 "awake screen off").
i am not sure why i dont see the 5-6% per hour today... but this might be sth additional like mobile signal strength.

i will keep that in mind and see how the rest looks like.


but my conclusion:
i will keep the AOD off...
 

Attachments

  • Screenshot_20211128-114227_Einstellungen.png
    Screenshot_20211128-114227_Einstellungen.png
    54.2 KB · Views: 32
  • Screenshot_20211128-114149_Einstellungen.png
    Screenshot_20211128-114149_Einstellungen.png
    51.6 KB · Views: 29
  • Screenshot_20211128-114327_Einstellungen.png
    Screenshot_20211128-114327_Einstellungen.png
    51.8 KB · Views: 26
  • Screenshot_20211128-114307_Google_Play-Dienste.png
    Screenshot_20211128-114307_Google_Play-Dienste.png
    56.2 KB · Views: 27
  • Screenshot_20211128-123438_BetterBatteryStats.png
    Screenshot_20211128-123438_BetterBatteryStats.png
    98.6 KB · Views: 26
  • Screenshot_20211128-125352_BetterBatteryStats.png
    Screenshot_20211128-125352_BetterBatteryStats.png
    128 KB · Views: 24
  • Screenshot_20211128-125344_BetterBatteryStats.png
    Screenshot_20211128-125344_BetterBatteryStats.png
    140.9 KB · Views: 30
Last edited:

Jacktortoise

Member
Aug 23, 2015
7
1
Modena
Hi everybody, are Bluetooth calls working with this rom?
On my A320FL I tried CrDroid 6 and RR 8 (both Android Q) but both have bluetooth issue.
 

Jacktortoise

Member
Aug 23, 2015
7
1
Modena
I've just tried LOS and (unfortunately) as explained by @TheObcd doesn't work too.
But I found calls works with my bluetooth speeker LG PH1, can you figure why?
So:
- Pantone headphones --> Doesn't work
- UConnect (car) --> Doesn't work
- LG PH1 Speaker --> Works

Does anyone has a solution for this?
 

Jacktortoise

Member
Aug 23, 2015
7
1
Modena
Actually I found my loudspeaker uses SBC and BT calls works. I'm unable to find other devices codec.
Moreover I found impossible to change any bluetooth options under developer options menu: all options revert back after leaving developer options.
 
Many thanks to the developers, this is an awesome ROM!

For other newbies who want to build this ROM with their own keys: I basically followed the LineageOS guide for the officially supported A3 (2016) but with two important changes. Having downloaded the source code with 'repo sync,' I added the file 'a3y17lte.xml' to a newly created folder '.repo/local_manifests.' After a second 'repo sync,' I prepared the device-specific code, skipped the step 'extract proprietary blobs,' and started the build.

There might be better ways to building the ROM, and I understand there is an active telegram group where most discussions take place. In my case, building has been straightforward once I managed to adapt an older local manifest found on gitlab with a bit of trial-and-error. I attach both, the xml and bash script so that you can check what worked well for me.

Again, many thanks to all developers, especially @Astrako for the work on samsung_exynos7870
Karl
 

Attachments

  • a3y17lte.xml
    1.1 KB · Views: 9
  • BashScript.sh
    1.5 KB · Views: 9
Last edited:
  • Like
Reactions: pmy7 and TheObcd

kurtn

Senior Member
Jan 28, 2017
4,316
1,881
Small town in Bavaria
Many thanks to the developers, this is an awesome ROM!

For other newbies who want to build this ROM with their own keys: I followed the LineageOS guide for the officially supported A3 (2016) but with two changes. Having downloaded the source code with 'repo sync,' I added the file 'a3y17lte.xml' to a newly created folder '.repo/local_manifests.' After a second 'repo sync,' I prepared the device-specific code, skipped the step 'extract proprietary blobs,' and started the build.

There might be better ways to building the ROM, and I understand there is an active telegram group where most discussions take place. In my case, building has been straightforward once I managed to adapt an older local manifest found on gitlab with a bit of trial-and-error. I attach both, the xml and my batch script so that you can check what worked well for me.

Again, many thanks to all developers, especially @Astrako for the work on samsung_exynos7870
Karl
Typo? We are talking about 2017 device here.
 
Typo? We are talking about 2017 device here.
No typo, actually.

The official guide for the 2016 device https://wiki.lineageos.org/devices/a3xelte/build is very useful also for the 2017 device but needs amendment. The official guide explains well what tools and packages are needed to set up a Linux machine for building the unofficial 2017 ROM.

My bash script contains the amended commands. Before running it, check the section on 'Generating the keys' in https://wiki.lineageos.org/signing_builds. Once you have your own keys created in folder '~/.android-certs', make a root directory 'android' and copy the 'android-certs' folder there. Now, place the file 'a3y17lte.xml' in 'android' and run the bash script. Depending on internet bandwidth, self-building takes 5 hours or more . You will then be asked to sign the various packages with your key passphrase.

Again, there might be better ways to building the 2017 ROM and I would be grateful learning them. As a novice self-builder, I was struggling with several guides and hints from XDA and Reddit but amending the official 2016 guide finally did the trick.
 
Last edited:

AnnieBody01

Member
Jun 4, 2020
18
0
LineageOS 17.x Unofficial for Galaxy A3 2017

main-qimg-eae07393a6257f6f44f3a6f2a0be5cbb


LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Quack), which is designed to increase performance and reliability over stock Android for your device.

Code:
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways :D
*
* I am 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 me for messing up your device, I will laugh at you.
*/

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.​

What's working?
  • Audio
  • Calls
  • Wifi
  • Hotspot
  • Mobile data
  • GPS
  • Bluetooth
  • Fingerprint
  • Camera (both photos and video)
  • NFC
  • Sensors
  • Vibration
  • Others I have forgot

What isn't working?
  • Echo present in calls for the other side (no fix currently found)
  • Video recording with stock camera (fix known, will be implemented in next build)
  • Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
  • Stretched preview in camera, photos are fine (fix has more downsides than upsides)

Supported variants

Galaxy A3 (2017). Dual SIM is also supported.
All variants should be working but only A320FL is well tested since all developers have it.

How to install
  1. Make sure you have latest bootloader and modem before installing this.
  2. Make sure you are using the latest OrangeFox build. (the older ones will fail)
  3. Make sure you have flashed the repartition script.
  4. Download the Lineage build, optionally GApps and Magisk.
  5. In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
  6. In OrangeFox wipe everything except SD and OTG.
  7. Flash LineageOS.
  8. Optional: Flash GApps (rightafter).
  9. Optional: Flash Magisk.
  10. Reboot.

Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.

Downloads

• ROM
get.mcfy.fr
Google Drive

• Recovery
OrangeFox

• GApps
OpenGApps (arm64): OpenGApps
BiTGApps (arm64): AFH

• Root
Magisk: GitHub

Credits
Huge thanks to:
  • @Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
  • @McFy for help along the way and letting me use his server as a mirror.
  • LineageOS Team
  • Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here

XDA:DevDB Information
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7

Contributors
MartinYTCZ
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest modem + BL recommended

Version Information
Status:
Beta

Created 2020-02-22
Last Updated 2020-08-26
Hi
I found the instructions provided assumed the person using them had a previous knowledge of the methods required. I also found that one link led to another and become quite confused by the chain created and seemingly contradictory advice. I also found some issues when attempting to install. I followed the instructions provided in the attached file 'Root Instructions'. As you can see not everything worked the way I expected and had to employ some workarounds, but I got there in the end at my second attempt.
Some issues I have found with the Lineage operating system installed:
I cannot find any means to update Lineage. Other websites appear to show settngs which do not exist on my version.
After enabling 'Developer Options', no additional option is displayed below 'About Phone', so although enabled, I cannot edit them.
I keep getting 'Android Setup' prompting me to 'Tap to finish' but as soon as I do I am notified 'System UI keeps stopping'. Closing the app does not clear it from the notifications and as it is not listed in the 'App notifications' I can find no way to cancel or remove it.
The apps list is purely alphabetical. Oreo, my previous version of Android, allowed me to group like apps in folders and pages, which meant it was easier to use. eg The folder 'Travel' would include language dictionaries, phone tracking, currency etc. I could also group unwanted Samsung stuff into a folder and forget it. The one layout is a step backwards and not one I was expecting to see in a later version of Android.
 

TheObcd

Senior Member
The apps list is purely alphabetical. Oreo, my previous version of Android, allowed me to group like apps in folders and pages, which meant it was easier to use. eg The folder 'Travel' would include language dictionaries, phone tracking, currency etc. I could also group unwanted Samsung stuff into a folder and forget it. The one layout is a step backwards and not one I was expecting to see in a later version of Android.
You are free to change your launcher to meet your expectations, it an easy change. Alphabetical order exists for years, it was Samsung's choice to replace it.
 
Last edited:

AnnieBody01

Member
Jun 4, 2020
18
0
Updated build are shared through telegram as explained several times. Orangefox wiki may help you too.
OK.
I can now use Telegram after I found I had to receive a phone call before I could make one.
But which group! There are references above to groups and changing names!
Please provide the latest version of the group name being used:
'A3 2017 LineageOS Discussion' is not a valid group name.
'A3 2017' finds no groups that meet this criteria.
'A3 2016 & 2017 Development' does have a group, but I cannot find any mention of a LineageOS update and like most social media that is uncontrolled is full of nonsensical and timewasting garbage you have to trawl through.
Surely, if the developers can post two previous releases on Google drive, they can also provide later updates this way too? If space is the issue then why not just update the first one known to have many problems? Why would anyone even want a version with known problems anyway?
I know the developers must be working hard on this, and it is much appreciated, but why are they making it so difficult to get a working version.
I needed an new OS as my phone memory was full due to having many updates of default Samsung and Microsoft bloatware over which I had no control. The LineageOS has freed up 8Gb, but is of little use to me if it doesn't work as a smartphone!
This is becoming VERY frustrating!
 

TheObcd

Senior Member
But which group! There are references above to groups and changing names!
The link of the group (if xda moderators do not remove the link) has been shared several times in this thread. It is also in the Lineage16 thread.
Surely, if the developers can post two previous releases on Google drive, they can also provide later updates this way too? If space is the issue then why not just update the first one known to have many problems? Why would anyone even want a version with known problems anyway?
Sadly, for the moment, I won't post it on google drive. If you really does not want to join the telegram group, I shared the November release on github above.

The LineageOS has freed up 8Gb, but is of little use to me if it doesn't work as a smartphone!
It is actually wrong, you can get 11 or 12GB of free data storage if you use the repartition script, mine is actually 11.3GB :).
If you set the data partition to 11GB, it should work well.

Note1 : that you can also save storage by shrinking the vendor partition too.
With lineageOS17, you can use theses values for the script for instance : system : 2600MiB ; vendor : 400MiB ; cache : 32MiB.

Note2 : As far as I know, values in the script are in MiB and not in MB, see the difference here. Thus you have to put higher value than what you expect. Below 2.2GB or so for the system, the recovery will show up an error while flashing (even if LOS takes only 1.6GB).
 
Last edited:

AnnieBody01

Member
Jun 4, 2020
18
0
The link of the group (if xda moderators do not remove the link) has been shared several times in this thread. It is also in the Lineage16 thread.

Many thanks for the prompt reply 'The Obcd'.
I followed that link and can confirm the group name is 'A3 2016 & 2017 Development'.
As described above it appears to be full of garbage! Which I have run through twice and can find no mention of any updates. So, when I am in this group how can I find the latest version and download it?
I understand that as a newbie to Telegram this is another learning curve for me and I am not trying to be obtuse, its just that I need to have better guidance and instructions.
So please would you advise me (and other users) how to download the latest updates using the above Telegram group.
 

TheObcd

Senior Member
I followed that link and can confirm the group name is 'A3 2016 & 2017 Development'.
It's wrong. Its name is 'A3 2017 LineageOS Discussion'.
Which I have run through twice and can find no mention of any updates. So, when I am in this group how can I find the latest version and download it?
I litterally shared an update yesterday... And I built both Lineage and CrDroid almost monthly for a year now. It seems hard to miss it !
So please would you advise me (and other users) how to download the latest updates using the above Telegram group.
On telegram, there is a file research. You can easily find updates thanks to it.

1641039338219.png
1641039449505.png
 
Last edited:
  • Like
Reactions: SuperDeformed86

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Typo? We are talking about 2017 device here.
    No typo, actually.

    The official guide for the 2016 device https://wiki.lineageos.org/devices/a3xelte/build is very useful also for the 2017 device but needs amendment. The official guide explains well what tools and packages are needed to set up a Linux machine for building the unofficial 2017 ROM.

    My bash script contains the amended commands. Before running it, check the section on 'Generating the keys' in https://wiki.lineageos.org/signing_builds. Once you have your own keys created in folder '~/.android-certs', make a root directory 'android' and copy the 'android-certs' folder there. Now, place the file 'a3y17lte.xml' in 'android' and run the bash script. Depending on internet bandwidth, self-building takes 5 hours or more . You will then be asked to sign the various packages with your key passphrase.

    Again, there might be better ways to building the 2017 ROM and I would be grateful learning them. As a novice self-builder, I was struggling with several guides and hints from XDA and Reddit but amending the official 2016 guide finally did the trick.
    3
    For most newbies, first-time flashing of an unofficial ROM is quite a challenge. You still lack insight into available tools and packages, recommended procedures are hard to understand, and you constantly fear you might end up with a bricked device.

    This is how I felt and why I spent several weekends on consulting the official LineageOS guide and collecting tips from various XDA forums. Last week, I succeeded in building and installing the ROM for A3 (2017) that -- apart from the well-known camera issue -- is running great. I attach my step-by-step installation description with annotations marked with 'K69'.

    One question that I found confusing, but think I could answer at least for my use case, is whether to root the device. Without any rooting app such as Magisk or SuperSU, my unofficial device passed SafetyNet when installing apps for banking and marine navigation. Before installation, though, I had to register my phone.

    Once again, many thanks to the developers of this ROM!
    2
    Many thanks to the developers, this is an awesome ROM!

    For other newbies who want to build this ROM with their own keys: I basically followed the LineageOS guide for the officially supported A3 (2016) but with two important changes. Having downloaded the source code with 'repo sync,' I added the file 'a3y17lte.xml' to a newly created folder '.repo/local_manifests.' After a second 'repo sync,' I prepared the device-specific code, skipped the step 'extract proprietary blobs,' and started the build.

    There might be better ways to building the ROM, and I understand there is an active telegram group where most discussions take place. In my case, building has been straightforward once I managed to adapt an older local manifest found on gitlab with a bit of trial-and-error. I attach both, the xml and bash script so that you can check what worked well for me.

    Again, many thanks to all developers, especially @Astrako for the work on samsung_exynos7870
    Karl
    1
    I followed that link and can confirm the group name is 'A3 2016 & 2017 Development'.
    It's wrong. Its name is 'A3 2017 LineageOS Discussion'.
    Which I have run through twice and can find no mention of any updates. So, when I am in this group how can I find the latest version and download it?
    I litterally shared an update yesterday... And I built both Lineage and CrDroid almost monthly for a year now. It seems hard to miss it !
    So please would you advise me (and other users) how to download the latest updates using the above Telegram group.
    On telegram, there is a file research. You can easily find updates thanks to it.

    1641039338219.png
    1641039449505.png
  • 34
    LineageOS 17.x Unofficial for Galaxy A3 2017

    main-qimg-eae07393a6257f6f44f3a6f2a0be5cbb


    LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Quack), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    /*
     * Your warranty is now void. Or not. Depends.
     * It's probably expired anyways :D
     *
     * I am 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 me for messing up your device, I will laugh at you.
     */

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.​

    What's working?
    • Audio
    • Calls
    • Wifi
    • Hotspot
    • Mobile data
    • GPS
    • Bluetooth
    • Fingerprint
    • Camera (both photos and video)
    • NFC
    • Sensors
    • Vibration
    • Others I have forgot

    What isn't working?
    • Echo present in calls for the other side (no fix currently found)
    • Video recording with stock camera (fix known, will be implemented in next build)
    • Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
    • Stretched preview in camera, photos are fine (fix has more downsides than upsides)

    Supported variants

    Galaxy A3 (2017). Dual SIM is also supported.
    All variants should be working but only A320FL is well tested since all developers have it.

    How to install
    1. Make sure you have latest bootloader and modem before installing this.
    2. Make sure you are using the latest OrangeFox build. (the older ones will fail)
    3. Make sure you have flashed the repartition script.
    4. Download the Lineage build, optionally GApps and Magisk.
    5. In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
    6. In OrangeFox wipe everything except SD and OTG.
    7. Flash LineageOS.
    8. Optional: Flash GApps (rightafter).
    9. Optional: Flash Magisk.
    10. Reboot.

    Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.

    Downloads

    • ROM
    get.mcfy.fr
    Google Drive

    • Recovery
    OrangeFox

    • GApps
    OpenGApps (arm64): OpenGApps
    BiTGApps (arm64): AFH

    • Root
    Magisk: GitHub

    Credits
    Huge thanks to:
    • @Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
    • @McFy for help along the way and letting me use his server as a mirror.
    • LineageOS Team
    • Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here

    XDA:DevDB Information
    [UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7

    Contributors
    MartinYTCZ
    ROM OS Version: Android 10
    ROM Kernel: Linux 3.x
    ROM Firmware Required: Latest modem + BL recommended

    Version Information
    Status: Beta

    Created 2020-02-22
    Last Updated 2020-08-26
    12
    Telegram group
    Join here! :)
    Go also thank @Astrako for his work on the DT, kernel, ports, recoveries and many more :)

    Changelogs
    - 20200221
    • Initial build
    - 20200403
    • March security patches
    • Many optimisations and smaller fixes
    • Rootdir updated from A6 2018 Q, along with some proprietary files
    • Graphics now r29, from A6 2018 Q
    • Way too much stuff to list here, thx @Astrako for the work :D
    - 20200613
    • Fixed GPlay crashes
    • June security patch, and all other LineageOS source changes
    • SEPolicy Enforcing
    • Reworked shims
    • Now using new power HAL
    • Many smaller optimisations
    - 20200713
    • July security patch and all other LineageOS source changes
    • Reworked overlays
    • ROM now passes SafetyNet out of the box
    • Defined location provider to *hopefully* fix location with MicroG
    • Updated OMX libs
    • Other smaller fixes and optimisations
    - 20200825 20200830
    • August security patch and all other LineageOS source changes
    • Updated FP from coral's April patch to keep passing SafetyNet
    • Switched to proprietary audio HAL - fixed in-call echo
    • Other smaller fixes and optimisations
    • NOTE: Encryption is currently extremely broken and your device will not boot if you'll try and encrypt.
    - 20210118
    • January security patch and all other LineageOS source changes
    • Other smaller fixes and optimisations
    9
    New build is coming tommorow with echo in calls fixed and various other things!
    (huge props to @Astrako as always)
    8
    No, sorry :(. Waiting for that too.
    I am wondering why echos are not present in VoIP calls (like WA or Telegram). Do that use different drivers/layers?
    Also, from the reports of a Galaxy Tab A (2016) it seems @Valera1978 could solve that.

    The problem is that we are using the Open source Audio HAL, which doesn't support Samsung's proprietary noise reduction. Once there is a viable proprietary alternative, it will be implemented

    EDIT: I am trying to implement the proprietary HAL used in gtaxlwifi, *hopefully* should work
    7
    All these bugs with gapps will be fixed in next update.