Google Voice Search/Maps Force Closes on Modaco 1.1 - Hero CDMA Themes and Apps

Don't mean to start too many threads, but this is meant to specifically discuss the above programs.
RE: Google maps
Completely uninstalling and then reinstalling from the market seems to address the force close that occurs when a search query is submitted.
Alternatively, you can move the google maps apk from the ext2 partition to the /system/app folder on the phone. This is the same fix as for the google voice search...
RE: Google voice search
I went about the rather cumbersome process of moving the apk from the ext2 partition (as automatically happens in the Modaco ROM) back to the /system/app folder on the phone. This has resolved all the voice search crashes that I have come across.
NB: I do not know the results if you were to fix google maps by uninstalling and reinstalling and fix google voice search by moving the apk. I.e. if you were to do a google voice search within google maps under this fixing method, Im not sure if the voice search will crash....I'm guessing not though.
Please bear in mind im a COMPLETE linux/andoird/adb/whatever noob. I can outline my method for moving the apks, but Im certain there are better ways to do it.

Sweet, that fixed my google voice issue (and a quick mv and reboot didn't seem so bad to me, but perhaps I just have a high pain tolerance lol)

that or i didn't know there was an mv command...like i said...complete noob

dom2114 said:
that or i didn't know there was an mv command...like i said...complete noob
Click to expand...
Click to collapse
No sweat, mv is a linux command that can be used to move (thus mv) or rename files.
Basic Syntax:
Code:
mv [source] [destination]
So what I did was
Code:
mv /data/app/com.google.android.voicesearch.apk /system/app
and then rebooted the phone. Worked like a champ!

thanks, worked perfectly
NOTE: be sure to issue this command before the move to not get the 'read-only file system' error
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system

Thanks a ton for this! I don't have A2SD running and my Google Voice Search was also not working, I didn't even notice until someone had pointed it out. Lucky for me, there was a solution almost as fast as the problem was discovered! We should probably point it out to Paul @ MoDaCo now!

tstack77 said:
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Alternatively, the following command works on MoDaCo's ROM:
Code:
adb remount
It accomplishes the same thing and is waaaaay easier for my simple mind to remember.

thecodemonk said:
Code:
adb remount
It accomplishes the same thing and is waaaaay easier for my simple mind to remember.
Click to expand...
Click to collapse
haha, totally agree. Thanks for that bit o' knowledge

AWESOME, thank you. I've been saving all of these forum posts together, I'll make a super-post once I get everything running the way I want, very clearly detailed and it will feature all of these different commands that I have used to help me along the way!

ok, so help me out if you can.
I want to copy the apk's on the ext2 partition i.e. in /system/sd/app to my computer in case I decide to wipe the sdcard for some reason.
In adb im typing:
cp /system/sd/app /desktop
Ive tried cp with the -r, -f, -rf options, and everytime i get a cannot create error message or sometimes a cannot create symlink message
Any tips??

dom2114 said:
ok, so help me out if you can.
I want to copy the apk's on the ext2 partition i.e. in /system/sd/app to my computer in case I decide to wipe the sdcard for some reason.
In adb im typing:
cp /system/sd/app /desktop
Ive tried cp with the -r, -f, -rf options, and everytime i get a cannot create error message or sometimes a cannot create symlink message
Any tips??
Click to expand...
Click to collapse
Once you're inside the adb shell, you don't really have access back to your desktop. Your best bet would be to run (from the windows command prompt where you normally run adb):
Code:
adb pull /system/sd/app c:\mybackup
(Replace C:\mybackup with whatever the path is to your destination...if you're on *nix or Mac, it will probably be more like "./Desktop" or something)

jesus, i think i might put a fist through a wall...im such an idiot.
pulling instead of pushing for the last half hour...
cheers, codemonk

dom2114 said:
jesus, i think i might put a fist through a wall...im such an idiot.
pulling instead of pushing for the last half hour...
cheers, codemonk
Click to expand...
Click to collapse
No sweat, we all have those moments. All the commands are fresh in my head since I've been researching and digging into things since before we had root (at the time trying to get it)...that and I think I've become addicted to the xda forums. (HALP!)

just as quick update to all.
Ive got a feeling that google voice search was actually causing all the force close issues in google maps. I still have google maps on my sdcard and did not uninstall it (only updated it) - have google voice search on phone and all seems to be fine.
A quick question for codemonk (& anyone else out there). For apps in the /system/app folder, you've got the apk and corresponding odex file. Anyone have any idea where the corresponding odex files for apps installed on the sd are (if they exist at all)?

dom2114 said:
just as quick update to all.
Ive got a feeling that google voice search was actually causing all the force close issues in google maps. I still have google maps on my sdcard and did not uninstall it (only updated it) - have google voice search on phone and all seems to be fine.
A quick question for codemonk (& anyone else out there). For apps in the /system/app folder, you've got the apk and corresponding odex file. Anyone have any idea where the corresponding odex files for apps installed on the sd are (if they exist at all)?
Click to expand...
Click to collapse
Not sure on the odex...I noticed some of the apps I removed didn't appear to have them (or are in a location I'm not aware of).
I ended up just moving the google voice app to fix it. (There's another thread on the google maps/google voice thing that contains the fix)

Ha, guess my XDA navigation isn't quite up to par. Care to post the link out of interest?

dom2114 said:
Ha, guess my XDA navigation isn't quite up to par. Care to post the link out of interest?
Click to expand...
Click to collapse
Wow I'm out of it...I was looking around, then realized...this *is* that thread. >.<

hahaha...guess it was your turn for onea those mistakes....

ok i dont even have voice search after installing modaco rom. all i have is the basic google search. how do i get the apk or download it. i tried the move, but it says it doesnt exist. i am complete noob so details are really needed thanks

if you decided to format your sdcard (using the recovery console) using the ext2/fat32/swap option, then the modaco ROM automatically moves google voice search and google maps (and a few other apps like quickoffice) to the ext2 partition on the sdcard.
this partition is accessible in various ways, but most people do it manually using ADB. if you don't know how to use adb, there are a bunch of threads here that talk about it. But in a nutshell, it involves downloading the android SDK, extracting it to somewhere on your computer (no need to install anything), open a command prompt in windows (start -> run -> cmd), navigate to the folder containing the sdk and go to the tools folder inside there (e.g. cd\androidsdk\tools), then type 'adb shell'. If all worked, you should have access to the phone.
then its just a matter of navigating to the ext2 partition on the sdcard (this is where all apps you install will be installed too - this is apps2sd automatically at work). You navigate there by typing:
cd /data/app
you should see the google voice search apk in there + others
then just use the command that codemonk helped me out with:
mv /data/app/com.google.android.voicesearch.apk /system/app
this will move the apk from the data/app folder (this is your sdcard) to the phone.
Written this response very quickly. Ask any specific questions and Ill try to help more if needed.

Related

(Solved) ADP1.5 (any) App2sd, After Wipe, Market No Longer Autoupdates Apps

First let me say that tho' I may not post here frequently, but I am an avid fan and supporter of this community. Much praise to all those who have so diligently worked on the custom roms, such as JF, Haykuro, TheDude, etc., and to their continuing cooperation and advancement.
However I come with an issue, that I have looked for a solution but have not been able to find one. And while I do dual boot with Jaunty, I am in no way a guru to have time to understand Android's systems. I do hope this would be fixed just for a more 'official' method of updating instead of aTrackDog.
After running nandroid for safety, wiping and flashing a new 1.5 ROM (Dude's .8, .92, .93, Haykruo's ADP1.5H [No JF yet, tomorrow]), then restoring apps and links through either manual method (I just adb the entire process for convenience) or through the apps2sd app (also for convenience). The official Market app does sync in some way with what is installed on the phone, until you go into the market, at which point it asks you if you want to install it to replace the version you have.
I am curious if there is a way to backup your Market application settings before wiping (I prefer to wipe, even if they are 'nowipe' builds, as I go from different developer's builds frequently too) so after redo the app2sd on your new install, you won't have to run aTrackDog to get your updates. Not going through and installing every single application is a plus too, why have more apps if we can just backup and transfer settings somehow?
As I previously mentioned, I don't know the Android system, or specifically the Market and Application systems, so I don't know if this could be done. Also, if I am the only one experiencing this, I would like to know how I am doing this improperly.
Update: Thanks goes to beagz for supplying the information and giving credit to haitiankid4lyf (http://forum.xda-developers.com/showpost.php?p=3655174&postcount=44)
It's not just you, that's how it works. But I don't see a problem running atrackdog.
I guess there is a file that you can transfer and it will make market remember your apps. Though I might be wrong. If it was that easy, someone would have figured it out by now.
Somebody discovered and posted this. I tried and it works.
mkdir /sdcard/market
cp /data/data/com.android.vending/databases/assets.db /sdcard/market/assets.db
To restore use
rm /data/data/com.android.vending/databases/assets.db
cp /sdcard/market/assets.db /data/data/com.android.vending/databases/assets.db
beagz said:
Somebody discovered and posted this. I tried and it works.
mkdir /sdcard/market
cp /data/data/com.android.vending/databases/assets.db /sdcard/market/assets.db
To restore use
rm /data/data/com.android.vending/databases/assets.db
cp /sdcard/market/assets.db /data/data/com.android.vending/databases/assets.db
Click to expand...
Click to collapse
Cool! It is an easy solution after all.
Thank you for sharing.
Cool, so just run the first two lines in the termainl and it will fix the issues?
Minker17 said:
Cool, so just run the first two lines in the termainl and it will fix the issues?
Click to expand...
Click to collapse
If you have not made backup prior to flashing a new ROM, this method will not help.
The first 2 are run before a wipe. After run market so that it is set then run the restore commands , reboot and you are set.
Just to clarify. This assumes you are starting from a stable running OS and are preparing to upgrade. All your apps must already be installed.
1) Run these commands to backup your market settings.
mkdir /sdcard/market
cp /data/data/com.android.vending/databases/assets.db /sdcard/market/assets.db
2) Install and wipe to update to the new build you want to use. (you don't need to do any of this if you are not wiping)
3) Complete the setup of your phone.
4) Start the market and agree to terms and conditions.
5) Run the second set of commands to restore your market settings.
rm /data/data/com.android.vending/databases/assets.db
cp /sdcard/market/assets.db /data/data/com.android.vending/databases/assets.db
6) Reboot and restart the market. All your apps should now be listed under downloads and should update as usual.
7) Kick back and smile since you do not have to redownload and install your apps again
beagz said:
The first 2 are run before a wipe. After run market so that it is set then run the restore commands , reboot and you are set.
Just to clarify. This assumes you are starting from a stable running OS and are preparing to upgrade. All your apps must already be installed.
1) Run these commands to backup your market settings.
mkdir /sdcard/market
cp /data/data/com.android.vending/databases/assets.db /sdcard/market/assets.db
2) Install and wipe to update to the new build you want to use. (you don't need to do any of this if you are not wiping)
3) Complete the setup of your phone.
4) Start the market and agree to terms and conditions.
5) Run the second set of commands to restore your market settings.
rm /data/data/com.android.vending/databases/assets.db
cp /sdcard/market/assets.db /data/data/com.android.vending/databases/assets.db
6) Reboot and restart the market. All your apps should now be listed under downloads and should update as usual.
7) Kick back and smile since you do not have to redownload and install your apps again
Click to expand...
Click to collapse
Also worth noting: this wont work if you go from rc33 to cupcake. I tried it and after restoring the database, market force closes on launch. Fortunately I made a backup of the new assets.db before I restored the old one.
@Azlum: Good to know. Never tried it before I was using the cupcake builds.
Wow this is so awesome, thamk you very much, this is exactly what I have been looking for. This makes apps2sd absolutely perfect for me now. I think I am going to add this to the wiki if at all possible. Thank you so much again.
I didn't wipe from JF RC33 to JF 1.5, had my apps to SD, and the market showed me having about half of my apps installed. Don't know why, but that's what it did.
well, my lazy ass didnt backup, so ill continue to use atrackdog. works for me
Just to let everyone know. I was very glad to help. However, it should be noted that as I stated I found this script posted by someone else. I feel that it is proper to credit
"haitiankid4lyf"
for posting this in the Gscript thread post # 44.
Thank you haitiankid4lyf! for posting this script so that we could use it to make recoveries easier!
beagz said:
Somebody discovered and posted this. I tried and it works.
mkdir /sdcard/market
cp /data/data/com.android.vending/databases/assets.db /sdcard/market/assets.db
To restore use
rm /data/data/com.android.vending/databases/assets.db
cp /sdcard/market/assets.db /data/data/com.android.vending/databases/assets.db
Click to expand...
Click to collapse
HOLY CRAP. That saved my life. This post should be stickied.
I believe that during the initial app2sd development, people experimented with moving the entire /data/data directory, which was unstable and is now not recommended (I never did it as I didn't want that many I/O operations wearing down the life of my card, tho' it is class 6) and I believe we wouldn't need to do this if we were to have /data/data ported.
I would also like to reference this thread http://forum.xda-developers.com/showthread.php?p=3729952 that details the backing up (and restoration) of specific application settings as this I believe would be useful for some (as it is for me). Integration of this into something like aTrackDog would be absolutely amazing, the reason why I say aTrackDog is since it already tracks applications and wouldn't just be copying the whole directory including system components (as the point of this is having things similar AFTER doing a wipe).
Anyway, just my two cents.
Wait...will this work if I backup with nandroid before I upgraded to 1.5?
What I did was setup a gscript to backup all the data to the sdcard.
cp -f -r /data/data/* /sdcard/backups/---mylocation--
You could reverse / restore by doing it in reverse and then chmoding as you said.

Mytouch 3g talking and working google nav

I HAVE CY 4.3.2.1 ROM RUNNING THIS IS WHAT I DID TO GET IT WORKING
I DONT KNOW HOW LONG IT WILL WORK AS I AM ONLY DOING WHAT WAS HAS BEEN DONE BEFORE ME
Copied the following onto my Android's SD card:
http://cid-3cf744d4c83401e6.skydrive.live.com/browse.aspx/.Public
build.prop
build.sapphire.prop
Maps.apk
Unplugged my phone and waited for it to prep the SD card
Fired up the application Terminal Emulator
Typed the following commands:
Code:
suYour phone may prompt you to allow or not allow this, allow it obviously, otherwise wait until you see a # before continuing to the next command
Code:
ashCode:
mount -o remount,rw /systemNext it's time to copy the build files into your system directory, but first you should backup the originals just in case.
Code:
cp /sdcard/build.prop /system
cp /sdcard/build.sapphire.prop /systemRemove the existing Google Maps app
Code:
cd /data/app
rm *Maps*
rm *maps*Code:
when i did this it siad it did not exist but i just keep going!!!
cd /data/dalvik-cache
rm *Maps*
rm *maps***END OF UPDATE**
All done with this part, time to reboot.
Code:
rebootGetting force close prompts for Google Voice? Yeah, go ahead and do the force close. Be sure to wait until your phone is done booting.
Now it's time to actually install the new app. So again, open up Terminal Emulator and type the following code:
Code:
suAgain, allow this command and/or wait until you see a # character
Code:
ash
mount -o remount,rw /system
install /sdcard/Maps.apk /system/app/At this point, I couldn't get things to work like the second post I linked earlier, so I'll did this command...
Code:
rebootGetting force close prompts for Google Voice again? Close the sucker and wait until your phone is fully booted.
Ok the app is installed and you may be thinking you're good to go, but you aren't. It's still not working for you like it wouldn't work for me. Do you have Google Voice installed before you did all this stuff? Most likely!
Go into your phone's settings and Manage Applications
Uninstall Google Voice
Fire up the Market and search for Google Voice
Install Google Voice
Reboot your phone (You can do this by holding the power button and select "reboot phone" or the long way through Terminal Emulator)
Run the Map app (now you may have your old address in there that you tried earlier, never fear. Just clear the map from the map menu)
Put in some directions like you normally would
You should see the option for "Navigate" after it gets the directions. Click it.
Accept the installation of the voice guide thingy
You're done! Revel in the awesomeness!
Get a beer and laugh at your friends with an iPhone
these is what i did exactley and it worked for me
I DONT NO HOW LONG THIS WILL WORK FOR!!!!!!
File to download
http://www.filefactory.com/dlf/f/a1a...apphireNav.zip
dude, the code tags failed. lol
also the link is dead
WOW
theomajigga said:
dude, the code tags failed. Lol
also the link is dead
Click to expand...
Click to collapse
that link died fast lol how do i upload it then i tired here and it says upload failed lol i have the neccsory file but how do i get it to you guys since that link died
i'd first fix the code tags
but im not sure, i think you cp the link wrong honestly.
-T
theomajigga said:
i'd first fix the code tags
but im not sure, i think you cp the link wrong honestly.
-T
Click to expand...
Click to collapse
http://www.mediafire.com/?tyzmnzzkhen
here is another link but this one makes face book crash i belive i dont use face book but thats what g1 users are saying
FOR SAPPHIRE
I read a post earlier about fixing some apps not working.
in build.prop
change to 4 instead of 5.
ro.build.version.sdk=4
Did this and re-ran part 1 and part 2. Works fine with Handcent and facebook app working. haven't got any FC with other apps and navigation still working after a few hours and some reboots.
Uploaded a new .rar with changes to build.prop
http://www.mediafire.com/?jwhmkzay2mm
Extract All to Desktop
Run part 1 - when prompted hit any key and phone will reboot.
when up and running, run part 2.
Test nav by opening google maps and geting directions. Underneath "Show on Maps" you should see "Navigate" If you don't try installing Google Voice (fixed it for a lot of people)
If you did the above and Navigate isn't working, here is a link to the build.prop version that causes some app errors but gets nav Working
http://www.mediafire.com/?tyzmnzzkhen
Skreacher said:
FOR SAPPHIRE
I read a post earlier about fixing some apps not working.
in build.prop
change to 4 instead of 5.
ro.build.version.sdk=4
Did this and re-ran part 1 and part 2. Works fine with Handcent and facebook app working. haven't got any FC with other apps and navigation still working after a few hours and some reboots.
Uploaded a new .rar with changes to build.prop
http://www.mediafire.com/?jwhmkzay2mm
Extract All to Desktop
Run part 1 - when prompted hit any key and phone will reboot.
when up and running, run part 2.
Test nav by opening google maps and geting directions. Underneath "Show on Maps" you should see "Navigate" If you don't try installing Google Voice (fixed it for a lot of people)
If you did the above and Navigate isn't working, here is a link to the build.prop version that causes some app errors but gets nav Working
http://www.mediafire.com/?tyzmnzzkhen
Click to expand...
Click to collapse
how do i run the .bat files on a mac? i double clicked on it and it opened terminal then it rebooted my phone but it was unable to copy the files over.
Code:
cannot stat 'build.prop': No such file or directory
cannot stat 'build.trout.prop': No such file or directory
: command not foundp/Android/tools/Part 1.bat: line 5: pause
logout
In windows all that is required is to extract all files to the same directory (only tried it by having them all on the desktop. then doubleclicking the part1.bat from the desktop.
I'm not familiar enough with OSX but it seems like its not finding the build.prop to push it to your phone.
Google Nav only works in the US
NOTE: Currently Google Nav will only work in the US.
You can get it running (as in install the app) on phones elsewhere in the world, but to actual use the Navigate feature you have to have the GPS turned on (duh) so it knows where you are, and due to licensing issues (I think) the Navigate feature will not work if you are not in the US.
Running Cyanogen 4.2.3.1, I used the files Skreacher provided on my T-Mobile MT3G, running on Mac OS X Leopard...it works! I installed the Text to Speech thing needed as well...Facebook loads as always (some people were having problems) but the only thing is that exiting Navigation sometimes doesn't work (I have to exit twice). Thanks a lot Trying this out on the road tomorrow!
for the semi-noobs, like myself lol, can someone please re-explain which codes to run with Skreacher's added input changes?
sorry dskyers, i'm confused like hell per your intructions.
i forgot to mention i'm kind of slow... lol all i want is google maps nav...
Try instructions at my blog: http://blog.mmayhew.com
Worked like a charm
I followed the instructions at the top of this thread. It works perfectly. Google voice is working too! I was having some trouble with that on my earlier attempts (i think i was using the build.prop's for the G1).
Also, I updated to CY 4.2.4 and there is no breakage. Navigation still works like a charm.
Thanks a million!
mmayhew said:
Try instructions at my blog: http://blog.mmayhew.com
Click to expand...
Click to collapse
Thanks mma, this worked perfectly and you covered all areas needed to get it installed correctly.
@op, thanks for the info and hopefully I don't offend you, but to anyone needing a clear how-to, go to the mma's blog.
I had this working. I used Nav once, then pressed 'Exit Nav' so it would shut up. Now I can't get it back. Help anyone?
Edit: By 'used once' I mean, I had it on for like an hour for a trip I had to make.
detox702 said:
I had this working. I used Nav once, then pressed 'Exit Nav' so it would shut up. Now I can't get it back. Help anyone?
Edit: By 'used once' I mean, I had it on for like an hour for a trip I had to make.
Click to expand...
Click to collapse
Try a phone reboot and test it again.
Anyone run this on any of the hero roms?
mmayhew said:
Try instructions at my blog: http://blog.mmayhew.com
Click to expand...
Click to collapse
EDIT number 1 MILLION!!!!!!!
IT WORKED!!!!!!!!!!!!!! IT WORKED!!!!!!!!!!!!!
ok... IF YOU WIPE YOUR PHONE AND YOU'RE STARTING FRESH, THEN YOU WILL MOST LIKELY HAVE TO SKIP SEVERAL STEPS IN MMAYHEW's INSTRUCTIONS!
I had to skip steps 9 through 18.
but it works!
thanks in advance guys!
thanks again to all!!! later
rydr1 said:
Try a phone reboot and test it again.
Click to expand...
Click to collapse
That would be negative. Still no option for nav.

[REF] Google Navigation Install on G1 (Dream) Running Cyanogen's ROM (any version)

LATEST AND LAST EDIT TO THIS THREAD:
Download the new maps from Google in the marketplace for Google Navigation. Works Android Phones running the 1.6 platform.
No need to follow these instructions anymore!
---------
#Thought I would make a thread with clarified instructions on installing the new Google navigation on a G1 running Cyanogen's ROM. There have been a lot of #problems with the instructions in the other thread since the files supplied (namely build.prop and build.trout.prop) are not correctly referencing each person's #setup correctly.
#Instead of pushing generic prop files onto your phone, you can simply edit one line in your build.trout.prop file found in the system directory on your G1. #Thanks goes to aad4321 who posted it.
#The edit is simply changing the ro.build.fingerprint line to:
#ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
#You can pull this file, edit, remount, then push back onto your phone to allow you install the new maps.apk. You can find the new maps.apk file in the #attachment. You can also find batch files to do all of the above, but is only guaranteed to work on the 4.2.5 ROM. All other Cyanogen version users can use #these files as well if they replace the build.trout.prop file with their own, and then edit the line as above.
#This method will keep all your apps intact, and not cause any problems with marketplace (protected apps not showing), google voice (force closing), facebook #(force closing), etc as reported in the other thread.
#<EDIT 1>If you get the errror "Device not found," make sure you have USB Debugging enabled in settings (thanks kizer).
#<EDIT 2>After performing a rm command, if you get a statement about the directory or file not existing, all is fine. Those rm commands are just trying to #find all possible places the old maps app could be stored, and so if it doesn't exist, you don't have to worry about it. Just go on to the next step.
#<EDIT 3>If you don't see the navigate function, install google voice.
#0) Connect phone
#1) Unzip downloaded file
#2) Run Part 1.bat
#3) When prompted to press any key, do so; the phone will reboot
#4) When your phone is running again, run Part 2.bat
#5) When prompted to press any key, the installation process is done.
#6) Make sure GPS is enabled
#7) Open Maps and press OK
#8) Press Menu
#9) Press Directions
#10) Enter an end point
#11) Click Go
#12) Just under "Show on map", click Navigate.
#13) If prompted to install the voice codec, do so.
#http://www.mediafire.com/?znzizmd1mmm
junker02 said:
Thought I would make a thread with clarified instructions on installing the new Google navigation on a G1 running Cyanogen's ROM. There have been a lot of problems with the instructions in the other thread since the files supplied (namely build.prop and build.trout.prop) are not correctly referencing each person's setup correctly.
Instead of pushing generic prop files onto your phone, you can simply edit one line in your build.trout.prop file found in the system directory on your G1. Thanks goes to aad4321 who posted it.
The edit is simply changing the ro.build.fingerprint line to:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
You can pull this file, edit, remount, then push back onto your phone to allow you install the new maps.apk. You can find the new maps.apk file in the attachment. You can also find batch files to do all of the above, but is only guaranteed to work on the 4.2.5 ROM. All other Cyanogen version users can use these files as well if they replace the build.trout.prop file with their own, and then edit the line as above.
This method will keep all your apps intact, and not cause any problems with marketplace (protected apps not showing), google voice (force closing), facebook (force closing), etc as reported in the other thread.
0) Connect phone
1) Unzip zip to desktop
2) Run Part 1.bat
3) When prompted to press any key, do so; the phone will reboot
4) When your phone is running again, run Part 2.bat
5) When prompted to press any key, the installation process is done.
6) Make sure GPS is enabled
7) Open Maps and press OK
8) Press Menu
9) Press Directions
10) Enter an end point
11) Click Go
12) Just under "Show on map", click Navigate.
13) If prompted to install the voice codec, do so.
http://www.mediafire.com/?znzizmd1mmm
Click to expand...
Click to collapse
While I placed the files from his zip directly on my SDcard and used terminal to run the command, Junker's method appears stable. I have Google voice, protected apps in market, and functional Navigation. (can't answer for facebook, since I don't have an account.)
Note to someone who does not know shell commands...don't try and copy the ADB commands they are not the same. Know what you are doing before you do it.
Thanks for the post Junker02
i really dont get why there are like 325435412512 threads for this.
They should be condensed into 1.... and listed as separate options/ways to do it.
I had no connection then realized I didn't have USB debugging enabled.
Seemed to work fine.
krstnsn said:
i really dont get why there are like 325435412512 threads for this.
They should be condensed into 1.... and listed as separate options/ways to do it.
Click to expand...
Click to collapse
I believe the methods listed on the other threads are incorrect, or are more complicated than need to be (and possibly breaks other apps). I only found this method buried in the think-tank post, and though it was suggested for the OP to fix the first post, it never was. Hopefully others who are on Cyanogen's ROM will appreciate the info.
kizer said:
I had no connection then realized I didn't have USB debugging enabled.
Seemed to work fine.
Click to expand...
Click to collapse
Thanks for the tip! I'll add it to the first post.
junker02 said:
I believe the methods listed on the other threads are incorrect, or are more complicated than need to be (and possibly breaks other apps). I only found this method buried in the think-tank post, and though it was suggested for the OP to fix the first post, it never was. Hopefully others who are on Cyanogen's ROM will appreciate the info.
Thanks for the tip! I'll add it to the first post.
Click to expand...
Click to collapse
I agree, the other threads over complicate it and cause problems for those who don't know what they are doing. If they learned how to do it themselves there would be less questions and complication.
But then again, now this is just another thread about nav. Really, they should all be locked and something like what is in the first post should be put in the informative links thread.
wanted to thank you for instructions, possibly a better forum wiulda been q&a, as I go there to find answers and help solve some =) other than that this does clear some things up such as the ro line. Like in the other post it says almost same thing but fails to mention the line to change. Etc..etc... this did catch my eye and I was was about to try another method for my buddies phone and this saved me of searching through a thread. My penies, again ty.
junker02 said:
0) Connect phone
1) Unzip zip to desktop
2) Run Part 1.bat
3) When prompted to press any key, do so; the phone will reboot
4) When your phone is running again, run Part 2.bat
5) When prompted to press any key, the installation process is done.
6) Make sure GPS is enabled
7) Open Maps and press OK
8) Press Menu
9) Press Directions
10) Enter an end point
11) Click Go
12) Just under "Show on map", click Navigate.
13) If prompted to install the voice codec, do so.
http://www.mediafire.com/?znzizmd1mmm
Click to expand...
Click to collapse
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?
scrappyabs2 said:
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?
Click to expand...
Click to collapse
I had no problems, but I did it myself:
from scratch (no map mods, orig build.prop):
adb remount
adb pull /system/build.trout.prop build.trout.prop
open it with notepad and edit the line
ro.build.fingerprint=tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys
so that it reads
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
save it
adb push build.trout.prop /system/
adb shell reboot
now reininstall google voice from market and reinstall maps with the new one
help me out here man, i dont have adb, i just use my phones terminal
bigstunta101 said:
help me out here man, i dont have adb, i just use my phones terminal
Click to expand...
Click to collapse
ok, even easier, do you have astro?
you can navagate to the /system directory, copy the build.trout file to your sdcard directory. mount your sdcard and edit the file with notepad. copy it back over to the /system directory and reboot
then install voice and maps
or try doing the same from your pc using droid explorer
http://forum.xda-developers.com/showthread.php?t=558108
haven't tried it either way way but it seems like it should work
scrappyabs2 said:
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?
Click to expand...
Click to collapse
Yes, that's exactly what it will do.
bigstunta101 said:
help me out here man, i dont have adb, i just use my phones terminal
Click to expand...
Click to collapse
The ADB app is included in the download. I'm not sure if it will work without the driver installed, but you can give it try and report back. Simply run the two .bat files and it will execute all the necessary ADB commands automatically.
Worse comes to worse, you would just need to install the driver for your phone.
Ok, here are the steps I took without adb, since comps at work do not allow USB write.
I uploaded the build.prop and maps.apk and sent them to my email using yousendit.com
Downloaded both into sdcard/download
Using "Root Explorer" navigated to /system and set it R/W (there's a button on the top)
Moved the build.prop to /system
Reboot
Install Maps
Reinstall GoogleVoice
Voila!
When I run the first batch file I get this errror: Device not found.
I've never gotten this message before. ADB was working fine for me a few days ago, before I reinstalled 4.2.5. Any ideas?
scrappyabs2 said:
When I run the first batch file I get this errror: Device not found.
I've never gotten this message before. ADB was working fine for me a few days ago, before I reinstalled 4.2.5. Any ideas?
Click to expand...
Click to collapse
Is your usb debugging enabled on your device?
Settings>Applications>Development
xavina said:
Is your usb debugging enabled on your device?
Settings>Applications>Development
Click to expand...
Click to collapse
Yes, its enabled. I swear I installed this navigation app on an earlier version of CyanogenMod and ADB worked just fine. Now it won't recognize my device. Please help me.
scrappyabs2 said:
Yes, its enabled. I swear I installed this navigation app on an earlier version of CyanogenMod and ADB worked just fine. Now it won't recognize my device. Please help me.
Click to expand...
Click to collapse
If you can't get the batch files to work, edit the batch files to see what commands are performed, and execute them in a terminal. There aren't that many.
junker02 said:
If you can't get the batch files to work, edit the batch files to see what commands are performed, and execute them in a terminal. There aren't that many.
Click to expand...
Click to collapse
adb remount says "error: device not found"
Here you go guys, safe simple and so easy a caveman can do it... (insert the, "If you break it, it's your own fault disclaimer here.)
Download the file in the first post of this thread.
extract the file on your hard drive and copy the build.trout.prop file and the Maps.apk, then put them on to your SD Card.
If you can't get this far....we have a bigger issue.
Then in terminal emulator type
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/build.trout.prop /system
reboot
When the device reboots then do this one in the terminal emulator
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/sd/app/*Maps*
rm /system/sd/dalvik-cache/*Maps*
rm /system/app/*Maps*
reboot
*Note: Someone might say that the reboot at the end of this code is not needed. That maybe, but it worked just fine for me.
Now using Astro, or another file manager, install the maps.apk from the sd card.
If prompted, install the voice. I had it from other programs.
Turn on GPS
Open the drawer
Click on Maps
Let the Maps program find you
Then click menu, directions
Enter the destination, and click go.
It should show
Code:
My location
<the destination address you entered>
Show on map
[B]Navigate[/B]
Thanks for making clear instructions for the terminal emulator [email protected]
Everyone please remember that one can only use the build.trout.prop file in the first post if they are also running Cyanogen 4.2.5 on the G1, else you run the risk of app errors and force closes. If you are running a different version of Cyanogen, make a copy of your own build.trout.prop file found in your system directory, and edit it.

mini how-to to _fake_ front camera for Google+ Hangouts

all you need to do, is get the permission XML for from face camera device rom (used the one from VIVO), and push it system, via recovery.
adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot
done
....
PROFIT
PS: this is NOT a flashable zip. but anyone wants to make one, be my guest
thanks to Kali- for the tips
Pushed the xml to the permisions folder with no problems. Ran fix_permissions and rebooted, doesn't appear to have done anything. I can verify that the xml is in the correct folder but google + just doesnt want to do hangouts.
Nexus One running CM7
Any ideas?
EDIT: I was wrong, I thought I would be able to start a hangout but once I found an existing one I was able to join no problem. THANKS!
Qestion
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
jossna said:
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
Click to expand...
Click to collapse
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Smtih said:
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Click to expand...
Click to collapse
Thanks, I try it, but doesn't work
This is how I got mine to work
There were some permissions issues and my phone can't adb anymore for some reason (seems common with the Captivate), so I did the following from Terminal Emulator:
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2
# chmod 777 /system
# cp /mnt/sdcard/Downloads/android.hardware.camera.front.xml /system/etc/permissions/.
# chmod 644 /system/etc/permissions/android.hardware.camera.front.xml
[Restart into recovery mode]
[Advanced]
[Fix Permissions]
And it worked! You just can't create your own Hangouts from the phone. You can join others though using your back-facing camera!
Thanks OP!
Jason Schoenbrun
jason schoenbrun gmail
-------------------
Why does xda developers require we create user names? If there's anyone who knows this, please let me know as I'm curious.
I haven't created a non-email username since the days of AOL. Now I have to make a dumb-sounding faux name like "hotmama2385" all over again? I really wish I could use my e-mail address as my persona. If I can't, at least I'd like to know out of curiosity why the design decision was made to exclude that possibility. of course as a protection from spambots I'd want some of my e-mail address hidden behind a CAPTCHA.
I know some people are privacy focused and/or want to be able to troll anonymously. So why not allow a username which can take whatever form we chose - AOL-esque IDs or an e-mail address - as most login services allow?
As an aside, I have the same question for Twitter, which is the reason I haven't signed up for it. I pushed off signing up for XDA by a couple of years until I absolutely had to because of this, and rarely log in because I can't remember that stupid username. (I just started to a little more because of LastPass.)
Nice work... I'll try this one...
hello,
how to fix permission?
with a terminal
I'm not sure what command that is specifically from a terminal, but you can type adb reboot recovery and then fix permissions via menu option once in recovery.
yep, but the problem I haven t a recovery mode. I want to say no menu.
I have an HTC evo 4g with CM 7.2RC1.
I implemented this fix, and rebooted, but still, when trying to do a video call, it stays on "video initializing" and never seems to finish. I have the latest skype from market.
What to do?
just maybe
So I installed the sdk tools, and opened cmd, and then cd to where adb is. I then copy and pasted the entire string "adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot" and pasted that into cmd is that all I do. I tried dong just "adb reboot recover" and waiting till it entered recovery, but then I couldn't do anything. after I pasted the entire string, my phone rebooted, and took a sec then started back up normally it seemed. So I think I did it correctly.
Perfect!!! Thanks, works like a charm on my Nexus One
great on arc s for hangouts
It's working great on arc s to create hangouts, but it still does not enable video chat in google talk.
I really don't understand why front camera is a pre-requisite for it. I shall be able to see at least the other's video if he has a front cam, even if they don't see me. Any way to workaround this issue of googletalk? (either to trick it to use front cam or just to display an empty frame, but receive other end's video).
I tried the same to see if it would work for Talk on my Defy, but no success

[Completed] can't get Radio3.apk back onto phone

Hi folks,
I removed Radio3 from /system/app because I was having an issue with my headphone jack and therefore the app wasn't useful (this is the stock FM Radio app that uses my phone's internal tuner).
Now, mysteriously, my headphone jack seems to be working again and so I wanted to put the Radio app back. Well, I've run into problems.
I have the original flashable firmware that I was using, so I mounted system.ext4 on my computer at /mnt/ and went to app/Radio3. Here, I found Radio3.apk and nothing more.
So, I've tried this three ways, one way is that I adb shell and then su. Then
Code:
# mount -o remount,rw /system
# mkdir /system/app/Radio3
Then I chmod and chgrp Radio3 so that it looks just like all of the other dirs in /system/app
Then I copy Radio3.apk into that dir and chmod and chgrp it as well. Reboot the phone and that's fine, but the app isn't installed, I don't see the icon in the app drawer. If I go to the apk in FileManager, I can click on it and the installer opens up, I say, sure install it and it says "App not installed" (what a helpful error message!?).
Okay, so I try another way, while still root, I say "pm install Radio3.apk", in this case, I get [INVALID URI].
Okay, so I try another way, this time I say exit and now, on my machine, I simply try to use adb to install the apk, "adb install -r Radio3.apk", in this case:
Code:
[email protected]:/mnt/app/Radio3$ adb install -r Radio3.apk
5446 KB/s (2667450 bytes in 0.478s)
pkg: /data/local/tmp/Radio3.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Does anyone have any advice on how to get my Radio app working again without reflashing /system? I don't want to reflash /system because I've removed a lot of bloatware and I don't want to have to redo that.
Thanks for any tips or tricks!
In case it helps, I've attached the Radio3.apk to this thread. EDIT: I couldn't figure out how to add a file to the thread, but I'll happily post it somewhere if someone wants to look at it. In any case, it's just the stock Radio3.apk from Sony for their Z3Compact firmware.
Problem solved.
I think I didn't have all of the perms and grps set correctly. I triple checked everything in /system/app/Radio3 and rebooted and I saw (app 1 of 1 optimizing upon reboot). Well, now I find the icon so I can say this issue is solved.
Unfortunately, trying to run the app force closed But that's a separate issue so I'm closing the thread.
Cheers,
--apexofservice
apexofservice said:
Problem solved.
I think I didn't have all of the perms and grps set correctly. I triple checked everything in /system/app/Radio3 and rebooted and I saw (app 1 of 1 optimizing upon reboot). Well, now I find the icon so I can say this issue is solved.
Unfortunately, trying to run the app force closed But that's a separate issue so I'm closing the thread.
Cheers,
--apexofservice
Click to expand...
Click to collapse
Glad you got it sorted
Regards
Sawdoctor

Categories

Resources