Jump to content

claude0001

Members
  • Content Count

    518
  • Joined

  • Last visited

  • Days Won

    58

Posts posted by claude0001

  1. 1 hour ago, PC_ said:

    Does anyone know if F(x)Tec are ever planning to release v10 for the Pro1?

    I am pretty sure there will never be an official Android 10 or 11 for the original Pro1. All development efforts target the Pro1X by now.

    As @VaZso wrote, Lineage 17.1 and 18.1 are available for the Pro1, and are technically equivalent to Android 10 and 11. Lineage 19.0 is already in preparation. 

    However, I have doubts that your security auditors will consider a custom ROM as equivalent to an official Android provided by the device manufacturer when it comes to certifications.

    • Thanks 2
  2. My thoughts on this (more or less unchanged since that other thread on the AstroSlide): The two devices are complementary.

    For me the AstroSlide is -- unfortunately -- too large. Imho, today's smartphones cannot practically be larger than the span of a person's thumb.

    The Pro1/X is really the largest device I could operate single-handedly in what is today's de-facto standard mode: portrait-touchscreen-only. The AstroSlide is significantly bigger, so I expect I would not be able to use it comfortably as a regular smartphone when holding it in one hand. This may seem like a small thing at first, but can become quite a nuisance in practical life if you intend to use your phone not only as a UMPC but also in the way 99.9% of modern apps assume.

    I do like the basic idea behind the AstroSlide: be a UMPC that is really able to emulate a phablet with keyboard closed. Unfortunately I do not believe it works in practice because of the size dictated by the (nice!) keyboard. 

    The Pro1(X) focuses on working well as a standard (touchscreen) smart phone and adds the hw keyboard as a bonus. The Astro is the opposite. It seeks to be a good UMPC primarily, with the added capability to disguise as a phone. For me the former is the right choice: whenever I expect the need to perform extensive typing on-the-go, I carry along my UltraBook anyway, which -- with all love due -- is superior to the Astro in every respect ... except in being a phone.

    That said: everyone who likes it, please buy and support the AstroSlide! The true problem we face is not competition by some other niche keyboard phone manufacturer, but the prevalent perception of smartphones as dumb(ed-down) consumer appliances rather than the full computer systems they really are.

    • Like 2
  3. 47 minutes ago, wrc08 said:

    The version is 16.0-20201019-NIGHTLY-pro1.

    That's the last official build that was made at lineageos.org. I am using my own builds since then but have never changed anything on the recovery system. So I think the keyboard should work in your version, too.

    Concerning transfer of your apps and settings I do not know. There are backup solutions that are supposed to be able to do that, but I have never used any of those.

  4. @Fxtecish Thanks for your compassionate words regarding F(x)tec's situation. Indeed, people tend to forget that what F(x)tec are doing is deemed unreasonable by all of the big phone manufacturers (as it supposedly does not pay off): make a keyboard phone for the few people out there that really want to use their device as the mobile computer it is.

    Off-topic: I do not get why you engage in refurbishing N900's in 2022. Do not get me wrong: I own two N900's and love everything about them. But I really think their time is over. Their CPU is too slow and their RAM too small for participating in today's Internet. 3G being shut down around the planet is the final nail in the coffin for me. What future do you see for that device?

    • Like 2
  5. Just as a last resort: What version of LineageOS 16.0 are you using, exactly? Go to "Settings -> About Phone -> Android Version 9": that will show the "LineageOS version" string. If it is a really early release, one could check if keyboard support in recovery was added only later during development ... I wouldn't count on it though.

    28 minutes ago, wrc08 said:

    What if I by a new Pro1...?.

    Unfortunately, there are no new Pro1s to buy. The Pro1X is a completely different phone, so it will not be possible to transfer your LOS 16.0 to it.

    I would contact F(x)tec and try to send them the phone for repair. Despite all the bad experience regarding their responsiveness reported here, there are people who have had their phone repaired without any trouble.

    Alternatively, you could open-up your Pro1 and look for the connection. But as far as I understand the guide, the process involves a hot air gun and and almost complete disassembly of the bottom part of the phone. I am not sure if I would try it myself.

    • Like 1
  6. 1 hour ago, wrc08 said:

    You mean the recovery mode with "volume- button" and "power button" at the same time?

    Yes that's what I mean.

    "Volume Up+Power" boots to the Lineage recovery system (which you used for flashing Lineage initially).

    Not to be confused with "Volume Down+Power" which takes you to the bootloader (which does not have keyboard support).

    • Like 1
  7. 16 hours ago, wrc08 said:

    1. I can determine if there is a hardware or software failure in the physical keyboard

    Actually, I just thought of a more simple test for this.

    I realised that the Lineage (16.0) recovery system supports the Pro1's hardware keyboard: when I boot into recovery, I can navigate through its menu using the up/down-arrow, return, and backspace keys on the keyboard.

    Could you check if this works on your phone? If yes, this would clearly demonstrate that the keyboard itself is fine. If not, I think it would be strong indication of a hardware failure and your chances of fixing things by reinstalling the system would be slim ...

    • Like 2
  8. Concerning:

    15 hours ago, wrc08 said:

    2. I reinstall LineageOS, either the 16 again or the 18, probably doesn't matter

    As you mentioned earlier, your present system is rooted.

    It might thus be of interest to you that LineageOS 16.0 was the last major release with built-in root management ("AddonSU").

    Starting from 17.1 you have to use Magisk for rooting, which I am sure will work, but may require to do differently whatever you are using your root access for.

    • Like 1
    • Thanks 1
  9. @VaZso : UbuntuTouch on the Pro1(X) is not about vanilla Linux support (mainlining). Ubuntu on Pro1 and Pro1X uses / will use libhybris, which does make porting easier. Still it takes a lot of polishing to get a port to a state where it can be useful to average Joe as a phone. Look at that thread I linked above: the UbuntuTouch port for Pro1 does not provide the most basic functionality you expect from a smartphone: GPS, cellular internet either do not work at all, or not out-of-the box. HDMI out is not there (which is huge, as many want Ubuntu for the "convergence" thing). When such bugs are still present two years after the device hit the marked, it is pretty clear that the community is not able to fix things on their own. Fact is, development of that port has stalled. The same will happen with Ubuntu on Pro1X if F(x)tec do not push the development themselves.    

    Of course, that same rom polishing is also necessary for any new Lineage release. But because of the much larger community, there is obviously more momentum in the development and bug fixing processes over there.

    I belive SailfishOS on the Pro1 is in much better shape than Ubuntu, actually. I tested a very early version, and only gave up on it because of reasons of App availability. From the point of view of OS architecture, yes, I think it is much closer to the N900. But we're drifting off-topic ...

    • Like 1
  10. 32 minutes ago, VaZso said:

    ... there would be people who don't really care the OS ...

    From an Android user perspective this may be true. Someone would eventually port LineageOS to the 662-Pro1, even if Fxtec would not support that process at all.

    But UbuntuTouch is a different story: F(x)tec themselves have stated (at some early stage of 662-Pro1 design) that the Ubuntu option was an important point for quite a few backers of the Pro1-X. So they'll have to have that OS available at some point. And, here, experience from the original Pro1 shows they cannot rely on the community to do the work for them: the UBPorts crowd is too small to support obscure devices on their own. As documented on this very forum, there is -- to this date -- no truly functional port for the 835-Pro1, and, sadly, probably never will be. 

    • Sad 1
  11. 4 hours ago, VaZso said:

    personally I would be completely okay with that... moving to another OS on Pro1 is not hard at all, I hope it will be similar on Pro1X.

    I had Android 9 on my Pro1 for a total of 5 minutes, or so, before flashing LOS onto it. So, yes, I fully agree, personally.

    Problem is, they made a big deal about the "other OS" option being really official this time. If they fail to deliver in this respect, it will add-up to what is already an unfavorable picture at best.

    • Sad 1
  12. In sharp contrast to when the original Pro1 was still in pre-production, whe have (to my knowledge at least) seen no enthusiastic demo videos of Pro1X's running an alternative OS so far. All there was, was a screenshot from the UbuntuTouch settings panel in the November update, along with the comment that porting of alternative OSes to the 662-Pro1 has "started".

    I thus expect LineageOS and UbuntuTouch development to be lagging behind at this point, which would explain why you were not offered the choice of the OS.

    I wouldn't be surprised if they eventually shipped all devices with Android after all, providing downloads and support for users to flash Lineage or UBTouch themselves when those are ready ...

    • Like 2
  13. 32 minutes ago, wrc08 said:

    I've wiggled the ribbon cable between the screen and the keyboard before

    The ribbon cable that is exposed by the Pro1's mechanism connects just the screen unit to the mainboard. The mainboard is inside the bottom half of the phone which also holds the keyboard. So the connection you are interested in is not visible from outside.

    • Thanks 1
  14. 1 hour ago, wrc08 said:

    Under Settings--> System--> Language&Input under Physical Keyboard it says "not connected".

    For LOS 16.0, the usual string shown there was "Builtin Keyboard".

    I'd say, either the keyboard is indeed physically disconnected, or the system has been re-configured to default to some other hw keyboard. Did you ever use an external USB or Bluetooth keyboard in the past? If yes, what happens if you re-connect that?

    However, as your problem appeared kind of gradually, I rather fear that the keyboard is indeed not properly connected to the system board anymore. Maybe the ribbon cable connecting it to the board has loosened with time. There is a quite complete official disassembling guide for the Pro1 (links have been posted here several times). I have never disassembled mine until now, so I cannot judge how easy it is to check this. Others here have more experience.

    • Thanks 1
  15. 21 minutes ago, wrc08 said:

    Is there any way I can get up to LineageOS 18.1

    If you haven't updated your LineageOS 16 in two years, chances are you using one of @tdm's unofficial builds. Not sure if there are supported upgrade paths from there. I'm still on (a modded) LOS 16 myself, others might know better if upgrading to 18.1 can be done tranparently in your case.

    However, if you never updated, regressions in LOS cannot be the reason for your troubles anyway, so what would be the point of upgrading now?

  16. 4 hours ago, wrc08 said:

    If I reset the factory settings, then everything is gone ...

    Before wiping everything, I would first try to just uninstall MS Swiftkey, and see if that helps.

    I do not know that software from personal experience, but from what I read, it does have functions related to hardware keyboards. Maybe there is some conflict with native keyboard handling in Lineage.

    Also, there has been quite some development around the keyboard driver in LineageOS (18.1) during the last few months. While all these changes were of course meant to improve things, regressions for heavily customised set-ups are always possible, I guess. Which release and version of Lineage are you using?

  17. 2 hours ago, suicidal_orange said:

    It wouldn't take 5 minutes to tell everyone what they already know

    Considering how people here and on IGG analyse (and maybe over-interpret?) these monthly reports, I think they spend quite some time writing those up. I can imagine they plan very carefully what to publish and how to present it in a way such as to cause least damage to the project. It is easy for us to ask for more honest reports and estimates, but unfortunately it is also a fact that many customers need the harsh reality to be "embellished" for them, or else they jump ship.

    Some people understand that by supporting Fxtec, they support an interesting enthusiast project: a concept of a smartphone all big players have abandoned for a reason (profit), and they are ready to go through some lengths for that dream. But many (most?) of their customers do not care about such things, and never thought of the possibility of Fxtec actually failing on the marked and them loosing their money -- simply because that is not what they are used to when buying from big manufacturers. If you had honestly told those people they just payed 700 bucks to get a 2019 SoC in 2022, they'd have said: "f**k you, gimme my money back, I'll get an iPhone!".

    One year ago, I did not believe one second Fxtec would be able to develop and deliver what amounts to a completely new Pro1 model within 7 months. And I guess they, too, knew that their proclaimed delivery in August was an overly optimistic estimate. But Just imagine they had, in January 2021, openly admitted people would probably not get their phones before mid-2022. Would the project still be alive? I honestly do not know. But this is the kind of questions they have to answer for themselves whenever they need to communicate another setback.

    • Like 6
    • Sad 1
  18. 2 hours ago, Rob. S. said:

    Comments on IGG

    I like most the ones that tell me F(x)tec is a fake company and that my Pro1 does not exist. 🙃

    Thinking that through, it follows that we in this forum as well as all other people publishing Pro1 videos on the web, discussing bugs and hardware issues, making custom ROMs, etc., are just actors hired to distract from the fact that Fxtec have long moved to the Caribbean where they spend their backer's money on expensive cigars. One wonders if setting up such an elaborate smoke screen would really be easier (or cheaper) than just producing the phone after all ...

     

    • Haha 3
  19. 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

    I finally made a new image (20220129-UNOFFICIAL) with the January 2022 security patch level.

    Full list of local mods with respect to upstream Lineage-16.0 tree (practically unchanged since December):

    • 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 multiple keystrokes: Backports of LOS 18.1 patches 318274 and 318496.
    • [New:] Some purely cosmetic changes to hardware keyboard settings panel, inspired by LOS 18.1.

    The source code changes with respect to upstream are now also available as a patchset at the above link.

    Have fun.

    • Like 6
  20. I've had one such dot since day one. It has not worsened one bit in 1.5 years. It seems to be a quite common QA problem with this kind of screen, not limited to the Pro1. I wouldn't worry too much about it.

    • Thanks 2
  21. On 1/25/2022 at 9:13 PM, LordV said:

    I was looking for a way to automatically turn it on, but everything I tried had no result.

    When I place a script named e.g. "99hwoverlays" with the following code

    #!/system/bin/sh
    #
    # Set "Disable WH Overlays" developer option at startup
    #
    bash -c "service call SurfaceFlinger 1008 i32 1" &

    into /data/local/userinit.d/, the "Disable HW Overlay" option gets set automatically after boot.

    Remember to make the script executable (chmod +x). Also note that user startup scripts in /data/local/userinit.d/ are no longer executed by default in modern LineageOS, you have to install some helper app like RunUserinit from F-Droid.

  22. 13 minutes ago, LordV said:

    Do I understand correctly that you have no problems with the animation? I have a very visible slowdown when scrolling through lists in all places without activating this feature.

    It's always difficult to discuss topics that are somewhat subjective ...

    It would probably be good if you could provide a specific and (hopefully) reproducible example of an app that does not scroll smoothly for you.

    I can scroll smoothly (as far as my expectations go) when browsing through a thread in QKSMS, when scrolling down a web page in Firefox, when displaying a thumbnail gallery in the default Lineage picture app, when displaying folder contents in MaterialFiles, and when browsing through a lengthy program in Acode.

  23. 1 hour ago, LordV said:

    If in the developer settings turn on the function "off hardware overlays" and "gpu rendering" then the problem disappears until you reboot the device.

    I have never played with those options and am certainly no expert in tuning the Android graphics stack to its max.

    However, there seems to be consensus that those options are not enabled by default for a reason. That's especially true for the "Disable HW Overlays" flag, which seems to worsen battery life (as more CPU load is generated). I'd rather not mess with those defaults in my ROM.

    I can confirm that also for me "Disable HW Overlays" is not persistent across reboots (while "Force GPU" is), which is kind of strange -- although it could also be an indication that this is really a debugging feature only that should not be enabled all the time on a production system. I could look into how to make that setting persistent for you, but it's going to take a while, probably.

    If you are rooted, there seem to be ways to enable "Disable HW Overlays" on boot automagically. Would that be an option for you?

  24. 6 hours ago, VaZso said:

    Right, but they planned that Pro1-X will be 100% identical to Pro1 inside

    That's a good point. You are right that the Pro1 could -- technically at least -- have had the upgrade to the Pro1X's Android 10 for "free" if the SoC thing had not happened.

    However, it is also true that updates of stock Android 9 stopped long before the mainboard change. As far as I know, they ran into trouble with their contractor making the OS, independent of the other issues with the SoC manufacturer. Let's hope they (and we) will have more luck with the Pro1X ... 

    • Like 4
×
×
  • Create New...

Important Information

Terms