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

[glenngaucigrech]

question.. is it even remotely possible that a bad hdmi cable or power supply can cause problems with boot up? this mxiii 1g I flashed it with the right rom 109k4 as its thee ap1618 version .. works and boots up at my place for as many times as I try it .. 20 plus times ..then take it to my pals house .. plug it on his hdmi cable which is the supplied one. .and it hangs at boot and stays there .. then the only way to wake it id a reflash ..


Sent from my Inspiron 7537 using Tapatalk

[no_spam_for_me]

So what I understand is, that the devices doesn't boot up at/with another HDMI cable and TV?
Maybe there is a problem with the HDMI cable and/or the other TV?
I think you use the same PSU?

[lawin1]

Found a temporal solution - use XBMC (Kodi) 14 alpha 3 build (latest builds do not work!). But XBMC 14 alpha 3 build apk isn't available on official FTP mirrors any more. So use this link instead - https://cloud.mail.ru/public/c671ee0...a3-armeabi.apk

Just updated firmware on Tronsmart s89 from 104k to the latest 109k. Launched XBMC 13.2 and enabled Live TV with IPTV Simple client. And now XBMC Live TV channel preview position is not centered as described in this post: http://www.freaktab.com/showthread.p...l=1#post213799
[ATTACH=CONFIG]8535[/ATTACH]

Before updating to 109k, I had XBMC 13.2 also but from official XBMC site and everything was ok. Is this known bug in included XBMC and how to deal with this problem?

[glenngaucigrech]

So what I understand is, that the devices doesn't boot up at/with another HDMI cable and TV?
Maybe there is a problem with the HDMI cable and/or the other TV?
I think you use the same PSU?

my house I took it out the box to set it up .. I used my own hdmi cable but the boxes power supply supplied in the box .. all worked fine I set it up and all good.. I gave it back to my friend and after 5 bootups or so it got stuck at mbox logo.. I went picked it up without the hdmi cable since I have some at home .. anyways .. I flashed it with latest fw 109k4 for ap6181 wifi chip ..(it was bundled with same rom) .. and it worked again .. I did on and off and unplugging it for over 20 times in 2 days and it worked .. s gave it back to him.. he calls me 20 mins later that the box is on mbox logo again stuck.. I took it back again and it really was stuck even on my tv with my hdmi cable then .. so I cleared cache n data from recovery and re flashed the rom this time via sd card.. again .. 20 bootups worked .. today I give it back to him and I will give him my hdmi cable .. so it was either pure coincidence .. or hid hdmi cable is really causimg the box to crash at boot .. so my question is .. could it be the hdmi cable that's causing it to basically die ?

Sent from my Inspiron 7537 using Tapatalk

[no_spam_for_me]

Ok, so it seems so that something went wrong if he connect it to his environment (maybe HDMI cable and/or TV)... BUT sorry I have no idea what went wrong???
Pity you don't tried it at your environment after wiping cache and data BEFOR you reflash it (only to find out if maybe some settings or so on run into what ever)...

[glenngaucigrech]

No no after wiiping them both i tried clearing data and cache and it still didnt boot .. i am hoping i did something wrong in the first img flash of the fw ...... now second time around i did the zip method maybe it works different . And i also cleared data and wipe cache right before the zip flash .


UPDATE .. i took it to his house .. and it worked for ten seconds then got stuck in menu . Restarted it amd stuck in mbox again ... i tried a new box and all worked well .. so may have been a defective box .. but something in his setup was triggering it ... that for sure . Cs i tried them plenty of times and on both occasions they fail in his house first try ..

Sent from my GT-I9505 using Tapatalk

[Finless]

WAKE LOCK permissions is an issue in the ROM

Oman, while the Bell TV app was something different, several other APPs also crash and this is due to permissions for Wake Lock.

The app is calling WAKE_LOCK and it doesn't have permission.

Here is the logcat error I saw in the PBS streaming APP.

W/System.err( 3847): java.lang.SecurityException: Neither user 10096 nor current process has android.permission.WAKE_LOCK.

Now I fixed the PBS APP by editing manifest.xml in the APK and repacking it. All I had to do was add this line to the XML file:
<uses-permission android:name="android.permission.WAKE_LOCK" />

Then the PBS APP worked. So the SDK has some issue with APP's requesting wake lock.

I have looked through some of the framework like policy, etc but cannot find anything sticking out at me to fix this issue in the ROM. But it does need to be fixed as many APPs will have this problem.

Anyway for anyone else interested, here is a working PBS APP

https://drive.google.com/file/d/0B9BFwCzfMWZ8ZVlabXlSSmllMnc/view?usp=sharing

Bob

[dave_999]

Good work Bob!

[mpolenis]

Disable usb sound

Hi Bob!
I hope this is the right place for my request.
Is there any chance that you may add a function to the next firmware update to disable usb sound on these devices (M8 etc.)?
I have purchased a minix A2 air mouse which has a speaker build in and I cannot redirect sound to my TV.
Thank you in advance.
Keep up good work!
Manolis

[JustMe]

Oman, while the Bell TV app was something different, several other APPs also crash and this is due to permissions for Wake Lock.

The app is calling WAKE_LOCK and it doesn't have permission.

Here is the logcat error I saw in the PBS streaming APP.

W/System.err( 3847): java.lang.SecurityException: Neither user 10096 nor current process has android.permission.WAKE_LOCK.

Now I fixed the PBS APP by editing manifest.xml in the APK and repacking it. All I had to do was add this line to the XML file:
<uses-permission android:name="android.permission.WAKE_LOCK" />

Then the PBS APP worked. So the SDK has some issue with APP's requesting wake lock.

I have looked through some of the framework like policy, etc but cannot find anything sticking out at me to fix this issue in the ROM. But it does need to be fixed as many APPs will have this problem.

Anyway for anyone else interested, here is a working PBS APP

https://drive.google.com/file/d/0B9BFwCzfMWZ8ZVlabXlSSmllMnc/view?usp=sharing

Bob

Yes there is definety issue with wake_lock

[indi123]

Looks like some lucky one's have it Ronin. Wonder why it don't work for all with 109k4? I'm for sure out of ideas

Could it be that beelink changed the hardware module on newer models of the MX3 2G version? This would be a question for Oman.

[oman]

Oman, while the Bell TV app was something different, several other APPs also crash and this is due to permissions for Wake Lock.

The app is calling WAKE_LOCK and it doesn't have permission.

Here is the logcat error I saw in the PBS streaming APP.

W/System.err( 3847): java.lang.SecurityException: Neither user 10096 nor current process has android.permission.WAKE_LOCK.

Now I fixed the PBS APP by editing manifest.xml in the APK and repacking it. All I had to do was add this line to the XML file:
<uses-permission android:name="android.permission.WAKE_LOCK" />

Then the PBS APP worked. So the SDK has some issue with APP's requesting wake lock.

I have looked through some of the framework like policy, etc but cannot find anything sticking out at me to fix this issue in the ROM. But it does need to be fixed as many APPs will have this problem.

Anyway for anyone else interested, here is a working PBS APP

https://drive.google.com/file/d/0B9BFwCzfMWZ8ZVlabXlSSmllMnc/view?usp=sharing

Bob

Ok,thank you.

Could it be that beelink changed the hardware module on newer models of the MX3 2G version? This would be a question for Oman.

NO hardware module adjust for mx3 2G version.

[oman]

I have posted the mx3 1G(ap6181) ROM onto the first page.

[Veronica]

I started to get flickering with black lines and black screen after wake from sleep, after a minute or so the black screen flickering stop but the thin black lines on screen will remain, i think mostly when i move the mouse. Anyways i went back to my 108k4 backup a week ago and no flickering at all, so far so good, i just need notification sounds fix.

[dave_999]

@Oman
I'm sorry to keep asking but do you know whether there is any development being made on the amcodec?