-
Content Count
1,053 -
Joined
-
Last visited
-
Days Won
76
Everything posted by Rob. S.
-
LineageOS 18.1 Official Release for Pro1
Rob. S. replied to Wheeljack's topic in Pro1 - Thoughts & questions
@VaZso I just went through the procedure of moving to LOS 18.1 from stock, too (even though I went through stock only to get those display margins right after a display replacement, after I had bought my device with LOS already installed, so I saw stock for the first and only a short time)... Booting LOS for the first time always took unusually long for me (compared to a normal boot), regardless of the device, and no matter whether with or without Magisk, and it did so again this time. I guess that's just normal. To the best of my knowledge, user data needs to be wiped before flashin -
I guess this is the time to mention @Erik so that he might get notice about @adam.c.r.roman's and @Swond's above cases? With the regularity these cases come up even with the limited base of existing Pro1 devices, I fear it is now becoming enough bad publicity to deter potential customers for the upcoming Pro1X. Regarding @ToniCipriani's case β I think we can be sure now that new display replacements will not come earlier than the new Pro1X itself, which (as of now) means not before October or November. Also, we don't know if there even will be black screen casings to buy for our exis
-
Ok, now I do: They're M1.4x2 and any shop that sells small screws should carry them. Also, they're easy to find in black, too, looking good enough for me to not bother with the black stickers anymore. (The black ones I just bought have a slightly thicker head than the original silver screws, but it's still flat enough for the black stickers to perfectly fit on top of them.)
- 157 replies
-
- 10
-
You might want to try the 'AccuBattery' app for that; to record charge and discharge periods is one of its features.
-
Ok, no, it isn't! That's too small. (And no, I won't reveal how much I paid for them... π€¨) Next size from the list of Nokia E7 screws is M1.4x2.3 which now should be the right one β also something similar enough should be much easier (and cheaper) to source... I'll report back later...
-
Pro1, Ghost touches and other digitizer and display issues
Rob. S. replied to michal@hanu.la's topic in Support
Better still, there actually is something between the LED and the display glass now although I don't think it does much to diffuse the light: After I glued on the display and finally removed the protective film, I sat there and scratched my head and asked myself why there still was a red tab on the upper side of the screen! -
Thanks for reminding me of that insightful table. No, I didn't exclude anything from the restore, only Chrome and Maps after TB got stuck or complained. I didn't even have in mind that switching the GApps package could have made a difference ("what could go wrong") at the time... Ok, then I guess it's back to step 4. β probably best if I choose MindTheGapps again for the new attempt..
-
This is what I did (starting with a fully functional and stable LOS 18.1 + GApps + Magisk + XPosed setup): Backed up everything (Titanium Backup). Replaced display. Flashed stock according to @Waxberry's [Guide] Restore to stock firmware using Fastboot method. Used the 20200825 firmware (it was necessary to re-enable the four commented-out lines in fastboot_all.bat). Display margins returned to normal on first boot. No installation of newer OTA updates necessary. Reinstalled LOS 18.1, GApps, Magisk, XPosed like in https://wiki.lineageos.org/devices/pro1/install and
-
Yes, they're slow end even erratic in answering emails... Also, sending multiple emails on the same subject is prone to slow things down even further, because that's how they said their ticket system works; another ticket on the same issue moves the issue to the end of the queue. That said, shouldn't your not being at home for a parcel be a subject between you and the parcel service? [Edit : didn't see your post in the other thread earlier]
-
ProΒΉ X β state of production and delivery
Rob. S. replied to Rob. S.'s topic in Pro1 - Thoughts & questions
-
Pro1, Ghost touches and other digitizer and display issues
Rob. S. replied to michal@hanu.la's topic in Support
Bummer! I just did my first own screen replacement (which seems to have gone well and was easier than I thought, and I also used B-7000 which is much easier to work with than any other glue I ever used for anything before, thanks to the tiny metal nozzle) but I forgot about the LED issue! -
Good question... Any new information on that, perhaps? [Edit] Earlier, someone reported success with black screws (black in order to make the stickers superfluous) from a Nokia E7 repair kit, which I gather must be the smallest of the few sizes Nokia had used in that phone, which would be M1.0x1.9 ? [Edit: No, it isn't. See followups...]
-
The location has changed, the teardown guide is now here: https://github.com/imax9000/fxtec-pro1-teardown
-
Theoretically, ACC/AccA has that function, it's called "charging power control" and it lets you set limits for both voltage and current. Problem is, so informs us the app, "unfortunately not all devices/kernels support this feature", and unfortunately I've had no luck getting this to work on the Pro1, either. Within the app, there's also no way to find out whether the device or the kernel is to blame... Another cool feature doesn't work with the Pro1, either: "prioritize battery idle mode": "This allows supported device to draw power directly from the external power supply when charging i
-
My Pro1 hasn't seen much use as of late due to my habit of breaking the screen, still charging has had a few hiccups here and there β though nothing as drastic as having to reboot to start charging again, if I remember correctly. That said, I'm running LineageOS 18.1 with Magisk and I have the ACC (Advanced Charging Controller) daemon installed as a Magisk module (plus the AccA app), which I had thought to be the culprit here. Whether it was or wasn't, whenever the phone wasn't charging although it should, I opened the AccA app and that usually made charging start again...
-
LineageOS 18.1 Official Release for Pro1
Rob. S. replied to Wheeljack's topic in Pro1 - Thoughts & questions
Its purpose is to bring the tap-insensitive display borders back from too wide to normal after a display replacement. If you need a display replacement and you get one from any other source than Fxtec (and Fxtec has been out of replacement units for some months now, also they're expensive as they include casing and front camera and other electronics), those replacement units will come with significantly wider tap-insensitive borders β to the extent of making it difficult to impossible to use some functions in some apps, even with the margin settings provided by LineageOS reduced to zero. -
LineageOS 18.1 Official Release for Pro1
Rob. S. replied to Wheeljack's topic in Pro1 - Thoughts & questions
Thanks @EskeRahn. Doesn't help me in flashing the display IC, though, which it seems requires a running LOS 17.1 or 16.1 or stock Android... -
LineageOS 18.1 Official Release for Pro1
Rob. S. replied to Wheeljack's topic in Pro1 - Thoughts & questions
Hmm... Is it possible to downgrade from LineageOS 18.1 to 17.1 without data loss (before upgrading to 18.1 again)? -
Display units with large tap-insensitive margin
Rob. S. replied to EvilDragon's topic in General Discussion
Thinking about it, the first time I had the screen replaced I could indeed still have been on LOS 16. That would explain it. (I would hate having to admit being too stupid to perform that relatively simple procedure π) -
Display units with large tap-insensitive margin
Rob. S. replied to EvilDragon's topic in General Discussion
It never asked for root permissions, as far as I can remember, so I couldn't grant any? About the updates, there were a few weekly security/bugfix updates for LOS 18.1, but nothing big... For what it's worth, I noticed in the adb root shell that the filesystem was mounted read-only, but remounting it as read/write β while letting me delete those two files I wanted to delete β didn't help with the display IC flash procedure, either. While I attempted the update once more today I noticed something else: a few seconds after starting, the flash tool showed a notice for one or to sec -
Display units with large tap-insensitive margin
Rob. S. replied to EvilDragon's topic in General Discussion
Now I have a new situation β I've got a repaired phone with a new replacement screen, only the driver flashing process to set the margins to a usable width doesn't work anymore. Tapping the app's 'update' button, the button stays orange for two or three seconds β but instead of starting the flashing process, the phone just cold-boots, with the margins staying as they were. (Yes, I double-checked everything, tried different PCs and stuff, but the connection isn't the problem this time, it's the part of the process that happens on the phone itself...) The big question now is, do I go a -
Display units with large tap-insensitive margin
Rob. S. replied to EvilDragon's topic in General Discussion
Things are getting more and more complicated in that regard. A number of apps don't work on a rooted device, and I fear they're getting more. Now some of them will work with MagiskHide, but some won't. On the other hand, some apps don't even work on an unrooted, alternative Android like LineageOS. They might explicitly check for a non-stock ROM, or they might check for an unlocked bootloader. Depending on how they do it, you might be out of luck whether you're rooted or not. With one important app (VPN identity token) which didn't run on the unrooted LOS that I had been using I was l -
Display units with large tap-insensitive margin
Rob. S. replied to EvilDragon's topic in General Discussion
From what I've read here, the driver does get updated with a stock reflash plus going through all OTA stock updates, as one of them includes the driver update. It would seem that Fxtec needed to apply the changes themselves because from some point on the displays they received (whether in production or for their repair units) were of the variation that needed them... -
Even in the EU, at least in Germany, those two years warranty are really only half a year, because after that it's the purchaser's obligation to prove that a defect was the manufacturer's fault. So a full year of real manufacturer's warranty may actually be an improvement to what the law requires.
-
I can't believe it, another screen broken β I just tried to swipe a fly from the display, and what I did was swiping the phone from the table, because the EFFING SCREEN PROTECTOR I'm now using since my last accident is sticky to the touch! So it's back to @EvilDragon's repair service...