Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/22/2023 in Posts

  1. In my case, I never parted from my dumb phone, however, I use my Pro¹-X every day. It's my ultra-portable laptop in which I do all sorts of stuff. I believe I open that keyboard a few dozens of times per day on weekdays and a few on weekends. Given claude001's answer, I think I'm lucky that the keyboard still works perfectly. When I reach 1 year, I will certainly write my 1 year review of my experience with my Pro¹-X. My dumb phone is mostly used for calls and SMS. Pro¹-X's call sound quality is fine but for me, my dumb phone is more reliable to not run out of battery when I most wan
    4 points
  2. I've been doing this with both my Pro 1 and now my Pro1x for years. I do home health care for my wife so my "phone" phone has to be flawless. I don't do a lot of calling and texting, but I'm the front office for doctors and insurance so when I need it, I need it perfect, I find it little trouble to carry two devices (and the cheap phone makes a great hotspot). I sometimes feel that while complaints about the call performance are understandable, people overlook what a fantastic pocket computer it is. It really has meant my laptops stay home, even if I'm traveling for a week. As far a
    3 points
  3. I may be on the other end of the opinions here. I use my Pro1 as a phone since around two years now and it was always a pleasure. I dropped it many times and every corner is damaged but the screen and phone works fine. I type excessively and fast (+300 keystrokes/minute) and the keyboard still works fine. I even melted some keyboard buttons on the right part when trying to change the usb port as I forgot that there was another side of the phone (you can easily get out the usb port pcb). But it works fine. I removed my fingerprint sensor and added a secondary usb port and... since I use
    1 point
  4. Unfortunately many are still waiting, some that bought years before you...
    1 point
  5. This sounds a bit low, how many hours of screen on does that include? If not many hours of screen time a day, you might want to install some helper program (e.g. GSAM or 3C toolbox) to find out where the energy are wasted. Could well be an app that is the culprit. When idle it should burn less than 0.5% per hour. On the other hand with screen on, it can be 10%/hour and even worse if doing something hard. Especially be aware of 'free' apps, the ad's can waste a surprisingly large amount of battery, and thus be a double nuisance.... Some of the apps calling home to deliver the data th
    1 point
  6. I have this problem sometimes but I think it's caused by ACC. It appears like there's some bugs in the custom android kernel which doesn't like when some of the settings inside /sys are used. I'm still probing because this only happens to me many hours after I start charging. However, if you have root permissions, this script works well for me: echo 1 > /sys/class/power_supply/battery/input_current_limited echo 0 > /sys/class/power_supply/battery/input_suspend echo 2 > /sys/class/power_supply/battery/charge_control_limit I appear to only need it if I have the phone connect
    1 point
  7. @Hook@EskeRahn thanks for the pointers, I'll give it a go Edit: Connected to pc via adb, ran: adb shell pm uninstall -k --user 0 com.android.cellbroadcastreceiver.module adb shell pm uninstall -k --user 0 com.android.cellbroadcastservice adb shell pm uninstall -k --user 0 com.android.cellbroadcastreceiver and the obnoxious mosquito has gone. Didn't need root, still good after a reboot and an update. Hopefully that's the end of it.
    1 point
  8. The first photo doesn't include the usb port. There's not much room behind the usb port (I'd say 3-4mm), we would need 17mm. The connector and wifi (?) cable are both in the way. The only way I see this happen would be to completely get rid of the usb port and add a second one around the fingerprint sensor like I did here. I never used my stock usb port anymore so it's not impossible. But is it really worth the effort to completely remove your main usb port, wire up a secondary port on the side of your phone only to gain gain up to 600mAh (17.5%) to the second best battery option? My i
    1 point
  9. Settings, Notifications, tap wireless emergency alerts.
    1 point
  10. Yes, it makes the app believe that the phone is not rooted
    1 point
  11. Thanks @Slion not the least for your Fx Service v0.4.0 that I benefit from many many times a day, with a magnet in the flip cover to lock the device. Very very handy. 😁 (Yes I know there are later versions with more functionalities - not even using all the functionality of the early one)
    1 point
  12. Thanks for your early development efforts for the Pro1. I still use Fulguris as a fast and efficient browser (alongside Firefox, which I keep just for access to my desktop bookmarks when I need one).
    1 point
  13. Charging-only mode is part of Android, so the phone must be able to boot the high-level OS to charge. When you connect a power source, it will always start the Android boot process. If the off-mode-charge flag is set, it will start the charger program instead of the full Android UI. Yep, you triggered the "battery protection bug". The problem is in the closed-source firmware, and relates to the PMC configuration. LineageOS doesn't have licenses for this source code, so we need F(x)tec to fix it. The only way to avoid it is to periodically charge your Pro1 X, and once a month should be
    1 point
  14. To be fair, the Pro1-X was initially quite close to that same idea. At the start of the IGG campaign, the Pro1 not only existed, but had been field-tested by quite a few customers already. The alternative OS's -- then the "big thing" about the Pro1-X -- were already available in either rock-solid (LineageOS) or beta-quality (UBTouch) form. Yes, you could add more memory and get a shiny blue body with custom engraving. But no one really expected any showstoppers there, given that the phone would technically remain a Pro1. In my view, the Pro1-X campaign was initially intended purely
    1 point
  15. Well they sort of did things the other way round. They produced the device, to a stage where they only needed to know how many they should produce, before going for crowdfunding. A bit unusual, but obviously crowdfunding can be used as a pure sales channel too. How they managed to ship it I do not know, My GUESS is it is/was easier for a Chinese company to ship out, than for foreign companies? But just my guess. Also remember that personal contacts is very important for Chinese deals to go forward, and as people was prohibited from going in from abroad, neither FxTec nor Planet could meet
    1 point
  16. This morning after about two and a half years I put back my primary SIMs in my Huawei P30 Pro. The main reason being I have hardly ever used the keyboard since I upgraded to Lineage OS back in late summer 2021. I used my own custom ROM with a few patches for the keyboard, lower brightness and darker Eye Comfort options. Together with Google Play and Magisk for better full screen gesture support. As someone who has to jungle with French, German and English languages the keyboard needs some extra customization for optimal use. I had a nice keyboard setup on the official Android 9 but never
    0 points
  17. Purchased 2 units on April 19, 2022 but still waiting for delivery. If there's already a thread for this please feel free to move this or point me to it. Thanks!
    0 points
  18. 20 hours before my flight, finally everything up and running. The screen flickers and dies on me 😑. I shit you not. Whn I press the power button the screen flashes yellow and that's it. Bye bye Pro1, back to FxTec you go 🤕.
    0 points
  19. You can try the following commands (from telegram) to get the camera working: Just executed two commands and voila: camera works again $ adb shell setprop vendor.debug.camera.eisv3enable 1 $ adb shell killall -9 [email protected]_64 I had even transport apps simply crash (on opening the account/tickets view) when the safety net check failed.
    0 points
  20. I had been suspecting this was the case for some time now. Thanks for clarifying. This means that off-mode-charging cannot actually protect us from the battery depletion bug. If the battery is flat, it's game over, irrespective of the off-mode-charge setting. Thanks, it is clear to me that LineageOS cannot fix those bits. Does anyone know whether F(x)tec actually have the sources? I.e. can they fix these things in house or do they rely on some external software company for maintaining the stock OS and its drivers?
    0 points
×
×
  • Create New...

Important Information

Terms