Could you please answer the question I asked you in post 71 so that we can get your receiver running again?
Thank you
AZBOX AzBox miniMe American edition version 2.00 beta firmware
- Thread starter pwrsurge
- Start date
- Latest activity Latest activity:
- Replies 97
- Views 10K
Could you please answer the question I asked you in post 71 so that we can get your receiver running again?
Thank you
I went out to dinner last night, and then went to bed. Yes, i can ping it, and i verified that it was the AZbox as i then unplugged the RJ45 and then it wouldnt respond to ping.
Please stop making unfounded statements like this. As you are not an embedded software engineer involved in AzBox firmware development, you have NO idea what issues are at hand. Unlike the AzBox Me, the European recovery interfaces that came with the miniMe are severely flawed as they simply got copied from the Me and were never properly tested by OpenSat on the miniMe.
From what I remember, the main issue was that the recovery interface only worked if an Ethernet cable was plugged in and the receiver was able to acquire an IP address via DHCP from a router. Unfortunately, these issues can't be fixed as that specific code is burned on a read only flash chip which can't be updated. Considering the fact that many of our North American users don't even have their receiver connected to the Internet, this was a showstopper for us so we had no choice but to design our own recovery system from scratch before being able to release the AzBox miniMe American Edition.
Thank you for your understanding
What unfounded statement I'm I making? The interface as you describe with an Ethernet cable connected works perfectly in my other Minime's I have 4 of them, so what is the issue of anybody that side of the pond plugging their box into a router just for a firmware flash? Why is it 'severley' flawed'? It does work. Infact, you might sell more boxes if this was the option to flash firmware as your American users could try out other firmware without the worry of having to send the box back for reflash in the boot 1 sector.
I may not be a software writer, I don't claim to be, but I have owned every AZBox that were available over here in Europe, and I can honestly say, none of the firmwares I have tested are 100% bug free, in fact out of all the receivers I own these are the worst in time spent rebooting them just to get them to work! and I have tested no end of firmwares. In all fairness to yourself, your American version is the best of them all for the MiniMe as regards for enthusiasts try to find feeds, in all the European software, the blind scan is appalling, except for Open ATV 3.0 which resides in My ME along with your North American AZtrino. I find the 3.3.1 Kernel the best for enthusiasts like myself who use blindscan.
Any way that aside Is my box totally bricked? If so, I might as well hit the recovery button on the back and get it working with Open ATV 3.0, unless you have the answer?
You answered the above in your other post.
Last edited:
Good news! We were already able to replicate and resolve the above issue so this fix will be included in the next firmware update. Now working on adding proper error validation for USALS latitude and longitude parameters.
I am pretty much feeling the same. There is a 30-day return policy and that time has about run out, so I too am going to have to return mine as well. I am having troubles getting the dealer to work with me on this, let alone even reply to emails so will see how this goes as well. This has not been a fun experience at all. I also agree with perhaps re-purchasing if and when the kinks get worked out. . My old X2 Premium HD blind scans in 1/2 to 1/4 of the time of most others and has been far more stable than the AzBox miniMe. With all sincerity, I wish everyone involved with this project the very best of success. I just do not have the luxury of time to wait for any further updates.
You are so lucky that you were not aware because the update was actually worse for me. I can't watch NBC West (103W) anymore after the upgrade for some reason after watching it for a few minutes the picture has motion breaks. The signal is rock solid as always (90%). On the NBC East (103W) the picture does the same thing after the receiver is on that channel for awhile. Never had any issues before the upgrade and now I have to wait to see if they will release a firmware so I can downgrade to the 1.86 version. I've cut down my FTA watching because of this feed issue. I bought a Seagate 1TB storage device and it won't recognize it. it did before, it just couldn't write to it. The movie folders are there but it just can't see it.
It's already too late to return the unit back for me for I am stuck with it. If any other FTAers read this thread, please do yourself a favour and look to other receivers like the MicroHD. I traded it in for the AZbox Minime 4:2:2 and it is not worth the trouble. Come the new year I have to suck up the lost and buy a 2nd receiver as a back up.
I did exactly what you did and NOT ONE official VEVO video was found during the search. All videos were of PRIVATE channels posted of people with their own variation of a song and making a video. Give me the exact search you entered and I will post what my findings were and if they were the same.
I get motion break ups with mainly 103w NBC West feed, which is the strongest transponder on NBC MUX. I don't have audio issues, but video issues. Amazing how this just happened right after the upgrade to 2.0. It looks like the box is having problems with processing the picture. This is very disappointing especially for the holidays. I can't time shift programs from the WEST feed anymore. Now I have to rely on the MOUNTAIN feed, which is an hour later for some programs.
Whoops, spoke too. Audio is breaking up on Mountain feed. :-(
It may have been tested at your end, but you can see that people have issues with the box being recognized. I could browse with 1.86, but when I pressed record the box would freeze and required reboot. Unless, you tested it with a storage drive that is less than 1TB. But, I'm sure that AZbox would have made that apparent to the public with documentation included in the packaging that you should not use 1TB or more storage.
P.S. It would have been a good thing to have a step down version ready in case people have issues with this firmware instead of having to wait for another release to go backwards. At least we could have enjoyed the holidays with what we were used to.
Is this with version 2.01 as well? A few parameters in the tuner module that were enabled for debugging purposes were disabled again in v2.01. This could be what's causing your performance issues with the NBC MUX on 103w.
I currently don't have access to the 103w NBC MUX as i'm home for the holidays and over here, I only have a C-band dish with a Ku LNBF not set for the 25 degree offset skew. However, I did check with the 105w NBC MUX and there are no video or audio playback issues under firmware version 2.01.
Please try upgrading to 2.01 for now and I will try to find a bit of time within the next day or so to release a KFL version of 1.86 so that you may downgrade if 2.01 still does not work out for you.
Had a chance to test this firmware on the Ku NBC MUX and was finally able to replicate the issue you are experiencing. Strangely, only the West feed seems to be impacted which explains why it was not noticed during regression testing.
Fortunately, the issue was not difficult to solve so the upcoming version 2.02 of the firmware which will be released momentarily fully resolves this issue.
Last edited:
Similar threads
