mcdinner

indeed, infinite focus is blurry, but I have never used it before. according to google this seems to be a common LOS problem on many devices

I sent you a PM with download links. Hope it works somehow.

i7-6600U here and 20gb ram first build was <24h and if you do not clean up the output an update is faster. Updating Git takes a while. If you want I can give you my boot.img and you can test if it works for you installing the official builds.

As far as I understand you would need my builds i you don't want to lose any data. I switched to building everything by my own with several packages included. If you have enough space left its easy to do, even if you have no idea what you are doing (look at me as proof) Do the pre-built lineage4microg images still not work?

Sure, I can upload it but it is signed with my personal keys, so that could be a problem.

Same here, they will send me a new display when they get new ones. Also they asked me to send them the old one for investigation. I hope they can get money back from their supplier as this really looks like a production fault.

did you buy the version with frame?

Hmm maybe something like "ghost touches and unresponsive area on lower screen. Oh and for me touching the display in the upper half seems to help to reduce the ghost touches. But also the unresponsive are remains.

@EskeRahn Is it possible to rename the Thread? I think it would make sense to address the problem in the Title as there are a few people now with that problem.

Exactly the same here. It happens for me when open or closed so i don't think its the cable. After lying around the night the problem did not appear yet but the unresponsive 1cm area is still there, so its not completely gone. I think it will come back very soon.

multiple displays with the error on the same location sounds like some production fault. I'll write support an email when I'm back home. If they send me a new display and are ok with it I'll try to play around with the broken one a bit, applying heat or ice spray and see what happens.

So, mine started having the same problem 30 minutes ago 😞 Same position as shown in the videos here in the thread and I also have it since beginning of January. It did not drop or bump anywhere, just started ghosting while typing on keyboard. Telegram just went nuts from one second to another... 😞 Addition what I noticed: * there is a ~1cm area around "the line" where touch is not recognized right. If i move my finger slowly over it no touch is shown using developer settings showing touch * slight pressure while touching triggers the mass touches on the line much more often

So, i just started from scratch and now it works like a charm. :)

using my own boot image did the trick :) Install works smooth now, but after boot settings app and others just crash all the time and the system is not really working. I deleted cache and userdata so I guess there is a problem with the build itself now

Thanks for the hints, I'll start the build again as build artifacts got cleaned as I can see... Add Thank you so much for all the work with Lineage!!

Thanks to you tutorial I managed to build lineage for microg but I have a problem installing it with lineage recovery and sideload. After confirming to install with failed signature verification I get an error. Happens with test recovery from tdm, official recovery and with official build microg and my own one. Any Ideas what to do?

I can confirm crackling audio is gone on dialpad tones :)

a2dp works now with my earphones. :) thank you! I'll try car connection tomorrow.

Flashing right now. Hopefully it will help with audio and calls :)

Oh and I found something very strange in my logs but don't know if it is just a problem with matlog. Just look at the times the messages were logged. 2020-02-20-20-38-39.txt

sounds promising :) checked again, calling with telegram is not a problem but real calls are. No BT or wired headset connected and not on speaker. Just receiving call and holding my hand in front of the proximity sensor to turn display on and off Here Is a log for a call with the audio problem. 2020-02-20-20-59-26rec.txt

@tdm After I got called today and audio was gone again, the tries after that were broken too. yesterday my tests were all fine and id did several successful calls with display off and on a few times...

nice :) have a good weekend

4 days ago. I did not bother to try because you did not mention fixing anything related, 2 days ago i received a call but used speaker as workaround. I retried again with a new alarm set 15 minutes back from now. After reboot it i get notification for 2 upcoming alarms (the morning and my test) and after a few seconds it switches to missed the test alarm. It seems to take a few seconds to get the wifi or network to get correct time. After a few retries the testalarm started again. oO

I checked gsm call and it seems to work now with test6. 😄 I'll check again tomorrow. Something seems to be off with the clock. I rebooted at ~19:40 and before putting in my sim pin my 7:20 morning alarm activated. Weird... Also the last full charge from battery is 22 hours ago which is wrong because I started charging when i got to bed and it should not be more than 18 hours. I can give you the logs if it helps.