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!
Hi all.
Is there a known issue with the latest "standard application updates" that may cause the system crashing and rebooting?
I dont know if there is such a thing like "event log" in android to help tracing the error im getting since today.
First time was while I was playing Mortal Kombat X Mobile, game went unresponsive, screen black, charge led was flashing strangely and very short, almost unrecognizable. Now this could perfectly happen just on the homescreen.
Occurs once in a while, Id say almost every 1-2 hours.
Have the latest stock rom , patched, rooted and some minor debloating. Havent touched the system for weeks, everything was perfectly fine, this is the first day it is not.
So if anyone can give me a hint on how to find whats wrong , that would be great.
Guess I'm not the only one! I've been having the same exact problem since yesterday too!
onkelfeix said:
Hi all.
I dont know if there is such a thing like "event log" in android to help tracing the error im getting since today.
Click to expand...
Click to collapse
There is logcat. You're rooted, so it's fine. You can also pull logcat logs via adb. However these logs are cleared once the phone reboots.
I've been having heating issues,very fast battery drain and my camera went back to taking green pictures . It was beacause of updating magisk. I uninstalled it and reflashed the 14v and it is back to normal. I'd recommend seeing if that is the problem
pikeylfc said:
I've been having heating issues,very fast battery drain and my camera went back to taking green pictures . It was beacause of updating magisk. I uninstalled it and reflashed the 14v and it is back to normal. I'd recommend seeing if that is the problem
Click to expand...
Click to collapse
I still have 14.5 installed while it tells me 15.3 is the latest.
No overheating (at least nothing that could be felt on the outside) , camera works as it should.
Did a shutdown and restart, device didnt crash over night, now after its been used for 30minutes, it crashed while reading the news within chrome....
Maybe some kind of Spectre/Meltdown countermeasure patch which affects stability?
Really cant need that as I use my phone for 24/7 support
Just found out that I didn't have the latest build. Was on 47.1.A.5.51 probably.....
Now on 47.1.A.8.49 , still rooted , restored almost everything what has been installed before, so far it has been crash-free since 1-2 hours. If it doesn't crash within the next 24hours , i'll put the simcard back.
Hi,
Hope you are well.
I had bought my Google Pixel about 2 months ago. It was completely new and working fine. I then upgraded it to Android P beta which ofcourse is buggy. After some time, I had random crashes and freezes on my phone so citing that I decided to move back to the stable update. Once I did that, the phone started behaving abnormally. I was unable to use it completely without anything installed or with the usual softwares. It would work fine in Safe Mode. It used to restart and then get stuck at Google Icon with a bar showing at the bottom of it. I then went back to beta where I had the exact issue but it then started working fine. However, yesterday on the beta version as well its speaker did not work. I restarted it and every app got stuck then it restarted on its own and got stuck like the stable version. But I rebooted forcefully and it worked fine. As I have it in warranty from a local vendor (now google in Pakistan), so I decided to reinstall the stable version as we now had June patch. As soon I installed the stable version, without anything installed the phone started restarting just like it used to. It gets stuck on google icon with a progress at the bottom and doesn't work until I use the power button to forcefully shut it down.
I want to unlock the bootloader and flash a previous build but I don't know whether I should do that or just send it back as I am not able to judge up until now whether that's the hardware or the software.
I will really appreciate some help as I have got multiple responses on google searches but these explain motherboard as culprit. :crying:
Update: The phone again is working absolutely fine in safe mode. I just tried that. However, I am unable to even touch it in the normal mode on stable version. I have already tried the rescue OTA.
My phone will occasionally crash and reboot. This only started happening after I updated to 10.3. 0. Also, this only happens when I'm on the Twitter app for some reason. The app crashes then the phone reboots. Any way to fix this?
I dirty flashed 10.3.0 over 9.0.9 and also experienced random black screens, freezes, and reboots along with really bad battery drainage, random app freezing, and occasionally lag (something I've literally never seen on a OnePlus device lol). Anyways, I ended up completely wiping my phone for a clean install and have had 0 problems. I don't think Android likes dirty flashes between different OS versions. I'm on 10.3.0 with magisk 20.2 and xXx NoLimits 9.5 btw.
Hey guys,
Ever since the latest update 10.0.5, I've noticed that my screen is not timing out and remains on until I press the power button. I am rooted with Magisk and am using EdXposed YAHFA with RiruCore.
I have the sleep settings set to 15 seconds in the display option.
The timeout does work properly in certain apps (I've noticed it works fine when I have Brevent open) but is not working in the majority of applications.
I've tried to boot the phone in Safe Mode and the issue persists even there.
Anyone else experiencing the same issue or have any solutions in mind aside from a factory reset? Should I try uninstalling Edxposed and Magisk?
Delete hidden core module and you will be fine. It is a known issue caised by that app as well as crashing chrome. By the way that module doesnt really work. Only fools magisk safety net check. Other checks qill still fail