Related
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
rocksolidsr said:
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
Click to expand...
Click to collapse
could be a ROM/Kernel pairing. have you tried wiping system/data/internal storage - reboot recovery, then flashing a new ROM?
the static screen is common on custom 4.2.2 ROMs, but it's usually a quick flash. I don't get any random reboots though.
I've tried many different rom's along with the Vanquishkitties kernal but still random reboots
I noticed my phone acting weird, specifically it would not play any audio, I noticed this because when I was in the dialer it was going really slow. Then I tried to play some notifications and none worked. I rebooted my phone and all seemed ok, I've attached two logs the first one being while audio would not work and the second after the reboot. I'm not really sure what to look for in the logs but thought someone here might.
This might be something...
E/AudioStreamOutALSA( 300): pcm_write returned error -5, trying to recover
Or this, just a warning though...
W/AudioTrack( 692): obtainBuffer timed out (is the CPU pegged?) 0x63d72108 name=0x6user=00001000, server=00000000
Sent from my Nexus 7 using Tapatalk HD
Just noticed that when in the dialer and the phone starts working very slow, if I turn the sound all the way off, the phone becomes responsive
two more logcats for anyone interested in helping this time one is when trying to use google voice actions, I actually get an error message that says can't open microphone and the other is when someone called me and I did not have any ringtone but I answered and I could not hear them and they could not hear me, shortly after my phone rebooted, I did not catch the reboot in the logcat.
Also when it reboots it doesn't reboot all the way it boots to the boot logo screen and then hangs and I have to hold all three buttons until it reboots again, is there a way to get it to just reboot on its own?
After the reboot everything seems to be fine until I experience the same issues again
Which ROM are you on right now? That sounds like a kernel level issue
Sent from my XT907 using Tapatalk 4 Beta
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
rocksolidsr said:
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
Click to expand...
Click to collapse
Has your issue been resolved? I am almost facing the same issues of random rebooting with my phone and was searching for a solution....
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
5318008 said:
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
Click to expand...
Click to collapse
Im having this issue and Im on kitkat.
Hi guys!
I am using Jamal's Asop google edition 4.4.2 version Final-R4 with alucard_24 newest kernel.
Everything sedms to work well, except one minor problem:
Sometimes when I open an app-folder on my homescreen, the folder somewhat "half-opens" and freezes. It either takes a couple of second until a random app inside the folder opens, or I actually need to press somewhere on the screen and re-open the folder once again. This problem has occured during the latest updates of this ROM, including two different kernels (alucard and ktoonsez). This usually happens couple of minutes after boot, but can occur randomly as well...usually the phone starts to act a bit sluggish during this time period...
What could my problem be? I have made system resets and wiped dalvik&cache. I haven't OC or UV in Stweaks...
I'm on baseband ml6 with new bootloader.
/Limpzon
Installation
https://github.com/LegacyHuawei/local_manifests/wiki/Installation
Bugs
https://github.com/LegacyHuawei/local_manifests/wiki/Status
Downloads
https://basketbuild.com/devs/LegacyHuawei
Changelog
https://github.com/LegacyHuawei/local_manifests/wiki/CM11.0-changelog
If you have any bugs to report, open new issue at https://github.com/LegacyHuawei/local_manifests/issues
Readme
Use the standard Torch app wherever possible, it only enables flashlight. Other apps from Play Store are designed to use the camera interface, which means camera will use additional power.
For more RAM: Settings->Performance->Memory management.
Do not enable KSM, as video encoder/decoder stops working.
HuaweiSettings
Charge current - allows you to set custom charging current. While this actually limits the current input, it effectively decreases or increases the available current transferred to the battery. This is useful in multiple ways:
Slower, but more effective charging. Your battery will last longer.
Faster charging when connected to USB. For example, USB charging is limited to 500mA, but newer PCs allow drawing up to 800mA or even more. This can be configured via the setting.
Manual override of non-standard charger allowing to draw more than 500mA.
Magnetic sensor calibration - lets you delete previous calibration information. This is useful to recalibrate the compass (when it's inaccurate). Just tap the item & then open any compass up to recalibrate your sensor.
If the phone reboots unexpectedly, crash log is found at /data/dontpanic .
To report bugs, use this app: https://play.google.com/store/apps/details?id=com.tortel.syslog
Thank you, i'll try
wow, downloaded...
Many thanks, good job!
after installing cm11 and gapps, the phone always reboot to recovery
ggunzio said:
after installing cm11 and gapps, the phone always reboot to recovery
Click to expand...
Click to collapse
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
before installing the rom, i've wiped everything, data, cache, system and dalvkit cache, reboot recovery. After installed the rom, and right after, installed the gapps. Then, in recovery, reboot system and after it show the huawei logo, it enters recovery without showing the CM logo.
EDIT: i will install ble_part stock, and them install again the B518, repartition again and try to install CM again.
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
ROM and GAPPS, everything works fine.
No glitches for me.
Great job, thanks!
faekplastik3s said:
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
Click to expand...
Click to collapse
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
Well, it stutters a lot, and it's not nearly as smooth as something like Aurora or even stock Huawei ROMs, but I'm sure it's related to the display issues or another issue like that because even scrolling through the Settings app or the little animation in the notification drawer that flips into the shortcuts stutters like hell and drags around, which shouldn't be an issue for this device and wasn't a problem with other ROMs, and overclocking and other user-level optimizations do nothing to alleviate it.
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
do i need to have my phone rooted?
faekplastik3s said:
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
Click to expand...
Click to collapse
This. If some months ago anyone told me I'd be installing 4.4 on this device I'd tell them they were crazy.
Thanks for your amazing work, Blefish
Here its works as it should be, you are awesome blefish
Sent from my SM-T210 with rocketTab 2.1 + MK1 kernel using tapatalk v4
Finally i could get it to boot.
probably i broke something, i've installed the oficial rom and then, with 5.5.0.4 recovery wiped everything. Next installed the blepart, new recovery and its working
Good job sir
Thank you!
faekplastik3s said:
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
Click to expand...
Click to collapse
Yes, I have waking problems too.
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
lemene said:
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
Click to expand...
Click to collapse
is anyone having problems to connect to wifi networks? i cant connect
EDIT: i guess that is a problem with the wireless definition of the rom, im thinking this, because i can connect to open networks, but when i change the segurity of the wlan to wpa or wpa2, i can't connect to it.
Could you look at this @Blefish?
Im not sure if its a bug or not, maybe something is broken in wpa.supplicant
[]
I have flashed BlePart recovery, i have rebooted the recovery and i have flashed blepart 2.2 then i have flashed CVM Version 6.0.4.6. The phone rebooted and now i cant open the phone or recovery. I tried to install offical 2.3 from sd card but i coudn't. How can i recover my phone?
Over the last few days I've been having seemingly random instances where the system slows right down, becomes almost completely unresponsive, the home screen goes blank and sometimes only half the screen displays. I then have to long press to power off, but instead of shutting down the phone reboots, then everything is fine again. Usually this has been happening once every few hours, and when left overnight the display doesn't even turn on prior to rebooting (I can use fingerprint sensor and feel it vibrate to unlock though). A few times I have seen the error message saying 'System UI has stopped' but most times I reboot before seeing that.
I was running stock 8.0 unlocked and rooted with TWRP 3.1.1.0 and Magisk 14, and also using the pixel launcher installed as a system app, with no issues previously. I can't remember exactly now, but I am pretty sure I had this occur while on 8.0 prior to updating to 8.1 (possibly following an update to Magisk 15), but mostly it has been happening post-update to 8.1. I followed the stickied guide using step 9 first, and after that was getting very frequent instances. Then realized I was using an old 8.0 pixel launcher app so thought that might be the problem, so re-flashed everything, updated to TWRP 3.2.1.0, re-rooted and installed pixel launcher via the linked post below. Was then stable for almost 24hrs before having the issue re-occur, but with longer gaps between successive instances. Yesterday I re-flashed using the flash-all script (8.1) to try to clean out any gremlins - all went smooth, then re-flashed latest TWRP/Magisk and installed pixel launcher. Seemed fine for an hour or so...
https://forum.xda-developers.com/nexus-6p/themes-apps/pixel-2-xl-launcher-google-feed-t3715294
Not sure what is going on, I don't think its the zip file, since I checked the hash prior to doing the very first update. Could be the launcher I guess, but wasn't having any issue before so don't see why that would be a problem. Only root apps I'm using are root explorer, naptime and f.lux. Naptime I haven't installed yet on this go around, and f.lux I uninstalled this morning to see if it makes the problem go away. I tried searching around and saw similar issues reported for people using substratum/themes, but I have never used anything like that.
I have a log but can't link it yet...?
cooke6 said:
Over the last few days I've been having seemingly random instances where the system slows right down, becomes almost completely unresponsive, the home screen goes blank and sometimes only half the screen displays. I then have to long press to power off, but instead of shutting down the phone reboots, then everything is fine again. Usually this has been happening once every few hours, and when left overnight the display doesn't even turn on prior to rebooting (I can use fingerprint sensor and feel it vibrate to unlock though). A few times I have seen the error message saying 'System UI has stopped' but most times I reboot before seeing that.
I was running stock 8.0 unlocked and rooted with TWRP 3.1.1.0 and Magisk 14, and also using the pixel launcher installed as a system app, with no issues previously. I can't remember exactly now, but I am pretty sure I had this occur while on 8.0 prior to updating to 8.1 (possibly following an update to Magisk 15), but mostly it has been happening post-update to 8.1. I followed the stickied guide using step 9 first, and after that was getting very frequent instances. Then realized I was using an old 8.0 pixel launcher app so thought that might be the problem, so re-flashed everything, updated to TWRP 3.2.1.0, re-rooted and installed pixel launcher via the linked post below. Was then stable for almost 24hrs before having the issue re-occur, but with longer gaps between successive instances. Yesterday I re-flashed using the flash-all script (8.1) to try to clean out any gremlins - all went smooth, then re-flashed latest TWRP/Magisk and installed pixel launcher. Seemed fine for an hour or so...
https://forum.xda-developers.com/nexus-6p/themes-apps/pixel-2-xl-launcher-google-feed-t3715294
Not sure what is going on, I don't think its the zip file, since I checked the hash prior to doing the very first update. Could be the launcher I guess, but wasn't having any issue before so don't see why that would be a problem. Only root apps I'm using are root explorer, naptime and f.lux. Naptime I haven't installed yet on this go around, and f.lux I uninstalled this morning to see if it makes the problem go away. I tried searching around and saw similar issues reported for people using substratum/themes, but I have never used anything like that.
I have a log but can't link it yet...?
Click to expand...
Click to collapse
Try using supersu again or maybe downgrade magisk. Mine for some reason after going back to supersu randoom reboot stopped. This even after ive downgraded to 8.0 thinking 8.1 was the reason though it was running fine before.
Sent from my SM-N950F using Tapatalk
[email protected] said:
Try using supersu again or maybe downgrade magisk. Mine for some reason after going back to supersu randoom reboot stopped. This even after ive downgraded to 8.0 thinking 8.1 was the reason though it was running fine before.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Thanks will give it a shot and report back. Like I said I think the instability coincided with an upgrade from Magisk 14.0 to 15.0 which happened right before I went to 8.1, so going back to 14.0 might be the first step for me.
Were yours just random reboot or also the system glitching/freezing?
cooke6 said:
Thanks will give it a shot and report back. Like I said I think the instability coincided with an upgrade from Magisk 14.0 to 15.0 which happened right before I went to 8.1, so going back to 14.0 might be the first step for me.
Were yours just random reboot or also the system glitching/freezing?
Click to expand...
Click to collapse
Just random reboot so far
Sent from my SM-N950F using Tapatalk
Well... flashed the Magisk uninstaller from 15.1 and re-flashed 14.0 and no system crashes yet.
However now I can't enable assistant vice activation. Possibly a separate issue I suppose, but it was working before.
Edit: Uninstalled Google app updates and reapplied from play store and now working.
So just as a follow up I've been running fine on Magisk 14 without issue for some time now. Have not tried the recent 15.2 release.
However f.lux is not behaving normally and for some reason is acting almost like a yellow filter. I found the thread below which seems to indicate some issue between f.lux / Android 8.1 / Magisk.
https://forum.justgetflux.com/topic/4667/f-lux-not-compatible-with-android-oreo-8-1/7
I have been having this exact problem on my Nexus 6P. Glad to know that I'm not going crazy. The switchover point for me was exactly from Magisk 14.5 to 14.6. 14.5 works fine for me with no issues. 14.6 and onwards (including 15.2) has exhibited this behavior very regularly.
One thing that I just tried that might have "fixed" it is I recently was in 15.2 beta (installed via TWRP) and it was having the problem. I was on the beta in order to capture some of its verbose logs. At one point, I wanted to just try a different installation method so I made sure to check the two options in the MagiskManager ("forced encryption" and "dm-verity") so that they are on and then reinstalled Magisk 15.2 directly from MM. After doing that, I haven't seen the issue crop up, so maybe installing from MM to make sure that it uses those options on install is the way to address this? I'll update if I see any more issues.
Thanks for the replies here and in the Magisk beta thread.
After installing with your described method/settings I reinstalled f.lux, and had a couple of glitch/reboots. I then uninstalled f.lux and I'm now over 24hrs without going into the glitched state. So it seems maybe this a compound issue. Can you confirm whether you had this or another similar app installed? I've seen other reports of this kind of behavior when using substratum.
mastercko said:
I have been having this exact problem on my Nexus 6P. Glad to know that I'm not going crazy. The switchover point for me was exactly from Magisk 14.5 to 14.6. 14.5 works fine for me with no issues. 14.6 and onwards (including 15.2) has exhibited this behavior very regularly.
One thing that I just tried that might have "fixed" it is I recently was in 15.2 beta (installed via TWRP) and it was having the problem. I was on the beta in order to capture some of its verbose logs. At one point, I wanted to just try a different installation method so I made sure to check the two options in the MagiskManager ("forced encryption" and "dm-verity") so that they are on and then reinstalled Magisk 15.2 directly from MM. After doing that, I haven't seen the issue crop up, so maybe installing from MM to make sure that it uses those options on install is the way to address this? I'll update if I see any more issues.
Click to expand...
Click to collapse
Hey just a heads up - I am now on opm3 (Jan) and 15.2 beta with the just preserve encryption checked and no glitches yet after ~15hrs. Will be installing f.lux soon to see if it triggers.
Installed f.lux and maybe an hour later started glitching. Uninstalled and had to reboot to clear things up, and now haven't had a glitch since. So definitely the source of the issue, but it's a compound thing since it only started happening since Magisk 14.6 onward. However, there are other reports saying f.lux hasn't been behaving properly on both 8.0 and 8.1, so likely not the fault of Magisk at all.
Hey, I was linked to this thread from Magisk thread, I had the same issue on my Nexus 5X with Magisk 14.6+, so I uninstalled f.lux and issue is gone as you said. Now I'm testing CF.lumen on Magisk 15.3 and it is w/o any issue so far.
Community of xda I need your help in the following:
I recently made a change and received a g4 plus motorcycle, originally had the patch on November 1 or September, one of those two
I have downloaded the complete firmware that included the patch NPJS25.93-14-15
1. I have the bootloader unlocked
2. I have ElementalX + root + xposed + greenify to hibernate my applications
Where does my post come from? simply that I am noticing that my battery is draining until when I have the screen off since I use whatsapp web
What do you recommend me to do?
Is there a profile for elementax that solves the problem ???
Absolutely no battery drain here with NPJS25.93-14-15 and ElementalX kernel. Must be on of your third party apps.
How I can recalibrate battery in system 50% in recovery 11%!?
xjj7 said:
How I can recalibrate battery in system 50% in recovery 11%!?
Click to expand...
Click to collapse
This is my battery history, without root, without xposed, only full stock
pure screen installed by installing the app and just installed the stock software last with the February 2018 patch
some help?
Could it be my battery problem?
better do a factory reset to fix your issue...
I can see you have used the Google voice typing ???
Absolutely no battery drain here using latest stock rom with EX Kernel.
My Moto G4, keeps restarting very often after installing this latest patch.
Can someone help me to get this resolved (or) how can i remove this patch?
This just keeps me frustrating as every now and then, even when i'm on a call with someone (or) whatever i keep doing with my phone - it restarts
Thanks