tdm
-
Content Count
801 -
Joined
-
Last visited
-
Days Won
84
Posts posted by tdm
-
-
On 11/25/2020 at 12:27 AM, MickH said:
I think I've found the culprit, actually. Firefox.
I'll do a bit more poking around, try other apps and browsers and see what happens.
Firefox does indeed lock rotation occasionally. I see it on my 1+7pro sometimes. You just need to kill and restart it.
Also, I generally like to keep some diagnostic tools on all my devices which can help figure out issues like these. Sensor Box (for all sensors including rotation), GPS Test, and NFC Tools frequently come in handy.
-
2
-
-
It's still on my TODO list. But I am writing an Android based backup/restore solution first. This will be much more flexible than TWRP. Check the AICP-Q thread.
-
5
-
-
2 hours ago, MickH said:
I've had a good read, but I don't think any of the first two methods would be of help, as I don't want to dismantle the phone at this stage, due to the warranty.
The last method needs the phone to actually turn on and display the Fx logo. I'm not getting that even with both volume buttons held and the power button pressed.Your phone is already booting to EDL mode. This is what you are seeing in the USB dialog. Specifically, "Qualcomm HS-USB QDLoader 9008" is exactly what the flash tool requires.
Now, why did it all of the sudden decide to do that? I don't know, but there is likely some underlying issue. Perhaps a dead or dying flash chip or worse. But using the factory restore tool is a good first start, along with starting an email thread with support.
-
3
-
-
1 minute ago, VaZso said:
Does it mean users will be able to install it on the official LineageOS build for Pro1?
So the solution may not be included when one installs LineageOS but can be added by this add-on mechanism and still receive security/other updates for the base OS?If it may work like this, then it will be a very good solution.
I hate I can not save / restore my phone correctly.
Yes, it should work just as well as gapps and su for any LineageOS version. This includes "stock" on the Pro1-X... which, as far as I know, is just going to be a normal LineageOS weekly build installed at the factory.
-
1
-
-
Just now, VaZso said:
Does it mean it will also work on stock LineageOS or it should be a customer compiled code base?
"Stock LineageOS" is a bit of an oxymoron. It will install on LineageOS via the add-on mechanism, just like gapps and su. I will provide that add-on, you will not need to compile it yourself. But it will be open source, of course, so you can compile it yourself if you want.
If you are asking if Lineage will incorporate this into their builds ... I cannot answer that. They are currently planning to use SeedVault. But SeedVault uses the built-in Android backup API which allows apps to opt-out of backup and restore. This is a fatal flaw for me and many others. So perhaps they will change their mind after my project is running... who knows.
-
5
-
-
14 minutes ago, VaZso said:
What is the chance it will work using an Android other than AICP?
Is there any chance LineageOS team will also import required code base?It will work on any custom Android version including Lineage. I plan to package it as an add-on, like the su package.
-
7
-
-
A brief update...
I've been working on a backup/restore solution for Linux (plus an Android app to drive it) that will be able to do full backup/restore, similar to TWRP.
This is a bit of an involved project, but it will be well worth it in the end. It will be cosmetically similar to tar on the command line to make it familiar to use, but it is an entirely new code base. Some of the features include:
- A client/server mode for use in Android and other privilege sensitive environments.
- Built-in compression and encryption support.
- The Android app will most likely support remote backup/restore via an HTTP streaming API.
- Built-in xattr support (including selinux labels).
- Incremental backup and restore support.
- Will backup and restore block devices.
- And probably more that I am forgetting...
So once I get a test version I'll include it in my AICP builds. I'll also make it available on github for those that want to give it a try on other Linux systems.
In the meantime, the Lineage folks have been busy improving stuff in 17.1, especially support for the hardware keyboard options. I'll be making a new AICP build soon and hopefully the OTA will work this time.
-
11
-
13 hours ago, FlyingAntero said:
Would it be possible to make AICP build with SafetyNet hack to pass the check? I know that there are some ROMs (like ParanoidAndroid) which passes SafetyNet check but I don't know how it is implemented. If you don't need root then you would not need to try any Magisk Hide things to pass SafetyNet.
Currently I am running Havoc OS on my Xperia XZ1 Compact and it passes SafetyNet checks by default.
I could check into it. Shouldn't be hard.
-
2
-
2
-
-
3 hours ago, pebert said:
Hi
Some days ago I got tired of Linages and decided to go back to stock, flashing all the different image files via fastboot. After this the phone won't boot, only get stuck showing the fxtec logo. Tried two more times with same result.
Then I followed this guide, everything went fine, tool is showing progress and says when it's done. But now the phone always gets to fastboot, and can't get it out from there.
Any ideas what has happened, and how to solve it?
Thanks
/Per
Try switching active slots? I've heard rumor that slot B may not work.
-
1
-
-
3 hours ago, daniel.schaaaf said:
@tdm Do you know if LineageOS creates a log file when updating? I updated to 10.0-20201026 (OTA), and now a lot of my apps are missing. The corresponding directories in \data\app are gone, even though the app data in \data\data is still there.
It depends on how you update. Recovery and OTA are completely separate. Which did you use? Either way, the data partition should not be touched by the upgrade. Can you spot any pattern with the missing apps? eg. are they all Google apps, or are they all large apps that have auxiliary data, or some other thing?
-
1
-
-
4 hours ago, EskeRahn said:
Reboots about every second hour or so, will try to re-flash, if that does not help, factory reset is next. 16.0 worked really well, but the upgrade to 17.1 was bad. But pretty sure it is the lack of a wipe that is at the root of it. As AICP-Q on what I believe is the same port is stable after a wipe.
My guess is that the wlan kernel driver is causing this. I'm sure it got updated.
-
10 hours ago, fxtec-preorder-47xx said:
@tdmWhat do you think about the differing values of android.lens.info.focusDistanceCalibration? Do you think you could add this to the LOS code? Or try if it improves focus?
You can try and let me know.
-
54 minutes ago, internationaltraitor said:
so does this have google spyware and playstore and needs a gmail account to set up the phone?? or is this a better de-googled software than lineage?
Both run just fine without gapps.
-
2
-
-
2 hours ago, shubell said:
well in the lineage gerrit you can see that a IMS fix is beeing worked on. Can't be working on aicp as it is lieage based, or can it 😉
AICP is not Lineage based. It does incorporate a lot of the QCOM hardware support and a few other things. But it specifically does not use the Lineage SDK. And I think the telephony stack is more similar to AOSP than Lineage. So it is quite possible that VoLTE/IMS is working on AICP. Though I haven't tested it myself, as my carrier still won't work with this device. 😕
-
2
-
-
1 hour ago, benoitjeffrey said:
I'm on volte and everything works well on this side
Oh reeeeeally. That's very pleasantly surprising. Especially when it's broken on Lineage. Thanks for letting us know. 🙂
-
2
-
-
VoLTE is currently not working on 17.1. The developers are looking into it.
-
2 hours ago, hxkafg said:
Does AICP include Lineage's SBC improvements?
I don't know, but my guess would be probably not.
-
New build is up, the link in the OP is updated. Changes:
* Fixed keyboard backlight.
* Fixed incremental file update.
New MD5: 8d557ea563667d1332dd99729fa5e4ca
This is a full update because the existing incremental updater is broken. Future updates should be incremental and automatic, if all goes well.
-
6
-
-
Figured out the issue with the keyboard backlight. Lineage decided they wanted to add the keyboard backlight logic into the Android core (frameworks/base) and delete the keyboard backlight logic from the lights HAL. This is Lineage specific -- neither AOSP nor AICP have it. I made a brief attempt to add the Lineage code into AICP's frameworks/base but it didn't go smoothly. So I'm just going to revert the change and move on. I hope to have a new build within a few hours.
-
4
-
-
I found the issue with the incremental updater. We will try that again with the next build.
-
1
-
-
1 minute ago, Hook said:
It installed fine for me sideloading, and I found the new keyboard settings, but they don't include anything about the keyboard backlight and I can't find any other setting for it. Needless to say, the backlight on the keyboard still isn't coming on by default.
Okay I'll look into that next.
-
2
-
-
Okay I've uploaded the file and pointed the link in the OP to the new one.
New MD5: e6d57186599ab0177a48fc3984c6ae5b
-
1
-
-
10 minutes ago, Hook said:
@tdmI must be doing something wrong. It says it downloads, says install. I tap install, it does something quickly and then gives the prompt to reboot. I reboot and I can't find any new controls (no backlight) and information says I still have 02 NOV build and updater says install again. I've never done OTAs, so maybe I'm missing a step.
Anyone else tried this?
It must be broken. I'll check into it and upload the full zip later. Thanks for testing.
-
1
-
-
10 minutes ago, Hook said:
Where? Is there a page for this. Or did you change the file the link on the OP downloads (I ask because the OP doesn't seem to have been edited)?
Settings, aicp extras, update center.
-
1
-
AICP Q: Discussion
in General Discussion
Posted
Maybe. Stock imposes some restrictions: you cannot modify /system or /vendor. This makes things more challenging.