Leaderboard
Popular Content
Showing content with the highest reputation on 02/11/2020 in Posts
-
5 points
-
Not sure if we've had much info on this officially but they at least Tweeted back on this... So if nothing else, then at least we know it's planned4 points
-
This will take you to a poll which includes the fxtec pro1 as one of it's options. Let's make this happen.3 points
-
@tdm I know you've got some ideas of what keycodes to assign the various modifier type keys, and recently I saw something about you doing some odd things with the slant-arrow keys that might restrict user customization, etc. I've chatted with mccreary a few times about my thoughts, and thus learned a lot of stuff, and wanted to share what I believe would be the ideal way to map keycodes in kernel that takes advantage of built-in AOSP features, and allows user to fully customize layout afterwards. Esc --> Esc Slant Arrows --> Meta (left & right - separate key codes ar3 points
-
3 points
-
I just found out about this phone, watched a vid, and am in looooove. Want to purchase (pre-purchase), but need to know-can this phone be locked/what kind of security features does it have?2 points
-
So I've managed to restore my device to the original image. I was following the solution from Tom and using his tool from here: http://files.nwwn.com/android/pro1/factory.html However, I've faced the same problem which some people were posting here: "Connection time out". Have no idea what could be the reason of that. Nevertheless, in the end I managed to successfully reflash the phone. The trick is to have prepared tool for reflashing and to press a button as fast as possible immediately after you reboot the device (power + volume button down). Because device ins completely unrespo2 points
-
Thanks. When Foxconn factories restart at Shenzhen it will be in the news. This news is about Zhengzhou: Apple supplier Foxconn restarts key China plant with 10% of workforce, source says "The company, however, has not yet been allowed to restart production in Shenzhen, a southern manufacturing hub, the source said."2 points
-
I'll attach it as a screenshot for others who can't get into it: basically it's something for the "near future"2 points
-
I think they don't know it - also their manufacturer doesn't really know that I think. Even our PCB production partner can not predict when they are able to assembly our panels - not related to F(x)tec.2 points
-
EskeRahn posted a NVRAM variable here, but how do I set it in fastboot?1 point
-
Let us help F(x)tec with some show casing! I hope everybody will flash it around and spread the word to everybody they think might be just a little bit interested, or might know one that is... At Crackberry a guy was asking where he could try it hands on. So if you are willing to be contacted by someone that wants a hands on before buying, here is a tread to post your Country, state/region, nearest larger town, Then people can create an account in here and send a PM to arrange further. Please mark the geography in bold and/or a larger font, to make i1 point
-
Sure, it seems silly to me also. But that's the way the keyboard is printed. I would map the fn keys to something else but they are required to generate '/' and '?'. But the beauty of the new keyboard driver is that you can remap all the keys. The gpio keys aren't remappable yet but I'd like to make them remappable before I finish.1 point
-
I am going to make the default keymap as close to what one would expect by just looking at the keyboard as possible. That means: * The right-slant-arrows (fn-keys) are (dead) modifiers that allow generating the yellow symbols. * The FxTec key could be anything, really. Home would be fine, or any other reasonable suggestion. * Chording the FxTec key (FxTec+number) is sort of asking for two things at once -- you want it to be both a normal key and a modifier key. That's probably not easily doable. But I would like a way to generate F# keycodes. I was thinking maybe fn+ctrl+#1 point
-
This happened to me too and I reported it in the Known Bugs thread. For me, it mysteriously started working again after firmly squeezing the phone shut, and it has worked since. I don't know if it was a hardware or a software problem because it hasn't happened since....1 point
-
The built in AOSP launcher shortcuts only work with Meta keys. That's why I originally suggesting make Fx key meta key, so you can use launcher shortcuts from there. But if we make the slant arrow keys meta, then that's where the global shortcuts will come from, and Fx key is useless (other than its current use, android home) but that function can be meta+h so not needed to have a dedicated key - but that's my opinion. I get the impression some people like this single press home key, and that's how Fxtec seems to want it. This is using built in Android stuff so not major work for fxte1 point
-
I created another (bash-)script, modding the specific line in the recovery. I hope you like it: modbootimg Custom builds are available over my profile page -> My Profile - "About Me" tab1 point
-
Thought this was worth reminding people of this while we wait for internal solution, as I've seen it referenced in a few other threads lately. Plus even if they fix the keyboard stuff, there's still plenty of use for this app.1 point
-
I play ToonBlast. Other than that not playing anything currently, but I'd also rather like to buy a game instead of freemium where I have to pay more for coins or no-commercials-option.1 point
-
Yeah I don't care about the colors, I expect shift to be level 2 like every other keyboard in the world, until now I hadn't even made the connection that the slant arrow and 2nd level characters were both yellow, I just assumed that's an fxtec color they chose to use for looks. But yes, the lack of slash and question mark should be handled in the kcm, not kernel. And if fxtec doesn't provide layouts that can get slash and question mark, then finqwerty is our solution. I personally plan to map the right slant arrow to slash key once the two oem keys have separate key codes in kernel.1 point
-
I don't have the Pro1 yet, but I'm looking forward on playing Age of Empires with it. It worked fine but relatively slow on other keyboard sliders (Moto Droid 4, Photon Q), so it should really be much fun. Otherwise I don't really play games on the phone anymore since they are bloated with ads or purchase options (pay to progress). I'd prefer to pay 20-60€ and have a game to play instead of having to pay unlimited amounts of money to get realistic progress. The only exceptions were Exiled Kingdoms and Andor's Trail, both RPG games. Lastly, I'll try Terraria on Android and Starbo1 point
-
Well it might work while closed, but I doubt they would stick when slid open, but could be worth a try. Note though that the hard edges could be complex to modify for the buttons and fingerprint reader. Being creative, what about modifying TWO sets? One for each part of the Pro1, cutting down the covering back on one case and the front on the other case...1 point
-
Thank you for answer. I'm on Magisk. When I was starting with Pro1 I was searching for method to not encrypt data partition (for future backups) but cannot find one...1 point
-
Last update was "However because of the virus no one knows when the traffic is re-open and people can get back to work.", does it really help to just repeat the exact same information?1 point
-
Yes, but manufacturer may just released an update about unknown production time (at least for us)... So, currently it is not simple at all to say any meaningful information... so yes, an update about no update is possible but nothing more unfortunately.1 point
-
The data is encrypted by default. You can set a lock screen code or pattern, as well as a separate one at boot time. It is pretty much stock android. There isn't a built in app locker, that I know of, but you can use apps like Smart AppLock for that.1 point
-
That would be a good thing but you can also make system wide shortcuts by using Keyboard/Button Mapper. It has a functionality to add specific shotcuts to key press combos.1 point
-
1 point
-
I know, I tried to find that information earlier when I was making the previous post. Thing is, because (I only just noticed) the screen of the Pro1 is marginally smaller than the base it looks as if even the other style of P20 Pro cover will also be too big. We'll need to locate a case with smaller dimensions than the Pro1 to fit the screen portion properly. EDIT: Scratch that, because of the screen curve the vast majority of it is 'smaller' but the screen actually curves down to the same size as the base. However, because its not as thick as the base the 'rear' cover doesn't f1 point
-
Well we expected at the least the first part see discussions on the different variants with front-over-back or back-over-front previous in this thread.1 point
-
Just curious. Are they a-holes because they only want to support mainstream phones with a large enough customer base to be profitable or are they actually a-holes? 😉1 point
-
One I spammed in the forum before, still happy with it 🙂 https://f-droid.org/en/packages/net.gsantner.markor/1 point
-
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 d1 point
-
It is slightly left of the speaker. Note that it got quite a delay in reacting to changes, but pressing power off and on, triggers a new read.1 point
-
I saw in the long case thread @wilhelmfitzpatrick has fitted a carbon fibre skin for a note 10, and it looked quite good.1 point
-
That's weird - I thought a posted (another) response... I got it working by allowing updates over data/the network (instead of just wifi). All sorted. 👍1 point
-
Could well be. Or perhaps the rooting mechanism is not perfected and have some odd side effects?1 point
-
Yes that is what I wrote: Android Market , http://market.android.com/ ...I know i'm old, but I'm not going to use the silly alias1 point
-
F(x)tec didn't think real hard about searching when they used parenthesis in the brand name and superscript in marketing name.1 point
-
1 point
-
Try read the initial post in the thread. It was never intended as a discussion threads on apps. And as this is actually a feature request that is fixed by the app, I found it more suitable in here. That apart it did not seem to work that well on my unit, maybe it is because I fetched it from the Android Market, where it is 3.2.0, the version is slightly lower in your link 3.1.8. It does offer a lock mode I did not try, but simply turning off the display would have been enough for me. It seems a little odd that it would need more privileges to turn off the screen than to turn it on. B1 point
-
1 point
-
The main part of this is you have to boot to bootloader before executing this command. From android, you can execute adb reboot bootloader; I think you're sfos, so you're stuck using the voldown+power method to get there which always works.1 point
-
You need to have usb debugging enabled, and ADB installed. Then we can execute fastboot oem off-mode-charge 1 EDIT: from fastboot mode, see Craig's correction below.1 point
-
is there any new information about the current corona virus lockdown and is there any idea when production will start again? the wait is really hard to bear 😢1 point
-
Hooray! The problem seems to be solved, after flashing some of the partitions, as described in thread of Factory Restore Tool, with command-line tool qfpkg_cli . Apparently, Sailfish OS makes it very easy for user to format internal phone partitions, under mistaken belief of them being memory card partitions... In short: don't go and format a partition just because GUI recommends to do so - it is not necessarily a good enough reason. Thank you! Best wishes. ~~~~~~~~~~~~~~~~~ Per aspera ad astra...1 point
-
Yeah, it is so big you can use the back as a plate eating 😇😜 It is nice that it is rugged though 👍, To me the Passport design offers the worst of two worlds: A cramped always out keyboard and yet too big to possibly operate even partly one handed. The Key½ design I can understand, as you get a keyboard (though cramped), and a screen that at the least to some extend can be one hand operated. I mean the Titan is really Titan-sized, it is humongous. Liiterally like three SonyEricsson txt pro landscape-keyboard-sliders side by side--- (including the weight)1 point
-
If I was F(x)tec I would get a portrait device in development to cover that section of the market.1 point
-
I was never in the BB team being a Nokia Communicator user long before they became a thing. Still as I was starved from physical keyboard smartphones I remember considering those Android BBs when they came out and decided not to, square screen and fixed keyboards are just not for me. Still too bad they stop doing it.1 point
-
I use the app "Battery charge limit" from XDA, which allows you to limit the battery percentage. I usually set it to 85% except if I'm going for holidays or so. I think it could already work with the Pro1, but maybe we need to wait (and ask) for the support. According to the magnetic chargers: I use a couple of mobile devices for work and have not yet found a reliable charger that does also charge quickly. And I'm not even talking about quickcharge or data transfer. They all are flimsy, have a stupid LED (and some further electronics to prevent burning them out) or break after1 point