Discussion in 'Archived Threads' started by savoxis, Feb 27, 2011.
Got scripts to open browser,thats cool!
That preview is, "the Beez kneez" great work!!!
Last nite my phone started acting very odd. Kept rebooting at random. I gotn it squared away and I thought it was really screwed by the way it was actin'! Anyhoo, I have the scribble boot anim. and I noticed at the end of scribble it does this cool lookin' sunburst type flashy deal, but it doesn't do it all the time. Is that normal? Does it mean anything I should be aware of? Also, how can I use different tones for different notifications? -----------"Rock on!"
For problems like reboots please post a logcat, without a logcat I cannot even begin to tell you where the problem is.
The sunburst only happens sometimes because your phone usually boots up before the animation is complete.
Thanks, I installed Alogcat. Dumb question....wait for it........ Can anyone tell me how to use it?? That sunburst deal is really cool!
Mighty quiet around these parts lately. Maybe that means we got some more medicine being cooked up in the kitchen? Or maybe that means everything is going fine and "if it ain't broke, don't fix it!"
im used the script to move dalvik 2 cache and I noticed something odd earlier today, i wiped my cache in recovery and when i rebooted it took way long like the dalvik was wiped too. So as soon as it booted up i hit my cache mate widget it cleared 2mb. So not sure if i had wiped dalvik on accident.
So i waited all day and wiped my cache and again long reboot and when i used cache mate it cleared 3mb. And when i wipe dalvik in recovery it goes though data:dalvik and cache:dalvik and wipes just fine.
Now i know my method is EXTREMELY techinacal and accurate, jk. But what i want to know is where did my cache go and why wouldnt it clear in recovery but did with cache mate? Now this hasnt caused me any trouble just curious and dont recall (may not have noticed) this with dtapps2sd script for dalvik2cache!
That is because recovery DID wipe your dalvik-cache. Since you have moved your dalvik over to /cache its new location is /cache/dalvik-cache, when recovery wipes cache is mounts the cache partition then deletes everything it can off of it.
Recovery did sucessfully wipe your cache, the reason cachemate showed that it cleared more after the phone booted is because there are parts of cache that cannot be wiped in recovery, because they are in use by recovery.
I don't recall either, however it may be important to take note of what recovery you are using it is possible but not probable that ClockworkMod has a check to see if your dalvik is located on /cache and avoid wiping it if it is.
I also would like to ask why you have been paying so much attention to the cache, and wiping in recovery. Your cache partition is incredibly large (128mb other devices have as little as 56!) and this is why it is being used for optional dalvik-cache migration and the Script's default download location. These two things will be taking up most of your room on cache as it stands, and the script allows you to wipe the download caches within. Also the system takes good care to manage its cache space, most items stored in cache are cleaned automatically.
This being said I think there are other areas you might want to pursue if you are looking for performance enhancing. The easiest being using less apps. I have in the past used apps from the market to disable startup for applications, I find this to boost performance and battery life immensely and plan on incorporating something like this in the script soon.
I wasnt wiping to save space or try to speed things up. Everything has been running just peferct for a while now. Even on my replacment (cant OC as high but catn really notice a big difference) just had been downloading a bunch of stuff and it was more OCD than anything else. Just wanted to know more about what was acutally going on and as always thank you very much because ive learned so much here and for getting back to me so quickly.
Sorry about the lack of updates as of late I have been taking a sabbatical from coding.
I did want to get some work done but dont know what project to tackle, if anyone has any ideas let me know
And remember, almost anything is possible.
I remeber in velocity .3 or .4 you could change clock color, i kinda miss that except with a way to remove it all together to.
Removing the clock is a lot more difficult than you think. Most themes edit the services.jar to fit their needs for the theme to look right. A universal way of removing the clock isnt possible. There would have to be a different services.jar for every theme, making it a pain in the ass.
I would love to see lockscreen gestures incorporated into Velocity. You should also look at making LauncherPro or ADW the default launcher. They are far more customizable and based on a quadrant benchmark LauncherPro improves the speed of your phone. Lastly, it would be great if you could decrease the lag when switching back to the homescreen from a running application. In terms of the lag I would be more than happy to send you a logcat.
Yeah, the lag factor seems to be my main looming vex at this point! I have Logcat and would be stoked if someone could explain to me how that works. Sorrry, I've just never messed with it. Thanks guys!!
Do you have widgets moved to your sdcard that are in use on the launcher? That would cause some lag. Also is it only certain applications? I cannot seem to reproduce this, a logcat may be crucial.
As far as alt launchers, I do plan on having a tool in the script to remove launcher2 and put in adw as default, but for theming purposes I think we will keep launcher2 as the one that ships with the rom
Has anyone noticed that in portrait, it's gingerbread dock, but in landscape its froyo
I do not have any widgets on my SD. In terms of the logcat I will do one later, I'm a bit busy right now. Thanks Oh, and I have noticed that it happens with most applications, but only if I use them for an extended period of time.
How/where do I send logcat?
So how bout that velocity script guys? Haha
Best thing since sliced bread.
I cleaned up the thread a little.
Please note I have put a new update to 25 out, this will make sure you have enough room to avoid any "catastrophic events" when odexing. ofcourse make a nandroid before odexing, or moving dalvik like the script says
Comming soon is a way to have th script automatically boot to recov and amke you a nandroid!
If you used alogcat, you can save a copy of it to your sdcard, then you can open the scripts and go to contact developer, make sure to attach the logcat to the email, this goes for any of you having problems, a logcat and a brief description of the problem will get these errors fixed quickly
Yeah its I just noticed its still like that in the beta, thanks for pointing it out!
Well that was...... interesting.
Glad to see it was cleaned up - it saved me some time. Let's hope there's no repeat to avoid infractions next time, as there's never any excuse for abusive language or accusations on this site. Please bear this in mind for the future.