[UNOFFICIAL][LineageOS 20.0][ Android 13 ] For A310, A510, and A710[ALPHA]

Search This thread

mtek89

Member
Oct 15, 2019
17
1
Okay Im going to ask again: where is the dev branch for this LOS20 release?


All I see is 17, 18, 19.

I want to patch some of the issues I've been having, but without seeing the branch that made the ROM this is impossible.

Release you sources, how am I supposed to trust that there's no hidden malware in there?

This is a fantastic ROM, working great on my A3 -- thanks for your hard work!

I noticed that Wifi Casting doesn't seem to be an option (three dots on casting screen for Wifi option doesn't seem to exist).

Off-topic:
I tried to get Magisk to work (sideload it right after sideloading the main zip), but when I tried to run the Magisk app after booting it said it wasn't active. I tried to get it patch your ROM image, but it couldn't do it. I am able to use rooted apps, though, so I still count it kind of as a win.

On-topic:
It seems pretty stable and I'm using it as my daily driver

Edit1: Sleep
I'm noticing faster battery draining during idle action. A full charge will lose 40% over 8 hours overnight when in Airplane mode and Battery Saver is on.

This is much more idle draining than LOS 17, which I was previously on.

Are the sleep modes fully activated on this ROM?

Edit2: Sources
I want to try patching some of these battery issues myself (I see a lot of BatteryExtHandler errors), but couldn't find the lineage-20 branch in the source code:


Where's the alpha branch?
 

Nova6K0

New member
Dec 8, 2022
3
4
43
Hello friends, I see that you are having problems with sound, specifically with sound controls. This is because configuration files are missing. And although html6405, he is doing a great job with his unofficial versions of LineageOS 19.x and 20, Android 10+, changes some things, which cause problems. The first thing is that .conf files no longer work (.conf to .xml compatibility form is removed since Android 10). All files have to be XML. And they must be in, this case in:

system/vendor/etc

And with the following attributes/permissions:

user (uid 0): root
group: (guid 0) root
permissions (octal): 644 -> -rw-r--r--

The missing files, you can download them from the Android 13 Source Code itself:

https://android.googlesource.com/platform/frameworks/av/+/refs/heads/master/services/audiopolicy/config/

The main problem is that it was missing, some important file such as default_volume_tables.xml not being found, it is as if the volume was always zero. And in fact if you went up manually, it returned to zero. At least in the case of my SM-A510F.

By the way, you can copy them all, it is the best. Everything has to do with each set of files, it is a revision or change of Framework (since API 29+ Android 10). Where you have to match the content of this, if not when the problems come. If you look, a 7.0 appears, at the end of some files. This is because it is version 7.0 (HAL/audioserver). The current one is 7.1, but with that it would work for you.

You can overwrite those who exist, but remember the correct permissions, if not it will not work, and even when restarting you will generate a bootloop.

Greetings.
 
Last edited:

html6405

Recognized Developer
The main problem is that it was missing, some important file such as default_volume_tables.xml not being found, it is as if the volume was always zero. And in fact if you went up manually, it returned to zero. At least in the case of my SM-A510F.
Hi,

thanks, default_volume_tables was really accidentally missing on one of the first builds,
but it should be already back,
but I fear the audio server crash has another reason.
Aren't you facing it while a phone call?
New builds are in the making.
 

Nova6K0

New member
Dec 8, 2022
3
4
43
It is a pleasure. And indeed. I am looking at the "App Manager" event viewer (another wonder, by the way) and puts something related to the AudioFlinger, which does not correspond to two flags, with the identifiers 0x0000006 and 0x0000008. That one had to be the other, as if they were the other way around. Forgive that I have certain knowledge, but not at your level.

In any case, I reiterate the thank you, for your great job.

Greetings.
 
  • Like
Reactions: html6405
May 30, 2013
8
0
Hey,

I'm on an A5 2016 from Belgium, and I'm having issues with the ROM. I started on an official rom with no root.

1. I rooted the phone (with some rootkit that I flashed via ODIN)
2. I installed TWRP 3.2.1.0
3. I downloaded the following zip : 20.0-20221130-HTML6405-a5xelte.zip
4. I Copied the above zip on the phone
5. I launched the install through TWRP

The phone's stuck in the "loading" screen.

Do you know what I'm doing wrong?

Thank you
 

kurtn

Senior Member
Jan 28, 2017
4,855
2,178
Small town in Bavaria
POCO M2 Pro
Hey,

I'm on an A5 2016 from Belgium, and I'm having issues with the ROM. I started on an official rom with no root.

1. I rooted the phone (with some rootkit that I flashed via ODIN)
2. I installed TWRP 3.2.1.0
3. I downloaded the following zip : 20.0-20221130-HTML6405-a5xelte.zip
4. I Copied the above zip on the phone
5. I launched the install through TWRP

The phone's stuck in the "loading" screen.

Do you know what I'm doing wrong?

Thank you
You forgot to factory reset / Format data.

Why don't you follow
 
  • Like
Reactions: notnoelchannel

mtek89

Member
Oct 15, 2019
17
1
Screw it. I wanted to like this ROM, but simple things that should work simply don't (3G, calls, decent battery life, low RAM usage). Worst of all, the developer won't share their source (or actively ignores my comments), which makes it extremely difficult to trust that any changes were made in good faith, nor contribute any meaningful patches.

Yes I know - don't like; don't use. I wanted to like it, but I simply don't trust this developer any more.

I will go back to the trusty danwood76 lineage-18.1 branch. At least he shares his sources.
 

html6405

Recognized Developer
Screw it. I wanted to like this ROM, but simple things that should work simply don't (3G, calls, decent battery life, low RAM usage). Worst of all, the developer won't share their source (or actively ignores my comments), which makes it extremely difficult to trust that any changes were made in good faith, nor contribute any meaningful patches.

Yes I know - don't like; don't use. I wanted to like it, but I simply don't trust this developer any more.

I will go back to the trusty danwood76 lineage-18.1 branch. At least he shares his sources.
Man, I'm busy and can't answere 100 messages per day, I have a job, life and a family to care for, so I'm sorry that I only find 5 minutes per day for XDA.

All my sources are on Github.
You can use the 19.1 branch, there is no 20.0 because there haven't been any changes in this repository,
but I will create another branch later if there will follow some commits.
but I simply don't trust this developer any more.
Thats not a problem for me.
I will go back to the trusty danwood76 lineage-18.1 branch. At least he shares his sources.
Good bye 👋
 

mtek89

Member
Oct 15, 2019
17
1
First of all, forgive my tone -- it genuinely felt like you were deliberately ignoring my requests for the source, since I'd asked twice before.

Secondly, thanks for dedicating any time at all towards FOSS projects. Toxicity from needy users (such as myself) can really drain any motivation to contribute anything at all, and juggling work and life along with projects like these is definitely not an easy feat and shouldn't be taken for granted.

Genuinely, apologies for my tone.

I guess I have one question then - is this LOS 19 or LOS 20? And if the latter, why is it not called LOS 19.1 or something?

Thanks again
 

html6405

Recognized Developer
First of all, forgive my tone -- it genuinely felt like you were deliberately ignoring my requests for the source, since I'd asked twice before.

Secondly, thanks for dedicating any time at all towards FOSS projects. Toxicity from needy users (such as myself) can really drain any motivation to contribute anything at all, and juggling work and life along with projects like these is definitely not an easy feat and shouldn't be taken for granted.

Genuinely, apologies for my tone.

I guess I have one question then - is this LOS 19 or LOS 20? And if the latter, why is it not called LOS 19.1 or something?

Thanks again
It's ok, I forgive you, I just wanted to clarify that I'm not ignoring anybody, any message or anything else.
I really just can answere a few questions per day and I have many threads, because I'm maintaining more than 10 devices and my spare time is really limited.
Sometimes it's better to contact me via PM, I try to help where I can.
I will recheck all sources later, if I've forgot anything to push.

This is LOS 20.0, but there were no changes needed from 19.0 to 20.0 in the a3xelte repo for example.

But I guess 3G, phone calls etc should work in this builds. Is your IMEI shown? Maybe this causes the battery drain on your phone?
 
  • Like
Reactions: mtek89

mtek89

Member
Oct 15, 2019
17
1
IMEI is showing, and phone calls do theoretically work I was just having the audio crashing issue. No 3G or LTE data though. The battery drain issue I still have no idea about, but I need to charge twice a day, instead of once back on 18-0
 

plaquito

New member
Feb 5, 2023
1
0
Hi,

thanks, default_volume_tables was really accidentally missing on one of the first builds,
but it should be already back,
but I fear the audio server crash has another reason.
Aren't you facing it while a phone call?
New builds are in the making.
Hi,

I can't wait to test this new build because I have exactly the problem described on my a3xelte, are you still working on it?

Great job for this rom anyway :)
 

Zentriks

Member
Dec 26, 2021
15
2
Xiaomi Mi 8
Anyone else having problems with volume sliders on A5. Mine tells me it's 0% for media, but when smth is played it's 100% media volume...
 
Found new bug, data usage cannot be checked
 

Attachments

  • Screenshot_20230214-114126_Gallery.png
    Screenshot_20230214-114126_Gallery.png
    56.6 KB · Views: 17
  • Screenshot_20230214-114121_Gallery.png
    Screenshot_20230214-114121_Gallery.png
    68.7 KB · Views: 17

Bogdans29

Senior Member
Jun 26, 2017
546
97
Samsung Galaxy Note 9
Is there gonna be any updates bcs

Quick settings cant expand
Home and recent buttons dont work only beck button works
Google play cant download and install apks
Default browser dont have permision do download files
In settings whan you tap to aplication nothing heppens
Audio is broken
A5 2016
Also lastest recovery is sttucking at samsung logo
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Thanks to @html6405 the room is pretty stable for my old devices for my daughter

    I fixed everything with the missing files, some are still away. Don't know if deleted or just undetectable.

    Use my small guide for a successful dirty flash:

    Optional:



    Now the Lineage 20 (a5xelte) works well, but found a few bugs.
    The biggest first:

    - Vol. up + down button doesn't work
    (I generally can't change the volume)
    - Can't download/update apps with PlayStore
    > pending... (view screenshot)
    (used/flashed BiTGapps via Magisk)
    - Bluetooth doesn't work
    (view screen record)

    Edit:
    With Bluetooth it's the same like with LineageOS 18.1 and 19.1. It needs many tries and reboots that it works. Now it does. Don't know the exact way to fix.

    Found another bug(s):

    - Smart Lock doesn't work
    (If I try to active it and choose my smart watch, there comes just a black screen...)
    - Up- and download-speed in the statusbar don't work

    I can confirm using my A5:
    - Volume up / down not working, but when opening apps the sound is 100% and we can't control it (still looking for a workaround, maybe using some magisk module?)
    - For download pending that @8y73 facing I manage to solve on My end (Using BitGapps as well), it's because somehow by default the play store and play service is not granted access to the network. To solve it, go to Google Play Store and Play Service (and other google related app) app info in android settings -> Mobile Data & Wifi -> Turn on -> Profit (You might need to also clear cache, retry download, or reboot, please try those combinations)


    Oh, and I need to do clean flash for the room to be able to boot + using TWRP 3.5.2.

    Dirty flash will either bootloop or stuck on startup screen.
    TWRP below requirement causing bootloop
  • 9
    Code:
    /*
    * Your warranty is now void.
    *
    * 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.
    *
    */
    Hi,

    here you can find my build for the A310, A510, and A710,
    most problems are already solved.

    Here you can see how far everything is working for now.

    • Boot
    • Audio
    • Bluetooth
    • Graphics
    • Cameras
    • Wifi
    • USB
    • Video playback (HW/SW)
    • Tethering via USB
    • OTA-Updates
    • RIL
    • Mobile data
    • GPS
    • DRM
    • Tethering via WIFI and Bluetooth
    • much more...
    • Sensors
    • Audio server is crashing in a phone call for a5 and a7
    • Date usage because of missing eBPF

    Do you like my work?
    Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
    I'm doing this in my free time and it also costs a lot of money to buy hardware.

    donate

    Instructions (for S3, simply use the files for your device)
    XDA:DevDB Information
    [ROM][13.x][a3xelte a5xelte a7xelte][ALPHA] LineageOS 20, ROM for the Samsung Galaxy A3, A5 and A7 ( A310, A510, and A710)

    Contributors

    html6405
    Source Code: https://github.com/html6405

    ROM OS Version: 13.x T
    ROM Kernel: Linux 3.x
    ROM Firmware Required: TWRP 3.5.2
    Based On: LineageOS

    Thanks
    danwood76 for the great work for these devices
    The LineageOS team
    And all others who have contributed to the Exynos projects past and present

    Version Information
    Status:
    Alpha

    Created 2022-11-30
    Last Updated 2022-11-30
    2
    Thanks to @html6405 the room is pretty stable for my old devices for my daughter

    I fixed everything with the missing files, some are still away. Don't know if deleted or just undetectable.

    Use my small guide for a successful dirty flash:

    Optional:



    Now the Lineage 20 (a5xelte) works well, but found a few bugs.
    The biggest first:

    - Vol. up + down button doesn't work
    (I generally can't change the volume)
    - Can't download/update apps with PlayStore
    > pending... (view screenshot)
    (used/flashed BiTGapps via Magisk)
    - Bluetooth doesn't work
    (view screen record)

    Edit:
    With Bluetooth it's the same like with LineageOS 18.1 and 19.1. It needs many tries and reboots that it works. Now it does. Don't know the exact way to fix.

    Found another bug(s):

    - Smart Lock doesn't work
    (If I try to active it and choose my smart watch, there comes just a black screen...)
    - Up- and download-speed in the statusbar don't work

    I can confirm using my A5:
    - Volume up / down not working, but when opening apps the sound is 100% and we can't control it (still looking for a workaround, maybe using some magisk module?)
    - For download pending that @8y73 facing I manage to solve on My end (Using BitGapps as well), it's because somehow by default the play store and play service is not granted access to the network. To solve it, go to Google Play Store and Play Service (and other google related app) app info in android settings -> Mobile Data & Wifi -> Turn on -> Profit (You might need to also clear cache, retry download, or reboot, please try those combinations)


    Oh, and I need to do clean flash for the room to be able to boot + using TWRP 3.5.2.

    Dirty flash will either bootloop or stuck on startup screen.
    TWRP below requirement causing bootloop
    2
    Hello friends, I see that you are having problems with sound, specifically with sound controls. This is because configuration files are missing. And although html6405, he is doing a great job with his unofficial versions of LineageOS 19.x and 20, Android 10+, changes some things, which cause problems. The first thing is that .conf files no longer work (.conf to .xml compatibility form is removed since Android 10). All files have to be XML. And they must be in, this case in:

    system/vendor/etc

    And with the following attributes/permissions:

    user (uid 0): root
    group: (guid 0) root
    permissions (octal): 644 -> -rw-r--r--

    The missing files, you can download them from the Android 13 Source Code itself:

    https://android.googlesource.com/platform/frameworks/av/+/refs/heads/master/services/audiopolicy/config/

    The main problem is that it was missing, some important file such as default_volume_tables.xml not being found, it is as if the volume was always zero. And in fact if you went up manually, it returned to zero. At least in the case of my SM-A510F.

    By the way, you can copy them all, it is the best. Everything has to do with each set of files, it is a revision or change of Framework (since API 29+ Android 10). Where you have to match the content of this, if not when the problems come. If you look, a 7.0 appears, at the end of some files. This is because it is version 7.0 (HAL/audioserver). The current one is 7.1, but with that it would work for you.

    You can overwrite those who exist, but remember the correct permissions, if not it will not work, and even when restarting you will generate a bootloop.

    Greetings.
    2
    Yes, I have the same audio issues described by @RidaRida08
    So far I haven't found a way to circumvent this sound issue. It also shows the mute sounds icon twice.


    Also in whatsapp when I do a videocall, video is fine but audio is scrumbled.

    Just a sidenote, apart from the sound issue I am really happy with the performance. I did not came across other issues. I installed BiTGApps - arm -13.0.0-v1.8signed

    Let me know if there is something I can do to fix this one, share logs or something similar.
    2
    The main problem is that it was missing, some important file such as default_volume_tables.xml not being found, it is as if the volume was always zero. And in fact if you went up manually, it returned to zero. At least in the case of my SM-A510F.
    Hi,

    thanks, default_volume_tables was really accidentally missing on one of the first builds,
    but it should be already back,
    but I fear the audio server crash has another reason.
    Aren't you facing it while a phone call?
    New builds are in the making.