In SatStat I don't see values for azimuth/nick/roll. Those are available in 17.1
[UNOFFICIAL][LineageOS 20.0][ Android 13 ] For A310, A510, and A710[ALPHA]
- Thread starter html6405
- Start date
notnoelchannel
Senior Member
Attachments
Hello,
Next time your phone is frozen or looping, try this combo that often helped me :
"Press and hold the Volume Down key and the Power key on your phone for about 10 to 20 seconds. Doing so executes a simulated battery disconnect on your device"
(see https://thedroidguy.com/fix-samsung-galaxy-a5-stuck-boot-screen-troubleshooting-guide-1078654 )
Just after it powers back on, you'll be able to reboot in recovery/download/normal mode.
Hoping this "good to know" may help.
RidaRida08
Member
notnoelchannel
Senior Member
RidaRida08
Member
RidaRida08
Member
Audio issue is the only thing preventing me from updating to LOS 20 
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.
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.
Last edited:
I use atm LineageOS 19.1 unofficial with Android 12L.
Is a dirty flash and OTA updates possible?
Edit: I saw at the previous page that a dirty install worked. I'll try it later too. But I have still the OTA question. It workes in the 19.1 version.
Is a dirty flash and OTA updates possible?
Edit: I saw at the previous page that a dirty install worked. I'll try it later too. But I have still the OTA question. It workes in the 19.1 version.
Last edited:
Like I'd sad; I dirty flashed it yesterday night (GMT+1).
1) Deactived the devices locking (like Fingerprint, etc)
2) Deactived all Magisk modules
3) Rebooted into SHRP to backup (much better than TWRP)
4) Flashed the zip
5) Wiped Dalvik Cache/ART (not sure about this, cause it was late and I had to sleep)
It worked at the first reboot, but because I was in a hurry I didn"t wait until the software started completly. Vol down + power button 2 do a new backup...
After this I was in a bootloop. I installed a backup and got a FRP lock. Now I installed Android 7 again and backuped to LAOS 19.1 with Android 12, but have a HUGE PROBLEM with my DATA:
I can't find my backup files/downloads/etc sincs the try with the new version.
I made a screenshot from the download folder. In none of the folders are visible files, sometimes emtpy folders.
Same in the SD card. I only could do a backup, cause I used a slot reader for the PC were I saw them. After this, the backup files were visible again.
Strange...
How to fix this? I need ur help and experience.
I need 2 see my files...
When it is fixed I'll give me more time for the flash.
Screenshots (normally there are a lot of files in it. Now EVERY folder is empty):
1) Deactived the devices locking (like Fingerprint, etc)
2) Deactived all Magisk modules
3) Rebooted into SHRP to backup (much better than TWRP)
4) Flashed the zip
5) Wiped Dalvik Cache/ART (not sure about this, cause it was late and I had to sleep)
It worked at the first reboot, but because I was in a hurry I didn"t wait until the software started completly. Vol down + power button 2 do a new backup...
After this I was in a bootloop. I installed a backup and got a FRP lock. Now I installed Android 7 again and backuped to LAOS 19.1 with Android 12, but have a HUGE PROBLEM with my DATA:
I can't find my backup files/downloads/etc sincs the try with the new version.
I made a screenshot from the download folder. In none of the folders are visible files, sometimes emtpy folders.
Same in the SD card. I only could do a backup, cause I used a slot reader for the PC were I saw them. After this, the backup files were visible again.
Strange...
How to fix this? I need ur help and experience.
I need 2 see my files...
When it is fixed I'll give me more time for the flash.
Screenshots (normally there are a lot of files in it. Now EVERY folder is empty):
Attachments
Last edited:
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:
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
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)
-
(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
Attachments
Last edited:
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:
github.com
Where's the alpha branch?
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:
GitHub - html6405/android_device_samsung_a3xelte
Contribute to html6405/android_device_samsung_a3xelte development by creating an account on GitHub.
github.com
Where's the alpha branch?
Last edited:
OK so here is a problem I hope someone cam help with. Son now has the a310 with this rom installed but hes a pokemon go nutcase(or sadsac) He has to login via his mums Facebook.. but he always gets the authentication error yet he can login on his tablet fine... the error only occurs on the this and the previous versions(18-19.1)
Has anyone managed to login if so how??? If not can anyone recommend a rom that would work?
thanks in advance
Has anyone managed to login if so how??? If not can anyone recommend a rom that would work?
thanks in advance
Pokémon go relies on safetynet for device integrity check. There are tricks with magisk to fake it.
Pokémon go relies on safetynet for device integrity check. There are tricks with magisk to fake it.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2Hello 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
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.2
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.
Thats not a problem for me.
Good bye
11
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? -
9Code:
/* * 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
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
XDA:DevDB InformationInstructions (for S3, simply use the files for your device)
[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-302Hello 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.2Yes, 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
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.
