EskeRahn

He he. Well If you got more that one phone in play, one may be idle for a while. And I deliberately left it (almost) idle to have a better estimate of the idle consumption than my previous claim that it was about 1%/h, it really is only about 0.5%/h I would recommend to install something like 3C Battery Manager (the image is from that) or GSAM, and be sure to give them a little extra privileges (see this), and use that to help spot the culprit(s) eating your battery

Note that the battery consumption of LineageOS is quite lean by it self. So what you experience could be some apps eating the battery in the background, or you are using it actively a lot (Displays are always eating a lot, especially if set bright, and oddly for amoled especially blue). Try to note the battery consumption while you are asleep it should not be above roughly ½% per hour. Have a look at the below, where it was (almost) idle for slightly over 4 days (99h) between 5th and 9th of August, and used 46%

This does not seem to work at all, says no signals are available even when connected - perhaps it is intended for older Android? Last updated over two years ago. Another one (open source) works, and displays at the least 5 and at the worst 15db worse results on a Pro1 placed at the same place as a Samsung S8-. So in 'mean' that is half the signal.

@tdm are providing builds faster than you can test them 🤣

There is a principal difference in paying a bill and making a refund... It could be their specific bank's requirement or some general rule - I do not know. We would need someone with detailed knowledge on how UK banks do stuff to give an exact answer. I just reposted what they have stated earlier.

Just a check, before sending back. As I understand it some units were sent out with incorrect firmware, Can you confirm that you are on the 2020707 version? And if you did not do it already, try a factory reset wiping everything. Just to make sure that it is a hardware failure and not because it has been delivered with wrong firmware/software.

This is a very small start-up and I think they use as much power as they can to push the waiting pre-orders out. I do not know the size of their support 'stack'.

The point is that it is NOT sliding - I do not have a good word for the motion though. It flips up like a dolphin jumping the water. If you do an even horizontal push it will 'lock'. See this thread.

For stock: This was a bug in an early sneak-view version of the March update, has been fixed with later OTA.

Interesting. In my case it looks logically the same in "File Transfer" and PTP from the PC (though obviously fewer entries in PTP, and different icon) But note that it appears as BOTH an Android Phone AND under Portable devices If I change to "No data transfer" on the Pro1, it disappears under portable devices (but is still registered as an Android Phone) (It looks the same for stock BTW)

What driver has Windows chosen - that might be the culprit.

One thing that really bugs me with that one is why they place the icon in forced positions where they are the hardest to reach? Why not start from the bottom - that is where the thumbs can reach easiest both portrait and landscape and both opened and closed...

Tanks for your analyse, and I agree to a large extent. Though I do find the build in quickstep solution of two blocks of equal side next to each other or on top of each other quite ingenious for a simple launcher, and thus simple to use for anyone, the only drawback is that a widget must stay within one of these blocks. And that is not a bad price for most. But obviously independent layouts are more flexible (including allowing for larger widgets) - at the price of more complex setup. Unfortunately the Total Launcher's auto-rotate is not really working - though it can do both orientations

Yes. But I do not use a vary fast charger normally. I try to use a charger offering 5W in normal usage, and only about 20W when I really need it. But even at 20W I do not have it go as high as 50°C, worst case in the forties. During fast charging usually peek at 42°C or lower. But once this year it has been above that, it reached 49.0°C on Feb 23. PS I use a shell case, and this actually makes the heating worse at at can not cool to the surroundings as easy (plastic with card board inlay()

I can confirm this has worked for me. I never had any problems UPgrading (I did have some issues once I tried to DOWNgrade a particular combination of test build) Even when I fumbled with the first change from Test to Nightly, Following the usual flashing procedure fixed that too.

WHAT! That sounds like pure Heresy! 😇

It is in the standard android market https://play.google.com/store/apps/details?id=aws.apps.keyeventdisplay

You could try to install "KeyEvent Display" and see if any of the problematic keys has any reaction what so ever..... (Note that Enter is interpreted by the App as Select, but you should see it doing something if the key is working)

Sorry, does not work by a simple side load - but it does VERY much sound like a hardware issue.. Assuming you have tried a simple reboot, you could try a factory reset, but the chances that it will help are slim.

Yes, was unaware that you were on Lineage. That package has not been moved over - not sure if it will run under Lineage. Just a sec.

The standard first guess is to try a different cable or port, or perhaps a different driver on the pc.

How sad. You should contact [email protected] (this is a user to user forum. AFAIK their office is near Baker Street St. But I do not know where they do service.)

Sounds like a hardware issue...😥 ADD: The below is for stock Android not e.g. LineageOS First go to Settings►System, Languages►Physical keyboard►Physical keyboard►Set up keyboard layouts, and de-select ANY selected. OR if you are using FinQWERTY you could also just select "FinQWERTY None (stock)" If QWERTZ ignore that the print is now wrong, we want to test hardware keys(!) Then try the factory test described here it is number seven on the list. Please note that the Esc-key has changed in later OTAs compared to this test , so not lighting up does not mean it is broke

....I can not help the feeling that you might have put more time into developing software for the Pro1 since autumn than Idealte....