tdm

Well, if fast poll does not help, I am wondering if there is some sort of hardware issue. The only two things I can think to try are: (1) making the keyboard poll code into a thread that runs at high priority. This would be fairly easy but I doubt it would change much. (2) not using polling at all. This would severely limit the ability to detect certain key combinations, like the bad old original stock keyboard driver. I don't think you or anyone else would want that. Regarding the log size, I can make it larger but I think it would need to be in /proc. I think files in /

I have a package to set the unlock flag without losing data. PM me.

It looks like one of the slots is marked bootable and the other is not. I think they were both marked unbootable before? Try switching slots via "fastboot --set-active=b". If that still does not work, you may have bad flash memory or some other problem that I can't help you fix. EDIT: Also try booting to recovery and see what happens. And last resort, try doing a full flash including userdata. If the device won't boot and it needs to go back to the factory, your data is probably irretrievable anyway. 😞

Okay then your only option is EDL. You must either get my tool to work or contact FxTec support.

It may take a few tries, and you may need to try different hardware. But it does work if you get the combination correct. It is much easier to use the fastboot method. Try that first.

Yes, Pay and Netflix and some banking apps require a locked bootloader. You can lock it again from fastboot.

Oh, I just realized ... since you are able to get to fastboot, why not just use the fastboot method to restore your device? Did you already try that?

That is the fastboot screen. It is entirely different from EDL. See my instructions on how to enter EDL mode: http://files.nwwn.com/android/pro1/factory.html Since you are able to get to the fastboot screen, the key combination (method 3) should work.

18d1:d00d is fastboot mode. 05c6:9008 is edl mode. There is no problem with the flash tool. It has worked for many people, including myself. The only reason it will not work is that edl mode is very picky about hardware. All I can say is keep trying with different combinations of hosts, cables, and hubs. Keep in mind, this is not an official FxTec tool. If you absolutely cannot get it to work, FxTec support may be able to help.

@divstar when you are in EDL mode, it is completely different than adb or fastboot. Neither of those will detect a device. You can run "lsusb" to see the device. It will be something like Qualcomm GOBI modem or such with vid/pid = 05c6:9008. And yes, @EskeRahn is correct, EDL is much picker about your USB setup than adb or fastboot. You may need to try different combinations of ports and cables to find one that works. I've found older hardware, particularly USB 2 (not 3), generally works better. Some people report that putting a low speed hub between the host and the phone wo

The keys are double because there is one entry for press and one entry for release. Backspace, DEL, and a couple others will show "?". Yes, in your log, at the start of the second line, it missed the "i" completely. I find it interesting that most of the time you hold a key for about 10 to 20 jiffies, but those particular lines are the same timestamp: 0000551c <D 0000551c >E 0000551c > In other words, the log says you released D, then pressed E and space all within the same 0.01 second interval. That seems unlikely. But only you can know for

I'm not sure exactly where rollback protection data is stored, but I have never run into issues with it. If we do, I guess I can figure it out. But I try to keep the latest images available. Currently my latest is 20200707, as I haven't gotten a copy of the most recent update yet.

Try my factory restore tool first. If you cannot get that to work, send me a PM and I can try to help you fix it.

Yes, that thread. I guess he thought persist was not necessary. Here is a copy: http://files.nwwn.com/android/pro1/persist.img

You need to clear the fingerprint HAL data in /persist. But since you are on stock you don't have root access. So you need to flash the persist partition from fastboot. Find the thread from Liancheng about how to go back to stock. Get the files. Reboot to bootloader and run fastboot flash persist persist.img. you will reset your WiFi Mac addr but that should fix the issue.

The change to fingerprints, as far as I can tell, was to delete the HAL fingerprint data when you delete the android fingerprint. So if you have "orphaned" fingerprint data in the HAL, this won't fix your issue. You need to clear the HAL fingerprint data to fix it. Thereafter you shouldn't have the problem anymore, unless you factory reset with active fingerprints.

Check logcat for something crashing.

Here is the debug kernel: http://files.nwwn.com/android/pro1/boot-keylog.img The file /sys/devices/soc/c17a000.i2c/i2c-6/6-0058/keylog records the last 256 key press/release events, one per line. The line format is: xxxxxxxx dK Where: xxxxxxxx is the time stamp in jiffies (1/100 sec), in hex. d is the direction, > for press, < for release. K is the key (without modifiers). It will only log the normal keys, not the gpio keys (shift, ctrl, alt, logo). You will need root access to read the file. I suggest an adb root session.

Lineage, like a lot of custom ROMs out there, builds on a schedule regardless of whether there are any actual changes. There are exactly zero actual code changes between 20200824 and 20200831. All of the changes in that week are administrative (adding supported devices, updating the wiki, etc.) So that means: - You do not need to update, there is nothing actually updated. Feel free to dismiss the OTA notification. - The update should not cause any issues if it is applied correctly and successfully.

Yeah, caps lock is a funny thing. The kernel controls the LED, but user space has the logic. So they can, and sometimes do, get out of sync.

Well, I found the first 5 paragraphs rather interesting. Probably because I live in the US, where a large portion of the population exhibits these traits. While I think he does explain some of the tendency to ignore science and facts, I think he completely misses a large portion of the problem -- people who are genuinely against certain things because the status quo favors them over others and they don't want to change because they are selfish. So they simply pretend the problem does not exist, and find people who agree with them and explain their willful ignorance with deception.

Currently sideload does not keep addons, so you must do the following: 1. sideload the new Lineage zip. 2. reboot recovery to switch slots. 3. sideload gapps and/or su. 4. reboot into android. This process takes about 5 minutes. OTA keeps addons, so just install and reboot. But since it is done in the background, it can take up to an hour or so.

Try the factory flash tool. Make sure to tell it not to flash data, or all your data will be erased.

Most likely not. I don't know if there will even be an official stock 10. And if there is, I'll probably make a package to update the firmware without going back to stock.

The device is rather busy for a couple minutes after boot. So the issue is probably load related (as I think we have all suspected for some time). I'm currently out of town, but I'll try to get you a debug kernel next week that shows what keys are being pressed and released. You can correlate that to your typing to see if the issue is in the kernel or in Android.