claude0001
-
Content Count
799 -
Joined
-
Last visited
-
Days Won
127
Posts posted by claude0001
-
-
13 hours ago, LikeThis said:
Is this still a problem for people. I have two verizon phones that I would like to consolidate to this one phone using dual sims in this. But if Verizon won't work and I can't text this might not be an option for me. Just trying to understand if these are ready for prime time usage in the US.
This is a user forum, and the problem seems to be between F(x)tec and US network carriers. While it would indeed be good to read an official statement by F(x)tec on this issue, this is usually not the place they publish such things.
Of the users around here, @Hook seems to be most experienced with the Verizon compatibility problem, and their opinion (which you probably have read already) seems clear to me: No, the (original) Pro1 cannot be expected to work with that carrier. For the (future) Pro1X, we do not know yet.
-
1
-
-
1 hour ago, EskeRahn said:
As @Totalnoob is allowed to do calls [...]
As I say, I have no personal experience here. But scrolling up that other thread I linked, one gets the impression that texting is indeed most sensitively affected by whatever changes in authentication that provider (Verizon) have rolled-out over the last year or so.
The US marked seems to be quite different from the European one when it comes to vendor lock-in/lock-out. See also this thread for more bad news on the topic. I feel like I can give no better advice than to seek help from other US forum users who have gone through the same troubles.
Edit: In fact, if it is true that US customers cannot expect their Pro1/X to work on their network anymore without Fxtec finding agreement with US carriers, they (Fxtec) should make a statement about that. I thought I had read somewhere that they were in discussion with some US provider, but cannot find that thread anymore.
-
1
-
-
8 hours ago, Totalnoob said:
Some details: I live in the USA, I have a Verizon SIM card that is frankly ancient
I am not from the US, so I can only forward what US users have reported here:
https://community.fxtec.com/topic/2133-fxtec-on-verizon/?do=findComment&comment=59026
It seems like some US carriers have started to no longer accept the Pro1 in their networks some time ago. Maybe try to PN the people in the above linked thread for possible solutions.
-
2
-
-
On 11/1/2021 at 9:08 AM, Wheeljack said:
Did the OTA just now and the new keyboard driver is a godsend.
This. I backported that patch to my LOS 16.0 yesterday and have yet to experience an unwanted double keystroke. Good work, people!
-
2
-
-
23 hours ago, VaZso said:
I am completely gave up using stock OS, going for LineageOS is a better option instead.
Also, it has Android 11 support...I fully agree personally, though I understand the disappointment of those who bought a (quite expensive) original Pro1 expecting regular minor and major updates of the operating system it shipped with, which IS the official Android OS, not some open-source fork of it.
Obviously, they have to focus all in-house effort on the Pro1-X now. However, I hope that, now that they are actively participating in alternative-OS development, also the original Pro1 will keep getting some love in the long run. E.g., I still hope for a useable UbuntuTouch port for the 835-Pro1.
-
4
-
-
On 10/16/2021 at 11:49 AM, dreamflasher said:
I have only used Lineage OS so far, and I tried a few times to upgrade the ROM with the internal upgrader, and afterwards the phone didn't boot anymore (I have Magisk root, and disk encrypted, that seems to be a problematic combination).
When I still had an official LineageOS, I was applying every weekly OTA and "su" would be preserved reliably. I never disabled encryption. Those were the days of AddonSU though, which was officially supported by LOS. Always remember that Magisk is a third-party tool before blaming the OS for it to stop working for some reason.
Today I run my own builds which I install via sideload. This requires "su" to be reinstalled at every update ... one gets used to it. At this point, I would not prefer one ROM over another just for its ability to maintain root across updates. Let's face it: us rooted users are considered weirdos in the Android world. Once we accept that, life becomes easier for everyone ... 😉
-
2
-
1
-
-
On 6/22/2021 at 8:15 PM, claude0001 said:
For the case anyone else still has interest in LineageOS 16.0, I've made them available here:
http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
Uploaded my LOS 16.0 build dated 20211017. AOSP patchlevel of October 2021. Contains a version of @Slion's experimental "Fn-Tab-as-Alt-Tab" mod as discussed above.
-
5
-
-
1 hour ago, Hook said:
Honestly, I've never seen a case that doesn't end up capturing dust on whatever surface it covers.
1 hour ago, EskeRahn said:I agree. The back of my daily driver is most likely just as worn as if I had not used a case.
Guys ... you do need to clean your gear from time to time! 😄
Ever heard of this (famously quoted in Kubrick's "Full Metal Jacket")? Different device, same approach. 😉
-
2
-
-
4 hours ago, Slion said:
Still I could not prevent myself from making plans in my head on how to modify that case so that the strap is attached to the back pane
This. That's also the most annoying issue I have with my flap case, which otherwise serves me well (see earlier in this thread). The strap is somehow always in the way, especially when taking pictures in landscape orientation.
When opening the flap by 360° it is possible to get the strap magnet to attach itself to the flap "in reverse", which gets both out of the way. But you obviously can't take pictures in that configuration.
What's more: in my case the magnet of the strap is exposed (i.e. not embedded in the leather, like in yours). Believe it or not, it has left scratches on the screen by now (Magneto: "Take that, Gorilla Glass 3 (tm)!"). Argh.
-
4 hours ago, PokeParadox said:
I've not got around to trying again, do you have a more recent set of steps I could follow? I don't seem to have much luck getting this set up.
I am ready to help, but I would first need to know what you are failing at ...
Please have a look at this post, and try to understand it, following the links I provided.
The first step is to prepare an SD-card with a partition containing the GNU/Linux distribution. This is best done from an existing (x86) Linux-PC using qemu as described in the first link of my post. As most modern Linux distros are based on systemd (which cannot run in an Android chroot), I suggest Devuan which uses traditional System-V init. It is possible to change the init system also in vanilla Debian, but that adds one more layer of complexity to the project you may want to avoid. 😉
Upon startup of LineageOS, that "Linux" partition of the SD-card is mounted via the Chroot script attached to said post of mine. Then, the script starts a few services within the Chroot environment, the most important ones being SSH and XRDP. On LineageOS, running the script can be automated by placing it into /data/local/userinit.d and installing the Run Userinit App from F-Droid. Note that the App -- as the Chroot script itself -- requires a rooted LineageOS.
With the SSH and XRDP servers running in the background, they can then be used for accessing the GNU/Linux environment, either remotely or by using suitable Android client-apps on the Pro1 itself.
Of course, you cannot just copy my Chroot script blindly. You should install your own system step-by-step, adjusting the script as required. Obviously, it is also good to first test the individual commands from an interactive (root) shell of LineageOS before trying to automate things using the script.
If we continue this discussion, it should probably be moved to another/a new thread, as this is explicitly about not using Termux now ...
-
3
-
-
12 hours ago, EskeRahn said:
If I don not remember wrong, the issue there is the margins, not that it does not react at all
You are right. But @Dyna Smart do not provide much details in their report: Replaced themselves or by FxTec? Source of the replacement screen? Installed OS?
My experience is that, in lack of more information, you never know what people understand by "not working at all", especially when they are at a certain level of frustration.
Hell: I myself have sometimes said my Pro1's camera was "not f**ing working at all!", although this is objectively far from true ... 😉
-
2
-
-
8 hours ago, DynaSmart said:
After replacing the cracked screen, the displa's touch function is not working at all (even after repeated re-booting).
Is there a solution to this bug?
In case you replaced yourself: most spare parts now seem to require a firmware update for the touch function to work correctly.
See this thread and the possible solutions discussed therein.
-
1
-
-
4 hours ago, raymo said:
I play a little whith termux, scripting inside Arch in order to automatize display and launching Xfce.
However I don't find solution launching XSDL apk from bash script yet,Termux is a nice project and has some interesting features. But as an in-app solution, I guess it will always be somewhat limited. That is why I decided to install everything from scratch by myself. Note that, in the beginning, I also knew nothing about chrooting Linux distros on phones: the Pro1 is my first Android device. Do not give up!
The reward for all the work and learning is that I have now a GNU/Linux distro running really in parallel to LineageOS, which allows me to use the Pro1 like an actual PC, while neither disturbing the Android environment nor depending on it in any way (except for the kernel, of course). I can SSH into my Pro1 for CLI access or file transfer. I can remote-desktop into it, which will spawn a fresh KDE desktop or reconnect to an existing session. I can start arbitrary GNU/Linux background processes via cron. All without relying on any supporting Android apps -- though it is of course possible and useful (thanks to the keyboard!) to have Android SSH or RDP clients ready for accessing the GNU/Linux environment on-device.
Yes, it was some work to get there. But it seemed like this was the only way the Pro1 could at last replace my beloved N900 ... 😉
-
3
-
-
Nice job! Always good to see I am not the only one using the Pro1 as an actual computer ... 😎
4 hours ago, raymo said:It also works with VNC but without sound
By using XRDP as a wrapper around VNC, you can forward sound from the VNC session to an RDP client (I recommend MS Remote Desktop 8 as it seems to work best with the Pro1's keyboard). This way you do not need a separate XServer on Android, and the Linux session can run in the background when disconnected. I gave an overview about such a setup in another thread. I do not use termux, but I guess it cannot install XRDP and the required PulseAudio drivers for you. You'll have to do that yourself from within your Arch system.
As I explained in this post, it is even possible to get rid of VNC altogether by using the (better performing) native X.org-backend of XRDP. However, that is even more complicated as it requires traditional shared-memory access from the Linux system.
Happy hacking.
-
1
-
1
-
-
1 hour ago, EskeRahn said:
Not saying that their timeframe will hold, but have a look at this
Oh, I did read that. As I did read all the other announcements since 2019.
I guess, for those who have followed FxTec's path for so long, there are only to possible outcomes: you become either a pessimist or a believer. 😉
-
2
-
-
1 hour ago, brunoais said:
In other words: Doable but I wouldn't put my bets on it
With all due respect: I think no one here ever got their phone within 3 months.
Even if mass production restarts in November, FxTec will be busy for months serving all the Pro1-X backers (and probably quite a few remaining Pro1 orders).
If you haven't pre-ordered a Pro1-X already, I do not think there is any hope to get it in the first half of 2022.
-
8 hours ago, jonyify said:
To eleminate clicking/popping sound: switch off NFC.
Confirmed on LOS 16.0: With NFC switched-off, no clicking when recording from the 3.5-mm-jack. Thanks for sharing!
-
2
-
-
1 hour ago, daniel.schaaaf said:
Will changes to 18.1 automatically integrate into the 17.1 code?
No, don't think so. Also the device-specific code has distinct branches for 16.0, 17.1, and 18.1.
That patch of @tdm is proposed against 18.1. So if it is accepted, it will be only in there.
Currently the driver in 18.1 is still (almost?) the same as in 16.0 and 17.1 so backporting the patch to your local 17.1 tree should be trivial. That may change in the future, as there are several proposals for improving the keyboard driver in 18.1.
I am loosely following that development, but almost certainly will not backport everything to 16.0, as I am in fact quite happy with the current low-level behaviour of my keyboard, even in complex use-cases (RDP) ...
-
1
-
1
-
-
5 hours ago, Apextech said:
If I had bought $700 USD in Bitcoin instead of this phone (which I still do not have) in Feb 2020, I would have over $2800 right now.
Try to be optimistic. Money is not everything. I paid my Pro1 (without the "X") also more than a year before I finally got it. Now that I have a real keyboard phone, I congratulate myself for the decision to preorder every day.
-
5
-
-
On 6/22/2021 at 8:15 PM, claude0001 said:
For the case anyone else still has interest in LineageOS 16.0, I've made them available here:
http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
Build 20210922 is available. It includes the September 5 AOSP security fixes.
As of this release, the build includes a backported patch, originally made by @Slion for LOS 18.1, which allows one to use "Fn-Tab" and "Alt-Tab" equivalently for switching Apps (see this thread). I find that feature really useful when holding the Pro1 by the keyboard.
I have used that modified keyboard driver for weeks without issues. Still, be warned that this code has not been merged into any official LOS branch yet, and should thus be considered experimental.
Edit:
I think I should clarify: the driver included here corresponds to @Slion's "patchset 7" in 315155, i.e. the version before "modifier passthrough" was introduced. I follow the discussions around improving the keyboard driver in LOS 18.1, but will probably backport to 16.0 only what seems useful to me personally ...
-
1
-
2
-
-
1 hour ago, Rob. S. said:
Angelo is the newest addition to team F(x)tec, and will work as our in-house engineer for Linux and mainline support, as well as adaptations and functionality of alternative OS’s for your devices.
I like those news in particular ... 😺
-
6
-
-
15 hours ago, tliebeck said:
I would strongly recommend the following:
- Place the /? key in the traditional location (replacing current \| key. (this puts in the traditional location on a PC/Mac keyboard)
- Replace the "Del" key with the \| key (this puts in the traditional location on a PC/Mac keyboard)
- Eliminate the right side "Up-Right" function key and replace it with "Del"
- Ensure that all yellow symbols can be rendered simply using the SHIFT key (I don't have my Pro1 yet, don't know if this is currently the case or not).
While I agree with most of your ideas, I think that ship has sailed. According to the last update from Fxtec, they should be in the protoyping phase by now. Even small changes to the hardware would likely introduce large delays at this point. As @VaZso pointed out, that's especially true for the Fn key which is wired differently than "normal" keys. So it is not only a matter of changing the printing on the caps.
That said, I would not worry too much. My experience is that typing on the phone and on the PC "feels" so different that it does not help to have identical layouts for the symbols (nor does it hurt to have some differences there).
I have a QWERTZ Pro1. And although that mimics the standard QWERTZ layout quite closely (I think as closely as possible without triple-labelling keys) this similarity to my PC keyboard did not help me much in learning to type efficiently. Most of the time, you thumb-type on the phone, so muscle-memory from the PC simply cannot help you find the right keys. And, even when using the phone on a desk, so that one can (in theory) use multliple fingers for typing, the gestures I am used to from the PC most often do not work, as the keys are simply too close together with respect to the natural span of my hands.
-
1
-
1
-
16 hours ago, Sean McCreary said:
I have verified that each key generates the glyph matching the printed keycap for QWERTZ variant Pro1 devices, as long as in 'Settings -> System -> Languages & Input -> Physical keyboard' *both* 'Advanced settings -> Physical layout' is set to QWERTZ *and* 'Builtin Keyboard -> Choose keyboard layout' is set to German. I will try to find a way to make it easier for users to set the correct configuration to make this less confusing.
Because this seems to be a configuration issue rather than a bug in the default keymap in the keyboard driver, I have abandoned CR#315195.
Exactly.
Out of interest, I had applied the proposed patch to my LOS 16 on my QWERTZ Pro1: The respective key immediately stopped working correctly. With @tdm's default keymap, things have always worked - given the correct configuration you describe.
That one has to configure things in two places is of course a little cumbersome, and many of us QWERTZies stumbled on that in the beginning. Streamlining the UI here would be nice, but also not strictly necessary, as for most users configuring this is a one-time action.
-
1
-
-
1 hour ago, Slion said:
What's your experience with call quality on LOS? So far I only had one phone call and the volume was totally ok, none of the extra loudness issues from stock. However as I tried to adjust the volume it did not seem to adjust by much I could hardly hear any difference. Not that it need adjusting though, it was just fine, just wanted to try it out.
Since I have never had stock, I cannot compare LOS to it regarding call quality. But I somehow remember @tdm saying the telephony bits were taken 1:1 from stock, so maybe there really should not be much of a difference ... All I can say is I'm happy with the few phone calls I make. Yes, sometimes I adjust the volume during a call, but no idea if the Pro1 is to "blame" in those cases, or whether it is my partner's phone.
That said, I am probably the wrong person to ask, really. I have accepted the fact that reliability and audio quality in telephony reached its peak around the time of the last mechanical-dial phones. Then we improved things further ... 😉
-
1
-
3
-
PRO1, LineageOS 16.0 Official Builds: Discussion
in General Discussion
Posted
My LOS 16.0 build 20211111 is available for download. It contains the "5th November" AOSP security fixes.
Meanwhile, my version has diverged somewhat from the official code. As of today, my tree contains the following local patches:
Have fun.