MotoTriumphant
Android Enthusiast
i flashed this rom and i flashed the 4.3 kernel as well and i lost root access is there a reason for that what did i do wrong
Try fixing permissions in recovery to fix root problem
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
i flashed this rom and i flashed the 4.3 kernel as well and i lost root access is there a reason for that what did i do wrong
OP Updated to beta 3.
How do you access the full Super User program? It's not listed in the main settings window like the other roms. I tried searching for the apk file in system\app but didn't find it there either. I just want to always allow programs.
Just wondering does this rom have per app dpi?
Does this have Halo?
Uh oh. Maybe I spoke too soon. Does anyone have an issue with the volume rocker not working after a while of using this rom? I'm not sure what is causing it but it happened to me twice so far. Only a reboot fixes it.
Uh oh. Maybe I spoke too soon. Does anyone have an issue with the volume rocker not working after a while of using this rom? I'm not sure what is causing it but it happened to me twice so far. Only a reboot fixes it.
This is one of the 4.3 bugs that seem to run across the various builds. After a while you might have all your apps close and the launcher restart. If that happens, reboot and you're good to go.
Yes, that happened to me in Paranoid, Illusion and now Slim Bean. I keep seeing all my constant app icons in the status go crazy with the restarts. I have to power off my phone and back on to get it stable again. It only happened once in Slim Bean though. It was happening within 1/2 hour with Paranoid rom.
I'm not able to update google search from the play store. It says that the package file was not signed correctly. Do I have to wait for a side load package?
Can you guys take a quick video and see if the gain on the mic is raised all the way?
When I play back my videos, it sounds distorted. I may have to go back to 4.2.2 until these issues get ironed out.