Jump to content

zurvan2

Members
  • Content Count

    110
  • Joined

  • Last visited

Everything posted by zurvan2

  1. Neither of these affect my Pro1. If anything, the screen stays off for too long after it is held to the ear. No complaints about audio, either. Have you installed all the OTA updates? I think one of them addressed some things like this.
  2. I have that exact version rooted, using pretty much the *current* steps in the first post of this thread. (I.E. I patched the boot.img using the Magisk Manager installed on my device and installed that using fastboot)
  3. Long press on the "normal" task part of the profile, and you should have an option in that menu to "Add Exit Task".
  4. You can do this pretty trivially with Tasker. Profile: * State: Keyboard out * add an innocuous task as the normal task * Add an exit task which has a step of Display -> System Lock. You need the exit task (as opposed to just inverting the state check) to be sure it doesn't constantly trigger.
  5. For termux, just create ~/.termux/termux.properties with the line: back-key=escape See https://wiki.termux.com/wiki/Terminal_Settings
  6. That phone is missing most of the useful keys from the keyboard! Most of my interaction with the Pro1 keyboard is using the keys "around the edges" so to speak. All the meta keys like tab, escape, control, alt, etc. A keyboard isn't a useful keyboard if it's not a full keyboard.
  7. You can choose whether or not to sync deletes per "folder pair". I have one "folder pair" set up for all of the SD card, with an exclusion for DCIM, and a separate folder pair for DCIM with slightly different rules. You can repeat this pattern and have completely separate rules for any folder. The initial sync is definitely expensive. Once the initial sync is complete it's much better. The whole thing is not as efficient as rsync or unison, but it does work.
  8. If you have a linux box on your LAN (or know enough windows to get a server working) FolderSync works well. I use it for two-way syncing. 99% of the time, it is effectively just a backup tool, copying everything from the (internal and external) sdcards to my linux server. Occasionally, when I want to put something onto the phone, I just put it in the appropriate folder on the server and run a sync. I mostly have stuff on that server in the first place, so it's simple for me. LAN recommended... it operates per file, so the overhead can become prohibitive on a slow connection.
  9. OMG this is awesome, thank you! To be clear, these are the *non*-rooted images, right? So we'll need to patch these in Magisk Manager to get rooted images? That is perfect, since we'll probably need to roll back to the correct version of these that match our patch level for the OTAs to apply correctly.
  10. Or, another possibility, the OTA I'm starting with isn't the first? (and hence I'm not applying them in the right order) I have three of them: 2019112919502366681, 2019121017300185739, and 2020010614044563241. Were there any others?
  11. I tried using the tool from this post on the boot.img files from the various phases: https://unix.stackexchange.com/questions/64628/how-to-extract-boot-img (links to a google tool) ONLY the boot.img from the stock rom looks correct. The others... kinda extract, but the file types are all wrong and the command output only looks right for the stock rom. The others look like garbage. So I'm thinking that payload_dumper.py is just broken/old/or for some other specific devices. 😞
  12. Right. payload_dumper.py seems to have next to zero validation, so we really need additional validation before we try these in a phone.
  13. Yep, that's the one I found. I don't claim to understand much of what it's doing. I did use the differential mode, and for the files it is *modifying* it looks like it's doing something sane, but it also needed other files that didn't exist (e.g. hyp.img). I just "touch"ed them and then the script proceeded. It also needed all files named ".img" instead of the other extensions in our stock rom. I ran it against all of the OTAs, and each one produced a modified boot.img. I'm also not sure if the OTAs are each supposed to work against the stock rom, or if they should be applied one aft
  14. I found a script to extract OTA updates, and the most recent OTA seems to have modified boot.img. So we will want to use an updated boot.img with root.
  15. Wel... my understanding is that boot.img contains the kernel and ramdisk. Aren't hardware drivers part of that? I'm trying to chase down mechanisms to extract the OTA updates, or at least get enough information from them to determine *if* they modify boot.img.
  16. Hrm. When I applied the OTA updates earlier, I did so with the following procedure: (previously discussed in this thread: ) 1. flash the stock boot.img (this removes root) 2. flash the stock system.img (this was necessary because I had apparently modified something in /system. You may not need this if you have not) 3. Apply the OTA updates 4. flash a modified boot.img to root again. The one I used was the one provided above, in *this* thread. It is very possible that this reverts some of the OTA updates... I can't tell. The version reported by android did
  17. Yes, I'm up to date with that update, but not today's, yet. I did re-root after that, which probably reverted the /boot partition, but I assume there's no runtime code there. (could certainly be wrong)
  18. I have also seen the touch screen get lost, *and* have experienced it (multiple times) overlapping with the keyboard not responding. The only way to restart at that point is to hold volume up and power for about 10 seconds, which also forces a reboot.
  19. FYI, I ordered this case in the US. "Premium TPU Case for Huawei P20 Pro Slim Fit Transparent Silicone Clear Soft Cover Case" It fits fairly well on the keyboard half of the phone. It does not interfere with the opening mechanism, really. I was afraid it would. It definitely improves the grip, and provides a bit of protection to half the phone. I modified it in a way similar to how @EskeRahn did. Tip: leather punches are great if you have them. It would be great if a similar case was made specifically for the Pro1, with a bumper case for the display half.
  20. Ah! Using a layout + keymapper for just a couple keys would be a lot less work.
  21. If Key Mapper can't automatically switch, Tasker and Secure Settings (a root app) can. Profile -> State -> Hardware -> Keyboard Out Task -> Secure Settings -> System+ -> Input Method -> Key Mapper keyboard add Exit Task -> Secure Settings -> System+ -> Input Method -> pick your normal keyboard.
  22. Key Mapper seems to do exactly the same thing as FinQwerty, as far as I can tell, and is customizable. It works really well so far when it is enabled. Er... except now that I'm done setting it up, I can't get the software keyboard back when the physical keyboard is closed without selecting a completely different keyboard, which breaks the Keyboard Mapper keyboard. Is there a way to have a different "virtual keyboard" when the physical keyboard is open? Edit: FinQwerty also does not appear to have any layout for "US for Physical QWERTY" and none of the other layouts look a
  23. What specific mapping are you using for these? I'm struggling to find a free key to put them on that would be any better than being access by the yellow arrow.
  24. I'm feeling particularly obtuse this morning... *where* in Key Mapper should I use arrow to enable using shift to access [email protected]#$%^&*()_+ ?
×
×
  • Create New...

Important Information

Terms