netman

I think I had tried those and failed, most likely just because of user error rather than them not being capable though xD

I've used this tool with success to modify both stock and lineage boot images: https://github.com/vianney/bootimgtool bootimgtool -x -v qcom To extract, and then to repack it, if i recall correctly: bootimgtool -c -v qcom -p parameters.cfg -k Image.gz-dtb -r ramdisk.img To replace the kernel I stole the DTB from the kernel in a boot image with https://github.com/PabloCastellano/extract-dtb and just used cat to append only the first one of the extracted DTBs to the new kernel (only that one appears to matter at all).

It's a known bug that happens for everyone I believe, the intention is probably to have this happen only when opening the camera from the lock screen so that people cannot spy on your pictures without unlocking. Most phones / camera apps I've used even allow gallery access from locked phone but only to new pictures.

For me this did not make a difference as far as i could tell.

This works in portrait for you?! I had no luck with it. I've searched high and low and what I found is that for whatever stupid reason Android only allows resizing the split screen in portrait mode but even that didn't work for me. I hope someone finds a workaround though.

This happened to me too, clearing it's data and cache seems to have permanently fixed it. I think it broke because of OTA coming in and not liking settings from a previous version of the app, or something like that.

For me it worked to just reboot and retry a couple times to get to the final update.

The F and J key nubs have been corrected in production version though if I am not mistaken.

Finqwerty just provides a bunch of .kcm files to android via an API. Where I imagine that could become difficult is that currently there are mappings that use fn-key combinations that are not any fn-key combination on the physical print, if the driver absorbs the fn key events there would be no way to remap those combinations in userspace I guess. A possible solution would be to provide an extra extra physical layout on the driver level as suggested for qwertz, where fn is a normal key and the user can figure out how to use it.

Won't this make handling different physical layouts like the qwertZ version of the phone and having custom mappings such as with finqwerty more difficult?

In these kinds of situations it may be worth sending the insurance company in question an e-mail and asking what they can do, I think.

i'm mostly shocked we only notice this now 😄

For now I don't think there's a solution for think, however I want to tell: the concept described is called "sticky modifier keys" if I understood you correctly.

That's really interesting! If it happens again try all numbers on the number row (edit: maybe try first the letters in the row above the one with f and j) first and let me know! (this goes for anyone that experiences the bug)

Video from @altwouss does seem way more rattly than my unit does... Does the screen move around loosely when the device is open? Mine does make a slight sound when i shake it but nothing appears moving or loose.

All the others would include n97, e7, n950... In my opinion they made the best possible choice.

This is amazing :).

The bubbles can go away over a few days if they aren't huge :).

From my PC I got 90wpm on the same test I posted above.

Certainly more like normal linux than android is, wayland instead of the familiar x11 on maemo, zypper and rpm for packages like on opensuse instead of apt/dpkg. I'm sure some of people here will be able to add to this :).

Sailfish not floating your boat either?

Me too :D.

I'm fairly sure it's a software bug that got fixed by the last OTA update. I was wrong, update to fix this is to come I had wrongly remembered from reading that.

My thumbs would probably burn before reaching that speed xD.

It sounds exactly like what I am doing here: https://community.fxtec.com/topic/2681-how-to-openshut-the-pro1/?tab=comments#comment-42057