Database Users

[Q] Suggestions? com.android.settings Force Close Issue

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.

Galaxy 3 Pinch to zoom

This is my 10th flash of Froyo 2.2 JP9 there was no problem of the previous flashing but just want to recreate the steps outline at rooting thread.After my last Flash i had observed that
1. SuperoneClick Root takes a lot of time to root
2.Pinch to zoom does not work anymore the default browser and any other browser i installed but still works on the galllery
3.The back hardware button does not works on the contacts it wont go back.
Anyone observed this same things?I objectively followed each step outliine in the first post doing some variations on these things on each installation.
1. Wifi on during rooting
2. waited 10 mins before rooting
3. using titanium backup to restore the progams
4.Unmount the sdcard during rooting
in each of these installation i observe that errors occurs and it depends on those variations.
Could anyone shed lights on these things?I think it that stability of i5800 depends on flashing it correctly.
example:
JH2 flash to JP8 then to JP9 yields a much stable phone with less errors
A complete reflash using only JP9 has pinch to zoom errors and the like.
DDJ6 flash to JP9 has difficulty in rooting and lots of force close to.
can we completely remove the firmware?before we flash it with odin so there are no remnants of that old firmware in the phone?

Remove boot.bin and Sbl.bin from the update package and add datafs.rfs to the file (with IZarc). Works for me, i5800, "Galaxy Teos", from France, SFR.

Phone Vibrate and haptics don't work after updates

Hi I rooted my fascinate, installed CWR and froze the apps as instructed in this post.
Root-CWR-MOD-
The I installed voodoo as instructed in this thread listed here.
Voodoo Install for Fascinate
After installing Voodoo almost everything works fine. I get a quadrant score of 1500+.
However my phone vibrate and haptic feedback is completely non functional. It is turned on under system settings. Any idea what could be causing this?

You probably flashed a kernel (with voodoo) that is for the DJ05 rom. If you flash DJ05 you will have the haptic feedback back or you will have to flash to a kernel designed for Di01

Thanks for the help. Yeah that's what I did. I disabled lag fix and will try to install DJ05 and hope that fixes the problem.

You will also need the DJ05 modem flashed via odin. I you want everything to work right.
good day.

[Q] JVP really slow when booted with bluetooth on

I've flashed new JVP into my SGS using ramad's deodexed firmware with CF-root kernel and JKay skin. Then I restored my backup and used it for some time. After one reboot I noticed that it suddenly got much slower than it was - before I got quadrant score of 1900-2200, after it dropped to ~1300. After some investigation I found that there must be some problem with my settings - if I use some "clean" database (com.android.providers.settings) it works like it should but with my backed'up data it works fine only if I boot it with bluetooth turned off.
Can someone suggest what could have I done wrong?

Try to re-flash and use the stock Kernel, then see if you get the same problem. If not then only restore /data applications (Never restore /system applications) and see again if you get a problem, and so on..
You need to find out at which stage you get the problem, this could help isolating the problem so you can help finding a solution by finding out what cause it... in the way you are asking every member will give you a theory, try to find out by your self, devices are all different and so are the applications/settings/Kernels are all different on members devices.

Sorry for beeing so vague on the first post.
I did tried to isolate the problem - reflashed everything at least 10 times with different configurations. The result is I can show the exact moment when after restoring the backup phone starts to act weird.
Unfortunately the problem probably lies somewhere in my old settings as restoring only this one piece into the clean firmware (or - as my steps were - after flashing cf-root and installing theme) doesn't activate the slowdown. Unfortunately I also did a mostly clean restore - restoring only things I really need (contacts, bookmarks etc.) and only a few applications with data and for the rest of backup only applications. It didn't help.
Today I'll try another way - I'll reflash it and then restore only applications without any data and see what would happen.

Ok. So I did another round and for now I'm satisfied with the result.
What I did was:
1. reflash deodexed JVP
2. restored my user apps with data from backup
3. restored pieces of system data and configured missing settings
it worked fine up until this point
4. reflashed to CF-Root kernel - it seems this broke my setup. I'm certain that there must be something in my config/installation that when added to CF-Root and bluetooth introduces slowdowns.
5. as I needed my theme I just flashed it using CF-Root's CWM and after that I reflashed back to the stock kernel - everything returned to normal - quadrant score was back up at ~1300 (from around 700 with CF)
6. as I also wanted to convert to ext4 I flashed a Speedode kernel and I test the speed - it showed stable 1300
7. converted to ext4 using SpeedMod's CWM then rebooted and retested with quadrant - it holds fine at around 2200.
This closes the case for me for now

matofesi said:
Ok. So I did another round and for now I'm satisfied with the result.
What I did was:
1. reflash deodexed JVP
2. restored my user apps with data from backup
3. restored pieces of system data and configured missing settings
it worked fine up until this point
4. reflashed to CF-Root kernel - it seems this broke my setup. I'm certain that there must be something in my config/installation that when added to CF-Root and bluetooth introduces slowdowns.
5. as I needed my theme I just flashed it using CF-Root's CWM and after that I reflashed back to the stock kernel - everything returned to normal - quadrant score was back up at ~1300 (from around 700 with CF)
6. as I also wanted to convert to ext4 I flashed a Speedode kernel and I test the speed - it showed stable 1300
7. converted to ext4 using SpeedMod's CWM then rebooted and retested with quadrant - it holds fine at around 2200.
This closes the case for me for now
Click to expand...
Click to collapse
Good work, and you did it all on your own
Now you know what was the cause for your trouble and how to deal with such problem next time.

For others that find themselves in a similar predicament, but want an alternative method (or workaround), then keep reading.
I too am using Ramad's deodexed Rom's with CF-Root & have similar problems.
Ramad, I know it's not your Roms.
There is definitely something flaky after flashing CF-Root (no disrespect to Chainfire) , as I can replicate the faults again & again & again, with only the deodexed Rom & CF-Root, APN & WiFi setup. No user apps or anything else on the phone at this stage.
Certain problems then arise (lag is often noticed first) after the phone is restarted while ever WiFi & BT are both turned on prior to restarting the phone.
See my posts in the CF-Root thread here (Posts #2151 & #2152) which lists a few other problems which arise after flashing CF-Root, along with my workaround in post #2152.
It'd be great if Chainfire was able to get this issue fixed, as a workaround is never as good as a permanent fix.
If anyone found my workaround worked for them, feedback is definitely welcome.

EF02 GPS and Rotation Fix here!

I finally got rotation and GPS to work on EF02!!!
Here's how I did it:
1. I odined back to the EC05 modem to fix all GPS issues.
To Odin to EC05 Modem:
Download this:
http://dl.dropbox.com/u/20210101/ec05modem.tar
Then Download Odin:
Odinhttp://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1052813&v=1&libid=1306116834963&out=http%3A%2F%2Fk0nane.info%2From%2Fodin-pit.zip&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D716&title=%5BHow%20to%5D%20Restore%20a%20semi-bricked%20Epic%20or%20Bring%20it%20back%20from%20the%20brink!%20-%20xda-developers&txt=http%3A%2F%2Fk0nane.info%2From%2Fodin-pit.zip
Enter Download Mode, then flash it
2. Then download SFR 1.2 final, (it does not come with a kernel, so you will need to flash it, I'd recommend the genocide kernel for the time being), Rotation should still be slow, until you apply this fix:
http://www.youtube.com/watch?v=DKECs764ayE
Skip to 1:20 and apply that fix
3. Now your rotation should be fast, now we will want to go back to EF02 and keep fast rotation, so download and flash the EF02 Rom, here via CWM (wipe cache, data, dalvik cache, etc.):
http://holylivingfuck.com/Decad3nce/...dex-Update.zip
4. Enjoy fast rotation, and if you want, you can go to the AA i1 rom, now, but you must do it after flashing the EF02 ROM located above because I tried flashing the i1 rom before that and I was stuck at a bootloop.
Tell me how it goes for you
Thanks

was your gps not working at all, disconnecting frequently or taking forever to find signal?

My GPS was working for the first few minutes, then it said GPS Connection Lost, and never found a signal until reboot, and the issue repeated until I flashed this fix

My rotation is still slow on EF02 even after the upside down calibration.
And of course, /system/bin/sensorcalibutil_yamaha doesn't exist in EF02.

pjy9394 said:
And of course, /system/bin/sensorcalibutil_yamaha doesn't exist in EF02.
Click to expand...
Click to collapse
It looks like someone has compiled this for Gingerbread. I used it and now my rotation lag is more or less tolerable.
See here:
http://forum.xda-developers.com/showthread.php?p=14935632