[Pro¹ X – state of production and delivery]

6 hours ago, linparda said:

Actually, they must have updated things - there were 3 left before I bought it and 2 left after I bought it. I checked. Maybe it is a different run? I see they started shipping already. I think only Germany and Korea are left and scheduled for next week, I believe. I like the mechanical keys and it is just a tad bigger than the Pro 1x - just under 3/4". I also like that the screen slides completely away from the keyboard. Of course, can't really tell which one I will like better until I get them both in my hands.

A tad BIGGER? I think the Pro1 is borderline too big. Wow.... I'd like a Pro1xc (c for compact, smaller like the Droid 4 lol)

[complaint problem, how long?]

On 5/24/2022 at 2:35 PM, pedro4444 said:

@EskeRahn

Hi now i have feedback.
They have repair parts so my phone is repaired.
reason for waiting that they did not had parts...
So I wait on delivery....

Thank you for the update. Their communication could be better, but it's good to know that they did get back to you eventually and offer a solution for you. They are obviously short-staffed and overwhelmed with their responsibilities, but it sure looks like they're trying their hardest to make things happen.

[Forum password reset broken?]

On 5/23/2022 at 3:15 PM, EskeRahn said:

PS A hint on this.
As the service used uses several severs, a simply retry of requesting a recovery is likely to be answered from another IP, that might not be blacklisted.

I tried that; several tries over a couple of days netted no response. 😞

[My Pro 1 just quit...]

On 5/2/2022 at 5:10 AM, theory said:

Well, got it apart today...

Found what appears to be a manufacturing defect... The sheet metal clip holding all the ribbon connectors on to the main board was installed in such a way it had partially cut the battery ribbon cable right at the connector...  Looks like I need a new battery as well...  I'm not sure if the battery is still providing power to the board or not...

Reseated the ribbon cable to the USB board at both ends... No change... Will not charge or boot.

Disconnected the USB board ribbon cable and tried to boot.  Did not boot...

While testing charging, I noticed that if I got the USB cable in just the right spot, sometimes the USB power meter I am using would indicate it drawing about 500mA for about  250mS...  Odd behavior...  But this behavior can only be seen with a standard USB A to C cable and a computer or general USB charger.  Using a USB C to C cable and a Power Delivery capable charger and the phone never communicates with the charger to start charging...

And I sent my request to buy a USB board to FXTec on 21APR2022...  I got the automated reply and nothing since...

Now I need a battery as well...

Start a new request?  Add to my existing request?  Wait until they answer my existing request?

--

 

 

I suspect that the reason it is completely unresponsive is the damage to the battery cable. Some devices will run without the battery connected, using power exclusively from the cord. This may not be one of them. It may need a bigger hit of power than the cord can supply to get things active initially. It may be possible with careful scraping and soldering to repair that ribbon cable at least enough to confirm that the device does operate when the battery is reconnected. It may leave the ribbon too thick to close the device though. The USB board is likely not the cause of the issue, and the draw you're seeing is probably it attempting to launch the charge program, then finding no battery and quitting. That would indicate that the mainboard is OK. I suspect that a USB board and a battery will make yours perfect again.

That said, the long lead times are par for the course. Thanks to CONTROL-19, everyone is short-staffed and FxTec was always a little short-staffed so they have it much worse. The majority of their focus has necessarily been on getting new devices out the door, since that's how they continue to exist, but history shows that they do eventually keep their promises to existing customers. Patience is a necessary virtue in all of life, and they just give opportunity to practice it. :)

[LineageOS 19.1 Official Release for Pro1]

5 hours ago, EskeRahn said:

Exactly. And for the first one rebooting the phone resting on the desktop, without touching the plug fixes it so it clearly is NOT related to the physical connection. It is some 'state' it enters, from which the only (known?) exit is a reboot.
And we have ONLY had reports on this from those on LineageOS & AICP, not Stock Android, so almost certainly a matter of the kernels handling the hardware differently. It MIGHT be that we would see the same if Stock was offered as 11 or 12. (If i recall correctly this was NOT reported for LineageOS 16 and 17, hence Android 10 most likely OK)

I'm using LOS 17.1 now, and used LOS 16 before, never used stock on this device (saw the Scroogle stuff and noped right into LOS flash before even completing the setup wizard lol) and I have never had this problem. My USB port is healthy, and I'm careful to keep it that way. It helps that the battery life is good enough that I never have to charge it anywhere other than on my desk.

[Pro¹ X – state of production and delivery]

4 hours ago, EskeRahn said:

Now that is good logic for ordering more than one ... 😁

There was discussion back in the early days of sending you a shipping container full of them. :)

[Comparing niche devices before I collect the whole set :O]

I looked on eBay, on a whim, to see if there were any cheap Cosmo Communicators out there.....I liked the idea of a pocket PC, and may come to the point where I can afford to have two nice devices. To my surprise, there were tons of them used, and everyone wanted $750-1100 for them. The manufacturer is selling them new for around $750, and is offering the Kana/QWERTY version for just over $500 right now. This tells me that this is a product that many people tried and regretted, especially since there is exactly ONE Pro1 I could find on eBay, asking nearly $1100. I see Cosmo's main drawback as the fact that you pretty much HAVE to put it on a table to use it. It is not really a phone; if you understand that going in, and actually want a UMPC with phone functionality, which is really what it is, it seems like a slick device. It doesn't look like it has official Lineage support, though I did see where it appears there are some unofficial ROMs for it. Mostly what tamps my interest right now is that my life is such that I use several phones, mostly on the road, and a desktop computer, and I don't really see where a UMPC would help with anything I do right now beyond being interesting. I can afford tools that help me, but I don't have that kind of money for "interesting" yet.

Then there's the Pro1X, which would be nice to have for sure, but I can't convince myself that it would be better for what I do than the Pro1 I already have. Assuming I don't destroy my Pro1 when I change the screen, I don't see why it couldn't serve its purpose for the foreseeable future, but then again, what if something happens to it? Having a Pro1X on tap would be very nice. I've only just gotten back to the Pro1 from the PRIV and I like it so much better. Unlike the Cosmo and friends, our beloved Klacks are NOT easy to get on a moment's notice. I almost think it would be smart to get a spare, and of course every unit sold helps to solidify the future of the company we all love so much.

I'm mostly just up past bedtime, but if anyone has any thoughts that might be interesting or helpful to my thought processes, please share them. I'll read them after sleeping. :)

[Pro¹ X – state of production and delivery]

I am toying with ordering one of these. Hmm. I still have my Pro1 and have no real objection other than I need to change my screen because the digitizer goes bananas sometimes. I like the improvements in the X, but doubt it will make any real improvement in my life. What to do.....

[Resurrection issues]

Strangely, the seemingly irrelevant APN works. When I went somewhere less off-grid, everything came to life. Now to get the screen fixed and all will be well. :)

[Game Gripper]

Two years later....BUMP! I guess this didn't happen, but if @Hyrum is still around, there are a lot of people who now own these things, and X variants heading out soon. Show of hands....who's still interested?

[Display units with large tap-insensitive margin]

6 hours ago, Kaali said:

I'm not 100% sure as i have rooted with magisk, but i recall doing that flash when i was running stock way back and i didn't need to root then. Also on lineage under developer options i have allow rooted debugging so it might be enough itself.

I guess I'll know soon enough lol. I think stock had a built-in path for the update that LOS may not. Hopefully I don't break the old one getting it out in case I have to reinstall it briefly. Heat should be my friend in that regard I think.

[Display units with large tap-insensitive margin]

7 hours ago, EskeRahn said:

I have no idea of the quality of the offerings, but I would suggest to start buying say two from each and test....

THAT is a genius idea. It also allows me to see how good their customer service may be if there's an issue, though I will have to make which came from which to do it properly.

EDIT: And I just did exactly that. I ordered 2 each from the 2 vendors offering the screen not as blems and will begin the discovery of the needed information. Thanks everyone for the supportiveness and great ideas!

[Display units with large tap-insensitive margin]

7 hours ago, Kaali said:

You don't need root to use the APK screen firmware flashing tool.

You sure about that? The instructions seem to call for some root ADB instructions, though being mostly in Chinese I can't be 100% sure. Perhaps it works anyway if that section is skipped, or the ADB part provides root access without actually rooting the device.....though I didn't think this was possible.

[Display units with large tap-insensitive margin]

1 hour ago, Rob. S. said:

I've bought two there in March 2021 and I currently have one of them in use. Except for the fact that I've managed to dameg it again recently (it's still usable so I try to keep using it until the Pro1X comes, while the USB socket is also becoming less and less reliable), and except for that little bit of excess black in the lower corners, there was nothing to complain about.

I fear it becomes clear from the shown images that the screens they sell all have differently sized, but generally large circular cuts in corners which stay black in operation... much larger than the small ones we've seen so far.

Yes, this seller is selling blems. Some might be OK with that, as long as they know what they're getting. I probably would for my own use, but since I'm considering resale I would prefer to at least not seek blems, knowing that some happen anyway :O

Thanks for all the great ideas and support, and most importantly for the flash file! That's super awesome. Is there any reason I shouldn't try it with my old display just to verify functionality before changing the screen? I don't see what it would hurt.

[Display units with large tap-insensitive margin]

So I found this for 30 shekels......

https://m.aliexpress.com/item/32956500815.html

I hope it's not fake for so few shekels. At that price I could have a bunch of spares, or order a bunch and sell pre-flashed units for less than the ones fxtec sells and still double my money. I feel like there would be a market for this considering this thread exists :) I could even let people trade in their unflashed ones for flashed ones at a reduced price. Am I an evil capitalist, a genius, or some of both? :O

After reading the reviews it sounds like there are enough quality issues that I'l have to eat some or fight them for exchanges, but it happens with hastily made low-cost products. Also some indicate it is identical, others only similar, but one person confirmed it works with Pro1 which is good. I see at least one user encountered the need to reflash but didn't know that was the issue. 

[Display units with large tap-insensitive margin]

16 hours ago, pebert said:

for me the touch worked perfectly after flashing OTA 2020-08-25. And the fastboot flashing worked fine as well after removing the "rem" from the line in the script that flashes the system image 🙄

 

So now I have upgraded all the 4 spare displays I have, hopefully I can stay on LOS for a while now. 

 

//Per

I am thinking of doing that too. The thought crossed my mind to get a bunch and sell them pre-flashed for the Pro1 and presumably also x because I assume it's the same display configured the same way, though that's not a guarantee. I am running 17.1 to avoid the bugs introduced in 18 and 19, and hence could root it and use the apk updater if I can get it. How hard is it to add root to an existing system? Is it necessary to do before first boot like gCraps?

Mine is behaving better at the moment; not correctly, but well enough to use until the spares arrive. Now if someone will point out a current listing for the screen at 40 shekels instead of 80 that would be fabulous. :) I'm going to try to find which Elephone model and do some research.

[Display units with large tap-insensitive margin]

3 hours ago, VaZso said:

I think sooner or later it should have, the state of LineageOS development at shipping is another question...

Considering that LOS is a promoted feature I think it's reasonable to expect that it will at least be usable at shipping. Being FOSS it will of course continue to be polished as time goes by, which is what makes it so great. I suspect they stopped updating the stock firmware because it was good enough for the few people who use it and they recognized that most of us are using LOS, and the value of LOS in providing ongoing updates and support without them having to do it themselves.

[Resurrection issues]

So I put the latest 17.1 on it, thanks to @claude0001 and @daniel.schaaaf which is super awesome, and now the APN list has an irrelevant entry and no warning, but it doesn't seem to actually save the new one I entered when I tap save. I'll play with it more. Any suggestions? Would it make a difference if I'm in an area with no signal? I can try in town tomorrow.

[PRO1, LineageOS 17.1 Official Builds: Discussion]

4 hours ago, EskeRahn said:

Also note that you can not upgrade to 19 OTA. But most likely the upgrade will work putting it on a SD-card.

And for me I had problems requiring a reset, that I belive was caused by switching from OpenGapps to MindTheGapps. (OpenGaps not available for 12 yet)

I switched from NormalGapps to SkipTheGapps a long time ago. My device performance has never been so good, and it's a small way I can strike back at the Evil Empire. :P The one and only Scroogle product I occasionally use is BooTube, and the app for that is Brave Browser. :)

[PRO1, LineageOS 17.1 Official Builds: Discussion]

1 minute ago, claude0001 said:

Lineage purges old builds as they do not want to promote the use of outdated (and thus unsecure) roms. It is however totally possible to build all supported branches (16.0, 17.1, 18.1, 19.1) yourself, in which case the latest security patches from the upstream Android project get included automatically. Such builds are then "unofficial" in that they are not signed with the keys of the Lineage project, but otherwise they are based on the same source code.

@daniel.schaaaf maintains an unofficial lineage-17.1 rom for the pro1. See this thread.

Myself, I maintain an unofficial lineage-16.0 as documented in this other thread, if you prefer to stay on 16.0.

Both roms are quite up-to-date with the latest Android security patches, though I must admit I haven't had time yet to build mine with the May 2022 AOSP patches. They also include a few improvements related to the keyboard driver we backported from 18.1.

THAT is awesome! Thank you so much!

[Resurrection issues]

Well, after suffering the random touches screen failure and having no pressing need for it, I set mine aside for awhile. However, I'm trying to use Patriot Mobile, a T-Mobile MVNO, and most of the T-Mobile towers in this area are on bands 12, 66, and 71, none of which the PRIV I was using support, so it's back on a well-supported AT&T MVNO for the moment, albeit data only because AT&T blocks VoLTE etc. on non AT&T branded devices. That's OK for the moment because all I do with it is VOIP and Web. The Pro1 supports band 12, which is available on all T-mo towers in this area, so I grabbed it again.

I'm going to have to replace the screen at some point. Sometimes it's usable, sometimes not. I'm going to see if careful thorough cleaning in isopropyl alcohol will stop the madness first. I think the info for that is all here already.

More urgently though, I need to enter an APN for the Web to work, and it says it can't for the current user. I am using LOS 16, probably an earlier WIP version at that, so I know I should upgrade it and plan to do so, but I do wonder if it is a bug I'm likely to encounter again. I'm still hoping for LOS 17.1 to avoid the charging bug.

Anyone care to tell me anything to make my life easier? 🙂

[PRO1, LineageOS 17.1 Official Builds: Discussion]

On 4/15/2021 at 5:24 PM, claude0001 said:

I am pretty sure many Lineage ports have AGPS disabled. As I wrote above, that default setting makes sense, considering that some users might choose LineageOS specifically for privacy reasons.

Of course, the option to opt-in to AGPS from the GUI without requiring root access to the system config would be great. However, I suspect that, if it was all that easy to implement, that feature would be available already.

No, never underestimate the ability of the FOSS community to overlook important and easy feature implementations. Nextcloud STILL hasn't added the ability to duplicate an event to their built-in calendar client after many years of people clamoring for it, in spite of the fact that it would be relatively easy to do. Ah well. We get what we get when we're getting it for free. :)

[PRO1, LineageOS 17.1 Official Builds: Discussion]

On 4/15/2021 at 11:59 AM, EskeRahn said:

As they sadly consider the previous version as unsupported as soon as the new is released, we should not expect anything regarding 17.1 😥

That is tragic. Considering the bugs with 18 and 19 I'd like to put 17.1 on mine, which is still on 16 initial Pro1 release and having a weird issue, but of course LOS has purged those builds because they do now. Anyone have a link to the last 17.1 for Pro1 that still works? If someone has it I can expose a folder on my server temporarily so you can share it with me.

[LineageOS 19.1 Official Release for Pro1]

7 hours ago, EskeRahn said:

The tap sensitive margins have to be programmed correctly.
If you ask WHY the screens comes with some other default - I have no idea....

How annoying. Is the necessary programming function something that could be put in an APK to avoid having to completely rework your software for a simple screen change? Of course I'm hijacking this thread with an OT now.....

[Forum password reset broken?]

I have always believed my mail server was about as unfussy and simple as they come, but of course it's possible I'm incorrect. I don't use spam filtering, so all the Nigerian lotteries, timeshares, handbags and enlargements go straight to my inbox. It can be entertaining at times. :) Gmail is notoriously fussy, as are Yahoo! and Hotmail (now called Outlook.com) and that's one reason (albeit a minor one) why I don't use any of them. They tend to spam flag my business email until a user whitelists me, likely because I'm sharing the hosting with less conscientious users.

None of that explains why I never got the recovery emails though. I'm glad it still works for some, but of course, intermittent issues are the hardest to troubleshoot.