Database Users

[MOD][CHEF][TOOLS] AROMA Installer

{
"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"
}
The World First ANDROID Touch and Customizable ROM Installer
Don't Forget To Donate Me:
​
Android has an advance system for installing OS and updates, unlike other mobile OS that distributed the contents of OS in static ROM image(s), Android distributing the OS and updates in a plain zip file that contains all packages files and the updater for processing the installation.
The updater split in 2 type, the binary (update-binary) and script (updater-script), while the binary was executable files, and the script was configuration script that controlling the binary executable what to install.
But this advance technology never expanded into it highest potential ability, the update-binary was simply the linux executable wrote in C that runs in root mode, and can do anything into your system, including accessing Display FrameBuffer, accessing key and touch screen, set vibrate, runs programs, parsing files, loading png(s) and zip, and also reading and writing filesystem.
Old update-binary only support few functions that can controlled only by updater-script for installing the files, and not even one function that allowed the installer to show interactive user interface for users to input something that can manipulating the installing process. There is some program called "yesno" that show Yes or No interface, but it wasn't even enough to create more customizable updater.
Now with AROMA Installer update-binary, all this limitation was gone, and this advance technology already expanded into the highest level of its pontential.
Read More in amarullz.com [+]​
What is AROMA Installer
"AROMA" was taken from Bahasa Indonesia (Indonesian Language) and it's mean "Smells", but also abbreviation of "Amarullz ROM Manifest". It was advance update-binary for Android that contains many features like Wizard Installation, Touch User Interface (AROMA UI), Customizable Packages, System Inspecting, Themeable, and User Interactive. All release version will had "Smell Things" codename, example in 1st version it has codename "Anggrek" which mean "Orchid".
How AROMA Installer Works
It works because Chuck Norris drive the high tech jet plane with high tech technology to be able to control your phone in remote and show you an awesome Installer in your phone.
No, Seriously, When user select the zip file to install it, the recovery will extract the update-binary and runs it with few arguments, all process and stuff was simply handled by update-binary, the recovery only show the information passed by update-binary via custom pipe. The great things is that update-binary can do anything if we can code it in C/C++, but not all people can easily playing with C/C++, and Its not effective and not fun at all to compiled it every time we need to change the process. That's why the custom script also used in AROMA Installer, it was simply edify script that used in normal updater-script but with expanded functions available.
It wasn't a simple thing to archive something like this, because the update-binary is simply the "linux executable" that doesn't even supported with dynamic links of libraries, not even supported basic drawing functions like drawrect, drawline, and don't expect it can included OpenGL in it's binary. It's runs on it's own. Even User Interface was wrote from scratch to manipulating directly into display framebuffer, user input was readed directly from raw of kernel input device, png and zip was readed with static link library, and the configuration was parsed in it's own program. It was result of one full month of developing, but you can use it in an instant learning without even need to know how to manage memory usage and pointers.
The AROMA Installer will read, parsing, and run the script commands to show it's UI's, Calculate partitions sizes, create-read and write temporary prop files, set & get variables, do simple integer comparisons and math sequences, do the if else or inline if conditions, configuring UI color scheme, configuring rom information, and many more.
Because it wasn't that simple and need a lot of time to developing it, did I worth to get some donations from my works?.

Go To Here: http://forum.xda-developers.com/showthread.php?t=1461712

---- http://forum.xda-developers.com/showthread.php?t=1461712

Reserved - For Development and Script Sintax...

Reserved - For Theming and UI Customization Info & Downloads

Thanks To
Sebastiaan15
Prof Peach

What exactly does this thing do? and for average minds like me how will this help in daily use

[CHEF] TAG : Only for ROM Maker.
It was for zip ROM, so User will be able to customize their rom installation...

[TOOLKIT] Touchpad Toolkit - Android automated installer.

Touchpad Tool-kit - Android automated installer.
{
"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"
}
This is a complete tool-kit to get android on the HP Touchpad.
The pack is designed for easy installation of Cyanogenmod 9 (ICS 4.0.4) or Cyanogenmod 10 (JB 4.1.2).
What does the pack do?
•Step by step guided installation wizard, fully configures the users PC.
•Installs Novacom (32bit or 64bit)
•Copies the following files to the "Palm, Inc" folder, ACMEInstaller3, ACMEUninstaller, uImage.ClockworkMod
•Runs the ACMEInstaller3 install command to install android
•Works with CM9 or CM10 (most likely CM7 too, although this is untested)
•Runs on Windows XP, Vista, Windows 7 & Windows 8
•Advanced section for experienced users to only access what they need
•Runs the ACMEUninstaller to remove android (advanced section)
•Does NOT require java to be installed on your PC
Download (be sure to untick "Use our download manager and get recommended downloads"):
http://d-h.st/bNH
Notes
•*IMPORTANT* If you run CM10 then as soon as possible go into settings > Storage > three dots in top right > USB Computer connection, and tick "Media Device (MTP)"
•Will not work if run from a directory containing spaces in the name, Windows 7 "C:\Users\[user name]\Downloads\" will work, Windows XP "C:\Documents and Settings\[user name]\My Documents\" will fail. Windows XP users I advice you extract the "touchpad-xcd.zip" folder to your C:\ drive and not my documents.
•Files will fail to copy if not run as administrator on Windows Vista, 7/8
•Tested extensively on Windows XP, Vista, 7 & 8 by users of various abilities with 100% success.
Changelog
•Version 1 - 22/12/2012 - Initial pack released for limited testing
•Version 2 - 20/2/2013 - Updated pack, moboot 037 replaced by 038, batch file tweaked based on user suggestions, rolled out to wider audience.
•Version 3.1 - 21/02/2013 - Batch file updated to improve use and readability, password removed. 'uImage.ClockworkMod' is now only copied when doing an advanced memboot install, and not by default.

How do I use it? (Full guide to follow shortly)
•Download and extract the "touchpad-xcd.zip" zip file, using the password "xcdtouch" (without quotes).
•Connect your touchpad to your PC the same as normal to transfer files.
•Copy the included cminstall folder to the main directory of your touchpad.
•Decide if you want CM9 or 10, get one or the other NOT both.
•If you want CM9 then download the newest files from the following links
◦CM9 Android (official nightly)
◦CM9 Google Apps
•If you want CM10 then download the newest files from the following links
◦CM10 Android (jcsullins preview)
◦CM10 Google Apps
•Copy the android and google apps you just downloaded into the cminstall folder on the touchpad
•Rename the two files so the file names start with “update-“ (no quotes), so your cminstall folder looks similar to the following screenshot.
•
•Run the “run-me.bat” file (Windows Vista, 7 & 8, right click and run as Admin)
•Select standard user and follow the step by step guide in the batch file

Reserved

Reserved.

Tested just for some feedback and can confirm it works as intended on windows 8 Pro
Sent from my HP Touchpad >

Currently at 300+ downloads would appreciate some more feedback on whether anything needs tweaking. I'm taking the silence to mean that everything works great as it is.

Worked perfect for me.

Best and easiest method yet kudos. I was able to use this after bricking my touchpad trying to install SickleROM Alpha due to an improper ACME installer. Used webos doctor to get webos back and then used your batch file and everything was back to the way it was before the failed install so easy that even the most timid among us could do successfully. :thumbup:
Sent from my LG-P930 using xda app-developers app

Used this today. Quick and easy install. Thanks!

thanks for the app and time you spent to do it

Is it possible to install a rom which is based on CM9 (e.g., Fat'n Creamy) using this?
EDIT: I'm guessing not... I ran it, but it didn't seem to update CWM to the included version. :/

Does the camera and flash player work with this mod?

What steps do you take to keep up with the nightly updates for CM9?

Kanzar said:
Is it possible to install a rom which is based on CM9 (e.g., Fat'n Creamy) using this?
EDIT: I'm guessing not... I ran it, but it didn't seem to update CWM to the included version. :/
Click to expand...
Click to collapse
I would imagine you would just need to name it update-CM9FatnCreamy_Feb2813.zip
Also the same would go for CWM. update-CWM6.zip
Sent from my SAMSUNG-SGH-T989 using xda premium

All this does it makes it easier to install android.
App support comes down to the rom you install.
Flash will work natively on CM9, it will work on CM10 with a bit of messing, camera depends on if the rom supports it again.
IT should install any rom as long as it start's with 'update-' as mentioned above.
To update either use CWM as normal, or just copy the new rom (and gapps) into the cm9 folder and run my script again.

Installer works perfectly fine. Although it's not as automated as I thought it would be.

Well I could make the steps run themselves, but I like to let people know what's going on.

I haven't tried this one but Easy Installer has less work to it and does the same thing.

cdmcfud said:
I haven't tried this one but Easy Installer has less work to it and does the same thing.
Click to expand...
Click to collapse
Don't you a least think you should try before comparing/criticising it against something else!!!
It looks extremely good and professional to me.

Going to give this a try on my other touchpad but instead of using CM9 or 10 I'm going with Fat n Creamy.
http://forum.xda-developers.com/showthread.php?t=1944556

Run Google Glass on your Android phone

Xenologer: repackaging Google Glass XE5 APKs to run on other devices
Google Glass's build process is fairly conservative - they don't use hidden APIs often, and when they do, they use reflection. Thus, it is relatively easy to repackage the Glass APKs for other devices.
Modifications to the base APK
The use-library element in AndroidManifest is removed, as it refers to unused code.
com/google/glass/hidden/HiddenViewConfiguration.smali is patched to always return 0xffff instead of calling the nonexistent View.getDeviceTapTimeout
An instructional video (don_doff_background.mov, 8MB) is removed to save space.
All native libraries required are shipped with the APK, as are all the Glass fonts.
For the camera, instead of calling Camera.open() to get the rear facing camera, Camera.open(0) is called to get the first camera, as the Nexus 7 doesn't have a rear camera.
Install
Download the APK:
Home: http://zhuowei.github.io/Xenologer/glasshome-modded.apk
Camera: http://zhuowei.github.io/Xenologer/glasscamera-modded.apk
Maps: http://zhuowei.github.io/Xenologer/glassmaps-modded.apk
Setup: http://zhuowei.github.io/Xenologer/glassmaps-modded.apk
This one's been modified so that instead of scanning a barcode, it uses the existing Google Account to setup and then force closes.
Install just like any other boring APK. None of the Google Glass apps need system privilages. I do not recommend installing these APKs as system APKs, as the Glass apps will attempt to reboot the phone after a force close.
Glass apps that won't be converted
Hangouts: crashes on Android 4.2 due to a change in the underlying Android code. If you have another version of Android, try http://zhuowei.github.io/Xenologer/glasshangouts-modded.apk
GlassSound.apk: installs and runs without modification. Get a copy from any XE5 system dump. Not essential for Glass; Glass will just run muted without it.
GlassPhotosphere.apk: As stated by http://www.studio8apps.com/running-google-glass-photo-sphere-viewer-on-android-phone/ , runs (for the easter egg) without modification. Again, any dumped copy from a XE5 should run fine. Not essential to Glass.
Building these APKs from the modified dump
This area is still quite rough - I would love some help!
These sources are managed with a shell script (because I am not familiar with git submodules).
Run getsrc.sh then one of the build*.sh to build the APK you want. You need to modify them to suit your needs. In particular, there's a dosignapk.sh script that they call, which signs the APKs with your key. Go to http://developer.android.com/tools/publishing/app-signing.html for details.
You must have APKTool, 7Zip, and the Android SDK in your path.
Finally, note that the build scripts copy the com folder into the resulting APKs, as APKTool is too dumb to get them from the original APK.
Credits/License
While I don't have permission from the Glass team to post these, Google Glass is a device for explorers, thus, I believe it agrees with the spirit of discovery to post these APKs.
The APK was pulled from Android Police's dump at http://www.androidpolice.com/2013/0...em-dumps-please-do-something-cool-with-these/

Excited to test it! Thanx!

Think you have the wrong link for the 'Setup'
Can't seem to get it working properly even when I have downloaded the correct link, just keeps telling me to register it on my phone/pc.
Also is there a way to get past the warning page of the maps?

where is the setup link? D:
Sent from my LG-P500 using xda app-developers app

Apktool isn't too dumb in the future 2.0 version for "unknown" files/folders (ex /com), fyi.

zeratos said:
where is the setup link? D:
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
It's http://zhuowei.github.io/Xenologer/glasssetup-modded.apk
Sent by typing on my Xperia Sola with my fingers using xda premium

Its awesome, very responsive. Wish I had the hardware to use with it.
SGH-T999

Seems like the Maps and Camera apk link is dead..

Sorry for this dump question, but what is this? Google glass on android? Means the APK is taken from google glass? Can I install it on my S3 non-rooted?

paranoid android got me with their hover joke :S
but i was happy to find the original https://github.com/zhuowei/Xenologer?utm_source=feedly
and then this thread.
the files are mixed from XE5, XE6 and XE7
current build is XE12 ill try with the newest files later...
i like it alot but:
- Browser is not working (no connection)
- Directions do not work (same problem)
- camera has a weird error
but i get incomming mails....
maybe i need a 2nd device for the myglass app? trying later...
currently running paranoid android 4.2 beta 3 (4.2.2) gs3
a nice feature is if you use it with xhalo floating window and launch it in window mode as you can use the touchscreen
too bad it doesnt work with android wear..
{
"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"
}

update the links
pls update the links...
NOMIOMI said:
Xenologer: repackaging Google Glass XE5 APKs to run on other devices
Google Glass's build process is fairly conservative - they don't use hidden APIs often, and when they do, they use reflection. Thus, it is relatively easy to repackage the Glass APKs for other devices.
Modifications to the base APK
The use-library element in AndroidManifest is removed, as it refers to unused code.
com/google/glass/hidden/HiddenViewConfiguration.smali is patched to always return 0xffff instead of calling the nonexistent View.getDeviceTapTimeout
An instructional video (don_doff_background.mov, 8MB) is removed to save space.
All native libraries required are shipped with the APK, as are all the Glass fonts.
For the camera, instead of calling Camera.open() to get the rear facing camera, Camera.open(0) is called to get the first camera, as the Nexus 7 doesn't have a rear camera.
Install
Download the APK:
Home: http://zhuowei.github.io/Xenologer/glasshome-modded.apk
Camera: http://zhuowei.github.io/Xenologer/glasscamera-modded.apk
Maps: http://zhuowei.github.io/Xenologer/glassmaps-modded.apk
Setup: http://zhuowei.github.io/Xenologer/glassmaps-modded.apk
This one's been modified so that instead of scanning a barcode, it uses the existing Google Account to setup and then force closes.
Install just like any other boring APK. None of the Google Glass apps need system privilages. I do not recommend installing these APKs as system APKs, as the Glass apps will attempt to reboot the phone after a force close.
Glass apps that won't be converted
Hangouts: crashes on Android 4.2 due to a change in the underlying Android code. If you have another version of Android, try http://zhuowei.github.io/Xenologer/glasshangouts-modded.apk
GlassSound.apk: installs and runs without modification. Get a copy from any XE5 system dump. Not essential for Glass; Glass will just run muted without it.
GlassPhotosphere.apk: As stated by http://www.studio8apps.com/running-google-glass-photo-sphere-viewer-on-android-phone/ , runs (for the easter egg) without modification. Again, any dumped copy from a XE5 should run fine. Not essential to Glass.
Building these APKs from the modified dump
This area is still quite rough - I would love some help!
These sources are managed with a shell script (because I am not familiar with git submodules).
Run getsrc.sh then one of the build*.sh to build the APK you want. You need to modify them to suit your needs. In particular, there's a dosignapk.sh script that they call, which signs the APKs with your key. Go to http://developer.android.com/tools/publishing/app-signing.html for details.
You must have APKTool, 7Zip, and the Android SDK in your path.
Finally, note that the build scripts copy the com folder into the resulting APKs, as APKTool is too dumb to get them from the original APK.
Credits/License
While I don't have permission from the Glass team to post these, Google Glass is a device for explorers, thus, I believe it agrees with the spirit of discovery to post these APKs.
The APK was pulled from Android Police's dump at http://www.androidpolice.com/2013/0...em-dumps-please-do-something-cool-with-these/
Click to expand...
Click to collapse

[TOOL] AppDeploy 8.1 all capabilities

After few tries, I've fixed application deployer from SDK 8.1 to sideload xaps with all "restricted" capabilities in the manifest
(he-he, just curious why nobody did it before?)
1) Backup original deployer "AppDeploy.exe" and "Microsoft.Phone.Tools.Deploy.dll" from "C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\Tools\AppDeploy" first!
2) Unpack attachment and replace files.
3) Enjoy!
I've tested modified deployer on WPTweaker and WPH Tweak apps, works perfectly.
Cons: I was lazy to add original localization so modified deployer has only English lang.
P.S. Of course to be able sideload apps with "restricted" capabilities your handset must be interop-unlocked

sensboston said:
After few tries, I've fixed application deployer from SDK 8.1 to sideload xaps with all "restricted" capabilities in the manifest
(he-he, just curious why nobody did it before?)
1) Backup original deployer "AppDeploy.exe" and "Microsoft.Phone.Tools.Deploy.dll" from "C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\Tools\AppDeploy" first!
2) Unpack attachment and replace files.
3) Enjoy!
I've tested modified deployer on WPTweaker and WPH Tweak apps, works perfectly.
Cons: I was lazy to add original localization so modified deployer has only English lang.
P.S. Of course to be able sideload apps with "restricted" capabilities your handset must be interop-unlocked
Click to expand...
Click to collapse
Works fine so far. Many thanks.
Maybe you can give instructions how to add other localizations. I would like to add german localization for myself.

sorry does not work for the : WebAccess_0_5_6_AllCapabilities.xap

@megasounds, do you have a handset with all capabilities unlocked? You may compare error message from the original 8.1 deployer and modified, messages are different. In case of modified deployer, the error message came directly from phone or (maybe, I'm not sure) from Microsoft.SmartDevice.Connectivity namespace.

Can't deploy WPTweaker_Release_ARM_1.4.0.xap
{
"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"
}

@titi66200, do you have WP8.1 SDK installed? It's not a standalone deployer but just a replacement of "native" SDK tool.

Yes.
I have build "MDILFileList.xml" with MDILXAPCompile.exe and rezip Xap.
And now i can deploy WPTweaker_Release_ARM_1.4.0.xap

titi66200 said:
I have build "MDILFileList.xml" with MDILXAPCompile.exe and rezip Xap.
Click to expand...
Click to collapse
Kinda strange 'cause I've tested on my xap downloaded from xda thread (for the test purity).
P.S. BTW, could you try to sideload other "interop-only" apps? (except @GoodDayToDie's WebAccess_AllCapabilities - I don't know how to sideload that app to the handset with "usual interop", not a "sammy" with the custom bits)

Can the coveted tetra lock screen app 1.2.0.0 finally be deployed? I'm currently on winmo 10 and can't test lol

megasounds said:
sorry does not work for the : WebAccess_0_5_6_AllCapabilities.xap
Click to expand...
Click to collapse
That's about half my fault and half Microsoft's; the AllCapabilities version of the webserver includes *all* the capabilities that were usable by a third-party app in 8.0 (even if they aren't necessarily used for anything). Microosft removed some of those in 8.1. This results in trying to install an app that requires capabilities which the OS doesn't even understand.
Workaround is to remove capabilities from the app's manifest until it installs. Alternatively, use the normal-caps version (or another registry browser) to see all the available capabilities - they're under HKLM\SOFTWARE\Microsoft\SecurityManager\Capabilities) - and remove the ones in the app's manifest that aren't supported.
I'm really sorry for not updating the app in so bloody long. I got stuck on some really huge set of changes for it that aren't working right yet, and then I got swept up in another project altogether, and that + life generally being busy (travel, girlfriend, day job, you know the drill) has meant I've been neglecting that app. I need to switch back to the stable branch, fix the capabilities, and release a trivial update. I'll try to do that as soon as possible (but my dev PC is temporarily dead, so I'll need to use my laptop, and I've got plans with friends tonight... again, you get the idea). Sorry again.

I've changed slightly AppDeploy (forgot to add app icon in the initial post ); also added decompiled sources (in case someone want to improve/add own localization - but my 2¢ - don't waste you time )

Removed ID_CAP_SOUND_CONTROL in "WMAppManifest.xml"
Added "WindowsPhoneReservedAppInfo.xml"
Code:
<?xml version="1.0" encoding="utf-8"?>
<WindowsPhoneReservedAppInfo xmlns="http://schemas.microsoft.com/phone/2013/windowsphonereservedappinfo" PinableOnKidZone="false">
<SoftwareCapabilities>
<SoftwareCapability Id="ID_CAP_SOUND_CONTROL" />
</SoftwareCapabilities>
</WindowsPhoneReservedAppInfo>
And i can deploy with original AppDeploy.

Hmm, I thought WindowsPhoneReservedAppInfo.xml is just for WinRuntime apps, not Silverlight...
@titi66200, are you able to see/play ringtones after that change (tap any button on the "Sounds" page)?

Yes all Works
Edit
glancescreen.xap is RuntimeType="Silverlight" and use "WindowsPhoneReservedAppInfo.xml"

Wow, pretty cool trick, thanks! I'll add your solution to the WPTweaker project.

sensboston said:
Wow, pretty cool trick, thanks! I'll add your solution to the WPTweaker project.
Click to expand...
Click to collapse
could anyone post not modified files here ?
today I am not able to sideload and debug any apps . and I can't remember where were my backed up files

AppDeploy.exe and Microsoft.Phone.Tools.Deploy.dll.

titi66200 said:
AppDeploy.exe and Microsoft.Phone.Tools.Deploy.dll.
Click to expand...
Click to collapse
I don't know why but I get Error - the specified module could not be found !

What app you try to deploy?

titi66200 said:
What app you try to deploy?
Click to expand...
Click to collapse
any app .
I am working on a new app when app has an error in mainfest or etc. it tells the error but It can't find module to install xap / appx or any other type of apps

[TOOL][ADB][Windows]RAM-Hog Sniffer For Rooted Android Emulators

Given the case you feel your favorite Android emulator runs slowly, especially at a certain game, then you should remind that Android emulator's (AVD) performance mainly depends on correct setting of its
A: Android per app Heap Size granted
B: VM total RAM (read: Random Access Memory) allocated off host machine
Most emulators don't automatically take care of this, they are preset to standard values: it's on the user to correctly configure it.
User has to check and monitor for the RAM usage of an individual app/game on Android, has to check which app/game is eating the maximum RAM and affecting the performance.
Yes, for me one of the fundamental questions users ask (or at least, they should) is: how much memory is my program using? It may be a simple question, but with a virtual memory operating system like Android the answer is quite complex.
By default Android OS - a derivate of Linux OS - since ages comes with procrank tool, what in detail shows you some RAM metrics for an application as those are VSS, RRS, PPS and USS. So also Android OS provided by the various emulators should do it, too.
Installed Terminal Emulator app on some wellknown emulators and ran procrank. Experienced that on Android emulators like
BlueStacks 4 ( Android Nougat )
PROCRANK doesn't work at all, you get message: "error creating kernel interface -- does this kernel have pagemap?"
MEmu 6 ( Android Nougat )
PROCRANK doesn't exist - means isn't implemented at all
NOX 6 ( Android Nougat )
PROCRANK isn't working, you get message: library "libpagemap.so" not found
Genymotion 3 ( Android Nougat )
PROCRANK doesn't work at all, you get message: "error creating kernel interface -- does this kernel have pagemap?"
Maybe someone knows reasons for that?
Hence, to get out the app/game specific RAM metrics ( read: VmPeak, VmVSS, VmHWM, VmRSS and VmPSS ) on an Android emulator, I wrote a Windows command script ( ~50KB ) that running against a rooted emulator gives them to me: I named it RAM-hog Sniffer. Notes: It's provided on an "AS IS" basis, it's free software, and you are welcome to redistribute it under license GPLv3.
Successfully tried it on properly rooted and ADB-enabled BlueStacks v4.50.5.1003 ( Android Nougat ):
Excerpt of logfile created:
{
"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"
}
Useful or not is for you to tell, give it a try and leave a comment with suggestion if indicated.
Usage:
• Download the attached ZIP and unpack it on Windows PC into any location of your choice
• Connect a rooted and ADB enabled emulator to PC
• Run Windows batch-file named RAM-hog-Sniffer
FYI: You will need to install the Android ADB drivers if your emulator is not detected.
PS: Please, do NOT share this elsewhere - I want to be able to update if necessary.

Script revamped. New version is in OP.

gr8. ty

To keep you updated: BlueStacks announced to fix the PROCRANK problem

According to the description I think something good,
but, can the script, not to change to the installed system,
for editing on a computer.>?

Ciuma777 said:
According to the description I think something good,
but, can the script, not to change to the installed system,
for editing on a computer.>?
Click to expand...
Click to collapse
You use any ANSI-editor of your choice, preferredly of course Notepad++, to edit the script on your Windows computer according to your needs.