Help! Reboots/Restarts across multiple ROMs and kernels - T-Mobile Samsung Galaxy Note5

Hi guys,
I'm experiencing reboots when I push my phone hard. I typically have reboots when I'm using Chrome to view webpages in desktop mode or when using GPS (Google Maps, Waze). I've used two different roms and a few different kernels, but seem to be experiencing the same reboots across all platforms (and various rom/kernel combinations). Any help would be greatly appreciated!
Device: T-Mobile Samsung Note 5 64GB
Recovery: Philz Touch
ROMs used (COJ5):
Hyperdrive RLS2
Hyperdrive RLS3
fOrEvErLoCo's BrEaKdOwN R3.0.1
Kernels used:
Stock Hyperdrive RLS2 Kernel
Stock Hyperdrive RLS3 Kernel
Stock fOrEvErLoCo's BrEaKdOwN R3.0.1 Kernel
arter97 N920TW8 9.4 Kernel
arter97 N920TW8 X Kernel
SkyHigh N920T TW LL Kernel
Could this have anything to do with SuperSU?

still random rebooting.
and apparently we currently can't downgrade from COJ5? Double
Any help would be very, very appreciated. Thanks in advance!

Have you odin'd to stock + factory reset?

10-K said:
Have you odin'd to stock + factory reset?
Click to expand...
Click to collapse
As of right now I'm on jovy23's COJ5 Deodexed Stock Rooted Rom, installed after a fresh wipe of cache, dalvik, data, system, etc.
I seem to have found what was causing the reboots. I think it's giving Lastpass accessibility rights.
All throughout the initial installing of apps, the phone never randomly rebooted. Shortly after I got all my apps up and running, the reboots would begin to happen (sometimes twice in 15 minutes.)
Even on this fresh install of the deodexed stock rom, I had one random reboot. Since turning off Lastpass in Settings > Accessibility, I have experienced zero random reboots.
Did anyone else experience this? I'm wondering if it's specifically Lastpass that's giving the phone issues or Accessibility as a whole.
Will try to see if turning off Lastpass on the other kernels and ROMs helps next week and will post an update.
Thanks everyone!

Related

[Q] Phone stuttering after flashing kernel.

I couldnt post in the kernel thread because I don't have enough posts yet..
I installed clean Rom a month or so ago and have been updating to the new versions ever
Since, everything had been running perfectly on the stock kernel. I got the itch to try a new kernel and
decided to try out the elemental kernel (later tried the beast mode as well). Ever since I flashed the new
kernels in recovery my phone keeps stuttering and the screen jumps a bit every couple of seconds, also the
browser keeps reloading when I am on google.com.
I have tried flashing both kernels with different options as well as clearing cache before and after flashing, plus
fixing permissions but the problem continues. I also did a factory reset and reinstalled clean Rom and both kernels.
Has anyone had this happen to them before and know of a solution?
Thanks in advance.
Are you overclocked? Not every phone can handle oc'ing.
No. At first I tried the kernels with the oc to 1.7 option, but then I tried both kernels with no oc, no gpu oc, no sweep to wake, and no
Under volt but the screen kept flickering and the apps kept having hiccups.
I flashed the stock kernel from viperxl and now the phone is back to normal.
I am on 2.20 with the hboot 1.14 by the way.

Having trouble with different kernals, quick question.

So i rooted my GS3 and ran the CleanROM6 R2 just fine and the new synergy just fine. However i can only run the new JellyBeans13 with the stock kernel, the other two kernels freeze at the Samsung Galaxy SIII screen every time. I am running CWM6023. I was wondering if that needed to be updated and if so how to update the CWM, also if anyone else has had that issue with certain Kernels. I want the Ktweaker that's why it bothers me right now i have the stock Jellybeans 13 rom and kernel. I am just confused it is the only rom that has done this to me.
Some kernels required a dalvik cache wipe in order for it to work properly.
jmxc23 said:
Some kernels required a dalvik cache wipe in order for it to work properly.
Click to expand...
Click to collapse
I do a Dalvik wipe everytime, i was just wondering if i needed a newer version of CWM.
Is your boot loader unlocked??
Sent from a Shaftamle Galaxy S3
Hit the "Thanks" button if I helped you!!
I know the kernels have been locking phones that are on latest updates. I believe they just found out what was causing the locks, so expect to see updated kernels over the next few days. You should run the stock kernel (supplied with the rom) until the updates are rolled out.
Sent from my PACmaned SCH-I535
JB13 has an issue if you use a different kernel that won't show a boot animation. It may not be freezing.

[Q] Random visual flashes/errors while using fresh PA

Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck
Turn off the corresponding setting in the developer options.
Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.
Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel

[Q] Help - Touchwiz vs AOSP on S3

I dont know if its my phone or what but I haven't had any luck with AOSP ROMS on this phone. It seems like there's always some sort of bug that just kills it. I flashed a CM10.2 rom that felt like speed of lightning but was bugging out. I tried ecilpse and some others but all were to buggy for me. I recently tried to flash liquid cause I wanted to run something else other than touchwiz but it ruined my phone and now I cant flash custom ROMS(i have a help thread up..feel free).. Anyone else having bad luck on these AOSP ROMS
Not what you want to hear, but I'm having no issues with flashing new ROMs. I'm only using LiquidSmooth and waiting/hoping for a 'complete' 4.3 version, but again, no problems with flashing to a new ROM. I have been running LS2.9 (4.2.2) for several weeks and on Sunday flashed up to LS2.10 (4.3) but went back to 2.9 because when I mirror my phone on my AppRadio3, it doesn't auto-rotate my screen to landscape, so I have a portrait orientation of my phone on the radio display, which makes it so small as to be unusable.
I don't recall what method I used to root my phone, but I'm using TWRP 2.6.3 to perform a) a clean wipe every time (Factory Reset + System), then b) install the new ROM, and c) a final reboot back in to recovery and flash the latest gapps image. Does it take a little longer to follow this process? Sure, but it's a reliable process that means I don't have issues afterwards to mess with, so the extra time spent on the front end is worth it to me.
I've had moderate success with the AOSP ROMS. Each one seems to have it's own small bugs, but the AOSP ROMs that I've tried didn't have anything that ruined functionality. Been running Dirty Unicorn ROM for the past couple days and it is really solid. Haven't noticed any issues at all with it yet.
It's got to be your downloads or install process. Do you check MD5? If no then start. Remember just wipe data for each install. Updater-script in ROM zip wipes system for you. Cache resides in data. Do NOT restore system data using TiBu. Other than that I don't know what else to tell ya bud :/
Sent from my SCH-I535 using Tapatalk
Haven;t had any trouble with AOSP flashes, but many of the ROMs or maybe most have some bugs. All the so called AOSP ROMs are built off the same base, CM10. None of them support all the hardware and software features that Tocuhwiz supports. I find the custom TW ROMs far superior in features and as good or better in speed as well.
Make sure you are flashing a compatible Kernel when you switch between CM based ROMs and TW based

Is there a stable ROM right now that doesn't random reboot???

I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Update:
Tried Elemental X, the phone reboots randomly now... And also just googled problem with Nexus 5... it seems like 5.0 and 5.0.1 have TONS of random reboot issues...? Goddamn it Google...
Do any of you have a stable ROM (stock or custom) that doesn't have random reboot issues?
Elementalx
codenamezero said:
I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Click to expand...
Click to collapse
i use franco kernel 70 with stock rooted 5.0.1 with no issues. but i don't see any differences between stock and franco. neither performance nor battery life.
This Nexus 5 is just getting worst... it random reboots now.
codenamezero said:
This Nexus 5 is just getting worst... it random reboots now.
Click to expand...
Click to collapse
Sorry to hear that. Could it possibly be a hardware issue since you say it's happening to you across all software? Corrupted storage media could cause random reboots such as that.
I'm not seeing any myself, though I do reboot the phone about once a week just as a precautionary measure with L's RAM management.
Was having this issue with Stock and Custom ROMS ended up going back to KITKAT and no problems. Hopefully they will have this fixed with 5.1 that will be released soon.
Stock one is allways the best choise. You must be aware, that the stock one is build by a lot of good developers and custom ones are made by individual enthusiasts. There is nothing wrong with that, but the pure logic here speaks by itself.
Used a lot of different roms
ordered my nexus on release day, used quite a few different roms and i've never had a random reboot.

Categories

Resources