claude0001
-
Content Count
753 -
Joined
-
Last visited
-
Days Won
108
Posts posted by claude0001
-
-
I've been using a Raspberry Pi3 for all my Pro1(-X) flashing for years. Its rustic USB turned out to be 100% reliable for adb and fastboot. Plus installing the latter is just an "apt install" away in Raspberry Pi OS. This is in contrast to my (Debian) Linux-PCs that repeatedly had problems with fastboot connections to my Pro1s.
-
1
-
-
The latest build of LineageOS16.0 (for SD835 Pro1), dated 20240924, is available at
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
(Kind of) full list of features:
- Backported security patches up to the September 2024 ASB.
- Improved keyboard behaviour (backported from later LOS releases) as documented in the local patch tarball.
- Several more improvements with respect to the upstream LOS 16 tree (GPS fix, touchscreen margin control, ...) as documented in that same patch tarball.
- Updated graphics driver stack (from LOS21).
- Update of the bundled System WebView and browser to Chromium 128.0.6613.88 (from LOS21).
Have a lot of fun!
-
4
-
We can't help if you don't disclose what is not working.
The how-to on the Lineage wiki is a s complete as it gets. What is the first step that fails in your case?
If you are using a Windows PC for flashing, it is likely that you need to install the Google OEM driver to get fastboot to work ...
-
2
-
-
7 hours ago, Burkhard said:
We went to a rock concert on Sunday and it didn't work at all. Not at all. I was really angry.
Forget it. The Pro1-X camera cannot handle such light conditions. The Pro1's is better, but still takes a lot of patience and manual intervention (and a good camera app) with night shooting.
The price tag comes from the mech keyboard. Full stop. Other than that they're mid- (Pro1) to low-class (Pro1-X) phones.
7 hours ago, Burkhard said:I've marked where the spot is on the screen.
The position of the spot on you screen is different from all I've seen before, though. Normally they are all in the corners of the display, and hardly visible in normal operation. So forget what I said before: Might be worthwhile contacting F(x)tec for a replacement after all.
-
3
-
-
2 hours ago, Burkhard said:
The camera is total crap. With the original app it rarely or never focuses and the Manuel Camera DSLR Pro app often freezes
Yep. One of the major reasons I went back to the original (SD885) Pro1. Although the Pro1 camera is also quite mediocre, it at least does not have these hangs of the Pro1-X's which make spontaneous picture shooting impossible.
Note that the Pro1-X camera at least did not hang for me when using the camera app built into LineageOS. This prevents access to advanced camera controls though, and anyway the optical quality remains horrible of course. Especially the vignetting is catastrophic on my prawnX.
As to your screen problem, I think everything has been said already. This has really been my least concern with F(x)tec phones over the last 4 years. If this turns you down a lot, better do not try to use them in your daily life, much more disappointment is lurking ... 😉
-
2 hours ago, phukfxtec said:
already tried installer. does not work
On discord they helped some guy install UBtouch manually after the installer didn't work for him either, basically following this how-to:
https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x
3 hours ago, phukfxtec said:i dont see artifacts.
To get all the partitions required for flashing, you need a "devel-flashable" zip. Unfortunately, the last successful job of that kind at UBports was 9 months ago, and the resulting artifacts.zip is no longer available for download:
https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x/-/jobs
So self-building the system partition image from an OTA, as hinted in the how-to above, might be the only way. For that the artifact.zip from the latest "build" job *should* be sufficient:
Disclaimer: I'm not using UBTouch myself. Ask on discord if you run into trouble. Regarding non-Android OSs, it's more active than this place.
-
1
-
1
-
-
4 hours ago, FlyingAntero said:
I was thinking that they are the same. Is the selfie camera different?
I once tried to swap-in the screen assembly of a Pro1-X into a Pro1. They fit mechanically and connector-wise. The result was that the Pro1 was able to boot into a (working) Lineage recovery, but not into the full OS. I thus assumed the selfie camera was different.
Of course, the top half of the Pro1(X) includes more than the (touch)screen and camera. There is the indicator LED, the ambient-light photodiode, a speaker and (I guess) a mic for handheld audio. But somehow I had assumed those were analogue devices that could not cause a crash upon boot.
-
1
-
4
-
-
Can't find it back either. But I just checked: If you *carefully* lift the edge of a cap with a pair of tweezers, you can see the transparent mat below. So the keycaps indeed seem to be individual parts.
Not something that was meant to be user-customizable, but it does seem possible ...
-
1
-
2
-
-
8 hours ago, EskeRahn said:
No we can't, it is a mat, sorry,
I think someone here reported that one of the keycaps came off, and they glued it back in place?
-
1
-
-
Several posts on the IGG comments thread suggest QWERTY variants are out now. Remaining orders seem to be asked to choose between QWERTZ and scandinavian keyboard layout ... 😕
Edit: Has hit the discord channel too, now.
-
1
-
-
22 hours ago, Aeong said:
Sure, the keyboard is pretty cool and works fine. But what can I do with it?
I'm a programmer, but I'm not one to code or use a terminal outside of the house.
I'm not going to do any document work on this phone.Oh, this keyboard would be nice for emulator games.
But I already have a much more capable $300 Android gaming console.I agree with your criticism of the Pro1-X's remaining hardware and delivery process.
But in these lines you essentially state that you backed a keyboard phone even though you have absolutely no use for a keyboard phone. Of course you have every right to do this. But then do not lateron blame F(x)tec when they indeed ship you a keyboard phone as ordered ...
-
4
-
-
19 minutes ago, brunoais said:
Mine has the marks too. This is an issue with the display manufacturer which seem to have a 70+% failure rate at the screen edges.
As previously stated, I can only agree. I have 2 x Pro1 and 1 x Pro1-X and all displays have these black moons in at least some of their corners. The good news is that they haven't worsened over time, which is 4+ years for my initial Pro1.
-
3
-
-
12 hours ago, ralpholzer said:
Only working thing:
The Terminal
Not using SFOS myself since many years. But others indeed have reported much better results. As you had similarly devastating experience with Droidian, also (kind of) positively tested by others, I wonder if something is wrong with your device. Did it work correctly with stock Android 11?
-
2
-
-
On 8/26/2024 at 4:03 AM, eda said:
Maybe is a time to go to psychologist, because I like all other aspects of the pro1x so far.
Maybe it is. But not because you dislike the screen. Rather because you do like the rest of the phone!
Just joking of course ... 😉
-
4
-
-
VoIP was enabled by default on my Pro1-X, and WCDMA (part of 3G) is being, or has been, phased-out in many regions ...
-
1 hour ago, FlyingAntero said:
Did you really receive black Pro1-X and not original Pro1 (snapdragon 835 chipset)? If it really is Pro1-X then it is weird that they produced also black back covers for Pro1-X. In addition to the color, the back cover of Pro1-X is little bit different than back cover of Pro1.
My Pro1-X from Expansis is also black. I think they made a lot of those.
-
2
-
-
2 minutes ago, eda said:
Just looked at the angry comments on indie, I'm not alone with this problem.
Happy to meet someone who is capable of joking on the subject. 🙂
You're not alone with that problem. As far as I know, most Pro1's and Pro1-X's have screens that shown black spots in their corners. Most users simply accepted them until now. I do not know of any standards that an AMOLED screen must legally fulfil in this respect.
-
Just now, eda said:
I've open a ticket with fxtec support (are they still in a business?) asking for refund or replace.
You must be new here ...
Sorry for the pun, but you'll soon learn that f(x)tec is no ordinary business ... 😄
-
4
-
-
I wouldn't worry about those.
My Pro1's (got two of them) and my Pro1-X have had these black spots in the corners of the screen since day one. They haven't worsened over time (we're talking years for my initial Pro1)
-
2
-
1
-
-
53 minutes ago, tonism said:
What happened to my phone and my money?
They have previously stated that they no longer have spare parts for all components of the OG (SD835) Pro1. So, depending on what's broken, they might simply not be able to repair it. I'm just guessing, though.
For any other company that wouldn't be a big deal - they'd just send you a completely new phone. In F(x)tec's case you could ask them for a new Pro1-X.
However, considering the rate at which they manage to send those out, also that could take a while ... In two years, they managed to get out an estimated couple hundred Pro1-X's into the wild. I.e., on average, they ship ~1 phone per day or so ...
-
I've just uploaded my latest build of LineageOS16.0 (for SD835 Pro1), dated 20240820, to
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
Changes since last month:
- Includes backported security patches up to the August 2024 Android Security Bulletins.
- Updates the bundled system WebView to Chromium 127.0.6533.103 (as shipped with official LOS 20 and 21).
Have a lot of fun!
-
2
-
1
-
4 hours ago, EskeRahn said:
I'm sad to say that I fear you are a bit optimistic with the pricing, despite the high costs you had. 😢
I unfortunately have to agree. The aftermarket is flooded with Pro1X's that Expansys sold for 300 $ a piece (that's how I got mine). No one is going to give you 800 bucks for that thing ...
-
I had this once (after dropping the phone) and solved it by re-seating the screen connectors in the top unit of the phone.
Disassembling the top unit is quite easy. I've done it many times. Take a good look at the instructional videos before though.
-
4
-
-
I cannot reproduce this with my Pro1-X. Not using Termux, though.
I'm running Debian 11 in a (rooted) chroot of LOS 20.0 and use ConnectBot as my terminal emulator. Your script works fine (with some trivial changes to match my environment).
As, also for you, the keyboard behaves normally in other apps, it seems to me that you are somehow triggering a bug in the terminal emulation of Termux.
-
1
-
Finally looking at my Pro1x, getting nowhere
in General Discussion
Posted
https://archlinux.org/packages/extra/x86_64/protobuf/
?