Hello guyzz... you can perform a simple trick described below to Enable Lock screen rotation. To do this ROOT is required.
1. Open the file manager on your Android device
which supports root file system access. I prefer Root Explorer.
2. Navigate to the following folder:
/system
3. There you will find a file named build.prop. You
need to edit it, so open it in your favorite text
editor. Again, I will use the built-in editor of the
Total Commander app, as it is powerful and
supports many useful features.
4. Add the following line to your build.prop file:
lockscreen.rot_override=true
Tip: Before you add the line, check if the same
parameter is present in the build.prop file, but with
the value set to false. If it is present, then modify
the existing line and set it to true.
That's it. Now reboot you device. The lock screen will
respect the gravity sensor right after reboot.
Related
Disclaimer: If your phone explodes, dies a miserable death, or any of a million things, don't come crying to me. Do this at your own risk!
Having said that... this is THE EASIEST way to change the Carrier Name in CM9, CM7, and MIUI on the Triumph.
This will NOT work on stock FROYO!
INSTRUCTIONS:
1. Download flashable Zip at end of post -- triumph_cm7_miui_carrier_name.zip
2. Open the Zip file and extract the eri.xml file in /data/ to your desktop using a zip utility such as WinZip, 7-zip, etc.
3. Open the eri.xml file in your favorite text editor such as notepad++.
4. In LINE 7, change Virgin Mobile in Eritext="Virgin Mobile" to whatever text you want, for example:
Code:
<EriInfo RoamingIndicator="1" IconIndex="1" IconMode="0" EriText="I am AWESOME" CallPromptId="0" AlertId="0" />
IF you want to use the following special characters in the text, you will need to use the escape characters instead (for example instead of & use & ):
Code:
Character Reference
& &
< <
> >
" "
' '
5. Save the eri.xml file after making your changes.
The following are 3 methods of updating your phone. Use whichever method you are most comfortable with.
A. Using the flashable zip and flashing in CWM.
1. Add the updated eri.xml back into the /data folder in the triumph_cm7_miui_carrier_name.zip -- make sure that you use "no compression" or "store" when adding it back.
2. Save the triumph_cm7_miui_carrier_name.zip on your sdcard.
3. Reboot into CWM and flash the zip file as usual.
B. Using ES File Explorer, Root Explorer, or another file explorer capable of root. (In the instructions below, I'll reference ES File Explorer since that is what I use but the instructions should be similar for any of the file explorers.)
1. Copy the updated eri.xml file onto your sd card.
2. On your phone, open up ES File Explorer.
Make sure that you have your settings set to mount the file system as writable:
2a. In ES File Explorer, hit menu --> Settings.
2b. Make sure there is a checkmark in the following checkboxes: "Root Explorer" and "Mount File System".
3. In ES File Explorer, browse to your sd card where you saved the eri.xml file.
4. Long press on eri.xml to bring up the popup menu.
5. Select Copy.
6. Next, browse to /data/. To do that, click the Favorites button on the toolbar and select the / from the Favorites popup window and then go into /data/.
7. Hit the Menu button on your phone and select Operations --> Paste.
8. You should now see the eri.xml file in your /data/ folder.
9. Close out of ES File Explorer.
10. Toggle Airplane Mode on and then off. When your service comes back, the carrier name should reflect your new Carrier name text. If not, reboot your phone.
C. Using ADB. The following instructions are for windows but you should be able to do the same in any other OS.
1. This assumes that the updated eri.xml file is on your desktop as I instructed above and you already have your phone connected to your computer. Open the command line in Windows.
2. type the following commands:
Code:
cd %userprofile%\desktop
adb push eri.xml /data/eri.xml
3. Toggle Airplane Mode on and then off. When your service comes back, the carrier name should reflect your new Carrier name text. If not, reboot your phone.
If you are uncomfortable using adb or don't have it installed or don't know what it is, then I'd recommend using method A or B.
To UNDO all changes:
This is SUPER EASY:
1. Using ES File Explorer, browse to /data/
2. Delete the eri.xml file.
3. Toggle Airplane Mode on and then off. When your service comes back, the carrier name should reflect your original Carrier name text. If not, reboot your phone.
Nevermind. I got it. Lol. very nice.
Sent from my Motorola Triumph using Tapatalk
woot.. been looking all over for a simple method to get my phone to stop saying sprint all the time...
INTRODUCTION:
Boot Buddy will allow you to run Linux shell scripts when your Android device is booting up. It will run your scripts early in the boot process, before the home screen appears.
The intended audience is generally intermediate to advanced users, and those who want to play with shell scripting on their device.
FEATURES:
BootBuddy is similar to init.d scripts, but with a core difference that it stores boot scripts on your SDcard instead of the internal system. This allows for several interesting enhancements. Feature listing-
Much more Safe than init.d. If you have a script that is malfunctioning, just boot with the sdcard out, and put the sdcard back in after your device reaches home screen. Your device is Saved, No Problem!
Boot Buddy is designed from the start to run scripts right from your SDcard. Just download any scripts to your boot_buddy_scripts directory and they're ready to run. (No more screwing around with permissions and files in your /system/etc/init.d/*)
SDcard storage allows you to copy a script to another device, or multiple devices easily.
Boot Buddy's author has several years of scripting and programming experience. It is streamlined, fast, and doesn't perform worthless functions like repeatedly logging the authors name and time (*hint to a t-init author*).
Clear goals of making operation simple, intuitive, and clean.
If you're currently using an "init.d" solution, BootBuddy can integrate seamlessly with it.
If you try BootBuddy and you don't like it, the installer also works as an uninstaller for easy clean removal.
BootBuddy is Open Source GNU GPL. Open for anyone to modify and improve upon.
As a developer, I make software to operate the way I would want if I were an end user, because I actually do use it, and I am an end user like you.
REQUIREMENTS:
Android 4.0 and up
Rooted device
An sdcard
Script Manager Free (or any other app that can run scripts as root)
Boot Buddy Installer bb_install.sh
INSTALL:
Start Script Manager, and allow/grant root access.
Navigate to the bb_install.sh file.
Tap on the file to show the menu options.
At the top, highlight the "Su" icon.
On the top-left, tap "Run".
The script will run quickly. It will automatically detect your sdcard location and create a folder on your sdcard named "boot_buddy_scripts". In that folder, you put the scripts you want to run at system boot. A log file will be kept at /data/boot_buddy.log
If you need your scripts to run in order, they are ordered by filename using the busybox "sort" program. They will run in alphabetical order using this format 0-9A-Za-z.
YOUR FIRST SCRIPTS: (OPTIONAL)
Here are a couple example scripts you may use.
The Android /system is normally mounted with read-only permissions by default. We will change that with the first script listed below. It will cause /system to be remounted to read-write permissions during boot.
The second script will create a file at every boot named /mnt/sdcard/sys_mount_info.txt. That txt file will give us information about how /system is currently mounted.
Download the file 00rw_system.sh into your boot_buddy_scripts folder.
Download the file 99sys_mount_info.sh into your boot_buddy_scripts folder.
Reboot your phone.
That's it, you just installed 2 new scripts and had them run at boot. It's Really just that simple to add startup scripts to your system.
To verify they are running, use any text viewer to open the file /mnt/sdcard/sys_mount_info.txt. It may show more than one line of text. There should be a line similar to this:
/dev/block/(device specific text) /system (fstype) rw,(more text)
The rw means that /system was successfully remounted as read-write during boot.
At any time you can delete either script if you choose. Easy!
UNINSTALL:
If for any reason you find you don't want or don't like Boot Buddy, you can cleanly uninstall it using the installer bb_install.sh. These instructions are almost identical to installing. (All match the installation steps, except step 4)
Start Script Manager, and allow/grant root access.
Navigate to the bb_install.sh file.
Tap on the file to show the menu options.
Type --uninstall in the text area labeled Arguments.
At the top, highlight the "Su" icon.
On the top-left, tap "Run".
Boot Buddy will be uninstalled. It will not remove the contents of your boot_buddy_scripts folder. If you have an "init.d" system installed, it will cleanly remove only Boot Buddy parts and leave the rest.
MUST READ
ADVANCED NOTES:
Boot Buddy will Not cause harm to your system, but it may not work on custom roms. Also, it may fail to detect the real location of your SDcard. It requires that /system/etc/install-recovery.sh is run during the boot process, and that file will be created if it does not exist. Also the file /data/boot_buddy.sh will be created. The script /system/etc/install-recovery.sh will run /data/boot_buddy.sh. The script /data/boot_buddy.sh will run the scripts on your sdcard. The file /data/boot_buddy.log will log any script output.
For Windows and Mac users- If you download the installer to your pc first, do not edit the installer with a text editor. Your computer will add hidden markers at the ends of each line that will prevent the installer from running. If you want to edit it, you should do so on a Linux pc or directly on your Android device.
Tell us about your results!!!
BootBuddy source code: http://github.com/Sepero/bootbuddy
NOTE : I AM NOT A DEVELOPER I AM ONLY SHARING THIS. So Try On Your Own Risk. I Can't Help Anything.
Credits :
[email protected]
Script mgr says I'm not root, despite me in a root terminal elsewhere. wtf ?? ...
I'm not root in script mgr., even though I'm showing up as root in terminal.
I've installed Super user (chains sd ), just in case the App doesn't support my other Supersu App or similar.
I've utilised the su icon and run.
I did tick run as executable.
No reboot tried.
What am I missing ??
Please advise.
I give you 5 stars to the thread
Almost first!!! haha.... this is awesome dude this could be HUGE.
Steve Eligoyo said:
I'm not root in script mgr., even though I'm showing up as root in terminal.
I've installed Super user (chains sd ), just in case the App doesn't support my other Supersu App or similar.
I've utilised the su icon and run.
I did tick run as executable.
No reboot tried.
What am I missing ??
Please advise.
Click to expand...
Click to collapse
You must to select root when start on script mgr, you have skull head with crossed bones
Steps to complete failure: Page 96 ?? ...
Here are the steps I've taken to get kicked in the teeth:
Boot phone > menu > script mgr. > start > scroll to file (in this case bb _install.sh ) > open file > tick su ( tried boot and bgr several times, nada amigo ) as instructions state > run > unexpected oper error: your not root > rinse and repeat sixty times > open terminal > su > Works just fine > Post my question on xda in the WTF Thread
Update:
After creating the directories and files needed to make this train wreck into a working setup, (obviously a few are missing here, working on it), I reopened script mgr and browsed the file system, which shows bb _install.sh file (and the other two in this
Thread as well) with the green su skull and crossbones with the boot dot next to those skulls, yet the apps shell /console says oper error - Your not root.
Again, I open terminal, su > enter > Viola!, I'm root.
I've installed the sdcard v. of script mgr as well and I get a message stating /data/system/xbin does not exist.
I'll likely need to tweak the script mgr settings to /sdcard 0/externalsd /directory bind /system /xbin/bb _install.sh - something like that.
Still doesn't explain why the app is putting the brakes on root terminal in the nag screen.
Any ideas ??
MAN THANK YOU !!!! as a noob i couldn´t get init.d to work right. so i tried your script on the xperia z3c with stock 4.4.4
to make it compatible with z3c you need to edit the file /data/boot-buddy.sh after the installation
and replace both
/boot_buddy_scripts/
with
/storage/emulated/legacy/boot_buddy_scripts/
or
/storage/sdcard1/boot_buddy_scripts/
or another prefered location
then make a new folder boot_buddy_scripts in the location.
really it executes the scripts way before the apps are starting , this is so nice and will be on my phones from now on !
edit: i also now changed the log file creation to the sd card for quick access (most filebrowsers open there by default)..
the logfile is major awesome btw if something didn´t go right , its easy to debug , thanx alot again
Won't install says I don't have busybox. I have it but it has to go in system bin instead of xbin. Amy way to get this working?
Here I'm gonna show how to enable VIRTUAL_KEYS by default
REQUIREMENTS:
1. Rooted device
2. Root Explorer here
PROCEDURE:
1. Open directory /system/build.prop:
2. Open the playful toy build.prop: with text editor
3. At the end add this code
Code:
qemu.hw.mainkeys=0
4. To disable it remove the code or edit it as
Code:
qemu.hw.mainkeys=1
HIT THANKS IF YOU LIKE MY SMALL THREAD
Virtual key
what is virtual keys in android
karthick mostwanted said:
Here I'm gonna show how to enable VIRTUAL_KEYS by default
REQUIREMENTS:
1. Rooted device
2. Root explorer
1. Open directory /system/build.prop:
2. Open the playful toy build.prop: with text editor
3. At the end add this code
Code:
qemu.hw.mainkeys=0
4. To disable it remove the code or edit it as
Code:
qemu.hw.mainkeys=1
HIT THANKS IF YOU LIKE MY SMALL THREAD
Click to expand...
Click to collapse
Virtual keys means are of those soft keys (home,back,search) to be filled inside the bottom of screen
Hello,
the Main XDA Page had a tutorial on how to disable the Google Assistant.
Step 1: Root
Step 2: Change build.prop
All you need to do is edit build.prop with the following change, reboot, and clear Google App data and you’ll no longer be greeted with the Google Assistant.
Change
Code:
ro.opa.eligible_device=true
to
Code:
ro.opa.eligible_device=false
Click to expand...
Click to collapse
But somehow I am stuck with how to change build.prop.
- With adb pull I can get the file, but I can't push it, I get the message "failed to copy 'build.prop' to '/system/build.prop': couldn't create file: Permission denied"
- I can't do adb root, I get the Message "adbd cannot run as root in production builds"
- With Total Commander I can't change the File as TC can't mount system with RW.
It would be great to know how to disable the Google Assistant, I anyway don't use it.
Cheers
I was able to mount as RW with ES File Manager (with root installed on the phone), they have a root browser option built in that is off by default. Enable it and select the mounts you want as RW and edit away. I used this to edit the build.prop and bootanimation
Tnx, worked smooth! Assistant no more
I'm guessing that we will need to be able to use TWRP to mount /system in order to modify the build.prop through ADB, that's what was required for Nexus without rooting.
FULL GUIDE TO CHANGE ACCENT COLORS
Hello everybody, This is my first post on xda. This guide is for those who want to change accent colors of non-system apps manually using substratum.
PREREQUISITIES
1.Rooted Android Phone
2.substratum theme engine(download from playstore)
3.Android Studio
4.Git installed on PC
5.APK tool (You can find easily on google)
6.Notepad++
STEPS
1.First of all, clone Substratum Theme Project from git into your Android Studio project
https:github.com/substratum/template (Add //)
2. Then change Theme Name,Email that is used for queries and other details in theme_configurations.xml
3.Then connect your device with the PC. Make sure ADB is installed in your computer and your phone has USB Debugging enabled.( Device Drivers should be installed too)
4.Go to the folder where ADB is installed(where adb.exe is located) and open a cmd window there(shift+right click)
5. Confirm that your device is connected properly by typing "adb devices"(without double quotes)
6.Once your device has been connected properly,you will see your device in List Of Devices
8. Then open root browser on your mobile and navigate to data/app/
9.Locate the android app folder you want to theme.(App must be installed on your phone)
Then type adb pull /data/app/com.android.yourapp/base.apk (Here change the app folder and app name accordingly.Copy the base.apk to apktool folder
7.Then open an another cmd window in to folder where apktool(jar) is located.
10.Then go to the cmd you opened in apktool folder,Type apktool_2.3.0.jar d base.apk
11.Then a folder will be created in that directory.
12.Then open the app in your phone with the device connected to pc and leave the phone with screen open(idle)
13.Go to tools->Android->Android Device Monitor->Dump View Hierarchy for UI Automator
14.Then a screenshot will get opened.
15.Moving the mouse will create a certain red boundary
16.Point it to any element you want to theme and check its resource-id
17.Then go to the folder which you created while decompiling the apk using apktool
18. Copy the path to that directory
19.Open Notepad++ and press Ctrl+Shift+F
20. Enter the resource-id you saw in "Find what" and directory in "Directory"
21.Notepad++ will search for this name in all the files of all the folders.
22. Then you will get some search results
23.Open the search result wherever you see background color code
24. Copy the line you want to change
(YOU CAN ALSO CHANGE THE COLORS USING COLORS.XML PRESENT IN res/values/colors.xml)
25.Then open Android studio and delete all the folders INSIDE the OVERLAYS FOLDER
26.In overlays folder,create a folder named com.android.(yourapp) and inside that folder create the whole directory of the file you edited) For example-> If you edited colors.xml,then create res folder and inside it create values then create a xml file named colors.xml
27. Inside that XML file inside the resources tag, paste the line you copied (The one you want to edit).
28. Compile and run the project on your phone(You will see the substratum theme installed on your phone with your app as a option)
29. Apply it and see the difference
(TIP: If you want to interchange white and black colors of the app, edit colors.xml and change all the white colors to black.After doing this,check whether all the colors are as desired. If not,change the color of a specific element manually as in this tutorial)
30. VOILA.!! You just made your first Substratum Theme. Good luck Themer...!!
(This method works on most apps)
Do ask if u have any query
Dosen't work
rohan_asthana said:
FULL GUIDE TO CHANGE ACCENT COLORS
Hello everybody, This is my first post on xda. This guide is for those who want to change accent colors of non-system apps manually using substratum.
PREREQUISITIES
1.Rooted Android Phone
2.substratum theme engine(download from playstore)
3.Android Studio
4.Git installed on PC
5.APK tool (You can find easily on google)
6.Notepad++
STEPS
1.First of all, clone Substratum Theme Project from git into your Android Studio project
https:github.com/substratum/template (Add //)
2. Then change Theme Name,Email that is used for queries and other details in theme_configurations.xml
3.Then connect your device with the PC. Make sure ADB is installed in your computer and your phone has USB Debugging enabled.( Device Drivers should be installed too)
4.Go to the folder where ADB is installed(where adb.exe is located) and open a cmd window there(shift+right click)
5. Confirm that your device is connected properly by typing "adb devices"(without double quotes)
6.Once your device has been connected properly,you will see your device in List Of Devices
8. Then open root browser on your mobile and navigate to data/app/
9.Locate the android app folder you want to theme.(App must be installed on your phone)
Then type adb pull /data/app/com.android.yourapp/base.apk (Here change the app folder and app name accordingly.Copy the base.apk to apktool folder
7.Then open an another cmd window in to folder where apktool(jar) is located.
10.Then go to the cmd you opened in apktool folder,Type apktool_2.3.0.jar d base.apk
11.Then a folder will be created in that directory.
12.Then open the app in your phone with the device connected to pc and leave the phone with screen open(idle)
13.Go to tools->Android->Android Device Monitor->Dump View Hierarchy for UI Automator
14.Then a screenshot will get opened.
15.Moving the mouse will create a certain red boundary
16.Point it to any element you want to theme and check its resource-id
17.Then go to the folder which you created while decompiling the apk using apktool
18. Copy the path to that directory
19.Open Notepad++ and press Ctrl+Shift+F
20. Enter the resource-id you saw in "Find what" and directory in "Directory"
21.Notepad++ will search for this name in all the files of all the folders.
22. Then you will get some search results
23.Open the search result wherever you see background color code
24. Copy the line you want to change
(YOU CAN ALSO CHANGE THE COLORS USING COLORS.XML PRESENT IN res/values/colors.xml)
25.Then open Android studio and delete all the folders INSIDE the OVERLAYS FOLDER
26.In overlays folder,create a folder named com.android.(yourapp) and inside that folder create the whole directory of the file you edited) For example-> If you edited colors.xml,then create res folder and inside it create values then create a xml file named colors.xml
27. Inside that XML file inside the resources tag, paste the line you copied (The one you want to edit).
28. Compile and run the project on your phone(You will see the substratum theme installed on your phone with your app as a option)
29. Apply it and see the difference
(TIP: If you want to interchange white and black colors of the app, edit colors.xml and change all the white colors to black.After doing this,check whether all the colors are as desired. If not,change the color of a specific element manually as in this tutorial)
30. VOILA.!! You just made your first Substratum Theme. Good luck Themer...!!
(This method works on most apps)
Do ask if u have any query
Click to expand...
Click to collapse
It doesn't work on xposed installer .
substratum isn't showing xposed installer in it's overlays.
Thanks for the post.