Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by agent008

  1. Thanks for your interest in helping. I can say that the last time I changed the screen (this is the second time now) it was the same. Screen completely unresponsive, 100% not working until the update came through. The problem now is that the OTA provider for the update is not serving the updates anymore! Therefore -- THIS IS IMPORTANT! @EskeRahn you might want to put this info somewhere very visible. If you are considering a screen replacement right now, don't do it until a way has been figured out to update the screen without the OTA! I would be very thankful if someone could provid
  2. I did because back then (in early 2021) it was the only way that solved for me (then later on stopped working anyway). Now after I solve my screen I'll use the QX1000 fingerprint. thanks
  3. If anyone can help me with the screen update package I'll be grateful. I was foolish enough to install a new screen without visiting the forum and this thread. Turns out the stock OTA updates are not working anymore and now I have a phone with a beautiful new screen that doesn't work (no touch at all!) and I can't solve it. Besides my hardware keyboard stopped working a couple weeks ago, so the only way I can use the phone now is by plugging an external mouse and keyboard... 😪
  4. Eske, have you ever heard of the "58 megabyte" update that installs on top of stock that @divstar mentioned? My memory isn't very sure but I believe I also had to go through this to make the digitiser to work last year when I replaced the screen for the first time. I wonder if that update can be downloaded somewhere?
  5. An observation: it is interesting that the device fingerprint remained as "Sony Xperia" (I don't remember the model, XZ II maybe?) even after flashing stock. Also, I got the fingerprint bug, seems "persist.img" is not included in the "back to stock" package? EDIT: never mind, persist.img is also part of the package. Sorry.
  6. Yes, it is. Actually my saga is longer and more convoluted. I had a cracked screen. Installed a new one like I did last year. Touch wouldn't work at all (like last time). Not only the edges but no touch is registered. I then went back to stock to see if the touch issue would be fixed. No dice. Plugged in a keyboard and mouse and tried to set up the stock firmware because I read that an OTA update might for stock solve the touch issue -- read it here: However, stock would show 'no updates'. But when configuring the device I realised that Google asked me to confirm on my other devices
  7. I successfully installed LineageOS19.1 20220502 with MindTheGapps 12.1.0 20220416, but I can't get past the welcome screen setup part. After it asks me for the PIN or lock pattern it takes me to the fingerprint setup. As soon as I finish the fingerprint setup it enters a loop, asking me again for the PIN or pattern and taking me through the fingerprint setup all over again.
  8. How difficult was it to find a new USB port for your Pro1?
  9. Great news! I'm reinstalling today because I replaced my screen (again) and need to go back to stock to make the touch digitiser to work. Has anybody at this point tried Magisk and Google Pay?
  10. I agree. I follow this sparsely but do not post much here anymore (lack of time). Just last night I have replaced the screen for the second time, and am now in the process of going back to stock, then reinstalling AICP yet again. Also my keyboard is inoperative (maybe a hardware issue, let's see after the reflash). I took the opportunity to open the back of the phone while changing the screen, I disconnected and reconnected the keyboard flat cable (it didn't solve the issue) but did not feel like tearing the whole thing apart before trying the reflash, which I need anyway because the touc
  11. Thanks. Yes, I also agreed to location services. But my phone often loses GPS fix and is usually clueless about where it is (maybe it's a good thing so nobody's tracking me? 😁) I had OpenGapps on the Q Beta, and also tried OpenGapps with this fresh AICP R install. Didn't make a difference, couldn't make SafetyNet nor GPS work with either of them. I'm now suspicious of the issue discussed here: But, I don't know how to change this file on my phone. Having Magisk installed, it seems I do not have a straightforward /system mountpoint? 🧐
  12. Hey guys, I'm having an issue with location. I already had the same problem on AICP Q beta. (Beta also had an issue with notifications. Most apps' notifications never played a sound or vibrated, this is now working on AICP R). I can't reliably get my location on Google Maps and other apps that depend on Google's location services infrastructure. I've already gone through all of the location settings and permissions to no avail. It seems that apps that communicate directly with the GPS work OK. Does anybody have any suggestions? Is AICP's standard behaviour to not allow location
  13. Wiped my phone which was still running AICP beta, installed November 10th build yesterday. I'm battling SafetyNet issues now but the ROM is running fine.
  14. @Rob. S.: Thanks for this thread. Your summary worked perfectly for me, I'm currently just battling with getting SafetyNet ctsProfile to pass. I too replaced my screen but somewhat botched the job, so another screen is on the way from China. Is there any possibility that someone could extract the "capacitive sensor firmware upgrade" part from the stock ROM so that when my new screen arrives I don't have to factory reset and reinstall the stock ROM all over again? Or tell me how to do it and I'd go about extracting the thing myself. I believe others wouls also benefit from this.
  15. Whoa! It had been a while that I didn't log in here. This is tremendously good news. @tdm being back and AICP with weekly builds. Thank you so much. Has anyone tried dirty flashing over the previous AICP? It would be better for me to not have to contact my banks to recreate all the smart tokens etc.
  16. Update on this. I use FairEmail as my email client. Also doesn't play any notification sounds. I use QkSMS for texts and it's notifications work fine. Whatsapp calls do work - phone plays repeatedly the sound that was meant to be played for incoming messages. Did anybody have the same problem?
  17. I chose a particularly bad example nthat was easy at hand. Many times my pictures seem to have a varying focus inside the picture. I will try to find some more examples to post, would be nice to have others' opinions as I might be biased by what I read here at the forum. With Open Camera I always had to set the manual focus to a distance which was totally different than the real distance between the phone and the phto subject. So, I'm not sure anymore whether there's a software bug when talking to the camera hardware where the focus distances are not interpreted/calculated correctly;
  18. It's because some people are getting to take only out of focus photos, like I am. 😩
  19. Oh man. It must be that my camera is kaputt. (Maybe from the beginning?) I never could figure out how to get the camera to focus properly. All my shots are ridiculous, as if I was using a 2004 VGA phone camera 🤦‍♂️ Example: Taken of my new toy and my youngest feline from inside the garage. Such a garbage focus.
  20. By the way. Whatsapp notifications don't make any sound for me. No matter what I choose on the settings, it just doesn't play any sound. The visual notification works ok, though. Has anybody had the same issue?
  21. oh no! I should've asked around before jumping ship to AICP. I'm liking it too. Battery life's great. I hope all's well with @tdm , that this might be temporary, and that he keeps doing his great work on the ROM.
  22. The Fxtec signature didn't work for me. That's why I chose the Sony one. EDIT: Well, of course, I ran the props command and it showed the current signature my device had. I compared it to the Pro1 key available from the list and found out they were the same. So I didn't confirm the changes and tried safetynet and Gpay, both failed. Maybe if I had confirmed the props script (even though signatures were the same between current and new one), it would have worked? On the surface it seemed nothing was being changed, but maybe the script would still change something even if confirming wit
  23. I took the plunge and installed AICP Q yesterday (coming from LOs 17). I can't however check for updates. Did I do something wrong? EDIT: It means I'm now on the Feb 6th 2021 version. Checking for updates gives the error message below (Failure while trying to check for updates. Please check your Internet connection and try again later) Thanks
  24. Thanks for the guide. In order to avoid having to install an "unofficial" Magisk module (Gpay SQlite fix) I simply used "props" command (from Magisk Hide Props Config module) to change my phone's signature to that of a Sony Xperia 10 II (Android 10). This instantly allowed SafetyNet to pass and adding cards to GPay.
  25. For me it's 17.1 Currently running 20201214 (I think). Am updating now to 20210118. Thanks
  • Create New...

Important Information