I use Locus Map pro 3.5 and Locus Map Gold on Samsung XCover pro and Samsung S 10 +.
When the sun is shining, I can't use Locus Map Gold for the display is too dark. On both smartphones I disabled "adaptive brightness".
Locus Map pro 3.5 always runs with max. brightness.
Can anybody help me?
Hi,
you probably use dark mode on the Locus Map 4. Check app settings > Controlling > Display > Dark theme and choose a "Light" theme here. Does it help?
Thank you for the answer. I will try your suggestion. I worked with "System" till today.
Hi Menion,
unfortunately the problem is still there.
There must be somewhere a problem in the software, for Locus Map Pro is running super.
I now decided to deinstall Locus Map and use in future only Locus Map Pro.
Please provide some screenshot of the Locus Map Pro and Locus Map 4 so I may see a problem. Maybe if you use some Xiaomi devices, they use some weird own system how to force a dark mode to apps, so check device settings and try to exclude Locus Map from this weird feature.
Hi Menion,
here two photos on which you can see the problem: LM 3 bright, LM 4 dark.
Fortunately another member has the same problems. See the answer of JackRussel to my post (https://forum.locusmap.eu/index.php?topic=7417.0) in the German forum.
It seems that the problem is on all Samsung devices (I tested S 6, S 8, S 10, S 21 ultra and Xcover pro).
I only can use Locus Map Pro but not the new Version.
Hi Wole
thanks for the screenshots. On the screen with darker LM4, it looks like even a top and bottom system control panels are darker, right? The app can't affect the brightness of these panels!
I'm sorry, but I have absolutely no idea how app may affect brightness of your display :-\
No, not only the panels are darker but the whole app is darker than LM 3.
If you can't find the reason, I will further use LM 3. Thats great.
Thank you very much for your efforts.
Quote from: Menion on July 01, 2021, 22:25:37
On the screen with darker LM4, it looks like even a top and bottom system control panels are darker, right? The app can't affect the brightness of these panels!
Hi Menion,
same Problem here. Samsung S20 FE 5G. LM4 Gold 4.2.1
The whole Display gets darker. Within 20 seconds the Display gets perhaps 20-30 percent darker and the Display is no longer readable.
There are no Difference between automatic Display brightness and manual max. brightness. The Display gets darker.
It seens that LM4 ist the Cause.
Without LM4 : If I cover the light Sensor with my Finger, the Display gets darker. If I take away my Finger, the Display gets bright, up to max brightness. Readable in the Sun.
The same procedure with LM4. If I cover the light Sensor with my Finger, the Display gets darker. If I take away my Finger, the Display gets bright but not to the max brightness. Not readable in the Sun.
The Problem stays if I close LM4. I start other Apps but the Display don`t gets the max. brightness. No difference on manual max. brightness. No Difference after Phone Standby. The Display stays darker.
I have a Workaround. That shows the Problem with LM4.
The Display gets darker with LM4.
Then I take LM4 in Backround (Backround is necessary, close LM4 is not necessary).
Then I take the Phone in Standby. (no Restart necessary)
Immediately I wake up the Phone.
Then I get out LM4 and the Display shows max. brightness. 20-30 sconds and the Display gets darker.
Then I repeat the whole procedure.
Thanks a lot.
P.S.:
I have found a little connection.
All tests with manual max. brightness (automatic off) on my Samsung S7 (same problem) and on my S20.
With LM4 the Display gets darker, like above. In my opinion it seems to be a problem with the read area (max. brightness), /see the Screenshots.
With LM4 the brightness ist falling down to high brightness (without red area).
But all other apps stay in the red area on max. brightness.
My S7 has a little difference like my S20. With LM4 the Display gets darker.
If I change the App the brightness rises to max. brightness. Without Workaround. After 10-20 seconds the max brightness is reached.. Standalone.
LM3 on my S7 keep max. brightness.
Hi Menion,
do you have found the problem or it is impossible to finde the reason for the dark display ?
I have maked another comparison.
Same Smartphone, Samsung S20 FE 5G, LM 4.2.1
Two Photos with the same preferences. f8, 1/160 s shutter speed, ISO 250
A directly comparsion in one Photo
The dark display is mainly visible (or not readable) when the sun shines directly on the display.
I am surprised that more Samsung users do not have these problems.
Samsung S7 with LM3 = no problem
Samsung S7 und S20 with LM4 = problems
Give a sign if you need more comparisons.
Thanks a lot
P.S.: Sorry
Left photo was recorded immediately -> brightness normal
Right Photo after 1 minute -> brightness dark , unreadable in the Sun
Hi Menion,
I am also still interested to know the reason for the problem. I also can't believe, that other Samsung users don't have these Problems.
The problem must have it's reason in the app for LM 3 works correctly.
Hi all,
Ihave a S10 and a Tab S6 light. Both do not suffer this problem, neither for LM4 nor LMP.
I could imagine that a mixture of screen timeout settings and energy saving modes may impact the behaviour.
But then why differently for LMP and LM4?
Good luck and cheers
Michael
I have the Problems on S 8, S 10+, XCover pro and S 21 ultra.
Quote from: michaelbechtold on July 16, 2021, 19:47:29
I could imagine that a mixture of screen timeout settings and energy saving modes may impact the behaviour.
I have also suspected.
But I have switched off all or the most energy saving settings. Shown on this page : https://dontkillmyapp.com/samsung (https://dontkillmyapp.com/samsung)
I have excluded Locus from the optimization.
The next problem ist that my Samsung S7 with Android 8 has other energy saving modes as my S20 with Android 11. I do not understand the relationship.
I am surprised that not all Samsung users are affected. Therefore I will delete Locus and after a new installation I will try a original profil and preferences without my old profil.
Quote from: michaelbechtold on July 16, 2021, 19:47:29
Hi all,
Ihave a S10 and a Tab S6 light. Both do not suffer this problem, neither for LM4 nor LMP.
I could imagine that a mixture of screen timeout settings and energy saving modes may impact the behaviour.
But then why differently for LMP and LM4?
Good luck and cheers
Michael
I also own a S 6. So I just installed LM 3 and LM 4. LM 3 okay, LM 4 starts bright and becomes after a few seconds darker. So I say, all Samsungs have a Problem with LM 4.
Quote from: JackRussel on July 16, 2021, 22:39:14
Therefore I will delete Locus and after a new installation I will try a original profil and preferences without my old profil.
No success. Only new and clean LM4 without personal data.
On my Samung I have maked the wipe cache partition and then optimze apps. I tried Always on Display off. "All" energy saving modes off.
No Success.
Where is the difference between LM3 and LM4 ? No idea.
LM 4 has a possibility to switch between dark mode light, system etc.
LM 3 not. Is here the problem?
Hi guys, thanks for testing. It does not make too much sense to me to be true. I also test the app on the S7 and no problem so far. Also, Samsung devices are the most used so there should be a lot more people with this problem.
Does this happen with a completely fresh new install of the LM4? Does a day/night theme (settings in the app "Controlling > Display") have any effect? Aren't you both using any app that should save power or reduce brightness?
At first: I don't believe that JackRussel and I are the only members with this problem.
I tested several Samsungs, all the same problem. The Problem can't be another app. My S 10 + reseted and installed only LM 4 and LM 3. Result: LM 3 super, LM 4 bad.
With the Dark mode I played, no better result.
The Question: Why not problems with LM 3? If another app would be the reason, why only with LM 4?
Quote from: Menion on July 19, 2021, 06:47:00
Does this happen with a completely fresh new install of the LM4? Does a day/night theme (settings in the app "Controlling > Display") have any effect? Aren't you both using any app that should save power or reduce brightness?
Hi Menion,
Complete fresh and new install. See Replay #15.
Theme day/night/daylight/system settings have no effect.
No power saving oder brightness apps are installed.
All power saving preferences in Samsung 20 are disabled.
Thanks a lot. But I don´t understand, that me and wole are all users with problems.
P.S.:
My S20 FE 5G is new, 2 1/2 month old.
I noticed the problem after 14 days, as of purchase.
Possibly blue light filter.
Ohh ... I always thought this missing brightness while sunny weather is a problem of my S10.
But today I checked brightness without LM 4 running ... and yes, incredible: my mobile is much more better to read.
Switched LM4 on ... and mobile gets darker after a short while.
Next step is installing 'old' LM pro to see the difference ...
Quote from: jonny.blue on July 19, 2021, 21:11:22
Ohh ... I always thought this missing brightness while sunny weather is a problem of my S10.
But today I checked brightness without LM 4 running ... and yes, incredible: my mobile is much more better to read.
Switched LM4 on ... and mobile gets darker after a short while.
Next step is installing 'old' LM pro to see the difference ...
Hi jonny-blue, welcome in the club. You are number 3, and the rest??
Hi Menion,
here is the next member with the problem: https://forum.locusmap.eu/index.php?topic=7417.msg64482#msg64482
He will not be the last. Most members probably only use LM 4 and don't see the difference to LM 3.
Hi Menion ... maybe it's unbelievable but true. 😳
Now at home I placed my mobil and a (good) digital cam on tripod and took a photo of the same area with exactly the same conditions.
The result is astonishing: LM4 is much more (not only a little bit) darker than old Pro version.
Although I love using LM4 ... my next trip outside is with Pro.😰
I hope you can find a reason ... or a way to detect this problem.
QuoteAlso, Samsung devices are the most used so there should be a lot more people with this problem.
Google translate !
That's a very arrogant statement as I find. Not every Locus user is in the forum and not everyone can English. And many just wait.
I also tested Locus 4 - on a Samsung Note9 with Android 10 - and had the same problem. These mistakes and other things allow me to use Locu Map Pro again.
QuoteDoes this happen with a completely fresh new install of the LM4?
Yes, Sir!
QuoteDoes a day/night theme (settings in the app "Controlling > Display") have any effect? Aren't you both using any app that should save power or reduce brightness?
No, Sir! Between LMPRO and LM4 I have not made a change in the settings.
LMP and LM4 are both excluded from the energy management. And I do not use principle the dark mode, but maximum brightness. It is too stupid to buy an OLED and then reduce brightness and resolution to a TFT.
Reminds me of the big software manufacturers. If one reports to those a problem is always the user guilt! Although the problem occurs after an update and gets away after a backup >:(.
Hi all,
today I found time to do some testing:
1) turn brightness to max manually
2) start LMP and LM4 on a S10 and Tab S6 light, both on Android 11
3) go to same area on same map (vector, MF4 (OAM))
4) set screen timeout to 10 mins
5) observe
Both apps show the same behaviour - no dimming before the screen timeout of Android kicks in.
Then there is some dimming, and soon after the screen goes black.
Tap in the dimming phase will bring back full light.
Above was with "Always on" switched off.
6) switch on Locus "Always on"
7) set screen timeout to 15 sec
8) wait - forever (to have screen dim/blacken)
9) switch off Locus "Always on" - dim/blacken after 15 sec.
That's just my 2 Samsung devices - seems there are differences to other experiences.
Cheers
Michael
Quote
today I found time to do some testing
You did the test in the direct full sunlight?
Only then the effect occurs ...
Was a bit late for that. To emulate sun light, I manually set the brightness to MAX.
I can test tomorrow morning with the real sun ...
Hi Michael,
I didn't quite understand what you were trying to say with your test.
Should the procedure be repeated every time?
Will the brightness be fully maintained during the runtime?
The fact is that LM 3 runs great without any further settings, while LM 4 causes the problems.
Here, in my opinion, Menion is asked to adapt LM 4 in such a way that it also runs without further ado.
One more question: where do you set "Locus always on"?
Thank you for your efforts.
Quote
I can test tomorrow morning with the real sun ...
I'm excited to see if you can reproduce it ... for me it only happens in direct sun light.
And that's unfortunately while walking or biking outside ... 🙄
Hi guys,
thanks for the tests. I'm still surprised that nobody on our official help desk reported this issue (we have there X-times more reported problems than here to be true).
I was able to probably simulate this issue on older SGS7 with Android 8. All other devices (older Huawei, Pixel 2, 5, ...) work without any issue ...
... and I have absolutely! no idea why this may happen. I search the whole code for any place where by accident app should handle with device brightness, but no such place exists. Uff
@Wole: go to settings, use the search function (top right) and enter the word always. Tap the right hit.
I have this option in my quick settings, BTW.
@all: I reran the tests on S10 and Tab S6 light - same results for both Apps. Darkening only when nearing the Android screen timeout.
Have those who suffer from the issue tried to use "Always on"? On my devices it does override the Android screen timeouts. And when you switch off the screen manually, a double tap brings back Locus.
Today I found an interesting behaviour while testing this problem.
In direct sun system sets brightness to maximum level (I don't know if there is a setting to specify a maximum point but on my system I can choose 100%).
My test situation:
- direct position to sun (only then the problem occurs)
- deactivate adaptive brightness (to change level manualy)
LM Pro:
- react on every level from dark to full brightness
LM4:
- reacts only in the lower area.
My S10 ( don't know if Samsung or Android specific) has a blue slider up to approximately 75% and then it changed to red plus a system warning that battery may drain.
LM4 reacts on the change up to this 75% level. Above this there is no visible change in brightness. It stays on the level of 75%.
While running LM4 in this state the whole system isn't allowed to go over this level.
Maybe there's a permission needed to go above this 'blue' level.
Hope this helps to find a repeatable test scenerio ... and sometime a solution.
Quote from: jonny.blue on July 24, 2021, 09:35:42
LM4 reacts on the change up to this 75% level. Above this there is no visible change in brightness. It stays on the level of 75%.
While running LM4 in this state the whole system isn't allowed to go over this level.
Same here.
If I starts LM4, the brightness is for example 100%. Immediately, the brightness count continuously drops below the red level (75% ??). The whole system does not go above this level at this time (75%).
When I put LM4 in the background, the brightness increases independently and continuously to 100%.
This takes about 10 to 20 seconds
I can show that with a brightness meter.
Maybe something is there:
https://www.technipages.com/prevent-apps-changing-brightness-android
Just to clarify:
the slider can be moved and remains in every position.
But above 75% with LM4 brightness doesn't increase anymore.
I looked again today. Samsung S8 with LM4. In direct sun I have 100% brightness.
Quote
I have 100% brightness.
How did you measure this?
Just checked my TabS7 ... and there is the issue too. 😰
Didn't detect this earlier because normaly I don't use the tablet in direct sun.
Hi all, Jonny's description of his test by explicitly moving the brightness slider made me do the same tonight (it is easier to judge brightness if there is no disturbing light around to distort the eyes).
My findings are:
1) indeed with LM4 the brightness increase stops just when reaching the red bar and does not change beyond
2) with LMP, the increase continues into the red range
3) HOWEVER, the ABSOLUTE brightness achieved with LM4 seems the same (if not better) as with LMP. Compare yourselves (images taken with an A52, at the same place, around the same time).
No one question could come: would an Android device really put more energy into screen brightness at 100%, with whatever LM, only because there is sun around? I heavily doubt.
I think we have to be VERY cautious to make sure we compare apples to apples in a reproducible way.
Cheers and have a nice weekend
Michael
PS: I had to scale them down, as the 2 MB restriction for uploads hit ...
Quote
only because there is sun around? I heavily doubt.
... but this is the only constellation where the problem occurs: in direct sun where system itselves scales up to highest brightness.
I think we're getting away from the problem now.
The problem does not occur in the shade, at dusk or at night, but when I use the app during the day and the sun is shining.
Otherwise there are no brightness problems.
Apparently Menion has now recognized the problem, which in my opinion should occur with all Samsung users (see his article).
I hope he can find a solution. In any case, LM 4 cannot be used on Samsung devices.
I used my Blackview 9700 pro yesterday. LM 4 runs great here and does not differ in brightness from LM 3.
Quote from: Wole on July 25, 2021, 11:14:53
I think we're getting away from the problem now.
The problem does not occur in the shade, at dusk or at night, but when I use the app during the day and the sun is shining.
Otherwise there are no brightness problems.
Apparently Menion has now recognized the problem, which in my opinion should occur with all Samsung users (see his article).
I hope he can find a solution. In any case, LM 4 cannot be used on Samsung devices.
I used my Blackview 9700 pro yesterday. LM 4 runs great here and does not differ in brightness from LM 3.
Thats not really correct. I use LM4 on Samsung S8. I have 100% brightness at sun. Not as described only 75%.
If the problem occurs with you, what have you been in% for a brightness. I'm still thinking about Samsung.
Agreed, freischneider.
I just reran my test in bright sunlight. No difference of absolute brightness between LM4 and LMP on my S10, regardless of %.
Definitely not all Samsungs suffer from this problem, only some - fortunately.
However, with Menions analysis of code in mind, I would assume there is some weird "optimization" on Samsung Android side that tries to do good, but turns bad in reality. Today, too many things happen under the hood in both, Android and iOS, claiming to "help" users ... but backfire in detail.
Fingers crossed.
Cheers
Michael
Interesting how everyone tests the settings on the device.
Why does you change the settings? If both apps show different results in equal settings, it can not be on the device!
That can not be it! I tried LMPRO and LM4 in parallel and individually. Without changing anything to the device settings. It gets really clear in the car. LMPro is easy to read at any time while driving. But with LM4 hardly a cache can be seen.
Since it has always been tested with the same settings, it can only be LM4.
Hello Freischneider, hello michaelbechtold,
I think you still don't understand the problem. The point is not to measure whether LM 4 has 100 or 75% brightness, but that LM 3 can be read much better in bright sunlight than LM 4 (without changing the settings).
As Holger says, it can only be due to the app, because otherwise the brightness should be identical.
LM 4 is actually unusable in bright sun.
Menion himself has now found that out.
Apparently you only ever compare LM 4. Install both variants and then compare in bright sunlight. LM 4 shows the full bar for the brightness, but is not readable.
In this respect, Holger is absolutely right.
Why are we still discussing here when Menion has recognized the problem and hopefully is looking for a solution.
We can only get ahead with one of these.
Holger, wole,
the manual brightness settings were an interesting observation that COULD contribute to the issue resp. its understanding. Hence worth evaluating. But that is not the essence of the findings!
Of course the ABSOLUTE, VISUAL brightness is of relevance in practical terms.
And this is what I tested - in darkness, and in bright sun.
No difference in brightness between LM4 and LMP with manual max in the night - nor with max triggered by direct sun!
Hence having a Samsung device does NOT mean that you have this problem.
And as the Locus App code itself for the devices is the same, the difference most probably is in the device dependent libraries - and its inteference of settings, AI, optimization, all this jungle that is hard or near impossible to debug from outside.
Maybe Menion nevertheless has an idea to analyze deeper.
Cheers
Michael
Jack Russel has written so with him the brightness is not 100%. He is only at 75%
So you have a display 100% and still badly readable? ?
I think it's a Samsung .... as Michael says.
Samsung presents different settings, depending on which app, time, etc. is used.
How do you see the samung settings from: Smart Stay and Adaptive Brightness.
Are these both disabled?
I just did a bit of Google towards Samsung and brightness.
One advise was to try resetting all SETTINGS (not the whole device!!!) Fromer may still be a pain, but maybe someone can try on an affected phone?
Quote from: freischneider on July 25, 2021, 21:23:05
Jack Russel has written so with him the brightness is not 100%. He is only at 75%
So you have a display 100% and still badly readable? ?
I think it's a Samsung .... as Michael says.
Samsung presents different settings, depending on which app, time, etc. is used.
How do you see the samung settings from: Smart Stay and Adaptive Brightness.
Are these both disabled?
Both functions are deactivated.
It may be that the problem lies with the Samsung, but why not with LM 3? This app from the same developer runs perfectly on the Samsung with the same settings.
Another interesting attempt in the living room last night. The sun was shining through the window from behind. I took my Samsung S 21 ultra and opened some apps:
All apps got brighter after opening, only LM 4 got darker. I repeated the experiment several times, always with the same result.
To be honest, I don't really care whether it's just the Samsung or the app. Samsung is not an exotic product that is only used by a few.
I expect a solution from the developer, otherwise I will certainly not extend my subscription, but will continue to work with the old, very good app.
Quote from: freischneider on July 25, 2021, 21:23:05
Jack Russel has written so with him the brightness is not 100%. He is only at 75%
On both Smartphones (S7, S20) is the brightness 100%. Immediately the brightness drops to 75% within 30 seconds. But I do not know the exact brightness (75%, 65 %, ?). Not readable in the sun, you can see the darkened display in the shade.
The controller is still at 100%.
When I put LM4 in the background, the brightness rises to 100% within 30 sec.
For my tests, all energy-saving modes were deactivated.
Next Test. On my S7, all energy-saving modes are activated. LM3 is on Android 8 preferences App "optimized". LM3 has no problems and stays on max brightness. LM4 on my S7 = problems.
But even in the shade you can see the difference. However, it is not immediately noticeable.
The display is darker, but remains readable.
For my last tour I used LM3 (on my S20). The display remained at 100%. I no longer knew this brightness. Wonderful.
Max. brightness and all is easy readable. The whole time.
In my opinion, the problem has other causes. This is what you should pay attention to.
It is not the one Android version or one Device. Different devices (for me S7 and S20, for Wole different devices) , different Android versions (8 and 11 and perhaps other versions).
The problme is not "one" Android version or "one" Device (for example only Samsung S20).
The problem or context is the difference. And not all devices are affected. Why ?
The next consideration. Samsung will bring a comprehensive update in 2 months. But the S7 or S8 will not get this update. So a Samsung update does not help.
In this different one would have to search (perhaps LM3 to LM4 or what LM4 functions concerns "many" Android versions )
I know. That is not easy. Sorry.
Quote from: Holger on July 25, 2021, 17:53:43
Interesting how everyone tests the settings on the device.
Why does you change the settings? If both apps show different results in equal settings, it can not be on the device!
That´s correct But it may be a help for Menion to find the reason.
Quote from: michaelbechtold on July 25, 2021, 20:01:58
Hence having a Samsung device does NOT mean that you have this problem.
And as the Locus App code itself for the devices is the same, the difference most probably is in the device dependent libraries - and its inteference of settings, AI, optimization, all this jungle that is hard or near impossible to debug from outside.
Maybe Menion nevertheless has an idea to analyze deeper.
I do not think so.
Topic same Code : Then the problem should exist with LM4 and LM3.
Topic device dependent libraries :
Then the problem with the devices should change, for example : On S7 max. brightness stays with LM4 and not on my S20 or with Andorid 11 max. brightness stays and not with Android 8.
There are too many different devices libraries are affected. But overall few devices.
Or only few people noticed that LM3 had more brightness. Just like with me.
I initially thought that the poor visibility was normal with LM4.
After LM4 and now with LM3 it is a difference like day and night.
I've spent on this weird issue almost whole day ... and I still have no idea, sorry.
The issue happens to me as well on mentioned SGS7. The nice test is a slider with the brightness that does not react in LM4 in last red segment ... wtf >:(
Thanks Menion for clarifying once again that the problem is with the Samsung devices.
If you read some posts, you already lose faith in yourself.
Even if I repeat myself, I found the problem with the S 6, S 8, S 10+ and the S 21 ultra, so you can really say that it exists with all Samsung devices.
It would be nice if you could solve the problem, because I want to continue using both LM 4 and my Samsung devices. I also believe that Samsung is not an exotic product, but is used by many users.
Of course, it is astonishing why so few reports are received. Either the users have never used LM 3, so that a direct comparison is missing, or they do not attach particular importance to readability in bright sunlight, but only record the tours.
Hi Wole,
definitely no need to lose faith, but rather look at the very details of the fact collection.
There is an impressive collection of Samsung MODELS that MAY suffer from the issue (you named them below).
But NOT ALL of the DEVICES of those models suffer the issue!
So, same Samsung model, but different behaviour - with the exact same software (as far we can tell - there is a lot of jungle beneath the surface and the app code of a smartphone).
And we can assume that the issue is not hitting the majority of the devices of those models. Otherwise there would be much more complaints. And believe me, if my Samsungs were affected, I would be loud and clear (Menion knows a bit of that :-)
Up to now, nobody knows what differentiates a device of the same model having the problem from one that does not suffer.
A typical strategy in IT for such situations is to revert to a safe ground. Which here can mean two things:
1) a factory reset: heavy impact to the user (and not yet done yet, if I screened all the thread pages correctly). Only realistic for devices not regularly used. Maybe someone has such.
After restart NOT apply Google recovery of ANY kind. ONLY install LMP and LM4 and then re-test.
2) an Android SETTINGS reset, which should be possible at least in newer Android releases on Samsung devices. To be accurate and take out assumptions as far as possible, backup the SETTINGS in LMP and LM4. Import settings of the other kind to LMP or LM4. Test. Then use the other settings backup for both, LMP and LM4. Test.
After 4 decades in IT and SW trouble shooting I learned to not believe in magic. Not regarding the root causes, nor for the remedy of issues. But that it can be tedious, lenghty, yet SYSTEMATIC work.
Good luck and cheers
Michael
Next Test :
I have LM4 installed on a friend's S7. Same problem.
New and clean install. No own profil. Max. manual brightness.
I have disabled most google services on my S20 and S7.
The S7 of my friend has no restrictions, other preferences and other apps.
Now I have 3 Devices with problems (2x Samsung S7 and 1x Samsung S20).
I have tested all Devices with a brigthness meter.
All devices have a different max. brightness.
But all devices have the same dimming. 35% darker than max brightness (34-36%)
There is a reason why many user do not report. It is hardly noticeable under normal conditions.
Only in direct Sunshine is the Display unreadable. But LM4 is a Outdoor app.
Hello Michael Bechthold,
thank you for your post. You are right when you say that it is difficult to identify the problem because there are so many different software combinations.
Nevertheless, in my opinion it is a problem with Samsung and / or LM 4 and occurs with all Samsung devices.
I have for excample bought the Xcover Pro a second time on a trial basis, only installed LM 4 there and the same problem again.
Yesterday evening I borrowed the S 20 from my daughter-in-law and installed LM 4 there. Today at noon I'll test it in the sun. I'll add a little post tonight.
Of course, as JackRussel notes, it is always important that the device is attached to the bike and that the perspective is always the same. Only then can I compare LM 3 and LM 4 and recognize the serious differences.
Once again, when Menion takes his old S 7 out of the blue and has the same problems there, that's very telling.
Only good luck and cheers really doesn't help here. I stick to the fact that a solution has to come from the developer.
Hi guys, the discussion here is not necessary.
As I wrote, I'm well aware of this issue. I've compared all major parts of LM4 and LM Pro that differ and can't find any reason why it should affect screen dim. I've also updated all possible libraries that the app use and still no difference. It has to be some issue on the Samsung (if on all devices or not is not important now), but it has to be somehow connected to anything in the LM4 app ...
So for now, I blame my code, but ...
Hi Menion,
thanks for your clarification. I assume that the problem is really being worked on and will wait and see.
Hi,
maybe the problem has started with introduction of dark/light theme settings (and internal reaction of LM4 according to settings)
In LM3 this doesn't exist ...
I have found my old Samsung S5 mini with Andrdoid 6.0.1.
I have made the same tests after factory Reset. But no problems with LM 4.2.1. The brightness stays at 100%.
Maybe it is a help for Menion.
Very interesting, indeed ...
Did it show the problem BEFORE the factory reset?
Did you backup Locus settings from the one with the issue and use them in the S5 mini?
Are the Android settings the same - as far as this is possible between very different versions?
Cheers
Michael
@michaelbechthold
Sorry, no.
The S5 is agonizingly slow and I have forgotten it.
Therefore factory Reset, out of the box, no Android preferences.
Then install LM4 without profil. Also here out of the box and no preferences.
But Wole said that he had also made a factory reset.
Quote from: JackRussel on July 30, 2021, 08:36:37
But Wole said that he had also made a factory reset.
Several times!!
Used a virgin Google account to avoid settings and other history being inherited?
Quote from: michaelbechtold on July 30, 2021, 11:12:05
Used a virgin Google account to avoid settings and other history being inherited?
No, I used my normal google account.
Quote from: michaelbechtold on July 30, 2021, 11:12:05
Used a virgin Google account to avoid settings and other history being inherited?
Not virgin, but
my S7 and S20 same Google Account.
S7 of my Friend different Account, my S5 mini different Account to all other.
Any chance to do a factory reset on the S7 and use a virgin Google account?
There are (at least) 4 dimensions where - from an architectural point of view) the trigger for the problem can come from:
1) device model(s)
2) Android settings
3) Locus settings
4) Locus code
Or a mix of above, to add insult to injury.
What we know so far:
- no smoking gun from #4 (alone, maybe unknown combination effects)
- no smoking gun from #3, but not targeted by testing, as far as I see
- #2 is intransparent to me - what happens in the underground of Android and its settings when you re-use an existing Google Account after factory reset? I do not know.
- does the device model alone make it? I do not recall all the tests by various people. I.e. is there a model that works for one and does not for another?
Quote from: michaelbechtold on July 30, 2021, 13:30:34
Any chance to do a factory reset on the S7 and use a virgin Google account?
I have now decided to do a factory reset on my S7. I will report as soon as I have the results.
Quote from: michaelbechtold on July 30, 2021, 13:30:34
Any chance to do a factory reset on the S7 and use a virgin Google account?
There are (at least) 4 dimensions where - from an architectural point of view) the trigger for the problem can come from:
1) device model(s)
2) Android settings
3) Locus settings
4) Locus code
Or a mix of above, to add insult to injury.
On my S7 I have made a factory Reset. Same problem like Wole.
Before S7 factory reset : Many years no Device reset, Google settings very restrictiv, many apps,
-> Display darkening
After S7 factory reset :
Android 8.0.0 Out of the box,
no Google settings (all original)
new and clean Play Store Account,
no Android settings,
no Apps
only Locus 4.3 App no profil, no Locus settings
-> Display darkening (test with brightness meter)
For me there are only 2 reasons :
1.) Locus code
2.) Different Firmware versions
Sorry Menion. I know, it is not easy.
So for now I'll stay with Locus 3.x but LM4 is better. ;D ;D
At the moment I also only use LM 3. For the pure navigation I don't see any big improvement in LM 4, but I think the web tool is very good and would like to use it in the future.
So I hope Menion can solve the problem.
In this respect it means for me: wait and hope.
Hello Menion,
are you still trying to solve the problem or can it be assumed that the app will not work permanently on Samsung devices?
Hi Wole,
I would like to, but sorry, I see no option even if I see (a very little dim) a problem on my SGS7. I've tried my colleague's S10 device and no problem at all. It is currently an unsolvable problem to me.
Thanks for the answer. I don't believe that other Samsung Users don't have these problems, but I have to accept your decision.
Wole, you have several devices. Maybe you can parcel Menion one with the problem.
Quote from: freischneider on August 25, 2021, 16:53:41
Wole, you have several devices. Maybe you can parcel Menion one with the problem.
Menion knows the problem and own a samsung device with this problem (look to his article from 23.07.). But it seems that he doesn't want to put any more work into problem solving because he doesn't know what to do next. There is no other way to explain his behavior and his response.
Quote from: Wole on August 25, 2021, 17:18:03
Quote from: freischneider on August 25, 2021, 16:53:41
Wole, you have several devices. Maybe you can parcel Menion one with the problem.
Menion knows the problem and own a samsung device with this problem (look to his article from 23.07.). But it seems that he doesn't want to put any more work into problem solving because he doesn't know what to do next. There is no other way to explain his behavior and his response.
that is an incompetent assumption. He's already searched all the code and hasn't found anything. and it's very weak on his device. And it doesn't appear on the colleague's S10. Maybe it's a Samsung problem too.
Incompetend?????????
Well the OS is complex, unfortunate problems, where sometimes you find a solution just because you hear of another dev who struggled with the same and luckily found an answer... or his users... it happens. Unfortunate, but this is reality. And please compare with the big company realities. Google. They never answer, they have no changelogs mostly, I wouldn't ever waste time on reporting them anything. Apple. They give you tools which aren't open to do what you need. You have to need what they offer... and look no further.
Let's keep our eyes and ears open, there is no doubt Asamm does the same.
Doesn't want? Funny ... :'(
As a Samsung user, I wondered if (also with all answers) this still only concerns the Gold version. I am a Silver user myself and I have the feeling that I have no problems there. is that important to know?
Although I have a silver abo (and was one of the early live users of LM4) since 4 weeks I completely switched back to LM pro.
And in this time I did several trips ... and enjoyed a bright display.
I'm really confused about this recent discussion because I really want to switch back to the active developed LM4 ... but only with this problem solved.
I am just as confused. That's why I made a conscious decision to express myself a little more clearly.
Again: The problem is guaranteed not to be a single problem, but affects all Samsung users, assuming the same conditions. Why do I have the problem on all of the devices mentioned, with the Xcover Pro even on the replacement device. Why does LM 3 work great, but LM 4 doesn't. So, according to the logic, something can only have been changed in the code of LM 4 that does not work with the operating system.
But it annoyed me, and therefore my contribution, that after many contributions Menion himself found the error on his device, but now points out the allegedly non-existent problem with his colleague and apparently no longer investigates the problem.
This is not how I imagine support, especially after it has to be paid annually. An app basically has to run on all devices, especially since Samsung is not an exotic device.
Following the suggestion from freischneider, it might make sense for someone who claims to be able to work with him to send us the device so that we can really test the device under the same conditions. So I'm curious about the result.
In conclusion: I know that troubleshooting is a huge problem and expressly state that the app, at least up to LM 3, is the best navigation software I have used so far. So it's really not about nagging, I don't want to sell my Samsung just to use the new app.
There seems to be some misunderstanding or I'm too stupid to understand this cyclic communication.
So again (summary)
- I'm aware that there is a problem with brightness on some (not confirmed on all!) Samsung devices
- I also think that on 90% it is caused by my code in the app
- I have device for test with this problem
- I've spent 10+ hours by searching and testing ... no effect
- I've spent a lot of time comparing Locus Map Pro and Locus Map 4 code that differ and that may have effect ... no discovery
- You may send me any devices you want, you may pay me a million, but I currently DO NOT SEE ANY OTHER OPTION TO TEST, I'm currently out of ideas!
- I'm not stupid enough to let satisfied paying users leave because of any issue in the app, but again, I simply DO NOT SEE ANYTHING TO DO NOW!
Sorry.
Thank you for this Statement, Menion.
So I can only hope that LM 3 can be User the nett years.
Menion's statement is clear to me. Still, I do see a possible solution unless I'm a moron.
I have a feeling that something is wrong with the cide abortus brightness settings in the software that affects the user settings as set on the smartphone. The solution seems simple to me. Remove all settings from the software regarding brightness (such as whether or not to use dark mode). Even remove the reference to the device settings.
The software will then use the user settings on the smartphone. If it still does not work, then I think there is a problem with the smartphone. Is this too simple thought?
In case, the app is in the light mode, it uses exactly identical theme like Locus Map Pro. The only change is a modification of few colors, but nothing more. So you may try to switch the app into a light theme if it has any effect.
Good idea ... I'll check it when sun is coming back (could last a little bit this summer 🙄)
Since the sun was shining today and my vacation is starting, I found some time to test the whole thing in the sunlight.
Unfortunately, the switch to "light" did not help.
Locus Map 4 simply darkens after a while.
Then I had the idea to install an "autobright" app to at least see the brightness values.
After my familiarization and setting up the app, I saw that you can use it to completely regulate the brightness. my hope was that with this app I could bring the brightness to 100% even in sunlight. Unfortunately, even after this app completely took over control of the brightness, lm4 darkened again after a short time. although the brightness is displayed at 100%.
Thank you for your efforts, Jonny.blue. I had already done exactly these tests. I had installed "Light Control" as the app.
Again, this app is unable to force LM 4 to stay light. But it works with other apps.
In one of my previous posts I said that I wanted to test my daughter-in-law's S 20. Here too, LM 4 darkens.
I am annoyed that some USERS say it is only due to my devices. I claim that if everyone were to test under the same conditions, the problem generally exists with LM 4, otherwise it would be absolutely unlikely that only I would have the problem with the S 6, S 8, S 10, S 20 and S 21 and the Xcover pro even twice (because I replaced the device).
However, I accept that Menion cannot understand the error in the app.
I am now sticking to LM 3 and, as I have already said, I will wait and see if there is anything new on this topic.
So that the problem will not forget. Compared twice Note9 with identical setting. Cloned by Backup.
Left LMPro - Right LM4. If possible also identically set. There is a clear gray fog on the LM4.
The device with LM4 is also clearly warmer and the battery faster empty (//)than that with LMP.
I am currently playing Android 12 on my Samsung S 21 Ultra 5G.
Hopefully it is now possible to use Locus map 4 on the device.
However, due to the position of the sun, real statements will probably only be possible next summer.
Now I have Android 12 on my Samsung S20 FE 5G.
It was marked as not optimized.
No improvement. Same problem. Too bad.
Really very sadly that the problem still exists ...
Meanwhile I'm back to the september version of LM pro ... although I have an abo of LM4.
Once again my hope that the problem could be solved by the new Android version is destroyed.
What really annoys me is that the developer, who is ultimately responsible for solving the problem, seems to have given up trying to find a solution to the problem.
Since the problem appears to occur with all Samsung devices, I would have expected at least a hint when buying it. So every Samsung owner, unless following this post, is buying software that is basically useless in full sunlight.
First of all, I canceled my subscription to the gold version and will stay with Locus Map pro (hoping that a new version will not make things worse here either).
So that there are no misunderstandings: I still consider the app to be the best I've had so far. That's why my disappointment is all the greater.
Has something changed about the brightness problems? Today I had the impression that it's not quite so blatant anymore.
Really?
hank you for the answer. I will try your suggestion. I worked with "System" till tomorrow.แทงบอลขั้นต่ำ10บาท (https://www.ufa222.info/%E0%B9%81%E0%B8%97%E0%B8%87%E0%B8%9A%E0%B8%AD%E0%B8%A5/)
Hello everyone,
at first, sorry about my bad English.
I have this problem too.
Is there a solution to this problem?
Some time ago I switched from Locus Map 3 Classic to Locus 4 Silver.
With Locus 3 bright display, everything top. With Locus 4 the display darkens after a short time, almost to the point of being unreadable.
The error occurs on a Samsung S10 as well as on Samsung S20 and Samsung A52s.
With my Doogee S96 with Locus 4, the basic brightness of the display is unfortunately too weak to be able to judge the effect.
But rather not, the display looks just as bright (better say dark) as with Locus 3.
Unfortunately Locus 4 is not usable for me on the bike and I will stay with Locus 3, check from time to time whether the error is gone.
Happy (with Locus 3 Classic)
I guess I'll have to bury my hopes after further attempts over the weekend.
Since the developer apparently no longer tries to find the error, I can only say for myself that Samsung devices are unsuitable for LM 4 (or vice versa). Probably too few use the exotic make?????
Only LM 3 runs satisfactorily on these devices. I've pointed out before that it should be officially pointed out for the sake of fairness, but even that doesn't happen, too bad.
I have no solution ,
but I can confirm this issue on my Samsung A52s.
I've never seen this problem with my two Samsung tablets. (I have no Samsung phones.)
Quote from: Wole on May 09, 2022, 10:49:48
Samsung devices are unsuitable for LM 4
@Wole saying (all) "Samsung devices" is a very broad brush stroke - I have no problems with a Samsung A520, although admittedly this is an older device now.
Quote from: Andrew Heard on May 10, 2022, 01:20:46
Quote from: Wole on May 09, 2022, 10:49:48
Samsung devices are unsuitable for LM 4
@Wole saying (all) "Samsung devices" is a very broad brush stroke - I have no problems with a Samsung A520, although admittedly this is an older device now.
Do you use the A520 and LM4 in bright sunshine ?
In cloudy conditions you can not see it or minimal.
The darker display don`t show immediately. It shows within 30 seconds. So you have to look at the display longer.
Quote from: Viajero Perdido on May 09, 2022, 17:16:19
I've never seen this problem with my two Samsung tablets. (I have no Samsung phones.)
I can't say about tablets. When I'm cycling or hiking, I only use my smartphone.
And here are the newer devices, I tested S 8 and up, see post, useless.
Quote from: jajaballard on May 09, 2022, 12:34:50
I have no solution ,
but I can confirm this issue on my Samsung A52s.
Look to the question of JackRussel. I dont't believe, that you testet LM 3 and LM 4 in bright sunshine.
The comparison between LM 3 and LM 4 is important. Of course, this is the only way to see the weakness of LM 4.
Quote from: JackRussel on May 10, 2022, 15:46:03
Do you use the A520 and LM4 in bright sunshine ?
@JackRussel - that's my usual case - for cycling.
Quote from: Andrew Heard on May 11, 2022, 09:13:38
Quote from: JackRussel on May 10, 2022, 15:46:03
Do you use the A520 and LM4 in bright sunshine ?
@JackRussel - that's my usual case - for cycling.
But did you really compare LM 3 and LM 4?
I just saw that A520 has Android 7.0??? The problem only occurs with Android 9 and higher!
LM4, Android 12, Galaxy S10, Locus Always screen on, full sunn in my back: stays at full brightness as long as I want (Android shows the red sun icon)
Switching off the Always screen on in Locus will die the screen after short time.
Quote from: michaelbechtold on May 12, 2022, 13:32:54
LM4, Android 12, Galaxy S10, Locus Always screen on, full sunn in my back: stays at full brightness as long as I want (Android shows the red sun icon)
Switching off the Always screen on in Locus will die the screen after short time.
Hallo, ich vermute nach Deinem Namen, dass Du aus dem deutschsprachigen Raum kommst. Daher schreibe ich hier auf deutsch, um mögliche Unklarheiten, die durch Übersetzungen entstehen könnten, zu vermeiden.
Ich verstehe Dich so, dass Du in Locus unter Einstellungen - Steuerung - Anzeige - Display immer an "immer" ausgewählt hast (oder meinst Du mit "Switching off/on the Always Screen in Locus" etwas anderes?). Wenn Du ansonsten keine anderen Einstellungen hast, kann ich mir das nicht vorstellen, denn auch ich habe diese Einstellung. Auch bei mir ist das rote Icon in Android immer vorhanden. Dennoch dunkelt Locus ab, allerdings stelle ich das Problem eher fest, wenn die Sonne von der Seite bzw. - ganz extrem - wenn sie von vorne kommt. Könntest Du das auch noch einmal überprüfen? Einen Vergleich zwischen LM 3 und LM 4 unter denselben Sonnenbedingungen hast Du auch gemacht?
Gut geraten ;-) Aber ich antworte in Englisch für breiteres Auditorium ...
I had not compare LM4 and LMP yesterday, as screen brightness of LM4 Was never less that Android UI.
But today I did extended tests:
- LM4 and LMP behavior exactly the same way, keeping max brightness, i.e. do not dim, even after longer wait.
- I also tested angles towards the sun, turning 90 degree every 20 sec: no change
Setting is indeed this "Display immer an" (Screen always on on my device)
PS: hast Du andere privilegierte Apps (Admin Rechte), die da reinfunken könnten. Bzw. andersrum: hat Dein LM4 Admin Rechte?
Quote from: michaelbechtold on May 13, 2022, 12:05:48
PS: hast Du andere privilegierte Apps (Admin Rechte), die da reinfunken könnten. Bzw. andersrum: hat Dein LM4 Admin Rechte?
We can continue our discussion in English (or switch to the German forum). It only mattered to me that we mean the same settings. This is not always clear in a translation.
But now a stupid question: Where can I see whether LM 4 has admin rights? Under the app info I had previously been "Change system settings - not allowed". But I also have this attitude with LM 3.
Admin righjts: when I mentioned this, I recalled the Locus request from quite some time ago.
Now I checked on my device: BOTH apps doe NOT have the admin right ... (still work fine)
Hello Michael Bechthold, thank you very much for your post of May 12, in which you say your S 10 does not dim. I couldn't believe this statement at first, so I rummaged through the relevant Samsung forums again.
There was actually often the statement that these problems do not exist with older devices such as the S 10.
So this afternoon I went on a bike ride in full sun for 2 hours using the S 10 +.
In fact, LM 4 did not get darker at any stage.
This obviously means that all devices that are younger than the S 10 series dim and are therefore not suitable for the use of LM 4.
I have therefore decided to stick with the S 10 +. This meets all my requirements (large and bright display, good battery life, SD card slot).
I have a Samsung S7. A friend of mine also has an S7. Also tested after a factory reset.
Same problem.
Android 8, 11 and 12 are affected in my case.
Exynos and Snapdragon.
The S10 seems to be a fluke.
I could not see any connection yet.
I have a Samsung S7. A friend of mine also has an S7. Also tested after a factory reset.
Same problem.
Android 8, 11 and 12 are affected in my case.
Exynos and Snapdragon.
My S7 is older than the S10.
The S10 seems to be a fluke.
I could not see any connection yet.
I'm happy my S10 is not the only happy one in this community :-)
With JackRussel's finding, however, the overall situation stays weird. This thread is SO old that I do not recall if anyone has done an Android (!) system level debug log? In addition I'm not sure if all the relevant displayrelated events are caught and logged at all.
Anyone knows?
When it comes to Samsung: S21 and following models - not for me, as they lack micro SD cards.
The A5x or A7x series will be good enough for me, once my S10 gets too slow and worn, some years from now.
I will try to test an A52 with LM4 maybe next weekend and report (LM3 is already installed).
There has been no common ground so far. That is confusing.
- I have 2x Samsung S7, Android 8, DBT region code, factory reset/no factory reset --> problems.
Samsung S7 (Graf Geo), Android 8 --> no problems.
- Samsung S10 (Happy) --> problems
Samsung S10 (Wole and michaelbechthold) --> no problems
other devices with problems :
Samsung S20 and A52s (Happy), S6 S8 S10 S21 ultra (Wole), S7 (Menion),
other devices without problems :
S5 mini Android 6.0.1 (JackRussel), S8 (freischneider), S21 (para), A520 (Andrew Heard)
There is now really no common ground.
Maybe a poll would be useful.
I think for starters (device, Android version, region e.g. DBT/EU, security patch level).
I would take part in the poll.
For me there is also the fact that I had the problem on the S 10 + about a year ago. Since I then bought the S 21 Ultra, my wife got the old S 10 +. Here I did a factory reset beforehand and did not reinstall Locus.
After Michael Bechthold reported that he was running S 10, I just installed LM 4 on the S 10 + yesterday, just for fun, and it worked (see my post).
Can it possibly be because LM 3 and LM 4 cannot be installed at the same time? That's the only difference from last year's test.
I will test my S 8 again later, once with both installations and once with a factory reset and then only LM 4.
If the S 21 really works for Para, why not for me???
On my S10, both, LMP and LM4 are installed in parallel.
With JackRussels compilation plus Wole's latest update, we have contradicting effects for the same device.
But without a differentiating parameteer that could explain. Hence a poll can only help if we collect tons of settings, beyond what has been reported in this thread, and then try to find a pattern.
I'm on the search for a successor for my good old S7 currently. Just tested a S22 lately. The first obvious thing that I noticed was the display dimming under Locus 4 way too low for reading it comfortably outdoors. All other apps stay at max brightness, except Locus and Google Maps. Looks like GPS apps are treated differently in the Samsung internal thermal management. The phone wasn't even hot yet, just shortly in max daylight.
I ended up returning the S22 just for that reason. It's sad as there are almost no other phones of an acceptable size on the market nowadays. Testing a Xperia 5-III in parallel. This is also dimming in sunlight, but only after getting hot and not restricted to GPS apps.
Quote from: michaelbechtold on May 16, 2022, 08:59:21
With JackRussels compilation plus Wole's latest update, we have contradicting effects for the same device.
That's the problem.
Wole did a factory reset (S10+) and the problems were gone.
I did a factory reset on my old S7 and only installed LM4. The problems have remained.
Axelpix:
I have the S21 Ultra. You can use Locus 3 super on this device. Oddly enough, nothing is insulated there. Readability in full sun is very good.
It's all about Locus 4. Basically, LM 4 just adds the web. If you don't need that, the LM 3 is a good choice.
Locus 4 runs e.g. B. on the Xiaomi redmi note 10 pro in full brightness. Nothing is dimmed here and the size of the display corresponds to that of the S 22.
I am attaching a photo of the phones from left to right Samsung S 8, S 10 +, S 21 Ultra and Xiaomi Redmi Note 10 Pro to this post.
Even if the picture is not particularly good, you can see that the cheapest phone, namely the Xiaomi LM 4, is the best.
In the practical test I just carried out, you could at least see something on the S 8 and S 10 + (but you couldn't read the names of places, etc.) and the most expensive device, namely the S 21 Ultra, failed completely.
But the Xiaomi Redmi Note 10 Pro was able to inspire. Here you could always see the map very well, no matter how the sun was shining.
LM 3 is very recognizable on all devices.
Since, according to my Google research, other manufacturers apparently also dim their displays under incomprehensible conditions, there is hardly any future for LM 4 if nothing changes in terms of software.
Sure there will be other phones that do LM 4 well, but
for me the testing is now hopefully over and the decision is made: I'll stick with the LM 4 and the Xiaomi Redmi Note 10 Pro for the time being.
After all this discussion hope returns ...😉🤔
Installed LM4 beside LMP on my S10e ... and for me the unreadable screen with LM4 is still present. 😭
Deinstalled LM4 and work with LMclassic ... 🙄
First question:
Someone indicated that setting LM4 to "Screen always on" might solve the issue on newer Samsung devices. Is this a solution that can be confirmed by someone else?
Second question:
During my tests with the S22 I noticed that the same behaviour (screen dims to ~50% brightness) also happens with the onboard Google Maps app. This led me to the conclusion that it might be the GPS activity that forces Samsung to better limit the backlight power. But if LM3 (LClassic) is still good, that's not the case. Can anybody confirm this consistency with Google Maps?
Regarding the first questions: I tested it, but it doesn't help.
Google maps also dims. But it is by no means due to the GPS, otherwise LM 3 should not continue to shine super.
Incidentally, other GPS applications such as TwoNav or OZI remain fully bright.
It's all down to LM 4.
Wole, you have a working and a non-working Samsung LM4 device (mine do all work ...):
- does the screen timeout on Android level define how fast the dimming occurs?
- to test for LM4 and for Google Maps
- closing PLUS Android killing the resp. other app
Quote
Can anybody confirm this consistency with Google Maps?
Yes ... this is exactly the same problem like LM4.
Quote from: axelpix on May 18, 2022, 15:26:25
Can anybody confirm this consistency with Google Maps?
Same problem here.
Now, those who have the problem should take the issue to Google and Samsung Support.
But only as a problem between Google Maps and Samsung, not diverting to Locus.
Both of those giants would easily ignore Locus. But they are not in a position to ignore each other ...
Quote from: michaelbechtold on May 18, 2022, 16:19:22
Wole, you have a working and a non-working Samsung LM4 device (mine do all work ...):
- does the screen timeout on Android level define how fast the dimming occurs?
- to test for LM4 and for Google Maps
- closing PLUS Android killing the resp. other app
First of all: In a direct comparison with the Xiamo 10, all Samsungs are darker (see my picture)
Screen timeout is set to 2 minutes on all devices.
What do you mean by closing Plus Android?
By PLUS Android I mean to swipe the app out of the Android App history.
The square in Oldenburg versions, the 3 vertical lines in current Androids.
To rule out any potential (indirect) interference between Google Maps and Locus.
Quote from: michaelbechtold on May 19, 2022, 08:45:20
By PLUS Android I mean to swipe the app out of the Android App history.
The square in Oldenburg versions, the 3 vertical lines in current Androids.
To rule out any potential (indirect) interference between Google Maps and Locus.
Thanks for the hint. You mean the "close all" notice, right?
I do that regularly anyway.
Google Maps is no longer installed on my phone.
It would also be interesting to ask why insulation is used at all.
The forums say that overheating should be avoided.
By pure chance, I was just sitting in the car in a car park under full sun.
The outside temperature was 31 degrees.
A warning message came up saying that the battery was overheating (41 degrees). I started LM 4 and the app ran uninhibited in full brightness. Do I need to understand this? Does it only insulate at full brightness, regardless of the temperature?
Addition:
On Monday I started LM 4 on all devices. The temperature was 13 degrees and the sun was shining. All Samsung devices darkened here.
Just an idea for Tasker nerds amongst you. Maybe it can help you debugging the brightness issue? There is a command called "Custom setting" which can get/set values from Android settings. Screenshot is related. Not having a Samsung phone myself.
Quote from: tapio on May 29, 2022, 12:03:37
Just an idea for Tasker nerds amongst you. Maybe it can help you debugging the brightness issue? There is a command called "Custom setting" which can get/set values from Android settings. Screenshot is related. Not having a Samsung phone myself.
Do you mean the view on my screenshot ?
The Tasker options look a bit different for me.
The display still gets darker
P.S.:
I wrote a short task. The display brightness is permanently set to maximum brightness after 20 seconds.
No success. The problem is that the display dims but the settings remain at maximum brightness.
When I manually dim the display, the display always brightens after 20 seconds.
The task works.
The display gets darker without changing the slider.
I tried the last Locus 4 update (02.06.2022), but the brightness in direct sunlight is still bad!
So I had to return to the older version of Locus. The brightness of the dipleje is better.
A little pity, but so far I have off the renewal of the subscription ..
@JackRussel, I was referring to <screenshot>, the action is called "Custom Setting", maybe there is something useful for analysis.
Quote from: tapio on June 26, 2022, 11:41:37
@JackRussel, I was referring to <screenshot>, the action is called "Custom Setting", maybe there is something useful for analysis.
thank you very much. I have found it.
Sorry for the late reply. I was away for a few days.
The hw_Screen option is not shown for me. I also have no other success so far.
I have no hope either.
The problem is this. When the display dims, the slider still stays at max brightness (255).
So I can't set a higher or new value.
But I will test a little more.
Hi guys, thanks for the time you still invest into this issue.
I have no idea so far, but at least I need to know: does this problem happen only when the main map screen is visible, or does it make no difference and happens on every big screen of Locus Map 4 (Map manager, data manager, ...)?
Quote from: Menion on July 08, 2022, 10:20:34
does this problem happen only when the main map screen is visible, or does it make no difference and happens on every big screen of Locus Map 4 (Map manager, data manager, ...)?
It makes no difference. It occurs with any screen.
- Maps Manager, Data Manager, Online/Offline Maps, Settings, Tracking, .....
One of tapio's screenshots (was it from Tasker?) revealed a long list of Android screen related internal settings that you cannot view or change via Android UI.
There is a 99% chance that one of those settings is screwed in your devices.
One additional question. Did anyone try if "dark mode" or "light mode" set directly in the Locus Map 4 settings make a difference?
I've also found a topic on XDA (https://forum.xda-developers.com/t/screen-dimming-temporary-fix.3784813/#post-80810011) with probably the same issue. One suggestion was to disable animation in the device, so maybe you should give it a try.
Quote from: michaelbechtold on July 08, 2022, 12:57:58
One of tapio's screenshots (was it from Tasker?) revealed a long list of Android screen related internal settings that you cannot view or change via Android UI.
There is a 99% chance that one of those settings is screwed in your devices.
I have found this list. Yes, this list was from Tasker.
But for me there are no or only a few entries for brightness.
This is probably because tapio does not have a Samsung phone.
Huawei probably has other internal settings
Quote from: michaelbechtold on July 08, 2022, 12:57:58
One of tapio's screenshots (was it from Tasker?) revealed a long list of Android screen related internal settings that you cannot view or change via Android UI.
There is a 99% chance that one of those settings is screwed in your devices.
Yes. I cannot teach how to use Tasker, just want to say there's the possibility to find something.
https://youtube.com/shorts/WaJrpuMr4xU?feature=share
@JackRussel, did you also search in Type:System?
Quote from: Menion on July 08, 2022, 13:25:52
One additional question. Did anyone try if "dark mode" or "light mode" set directly in the Locus Map 4 settings make a difference?
"Light Mode" or "Dark Mode" make no difference.
QuoteI've also found a topic on XDA (https://forum.xda-developers.com/t/screen-dimming-temporary-fix.3784813/#post-80810011) with probably the same issue. One suggestion was to disable animation in the device, so maybe you should give it a try.
Thanks for the link. But there Huawei cell phones are affected and they do not cause problems in Locus.
Regardless. I turned off animation in developer options. Then I set the animation to 0.5x. No effect.
The option "under sunlight" does not exist on Samsung.
Thanks anyway.
Hi,
I just found this entry in an Android help forum:
https://www.android-hilfe.de/forum/samsung-galaxy-s22-ultra.4041/maximale-helligkeit-bei-sonneneinstrahlung-erzwingen-temperatur-limit-deaktivieren-how-to-no-root.1004285.html
I tried it (with google maps) ... and it seems to work.
Display remains bright ... 👍
I studied the (German language) Android forum entry and it shuts down the (partially emotional) Locus related discussion once and for all.
It is Samsung's strategy to cope with overheating and their approach, controlled by two hidden switches.
I set my two flags ... removed rights... and finaly deinstalled the app.
... and LM4 (and google maps) remains bright.
Quote from: michaelbechtold on August 02, 2022, 11:57:59
I studied the (German language) Android forum entry and it shuts down the (partially emotional) Locus related discussion once and for all.
It is Samsung's strategy to cope with overheating and their approach, controlled by two hidden switches.
First of all, many thanks to jonny.jlue for your tip.
I made the changes and my S 21 stays bright.
So far so good. But it's not that simple after all. The general question, why LM 3 no and LM 4 yes, is not answered by this.
During my two-hour bike ride yesterday (outside temperature 25 degrees and full sun) I measured the battery temperature with both LM 3 and LM 4. In both cases the temperature was identical between 34.4 degrees in the shade and up to 39 degrees in the sun.
I read in the forums a few weeks ago that Samsung generally darkens from 35 degrees, other manufacturers only from 50 degrees.
So why doesn't LM 3 darken?
But I don't invest any more time in answering this question. I had already bought the Oppo cheaply used and am very satisfied with it and the LM 4.
Is there also a way to prevent dimming on the Samsung S8? Alliance Shield does not display the two switches on this device.
Meanwhile unfortunately Alliance Shield has stopped working. Samsung has withdrawn the license for Knox. So even if you still find the apk somewhere to download, it will not get Knox clearance and therefore is not able to change our two thermal throtteling switches.
So we're back to where we started. No chance to prevent LM4 from dimming under daylight.
There must be something different in LM4 than in LM3 as LM3 doesn't dimm. Really no idea, Menion what this difference might be?
How long has the app stopped working?
I can only hope that once changes have been made to the switches, firmware updates will not reverse them.
I can't test that at the moment because we only have overcast weather, so the dimming isn't noticeable.
Is there any experience with this?
Ah damn!
There are a lot of differences between both apps, but not directly in the core. I'm still using a shared "app core" between Locus Map, Locus Classic, and Locus GIS.
It is really not about "I do not want...". I simply do not know. I've already spend many many hours on this problem and as you see, no success so far :'(
Quote from: Menion on October 01, 2022, 20:33:44It is really not about "I do not want...". I simply do not know. I've already spend many many hours on this problem and as you see, no success so far :'(
I am not a developer. Therefore, I only have observations.
I have installed the app Thermal Guardian from Samsung.
There I have activated: "Limit CPU Boosting when heating".
I have disabled : "Decrease maximum brightness when heating".
--> No success
The display gets darker on LM4 immediately after startup. Without further use.
I have the feeling that the call of a function directly after start is responsible for it. A function that is started at LM4 but not at LM3.
Are there any differences in the API between LM3 and LM4 ? Is the SDK the same ?
In my case devices with Android 8 have the same problem. So it should be a function, API, SDK that already existed in Android 8.
Samsung darkens the displays in heat. But my Samsung S7 with Android 8 does not have this feature. The display remains bright even in heat.
The display still gets darker right after starting LM4.
Only my old S5 with Android 5 does not darken.
A long answer from you is also not necessary. I am not a developer anyway.
I rather hope for a new perspective on the problem. Time is precious.
However, I hope for a "long" support of LM3. After all, I am still very happy with LM3. Maybe the problem will be solved sometime.
Don't want to sound too confident, but with the update to Android 13 on my S22 the issue seems to be gone. Haven't seen any dimming since then so far, even in direct sunlight after some minutes. Crossing fingers!
Important is the temperature, not only the brightness of the sun.
So let us wait for the summer and hope for the best.
No, for me it allways dimmed immediately within 1 minute after starting LM4, even at overcast daylight with an ice cold device. LM4 was barely usable at all. This has gone with Android 13. Already spend 2 hiking days out there with perfectly usable LM4.
I have now received the update to Android 13.
Unfortunately, nothing has changed.
The brightness and the speed of the dimming did not improve.
I must therefore continue to do without LM4 and hope for long support of LM3 by Menion.
I use the Oppo Find X2 pro as a bike sat nav because LM4 doesn't run properly on most Samsung devices.
Now my Oppo receives the ColorOS 12.1 software with the information that overheating protection has now been installed. According to the description, apart from a few apps, all the rest should be shut down when a certain temperature is exceeded.
Then it seems that the other manufacturers of smartphones are gradually following Samsung's example, so that it can be foreseen when LM 4 is no longer useful.
I will not import the update for the time being and have asked Oppo at what temperature the function will take effect.
I have now received the following answer to my request from Oppo about installing the overheating protection:
"When the temperature of the device reaches around 40 degrees Celsius, appropriate temperature control measures and strategies are taken. This is mainly to protect the battery to prevent damage to the device and battery.
If you receive a corresponding warning message or the device switches itself off, it is advisable to let the phone cool down before continuing to use it."
The Oppo reached temperatures of max. 44 degrees outdoors in summer. This means that the use as a navigation system for LM4 is so severely restricted that I will not import the update in order to be able to continue using LM4. This information for other users to decide how to deal with this issue.
I do not have this dimming issue with LM4 on my Samsung S22 Ultra running Android 13.
Since the post was reopened in the German forum, here is my answer in case it should interest one or the other:
"It shouldn't be the problem of a navigation app. I had already rummaged through all sorts of German and English-speaking forums. At least with Samsung, the problem also affects other apps, such as e-mail apps, etc.
If it only affects the navigation apps, the question always arises, why only LM4, why not LM3 as well? So I agree with JackRussel that Menion is accessing some function in LM4 that is causing the problem.
Thank God I was able to deactivate the function on my S 21 Ultra in good time via Alliance Shield. All firmware updates have not changed this, thank goodness, so I can currently navigate with the device and LM4 without blacking out.
What surprises me, however, is that these problems are not still being reported here or in the English-speaking forum. It shouldn't just be the Samsung devices that are affected, right. I also use an Oppo Find X 2 pro as a navigation device. A firmware update with the great improvement "automatically switches off the display if it overheats" has been offered here for months.
When I asked when the protection would take effect, I received the following message from Oppo "When the temperature of the device reaches around 40 degrees Celsius, appropriate temperature control measures and strategies will be taken."
Before that, there was the following message without temperature information: "If the device is exposed to high ambient temperatures and performance-intensive applications are run, the device may heat up more."
It follows for me that when dimming, the firmware distinguishes between "power-intensive and non-power-intensive applications." So it may be that LM3 is not performance intensive and LM4 is performance intensive, whatever the difference.
Of course I haven't updated the firmware, so I can currently run LM4 on both devices without any problems.
But how it will work with new devices later, when the devices are getting old, remains the exciting question.
Finally, the question: Has anyone ever tried to factory reset a device with current firmware on which Alliance Shield can no longer disable temperature protection and then before updating the firmware to the current state, the protection turn off? Because as I said, once deactivated, the protection apparently remains deactivated even with the latest software. "
Thanks
@Wole for the additional info.
I'm still unable to find any reason for this behavior, sorry. The core of both apps is still identical. We also tried even a basic clean app install and the result is the same. Also, it does not happen on any devices we currently have.
Complicated and still unsolvable issue ::)
Hi guys,
this topic is heavily discussed in German topic and I would like to do something with it, of course. But still not sure what. Because my Pixel 5 is close to the end of its developers lifetime (no more updates after Android 14, but the device will of course serve a few more years in our team), the best should be to purchase a device that will have this problem as well, so I will be able to test and play with it.
What devices suffer by this? Samsung devices, but any other? Has anyone experienced with the new S23?
Hello Menion, did you find the problem in the meantime?
Sorry Wole, no. No one in our team has any idea regards this problem.