Database Develop

[Q] Foce close error all installed apps not showing 2nd time...

Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.

i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run

Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.

I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.

nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later

I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.

read this
http://forum.xda-developers.com/showthread.php?t=793404

Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...

I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?

Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.

[Q] Back from the dead!

2 months ago I was installing a CM nightly and something went wrong (I think it was incompatible versions of CM & gapps) and the main result was I had no keyboard access. No amount of attempts to correct this were successful at the time. Things just seemed to be going from bad to worse quickly. Failing all else I picked some option for system restore (I can't recollect what at this point) and got a screen that it was downloading the OS (I presumed the default Samsung OS for the phone but I have no way of knowing) It just stayed on that screen for hours. (possibly because I was off my data plan at the time. I've heard (too late) that some upgrades require it). Since it was getting nowhere I powered down the only way I could... taking out the battery. Then nothing. No boot screen, no recovery, nothing. For over 2 months. Last night I charged it figuring I'd give it one more shot before tossing it in the recycler. Then it boots up! WTH? I'm so happy!!!
But my problem remains what it was prior to going dead... no keyboard and erratic behavior (in particular the back button rarely activates. It will vibrate when pressed but not DO anything)
Baseband= N7000UUBKK2
kernel ver. 3.064-CM-gb07657a
CM ver. 10.2-20130824-nightly-n7000
build number cm_n7000-userdebug 4.3 JSS15Q
gapps-jb-201308-signed.zip
So I've been given a second chance to do it right. What can I do to fix this? Any suggestions would be much appreciated even if it involves moving back to unrooted stock OS and firmware.
Thanks in advance,
A.D.
P.S. I will be getting my data plan back if I can get this working right. Wish me luck.

First an foremost then update - and do a full wipe before. If you still want CM 10.2 then just go for it, but you can also try out KitKat (OmniROM - original development)

[C6903] Persistent problems with full screen and home bar, detailed info.

I updated my C6903 to Android 5.1.1 around... say a month ago? Or around there. It was giving me so much trouble, I couldn't stand to use my phone anymore.
Therefore, I read up on what I could, and attempted my first downgrade to 4.4 KitKat (Central European 01 version 108, unbranded). I didn't wipe the data and that turned into a bit of a mess, but I successfully flashed it and wiped the data properly during the second time around.
But I was still getting some problems, ones that had been occuring since my phone was upgraded to Lollipop. First, that my phone can not enter full screen at all, on any app. The home bar flickers on and off all the time, during Youtube, during any videos, during visualiser, or any app that will make use of fullscreen.
The second issue is that my home keys become unresponsive the vast majority of the time. Restarting does not fix this, and locking my screen then unlocking it again works for roughly 1 minute, then it's back to freezing and no response.
So, considering my main issues were persistent since the update of 5.1.1, I tried a factory reset. I wiped everything and flashed it properly again with Flashtool, to 4.4 KitKat.
It has not worked. Using the developer options/diagnostics I have tested my display and my entire screen has no dead pixels and reacts to the movement or touch of my finger with no issue. So if my screen is fine otherwise, why has 5.1.1 completely ****ed my phone over? It does not make any sense.
At this point I cannot even watch videos or do basic things on my phone as the above issues are preventing me from doing anything. I'm willing to provide as much information as I can, so I would appreciate some help and insight into this. Thank you!
EDIT: Additional information - Trying to view pictures in full screen (Album) ends up with it zooming in and out constantly, even when nothing on the screen is being touched.
When my phone is on landscape/full screen android keyboard, it will intermittently go crazy and start vibrating. I believe it is the symbol key being pressed on it's own, off/on constantly. Nothing on my phone is being touched or moved at this time, it just does this by itself.

it looks like some dirt got on the edges of the screen and it's messing with the touch detection.give that phone a nice bath(one of the best advantages it of being waterproof ) and clean that screen.that should fix it!

masterofnocrack said:
it looks like some dirt got on the edges of the screen and it's messing with the touch detection.give that phone a nice bath(one of the best advantages it of being waterproof ) and clean that screen.that should fix it!
Click to expand...
Click to collapse
The cover for the charger port is broken and just fell off one day a long time ago (it never closed properly, though) so unfortunately, I won't be able to go through with that suggestion.

Added new information. I hope I can get some insight into this soon.

Need help (Unfortunately the process com.android.phone has stopped working)

Hey, I need help, today I tried to replace the stock battery of my S5 with a replacement battery which came with the phone I bought in Amazon, but I noticed that the second battery was fake since it weighted less than the original one, but I was desperate for more battery life (since updating to MM my battery last 1 day and a half max when it used to hold charge 2 and a half days), I turned my phone off and changed the batteries, I turn on my cellphone everything seems alright but then a pop up (Unfortunately the process com.android.phone has stopped working) appears and I'm like, alright, that's new, and accept, but then it appears again and again every 7 seconds, I rebooted, no change, I followed some online instructions (disable the process, delete cache, data, force stop, wiped the cache partition) but nothing works, so I switched the batteries back, thinking it would fix everything but to my surprise, the pop up still appears, and my SIM is not recognized anymore, can't make calls, can't do anything SIM related, please help me i don't want to wipe the phone again since I just restored all my data like 2 days ago, thank you.

If you aren't rooted you will most likely than not have to restore. That sound like something went corrupt with in the sec.phone apk or even system wide. I don't think it was the battery that did it tho.
Anyone more knowledgeable might have a better solution, good luck.

sejodesign said:
If you aren't rooted you will most likely than not have to restore. That sound like something went corrupt with in the sec.phone apk or even system wide. I don't think it was the battery that did it tho.
Anyone more knowledgeable might have a better solution, good luck.
Click to expand...
Click to collapse
I guess it's firmware because I hard reset my phone and after the first reboot the problem came back

Jumping Screen After Nougat

Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/

Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)