Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/08/2021 in all areas

  1. Got my Titan Pocket today! I will try it as my main phone for a while and see how I like it, I really lile that it is smaller than the pro1 and I actually prefer that style of keyboard (can reach entire keyboard and operate the phone one handed easily).
    5 points
  2. Sure, its their choice. And I fully understand that Lineage is not in the position to lead Android development and force Google to adapt. Still, I feel like this is the end of the road for me. (Edit: And I am very thankful for the work everyone has done with LineageOS! Lineage is clearly the better Android, and they rescued countless devices from an early obsolescence.) (Warning: Old-man-rant approaching!) Google's choice to develop Android the way they did made sense, back in the olden days. But they quickly gained marked shares, followed by absolute power. Despite that, they contin
    4 points
  3. That looks correct. Here is a current link onAlieExpress: https://www.aliexpress.com/item/32956500815.html
    3 points
  4. Yeah, I've had to do changes in Fulguris for that stuff. What's nice though is that you can support any kind of Cloud storage through those APIs. It's totally transparent for the app developer which is pretty awesome I find. For instance where before in Fulguris you could do only local backup now you can manage Cloud backup in the same way.
    3 points
  5. Beloved community, here it is: Another up-to-date outdated ROM to satisfy your custom ROM fetish. LineageOS 17.1 JeBB "A noble spirit embiggens the smallest man!" is (so far) a slightly modified build that will be updated in irregular intervals. Future builds may contain additional fixes, or I may attempt to fix things with a Magisk module ... "may" is the important word here 😉 This build can be installed from scratch like any LineageOS build (LineageOS Wiki). Dirty-flashing from the last official LineageOS 17.1 is possible, but the official signature keys have to be exch
    2 points
  6. Good idea for a phone. Since i prefer buttons when using technology privately rather than touch and touch
    2 points
  7. SD-cards are still working in Android 11. The difference is that apps are forced to use Scoped Storage exclusively. From November 2021, targeting Android 10 to circumvent the Scoped Storage API will be forbidden. This means that direct file access is impossible. Every file access has to be routed through Scoped Storage. The point is to prevent apps from accessing data on the SD-card they are not supposed to access. And it is supposed to reduce clutter. So, instead of using an appropriate file system for SD-cards (like F2FS or ext4 without journaling), Google introduced a high level "file
    2 points
  8. https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/315360 - this was merged - we missed one conversion from 44 -> 2c, the value mismatch caused the powerhal to crash. Issue is remediated.
    2 points
  9. You can, with fastboot. fastboot --set-active=a
    2 points
  10. Google and Lineage are going the wrong way, making things too "secure" and "fool proof". Root and SD-cards are a good example of the things the future won't hold. I feel that power-users have to bend over backwards to use their devices the way they want. So that's what I did. I bent over backwards ... and gave birth to an old-timer 🤰👴 😁
    2 points
  11. Changelog 20211025: New build with Android security patch level 05.10.2021. No other changes.
    2 points
  12. I bought an old house some ten years ago, and found out that part of the insulation used in walls and ceiling was a sheet of metal foil, so to a large extent I live in a Faraday's cage. Thus I can not use my WiFi in the garden - no big deal for me, but a big surprise for many guests. So it was no surprise to me that none of my phones have been able to get an indoor gps fix. (Except when standing under the passage to the attic) The big surprise is that the Titan gets a fix indoor, and with 3-4m accuracy!! (2m under the passage)
    1 point
  13. Now that custom keymaps are working, you can remap the 'up arrow' key to '/', with Android handling shift+'/' -> '?' with the following: 04:0035:0067 I chose to remap Fn+'/' to 'up arrow' so you can still use that, but it overwrites the default keycode of 'page up'. That's the '0067' part in the string above, where 'page up' would be '0068'
    1 point
  14. Anyway, I had the same feeling after switching to Pro1 from Moto G6, however, I wasn't satisfied with G6's GNSS generally. If Titan is even better then it should be definitively good in this area.
    1 point
  15. Getting sick of waiting on Fx to send me my replacement, might just order via a friend from China directly. Does this look like the right screen? 大象Elephone U U Pro屏幕总成 Amoled elephone u upro E9002-淘宝网 (taobao.com)
    1 point
  16. Yes, that is how I have installed Magisk.
    1 point
  17. ok I just remember, I have installed Magisk via the .apk, this mean, if I reinstall Magisk via sideload it will do the trick ? (If I understant correctly, magisk.apk could also be magisk.zip, I've just to rename it and sideload via adb).
    1 point
  18. My results are the same as @Rob. S. No need to reflash either Magisk (used for SU only) or Gapps after OTA.
    1 point
  19. Really ? since LOS17 I have to flash magisk at every OTA update. For Gapps I never reflash it. edit : to clarify the whole things, this mean A/B slots are just for wiping partitions, (like a "transfer") but there are many slots, physically talking ? and so the priority order when flashing roms, Gapps, Magisk, etc... decide if it will be persistent on next update ?
    1 point
  20. Seems like they indeed fixed it and somehow without reverting those changes. I wish someone could explain that to us. My latest build is real smooth.
    1 point
  21. Very good point, I'm just like you, trying to understand and learn.
    1 point
  22. I don't know since I always just went ahead and reflahed Gapps and Magisk when I was sideloading because it was easy. But tdm indicated that you shouldn't need to in his instructions for LOS 16 (though he noted some said it didn't work). And why does both Gapps and Magisk persist after OTAs? Just asking questions because I'd like to learn.
    1 point
  23. They have good intentions and a great product (hardware-wise), however: They SERIOUSLY need to work on their public relations. It really needs a STRONG improvement. @Erik! That guy is at a mess and He desperately NEEDS YOUR HELP!
    1 point
  24. Interesting. I have compiled it on a chrooted Ubuntu environment earlier and now I have checked relevant packages were not upgraded since then. I have not tried yet to compile the very latest version of Pro1-related codes anyway. Maybe - are you sure you have enough free space on the partition where this compile runs?
    1 point
  25. (lineage-18.1-20210906-nightly-pro1-signed.zip on August 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.
    1 point
  26. Just wanted to provide links to source files that makes our Pro¹ keyboard. That can be used as reference for anyone wanting to understand and customise Pro¹ keyboard experience by building Lineage OS. From low to high level files we have identified the followings key components: Device Tree Structure Include, contains GPIO pin mapping to scan codes: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/lineage-18.1/arch/arm/boot/dts/qcom/msm8998-qrd-skuk-t5.dtsi Permalink Driver, brings together GPIO and aw9523b controller input to define the scan codes sent to user space: h
    1 point
  27. "Mainline" refers to using the upstream Linux kernel with open-source drivers. That's what I think Mobian does. To this date (and to my knowledge), there is no OS for the Pro1 that uses upstream Linux. All available systems use the vendor-supplied Linux kernel of Android 9 ("4.4.153-perf+") with the proprietary (and closed-source) device drivers. That includes UbuntuTouch and SailfishOS! The latter actually run a slimmed-down version of Android 9 in a container and access the hardware via Android compatibility layers (libhybris). I suspect the situation will be quite similar for the Pro1
    1 point
  28. Well, in that case there is really no need to go for a Pro1(X). The built-in keyboard is pretty much the defining feature of the device. If you're going to use a separate keyboard anyway, you'll find devices that are cheaper while having better mainline Linux support. Running GNU/Linux in a [ch,p]root of Android takes care of that. Networking is managed by Android and just works (tm) in the chroot system. For Termux, there are even extensions to use the Android location services from within GNU/Linux-programs. But, yes, UbuntuTouch can also be a solution (although GPS does not seem to
    1 point
  29. I bought myself a Jelly 2 from Amazon. I went straight to LoS 18.1 from meetoul. If you're looking for a compact smartphone 4" screen and have good eyesight, I highly recommend this little gem. LoS 18.1 works like a charm, except for drainage. The battere depletes in 24 hours no matter what you do (or don't). Typing is bi!@#$ of course. Still no response from FxTec regarding my RMA. At least for now, I'm covered.
    1 point
  30. This is an ancient thread, but I might just as well add that this thread: and my recent update for LineageOS 18.1: ... details a relatively easy way to install and configure Pro¹ devices to use AICP or LineageOS so that Netflix and Disney Plus apps do appear in the Play Store and can be installed normally; also Google Pay works for contactless payment with the smartphone at the supermarket counter (which over here is the only real method to make sure you don't need to touch that keypad)...
    1 point
  31. Just to follow up on this, before it becomes forgotten – my Pro1 is as good as new again, thanks to @EvilDragon!
    1 point
  32. I'm like you yes. I think the pro1 is excellent, it has the portrait full keyboard I desperately wanted, and it is the only one. But a bit too big. To me the best size was the Droid4, I could easily reach the center of the keyboard with my thumbs. Nothing is perfect, and regarding my wishes, the pro1 is by far the best option.
    1 point
  33. I completely agree. I don't think anyone here tries to defend IGG. I think the whole concept of Crowdfunding for perks is a really bad deal for the consumer. It probably should be regulated more. So please be angry at IGG, but not at fxtec. And do not try to ruin them, call your local politician and complain about crowdfunding or whatever. But don't try to damage a company which is in my opinion in a position, where crowdfunding is not too unethical!
    1 point
  34. I think the main issue is that while crowdfunding is NOT the same as a purchase, it FEELS like a regular purchase. https://wp.josh.com/2014/01/21/read-this-before-you-contribute-to-an-indiegogo-campaign/ The blog post lists some complaints about how IGG tries to make the experience of crowdfunding similar to that of shopping despite attempting to avoid the legal obligations of normal ecommerce sites. So I'm sure plenty of people who are crowdfunding for the first time are easily swayed into thinking that they are guaranteed to receive a product. Now you can call them naive and
    1 point
  35. @Doktor Oswaldo I can not thank you enough for a well balanced post! I totally agree on all points. I think that much of the commotion arises out of people not being able to distinguish between making a pre-order and taking a crowd-funding perk. Foreigners like me could start by usign a dictionary: Perk Though IGG tries to scream out in large letters that perks aren't pre-orders, unfortunately the campaigns I've seen (including this one) are formulated in such an optimistic way as if it was a sure thing that we will end where they hope we will, and that we will get exactly what
    1 point
  36. Well since this feels a bit like Fanboys defending, I think it is important to state at @PsyDucky that we all have been through this. We all agree that communication is not the best, we all agree that it is hard to know anything for sure, since a lot of unofficial information pours in, while official is missing. But in this case, they stated relatively clearly, what happened and why. Yeah there are some Information missing, like HDMI out. But you know what? I am pretty certain they don't know yet. They haven't redesigned the thing yet! Community asked if it will do HDMI out, so they asked
    1 point
  37. So I contacted FxTec on the 21st of July. I got a response on the 13th of August, asking if I could re-connect the flat cable/ connector and take pictures from all corners (guess to prove It hadn't been dropped). Today it's August the 8th. Still no response. I have swapped the display with a (damaged) spare to no avail. They really need to take a look at the phone. I'm pretty sure there is something wrong with either the flat cable or the connector on the mainboard and not the display. I wouldn't be surprised if my Pro1x gets delivered earlier than my Pro1 gets repaired and delivered
    0 points
  38. What about the camera modules? I have asked Fxtec to get a warranty replacement for my camera module (due to focus issue), but I don't feel very confident on getting that module very soon. So I wonder if I could source a replacement module on my own. edit: looks like the Pro1 camera module (IMX363) is not available on Aliexpress. The Pro1-X module (IMX586) is there at least. I couldn't find the IMX363 from Google either, so looks like it is already too old technology? Also I am not sure if it is the actual camera module which needs replacement, or is it the smaller, assisting modul
    0 points
×
×
  • Create New...

Important Information

Terms