Blue bg green font
deanoblock opened this issue · 8 comments
Version: 0.1
Environment:
Galaxy S4 SGH-I337
CM11 ROM
TWRP
Description:
Installed Hall Monitor and enabled Root access function + notifications.
Within a day the S-view when closed went from being the standard black bg white font to a bright blue bg with green font (hard to read for color blind).
Only way to resolve issue was to uninstall apk and reinstall.
I've seen a similar issue, where the widget settings seen to be lost when the phone restarts. Do you know if your phone was restarted?
I am surprised that you weren't able to change the settings back without reinstalling. I assume you tried simply going to the settings page and selecting other colors? Thinking about it as I write, I'm wondering if those settings might not be applied until the service is restarted. I'll look at the code in a minute.
Anyway, in a day or two my laptop will come back from Apple with a working battery and hopefully I'll be able to fix this then.
Nope (to what I was thinking about), looks like the background/foreground color settings are read every time the overlay comes up. So getting "stuck" on the defaults is definitely a bug. I will look into it but let me know if it happens again, I could have you do a diagnostic maybe.
Hey, on CM11 the settings page does not open so maybe thats why I couldn't
reset manually...
I have no problem debugging it for you, do you want logcat or anything
specific?
On Tue, Feb 4, 2014 at 10:13 PM, Alex Burka notifications@github.comwrote:
Nope (to what I was thinking about), looks like the background/foreground
color settings are read every time the overlay comes up. So getting "stuck"
on the defaults is definitely a bug. I will look into it but let me know if
it happens again, I could have you do a diagnostic maybe.Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-34133995
.
Wait, you can't get to the settings? That's certainly a problem. It's working for me on CM11 so far. If you can get a logcat of the settings trying to open (launch HM from the home screen/app drawer, make sure it's enabled, then tap on the word Enable (not the on/off switch) and see if the general settings come up), I'd love to see that!
When I follow the above steps, from the word Enable. Settings opened but on the 3rd try.
Here is a logcat of opening HM and going to menu and clicking Settings.
Result: settings does not appear
logcat: http://s000.tinyupload.com/?file_id=07494414114334564549
anything else I can do?
@DeanoB: press about preference until overlay "debug enabled now" appears (7 times).
repeat your test and post the new logcat. disable debug again.
Also, the "Settings" in the menu doesn't do anything and shouldn't be
there. We'll fix that. The settings are hierarchical and when the switches
on the main screen are set to On, you can click through them to the
sub-pref-screens. This may need to be made more obvious.
On Fri, Feb 7, 2014 at 11:34 AM, habeIchVergessen
notifications@github.comwrote:
@DeanoB https://github.com/deanob: press about preference until overlay
"debug enabled now" appears (7 times).repeat your test and post the new logcat. disable debug again.
Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-34463569
.
Agreed settings menu should be more user intuitive.
On Feb 7, 2014 11:37 AM, "Alex Burka" notifications@github.com wrote:
Also, the "Settings" in the menu doesn't do anything and shouldn't be
there. We'll fix that. The settings are hierarchical and when the switches
on the main screen are set to On, you can click through them to the
sub-pref-screens. This may need to be made more obvious.On Fri, Feb 7, 2014 at 11:34 AM, habeIchVergessen
notifications@github.comwrote:@DeanoB https://github.com/deanob: press about preference until
overlay
"debug enabled now" appears (7 times).repeat your test and post the new logcat. disable debug again.
Reply to this email directly or view it on GitHub<
https://github.com/durka/HallMonitor/issues/32#issuecomment-34463569>
.Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-34465521
.