Hi everyone,
I tried the HTC Google ION v1.6 and was just completely blown away with the awesomeness of Google Voice Search.
Now I just HAVE to have that on my custom rom(I'm running MyHero 2.0.4), is there a way? I've copied the .apk from several roms and installed it but it's always ends up as a Force Close, maybe something is missing?
All help/tips/pointers are appreciated!
/D
you cannot just push the APK on a hero ROM, there is probably some framework stuff that is unavailable on hero ROM that stops it from working. contact the maker of your ROM.
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
Samsung Infuse
ATT
Now running GingerReal 1.1.9
Couldn't get Swype to work correctly, but expected that: the porter said so
Couldn't get Swype to uninstall using Manage Apps or Root Explorer so used TitaniumBackup to to exploit and remove the .apk
Installed Swype Installer, still getting same message: "Sorry, the Swype Beta is currently unavailable for devices that have Swype preinstalled."
The porter mentioned a .lib file might need to be deleted, but I can't find it anywhere.
Any ideas?
(For the record, GingerReal is very, very pretty. I just need my keyboard back.)
Nuke the Swype files on your /system. There should be the apk in /system/app and the Swype core library in /system/lib.
This is still a learning process for me. I had Root Explorer in R/W. *sheepish grin*
Downloading Swype through the installer now; I'll post again if it's successful. Thanks for the help!
Swype seems to be taking an abnormally long time to download.
My phone shows that I'm connected to WiFi, and unless I'm mistaken I see the connection through my router, but I'm beginning to wonder.
Any recommendations for checking my connectivity?
Edit: If I keep making stupid mistakes, I don't deserve an android phone. :/ Forgot to wipe the cache, and of course as soon as I did, Swype installed just fine. I'd still be interested in an way to check my wireless connection, though.
I installed the Android joy with the system htc, when use blinkfeed, I get an error message permissions goolge + for htc sense, I set permissions but nothing to do. how do I fix?
Why you don't ask it in the Android Joy thread?
Hello, I am currently making a few software modifications on my rooted Galaxy S9 on which I installed Noble ROM from AlexisXDA to be able to use one ui 4.1 with android 12. Now I’m trying to install One UI 5 apps on it, so I already installed Samsung Messages, Contacts, Phone dialer and Gallery as system apps using Lucky Patcher and everything worked as expected, and these apps simply replaced the old ones. Though, now I am struggling to install One UI 5 files app (aka Samsung My Files 14.x). This app is only supposed to be compatible with android 12L and more recent, but I managed to change the min SDK requirement to make it run on android 12. After I changed the min SDK I installed it as system app using Lucky Patcher and now everything is working until I long press a file which makes the app crash. Digging into android files, I noticed in the system/priv-app folder that the original version of MyFiles was still installed and I can’t delete it. Second thing I noticed, in the original MyFiles folder (in private app) there’s a file with the same name as the apk but the extension .prof is added next to it. I don’t know what this file is but I’m pretty sure this is what makes the original version work fine. So, can anyone tell me what this prof file is, and how I could make one for my custom My Files App please ?
Only for clarity:
Apps stored in /system/app are APKs what are indispensable part of Android OS - user apps has nothing to do there
whereas
apps stored in /system/priv-apps are APKs to be granted system permissions, regardless of the app signature: they at any time can get removed - mostly without any harm but requires Android is got rooted
jwoegerbauer said:
Only for clarity:
Apps stored in /system/app are APKs what are indispensable part of Android OS - user apps has nothing to do there
whereas
apps stored in /system/priv-apps are APKs to be granted system permissions, regardless of the app signature: they at any time can get removed - mostly without any harm but requires Android is got rooted
Click to expand...
Click to collapse
So, if I understand it correctly it means my version of the app gets rejected every time by the priv-app folder right ? Unlike the preinstalled My Files app which is granted system permissions ?