Jump to content

pistikem

Members
  • Content Count

    53
  • Joined

  • Last visited

Community Reputation

64 Excellent

Recent Profile Visitors

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

  1. i wrote - like others too - a few months ago a few words about my experience with the Snakehive wallet, see here and here. so far i am pretty happy with the result, no major complains about this new wallet & case (TIYA P20 Pro TPU) combination.
  2. i just replaced my screen a few days ago - wasn't hard at all, see here. i followed for that TeZdevice's advice here. you can do it in less tan half an hour. my screen & digitizer worked thereafter flawlessly. the reboot also brought back some sound effects such as the glang when charging - which implies that Android isn't as stable as a full-fledged unix box. my linux-based Nokia N900 was rock-stable and robust with uptimes up to a year or so...
  3. TeZtdevice, your advice was greatly appreciated - i replaced the original screen of my Pro1 and the new screen works flawlessly, or let's say, the upper 1/6 part of the screen started to be responsive again ! that's fantastic because apps like SONOS or FOTOS cannot be rotated and do not allow landscape mode. now i am able to reach reach again the apps' settings buttons. of course i also very much appreciate Fxtec's support service that sent me this replacement part for free !
  4. does anybody know where to get the HOWTO video shows from that will explain how to replace the Pro1's screen ? i just received a new screen by mail (see here) which should fix the problem i describe in the above post.
  5. i first wrote to Fxtec 2020-02-15, got a first answer 4 days later, was asked 2020-02-24 if i preferred a new screen to install myself or a repair service with Fxtec, and was confirmed 2020-02-26 to receive a new screen in the coming weeks - which arrived indeed yesterday, after all this covid hassle. so i am perfectly happy with their service. now i only need the video HOWTO to replace the Pro1 screen... ADDON : issue of switching screens solved : see here
  6. perhaps you only need a new screen digitizer - see here and here ! by the way, that's quite a coincidence, i just received today two hours ago a new back part for the phone base which i suppose holds that digitizer parts that malfunction in my Pro1. with phone base i mean the part that holds the keyboard. anyway, now i need to get that video with the instructions how to replace the faulty piece with this new one. will keep you posted... CORRECTION : i actually had received last night the screen part from the Fxtec support team ! now i just need their HOWTO video ...
  7. 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 !
  8. 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...
  9. 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.
  10. 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
  11. 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 !
  12. 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.
  13. 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...
  14. 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 !
  15. 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...
×
×
  • Create New...

Important Information

Terms