Leaderboard

I've seen it reported that the Pro1 doesn't come with its own recovery. There is a standard recovery included with the phone's firmware. I think there may have been some confusion due to the way you need to access recovery mode. To access recovery mode, you have to either: A) Hold down the volume up when you boot the phone (before the logo screen comes up) or B) Use "adb reboot recovery" from a connected computer or C) Boot into the bootloader (by holding down the volume down when you boot the phone (before the logo screen comes up) O

Let's see, there are a number of games I play on the Pro1 Where Is the Setting Game How Do I Make This Stop Search Game What Does This Do Challenge The Volume Game Puzzle The Notification Light Game Holding The Pro Russian Roulette Can You Hear Me Challenge I find new games to play EVERY time I use it. It's such fun :D

Basically it's a standard Qualcomm device. Meaning that data is encrypted and this cannot be disabled. The method of encryption varies: stock uses FDE while my lineage ROM uses FBE. There is currently no TWRP that can decrypt data but it's on my todo list. If you mean a locked boot loader, yes it comes locked by default, and can be unlocked. However, being a device aimed at hobbyists, FxTec chose to disable Secure Boot. Which basically means that you cannot force your device to only run OEM signed code -- it will always allow you to flash a custom ROM

FYI... for those following this thread: The Linux and Windows tools have been updated and now flash xbl properly. This has been verified with real bricked devices (no shortage of those recently!) I'll try to update the MacOS version within a day or two. I asked the Sailfish developers to please remove the option to flash internal storage partitions. They had no idea so many people were doing this, and said they would fix it soon. That's great, but why didn't they know? Did nobody file a bug report or anything after bricking their device?!?

Here's the details from android source (emphasis added): https://source.android.com/devices/input/key-character-map-files ALPHA: A keyboard with all the letters, and maybe some numbers. An alphabetic keyboard supports text entry directly but may have a condensed layout with a small form factor. In contrast to a FULL keyboard, some symbols may only be accessible using special on-screen character pickers. In addition, to improve typing speed and accuracy, the framework provides special affordances for alphabetic keyboards such as auto-capitalization and toggled /

If not mistaken Swiftkey can do that for you.

Canada, Québec, Montréal

Finqwerty is not an 'active' app. It 'just' presents the system with some alternative pre-fabricated .kcm keymaps, and lets the system do all the active work. The KeyMapper is installed as a keyboard driver, that is an active app, and let you map things one by one. Nice versatility, but quite a bit of work to set up fully. I do not know if the setups can be exported and edited in an editor and reimported though - that could help. (Unless I'm mistaken the keymapper only handles individual keys not combinations, but i could be wrong) KeyMapper requires a LOT of high privileges, so

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.

I think he gets a new one sent to him every 2 weeks. 🙂

Perfect! It took some time to configure it the way I want, but it solved for almost everything. It took me a while to get "i" to auto cap. I had to enable autocorrect by tapping on that icon. It can be a bit odd about learning some shorthand capitalization I use with a friend, but I seem to be able to get it to work eventually, if I keep trying. The only 3 things it doesn't have for the physical keyboard settings are: - No double space to insert a period. That setting is only in the generic settings, not in the physical keyboard settings. - When you type punctuation, it inserts

Even if the card was too big/wrong format/wrong block size (etc) I think it would at least know that an SD card had been inserted. My phone isn't even detecting that there's an SD card in place.

They do.

Roguelikes! The keyboard lets us play "real" roguelikes, not just the ones that have been simplified for mobile. Cataclysm: Dark Days Ahead Dungeon Crawl Stone Soup Nethack Brogue

Possibly stupid questions but they gotta be asked: Did you try rebooting after inserting the SD card? Did you look in settings->storage?

Please note that this is NOT the straight apostrophe, it is the backwards slanted one (apostrophe not accent!), printed left of Q, My English isn't good enough to even know where I could (or should?) use a slanted apostrophe over a straight one. Please tell me where it is used. (see also this) And the Alt functions are Stock Android afaik...

Don't know if Eske gave him the idea, But Anssi asked me what I thought of the idea back in December and I told him I thought it was a good solution (which I continue to think) so you might have to blame me too. 😄

This is in the splash partition. It's a BMP file with a custom header prepended. I don't know the header format off the top of my head though. Feel free to play with it, it's a rather easy customization. Also please note the "powered by Android" text, including font, size and color, is mandated by Google for play store certification. There is no use requesting that FxTec change it.

This was incorrect. I posted that before receiving my phone. I posted instructions on how to access the Pro1 recovery mode here:

Never uses PTP either, but it CAN make sense if you want to show images on some computer you are not 100% happy connecting to. As the PC is not supposed to be able to access other than the photostuff. (the pc can still copy/delete/modify those, but should not be able to do it outside the picture folders)

I tried some testing without much success with Light Flow a couple days ago. I didn't do a lot of testing, because I got sidetracked with a bug where gmail notifications won't come through in a timely manner and that is what I was using to test notifications. Turns out google changed something on purpose to not make gmail notifications be timely. They say that email is something that doesn't need to be dealt with on in a timely manner. Now, either they are covering up for their mistake, or it is yet another case of google thinking they know what we want, when they clearly don't. The way a

Sweden, Skåne, Lund-Malmö

Munich, Germany

Taiwan, Kaohsiung

Minsk and Vitebsk, Belarus

Slovakia, Zilina

USA, Washington, in Seattle

USA, Minnesota, near Minneapolis and St. Paul (Twin Cities)

I've tried 3 working MicroSD cards (that all work fine in an Android phone or a laptop), and none of them are being detected by my Pro1. Anyone else had this? I bought phone from Clove. They want me to try troubleshooting with FxTec, which I'm happy to do. If it doesn't work, I guess I'm returning it, and I'll have to get back in the queue... 😒😕

Let's have a poll: Will you use your screen protectior?

Hamburg, Germany

The backtick (grave accent) isn't used in in English at all. Some applications use it as monospace/code formatting, and programs like ssh use it in some keyboard shortcuts. At this point it's only there because it's been there long enough for enough programs to assume it's there. Some people use it as if it's the apostrophe but they're wrong 😁.

IMO, if SFOS wanted to establish itself as the defacto 3rd platform of choice (after the duopoly overlords)... They would concentrate on monetising the direct-to-consumer sales of their OS for these 5 devices... and they could charge a monthly/yearly optional support fee... and a higher fee per device for businesses to manage them...

That's a nifty idea, it'd certainly help lessen cpu load when keys are held down compared to my relatively naive approach.

I did neither, so no.

Mine wasn't recognized until I rebooted.

Germany, 20km from Brunswick / about an hour from Hannover

So basically, duplicating the shift key? Seems silly to me. But if you have a reason for it, great, but please make sure they're separate keycodes so user can remap them individually. In stock currently if you change behavior of one, it affects both. If you're not going to make them meta left & meta right, then fx key should be meta.

I re-read this now, in OP he asked from "fastboot mode" so my contribution was superfluous.

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

I don't know, I have just installed and it works well for me... ...but it does not work on my friend's phone. Basically one can assign a colour to a notification of an application. You can even test it and it should display appropriate colour then... Anyway, it seems for me those values are digital 1 or 0 so I have not really noticed any change in brightness - I wanted to lower the brightness of notifications without any success. Also, RGB LED is a bit uneven, if I was F(x)tec, I would put some light diffuser on top of them...

Well the standard question is of course what happens after a factory reset without install of previous? But that is a bit of overkill I guess. Maybe trying to compare the list of installed apps (enabled) could be a good starting point. And we are sure the Light Manager got notification access, right? If you uninstall and re-install it, it should clearly have a button to enable notification access.

Another possibility is some software a little too aggressively putting things to sleep when the screen goes Off?

Really odd that it works on some and not others. Only explanation when the LED works on charging is that some software are different. I assume we are on newest OTA on all, and that the notification access has been granted? And if so there really are only two possible explanations. Either we got something installed that magically make it work OR he got something installed that somehow interfere and disallow it. Could it be a program that ALSO got some notification LED action (he might not be aware of the app has), and this app somehow got an exclusive lock on the LED access???

Unfortunately, he don't have root access and also I have not gained root as it may cause problems with OTA - this is one reason why I don't like Android. Also, he has closed bootloader while I have opened it in case a reliable backup solution will come up. (I would like to have a real backup / restore solution later.) Basically LED is working for him, at least red and green can be controller by system but not by a user application which is strange as it works for me using the same software version...

Everything that I've been prompted to install. Is there a way to confirm I have everything?

Well that's disheartening. How did you go about getting a replacement device? edit: And I've just discovered my headphones have stopped working, though they were fine two days ago when I first got my Pro1. I've installed some updates since then, so it seems one of them broke something.

Munich, Germany. Not yet received, but will receive before general availability.

Usually a giant padded mousepad on a table should be sufficient. I do worry everyday about dropping the phone during the daily commute in the train. Anodised metal looks cool, but oh so slippery

It didnt disable them, you are using the one with dead keys on first two levels. Switch to the layout with altgr dead keys, then everything will behave normal. The way I read the last post in that git thread, from 7 days ago, implies the us-intl with alt-gr dead keys is already the default, but it seems its not? Either way doing it following kabouik's method works until its fully resolved. Explanation of dead-keys and difference between the two us-intl layouts. A dead key is a key that, on a typewriter would not advance the cursor, so they are typically used for accented le