Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/23/2021 in all areas

  1. 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
    4 points
  2. 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
    3 points
  3. It works with Pro1, however, a bit more complicated to replace as it does not come together with a frame. However, as far as I have found, these displays (at Aliexpress) are not perfect, so you should expect some (mostly minor) problems like smaller or bigger blank (black surface) area at one or two corners. I have even received a display which has a relatively large black spot in a very wrong place. So, generally they are useable, but some minor problems (mostly acceptable) are exists, so it is unlikely you will receive an absolutely perfect one. I have replaced my display
    3 points
  4. With my understanding the "recovery image" for Pro1 comes together with "boot image". The "boot" is only missing in the naming of the recovery-file offered for LineageOS. The fastboot command flashes the "recovery" into "boot(_a)". That means, as long the LineageOS-recovery.img is flashed into slot A, the boot-img-part is not the right one for Ubuntu Touch (that also resides in slot A) and Ubutnu Touch wont boot up fully. It needs to have its boot.img (re)flashed into slot A. So instead of "keeping" I suggest temporarely flashing the LineageOS-recovery-image to slot A, boot into that slo
    2 points
  5. I havent tested it yet but i think updating may be possiable but not exactly easy. In theory, if you keep the lineage recovery in slot a you should be able to sideload "OTA" updates to it without loosing data but this is of course much more tedious. Additionally i would think that UBTouch would do live updates and wouldnt require a second slot. Not to sure but the update scheduale for the pro 1 isnt particulary often so ill let you know more once ive tested it. Additionally, I have been using ubtouch as my daily driver and find with a little tweaking it is pretty stable. Once yo
    2 points
  6. Good news, I heard from F(x)tec support today. Bad news, it may be months before they can ship. Really would have liked to know this sooner.
    1 point
  7. Today I found over at Twitter twitter.com/lukapanio/status/1385479765445025792 : "Nice thing, but soon (some 3 month) ABM for pro 1/x will be avalible 🙂 you will have nicy boot menu, and unlimited number if OSes" ABM seemingly stands for Android Boot Manager and it is posted by the one who has started the thread at xda forum I linked here in last December. The suggested release time comes together with the time the new Pro1 X should become available. I love the idea to boot into Maemo Leste on the Pro1 (X) every now and then (additionally to UT and LOS like now). We will hop
    1 point
  8. Exactly. You may also try Finqwerty if you would like to use other layouts fit for QWERTZ keyboard.
    1 point
  9. Lineage dose not reset the Bluetooth chip to the right RF state and UBTouch isn't able to resolve it for whatever reason. You will need to ensure Bluetooth is off in lineage before switching to UBTouch.
    1 point
  10. Well thats a much easier way to do it 🙂 Thanks for the write up mate.
    1 point
  11. Wow, that looks terrible. Seems like you should be able to add options to it according to this article? Though it mentions a three dots button, which I'm not seeing in your screenshot. This is like Windows 8 all over again, why make it huge and occupy the whole screen? The small 4 options on the side in LineageOS 16 were great.
    1 point
  12. Here is a screenshot. According to Reddit discussion the screenshot option does appear for some phones (not sure why some phones and not others), but aside from screenshots in 14.1 I remember being able to toggle DND, aeroplane mode, ring/vibrate.
    1 point
  13. First attempt in blue, second attempt on the green parts in an effort to improve it. Turns out no difference between the two. And as of today the phone is still working minus that strip.
    1 point
  14. @tdm Hello Since you're The Pro1 Developer, do you think it might be possible to add kernel support for "battery idle mode" - I mean the state with charger plugged in, when battery is charged to some level, for example 80%, but is neither charged up further nor starts discharging - phone takes energy from charger, but not from battery. There are apps that can utilize this mode to preserve battery life (i.e. ACC: https://github.com/VR-25/acc/ ACCA: https://github.com/MatteCarra/AccA). As for now, with these apps, Pro1 stops charging at given threshold, but instead of keeping this
    1 point
  15. Unfortunately I cannot tell anything new. My phone has been at F(x)tec for about a month now and I expect it to still be there for a while.
    0 points
  16. I am also having issues making contact since the beginning of March. They were very quick to respond to my request to buy a new screen and sent me an invoice and instructions. I paid that day, March 1st, and confirmed my shipping address. They responded confirming the order March 2nd and said it should ship the next week. Seven weeks later I have not received a screen and have never heard from them again. I did send e-mails on April 3rd and 14th asking for a shipping update, no reply. I started a new case this Monday, got their auto e-mail response, but nothing since
    0 points
×
×
  • Create New...

Important Information

Terms