{
"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"
}
INTRODUCTION:
The "hosts" file - what you typically use to block unwanted connections - in emulator's Android system is located in subfolder /system/etc. This file in most cases doesn't care of fact that not 127.0.0.1 ( 0.0.0.0 ) is the special alias to Windows host's loopback interface, but 10.0.0.2 - at least that's case with VirtualBox based emulator engines.
MVPS.org provides a "hosts" file ready for Windows PCs, for the reason pointed out before it isn't compliant to Android emulators: You'ld have to convert it to get it working.
To make life easier I made a small tool that
1. downloads the "hosts" file
2. converts it thus it suits emulator's Android
3. deploys it to Android emulators attached
and decided to make it publicly available.
DOWNLOADS:
Default
Mirror
Please do NOT SHARE these links anywhere else.
USAGE:
• Unpack the .ZIP-file
• Run Windows command script named "AndroidEmulatorHostsUpdater.bat"
IMPORTANT NOTICE:
Only works on properly rooted emulators where USB Debugging got enabled.
FYI:
Successfully tested on BlueStacks v4.50.0.1043 installed on laptop running 64bit Windows v10.0.17134.523.
BTW: I don't no longer use Chinese emulators because I noticed these throughout track you, send your data to Chinese servers and/or advertisers. BlueStacks, an US American product, does this not!
Related
Hey all,
http://www.codeplex.com/psmobile/
Installer is built using WiX ps extensions. Source snapshot of this release available as separate download, and also in codeplex TFS. I am not releasing the source of my common provider library, but symbols are included in the source download and it is not obfuscated.
Instructions and rudimentary guff about it on home wiki page, but more to come.
fun things to do:
ps c:\> add-pssnapin psmobile
ps c:\> cd mobile:
ps mobile:\> cd \temp
ps mobile:\temp> copy \windows\*.gif .
ps mobile:\temp> ii banner.gif
ps mobile:\temp> ii -local banner.gif
ps mobile:\temp> ii \windows\tasks.exe
ps mobile:\temp> convertfrom-wmfile *.gif c:\temp\
etc.
"Invokability" (visible via format-list) is determined via registry checks on local desktop AND remote device registry. Two additional atttributes are available for file modes: "i" and "m" for InRom and RomModule respectively. Attributes can be manipulated just like regular FileInfos, where permitted.
Have fun, and feedback/suggestions are very welcome.
- Oisin
updated 0.4.1
bugfix release: 0.4.1 - http://www.codeplex.com/psmobile
A picture's worth a thousand words:
{
"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"
}
Blog Post
http://www.nivot.org/2008/06/06/WindowsMobilePowerShellProvider.aspx
CEListFiles
From time to time I have the "pleasure" to see my WindowsMobile device struggle with low storage / low main memory. I get that low memory message and have no clue, what caused the problem, which program used the place up or what data files should rather be saved on memory card. Searching for files I can delete on the device itself is painfully slow, especially if I examine the Windows folder and it'S sub-folders. Using ActiveSync and the Explorer on the DesktopPC is better but not efficient too. So I wrote a little tool for myself I want to share with whomever it appeals to use it.
{
"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"
}
CEListFiles is a tool that displays the device's file/folder structure on your Desktop PC. There are a few special features:
it shows each folders size including all subfolders
it shows ROM files with a little "R" in the icon
it lets you export and import the file/folder structure so you can compare it to a previous state or have the file/folder structure analysed by a more experienced user without need to have access to the device
CEListFiles is easy to use:
connect your device to your DesktopPC via ActiveSync
select the folder you want to examine in the edit field ("/" for the all folders)
click the button bottom left
Attached you find the most recent version CEListFiles 1.5
If you like CEListFiles just buy me a beer.
I'm impressed: great work!
usefull for me too, let's test the speed
Hello,
I developed a new program for view processor and memory activity in a computer screen while the Android device is connected via USB.
Functionalities:
Take screen shoot and save it in your computer.
Reboot to (System, RecoveryMod or FastbootMod).
View Processor Activity and memory RAM and SWAP activity.
Just i need for a beta testers and if you want to integrate the Project developers team send me a private message. the source code will be published shortly on GitHub, and new features will come with the source code.
Contact me!
Downloads:
Android Debug Bridge.
the Jar Application
You need to:
A computer with Java installed.
Android device.
Activated ADB service in your android device.
install ADB service in your computer.
How to use:
{
"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"
}
for Window users:
You need to copy the Jar file to ADB repertory and double click the jar
for Linux users:
Run the jar with the commande:
Code:
:~$ java -jar AndroidProcessActivity-Beta_0.0.1.jar
getting devices list:
[*] HT**********
dev : HT**********
device HT********** is used as default.
The source code:
soon on github
works well, but I have a problem with the alignment of the buttons.
and when there is no device connected to the program is blank, you should do a window with a message: "no device did detect".
thank you.
For example you've BlueStacks, MEmu, LDplayer, Peak, etc.pp emulators on your Windows machine installed. Now you want to have apps installed on Bluestacks installed on other emulators, too, without doing this manually what is time-consuming undertaking.
So the question is:
How can I copy from the one emulator the installed 3rd-party APKs to another emulator?
The answer is quite simple:
You simply on the base emulator extract the installed 3rd-party APKs and then install
these on other emulator(s) by means of my tool provided here.
{
"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"
}
PROGRAM LOGIC:
The software's program flow ( top down approach ):
Stage 1
1. Sanity check
2. Verifying an emulator, what is the emulator to derive installed APKs from, is running
3. Enumerating installed APKs
4. Extracting installed APKs
Stage 2
1. Verifying emulators are running where APKs should get installed on
2. Installing previously extracted APK on all emulators running
DOWNLOAD:
Default
Mirror
USAGE:
• Unpack the .ZIP-file
• Run Windows command script named "PRIMITIVE-APK-SHOVELER.bat"
IMPORTANT NOTICE:
Only works on emulators where USB Debugging got enabled
and Google's "Android USB-driver for Windows" is properly installed
on your Windows machine.
SCREENSHOTS:
Hello,
I'm in the process of developing a single Android application that runs on multiple different types of devices.
From normal smartphone, tablet to Android TV.
The layouts and styling for each tend to look quite different.
To manually test these applications I can resort to using emulators.
A big downside to emulators is that they tend to take up a lot of valuable resources from the development machine.
Therefor I prefer using real devices. (Ideally just 1 device).
I can use my smartphone to test both the normal layout AND
with the help of the smallest width option in the developer settings I can also test the tablet layout.
{
"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"
}
However there is no such option available to spoof/fake Android TV/Google TV on my test smartphone.
AFAIK Android has a kind of prioritisation which layout it tries to inflate.
When it detects a device that has the android.software.leanback feature it will inflate the TV-layout which typically resides in the `layout-television` folder.
Programmatically I check it as such:
Java:
getPackageManager().hasSystemFeature(PackageManager.FEATURE_LEANBACK));
// PackageManager.FEATURE_LEANBACK == "android.software.leanback"
Reference documentation https://developer.android.com/reference/android/content/pm/PackageManager#FEATURE_LEANBACK
Since this system feature is missing for normal smartphones it will never work.
You can find the supported features with:
Code:
adb shell pm list features
After some digging I found you can add these system features when you have root access.
They are kept in the /system/etc/permissions folder.
So I simply copy-pasted the `tv_core_hardware.xml` from the Android source code after which I briefly saw my phone render my application in Android TV.
Also the hasSystemFeature(PackageManager.FEATURE_LEANBACK) returned true!
Unfortunately the screens goes completely black after a second or two and reboots in panic mode.
TLDR; How can you force Android TV on a rooted smartphone/tablet?
FYI my rooted test device is an OnePlus 6
Thanks in advance.