[NEW] Beelink M18 Amlogic S905 4K 2G/16G TV BOX - Android Stick & Console AMLogic based Computers

Specifications
Beelink M18 Amlogic S905 4K 2G/16G TV BOX 2.4G/5G Dual Band WIFI 1000M LAN Bluetooth4.0 HDMI2.0 H.265 Miracast DLNA
Android 5.1
Amlogic S905 Quad-core 64-bit ARM Cortex-A53 up to 2GHz
Penta-core ARM Mali-450
DDR3 2GB
eMMC Flash 16GB
IEEE 802.11a/b/g/n,2.4G+5.8G
Ethernet 1000M
Bluetooth 4.0
UHD 4K*2K
Standard HDMI 2.0
Miracast DLNA support
Original Firmwares
105L1
Download Android Lollipop 5.1.1 stock firmware from here, here or here.
Firmware details:
Archive name: MX64_105L1
Image: MX64_105L1.img
Archive file size: 331 MB
Platform: AMLogic S905
Custom Recovery
TWRP Recovery 3.0.2-0 for Beelink_ M18_MX64
Code:
[B][U]Steps to install twrp 3.0.2-0:[/U][/B]
[B][U]Option 1: Running from sdcard or USB device.[/U][/B]
1. First download TWRP files from [URL="https://yadi.sk/d/q0Wi2QiLrNbRT"]here[/URL]
2. Extract files to SDCARD or USB
3. Place [B]recovery.img[/B] from [B]TWRP_3.0.2-0_Beelink_M18_MX64_SDcard_USB[/B] folder on SDCARD or USB's root
4. Power off Beelink M18 and insert a pin/clip inside your earphone plug as to push reset button (you ear a *click* sound)
5. Power On Beelink M18 while pressing reset button for about 5/10 seconds
6. TWRP will be launched.
[B][U]Option 2: Install TWRP into device's recovery partition:[/U][/B]
1. Follow Option 1. steps
2. Swipe right to enable system modifications.
3. Press "Install" button and select [B]recovery.img[/B] from [B]TWRP_Recovery_3.0.2-0_Beelink_ M18_MX64[/B] folder. Beware not to choose recovery.img from SDCARD or USB's root!!!
4. Select install into /recovery partition
5. Wait until process is finished.
6. Done!
Custom ROMs
Full 107L Firmware Backup for TWRP_3.0.2-0 working with FOTA
Finless 1.0 ROM for S95 Meta - Final for M18/MX64
OpenELEC 7.0
Firmware M18-MX64_Minix_NEO_U1_FW_007_TWRP
Firmware Port_Minix_U1_FW12_20170227_for_Beelink_M18
Code:
[B][U]Steps to install any TWRP Full ROM Backup using TWRP Restore Option:[/U][/B]
To start from removable devices / micro SD cards (connect without using USB hubs, if recovery does not load - change the media):
1. format micro SD card / USB stick in [B]Fat32 file format[/B];
2. copy [B]recovery.img[/B] file and [B]Full ROM Backup[/B] to media root, making sure you keep its file structure: [HIDE]i.e.: (\TWRP\BACKUPS\Amlogic\Port_Minix_U1_FW12_20170227_for_Beelink_M18_TWRP_Backup\)[/HIDE]
3. disconnect power supply from the box;
4. press and hold the "[B]recovery[/B]" button through the hole on the bottom of the box and while pressing recovery button connect power supply
5. Release "recovery" button after[B] 10 seconds[/B]
6. TWRP Recovery should start
7. First step needed is a Factory Reset. You’ll have to Wipe with the following options:
[CODE]- Dalvik / ART cache
- Cache
- System
- Data
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Go back to Main Menu and press "Restore" button and select your SDCARD or USB as the restore source.
9. TWRP detects the ROM's full backup and you just have to select it and swipe right to restore it.
10. Wait until process is finished.
11. Done! Enjoy[/CODE]
DISCLAIMER:
These links are only a compilation of useful information regarding this TV Box.
I'm not to blame if you brick your device. I'm not responsible for any content in this post!

---

This is a fantastic box - great spec. Although referred to as Beelink M18 there is no sign on the device that it is made by Beelink.
Full of the usual junk & rubbish when booted, but very fast! Comes with latest firmware, rooted & Kodi 16.1.

---

Have you tried any custom rom?
sent from my Nexus 4

---

Hi,
I have this box bought on GreaBest website. The first I received was defect and crashed every 5 mins of usage (no idea why). I keep it and for some euros more I got a second one that it is OK.
The powerful of this box is very impressive. Fast as a standard phone for a cheap price. The defect one is now working with the CPU locked to 1,3Ghz max but is slower.
Sometimes I get some crash but it's quite OK. I want to integrate this box in my car as car PC.
I replaced the standard TV launcher by nova by I have a main issue: The background tasks are always killed. I can't keep Waze or Google play music running in background. I try to understand why it doesn't behave as a standard tablet but I have not yet the answer. If somebody can hepl me!

---

ed_bracam said:
Hi,
I have this box bought on GreaBest website. The first I received was defect and crashed every 5 mins of usage (no idea why). I keep it and for some euros more I got a second one that it is OK.
The powerful of this box is very impressive. Fast as a standard phone for a cheap price. The defect one is now working with the CPU locked to 1,3Ghz max but is slower.
Sometimes I get some crash but it's quite OK. I want to integrate this box in my car as car PC.
I replaced the standard TV launcher by nova by I have a main issue: The background tasks are always killed. I can't keep Waze or Google play music running in background. I try to understand why it doesn't behave as a standard tablet but I have not yet the answer. If somebody can hepl me!
Click to expand...
Click to collapse
I've another box with the same issue. I don't know why there is no multitasking.

---

Are you sure that apps are not running at all?
Are you using any widget on nova launcher to show running apps? It could be some kind of sync problem between the OS and perhaps a widget?

---

redglory said:
Are you sure that apps are not running at all?
Are you using any widget on nova launcher to show running apps? It could be some kind of sync problem between the OS and perhaps a widget?
Click to expand...
Click to collapse
I don't know but when I'm using Waze or Google play music, if I use home key, the application is stopped (deseappear from the tray).
Another issue is the TV box virtual button style. I want to increase the DPI of the interface (to display on a 6,5 inch Car display in 800x480) and the standard android TV doesn't work on more than 190dpi. I would like to have a simple one.

---

ed_bracam said:
I don't know but when I'm using Waze or Google play music, if I use home key, the application is stopped (deseappear from the tray).
Another issue is the TV box virtual button style. I want to increase the DPI of the interface (to display on a 6,5 inch Car display in 800x480) and the standard android TV doesn't work on more than 190dpi. I would like to have a simple one.
Click to expand...
Click to collapse
Can you check if they are running? try this
For the DPI settings if you are rooted:
Code:
Method I – Do it from the phone on a Rooted ROM
1. Open Root Explorer.
2. Go to /system
3. Click on Mount RW (It should appear as Mount RO, that’s when it is correct!)
4. Look for build.prop. Long press on the file and press Open file in Editor
5. Scroll down to ro.sf.lcd_density=240
6. Change the value to anywhere between 180 and 240. The lower the value, the higher density your screen will have.
7. Click on the Menu button, and Save and Exit.
8. Reboot.
Method II – Before flashing a Custom ROM (Including AOSP ROMs for your phone)
1. Open the zip file containing the custom ROM.
2. Navigate to System Folder, then extract build.prop to your Desktop.
3. Edit the file using Notepad or EditPad or Notepad++
4. Click Ctrl + F(Search) and enter ‘ro.sf.lcd_density’ or navigate to this line.
5. Change the value to your desired (Higher Value = Bigger font and lower density, Lower Value = Higher Density and smaller font)
6. Save the build.prop file and replace back into the zip file in the same place.
7. Flash the Custom ROM as per directions.

---

redglory said:
Can you check if they are running? try this
For the DPI settings if you are rooted:
Code:
Method I – Do it from the phone on a Rooted ROM
1. Open Root Explorer.
2. Go to /system
3. Click on Mount RW (It should appear as Mount RO, that’s when it is correct!)
4. Look for build.prop. Long press on the file and press Open file in Editor
5. Scroll down to ro.sf.lcd_density=240
6. Change the value to anywhere between 180 and 240. The lower the value, the higher density your screen will have.
7. Click on the Menu button, and Save and Exit.
8. Reboot.
Method II – Before flashing a Custom ROM (Including AOSP ROMs for your phone)
1. Open the zip file containing the custom ROM.
2. Navigate to System Folder, then extract build.prop to your Desktop.
3. Edit the file using Notepad or EditPad or Notepad++
4. Click Ctrl + F(Search) and enter ‘ro.sf.lcd_density’ or navigate to this line.
5. Change the value to your desired (Higher Value = Bigger font and lower density, Lower Value = Higher Density and smaller font)
6. Save the build.prop file and replace back into the zip file in the same place.
7. Flash the Custom ROM as per directions.
Click to expand...
Click to collapse
I just checked, the application is not anymore in memory. Killed by the go to home function. How is it possible!!??
I checked with google launcher. Same issue
For the DPI, I use a DPI changer application from the market that works great. And I can confim you the softkey ribbon is not working properly with a DPI equal or more than 200. The ribbon goes to the left side and a part of the screen is not usable anymore. Reboot needed. 190dpi is OK.
I want to simplify it removinf some buttons, it should help.
But the home button killing applications is my real problem

---

I don't know... Have you installed any memory management app?
sent from my Nexus 4

---

redglory said:
I don't know... Have you installed any memory management app?
sent from my Nexus 4
Click to expand...
Click to collapse
No it's from fresh installed. I have many Android phones at home and I never seen a home button that kill the current application. It's a nightmare. Is some other user of the M18 stock firmware can confirm?
I can't see how to stop that. if you swith the current application with the recent app or back button, it stay in background but not with home button. which stupid code they put in this function!!!!!

---

Try a custom debloated rom. Perhaps it might help
sent from my Nexus 4

---

redglory said:
Try a custom debloated rom. Perhaps it might help
sent from my Nexus 4
Click to expand...
Click to collapse
There is not plenty of rom today for the M18. Most a in non english forums.
For my usage I could be satisfied by a AOSP version

---

On the original post i've linked some to the 4pda ROMs and how to's
sent from my Nexus 4

---

A logcat to understand better
Code:
06-08 14:53:11.239 D/WAZE ( 6781): in updateNavResultPopup eta=19 dist=null unit=null
06-08 14:53:11.994 I/ActivityManager( 3167): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.teslacoilsw.launcher/.NovaLauncher} from uid 1000 on display 0
06-08 14:53:12.060 W/WAZE ( 6781): MapView onPause
06-08 14:53:12.060 D/WAZE NTV RENDERER( 6781): onViewSurfaceDestroyed: [ Main Canvas ]. Event: UISurfaceEvent. Type: CHANGED. Frame id: 1 . Shutting down: false UISurfaceEvent. Type: CHANGED. Frame id: 1
06-08 14:53:12.063 D/WAZE NTV RENDERER( 6781): Going to run destroy event. Created: true
06-08 14:53:12.095 D/WAZE NTV RENDERER( 6781): Finished to run destroy event
06-08 14:53:12.095 D/WAZE NTV RENDERER( 6781): Finished onViewSurfaceDestroyed
06-08 14:53:12.143 W/IInputConnectionWrapper( 6781): showStatusIcon on inactive InputConnection
06-08 14:53:12.181 D/WAZE NTV RENDERER( 6781): onViewSurfaceDestroyed: [ Main Canvas ]. Event: UISurfaceEvent. Type: DESTROYED. Frame id: 1 . Shutting down: false UISurfaceEvent. Type: DESTROYED. Frame id: 1
06-08 14:53:12.237 I/RemoteControlService( 3407): NEW NOTIF FROM (Listener Service):com.waze
06-08 14:53:12.241 I/RemoteControlService( 3407): NEW NOTIF FROM (Listener Service):com.waze
06-08 14:53:12.531 I/ActivityManager( 3167): Force stopping com.waze appid=10069 user=0: from pid 3167
06-08 14:53:12.532 I/ActivityManager( 3167): Killing 6781:com.waze/u0a69 (adj 2): stop com.waze
06-08 14:53:12.651 W/InputDispatcher( 3167): channel '1225a39f com.waze/com.waze.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
06-08 14:53:12.651 E/InputDispatcher( 3167): channel '1225a39f com.waze/com.waze.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 14:53:12.655 I/WindowState( 3167): WIN DEATH: Window{1225a39f u0 com.waze/com.waze.MainActivity}
As I see:
- Waze is running
- the system catch home button
- Waze goes in backgroung
- ActivityManager decide: I want to kill it
- Waze is dead
I googled it and it look like a saving power managdement behaviour ???? But there is no power management in this box

---

ed_bracam said:
A logcat to understand better
Code:
06-08 14:53:11.239 D/WAZE ( 6781): in updateNavResultPopup eta=19 dist=null unit=null
06-08 14:53:11.994 I/ActivityManager( 3167): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.teslacoilsw.launcher/.NovaLauncher} from uid 1000 on display 0
06-08 14:53:12.060 W/WAZE ( 6781): MapView onPause
06-08 14:53:12.060 D/WAZE NTV RENDERER( 6781): onViewSurfaceDestroyed: [ Main Canvas ]. Event: UISurfaceEvent. Type: CHANGED. Frame id: 1 . Shutting down: false UISurfaceEvent. Type: CHANGED. Frame id: 1
06-08 14:53:12.063 D/WAZE NTV RENDERER( 6781): Going to run destroy event. Created: true
06-08 14:53:12.095 D/WAZE NTV RENDERER( 6781): Finished to run destroy event
06-08 14:53:12.095 D/WAZE NTV RENDERER( 6781): Finished onViewSurfaceDestroyed
06-08 14:53:12.143 W/IInputConnectionWrapper( 6781): showStatusIcon on inactive InputConnection
06-08 14:53:12.181 D/WAZE NTV RENDERER( 6781): onViewSurfaceDestroyed: [ Main Canvas ]. Event: UISurfaceEvent. Type: DESTROYED. Frame id: 1 . Shutting down: false UISurfaceEvent. Type: DESTROYED. Frame id: 1
06-08 14:53:12.237 I/RemoteControlService( 3407): NEW NOTIF FROM (Listener Service):com.waze
06-08 14:53:12.241 I/RemoteControlService( 3407): NEW NOTIF FROM (Listener Service):com.waze
06-08 14:53:12.531 I/ActivityManager( 3167): Force stopping com.waze appid=10069 user=0: from pid 3167
06-08 14:53:12.532 I/ActivityManager( 3167): Killing 6781:com.waze/u0a69 (adj 2): stop com.waze
06-08 14:53:12.651 W/InputDispatcher( 3167): channel '1225a39f com.waze/com.waze.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
06-08 14:53:12.651 E/InputDispatcher( 3167): channel '1225a39f com.waze/com.waze.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 14:53:12.655 I/WindowState( 3167): WIN DEATH: Window{1225a39f u0 com.waze/com.waze.MainActivity}
As I see:
- Waze is running
- the system catch home button
- Waze goes in backgroung
- ActivityManager decide: I want to kill it
- Waze is dead
I googled it and it look like a saving power managdement behaviour ???? But there is no power management in this box
Click to expand...
Click to collapse
I've also searched a bit and found some opinions towards that behaviour.
I've received mine today and I've installed twrp and the finless 1.0 ROM and tried to execute some apps and hit home button. I still have apps running as expected...
One problem... I tried to install Waze and it says my device is not compatible...

---

Hi, it is nice to find a place where we can talk about this box...
I recieved my Beelink M18 a couple days ago and I've tested it and found some frame jumps in Youtube app playing 720p or 1080p videos... They also appear on Kodi at almost every videos I play. The videos don't play smoothly at all... I have HDMI self-adaption turned on and screen resolution at 1080p/60Hz. This kind of things also happens to any of you? Or it is just my unit?
Do you recomend any of the firmwares presented above in order to solve this problem I have? Have you tried any of them?
Thanks for your support!!!

---

I've just installed Finless 1.0 port.
But i didn't have time to test much. Tomorrow i'll give it a try
sent from my Nexus 4

---

redglory said:
I've also searched a bit and found some opinions towards that behaviour.
I've received mine today and I've installed twrp and the finless 1.0 ROM and tried to execute some apps and hit home button. I still have apps running as expected...
One problem... I tried to install Waze and it says my device is not compatible...
Click to expand...
Click to collapse
I use market helper app to get it recognised as a Nexus 7 by the market.
Can you try with google play music app? If it stays in background when press home?
If it works, I will change rom soon
Thanks for your help
Sent from my D5803 using XDA-Developers mobile app

---

Yupp i'll spoof my M18 which now is spoofed as a tromsmart vega 95 to be a nexus 10 and i'll give it a try when i get home.
sent from my Nexus 4