Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

57 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. regarding hardware issues : i am experiencing trouble with the screen digitizer (see an earlier quote of mine and others' too) and then with that infamous fingerprint reader, again as others... the fingerprint scanner and the associated software work essentially at random, i have no clue how to improve hit rate... otherwise i am more than happy with the Pro1 - but i am at the same eagerly awaiting an OS update too !
  2. i also had and still have an annoying screen digitizer problem (see my post in this forum), and was promised a while ago a replacement screen - which i assume should at some point arrive after all the global viral troubles are settled...
  3. in my case jmtpfs was extremely slow too, but only with an old Android version, v4 i believe. now, having two Android 9 phones (Samsung A10e and Fxtec Pro1) transfer speeds and access are lightning fast under jmtpfs and the very same version(!) - to my surprise i must admit. in contrast, my old N900 was on my host usually mounted as /dev/sd?1 (? being b,c or whatever) - that worked perfectly fine too.
  4. i use Slackware linux - depending on your linux flavor things may look a bit different. 1) you need to install jmtpfs on your linux box. in my case it's v0.5 2) add yourself to the uucp group : /etc/group : uucp:x:14:uucp,YourUserName 3) /etc/udev/rules.d/51-android.rules : SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0660", GROUP="uucp", ENV{ID_MTP_DEVICE}="1", SYMLINK+="libmtp" 4) as root, do : udevadm control --reload 5) mkdir ~/mtp ; jmtpfs ~/mtp/ ; 6) do your copy/move/delete jobs... 7) fusermount -u ~/mtp
  5. oops, you are right, tdm, i should have specified who owns root here, sorry about that ! i meant root on the host (and i did not yet need to be root on the phone). you are most probably right regarding the udev rules and i googled similar notes elsewhere on the web. interestingly jmtpf worked over the last few worked for the "PTP"-mode - but as i started to play also with the "File transfer" mode it broke my previous access to the phone photo data. so neither access worked for me as regular user as of today but for root both worked just fine. anyway, i assume the number will be the following : vid=18d1 pid=4ee2, taken from the CLI output "Device 0 (VID=18d1 and PID=4ee2) is a Google Inc Nexus/Pixel (MTP+ADB)". and this seems to be indeed the case, as it started to work just a minute ago ! first i had to add myself to the uucp group. then my 51-android.rules looks now the following way : SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0660", GROUP="uucp", ENV{ID_MTP_DEVICE}="1", SYMLINK+="libmtp" many thanks, tdm, for your suggestion !
  6. how do linux users access the Pro1 data directories using the "File Transfer"-mode with the USB port ? i don't mean the MTP-mode, that will only show camera data. i used mtpfs and lately jmtpfs on various Android phones successfully - but on the Pro1 specifically i succeed only as root to do so, and not as regular user like on the other phones. bizarre, right ? for the linux fanatics : i use Slackware -current.
  7. i am not sure if i mentioned it already in this forum (my search before didn't help) but i experienced some two weeks ago the very same problem as alexmarzulli did in that the upper 16% or so of the screen became unresponsive to touch, out of the blue, for no clear reason. i used the built-in factory test mode which revealed that the area of the last two upper rows with red circles are indeed unresponsive to touch as i can't erase them like the others lower down : i contacted Fxtec and they promised me a replacement screen in the coming weeks - see my recent post in this forum. obviously it's at times pretty inconvenient as i need to rotate the Pro1 allover the place which can be even more tricky when i use the keyboard with some apps while the settings buttons are usually located to the very left (in landscape mode, very top in portrait mode). anyway, one manages somehow...
  8. i had to ask Fxtec recently to replace my screen (i suggested to pay for it) because the upper 16% became unresponsive to touch after which they promised to send me for free a replacement screen & installation video within in a few weeks. i was quite happy with their response and added to my response letter to Fxtex the following few lines : i have my own experience (a little bit) what it means to start a company : it's incredibly and painfully difficult and one also needs a (metric) ton of unpredictable luck for that - all my kudos to Fxtec !
  9. regarding LED lights for incoming SMS i realized the following thing : messages sent to my mobile number as regular SMS do *NOT* elicit any LED activity, or just a short little green blip. however, when messages are sent to my mobile phone SMS address as email such as [email protected] then a beautiful green light starts blinking regularly and right away, together with sound and vibration. i need to point out that this email address get forwarded by Bell to my gmail address. so this fact may perhaps facilitate something googly inside the Android OS ? importantly, i don't read email at all directly on my Pro1 but remotely on a server via vpn/ssh/alpine. the only app i have installed and currently active is "VolumeControl" to separately control the volume for incoming phone calls vs txt messages - though it's somewhat useless and i may remove this app altogether - just like so many other apps i tried for the LED business, for volume control, rotation control etc. the only useful app so far is EdgeNull for me. regarding missed calls - i don't know (yet) much about the response pattern of the LEDs - seems somewhat erratic anyway...
  10. by the way, and unrelated to LED lights, how do i crank up the volume for arriving messages to make the associated notification sound noticeable ? i know how to change the sound file - but how to play it much louder so i hear it on a busy street ?
  11. separating the TPU housing from the Snakehive leather is pretty easy and straightforward : detach it slowly, help with your finger tip, so you don't rupture the thin leather sheet. you may first want to remove that thin black foil attached to the inner side of the TPU case. that way you see what you do underneath the TPU when detaching it from the leather. tape : i bought double-sided sticky carpet tape but ultimately refrained from using it as i was afraid i can't separate it later from the leather. glue : i went with the glue solution which worked flawlessly. i guess they have a similar approach at Snakehive. i bought a few ml of 'flexible plastic glue' by LePage/Henkel which sticks to all kind of soft plastics as well as leather and more, just anything it looks. it smells like Cementit we had used as children years ago. i pressed the parts together after some 20min of drying, then left the phone overnight inserted in the TPU housing and a layer of cloth wrapped around the Snakehive so to evenly distribute the pressure of a few books i used as weight. results looks and feels perfect. TPU holes : i cut this time only four holes into that TIYA P20Pro housing : 0) for the headphone jack, 1) enlarged the adjacent speaker aperture, 2) for the USB-C opening, and finally 3) for the fingerprint reader an oval hole, leaving the upper rim of the TPU case intact and sturdy so it holds the Pro1 more safely.
  12. like others i bought a Snakehive P20 Pro leather case but it didn't hold my Pro1 safely. i exchanged the original TPU holder with a TIYA P20 Pro TPU case which fits the Pro1 much better. one still needs to cut a hole or two into the TPU. importantly, opening the keyboard is now much easier, a klacks :) now i just need to find the right glue to bind the TPU plastic to the Snakehive leather case. i would refrain from the Spigen P20 Pro hybrid case - it just doesn't fit the Pro1, is too hard, too tight and too deep so that opening of the keyboard becomes a nightmare.
  13. yes, that was the case - i couldn't get those LEDs to shine with any app last week. but now, as i used this built-in device test, a re-installation of LightManager2 did the job finally. klick on the three bars at the left top and chose accordingly. unfortunately, additional device tests confirmed also that my Pro1's screen's upper two rows truly became unresponsive to touch. this after just two weeks of usage... i didn't hear yet back from Fxtec support. i contacted them via their web form. CORRECTION : things are again dead since this morning !!! just like last week, the notification LEDs stay pitch-black, no activity whatsoever after missed calls or SMS messages. obviously i didn't change anything over night during sleep. something else must resetting settings & permissions. Android looks to me like a windows box, no comparison to a rock-solid unix system...
  14. thank you, EskeRahn, the sub-LED test worked just fine, all three colors, that's reassuring - but as observed by others, the notification system for messages and phone calls seems to dead, sadly. perhaps a future software upgrade will help here. or an Fxtec-supported Android 10 install, if/when available ? ADDENDUM : Light Manager 2 finally started to work as described here in this forum (which wasn't the case for me earlier). i guess my recent manipulations with this sub-LED test did something to some permission settings, and now my calls/SMS/etc get their LED spot light attention, finally ! and incoming SMSs are getting now their acoustic backing too...
  15. same issue here - charging the Pro1 means the LED is green most of the time, but at times it begins red then turns green - which depends on our local weather forecast i guess. i never got it running to indicate missed calls, SMSs and so on. that's truly sad, i miss this feature terribly - it beautifully worked even on my 10y old Nokia N900... by the way, did anybody get sound working for incoming SMS messages ?
  • Create New...

Important Information