OLD - USE NEW POST - MK808b FAQ's, includes 1080p

[ididmytime]

This fix doesn't work for me. Infact, it doesn't seem to do anything at all. Is anyone able to shed some light on this as I'd really like to get my ethernet to connect on boot.

I have an MK809II with Finless 1.7a 1080p ROM.

Thanks

Try this one and do the following. This should work.

1) Extract the .zip and place the ethernet.sh into the root of the sdcard.
2) Download Script Manager from Google Play store.
3) Reboot the device with ethernet connected.
4) You shouldn't have an internet connection, load up Script Manager and select the ethernet.sh, choose the SU (skull and crossbones) and press RUN.

If you get a connection afterwards then it works with your device. Keep SU selected and choose BOOT as well, go into advanced settings and there is a setting to disable notification/silent boot.

Then from now on, you will get a connection within 5-10seconds after boot, let me know how you get on with it.

ididmytime, I followed this guide completely through and through... great work as it is a great one stop shop for newbie resources.

I was able to get a stream from my PC to run great with few dropped frames on 1080p through MX Player, however when I use XAF, the stream is considerably choppier. I was using XAF Neon for set top. Have you seen this before?

I loaded MX prior to installing XAF, so I'm assuming its using MX to play the content?

Can't say I have since I don't use external players, however, if you go to the forum, there are many configs to use other players, like Archos and Wondershareplayer ect... you may have better luck with one of those. It also might be worth downloading the armv7 codec pack on Google Play, and making sure it's running in HW mode.

I would say it could be your Wifi isn't fast enough, but if it works ok using another I doubt it's that.

[snipez]

Can't say I have since I don't use external players, however, if you go to the forum, there are many configs to use other players, like Archos and Wondershareplayer ect... you may have better luck with one of those. It also might be worth downloading the armv7 codec pack on Google Play, and making sure it's running in HW mode.

I would say it could be your Wifi isn't fast enough, but if it works ok using another I doubt it's that.

thanks for quick reply - how do you ensure its running in HW mode - from the instructions for MX it states to make sure all HW / SW decoding is off

[ididmytime]

thanks for quick reply - how do you ensure its running in HW mode - from the instructions for MX it states to make sure all HW / SW decoding is off

When running the video it will say HW at the top right hand corner, it's important that it says this. If you have MX running relatively well on it's own I'm sure after some fiddling you will have it up and running no problem. If not I have used the Archos player in XBMC as that supports more streaming services, and that worked pretty well.

You can configure XBMC to be able to select a whole host of video players before you run it, may take some time before you find one right for you, but most of us have spent hours to get our devices to the way they are now.

[big10p]

Try this one and do the following. This should work.

1) Extract the .zip and place the ethernet.sh into the root of the sdcard.
2) Download Script Manager from Google Play store.
3) Reboot the device with ethernet connected.
4) You shouldn't have an internet connection, load up Script Manager and select the ethernet.sh, choose the SU (skull and crossbones) and press RUN.

If you get a connection afterwards then it works with your device. Keep SU selected and choose BOOT as well, go into advanced settings and there is a setting to disable notification/silent boot.

Then from now on, you will get a connection within 5-10seconds after boot, let me know how you get on with it.

Unfortunately, nothing happens when I run the script in Script Manager.

Thanks for trying to help out, though.

[ididmytime]

Unfortunately, nothing happens when I run the script in Script Manager.

Thanks for trying to help out, though.

Last resort is to execute it via root browser lite to see if it gives an error. Also adding .sh to the original fix to see if that works (it will take 45seconds, but can be adjusted if working).

It should just come up null. If any errors come up let me know and I can make up a few test scripts if you're willing.

I believe all finless roms are based on the stock rom the device came with, so your 1.7 will be different to mine, so the commands may not be supported, or need adjusting.

[ididmytime]

I really, really, don't get why the ethernet fix is not working for people.

It clearly is working for me, if any evidence is needed this proves it (shaky cam ahoy).

Maybe we need someone else who is actually good at this kinda stuff to have input.

Edit:

To the two people that this script isn't working for.

The original commands for the fix was from someone using an mk808b, the same device I am using, with the 2dark4u overclocked kernel. I am also using the OTG port.

Considering one of you are using the same rom as I am, surely the commands would work.

The only thing I can think of, is perhaps your usb lan is being called something else rather than eth0. If that's the case then all it would take is a simple edit and you're up and running with the ethernet on boot.

Since 2.2.3, the rom comes with a terminal emulator app. If you dont have it download this one. Load it up once you have an ethernet internet connection and type netcfg.

Find the device with an IP and let me know what it's called. If it is eth0 then I have absolutely no idea, and it may be kernel related.

[snipez]

When running the video it will say HW at the top right hand corner, it's important that it says this. If you have MX running relatively well on it's own I'm sure after some fiddling you will have it up and running no problem. If not I have used the Archos player in XBMC as that supports more streaming services, and that worked pretty well.

You can configure XBMC to be able to select a whole host of video players before you run it, may take some time before you find one right for you, but most of us have spent hours to get our devices to the way they are now.

When I run it in MX Player it def has the H/W on top -- if i click it, itll have options that include H/W+ and S/W... I left it as is... but assume the others dont matter.

When running in XBMC, I don't see a H/W on top, if that was what you were referring to... Is there something we do in XBMC to direct it to that?

Anyways thanks for your help..!

Also, for those of you who may be a few steps behind me... the codec that @ididmytime was referring to makes a huge difference, and I missed it the first few times I tried to fiddle.

[snipez]

When I run it in MX Player it def has the H/W on top -- if i click it, itll have options that include H/W+ and S/W... I left it as is... but assume the others dont matter.

When running in XBMC, I don't see a H/W on top, if that was what you were referring to... Is there something we do in XBMC to direct it to that?

Anyways thanks for your help..!

Also, for those of you who may be a few steps behind me... the codec that @ididmytime was referring to makes a huge difference, and I missed it the first few times I tried to fiddle.

edit: problem solved! THANK YOU ALL!

[big10p]

Last resort is to execute it via root browser lite to see if it gives an error. Also adding .sh to the original fix to see if that works (it will take 45seconds, but can be adjusted if working).

It should just come up null. If any errors come up let me know and I can make up a few test scripts if you're willing.

I believe all finless roms are based on the stock rom the device came with, so your 1.7 will be different to mine, so the commands may not be supported, or need adjusting.

I ran both scripts in Root Browser and they executed without error, but ethernet was not switched on, still.

I actually have the Imito MX1/MX2 1.7a ROM installed on my MK809II. Ethernet wouldn't switch on at boot even with the stock ROM. My MK809II is actually a replacement for one I had to return as faulty and has a different circuit board (relocated reset button etc.). The one I returned actually did boot with ethernet (on stock ROM), without having to run any scripts, or anything.

I can confirm my ethernet connection is called eth0.

Bit of a head scratcher this one, eh.

[nipper]

My stick doesn't seem to be affected by this lan issue, the connection is ready to go as soon as the stick is booted. The only thing I have done is setup a static IP address in ethernet settings.

[big10p]

My stick doesn't seem to be affected by this lan issue, the connection is ready to go as soon as the stick is booted. The only thing I have done is setup a static IP address in ethernet settings.

I'm also using a static IP. I've also tried using a dynamic IP but it didn't make a difference.

[Horrorzilla]

My stick doesn't seem to be affected by this lan issue, the connection is ready to go as soon as the stick is booted. The only thing I have done is setup a static IP address in ethernet settings.

Mine did as well until Lewy's 2.2.3 but it runs so smooth and fluid I can live with disabling/enabling it on start up.

[big10p]

I've found a semi-fix for this:

I created a Root Toolbox shortcut on my home screen that runs the commands 'ifconfig eth0 down' and 'ifconfig eth0 up', so I just have to click on it after boot, instead of going into settings to do it.

[Horrorzilla]

I've found a semi-fix for this:

I created a Root Toolbox shortcut on my home screen that runs the commands 'ifconfig eth0 down' and 'ifconfig eth0 up', so I just have to click on it after boot, instead of going into settings to do it.

Never thought of that - thanks for the tip.

[ididmytime]

I've found a semi-fix for this:

I created a Root Toolbox shortcut on my home screen that runs the commands 'ifconfig eth0 down' and 'ifconfig eth0 up', so I just have to click on it after boot, instead of going into settings to do it.

That is the exact command the script uses... it runs ifconfig eth0 down, then it will run ifconfig eth0 up afterwards, using it with script manager, or delaying it by boot, means no toggle is needed.

Maybe some devices need a delay between the off and on?

I have two test scripts this one and this one, see if one of those work, they both have a 7 second delay between off and on. If the commands work, and you can get it to work by manually inputting the commands, then surely it's just a matter of figuring out why it's not working via a script.

This has to work... right?

My stick doesn't seem to be affected by this lan issue, the connection is ready to go as soon as the stick is booted. The only thing I have done is setup a static IP address in ethernet settings.

It's fixed on 4.2.2 roms, however because they are so slow hardly anyone uses them.