mcdinner

If there is no downside of using all keys, why not :)

don't want to 😉

@tdm Backlight comes on now when I open the keyboard, but does not turn off when closed until display goes off.

Thx for the new update! I agree with you on a2dp, but the "no audio on voice call when display goes off" should be very high priority. At the moment the ability to use the phone as a phone is 'deminished' since test3.

I'd also like to "send a beer", maybe all europeans who want to donate should get together and collect with one person so we do not "donate" paypal 1Euro international transaction fee everytime.

please don't !

backlight was broken all the time. try this app, it works fine now.

thank you. :) Is there a way to disable proximity sensor while calling? It could work as a workaround to not switch display off while calling.

@tdm thx for the update, did you fix anything except the keyboard mapping? Calls are still broken for me + Audio errors in log. (with bluetooth off)

@tdmThx for the new build, I'll install it soon. Could you update the md5/sha1 susm for the new files ?

Thank you! :) I have microg, Magisk and Xposed installed but at the time the logs were created, i flashed the Lineage SU addon instead of Magisk so Xposed and Magisk Modules should not have been active and interfering. (At least I hope so...) If you need any more infos i can give them to you.

I'm having audio related problem with test3. System gets laggy and the UI restarts from time to time. Audio output from Spotify and other Apps is working. @tdm I appended some logs, any Idea what could be the problem? logs-2020-02-10-23-00-03.tar.gz

FakeGApps also works well.

If it is not too much trouble or you have a link it would be nice to know, don't really need it. I tried to get boot log working a week ago but failed. When lineage boot animation started, adb told me I'm not authenticated. I edited build.prop on the device (via shell 😄) and added persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb Also added the public key from computer to adb_keys. Did not work, guess it was completely wrong.

I'm fiddling around with haystack for signature spoofing. But I think i have problems with it (I had serious audio problems the last 2 days).

I had to clarify, i was unable to get shell in recovery

With the keyboard boot.img I cannot get an adb shell in recovery and flashing magisk module had signature verification enabled.

before wiping, you could try to flash the original boot image to both slots and then flash the lineage boot image again. Not sure at all if it helps, but better than direct wiping. :) few days ago my system also rebooted to fxtec logo and did not boot anymore.

qwerty works as I would expect it. Print on KB matches typed chars. Except arrows 😉

echo I had might be from bot phones in close range wile testing.

YES! ♥️ It works fine until i put my hand over the sensor. It goes on , but after i lift the hand and display goes on again its silent for a while. I can also confirm the echo and when I switch to speaker, display does not shut off and audio keeps going. So seems to be something with display off

@tdm I just recognized normal phone calls (GSM/CDMA) are broken on test3. I can be called or start a call but after a few seconds its just silence on my side and the other phone. After a few seconds call audio and mic is back again for a few seconds, then silence again. This goes on for a while or the silence part does not stop. Call is active all the time. I reflashed to be sure it's not related to other stuff. If you can confirm this, could you build a fixed img soon please? 😉

you know, it comes with stock preinstalled 😉

Yes, no Audio and volume controls after wipe. I also know what @SteffenWi means with the keyboard. No keyboard in portrait mode until i go to the icon on the bottom right and enable "Show virtual keyboard" with the description "keep it on screen while physical keyboard is active".

I'll wipe again and recheck, just to be sure.