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] * Question about a OTA Hard Brick*

Hey All,
I decided to flash back to stock using the odin 3 method. Basically I was planning on getting rid of the phone soon. I cleared everything off the internal "SD" card, wiped all user data and cleared the cache. Booted back into the stock OS, everything looked fine. Checked the internal card again and it had written some new files. I assume these are just operating files for the stock OS.
So I power down the device correctly, pull the battery and install the sim card and 8 gig flash micro sd card. The micro card is completely clear. I boot the phone back up with no issue, it hits the network with no issues. I start looking though all the bloatware and go back into setting and turn the USB setting from Kies to USB storage. Then a get an odd alert telling me an update for my phone is available. So, I figure a stock update couldn’t hurt and let it download and install. It downloads to 100%, and advises it needs to reboot to install the update... Ok, so I let it... the screen come back with a progress bar and not much else. At 50% the progress bar stops and a message telling me the update has failed pops up... The phone then shuts off.......
Bricked..... I mean bricked bricked. 3-button doesn’t work, Jig doesn’t work. the 3 button battery pull doesn’t work. 2 button while putting in the usb cable with odin loaded doesn’t work. 3 button with battery out, usb in and then put the battery in doesn’t work.. This thing is dead....
Now my question....LOL... since I had cleared out any and all data, will AT&T give me crap saying I voided the warranty by flashing my phone?
Do they look at what’s stored in ROM? Because before the phone died I had flashed it to stock... I know how to call XBM (their exchange program) and I know they will send me out a refurb phone, to questions asked. But my concern comes in when I ship them back my device and start snooping around... what are they looking for? No liquid or physical damage. Normally I don’t try to get one over on the man, but it was their crappy update that bricked the phone, not my tampering….
any thoughts or experience with this matter?

Did you flash back to JF6 or something? That OTA was probably the busted JH2 they pushed out to all our devices last year, resulting in tons and tons of bricks. They shouldn't give you any crap over it - it was their own fault that your device got damaged - and if you flashed everything back to stock and formatted the internal SD, then technically your phone WAS at factory defaults, so they wouldn't be able to tell what you've been doing with it prior to that anyway.
Edit:
Also, if ATT gives you **** over it, mail it to Samsung. Tell them you were on eclair, got an OTA notification and it bricked your device. They'll ask you to mail it in without the battery and back cover, and swap the board for you. Takes about a week, but whatever.. beats having to deal with some dumbass ATT rep.

this is just good to know....dont flash to stock and try an OTA update.

This exact thing happened to me. My phone was replaced without question but the tech guy told me something interesting. Just to check things, he took the battery from my bricked phone and tried it in a new phone - nothing. The battery didn't even work anymore. Likewise, he tried a new battery in my bricked phone. Again, nothing. Anyway, I got the new phone and battery and all is well. He said it was junk now. They will never be able to tell what ROMS were flashed on there, I suppose.

jack man said:
This exact thing happened to me. My phone was replaced without question but the tech guy told me something interesting. Just to check things, he took the battery from my bricked phone and tried it in a new phone - nothing. The battery didn't even work anymore. Likewise, he tried a new battery in my bricked phone. Again, nothing. Anyway, I got the new phone and battery and all is well. He said it was junk now. They will never be able to tell what ROMS were flashed on there, I suppose.
Click to expand...
Click to collapse
Well I thought they do like a jtag, or am I wrong?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

nope, no JTAG, just a new motherboard

"Check for update not available" error

Here's a new one, at least for me...when I hit my system update check button in about phone, my Bionic is spitting out
"check for update is not available
at this time.
Try again later,"
Has anyone else ever seen this message? It looks like its happening on 4G or wifi, haven't forced 3g and tried yet.
Usually I expect the "Your phone is up to date" message, but this one's new to me.
I'm bone stock, btw...no rooting yet.

I got that a few times yesterday and then tried again 10min later and it ran the check successfully but didn't find an update. When I ran the check for updates this morning it found the update and downloaded/installed successfully.

Well, that's encouraging I suppose...every time I think I really like this phone, something like this pops up...ugh, I want bionic speed and HP, but with my OG droid and droid X's "it just works" reliability.

I think the only reason you're seeing this error is because the servers are under a very heavy load pushing out the updates. I never saw this error before yesterday. But I'm with you on the frustration factor. I'm on my 4th Bionic now, if I continue to get the black screen of death, random reboots, or data connection issues, I'm going to do whatever I can to get a different phone. I've never had to return a phone to Vz before this model, nor I have ever spent so much on a phone. I certainly don't feel like I'm getting what I paid for. How this phone made it thru user testing with these issues blows my mind.

I had been getting that message ever since I replaced my SIM a couple months ago. I figured it wouldnt interfere with me getting any OTA's, but last night I decided to do a factory reset to see if that cleared it up. Low and behold i hit system updates and it said my system was up to date. An hour or so later I did it again and I got the update!

Good to know. I read a thread somewhere, I think it pertained to battery issues, and someone suggested that when you first take the phone out of the box the first thing you should do is a factory reset b/c it helps with overall performance. I don't know if there's any truth to that but that's what I've done on all of my replacement Bionics and I do perceive there to be some improvement. I don't know if it was necessary but I ran the reset after receiving the OTA today too just to rule that out if I have issues going forward - that's the first thing tech support makes you do when you have problems from my experience anyway.

I've been getting that message a lot too when checking for the update. I got the update today and it installed fine. Still have the data drops though. VERY frustrating.
One think I HAVE noticed with this update is that the battery stats are completely reversed. It used to be the display was down in the 3-5% region, as well as the Android OS. Now, those 2 are at the top, and my phone has just been laying on my desk most of the day.

I am not rooted. I've been getting that message since I got the phone in October. It only happens when I am on 3G. I haven't checked it on 4G (don't live near one) and it says "...up to date" when I am on WiFi.
Sent from my DROID BIONIC using xda premium

I am getting frustrated... I have been getting the same error for three days now. I am rooted, but am on 5.5.886 and everything still the same. My partner is still original stock, and he's getting the same errors as well. Perhaps this is a regional thing? Anyone in the DC area get the update rolled out to them?
Additionally, can I just flash the update file that is posted here on the forums to upgrade manually? Or should I just wait?

Works!
I was getting the same "check for updates not available at this time" message, however I rebooted (used Quickboot, battery pull is not necessary). After the reboot went back to "Check for upgrade" and it worked; BUT just like the previous upgrade the process checks your file system and if you removed/altered any bloatware then it will fail and reboot. After the first time, I decided instead to create a folder "bloatware" in the system direction and move all bloatware apps to that folder. So this time around all I had to do was move all the bloatware back to the "app" folder in one shot. Very easy and straight forward (I also wrote down the bloatware apk filenames so I didn't forget that I moved over last time). Tried the update again, installed just fine, and phone is up and running.
AND....root is INTACT!
Btw...I had no idea there was a new update available until my friend who just got a new Bionic said he's having problems rooting on software v5.9.902

[Q] How to stop auto update to 5.9.905?

I am wondering how stop an update on a Droid Bionic?
I understand you need to "move the update from /cache to your SD card" once downloaded.
However, I do not know where "/cache" is located, how it is accessed, or how the moving process is done.
I connected my phone to a PC via USB and could not find "/cache" stored on the phone. The only thing close was a cache folder within "com.google.android.apps.maps", which doesn't seem like what I'm supposed to be looking for. I've also tried looking in Menu>Settings>Storage but do not see any 'cache' info.
I've been searching the forums but have had no luck; plenty of references to a 'cache' from
people who clearly know what they are talking about, but I can not find any explanations or instructions.
Any help is appreciated. This is my first Android device btw! (though I've been reading this forum for a week or two now)

Wow, you're wanting to stop .905 while most people are chomping at the bit to get 6.7.xxx. You can't do it with your PC, you will need to do it from your phone with a file manager app.
I think you need to be rooted to see the cache'. you will also need a root file manager like "root explorer" to move the update to your SD Card.
ICS is much much better than the GB OS. I would reconsider the update, better things are coming around the corner.
If you choose to stay at .902, I would suggest doing some reading about the rooting process. Bad things can happen if you haven't done some research.
There are many here that will be glad to help you, but you will need to be a little knowledgeable to "help them, help you"
root .902
http://www.droidforums.net/forum/droid-bionic-hacks/198045-902-root-method.html
advanced root and play with leaks and return (well written, read 1st post several times,) also has links to current drivers
SamuriHL spends his life supporting that thread and spends too much time helping others
http://www.droidforums.net/forum/droid-bionic-hacks/214902-downgrade-902-no-app-data-loss.html
I'm not sure if I helped or confused, mainly just want you to be aware

greeneink said:
Wow, you're wanting to stop .905 while most people are chomping at the bit to get 6.7.xxx. You can't do it with your PC, you will need to do it from your phone with a file manager app.
I think you need to be rooted to see the cache'. you will also need a root file manager like "root explorer" to move the update to your SD Card.
ICS is much much better than the GB OS. I would reconsider the update, better things are coming around the corner.
If you choose to stay at .902, I would suggest doing some reading about the rooting process. Bad things can happen if you haven't done some research.
There are many here that will be glad to help you, but you will need to be a little knowledgeable to "help them, help you"
Click to expand...
Click to collapse
thanks; that's really what I needed, a point in the right direction. I confess it's a bit new to me. I just got this phone, programmed it using steps found here (great forum!), and activated it on pageplus, but this was the first time I just got 'stuck' on something.
I read that 3G worked much better with 902 than with 905. this is why I was thinking of sticking with 902, at least until a legit/finalized version of ICS gets released (which allegedly, is very soon...maybe). Since I don't know much about the OS yet I figured I could survive the wait without 'knowing what I'm missing' so to speak.
whoa, just googled and saw that a new leak is out. I picked an odd time to be a newb working on a Bionic.
Thanks again!

If you do take the plunge into a leak, you should probably stick to one where FXZ to 902 isn't blocked so you can return to stock if needed. Everything 235 and after is poison, so to speak, and you won't be able to go back, which (thanks Moto) makes it really difficult to go forward (thanks Moto). I'm on 232 and I'm happy as a clam. It's stable and doesn't have many issues. Now when the official update comes out, they should release an FXZ and we'll be safe again and can all take the dive into ICS.

so, I realized you could postpone the update by just not accepting it when the prompt comes up.
so, I use my Bionic for a while and am quite happy. Then today, I noticed I no longer had 3G service. I tried restarting it, removing the battery,
toggling some of the data changes, no luck. I figured since ICS is (allegedly) right around the corner, there was really no reason not to go ahead and update.
I ran the update. I now have no phone service, no texting, and no 3G/1x.
My question is: how far in the process do I need to go back to get things running again? Right now what I have is a blinking white triangle in the notifications bar. My phone is stock in every way.
Edit: in "about phone/status" I have no phone number (it's blank). no MIN, no network. My PRL version is 'unknown'. so, basically I think I need to just start over, using the info I used successfully before (adam3rd is my hero), beginning with flashing a pageplus PRL. but I shouldn't need to reactivate it on pageplus, or need a new sim card, right? I feel like whatever happened wouldn't have effected my status with PP or the sim card, but I can't find a clear answer....any help appreciated

The white triangle is your phone searching for a signal to activate itself. Take your sim card out and re-insert it. you may need to wipe the dirt off the gold metallic area

greeneink said:
The white triangle is your phone searching for a signal to activate itself. Take your sim card out and re-insert it. you may need to wipe the dirt off the gold metallic area
Click to expand...
Click to collapse
thanks for the response. I actually had 4 bars of signal strength along with the white triangle. I'd assumed this meant I could 'detect' the verizon/PP network but wouldn't be able to get out of 'roaming' status until it was activated for the network.
I actually contacted PP via chat to reactivate it. they did it, but the problem wasn't resolved so I tried a factory reset. boom, activation screen came up! now I have fone and text again.
my real problem now is getting data to work consistently. gonna wait until the legit ICS comes out before tackling that one again.

You're going to love .246
no signal drops, fast reaction on apps. it's truly a who;e new phone experience

greeneink said:
You're going to love .246
no signal drops, fast reaction on apps. it's truly a who;e new phone experience
Click to expand...
Click to collapse
yes, I'm very excited. a little paranoid about updating since I'm on PagePlus and haven't seen anyone use Pageplus and .246 yet. but I may just try using the info on howardforums; I know it 'should' work, but that's just not the same as confirmation.
on a side note; I believe I may have discovered what my data problem was; I think I'd just disabled the 'connect with data over mobile network' option and forgotten I'd done so a month later. pretty funny. but it's been a good learning experience, heh

[Q] Power-On Lag/Freezeing

So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)

I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.

wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).