NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.
One of the things that has been "resolved" is the "dumpstate" situation. Resolved is in quotes because the problem has always been there, SuperSU just only picked up on it in 1.00 and 1.01, and it's now back to being ignored as it was in the past.
For a complete background and explenation on the "dumpstate" issue, see the article on my blog.
Thx for the steady updates and support.
another fine update... keep up great work....
Hey, any idea when we can use root on non-primary user accounts?
No Brasil o estoque não acaba nunca. O preço praticado aqui será o responsável.
Thank you, love and recommend the application to all that love to root their devices :O
It's a fix yes, but disabling dumpstate does make it hard to get good data. Maybe you could patch or fix dumpstate? And what about ROMs like cyanogenmod that might not have the 'naive' version of dumpstate?
It might also be helpful to report the bug to Google and/or CM maintaners so that dumpstate itself can be improved in future versions.
+Zazie Lavender I don't think you really (read well enough to) understand. Dumpstate itself still works, SuperSU just now explicitly ignores a bunch of commands that were previously ignored by both SuperSU and Superuser (and ROMs without root) already anyway. As such, there is no change in state. There is no change in the dumpstate reports, dumpstate is just no longer able to take down your entire phone due to its crappyness.
But wouldn't that still need to be reported as a bug in dumpstate?
Thanks for working on this.
BTW...I have a Nex7 tablet, Andy 4.2.1 if it matters, and since 1.00 I have used the in-app "integrate into /system" function after updating from Play. I also have Pro installed, except if it matters I haven't updated Pro (mainly because it doesn't show up in Play as needing an update, so I'm guessing it's not relevant but just want to cover all bases). Rather unfortunately, everytime I do this I lose all my settings. I have to change the log format, what's logged, reauthorize all apps and make exceptions for notification and logging--everything as if I'd just installed for the 1st time. Is this a "feature?" I wish there were a warning about this in the dialog which pops up asking to reboot after close, or some export/import/back up functions added. It's also ironic that this is one thing that unfortunately +Titanium Track 's Backup won't touch for some oddball reason.
+Zazie Lavender Maybe. Is it truly a bug? From Android's developers perspective, it works as it should. It works with their version of su, which isn't present on production builds. How we modify the device after that with rooting and whatnot, is outside of the scope of their project.
Furthermore, who is actually wrong here ? Android's dumpstate ? Android's su ? SuperSU and Superuser's su ?
Not to mention that it'll make absolutely no difference if they ever fix it or not, as SuperSU will have to keep ignoring it anyway, in case its run on a device with the problematic dumpstate on it.
+Joe Philipps It's not supposed to do that, and I've tried it on my S3 and that doesn't happen. I'll see about trying it on a Nexus7 tomorrow.
I bought the Pro version to say thank you 4 good job!
Thanks updated ROMs to include the update :-)
Bought SuperSu just a couple of days ago. You rock and deserve our support, great work!