http://forum.xda-developers.com/showthread.php?t=772795
Apparently it is possible to run the PSFreedom Jailbreak App on all MSM72x CPU, and considering the Tattoo has one, then theoretically it should be able to run it right?
But in it's current state, will it work on our Tattoo's and how in the freaking hell does it work anyway? xD
Anyways, just wanted to drop this here.
It would be wonderful *______*
I was thing of that.. lol
Well we just have to give it a try...
KezraPlanes said:
http://forum.xda-developers.com/showthread.php?t=772795
Apparently it is possible to run the PSFreedom Jailbreak App on all MSM72x CPU, and considering the Tattoo has one, then theoretically it should be able to run it right?
But in it's current state, will it work on our Tattoo's and how in the freaking hell does it work anyway? xD
Anyways, just wanted to drop this here.
Click to expand...
Click to collapse
Is confirmed the porting on android and psp. But we don't know what will need to run. A new kernel, sure. Maybe the terminal emulator (or a gui) to start/stop the deamon.
francians said:
Is confirmed the porting on android and psp. But we don't know what will need to run. A new kernel, sure. Maybe the terminal emulator (or a gui) to start/stop the deamon.
Click to expand...
Click to collapse
As far as I've heard, you need to not have USB at all (only charging works) to be able to run this.
So either as someone said on the original thread, someone makes a recovery image that we can flash for that same purpose OR dual-boot from SD.
To be honest I don't see the second one happening on the Tattoo
To run this hack you'll need a non-senseUI 2.2 rom.
https://spreadsheets.google.com/lv?key=tarAC83Wjsq2QZvP4iR5mlw&toomany=true
At least on kernel 2.6.29 (spqrom 0.4), the tattoo uses the msm_hsusb driver instead of the MSM72K, so i don't think it will work without porting it. But the hero and dream use msm_hsusb on 2.6.2x kernel and MSM72K on 2.6.3x. Maybe a kernel update could fix this for us (hear that, rom cookers? update the kernel of your froyo roms!)
blackkn1ght said:
To run this hack you'll need a non-senseUI 2.2 rom.
https://spreadsheets.google.com/lv?key=tarAC83Wjsq2QZvP4iR5mlw&toomany=true
At least on kernel 2.6.29 (spqrom 0.4), the tattoo uses the msm_hsusb driver instead of the MSM72K, so i don't think it will work without porting it. But the hero and dream use msm_hsusb on 2.6.2x kernel and MSM72K on 2.6.3x. Maybe a kernel update could fix this for us (hear that, rom cookers? update the kernel of your froyo roms!)
Click to expand...
Click to collapse
Hi,
In eclair kernel for tattoo there are the drivers for MSM72K! Later i ll try to
compile a kernel with MSM72K support for tattoo and publish it here to test
it.
Seg.
Nice already some progress
Well were we go... for Desire and G1...
h**p://forum.xda-developers.com/showpost.php?p=8025826&postcount=52
h**p://www.ps3-hacks.com/2010/09/06/hack-your-ps3-with-your-androiddesire/
it works?
Im going to try this now :0
already try, does not work((( at spqrom 0.4
I tried flashing the zip and it said error in /sdcard/PS3-signed.zip (Status 0)
That's because they weren't made for the Tattoo
Tattoo appeared in the list http://psfreedom.com/wiki/index.php?title=Device_compatibility_list. waiting ...
It works on HTC Wildfire : http://www.ps3underground.net/esclusiva-port-del-psfreedom-su-htc-wildfire/
tibob33 said:
It works on HTC Wildfire : http://www.ps3underground.net/esclusiva-port-del-psfreedom-su-htc-wildfire/
Click to expand...
Click to collapse
The wildfire uses the same msm_hsusb as shown in the graph, so maybe the ball is now rolling?
Edit:
I flashed the wildfire zip and it returned no errors like the other zip, but failed to go past the tattoo logo on SPQRom 0.4.1?
Incorrect boot.img I guess
Wildfire kernel 2.6.32
Tattoo kernel 2.6.29
so probably if you use segway's experimental .32 kernel it is going to work . try it.I don't have a ps3.
rwmanos said:
so probably if you use segway's experimental .32 kernel it is going to work . try it.I don't have a ps3.
Click to expand...
Click to collapse
Im pretty noobish at android stuff, seen the thread and gone to the link and there is loads of files... please guide
Related
I thought a thread would be nice where you guys can show us your custom roms and where to download it ;-).
There are no custom ROMs for the Milestone, because of his locked bootloader. There are some personalized Nandroid backups, but they aren't true custom ROMs.
However, some hackers are working on a kernel module for the Milestone that could load a customized kernel after the original one starts.
But i thougt i read something yesterday about that the bootloader is cracked now.
Masterchief14 said:
But i thougt i read something yesterday about that the bootloader is cracked now.
Click to expand...
Click to collapse
Cracking the bootloader would be very hard, the only thing that is currently possible is a kexec attack, thou it's not ready for normal users ; )
Read more here:
http://and-developers.com/motorola_milestone
this is as good as it gets for now.
http://motofunvn.com/forum/?showtopic=60242
pulsar roms. they arent roms, just a script to add and remove apks. but i think most of the mods are now part of 2.1 oficially realeased.
What abaut just replacing /system partition file by file from some 2.2 ROM and see how it works. Though since kernel must not be touched, many things like WIFI tether will not work this way anyway. But in theory, wouldn't this make an almost 2.2 ROM for Milestone? Like all the spedups, louncher, new gmail app and stuff, that is not related to kernel right?
Sense ui for Milestone
Theres a sense ui rom that i found, looks like that the developer abandoned it, iv tried to port it into my milestone...but im just a novice user...so dont know how to tune the rom...hope some one here can further develop it...
http://forums.zeusdroid.org/viewtopic.php?f=3&t=25
CommanderThor said:
What abaut just replacing /system partition file by file from some 2.2 ROM and see how it works. Though since kernel must not be touched, many things like WIFI tether will not work this way anyway. But in theory, wouldn't this make an almost 2.2 ROM for Milestone? Like all the spedups, louncher, new gmail app and stuff, that is not related to kernel right?
Click to expand...
Click to collapse
Applications are not the problem, for that you only have to edit few lines in
/system/build.prop
ro.build.version.sdk=8
Click to expand...
Click to collapse
and probably all references from version 2.1-update1 to 2.2, e.g.:
ro.build.version.release=2.2
Click to expand...
Click to collapse
Then you should be able to install android 2.2 apps...
As far as the whole system partition is concerned, there might be some dependencies for some libraries that require parts of the new kernel, you are free to try that out... Just don't forget to create a nandroid backup
Also the "new"-jit-speed up is already possible with the 2.1, it's just buggy as hell
Wifi tether might work, for the same reason that android-wifi-tether works with milestone with only su permissions, because the kernel for 2.0 included the necessary module(s) : )
CommanderThor said:
What abaut just replacing /system partition file by file from some 2.2 ROM and see how it works. Though since kernel must not be touched, many things like WIFI tether will not work this way anyway. But in theory, wouldn't this make an almost 2.2 ROM for Milestone? Like all the spedups, louncher, new gmail app and stuff, that is not related to kernel right?
Click to expand...
Click to collapse
Most of the performance related things and Flash stuff etc. are as a result of the new kernel.
The new Gmail app however...
The source code for Froyo was released today
I am building a Vanilla Froyo rom for Legend, and should have the beta ready for download soon!
Great news
Just a stupid question: Froyo is available on AOSP. That means the sources of the OS are available. With this as a starting point, what is required to port it to a specific device (ie the legend)? Do you need the sources of the kernel (that HTC published), specific drivers (which ones?), something else?
Thanks!
MichaelAlexanderBull wel all love you!!!
gooooooood jub
Yeahhh!!!! CanĀ“t wait.
Thanks!!!!
If you are succesfull, you will be our hero. Ohw and please put htc sens on it
This is really good news! I'm currently running the rom from Ali Ba, and I already prefer stock Android over Sense. Keep up the good work!
Great news!!!!
please let me enjoy legend without looking at my brother's nexus one with froyo
good news. cannot wait for the new ROM
qzem said:
If you are succesfull, you will be our hero. Ohw and please put htc sens on it
Click to expand...
Click to collapse
sorry i won't be able to put sense on it
MichaelAlexanderBull said:
sorry i won't be able to put sense on it
Click to expand...
Click to collapse
I think most of us would prefer it without sense ..
Y is sense so bad? I don't mind having sense maybe not the news and footprint but a lot of the sense I think its great
Sent from my HTC Legend using XDA App
I guess it will be very hard to port Froyo to the Legend because HTC devices often depend on com.htc.framework which will most likely not work with Froyo.
I'm going to try to port Froyo too once I get Vanilla Bean 0.3 ready, but this is hard work.
Sorry, not that I think MichaelAlexanderBull is doing bad work, but he simply doesn't have the source code for a few of the libraries needed to run HTC devices (especially some libraries that implement proprietary hardware calls). So don't expect a fully functional release.
I'm sure will see Froyo on the Legend though, just be patient.
ali ba said:
I guess it will be very hard to port Froyo to the Legend because HTC devices often depend on com.htc.framework which will most likely not work with Froyo.
I'm going to try to port Froyo too once I get Vanilla Bean 0.3 ready, but this is hard work.
Sorry, not that I think MichaelAlexanderBull is doing bad work, but he simply doesn't have the source code for a few of the libraries needed to run HTC devices (especially some libraries that implement proprietary hardware calls). So don't expect a fully functional release.
I'm sure will see Froyo on the Legend though, just be patient.
Click to expand...
Click to collapse
You know more than me, But im still going to try
EDIT:
I have managed to get the G1 port to boot and run on my legend in the past, it could recieve calls etc, but the touchscreen problem was there.
So i'm feeling confident that we will get a good stable release working with the ASOP release! Will probably take a bit of time, but it is going to happen
W00T!?
MichaelAlexanderBull said:
sorry i won't be able to put sense on it
Click to expand...
Click to collapse
NOT ?! You are fired!
Vanilla will be nice anyway
This is a good reason for me to root my Legend.
MichaelAlexanderBull said:
You know more than me, But im still going to try
EDIT:
I have managed to get the G1 port to boot and run on my legend in the past, it could recieve calls etc, but the touchscreen problem was there.
So i'm feeling confident that we will get a good stable release working with the ASOP release! Will probably take a bit of time, but it is going to happen
Click to expand...
Click to collapse
i'm sure you'll do just fine
MichaelAlexanderBull said:
You know more than me, But im still going to try
Click to expand...
Click to collapse
If my comment had made you run away and stop development I'd be very disappointed!
No, really, I'm confident you'll learn how to compile and port Froyo in no time. It's hard at the beginning, but once you get into it, it can be lots of fun too.
I wish you great success.
I would like to know if Flash would work in the browser.
That would be AWESOME
Froyo FTW
Cant wait for this ROM. It will be awesome
Will
you guys (michael and ali ba) should work together. this will make porting froyo to legend faster. =)
Hey guys,
Now that Gingerbread is out, I think most questions on people's minds are: Can it happen? What's needed?
Sent from my Tattoo using XDA App
I'm trying to do something about it stay tuned...
i just saw a youtube video about a wildfire running an early built,
so i thinks its not a matter of resolution.
I just hope the CM can be work on ROM.
We need AOSP sources before it can be built properly. The ones on Wildfire etc are just hacked together from an emulator image, and they run quite slowly. For the Tattoo, I'm a bit uncertain if it can be used with kernel 2.6.29, or if 2.6.32 or higher is required.
It will eventually - Froyo took a while but is here. But I can't wait for the new UI and it will be speedy if Google are telling the truth
I was WAITING for someone to ask this question
Anyway, fingers crossed
It has to be possible: http://androinica.com/2010/12/07/go...droinica+(Androinica+-++A+Google+Android+Blog)
I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.
aliwaqas said:
I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.
Click to expand...
Click to collapse
I guess it will be pretty soon, because Gingerbread AOSP is already available to create ROMs like fyodor's or spartm's, and Cyanogen is working on modded Gingerbread too already
gingerbread on tattoo would be GREAT
Sent from my HTC Tattoo using XDA App
@those who try to port 2.3 for tattoo: If you're successfull, plz change the icon for mobile data... it's just too tiny for our small screen!
the source code for the nexus one is out, i dont know how difficult it is to port it to another device but i hope someone tries it already
I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?
Aaroneke said:
I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?
Click to expand...
Click to collapse
Stuck when compiling or when booting?
Compiling i've managed this problem, but i changed some stuff and now i got it again, i'm trying to make new vendor files step by step using fyodor,..etc (and google ref) files just for reference, but it can take a while(if i'll get it working..)
Hey All,
I was just wondering if data2ext would be possible for our beloved milestone. Could some devs please take a look at this - http://www.xda-developers.com/android/new-hack-for-desire-and-nexus-one-data2ext/ ?
I hope this will be possible.
mohitrocks said:
Hey All,
I was just wondering if data2ext would be possible for our beloved milestone. Could some devs please take a look at this - http://www.xda-developers.com/android/new-hack-for-desire-and-nexus-one-data2ext/ ?
I hope this will be possible.
Click to expand...
Click to collapse
I'm going to say no (on Froyo) currently - data2ext seems to requires the same thing that apps2sd (CM) does, and the G.O.T. 2.2.1 leaked SBF doesn't support it.
If you still have 2.1u1/2 from MOTO - then maybe.
So you are saying that the former one is may be compatible but no for the new one ? may be we have to wait for the officiall froyo for this ?
Craven68 said:
So you are saying that the former one is may be compatible but no for the new one ? may be we have to wait for the officiall froyo for this ?
Click to expand...
Click to collapse
Yes, the 2.1 moto kernel supports it, but the leaked 2.2 moto kernel doesnt. Hopefully the official kernel 2.2 will. So if your phone is still on eclair it could be potted, but I don't think any devs are focused on eclair roms much anymore
The way it's implemented requires ext access from Android. This requires a kernel module which for now does not work in our leaked 2.2.1 based builds. It will probably work when Moto releases the source code for the kernel. As of now, ext access is only on 2.1 based builds.
Lollipop_Lawlipop said:
The way it's implemented requires ext access from Android. This requires a kernel module which for now does not work in our leaked 2.2.1 based builds. It will probably work when Moto releases the source code for the kernel. As of now, ext access is only on 2.1 based builds.
Click to expand...
Click to collapse
So will this work with eclair then? (2.1) And if yes, how?
mohitrocks said:
So will this work with eclair then? (2.1) And if yes, how?
Click to expand...
Click to collapse
yes, it should work on eclair - if a dev is willing to try to port it.
Can't wait, hope this will get ported so I can mess with it my Milestone.
Tried this on my Droid tonight and had no luck. On my old phone(CDMA HTC Hero200) I was going from 190MB of internal space to around 473MB of internal space. I just tried it tonight on my Droid with all the coding on Better Terminal Emulator Pro and had no luck whatsoever. I am running CM7.1 Stable on my Droid. It's Android 2.3.7 Gingerbread and thats what I had on my Hero as well. I'll keep looking at the coding and everything and see what I can do for us. I'll talk with some guys over in the Hero Forums about it too. There are different types of data2ext versions as well that may be of some use to us.
EDIT: OK,I had an old android app sitting around on my external called swapper.apk. I gave it a try on my droid today as well and had no luck. I used to use that app on my old T-Mobile G1 way back in the day. Thought it MAY work but got nothing,I'm at a loss right now but will keep working on this for everyone!
So I've just recently flashed my vogue with myns donut for a couple days and It was pretty good. The camera worked but no video and neither did the gps. I understand that for verizon you have to follow a specific procudure to get that to work so that makes sense. I'm just curious to what android roms they are using for their vougue. I'm looking for one that has the most working features. Let me know what it is and how you had it set up.
For my Fresh Froyo although remember android no is 100% stable but Fresh Froyo is very good.
If you know what you want my barebones build is known to be one of the fastest and most stable builds. With that though you need to get the apk's to what you want and add them in. It is meant to be as cut down to the minimum to be light and lithe on our devices.
Another way to get apps is to use the market, I have the most recent version of the market in my build. CM 6.1 is Froyo based so you have video and all the other froyo features.
aceoyame said:
If you know what you want my barebones build is known to be one of the fastest and most stable builds. With that though you need to get the apk's to what you want and add them in. It is meant to be as cut down to the minimum to be light and lithe on our devices.
Another way to get apps is to use the market, I have the most recent version of the market in my build. CM 6.1 is Froyo based so you have video and all the other froyo features.
Click to expand...
Click to collapse
I tested more than 10 ROM including the yours and I am sorry to tell you than ever before me to worked well even the last released CM 6.1, does not work properly with the kernel that is in my signature and is the one that works best with the USB sync and just by this already this ruled out your ROM, so I'm still saying Fresh Froyo for me is the more stable and clean ROM of froyo that I tested.
Josue_181 said:
I tested more than 10 ROM including the yours and I am sorry to tell you than ever before me to worked well even the last released CM 6.1, does not work properly with the kernel that is in my signature and is the one that works best with the USB sync and just by this already this ruled out your ROM, so I'm still saying Fresh Froyo for me is the more stable and clean ROM of froyo that I tested.
Click to expand...
Click to collapse
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Josue_181 ......Any chance you could post where you got the exact images/files etc. if it's not too much trouble. Thanks! I hope to run from haret if possible.
I have searched but it has been a while since I looked in this section. Is it DZO's Fresh Froyo you use and I cannot find Kernel: 2.6.25 10-31-10??? Hope you can help, thanks.
aceoyame said:
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Click to expand...
Click to collapse
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
aceoyame said:
Well mine is assuming you want to use the .32 kernel. Which with Clemsyn's kernel works very well. Battery life sucks though since the changes haven't been committed to git yet. But with that kernel I have not had any data loss since it came out.
Click to expand...
Click to collapse
Would have to prove with that kernel I know how to adapt the kernel Clemsyn's to our Vogue if it works I comment as I was to see if I change my mind about your ROM
krwilson said:
Josue_181 ......Any chance you could post where you got the exact images/files etc. if it's not too much trouble. Thanks! I hope to run from haret if possible.
Click to expand...
Click to collapse
The thread Fresh froyo this here, as well as guides for the installation of haret/nad, only is question search and read...
Prowess said:
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
Click to expand...
Click to collapse
our vogue would not benefit from the battery enhancements since our kernels were designed for our battery
Okay so you say fresh froyo is one of the best? I looked it up but I am confused about what to download. Any advice would be great. I know how to install it I just dont know what file is the latest/best
loffyg said:
Okay so you say fresh froyo is one of the best? I looked it up but I am confused about what to download. Any advice would be great. I know how to install it I just dont know what file is the latest/best
Click to expand...
Click to collapse
This is my situation too....as I posted above. I know how to install, but am unsure of exactly what you are recommending as to the Fresh Froyo files. Thanks again.
Well try to be brief to that understand... (my English is very bad).
They must go to the thread of Fresh Froyo and go to this page, there download the ROM latest although I recommend the penultimate that is in my signature the most recent gave me problems.
The ROM download whith the name system-froyo-us-unodex-XX-XX-XX (X are date) have to rename it to androidinstall.tgz and copy in the ANDBOOT folder then locate the kernel of their choice here, the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
For the rest follow the installation guide in NAND is here and everything should go well.
Not be as it is done for HARET but here also the Guide to install in haret. I believe with what I said is more than enough so installed android in their device.
Best regards.
Josue_181 said:
Well try to be brief to that understand... (my English is very bad).
They must go to the thread of Fresh Froyo and go to this page, there download the ROM latest although I recommend the penultimate that is in my signature the most recent gave me problems.
ROM: Fresh Froyo 2010-12-03
Kernel: 2.6.25 10-31-10
The ROM download whith the name system-froyo-us-unodex-XX-XX-XX (X are date) have to rename it to androidinstall.tgz and copy in the ANDBOOT folder then locate the kernel of their choice here, the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
For the rest follow the installation guide in NAND is here and everything should go well.
Not be as it is done for HARET but here also the Guide to install in haret. I believe with what I said is more than enough so installed android in their device.
Best regards.
Click to expand...
Click to collapse
Okay I am pretty sure I understood what you said. I have the files you suggested thanks for the help I will try it tonight.
Josue_181 said:
the most recent is 2.6.32 although I recommend 2.6.25 which is in my signature if need USB mass storage in 2.6.32 doesn't work.
Click to expand...
Click to collapse
It works in Ubuntu Linux. It does not work for Windows 7, at least that I could configure successfully.
I'm using SuperFroyo and the 2.6.32.9 Kernel and a few things I noticed to make it more stable: don't use a Task Killer and be sparing in your use of a cache cleaner. Seriously, a week of doing that has really helped things. Trust the Linux Kernel, it's not Windows. I also used Autostarts to prevent a few of the more eager apps from starting automatically post-boot, but that's optional.
Prowess said:
aceoyame,
How would it be possible to get the battery enhancements into the git? We need help!
Click to expand...
Click to collapse
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
So it loses a lot of those tweaks but I can say 1 thing about cm6.1 and 7 so far, they are getting rather large themselves, I can look into cm7 for hero and find atleast 10 apks that just take up space or are only good once
aceoyame said:
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
Yeah that is true, it's why I made a barebones.
goducks3620 said:
It works in Ubuntu Linux. It does not work for Windows 7, at least that I could configure successfully.
I'm using SuperFroyo and the 2.6.32.9 Kernel and a few things I noticed to make it more stable: don't use a Task Killer and be sparing in your use of a cache cleaner. Seriously, a week of doing that has really helped things. Trust the Linux Kernel, it's not Windows. I also used Autostarts to prevent a few of the more eager apps from starting automatically post-boot, but that's optional.
Click to expand...
Click to collapse
Does seem contradictory as to not use a task killer, the task killer close applications that are open and if you don't use are accumulating and this put slow the phone, the APP autostarts manager if I heard but none that worked well in my Vogue, which do you use?
aceoyame said:
I cannot as I do not have Clemsyn's kernel so I cannot commit his fixes for stability to git. As far as the git kernel goes it already has those fixes.
Also with fresh froyo or any AOSP build you will not have as much speed since it does not have all the Cyanogen Mod tweaks.
Click to expand...
Click to collapse
Using this kernel modified with atool I may obtained the benefits mentioned in the battery life?
aceoyame said:
Yeah that is true, it's why I made a barebones.
Click to expand...
Click to collapse
even with barebones, the cm settings along with the now statistic reporting and updater (which cause FC's if removed) are still pretty huge. i have grown to like cm7 on my hero but with having so much stuff commited to the project as much as i hate to say it, there is starting to be alot of ::gulp:: bloatware
Josue_181 said:
Does seem contradictory as to not use a task killer, the task killer close applications that are open and if you don't use are accumulating and this put slow the phone, the APP autostarts manager if I heard but none that worked well in my Vogue, which do you use?
Click to expand...
Click to collapse
You don't need a task killer. The newer versions of Android will shut down apps that aren't being used if the resources are needed elsewhere. If you run a Advanced Task Killer or something similar, it will use system resources shutting down apps that then re-open themselves, which the task killer will again kill. It drains the battery and makes the OS unstable. Uninstall your task killer for a few days and see if it helps.
I use Autostarts because it fixed a problem--the music player started randomly. I also use it to prevent some apps from starting up but it is probably not necessary.