The A500 has keypress feedback sounds which I like, but I wish they were a little quieter. There is only an On/Off toggle in the settings, and the volume of the sounds is not affected by the 3 volume settings on the tablet.
Since my tablet ia rooted, I decided to experiment with trying to replace the sound files with copies modified to have a lower volume (using Nero Wave Editor on my PC).
I found the files are ogg-vorbis format, and stored in /system/media/ui. I backed them up to the SD card, then copied them off to my PC, did the volume voodoo, and copied them back to the above location.. The end result of my testing is that:
1 - a reboot is necessary to effect changes to those files
2 - the tablet doesn't like those files to be changed.
When things did not seem to be working out, I decided to restore the backups to the original file locations. But even after rebooting, and also trying toggling the keyboard sounds on and off, the tablet began malfunctioning in the attempt to play the sounds while typing. I had to restore a nandroid to get the original sounds working again.
I'd like to learn why this did not work. I suspect it has to do with file permissions, and/or formatting, because every time I copied the edited files back to the tablet by USB it warned that they might not be playable. That reminded me of how, when dealing in the past with some PDAs, files had to be ''converted'' for their use, even though they retained the same identical file name extensions. Might that be the case here?
Related
I've been having an issue with my device. Once every week or so, something happens to my 16 GB SanDisk memory card. Exactly what happens I can't tell you, but it can be stuff from Media Player not beeing able to add files to the library (but plays them fine if you open them manually), to the phone freezing after entering PIN upon start-up. Sometimes it freezes randomly, and I have to remove the SD-card. Whenever this happen, using my card reader and running Vistas error-checking sorta helps it, or if I can isolate a file that causes a problem (not a program, any kind of file) and delete it, it usually works.
But, why does this happen? I never take the card out of the phone, except when trying to fix the errors. I sync over Bluetooth and USB, I've used different ROMs (I think, I've flashed quite a few recently so can't tell for sure), I've used diffrent line-up of programs, but it stills keep acting weird. Any clues? It's quite annoying. I didn't search the forums, since I honestly don't know what to search for. Any clues or search strings are most welcome! Thanks!
Forgot to mention, I'm currently running CRC's latest stable, but, as I said, I don't think that's the problem.
same thiong happened to me
My mem card started showing up files with some weird names, other files were unaccesible, programs stopped responding and the phone would freeze until I took out the mem card. What I id to fix the issue was, took out all the vital info (keep it minimal cuz there might be a corrupted file and we dont want to transfer that one to the phone again. format your memory card using a "low level" format application http://lmgtfy.com/?q=low+level+format+freeware+download+sd&l=1 then pop it back in again and the phome will format it, and transfer your old data back. This happened to me a while back and havnt had a single issue sience the low level thingie. Hopes this helps
I'm afraid this is a common enough problem and has been written about many times. Causes vary from software errors, switching off before all data is written or even physical contacts between phone and card (some evn say different brands of card work better).
If it happens that you see corrupt file names do not continue using the device or open programs or trying to delete data. Imediately perform a soft reset, this can recover (sometimes) the corrupt FAT file and save data.
The inability to save Media Player files to the library is an un-related issue and is a known software issue. You can overcome the issue by deleting the msmetadata file (search this forum for more info). Unfortunately it's something you may have to do fairly regularly.
Mike
I've looked through this site and others about rooting my Droid X and it seems easy enough. I'd like to do it to solve a few problems I've had with my X since it was released.
Namely, (1) I want access to the internal phone storage to remove bloatware, save pictures/ringtones, etc. (2) Fix the issue of randomly deleted pictures from my SD card. (3) Run custom (non blur) UIs, among other things.
I've already started using Launcher Pro, so my phone's appearance is pretty close to acceptable. My X still deletes pictures, though, which apparently isn't as wide-spread as I thought...
Will rooting my phone fix any of these issues?
(1) If you root you can remove bloatware (though freezing it is a better option), I don't know what you mean by saving pictures/ringtones - you want to store it on internal memory? (2) Not sure about the randomly deleted photos. I used to have that issue from time to time, but read that it happened b/c I wasn't unmounting my phone from USB mode before disconnecting it from my computer. I unmount every time now and haven't had that issue since. Could just be a coincidence since it was a sparse occurrence anyway. (3) Rooting will let you install and run ROMs, which will give you custom UI's as far as changing the status bar icons and whatnot.
Personally, I'd recommend Fab's ApeX ROM. It kills the bloatware and changes the Blur theming throughout from Blur to Gingerbread.
Yeah, I want full access to the internal memory. Everytime the SD card is in use by the computer or my car stereo, I can't take pictures and it goes to the default (read: crappy) ringtones (which I'd like to delete anyway). I'd like to store camera pictures and ringtones on the internal memory.
I've been unmounting before I disconnect my phone and I have even been using the wall wart to charge it, when I don't need to modify data. It has lost my pictures, namely cd cover art, even after that. I probably forget sometimes, or someone else unplugs the phone. The only other conclusion I can think of is that it still can happen when I unplug my phone from my car stereo USB port.
I can say for sure rooting the phone will not cure the deleting pictures off the SD card. Mine has done it three times now. The first couple of times I chalk it up to me since one time I did install a themed gallery app. But the third time I know for a fact the photos where there one day and gone for the next. There is a great big long thread at the Moto DX forums on this problem and not a single peep from Moto in the thread on the subject.
I've also read (here I think) that apps like picture gallery will not be able to see the photos on the internal memory so you won't be able to view them on the phone. Same goes for music I think. Something along the lines of the apps don't have Super User rights so they can get into the internal file system. I could be wrong on this part but I know I did read it.
As the other post suggest it is better to freeze the bloat instead of deleting them. If the bloat is missing the phone will not update should Verizon push more updates out. Of course once you root you can install a ROM and not worry about the updates. Just be sure to make a backup before installing the ROM so you can go back if you need or want to.
Also try changing the USB connection to Charge only. That should keep the SD card from mounting when plug the phone into a PC, not sure about the car mount though since I don't have one.
fasthair
After updating to EB13 (OTA), my phone seems to lose the ability to play ringtones, notifications and alarms sometime during charging. Interface and game sounds still play and a reboot will bring back full functionality.
It's particularly strange because if I temporarily plug the phone in for a brief charge (an hour or so) everything works fine. It manifests only while the phone is charging overnight. It fails to play the wakeup alarm and incoming calls and texts are completely silent, even if you try to play or change them from the settings.
Any ideas on how to fix this?
Did you try a hard reset yet? If not try that, if all else fails then I would suggest wiping the phone and loading Froyo either via odin, or from the .exe file from the Samsung site
I played with the phone most of yesterday and I'm still having the same issue. I the stock/deodexed/rooted EB13 and TrulyEpic in addition to the OTA Froyo update that the problem first manifested on. If I charge the phone to 100% battery, media files on the SD card are suddenly unrecognized. Media files that are part of the ROM and on the phone itself still play fine. A reboot or rescan of media solves the problem, but it returns as soon as the battery is fully charged. When I try to play the files through the default media player in those ROMs, it says that the file type is not supported. I've tried both ogg and mp3 files.
The problem started occurring right after my phone received the OTA Froyo update- prior to that, everything had been working fine.
While my alarm and ringtone issues did not seem to be affected by any battery levels, I thought I'd share just in case. After reading reports of success using this method, I backed up the entire SD card contents onto the PC, then formatted the SD card (using the option in the phone's settings), then moved the contents back onto the card. After that everything works great! Except a streaming re-buffer problem, but that's minimal compared to the boatload of issues I was experiencing before doing this. Really saved my bacon because I did not want to have to wipe the phone completely and start from scratch.
Wondering if disabling touchwiz and running with stock froyo would alleviate all the "little glitches" ppl are experiencing with eb13...anybody?
Sent from my SPH-D700 using XDA App
Just want to make sure-- you haven't manually removed the DRM apks, have you?
decalex said:
Just want to make sure-- you haven't manually removed the DRM apks, have you?
Click to expand...
Click to collapse
I didn't change anything at all. The OTA update was when I first started experiencing the problem so I figured I might have had an app that caused the issue. I was waiting for Froyo to root anyway, so I figured I would just flash a new ROM and start fresh. I first flashed the ROM in this thread: http://forum.xda-developers.com/showthread.php?t=853209 (the CWM 3.0.0.6, EXT4 version). Everything seemed to work fine, except for some issues with GPS that I wasn't too worried about. I didn't install any apps specifically because I wanted to make sure I still didn't have the media problem. It worked fine for a while but sometime after I started charging it, the problem reappeared. I clockwork flashed to the TrulyEpic ROM (http://forum.xda-developers.com/showthread.php?t=971105) and installed all the extra patches in the 2nd post as well. Problem again reappeared sometime after charging it.
It only happens with audio files as far as I can tell. I haven't tried any video yet, but I have documents on the SD card that I can open fine even while it won't play the MP3s or OGGs. My wallpapers are stored on the SD card and they appear fine. Something happens during the charging process that gimps the ability to play audio but only off the SD card.
I did reformat the SD card before the first post-OTA flash. I'm going to charge the phone from a wall outlet tonight (I've been charging off USB) to see if that makes any difference. If it doesn't, I'll reformat the SD card again and see what happens.
Took a video this morning to help illustrate the problem:
After my last post in this thread, I went back to DI18 to see if my problems would reappear. They did not, so it's almost certain that it isn't my phone. Yesterday I flashed to Syndicate and this morning I woke to a ton of missed notifications again. I check and sure enough, it won't play A/V media from the SD card again. Curiously though, while an MP3 and AVI would not play, an OGG file did play. Images and documents opened and saved fine again.
I'd really like to get this figured out. What other logs or information can I provide that would be useful to debug this issue?
ZephyrFox said:
After updating to EB13 (OTA), my phone seems to lose the ability to play ringtones, notifications and alarms sometime during charging. Interface and game sounds still play and a reboot will bring back full functionality.
Any ideas on how to fix this?
Click to expand...
Click to collapse
I don't know if you have already found the reason for this, but you don't need to reboot to fix this. All you need is to Unmount and Mount the SD card.
Good morning XDA, I've come to you this morning because of some ongoing issues with my A500. It all started a few months back when I decided to try out utorrent on my tablet, everything was running smoothly and the speeds were around 1MB/s down so no complaints there. Then suddenly my speeds drop off to almost nothing and nothing I tried short of a reboot fixed it...temporarily. Then I started noticing other things that just didn't make sense such as file downloads from the browser finishing incredibly fast only to find out the file was only partially downloaded. I've also noticed when I transfer files to the external SD or to a USB drive that sometimes the file copy/cut/paste/delete says unsuccessful using ES File Manager. Sometimes the file will transfer incredibly fast but when I look it's only partially transferred, sometimes when a file transfer fails on a copy the source file vanishes from my internal SD. Every so often when I put files on the micro SD and even a USB drive when I put it into my PC to tranfer files that way windows wants me to scan for errors. I notice when my tablet is showing these symptoms it's also quite laggy and it appears to happen after long periods of being on even if it's been asleep most of that time.
I did a factory reset and it seemed to help but only temporarily and I have no idea what's going on. I'm running stock ICS and I am not rooted. It's just strange that I can fix all the symptoms temporarily with a reboot but a few hours later it all comes back and I have to reboot again. Thinking maybe my micro SD was faulty I put all my music on my internal SD via USB but some of my music files have been corrupted with noise and random skipping through the tracks. When I transfer large files or even large amounts of files over USB to my PC it also makes my PC BSOD but that's a whole other can of worms.
Any help would be much appreciated, anything you need from me to help diagnose the problem will be provided, thanks in advance.
-bong
92 views and nobody even has any suggestions?
To start, I'd like you all to know I've spent the better part of a day searching google and elsewhere for an answer to my quandary. If there is an answer to this somewhere that I've missed, I apologize. I am at my wit's end.
I'm running a rooted SM910P with MasterZen88's rom. I have hardly anything extra installed (just SuperSU, FX, TB). I cannot for the life of me get the system to use screen touch and screen lock sounds that I place in /system/media/audio/ui. I have adjusted the permissions for the new files as appropriate (rw-r-r), though they were properly set from the get-go anyway. I've tried restarting the phone and clearing the cache several times. No luck. Those sounds will not work - they are always the awful default sounds, even though I've explicitly overwrote those files.
It seems that the sounds in question are actually being read from somewhere else, but in my exploring I haven't been able to find them. Perhaps embedded in some of TW's apks? I don't know a whole lot about this. The most perplexing thing is that some of the sounds I replaced work perfectly fine - the pen detach/attach, the power on and power off, and even the charger connect sounds all work just fine. If anyone has any ideas or could point me in the right direction, it would be much appreciated.
As an update, I did find out that there are some raw resources in the default Keyguard.apk that I assume (I have not tested because I'm still learning how apks work) are being used in place of the /system/ui directory ones, but that's only really for the lock screen - it doesn't explain the screen touch sounds not working when replaced. Still at a loss there.