Hi,
since a few weeks i've got a big problem, my phone freezes to the point where I have to hold the power button to restart it. this started happening when I was on Jellykat v6.7 but still persists after flashing stock rom.
Info:
Flashed latest bootloader
Problem persists on Jellykat and stock, with multiple and stock kernel.
Problem does not occur when running spotify in the background.
Right now I'm running stock rom (4.4.2 from sammy, flashed via odin) with stock kernel and latest bootloader.
When I restart it and check my battery stats I can see my wifi was still working when my phone did not respond, thus the device was on and I was recieving messages while the decive was not awake.
Weird thing is that it works properly when I let spotify play in the background, meaning it doesn't go into deep sleep (I think).:silly:
Right now my device works fine, but only because I have spotify playing the background 24/7 which isn't ideal in terms of battery life and such.
Any thoughts on it?
Thanks in advance!
Still no one? I guess i'll have to survive till I get the note 4 :silly:
Same here
Same thing happened to me when I was on stock rom.. sometimes it froze sometimes it didn't.. (Without spotify)...
Now changed to custom rom... havent faced such issues since then (last one month..not much)
silentkiller143 said:
Same thing happened to me when I was on stock rom.. sometimes it froze sometimes it didn't.. (Without spotify)...
Now changed to custom rom... havent faced such issues since then (last one month..not much)
Click to expand...
Click to collapse
It started on custom JellyKat ROM, weird thing is, yesterday it worked perfectly fine without spotify and today it's screwing me over again
Related
I have a used (out of warranty) DINC 2 rooted with Cyanogenmod 7.2 installed (Page Plus). The phone has been working fine for about a month. All of the sudden, the phone will not turn on unless I remove the battery first. If I remove the battery and boot the phone, everything is fine until I turn it off and then it won't come back on. If I do a complete shut-down, then it will turn on. I tried wiping the cache - no help. I tried restoring an old backup that was working at the time - no help. Any ideas? What should I try next to debug this?
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
brymaster5000 said:
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
Click to expand...
Click to collapse
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
rh09 said:
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
Click to expand...
Click to collapse
UPDATE: I think I might have figured it out. I borrowed a battery from another phone and it seems to work fine with a different battery. Anyone have recommendations for a good aftermarket battery (not extended) for the DINC2?
UPDATE 2: The "fix" didn't last. The same problem resumed after an hour or so on the other battery. Still open to suggestions.
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
vforaci said:
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
Click to expand...
Click to collapse
I don't have any bootlooping - the phone was working great with CM7.2 until this started happening. Can't figure out what caused it. How well is CM10 running on your DINC2 (like, performance-wise)? (Assuming that's the phone you have.)
Performance is better than Viper and yes I have the Dinc2.
What is the turbo engine? I've never used or heard of it. I did have reboot issues with the early builds of cm10. I just flashed psycho's new 4.2.2 build & it seems to be quicker than evervlov. I need to give a couple days though.
Hello guys,
I have some issues while using the latest 4.4.2 DN3 ROMs. Before installing DN3 4.2 I flashed MJ5 bootloader, and it was running for a couple of weeks fine, then the phone started to freeze and reboot several times a day. I thought DN3 v5+ would fix these freezes and reboots but it was no good. I was really disappointed, as I really liked the look and feel of DN3. Now I'm using Revolution HD 31, it's stable (more or less, a couple of freezes and reboots for two weeks) and fast, but I really liked the looks of the latest DN3...
So the question is - what can I do to avoid these freezes and reboots and will upgrading the bootloader to a newer one will help me?
I don't think bootloader has anything to do with it. I was on MJ5 with 4.3 creikelo and NEVER had a reboot or force close. DN3 just freezes after 1-3 days. I had the same experience. It started getting laggy, or better said, the CPU was doing something, hence the lag, and then it just restarted by itself. And I did clean install. It is enough to reat the DN3 topic and see how many people have problems with it - and most still consider it the best ROM... I just went away to another ROM, and will post results in a week hope it doesn't behave the same as DN3
Thanks for the reply!
What ROM did you install? Is it stable?
I had a problem with mj5, my phone froze on the boot and i had to reinstall the ROM.
I think mj5 is for 4.4.2 ROMs, is a older bootloader.
brainstormer911 said:
Thanks for the reply!
What ROM did you install? Is it stable?
Click to expand...
Click to collapse
I tried JellyKat 6.7, but seems I have same issue... at first it was getting high CPU usage after a day or two, then phone became so overloaded it reacted to nothing and I had to pull battery out. Then all of a sudden I started getting SOFT reboots (that means only from the point of boot animation, no samsung screen) and I installed Xposed module Samsung Crash Fix and will see if it helps... I dunno, I am begining to believe there's something wrong with all 4.4.2 ROMs Because I never ever had FC, crash or reboot with 4.3 Criskelo....
Okay so, first off, I'm not much of a noob in flashing ROMS and tools, I've had a bit of experience with a Samsung Infuse before, now I got this Note 2 and TouchWiz pissed me off, of course, now I need a lolipop ROM, I used ODIN to root and install TWRP recovery, also flashed a 5.1.1 "RESSURECTION" ROM, tried CM12 too, now the thing is, I'm getting a weird lag, this lag occurs randomly, lasts 2-3 seconds, followed up with a weird vibration, yes the vibrator vibrates the fone whenever this lag occurs... Now I tried a lot of stuff, except unlocking the bootloader because I'm not sure if it'll fix it or not, also after a while I noticed that it didn't detect my SIM card, could it be that my phone is refurbished? Everything else works ok but the lag makes it unusable.. The lag occurs on both CM12 and the other ROM so I don't think it's because of the ROM.. I'll revert to stock Kitkat using ODIN, but I really need to fix this. I tried Google for solutions but I can't seem to find anyone else having the same problem... So please help me out here mates
I'm running stock 5.1.1 rooted. Whenever the battery dies on the tablet, it will go into a bootloop when I charge it and turn it back on (gets to Samsung logo with no start up music). So far, that only thing that seems to work is wiping data. Has anyone experienced something similar? Bad install maybe?
I've had the same thing happen to me last night. I tried everything and nothing worked. I had to restore a old back up i had with twrp and it started fine. Not sure what causes it though.
I've been having this problem for 6 months now. Let me try a custom rom.
dkb218 said:
I've been having this problem for 6 months now. Let me try a custom rom.
Click to expand...
Click to collapse
Update the twrp tp latest version.I had the ame problem with old twrp but now all is fine with 3.0.2.0.
mine just started doing this. i can boot into recovery but the touch screen doesn't respond. i can also get into odin. I believe i was running Rooted Stock 5.1.1. Should i just reflash (i was thinking of going custom like LineAge) or do i need to reflash stock rom? I was also reading about just flashing the PIT and EFS. i know it's a 3 year old tablet at this point, but it's been good to me and i'd like to increase my odds of bringing it back to life
Hi,
My OnePlus 3 keeps freezing or crashing, I don't really know; when I get to school and try to unlock the phone the screen won't come on, it just stays black, then I have to hold the power button to force a reboot. It happens really often, I thought it was because of my school's wifi but that's not it because it also does it when at home or after making a call. Sometimes it also randomly soft reboots. I honestly don't know what is happening, I'm running the latest OxygenOS Nougat.
Think about sending it in, sounds weird.
Gesendet von meinem SM-T530 mit Tapatalk
dcf007 said:
Hi,
My OnePlus 3 keeps freezing or crashing, I don't really know; when I get to school and try to unlock the phone the screen won't come on, it just stays black, then I have to hold the power button to force a reboot. It happens really often, I thought it was because of my school's wifi but that's not it because it also does it when at home or after making a call. Sometimes it also randomly soft reboots. I honestly don't know what is happening, I'm running the latest OxygenOS Nougat.
Click to expand...
Click to collapse
Did you update it via OTA? If so, try a clean install of the full ROM.
dcf007 said:
Hi,
My OnePlus 3 keeps freezing or crashing, I don't really know; when I get to school and try to unlock the phone the screen won't come on, it just stays black, then I have to hold the power button to force a reboot. It happens really often, I thought it was because of my school's wifi but that's not it because it also does it when at home or after making a call. Sometimes it also randomly soft reboots. I honestly don't know what is happening, I'm running the latest OxygenOS Nougat.
Click to expand...
Click to collapse
Are you running any custom kernels or a OxygenOS based ROM or just pure stock
crzykiller said:
Are you running any custom kernels or a OxygenOS based ROM or just pure stock
Click to expand...
Click to collapse
Just the stock ROM, no custom kernels whatsoever
I think it has something to do with 4g switching to wifi. I switched the wifi off before I got to school and there was no freeze. Don't know how to fix it though, still unsure over the random reboots.
dcf007 said:
Hi,
My OnePlus 3 keeps freezing or crashing, I don't really know; when I get to school and try to unlock the phone the screen won't come on, it just stays black, then I have to hold the power button to force a reboot. It happens really often, I thought it was because of my school's wifi but that's not it because it also does it when at home or after making a call. Sometimes it also randomly soft reboots. I honestly don't know what is happening, I'm running the latest OxygenOS Nougat.
Click to expand...
Click to collapse
Got the same problem I tried everything nothing works :/
I factory restored my phone, I downgraded my phone, I smashed my phone (out of frustration), I cleared cache but nothing helps I updated 3 times already but no fixes
Mayoketchup said:
Got the same problem I tried everything nothing works :/
I factory restored my phone, I downgraded my phone, I smashed my phone (out of frustration), I cleared cache but nothing helps I updated 3 times already but no fixes
Click to expand...
Click to collapse
Same here, I can,t even configure the phone. Almost instant crash. I used flash method for bricked devices and nothing changed.
Hello. Have you guys found any solutions for this? I am on the latest Oreo Update (full stock) and this happens to me too. It also happened in the latest stable version of Nougat.
Same here! Full stock...
Recently I rooted it so I could read the logs, the key error was:
11-18 11:21:47.581 1176 1176 E AndroidRuntime: at android.view.WindowManagerGlobal.getWindowManagerService(WindowManagerGlobal.java:170)
I contacted support, but for now they just flashed a new 4.5.0 version on it. Problem still exists, so I contacted them again.
Exactly the same problem here (OP3), i tried with 4 or 5 combinations or Rom, Kernels. I completely back to stock + lock bootloader, the problem still persist . The support accepted to launch a repair process last week. They completed the process. It should returned to me today, i have no information about any problem they found on the phone...
I will tell you if they resolved the problem.
martinoouu said:
Exactly the same problem here (OP3), i tried with 4 or 5 combinations or Rom, Kernels. I completely back to stock + lock bootloader, the problem still persist . The support accepted to launch a repair process last week. They completed the process. It should returned to me today, i have no information about any problem they found on the phone...
I will tell you if they resolved the problem.
Click to expand...
Click to collapse
Hi Mate,
do you have an update from them? My phone hangs and goes black screen. Normal power on does not work most of the times. I had to use power + volume up to get the fast boot loader menu. This is really annoying.
Turn off wifi
Turning off WiFi, as suggested previously, seems to resolve the issue, i've exactly the same problem as above, flashing ROMS or Kernels did not solve the issue. It was strange for me as it all began once i upgraded my OxygenOS 4.5.1 with Nougat base to the new 5.0 with Android Oreo. Since then i started reporting system freezes anytime i turn off the screen or it goes to sleep. downgrading did not solve the problem of course. Could it be a hardware related problem??? Strange...
Cheers