Posts by tromo

I hope that most of the problems for A5 are solved. There could/should be 6.3 version soon.

It is **intentionally** disabled by default as it can slow down older boxes or with really big EPG, etc.

One can re enable this via:

MENU-->Setup-->System-->Keyboard/RC-->Button Setup

and change

History button mode to "Show Menu" from default setting (Show Menu with service name only)

Actually, today drivers already in 6.3 image for Zgemma H7. So far all fine, Kodi works :)

6.3 H7 Kodi ***could/should*** be ready next week. Still in testing phase. No need to test ti now as it fails. 6.2 is ok.

Strange, works fine in my case. Did you do backup of system settings from 6.2 and restore in 6.3 or a fresh start? Although, did never check mgcamd in 6.3... then again, oscamemu **should be** more than ok.

Great, thx on feedback!

I'm pretty sure that a reflash is needed

I think (ok well, hope) that today's build of pure2 for A5 works a bit better. At least in a rather limited time I had to test it.

I'm really not an mgcamd expert and I'm the wrong person to answer your question, but some say that mgcamd works fine on pure2. Perhaps you could copy the bins and settings to atv ?

OK, that changes the whole concept a bit :) You could try with strace, and gdb using original source, but it won't be fun.

Uhh, ok, but can I ask why? There is source code :)

great news!

Sorry, a bit late with the answer :( If I recall correctly, flodder has a 512mb swap by default.

Ok, we'll do it in a blind mode against the common sense :) But that box, however wonderful at the time.... mah... :)

Frankly, at this moment, there is no sense to push for a 6.3 800se/500hd build. Sometimes, especially for older boxes, a bigger number does not equal more joy.
For those who do not like 'flodder' as suggested after fresh install, i.e. might prefer openmultiboot or whatver, please use --> enigma2-plugin-systemplugins-swapmanager2.
Then again, the last time I have checked, it was not really needed even for more demanding plugins like yify, olm, lookseries, etc. But, it cannot hurt, especially on a reasonably fast USB stick or eSATA stuff (a bit exotic in a case of the original 500HD).

OK, 4kse model was a limited edition, very few units were made (perhaps less than 100, but I might be wrong). Trouble is that we do not have the box anymore (it was on a loan). Anyway(z), Kinda sad,as it was perhaps HW wise the most powerful box ever (except a bit later Dinobot Mini, which used the same SoC).
There were two Pure2 images, one was for mSD card, the other was internal flash.
If there is a rational interest, I guess we can build these images again.

I do use sf8008 daily on pure2 and wpa2 and cannot find such problems. Usual suspects are AES vs TKIP settings (router/AP vs client/box).

These are probably the best boxes around at the moment (HW/SW/drivers).

Well, any usals motor works just fine, for older ones (goto, rod extenders, jaeger etc) I'm also pretty sure they work ok. So... a bit strange report

That is really strange, as I did have dm9x0 and it worked fine with motor, and all the other boxes work ok with motor.
Are you using USALS or goto protocol? Frankly did not use 'goto' for a long time, so a bit off with any advice about that.