Related
a few days ago i mentioned that i kept getting a force close in the martket and i couldnt install any app from it
i did several wipes and noticed as soon as i apply the dark facebook or transparent facebook widget, i get the force close on the market.
so i think that is the problem.
anyone else facing this?
can someone check if the same thing happens with them?
however this issue is resolved when i uninstall updates from market using application manager. but i have to do that everytime i want to install an app from the market.
what morph are u using
all of these cause the same problem for me:
http://forum.xda-developers.com/showthread.php?t=652661
http://forum.xda-developers.com/showthread.php?p=6325029#post6325029
Did you apply any morph that modified framework-res.apk ?
I've noticed that sometimes it screws up the UIDs and the Market app loses the PACKAGE_INSTALL permission.
Only way out I've found is to restore your most recent nandroid backup.
I'm sure theres a manual way to fix this (if this is even your issue), but havent found instructions yet.
Its likely not this facebook morph as it includes only images and xml, and cannot affect any other part of the system.
Post your logcat around the time the market force closes.
britoso said:
Did you apply any morph that modified framework-res.apk ?
I've noticed that sometimes it screws up the UIDs and the Market app loses the PACKAGE_INSTALL permission.
Only way out I've found is to restore your most recent nandroid backup.
I'm sure theres a manual way to fix this (if this is even your issue), but havent found instructions yet.
Its likely not this facebook morph as it includes only images and xml, and cannot affect any other part of the system.
Post your logcat around the time the market force closes.
Click to expand...
Click to collapse
yes i did apply themes that modify framework-res
how can i post a log of this as you mentioned?
can you tell me how to get the log from my phone?
1. open a command shell. Start-run-cmd
2. Type in: adb logcat
3. On your phone, wait til you get the error, click close
4. On the command shell press control-c to stop.
5. Select the part that contains the error. You may have to use the top right window button to choose edit-mark and then edit-copy
6. Paste the log here or better still on www.pastebin.com
try this
http://forum.xda-developers.com/showthread.php?t=673870
This works but I have to do it everytime I want to install an application
britoso said:
1. open a command shell. Start-run-cmd
2. Type in: adb logcat
3. On your phone, wait til you get the error, click close
4. On the command shell press control-c to stop.
5. Select the part that contains the error. You may have to use the top right window button to choose edit-mark and then edit-copy
6. Paste the log here or better still on www.pastebin.com
Click to expand...
Click to collapse
thanks for this
now since i've uninstalled updates, i didnt get any force closes
i'll keep checking, if i do get one, i'll post the logcat here
thanks for your help!!
This is just a thread to get this started, I know a lot of people hate the sense dialer and want to change. I also know that AOSP dialer/contacts has been put into custom roms. What we need to do is make something where people can put the AOSP dialer/contacts into stock without too much trouble.
I don't have any help to include but I'd be interested in this as well. I love the AOSP style contacts/phone app.
Can you not simply do an adb install mms.apk and install an AOSP MMS handler? Both should use implicit intents, so when "launching" a messaging application, Android should ask you how to handle the action--and theoretically let you choose "MMS" every time.
Have you given that a shot?
EDIT: I can't test as I'm running an early build of Froyo.
EDIT 2: Attached Mms.apk from Eclair. Try placing it in C:\Mms.apk and do the following from the terminal:
adb install C:\mms.apk
with the hero all i did was push them to the system app folder and reset default.
Shidell said:
Can you not simply do an adb install mms.apk and install an AOSP MMS handler? Both should use implicit intents, so when "launching" a messaging application, Android should ask you how to handle the action--and theoretically let you choose "MMS" every time.
Have you given that a shot?
EDIT: I can't test as I'm running an early build of Froyo.
EDIT 2: Attached Mms.apk from Eclair. Try placing it in C:\Mms.apk and do the following from the terminal:
adb install C:\mms.apk
Click to expand...
Click to collapse
adb install Mms.apk
1067 KB/s (263733 bytes in 0.241s)
pkg: /data/local/tmp/Mms.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Also, that's for MMS, we're wanting dialer/contacts
mrono said:
adb install Mms.apk
1067 KB/s (263733 bytes in 0.241s)
pkg: /data/local/tmp/Mms.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Also, that's for MMS, we're wanting dialer/contacts
Click to expand...
Click to collapse
In Settings -> Application Settings, do you have "Allow Unknown Sources" checked? Here's a package with Contacts & Phone, you can try both.
I flashed the modded Mms.apk from nexus apps section and it worked fine until I realized it has a lot of mms issues on the EVO
Sent from my PC36100 using XDA App
Shidell said:
In Settings -> Application Settings, do you have "Allow Unknown Sources" checked? Here's a package with Contacts & Phone, you can try both.
Click to expand...
Click to collapse
I do, giving that zip a try right now
-edit- I tried rocking a contacts and phone from somewhere else(i think a nexus one aosp build) awhile back and it just went to hell.
also
Code:
C:\Users\Mrono\My Documents\downloads\Eclair Apps>adb remount
remount succeeded
C:\Users\Mrono\My Documents\downloads\Eclair Apps>adb install phone.apk
887 KB/s (582849 bytes in 0.641s)
pkg: /data/local/tmp/phone.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\Mrono\My Documents\downloads\Eclair Apps>adb uninstall phone.apk
Failure
Damn, that's frustrating. Looks like the system is securing certain applications.
I definitely understand your frustrations; I migrated to a early build of Froyo immediately because I vastly prefer Stock AOSP over Sense UI.
On that note, I'm a bit surprised we have yet to prepare an Eclair AOSP build for the EVO. Perhaps one of us should undertake that project, so we can have a clean, Sense-free build for others to use?
Shidell said:
Damn, that's frustrating. Looks like the system is securing certain applications.
I definitely understand your frustrations; I migrated to a early build of Froyo immediately because I vastly prefer Stock AOSP over Sense UI.
On that note, I'm a bit surprised we have yet to prepare an Eclair AOSP build for the EVO. Perhaps one of us should undertake that project, so we can have a clean, Sense-free build for others to use?
Click to expand...
Click to collapse
From what i've gathered it's possible to build an aosp eclair, but pointless as HTC STILL hasn't released the source code so it would be like the current froyo builds, broken camera and other things. So why bother build something that's as broken as froyo when froyo is better.
True enough. HTC customized enough of their Eclair build to make the EVO functional that it probably would be an exercise in futility as compared to Froyo.
I suppose my recommendation becomes to try some Froyo (Avalaunch?) and be patient on the kernel.
Just want to store the apk here is well. I'll pay to get this done.
Shidell said:
In Settings -> Application Settings, do you have "Allow Unknown Sources" checked? Here's a package with Contacts & Phone, you can try both.
Click to expand...
Click to collapse
did anyone get this working
i pushed the apps to /system/app in adb and rebooted started up and told me com.htc.dialerstorage has stoped working
and i had no reception with no contacts app and no phone app at all
so had to push the ones that i had before back on to it
(did and adb pull before pushed them over)
no luck... I cant even get android to acknowledge the apk. I can see it in the directory after an adb push but it's like nothing is installed in terms of OS recognition.
Any update on this? This is the only reason i use cyanogen instead of sense
These should work...Put them in /system/app and change the permissions to match the other apps in /system/app
command for correct permissions: chmod 644 /system/app/{name of app}.apk
snandlal said:
These should work...Put them in /system/app and change the permissions to match the other apps in /system/app
command for correct permissions: chmod 644 /system/app/{name of app}.apk
Click to expand...
Click to collapse
Has anybody successfully installed the AOSP dialer/phone using this method? Every time I mess with these apks I get serious phone problems and have to restore a Nandroid. Just wanted to see if this in fact works before I try again.
Like what kind o f problems?...using root explorer, when i first put those 3 apks in the /system/apps folder i got force closes...rebooted...changed permissions and rebooted again...i have both htc's phone and aosp's phone on my phone...using fusion's rom
snandlal said:
These should work...Put them in /system/app and change the permissions to match the other apps in /system/app
command for correct permissions: chmod 644 /system/app/{name of app}.apk
Click to expand...
Click to collapse
Can anyone confirm? I'd love to get rid of Sprints crap
Will flash from cyanogen to Fresh 3.1.0.2 and let you know if this works
ok this is where it all started
after downloading the latest launcherpro onto my froyo 2.2 polaris
it was regularly force closing, seemed to be unstable
after i downloaded a few wallpapers through market
launcherpro force closed again so i rebooted and now i cant get past the locked screen it just instantly force closes
is there a way to boot up with launcherpro disabled?
i posted this question here
http://forum.xda-developers.com/showthread.php?p=7572316#post7572316
i ended up having to wipe data and reinstall system from the replimenu
after i did this i reinstalled all my apps
and everything was fine
after i rebooted the phone
half my apps were missing,
so i went to market and all the apps that were missing still say there installed but the open and uninstall buttons are grayed out
i searched google and found this but i dont think it works for froyo as i tried but it just says not found
With ROOT Access:
1) Terminal Emulator
Type: rm -r data/data/com.android.vending/cache
Press ENTER
Type: Reboot
Press ENTER
If this doesn’t work, you can also try
2) Terminal Emulator
Type: rm -r data/data/com.android.vending/databases/*
Press ENTER
Type: Reboot
Press ENTER
You need to reboot because the Market App is always resident and will not update its cache and databases until it is restarted
any ideas??
any other people have a similar problem?
ended up reflashing froyo again oh well.
Tsenru said:
Hey guys, these instructions are based around Cyanogenmod 6 RC2, but should work fine for other ROMs if you've had trouble installing the updated Voice Search from the Market.
You MUST be running 2.2 (Froyo) for this to work however!
Updated this with instructions on how to fix the Google Search widget as well. Thanks to klinster, devlogic and OhioDroid.
Hey everybody, I don't know if anybody else is having this issue, but the new version of Google's Voice Search released today wouldn't install on my G1 (running CM6RC2) due to an incorrect signature. Anyway, there's a quick workaround, you just have to uninstall the voice search installed by default in CM6.
Anyway, if you have adb, plug into usb and run:
Code:
adb pull /system/app/ ~/Desktop/app/
adb remount
adb shell rm -f /system/app/VoiceSearch.apk
adb shell pm uninstall com.google.android.voicesearch
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb shell pm uninstall com.google.android.googlequicksearchbox
If you don't, open Terminal Emulator on your phone (This does NOT backup the .apk's, so proceed at your own risk!) and run:
Code:
su
mount -o rw,remount /system
rm -f /system/app/VoiceSearch.apk
pm uninstall com.google.android.voicesearch
rm -f /system/app/GoogleQuickSearchBox.apk
pm uninstall com.google.android.googlequicksearchbox
Your old out of date versions are now removed. Now go to the Market and install "Voice Search" and "Google Search".
Anyway, this is all pulled from the Cyanogenmod Wiki and most have you probably have already figured this out. In case you were stuck though, hopefully this helped you resolve the problem.
What's working:
Google Search Box (Reply if you have problems with listed method)
Most Voice Actions
What isn't:
"set alarm" action seems to rely on an as-of-yet unreleased Clock app from google. I am unable to confirm this as I do not have access to a stock Nexus One.
-Thanks to klinster for backup line for adb
-Thanks to devlogic and OhioDroid for search widget fix
-Thanks to BinaryMan, fixed typo in adb commands
Click to expand...
Click to collapse
originally posted by Tsenru in the G1 forums, just bringing it here.
I use latest RoDrIgUeZsTyLe ROM w/ A2SD (from 8-10). I was able to use Titanium Backup to uninstall Google Search, Voice Search and Voice Dialer, REBOOT, then install the new Google Search and Voice Search from market. As stated above all commands work, but the Clock Alarm.
As usual nandroid first just in case.
-Karl
Can anyone please post the 2 new APK's ? I'm in Canadia, can't see them.
CasseTrop said:
Can anyone please post the 2 new APK's ? I'm in Canadia, can't see them.
Click to expand...
Click to collapse
I attached the app to the first post.
Thanks to all that helped, and the OP.
Thank you!! It works perfectly.
Im runnin the latest cm6 nightly an i justed went on titanium backup an uninstalled google search an uninstalled voice search, rebooted, went to the market installed the latest google search an voice search app an everything works great
anyone else find that the new google search does not bind to the search soft-button after uninstalling/reinstalling ?
britoso said:
anyone else find that the new google search does not bind to the search soft-button after uninstalling/reinstalling ?
Click to expand...
Click to collapse
I have this same problem too x.x
android.modaco.com/content/software/315754/google-voice-actions-updated-quick-search-box-apks-original-testsigned/
try this instead of running terminal command.
britoso said:
anyone else find that the new google search does not bind to the search soft-button after uninstalling/reinstalling ?
Click to expand...
Click to collapse
If you rename the new voice search as the old ones and move them back into system/app and reboot, the search soft-button should work again.
Sent from my Nexus One using XDA App
illumina0 said:
If you rename the new voice search as the old ones and move them back into system/app and reboot, the search soft-button should work again.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Moving them back to /system/app worked. Thanks for the tip!
How do you guys make the voice command for the clock to work? It keeps syaing i have to update the clock?!? Thanks!
cloversis said:
android.modaco.com/content/software/315754/google-voice-actions-updated-quick-search-box-apks-original-testsigned/
try this instead of running terminal command.
Click to expand...
Click to collapse
I'm following this guide:
http://code.google.com/p/android/issues/detail?id=10389
to getting the search button to work on my Desire.
Problem - if I go into ADB shell and I can "ls data", and see in there an app folder, but if I do "ls /data/app" is says "no such file or directory"?
Is this because I'm using app2sd and if so, why?
Anyway, I got the googlequicksearchbox.apk from modaco here
http://android.modaco.com/content/s...ed-quick-search-box-apks-original-testsigned/
copied to system/app and rebooted and it works great. smashing.
do the navigate and map commands now work with bluetooth headsets?
Thnks for the .apk !!!
??
Im using Kang-o-rama 1.0 b2 CM6RC2 / Apps2Ext.. My apps are on my sd so when ever I get to ( pm uninstall com.google.android.voicessearch) it say failure.. I forgot were my app are stored once you push a2sd ?
I am running froyo and CM6 RC2. I used Titanium Backup to uninstall both voice searce and google search. Rebooted and went to the market to install. Worked!
Just trying to install before reboot will not work. Thanks for the heads up guys/gals!
gj13 said:
Moving them back to /system/app worked. Thanks for the tip!
Click to expand...
Click to collapse
For the search button binding:
Code:
adb remount
adb pull /data/app/com.google.android.googlequicksearchbox-1.apk .
adb shell pm uninstall com.google.android.googlequicksearchbox
adb push com.google.android.googlequicksearchbox-1.apk /system/app/GoogleQuickSearchBox.apk
Root explorer, Search for VoiceSearch.apk, mount system. Rename to VoiceSearch.apk.old. Unmount system, Install From market. Done.
Works like a champ for me, screw all this adb stuff and terminal. Lol.
I've installed new firmware and I've rooted my device however I'm not able to download new applications and my GPS doesn't seem to be working.
Error "Package file wasn not signed correctly. Uninstall the previous copy of the app and try again. (option to uninstall is available but never works)
Does anyone else have these issues and does anyone have a fix most importantly?
Thank you,
rci_canada said:
I've installed new firmware and I've rooted my device however I'm not able to download new applications and my GPS doesn't seem to be working.
Error "Package file wasn not signed correctly. Uninstall the previous copy of the app and try again. (option to uninstall is available but never works)
Does anyone else have these issues and does anyone have a fix most importantly?
Thank you,
Click to expand...
Click to collapse
Have a look at thread http://forum.xda-developers.com/showthread.php?t=2479695 which has quite a lot of information on rooting and flashing this phone. For this particular problem, try the following:
1. Use a Root Uninstaller (I use System App Safe Remover) to uninstall Documents to Go, Skype, Twitter, YouTube and WhatsApp. Don't uninstall Facebook - I can't get that one to reinstall properly yet.
2. You can also uninstall unwanted stuff like 3D Live Weather, Weather, Weather Service and the Chinese keyboard if you want - I've installed Google Keyboard instead which seems much better.
3. Reboot the phone
4. Go to Settings / Apps / All and, for Google Play Services and Google Play Store, Clear Cache, Clear Data and Force Stop
5. Reboot the phone
6. Reinstall the desired apps from the Play Store
Docstogo won't reinstall properly - it'll give an error about a shared ID. Have a look at this thread http://forum.xda-developers.com/showthread.php?t=1219029- use ADB (via MTKdroidTools) to copy packages.xml to your computer, edit it to remove the DocstoGo section, copy it back to the phone, reboot, and install from Play Store:
1. adb shell chmod 666 /data/system/packages.xml
2. adb pull /data/system/packages.xml
3. Now edit (notepad++) and remove the shared user in question xml block from the file:
Code:
<shared-user name="com.docstogo" userId="xxxxx"> (or whatever)
...
</shared-user>
4. adb push packages.xml /data/system
5. adb shell rm /data/dalvik-cache/*
6. adb reboot
Hope that helps.
Everything is working except facebook
serafis said:
Have a look at thread http://forum.xda-developers.com/showthread.php?t=2479695 which has quite a lot of information on rooting and flashing this phone. For this particular problem, try the following:
1. Use a Root Uninstaller (I use System App Safe Remover) to uninstall Documents to Go, Skype, Twitter, YouTube and WhatsApp. Don't uninstall Facebook - I can't get that one to reinstall properly yet.
2. You can also uninstall unwanted stuff like 3D Live Weather, Weather, Weather Service and the Chinese keyboard if you want - I've installed Google Keyboard instead which seems much better.
3. Reboot the phone
4. Go to Settings / Apps / All and, for Google Play Services and Google Play Store, Clear Cache, Clear Data and Force Stop
5. Reboot the phone
6. Reinstall the desired apps from the Play Store
Docstogo won't reinstall properly - it'll give an error about a shared ID. Have a look at this thread http://forum.xda-developers.com/showthread.php?t=1219029- use ADB (via MTKdroidTools) to copy packages.xml to your computer, edit it to remove the DocstoGo section, copy it back to the phone, reboot, and install from Play Store:
1. adb shell chmod 666 /data/system/packages.xml
2. adb pull /data/system/packages.xml
3. Now edit (notepad++) and remove the shared user in question xml block from the file:
Code:
<shared-user name="com.docstogo" userId="xxxxx"> (or whatever)
...
</shared-user>
4. adb push packages.xml /data/system
5. adb shell rm /data/dalvik-cache/*
6. adb reboot
Hope that helps.
Click to expand...
Click to collapse
Everything is great now ! The only problem I am currently having is my facebook app won't install. I tried to uninstall but the app isn't there. When I reinstall I receive a message that the package is not digitally signed. Anyone one else have a Facebook issue with there Doogee dg100 ?
Facebook won't install - Doogee DG100
rci_canada said:
Everything is great now ! The only problem I am currently having is my facebook app won't install. I tried to uninstall but the app isn't there. When I reinstall I receive a message that the package is not digitally signed. Anyone one else have a Facebook issue with there Doogee dg100 ?
Click to expand...
Click to collapse
Is there any solution to re-install Facebook app? My girlfriend is accidentally uninstall app and we cannot install it again, package is not digitally signed... thanks
Is the GPS fixed
rci_canada said:
Everything is great now ! The only problem I am currently having is my facebook app won't install. I tried to uninstall but the app isn't there. When I reinstall I receive a message that the package is not digitally signed. Anyone one else have a Facebook issue with there Doogee dg100 ?
Click to expand...
Click to collapse
Did the above cited procedure fixed you GPS as well?
GPS as well as magnetic sensor or out of order in my new DG100
Rooted with SRSroot and am having the latest firmwire from doogee site (20140317)
Thanks