Anyone know the exact name of the file as it sits on our phone? I made the mistake of overclocking too high, and now I am unable to make the changes to the application. It crashes right away. I'd like to remove using adb command.
Mine is listed as /data/app/com.mhuang.overclocking-2.apk
You can get a file directory list in adb by just using command ls after you move into that folder.
Thanks guys. Got it. Won't make that mistake again.
I'm trying to add a custom boot animation with sound, but I can't figure out if this is possible with the galaxy nexus.
I followed this tutorial:
http://forum.xda-developers.com/showthread.php?t=1096068
I can get the boot animation to load, however, when I try to run the script for adding the sound (sh bootsnd.sh) I get this:
bootsnd.sh[14]: grep: not found
No such user 'root:shell
So yea, I'm not even sure that it's possible. Any suggestions?
Had same issue. I closed out the terminal emulator window. Reopened typed in "su root" then closed out of that terminal emulator window. Reopened and ran all the other commands from the tutorial you followed. All the files were created specified in the bootsnd.sh and update to build.prop was successful too. I even have the android_audio.mp3 in the right spot...still no sound. I might try deleting the created files and editing build.prop back. I wonder if it will work if I change the .mp3 to .ogg on the file and in the reference to the file? Everything else seems to be in .ogg .
Ran bootsnd.sh with no errors.
I was able to fix the grep error by installing busybox. To fix the root:shell error I modified the the script to run root.shell instead. Of course I manually undid the script creations and edits before I ran bootsnd.sh a second time. Even though I ran with no errors I still can not get sound at boot up. I have put the android_audio.mp3 file in system/media. I even edited the script and converted the audio file to reflect .ogg. Still no luck. I believe one cause is that there is no stagefright command file on the phone. ( the bootsnd.sh script calls this function) Obviously bootsnd.sh wasn't written for ICS. I wonder if HoneyComb had this same issue? Searching for a fix to Honeycomb boot sound now to see if it might work for ICS.
Hello,
I am trying to develop an app for my Samsung Galaxy Nexus but I have problem with the logcat :
?:??: W/?(?): Unable to open log device '/dev/log/main': No such file or directory
I think it's deactivated in the Glados Kernel which I use, so if somebody know how to enable it without change of kernel, it would be very helpful.
Thanks in advance,
Just load the logger kernel module
Create a file called "98logcat" or similar in /system/etc/init.d with contents
Code:
#!/system/bin/sh
insmod /system/modules/logger.ko
Thanks for your answer.
You made just a small mistake. It's :
Code:
insmod /system/modules/logger.ko
I see the logcat of my device but I can't see the log of my app. When I do a Log.i("Msg", "Msg") for example, nothing appear in the logcat and I have this message at the launch of my app :
03-13 20:09:23.988: I/AndroidRuntime(3357): NOTE: attach of thread 'Binder Thread #3' failed
Unless it was introduced with that kernel, there is no /system/modules.
OP, check system/etc/init.d for a script.
See if it contains:
rm /dev/log/main
If it does, comment it out or remove it, save, and reboot your device.
benoitm76 said:
Thanks for your answer.
You made just a small mistake. It's :
Code:
insmod /system/modules/logger.ko
I see the logcat of my device but I can't see the log of my app. When I do a Log.i("Msg", "Msg") for example, nothing appear in the logcat and I have this message at the launch of my app :
03-13 20:09:23.988: I/AndroidRuntime(3357): NOTE: attach of thread 'Binder Thread #3' failed
Click to expand...
Click to collapse
Ah, sorry, made a typo there.
Hmm, my logcat seems to show messages from my installed apps fine. I suppose this is a stupid question to ask since your logcat does work, which probably means the init.d script is running, but your permissions on your new init.d file are 755 root root, right?
If that isn't the problem, I have one more stupid guess to hazard: I think this is what a normal init.rc file is supposed to contain to run init.d scripts:
Code:
service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
class late_start
user root
group root
However, my init.rc mysteriously contains this instead:
Code:
service run_parts /system/xbin/run-parts /system/etc/init.d
class main
oneshot
Did you turn device encryption on? Might it be that the logcat module has to be loaded earlier in the boot process than when /data is decrypted (late_start services run only after the decryption, I think, unlike main, which run before that)?
Sorry if this isn't helpful. I googled and found a few others saying they faced your problem (no app messages), but no one ever posted that they'd found a solution. This difference in my init.rc (class main as opposed to class late_start) is the only difference I could think of that might be affecting this.
Problem solve.
@vincom2 : Your first method work good, I made just a little mistake when I created the file the first time.
Thanks for your help !
I've been trying to get logcat to work on my phone all day (AOKP M4 and GLaDOS 1.24) with very little luck. Creating /etc/init.d/98logger containing
Code:
#!/system/bin/sh
insmod /system/modules/logger.ko
doesn't seem to do anything. I reboot, the the module isn't loaded. Same behavior if I add it at the end of an existing init.d script.
Manually executing
Code:
insmod /system/modules/logger.ko
doesn't do me any good either... "lsmod" doesn't show any modules loaded.
Anyone have any ideas? I really like the performance and battery life of GLaDOS, but get really frustrated that I can't do something simple like pull a logcat.
I have a shell command that I manually type in terminal everytime my phone starts up. How can I make it automatically execute @ each boot? I've seen init.d scripts, but I'm currently on ICS and I don't believe the kernel I am on supports init.d scripts yet. Any other way without using an external app?
thanks..
Check my thread out in here,
http://forum.xda-developers.com/showthread.php?t=1610741
You can run any scripts during the boot.
HERE'S THE ANSWER!
Let's say the script is on the /sdcard and named 'script.sh'. The script would be run like so....
Code:
adb connect
adb shell su
cd /sdcard/
sh ./script.sh
@rbox
I've been searching for a guide to run .sh scripts on my Fire Stick Gen1. I've found a couple guides on how to auto run scripts on boot...but I want to simply run a script on demand. Particularly, I'm trying to run a few of the debloat scripts offered inside "esc0rtd3w" FirePwn Amazon FireTV Stick Loader located at... https://github.com/esc0rtd3w/firestick-loader
To run a script on demand. Do I need to have the script in a specific location on the Fire device? Do I need to set permissions for the script? Does it matter what file extension the script has? Does it need .sh at the end of the filename? I noticed the autoboot script guides DO NOT have .sh at the end of the filenames for the scripts its auto running at boot.
I also have another question...
I want to try out esc0rtd3w's FirePwn Amazon FireTV Stick Loader. I downloaded his entire github repo and open the 'autorun.cmd' but it doesn't recognize my device. Does anyone know how to successfully connect to the FireTV Stick Gen1 with his script? I've tried adb connecting to my device and then running his script but it still doesn't recognize my device. Has anyone successfully utilized this tool? If so, how did you get it to recognize your device? Because I haven't been able to utilize his windows script to automate the plethora of tasks it offers, it led me to seek how to run .sh scripts manually.
I still CANNOT for the life of me, figure out how to run a script on the Fire TV through ADB. I'm using terminal on Linux, directly connected to a FireTV Stick Gen 2 with full root. I can manually execute the commands in the script but I cannot execute the script(s)! So here's one of the scripts I'm trying to run... Script Could someone explain to me, how would I execute this script via ADB?
Edit: I solved my issue! The text needs to be in unix format!! I used dos2linux to fix all the scripts and they go without a hitch. So I put all the scripts into a folder. I right clicked on that folder and clicked open terminal. I then executed this code to batch convert all files in the folder to unix format.
Code:
find . -type f -print0 | xargs -0 dos2unix