Stock Firmware - Beelink S82/M8 - MXIII 1/2G - Official FW Releases from Beelink - user feedback thread

[fikhl]

All I want is that HDMI error fixed (no video or correct resolution to the tv), that's all I ask fw 108k was the last one without this error

Amen to that.

It's VERY annoying! The frequent updates we got over the past few months have been amazing and I'm thankful for that. But this HDMI issue is a real deal breaker. I sincerely hope it's fixed sooner rather than later.

-----------------

Guys, how can I manually access the recovery mode?



Tapatalked

[hereje]

Guys, how can I manually access the recovery mode?

the way I do it is:
install Terminal from Play Store

enter this commands:

su
reboot recovery

[Ichijoe]

If the S82... (I guess it must be...), is this bad with respect to the HDMI Port... I'm now kinda glad that I only have the M82 (i.e. 1G/8G) Version...

Amen to that.

It's VERY annoying! The frequent updates we got over the past few months have been amazing and I'm thankful for that. But this HDMI issue is a real deal breaker. I sincerely hope it's fixed sooner rather than later.

-----------------

Guys, how can I manually access the recovery mode?



Tapatalked

As to the Recovery Mode... You need to take a small non-metallic Probe. (I'd recommend using a Q-Tip, with the ends removed. With which you need to jam up the AV Port behind the Device, till you hit the hidden Reset Button. Hitting this, you then power up the Device.

Now it gets a bit tricky... As on my Old Mans MXIII you must hold the Reset Button till the Recovery hits. While on my personal MXIII you can release it on the Google TV Screen. How this may play out on your Box? I know not. But, that would be pretty much how you'd do it.

Otherwise take a look though the Play Store, and see if you can't find any Re-boot to Recovery App(s). Which should also land you back into Recovery Mode.

[dave_999]

Fail when flashing

Well so far I've tried flashing the 113k4 S82 & the 113k4 Tronsmart images on my Measy S82 2/8gb and it fails at 3% using the USB tool.

Anyone having any luck? Perhaps they're only for the 1gb devices.

[rompom]

I flashed yesterday mxiii 113k4 firmware on my beelink m8 round box.Everything works normal.I mean is no difference to 112k firmware.

[Ichijoe]

Well so far I've tried flashing the 113k4 S82 & the 113k4 Tronsmart images on my Measy S82 2/8gb and it fails at 3% using the USB tool.

Anyone having any luck? Perhaps they're only for the 1gb devices.

Yeah I noticed that too... The "trick" here is to leave the Erase Options all unchecked. Then it worked for me...
Otherwise with such Options checked... It also failed with 3%
Its also worth pointing out that, this was also the case on my 1G MXIII (K200, M82), so its probably not just you...

I flashed yesterday mxiii 113k4 firmware on my beelink m8 round box.Everything works normal.I mean is no difference to 112k firmware.

Well that's not entirely the case.... They did manage to find the F7 Key and correct "Dobly" for "Dolby" on the Setting > Advanced Screen. We also have the option to disable usb-audio OUTPUT... (Whatever that does... I'ma gonna guess this is for those freaky Airmice with the built-in Mics on them... However not owning such a Device I wouldn't really know).

Can anyone else confirm both the Kernel Ver. and XBMC Ver on this Build? For me its

Android Ver. 4.4.2 Stock Nexus build (KOT49H)
Kernel 3.10.33 (Same as 112k4!)
And SPMC/XBMC 13.4

Or was it something I done, did wrong?

[Magnifico]

I read about an HDMI problem. Could some please EXPLAIN that problem?
I don´t think I have that kind of problem but still I would like to know about that problem.

[dave_999]

HDMI video signal bug still exists - 113k4

Updated to 113k4. I can confirm that the HDMI signal is still flakey when the box adjusts the frame rate.

This is the only thing I really want to see fixed. The wait continues... I can only hope that lollipop addresses this issue as Google recognises that android is widely used on TV boxes.

[hereje]

I read about an HDMI problem. Could some please EXPLAIN that problem?
I don´t think I have that kind of problem but still I would like to know about that problem.

It has something to do when you resume the TV Box from sleep. Some TV's (like my Philips) does not recognice the resolution or refresh rate that the TV Box is sending (sometimes a black screen, sometimes an error message), in my case I have to press the source button from my TV remote a few times until the TV can show what the TV Box is sending.

[Ichijoe]

It has something to do when you resume the TV Box from sleep. Some TV's (like my Philips) does not recognice the resolution or refresh rate that the TV Box is sending (sometimes a black screen, sometimes an error message), in my case I have to press the source button from my TV remote a few times until the TV can show what the TV Box is sending.

That could be the problem right there in the Nutshell... Not that I'm hurting much having just ditched a 450W+ HTPC for this "Device"... And was more then happy to do so. But, when it comes time to shut the damned thing off... This is what I invariably do... After all its all about keeping "Green"...

Green here being of the folding kind, that weren't on the whole unhappy... Even if I'am and am sitting here thinking that leaving the Trees was a bad move. lol But hay if it also has the side effect of saving a few Trees... Then more so...

But, I think I can live with a ~20-ish Second Boot time...
Because I can live with it.... Its just as likely why I've never seemed to actually "hit" this "problem"... If its even indeed a problem.

[daniello9]

That could be the problem right there in the Nutshell... Not that I'm hurting much having just ditched a 450W+ HTPC for this "Device"... And was more then happy to do so. But, when it comes time to shut the damned thing off... This is what I invariably do... After all its all about keeping "Green"...

Green here being of the folding kind, that weren't on the whole unhappy... Even if I'am and am sitting here thinking that leaving the Trees was a bad move. lol But hay if it also has the side effect of saving a few Trees... Then more so...

But, I think I can live with a ~20-ish Second Boot time...
Because I can live with it.... Its just as likely why I've never seemed to actually "hit" this "problem"... If its even indeed a problem.

I found not much difference between standby and idle power consumption when I measured. Just leave it on.

Sent from my phone.

[wheelboy]

I found not much difference between standby and idle power consumption when I measured. Just leave it on.

Sent from my phone.

i always pull out the powercord lol thats real dutch. but real grean also i have for 3400kw on solar panels'.

thats real grean. Lol dont like to pay taxes dutch gov likes to tax everything.

i played along time with my gaming laptop. It was better than the tronsmart but also 180w power consumption was to much 4 me
so i take it for granted that it takes a little longer and sometimes doesnt work the way i want it. Also i have the tronsmart from june 2014 and i spend a lot of time waching tv with that thing. Thats why the next one is going to be more expencive (want the nvidia shield that comes out in may) since i spend a lot of time with it .

[hereje]

I can only hope that lollipop addresses this issue as Google recognises that android is widely used on TV boxes.

mmm, I hope we don't get any Lolipop update until the 5.1 be stable enougth, I use to have 5.0.2 in my Moto G and I ended flashing Cyanogenmod 11 (4.4.4) because I got sick of all that many memory leaks

[scooter2014]

Got s5 lollipop battery blew up from memory leak. Sweet Jesus.

[wheelboy]

mmm, I hope we don't get any Lolipop update until the 5.1 be stable enougth, I use to have 5.0.2 in my Moto G and I ended flashing Cyanogenmod 11 (4.4.4) because I got sick of all that many memory leaks

Oh so true. Progression doesnt always mean that its better. I have 5.01 on my note 3 and indeed lot of mem leaks .But with clean master i think the problem is gone.And it looks great