I currently use Android-device with Maximum power savings enabled which only permits Samsung Internet app, and browse to OGS-website.
Tapping an intersection places the stone on the wrong intersection, typically one of the adjacent ones, and not the intended one.
I am testing currently to see if this happens also with OGS app, regular power savings mode on device.
From my own personal experience, I used to play on my phoneâs browser on a daily basis and never encountered this problem.
Ironically, I sometimes face this problem here in the forum on my phone, where I am unable to click the âsubmitâ button on a post. But Iâve found closing and reopening the browser resolved this.
You didnât mention whether youâve tried the steps and whether they worked.
If zoom level already is 100%, set it to 110%, then back to 100%, refresh.
Test.
In tech, itâs not about what should or shouldnât work, itâs what does. If you have power saving on (do you mean bandwidth saving perhaps?) and youâre convinced thatâs the reason,⌠simply do abovementioned steps. If it works afterwards despite âpower savingâ, that canât have been the problem.
Use the zoom gesture. Apart=zoom in, together = zoom out. The % shows in your browser - the field where you enter URLs - on the right side.
Refreshing might work differently on your phone from how Iâd do it on mine but what I do is to press on the top 1/3 of the screen showing the website, then keep pressing (lightly, of course ) and move my finger down, then release.
From your overly defensive replies I gather that youâre frustrated because youâre not very familiar with your own device and perhaps ashamed that it was a âuser errorâ instead of a technical fault. Thatâs fine, and if the workaround is all you need, the better.
FYI, my device uses Android but we probably donât share the brand or model of the actual phone.
Just keep in mind that you should probably not be hostile to people who just took precious time out of their day to help you, because the more people you treat like this, the fewer will help you in the future.
I am defensive? You have done nothing but to call people stupid. First you assume the user hasnât zoomed out correctly, which is (not true?). Second, you lecture people on âin techâ which is condescending, I am a tech genious, and do not need fools to explain conpects idiots understand. That is just being disgusting. Third, you have again claimed that I am not âfamiliarâ my own device. I just showed you a feature that you wherenât aware of
For the last time, there is a problem in Max power savings that need no be addressed.
Iâm not backing down from this point. Atleast twice today, the wrong move has been submitted.
Understood. Unfortunately there are no other browsers available in Max power savings that I am aware of currently. It would be very inconvenient to research how to âhackâ this.
For some reason the assumption arose that I was not fully zoomed out. There is no other option that would be logical, which is why I got frustrated.
I apologize to the admins and non-trolling users. I am not intellectually impaired in any way and do not enjoy doubts of such ridiculous nature taking up an hour of my day.
Have a great day.
No, actually it was. I just tested it and it works as intended on ultra power saving mode. I did have this problem (off stone placement) before and I solved it by doing exactly what I described.
It reliably happens in Chrome when I zoom, and itâs probably because the javascript âboard positions layerâ does not scale proportionally to the âdisplayed boardâ. We can see the visible board is not automatically aligned with the stone placement layer if we rotate said visible layer.
No, actually it was. I just tested it and it works as intended on ultra power saving mode. I did have this problem (off stone placement) before and I solved it by doing exactly what I described.
So this person is wrong too?
I did have this problem (off stone placement) before and I solved it by doing exactly what I described.
So you understand that there is an issue. Your philosophy is that if a user expects something to work, and it doesnât that they should do something different. Honestly: few people share that philosophy. Users use what works. If it doesnât it might need some affection. Im aware that you disagree with that, but thatâs not in my interest. 'Prende?
Iâm not interested in your philosophy
Iâm interested in things working smoothly, doing what I can to help out to do so.
No, he is correct. He says itâs got nothing to do with power saving.
And apparently the zoom in problem (read your quote of his post) also happens in the Samsung Browser. Iâm not surprised because as I said above the root cause seems to be how the shadow layer is handled. I canât test that on mobile because I use Chrome, but on my desktop the zooming works fine in Firefox so Iâll just take flovoâs word that it also does on mobile.