Megatron ROM for ENY EM8 and K200 T8 boxes

[Krankie]

sleep / wake

I tested sleep / wake function from android home screen ( megatron main launcher ) and repeated sleep / wake many times without any issues , did not try from within xbmc / kodi as I close down programmes before putting to sleep

[TMx]

Testing I carried out was on a m8 and was hard wired and I had no issues

Exactly ,Kernel has Wifi problem... Matricom guys also reported same issue sometime ago ...

Should work OK with LAN wired connection.

[pj8]

The browser button next to standby button on round original remote can be re-assigned to a second more resolute type of sleep/wake procedure I guess but it needs quite a bit of coding to make it work & cover all types of scenarios & events handling such as from inside big apps or busy states etc.

I hope a mod can make this thread a sticky.

[userofthenet]

Exactly ,Kernel has Wifi problem... Matricom guys also reported same issue sometime ago ...

Should work OK with LAN wired connection.

it seems like ported ROMs have this wifi issue. Justme ver 1.5 and up also have this issue. Also, mediaman rom's have this wifi wake up from sleep issue

[TMx]

it seems like ported ROMs have this wifi issue. Justme ver 1.5 and up also have this issue. Also, mediaman rom's have this wifi wake up from sleep issue

True Ported roms has wake up issue but this wifi issue is different story...

[warlock09]

So this megatron for M8 still has power on /off issues ..

[seymourtv]

I have had the pleasure of testing this ROM from conception to release and have been running on my T8 and M8. This ROM is awesome , many
thanks for sharing your work , give this ROM a try guys as you will love it

Thanks Krankie. Good to know someone has tried it.

[superfreak79]

I still have the Wake Up issue

I guess its related to Wifi connection , box wakes up ,works ,trying to establish a wifi connection for a while but no success = Reboot

True Ported roms has wake up issue but this wifi issue is different story...

Thanks a lot TMx for testing the ROM. Which box did you install the ROM on? Do you know the wifi chipset?

As I wrote in stane's thread, the Touch standBy app actually works most of the time as the box wakes up but it needs exiting xbmc to click it's icon to go to sleep.

Thanks pj8. It's good to have someone like you around. I wonder if the Touch standBy can be a good "solution" to the problem which appears to be kernel based. Can you post a link to the app? I'll consider updating the ROM to include it.

The browser button next to standby button on round original remote can be re-assigned to a second more resolute type of sleep/wake procedure I guess but it needs quite a bit of coding to make it work

Also a good idea. The scancode currently used for POWER WAKE is 116 - if someone wants to suggest a different scancode, I'm willing to try it out.

[TMx]

@Super

Tried your m8 rom on

M8N original V1 pcb, AP6330 wifi chip....

Thanks again for sharing

P.s we had the same wifi issue at the time stane released his rom so its not something new...

[okey]

installed on my m8, all works very well indeed, but when i press the red button on the remote, picture goes off, but blue light stays on.

any ideas

[Krankie]

installed on my m8, all works very well indeed, but when i press the red button on the remote, picture goes off, but blue light stays on.

any ideas

This happened to me initially but after using the app reboot the light then powered off the next time I put it to sleep

[pj8]

Hi Superfreak79,

Couldn't install the ROM, message said something like:
This ROM is for K200 or ENY-EM8 boxes, your box is M8.

My box is an original 2GB OTT, before clones came out, and running stane's since release happily: NO bugs or crashes or hangs/freezes ever, though overloaded with 400+ heavy widgets/apps, nor ether/wifi/BT problems ever, unlike other ROMs.

I tested over 20 standby apps, the one linked below was the only one that works almost always and wakes up. Also unlike most when you stick it on desktop it's not a widget like most standby apps and the remote arrow keys can actually select & run it, not skip over as most desktop widgets:

https://play.google.com/store/apps/details?id=com.alinberce.standbytouch

I don't code Android SDK but if you can assign a remote key to run it then it will be great, don't know if an app can be triggered by a scancode.

Good luck and thanks.

[superfreak79]

Tried your m8 rom on M8N original V1 pcb, AP6330 wifi chip....

P.s we had the same wifi issue at the time stane released his rom so its not something new...

Thanks. I spoke with Stane and he said the following:

"I've never had M8N personally - but know there are small hardware differences between M8 and M8N. Also the bootloader on M8N is different as it has some SecureOS features. Ultimately, I don't know what the reason is for WiFi performing that way. Amlogic is using a very old broadcom driver which is filled with their crap and causes all kind of instabilities. It's not unlike the situation with RTL 8188EU/ETV and RTL 8192CU chips."

That's a far better answer than I could've given . In summary, I think it's safe to say the ROM will behave differently for M8* variances. The solution many not be quick or simple. Sorry guys...

[superfreak79]

Couldn't install the ROM, message said something like:
This ROM is for K200 or ENY-EM8 boxes, your box is M8.

Can you write down what you see word for word? As mentioned in the OP, only "eny_em8" and "k200" devices are currently supported - but it seems I might need to add "m8" to the updater-script

I don't code Android SDK but if you can assign a remote key to run it then it will be great, don't know if an app can be triggered by a scancode.

I didn't understand what you were saying... now I get it. Unfortunately, I won't be able to do this

Cheers

[pj8]

That's exactly what the message says, strange as it's based on Stane's, maybe he can help with the installer.




Also the Wake issue for anyone interested: Maybe trying the 3 power assigning modes in remote conf file might help:

0x01 0x0081 System Power Down 0x0074 KEY_POWER 1.6 0x001a KEYCODE_POWER


0x01 0x0082 System Sleep 0x008e KEY_SLEEP 4.0 0x001a KEYCODE_POWER


0x01 0x0083 System Wake Up 0x008f KEY_WAKEUP 4.0 0x001a KEYCODE_POWER

Also it says:

4. The InputDispatcher asks the WindowManagerPolicy what to do with the key event by calling WindowManagerPolicy.interceptKeyBeforeQueueing. This method is part of a critical path that is responsible for waking the device when certain keys are pressed. The EventHub effectively holds a wake lock along this critical path to ensure that it will run to completion.

Seems the wake lock along that critical path is not held.

https://source.android.com/devices/input/keyboard-devices.html