Can someone help me by telling me what this command actually does?
Code:
echo 1 > /sys/devices/system/cpu/cpu1/online
A thread has been started elsewhere claiming this enables the "second core" for the Atrix CPU. I know there is no need to "enable." I just want to make sure applying this is not harmful as it's been instructed for people to do this on their phone and then use this to check and make sure it worked:
Code:
cat /proc/cpuinfo
Help would be appreciated as I want to avoid problems caused by misinformation.
Thanks in advance.
Moved to Q&A as not android development
I don't know what these commands are supposed to be doing for you but...
"echo x > filename" is just going to create a file with x in it.
cat filename is just going to display what is in file.
Contact the original poster of that command and ask them for more info.
Thanks, I tried asking him. He essentially just found it somewhere on the net and decided to post it claiming that it 'cured' our 'inactive second core.' I don't think he knows, honestly. He's since stopped posting there. I just didn't want anyone to see it and try it and it do something harmful. Thanks again.
Related
I want to use eclipse and the sdk to launch apps I am developing on my touch pro 2. I have installed the htc adb drivers, but my phone dosn't show up in adb even though android thinks it is connected. It is definitly some combo of phone/drivers as my friends hero works perfectly.
Any advice?
incase anybody cares, they answered this over on ppcgeeks
forum.ppcgeeks.com/showthread.php?t=116900
quick summary
millmanorama said:
incase anybody cares, they answered this over on ppcgeeks
forum.ppcgeeks.com/showthread.php?t=116900
Click to expand...
Click to collapse
For those just looking for the answer without registering for another forum:
Edit the andboot/conf/eclair.user.conf file to include
Code:
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
in the custom_shells section (at the bottom) so that it looks something like this:
Code:
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
}
Hello guys, I find this thread through Google and xda search. I am using XDAndroid port Froyo 2.2.1 update 1/23 and the method of edit user.conf doesn't work anymore.
This takes me many hours of searching to come to another solution in another thread.
Some may found that installing DroidExplorer may help, as suggested in this post and some posts after.
This takes me an amount of time, so I hope by leaving a note here may help some others when search for this problem.
there are two adb driver version
htc and google, you need to install htc driver
BTW,my adb shell have color control character ,so need to use shell soft to list files
I tried searching but I was surprised when I couldn't find anything.
After the froyo update, I now have twitter on my phone...I really want this **** off of my phone, but can't delete it? Someone direct me to an app to do so please?
Thanks
Sent from my Droid using XDA App
If you're running FroYo, I'm assuming that means you have root? Unless Big Red pushed out an OTA.. but I'm going to assume you have root, otherwise you're screwed 8D
So again, rooted phone: download Terminal Emulator from the market, and in it, type these commands (hit enter after each line)
Code:
su
cd system
cd app
ls
Now look through that list for what will probably be named Twitter.apk. Take note of its exact name, then
Code:
rm (whatever the exact name is).apk
And that should get rid of it. There may be extra steps to get rid of its entire footprint, but that will at least remove the app from your device.
No luck
Hi, sorry to bother. I read your thread and tried to remove that piece of **** twitter as per your instructions. It went beautifully until I hit Enter and the result was:
"failed for twitter.apk read only file system"
Is there a way to get beyond that point? Or is "Read Only file system" the final word?
Thank you in advance,
T
Did you saw the date of previous post
Saludos
thimage said:
Hi, sorry to bother. I read your thread and tried to remove that piece of **** twitter as per your instructions. It went beautifully until I hit Enter and the result was:
"failed for twitter.apk read only file system"
Is there a way to get beyond that point? Or is "Read Only file system" the final word?
Thank you in advance,
T
Click to expand...
Click to collapse
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Posted it here as this section gets the most views. If needed tom will move it to the rightful section.
There has been a lot of disappointing posts all over the forum with people complaining about bugs, while not providing any kind of information for the developers aside from "X doesn't work" or "I get random reboots".
Well, without the proper knowledge, how are we going to fix it? We don't know what kernel you may be running, what version number you're on, or any information that the system spits out to let you know there's an error. So, I decided to start this thread, to hopefully teach newbies how to give us (developers) proper knowledge when complaining about issues.
This thread will have 3 sections, Logcat (App / system debug log.), Dmesg (active kernel output) and last_ksmg (Typically if you get a random reboot or something of that sort {this is the same as dmesg except it gets the info from the last shutdown [like a kernel panic]})
Section 1: Logcat This log should almost always be included just because it provides more info than just saying something doesn't work. It will essentially tell you which apps are crashing and why and it also gives output of what they're doing. (Your system is running through apps, the dialer, wireless radio's, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat: Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don't feel like writing a 'how to use adb' tutorial for everyone's phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to the thread. It's really that simple!
For more info, check out my logcat guide here.
Section 2: Dmesg
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go "OH F***" when we use our devices. Note: You will need adb access for this to work, same as logcat. What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things. This is linux, so kernel output is important if a hardware aspect isn't working right. How to get a dmesg: This is simple as well, no matter what operating system you're on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post. You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
Section 3: last_kmsg Ok, the last thing is last_kmsg. When android kernels crash, they write the log to last_kmsg so then you can find out what's going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can't. It doesn't mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it's trying to do instead of trying to guess what it is trying to do How to get a last_kmsg: This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
Hopefully, this way we developers can have our lives be a little bit easier and you can learn more about android.
Taken from here. All due credits to him. I just edited a little part.
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
Nice.
i will add this in my developer 101 thread in next update...thanx
Xenon X said:
i will add this in my developer 101 thread in next update...thanx
Click to expand...
Click to collapse
Sure.
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
Nice tutorial :good:
Nice guide:good:
download error
when i press download rom.it doesn't download
it shows this error report when i trying to download rom
"Unable to resolve domain name
Please make sure:
- You are connected to the Internet.
- Your DNS server settings are correct.
Error code 105 (net::ERR_NAME_NOT_RESOLVED)"
please help me
Our developers are hard workers and when one of us finds a problem with a ROM or kernel it is difficult to troubleshoot without some type of log. Since the developers spend a lot of their free time creating things for us to make our phone more enjoyable the least we could do is provide something useful to them to assist in the development of their creations.
Most of you here already know how to get logs, but for those who don't or are rusty at it here are links with useful information and apps to assist in obtaining a log. Also, .torrented provided the basic commands if you're okay using adb.
So let's give back to our developers by giving them logs which are vital for development.
All-in-one logger for use in Windows
http://forum.xda-developers.com/showthread.php?t=1944776
Another logcat tool for use in Windows
http://forum.xda-developers.com/showthread.php?p=28193613#post28193613
Lumberjack- apk for obtaining logs while in android
https://play.google.com/store/apps/details?id=net.solarnz.apps.lumberjack
Universal how to get and read logcat
http://forum.xda-developers.com/showthread.php?t=2274119
There are three types of logs that are used most often: logcat, dmesg, and last_kmsg. Here is an explanation of what they are and what they're useful for
Indirect said:
Alright guys, I was on an irc channel when I considered posting this since it's rather important. There has been a lot of disappointing posts all over the forum with people complaining about bugs, while not providing any kind of information for the developers aside from "X doesn't work" or "I get random reboots".
Well, without the proper knowledge, how are we going to fix it? We don't know what kernel you may be running, what version number you're on, or any information that the system spits out to let you know there's an error. So, I decided to start this thread, to hopefully teach newbies how to give us (developers) proper knowledge when complaining about issues.
This thread will have 3 sections, Logcat (App / system debug log.), Dmesg (active kernel output) and last_ksmg (Typically if you get a random reboot or something of that sort {this is the same as dmesg except it gets the info from the last shutdown [like a kernel panic]})
Section 1: Logcat
This log should almost always be included just because it provides more info than just saying something doesn't work. It will essentially tell you which apps are crashing and why and it also gives output of what they're doing. (Your system is running through apps, the dialer, wireless radio's, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don't feel like writing a 'how to use adb' tutorial for everyone's phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to the thread. It's really that simple!
Section 2: Dmesg
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go "OH F***" when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things. This is linux, so kernel output is important if a hardware aspect isn't working right.
How to get a dmesg:
This is simple as well, no matter what operating system you're on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
Section 3: last_kmsg
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what's going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can't. It doesn't mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it's trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
Hopefully, this way we developers can have our lives be a little bit easier and you can learn more about android.
I'm glad to have written this and devs, feel free to link to this guide as a "bug reporting FAQ"
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=23036410
@orangechoochoo, any urge to update the title and the content to provide information about getting dmesg output and last_kmsg?
Once your android device is plugged into your machine, enable Android Debugging in the Developer Options! (this has to be enabled)
If you do not have ADB installed go find a tutorial and install it! (this is a must)
Very simple command, what this does is it will start ADB and output the text into a text file called logcat.txt, once you are done re-creating the error/FC/whatever take that file and upload the contents to a paste site such as https://www.pastebin.com
It's free and you do not need to sign up to create a paste!
logcat via ADB!
Nix:
Code:
[email protected]:~$ adb logcat > logcat.txt
Windows:
Code:
C:\android-tools> adb logcat > logcat.txt
last_kmsg via ADB!
Nix:
Code:
[email protected]:~$ adb pull /proc/last_kmsg
Windows:
Code:
C:\android-tools> adb pull /proc/last_kmsg
dmesg via ADB!
Nix:
Code:
[email protected]:~$ adb shell dmesg > dmesg.txt
Windows:
Code:
C:\android-tools> adb shell dmesg > dmesg.txt
crpalmer said:
@orangechoochoo, any urge to update the title and the content to provide information about getting dmesg output and last_kmsg?
Click to expand...
Click to collapse
I just finished adding more stuff, let me know if you want me to put anything else that will be helpful. The All in One tool looks useful if someone is stuck in the boot animation, and Lumberjack looks useful for obtaining logs while booted in android.
Thanks for the quick links, I'm sure it will help alot of users out. MY question is whether devs want us to filter anyting out, its not too hard to select faults and errors and filter useless info.
This should be pinned.. for sure!
jake.corey.jacobs said:
MY question is whether devs want us to filter anyting out, its not too hard to select faults and errors and filter useless info.
Click to expand...
Click to collapse
That would be nice to know, last night I provided Pio a long a$$ logcat so I feel bad for giving him that extra homework
The ROM was stuck in the boot animation and logcat was spitting out line after line after line so I hit ctlr C to stop it.
Nice guide...
I'm trying to get a script to execute via init.d or even in the terminal ... sh ./script but am running into issues that I'm not sure why or what is happening. I can't get the script to even execute via command line with the terminal app...so I need to figure that out first then maybe init.d will work. I can however execute the command in the script just fine, so I am not sure what is going on. It should be a simple script that I've seen posted on XDA. I started a thread over on the blaze dev section buy have been told it would fit here better so I'm posting a link to what I've already done.
http://forum.xda-developers.com/showthread.php?p=45042841#post45042841
As you can see from that link and the screenshot the execution of the script fails but I can echo that string in just fine. I'd like to get this scripted to it will work on boot and hopefully find a way to make it run before apps start starting so the sd card will prepare faster and the files I have apps linked to will be present when there requested...which is a problem.
Thanks!