so as you may noticed catlog /logcat/ alogcat and such are not working properly or at all.
that is because google added a new permission request from apps which they don't usually request.
but alas, there is fix, if you're working with one of the latest versions of JB (quarx or epsylon3 it doesn't matter) you can fix it by simply by following the next steps:
1. make sure your'e phone is rooted and has superuser or any other permission manager app (superuser zip flashable can be downloaded here)
2. enter the app drawer and enter the "terminal emulator"
3. gain root permissions by typing :
$su
wait for the notification about permission allow/deny, and allow it.
4. now you give permission to the program you want by writing the following line:
pm grant [programs name] android.permission.READ_LOGS
(the upper case /lower case is important)
I.E for catlog you should type:
Code:
su
pm grant com.nolanlawson.logcat android.permission.READ_LOGS
now your logging app should work fine, enjoy!
Thanks! ill try it, i need logcat a lot
Great It works for me im on JB Quarx 22Aug12
ksrao_iete said:
Great It works for me im on JB Quarx 22Aug12
Click to expand...
Click to collapse
Good. if i helped please press the thank you button.
also moderators if you can see this, you'd might want to add this to the wiki or something.
Works on CM10 for S3.
Hrm.
Sent from my SCH-I535 using Tapatalk 2
It worked! Thanks a lot. For alogcat it's
Code:
su
pm grant org.jtb.alogcat android.permission.READ_LOGS
Here's a way to make all log reader apps work instead of going one by one:
su: "chmod 04755 /system/bin/logcat"
or open root explorer, navigate /system/bin/logcat, long press logcat and select "permissions", then check the box "Set UID".
Both ways require a reboot after!
Hope this helps, thanks to ChainsDD for this!
Working on LC's Ice Cold Jelly on the One X.
Thanks so much for this
Sent from my HTC One X using xda premium
Thanks, really thanks.
I use aLogcat and the code that I used was
Code:
pm grant org.jtb.alogcat android.permission.READ_LOGS
You can find your logger program accessing with any root explorer the folder "data>data" and look for the name of the folder that contains the name of your app within. I looked for it because I'm not using the same app that you used, so I opened the "Root Explorer>Search" and searched for "logcat". So I found the folder "Data>data" and tried using the name of the folder that was "org.jtb.alogcat" and worked.
Thanks very much, nice job.
alienhead13 said:
It worked! Thanks a lot. For alogcat it's
Code:
su
pm grant org.jtb.alogcat android.permission.READ_LOGS
Click to expand...
Click to collapse
For the donate version it's:
Code:
pm grant org.jtb.alogcat.donate android.permission.READ_LOGS
shag_on_e said:
Here's a way to make all log reader apps work instead of going one by one:
su: "chmod 04755 /system/bin/logcat"
or open root explorer, navigate /system/bin/logcat, long press logcat and select "permissions", then check the box "Set UID".
Both ways require a reboot after!
Hope this helps, thanks to ChainsDD for this!
Click to expand...
Click to collapse
Thanks for the alternative way to do it. Though considering the information the logs contain, I would rather grant a specific app than have everyone see it.
I'm on Sky-JB T11.4 and while I can grant the permissions successfully, there is no content in either alogcat or catlog, even after a reboot. Catlog just shows a spinning busy circle forever, and alogcat just shows a blank screen.
Tried running an app I know crashes (WMUR 9 News app), but the same behavior continues...
Any ideas where to look to resolve this?
NoSpamDan said:
I'm on Sky-JB T11.4 and while I can grant the permissions successfully, there is no content in either alogcat or catlog, even after a reboot. Catlog just shows a spinning busy circle forever, and alogcat just shows a blank screen.
Tried running an app I know crashes (WMUR 9 News app), but the same behavior continues...
Any ideas where to look to resolve this?
Click to expand...
Click to collapse
Check your ROM's kernel doesn't disable logging. Semaphore for my SGS does this but there's an app by the dev to renable it.
Thanks
..thank you, I was having a hard time getting logcat, you really helped me a lot!
One of the latest versions of JB
rtk217 said:
so as you may noticed catlog /logcat/ alogcat and such are not working properly or at all.
that is because google added a new permission request from apps which they don't usually request.
but alas, there is fix, if you're working with one of the latest versions of JB (quarx or epsylon3 it doesn't matter) you can fix it by simply by following the next steps:
Not clear : what do you mean with "latest versions". I have JB 4.1.2, quarx or epsylon doesn't mean anything comprehensible for an ordinary android smartphone user like me..
Click to expand...
Click to collapse
Related
Im using the Root Explorer v2.10.2(which is the latest) to delete some unwanted system apks in system/apk folder, and im pretty sure i have already deleted those apks, but when i go into Settings->applications->manage applications, i still can find those deleted apks. Altho they are like 0 bite in memory, but still looks very annoying to me. Is there any way to get rid of those things in 'manage applications'? I have tried to search keywords in RootExplorer, and deleted the apk folders under data/data, and reboot my phone, and they are still there..
Also, if i click on any of those apks, "settings" will FC.
tzf123 said:
Im using the Root Explorer v2.10.2(which is the latest) to delete some unwanted system apks in system/apk folder, and im pretty sure i have already deleted those apks, but when i go into Settings->applications->manage applications, i still can find those deleted apks. Altho they are like 0 bite in memory, but still looks very annoying to me. Is there any way to get rid of those things in 'manage applications'? I have tried to search keywords in RootExplorer, and deleted the apk folders under data/data, and reboot my phone, and they are still there..
Also, if i click on any of those apks, "settings" will FC.
Click to expand...
Click to collapse
Did you try running fix_permissions?
Binary100100 said:
Did you try running fix_permissions?
Click to expand...
Click to collapse
hmm.. what is fix_permissions?
i searched on google and it says:
From a running ROM
To execute the fix_permissions script on your phone:
Open the "Terminal" app from the application drawer.
Type
su
fix_permissions
when i type fix_permissions in terminal, it indicates fix_permissions not found, i also tried fix_permissions.sh, still not found
tzf123 said:
hmm.. what is fix_permissions?
i searched on google and it says:
From a running ROM
To execute the fix_permissions script on your phone:
Open the "Terminal" app from the application drawer.
Type
su
fix_permissions
when i type fix_permissions in terminal, it indicates fix_permissions not found, i also tried fix_permissions.sh, still not found
Click to expand...
Click to collapse
what rom and recovery are you using?
Binary100100 said:
what rom and recovery are you using?
Click to expand...
Click to collapse
SMOKI 0.6.3, RA-hero-v1.6.2
it seems like the fix_permissions command can be used in CM ROMS..
tzf123 said:
SMOKI 0.6.3, RA-hero-v1.6.2
it seems like the fix_permissions command can be used in CM ROMS..
Click to expand...
Click to collapse
Try running fix_permissions from recovery.
its not working... those apks still stay in 'manage applications'.. altho recovery said its successful
Binary100100 said:
Try running fix_permissions from recovery.
Click to expand...
Click to collapse
LOL, problem solved, by editing the packages.xml under data/system, somehow the apk details are recorded in that file, so i just delete the corresponding codes and reboot my phone, walllllaaaaaaaaaa
AND, thanks a lot for your guide, LOL
tzf123 said:
LOL, problem solved, by editing the packages.xml under data/system, somehow the apk details are recorded in that file, so i just delete the corresponding codes and reboot my phone, walllllaaaaaaaaaa
AND, thanks a lot for your guide, LOL
Click to expand...
Click to collapse
Glad that you got it solved.
Also I hope that you don't mind by I edited your title because your problem wasn't specifically related to the Root Explorer app. This problem would occur if you had used any other means of removing the system app. By editing the title it'll make it easier for those that need assistance with a similar issue post their problems and find solutions. Adding [Solved] is effective to let them know that a resolution is available within the thread.
And it's not my guide, it's a reference for others that can't find the answer with the apparently evasive search feature.
Hi all!
Recently I flashed tytung rom:
[2.Jun.2012] NexusHD2-ICS-4.0.4-CM9-HWA V2.2 (Kernel: tytung_HWA_r3)
It's a good one, no random resets since flashing, it's quite stable.
2 issues i encountered:
1. no way to remove google search from main screen
2. FuelLog Pro v2.2.1 doesn't work, crush right away
Did anyone experience it and can help solving it up?
Thanks!
ehud83 said:
Hi all!
Recently I flashed tytung rom:
[2.Jun.2012] NexusHD2-ICS-4.0.4-CM9-HWA V2.2 (Kernel: tytung_HWA_r3)
It's a good one, no random resets since flashing, it's quite stable.
2 issues i encountered:
1. no way to remove google search from main screen
2. FuelLog Pro v2.2.1 doesn't work, crush right away
Did anyone experience it and can help solving it up?
Thanks!
Click to expand...
Click to collapse
The Google search bar can be removed in the Trebuchet settings (there's a flashable zip in the thread which enables them) and try moving that app to the internal storage (it's a weak suggestion but on occasion it works).
Thanks!
Number 1 solved.
Now I need help with number 2..
ehud83 said:
Thanks!
Number 1 solved.
Now I need help with number 2..
Click to expand...
Click to collapse
Try clearing the data for that app and then rebooting to recovery and under advanced menu option select "Fix Permissions" solves a lot of my force closes. Other than that you may need to post a logcat and/or traces.txt file
elesbb said:
Try clearing the data for that app and then rebooting to recovery and under advanced menu option select "Fix Permissions" solves a lot of my force closes. Other than that you may need to post a logcat and/or traces.txt file
Click to expand...
Click to collapse
I tried what you suggested - no success.
I'll appreciate if you tell me where can I find logcat and traces.txt
Thanks!
ehud83 said:
I tried what you suggested - no success.
I'll appreciate if you tell me where can I find logcat and traces.txt
Thanks!
Click to expand...
Click to collapse
Well logcat is an android debug tool found in ADB or a terminal emulator. Traces.txt is located
Code:
/data/anr/traces.txt
To make a logcat follow the steps below
Code:
1. Open ADB or a terminal emulator inside your phone.
PRESS ENTER after each command or after each segment of ' '
2. Type 'su'
3. followed by 'logcat -c'
4. Then go open your program that always force closes
5. Go back to your ADB or terminal emulator
6. Then type 'logcat -d > /mnt/sdcard/logcat.txt'
7. Then plug your phone into your computer and enable USB mass storage and find the file on your SD card labled "logcat.txt"
8. And post it for me to look at :)
That should help in the diagnoses
elesbb said:
Well logcat is an android debug tool found in ADB or a terminal emulator. Traces.txt is located
Code:
/data/anr/traces.txt
To make a logcat follow the steps below
Code:
1. Open ADB or a terminal emulator inside your phone.
PRESS ENTER after each command or after each segment of ' '
2. Type 'su'
3. followed by 'logcat -c'
4. Then go open your program that always force closes
5. Go back to your ADB or terminal emulator
6. Then type 'logcat -d > /mnt/sdcard/logcat.txt'
7. Then plug your phone into your computer and enable USB mass storage and find the file on your SD card labled "logcat.txt"
8. And post it for me to look at :)
That should help in the diagnoses
Click to expand...
Click to collapse
OK! I'll try to do it, but it would take a few days due to work and semester exams.
I'll post it as soon as possible.
Thank you!
ehud83 said:
OK! I'll try to do it, but it would take a few days due to work and semester exams.
I'll post it as soon as possible.
Thank you!
Click to expand...
Click to collapse
Yep not a problem! Traces.txt is auto generated by the program so thats just a matter of extracting and posting logcat is a little more complicated.
Here is logcat.txt file
Thanks a lot!
ehud83 said:
Here is logcat.txt file
Thanks a lot!
Click to expand...
Click to collapse
good job creating that logcat not much garbage was inlcuded thank you so much!!!
But after looking at it, its a developer error on terms of the person who created it, not your HD2 or anything on your part.
Code:
W/dalvikvm(12012): Verifier rejected class Lt7iscAj4/UDOaYxz;
and
Code:
W/dalvikvm(12012): threadid=1: thread exiting with uncaught exception (group=0x40a571f8)
E/AndroidRuntime(12012): FATAL EXCEPTION: main
E/AndroidRuntime(12012): java.lang.VerifyError: t7iscAj4/UDOaYxz
E/AndroidRuntime(12012): at ch.simonmorgenthaler.fuellog.FuelLog.onCreate(FuelLog.java:41)
E/AndroidRuntime(12012): at android.app.Activity.performCreate(Activity.java:4465)
E/AndroidRuntime(12012): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1049)
E/AndroidRuntime(12012): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2033)
E/AndroidRuntime(12012): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2104)
E/AndroidRuntime(12012): at android.app.ActivityThread.access$600(ActivityThread.java:132)
E/AndroidRuntime(12012): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1157)
E/AndroidRuntime(12012): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(12012): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(12012): at android.app.ActivityThread.main(ActivityThread.java:4575)
E/AndroidRuntime(12012): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(12012): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(12012): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
E/AndroidRuntime(12012): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
E/AndroidRuntime(12012): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(10213): Force finishing activity ch.simonmorgenthaler.fuellog/.FuelLog
are all common errors developers get when something doesnt work. (Ive seen lots of these in my programs xD) It almost seems like its due to it being androd 4.0 from what i read in the logcat. email the developer and give them the logcat, and the traces.txt (if there was one) they should be able to fix it. Also firstly check for an updated version.
I tried to access traces file, but my Data directory is empty..
ehud83 said:
I tried to access traces file, but my Data directory is empty..
Click to expand...
Click to collapse
Are you using data2ext? Plus what file browser did you use?
Sent from my GT-I9100 using Tapatalk
elesbb said:
Are you using data2ext? Plus what file browser did you use?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I'm not using data2ext.
I'm using File Manager comes with rom
ehud83 said:
I'm not using data2ext.
I'm using File Manager comes with rom
Click to expand...
Click to collapse
And your entire data directory is empty? -scratches head- that's kind of impossible xP
Sent from my GT-I9100 using Tapatalk
elesbb said:
And your entire data directory is empty? -scratches head- that's kind of impossible xP
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I know. I'll try to upload a screenshot, to prove it.. My \Data was always empty, don't know why.
By the why: I'm using HTC HD2, if it's help..
ehud83 said:
I know. I'll try to upload a screenshot, to prove it.. My \Data was always empty, don't know why.
By the why: I'm using HTC HD2, if it's help..
Click to expand...
Click to collapse
Try doing this
Open a terminal emulator
Enter following:
Again pressing enter after each line:
Su
Cd /data
Ls
Then make a screen shot of that. It might be the file browser you're using. Ls will let us know if your data directory is truly empty
Sent from my GT-I9100 using Tapatalk
elesbb said:
Try doing this
Open a terminal emulator
Enter following:
Again pressing enter after each line:
Su
Cd /data
Ls
Then make a screen shot of that. It might be the file browser you're using. Ls will let us know if your data directory is truly empty
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Here you go
By picture I guess it's not..
ehud83 said:
Here you go
By picture I guess it's not..
Click to expand...
Click to collapse
yep its not empty, your file browser is just not working i guess. under settings, is there a "show hidden files" option? i use root browser and never had an issue, plus ive never used file manager so i know nothing about it. but you are correct it is not empty, also, if you look at that, you will see a "anr" in the list, that is where your traces.txt file will be
OK. I got access to \data\anr\traces.txt, but accidentally i deleted the file, but phone refuse to create it again!
Tried reboot, create it on my own (if so, it doesn't write anything in file), nothing works.
Any ideas?
Thanks!
ehud83 said:
OK. I got access to \data\anr\traces.txt, but accidentally i deleted the file, but phone refuse to create it again!
Tried reboot, create it on my own (if so, it doesn't write anything in file), nothing works.
Any ideas?
Thanks!
Click to expand...
Click to collapse
well the program that FCs all the time is the program that creates it. you just have to keep running that fuel log program a bunch of times to generate it.
This is a consolidated step by step for getting Google Play Music side loaded on the OUYA.
After the 5/21/2013 system update I had to redo the su install, as it wipes the system.
The first step is to install su and busybox.... Or to setup your computer for adb...
http://forum.xda-developers.com/showthread.php?t=2270589
To get google play music you need the 3 files listed below, I pulled the login and framework apks out of a 4.1.2 gapps zip.
http://goo.im/gapps/gapps-jb-20121011-signed.zip
the files are in /system/app
The music apk can be found here... or do a quick google...
http://forum.xda-developers.com/showthread.php?t=1350164
1) com.google.android.music-1.apk
2) googleloginservice.apk
3) googleservicesframework.apk
Put the files in the same folder as adb.exe you used in the su busy box install.
How to:
0. Connect to the device. if you followed the first link about su you should have wireless adb.
adb connect 192.168.xxx.xxx
1. Push the files over to the sdcard.
adb push GoogleLoginService.apk /sdcard/.
adb push GoogleServicesFramework.apk /sdcard/.
adb push com.google.android.music-1.apk /sdcard/.
2. Open a super user shell.
adb shell
su
3. Copy the files over to the system/app directory
cat /sdcard/GoogleLoginService.apk > /system/app/GoogleLoginService.apk
cat /sdcard/GoogleServicesFramework.apk > /system/app/GoogleServicesFramework.apk
cat /sdcard/com.google.android.music-1.apk > /system/app/com.google.android.music-1.apk
4. Set permissions on the system/apps files.
chmod 644 /system/app/GoogleLoginService.apk
chmod 644 /system/app/GoogleServicesFramework.apk
chmod 644 /system/app/com.google.android.music-1.apk
5. Exit and reboot.
exit
exit
adb reboot
6. When you launch the music app it will ask you to login to your google account.
7.Enjoy!
*remember any future updates will most likely remove any changes you made to system.
** I ran this on the 328 ota and got a few googleframework FC's when signing into google, I just closed out of them and its ran fine since.
*edit - typos, thanks zdraw
**edit - efficiency/least privilege permissions
Thanks! I'm going to try this tonight.
Worked for me but you have a few typos. There's no location after "adb push com.google.android.music-1.apk". You switched from GoogleLoginService to Services (not a big deal). In section 4, it should be app instead of apps. If your intent was to trip up copy-pasters you succeeded
zdraw said:
Worked for me but you have a few typos. There's no location after "adb push com.google.android.music-1.apk". You switched from GoogleLoginService to Services (not a big deal). In section 4, it should be app instead of apps. If your intent was to trip up copy-pasters you succeeded
Click to expand...
Click to collapse
That's what I get for re-typing rather then copy-pasting! lol
So I get about a few seconds into a song, and my Ouya just turns itself off... Thoughts? Logs I can look at?
Theres 2 ways we can do logcat, $ or #
First try a user logcat:
Adb shell
Logcat > /sdcard/log.txt
Then get the music app to crash
then stop the logcat (close terminal or cmd window...)
then take a look at the file for clues! ... or post it here for help.
For a root logcat do the same thing but type su once in shell... a ton more info is there if we cant find anything in the user logcat.
Thought though. .. are you on wifi or hard line? Put a bandwidth speed test app on the ouya and see what your speeds look like.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
My problem is selecting the log in option does not bring up a log in window. I got this loaded on no problem (using the .apk via drop box), and can get it to open, but not log in. Any idea's?
Sad . didnt work.
"Cant establish a reliable data connection to the server"
EDIT: Doesnt like wifi chip How odd.
pastebin.com/6EP5R5up
---------- Post added at 02:05 PM ---------- Previous post was at 01:58 PM ----------
APriestOfGix said:
My problem is selecting the log in option does not bring up a log in window. I got this loaded on no problem (using the .apk via drop box), and can get it to open, but not log in. Any idea's?
Click to expand...
Click to collapse
press the middle "U" button on your controller.
Setting > Google account
your welcome lol.
Off topic:
also this new account crap is annoying, trying to contribute to ouya modding since ive been working with android FOR YEARS, and someone sent me here, but i cant post till 5 min, cant post in dev section AT ALL. its annoying.
My Ouya arrived yesterday, this is exactly the sort of thing I was hoping to see on xda! I'll check this out now. Would it help if we flashed the zip from CWM rather than pushing the individual apks?
Thanks a lot for your work!
professorpoptart said:
4. Set permissions on the system/apps files.
chmod 6755 /system/app/GoogleLoginService.apk
chmod 6755 /system/app/GoogleServicesFramework.apk
chmod 6755 /system/app/com.google.android.music-1.apk
Click to expand...
Click to collapse
Why on earth would you chmod these to 6755? you do know what the 6 stands for, dont you? My guess is you probably dont. How about the 755? No? Apks are zip files. They do not get executed. You probably want to chmod them to 644.
gianptune said:
Why on earth would you chmod these to 6755? you do know what the 6 stands for, dont you? My guess is you probably dont. How about the 755? No? Apks are zip files. They do not get executed. You probably want to chmod them to 644.
Click to expand...
Click to collapse
And why the hell is the whole file name typed after the push when the name is exactly the same! what a waste of typing. We're dealing with a real noob here! lol
coleshill121 said:
My Ouya arrived yesterday, this is exactly the sort of thing I was hoping to see on xda! I'll check this out now. Would it help if we flashed the zip from CWM rather than pushing the individual apks?
Thanks a lot for your work!
Click to expand...
Click to collapse
If i can find a way to log into my google account i can make a flashable zip and probably get the play store working too :/
No Google account?
I following the directions, which look like they've been edited with the feedback provided already. I used the two APKs from the link provided, and the Google Play Music APK from the link provided, too. The latter had a different filename, but I renamed it, just in case.
I can launch Google Play Music fine, but all I get is a simple menu. There are no prompts to log in, and frankly not much to do. If I pull up my Android settings, I see an Ouya account listed, but not a Google one (nor a prompt to add one). If I pull up apps and go to "All", I have "Google Play Music" and "Google Account Manager" and "Google Framework Services".
Any ideas what I should try next?
rjbell4 said:
I following the directions, which look like they've been edited with the feedback provided already. I used the two APKs from the link provided, and the Google Play Music APK from the link provided, too. The latter had a different filename, but I renamed it, just in case.
I can launch Google Play Music fine, but all I get is a simple menu. There are no prompts to log in, and frankly not much to do. If I pull up my Android settings, I see an Ouya account listed, but not a Google one (nor a prompt to add one). If I pull up apps and go to "All", I have "Google Play Music" and "Google Account Manager" and "Google Framework Services".
Any ideas what I should try next?
Click to expand...
Click to collapse
You did hit the "U" button in google music and went to settings > google account right?
faxanidu said:
You did hit the "U" button in google music and went to settings > google account right?
Click to expand...
Click to collapse
Um, er, ...
Well, I thought I did. To be fair, this is brand new, and there are a couple of "U" buttons. I guess I hit the U-in-OUYA button once, and had only double-tapped the special-light-up-U button. Single-tapping that button pulls up settings, and I can connect, and now I'm listening to Google Play Music All-Access though my TV.
Pretty awesome... thanks, everyone.
rjbell4 said:
Um, er, ...
Well, I thought I did. To be fair, this is brand new, and there are a couple of "U" buttons. I guess I hit the U-in-OUYA button once, and had only double-tapped the special-light-up-U button. Single-tapping that button pulls up settings, and I can connect, and now I'm listening to Google Play Music All-Access though my TV.
Pretty awesome... thanks, everyone.
Click to expand...
Click to collapse
LOL. no problem man it happens took me like 2 days to figure out you can do that for almost all aps as the menu button on your phone. But now im still trying to figure out why i cant login to google. you using wifi or LAN???
faxanidu said:
LOL. no problem man it happens took me like 2 days to figure out you can do that for almost all aps as the menu button on your phone. But now im still trying to figure out why i cant login to google. you using wifi or LAN???
Click to expand...
Click to collapse
I started with WiFi, and before I tried and got it to work, I plugged in an Ethernet cable. My Ouya currently has two IP addresses, one for each interface. I presume that means that it would actively use the LAN interface, but I'm not certain.
rjbell4 said:
I started with WiFi, and before I tried and got it to work, I plugged in an Ethernet cable. My Ouya currently has two IP addresses, one for each interface. I presume that means that it would actively use the LAN interface, but I'm not certain.
Click to expand...
Click to collapse
hmmmm probably gonna have to go to a friends house since the roommate has a wifi router with no lan ports. Everytime i try to log in via wifi logcat says "failed to interface wlan0" -.-
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.
Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app
RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app
Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!
solved...
Installing busy box should resolve the issue...
Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?
Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.
My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.
I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues
CM Dev Settings
In Dev options is Root access set to Apps and ADB?
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?
hi, 2months ago I root the device with cm-10.2.1-maguro all working as expected, till I liked to use voice recorder after recording stopped the app close, realize that has to do with root.
I couldnt find how to enable the app through superuser, so start to check for alternatives so I landed here
Code:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
no hope also with that, uninstalled. The problem :
through adb + eclipse I can browse the device folders when using adb root - OK
on device superuser still @ settings - OK
when on android terminal - and run the command su writes su not found!
then I red @ superSU GplayURL
Superuser access management runs through a so called "su binary". There can be only one of these at a time.
Click to expand...
Click to collapse
how I can restore the original cm-10.2.1-maguro su binary?
whokn0ws said:
hi, 2months ago I root the device with cm-10.2.1-maguro all working as expected, till I liked to use voice recorder after recording stopped the app close, realize that has to do with root.
I couldnt find how to enable the app through superuser, so start to check for alternatives so I landed here
Code:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
no hope also with that, uninstalled. The problem :
through adb + eclipse I can browse the device folders when using adb root - OK
on device superuser still @ settings - OK
when on android terminal - and run the command su writes su not found!
then I red @ superSU GplayURL
how I can restore the original cm-10.2.1-maguro su binary?
Click to expand...
Click to collapse
Have you tried installing a rooted ROM?
Sent from my Nexus 4 using Tapatalk
nada, just download the cm desktop + cm android and made the root, nothing else.. please, advise how I can fix it..
whokn0ws said:
nada, just download the cm desktop + cm android and made the root, nothing else.. please, advise how I can fix it..
Click to expand...
Click to collapse
What recovery do you have installed?
Sent from my Nexus 4 using Tapatalk
http://www.cyanogenmod.org/
from desktop navigate to http://get.cm (download app)
from mobile navigate to http://get.cm (download app)
mobile get rooted in ~15min
thanks
so I dont know anything else..
I used to have this issue (but I didn't realise I had lost root because of an app), so I just downloaded and reflashed SU and all was good.
Download and flash from recovery: http://download.chainfire.eu/282/SuperSU/
hmm tried I got :
- Mounting
- Removing old
- Extracting files
- Restoring files
- Settings Permissions
set_perm : some canges failed
E: Error in data/media/0/CWM-SuperSU-v0.98.zip
(Status 7)
Installation aborted
-- when tried sideload ^the same with :
E: Error in /tmp/update.zip
!?
@nicknc writes :
ClockworMod Recovery v6.0.4.7
[searching..searching..searching..]
the solution is to download the latest SuperSU zip aka
http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
there isnot error7, installed rebooted su is there!.
the final Q, is how to enable an application to have root access (when SuperSU not prompt me) ?
Marvlesz thanks!
whokn0ws said:
the final Q, is how to enable an application to have root access (when SuperSU not prompt me) ?
Click to expand...
Click to collapse
When an app requests SU, you should be prompted. If you've set a default choice, you should be able to change that from the SU app. You should also be able to change previous choices from there as well.
basically the problem is :
1-voice recorder recording but no output
2-on built-in browser in any page has 'browse' to choose a file - the open dialog never opens! (aka facebook.com upload photo or imgur.com)
how I will resolve these? googlesearch=0%