EskeRahn

Try the factory test described in this thread, The magnetic hal sensor is number six from the bottom, just above "OTG"

Just for info and off topic this is not LineageOS only, the same goes for Stock. Below an example from July 19th, with very little usage, where it dropped 10% in 20½h (red line)

That is interesting. I use password or fingerprints for unlock, and does not see it on unlock. I wonder if it is a general issue when used 'unprotected' or it's some software you have installed that triggers the issue? We have had people reporting random boots most likely related to when a WiFi signal is seen as very weak. I wonder if what you see could be a milder version of that? Could you try to temporarily stop WiFi, and see if this has any effect on the bug.

Is this a temporary hiccup where it continues by it self, or does it hang so you need to force a restart by long holding the power button?

Something is clearly wrong if it reached close to 60°C. I would suggest to hear what Support has to say in the matter.

The odd thing is that if I in Stock settings search start to type "wi-fi-calling" it knows where the setting is supposed to be - it just do not display (It displays correctly on LineageOS) Stock: LineageOS

The one I currently use is this one. Do not get confused on the "2.1A" print it only delivers 1A - and this is exactly what I want from it *LOL*

Try something like adb shell settings put global sms_outgoing_check_max_count 99999 adb shell settings put global sms_outgoing_check_interval_ms 9000 It is a silly default set way too low IMHO.... Note that is is counting the INDIVIDUAL SMSes that is roughly each 157 char for plain A-Z type, and 67 chars if at the least one unicode char is used. So a lengthy SMS sent to a several friends (bulk not chat) can easily hit the default ceiling,

Unfortunately QC chargers does not come with a simple switch to select normal or quick charge (I have not found one yet). BUT you can easily find QC 3.0 chargers with two or more slots, where only one is QC. This is a very handy thing. Use the normal slots normally and only the QC3.0 one when you are really in need of it. See also this I use one found on ebay that provides 5W in two slots and 20W QC3 in the last one. it is 2.5cm thick, and 5x5cm excluding plug (85mm including EU plug) so not much bigger than other chargers.

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.