Related
I have been wondering if it is possible to modify where programs store their external data on the SD card, but have not been able to find an answer yet.
Example...
I have the program "FolderOrganizer" and it stores it's backup data to /mnt/sdcard/FolderOrganizer. Now what I would like to do is to clean up my SD card a bit by moving all my program saves to the /mnt/sdcard/Android/xxxxx folders. This way I know where all my backups, skins and etc are located at while keeping my file structure clean.
I have been using Root Explorer to poke around and see if I can find any indication of where these programs set their external save directories at (xml files etc), but I have not been able to figure it out yet.
I bet it is something easy that I am just missing. Can anyone help out or point me in the right direction?
djstaid said:
I have been wondering if it is possible to modify where programs store their external data on the SD card, but have not been able to find an answer yet.
Example...
I have the program "FolderOrganizer" and it stores it's backup data to /mnt/sdcard/FolderOrganizer. Now what I would like to do is to clean up my SD card a bit by moving all my program saves to the /mnt/sdcard/Android/xxxxx folders. This way I know where all my backups, skins and etc are located at while keeping my file structure clean.
I have been using Root Explorer to poke around and see if I can find any indication of where these programs set their external save directories at (xml files etc), but I have not been able to figure it out yet.
I bet it is something easy that I am just missing. Can anyone help out or point me in the right direction?
Click to expand...
Click to collapse
No... it's not something you're just missing... there is no standard and as a result it's almost impossible to achieve what you're aiming for. I too wish for the same, everything simply under <sdcard>/android/ ...
Some apps are hard coded in their code, some allow the user to select, some store in /data/data/xxx/shared_prefs/ - it's a lottery.
djmcnz said:
No... it's not something you're just missing... there is no standard and as a result it's almost impossible to achieve what you're aiming for. I too wish for the same, everything simply under <sdcard>/android/ ...
Some apps are hard coded in their code, some allow the user to select, some store in /data/data/xxx/shared_prefs/ - it's a lottery.
Click to expand...
Click to collapse
Thanks for the response. That is a bummer though, I was really hoping to be able to tell everything where to write to. I currently have a ext4 partition on my SD and that is where all my apps install to... if I can't tell the apps where to save on my SD partition, it would be nice to at least move it all to the ext4 partition.
There is crap all over on my SD card and my OCD is starting to kick in!
Yeah, I know the SD card can get messy... it's really stupid and annoying... Unfortunately, there is no SD card data saving guidelines for developers... and writing to an ext partition is completely out of scope for market apps because not all users have ext partitions... it would be nice, though, to have apps save data under one common folder... say /sdcard/data or /sdcard/Android... maybe we need to petition developers or Google!!
I agree with the saving to and ext partition. I just think it is silly that you can't at least specify a directory to save external data. I know some apps allow this, but I guess that if Google forced a change then everyone would have to change their code.
I wonder what would happen if you took out your SD and tried running those apps. Where would they write to then?
djstaid said:
I agree with the saving to and ext partition. I just think it is silly that you can't at least specify a directory to save external data. I know some apps allow this, but I guess that if Google forced a change then everyone would have to change their code.
I wonder what would happen if you took out your SD and tried running those apps. Where would they write to then?
Click to expand...
Click to collapse
Apps that require the sdcard for storage will usually either give an error when run without an sdcard or just not work at all.
I am also pretty anal about my storage and neatness, and I have given up on my sdcard being organized. What I have done is create folders with capital first letters to bring them to the top of the listing when browsing by default sort, at least I can find what I want easily without sifting through all the data folders..
That is pretty much what I have done. I guess it it better than nothing. If I knew more about programming I would try and build something to look for and modify those paths. I just never really understood/got into the whole programming thing... that is why I ended up in Infrastructure. lol
djstaid said:
That is pretty much what I have done. I guess it it better than nothing. If I knew more about programming I would try and build something to look for and modify those paths. I just never really understood/got into the whole programming thing... that is why I ended up in Infrastructure. lol
Click to expand...
Click to collapse
I'm with you there, long time (20+ years) building and repairing pcs, 0- years programming.
As far as building something to modify the paths used by programs accessing the sdcard in Android, that seems a nearly impossible feat. Each program would have to be modified, requiring reverse-coding (baksmali) each one individually, modifying the code, and recompiling (smali). This would also require re-signing and reinstalling each application, making updating from the market impossible, and would take a lot of work.
Due to the fact that applications are "sandboxed" (so to speak) in Android, I wouldn't think there was a global %externaldata% path variable that can be modified from /mnt/sdcard to /mnt/sdcard/Android, I am pretty sure that path is set in each application.
Though, I could be wrong. However, it is worth noting that if it is a global variable, changing it would result in applications that are already properly coded to use /mnt/sdcard/Android/%appname% or /mnt/sdcard/data%appname% to instead attempt to write the data to /mnt/sdcard/Android/mnt/sdcard/Android/%appname% as they would append their string to the global variable.
I believe, all we can do is petition developers to use a more structured data path in their programs, and learn to live with disorder!
daveid said:
I believe, all we can do is petition developers to use a more structured data path in their programs, and learn to live with disorder!
Click to expand...
Click to collapse
lmao!
this is true though... at least I know that I am not alone. haha
I am definitely with you all on this. I found this post after having the same epiphany just now. There needs to be more structure to the use of external storage. These little things are what set our OS apart from say, the "forbidden" iphone...
I have actually tried digging into different apps to see where the store locations are set at and have had no luck. I guess if I knew how to program or at least modify that one part of the app I would have more luck.
Problem with that is if I modify something in an app and it gets updated, I would have to do it all over again. I guess that is the gift and curse of having such an open OS. I will post back here if I figure something out though. I have been digging into the Android OS a little more, but I am still having problems understanding how it all works underneath.
Is anyone aware of any way to force an app to stay in memory, rather than getting killed when free RAM is running low? I'm aware of how android's memory management works, lowmemkiller and oom_adj and all that, but setting oom_adj isn't persistent... as soon as you open another app it gets reset. Anyone know how to make an oom_adj setting stick? (or achieve the equivalent via some other method)?
Sure wish someone could come up with a solution for this!!
I am on Galaxy S but also very interested in this.
I found some thread where I saw explanation about how to keep default launcher in memory ( also lowering oom ) using terminal.
But I don't know how to apply same thing on any application.
I mostly need it to keep Phone.apk in memory (cached process)...
So if anyone can help that would be great.
Cheers
With the recent release of Spz0s rom and Adrynalyne getting this beat over clocked these settings are becoming obsolete. Use at your own discretion.
I recently restored my phone to stock, with basic settings, meaning I did not use any of the settings listed here. I scored a 1013 on a bench with stock everything. Now that I have VTL Launcher as stock again and have everything set back up for me, I'm scoring 1000s and 990s regularly. Again without any of these settings enabled. Which is leading me to believe that a stable system is the fastest thing when it comes to performance and benchmark scores. The settings listed below did help me out, with an unstable system. Now that I am running on a stable system, none of the settings below helped my performance or bench scores, they only hurt them. So these settings below will help anyone with an unstable system to not feel the lag of said unstability. If you try these settings and they don't do anything, or hurt your performance or score, turn them back to stock and revel at how much you rock for having a super stable system! I have also noticed that the app AUTO KILLER MEMORY OPTIMIZER virtually replaces sysctl. If you run AUTO KILLER I would suggest setting sysctl back to stock! I would recommend AUTO KILLER MEMORY OPTIMIZER from the Market to EVERYONE with a Zio. Nice app, set it to Aggressive!
FIRST OFF, THESE SETTINGS ARE ONLY CHANGEABLE IF YOU ARE ROOTED!! If you are not I cannot help you!!
I am making this thread to address performance issues with the Zio. If you have done a benchmark score with just basic settings, it's already apparent to you the Zio is not the best phone. I have found some tweaks to make the phone run faster and score better on benches.
USE THESE SETTINGS AT YOUR OWN RISK. IF YOU SCREW SOMETHING UP, DON'T CRY TO ME.
Stagefright: Stagefright is part of the stock media player that comes disabled on the Zio. Turning on stagefright will increase your benchmark score by a lot, and has also been reported to make Video Playback much better, getting rid of jumpy lagging videos.
You need to make sure you have r/w(read/write) access in your file manager. Root Explorer has r/o(read/only) and r/w. You cannot change any files without r/w access in your file manager.
To Enable Stagefright you open your file explorer(i.e. root explorer, astro, etc.) and navigate to the system folder. Open build.prop in your text editor. Scroll down to where you find stagefright. There are four settings for it grouped together near the bottom of the script. Next to each setting it says =false. You need to edit the false to say true. Once that is done, go up just slightly from that spot, there is also another spot to enable stagefright. Change that to true as well. Also notice that just above this last stagefright script, there is something about the vm.heap and dalvik cache. This is where you change your VM Heap size.
(NOTE: ENABLING THE HTTP SETTING IN STAGEFRIGHT ALLOWS FOR A RICHER HTTP BROWSING EXPERIENCE BUT WILL ALSO PUT A GREEN BAR ON YOUTUBE VIDEOS. KEEPING IT SET TO FALSE WILL AVOID THIS GREEN BAR AND SHOULD NOT AFFECT OVERALL PERFORMANCE!)
VM Heap-Not exactly sure what the technical aspect of it is, but increasing the vm.heap gives the dalvik cache more room to work with, thus making your memory faster. THIS NUMBER SHOULD NOT BE SET BELOW ANDROID DEFAULT WHICH IS 24. And should also not be set above 44. If you want to change this number, add or subtract 4 within the above values, 24-44. This can go down to 16 but you'll see the results and why I said to leave it up pretty fast.
SYSCTL- To edit these settings, open your file explorer, hit the ETC folder. Scroll to bottom and find sysctl.conf, long press and open in text editor. So far I can only say there are three settings here you need to adjust.
To edit SYSCTL settings you must first download and install the app sysctl config from the Market. After you set it up initially it can be uninstalled and leave behind the settings folder for further settings changes by manually editing or you can keep it and just use it to make the changes.
First is MIN FREE KB. This number will not be the same for everyone, although I can tell you setting this number above 4096 seems to slow the system way down. Although you may try any of the following numbers..
1536, 2048, 4096, 5120, 5632, or 6144.
These are the only numbers I would suggest using as they are parameters that came out of the phone itself.
sys/module/lowmemorykiller/parameters. <----DO NOT CHANGE the numbers in this location, they are system defined parameters and are NOT to be changed!
The second setting is vfs.cachepressure. I have this set to 10. Default is 50. Basically what I've read about this, it opens more room by setting it lower, leaving more memory free from constantly checking and clearing the cache. Read more here http://forum.xda-developers.com/showthread.php?t=523707&page=12
The Third setting is oom. It's the last value in sysctl.conf and needs to be set to 1 or 0. Instead of your phone starting to kill apps when it's out of memory, it does something else that I didn't quite understand, which is supposed to boost memory performance. Some people are seeing great results with this setting. Some people say it doesn't do anything. Seems to be specific to the user, and I have yet to find anything in common between two users who say this helps. Although bench scores are higher with it set to 1.
For these settings to take effect you must reboot your phone. Changes to these settings are only applied by a reboot, so any time you change anything, REBOOT!
If you do not know how to change settings manually, there are two apps in the market to help. VM Heap Tool will change your VM Heap for you, no need to manually edit if you don't want to. sysctl config is an app that will allow you to easily change the sysctl settings.
There is an App that will change your stagefright settings for you called Blade Buddy. I did not have a good expeience with this program and would suggest that you edit stagefright manually since it's pretty easy with a superuser file manager.
I can say with certainty that turning on stagefright and adjusting and playing with the rest of the settings that your phone will turn in to a beast compared to how it came out of the box.
As far as battery performance goes, I've noticed a 10-15 percent increase(estimated) over the life of a charge(depending on amount of usage and type). I have noticed more battery use. But not so much that these settings wouldn't be worth using. I gave numerous variations of these settings tries over 2 very long months of restarts and three different benchmark programs. Any additional information or discoveries are welcome.
If this helped, please hit Thanks!!
Muchos Gracias to everyone in #openzio as always. Spz0 n Mattix are always a big part of anything I do. They are always nice enough to save me from myself. And much thanks to anyone that helps out with the Zio at all. Lets own this phone!
Nice write-up bro.
Well, good guide. Hopefully Kyocera calls me back in regards to the kernel source code so we can really overclock this thing.
Sent from my Zio using XDA Premium App
Their lawyer in San Diego got a hold of me on Facebook. Asked me to call her back. Three calls and no dice. Waiting on her response now. Hopefully soon. She said they are "working the bugs out". Which is a load of BS since we have phones in our hands, the source is done. They just have to give it to us and I told her bluntly just that.
Tell them to call me lol, I want the source. Give us the source!
Sent from my Zio using XDA Premium App
So what happened to getting it? Teacher not know the right trick? Have you heard about using git to get the source? I dunno what git is but it may help? Ever heard of it?
Sent from my Zio using XDA Premium App
http://en.wikipedia.org/wiki/Git_(software).
Google is your friend???
Also, I don't have a sysctl.conf file. At least not where you said it is or one that root explorer can find...
Yeah if I actually understood any of that I wouldn't be asking.
Ok here is the best benchmark average I have gotten so far. These are the settings I used to achieve it.
Avg Benchmark - 795
High - 900 (omitted from average)
Low - 710 (omitted from average)
Avg with high and low only changed by 6 points.
Sysctl Support - Enabled ( I am using the Sysctl app form the market.)
Min free Kbytes - 4096
Dirty Ratio - 80
Dirty BG Ratio - 40
Oom Allocating Tasks - Enabled
VM Heap Tool - VM Heap set to 36m
Stagefright settings are all set to "True"
What we need to know now is what setting are going to speed up the UI. Like cutting load times on FB and other apps, what is making the phone just lightning fast? Doesn't seem to matter too much as long as you don't go above 4096. Finally started to see some system lag with 8192. We need to figure out what makes the phone the most responsive, fastest, beast of a phone.
Messing with the radio numbers only seems to slow me down. And still can't really find anything on what vm.swapiness does either.
sinisin said:
What we need to know now is what setting are going to speed up the UI. Like cutting load times on FB and other apps, what is making the phone just lightning fast? Doesn't seem to matter too much as long as you don't go above 4096. Finally started to see some system lag with 8192. We need to figure out what makes the phone the most responsive, fastest, beast of a phone.
Messing with the radio numbers only seems to slow me down. And still can't really find anything on what vm.swapiness does either.
Click to expand...
Click to collapse
Well, I have also downloaded Link2SD from the market and put every app (except system apps) on the SD card and That has given me a little over 100MB free on phone storage and I am using Memory booster lite to free up memory on the phone. All of these things have made a huge difference in the speed and performance of the phone including page load times. (facebook opens and loads almost instantly).
Be careful. Don't move things like Widgets that need to refresh or themes for your launcher or the launcher itself. Seems fine at first until you run for a while and Widgets stop and launcher always reloads.
Sent from my Zio using XDA Premium App
Are you on Wi-Fi while opening apps or 3G and if 3G how many bars?
Sent from my Zio using XDA Premium App
Using Root Explorer /ect/sysctl.conf I'm not seeing this file...
sinisin said:
Serious changes coming soon. New numbers up for min free KB below already.
Stagefright: Stagefright is part of the stock media player that comes disabled on the Zio. Turning on stagefright will increase your benchmark score by a lot, and has also been reported to make Video Playback much better, getting rid of jumpy lagging videos.
To Enable Stagefright you open your file explorer(i.e. root explorer, astro, etc.) and navigate to the system folder. Open build.prop in your text editor. Scroll down to where you find stagefright. There are four settings for it grouped together near the bottom of the script. Next to each setting it says =false. You need to edit the false to say true. Once that is done, go up just slightly from that spot, there is also another spot to enable stagefright. Change that to true as well. Also notice that just above this last stagefright script, there is something about the vm.heap and dalvik cache. This is where you change your VM Heap size. (NOTE: ENABLING THE HTTP SETTING IN STAGEFRIGHT ALLOWS FOR A RICHER HTTP BROWSING EXPERIENCE BUT WILL ALSO PUT A GREEN BAR ON YOUTUBE VIDEOS. KEEPING IT SET TO FALSE WILL AVOID THIS GREEN BAR AND SHOULD NOT AFFECT OVERALL PERFORMANCE!)
VM Heap-Not exactly sure what the technical aspect of it is, but increasing the vm.heap gives the dalvik cache more room to work with, thus making your memory faster. THIS NUMBER SHOULD NOT BE SET BELOW ANDROID DEFAULT WHICH IS 24. And should also not be set above 44. If you want to change this number, add or subtract 4 within the above values, 24-44.
Phone Edit- Found numbers for min free KB. sys/module/lowmemorykiller/parameters. 1536, 2048, 4096, 5120, 5632, 6144. Assuming these are new guidelines. Will edit fully tomorrow. Don't change these settings. They are system parameters and should NOT be changed.
SYSCTL- To edit these settings, open your file explorer, hit the ETC folder. Scroll to bottom and find sysctl.conf, long press and open in text editor. So far I can only say there are three settings here you need to adjust. First is MIN FREE KB. This number will not be the same for everyone, although I can tell you setting this number above 8192 will slow the phone down, most people report anything over 4096 slowing the phone down. The default is 2048, I would suggest going up to 4096 or 8192.
The second setting is vfs.cachepressure. I have this set to 10. Default is 50. Basically what I've read about this, it opens more room by setting it lower, leaving more memory free from constantly checking and clearing the cache. Read more here http://forum.xda-developers.com/showthread.php?t=523707&page=12
The Third setting is oom. It's the last value in sysctl.conf and needs to be set to 1 for everyone. Instead of your phone starting to kill apps when it's out of memory, it does something else that I didn't quite understand, and this should add speed to everything you do, like surfing or Facebook. Everything should load faster and smoother with this setting enabled. Remember stock value is Zero and may only be set to 1 or 0.
If this helped, please hit Thanks!!
Click to expand...
Click to collapse
Try /system/etc micro. Same thing.
Sent from my Zio using XDA Premium App
Current settings.
4096
95
60
50
Oom
VM heap 30
Stqgefright all but http
Running fast and stable. Launcher pro Orientation from portrait to landscape is faster. Home loads instantly even though I am not using a launcher from /system/app
I will be doing some more tweaks to speed this up but maintain some battery life.
Sent from my Zio using XDA Premium App
I have Stagefright fully enabled. Running 2048 Free KB. Stock radio and background. Turned oom to 0. Zoomin right along.
Sin. How did you edit sysctl.conf I can't find it in ETC
Sent from my Zio using XDA Premium App
Thanks! /system/etc still nothing. I have rtecdc_apsta.bin and void.fstab no luck still.
sinisin said:
Try /system/etc micro. Same thing.
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
Looks like we need to include sysctl.conf in the next theme update.
Sent from my Zio using XDA Premium App
Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2
Difficulty Easy - Controlling app 'net Access
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3
Difficulty Moderate - SD cache/readahead tweaking
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4
Difficulty Moderate - Overclocking
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5
Difficulty Advanced - How Android Manages Memory/apps
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6
Difficulty Advanced - Managing Apps that auto-start on boot
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.
Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any TOPAa-specific tweaks that others should be made aware of!
Update to this - I changed around how topic 4 is done. Feel free to re-read that section.
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
metho88 said:
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
Click to expand...
Click to collapse
For the pm disable stuff? If you find an app that does it, more power to you. I want to control Android directly, hence the reason I went with a script that utilizes that concept. The pm disable stuff is obnoxious I know - so if you do find an app that'll do it for you, have at it. I didn't want to add any more apps into the mix if it wasn't necessary .
Rhod400 in startup.txt
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
1edge1 said:
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
Click to expand...
Click to collapse
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
arrrghhh said:
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
Click to expand...
Click to collapse
yeah i do use the startup for topaz. Was just wondering. haha. thanx for clearing it up
Hi everybody,
after beeing so glad that Motorola fixed the blue-tint issue they punished us with 12fps video recording in low light. But mostly I shoot videos in low-light-party conditions. So I searched around a bit (I'm not a developer or anything like that) and found a way for getting back to old settings and fps:
Open /system/etc/TICameraProperties.xml
Search for <prop-framerate-range-default>12000,30000</prop-framerate-range-default>
As you can imagine 12000 is 12fps and 30000 is 30fps. So there are two steps of framerates, depending on light situations.
Change 12000 to whatever you think is good, I changed it to 20000 so I have wonderful 20fps in low-light conditions.
Restart and have fun recording good videos
Please report if it works for you. Also someone more expierenced wants to have a look at the whole file, maybe there are other tweaks that can be applied.
Thanks everyone.
Have you tried filming in low light after doing this? Did you have any issues? I'm going to a concert tonight and wanna take video, but if this will mess up the camera at all (or bring back the blue tint) I'd rather not risk it...
Yes, I tried it with almost 20 Clips, since 3 hours, everything is allright! No blue-tint or anything! It's just better low-light-fps Just try it
I will have to compare the OEM file to the Leak file. I bought 2 droid 3's (with the BOGO deal). Maybe there are some obvious differences that I can post up.
---updated----
these are stock settings I found on the OEM software of the D3.
on line 50:
<prop-framerate-range-default>20000,30000</prop-framerate-range-default>
and on line 137:
<prop-framerate-range-default>24000,30000</prop-framerate-range-default>
<prop-framerate-range-values>(24000,30000)</prop-framerate-range-values>
Izeltokatl said:
I will have to compare the OEM file to the Leak file. I bought 2 droid 3's (with the BOGO deal). Maybe there are some obvious differences that I can post up.
Click to expand...
Click to collapse
I have stock still, and I just pulled the file up to see what the default was for this property on stock. It is 20000, so the OP set it to the original default.
Rotkaeqpchen said:
Hey together,
after beeing so glad that Motorola fixed the blue-tint issue they punished us with 12fps video recording in low light. But mostly I shoot videos in low-light-party conditions. So I searched around a bit (I'm not a developer or anything like that) and found a way for getting back to old settings and fps:
Open /system/etc/TICameraProperties.xml
Search for <prop-framerate-range-default>12000,30000</prop-framerate-range-default>
As you can imagine 12000 is 12fps and 30000 is 30fps. So there are two steps of framerates, depending on light situations.
Change 12000 to whatever you think is good, I changed it to 20000 so I have wonderful 20fps in low-light conditions.
Restart and have fun recording good videos
Please report if it works for you. Also someone more expierenced wants to have a look at the whole file, maybe there are other tweaks that can be applied.
Thanks everyone.
Click to expand...
Click to collapse
AWESOME!!
how would i go about doing this? do i need to root???
If someone would kindly walk me through this i woul be more than apprecitave
edit: hell, ill even paypal you five bucks XD
Those instructions are as easy as it can get. If you have no idea on how to follow it, you should turn away and get someone else to do it for you.
Sent from my DROID3 using Tapatalk
Izeltokatl said:
and on line 137:
<prop-framerate-range-default>24000,30000</prop-framerate-range-default>
<prop-framerate-range-values>(24000,30000)</prop-framerate-range-values>
Click to expand...
Click to collapse
The second values are for the frontfacing camera I guess.
Thanks for the values!
@Moderator: Please move this topic to general! Thanks!
eXecuter.bin said:
Those instructions are as easy as it can get. If you have no idea on how to follow it, you should turn away and get someone else to do it for you.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Wow, no need to be a tool. Let me explain myself. I have no idea if i have to be rooted or not, im assuming yes. From there i have no idea how to open /system/etc/TICameraProperties.xml or what program i would use to do so.
Thanks for being a proud upstanding member of this community, always ready to stand up and help another user. your mother would be proud.
`Ghost` said:
Wow, no need to be a tool. Let me explain myself. I have no idea if i have to be rooted or not, im assuming yes. From there i have no idea how to open /system/etc/TICameraProperties.xml or what program i would use to do so.
Thanks for being a proud upstanding member of this community, always ready to stand up and help another user. your mother would be proud.
Click to expand...
Click to collapse
Root Explorer is the de facto standard. If you want a free alternative, give File Expert a try (my issue with this one is it is shady when extracting zip files, Root Explorer is better IMO). Yes you need root because /system has to be mounted as r/w to edit the file.
Additionally: To open a file like a xml file you have to longpress on a file in root explorer and choose "open in text editor".
sic4672 said:
Root Explorer is the de facto standard. If you want a free alternative, give File Expert a try (my issue with this one is it is shady when extracting zip files, Root Explorer is better IMO). Yes you need root because /system has to be mounted as r/w to edit the file.
Click to expand...
Click to collapse
Okay cool. I see it in the market for 3.99. ill support the dev and buy it.
now i have no idea how to mount /system as r/w to edit the file. does rootexplorer help with that or let me input commands?
sorry for the questions as i have not done this before. everyone has to learn somewhere.
`Ghost` said:
Okay cool. I see it in the market for 3.99. ill support the dev and buy it.
now i have no idea how to mount /system as r/w to edit the file. does rootexplorer help with that or let me input commands?
sorry for the questions as i have not done this before. everyone has to learn somewhere.
Click to expand...
Click to collapse
In root expolorer, once you get to the directory in question, there is a R/W link in the top right hand corner, click it and it will make it Read/Write. At that point you can make changes to files within that folder (directory).
I would suggest making a backup of the file. I personally saved a copy on my SD card, mounted it, edited in my text editor on my PC and then copied back. Do this because its easier to edit files on a PC than on the phone, and so I dont mess up any other items. That and I have a permanent backup in case I screw something up.
I made the changes last night but haven't bothered to test yet. will do it tonight.
Izeltokatl said:
In root expolorer, once you get to the directory in question, there is a R/W link in the top right hand corner, click it and it will make it Read/Write. At that point you can make changes to files within that folder (directory).
I would suggest making a backup of the file. I personally saved a copy on my SD card, mounted it, edited in my text editor on my PC and then copied back. Do this because its easier to edit files on a PC than on the phone, and so I dont mess up any other items. That and I have a permanent backup in case I screw something up.
I made the changes last night but haven't bothered to test yet. will do it tonight.
Click to expand...
Click to collapse
when I long pressed and opened it in text editor, it automatically created a .bak of the original. Don't know if everyone will experience this, so like the above says, make a backup.
thanks guys. seems pretty simple. ill give it a shot.
im gonna oneclick root and hop to it!
It worked!!! Thank you!!
thankgod i can actually have non bluetint video/pictures and still keep my 20fps low light.
anyone try increasing the lowlight past 20??
btw my guess on why they decreased it to 12000 is maybe the processor has to work harder with the new white balancing and to even it out they lowered the fps.
Glad to hear that, I was so happy like you are now
Rotkaeqpchen said:
Glad to hear that, I was so happy like you are now
Click to expand...
Click to collapse
Thank you very much.
Someone get this man a beer.
Thanks ^^ but this forum has given me so much stuff and modifications, the real developers deserve the beer! But thanks anyway
Hi Guys,
I've fiddled around with the Camera application and found some other tweaks that some of you might like.
This goes hand in hand with Rotkaeqpchen's low light FPS tweaks above.
I've also modified the Camera apk to increase image quality above 100% which has a bug of fc on the Panorama mode so im trying to work that one out, modded application is attached if you wish to try it called MODDED-Cam-installer.zip, once extracted from zip copy to system\app folder on your phone.
Some more digging around found the following:
build.prop - found in System folder
----------
Increased video bitrate past the default 15mbp to over 30mbp is possible and looks really nice at 1080P, no stuttering with frames and in high quality audio.
Enabled slow and fast motion recording in the camera menu.
mp4(extention),h264,30(fps),30000000(bitrate),aac,128000,44100,2(audio channels)
ro.media.camcorder.1080p=mp4,h264,30,30000000,aac,128000,44100,2
ro.media.camcorder.720p=mp4,h264,30,15000000,aac,128000,44100,2
ro.media.camcorder.d1NTSC=mp4,h264,30,6000000,aac,128000,44100,2
ro.media.camcorder.vga=mp4,h264,30,4000000,aac,128000,44100,2
ro.media.camcorder.cif=mp4,h264,30,1500000,aac,128000,44100,2
ro.media.camcorder.qvga=mp4,h264,15,500000,aac,64000,44100,2
ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1
ro.media.camcorder.mmsres=qvga
ro.camcorder.zoom=true
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true <- This will enable fast and slow motion recording.
media_profiles.xml - found in Etc folder
-----------------
Increasing the following Max values will enable higher settings for the above to work:
<VideoEncoderCap name="h264" enabled="true"
minBitRate="64000" maxBitRate="30000000"
minFrameWidth="176" maxFrameWidth="1920"
minFrameHeight="144" maxFrameHeight="1080"
minFrameRate="1" maxFrameRate="120" />
TICameraCameraProperties.xml - found in Etc folder
-------------------------------
Still unknown as to what this file does, first appears to be info only on settings for the front and back cameras, as i've not had much luck in changing values like sharpness/brightness/contrast, file format etc.
Only thing I've been trying out is the low light tweaks, mine are currently set to:
<prop-framerate-range-values>(5000,30000),(10000,30000),(12000,30000),(15000,30000),(25000,30000),(25000,120000)</prop-framerate-range-values>
and
<prop-framerate-range-default>25000,30000</prop-framerate-range-default>
I don't know why all this couldn't have just been in the camera app like every other company, Motorola doesn't like to make anything easy.
Have fun.
Edit:
Easy Clockwork installers attached.
- MODDED-Cam-installer.zip - Modded Build.prop, Modded Media_profiles, Modded TiCamera and modded Camera app installer.
- ORIGINAL-Cam-installer.zip - Modded Build.prop, Modded Media_profiles, Modded TiCamera and original (dedexed) Camera app installer.
- DEFAULTS-Cam-installer.zip - Default Build.prop, Default Media_profiles, Default TiCamera and Default Camera app files installer.
Edit2:
Added 5.7.894 camera mod, increase speed, new icons and high image quality, Panorama mode has a bug.
Added huge APN list for GSM using countries, no more manual adding apn's.
Updated for 5.7.894:
-gps.conf
-media_profiles.xml
-TICameraCameraProperties.xml
-build.prop
Edit3:
DarkDroid rom power menu with reboot and screenshot functionality, camera quality mods etc, do not install this file unless you are running the Dark Droid rom 1.01-01/20/12 with framework 5.6.890, infact just download dpwhitty11's rom instead here:
http://forum.xda-developers.com/showpost.php?p=18424016&postcount=1
Instructions for ORIGINAL-Cam-installer.zip, MODDED-Cam-installer.zip and DEFAULTS-Cam-installer.zip:
1.Place the desired zip on your external sd card.
2.Restart phone into clockwork mod.
3.Choose install from zip.
4.Choose zip from sd card.
5.Go back to main menu and select reboot phone, done.
Manual copying to the desired directory must be done with these 5.7.894 files:
-BlurCamera5.7.894mod.apk
-apns-conf.zip
-gps.conf.zip
-media_profiles.zip
-TICameraCameraProperties.zip
-build.prop.zip
-smc