yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] RayWalton:
Well I have no desire to go down the OpenELEC path. However you have made me think that if installing OpenELEC firmware over the top of my currently corrupted EmbER installed M12 boxes, that may possibly clear the corrupted boot loader sectors of memory. That may then allow a good new clean install of EmbER 3.0.1 for me to create a brand new set of add-ons and settings as I proposed. Do not though want to create a worse problem that may not be possible to clear easily, so for now waiting patiently for Josh and/or Cory to shed some light on this issue.

Yes you should have for now at least got the very nicely constructed MXQ M12 box as less than US$20 dearer and has Bluetooth too which may be supported it seems with EmbER 4 or later. I too have a virgin plastic MXQ S805 box which as yet has no EmbER build available for it. I want to keep that MXQ box in virgin Android state for now so I can test the installation of the new EmbER build as soon as it is released.

Important for people to note that the EmbER 3.0.1 M12 firmware though does work well as long as you do not try to install your old M6 box EmbER backups to these excellent M12 boxes. The remote issue is minor and can soon be corrected and even okay though not ideal to manage with it as is if needed. So no need to delay moving up to these new M12 quad core boxes with EmbER S805 firmware as this is the way forward. Dual core M6 based boxes will soon become more and more difficult to source of course, though I understand Geniatech are for now continuing production of their ATV1220T dual core G02Ref based boxes.
[Miscellaneous Android Development] Wotzit:
Yeah I'm also waiting for an EmbER build Ray, that's why I downloaded the latest Android rom for the box prior to flashing OE (so I can restore it to OOB, if necessary, when one is available).

I really can't stand Android, and don't see the point in missing out on the extra 'oomph' the new toy has to offer (which is impressive) and, as you have already said, "cheap as chips" for less than AU$60 including postage.

Happy Days . . . :good:
[Miscellaneous Android Development] Russell_S:
Hi Ray, what about using the 'Revert To Android' software which will rewrite the original MTD partitions to your box and then re-flash EmbER again.

Also, ssh works exactly the same on the M12 as the older boxes:

User: root

Password: letmein

Russell
[Miscellaneous Android Development] RayWalton:
Hmm thought I had replied to this yesterday but seems not ??

Okay well there is no revert to android build yet available on the EmbER site as it simply gives Error 403 Forbidden !!! So I wonder where Wotzit got the revert to Android files for use with the M12 box ?? Would like to try that to restore my M12 boxes to virginal state, but I think we need to use the EmbER revert files as they change the EmbER reorganised NAND partitions back to the original too. Not sure though if an original M12 Android image will do that too ???

Thanks for confirming the /root password is unchanged.
[Miscellaneous Android Development] Russell_S:
Oh, sorry about that. I saw the 'Revert to Android' link but didn't actually try it. Hopefully Josh or Corey will come up with something.

My main problem at the moment with the M12 box is it's inability to play back Mpeg2 video files with hardware acceleration which Corey has confirmed is a long standing problem with the amcodec. He has been in contact with Amlogic about it but they have yet to resolve it. Hopefully it won't be an issue for me for too much longer as I am gradually converting all my old Mpeg2 DVD files to h264 files because they won't play in Plex either. So I will be killing two birds with one stone so to speak.
[Miscellaneous Android Development] Wotzit:
Sorry, no revert to Android required here, I have an MXQ so no EmbER build available yet to come back from

Presumably, that didn't work then? As far as your MXQ goes . . .

Have the best of both worlds Ray.

Install OE to an SD card and it will boot and run from that, leaving your Android installation untouched ;)

That what I'm doing at the moment, until the EmbER build for MXQ is released
[Miscellaneous Android Development] charlie_mtl:
Hi buddies,

I bought a MXQ with OE already installed. downloaded and installed EmbER v3.0.1 for M12, tweaked the remote.conf.

Everything works pretty well. I have the NTP issue when wake-up after suspend and System setting crash when kodi starts. So probably no wifi but it is not a problem for me as I use the RJ45 connection.

Regards.

Charlie
[Miscellaneous Android Development] Josh.5:
Fingers crossed... M12 users should see a new nightly for Ember v4 in the next 24 hours. Stock M12 remote has been mapped as follows:

TV Buttons are mapped to:

TV IN = Play/Pause,

VOL- = SUBS,

VOL+ = AUDIO,

POWER = STOP,

Coloured buttons are mapped to:

SETUP = Open Kodi settings,

APP = Show media info,

VOL-/VOL+ = Volume controls,

Mouse button is mapped to TAB (media full screen/minimise)

Please note that while I have mapped the default TV buttons that are on the top of the remote, these buttons are designed to be programmed. If you do program them, you will loose these defaults (I do not know how to get them back...perhaps remove the battery for a very long time). If you do wish to program these buttons, do so as follows:

Hold down the "SET" button (the power button will light a solid red).

Press the button (TV IN, VOL-, VOL+ or POWER) that you wish to program (the power button will begin flashing red).

Point the remote you wish it to learn from directly at the front LED of the M12 remote.

Press the button on the remote you wish for it to learn (the power button will flash x3 times and then remain solid red. This confirms that it has now learnt that IR Code).

To exit the remote learning function, just press the "SET" button again.

If you are using this remote and you have an idea for a better use for buttons such as the green "APP" button, let us know. I just chose this config off the top of my head.

For anyone waiting on EmbER v4 for m6 devices, you will need to wait for a bit longer. G18ref nightlies may also appear in the next 24hours....no promises...
[Miscellaneous Android Development] Wotzit:
Strange, most come as Android boxes - Is your MXQ HD18Q or m201 type ? It's pretty important for those that might follow your lead, and with no revert available yet . . .:crying:

---------- Post added at 07:12 PM ---------- Previous post was at 06:51 PM ----------

c'mon Josh - give us something to play with. . . . :good:
[Miscellaneous Android Development] RayWalton:
Not tried the OE on my corrupted M12 EmbER box as do not want to complicate things until Josh has an answer to clear the corruption on the M12 box.

No rush on the MXQ box either but did not know you could run OE from an SD card and keep the internal firmware and nand memory allocation all untouched. Interesting and something I may try at some time but no rush to try OE either to be honest.
[Miscellaneous Android Development] Wotzit:
No worries man, just couldn't bear to think of you not being able to play with your new toys :laugh:
[Miscellaneous Android Development] charlie_mtl:
Hi,

Sorry but I don't know the type of this box.

FYI:

https://www.amazon.ca/MXQ-OpenElec-...UA?ie=UTF8&ref_=pe_386430_30332290_TE_3p_dp_1

[root@EmbER ~]# cat /proc/cpuinfo
Processor	: ARMv7 Processor rev 1 (v7l)
processor	: 0
BogoMIPS	: 3.75

processor	: 1
BogoMIPS	: 3.75

processor	: 2
BogoMIPS	: 3.75

processor	: 3
BogoMIPS	: 3.75

Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc05
CPU revision	: 1

Hardware	: Amlogic Meson8B
Revision	: 000a
Serial	: 1b00000000000000
[root@EmbER ~]#

Regards,

Charlie
[Miscellaneous Android Development] Wotzit:
Presumably you altered updater-script in EXTRACTME_EmbER-Amlogic-M12-3.0.1.zip to get it to install :confused:
[Miscellaneous Android Development] RayWalton:
That is clearly an MXQ box and there is no appropriate EmbER build released for it yet as it clearly says on the EmbER download page. THe build that is available of EmbER 3.0.1 is for the MXQ M12 box which is in a metal case with only two USB ports but built in BlueTooth and sell for something like US$55 with basic Android bloatware.

You may get all sorts of problems with that wrong EmbER build installed. In fact I see you already have some like the EmbER Settings screen wont work probably because the version you installed has the wrong WiFi chipset drivers and with no WiFi available EmbER settings cannot launch and will through an error at boot up. So you can neither register or update the EmbER firmware nor indeed access any other EmbER setting utilities liek Backup and Maintenance.

You will need to wait for the MXQ Ember release which is as they say coming soon. Hope you have not caused a problematic corruption installing the wrong firmware. I would have simply left OE on there for now.

BTW what did you pay for the box including delivery ?? Normally with default Android they are about US$32-US$35 with free shipping.

So with EmbER S805 firmware registration at US$25 and the roughly an hours work involved in changing it over from Android and then installing a good set of add-ons with configurations and thoroughly checking it and packing it for shipping, I would imaging they could not feasibly be sold under about US$100. And the dearer M12 box about US$120, all of course pre-registered and activated with the latest OTA updateable EmbER firmware.
[Miscellaneous Android Development] Russell_S:
I've just updated my M12 box to the v4 nightly build (4.0.0~nightly_20160420) and everything went well. The update itself was smooth enough and it is now running Kodi 16 (Jarvis). One thing that I wasn't expecting is that my Mpeg2 DVD rips are now working with amcodec hardware acceleration enabled which is a big positive for me.

The only thing that I did notice is that video playback is not filling the screen and has a black border on all sides. I subsequently found that the video calibration had been lost for whatever reason and had to be redone. So no big deal but I thought it was worth mentioning.

Everything appears to be working as it should. If I find any issues I will report back.
[Miscellaneous Android Development] Wotzit:
Thanks for confirming that Ray.

Had me wondering for a minute since that looks exactly like my box (although, as I have since discovered, not all MXQ's are the same).

Best to wait until an 'Android revert' is available (or confirmed unnecessary), before even installing the correct EmbER build, once it is ready
[Miscellaneous Android Development] RayWalton:
Well Wotzit my response was to charlie_mtl really following his post. It was purely the look of the box that the link he posted that confirmed it was not an M12 metal cased box that the available Ember S805 build is exclusively for. Charlie's box as pictured on the Amazon link is in fact clearly the bigger plastic cased MXQ unit with 4 USB ports rahter than 2 with the smaller better looking M12 box. Charlie's new MXQ box should be okay with the forthcoming EmbER MXQ S805 build, but we have to wait for that to be available as per the EmbER download page.

Anyway some partly good news is that I have discovered my apparently corrupt M12 box at power on bootup was not seriously corrupted at all as if I turn off my Denon X500 AVR unit and back on again then the EmbER KODI screen is displayed and all working now or at least with the nightly new V4 Jarvis build. Also importantly if I connect the HDMI cable direct to my TV set then it shows all the Ember boot up logos as normal. Never had that before with my Denon AVR so I feel that something is not right with the EmbER display handshaking at power on boot up as this problem just does not happen with my M6 boxes nor with any other device I connect to my AVR ???

Also of course still get the 720 res bootup logo screens on a 1080 display so see a small logo picture both the static sponsored one and the second animated one, as was reported bu others here. So that I feel sure must be related to my boot up display problem . Corey or Josh will likely know the cause of this, as they usually do/ Well I hope so else I have to switch my AVR off and back on each time I power on boot up my M12 box, which is far from ideal of course.

---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------

I am getting a major problem with this nightly build as after I set up the short cut icons for Pictures, Videos, Music and Program groups (and of course then EmbER back this up) all is fine with the remote soft reboots but if I power down and back up then I lose all the short cut icons :( Of course I can restore t hem from the EMbER back up I made. Are you also getting that problem?

On a positive note the remote now seems to be mapped okay and all else so far seems to be working well :) other than still my power up boot up display problem mentioned above.

Of course this sort of feedback is exactly what the nightly beta builds are intended for in locating any bugs, but naturally the whole point is that discovered bugs must be reported by us all either here or direct to Josh and/or Corey.
[Miscellaneous Android Development] Russell_S:
Yes the boot logos are still the small ones I originally reported about. I only have the M12 box directly connected to a 1080p TV at the moment so I wasn't aware of the problems it may be causing when connected to an AVR. As a temporary solution rather than having to turn off and back on your Denon could you not just switch the input to another source and back again. If that does work it would be preferable to power cycling the AVR.

I must admit I wasn't even aware that you could put short cut icons on the home screen. Anyway, I have just tested this and I have the same result that the settings are not saved and a hard reboot looses these settings. I have also tested other settings in the 'Skin settings' and it appears that none of them survive a hard reboot. Other 'Appearance' settings appear to be saved correctly and it only appears to be the 'Skin settings' that aren't saved.
[Miscellaneous Android Development] RayWalton:
Thanks Russell and yes just switching the AVR input source to another and back again also brings back the display as of course it should do too. Makes life simpler and less wear on the AVR than power cyucling of course. But hope this problem will be fixed soon anyway.

I have two M12 boxes now one registered with EmbER 4 nightly build and one with a public unregistered EmbER V3.0.1. Both have the same boot up display problem via the AVR. However with 3.0.1 it does retain the Skin Settings with short cut icons okay when you power cycle reboot unlike the new nightly build which loses those Skin settings as we both have found.

Of course V3.0.1 does still have the remote mapping problem so will take a copy of the Nightly build remote.conf file and for now put a copy in the old build's /root/Comfigs/.kodi folder to correct that for now.
[Miscellaneous Android Development] Wotzit:
Nonetheless, still enough confirmation to help me decide not to let my curiosity get the better of me ;)
[Miscellaneous Android Development] robikonobi:
[MENTION=5804734]Josh.5[/MENTION] - I see that nightly builds are starting to become available for certain devices. Are there plans to include atv1200 in those nightly builds? If so when do you think we will begin to see them?
[Miscellaneous Android Development] RayWalton:
Just for info I can confirm that the skin settings with EmbER 4 nightly build now are indeed saved okay. Do not know why this has happened as still on the same build and have changed nothing else. But EmbER 4 beta is running very well indeed now and extensively testing it by using it heavily as my main box.

So IMHO well worth trying out the EmbER 4 nightly beta build, as clearly the more that test it the better of course with plenty of feedback both positive and negative with essential reports of any discovered bugs.

To summarise then, so far the only problem I can see is a minor one with the boot up logo screen at 720 res on a 1080 display so small boot up logo screens. No problem after that, apart from with my Denon X500 AVR which has a problem requiring changing sources and back again to get a display as mentioned before, but all fine with direct to TV HDMI connection of course.
[Miscellaneous Android Development] Russell_S:
Well that's really odd as my skin settings still aren't being saved. I've just checked and it is still on the same nighltly build (4.0.0~nightly_20160420) and there isn't a newer one available. I've just created a shortcut icon on the home page and after a reboot it is gone again.

Everything else though seems to be running great.
[Miscellaneous Android Development] Dru79:
Why I can't upgrade to nightly? I have TLBB v2.
[Miscellaneous Android Development] RayWalton:
That is weird or more weird why mine suddenly started working. Trouble is the changes I was making with reinstalls etc were with my trying to cure the no display problem I had but that was later proved to be purely a problem with my Denon X500 AVR. Somewhere along the line of changes I was making re the display problem, the saving of skin settings must have come good but of course I was not concentrating on that side at the time so no idea what cured that problem.

On a positive note though my old Passthrough problem with the AVR is now cured with this new S805 box but that is likely down to completely different HDMI hardware.

Other than that I love this new box with EmbER 4 nightly, which is working truly superbly. To be honest, in fact overall this M12 with Ember 4 nightly is the best KODI box I have ever had the pleasure to use. So now I am eagerly awaiting the full release of EmbER 4 once Corey and Josh are 100% happy with it.
[Miscellaneous Android Development] Slymobi:
Hello all.

Just wondering about this revert to android option. i have the jarvis box mach10 pure linux version but unsure on which firmware from emberdev site it is classed as ?

Is there a revert to android for this box ?

Also maybe off topic but i thought the best knowledge would come from here.. All of a sudden absolutely no display from any local media or http based media whilst amlogic hardware enabled !! Switching the accelerators off resolves all display issues for all media. Why would this be such a sudden issue as last week using acceleration was working ? using the latest ota update on the mach 10 so i believe it to be Jarvis (16).

regards.

Regards As Always
[Miscellaneous Android Development] Russell_S:
I don't think that there is any firmware versions or revert to Android version on the Ember site that is suitable for your box. The Arnu Box Mach 10 uses the Amlogic S812 Soc whereas the latest stuff on EmbER is for the S805 M12 box.

I have looked on the Arnu Box website and I cannot find any reference to Kodi 16 (Jarvis) being released yet. Are you sure you are on Jarvis. Check what firmware your box is running. Looking on the Arnu Box forums the latest firmware release for the Mach 10 appears to be v3.2.2 which is Kodi 15.2

I have had problems with the S805 box playing back mpeg2 video with hardware acceleration enabled where it plays the audio but no video which sounds the same as you are experiencing. This was with Kodi 15.2, however the update to Jarvis has resolved that issue but the EmbER Jarvis release is still beta at the moment.
[Miscellaneous Android Development] Slymobi:
Ah bloody hell !! Im out so cant check but i think your correct, i think its Isenguard 15.² not Jarvis now :(

Regards As Always
[Miscellaneous Android Development] Russell_S:
Having said that I have just had another look at the Arnu Box forum and there is a banner at the top of the forum stating:

However, I couldn't find any download link for it or any information on when it was released. So it is possible that you were correct and your box is on Jarvis.

In order to revert your box to Android I think you need to return it to Arnu Box because they do not provide any way for the end user to do it themselves. Obviously you then need to take shipping costs into consideration to decide if it is worth it. However, from personal experience, I think you will be dissapointed if you go back to Android on your box. I have recently purchased an M12 S805 Android box and I really couldn't wait to install EmbER onto it because it runs just so much better.

When you get the opertunity, check what firmware version your box is on and if it is 3.2.2 then see if there is an OTA update to 3.3.0 and try that.

Alternatively, just get a cheap M12 box from eBay or Aliexpress and put EmbER on it.

Good luck
[Miscellaneous Android Development] t3al:
Hi there, I'm having the same issue as the guy you quoted last year. I got this MX Box (g18ref) from a friend a couple of days ago. The first time I tried flashing EmbER was through a USB. All good, boots up to first time setup, but no mouse pointer (I don't have the remote). So I reverted back to the stock firmware using the method from chinagadgetsreviews, and tried again to flash EmbER through an SD card, but still there is no mouse. I'm using the Generic E-M6 download.

Is this something to be expected or can I do something?
[Miscellaneous Android Development] Slymobi:
Ok im on 3.3.0 jarvis lol. i have reasons to want android as this openelec ember is good but its too locked down for me amongst other things. Android gives me possibilities via apks over openelec for personal requirements. I got the box as a gift so its holding only sentimental reasons as to why to keep it hence why id really wish to be able to do the revert and not change device totally. Thanks for replys.

Regards As Always
[Miscellaneous Android Development] DancesWithChickens:
TLBBv2 has ARM Cortex A9, Amlogic 8726-M6.
[Miscellaneous Android Development] john3voltas:
Hi. I've been waiting for compatibility with Tronsmart Prometheus (Vissontech ATV-106) before I go premium.

Any news on this? Because last time I checked the github it said WIP and I wouldn't want to risk (again) bricking the tv box.

Thanks
[Miscellaneous Android Development] RayWalton:
The remote.conf with the latest EmbER 4 S805 nightly build as you guys will know is working well but with one major exception that was there before too With EmbER 3.0.1 as well. That problem is the remote button repeat timing is way too fast, as it is often very difficult not to record two (or more) key presses when you only intended to make a single button press.

This does becomes somewhat of a nuisance and in the end very annoying, making remote operated on-screen navigation far more difficult than it need be. Sure you soon get used to using very quick jabs on the remote buttons but it does need fixing.

Will try and take a look at fixing that but if anyone here has the time and better know how than I, then can they help with this ?? Of course it may be a parameter that is fixed within the remote unit itself which will require a factory change. If a hardware problem then that would manifest itself with default Android operations too so anyone here with one of these Metal cased MXQ M12 boxes still with default Android finding the button presses are too rapidly repeated as referred to above ??
[Miscellaneous Android Development] dartsma:
Are the g02ref boxs still going to be included in the updates
[Miscellaneous Android Development] RayWalton:
Yes I am informed that they will be dartsma. I do know though that these boxes are the cause of the delay in rolling out EmbER 4 However, yes they will be supported, and I am certain that you will get EmbER4 with Jarvis with an OTA update in the near future, of course only for those who have subscribed and activated to the Donor Edition (DE)of EmbER of course.

So there is really no reason why you should delay in going ahead and donating and activating your EmbER firmware to the full DE version. After all there is really no excuse IMHO at just a US$10 or more donation needed to update to DE.