Welcome to Esato.com




Google Maps on K850


Click to view updated thread with images




Posted by plankgatan
which version works best on k850 ???

im curious to test google maps, seems quite cool




_________________
I K850, W810 & T29
------------------------------------
http://www.flickr.com/photos/21179102@N07/
(t610, t630, k700, k750, k800, k810)



[ This Message was edited by: plankgatan on 2008-04-02 10:48 ]


Posted by masseur
thats a native version for windows mobile devices and so will not work on the K850

I'm running this on my TyTN II and it is quite good!

edit: ah, I see you removed the link you posted!

_________________
Unless I'm very much mistaken...
A-ZoTT

[ This Message was edited by: masseur on 2008-04-02 10:50 ]

Posted by plankgatan
he he.. i noticed that.. i change the post like you see.

can you please give me a link where to download this version ??

thanks

Posted by himlims_nl
www.google.com/gmm

Posted by masseur
http://www.google.com/mobile/gmm

Posted by Supa_Fly

On 2008-04-02 11:51:08, plankgatan wrote:
he he.. i noticed that.. i change the post like you see.

can you please give me a link where to download this version ??

thanks



it eats up data QUITE a bit! But I think you're gonna LOVE it!

Cheers.

Posted by tranced
so does m.youtube.com. that's why the tell you to upgrade your data plan to an unlimited one.

Posted by vegetaleb
Do you use it with WAP?
Because WAP is kinda slow for those stuff no?

Posted by Supa_Fly

On 2008-04-05 11:46:49, vegetaleb wrote:
Do you use it with WAP?
Because WAP is kinda slow for those stuff no?


WAP doesn't have any inherent "speed" that you relate to it. The speed association you relate is based on your data medium (GPRS/EDGE/3G/HSDPA) and your network conditions (Roaming, signal strength, but most likely How Busy the network tower your on; or gateway behind it GGSN). Most WAP sites are VERY fast to load because the "content" & "structure" adhere to an older web standard; WML. Tables are usually omitted in the WAP 1.1 (select WAP on Esato and you'll see what I mean - there is "usually" hardly any color if any at all used. So WAP sites WILL load quickly. If the site takes long to load - then either certificates are being used/loaded/not matching or outdated - like banking sites. But I STILL stand by my definition of WAP not having any speed.

Mobile sites like the m.siteaddress.com (or m.youtube.com) are based on xHTML or cHTML and are VERY modern. These mobile sites are more suited for modern phone browsers (say the past 2yrs or less). Now because of the new code; we SE users will have to be especially careful on jsut how many we load or frequency during surfing. Remember that - depending on the model - SE phones have a NetFront browser using limited cache (1MB older phones like W810/K790a/K800 vs 1MB + 3MB for K850i or other A200 phones).




Posted by max_wedge
WAP is largely being replaced by xhtml or chtml, or even full html.

WAP (Wireless Application Protocol) is simply a set of standards that define how a device will access data on the internet using a mobile phone. WAP was designed when screens were monochrome 1 line x 10 character screens! WAP handsets evolved to encompass slightly better hardware, for example 128x128 screens with colour and images.

WAP browsers reads WML (wireless markup language), so WAP is not a transmission medium (or speed as prom1 says) but a standard for viewing websites that are written in WML. Hence, a website written in WML is called a WAP site.

A WAP phone is a phone with a WAP browser for viewing WML websites that uses GPRS to transfer the data from the WAP site to the phone. Actually in the very early days, before GPRS, WAP used a timed CSD connection to transfer the data. So WAP is basically independent of the transmission medium.

Most mobile websites now use xhtml which is a much more flexible and powerful markup language than WML. So technically there are very few WAP sites around anymore.

Esato mobile site is written in xHTML.

Because of the resource restrictions of mobile phones, xHTML is much tighter than HTML (for example you can't leave any tags open in xHTML) but otherwise it's very similiar to HTML. Most of the commonly used tags are identical.

So the question of speed is answered by what type of data connection you have and how much capacity is spare on the network, ie: 3G, 2.5G, HSDPA etc.

@prom1, hope you don't mind me re-iterating most of what you have already said, just thought I'd throw in a bit of historical
_________________
Tricks and Tricks for K800 File System Tweaks for K750

[ This Message was edited by: max_wedge on 2008-04-08 08:46 ]

Posted by max_wedge

On 2008-04-05 05:43:50, Prom1 wrote:
it eats up data QUITE a bit! But I think you're gonna LOVE it!


Hell Yeah, on a test once I used about 2MB of download for only 5 minutes of browsing. That was at 2.2 cents per Kb. $45 worth The data was on my cap, and I was well under on calls that month so didn't end up "paying" for it as such.

That was on a gprs connection (no more than 44Kbps) and a 320x240 screen. So it's not too bad but you need reasonable data rates to use it often. And browsing on X1 with 800x480 pixels will multiply that data use considerably



Posted by plankgatan
but cant you use turbo 3g connection when you using google maps ???

Posted by max_wedge
yes but even at gprs speeds it was usable. On a 320x240 resolution handset, google earth throughput is probably not much more than about 100-200Kbps

Doing some pretty intensive Google Earth browsing on my PC, on a 10Mbps connection, at 1280x1024 resolution, google data throughput (from Google server to my PC) never went over 112KB/s (even though my connection is faster than that) and averaged 55KB/s. That's an average of 400 or so Kbps, so a HSDPA 3G connection would be better than a normal 3G for laptop google earth browsing, but probably doesn't make much difference having HSDPA on a phone with a 320x240 screen.

But maybe someone with actually experience of 3G compared to HSDPA google earth browsing can say for sure.


Click to view updated thread with images


© Esato.com - From the Esato mobile phone discussion forum