Jump to content

mcdinner

Members
  • Content Count

    231
  • Joined

  • Last visited

  • Days Won

    1

mcdinner last won the day on September 17

mcdinner had the most liked content!

Community Reputation

373 Excellent

5 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. @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.
  4. 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.
  5. 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.
  6. 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
  7. So, i just started from scratch and now it works like a charm. :)
  8. 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
  9. 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!!
  10. 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?
  11. I can confirm crackling audio is gone on dialpad tones :)
  12. a2dp works now with my earphones. :) thank you! I'll try car connection tomorrow.
  13. Flashing right now. Hopefully it will help with audio and calls :)
  14. 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
×
×
  • Create New...

Important Information

Terms