[UNOFFICIAL] LineageOS 18.1 For A310, A510, and A710

[kurtn]

hello do you recommend the ROM for daily use and which gapps should I choose?

Yes it is stable. LineageOS recommends mindthegapps. I recommend no GApps but f-droid

 

[CristianIs98]

Yes it is stable. LineageOS recommends mindthegapps. I recommend no GApps but f-droid

Thank you for your response.

 

[CristianIs98]

The ROM is amazing but a small problem occurs Instagram videos lowers the quality when playing them.

 

[nishhhhhh]

This is the solution to your problem. Just log out of your Google accounts in stock and you won't have issues.

You should be able to unlock the phone with a valid Google account in the setup wizard though.

Regards,
Danny

So I tried removing all the accounts including google and Samsung but the problem was still there so I decided to let it cool down. After a week or so did everything again and unlocked the phone from dev options and it worked so thank you for all the suggestions.

Also there seem to be a new problem with the device with lineage 18.1, I always had some screen flickering issues at low brightness in 17.1 but it seems to have worsen and screen would just flash and then go dark again when trying to unlock the phone (I've attached a small sample video) and this occurs randomly, sometimes it would work in a few tries but other times it would refuse to work and I have to force restart to get it working. This seem to happen more on low brightness and mostly when there's a lot of background processes and its running low on RAM. the issue doesn't exist on stock or 17.1

 

[CristianIs98]

So I tried removing all the accounts including google and Samsung but the problem was still there so I decided to let it cool down. After a week or so did everything again and unlocked the phone from dev options and it worked so thank you for all the suggestions.

Also there seem to be a new problem with the device with lineage 18.1, I always had some screen flickering issues at low brightness in 17.1 but it seems to have worsen and screen would just flash and then go dark again when trying to unlock the phone (I've attached a small sample video) and this occurs randomly, sometimes it would work in a few tries but other times it would refuse to work and I have to force restart to get it working. This seem to happen more on low brightness and mostly when there's a lot of background processes and its running low on RAM. the issue doesn't exist on stock or 17.1
View attachment 5507553

I also had the same thing happen to me, the only solution is to change the screen for a new one.

 

[danwood76]

So I tried removing all the accounts including google and Samsung but the problem was still there so I decided to let it cool down. After a week or so did everything again and unlocked the phone from dev options and it worked so thank you for all the suggestions.

Also there seem to be a new problem with the device with lineage 18.1, I always had some screen flickering issues at low brightness in 17.1 but it seems to have worsen and screen would just flash and then go dark again when trying to unlock the phone (I've attached a small sample video) and this occurs randomly, sometimes it would work in a few tries but other times it would refuse to work and I have to force restart to get it working. This seem to happen more on low brightness and mostly when there's a lot of background processes and its running low on RAM. the issue doesn't exist on stock or 17.1
View attachment 5507553

Looks strange. When it happens next can you dump a bug report afterwards and send it to me?

It might just be a bad/faulty display. Have you ever had it replaced?

Kind regards,
Danny

 

[fneuf]

Many thanks for this WIP!

What will be the status of ANT+ support in 18.1?

 

[lohtse]

Same here Need both screen caste and Ant+ reenabling for my a310f...



Is there an eta on next release yet??

 

[nishhhhhh]

Looks strange. When it happens next can you dump a bug report afterwards and send it to me?

It might just be a bad/faulty display. Have you ever had it replaced?

Kind regards,
Danny

Here is a bug report

 

[nishhhhhh]

I also had the same thing happen to me, the only solution is to change the screen for a new one.

I have this suspicion too, and screen does look a bit washed out but this only happens on this rom so maybe it is screen plus a bit of something else? like on stock ROM which I was forced to use for a month this issue isn't present, and this issue only shows up when the memory is clogged on lineage as well. So I thought about asking for a solution, this is now my secondary device so I'll try and clear a bit of storage and apps as well to see if it helps.

 

[vuut]

Looks strange. When it happens next can you dump a bug report afterwards and send it to me?

It might just be a bad/faulty display. Have you ever had it replaced?

Kind regards,
Danny

Does Rom support dual app as same stock ROm

 

[danwood76]

Here is a bug report

It looks like that is caused by low memory as you suspected. Which gapps are you using?

Kind regards,
Danny

 

[Gartenkralle]

Hey there,

i have a problem with my bluetooth connection in my car (Ford Focus Sync 3). The Bluetooth connection is very unstable. These are my steps:

1. turn on bluetooth
2. pair phone and car
3. wait for both devices to connect
4. wait another few seconds
5. its connected for a few seconds, then the bluetooth service crashes and bluetooth in the phone is deactivated
6. at the same time i get a popup message in my phone like this:
   
7. Clicking "Accept" or "Zulassen" doesn´t have any effect.
8. then bluetooth gets activated again and it tries to connect. -> it crashes again and the procedure starts from the beginning.

The problem is also described in the LOS gitlab. See here and here

Is anybody here with a similar behaviour? Unfortunately there is no clear solution yet... LOS 18.1 doesn´t have this issue so the final "solution" is an update to 18.1.

Appeareantly the problem exists since last year august, when an security update came out, but i´m not sure.

Dirk

 

[nishhhhhh]

It looks like that is caused by low memory as you suspected. Which gapps are you using?

Kind regards,
Danny

I'm using nano, should I downgrade and test it again?

 

[danwood76]

I'm using nano, should I downgrade and test it again?

Nano should be ok.

You must have an app that is eating all your ram. When the screen is off ram usage should be at its lowest.

Kind regards,
Danny

Hey there,

i have a problem with my bluetooth connection in my car (Ford Focus Sync 3). The Bluetooth connection is very unstable. These are my steps:

1. turn on bluetooth
2. pair phone and car
3. wait for both devices to connect
4. wait another few seconds
5. its connected for a few seconds, then the bluetooth service crashes and bluetooth in the phone is deactivated
6. at the same time i get a popup message in my phone like this:
   
7. Clicking "Accept" or "Zulassen" doesn´t have any effect.
8. then bluetooth gets activated again and it tries to connect. -> it crashes again and the procedure starts from the beginning.

The problem is also described in the LOS gitlab. See here and here

Is anybody here with a similar behaviour? Unfortunately there is no clear solution yet... LOS 18.1 doesn´t have this issue so the final "solution" is an update to 18.1.

Appeareantly the problem exists since last year august, when an security update came out, but i´m not sure.

Dirk

This thread is for LineageOS 18. 17.1 is nearly eol. Can you confirm it is ok in LineageOS 18.1?

From your log it looks like you aren't even using LineageOS? Can you dump an entire bug report?

Kind regards,
Danny

 

[Gartenkralle]

Nano should be ok.

You must have an app that is eating all your ram. When the screen is off ram usage should be at its lowest.

Kind regards,
Danny

This thread is for LineageOS 18. 17.1 is nearly eol. Can you confirm it is ok in LineageOS 18.1?

From your log it looks like you aren't even using LineageOS? Can you dump an entire bug report?

Kind regards,
Danny

Oh sh... yes you are right - my question belongs in the 17.1 thread. But yes i can confirm that the problem doesn´t exist in 18.1.

Dirk

 

[danwood76]

Oh sh... yes you are right - my question belongs in the 17.1 thread. But yes i can confirm that the problem doesn´t exist in 18.1.

Dirk

Then the solution is to switch to 18.1. Like I said 17.1 is nearly EOL anyway.

Also from your logs it looks like you aren't event using LineageOS but are infact using /e/?

 

[Gartenkralle]

Then the solution is to switch to 18.1. Like I said 17.1 is nearly EOL anyway.

Also from your logs it looks like you aren't event using LineageOS but are infact using /e/?

Yes you´re right, i tested several versions of 17.1 including /e/ and the official version from here. Unfortunately the attached logcat is from the /e/ version but the problem exists in both 17.1. versions.

OK then i think it´s time to switch to 18.1.

DIrk

 

[danwood76]

Yes you´re right, i tested several versions of 17.1 including /e/ and the official version from here. Unfortunately the attached logcat is from the /e/ version but the problem exists in both 17.1. versions.

OK then i think it´s time to switch to 18.1.

DIrk

I just had a quick look at github and this is the patch that fixed the issue in 18.1:

HFP: use Bundle to query call log and phonebook · LineageOS/[email protected]

Tag: #security Bug: 163269064 Test: manual Change-Id: I9dac26fb34d974d5a8e7f60d1ce609201e1d2ecf

github.com

 

[greebpaprika]

yada yada
weirdly, as i tried to rollback, both via flashing my backup (that i had made with twrp) as well as, after that led to a seemingly never ending boot process (not a loop, just taking way too long to boot, like 10 minutes or so) yada yada

hey,
the LOS 18 is working on my phone (a5 2016), my only issues are sometimes app crashes (both those that i were actively using and background things) and camera won't shoot a picture when opened via whatsappthe first try, then if i go back and try again it works normally, but this camera issue i already had in LOS 17.

now turns out i didnt properly backup my data so i'd like to re-flash my backup of LOS 17 which i made with twrp, get the data, and then flash LOS 18 again - for this, do I have to first flash LOS 17, then the backup, or is the backup enough? does the flashing have to be done via TWRP or would it also work with the LOS recovery that came with the zip?
kind regards