EDIT 31aug2012: also this message appears if there is no "classes.dex" in the apk
Hi,
When you try to install certain apk you might get this error when using "adb install something.apk"
Andoid creates "shared users" like app_1 app_3 etc for packages you install. These UID's are like 10001, 10002, 10003 etc.
Sometimes the administration of these shared users gets messed up and you get error messages like:
INSTALL_FAILED_SHARED_USER_INCOMPATIBLE
The shared user administration is kept in /data/system:
-rw-rw-r-- system system 129933 2011-08-15 12:08 packages.xml
How to solve? You need a rooted phone and adb:
adb shell chmod 666 /data/system/packages.xml
adb pull /data/system/packages.xml
Now edit (notepad++) and remove the shared user in question xml block from the file:
Code:
<shared-user name="com.navngo" userId="10000">
<sigs count="1">
<cert index="4" />
</sigs>
<perms>
<item name="android.permission.READ_PHONE_STATE" />
<item name="android.permission.DISABLE_KEYGUARD" />
<item name="android.permission.INTERNET" />
<item name="android.permission.WRITE_EXTERNAL_STORAGE" />
<item name="android.permission.ACCESS_FINE_LOCATION" />
<item name="android.permission.ACCESS_LOCATION_EXTRA_COMMANDS" />
<item name="android.permission.ACCESS_COARSE_LOCATION" />
<item name="android.permission.READ_CONTACTS" />
<item name="android.permission.WRITE_CONTACTS" />
<item name="android.permission.ACCESS_NETWORK_STATE" />
<item name="android.permission.WAKE_LOCK" />
<item name="android.permission.MODIFY_AUDIO_SETTINGS" />
</perms>
</shared-user>
adb push packages.xml /data/system
adb shell rm /data/dalvik-cache/*
adb reboot
Now you should be able to install that apk.
Cheers
This problem might also be solved using ad uninstall command. (only for user apps)
Lets keep the same program as above as an example the you type from a dos box:
adb uninstall com.navngo.igo.javaclient
Now install it again. You need to know the package name. You can open the apk with winrar/zip and view the AndroidManifest.xml file. There you see the package name.
Cheers
thanks
thanks,
that's helped me to install new dolphin browser on mine superpad tablet pc
Hi,
I want to use android:sharedUserId="android.uid.system"
Then I get this error: Installation error: INSTALL_FAILED_SHARED_USER_INCOMPATIBLE
I removed the system uid following this procedure
It didn't work though
How to use system level privilege? I am working with hardware video codec, without system privilege. I am facing the same problem here : developer.nvidia.com/archived-tegra-forums/forum/android-how-call-libpvnvomxso-successfully
Any suggestion/idea would be welcome
The deleted "android.uid.system" in packages.xml comes back after reboot.
Hi,
I followed the instructions to remove section of android.uid.system in packages.xml. But after reboot, I felt that this file was re-generated and overwritten by system itself. I still can't install my app due to the same incompatible error.
Any help? Thanks!
Comment out shared-user name="android.uid.shared" xml block
mylifeisjourney said:
Hi,
I followed the instructions to remove section of android.uid.system in packages.xml. But after reboot, I felt that this file was re-generated and overwritten by system itself. I still can't install my app due to the same incompatible error.
Any help? Thanks!
Click to expand...
Click to collapse
Hi,
It worked for me... All you want to do is just comment out the block of XML elements under <shared-user name="android.uid.shared" userId="10012">
Note: I have "Su" permission in my Device.
This is is how i did
<!-- <shared-user name="android.uid.shared" userId="10012">
<sigs count="1">
<cert index="3" />
</sigs>
<perms>
<item name="android.permission.USE_CREDENTIALS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.mail" />
<item name="android.permission.WRITE_EXTERNAL_STORAGE" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.cp" />
<item name="android.permission.GET_ACCOUNTS" />
<item name="android.permission.READ_CONTACTS" />
<item name="android.permission.WRITE_CONTACTS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH" />
<item name="android.permission.READ_SYNC_STATS" />
<item name="android.permission.READ_PHONE_STATE" />
<item name="android.permission.READ_SMS" />
<item name="android.permission.MODIFY_PHONE_STATE" />
<item name="android.permission.WRITE_SETTINGS" />
<item name="android.permission.INTERNET" />
<item name="android.permission.SUBSCRIBED_FEEDS_READ" />
<item name="android.permission.VIBRATE" />
<item name="android.permission.SUBSCRIBED_FEEDS_WRITE" />
<item name="android.permission.WAKE_LOCK" />
<item name="android.permission.CALL_PRIVILEGED" />
</perms>
</shared-user> -->
mylifeisjourney said:
Hi,
I followed the instructions to remove section of android.uid.system in packages.xml. But after reboot, I felt that this file was re-generated and overwritten by system itself. I still can't install my app due to the same incompatible error.
Any help? Thanks!
Click to expand...
Click to collapse
same here, after I change the file and reboot it restore the line
no one?
android.uid.system (id 1000) is used for installing packages and I think this trick only works for 10.000 and higher id's.
Use google to find out more about the problem: https://www.google.com/search?num=40&hl=en&q=android.uid.system
Cheers
never mind
Okey, I did a small research to find out why my app was force closing everytime after I removed android:sharedUserId="android.uid.system" from AndroidManifest.xml.
It turned out that it doesn't have permission to force stop packages(it's a system monitor).
I have checked the androidmanifest.xml and everything looks correct to me. When installing, only wake lock and internet permissions are granted. I have attached the txt file... I hope somebody can help me out of here.
Thanks man This helped. A lot.
install failed shared user incompatible
Hi,
I have decompiled an APK using apktool. And changed one file "stings.xml" The language was in Chines and I just replaced all Chines text with English. Now I recompiled that APK using apktool. Then I signed that APK with JARSIGNER. Then I zipaligned the APK.
Even after that I was geeting "install failed shared user incompatible".
Then I used method told in this thread. But still having the same problem.
These are starting line of Menifist.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="android.uid.system" android:versionCode="1" android:versionName="1.0" package="com.android.ktcit"
xmlns:android="http://schemas.android.com/apk/res/android">
<application android:label="@string/app_name" android:icon="@drawable/icon" android:name="KTCITApp">
<receiver android:label="@string/app_name" android:name=".KTCITBootReceiver">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</receiver>
Could anyone help me out?
LLegend thanks a ton buds... helped me fix gmaps
It's the 1st time I encounter such problem. Fortunately got your solution . Thank you!
not worked for me
installing google calendar on i9100 4.0.4 simplistic V i have error
"incompatible wit other apps using same user id"
Hi, all. I'm desperately trying to understand what's going on here, but my programming/coding skills are nil. I've run into a shared user ID error with Google Calendar... How exactly would I use this technique to fix that?
Same here, can anyone please explain what should I do in simple words? I have this same problem and i'll be glad if you explain what is adb and those other comands, I have rooted tablet
Plz?...........
I was thinking that I could simply make the edit on boot, but it seems to regenerate every time an attempt is made to install. Everything can be hacked, there must be a way
Related
Hey all! I sat down today, for hours, trying to figure this out and I finally got it. The solution was actually a little bit easier than I had thought but I had to jump through a lot of hoops, semi-boot loops and more.
Status Bar XML's per a couple requests. Download and pop in an Extracted (NOT decoded) framework-res.apk. These are encoded with light colors. You CAN edit these in a hex editor like HxD, open up the file, then Find 0800001C Make sure "Hex Values" is selected.
EDIT: Currently Making a Windows App to do this and other things. Stay tuned.
First things first:
- Instructions are from a Win 7 x64 PC perspective
- I am NOT liable if you screw something up
- Your phone must be rooted, have froyo (2.2), and be de-odexed.
- This guide assumes you know how to use adb, 7-Zip
- I am not going to explain the above steps, use google or xda's search.
- If you are going to edit any .9.png files like "status_bar_close_on.9.png" you MUST keep the existing transparency and black bars in place. If you don't you will NOT be able to finish the process.
** Quick Trick **
Windows 7: Right click My Computer, Click Properties, Click Advanced System Settings, Click Environment Variables. In user vars and system vars there is a "path" variable. Edit it. Copy paste your SDK path and the SDK\Tools path.
Windows XP: Right click My Computer, Properties, Advanced Tab, Environment Variables. In user vars and system vars there is a "path" variable. Edit it. Copy paste your SDK path and the SDK\Tools path.
This will allow ADB to run without being in the sdk\tools folder.
Instructions:
0. Make a backup of framework-res.apk from /system/framework
- Open the command Prompt
: adb pull /system/framework/framework-res.apk C:\phonetheme\backup\fwbu.apk
: adb pull /system/framework/framework-res.apk C:\phonetheme\working\framework-res.apk
1. Get APKTOOL.
2. Download the top 2 files. Extract the contents of the files to C:\Windows
3. Open the command prompt
: apktool if C:\phonetheme\backup\fwbu.apk droidx (or whatever your device is)
: apktool d -f -t droidx C:\phonetheme\working\framework-res.apk C:\phonetheme\working\framework-decoded\
Optional. Go to C:\phonetheme\working\framework-decoded\res\drawable-hdpi-v4\ and modify images if you wish. You do not have to do it this way, but it can be done. You can just open the apk with 7 zip and extract them/edit them as well.
4. Go to C:\phonetheme\working\framework-decoded\res\layout
5. Open status_bar_latest_event_content.xml in notepad
6. Where ever you see something like this: android:textColor="?textColorSecondaryInverse"
In between the quotes, replace @color/dim_foreground_dark (or whatever) with a 8 char hex string. The format is NORMAL, not BACKWARD like in Hex. So when you are done you should have something like "#FFFFFFFF". The format is #AARRGGBB
The first color changes the heading "Voicemail Messages"
The second changes the descriptor "Dial *86"
The third changes the datetime stamp
So mine is, "#FFFFFFF", then "#FF747c8d", last "#ffbdc8df"
7. Make all your color changes. Save.
8. Open up the command prompt again
: apktool b C:\phonetheme\working\framework-decoded C:\phonetheme\build\framework-res.apk
Now IF you get a LOT of messages, like hundreds. Your .9.png's are not compiling correctly. You may have to load the originals and start over.
If you get WARNINGS but not many (mine were related to a translation message for "en-GB") then you are fine.
9. Browse to C:\phonetheme\working\framework-decoded\build
Ah ha, that wasn't there before!
10. Open C:\phonetheme\working\framework-res.apk in 7-Zip
11. With it open delete the /res directory, AndroidManifest.xml, resources.arsc files from 7-Zip.
LEAVE THE /META-INF and /assets folders!
12. From the C:\phonetheme\working\framework-decoded\build directory, open apk directory. Select and drag the /res folder, AndroidManifest.xml, and resources.arsc to the 7-Zip window so they are in the archive.
13. Backup C:\phonetheme\working\framework-res.apk. Copy to C:\phonetheme\backup\ and name it something like framework-res-new.apk
14. Open the command prompt window
: adb remount
: adb push C:\phonetheme\working\framework-res.apk /sdcard/framework-res.apk
: adb push C:\phonetheme\backup\fwbu.apk /sdcard/fwbu.apk (you only need to do this when you have a new backup!
: adb shell
#: su (if not already #)
[At this point, I always make my screen on and unlocked, you don't have to, but I like to]
#: cp /sdcard/framework-res.apk /system/framework/
At this point, if you try and open anything on your phone, it will lock for a second and droid to the droid text/eye animation for a second. IF it loops! You will notice that you are still connected over ADB.
If and only IF it LOOPS from the eye to the text or if the text animation looks obviously broken. Type the following
#: cp /sdcard/fwbu.apk /system/framework/framework-res.apk
The next time it loops, it will load your backup and start running again. DO NOT REBOOT! Other wise you have to nandroid or SBF it like I did.
#: rm /sdcard/framework-res.apk
#: exit
: adb remount
: adb pull /system/framework/framework-res.apk C:\phonetheme\backup\fwbu.apk
If it comes up normally, and you get to the lock screen, unlock, and open your notification shade. Tada! You are done!
Best part? Because the decoded folder is there, if you want to make changes you just start at Step 7 again, delete the build folder, re-build and so on.
Here's what mine looks like!
{
"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"
}
Last note. If I missed something, let me know, or if you have problems, report them here. I'll try and answer best I can. I worked for hours on this today, so I may have missed something, though I doubt it.
In the XML. Look in the "layout" folder of framework-res.apk. I'm not sure whicl file it is. But try this:
Pull every file from the "layout" folder. Open each XML file in a hex editor, like HxD or Hex Workshop. Now in status_bar.xml if you edit it the right way you can change the color of notification, like when you get a text message or when you connect the phone to a computer. That's for notifications though.
So you might want to try other XML files.
Open an random one (in the hex editor), and look for the values 08 00 00 1C, then you have to change the values AFTER that. The are black so that values are going to be 00 00 00 FF. Change the 0's to the color you want, the color you want has to be a hex value.
If that's confusing. PM, and I'll give you my gTalk.
ghostlypickel said:
In the XML. Look in the "layout" folder of framework-res.apk. I'm not sure whicl file it is. But try this:
Pull every file from the "layout" folder. Open each XML file in a hex editor, like HxD or Hex Workshop. Now in status_bar.xml if you edit it the right way you can change the color of notification, like when you get a text message or when you connect the phone to a computer. That's for notifications though.
So you might want to try other XML files.
Open an random one (in the hex editor), and look for the values 08 00 00 1C, then you have to change the values AFTER that. The are black so that values are going to be 00 00 00 FF. Change the 0's to the color you want, the color you want has to be a hex value.
If that's confusing. PM, and I'll give you my gTalk.
Click to expand...
Click to collapse
Yes. He's correct ^^^. I replied to your question in my theme thread and this correlates with what I stated. Look for other status bar xml's. I know there are more than just status_bar.xml
Sent from my DROIDX using Tapatalk
Doesn't work for FroYo.
The hex string 0800001C doesn't exist in the other status bar xmls. I think I've figured this out though.
This is out of status_bar_extended.xml (plain-text)
Code:
android:textColor="?textColorSecondaryInverse"
Then I found a file in /res/values/styles.xml I see:
Code:
<item name="textColorSecondaryInverse">@color/secondary_text_light</item>
Then in /res/color/secondary_text_light.xml
Code:
<selector
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:state_window_focused="false" android:state_enabled="false" android:color="@color/dim_foreground_light_disabled" />
<item android:state_enabled="false" android:state_selected="true" android:color="@color/dim_foreground_light_disabled" />
<item android:state_enabled="false" android:state_pressed="true" android:color="@color/dim_foreground_light_disabled" />
<item android:state_selected="true" android:color="@color/dim_foreground_dark" />
<item android:state_pressed="true" android:color="@color/dim_foreground_dark" />
<item android:state_enabled="false" android:color="@color/dim_foreground_light_disabled" />
<item android:state_window_focused="false" android:color="@color/dim_foreground_light" />
<item android:color="@color/dim_foreground_light" />
</selector>
Then FINALLY in /res/values/colors.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<resources>
<color name="darker_gray">#ffaaaaaa</color>
<color name="white">#ffffffff</color>
<color name="black">#ff000000</color>
<color name="transparent">#00000000</color>
<color name="background_dark">#ff000000</color>
<color name="background_light">#ffffffff</color>
<color name="safe_mode_text">#80ffffff</color>
<color name="bright_foreground_dark">#ffffffff</color>
<color name="bright_foreground_dark_disabled">#80ffffff</color>
<color name="bright_foreground_dark_inverse">#ff000000</color>
<color name="dim_foreground_dark">#ffbebebe</color>
<color name="dim_foreground_dark_disabled">#80bebebe</color>
<color name="dim_foreground_dark_inverse">#ff323232</color>
<color name="dim_foreground_dark_inverse_disabled">#80323232</color>
<color name="hint_foreground_dark">#ff808080</color>
<color name="bright_foreground_light">#ff000000</color>
<color name="bright_foreground_light_inverse">#ffffffff</color>
<color name="bright_foreground_light_disabled">#80000000</color>
<color name="dim_foreground_light">#ff323232</color>
<color name="dim_foreground_light_disabled">#80323232</color>
<color name="dim_foreground_light_inverse">#ffbebebe</color>
<color name="dim_foreground_light_inverse_disabled">#80bebebe</color>
<color name="hint_foreground_light">#ff808080</color>
<color name="lighter_gray">#ffdddddd</color>
<color name="perms_dangerous_grp_color">#ffdd6826</color>
<color name="perms_dangerous_perm_color">#ffdd6826</color>
<color name="shadow">#cc222222</color>
<color name="search_url_text_normal">#ff7fa87f</color>
<item type="color" name="search_url_text_selected">@color/black</item>
<item type="color" name="search_url_text_pressed">@color/black</item>
<item type="color" name="search_widget_corpus_item_background">@color/lighter_gray</item>
<item type="color" name="sliding_tab_text_color_active">@color/black</item>
<item type="color" name="sliding_tab_text_color_shadow">@color/black</item>
<color name="keyguard_text_color_normal">#ffffffff</color>
<color name="keyguard_text_color_unlock">#ffa7d84c</color>
<color name="keyguard_text_color_soundoff">#ffffffff</color>
<color name="keyguard_text_color_soundon">#ffe69310</color>
<color name="keyguard_text_color_decline">#fffe0a5a</color>
<color name="config_defaultNotificationColor">#ff00ff00</color>
</resources>
I think I have to hex edit that, and figure out where in the hex it is....I'll test it all out and let you guys know!
Please do... I wanna shade those damn notifications black asap lol.
phimuskapsi said:
Doesn't work for FroYo.
The hex string 0800001C doesn't exist in the other status bar xmls. I think I've figured this out though.
This is out of status_bar_extended.xml (plain-text)
Code:
android:textColor="?textColorSecondaryInverse"
Then I found a file in /res/values/styles.xml I see:
Code:
<item name="textColorSecondaryInverse">@color/secondary_text_light</item>
Then in /res/color/secondary_text_light.xml
Code:
<selector
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:state_window_focused="false" android:state_enabled="false" android:color="@color/dim_foreground_light_disabled" />
<item android:state_enabled="false" android:state_selected="true" android:color="@color/dim_foreground_light_disabled" />
<item android:state_enabled="false" android:state_pressed="true" android:color="@color/dim_foreground_light_disabled" />
<item android:state_selected="true" android:color="@color/dim_foreground_dark" />
<item android:state_pressed="true" android:color="@color/dim_foreground_dark" />
<item android:state_enabled="false" android:color="@color/dim_foreground_light_disabled" />
<item android:state_window_focused="false" android:color="@color/dim_foreground_light" />
<item android:color="@color/dim_foreground_light" />
</selector>
Then FINALLY in /res/values/colors.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<resources>
<color name="darker_gray">#ffaaaaaa</color>
<color name="white">#ffffffff</color>
<color name="black">#ff000000</color>
<color name="transparent">#00000000</color>
<color name="background_dark">#ff000000</color>
<color name="background_light">#ffffffff</color>
<color name="safe_mode_text">#80ffffff</color>
<color name="bright_foreground_dark">#ffffffff</color>
<color name="bright_foreground_dark_disabled">#80ffffff</color>
<color name="bright_foreground_dark_inverse">#ff000000</color>
<color name="dim_foreground_dark">#ffbebebe</color>
<color name="dim_foreground_dark_disabled">#80bebebe</color>
<color name="dim_foreground_dark_inverse">#ff323232</color>
<color name="dim_foreground_dark_inverse_disabled">#80323232</color>
<color name="hint_foreground_dark">#ff808080</color>
<color name="bright_foreground_light">#ff000000</color>
<color name="bright_foreground_light_inverse">#ffffffff</color>
<color name="bright_foreground_light_disabled">#80000000</color>
<color name="dim_foreground_light">#ff323232</color>
<color name="dim_foreground_light_disabled">#80323232</color>
<color name="dim_foreground_light_inverse">#ffbebebe</color>
<color name="dim_foreground_light_inverse_disabled">#80bebebe</color>
<color name="hint_foreground_light">#ff808080</color>
<color name="lighter_gray">#ffdddddd</color>
<color name="perms_dangerous_grp_color">#ffdd6826</color>
<color name="perms_dangerous_perm_color">#ffdd6826</color>
<color name="shadow">#cc222222</color>
<color name="search_url_text_normal">#ff7fa87f</color>
<item type="color" name="search_url_text_selected">@color/black</item>
<item type="color" name="search_url_text_pressed">@color/black</item>
<item type="color" name="search_widget_corpus_item_background">@color/lighter_gray</item>
<item type="color" name="sliding_tab_text_color_active">@color/black</item>
<item type="color" name="sliding_tab_text_color_shadow">@color/black</item>
<color name="keyguard_text_color_normal">#ffffffff</color>
<color name="keyguard_text_color_unlock">#ffa7d84c</color>
<color name="keyguard_text_color_soundoff">#ffffffff</color>
<color name="keyguard_text_color_soundon">#ffe69310</color>
<color name="keyguard_text_color_decline">#fffe0a5a</color>
<color name="config_defaultNotificationColor">#ff00ff00</color>
</resources>
I think I have to hex edit that, and figure out where in the hex it is....I'll test it all out and let you guys know!
Click to expand...
Click to collapse
08 00 00 1C does exist. That's how I was able to change the colors for my theme.
Make sure the there are spaces, exactly like I typed.
I have gone through all of the other status bar xmls, searched for it with and without spaces. Both work in HxD search. Anyway. My method now.
1. Get apk tool and follow the instructions to install
2. Decode framework-res.apk to a dir of your choosing
3. Now you have xmls you can edit without a hex editor, notepad works.
4. Change the values, re-encode with apktool
5. Pop the new framework on.
I'm out smoking a cig I'll test this method when I go back in. and update with results
Getting errors on build...hrm...
EDIT: Finally got it to build. Making a nandroid backup before copying it back though....
EDIT2: built and then signed (which I shouldn't have done apparently) almost bricked. Apparently my nandroid backup failed too -.- says it can't mount the sdcard. I'll be back, have to SBF to 2.1 then Root, then install 2.2 again.
EDIT3: Whew, after a scare where SBF failed (had to format the ROM!) got it back on. About 15 minutes and I'll try somethin else.
EDIT4: Finally looks like I'm ok...working on nandroid, keep getting an error....
if you edit an xml file can you drop it straight into an unzipped fram folder, rezip it, rename it and install?
No. because the apk is decompiled. It has to be recompiled then I think signed. I've tried a couple methods and every time I copy the recompiled one to system, signed or not I get trapped at a logo loop. Thankfully if you use adb to copy the framework over you can copy a good one back the adb connection stays open. Copy it back and after a few seconds it starts to loaf properly again
Sent from my DROIDX using XDA App
when i decompile it said it couldnt for a few files, so recompiling will give me a bad apk, what if you recompile then pull just the xml files and place them in a good framework.apk . Have you tried that yet?
how many xml's are you changing at once?
bad4u6669 said:
when i decompile it said it couldnt for a few files, so recompiling will give me a bad apk, what if you recompile then pull just the xml files and place them in a good framework.apk . Have you tried that yet?
how many xml's are you changing at once?
Click to expand...
Click to collapse
Just one. The reason I can't just drag and drop to a known good one is that the folder is not in the normal one. There are a bunch of folders missing. Look at the decoded folder vs. what's in the file when opened with 7-zip.
I'm changing /res/values/colors.xml
no luck with status_bar.xml in res/layout ? there is colors in there...
Thought I had it there for a sec....getting much much closer. I can compile now, I get warnings but no errors...
Before when I had a "bad" framework, the droid text wouldn't even animate right, never got to the eye either.
Now I can get to the eye, but it just loops. Can fix by adb'ing the files back.
... Still working on this. Not giving up.,
EDIT: Yes. I'm positive. I've edited all I can in that file.
imma see what i can get out of this
https://docs.google.com/Doc?docid=0AcdxIJRSH9ypZGZzc2pxNDlfMjdnazk4OHNxZA&hl=en
and maybe tinker more with xultimate tool
dont you just love how no one will give a straight answer on how to do this... half threads here and there and still no whole...
I am very...very close.
EDIT:Omg...I got it. I'll edit the front page in a bit with instructions.
phimuskapsi said:
I am very...very close.
EDIT:Omg...I got it. I'll edit the front page in a bit with instructions.
Click to expand...
Click to collapse
hope thats going to come with full command lines you had to type
Proof of concept...the only problem is the way I edited it...well, it's gonna be complicated to get it JUST to effect the notification bar. I'm working on that part now.
phimuskapsi said:
Proof of concept...the only problem is the way I edited it...well, it's gonna be complicated to get it JUST to effect the notification bar. I'm working on that part now.
Click to expand...
Click to collapse
you have exactly what i need for my theme, white verizon , notification text and white date.
Note the Verizon is changed by a services.jar hack. Not this XML editing method.
This is a tutorial about how to download and compile specific parts in aosp based roms (such as CM10)
Written for AOSP noobs like me a year ago.
Note: I wrote this tutorial actually for my blog, as a beginners repo/compile tut, but why not share here
Introduction:
Downloading rom sources is done with the tool “repo”, this is the most awesome downloader in existence. Not only it looks very cool, it also reaches top speed at all times. But it’s only for linux (which is good since when you are busy with aosp roms you should be on linux)
Why is it awesome? Since you decide yourself how many jobs (aka connections) you make with the server. This means you always will get top speed, there is probably no faster download method available on the Internet (except for speedtests, but they don’t count). Next to the downloading of specific parts it’s of course also handy to know how to actually compile them.
Download:
The easiest way of fetching for example a batch of AOSP apps is like this:
1. Choose the desired tag you want to use, in the example I will use android-4.2.2_r1
2. Now make a dir somewhere:
Code:
- mkdir ~/aosp-apps
- cd ~/aosp-apps
3. Download repo when not installed yet:
Code:
- curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
- chmod a+x ~/bin/repo
4. Enter the line that will download the initial manifest.
for AOSP:
Code:
- repo init -u https://android.googlesource.com/platform/manifest -b android-4.2.2_r1
Enter your name and email address and wait until it completes
for CM
Code:
- repo init -u https://github.com/Cyanogenmod/android -b cm-10.1
5. Go in the hidden “.repo” dir and change the manifest
Code:
- cd .repo
- gedit manifest.xml (if you don’t have decent text editor such as “gedit”, install it! “sudo apt-get install gedit”
)
For example when you only want to download the apps, just remove all lines that are not app related. simple as that:
Code:
<?xml version=”1.0″ encoding=”UTF-8″?>
<manifest>
<remote name=”aosp”
fetch=”..” />
<default revision=”refs/tags/android-4.2.2_r1″
remote=”aosp”
sync-j=”4″ />
<project path=”packages/apps/BasicSmsReceiver” name=”platform/packages/apps/BasicSmsReceiver” />
<project path=”packages/apps/Bluetooth” name=”platform/packages/apps/Bluetooth” />
<project path=”packages/apps/Browser” name=”platform/packages/apps/Browser” />
<project path=”packages/apps/Calculator” name=”platform/packages/apps/Calculator” />
<project path=”packages/apps/Calendar” name=”platform/packages/apps/Calendar” />
<project path=”packages/apps/Camera” name=”platform/packages/apps/Camera” />
<project path=”packages/apps/CellBroadcastReceiver” name=”platform/packages/apps/CellBroadcastReceiver” />
<project path=”packages/apps/CertInstaller” name=”platform/packages/apps/CertInstaller” />
<project path=”packages/apps/Contacts” name=”platform/packages/apps/Contacts” />
<project path=”packages/apps/DeskClock” name=”platform/packages/apps/DeskClock” />
<project path=”packages/apps/Email” name=”platform/packages/apps/Email” />
<project path=”packages/apps/Exchange” name=”platform/packages/apps/Exchange” />
<project path=”packages/apps/Gallery” name=”platform/packages/apps/Gallery” />
<project path=”packages/apps/Gallery2″ name=”platform/packages/apps/Gallery2″ />
<project path=”packages/apps/HTMLViewer” name=”platform/packages/apps/HTMLViewer” />
<project path=”packages/apps/KeyChain” name=”platform/packages/apps/KeyChain” />
<project path=”packages/apps/Launcher2″ name=”platform/packages/apps/Launcher2″ />
<project path=”packages/apps/LegacyCamera” name=”platform/packages/apps/LegacyCamera” />
<project path=”packages/apps/Mms” name=”platform/packages/apps/Mms” />
<project path=”packages/apps/Music” name=”platform/packages/apps/Music” />
<project path=”packages/apps/MusicFX” name=”platform/packages/apps/MusicFX” />
<project path=”packages/apps/Nfc” name=”platform/packages/apps/Nfc” />
<project path=”packages/apps/PackageInstaller” name=”platform/packages/apps/PackageInstaller” />
<project path=”packages/apps/Phone” name=”platform/packages/apps/Phone” />
<project path=”packages/apps/Protips” name=”platform/packages/apps/Protips” />
<project path=”packages/apps/Provision” name=”platform/packages/apps/Provision” />
<project path=”packages/apps/QuickSearchBox” name=”platform/packages/apps/QuickSearchBox” />
<project path=”packages/apps/Settings” name=”platform/packages/apps/Settings” />
<project path=”packages/apps/SoundRecorder” name=”platform/packages/apps/SoundRecorder” />
<project path=”packages/apps/SpareParts” name=”platform/packages/apps/SpareParts” />
<project path=”packages/apps/SpeechRecorder” name=”platform/packages/apps/SpeechRecorder” />
<project path=”packages/apps/Stk” name=”platform/packages/apps/Stk” />
<project path=”packages/apps/Tag” name=”platform/packages/apps/Tag” />
<project path=”packages/apps/VideoEditor” name=”platform/packages/apps/VideoEditor” />
<project path=”packages/apps/VoiceDialer” name=”platform/packages/apps/VoiceDialer” />
</manifest>
When done, save it and go a dir back in the terminal
Code:
- cd ..
6. Download the packages
Code:
- repo sync -j16 (-j16 stands for 16 jobs max. This is for around a 100mbit line)
(With my 60mb/s connection I get max speed 7.2mb/s at -j8)
The packages will be download as quickly as possible to your harddrive now.
Compile:
To compile the obtained packages separately you will need a AOSP environment (or CM/AOKP etc). When you have a succesfull environment which is able to compile for your device you may enter:
Code:
- source build/envsetup.sh
- lunch (now choose your device, for example, full_ariesve-userdebug)
- now you’re theoretically ready to compile
to compile an app on the easiest way:
Code:
- make Appname -j8
where “Appname” is the name of the folder placed in packages/apps/..
This also counts for “SystemUI” which is not in that folder.
Code:
- make Calculator -j8 (for example)
And the -j param again stands for the number of jobs, remember that this is compiling and not downloading, so the “standard rule” with this is, number of cores of your CPU + 1.
Which makes a regular quad core (-j5) but makes a i7 CPU with Hyper threading (-j9). When using -j16 for example there could be moments that your cpu will be overloaded so much that your mouse will lag all over the place.
(Linux forces the cpu to perform higher then it actually should, resulting in a very strange fan sound in my case)
When having trouble, when it stops or just nags about some useless stuff.
You should try using the “-k” param, this tells the make command to keep going when a non-critical error occurs.
Code:
- make Calculator -k -j8
When having issues with the local module tags, you should enter this:
Code:
- make Calculator -k LOCAL_MODULE_TAGS=optional -j8
To compile other parts you also need to enter the folder name, here are some examples from /frameworks/base
Code:
- make policy (the power menu and lockscreen)
- make framework (the initial framework files)
- make framework-res (the initial framework resources)
- make services (the services.jar file)
or more examples:
Code:
- make sdk (builds the android sdk)
- make modules (builds all modules)
- make installclean (removes all staging directories, such as out/target/product/boardname/system)
- make clean (removes the whole /out directory)
:silly:
another amazing tutorial made by you.. THANKS !!
This is huge! Thanks brood!
Laurentyu1995 said:
another amazing tutorial made by you.. THANKS !!
Click to expand...
Click to collapse
You're welcome, I will keep em comming
educk said:
This is huge! Thanks brood!
Click to expand...
Click to collapse
Thanks, and you're welcome
o, btw, added link to aosp tags and removed links in code
broodplank1337 said:
You're welcome, I will keep em comming
Thanks, and you're welcome
o, btw, added link to aosp tags and removed links in code
Click to expand...
Click to collapse
Great job !! Might want to clean it up and fix up the few mistakes. Also, not sure if you did it on purpose or not but you gave the 4.2 branch of AOSP and 4.1 of CM. Other than that, great guide brood!!
Xistance said:
Great job !! Might want to clean it up and fix up the few mistakes. Also, not sure if you did it on purpose or not but you gave the 4.2 branch of AOSP and 4.1 of CM. Other than that, great guide brood!!
Click to expand...
Click to collapse
Thanks . the actual tutorial (on my site) only includes the AOSP example, I added the CM example here but didn't thought about making them match versions, however, I will change it ^^.
Hi,
Is there any way to add/update a configuration xml file to an app already installed on an Android 4.2+ device?
The purpose of this would be to eliminate the setup process for technologically impaired users.
Case in point: an application through which the user can send data over wifi/3g to an IIS server, the user will have to configure the server address/location, username and password (which is generally void if it's not requested otherwise), the location of the actual data file that must be synced.
All i want to do is eliminate the part where the user has to set-up anything else but his username.
The configuration file is located in </Data/Data/application.name/files> and it's called application.config.xml
Could it be added in an apk which will act as an update?
The devices will not be rooted and the config.xml file will be different (different servers), depending on the users' location so it can't be hardcoded in the sync application.
This is the actual content of the .xml file once the settings have been made, the sync app generates a blank config.xml file during the installation.
Code:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="ClientLocation" value="/storage/emulated/0/clientapp_00" />
<add key="Username" value="User Name" />
<add key="Password" value="d41d8cd98f00b204e9800998ecf8427e" />
<add key="ServerLocation" value="Http://192.168.0.101:55541/server/sync.aspx" />
<add key="Compression" value="True" />
<add key="ServerConnections" value="Sync Serv,Http://192.168.0.101:55541/server/sync.aspx" />
<add key="Language" value="en" />
<add key="SyncApk" value="Sync.apk" />
<add key="SyncPackage" value="Data.Sync" />
</appSettings>
</configuration>
Thanks in advance!
Any help guys?
Can somebody tell me how to keep the battery from looking like it`s draining, meaning keeping the battery white while discharging.i like to always have a solid color battery without discharging animatition, and percentage on the side. i tried editing system ui arrays.xml turning every thing under battery to white but no go please anyone thankyou
Decompile systemui and replace all of the charging drawables with the normal ones. Them recompile and push back into system/priv-app with rw-r-r permissions.
Sent from my HTC Desire using xda app-developers app
Chromium said:
Decompile systemui and replace all of the charging drawables with the normal ones. Them recompile and push back into system/priv-app with rw-r-r permissions.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
does this keep the battery white while not charging,i want the battery to stay white never looking like its draining
wait theres are no charging drawables in system ui
daman215 said:
does this keep the battery white while not charging,i want the battery to stay white never looking like its draining
wait theres are no charging drawables in system ui
Click to expand...
Click to collapse
Decompile SystemUI.apk then go to /res/values/ and open colors.xml
You'll find several codes for the battery including the one your are looking for. (I don't remember the right name - 'highlighted xxx' I think)
Recompile and push it to your phone.
Primokorn said:
Decompile SystemUI.apk then go to /res/values/ and open colors.xml
You'll find several codes for the battery including the one your are looking for. (I don't remember the right name - 'highlighted xxx' I think)
Recompile and push it to your phone.
Click to expand...
Click to collapse
heres my colors xml theres only 3 codes and i change 1 to ffffffff and thats the frame no change at all
<?xml version="1.0" encoding="utf-8"?>
<resources>
<color name="card_background">#ffffffff</color>
<color name="card_background_header">#ffffffff</color>
<color name="card_backgroundExpand">#fff5f5f5</color>
<color name="card_text_color_header">#ff000000</color>
<color name="card_expand_title_color">#ffb3b2b2</color>
<color name="card_pressed">#7e3c3c3c</color>
<color name="card_activated">#ffcfe9f3</color>
<color name="notification_shortcut_color">#ffffffff</color>
<color name="navigationbar_button_default_color">#ffffffff</color>
<color name="navigationbar_button_glow_default_color">#ffffffff</color>
<color name="navring_system_icon_default_color">#ff000000</color>
<color name="qs_background_color">#ff212121</color>
<color name="qs_background_pressed_color">#ff161616</color>
<color name="system_bar_background_opaque">#ff000000</color>
<color name="system_bar_background_semi_transparent">#66000000</color>
<color name="notification_panel_solid_background">#ff000000</color>
<color name="status_bar_recents_app_label_color">#ffffffff</color>
<color name="notification_list_shadow_top">#80000000</color>
<color name="notification_panel_scrim_color">#b0000000</color>
<color name="batterymeter_frame_color">#ffffffff</color>
<color name="batterymeter_charge_color">#ffffffff</color>
<color name="batterymeter_bolt_color">#ff000000</color>
<color name="status_bar_clock_color">#ffffffff</color>
<color name="pie_overlay_color">#ff000000</color>
<color name="pie_snap_color">#ffffffff</color>
<color name="pie_text_color">#ffffffff</color>
<color name="pie_foreground_color">#ffffffff</color>
<color name="pie_background_color">#ff000000</color>
<color name="pie_selected_color">#ff5c5c5c</color>
<color name="pie_long_pressed_color">#ff8c8c8c</color>
<color name="pie_outline_color">#ff5c5c5c</color>
<color name="recent_background">#80f5f5f5</color>
<color name="gesture_overlay_background_fill_color">#80000000</color>
<color name="gesture_color">@android:color/holo_blue_light</color>
</resources>
daman215 said:
heres my colors xml theres only 3 codes and i change 1 to ffffffff and thats the frame no change at all
</resources>
Click to expand...
Click to collapse
Here is my systemui (from my theme so these are redirections!):
Code:
<item name="color/batterymeter_frame_color">@color/highlighted_text_holo_dark</item>
<item name="color/[B][COLOR="red"]batterymeter_charge_color[/COLOR][/B]">@color/holo_blue_light</item>
<item name="color/batterymeter_bolt_color">@color/holo_blue_flash</item>
<item name="color/batterymeter_critical">@color/holo_red</item>
<item name="color/batterymeter_low">@color/holo_orange</item>
<item name="color/batterymeter_full">@color/holo_blue_flash</item>
<item name="color/status_bar_clock_color">@color/holo_blue_flash</item>
<item name="color/status_bar_battery_text_color">@color/holo_blue_flash</item>
<item name="color/status_bar_battery_text_color_plugged">@color/holo_blue_strong</item>
Maybe you have to modify another thing if you keep the original apk. Check /res/values/public.xml too.
With Mahdi ROM for instance it's probably necessary to modify this line:
Code:
<public type="color" name="batterymeter_frame_color" id="[B][COLOR="Red"]0x7f06000d[/COLOR][/B]" />
Primokorn said:
Here is my systemui (from my theme so these are redirections!):
Code:
<item name="color/batterymeter_frame_color">@color/highlighted_text_holo_dark</item>
<item name="color/[B][COLOR="red"]batterymeter_charge_color[/COLOR][/B]">@color/holo_blue_light</item>
<item name="color/batterymeter_bolt_color">@color/holo_blue_flash</item>
<item name="color/batterymeter_critical">@color/holo_red</item>
<item name="color/batterymeter_low">@color/holo_orange</item>
<item name="color/batterymeter_full">@color/holo_blue_flash</item>
<item name="color/status_bar_clock_color">@color/holo_blue_flash</item>
<item name="color/status_bar_battery_text_color">@color/holo_blue_flash</item>
<item name="color/status_bar_battery_text_color_plugged">@color/holo_blue_strong</item>
Maybe you have to modify another thing if you keep the original apk. Check /res/values/public.xml too.
With Mahdi ROM for instance it's probably necessary to modify this line:
Code:
<public type="color" name="batterymeter_frame_color" id="[B][COLOR="Red"]0x7f06000d[/COLOR][/B]" />
Click to expand...
Click to collapse
i will have a look and try again
edit: i just tried to change battery level color but no go
I am sure this information can be found in some forum on XDA with adequate searching, but who wants to do that? Read on.
Many here do not want to set default access in SuperSU to "Grant." For the Fire devices, setting it to "Prompt" has the same effect as "Deny." Manually changing the default from "Prompt" to "Grant" whenever an app needs access isn't a great solution either. Here's how you can configure per-app access in SuperSU using its preferences file:
-- Edit /data/data/eu.chainfire.supersu/shared_prefs/eu.chainfire.supersu_preferences.xml in this manner:
Code:
<string name="config_com.keramidas.TitaniumBackup_access">grant</string>
This will tell SuperSU to grant permanent root access to, in this example, Titanium Backup.
You will have to add such a line for every app that needs root access. If you do this, all the permitted apps should now show up in the Apps tab in SuperSU. You can then set default access to "Prompt" or "Deny" in SuperSU.
Here's what I have in my current preferences file:
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<boolean name="config_default_notify" value="true" />
<int name="shown_follow" value="1" />
<boolean name="freeload" value="false" />
<string name="config_default_log">access</string>
<boolean name="tapjack" value="true" />
<boolean name="config_default_enablemultiuser" value="false" />
<string name="config_default_access">prompt</string>
<string name="locale"></string>
<boolean name="refresh" value="true" />
<boolean name="config_default_enableduringboot" value="false" />
<string name="config_default_logformat">31122359</string>
<boolean name="config_default_enablemountnamespaceseparation" value="true" />
<boolean name="superuser" value="true" />
<string name="theme">material_dark</string>
<boolean name="reauthenticate" value="true" />
<string name="config_default_logage">14</string>
<boolean name="config_default_trustsystem" value="false" />
<string name="config_default_wait">10</string>
<string name="config_com.speedsoftware.rootexplorer_access">grant</string>
<string name="config_jackpal.androidterm_access">grant</string>
<string name="config_eu.chainfire.flash_access">grant</string>
<string name="config_eu.thedarken.sdm_access">grant</string>
<string name="config_org.adaway_access">grant</string>
<string name="config_in.co.pricealert.apps2sd_access">grant</string>
<string name="config_com.dp.sysmonitor.app_access">grant</string>
<string name="config_com.jrummy.liberty.toolbox_access">grant</string>
<string name="config_com.k2.backup_access">grant</string>
<string name="config_com.seasmind.android.gmappmgr_access">grant</string>
<string name="config_ru.littlevictor.powermenu_access">grant</string>
<string name="config_com.keramidas.TitaniumBackup_access">grant</string>
<string name="config_com.buak.Link2SD_access">grant</string>
<string name="config_de.robv.android.xposed.installer_access">grant</string>
<string name="config_ADB shell_access">grant</string>
</map>
This, while cumbersome at times is the much more secure solution.
Thank you @retyre. I've always depended on your help and your guides when it comes to the Fire HD. Thanks for finding this and sharing it with us.
retyre said:
I am sure this information can be found in some forum on XDA with adequate searching, but who wants to do that? Read on.
Many here do not want to set default access in SuperSU to "Grant." For the Fire devices, setting it to "Prompt" has the same effect as "Deny." Manually changing the default from "Prompt" to "Grant" whenever an app needs access isn't a great solution either. Here's how you can configure per-app access in SuperSU using its preferences file:
-- Edit /data/data/eu.chainfire.supersu/shared_prefs/eu.chainfire.supersu_preferences.xml in this manner:
Code:
<string name="config_com.keramidas.TitaniumBackup_access">grant</string>
This will tell SuperSU to grant permanent root access to, in this example, Titanium Backup.
You will have to add such a line for every app that needs root access. If you do this, all the permitted apps should now show up in the Apps tab in SuperSU. You can then set default access to "Prompt" or "Deny" in SuperSU.
Here's what I have in my current preferences file:
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<boolean name="config_default_notify" value="true" />
<int name="shown_follow" value="1" />
<boolean name="freeload" value="false" />
<string name="config_default_log">access</string>
<boolean name="tapjack" value="true" />
<boolean name="config_default_enablemultiuser" value="false" />
<string name="config_default_access">prompt</string>
<string name="locale"></string>
<boolean name="refresh" value="true" />
<boolean name="config_default_enableduringboot" value="false" />
<string name="config_default_logformat">31122359</string>
<boolean name="config_default_enablemountnamespaceseparation" value="true" />
<boolean name="superuser" value="true" />
<string name="theme">material_dark</string>
<boolean name="reauthenticate" value="true" />
<string name="config_default_logage">14</string>
<boolean name="config_default_trustsystem" value="false" />
<string name="config_default_wait">10</string>
<string name="config_com.speedsoftware.rootexplorer_access">grant</string>
<string name="config_jackpal.androidterm_access">grant</string>
<string name="config_eu.chainfire.flash_access">grant</string>
<string name="config_eu.thedarken.sdm_access">grant</string>
<string name="config_org.adaway_access">grant</string>
<string name="config_in.co.pricealert.apps2sd_access">grant</string>
<string name="config_com.dp.sysmonitor.app_access">grant</string>
<string name="config_com.jrummy.liberty.toolbox_access">grant</string>
<string name="config_com.k2.backup_access">grant</string>
<string name="config_com.seasmind.android.gmappmgr_access">grant</string>
<string name="config_ru.littlevictor.powermenu_access">grant</string>
<string name="config_com.keramidas.TitaniumBackup_access">grant</string>
<string name="config_com.buak.Link2SD_access">grant</string>
<string name="config_de.robv.android.xposed.installer_access">grant</string>
<string name="config_ADB shell_access">grant</string>
</map>
Click to expand...
Click to collapse
Many thanks for this. Just tried and works as advertised. Much better thank blanket granting su access!
Adaway
Thanks for the post. Nice workaround for this issue. I added the Adaway entry but it keeps removing itself from the xml file.
All other entries work great. Not sure what is going on with this. Thanks again.
Thank you for posting this solution. It's worked fine so far for me, except for granting root access for AFWall+, I added <string name="config_dev.ukanth.ufirewall_access">grant</string> to the preferences file, but AFWall+ doesn't show up in SuperSU's Apps tab.
Edit: AFWall+ showed up after rebooting.
This is pretty sweet. I've got it all running, but I have a few questions.
1. On my pixel phone, it has Adaway and Adaway [UID] in the grant list. What is the UID? It also has SuperSu [UID] in the grant list and wondering if that is different?
2. I notice the silently denied entry in the xml file. Any way to use that so that whenever supersu denies a request for root, it gives me a notification or something?
3. I notice you have sdmaid added. Have you gotten SD maid to do any root functions, like freeze another app, turn receivers on and off, etc? Its still not doing anything with root for me, and gives an error in the SuperSu log about the libs not being x64 or something.
4. Here's my xml file (below), it's apps that i sometimes install and i will just have them in supersu grant list so that when i install the app i don't have to mess with the xml file. Does anyone see anything in the other settings that maybe I should change?
I also have a couple tips to share:
1. force close supersu after changing the xml file. then restart supersu. That way, you don't have to reboot.
2. If you don't see your apps *icon* on the grant list, you either don't have the app installed or you made a typo in the package name or formatting. This holds true for every app I've done except for ADB shell - that one does not have an icon.
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<set name="silently_denied_requests" />
<int name="shown_follow" value="1" />
<boolean name="config_default_notify" value="false" />
<int name="last_boot_version" value="282" />
<string name="config_default_log">content</string>
<boolean name="freeload" value="true" />
<string name="icon">material</string>
<boolean name="tapjack" value="false" />
<boolean name="config_default_enablemultiuser" value="false" />
<string name="config_default_access">prompt</string>
<boolean name="refresh" value="true" />
<string name="locale"></string>
<boolean name="config_default_enableduringboot" value="true" />
<boolean name="shown_backup" value="true" />
<string name="config_default_logformat">31122359</string>
<boolean name="superuser" value="true" />
<boolean name="config_default_enablemountnamespaceseparation" value="false" />
<string name="theme">dark</string>
<boolean name="reauthenticate" value="false" />
<boolean name="config_default_trustsystem" value="true" />
<string name="config_default_logage">3</string>
<string name="config_default_wait">10</string>
<string name="config_com.speedsoftware.rootexplorer_access">grant</string>
<string name="config_jackpal.androidterm_access">grant</string>
<string name="config_eu.chainfire.flash_access">grant</string>
<string name="config_eu.thedarken.sdm_access">grant</string>
<string name="config_org.adaway_access">grant</string>
<string name="config_in.co.pricealert.apps2sd.pro_access">grant</string>
<string name="config_com.dp.sysmonitor.app_access">grant</string>
<string name="config_com.jrummy.liberty.toolboxpro_access">grant</string>
<string name="config_com.k2.backup_access">grant</string>
<string name="config_com.seasmind.android.gmappmgr_access">grant</string>
<string name="config_com.antaresone.quickrebootpro_access">grant</string>
<string name="config_com.keramidas.TitaniumBackup_access">grant</string>
<string name="config_com.buak.Link2SD_access">grant</string>
<string name="config_de.robv.android.xposed.installer_access">grant</string>
<string name="config_ADB shell_access">grant</string>
<string name="config_me.kuder.diskinfo.pro_access">grant</string>
<string name="config_com.google.android.diskusage_access">grant</string>
<string name="config_org.freeandroidtools.root_checker_pro_access">grant</string>
<string name="config_nl.leonardsimonse.softreboot_access">grant</string>
<string name="config_org.fdroid.fdroid_access">grant</string>
<string name="config_flar2.exkernelmanager_access">grant</string>
<string name="config_com.grarak.kerneladiutor_access">grant</string>
<string name="config_com.swapit.expander.de_access">grant</string>
<string name="config_com.jumobile.manager.systemapp_access">grant</string>
<string name="config_eu.chainfire.supersu_access">grant</string>
<string name="config_stericson.busybox.donate_access">grant</string>
</map>
mistermojorizin said:
... I have a few questions.
Click to expand...
Click to collapse
1. Every app has a User ID. If you delete the non-UID entry, does everything work as expected? Some discussion of the duplicates issue is here.
2. I think that option is for apps that are in the "deny" list. SuperSU doesn't even prompt for access, so I doubt it will notify you when access is denied.
3. No, it does not (I remember reading something on GitHub from the app developer about the root features being ROM dependent). I use it for its primary purpose (cleaning). Why aren't you using ROM Toolbox to freeze apps and disable receivers?
4. Why do you want to grant su access to apps you haven't installed yet? Leave them at "Prompt" and change to "Grant" from the SuperSU Apps tab as needed. Since these entries are already in your preferences file, you don't have to mess with that file to do this.
Thanks for the info. In response to this, I dont use it for freezing, but I use the freezing ability as a gauge of whether it's actually able to use root at all (because if it's not, why add it to supersu?) and also for compatibility purposes (there might be other apps that won't be compatible if this one isn't compatible).
retyre said:
3. No, it does not (I remember reading something on GitHub from the app developer about the root features being ROM dependent). I use it for its primary purpose (cleaning). Why aren't you using ROM Toolbox to freeze apps and disable receivers?
.
Click to expand...
Click to collapse
Working
I just wanted to say that this method indeed works and it works very well. However, you need to be careful and patient when you try this. I gave up on it the first time I tried it because it didn't seem to work, but when I tried it again and few days later with a bit more diligence it worked beautifully. Some commonsensical suggestions:
1- Make an original backup of the XML file for faster editing in case you mess up the first time.
2- Start with setting the access to "grant" in the superSu app before you edit the XML.
3- Add your entries to the XML and be careful with the syntax especially with config_ and _access before and after the package names.
4- Before closing the XML change the default access to "deny" on the line that says: <string name="config_default_access">grant</string>
5- Reboot and check that your apps work and other su requests are rejected (for example, make sure a root checker program shows your device is unrooted). If that doesn't happen check the XML to make sure your additions are still there, and make sure they are listed under the Apps tab in superSu with access set to grant (with a green hash sign next to them). A few reboots, closing all apps, and some waiting may be needed, but eventually it will work.
6- If it doesn't work start over and follow the steps more carefully. It will eventually work...
"I am sure this information can be found in some forum on XDA with adequate searching, but who wants to do that?"
I WANT to do it, but searching here is a terrible, unrewarding process!
Given the many new posts about SuperSU not prompting, might this be a good time to bump this? Bump first, think later.
I wish someone can write a little app for this
This is working.
1. After forced stop, the App tab will show the new app added without reboot. However, the new app does not take effect until reboot.
2. Any app not yet installed will disappear from the list after reboot.
Can SuperSU 2.7.9 be upgraded to Pro Version in order to get the grant access prompt?
thanks for the guide but how do I find the correct app name that I need to enter?
Hello
Thank you for this useful thread
How can I get the list of applications name ?
(for ex can't get ADB shell when I use pm list packages )
ex :
<string name="config_ADB shell_access">grant</string>
but I can only get this from 'pm list packages' as shell :
package:com.android.shell
How to find the correct APP name to enter
9000RPM said:
thanks for the guide but how do I find the correct app name that I need to enter?
Click to expand...
Click to collapse
After you gain root, the APP name you need to enter is the "FOLDER NAME" of the APP in the /data/data/
directory of your Fire device.
You need a file manager with root access, such as FX, to navigate to the /data/data/ folder in order to find out the correct "FOLDER NAME".
For example, the app "Link2SD" has a folder name :
/data/data/com.buak.Link2SD/
So one enters :
<string name="config_com.buak.Link2SD_access">grant</string>
FOLOL2011 said:
Hello
Thank you for this useful thread
How can I get the list of applications name ?
(for ex can't get ADB shell when I use pm list packages )
ex :
<string name="config_ADB shell_access">grant</string>
but I can only get this from 'pm list packages' as shell :
package:com.android.shell
Click to expand...
Click to collapse
Sometimes the application name is not embedded in the package name. So there are many apps that will show you what you want. An example in the Play Store is "my app list".
sga999 said:
Sometimes the application name is not embedded in the package name. So there are many apps that will show you what you want. An example in the Play Store is "my app list".
Click to expand...
Click to collapse
Thank you! Very useful app