Most remember the battery percent is hidden by default, granted when you pull down the notification, it shows. However this will enable native percent on the icon itself.
I didn't create this. Just sharing.
https://play.google.com/store/apps/details?id=com.ethanf.nexusbatterypercentenabler
Top corner. Ignore my tiny DPI. Normal DPI of 560 is very visible.
Works great, thanks for sharing
Posted from a Nexus 6 running Slim Rom
Thanks allot.
or you can do the simple adb command
Code:
adb shell content insert --uri content://settings/system --bind name:s:status_bar_show_battery_percent --bind value:i:1
adb reboot
cool app, but i'd rather do this without installing another app on the phone.
Lucke said:
or you can do the simple adb command
Code:
adb shell content insert --uri content://settings/system --bind name:s:status_bar_show_battery_percent --bind value:i:1
adb reboot
cool app, but i'd rather do this without installing another app on the phone.
Click to expand...
Click to collapse
Not everyone is familiar with adb and its usage. Granted being a nexus owner they should. However remember we have toolkits that do everything where one does not need education on adb and its commands.
Also you dont have to keep the app installed. You can delete it after you enable battery percent.
However thanks for the adb command.
antiochasylum said:
Not everyone is familiar with adb and its usage. Granted being a nexus owner they should. However remember we have toolkits that do everything where one does not need education on adb and its commands.
Also you dont have to keep the app installed. You can delete it after you enable battery percent.
However thanks for the adb command.
Click to expand...
Click to collapse
that's why i hate toolkits, keeps the users from actually learning things about their phones
was not aware that uninstalling the app would keep the battery percentage. that's good info.
6 of one, half a dozen of another... multiple simple ways to achieve the same result... gotta love it
Lucke said:
that's why i hate toolkits, keeps the users from actually learning things about their phones
was not aware that uninstalling the app would keep the battery percentage. that's good info.
6 of one, half a dozen of another... multiple simple ways to achieve the same result... gotta love it
Click to expand...
Click to collapse
Exactly. I personally use adb for all my flashing. Don't like toolkits either.
And exactly. All achieves the same result. Ones easier and ones for advanced users
Beauty of android. Multiple ways to achieve the same end result.
Lucke said:
that's why i hate toolkits, keeps the users from actually learning things about their phones
Click to expand...
Click to collapse
I totally agree with you, but we live in a "gimme gimme" society. I'd rather learn how to do these things to my phone. If I screw something up, chances are I can fix it, especially on a Nexus device. Someone screws up a device with a toolkit, and they come to XDA looking for immediate "gimme gimme" help LOL
Lucke said:
or you can do the simple adb command
Code:
adb shell content insert --uri content://settings/system --bind name:s:status_bar_show_battery_percent --bind value:i:1
adb reboot
cool app, but i'd rather do this without installing another app on the phone.
Click to expand...
Click to collapse
Does this adb command do the same as the app (put the battery percentage in the battery icon) or does it put the battery percentage beside the battery icon?
eL_777 said:
Does this adb command do the same as the app (put the battery percentage in the battery icon) or does it put the battery percentage beside the battery icon?
Click to expand...
Click to collapse
in the battery icon
You can also use an sqlite editor and add the record to the system table in the com.android.providers.settings setting.db database.
Any adb command for center clock.
Lucke said:
or you can do the simple adb command
Code:
adb shell content insert --uri content://settings/system --bind name:s:status_bar_show_battery_percent --bind value:i:1
adb reboot
cool app, but i'd rather do this without installing another app on the phone.
Click to expand...
Click to collapse
Is there a list of these commands somewhere . you just thought me something new thank you
Sent from my Nexus 6 using XDA Free mobile app
I used the app, but I much rather use the adb command. I guess I need to learn how to do it.
Thanks for the link. Worked perfect.
Lucke said:
or you can do the simple adb command
Code:
adb shell content insert --uri content://settings/system --bind name:s:status_bar_show_battery_percent --bind value:i:1
adb reboot
cool app, but i'd rather do this without installing another app on the phone.
Click to expand...
Click to collapse
Thank you, sir. I used the terminal emulator app to execute the command. Much easier than using the computer.
Sent from my Nexus 6 using Tapatalk
Cheater912 said:
Thank you, sir. I used the terminal emulator app to execute the command. Much easier than using the computer.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
How did you do that? Would you mind sharing how you did that ?
stas333 said:
How did you do that? Would you mind sharing how you did that ?
Click to expand...
Click to collapse
Install this:
https://play.google.com/store/apps/details?id=jackpal.androidterm
In the app, type in "su" to switch to root. Then enter:
Code:
content insert --uri content://settings/system --bind name:s:status_bar_show_battery_percent --bind value:i:1
Reboot
Sent from my Nexus 6 using Tapatalk
Or you can run it as a root script in ROM toolbox
Related
I don't know how I did it. I don't even know if it's a windows 7 thing, or a adb shell thing. But...
When I open adb shell and enter the "ls" or "ls -l" command, it returns the name of the file/dir in a strange format. Instead of just the name like "sdcard" I get:
<-[1;34msdcard<-[0m
I'm pretty sure it didn't always do this, so I must have enabled a switch somewhere (or I'm misusing the "ls" command). I do not have this problem with Terminal Emulator on the Captivate itself... just when using ADB shell on a Windows 7 machine. How do I turn this off? Any help would be greatly appreciated.
Thanks!
dc41 said:
I don't know how I did it. I don't even know if it's a windows 7 thing, or a adb shell thing. But...
When I open adb shell and enter the "ls" or "ls -l" command, it returns the name of the file/dir in a strange format. Instead of just the name like "sdcard" I get:
<-[1;34msdcard<-[0m
I'm pretty sure it didn't always do this, so I must have enabled a switch somewhere (or I'm misusing the "ls" command). I do not have this problem with Terminal Emulator on the Captivate itself... just when using ADB shell on a Windows 7 machine. How do I turn this off? Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
ugh, this isn't garbage information or a mistake. this is windows command prompt (which isn't a proper terminal emulator) not being able to deciper the color coding techniques used in *NIX shells.
all these odd numbers are are simply color coding to "prettify" the shell if you're using a *NIX shell
Kaik541 said:
ugh, this isn't garbage information or a mistake. this is windows command prompt (which isn't a proper terminal emulator) not being able to deciper the color coding techniques used in *NIX shells.
all these odd numbers are are simply color coding to "prettify" the shell if you're using a *NIX shell
Click to expand...
Click to collapse
Thanks for the info! Now that I know what's going on, I should be able to find solution on the web.
Thanks!
dc41 said:
I don't know how I did it. I don't even know if it's a windows 7 thing, or a adb shell thing. But...
When I open adb shell and enter the "ls" or "ls -l" command, it returns the name of the file/dir in a strange format. Instead of just the name like "sdcard" I get:
<-[1;34msdcard<-[0m
I'm pretty sure it didn't always do this, so I must have enabled a switch somewhere (or I'm misusing the "ls" command). I do not have this problem with Terminal Emulator on the Captivate itself... just when using ADB shell on a Windows 7 machine. How do I turn this off? Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
I've never had this happen when I use the adb shell on my Win7 machine. Which distro are you using? I have Home Premium x64.
miztaken1312 said:
I've never had this happen when I use the adb shell on my Win7 machine. Which distro are you using? I have Home Premium x64.
Click to expand...
Click to collapse
Ultimate 64, but like I said, it wasn't always like this. Some point in the lady week I must have changed a setting or something. Now I just have to figure out what I did and how to undo it.
I am guessing you switched ROMs? Seems to be the color setting in some of the ROMs on the LS command. It is not a windows bug, any terminal/shell that doesn't support colored directory/file names will give you this behavior.
See this thread for a fix:
http://forum.xda-developers.com/showthread.php?p=7714491
I have been having this issue since I upgraded to JH3 and SRE 1.2.1a (which included a new busybox 1.17.1 and proper symbolic links). SRE 1.2.1a also remove the stock ls command. I did not start looking into fixing it until tonight. Setting an alias for every adb shell session is annoying. Android does not include any of the profile start scripts like linux does or we would be able to stick an alias in some place like a .bashrc or /etc/bashrc.
Here is a permanent solution. I normally have a permanent alias setup on my linux machines with the switches below, you can modify the switches to your liking.
create a file in notepad with the following:
"ls -alh --color=never [email protected]" do not include the quotes.
Note the switches I am using:
a = show all files including hidden (the ones that start with a "." as a prefix on the name)
l = show files in long listing format/layout
h = show file size in human readable format eg and 1k instead of 1000.
Save the file as "ll" without an extension. You can use another name if you wish.
Use adb to push the file into /sdcard then adb shell to copy it to /system/xbin or copy via root explorer.
#assuming ll is in your SDK tools folder - move to sdcard
adb push ll /sdcard
#move to xbin folder
adb shell
su
mv /sdcard/ll /system/xbin/ll
I didn't touch the permissions (its working with -rw-rwxr-x) but just in case you can set permissions on the file.
chmod 755 ll
I rebooted my phone and I was still good to go using "ll" from adb shell.
adb shell ll
or adb shell
$ll
enjoy.
Mine does the same, looks nice when I am using on Ubuntu. I had flashed JH3 + SRE 1.2.1a also.
Did you try using the "dir" command? I think it comes with busybox 1.7.1. That one outputs fine for me when I am using the cmd prompt. Only little quirk is that I have to remember not to use ls when logged on Win7.
color codes were removed in SRE 1.2.2a: http://forum.xda-developers.com/showthread.php?t=751934
tikidroid said:
I have been having this issue since I upgraded to JH3 and SRE 1.2.1a (which included a new busybox 1.17.1 and proper symbolic links). SRE
Click to expand...
Click to collapse
Your fix worked perfectly for me!
Thanks!
tikidroid said:
Here is a permanent solution. I normally have a permanent alias setup on my linux machines with the switches below, you can modify the switches to your liking.
create a file in notepad with the following:
"ls -alh --color=never [email protected]" do not include the quotes.
Click to expand...
Click to collapse
Ahhh.... thank you so much for this post. This has been driving me crazy for a few hours, and I almost considered putting an alias to ll in init.rc (but I much prefer this less invasive method)
Useful workaround, thanks. Still needed, some two years later!
Just wondering if I have installed adb correctly I can open my command prompt using windows vista and type adb devices and I get my serial number displayed as a connected device does this confirm and is working? Thanks for your help! Completely new to this.
Beamer9408 said:
Just wondering if I have installed adb correctly I can open my command prompt using windows vista and type adb devices and I get my serial number displayed as a connected device does this confirm and is working? Thanks for your help! Completely new to this.
Click to expand...
Click to collapse
As far as I know that does mean you have it installed and running correctly.
I agree, that would tell me it's installed correctly. Shell into your phone. If you can do that, you should be all set. Directions for shelling into your phone can be found in the forums. If you can't find them, let me know and I'll help you out. We all have to start somewhere. Lol!
Sent from my VS910 4G using XDA Premium App
Are you rooted? Meant to ask that.
Sent from my VS910 4G using XDA Premium App
thermal_tim said:
Are you rooted? Meant to ask that.
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
Oh sorry I thought I mentioned that in my earlier post I am rooted running decrap..and the other mods that are on this forum
Ok so this is what is going on I go into command prompt type in CD then to the tools directory and hit enter then type adb devicesand hit enter serial number comes up so I type adb shell and I get $ ok so I read somewhere if you get that prompt type aubri hit enter ok so I do that superuser permission is asked on my phone so I said allow it. Retyped adb shell and it isn't recognizing what adb is? Not sure what is going on here thanks to anyone who helps explain if I'm doing something wrong.
Beamer9408 said:
Ok so this is what is going on I go into command prompt type in CD then to the tools directory and hit enter then type adb devicesand hit enter serial number comes up so I type adb shell and I get $ ok so I read somewhere if you get that prompt type su hit enter ok so I do that superuser permission is asked on my phone so I said allow it. Retyped adb shell and it isn't recognizing what adb is? Not sure what is going on here thanks to anyone who helps explain if I'm doing something wrong.
Click to expand...
Click to collapse
Once you
$adb shell
$su
#
You shouldn't need to type adb shell again bc ur already in it...
it would also help us to help you to know what you are trying to do with ADB shell... being that you are rooted, what else do you need to do with it?
Sent from my VS910 4G using Tapatalk
S.Meezy said:
Once you
$adb shell
$su
#
You shouldn't need to type adb shell again bc ur already in it...
it would also help us to help you to know what you are trying to do with ADB shell... being that you are rooted, what else do you need to do with it?
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Thanks honestly I'm not trying to do anything with it just trying to seeif I have it installed correctly someone suggested to see if I could go into shell so I tried and that was my results.
Beamer9408 said:
Thanks honestly I'm not trying to do anything with it just trying to seeif I have it installed correctly someone suggested to see if I could go into shell so I tried and that was my results.
Click to expand...
Click to collapse
assuming your screen looked like this...
$adb shell
$su
#
...and changed from $ to # when you did it, you're good. also, it showing as a device was a good indicator too.
What is it ? ADB Shell . is it CMD command on Windows or what ?
muslimbaha said:
What is it ? ADB Shell . is it CMD command on Windows or what ?
Click to expand...
Click to collapse
https://developer.android.com/tools/help/adb.html
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
kt-Froggy said:
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
Click to expand...
Click to collapse
Sorry, but i know what it is now, how do i run it though? im trying to follow the htc desire hd guide to root my phone, which everything is done up until the point i have to test that i have root in debug mode. Not sure how to do this? run abd.exe? it just showed me a cmd window which runs and then dissapears.
If you got your phone rooted or want to test it run adb.exe shell the type su and hit enter. If the prompt change from $ to # you have root access
Sent from my LG-P990 using xda app-developers app
bitdomo said:
If you got your phone rooted or want to test it run adb.exe shell the type su and hit enter. If the prompt change from $ to # you have root access
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
What is likely to be the problem if it says SU permission denied?
If you are on stock, that means that you have no root access. If you have cm10 or cm10.1 you have to enable adb root access somewhere in the settings. I am sorry but I can not tell you at the moment where to enable it because I am on stock right now.
Sent from my LG-P990 using xda app-developers app
kt-Froggy said:
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
Click to expand...
Click to collapse
Thanks Bro for this information
Sprint users, here is a fix for wifi tethering not working
In Terminal emulator:
Code:
su
settings put global tether_dun_required 0
Reboot
Devs should incorporated into their ROMS
I still can't get this to work on sprint with LRX210. Worked on 4.4.4 by doing the tether_dun_required=0. On a side note even usb tething won't work. The built in one or EasyTether Pro.
worked for me. thanks
http://forum.xda-developers.com/showthread.php?p=56730158 this gets USB tethering working on Sprint.
Thanks everyone for your help. I re-flashed lollipop and is working great with both wifi and usb on sprint.
WhiteWidows said:
Sprint users, here is a fix for wifi tethering not working
In Terminal emulator:
Code:
su
settings put global tether_dun_required 0
Reboot
Devs should incorporated into their ROMS
Click to expand...
Click to collapse
When I try this using the Terminal Emulator in ROM Toolbox Pro, I get "Permission Denied"
hewey_mx5 said:
When I try this using the Terminal Emulator in ROM Toolbox Pro, I get "Permission Denied"
Click to expand...
Click to collapse
You need to have root access
"su"
I have root and it's granting root to RTP when I type "su".
---------- Post added at 07:33 PM ---------- Previous post was at 06:34 PM ----------
WhiteWidows said:
You need to have root access
"su"
Click to expand...
Click to collapse
Tried again and I'm still getting the same error. It is giving RTP root because I'm getting the # at the start of the next command line. I don't understand why it isn't letting me edit that file. I tried installing SQLite Editor and it doesn't even see the db even though I can see it with Root Browser. I tried making a copy of the db and putting it in a folder that my laptop can see so I could just edit it that way but that didn't work either because my laptop couldn't see the file (this is how I did it on 4.4.4). Any ideas?
hewey_mx5 said:
When I try this using the Terminal Emulator in ROM Toolbox Pro, I get "Permission Denied"
Click to expand...
Click to collapse
Set permissive in SELinuxModeChanger app from the play store.
You do NOT need root for this.
You can do this simply via ADB commands (no root required!) Go to the command prompt and go to the directory with adb/fastboot, etc. Type adb devices to ensure your computer sees your phone. After this do the following:
adb shell content insert --uri content://settings/global --bind name:s:tether_dun_required --bind value:i:0
To verify that it worked, type in the following:
adb shell content query --uri content://settings/global --where "name='tether_dun_required' AND value=0"
The query should return a row_id and a value, reboot and you should be good to go.
freshlysqueezed said:
Set permissive in SELinuxModeChanger app from the play store.
Click to expand...
Click to collapse
This worked. The terminal emulator method still didn't stick but SQLite Editor was able to open the db.
works, but needed some jujitsu
I was able to get my Surface Pro 2 tethered to my Sprint-connected Nexus 5 using the latest release of Wifi Tether Router (11/25). However, I had to go through the standard set of "Airplane Mode" reboots to get it to work.
IN ADDITION:
Fabio counseled me to select the "Reset Defaul Conf" option from the top right menu (yeah, his spelling is atrocious). After that it worked fine for me. I think it is still a bit rickety. Good luck all.
adb shell content insert --uri content://settings/global --bind name:s:tether_dun_required --bind value:i:0
Works using stock Tethering app on lollipop
Some guys may thing that you will need to mod system apks or may need to flash external zip files but NO this guide just ues simple adb command you will not even need to be rooted to impleament this guide
Instructions:-
1)Enable USB debugging
2)Connect your phone and make sure you have permitted your computer for adb operations of your device...
3)Use following adb commands
Code:
adb shell
content insert --uri content://settings/system --bind name:s:status_bar_show_battery_percent --bind value:i:1
exit
adb reboot
4)Enjoy :good: :highfive:
And this will work on almost every device
Thanks
U can easily do it by downloading Battery precentage Enabler from playstore! Is all this effort needed?
Don't know about that app
Sent from my Spice Mi-498 using XDA Free mobile app
hjmodi said:
Don't know about that app
Sent from my Spice Mi-498 using XDA Free mobile app
Click to expand...
Click to collapse
That app also works. I tried it on KitKat.
Okey, one question, how to if I want to revert back? Change the bind value:i: from 1 to 0 right?
https://play.google.com/store/apps/details?id=de.kroegerama.android4batpercent&hl=en
mohaxs said:
Okey, one question, how to if I want to revert back? Change the bind value:i: from 1 to 0 right?
Click to expand...
Click to collapse
Yep
Work lollipop 5.1 bro?
Yes
Sent from my Spice Mi-498 using XDA Free mobile app
help not commands
puturaya20 said:
help not commands
Click to expand...
Click to collapse
Have you installed ADB or Android SDK before ?
If yes, make sure the CMD is in the same folder as adb.exe
If not, install it, there's some guide floating on the forum.
hjmodi said:
Some guys may thing that you will need to mod system apks or may need to flash external zip files but NO this guide just ues simple adb command you will not even need to be rooted to impleament this guide
Instructions:-
1)Enable USB debugging
2)Connect your phone and make sure you have permitted your computer for adb operations of your device...
3)Use following adb commands
Code:
adb shell
content insert --uri content://settings/system --bind name:s:status_bar_show_battery_percent --bind value:i:1
exit
adb reboot
4)Enjoy :good: :highfive:
And this will work on almost every device
Thanks
Click to expand...
Click to collapse
Is there any command can run through Terminal Emulator app to do this???
just install that app from playstore to get thos numbers in the batt icon, much simpler i guess