EskeRahn

I think the optimal would be if we could arrange things independently for the two directions BUT when adding a new item in one direction it also tries as best it can to add it in the other, but allows us to rearrange independently and even to remove for one direction only. The automatic system could then have different 'modes' like the 'two-half' approach, 'keep centre and corners', 'start filling bottom up' and what ever other algoritms that can be thought up.

You are welcome. And no wiki I'm aware of.

It seems to always do this, did on all the test/images too, so quite normal. Actually the gaps also 'stops' at 47% but is so much faster that we usually do not notice. (I wonder why they did not choose to stop at 42 😁😇)

This sounds really bad! Let us tag @Erik so he can find out what has gone wrong.

Also try and 'dial' *#*#4636#*#* (4636=INFO) and select Phone1 Information, and double check that "Mobile Radio Power" is ON. You could generally compare the settings for slot 1 and 2.

For the first time in at the least a year I had it too this morning. And looking at the logcat it could be related to WiFi. I see entries like these before and not after the crash 08-24 07:48:21.605 1668 2065 E AndroidRuntime: FATAL EXCEPTION: LocaleTracker 08-24 07:48:21.605 1668 2065 E AndroidRuntime: Process: com.android.phone, PID: 1668 08-24 07:48:21.605 1668 2065 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.net.wifi.WifiManager.setCountryCode(java.lang.String)' on a null object reference 08-24 07:48:21.605 1668 2065 E Andr

Indeed this is rather limited, but a convenient usage of MTP to INCREMENTAL copying files can be found here.

Indeed. Had it been easy to spot, they would most likely have fixed it. If it 'only' happens as seldom as in the order of days or even week it will be very hard to reproduce systematically, no matter what you do.

You do not need a sim to do emergency calls. And I did disconnect immediately when I accidentally triggered it - and yet got contacted to assure that I was OK....

Obviously the bug should be fixed on the Pro1, but you might help them in testing if this theory has anything to do with reality. It could be other things that also affects it so even if they bought the exact same router they just might not see the same bug. And thus would not find the bug pestering you. The more it can be narrowed down, the easier it will be to find and fix.

An interesting theory if SON is triggering this bug! Could you (temporarily) set them as two independent networks, and see if the Pro1 can work with both without the random boots? And if that works double check that the bug reappears by setting your router back to using SON.

Great! ... But skip the emergency test.... It will call your local emergency with no warning on click....

On stock this (still) requires you to be careful how you grab the device, to avoid accidental triggering, and the annoying "Too many retries". OR on the contrary be sure to register the fingerprint of the finger touching when grabbing to deliberately unlock when picking it up from the table/pocket. It should be said that this problem is in reality eliminated if you use some sort of case. And 100% eliminated if a flip case opening to the right behind the screen is used ('Japanese' style book).

It is simpler to just add some pieces of 0.5-1mm thick adhesive rubber/felt without removing anything.

Interesting. Though my experience with the stiff types are a poor fit. The reason is that the back of the Pro1 is not just flat but slanted towards the sides.

Stock is even pickier on VoLTE it seems... https://community.fxtec.com/topic/3055-volte-voice-over-4g-data/

Good to know that it is not a thing specific to the Pro1, but a more general issue.

Thanks for the info and link. and indeed the first green is on page 6 💚

Thee first weeks after it went official we got weekly Monday builds. But not the last two Mondays. I see a lot of pending stuff described here https://download.lineageos.org/pro1/changes/ Anyone knows what is preventing these from going 'live'?

Let us hope for those preferring the keyboard in the wrong direction that this will be something less humongous that the Titan. The larger the variation the larger a target audience that can get what suits their needs.

I am by far an expert in this, though I have used some time digging into it. The first part of the quote is clearly right in broad terms, but it is actually more complex. If we are below 50% and the battery is at room temperature high currents are not a problem, it is when the battery get more filled up and&or the temperature rises that the high currents are problematic. On the second part, this sounds really confusing and against normal physics. I never heard of a charger overheating by supplying a low charge (On the contrary cheap ones can overheat while producing high currents

Well the answer is that to care for the battery as slow as possible - it is a matter of keeping the temperature at room temperature below 30°C. BUT it is not that it is killed immediately by fast charging, or a very sharp limit at 30. it is like fast-food: Occasional usage can be very convenient, but very bad for the health and overall lifespan if used daily. I have written a lot more on my blog with links. Start e.g. here

Interesting bug! Does this mean that sim1 is active bypassing the pin? Or 'merely' that both are deactivated (despite you only requested sim2 deactivated). Can you do calls/sms/mobile data on sim1?

(merged threads)