Rebooted phone several times, restarted FitBit app several times, finally tried rebooting the FitBit itself (hold down button for several seconds while plugged in) which seems to finally work.
Symptom: FitBit no longer synced with phone. Thought maybe I had to re-pair the device, I removed the device. When re-pairing, I continually received the error "Bluetooth issues" "if you see this message for the first time..." Occasionally, I was able to get the app to show "We found your Charge HR" but would still popup the Bluetooth issues error box.
Solution: Called tech support, explained the situation, and they were able to cover a replacement under the warranty. Which was really nice since I didn't think there was warranty. The experience was positive although I really wanted to know what was wrong with my current one.
So far, I am not exactly sure what the fix is as I cannot replicate the issue. It appears restarting the Fitbit fixes this problem. But may also include restarting phone and app. Restarting app fixed the problem of pairing as it appears to only work on the initial attempt. If I retry then the FitBit appears to no longer attempt to pair even though it says it is searching. The FitBit is definitely in some sort of off-mode during this time as the steps are not registered either. That is about all the information I think is relevant.
Showing posts with label troubleshooting. Show all posts
Showing posts with label troubleshooting. Show all posts
Tuesday, April 11, 2017
Thursday, November 6, 2014
Buggish: Disappearing Scroll Bar on MSN site on IE11
While testing Hebrew on different browsers, I clicked on an interesting news article on Internet Explorer which defaulted to MSN. While reading the article, I kept failing to scroll down the page. This is when I realized that as I read the article, the vertical scroll bar disappears (reappearing after moving the mouse around).
I assume this is by design because other pages on IE does not have this problem. Nor is MSN a problem on Chrome or FF. Sure I could use the scroll wheel on a mouse or the arrows on the keyboard, but unfortunately I happen to want to use the touchpad tap because double finger slide is not very fluid on this laptop nor the tiny up/down cursor buttons. I guess this is kind of a rant on my laptops keyboard and touchpad designs too. At least keep the arrows there... or even better let the functions exist even if the scroll bar is not visible.
I assume this is by design because other pages on IE does not have this problem. Nor is MSN a problem on Chrome or FF. Sure I could use the scroll wheel on a mouse or the arrows on the keyboard, but unfortunately I happen to want to use the touchpad tap because double finger slide is not very fluid on this laptop nor the tiny up/down cursor buttons. I guess this is kind of a rant on my laptops keyboard and touchpad designs too. At least keep the arrows there... or even better let the functions exist even if the scroll bar is not visible.
Monday, September 1, 2014
Review: ChromeCast (2 month impression)
I still enjoy Google's ChromeCast. I use it primarily to stream to my TV from a PC browser. The ChromeCast device is very simple to move it from one TV to another within the same network. I am not sure if there is more setup if the network is changed. A friend was even able to broadcast from his Samsung tablet.
I have figured out one of the problems with the lag with ChromeCast (as noted in a previous post). After a few hours of use, the stick becomes really hot. I think this has an impact on its performance. To test this hypothesis, I turned off the streaming for a few minutes. This resolves all lag issues for a while. If I streamed immediately after turning the stream off, the lag still persists. Over a few days, I have also tried with cooler and warmer environments (primarily me having the A/C on or off). Performance seems to degrade faster when it is off where the room is noticeably warmer (probably around low 80s). Performance seems to last longer when in low 70s. My guess is that the temperature has an impact on the rendering of the video. The device becomes pretty hot to the touch but not burning (at least for an adult).
I have figured out one of the problems with the lag with ChromeCast (as noted in a previous post). After a few hours of use, the stick becomes really hot. I think this has an impact on its performance. To test this hypothesis, I turned off the streaming for a few minutes. This resolves all lag issues for a while. If I streamed immediately after turning the stream off, the lag still persists. Over a few days, I have also tried with cooler and warmer environments (primarily me having the A/C on or off). Performance seems to degrade faster when it is off where the room is noticeably warmer (probably around low 80s). Performance seems to last longer when in low 70s. My guess is that the temperature has an impact on the rendering of the video. The device becomes pretty hot to the touch but not burning (at least for an adult).
Reference
http://douglastclee.blogspot.com/2014/07/review-chromecast-first-impression.html
Labels:
Google Chromecast,
review,
troubleshooting,
workaround
Monday, July 22, 2013
Coding: JavaScript - Single Var vs Multi Var
I came across an article discussing Single-Var vs Multi-Var declaration for JavaScript. I am almost always for multi-var pattern from experience.
Programming from scratch, I do not particularly care for one pattern over the other. Some argue one looks better than the other. That is a personal preference. Single-Var promoters say it saves space, but most people tab it to the same level as the other variable names which defeats the space saving (unless you compress the file, then maybe there is an argument there). Even then, space is so irrelevant today because either the program is so large that the difference is insignificant or so small that systems today are so advanced that no one will even notice the minuscule delay.
Having to deal with troubleshooting, debugging, and reading through thousands of spaghetti-code, multi-var has so many more advantages. You cannot assume process when debugging or troubleshooting because if you are troubleshooting an issue, you are looking for a problem. On the same note, you cannot assume strict is being used. Also, developers may easily assume others can pick up the code easily or be aware of certain standards but not everyone is like that. You also do not know how many people the code has gone through or even how many companies.
There have been plenty of codes that I had to debug due to a variable not declared properly or even just misspelled. There was a code I had troubleshot because someone used an I instead of l or maybe it was a 1. Who is going to notice an upper-case 'i' to an lower-case 'l' to the number 1 when skimming through hundreds of lines of code?
Another use of declaring multiple vars is also to find where the variables are declared. Sure you can have IDE. But if you find yourself having to troubleshoot in unfamiliar environments, this makes a world of a difference to navigating through code with a simple text editor with a word find (or find word within a library of files). Even if comma-first, you then have to search for both comma-first and with var (in-case it is the first variable in the list or a parameter to a method/function or a different variable on a different block level [scope]).
For any advanced debuggers (I assume advanced developers), the cosmetics of tabs, alignments, etc., is barely a nuisance. At some point, I can read both styles easily without complications even if they were multi-line or single-line or case-insensitive.
So if there was an opinion to be made on this topic, it should be the people who are going to maintain the code after deployment. Developers have a project plan. Troubleshooters are expected to fix the problem yesterday. Time is more valuable to them than developers. No matter how experienced developers are or how mature the procedure may be, errors are human-nature.
Ultimately, either is acceptable. To me single-var would be like the developers leaving the power button in the back of the computer. You don't have to see the button and closer to the power supply which means no extra wires in the case. When was the last time you seen that design (the design did exist for those of you too young to have seen them)?
Ben Alman - http://benalman.com/news/2012/05/multiple-var-statements-javascript/
Dan Hough - http://danielhough.co.uk/blog/single-var-pattern-rant/
Programming from scratch, I do not particularly care for one pattern over the other. Some argue one looks better than the other. That is a personal preference. Single-Var promoters say it saves space, but most people tab it to the same level as the other variable names which defeats the space saving (unless you compress the file, then maybe there is an argument there). Even then, space is so irrelevant today because either the program is so large that the difference is insignificant or so small that systems today are so advanced that no one will even notice the minuscule delay.
Having to deal with troubleshooting, debugging, and reading through thousands of spaghetti-code, multi-var has so many more advantages. You cannot assume process when debugging or troubleshooting because if you are troubleshooting an issue, you are looking for a problem. On the same note, you cannot assume strict is being used. Also, developers may easily assume others can pick up the code easily or be aware of certain standards but not everyone is like that. You also do not know how many people the code has gone through or even how many companies.
There have been plenty of codes that I had to debug due to a variable not declared properly or even just misspelled. There was a code I had troubleshot because someone used an I instead of l or maybe it was a 1. Who is going to notice an upper-case 'i' to an lower-case 'l' to the number 1 when skimming through hundreds of lines of code?
Another use of declaring multiple vars is also to find where the variables are declared. Sure you can have IDE. But if you find yourself having to troubleshoot in unfamiliar environments, this makes a world of a difference to navigating through code with a simple text editor with a word find (or find word within a library of files). Even if comma-first, you then have to search for both comma-first and with var (in-case it is the first variable in the list or a parameter to a method/function or a different variable on a different block level [scope]).
For any advanced debuggers (I assume advanced developers), the cosmetics of tabs, alignments, etc., is barely a nuisance. At some point, I can read both styles easily without complications even if they were multi-line or single-line or case-insensitive.
So if there was an opinion to be made on this topic, it should be the people who are going to maintain the code after deployment. Developers have a project plan. Troubleshooters are expected to fix the problem yesterday. Time is more valuable to them than developers. No matter how experienced developers are or how mature the procedure may be, errors are human-nature.
Ultimately, either is acceptable. To me single-var would be like the developers leaving the power button in the back of the computer. You don't have to see the button and closer to the power supply which means no extra wires in the case. When was the last time you seen that design (the design did exist for those of you too young to have seen them)?
Reference
Kent Dodds - https://plus.google.com/u/0/114245123507194646768/posts/dnRkxWyQ4fMBen Alman - http://benalman.com/news/2012/05/multiple-var-statements-javascript/
Dan Hough - http://danielhough.co.uk/blog/single-var-pattern-rant/
Updates
3/12/2014 - Added two more references which support multi-var patterns. Ben Alman does a good job describing work-arounds to the advantages of single var pattern. Dan Hough does a good job explaining preventing errors and simplifying rafactoring. I like the addition of the refactoring which also expands on code maintenance.
There were a couple posts on the use of 'use strict'. For someone maintaining code, you may not always have access to modify code. Also, there are times working in a corporate environment which you may not even be able to install your choice of IDE or add-ins. Using multi var pattern is much more helpful for programmers supporting old code. Especially with javascript where code can put interjected in out-of place areas or written by untrained programmers like web designers.
Labels:
coding,
debugging,
design patterns,
javascript,
opinion,
troubleshooting
Subscribe to:
Posts (Atom)