Craig

USB debugging is for adb, not for file transfers, and requires developer options enabled to even get that setting I believe. Sorry I mixed up the term. For MTP file transfers gotta tap the notification lotsa times like Hook described, does not require developer options or usb debugging.

I thought (although probably wrong) that only happened when you enable adb debugging and was for adb access, not for mtp...

See TDM's thread about factory restore tool for EDL info.

I believe this is by design and Android default. So if you plug into random cable to charge somewhere, the other end doesn't get get access to your files. Although I agree its annoying. That's why I use ftp server on phone and just use wifi to transfer stuff.

I can't one handed open without pushing volume or power buttons.

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

I had a similar issue at first, kept hitting del instead of backspace. But I got used to that fairly quickly. Esc key is currently mapped to Android Back (not Esc) although this may change soon. That being said, you can probably do that with key-mapper: https://community.fxtec.com/topic/2557-key-mapper-foss-app-to-bind-keys-buttons-to-other-keys-or-actions/?tab=comments#comment-37604

This will be a challenge, considering we have no recovery partition, at least as far as I understand it. Good luck with that too. Although I believe that feature is coming to TWRP sometime in the future; as of now it cannot even decrypt for backup purposes.

I've made it the topic of #bugs on discord; if you want to post it on reddit I could pin it there too.

That's something I haven't heard of in a while. Any connection to the the shareware dos/os2 versions from the 80s/90s?

I've had mine a month and a half, I'm much better at it now, but still find it awkward and difficult. I can close it one handed no problem, but opening isn't something I try very often and I can do it, but haven't practiced that. I certainly never had an issue sliding my photon q, in fact cuz I had slide set to unlock automatically, even when I wanted to use in portrait I'd open/close the slider as I found that quicker. I can't see Pro¹ ever being that easy.

I had noticed the similar issues in Termux until somebody mentioned in another thread it has its own keymap file. (Forgot exact location of file.)

Ok, my editing window is over and I think it's good enough to update the first post if you'd be so kind (other than change "Unlock Booloader" to ""Unlock Bootloader" in the last line of step 3.). As I made it difficult for you to edit the original one with strikethrus as you started to do before, I'd suggest just replace the whole post with updated version but keep the old one in a spoiler block or something and leave it as is for historical purposes. But however you want to do it is fine. @J_P Not sure what's going wrong for you. I personally haven't tried it with current v

I think that'll be resolved with next OTA.

You're right, I don't see for example anything about bluetooth, but you're not alone in that, I think only speakers/headphones working right.

True @waxberry about recovery partition on A/B devices, but even on other A/B devices, that (quoted) works, why not on Pro¹? (I still wouldn't call this a bug tho, just lack of a feature).

I used keymapper to make it into a slash key.

In sailfishos kernel, slant arrow keys are mapped as right-alt. Thus, can alt-tab with those as well. Dunno if we'll be so lucky to have that happen in stock kernel tho, but I hope so.

Yep. Most Some are already listed as known issues on the github issue tracker (linked in 3rd post of this thread by one of the hardworking devs :) https://github.com/sailfish-on-fxtecpro1/droid-config-t5/issues i.e.: Extra imaginary partitions SD card : https://github.com/sailfish-on-fxtecpro1/droid-config-t5/issues/24 usb ssh: https://github.com/sailfish-on-fxtecpro1/droid-config-t5/issues/20

The Pro¹ is just too powerful. Phone too loud at lowest volume. Screen too bright at lowest setting. Keyboard too awesome even when backlight off. Where does it end?

For those getting their devices and wanting to root now, the recommended procedure has changed! This method should allow you to take future OTA updates keeping root using the A/B method linked earlier in thread. Steps have been reordered and updated since first post. 1. Install Android Platform Tools on PC (adb & fastboot) Ubuntu (and presumably debian): sudo apt install adb Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip Windows/Mac/Linux: https://developer.android.com/studio/releases/platform-tools 2. Connect Phon

# java -d64 version Unrecognized option: -d64 Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.

You've probably explained why I've noticed Termux behaves differently than other apps in regards to keymaps; its got its own!

I did have to install it (that was indeed the correct package name). Version 11.0.05 2019-10-15. It doesn't recognize the option -d64 tho. It tells me so.

I got used to it also, but it does make left shift and tab seem far away.