tdm
-
Content Count
801 -
Joined
-
Last visited
-
Days Won
84
Posts posted by tdm
-
-
18 minutes ago, Slion said:
@tdm does FinQwerty and the likes even work as intended on LOS since the keyboard driver was changed and the keyboard was set to ALPHA?
Stock qwerty provides things like Alt + U for umlaut dead key I believe. FxQwerty provides possibly more of such international characters though the current version is geared more toward French than German it does give you ß with Alt + S.
I don't know, I don't use a keyboard mapper because the keyboard works as it should in lineage.
My impression is that most people use a keyboard mapper on the stock pro1 only because it is so broken. But that could be off.
-
1
-
-
1 minute ago, Slion said:
My point exactly, slant arrow is Fn on stock.
I think you misunderstood my point. When you press '/' on a normal keyboard, you don't do it with Fn down. That is incorrect behavior from the keyboard driver. An app would be within reason to interpret this as Fn+'/' and do something unexpected, or nothing at all.
That said, it is very much possible to make the slant arrow into Fn modifier for the keys without yellow labels so you could press eg. Fn+1 and get F1. In fact this is one of the standard customization options on Lineage. You can do this with any key(s) that you choose.
-
2
-
-
2 minutes ago, Slion said:
It's also there to give access to missing standard functions, yellow labels in our case.
Which missing standard functions are you referring to? The only yellow labels I see that isn't on a standard PC102 keyboard are the emoji label on Alt and the WWW label on the spacebar. Both of these are functional on Lineage.
-
2
-
-
2 minutes ago, Slion said:
I'm confused, I'm pretty sure that's what stock does.
I am pretty sure it's not. Try running getevent on stock and then pressing Fn+P to get a forward slash. You should see key down for Fn followed by key down for '/' or something similar.
The Lineage kernel tries to emulate a normal keyboard as much as possible because the stock way of doing the keyboard is pretty awful. You must leave keyboard layout unconfigured or things break. Which is very confusing to many users because Android tells you to configure the keyboard layout. Further, because of this, you cannot leverage any of the locale specific keyboard layouts that ship with Android.
Sorry, but I feel strongly that avoiding all that awfulness by making the slant arrow a dead key is a huge win.
-
2
-
1
-
-
7 hours ago, Slion said:
That's rather unfortunate. Slant arrow AKA Function AKA Fn has been a common feature on keyboards for years. Mess with Fx and Sym keys if you want to but leave the common modifiers untouched on the default keyboard layout to avoid such situations. Replacing Function with Alt is like replacing Ctrl with Shift, it does not make sense, not in a default configuration anyway.
Okay, a few things to note here:
The slant arrow is not a standard key. Unless I missed something, it is never stated anywhere that the slant key is supposed to be a Fn key.
Certainly most keyboards have a Fn key. But it was not on the original PC102 keyboard and it is not difficult at all to find a keyboard today that lacks one.
Now, as for actually handling the slant arrow key: (1) How would you propose to do make it behave such that one can make it both act like a Fn key and have the yellow labelled keys be available without extra keystrokes being reported? Any solution must also work with userspace key repeat. (2) Why is it useful to have a Fn key at all, given that the Fn key is a non-standard key and exists to provide access to non-standard functions like sleep, volume, etc. while the Pro1 has no labels for non-standard functions?
-
3
-
-
Keyboard mapping is fine with kcm files. You can map characters in both stock and lineage. Find the people that use FinQwerty, they can probably tell you more.
-
1
-
-
9 minutes ago, JooJooBee666 said:
FWIW, I thought I should note on this thread why my device was no booting anymore, even on a new build: Magisk. Some of the recent changes must have broken this. I tried an older version and the latest from the canary channel, same problem. Back to standard SU for now.
Thanks for noting that.
Now it is clear why developers don't like nor support magisk. My fault for not asking if you had it installed.
-
1
-
-
It is possible that the Lineage GPS configuration files are not optimal for certain areas. Me or one of the other devs can look into that.
-
3
-
1
-
-
2 minutes ago, Hook said:
I don't know what you use to determine fix-- I only ever use Google Maps and it always does a good job of telling me where I am and where I have been. If there is some app I need to tell you exactly what you need to know, let me know and I will test.
There are several GPS test apps in the Play Store. I use "GPS Test" by Chartcross Limited. No reason for that particular one, really, except it's the first one I found years ago when I first started developing for Android.
Another one I always have installed is "Sensor Box for Android".
-
1
-
-
26 minutes ago, marmistrz said:
I have recently updated from test16 to test22 and today I noticed I can no longer get a GPS fix. SatStat sees a couple of satellites, but marks them red. I attached logcat. I tried clearing the data for com.qualcomm.location and FusedLocation, but it doesn't help.
I haven't updated to the official releases yet, but since test22 and current official are mostly the same, this shouldn't matter. Let me know if I should try it.
I'd prefer to avoid wiping everything for obvious reasons.I can get a fix -- possibly a bit slow, but it works. Any one else having issues?
-
33 minutes ago, JooJooBee666 said:
That's what I did. I added the following to system_prop.mk:
# ADB Overrides PRODUCT_SYSTEM_DEFAULT_PROPERTIES += \ persist.service.adb.enable=1 \ persist.service.debuggable=1 \ persist.sys.usb.config=mtp,adb
Rebuilding now. Should that work or do I need to do more?
Let's not spam users with dev stuff. PM me if you need further help.
-
1
-
-
20 minutes ago, JooJooBee666 said:
@tdm Do you know what I need to do to allow ADB Shell to work from recovery?
adb should be enabled, you just need to auth. Extract your boot image, add your host adb key to /adb_keys, repack, and flash. Alternatively, instead of adding your key, you can disable adb auth in default.prop.
-
34 minutes ago, EskeRahn said:
Real-time clock (RTC)
The RTC module found on the PM8998 PMIC block works with
CONFIG_RTC_DRV_PM8XXXenabled. It can be easily tested from userspace like so:# cd /sys/class/rtc/rtc0/ # echo $((`cat since_epoch`+120)) > wakealarm
After running that and fully powering down the device it should power on by itself soon afterwards (2 minutes later to be exact).
Sorry, I misspoke. Yes, there is an RTC. Yes, it can be programmed to power on for an alarm. No, it cannot keep time while off.
-
1
-
2
-
-
4 hours ago, Wheeljack said:
Where would I run "tar" from? Within the adb root shell? How would I stop services? Do I need to be in system/bootloader/fastboot?
Anyone willing to write that up in a bit more detail? I'd really like to test some bluetooth things on stock but would then want to return to the current state Lineage is in.
Yes, you would run from the adb root shell. You stop services exactly as I said, with "stop". It is assumed that you would be running Android (which is the only place where you have both an adb shell and unencrypted data).
I haven't really tried this, so if your data is important, it may be wise to boot into recovery and save off a "dd" copy of the userdata partition just in case it doesn't work. That is a challenge in itself, though, because there isn't any place on the device to put that amount of data. You need to have a large enough sdcard to hold the data or stream it to your PC.
And to be completely honest, if you are asking these questions, I'm not sure you really want to be messing around with backup/restore of data that is super important to you. I'll get TWRP decrypt working before too long, and I can do the factory package stuff myself easily enough.
-
4
-
-
1 hour ago, raymo said:
Hello, I'm using Lineage since build test18. Great work ! I have also two issues, one with sms/mms sending, it work but only when he wants. Perhaps I send a sms or mms in a few seconds, sometimes it doesn't send anything for two days. Maybe issue with operator I don't know (I'm in France, SFR Mobile) but it worked well with an old samsung.
Second issue is with time/date : everytime I shutdown the pro1 I have time reinitialised at 20 july, 4h17 am. So no awaking clock available, and I can't work with that if no network.
I have done a full reinstall with the last official Lineage (fastboot *.img and adb *.zip, with Mindthegapps and su-add) with complete wipe data, but it looks same as it was. Maybe somebody has an idea, something I can do ?
Thanks (and sorry for my bad english)
The SMS/MMS issue is most likely an issue with your operator/carrier. But even if it is the phone, all of the radio code is closed source and copied exactly from stock. So I almost surely could not fix it.
Unfortunately, Qualcomm devices do not have an RTC. So the date/time needs to be set at each boot. Normally, the date/time can be set via either a broadcast from your operator/carrier or via NTP with a WiFi connection. But when neither are available, the date/time is indeterminate. Qualcomm does make some attempt to save the current date/time at shutdown, but this code is closed source so I do not know exactly how or why or when (or if!) it works.
-
2
-
-
3 minutes ago, JooJooBee666 said:
I have wifi calling enabled, but I'm pretty sure it's not working. Whenever I call out, it switches to H+ (or doesn't and fails). If I force LTE, the call just ends immediately. So I cannot call with LTE only, VoLTE or not.
Does AT&T VoLTE work on stock?
-
6 minutes ago, JooJooBee666 said:
@tdm This problem started before the official builds here, but I've had issues the last couple of months trying to make calls. They usually fail the first time, not always. Just kept forgetting to mention it as I don't make many calls. However, it happened again today and I thought I'd get take a look at the Radio logs. Seeing this repeated message over and over again:
7-23 12:52:54.500 2064 2230 D LocaleTracker: getCellInfo: cell info=null 07-23 12:52:54.500 2064 2230 D LocaleTracker: Can't get cell info. Try again in 2 secs. 07-23 12:52:54.500 2064 2230 D LocaleTracker: updateLocale: mcc = null, country = 07-23 12:52:56.508 2064 2230 D RILJ : [8132]> RIL_REQUEST_GET_CELL_INFO_LIST [SUB1] 07-23 12:52:56.522 2064 2179 D RILJ : [8132]< RIL_REQUEST_GET_CELL_INFO_LIST error 39 [SUB1] 07-23 12:52:56.523 2064 2179 D RilRequest: [8132]< RIL_REQUEST_GET_CELL_INFO_LIST error: com.android.internal.telephony.CommandException: SYSTEM_ERR ret=[] 07-23 12:52:56.524 2064 2064 D SST : [1] EVENT_GET_CELL_INFO_LIST: error ret null, e=com.android.internal.telephony.CommandException: SYSTEM_ERR 07-23 12:52:56.525 2064 2230 D SST : [1] SST.getAllCellInfo(): X size=0 list=null 07-23 12:52:56.525 2064 2230 D LocaleTracker: getCellInfo: cell info=null
Also a bunch of these:
07-23 12:56:33.349 900 1187 E RILC : oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL
I attached the entire log for review. It starts right at the beginning of me hitting send and ends right after it fails. Provider is AT&T.
Thanks for the detailed info. Unfortunately, I don't see anything specific to Lineage that could be causing your issue. The RIL handler is closed source. The only thing you could try is replacing your libril with one from an older build and see what happens. But the issue might just be your provider.
6 minutes ago, JooJooBee666 said:Also, on a side note, since AT&T claims 3G is going away in F1b 2022, what do we need to do to get VoLTE working here on this guy?
Nothing uses 3G anymore. You should be fine. But VoLTE is working on Verizon, I believe, so it will probably also work on AT&T. Give it a shot.
-
Note:
This thread maintains the full factory packages with a user friendly tool:
https://community.fxtec.com/topic/2559-factory-restore-tool/
It uses EDL which can be finicky, scary, or otherwise problematic for some folks. So a fastboot flashable zip with a script is nicer for many users.
-
50 minutes ago, dicer said:
Cool! This means I could "restore" my phone with the restore tool, extract all the necessary firmware partitions and make them available for manual flashing via fastboot.
Yes, you could. But I have the original factory package (from @Waxberry) which was used to make my factory restore package. It is much quicker and easier to make a fastboot package directly using the original factory package. Plus you get the original sparse images which are much smaller than full images.
So either I could give you the images from the factory package with Chen's approval, or he could go ahead and make another fastboot zip like he did before.
QuoteDoes anyone else know if I can make a backup of my data partition with the currently available TWRP even without encryption support? I guess that the encryption key is probably stored in a hardware vault on the phone and I won't be able to restore the backup on a different phone, but it might work on the same one? As long as the key does not get erased by stock or the factory reset tool...
Yes, this does work. You just "dd" the userdata partition. The encryption footer is on the userdata partition, so that comes along for the ride. And yes, the hardware key is burned into the device and is (or should be) unique for each device. So in theory your backup should restore fine on your phone and only your phone.
If you have root, you can also try a "tar" backup from Android. Just stop everything ("stop"), make a tarball of /data, and start everything again (reboot or "start").
-
1
-
-
5 minutes ago, marmistrz said:
Well, the point is that even while building in-tree, I won't be able to build the kernel unless I apply this patch. It looks like `make bootimage` (and in general the kernel build system) uses the host compiler at some early stage to compile dtc instead of the Lineage DT compiler. This makes sense, because the Lineage DT compiler is an arm64 cross-compiler and dtc will be run on the host and needs to be an x86 binary.
SHIPPED scripts/dtc/dtc-lexer.lex.c HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTLD scripts/dtc/dtcOkay, I can see this conversation taking up several dozens of messages in this thread. Please contact me in PM and we can find a way to chat without spamming users.
-
1
-
-
2 minutes ago, marmistrz said:
@tdmwe need to cherry-pick this commit to enable build of gcc 10 hosts. (dtc is built using the host compiler)
https://github.com/torvalds/linux/commit/e33a814e772cdc36436c8c188d8c42d019fda639I don't see the point.
Once you get the DT compiled, how are you going to generate the overlay? And then how are you going to generate the initrd and the boot image? The only practical way, really, is to use the Lineage source tree. So if you are already using things from the Lineage source tree, you can use the Lineage DT compiler also. And as long as you are at it, you might as well use the Lineage cross compiler.
-
10 minutes ago, itsdevilslettuce said:
Hey. I've been playing around with the official build and noticed that the fingerprint doesn't work very well on the lock screen and sometimes works within apps that can use fingerprints (banking apps). However when rebooting device the fingerprints are no longer saved.
I looked back in the test build forums and found the post regarding removing all the files within the /persist/data/fingerprint ... this directory doesn't seem to exist in the official build.
I did a full wipe and clean install of official build and recovery.
Hmm, thanks, I'll take a look.
Note the /persist partition is not wiped when you do a factory reset. I have a script in Lineage that deletes /persist/data/fingerprint at boot when the Android fingerprint data does not exist (eg. after a factory reset) so that Android and the fingerprint HAL can stay reasonably in sync. The fingerprint HAL should be re-creating that directory when you first enroll a fingerprint.
EDIT: Also note that the fingerprint HAL is entirely closed source. The only possible changes have been in updating the vendor blobs from the 6/22 OTA and the 7/7 OTA. But I just checked and it seems the fingerprint blobs have not changed at all.
-
1
-
-
1 minute ago, marmistrz said:
Thanks for your reply. I'll try building it within the Lineage tree.
You mean an entry in the settings app, so that people can toggle it without command-line tweaking?
I can't join the Telegram group without providing my phone number, which I'm unwilling to do.
Is there any IRC/Matrix/XMPP/... room/bridge?Yes, an entry in the settings app to toggle sticky fn. Because surely some users will want it and other users will not.
I'll try to think of a way. But I do not know of any other Pro1 group except on telegram. I do sympathize with you, though. I really don't like giving my phone number for internet chat. It is just that with all other modern privacy and security concerns, it seems a small thing in comparison.
-
1
-
-
First, thank you for volunteering to contribute. I've been working my figurative butt off for months and I'm getting tired, to be honest. Which is why Nolen is doing Lineage 17.1. More inline...
14 minutes ago, marmistrz said:1. Add a possibility to turn off autocapitalization
Check the keyboard files. This is probably in the KCM file, if it can be changed at all. Notice the keyboard is declared type ALPHA. If you declare it type FULL, I believe both autocapitalization and the symbol popup will go away.
14 minutes ago, marmistrz said:2. Implement sticky fn. The idea here is to store a boolean flag `fn_sticky_pressed` and set it `aw9523b_check_keys` while checking the state of the keys
Certainly. And add a device specific setting to toggle sticky fn, I assume.
14 minutes ago, marmistrz said:What's the correct way of building the kernel?
Build it in a Lineage tree. There are tons of articles and tutorials about how to build Android generally and Lineage specifically, including those on the Lineage wiki. For just the "kernel", you want to build the target "bootimage".
While it is possible to build the kernel outside the Lineage tree, it is going to be difficult as you can see. Not only do you have compiler versions to contend with, you also have the DT -- the Pro1 uses a so-called "DT overlay", which requires and Android tool to build. Further, once you get the kernel built, you cannot just flash the kernel. You must flash the boot partition, which also includes a ramdisk and a special header.
And finally, this is not really a development thread. Perhaps we could communicate another way? There is a Pro1 telegram group that would work.
-
2
-
PRO1, LineageOS 16.0 Official Builds: Discussion
in General Discussion
Posted
Nice!
Note that 17.1 will be relatively easy with 16.0 working. It should be ready within a week or two. Nolen and Ethan are making great progress.