tdm

It seems f2fs is also supported. And NTFS, if you hate yourself. 😆 https://github.com/LineageOS/android_system_vold/tree/lineage-16.0/fs

Lineage should support ext4 for sdcards. I expect I'll add exFAT support at some point now that Microsoft has opened up the patents. Unfortunately, I doubt you'll see exFAT on stock anytime soon. The most likely path is for Qualcomm to add exFAT support as a standard driver in their Q kernel. But I haven't looked to see if they did that, and I have no idea if IdeaLTE is even working on Q for the Pro1.

Yes, this.

@EskeRahn is correct, the A/B system is for updates. Android (either stock, or Lineage when it's official) will install OTA updates to the non-active slot, then tell the boot loader to switch active slots, and then prompt you to reboot. So no, by default, you cannot use A/B for a dual-boot system. Additionally, there is only one data partition. So any dual boot scheme would require some way to separate data A from data B. And lastly, you would probably want some sort of a boot manager to select the slot at boot time. So in theory, it would be possible to

Catching up on a couple days here... Yes, I'm working with @Digital_Toxin to resolve the locked boot loader. @acrux @schmittlauch I've never installed SailfishOS, so I'm not sure how that would affect the phone. But I can tell you that Lineage uses a different format for userdata (FBE instead of FDE) and modifies boot, vendor, and system partitions. I also suspect that AVB may have something to do with this. Are either of you currently stuck in a place where you are not able to use your preferred OS? @SchattengestaIt the kernel keymap location has been me

I have not completely backed out the double-tap-to-wake (dt2w) changes from stock. That could be what you are seeing. I'll try to get that done for the next build.

Well, depending on the device configuration, a reboot may put the device into "ramdump" mode. This is a variation of EDL mode and can easily be mistaken for being off.

All Qualcomm phones have thermal protection built-in. I have never heard of a faulty thermal sensor, but I guess it is possible. The thermal daemon does copious logging to logcat, so it would be easy to see that. The most common reboot reasons for a production Qualcomm device are a cell modem fault and a kernel panic. The cell modem is completely closed source and cannot be touched, so if that is faulty, the OEM needs to fix it. Kernel panics are possible to fix, in theory, but first the issue needs to be identified with a kernel log. That can be tricky -- the best way is to d

No, it has not changed since test2. Can you figure out how to fix it? I am not familiar with the accents vs. apostrophe keys.

I would prefer not to do that, as it could introduce a security risk. Simply run "adb root" and then make your change. Afterward, you can "adb unroot" or reboot the device. I don't think Android lets you deselect the qwerty/qwertz setting. But yes, the setting is directly tied to that file. Note: In an ideal world, the factory would provide some sort of way to find out the physical keyboard layout. The only difference I can see between a QWERTY stock image and a QWERTZ stock image is in the Android keylayout files in /system. These get over-written with t

Yes, it would be nice to have the Pro1 specific settings sprinkled throughout the settings menus, eg. keyboard settings under keyboard, display settings under display. But doing that requires modifying the code in the settings app, which is not allowed in official Lineage builds. The way I've added the Pro1 settings is the "official" way to add device-specific settings. That said, I could possibly rename and rearrange the Pro1 settings. Perhaps Settings->System->Pro1 could be a separate screen with the keyboard and touchscreen settings. I believe that is key #31

The Pro1 has a combined boot/recovery partition. This is why my Lineage install page instructs you to download and flash the boot image and then boot into Lineage recovery. Great, so you should be able to build your own ROM. Once you can do that, let me know and we can talk about stuff to fix. 🙂

test13 is up. Changes: * Updated QWERTZ keymap. * Addressed some SELinux denials. If you have a QWERTY device, there is pretty much no reason to upgrade from test12. If you have a QWERTZ device, please test and provide feedback. Please remember to remove any custom keymap before testing.

Yes, with the qwertz test2 boot image you may specify AltGr as a modifier. It seems this is very close to the final desired mappings, so I will incorporate it into test13. Because the '?' symbol is generated with shift, you would probably need to choose another key to map for use with the yellow-arrow. Perhaps the "O" key, for example: 44:0018:8035 And, now that you mention it, the SYM key does also generate KEY_RIGHTALT, aka. AltGr. So I am wondering if that is still desirable...? Thanks for the report. Please file an issue on g

This looks interesting: 06-04 13:52:08.223 731 1420 D voice : voice_start_usecase: enter usecase:voicemmode1-call 06-04 13:52:08.224 731 1420 D audio_hw_primary: select_devices for use case (voicemmode1-call) 06-04 13:52:08.224 731 1420 D audio_hw_extn: audio_extn_should_use_handset_anc: AANC enabled in the property 06-04 13:52:08.224 731 1420 D audio_hw_extn: audio_extn_should_use_handset_anc: AANC enabled in the property 06-04 13:52:08.224 731 1420 D audio_hw_primary: select_devices: out_snd_device(15: voice-handset) in_snd_device(72: handset-mic) I

Alright qwertz folks, here's another test boot image. Please try and let me know how the keyboard works. Most keys should be correct, but I may have made a mistake or two... http://files.nwwn.com/android/pro1/boot-qwertz-test2.img Note that I have added a flag for AltGr = 0x1000. So we have: 0x8000 = shift (left shift) 0x4000 = ctrl (left ctrl) 0x2000 = alt (left alt) 0x1000 = altgr (right alt) Note there is only space for one more flag. If more flags are needed, I will probably expand the codes from 16 bits to 32 bits.

Okay I see what's going on with QWERTZ now. All of the incorrect keys (except possibly apostrophe) are accessed via AltGr. So I'll add that as a modifier in my driver and redo the layout for these keys. I should have a new boot image later today.

Audio issues in cars can be difficult, both because it is more challenging to get logs (most folks don't carry their laptops with them in the car) and because each car manufacturer seems to have their own unique BT implementation. First question, how does stock behave? Second question, are you able to get a logcat of this happening? EDIT: Also, please file an issue on github. Issues get lost easily on the forum.

I am not very familiar with international keyboards. It is only through this project that I even learned the basics about how non-US keyboards worked. But I'm learning. 🙂 Unfortunately, keyboards are hard. There are multiple layers of translation involved from the physical key press to what you see on the screen. The kernel keymap is the lowest level, which makes it difficult to choose the correct values that generate the symbol you wish to see. I've downloaded your attached file and each line has three symbols on the left and a comment on the right. I presume th

Yes, this. I was addressing the comment from people that they had installed the ROM but not installed the boot image provided with it. I was just making it clear that the ROM has a boot image. So you cannot eg. install test12 but still have the boot image for test11.

Thanks for the reports. Please note that the separate boot image is provided only for booting into Lineage recovery when switching from stock to Lineage. The main Lineage zip file has its own (identical) copy of the boot image that is flashed along with the rest of the system.

I believe this is your issue: [ 21.543915] msm_sensor_fill_eeprom_subdevid_by_name:222 Eeprom userspace probe for sunny_bl24sa64cs_imx363 [ 21.545076] msm_camera_request_gpio_table:774 gpio 29:CAM_VANA request fails ... [ 21.700128] imx363 power up failed The imx363 device (that is, the camera) is failing to power up -- it's dead, Jim.

Hmm, interesting. It installed and booted fine for me. Is anyone else having trouble with test12?

Thanks. Unfortunately, your output.txt does not really help me, as I don't have a qwertz model. If you can just send the changes to the keymap as you did in the github issue report, that would speed up this process greatly.

Yes, Lineage only writes to a couple of partitions. Mainly boot, vendor, and system. You can return to stock by writing these three partitions from the stock firmware and doing a factory reset. EDL can be very picky about both hardware and timing. I'd stick with the fastboot method to restore. No, this is not the fault of Lineage. The camera stack is completely closed source blobs from stock except for the kernel driver, and I have not touched the kernel driver at all. You can start by getting a dmesg from a fresh boot ("adb