MK808 "all models" Finless 1.7

[kedat]

Yes Leo, this is why I asked people if they side loaded some older version or something or Titanium backup has restored some bad version? I cannot recreate any of these problems and I have tried like hell to do so!


Bob

Regarding MXPlayer, I now have Lewy's latest ROM - so different base and kernel as far as I understand. And also have some problem others reported:
1. Hard to enter settings when on FULL screen
2. Sometimes skips fraction of second up to second while playing movie.

I have org. MK808 but using internal MEM (no SD card). Could this be a reason as system uses this memory for swap - just my wild guess? Using latest MXPro, clean system setup.

[nalle303]

First try

First try using MK808B.

Flashing with no problems at all, had to use the alternate_reboot_to_flash_tool.

Never figured out how to bring back the statusbar when using auto hide with the new launcher. So had to keep it visable.

XBMC, both official and XAF makes the MK808B turn of at what seems random. Using Latest MX player from Play-store in lates XAF-XBMC gave me MXplayer interface but only black screen.
Trying the older MXplayer app linked in the OP on XDA crashes XBMC.

Reverting back to 1.6 till i get my new MK808 next week.

[exglynco]

Have you flashed any other ROMs before? Opening a terminal and typing reboot bootloader is a kernel thing. For instance, my Arnova 10 kernel does not support this. If you flashed some other ROMs and currently have a kernel where support for this is removed, it will never work until you manually enter flash mode and flash with tools.

Bob

Thanks Bob,

Yes, I've flashed multiple ROMs before. I've returned to your 1.7 ROM, and even it won't allow a reboot to recovery or bootloader, despite doing it before. I made a CWM Nandroid backup, and can't get into recovery to restore it.

[leolas]

Re: BETA - MK808 "all models" Finless 1.7 BETA TEST - Report thread

Thanks Bob,

Yes, I've flashed multiple ROMs before. I've returned to your 1.7 ROM, and even it won't allow a reboot to recovery or bootloader, despite doing it before. I made a CWM Nandroid backup, and can't get into recovery to restore it.

Have you tried to enter recovery pusshing the reset button while you power on the device?

[lukesan]

First try using MK808B.

Flashing with no problems at all, had to use the alternate_reboot_to_flash_tool.

Never figured out how to bring back the statusbar when using auto hide with the new launcher. So had to keep it visable.

XBMC, both official and XAF makes the MK808B turn of at what seems random. Using Latest MX player from Play-store in lates XAF-XBMC gave me MXplayer interface but only black screen.
Trying the older MXplayer app linked in the OP on XDA crashes XBMC.

Reverting back to 1.6 till i get my new MK808 next week.

Be careful with XBMC. I would not touch it or make references to the 1.7beta at the moment.
The latest beta and the non beta (how can since it was not so developed yet for Android, still not to mature yet) crashes like crazy at random points and has nothing to do with the kernel or the rom.

I am using the Archos free player to test stuff and it hasn't let me down for a second.
The only thing is that I have to use the kernel from Alex because the one that Bob has included in the rom and the Omegamoon one is causing dropped frames if I stream from my sat receiver.
The Omegamoon seems to be extreemly slow in general use on my MK808 anyway.

[Finless]

Regarding MXPlayer, I now have Lewy's latest ROM - so different base and kernel as far as I understand. And also have some problem others reported:
1. Hard to enter settings when on FULL screen
2. Sometimes skips fraction of second up to second while playing movie.

I have org. MK808 but using internal MEM (no SD card). Could this be a reason as system uses this memory for swap - just my wild guess? Using latest MXPro, clean system setup.

What has Lewy's ROM have to do with this beta?

Lewy's ROM is just the Minix Neo X5 ROM with whatever kernel he is using. This ROM is not like this. I have modified it a lot! Taken smali code from many ROMs to add features including some cool ideas from the Neo X5. A prime example. Enabling the lock screen is all my code!
So the 2 are not even the same. So I am not sure what the reference or purpose this feedback has for this ROM BETA test?

Bob

[kedat]

What hasstateds ROM have to do withtotallys beta?

Lewy's ROM is just the Minix Neo X5 ROM with whatever kernel he is using. This ROM is not like this. I have modified it a lot! Taken smali code from many ROMs to add features including some cool ideas from the Neo X5. A prime example. Enabling the lock screen is all my code!
So the 2 are not even the same. So I am not sure what the reference or purpose this feedback has for this ROM BETA test?

Bob

Did you even read my post? I have stated I know this is totally different Rom. The thing is that the symptoms with MXplayer are same with both roms so maybe its not this particular Rom problem... do I really have to explain this?

[exglynco]

Re: BETA - MK808 "all models" Finless 1.7 BETA TEST - Report thread

Have you tried to enter recovery pusshing the reset button while you power on the device?

I've also tried pushing the flash button before, during, and after booting. Nothing works.

Sent from my rooted MK808 using Tapatalk 2

I'm not the lowest of the low, but I am the slowest of the slow (49.6 mpg over 38k miles in Scion xB)

[Finless]

Did you even read my post? I have stated I know this is totally different Rom. The thing is that the symptoms with MXplayer are same with both roms so maybe its not this particular Rom problem... do I really have to explain this?

This does not help me. I cannot recreate this problem with MX player nor can several other testers using it.
So throwing Lewy's ROM into this mix does not help me try to troubleshoot this.

Perhaps a video showing exactly what your are doing will help me!

Bob

[Finless]

QUOTE=exglynco;53429]I've also tried pushing the flash button before, during, and after booting. Nothing works.

Sent from my rooted MK808 using Tapatalk 2

I'm not the lowest of the low, but I am the slowest of the slow (49.6 mpg over 38k miles in Scion xB)

Since your very close to me, how about sending me this unit US mail and let me have a go. Just put about $5 and a return shipping label in the box. I will be out of town next week so best to ship it about Wednesday next week if you want to go this route.

PM me for address if interested.

Bob

[leolas]

Re: BETA - MK808 "all models" Finless 1.7 BETA TEST - Report thread

I think he want to say that he have some problems with mxplayer too in that Rom, that is not the same that we have, if I don't understand bad. Then maybe is a mxplayer problem, I dont have any problem with mxplayer by the moment.
I want to have problems to report them, but all I can see whith this Rom is that looks good, don't have great issues for me, and runs smoth with a 1080p kernel.
Ahh, forget to say that adb isn't work in stock Rom too for me so thats is not a bug.

[neoal]

Bob, i would like to try out the new beta test 1.7 firmware for my mk808b with rk903. Can you give me a link to download and test it and ill try to give info if smth unusual comes up

[kididaho]

Re: BETA - MK808 "all models" Finless 1.7 BETA TEST - Report thread

I am experiencing some sites thinking this is an IPAD, such as android forums which i have in Tapatalk II and doesn't recognize that i have Tapatalk installed. I believe it was Amazon last night that thought the same thing. Weird but nothing to worry about. Just a FYI

ROM is running really well for me, no problems with Droidmote or any of the stuff I am seeing pop up here in the thread. I do know that Droidmote just came out with an update so if one side i.e. phone or tab, was updated and not the other they wont connect.

Jim
MK808 Tapatalk II

[KasSGT]

Why can I not recreate this problem? Are you guys side loading MX player or getting the latest and greatest from Google Play. I just installed it from Google Play and again, I am not having this issue nor can recreate it.

I am going to need to help and detailed explanation of what exactly your doing and how in order to debug this. Maybe someone can make a video? Maybe it is a specific movie or video format? e.g. like RIOvers said with his MKV video (which are known issues anyway).

More help to debug this please.

Bob

Hi Bob,

First I just want to say that it's not a big issue regarding the MX Player, it's just one of the two things that came up that I wanted to let you know. Don't want to be banned from future Beta's, just because I am happy with the ROM and don't give any feedback.

I am currently uploading a small video on Youtube, which shows my setup and also shows the issue I'm experiencing with MX Player: http://youtu.be/5apIa_9R7Iw I've tried to do it the Rivers way (aloha!), but it's really hard, so it's not even close to his standards. I had to make four retakes, before the uhs and ahws became a bit bearable and had to write out some basic script to keep the story going... Kudos to Rivers on the way he does his videos, making it look so easy... But it really isn't!!!

So the two issues I have are (recap and giving you a better insight on my setup):

1. MX Player has a problem showing the info when left clicking (on my RC11 flymouse). It only stays up for a fraction of a second. This only happens when the nav bar is hidden. I deinstalled eveything and reinstalled the latest and the greatest from the GPlay store, before I made the video. I had downloaded the NEON codecs, which add a lot of decoding options to MX Player, from here: http://forum.xda-developers.com/show...php?p=38224432
I have tried the standard codecs and these codecs I downloaded. Doesn't make a difference with regards to the issue.

2. The other issue, which I haven't made a video of, because it's impossible to predict when it will happen: When coming out of sleep I had two scenario's happening to me a couple of times, but not always.
a. The mouse pointer was gone, just not accessible in any way (see mouse type above). Had to reboot by pulling power cord. However, I haven't had the situation happening againg lately. When it does, I will not pull the power cord, but I will first unplug and replug the usb stick for the airmouse. As soon as I have feedback, I will post it.
b. I had the situation where I was able to unlock the screen, but as soon as I did that, the screen went blue, which means there is no input detected on the HDMI port. After shutting of the television and turning it on again, the unlock screen would appear again, but unlocking would result in the same blue screen. This happened to me two times and I am unable to recreate it.

If you need more input on my setup, please let me know.

[lukesan]

Ok tested another rom to test KasSGT findings.

On another, non mr-Bob-rom, I am having the exact same thing when I am hidding the bar with mx player so it is not rom related.
Not only mx player is affected but the Archos player which automatically resizes to max anyways also shows weird behaviour with the onscreen data when the bar is hidden.

So lets conclude that hidding that bar is not always a good thing, but not a bug in the rom