{
"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"
}
Release notes
This build includes a totally new kernel and Amlogic code based on their latest SDK, and I took the chance to get rid of Amlogic DVB drivers and use those from WeTek Play's OpenELEC build; by doing this I am able to run DVBAPI apps like Tvheadend.
Kodi Live TV support under Android was one of the most requested features, this experimental build allows you to run Kitkat (CyanogenMOD 11) or Lollipop (CyanogenMOD 12 or Android TV) and Kodi Live TV (WeTek Theater is no longer supported with the provided drivers).
The new 3.10 kernel brings OMX support as well (Android libstagefright media decoding), while Amlogic's prebuilt libraries work very good on KitKat they don't work at all with Lollipop.
Just to be sure to have a good media experience use Kodi, at the end of the post you will find latest stable official Kodi packed in a flashable zip and in the second post you will find a link to a modified version that should give a better experience on the WeTek device.
Now I will give you some details on how to configure Tvheadend, if you already know what to do you can skip this section.
Tvheadend will run automatically at boot and you can access to it from a web browser (even from a different device, you are not forced to do it from the box) at http://wetek_ip_address:9981
From this WebUI click "Configuration" -> "DVB Inputs" -> "Networks" and add a new Network according to the type of tuner you have (for example I created a DVB-S network called "Hotbird" and assigned the E13.0 pre-defined muxes, just pay attention that they are not bleeding edge updated so if you don't find a channel you might have to insert manually the transponder by looking at frequencies on sites like kingofsat or lyngsat).
After that go to "TV Adapters", click the link with a folder icon showing your adapter's name (if you're running the dual DVB-S2 tuner you will see two of them, #1 is the input closer to the edge of the box, while #0 the one closer to the rear usb ports), and click "Enabled", configure the eventual parameters (DiseqC, Unicable, etc.) and save the settings.
Go to the option right under the adapter name, assign it to the network that you have created and configure the eventual parameters.
Now go back to "Networks", after a couple of minutes you should see the "Scan Q length" lowering its value, when in reaches 0 everything has been scanned and you can proceed mapping the channels from "Services" section.
For further instructions, here you can find a tutorial to show you how to configure the DVB-T/C tuner, and here one for the DVB-S tuner.
Before leaving the configuration go to "Recordings" and set a "Recording System Path" pointing it to your external storage (on my roms it will be "/storage/sdcard1" for the MicroSD, "/storage/usbdisk0" for the lower rear usb port, "/storage/usbdisk1" for the upper rear usb port and "/storage/usbdisk2" for the side usb port).
Not doing that will drive Kodi's Tvheadend client plugin crazy trying to determine the available space for recordings.
Now you can launch Kodi, go to its settings, enable Live TV and select the "Tvheadend backend".
Remember that this is still something EXPERIMENTAL
Like the other Lollipop buils, remember, this is not a bug, but a consequence of the switch to art from dalvik: first boot, updates and apps installation will take longer; this happens because art compiles the apk and does not work like dalvik that was using a just-in-time approach (so expect almost 10 minutes for the first boot and future upgrades)
First install instructions
* As really first thing get this CWM recovery, unrar it and copy "recovery.img" to a MicroSD.
* Power off your device and unplug the AC power cord.
* Get the latest available ROM and GAPPS version from the links below and copy them to a MicroSD card.
* Now insert the MicroSD card in your STB.
* Plug the AC power cord while you keep pressed the little reset pinhole (located on the bottom of the device) for 10 seconds (just count slowly to ten and it will be good).
* Once the device has booted to recovery perform a factory reset and flash the ROM's zip for first followed by the GAPPS zip.
* Reboot and enjoy CyanogenMOD.
Update instructions
* If you're coming from the "regular", not "experimental" builds, please follow the "First install instructions"
* Get the latest available ROM and GAPPS version from the links below and copy them to a MicroSD card.
* Now insert the MicroSD card in your STB.
* Enable "Developer options" following this tutorial and from it enable the "Reboot to recovery" option.
* Bring up power menu by keeping pressed the power button on the STB for a couple of seconds (or pushing F4 if you have a keyboard plugged in) and select "Reboot -> recovery".
* Once the device has booted to recovery flash the ROM's zip for first followed by the GAPPS zip.
* Reboot and enjoy your updated CyanogenMOD.
Downloads
* ROM (CM12) 2015-03-20
* GAPPS 2015-01-07 (LITE)
* ROM (Android TV) 2015-03-20
* GAPPS (Android TV) 2015-01-30
* ROM (CM11) 2015-04-06 - Real 1080p output (r1)
* GAPPS 2014-06-06 (LITE)
* Kodi 14.1 "Preinstall"
Misc tips
* If you wanna start Kodi at boot go to "Developer options" and enable the last entry called "Start Kodi at boot"
* There are some keyboard shortcuts: F1 (Home), F2 (Menu), F3 (App switch) and F4 (Power menu) and some CEC remote shortcuts: Red (Power off the device), Green (Home), Yellow (Menu) and Blue (Search).
* By enabling "Google remote support" in "Other" section of "Network" configuration you will be able to control your device from your Android smartphone / tablet by using this app on it.
* When an app forces the portrait orientation, the default behavior is to simulate a portrait / phone-like UI adding black bars to the sides (an example is Antutu when it runs the benchmark, or Box.com). If you prefer to have a landscape stretched UI flash this zip. To revert to the default behavior flash this one instead.
Note that the setting will persist even if you upgrade the ROM so you have to flash that zip only once.
* Once you have configured your OSCam reader, set-up Tvheadend this way.
Real 1080p output (optional zip for CM11)
On Android Amlogic MX SOC uses a 1280x720 framebuffer coupled with a scaler to do the up/down scaling.
They did it for a good reason, 720p resolution has half the pixels of the 1080p one so the UI will be snappier and 3D performance will be better but if you don't care about that and you just wanna the best image quality (I noticed the scaler gives me a weird motion when watching sports) you can flash that optional zip.
Once flashed if you wanna change resolution go to Android Display settings, set your resolution and reboot the device (this step is required because some stuff has to be set at boot because Android is not meant to change resolution while it's running).
I didn't do it for Lollipop builds because it runs already slower than Kitkat, adding this mod might be too much
Since you have this option (WeTek Play is the only MX device that allows you to do that) I would give it a try, if you have a good TV set you will clearly see the difference.
Kodi 14.2 WeTek_mod_v1
This is a Kodi build that includes some patches not included upstream that will improve (hopefully) your overall experience.
Since it's been signed with different keys respect those from Kodi build server you won't be able to install it over the older Kodi but you'll have to uninstall it.
Take a backup of /sdcard/Android/data/org.xbmc.kodi folder before uninstalling or Android will delete it and you'll lose your configuration; restore it after installing the new APK.
Download
You can use OE's /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<advancedsettings>
<network>
<cachemembuffersize>20971520</cachemembuffersize>
</network>
<samba>
<clienttimeout>30</clienttimeout>
</samba>
<network>
<readbufferfactor>4.0</readbufferfactor>
</network>
<pvr>
<minvideocachelevel>5</minvideocachelevel>
<minaudiocachelevel>20</minaudiocachelevel>
</pvr>
</advancedsettings>
or (this is what I'm using)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<advancedsettings>
<network>
<buffermode>1</buffermode>
<cachemembuffersize>31457280</cachemembuffersize>
<readbufferfactor>10</readbufferfactor>
</network>
<gui>
<algorithmdirtyregions>0</algorithmdirtyregions>
</gui>
</advancedsettings>
External disk spindown for WeTek Play
Flash this zip from recovery, once booted to android use a root capable file explorer (like Solid Explorer for example) and edit "/system/etc/spindown.conf" to fit your needs.
The default configuration is set-up to spin down "sda" disk after 3600 seconds (60 minutes) using sg3-tools.
You don't need to flash the zip again if you do a rom update because I've added the addon.d backup script.
Note: your drive have to ne able to be set to sleep using "sg_start --stop /dev/block/$disk", I've tried it with 3 drives, 2 WDs and 1 Seagate and it worked.
Debian chroot
As very first thing you have to set-up a MicroSD card with two primary partitions, the first one must be formatted in FAT32, the second one can be left unformatted because the "sdcardfiles" zip will format it (I suggest you to give at least 1GB of space to the secondary partition).
After that grab the two zips: wetek-debian-chroot-sdcardfiles.zip and wetek-debian-chroot-systemfiles-rc1.zip and copy them (together with CWM's recovery.img) to the FAT32 partition of the MicroSD (the primary one).
Boot to recovery and flash the two zips (the order doesn't matter).
How to actually use it:
The "systemfiles" zip will add an helper file that I called "debian-chroot", together with the init.d script it will set up the chroot at boot and run the configured services (as a template the /system/xbin/debian-chroot file includes the execution of dropbear daemon, so you can use it as starting point for your own stuff).
To access Debian you can just type as root from terminal emulator / serial console / adb over network "debian-chroot chroot", othwerise you can access using an SSH client to the configured Dropbear SSH server that is listening on port 2222.
There are two default users: 'root' (pwd: wetek) and a regular user 'wetek' (pwd: wetek), both can be used to access to the ssh server.
* ROM 2015-01-30
* GAPPS 2015-01-07 (LITE)
* ROM (Android TV) 2015-01-30
* GAPPS (Android TV) 2015-01-30
In the "regular" CM12 build added some things I had forgotten when upgrading the device tree from the old to the new kernel (the most important, I had forgotten to mkdir the paths for the hard drives mounting).
Included the new tvheadend posted in OpenELEC section (the one with the different decsa algorithm)
Added Android TV build and just a tip for the first boot of it...
Don't change the language, use the default english already selected (don't know why but changing language is VERY sluggish/laggy), when you're doing configuring it you can change it to your preferred one in Android's settings.
Another thing, if the screen stays black after allowing or denying the "Network location" option (the last step of the wizard) for more than 10 seconds just bring up power menu and perform a reboot, the Wizard will kick in again, you'll have to just click continue because everything is configured and it will work. I don't know why it acts like this sometimes!
Guys if you experience some freezes of the box after running for certain time an encrypted channel (I noticed that it happens to me between 45/60 minutes after tuning to such channels) it might be caused by the new decsa library, it looks like it has a memory leak.
I will revert to the older binary, in the meantime you can flash this zip to go back to the one from the older build.
After reverting I'm tuned on an encrypted channel since an hour and I don't see any weird memory issue
Oh, guys, I forgot to mention that in this build I've enabled Amlogic's "anymote" support (the backend to be remotely controlled use Google TV remote app).
To use it go to "Network -> Other" options in Android's settings and enable "Google TV Remote support", after that install this app on your Android phone/tablet and you'll be able to use it as a remote.
PS: I didn't have much luck running the "Google TV Remote" app from the Play Store, it wouldn't find the device at all, maybe they are enforcing a private key handshake like in newer Google Cast Receiver to be able to run it only on official Google TV devices.
PPS: remote audio input doesn't work, the Amlogic's anymote throws an exception regarding a class not found. Can't do much about that since it comes as a precompiled APK (and I already had to do some smali hack to be able to run it on Lollipop)
* ROM (CM12) 2015-01-31
* GAPPS 2015-01-07 (LITE)
* ROM (Android TV) 2015-01-31
* GAPPS (Android TV) 2015-01-30
* ROM (CM11) 2015-01-31
* GAPPS 2014-06-06 (LITE)
Lollipop ROMs:
* Reverted tvheadend to the older version that doesn't suffer of memory leak
* Introduced a workaround to prevent Netflix from using OMX
* Updated upstream sources
Kitkat ROM:
Added CM11 based on the new kernel. It's generally faster than Lollipop, as I have said ART probably is too much for the MX
I haven't added the extra stuff to Android settings so I'm including the ugly MboxSettings app, I have given more love to Lollipop, I have to admit it, in case if you people prefer this rom I can start customizing it more.
I suggest you to install SuperSU from Play Store, let it update the "su" binary choosing the normal way and converting it into a system app + installing the backup script to let it survive rom updates. This because CM11's SuperUser doesn't work nicely with the way Kodi request root rights.
Beside the same F1/F4 shortcuts as the Lollipop roms above, there's a further shortcut with F8 to toggle expanded desktop mode.
* ROM (CM11) 2015-02-01
* Added the most important things of MboxSettings to Android settings (display resolution, overscan, cec, digital audio and google tv remote).
* Added an entry, accessible through developer settings (at the very end of the list), to enable the autostart of Kodi at boot
* ROM (CM11) 2015-02-02
* added the new suspension method (I will quote my previous post to describe it)
ChristianTroy said:
Guys I've been trying a new suspension method, it's a better solution IMHO.
I'm going to use Android's capabilities to prevent the device from entering suspension (with wakelocks) to only let the kernel turn off everything but without really entering suspension, something like flashing the "wetek-disable-shutdown.zip" that you find in the second post of all my other rom's threads.
But I did a modification in the kernel: it will turn the power led blue/red if the display is on/off so you'll know if you actually turned it off. I decided to mantain on the eventually enabled wifi or eth led so you'll see if you have connection or not.
This thing is very useful if you're going to program a recording in tvheadend, otherwise the device won't wake from sleep (at least not with easy work without using Android's AlarmManager to create a new wake up task) and in this way the device won't have to perform boot from scratch once you put it to sleep, but it will be instantly on again.
It will consume a little bit more of power though (haven't run much tests but since this device when it's on runs at 7w, I guess it will be <5w) but I think that many of you keep it running all the time, in this way it's like if it was running but just with the output turned off
Click to expand...
Click to collapse
* corrected an unwanted (by me) behavior of Amlogic's android ethernet service that was putting off the interface when the display was being turned off. If you were connected using eth you would find yourself without network with the new suspension method... if for some reason you want your eth to be turned off when the display is off add "ro.screen_off.disable_ethernet=true" to /system/build.prop
* disabled google setup wizard that was causing a black screen on first boot because it was invoking the AOSP version of setWifiEnabled instead of CM's one with AppOps support
* enabled the execution of a boot service to set up the remote (you couldn't power off the device using the remote before this build) that I had forgotten to set up after moving to the new kernel branch
ps: let me know what you think about this new suspension method, personally I do really love it and was thinking about that since quite some time
Debian chroot
As very first thing you have to set-up a MicroSD card with two primary partitions, the first one must be formatted in FAT32, the second one can be left unformatted because the "sdcardfiles" zip will format it (I suggest you to give at least 1GB of space to the secondary partition).
After that grab the two zips: wetek-debian-chroot-sdcardfiles.zip and wetek-debian-chroot-systemfiles.zip and copy them (together with CWM's recovery.img) to the FAT32 partition of the MicroSD (the primary one).
Boot to recovery and flash the two zips (the order doesn't matter), after each ROM upgrade you'll have to flash only "wetek-debian-chroot-systemfiles.zip" (the other one is just to set up Debian, flash it in case you mess up the system and wanna start from scratch).
How to actually use it:
The "systemfiles" zip will add an helper file that I called "debian-chroot", together with the init.d script it will set up the chroot at boot and run the configured services (as a template the /system/xbin/debian-chroot file includes the execution of dropbear daemon, so you can use it as starting point for your own stuff).
To access Debian you can just type as root from terminal emulator / serial console / adb over network "debian-chroot chroot", othwerise you can access using an SSH client to the configured Dropbear SSH server that is listening on port 2222.
There are two default users: 'root' (pwd: wetek) and a regular user 'wetek' (pwd: wetek), both can be used to access to the ssh server.
Regarding the random black screen on channel change can anyone try this advancedsettings.xml (location on Android is "/sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/") and tell me if it acts better? I didn't have any black channel since using it (3 days) but I don't wanna that it's just a lucky coincidence
Code:
<advancedsettings>
<network>
<buffermode>1</buffermode>
<cachemembuffersize>52428800</cachemembuffersize>
<readbufferfactor>10</readbufferfactor>
</network>
<pvr>
<minvideocachelevel>10</minvideocachelevel>
<minaudiocachelevel>15</minaudiocachelevel>
</pvr>
</advancedsettings>
Regarding the XMLTV EPG I set up xmltv to use tv_grab_it for some channels (47 to be precise, and it takes ~1 hour per fetched day with the --slow parameter that includes descriptions) and fix it using tv_sort on the generated output because some channels don't have a stop time and this won't let tvheadend add them to its database.
I used a Debian chroot in my Synology NAS and set up a crontab job in Synology's crond to execute a script, located at '/root/xmltv.cron' with this content:
Code:
#!/bin/sh
# Package
PACKAGE="debian-chroot"
DNAME="Debian Chroot"
# Others
INSTALL_DIR="/usr/local/${PACKAGE}"
PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"
CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`
chroot ${CHROOTTARGET}/ su -c 'tv_grab_it --output /volume1/homes/alan/www/tvguide_wip.xml --days 3 --quiet --slow --cache-slow && tv_sort --output /volume1/homes/alan/www/tvguide.xml /volume1/homes/alan/www/tvguide_wip.xml' alan
After that I enabled "Web Station" for the users and I can access my EPG from "http://NAS_IP/~alan/tvguide.xml" and use this URL as w*g*e*t parameter for tv_grab_file
This is the result:
If you install on your Play the Debian chroot that I posted yesterday you can practically do the same, just install xmltv on it running
Code:
sudo aptitude install xmltv
(or, if you know what you're doing, compile it from sources installing the required dependencies, some perl modules)
Install a cron daemon like "vixie-cron" and add it to "/system/xbin/debian-chroot" in the "start_services" function (like the template that runs the SSH server).
Set it up, save the XML output somewhere like "/home/wetek/tvguide.xml" and replace the "w*g*e*t" line in tv_grab_file with "cat /storage/debian/debian-chroot/home/wetek/tvguide.xml"
* ROM (CM12) 2015-02-07
* ROM (Android TV) 2015-02-07
Both Lollipop roms have been updated to match features/fixes of latest CM11 builds, plus upstream sources have been updated
New builds:
* ROM (CM12) 2015-02-14
* ROM (Android TV) 2015-02-14
* ROM (CM11) 2015-02-14
* OSCam (r10566)
Oscam zip for these builds, just flash it from recovery, when booted into Android access to http://wetek_ip:8888 and add your server (remember to add it to group 1, that is the group assigned to the dvbapi user).
Open TVH configuration page and in "CAs" section add a new "CAPMT (Linux DVBApi)" with these content:
ps: this oscam has Smargo (libusb) and PCSC support
tvh-3.9.2509_oscam-r10566_android-wetekplay.zip
New Tvheadend built from sources (updated this morning), no more using OE's libraries but with another approach instead. I've built it with some enhancements in CFLAGS for the cortex-a9 cpu.
OSCam included, if you set it up the way I explained yesterday you're good to go, otherwise just configure it that way
ps: it looks like this version recognizes the hybrid c/t tuner as c only so if you need dvb-t keep using the one you're already using
* ROM (CM12) 2015-02-22
* ROM (Android TV) 2015-02-22
* ROM (CM11) 2015-02-22
tvh-3.9.2515_oscam-r10607_android-wetekplay.zip
Test zip that will change the following things:
- update tvh to latest sources (synced this morning)
- update oscam to r10607
- update wetekdvb.ko with the one from OE 5.0.4
PS: now the hybrid tuner is recognized, I had to change a couple of things
* ROM (CM12) 2015-03-05
* ROM (Android TV) 2015-03-05
* ROM (CM11) 2015-03-05
If you're upgrading from a build where you were running oscam, go to "mounts and storage -> format /system" before flashing the new stuff (or manually delete "/system/addon.d/80-oscam.sh" if you know what you're doing).
Changes:
* updated upstream code
* updated WeTek DVB kernel driver
* updated Tvheadend
* added OSCam (no support for it, it's a "grey area" thing)
* fixed a bug where the resolution was resetted to 720p @ 60hz under certain conditions (like when swapping HDMI input in some TVs), and use 1080p @ 50hz as fallback resolution
In case you wanna try a test zip with brand new OSCam and Tvheadend built with Android toolchain (NDK) flash THIS zip on top of today's build. I'd really like some reports about any crash using the native binaries.
Kodi 14.2 BETA 1 apk
This is a Kodi 14.2 BETA 1 based build with two patches added that add support for automatic frame rate switch (you have to enable it in settings) and that should behave better with the black screen bug.
Since it's been signed with different keys respect those from Kodi build server you won't be able to install it over the older Kodi but you'll have to uninstall it.
Take a backup of /sdcard/Android/data/org.xbmc.kodi folder before uninstalling or Android will delete it and you'll lose your configuration; restore it after installing the new APK.
Download
I'm using this /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<advancedsettings>
<network>
<cachemembuffersize>20971520</cachemembuffersize>
</network>
<samba>
<clienttimeout>30</clienttimeout>
</samba>
<network>
<readbufferfactor>4.0</readbufferfactor>
</network>
<pvr>
<minvideocachelevel>5</minvideocachelevel>
<minaudiocachelevel>20</minaudiocachelevel>
</pvr>
</advancedsettings>
* ROM (CM12) 2015-03-10
* ROM (Android TV) 2015-03-10
* ROM (CM11) 2015-03-10
- CEC improvements (codesnake's OE fix)
- Mapped CEC red/green/yellow/blue buttons to power/home/menu/search
- upgrade tvheadend and oscam with the native (android ndk) ones
- updated dvb code (same code as latest OE)
- few other minor things at kernel level
- updated upstream sources
Notes: run it with Kodi that I posted yesterday (and that you can find in the second post) with Aeon Nox skin + Live TV mod and you will get a very good experience, specially if using CM11 or, if you don't mind it being a bit more laggy, ATV
* ROM (CM12) 2015-03-11
* ROM (Android TV) 2015-03-11
* ROM (CM11) 2015-03-11
Fixed a problem with the dual tuner and the new bootloader (the one flashed by NAND version of OE and latest WeTek OS)
Related
Clean | Stable | Carbon | Flexible | Optimized | Excellent
-> ArchiDroid 2.X <-
Ported to the Galaxy Player 4.0
BIG thanks to @JustArchi
{
"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"
}
Changelog
ArchiDroid 2.4.3
- Improved archidroid_pixelserv
# Previously archidroid_pixelserv responded to all requests with the same 1x1 NULLGIF response (GIF89a[]![])
# This was OK but in some apps it showed our gif in binary form (GIF89a[]![]) instead of showing nothing, i.e. in Subway Surfers game
# Now we respond with a "NULL" content proper for request
# If app requests JPG, we respond with NULLJPG, if app requests TEXT, we respond with NULLTEXT etc.
# This way app "gets what it wants" and won't show something, which it can't understand to user
# Surprisingly, at least Subway Surfers doesn't show any ad right now, so it also stops some apps from displaying NULL content, instead of showing NULL in binary form
- Removed VNC Viewer
- Updated ArchiDroid Backend tools (dnsmasq, haveged, dnsproxy2, pixelserv) to latest versions
- Updated PA GAPPS to 0417
- Used Carbon as base; Omni is maybe coming in future (if requested; this eventually needs much time)
Download
All Files Dev-Host
Experimentals on GitHub
Stable: ArchiDroid 2.4.3
Oldstable: ArchiDroid 2.X
Remember that you don't need anything else to flash. Google Apps are included already.
Known Issues
All known and unknown Carbon/CM bugs (if any)
Debian and adflash are not working yet (maybe we have to create a virtual ext4 partition cause of too little /data partition).
If this is working it's possible to modify adflash to fit my GitHub repository.
Follow (original) ArchiDroid On XDA!
Write A Review!
Rate the Official Thread!
Buy The Masterchief A Beer (he created this awesome ROM!!)
Like ArchiDroid On Facebook!
Hit Thanks!
Informations:
[ROM] [KVT49L] [OmniROM] [Linaro] [Stable] [Flexible] [Excellent] [20/04/14] ArchiDroid V2.4.3 | Power In Your Hands, a ROM for the Samsung Galaxy Player 4.0
Contributors
JustArchi
andreasltcf
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: Carbon; ArchiDroid
Version Information
Status: Beta
Created 2014-04-28
Last Updated 2014-04-28
[SIZE="+3"]ArchiDroid's FAQ / Q&A (i9300)[/SIZE][SIZE="+1"]Remember.. This is the Galaxy Player 4.0 thread.. And based an Carbon.. It maybe differs from following information..[/SIZE]
[SIZE="+1"]Features / Why ArchiDroid?[/SIZE]
First of all, ArchiDroid includes everything available in it's base. The whole point of ArchiDroid is to improve the base, without needing of making any trade-offs, so by flashing ArchiDroid, you're getting everything offered by the base itself. There's nothing to lose, everything to gain.
You can read detailed information about every ArchiDroid component here. It's a massive wall of text, so I'm only going to list the core features without describing them.
These were written from scratch, they're completely unique and you won't find exactly the same implementation in any other ROM.
ArchiDroid-Unique features:
- ArchiDroid's AROMA Installer
- ArchiDroid's Pocket Debian
- ArchiDroid's Flasher
- ArchiDroid's RunOnce
- ArchiDroid's Init
- ArchiDroid's Backend Control
- ArchiDroid's HArdware Volatile Entropy Gathering and Expansion Daemon (Haveged)
- ArchiDroid's Fast Random Number Generator (Frandom)
- ArchiDroid's Adblock (dnsmasq/dnrd, dnsproxy2, pixelserv)
- ArchiDroid's Forced Update
Apart from that, here, on the credits page, you can find all third-party projects, which have been implemented into ArchiDroid. In addition to that, it's up to YOU to decide if you want to install something, or not.
ArchiDroid focuses on flexibility and user choice.
If you're looking for fastest ROM, choose ArchiDroid.
If you're looking for most battery-saving ROM, choose ArchiDroid
If you're looking for cutting-edge functions, choose ArchiDroid
If you're looking for the most flexible rom ever created, definitely choose ArchiDroid
ArchiDroid adjusts to your needs. You can make it whatever you want. With bunch of presets, modes and questions, you can make your ArchiDroid behave. Check yourself why ArchiDroid is The TOP 1 ROM for Galaxy S3http://forum.xda-developers.com/galaxy-s3#romList, according to number of followers, rates, reviews and downloads count. Check the Reviews, take a look at Video Reviews, do whatever you want to, ArchiDroid is proven to be one of the best ROMs for Galaxy S3, ever created.
Try ArchiDroid once, and you'll never look back. I can assure you.
Disclaimer
Developer's Kitchen
Unless stated otherwise, all ArchiDroid components are licensed under the Apache License:
Code:
Copyright 2014 [email protected]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Especially:
ArchiDroid is one of the most complex ROMs ever created. When you start digging in my work, you can very easily get lost. And I'm not talking about base itself, but about everything next to it. You can use every part of my work, as long as:
1. You include proper credit where you should. This usually includes proper comment in a script/file and in the credits of the project, including license (if needed)
2. You let me know about this fact. Through PM on xda or e-mail
I'm always happy to help, especially with the problems I faced in the past. However I also want to be respected, considering that most of the ArchiDroid parts were written from scratch.
Know Your ArchiDroid
ArchiDroid is not only a rom. It's not only a baked android with third-party apps, modifications and tweaks. ArchiDroid is an universal backend which improves rom by many built-in functions.
Let me tell you a story. During developing first version of ArchiDroid 2.0 I experienced many problems, which were not that easy to solve. First of all - apps data. Trust me or not but you can't simply extract data, put it in /data/data after install and hope that it works. Android will detect such injection, report inconsistent of data and wipe everything attached to that. Okay so... How I should provide you with my boeffla preset? CoolTool settings? STweaks profile? If I put my data during flashing it'll get wiped. If I put my data and deny wiping it then Android will report inconsistent of data to user and work unstable. Yes guys, it's impossible to do so without a trick or without recompiling whole rom.
I won't tell you a whole story, because you probably don't want to hear about ArchiDroid development. I'll simply tell you that I overcome MANY difficulties, simply because I do what I like, and I like what I do. After countless number of hours, I can finally provide you with the ROM, which is the best. Why is it the best? Because I'm improving the base, and I'm not making any trade-offs.
GitHub / Versioning / Experimental Versions
You can easily "pack" latest experimental and flash without needing to wait for the next build. I'll tell you how to download and flash it by yourself.
[Newbie Version]
1. Open 2.X-EXPERIMENTAL branch.
2. Click on Download Zip button located in bottom-right corner.
3. Install 7-Zip if you don't have that already. Other programs may, or may not work correctly.
4. Right-Click on zip, select Extract Here
5. Navigate to newly created ArchiDroid-2.X-EXPERIMENTAL folder
6. Select all files WITHOUT __dont_include folder, right-click and select 7-Zip => Add to archive
7. Make sure that you have zip format, Fastest compression (to save some megabytes) and Deflate method of compression.
8. Voila, copy newly created ArchiDroid-2.X-EXPERIMENTAL.zip to your phone and flash as usual.
[Expert Version]
1. Install Git for Windows or Linux
2. If you're on windows then make sure that windows won't change LF into CRLF (git config --global core.autocrlf false)
3. Clone my git repository using .git file. Keep in mind to specify depth, as this repo is really big. (git clone https://github.com/andreasltcf/ArchiDroid.git --branch 2.X-EXPERIMENTAL --depth 1)
4. Select all files WITHOUT __dont_include folder zip them into standard .zip format with Deflate compression or without any compression.
5. Copy .zip to your phone and flash as usual
6. In order to update your local repo execute git pull origin 2.X-EXPERIMENTAL and go to point 4.
Additionally you can watch @JustArchi's short video, which shows how to flash experimental ArchiDroid going through "Expert Version" (Archi's GitHub).
ArchiDroid Features
Know your ArchiDroid, learn how to use it
Introduction / Basics
Welcome to ArchiDroid's world mortal. In this tutorial we will show you what ArchiDroid has "inside" and what it really offers. All of things included in this post are ArchiDroid-specific, which means that you won't find any ROM with the same features, as they're written from scratch.
Here you can find some definitions of the words used in sections below. You should know most of them, but in case somebody is lost here you can get back on track.
Terminal, Shell - Typical android shell, which may be obtained in three ways.
1. Through native Android Debug Bridge (ADB) with command "adb shell" from the PC or even "ADB through network" (if supported).
2. Through any Android terminal app, f.e. Android Terminal Emulator bundled with ArchiDroid.
3. Through secure shell daemon (sshd), which needs to be turned on firstly. This is extremely useful in terms of pocket debian, which will be described later.
You can use any of these methods to access android's terminal, however usually Android Terminal Emulator will be the easiest one, as it's android app bundled with ArchiDroid. WARNING! Most of the commands below WILL require root access. You can log in to super user shell by "su" command right after obtaining shell. If you're unsure if you're logged as root or not, "whoami" command should print actual user, "root" or "unknown uid 0" are OK, others are not.
ArchiDroid's Pocket Debian
From wikipedia:
From debian site:
How exactly this covers our beloved SGS3 (and countless number of other android arm-based phones)?
As you may (or even should!) know, Android operates on it's own Linux-based kernel. Android's kernel is literally a fork of Linux kernel, with a few special/unique functions which are required, mostly hardware-specific. Because of that kernel itself is VERY compatible with everything based on Linux.
However there have always existed one typical problem, lack of proper environment. We have a great kernel, great power, linux-based android environment, but this environment lacks of very common and required libraries/binaries. If you ever wondered what is or what does busybox, this is the answer. Busybox is just a small package which offers a few standalone GNU/Linux binaries, which are required to make certain things work. For example, swap priorities. Android knows what swap is, and nothing else. It doesn't know that swap could have a priority, so if you use android's swapon command on 4 devices, it will firstly fill first device, and then proceed to the next. That's why we need busybox in ALL custom kernels, because android environment isn't enough.
However busybox sometimes isn't enough. If we focus only on Android itself, it is. But if you for example want to run stricly linux-based service, I don't know, a web server for example... Is it possible to run a native linux web server on an android? No, it's not. You should firstly compile such service on arm architecture, including all dynamic and static libraries (wrrr ) in it only to finally get mad because of missing libraries or other dependencies. Of course if you're patient you'd finally compile everything and set up, however how long would it take? A few days maybe? If you're skilled in what you're doing...
This is why I included built-in "pocket" debian in ArchiDroid. It's FULLY compatible with everything compiled/based on armhf/armel GNU/Linux architecture, for example Raspberry Pi. With two easy commands you can literally jump into debian environment and use every typical GNU/Linux utilities known from debian itself. Of course this means nothing for most of the users, because they'll never have any reason to use such debian environment but from the developer side, it's big step forward. The best example is with github. As you know ArchiDroid has it's own repo on github, from where you can download/manage stuff. There also exists git app for linux and windows. If you want to follow "expert" way of flashing experimental ArchiDroid version, such program is required. The scenario is the same as compiling web server for an android, it requires much more effort than it's worth. And even then you can end up with syncing external dependencies and searching for solutions for the problems you've never seen before... And with ArchiDroid's pocket debian? It's as simple as in any debian/ubuntu distro. "apt-get update && apt-get install git" and voila. Your git is installed and ready for work. Going further I've even included git in pocket debian itself. Okay, I have debian, I have git, and what next? With git utility I can for example provide you with delta updates for ArchiDroid! ArchiDroid can easily use pocket debian to set up and sync ArchiDroid's repository and then pack and flash latest version without even needing of a PC, using 7-zip or anything else. Another example? A web server. I know that it's very dev-specific but if you for any reason need a web server running, just for example to test simple website, you can have it with just one command. Going further, VNC? MySQL server? PHP? Python? Perl? Ruby? Maybe conditional tasks with cron? Persistent minimal IRC client? rtorrent with rutorrent GUI over WWW? The list goes on... Anything based on linux will work. You can even host a server for your favourite game, as long as it has armhf/armel binaries (unfortunately most of the games don't).
So that's it. In short, debian is an operating system built-in in ArchiDroid to provide you with (unfortunately missing) GNU/Linux environment, with full power, ready to handle anything you could request. I made my best to include fully working debian in ArchiDroid for a minimal cost. Whole OS is packed in one big tar file, compressed using highest bzip2. As for now pocket debian has ONLY 40 megabytes of size, maybe in future it will have up to 50 megabytes, but no more. It's a VERY small cost for having such great power, especially if you know how to use it.
This is a really cutting-edge feature, mostly because I have no limitiations what I can include in my ROM right now, and while other developers are dealing with OpenDelta updates and many Android-based problems, I'm just launching my pocket debian and manages linux stuff.
I'm SURE that most of the advanced ArchiDroid user will just LOVE this feature, as much as I love it. I'm looking forward to your responses how YOU use pocket debian with your ArchiDroid. It's also a great time to learn what does the debian offer and how you can simplify your common tasks with just one example debian utility .
Technical informations:
1. Pocket Debian does not cause any additional overhead. We don't need to use emulation, neither virtualization to boot our monster. I used chroot technology to "jump" into debian environment with already running kernel and Android. That means additional required CPU/RAM is based on what you run in pocket debian. Booting itself doesn't require anything, just about one megabyte of ram for /bin/bash shell .
2. Android has some restrictions, mostly sockets. It doesn't allow to create inet sockets by default, even for root users. You will need to add your custom debian users to special group called "inet" (GID 3003) to allow creating of inet sockets, and you may also need to add a group to net_raw group (GID 3004) to allow creating of raw sockets. Please keep in mind that it's only required if you're running an app which required it's own socket, for example mysql server. So apt-get install mysql-server will fail right after booting, you will need to use "addgroup mysql inet" and then apt-get -f install to complete installation. Of course "mysql" is the new user under which mysql-server really operates. I've added root to both of these groups by default.
3. The only "real" restriction is the kernel. Our debian uses Android kernel and it's filesystem. It should work with most common tasks but in some cases our kernel may lack specific modules or built-in code, for example tun/tap required for OpenVPN. Still it's enough to run pretty much everything and if you get in touch with your favourite kernel developer you can also kindly ask for specific missing things.
4. Debian is built and included thanks to debootstrap utility, ArchiDroid command used for creating debian environment is debootstrap --verbose --arch armhf --include=git,ca-certificates,ssh,htop,tightvncserver,xterm,xfonts-base --exclude=manpages,man-db,rsyslog,vim-common,vim-tiny testing debian http://ftp.fr.debian.org/debian
HowTo:
Pocket Debian contains two main terminal commands, "adlinux" and "debian". Both of them are described below. By adlinux and debian you boot and jump into debian's chroot, which means you can use any debian-specific commands.
Examples:
passwd - changes password of actual user. This is needed to login as specific user, for example through ssh.
service ssh start - starts local SSH (secure shell) daemon on native port :22, to which you can easily access via any client supporting ssh, f.e. PuTTY. So basicly after you start shell you can literally connect to your local area network (LAN) IP on port 22 f.e. through PuTTY from your PC.
ifconfig - prints network-related informations about online interfaces, including your local IP, which may be useful for connecting to SSH.
htop - Enhanced top utility. Gives you very good terminal-based view on actual running processes, used ram, load, and more.
apt-get update - Syncs with debian's apt repository. This is mandatory to use many of apt commands because ArchiDroid's debian comes without local repo available, however fully configured to download and access it with just one command
apt-get install XXX - installs packet XXX from debian's repository.
apt-cache search XXX - searches for all packets including keyword "XXX". Ultra useful in terms of searching for specific packet.
Please note that pocket debian is VERY similar to normal native Debian/Ubuntu distribution, therefore above commands are not ArchiDroid's magic, they're very widely used in Debian/Ubuntu distros. If you want to learn more, most of the Debian/Ubuntu tutorials will be very helpful.
ArchiDroid's Pocket Debian Booter (adlinux)
You can call "adlinux" command from your favourite terminal.
adlinux is designed to boot and prepare ArchiDroid's Pocket Debian environment. It requires mode to be specified, and also respects any extra arguments passed.
If you call standalone "adlinux" command then it will print usage and then ask you what you want to do with giving proper informations about every choice. Additionally if you know what you want to do, you can also pass arguments directly to adlinux command, f.e. by executing "adlinux default", which will execute adlinux with "default" mode.
Available modes:
default - Will mount /data /system /storage/sdcard0 /storage/sdcard1 and core filesystems in chroot. Default suggested mode
safe - Will mount only core filesystems in chroot. Useful if you don't want to share your storage in chroot
bare - Won't mount even core filesystems such as /proc /dev or /sys. Requires "debian force" to enter chroot. This is the "real" safe mode. You won't be able to interact with an android in any way, while debian itself will work in very limited environment, making core functions unavailable. Suggested only for testing purposes
rebuild - Will automatically reboot your device and remove debian folder in the safe way. WILL CAUSE ALL DEBIAN DATA TO BE LOST!
unmount - Will automatically reboot your device to safely unmount debian environment
Extra options:
extsd - Use external sd card (/storage/sdcard1 /storage/extSdCard), if possible
intsd - Use internal sd card (/data/media/0)
Additional information about modes:
Debian shares core kernel filesystems in "safe" and "default" modes, while it also shares your internal and external sd card in "default" mode. This is nothing to be scared of, as you have full control of what you run in debian, however please note that you CAN'T do whatever you want. All mounted partitions in debian are "binded". "Bind" means that it's mirrored to the mount point and all changes on mounted partition WILL affect the mount point, which is logical. This is nothing to be scared of, as long as you know that debian only extends your environment, it does not fully works in it's own and you CAN cause serious problems from inside of chroot. The only really safe mode is "bare" mode, however in "bare" mode debian can't really do anything, as kernel filesystems are absolutely required for most of the functions. Okay so, you need to know one thing. If you have booted debian you SHOULD NOT touch debian's folder, which is ArchiDroid/debian (on your internal or external sd card, depends what you choosed).. As you know debian for example binds /data to it's folder /data, which is physically ArchiDroid/debian/data. If you for example delete ArchiDroid/debian through root explorer WITH mounted debian then it will ALSO delete debian/data folder, which is binded to /data, and therefore will delete your whole internal sd card, that's why it's extremely important to take care because booted debian becomes part of the android and deleting it can cause at least soft bricks, with a possibility of hard as well. If you want to delete debian folder PLEASE use "rebuild" mode, only through this way you're absolutely sure that nothing bad happens and you won't delete your whole system partition by accident.
Note about extsd option:
Debian requires symlink functionality, typically native windows filesystems DON'T support symlinks, therefore you need to have your external sd card formatted in one of the native linux filesystems, f.e. ext4. adlinux will automatically tell you if debian can be unpacked and used on your external sd card, however it won't be possible under most common filesystems, such as exFAT or FAT32.
Technical informations:
1. Pocket debian archive is located in ArchiDroid/System/debian.tar.gz file. This is "bare" system used for creating environment for the first time, you should not touch it.
2. adlinux detects if debian is already extracted when booting, if not, it's firstly extracted from the file described above.
3. After extracting (if required), core filesystems are mounted with "bind" option based on the mode you've selected in "mode" question above. Typically it mounts /data /system /storage/sdcard0 /storage/sdcard1 /storage/extSdCard /dev /proc /sys.
4. Unmounting is not fully supported right now (linux barrier), therefore both "unmount" and "rebuild" options require a restart to execute properly.
ArchiDroid's Pocket Debian Shell/Chroot (debian)
You can call "debian" command from your favourite terminal.
debian command is designed to allow you "jumping" into debian chroot created by adlinux. Please read how adlinux command works firstly if you haven't done that already. debian command checks if core filesystems are available (if debian is booted), and if they are then it firstly modifies required environment variables to make debian happy (such as TERM, HOME, PATH), then it changes root (chroots) into debian folder, therefore allowing you to execute everything from inside of chroot. It's very generic command, therefore standalone "debian" command won't give you a choice the way adlinux did.
Available options (parameters):
force - required for jumping into bare debian, created with "adlinux bare" command above. This skips debian checks for mounted core filesystems, normally you should avoid it at all cost, unless you know what you're doing. If core filesystems are missing then it's very likely that your debian will be disabled in more than 90%.
extsd - Use external sd card (/storage/sdcard1 /storage/extSdCard), if possible
intsd - Use internal sd card (/data/media/0)
cmd - Executes command in debian chroot
WARNING! cmd parameter will cause all further parameters to be threated as a command passed to debian, therefore you need to make sure that this is the last debian parameter which you want. For example "debian force cmd service ssh start" will skip filesystems checks and execute "service ssh start" in debian's chroot, however "debian cmd force service ssh start" will pass "force service ssh start" to debian, therefore respecting filesystems checks and passing invalid command.
This function is extremely useful for making init.d and other startup scripts. For example you can easily call "adlinux default" and then "debian cmd service ssh start" to call secure shell daemon on every boot with two easy steps.
Technical informations:
1. debian command uses chroot technology to change root of current shell to debian shell.
2. After chrooting to debian directory, /bin/bash shell is automatically called as default debian shell.
ArchiDroid's Flasher (adflash)
You can call "adflash" command from your favourite terminal.
adflash is a great small utility, which allows you to easily update your ArchiDroid to latest stable or experimental version with one easy command and delta upgrade. It utilizes ArchiDroid functions, therefore you must be running ArchiDroid to use it.
If you call standalone "adflash" command then it will print usage and then ask you what you want to do with giving proper informations about every choice. Additionally if you know what you want to do, you can also pass arguments directly to adflash command, f.e. by executing "adflash 2e git", which will execute adflash with 2.X-EXPERIMENTAL version using git mode.
Available versions:
2e - 2.X-EXPERIMENTAL
2s - 2.X-STABLE
1e - 1.X-EXPERIMENTAL
1s - 1.X-STABLE
Extra options:
git - Sets up local git repository, which gives you delta upgrades and bandwidth saving
direct - Downloads targeted branch as .zip file directly from github
clean - Cleans everything up, including local repo and tmp folder from ArchiDroid directory specified below
extsd - Use external sd card (/storage/sdcard1 /storage/extSdCard)
intsd - Use internal sd card (/data/media/0)
nozip - Shows changelog and changes only
Okay so, the most interesting option is the mode...
Direct mode is simple, fast and effective. It downloads target version (stable or experimental) from GitHub server, then it repacks downloaded zip file and makes it available for flash. You should use this mode for one-time downloads, such as once per stable version or two. The only advantage of this method is the ability to download from github (and with one command).
Git mode is complex. It uses ArchiDroid's Pocket Debian (read above) for cloning and updating local ArchiDroid repo. This gives several number of advantages, mostly for using experimental versions. Firstly, by having local ArchiDroid repo you have to download ONLY changes between your snapshot and server's snapshot, which means delta upgrades. Secondly, you have access to all commits from target branch, so you know exactly what has changed since your latest download. Again, this is extremely useful for experimental branch, as changelog may not be up-to-date. Keep in mind that git mode will require additional space on your device for keeping ArchiDroid repository, therefore you sacrifice some space for delta upgrades. This mode is extremely useful for flashing ArchiDroid often, for example daily experimental versions, because in fact you download only new commits instead of whole repo/archive.
ArchiDroid's RunOnce (Backend)
ArchiDroid's Init (Backend)
ArchiDroid's Backend Control
ArchiDroid Backend Control is a set of settings, which controls behaviour of ArchiDroid's Init. It's located in /system/archidroid/dev and contains a number of files, which are recognized by ArchiDroid's Init. You shouldn't directly touch /system/archidroid/dev, instead you can control behaviour of ArchiDroid's Backend through /system/archidroid/scripts. They can be easily executed through any script manager, f.e. Root Browser or Android Terminal Emulator. Some of the settings are also located in /system/archidroid/etc folder, mostly configurations for binaries utilized by ArchiDroid's Init.
ArchiDroid's HArdware Volatile Entropy Gathering and Expansion Daemon (Haveged)
The haveged project is an attempt to provide an easy-to-use, unpredictable random number generator based upon an adaptation of the HAVEGE algorithm. Haveged was created to remedy low-entropy conditions in the Linux random device that can occur under some workloads, especially on headless servers. Current development of haveged is directed towards improving overall reliablity and adaptability while minimizing the barriers to using haveged for other tasks.
The original HAVEGE research dates back to 2003 and much of the original haveged documentation is now quite dated. Recent work on haveged has included an effort to provide more recent information on the project and its applications.
The original research behind HAVEGE use was based upon studies of the behavior of processor caches from a hardware level. The 'Flutter' documents attempt to provide a modern view of HAVEGE at software level through the use of a diagnostic build of haveged that captures the non deterministic inputs to haveged for analysis by external tools.
ArchiDroid has built-in haveged entropy generator. It's controlable through ArchiDroid's Backend Control - ArchiDroid_Haveged_EnableDisable.sh. It's turned on in default configuration, through HAVEGED_ENABLED
ArchiDroid's Fast Random Number Generator (Frandom)
Frandom is a Linux kernel random number generator, which is 10-50 times faster than what you get from Linux' built-in /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.
ArchiDroid has built-in frandom activator. It's controlable through ArchiDroid's Backend Control - ArchiDroid_Frandom_EnableDisable.sh. It's turned on in default configuration, through FRANDOM_ENABLED.
Notice: Kernel must support frandom module to actually make use of that. Init will try to search for frandom.ko module and load it, then use /dev/erandom for both /dev/random and /dev/urandom. If your kernel supports frandom, it will work. If it doesn't, obviously this will be skipped even if you have FRANDOM_ENABLED. Check ArchiDroid Init log located in /data/media/0/ArchiDroid/Init.log to check if frandom works properly for you.
ArchiDroid's Adblock (dnsmasq/dnrd, dnsproxy2, pixelserv)
dnsproxy2 is a replacement DNS proxy for Android 4.3+
This currently allows the user to manually override the DNS server IP,
and it sets the correct UID on outbound requests so they can be filtered
via iptables / AFWall+ / DroidWall / etc.
Dnsmasq is a lightweight server designed to provide DNS, DHCP and TFTP services to a small-scale network. It can serve the names of local machines which are not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP-allocated addresses to appear in the DNS with names configured either in each host or in a central configuration file. Dnsmasq supports static and dynamic DHCP leases and BOOTP for network booting of diskless machines.
Dnrd, Domain Name Relay Daemon is a caching, forwarding DNS proxy server. Most useful on vpn or dialup firewalls but it is also a nice DNS cache for minor networks and workstations.
Pixelserv is a super minimal webserver, it's one and only purpose is serving a 1x1 pixel transparent gif file. Using some creative firewalling (netfilter/iptables) rules you can redirect some webrequests (for adds for example) to pixelserv.
ArchiDroid has built-in Adblock. It's controlable through ArchiDroid's Backend Control:
ArchiDroid_Adblock_DnsmasqDnrdModeSwitch.sh
ArchiDroid_Adblock_EnableDisable.sh
ArchiDroid_Adblock_EnableDisableLocalDNSes.sh
ArchiDroid_Adblock_EnableDisableLocalDNSesDaemon.sh
ArchiDroid_Adblock_LockUnlockHosts.sh
ArchiDroid_Adblock_MoabAdawayHostsSwitch.sh
ArchiDroid_Adblock_Reload.sh
It's turned on in default configuration, through:
ADBLOCK_ENABLED
ADBLOCK_LOCAL_DNSES_DAEMON_ENABLED
ADBLOCK_LOCAL_DNSES_ENABLED
ADBLOCK_USE_ADAWAY_HOSTS
ADBLOCK_USE_DNSMASQ
In short. This is a very advanced and powerful solution for blocking ads through DNS queries. First of all we're forwarding all DNS traffic to localhost (127.0.0.1). Then we're handling them through local DNS server - dnsmasq (default), or dnrd (option). Our local DNS server reads blocked hostnames through special /system/archidroid/etc/hosts file, then if no record is found, it forwards DNS query to OpenDNS/Google DNS servers, or if it's found, returns 127.0.0.1 as the address. Lastly, pixelserv is providing a 1x1 NULLGIF response on local web server, so instead of big black/white screen instead of the AD, we get 1x1 transparent pixel, which usually perfectly hides ad from the app or the website.
Extra features:
1. You can specify if you want to use dnsmasq (default), or dnrd (option) as a local dns server. Dnsmasq is more flexible, modern, faster and has less memory footprint, however I also left dnrd as an option, because it's proven to work stable.
2. You can specify hosts file, which you want to use. In default configuration we use AdAway's hosts file, with more than 30 thousand of records, which results in extra ~2.5 MB memory usage. You have also an option to use MOAB (Mother Of Ad Blocking) hosts file, with more than 330 thousand of records, which will result in about ~30 MB memory usage. Eventually you can append your own rules or use non-standard hosts file, available in /system/archidroid/etc/hosts. Pro tip: You can point AdAway to use this hosts file (/system/archidroid/etc/hosts_adaway), which will result in automatic updates. /system/archidroid/etc/hosts is a symbolic link, either to hosts_away or hosts_moab, if you want to specify your own hosts, you can delete symbolic link and write your own rules.
3. Original /system/etc/hosts file has been locked from editing. This is to ensure that AdAway or other adblockers won't use obsolete and slow method of blocking ads through hosts. The whole point of implementing Adblock in ArchiDroid is to provide you with super-fast, flexible and effective way of blocking ads, also with getting rid of black/white ad screen. In 99% situations you don't want to touch ArchiDroid's default behaviour, as it blocks ads perfectly. Eventually, if you have a very good reason, you can unlock original hosts file through ArchiDroid's Backend Control and modify them, however keep in mind that every additional rule WILL slow down your network speed.
4. In default configuration local dns server uses two OpenDNS servers at port 5353, two Google DNS servers at port 53 and up to two local DNS servers provided by your Wi-Fi/3G connection, which overall gives a sum of 6 remote dns servers. In some rare scenarios (f.e. some wi-fi hotspots) you can notice that a moron, administrator of this wi-fi, blocked all dns queries and forces you to use his DNSes. This is BAD because of freedom and so on, but it's very common practice, that's why I turned on local DNSes as well. If you want to improve your privacy at least a bit, you can disable local DNS servers and then use only OpenDNS and Google DNS.
5. Above option initialy has been written to allow you one-time access to such non-trusty wi-fi's. But if you for any reason need automatic update of your local DNSes (3G and Wi-Fi's will use different local DNSes), you can also turn on Local DNSes Daemon, which will automatically query and update local DNSes if needed. This is also turned on in addition to local dnses above, of course in default preset.
ArchiDroid's Forced Update (RunOnce)
Forced update selected during mode selection in aroma tells RunOnce to work in "INSTALL" mode even on "UPDATE" mode, apart from that it works exactly the same as update mode, only RunOnce is affected.
Credits
ArchiDroid Core
- AROMA Installer
- AROMA Filemanager
- PhilZ Touch Recovery
- SuperSU
- Nova Launcher
- TouchPal Keyboard
- Hacker's Keyboard
- Android Terminal Emulator
- BetterBatteryStats
- Cool Tool
- Greenify
- MX Player & Custom Codec
- LMT
- Root Browser
- Titanium Backup
- CrossBreeder
- Online Nandroid
- Xposed Framework
- App Settings
- XPrivacy
- Debian
- cURL
- GitHub
ArchiDroid 2.X
- Carbon Rom
- Linaro Toolchain
- Impulse Kernel
- Spirit 2
Special thanks to:
- @JustArchi for creating ArchiDroid icluding all it's optimizations, a helpful hand to make this possible and his AWESOME SCRIPTS + documentation inside them.. really.. this guy is able to do ALL with scripts..
- @zaclimon for his work on our device with its own very little but awesome community, Impulse kernel, his sources for building and again all his contributions for our device..!!
- Kenshin, for graphic design and ArchiDroid Touhou bootanimation
- @mrtur, for graphic design and helpful hand during ArchiDroid experimental tests
- @malachow, for helping users across both international and polish board, sharing the spirit of ArchiDroid
- All ArchiDroid Contributors, for improving and making ArchiDroid better!
- ArchiDroid Facebook Group, for beta-testing the very first alphas of ArchiDroid 2.0.0
- ROM Cleaner, for awesome generic list of bloatware
- Android Revolution HD, for being ex-ArchiDroid 1.X base
- WanamLite, for being ex-ArchiDroid 1.X base
- Temasek's Unofficial Build, for being ex-ArchiDroid 2.X base
- crDroid, for being ex-ArchiDroid 2.X base
- You, for choosing ArchiDroid over other available ROMs
Nice to see it here as well, good luck with the port .
okay.. if anybody out there using this rom.. pocket debian is working fine.. (img on external sd).. have to write the scripts to do it all automatically..
edit: ups.. have to upload the rom first.... but if there's any interest in this.... btw if you're using carbon just now.. you'll love this rom..
I think people would be interested... I would be interested in trying it out once I get more time on my hands, maybe use it as a daily driver if it fits my needs.
Now that I've ported the Kexecboot bootloader, I'm moving on to my ultimate goal of getting a GNU/Linux desktop distribution running on the Note. My distro of choice for ARM these days is Debian, because it works well both in a chroot on Android as well as natively booted on its own. With kexecboot, you can boot kernels off of the external SD card or even off of USB drives, so you can have Debian and Android installed simultaneously. I'm booting Debian off of my external SD, a 16GB Sandisk class 10.
TO-DO LIST:
* Creating rootfs [DONE] - Use debootstrap to create a minimal armhf rootfs of Debian testing
* Compile kernel [DONE] - Using the CM11 kernel as a base, compile a kernel with features necessary for Debian
* Booting [DONE] - Boot a kernel that loads the Debian root filesystem natively
* USB OTG [DONE] - Once booted, use USB keyboard and mouse to interact with the device
* WiFi Networking [DONE] - Automatically load the WiFi driver and connect to a wireless network at boot, enabling remote access
* Basic Video [DONE] - Load an X server to display graphical applications on the display
* 3D Acceleration [WIP] - Use the Freedreno driver to accelerate GLES and GL 3D applications
* Screen rotation [TODO] - Figure out if Freedreno can rotate the screen to landscape mode
* Video Acceleration [TODO] - Use the MSM video decoder to accelerate video playback
* Audio [WIP] - Write an ALSA UCM configuration file to map the correct mixer channels to get sound out of internal speaker and/or headphones
* Touch and Pen [WIP] - Pen input seems to work, but touchscreen isn't being detected by X
* Bluetooth [WIP] - I can initialize and scan, but was unable to pair and hold a connection. Useful for keyboard and mouse while charging/externally powering device.
* Mobile Radio [TODO] - Make use of the mobile connection for data, possibly calls if anyone wants to take a shot. I'm not going to work on this.
* Package for release [TODO] - Build a fresh rootfs free of my development changes, copy any necessary stuff, package, and upload.
I plan on developing this simultaneously for the Note i717, Note 3 (N900T), and HP TouchPad as I have all three of these and I should be able to get supported kernels working for all three as well. I'll post pictures as I go, right now I'm still mostly working from an SSH shell over WiFi.
https://www.youtube.com/watch?v=qtb-TSGumNo
EDIT: Got the same patch applied to the TouchPad and it too is running these programs as shown in the video. Unfortunately the backlight doesn't come on on the TouchPad so it's hard to see anything.
EDIT 2: Colors sorta fixed: http://i.imgur.com/1kmKDOw.jpg I fixed the main picture but the 3D rendered video is now messed up with red and blue swapped.
CalcProgrammer1[/QUOTE said:
That sounds way to kool.
If I could get over my "terminal" fear I'd give you a hand, but as reading code I have no clue.
I couldn't even get linuxonandroid nor deploylinux to work and they both had a GUI.
That idea to use a REAL OS on the plablet is as great as using a REAL OS on a computer.
I do hope you succeed especially if the phone works also. LOL!
Thanks. :good:
Click to expand...
Click to collapse
What keyboard/trackpad combo are you using?
Only K1 Plus DVB-S2 / T2
Android 5.1.1
{
"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"
}
Sorry, I write in bad English. Used Google translator.
Firmware was made on the basis of the factory firmware from 06.06.2016.
What added, modified and deleted:
Version 2.5 of 29/07/2016
Changed the info bar in the application for DVB television viewing, namely: EPG became fixed and changed the color of the line - the elapsed time
and I made semi-transparent substrate under the panel.
Built into the firmware Xposed.
Remove the Chinese keyboard and some programs.
Added programs: ES File Explorer , Root Explorer and Titanium Backup
Established another, completely redesigned home launcher, sharpened for our unit.
Android base dated June 06, 2016
DVB-T2 is run a separate icon.
Added program to autorun programs (eg TV) at system startup.
You can set your wallpaper and live wallpaper (in the factory launcher that could be done)
Removed Kodi, who pre-install the Chinese version of the installed Play Market
Now there is a choice of firmware run - Launcher, DVB-T2, DVB-S2 / DVB-T2 / The first time you ask that run by default. Change then start: press the Apps button on Moodle, launch the Settings - Home Screen, activate on Moodle mouse button and choose the cursor that run at startup.
Many other small fixes.
If you like my firmware and think that I'm wasting a lot of time to improve the firmware, then "Donate to Me"
Download: https://mega.nz/#!RgxmXB7D!u1Xvcr2Mqwpz6N8K96eA_sVP9aUukJVjis807xOCNAE
Version 3 of 04/09/2016
Firmware was made on the basis of the factory firmware from 09.08.2016.
Separate selection of firmware run - TV launcher, launcher Staff, DVB-S2, DVB-T2, DVB-S2 / DVB-T2. When you first start you will be asked what to run by default. Change then start: press the Apps button on Moodle, launch the Settings - Home Screen, activate on Moodle mouse button and choose the cursor that run at startup.
SPMC - can be removed in the Settings - Applications
Kodi - can be removed in the Settings - Applications
All programs can be run in the TV launcher.
Many other fixes.
Download: https://mega.nz/#!opgTCLAB!DWuXujguK7_3qZ12fYUEu8yiQTk70Awo-yI1TX90yME
Version 4.5 of 09/10/2016
Firmware was made on the basis of the factory firmware from 09.02.2016.
Base of September 02,
Established last SuperSu
Changed info Bar in the DTV application
Button to access the settings and the BISS key sharinga made directly in the basic settings (now do not need to enter the code 111111)
Fully customizable clock and weather.
Changed Status Bar
Added YouTube
Added - Settings - Display - Traffic display in status bar.
Altered settings.
Reworked DTV application. Enjoying all screenshots
Many other fixes.
If you want to install the firmware update just - while retaining all of your settings and programs that change factory_update_param.aml file, which is in the archive with the firmware in the folder - "To save all the data app to change the file"
View attachment 3882359View attachment 3882360
Version 5.2 of 23/11/2016
Firmware was made on the basis of the factory firmware on November 11, 2016.
+ New launcher (serial removed)
+ Reworked application for DVB S2 - T2
+ Changed the volume control
+ Corrections and additions in the new launcher
+ After exiting the DTV application is now immediately get into the launcher
+ The launcher now can set their wallpaper. Settings - Display - Wallpaper.
+ The launcher is added off button - Restart the machine. If you choose to exit there rekaveri and insert the SD card with the firmware, the device will begin flashing, without of pressing a button on the rear of the unit.
View attachment 3941916View attachment 3941917View attachment 3941918View attachment 3941919
Version 6 of 19/12/2016
Firmware was made on the basis of the factory firmware on November 22, 2016.
+ Fixed problem with Google Play authorization
+ Added a choice of aspect Pan&Scan and Combo (Thanks _sm0ke_)
+ Added a choice of visiting infobar 1-2-3-5-7-10-15-20 seconds.
+ Fixed launcher NewLauncher
+ Added ViperFX
+ Added button in the status bar Back, Home, Menu, Latest Applications Screenshot (convenient for those who use the mouse Aero)
+ The TV settings added setting Prognosis
+ The weather added launcher show
+ By correcting the little things.
Download Version 6: https://yadi.sk/d/fQPfQRuA342Dza
Version 6.5 of 02/26/2017
+ Updated Google Services
+ New Boot Animation
+ Visually redesigned infobar in DTV application
+ Changed launcher NewLauncher, you can now change the program to run on the main icons (which in the mid - high)
+ Changed the status bar and adds it off button - reload.
+ Added new settings for the display of hours in the status bar (located under Settings - System - Setting the clock and date) is now possible to change the layout, color, date, seconds, size and so on..
+ Added new settings statusbare gradient (found in Settings - System - Polat gradient) You can put any color (two - 4 colors) in the status bar.
+ Other settings under Settings - System.
+ New app to clear the memory (in the launcher NewLauncher).
+ Many other fixes and additions.
Download Version 6.5:https://yadi.sk/d/P7A_Xk6U3EeJuj
Version 7.0 of 03/09/2017
When you first start the DTV application, you will not see Infobar! Do not panic and click on the MENU button - Installation - Configuring InfoBar and Weather - Configuring InfoBar and there we enable and configure Infobar itself.
Now you can fully configure InfoBar and not only. Almost all DTV applications have been redesigned in a graphic form.
You can completely disable Infobar, disable - include individual elements in it, set as one color of the background, and set a gradient of two different colors, change the color of all elements and labels, etc. That is, you can modify about 100,000 varieties of graphical appearance.
+ Added service information in InfoBar (Satellite name, Frequency, Speed, VPID, APID, etc.) You can disable - Enable,
Change the color in Settings - Install in the DTV application.
+ Only for DTV-T2: Infobar, Weather, Dates and Clock settings (Menu - Install)
+ Application signature check disabled
+ APK integrity and version checking disabled
+ Increased the volume level to 30 (was 10), now you can more fine-tune the volume level.
+ Fixed a volume scale (there was an overlay of two pictures)
+ Added files to control the gyro of the mouse and mouse
+ Added a button for cleaning background processes and displaying free memory in the curtain Last apps (you can turn off in Settings - System)
+ Error correction.
Download Version 7.0:https://yadi.sk/d/FjnY5jDK3FNrVb
Version 7.5 of April 3, 2017
+ Added support for Picons ( images Channel )
+ Added to TV Settings item autoframerate
+ Support for scripts in Init.d is added
+ Added information to the channel list: channel name, channel number, epg of the ongoing transmission, epg of the next transmission, description of the ongoing transmission. The only downside - when switching the channel does not have time to load epg, just pressing the up-down button will update the information.
+ Added 5 on the screen invisible buttons for controlling the air mouse.
List of channels - middle
Menu - the upper left corner (where the weather information)
EPG - bottom left corner
Detal EPG channel - right upper corner
Favourites - right bottom corner
+ Added about 40 new buttons !!! For controlling the air mouse in the DTV application
+ When switching favorites, it is now NOT automatically triggered Channel list
+ Other fixes and additions.
Now to the Picon. For satellites, your help is required. In order for the picons to show up, you need to copy the Picons folder into the internal memory of the receiver to the root of the disc. The path will look like this - mnt/sdcard/picons/. To make the picon appear on a specific channel, the name of the png file must have the same name as the channel. For example channel name First HD, then the picture name should be such First HD.png To make it much easier to fill your backup channels in the Channel Editor and just copy the name of the channel to the picture. Picks are recommended with a resolution of 220X132, and then put it on this site, and I'll add them to my main message.
Download Version 7.5:https://yadi.sk/d/Z2RSwL2V3Gbqcs
Examples of Pikons of 220x132 with names: https://yadi.sk/d/rK4xvWlt3Gbo7j
Movistar+ picons - https://yadi.sk/d/_kzwudQB3GbDzz
Version 8.1 of May 30, 2017
I recommend installing this firmware with cleaning all data !!!
1. Delete the Google services.
2. An analog of Google services is installed - MicroG. Now after downloading free RAM became more than 740 mb from 1 Gb. Correctly need to configure only them - read this
See photos - https://forum.xda-developers.com/showpost.php?p=72475106&postcount=219
1. go into the microG Settings application and activate the background services:
- Register your device with Google
- Google Cloud Messaging
2. In the same place, select the UnifiedNlp settings and note (if you only use GPS, you can skip it):
- location programs (just select one that is more like it), so that the search for networks
- address search programs - mark Nominatim with a daw (conversion of coordinates to address)
3. reboot the device
4. Go to the Play Market and enter your account.
Click to expand...
Click to collapse
3. The default picture in the display of picos in the DTV application has been deleted. (You can set transparent picos)
4. The picture of the displayed picos is enlarged.
5. Replaced bootanimation.
6. Added what did Pily_W (for which many thanks to him)
Boot with init.d support, root shell, more than 100 hid drivers
SAMBA server, copy speed ~ 11.5MB / s, minimal assembly, no GUI (settings are in /system/usr/data/samba/smb.conf, login: admin pass: admin)
If you have a different workgroup name on the network on behalf of WORKGROUP, then go to /system/usr/data/samba/smb.conf and change the name in the line "workgroup = WORKGROUP"
MSG is a very useful micro application for displaying dialog boxes and notifications from under the shell
Autoframerate script and LED display scripts displaying toasts via MSG
7. YouTube has been added with support for downloading and without ads.
8. Added control of the aero mouse, here's a - https://ru.aliexpress.com/item/MX3-...8b56b76aa14d0e57-1496145022581-08947-VnYZvQVf
Download Version 8.1:https://yadi.sk/d/psi-Vlnx3JfBBv
Version 8.5 of August 10, 2017
1. The firmware was made on the basis of the last official on December 17 (before that all were on the November version)
2. The firmware is completely deodexed.
3. MicroG services are cleaned and installed the latest versions of Google Services (official)
4. Xposed is removed as a braking system.
5. The latest versions of SuperSU (hidden RTH access), Bysybox and fixed time zones are installed.
6. Only the launch of the SAMBA server is left, who needs the rest (script autoframerate and LED display scripts output toasts via MSG) go Root Explorer by the way System/ETC/ Init.d and there we set the right 0755 on the scripts you want to start when the system boots.
7. Changes in the launch of the main application for DTV (now there is a countdown of 5 seconds and the start occurs automatically, what you ran last) and changes in the DTV application itself.
8. YouTube 4K for consoles (will appear if you install the firmware into a clean one with the removal of all data)
9. There are a lot of other additions and fixes.
Download Version 8.5:https://yadi.sk/d/IbJ9ihFR3LtKTc
Version 9.0 of 13/01/2018, Android 5.1 ONLY OLD KI Plus!
Android base from the factory firmware from August 18, 2017.
1. The provider's name is written to the root of the internal memory in the folder SDCARD\Picons\namesprov\ names.ini
We look in the InfoBar or in the Channel list number of the provider and then write his name.
Example file names.ini:
Code:
[settings]
112=NTV +
43001=GeoTelekom
253=Tricolor
2. The image of the provider must be copied to the folder SDCARD\Picons\Piconprov with the same name that you wrote in the names.ini file
For example :
Code:
NTV+ image name will be NTV+ .png
GeoTelekom image name will be GeoTelekom.png
Tricolor image name will be Tricolor.png
3. The satellite image must be copied to the SDCARD \ Picons \ Piconsat folder
The image name must match the satellite name in the DTV-Menu-Settings-Satellite List
For example :
Code:
Eutelsat 36A image name will be Eutelsat 36A.png
If the satellite name is a slash "/" then in the DTV-Menu-Settings-Satellite list, select the satellite and click Edit.
Write your satellite name without a slash.
For example, the satellite name was Eutelsat 36A/36B, then rename it to Eutelsat 36A and the name of the picture will also be Eutelsat 36A.png and the position
picture in the folder SDCARD\Picons\Piconsat
Download fully customized Picons for satellite 36, provider NTV + (suitable for other satellites, if the names match) -
https://yadi.sk/d/JmpykWjd3RRGNi
Unarchive. Copy the entire Picons folder to the internal memory of the device.
Download firmware 9.0, Android 5.1 ONLY OLD KI Plus!: https://yadi.sk/d/5ddJQ4Io3RRGNt
If you like my firmware and think that I'm wasting a lot of time to improve the firmware, then "Donate to Me"
Installation (standard):
A MicroSD - in FAT32, write it 3-4 files from the archive, turn the power off the map - in the box,
the bottom through the hole with a needle push button,
connect the power, after 5 seconds, release the needle - waiting for the end of the firmware.
The first boot will be more long.
Setting Weather - http://forum.xda-developers.com/showpost.php?p=69706785&postcount=53
K1 PLUS EDITOR Сhannels - http://forum.xda-developers.com/showpost.php?p=68260031&postcount=13
.
A big thanks , you do a great job, i have one question , we can adabt the firmware of ferguson avira combo 4K for impliment it in our K1 PLUS
ferguson-digital.eu/en/ferguson-ariva-4k-combo/
thank you for this great work
I think the solution is to adapt a firmware "wetek play 2" in which the same processor etc.
because with the original firmware lot of bugs and list of DVBS2 channels can not be classified
So it is best to work on another stable and brand as wetek or ariva
give this firmware "wetek play 2" now i know how to do
thnks
here for wetek play
wetek. com/downloads
the biggest dream is to run enigma2 [OpenELEC (Vitmos OS) ] but I think this is not your field?
hello pleas need enigma2
thank you for this great work
Hi,
THanks for your job!
Do you think if it works with the K2 plus?
It's the same only with 2gb and ram 16gb !
Would this work for the original K1 Plus S905?
Thanks Malaysk for the work you did with the firmware, it looks great from the screenshots you posted.
Could this be adapted to work with the original K1 Plus S905 (without DVB-S2/T2)?
They look mostly identical to me apart from the tuner. goo.gl / AjN6ts and goo.gl / cVbNB9 .
I am trying to make that Fake Wi-fi fix work with mine but I don't know where to start (found this goo.gl / g97Ngx) for Root, Xposed, etc.
I don't understand why the original firmware build doesn't have a checkbox similar to what they were able to put in that thread, so many apps check for wi-fi these days.
Since you already have Xposed in your build, this could be great step forward in getting there if they can't put it in the firmware itself.
(Sorry for the links, the forum policy thing prevents me from putting urls in my post)
Thanks!
Thank you very much
I have android 6 installed on my k1 combo very smoth and stable but unfortunately no dtv app inside is possible to install dtv app on android 6 or modifying or not??
Verstuurd vanaf mijn SM-G901F met Tapatalk
Perfect work. Thanks. If you could add oscam support to the dtv application or make the tvheadend backend working, I would donate 10 beers.
Thanks for your great job.
Could you add to firmware that it accept external bluetooth dongle?
And, it is possible made fav list with sat and tdt channels mixed as other combo receivers?
K1 PLUS EDITOR Сhannels
4PDA- http://4pda.ru/forum/index.php?showtopic=730111&st=1880
How to work:
By clicking on the button "Загрузка" you must choose "dtv_user_data" folder;
When you click on "Сохранить" - saves in the previously selected folder;
Removing the channel - the channel selected in the list, and press the Delete button (on the keyboard);
Moving the channel in the list up / down (buttons are located to the right of the channel list);
Possibly select multiple channels (but only in sequence), and move them;
It is necessary to add that you can also select multiple channels (either sequentially or through the Ctrl key in any order), and also remove the button Delete.
With the change of the order there is a nuance - normally only channel group will move that highlighted consistently. Those. if through the Ctrl key mark the channels in any order, the move will be a group that starts on the first selected, and ends on the last selected.
version 0.3
[+] Added context menu (right click), through which you can delete and move selected lines.
Moving rows to the specified position: select the channels we want to move (on Ctrl can be selected in a random order, not
necessarily in a row), press the right mouse button and select "Move". In the window that appears, specify the number of positions on which we want
move the selected channel and press OK. It made to speed up the channel grouping.
[-] Removed conversion;
[+] Cosmetic changes
[*] Working on the firmware to version from 25.06.2016.
version 0.4
[+] Added support for the new format (for firmware from 25.06.2016)
[+] Added the ability to convert between the formats from 06.25.2016 <-> 06.06.2016. To do this, you need to download the channel list and, at the bottom of the window (in the status bar, where a written format), select the format in which we want to convert.
version 0.4.2
[+] Remembers the last selected folder.
version 0.5
[+] Add to the list of channels on the satellite information (name, latitude, transponder data)
[+] Added the ability to edit the list of satellites. To do this, you must switch to "каналы/спутники" translate to "спутники" and download the list via the "Загрузить" button. The satellite list by double-clicking on the satellite, the transponder list will be thrown out (you can add / delete).
version 0.5.2
[+] Click "Группировка" is added to the context menu - the grouping of dedicated channels (takes all selected, and puts them behind the first selected). Allocate by CTRL.
version 0.6.0
[*] Changed almost all code
[*] The application design with multi-window interface with a tabbed interface
[+] Following function template (template includes favorite channels, regardless of the version of the channel list;
those. imposing a pattern on the channel list, favorites are restored)
[+] For foreigners added 2 languages - English and German (toggle through the "Help" menu item)
[+] To choose the audio track by default.
[+] Filter to use to search for the channel (s) (for example, when searching for 3 satellites (astra, hotbird, sirius) finds more than 4000 channels; look for scrolling through the list would take a lot of time, but knowing that the desired channel has a specific signature ( name, frequency, etc.), it is possible to apply a filter)
[+] Column indicating the channel type (HD, encrypted)
version 0.6.3.3
[*] Fixed bug with downloading the configuration to the receiver;
[*] Fixed a bug with the addition of transponders;
version 0.6.4.0
[*] Fixed bugs;
version 0.6.5.0
[+] Added support for T2 (until a minimum volume - rename, move, delete, and favorites);
[+] Added languages;
[*] Bug fixes.
version 0.6.5.1
[+] Added languages
version 0.6.5.3
[+] Changed the way display the channel list;
[+] To the channel list added drag & drop (the ability to drag and drop channels);
[+] Added languages
version 0.6.5.5
[+] Added the ability to check program updates (check carried out each time you start);
thank you for this tutorial.my k1 on dvb s2 .with DTV application I can not logged more than 4 server cccam . i managed to logged in to 5 but no more. you have the same problem ?
Sorry I use Google translate.
thanksK; can i install this rom in kII pro s2 t2?
Hi Malaysk, i know your custom firmware is for K1 PLUS, but i have Xtreamer MXV PRO (it's the same box....) i have try to install your firmware but i have this error :
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
you think is possible to bypass this error and your firmware work in this box ? or is totaly not compatible ?
because the xtreamer firmware is... VERY POOR !!!!
thank you in advance for your help.
Deki95 said:
Hi Malaysk, i know your custom firmware is for K1 PLUS, but i have Xtreamer MXV PRO (it's the same box....) i have try to install your firmware but i have this error :
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
you think is possible to bypass this error and your firmware work in this box ? or is totaly not compatible ?
because the xtreamer firmware is... VERY POOR !!!!
thank you in advance for your help.
Click to expand...
Click to collapse
You must install this firmware before instal firmware's malaysk
https://mega.nz/#!TwwkTJ7D!5UhmMkkO6...hcWfQn3eCjSKv0
OR this one with android 6.0 for K1 plus but without DTV
https://mega.nz/#F!lp4zyb6Z!-0y-n5ByZSgJKryRDgeOPw
futrist said:
You must install this firmware before instal firmware's malaysk
https://mega.nz/#!TwwkTJ7D!5UhmMkkO6...hcWfQn3eCjSKv0
OR this one with android 6.0 for K1 plus but without DTV
https://mega.nz/#F!lp4zyb6Z!-0y-n5ByZSgJKryRDgeOPw
Click to expand...
Click to collapse
this link no ok
https://mega.nz/#!TwwkTJ7D!5UhmMkkO6...hcWfQn3eCjSKv0
Please port rom for Ferguson Ariva 4K Combo to K1plus
Thank you for this rom.
Damage, restore DVB channels not working.
AMLogic S912 & S905 FAQ ✰ Fix Root, Hide SU, Backup/Restore... ✩ Media Player TV Box!
AMLogic S905 & S912 FAQ, Resources, Hints & Tips ✩ Fixing Root, Masking SU, Switch SuperUser (SU), Backup & Restore!
~ Android Media Centres, Streaming Players, Smart TV's & Multimedia TV Boxes ~
SUMMARY:
This topic provides help and assistance to users of all levels, giving access to resources for all AMLogic S905 and S912 media centers and TV boxes (and any other compatible devices), and provides detailed steps and examples - all fully-tested. I have writen my own documentation for myself and friends, so decided to simply cleaned it all up and pasted it here to share.
There is limited support for these Chinese no-name clones, so I hope this is helpful to others, and others will share their knowledge too!
Warning! Beware of S905W devices (e.g. X96 Mini). The "S905W" has inferior specifications, a crippled CPU (1.5GHz), has no 3D support (among other limitations and missing features). Always buy a S905x or S912 CPU device.
Tested on the following hardware specs: ($40-50 & $80-$120 AUD from Ebay/GearBest)
- CPU: Amlogic S905x Cortex-A53 Quad-Core 1.5GHz -&- AML S912 Cortex-A53 Octo-Core 2.0GHz.
- GPU: ARM Mail-450MP5 Penta-Core 750MHz -&- Mali-T820MP3 Tri-Core 750MHz. [I question these Chinese Specs!]
- RAM: 1GB, 2GB, 3GB or 4GB (DDR3\DDR4); FLASH 'ROM': 16GB, 32GB+ (EMMC).
- OS: Android 6.0.x Marshmallow.
Magisk Topics » Magisk Stable | Magisk Beta | Support Q&A
Downloads » Magisk Manager | Magisk Flashable | Magisk Clean-up v20180429 | v20180328
Requirements Magisk uses logging ('logd' service) to hide/mask root. Magisk Hide needs Kernel v3.8+ or newer (e.g. My Galaxy S5 uses v3.10.40 & X96 TV box has v3.14.29).
Troubleshooting Documentation, Wiki & FAQ | Magisk Hide Help | Diagnosing Magisk Issues
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FAQ, HINTS & TIPS ARTICLE INDEX
» How to Backup your Device & Data (w/o Modifying Stock Recovery/Boot).
» Magisk SU & Magisk Manager Root (w/o Modifying Stock Recovery).
» Replacing BusyBox & Optimal Systemless BusyBox Installation.
» Handy Resources & Useful Download Tools.
» Anti-Detection Methods: Masking Magisk SU Root & Renaming Magisk Manager.
» Magisk Hide Settings Lost & Not Saving (Re-Opening App / Reboot) - Troubleshooting Magisk Hide.
» Corrupt or Problematic Root? Re-Rooting!
» Backup Important System, Boot, Recovery & Data Partitions.
» How to Access TWRP Recovery W/O Modifying Recovery/Boot.
» Find & Locate your Stock Boot Image Backup Created by Magisk.
» BusyBox App or BusyBox Applets Installed on your Device.
» Masking BusyBox Modules and Applets.
» Google Play Store & Play Services - Old Versions, APK Backups & Archives.
» Google Play Store & Play Services - Errors, Issues, Fixes & Troubleshooting.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
HOW TO BACKUP YOUR DEVICE & DATA (W/O MODIFYING STOCK RECOVERY/BOOT)
I recommend backing up the partitions before making any changes to your default box. In fact, whenever you buy *anything*, always take a full backup before doing anything - yes, before connecting it to the Internet! Regardless if there is no important data there, ALWAYS make a backup!
Requirements:
Download Optimised AML S905 & S912 Media Player Bootable TWRP Recovery image (13.3MB): https://forum.xda-developers.com/attachment.php?attachmentid=4426811&d=1519210044 (attached at bottom of post)
Reasonable quality Micro SD Card (Class '4' or higher) w/ 2GB+ size formatted in FAT32 - run a disk check if any doubts or issues w/ card;
USB Storage (memory stick, external USB drive) - optional;
USB Input (cordless mouse & keyboard, as the "air mouse" remote sends you crazy! Get a Logitech K/B & Mouse w/ unifying dongle); and
Dismantle a ball-point pen and remove the long plastic ink nib section (or a kebab stick, tooth pick, paper clip);
Backup Procedure w/o Modifying Stock Recovery/Boot:
Stage 1. Access recovery w/o modifying stock device status.
1.1. Extract the Media Player compatible TWRP 'recovery.img' image from ZIP file (DO NOT RENAME FILE!).
1.2a. Insert a 2GB+ Micro SD card (Class [4] or higher) to Windows computer.
1.2b. Format Micro SD card on PC: untick "Quick Format" and select 'FAT32' (not 'FAT', not 'NTFS', not 'exFAT').
1.3a. Copy only the 'recovery.img' to the root of the Micro SD card (excluding any other files and folders).
1.3b. Safely eject the Micro SD card from computer and insert upside-down in the TV box.
1.4. Unplug the "AV" port cable (3.5mm audio socket) and A/C power from TV box. NOTE: May reset system date/time! TWRP Backups then have wrong time stamps!
1.5a. Carefully insert the long plastic ink ball-point pen nib/tip into the "AV" port and you will feel a button depress.
1.5b. Connect the A/C power cable to the TV box, while holding the button inside the "AV" port.
1.5c. Wait while device initialises and displays TWRP screen (Black & Blue TWRP interface).
1.5d. Release the pen ink nib NOW and reconnect the "AV" audio cable, if in use.
.
Stage 2. Perform a device partition backup.
2.1. From the on-screen TWRP menu, select "Backup" menu option.
2.2a. Select three most important partitions: "/boot", "/system", "/data" (untick "/cache").
2.2b. Check the required backup space "Total Size of All Data 3100MB" against the available space on selected backup volume (enable compression if req'd).
2.3. Click the GREY button at the bottom-left to specify backup location. Choose your USB stick (or Micro SD if sufficient free space).
2.4. Backup will now run. Do not walk away - watch the process for any errors. It will only take 3-8 mins (depending on amount of data and apps on the device). N.B. Check system temperature at top-left corner before executing backup. If you are concerned about heat you should monitor this (mine was really bad - floating around 69-72'c during backup).
Once complete it will be display in Blue text: "Backup Completed in 485 Seconds". Remove the Micro SD and reboot!
** Don't forget to install a better or light-weight Launcher! Try "Nova" or even "Microsoft" Launcher - both feature rich and easy-to-use!
** Don't forget to copy/move TWRP backups from SD card to PC, to restore any partitions in future!
** Don't forget to install "BK Disabler" to disable/remove all useless system packages plus disable their services to save memory and resources!
- - - - - - - - - - - - - - - - - - - - -
MAGISK SU & MAGISK MANAGER ROOT (W/O MODIFYING STOCK RECOVERY)
Connect your WiFi so that any auxillary files and updates can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free space. Allow for 1-3 hours to perform these steps. Do not rush!
Identify your device and save the essential details - see the tabs with most important information. Search for words like Build ID, Device, Model, Fingerprint, Baseband, Modem, Bootloader, CSC, etc. as these will give you most of the information you are seeking.
Download two of these "System Info" apps (unfortunately no one app covers all the information in one!) to perform a hardware and software audit of your device - personally, I use all three:
AIDA64 ("System", "CPU" & "Android" tabs.),
DevCheck ("Hardware" & "System" tabs. Has nice 'Charger Connect' counter and UI),
Device Info HW ("General" & "System" tabs.), and
SamMobile Device Info (General, Firmware & Android tabs)
Search DuckDuckGo/Google for a backup of your exact Bootloader and Build ID. This signifies a version that matches the OS and hardware variant. For example the 1st box I tested was a 1GB/8GB X96 Amlogic P212 ($40). All your finite and detailed specs are available within the System Info apps mentioned above (#1 A, B, C). Write down, export and screen shot your device's specs and details somewhere for quick reference.
For example, System Info output for my device:
Build: '20170622.19:55' in one app, but 'MHC19J' in another app (often letters & numbers and not a date w/ other hardware);
Fingerprint: 'Amlogic/P212/P212 6.0.1/MHC19J/20170622:userdebug/test-keys' (inc. make, model, device, OS, etc.);
Due to many of these Android media centres coming with a Faulty or Corrupt bundled Root, unknown SuperUser and an unlocked Bootloader - I highly recommend you either:
Flash the Magisk Combined Installer .ZIP through recovery;
backup the boot partition, extract (or download) the boot.img image, patch, then flash modified boot image .IMG through recovery; or
Install Magisk Mananger then click "Install" and select "Direct Method".
I had nothing but problems with Magisk Manager trying to take ownership and replace the corrupt SuperUser SU and SUD files (bundled with the device on delivery). For this reason, due to the boot and system partitions already being modified, I chose option "#3 A." - to flash the Magisk Flashable ZIP through recovery. However if you do have working root and an operational SuperUser, you may choose the fastest option of "#3 C.". Or if you can obtain a stock Boot image, then use option "#3 B.". The choice is yours and it really depends how messed up your device is!
Note: As many of these devices either come already rooted or are unstable, perform a full backup before installing or doing anything, so that if you make a mistake you can always revert back to that original state! e.g. An on-device backup, or backup via a PC with Google's SDK Tools (ADB) . Follow the steps above under "BACKUP YOUR DEVICE & DATA" from #1.1 to #1.5 for on-device backup instructions.
Scenario A) Stock ROM W/ Root Access
Download Magisk Flashable ZIP, Magisk Manager APK, and Magisk Uninstall ZIP onto your external storage.
Install Magisk Manager and launch the app.
Within the Manager UI, click "Install" button on screen and choose "Direct Install" method. Magisk will now attempt to install SuperUser and confirm root status.
No Errors? You are finished. Done.
Errors? Failed? If this fails, as it did for me, you need to follow the instructions above under "BACKUP YOUR DEVICE & DATA" from #1.1 to #1.5. to reboot into Recovery and perform a backup (w/o modifying Stock recovery/boot etc).
Follow steps to download the S905/S912 Backup & Recovery ZIP file (attached to bottom of topic) and prepare the Micro SD or SD Card or USB drive.
From the Recovery interface, where you performed your backup, return to the main menu and choose Install (Flash).
Now browse and select the previously downloaded Magisk ZIP file. Slide the right-hand-side button to proceed.
NOTE: If prompted whether you want to keep System partition "Ready Only", select "Keep Read Only" button to allow future OTA device updates.
. . . Trying to find MORE time to re-type & clean up notes . . .
Scenario B) Stock ROM W/O Root Access (or if Scenario A. fails)
Download Magisk Flashable ZIP, Magisk Manager APK, and Magisk Uninstall.
If your bootloader is locked (To-Do: reference process to check), you will need to first unlock it. Download the original boot image or backup your device, should you
need to undo your changes. Follow steps above to backup the device (selecting Boot or all partitions) and then extract the boot image once complete -or- download the original boot image and keep it handy.
Install Magisk Manager and launch the app (green mask icon with bits of white and blue).
Select Install from middle of screen, then from the pop-up click Install on the right-hand-side.
Choose "Patch Boot Image File" and you will be asked to navigate and browse to where you downloaded the original boot image (or performed the backup). Be very careful as you will not be prompted to confirm your selection!!!
Wait for the process to complete. Now reboot into the recovery on your Micro SD card.
From here you can choose Flash to flash the previously patched boot image from within the /MagiskManager/ directory.
Once complete, reboot the device and launch Magisk Manager. At the top of the screen it will verify the Magisk SU is install and up-to-date.
If you have any doubts, you may click "Install" again and verify the process completes successfully.
. . . Trying to find MORE time to re-type & clean up notes . . .
** Don't forget to install a better or light-weight Launcher! Try "Nova" or even "Microsoft" Launcher - both feature rich and easy-to-use!
** Don't forget to copy/move TWRP backups from SD card to PC, to restore any partitions in future!
** Don't forget to install "BK Disabler" to disable/remove all useless system packages plus disable their services to save memory and resources!
- - - - - - - - - - - - - - - - - - - - -
REPLACING BUSYBOX & OPTIMAL SYSTEMLESS BUSYBOX INSTALLATION
What exactly is this whole Busy Box thing? Well ... BusyBox is this unified bundle of over 300 common Unix commands (as applets) forming an 'Android Swiss Army Knife' (as it is commonly referred as) that replaces and adds standard Linux functions on your device, so that you can have greater control over your device - just like a PC with Linux OS. This 'toolkit' was specifically built to accommodate embedded OS devices with limited resources to work with the Linux Kernel. It is FREE software under the GNU, however various developers create easy-to-use BusyBox installers which are available both free or paid online.
Due to many of these devices coming pre-installed with BusyBox and old/outdated bundled Applets, there can be confusion with what does or does not work. Therefore it is very important to determine what state your device is in (again writing down what works or does not) and take a backup before making changes. In recent years, developers have added code to their programs to detect BusyBox and 3rd party apps, just like other root methods. Therefore it is *highly* recommended you migrate away from the standard/bundled BusyBox and move to the Magisk 'Systemless' version of BusyBox that makes no changes to your /System partition and does not mount it 'RW'.
Please direct your thanks to @osm0sis - a truly valuable community member.
Requirements:
Download Stericson's BusyBox installer 'Free/Pro' (or reputable alternative) [https://play.google.com/store/apps/details?id=stericson.busybox].
Have already flashed 'Magisk Flashable ZIP' to gain Root; or installed 'Magisk Manager' v12+ (replaces BusyBox App & SuperUser Manager) and flashed 'Magisk' SU v5.6+).
Install two or more of these excellent system info apps from the Android "Play Store" to audit and display system info (OMG! I am over calling it Google "Play"! It's the Android Market!):
AIDA64 (System, CPU & Android tabs);
DevCheck (Hardware & System tabs);
Device Info HW (General & System tabs); and
SamMobile Device Info (General, Firmware & Android tabs).
BusyBox Procedure:
To begin, download and install Stericson's BusyBox installer (link above).
Launch the BusyBox app, click "Grant" to the root request, and wait for 2-3 minutes while the app initialises for the first time.
At the top of the screen it will show your current BusyBox version and details. At the bottom-left of the screen, click "Install" to update. It will automatically update and perform maintenance on SymLinks, fixing any issues for you.
Exit BusyBox and re-open. Now click "Uninstall" at the bottom-right and click "Uninstall" again saying yes you understand.
Now your system has no BusyBox! Some background services may complain but this will only be for a few minutes.
Open Magisk Manager and swipe open the left-hand side-menu and click Modules.
You will now see your currently installed (active/disabled) modules plus the latest versions of other Magisk-compatible modules below.
Click the Search icon at the top-right and search for 'busybox'. You should find "Busybox for Android NDK" (ignore the "NDK" part).
This is the Magisk recommended Systemless BusyBox module managed by XDA member 'Osmosis' @osm0sis. Click the Row for more information or click the Download icon then "Install" on the right-hand-side to begin. Once complete, without any errors, click "Reboot". If you experience any errors just reboot and try again or click save and examine the logs.
Now open one of the three 'System Info' apps (listed above) -OR- re-open the BusyBox installer app again. This will allow you to determine your BusyBox name and version! If everything was successful, you should see something like "BusyBox v1.23.4-OsMoSiS" with path "/system/xbin/".
All Done!
When an app requests SU and BusyBox access, Magisk SuperUser will prompt to grant or deny this request, then if accepted, automatically serves the Systemless BusyBox environment to the requesting app. Amazing!
If you have any issues, please use the Magisk Manager support topic and attach all related logs.
- - - - - - - - - - - - - - - - - - - - -
HANDY RESOURCES & USEFUL DOWNLOAD TOOLS
Below are some handy tools you should download and have ready on the external Micro SD Card and your PC's HDD. This list is far from complete and will be updated by member suggestions! The list includes a short description plus links to further details, support, downloads and dates they were last updated. If you know an Android or Windows app that is *essential* for use, please feel to post it here, and I will add it to the list. Thanks!!
Where is the AMLogic Website? Site shows compatible OS versions, hardware specifications w/ chipset, memory RAM, CPU & frequencies, etc. Click around and you will find all sorts of info, e.g. Email address mbox-android[@]amlogic.com
» http://openlinux.amlogic.com/Android/Mbox (Strange 'S905x' is planned for OS v8 but the 'S912' is not planned beyond OS v7??)
AMLogic S912 & S905 Toolkit [Bundled Fastboot, Flash, Burn, Port, Backup] (Tool & Drivers) - IMPORTANT! Combined toolkit to flash, backup, convert recovery images and restore ALL AMLogic AML S912 & S905 TV Boxes remotely from your PC. Read more...
AMLogic Network Flash Tool [Bundled ADB & FastBoot] (Tool & Drivers) - IMPORTANT! Ability to flash, backup, convert recovery and restore AMLogic Media Player TV Boxes remotely over the network (LAN Cable or Wireless/Wi-Fi). Always backup prior to upgrading/downgrading! Capable of backing up, restoring and converting any other device's TWRP Recovery. Read more...
» https://mega.nz/#!AII2TB6R!Tk8SS9RUZbFHF9Nwl2H27fD_z54o6Ph2nSlK-JdlZDc [2018.02.24 v1]
AMLogic USB Burning Tool v2.1.6 [Device Re-Imaging] (Tools) - IMPORTANT! This tool allows you to Flash (or "Burn") an update to AMLogic Media Player / TV Boxes using a USB Type-A to Type-A cable. Ability to "Burn" (Flash) and upgrade your device. Please always backup prior to updating!
*Warning!* Wipes ALL device data!!! Use *.img files only, not *.zip files!
» https://mega.nz/#!8ZJTETzL!cdPql9YqK0GGT-xhCfplCVI7b-d0xR-nH5tDIhdeZEg [2018.03.07 v2.1.6]
» https://mega.nz/#!RcglgLrK!0rLQQP_kWCQsLbyAoBBvxFpPsy47A2KP0ycLX1FzgPI [2017.08.14 v2.1.2]
TeamWin TWRP S905 S912 Recovery (Bootable) - IMPORTANT! [Micro SD Boot 100% Guaranteed!] Use to access TWRP recovery without modifying your recovery partition. Frequently updated alternate recovery project. The most suitable recovery will depend on your device! If you cannot boot into TWRP recovery, you will need to learn your Device's Model/Fingerprint/Bootloader/Modem/CSC. Check the XDA Forums relevant for your device and custom Recovery solutions listed. Flashing will modify your Stock Recovery - this is not recommended should you wish to perform OTA firmware updates and use 3rd party apps that circumvent modified/rooted device detection (Spotify, Netflix, Stan, etc.). Be sure to take a backup of ALL IMPORTANT partitions, plus separate backups of EVERY partition too.
» https://mega.nz/#!4Mx2wSbQ!G-Vws-Xv1KfKLMg2MytoroMik_5MBVc4IZ4c7SfCpZE [AmLogic-specific S905 & S912, TWRP v3.0.2]
Odin3 for Windows - Flash various types of firmware for your device - e.g. modem, boot, system, etc. Odin can push OTA manufacturer and third-party signed/unsigned software updates / patches to devices via USB. e.g. Flash Radio to resolve various issues, or flash and restore the original to resolve custom ROM issues. Please visit the Odin3 thread by ChainFire for support. Read more...
» Odin3 v3.09.0 [2013.06.21] | Odin3 v3.09.5 [2014.03.12] | Odin3 v3.11.1 [2016.05.13] | [url=https://mega.nz/#!NJxxCbAS!EE1zGsa200NiR5RaPlAV7e4ac8YCslgELZAfxepNRJo]Odin3 v3.12.7 [2017.05.06] | Odin3 v3.12.10 [2017.11.01]
Fix Permissions v2018.04.15 by Osm0sis [Repair Micro SD & TF] Flashable - Repair and fix both file and directory errors/corruptions with ownership and permissions. Flash the signed package to execute. [URL=https://forum.xda-developers.com/showthread.php?t=2239421]Read more...
» https://mega.nz/#!wRYiSZ6K!8DVVq5v9KFsu0kkciqtla156l7nlYFCVy0QssuE8Qvw [2018.04.15]
ADB & FastBoot Drivers [Windows Mac Linux] (Drivers) - Essential if pushing, pulling and backing up device content & partitions. Familiarise yourself and bookmark the command examples on ADB + Fastboot. You will need to verify your Device's Model/Fingerprint/Bootloader/Modem/CSC BEFORE flashing. Enter commands via command prompt - for example, to push new recovery image: "fastboot boot xyz-recovery.img". Read more...
» OS Selection: Windows | Linux | MacOS
» https://mega.nz/#!EB4C3bwR!d7jO4ngpCxSsDc21ZA5l2dhDNbXnXTKFVspA8uCmUs0 [2017.12.13 Win v27.0.1]
Root SU Uninstaller by Magisk - Un-Root & Clean-up (Flashable) - IMPORTANT! UnRoot / DeRoot and reverse system modifications from Magisk SU, SuperSU and other 3rd party rooting tools. Excellent tool for removing corrupt Chinese root to install Magisk SuperUser and Magisk Manager or SuperSU. Read more...
» http://bit.do/magisk-uninstaller-flashable-zip-20180429 [Latest! Dev Link]
» https://mega.nz/#!xZInDJSQ!l_Kl-NcHvwAUEu9kC8UbH9sm14EcAzMrHFutREl4BVs [v20180429]
» https://mega.nz/#!ABJU1Jza!6xYhQn_RGJGCpQRTzX4CvDqli351p-uc28KXCX5SSkA [v20180222]
» https://mega.nz/#!4Bwn0azK!fc9roBz32eTkbJ1POy5OcsHOGTKkFShQz515PlQ4KXY [v20180113]
Osm0sis UnSU Un-Root & Clean-up (Flashable) - UnRoot and restore modified system files correctly from half a dozen 3rd party root methods. See also the Magisk Uninstaller above for more up-to-date solution should this not work. Read more...
» https://mega.nz/#!gUZhXbTD!bUGGnnDuqCRPhYoYsTOZJBWlP9B3MbroCc3vUxOgGiE [2018.02.06]
CleanupSU (Flashable) - Cleans up all leftover SuperUser files that might be laying around. Perform every time you need to re-root. See also the Magisk Uninstaller above for more up-to-date cleanup solution.
» https://mega.nz/#!MNpUjaTZ!VYBOQRfelzrFVSWdxGZdMKgY6pTa-kgJJPdfygmjblw [2016.11.03]
SUMount (Flashable) - For use with either 'Systemless' root options: @topjohnwu's Magisk SU -or- Chainfire's SuperSU. Toggles mounting of 'magisk.img' & 'magisk_merge.img' or 'su.img' to access their file systems for manipulation (ADB Shell, Aroma File Manager, TWRP Terminal or TWRP File Manager, etc.). Read more...
» https://mega.nz/#!lYZmhIga!TSE-l519X2-AUNbdPnfpzGI244TJRYGpWM9IG4HoPhE [2008.02.28]
TeamWin TWRP Recovery (Flashable & Bootable?) - NOT TESTED!! UNTESTED!!! You can always try booting (not flashing) from this recovery image if the AML S905/S912 Recovery above does not work. I recommend you learn your Device's Model/Fingerprint/Bootloader/Modem/CSC. Be sure to take a backup of ALL Important partitions. Read more...
Philz Touch Recovery [Database of Devices] (Flashable & Bootable?) - NOT TESTED!! UNTESTED!!! You can always try booting (not flashing) from this recovery image if the AML S905/S912 Recovery above does not work. I recommend you learn your Device's Model/Fingerprint/Bootloader/Modem/CSC. Be sure to take a backup of ALL Important partitions. Read more...
» https://mega.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw
Want to backup your device's Recovery? Want to restore another device's Recovery? Want to use it for another Media Box? Try the nifty little tool called: AMLogic Network Flash Tool! (see above) Note: I have not tested with RockChip media boxes (RK3328 RK3368 RK3399).
- - - - - - - - - - - - - - - - - - - - -
More hints and tips to come as I find time to document them:
» SafetyNet issues...
» Google Play Store & Play Services - Errors, Issues, Fixes & Troubleshooting.
Found this useful? Click the [:good: Thanks!] button below!
Cheers!
.
General Support - TV & Media Boxes, Magisk Root, Backup, Restore, Play Services, etc.
Continued.....
- - - - - - - - - - - - - - - - - - - - -
ANTI-DETECTION METHODS: MASKING MAGISK SU ROOT & RENAMING MAGISK MANAGER
Two features 'Magisk SU Root Masking' labeled as "Magisk Hide" -and- 'Magisk Manager Rename' labeled as "Hide Magisk Manager". This can be confusing and the sequence of these options are in reverse order, than what I would have thought. Enabling 'Magisk Hide' detection system is *usually* sufficient for most scenarios with problematic Catch-up TV apps, Banking apps, Google apps, Music services (Spotify, etc), Anti-tamper Game hacks, and so on. A better word to describe what Magisk Hide does would be 'masking' or 'cloaking' its presence from other apps.
For further assistance, access the Magisk Hide FAQ: https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
» Activate Magisk SU ROOT Masking (i.e. Magisk Hide)
What does it do? It masks detection of the presence of SU from selected apps. This feature will activate a hidden option in the left menu. When opened it allows you to select various applications to BLOCK detection from these apps from recognising system has been compromised and has SuperUser + ROOT.
Magisk SU ROOT Masking Steps:
Always Backup! Take a full backup using TWRP app, or alternatively via "recovery.img" (attached & already discussed).
Launch Magisk Manager (round green mask icon).
Slide open the left menu by swiping left-to-right. Click Settings.
Scroll down to yellow 'MAGISK' section.
Enable "Magisk Hide".
Close Magisk Manager. Open Magisk Manager. Slide open the left menu by swiping left-to-right.
Select 3rd option "Magisk Hide" and begin selecting which apps to "Cloak" or "Mask" Root to prevent detection.
NOTE: Do you find after closing Magisk Manager or rebooting, that "Magisk Hide" disappears from the left menu and is disabled in settings? See Magisk Hide Troubleshooting steps below to resolve!!
» Activate Magisk Manager Package Rename (i.e. Hide Magisk Manager)
What does it do? Should you have issues where an app is circumventing the Magisk Hide feature (above), you can use the Magisk Manager Package Rename feature (ironically named "Hide Magisk" just to confuse you!). The feature creates a cloned APK file of Magisk Manager but with a random package name ('com.XxXxXxXxXx' instead of 'com.topjohnwu.magisk') and installs it, then automatically removes the original Magisk Manager app to avoid detection.
If you proceed with Hide Magisk Manager (Rename) there are a number of inherent limitations. Research on the forums first to fully understand the consequences of this feature. For example, Magisk Manager check for updates fail, automatic update notification is unavailable, re-install Magisk Manager unavailable, plus numerous other restrictions.
Magisk Rename Steps:
Always Backup! Take a full backup using TWRP app, or alternatively via "recovery.img" (attached & already discussed).
Launch Magisk Manager (round green mask icon).
Slide open the left menu by swiping left-to-right. Click Settings.
Under the yellow 'GENERAL' section.
Click "Hide Magisk". *NOTE* There is NO CONFIRMATION prompt!
Wait 1-2 mins and Magisk Manager will close automatically.
Open Magisk Manager (same round green mask icon). You can now check the new package name.
Under settings where you selected "Hide Magisk" is now a "Restore Magisk Manager" option to restore the original package (e.g. for Magisk updates or modules).
What does the Uninstall button do?
When removing Magisk & Magisk Manager there are three options:
Remove the "Manager" app only = "Uninstall App";
Restore stock/original Boot image for OTA Updates = "Restore Images";
Clean-up & removes Magisk SuperUser, Modules & Manager = "Complete Uninstall".
Magisk Topics » Magisk Stable | Magisk Beta | Support Q&A
Downloads » Magisk Manager | Magisk Flashable | Magisk Clean-up v20180429 | v20180328
Requirements Magisk uses logging ('logd' service) to hide/mask root. Magisk Hide needs Kernel v3.8+ or newer (e.g. My Galaxy S5 uses v3.10.40 & X96 TV box has v3.14.29).
Troubleshooting Documentation, Wiki & FAQ | Magisk Hide Help | Diagnosing Magisk Issues
- - - - - - - - - - - - - - - - - - - - -
MAGISK HIDE SETTINGS LOST - TROUBLESHOOTING MAGISK HIDE
Magisk Hide (Masking Magisk SuperUser) - 2 Solutions w/ Magisk Hide being disabled after reboot or closing and re-opening Magisk Manager.
If you are using Magisk Manager and Magisk Root and are experiencing difficulty with Magisk Hide (Masking Magisk's SU) not showing in the Manager's side-menu or remembering its status in settings, it occurs when a file is not automatically deleted and removed.
PROBLEM:
Open Magisk Manager, Settings >> Enable Magisk Hide, close Manager, re-open and Magisk Hide is disabled and not visible (hidden) in the left side-menu. i.e. Exit, Close, Stop, Re-Open & Reboot Reset's Magisk Hide's State to Disabled.
SOLUTION 1.
Force stopped Magisk Manager.
Backup then Delete file /data/property/persist.magisk.hide (0600).
Launch Magisk Manager.
Go to Settings >> Enable Magisk Hide.
Go back to Manager home screen. Swipe to reveal side-menu and check Magisk Hide menu is visible.
Close Magisk Manager or Force stop.
Reopen and Swipe side-menu and confirm Magisk Hide is still visible!
I hope this helps others also experiencing issues with Hiding Super User SU. Thanks Shak!
SOLUTION 2.
Another fix @dunderball posted Dec 2017 was in regards to an error "fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory"
The issue is due to Magisk Manager being unable to save the list of ticked Apps to hide from SU to /magisk/.core/magiskhide/hidelist.
Check the existence of the "/magisk/.core/magiskhide/hidelist" path.
Create the "/hidelist" directory.
CHMOD "/magisk/.core/magiskhide/hidelist" to 0644.
Thanks go to @dunderball. :highfive:
SOLUTION 3.
If you are using an old device or perhaps an old ROM with custom Kernel, you may find Magisk does not work. Magisk Manager & Magisk SuperUser requires a Kernel with version v3.8.x or newer.
Check your device forums on XDA for assistance.
SOLUTION 4.
Magisk Hide will not function if you have disabled your 'logd' service, or your have set your log threshold to 0 bytes. Magisk requires to examine the logs in order to hide the selected apps from root status. Enable and start the 'logd' service and try again! Solution 5 also discusses the importance of the Logging service.
SOLUTION 5.
Magisk anomalies, problems with diagnostic logs and non-functioning Magisk Hide.
ATTENTION: If you are experiencing diagnostic and logging issues (e.g. blank or no debug logs created in "/data/adb/Magisk/") or you are experiencing some anomalies after enabling Magisk Hide, please be aware v15.4+ of Magisk Manager checks and verifies if the "LOGD" diagnostic logging service is running. Devices NOT using the 'logd' service for logging will therefore NOT be able to successfully have "Magisk Hide" enabled and functioning.
If you really wish to use this feature, then I recommend:
Performing a backup of your data, important partitions and system state;
Flash Magisk Uninstall ZIP (link available above & on Magisk topic); and
Flash Magisk v15.31 ZIP to allow enabling the Magisk Hide feature.
Disable the check for updates option within Magisk Manager settings to prevent accidental upgrade until the issue is fixed by @topjohnwu.
Magisk Topics » Magisk Stable | Magisk Beta | Support Q&A
Requirements Magisk uses logging ('logd' service) to hide/mask root. Magisk Hide needs Kernel v3.8+ or newer (e.g. My Galaxy S5 uses v3.10.40 & X96 TV box has v3.14.29).
Troubleshooting Documentation, Wiki & FAQ | Magisk Hide Help | Diagnosing Magisk Issues
- - - - - - - - - - - - - - - - - - - - -
CORRUPT OR PROBLEMATIC ROOT? RE-ROOTING!
Restore to factory defaults does *not* work on these devices. It will NOT restore root or any 'destructive' actions made on the OS and to any apps. The great thing about MagiskManager is that it can co-exist with SuperSU, however it will not truly be hidden and invisible. If you do mix-and-match SuperUser's then make sure you use their method for hiding, e.g. search for Hide SuperSU by ChainFire.
Depending on how 'destructive' your previous actions were on the device, you should have a 'close to original' stock System partition and a copy/backup of the *Original* device's Boot Image. There are two things you can try when either root, SU, permissions or something else is corrupt:
flashing the Magisk Uninstall ZIP to un-root your device to perform a clean-up and proper removal; or
try restoring (flashing) the stock/original untouched device Boot Image via TWRP.
Once you confirm things are stable and working, you can then either:
Launch MagiskManager and click Install and choose 3rd option, Direct Method;
flash Magisk via TWRP again; or
Launch MagiskManager, click Install and choose 2nd option, browse for your stock Boot image and then flash the updated image via TWRP.
Requirements:
With either the Stock Standard or a Custom Recovery:
Download the S905 & S912 Media Player Bootable TWRP Recovery image (13.3MB): https://forum.xda-developers.com/attachment.php?attachmentid=4426811&d=1519210044 (attached to above post)
Reasonable quality Micro SD Card (Class '4' or higher) w/ 2GB+ size formatted in FAT32 - run a disk check if any doubts or issues w/ card;
USB Input (cordless mouse & keyboard, as the "air mouse" remote sends you crazy!);
Dismantle a ball-point pen and remove the long plastic ink nib section (or a kebab stick, tooth pick, paper clip); and
Attempt to fix and repair all file, directory and application permissions by booting into TWRP and selecting "Fix Permissions".
Options and Procedure:
# Magisk
Flash Magisk ZIP installation script.
Boot into TWRP recovery via 'recovery.img' on Micro SD card.
Take a full device backup.
Flash Magisk latest stable or beta ZIP.
Magisk Manager will be re-installed automatically.
Alternatively,
Open Magisk Manager and click "Install" at the bottom of the screen.
# SuperSU
Flash SuperSU ZIP installation script.
Boot into TWRP recovery via 'recovery.img' on Micro SD card.
Take a full device backup.
Flash SuperSU latest stable or beta ZIP.
# ChainFire
Flash ChainFire ZIP installation script.
Boot into TWRP recovery via 'recovery.img' on Micro SD card.
Take a full device backup.
Flash CF Root ZIP.
NOTE: Cannot flash via ODIN w/ standard Micro USB cable due to Media TV Boxes not having USB peripheral 'host' ports. You will need to buy a USB type-A to type-A cable for this to work - compatibility will be device dependant ($5 investment on Ebay). If you are more comfortable with Odin, you can flash either a 3rd Party Recovery (temporarily) or Stock Recovery in the "AP" slot (*.tar or *.tar.md5) - always backup first! I have not tested any WiFi ADB tools or flashing with "FlashFire", "Rashr" or "Flashify" (Odin update) - should essentially work once you have root access...
The process is essentially the same as the process to root. However you simply select a different SU ZIP to flash. There is ample documentation available for using TWRP. Please DuckDuckGo/Google your specific root method and TWRP if you are unsure.
If you do receive an error and the process does not complete, copy the log to your card and try again. Fails again? Examine the logs and look for any errors.
WHAT IF? If this all fails, try using ChainFire's "UnSU ZIP script" -or- Magisk's "Uninstaller ZIP script" and flash either via TWRP to clean-up the system. Alternatively, you could use TWRP to flash the stock boot/recovery/system partitions -OR- use TWRP to Factory Reset (after backing up all data!!), and then begin the Magisk Root steps from scratch!
Magisk Topics » Magisk Stable | Magisk Beta | Support Q&A
Downloads » Magisk Manager | Magisk Flashable | Magisk Clean-up v20180429 | v20180328
Troubleshooting Documentation, Wiki & FAQ | Magisk Hide Help | Diagnosing Magisk Issues
- - - - - - - - - - - - - - - - - - - - -
BACKUP IMPORTANT SYSTEM DATA & PARTITIONS
Prior to installing lots of apps or making any system changes, it is *always* advised to take regular full backups, plus backup of your Boot and Recovery. If you cannot find the original ROM images easily online (e.g. obscure media player device, non-existent version numbers) then perform a backup within TWRP app or boot into recovery. It is *highly* recommended you have Stock backups prior to performing any actions that may affect the boot partition (inadvertently).
Backup Boot & Recovery Partitions:
If you DO NOT have Root, follow the Backup instructions above under "HOW TO ACCESS TWRP RECOVERY W/O MODIFYING RECOVERY/BOOT" (below) to access the backup recovery environment.
If you DO have Root access - download, install and open TWRP (has a stupid name "Official TWRP App"), click 2nd option "Backup Existing Recovery".
Perform two backups: first enter a meaningful "Device Recovery Backup" file name and click "Backup Recovery"; then repeat for the "Device Boot Backup" and update the backup file name.
The backup should complete within a few seconds, depending on its size and destination.
To restore, follow the same steps via TWRP app, or alternatively boot to the 'recovery.img' (attached & discussed above) and choose TWRP Flash restore, browse and select the backup, then select which partitions you wish to recover.
- - - - - - - - - - - - - - - - - - - - -
HOW TO ACCESS TWRP RECOVERY W/O MODIFYING RECOVERY/BOOT
Requirements:
Download the AMLogic S905/S912 TWRP Bootable Recovery image (13.3MB): https://forum.xda-developers.com/attachment.php?attachmentid=4426811&d=1519210044 (attached to above post)
Reasonable quality Micro SD Card (Class '4' or higher) w/ 2GB+ size formatted in FAT32 - run a disk check if any doubts or issues w/ card;
USB Input (cordless mouse & keyboard, as the "air mouse" remote sends you crazy! Get a Logitech K/B & Mouse w/ unifying dongle); and
Dismantle a ball-point pen and remove the long plastic ink nib section (or a kebab stick, tooth pick, paper clip);
TWRP Procedure:
1. Extract the Media Player compatible TWRP 'recovery.img' image from ZIP file (DO NOT RENAME FILE!).
2a. Insert Micro SD card (Class [4] or higher) to Windows computer.
2b. Format Micro SD card on PC: untick "Quick Format" and select 'FAT32' (not 'FAT', not 'NTFS', not 'exFAT').
3a. Copy only the 'recovery.img' to the root of the Micro SD card (excluding any other files and folders, unless flashing the firmware).
3b. Safely eject the Micro SD card from computer and insert into TV box.
4. Unplug the "AV" port cable (3.5mm audio socket) and A/C power from TV box. NOTE: May reset system date/time! TWRP Backups then have wrong time stamps!
5a. Carefully insert the long plastic ink ball-point pen nib/tip into the "AV" port and you will feel a button depress - don't let go!
5b. Connect the A/C power cable to the TV box, while holding the button inside the "AV" port.
5c. Wait while device initialises and displays TWRP screen (Black & Blue interface).
5d. Release the pen ink nib NOW and reconnect the "AV" audio cable, if in use.
Done. Rock and roll!
Now perform any TWRP functions - backup, restore, fix permissions, flash, etc.
NOTE: If you wish to install vendor OTA updates, I recommended you continue using TWRP (or other solution) via Micro SD Recovery and the TWRP Android app. Otherwise, if you flash TWRP (or other recovery) you will need to take extra steps to re-flash your Bootloader prior to any updates, then flash again, and again afterwards.
- - - - - - - - - - - - - - - - - - - - -
FIND & LOCATE YOUR STOCK BOOT IMAGE BACKUP CREATED BY MAGISK
Whether you initially used the Magisk Manager app -or- TWRP Recovery \ ADB FastBoot \ Odin3 to flash the Magisk patched boot image, a backup copy of the existing stock boot image is stored in "./data/" as "stock_boot.img".
However, if you flash an already Magisk patched "boot.img" through ADB FastBoot (Download Mode), then neither a "stock_boot.img" backup will be created or existing backup overwritten. Magisk detects the active boot image as already patched, therefore you must manually create a backup if you wish to retain the existing boot image.
Note: When patching a stock boot.img and flashing via Magisk Manager, the backup of the stock boot image is temporarily held until the next reboot in: "./data/user/0/com.topjohnwu.magisk/install/stock_boot.img".
If you are struggling to locate the file, access an on-device terminal emulator, type "SU" and enter: "find -name 'stock_boot*'".
- - - - - - - - - - - - - - - - - - - - -
BUSYBOX APP OR BUSYBOX APPLETS INSTALLED ON YOUR DEVICE?
Download, install and open your Busybox app. We will only use the "Uninstall" component of this app to clean-up any Busybox applets and remnants left behind.
If you have any corruptions in BusyBox preventing removal, first click "Install" to update, and then click "Uninstall".
Once complete, you may uninstall your Busybox app as is no longer required!
MASKING BUSYBOX MODULES AND APPLETS
Open Magisk Manager. Slide open the left menu by swiping left-to-right.
Click the "Downloads" menu item.
Scroll down the list and looks for something like "Busybox NDK" or similar.
Read the module description. Click Install and follow the steps.
Slide open the left menu, select the "Modules" menu item to see the list of (active/inactive) installed modules (you may tick/untick a module to temporarily disable it, or click the trash icon to remove and uninstall it completely).
You should now see the 'BusyBox NDK' systemless module installed.
- - - - - - - - - - - - - - - - - - - - -
GOOGLE PLAY STORE & PLAY SERVICES - OLD VERSIONS, APK BACKUPS & ARCHIVES
Normally most Android devices have a "Vending.apk" as their Google Play Market package. However some devices use a different package name for Play Market and Play Services packages e.g. "Phonesky.apk" or "Velvet.apk".
In order to upgrade Play will depend on your system. Installing an updated Phonesky.apk will work. e.g. I updated my unstable Google play from v6.0.1 and Play Services with the following packages:
- Play Store v6.0.5 as 'com.android.vending' in "./system/priv-app/Phonesky/Phonesky.apk"
- Play Services v8.4.89 as 'com.google.android.gms' in "./system/priv-app/PreBuiltGMSCore/PreBuiltGMSCore.apk"
Updating Google Play and Play Services options:#1. use any root explorer (Solid Explorer, FX Explorer, ES Explorer, Root Explorer) to rename (backup) and replace the "Phonesky.apk" and "PreBuiltGMSCore.apk" packages;
#2. flash the updated Play Market or Play Services ZIP package via Magisk Manager;
#3. flash the updated Play Market or Play Services APK package via Recovery; or
#4. flash via ADB FastBoot (please search the XDA forums for examples [ADB, FastBoot, Push/Pull]).
IMPORTANT! Always backup your existing APK files (both system and manufacturer apps!).
If you wish to Disable Apps do not use a Root App Uninstaller. Instead, use a systemless application disabler with your systemless root - e.g. Magisk Manager + App Systemizer module. This will allow you to achieve the temporary removal of system apps without modifying the /system/ partition. Why is keeping the System image original and stock important? If you modify the system partition (mount RW, delete an app, or make any changes) it will cause future issues and prevent updates when you wish to upgrade your OS or perform an OTA update.
» Google Play Services APK
Before installing any random version of Google Play Services, you must first make sure it matches a number of variables to prevent conflict on your device (Android TV, Mobile Device, TV Box, etc) and the corresponding OS etc. To do this, expand the box below but clicking "Un Hide".
To determine the suitable version of Google Play services for your Android device, go to Settings » Apps » Google Play Services (or Play Services). Here you will see the size, memory use and the version. Observe the three digit 'xyz' sequence 'v##.#.# (xyz-#########)'.
For example: Play Services v11.0.45 (430-155874144)
The 'xyz' here shows '430' which will represent which 'variants' of Google Play services that are compatible with your device. Therefore "430" represents:
X = "4" = if OS 5.0, 5.1 = Play Services v7.9 and older -OR- if OS 6.0+ = Play Services v8.0 and onwards.
Y = "3" = armeabi-v7a ARM CPU.
Z = "0" = Universal and can be used on any device with high or low DPI.
Example 3 Digit Prefixes:
430 = Android >=6.0; armeabi-v7a; NoDPI/Universal device;
046 = Android <5.0; arm64-v8a CPU; Max 320dpi device;
876 = Android TV; x86 CPU; Max 320dpi device;
940 = Android >8.0; arm64-v8a CPU; NoDPI/Universal device;
438 = Android >=6.0; armeabi-v7a CPU; Max 480dpi device;
Download All Versions of Play Services:
- TV Versions: https://www.apkmirror.com/apk/google-inc/google-play-services-android-tv/
- Standard: https://www.apkmirror.com/apk/google-inc/google-play-services/
View further information on these 3-digit prefixes:
STATUS: Work In Progress!
Code:
ANDROID TV & GENERAL GOOGLE PLAY SERVICES COMPATIBILITY FINDER
X represents the Android OS version:
'0' = Android <5.0 (pre OS 5.0.x. e.g. OS 4.3)
'2' = Android 5.0 and 5.1 starting with Play Services v8+
'4' = Android 5.0 and 5.1 before Play Services v8, Android >= 6.0 after
'5' = Android Wear OS
'7' = Android 5.0
'8' = Android TV
'9' = Android 8.0+
Y represents the CPU Architecture:
'1' = armeabi
'3' = armeabi-v7a
'4' = arm64-v8a
'5' = mips
'7' = x86
'8' = x86_64
Z represents the Screen 'dots per inch' (DPI):
'0' = Universal or "NoDPI" restrictions.
'2' = Max 160 dpi
'4' = Max 240 dpi
'6' = Max 320 dpi
'8' = Max 480 dpi
OS Changes & Play Services Notes (exclusions):
- With Google Play services v6.5+, builds migrated from '7yz' to '4yz'. Therefore, if you were on '7yz' with Play Services 6.4.x AND now have Play Services v6.5+, then the prefix changes to '4yz'.
- With Google Play services v8.0+, '4yz' builds were split into '2yz' for Lollipop OS, and '4yz' for Marshmallow OS. Therefore, if OS is Lollipop v5.x AND Play Services v8.0+ used, then the prefix changes to '2yz'.
- Please be aware the "Android TV" does not refer to ALL Android TV's or TV Boxes, but refers to light-weight bundled compatible Android enabled TVs. Double-check your television!
NOTE: This list is not fully complete and is only a guide.
Variant Arch O/S Screen DPI
(000) arm OS 4.0+ nodpi
(001) arm OS 4.0+ 160dpi
(002) arm OS 4.0+ 240dpi
(003) arm OS 4.0+ 320dpi
(004) arm OS 4.0+ 480dpi
(005) x86 OS 4.0+ nodpi
(006) arm OS 5.0+ nodpi
(007) arm OS 5.0+ 240dpi
(008) arm OS 5.0+ 320dpi
(009) arm OS 5.0+ 480dpi
(010) arm64/arm OS 5.0+ nodpi
(011) arm64/arm OS 5.0+ 320dpi
(012) arm64/arm OS 5.0+ 480dpi
(013) x86 OS 5.0+ nodpi
(014) x86/x86_64 OS 5.0+ nodpi
(017) arm OS 6.0+ nodpi
(018) arm OS 6.0+ 240dpi
(019) arm OS 6.0+ nodpi
(020) arm OS 6.0+ 240dpi
(021) arm OS 6.0+ 320dpi
(022) arm OS 6.0+ 480dpi
(023) arm64/arm OS 6.0+ nodpi
(024) arm64/arm OS 6.0+ 320dpi
(025) arm64/arm OS 6.0+ 480dpi
(026) x86 OS 6.0+ nodpi
(027) x86/x86_64 OS 6.0+ nodpi
(030) arm OS 4.0+ nodpi
(032) arm OS 4.0+ 160dpi
(034) arm OS 4.0+ 240dpi
(036) arm OS 4.0+ 320dpi
(038) arm OS 4.0+ 480dpi
(046) arm OS 8.0+ nodpi
(047) arm OS 8.0+ 240dpi
(048) arm OS 8.0+ nodpi
(049) arm OS 8.0+ 240dpi
(050) arm64/arm OS 8.0+ nodpi
(051) arm OS 8.0+ 480dpi
(052) arm64/arm OS 8.0+ nodpi
(053) arm64/arm OS 8.0+ 320dpi
(054) arm64/arm OS 8.0+ 480dpi
(055) x86 OS 8.0+ nodpi
(056) x86/x86_64 OS 8.0+ nodpi
(070) x86 OS 4.0+ nodpi
(230) arm OS 5.0+ nodpi
(234) arm OS 5.0+ 240dpi
(236) arm OS 5.0+ 320dpi
(238) arm OS 5.0+ 480dpi
(240) arm64/arm OS 5.0+ nodpi
(246) arm64/arm OS 5.0+ 320dpi
(248) arm64/arm OS 5.0+ 480dpi
(270) x86 OS 5.0+ nodpi
(280) x86/x86_64 OS 5.0+ nodpi
(430) arm OS 6.0+ nodpi
(434) arm OS 6.0+ 240dpi
(436) arm OS 6.0+ 320dpi
(438) arm OS 6.0+ 480dpi
(440) arm64/arm OS 6.0+ nodpi
(446) arm64/arm OS 6.0+ 320dpi
(448) arm64/arm OS 6.0+ 480dpi
(470) x86 OS 6.0+ nodpi
(480) x86/x86_64 OS 6.0+ nodpi
(736) arm OS 5.0+ 320dpi
(738) arm OS 5.0+ 480dpi
(746) arm64/arm OS 5.0+ 320dpi
(930) arm OS 8.0+ nodpi
(934) arm OS 8.0+ 240dpi
(936) arm OS 8.0+ 320dpi
(938) arm OS 8.0+ 480dpi
(940) arm64/arm OS 8.0+ nodpi
(946) arm64/arm OS 8.0+ 320dpi
(948) arm64/arm OS 8.0+ 480dpi
(970) x86 OS 8.0+ nodpi
(980) x86/x86_64 OS 8.0+ nodpi
» Google Market Play Store APK
Should you require any older versions of Google Play / Market either to resolve instability, require less memory, or for use on a low-end/budget device, you can easily downgrade without issues. There are multiple methods of installation here, and it depends on your device type. If one method does not work, then simply try the next available.
Download All Versions of Play / Market:
- Standard: https://www.apkmirror.com/apk/google-inc/google-play-store/
Code:
Amalgamating and collating resources...
- - - - - - - - - - - - - - - - - - - - -
» GOOGLE PLAY STORE & PLAY SERVICES - ERRORS, ISSUES, FIXES & TROUBLESHOOTING
STATUS: Work In Progress!
Be aware you do *not* need the latest version of every Google app to use your device. Updating often introduces issues and more resource intensive apps and services. May of 2018 and I am still using Google Play v6 without any issues on my TV Box.
More information will be updated soon...
Found this useful? Click the [:good: Thanks!] button below!
Cheers!
.
i have KI plus Amlogic S905D and 7.1.1 android version
can't find stock Rom download link (to use it in case of failure)
i tried to boot to recovery to install TWRP, but the device not accepting to boot to recovery
only showing Mecool Logo
flipmode_11 said:
.
.
Click to expand...
Click to collapse
For hiding magisk you need to edit the APK file, as for safety net I believe @whiteak has passed safety net
As for the playstore fix, simply replace vending.apk
As for the crashes(not only Firefox) I believe it's got something to do with Amlogic-res or some other frameworks and libs
The recovery varies on Android version, I know you cannot load a fresh kernel from a different version and my best bet is either due to the bootloader or dtb, I cannot successfully flash either without USB burning tool, so if you find a way let me know so when can implement this fix in future roms removing the need to flash the same stock firmware as the target android version prior to flashing a rom
black-hook said:
i have KI plus Amlogic S905D and 7.1.1 android version
can't find stock Rom download link (to use it in case of failure)
i tried to boot to recovery to install TWRP, but the device not accepting to boot to recovery
only showing Mecool Logo
Click to expand...
Click to collapse
Pm me, I'll fix it for you
Ricky Divjakovski said:
Pm me, I'll fix it for you
Click to expand...
Click to collapse
i sent pm to you yesterday
Blackhook, you are very lucky!
All us Aussie's are top blokes! Ricky especially!
Ricky Divjakovski said:
Pm me, I'll fix it for you
Click to expand...
Click to collapse
black-hook said:
i sent pm to you yesterday
Click to expand...
Click to collapse
Thank you Ricky for taking the time to respond in the topic. Much appreciated!
Okay, so I don't understand "Edit APK file"? Can you please be more specific?
I cannot get Play/Play Services to work in anymore (15.3 to 16). Currently Play says "Certified" under settings. I've no idea how to replace Play, as it uses a different APK file name.
'WhiteAK'? has passed SafetyNet? I don't know what you mean... Whiteak has the same device and managed to update Play/Play services and get it working??
Crashes are "Amlogic-res" and/or lib \ framwork related. Okay I get System, Settings, plus any app I'm in... So perhaps some file/library can be updated to resolve this instability?
Strange as it doesn't appear as "Vending.apk" within BK Disabler, Titanium and other apps.
It is listed as
* Play Store v6.0.5 'com.android.vending' /system/priv-app/Phoneysky/Phonysky.apk
* Play Services v8.4.89 'com.google.android.gms' /system/priv-app/PreBuiltGMSCore/PreBuiltGMSCore.apk
So backup Vending.apk; download new Vending.apk (any original version?); overwrite old with new Vending.apk from (Link ???); that should take care of Play Store AND Play Services?
How do you prevent updates for Play + Play Services, like it is currently?
Will this solve the download/install issue?
Oh, so if reflashing, Slot 1 = current ROM version/variant (from backup I assume) and Slot 2 = new ROM to install?
I don't know what a "USB burning tool" is. Link to dev/site?
Thanks for sharing your knowledge.
Cheers mate!
Ricky Divjakovski said:
For hiding magisk you need to edit the APK file, as for safety net I believe @whiteak has passed safety net
As for the playstore fix, simply replace vending.apk
As for the crashes(not only Firefox) I believe it's got something to do with Amlogic-res or some other frameworks and libs
The recovery varies on Android version, I know you cannot load a fresh kernel from a different version and my best bet is either due to the BOOTLOADER or DTB, I cannot successfully flash either without USB BURNING TOOL, so if you find a way let me know so when can implement this fix in future ROMs removing the need to flash the SAME stock firmware as the target android version prior to flashing a ROM
Click to expand...
Click to collapse
Updated first two posts above.
If you notice any mistakes or typos, let me know.
Please share your knowledforfor anything Media Centre / TV BOX related!!
Cheers!
will this only work for the t95z plus, i have a m9x 3 that has the amlogic 3912 with 3/32gb, the stock rom on it is really buggy would like something that works well. I have this installed on my t95z plus and works well.
ItsSunnyB said:
will this only work for the t95z plus, i have a m9x 3 that has the amlogic 3912 with 3/32gb, the stock rom on it is really buggy would like something that works well. I have this installed on my t95z plus and works well.
Click to expand...
Click to collapse
This will work as you have the same S912 standard chip and hardware.
Devices like the $$$ Nvidia Shield are very different units with very different hardware.
Booting to the recovery image and backing up WILL NOT make any modifications, unless you wipe, install or repair, etc...
Perform a (NANDroid) Backup of your device with above steps before attempting [*anything*].
good info
Thanks a lot for the useful info you posted here. I have kiii pro with amlogic 912, but the stock kernel doesn't include all device modules from source. I have some joysticks and they never work since no drivers are loaded for them. I would be grateful if you could help me with kernel source and a way to compile it with modules i need
G'day Luffy,
I think the issues you've highlighted with the missing framework and modules is something you should post separately as this topic is for rooting, backing up, flashing, etc.
Create a new topic with subject: Kiii K3 Pro S912, Missing Modules / Drivers in Stock Kernel
Something like that in the subject, to describe the issue. Is it a Mecool? I nearly bought the Kiii/K3 but keep seeing people have issues on the forums!
I suggest you follow the Backup instructions above before you do anything else.....
P.s. Replace "xxGB" with model's RAM you have below.
Goods luck mate!
luffy_senpai said:
Thanks a lot for the useful info you posted here.
Click to expand...
Click to collapse
Hello, I have a Kiii Pro TV box w/ xxGB RAM, Amlogic S912 & DVB T2/S2.
I am experiencing issues with the stock kernel as it does not include all standard peripheral device modules. For example: I have some joysticks and they are neither recognised nor work, since no drivers are available to be loaded.
I would be grateful if you could help me with Kernel source and a way to compile it with all standard driver modules or those module drivers I need
Thank you.
Click to expand...
Click to collapse
flipmode_11 said:
Thanks for sharing your knowledge.
Cheers mate!
Click to expand...
Click to collapse
Download the latest 7.1.2 gapps, get the vending file from within it.
On your device, playstore is either stored as vending, phonesky or velvet, so whatever one it's stored as delete the folder, make a new folder called vending and add the vending.apk inside it, set permissions to rw-r-r(644) , that's your playstore issues fixed(all of them)
You don't need to prevent updates, updates are distributed for a reason
Gms core is the core of all Google's services and does not need to be touched
Yes Whiteak has a t95z plus and managed to pass safety net, im unknown how though
For recoveries, I made a great tool to port recoveries to any device, removing the need to find a specific recovery for the variant, check this forum for my Amlogic flash tool and recovery porter
The random crashes I still haven't figured what fixes them but in my PoisonRom, none of those issues appear
And with next release, it compiles the kernel on the device so it will be compatible with every single Amlogic device.
Champion mate! Really appreciate it.
Yes, PhoneSky. But Play Services is updated, and I updated Play from 6.0x to 6.0.5.
I downgraded from 12 to 11 on GMS (Play Services) and stopped getting the new crashes within apps. However it just auto-updates itself again and starts crashing again...
So flash Poison on to this X96 1GB (800MB) device? Already deciding on my next Media Box! (Shortlist: H96 Pro, X99 Max RKM MK39, R-TV K99 / CSA96, R99, CloudNetgo CD19, and......?). Any recommendations
They're all 4GB DDR3 RK3399 T860 models. I assumed the RAM capacity was more important than DDR4 speed....
Cheers!
p.s. downloaded your tool some time ago but now I understand what it does, given your explanation - Port a 3rd Party Recovery to be Generic Recovery supporting any AML S905/S912 media centre? Does that include RK33xx RockChip too?
@ricky Your name has a space so cannot write @ and mention you
Did you see I included your tool above? This was all I could interpret from descriptions and forum messages:
AMLogic Network Flash Tool [Bundled ADB & FastBoot (Tool & Drivers) - Ability to flash AMLogic Media Player TV Boxes remotely over the network (LAN Cable or Wireless/Wi-Fi). Always backup prior to upgrading/downgrading! Read more...
Click to expand...
Click to collapse
Will need to fix it up.
Thanks again for your information. I will add it to the top articles.
EDIT: p.s. Play Services has crashed 3 times on my phone today. So it is definitely the most latest version that is causing it to crash *more* than usual.
Ricky Divjakovski said:
Download the latest 7.1.2 gapps, get the vending file from within it.
On your device, Play Store is either stored as "vending", "phonesky" or "velvet", so whatever one it's stored as delete the folder, make a new folder called vending and add the vending.apk inside it, set permissions to rw-r-r(644) , that's your playstore issues fixed(all of them)
For recoveries, I made a great tool to port recoveries to any device, removing the need to find a specific recovery for the variant, check this forum for my Amlogic flash tool and recovery porter
The random crashes I still haven't figured what fixes them but in my PoisonRom, none of those issues appear
And with next release, it compiles the kernel on the device so it will be compatible with every single Amlogic device.
Click to expand...
Click to collapse
This worked for me on Bqeel k12 (amlogic s912) octacore running stock 7.1.2 ? thank you very much to OP ? booted into twrp first time from fat32 formatted sd card so I restarted, downloaded supersu zip, back to recovery, flash su.zip (via nice shiny new twrp?) root check and all is 100%
I see the twrp is 3.1? Will the theme zip work on it that was for 3.1 twrp ?
Updated Support Downloads and Links.
+ Included AMLogic "USB Burning" Firmware Update/Imaging Tool v2.1.6 2018.03 Update..
+ Included Magisk Flashable Multi-Root Uninstaller ZIP latest update.
@Kurtlestat Thanks for the feedback.
I've not tried any theme.zip's so cannot comment. But trying standard Philz or TWRP do not work. This is a specially modified version to be compatible with all AML devices.
I'm actually looking for a RockChip compatible TWRP image but so far have not been successful!
If I were you, check out Magisk instead. It is systemless too. I switched as seems to be more actively maintained and organised.
I tried the theme zip but it's only for twrp 3.1.0 This version is 3.1.1 so it was no dice, but still gave it a try ?
Now the sad news ? I tried flashing the poison rom and it failed with error 7. I went to restore my backup and musta wiped it lol can't even say I've got an expensive paperweight cos the things so light ?
Anyways does anyone know of stock firmware or custom rom for bqeel k12 amlogic s912 octacore 2/16gb it came with nougat 7.1.2 stock. Going to try download poison rom in mean while as I think error 7 is corrupt file. But..... to OP ...... the twrp still works ?
New article added to 2nd post.
FIND & LOCATE YOUR STOCK BOOT IMAGE BACKUP CREATED BY MAGISK
Whether you initially used the Magisk Manager app -or- TWRP Recovery \ ADB FastBoot \ Odin3 to flash the Magisk patched boot image, a backup copy of the existing stock boot image is stored in "./data/" as "stock_boot.img".
However, if you flash an already Magisk patched "boot.img" through ADB FastBoot (Download Mode), then neither a "stock_boot.img" backup will be created or existing backup overwritten. Magisk detects the active boot image as already patched, therefore you must manually create a backup if you wish to retain the existing boot image.
Note: When patching a stock boot.img and flashing via Magisk Manager, the backup of the stock boot image is temporarily held in a directory until the next reboot: "./data/user/0/com.topjohnwu.magisk/install/stock_boot.img".
If you are struggling to locate the file, access an on-device terminal emulator, type "SU" and enter: "find -name 'stock_boot*'".
*Magisk Topic* » https://forum.xda-developers.com/showthread.php?t=3473445 (Features, Functionality, Q&A, Discussions)
*Troubleshooting* » https://www.didgeridoohan.com/magisk/HomePage (FAQ & Detailed Solutions & Examples)
Masking and Cloaking Root Access & SuperUser
Open Magisk Manager, open Settings. Scroll down to the yellow heading "MAGISK" and enable "Magisk Hide" (Note: do NOT enable "Hide Magisk"!!!)
Close Magisk Manager. Open Magisk Manager. Slide open the left menu by swiping left-to-right.
Click the 3rd item down - "Magisk Hide".
Scroll down and tick the box on "Spotify" or any other item you want to "Cloak" or "Mask" Root to prevent detection.
BusyBox App or BusyBox Applets installed on your device?
Download, install and open your Busybox app. We will only use the "Uninstall" component of this app to cleanup any Busybox applets and remnants left behind..
If you have any corruptions in BusyBox preventing removal, first click "Install" to update, and then click "Uninstall".
Once complete, you may uninstall the Busybox app. It will not be required from now on.
Masking BusyBox Modules and Applets
Open Magisk Manager. Slide open the left menu by swiping left-to-right.
Click the "Downloads" menu item.
Scroll down the list and looks for something like "Busybox NDK" or similar.
Read the module description. Click Install and follow the steps.
Slide open the "Modules" menu item to see the list of (active/inactive) installed modules (You may tick/untick a module to disable it temporarily, or click the trash icon to remove and uninstall it completely).
You should now see the BusyBox NDK systemless edition installed.
Found this useful? Please click "Thanks". :good:
Cheers!
Mate I would literally post that in the Poison ROM topic as they will know the best thing to do.
Didn't you save the TWRP backup on your SD Card or PC? Always save to a PC! Read all my posts! I'm obsessed with backups! Hah
Bqeel K12... Find their web site and use the contact form if you cannot find the support downloads. I had a quick google and struggled. However many sellers now have "Support" tabs, with links to firmware.
Don't stress mate, you'll be right. They're fairly indestructable as all unlocked and fairly flexible boxes.
p.s. From your experience, would you get an S912 or RK3399 or RK3368? and 4GB DDR3 or 3GB DDR4?
Trying to get a more reliable box, that can handle the power. I have seen no bootable SD recovery.img for RockChip. Bit of a concern I can't get to TWRP on this $50 RK3328. Next box: RKM MK39 or CloudNetGo CR19 (RockChip) - and - Any 3GB DDR4 or Any 4GB DDR3 (S912) - and- Meecool KIII DVB-T2 or ....
Kurtlestat said:
I tried the theme zip but it's only for twrp 3.1.0 This version is 3.1.1 so it was no dice, but still gave it a try
Now the sad news I tried flashing the poison rom and it failed with error 7. I went to restore my backup and musta wiped it lol can't even say I've got an expensive paperweight cos the things so light
Anyways does anyone know of stock firmware or custom rom for bqeel k12 amlogic s912 octacore 2/16gb it came with nougat 7.1.2 stock. Going to try download poison rom in mean while as I think error 7 is corrupt file. But..... to OP ...... the twrp still works
Click to expand...
Click to collapse
Hi, there!
Now that we can use Project Croissant to get ChromeOS running or non-Chromebook devices, what is missing is a better kernel for improved compatibility.
Thanks to the threads by @nabil2000 I was able to successfully build a chromeos-4.14 kernel that boots on my test device (Lenovo MIIX320-10ICR - Z8350 processor) using a CONFIG from FydeOS 5.31 with most hardware enabled (WiFi, Bluetooth, sound), but it has the same issue as latest ATB builds: it freezes after a while. This doesn't happen with latest FydeOS or CloudReady builds (CloudReady bought FlintOS so I guess they are using some of their code now), so my guess if that their kernels have some patches that aren't included in the Chromium git. FydeOS is open-sourced only for RaspberryPi and TinkerBoard, there are no sources available for the PC or VMWare versions (PC version is not open source as many say, so be aware).
I already have some ideas to make the trackpad as well as the battery meter and brightness work, but it is not useful if the kernel isn't as stable as FydeOS (virtually no freezes or crashes once booted). I have already checked, and the issue is not the intel_idle.max_cstate issue that plagued most BayTrail/CherryTrail devices in the past (using value 1 doesn't change anything).
So any ideas how to get FydeOS kernel source? Patches to make the current chromeos-4.14 kernel stable?
UPDATE: As @nabil2000 reported, it seems that FydeOS is not willing to release their kernel source. But it is possible to get kernel config from v5.31 using configs.ko module, which is missing in the next version (v6.0). Using FydeOS v5.31 as base it is possible to build a very stable kernel for CherryTrail devices.
Thanks
Installation v71/v72 - kernel 4.14
FydeOS has the best support for the MIIX320-10ICR, with some caveats:
It will boot to a black screen, but you just need to wait until it finishes loading the hit Ctrl+Alt+Fn+F2, the screen will blink and then hit Ctrl+Alt+Fn+F1 to go back to ChromeOS (for some reason, the developer shell is blank in 5.31 but it seems to work fine on 6.0). Use Ctrl+Shift+Fn+F3 to rotate the screen manually;
WiFi works out of the box, Bluetooth is detected but audio does not work (Chromium misses a library for audio over Bluetooth);
Sound works too, but you need to install some UCM files (more about this later);
Camera does not work, and the trackpad works very well, with gestures, but does NOT click (tap to click work with a custom conf file, see below - the trackpad actually sends two events when clicking the physical button, as some Windows devices do, and this doesn't work with cmt driver).
First I tried to build the ChromeOS file using the chromium.img from FydeOS v5.31. It booted fine and I was amazed to see the ChromeOS logo and Google enrollment, but PlayStore setup didn't finish (low space?) and there was no way to install it to another driver: many GPT errors and the installer failed...
Then I tried to do everything on place:
Booted to FydeOS on USB drive;
As I could not get to the dev shell in v5.31, I had to login then use crosh and shell, then installed it on a second external disk (120GB SATA on USB, /dev/sdb):
PS: your device may be a different one, check the correct device name using "lsblk" or "fdisk -l" and be aware that this installation erases the whole disk!
Code:
sudo chromeos-install --dst /dev/sdb
After installing, I have used option 2A from GitHub page (very detailed, thanks!) with the script, soraka (or pyro) and caroline recoveries (both versions 11151.113 = v71) on another disk:
PS: FydOS v5.31 kernel does not have support to VTPM_PROXY, while v6.0 does, it means you cannot use swtpm.jar with FydeOS v5.31 and chromefy. For nocturne or Android Pie ARC, you must use FydeOS v6.0, otherwise ARC won't work.
Code:
sudo bash ./chromefy.sh /dev/sdb recovery.bin caroline.bin
Answered YES to use the local installation, YES to resize partitions and NO in the end to keep SELinux as enforced (it may work fine if you keep it to enforced with nocturne recovery tho when using FydeOS v6.0);
Rebooted using the final installation, logged in and everything seemed fine, but then Play Store would not show installed apps even after a reboot, so I tried a powerwash and it seems it fixed the issue, now it seems to be working fine.
Original post: https://forum.xda-developers.com/showpost.php?p=78891386&postcount=729
Post installation fixes v71/v72 - kernel 4.14
1. Sound
You need to install UCM files using linuxium-install-UCM-files.sh script after remounting rootfs as RW.
Code:
sudo remount -o rw,remount /
sudo bash ./linuxium-install-UCM-files.sh
2. Headphone jack
You must send this quirk to the rt5645 module when loading it, so while rootfs is still RW, as root add a file named "miix320.conf" to /etc/modprobe.d with this line:
Code:
options snd_soc_rt5645 quirk=0x1030
PS: if you have used the correct UCM files then the audio should change between speakers and headphones, but not mic. To enable internal mic:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev DMic
and to enable mic from headset:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev HSMic
3. Tap to click with trackpad
While rootfs is still RW, as root add a file named "50-mixx320.conf" to /etc/gestures:
Code:
Section "InputClass"
Identifier "MIIX320 conf"
MatchUSBID "048d:*"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "Tap Minimum Pressure" "1"
EndSection
PS: for this to work, make sure "tap-to-click" is enabled in trackpad section of system Settings. If you have another device, use "dmesg | grep input:" with "lsusb" to find your device USB id instead of "048d:*".
Still needing fixes:
- chrome://flags is blank for some reason, so any special flags should be added manually to "chrome_dev.conf" instead;
- Trackpad physical button click;
- Brightness control;
- Battery meter;
- Rotation;
- Automatic change between tablet/desktop modes;
- Cameras (hardly they will work as they rely on ATOMISP, which was abandoned and does not work even on newest kernels).
Original post: https://forum.xda-developers.com/showpost.php?p=78978577&postcount=757
reserved
Good news! With chromeos-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
lfom said:
Good news! With chrome-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
Click to expand...
Click to collapse
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
nabil2000 said:
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
Click to expand...
Click to collapse
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-dev in order to successfully build it.
lfom said:
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-devel in order to successfully build it.
Click to expand...
Click to collapse
I am a lazy billy - thanks - I like copy & paste, & think as little as I can afford
Could you help me patching it on my GPD pocket?
it uses cherry tail
https://forum.xda-developers.com/ha...gpd-pocket-t3928828/post79496417#post79496417
thank you