daniel.schaaaf

Apart from this kind of looking suspicious, it does at least deactivates dm-verity and forced encryption. Since the boot image is patched to deactivate dm-verity and data encryption, I guess you won't be able to install OTAs any more.

Official OTAs won't install when the checksum of the system partition does not match the expected value. Even remounting /system as rw, without further modifications, will change its checksum. Magisk prevents this by linking files to /system during boot without altering the system partition itself. This should also benefit LineageOS, because Magisk modules and settings survive /system updates.

You forgot to warn people: This is a tutorial to prevent OTAs from installing!

I don't think it is reputation the manufacturers are concerned about. They care about money before anything else. Yes, reputation can affect sales (ever so slightly), but that is a secondary effect. A primary effect is customer support. And, it is sooooo easy to refuse support for a rooted device. Yes, there are half-wits who have no clue what they are doing and who break their devices ... but these will find a way to root and screw up anyways. On the other side, if the manufacturers and Google would not constantly screw up and give their users more choices/freedom, there would be fe

Hm, it may not be the sensitivity of the proximity sensor after all. I noticed that I usually see my screen set to max. brightness by my ears touching the screen after a longer conversation. Apparently, the proximity sensor gets ignored ten minutes into a phone call. I can cover the sensor all I want, the screen would not switch off. I usually use Signal to make calls, but I think the phone app has the same problem...

An alternative could be to implement fixes with Magisk. This is on my to-do list ... which is on pause for the moment 😞

Very important piece of information, thanks! I would also like to thank everyone else here for being sympathetic, despite my harsh words. Although the Pro1 (software) can be frustrating to use at times, I do not regret having bought one, and I am glad that F(x)tec made such a fine piece of hardware. I guess this is part of the problem for me: Had the hardware been crappy, I could have written off the Pro1 and simply forget about it 😄

Haha, I do that too. Unfortunately this triggers another bug: The proximity sensor is not sensitive enough (probably just a too low threshold value in some config file). During a call, the screen switches on "randomly", and my ear or cheek change the brightness to max or launch apps ...

This is even more of a reason to fix these huge annoyances that need so little work to be done. Software is, in my opinion, the number one reason not to buy a Pro1. This is in stark contrast to the hardware. F(x)tek made some really good choices there, with plenty of RAM and internal memory...

I am talking about really easy fixes, like the in-call audio volume, that are actually fixed in LineageOS already. You guys/gals from F(x)tec get bugfixes presented on a golden plate. And yet, nothing happens! The Pro1 could be made so much better with so little effort and just a tiny OTA! Sorry, I just called family and friends, and the crazy high in-call volume made my ears bleed ... "Hey, could you please call me back? I bought this cool phone for just 800€ ... and ... I can only use it for calls when people call me. Otherwise, the audio is too high. And yes, this is embarrassin

Are you familiar with the Xposed framework? Xposed is not available for Android Pie or later. But with Riru Core installed, you can run EdXposed, which in turn can run (some) Xposed modules. Before Google broke SafetyNet for Magisk, it was actually Xposed that triggered SafetyNet. In a way, (Ed)Xposed is not the solution but the problem However, there is ... was? ... a complicated way to pass SafetyNet with Riru Core and EdXposed: https://forum.xda-developers.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607 Having read some of the above XDA thread, I am glad that

Alright, I just updated to Riru Core v20.1 and Magisk v21.4 without any problems. I had the impression that the reboot after the Magisk update took longer than usual and I was actually afraid the Pro1 got stuck in the boot process again. Thankfully it was just a little hiccup :-)

No, that's too easy a solution to work ... oh ... but it _did_ do the trick! Thanks! 😄

Tanks, this was good to read 🙂 The slant arrow(s) doesn't do anything on my phone. I just get a lower case "l" or "p". I also have sticky keys and a dead key on my wish list of "things never to see the light of day". Whether the Pro1 can be bricked or not is a matter of definition. To me, a phone is bricked, when one needs to re-flash its partitions using a computer. Actually, I have never encountered a phone that cannot be un-bricked (a word that shouldn't exist if bricking was as irreversible as the word "brick" implies). Over the years, I have grown tired of restoring my data afte

These were my exact expectations. And they turned out to be a huge let down. I have yet to get into key remapping. Without remapping, the keyboard is utterly useless and I feel mocked every time I try to use it. Heck, I have to fold my precious "physical" keyboard away to get access to something as simple as a question-mark on my virtual keyboard! The rooting and tweaking is useless without the ability to make (and restore!) NAND-backups. The ever present fear of bricking my Pro1 prevents me from doing anything "fun". Like fixing the audio distortion and audio volume problems that cripple

Any news on this topic? I found out today, that the caller volume in Signal is only too loud (and not adjustable) when I call someone. When I receive a Signal call, the caller volume is fine. I don't know yet if the phone app is similar ... Wow, this issue is so annoying, it makes me (almost) hate my Pro1 at times ... 😞

I see these errors as well. Looks like an SELinux issue. As with so many apps, libraries and other blobs, I would very much like to know what they all do ...

I did some more testing, thanks to having numerous home office meetings these days :-) The call volume adjustment does in fact work do something. To me it seems to adjust the volume between 60 and 80%. Obviously, its not as noisy as before, but it still won't adjust below 60%. And missing a setting above 80% proved to be an issue during a conference call, when I could barely hear anything. I also noticed that the phone speaker struggled a lot with low frequencies. This made things much worse and should be taken care of by an equaliser. Human (male) voices do not transmit information

Is it really fixed though? I installed the latest OTA (2020-03-06) and still cannot adjust the call volume in Emerald Diler or Signal. The caller volume is fixed to "crazy loud" and I have to hold the phone away from my ear. When I go to Settings to adjust the call volume, my phone plays the alarm chime in different volumes, without any effect on the call volume. In GravityBox, I activated all volume adjustment sliders, seven in total (!), and none affects the call volume.

Good question 😄 You could give oandbackup (opensource) or Appwhererrabbit (closed source, paid) a try. Both support backing up /data/data with root.

TaiChi is closed source, unfortunately. Although Riru is opensource, I have an icky feeling using it. But TaiChi is something I would not even consider installing on my phone 😉 SafetyNet and other root detection methods in e.g. banking apps are a nuisance. In your case, I'd rather do without NFC than have TaiChi on my phone. Sometimes you can be lucky with an old version of an app. I am using an old version of a "photo TAN" app successfully 🙂 If/when it stops working some time in the future, I will simply tell my bank "f*** you!" ...

Did anyone here update Riru EdXposed to "0.4.6.1 (4510) SandHook" already? The thought of updating and getting stuck in a boot halt terrifies me ... but my OCD wants to klick the download button in Magisk manager 🙂

I am too lazy to get ye olde oscilloscope out of the cabinet, but I too suspect it to be electrical noise. Possibly not even from the charger itself. The ghosting only happens when the phone sits on the plastic surface of the table. IT is a height adjustable office table with a laptop and two screens on it. Maybe the table itself acts like a capacitor and the surface of the phone gets charged electrically when it is in contact with the table surface while connected to a power outlet. Oh my, so much text and I bet @[email protected] is not even struggling with ghost touches only while chargin

I see these ghost touches when a certain charger is connected. On another phone, I had ghost touches in strong winds...

Yes, AppWereRabbit can be confusing and it is still in development. E.g. the author wants to implement batch data recovery, which is missing so far. Looking at the list of issues with oandbackup on GitHub, you can see for yourself whether oandbackup would work for you or not. The author is still active and does release new versions every now and then. The last update made oandbackup ready for Android Pie. IF you are a messy like me, and have 500+ apps installed, any backup solution will fail for at least one app 😉