How do I set up a program to run at the boot of android?
I'd like to run NetCounter every time my phone starts (to eliminate the risk of me forgetting to start it)
it should be set to start on boot by default. when i boot my phone i can see it in my running programs(i use dxtop) and it counts all the time
Related
I was looking through the Dev Tools app this morning and was in Development Settings. As I was scrolling down looking at stuff I accidentally checked "Show Running Processes".
My phone stopped responding and then a few seconds later did a quick reboot (it only went to the Android loading screen). It came back up but only for a few seconds then it went back to the Android loading screen. It hasn't stopped.
I did a Nandroid backup of it (unfortunately I didn't have a recent backup to restore too) so that if someone can help me fix this I'll be able to reload it. I ended up having to do a wipe to restore functionality to my phone.
I'm guessing that it's running out of memory trying to do what ever the "show running processes" does and ends up reloading due to that. Only problem is it keeps doing it again and again and again...
When the phone reboots I don't have any functionality, all I see is the lockscreen. Sometimes I can hit menu and it'll take me to the home, but there is nothing on the home screen and I can't move the launcher tray.
I'm in the process of moving, so I can't find a USB cord to hook to my computer to get an ADB logcat of what is happening.
Any help?
Is this on CM 4.2.13? If so, it is a known reproducable bug, that happens when you tinker with settings you shouldnt be
Try flashing down to 4.2.12.1 via recovery, you should not get the loop in this version. Then disable the 'display all running processes' and flash to 4.2.13, then re push the Contacts.apk
I just found that interesting feature with SuperD 1.9.2 last night. (I was heading for "Show CPU usage" and got curious).. word of advice, don't check the "show running processes" box..
interesting thing though, I noticed on each of the successive reboots it started at the android boot anim, skipping the T-Mobile G1 boot screen. Anyway, I ended up wiping and reinstalling. Weeeee......
Help!
I upgraded to froyo via Kies then all hell broke loose.
On first reboot after installation..a "new user menu" comes up asking for the user's preferences, once that pops up I start getting the following force close loops one after the other, force close one...another pops up:
The application logs provider
Gmail something
Media something
And keeps going on and on.
Decided to do a factory reset, since everything is backed up by google, did 3br clicked on factory reset...phone gets into "Downloading, do not turn off targett!!!" screen....I let it sit there for 30 minutes, no action. So disconnected the battery.
Booted normally, same issue as above.
Then decided 3br, and the "downloading" screen immediately came up after reboot without giving me the options of recovery mode.
So now, my phone boots into two forms only, and gets stuck there:
1. force close loop on user data entry page
2. with 3br, phone gets stuck on "Downloading' screen.
Any solutions for a non-developer like me?
FYI, running ryanZa one-lick lagfix. So phone is rooted.
Help...really need my phone back
Its easy!!! go to app manager and clear data!
Did you undo lagfix before updating ??.
jje
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
This is not a reason to start a new thread in the Development forums.
Support and Q&A for custom roms should take place in their appropriate threads. Use a bit of common sense, courtesy, and patience -- people will help you.
Please read the rules of posting new threads again here: http://forum.xda-developers.com/showthread.php?t=788800
anoneemooz said:
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
Click to expand...
Click to collapse
1) Lock ups most likely due to removing drm file from system apps.
2) Your using lagfix (I assume) and when you pull battery data corruption is very likely on some configs.
3) Read rules before posting.
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
This turns out to be a crash bug in Android see last post
While i was researching ways to maximize the battery life on my captivate I came across a setting in the tasker wiki that would help me log the life of my battery.
I had already set up juice defender and other ways to let tasker turn on and off battery draining settings like GPS and WIFI and thought that this would be a good way to track on a day to day basis how much life i was getting out of each battery.
Here is what i found. The day after i set up the tasker profile i began watching results. Around 11 am the next day my phone began to loop in reboot. it just went right to my bootanimation and then home screen, boot animation, home screen....
I thought nothing of this as i flash roms often and was beta testing some stuff at the time. I proceeded to flash stock ---> flash custom rom. what i i had to repeat this process a few times because it continued to reboot. After a few flashes i became stable. the following day at around 11 am my phone began to boot loop again. this time i flashed stock and left it there only to begin looping again. i turned the phone off for a while and then flashed stock--> custom rom. It looped again.
this time i brought the phone to a device support center and had it replaced.
with the new phone i use no settings or backups from TiBu except for a few apps like handcent, takser, angry birds and a couple other games. at this point i thought that my old phone was just worn out from the many flashes. Two days after getting the new phone and installing all apps (except the few apps like tasker) my phone began to boot loop at 11AM. this time i flashed to stock and it began to boot loop again. I repartition and flashed again and it became stable. Until the next day at 11am when it began to boot loop again.
i returned to the device support center with a stock phone in boot loop.
this time I have not used a setting from tibu backup but have returned all aps to almost the same as before (the best i can by memory)
day one i Ran stockfor a day.
day two i ran the same custom rom/kernel combo.
day 3 i ran everything with the apps set up and used the same battery that was in from the last time it looped.
The only Thing that was the same from both phone that looped what isn't in my newest phone is that tasker setting.
I am almost 99% sure that this setting did something to the file system at low levels which is unrepairable by flashing.
Is this a bug? i do not know, I reproduced it twice but do not think that a device support center will replace a third device for me.
If anyone is/has ran this profile with no problems than I can let this go as unsolvable.
If anyone is willing to test this setting and can reproduce the bug then i think we will have something to take to Samsung regarding a system bug that is unrepairable at user level.
here is the link for the profile
i followed this setup exactly as stated except here Write File: File "Batterlog.txt" i used "BattLog.txt" im not sure if it makes a difference but if you are going to set this up please try it using BattLog.txt
here are the steps
Code:
1. Make up a new profile, context: Power: Battery changed, priority normal -> done.
3. Add task Alert: Flash: Text "%BATT % %MEMF", If checked "%BATT !~ %BATTPREV" -> done
4. Add task File: Write File: File "BattLog.txt", Text "%DATE %TIME %BATT", Append checked, If checked "%BATT !~ %BATTPREV" -> done
5. Add task Variable: Variable Set: Name "%BATTPREV", To: "%BATT"
I guess everyone must think that i indeed did find a bug in the filesystem because not one person has come forward to try this out. If I am wrong at least you have yourself a very nice way to track you battery usage.
I read over your task and don't think I missed anything unusual (ie. weird infinite loop condition that would make it constantly write to the file).
I'm not about to try it, of course, given what you have experienced. You might try the limit repeats or cooldown period settings for the profile in case that really is the issue.
I can tell you I've been using the file writing actions for a clipboard history task I wrote and have not had your issue, even when I screwed up a condition and it was infinitely writing my clipboard contents to a file for a couple of minutes straight.
I'm running an i896 captivate with a js3 rom fwiw. Hope you get it figured out.
Sent from my SAMSUNG-SGH-I897 using XDA App
tiuk said:
I read over your task and don't think I missed anything unusual (ie. weird infinite loop condition that would make it constantly write to the file).
I'm not about to try it, of course, given what you have experienced. You might try the limit repeats or cooldown period settings for the profile in case that really is the issue.
I can tell you I've been using the file writing actions for a clipboard history task I wrote and have not had your issue, even when I screwed up a condition and it was infinitely writing my clipboard contents to a file for a couple of minutes straight.
I'm running an i896 captivate with a js3 rom fwiw. Hope you get it figured out.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I am not attempting to recreate at this time. I will be when I have a replacement phone. If this is indeed a fs bug i can imagine anyone who does not want their phone aymore could use this setting and go into infinite loop and get a replacement. The does not require root and can be used on any firmware. Samsung would have to react.
so after running the new phone for a week i got the boot loops again today at 11:08am
i am trying to see if it is battery related as I DID NOT have the tasker setting in place.
here is the log if anyone wants to try and help solve this. i have other batteries i will be trying this week. (everyday until i fix it) the problem is though that if the filesystem is damaged than testing on this phone is useless.
http://dl.dropbox.com/u/17699865/android_report1298308267139.zip
I solved the bug bug cant fix it.
follow the link to my report.
anyone able to reproduce?
i have been able to send the message to myself but it always arrives in 2 part.
goo.gl/wCrlp