EskeRahn

People very often confuses the percentages shown with something meassured. In reality it is estimates - or less kind "guesses". A bit like the ETA of a train or plane. A LOT of factors come in. The workload, the temperature, the age of the battery... See this ancient post.

My guess would be that after a period a lot of things are initialized and even cached, so your total system has less to do, and thus less 'stress' now than immediately after install. Similar it is not unusual that the battery stamina on a charge is relatively poor just after an install. We usually don't register this, as the extra load is often drowned by the extra screen-on we usually have with a new phone.

Yup that is why I'm keeping it. Reported both as bugs to Swiftkey.

Could well be. Interesting theory. I'm on a carrier not supporting 2G, so the phone won't try to go there (except emergency calls) So that could explain why I do not see the bug.

You are really doing an awesome job, can't repeat it enough Less the Google certification some need for banking apps and the like I will say that the Lineage implementation is better than the stock one in several ways. I certainly hope they will adapt some of it in stock.

Actually I do not know what roles people got, but send a mail to support, and I'm sure they will try to help.

Well you could check what bands your carrier supports. That would limit it. In the can it might try to change band from the one actually in use, searching for alternatives in the can.

Interesting! Do you know what network bands are active? As relatively few reports this, I have a suspicion that it (for whatever reason) is limited to some specific bands. I just tried here, and it did NOT boot it goes down to 3G, and then zero bars.

Yes it would be nice with a formalised channel for this. Currently we have two threads: One for discussing and testing possible bugs and the like, and one that was supposed to have confirmed bugs... But they are not 'clean', so hard to find anything in them. There is an unofficial bug-list here that is more easy to read. But a more formalised system would certainly be to everyone's benefit....

Yes, they are also messing with the Ctrl-key!!! So when I press Ctrl+Fn+3 to get a £ symbol with FinQwerty it does not work. FinQwerty offers Ctrl+Fn as a one finger doublet for the two finger Shift+Fn. But Swiftkey steals Ctrl and ignore the Fn...

Erhmm did you read what we have been debating in this thread since yesterday? Just asking... 😇

Moved the further Spontaneous reboot discussion over here

4.4.153-perf

Settings, About phone, Android Version, Kernel version.

Hmm, to me laptop associates with clamshells, like the Cosmo. But retractable is a good word... Does anyone recall what Nokia called them back in time?

Exactly. The word has to be descriptive, and it won't help to find a rarity deep in the English dictionary that no one understand. Maybe one should see it more as the keyboard dropping down than the display popping up? A jaw dropper perhaps... 😜 If one holds the display part and gives the back edge of the lower part a slight push with a third finger, i is actually a bit like a jaw dropping... Ideas have been thrown around in this thread after @Waxberry asking

Indeed it is confusing that the Pro1 is called a slider, as it does not slide... But I guess no one have come up with a good descriptive word. The movement reminds me of a dolphin jumping out of the waterr. So my least bad suggestion is "Flipper", that both relates "flipping" it open and the famous film, but people also associate flipping with opening a clamshell, so not good.... I would love it if someone had a good descriptive word for it.

Standard Android, see discussion in other threads. Just click The square, Click the icon of the app at the top, and select split (if the app supports it)

I'm not saying that it is a big issue, just some lost functionality, that might be missed. There might be other issues we do not know of. Say some app that requires an edge swipe to reach the very edge, or really close by. What is the maximum dead-zone that allows us to drag an icon from one screen to the next in various launchers? With Trebuchet you have to be really close before it moves over. So I like the software-bezel idea David mentioned with completely reducing the apparent display size. Optimally an option reducing either just touch or touch+display or perhaps even a

There are a few scrollbars with the slider only 20 pixels wide (Small Display size, even less with Smaller and 16 with Smallest). E.g. in the Settings, Apps, See all

Well you could follow the guide here, and do OTA from that (of course wiping everything). And then use David's model moving forward with future OTAs.

It would be a SUPER elegant solution if it after a failed attempt could ignore any touches until it has been untouched for say 2secs. This would mean that grabbing or holding it would only count as one single failed attempt....

Old, but not wooden legs (yet) 🤪 Haglöfs fleece soft shell.

I would say these two are the ones with most complains for stock. Though I personally have no really issues with either in a flip case. On the second I would suggest an OPTION that requires that we press Power, or slide out the keyboard, before the reader gets active. My personal favourite would be to have a magnet close to the second Hall sensor turn the display off. For me it does not need to turn on with the magnet moved away, as I will use the fingerprint sensor anyway. (Preferably some options, for the benefit of those with a flip-case with a window) ....Would

We are supposed to just hold the key long when at the home screen, but SwiftKey is messing with that on mine too... 😫 Force-stopping it (after re-enabling Gboard) make the short-cuts work again...