I am annoyed by this random reboot issue still being unsolved.
Please if someone can help with troubleshooting the errors in last_kmsg:
"unable to handle the NULL pointer dereference at virtual address...... "
"unable to handle the paging request at virtual address........"
I am not an expert but I have read on the Internet about Linux kernel "oops" leading to kernel panic and reboot.
Can anyone build a fix for the Android kernel to handle these oops errors and not panic? Or can anybody read these last_kmsg files and tell me what is causing this?
last_kmsg files attached.
im going to check them out shortly, but kernel panics can be caused by just about anything. even a simple derp, will lead to a kernel panic, which will lead to a reboot.
---------- Post added at 07:04 PM ---------- Previous post was at 06:55 PM ----------
Zaeem Adil said:
I am annoyed by this random reboot issue still being unsolved.
Please if someone can help with troubleshooting the errors in last_kmsg:
"unable to handle the NULL pointer dereference at virtual address...... "
"unable to handle the paging request at virtual address........"
I am not an expert but I have read on the Internet about Linux kernel "oops" leading to kernel panic and reboot.
Can anyone build a fix for the Android kernel to handle these oops errors and not panic? Or can anybody read these last_kmsg files and tell me what is causing this?
last_kmsg files attached.
Click to expand...
Click to collapse
if youre using avast security software, i think its causing it, or is playing a role in it. but thats my guess, not 100%.
simms22 said:
im going to check them out shortly, but kernel panics can be caused by just about anything. even a simple derp, will lead to a kernel panic, which will lead to a reboot.
---------- Post added at 07:04 PM ---------- Previous post was at 06:55 PM ----------
if youre using avast security software, i think its causing it, or is playing a role in it. but thats my guess, not 100%.
Click to expand...
Click to collapse
Thanks
I am currently using avast but these kernel_panics occur without any 3rd party app installed at all.
are you completely stock? the kernel panics occur not because of the kernel, it just reacts to the oops. anything, including rim, apps, data flow, your router, etc can cause them. sounds like you get them often, which you shouldnt. if rarely, then id say it was normal, but often isnt normal.
oh, i said avast because it shows up twice, right before stuff goes wrong.
simms22 said:
are you completely stock? the kernel panics occur not because of the kernel, it just reacts to the oops. anything, including rim, apps, data flow, your router, etc can cause them. sounds like you get them often, which you shouldnt. if rarely, then id say it was normal, but often isnt normal.
oh, i said avast because it shows up twice, right before stuff goes wrong.
Click to expand...
Click to collapse
Yes I am completely stock and yes I get reboots very often. Please guide me how to get to the actual culprit which is causing this. I have uninstalled avast.
I got 3 reboots in last 5 minutes here are the logs.
Zaeem Adil said:
I got 3 reboots in last 5 minutes here are the logs.
Click to expand...
Click to collapse
Flash some other kernel. If it doesnt work its either rom or hardware related
lolerpro8 said:
Flash some other kernel. If it doesnt work its either rom or hardware related
Click to expand...
Click to collapse
I have used Franco kernel on stock 4.4.4 and I even tried CM11 the problem persisted in both situations. Suggest me some better kernel I'll try it.
try without any custom kernel, stock kernel.. problem persists? go get an RMA, its not supposed to be happening. actually, i have never seen so many wdog bites!
Zaeem Adil said:
I have used Franco kernel on stock 4.4.4 and I even tried CM11 the problem persisted in both situations. Suggest me some better kernel I'll try it.
Click to expand...
Click to collapse
Flash factory images. If it doesn't work its hardware related
lolerpro8 said:
Flash factory images. If it doesn't work its hardware related
Click to expand...
Click to collapse
this. if still happening, go get it exchanged.
lolerpro8 said:
Flash factory images. If it doesn't work its hardware related
Click to expand...
Click to collapse
I flashed factory images and the issue is still there. There is an app named stability test on play store it runs several stress tests on the cpu at different frequencies and also on the ram. I ran it and during the tests the device temp got up to 45 degrees and even after 50 successfull cpu runs on all the 4 cores and 500 successful ram runs the device didn't reboot. If it is hardware related why does it pass the stress test over n over again? One thing more, the device reboots most of the time when it is connected to internet through wifi or mobile data. I am doubtful that it is something related to the modem drivers. I found stock flashable radio images n i flashed them but the problem is still there.
Zaeem Adil said:
I flashed factory images and the issue is still there. There is an app named stability test on play store it runs several stress tests on the cpu at different frequencies and also on the ram. I ran it and during the tests the device temp got up to 45 degrees and even after 50 successfull cpu runs on all the 4 cores and 500 successful ram runs the device didn't reboot. If it is hardware related why does it pass the stress test over n over again? One thing more, the device reboots most of the time when it is connected to internet through wifi or mobile data. I am doubtful that it is something related to the modem drivers. I found stock flashable radio images n i flashed them but the problem is still there.
Click to expand...
Click to collapse
When you talk about hardware problems you can only speculate. There is most likely cpu related. If it was software related, flashing other fitmware would fix the problem. Since it doesn't the only answer is hardware
https://www.dropbox.com/s/j7o39s38anhc7cy/2014-08-17_08.13.zip
Sent from my Nexus 5 using XDA Premium 4 mobile app
Related
Hello guys
Please excuse me if this has already been posted before!
I've heard things about the camera not working in 4.4.4. Mine doesn't as well - only in safe mode. No matter what. Then I tried to pinpoint a 3rd party app that could've blocked the camera, both the back and the front (mostly front), but the issue keeps getting on top. I just rooted my N5 and installed PA, and the issue is still on! I haven't even installed the G-apps yet.
Any ideas?
Thank you so much!
install the gapps, but do not install/restore your other apps yet! try to see if the cam works. if so, install your apps after. to me it sounds as an app is causing you issues. btw, have you tried clearing the camera apps data? and by not working, what error do you get?
Install a different kernel PA uses stock Google kernel
spinninbsod said:
Install a different kernel PA uses stock Google kernel
Click to expand...
Click to collapse
what does the stock kernel have to do with the camera not working??? the right answer is absolutely nothing.
Because the kernel connects the hardware to the software and the kernel has all the drivers in it
spinninbsod said:
Because the kernel connects the hardware to the software and the kernel has all the drivers in it
Click to expand...
Click to collapse
so, all those unrooted nexus 5, running stock kernels, all have non working cameras? lol!
Well do you have any other reason maybe it is just an isolated incident with his specific device with the kernel maybe it's not functioning properly
spinninbsod said:
Well do you have any other reason maybe it is just an isolated incident with his specific device with the kernel maybe it's not functioning properly
Click to expand...
Click to collapse
A kernel has nothing to do with the camera, or do you have proof that it does?
Well if the kernel has nothing going to do with the camera what does?
spinninbsod said:
Well do you have any other reason maybe it is just an isolated incident with his specific device with the kernel maybe it's not functioning properly
Click to expand...
Click to collapse
well, the probability that its something else besides the kernel is off the charts. most likely it is an app, or corrupt data. actually, in my 6 years with android, not once have i seen a camera issue caused by the stock kernel. now a custom kernel can have issues with the cam, but thats usually because something was forgotten to be added. oh, and a rom can cause camera issue, which is the #2 spot of where his issue might come from. many times i have seen custom roms forget to add in all the needed camera libs.
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
spinninbsod said:
Well if the kernel has nothing going to do with the camera what does?
Click to expand...
Click to collapse
the libs for the camera, which comes from the rom, which people forget to add to their roms often enough.
you have not right camera blobs
that very well could be as well..
simms22 said:
install the gapps, but do not install/restore your other apps yet! try to see if the cam works. if so, install your apps after. to me it sounds as an app is causing you issues. btw, have you tried clearing the camera apps data? and by not working, what error do you get?
Click to expand...
Click to collapse
Thanks for your reply! I'll try this right away. Is there any way I can install the Google Play market without having the Gapps? Otherwise I'll try to go for the minor Gapps ibcluding the most important ones - if of course it happens to work without it.
Clearing data causes it to say that it cannot connect to the camera!
Bad news. Clean PA Install - no Gapps and the problem is still on my agenda!
Any other suggestions? It cannot be hardware; why else would it work in safe mode?
Hey guys,
ive tried different roms (stock cm11s, mahdi, droidkang) with different kernels (stock, franco, ak).
I have completely wiped my device and set up everything new.
Still im getting reboots every now and then.
Mostly it happens to me while im surfing with chrome, but it also happened in the gallery, while watching movies and so on. Never had a problem while gaming.
Last_ksmg always says "kernel panic", followed by "failed to stop secondary cpus".
Please see the linked last_ksmg files.
https://dl.dropboxusercontent.com/u/16054199/last_kmsg6
https://dl.dropboxusercontent.com/u/16054199/last_kmsg7
Any help is highly appriciated, im getting really frustrated...
Are you using any kernel apps? What other apps are you using? Are you running Xposed?
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
soulcrash said:
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
Click to expand...
Click to collapse
Try reflashing everything through fastboot. Each individual partition, just to make sure everything is clear and wiped.
soulcrash said:
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
Click to expand...
Click to collapse
I was having reboot issues will using both DPI changer and textdroider from the playstore. I would suggest getting rid of textdroider DPI and instead manually change it. Go into your file manger then system/build prop and look for LCD.density. It fixed my rebooting issues running Jedi Open Source rom.
Sent from my Oneplus one using XDA Free mobile app
Hey guys,
i have fastboot flashed the stock images of 25r, 33r and 38r, and even without installing one single app or changing any system settings, i get reboots.
Any ideas left, or is my hardware defect?
soulcrash said:
Hey guys,
i have fastboot flashed the stock images of 25r, 33r and 38r, and even without installing one single app or changing any system settings, i get reboots.
Any ideas left, or is my hardware defect?
Click to expand...
Click to collapse
Reboots are usually on the software level, but 38R actually had reboot problems. Best if you installed a custom kernel and tweaked it yourself, say AK.
Well, i have tried almost every possible rom-kernel-modem combination, including stock images with fastboot. I dont know where this could be a software problem...
soulcrash said:
Well, i have tried almost every possible rom-kernel-modem combination, including stock images with fastboot. I dont know where this could be a software problem...
Click to expand...
Click to collapse
Yes, but I and a couple of friends get those reboots too. It's a common problem, not easily diagnosed. If your last_kmsg gets written to, it's saying that a configuration has crashed and the software itself is requesting a forced reboot.
If the last_kmsg has nothing inside then it's obviously a hardware issue.
Sent from my OnePlus One using Tapatalk VIP
Hmmmm...
You say i should set up the ak kernel until it works on my device ... I have no clue what all these detailed settings, apart from mhz and voltage mean - can u recommend some "safe" settings for me?
soulcrash said:
Hmmmm...
You say i should set up the ak kernel until it works on my device ... I have no clue what all these detailed settings, apart from mhz and voltage mean - can u recommend some "safe" settings for me?
Click to expand...
Click to collapse
After you install ak, install UKM (flashable zip in recovery) and then install Synapse from the Play Store. Then go into Synapse and swipe the drawers to see these options.
CPU:
Set a safe non overclocking frequency
Governor: slim
Hotplug: CPU Boost by CyanogenMod
GPU Governor: msm-adreno-tz
Memory: Drop Caches Enabled
USB Fast Charge Disabled
Log Creation disabled.
Thanks for your help man, i still get reboots, im back at my nexus5 and wait if someone from the opo support answers me ... Frustrating.
have you the problem on all ROms after updating to R38? Some ppl are reporting that after R38 Update even other ROm Versions does the Random Reboot Bug....
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
I have the same problem with craching and rebooting on both Tab2`s in the house.
One completly stock and one with CM11.
Mabye an faulty app ?
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Well, it is happening with everyone, the apps have become memory hungry and our devices lack RAM, andoid L, and our device kernel is full of bloatwares, our devs are trying very hard to overcome this, and we hope they will succeed in this too.
many people are of the view that android M has better management of ram, and I have seen in other devices that have confirmed they are experiencing better stability than lollipop. well on our device it's still in alpha stage, so wait and watch. till then keep your tab less burdened.
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Zte blade l said:
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Steveh8204 said:
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
No need for that, just follow the original thread, bugs have been squashed. There are no more random reboots on latest builds.
I am on my second moto G 2015 from koodo now and this one random reboots like the first one. I seem to have tried nearly everything but may have a log with the answer this time. Any help appreciated.
Another reboot log
Got another reboot an hour later. Here's another log. These reboots happen no matter what rom.
"Fatal signal 11" is the key here, it's a segmentation fault, meaning that the program (libc in this case) accessed a memory location that was not assigned... Since libc is a core library, this should go back to the CM team as a bug report, there is nothing you can do about it.
Of course, this is assuming you have done a clean flash with recommended Gapps, and not restored any data from TiBu or any other tool, if you have you need to do that first to verify it is not an app conflict.
acejavelin said:
"Fatal signal 11" is the key here, it's a segmentation fault, meaning that the program (libc in this case) accessed a memory location that was not assigned... Since libc is a core library, this should go back to the CM team as a bug report, there is nothing you can do about it.
Of course, this is assuming you have done a clean flash with recommended Gapps, and not restored any data from TiBu or any other tool, if you have you need to do that first to verify it is not an app conflict.
Click to expand...
Click to collapse
Thanks acejavelin. I did a clean flash many times and didnt install any additional apps. I even restarted in safe mode to confirm that an app wasnt the cause and still got reboots. I tried with both open gapps and dynamic with same results on two different phones. Even tried a new sim card.
jackching said:
Thanks acejavelin. I did a clean flash many times and didnt install any additional apps. I even restarted in safe mode to confirm that an app wasnt the cause and still got reboots. I tried with both open gapps and dynamic with same results on two different phones. Even tried a new sim card.
Click to expand...
Click to collapse
Then I would suggest opening a bug report with the Lineage team (I'm guessing it's latest LM already from logs).
acejavelin said:
Then I would suggest opening a bug report with the Lineage team (I'm guessing it's latest LM already from logs).
Click to expand...
Click to collapse
I posted my logs in the lineage thread if thats what you mean. It is the latest but also happens with aosp roms.
jackching said:
I posted my logs in the lineage thread if thats what you mean. It is the latest but also happens with aosp roms.
Click to expand...
Click to collapse
This could be a hardware glitch too... We have started seeing a few Moto G 3rd Gens where the emmc chip is starting to fail, not sure if it's a poor quality nand chip or just a fluke, but seen probably a dozen or so in the last couple months fail. That could cause a similar error if it is inconsistent.
acejavelin said:
This could be a hardware glitch too... We have started seeing a few Moto G 3rd Gens where the emmc chip is starting to fail, not sure if it's a poor quality nand chip or just a fluke, but seen probably a dozen or so in the last couple months fail. That could cause a similar error if it is inconsistent.
Click to expand...
Click to collapse
Thats what im starting to believe it is. I've did a lot of research and tried pretty much everything it seems. That is probably why koodo is selling them as "Certified pre-owned" phones. I sent my first one back and they replaced it with another pre-owned that is doing the same thing. I see reports of it on google happening to different gen moto phones but dont seem to be any solid answer for it.
Factory firmware
acejavelin said:
This could be a hardware glitch too... We have started seeing a few Moto G 3rd Gens where the emmc chip is starting to fail, not sure if it's a poor quality nand chip or just a fluke, but seen probably a dozen or so in the last couple months fail. That could cause a similar error if it is inconsistent.
Click to expand...
Click to collapse
After wiping my phone completely and putting on factory firmware, i havent gotten a reset once in two days while running the factory firmware. I dont really understand why it wouldnt reboot now. Are there parts of the software that stays on the phone even after a total wipe? Should i be installing factory firmware between each rom install? I never had this type of problem with xt1032 (falcon). I always do a full wipe between roms.
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
What version of magisk are you using?
snake218 said:
What version of magisk are you using?
Click to expand...
Click to collapse
it's v16 stable
boydzethuong said:
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
Click to expand...
Click to collapse
Bro I'm having the same, loosing randomly my second sim card... Thought it was caused by some apps abusing of phone permission, but no luck it's not that. I cleared cache and art yesterday, now it's has not happened, but I guess it will happen again soon
Tonio78r said:
Bro I'm having the same, loosing randomly my second sim card... Thought it was caused by some apps abusing of phone permission, but no luck it's not that. I cleared cache and art yesterday, now it's has not happened, but I guess it will happen again soon
Click to expand...
Click to collapse
it will, unfortunately. i tried almost everything except uninstall magisk, lose root and restore TA & stock image. maybe it will fix the problem but whats the point if we no longer have root right?
back to nougat it was running flawlessly so i have a doubt that it has something to do with the combination of oreo + magisk + ta_poc method but i have no idea.
in ta_poc method i see it executes something like ua_modem_switcher. does it has something to do with modem?
@serajr you mind having a look pls. sorry to bother you the master but im running out of hope...
boydzethuong said:
it will, unfortunately. i tried almost everything except uninstall magisk, lose root and restore TA & stock image. maybe it will fix the problem but whats the point if we no longer have root right?
back to nougat it was running flawlessly so i have a doubt that it has something to do with the combination of oreo + magisk + ta_poc method but i have no idea.
in ta_poc method i see it executes something like ua_modem_switcher. does it has something to do with modem?
@serajr you mind having a look pls. sorry to bother you the master but im running out of hope...
Click to expand...
Click to collapse
Yes, removing magisk will lead to loose root access. But we can keep SONY features with kernel and TA.
The idea is :
-trying running stock OREO without root
-then adding custorm kernel with or without TA (original or drm_fix)
-at least adding magisk
I guess we need to try each step for a while
Maybe Serajr will have an idea, on my side i will try these steps and report...
highly appreciate that. i will do some more testings on my side too. the point is, although i know it will happen eventually but it happens so unpredictably its not easy to reproduce.
it may sound odd but you're here so i can at least hope it is just a software problem not hardware.
I was never be able to get my xz working with magisk 15 or 16. Always get the sim not recognized problem, maybe yours is magisk related.
snake218 said:
I was never be able to get my xz working with magisk 15 or 16. Always get the sim not recognized problem, maybe yours is magisk related.
Click to expand...
Click to collapse
Hmmm how come? Try this yet? https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
Both ta_poc and drmfix working.
hmmm anyone?
boydzethuong said:
hmmm anyone?
Click to expand...
Click to collapse
My phone is working fine for some days so far. Just cleared cache and dalvik as I mentionned earlier. BTW before doing this I've updated my Magisk from 15.3 to 16 without clearing anything (maybe the problem is related). Will report soon if it's still working or not...
Tonio78r said:
My phone is working fine for some days so far. Just cleared cache and dalvik as I mentionned earlier. BTW before doing this I've updated my Magisk from 15.3 to 16 without clearing anything (maybe the problem is related). Will report soon if it's still working or not...
Click to expand...
Click to collapse
I did that, many times. clearing cache and dalvik seems do the trick. but it actually doesn't. it will work for a few days and the issue will happen again. unfortunately.
by the way I spent some times paying high attention to the screen just to wait for it to happen. It looks like the moment when it happens, SystemUI (or Home Launcher I dont know) is terminated (stopped) then I am brought back to lock screen and at that moment, one of my SIM gone. So to me it looks like a service (or an app) is terminated and isn't restarted properly?
have you tried using stock rom and see if the problem persists?
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Pandemic said:
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Click to expand...
Click to collapse
oh nooo!!!
Pandemic said:
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Click to expand...
Click to collapse
@Pandemic hmmm im not saying i dont believe but how do you explain it runs just fine for days after restart? usually 2 3 days then it happens.
and like i said the moment when it happens it looks like the whole systemui and running apps get force stopped.
lets say im playing a game then it becomes a bit laggy like its running out of memory then everything just closed then im brought back to lock screen and one of the signal indicator on status bar disappears.
do you happen to know any command that can restart the modem / cell / signal service? or any services related? just wanna try to manually execute it see if it fixes it.
also wanna mention again that im using ta_poc method for the drm sh!ts and it does have something like ua_modem_switcher executed. no idea whether it could be related
Hy guys, juste a quick update, my phone was working fine until 2/3 days. I've removed magisk but problem still happening, even clearing cache and dalvik didn't fixed it. My guess is, it could it be app related or crash due to RAM to high (my ram usage average is about 2.5 Go/day)...
Hi guys,
I have the same issue on a Note 4 (sm-n910f)....
I have been flashing roms in a long time and this is the first time it happens to me.
For me, the phone shows some lag, it auto restarts and the signal is lost. I can get it back by clearing delvik and cache, but this will happen at least twice a day.
I flashed stock and the problem goes away, does not happen even once on stock. So this tells me its not a hardware issue (i was so close in thinking its a motherboard issue)...
From reading various threads on this, i get to the conclusion that it is not device specific.
I have flashed half a dozen roms and only stock eliminates the issue. I stayed on stock for 3 days no issue, then reflashed lineage 15.1 and the problem is back. The really weird part is that this happened suddenly, not after a new flash or any operation on the phone.
Anyone figured this out?
---------- Post added at 07:20 PM ---------- Previous post was at 07:14 PM ----------
vasilis_84 said:
Hi guys,
I have the same issue on a Note 4 (sm-n910f)....
I have been flashing roms in a long time and this is the first time it happens to me.
For me, the phone shows some lag, it auto restarts and the signal is lost. I can get it back by clearing delvik and cache, but this will happen at least twice a day.
I flashed stock and the problem goes away, does not happen even once on stock. So this tells me its not a hardware issue (i was so close in thinking its a motherboard issue)...
From reading various threads on this, i get to the conclusion that it is not device specific.
I have flashed half a dozen roms and only stock eliminates the issue. I stayed on stock for 3 days no issue, then reflashed lineage 15.1 and the problem is back. The really weird part is that this happened suddenly, not after a new flash or any operation on the phone.
Anyone figured this out?
Click to expand...
Click to collapse
Adding some additional info from my experience:
- Tried flashing latest BL and CP files (using odin) without any luck
- Tried various 15.1 roms as my device is not officially supported by lineage, again no luck
---------- Post added at 07:32 PM ---------- Previous post was at 07:20 PM ----------
pijes said:
have you tried using stock rom and see if the problem persists?
Click to expand...
Click to collapse
I have and the problem goes away....thing is the device is so much better on OREO
alex.do said:
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
Click to expand...
Click to collapse
similar thing i replied here
plzzz see
https://forum.xda-developers.com/showpost.php?p=77103551&postcount=190