tdm
-
Content Count
801 -
Joined
-
Last visited
-
Days Won
84
Posts posted by tdm
-
-
58 minutes ago, Hook said:
I raised that issue above and tdm said he would look into it.
Yeah it's probably related to the different way of doing custom settings. I'll get that done next build.
-
3
-
-
1 hour ago, Hook said:
Boy, I am enjoying AICP. Pretty much have everything I want without root, though I hope a simple SU option is coming. I tested the Magisk zip that works flashed via recovery in Lineage 16 and it doesn't work. I don't like magisk enough to do the whole patch the boot dance. Really, I just want SU, like addonSU.
@tdmam I overlooking a buried setting or is there no keyboard backlight in this ROM. Not a big deal as I don't type often in the dark, but I would like it to work.
Very solid, stable ROM so far! Reminds me a lot of Dirty Unicorns.
The device specific keyboard settings are a bit hidden because AICP does not use the same methods for adding to the settings menus. So I'll have to check on that.
-
1
-
1
-
-
-
5 minutes ago, Breeze said:
Hi!
So firts update the recovery to 17.1. Can i flash the new LOS 17.1 using the SDcard method? And keep my data?
I use openGapps already. But what i understand i have to download and install it again with the new LOS 17.1?
sdcard should work, but I haven't personally tried.
Yes you need a gapps that matches your android version. So, for example, opengapps for Android 10 (and arm64, of course). Don't forget to switch slots with reboot/recovery before installing gapps.
-
3
-
-
I think I've found where the issue is in the QWERTZ settings. I have a patch up to fix it now.
If anyone is interested...
https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/292350
-
1
-
2
-
-
1 minute ago, EskeRahn said:
The settings section where we could set the layout and other keyboards options seems omitted in the 17.1
Interesting. The code is still there, and apparently still being built. @npjohnson do you know anything about this?
-
The 16.0 recovery should be able to flash 17.1. Give it a try.
The keyboard driver in 17.1 is the same as 16.0, as far as I know. I suspect something is preventing the qwertz flag from taking effect for @EskeRahn ... logs would help with that.
-
1
-
-
15 minutes ago, EskeRahn said:
I waited about half an hour or so... After a wipe it booted quickly.
Will try the Pre-production unit too without the wipe, as this got qwertY.Do we need to remove the mindthegapps while still on 16.0 before the upgrade? Or should installing opengapps in the 17.1 process fix it?
If you sideload, gapps does not migrate, so you do not need to remove anything.
I do not believe major updates are distributed as OTA so that path is not possible.
I cannot say why your upgrade failed without a log, and that is no longer available I guess.
-
1
-
-
Lineage upgrades should always succeed without wipe, even major versions. This is independent of gapps though, you are responsible for that.
Keep in mind that first boot after a major upgrade takes a long time. I would give at least 5 minutes before giving up.
-
2
-
-
The first Lineage 17.1 build has been posted on the official download site. Please note, I have not really been involved with this version and I am not running it on my device, as I prefer AICP. I would suggest @EskeRahn create a discussion thread. I'll probably monitor that in case any issues arise and need pointed out to the current developers.
-
1
-
3
-
-
On 11/4/2020 at 12:04 PM, proprog said:
I have no luck with LOS and swedish keyboard on my QWERTZ phone. Whatever I try I can not write the swedish characters and @ with the same configuration. One of them is always broken (at the moment I can write å, ä, ö but yellow key plus q just gives a capital Q). I have tried with and without FinQWERTY with no luck. All help is appreciated.
The Lineage keyboard driver tries to make the keyboard look like a "normal" keyboard to Android. Because the print is in German, the default QWERTZ layout is the same as a German keyboard. I would be happy to work with you to adjust this for Swedish. Please send me a PM.
-
1
-
-
1 hour ago, Wheeljack said:
I'm only seeing the 17.1 build in the queue for today. I don't know if there were cases where 16 and 17 builds for the same device were run side by side.
On another note... I'm running 16.0 with MindTheGapps. What are my options when upgrading to 17.1 (since OpenGapps is recommended now)?
I'm using opengapps nano for Android 10 on AICP Q. It works fine. So I'm sure it will work fine on Lineage 17.1 also.
-
1
-
-
1 hour ago, claude0001 said:
Bumping my question from above as the silence about this worries me a little bit. After all, LineageOS 16 is the very topic of this thread.
I was hoping to keep LOS 16 on my device for a while, not expecting it to be abandoned so quickly.
I worry that 17.1 will not work as a drop-in replacement for me due to the absence of AddonSU, which was a nicely integrated and low-profile root-management solution. I require permanent root access for several things (SSH server, Debian Chroot, cross-system file management), but I obviously do not want random apps to be able to su all the time.
I read about magisk of course, but it is not an "official" solution and a much heavier application - two facts I worry about in such a (safety-) critical system component. Also -- from what I read at least -- it is much more tricky to install (does not work with Lineage recovery, I guess) and integrates less nicely into Lineage (does not survive OTA updates?).
So ... could anyone with background knowledge comment on the future of 16.0? Do I have to prepare for the transition already? @tdm, maybe?
Only 17.1 will build now, but you are free to keep 16.0 as long as you wish, and even build yourself when new security updates come in.
-
2
-
-
Is anyone actually running this? I don't see any evidence, so I am not putting any effort into it.
I found an issue with WiFi not connecting, but I don't know if it is just my device or not. The issue was some unrecognized data in a WiFi data file. I upgraded from AICP P without wiping my data, which I know users never do... right? right? 🙂 🙂 🙂
-
2
-
-
1 hour ago, EvilDragon said:
@tdm: Are you aware of such a driver change? Maybe this would be something that should be included in the next LineageOS versions as well?
I'll try to find out more about it - but maybe you know about that already or have an idea what this could be 🙂
Sorry I am not familiar with the hardware on this level. It is possible that the new screen is different in some subtle way. Or perhaps it is possible you got a defective screen. I know others have changed screens without any apparent issues.
-
1
-
-
7 hours ago, jamescarruthers said:
Any chance of the upgraded keyboard files being in the version 17 LOS files? I had a really busy few days at work recently which would have been a pleasure on my Passport but were quite trying when typing fast on the Pro1 with LOS: random extra characters, deleting the odd few words and moving the cursor of its own accord now and again!
No but if I can get the issue sorted out and fixed I'll get that change in both versions. Are you willing to test?
-
1 hour ago, EskeRahn said:
A LOS question from another thread
This is not limited to Swedish. How do we get to standard symbols like these? It is accessible when German is selected though.
I'm not super familiar with Intl keyboard layouts, but my guess is that keyboards for these languages are different than German. I setup the key map to match the labels, which I believe is German.
Since the key map is fully customizable, I could add options for the language in settings. Say, qwerty, qwertz/German, qwertz/Swedish, etc. But I would need help getting those right.
-
1
-
-
16 minutes ago, CornholioGSM said:
@tdm ....and will be new AEX too? 🙂
Maybe, if I can find the time.
-
1
-
1
-
-
1 hour ago, claude0001 said:
OK. Problem solved (for now).
I re-flashed the same 16.0-20201026-NIGHTLY-pro1 via sideload and guess what: GPS is working again. Previously it had been installed via OTA update. No idea what may have gone wrong there.
Thanks to all for your support.
Are you using gapps or not?
-
2 minutes ago, daniel.schaaaf said:
May I ask why you don't want Magisk on your phone? In my opinion, Magisk is as important a "tool" as the Xposed framework. Being able to modify /system without actually touching the system partition is ... magic 🙂 Magisk also brought Xposed to Pie and Oreo with Riru. OK, it gets fishy and suspicious here ... despite that, I would not touch a phone I could not run Magisk and Xposed modules on 😁
These tools change the way Android works. If they have a bug or if they are misconfigured, it is difficult to track down the issue. So users will frequently file bug reports against the device in Lineage and waste developer time trying to reproduce an issue that doesn't really exist.
For me, personally, I don't like to give that kind of power to any program that I have not personally built and reviewed. And both of these tools are complex enough that I'm not going to go through their source code. Further, they both have a modular system where anyone can contribute. This means that there are invariably modules that are poorly done or even broken. And when you have poor quality modules with such a powerful tool, it is a recipe for much pain and failure.
And finally, I simply have zero need for either of these. I have a working device that does what I want. I would rather cast my "vote", so to speak, by not running a SafetyNet enabled package than emboldening companies to continue abusing user freedom and choice. That is somewhat easy for me, as my banking app is not SafetyNet enabled. But if it was, I would ditch the app.
-
3
-
5
-
-
7 minutes ago, claude0001 said:
Thanks, Eske.
I remember that I was able to toggle the AGPS setting somewhere (in Settings -> Location -> Mode according to the "Internet"). I suspect I set it to "device only" recently, disabling Wifi-assisted GPS. Now I think this may have been a bad idea, but cannot find the option to re-enable AGPS anymore.
Was something changed in this respect in LineageOS in the last ~ 2 weeks?
There were two changes around the location provider overlay about 2 weeks ago. But I don't think that should affect your ability to get a lock.
-
1
-
-
2 hours ago, Hook said:
@tdmIf we want root, do we use Magisk or is there another way?
Good question. I had not actually checked. It seems "su" is present in their sources, but does not build by default. This is the good old bog standard "su" that ships with AOSP, no integrations with Privacy Guard or anything like that. So I have to assume everyone who uses AICP and wants "su" is running magisk. But I'll look into it some more, as I refuse to install magisk on any of my devices.
-
1
-
3
-
-
4 hours ago, daniel.schaaaf said:
AICP has an impressive list of features: https://github.com/AICP/vendor_aicp/blob/q10.0/docs/features.md
It looks like they implemented features from GravityBox and other customisation apps and Xposed modules.
@tdm Will AICP be maintained like LOS, or is there a chance development for AICP will stop sometime in the future? I don't have a clue about how much work is involved in maintaining two or three Android varieties instead of just one.
I will be maintaining AICP for a long time, I'm sure.
-
2
-
4
-
-
For those asking why AICP, I personally have two main reasons:
It has more customization options than Lineage.
It is more fun to work on, Lineage takes themselves too seriously.
I've been using custom ROMs on my devices since my first Android phone in 2012. I have always run AOKP for the above reasons. But AOKP is gone now and AICP fills the same needs for me.
That said, I'm aware Lineage is perfectly fine for a lot of folks. That's great. The beauty of it is that you can choose what you like. 🙂
-
5
-
2
-
AICP Q: Discussion
in General Discussion
Posted
I just put up an incremental ota with the keyboard settings fix. I don't have time to test it myself right now so you guys are the guinea pigs. 🙂 Please let me know if it works. No need to futz with gapps, just install and reboot.