Database Info

[APP][2.2+][24 Jul - v0.11] CommandCenter the power of shell without the terminal

Have you ever dreamed of an app to execute your favorite shell commands, whether it is for collection dmesg/logcat/dumpsys or set kernel parameters.
Well here comes CommandCenter, a generic app for grouping all your favorite commands.
CommandCenter is free with ads and can be downloaded from the Google Play (please be patient, it takes a while to update as I just published)
It is also open source and your can check my repo to inspect / review the code.
If you are a kernel developer you may want to provide a tool for your users to run certain commands without havint to maintain an app for that; if yes just submit a Command Set and have your users download it.
If you are a poweruser there are commands that you use all the time, wither from adb shell or in the terminal. Make one or multiple Command Set and enjoy the comfort of an Android app and the power of your favorite commands.
From version 0.10 a Locale / Tasker Plugin was added to execute command from actions.
{
"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"
}
How it works
The command sets are stored of the sdcard in the app's private folder /sdcard/Android/data/com.asksven.commandcenter/files in the form of json files. On load the files are parsed and each file (Command Set) shown as a tab.
A single click on a Command displays its details, a long click pops up a dialog from where you can run the command (this is configurable in the preferences).
A command has two parts:
- the command to be executed itself: it may contain a variable and in that case a popup will ask for the value to be used
- an optional command to retrieve a status: if a status can be read it will be displayed
CommandCenter comes with two pre-configured Command Sets:
- general commands for logging / diagnosis
- a few command for Fracisco Franco's awsome GN kernel
Want to contribute?
If you want to create and distribute command set just drop me a PM. I would be happy to give you more details about the syntax of the command sets and there is a section in this thread to list authored Command Sets. I may also add some to the Market app.
Caution
Always check the command's before running them. CommandCenter support 'su' command and you should know what you do as those could harm your phone. I will not take any responsibility for any dammage caused by command run using CommandCenter
Contact
You can contact me here (PM, this thread) or on twitter

Release Notes
v0.11.0 2012-07-24
Major fix: added synchronization to avoid freeze conditions
#24: "refresh" reads changes on command collections from the external storage
#26, #27, #28: different error conditions from reports
v0.10.1 2012-05-06
#15: samples scripts were being re-created on every start instead of once at first install
#14: FC when turning to portrait
#16: FC when number of result lines for a command < 5
#17: Various FC conditions from google play logs
#21: error in one script should not cause the other not to load
v0.9.0 2012-03-10
Solved stability issues (threaded processing)
Tablet support
#8: new command dialog layout
v0.8.0 2012-02-24
#4 Popup menu was called "edit"
#5 added support for user defined and editable commands
#6 added support for commands returning data
v0.7.2 2012-02-12
#2: dumpsys missing su, and logcat files have zero-length
#3: A few issues with backward compat to Android 2.1/2.2 fixed
v0.7.1 2012-02-11
#1: fixed Android 2.1 compatibility issue
v0.7 2012-02-11 Initial release

Command Sets
If you want to create command set for CommandCenter please read this

FAQ
For future use

sounds quite nice, can't wait to try. Have been using Tasker + Secure Settings for that so far, let's see how it compares.

V0.7.1
Fixed a minor issue with Android 2.1 (getExternalFilesDir does not exist on Eclair)

When I try and dump logcat radio or logcat it creates the file but it's blank. Also when I dump alarms the file reads Permission Denial: can't dump AlarmManager from pid=5637, uid=10128. ComandCenter never ask for SU Permissions. I ran the dump alarms with su permission from the terminal and it worked fine. HTC Inspire running ICS.

harpo1 said:
When I try and dump logcat radio or logcat it creates the file but it's blank. Also when I dump alarms the file reads Permission Denial: can't dump AlarmManager from pid=5637, uid=10128. ComandCenter never ask for SU Permissions. I ran the dump alarms with su permission from the terminal and it worked fine. HTC Inspire running ICS.
Click to expand...
Click to collapse
Ok the alarm dump is fixed, it was a definition error in the command set (dumpsys did not require su).
Testing the other commands now on rooted and unrooted device

V0.7.2
Fix-Release is rolling out, see post #2 for release notes.
I did quite a lot of testing on 2.1, 2.2, 2.3 and 4 devices with and without root and I hope the fixes work for everyone.

chamonix said:
Fix-Release is rolling out, see post #2 for release notes.
I did quite a lot of testing on 2.1, 2.2, 2.3 and 4 devices with and without root and I hope the fixes work for everyone.
Click to expand...
Click to collapse
Thanks for fixing this so fast. Everything is working perfectly now. Great app.

Another great release from chamonix
I have been looking for an app like this..so thank you very much. Now I'll start study it to take full advantage from it
Sent from my sandwiched SGS

It's time to collect some feature requests and build some use cases. Do you guys have suggestions for feature or know a kernel dev who has no time to write a sexy "settings" app. I'd be happy to provide the command sets while finalizing the schema aiming at making it public for contributors

Should it be possible to add or modify the command sets? I don't seem to be able to do either. In Edit mode, my soft keyboard never open and I don't see any option to create a new command set. Maybe I'm just not looking in the right place?
This is on a Samsung Galaxy Nexus running a rooted AOSP ICS.

short/y said:
Should it be possible to add or modify the command sets? I don't seem to be able to do either. In Edit mode, my soft keyboard never open and I don't see any option to create a new command set. Maybe I'm just not looking in the right place?
This is on a Samsung Galaxy Nexus running a rooted AOSP ICS.
Click to expand...
Click to collapse
In fact the is no way of editing the commands from within the app. I have been thinking about that a lot and the functionality itselt is not the problem (it occurs to me that the popup menu is named "edit" and this is of course not correct).
The reason I did not provide edition of commands within the app is that I want to offer a distribution channel for authors to update their command sets. Those updates would overwrite the local changes.
What you can do to edit the commands is edit the json files located on the sdcard in Android/data/com.asksven.commandcenter/files (one file per command set).
Do you feel the need to have "local" commands as well that could be edited from the app and stored in a local database?

chamonix said:
In fact the is no way of editing the commands from within the app. I have been thinking about that a lot and the functionality itselt is not the problem (it occurs to me that the popup menu is named "edit" and this is of course not correct).
The reason I did not provide edition of commands within the app is that I want to offer a distribution channel for authors to update their command sets. Those updates would overwrite the local changes.
What you can do to edit the commands is edit the json files located on the sdcard in Android/data/com.asksven.commandcenter/files (one file per command set).
Do you feel the need to have "local" commands as well that could be edited from the app and stored in a local database?
Click to expand...
Click to collapse
Local commands would be handy also you can do generics for brand htc Samsung etc as the kernels tend to have commands in the same spot, also a log viewer would be cool but they are. Readily avaliable
Sent from my HTC Evo 3D using Tapatalk

Auto upload to paste bin would be sick and the ability to email to dev as well as adding the kernel version to the file name
Sent from my HTC Evo 3D using Tapatalk

chamonix said:
In fact the is no way of editing the commands from within the app. I have been thinking about that a lot and the functionality itselt is not the problem (it occurs to me that the popup menu is named "edit" and this is of course not correct).
The reason I did not provide edition of commands within the app is that I want to offer a distribution channel for authors to update their command sets. Those updates would overwrite the local changes.
What you can do to edit the commands is edit the json files located on the sdcard in Android/data/com.asksven.commandcenter/files (one file per command set).
Do you feel the need to have "local" commands as well that could be edited from the app and stored in a local database?
Click to expand...
Click to collapse
Yes, I'd like to have that. I can think of a few I'd like to have NOW as opposed to waiting for someone to come up with them
Code:
df -h /sdcard
df -h
ls -lrt /mnt/sdcard | tail
ls -lrt /sdcard/Download | tail
ping www.google.com
ifconfig lte_rmnet1
netstat -rn
netstat -l
netstat | grep CLOSE
uptime
And probably few others that I could come up with once I really thought about it. Why not have "protected" command sets which are updated thru the app or Market and "user" or, as you call them, "local"?

First of all, thanks for develop another great application.
I concur that having the possibility to add commands is really a 'must have'. Of course, if we are thinking about to create commands, this means all of us have already a terminal app installed to run them, but the purpose of this app is to make life easier for having our favorite commands ready to execute. Many of these commands are possibly a small subset of common ones, but even with that, I probably prefer to redirect the output to a diffferent place that abother user using the same command. So having a 'user tab' to be able to add, edit and delete commands (also maybe copy a command from other tab) will be very useful.
Anyway, congrats for comming up with this useful app.

short/y said:
Yes, I'd like to have that. I can think of a few I'd like to have NOW as opposed to waiting for someone to come up with them
Code:
df -h /sdcard
df -h
ls -lrt /mnt/sdcard | tail
ls -lrt /sdcard/Download | tail
ping www.google.com
ifconfig lte_rmnet1
netstat -rn
netstat -l
netstat | grep CLOSE
uptime
And probably few others that I could come up with once I really thought about it. Why not have "protected" command sets which are updated thru the app or Market and "user" or, as you call them, "local"?
Click to expand...
Click to collapse
One question about those commands: some of them return results that will not fit on one line and so would not fit in the space reserved for the status (lower line in the list).
How would you like to display the result?
- as a popup when running the command
- as a multi line status field 'growing' when required and updating automatically

pp1276 said:
First of all, thanks for develop another great application.
I concur that having the possibility to add commands is really a 'must have'. Of course, if we are thinking about to create commands, this means all of us have already a terminal app installed to run them, but the purpose of this app is to make life easier for having our favorite commands ready to execute. Many of these commands are possibly a small subset of common ones, but even with that, I probably prefer to redirect the output to a diffferent place that abother user using the same command. So having a 'user tab' to be able to add, edit and delete commands (also maybe copy a command from other tab) will be very useful.
Anyway, congrats for comming up with this useful app.
Click to expand...
Click to collapse
I am convinced: https://github.com/asksven/CommandCenter/issues/5

[DATABASE] Best Root Apps [Updated 03 nov]

Most of you might be very much familiar with the rooting procedure. Its the process of giving yourself superuser permissions (ex - administrator in windows xp ).
If you are using a custom rom, then there is no need to specifically root your phone. But if you are using stock roms, then there is a guide to root in the forums.
Once rooted, you can now take your own decisions for your device which include improving system performance or flashing custom roms using cwm recovery or using any of these below listed apps. Use it wisely, as playing with your device performance can have damaging effects.
I AM NOT AT ALL RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE BY YOU.
Moving on, many of the rooted-on-stock and custom rom users might already know most of these apps and their uses, so this thread is for the beginners who have just rooted their devices.
Further, most of these apps are available in the playstore (mostly paid, but if you want the cracked versions, you can find them in the internet.
So here are some of the apps that might be useful for you. I will also update this apps list as soon as, I find more useful apps.
SPECIAL THANKS TO Android_United
Original Thread:Link
HIT THANKS IF YOU LIKE THIS THREAD.
TITANIUM BACKUP ROOT
{
"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"
}
Description
EXTREMELY powerful tool. Backup ALL apps, Market links, remove bloatware & MORE!
☆Needs ROOT, Android 1.5-4.1+ (ARM,x86,MIPS)
☆Over 6.5 million users, 29+ languages.
☆PRO Key is available on Play Store!
☆Voted #1 TOP ROOT APP on Twitter.
☆Problem? See titaniumtrack.com/kb
☆Scroll down for more info & DEMO VIDEOS
☆ ☆ ☆
Titanium Backup is the most powerful backup tool on Android, and then some.
You can backup, restore, freeze (with Pro) your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card. You can do 0-click batch & scheduled backups. Backups will operate without closing any apps (with Pro). You can move any app (or app data) to/from the SD card. You can browse any app's data and even query the Market to see detailed information about the app.
Also see the paid PRO key which adds EVEN MORE awesome features such as:
[✔] 0-click batch restores
[✔] Keep multiple backups per app
[✔] Backup/restore SMS,MMS,calls,bookmarks,Wi-Fi AP as XML
[✔] Multi-user app data
[✔] Apps freezer
[✔] Sync to/from Dropbox (manual/scheduled)
[✔] Sync to/from Box (manual/scheduled)
[✔] Sync to/from Google Drive (manual/scheduled)
[✔] Convert user apps <=> system apps
[✔] Integrate system app updates into ROM
[✔] Encryption
[✔] Market Doctor (relink apps to Market)
[✔] "Destroy all Market links" feature
[✔] Hypershell speed
[✔] Backup apps without closing them!
[✔] Restore individual apps+data from non-root ADB backups!
[✔] Restore individual apps+data from CWM backups!
[✔] Restore individual apps+data from TWRP backups!
[✔] Market "auto updating" manager
[✔] Dalvik cache cleaner
[✔] Integrate Dalvik cache system elements into ROM
[✔] Unlimited schedules
[✔] Load/Save a Filter and use it in Widgets/Schedules
[✔] Change the device's Android ID, restore it from a backup or after a factory reset
[✔] Protect backup against deletion
[✔] Send backup (to e-mail/cloud) and import it in 1 click
[✔] Backup→Verify→Un-install an app in one shot
[✔] Freeze/defrost/launch apps in a single click
[✔] CSV export any app DB (e-mail or Google Docs)
[✔] Convert app data to/from fast WAL format
[✔] WAY MORE!
Check out this in-depth review of TB PRO:
http://youtube.com/watch?v=vuvDTS9RDrM&hd=1
And check out the new TB PRO demo video:
http://youtube.com/watch?v=YU33zabluSY&hd=1
More info on permissions:
• "Internet" is used to access Market,Dropbox,ChangeLog.
• "Accounts" is used to access Market.
Some advice:
• We recommend to avoid "modified" TB versions because they can cause various problems down the road.
ROOT EXPLORER (File Manager)
Description
Root Explorer is the ultimate file manager for root users. Access the whole of android's file system (including the elusive data folder!).
Features include SQLite database viewer, Text Editor, create and extract zip or tar/gzip files, extract rar archives, multi-select, execute scripts, search, remount, permissions, bookmarks, send files (via email, bluetooth etc), image thumbnails, APK binary XML viewer, change file owner/group, create symbolic link, "Open With" facility, MD5, create shortcuts.
For fast, friendly support simply email us: [email protected]
We will always try to help with any problem you may have with the app. If we can't help then you can have a refund, no questions asked.
Although 14,000+ five star ratings will tell you that most people are very satisfied customers. Make sure you read as many comments as possible to get a good idea of what most people think of the app.
We still respect the old 24 hour refund policy. So if you're not happy with the app just email us within 24 hours and you can have a refund. We'll need to know the order number, which you can find on the emails sent to you by Google when you downloaded.
Why compromise? Get the original and the best!
[root] MOBILE ODIN PRO
Description
Mobile ODIN - Full firmware flashing straight from the device itself!
Mobile ODIN is the on-device firmware flasher of choice. Just throw those firmware files on your (internal or external) SD card, start Mobile ODIN and flash away.
! Your device must be rooted to be able to use Mobile ODIN. Check the list below to see if your device is supported !
If you use the EverRoot option, Mobile ODIN will root the firmware while you flash it. Checking out that new leaked firmware? No reason to lose root!
Currently supported devices:
- Samsung Galaxy S GT-I9000/B/M
- Samsung Galaxy S GT-I9003/L
- AT&T/Rogers Captivate SGH-I896/I897
- Samsung Galaxy S2 GT-I9100/T/G/m
- Samsung Galaxy S2 SHW-M250S/K
- Samsung Galaxy S2 SC-02C
- AT&T Galaxy S2 SGH-I777
- Sprint Epic 4G Touch SPH-D710
- US Cellular Galaxy S2 SCH-R760
- Samsung Galaxy S3 GT-I9300/T
- Samsung Galaxy S3 GT-I9308
- AT&T/Canadia Galaxy S3 SGH-I747/M
- TMOUS Galaxy S3 SGH-T999
- Sprint Galaxy S3 SPH-L710
- VZW Galaxy S3 SCH-I535 (unlock bootloader !)
- US Cellular Galaxy S3 SCH-R530
- Samsung Galaxy S3 LTE SHV-E210S
- Samsung Galaxy S3 LTE GT-I9305
- Google Galaxy Nexus (GSM) Maguro/Yakju/GT-I9250
- Google Galaxy Nexus (CDMA/LTE) Toro/Mysid/SCH-I515 (no cdma radio flashing)
- Samsung Galaxy Note GT-N7000
- Samsung Galaxy Note GT-I9220
- Samsung Galaxy Note GT-N7000B
- Samsung Galaxy Note 2 GT-N7100
- Samsung Galaxy Note 2 LTE GT-N7105
- Samsung Galaxy Note 10.1" GT-N8000
- Samsung Galaxy Note 10.1" Wi-Fi GT-N8010/N8013
- Samsung Galaxy Tab 7" GT-P1000
- Samsung Galaxy Tab 7.0 Plus GT-P6200
- Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210
- Samsung Galaxy Tab 7.0 Plus GT-P6200L
- Samsung Galaxy Tab 7.7" GT-P6800
- Samsung Galaxy Tab 7.7" Wi-Fi GT-P6810
- Samsung Galaxy Tab 10.1" GT-P7500
- Samsung Galaxy Tab 10.1" Wi-Fi GT-P7510
- Samsung Galaxy Tab 2 7" GT-P3100
- Samsung Galaxy Tab 2 7" Wi-Fi GT-P3110/P3113
- Samsung Galaxy Tab 2 10" GT-P5100
- Samsung Galaxy Tab 2 10" Wi-Fi GT-P5110/P5113
- Samsung Galaxy 5 GT-I5500/B/L/T/M
- Samsung Galaxy 5 GT-I5503/T
- Samsung Galaxy 5 GT-I5508
Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear.
For discussion and support: http://forum.xda-developers.com/showthread.php?t=1347899
- MANUAL -
Flashing with Mobile ODIN is easy. You start by starting the app and the app will check your system has everything it needs to continue (like root). It may need to download an additional package, so it is advised you have Wi-Fi available.
Now you should see the main Mobile ODIN screen. It will list a set of partitions. Clicking a partition will allow you to select a file from your SD card to flash to that partition. Do not worry about selecting the wrong file - Mobile ODIN will not let you. Separate files (named after the partition) as well as .tar and .tar.md5 files are supported.
From the desktop ODIN you may be used to "PDA", "PHONE", and "CSC" buttons. All three of these buttons have been replaced by the "Open file ..." button. This button will open the file you select from the SD card, and find all the partitions it can flash inside that file. So if you select a .tar file containing kernel and modem, the Kernel and Modem partitions will be set up to use that .tar file for flashing.
Now that we have selected what we want to flash, if you have the Pro version you can proceed to the EverRoot section. The EverRoot options allows you to root your firmware while it is being flashed. Never again will you be without root! Select here which apps you want to inject in the firmware that is being flashed.
Now that we are all done selecting partitions and configuring EverRoot, we continue to "Flash firmware". Mobile ODIN will gather all the information it needs and perform the flash. Before starting, however, it will check that your battery level is over 50%, and if applicable offer to verify MD5 checksums on the files you have selected to flash. If all is well, it will reboot into recovery mode, and flash the firmware you have selected.
ROM MANAGER
Description
Must have app for any root user. Make backups, flash ROMs, and own your device.
ROM Manager is THE MUST HAVE APP for any Android root user. (Over 3 million downloads and counting!)
* Flash your recovery to the latest and greatest ClockworkMod recovery.
* Manage your ROMs via a handy UI.
* Organize and perform backups and restores from within Android!
* Install ROMs from your SD card.
* Install your favorite ROMs over the air!
Premium Version:
* Premium ROMs
* Receive notifications for when your ROM is updated!
* Automatic backups
* Install from QR Code
* Web Connect
* Support
Do you prefer using only recovery manually? Check out the Touch Recovery in app purchase, for the most advanced recovery available!
Why does ROM Manager ask for account permissions?
Web Connect only needs to access your Google account to connect it to your google account. It can't access any private data or passwords.
Troubleshooting:
Droid users: Stuck at the "M" logo? Flash an alternate recovery and flash back to ClockworkMod.
HTC Users: Flash recovery not working? Try fastbooting a recovery on.
Droid X/2/Pro Users: You must run the Bootstrap application first to use ROM Manager.
Samsung users: You must flash a Clockwork compatible kernel first (see XDA forums)
IF YOU ARE HAVING LICENSE ISSUES, MAKE SURE YOU HAVE THE LATEST VERSION OF FREE (4.0+) AND THE LATEST LICENSE (1.0.7+) INSTALLED!
SETCPU for Root Users
Description
Supercharge your Android device with SetCPU. A must-have tool for root users.
SetCPU is a tool for changing the CPU settings on a rooted Android phone or tablet, including the Galaxy Nexus, HTC One series, Nexus S, Nexus One, Motorola Droid, Samsung Galaxy series, and most other devices. You're under control: SetCPU can improve your performance, save battery, or both!
Automate SetCPU with profiles! SetCPU allows you to set up powerful profiles to change your settings under certain conditions, such as what app is running, when the phone is asleep or charging, when the battery level drops below a certain point, when the phone's temperature is too high, or during certain times of day. See the screenshots for examples of how you might set up profiles.
SetCPU's wide feature set make it useful to Android beginners and enthusiasts alike. Accelerate your processor to unleash your phone's true multitasking potential, or dial your CPU's speed down to save battery.
SetCPU also includes a "voltage control" menu, available to certain devices with custom kernels that support it, to control undervolting to save even more battery. Keep in mind that undervolting is only available for certain kernels.
Recent Changes:
Additional permission: Read logs is used for efficient app condition checking. That is currently all it's used for.
3.0.0:
Profiles tab
- Completely rewrote profiles.
- Older profiles will automatically be converted into new profiles.
- Added app and day of week in addition to the older conditions, and more are coming.
- Profiles now support combining conditions under logical trees, with nestable "and," "or," and "not" operators available. It is now possible to easily build complex profiles that take the place of multiple profiles in the older version.
- Actions can now be selected individually.
- Profiles can now be marked as "non-exclusive," which means they will not block profiles with lower priorities from evaluating. In this case, the profiles with lower priorities will perform only actions which have not been performed by profiles with higher priorities. SetCPU will keep evaluating profiles until it reaches an "exclusive" profile that evaluates as true.
- All number selectors in profiles are now in the style of the frequency selector in the main tab.
- The new file extension for exported profile settings is ".setcpu.json."
- To prevent ambiguous situations, it's no longer possible to select priorities that have been used by other profiles.
- The CPU temperature sensor on OMAP4 and some other devices should now be supported for profiles. The option will appear if available.
- Notifications are now set as an action per profile and can now be non-persistent.
- SetCPU will still use the main screen as a "default profile" to set if no other profiles are active. It is now possible to specify an alternate default profile by creating an exclusive profile with no conditions at priority 0.
- SetCPU now asks for a file name before backing up profiles to storage.
- It is now possible to share profiles without having the internal/external storage mounted.
Main tab
- IO scheduler selection has been added via a drop down menu in the main tab.
Bugfixes
- Fixed a bug where the short benchmark always reported 0 ms.
- Fixed the labels in the pie graph in system info.
- Fixed some common crashes.
Permissions:
Root: SetCPU needs root permissions to modify the CPU speed and other settings.
Start at boot: SetCPU will start a profiles service at boot, if enabled. It also sets default boot settings, if enabled. SetCPU does not run in the background if profiles are not enabled, and becomes inactive after settings, if any, are applied.
Wake lock: This prevents the phone from sleeping while stress testing and benchmarking.
Write external storage: SetCPU needs to read from and write to the SD card or internal storage to back up profiles.
Read phone state: The "in call" condition needs this to determine if the user is making a phone call or not, and trigger the profile if the user wants to.
BUTTON SAVIOR (Root)
Description
Requires root for full function. Some keys can still work without root.
Top 1 Software key App on Android Market
Top 10 Must have app for root devices
Top 1 Must have app on HTC HD2
Top 1 Software key app with best customization features
Works from 1.5 to 4.0(ICS)
If you are afraid of breaking your hardware keys or you have broken keys or you simply just don't have any key on your device, get Button Savior to make your life easier.
This app will display a floating software key panel which can be summoned everywhere anytime. Button Savior 1.1.6 or later now suppports E-INK display with specially made themes provided by XDA member Berlinski.
For non root user: You can still use power off, Home, Camera, Call , and volume keys.
[Features]
☆ Simulates 'Home' 'Back' 'Search' 'Back' 'Recent Task' 'Screen Off' 'Volume'
☆ Can set to always open or auto hide based on user customizable timer
☆ Two types of trigger action to choose from (Gesture trigger and Click trigger)
☆ Added Camera key and Call key simulation
☆ Customizable trigger position
☆ Also provides themese to support e-ink display
☆ Can change it to one click mode for super fast button action in option
☆ Can create shortcut action such as call someone or go to bookmark on Call or Camera keys. (With PRO)
[Not Root?]
☆ Home key is supported
☆ Power key is supported
☆ Volume key is supported
☆ Camera key is supported
☆ Call key is supported
IF YOU HAVE PROBLEM GRANTING ROOT FOR THIS APP
If your device is rooted and still cannot use keys except home, please update su binary and superuser apk.
IF YOU ARE UNABLE TO UNINSTALL
You need to disable screen off feature first. To disable, go to setting/location secuirty/device admin to remove Button Savior from the list.
Theme contribution list:
(1) Default (XDA member stefen)
(2) Froyo (XDA member hlvl)
(3) Sense UI (XDA member internauta2000)
(4) Honeycomb (XDA member securecrt)
(5) Pen's Ginger (XDA member Pens and DreamS)
(6) Pen's Honeycomb (XDA member Pens and DreamS)
(7) Pen's Sense UI (XDA member Pens and DreamS)
(8) Contrast for E-INK (XDA member OMGWTF_BBQ aka BerlinSki)
(9) Metro for E-INK (XDA member OMGWTF_BBQ aka BerlinSki)
(10) Subtle for E-INK (XDA member OMGWTF_BBQ aka BerlinSki)
(11) K3 ICS (XDA member kam333)
(12) K3 Honeycomb (XDA member kam333)
[This app requires following permission because]
☆ GET TASK: Need to display recent app
☆ VIBRATE: For hepatic feedback
☆ INTERNET: For ads and for shortcut with internet action
☆ ACCESS NETWORK: For ads
☆ MAKE CALL: For direct dial shortcut
[root] CHAINFIRE3D
Description
Chainfire3D - Take control of your GPU (OpenGL) !
Take control over your GPU!
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
!! For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/Ice Cream Sandwich/Jelly Bean !!
!! Chainfire3D is for 1ghz+ devices only !!
!! ROOT is required for this program, as well as a writable /system partition. S-OFF is also required on HTC devices !!
Features include reducing texture size and quality to reduce memory use and potentially increase game performance, as well as increasing memory use potentially increase performance.
If you also install the (experimental) EGL driver, AND your GPU supports it, AND you have the Pro version, you can enable 4xMSAA or 16xMSAA on a per-app bases. This can drastically improve image quality!
Be sure to check the thread on XDA for available plugins !
( http://forum.xda-developers.com/showthread.php?t=1087427 )
Chainfire3D has been tested on:
- HTC HD2
- Samsung Galaxy S
- Samsung Galaxy Tab 7"
- Samsung Galaxy S II
- Samsung Galaxy Note
- Samsung Epic 4G
- Motorola Atrix 4G
- Motorola Droid 2
- LG Optimus 2X
- Google Nexus S
Many users are running Chainfire3D on devices not listed here - it's likely to work on all modern devices. So far nobody has reported a failed install, so that's good. Doesn't mean problems can't happen.
!! There is some risk involved installing the driver. Your device may not boot. If you have CWM, it would be prudent to create a backup before installing !!
SUPER SU
Description
SuperSU is the Superuser access management tool of the future
!!! SuperSU requires a rooted device !!!
SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root. SuperSU has been built from the ground up to counter a number of problems with other Superuser access management tools.
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
The discussion and support thread can be found on XDA-Developers here:
http://forum.xda-developers.com/showthread.php?t=1538053
SUPERUSER
This is meant to replace Superuser (if installed), you use either one or the other. You cannot combine them. Statements that this breaks Superuser are therefore completely nonsensical.
NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.
Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU.
TRANSLATIONS
Want to help translate SuperSU ? See http://www.getlocalization.com/supersu/ !
UNDELETE FOR ROOT USERS
Description
Undelete for Android is an application for root users that allows you to recover any type of deleted file from your SD card or internal storage.
With support for over 1000 file types, Undelete can come in handy if you accidentally delete photos or want some old tunes to listen to on the go.
Undelete can also securely wipe and shred files so that they will be impossible for others to recover.
Features:
★ Restore any file that has not been written over
★ Securely wipe/shred files
★ Works with documents, images, video, music, archives and binaries
★ Thumbnail preview generation
★ Batch operations
★ Custom restore folder
★ Preview media files
Without the unlock Key, this application will only restore image files. Please buy the Key to unlock full functionality.
Currently, only FAT is supported. On most devices this means that only the external SD is supported.
Some files that are discovered after a scan may fail to recover as the data can be corrupted beyond repair, just like desktop based solutions.
ROOT PERMISSIONS require that you modify the operating system on your device, visit our website for more information: http://fahrbot.co.uk/root
INTERNET and READ DATA permissions are needed for the logging system. Logs are only sent manually with your permission through the "Write to us" dialog.
BUSYBOX
Description
Root required for this application!
The fastest, most trusted, and #1 BusyBox installer and uninstaller!
Over 3 million installs and over 10,000 5 Star ratings!
Mentioned in the new XDA-Developers book "XDA Developers' Android Hacker's Toolkit: The Complete Guide to Rooting, ROMs and Theming"
Winner of best Utility Software award for Android via Handster.
This is the only installer that is ad free and requires no internet permission!
This installer has the smallest Busybox binaries available, right around 800kb unlike the other installers which are over a meg.
The source for this application can be found here: https://code.google.com/p/busybox-android/
Featured on the BusyBox website at: http://busybox.net/products.html
The BusyBox source code can be found here: http://git.busybox.net/busybox/
A must have for any rooted phone! Almost EVERY rooted applications needs BusyBox to perform their magic, if you have a rooted phone then you need BusyBox.
Pro version contains Backup feature (for safer installs), uninstall feature, Advance Smart install feature, the ability to hand pick the applets you want, safety check for missing applets on start, and better overall support. The pro version will receive more frequent updates than the free version will.
Please note I did not write BusyBox! I wrote this installer and cross compiled BusyBox for Android. Please see the about menu option for more details or here: www.BusyBox.net
BusyBox is a software application that provides many standard Unix tools, much like the larger (but more capable) GNU Core Utilities. BusyBox is designed to be a small executable for use with the Linux kernel, which makes it ideal for use with embedded devices. It has been self-dubbed "The Swiss Army Knife of Embedded Linux".
Leave this installed if you always want to get the latest version of busybox!
AnTuTu CPU MASTER (Free)
Description
CPU Master is AnTuTu Free App!
Note: Root is necessary
AnTuTu CPU Master is a tool for changing the CPU/GPU speed on a rooted Android Mobile Phone/Pad.
CPU Master Automatic detection CPU's available frequencys, don't need to manually choose.
CPU Master's OverclockWidget show the CPU and battery stats, and change the CPU speed faster and simple.
Easy to find the following brands HTC,Motorola,Samsung,Google,LG ROOT, CPU Master can set cpu High-low frequency on your rooted mobile, capable of overclock and underclock.
CPU Master feature:
+ Speed up your processor
+ Powersave battery (speed down)
BATTERY CALIBRATION
Description
Calibrate your battery when you think it's miscalibrated.
Requirements: Android 2.1+ | Root permissions
Calibration needs to be done after flashing a new ROM, but you can calibrate any time you think your battery is miscalibrated. This program does it by removing the batterystats.bin system file. The OS generates a new clean batterystats file soon, thus any fake information from the previous ROM is removed.
It's suggested, but not necessary, to let the phone fully discharge after calibration, then charged to 100% without break.
The app shows your actual battery status, and only allows you to start the calibration (i.e. removes the file) when it's fully charged, unless you force earlier calibration.
The voltage meter can be useful too. Full charge is around 4200mV.
There is an option to beep when 100% is reached so you don't have to closley follow the changes.

GL to SD(root)
Description
Root Required.
Get Gameloft games to external SD and work fine.
So you can easily move the game data files to external SD card and solve the problems that internal SD space is too small or slow.It also applies to other games data to external SD, such as gun bros, Dungeon Defenders.
Users can customize the mounted folder in the configuration interface.Must wait for data loading is complete, and set the folder with the corresponding app.It can be used in exceptional folder or navigation, etc.
How to use and please Note:
Only root required.
1.For new user,using "move data" function move your game data to external SD.
(Android/data folder is moved to "data" ,gameloft/games folder is moved to "games",and Android/obb is moved to "obb" folder in the SD card)
2.Run this program.It lists all gameloft games and click 'open' to play.
3.If you wanted see other games (not gameloft)
,press Menu->Click "Setting"->Check "/sdcard/Android"->back to list.
4.If you want to click the desktop icon to execute,You will mount and press Menu -> Exit
5.If you do not know how to move files, delete the /sdcard/gameloft/games data, open wifi, run the program and click game,leave it to download.
6.Press and hold can remove non-game item.
7.If you flashed new rom or updated and "GL to SD" didn't work,please clean the data of "GL to SD".
**Limited to the core of each phone set different, each phone have encountered can not guarantee normal operation.
If not executed, please return your phone's models and ROM versions, have the opportunity to add in the new version.
**When you want to connect to the computer as a USB hard drive, remember to unmount(or check auto unmount).
**There are still some games left running in the background, will mount unsuccessful. Please using other app to kill this game process and re-mount again.
**If you had any question about this app.Email to me.
Suit for:LG P990,P920,Samsung Galaxy Note,Galaxy S2,Galaxy R,i9000,i9003,yp-g1,Galaxy W,YP-G70,Samsung Galaxy Tab(P1000),Acer Iconia A100,Moto Atrix 4G ME860,Photon 4G,razr,Asus Transfomer,Ainol Novo 7
Use but no report:Captivate,SEMC Xperia X10,Table S,Samsung Galaxy Tab,Infuse 4G,Acer Picasso,Moto Droid X2,LG GT540 Optimus,Toshiba Folio 100,Scroll Tablet
(If you have any questions, email me rather than to the star.)
Sixaxis Controller
Description
*** Caution: This app is not for the faint-hearted!! ***
Please read all instructions carefully.
Not all devices are supported, therefore it is strongly recommended that you try the 'Sixaxis Compatibility Checker' (available for free in the Android Market) before purchasing this app.
Finally the wait is over... The ultimate gaming experience awaits! Now you can play games on your phone the way they were meant to be played! Sixaxis Controller allows you to use your Sixaxis and DualShock 3 controllers in many of your favourite games and applications.
*** IMPORTANT ***
- ROOT access is required!!!
- Due to the way pairing is done with the controllers, you need to manually pair your controller with the PC utility 'SixaxisPairTool' (available on the website) and a mini-USB cable. Android 3.1+ users can also pair directly on their devices via USB.
- It is highly recommended that you use an ORIGINAL controller. Many after market controllers will not work with this app. If you get a 'Client connected: 1' message, but the lights on your controller continue to flash, it is almost certainly not an original Sony controller.
- Be sure to read the instructions in the help menu carefully.
Features:
- Up to four Sixaxis and DualShock 3 controllers supported at once.
- Support as a native gamepad in Android 3.1+ devices. Full support for analog sticks and analog triggers.
- Keyboard emulation. Map all buttons and sticks to almost any key available in Android.
- Mouse emulation. Configure a button to activate the mouse pointer on devices that support mice (most tablets, and many phones should work).
- Touch emulation allows you to map buttons and analog sticks to the screen. Play all your favourite games with full analog support, even those without built-in controller support!
This product is not affiliated with, nor authorized, endorsed or licensed in any way by Sony Corporation, its affiliates or subsidiaries. All trademarks are property of their respective holders.
For assistance, full instructions and FAQ, visit our website at http://www.dancingpixelstudios.com
AdFree Android
Description
THIS APP IS FOR ROOTED PHONES ONLY!
AdFree removes most ads in the browser and other apps. It does this by nullifying requests to known host names in the system hosts file.
If you have problems with this app, or you know of additional host names not being filtered, please comment in xda-developers.com forum so it can be fixed!
SD-Booster
Description
SD-Booster speeds up your external and internal SD-Card(s) (external and internal memory) up to 40 times! Enjoy a new feeling of speed on your Android smartphone anytime and everywhere you are.
Starting apps, listing to your favorite music or just swapping data with your PC ? Whatever you do, the SD-Booster improve your phone speed!
SD-Booster needs root permission to run, otherwise SD-Booster can't do anything!
Features:
-MMC detection framework to support any SD-Card
-Speedup every external and internal SD-Card
-Set on Boot
-Color based suggestion terms of current cache size
PLEASE don't move SD-Booster to your SD-Card, otherwise SD-Booster doesn't work on boot!
Script Manager - SManager
Description
Powerful application to execute scripts and executables, root explorer and browser and multi terminal emulator.
Execution Functions:
------------------
Manage and execute shell scripts and programs in file system.
All executions run over vt100 terminal accepting user input and esc codes (colors, bel, cursor movement ..)
Run them at boot-up and on network status change possibility.
Schedule at selected time. (cron jobs)
Show graphical dialogs from running process.
Create widgets at desktop.
Edit and create scripts, also create them from url.
Insert code in your scripts using QR codes.
Share execution output.
Bookmark your scripts.
Test SM_VERSION and/or SM_VERSIONCODE to know if is running inside SManager.
With root privileges you can also execute them with superuser privileges.
File explorer Functions:
------------------------
Browse all phone's file and network files.
Open multiple directories with one screen.(3 directories for Ads version)
Open and edit all files associated to an application.
Click to execute scripts, and long tap to edit, move,copy and rename files and directories. Also Create links and show files properties
Multiselect function from different directories. (Ads version only support 7 selections from different directories. No limit if selections are in the same directory)
With root privileges you can also:
Root explorer
Modify RO (Read Only) partitions easily.
Root editor (Allow edit files with root privileges also usable by other applications. Configure "Browse as root" to use it with script manager or other application)
Open and edit ALL files regardless the permissions they have with selected application. Use CAREFULLY(Configure "Browse as root" in order to get this feature)
Console screen:
---------------
Volume Up: Mapped to Esc key.
Volume Down: Mapped to Enter key.
DPad press: Mapped to Control key. (Press and then press other key. Not simultaneous pressing required)
Enable "extra gestures" in config screen in order to send Home/End,del/tab,left/right,pgup/pgdown keys. This is very useful to execute shell and ssh connections.
WEIRD CHARACTERS: If you get a lot of [[^ characters, is due you have "extra gestures" enabled and script/program doesn't process them. Use most right side of screen to send standard scroll event, or disable "extra gestures"
External Storage SD Notes:
-------------------------
You can install SManager on external Storage SDcard, but you must be know:
- If you are using boot scripts or scheduled script, you will need SMExternalSD app.
- All events like network status change and scheduled scripts while external storage is shared or unmounted will not be processed. Although you have SMExternalSD installed
NOTE:
SManager does not launch executions until external storage is mounted.
NOTE2:
Detected some programs/daemons (like dropbear) fails if has stdin closed. Try put "exec 0>&1" to reopen stdin in background executions.
No ads version features:
------------------------
No ads.
Execute scripts from widgets without opening console.
No limits in multiselect.
No limits opening multiple directories.
Alias keys in SMConsole.
Hide/show SMConsole status bar with up/down gesture at top of SMConsole screen.
FasterFix
Description
Speed up your gps, and get faster GPS-Fixes using FasterFix.
- Root access required -
- BusyBox Required -
- New HTC phones need NAND-unlock -
This app enhances your GPS by using a more accurate time estimation from a NTP server near you. Select one from the list, or add your own.
If the app doesn't work, please use "root checker" to check if you are correctly rooted and busybox is installed before you give a bad rating.

reserved 2

reserved 3 now u can post

nice thread

updated nov 03 with script manager and faster fix

[SCRIPT][1.6+][WHATSAPP][14/11/08] Disable sending read-receipts for WhatsApp msgs

Shell script to disable read receipts for all your incoming Whatsapp messages
Even "better": Others won't see whether you've already read their message(s) or not. However, you will still be able to see the read receipts of others!
Code:
################################################################################
#
# Shell script to disable read receipts for all incoming Whatsapp messages.
#
# [ ANDROID AND ROOT ONLY ! ]
#
# Author: Stephan Schmitz <[email protected]>
# Source: https://gist.github.com/eyecatchup/9af90363732801b131bf
# Last Updated: 09. Nov 2014
#
# ABOUT
#
# You don't like that everyone in your Whatsapp contact list is now able to see
# whether you've already read their latest message(s) or not? Then feel free to
# use the following "work-around" that I found to disable sending read receipts
# globally. Once patched, whenever you get new messages, the senders will never
# see the 2 check marks in blue. They'll just stay gray, just like it was until
# recently. Well, almost. Because you'll still be able to see whether your chat
# partners have already read the messages you sent to them. ;)
#
# DESCRIPTION
#
# In early Nov. 2014, Whatsapp added a new "feature" - read receipts. It means,
# your chat partners will get a visual feedback (2 blue check marks) as soon as
# you've read their message(s).
#
# Unfortunately, Whatsapp's dev team forgot to implement a corresponding privacy
# setting for users to be able to turn off this feature. However, fortunately, I
# found it was fairly simple to disable the feature, since it is set in a public
# XML file in Whatsapp's app data directory.
#
# This script shall serve as a convenient wrapper for those Android users who do
# not live in userland - as well as for the lazy ones.
#
# PRE-REQUIREMENT
#
# Basically, all it needs is a working `sed` commandline utily in path.
# If you should not have "Busybox" installed yet, choose one of the available
# "Busybox" installer apps from Google Play Store and let it install busybox.
#
# USAGE
#
# - Save this script to your phone's sdcard as disable_whatsapp_read_receipts.sh
# - Open a terminal session on your device
# E.g. https://play.google.com/store/apps/details?id=jackpal.androidterm
# - In the console, login as root (type su, hit enter) and type:
# sh /sdcard/disable_whatsapp_read_receipts.sh
# (adjust the path, if required, to fit your's!)
# - Hit the enter button. Done. (Whatsapp will restart afterwards)
#
# If you get any error message a) make sure the /data partition is mounted /w rw
# permissions and b), if the permission for restarting WA is denied, 1st try to
# uncomment the last line of this script (append hash char "#" (without quotes))
# and run the again. Otherwise, consult me for help here:
# http://forum.xda-developers.com/android/development/script-disable-whatsapp-read-receipts-t2933467
#
# IMPORTANT NOTE
#
# The last successful test for this was run at 09. Nov. 2014 and on the Whatsapp
# Android version 2.11.399 and 2.11.432 only. Even though it should work for all
# Android versions, it was not tested. Also, Whatsapp might change their current
# implementation any time soon. So this work-around might stop working any time
# soon too. Keep that in mind!
#
################################################################################
Download
NOTE: This script requires the "sed" command line utily (ie "busybox") installed on the system, which pre-requires a rooted device!
NOTE: The gist requires an update, which I'll post tomorrow. For further details and a manual workaround see my post here: http://forum.xda-developers.com/showpost.php?p=56640205&postcount=9
External link to gist.github.com (see the inline comments for further instructions): http://goo.gl/EiOvO0
Download, run, done. Enjoy. Whatever.
PS: For those who understand German, here're some screenshots of testing this " hack". As you can see, my chat partners can't see the read status. http://imgur.com/a/kzQs3

Nice trick!
However, I've noticed that the preferences .XML files are reset to the original values once the application relaunches. So, basically, the changes do not stick.
Any workaround on this?

smartxdev said:
Nice trick!
However, I've noticed that the preferences .XML files are reset to the original values once the application relaunches. So, basically, the changes do not stick.
Any workaround on this?
Click to expand...
Click to collapse
That's kind of odd, since the script explictly restarts the Whatsapp package *after* applying the changes to the prefs xml. Which then, in turn, should result in no result at all (assuming a restart rewrites the xml), right!? But it does work. Now, the first question would be how you define restart (activity (re)launch, package force && start)?
Update: Just checked it and you're right. If I use the -S option on the am start call (to force stop Whatsapp before (re)starting the activity), running script has no effect at all - since the XML is being recreated. And that also means, that the change will gets lost with every device reboot.
The easiest solution I see here, to have a "permanent" effect, to wrap the script in a plain simple app and attach it an onboot service. (Also, looking at #4, some further checks should be added.) If Whatsapp will leave this current implementation of defining whether to send read receipts or not, I'll invest the time into an app version, I think. (Just don't want to have too much hustle with it. So want to wait whether it's worth to spend more time on this.) Thoughts?

hi, i have this problem:
{
"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"
}
can you fix it?

Dj Mauro said:
hi, i have this problem:
can you fix it?
Click to expand...
Click to collapse
I had permission error too.
In the terminal, try to first run "su" command (without the quotation marks), it will obtain root permissions for the terminal.
Then run the actual command. That solved the permission error for me.
Bexton said:
That's kind of odd, since the script explictly restarts the Whatsapp package *after* applying the changes to the prefs xml. Which then, in turn, should result in no result at all (assuming a restart rewrites the xml), right!? But it does work. Now, the first question would be how you define restart (activity (re)launch, package force && start)?
Click to expand...
Click to collapse
Actually it never worked for me (I mean, script ran successfully, but i have no success in disabling the "read recipient" when i tested it).
Then, I tried to do it manually:
- make a backup copy of the target file (/data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml)
- and then set: "read_receipts" to value="0" in the original file
- save it
- and when i open whatsapp app again, the XML file is restored to the older values, and the "backup" copy gets erased.
And for the "restart" question, i tried the following:
1 - swipe the app away from the recents, make XML modifications, and relaunch
2 - kill the app, make XML modifications, and run it again
I also tried to set XML file permissions to read-only, but it still was replaced by original config. once i opened the app.
-----
I was thinking about another workaround:
Since the read receipt (and delivery too) is usually done by transmitting a small message by the application, back to the sender, once the conversation window is opened.
It may be possible to just block this outgoing communication on your side by XPrivacy.
But, i have yet to hunt down the specific permission/address to block, without crippling the app..

Dj Mauro said:
hi, i have this problem:
snip
can you fix it?
Click to expand...
Click to collapse
As a quick fix, this should work for you:
1.) Add the following line above the line with the sed command:
Code:
mount -o rw,remount /data
2.) Change the last line of the script to the following (if it still compains replace the user id value in the command with that from the error message. and if it still complains, it might even work when you just comment out the line):
Code:
echo `am start --user -2 -n com.whatsapp/com.whatsapp.Conversation`
3.) Back in the console again, login as root (su, enter) and run the script.
Let me know if it worked.
As said in my update to post #3, I'll probably add some automatisms for such issues soon.

Bexton Tnx !

how about an xposed module?

smartxdev said:
I had permission error too.
In the terminal, try to first run "su" command (without the quotation marks), it will obtain root permissions for the terminal.
Then run the actual command. That solved the permission error for me.
Click to expand...
Click to collapse
Yeah, recognized already that I completely forgot to mention that at all (to run the script as root). I updated the inline instructions accordingly.
smartxdev said:
Actually it never worked for me (I mean, script ran successfully, but i have no success in disabling the "read recipient" when i tested it).
Then, I tried to do it manually:
- make a backup copy of the target file (/data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml)
- and then set: "read_receipts" to value="0" in the original file
- save it
- and when i open whatsapp app again, the XML file is restored to the older values, and the "backup" copy gets erased.
And for the "restart" question, i tried the following:
1 - swipe the app away from the recents, make XML modifications, and relaunch
2 - kill the app, make XML modifications, and run it again
I also tried to set XML file permissions to read-only, but it still was replaced by original config. once i opened the app.
Click to expand...
Click to collapse
Sheesh. Okay, I think I got what's wrong here.
As far as I understood, you didn't even got to the point where the file
Code:
/data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml
stored the modified value, correct?
When I was looking at your manual procedure I recognized a small but probably crucial difference! Let's have a look at it. My initial, manual approach was:
# Login as root
Code:
[email protected]> [B]adb shell[/B]
[email protected]:/ $ [B]su[/B]
# Copy the original prefs xml file to /sdcard/.
# NOTE: We use cp as root user, but with the --preserve switch to copy a file owned by Whatapp's OS user.
Code:
[email protected]:/ # [B]cp -p /data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml /sdcard/[/B]
# So, at this point, the copied file /sdcard/com.whatsapp_preferences.xml is still owned by Whatapp's OS user.
# Now, my last 2 steps were to modify the read-receipts settings value in /sdcard/com.whatsapp_preferences.xml and copy back the modified file to its original location, which I did as follows:
Code:
[email protected]:/ # [B]sed -i'.bak' 's/^.*\bread_receipts\b.*$/ <long name="read_receipts" value="0" \/>/g' /sdcard/com.whatsapp_preferences.xml[/B]
[email protected]:/ # [B]cp -p /sdcard/com.whatsapp_preferences.xml /data/data/com.whatsapp/shared_prefs/[/B]
So all together, this was:
Code:
[email protected]> [B]adb shell[/B]
[email protected]:/ $ [B]su[/B]
[email protected]:/ # [B]cp -p /data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml /sdcard/[/B]
[email protected]:/ # [B]sed -i'.bak' 's/^.*\bread_receipts\b.*$/ <long name="read_receipts" value="0" \/>/g' /sdcard/com.whatsapp_preferences.xml[/B]
[email protected]:/ # [B]cp -fp /sdcard/com.whatsapp_preferences.xml /data/data/com.whatsapp/shared_prefs/[/B]
So what happened with the last 2 commands that made it work for me, but breaks in the script version?
The core problem here is, as I just learned, that GNU sed's -i extension does not actually edit files in place (--in-place is a misnomer, in my opinion); it creates a temp file, deletes the original file, then renames the temp to the name of the original. The result is a new file - much possibly with a different owner.
So in my manual procedure, the result of the sed command worked fine except for the fact that it changed ownership on all the files it went through. The only problem is that these files (or at least the backup file) were owned by the root user - the user I run the command as. However, then I used the -f switch (to force overwrite) and the -p switch (to preserve permission, ownership and timestamps) to copy back the prefs file from /sdcard/ back to its original location in the Whatsapp data folder. That means, as a result, in the Whatsapp data folder there was a) no new file from another user (the backup file) and b) the modified prefs xml file still had its original ownership information. Basically, this kind of "fixed" sed's -i mode behaviour on the prefs file plus didn't created a new file in Whatsapp's data folder.
The last step to solve the puzzle is fairly simple. I just tried the procedure manually - as defined upthread - with all my friends' phones. Thus, I didn't noticed the sed behaviour. Plus, the friend Iinitially wrote the script for didn't told me that it wasn't working for him.
Anyway. Let's finally come to how to fix.
A quick look into the sed manual unveils that -c switch should do the trick:
Code:
-c, --copy
use copy instead of rename when shuffling files in -i mode
(avoids change of input file ownership)
Unfortunately, this switch is not enabled in all the busybox sed's for Android. Also, this would still leave us with a new file in Whatsapp's data directory. Even if all ownership information of existing files can be preserved, we should also not create any files in the folder that are not known to the Whatsapp app.
So basically my manual approach is the way to go:
a) Save the backup of the original prefs file somewhere on /sdcard/
b) Preserve ownership and permissions for /data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml
NOTE: Even if you got the value in the prefs xml saved to "0" and with no changes to ownership and permissions, you still need to restart any running Whatsapp process. Otherwise the change will have no effect! And, rebooting the device, resets the prefs xml file!
I'll post an updated version later. Until then, probably the easiest way to test this, is the manual way using a text editor app on your device.
- Open any text editor app with root capabilities (I used https://play.google.com/store/apps/details?id=com.maskyn.fileeditor )
- From the menu choose "Open file", navigate to /data/data/com.whatsapp/shared_prefs/ and open the file com.whatsapp_preferences.xml
- Find the line that reads <long name="read_receipts" value="SOMENUMBER" /> (SOMENUMBER is a placeholder, of course)
- Replace SOMENUMBER with 0 (zero), so the line reads <long name="read_receipts" value="0" />
- Save the file
- Now, close Whatsapp from the recent apps view and restart it.
- You can verify the change by running the following command (as root) from a terminal on your phone:
Code:
cat /data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml |grep read
- You can verify the ownership and permissions by running the following command (as root) from a terminal on your phone:
Code:
ls -l /data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml
smartxdev said:
I was thinking about another workaround:
Since the read receipt (and delivery too) is usually done by transmitting a small message by the application, back to the sender, once the conversation window is opened.
It may be possible to just block this outgoing communication on your side by XPrivacy.
But, i have yet to hunt down the specific permission/address to block, without crippling the app..
Click to expand...
Click to collapse
Sure, feel free to share any suggestions!

Ather said:
how about an xposed module?
Click to expand...
Click to collapse
I guess that'd be possible too. Just that I never looked into it yet.

Thanks, @Bexton for your detailed explanation.
Manual editing by Turbo Editor did the work for me.
I tested it, and the blue check marks were indeed blocked.
And btw, Turbo Editor has a nice "recent files" list on the startup, so reediting of the parameter on restart should be simple and easy.
Then, i did Restart (full restart to the device), and.... ...it still holds!
The parameter in the XML is unchanged and read notifications are still blocked
So, it made me wonder, why it didn't work for me before? I used ES Text Editor to edit the XML, it was fine, but then i made a backup copy somewhere inside the /data/data/com.whatsapp/ folder. And I think that "foreign" file caused full rewrite of the xml files by the app.
I hope it may hold permanently, but, we'll see..

Ahoy everyone!
We're 2 students from the University of Milan who created a repository [https://github.com/phosphore/whatsapp-blue/wiki]
for an Android app with the aim of getting rid of those blue ticks. We're currently
considering and testing out all the possible solutions including the modification
of com.whatsapp_preferences.xml (as found by @Bexton) or the filtering of the TCP
packet responsible for the read receipt.
Although using Bexton's method greatly simplifies the solution, it is just a
temporary workaround before Whatsapp fixes it.
Having a proxy filtering the requests should be a permanent solution. We are
reverse engineering FunXMPP (WA proprietary protocol) to find that particular request.
We're open to contribution!

smartxdev said:
So, it made me wonder, why it didn't work for me before? I used ES Text Editor to edit the XML, it was fine, but then i made a backup copy somewhere inside the /data/data/com.whatsapp/ folder. And I think that "foreign" file caused full rewrite of the xml files by the app.
I hope it may hold permanently, but, we'll see..
Click to expand...
Click to collapse
Some editors use a similar internal workflow as GNU's sed in -i mode and without the c switch. Resulting in "corrupted" files (in the sense of ownership & contex)..
Th3Zer0 said:
Ahoy everyone!
We're 2 students from the University of Milan who created a repository [https://github.com/phosphore/whatsapp-blue/wiki]
for an Android app with the aim of getting rid of those blue ticks. We're currently
considering and testing out all the possible solutions including the modification
of com.whatsapp_preferences.xml (as found by @Bexton) or the filtering of the TCP
packet responsible for the read receipt.
Although using Bexton's method greatly simplifies the solution, it is just a
temporary workaround before Whatsapp fixes it.
Having a proxy filtering the requests should be a permanent solution. We are
reverse engineering FunXMPP (WA proprietary protocol) to find that particular request.
We're open to contribution!
Click to expand...
Click to collapse
Could you hook up via email? I'm working on an app as well and currently considering the possibilities. Maybe it's worth sharing thought.. Please send to [email protected], thanks!

This is why I waited before investing more time into it, hehe. So, time to relax for everyone. Here is news:
Whatsapp will soon get the ability to turn off the blue checkmark read indicator, according to an alleged Beta tester of the application.
Click to expand...
Click to collapse
Original tweet: https://twitter.com/0xmaciln/status/530294585072025600
Via: http://www.myce.com/news/whatsapp-w...ble-privacy-sensitive-blue-check-marks-73438/
Looks like this thread will be obsolete very soon.

Bexton said:
Whatsapp will soon get the ability to turn off the blue checkmark read indicator, according to an alleged Beta tester of the application.
Original tweet: https://twitter.com/0xmaciln/status/530294585072025600
Via: http://www.myce.com/news/whatsapp-wi...k-marks-73438/
Looks like this thread will be obsolete very soon.
Click to expand...
Click to collapse
Nice!
I think whatsapp(facebook?) expected this to come, they already had some bad experience with the "last seen" issue some time ago.
And it is already implemented as a simple switch inside XML prefs...

Bexton said:
Looks like this thread will be obsolete very soon.
Click to expand...
Click to collapse
Hm, maybe I was wrong and it will not become obsolete. Maybe I will still build an app for it. Why? I found more news on the matter, that pointed out a major difference to me.
The same person who confirmed the additon of the on/off toggle for the read receipts, Ihlan Pektas, actually blogged about the feature already a few days ago. The essential information given in his blog post here (in German language) for me is, that he says that early alpha builds already have an implementation for it, and when you disable sending your read status (so that others can't see if you've read a msg), you will, in return, NOT be able to see the read status of your chat partners! (What makes perfectly sense, becausee it's the same way they do it for the "last seen" status.)
That being said, I think there'll be interest in an alternative. An alternative that is capable of disable sending one's own read status, while still being able to see the read status for one's own msgs, sent to others?!
Well, we'll see. (But the party ain't over yet.. )

Thanks Bexton. Tried your manual method with ES File Explorer, without making a backup, and it works. Even survives a full reboot.

Bexton said:
That being said, I think there'll be interest in an alternative. An alternative that is capable of disable sending one's own read status, while still being able to see the read status for one's own msgs, sent to others?!
Well, we'll see. (But the party ain't over yet.. )
Click to expand...
Click to collapse
I see your point, but to make this happen, we need to look at another approach. Because, now we disable it by the pretty obvious flag in the pref. file, and once they release a "feature" it will be probably the same flag that will cause you not the deliver read receipts either.
The thing is, that in fact I barely use whatsapp, for various reasons. I'm here to help some non-techie friends of mine.
Anyways, I use Open WhisperSystems' TextSecure mostly (less polished and fewer features, but free, opensource, and actually secure).
So, a short while ago, they've introduced "delivery receipts". And for some reason, only I was able to get others' delivery receipts, but when others send me messages, they didn't receive a delivery receipt from me. (That's basically what we are trying to do here, just with read receipts)
At first, I was sure there is some bug in this. But then it turned out that I tuned XPrivacy too tight on restrictions, and this new feature could not get through and send the delivery notice. (unfortunately I don't remember what exactly the troublesome restriction was)
That's why i first thought about XPrivacy for this case as well.
Logically, the mechanism here might be the same, and once we find out what activity or address to block it will do the trick without letting the app itself know about it.
And it seems like @Th3Zer0 guys have the same direction in mind.
Bottom line: sounds like a good idea to find out how to "cheat" those things, and maybe build Xposed module/app on it

This seems to be the equivalent of downgrading whatsapp, letting you see blue ticks but other's cant see
It seems that it disables the part where you can highlight your own message and see who has seen the message though.
Working on 2.11.432.
Whatsapp just enabled a new feature a la Telegram where you can see who's typing in a group.

Contradictory to my previous report, I'm noticing that over time the "read_receipts" parameter keep reverting to a original value. What's weird though is that i was unable to pinpoint when it actually happening, since it happens without any kind of full phone restart in between.
Have you (@Bexton?) any insight on it?
And by the way, as I was talking about the sadly unpopular, but security-wise superior TextSecure, this post came out: Open Whisper Systems partners with WhatsApp.
Sounds promising, but it still remains to be seen how it all gets implemented and how much of a metadata leakage will be going on, since it is very unlikely that a proprietary and closed source SW company as WhatsApp will kill their business value (which is an insight on near 700M users' data) just like that.

[Guide] Multi User Setup for Kitkat 4.4.4 (for noobs)

This tutorial will show you how to setup your device as admin and configure other user profiles (this is important when you're not the owner). Your device maker disabled multiuser functionality in Kitkat, like on my Lenovo Tab 2 A10-70L? - then this for you. At least, that's where this procedure is tested on. Afaik, this should work on Lollipop too. But will it work for your device? - No clue, you tell us!
Basically it's an accumulation of what I've read here (thanks again) and my personal experience as a noob myself.
So far, this guide is incomplete and I'm hoping for some pro tipps to perfect it. Please help me sort out the unclear parts highlighted in red and I'll update this post accordingly. The sooner the better, because this actually is not my device and someday soon I'll have to pass it over to my mom since it's my present to her, I'm only setting this slab up...
Preconditions:
Android treats the first account created as "owner". Only owner will have root privileges if installed accordingly (=admin).
Root permission and a file manager (e.g. ES File Explorer) are required for this fix so go get that first. For the Lenovo Tab 2 A10-70L, I followed this beautiful guide, besides that, I can't help much here.
Unable/uninstall all bloatware (I was adventurous with Titanium Backup with no probs so far, but some crap remained from looking at new user folders; still in search of a vendor/device-specific "save to remove" list)
Install ALL apps you and the other users suppesdly need. This will avoid the need to redownload and reinstall all the apps for each and every user wasting storage. Think thrice, usually it'll be more than desired, but better you do it instead of a DAU... Each user will be able to install apps later though. Full control over user restrictions can be applied for "guest profile" only.
Steps:
In file explorer, go to /system/ and open build.prop
Check if you have anything like the below text (you shouldn't, otherwise edit accordingly) and add these lines at the end of it:
Code:
# Multi Users
fw.max_users=[COLOR="DarkGreen"]X[/COLOR]
fw.show_multiuserui=1
Replace X with your desired digit (up to 7?)
(I've read somewhere that 7 users is maximum that system can handle, but I haven't tried)
Save, reboot and log in as "owner" (your profile)
Go to Settings>Device and say hello to new item "Users"
Create new users and/or a guest profile (important: write down the order in which you created them!)
All new user profiles are now shown as "new user" no matter what you wrote in the profile properties (only guest will be shown as "guest"). Mind you, this also applies for the lockscreen!
In file explorer, go to /data/system/users/ to find your users' folders containing some system files (what exactly?) Now guess what - the order of the numbered folders and #.xml files match the order you created them. "0" is you, the owner.
Open each .xml file and replace "Owner" with "Your Name" and "New user" with "Username"
Put the device to sleep, trigger lockscreen and log in to each user profile and
Pull down shortcut menu from top right and enable autorotate
Go to Settings>Users>Security, check all settings and note each unlock-code
Disable background services like sync, location, etc. that could potentionally drain battery where applicable
Rinse & repeat 8) for all new profiles
Install "Multi-User App Share" and set apps per user. (Or is there a newer app or more hackish approach without the need for xposed or compiling stuff etc.?)
= DONE =
If you want the user icon in status bar, follow http://forum.xda-developers.com/gal...-users-mod-t3017782/post58659868#post58659868 (haven't tried that ).

Well... build.prop fixes are working, at least for me. It's good alternative to multi-user app from Xposed (we don't want to use Xposed too much...).
Still tried with decompiling & compiling framework for fixing icon problem, and... in framework-res there is not status_bar_expanded_header.xml file, se we are in deep ****.
I am working on: LP

Software Development [XPOSED][INTEL][PX5] 4 Xposed modules to tweak your FYT based (Joying) unit

Currently there are 4 Xposed modules available for the FYT based Intel (Joying) Sofia 3GR Intel and (Joying) Rockchip PX5-A53 units.
GPSSpeedFix V1.12 (by lbdroid, not by me) (Changelog in post #3)
[*]XSofiaTweaker V1.26 (Global Xposed repository) DISCONTINUED
XFytTweaker V1.2.0 (Global Xposed repository)
SofiaServerNoKill V1.01 (Global Xposed repository)
SofiaServerCustomKeyMod V1.01 (Global Xposed repository) (Changelog in post #3)
All modules function on the Joying 6.0.1 stock ROMs (when rooted and with Xposed installed) or on the GTX custom ROMs (pre-rooted and pre-installed with Xposed)
Only the first module can *currently* be installed from my apk, as it is not my module. The other 3 my modules are avalaible on http://repo.xposed.info. The Xposed Installer on the unit can be used to install them.
GPSPeedFix: (stable)
This Xposed module is written by lbdroid. (lbdroids repository)
Since the Joying July 2017 ROMs, there is an error in the GPS Speed on the Sofia 3GR units. The GPS HAL in the Joying Sofia 3GR units uses integers instead of floats to calculate the meters/second. This give speed steps of 3.6 km/hr, or actually rounded to 3 or 4 km/hr steps. This Xposed module calculates the right GPS speed and feeds it back to the "system", so that all dependent apps like navigation apps or GPS trackers can use the correct speed. (require full reboot on installation/activation)
XFytTweaker: (Stable).
This is the successor module of the XSofiaServerTweaker, which on its turn was the successor of the SofiaServerCustommod (See Gustdens post).
The reason for the XFytTweaker was that actually any FYT based unit is running the same FYT/SYU software no matter whether it is an Intel Sofia or a Rockchip PX5. So after making the module suitable for Android 8.0.0, I changed the name.
captures the hardware keys from the Joying unit and allows you to reprogram them. This must/can be configured from the Settings (sub)screen.
allows you to switch on/off the nokill.
allows you to unmute channel 4, which is used for Google voice feedback.
can act on the ACC_ON, ACC_OFF and Resume events.
option to prevent the Bluetooth app from staying full screen on top (thanks to @gtxaspec)
option to prevent the CANbus overlays popping up on heat/airco change or door(s) opening
Option to run system calls as root (Know what you do!)
Option to display the CPU temperature in the status bar next to the time
option to disable the yellow MCU errors overlay (in case this happens to you) (thanks to @RoNeReR)
option to disable the overlay display of the volume bar on volume changes (the volume is always numerically displayed in the status bar)(thanks to @IG_Vasilich for pointing me to the right hook)
supports a usb dac where volume control will be rerouted to stock android volume control (thanks to @RoNeReR)
eliminates feedback during the call if you have OK Google anywhere enabled (thanks to @gtxaspec)
Translated into Spanish (tOz-666), German (mitchum67), Russian (gorlexx @ 4pda), Dutch. Help translate in your own language.
Big thanks to @gustden who analyzed which functions to hook (or directly mod in his case). Note that this module is extended with the EQ and Eject key (when applicable).
Below this post are some images attached from the XSofiaTweaker.
Changelog in post #3.
SofiaServerNoKill: (Stable)
This Xposed module skips the SofiaServer "kill all apps" when going to sleep. This should replace the old nokill mod from Gustden.
Note: Some apps prevent the unit from going into deep-sleep by setting a "wakelock". The old SofiaServer simply killed these apps. This module doesn't do that. The MCU detects the apps using the wakelock to keep the CPU awake and the MCU will completely switch off the unit, resulting in a cold-boot upon switching on the contact. That is not the fault of this module. It is the fault of these bad behaving apps.
Big thanks to @gustden who analyzed which functions to hook (or directly mod in his case)
SofiaServerCustomKeyMod: (Stable)
This is a direct "functionality" copy of Gustdens CustomKeymod, but then as an Xposed module.
This Xposed module captures the hardware keys from the Joying unit and allows you to reprogram them. This should replace the custom key mod from Gustden. It mimics the same behavior and therefore also needs a launcher.sh. In contradiction to the mods of Gustden, these Xposed modules do not touch the original SofiaServer binary and are therefore firmware version independent.
Big thanks to @gustden who analyzed which functions to hook (or directly mod in his case) and how to apply them in the launcher.sh script

XFytTweaker HowTo
(previously XSofiaTweaker)
Every button or event (acc_on/off) has a "Call method" and a "String to be used".
Currently there are 3 options to "start something" with the "Call method"
by package name
by intent (package name / intent)
by system call (terminal command(s) or script)
by package name: This is NOT the name of the apk but the internal package name. How do you get this "package name"?
Use the "List all Installed apps" option in the main screen of the settings. It shows the app icon, the app name and the package name. This package name is what you need. You can select it and copy & paste it into the field.
use the "Display my installed apps (with package name)" option from the JET apk from the top-left menu.
Search in play.google.com for the app you want to start. Say you want to start the navigation app "Magic Earth" and you have selected that one in the play store (in a browser, not the android app). In the address bar you will then see "https://play.google.com/store/apps/details?id=com.generalmagic.magicearth". The bold part behind the "id=" is your package name.
by intent: Every app has a "launch" intent to start the app. Some apps can also be started with other intents to immediately start a specific function. Google Search can be started with the launch intent, but you can also start it with the Google Voice search option intent. The Google (Search) package name is "com.google.android.googlequicksearchbox", the specific intent for google voice search is "com.google.android.googlequicksearchbox.VoiceSearchActivity". The combined "String to be used" is therefore "com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity".
Another example is the Joying Bluetooth apk having intents for the dialer (default launch), the call receiver, the bluetooth streaming, the pairing and a few more.
by system call: A system call can be a direct (linux) command or a shell script or a binary (to do something).
= Commands can be a single command as in:
"ls -l > /sdcard/some_file.txt" to capture a directory listing to a file
"input keyevent 3" => Go to the Home screen (of the default launcher)
"am start -a android.intent.action.MAIN -c android.intent.category.HOME" => Go to the Home screen (of the default launcher)
"input keyevent 127" => pause active media player (any media player)
"input key event 126" => (re)start last used media player.
"am start com.syu.radio/com.syu.radio.Launch" => Start the radio app with the default launch intent (or better use "by package name": com.syu.radio; Or use "by intent": com.syu.radio/com.syu.radio.Launch)
As you can see from the 2nd and 3rd example, there are multiple ways to do something.
From the 6th example you can see that you can start an app (the radio) from the command line with "am start <full intent>", or by package name, or by intent directly.
= A system call can also be a number of commands separated by a ";".
Say you want to pause the media player and switch of the leds, when switching of the contact (ACC_OFF event), you can use as "String to use"
Code:
input keyevent 127; echo -n "h" > /sys/fytver/colorled
Upon switching on your car, you might want to continue your media player and switch on your leds to green
Code:
input keyevent 126; echo -n "b" > /sys/fytver/colorled
Note that you need to separate the commands with a ";" (a semi-colon without the quotes). I have currently no idea how long the entire command can be but I assume some system standard like 255, or 1024 or 2048 or 32767 or 65535, but I advise to use a script anyway when it gets that long (see next point)
= A system call can also be a call to a shell script
Say you want to pause the active media player and switch off the leds (like the example above), you can also put these commands (and 2-200? more) in a script like:
Code:
#!/system/bin/sh
input keyevent 127
echo -n "h" > /sys/fytver/colorled
You copy that script to a location where you can give it the execute bit (necessary on linux), which means not the internal or any external sdcard, but for example /data. You need adb, a rooted terminal or a rooted file manager to do that. Give it the execute rights like "chmod 755 my_great_script.sh"
Multi-tap options (preferred method)
The XFytTweaker and previously the XSofiaTweaker (since v1.22) directly supports double-tap and triple-tap options for hardware and steering wheel buttons, thanks to @gtxaspec.
Simply assign a call option and call entry to the double-tap and triple-tap option. The default delay is 300 ms, but this is user configurable via the "tap delay" setting.
Using NoKill and experiencing cold boots
The NoKill module/option in XFytTweaker is NOT the cause of the cold boots! Bad behaving apps keeping the CPU awake by setting a "wake lock", thereby preventing the unit to go into deep-sleep, are the cause. They make the MCU shutdown the unit completely after about 20 minutes.
The original sofiaServer app simply kills everything, so no problem there.
Especially some GPS, tasker and media player apps are bad behaving apps holding a "wake lock".
You can completely, safely use the NoKill option, but you should find those bad behaving apps and get rid of them, or kill them on going into deep-sleep using the ACC_OFF event and start them again using the ACC_ON event.
To kill an app on going into deep-sleep and start it when coming out of deep-sleep, AND to pause any mediaplayer on going into deep sleep, you can for example use the ACC_OFF option with a "system call".
Code:
am force-stop com.waze; input keyevent 127
And in the ACC_ON command to restart waze (in this case) and restart any media player on coming out of deep sleep:
Code:
am start com.waze/.MainActivity; input keyevent 126
Multi-tap options (deprecated method)
The customkeymod from Gustden and my sofiaservercustomkeymod xposed module both use the launcher script that enables multi-tap options.
The XFytTweaker (previously XSofiaTweaker) does support that as well using a script approach by using a "by system call". But it is advised to use above mentioned method.
So lets say we want to capture the src/mode button and assign 3 apps to that by consecutive key-presses, and lets say we call our script "src_mode.sh"
Code:
#!/system/bin/sh
# Goto Home screen
home="input keyevent 3"
# my apps
app_no1="blah"
app_no2="blahblah"
app_no3="blahblahblah"
last=`cat /data/src_mode.cnt`
last=$((last+1))
case $last in
1)
echo $last > /data/src_mode.cnt
(sleep .7 && [ `cat /data/src_mode.cnt` = $last ] && echo 0 > /data/src_mode.cnt && ${app_no1} ) &
;;
2)
echo $last > /data/src_mode.cnt
(sleep .5 && [ `cat /data/src_mode.cnt` = $last ] && echo 0 > /data/src_mode.cnt && ${app_no2} ) &
;;
3)
echo 0 > /data/src_mode.cnt
${app_no3}
;;
*)
echo 0 > /data/src_mode.cnt
$home
;;
esac
;;
Save that script to /data as "src_mode.sh" (for example) and make it executable "chmod 755 src_mod.sh". Make the call method in the XFytTweaker "system call" and the string "/data/src_mod.sh"
Assign full launch intent calls to the ${app_no1} for your apps.
In case of google maps like
Code:
app_no1="am start com.google.android.apps.maps/com.google.android.maps.MapsActivity"
And use something more logical that "app_no1"
- Use an editor that can handle unix line ends/line feeds, so not notepad.
- Some of the "complaints" about the previous mods from gustden was the "delay". This was also caused by the multitap, as the scripts waits 0.7 seconds for the second tap, and 0.3 seconds for the 3rd tap. If you are a "fast tapper", you could reduce this to 0.5 and 0.3 (or 0.2) seconds.
(Will be further expanded)

Changelogs
Changelog GPSSpeedFix:
1.12 Fix int/float bug in GPSSpeedFix (thanks to IG_Vasilich)
1.11
Switch from 5 moving average samples to 3 moving average samples to improve responsiveness on speed changes. (note: 2 samples and 1 sample simply work worse)
Remove appcompat layer library. Size reduction from 1.3MB to 98KB.
1.1 fix bearing error (user jvdv): prevents the "jump all over the place and point into wrong direction" cursor when navigating.
1.0 first version
Changelog XFytTweaker:
(previously XSofiaTweaker)
Version 1.4.0, 18 August 2018
Created a small wiki on the repository. Added link as third option in "Information Screen"
Added option to disable the overlay display of the volume bar on volume changes (the volume is always numerically displayed in the status bar)(thanks to @IG_Vasilich for pointing me to the right hook)
Some more code cleanup
Version 1.3.0, 12 August 2018
Option to display all installed apps with their package name. This makes it easier to assign an app by its package name to a button.
major code clean up of all unused and/or incorrect, rubbish code.
Version 1.2.0, 11 August 2018, First version of follow up XFytTweaker
Functionally unchanged when compared with XSofiaTweaker 1.26
internal renaming
Major rewrite to make it work on Android 8.0.0.
Version 1.26, 19 May 2018. Final and last version of XSofiaTweaker
Improved mute function for USB DAC mode (RoNeReR)
Improved and correct hook for the EQ button (RoNeReR)
Re-enable EQ button in the preferences
Add double-tap and triple-tap also to EQ button
Version 1.24, 11 May 2018
Really fix mode_src button configuration this time
Version 1.23, 08 May 2018
Correct typos in mode_src button settingsFragment
re-enable debugging messages
Version 1.22, 05 May 2018
next/previous/playpause functions work (gtxaspec)
Make double-tap, triple-tap functionality for keys internal instead of via a script (gtxaspec)
Updated German translation (mitchum67)
Version 1.21, 14 April 2018
improved USB DAC functioning (thanks to RoNeReR)
Version 1.20, 7 April 2018
Added Russian translation (thanks to gorlexx @ 4pda)
Version 1.19, 3 April 2018
eliminates feedback during the call if you have OK Google anywhere enabled (gtxaspec)
Version 1.18, 2 April 2018
Now supports a usb dac where volume control will be rerouted to stock android volume control (thanks to RoNeReR)
Create separate (sub) settings screen for CAN bus settings as it might expand (and users without CAN bus can skip it)
Version 1.17, 29 March 2018
option to disable the yellow MCU errors overlay (in case this happens to you) (thanks to RoNeReR)
Version 1.16, 28 March 2018
Option to display the CPU temperature in the status bar next to the time (It reads all 4 cores and displays the highest core temperature)
Dialog box to immediately do a soft reboot for the options that need it (not yet for HOME/MUTE as they are combined options. I have to think about those)
Version 1.15, 25 March 2018
Updated Spanish translation (thanks to tOz-666)
Made separate Settings screen for hardware buttons and for Steering wheel buttons
Added option to execute "system calls" under normal or root access. root access is necessary if you want to kill an app (for example upon ACC_OFF)
Version 1.14, 18 March 2018
Added German translation (thanks to mitchum67)
Version 1.13, 14 March 2018
Added option to prevent Bluetooth phone app from staying "full screen on top" during a call (thanks to gtxaspec)
Options to prevent Canbus overlays from being displayed on changes in heating/airco, door(s) opening (slightly improved to v1.1).
Remove appcompat layer library. Size reduction from 1.4MB to 195KB.
Version 1.11
bugfix: bt_phone button function used wrong key to call action to be executed
functionally identical to 1.1
Version 1.1
Added Spanish translation (tOz666) and Dutch translation.
Added options to disable CANbus overlay on heating/airconditioning change or door opened (untested; no canbus)
Modified BT/phone button hook (gtxaspec)
1.0: First release

Looks like there has been great progress on these units with xposed, custom roms & twrp. I hope to get a chance to try it all out this week. Finally back home with access to my car
Great work guys!

gustden said:
Looks like there has been great progress on these units with xposed, custom roms & twrp. I hope to get a chance to try it all out this week. Finally back home with access to my car
Great work guys!
Click to expand...
Click to collapse
Great to see you back!
When you say "finally back home" I hope your health is OK and that it's not your health that kept you away from home (and here) so long.
And yes, I finally picked up java.

Hey @surfer63, great work on this! Quick question, if I want to initiate the Google voice search, that intent do I use for com.google.android.search?

bogdi1988 said:
Hey @surfer63, great work on this! Quick question, if I want to initiate the Google voice search, that intent do I use for com.google.android.search?
Click to expand...
Click to collapse
For the customkeymod with launcher.sh "am start com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity"
For the XSofiaTweaker:
Use the "by intent (package name / intent)" with string "com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity"
Alternative 1, but some milliseconds slower: "by broadcast" with string "com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity"
Alternative 2, but some more miliseconds slower: "system call" with "am start com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity".
Somehow the "update on change" in the XSofiaTweaker does not work correctly (yet). It requires a soft boot from the Xposed installer (main page, "triple dot menu", soft boot")

surfer63 said:
For the customkeymod with launcher.sh "am start com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity"
For the XSofiaTweaker:
Use the "by intent (package name / intent)" with string "com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity"
Alternative 1, but some milliseconds slower: "by broadcast" with string "com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity"
Alternative 2, but some more miliseconds slower: "system call" with "am start com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity".
Somehow the "update on change" does not work correctly (yet). It requires a soft boot from the Xposed installer (main page, "triple dot menu", soft boot")
Click to expand...
Click to collapse
Thanks! I will give this a try in the morning! Last question, does the V5 rom include the Sofia no kill fix? Figured you'd know the answer to that

bogdi1988 said:
Thanks! I will give this a try in the morning! Last question, does the V5 rom include the Sofia no kill fix? Figured you'd know the answer to that
Click to expand...
Click to collapse
No, it does not. You can currently install it from my apk, or use the Xposed Installer on the ROM (preferred) as the NoKill and Customkeymod are already there.
Note: you mention the "Sofia no kill fix". The GPSSpeedFix is fixed, not the NoKill.
That fixed GPSSpeedFix is not in the V5, and due to the fact that it is installed as a system app, you currently need to install it via adb or a rooted file manager.
You can temporarily download the "fixed" GPSSpeedFix from here.
It contains the fix and uses 3 samples instead of 5. This should reduce the lag somewhat.
Edit: My new apk will support the system/app install from the gpsspeedfix.

surfer63 said:
No, it does not. You can currently install it from my apk, or use the Xposed Installer on the ROM (preferred) as the NoKill and Customkeymod are already there.
Note: you mention the "Sofia no kill fix". The GPSSpeedFix is fixed, not the NoKill.
That one is not in the V5, and due to the fact that it is installed as a system app, you currently need to install it via adb or a rooted file manager.
You can temporarily download the "fixed" GPSSpeedFix from here.
It contains the fix and uses 3 samples instead of 5. This should reduce the lag somewhat.
Edit: My new apk will support the system/app install from the gpsspeedfix.
Click to expand...
Click to collapse
Awesome! And yes, the server no kill fix. The other I updated manually - Total Commander to the rescue! I tear with nostalgia each time I use it! ???

surfer63 said:
Somehow the "update on change" in the XSofiaTweaker does not work correctly (yet). It requires a soft boot from the Xposed installer (main page, "triple dot menu", soft boot")
Click to expand...
Click to collapse
I found why it does not get updated. I use a broadcast to update (from the example), but I do not have a broadcast receiver. So now find a new example to implement that broadcast receiver

I tried installing Xposed on my rooted Joying Sofia JY-VL130N2 and ended up with a brick (stuck in Android boot logo).
My steps were:
1) Downloaded and installed XposedInstaller_3.1.5.apk from the official XDA page https://forum.xda-developers.com/showthread.php?t=3034811
2) Installed some "v89" thing (sorry, I am a newbie to Xposed)
3) Accepted the dialog which warns about soft-bricks and the app restarted the unit
4) Not starting up anymore. Stuck in Android's boot logo after its animations had played.
What was wrong?
EDIT by myself: I did not use the Superuser apk for Sofia as documented by you. Sorry for the noise.

realzoulou said:
I tried installing Xposed on my rooted Joying Sofia JY-VL130N2 and ended up with a brick (stuck in Android boot logo).
My steps were:
1) Downloaded and installed XposedInstaller_3.1.5.apk from the official XDA page https://forum.xda-developers.com/showthread.php?t=3034811
2) Installed some "v89" thing (sorry, I am a newbie to Xposed)
3) Accepted the dialog which warns about soft-bricks and the app restarted the unit
4) Not starting up anymore. Stuck in Android's boot logo after its animations had played.
What was wrong?
Click to expand...
Click to collapse
Need to reflash the unit.

@surfer63 when I try to download and install package in Xposed installer I get an error that package name is incorrect

bogdi1988 said:
@surfer63 when I try to download and install package in Xposed installer I get an error that package name is incorrect
Click to expand...
Click to collapse
Please be a bit more concrete.
Any package or "my" modules?
Did you already had the NoKill and/or CustomKeymod installed via my apk?
If so , first uninstall them as they are signed differently by the repo.
If it is a "fresh" install, then it is weird.

surfer63 said:
Please be a bit more concrete.
Any package or "my" modules?
Did you already had the NoKill and/or CustomKeymod installed via my apk?
If so , first uninstall them as they are signed differently by the repo.
If it is a "fresh" install, then it is weird.
Click to expand...
Click to collapse
Fresh install I even tried clearing Xposed app data/cache and same issue. Downloads like 71kb and then errors out that package name is incorrect and that a different name was expected.
EDIT: I was also driving when I posted that, so I had to be short :silly:

bogdi1988 said:
Fresh install I even tried clearing Xposed app data/cache and same issue. Downloads like 71kb and then errors out that package name is incorrect and that a different name was expected.
EDIT: I was also driving when I posted that, so I had to be short :silly:
Click to expand...
Click to collapse
I did not even try if it worked. I simply assumed that the global repository would simply work.
Will test tomorrow.

surfer63 said:
I did not even try if it worked. I simply assumed that the global repository would simply work.
Will test tomorrow.
Click to expand...
Click to collapse
How do I manually install the module?

bogdi1988 said:
How do I manually install the module?
Click to expand...
Click to collapse
manually via adb or a rooted file manager.
You can also install the latest nokill and customkeymod from my apk.
Probably this evening I will release my new JET apk also allowing you to overwrite/install the current, as system app installed, GPSSpeedFix in the gtx ROM.
And I will add my XSofiaTweaker to the apk. I need to do some final tests this afternoon.
I had done it wrong with my modules on the xposed repo, but I corrected that and they still give errors. Customkeymod still gives a package error.
The Nokill gives a 404 error and can't be downloaded. I really don't understand it.

if I install the Xposed modules with the version 40, I find you in Xposed not. with version 39 this worked. I use the GTX Rom.
greeting