Does the average user need terminal emulator? I've never use it so is it safe to delete?
There are only 10 kinds of people. Those who understand binary math, and those who don't.
duckredbeard said:
Does the average user need terminal emulator? I've never use it so is it safe to delete?
Click to expand...
Click to collapse
No. So yes it is safe to uninstall it.
Related
I am running the SuperD donut rom. People have had trouble with Apps2SD not being active. I know there is something I can type into terminal to check if it is running, but I do not know what it is. I have searched, but the search on XDA does not work very well.
The only people with trouble are the ones using EXT4 which is the slowest but some say it has more feats than ext2.
Isn't there a terminal command that I can do that will confirm it is running though?
mekkelrichards said:
Isn't there a terminal command that I can do that will confirm it is running though?
Click to expand...
Click to collapse
No, check how much space you've used in phone storage
so i managed to root my g1....now when i install apps how do i know that its installing in the memory card and not the phone memory
2:what are the full advantages of rooting
3:anythin i should know since i did my rootin
1. Type in terminal
Code:
busybox df -h
and look in your /system/sd, if any of it used - then you're doing it right.
2. Tethering, apps2sd, Ram swap, overclocking, different roms, etc,
3. Search before asking, google is your friend, post in the right forum (which you did). You can figure out everything else else.
Good luck.
borodin1 said:
1. Type in terminal
Code:
busybox df -h
and look in your /system/sd, if any of it used - then you're doing it right.
2. Tethering, apps2sd, Ram swap, overclocking, different roms, etc,
3. Search before asking, google is your friend, post in the right forum (which you did). You can figure out everything else else.
Good luck.
Click to expand...
Click to collapse
alrigth actually i searched but i didnt have the right question so i wasnt gettin the answer
thanx
borodin1 said:
1. Type in terminal
Code:
busybox df -h
and look in your /system/sd, if any of it used - then you're doing it right.
2. Tethering, apps2sd, Ram swap, overclocking, different roms, etc,
3. Search before asking, google is your friend, post in the right forum (which you did). You can figure out everything else else.
Good luck.
Click to expand...
Click to collapse
I get permission denied
what do you get if you type
Code:
su
and which rom are on you?
borodin1 said:
what do you get if you type
Code:
su
and which rom are on you?
Click to expand...
Click to collapse
it asks me if i want to allow or deny
Allow it (and check the mark to always to it, you'll get sick of allowing it every time).
See if works
Code:
su
busybox df-h
This is weird though....this does not modify anything else... just gives you the output of your partitions.... works for me without su prompt.
borodin1 said:
Allow it (and check the mark to always to it, you'll get sick of allowing it every time).
See if works
Code:
su
busybox df-h
This is weird though....this does not modify anything else... just gives you the output of your partitions.... works for me without su prompt.
Click to expand...
Click to collapse
now it says busybox not found...
i completed everythin from here
http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/
Which rom did you flash once you rooted your phone? This will determine if you have busybox utility (which is helpfull)
OK.... here's another one
Code:
ls /system/sd/app
ls /data/app
That will give you a list of apps installed in each partition (/data/app is internal, /system/sd/app is external)
Doesn't quite give you the size or free space in each but gives you at least some idea of where your apps are going.
Good luck.
borodin1 said:
Which rom did you flash once you rooted your phone? This will determine if you have busybox utility (which is helpfull)
OK.... here's another one
Code:
ls /system/sd/app
ls /data/app
That will give you a list of apps installed in each partition (/data/app is internal, /system/sd/app is external)
Doesn't quite give you the size or free space in each but gives you at least some idea of where your apps are going.
Good luck.
Click to expand...
Click to collapse
i flashed the generic rom from unlockr
So it may not have that utility... sorry I'm not about to look through that whole website just to find out. And it's not a big deal for most people anyway. I'm sure you will not be on that rom too long anyway .
borodin1 said:
So it may not have that utility... sorry I'm not about to look through that whole website just to find out. And it's not a big deal for most people anyway. I'm sure you will not be on that rom too long anyway .
Click to expand...
Click to collapse
thats ok actually i think i need to downgrade to 1.5 again cuz i'm not even able to instal other roms it just aborts
how do i use the terminal emulator app to access adb shell?
adb shell is only used when you're on a computer, like when using android sdk tools. When you use the terminal emulator you use different commands try This Link for some help using the terminal emulator, they're basically the same as linux commands.
also this should be in the Q&A section
lol the terminal is the 'shell'
if you're running a terminal right on the phone, then consider yourself already @root when you're typing in commands.
foil said:
lol the terminal is the 'shell'
if you're running a terminal right on the phone, then consider yourself already @root when you're typing in commands.
Click to expand...
Click to collapse
Sort of. You are a user, but not "root". To become superuser you have to use the SU command.
/ $ su
~ # |
Click to expand...
Click to collapse
I'm sorry if I'm nitpicking here. Your original point remains true. You don't have to use ADB at that point to run commands. You run the command without ADB right in the terminal.
subcypher said:
Sort of. You are a user, but not "root". To become superuser you have to use the SU command.
I'm sorry if I'm nitpicking here. Your original point remains true. You don't have to use ADB at that point to run commands. You run the command without ADB right in the terminal.
Click to expand...
Click to collapse
No, you're fine. I was just assuming that he was already rooted, but you're right - it's a regular user account unless you change to superuser.
in order to do what you probably want you will have to type su. It should then ask for SU permission and then you should gey
Code:
#
.
hello everyone, idk if im in the wrong place, but im trying to connect my non rooted phone to my rooted tablet with terminal emulator.Is there a way for me to use adb because it worked with my previous phone...its not working and isn't showing any device when i input "adb devices"...Can anyone help me please, help would be greatly appreciated ?(btw usb debugging is enabled on my phone)
Like the title says, I always to type busybox in front of every command. I hate it, and any way to remove that?
Bump!?!?! No one can help?
what are you trying to do? you need to give more details.
refthemc said:
what are you trying to do? you need to give more details.
Click to expand...
Click to collapse
I want to run commands normally, but I have to type "busybox" in front of every command to make them work.
SimranSingh said:
I want to run commands normally, but I have to type "busybox" in front of every command to make them work.
Click to expand...
Click to collapse
I am trying to figure out what commands your running. It can make a difference. Are you typing these in a shell or using a terminal emulator? You need to be more specific for us to help.
I have heard that disabling it can make Oreo ROMs faster. Also, can someone help me with screenshots of using those commands on a computer?? I don't know if I'm doing it right.
Basically, tell me everything bout it.
Regards
@m00nlighter can help, he seems to know bout thjs
Dude, just wait for the Pie ROMs to become mature.
Oreo ROMs for Titan were simply not on par with Nougat ones, and a debloated stock Marshmallow ROM with ZRAM disabled will beat both Nougat and Oreo ROMs in terms of performance and stability.
So for now it's either stock or Pie, Oreo is history.
But I want to use Oreo, they ain't that bad for me. Could you please help me??
Detailed instructions are below. Please don't ask for further explanations, this is as simple as I can make it.
It's somewhat complicated and requires adb access and root permissions, so you have to be rooted.
Moreover, you have to have some free space on /system partition (I'd say around 300 megabytes) because ALL packages (apps) will be recompiled, including system apps. As for the data partition, it is hard to tell, depends on what apps you have. I recommend starting with minimum required apps.
First, disable the JIT compiler
adb root
adb shell stop
adb shell setprop dalvik.vm.usejit false
adb shell start
Click to expand...
Click to collapse
Second, clear profile data and remove compiled code for all packages
adb root
adb shell cmd package compile --reset -a
Click to expand...
Click to collapse
Third, force compile all packages using "speed" compiler profile (AOT-compiles all methods in app code)
adb root
adb shell cmd package compile -m speed -f -a
Click to expand...
Click to collapse
And finally, add/edit the following two properties to system.prop:
dalvik.vm.usejit=false
Click to expand...
Click to collapse
This will permanently disable the JIT compiler.
pm.dexopt.install=everything
Click to expand...
Click to collapse
This will force AOT compilation for apps, including updates and new installs.
After that, reboot and enjoy your FAST Oreo ROM
Why JIT compiler should be disabled on old devices like Titan?
Read the excellent post by Farhan on Stack Overflow here:
https://stackoverflow.com/questions/40336455/difference-between-aot-and-jit-compiler-android#
Where did I get this info from?
Official Android docs. See
https://source.android.com/devices/tech/dalvik/configure
and
https://source.android.com/devices/tech/dalvik/jit-compiler
m00nlighter said:
Detailed instructions are below. Please don't ask for further explanations, this is as simple as I can make it.
It's somewhat complicated and requires adb access and root permissions, so you have to be rooted.
Moreover, you have to have some free space on /system partition (I'd say around 300 megabytes) because ALL packages (apps) will be recompiled, including system apps. As for the data partition, it is hard to tell, depends on what apps you have. I recommend starting with minimum required apps.
First, disable the JIT compiler
Second, clear profile data and remove compiled code for all packages
Third, force compile all packages using "speed" compiler profile (AOT-compiles all methods in app code)
And finally, add/edit the following two properties to system.prop:
This will permanently disable the JIT compiler.
This will force AOT compilation for apps, including updates and new installs.
After that, reboot and enjoy your FAST Oreo ROM
Why JIT compiler should be disabled on old devices like Titan?
Read the excellent post by Farhan on Stack Overflow here:
https://stackoverflow.com/questions/40336455/difference-between-aot-and-jit-compiler-android#
Where did I get this info from?
Official Android docs. See
https://source.android.com/devices/tech/dalvik/configure
and
https://source.android.com/devices/tech/dalvik/jit-compiler
Click to expand...
Click to collapse
Dude, one last question. What is the output of cmd after you type :
adb shell stop
CMKdaGreatest said:
Dude, one last question. What is the output of cmd after you type :
adb shell stop
Click to expand...
Click to collapse
There should be NO output. This command effectively stops the shell.
@m00nlighter
This is the result I'm getting. Please tell me if it is what it is supposed to be
Please answer my question, pleaseeee
If you can't see the pic,
The output to adb shell stop is something like this
"stop:must be root"
Am i doing something wrong?
CMKdaGreatest said:
@m00nlighter
This is the result I'm getting. Please tell me if it is what it is supposed to be
Please answer my question, pleaseeee
If you can't see the pic,
The output to adb shell stop is something like this
"stop:must be root"
Am i doing something wrong?
Click to expand...
Click to collapse
Yes you are doing something wrong. Please go learn how to work with adb, enough info is available, just google it.
Unfortunately I'm not able to work with adb very well. adb root command is failing I think, so adb shell stop is also failing.
Someone help me please @m00nlighter @sapo_joe @Oshmar @thedeadfish59
I use magisk as su. Is that a problem for this?