android-discuss, Forcibly using 3G or CDMA network even though wi-fi is available.

 One of the reason would be - when switching 3g/WiFi takes place
network
connections are dropped




> >

 They can be dropped for many other reasons as well, such as losing cell
signal.  You must write an app that robustly deals with such a situation,
this is standard behavior for a phone.






> > >

 Apps that need to route all client-server communication through the
operator infrastructure. One reason for this is that for example for
client-> server HTTP requests, the operator will add various
parameters to the request (like subscriber ID/name/phone
number/whatever) so our server side app will know information about
the actual subscriber who is making the request. Another reason is
operator billing - if the request from client -> server goes through
the operator servers (eg over 2g/3g), the subscriber can be
automatically billed for the services that he uses (so the cost of
whatever services the user uses, will automatically show up on his/her
phone bill.. more specifically - an app that has a "buy" button and
when pressing it, a request is made through the operator servers to
the app provider servers and the user gets the content from the app
provider and the cost is added to the phone bill by the operator. For
this to work, the request MUST go over 2g/3g )

Currently the only solution for these kind of applications is to
present the user a dialog "Please turn off WiFi if you want to use
this application" and that's not really nice from the users point of
view :(

Tauno




>>

 For the same reason you added the "feature" that allows the MMS
application to switch to a specific APN even when WiFi is
available..... lots of mobile apps require you to go through a
specific APN - for billing purposes amongst other things.

Dongjoon: You could check if the same crazed hack that allows the MMS
application to work can be used by you?

Br
Jens




> >

 The application needs to get some information from operator's server.
And operator want us to make use operator's network, not wifi, even
though wifi is available.

It's very difficult to find solution. May I need to search alternative
way.

Anyway, thanks for your advice.

Best regards,
Dongjoon.





> > >

 For development reasons, I have to switch wifi off to make use of 3G to
route my requests to a domain name that then maps to one of my internal
servers (using no-ip.com to forward a dns name to my provider IP.. and
setting up my router to forward http requests to proper server). I can also
do this by using the internal IP of my computer, but then I have to set up
hosts and such to get it out to find the dns entry that then routes it back
to my ip. It's a development issue only.. but thought I'd share that issue.
I manually switch it off myself tho, so not quite the same thing.

2010/2/2 Dongjoon Lee <sky...@gmail.com>




> > > >

 ere's another one - it bit me just the other day.



- I was at a restaurant that offered a free HotSpot.  (although

exactly the same scenario would apply if I was staying at many hotels,

or at an airport, or any number of other locations that offer "free"

WiFi)

- I told my phone to connect to the HotSpot.  It attached to the AP

and got an IP address.

- At that point the phone "preferred" to use WiFi - even though all I

was able to see was the login page for the WiFi service.

- Suddenly my app is unable to communicate with servers - I had to

disable WiFi to get it to use the cellular network.



Now, you could argue that all I needed to do was open my browser and

accept the terms of the HotSpot and I'd have access to (at least some)

data services, but:



1) What if my app doesn't connect using a "well known" port?  (i.e.

one that the HotSpot will *probably* allow... HTTP/S, IMAP, SMTP,

POP3)

2) What if my application communicates with my carriers servers which

are inside their walled-garden, and for obvious reasons are only

accessible via the cellular network?

3) What if the AP's internet connection is down?



I suggest that Android be extended to allow an application to specify

(and this is only a start) whether it wishes to take advantage of WiFi

should it be available.  That would allow an application to choose to

"pass" on a WiFi connection and continue to use cellular data.

(obviously the default would be the status quo)



Its not like you'd be leading in this area - many (most?) of the other

mobile platforms allow an app (either programmatically or via

configuration) to specify which data services it will use - regardless

of the presence of other options.



Doug





On Feb 2, 9:35 pm, Kevin Duffey <andjar...@gmail.com> wrote:

> > > > >

 ------------------------------

MMS cannot be sent over wi-fi.Carriers network is mandatory to send/recv.
The MMSC need to identify from/to the message coming going and it wont be
possible while using wi-fi.
So its required to switch to 3g or CDMA even if wi-fi is available.


2010/2/3 Dongjoon Lee <sky...@gmail.com>




> > > >

 hy not add a feature request?  Just talking about it here does not

get it considered for future releases.



http://code.google.com/p/android/issues/entry



On Feb 2, 11:35 pm, Doug <dougforp...@gmail.com> wrote:

> > > > > >

 Uh yeah, that's why they added that particular crazed hack - an
undocumented call to #startUsingNetworkFeature(int, String).

On 3 Feb, 09:31, Anonymous Anonymous <firewallbr...@googlemail.com>





> > > > >

 I added a request feature:
 http://code.google.com/p/android/issues/detail?id=6518 








> > > > > >

 Oh, that's nice:)









> > > > > > >