Related
Can't see why this is the case (but it obviously is) as long as I have lots of free disk space and not many apps running at the same time. Any logic in this?
I've been experiencing the same issue and wondering the same thing...
Sent from my Samsung Galaxy S GT-I9000 using Tapatalk Pro
There seems to be several things causing this, but the two key issues are:
The moviNAND (the internal flash drive/"SSD") firmware seems to have an issue with fsync() taking extremely long. E.g., it slows down whenever a file is written/updated on the internal storage.
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
There are several topics on these issues in the Android Development forum. There are also several "lag fixes" trying their best to overcome these issues. Go check them out
Einride said:
There seems to be several things causing this, but the two key issues are:
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
Click to expand...
Click to collapse
We have no idea if that is ACTUALLY true.. Just because fsck picked some things up on 1 phone, doesn't mean it happens everywhere.. Furthermore, it doesn't mean the problems detected affect operations
that has no truth at all about more apps slowing down the phone, my phone is the prove
Before jpk i didn't noticed slowdowns with aprox 100 apps, now i do on jpk =/
Prolly that all pictures/links/info stays in his workmemory?
probably cause some of them run in the system memory or run at startup
KaliKot said:
probably cause some of them run in the system memory or run at startup
Click to expand...
Click to collapse
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
AllGamer said:
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
Click to expand...
Click to collapse
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Oletros said:
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Click to expand...
Click to collapse
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
bonehooch said:
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
Click to expand...
Click to collapse
Utter ****e? Why?
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
AllGamer said:
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
Click to expand...
Click to collapse
With autokiller the phone is still laggy.
And please, stop thinking I'm stupid or I don't know a **** about smartphones, ROM's changing, firmware or knowing how a phone must run.
AFAIK this topic and its responses are for the OP
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
TMReuffurth said:
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
Click to expand...
Click to collapse
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Autokiller and task killers are not the solution here! Quick lesson on Android, and why having even A SINGLE BAD APP is going to ruin your whole phone!
Android has something called an 'Intent'. In order to start an app, an intent is made by your launcher or a button you press, and the Android system reads this intent and works out what app it needs to start up.
There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it. This means that an app can register to listen to all sorts of events, such as battery level changed, application start, or a tons of other things. Even if the application is closed, if it is registered as a listener, Android will start it right back up so it can deal with the intent. If the intent comes every 5 seconds, Android will run this app every 5 seconds even if you have a taskkiller killing the app.
The only real solution is to not install apps which are bad! Finding bad apps is a real mission, too. Hopefully in the future, utilities will be available to let us track down these terrible apps, but till then, you'll have to work it out yourself.
yiannisthegreek said:
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Click to expand...
Click to collapse
No need for Root to use all features of Autorun Killer. I would disable only the apps you know and which you do not need at startup and running in background, such as (in my case) Paypal, App Center from Androidpit, Daily Briefing, Photoshop Express, Word Press, TweetCaster, etc.
Every of these apps works normal, even when deactivatet on startup.
So unless you do not disable system apps (must be previously set enabled in settings) you are safe.
RyanZA said:
(...)There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it.(...)
Click to expand...
Click to collapse
Is there any possibility/app to show what is registered for which app?
watching the apps
Samga said:
Is there any possibility/app to show what is registered for which app?
Click to expand...
Click to collapse
There is an app called Autostarts at 0.95$.
It shows what is launched au startup, when you enable/disable wifi etc.
It think it gives insight on how apps seems launching out of nowhere.
I also reccomend Watchdog Task Manager Lite, the free version.
It does not kill anything, but notifies and logs the bad apps that consumes over a certain CPU percentage.
This has been pissing me off for quite some time. I hear Android's RAM is managed internally and that there's nothing to worry about - task killers are redundant.
I understand the logic, I understand the reasoning.
It just won't receive any of my understanding because this is frankly wasting too much time in the course of a day.
What happens due to this "internal management" is that programs I want to keep alive and return to in the state I left them isn't happening. Let's take Aldiko (or we could say the browser, pdf reader, music player, take your pick), the ebook reader; it can take up to 30 seconds to load a book, uses a lot of RAM, and opens at the page I was at.
Now imagine that I'm getting a phonecall, or an SMS, maybe even need to check the mail, or the bus-times, perhaps needing to use the browser. The RAM dips below the line and Android kills a process. 3 guesses to which process it killed to free RAM? You got it, Aldiko. The one that it took me 30 seconds to open. The one I was using, the one I actually cared about.
Checking the list of programs running I see that Aldiko's there, just not with an open book. What I also see is 987645984549 programs that I don't use, never activate, and serves absolutely no purpose on the phone, waiting for me to start them again for the second time in the phone's lifetime (which isn't happening). They're hogging RAM for some godforsaken reason, still sitting there doing nothing, not being used. Yet it killed Aldiko. Or any of the other processes I actually need, want and use.
Why does Android behave so ridiculously? How can I fix this? Installing a task killer helped somewhat, it keeps the stupid programs off so it doesn't close the ones I need all the time, yet the more frequently I run it (increasing the uptime for Aldiko), the harder it is on the battery because the programs keep popping up. Despite never being used.
Or maybe I want to use them at some point in the future, but not all the time. Not more than once a week. It doesn't matter. They shouldn't be allowed to interfere with the programs I actually use.
Is there some way for the android management to be a little less random, and a bit more like Windows Mobile, where a program stayed on as long as I wanted it to (unless there was a crash...)?
You could use Swap memory, if you REALLY want to fiddle (like what Windows/Linux/OSX does), and maybe tweak configs. It might be just possible to "swapon"
But the reason it's done is to provide quicker performance. Aldiko SHOULD be coded to remember the last book anyway, and does it REALLY take 30secs to open? That sounds like bull to me (I just tried it, and it took maybe 5 secs). Granted Aldiko could open the last book being read by default, but you could contact the aldiko developers for a setting to do that.
Either way, swap memory would be a prereq to doing this, because if you don't have enough RAM, apps will crash. So try that first
Hehe, yeah, it does take 30 secs. Maybe a big book or something. It was just an example. There's also the browser losing the pages it was on, music player losing place where played, pdf reader, and so on.
I'll check out out, but I'm not keen on rooting though.
Thanks for replying
Sent from my GT-I9000 using XDA App
Or is it just my phone?
I originally thought it was just an Android thing; A minor inconvenience that I could get used too. After helping my brother flash his Droid X and seeing how fast it completes it's scan I have to ask, what makes our phones slower?
the problem is with the file system that samsung used for our phones, you need to install a kernel where it converts it from the rfs system they used to an optimized ext 4, most of the roms come with this feature or you could just use supercrucio's kernel (Voodoo) which works best for me
whirly said:
the problem is with the file system that samsung used for our phones, you need to install a kernel where it converts it from the rfs system they used to an optimized ext 4, most of the roms come with this feature or you could just use supercrucio's kernel (Voodoo) which works best for me
Click to expand...
Click to collapse
I should have mentioned that I almost always run a lagfix.
Maybe the Droid X is just that much faster with reads, and the Captivate isn't slow.
If you have root, you can d/l rescan media root and control all that nonsense.
Sent from my SAMSUNG-SGH-I897 using XDA App
Media scan is still horrid even under custom ROMs.
Admittedly I thought it was due to the large amount of data on the slow external SDCard I have (16gig).
I want to find something where I can just disable it and run it manually whenever I want it to update.
Found an app called Rescan Media and tried it for giggles.
"Disabled" using the application - and I have to say my phone rebooted seemingly much faster - Widgets loaded and ready to use faster then I've ever had to wait before.
The media scanner will still load on boot - but doesn't re-scan your entire cards during the bootup process. And if you hit the app it will cause the Media scanner to read your cards which doesn't take very long at all since your phone is already up and booted.
Have to use it for awhile and see if it screws anything up - but I think this app is a keeper!
avgjoegeek said:
Media scan is still horrid even under custom ROMs.
Admittedly I thought it was due to the large amount of data on the slow external SDCard I have (16gig).
I want to find something where I can just disable it and run it manually whenever I want it to update.
Click to expand...
Click to collapse
See the post above yours. I tried that solution a couple weeks ago and didn't really like it, but others seemed to. (edit: just saw your previous post)
It probably wouldn't be such a nuisance if it wasn't the first freaking thing it did after reboot. Media scanning should run after other startup items... like obtaining signal, loading widgets, launcher, etc.
Or even better, have it run only when you launch the music player or gallery. I'm not sure why we would need it any other time. Or even betterest, let us set up specific folders for media so we don't need the scanner at all.
Yup I agree - Samsung strikes again at being lazy just doing a blind scan at boot up.
Since all the processes are trying to startup at the same time of the scan - it's causing the perceived lag as they are both fighting each other (for lack of a better term) for resources and I/O and takes forever for them to figure it out.
It would be nice if a Dev could create a 3rd party app that takes control of the Media Scanner - then gives us the options of only scanning certain folders and have it scheduled to run like you mentions - i.e. when <x> app loads, or after you unplug your USB, or just run it manually.
The app I posted isn't that elegant a solution but it does seem to work. My bootup time is cut in half (This is from Power Up to Usable UI Interface with Widgets loaded.).
Just nice to have considering I STILL (i.e. will never) haven't gone to AT&T to exchange my phone due to the shutdown issues I've been having. At least it's not the up to 3 minutes!! I used to have to wait for me to be able to use the phone again.
LOL.. but coming from an Apple iPhone 3G I was used to it.
it truthfully is slow... i have a sd card for more memory so it takes about twice as long than the normal.. im running darky port 8.0 with voodoo but dont see a difference..
Put a file in your folders named ".nomedia" (without quotes) that contain things like rom zips, backups, etc and media scanner will stop spending time sifting through them searching for music and photos
edit....this will also eliminate unwanted images from showing up in the gallery if you have icons or png's that you use for other purposes
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
So after some great help by gregbradley and others, I have a rooted T and now have an OTA 195 update.
However I have a couple of questions (apart from my continued quest to find a way to get the phone to save camera output in less compressed fashion.
1) Is it usual for mediaserver to be the 2nd great drain on battery after the screen and ahead of android system?
(there appear to be many web discussions on this, but I could not find a definitive answer. Mine has always been like this even before I tinkered with it, or before I put the sim in (I didn't put the sim in until after I had rooted and updated. I do not have an SD card in there yet (64Gb on order) and I have not added any new pics or movies to the stock provided ones.
2) Can you change where apps are installed? Can this be changed for Google Play apps (like xda) Is the default to install to "phone memory" rather than "internal storage". Given that "phone memory" is only ~ 2Gb, it would be good to install to "internal storage"
3) Are apps on the home screens (eg Walkman) always running, even when not in use (the walkman example is the app 4x1 icons wide and has basic controls on it)?
Many thanks as always!
icstm
some clarification I should have added yesterday...
1) quite simply I would be keen to know what type of apps call on the mediaserver process
2) I know that from the "apps" in settings" some apps can be moved, but that appears limited and no default can be set
3) when I say apps, I mean widgets and the like, not the simply shortcut icons
icstm said:
some clarification I should have added yesterday...
1) quite simply I would be keen to know what type of apps call on the mediaserver process
2) I know that from the "apps" in settings" some apps can be moved, but that appears limited and no default can be set
3) when I say apps, I mean widgets and the like, not the simply shortcut icons
Click to expand...
Click to collapse
1) Anything that needs to scan the sdcards for contents will call on the media server. After a fresh flash many apps will be collating their cache so the mediaserver may have a high battery drain, you should never worry about battery drain untill you have run a ROm for at least 3-4 days to let it settle
2) Yes, use apps such as link2sd or app2sd, free in the market. However I have not yet felt the need to do this with a 16gb internal memory
3) Thos e widgets are just shortcuts, e.g. I have a weather app set to refresh every 2 hours...it will be woring in the background whether or not the homescreen widget is on the homescreen or not.
However, do not worry about task killers, since android 2.1 the best task killer is the one that comes with the OS. The only other exception is if you install init.d scripts and supercharge scripts etc, but you may want to leave that for a bit and get used to the phone first.
So I am on the xda app, much better way to view the site than mobile browser .
However, I cannot see what you wrote when I reply.
But it relates to your last point on making customisations. And not just keyboard which prefers US spellings over UK ones .
I am thinking of tinkering with the OS files as I am very upset with the compression of photos. So I am keen by what you say just below number 3.
Sent from my LT30p using xda app-developers app
AW: [Q] Couple of days in - a couple of Qs...
Change your keyboard or even better your whole phone to UK in language and keyboard setting and it'll propose BE instead of USE.
Greg is correct, the media server goes nuts the first two to three days after (re)flashing or taking up a device. You can improve the situation by keeping your folder structure clean and neat and trash out left over files, old garbage and file system junk.
Thanks for your posts in both threads.
As for mediaserver, yes all is quiet now.
Not sure about which system files to delete at this stage, but I sure do keep a neat folder structure for my content.