Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/27/2020 in all areas

  1. Alright things are moving right along now... I've got the touch screen margin/deadzone implemented and a nice little settings preference for it. The display margin will not happen until later, if at all. That's much more difficult to implement and intrusive to the system (it will likely require a reboot to take effect). I'll be adding a keyboard layout setting (qwerty/qwertz) next. Then I'll see what I can do with the fingerprint reader mitigations.
    6 points
  2. Yes it would be nice with a formalised channel for this. Currently we have two threads: One for discussing and testing possible bugs and the like, and one that was supposed to have confirmed bugs... But they are not 'clean', so hard to find anything in them. There is an unofficial bug-list here that is more easy to read. But a more formalised system would certainly be to everyone's benefit....
    4 points
  3. As a preorderer I would easily pay 100€ more for no accessories but the phone itself.
    4 points
  4. This is very interesting! Are you able to reproduce the issue? If you can then maybe Pro1 is rebooting in specific situation when there is no network or the network is changing. Reboots seems to happen during traveling. It is common that there are areas without network when you are driving between cities. Similar thing might happen when you put phone to metal locker which blocks network (like a Faraday cage).
    3 points
  5. No. 1: Full TWRP support No. 2: ExFAT support for large sdcards (generally 64gb+) No. 3: to take a time out @tdm after all that hard work/support 🙂
    3 points
  6. I think it's safe to say that we're by-and-large the 'tinkering' types that enjoy spending time on an unrestricted/unlocked device even if it makes no rational sense. I like having something different. It makes me proud even if it's behind the times and absolutely flawed lol.
    3 points
  7. I suggest reading up on what Magisk does and why. With great power comes great responsibility and it doesn't sound like you exactly knew what you were doing. You can get by fine with rooting stock, but modifying the system partition for real will break delta updates as OTAs are, so even if they'd allow it, it would not be a great idea.
    3 points
  8. Poking around a bit in the touchscreen driver. Adding code for the side dead zones is trivial and it works here. Hooking it up to a sysfs node and adding a setting item in the settings app will be a bit more work, but very doable. Not sure about the fingerprint reader yet. I may implement two options: one to only activate the reader when the screen is not off and one to limit the amount of time between reads. I personally like the latter -- I love to be able to unlock the device without pressing any physical keys. But I'm not really sure exactly how to implement either of them
    3 points
  9. https://github.com/tdm/android_device_fxtec_pro1/issues/31
    2 points
  10. There is an add-on su package for Lineage. See the extras download page.
    2 points
  11. I've been working on that two weeks ago (didn't have time after that), I was still stuck at the building stage with caf sources. I'll try it this weekend without caf, maybe that's my issue.
    2 points
  12. The Tasker Profile "Edge Block" created by @elvissteinjr works really well to solve the problem with typing the top number row on the physical keyboard. You don't even have to really know how to use Tasker. Lol. I don't. Just import by tapping the Profile and scenes tabs and away you go. Has advantages over Edge Null as explained in the post, especially the not getting kicked out by Android.
    2 points
  13. For me, I have tried to check what bands my carriers support but it does not seem to be an easy task. It seems both of them currently support only B3, B7 and B20 for LTE. The provider which I don't use for data has B1 and B8 bands for 3G. The other service provider which I have 4G and mobile data, only supports B1 for 3G. Both of them have 2G as fallback (at 900/1800 MHz). Looking at coverage map, the carrier I use also for data has good coverage for 4G but fair coverage for 3G and practically full coverage at 2G. The other carrier has fair coverage for 4G but good coverage f
    2 points
  14. Now having caught up a bit 😄 "What is the maximum dead-zone that allows us to drag an icon from one screen to the next in various launchers? With Trebuchet you have to be really close before it moves over." The Microsoft launcher also has this problem of needing to be very close to the edge you have to be on the curve for it to trigger the other screen.
    2 points
  15. Erhmm did you read what we have been debating in this thread since yesterday? Just asking... 😇
    2 points
  16. With this would it be possible to have the screen size generally reduced so the curved parts are not used for display at all?
    2 points
  17. My Pro1 restarts itself when I put it into a metal locker. WiFi connected, both SIMs inserted.
    2 points
  18. Did you mean that Night Sight is slow? The whole idea behind it is to take sevaral shots and combine them to one picture. There are some algorithms that can produce geat pictures in low light. It is the "magic" behind Gcam.
    2 points
  19. Agree with both of you. Funny in that I have never referred to my phones as sliders (although they have been, or pop-up, or flip and spin, lol). I just always referred to them as tactile, or physical, landscape keyboard phones. This was perfectly descriptive, and never became confusing in conversation. Speaking to someone who isn't familiar with a Pro1 they wouldn't have a clue what a clack phone, or a clacker is and I would be afraid it would just introduce more confusion.
    2 points
  20. I take it that he is referring to a traditional slider where the screen isn't angled, but is parallel with the keyboard (a good example is my Droid 4).
    2 points
  21. I'm not saying that it is a big issue, just some lost functionality, that might be missed. There might be other issues we do not know of. Say some app that requires an edge swipe to reach the very edge, or really close by. What is the maximum dead-zone that allows us to drag an icon from one screen to the next in various launchers? With Trebuchet you have to be really close before it moves over. So I like the software-bezel idea David mentioned with completely reducing the apparent display size. Optimally an option reducing either just touch or touch+display or perhaps even a
    2 points
  22. The other reason is for aesthetics, so someone who doesn't want to see content on a curved display can have a flat display. Related to that, would be square corners, not rounded. Aesthetics are probably way down on the priority list, but just mentioning for the future. I have no idea if you have control over things like this, but the pull down menu that has all the system shortcuts in it does not fit the screen when in landscape mode with the default settings for screen size and font size. The edit and settings buttons are off screen and can barely be accessed by tapping the
    2 points
  23. You can scroll with a vertical swipe anywhere on the screen for that. The scroll bar is just a visual indicator of your position in the list. I couldn't imagine requiring the user to hit that tiny scroll bar with their finger.
    2 points
  24. I don't use LOS yet, but just contributing ideas. With the dead zones, an option to change the physical resolution that is reported to apps would also be nice. That way, edge UI elements that a null solution would make inactive can be solved for. Another to add to the list is double tap on screen to wake it. I can't remember if that is already available.
    2 points
  25. Holy crap, I finally got a2dp working. That took waaaaaaay too long, but it's working now. Next build will have it, probably tomorrow since I am a bit busy today and there's some other stuff I want to fix/add also.
    2 points
  26. When I first saw there was going to be a tilt, not straight slider, I was concerned the angle would be annoying when holding the device. I've found that isn't the case, and the angle makes it better for reading when placed on a table (like while eating alone or something). I've got much better with opening than December, but I still feel this will remain an ongoing complaint by reviewers and new users. And if there were competition, and someone walked into a phone store w/o any prior experience and compared pro¹ to any other regular slider, they'd buy the regular slider, cuz pro¹ so d
    2 points
  27. I discovered I had no assistant app set, presumably a lineage default. In the choices, one was google assistant, but another was firefox. So now my F key (assigned as meta) opens a new firefox tab (whether firefox is open already or not). Kinda neat.
    1 point
  28. "Pull Request", a convenient means of asking like "hey, take this particular change from my git repository and apply it to yours"
    1 point
  29. I have planned to try it anyway (I saw it in Tasker thread) but still not played with it.
    1 point
  30. You can check with CellMapper to which network you are currently connected. Also, I found little bit similar case from xda with Xperia M5 phone. In that case the root cause was probably a faulty battery. Perhaps some band causes peak to the power consumption when connection is weak or network changes which leads to a reboot? - https://forum.xda-developers.com/xperia-m5/help/xperia-m5-auto-shutdown-fix-temporary-t3356247 I need to drive 70km away from my home tomorrow so I am planning to put phone to wcdma only and check what happens.
    1 point
  31. Hi, about those dead zones: I would just need one on the bottom when the keyboard is open: Then my thumbs sometimes touch the screen when using the top row of keys. But it is not a big deal, so if it is easy to implement together with the usual dead zones it would be nice, but if not it is probably at the bottom of the list (or not even on it, if too complicated of if I am the only one with this problem).
    1 point
  32. I take back what I said about Open Camera and found it to not be suitable or smoothly functioning at all on my otherwise lean Pro 1. Went back to using Snapdragon until I find and install the right Google APK. The main thing in both was how slow it was to take a picture. Especially in low light, it would take as much as 4-5 seconds to shine for focus and then flash again for the actual photo. Daylight is OK but not very detailed or crisp. edit: Thank you AHunter I will try those as they will be quicker and easier to install than the Gcam APK.
    1 point
  33. Me too. The ideal dead zone control would be number of pixels to black out (turn off, reduce resolution) and number to ignore touch screen reponse on, for edge of the four edges. I mentioned this in my feature request thread in December. If this were the case, I'd turn off enough pixels on the top/bottom (landscape) to square the corners and maybe add another few pixels to ignore touch if I still bump the screen when typing numbers. Left/right sides are no issue cuz there's bezel on that side already so I wouldn't change those much, if it all. Maybe a couple pixels if it takes to
    1 point
  34. It was standard starting with Nougat, although some roms had it as early as kitkat.
    1 point
  35. It would be a SUPER elegant solution if it after a failed attempt could ignore any touches until it has been untouched for say 2secs. This would mean that grabbing or holding it would only count as one single failed attempt....
    1 point
  36. No issues with getting insurance here. Mine is covered for theft and accidental damage in and outside my home. Don't bother with online insurers, if you've got contents insurance on your dwelling have a word with your provider, they should be able to provide cover for a fraction of the cost of say Gadget Cover etc. For reference my home contents is with Barclays.
    1 point
  37. My touch screen laptop like to activate if there is wind around opening a door quickly and causing a draft will do it. Annoying when your trying to watch something! 😄
    1 point
  38. I am too lazy to get ye olde oscilloscope out of the cabinet, but I too suspect it to be electrical noise. Possibly not even from the charger itself. The ghosting only happens when the phone sits on the plastic surface of the table. IT is a height adjustable office table with a laptop and two screens on it. Maybe the table itself acts like a capacitor and the surface of the phone gets charged electrically when it is in contact with the table surface while connected to a power outlet. Oh my, so much text and I bet @[email protected] is not even struggling with ghost touches only while chargin
    1 point
  39. Or at absolute zero! I do feel your pain, however, @SchattengestaIt. My Relay 4Gs (many of them) would get to that state with the ribbon cable for the screen, and I'd have to heat them up or cool them down, depending on how they were feeling at the time. Due to the delay in getting the Pro1, and because I had exhausted my supply of spare Relay 4Gs, I finally had to acquire some ribbon cables (they are almost impossible to find now) and replace them in a couple of the phones so that I had something to get me by until my Pro1 arrived. I'm ashamed to say that did use a Pixel 1,
    1 point
  40. It only works in the fires of hell.
    1 point
  41. After using my Pro1 for a little bit, I wanted to share my Tasker profiles here. Tasker is that one app I've had bought just in case but never really used before. But on the Pro1 it turned out to be very useful to create workarounds for some of the software issues. That also means I'm pretty much a beginner when it comes to Tasker. This stuff does work on my phone, though. Not going to explain how to import these, nor do I have actually tried to import them back myself, but the files look like they contain everything needed. If problems arise, just ask. Force Landscape on Keyboard Out
    1 point
  42. Is there anyone in UK who would like to order directly from the original seller and forward few stickers to the community members (in Europe for example)? I can also use the forwarding service to Finland but I would rather pay for a community member. Also, I don't need 1600 stickers. I calculated that there are 11 or 12 stickers in Pro1 so 50-100 should be just fine for several repairs.
    1 point
  43. Which one of these two theories is more likely to explain that one unit with the upside-down 3-key, I wonder.
    1 point
  44. No no no, use the link.... It is MAGNETIC and works in either landscape or portrait....
    1 point
  45. I'm thinking of jumping in the AnySoftKeyboard code base to had that feature there too.
    1 point
  46. Although its's more of FedEX issue but I will pushing / checking with out logistics partner see if there is anything we could do to speed that up. That seems rediculous to me as well!
    1 point
  47. Oh, so we don't need any writing on them. We can just get them with blank keys and write on them with some marker that wears off after a few weeks? :-) I still have to cheat for numbers sometimes or to make sure my fingers are on the right keys sometimes, and definitely for some of the punctuation characters that aren't used as often.
    1 point
  48. I was going to say the same thing. I would have no problem if they wanted to have dynamic display technology on the top of the keys. That would also be efficient from the perspective of manufacturers, so they wouldn't have to have different hardware keys. But the keys would need to be like the ones on the Pro1, where they are staggered, rounded on top, spaces in between, rounded corners on the keys, etc. There would need to be an override to put it back to the stock keyboard in any apps where the apps decide to re-write the keyboard too (last picture). Ideally, the norm would be tha
    1 point
  49. If this is to be real keys and not just touch, it would be awesome. But why not stay staggered?
    1 point
×
×
  • Create New...

Important Information

Terms