I compiled kernel, has been able to compile. But the brush to the mobile phone can't boot, black screen. How to debug? If there is no development board can see the kernel boot messages?
smallcsduck said:
I compiled kernel, has been able to compile. But the brush to the mobile phone can't boot, black screen. How to debug? If there is no development board can see the kernel boot messages?
Click to expand...
Click to collapse
try logcat kernel
adb shell dmesg
Check this out! Links to useful Guides and " Banned " Documentarieshttp://forum.xda-developers.com/showpost.php?p=44762570&postcount=7
xsenman said:
try logcat kernel
adb shell dmesg
Check this out! Links to useful Guides and " Banned " Documentarieshttp://forum.xda-developers.com/showpost.php?p=44762570&postcount=7
Click to expand...
Click to collapse
Phone on the computer, the computer can find the phone. But adb device couldn't find the equipment. This can use adb shell dmesg?
There was no kernel to boot up?
Related
I guess this is a general question, not dev specific, so I'll post it here. I hope some people are using Linux:
Ok so something is wrong with my USB driver setup in android SDk.
I'm using Ubuntu Jaunty x64, and followed the steps here:
http://developer.android.com/guide/...ing/device.html
Everything was Ok last week.
Today, the device is not recognized:
Code:
[email protected]:~/android-sdk-linux_x86-1.5_r3/tools$ ./adb devices
List of devices attached
I can fastboot a recovery ROM just fine:
Code:
[email protected]:~/android-sdk-linux_x86-1.5_r3/tools$ ./fastboot boot recovery-RAv1.2.1H.img
downloading 'boot.img'...
OKAY booting...
And in fastboot mode:
Code:
[email protected]:~/android-sdk-linux_x86-1.5_r3/tools$ ./fastboot devices HT95RNK02763 fastboot
Any ideas? This is preventing me from remounting the system in write mode.
Try using sudo before your adb commands and it should work, the problem is to do with the unprivileged user not having access to the hardware.
You can fix it permently by telling udev about the device, see this thread for details.
http://www.anddev.org/viewtopic.php?p=21753
Nice to see some other Ubuntu users on the forum!
sdk problem
Hey sorry to bug guys. Since u guys have the sdk working already i figured to ask. How did u get the enviormental path changed? I cant get it to work for the life of me. Im using linux mint 7.1. I got it to work on ubuntu 9.04 but mint is making me grrr. Thanks!
rockin_mod said:
Hey sorry to bug guys. Since u guys have the sdk working already i figured to ask. How did u get the enviormental path changed? I cant get it to work for the life of me. Im using linux mint 7.1. I got it to work on ubuntu 9.04 but mint is making me grrr. Thanks!
Click to expand...
Click to collapse
You should just be able to add it to .bashrc. I read somewhere that adding it to .bash_profile works.
rockin_mod said:
Hey sorry to bug guys. Since u guys have the sdk working already i figured to ask. How did u get the enviormental path changed? I cant get it to work for the life of me. Im using linux mint 7.1. I got it to work on ubuntu 9.04 but mint is making me grrr. Thanks!
Click to expand...
Click to collapse
I never bothered changing the environment path. Just cd in to the tools directory, and start your commands with ./
Code:
./fastboot boot recovery.img
Add a line at the end of ~/.bashrc that points to directory containing fastboot, adb, etc.
For example mine is /home/ben/androidsdk/tools and the path statement is:
export PATH=$PATH:~ben/androidsdk/tools
I'm trying to start busybox's httpd at boot w/o success. However, I can start it manually post-boot w/o problems. Can I enable a syslog facility so I can see what happens when the bootup script calls it?
Code:
httpd -p 80 -u 80 -h /sdcard/www -c /etc/httpd.conf
I've tried running the process as -u 80 and as -u 0, both work post-boot, not before.
It's Linux - if there is an rc.local you should be able to drop a string in there to make it start.
KaiserLinux said:
It's Linux - if there is an rc.local you should be able to drop a string in there to make it start.
Click to expand...
Click to collapse
Not that simple
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Go into applications and turn on debugging mode. Plug your phone into your computer and run 'adb logcat' or something to that effect. You can play around with your phone and watch the log scroll by.
Your gonna need the whole ADB setup. Go to the samsung epic 4G wiki and check the article about getting root and flashing a new kernel. This will have the instructions for getting ADB on your system as well.
KaiserLinux said:
Go into applications and turn on debugging mode. Plug your phone into your computer and run 'adb logcat' or something to that effect. You can play around with your phone and watch the log scroll by.
Your gonna need the whole ADB setup. Go to the samsung epic 4G wiki and check the article about getting root and flashing a new kernel. This will have the instructions for getting ADB on your system as well.
Click to expand...
Click to collapse
I've compiled my own rooted kernel and a new busybox with syslogd to see if I can diagnose why bb's httpd isn't starting at boot. As I mentioned, it starts manually w/o a problem. adb logcat isn't very useful in this particular situation. Thanks for the reply though.
jocala said:
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Click to expand...
Click to collapse
I'm kind of a noob myself, but I recall reading that init.rc isn't really a shell script. It has a special syntax that is parsed by Android init, I'm not sure just throwing shell commands in there is going to work. I'd post a link to the doc but I can't post links yet
coldguy said:
I'm kind of a noob myself, but I recall reading that init.rc isn't really a shell script. It has a special syntax that is parsed by Android init, I'm not sure just throwing shell commands in there is going to work. I'd post a link to the doc but I can't post links yet
Click to expand...
Click to collapse
Weird, the first 500 lines of init.rc are nothing BUT shell commands.
i.e. chmod 0666 /dev/input/event0
Anyway, further along in init.rc the daemon processes are started up. syntax looks like:
Code:
service playlogo /system/bin/playlogo
user root
oneshot
I've tried setting up my programs (httpd,syslogd) as services, no joy.
jocala said:
Not that simple
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Click to expand...
Click to collapse
sorry to hijack your post.
but i want to know how do you modify the /init.rc,
because when i reboot, the /init.rc will automatic recovery the old verison.
did you check the /init.rc, is it modified, after your phone reboot?
Does logcat not give you the info you want?
You can go here to find out how to redirect stdout and stderr to the logcat as well.
init.rc is part of the root fs, which is compiled into the kernel. So, a custom kernel is required. Search for custom kernel for details.
Hi, do you know? How can i connect adb drivers and ideos x5 on xp?
I did try some drivers but in device manager, in other device "android" but all drivers not runing. I want to runing on sdk and sent log dzo.
thanks for helps,
miskiab said:
Hi, do you know? How can i connect adb drivers and ideos x5 on xp?
I did try some drivers but in device manager, in other device "android" but all drivers not runing. I want to runing on sdk and sent log dzo.
thanks for helps,
Click to expand...
Click to collapse
you have to use the adb drivers for ics, now I have the link here. But you can report an error like this:
(1) Open the Terminal Emulator
Write to SU and Enter.
(2) Write the following commands:
cat /proc/kmsg > /sdcard/dmesg.log
logcat > /sdcard/CAT.log
Aurora ICS ADB drivers: http://forum.xda-developers.com/showthread.php?t=1566393
I just it but not solved this problem
asm19 said:
Aurora ICS ADB drivers: http://forum.xda-developers.com/showthread.php?t=1566393
Click to expand...
Click to collapse
hi, thanks for answered my question. But i just tried:
AndroidDriverForPc
Adb Device for AURORA
Huawei_U8800_ICS_ADB_Driver
usb_dirver4
Universal_Naked_Driver_Beta_0.6.2
and orjinal huawei drivers with hisuite.
How can i did it?
asm19 said:
you have to use the adb drivers for ics, now I have the link here. But you can report an error like this:
(1) Open the Terminal Emulator
Write to SU and Enter.
(2) Write the following commands:
cat /proc/kmsg > /sdcard/dmesg.log
logcat > /sdcard/CAT.log
Click to expand...
Click to collapse
edit// "you have to use the adb drivers for ics" I don't have adb drivers. Just i wanting it.
I think this commands for linux, right? Can i it any linux version?
i using this commands what will happen? ( i want learn)
thanks.
any idea?
Is there no one with a different suggestion?
Please give a try to this solution.
m!xal!s said:
Please give a try to this solution.
Click to expand...
Click to collapse
Yes, its ok, adb driver seen by xp but when i can adb shell;
* deamon not runing. starting it now *
* deamon started successfully *
error: device not found
writing, what can i for it?
strange problem!!
device not found
"You can identify you CPU chip by below command in terminal.
adb shell dmesg | grep PVS"
my device shows an error
"error: device not found"
i am currently on franco.kernel and i wanted to know if my CPU chip is fast or slow using the above command posted on http://forum.xda-developers.com/showthread.php?t=2048739 but it only shows the above error. can someone please explain me why am i getting that error?
thanks in advance
dannaoj said:
"You can identify you CPU chip by below command in terminal.
adb shell dmesg | grep PVS"
my device shows an error
"error: device not found"
i am currently on franco.kernel and i wanted to know if my CPU chip is fast or slow using the above command posted on http://forum.xda-developers.com/showthread.php?t=2048739 but it only shows the above error. can someone please explain me why am i getting that error?
thanks in advance
Click to expand...
Click to collapse
"error: device not found" is pretty self-explanatory. Your device isn't communicating with your computer. Make sure USB debugging is on and you have the correct drivers.
smacksa said:
"error: device not found" is pretty self-explanatory. Your device isn't communicating with your computer. Make sure USB debugging is on and you have the correct drivers.
Click to expand...
Click to collapse
i am using the terminal emulator and i have the USB debugging on
Ah, ok. You can just drop the "adb shell" part and it should work. That leaves you with "dmesg | grep PVS". You will need root access to do it from inside the OS so if you are rooted type "su" and hit enter (granting permissions if you haven't done so before) before using the command.
Hi everybody. I wanted to logcat an app but didn't get any tutorials, guides, etc. So would you please tell me how to do that or if there are any guides then please provide a link. TIA for the same.
sameer.n.soni said:
Hi everybody. I wanted to logcat an app but didn't get any tutorials, guides, etc. So would you please tell me how to do that or if there are any guides then please provide a link. TIA for the same.
Click to expand...
Click to collapse
best thing for this is just type in google how to adb logcat
see
http://forum.xda-developers.com/showthread.php?t=2141817
in adb type
Code:
adb logcat -v long > logcat.txt
then run the app you want to logcat on your phone
once done press cntrl c and the logcat.txt will be at your adb location - read the thread for full instructions for adb
marcussmith2626 said:
best thing for this is just type in google how to adb logcat
see
http://forum.xda-developers.com/showthread.php?t=2141817
in adb type
Code:
adb logcat -v long > logcat.txt
then run the app you want to logcat on your phone
once done press cntrl c and the logcat.txt will be at your adb location - read the thread for full instructions for adb
Click to expand...
Click to collapse
Sir how can I open Media Scanner?
sameer.n.soni said:
Sir how can I open Media Scanner?
Click to expand...
Click to collapse
there is an app in the play store that you can use to invoke a media scan - it will work on all stock roms
https://play.google.com/store/apps/details?id=com.addz.mediascanner&hl=en_GB
cm roms are different and will probably not work