Before.About formatting the data, you do it before or after flashing rom?
Before.About formatting the data, you do it before or after flashing rom?
Strange.I softbricked by updating to this weeks update from last weeks update.
Two weeks ago I switched from 17.1 tot 18.1 by clean installing.
Last week I softbricked by updating from the clean install to the update of that week. I clean installed with the latest lineage package.
Yesterday same issue... I softbricked by updating the clean install to latest version.
What did I already try?
- reboot to TWRP
- reboot into system
- re install the update zip in TWRP
- re install the lineage package in TWRP
Now I have doubt as to the next step:
- TWRP wipe dalvik cach and reboot into system
- TWRP wipe cach and reboot into system
- TWRP wipe data,cach and reboot into system
-clean install and sit and wait for a clean install next week (the you are ****ed option)
More fundamental: how comes I softbrick every time?
On clean install I flash the RMM and verity-opt encrypt, lineage, gapp pico, magisk to root.
Lineage, TWRP all latest versions, no encription, use sd as internal mem
installed magisk and V4android module
Hide magisk from view and hide magisk for banking apps.
When it softbricks, try reinstalling both magisk and gapps (if you used these)I softbricked by updating to this weeks update from last weeks update.
Two weeks ago I switched from 17.1 tot 18.1 by clean installing.
Last week I softbricked by updating from the clean install to the update of that week. I clean installed with the latest lineage package.
Yesterday same issue... I softbricked by updating the clean install to latest version.
What did I already try?
- reboot to TWRP
- reboot into system
- re install the update zip in TWRP
- re install the lineage package in TWRP
Now I have doubt as to the next step:
- TWRP wipe dalvik cach and reboot into system
- TWRP wipe cach and reboot into system
- TWRP wipe data,cach and reboot into system
-clean install and sit and wait for a clean install next week (the you are ****ed option)
More fundamental: how comes I softbrick every time?
On clean install I flash the RMM and verity-opt encrypt, lineage, gapp pico, magisk to root.
Lineage, TWRP all latest versions, no encription, use sd as internal mem
installed magisk and V4android module
Hide magisk from view and hide magisk for banking apps.
nightly -> nightly is an automatic process if you use the updater. (Setttings > System > Advanced > Updater), so if it's needed it will do it. (also doesn't matter anymore, dalvik hasn't been a thing since 5.1 or thereabouts)Sorry for that question but can I update from nightly to a newer nightly (i. e. lineage-18.1-20210909-nightly-a5y17lte to lineage-18.1-20210916-nightly-a5y17lte) without wiping dalvik and so?
GPS won't work so fine and my hope is that it ist better after an update.
Edit: There's is an update function in lineage os. Till today there was no function and now it works. I'm able to update the os to the newset version but gps didn't work so fine. If I try to make an GPS-test it needs a little time to find satellites an then google maps an other apps they need gps will work but not after a restart of the device.
Any ideas?
FM radio isn't happening, at least not any time soonnightly -> nightly is an automatic process if you use the updater. (Setttings > System > Advanced > Updater), so if it's needed it will do it. (also doesn't matter anymore, dalvik hasn't been a thing since 5.1 or thereabouts)
Personally haven't had issues with GPS. Sure you're in an area with a clear line of sight to the sky, not around tall buildings, and not using a case made of metal?
Unrelated, but in the changelog, I'm noticing some mentions of FM (radio, presumably). Is there any progress on making it available for this device? Last I heard, it was mostly dropped until someone could make an open source version of the driver for it.
Thought as much.
Hi.(...) So I have only this one issue of crackling sounds via Wifi calling especially with my SIP client and a bit on telegram, the weird thing skype calls working fine. I tryed to flashing without gapps und deactivated each speech inputs on 17.1 and 18.1 Lineageos and CRdroid but nothing really works. The main thing is the SIP client with it i can use my phone as a landline phone, telegramm isnt much necessary.
(...)
I am aware of this bug. It is present both here and on other roms like riseq. Yes we can't get our aec and ns to work and multiple people have tried fixing it but unfortunately we haven't had any luck so far. This is an older Samsung phone issue and wrong UUID is not the problem here.Hi.
I had this crackling sound in WiFi calls (=VoIP) already on LOS 17.1. On my side I heard the crackling sound and the other party heard a quite strong and irritating echo of its own voice.
After LOS 17.1 was officially stopped, I set up a clean wiped A5 (2017) with the actual version from Sep 02 and tested the same VoIP app again: Unfortunately the symptoms were the same as under LOS 17.1. Strange: With the old and latest official Samsung Firmware this is not the case?!
While searching around I found a similar issue reported by the Fairphone community relating to FP2 (Android9). The analysis there showed that it has to do with the advance echo cancelling (AEC) chip that needs a specific UUID. The Fix on the FP2 is described under FP2: Fix UUID's of aec and ns for audio_pre_processing
Maybe a similar error still exists in the actual build. If yes, maybe the hint from the Github commit above leads to a solution.
As I'm not developper I have no clue how to perform this, but I'd be very happy if somone can do it as I like this phone AND first of all Lineage OS
PS: I can do tests of course as the latest build is not in production yet due to the described bug which is very annoying for me in daily use.
I would've done it already if I knew how. Original firmware is oreo. Well, okay...pie if you count a720s koreas rom. We are using android 11 ril + audio hal here. Not made for our device. Need to fixup the missing or incorrect function somewhere.Thank you for explaining. Would it be possible to analyse in some way how the original firmware can make proper use of the AEC?
Hi I could fix it with kernel auditor app setting TCP Congestion on "cubic" and Kernel Governor on "performance" that the crackling sound disappear. But sometimes after restart you have to set again probably the lineage kernel is not made to tweak.Hi.
I had this crackling sound in WiFi calls (=VoIP) already on LOS 17.1. On my side I heard the crackling sound and the other party heard a quite strong and irritating echo of its own voice.
After LOS 17.1 was officially stopped, I set up a clean wiped A5 (2017) with the actual version from Sep 02 and tested the same VoIP app again: Unfortunately the symptoms were the same as under LOS 17.1. Strange: With the old and latest official Samsung Firmware this is not the case?!
While searching around I found a similar issue reported by the Fairphone community relating to FP2 (Android9). The analysis there showed that it has to do with the advance echo cancelling (AEC) chip that needs a specific UUID. The Fix on the FP2 is described under FP2: Fix UUID's of aec and ns for audio_pre_processing
Maybe a similar error still exists in the actual build. If yes, maybe the hint from the Github commit above leads to a solution.
As I'm not developper I have no clue how to perform this, but I'd be very happy if somone can do it as I like this phone AND first of all Lineage OS
PS: I can do tests of course as the latest build is not in production yet due to the described bug which is very annoying for me in daily use.
I also have an A520W, and I do not have any issue with YouTube. Mind you, I don't typically play videos on the phone.@Option58
could the reason for my youtube lagging issue be that I am using the Canadian A520W version of the a5 and the firmware is based off of the A520F? I am not sure if there are hardware or firmware variations that could make this lag.
Yeah no one else seems to have been to replicate the problem, YouTube runs perfectly at full framerate on 1080p60I also have an A520W, and I do not have any issue with YouTube. Mind you, I don't typically play videos on the phone.
That's right, our kernel is 3.18 and there's no eBPF backport (yet). Fear not, I'm using a hack in core files to make everything work for my own a12 builds, but can't push that to official. However, that's just the current state, who knows what might happen eventually.The LineageOS 19 release notes say that only devices with kernels >= 4.4 will be supported, because eBPF support is required. I haven't installed the 19 preview here, but all the universal7880 kernel sources I can find are 3.x. Is there a branch I'm missing somewhere?
ro.surface_flinger.supports_background_blur=1
ro.sf.blurs_are_expensive=1
Hmm Then i think its a problem with you phone i have exactly the same model and it runs perfect exept from volte .hmm did you try a the latest stock rom?, ps.. ich komme auch aus deutschland wir können auch deutsch schreibeni have tried 3 different versions of lineage os und 2 other Roms. Nothing has happened, the problem is still there
/*
* 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.
*/