Develop Bugs

[Q] Freeze then reboot

So here is my problem, from time to time the tablet just freezes, only the notification bar is responsive and as soon as I pull it down, It becomes too late and the only wawy I can use the tablet again is to force reboot by holding the power button.
My GT-N5110 being rooted and the Android version is 4.1.2 stock (^^).
If you know where the problem comes from feel free helping me getting ride of it

I've gotten this occasionally. I went through the device the other night and uninstalled a lot of stuff that was in the "maybe works/maybe not, I never use" category, and I've been getting much less of this behavior since.
After installing the multiwindow app (which I like) I found that the camera app would make my device lock up and require a reboot.
Turning off the multiwindow feature (not uninstalling the app) gave me the ability to use the camera again.
Sorry I can't remember what-all I uninstalled.

It happened to me when i rooted with superuser, i unrooted and then re-rooted using SuperSU (same root app, only chose supersu). Never happened to me since.

thank you all,
i'll try uninstalling and unrooting then rerooting it using superSu.
Just for the update : the manipulations above seem to have solved the issue. Thank you again for your help.

[Q] Either enable SuperSU or turn off the damn "blocked" notification

So, I just got am SGH-T747 S3 yesterday, and was poking around in all the new settings, when I came across "Software Update". I wasn't sure if this meant firmware or what, but I went ahead and let it download what turned out to be 4.3 (whereas I was on 4.1.2 or thereabouts).
Then I tried to root it today, with a couple of methods but most recently CF-Autoroot. I haven't flashed any ROMs or done anything else beyond this yet, I just wanted my Ad Blocker. And then I start getting this business about "SuperSU has stopped", and the "An application attempted to access system" nonsense. So of course I Googled it, and came across a number of different articles/posts about this problem, including some on XDA, none of which seem to offer any solutions.
I'm not really sure at this point how or even if this problem can be fixed or not. I've read that you can't downgrade to a lesser ROM version (?). Also, I'm not sure if flashing CyanogenMod (which is what I eventually want to do) would solve the problem, and I'm not about to try it for fear of what other surprises I might encounter.
But if for some reason I can't have root, I'd at least like to be rid of this incessant notification that the program has been blocked. TIA.

Well, if you want adblock, there is a VPN called Spotflux that doesn't slow your speeds down, has adblock, and is free.
About the root issue....I wouldn't know as my i747 is in a coma of the QHSUSB - DLOAD disease.
You might wanna try the cyanogenmod installer in google play to see if your device is supported ( proceed with caution)

99ytrewq9111 said:
Well, if you want adblock, there is a VPN called Spotflux that doesn't slow your speeds down, has adblock, and is free.
Click to expand...
Click to collapse
Thanks, that is an interesting alternative in the interim. As with everything ad-related, it doesn't work everywhere (I guess they are pulling ads from custom servers or whatever), but it does seem to work with some programs. I've had the same issue with AdBlocker too.

voxluna said:
So, I just got am SGH-T747 S3 yesterday, and was poking around in all the new settings, when I came across "Software Update". I wasn't sure if this meant firmware or what, but I went ahead and let it download what turned out to be 4.3 (whereas I was on 4.1.2 or thereabouts).
Then I tried to root it today, with a couple of methods but most recently CF-Autoroot. I haven't flashed any ROMs or done anything else beyond this yet, I just wanted my Ad Blocker. And then I start getting this business about "SuperSU has stopped", and the "An application attempted to access system" nonsense. So of course I Googled it, and came across a number of different articles/posts about this problem, including some on XDA, none of which seem to offer any solutions.
I'm not really sure at this point how or even if this problem can be fixed or not. I've read that you can't downgrade to a lesser ROM version (?). Also, I'm not sure if flashing CyanogenMod (which is what I eventually want to do) would solve the problem, and I'm not about to try it for fear of what other surprises I might encounter.
But if for some reason I can't have root, I'd at least like to be rid of this incessant notification that the program has been blocked. TIA.
Click to expand...
Click to collapse
if i remember correctly, in settings>security you can disable the notification of supersu being blocked and now you can access root. happened to me when i first updated

I used cf autoroot and then installed supersu from the play store. When I opened supersu it asked me if I wanted to disable knox and I pressed yes. Then I installed titanium backup and froze knox.
Sent from my SGH-I747M using Tapatalk

Try this http://forum.xda-developers.com/showthread.php?t=2538991

Cyanogenmod Installer

Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.

Capa1970 said:
Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Click to expand...
Click to collapse
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.

WearySky said:
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
Click to expand...
Click to collapse
I am not rooted.

Capa1970 said:
I am not rooted.
Click to expand...
Click to collapse
I wasn't able to find any way to get around Knox without rooting, but I may not have looked hard enough.
If you're willing to root first, CF Auto Root was super easy to do:
http://forum.xda-developers.com/showthread.php?t=1963790

Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?

Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?

Capa1970 said:
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Click to expand...
Click to collapse
That *is* a Knox message, for sure.

So it looks like the Cyanogenmod team were not able to circumvent Knox for their CM installer. It's probably just a matter of time. Here is the full Knox notification:
"An application attempted to access system on your device without authorization. This attempt has been blocked. Updating your security policy may solve this problem. Deleting applications obtained from unauthorized sources may improve security."
There are three options at the bottom of the screen: Cancel, Update, and View Apps.

Update: I was able two days ago to use the Cyanogenmod Installer and I am now running CM!! First time for me to ever root and flash a Rom (I was an iPhone guy).
The phone is faster and smoother. I never liked the Touchwiz lag and most of the Touchwiz features worked inconsistently. The only thing that I miss is the camera. I have not found any bugs yet and so am very happy thus far.

Is Magisk/Root causing random reboots for anyone?

I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.

Looks like Magisk 14.5 might have something to do with it.
Starting on page 452 there are a few posts from there on about it.
Symptoms are a random reboot with a soft boot loop of the SystemUI. The only way to correct it is to hard reboot the device.
I can usually go a few days worth of up time between the bug reappearing.

I was the exact same way on 8.0. Every couple of days, it would start randomly rebooting and/or apps would start crashing. The only fix was to hold the power button until it rebooted. Rebooting by just pressing the power button and selecting reboot would always hang.
I was hoping 8.1 would fix it, but it's quite a bit worse. It's done it at least 4 times so far today. Same symptoms. Apps will start crashing (sometimes the foreground app, sometimes background ones), or the phone will just soft reboot, or both. Sometimes it's while I'm using it, sometimes I'm not using it at the time. No rhyme or reason, that I can tell..
I had one app that crashed immediately every time I tried to start it until I uninstalled it and restored it from backup (with data). That was weird.
If this keeps up, I may have to roll back to 8.0.

theycallmerayj said:
I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.
Click to expand...
Click to collapse
There is a larger thread on this HERE. There is no definitive smoking gun yet but certain root apps seem to be causing it. One way to rule out Magisk would be to simply uninstall the app temporarily (longpress>>App Info>>Uninstall) then fastboot flash the original boot.img and dtbo.img. Run this way long enough to know for sure whether being rooted is causing the issue. There are tons of people rooted who do NOT have this issue, so it is more than likely one of your root apps/themes is causing it.

Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.

theycallmerayj said:
Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.
Click to expand...
Click to collapse
Have you tried Adaway? I use very few root apps, but that is the first one I add every time. I've not had any reboots at all and it is very effective. Because you only use the one root app, you may find the culprit was UH, and not Magisk.

I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots

theycallmerayj said:
I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots
Click to expand...
Click to collapse
You can use different host files you don't have to use the ones that come with AdAway. Try Steven blacks out

I'm having this same issue with Magisk. I experienced it with an older Magisk on 8.0 as well.
I'm thinking about just getting rid of Magisk altogether. However, I used ES File Explorer to edit my build.prop to add the command to disable the nav bar. I'm nervous that uninstalling Magisk will cause the "your system is corrupt" message and a bootloop. However, I also have Flash Kernel installed. I wonder if the custom kernel will allow me to use the phone with the modified build.prop and without Magisk...

Question [Root] Device crashing & rebooting after one minute of usage

I'm using a Pixel 6 Pro rooted and after 1 minute of using the device the device completely freezes and reboots. This happened one day after I rooted my phone and I rebooted my device and it completely stopped working. The logs provided in Magisk don't seem to be useful nor point to the main issue. Safe mode doesn't have this issue, but I'm looking to see how to fix this issue. I'm running TQ1A.230105.002 build. I can try and install a module to help diagnose the issue if it's useful.
Magisk modules installed: Universal Safetynet
Zygisk: Enabled
Rooted apps: Greenify, GoogleDialerMod, Shizuku, Storage Isolation, BBS

fillwithjoy1 said:
I'm using a Pixel 6 Pro rooted and after 1 minute of using the device the device completely freezes and reboots. This happened one day after I rooted my phone and I rebooted my device and it completely stopped working. The logs provided in Magisk don't seem to be useful nor point to the main issue. Safe mode doesn't have this issue, but I'm looking to see how to fix this issue. I'm running TQ1A.230105.002 build. I can try and install a module to help diagnose the issue if it's useful
Click to expand...
Click to collapse
Do you have any Magisk mods installed? If so, one of them may be causing it given you don't have any problems in safe mode.

Lughnasadh said:
Do you have any Magisk mods installed? If so, one of them may be causing it given you don't have any problems in safe mode.
Click to expand...
Click to collapse
My bad, I'll edit the post right now. The freezing does occur even after denying all of them permissions

If it is a module just type in adb magisk –remove-modules
there's also a magisk module that disables misbehaving modules at boot to protect against bootloop it's called magisk bootloop protector

fillwithjoy1 said:
My bad, I'll edit the post right now. The freezing does occur even after denying all of them permissions
Click to expand...
Click to collapse
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Also, if you booted into safe mode and rebooted your modules should be disabled. Does the problem persist with those mods disabled?

Lughnasadh said:
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Also, if you booted into safe mode and rebooted your modules should be disabled. Does the problem persist with those mods disabled?
Click to expand...
Click to collapse
No safe mode is completely fine, but I will look into uninstalling Greenify and see if the problem is fixed.

Thank you! Greenify is the issue!
Lughnasadh said:
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Click to expand...
Click to collapse
I'm not sure why Greenify has been so problematic recently, it even crashes on non-root devices. Maybe it's out of date for such a long time?

fillwithjoy1 said:
Thank you! Greenify is the issue!
I'm not sure why Greenify has been so problematic recently, it even crashes on non-root devices. Maybe it's out of date for such a long time?
Click to expand...
Click to collapse
Excellent! Glad you got it straightened out.
I find Greenify and similar apps aren't really needed these days.