agent008
Members-
Content Count
227 -
Joined
-
Last visited
-
Days Won
4
Everything posted by agent008
-
Display units with large tap-insensitive margin
agent008 replied to EvilDragon's topic in General Discussion
Okay, before opening the phone again to check the screen connector etc I'll flash Lineage or AICP and Magisk for root then I'll run i2cdetect and report back here. Tks -
Display units with large tap-insensitive margin
agent008 replied to EvilDragon's topic in General Discussion
Thanks. Yes, I did. In fact the phone is on right now in hopes the OTA might come yet. haha If I remember correctly, last time it took an OTA to solve the screen too. However, I will reopen the phone this evening and recheck all connections. Maybe something is not right in there. I also can try the old screen and a third new one I have still on the box. Thanks for everyone's inputs! -
Display units with large tap-insensitive margin
agent008 replied to EvilDragon's topic in General Discussion
Thanks. With my Samsung laptop, it doesn't work. Or it might be my Pro1's already a bit worn out USB port? The saga continues... -
Display units with large tap-insensitive margin
agent008 replied to EvilDragon's topic in General Discussion
I used two different ports from my laptop, will try a third one. Thanks -
Display units with large tap-insensitive margin
agent008 replied to EvilDragon's topic in General Discussion
I see. I might try an older stock then, if OTA is still up i might be lucky. I only found older stock firmware at @tdms link but they are EDL files and his Linux tool didn't work for me. I'll try the windows tool. EDIT: or if anybody has the older fastboot image I'll be thankful if you share it with me. Fastboot works well with my Linux box. -
Display units with large tap-insensitive margin
agent008 replied to EvilDragon's topic in General Discussion
I flashed the 20200825 fastboot firmware from the Back to Stock guide thread: https://community.fxtec.com/topic/2466-guide-restore-to-stock-firmware-using-fastboot-method/?do=findComment&comment=33838 -
Display units with large tap-insensitive margin
agent008 replied to EvilDragon's topic in General Discussion
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 -
LineageOS 19.1 Official Release for Pro1
agent008 replied to wapsi's topic in Pro1 - Thoughts & questions
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 -
Display units with large tap-insensitive margin
agent008 replied to EvilDragon's topic in General Discussion
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... 😪 -
LineageOS 19.1 Official Release for Pro1
agent008 replied to wapsi's topic in Pro1 - Thoughts & questions
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? -
LineageOS 19.1 Official Release for Pro1
agent008 replied to wapsi's topic in Pro1 - Thoughts & questions
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. -
LineageOS 19.1 Official Release for Pro1
agent008 replied to wapsi's topic in Pro1 - Thoughts & questions
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 -
LineageOS 19.1 Official Release for Pro1
agent008 replied to wapsi's topic in Pro1 - Thoughts & questions
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. -
LineageOS 19.1 Official Release for Pro1
agent008 replied to wapsi's topic in Pro1 - Thoughts & questions
How difficult was it to find a new USB port for your Pro1? -
LineageOS 19.1 Official Release for Pro1
agent008 replied to wapsi's topic in Pro1 - Thoughts & questions
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? -
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
-
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? 🧐
-
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
-
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.
-
@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.
-
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.
-
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?
-
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;
-
It's because some people are getting to take only out of focus photos, like I am. 😩
-
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.