[Q] Llama Root Access - Galaxy S III Q&A, Help & Troubleshooting

Hi
Ever since I rooted my GS3 I9300 I have been getting the following error message on a regular basis" "Error-Llama could not get root access in time. Check your SU settings"
Any clues on what I need to do to allow Llama to do its thing in real time?.

---

What root ??

---

Warthog01 said:
Hi
Ever since I rooted my GS3 I9300 I have been getting the following error message on a regular basis" "Error-Llama could not get root access in time. Check your SU settings"
Any clues on what I need to do to allow Llama to do its thing in real time?.
Click to expand...
Click to collapse
Does LIama shown as root-granted in superSU app?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9300 using Tapatalk

---

JJEgan said:
What root ??
Click to expand...
Click to collapse
Sorry--I'm a bit of a root newbie. Don't understand the question--I rooted a few months ago--no problems other than the Llama stumble.

---

LLama Root access
amirTor said:
Does LIama shown as root-granted in superSU app?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
AmirTor
Not specifically (as in your screenshot). How do I add it?
BTW there are numerous instances of Llama in the SU log??

---

Warthog01 said:
AmirTor
Not specifically (as in your screenshot). How do I add it?
BTW there are numerous instances of Llama in the SU log??
Click to expand...
Click to collapse
I think that @JJEgan meant- what tool did you use in order to root your device (CF-autoRoot, etc)
Anyway- is there a running app which uses root permissions other than Llama? If true- try to clean superSU log, reboot and see if Llama gets recognized by SuperSU.
if false- try to check other root apps, and if the issue stays the same- try to reflash root using newest CF-autoRoot (otherwise- reinstall Llama)
Sent from my GT-I9300 using Tapatalk

---

amirTor said:
I think that @JJEgan meant- what tool did you use in order to root your device (CF-autoRoot, etc)
Anyway- is there a running app which uses root permissions other than Llama? If true- try to clean superSU log, reboot and see if Llama gets recognized by SuperSU.
if false- try to check other root apps, and if the issue stays the same- try to reflash root using newest CF-autoRoot (otherwise- reinstall Llama)
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
OK, thanks. I've cleaned the log and rebooted. I think SU recognizes Llama--from the way the error message is worded it appears it doesn't recognize it quickly enough to trigger the action.

---

JJEgan said:
What root ??
Click to expand...
Click to collapse
Ahh, AmirTor set me straight. I'm sure it was CF-autoRoot

---

Warthog01 said:
OK, thanks. I've cleaned the log and rebooted. I think SU recognizes Llama--from the way the error message is worded it appears it doesn't recognize it quickly enough to trigger the action.
Click to expand...
Click to collapse
Look in settings I think you can extend the time it takes for SU to recognize apps gaining root access...I'm using a rom with SU inbuilt and you can change the length of time it takes to detect not sure if the app version as that feature?

---

tallman43 said:
Look in settings I think you can extend the time it takes for SU to recognize apps gaining root access...I'm using a rom with SU inbuilt and you can change the length of time it takes to detect not sure if the app version as that feature?
Click to expand...
Click to collapse
Thanks, Tallman
There's nothing that specifically refers to extending recognition times, but there are a couple that might apply: Re-authentication, enable during boot, Trust system user, etc--I'll give 'em a try.

---

Was this issue ever resolved? I'm getting the same problem.

---

LLama Root access
No, never resolved and I'm still getting the message.

---

Warthog01 said:
No, never resolved and I'm still getting the message.
Click to expand...
Click to collapse
I ran Llama fine on 4.2.2 stock for a year or so. When I switched to 4.4.2 WanamLite (stock less Knox) I started getting the message. I got SuperSU pro to enable logging.
My morning action turns airplane mode off, turns sync on, turns wifi on, then runs a bunch of things like facebook, email, etc to sync. I get the exclamation mark and the message at the top of the thread when this runs, or when the similar evening action runs. I'm getting the following log entries when it goes out of airplane mode (in approx these colors). Nothing in supersu says anything about delays.
1.
settings put global airplane_mode_on 0
exit
Warning: App_process has text relocations. This is wasting memory and is a security risk. Please fix.
2.
am broadcast
a android.intent.action.AIRPLANE_MODE -e llama.sender llama -e state false
exit
Warning: App_process has text relocations. This is wasting memory and is a security risk. Please fix.
Boradcasting: Intent (etc).
Broadcast completed: result=0

---

Ok, I have a solution or workaround, but not a full explanation.
It seems permissions and such have changed between 4.2.2 and 4.4.2 and Llama isn't compatible, or maybe it's just not possible. The trick is to use the secure settings app, and enable the System+ Module inside it. I think I also made Secure Settings a device admin, just in case, but unsure if that's required. Then go to the compatible apps tab and click llama help for instructions.
Basically, in Llama, instead of using the built in airplane mode commands you add an action "locale plugin", then choose "secure settings", "root actions", then "airplane mode". That lets you turn it on, off, or toggle.
If you purchase secure settings pro (about $1.50, in-app purchase via google play) you get access to a shutdown and reboot command. I can't find any other way to do this - even via a shell where you can usually do it the shutdown/reboot commands don't seem to be there.
Sorted!

---

Same problem here with a Moto X with root and it shows up as having root access in SuperSu.

---

atomb said:
Same problem here with a Moto X with root and it shows up as having root access in SuperSu.
Click to expand...
Click to collapse
Did you read the solution, one post up from yours on page 2?

---

commandonz said:
Ok, I have a solution or workaround, but not a full explanation.
It seems permissions and such have changed between 4.2.2 and 4.4.2 and Llama isn't compatible, or maybe it's just not possible. The trick is to use the secure settings app, and enable the System+ Module inside it. I think I also made Secure Settings a device admin, just in case, but unsure if that's required. Then go to the compatible apps tab and click llama help for instructions.
Basically, in Llama, instead of using the built in airplane mode commands you add an action "locale plugin", then choose "secure settings", "root actions", then "airplane mode". That lets you turn it on, off, or toggle.
If you purchase secure settings pro (about $1.50, in-app purchase via google play) you get access to a shutdown and reboot command. I can't find any other way to do this - even via a shell where you can usually do it the shutdown/reboot commands don't seem to be there.
Sorted!
Click to expand...
Click to collapse
Thanks for this solution. Works perfect !
$1.50 is really cheap for that nice app

---

burnout said:
Thanks for this solution. Works perfect !
Click to expand...
Click to collapse
Hit thanks if it helped