EskeRahn

Well though you might not care on the battery stamina, I assume you are interested in the battery life - even if the device are not glued together. Heating the device too much kills the battery. (That is the exact reason why we -as you wisely do- should avoid fast charging in normal daily usage, and only use it when we are in a hurry)

Well if you quick-charge it you certainly get it extensively heated, so if you get a low FPS rate then, but a high rate when it is cold, that should give a pattern. You could even try to operate it on something cold, and see if that helps it. If it does, your intuition on throttling is right. Be careful not to take something TOO cold, we do not want risking condensation of water vapour from the air inside the device.

Hmm, that is odd. No matter how good or bad, we would expect it to be consistent. Could something be running in the background taking the resources? Try something like "Android Assistant", and click the "Processes" tab, and perhaps kill (=stop) irrelevant stuff, and see if you can get more consistent results. Perhaps try something that works off line, and put it in Aeroplane mode, to isolate.

Well good that you reported it, and the more details the better. I'm not in anyway saying that they by optimisation wenot could extra out of the hardware. But I think they are more than busy with fixing bugs & malfunctions, so the easier we can make it for them to narrow down where there is an optimisation needed, the more likely it is to be implemented. It could be as simple as some code left in a debug mode somewhere, that uses/wastes time on logging, or it could be a complex thing needed. And worst case it is a limitation with the screen hardware/interface. So the more it

Note this is open camera, and I see similar on both Stock and LOS. I'm pretty sure there is BUG in the camera API, so when OC tries to stitch things together we get weird Halo's. HDR with OC works just fine on other phones, so I'm pretty sure it is a parameter issue on one (or both) the images that are to be stitched. My GUESS is that something is handled as linear that ought to be handled logaritmic or vice versa.... e.g what should be 10% longer exposure is handled as 2^10%=7% The snapdragon-camera-app does NOT have this on HDR. So it either access the camera directly, and not through t

Those mushrooms clearly did not do you any good... 🤢 But on a more serious note, I tried to take an extreme HDR-image with both LOS and stock, and in stock I got the below (well here a cropped and reduced version of it). Note the lime-green halo on the flames.

...Stop eating whatever you are eating immediately... 🤣

Just a random case for another new device, and this is even just an evolution over what they already got.... https://www.dpreview.com/news/4862735124/some-galaxy-s20-ultra-smartphone-reviewers-report-multiple-camera-issues

Yup. As I usually say: Every £1M spent on a device selling 1M pieces is just £1 each, but for a device selling 10K it would be £100 each... And this goes for development and optimising just the same... And this is also why we should not expect massive ad campaigns at e.g. super bowl... So everybody should spread the word to everybody they think might be just a little bit interested, or might know one that is... The best chance of this being a success is if the info on it spreads viral.

Do we even know how their workflow on service requests are supposed to work? I would not expect any reaction that fast either. As Eric said everyone is still doing everything, and most likely that means they have piles of work each...

Different tools reports slightly different. They say MSM8998 835, but the max frequency is reported at 2.46GHz by CPU- and as 1.9GHz by "Device Info" (Quixon). (ADD: they report the same on Lineage and on Stock Pie)

Though there is a common rubber mat over everything, and clicking VERY close to a border with a nail, can click the neighbouring key also. Tried to lift up the separator grid with a nail and hold it with a toothpick: So optical illusion that the e-ink moves with the key...

I yesterday got the old SCH-U750 aka Zeal aka Alias 2. Very interesting. There are little movement of each key, but to my surprise it looks like the e-ink move with the key, so it is not just a transparent mat on top of a common e-ink display, But it looks like it is 42 individual matrix e-ink displays! And a warning to @abielins: The below is AFTER a thorough cleaning attempt. You do NOT want to know how it looked before. I believe it might have been an entire eco-system....

Are you even reading what I'm saying?

I highly recommend this phone, but not to everyone... Generally I would not recommend anyone to buy a brand new device if they want an errorfree experience out of the box (any brand) The Pro1 is a niche product with a limited audience. AND like most new devices it comes with a bunch of more or less annoying software-bugs. And sure bugs ought not to be there, but in the real world they are, the important thing is that things get fixed, but like everything else in China these are delayed by new year and virus... You should try the LineageOS (see the long thread) where quite a lot of the

I doubt it, but I do not know. People in general are complaining about battery sizes/stamina of their smartphones, because they are unaware of all the bloat running and unneeded radios kept on. It is as if Google and the manufacturers want people to have bad user experiences with their devices!!! What about a little AI here! Or at the least Common sense!! Let us have some automatic on and off! But start by the simple: Replace On/Off with Sliders for all the radios like: "Always on" "On when requested by app" "On when requested by foreground app" "On while requ

I certainly agree that @tdm is doing a great job here, others have contributed, but he caries a huge load here, And I too hope some of it finds it way back to stock.

The thing I hate about al the providers offering equals slabs, is the idea that different people all fits in the same box. That is what I love about the Pro1 offering something not like that. In this edge-case it is matter of finger size, usage pattern and perhaps even motor skills. We are so far from all equal so why should one set of settings fit all?

I think it is much a user-dependant thing. When opened I'm yet to experience accidental touches clicking the numbers. But it requires more care opening. Personally I ONLY have problems with the edges when it is closed. Not when opened. Others have huge problems clicking the numbers. I would say the thumb-width is what matters. So I would prefer a setting. But when you got one slider, would it be much work to copy and paste to four? Giving the user complete control of the two edges, opened and closed. You MIGHT even add a tick-box (default set) "Same margin", that links

Seems like we got quite similar units 🙂

Sad to hear you don't like it. 😥 But glad to hear you are not in it for the profit. 👍

When doing images comparing the toning of either white or black, I strongly suggest doing it at a real white background, as the white balance of the camera can easily get confused and show things either better or worse than they actually are. I often use a bright red table for background of device photos, for the nice effect of it. But the downside is that it can come out in the digital images as anything from pink to burgundy, and even orange some times. Sorry to hear, hope you come back at a later time. 🙂

Oddly only ONE of the two units had this ??? The "Final Sample". The old "Pre-Production" did NOT. And anyway it was only initially, so at most a very low priority thing. You got a Pre Production too for the testing, right? So it just MIGHT be that they changed something - or that it was merely a strange coincidence. Let us not dwell on it, we will see if any other see the same. 😊

BTW it would be great if the two edge margins were handled independent. The Keyboard-edge can take a lot more margin than the opposite without affecting functionality. And it is the side that is most prone to accidental touches both opening by pushing, and for entering numbers.

I see, not a big deal in any way, only an initial issue looking for it. 🙂 Thanks for the explanation. If it is power consuming, perhaps it would be beneficial to slow it down to say 100ms when the keyboard backlight times out, so it only consumes when needed. It did not work when I initially changed it from zero. But after the restart I can change it and even set it to zero and up again. Could it be an initialization issue?