Hello. I can't unlock my phone smooth on android 5.x and 6.x (after pressing power button i have to wait 10s+ until screen will wake up), because it doesn't go into deep sleep mode and just working @lowest set frequency . I've tried few roms (e.g. resurrection, nitrogen, aosp, cm...) few kernels (e.g. nitrogenex), fev cpu governors and everytime i had the same problem, even on clean rom, after wiping and configuring only google account without restoring apps, without location, wifi, data etc. I gave up with it some time ago, but now i tried again, new release of resurrection and decided to ask you for help. On stock 4.4.2 it's fine, unlocking instantly, and going into deep sleep normal, but i wanted to get newer android What do you think, is NFC may causing this problem? Because probably i've got broken chip or something, because i can't even turn on nfc, doesn't matter what rom, stock or custom.
Thank for answer
Related
Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.
I have finally decided to give CM13 and related AOSP ROMs a go after the mess I consider MM LG software is. The problem I keep having is calling. No matter what ROM I have (have tried different CM13, Exodus, etc nightlies) all suffer from soft reseting every time I make or receive a call. I have reseted the phone completely, have gone back to LG's software where it works correctly, reinstalled the 21c baseband which is the only one available for AOSP ROMs and practically all the possible roots of error. I have tried other dialers, with & without data enabled, in airplane mode, practically everything I can try and can't really seem to find any answers around the forums without asking. Is there something I can do to remain in one of these ROMs? I really don't want to go back to Stock. :crying: :crying: :crying:
If you flashed open gapps then you need to make the default phone app the phone app. Go into settings and search for phone. Tap on phone app In the results and tap on phone. Select phone for the phone app and you're good to go
Hello people! I have strange problem.
Yesterday my phone freezes and rebooted, SIM was not working. I was on 30.3. 2106 cm nightly.
From that time, my phone randomly freezes and then immediately rebooted.
Before that, I was playing with CPU governor values, can that damage hardware? (No heat or something like that, but SIM)
Tried many cm13 builds, aosp's, fulmics, cloudy, another kernels, reflahed modem, another battery..
Every ROM was after clean install, apps installed from play store, few with restored data, tried with and without them, same with Xposed, doesn't matter anything.
Anyone know what is it? My phone leaving?
Sorry for bad English. Thanks David.
Tell us, which baseband version you have.
Only 21c on cm13 works. So this one.
OK, I had the same problem too.
I fixed it by removing Kernel Adiutor (yeah, Kernel Adiutor). Then I installed V21C (13.2-00002) modem and rpm/tz partitions (V21C too) posted by @Step-han right here.
I don't know how it works on cm but I'm using stock mm and it works good
Let's try it! I will post results
@jaro1221 It works! Thank you man! Maybe it was caused by installing Fulmics, which reflahed modem.
Thanks!
Having this same problem,first the sim not detected,then from a couple of days apparently random freezes and reboots that persist across stock based and aosp/cm Roms. But I noticed that the freezes and reboots occur only when the device is warm. Not hot,warm as in if the CPU temp is above 60�° C. If it is below 60, the phone can be used for hours without a problem. Any ideas? Could it be hardware related? I've used for months my g3 , and it rarely crossed the 70�° , and did not have this problem. I'm using a d855 16 GB if that matters.
Update: Just in case this could be useful for someone. First,my device got worse,it couldn't boot at all even while cold. it could not get past the lg logo,not in rom,not in recovery. I fixed my problem, maybe temporary, by using some folded aluminium foil. I opened the phone, and put some of it between the mother board and the display, in the same place where you can apply the thermal mod,and then some other between the board and the back case, under the place where the power and volume buttons are. I closed the phone and it booted up, I'm using it for half a day now, installed some games, played while monitoring the CPU temperature. It can go up to 70 degrees and it did not freeze,nor reboot as far. I rebooted some times myself to test if it would detect the sim card,and it had no problem so far,but maybe it is to soon to tell. So... I will update if something happens.
Hey guys,
i have been using Ivan Mehler's cm 5.1 rom and since early this year i am on his 6.0 rom and everything was fine until mid june. Since than i have the 'sleep of death' syndrom (phone won't wake up from deep sleep until hard reset). I can keep it from freezing when i stop it from going into deep sleep via apps like 'Safecharge' or having muted music playing in the background. It could be a hardware issue. I have dropped it twice pretty hard, once in 2014 and a second time 2 weeks before the sods started. Else it runs without issues. I reverted to a backup, installed another cm 6.0 rom and reverted back to stock, to no avail.
First, how do i best diagnose whats causing this?
And secondly, are there any leftovers from older roms that could interfere when i install a new rom via twrp and doing a complete wipe including reformatting the file system etc? What i like to know is whether when installing the latest stock rom via odin, does that mean that every bit on every storage/memory of the phone is being completely wiped and newly written, or are there some basic parts of android/linux that would not be touched?
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