claude0001
-
Content Count
645 -
Joined
-
Last visited
-
Days Won
81
Posts posted by claude0001
-
-
18 minutes ago, dorkydicken said:
but it uses Arch Linux
According to their website, you can use "apt, dnf, pacman and yay" interchangeably. apt will use the Ubuntu repos, pacman those from Arch, and dnf will get its packages from Fedora.
P.S.: As a hardcore Debian user, who even hesitates to mix "stable" and "testing" packages, I am horrified by the idea to blend together several distributions that are completely unrelated. But that's a different question ... 😉
-
3 hours ago, dorkydicken said:
Okay anyone have a tute on how to flash in Linux?
I'm using BlendOSI do not know BlendOS, but it appears it can use the Ubuntu package repositories.
In that case a simple
sudo apt install adb fastbootshould provide you with everything you need to follow e.g. the flashing instructions from the LineageOS wiki.
-
3 hours ago, EskeRahn said:
As the Pro1X seem to have a bug, where you can not have it charging while off
The Pro1-X can can do off-mode-charging. I have it enabled and working on one of the Lineage beta releases.
That being said -- as @Sean McCreary clarified in another thread -- Android devices are not truly "off" during "off-mode-charging". The Linux kernel and battery management software need to be up and running, just like if the device was switched "on". The only difference is that the Android GUI is not loaded.
Now the problem with the Pro1-X is that it's got a bug which allows the battery to discharge completely. If that happens, the device is bricked, irrespective of off-mode-charging being enabled or not. The point is that switching the power source over to the USB PSU is software-controlled. Thus, even with off-mode-charging enabled, the phone needs enough residual charge to at least boot its OS from the battery. Only then can the re-charging actually start.
Normally (as with the Pro1), battery protection should prevent a total discharge from happening. I.e. the battery should get disconnected from any power sinks before the stored energy reaches a so low level that the OS could no longer boot. With the Pro1-X, that part somehow does not seem work, thus letting its battery run low is very dangerous.
-
2 hours ago, jakfish said:
Aside from my angst, the Pro1x can truly be a stand-alone HPC. Before, I traveled with a GPD MPC, an admirable device, but the Pro1x is even more portable, especially with its--albeit buggy--mobile data.
@jakfish, @Hook, @brunoais: I respect (and sometimes admire) your point of view.
However, please let's agree on that the Pro1-X was not marketed as an HPPC, but as a phone that could (maybe) double as an HPPC. Let's also not forget that it was meant to be delivered with LineageOS (OK, we finally have that now thanks to community support) and UbuntuTouch (nowhere close). Let's further not forget that it was supposed to come with HDMI-Out to enhance that HPPC aspect (especially with UBTouch). I do not see how my Pro1-X is fulfilling any of those design goals. That's why I, sadly, shelved it before it could see any significant action. As much as I liked my Pro1, I do not think I'll be changing my mind on the Pro1-X.
-
1
-
-
Another update of LineageOS 16.0 (for SD835-Pro1 only) is available at
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1.
The ROM dated 20230516 gives you backported security patches up to the 5 May 2023 ASB. No other changes since last month. As usual you can refer to the tarball of local mods to learn all about differences with respect to the official lineage-16.0 tree.
Have fun!
-
1
-
2
-
-
8 hours ago, VaZso said:
OS developments
We hope you are having an enhanced experience with your Pro1-X and enjoying LineageOS 20, with improved performance, new features, and bug fixes.
It's really hard to interpret those lines differently than that further development of stock Android (on which all alternative OS's rely on in the end!) is essentially off the table. Bad news for anyone who hoped for updated driver modules or firmwares that would fix network reliability issues.
This is the second month in a row with no news whatsoever on in-house software development or bug-fixing (after we've been in "the final sprint" for an OTA since November or so). Do not get me wrong: Yes, it's great that we have LOS 20.0. But that's a community effort. In my understanding, F(x)tec has as much to do with LOS 20 for the Pro1-X than Google has with the respective ports for the Pixels ... Correct me if I am wrong.
-
1
-
-
7 hours ago, SchattengestaIt said:
But from a developer standpoint the fix should be in every version of LOS. I think I jumped from LOS 16 to LOS 18 directly
... well that's the point: I want to stay on my custom LOS 16.0 ROM, but have backported quite a few fixes from later LOS releases. That's why I was asking about the specific patch to look at ... 🙂
-
On 5/6/2023 at 7:56 AM, SchattengestaIt said:
the screen brightness issue was solved with LOS 18
I'm about to update my LOS builds with the May 2023 ASB fixes. So I repeat my question: Does anyone know what patch in LOS 17 or 18 apparently fixed low-brightness screen colours on the Pro1? Would love to include that one ...
-
15 hours ago, SchattengestaIt said:
Believe it or not, the screen brightness issue was solved with LOS 18. Lowest brightness doesn't turn your phone greenish anymore.
As you have guessed, I find this hard to believe, indeed. @tdm once argued that the green tint problem was likely related to lack of stringent screen calibration, something supposed to be near-unaffordable for small-series manufacturers, so that it is essentially a matter of luck, whether you get a green-tint screen or now ...
Are you able to point out the LineageOS patch that you think did this magic for you? If it exists, I would love to backport that fix to my LOS 16.0.
However, I'm not able to find anything that seems related, neither in the pro1-specific LOS 17.1, nor the LOS 18.1 merges.
-
1
-
-
In LOS 16.0, there is a setting "System > Gestures > Jump to Camera". Enabling that causes the camera app to launch when the power button is pressed twice.
Not sure that feature exists in later LOS versions, but if yes, you might want to make sure it is disabled. Otherwise accidential double-presses of the power button might indeed cause the behaviour you observe.
-
1 hour ago, EskeRahn said:
It is a known problem and the known fix is tedious, we got a thread on it, somewhere, will move if/when i find it.
The thread you are looking for is here:
https://community.fxtec.com/topic/3204-display-units-with-large-tap-insensitive-margin/page/9/
However, I do not think we had a case of Pro1-X with this problem yet.
For the Pro1, the usual fix was to flash back to the initial stock (Android 9) OS. Not sure it works similarly for the Pro1-X ...
-
1
-
1
-
-
4 hours ago, AndytheNoob said:
Are there any disadvantages to running Lineage 20.0 over Android 9?
I'm a big fan of LineageOS. But for completeness, let's mention that there seem to be some apps that refuse to install and/or run on LineageOS, because they identify the system as "unsafe" (unlocked bootloader and all that ...).
Yes, it is nonsensical to consider stock Android 9 -- with by now hundreds of unpatched security holes -- as "safe", but, apparently, that's what they do ...
-
1
-
-
1 hour ago, Slion said:
Lately I was contemplating the FairPhone 4 but I eventually ruled it out. I think the LCD screen put me off.
The FP3 also has an LCD. But especially at low brightness it looks way better than my Pro1's AMOLED. Also: No f**ing rounded edges! 😄
It's not all in spec sheets.
-
1
-
-
Dear @Slion,
I think I've got an idea how you are feeling.
While I haven't retired my Pro1 yet, I also use the HW keyboard less and less. Partly, this is because some keys are becoming more and more unreliable, which makes typing a frustrating experience. Mostly, however, my use cases for the keyboard are much fewer than I had initially expected. I came to the Pro1 from an N900, which had an OS and an app ecosystem that was designed around landscape use of the phone. This is simply not true with Android. While almost all apps support landscape in some way, few make intelligent use of it, and many are just cumbersome to use in non-portrait-orientation.
The keyboard has its place in operating my GNU/Linux chroot, where it allows the Pro1 to work like a miniature laptop. But admittedly, I also use this possibility rarely. Most of the time, I just access the Debian system via SSH, which would work equally well on any random slab.
Then there are the many small non-keyboard-related inconveniences with the Pro1: green screen tint, poor audio quality, low-quality camera, mediocre battery lifetime, etc.. Not too long ago, my wife got herself a refurbished FairPhone 3+. In an impressive way, that device demonstrates that also small-series manufacturers can make quality (and well-supported) phones, and painfully highlights all the compromises I am accepting with the Pro1.
In came my Pro1-X. I had truly hoped it would improve on some of the bugs of the Pro1, and that I could configure it into a worthy successor. In some aspects it actually is better: The keyboard response is impeccable, the screen colours are more accurate. But, unfortunately, it is plain unusable as a mobile phone because of its connectivity issues. That's a no-go for me, also for professional reasons. I've essentially given up on the device.
This forum documents that we're not alone. More and more, this place feels like a party that's actually long over, except for the few guys still hanging around 'cause they're too drunk to realise they should better go home. 🙂
Anyway: Thanks for all you've done in the past years! While I've never used Fulguris productively, I still use your initial "Fn-Tab = Alt-Tab" patch in my custom LineageOS builds. Concerning the latter: I think I will be continuing to make updated LOS 16.0 ROMs as long as the upstream sources get updated with backported ASB fixes, and switch to another phone after that support ends ...
-
2
-
1
-
-
27 minutes ago, fxnoma said:
So if I understand that correctly, even with the LineageOS 20 build, the connectivity is still all over the place, correct?
If the issues are software-related at all (which has not been proven), it is reasonable to assume that the bugs are in the drivers and/or their firmwares. Those bits are closed-source and cannot be fixed by LineageOS. They just re-use them 1:1 from stock.
-
2
-
-
18 hours ago, ScottB said:
Does anybody know when the phones will be available for sale? The website still says March 2023.
No, we don't. What we do know is that F(x)tec have been struggling to fulfill the pending orders and IGG perks for the better part of a year, and the situation does not seem to clear up. The phone might eventually become reavailable for purchase from their web store, but I wouldn't hold my breath.
That being said, quite a few phones have been delivered (though mostly not by F(x)tec), and unboxed-but-unused Pro1-Xs pop up on ebay all the time. So it shouldn't be that hard to get one if you really want it.
Then again, you might ask yourself why the Pro1-X is easily available on the secondhand market, while the much older Pro1 isn't ... 🤔
-
1
-
-
On 4/26/2023 at 12:23 AM, Name_not_avail said:
If the LOS devs re-establish the ability of the 1x to charge offline, then hopefully I never will.
As @Sean McCreary clarified in the LOS 20 thread, off-mode-charging cannot actually protect you from the battery-depletion-bug.
The Pro1X's (and likely any other Android devices's) charging is controlled by the OS in all cases. Seemingly, this means that some minimal amount of battery-charge is always required to boot the OS to the level where power-supply can be actively handed-over to a USB-connected PSU - irrespective of whether only the "charging screen" is loaded, or the full Android/Lineage GUI. Do not ask me why things are designed this insane way. It just seems to be the reality ...
-
1
-
1
-
-
@SchattengestaIt Those are amazing hardware hacks. Many thanks for sharing! We're slowly getting to where the maemo.org forum left off ... 😉
-
27 minutes ago, Sean McCreary said:
If the off-mode-charge flag is set, it will start the charger program instead of the full Android UI.
I had been suspecting this was the case for some time now. Thanks for clarifying.
This means that off-mode-charging cannot actually protect us from the battery depletion bug. If the battery is flat, it's game over, irrespective of the off-mode-charge setting.
29 minutes ago, Sean McCreary said:LineageOS doesn't have licenses for this source code, so we need F(x)tec to fix it.
Thanks, it is clear to me that LineageOS cannot fix those bits. Does anyone know whether F(x)tec actually have the sources? I.e. can they fix these things in house or do they rely on some external software company for maintaining the stock OS and its drivers?
-
1
-
-
3 hours ago, EskeRahn said:
ACCURACY_THRES seems to indicate that you now include some that were previously thought to poor quality signal to use.
That variable has nothing to do with individual signal levels. It works in conjunction with the INTERMEDIATE_POS=1 setting, and causes also the very early iterations of position estimates to be reported to client apps as a "fix".
The unit of ACCURACY_THRESH is meters. Setting it to 3000 means that early position estimates are reported, even if they are still uncertain by 3 km. However, to my knowledge, the variable does not actually influence how the iteration towards the final solution for the position progresses.
To me, the fact that @Name_not_avail saw their phone getting the fix while editing the gps.conf (without reboot!) suggests that the change of ACCURACY_THRESH from 5000 to 3000 did not have any part in getting things working. Rather, I think the other edits enabled AGPS in the first place. Note that, even with AGPS, getting the initial fix after a reboot can take some time. If the "A" in AGPS is not working for whatever reason (for example if there is no cell tower or internet connection), a phone GPS is often not able to get an initial fix at all - that's perfectly normal and expected.
-
1
-
1
-
-
So ... I recharged my Pro1-X battery using a laboratory power supply after it had depleted completely, probably due to the "battery protection bug" mentioned by f(x)tec in their updates.
It turned out that the most difficult part in this is getting to the battery. The Pro1-X is not nearly as "serviceable" as I expected. Separating the different parts of the body is not as easy as the instructional videos suggest. Also, the battery itself is glued into the phone, which makes its removal a scaring endeavour. Note that removing the battery from the phone is not strictly necessary for re-charging it. In principle, disconnecting from the phone circuitry would be enough. But for me, having the battery detached simplified connecting the external charger. You decide.
The charging itself is actually not very difficult, provided you have the necessary equipment and at least some basic electrotechnical skills. Still, here comes the obligatory disclaimer: Mistreating a Li battery can set it on fire and/or release toxic gases, be sure you know what you are doing at all times.
The Pro1-X's battery has a more-or-less standard connector featuring two power lines and two sensing wires. For external charging, make sure to connect to the (outer) power lines.
The laboratory powersupply I had at hand was a bit oversized for the purpose (32 V x 5 A), so I included two multimeters in the charging circuit as shown in the pictures. Using them, I could monitor the charging current and voltage with greater precision than the PSU's built-in gauges would allow. Especially for the voltage, we are interested in the 1-mV scale.
As written above, my battery started with a charge of "0.00 V". I started by slowly raising the charging voltage in voltage controlled mode, taking care that the current never rose beyond 1 A. This way, I quickly reached the 3.7-V operating plateau of the battery. From there, I set the power supply to charge at 840 mA in current-controlled mode for 1.8 h. I figured this should be a quite safe value, as the fast-charger operates at much higher current. Given the battery capacity of 3.2 Ah, I estimated to reach an approximate charge level of 50%, as the Pro1-X would later confirm.
During the current-controlled ramp, the charging voltage never exceeded 4.1 V. The battery did not noticeably warm up in the process. At the end of the procedure, the battery voltage (measured with the charging PSU switched off) was approx. 3.9 V.
In the end, my Pro1-X booted normally with the re-inserted battery.
-
2
-
4
-
1
-
-
So ... in case you want to relive the good old days with the Pro1 (SD835 only!), LineageOS 16.0 just got another update. At
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
fetch the ROM dated 202304024. It gives you backported ASB patches up to 5 April 2023.
There are no other changes compared to last month's release. Refer to my tarball of localmods for the full list of code changes with respect to upstream LineageOS 16.0.
Have a lot of fun.
-
3
-
2
-
-
18 hours ago, Name_not_avail said:
@claude0001That is terrible news. Maybe there is a thin hope, since there is enough power to illuminate the LED still.
Hold the power button for 60 seconds, and see if it tries to boot. Keep a charging cable handy, and jam it in there if you see the boot starting to happen.
LOS beta has only been around for a couple of months, so as long as you stored it while powered off, that seems like a short time for the battery to die. If it was stored while powered on though, that is probably the end of the story.
OK, fixed it. Prawn-X is back alive! 🥳
Turned out the battery was completely flat. After disassembling, I measured 0.00 V between the pins! I do not know how that happened, maybe I did accidentally leave the device on when putting it away. Still, I'm pretty sure the battery should never discharge to 0 V in any design scenario, as the device should automatically switch itself off before. I guess this is related to the "battery protection bug" f(x)tec keep mentioning in their updates ...
Anyway, I was able to charge the battery to ~50% (3.9 V) using a laboratory power supply. After that the Pro1-X booted normally and is now doing the rest of the charging from the usual wall plug.
I took some notes and pictures about how I did the manual charging and will report here. I remember there was some other thread about that ...
-
3
-
4
-
-
I fixed similar problems (in Germany) years ago by having the following changes in /system/vendor/etc/gps.conf:
[...] XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin [...] XTRA_VERSION_CHECK=1 [...] NTP_SERVER=europe.pool.ntp.org [...] INTERMEDIATE_POS=1 [..] SUPL_HOST=supl.vodafone.com SUPL_PORT=7275 [...]since then, GPS has been working quite OK for me (I have no Gapps on my Pro1).
Changing that file in LOS 20 probably involves Magisk scripting, which I unfortunately have no experience with.
As a quick check whether those settings help at all in your case, you could just try one of my LOS 16.0 builds, which have them already included. Of course you'll have to wipe data for that, but it seems like you're in the process of flashing OS's back and forth anyway ... 🙂
-
2
-
Retiring Pro¹ as my daily driver
in Pro1 - Thoughts & questions
Posted · Edited by claude0001
Happened to me once with LOS 20. The battery literally ran down to 0.00 V and I had to use a lab PSU to recharge it -- definitely not something you want to do every week.
@Sean McCreary confirmed that it is a problem with the proprietary BMC code, so the fix needs to come to Stock before community OSs can pick it up. I do not believe it is fixed in 2.1.5 as that has been around since September last year, and f(x)tec reportedly were working on the issue as recently as in March. Maybe in that 2.1.6-beta?