Related
I have had a problem occur a couple of times today that has never happened before. I have an extended battery installed(3500mAh). After 2 hours of not using the phone this morning after I pulled it from the charger I noticed the battery was down to 86% when it should have been still at 95% or higher. About an hour after that I went to make a call and the phone would not unlock. In fact it would not respond to any gesture or button push. I had to pull the battery to get it to boot up again. That freezing up has happened twice today. Once with the extended battery and once with the stock battery. Should I wipe the data and start all over again? Or is there another solution?
Have you installed any new programs recently?
No nothing for a couple of weeks now.
Still having a lot of freezes. Should I go to the security settings and tell it to do a factory reset and then start over again with rooting and customizing?
just out of curiosity did you reinstall the location services?
No. The only things I added back in after the last flash were the ringtone trimmer, sound recorder, and the sprint tv.
one thing that I noticed when I had my phone hooked up to ddms looking at the debug log I had a RSS reader app that was add supported and every 30 seconds it would search for and dowload a new add. once I got rid of that app it seemed to help.
another thing that really helped was I downloaded an app called "overclock" it let me set my CPU to 528 when the screen was active really helping with the speed and how fluid the scroll in menu's is, but it also lets you set it to like 128 when the screen is off. seems to really help with battery life as well.
What is throwing me for a loop is that the phone sleeps like it is supposed and I have verified this with spare parts show I am not sure why all of a sudden the battery is draining much faster than before. As far as the lockups, they are just temporary freezes, it locks and I have to remove the battery to get it to reboot.
Well I wiped the data then flashed to the newest sprint rom(1.56) and then rooted again. I then wiped data again and then flashed to fresh 1.1 and installed my apps and setup my home screens. So far no problems and it seems to run a lot faster and smoother.
Quick off-topic question:
When you say "wipe your data" does that mean you rm the /data directory? Or what? Just curious
No. I used Wipe in the recovery screen.
i just did a upgrade on my hero too from fresh 1.0 to 1.1
when you select wipe data from recovery mode, besides wiping data with option 1, do you choose option 2 as well ? wipe dev something. i wasnt sure what the 2nd wipe option is for, so i did the first option only and it only took 2 sec to complete that step. my phone is up and running with fresh 1.1 without any issues, so did i do it rite ? just outta curiosity
The second one is the cache. I think it gets rebuilt anyway on the first boot with fresh installed.
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.
Came from dark and sinistar to ultimate rom. All the sudden about 2 hours in, every time I turn my phone on, the lock screen don't come up and it just is ready to play.. I was like wtf its this rom. Flashed back to dark and sinistar and now the same thing. Goes straight into the system bypassing the lock screen. So I hard reset, wiped data, dalvike and hard reset.. Now lockscreen works again. so I flash back to ultimate, check lock and its golden. Restore my tb and check again, everything is fine, lock screens there...
So about 20 mins in I realize the battery meter on this rom don't show %, so I opened my usual battery indicator app and I got my% in the task bar now...
Ok, I shut phone off to standby, turn back on and no lockscreen, I instantly think battery indicator. I delete app and check lockscreen again and it works..
So both times flashing ultimate I installed battery indicator and know that was my issue.... So weird how a app can cause so many issues, and from this little deal I believe the issues people have are app related. Could even cause reboots.. Hell this app made my lockscreen disappear and I've been using that app forever on different phones and roms..
Battery indicator is my culprit, I'm sure yours is a app also...
nm found it
OK I'm tired of seeing people complain about random reboots even though its been discussed multiple times. So here's a true story to help you all out.
I was on octane 3.0 problem free when I decided to go to Valhalla black final. I had reboots and force close issues. I went back to octane 3.0 and started having annoying force close issues. Now I know its time to start fresh from stock since I haven't cleaned the gremlins out of my phone in so long.
So I download kies mini for the drivers (since I got a new laptop in December) and pop in a DVD that had a backup of all necessary files (odin, kc1 and whatever was in fbs original gb starter guide, I want to say kg4). I load the kc1 files in Odin and Odin freezes at checking connection.
I unplug my phone, pull the battery, reinsert the battery and put it back into download mode (which is now a pic of a phone with a cord running to a computer), I then restart Odin with the kc1 files and everything goes through fine. I then do the kg4 files, once that's done I reboot into cwm and flash bhundvens latest kernel with the newer version of cwm.
Once that's done I flash Valhalla black final fixed followed by Valhalla booster. Now I've been running flawlessly for over 24 hours so its about time to UV/OC. Once I UV/OC, if I start having issues I'll know I need to change my UV/OC values, since I wasn't having problems with stock voltage.
Alternatively you can use bhundvens heimdall package that already includes his latest kernel. I just stuck with the files I already had saved cause my home internet sucks.
Sent from my SGH-T959V using xda premium
Great guide 10x
Did I hear wiki?
Sent from my SGH-T959V using XDA App
Thanks... I'm planning to do pretty much the same this afternoon. I had the reboots, but they stopped for a few days when I reflashed rc1.1 kernel... started happening again yesterday, so I flashed 2d, but still getting reboots.
Figured it was time to start back from ground zero.
I only had reboots when attempting to access the messenger toggle at the lock screen, Drive smart, and battery history in spare parts.
generalbrownie said:
I only had reboots when attempting to access the messenger toggle at the lock screen, Drive smart, and battery history in spare parts.
Click to expand...
Click to collapse
1) mess. toggle= you have to set that via settings> tweaks (or edt tweaks)> lock screen settings> choose custom app
2) drive smart= labeled "bloat" & removed
3) spare parts= I don't believe there's gb support... Though you can access via settings> about phone> battery use
Hope this is helpful
Sent from my SGH-T959V using xda premium
Very helpful I appreciated it. =D, I just changed the lock screen and wasn't going to use those, they bare no real importance and the ROM functions amazingly.
.......................
Wow i had same problem with odin at setup connection but i did not.try.odin again yet as my.phone is already at stock and im about to cancel the contract.and get another phone as its not been 30 days yet. I am thinking of trying odin again.
Sent from my SGH-T959V using XDA Premium App
QUIETLYloud said:
3) spare parts= I don't believe there's gb support...
Click to expand...
Click to collapse
To add to what QUIETLYloud wrote - Spare Parts is GB supported according to the app description in the market, but it also tells you not all phones store battery history and if your phone does not store it you will FC if you select that option within the app.
Add: I decided to uninstall Spare Parts that came with the ROM and download Spare Parts from the market. No more FC on battery history.
lumin30 said:
To add to what QUIETLYloud wrote - Spare Parts is GB supported according to the app description in the market, but it also tells you not all phones store battery history and if your phone does not store it you will FC if you select that option within the app.
Add: I decided to uninstall Spare Parts that came with the ROM and download Spare Parts from the market. No more FC on battery history.
Click to expand...
Click to collapse
Is it a completely different version or just newer?
Installed this and still force close on battery history selection. Im batting 0-4 tonight. /sigh
yes the messageing icon will fc and cause a reboot if you do not assign a button to it... I should add that to the op its inteintally left un assigned so you can assign whatever you want to it though tweaks...
Spare parts battery status will fc it was the only version i had at the time but the newer one should be ok if you wipe the data from it then force close uninstall and download form market ... If not wait tell they add better support.
There are a couple Spare Parts in the market. The one I used was Spare Parts+ (no ads) by DroidGram. It worked for me.
The weird thing is using a widget for the battery shows the history just fine. Spare parts is a weird animal.
So, I flashed Bryan's d2 version of the kernel yesterday and am now going on 33 hours without a reboot.
I'll leave it on the charger for the night and see what uptime is in the morning, if no reboots over night then I'll flash back to 1.1 and see what happens.
speaking of charging.. I am at 73% battery life at 9 hours on battery, so bat life is looking good
Core
Sent from my SGS4G using Tapatalk Pro
eollie said:
Is it a completely different version or just newer?
Installed this and still force close on battery history selection. Im batting 0-4 tonight. /sigh
Click to expand...
Click to collapse
I think it is newer. But if you are using the one from the market, make sure you removed the one that came with the ROM.
I'm on Bryans 1.1 which has yet to give me any problems.
I've been playing with UV settings (always OC'ed @ 1.2) trying to find the right settings for my phone. I think I'm finally making progress, I had been getting a reboot within 8 hours, on my current settings I've just hit 12.
Once I hit 24 hours up time I'll adjust again and see how it goes.
I have the random reboots to and i used the back to stock one click, but I still get the random reboots. However, it only happens when I restore my apps thru TB. Is it possible one of my apps has some sort of "virus" causing it to do that?
Actually TB causing problems is an issue that has been discussed. Personally it hasn't given me any issues, but I've read after flashing a new ROM you should only restore user apps. So don't restore app data or system apps.
Its worth a try anyway. Otherwise one app causing your problem is a possibility, but depending on how many apps you have it could take a while to restore one by one til finding the problem one.
Sent from my SGH-T959V using xda premium
I am having some random hangups followed by reboot when I'm using stock browser. I'm on rooted but stock GB KJ6 with stock kernel. I never had such behavior when using other apps. and it does not matter if OC or not.
Well, I'll try another browser for a while and will report back.
I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.