yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] braindamage985:
up :/
[Android Q&A, Help & Troubleshooting] croniccorey:
Hi,

We do support 802/805/812 but we don't release FW for these SoC's instead we encourage users looking for quad-core EmbER to consider buying from our sponsors ArnuTvBox they run OEM EmbER with all the same features as generic EmbER outta the box and have a great team including Josh and myself to back it.

Thanks,

Corey
[Android Q&A, Help & Troubleshooting] braindamage985:
Ookk thank you Cor :D
[Android Q&A, Help & Troubleshooting] rusnak666:
revert from ember to android?

Hi,

please how can i revert from ember to android? Im using atv520e, downloaded revert to whatever files and followed all steps, but im getting this message: assert failed: getprpop("ro.product.device") == "stvmx" II getprpop("ro.product.device") == "stvmx" Installation aborted

Please can you help how to revert? Thanks
[Android Q&A, Help & Troubleshooting] madmaxamus81:
confluence skin

Hi All,

I have successfully installed EmbER on TLBBv2 and was wondering if anybody knows how to install the kodi default confluence skin? I have tried to find it in the Kodi repo but its not there.

I am trying to use a specific addon that needs to be used in the official confluence skin and wont work when in the EmbER mod skin.

Thanks in advance.

Regards, Adam
[Android Q&A, Help & Troubleshooting] croniccorey:
I will add Confluence to the EmbER repo asap.
[Android Q&A, Help & Troubleshooting] madmaxamus:
Many thanks croniccorey, much appreciated.
[Android Q&A, Help & Troubleshooting] madmaxamus:
Sorry to be a pain, just wondering when you think you will be able to add confluence to the EmbER repo?
[Android Q&A, Help & Troubleshooting] Josh.5:
Sorry for the delay. Been real busy lately.

I'll get this done ASAP. Hopefully before the weekend.
[Android Q&A, Help & Troubleshooting] spinaltapt:
Help Required - changing network connection in EmbER 2.02

Hello

I have a Geniatech / Mygica 520e AML MX box running EmbER Rom V1.01 without any stability issues working on the wired Ethernet port, and I subscribed to the Donner Edition when this hardware was listed as supported.

I have tried updating the firmware to V2.02 which installs without any problems but then fails to connect on the wired Ethernet connection.

I understand that there is no driver support for the wireless card in this box, and I also understand that there is a EmbER Settings addon bundled with the firmware that has a network manager tool to allow you to switch from the wireless to the wired Ethernet connection, the problem I am having is that this addon gives me a script error every time I try to open it so I cant get into the network manager settings to either view or change the settings.

Does anyone know if there is Any way of changing the Ethernet connection to the wired Eth0 port either by getting the EmbER settings addon to run or by changing a configuration file somewhere.

In the mean time I have re-installed EmbER v1.01 and that is still working okay on the wired Ethernet port so I am fairly sure the problem is not with my wired Ethernet connection.

Many Thanks

Mick.
[Android Q&A, Help & Troubleshooting] RayWalton:
I would backup your current add-ons and settings using Rob Weber's backup add-on. This backup add-on is available in the main KODI repository and once installed set it to point to your installed SD card under the General tab and also set it to backup Addon Data and Profiles in the next top File Selection tab. Then run the Backup add-on and select Backup and wait whilst it backs up your data to your installed SD card. Once completed successfully shut down the box and power it off and to be safe remove the SD card for now.

With no SD card installed (or at least not a bootable one), using a toothpick hold in the recessed Reset button and apply the power. The box should, after about 20 seconds of continuing to hold in the Reset button, then boot your box up to the default EmbER Recovery screen, and of course you can then release the Reset button. From the list of options you are presented with select the Factory Reset one and that will clear all the data out leaving you still with the EmbER V2.0.2 firmware. Once if has confirm it has completed the Factory Restore then select the Reboot option at the top of the list and that should boot you back up into the home screen, only now with a new virgin EmbER setup. You can now check your EmbER Settings add-on now runs without a script error, if not then you will have to reinstall EmbER V2.0.2 before going any further. You can now reinsert your SD card.

Now you should re-install the Rob Webber's Backup Add-on from the KODI repository again (that repo will be available by default) and set it up as before to point to your SD card, and include the Addon Data and Profiles in the File Selection list (the only options in the file selection list not enabled should be just the two Custom ones at the bottom of the list.). Once installed and set up then run this backup add-on and select Restore where you should see your initially saved backup on your SD card. Select that backup to restore your add-ons and settings. IMPORTANT, immediately the back up has finished restoring then before doing anything further pull out the power plug wait about 10 seconds and then reapply the power and reboot. All your settings should then be restored, including things like short cut icons, screen calibration, International settings etc,

Hope that works for you spinaltapt. Good luck and always remember you do all the above at your own risk of course.

Ray
[Android Q&A, Help & Troubleshooting] baruchin:
I know they're old. But, I have a couple of those getting dust in my house. Is there going to be support ever for old M3 devices like TLBB v1?
[Android Q&A, Help & Troubleshooting] jona5:
I've also got problems with the system settings script crashing with my g18ref (HD18T2) which I'll detail in my next post.

But the way I got an Ethernet connection via dhcp was to create a file in /root/Run with the following in it.

ifconfig eth0 up

udhcpc eth0

I did this through a UART console, but I think if you're upgrading from 1.01 the file will remain when you upgrade to 2.02.

---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------

This is after a fresh install (nand erase) of Ember 2.02 on a g18ref board (ENY HD18T2).

kodi.log

ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.IOError'>
Error Contents: (19, 'No such device')
Traceback (most recent call last):
File "/usr/share/kodi/addons/script.system.settings/service.py", line 4, in <module> from resources.lib import onrun
File "/usr/share/kodi/addons/script.system.settings/resources/lib/onrun.py", line 6, in <module> from resources.lib.update import rsspyota
File "/root/.kodi/addons/script.system.settings/resources/lib/update/rsspyota.py", line 66, in <module>
File "/root/.kodi/addons/script.system.settings/resources/lib/update/rsspyota.py", line 50, in getserial
File "/root/.kodi/addons/script.system.settings/resources/lib/update/rsspyota.py", line 36, in getHwAddr
IOError: (19, 'No such device')
End of Python script error report<--

INFO: Loading /root/.kodi/addons/skin.embermod/sounds/sounds.xml
NOTICE: /root/.kodi/addons/skin.embermod/sounds/sounds.xml, Line 0
Failed to open file

It doesn't look like I have any script.system.settings directory under /root/.kodi/addons

Anyone have any idea?
[Android Q&A, Help & Troubleshooting] RayWalton:
I have an MX2 box which of course has a G18Ref board and was successfully flashed to EMbeR V2.0.2 some months ago, It has been used successfully and stable too by a friend of mine who brought this box off of me all configured for him. Well a few days ago he phoned me to say it would not boot at all and just left a blank black screen and he says he had done nothing to the box to change anything which I well believe knowing him well.

So I brought the box home and have found it is endlessly trying to go into recovery mode without even pressing in the reset button, but without a bootable SD card in the slot then of course nothing will happen and thus the blank screen after power up.

So I tried to re-flash the device with Ember V2.0.2 which it already had installed and sure it booted up to recovery mode and auto started installing EMbeR 2. and all seemed to go well reporting a successful installation. However when it tried to auto reboot it simply kept repeating the installation even though I was no longer Holden in the reset button of course.. I forced the box into the recovery screen with a bootable otherwise empty SD card and tried a Factory Reset and Cache Wipe all which went successfully, Tried then a manually selected reboot and the same problem as it either auto returned to the recovery screen or if I removed the SD bootable card then back to the blank screen boot up originally reported.

Tried reverting to Android using the EmbER Android recovery set of files supplied at the same time as EmbER 2 and even tried the original 1.1.5 Android OS the boxes were shipped with. All showed they installed successfully but then the same problem when auto rebooting and it returning to reinstalling form the SD Card. So it is like I was continually holding in the reset button.

Next step with a multimeter I opened the box and checked the reset button and proved it was physically working correctly. So it seems to be not a hard brick but what I think is called a soft brick. Tried everything I know to unbrick it (other than pin shorting as do not know which pins to short on this MX2 box) and all to no avail. Images install successfully but will nto boot into anything other than recovery mode as though I was holding in the reset button on power up..

So can anyone like Josh or croniccorey please help here who knows of this problem and its cure ? Would very much appreciate some help and feedback regarding this issue.
[Android Q&A, Help & Troubleshooting] ninguemrj:
Hi all,

I have an atv1200 box running the second flavour of kodi Linux from this page : http://forum.kodi.tv/showthread.php?tid=180446

I'd like to change it to ember... Should I use the android to Linux installation file or something else?

Could you please guide me in order to avoid bricking my box?

Additionally, in the ember web page I couldn't find the directly link to install v3.0.0 from scratch. Should I install the 2.0.2 and than update it to 3.0.0?

Thanks!

Ricardo Jr
[Android Q&A, Help & Troubleshooting] ninguemrj:
Anyone?... :(
[Android Q&A, Help & Troubleshooting] Josh.5:
Just download the ember v2.0.2 files from http://ember-dev.com

Just be sure to extract all files from the zip to your SD card and read the instructions provided carefully.
[Android Q&A, Help & Troubleshooting] RayWalton:
EmbER 3 is only available to DE subscribers and not available as a public download and maybe will not be. So yes indeed first get EmbER V 2.0.2 working first and then subscribe to the Donor Edition and it should auto update to EmbER 3 shortly after you have registered your EmbER 2 copy on your box.

I now have EmbER 3 running after a little annoying auto update bug with my particular box but I h ave to say positively that EmbER 3 is now running fine and so far seems very stable but gives me no significant new features I did not have with EmbER 2 running Helix.

Be warned if you prefer MX Linux and want to return to it I have to say so far I have found no way to do so. EmbER 2 has bugs so you will need to subscribe to the DE to get EmbER 3 to make it at all worthwhile. Isengard gives little improvement over Helix that I can see only a few small procedural changes and bug fixes I understand, so tbh not worth updating IMHO just for Isengard at this time. Unless someone here can give me a good reason I am not aware of as to why it is still worth while
[Android Q&A, Help & Troubleshooting] RayWalton:
I want to add to my last post here that EmbER 3 is well worth the upgrade as it is far more stable and reliable and fixes the important skin and GUI sounds bug in EmbER 2 as well. As to Isengard over Helix, well after using it for some time it has a few undocumented improvements I have noticed, one being the skip forward or back when playing a video stream as this is not superb as with multiple left/right arrow presses you can skip various lengths of time form, 10 seconds to 30 minutes and it si also configurable in the System Settings|Video options as to what skip periods you want available and how long it will pause before carrying out your request.

So I take it back that it is indeed well worth the upgrade to EmbER 3 and Isengard 15.2 and of course if your box is registered for EmbER Donor Edition you get it anyway automatically. So for that US$10 registration fee it is great value and well worth while registering your EmbER firmware, and very importantly it supports these great developer guys Josh and Croniccorey at EmbER Developments and indeed additional donations would be well deserved too.
[Android Q&A, Help & Troubleshooting] Slymobi:
Hi

Recently got an Arnu Mach 10 ( Crimbo present ) just trying to figure things out, hopefully you guys are the best place to ask ?

Basically just wondering why the Mach 10 internal memory is partitioned into 4 slots ?

On the raspberry pi running pure openelec the partitions would be 2: 1 system and 1 storage.

As you can see here it has 4.

Is this the standard partitioning for the Mach 10 ?

Also, kodi/open elec has peripheral settings that give cec options but the Arnu box does not have these settings enabled, is there a reason why we can't alter the cec settings ?

Regards as always

Regards as always
[Android Q&A, Help & Troubleshooting] Josh.5:
That is 3 partitions. 1 is system, one is cache (dedicated for firmware updates on these boxes), and the last one is data (which is split into a few separate mount points that you seen on you screen there. Openelec does this too with the exception of our dedicated cached recovery partition.
[Android Q&A, Help & Troubleshooting] croniccorey:
FIRST

Waiting to see the Amlogic S905 running 64bit Linux....? wait no more EmbER-Dev has completed the first alpha builds of EmbER 3.0.1 for the upcoming ARNU Box

Check out this tweet to see it in action.
[Android Q&A, Help & Troubleshooting] Slymobi:
Thanks josh.5 was starting to think this forum was abandoned.
[Android Q&A, Help & Troubleshooting] RayWalton:
Have not tested it yet as waiting for a new MXQ M12 box I have ordered from AliExpress to arrive, but there is now a released version of EmbER V3.0.1 public edition for the S805 quad core MXQ M12 box. It is there to download from the EmbER website.

Looks very promising indeed and I know that EmbER are very excited about it as it is as I see it a major step forward. So this to my knowledge is the first public release of any Linux quad core firmware, but note this is not for the generic MXQ boxes as yet. Anyone here who gets this installed on their M12 S805 based boxes then please report back to us here, as indeed I shall once my new M12 box for testing arrives through the post and is flashed with this new EmbER firmware.

Congrats to EmbER Developments and thanks Josh and Corey for all their hard work in making this possible. It will be good for us all to be able to fully support them on this great new project.

Enjoy
[Android Q&A, Help & Troubleshooting] RayWalton:
Good news new nightly builds for m6 boxes now available :)

You should now see EmbER V4 nightly builds available for the supported M6 boxes so G02Ref, G18Ref, CMX and TLBB versions available and these are now using of course KODI V16 Jarvis. So as long as you are a registered Donor Edition user you can test the new nightly builds for yourself but of course at your own risk. Main thing is that folk should report any bugs that they may find here together with their box type and the nightly build version they are using.

There is also a new nightly build for the MXQ M12 S805 metal cased boxes too which superseded the earlier one released last month. I have already installed that OTA and it went very smoothly. No real differences I noticed though but I understand only minor background bug fixes. This S805 build works very well indeed with a few very minor bugs that really do not detract from using this build at all.

Josh has also mentioned that EmbER 4 should be out of beta, at least for the M12 boxes, by the end of next week. So more good news and all should show it has been well worth the wait. He is extremely busy getting it all finished off ready for release so unable to post here himself right now, so he sends his apologies for that. So my posting this announcement here on his behalf purely as a messenger will hopefully be a great help to him as you will appreciate.
[Android Q&A, Help & Troubleshooting] DancesWithChickens:
I just updated my TLBBv2, went smoothly.

Will report any findings.

For those updating to Jarvis:

Make sure to switch to the default skin first.

edit:

Small thing - after updating, country (and therefore timezone) was changed to USA for some reason.

Video playback has improved - i have some high bitrate convert videos (mkv/1080p/DTS) which would freeze for a few seconds when skipping chapters, now it's almost seamless.
[Android Q&A, Help & Troubleshooting] RayWalton:
Yes this is a small bug with it not retaining your existing timezone when updating, but easy to set back correctly so just a small nuisance really . Josh does know about this as have mentioned it to him before.
[Android Q&A, Help & Troubleshooting] RayWalton:
List of discovered bugs with ember 4 s805 nightly build.

Thought I would start a list of the minor bugs I have so far found with EmbER 4 nightly build for the M12 S805 box. Please make sure you are fully aware that this S805 build is ONLY for the metal cased MXQ M12 box so please only add any discovered bugs to this list if you are using that particular box for which the build is exclusively intended.

Here is my list of bugs to date of which I am sure Josh already knows about.

1. Small size flash EmbER logo screens both the passive and active ons at boot up.

2. When updating to new EmbER firmware the old settings are retained EXCEPT not the time zone which reverts to USA New York time adn needs resetting.

3. Over sensitive repeat function with remote. This may be a hardware problem with the remote though rather than in the firmware. Not a deal breaker as you soon get used to it.

4. When box is in Suspend mode the system clock loses a lot of time which can be over an hour a day!! It stays correct if you leave the box fully on even though idle. A full reboot of course resets the clock correctly.

5. With laggy internet connection to the USA the date/time initial setting at boot up can fail to access the US ntp servers, thus leaving you with a 1970 default Linux date. There is a simple fix for this already (see back in this thread) for those few of us who are affected by it, as we are currently in SE Asia due to a long standing subterranean cable outage.

6. Often with the EmbER backup utility you cannot get a list of existing backups to restore from if using the SD card for saving backups to. A system reboot fixes this. Never a problem backing up to the SD card though.

As I mentioned these are all very minor bugs, many with easy work arounds, but please feel free to add to this list if you have any more. Other that that the latest EmbER 4 nightly build for S805 is very stable indeed and runs very well with good snappy operations and navigation too :)

For those running M6 dual core boxes then please c.an someone start another list for any bugs they discover with the new EmbER 4 nightly builds for the various M6 boxes. Currently I have not got a working M6 box to test with and now using my available time to work with the new S805 M12 quad core box as i believe this is the way forward right now though the M6 boxes are still perfectly serviceable of course
[Android Q&A, Help & Troubleshooting] RayWalton:
Tip before flashing MXQ M12 boxes to EmbER

Many would have seen the reports of a minor bug when booting an MXQ M12 S805 box to EmbER where the boot up two logo screens appear very small rather than full screen, in fact a 720 res frame on a full 1080 display. Well this is easily avoided by firstly changing the display setting in Android to a 720 res mode before first flashing to EmbER.

It is anyway always best to first check your new box is working properly with it's default Android firmware, so let your new box boot fully into the Android opening screen. Then from the menus options select Settings and then Display. Turn off the auto HD detect option and set the resolution to 720p mode and ensure all is working well when you return to your Android home screen. Now you can power off and flash the latest EmbER firmware in the normal way. Once complete you will enjoy the full screen opening two EmbER logo screens and for the latest Nightly you will also see the very nice new animated logo screen too

I discovered this little trick thanks to Cory mentioning this small boot logo display problem was not an EmbER bug but due to the default screen res inherited from the default Android firmware. So tried the above method with one of my new stock of MXQ M12 metal cased boxes with EMbER V3.0.1 and then updated it to the latest Ember 4 Nightly build for these S805 M12 boxes, and voila problem solved.

With the full public release of EmbER 4 due any moment now, the above tip will be very useful for many of you who have been waiting for this latest S805 EmbER release to flash to your new MXQ M12 boxes. But this MUST be carried out prior to flashing of course as so far there is no way I have yet found to go back to default Android just yet, though I am looking for a default Android build for these boxes to supply to Josh who will then compile, check and release a suitable revert image for EmbER back to Android on the S805 boxes. So does anyone here have a link for such a default Android S805 build for these M12 boxes ??