Develop Bugs

[Q] Why isn't my Updater-Script working!!!!

Hey can someone take a look at this updater script and see why it keeps giving me a status 6 error when I try to flash. I made sure it was in UNIX format when usig notepad++ and I tried signing the whole .zip with no prevail. I had to attach as .txt

You made sure to take off the .txt right? Great question huh?
EDIT: Oh and I have no freaking idea.

darkierawr said:
You made sure to take off the .txt right? Great question huh?
EDIT: Oh and I have no freaking idea.
Click to expand...
Click to collapse
Yes I did it just wouldn't let me attach without it. And yeah I cannot for the life of me see why this isn't working... ughhhh!!!!

I can't see nothing either... hopefully someone with more knowledge than me comes along...
Sent from my SPH-D700 using Tapatalk

The_Legendary said:
Hey can someone take a look at this updater script and see why it keeps giving me a status 6 error when I try to flash. I made sure it was in UNIX format when usig notepad++ and I tried signing the whole .zip with no prevail. I had to attach as .txt
Click to expand...
Click to collapse
I just checked it out and, regardless of what you said, it's using Windows-style EOL characters, not UNIX-style EOL characters.
Check out my post that covers this extensively, including how to fix it, in benzyniarz1's [Tool][TLC]UpdatezipCreator topic, which you will probably find to be an interesting tool--especially now that he's fixed it to write UNIX-style EOL characters!

Ok well I kid of figured it out, I got the script running but it was an important chunk I took out. This line
assert(package_extract_file("modem/modem_delta_el30.bin", "/tmp/modem_delta.bin"),
write_firmware_image("/tmp/modem_delta.bin", "modem_delta.bin"),
delete("/tmp/modem_delta.bin"));
Click to expand...
Click to collapse
I also tried adding this line that was in the flashable modem zip
# ---- Flash the modem update ----
Click to expand...
Click to collapse
I tried this after the first line of ui_print and still a no go
# ---- Flash the modem update ----
(tried with and without a ui_print here)
assert(package_extract_file("modem/modem_delta_el30.bin", "/tmp/modem_delta.bin"),
write_firmware_image("/tmp/modem_delta.bin", "modem_delta.bin"),
delete("/tmp/modem_delta.bin"));
Click to expand...
Click to collapse
I tried placing it at the beginning and end but still status 6. I take the line out and POOF!! it magically works. Which is odd sense I got that line from the script in the flashable zip. But it doesn't play nice with any other syntax.

Is this for MTD?

[HOW TO][MOD] V6 SuperCharger Script

Hi all,
I own no credits to this mod/script, it's all put together by zeppelinrox, Thanks go out to him for this! Orginal thread can be found here.
http://forum.xda-developers.com/showthread.php?t=991276
This is the first post of this kind I have ever made, so it might not be that good, or any help at all, but for those who want to try this script for the first time, I shall try my very best to explain how to do so.
I had been running ROMS for my Nexus with the V6 SuperCharger built in, and decided to see if it'll run well on our humble little Tabs. And indeed it does, it could be a placebo of course, but I seem to notice a good difference.
First, there are a few requirements in order to use this script :-
You NEED to be Rooted, in order to do this (if you aren't already) you could try the excellent Quick and Easy Root Script by the genius Crossix http://forum.xda-developers.com/showthread.php?t=1472521
Download and Install Script Manager from the Market
https://market.android.com/details?id=os.tools.scriptmanager
You also need to have BusyBox installed for the script to be run, I suggest installing the Script attached to the above V6 SuperCharger thread (even if you already have BusyBox installed to avoid errors). Simply scroll to the bottom of the thread and download the file named "busybox_v1.19.3_installer_script_wraithdu.zip"
To install this version of BusyBox navigate to where you saved the ZIP file, if on the Tab it should have downloaded to "/mnt/sdcard/Download", extract it using your file manager, I use ES File Explorer. Then open Script Manager and navigate to the extracted folder, find the script that should be called "busybox_v1.19.3_installer_wraithdu.sh", open this and select the "su" icon, make sure it is selected as a script and not executable.
To Run the Script:-
Scroll to the bottom of the SuperCharger thread and Download the file named " V6_SuperCharger_for_Android-update8.sh.txt" Navigate to where this file is downloaded, if on the Tab it should have downloaded to "/mnt/sdcard/Download", rename it using your favourite file manager, usually via a long-press to "V6_SuperCharger_for_Android-update8.sh"
Then open Script Manager and navigate to the script, open it using script manager, again taking care to run it as "su" as a script not an executable. The script should Run and prompt you for an option numbered 1-17. I chose Option 2, which is Aggressive Level 2 and noticed a good improvement, you can of course opt for the balanced options of 3 or 4. To input a number touch the screen and the on screen keyboard should pop up, hit a number and enter it.
The Script Should run and then prompt you for another option, don't choose another one just yet.
If you are running the excellent build.prop by Crossix, Icewyng et al, it is recommended to disable the device keeping Launcher in memory for the script to run properly. To do this, open Root Explorer, navigate to the build.prop, in "/system", and open it in the text editor. Scroll to the part of the prop file that begins "store launcher in memory" and change the below string to "ro.HOME_APP_ADJ=0"
In order for this to be a persistent change to how RAM is managed on our Tabs, a script has to be set up to be run at boot. To do this, in Script Manager, navigate to "/data" and open the script named "99SuperCharger.sh", and check the boxes of "su" along with "boot" to run it at boot.
After you have followed these steps reboot your Tab and you *should* see a snappier Tab
Please be aware that this is the very first HOW TO I have ever written, and it will probably be inaccurate and crap. So, please, feel free to correct my errors and I will try to help running the script.
Yours,
Toyface

Awesome scripts. Im going to give it a try here in a bit and see if there is a difference in performance.

Could someone confirm if this really works?

I just did this and have notices an improvement but do follow instructions carefully
Sent from my A500 using xda premium

I can't download the update 8 sh.txt file it just opens it in my browser

I used taptalk to download it it worked great and is still working its magic
Sent from my A500 using xda premium

Super huge improvement. Thank you!

rando152 said:
I can't download the update 8 sh.txt file it just opens it in my browser
Click to expand...
Click to collapse
Which browser are you using? If chrome on the PC, try a right click and save as a txt file and rename it as a file ending .sh
Sent from my A500

Thanks for all the cool info. Using info I found in sin threads Skype seems to stay running for hours now instead of just 15 Minutes.
Sent from my modified A100 using Tapatalk and SlideIT keyboard.

so far so good.
Just had time to get this installed. So far it seems to be a bit snappier. Wish i had thought to benchmark first. Grrrr....

I think this should be in the dev section, I might ask to have it promoted... Good Work!

Frankly the whole you cant modify his script deal is a HUGE turn off. I understand him wanting credit for his hard work, BUT wth. I'll stick to safer things.
EDIT: Forget what I said I completely miss understood what he says in his post. He says
"Personal Use: You may tweak the V6 installation script (leaving credits intact) to your own personal liking as long as it is NOT redistributed in any way."
His autostart script script looks very handy. I was considering trying Gscript already here is a new reason hehe.

NoSudo said:
Frankly the whole you cant modify his script deal is a HUGE turn off. I understand him wanting credit for his hard work, BUT wth. I'll stick to safer things.
EDIT: Forget what I said I completely miss understood what he says in his post. He says
"Personal Use: You may tweak the V6 installation script (leaving credits intact) to your own personal liking as long as it is NOT redistributed in any way."
His autostart script script looks very handy. I was considering trying Gscript already here is a new reason hehe.
Click to expand...
Click to collapse
I can see why he doesn't want redistributables floating around, even with the open source (something I feel very strongly about) nature of the forum.
All I wanted to do was spread the word, maybe help along the way, if I've done this then I'm happy
Sent from my Nexus S using xda premium

NoSudo said:
His autostart script script looks very handy. I was considering trying Gscript already here is a new reason hehe.
Click to expand...
Click to collapse
You can also auto start scripts without having to use script manager or any other scripting program by calling them from within install-recovery.sh (see my sdswap mod).
For example if you had a script /data/app/supercharger.sh
in install_recovery.sh you'd add a line sh /data/app/supercharger.sh

crossix said:
You can also auto start scripts without having to use script manager or any other scripting program by calling them from within install-recovery.sh (see my sdswap mod).
For example if you had a script /data/app/supercharger.sh
in install_recovery.sh you'd add a line sh /data/app/supercharger.sh
Click to expand...
Click to collapse
Cool. I have re-written another version of my hulu script in .sh and set it up to be able to run in a normal verbose mode, or to accept "silent" as a command line argument to redirect output to a lhulu.log file instead to better allow for the option of running at startup like a cron entry or what ever our allowed methods are on android.(like the one you just referenced, thanks) I'm planning on playing with it a little to figure out the best and easiest method. Then repost the updated version that can be a semi permanent fix.

NoSudo said:
Cool. I have re-written another version of my hulu script in .sh and set it up to be able to run in a normal verbose mode, or to accept "silent" as a command line argument to redirect output to a lhulu.log file instead to better allow for the option of running at startup like a cron entry or what ever our allowed methods are on android.(like the one you just referenced, thanks) I'm planning on playing with it a little to figure out the best and easiest method. Then repost the updated version that can be a semi permanent fix.
Click to expand...
Click to collapse
install-recovery.sh won't work for the hulu lib, sometime after that script is loaded all the apks libs get extracted for whatever reason. Unless you put a wait in there for the prop sys.boot_complete or something like that. Might also need to use busybox run-parts for a seperate init.d script, not sure if the wait would actually stop the rest of the boot process.

It should be fine, install_recovery is called really late in the boot process you're right about putting the waits in, if you look at my swapscript you'll see the amount of time I used to get it to work (and it does not pause the other processes).
Sent from my MB860 using XDA App

crossix said:
It should be fine, install_recovery is called really late in the boot process you're right about putting the waits in, if you look at my swapscript you'll see the amount of time I used to get it to work (and it does not pause the other processes).
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It's not as late as I previously thought myself. dmesg won't work at that point and getting a logcat from there you'll see it's the start of the system log just when vold starts up. Which is why you need a few sleeps in your script. Using it was my second attempt at 2nd-init, which wasn't possible until after my first bootloop, the boot animation starts later but also before the libs are replaced.
For hulu I've just been running a gscript after a reboot because of this, at least until I find a different solution.
Anyway install-recovery is the perfect spot for any kind of kernel tweaks and also SuperCharger.
@toyface sorry for being off topic

Sorry a little confused with the last part how do I navigate to /data in script manager?
Edit.. never mind. ma bad noob moment, couldn't for the life of me figure out how to get out of the mnt part of the directory.
Sent from my A100 using Tapatalk

[Guide] How to Install Ubuntu On Galaxy Nexus

First before I start. I just wanted to say that this is not my work. This is simply a guide
to assist other galaxy nexus users who would like to run ubuntu but don't have an understanding
on what they should be doing precisely. The original thread called "linux on android" will be
posted at the bottom of the thread for those wanting to thank the original author. I couldn't
find a guide specific to our device hence the creation of this one. If this has not been posted
in the correct area, moderators please feel free to move it to the correct subforum.
Here is the part where I say, I'm not responsible for anything that happens to your phone. You do
this at your own discretion. This is something to tinker with for anyone who likes to mess with
their phone and show off a little bit.
Also be sure to follow my instructions exactly how I write them to avoid any unnecessary confusion.
As a base, I am using AOKP B39 and franco kernel Nightly 192.
If you have terminal emulator or androidVNC currently installed please clear app data and uninstall.
This of course is to be extra careful.
First things first: You want to have root and a kernel installed that has loop device support.
Like I've mentioned already, I am using Franco Nightly 192 and it is working perfectly fine
therefore I see no reason why it should not work for you. Best results in my opinion will come from using my
ROM base and kernel.
Next here are links to the following files you need. These files are quite big and there are 3
different kinds. The difference between each kind is explained on the page. Remember to keep in
mind how much space you must have on your phone before downloading a file. You don't want to waste
your time downloading the full image if you don't have the space to install it.
Here is the link to the full/small/core images. Download the version of ubuntu you wish to run on
your phone and make sure it is the latest which as of today is dated June 8th 2012.
Remember that the "core" version is for experienced ubuntu users only as it has no GUI. only
command line.
http://sourceforge.net/projects/linuxonandroid/files/Ubuntu/12.04/
Once you have downloaded the image you wish to run. You may extract the img file from the zip file
using 7zip or winrar. Both work perfectly fine. You will notice that once you extract the file
there is a ubuntu.img and an ubuntu.img.md5
The md5 file is a checksum file, if you wish to validate the integrity of the file you just downloaded
go ahead and use a program such as cygwin to compare the md5 hashes.
Moving on, once you have extracted the ubuntu.img file. Move the file onto your galaxy nexus
internal memory to the root of your sdcard inside a folder named "ubuntu".
If you have done this correctly your directory should be as follows. /sdcard/ubuntu
Next you want to download the bootscript which I will attach at the bottom of this thread. Extract the ubuntu.sh file from the zip i posted below.
Once you have downloaded the ubuntu.sh file I have attached. You need to place that file in
the same /sdcard/ubuntu directory where your unbuntu.img file is located.
To confirm you are on the right track you need to install terminal emulator from the
google play store as well as install androidVNC. Once you have both apps freshly
installed you can go ahead and open up terminal emulator, grant it superuser permission
and then type the following:
su
(followed by the enter key) you should see the $ turn into a # symbol.
Next you type:
cd /sdcard/ubuntu
(again followed by the enter key) now your directory should be changed to the /sdcard/ubuntu folder
Next command:
ls
(once more followed by the enter key) This should list all files currently in the folder if you
see ubuntu.img as well as ubuntu.sh listed then you are right where you need to be.
Once you have confirmed that both files are listed we can go ahead and start the process of starting
up ubuntu. In terminal emulator type the following:
sh ubuntu.sh (all commands are followed by enter key by the way)
Terminal emulator should start the launch sequence then ask you if you want to start VNC server.
Type "y" then hit enter. Type "y" without quotations of course.
Next it will ask you if you want to start the ssh server. Again type "y".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next it will ask you for the screen size you wish to use. You can choose whatever resolution you
wish to use. I like to use the nexus native resolution which is 1280x720.
Therefore I type "1280x720" and press enter.
Next it will ask you if you would like to save your settings type "y".
Finally your terminal should say "[email protected]:/#"
Now you are ready to start up androidvnc. Press the home button and DO NOT EXIT terminal emulator.
Once you open up android VNC enter the following information:
nickname: ubuntu
password: ubuntu
address: localhost
port: 5900
Check off the keep password option then scroll down to the botton of that page where it says
Color Format and change it to 24-bit color (4bpp)
Then press connect and voila whatever ubuntu version you downloaded should start up. The mouse should basically be used as if the screen was a track pad.
Exiting ubuntu is also easy. Just hit the settings button and a prompt should pop up with an option that says disconnect. Simpy disconnect then switch over to terminal emulator which should still be running and type:
exit
Wait around 30 seconds and it should say It shut off correctly. Type exit once more and It will close the directory you were in. One more exit and terminal emulator will close itself.
The next time you want to load up ubuntu just open up terminal emulator follow the first 2 steps and once you load up ubuntu.sh your config file should be loaded and you will be able to skip all the tedious settings. Then go over to androidVNC and your settings should also be saved. All you do is hit connect and you should be good to go.
Good luck and hope you all enjoy it. I'll post pictures of the steps that I think will be helpful. Also if this helped you out. Hit the thanks button please.
Also don't forget to checkout the original thread for further information and details.
http://forum.xda-developers.com/showthread.php?t=1585009

This looks awesome, downloading atm and will test on Rascream/Trinity
Edit: Seems that trinity kernel doesnt support loop so it wont work.

in april i buyed the paid version of this app (ubuntu,because months ago backtrack and debian wasn't released i think)but never ever tried due to many probems\errors on vnc.thank you very much for this guide,now i'm downloading the 12.04 full and retry with yours tutorial.appreciated man!:good:

Afwasmassi said:
This looks awesome, downloading atm and will test on Rascream/Trinity
Edit: Seems that trinity kernel doesnt support loop so it wont work.
Click to expand...
Click to collapse
Try flashing a different kernel such as Franco's kernel to make sure it is indeed the kernel and not the rom.
Sent from my Galaxy Nexus using xda premium

Find much more here: androlinux.com

rjmohit said:
Find much more here: androlinux.com
Click to expand...
Click to collapse
That is a universal guide. I made this thread specifically for the galaxy nexus. Please do not post links as that can confuse other users on what they should be doing. Thank you.
Sent from my Galaxy Nexus using xda premium

*le bump-a to the top-a*

Theshawty said:
*le bump-a to the top-a*
Click to expand...
Click to collapse
Lol you didn't have to bump it. Just for people who are searching for a guide.
Sent from my Galaxy Nexus using xda premium

fire & ice said:
Lol you didn't have to bump it. Just for people who are searching for a guide.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Considering how people don't use the search button here, I thought I had to bump it
Sent from my Galaxy Nexus using Tapatalk 2

Thanks for the guide. I did exactly what you said, but I got this error:
http://dl.xda-developers.com/attach.../5/9/1/1/3/Screenshot_2012-08-13-20-51-35.jpg
That's probably connected to the kernel's loop device. I tried first with the one included in the rom (liquid beta1 JB), then I flashed the last release of Franco (r241) but got the same error. Am I missing something?
Thanks for your help

Great guide, i am gonna try to make a complete ROM + awesome kernel
Sent from my Galaxy Nexus using xda app-developers app

mastergrifis said:
Thanks for the guide. I did exactly what you said, but I got this error:
http://dl.xda-developers.com/attach.../5/9/1/1/3/Screenshot_2012-08-13-20-51-35.jpg
That's probably connected to the kernel's loop device. I tried first with the one included in the rom (liquid beta1 JB), then I flashed the last release of Franco (r241) but got the same error. Am I missing something?
Thanks for your help
Click to expand...
Click to collapse
I got the same thing running BAMF Paradigm and Franco's 241 nightly. It appears to be a problem with the busy box. I got the same message and researched that busybox distribution (is it a distribution?) and came across this:
https://play.google.com/store/apps/...ndroid&feature=nav_result#?t=W251bGwsMSwyLDNd
It booted to the shell and asked if I want to start VNC/SSH, I am able to connect to VNC/SSH from my phone (duh) and my laptop but the VNC client comes up and displays an error message:
"Xsession: unable to start X session --- no "/home/ubuntu/.xsession" file, no "/home/ubuntu/.Xsession" file, no session managers, no window managers, and no terminal emulators found; aborting."
I will get some screen shots up tomorrow. I'm using the v4 image from the download site. It might just be the image. I did an MD5 check and everything matched up.
I know this isn't your project, does anybody have any ideas? I tried installing ubuntu-desktop from command line but there was not enough room for the install...
EDIT: I feel like an idiot now... The OP clearly states that the core version has no GUI. That might be why I couldn't get to a GUI... I guess I could put the LAMP packages on it and use webmin... Or I'll just get the small package.

mastergrifis said:
Thanks for the guide. I did exactly what you said, but I got this error:
http://dl.xda-developers.com/attach.../5/9/1/1/3/Screenshot_2012-08-13-20-51-35.jpg
That's probably connected to the kernel's loop device. I tried first with the one included in the rom (liquid beta1 JB), then I flashed the last release of Franco (r241) but got the same error. Am I missing something?
Thanks for your help
Click to expand...
Click to collapse
The error is from the script trying to use the busybox that's included with the app. In order for it to work without the app installed, it needs to be changed to point to /system/xbin/busybox instead of /data/data/com.whatever/busybox. That is assuming that you have busybox installed (and that your busybox takes the same arguments for the loop command as the busybox the app provides).

Thanks everyone for the answers :laugh:

I'm using the same Rom build as you. How do you move the files into root of /? I am using Astro browser and it wont let me copy or move anything into that directory....I cannot see any way to do it through Windows either. Any help?
I assume I am getting my errors because the file is not located in that directory.
ttp://pic90.picturetrail.com/VOL2353/13103118/24172961/403735977.jpg[/url]
ttp://pic90.picturetrail.com/VOL2353/13103118/24172961/403735976.jpg[/url]

Looks like your Ubuntu image is corrupt. Did you download it on Wi-Fi?
The files should not be in the root of your filesystem either. Everything should be at /sdcard/ubuntu and it's case sensitive. If you know the image is good, just delete the md5 file and it won't do the check.
Sent from my Galaxy Nexus using xda app-developers app

Echo5ive said:
Looks like your Ubuntu image is corrupt. Did you download it on Wi-Fi?
The files should not be in the root of your filesystem either. Everything should be at /sdcard/ubuntu and it's case sensitive. If you know the image is good, just delete the md5 file and it won't do the check.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can only make my file path /storage/sdcard0/Ubuntu. I see no way to get it to plain old sdcard/Ubuntu
I downloaded it via wifi multiple times and same error. Tried small and large images too with same error.
I deleted the md5. Fails now during checking loop device...MISSING. Unable to create loop device.
I tried the kernal that came with the AKOP 39 rom as well as franco.Kernel-milestone2.zip, I cant find the franco 192 kernal that you are using anywhere
I did this EAILY on the first try with my Triumph many months ago....no idea why I'm having so many problems with my GNex...

Try clearing the app data, uninstalling, and then reinstalling the terminal emulator you are using. (And a reboot wouldn't hurt...) I haven't tried it on AOKP but it should handle it fine.
The Franco kernel I use is the most current release at the time of this writing, #241.
Sent from my Galaxy Nexus using xda app-developers app

Echo5ive said:
Try clearing the app data, uninstalling, and then reinstalling the terminal emulator you are using. (And a reboot wouldn't hurt...) I haven't tried it on AOKP but it should handle it fine.
The Franco kernel I use is the most current release at the time of this writing, #241.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Still a no go with #241 Kernal.
Checking loop device... MISSING
Creating loop device...ubuntu.sh [86]: /data/data/com.zpwebsites.completelinuxinstaller/files/busybox: not found
FAILED
Error: Unable to create loop device
I have Busy Box Free v 1.20.2 installed.

Are you using the ubuntu.sh file from the OP or the app from one of my previous posts? I initially tried installing that app to install the specific busy box instance referred to in the script.
If you are using the app and trying to launch from there, try modifying the .sh file to point to your installed version (should be /system/xbin/busybox).
Sent from my Galaxy Nexus using xda app-developers app

[Q] init.d script to start a service

Hey,
im not sure if anyone is familiar with KeepScreen but its an amazing app which has a wake lock preventing the screen from timing out. So for instance, if youre reading xda and your screen shuts off, use this app to set it to never shut off when xda is the foreground app. It seriously works amazingly and i love it. But ever since ICS it doesnt start on boot.
I have found the command am to start an app from the command line but i can not for the life of me figure out how to use it inside an init.d script to start keep screen's service.
Any help?

Not sure if this is ROM specific, but I use the feature where the screen won't timeout if I'm looking at the screen. Can be finicky in lite light but other than that our had been great for me.
Sent from my SGH-T999 using Tapatalk 2

threshold350 said:
Not sure if this is ROM specific, but I use the feature where the screen won't timeout if I'm looking at the screen. Can be finicky in lite light but other than that our had been great for me.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I've used that but like you said it's not always perfect. KeepScreen has been flawless except the starting at boot issue
Sent from my SGH-T999 using Tapatalk 2

@ OP....
if your app is using init.d scripts to execute commands... and they aren't starting up after boot...
I think I understand you correctly here...
Then navigate to /system/etc/ and find the file init.qcom.post_boot.sh and open it in edit mode with a file explorer (root explorer is my preference but whatever gets it done) and add this line to the very end of the file as text
/system/etc/init.d*
That will execute init.d scripts AFTER boot, and might solve your problem.
Init.d executes early in the boot phase (pretty much when you see your boot animations and such) and simply put, that could be your issue.
Give it a shot, and if it doesn't work then there is likely and issue caused by what you described in your post.... (not every app works flawlessly with any version of android)

cobraboy85 said:
@ OP....
if your app is using init.d scripts to execute commands... and they aren't starting up after boot...
I think I understand you correctly here...
Then navigate to /system/etc/ and find the file init.qcom.post_boot.sh and open it in edit mode with a file explorer (root explorer is my preference but whatever gets it done) and add this line to the very end of the file as text
/system/etc/init.d*
That will execute init.d scripts AFTER boot, and might solve your problem.
Init.d executes early in the boot phase (pretty much when you see your boot animations and such) and simply put, that could be your issue.
Give it a shot, and if it doesn't work then there is likely and issue caused by what you described in your post.... (not every app works flawlessly with any version of android)
Click to expand...
Click to collapse
Thanks! But this isnt my app. Its an app in the playstore. I linked it in the first post. The app works on Gingerbread perfectly, but not on ICS or JB. It fails to start the service once the BOOT_COMPLETE broadcast is sent. So i was hoping to use an init.d script to manually start the service. However, when i open terminal emulator and type
Code:
am KeepScreen
nothing happens. So i guess my question is more directed to how to properly use the
Code:
am
command from terminal.

Your command line is incomplete
elesBB,
I ran into this old thread, but this might be helpful to others having the same problem as elesBB did. The command line is incomplete. Try:
am com.tni.KeepScreenLite
scvjohnny

scvjohnny said:
elesBB,
I ran into this old thread, but this might be helpful to others having the same problem as elesBB did. The command line is incomplete. Try:
am com.tni.KeepScreenLite
scvjohnny
Click to expand...
Click to collapse
I've since modded the apk but thanks!
Sent from my SGH-M919 using Tapatalk

[root] win and lin root

Because I didn't really like all the useless code in the windows root method, I decided to clean up that batch file a bit as well as convert the whole process to linux (not sure if it's out here, I remember seeing a linux rooting thread but kill me if I can't find it right now) and remove leftover files from the /stuff directory (they're not really needed, just methods for other devices based on the original root method
Anyway, on the Windows script side, I cleaned up the code, removed the korean text and rewrote what echos because I believe the lines that were there were simply not telling what the user what the script was doing. (installing vs pushing, there IS a difference).
On the linux side, I tore the script from the windows root, and modded it out to work on most linux systems (you need sudo for it to work right, and it helps if you have adb preinstalled in your path, but the way I wrote it it should detect if you have adb running and skip the startup of the version I provided)
As always, with the windows root method, make sure you have the drivers (i tried to download but keep getting 'access denied', you may have to search for these in other places, or maybe it's just not liking that I'm on linux) and try running as admin first, if that fails, run normally, and with BOTH methods, turn on 'unknown sources' and 'usb debugging'.
Other than that, if you have any issues with this, (other than forgetting to chmod +x RootOptimusG.sh ) let me know below!

Is this for V7 and V8, or does this work with V9 as well?

j4g3rb0mb3d said:
Is this for V7 and V8, or does this work with V9 as well?
Click to expand...
Click to collapse
only tested with V8

jat255 said:
http://forum.xda-developers.com/showthread.php?t=1996702
[HOW-TO][Linux] Root Sprint Optimus G
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Aah, yes I see it now, however my script does most of the work yours manually asks for automagically. Though TY for your link too

Also AIO in the dev section for lin and win.
http://forum.xda-developers.com/showthread.php?t=2039421
Sent from my LG-LS970 using xda app-developers app