Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/07/2021 in all areas

  1. well there is no problem with rooting just don't modify system partitions 😉
    1 point
  2. The problem is I had Magisk installed and used it to install some stuff which modified the system partition, then instead of uninstalling the addons before uninstalling magisk I just uninstalled Magisk, so of course it now has no knowledge of what was previously modified. When I get around to it I'll just wipe the whole phone with the 2020 firmware listed above. If I can't figure out a fireproof way of backing up the boot and system partitions before I go rooting it again I guess I just won't be rooting it again...
    1 point
  3. Not currently. If I could decrypt data, I'd have a decrypting TWRP released by now. 🙂 I am hoping that backing up an FBE encrypted data partition (eg. while in recovery) and then restoring it in the same environment will work. But I have to test that out.
    1 point
  4. Think one of the reasons hes doing this as a CLI type tool is data will be decrypted (as it reads the files direct on device not external) before sending to the backup so you have the data unencrypted.
    1 point
  5. I had a nasty ghosting keys issue on 16, phone died. Confiscated one and went straight to 18. I think tdm mentioned a while aago that 18 was running smoothly according to !?!?. So I took the plunge and have been running 18. HD-media worked under 16. When you ook under DevOps you can see that it's unavailable. So I was wondering if it's going to be fixed. If not, too bad, just curiosity from my part. Screen brightness was an issue on stock and if recall correctly earlier versions of LoS. I would suggest you use the front camera in a dark room with creen brightness >25 (slider). It looks
    1 point
  6. Well, the standard Unix-y part of it will be a CLI tool with arguments more or less like tar. But the backup and restore arguments will likely be limited to block devices and directories, though that is not certain yet. Block devices will be backed up as a single unit of data (as you would get with "dd") and directories will be backed up recursively (as you would get with "tar"). It will also have a client/server mode similar to rsync, which will communicate over sockets (meaning remote backups are possible without using tools like stdio pipes or sshfs etc.) Android will surely
    1 point
  7. If you want to put it this way: yes, you are buying a smartphone with technology that has been on the market for a few years. The focus of this device is on the physical keyboard. Current hardware does not really exist with such a keyboard. If you want newer hardware, you'll have to request a refund and buy something out of the mainstream. The unfortunate delays have already been discussed many times.
    1 point
  8. Currently using black gorilla tape for the back so I don't feel bad setting my phone down. Looks like absolute ass to my standards, but putting it out there as it is very easy to stick on, and has stayed on for a few days now. Probably transparent packing tape could have worked too, dunno why I didn't think of that first. Also would prefer a hard shell but does not seem feasible for the moment.
    1 point
  9. We have heard Google for YEARS saying that with the NEXT release, updates will be easier.... We are yet to see it actually happen. But will be great for the consumers if it becomes reality.
    1 point
  10. i know that I am repeating mine and many others here. I have been waiting since the middle of April last year for my device. I do understand the virus and other things that go on. But. we keep being told twelve weeks and twelve weeks and other things. The last I heard was between January and March 2021. I am being respectful here but our phones will be at least a year old with year old technology. Are they going to be updated with the latest technology or are paying for a year old phone. Thanks, Bob
    0 points
×
×
  • Create New...

Important Information

Terms