Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by zurvan2

  1. On 4/2/2021 at 2:57 PM, Chad Joan said:

    What operations would modify the system partition?

    Any root-using software could do it. I hit it using AdAway before I found the Magisk and AdAway option to configure "systemless" mode for both. Some apps or plugins/whatever might have a "systemless" option that prevents modifying the system partition.  Check docs, but the best way to know is to test. 😉

    The way it works is that an incoming OTA update checks the signature of the filesystem before proceeding, and if it's different at *all*, it can't be applied. OTA updates are basically a binary diff of the whole disk, so any difference from what it expects could result in a completely bricked phone.


    Yes, that is the system partitions. I assume that was in the thread about returning to stock. In theory if you have the system image for your current state, you could use that type of flash to allow an OTA update to proceed, and wouldn't lose data (but would lose any modifications to the system partition, of course).

    • Like 1
  2. There are several links to various stock rom packages in this thread:

    That thread also has instructions for rooting the stock rom. It will require wiping data.


    This thread

    Has yet-more images, and also instructions to roll back to older releases.

    Personally, I recommend rooting, installing all the magisk stuff you want to use, and then testing the ability to upgrade without losing root before you add any other data. You have to be very careful to not modify the system partition to preserve the ability to upgrade.


    • Like 1
    • Thanks 1
  3. I've had mine for a bit over a year, since December of 2019, with a several-month gap this past summer while it was repaired/replaced in London.

    Covid-19 has meant that I'm at home most of the time, so there aren't as many reasons to use the phone keyboard, since I'm not "out and about." I always have quick access to my own real computer instead.

    The phone is still excellent in most ways. It really does "just work" for almost everything. The keyboard is still great when I use it, battery life is great, etc. No complaints about power or the screen or most of the software.

    Update on annoyances:

    • The edges are less prone to accidental input with Edge Null.
    • There is still no acceptable case solution to protect the screen. The curved screen is a big part of this. I really hope future models plan for support for cases. See also above about not having my phone when the screen was damaged.
    • The fingerprint sensor is *mostly* fine with a case that reduces the sensor's exposure. It mostly activates when I mean it to, now.
    • The camera software is still pretty bad. Pictures are OK, but opening the app and taking a shot is slow. I miss many shots due to the software. This is a real shame... I feel like there is so much potential with the hardware, but the software just doesn't capitalize on it.
    • NEW (or newly noticed): lately the thing that annoys me is that when hitting the power button or the fingerprint sensor, it takes too long for the screen to turn on. Often I assume I didn't actually trigger it, and hit the power button *again* and that gets queued up and turns the screen *off* instead.

    Still, overall very happy with the phone.


  4. My pro1 took a little vacation to London to be repaired, and it's now back, so I'm setting it up again.

    In the stock camera app, if I select "SD Card" for storage, it's writing the files to Android/data/org.codeaurora.snapcam/files rather than to DCIM/Camera. I thought this wasn't the case the last time I had a pro1 set up...

    Is there a way to get the stock camera to store photos in the standard place (I.E. DCIM/Camera) on the SD card? (and the card is set up as external, not adopted storage. I want it to be usable as a way to move files on and off the device)


    • Like 3
  5. I have always required root on my phones. I will not buy a phone that can't be rooted. I've even bought phones without a keyboard, but that were rootable. Root is non-negotiable.

    OTA Updates are affected, not directly by root, but by other things using root to modify the partitions that the OTA updates would affect. The OTA mechanism is a simple binary diff, so if a single byte is out of place, it would fail. This is done to minimize download size.

    I totally agree that android would be better off for all users if they adopted a finer-grained permission model for apps. In particular, the one permission that I want to see is a permission for network access. Stupid silly local games have no need for network access, etc. Network access is the one permission that trumps all the others. I don't care if a silly game reads my contacts, as long as it is not allowed to talk to the network.

    We saw teases of better permission models in Android for a long time, which to me indicates that the Developers want to add them. The features must keep losing out to other work, though. Apparently adding permissions doesn't make money. 

    I would love to hear about which phone operating systems are *more* open than Android, though. IOS certainly isn't... everything that's limiting about android is 5x worse on an iPhone. Bonus points if those operating systems also have robust app stores and available supported hardware.

    • Like 2
  6. On 5/12/2020 at 11:54 AM, 3zet said:

    I think the most comparable apps and games will be from this post below:

    I've attempted to get Dolphin up and running, but no luck so far. If anyone has a game that's free on the play store that demonstrates the issue, that would be simplest to test.

  7. 7 minutes ago, 3zet said:

    Can you compare performance on your device with original governor and with ondemand, please? 

    How would you recommend doing so? I haven't noticed any performance problems so far, so I don't think I have any use cases that would stress it.

  8. 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.

    • Thanks 1
  9. 13 hours ago, tdm said:

    If you want to root your phone and be freed from this nonsense, don't run stock.  Lineage is coming along nicely and Sailfish is supposed to be rather good as well.

    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.

  10. 9 hours ago, DieBruine said:

    This has happened to me with Enter. Started on Saturday. I have to use one of the numbers or letters before Enter starts working again.

    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.

  11. On 1/31/2020 at 10:52 AM, ermghoti said:

    Well, yes, but if you register the part of your hand that causes inadvertent reads, the reads would be successful, and there'd be no lockouts, correct?

    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".

    • Like 1
  12. 8 hours ago, brockhulse said:

    Guys, I just registered the part of my hand near the reader (at the base of my index finger) as a new "fingerprint", and now all I have to do to unlock my phone is hold it. I was initially confused by the placement of the fingerprint reader as well, but I think this may end up being an even better placement than most other fingerprint reader placements. I'll have to see over the next few days how it goes, but it at least has potential.

    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.

    • Like 1
  13. 6 hours ago, SirBaconIII said:

    "intall failed, reason: 20" which is rather cryptic.

    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.

  14. 13 hours ago, Pete said:

    why is one of these T-Mobile only phones getting full signal and one of them getting almost nothing?

    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.

    • Like 2
  • Create New...

Important Information