Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 03/22/2021 in all areas

  1. Alright, after toying with it for a few days I have cracked dual booting and decided to write up the steps myself. YOU WILL LOSE YOUR DATA DOING THIS. Credit to @order#10248 for proving the concept. First thing you will want to do is re-flash stock android on your phone. There isn't an official repo for this yet but @Waxberry has kindly provided one on this post. Download and extract the files from there and run the script fastboot_all.bat or you can download my modified linux version flash_all.sh. While that is flashing, download the latest version of Lineage here. Yo
    14 points
  2. YES!!! See attached video file (sorry for the ridiculous video quality ... had to shrink 2min to 2MB ...) I now have Ubuntu Touch via "Slot A" and LineageOS 18.1 via "Slot B". Dual boot procedure takes to get used to: It's not choosing OS during boot, instead it works from fully booted OS and then "OK, reboot into the other OS". The app used for that is "Switch My Slot" , with existing versions for UBports (Ubuntu Touch), Android and Sailfish. Feels like ages ago having such a satisfying moment like seeing this on my Pro1 \o/ Cheers, order#10248 Edit: Video is
    9 points
  3. Update: I can now run the X.org X11 server inside my Devuan chroot. Yes, the real thing, not TigerVNC or TightVNC. The nice thing with X.org is that I can use it with xorgxrdp in the chroot and connect to my Linux distro via a much better-performing (native) RDP connection as compared to using VNC as backend for XRDP. I still use the Microsoft Remote Desktop 8 App combined with the default xrdp-0.9.9 shipping with Devuan 3/Debian 10. As far as I can see, one can find no information on how to do this on the internet. Either it is really tricky and I am a genius, or no one cares about
    8 points
  4. I figured it out and wrote up detailed instructions for anyone else looking to do this.
    7 points
  5. tdm added a feature to his keyboard driver that allows the user to specify a custom keyboard map. Unfortunately there is no documentation (other than the source code), but you should be able to remap any non-modifier key (e.g. not shift or ctrl) to generate any keycode you want. By default, the QWERTY and QWERTZ maps are set to match each key to the glyph printed on top, but of course the FinQWERTY maps make different choices than F(x)tec did when they designed the two keyboard layouts. The relevant source code is here: https://github.com/LineageOS/android_device_fxtec_pro1/tree/line
    7 points
  6. Hi re-flashed the phone two days ago, and now the HDMI works. So now when I writing this post i have my phone connected to my Dell WD19 docking station. I see the phone screen on all three monitors, mouse and keyboard is working . (sorry for the really messy desk, I am a hardware developer )
    7 points
  7. As much as I enjoy the fact that LineageOS on the Pro1 seems to be alive and well, I am puzzled by the practice of removing previous major releases from the build systems as soon as a new version is made. In November, LOS 16 stopped receiving upstream updates (in favour of 17.1) just a few months after I had installed and -- quite heavily -- configured it. Now, 5 months (!) later, 17.1 disappeared from the build targets for the Pro1 at the very moment 18.1 came around the corner. I understand that a community project may need to save computing ressources on the build farms. Stil
    6 points
  8. Looks like the suspicion I wrote about earlier was correct. Since I disabled "4G calling" (HD voice aka wideband audio) in "Network and Internet" -> "Mobile Network", I didn't get any calls anymore with too loud in-call audio. I'm quite confident about this now as one specific caller which always used to be too loud when calling from his home line wasn't too loud anymore after I made that change. So far I don't see any disadvantages of that change, either. [Edit:] This is LineageOS 17.1. Sorry I didn't mention this earlier...
    6 points
  9. Latest experiment (courtesy @vvv): Adding more padding to the LCD connector. I noticed the foam where cutout for the LCD o on the chassis has a pretty deep marking (not my phone shown, just for location): (Source: https://gelraen.github.io/fxtec-pro1-teardown/) Folded up some duct tape, and padded that cutout. So far it's working, I was able to complete 2 Mario Kart races without losing control. Calculator test also passed. Will report back in a day, my last reseat lasted that long.
    5 points
  10. Announcement: https://www.xda-developers.com/lineageos-18-1/ Upgrade: https://wiki.lineageos.org/devices/pro1/upgrade Get it here: https://download.lineageos.org/pro1
    5 points
  11. Flashed the first 18th version that was listed for download. Backuped everything, but didn't need to. Flashed the 18th version, flashed MindTheGapps, flashed Magisk, done. Everything works as good as before. Went from 16 to 18. The phone seems to respond quicker than before, or the animations give the impression that it does. I like the new theme.
    5 points
  12. A quick rundown of my dirty flash: Had LOS 17.1 with OpenGapps Nano installed. Download LOS_18.1.zip and MindTheGapps_11_arm64 to PC Connect phone to PC Reboot to recovery (the recovery from LOS 17.1 will do - no need to fastboot flash the recovery.img) Install via ADB sideload run from command line: adb sideload lineage-18.1-20210401-nightly-pro1-signed.zip Select Advanced -> Reboot to Recovery run from command line: adb sideload MindTheGapps-11.0.0-arm64-20210220_140101.zip Reboot Have my Pro1 running for 4 hours now without issues.
    5 points
  13. Of all the days to release the first official 18.1 build, they chose this one.
    4 points
  14. Another update... so my last experiment failed, problem came right back after 24 hours. However, re-reading what @vvv was saying about the PCB flex, I tried adding a little tape to the hold the PCB down rather than padding the connectors. Seems like this one did the trick, it hasn't gone crazy for more than a day. One little symptom remain though, is that "strip" of display where it dances on when it goes crazy, isn't as sensitive anymore. More specifically, sometimes it misjudges a swipe as a tap, accidentally activating the item there. This does bring a lot of validity to say the proble
    4 points
  15. ...and my cat today in a very dark environment:
    4 points
  16. Most threats can be avoided by installing only trusted (if possible open-source) software on the device. This includes an up-to-date web browser. No one is forced to use the default browser shipping with the OS. Of course, having AOSP security fixes would be nice, and we would readily apply them if we could have them without the functional regressions related to upgrading to a higher Android version.
    4 points
  17. I do not understand this point. Actually, the Pro1-X SoC still has a long support life ahead. After all, that was the reason for the switch. With its longer EoL, the 662 Pro1-X may also eventually have better software support: I doubt that newer Android versions will ever appear for the original Pro1. Ubuntu development is probably focusing on the Pro1-X right now. In the long run, the 662 may also have better chances regarding mainline Linux support than the de-facto obsolete 835-Pro1 ... Finally, the redesign of the mainboard may be a chance for FxTec to fix a few quirks of the ori
    4 points
  18. There seems to be some TWRP ... see https://community.fxtec.com/topic/3005-ubuntu-touch-os-for-fxtec-pro1/ ... Preparation: TWRP for Pro1: Download here https://drive.google.com/open?id=1IgUjxEKV5MU_3cRkNCyGc-YpRkUQ3xHh (Credit to Mccreary) ... Thanks for for the steps/listing! I was on LineageOS 16 (Android9) and had to activate USB debugging via --> Settings --> About Phone (scroll down to last option) --> Build number (scroll down to last option) and tap on "Build number" multiple times --> until notifcation for "developer options are enabled" -->
    4 points
  19. Tried to extend the opengapps table with MindTheGapps: The last two I THINK could be included as obligatory in say "Google System Base" for OpenGapps. (I got them on AICP Q + OpenGapps 10 Pico also)
    4 points
  20. Let me try to rephrase that in a more optimistic way: They are very enthusiastic about porting the latest-and-greatest release to the Pro1. 🙂 The real problem is that, as soon as a new release (here 18.1) is declared "official", the previous one (17.1) stops receiving upstream patches. De-facto, releases are dropped from support at the very moment they have matured ... Effectively, users have only this choice: Either stay on an older, stable, and nicely de-bugged LOS port that does however no longer receive upstream AOSP fixes. Or change horses every few months b
    4 points
  21. If you just want to run a few Linux programs, something like Termux and AnLinux is definitely the easiest way to start. I have never used those Apps, though, so I cannot help with specific questions about them. For advanced stuff, like the above, a "hand-made" chroot (with root access to Android/Lineage) will probably always be superior to (non-root) in-App solutions. Setting up your own Linux chroot on Android is actually not that hard provided you have some experience with Linux. The real problem is that the required information is scattered all over the internet. Also, some things
    4 points
  22. As I wrote above, 17.1 no longer has the Pro1 as build target, so there will be no more (official) updates for it. See https://www.lineageoslog.com/17.1/pro1 ... and that is exactly why the older, stable versions should keep building, at least on monthly basis so they keep receiving the upstream security fixes in AOSP. Every upgrade that changes APIs or other major parts of an OS is potentially disruptive for the already-installed base. That is why professional distributions keep their "stable" branches alive as long as upstream fixes can be picked-up with reasonable effort.
    4 points
  23. Just a small update... The ghost touching got to a point where the phone was unusable and I couldn't even enter my pattern at boot without a lot of retries. Also got a bit dangerous yesterday when I was using my phone as GPS and it kept randomly switching out of Waze. @Hook posted some troubleshooting steps done with F(x)tec so I thought I give it a try (specifically checking if any flex cables were loose), and it SEEMED to have helped. I followed gelraen's teardown instructions and took the screen apart. Cables seemed tight, but I went ahead and reseated both the LCD/Camera to main
    4 points
  24. I shattered a screen with a closed flip case, it won't protect the left side of the phone at all. Personally I really enjoy the 3d printed case from @LIMA but I'm looking closely for the one from @ubuntuscofieldand @belletrist Those 3d printed case can protect the phone way better than a flip case
    4 points
  25. 1. An IGG perk is NOT a contract, which is clearly stated by IGG in many places, including when you select your perk. 2. They substituted a slower, less powerful SOC, but you are right, it won't change it that much. 3. While they do like to show off games on their Pro1s in their tweets, that isn't the main point of the pro1 and it won't be for the Pro1 X either. 4, They have carefully explained everything in the IGG Updates including what happened and why they made the choices they made. You are entitled not to like those choices, but such changes are the things that happen wh
    4 points
  26. @tdm I'd also be very happy if you'd find a solution to decrypt the data partition. Full description why here: Essentially the problem is that I want to get one file off from the data partition and I basically don't have root.
    4 points
  27. conjuring for sure. If you have no virgin blood, you should try emailing them directly.
    4 points
  28. 4 points
  29. Ok case arrived and as it does indeed fit very well. Needs the normal holes cutting which I haven't done yet can't find my belt cutter.
    4 points
  30. Congratulations Zahkc for getting it done and a very big Thank You for writing this up! Excellent work, I was about to share the notes I have made while dressing up my Pro1 to get famous, but that were already some meters to scroll (thats how it felt 😉 ) ... and you nailed it down. My way to get to dual booting was slightly different in details. But all in all the same. Still I want to paste some additional notes here. ****************************************************************************************************************** Basic things I learned, that might enlight the gu
    3 points
  31. Yeah your going to need to request the evidence of delivery from DPD. As they say they have delivered it somewhere if they can't provide it then they are liable. (But only to the insured amount) But if the evidence does suggest they delivered it is with FxTec and in that case you can take them to the small claims court in the UK. (Not sure how that stands for an alien)
    3 points
  32. This actually explains why sliding your finger on the bottom it might trigger the problem. Now I'm curious if everyone is having the problem at the same exact location, which could indicate a recurring problem caused by a particular flaw in the design.
    3 points
  33. Good point. (I can not seize to be amazed of the odd results when the forum when referencing a thread just adds a random excerpt of a picture from a random post in the thread to 'illustrate' the link. The picture is certainly more confusing that helping here 🤣 )
    3 points
  34. Just an idea: Find a different cheap phone (possibly used with broken display) that also supports LineageOS, and try to build roms for that. when you feel comfortable doing that, you could switch to your Pro1
    3 points
  35. One more datapoint for the group here, but I'm experiencing the same problem, and noticed the same behavior. I then noticed that the ghost touching starts pretty much soon as I clip in the lower-right corner of the screen, near the lcd connector. The black PCB there seems like it has a lot of flex to it, and my theory something's damaged in that PCB from the flex. I stuck a folded up sticky note under that pcb to provide some rigidity, and although the problem is not resolved, and I still have a bit of a weird unresponsive area of the screen, it seems to be an improvement since I'm not ge
    3 points
  36. Several older branches are patched each month from the Android Security Bulletins on an unofficial basis, but the LineageOS project only makes official builds for one branch at a time for each device. You can use the updated branches to build a (mostly) patched version of 16.0 or 17.1 for the Pro1 by following the instructions for building your own images: https://wiki.lineageos.org/devices/pro1/build These monthly updates do not include any new kernel patches, however, or any fixes for the pre-compiled libraries (a.k.a. the 'vendor security patch level'). For a sample ASB update (Ap
    3 points
  37. You're right. I just checked by powering it back to life. I've put lineage 14 at that time. And it's damn slow... It boots and charge the battery though. It's funny how it looked big at the time I got it, and now it is cute and the good size to me. Sad in a sense...
    3 points
  38. I have one phone i stuck an iphone 4 keypad to I found still in stock in a local webshop after a long search: I cut off the edge of the iphone case thing with a knife and put double-sided tape on there. Removing the case entirely wasn't possible as it's integral part of the sliding mechanism. It works allright but there only being a shift key on the left side is rather annoying, also it slightly interferes with the camera when closed but if I'd been more thoughtful before sticking it on there that could have been prevented I think. Also the keypad is quite low quality and it's
    3 points
  39. OK more updates... Mine went absolutely nuts again, couldn't even control it. Out of desperation, I tried loosening and retorquing the screws mounting the screen with, seems like it helped. Somehow I managed to get it back in control to a usable level. One theory was that it could be due to the mounting of the screws causing a torsion on the screen, since sometimes pressing on the side frame it would trigger the issue. Could be fluke, not sure. Guess I'll just have to keep experimenting till I get my replacement screen.
    3 points
  40. OK, look guys, my post was a reaction to @daniel.schaaaf, who I think is fundamentally right in his criticism of some aspects of today's open-source software culture. I tried to provide some examples how us so-called "power users" are simply more affected by major OS upgrades, and are hence left in the rain if Lineage versions are abandoned at every second stop. True. But neither can we change FxTec ways of public communication, IGG policies, or EOLs of QualComm product lines (to name but a few). Did that stop anyone from whining and complaining here? Now it is my turn. 😉 Self-bu
    3 points
  41. The case in black.
    3 points
  42. I certainly hope he will 🙂 The issue as @claude0001 pointed out is that LOS is great when it stabilised, but pretty crazy that they immediately remove the older version as supported. A few months overlap - with security updates would be nice. Even what in the broad perspective can be seen as minor bugs, can be crucial for others, so some overlap where people can jump back waiting for a fix (even if it requires a wipe) would be nice. Or simply be hesitant in upgrading until those of us not dependant on it has stumbled on the bugs, and can report if&when they are fixed. I can fully u
    3 points
  43. ...As long as we avoid HDR mode, yes. Currently HDR works with the stock app, but not trough the api with other apps. Be aware that the HDR mode does not work as intended. It do take a high and low light image as it is supposed to, but some metadata handling in the Camera2 API interface must be wrong, so when the software tries to stitch the two together, we get odd shadow-results. e.g. OpenCamera HDR works just fine on a Samsung S8, so not the app that is wrong. it must be the returned images that does not match the requested shuttertime/ISO settings. And this obviously confuses the
    3 points
  44. This didn't quite work for me. I've had my Pro 1 on the stock firmware up until today, where I installed LineageOS 18.1 20210401. I followed this guide, did the magisk hideprops config, and cleared the google play settings, but afterwards the safetynet would still not pass (even in magisk's own check). I googled a bit, and installed https://github.com/kdrag0n/safetynet-fix (downloaded + installed via magisk), then hid magisk and did the clear data/cache/reboot dance again, and afterwards safetynet passes. I also installed Google Pay and was able to set up NFC and everything seem
    3 points
  45. OK I think I managed to reproduce it. - (Optional) open slide and set phone on table (had to do this, only got 2 hands to hold camera and trigger problem, lol) - Open Calculator - Slide finger alongside the bottom of the screen (right edge when phone is open), outside of the actual touch area - Watch the Calculator go crazy It's actually along the whole edge, not just the corner. When in portrait mode, it randomly triggers the "7 8 9 Divide Backspace" row.
    3 points
  46. Sorry haven’t checked the forums of late. here is the fix: https://forums.ubports.com/topic/5699/libertine-container-manager-create-error-makedev
    3 points
  47. thanks, going to stock and back solved the issue
    3 points
  48. I don't kow if it is related to VoLTE but that is not available for me (however, the service provider supports it). Anyway, I have to turn speaker volume to lowest level and I still feel it is sometimes too loud - however, when speaker volume is higher, it can even have distorted audio because it is too loud also for the speaker (and overdriving the speaker it is generally not a good thing at all). Otherwise, there are solutions which are louder while others are relatively quiet. ...like when I have tested my Pinephone for the first time, its output (at other party) was extremely loud
    3 points
×
×
  • Create New...

Important Information

Terms