Skip to content
This repository has been archived by the owner on Oct 7, 2018. It is now read-only.

Random black screens #21

Open
AlvaroBrey opened this issue Feb 20, 2017 · 121 comments
Open

Random black screens #21

AlvaroBrey opened this issue Feb 20, 2017 · 121 comments
Labels
bug-verified critical

Comments

@AlvaroBrey
Copy link
Member

AlvaroBrey commented Feb 20, 2017 •
edited
Loading

Random black screens with white led on are reported on most nougat ROMs for this device.
Edit: ramoops has been enabled, issue seems related to modem
@marchi19217
Copy link

This has happened to me on other ZUK ROMs but not this one thus far. I did make sure I erased all storage including SYSTEM when flashing this ROM

@marchi19217
Copy link

Can confirm this is present on my device
bugreport-NMF26V-2017-02-25-10-34-27.zip

@koichirose
Copy link

koichirose commented Feb 27, 2017 •
edited
Loading

Managed to get a console-ramoops thanks to the latest build (20170224). The file was stored in /sys/fs/pstore.
Attaching it here, hope it's useful!
console-ramoops-koichirose-20171227.txt

@koichirose
Copy link

Happened again after a couple of days.
Error is the same (something about SLPI), this time it happened right after I turned on the screen.

Can I help out in some other way?
console-ramoops-koichirose-20170302.txt

@AlvaroBrey
Copy link
Member Author

AlvaroBrey commented Mar 2, 2017 •
edited
Loading

Thanks @koichirose , the fact that it's the same error is good, means that it's not a coincidence.
SLPI is apparently related to the modem but the information in the ramoops is pretty limited. I'm still investigating.

@fraCPH
Copy link

fraCPH commented Mar 3, 2017

I can easliy reproduce the bug, I also posted an adb bugreport on the zukfans forum.
Let me know if I can be of any help with a log, and how to get it. I'm with stock ZUI and not rooted though.

@AlvaroBrey
Copy link
Member Author

AlvaroBrey commented Mar 3, 2017 •
edited
Loading

@fraCPH It would be interesting to know how you can reproduce the bug
Edit: also, where did you post the bugreport? Link?

@fraCPH
Copy link

fraCPH commented Mar 3, 2017

These posts:
http://zukfans.eu/community/threads/zuk-z2-multiple-roms-freeze-with-white-led-on.3514/page-5#post-30742
http://zukfans.eu/community/threads/zuk-z2-multiple-roms-freeze-with-white-led-on.3514/page-6#post-31332
My phone never freezes if I keep it in airplane mode (whether wifi is ON or OFF), but as soon as I switch off the airplane mode it's a matter of seconds/minutes and it freezes. This has happened once with a SIM card in place and several other times with no SIM card in.

@poseidonss
Copy link

I can reproduce the bug easely also. What can I do to help you guys?

@fr0x3n
Copy link

fr0x3n commented Mar 7, 2017

Hi ontherunvaro,
I'm not an android dev but I'm facing the same issue (freeze black screen with notification led on). If I can be of any help, please let me know.

Also considering that we have to force a reboot (long press power button) I don't know how to extract a log that contain relevant information. Would you be so kind to explain how so I or any other can provide you with multiple log?

I've run different test here :
- never freeze while connected
- never freeze while screen on (at least for me)
- freeze always occured while phone locked
- I've been running "screen backlight off" instead of locking the phone and it never freeze since (about a month) except while I accidentally lock.

@AlvaroBrey
Copy link
Member Author

@poseidonss , @fr0x3n
Logs after a kernel panic can only be found in console-ramoops:
adb shell cat /sys/fs/pstore/console-ramoops > ramoops.txt on your computer, on the first reboot after the black screen. Obviously you need adb installed on your pc, and usb debugging enabled on the phone.

@koichirose
Copy link

@poseidonss, @fr0x3n you can also do it directly on the phone as I did, simply open a root browser, copy /sys/fs/pstore/console-ramoops somewhere in local storage and then post it here.

@fr0x3n
Copy link

fr0x3n commented Mar 7, 2017

well I tried but I don't have any "pstore" folder in /sys/fs/
I also tried to search for a "console-ramoops" file in / but nothing came up (except "console-ramoops-koichirose-20171227.txt" from my download folder)

Is there any other command to launch prior to that in order to activate monitoring?

@koichirose
Copy link

@fr0x3n you need to be at least on build 20170224, it was enabled in that build.
https://github.com/ontherunvaro/android_device_zuk_z2_plus/wiki/Changelog

@fr0x3n
Copy link

fr0x3n commented Mar 7, 2017 •
edited
Loading

Ahhh thats why... Sorry for my noob question but I'm current on Dirty_Unicorn_z2_plus_7.1.1_20170206-2233.v11.0-UNOFFICIAL

What rom do I need to flash ? Or maybe I can stay with this rom and flash something else?

@AlvaroBrey
Copy link
Member Author

AlvaroBrey commented Mar 7, 2017 •
edited
Loading

@fr0x3n issues in this repository are just for my LineageOS builds, not for any other ROM.

@fr0x3n
Copy link

fr0x3n commented Mar 7, 2017

ok my mistake again though this issue is general on any rom i've tried.
I'm downloading your rom and keep you posted.

Thanks

@poseidonss
Copy link

ramoops.txt
ramoops1.txt

Here are the ramoops files.

Its very easy to reproduce so I did it twice.

@poseidonss
Copy link

ramoops_lineageos.txt
These two I posted was with lastest stock chinese rom.
This one is with lineageos.

They all happen the same way:
Right after I lock the screen.

@poseidonss
Copy link

poseidonss commented Mar 11, 2017 via email

@SuperLamic
Copy link
Contributor

@poseidonss what are the steps to reproduce it? I'm running my phone for a week on Lineage and I haven't had any reboot/black screen.

@poseidonss
Copy link

@SuperLamic I just need to lock the screen.

@SuperLamic
Copy link
Contributor

@poseidonss have you tried reflashing the phone via qfil (zui 2.5) and flashing Lineage back?

@poseidonss
Copy link

@SuperLamic Yes, I think I flashed every rom there is. No success. The only thing that keeps the phone working is a wakelock app.

@marchi19217
Copy link

marchi19217 commented Mar 15, 2017 •
edited
Loading

Did you try formatting all partitions including system/cache/data? Also try after a clean install with no third party apps

Seems you have hardware issues. Regardless it's not specific to this ROM

After 2 months of using this rom I have experienced the black screen once

@fraCPH
Copy link

fraCPH commented Mar 17, 2017 •
edited
Loading

Seems you have hardware issues. Regardless it's not specific to this ROM

That's not very encouraging.
@ontherunvaro are there any comments about the ramoops posted by @poseidonss ?
Is it worth that someone else tries installing your ROM to produce other bug reports, or, given that this is (likely) a baseband problem, you cannot do anything about that ?
In this case I would keep the stock ZUI to maintain the warranty and send the phone back.

@SuperLamic
Copy link
Contributor

@ontherunvaro seems like a hard reboot (via holding power button). Indeed I find it in most logs too. Maybe they don't understand that they have to grab the log RIGHT when their device first boots into android... I don't know, but these logs are without any error. (that would cause kernel panic)

@poseidonss
Copy link

poseidonss commented Apr 6, 2017 •
edited by AlvaroBrey
Loading

I, rarely, can make this bug stop if I'm lucky(its totally random) flashing a ROM. The phone don't crash, even without wakelock app, until I reboot it then start crashing again. So there might be a way to stop this crash to happen.
I also can make it crashes even with the wakelock app, I just need to put it in airplane mode.

@koichirose
Copy link

koichirose commented Apr 7, 2017 via email

@SuperLamic
Copy link
Contributor

@koichirose you can't reboot into download mode at all (it reboots into it when crash happens)

@koichirose
Copy link

koichirose commented Apr 7, 2017 via email

@SuperLamic
Copy link
Contributor

@koichirose when you need to use qfil, you use download mode

@koichirose
Copy link

koichirose commented Apr 7, 2017 via email

@AlvaroBrey
Copy link
Member Author

@koichirose I'll try to explain it neatly:

  • EDL/download mode is a low-level utility that allows you to flash a ROM directly to the phone memory even if recovery/etc are broken. As such, it is invaluable in case of a brick because it has the potential to repair it.
  • Black screens are happening because when the phone crashes, instead of rebooting (normal behaviour), it's entering download mode for some reason.
  • In the previous build I disabled this behaviour, but in doing so I inadvertently disabled the possibility to enter download mode willingly.
  • I am going to try to disable the black screens without disabling download mode altogether, just haven't gotten to that yet.

Hope that clears things up

@koichirose
Copy link

koichirose commented Apr 7, 2017 via email

@koichirose
Copy link

Just wanted to report that since I installed release 20140407 (5 days ago) I had zero black screens.
The changelog only mentions the reverted reboot workaround, did anything else change?

@AlvaroBrey
Copy link
Member Author

@koichirose I'm happy to read that but unfortunately no, I didn't change anything else related to reboots on latest release.

@poseidonss
Copy link

poseidonss commented Apr 13, 2017 via email

@poseidonss
Copy link

poseidonss commented Apr 13, 2017 via email

@fraCPH
Copy link

fraCPH commented Apr 13, 2017

@poseidonss can you name your wakelock app? I'd like to test it.

@poseidonss
Copy link

poseidonss commented Apr 13, 2017 via email

@fraCPH
Copy link

fraCPH commented Apr 14, 2017

I tried it this morning and after 4 hours I believed I had solved the problem, but then I had another crash, and then another one after 1 hour.
In both cases the phone freezed again a couple of times during the reboot.
Here are the logs I collected as soon as I finally managed to boot into the OS.

console-ramoops 17-04-14-01.txt
console-ramoops 17-04-14-02.txt

@lastfreenick
Copy link

I've been using the rom for a few days now and all of a sudden the black screens started to show up two or three days ago which is strange because I had none in the beginning and then I realized after installing the rom I played around with the settings and set the networks of both simcards I use to prefer 3g networks because my provider does not offer 4g. Playing around in the settings again about three days ago I set both sim cards back to lte preferred.
Today, after remembering that the black screens are baseband related, I set the simcards to 3g for my data card and 2g for my voice card and went from half a dozen black screens to none so far.
Of course this could be a coincidence, but maybe someone with lots of black screens could test it out.

@zhadel2
Copy link

zhadel2 commented Apr 15, 2017 •
edited
Loading

i'm using 20170414 rom without Gapps, without root,, black sceen with led on for me with ur latest rom:
ramoops.txt
ramoops1.txt

@zhadel2
Copy link

zhadel2 commented Apr 20, 2017

i don't have this problem with zui 2.3 oficial rom, all other, i get black screen

@AlvaroBrey
Copy link
Member Author

Unfortunately seems the reboot workaround has stopped working on build 20170811

@AlvaroBrey
Copy link
Member Author

Reboot workaround is back via z2-dev/android_kernel_zuk_msm8996@6227844

@koichirose
Copy link

@ontherunvaro I don't have any issues on 20170811 about black screens/reboots.
I don't know if you remember, but I've had this issue in every build until this: #21 (comment)

@poseidonss
Copy link

I had no more "white led of death" in this last build. I dont need to use wakelock anymore.

@AlvaroBrey
Copy link
Member Author

@poseidonss @koichirose That is probably because this last build has a constant kernel wakelock, sadly. We will see if the next release (without said wakelock) still works for you.

@koichirose
Copy link

@ontherunvaro an interesting thing: my problems where "fixed" approx on April 5, see here.
I moved to a new office in the beginning of April, I had zero black screens for months until a few days ago...when I moved back to the same area as my old office.
I got a couple black screens in the last few days. I'm pretty sure that, for me, this is related to some cell around where I work.

Just heard you'll stop supporting this ROM, I'm really sorry to hear that. Hope everything will be ok for you. Thank you for this amazing ROM, I wish you all the best.

@AlvaroBrey
Copy link
Member Author

@koichirose We were suspecting modem from the start, weren't we? Your comment only makes me more suspicious of that.

Also, I will be ok, don't worry. Just going to be very busy for a few months.

@AlvaroBrey AlvaroBrey mentioned this issue Sep 29, 2017
Closed
@shaicoleman
Copy link

Workaround that works for me is to switch to 2G when charging and back to 3G on battery power. I use Automagic to automate that

@Mixxer5
Copy link

Mixxer5 commented Dec 14, 2017

If someone's still looking at this thread/build: I wanted to confirm what @koichirose wrote. For me black screens started (again) with newest build (20171120) and wasn't present with older one (20171014). I updated my phone at work and it worked perfectly until I came home. Now it goes black right after reset (I can see launcher screen and then it goes off). So it must be some kind of network issue.

@sisqoboy
Copy link

Hi

Has any solution been found for this issue? Can we force the phone to reboot instead of the black screen?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug-verified critical
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests