-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4K stability problems #42
Comments
lol, I'm not going to install that. I'm not going to install Cydia on any of my phones, so yeah, I suppose pretty much this is it. Luca was right and the problem is not with the kernel exploit itself, but with the KPP bypass. BUT, I might have something completely different. Not sure whether it will ever work with Cydia, but works just fine for my ssh setup. Still pondering whether I should push it or not... |
Just for the record, I suggest you delete all panics form the device once jailbroken and, when it panics, grab the log. Now that might be helpful. |
Unfortunately the way it panics, either the entire device freezes or instantly reboots and doesn't generate a panic log. Would it be helpful if I provide an app that can cause this issue without substrate (this problem should even be able to be replicated from a sandboxed app)? |
same/similar issue on iPhone 7. a 32 bit app with graphics is most likely to consistently cause the panic. such as adobe photoshop touch (PS Touch). No crash or panic log created. Same instability existed with mach_portal. however the scenario is stable with Yalu B7 on 16 K such as iPhones 6S, 6S plus and SE. no such crash or panics there.. |
4K devices running extra_recipe still exhibit some of the same stability problems yalu102 had.
Seems the kernel patches might need some modifications to fix the issues.
(This same issue happens on mach_portal: kpwn/yalu102#478)
For running the test, downgrading to Anemone 2.1.1-27 is needed: http://files11.thebigboss.org/repofiles/cydia/debs2.0/anemone_2.1.1-27.deb
Seems some memory leak/corruption is occurring that can be easily triggered by Camera/UIGraphics/CoreGraphics usage...
The text was updated successfully, but these errors were encountered: