tdm

Thank you for noting your github name. 🙂 The aim is to get the keyboard working in the most obvious way possible. In other words, start by: 1. Select QWERTZ under settings -> system -> keyboard -> layout. 2. Select German (or similar) under settings -> system -> languages/input -> physical keyboard -> builtin keyboard. With that done, the keys should generate the symbols as marked, eg: 1. Pressing a key with no shift should generate the white marking. 2. Pressing a key with yellow-arrow should generate the yellow markin

Absolutely. Reading the issue report, there is a modified keymap in comment by rehejuhan on March 10: 11:0033:8033 (, and ; ) 26:002c:0026 (y and |) <- update, not correct, 0026 is just l, not | 30:0011:0029 (w and ^) 38:0013:8029 (r and °) 39:0028:002b (ä and #) 42:0056:8056 (< and >) 47:0026:802b (l and ') Shall I use this?

Following up on @VaZso and his friend's device... we looked at a USB packet capture and determined that everything was fine until the programmer tool sent a request to write to UFS, and the device never responded. I have never seen this issue before on any device. My theory is that UFS is bad and the device needs to be returned for service.

That is great (well, great for reproducing the issue). Can you connect the device to a PC and run "adb shell cat /dev/kmsg" and then cause the issue to happen? Hopefully the device will show a kernel panic message before it resets.

Reboots like this are not tracked anywhere for production devices. I'm pretty sure you are seeing a bug in the qcacld kernel driver (eg. the Qualcomm wlan module). Is there anything particular about this wireless router that might cause the issue? I would like to see if anyone else can reproduce this.

I have access to the stock code and I could do some builds with bug fixes. But I don't see the point. The biggest (only IMO) reason to run stock is for the locked boot loader and play store certification (aka safety net). IdeaLTE does not share the keys to sign builds, so my builds cannot run locked. And, if you really want safety net to pass in Lineage, there are ways to make that happen.

The issue is that data is encrypted. When we get a TWRP with decrypt support, wiping all except media will be possible.

I replied to the issue on github. The timing issue is probably not fixable. But I can look into an option to disable the popup. Or, more specifically, treat the keyboard as full instead of alpha.

@VaZso we should take this to PM to figure this out, and then post the solution here. Please PM me with the best time to reach you. Thanks!

Hey all, sorry for missing out on the last few weeks of posts. If anyone is still bricked and needs help, please let me know.

Hey all, I know it's been a while but .. well .. pandemic and all. I have been doing my "day job" remotely from home with 4 boys running around doing some sort of "school" for a couple hours of the day and being .. well .. being boys the rest of the day. So it's been a bit of a challenge to manage everything and still run side projects. But I think I've got most everything under control now and I'm going to try to drive this thing to the finish over the next couple of weeks. So, as a (re)starting point, I've synced up my Lineage tree and rebuilt from where I left off to make tes

MediaTek doesn't release any open source code. So custom roms like Lineage etc. are very difficult to make. So you are stuck with stock. And further, given that it's all closed source Chinese code, I'm not going to take any chance that it's spying on me.

MediaTek is a hard stop. I won't t touch it.

Hey all, it's been a while since I've been here so I wanted to pop in and give an update. I live in Seattle, which has been under stay-at-home orders for over two weeks and will continue until at least the end of this month. I have a wife and 4 boys at home, and we are all healthy. But it is difficult to get any work done between the constant interruptions. In addition, I have been given a new project at work that will take a week or two to complete. So I'm afraid that I won't have much of any time to work on the Pro1 until at least the middle of April, but more likely the star

Glad you got it to work. Where did you get the idea that the firehose for any of those devices was used? None are, of course. The pro1 firehose is used.

Several minutes, same as actual writing. Yes, I can give you a debug version. But a packet capture with eg. WinPCAP or wireshark would probably be just as useful. Nope, the edl code knows nothing about led or screen or anything else. That's the thing, USB does not have a programmatically settable speed. So you can set the virtual serial speed to whatever you like and the actual transfer speed will be the same.

If xbl is functional this should always work. And if you can get to the point where you see a boot logo when turning on the device, xbl (and much more!) is functional. Try putting the cable in the other way (eg. upside down). @Sean McCreary was unable to get his device into EDL mode using a "deep flash" cable, so he disassembled it to fix it. A couple months later, he found that if he flipped the cable upside down, it worked.

@david you had several posts with several questions so I'll answer them here. Why did I choose to use WinUSB instead of the Qualcomm driver? There are a couple of reasons: The Qualcomm driver exposes the device using a serial port. This is ancient and outdated technology that is difficult to use. At minimum you need to figure out the virtual "com" port number assigned to the device by the Windows device manager. This is unnecessary and confusing. The Qualcomm driver is not installed automatically for all versions of Windows. Finding it and installing it manually is

Did Sprint ever use TDMA? I thought AT&T was the only one that used TDMA (before they moved to GSM)?

I'm not going to say anyone is lying. Certainly it appears that some CDMA data capabilities exist. But it is not fundamentally a CDMA device. I would say that it is a GSM device that is compatible with modern CDMA networks that implement data-only voice services.

That is all data. And I presume Verizon users can get data. Can you make a CDMA voice call? Can you show me your CDMA MEID? Can you operate the device on the network without a SIM card? The answer is no to all three. Any actual CDMA device would answer yes to all three.

Sorry, no. It is not a CDMA device. GSM and CDMA are fundamentally and technically different protocols. Just because Verizon (and I assume Sprint) has seen the future and is ditching traditional CDMA for VoLTE and they can support random GSM devices does not magically make them CDMA devices. On the other hand, if you can take your SIM card out of the Pro1 and still make a voice call on Verizon, like you can with any real CDMA device, then I will retract my statement.

This isn't a Pixel device and FxTec is no Google. You'll be lucky to just get support equal to other manufacturers. Read the Lineage wiki. I'm sure this is covered in detail. Hint: extract-files.sh. If you need to do a full factory restore (you won't if you are careful), just grab the latest fastboot package and flash it, then "fastboot -w" to erase userdata.

I do not have Verizon, so I cannot really fix it. It would be great if we had a developer that did use Verizon. But if none appear within the next few weeks, I'll probably need to have a Verizon SIM card sent to me. However, as this is a GSM phone and Verizon is a CDMA carrier, I see this as a sort of "extra" functionality -- an enhancement request of sorts. It will take a back seat to getting all the other bugs fixed and official builds running.

Production and software updates are the fault of IdeaLTE. Lack of communication is clearly the fault of FxTec.