so my phone has recently started to reboot when i power off. ive switched roms the problem still persist. is any one having this problem? and did anyone come up with a soloution?.
seems all of a sudden a few people have been having this issue, i was running many roms for a few months with no problems at all then all of a sudden phone just started rebooting after being powered off. people keep saying its something with CWM but i cant fix the issue.
Just copied this from another thread.
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
I did as he said and it did nothing, but just now i tried it again and set the date to 1/1/2011 and now my phone turns off and stays off
Since I was quoted I thought I would jump in and let you know that changing the date for a whole day like I described did work for me. I have since changed back to automatic date and time and so far the phone has been all right for the last few days. (From what I have researched I think this is some kind of daylight savings time change issue or something like that occurring with CWM that some people are having.)
ok so i changed the date and it worked!!!! thank you!!!!!
so mine works correctly as long as i leave it on the wrong date, as soon as i put it on automatic or change it to the correct date it goes back to rebooting
I reinstalled my stock firmware last night with odin (or atlease i think i did..i notice things like my modded recovery still in the system/bin folder, etc) all is working fine but the time seems to change at times, specially after a reboot. I have to go to setting and toggle the the automaic network time box for it to correct the time. my texts are ALL mixed up now due to this. Anyone have any idea whats causing this or how it can be fixed?
I always have this issue as well when I go back to stock, and so far has always been corrected with a factory restore. I consider it the final step when going back to stock now. Hope this helps.
One day my skyrocket started acting up. I have the AT&T version. what happens is The wifi could be working perfectly fine then when i let it sleep and then wake it the wifi is on and sometimes turns right back on and connects and other times it won't turn on, even when I try to manually. I've tried going back to pure stock, ICS Stock, and tried custom roms and it's all the same. Sometimes on first boot the wifi won't even turn on. Then sometimes when I'm out of wifi Range I turn it off and when I come back and try to switch it on it says "Wifi turning on.." then the toggle goes back to off but it still says that. Sometimes when the phone is in use, screen on, I could be browsing the web or on facebook and it shuts off and won't come back on. This has nothing to do with the Power Saving mode, I never touched that setting and I checked and it's set to "Always." So what could it be? It gets extremely frustrating. someone please help me :l
I searched the forums before I posted, I know this may fall into the development category but I couldn't post there..
r0ttenways said:
One day my skyrocket started acting up. I have the AT&T version. what happens is The wifi could be working perfectly fine then when i let it sleep and then wake it the wifi is on and sometimes turns right back on and connects and other times it won't turn on, even when I try to manually. I've tried going back to pure stock, ICS Stock, and tried custom roms and it's all the same. Sometimes on first boot the wifi won't even turn on. Then sometimes when I'm out of wifi Range I turn it off and when I come back and try to switch it on it says "Wifi turning on.." then the toggle goes back to off but it still says that. Sometimes when the phone is in use, screen on, I could be browsing the web or on facebook and it shuts off and won't come back on. This has nothing to do with the Power Saving mode, I never touched that setting and I checked and it's set to "Always." So what could it be? It gets extremely frustrating. someone please help me :l
I searched the forums before I posted, I know this may fall into the development category but I couldn't post there..
Click to expand...
Click to collapse
when you say pure stock, do you mean you odin'ed back to stock? i'm no expert but if you've had the same issues on pure stock rom, custom roms it sounds as though it may be a hardware issue.
ctalcant said:
when you say pure stock, do you mean you odin'ed back to stock? i'm no expert but if you've had the same issues on pure stock rom, custom roms it sounds as though it may be a hardware issue.
Click to expand...
Click to collapse
Well yes odin'd back, & also used kies through download/recovery mode. well the custom roms it does it on are all stock based... well I had installed MIUI but idk If it had done it on there. this issue is very frustrating..
i realized last night that the bluetooth does it too, so if it's a hardware problem does that mean the motherboard could be bad, not the actual components?
Had the M8 for about a week before rooted it and installed CM11-M12. Haven't had any problems for the past ~6 months up until a few weeks ago.
During that time, I upgraded from 3.28.605.4 to the 4.17.605.5 firmware along with CM12 Snapshot (2015-06-25). Things worked fine for over a week until one morning I woke up late and found out the phone's alarm never went off. In fact, the phone was frozen and wouldn't respond to anything. Force powered it off and on again. Upon bootup, there was a message which stated something to the effect that the System UIDs Inconsistent. I think I used the TWRP fix permissions and it went away (but many of the application's settings had been wiped). I continued to use the phone for about another week and noticed a new problem where touches on the softkeys wouldnt always work. Enabled the debugging tools option to show touches and when the problem is occurring, I can see the touch doesnt register to the very bottom of the screen. The rest of the touch screen works fine. The 'pointer location' debugging tool shows multiple touches works fine too. Additionally, some times ghost touches are registered and stuck in the softkey area.
I got fed up with the CM12 bugs and the softkey issues so I went back to my CM11-M12 nandroid backup and was fine for a few weeks before softkey issue came back. Now its happening a lot more frequently. Most often in the bottom right corner of the softkeys and/or ghost presses getting stuck (I have the dev Show Touches always enabled now). I've went back to the 3.28.605.4 firmware, no change. The softkey issue even occurs in TWRP, which would lead me to believe that it's really a hardware problem.
Tried calling Verizon support but soon as they found out its been rooted, warned me that very likely will get charged for a new phone if it got sent into HTC.
Thoughts on a fix or other options?
Got replacement M8 from VZW. restored CM11 via nandroid and this problem no longer occurs.
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!