Problems after the last firmware update.
Re: Problems after the last firmware update.
(edited) Exasperated
Last edited by dogstar7 on Tue Jan 15, 2019 6:17 pm, edited 1 time in total.
Re: Problems after the last firmware update.
Not from anything that I have tested (and I've tried every possible iteration). There is absolutely no need to reinstall anything that has not changed.
Hubsan need to come clean on this and stop confusing people.
The issues people have had are because they have either not completed the camera update correctly, it was corrupted, they have left the firmware on the card, the card is incorrectly formatted, the card has been removed from a device without dismounting ot cleanly, the speed test file is corrupt or missing, the FW is a lower version than already installed.
No doubt this will get deleted like the previous times I posted the same advice
Re: Problems after the last firmware update.
(edited) Exasperated
Last edited by dogstar7 on Tue Jan 15, 2019 6:17 pm, edited 1 time in total.
Re: Problems after the last firmware update.
Here's the problem.
People have been having issues with the wifi connection reliability.
Some can't connect, others connect and then disconnect.
A myth (IMHO) propagated by Hubsan themselves says:
"when you upgrade any firmware, you must upgrade all of it together"
When asked what exactly that means you get no response.
When asked why you should do that, you get no response.
When asked what order you do the update in, you get no response.
Let's look at it logically.
I have 3 bits of firmware called Apple, Banana and Cherry.
Hubsan replace Cherry with Damson.
So I install Damson and the quad breaks.
So I install Damson, Apple and Banana. Does it now work? That's the advice I'm given to fix it.
What happens if I install Banana, Damson and Apple, in that order? Will that fix the issue too?
What if I leave out Apple?
If I have code which I'm replacing with identical code, how the heck does anything change?
It's like redecorating a room because you have water damage.
You get a new grey carpet, pink walls, white ceiling.
A week later you ask the decorator to come back to change the carpet to green as the grey one seems to be discoloured.
"No problem" he says, "we'll have to repaint the ceiling white first and the walls pink".
"What? It's brand new, you only painted that last week" you exclaim.
"Yea mate, can't replace a carpet without a complete repaint job"
"Let's hope you don't get tired of the pink walls in a couple of days....."
Meanwhile the burst pipe under the floor is still leaking
Anyway,to prove the point, I rolled back all the zino firmware to earlier versions (too many times ).
I then reloaded it in every single possible combination of loads.
ABC
ACB
BAC
BCA
CAB
CBA
Guess what? I could not get the connection to fail.
If there was a dependency on how you load the firmware it would have shown up and it would be easy to replicate it at will.
Someone show me how to replicate the issues because I have drawn a blank.
Meanwhile, I can create a situation where I can get the quad to disconnect and connect exactly as other are seeing.
I could do it right this minute if someone asked. It has nothing whatsoever to do with loading firmware in any particular order or loading just one component. I guess if i asked for help to fix it, I'd be told to reload all the firmware again....
So let someone please replicate the "re-install everything or it breaks" myth, and I'll back down and eat my words.
In the meantime, when new code comes along, I'll update what needs changing, and not code that hasn't....
Yes, people want answers, but the confusion is arising from exactly the advice that is being given and propagated widely IMHO.
Not identifying what the actual problem is, and not giving the correct, clear instructions to rectify it is where the problem is.
People have been having issues with the wifi connection reliability.
Some can't connect, others connect and then disconnect.
A myth (IMHO) propagated by Hubsan themselves says:
"when you upgrade any firmware, you must upgrade all of it together"
When asked what exactly that means you get no response.
When asked why you should do that, you get no response.
When asked what order you do the update in, you get no response.
Let's look at it logically.
I have 3 bits of firmware called Apple, Banana and Cherry.
Hubsan replace Cherry with Damson.
So I install Damson and the quad breaks.
So I install Damson, Apple and Banana. Does it now work? That's the advice I'm given to fix it.
What happens if I install Banana, Damson and Apple, in that order? Will that fix the issue too?
What if I leave out Apple?
If I have code which I'm replacing with identical code, how the heck does anything change?
It's like redecorating a room because you have water damage.
You get a new grey carpet, pink walls, white ceiling.
A week later you ask the decorator to come back to change the carpet to green as the grey one seems to be discoloured.
"No problem" he says, "we'll have to repaint the ceiling white first and the walls pink".
"What? It's brand new, you only painted that last week" you exclaim.
"Yea mate, can't replace a carpet without a complete repaint job"
"Let's hope you don't get tired of the pink walls in a couple of days....."
Meanwhile the burst pipe under the floor is still leaking
Anyway,to prove the point, I rolled back all the zino firmware to earlier versions (too many times
).I then reloaded it in every single possible combination of loads.
ABC
ACB
BAC
BCA
CAB
CBA
Guess what? I could not get the connection to fail.
If there was a dependency on how you load the firmware it would have shown up and it would be easy to replicate it at will.
Someone show me how to replicate the issues because I have drawn a blank.
Meanwhile, I can create a situation where I can get the quad to disconnect and connect exactly as other are seeing.
I could do it right this minute if someone asked. It has nothing whatsoever to do with loading firmware in any particular order or loading just one component. I guess if i asked for help to fix it, I'd be told to reload all the firmware again....
So let someone please replicate the "re-install everything or it breaks" myth, and I'll back down and eat my words.
In the meantime, when new code comes along, I'll update what needs changing, and not code that hasn't....
Yes, people want answers, but the confusion is arising from exactly the advice that is being given and propagated widely IMHO.
Not identifying what the actual problem is, and not giving the correct, clear instructions to rectify it is where the problem is.