Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/23/2021 in Posts

  1. There have been rumblings of starting official release builds, so I'm guessing in the next couple weeks.
    5 points
  2. I read Fxtec was accepting suggestions for new keyboard layouts. Has anyone suggested a blank keyboard layout? That way you can remap keys however you want without having to worry about letters matching up And you don't have to worry about letters fading over time
    1 point
  3. 1 point
  4. I've not had a problem with the OTA udates. But I'm still on 16 so not updated in ages waiting for 18 😄
    1 point
  5. You have to go with a flat plate along the flat cable into the housing and try to open it with small tilting moves. At some point it will open and it splits. Cable is pretty stable and I did it already 3 times but neverhteless be carefull. You can also use a small screwdriver. But thats one of the reasons why I bought 3 of the Nillkin 😁 And just to make it clear: I only removed the housing on the top - not the housing which goes in the USB port.
    1 point
  6. Tested out Nilkin and MyMax Qi Receivers. Both work well, albeit slow charging. MyMax: https://www.amazon.com/gp/product/B07XD75XY3/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1
    1 point
  7. Yeah but the cool thing with tasker is the auto adjust on situation, I made one more task when the phone connects to my car Bluetooth everything is bigger and it start music too. For the OP I can understand the idea the phone act a lot more like it should. In portrait or landscape the size is normal and there is no special needs to be precise on touch on the screen. Then when you need more productivity and get that keyboard out everything follow for the time you need it and get back to normal when it close. I'm probably getting old on this and don't want my phone up to my face ever
    1 point
  8. Had that with every OTA so far. But I can't tell you if it's a reason to worry. At least I never had any problems.
    1 point
  9. yoy can just go to devoloper settings and change dpi there towards the bottom... i have mine on 580
    1 point
  10. any wod of an update to AICP R ?? :))
    1 point
  11. Just to make it more clear: I don´t think the charging pad is important if it loads or not. I am also using it in the car with an quite old one and it works. Other pads I am using are 10w no name pads from a local electronic store. Works too. I don´t think the loading pad is important - the receiver is more important. And the only one that is working (and I tried already 3 of them as I wanted to have replacement parts) is the Nillkin.
    1 point
  12. Yes it is two different issues. One is something gotten loose or worn, the last should be unlikely this soon. For the loose I too would check the screws as the first guess. Another is that the support-arm when closed are free, and thus can rattle a little if you shake the device, a tiny piece of ½-1mm thick self-adhesive rubber or felt can be placed in the 'groove' for it. to inhibit its movement.
    1 point
  13. I would contend software optimization will matter more than outright processor power - at least for actual use scenarios. I hope that gap is filled. But we've hoped a lot since this started Also, @fxtec STOP giving time estimates. Just do periodic updates.
    1 point
  14. It is sad indeed. But as I see it they had very few alternatives after being swindled. Redesign the Pro1(x) using as much as they can of the existing with the remaining money. Await the months or years a trial may take, and hope they win, and HOPE they can buy and stock whatever 835 they could find (if any!), and then have someone making the pcbs if they win - a high risk gamble, and the device would likely be quite outdated then, and no income while you and others were waiting. Start the development of a totally new Pro2, my guess would be it would reach us after 2021. and m
    1 point
  15. So what I'm seeing is, the device I purchased in February 2020, which I have never received, is now going to be a different device than I purchased. I love waiting on stuff that's going to be slow and outdated by the time I get it, just to find out it will be even slower than before and a year later.
    1 point
  16. Just when I was prepared to wait another six or more months for the Pro¹ (or now rather Pro¹ X) I had ordered in September 2019, now I got lucky – and my hands on a used device! It came with (non-rooted) LineageOS 17.1 (February 15 update installed like a charm from within the system menu) and all the apps I need work, even banking and the health insurer's app (and Netflix via APK), except only one, the "Entrust IdentityGuard Mobile Softtoken" app for connecting to my employer's VPN from the home office. For the time being, I guess I'll just keep my old phone lying on my desk.
    1 point
  17. Now that I finally got a phone, I can confirm that the Brodit 711042 doesn't quite accommodate the thickness of the device (and just holding the keyboard part with it doesn't really work, either), so I got a 511307 and it's good indeed!
    1 point
  18. YES! It snapped! And now there's normal call audio... Best thing is, it isn't even as loud as I feared. Sounds as if it was low enough even for the workplace, whenever I'll return there. All good! (Why can't I give you a 'thanks' and a 'like'? 😉) __________ While I was following this forum, I thought when I would have read about all the issues and hints and tricks and solutions and workarounds, I would immediately know what to do when something would occur with my phone-to-be. Far from it! I've already forgotten even what was discussed quite recently...
    1 point
  19. OTA updater crashed during 20210222 update. Most likely file was corrupted, after reboot it shows 20210222 version and no need to update. OS is not crashing at all. Should I be worried?
    0 points
×
×
  • Create New...

Important Information

Terms