Designing a barcode app which doesnt sign your life away

by DManzaluni » Tue, 29 Mar 2011 10:23:52 GMT


Sponsored Links
 Has anyone designed an app which scans barcodes (a shopping app) which
doesnt force you to let Google track your every move (whether the app
is on or off, working or not etc etc) when you have installed it?

I installed Copilot and before getting it running, my smartphone
demanded that i let google track my every move before running SOMEONE
ELSE's GPS app!  In fact when I carefully didnt agree to this, my G2
did let me into the program and presumably interact with Copilot's
transponders (meaning, I suppose, I don't know whether Google is or
isnt tracking me!)

Or can I consciously turn off this tracking feature for whenever I
haven't got such app running? I am nervous about this AND ALSO am on a
very limited data plan. I dont want anyone using my limited usage for
their own purposes.

-- 



Re: Designing a barcode app which doesnt sign your life away

by lbendlin » Tue, 29 Mar 2011 11:21:48 GMT


 Very refreshing. You may want to read up on how cellular networks work. 
Google is just a third party in that game. The cellco-s know pretty well 
where you are, even if your phone is on standby, and even if you have 
declined Google's request. Don't want to be tracked? Don't use a cellphone.

-- 


Sponsored Links


Re: Designing a barcode app which doesnt sign your life away

by lbendlin » Tue, 29 Mar 2011 11:24:51 GMT


 oh, and "Barcode Scanner" v3.53 in the Android market is not using location 
at all.

-- 



Re: Designing a barcode app which doesnt sign your life away

by Maps.Huge.Info (Maps API Guru) » Tue, 29 Mar 2011 12:01:54 GMT


 "If you decline, network location won't be enabled at all"

It's just disabled on the device itself. The carrier can still track
you if they want or have a warrant to do so. There's no way except
turning the device off or sticking the thing in a Faraday cage to stop
that.

As another poster mentioned, if you don't want to be tracked, just
don't carry a cell phone. It's that simple.

-John Coryat

-- 



Re: Designing a barcode app which doesnt sign your life away

by Nathan » Tue, 29 Mar 2011 12:09:06 GMT


 It's not specific to the app. It's something that comes on when you
enable network location. Google wants to collect anonymous location
data. If you decline, network location won't be enabled at all.

Nathan

-- 



Re: Designing a barcode app which doesnt sign your life away

by DManzaluni » Thu, 31 Mar 2011 04:33:31 GMT


 



Interestingly enough it was barcode scanner 3.53 which prompted me to
put out this thread precisely because it  felt it necessary to put out
a strong legal warning mandating that I let google track me even when
the app is off in future (even though I know full well that it can get
my location just by looking to the location of the cell tower I am
using). Now I learn that it doesnt even do network location!

-- 



Re: Designing a barcode app which doesnt sign your life away

by lbendlin » Thu, 31 Mar 2011 09:49:08 GMT


 This is slightly off topic but here's a nice little story from Germany

 http://www.zeit.de/datenschutz/malte-spitz-data-retention 

-- 



Re: Designing a barcode app which doesnt sign your life away

by DManzaluni » Fri, 01 Apr 2011 09:43:39 GMT


 Interesting and it proves both what I was saying about using those
facts in court and how productive you can be and how much ground you
can cover when there arent any speed limits on the roads.  There dont
appear to be any white bits while he is in the air.

(It isnt really off topic although what I was asking about was the
google legal warning about them doing this, -  and while you arent
using their apps)




-- 



Re: Designing a barcode app which doesnt sign your life away

by lbendlin » Fri, 01 Apr 2011 09:51:12 GMT


 to (half) answer your original question - you can disable data services in 
your phone settings. Settings...Wireless and networks...Mobile network 
settings...uncheck "Data enabled"

-- 



Re: Designing a barcode app which doesnt sign your life away

by DManzaluni » Mon, 25 Apr 2011 22:07:53 GMT


 Anyone notice how this subject matter has suddenly become a supposedly
hot topic in the media recently with continuous time given on all
channels on TV to the recent revelation that the iPhone stores all
sorts of personal data in a hidden file on the iPhone!

With whole countries like South Korea suddenly being spurred to take
action to see if Apple doing this is illegal, to me, the only
surprising bit was that the file is apparently unused..

No one seems to have noticed that the Google user agreement demands
that you let them do this and much more before you can use an Android
phone for lots of non-google apps as I suggested in the OP.

As I have suggested, I dont know why,   but I have no problem with my
carrier doing this but somehow it seems odd for Google to remind you /
demand constantly that you let them do this every time you install a
new non-google app.   Anyway it is I suppose reassuring that you can
obviously turn this off.

Most of the context of all this is in the field of private banking
where these smartphones are being used for all sorts of REALLY
sensitive information and they are quite easy to hack into: I wonder
if the answer to any of this lies here:

 http://www.pinoyview.com/video/c9739347688571d/Privacy-Enhancing-Technologies-for-Mobile-Applications& ;source=video&vgc=rss&usg=AFQjCNERCDN6o1giryxTIMnGGlsReHBLLw




-- 



Other Threads

1. game source code

HI guys,

 would you share with me where can i get some android game souce code
like "angrybirds"...?

 i want to develop the game, but i don't know how start?

-- 

2. What is the recommended resolution/aspect ratio for android graphics

Hi All, I'm trying to write an application that will work well on all
screen sizes, for that I have my graphic designer produce images that
are in the requested dpis for each directory (Low density (120), ldpi,
Medium density (160), mdpi, High density (240), hdpi, Extra high
density (320), xhdpi) however, they want to know at which resolution
and aspect ratio each image should be, after looking around the
android documenation, namely: 1)http://developer.android.com/guide/
topics/resources/providing-resources.html#AlternativeResources
2)http://developer.android.com/guide/practices/screens_support.html I
came up with the following information: It is not exact that android
supports 3 screen sizes, android is an OS that can run virtually on
any screen size but there are some screen sizes that are more common
than others, these are demonstrated in the table below (taken from
http://developer.android.com/guide/practices/screens_support.html)

Table 1. Screen sizes and densities of emulator skins included in the
Android SDK. Low density (120), ldpi Medium density (160), mdpi High
density (240), hdpi Extra high density (320), xhdpi Small screen QVGA
(240x320)
Normal screen WQVGA400 (240x400) WQVGA432 (240x432) HVGA (320x480)
WVGA800 (480x800) WVGA854 (480x854)
Large screen WVGA800* (480x800) WVGA854* (480x854)
Extra Large screen

It worth noting here that even though it seems that there is no
correlation between these screen sizes, there is a 3:4:6 scaling ratio
between the three densities, so a 9x9 bitmap in ldpi is 12x12 in mdpi
and 18x18 in hdpi (see
http://developer.android.com/guide/topics/resources/providing-resources.html#AlternativeResources).

We can see some more information on what the screen sizes mean here:

Screen size small: Screens based on the space available on a low-
density QVGA screen. Considering a portrait HVGA display, this has the
same available width but less heightt is 3:4 vs. HVGA's 2:3 aspect
ratio. Examples are QVGA low density and VGA high density. normal:
Screens based on the traditional medium-density HVGA screen. A screen
is considered to be normal if it is at least this size (independent of
density) and not larger. Examples of such screens a WQVGA low density,
HVGA medium density, WVGA high density. large: Screens based on the
space available on a medium-density VGA screen. Such a screen has
significantly more available space in both width and height than an
HVGA display. Examples are VGA and WVGA medium density screens. xlarge: Screens that are considerably larger than the traditional
medium-density HVGA screen. In most cases, devices with extra large
screens would be too large to carry in a pocket and would most likely
be tablet-style devices. Added in API Level 9.

We can also support specific aspect ratios, as defined here:

Screen aspect long: Long screens, such as WQVGA, WVGA, FWVGA notlong: Not long screens, such as QVGA, HVGA, and VGA

-- All of this however, is not enough to answer the simple question of
what the resolution should be on those images - can they all be cut
from the same high res image or should they be re-done for each dpi
since the aspect ratio is different?
 Thanks!
P.s. To clarify, I'm talking about images that should take up the
entire screen - images such as backgrounds etc, and not just regular
images

-- 

3. Populate Spinner from database

4. Canvas vs OpenGl drawline speeds

5. Thickness strikethrough

6. How to setImageViewUri in Widget using getFileStreamPath()?

7. Receiving phone calls regarding Android Market billing issues?