How can I tell what is causing my phone to freeze? Is there an error log or something that will point me in the right direction?
At first I thought it was power amp causing the phone to crash, out doesn't matter whether I have headphones in or not. But it's also been rebooting all by itself. Even when not using that app. I've tried clearing data, have NEVER restored appdata with tibu. Tried downloading fresh copies of apps and have even changed UV settings. Nothing works. Phone freezes and touch screen is completely unresponsive, no buttons work and I have to pull battery to reset. HELP?! I just wasn't to find out what's causing this error. Has happened on nearly every ROM I've tried. They start out ok and two Weeks in the problems start
Any UC/OV?
No oc. Only UV but I've backed off on UV settings as this was my first thought. The phone only freezes when using power amp. I've been using the same UV settings since I flashed this ROM. I believe at this time it has nothing to do with voltage settings but possibly a software conflict with this app.
Sent from my GT-I9000 using Tapatalk 2
Related
So as soon as I took the phone out of the box I root it, installed setcpu, removed all the att apps and got rid of the original launcher. My issue is this: It seems as if I leave my phone in my pocket for any amount of time, I check it and its blank. It's not off, because it will not respong to any button presses and I have to pull the battery to get it to respond. I've tried changing the settings on the setcpu, even disabling profiles and using the ones that come on it and it still has issues. Any input, or am I overlooking something here?
Thanks!
md1609 said:
So as soon as I took the phone out of the box I root it, installed setcpu, removed all the att apps and got rid of the original launcher. My issue is this: It seems as if I leave my phone in my pocket for any amount of time, I check it and its blank. It's not off, because it will not respong to any button presses and I have to pull the battery to get it to respond. I've tried changing the settings on the setcpu, even disabling profiles and using the ones that come on it and it still has issues. Any input, or am I overlooking something here?
Thanks!
Click to expand...
Click to collapse
What makes you think its the battery? It is probably setcpu that is causing the issue. Try disabling or uninstalling it and see if that fixes it.
its a setcpu issue. I had it installed and random times, when its locked and I wanted to unlock it, I could not and I also had to do a battery pull
Uninstalled it and its been fine since
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.
So I've had a few similar problems with recent ROMS i have flashed.
I'd been using CM9 and CM10 for a while, but got tired of lag and bugs. I thought I'd go back to GB for a while and reflash after some bugs had been worked out.
From CM10 odin'd back to GB stock with CWM and root, then installed AEON purely by reputation. That lasted for about a week. The phone had all kinds of issues with the battery. The battery level would often be all over the place (i know this sometimes happens after a reboot.) After a full charge the phone would stay on for about 4-12 hours, and simply turn off. Prior to shutting off the battery would read at 50%+.
Every time the phone shut off like this I could charge it all day and it would not restart. The only way it would start is if i pulled the battery, plugged in the carger and reinserted the battery. Once I did that an empty battery would show up on the screen. However it was not the normal green one with gradients that would show up, but simply a white box showing no charge. If i held down the power button eventually the normal battery charging screen would show up and it would reboot.
I'm assuming the phone was misreading the battery level for some reason. I tried clearing battery stats. No change.
So I thought 'time for a new rom'
I'm not certain if I went back to stock before this.
So from there I went back to CM9 and then to CM10. The battery issues remained, and two new issues arose.
My reception in the notification bar would turn to an empty triangle. It was not a misreport. I could not make calls or access the internet.
Also whenever i went in to airplane mode it would be grayed out in the power menu. It was impossible to turn off airplane mode without restarting.
I'm not on the most recent verison of liquid smooth. The issues remain, but I don't think it's the ROM as others don't seem to be having these issues.
Does anyone know any reason for this?
My understanding of flashing is that it's essentially a list of folders and files that replaces or adds to existing ones on the phone. Does it actually erase anything? Obviously it leaves our simcards and picture files. It also seems to leave app folders.
And just to be clear I wiped user data, cache, fixed permissions, etc. IMEI is still there, so i don't think that's the service issue. I did not restore any apps with titanium backup for similar. Everything was installed from the play store.
Whenever you flashed back to stock, do you happen to flash boot loaders?
Sent from my SGH-I997 using xda app-developers app
magnetboard said:
Whenever you flashed back to stock, do you happen to flash boot loaders?
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I flashed back to GB so I don't think that was necessary. I've not had the other bootloader issues with garbled display, etc.
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
leesumm said:
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
Click to expand...
Click to collapse
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
could be.
DvineLord said:
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
Click to expand...
Click to collapse
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Yeah I have found some of the Venom tweaks really affecting responsiveness. For example if you could figure power long press to turn on the flashlight it takes NOTABLY longer to wake the phone. I can see s2w having the same effect
Here I thought I was the only one experiencing this issue. I did a full wipe and format and flashed a bone stock (default configuration) flash of ViperXL to see if that would solve the issue. Screen issue doesn't occur as often as before bit it still happens. I found that if I block the light sensor, the screen begins to behave normally. I don't have a logcat yet but can upload if necessary.
Sent from my HTC One X using xda app-developers app
same problem again.
leesumm said:
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Click to expand...
Click to collapse
I thought wrong , again, tried this morning just moving an app from home screen to second screen. It will open but unable to move it or delete it from the screen. Rebooted and seems everything is normal again.
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
area51avenger said:
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Not really sure, I can't find anything that 4x5 is enabled. S2W I disabled also, this is not a big problem just irritating some times. Things usually start working normal when I reboot system .
You could try increasing the voltage.
ken bentley said:
You could try increasing the voltage.
Click to expand...
Click to collapse
At this point I am not sure I am that smart to be messing with volotage and such on the inside of this thing.
just stopped using a custom kernel. i stopped using them cause of freezing issues.
I seem to have really strange issues with this phone.
I've tried both C-Rom and Cyanogen and both of them have these same issues.
When I first turn on the phone, it will run, but everything will stutter around at about 1-2 fps for about 2 minutes. I can confirm that this happens even with no 3rd party apps installed.
Secondly, half the time when I go to grab the phone and just check notifications and so on, I'll unlock it and try to press something and it'll be frozen. I have to wait about 2 minutes before I can do anything else on it. The only thing I can do in this time is lock the screen, but not unlock it. I can tell it frozen at a low level because I have a system setting in C-Rom to play a sound when the battery dis/reconnected and that doesn't play while it's in this state. Has anyone else been experiencing this? I've already completely wiped the phone completely once using the return to stock guide and these issues have not been resolved.
Had the same problem with stock ROM or tried with GPE? Might be a hardware problem...
fckland said:
Had the same problem with stock ROM or tried with GPE? Might be a hardware problem...
Click to expand...
Click to collapse
Are you still having these issues or did you find a fix for them? I have the Boost Mobile one, but are you suggesting that I could/should put the GPE ROM on here?
Isn't this a memory usage ( ram ) problem that's been mentioned?
Sent from my XT1032 using xda app-developers app
The first part (FPS issue) happens to me, whe the phone boots, the FPS go down, bad, but the phone works ok, if i put the stopwatch app (CM11) time runs normally but the screen refreshes every half second or more.
Now, the second problem, about the phone freezing whan it wakes up, never happened to me, but i have to recognize that i had a few (2 or 3) reboots just when i waked up the phone and one time it just freezed with the screen off.