Database Develop

[SOLVED] Backlight doesn't turn off when using TomTom...?

TomTom v7.450
Diamond ROM v1.37.405.1 WWE
Can anyone else confirm that their backlight never turns off whilst using TomTom, regardless of what setting/timeout they've got on the device's Power config page? Whether I'm using it on battery or mains the result is the same - backlight remains on continuously. If I shut TomTom down I then see normal behaviour and the light turns off after the set time.
Interestingly, if I install the very same TomTom CAB on my M600/Prophet it behaves correctly i.e. the backlight turns off after a time. The device remains continuously on, regardless of setting, but then that's what I'd hope for anyway as TomTom is no use if the device is not active.
Given the above, has anyone got any ideas as to why this might be the case, and what I might be able to do to solve it? I really want the backlight to dim as it will save a considerable amount of battery should I be using TomTom on battery... and it would automatically turn it back on when it comes to advised turns etc.
Incidentally, the backlight does dim/brighten in response to changes in the ambient light level so that's at least something - however I tried removing this setting in case that was the problem but it wasn't.
Mathew

I also use TOM TOM on my Diamond..and I think that is normal that the backlight is on when using the navigato..also if you use the Stand Alone navigator the back ligt stays on!
I can't see the use of the navigator with the device in standby..you should buy a car charger so your battery recharge during the utilization of navigator

Backlight doesn't turn off when using TomTom...?
Click to expand...
Click to collapse
I have a question, can this problem co-exist with the problem of backlight turning off too fast when making a call, or do these two problems cancel each other ?

MJNewton said:
TomTom v7.450
Diamond ROM v1.37.405.1 WWE
Can anyone else confirm that their backlight never turns off whilst using TomTom, regardless of what setting/timeout they've got on the device's Power config page? Whether I'm using it on battery or mains the result is the same - backlight remains on continuously. If I shut TomTom down I then see normal behaviour and the light turns off after the set time.
Interestingly, if I install the very same TomTom CAB on my M600/Prophet it behaves correctly i.e. the backlight turns off after a time. The device remains continuously on, regardless of setting, but then that's what I'd hope for anyway as TomTom is no use if the device is not active.
Given the above, has anyone got any ideas as to why this might be the case, and what I might be able to do to solve it? I really want the backlight to dim as it will save a considerable amount of battery should I be using TomTom on battery... and it would automatically turn it back on when it comes to advised turns etc.
Incidentally, the backlight does dim/brighten in response to changes in the ambient light level so that's at least something - however I tried removing this setting in case that was the problem but it wasn't.
Mathew
Click to expand...
Click to collapse
this is a feature (and a good one) and not a bug. i bet you don't want that when driving, right before a big intersection yr screen go off....
for example,the igo (that's what i am using) give you the option to go by the device or all time on.

KukurikU said:
this is a feature (and a good one) and not a bug.
Click to expand...
Click to collapse
If it was a feature I would expect it to manifest itself when installed on both the Diamond and the Prophet (given the common application) - the fact it doesn't suggests to me it is a 'quirk' (not necessarilly a bug) with the way it works on the Diamond. As mentioned, the backlight used to come back on when being advised of any directions etc and would remain until well clear of a junction so if it is a feature it's an unnecessary one!
Sometimes it is not convenient for me to use external power - when riding on my bike for example. And in such circumstances the high ambient light level used to be plenty sufficient for me to see the screen on the Prophet without the backlight being on - this is obviously great for conserving battery power as the light ranks as one of the highest power consumers.
I might see if the TomTom menu is still customisable and, if so, include the 'Backlight Preferences' icon that was present in versions of Navigator prior to v6.
Mathew

As mentioned, the backlight used to come back on when being advised of any directions etc and would remain until well clear of a junction so if it is a feature it's an unnecessary one!
Click to expand...
Click to collapse
interesting! didn't know that...doesn't bother the on\off of the screen while navigating in town (lots of instructions)? not sure i'll want all this flickering

Solved it!
In fairness, it seems that it is a TomTom quirk.
Specifically, the application has always (since I've been using it from v5) had a built-in setting for when to turn the backlight the backlight off (or, more accurately, when to allow the device to turn it off in accordance with your time setting) - the options being: 'Always', 'When on a walking route', 'When not charging' or 'Never'. The default being 'Never'.
However, since v6 the button to change this setting disappeared from the menus however given it is possible to customise the TomTom menus and, even better, to include icons from previous versions of TomTom (assuming the feature is still supported internally) I did the following to turn my backlight setting to 'When not charging'...
- Create a file \TomTom\SDKRegistry\TomTom.mnu in the root of the device
- Inside this file put the following:
Code:
MENUBLOCK|BLOCK_MAIN|BTM_DONE|
MENUPAGE|TASK_PAGE1|Main Menu|
MENUITEM|TASK_EXIT_APP|
MENUITEM|TASK_SET_BACKLIGHT|
MENUITEM|TASK_PAGE1|
- Now run TomTom and click the main screen - up will come a menu with two items in it - Exit and Backlight Preferences, the latter will allow you to configure exactly how you want the backlight to behave.
- Quit TomTom and delete the TomTom.mnu file - this will revert you back to the stock menus, but with the backlight setting (permanently) set.
Of course, this process can be used to configure your menus exactly how you want them however I don't know the keys for all the icons - only for those when I last dabbled in v5 - maybe if I can find some time I'll find the others (I haven't Google for them so perhaps these are now common knowledge) such as the MapShare functions that only came in v7.
The reason it the backlight worked as I wanted when installing the cab on my Prophet was because it still had my menu configs from v5 installed on it... d'oh!
I could be alone in wanting to be able to choose how the backlight is managed, but just in case there's someone with the same desire hopefully this'll be some use to you. It does of course beg the obvious question - why did TomTom remove this customisable feature?!
Cheers,
Mathew

youupy! drinks on you!
congrats and yes, i knew from the beginning that i can help you. dhaaaahh. lol!

Interesting, previous versions of tomtom allowed you to adjust the backlight settings within the application.
cant find it in TT7 though

KukurikU said:
doesn't bother the on\off of the screen while navigating in town (lots of instructions)? not sure i'll want all this flickering
Click to expand...
Click to collapse
On the contrary; they've handled it handle it very well.
Say you've got your backlight timeout set to 30 seconds then after this amount of time with no activity (direction instructions etc) it will turn the backlight off - you can still see the map outline in ambient light and, most importantly, can easily see the distance indicator to the next direction.
A few seconds prior to the next instruction the light will reilluminate, a few seconds later it will give the direction advice/distance etc and then once you're through the junction it will turn the light off again after 30 seconds.
Of course, when following a rapid series of instructions in, say, a built-up area then the backlight will stay on continuously - each instruction essentially resets the timer. It's only when out on the 'open road' with no isntructions for miles that you'd see the effect.
All said and done, when I've got access to external power I keep the backlight on constantly (that's where the 'Extinguish only when not charging' option comes in) but when I'm running on batteries I need all the power-saving I can get, not least given the limit battery capacity in the Diamond!
Rumpleforeskin said:
Interesting, previous versions of tomtom allowed you to adjust the backlight settings within the application.
cant find it in TT7 though
Click to expand...
Click to collapse
As mentioned they dropped the icon in v6 yet still supported the functionality internally - it's just that with no icon you can't change the setting hence the temporary icon-insertion method discussed above.
Mathew

[Q] problem with brightness

Hello! I have strange problems with backlight
1) back light is turned off -- i can't see anything on the screen with the day light. Changing the brightness in Settings/Display don't help.
2) but, after power off+power on, backlight is OK for 10 seconds, and turns off right after that.
I find the guy with the same problem,but on droid 2 -- youtube.com/watch?v=RxHqN_lycG8
Btw, in "AP Fastboot" mode ("M" key+PowerOn), backlight is don't turn of.
I try some ROMs, they all don't work for me. Only "kexec CM10" ROM have one difference: if I turn the phone off and on, the backlight is turning on for the 1/2 of second, I can see the lock screen, and after that it is turned off...
What can it be? How can I fix it? Any ideas will be very appreciated! I very like my Droid3,and want it back

al.zatv said:
Hello! I have strange problems with backlight
1) back light is turned off -- i can't see anything on the screen with the day light. Changing the brightness in Settings/Display don't help.
2) but, after power off+power on, backlight is OK for 10 seconds, and turns off right after that.
I find the guy with the same problem,but on droid 2 -- youtube.com/watch?v=RxHqN_lycG8
Btw, in "AP Fastboot" mode ("M" key+PowerOn), backlight is don't turn of.
I try some ROMs, they all don't work for me. Only "kexec CM10" ROM have one difference: if I turn the phone off and on, the backlight is turning on for the 1/2 of second, I can see the lock screen, and after that it is turned off...
What can it be? How can I fix it? Any ideas will be very appreciated! I very like my Droid3,and want it back
Click to expand...
Click to collapse
You'll have to try to turn the brightness up manually. It may be a broken light sensor. If you get in the right light you might be able to see the background and be able to turn it up.

MrObvious said:
You'll have to try to turn the brightness up manually. It may be a broken light sensor. If you get in the right light you might be able to see the background and be able to turn it up.
Click to expand...
Click to collapse
In the dark room, I can see everything on the screen. Unfortunately, brightness in Settings/display does not affect the backlight on my device.
I set the brightness to the maximum, but it still too dark

Is it possible that the problem is in flexible cable?

Dim brightness + Mic sensibility + other infos

Hi there!
I am a new user, and I've got some questions:
1) Is there any way to change dimmed mode brightness live from the watch?
2) Is it normal that alarms don't work during Theater mode?
3) Is there any way to reduce microphone sensibility? I find it pretty unusable when in my car because of the ambient noise (it just keeps listening as there are other sounds)
Thank you very much in advance!

Hi, let's se what i can help u with
1) From the watch you can download the swapps true dark or something like that which is a kind of screen filter reducing the brightness on both dimmed and live mode.
2)yeah, that's how its supposed to work
3) mmmh same thing here, since we use it on the wrist which normally is used to drive the car xD idk of anything to reduce the sensibility, hope someone here comes out with a solution

alahkel said:
Hi, let's se what i can help u with
1) From the watch you can download the swapps true dark or something like that which is a kind of screen filter reducing the brightness on both dimmed and live mode.
2)yeah, that's how its supposed to work
3) mmmh same thing here, since we use it on the wrist which normally is used to drive the car xD idk of anything to reduce the sensibility, hope someone here comes out with a solution
Click to expand...
Click to collapse
Thank you very much!
1) I've found the app, it works, but still have to figure out HOW does it work :silly:
I don't understand what the light bulb stands for and why it becomes full or empty when I choose the settings (I suppose that the bulb "on" means the higher lvl of brightness, bulb "off" the lower one, but can't really understand how to set this properly - but it works somehow, so this doesn't matter too much)
2) Ok
3) I think this is something kernel/rom related, some value to change, like the vibration one (by the way I MUST apply the vibration mod, because I don't wake up with the normal intensity)
Thank you again for your help!

wanzer said:
Thank you very much!
1) I've found the app, it works, but still have to figure out HOW does it work :silly:
I don't understand what the light bulb stands for and why it becomes full or empty when I choose the settings (I suppose that the bulb "on" means the higher lvl of brightness, bulb "off" the lower one, but can't really understand how to set this properly - but it works somehow, so this doesn't matter too much)
2) Ok
3) I think this is something kernel/rom related, some value to change, like the vibration one (by the way I MUST apply the vibration mod, because I don't wake up with the normal intensity)
Thank you again for your help!
Click to expand...
Click to collapse
You're welcome!
In swapps the bulb should work the exact opposite way you guessed xD i mean full bulb means the "dark mod" is on so you should see the screen darker (select the intensity of this "dark filter" below on the grey-scale thingy, on watch app). When you tap on the bulb it becomes empty and the filter is deactivated so your screen turns back into default brightness.

T713, LinageOS 14.1: Adaptive brightness not working

Edit: I didn't search hard enough earlier on, this issue is known and unlikely to be fixed, see the following post and the dev's reply in the following posts: https://forum.xda-developers.com/showpost.php?p=70838767&postcount=41
Adaptive brightness doesn't adjust the brightness but uses something in the middle (tested by blocking the light sensor / holding a flashlight over it). Changing the brightness slider (which is an offset from the calculated/measured brightness, yes?) has no effect either. Hardware is okay, it used to work with stock ROM. I'd be grateful for any infos or tips on how to debug this or what to try to fix this.

Pixel 4: deactivate the proximity sensor

Hello!
Is it possible to deactivate the proximity sensor? I know that ALL sensors can be deactivated in the quick setting panel, but I want just the proximity sensor to be deactivated, so the "always-on-screen", showing a clock and incoming messages, does also stay on when I put the phone into a transparent rain cover on my bike. Right now I need to push the on-button to be able to see the clock or other information, and that is something I'd rather avoid while riding.
Does anyone know a solution for this? An app or a patch maybe?
Nearly forgot to mention: the phone is running on LOS 18.1.

If you have root it's posible to do everything, though I am not sure how to help you...
What I know is that you will propably have to edit some tables on the system, maybe the system table. There is an app from the playstore that you can downlaod that allows you to modify some system tables(like global tables as well). Maybe if you play with that you may be able to deactivate the proximity sensor. The app is called SetEdit.
Hope this helps you, and in case it did, and you downlaod the app, could you please tell me if it is posible to modify the android properties table?
thx!

Thanks for your reply!
I should have been more precise when expressing my wish: I meant to switch the proximity sensor off while system is running and switch it back on later. The app that you pointed me to, reads as if the sensor will be deactivated at boot time and stay off until I reverse the change to the table and reboot again.
Basically, what I need, is an app that can switch the sensor off and on again without the need for rebooting in between, or an option in the system settings, that can be set within a profile: switching to profile A, which has proximity sensor on, switching to profile B, which has the sensor turned off, while all other sensors stay unchanged, would be a very good solution.
I don't know it that would be possible at all. On the other hand, there are "tasker apps", which can do "X if Y happens" or something like that. If such an app could "turn proxi sensor off when profile B is activated", that would also be a solution to my problem.
Do you know of any such app?

Oh. Yeah, that seems to be a very specific usage, and I don't believe you will find an app to disable the proximity sensor. Maybe you can develop that, it shouldn't be very hard, especially if you already have some knowledge of android development.
Good luck!

To my opinion the screen's on/off status should not always be determined by the proximity sensor, but by surrounding brightness instead, because the way it is now, you can not put the phone into a transparent cover, without the screen being switched off.
I agree that only a very few people will use transparent covers, and that the proximity sensor does have its advantages when holding the phone to your ear, but I also can imagine more situations where the screen wil be turned off by accident, when it rather should be kept on.
So, an option like
Code:
Use proximity sensor to turn off screen [ ]
Use light sensor to turn off screen [ ]
inside a system profile would be a great thing!