EskeRahn

ADD: A really low priority bug. When attepmting unlocking with the fingerprint scanner from display-off it quite often does not work.. If I then press Power and tries again (from the lock screen) it (AFAIK) always works, including the haptic feedback. I THINK it is could be related with how deep it sleeps, that is if after a while in lock it might work if by some chance I touch it while a wake lock has woken the system, e.g. to check mails. But that is pure guesswork. This is absolutely a low priority issue, but just to the list to remember if more important things fails to do as ex

(lineage-18.1-20210920-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.

An odd bug with 1.1.3, on AICP-R: It very often auto-opens when lid closed, after some seconds. (with the "....screen lock aborted") It MIGHT be related to the motion detector, as it seems easier to have it stay off when on a table. But there are no full correlation, at the best a tendency, but could be multiple factors, that effect when it triggers and when not. A not too slow 'close-open-close' on a table seems to work quite often.

Just an idea on Lineage. Perhaps you should grey-out or hide the screenfilter when on lineage, until you find a workaround? In the Advance settings I guess the four key-filters are irrelevant to Lineage too, right? If so you might hide (or disable) when on Lineage. I know that on stock you had to use the proximity sensor to wake the screen, as the hall sensor did not fire. Does the same go for Lineage?

Thanks for your guidance. 2½ years ago I started on a project doing exactly that, but lacked the information, I will try to find time to finish it. If anyone wants to finish it, or fork it PLEASE feel free, it is in simple C# and feel free anyone, all I request is if someone uses it to make something useful, is that I get a copy. 😁 (Just reopend it, and it is currently not much-more than an UI template) I had an idea that it should have some 'layers' that could be shared/imported by dfferent languages. say you had a math-layer that you mapped to Ctrl+Yellow, Or whatever, someo

The funny thing here is that if you on a PC with a keyboard with 'tall' Enter key select US-keyboard (That is what I normally use), then you will find \| IS placed next to Z, so the two keys seem to be wired the same - rather odd... I have not checked their scan-codes. That is the key in e.g. UK keyboard three right of L is new, and NOT the one above Enter in the US-layout, that one is MOVED to left of Z. Strange...

(Just downloaded, will flash within minutes 😍) It did not install with the previous AICP-q boot.img, but it did install with the latest LineageOS 18.1 .img open_gapps-arm64-11.0-pico-20210712.zip installed as well. So now i'm back on AICP after being 'unfaithfu'l using LineageOS 18.1 for some weeks on the 'final sample' too. Lovely. 😁 Battery saver "Battery may run out soon ....blah blah .... 40%" I would say that kicks in a little early.... But it was when it still installed apps in the background, so the projected remaining time was low as could be expected. I usually turn

Thanks @tdm, links added here 😁

I like Slions version, except I would swap the backslash and back- apostrophe keys. to more usual placements, and especially in light of other qwerty-based languages where the accents are usually on the right side

Thanks. But if it ONLY works with German, this seams to break the whole original idea of letting the qwertz/qwerty switch select all the necessary remapping to get a standard layout so ANY available android standard layout could be selected, fitting the users language. ADD: Obviously if I select a qwerty based language on the qwertz keyboard with the qwertz switch, I EXPECT the letter between T and U to send a Y, and similar others will not match the print. (and obviously similar issues the other way round) No better or worse than if I selected to write with another language on a phy

Ah I see. Please note that their support mail system (zendesk?) works in a way collecting mails in the queue, so sending in a new mail pulls back the previously mail to the end of the queue.

I currently have two Pro1s on Lineage, and am unable to reproduce the issue, no matter how much I let it charge or discharge, and no matter if it is a slow or quick charger. One of them recently factory reset (had AICP on it before). So unless there are unknown hardware sub-variants, it must be something different we got installed that somehow triggers (or remedies) the issue.The only explicitly battery-related I got installed is GSAM battery manager, and 3C all-in-one Toolbox. Both just monitoring the usage.

Sad to hear. But just to be sure, are you on stock Android or LineageOS? (Some are having charging-issues on Lineage)

As I read what @3zet writes, the point is if you have some software that stops charging when full (to prolong battery life when constantly connected). Charging ought to be accepted again once below a certain threshold.

(lineage-18.1-20210913-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.

My guess is that the OP was asking if you could keep some spare batteries (say in your backpack during a hike) for a quick swap anywhere.. And to that the question is definitely NO (But nice that it should be replacable once worn down, but I would not call it "easily")

Note that some navigation apps tend to be smart, so if you move at some speed along a road it will snap you to the side of the road it expect you are. (so this could muddle things further)

Sorry. I was not trying to say that the GPS on the Pro1 is bad. What I meant to say was that it is surprisingly good on the Titan.

Well apart from a good idea, that IS also good news, as this means it is not too deep down the sound is filtered, so that increase the chance of a fix - though I certainly will not hold my breath for it. I would suggest using a dedicated app you do not normally use for video and set it to the lowest possible video-resolution, e.g. 320x200 if offered, as this would mean a less huge intermediate file for long recordings.

Indeed, and it sounds similar to what you get using it for calls hands free. If you talk loud and clear as you would at a (physical) meeting, it works fine. But if you talk in a normal voice, the other end complains that they can not hear what you are saying.... It has -unfortunatly- been a known issue since 'day 1' on stock, and I have long given up hoping for a fix and use it with a headset, as I seldom do voice calls. I fear this 'filter' is deep down, either hardware or software in the driver, as I assume they would have fixed it quickly if it was in software they could ac

I bought an old house some ten years ago, and found out that part of the insulation used in walls and ceiling was a sheet of metal foil, so to a large extent I live in a Faraday's cage. Thus I can not use my WiFi in the garden - no big deal for me, but a big surprise for many guests. So it was no surprise to me that none of my phones have been able to get an indoor gps fix. (Except when standing under the passage to the attic) The big surprise is that the Titan gets a fix indoor, and with 3-4m accuracy!! (2m under the passage)

I got one too. Have not found the time to make a review of it. I'm not a fan of keyboards in the wrong direction, with REALLY few keys though - but to each their own. Though (almost) any real keyboard phone is worth supporting, as it is still better than touch only. But I must accept that I'm simply too old to use a device with that size of screen, despite it being more pocketable, for other than occasional usage. I really struggle with the small print. And yes yes not illustrated by the picture below, that was just a quick one for the content. The hardware feels sturdy and g

Yes, I guess it could be argued that it is a bug in recovery that it does not correctly reflect that installing an image might have changed the active slot, before a boot has been made.

I believe the last remark is not quite accurate. It is the flashing&install of the main image that also changes the active slot. Reboot to Recovery just boots to that. If you do not want gapps/magisk/... a reboot from the main menu will also boot into slot B

Sad to hear you broke the screen. On the call quality, a headset might help you. I use a wired one, and that works fine. (though obviously just a workaround not a fix)