Hi there,
I've posted this already in the launcher 8 thread, but I guess it should've gone here from the start since it's a very specific nook question, so here goes:
I've rooted my nook and am running launcher 8 now, I am on 1.5.2 right now but I've tried newer versions too which still work with the old android system running on the nook. The latest 2.6 and 3.0 versions do not work.
I've ran into a problem though: I don't seem to be able to choose launcher 8 as the default launcher when I press the home button.
Is there anything I can do to solve this?
Some pictures attached just to make clear what my problem actually is.
schelleursli said:
Hi there,
I've posted this already in the launcher 8 thread, but I guess it should've gone here from the start since it's a very specific nook question, so here goes:
I've rooted my nook and am running launcher 8 now, I am on 1.5.2 right now but I've tried newer versions too which still work with the old android system running on the nook. The latest 2.6 and 3.0 versions do not work.
I've ran into a problem though: I don't seem to be able to choose launcher 8 as the default launcher when I press the home button.
Is there anything I can do to solve this?
Some pictures attached just to make clear what my problem actually is.
Click to expand...
Click to collapse
It appears from the photographs that your Nook is not recognizing Launcher8 as a launcher app, but instead as a regular app. Are you able to view Launcher8 from ReLaunch's app drawer?
Thanks for the reply, I guess you mean the "All applications" bit in ReLaunch? Then yes, it's there, thats how I start it at the moment.
I've already tried fiddling with the AndroidManifest.xml but I really don't know what I'm doing.
schelleursli said:
Thanks for the reply, I guess you mean the "All applications" bit in ReLaunch? Then yes, it's there, thats how I start it at the moment.
I've already tried fiddling with the AndroidManifest.xml but I really don't know what I'm doing.
Click to expand...
Click to collapse
Yes, "All applications" is ReLaunch's app drawer.
I don't know exactly how to fix this, but let me do some research, and I'll get back to you.
Check the intent-filter's in AndroidManifest.xml
You probably should see something like this:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You can also try through ADB shell:
Code:
am start -a android.intent.action.MAIN -c android.intent.category.HOME
and see what happens.
Renate NST said:
Check the intent-filter's in AndroidManifest.xml
You probably should see something like this:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You can also try through ADB shell:
Code:
am start -a android.intent.action.MAIN -c android.intent.category.HOME
and see what happens.
Click to expand...
Click to collapse
Thanks for that, I've tried fiddling with the Manifest but I always either get a non working application with an entry in the Home menu or a working application with no entry in the Home menu to choose as default.
If you feel like having a look, this is the default manifest that is in use by launcher 8: pastebin.com/K8BknQuk (I'm not allowed to post links yet)
I do not have the android sdk installed or anything prepared to run ADB on my nook, I'll look into that at some point if the manifest fiddling doesn't work out.
The AndroidManifest.xml looks fine, which is to be expected.
Maybe you "picked" the wrong application at some point?
That's all in /data/system/packages.xml
Check preferred-activities in there.
You can always delete that whole section, as long as you do it cleanly.
Thanks for the continued help. I've had a look at packages.xml preferred-activities looks like this:
Code:
<preferred-activities>
<item name="com.lx.launcher8/.AnallLauncher" match="100000" set="4">
<set name="com.bn.nook.home/.HomeActivity" />
<set name="com.lx.launcher8/.AnallLauncher" />
<set name="com.lx.launcher8/.Home" />
<set name="com.harasoft.relaunch/.Home" />
<filter>
<action name="android.intent.action.MAIN" />
<cat name="android.intent.category.HOME" />
<cat name="android.intent.category.DEFAULT" />
</filter>
</item>
</preferred-activities>
I can turn off my nook and turn it on again then launcher 8 starts by default, but if I press the "n" button on the nook and then press home on the touch-screen I still only get the choice between ReLaunch and the default nook Home. I've also tried completely resetting my device restoring an old unrooted backup then root it again and set it up from scratch, same problem.
I don't have my nook with me (lost it a few days ago) but I seems to remember seeing a nook manager app that can help program what buttons do what, including the N button. You may have to lose the pop up home/library/shop/search/glowlight/setting thing (you could delegate that function to long press N if you want.) but the app should properly program the N button to start up the launcher 8. I THINK it's the Nook Color Tool? I remember the appropriate app came with the 1337 ROM.
Deafcyclist said:
I don't have my nook with me (lost it a few days ago) but I seems to remember seeing a nook manager app that can help program what buttons do what, including the N button. You may have to lose the pop up home/library/shop/search/glowlight/setting thing (you could delegate that function to long press N if you want.) but the app should properly program the N button to start up the launcher 8. I THINK it's the Nook Color Tool? I remember the appropriate app came with the 1337 ROM.
Click to expand...
Click to collapse
Yep, that's Nook Touch Mod Manager. It comes pre-installed with NookManager and my 1337 ROM, but it can also be installed manually with some modified framework-related .jar files.
Thanks for the tip, sounds like a good workaround for now.
edit: I see I need a running build environment for that, will see if I can get this to work on my virtual machine.
edit2: got it working
Oh, the "n" button?
B&N has that hardwired to do some B&N specific intent.
This problem has been solved many different ways.
My solution is to patch where the problem is, com.android.internal.policy.impl.PhoneWindowManager (in android.policy.jar).
This just makes the "n" key a normal Home key.
Code:
apktool d android.policy.jar -o C:\AP
mergesmali /v C:\AP PhoneWindowManager.smali PhoneWindowManager$HomeButtonHandler.smali
apktool b C:\AP -o android.policy.jar
Check the mergesmali link in the signature, a zip of the patches is there too.
No it was the "Home" menu button you open by pressing the "n" button. But with Nook Touch Mod Manager I've managed to change the behaviour of said "Home" even though Launcher 8 still wasn't shown as a choice. Thanks for all the help.
Related
open dialer and enter this code *#*#8736364#*#*
if you use apk manager to decompile an apk and look inside AndroidManifest.xml
you can find all sorts of secret codes but be careful I found one that instantly does a factory format including the internal sd card.
example:
Code:
<intent-filter>
<action android:name="android.provider.Telephony.SECRET_CODE" />
<data android:scheme="android_secret_code" android:host="8736364" />
</intent-filter>
just enclose the numbers with *#*# before the numbers and #*#* after the numbers.
tried it and it didnt update Similar thing was posted in a different thread. Anyone able to get it to update?
it was about 10min before I got a notification that there was an update.
I tried it and think it works. I am unable to receive an update because I have my vibrant on att network. Do you know the correct device manager settings for t-mobile
Sent from my SGH-T959 using XDA App
If you've got one of the ICS roms installed and want more of the market, this worked for me.
edit /etc/permissions/tablet_core_hardware.xml
Below <feature name="android.hardware.screen.landscape" />
add
Code:
<feature name="android.hardware.location.gps" />
<feature name="android.hardware.camera" />
<feature name="android.hardware.camera.autofocus" />
<feature name="android.hardware.camera.autofocus-flash" />
<feature name="android.hardware.camera.front" />
Then goto Settings, Apps, All, Google Services Framework. Force Stop and Clear data.
Reboot
That should enable all the features cept for the phone stuff. After doing this I can find and install Facebook, NFL '11 for Android Tablet, Springpad, Tiny Tower, etc. All the examples I could find of people saying they couldn't install.
If there is an app in the market you can't install, find a copy of the apk and run
Code:
platform-tools/aapt dump badging file.apk
That will give you the list of required features. For example
Code:
uses-feature:'android.hardware.location'
uses-feature:'android.hardware.location.gps'
uses-feature:'android.hardware.location.network'
uses-feature:'android.hardware.microphone'
uses-feature:'android.hardware.touchscreen'
uses-feature:'android.hardware.screen.landscape'
Just add whatever you're missing. Do the force close, clear data, reboot.
Info obtained from here developer.android.com/guide/topics/manifest/uses-feature-element.html
UD.
Wow, that's awesome! That explains why so many apps were "incompatible". This saves us the trouble of hijacking some other devices fingerprint to bypass the problem.
I thought I'd add my 2 cents to your guide though as /etc (/system/etc) is readonly through adb.
Remount the system partition as read-write
$ adb remount
Enter the shell
$ adb shell
Edit your file with your editor of choice
# vi /etc/permissions/tablet_core_hardware.xml
Insert lines and save
Code:
<!-- Fake it 'til you make it! -->
<feature name="android.hardware.location.gps" />
<feature name="android.hardware.camera" />
<feature name="android.hardware.camera.autofocus" />
<feature name="android.hardware.camera.autofocus-flash" />
<feature name="android.hardware.camera.front" />
Then force close Google Services Framework, clear it's cache and reboot.
As for the facebook and twitter apps, you only really need the location.gps line.
Yeah looks like build.prop is irrelevant for market access in ICS. This is a far better way for them to do it. Kinda stupid that apps would be "incompatible" due to gps but that's on the app developers.
Make sure those feature name lines are added inside of the <permissions> tag. Don't just add them to the end of the file.
Within about 2 hours of making this change, the market website updated and everything became compatible so I could also do installs from there.
Oh and could someone with enough post-juice link this thread into bl1nkk's ISC development thread?
To be clear, this is ICS specific right?
Because it would be amazing to not have to screw with build.prop on the stock ROM.
UberDuper said:
Oh and could someone with enough post-juice link this thread into bl1nkk's ISC development thread?
Click to expand...
Click to collapse
Done.
I don't have a stock or cm7 rom installed to test, but looking at the modaco zip file the directory structure and files are there. They're named a little different but it should be easy enough for someone to test. Just add everything to /system/etc/permissions/handheld_core_hardware.xml.
Just make sure anything you add is inside these tags
Code:
<permissions>
</permissions>
Fantastic work! I can get NFL '11 for Tablets. There's one that still eludes me now...
Media Remote for Tablets by Sony.
Anyone have any thoughts?
rmagruder said:
Fantastic work! I can get NFL '11 for Tablets. There's one that still eludes me now...
Media Remote for Tablets by Sony.
Anyone have any thoughts?
Click to expand...
Click to collapse
Yeah, platform-tools/aapt dump badging file.apk
rmagruder said:
Fantastic work! I can get NFL '11 for Tablets. There's one that still eludes me now...
Media Remote for Tablets by Sony.
Anyone have any thoughts?
Click to expand...
Click to collapse
I went and downloaded version 2.1.1 from somewhere and this is the aapt output I get
Code:
package: name='com.Relmtech.RemotePaid' versionCode='19' versionName='2.1.1'
application-label:'Unified Remote Full'
application-label-ja:'Unified Remote Full'
application-label-sv:'Unified Remote Full'
application-icon-120:'res/drawable-ldpi/icon.png'
application-icon-160:'res/drawable-mdpi/icon.png'
application-icon-240:'res/drawable-hdpi/icon.png'
application: label='Unified Remote Full' icon='res/drawable-mdpi/icon.png'
launchable-activity: name='com.Relmtech.Remote2.Activities.MainActivity' label='Unified Remote Full' icon=''
uses-permission:'com.android.vending.CHECK_LICENSE'
sdkVersion:'3'
targetSdkVersion:'9'
uses-permission:'android.permission.INTERNET'
uses-permission:'android.permission.BLUETOOTH'
uses-permission:'android.permission.WAKE_LOCK'
uses-permission:'android.permission.READ_PHONE_STATE'
uses-permission:'android.permission.ACCESS_WIFI_STATE'
uses-permission:'android.permission.VIBRATE'
uses-permission:'com.android.launcher.permission.INSTALL_SHORTCUT'
uses-permission:'android.permission.ACCESS_NETWORK_STATE'
uses-configuration: reqTouchScreen='3'
uses-feature-not-required:'android.hardware.bluetooth'
uses-feature-not-required:'android.hardware.touchscreen'
uses-feature-not-required:'android.hardware.touchscreen.multitouch'
uses-feature-not-required:'android.hardware.touchscreen.multitouch.distinct'
uses-feature-not-required:'android.hardware.wifi'
main
other-activities
other-services
supports-screens: 'small' 'normal' 'large' 'xlarge'
supports-any-density: 'true'
locales: '--_--' 'ja' 'sv'
densities: '120' '160' '240'
That doesn't appear to require any features we don't have. I'll poke at it more later tonight.
That is the tablet version, right? Is there an alternate location to download it while we try to figure out Market? I it IS a free app after all.
Sent from my Xoom using Tapatalk
"handheld_core_hardware.xml" does not seem to exist on the stock ROM.
In the permissions folder there are;
android.hardware.sensor.accelerometer.xml
android.hardware.sensor.light.xml
android.hardware.touchscreen.multitouch.distinct.xml
android.hardware.wifi.xml
android.software.live_wallpaper.xml
com.android.location.provider.xml
platform.xml
Each of the hardware ones list individual hardware features (indicated by their file name).
I wonder if adding some of these other ones to one of these files would allow it to work as you're suggesting (they're all permissions files).
Edit: After testing this, I can confirm it does not work on the stock ROM. At least not with the apps listed above (Facebook, Tiny Tower, etc). Guess it's back to build.prop.
Hey this is awesome! Was hoping a fix for talk on ICS was in these files somewhere but I don't find anything :'(
rmagruder said:
That is the tablet version, right? Is there an alternate location to download it while we try to figure out Market? I it IS a free app after all.
Click to expand...
Click to collapse
After looking again.. What I downloaded is not the right app. If I can find that apk anywhere I can take a look. I'm on the 4th page of google results and I got nothing yet.
You are a god! Google maps working again now too! Thanks heaps.
Sent from Fire
Edit: wrong thread.
Sonic 4 ep1 cant install
Does anyone out there have an Android tablet that will download the APK for Sony Media Remote for Android Tablets so we can install/analyze it?
rmagruder said:
Does anyone out there have an Android tablet that will download the APK for Sony Media Remote for Android Tablets so we can install/analyze it?
Click to expand...
Click to collapse
is it not available via ics ? have it on the market with stock rom
rmagruder said:
Does anyone out there have an Android tablet that will download the APK for Sony Media Remote for Android Tablets so we can install/analyze it?
Click to expand...
Click to collapse
I was able to get it to install from the market using the browser trick.
Code:
bash-3.2# ./aapt dump badging apks/com.sony.seconddisplay.tabletview-1.apk
package: name='com.sony.seconddisplay.tabletview' versionCode='20111221' versionName='3.0.0'
application-label:'Media Remote'
application-label-ja:'Media Remote'
application-label-de:'Media Remote'
application-label-nl:'Media Remote'
application-label-fr:'Media Remote'
application-label-es:'Media Remote'
application-label-it:'Media Remote'
application-label-pt:'Media Remote'
application-label-ru:'Media Remote'
application-label-zh_CN:'Media Remote'
application-label-zh_TW:'Media Remote'
application-icon-160:'res/drawable-mdpi/ic_launcher_bdremote.png'
application: label='Media Remote' icon='res/drawable-mdpi/ic_launcher_bdremote.png'
launchable-activity: name='com.sony.seconddisplay.MainActivity' label='Media Remote' icon=''
sdkVersion:'11'
maxSdkVersion:'13'
targetSdkVersion:'11'
uses-permission:'android.permission.INTERNET'
uses-permission:'android.permission.ACCESS_NETWORK_STATE'
uses-permission:'android.permission.CHANGE_WIFI_MULTICAST_STATE'
uses-permission:'android.permission.ACCESS_WIFI_STATE'
uses-permission:'com.android.browser.permission.READ_HISTORY_BOOKMARKS'
uses-permission:'com.android.browser.permission.WRITE_HISTORY_BOOKMARKS'
uses-permission:'android.permission.VIBRATE'
uses-feature:'android.hardware.wifi'
uses-feature:'android.hardware.touchscreen'
uses-feature:'android.hardware.screen.landscape'
main
other-activities
other-receivers
supports-screens: 'small' 'normal' 'large' 'xlarge'
supports-any-density: 'true'
locales: '--_--' 'ja' 'de' 'nl' 'fr' 'es' 'it' 'pt' 'ru' 'zh_CN' 'zh_TW'
densities: '160'
native-code: 'armeabi'
I'm stumped on this one. It looks like it should work but it's still filtered out in the Market.
UberDuper said:
Code:
maxSdkVersion:'13'
I'm stumped on this one. It looks like it should work but it's still filtered out in the Market.
Click to expand...
Click to collapse
SdkVersion of 11 and maxSdkVersion of 13, means it's only for Honeycomb tablets, 3.0-3.2. ICS is 14-15.
http://developer.android.com/guide/topics/manifest/uses-sdk-element.html
Future versions of Android (beyond Android 2.0.1) will no longer check or enforce the maxSdkVersion attribute during installation or re-validation. Android Market will continue to use the attribute as a filter, however, when presenting users with applications available for download.
Click to expand...
Click to collapse
Oooooh. The only stuff I read about the (min|max)sdkVersion was in relation to bluetooth. Well I guess I can stop looking into that then.
About the Sonic app, does anyone have access to the apk to run and give us the output of
Code:
aapt dump badging sonicapp.apk
Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
(Problems with Google Apps might be solved with editing packages.xml and replacing apks. see EDIT 3 bottom)
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install
Titanium Backup
com.keramidas.TitaniumBackup
OR
ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Go for the Apps list.
on Titanium Backup
Tap Backup/Restore
OR
on ROM Toolbox Lite
Tap App Manager
then Tap All Apps
4.
App which its names written Red are on /system/app on apps list.
5.
Find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
Press Uninstall
if you can't find, swipe left or right - it might be there.
8.
Wait until uninstall finishes...
9.
Reboot Your Phone NOW.
It's Done.
There's a one more step if you want to use them is:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
EDIT 1---------------------------------------------------------------------------------------------
for someone having poor(? disconnects too often) data reception,
please check this thread about build.prop Fast Dormancy:
t t p : / / forum.xda-developers.com/showthread.php?t=1684604
EDIT 2---------------------------------------------------------------------Sept. 21th, 2012
>> Oops, I forgot to tell reboot your phone. also, wrote about steps for titanium
EDIT 3------------------------------------------------------------------------Oct. 1st, 2012
>> Found something weired with Google apps by myself. so I edited again.
due to some reason you can't update or Install some Google apps like Google Play Service, etc.
1.
extract apks from gapps package 20120429
if you don't have it, Google it.
2.
go to recovery.
3.
mount /system/as writable.
4.
replace corresponding apks in system/app/
(Incldue MarketUpdater.apk: if you want to keep Play Store updated. and.. included Play Store App from gapps 20120429 IS OUTDATED.
DO NOT REPLACE GoogleBackupTransport.apk: this shares signature with the ROM's so do not replace it otherwise it will be NOT AVAILABLE on your phone.)
if you extracted the gapps package in folder gapps,
Shift-Click upper folder on tree view.
and open command window here
in command-prompt:
adb push /gapps /system/apps
Replacing apks done however you have more steps to do for replaced apks start working.
(optional)
you can unmount /system/ because you have finished replacing apks.
5.
mount /data/as writable.
6.
pull out packages.xml
in command-prompt:
adb pull /data/system/packages.xml
7.
open packages.xml in text editor
(IMPORTANT: DO NOT SAVE files on windows notepad or something else displays all of lines as single line because lack of UNIX support)
8.
Delete shared-user element has name=com.google.uid.shared.
then save.
you have to delete whole element this might look like:
<shared-user name="com.google.uid.shared" userId="10000">
<sigs count="1">
<cert index="1" />
</sigs>
<perms>
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.youtube" />
<item name="android.permission.INTERNET" />
<item name="com.google.android.providers.gmail.permission.WRITE_GMAIL" />
<item name="android.permission.WRITE_SYNC_SETTINGS" />
<item name="android.permission.BROADCAST_STICKY" />
<item name="com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH" />
<item name="android.permission.VIBRATE" />
<item name="android.permission.GET_ACCOUNTS" />
<item name="android.permission.MASTER_CLEAR" />
<item name="android.permission.SUBSCRIBED_FEEDS_WRITE" />
<item name="android.permission.ACCESS_DOWNLOAD_MANAGER" />
<item name="com.google.android.providers.gmail.permission.READ_GMAIL" />
<item name="android.permission.WRITE_CONTACTS" />
<item name="android.permission.READ_PHONE_STATE" />
<item name="com.android.providers.im.permission.WRITE_ONLY" />
<item name="android.permission.RECEIVE_BOOT_COMPLETED" />
<item name="com.google.android.gtalkservice.permission.SEND_GTALK_DATA_MESSAGE" />
<item name="android.permission.READ_CONTACTS" />
<item name="android.permission.READ_SYNC_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES" />
<item name="android.permission.WRITE_SETTINGS" />
<item name="android.permission.SUBSCRIBED_FEEDS_READ" />
<item name="android.permission.ACCESS_NETWORK_STATE" />
<item name="android.permission.WAKE_LOCK" />
<item name="com.android.providers.im.permission.READ_ONLY" />
<item name="android.permission.WRITE_SECURE_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser" />
<item name="android.permission.CALL_PHONE" />
<item name="com.google.android.gtalkservice.permission.GTALK_SERVICE" />
<item name="com.android.vending.INTENT_VENDING_ONLY" />
<item name="com.google.android.googleapps.permission.GOOGLE_MAIL_SWITCH" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.mail" />
</perms>
</shared-user>
Click to expand...
Click to collapse
9.
put packages.xml back to your phone.
in command-prompt:
adb push packages.xml /data/system/packages.xml
10.
set its permission rw-rw-r-- as it was.
in adb shell:
# chmod 664 /data/system/packages.xml
# chwon system.system /data/system/packages.xml
(optional)
to check permission has set:
# ls -e /data/system/packages.xml (if -rw-rw-r-- is okay first char is for a directory)
11.
Reboot Your Phone NOW.
It's Done.
Fails to install from Play store
AtomosVE said:
Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Tap App Manager
4.
Tap All Apps
Like Titanium, App which its names written Red are on /system/app on apps list.
5.
find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
press Uninstall
8.
wait until uninstall finishes...
It's Done.
There's a one more step if you want to use them:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
Click to expand...
Click to collapse
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Oops, I forgot something..
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
Oh, Forgot to tell rebooting your phone after uninstalled app. Hope you enjoy Facebook
Yowhy said:
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Click to expand...
Click to collapse
Thanks for telling them reboot is need. I was forgot but Now, Corrected
I know of three ways to disable/freeze unwanted apps:
Using the command pm disable PACKAGE_OR_COMPONENT
Titanium Backup Pro
Disable the app through the built-in Application Manager (does not work for all apps)
Here's some details I could find about pm disable: http://www.kpbird.com/2013/05/android-shell-command-pm-package-manager.html
But my question to the community: When an app is disabled/frozen by any of these methods, what keeps track of these? Where is this data stored?
If nobody can answer my question above, then I have a different question: Are there any apps/commands that would allow you to view/log filesystem changes on-the-fly? (goal with this: start this "watcher" app, then disable an app using pm, and figure out what changed).
Thanks!
I found it! After quite some time grepping around, I found that the list of enabled/disabled apps is located here:
/data/system/users/0/package-restrictions.xml
Now, all I need to do is find a way to update this file in bash, without relying on any external programs. I plan to make a flashable zip to run a simple script that searches for each of the following three lines:
Code:
<pkg name="com.wssyncmldm" enabled="1" />
<pkg name="com.LocalFota" enabled="1" />
<pkg name="com.sec.android.fwupgrade" enabled="1" />
And updates each to a "2".
If any of the three lines are not found, the script should add them near the end of the file, on new lines immediately before this one:
Code:
<preferred-activities />
One more thing: it's possible that a person might have multiple user accounts on their phone (seems rare...), there could be other package-restrictions.xml files in other directories (maybe a /data/system/users/1/ or example). It would be ideal if the script could search for other user accounts and make the same modifications.
Any scripting-heroes willing to make this up for me??
BTW: the point/purpose of this is to disable the OTA updates from a flashable zip, in a custom recovery, without requiring a rooted system.
Aou said:
I found it! After quite some time grepping around, I found that the list of enabled/disabled apps is located here:
/data/system/users/0/package-restrictions.xml
Now, all I need to do is find a way to update this file in bash, without relying on any external programs. I plan to make a flashable zip to run a simple script that searches for each of the following three lines:
Code:
<pkg name="com.wssyncmldm" enabled="1" />
<pkg name="com.LocalFota" enabled="1" />
<pkg name="com.sec.android.fwupgrade" enabled="1" />
And updates each to a "2".
If any of the three lines are not found, the script should add them near the end of the file, on new lines immediately before this one:
Code:
<preferred-activities />
One more thing: it's possible that a person might have multiple user accounts on their phone (seems rare...), there could be other package-restrictions.xml files in other directories (maybe a /data/system/users/1/ or example). It would be ideal if the script could search for other user accounts and make the same modifications.
Any scripting-heroes willing to make this up for me??
BTW: the point/purpose of this is to disable the OTA updates from a flashable zip, in a custom recovery, without requiring a rooted system.
Click to expand...
Click to collapse
I could probably make a flashable zip that replaces package-restrictions.xml with a modified version that disables OTA
do you have that file?
the bash script looking for and replacing lines is not possible AFAIK via recovery.
jetlitheone said:
I could probably make a flashable zip that replaces package-restrictions.xml with a modified version that disables OTA
do you have that file?
the bash script looking for and replacing lines is not possible AFAIK via recovery.
Click to expand...
Click to collapse
Well, I've done this sort of thing in MS-DOS batch, using For loops (reading the file, line-by-line and processing it). I'll have to look into the bash equivalent.
Also, simply replacing the file is far too dangerous. If any entries in that file mismatch what's installed on the system, the device will not boot properly (TouchWiz launcher will not load, for one). Every time you enable/disable an app, the entire file shifts around and changes. It's a nightmare. But dealing with it line-by-line would be feasible...
Aou said:
Well, I've done this sort of thing in MS-DOS batch, using For loops (reading the file, line-by-line and processing it). I'll have to look into the bash equivalent.
Also, simply replacing the file is far too dangerous. If any entries in that file mismatch what's installed on the system, the device will not boot properly (TouchWiz launcher will not load, for one). Every time you enable/disable an app, the entire file shifts around and changes. It's a nightmare. But dealing with it line-by-line would be feasible...
Click to expand...
Click to collapse
Yeah I know what you mean I don't know it might be possible. Only thing I know of is applications that run bash scripts on boot up. But not of running one via a flashable zip in recovery
Sent from my SGH-I337 using Tapatalk 4 Beta
Based on some of the flashable zips out there, I think it's possible to use busybox to execute a bash script. I came up with a little bit of crappy psuedocode for what needs to happen:
Code:
set foundFlag = 0
if (file exists: /system/app/<app>.apk) do:
for (each line of package-restrictions.xml) do:
if ( line = <pkg name="com.wssyncmldm" enabled="1" /> ) do:
echo <pkg name="com.wssyncmldm" enabled="2" /> into newfile
set foundFlag = 1
else do:
echo line into newfile
end if
end for
if (foundFlag != 1) do:
for (each line of package-restrictions.xml) do:
if ( line = <preferred-activities /> ) do:
echo <pkg name="com.wssyncmldm" enabled="2" /> into newfile
echo <preferred-activities /> into newfile
else do:
echo line into newfile
end if
end for
end if
move newfile -> package-restrictions.xml
end if
The above would need to be repeated 3 times for the 3 apk's that need to be disabled.
.
To anyone who has installed Kitkat XXUFNAD and lost write access to their SDcard, here is a solution.
I am not the original person who found this solution , I'm just putting it together here to help others.
You need root access to do this, of course.
1. Use something like root explorer to to go to the root folder
2. From there go to folder system/etc/permissions
3. Look for file called "platform.xml"
4. Edit this file ( your editor should open it in R/W mode )
5. Locate the following line :
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
6. Add this line " <group gid="media_rw" />", so you get
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
7. Save the file
8. Reboot
You should now have WRITE access back for your SDcard.
I have done this on my i9505 snapdragon without any issue.
All the usual caveats apply ie I not responsible etc etc
I can only assume that when Samsung release the official version, they will put this feature back.One of the fundamental reason I have bought and stayed with Samsung is because of the SDCARD possibility.
sohotha said:
To anyone who has installed Kitkat XXUFNAD and lost write access to their SDcard, here is a solution.
I am not the original person who found this solution , I'm just putting it together here to help others......
I can only assume that when Samsung release the official version, they will put this feature back.One of the fundamental reason I have bought and stayed with Samsung is because of the SDCARD possibility.
Click to expand...
Click to collapse
Good, good, I feel that the Force is strooong in you, young padawan. But, still the learning need you. It will be a day, when the force will allow you to be able with understanding to read, and to search.
But you are not patiently waiting until your abilities will grow I see. Into the dark side it will take you, I feel.
For the next time, instead to rediscover the America, please read the General section. Doing such, this old info you will find.
And now return to the Jedi practice with sword I recommend you to get stronger force control I ask you.
:laugh::laugh:
spamtrash said:
Good, good, I feel that the Force is strooong in you, young padawan. But, still the learning need you. It will be a day, when the force will allow you to be able with understanding to read, and to search.
But you are not patiently waiting until your abilities will grow I see. Into the dark side it will take you, I feel.
For the next time, instead to rediscover the America, please read the General section. Doing such, this old info you will find.
And now return to the Jedi practice with sword I recommend you to get stronger force control I ask you.
:laugh::laugh:
Click to expand...
Click to collapse
Yes .. yes.. I find myself too impatient to look for the ways of the power of the "SEARCH" on my path to enlightenment ...:crying:
sohotha said:
Yes .. yes.. I find myself too impatient to look for the ways of the power of the "SEARCH" on my path to enlightenment ...:crying:
Click to expand...
Click to collapse
:good:
Camera not working after this tweak