Hi again, folks.
I am currently on the stock ROM that came with the tablet, but it's rooted and I have a custom kernel (Villain). I recently did the rooted 3.2 (GEN2) update and I thought it was quite cool that it added the sd card initialization sound "On The Hunt". (I like that one.) Anyway, this is my second install, and the second time that sound has just simply stopped. There aren't any options to enable the sound, but it was working before. What can I do to restore this?
Thanks for any help!
Related
Well, first post is troubleshoot post for me but need some suggestions to track down a small problem.
Had my phone for a while and have had no problems thus far till yesterday and i'm stumped.
Main Issue: In the settings menu when I click on "SD card and phone storege" I get a "Sorry! The application Settings (process com.android.settings) has stopped unexpectedly. dumpstate...yada yada yada---->[Force Close]
Every other settings entry I can go into and they all work flawlessly from top Wireless and Network to bottomSoftware Update. Only the "SD card and phone storage" force closes on me.
Last thing I did was apply Project Voodoo Update3 for Vibrant and it worked fine. I was able to check the SD card/phone storage section than. I temporarily disabled voodoo to get clockwork recovery to install and work properly so I could add the latest J16 MobileAP over my existing older MobileAP. Afterward I uninstalled clockwork. Somewhere in between all of that is when it started.
I let voodoo reoptimize back to ext4 and had the issue still. So thought disabling voodoo lagfix but made no difference. Turned off and on phone 3 times, Once without the SD card even inserted. Each time I still could not enter the SD card and phone storage section in the seetings menu. Always same Sorry! Force Close message. Just bugging me. Guessing some file may be corrupted or missing in data/cache or android settings.
If anyone can steer me in the right direction to fix than I will be happy as everything else work perfect on my phone for me. Thank you for your suggestions and thoughts. tryign to avoid wiping or redoing all my apps and settings and contacts/contact pictures etc for such a small issue.
For reference the phone has been for over a month now rooted & unlocked, t-mobile startup/shutdown logos removed, battery circular icon mod, most bloatware been gone for some time, Captivate camera app installed, J12 GPS files, J16 baseband modem installed, Mobile AP J16 installed working, did not want the whole J16 update. Rather wait for froyo or full working froyo builds later. Project Voodoo lag fix installed and running. SD card is a genuine 32Gb Sandisk not ebay knockoff.
Also in case it matters, I can use gallery and view files effortlessly, Market still installs and uninstalls applications just fine as well. So has to be something minor I would guess.
I'm getting that while setting the System and Ringer Volume (volume set via side keys work fine).
Odin JI6 (after dead OTA)
root (will probably unroot since no remount prevents removing startup/shutdown sounds)
ROM Manager loaded
Mobile AP loaded
Well, this is depressing. I tried going to system volume and ringer volume and also get the Sorry! [Force Close] their as well just as you do.
Maybe for me it is the kernel that is installed when you apply the Project Voodoo lag fix. What do you all think? Do you think removing the voodoo lagfix entirely and flashing the backup orginal kernel back on would resolve it. I don't mind but i'm really just not sure what to try before changing too many things unnecessarily.
Just fixed it. Found the cause. Since i'm not fully on J16 update; installing the MobileAP J16 version caused the problem for me cause it re does the settings layout it seems. Flashed back original MobileAP for while i'm on JFD still.
Just thought you would like to know and noticed that you also have MobileAP installed. Make sure it is the right version for your firmware...guessing J16 your on now.
I didn't apply any lag fix.
I may reload JI6 and see what that does.
Yeah, lag fix was not the cause. Definitely my fault installing the J16 MobileAP. Put back old version and I was fine. System Volume, Ringer Volume and SD card and phone storage settings all work again. But since you are on J16 maybe thought you installed old MobileAP on your phone causing your problem . But reapplying J16 update may fix it too for you. Good luck
rmeden said:
I'm getting that while setting the System and Ringer Volume (volume set via side keys work fine).
Odin JI6 (after dead OTA)
root (will probably unroot since no remount prevents removing startup/shutdown sounds)
ROM Manager loaded
Mobile AP loaded
Click to expand...
Click to collapse
im getting the same thing. anyone? if i need to update the mobile ap can you please tell me how?
rmeden said:
I'm getting that while setting the System and Ringer Volume (volume set via side keys work fine).
Odin JI6 (after dead OTA)
root (will probably unroot since no remount prevents removing startup/shutdown sounds)
ROM Manager loaded
Mobile AP loaded
Click to expand...
Click to collapse
I noticed there was a JI6 MobileAP version. I had re-installed the already downloaded JFD one. I installed the JI6 MobileAP version and no longer get a crash pulling up the volume settings.
Yesterday I needed to take a picture and used my Galaxy S. for it. After that I connected my phone to my laptop USB port and got an unknown device error. Assuming it was a driver problem I re-installed them keeping the same error.
I also got telephony problems before, after some minutes calling the other side couldn't hear me anymore and I needed to put the call on wait and back to continue the call.
Both problems together made me decide to update my Darky 10.1 Extreme edition to the latest 10.2 Extreme edition. I took my sd card out and copied the darky 10.2 zip to it using my laptop. Put it back in and used Astro filemanager to copy it to the internal sd. Because I can't use the usb port this was the only way.
Rebooted to recovery and flashed 10.2. After reboot the screen stayed at the boot screen with green Darky text for half an hour without doing anything. No vibrate or anything. I did read some info about 10.2 before i downloaded it but missed the lagfix point. Tried to get into recovery and luckily that worked. Turned on the lagfix, did hear the computer voice 2 or 3 times and last time it said lagfix was enabled. Rebooted to recovery again, checked lagfix was on, also for next boot, and flashed 10.2 again. Same problem, hangs at bootscreen.
Turned lagfix off again and flashed the old 10.1 again. Same problem again, this time only bootscreen with white SG text and both button lights on. Nothing for the rest. Flashed back, after lagfix enabled, to 10.2 again without luck. Again bootscreen only.
Someone knows how to fix this? Because of the usb problem I can't use Odin. I did read somewhere now there might be a cable problem or a dirty usb connector on the phone. Checked the connector visually and can't see any dirt, I also keep it closed when not using it.It does load the battery also when connected to my laptop. At least it did when I first got the unknown device error.
1) USB Error
I am not sure you have Only installed the USB driver alone or Kies it self. Anyway, try this http://support.microsoft.com/kb/315265. Scandisk with delete currupted file on your disk drive and replace with default window file. You can reinstall your driver/Kies on your laptop after scandisk complete.
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
from.insider said:
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
Click to expand...
Click to collapse
If your boot takes so long, you doing something wrong
First boot, yes... it takes some time. But then, the animation isn't finished yet and I'm already good to go (after media bla bla bla)
@OoZic
For darkys rom... i had the same problem.
First flash Ficetos resurection 10.2, then make shure lagfix is ON (full lagfix - check in voodoo control app) and then flash 10.2 extreme edition
For details go to
http://www.darkyrom.com/community/index.php?threads/v10-2-final-what-are-you-waiting-for.4253/
I had the problem too
Thank you for your reply from.insider
Problem is the phone can only do bootscreen and recovery. The device isn't recognized in any way. Tried it on 2 computers (laptop/PC) with different multiboots (Win7 X64 and Vista X86 on both). Maybe that is because the OS isn't loaded and can't go to MTP?
Is there a way to copy something from external SD to internal SD within recovery menu? Because that way I can copy a JVP or JVQ image to internal. Now there are only the 10.1 and 10.2 zips from Darky.
FSCK didn't find any problems btw.
Thanks again.
Problem solved, my Galaxy is unbricked and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
OoZic said:
Problem solved, my Galaxyd and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
Click to expand...
Click to collapse
Can you copy and paste the the answer and post it here man, i cant find the post your talking about and my phone has the exact same problem.
Hello members.
I just found a strange issue that I have started facing lately whenever I try to flash a custom ROM on my Defy.
Current stock ROM was 2.2.2
I rooted it and tried This ROM. After flashing I realized that the ROM is slowly slowly eating up my space on my sd card. I checked my sd and it showed an ANDROID folder with all app backed up.
I tried playing with the Install location in Cynogenmod settings but still no help.
Tried Internal, Auto , External options but still nothing
Then I changed the ROM to 2.3.7 posted by Quarx hoping it would solve my issue but I had same issue again.
Please tell me what do I do ?
I want to use custom ROMs real bad :3
Still waiting for a response. :/
Hello, I have a Samsung Galaxy S4 (GT-I9505) and I'm having a couple problems with it.
First the phone freezes when its turned on it using Official software or a Touchwiz rom but doesn't happen with other Roms so I'm not very bothered about that.
Secondly there is no sound coming from the device, the only sound that comes off is the booting sound when using touchwiz, I've tryed with headphones and still nothing, and If I go to music and try to play a song the phone freezes until I press the home button, It also freezes when dialing or when any other sound should be coming of the device.
I've done a lot of factory resets and tried various roms but the problem stays.
And thirdly I have no signal on the device, when I put the sim card it just says no service, to be fair the sim card is a normal sim that has been cut to fit micro sim slot, becasue its what I use on my other phone and it works, I'll try with an actual micro sim when I have one available.
I don't know it these problems could be linked, that's why I'm putting them together. I have been searching online but I can't find anything similar.
Hope someone here can help me. Thanks a lot in advice!!
Can't get arorund this!
Ok, so I'm now looking at the sound problem now, seems like there is some people having this issue when the phone freezes when the phone should be playing sound.
I've looked at several threats here and for most people flashing I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar resolved the problem, so I tried it but still no sound.
So my I9505 is now on XXUDMH8, I rooted it again and installed a custom rom since the original firmware is not working very good.
Hope someone can help me!
Can anyone help?
OK so last night I tried flashing I9505XXUEMI8_I9505OXAEMI8_I9505XXUEMI8 and after I changed the kernel I got some sound when turning the volume up and down but the phone was running very slow.
Today I tried flashing Omega rom v15 flashing the right modem for the new bootloader before flashing the zip and no sound, I tried changing the kernel, still nothing.
So now I'm in build number XXUEMJ9 and baseband MJ5.
Please I've tried everything I can think of and I can't fix this, I need help! :crying:
Hello guys,
i tried to install a custom rom and i actually managed it to work. After 2 days i noticed, that there is no sound (not even with headphones). Im not sure what to do now cause i didnt do a backup and i tried so many things but the audio doesnt work. When i installed the custom Rom, i formated the data on the phone, was that a bad idea?
Is there a way to fix this, i have no idea what to do.
Thanks guys
hi
whay dont you tray to restore the stock rom?
using sd card and /dload folder..
just a thougth, i am no expert whatsoever
I've had this issue and I'm not sure the cause.
I fixed it once by using KingOfMezi's TWRP and stock firmware compilation.