pistikem
-
Content Count
70 -
Joined
-
Last visited
-
Days Won
3
Everything posted by pistikem
-
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.
-
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
-
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 th
-
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.
-
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. ob
- 11 replies
-
- 4
-
-
-
- touch screen
- digitizer
- (and 1 more)
-
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 !
-
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 a
-
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 ?
-
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
-
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.
-
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 notifi
-
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, fi
-
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 ?
-
i am not sure where to post this - but as it's related to production, and perhaps a new phone, i am going to post this here : unfortunately, my 2-weeks old Pro1 broke last night : the upper 6th (some 16%) of the screen turned suddenly insensitive to touch. i can't pull down that top menu nor the subsequent second menu bar. i removed the protective foil, warm-rebooted, cold-rebooted, cursed and so on, w/o any prevail. now, in landscape mode, things at the top (the long edge of the screen) work again - but at the physical screen top, the one close to the phone speaker and the front camer
-
Help show your Pro1/Pro1X to others close by
pistikem replied to EskeRahn's topic in Pro1 - Thoughts & questions
Canada, Québec, Montréal -
CORRECTION #2 : testing the indicator LED actually worked just once, for missed phone calls - now it doesn't make a blink, nada. i suppose the Android permission settings in my Pro1 don't suit the requirements for the Light Manager 2 app. oh man, how much do i miss the CLI - there at least i know what and when i do something wrong... is there any other app out there that could help here ? HOPPALAH ! the LED is now blinking yellowish and greenish alternatingly, perhaps some 10min after i had started the last test ! there is even some red in the light. as you say, VaZso, a light d
-
no luck so far, EskeRahn, though thank you for your suggestion. i run Light Manager 2 in 'normal' and in 'alternating' mode, wait for seconds and seconds, without any lack, no LED activity whatsoever. only the 'screen mode' works, on the OLED obviously. but i also observed that the app doesn't show anymore its transparent three-ring logo/icon at the left top, for whatever reason... does that mean something ? CORRECTION : green light (associated with missed calls) works - but not for any of the other services nor colors...even when i set a service' color to green for example...
-
which app do you speak about, EskeRahn ? i tried LightManager 2 but not much happens, actually no change at all. also the app-built-in tests to make the LEDs shine doesn't work. i assume i don't need root access, correct ? i even rebooted the pro1 w/o success, no LEDs lighting up... which is the most suitable app to get the LEDs running for regular notifications such as SMS or missed calls ? i currently don't care much about the green charging LED, but i would like the LEDs help with my daily work flow.
-
ok, folks, i got my Pro1 an hour ago today, in Montréal Canada, featuring S/N 711. very nice piece of heavy duty material, feels like metal, feels like a Leica M. my Nokia N900 is still operational after 10 years but feels so small and a bit cheap too, as compared to this new FxTec. anyway, let me now start setting it up, then register it with Bell, get a SIM card etc, then install openVPN and Termux and so on...
-
regarding Canadian import taxes, see here : https://community.fxtec.com/topic/2463-got-your-pro1-tracking-number-or-stock-assigned-message-post-here/page/14/?tab=comments#comment-42894 CAD70.14 in my case
-
delivery of my Pro1 is scheduled for Montréal for coming MON 2020-02-03 - although the package is kept since yesterday FRI at Mirabel, just a few kilometers away from here ! i guess that's a consequence for having it shipped with FedEx economy......
-
FedEx called - duties & taxes are CAD70.14. delivery may happen on MON 2020-02-03 if all goes well for Montréal although scheduled delivery still shows 'pending'...
-
not yet... delivery is still marked as 'pending' for Montréal on FedEx' website
-
me too, i just got a new "in transit" for TA YUAN DISTRICT, TW a FedEx representative from Montréal actually just called me a minute ago and told me that because of 'high volume' and the 'economy status' of this delivery my Pro1 package would get pushed back till there is enough space on one of the next planes... i also asked about taxes but there she didn't see any duties for this delivery. well, we will see.
-
regarding my Pro1 to Canada : i just called FedEx and was told that my package in Taiwan is still waiting for the next available plane to Montréal...for the last 7 days actually !!! but i was told that they will call me back within 3 hours and let me know what the new delivery plan will be... i am not sure if custom issues play a role here ? do we in Canada need to pay import/sales taxes - or is it taken care of by FxTec ?
