Related
This has been solved! Please see around page 8 of this thread.
esmith972 said:
Here guys, all wrapped up.
Make sure you have CyanogenMod 4.2.3.1, by the way.
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) When prompted to install the voice codec, do so.
14) Enjoy.
http://www.mediafire.com/?lioyoy2ydzu
Click to expand...
Click to collapse
If you have no navigation option after the above steps try installing Google Voice from the market:
1wayjonny said:
AWESOME !!! Took another users post to install google voice and BAM the navigation button showed up!!!! Woot!
Click to expand...
Click to collapse
===============================================
This is a continuation of a discussion that started in this thread: http://forum.xda-developers.com/showthread.php?p=4918275
My best guess as to why navigation works in the emulator but not on the phone has to do with what kind of device the Maps application thinks it is running on.
For example, if you start maps and press menu->more->about and look at the "Platform" line, that will be different according to the device (emulator or G1 or other) that you are running on. What we need to change (I think) would be that setting.
According to this link, you can programatically get that string (I'm pretty sure they were talking about that string) through the API. Anyone more familiar with the API know where that string is stored?
Also, any other suggestions as to why it won't work on a real phone may be discussed in this thread.
What does platform say on the emulator? According to the info in that link, it should be null.
Cyanogen 4.3.2.1 Instructions http://forum.xda-developers.com/showpost.php?p=4921092&postcount=196
On my way to verizon to see what I can find out off the droid.... wonder if I can bring my laptop in and plug it up.... lol
[email protected] said:
What does platform say on the emulator? According to the info in that link, it should be null.
Click to expand...
Click to collapse
I fired it up to check. The exact string is "android:unknown-generic-sdk"
followinginsanity said:
On my way to verizon to see what I can find out off the droid.... wonder if I can bring my laptop in and plug it up.... lol
Click to expand...
Click to collapse
You should then just do adb pull /system C: and then bring it here. I'm sure they won't mind you trying to break their system
One thing I noticed is that it repeatedly references epc.tmobile.com as the provider. Let's hope they aren't using that and checking for verizon or this is a fool's quest.
Some interesting things to note:
The Version string of the Maps app is different in the emulator than on the phone as well.
Emulator: "3.2.0 (#3232) Web"
Phone: "3.2.0 (#3232) gmm-google"
Also, there was a blog post put up before 1.5 was released showing a way that you could spoof the ANDROID_ID on the phone by modifying a database (article here). I don't know if this is valid since at the end of the article he stated that they were supposed to fix it with 1.5.
Edit: I may have gotten ahead of myself. The ANDROID_ID string I think is not the correct one that I was looking for. That seems to be unique to the phone and not to the model, maker, whatever.
octobclrnts said:
Some interesting things to note:
The Version string of the Maps app is different in the emulator than on the phone as well.
Emulator: "3.2.0 (#3232) Web"
Phone: "3.2.0 (#3232) gmm-google"
Click to expand...
Click to collapse
Hmm mine actually says "3.2.0 (#3232) gmm-android-tmobile" for the version number... interesting.
[email protected] said:
Hmm mine actually says "3.2.0 (#3232) gmm-android-tmobile" for the version number... interesting.
Click to expand...
Click to collapse
I'm thinking that we're going to need someone to go to a Verizon store and see what the droid says there.
JAguirre1231 said:
I'm thinking that we're going to need someone to go to a Verizon store and see what the droid says there.
Click to expand...
Click to collapse
The question is, even if we knew what the droid said - how can we change our Platform string to match. It's clearly not reading off of the build.prop file (and neither is the device string in the about phone menu).
Maybe it's a database issue (the database gets initialized the first time the phone is booted to the values in the build.prop file?) that just needs to be wiped.
octobclrnts said:
The question is, even if we knew what the droid said - how can we change our Platform string to match. It's clearly not reading off of the build.prop file (and neither is the device string in the about phone menu).
Maybe it's a database issue (the database gets initialized the first time the phone is booted to the values in the build.prop file?) that just needs to be wiped.
Click to expand...
Click to collapse
Yeah, I know where your coming from. However, I think it would be easier if we at least knew what build we were aiming for
JAguirre1231 said:
Yeah, I know where your coming from. However, I think it would be easier if we at least knew what build we were aiming for
Click to expand...
Click to collapse
Well let's see... what do we know so far?
The version string shows up differently on different phones and the emulator shows up with a general one, but all have the same number. So it's probably not that, it seems to be building that from information it gathers elsewhere on the phone.
It's probably not reading which network is being used since that would block the emulator(which isn't running off the verizon network).
The only thing left I can think of immediately is the model string. That would actually make perfect sense, check against the model string to make sure that it's either the emulator or the droid. Otherwise turn off navigation. Changing that would be my first thing to aim for.
[email protected] said:
Well let's see... what do we know so far?
The version string shows up differently on different phones and the emulator shows up with a general one, but all have the same number. So it's probably not that, it seems to be building that from information it gathers elsewhere on the phone.
It's probably not reading which network is being used since that would block the emulator(which isn't running off the verizon network).
The only thing left I can think of immediately is the model string. That would actually make perfect sense, check against the model string to make sure that it's either the emulator or the droid. Otherwise turn off navigation. Changing that would be my first thing to aim for.
Click to expand...
Click to collapse
How tough is that to do?
Just wondering since if easy someone would of tried already.
Coderedpl said:
How tough is that to do?
Just wondering since if easy someone would of tried already.
Click to expand...
Click to collapse
No clue, probably need someone with experience making ROMs for that info. I'm guessing it has to be in some file somewhere. Seems highly unlikely they'd have done something as crazy as building that into the hardware.
Well, I modified cyanogen's build.prop file to include the lines below:
ro.build.id=ECLAIR
ro.build.version.sdk=5
ro.build.version.release=2.0
ro.product.name=sdk
ro.product.device=generic
ro.product.manufacturer=unknown
As well as put the Maps.apk into the system/app folder in his update file. Then I resigned the file, put it on my SD card and wiped my phone. I installed the "new" rom and booted up. The maps app works exactly as it should sans navigation options. The Version string i have now is the "3.2.0 (#3232) gmm-androidd-tmobile" one but the Platform string is unchanged.
I noticed in the "About Phone" menu, the Model Number (T-Mobile G1) was unchanged but the Firmware version said "2.0" and I'm pretty sure it said "1.6" before.
octobclrnts said:
Well, I modified cyanogen's build.prop file to include the lines below:
ro.build.id=ECLAIR
ro.build.version.sdk=5
ro.build.version.release=2.0
ro.product.name=sdk
ro.product.device=generic
ro.product.manufacturer=unknown
As well as put the Maps.apk into the system/app folder in his update file. Then I resigned the file, put it on my SD card and wiped my phone. I installed the "new" rom and booted up. The maps app works exactly as it should sans navigation options. The Version string i have now is the "3.2.0 (#3232) gmm-androidd-tmobile" one but the Platform string is unchanged.
I noticed in the "About Phone" menu, the Model Number (T-Mobile G1) was unchanged but the Firmware version said "2.0" and I'm pretty sure it said "1.6" before.
Click to expand...
Click to collapse
You would be right, cyanogen only makes builds from soure code. And the source code for 2.0 hasn't been released yet. So, obviously we need to have a modified build.prop before we flash a rom, or it won't read it correctly
I was wrong. I had that same modified build.prop on my phone before I wiped, I just hadn't noticed that the firmware version number had changed. Perhaps I didn't modify the right valued to also get the model number to change.
I have decompiled Maps.apk using dedexer 1.7. Here is all the stuff it gave me. I used dexdump last night and it gave me something similar. Im using notepad++ to search through all the files for keywords but I cant find anything interesting. Maybe you can...
http://rapidshare.com/files/305162283/Maps.apk-dedexed.rar.html
staulkor said:
I have decompiled Maps.apk using dedexer 1.7. Here is all the stuff it gave me. I used dexdump last night and it gave me something similar. Im using notepad++ to search through all the files for keywords but I cant find anything interesting. Maybe you can...
http://rapidshare.com/files/305162283/Maps.apk-dedexed.rar.html
Click to expand...
Click to collapse
Cool I'll go through it in a min. and see if I can find anything interesting.
edit: opened it up and there is googlenav stuff com/google
There is also an android folder too. I'm going to look there first
As I'm going through these I found that Google has these things filled with static locations. Haven't found any that seem to lock it down, but that's not to say there aren't any
I just discovered this by casual browsing a few mins ago by reading a post saying this wasn't possible. I said bs and went looking for solution.
I'm sure some of you already know about this from it being mentioned in threads here or there. I wanted to make a dedicated thread for those searching for the answer that much easier. Without further adieu, here it is.
Download an app called Market Enabler from softpedia: http://handheld.softpedia.com/get/Internet-Utilities/Misc-Shopping/MarketEnabler-88713.shtml
Install via your preferred method IE Astro, Estrongs, adb install, whatever.
From here, everything should be self-explanatory, but in case it isn't. Open the app; select the "save current settings" button.
Go to "settings list" tab and choose alternative. I picked [us] T-mobile (cause it's the only US option). Don't ask me what happens with the others. I didn't try.
Bam, you're done. No reboot needed. Requires root with 2.1/2.2. I have only used this with CM6.
Enjoy.
theresthatguy said:
I just discovered this by casual browsing a few mins ago by reading a post saying this wasn't possible. I said bs and went looking for solution.
I'm sure some of you already know about this from it being mentioned in threads here or there. I wanted to make a dedicated thread for those searching for the answer that much easier. Without further adieu, here it is.
Download an app called Market Enabler from softpedia: http://handheld.softpedia.com/get/Internet-Utilities/Misc-Shopping/MarketEnabler-88713.shtml
Install via your preferred method IE Astro, Estrongs, adb install, whatever.
From here, everything should be self-explanatory, but in case it isn't. Open the app; select the "save current settings" button.
Go to "settings list" tab and choose alternative. I picked [us] T-mobile (cause it's the only US option). Don't ask me what happens with the others. I didn't try.
Bam, you're done. No reboot needed. Requires root with 2.1/2.2. I have only used this with CM6.
Enjoy.
Click to expand...
Click to collapse
i wish you had posted this yesterday, I spent a good couple of hours fixing this, and posting rather long winded howto manually do this on cm6.
Haha, just tried this, works great, very quick, but in case it isn't obvious - it gives you the t-mobile apps in the market, and takes away the sprint ones. That's no biggie if you're on cm6 though, which doesn't have any sprint apps lol
Edit: haha fyi t-mobile social buzz works great on here, it's like friendstream, but has myspace support. And it doesn't have a widget sadly... Make sure to install t-mo social service first.
Sent from my CDMA Hero, sucka!
codejunkie78 said:
i wish you had posted this yesterday, I spent a good couple of hours fixing this, and posting rather long winded howto manually do this on cm6.
Click to expand...
Click to collapse
I'm intrigued. Link?
edit: I found your post. Could your method work for Sprint users by substituting sprint for another carrier? also confused as to the origin of the eri.xml file. googling it i come up with a lot of verizon forums and talk.
theresthatguy said:
I'm intrigued. Link?
edit: I found your post. Could your method work for Sprint users by substituting sprint for another carrier? also confused as to the origin of the eri.xml file. googling it i come up with a lot of verizon forums and talk.
Click to expand...
Click to collapse
in theory it should work for sprint users to. i played around with it a bit, so far i changed it from Sprint to my carrier then to Verizon, and back to my carrier.
the build.prop file tells the market your carrier id, then google adds the market tab for your carrier.
i found out about the eri.xml file in the darchdroid2.8 thread, it changes the name displayed on the lock screen and the status bar.
so i'd say a sprint user could change the build.prop file to another carrier and change the eri.xml to sprint and it would work just fine.
BBC just released their official News app for Android, but it's not available for US in the Market.
Can someone [probably in the UK] share the APK???
http://dl.dropbox.com/u/24917729/bbcnews.apk
Is there a way to get this to work in the USA?
c33v33 said:
Is there a way to get this to work in the USA?
Click to expand...
Click to collapse
Yeah mine just says "Application not installed" on my HD2 running gingerbread.
Edit: With market enabler I was able to change my country ID to a UK one and eventually the market website recognized my phone as elligible. I was able to install it from my PC just now.
Double edit: The live stream portion of the app still doesn't work - it says "not available in your area" but the text news stories work.
They just released it? I've had this app for the past 6 months...I live in Canada, not sure if that matters?
08cherd4 said:
They just released it? I've had this app for the past 6 months...I live in Canada, not sure if that matters?
Click to expand...
Click to collapse
This is the official BBC News App. The other one is not.
squish_123 said:
Yeah mine just says "Application not installed" on my HD2 running gingerbread.
Edit: With market enabler I was able to change my country ID to a UK one and eventually the market website recognized my phone as elligible. I was able to install it from my PC just now.
Double edit: The live stream portion of the app still doesn't work - it says "not available in your area" but the text news stories work.
Click to expand...
Click to collapse
I'd never thought of using Market Enabler for stuff like this. Very nice. Thanks for the tip.
I ended up changing it to O2, number 23410. Installed without a hitch (or reboot).
mercado79 said:
I'd never thought of using Market Enabler for stuff like this. Very nice. Thanks for the tip.
I ended up changing it to O2, number 23410. Installed without a hitch (or reboot).
Click to expand...
Click to collapse
I was pretty surprised a refresh of my browser did the trick - pretty neat indeed. That's the same code I used as well .
Not sure why the apk in the Dropbox link (633kb) didn't work, but here's the copy from my phone (591kb):
http://www.mediafire.com/?whi03mz89j5htua
Thanks, it works
Edit: Dammit, Live news and other videos doesn't work
No scrolling widget
Same here, but yours worked for me on my Atrix and Xoom Much appreciated.
Now, BBC just needs to give some real Honeycomb love.
mercado79 said:
Not sure why the apk in the Dropbox link (633kb) didn't work, but here's the copy from my phone (591kb):
http://www.mediafire.com/?whi03mz89j5htua
Click to expand...
Click to collapse
It works. First time mine phone says "Application not installed" and second time the application was installed without any problems. Link to the livestream is missing unfortunately . Thanks for the APK File. Looks like a great app. I would consider about moving to the UK. lol.
As others have said, no live stream, but it works well otherwise.
any ideas how to make it landscape?
Hi guys,
There is a new BBC News app for tablets. Can someone from UK download it and post it here?
market.android.com/details?id=bbc.mobile.news.uk&feature=search_result#?t=W251bGwsMSwyLDEsImJiYy5tb2JpbGUubmV3cy51ayJd
Thanks
no one? c'mon guys
Hi all,
I have a quite annoying issue with my Belgian Transformer.
There is no YouTube app (no widget either) on it! Apparently it is due to the stupid Belgian copyrights protection organisation, called SABAM.
When I search for it in the Market, I can't find it. When I click on a direct Market link to the app, I can find the phone version, but when I try to install it, the Market can't find it anymore.
I also tried a hint from someone, he said to search for the wigdet, and then the app would show up in the app drawer.
I installed the Youtube 2.1.6.apk (for phones) on it, and it works, but it does not have the nice Honeycomb interface.
Is it possible to exctract the application from an onther TF (rooted or unrooted) so I can install it on mine?
If yes, would someone be that nice?
Thanks!
I hope it's not against the rules for me to post this, but please delete it if it is.
This is the YouTubeTablet.apk extracted from the Prime_v1.2_US ROM (I just happened to have that one on my PC), it should work for you. If it's not what you want, head over to the development section, download one of the ROM's and extract the apk.
http://www.mediafire.com/?reg913u9uwqse6w
UKseagull said:
I hope it's not against the rules for me to post this, but please delete it if it is.
This is the YouTubeTablet.apk extracted from the Prime_v1.2_US ROM (I just happened to have that one on my PC), it should work for you. If it's not what you want, head over to the development section, download one of the ROM's and extract the apk.
http://www.mediafire.com/?reg913u9uwqse6w
Click to expand...
Click to collapse
Thanks for the help, I'll try it this evening !
@i_machine: Look for "Market Enabler" in market and set it to US. Then open market again and see if you can find Youtube now
P.S.: F**k those governments that try to censor your daily life! Stay out of my affairs, state! I'm the one who's paying you!
nachtschicht said:
@i_machine: Look for "Market Enabler" in market and set it to US. Then open market again and see if you can find Youtube now
P.S.: F**k those governments that try to censor your daily life! Stay out of my affairs, state! I'm the one who's paying you!
Click to expand...
Click to collapse
Thanks for the tip, but this requires root access, which I'm not planning to do in the near future.
@I_machine,
Where did you buy your TF ?
I got mine imported fom US so no issues with stupid Sabam...
Nice to know a fellow Belgian is using the TF
AFAIK there is are no separate firmware update for BE. Don't know how they will detect that your device is a SABAM'ed one. Did you upgrade to 3.1 already?
Or will it just filter Youtube out as soon as you set your location to BE?
Tutti-frutti said:
AFAIK there is are no separate firmware update for BE. Don't know how they will detect that your device is a SABAM'ed one. Did you upgrade to 3.1 already?
Or will it just filter Youtube out as soon as you set your location to BE?
Click to expand...
Click to collapse
I have an imported US model, youtube works fine on mine, but indeed in the market it isn't available so i guess future Youtube updates are also an issue for me I Guess.
regards
Kef
I do find it strange that 1 TS bought in Belgium does not have the youtube app/widget where mine also bought in Belgium does have the youtube app/widget installed by default.
Am happy to see that I_machine finally got his app
I_Machine and had already a discussion about this subject on a dutch forum.
Tutti-frutti said:
AFAIK there is are no separate firmware update for BE. Don't know how they will detect that your device is a SABAM'ed one. Did you upgrade to 3.1 already?
Or will it just filter Youtube out as soon as you set your location to BE?
Click to expand...
Click to collapse
haha, maybe thats the cause, you just give me the answer i think.
Difference between me and I_machine is that i choose for the English installation and he obvious choose for the dutch (Belgian) configuration.
Only way to not install that youtube app is indeed looking for country specific setting.
same problem here.
Belgian transformer french and no YouTube :-(
Tryed toi install thé apk but. I have a message application ont installed
Someone could help ?
Thxxxx
I bought mine at mediamarrkt in Brussels... left it in English. Was able to install YouTube without a problem. I have 3.0.1 and SKU HRI
Same problem for me too.
If anyone has a working youtubetablet.apk.
I have 3.2 and sku TB
Thanks in advance
Me too. No youtube app (Belgian TB) bought at Makro and installed Dutch.
Today on 3.2; notice that when I open a non-tablet app and the screen resizes, when I leave the app and go to the home screen, one third of the bottom screen keeps on 'flashing' and is unreadable until I open another app and then go back to the home screen.
I've uploaded the latest version of the youtube app here:
http://ubuntuone.com/p/18j6/
Sorry this one does not work on the tablet. This the one for Android 2.x
I think we need youtubetablet.apk and youtubetablet.odex.
This one worked for me:
http://forum.xda-developers.com/showpost.php?p=15817110&postcount=19
I'm now on 3.1 rooted.
Yes thank you It works on 3.2 unrooted
Thanks Dauntless, version works just fine!
I'm using a Chinese version Nex S on T-mobile in the US. It works almost flawlessly but one thing keeps bugging me. When there are incoming calls, vivo dialer app always recognizes the US phone numbers as Chinese numbers. It sometimes returns a Chinese city name under the phone number sometimes just display "unknown attribution". I tried to replace the dialer app but it was not very successful. In Chinese forum, someone mentioned that all phone number attribution data are saved in a databased called numberdb2.bin in Attribution folder. I was able to locate the file but don't know how to open or edit it. I was curious if a global version Nex has a database that covers the US. Can any global version user please post the numberdb2.bin file from they phone? I will definitely replace the file and report back the result.
I have the exact same problem. Anybody know how to fix this?
dstarr said:
I have the exact same problem. Anybody know how to fix this?
Click to expand...
Click to collapse
I don't mean to be a smart-ass, but sell it and buy the international version.
See if you can get the international *.bin file from a forum member then copy it into your folder. Keep us updated.