Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
[ROM] Unofficial OpenELEC for MXIII-G & Tronsmart MXIII+
Collapse
X
-
Originally posted by vn800art View Post
-
Pls pls don't do that and wait I explain shortly and edit this msg!
So, read well msg 226 mine', 229 wilro' and msg from the page previous to this! Wilro has not yet updated instructions for the new aml.autoscript method.
Wait
Read this page msg. from Mr. KSZAQ!http://freaktab.com/forum/tv-player-...nd-mxq/page139
Now I think You can tell me if You have device like mine and that you want to keep android 4.4 on nand and install OE on SdcardLast edited by vn800art; 02 March 2016, 19:57.
Comment
-
Originally posted by vn800art View PostPls pls don't do that and wait I explain shortly and edit this msg!
So, read well msg 226 mine', 229 wilro' and msg from the page previous to this! Wilro has not yet updated instructions for the new aml.autoscript method.
Wait
Read this page msg. from Mr. KSZAQ!http://freaktab.com/forum/tv-player-...nd-mxq/page139
Now I think You can tell me if You have device like mine and that you want to keep android 4.4 on nand and install OE on Sdcard
Comment
-
Originally posted by t0mekk View PostThanks for this, but it have a bug. On pvr iptv simple client, the client doesnt show channel categories...i see there is same bug on codesnake release, so probably something wrong in openelec addons..
Originally posted by t0mekk View PostHello, i tried this lateet and kszaq, in kszaq hdmi cec working..on this one not..anybody with same problem?
It seems that the OE team have skipped over 6.0.2 (now at 6.0.3!), & there is mention of cec with LG TV's (My samsung TV works fine) - I will be putting up another test build shortly.
Still testing OE6.0.3, as I'm not happy with the wifi stability in this build - Wifi appears a lot more stable in the test builds, so I'm going to try kodi 15 on top of it to see if the problem is related to kodi 15 or my OE6 build environment.
FWIW: My MXQ & mk808b+ devices are back to running kszaq's 5.95.5.2 build, as the newer builds appear less stable in my environment
Comment
-
Originally posted by vn800art View PostFirst report: MXIII Plus ( old Beelink model ) => SUCCESS ( for the large part ): 6.0.1A ! All networks working, blazing fast! BT turns on but doesn't find anything. Remote works only for resume from stand by - light on the device remains BLUE even if OE has shut down ( no Red light doh ! ). I charge a large wizard and system is snappier than my NVIDIA SATV ! As I had used aml.script for the previous test, recovery refused to work this time ( no usb working, mose and Logitech k400 dead ! ), so I unplugged and replugged AC, OE started after the second boot ( just like the first time with release 6.0.1e and toothpick method working ! ).
Coming back soon !
Edit 1 : 6.0.1D: no WiFi, no BT working as before, remote works only as before, light becomes RED if in suspend !
More to come
Edit 2: 7 devel from 1/3 ( today !) only Ethernet working ( well, must say ), no Wifi, Bluetooth works and hold connection, but I haven't find a way to make it play from TV loudspeakers or send smtg outside ! Stock remote work as before, RED light comes out when shut off.
Edit 2/a : I have seen You put aml.autoscript in the file, but OE booted without toothpick method!
Thanks again for Your work, Wilro !
If You want me to check something I can test in the mornings ( Central European time, btw ) , much easyer than in the afternoons !
Alessandro
What's really curious is BT working but NOT wifi in the test build (same chip controls both functions, & my wifi is far more stable in the test build!) - Bluetooth+OE in general is quite limited on these devices, as originally, the only way to get it to work was to lose all audio pass-thru capabilities - Having the ability to at least output audio to a headset now is a nice improvement on this situation
The led issue is also really strange, although it did take a fair bit of effort to get consistant behaviour for the MXIII-G with the newer kernel's. (My all black MXQ's refuse to turn the led red, but then, the original android firmware didn't either, so I'm not that fussed
I will have a bit more of a poke around to see if I can find out which wifi options could possibly stop it from working in the newer builds...
Comment
-
I must then ask people and You Wilro to excuse me, but me and cvo123 will stop I think briefly to be OT on here, but, as I told im my msg, newer sd installation procedure is so simple that one barely understand something is happening and is cross device ( my experience ) and build compliant ( Kszaq words) starting from release 6.0.0.0 ( if I remember well ). So, I will copy and paste Kszaq word for sdcard installation and add my experience with aml.autoscript : QUOTE- I'm testing a new method of updating uenv variables that won't need flashing, one time toothpick and you'll be good to go. To try it, download this file and unpack it to SD card. You should have three files: kernel.img, SYSTEM and aml_autoscript. Delete any other files if they are present. With card made that way inserted, use a toothpick ou have to have only two files method to power on the box. It should boot straight to OpenELEC. Toothpick is only needed for a first boot.
Yes, it worked!
I add the new aml_autoscript file to 6.0.1.3 files and boot with toothpick method and instantly I am booting in OpenElec
Wifi works flawless with my RTL8723BS also!
Thanks kszaq for your hard work and four your patience with newbies like me.
UNQUOTE
To arrive to this point you know you have to use Wilro build nr. 6.0.1.A ( see my test ) with the end of the file description named img.gz . You have to use some tool to extract the image from that zip ( I use winrar ) then you have to write the extracted image on a fresh formatted microsd hc or better, but class 10 to assure speed. To do this you use win32disk imager. After this tool has done its work ( be carefull, check your correct drive to write to ( your sdcard inserted in the PC ), you check if in there there are 5 files ( as in the old risky business procedure!!!! ), you have to take off everything ( recovery, factory update param, OE Bootloader if any [or dualboot bootloader]), leaving only Kernel and Sistem files. To this card that you have burnt you will extract the aml.autoscript , so in the end you have three files ( in the test build 7 freshly published from Wilro, in the img.gz file once extracted and burnt on a sdcard, You will find three files as I said, You can take aml.autoscript from there and put it in the release 6.0.1A, once you have burned it to the card, taking out the other files I mentioned ) . Disconnect device from mains, take the card, insert in the little slot on device, take a cotton fioc ( for girl's use ) cut one end taking off the part covered with cotton, keep button inside AV port pressed, insert mains, press the button to switch on, continue to keep cotton fioc pressed inside till you see the great red circle with the B ( eelink ! @"$%& ), release the cotton fioc. You must wait the magic happen now !
Let us know
Thanks for your patience, my friends and Wilro !
AlessandroLast edited by vn800art; 03 March 2016, 08:00.
Comment
-
Well wilro_6276 , thanks for your time ! I will try to test more ( starting without ethernet connected ? disconnect ethernet while connected ? ) and report back. I have red something about correct remote behaviour in setting device ON depend on bootloader ( which in my case is correct BUT the light remains blue ! even if shutoff ) the important part is all the three main connections working ! Will try to fix remote config, too !
Regards
Alessandro
Comment
-
[QUOTE=wilro_6276;n558431]
I have had a look at the sample you sent me, & unfortunately it does appear to be a problem upstream (Either in OE or kodi, I'm not sure - doesn't worked on any of my OE 6/7 based boxes)
Thanks, the problem is sure in OE, cus ive tried almost all firmwares. In firmwares which pvr addon is not from OE the categories are working...but other problem is that i have a stutterin problem on live tv channels...anyway, slowly and this will be perfectthanks
Comment
-
Howdy All,
I have uploaded build "6.0.3a" (1st post), & a new test build HERE
These are based off codesnake's Febuary kernel release, with various patches required to allow our little box to behave- Openelec 7.0 is approaching feature freeze, so we will hopefully start seeing 6.95.x releases shortly. This development release is already better in a lot of ways on this box than OE6 - Kodi 16 in particular appears a lot smoother overall (sadly, I'm sure we're going to see more addon breakages initially, various regressions due to it's freshness, but for myself, the smoother/consistant behaviour trumps that
Enjoy!
Comment
-
Originally posted by slippery49 View Posttoothpick install on 6.0.3a link no go
had to use
thanks for the great work
Comment
-
Originally posted by vn800art View PostI must then ask people and You Wilro to excuse me, but me and cvo123 will stop I think briefly to be OT on here, but, as I told im my msg, newer sd installation procedure is so simple that one barely understand something is happening and is cross device ( my experience ) and build compliant ( Kszaq words) starting from release 6.0.0.0 ( if I remember well ). So, I will copy and paste Kszaq word for sdcard installation and add my experience with aml.autoscript : QUOTE- I'm testing a new method of updating uenv variables that won't need flashing, one time toothpick and you'll be good to go. To try it, download this file and unpack it to SD card. You should have three files: kernel.img, SYSTEM and aml_autoscript. Delete any other files if they are present. With card made that way inserted, use a toothpick ou have to have only two files method to power on the box. It should boot straight to OpenELEC. Toothpick is only needed for a first boot.
Yes, it worked!
I add the new aml_autoscript file to 6.0.1.3 files and boot with toothpick method and instantly I am booting in OpenElec
Wifi works flawless with my RTL8723BS also!
Thanks kszaq for your hard work and four your patience with newbies like me.
UNQUOTE
To arrive to this point you know you have to use Wilro build nr. 6.0.1.A ( see my test ) with the end of the file description named img.gz . You have to use some tool to extract the image from that zip ( I use winrar ) then you have to write the extracted image on a fresh formatted microsd hc or better, but class 10 to assure speed. To do this you use win32disk imager. After this tool has done its work ( be carefull, check your correct drive to write to ( your sdcard inserted in the PC ), you check if in there there are 5 files ( as in the old risky business procedure!!!! ), you have to take off everything ( recovery, factory update param, OE Bootloader if any [or dualboot bootloader]), leaving only Kernel and Sistem files. To this card that you have burnt you will extract the aml.autoscript , so in the end you have three files ( in the test build 7 freshly published from Wilro, in the img.gz file once extracted and burnt on a sdcard, You will find three files as I said, You can take aml.autoscript from there and put it in the release 6.0.1A, once you have burned it to the card, taking out the other files I mentioned ) . Disconnect device from mains, take the card, insert in the little slot on device, take a cotton fioc ( for girl's use ) cut one end taking off the part covered with cotton, keep button inside AV port pressed, insert mains, press the button to switch on, continue to keep cotton fioc pressed inside till you see the great red circle with the B ( eelink ! @"$%& ), release the cotton fioc. You must wait the magic happen now !
Let us know
Thanks for your patience, my friends and Wilro !
Alessandro
By the way, can I install any internet browser in OE? Thanks
Comment
What's Going On
Collapse
There are currently 2616 users online. 4 members and 2612 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment