Hi, I've rooted my mesmerize with z4root and have installed a couple root apps. One being ROM Manager, which I flashed clockworkmod for fascinate.
Now sometimes my screen just freezes, and when I try to the screen off, then on. It doesn't turn back on. It's still actually on because I was listening to music, and the music kept playing. Anyone know how I can fix this?
Might be a hardware issue (but I doubt it).. some people have been reporting screen trouble. If you want to be 100% sure it's not software then use Odin v3 to get it back to stock and then see if the problem persists. It shouldn't be software though. My phone is working fine and I have both those "apps".. If it does continue just take it back to the store and they should swap it for you (if you can get it to do that for them). However, they'll probably just do a factory reset first. So, in general, I always make sure I can get a problem to happen when I'm on a factory reset device running a stock rom and kernel before I take it into the store.
Also, does this happen often? Or has it just happened once or twice. Now that I think about it I may recall having to pull my batter a few times because it was frozen.. but that was back when I was on the stock ROM and kernel.
Perhaps you might want to try the Voodoo lagfix kernel. It may be a combination of the buggy/slow RFS and frequent use..
dcow90 is right, how often do you reboot the phone within a weeks use?
Related
I am getting random reboots and I am unable to figure out what is causing the problem and I have not found any thread about random reboots with the Captivate.
haojan said:
I am getting random reboots and I am unable to figure out what is causing the problem and I have not found any thread about random reboots with the Captivate.
Click to expand...
Click to collapse
Provide us with more information. Is your phone rooted, on a custom ROM maybe, what have you been doing to your phone, when did this start happening, etc.
History
I started with stock, rooted, non-market apps, unhelpful kernel v1.2, removed AT&T bloatware. LCD density @ 180. Tried One Click Lag Fix v1.0 and v2.2 and uninstalled. Juice Defender to manage 3G. Juice Plotter to track battery.
After messing around with it, I encountered a reset of the default launcher selection each time I long pressed the home button to bring up the recently used programs. I then did a hard reset and that fixed that problem. After the hard reset, my Captivate ran great! I found it responsive and fast enough without the need to try and apply any lagfix.
I then reinstalled my selected applications. My phone started to randomly reboot about once a day. I noticed Juice Plotter's data would be lost and it had to rebuild. It also happened to reboot on me once while I was using it. Other than that, it has not really affected my usability.
If it hasn't affected your usability, do you want to fix it?
If you do want to fix it, then the best way is to restore to Stock and add things slowly until you determine the problem. If you return to Stock and it still reboots, then you have a hardware issue.
It doesn't "quite" affect usability but it is not working "normally" either.
Was hoping to see if anyone else have experienced random reboots and how to troubleshoot it. If not, I will try out Odin one-click flash to stock...
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, ever since I rooted my SGS4G I've had three really odd issues that happens across all ROMs - stock, custom, ODIN, CWM - all of them.
1. When I first boot up the phone it gets stuck in landscape mode. Sometimes it fixes itself after 30-60 minutes, sometimes it doesn't.
2. It randomly goes into Car Mode or Desk Home starts up on its own - on ICBINB and Audiophile if I hit the Home Key then it starts Desk Home. So I have to back out to the Home screen.
3. Also, whenever I play certain games (ex. Angry Birds), it only works for a minute or two, then goes to the home screen. I've uninstalled and reinstalled the games and it still happens.
So, has anyone else had similar or identical issues? If so, how'd you fix them?
I use Titanium Backup to restore most of my apps because, for whatever reason, the Google backup/restore doesn't work with this phone (even in stock). I don't restore system information, just missing apps.
If you want my 2 cents i would say it is hardware, where you are switching roms and the same problem is still happening, the rom should clear out all memory, cache, etc. i would you say to take it back to the store and get a new one. sounds like there is an error with the sensor. good luck
HB66 said:
If you want my 2 cents i would say it is hardware, where you are switching roms and the same problem is still happening, the rom should clear out all memory, cache, etc. i would you say to take it back to the store and get a new one. sounds like there is an error with the sensor. good luck
Click to expand...
Click to collapse
Yeah, I was hoping it wasn't the hardware. Oh well.
if you do take it back you may want to unroot and go back to stock just to be safe because they may see that and say you voided the warranty.
HB66 said:
if you do take it back you may want to unroot and go back to stock just to be safe because they may see that and say you voided the warranty.
Click to expand...
Click to collapse
Yeah, but I'm kinda SOL because I'm not with T-Mobile. I'll just deal with it til I get another phone.
those are very unique problems. i have yet to hear of anyone experiencing problems like that. to me, it sounds like you didnt calibrate your horizontal sensor properly. odin to kc1 and get a fresh start. then make sure you factory reset, wipe cache and your mounts are correct before flashing the ext4 converter and then the audiophile or icbinb rom again. dont reinstall your apps from TB. it usually causes problems for certain apps. download from the market again, back up your apps with cwm, or simply go into data folder with root explorer and copy the apk and the data lib and push it to the rom before you flash. when this is done, let it load and then go back to fix permissions. then go back and recalibrate your horizontal sensor. if you want, you can delete the carcradle.apk and the deskcradle.apk if it still gives you problems.
jager555 said:
those are very unique problems. i have yet to hear of anyone experiencing problems like that. to me, it sounds like you didnt calibrate your horizontal sensor properly. odin to kc1 and get a fresh start. then make sure you factory reset, wipe cache and your mounts are correct before flashing the ext4 converter and then the audiophile or icbinb rom again. dont reinstall your apps from TB. it usually causes problems for certain apps. download from the market again, back up your apps with cwm, or simply go into data folder with root explorer and copy the apk and the data lib and push it to the rom before you flash. when this is done, let it load and then go back to fix permissions. then go back and recalibrate your horizontal sensor. if you want, you can delete the carcradle.apk and the deskcradle.apk if it still gives you problems.
Click to expand...
Click to collapse
I'll try all this tomorrow. I just got home from work and I'm tired as hell. Thanks for the info and I'll letcha know how it turns out.
Just putting this out there for anyone who may be having the same issue as a possible fix for them.
The wifes sgs3 would not go into deep sleep mode. as a result the battery was under constant drain.
her phone is set up pretty much like mine is and i wasn't having the issue and I couldn't seem to figure it out.
i did a clean flash but still the same problem. (wiped everything, even data)
I've been looking at BBS and wake lock detector for days but nothing was coming to mind, everything looked as it should.
i started removing apps, till there was nothing. still. same issue. tried different kernels. etc. still same issue.
I was about to move on to another rom (beans 18) to see if that would help. and i decided just for giggles to reflash the modem.
and what do you know upon reboot the phone started going into deep sleep mode.
I think i was running MF1 Modem and Bootchain with Mb1 TZ on her phone. but can't say for sure.
i downloaded the latest (d2vzw_VRBMF1_firmware) and flashed it. couldn't believe that is what the issue was.
anyways, if someone runs into the same issue. try flashing the latest modems or perhaps a previous and see if that helps.
Hi everyone, few days ago i got some problems with my phone.
When i am doing smth, for example chatting in whatsapp(it can be any app, even the menu) , the screen may freeze from 5 to 20 sec. After it, the device may become locked or not. Also, after it, device may reboot. Or just shutdown.
I already tried :
1 wipes (full via phone menu and recovery)
2 formatting flash via custom recovery
3 flashing 5.1 via odin
4 emergency restore via Smart Switch
But the problem is still here.
Is this a hardware problem, or should i try smth else?
Thanx for advice
I'm starting to wonder about hardware issues myself.
I'm getting the feeling that Samsung wound the processor too tight on these phones.
Once I get rooted again,I'm planning a proc' downclock to 2.3/2.4 Ghz.
I'm not totally sure,but if these proc's control the RAM directly,that might help with stabilty issues.
Just to confirm; you did a factory restore and also flashed the stock 5.1.1 for your model and region with Odin 3.10.7?
Sent from my SM-N915G using Tapatalk
yes, exactly. Not sure with odin version, but everything was fine.
Yesterday also tried River rom with Mickey Kernel. First few hours phone worked normally, but was a little bit slow (it is normal for this kernel). But then the problem returned, i got some (2 or 3 ) reboots and lots of freezes.
weird. I started gettig these issues a couple of weeks ago too. Did as you did, Odin, Smart Switch, TWRP. Nothing. On RiverRom it seems to be more stable than on the official Rom. Which is crazy. Searched through all the logs, only idea i got left is keeping in under android logcat on my computer until it crashes.
Also phone won't restart if I want to do that. Not from menu, not from TWRP. It will just not do it. It shuts down and no matter how much I press the power button.... nothing. Hve to take out the battery, wait 30 seconds, plug it back in, and it will start.
Any advices on what logs should be looking at would be much appreciated.
kalin12351 said:
weird. I started gettig these issues a couple of weeks ago too. Did as you did, Odin, Smart Switch, TWRP. Nothing. On RiverRom it seems to be more stable than on the official Rom. Which is crazy. Searched through all the logs, only idea i got left is keeping in under android logcat on my computer until it crashes.
Also phone won't restart if I want to do that. Not from menu, not from TWRP. It will just not do it. It shuts down and no matter how much I press the power button.... nothing. Hve to take out the battery, wait 30 seconds, plug it back in, and it will start.
Any advices on what logs should be looking at would be much appreciated.
Click to expand...
Click to collapse
I just tried to restart my, it booted normally.
Maybe its overheating or smth like this? It will be difficult to demonstrate this problem in service centre
honestly i don't think it's overheating. For me the behavior is a bit weirder, as said, as the phone won't restart, unless removing the battery and waiting for a minute or two before plugging it back in. Every. Single. Time. Not even rebooting from recovery.
I use now riverrom with the emotion kernel (they launched this year a new version of the kernel) and it seems to be better. Weirdly enough, the system gets slower when i turn on GPS (although i have next to nothing appls installed), and the apps that say they stopped responding are the boring ones. System UI, Google Play, etc. Also downloading the kernel auditor from the guys at emotion and enabling logcat seems to help too.
An error i seem to get constantly now is google play services error.
Bluetooth also seems to be an issue, i also have a android watch and it gets kinda weird behavior.