Jump to content

zurvan2

Members
  • Content Count

    94
  • Joined

  • Last visited

Community Reputation

111 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Each partition has an image that can be applied to reset that partition to what it "should" be. Most of the partitions then cannot be modified and have OTA updates work... any modifications would make the OTA fail checks that ensure that the update is safe to apply. This is actually valuable, because the updates are not complete images, they are like a recipe to take the existing data on the partition and write new bits in specific locations. If the existing partition doesn't match the expected image, that could write complete garbage over whatever is actually there. There are a couple partitions that can be changed, notably the userdata partition, where all your stuff is normally written. If you look at the "return to stock" thread, you'll find a script that has 18 unique images, most of which get applied to 2 partitions each so android can perform online updates. One of these images is "system.img" and the partitions it goes on are system_a and system_b. So, steps: 0. Make sure you have a good backup of your stuff. (Google actually does a surprisingly good job at this nowadays, at least for stuff from the play store) 1. Find the system.img that goes with your current system version. I have no idea where you can find this for recent updates. When I did this, I returned to the original stock image, before any OTAs, but that only worked because that was what the rest of my system was at. You must have the right version of this image for your phone to have the OTA work, and using the wrong image could prevent the phone from booting. 2. get your phone into bootloader mode and connected to your computer. You can either do this by turning the phone off, and then turning it on while holding volume up, *or* connect it while running normally and run "adb reboot bootloader". You can verify that the device is connected properly by running "fastboot devices". Your device should be listed. 3. run "fastboot flash system_a system.img" and "fastboot flash system_b system.img" You only actually need one of these, but I have no idea how to figure out which one is currently in use. Standard disclaimers apply... if everything breaks, you can always return to stock, but only by wiping userdata, as far as I know.
  2. Do Lineage and/or Sailfish have OTA updates that work while rooted? I've always been under the assumption that stock + rooted is the simplest to maintain, but perhaps I've drawn incorrect conclusions.
  3. Same here. I mostly notice it in Termux, and didn't know if it was specifically an issue with Termux. Now confirmed in other apps. This happens every time the screen turns on and off, not just at boot time.
  4. 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
  5. There's an app called KeyMapper (and many other options as well) that will let you redefine the behavior of keys. You could use that to make shift-3 produce that symbol.
  6. I would rather have to enter my password manually than have my phone subject to arbitrary inputs when it was unlocked without my knowing. This is the original purpose of a "keyguard".
  7. I don't think most people are complaining that it's hard to reach the fingerprint reader... most complaints are that it's too easy to *unintentionally* activate the fingerprint reader. The failure cases are that the phone is already unlocked when you go to use it or that the screen shows "too many attempts". Both are because the fingerprint reader is, in essence *too* convenient.
  8. I also had this. My theory was that despite my best efforts, something had actually modified the system partition, making the checksums not match. I restored the stock system.img as well as boot.img, and that let the update proceed. I was lucky that the version I was updating from was the original stock rom that I had system.img for. Since then I have been *much* more careful about things modifying the system, and have not had the same problem.
  9. Compare lists of LTE bands on the two phones and t-mobile. You could also try an app like LTE Discovery on each device to show you which bands are in use.
  10. 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.
  11. 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)
  12. Long press on the "normal" task part of the profile, and you should have an option in that menu to "Add Exit Task".
  13. 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.
  14. For termux, just create ~/.termux/termux.properties with the line: back-key=escape See https://wiki.termux.com/wiki/Terminal_Settings
×
×
  • Create New...

Important Information

Terms