Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 12/18/2021 in all areas

  1. @SlionSadly all too true in general... However... 😃 !!! I FIXED IT !!! 😃 Disassembly was easy with guide referenced above on github. Actually impressed by how repairable this phone is. Removed battery (cell), did the "prick a hole in the cell to release the gas" trick (don't try this at home - see below). Put it back together and my phone is working just fine after 4 hours' careful work. Will be ordering a new battery from Indiegogo. Obviously, the battery is degraded but phone is working 100%. Yay! * * * The full story... Root cause analysis: I now think it
    8 points
  2. Personally I hope for e-ink keys like they had on the "Alias 2" a.k.a. "SCH-U750" Samsung made for Verizon. An ingenious solution, fitting 'any' language or gaming...
    7 points
  3. I recently discovered that /e/OS has a beta build for the F(x)tec Pro1 (the original device with the SD835 SOC, not the Pro1X, for now) available for downloads for those that are interested. According to /e/ themselves, "/e/OS is a complete, fully 'deGoogled', mobile ecosystem." It is compatible with normal Android apps, F-droid, Aurora Store and can, supposedly, pass SafetyNet checks by default. what do you think about adding this to the list of available ROMs, @EskeRahn? The link for info and download(s) is: https://doc.e.foundation/devices/pro1
    5 points
  4. They have just released another update here: Link Also, I wish you a Happy New Year!
    5 points
  5. Yep very good idea simply using a 1A-only port. I am exactly with you here, I don't need fast charge, the phone already lasts all day and 1A or even 0.5A is enough to recharge overnight. I was just lazy and did not do this, and now paid the price. I am a little happy though because I learned a lot, and I am now more certain of the quality and my ability to maintain/repair the phone. The Pro-1X will only be as good or better. Did more digging, and agree the Pro-1X is as compatible as it could possibly be including the battery. So I'll be ordering one on Indiegogo - along with the extra scr
    5 points
  6. Darn, well at least I know now, thanks for that! I will ask fxtec for the tool, and maybe can reverse-engineer it enough to make it work. It actually would be nice to be able to control the margins - by default, it is a little overzealous in that if you are holding the phone in your hand it's hard not to accidentally be touching a screen edge, which blocks all other touches from working. So a little bit of margin, but not too much, would be good. Probably not possible to reverse-engineer things enough to achieve that level of control, though, without ridiculous effort. I can't put my
    4 points
  7. Hey guys, Just as a minor update, I've been running ACC / AccA for a while now and it continues to work great. Charging current limit is rock-solid and will definitely prevent fast-charging if you don't want it. As others have noted, tweaking the PMIC settings may mess with the battery "fuel gauge." If you use more extreme settings, the more it may be messed up. Charging current limit is straight-forward and won't mess with the fuel gauge much/at all, as it works by measuring current in and out. One thing that will seriously mess up the fuel gauge is the max charge voltage. I've
    4 points
  8. Some time ago, I recommended Devuan as my GNU/Linux distribution of choice for installation in a chroot of LineageOS. Today, I wanted to upgrade my xrdp-pulseaudio modules (providing seamless sound forwarding to Android when using my X11 desktop) and found out that installing them on Devuan is not possible in a straightforward way using the tools provided on neutrinolabs' GitHub repo. The reason is that the drivers need to be compiled against the pulseaudio sources matching the version of each respective distribution. On Devuan, the command: # sudo apt build-dep pulseaudio fai
    4 points
  9. Thanks for sharing this article. Note that the comparison is quite unfair with respect to LineageOS in that, in this study, the LOS device had GApps installed, which then -- unsurprisingly -- phone home to Google in the same way they do when installed on a commercial AndroidOS. The Lineage Project does not ship GApps in their ROMs -- users have to install them separately (and willingly) from a 3rd-party source after flashing the OS. I think it is safe to assume that a LineageOS with MicroG (as also used by /e/) or a vanilla LineageOS (with neither GApps nor MicroG installed) would co
    4 points
  10. Build 20211219, with the December AOSP security fixes, is available at the above link. Full list of local mods with respect to upstream Lineage-16.0 tree: Modified gps.conf which (for me) enables the Pro1 to get its initial fix much faster. Corrected QoS powerhint signals. Backport from Lineage 18.1. Keyboard driver: Enable high keycodes Backport from Lineage 18.1. Keyboard driver: Fn-Tab acts as Alt-Tab. Cherry-picked from an experimental patch proposed by @Slion against LOS 18.1. Was never merged into any official distribution. Keyboard: Prevent unwanted mu
    4 points
  11. Only had to convince mine to move out 🤣
    3 points
  12. @mbecroft The instructions I suppose you're referring to describe the use of a proprietary not-for-distribution flashing tool specific to the digitizer in our screens. The flashing tool used to work with LOS 17.1 (Android versions up to Android 10), but there's no way to make them work with LOS 18.1. Hardly anything about that tool seems to exist on the net, and the few mentions I found only refer to even older versions than the one we're talking about here. For the time being, the only solution to the margins problem (for someone not using stock Android) unfortunately seems to be to flas
    3 points
  13. Wait. What? We have to convince our spouse??
    3 points
  14. Right - for example, if electrical design of Pro1-X seems to be done (which is the case hopefully), they can move to an other product without affecting Pro1's future development. If Pro1-X is mechanically complete, engineers may design something else mechanically. That way a company may keep its employees and make profit with something else when development of a product has been finished. Also that would mean a development of a future phone would be easier if you could keep your employees... Basically development of Pro1-X should has been already finished and manufacturing it the
    3 points
  15. Definitely! But with only one product that had to be delayed again and again for mostly no reasons of your own, with what would you pay your debts? Using the delay to design and market something else, potentially with a good profit margin, too, thereby hoping to keep your company afloat, actually might be the best option for enabling you to finally pay those debts.
    3 points
  16. 3 points
  17. I have received a reply from them today. They have promised me to send a replacement USB board, so I hope it will happen soon...
    3 points
  18. In case you have root, you can take a look at /sys/class/power_supply/... Just open any of the files inside the sub-directories of power_supply as text file to get an idea what it does. Some files can be read to get information about the hardware, like the battery voltage. Other files can be written to, to control the hardware. After some trial & error, you should have an idea which files are important to control the charging process. I guess this is also how ACC works. With apps like Automate or Tasker, you can run different scripts/commands to control the charge process i
    3 points
  19. Update FWIW, after running ACC for a few days. This is the best thing I've ever done to my phone (especially considering my current battery is not in top shape so I need to take care of it). The screenshot says it all. ACC does what it says on the tin and is perfect for keeping the battery charged between whatever levels you want, and at whatever current and voltage you want. Currently I've set it to start charging below 75% and stop above 85%, and at 650mA and 3.3V max (instead of 3.4V). Both of these dramatically reduce stress on the battery. As you can see, it is over 3 days since
    3 points
  20. I sent a message to Chen about this problem of people not getting responses. I hope they can find a solution to this problem.
    3 points
  21. Didn't find this topic which I think is a nice feature on maemo forum. So hello to everyone and happy new year 2022! I am hoping to be a new Pro1X user on february. Hoped I would have got it as a birthday present to myself on last march but didn't happen. I have been hassling with Nokia N900 devices for some years and managed to save 70 pieces of them from three crackheads who were thinking of using them as burner phones! They weren't in good condition (I mean the devices) but I am putting them together to contribute them to Maemo Leste developers. Have been sending working one
    3 points
  22. Yes, a happy new year to all! Or like the toast was in my house last night: "f*ck 2021"! By the way, there is a new product coming from F(x)Tec which I only learned about today through the Vimeo username from which the Pro1X video clips were posted. It's called the Linxdot Helium Hotspot, which seems to be a device that, in starting it up, becomes part of a LoRaWAN (low-power wide area network) based wireless network infrastructure. The owner then is rewarded with "Helium Network Tokens" ($HNT) which is a cryptocurrency, depending on how much coverage the device provides within that netwo
    3 points
  23. For limiting the maximum charge level, I use the Magisk module 'Advanced Charging Controller' (ACC) which also has a corresponding app (AccA). In normal use, I let it stop charging at 75% and start again when the level is down to 70%. ACC also has options to limit charging current and voltage, but these don't work with all phones and it seems they specifically don't work with ours. Neither do we have a 'battery idle mode' which could be prioritsed by ACC (completely bypass the battery when charger is connected and battery does not need charging).
    3 points
  24. Minor update: run-down tested repaired cell - using CPU/GPU-intensive benchmarks for several hours. Got down to 3% and 3.45V while pulling ~1.3A on OpenCL benchmark - terminated test at this point. Definitely was close to rated 3100mAh. I tried the trick of using a charger with 1A and 2.1A outputs, but even when connected to the 1A output, it charges at 1.5A (so obviously my charger does not signal the 1A charging rate, or current-limit the supposed 1A output). In fact, I tried 2 different chargers and on all of them it charges at 1.5A. (More specifically the "Max USB current" parameter i
    3 points
  25. As far as I know, those are real keys with tactile feedback but with a e-paper-like display area.
    3 points
  26. "Working on their next phone" might not be that absurd after all... If everything would have gone well with the Pro1, I suppose 2021 would have been the proper year to introduce a Pro2 anyway... And with the kind of stopgap the Pro1X has become and all the additional design work that had become necessary now done, I suppose that, commercially, getting a new, attractive phone ready is really the most import thing for them now...
    3 points
  27. Oh... and the ugly: I lost the rubber microphone damper (for the main mic) somewhere on the floor while removing the back cover. Phone calls are still loud and clear, but now markedly more sensitive to slight hand movements or brushing of the phone against the ear etc. while talking 😞 Moral of the story: microphone dampers are important - don't lose them!!
    3 points
  28. I haven't heard of any battery problems yet but the battery can be replaced relatively easily. However, I can not provide you any replacement battery sources except what you may find at their Indiegogo site (and which claims delivery next February if that is true). Anyway, currently I don't remember what an expanding battery may destruct inside (physically) but it may be a good idea to remove it before causing additional problems in the device...
    3 points
  29. Update: fx support got back to me and offered a free replacement screen assembly, which they claim will become available some time in January. They also pointed me to an aliexpress seller and suggested if I want it fixed sooner, I could buy this at my own expense. With fx timelines being what they are, I am not holding my breath for January, so have ordered screen from Aliexpress. Meanwhile, my current screen has mainly settled down and just sometimes has that one unresponsive row, but no crazy random presses, thank goodness! It seems I may now have another major problem - the batter
    3 points
  30. I don't know @Slion's reasons but for me, it started doing a soft-reboot loop every time when I have restarted my phone. Later, it has also started doing the same loop every time I put my phone to charger. That loop took for half an hour or so before the system booted up correctly. Also, uptime was still increasing, only Android soft-restarted on top of the kernel. After a while, I did a factory reset and it worked fine, but after all applications were reinstalled, it started doing the same loop. After another factory reset and unticking some applications during restore, it wor
    3 points
  31. I also use evil and vim keybindings on emacs. I remapped the left Alt on Pro1's keyboard to Ctrl key and remapped right Ctrl to Escape key. Thus, the most used modifier keys are near the home row. I have similar keybindings on my desktop mechanical keyboard as well, so there's a nice parallel. I can also remap the yellow arrow key on the right side to Ctrl, so I can still have two Ctrl keys. I also owned the Gemini and Cosmo Communicator. I just found them too bulky and awkward to thumb type on; 95% of the time I'll be using the phone while holding it in my hands, so the touch typing
    3 points
  32. I know you are joking, but I meant that quite seriously. My wife brings home half of the family income, but, for some reason, I thought I need a phone that is 10x more expensive than hers (while having worse audio quality 😉 ). Of course I explained to her why I wanted that Pro1 so badly before throwing all that money at a company that, even then, I was not sure would be able to deliver at all. If you manage your entire household from a common financial pool, it is imho a question of mutual respect to discuss major expenses prior to engagement -- especially if they are about what most peop
    2 points
  33. I wonder if the Pro2 could actually be that way... With an e-ink display under transparent keys 😍
    2 points
  34. Got it today, and took it apart, in an irreparable way. It is clearly one contiguous display., with a click-mat on top, that years back were transparent (...yuck it was gross beneath the metal frame on top...).
    2 points
  35. Right, that was what I have tried to point at. So an electrical engineer can do schematics and PCB design and microcontroller programming (but not every electrical engineers do all of them and the same level) and a mechanical engineer may do assembly-related designs (including the whole body) and modifications and usually high level software is also related to another team. It is not necessarily work this way but these are different professions and one territory may need specialists like designing multi-layer, high frequency PCB needs a special knowledge and correct antenna design ne
    2 points
  36. That could not be more true. Canonical (at the time they still backed the project) would have liked us to think about Ubuntu Touch and the Ubuntu distribution for PCs as two flavours of the same OS -- as in iOS vs. MacOS. Many users unaware of technical details may believe that to this date. The truth is, for all but a few exotic devices (like the PinePhone), Ubuntu Touch does not even use an Ubuntu Linux kernel! It bundles a minimal version of the device-vendor supplied Android system, including its kernel and driver blobs. It then uses compatibility layers (libhybris) to interface
    2 points
  37. Hey there. It took a while but I ended up disassembling my phone today (probably because I dropped it into water not only once but twice...). Sadly, I see no way to removing the fingerpring sensor to replace or remove it. Since it's not a double connector I can't disconnect the ribbon and send it to you. And to remove the sensor I'd have to break parts of the body. Since my secondary USB C jack isn't an option due to its depth (the battery would be in its way) I don't want to break the body to remove the fingerprint sensor. I'm very sorry. If you do find a way to remove the finger
    2 points
  38. @Jack T. Chance Exactly, the case you mentioned was hand-made from Jordi. I already gave it away to another forum user. I do think however that it's not too hard to make and Jordi might gives advice in case you need help.
    2 points
  39. After reading a little, I am under the impression that /e/ is indeed more about the default software distribution than about the underlying OS. Not to turn down that effort -- sane defaults that just work out of the box are certainly a good thing. I'll keep using vanilla Lineage (without Gapps or MicroG) for now. The Aurora store also displays tracker information from Exodus btw. But most of my apps are from F-Droid anyway... Thanks for sharing.
    2 points
  40. Well, to be honest, I just like the feel of /e/ better than lineage. Also, /e/ has their own Apps store that includes a privacy scan from Exodus Privacy (lists all recognized trackers and permissions in the apps) for all apps in the store and gives the apps a "privacy score" based on that. Pretty neat. I do like the default apps in /e/ a little better, while I have to say I like the default launcher of lineage a bit more, but both are highly subjective, I suppose.
    2 points
  41. For those with GNU/Linux-chroots: UPower provides a friendly interface to display the information from that sysfs tree. E.g. rostkatze:~ # upower -e /org/freedesktop/UPower/devices/battery_battery /org/freedesktop/UPower/devices/line_power_dc /org/freedesktop/UPower/devices/battery_main /org/freedesktop/UPower/devices/line_power_pc_port /org/freedesktop/UPower/devices/line_power_usb /org/freedesktop/UPower/devices/battery_bm
    2 points
  42. Generally, charge estimation based on voltage is very inaccurate if we are speaking about Li-Ion-like batteries but old phones used this prediction. However, there are "battery fuel gauge" ICs which a modern phone should use and it measures incoming/outgoing charge of the battery (charge / discharge quantity). It may have a very good prediction based on charge/discharge current, voltage, elapsed time, predicted battery degradation, etc. ...so it is much more complicated than simply measuring battery voltage what would be very inacurate if we are speaking about accurate percents...
    2 points
  43. I confirm that it works with my phone, too! (It's been a while that I tried and found it to not work, there were a few updates for both LineageOS and ACC in the meantime.) It's does not follow my voltage and current limits exactly, but it generally does what it says it does.
    2 points
  44. 2 points
  45. See my edited post - ACC is working really well including charge current and voltage limits. One time only I encountered the "not charging" state, and this corresponded with when my battery nearly self-destructed. Not sure if this was coincidence or if it sensed too high battery temp or what. The charge control on the Pro1 is more advanced than on previous Qualcomm MSM chipsets I've worked with. For one thing, it has the "Max USB current" setting (see in my screenshot further up in thread) and this gets set based on a number of parameters. It is this parameter which gets set by ACC t
    2 points
  46. Hmm, interesting, thanks @Rob. S.. Looks like I may need to poke around a bit more... I have dealt a bit with Qualcom PMIC before, but this one may be completely different, who knows! Will report if I find a solution 🙂
    2 points
  47. Yes, never trust the rated max output on a charger! Especially if it is an 'unknown' brand. I always use a meter to test, and have seen both way below and quite a bit above the rating. As many in here will know, I also recommend charging at no more than 5W for daily charges. I only use fast charge when I really need it, and not for full charges.
    2 points
  48. I have picked a USB charger which has a 5V 1A-capable port along with a QC 12V compatible second port. I use the former to charge my Pro1 overnight which is well enough for me for daily use and it does not cause any excessive heat of the phone at all. Yes, I think. They wanted to manufacture the very same phone which was not possible, but they still wanted to keep as much of the Pro1 as possible, so there is high chance for the battery remained the same. I am glad you could solve the most urgent problem in your phone. I am agree there are two possibilities of long-term solut
    2 points
  49. I use my Pro1 using LineageOS with two SIM cards and I have no problems with it. However, I have experienced a similar problem when VoLTE was enabled but Mobile Data was connected using the other card, so that may be the cause of such a problem. ...but otherwise it works well with 4G enabled, but only primary card can use 4G (by design, not limited to Pro1). So in a country (like in the USA) where 4G is the only option (so no 3G or 2G coverage), the usage of two SIM cards really does not work because of technical limitations.
    2 points
  50. I just thought of a few more reasons why the z fold soft keyboard annoyed me. 6) There's no way to hold down a key to send multiple presses at once. For example, I'm using evil in emacs and I'm trying to go down some text; I can hold down the j key on my desktop to go down multiple lines quickly. However, with a soft keyboard holding down a key doesn't work that way. A key press only registers once you let go of the key. The only thing you can do with a long press is pop up a different symbol to input. Thus, I have to repeatedly press the key to go down one line at a time. So it's ju
    2 points
×
×
  • Create New...

Important Information

Terms