In this post, I will try to explain the devices I purchased, the mods I needed to do, and how they can be useful.
I wanted a touch panel on my wall to control my home automation system (Home Assistant). While most people just wall mount an old tablet, I did not like that idea due to a tablet being a battery powered device and not designed to be plugged into a wall charger 24/7.
So I started looking for alternatives, from China of course. In mid-2020 I purchased a couple of 'Android In-wall Amplifiers' from AliExpress. These devices mains voltage powered (110V-250V AC). They are designed to be mounted 'in-wall' and control multiple audio zones throughout rooms in your house. They also happen to have RS485 (which I am yet to explore).
I ordered 2 variants to test. Here are the specs:
'Rockchip 86F' - AliExpress Link
4-inch IPS Display, 480*480 Resolution
Android 7.1 System, 4 Core Processor, Cortex 1.2G CPU
RAM: 1GB
Storage: 8GB
Network: Support Wi-Fi
Bluetooth: Support
Power Supply Mode: AC 110-250VC
Output Power: 2*20W or 4*15W (simulation power amplifier)
Output Impedance: 4-8Ω
Audio Inputs; Output
'Rockchip A7' - AliExpress Link
7-inch IPS Display, 1024*600 Resolution
Android 8.1 System, 4 Core Processor, Cortex 1.5G CPU
RAM: 2GB
Storage: 16GB
USB 2.0 port, can read 32GB
Network: Support Wi-Fi 2.4GHz/5GHz
Bluetooth: Support BT 5.0
Power Supply Mode: AC 110-250VC
Output Power 8*20W (Yamaha digital amplifier)
Output Impedance: 4-8Ω
The Goal
My goal was to install Home Assistant companion app on these devices, and mount them in my walls to help control/monitor my smart home. The 'proper' way to go about this would be to install the Home Assistant companion app from the Play Store. While the 7-inch version was marketed as having the Play Store, the 4-inch was not.
The Problems
As it turned out, the Play Store app on the 7-inch version did not function. It simply crashed on launch, over and over again. The 4-inch version simply does not come with the Play Store at all. So I decided to sideload the Home Assistant companion app and try things that way. At the heart of it, the Home Assistant companion app simply shows a WebView. I was met with 2 main problems.
Non-functioning (or missing) Play Store
Missing SSL CA-Bundle certs (meaning I was getting SSL errors)
An outdated Android WebView (meaning I was getting rendering errors and glitches)
Please see the following posts (coming soon) for my journey into these devices, and how I solved the problems.
Let's start with the 7-inch version.
First, I tried to tackle the broken Play Store. Generally speaking, people will suggest downloading OpenGApps and using TWRP to flash them. Unfortunately because this device is some random no-name device from China, it would be nearly impossible to find a working TWRP recovery for it. So flashing OpenGApps via a custom recovery is out of the question. Thankfully, there are other ways.
Installing the Play Store
First we need to enable 'USB Debugging' which can be found in 'Developer options' part of the Settings app within Android.
Open 'Settings' app, scroll down and select 'System' and then 'About tablet'
Once there, look for 'Build Number' and quickly tape on it 10 times or so until you see 'You are now a developer'
Back out of that menu and you should now see a new 'Developer options' section.
Inside 'Developer options' there is a setting labelled 'USB debugging'. Enable it.
Connect your tablet to your PC using a micro-USB cable.
Now we need to use ADB to install a few APKs to the device. If you don't have ADB installed on your computer, now is a good time to do it. Search this forum for information on how to do so.
The following APKs are needed, and should be installed in this order:
com.google.android.gsf.login
com.google.android.gsf
com.google.android.gms
com.android.vending
Obtain those APKs from your favourite APK repository and install them using '
Code:
adb install <filename>
'. Once all 4 are installed, the Play Store should be working. If not, reboot for good measure. I will attach a list of the specific versions of the APKs I installed.
Now you can install the Home Assistant companion app (or another browser of your choice, such as Fully Kiosk) and away you go, right? Well, sort of.
Since this tablet comes with an old/outdated version of Android WebView you are likely to get rendering/display issues in both the HA app, and Fully Kiosk app. Both of these use the configured 'Android WebView' option found in 'Developer options'. Unfortunately, in this ROM, that value has been hardcoded to use 'com.android.webview' package, which is a system app and not updatable from the Play Store. The Play Store 'Android WebView' is actually 'com.google.android.webview' and is not in the list of allowed 'Android WebView' options for this device. So I had two options. Firstly, ask the device manufacturer to make an updated ROM that allows other WebView implementations, or, try and modify if myself.
Updating (Installing alternative) Android WebView
The first method I tried was to install a newer 'com.android.webview' into /system/ which ended in failure... The tablet didn't appreciate this, and got stuck on next boot. Do not try this.
The second method I tried was to modify /system/framework/framework-res.apk to include alternative WebView implementations. This also failed. Do not try this.
The third method I tried was installing Xposed Framework, so that I can modify the WebView options that way. This method usually requires a custom recovery such as TWRP, which we do not have. Here is what we have to do instead:
Download the xposed-v90-sdk27-arm.tar from here
Download the XposedInstaller_3.1.5.apk attached to this post.
Use adb on your PC to copy it to the device
Code:
adb push xposed-v90-sdk27-arm.tar /sdcard/Download/
Use adb on your PC to install the XposedInstaller apk
Code:
adb install XposedInstaller_3.1.5.apk
Open an adb shell
Code:
adb shell
and switch to root by typing
Code:
su
Remount the /system filesystem (may not be needed as the install script may do this)
Code:
mount -o rw,remount /system
Extract the xposed-v90-sdk27-arm.tar file
Code:
tar -xvf xposed-v90-sdk27-arm.tar
Change into the directory that was just created
Code:
cd xposed-v90-sdk27-arm
Make the installer script executable
Code:
chmod a+x flash-script.sh
and run it
Code:
./flash-script.sh
Xposed Framework is now installed, but not activated. Reboot your device. Please note, it will take longer to boot than usual on the first boot.
Once your device has rebooted, open the Xposed Installed app and make sure it is activated. If it's orange and says its not activated, another reboot should sort it.
Once you have confirmed it is activated, we need to install a module called 'Any WebView'. Click on the Hamburger Menu, tap 'Download' and use the search to look for an install 'Any WebView'. Reboot your device.
Now, we need to install an updated Android WebView. You can install any compatible webview such as 'Google Chrome' or 'Android WebView' from the Play Store.
Go back into Settings->Developer options, select 'WebView Implementation' and choose your newly installed WebView. Do not use 'Android System WebView 61.0.x' as it is outdated.
Congratulations! You can now install the HA app, Fully Kiosk app, or anything else you need from the Play Store.
Here are some images of my 7 inch device displayed the Home Assistant Lovelace UI in Fully Kiosk Browser.
On to the 4-inch version
This unit had similar problems (no Play Store and outdated WebView implementation) but it was a bit more of a mess to deal with.
Installing the Play Store
Unlike the 7-inch version, you cannot simply install the APKs and expect it to work. Google Play Services will repeatedly crash and logical shows this is due to a missing MANAGE_USERS permission.
Like the 7-inch version, there is no custom recovery available for this unit, so flashing something like OpenGApps in the normal fashion is not possible either. Unpacking the OpenGApps zip and attempting to run the installer script within is also a dead-end as it requires the 'ash' shell that is not available on the device. But never fear, I got things to work.. here is how:
First we need to enable 'USB Debugging' which can be found in 'Developer options' part of the Settings app within Android.
Open 'Settings' app, by swiping down from the top of the screen and long-pressing the Wi-Fi icon.
This will load the settings app on the Wi-Fi page
Press the 'hamburger menu' and scroll down and select 'About device'
Once there, look for 'Build Number' and quickly tape on it 10 times or so until you see 'You are now a developer'
Click on the 'hamburger menu' again and you should now see a new 'Developer options' section.
Inside 'Developer options' there is a setting labelled 'USB debugging'. Enable it.
Connect your tablet to your PC using a micro-USB cable.
This is where things get a bit different. I had to unpack the OpenGApps zip file, unpack the lzip archives inside that, and figure out where all the files are meant to go so we can manually graft them into the /system/ folder on the device. You can download the ready-to-go folder here.
If you're the kind of person who wants to do it themselves, I have attached a directory tree structure to this post that shows where the files need to be.
As with the 7" version, we are going to use ADB to get these files onto the unit.
Copy the files onto the device
Code:
adb push opengapps-4inch.tar /sdcard/Download/
Open an adb shell
Code:
adb shell
and switch to root by typing
Code:
su
Remount the /system filesystem
Code:
mount -o rw,remount /system
Unpack the opengapps-4inch.tar file
Code:
cd /
tar -xvf /sdcard/Download/opengapps-4inch.tar
That should be it. Reboot and check that the Play Store is now available on your device.
Updating (Installing alternative) Android WebView
Just like the 7-inch version above, we do basically the same thing, but we have to use a different version of the Xposed Framework suitable for Android 7.1.2
Download the xposed-v89-sdk25-arm.tar from here
Download the XposedInstaller_3.1.5.apk attached to the first post. We can use the same version of this app.
Use adb on your PC to copy it to the device
Code:
adb push xposed-v89-sdk25-arm.tar /sdcard/Download/
Use adb on your PC to install the XposedInstaller apk
Code:
adb install XposedInstaller_3.1.5.apk
Open an adb shell
Code:
adb shell
and switch to root by typing
Code:
su
Remount the /system filesystem (needed if you rebooted after installing Play Store)
Code:
mount -o rw,remount /system
Extract the xposed-v89-sdk25-arm.tar file
Code:
tar -xvf xposed-v89-sdk25-arm.tar
Change into the directory that was just created
Code:
cd xposed-v89-sdk25-arm
Make the installer script executable
Code:
chmod a+x flash-script.sh
and run it
Code:
./flash-script.sh
Xposed Framework is now installed, but not activated. Reboot your device. Please note, it will take longer to boot than usual on the first boot.
Once your device has rebooted, open the Xposed Installed app and make sure it is activated. If it's orange and says its not activated, another reboot should sort it.
Once you have confirmed it is activated, we need to install a module called 'Any WebView'. Click on the Hamburger Menu, tap 'Download' and use the search to look for an install 'Any WebView'. Reboot your device.
Now, we need to install an updated Android WebView. You can install any compatible webview such as 'Google Chrome' or 'Android WebView' from the Play Store.
Go back into Settings->Developer options, select 'WebView Implementation' and choose your newly installed WebView. Do not use 'Android System WebView 61.0.x' as it is outdated.
Congratulations! You can now install the HA app, Fully Kiosk app, or anything else you need from the Play Store.
Nice DIY project!
Google Assistant (including "Hey Google" activation) on the 4-inch device
So I managed to get Google Assistant installed and working on the 4-inch version (The 7-inch does not have a microphone built in).
You need both the "Google" app and the "Google Assistant" app, and both are available in the Play Store, but "Hey Google" voice activation will not work unless the "Google" app is installed as a system app.
Getting "Google" app installed as a system app
1) Download and install "Google" from the Play Store as you would any other app.
2) Use adb to connect to the device
Code:
adb shell
3) Switch to root user
Code:
su
4) Remount the system partition as read/write
Code:
mount -o rw,remount /system
5) Navigate to the user apps directory
Code:
cd /data/app/
6) Copy the "Google" app into system apps folder
Code:
cp -R com.google.android.googlequicksearchbox-1 /system/priv-app/
7) At this point, you should be able to delete the 'user app' copy and reboot.
Code:
rm -rf /data/app/com.google.android.googlequicksearchbox-1
reboot
8) Once the device has restarted, go to the Play Store and install "Google Assistant".
You should now be able to configure your Google Assistant to respond to "Hey Google" and "Ok Google" voice activations.
Related
I am attempting to port Cyanogenmod to the Garminfone. I have root, know how to have it load a recovery.img at boot, and know how to flash partitions on it (it comes with a flash_image program that can flash an image to a given partition, which is how it flashes the recovery.img
I am very familiar with the layout of the partitions, os, and with not too much effort could get the current OS running in the emulator,as they left all of the emulator initial scripts on the device and did a great job commenting everything.
The one thing I am not sure about is flashing the bootloader in a way that will not trash the device. I know it is a msm7227 cpu and can provide dumps of anything anyone may need to help.
Any assistance would be appreciated. Thanks!
Hi Merwin, Have you had any success porting CM to garminfone/nuvifone A50?
No luck yet... still trying to figure out how to do it without bricking it. Not getting much in the way of assistance on how to port the recovery image to my phone properly, so I can recover while testing.
I know how to unpack it and a couple ways of getting it flashed back that are yet untested but should work.
Its pretty standard hardware (msm7227), and aside from the Atheros wifi and potentially the gps in it (crazy accurate, down to 6.6 feet and works without a sim, so I think there must be something different) the sensor drivers all report being standard android drivers.
I make my living doing software development, database development, and lots of middleware to get different systems to play nicely,but have nearly no hardware or driver development experience and very little work with asm, so decompiling and inspection is out, but can figure out most anything when pointed in the right direction. I just need someone experienced to work with me on it.
Anyone interested?
Sent from my Garminfone using XDA App
Wouldn't it just be easier to figure out how to compile a rooted recovery and to set up mayb keymaps to be able to boot from.. With a recovery thats able to flash if we were to have to flash the bootloader change spl/radio or anything we would be able to go about making a update.zip for the recovery and flash it that way???
I can already rebuild the existing recovery img as well as the bootloader. The existing recovery can flash an update.zip if the keymapping to select menu entries was there.
There is no hardware method to boot into recovery aside from the failsafe, which triggers if the main boot image fails to load a certain number of times.
So, you are safe unless you **** up both the main bootloader and the recovery... which is why I flash any test boot image to the recovery partition first, test it, then flash back my rooted recovery, test it, and flash the main boot image.
It takes longer, but works. What would be nice would be to compile the boot image using the first stage loader as well as the second stage loader. That would let you have your minimal loader that responds to the recovery keychord and then boots to the second stage loader that has all the features. Not sure how to accomplish it.
I did check the kernel config and every nonstandard component is loaded as a module and the kernel is 2.6.29 so there is no reason why we shouldn't be able to configure and compile a working Froyo at the very least.
I just need to work my way through the build process. The fun part will be seeing if the Garmin software would run on Cyanogen or if it checks more than just the model and serial.
I'm watching your progress with anticipation. I have no programming or development experience, but if I can help with testing or anything let me know.
Sent from my Garmin-Asus A50 using XDA App
Also watching this thread! Would love to be able to flash a kernel that allows overclocking and hopefully 2.2
Was this ever completed?
Re: Cyanogen for Garminfone
There is a solution. I just made it last weekend. This post will follow with video demos.
---
Start with a factory wipe.. not using garmins KB method: (We want a clean FS mounted)
Unmount and remove SD Card from phone.
Connect a usb cable and enable USB mass storage mode.
Create a desktop folder and move all contents of Garminfone drive to new folder.
Download 7-zip and restore.zip from garmin-asus support site.
Open restore.zip, browse restore and drag drop .system to root of Garminfone storage.
While USB mass storage mode is enabled hit menu > settings > privacy > master reset. Yes, yes.
Wait for the phone to reboot twice.
Pop cover, install SD card.
Menu > Settings > Storage
SD Card detected use as default? No.
Scroll down, unmount, format.
Scroll up, Default storage > SD Card
Home
Slide > USB > File Transfer
Launch Garmin Web Updater .. install select guide icons, voices, etc.
Optionally update garmin lifetime maps now here.
Install z4root and root phone
Open Superuser and check for updates, reboot if updates apply.
Install GO Launcher and replace ‘Breeze’ launcher
You should reboot now. (Apps > Terminal Emulator > #su > #reboot )
Install a startup manager (I used Android Assistant)
Cut the following apps from User/System startup: Flashlight,CardioTrainer,My Tracks, Pandora, Garmin Voice Studio, IM, Messaging, My Account, Offers Provider..
Install Dolphin Browser Mini
Install Google Voice (Port your number!!)
Install SSHDroid
Reboot phone when all is complete (Apps> Terminal Emulator > #su > #reboot )
From here forward it is much easier from a desktop ssh terminal such as putty, but this is entirely up to you. It may also be done in the Terminal Emulator app on the phone without using SSHDroid.
If you use Visual Voicemail still.. (its a mem hog!) omit the line with vvm-signed.apk
Either use T.E. and start with #su (root) and do the following commands or ssh as root/admin:
We’re going to remount the system partition so we can move some stuff around and trim the fat.
mount -o remount,rw,noatime,nodiratime,data=ordered -t ext3 /dev/block/mmcnand
blk0p3 /system
We’re going to hide some of the standard bundled apps since the phones permissions are all over the place we’re going to rename the files instead of doing a chmod -x:
cd /system/carrier/persist-app/
mv amazonmp3.apk amazonmp3.apk.no
mv HotSpotApp.apk HotSpotApp.apk.no
mv Myspace.apk Myspace.apk.no
mv Twitter.apk Twitter.apk.no
mv vvm-signed.apk vvm-signed.apk.no
Let’s make the phone boot the way Garmin-Asus intended:
mv /system/carrier/images/startup/bootanimation.zip /system/carrier/images/startup/bootanimation.zip.no
reboot !
The phone should now have around 70Mb RAM free!! Around 32Mb with Google maps/navigation running. This *will not* break your lifetime maps!
I highly reccomend making a point in time snapshot of some sort (Titanium Backup)
---------- Post added at 12:50 PM ---------- Previous post was at 12:37 PM ----------
There is a solution. I just made it last weekend. This post will follow with video demos.
---
Start with a factory wipe.. not using garmins KB method: (We want a clean FS mounted)
Unmount and remove SD Card from phone.
Connect a usb cable and enable USB mass storage mode.
Create a desktop folder and move all contents of Garminfone drive to new folder.
Download 7-zip and restore.zip from garmin-asus support site.
Open restore.zip, browse restore and drag drop .system to root of Garminfone storage.
While USB mass storage mode is enabled hit menu > settings > privacy > master reset. Yes, yes.
Wait for the phone to reboot twice.
Pop cover, install SD card.
Menu > Settings > Storage
SD Card detected use as default? No.
Scroll down, unmount, format.
Scroll up, Default storage > SD Card
Home
Slide > USB > File Transfer
Launch Garmin Web Updater .. install select guide icons, voices, etc.
Optionally update garmin lifetime maps now here.
Install z4root and root phone
Open Superuser and check for updates, reboot if updates apply.
Install GO Launcher and replace ‘Breeze’ launcher
You should reboot now. (Apps > Terminal Emulator > #su > #reboot )
Install a startup manager (I used Android Assistant)
Cut the following apps from User/System startup: Flashlight,CardioTrainer,My Tracks, Pandora, Garmin Voice Studio, IM, Messaging, My Account, Offers Provider..
Install Dolphin Browser Mini
Install Google Voice (Port your number!!)
Install SSHDroid
Reboot phone when all is complete (Apps> Terminal Emulator > #su > #reboot )
From here forward it is much easier from a desktop ssh terminal such as putty, but this is entirely up to you. It may also be done in the Terminal Emulator app on the phone without using SSHDroid.
If you use Visual Voicemail still.. (its a mem hog!) omit the line with vvm-signed.apk
Either use T.E. and start with #su (root) and do the following commands or ssh as root/admin:
We’re going to remount the system partition so we can move some stuff around and trim the fat.
mount -o remount,rw,noatime,nodiratime,data=ordered -t ext3 /dev/block/mmcnand
blk0p3 /system
We’re going to hide some of the standard bundled apps since the phones permissions are all over the place we’re going to rename the files instead of doing a chmod -x:
cd /system/carrier/persist-app/
mv amazonmp3.apk amazonmp3.apk.no
mv HotSpotApp.apk HotSpotApp.apk.no
mv Myspace.apk Myspace.apk.no
mv Twitter.apk Twitter.apk.no
mv vvm-signed.apk vvm-signed.apk.no
Let’s make the phone boot the way Garmin-Asus intended:
mv /system/carrier/images/startup/bootanimation.zip /system/carrier/images/startup/bootanimation.zip.no
reboot !
The phone should now have around 70Mb RAM free!! Around 32Mb with Google maps/navigation running. This *will not* break your lifetime maps!
I highly reccomend making a point in time snapshot of some sort (Titanium Backup)
---------- Post added at 01:01 PM ---------- Previous post was at 12:50 PM ----------
Since I can't link, I'm too new. You'll have to search youtube for Garminfone 2.1 root demo under user mjlar94. There are three videos, enjoy. You are now back on the grid using actively supported and updated applications.
I was unable to locate and disable the WhereTo app, this would take some discovery to find out if the GPS functionality is nested in the Garmin apk's. You should switch to google Nav/Places
Hi
Any help where can I fine the procedure on how to port Cyanogenmod 10 on a ICS phone? Can I do this on a stock rom of an ICS phone or do I need to wait for a JB Rom?
Hello all,
It's fantastic this works, but as you see i'm a noob. And these guidelines above are simply too difficult to follow...
I looked for the vid's but none of them show the whole deal...
Can you bee so kind to go thrue this step by step?
That would help me very much to get cyanogen on my Garminfone...
I'm waiting already very very long to do so...!!
So MLARIV, thank you in advance!
Grtz From Belgium
Dreezyne
What is a shame is native Adobe Flash is still not functioning properly with Opera 11 for Android.
Here's how I solved my issue with it - 'Simply' (lol) install Adobe Flash 10.x.x to SD card.
You MUST be rooted for this to work.
And please also be an experienced user ^>^
To do this:
Uninstall any UPDATES of flash that you already have.
And uninstall any opera versions you have.
Be sure to backup any bookmarks you have
Search Move2SD Enabler in the Market and install it,
Load Move2SD Enabler, read instructions on first page of app and hit 'Next,'
Choose 'External.' (It is your choice to return this option to the other two or leaving it as is after the tut ^>^)
Restart your device.
Okay. Next is tricky.
Here you have to have the Android SDK installed. And from here we call on that driver to detect the device. You also must have USB Debugging 'Enabled.'
You need an Explorer like app; I use Adao File Manager to search my device.
Navigate to /system/app/ - Here are all the installed apps, you will want to swipe through and remember the EXACT name you want to remove (Also, you need to type case sensitive).
Ex.: install_flash_player.apk or install_flash_player.odex
On the PC Open a CMD and navigate to the Android SDK:
C:\>
C:\>cd C:\Program Files (x86)\Android\android-sdk\tools
(Now type in ->)adb devices
(You'll see something like this
List of devices attached
0123456789ABCDEF device
(Now type in ->)adb shell
(Now type in ->)su- ENTER
(Now type in ->)cd /system/app
(Now type in ->)mount -o rw,remount /system
(Now type in ->)rm -r install_flash_player.apk
(Now type in ->)rm -r install_flash_player.odex
Now just exit CMD.
Then, restart your device again,
Next, go to an external source (other than the main markets i.e. 4Shared) for Adobe Flash 10.x.x and install that version.
Here, install Opera again and then go to Opera and see the labor you just put forth in action. Such as a site like Megavideo.com (in desktop mode).
Also, Youtube is still not working properly, not sure why..
(I also am not responsible for those of whom have "messed up" their devices ^>^)
(Thanks to user: qiuness)
I had purchased Teewe 2 Dongle from flipkart during Big Billion days for ₹999/-.
For your information Teewee is a HDMI dongle just like Google chromecast using which you can play the media stored on your phone/pc on your TV with HDMI. So i wasn't expecting much other than playing my media from the phone/pc.
But to my surprise Teewe 2 is running a full blown Android 4.2.2 . You can convert your TV into android smart TV using Teewee. Just follow the instructions below:
Requirements:
1. You need a Teewee dongle (obvious)
2. You need an android phone
Thats it.
Instructions:
1. Install ES File Explorer and Handy Smart TV on your android phone.
2. Download Handy Smart TV Launcher apk from mod edit - link removed
3. Connect Teewee to your TV and power it on.
4.Open ES File Explorer and select the Android TV option from the menu. It will display a device called rkXXXXXX. click on it and Select Applications
5. From the menu select install and browse to the location where you downloaded Handy Smart TV Launcher.apk. Voila The launcher is installed on your Teewee
6.. power off and power on your teewee.
7. open handy smart tv app on your smart phone. It should have connected to your teewee by now. In case it is not connected connect it by clicking the icon on the top right side. it should turn into blue from grey. press the home button on the Handy Smart TV app. It should launch the handy Smart TV launcher. U can also launch the Handy SMart TV launcher from the ESFileExplorer app from your android phone.
8. To learn how to use Handy Smart TV Launcher visit here
How to Install Google Play Store
1.you need to have adb tools installed on your PC and should have knowledge on how to use adb.
2. type the following command on your PC.
Code:
adb connect 192.168.1.101
where 192.168.1.101 is the IP address of the teewe dongle
you should get a response as
Code:
connected to 192.168.1.101
type
Code:
adb shell
on your PC
you should get a shell prompt which is already has root access
Code:
[email protected]:/ #
Now mount the /system folder with r/w access by the following command
Code:
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
unzip files in the Gapps.zip , move to /system/app on your PC and type the following commands
Code:
adb push GoogleBackupTransport.apk /system/app
adb push GoogleCalendarSyncAdapter.apk /system/app
adb push GoogleContactsSyncAdapter.apk /system/app
adb push GoogleLoginService.apk /system/app
adb push GoogleServicesFramework.apk /system/app
adb push NetworkLocation.apk /system/app
adb push OneTimeInitializer.apk /system/app
adb push Phonesky.apk /system/app
adb push SetupWizard.apk /system/app
The device is already rooted but the su binary is not updated and has root access to adb shell only so to have root access to other apps push the files in Root.zip . This is an optional step only for those who need root access.
Code:
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
and finally mount /system as r/o.
Code:
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
Thnk u so much
i followed ur steps carefullly and its worked !
thank you so much for sharing this awsum information ..im so happy
EDIT:[DETAILED INSTRUCTION UPDATED in the OPENING POST]
Google play is easy to install. Use adb connect to connect to the teewe . u will get a shell with root access . mount /system as r/w. push the google files necessary to /system/app folder. Mount /system as r/o.
Detailed instructions will follow as i am outside on holiday.
Meanwhile enjoy Playstore, and other apps on teewee. Android TV in Rs.999
After pushing tv launcher to tv
I saw select default launcher for a brief time
But was unable to sleect handy tv launcher in that
Now it opens default teewe launcher and not handy tv launcher
pritish_kul2 said:
After pushing tv launcher to tv
I saw select default launcher for a brief time
But was unable to sleect handy tv launcher in that
Now it opens default teewe launcher and not handy tv launcher
Click to expand...
Click to collapse
I had a similar issue. Went to ES Explorer.. selected Handy Smart and selected "launch"
Hope this helped
Thanks for this post. I could get the android TV functionality on my Teewe2. I have installed Kodi (XBMC) and now able to enjoy movies from my NAS. I tried installing play store but it needs Google play services to be installed. How do I get the correct version of google play services?
Application not installed...do you want to install. after opening handy smart. please help me out and unable to change the default launcher
Press the home button on the phone app. It should launch the launcher on TV. if it doesn't work, disconnect by long press the connection icon on the phone app and reconnect by pressing once. If u make handy smart tv launcher as default launcher, teewe app will not work even if u launch it from menu.( anyway i dont think u need it now).
Expect Google Play detailed installation procedure on 27/10/15
Need Play store to install the apps. Short procedure is posted above. Detailed procedure on 27/10/15 when i reach back home
ashazmirza said:
Application not installed...do you want to install. after opening handy smart. please help me out and unable to change the default launcher
Click to expand...
Click to collapse
Need Play store to install the apps. Short procedure is posted above. Detailed procedure on 27/10/15 when i reach back home
has anyone opened it and checked the hardware? teewe1 showed very promising results.
http://techbuzzzzzz.blogspot.in/p/blog-page.html
gpriyesh said:
Thanks for this post. I could get the android TV functionality on my Teewe2. I have installed Kodi (XBMC) and now able to enjoy movies from my NAS. I tried installing play store but it needs Google play services to be installed. How do I get the correct version of google play services?
Click to expand...
Click to collapse
Check the OP. I have updated detailed instructions on installing Play Store
ashazmirza said:
Application not installed...do you want to install. after opening handy smart. please help me out and unable to change the default launcher
Click to expand...
Click to collapse
Install Google Play Store to install Apps. Detailed Procedure in the OP
i have opened there are traces(requires soldering) for usb and otg but the ports were not present... we have to purchase usb female pin and solder onto the board.... so teewe 1 is the best choice..........
I have pushed smart TV launcher on the teewee thru es. But I am not able to connect it. Opened it on phone aswel.when I click on WiFi direct in settings it says looking for device and still nothing happens.
Request Mirroring For Features for teewe 2 android ?
After following all the steps was able to access play store but the device started disconnecting or shutting down after 2 - 3 minutes, not sure what's happening and what to do . Please help.
coolhunk4o2 said:
Need Play store to install the apps. Short procedure is posted above. Detailed procedure on 27/10/15 when i reach back home
Click to expand...
Click to collapse
Thanks for the detailed instruction. One question...where should I unzip the Gapps.zip file
coolhunk4o2 said:
Need Play store to install the apps. Short procedure is posted above. Detailed procedure on 27/10/15 when i reach back home
Click to expand...
Click to collapse
today is 28 oct plz soon post another procedure.
pradeep_k said:
After following all the steps was able to access play store but the device started disconnecting or shutting down after 2 - 3 minutes, not sure what's happening and what to do . Please help.
Click to expand...
Click to collapse
I too had shutdowns when the power source was TV or some other USB based Power source. I connected to the STB USB there too i had reboots.I think the Full Android requires more power and the power from TV/STB is not suffiecient. Once I shifted to the plug based power souce, no reboots so far.
I can't find much of any information on hacking the microsoft android emulator. Ideally, I'd like to get it working with superuser, exposed, etc, so it can be a fully functional way to see how android itself and apps work in different environments, all from my desktop. Also, I can just play around with stuff that I wouldn't touch on my tablet for fear of bricking it. I like playing with things.
Disclaimer: I'm not interested in maintaining anything, but as mentioned above, I can't find any information. Therefore, I'm simply posting what information I have here, in the hopes it will interest someone else enough to take a harder look at it. My original post was over here, but I've expanded beyond simply adding supersu to the image.
Things I can't do:
- Install superuser
- Install Xposed
- Install Google Play for anything more recent than KitKat
- Install recovery scripts
Things I can do:
- Run commands as root.
- Install Google Play Services on KitKat
- Change the screen resolution
- Change the amount of internal disk space
- Change the amount of memory and cpu cores available.
- Install busybox
- Flash simple scripts that don't require recent versions of cwm/twrp/other modern recovery.
----------------------------------------
Background information: The Microsoft Android "Emulator" is actually a HyperV virtual machine. When you install it, it enables the HyperV virtualization service in windows*. The effect of this is that instead of running android by emulating an arm processor, it runs android natively, with far better performance, by using Microsoft's hypervisor that's built into windows (win8+). You can work with it with Visual Studio and with Android Studio, but I don't use either much, so I can't help you with that. You can download it from Visual Studio if you want to (VS 2015 is free), or you can download a standalone version. I don't know if there's a difference between the two.
* I'm not sure if it installs the HyperV GUI as well, as I already use HyperV for other things and had it already installed. If you need to do so, you can install the GUI by going to add-remove windows features in the control panel ('appwiz.cpl' from the control panel).
----------------------------------------
Modifying the properties of the emulated system.
Configuration file location: After you create a device, the .cfg file for it will be located in %localappdata%\Microsoft\VisualStudioEmulator\Android\Containers\Local\Devices
To change the resolution: So far, I haven't identified any supported resolutions other than those listed in the device profiles list. So far, supported resolutions that I've used successfully are 480x800, 720x1080. You can edit the .cfg file for the specific device that you want to change the resolution of, and change the `device.screen.resolution=` line to any supported (see previous) resolution.
To change the size of the internal storage, follow the instructions here. You'll need an ubuntu cd; minimal install cd is fine if you have slow internet/computer or low ram.
To change the amount of ram or processors allocated to the virtual machine: Open Hyper-V manager, right-click the appropriate VM and click settings.
- Change the ram allocation by clicking Memory in the list at left. I do not know what happens if you try using Dynamic Memory; if it works, it should be more memory-efficient, but I left that alone. Now update the `device.vm.ram.size=` line in the .cfg file.
- Change the cpu allocation by clicking the Processor field. Please note that if you have hyper-threading, you should only use half your logical processors as cpus; the hyperthreaded 'cores' won't work as well (according to information online; you can check number of logical processors in windows task manager's performance tab). Now update the 'device.vm.cpu.count=' line in the .cfg file
----------------------------------------
Info on "recovery" and "flashing" - Installing google play
So far, I have only managed to get Google Play Services working on KitKat. I can't get it to work on Lollipop or Marshmallow (and haven't tried earlier versions at all); the virtual machine does *not* have a recovery or fastboot because of the way it works, and I haven't figured out any way of installing such. Instead, there's a simple shell file called install_zip.sh. It does not work with modern flashable zips that require TWRP/CWM; it only works with the old style zip designed for a specific architecture. As such, opengapps flashable zips will not work.
To install Google Play Services on KitKat (4.4.4)
1. Inside the emulator, open the browser and go to http://www.teamandroid.com/gapps/ and download the file linked under Gapps CyanogenMod 11.
2. Open the window the the android VM from the Hyper-V Manager to get console access. If you have ADB installed locally, you can use that in the future, but getting the VM's shared IP requires terminal access anyways (run `ip addr` as root inside the emulator to get the list of IPs).
3. Run `adb shell` to get access to the root shell (yes, it's that easy).
4. Run `install_zip.sh /sdcard/Downloads/gapps-kk-20140105-signed.zip` (or whatever the name/path for the downloaded gapps file is).
5. It should complete successfully. Now type exit to exit the adb shell, and close the hyper-v console window (the android emulator will continue running).
6. Click the 'X' at the top right of the Emulator to shut down/close the VM
7. Start the emulator back up. You should now have access to Google Play Services.
----------------------------------------
Busybox
The emulator does not come with a preinstalled copy of busybox. It does come with the android toolbox, but this has only a very minimal amount of commands in it. The instructions below are for installing stericson's busybox.
1. Get a copy of stericson's busybox from somewhere--your personal device, etc, it doesn't matter. The easiest way is to either install it on a real android device and grab it with airdroid (or other), or to use a play store scanner to get it. The file name will probably be something like stericson.busybox.apk.
2. Rename it to .zip so you can access the contents.
3. Extract the busybox-x86.png file from the 'assets' folder inside the zip, and rename it to `busybox`.
4. In the Android Emulator, click the >> button for tools, and click the sdcard header. Choose a folder (a new one on your dekstop will do) and tell it to pull the contents of the sdcard to the folder.
5. Move the busybox file into the Download folder that you just pulled from the sdcard. If you created a folder for this, you can delete it now.
6. Back in the android emulator, push the folder structure back into the sdcard; this will move the busybox onto the emulator.
7. Open the HyperV console for the emulator or open a terminal app in the android emulator (installing it is up to you)
8. Run `adb shell` to get a root prompt.
9. Run `mount -o rw,remount /system` to remount the system partition as writable
10. Run `cp /sdcard/Download/busybox /system/xbin` to copy the busybox binary over
11. Run `chmod 777 /system/xbin/busybox` to make the busybox binary executable.
12. Run `busybox --install /system/xbin` to copy the busybox binary for all the included applets. I think the -s paramter will symlink the applets to the main binary instead, but I'm not sure.
13. Type exit in the adb shell.
14. You can now run busybox commands in the terminal, and use apps that require busybox to be installed.
Now that you have busybox installed, you can use unzip, etc.
----------------------------------------
Hacking the OS itself.
The android emulator uses a VHD file for the disks. I've mounted the vhd file inside an ubuntu server to play with, and discovered several things about the way it works. The first partition is the boot partition, it contains 3 files:
- kernel - the android/linux kernel
- ramdisk - the ramdisk for the root filesystem. gzipped cpio archive.
- cmdline - the kernel parameters(? not sure what to call this)
I've tried modifying the ramdisk to add the init files for the superuser, but this doesn't seem to work properly; when I boot up the vhd file, I can open the console with hyper-v manager (the android emulator machines show up there automatically), and when it gets to the ramdisk, it says so--then the caps/num/scroll lights start flashing and it hangs. I haven't gotten any further than that at this time.
Hello,
I am looking to watch my PS Vue subscription on my rooted Galaxy S7. I've tried to use RootCloak to no avail. Added com.snei.vue.android to the application list to cloak but PS Vue comes back with "Not available for your device" after launching. Obviously it's still seeing the device is rooted.
Any thoughts on getting this to work? The Amazon Fire TV forum says to rename xbin/su and superuser.apk but adb is giving me a "device or resource busy" when running the first mv command.
For reference, here is what Fire TV users are doing to get theirs working on rooted FTV's:
Code:
adb shell
su
mount -o remount,rw /system /system
chmod 761 /system/xbin/su
mv /system/xbin/su /system/xbin/xsu
mv /system/app/Superuser.apk /system/app/XSuperuser.apk
Thank you for your help in advance.
MrBaltazar said:
Hello,
I am looking to watch my PS Vue subscription on my rooted Galaxy S7. I've tried to use RootCloak to no avail. Added com.snei.vue.android to the application list to cloak but PS Vue comes back with "Not available for your device" after launching. Obviously it's still seeing the device is rooted.
Any thoughts on getting this to work? The Amazon Fire TV forum says to rename xbin/su and superuser.apk but adb is giving me a "device or resource busy" when running the first mv command.
For reference, here is what Fire TV users are doing to get theirs working on rooted FTV's:
Code:
adb shell
su
mount -o remount,rw /system /system
chmod 761 /system/xbin/su
mv /system/xbin/su /system/xbin/xsu
mv /system/app/Superuser.apk /system/app/XSuperuser.apk
Thank you for your help in advance.
Click to expand...
Click to collapse
Hi
Try with Magisk , it works for android pay.....
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I want to use mine also. It worked on 2 roms I tried. I'm using a oneplus 3.then I switched to a other rom (one which I want to keep) and it's giving me that error.
Fix for Playstation Vue Mobile on Galaxy Note 10
I came across this page in my search and thought I'd come back to share the fix I found using RootCloak. I can't share links yet, but you can find the video on Youtube by searching "How to Hide Root on Android with RootCloak" by AppReviewBros.
1. Install Xposed-Modules from the Play Store
2. Open it and select "Download"
3. Enter: RootCloak
4. Swipe the RootCloak page to the left and select the latest download.
5. Once it finishes, click "Install"
6. Activate the module (you should see that your device has a new notification; just open it and check the box)
7. Go back to the home screen and reboot the device
8. After it restarts, open RootCloak
9. Select "Add/Remove Apps"
10. Press the "+" in the upper right corner
11. Find and select "PS Vue Mobile"
12. Go to your device's Settings>Application Manager>PS Vue Mobile>Force Stop
13. Run the Vue app again, and it should work!
jshea001 said:
I came across this page in my search and thought I'd come back to share the fix I found using RootCloak. I can't share links yet, but you can find the video on Youtube by searching "How to Hide Root on Android with RootCloak" by AppReviewBros.
1. Install Xposed-Modules from the Play Store
2. Open it and select "Download"
3. Enter: RootCloak
4. Swipe the RootCloak page to the left and select the latest download.
5. Once it finishes, click "Install"
6. Activate the module (you should see that your device has a new notification; just open it and check the box)
7. Go back to the home screen and reboot the device
8. After it restarts, open RootCloak
9. Select "Add/Remove Apps"
10. Press the "+" in the upper right corner
11. Find and select "PS Vue Mobile"
12. Go to your device's Settings>Application Manager>PS Vue Mobile>Force Stop
13. Run the Vue app again, and it should work!
Click to expand...
Click to collapse
Great mate
Yes latest RootCloak is working for me too. Just signed up for this thing, and would have been a dealbreaker if this didn't work.
What I'm hoping to find out is, if I could set up some kind of proxy here to make the app think i'm ALWAYS home...
VPN on home router
Phreaker47 said:
Yes latest RootCloak is working for me too. Just signed up for this thing, and would have been a dealbreaker if this didn't work.
What I'm hoping to find out is, if I could set up some kind of proxy here to make the app think i'm ALWAYS home...
Click to expand...
Click to collapse
As far as i know, you would have to setup a vpn service on your home router and then tunnel to it whenever you were not at home. Then all traffic would look like it was coming from your home router. Of course your download speed while tunneling would be limited to your maximum upload speed for your service connected to the router providing the vpn. I have successfully tried this with my own hardware and it works. Just be aware of the download/upload caveat i mentioned.
oneleft.ak said:
As far as i know, you would have to setup a vpn service on your home router and then tunnel to it whenever you were not at home. Then all traffic would look like it was coming from your home router. Of course your download speed while tunneling would be limited to your maximum upload speed for your service connected to the router providing the vpn. I have successfully tried this with my own hardware and it works. Just be aware of the download/upload caveat i mentioned.
Click to expand...
Click to collapse
I do have 24Mb upstream, but between the remote streaming they do allow and also getting access to the various networks' apps (Fox Sports GO etc), I'm not sure it's worth bothering. I also still have my trusty Plex server as well.
MrBaltazar said:
Hello,
I am looking to watch my PS Vue subscription on my rooted Galaxy S7. I've tried to use RootCloak to no avail. Added com.snei.vue.android to the application list to cloak but PS Vue comes back with "Not available for your device" after launching. Obviously it's still seeing the device is rooted.
Any thoughts on getting this to work? The Amazon Fire TV forum says to rename xbin/su and superuser.apk but adb is giving me a "device or resource busy" when running the first mv command.
For reference, here is what Fire TV users are doing to get theirs working on rooted FTV's:
Code:
adb shell
su
mount -o remount,rw /system /system
chmod 761 /system/xbin/su
mv /system/xbin/su /system/xbin/xsu
mv /system/app/Superuser.apk /system/app/XSuperuser.apk
Thank you for your help in advance.
Click to expand...
Click to collapse
Well I found a quick fix for that everyone is over analyzing it if you have SuperSU watch my video
https: // youtu.be/4uG8YcNMNhI
It appears I can't post links yet so you'll half to just backspace the empty spaces
I got it working by flashing Magisk instead of SuperSU in twrp. Then just download the Magisk Manager in the play store then select PSVue under magisk hide in the app.