First thanks to the guys helping with this in a thread that was started for another problem.
But, I still can't get adb to work. I've installed jre,jdk, and sdk with a lot of packages ( all from the Android repo and a couple from the 3rd party one). My problem isn't having the right software. My problem is I don't know how to you're out the file path in Ubuntu. On my windows position, I know that it's C:/adb. But I don't know how to type my file location in Linux. Right now, the Android-sdk-linux_x86 folder is in my home folder. I can navigate there by pointing and clicking, but how do I type that in my terminal?
Cd /home/android adb location
Sent from my GT-I9000 using xda premium
Someone with more Linux experience will probably correct me, but I believe it's:
cd /home/(your username)/adb
(bulletproof caught the CD thing)
And/or you can add that to your path...or you can move adb to something like /usr/bin...
Sent from my GT-I9000 using xda premium
mrhaley30705 said:
First thanks to the guys helping with this in a thread that was started for another problem.
But, I still can't get adb to work. I've installed jre,jdk, and sdk with a lot of packages ( all from the Android repo and a couple from the 3rd party one). My problem isn't having the right software. My problem is I don't know how to you're out the file path in Ubuntu. On my windows position, I know that it's C:/adb. But I don't know how to type my file location in Linux. Right now, the Android-sdk-linux_x86 folder is in my home folder. I can navigate there by pointing and clicking, but how do I type that in my terminal?
Click to expand...
Click to collapse
As bulletproof said, you can add it to your path, which if you're going to be using it a lot is the best solution. Then you could type adb from anywhere you are and it would work. Otherwise, you cd ~/Android-sdk-linux_x86/platform-tools, then the first time you run it do sudo ./adb start-server. From there on, you can just do ./adb insertcommandhere if you don't add it to your path. If you do add it to your path, you don't need the ./
ok, tried that, and i keep getting no such file or directory.
mrhaley30705 said:
ok, tried that, and i keep getting no such file or directory.
Click to expand...
Click to collapse
first off.
rename your SDK folder
keep it simple. i just name mine sdk in my home directory
then i add it to my path
i want to point you to a thread that i have been pushing a lot lately. it is how to setup and configure your ubuntu machine to compile CM7. it is oriented to htc devices, and more specifically the Desire Z/G2
http://forum.xda-developers.com/showthread.php?t=915435
the key part to read and comprehend is the part where you configure your ADB. you dont HAVE to do all the other stuff, but its all good info to have for the future.
its not as complicated as you are making it out to be, you just need to take the few extra minutes to understand it.
~ represents your home folder
cd ~/sdk/platform-tools
takes me to my adb executable, although by following the guide i mentioned above, i can run adb commands from anywhere within my OS, and i dont have to use sudo.
That no such directory IS due to there being spaces in the file path
Sent from my I897 using xda premium
Ok, I think I understand. I will give ita shot tomorrow. Would hit both of you with another thanks, but i've ran out today.
Update:
Thanks Pirateghost, that got it for me. Between you and sixstring I have adb working. One more question, do I have to restart the adb server everytime I use adb?
mrhaley30705 said:
Update:
Thanks Pirateghost, that got it for me. Between you and sixstring I have adb working. One more question, do I have to restart the adb server everytime I use adb?
Click to expand...
Click to collapse
you shouldnt.
Bump........
You shouldn't have to restart the server. When I switch between my phone and tablet, I just type adb devices to make sure its seeing the new device.
Sent from my SGH-I897 using Tapatalk
Related
I am keep getting this message whenever I try to adb. It corrects itself and works fine after. But it annoying waiting that additional few seconds... I didnt have this before. Any idea why I am getting it now?
what sdk version are you using? also have you gone to task manager and tried ending adb.exe?
david1171 said:
what sdk version are you using? also have you gone to task manager and tried ending adb.exe?
Click to expand...
Click to collapse
I am using the latest SDK. Thanks! That fixed it. Ending adb.exe in Task Manager... I was messing around cos I cant get fastboot to work. I go into FastbootUSB, connect my usb, run "fastboot devices", and I get no results. It just waits for my next command.
I tried killing adb.exe after I wrote an adb command and it didn't do anything. I keep getting that out out date killing .... can anyone help? thanks!
I have the same problem. Can't get rid of that stupid message.
i was having the same problem, i took ADB.exe and adbwinapi.dll from 1.5r2 SDK and put it in the new SDK Tools folder, problem was fixed
palosjr said:
i was having the same problem, i took ADB.exe and adbwinapi.dll from 1.5r2 SDK and put it in the new SDK Tools folder, problem was fixed
Click to expand...
Click to collapse
I did that and still have that problem ...
could someone please help me .. thanks!
If anyone runs into this problem I fixed mine with the adb.exe from the new "universal" sdk. I downloaded it and just pasted that adb.exe into the existing tools folder. May not be recommended but I did not want to change my setup.
while your phone is in recovery and plugged in, go to device manager and see if there is a listing called adb interface. if so, do you know how to manually update the drivers? by pointing the driver update to the usb folder of the sdk?
konzern
running my adb shell ums_enable is no longer working says ums not found ?
edit to m y post i found a alternative thank god!
1.plug in your phone and open command prompt
2.change directories to where u have ur sdk stuff (ex. cd c:\thenameofdirectory/tools)
3.type this in
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
I am curious if any of you loaded Droid Explorer? I loaded it, played around with it, and it was pretty cool for the screenshot and screencast stuff. But, later I noticed I kept getting the "adb server is out of date. killing..." I searched through these threads and Google for a solution, but nothing seemed to work. I could enter "adb remount" and it might work about 1 time in 5. Even adb devices would fail and fail before finally reporting my device. After I uninstalled Droid Explorer. The problem stopped immediately. Now that I think about it, I think Droid Explorer runs a service. Maybe after uninstalling, the services stopped, fixing this problem. If not Droid Explorer, maybe some other program that is trying to detect the device at plugin. Just my experience.
I just killed the DroidExplorer service, and set it to manual. Problem solved.
I've had no luck with DE anyhow, so it probably won't get started again any time soon.
_zygo_ said:
I am curious if any of you loaded Droid Explorer? I loaded it, played around with it, and it was pretty cool for the screenshot and screencast stuff. But, later I noticed I kept getting the "adb server is out of date. killing..." I searched through these threads and Google for a solution, but nothing seemed to work. I could enter "adb remount" and it might work about 1 time in 5. Even adb devices would fail and fail before finally reporting my device. After I uninstalled Droid Explorer. The problem stopped immediately. Now that I think about it, I think Droid Explorer runs a service. Maybe after uninstalling, the services stopped, fixing this problem. If not Droid Explorer, maybe some other program that is trying to detect the device at plugin. Just my experience.
Click to expand...
Click to collapse
Yes, this is a problem that occurs after installing Droid Explorer. The service also takes a lot of idle CPU time. I have uninstalled it due to this and other reasons.
Damn, Droid Explorer! I uninstalled and I am still having this problem. Damn !
OK, I got droid explorer and adb playing nice together. I deleted the SDK from my PC, and reinstalled droid explorer full (which comes with the SDK already). Then I just added the new tools directory droid explorer installs to the system path. You can find directions on how to do that here -> http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec02 . Instead of using C:\AndriodSDK\Tools\ for the string I added, I used the default location where droid explorer installs the tools directory ( C:\Program Files\Droid Explorer\SDK\tools ). Now I have the best of both worlds !
lotherius said:
Yes, this is a problem that occurs after installing Droid Explorer. The service also takes a lot of idle CPU time. I have uninstalled it due to this and other reasons.
Click to expand...
Click to collapse
I also noticed I was getting the blue screen of death, which I hadn't seen in years. I think DE was causing that, too, because I haven't had the BSOD since uninstall. So two problems I didn't think were related seem to have been caused by Droid Explorer. I think it's a pretty cool program, but I'd rather do things the "old fashioned" way.
Can any of you point me in the direction of how to use ADB to take a screenshot? Maybe it can't. Thanks.
Edit: I found it...Through DDMS!
sacredsoul said:
I am keep getting this message whenever I try to adb. It corrects itself and works fine after. But it annoying waiting that additional few seconds... I didnt have this before. Any idea why I am getting it now?
Click to expand...
Click to collapse
Sounds like you have droid explorer installed, goto the sdk folder in droid explorer (c:\program files\droid explorer\sdk) copy the 2 folders (platform and tools) to your own sdk folder.
billquinn1 said:
If anyone runs into this problem I fixed mine with the adb.exe from the new "universal" sdk. I downloaded it and just pasted that adb.exe into the existing tools folder. May not be recommended but I did not want to change my setup.
Click to expand...
Click to collapse
Can you link to the "universal" download please? Probably missing something obvious here, but can't seem to find any other version than the most recent r05.
Thank you - worked a treat
palosjr said:
i was having the same problem, i took ADB.exe and adbwinapi.dll from 1.5r2 SDK and put it in the new SDK Tools folder, problem was fixed
Click to expand...
Click to collapse
where can i get 1.5r2 SDK?
THX BRO!
I have the one click root on my computer. I was able to root stock 2.1 but not Froyo. I cant seem to get a normal Update.zip to reinstall to root it. Can anyone help me out with this? Thank you
Have you used adb before? Its easy. Just need to get the sdk dev kit. Then go here.
http://forum.xda-developers.com/showthread.php?t=797397
smokestack76 said:
Have you used adb before? Its easy. Just need to get the sdk dev kit. Then go here.
http://forum.xda-developers.com/showthread.php?t=797397
Click to expand...
Click to collapse
I never have. But Im to nervous to attempt it bud lol
Its not hard. You can PM me if you want. Its easier than all the flashing to swap Kernels i think.
smokestack76 said:
Its not hard. You can PM me if you want. Its easier than all the flashing to swap Kernels i think.
Click to expand...
Click to collapse
+1 Its easier to cut and paste between windows. I also like to see how adb commands are used.
Terrigno said:
I never have. But Im to nervous to attempt it bud lol
Click to expand...
Click to collapse
If you're comfortable with flashing Froyo using adb shouldn't be a problem.
cappysw10 said:
If you're comfortable with flashing Froyo using adb shouldn't be a problem.
Click to expand...
Click to collapse
I sent smokestack a PM to see if he can help me out on how to do it. I just flashed the phone with Froyo following the directions here. I wasnt to sure about what I was doing but I did everything and it all eventually worked out well, with a couple scares lol. Im new to the rooting scene. I mean Im pretty savy when it comes to certain stuff and I was easy to install beta leaks and builds with BlackBerrys for 3 years. Im new to Android since the Captivate came out, so Im slowly trying to learn the tricks of the trade
Terrigno said:
I sent smokestack a PM to see if he can help me out on how to do it. I just flashed the phone with Froyo following the directions here. I wasnt to sure about what I was doing but I did everything and it all eventually worked out well, with a couple scares lol. Im new to the rooting scene. I mean Im pretty savy when it comes to certain stuff and I was easy to install beta leaks and builds with BlackBerrys for 3 years. Im new to Android since the Captivate came out, so Im slowly trying to learn the tricks of the trade
Click to expand...
Click to collapse
Sent you a reply as well.
I was wondering if someone was also willing to help me, the instructions on the link are kinda of vague I think
we are working on it
Seems that adb does not like Win7. Anyone else see issues?
smokestack76 said:
Seems that adb does not like Win7. Anyone else see issues?
Click to expand...
Click to collapse
nope. been working fine on mine since July....i have it on 3 machines all running win7 64bit ultimate
alme1304 said:
I was wondering if someone was also willing to help me, the instructions on the link are kinda of vague I think
Click to expand...
Click to collapse
The instructions seemed clear as day to me. Put the phone in debug mode, use adb to push the files, execute a shell script, use sqlite3 to allow side loading, change permissions on the files you pushed, and reboot.
Sent from my SAMSUNG-SGH-I897 using XDA App
rajendra82 said:
The instructions seemed clear as day to me. Put the phone in debug mode, use adb to push the files, execute a shell script, use sqlite3 to allow side loading, change permissions on the files you pushed, and reboot.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
you are forgetting one important step that nobody seems to want to do.
learn what all that means
its a gimme gimme gimme world....gimme now, i dont want to understand it! just do it for me!
Pirateghost said:
you are forgetting one important step that nobody seems to want to do.
learn what all that means
its a gimme gimme gimme world....gimme now, i dont want to understand it! just do it for me!
Click to expand...
Click to collapse
Kinda. Seems the OP here has win7 and i cant get it to play right. I see the above poster said they have it. Please post some info
rajendra82 said:
The instructions seemed clear as day to me. Put the phone in debug mode, use adb to push the files, execute a shell script, use sqlite3 to allow side loading, change permissions on the files you pushed, and reboot.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I think what they are looking for is where to put the files that they download. I know in the rooting tread, it was missing. I also think some people do it differently, so it may help just to let them know how you find it easiest to navigate to them, etc.
Personally, I take the files that were downloaded and extract them all. Then make sure you have downloaded the android SDK program and put it on the root of your computers hard drive such as drive C:. Then add those files you downloaded to the "Tools" file within sdk.
To navigate to them with command prompt, it would look like: cd C:\android-sdk-windows\tools
Then run the commands as listed in the tread.
Hope this helps.
Perhaps this is not the answer you are looking for, but if you are comfortable flashing roms, flash Cognition 2.2 (its already rooted).
Good luck
ronandi said:
Perhaps this is not the answer you are looking for, but if you are comfortable flashing roms, flash Cognition 2.2 (its already rooted).
Good luck
Click to expand...
Click to collapse
Its funny all the n00b post. I guess i dont know what im doing
Gr8Danes said:
I think what they are looking for is where to put the files that they download. I know in the rooting tread, it was missing. I also think some people do it differently, so it may help just to let them know how you find it easiest to navigate to them, etc.
Personally, I take the files that were downloaded and extract them all. Then make sure you have downloaded the android SDK program and put it on the root of your computers hard drive such as drive C:. Then add those files you downloaded to the "Tools" file within sdk.
To navigate to them with command prompt, it would look like: cd C:\android-sdk-windows\tools
Then run the commands as listed in the tread.
Hope this helps.
Click to expand...
Click to collapse
I'm running W7 and am having issues with adb. I'm a noob to android but I'm learning. Anyway, I tried your suggestion of adding the files to the tools directory but when I enter "su" the system returns "su: not found". Any help?
Moved to Q&A.
Ok so this started out as a small project to make my day to day phone functions easier and quicker but I thought I might share it incase anyone thought my AdbTool was helpful or just nice to have.
Functions so far:
1. Check for device
2. Push or Pull a File
3. Install .apk
4. Reboot
5. Root your Droid X
6. Change bootanimation
7. Push framework (specifically for framework)
8. issue whatever adb command you need to with out the extra typing
9. Set project
10. Error log
11. Clean up folder
There are more functions to come in the future so let me know if you like this script and what you wanna see added. There is no install just unzip and open the .bat file.
This sounds great! Though I'm on Linux machine, so I don't think ill be able to use it :/
Sent from my DROIDX using XDA App
No sorry, I should have specified. It is a Windows script... Just wait though, because Sunday I will be getting a desktop that is already running linux. If you really want I will take the time to make a script to run for linux?
Sent from my DROIDX using XDA App
rooting the dx doesnt work for me :/
Huh... what is happening when you enter that option? Sorry for the long time for me to post I missed the email alert.
Sent from my DROIDX using XDA App
I'm assuming this doesnt allow root for 2.3.3 ota correct?
since all I see is rageagainstthecage in the files
This looks like a really useful program! I might do some work this weekend on it and see if I can get it working for the DROID 2 and port it over to UNIX machines.
If I set it up for unix I will add an SBF option too.
Woa just realized this is a really old thread
ljbaumer said:
This looks like a really useful program! I might do some work this weekend on it and see if I can get it working for the DROID 2 and port it over to UNIX machines.
If I set it up for unix I will add an SBF option too.
Woa just realized this is a really old thread
Click to expand...
Click to collapse
Yeah, this thread is quite old (almost a year) and I am sure the program/script needs to be updated to work.
It is a good idea though (if it can be updated)
D.
I'd like to make a request for a Mount and UnMount command.
fyi....you spelled Folders wrong in the main menu "Floders"
.
I can make the program for yall. Yall just need something for shell or a gui for windows?
whatever's easier for you, either would be appreciated it
i have adb properly installed by doing adb devices in cmd it shows my dx
but when i use your tool it says it cannot find the path specific
Hey everyone, I've been following the Honeycomb developments on the nook, but havent posted yet. I just got my nook this weekend and immediately installed deeper blue's Honeycomb ROM on the SD card without rooting my nook.
It is great and he deserves all the praise in the world, but unfortunately does not have a ton of use to me without being able to download items from the market.
I'm not very experienced in programing in general or using the android sdk or adb.
I tried installing the market using the instructions in the following places:
w w w.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
w w w.addictivetips.com/mobile/install-android-3-0-honeycomb-and-market-on-nook-color/
After 2+ hours of frustration, I was finally able to get my device recognized in the command prompt using "adb devices" or something like that.
However, when I copied and pasted the commands, the command prompt text just scrolled and then the command prompt closed all together.
Alas, there was no market on my honeycombed nook.
Any ideas where I could have been going wrong?
I could really use an extremely basic step-by-step here.
Unfortunately, I wont be able to test anything until I get home from work later tonight.
Thanks in advance for any ideas or tips.
http://forum.xda-developers.com/showthread.php?t=937752
forsaken82 said:
http://forum.xda-developers.com/showthread.php?t=937752
Click to expand...
Click to collapse
I saw that, but didnt know if it was the same thing I was looking for. I dont remember if I tried it or not.
Is it just as simple as it sounds? What directory exactly do I extract it in? The platform-tools folder?
Then just double click that one file and it should automatically install the market on my device?
Are there any prereqs? Like I said in my original post, I THINK i got my device recognized in the command prompt, as it gave me a serial number in the response.
Sorry for the noob questions, but I am truly unexperienced.
Yup. It makes the files pushable. From there just copy paste his code
Sent from the honeynook pad
n4m347yp3 said:
Yup. It makes the files pushable. From there just copy paste his code
Sent from the honeynook pad
Click to expand...
Click to collapse
Im actually typing from my honeynook now.
The script worked like a charm and i now have gmail, market, etc.
Thanks everyone!
pman555 said:
Hey everyone, I've been following the Honeycomb developments on the nook, but havent posted yet. I just got my nook this weekend and immediately installed deeper blue's Honeycomb ROM on the SD card without rooting my nook.
It is great and he deserves all the praise in the world, but unfortunately does not have a ton of use to me without being able to download items from the market.
I'm not very experienced in programing in general or using the android sdk or adb.
I tried installing the market using the instructions in the following places:
w w w.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
w w w.addictivetips.com/mobile/install-android-3-0-honeycomb-and-market-on-nook-color/
After 2+ hours of frustration, I was finally able to get my device recognized in the command prompt using "adb devices" or something like that.
However, when I copied and pasted the commands, the command prompt text just scrolled and then the command prompt closed all together.
Alas, there was no market on my honeycombed nook.
Any ideas where I could have been going wrong?
I could really use an extremely basic step-by-step here.
Unfortunately, I wont be able to test anything until I get home from work later tonight.
Thanks in advance for any ideas or tips.
Click to expand...
Click to collapse
Hello,
I am the Mobile Technology Editor at AddictiveTips and both the guides that you quoted here were written by my writers and heavily edited by me. The issue lied in you not following one crucial step of the ADB guide - it seems you didn't add the tools and platform-tools folders of your SDK installation to your computer's PATH variable as outlined in that guide.
Doing that basically makes things a lot easier as you don't have to copy files for any such hacks or tricks into the tools or platform-tools folder of ADB and it keeps those folders clean, containing only the default tools files. It also eliminates the risk of you deleting any of those essential files when you are done with your customization and delete the files that you pasted there earlier.
The script you used was awesome as well...jleecong has done an excellent job at putting it together and I will update my guide to include it. Just like you, I've also got to thank forsaken82 for bringing it to my attention as while the guide I featured does install Market, enabling you to install the rest yourself...this one installs some other useful apps for you directly too. =)
HQRaja said:
Hello,
I am the Mobile Technology Editor at AddictiveTips and both the guides that you quoted here were written by my writers and heavily edited by me. The issue lied in you not following one crucial step of the ADB guide - it seems you didn't add the tools and platform-tools folders of your SDK installation to your computer's PATH variable as outlined in that guide.
Doing that basically makes things a lot easier as you don't have to copy files for any such hacks or tricks into the tools or platform-tools folder of ADB and it keeps those folders clean, containing only the default tools files and eliminates the risk of you deleting any of those essential files when you are done with your customization and delete the files that you pasted there earlier.
Click to expand...
Click to collapse
Thank you for your reply, but I have already figured everything out using a script.
I actually did add the tools and platform-tools folders to the PATH variable though.
Either way, the issue has been resolved.
pman555 said:
Thank you for your reply, but I have already figured everything out using a script.
I actually did add the tools and platform-tools folders to the PATH variable though.
Either way, the issue has been resolved.
Click to expand...
Click to collapse
It should definitely work if you added those folders to the PATH variable correctly - it has been tested by many users to work successfully. I am now curious on what sort of error you received but most likely you wouldn't have saved the output from those commands. In any case, as long as you got it working, it's all good. =)
EDIT: Just out of curiosity...did you copy and paste the commands there all together or did you enter them one by one?
Well to get a long story short,im not a complete noob in the rooting,optimising,flashing bussiness.
So dont tell me flash this kernel or this stock rom,or this or that.
The problem after hours of searching is a bad app.
I have bought over 500 apps cause i want to support the community.
So,when i restore all my apps,when the phone starts,after the home screen loads AT THE MOMENT WHERE IN TOUCHWIZ OR ADW OR WHATEVER THE APPS ARE FINALLY LOADED
REBOOT,hot reboot most of the times...
I tried everything...startup managers to block everything and i mean everything...
Rescan media root app to stop scanning of sdcard...
Everything,no matter if it froyo,ginger,ics,stock,rooted or WHATEVER.
Of course i can install one app at a time an reboot,to see what happens but that will take ages and also maybe one app 'hit' with another...
So help me find the bad app...
I am no noob but i am no pro either...
So how do i take a logcat? Will that help either way?
Do i have to use adb?
help....
You are kidding right? You have 500 apps installed at the same time? Why on Earth? I think you are lucky the phone even tries to boot...
On to your problem at hand - no one here will be able to help you with the info you provided.
I thought their was like a 30 app limit to android?
Adb is your best bet.
Sent from my HD2 using xda premium
kylew1212 said:
I thought their was like a 30 app limit to android?
Adb is your best bet.
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
Yes,i have so many apps and i want to find which app 'collides' with another or at least which app causes problems.
I used logcat with semaphore kernel and i have taken out some txt files just before the soft reboots...
How adb will help me.
I will find how to install adb but what then?
What command should i use?
And the phoen will be open?In recovery? What?
Please help....
karapoutsoglou said:
Yes,i have so many apps and i want to find which app 'collides' with another or at least which app causes problems.
I used logcat with semaphore kernel and i have taken out some txt files just before the soft reboots...
How adb will help me.
I will find how to install adb but what then?
What command should i use?
And the phoen will be open?In recovery? What?
Please help....
Click to expand...
Click to collapse
Well you certainly need apps 2 SD ... but you probably already have that.
To use adb, download it firstly. Its in the Google developer tools.
Once downloaded open terminal. Alt+ctrl+t. Use CD to change to the directory that contains adb in the platform tools. Once your in the folder containing adb, type "./adb logcat" without the quotes. This is for a computer running Ubuntu Linux also
Sent from my HD2 using xda premium
kylew1212 said:
Well you certainly need apps 2 SD ... but you probably already have that.
To use adb, download it firstly. Its in the Google developer tools.
Once downloaded open terminal. Alt+ctrl+t. Use CD to change to the directory that contains adb in the platform tools. Once your in the folder containing adb, type "./adb logcat" without the quotes. This is for a computer running Ubuntu Linux also
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
thanx for the response.
i have set adb succesfully and i see the logcat on my cmd window running like hell most of the time.
i read that you can use some commands like -w -e etc to narrow the results to important messages? is that correct?
if yes,how you can do that? i mean the full command adb logcat....etc
thanx in advance
karapoutsoglou said:
thanx for the response.
i have set adb succesfully and i see the logcat on my cmd window running like hell most of the time.
i read that you can use some commands like -w -e etc to narrow the results to important messages? is that correct?
if yes,how you can do that? i mean the full command adb logcat....etc
thanx in advance
Click to expand...
Click to collapse
Unfortunately I have very little adb experience...
Maybe try something like the same command you used
"./adb logcat"
I guess going by what you're saying you could try something like
"./adb logcat -w" try that then maybe replace the w with e..
Keep in mind these are just guesses because I do not know for certain
I will research as soon as possible and write a quide for it as this can benefit lots of people
Sent from my HD2 using xda premium
kylew1212 said:
I will research as soon as possible and write a quide for it as this can benefit lots of people
Click to expand...
Click to collapse
thanx.
i had the same in mind.maybe something good can come out of this
Another way would be using ddms - connect your phone in debug and run ddms (it's included in the SDK Tools). It provides an interface to browse your device's logs and filter them according to your needs. I think you'll be able to locate that one which explains why your phone is crashing.
On second thought however - is it possible for you to turn the debug on?
avltree said:
Another way would be using ddms - connect your phone in debug and run ddms (it's included in the SDK Tools). It provides an interface to browse your device's logs and filter them according to your needs. I think you'll be able to locate that one which explains why your phone is crashing.
On second thought however - is it possible for you to turn the debug on?
Click to expand...
Click to collapse
thank you!
great idea,i will test it
yes,i can turn the debug on,because the phone crashes just when all the apps are loaded in the drawer.
it must be a bad app because i used to have many apps since froyo times and no problem.
like 500...and the phone was fast.
i really want to find that bad app and kill it
edit
================================
wow,ddms is a dream! thats what i was looking for!!!
thank you
Sorry for the double post but i thought it needed a single post.
Well,the problem is fixed with the help of you guys!!!
I was getting a hell lot of warnings about watchdog_n and stuff.
I googled it and appeared that a whole bunch of people had the same problem especially with nexus s etc.
They said it was due to some crappy app wanting to auto-sync.
So i did a wipe cache,wipe dalvik cache,fix fc and then when the phone rebooted i disabled the auto-sync.
Guess what,no more loops and soft reboots!!!
I still dont know what app is causing all the problems and propably never will,if you thing that the same apps in my tablet dont cause a thing,but after the auto-sync off the problem is gone.
Good thing though i dont need auto-sync cause its not the best solution...