Related
So I wanted VoiceDialer on my stock ADP1. I grabbed VoiceDialer.apk from JFv1.31_ADP1.zip and installed it using adb (sdcard mounted on computer, so it wasn't mounted on the phone). It runs, and I was quite satisfied with its recognition abilities, but when it comes to clicking "OK" to dial, it always crashes with a "force close" dialogue. Holding the "send" button does bring up the VoiceDialer program. My guess is I'm missing some sort of configuration somewhere. Does anyone know?
Make sure you grabbed the VoiceDialer.odex too, if there is one.
Koush said:
Make sure you grabbed the VoiceDialer.odex too, if there is one.
Click to expand...
Click to collapse
I didn't find any odex files (unless they would be in recovery.img, which I haven't yet learned how to open). These files are not created automatically?
Unzip a RC30 update.zip and look in \system\app\
On ADP1, the dex is created at runtime by the dalvikvm from the classes file inside the zip. On RC30, the dex files for the builtin apps are created ahead of time and stored alongside the apk. This prevents the system from using up \data partition space with dex files (As the ADP1 build does).
jashsu said:
Unzip a RC30 update.zip and look in \system\app\
On ADP1, the dex is created at runtime by the dalvikvm from the classes file inside the zip. On RC30, the dex files for the builtin apps are created ahead of time and stored alongside the apk. This prevents the system from using up \data partition space with dex files (As the ADP1 build does).
Click to expand...
Click to collapse
I was able to find a copy of VoiceDialer.odex as per your description, but if I understand you correctly, that will not solve my problem.
If the dev phone uses dex files instead, and these are created at runtime, then I would expect to find a dex file for VoiceDialer if everything is working properly. Indeed, the file "[email protected]@[email protected]" exists.
Any other hints as to why the application might crash after clicking "OK" to dial a number?
Yeah just grab the VoiceDialer.apk from JF's modified ADP1 build. It contains the classes.dex file required to run on ADP1 build.
jashsu said:
Yeah just grab the VoiceDialer.apk from JF's modified ADP1 build. It contains the classes.dex file required to run on ADP1 build.
Click to expand...
Click to collapse
That's what I did initially. That part all seems to work.
Doh, went around in a circle ;-) I thought we were talking about the RC30 version.
Yeah you'll have to ask JF about this since I think he compiled VoiceDialer from source for his ADP mod build. There is no odex file to look for.
jashsu said:
Yeah you'll have to ask JF about this since I think he compiled VoiceDialer from source for his ADP mod build.
Click to expand...
Click to collapse
Yeah, I'm sure JF could see the problem real quick. I'm real timid about bothering people, though - I was hoping he might swing by this thread by chance. What's considered appropriate on this forum: PM? E-mail? IM? Visitor Message?
IMSargon said:
Yeah, I'm sure JF could see the problem real quick. I'm real timid about bothering people, though - I was hoping he might swing by this thread by chance. What's considered appropriate on this forum: PM? E-mail? IM? Visitor Message?
Click to expand...
Click to collapse
Your best bet is IRC. A lot of us hang out in #android on Freenode.
IMSargon said:
So I wanted VoiceDialer on my stock ADP1. I grabbed VoiceDialer.apk from JFv1.31_ADP1.zip and installed it using adb (sdcard mounted on computer, so it wasn't mounted on the phone). It runs, and I was quite satisfied with its recognition abilities, but when it comes to clicking "OK" to dial, it always crashes with a "force close" dialogue. Holding the "send" button does bring up the VoiceDialer program. My guess is I'm missing some sort of configuration somewhere. Does anyone know?
Click to expand...
Click to collapse
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.
JesusFreke said:
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.
Click to expand...
Click to collapse
Yeah, I had the same problem (I've installed voice dialer using adb install)
Uninstalled in application manager, rebooted, remounted, pushed voicedialer.apk to /systemp/app, rebooted again, and it worked )
JesusFreke said:
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.
Click to expand...
Click to collapse
It worked! Great! Thanks a ton!
------------------------------
Steps taken:
1. copy VoiceDialer.apk to phone
# adb push VoiceDialer.apk /sdcard/VoiceDialer.apk
763 KB/s (51125 bytes in 0.065s)
#
2. enter shell on phone, and gain root
# adb shell
$ su
#
3. mount the system partition as rewritable
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#
4. copy VoiceDialer.apk to the proper system directory
# cat /sdcard/VoiceDialer.apk > /system/app/VoiceDialer.apk
#
5. make permissions match the other files
# chmod 644 /system/app/VoiceDialer.apk
#
6. reboot the phone
# reboot
------------------------------
For extra credit, does anyone understand why this happens? What does it tell us about how apps work and install?
adb pushing the apk directly bypasses the PackageManager. By using adb install, the package manager will run (as if the package was installed from the Market or Browser). There are various reasons the PackageManager might reject a package, including inability to run dexopt, incompatibility with existing data registered to an older version of an app, etc. A list of errors that would block an apk installation is here. Look at the constants starting with INSTALL_FAILED and INSTALL_PARSE_FAILED.
jashsu said:
adb pushing the apk directly bypasses the PackageManager. By using adb install, the package manager will run (as if the package was installed from the Market or Browser). There are various reasons the PackageManager might reject a package, including inability to run dexopt, incompatibility with existing data registered to an older version of an app, etc. A list of errors that would block an apk installation is here. Look at the constants starting with INSTALL_FAILED and INSTALL_PARSE_FAILED.
Click to expand...
Click to collapse
Interesting, but in this case the application did not fail to install. The installation went normally, and the application functioned normally up to the point where it attempted to interface with another application/subsystem (whatever dials the phone).
IMSargon said:
Interesting, but in this case the application did not fail to install. The installation went normally, and the application functioned normally up to the point where it attempted to interface with another application/subsystem (whatever dials the phone).
Click to expand...
Click to collapse
When you install it with adb install, it gets installed as a normal (non-system) application. This can be verified by checking /data/system/packages.xml:
Code:
<package name="com.android.voicedialer" codePath="/data/app/VoiceDialer.apk" [B]system="false"[/B] ts="1232083952000" userId="10029">
<sigs count="1">
<cert index="0" />
</sigs>
</package>
One of the permissions it requires is "android.permission.CALL_PRIVILEGED". Based on the info in frameworks/base/core/res/AndroidManifest.xml (in the git source):
Code:
<permission android:name="android.permission.CALL_PRIVILEGED"
android:label="@string/permlab_callPrivileged"
android:description="@string/permdesc_callPrivileged"
[B]android:protectionLevel="signatureOrSystem"[/B] />
You can see the protectionLevel is "signatureOrSystem", meaning that the application has to be a system application in order to use that permission. Since the voice dialer was not installed as a system application, it can't be assigned that permission.
To confirm this, I tried installing the voice dialer with adb install, and then took a look at the logcat output, which contains the following line:
Code:
01-15 23:32:32.903: WARN/PackageManager(56): Not granting permission android.permission.CALL_PRIVILEGED to package com.android.voicedialer (protectionLevel=3 flags=0x44)
However, when you copy the apk to /system/app, it gets installed as a system application, which can be verified again by looking at /data/system/packages.xml:
Code:
<package name="com.android.voicedialer" codePath="/system/app/VoiceDialer.apk" [B]system="true"[/B] ts="1232084484000" userId="10035">
<sigs count="1">
<cert index="0" />
</sigs>
</package>
So it is able to use the "android.permission.CALL_PRIVILEGED" permission. After coping the apk to /system/app, I checked the logcat output and there was no mention of not being able to grant the android.permission.CALL_PRIVILEGED permission, as expected.
Interestingly enough, copying the file to /system/app doesn't bypass the package manager. The package manager is watching both /data/app and /system/app for new files, and it automatically installs anything you copy into either location. It also does an uninstall when you delete an apk from either location.
JesusFreke said:
Interestingly enough, copying the file to /system/app doesn't bypass the package manager. The package manager is watching both /data/app and /system/app for new files, and it automatically installs anything you copy into either location. It also does an uninstalls when you delete an apk from either location.
Click to expand...
Click to collapse
I didn't know that. In that context it does make sense why it would disallow call permission if put into /data/app
Offtopic, but are you planning on creating a modified version of the newly released ADP1 "1.1" build?
Thanks, JF, your explanation makes the problem quite clear!
I've removed a bunch of the crap apps that come pre-installed on the Galaxy, however the stupid icons still show up in my app menu. Anyone know how to get rid of these icons??
You can make a custom app draw and place the apps in the order you want. Not sure if you can fully remove an icon but you could create another page and place them all on that.
Edit: How did you remove the stock junk? I've looked in the Setting > apps menu but uninstall was grayed out.
you need to r00t it then use adb shell goto data>app> then use the rm -r command to remove anything u don't want....
I don't know how to create a custom app drawer, can you elaborate?
There has to be a better solution than that btw, anyone else?
open app draw > menu > view type > customizable grid > puts you back at app draw.
Menu > edit > move app icons at will and create multiple pages, pages can have as many for as few icons as you chose.
I have removed these so far from /system/app:
AccountAndSync.apk
AddToHome.apk
Avatar.apk
BuddiesNow.apk
DualClock.apk
DualClock.odex
Email.apk
Email.odex
GoGo.odex
KindleStub.apk
MediaHub.apk
MobiTV.apk
MyAccountStub_4-5-10.apk
Swype-Tips.apk
Telenav.apk
vvm-signed.apk
how did you get them to delete? when i do rm -r BuddiesNow.apk i get a permissions denied
Mookie_Jones said:
how did you get them to delete? when i do rm -r BuddiesNow.apk i get a permissions denied
Click to expand...
Click to collapse
You need to be root.
Mookie_Jones said:
how did you get them to delete? when i do rm -r BuddiesNow.apk i get a permissions denied
Click to expand...
Click to collapse
1. Grab ADB from the SDK from Google and put the tools dir somewhere easy to access via command line
2. Install the USB drivers (I had to install 3 drivers)
3. Root the phone
4. CMD to wherever you put the tools directory
5. Run "adb remount"
6. Run "adb shell"
7. (inside of the shell) "su" to root (only if you get a $ prompt, if you have a # prompt skip this step)
8. "cd /system/app"
9. Delete the above apk's
Do not enter any quotes above, only enter the command inside of the quotes.
Any suggestions on any other apk's to delete?
Simply reboot! That's all I did after I removed a bunch of apk and none of the icons show up anymore
I removed them and now it tells me that my camera doesn't work.
Sent from my SGH-T959 using XDA App
t1n0m3n said:
1. Grab ADB from the SDK from Google and put the tools dir somewhere easy to access via command line
2. Install the USB drivers (I had to install 3 drivers)
3. Root the phone
4. CMD to wherever you put the tools directory
5. Run "adb remount"
6. Run "adb shell"
7. (inside of the shell) "su" to root (only if you get a $ prompt, if you have a # prompt skip this step)
8. "cd /system/app"
9. Delete the above apk's
Do not enter any quotes above, only enter the command inside of the quotes.
Any suggestions on any other apk's to delete?
Click to expand...
Click to collapse
just wanted to post an alt method for those that dont like adb (we're out here, i have yet to install the drivers for this phone lol
Alt Method
1. If you’re rooted, purchase Root Manager (a must have tool for rooted androids)
2. Open Root Manager
3. Select System apps
4. Select App Remover
5. Seleck .apk files you don’t want and remove them.
6. Reboot the phone immediately after
7. Now go to menu
8. settings
9. manage applications
10. you will see apps that have their long name/path name “com.xxxx.xxxx.xxxx” and no icons
11. those are the remnants of the apk files you used to have which were locked (hence needing Root Manager)
12. uninstall these like you would any other non OEM/3rd Party app
13. You should be done!
)
i've removed telenav, mobitv, amazon mp3, and slacker radio so far
Let me know if this works for you guys or if i've missed anything (i am here to learn from this great community as well)
P.S. I had a hard time with Slacker Radio because i deleted the .apk as mentioned above but still had app in the app drawer and it still launched when i selected the icon. Turns out, I had updated it with AppBrain. When i went to uninstall Slacker through manage applications, it removed the update first then gave me a "uninstall unsuccessful". However when i went back to the list of apps, it did remove the icon and revert to "com.slacker.radio" in the apps list, then i went in to uninstall that and it worked fine. So, if any apps have updates on top of "factory", keep that in mind
I have noticed that the slacker radio and layar from samsung/TMO are quite gimped and don't really function very well. They seem to be tied to TMO and wants to charge your TMO account monthly for something. (I didn't really look close, I got to the "we want to charge your account" part and canceled.) I deleted them from the phone and then went to the market and downloaded the "real" apps... Yeah, there is none of that crap on the real apps.
>:-(
Most of the other TMO/Samsung apps did this as well, but I deleted most of them pronto. So if you want to use layar or slacker radio... Do yourself a favor and delete them, and grab them from the market.
I actually use Amazon MP3, so I kept that one.
When, oh when do the CMs a come!? Get along little doggy. Yehaw. *Bullwhip* (Yay, we got Cyanogen!)
I'm just uninstalling them with Titanium Backup (root needed). Things that I think I MAY want back, I just back up... I found that some after uninstalling, you can see in Settings->Applications->Manage, right under 3rd party at 0 bytes. I just uninstalled from there and it appears it removed all traces.
Note: Titanium Backup is acting flaky with restores, apps go back but it FC's before restoring data. Then I have to go back and restore data only. I felt better just reinstalling from market then restoring data only from TB. But that is another thread
could someone tell me what these apk are?
MyAccountStub_4-5-10.apk
vvm-signed.apk
My list of backed up and removed files are
AccountAndSync.apk & odex
Amazon apk
Avatar.apk & odex
AddToHome.apk & odex
DualClock.apk & odex
Email.apk & odex
Infoalarm.apk & odex (daily briefing)
KindleStub.apk
layar-samsung.apk
MediaHub.apk
Memo.apk & odec
MiniDiary.apk & odec
Myfiles.apk & odex
slackerradio.apk
Telenav.apk
Writeandgo.apk & odec
I will probably take out most of the sammy widgets and some of the dull live wallpapers also. Will report back if there are any issues but they all came from other people's "safe" lists. (thanks Jonas.M and t1n0m3n)
SykesAT said:
could someone tell me what these apk are?
MyAccountStub_4-5-10.apk
vvm-signed.apk
My list of backed up and removed files are
AccountAndSync.apk & odex
Amazon apk
Avatar.apk & odex
AddToHome.apk & odex
DualClock.apk & odex
Email.apk & odex
Infoalarm.apk & odex (daily briefing)
KindleStub.apk
layar-samsung.apk
MediaHub.apk
Memo.apk & odec
MiniDiary.apk & odec
Myfiles.apk & odex
slackerradio.apk
Telenav.apk
Writeandgo.apk & odec
I will probably take out most of the sammy widgets and some of the dull live wallpapers also. Will report back if there are any issues but they all came from other people's "safe" lists. (thanks Jonas.M and t1n0m3n)
Click to expand...
Click to collapse
couple of noob questions for you, that addtohome thing, if you uninstall that, what happens when you long press on an empty space on a home screen? launching addtohome brings up the same menu as a long press so i was wondering. Also what are the .odex files and what do they do?
jblade1000 said:
couple of noob questions for you, that addtohome thing, if you uninstall that, what happens when you long press on an empty space on a home screen? launching addtohome brings up the same menu as a long press so i was wondering. Also what are the .odex files and what do they do?
Click to expand...
Click to collapse
long press on home screen brings up.... add to home menu
I believe removing that apk just removes the icon in the app draw, Similar to the Avatar APK which is also just an icon with a link... Not too sure about odex but read they should be removed also. When I "removed" items it was more move to a backup folder on the SD card just incase.
Jeez, I found another one. The kindle app (which I use) was not uninstallable. It had a "remove updates" button instead. I click on remove updates, and it basically uninstalled the app, but left all of the shortcuts on the home screen and the app menu orphaned.
I had to install it from the market, uninstall it from the market, and install it from the market again to get it working correctly. Now I have a proper "uninstall" button and market updates for this app.
It seems to me like every T-mobile/Samsung pre-installed app has something wrong with it. I can't wait until we get a real rom for this phone.
SykesAT said:
could someone tell me what these apk are?
MyAccountStub_4-5-10.apk
vvm-signed.apk
Click to expand...
Click to collapse
vvm-signed.apk - T-Mobile's Visual Voice Mail (If you use this, I recommend deleting this version and installing from the market instead.)
All of the stubs are basically shortcuts to the market to install the real apps. That one is the stub to install the T-Mobile "My Account" app. I removed all of the stubs. They just get in the way IMO.
jblade1000 said:
couple of noob questions for you, that addtohome thing, if you uninstall that, what happens when you long press on an empty space on a home screen? launching addtohome brings up the same menu as a long press so i was wondering. Also what are the .odex files and what do they do?
Click to expand...
Click to collapse
The addtohome apk just puts a shortcut in the app tray to bring up the same menu as when you long press the background. I found it annoying, so I removed it. Removing it does not effect the menu that pops up when you long press an empty space on the home screen.
As I understand it, Odex files are there to speed up boot and to lessen the dalvik-cache usage a bit.
T1n0m3,
thanks again vvm and myact are removed myact added back from market, use GV for VM.
So its correct and safe to delete the the odex files of any apk you've removed?
Hi,
First of all is it possible?
If it is, has anyone tried to extract Swype from Telstra's RUU and install it in another Wildfire?
Tried extracting the installer but was unsuccessful.
Thanks in advance
I've tried to extract (and was successful), but when I tried to execute it gave me a FC. I guess it was because libSwypeCore.so was not in the /system/lib folder.
Like busybox in my other thread, every time I tried it gave an error.
Something like:
# ./busybox cp /sdcard/libSwypeCore.so /system/lib/
cp: can't create '/system/lib/libSwypeCore.so': Cannot allocate memory
# cd /system/lib
# cat /sdcard/libSwypeCore.so > libSwypeCore.so
cannot create libSwypeCore.so: not enough memory
# mv /sdcard/libSwypeCore.so /system/lib
failed on '/sdcard/libSwypeCore.so' - Cross-device link
# dd if=/sdcard/libSwypeCore.so of=/system/lib/libSwypeCore.so
/system/lib/libSwypeCore.so: cannot open for write: Out of memory
I really need to know how to copy files to the /system folder.
http://rapidshare.com/files/419489818/swype-telstra.zip
MD5: BDE9ACBCFD58AD39EC11A4859ADEBE3B
Ok I think I found a way
Just edit the APK and put the libSwypeCore.so in the lib/armeabi folder, zip the files and sign the APK.
It runs nice and no FC I will edit the APK (again) to include the Portuguese language.
Could u please upload it
Sent from my HTC Wildfire using XDA App
@ricardoft : Edited the Swype.apk
Put the libSwypeCore.so
Under
Swype.apk
->Lib
---|>armeabi
---------|> libSwypeCore.so
Is this right ? repacked the apk as above attached with the post.
I got "application not installed" as error message
I wonder how to repack it then :|
I am using the 1.54 Version for QVGA , Works fine in Portrait mode , hides some keys in Landscape.
I've been busy with the University but here is the modified APK.
http://rapidshare.com/files/419569794/Swype-signed.apk
MD5: 56338F5EE8D53BE3A22EFE6CB96E1A7C
It still has some issues. One of them is when choose Swype for the Input Method it still crash. Don't know why, but I think it still has something to do with the libSwypeCore.so.
i wouldnt mind doing this as i basically paid for it when i bought the phone...
using a clockwork backup i was able to extract the apk and libSwypeCore.so
butwhen i put the lib in place and installed the apk i just get blue flashing outline of keyboard and no output text...
I am wondering if someone would make a list of system apps that would be safe to remove.I know I can remove pulse because ive done it before.
http://forum.xda-developers.com/showthread.php?t=1411953
Thanks for the link
Rooted and with superuser.apk.
All I have removed.(Just necessary apps left, in basis of stock 6.2.2)
amazonmp3-unsigned.apk -- Music player
AmazonVenezia.apk -- Amazon app store
ATVAndroidClient.apk -- Video player
AudibleAndroidApplication-venezia.apk -- Audible book
CalendarProvider.apk -- Calendar
Cloud9-release-unsigned.apk -- Amazon browser
Cloud9SystemBrowserProvider-unsigned.apk-- Amazon browser
com.amazon.dcp.apk -- About Amazon registration
Contacts.apk -- Contact
ContactsProvider.apk -- Contact
CSApp-unsigned.apk -- Amazon app
DownloadProvider.apk --
DownloadProviderUi.apk --
Email.apk -- email
Facebook.apk
IMDb-2.3.apk -- Movies
KindleForOtter.apk -- kindle book read app
LatinIME.apk XXX Only after you install another input app, this is the original input app
Launcher.apk XXX Only after you install another launcher app
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
oem_install_flash_player_signed.apk -- Don't remove it if you want to see adobe flash in browser
OOBE-unsigned.apk -- Kindle reader component
OtterTutorial.apk -- Kindle manual
OTASilentInstall.apk -- Kindle On The Air update app
PicoTts.apk -- Text To Speech
Pulse-amazon.apk -- News reader app
Quickoffice_AMAZON_4.1.467_VC.apk -- Office component
QuickSearchBox.apk
TtsService.apk -- Text To Speech
VisualizationWallpapers.apk
Windowshop.apk
My suggestion is :
create a folder named "app_backup" under /system, then move the above into it.
While your KF cannot startup, you can use following adb commands to restore apps.
Win7 32bit code:
c:\adb\adb shell
>su
>mv /system/app_backup/*.* /system/app
My apps installed.
Opera browser
Root Explorer
ES explorer
Good luck!
SOLVED
I wanted a completely clean ROM to start developing on. I have looked at CleanROM, but it has too many system apps.
These are the system APKs the ROM is currently running with.
Code:
ApexLauncher.apk
Bluetooth.apk
CertInstaller.apk
ConfigUpdater.apk
DefaultContainerService.apk
DownloadProvider.apk
DownloadProviderUi.apk
FusedLocation.apk
HTMLViewer.apk
InputDevices.apk
KeyChain.apk
LatinImeDictionaryPack.apk
LatinImeGoogle.apk
MediaProvider.apk
MediaUploader.apk
Nfc.apk
PackageInstaller.apk
Settings.apk
SettingsProvider.apk
Superuser.apk
SystemUI.apk
UserDictionaryProvider.apk
XT9IME.apk
Honestly the stock Nexus 7 build is pretty damn clean.
If you want to experiment with disabling APKs, try the built-in disable functionality in Settings / Applications / All. Any system app that can be safely disabled (and some that can't) will have a Disable button. This is safer to try out than zapping apk files yourself. If something goes wrong after disabling an app, you'll know you need it back.
I have narrowed down the APKs and it is working fine, but now the middle home navigation button doesn't do anything. I suspect it is one of the google search apps that I deleted, but which one? I always assumed the navigation bar was handled by systemUI. :/
Forty.Two said:
I have narrowed down the APKs and it is working fine, but now the middle home navigation button doesn't do anything. I suspect it is one of the google search apps that I deleted, but which one? I always assumed the navigation bar was handled by systemUI. :/
Click to expand...
Click to collapse
Did you disable the launcher by accident?
Also I have heard that the OS immobilizes the home button until initial device setup is complete and then lets it work. Maybe it has something to do with that.
Thanks!
cmstlist said:
Did you disable the launcher by accident?
Also I have heard that the OS immobilizes the home button until initial device setup is complete and then lets it work. Maybe it has something to do with that.
Click to expand...
Click to collapse
It was the setupwizard.apk! I deleted it to make changes too the ROM faster.
It makes perfect sense too. The power menu had limited options, the battery drop down bar was gone, and the home button wasn't working. Just like during the setup!
This is what I did to bypass the setupwizard.apk when it start up:
1. Launch adb shell
2. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
3. Exit shell and issue an adb reboot.
4. Delete setupwizard.apk if you want
Now the ROM works fine with only 23 APK files in the /system/apps folder! That is a great improvement compared to the original 85.