On Oct 21, 4:46 am, zhen guo wrote:
> why not imsi?
1. IMSI is tied to subscriber, not handset. There's definitely a
difference for SIM-card based phones, and likely to be one for non-SIM
phones also.
2. Like IMEI, it's not clear if non-phone devices (like the Archos 5)
will have an IMSI.
Str
why not imsi?
On Wed, Oct 21, 2009 at 4:55 AM, Wayne Wenthin wrote:
> wow replying to myself... So as I was reading other posts here I came
> across an idea. We (well I am) are talking about the ANDROID_ID as if it
> were a MAC. I haven't looked but if the phone supports Wi-Fi wouldn't it
wow replying to myself... So as I was reading other posts here I came
across an idea. We (well I am) are talking about the ANDROID_ID as if it
were a MAC. I haven't looked but if the phone supports Wi-Fi wouldn't it
need an MAC?
Going to look at the SDK docs now.
On Tue, Oct 20, 2009 at 12:
Sorry Mark I misread your earlier post. I don't know where I got a number
from ;-)
On Tue, Oct 20, 2009 at 12:00 PM, Mark Murphy wrote:
>
> RichardC wrote:
> > Given that people are rooting phones and producing their own custom
> > platform builds I cannot see how any field can be relied o
RichardC wrote:
> Given that people are rooting phones and producing their own custom
> platform builds I cannot see how any field can be relied on to be
> unique across all devices.
Good point. ANDROID_ID is stored in a SQLite database IIRC, so you do
not even need to replace the firmware to hac
Given that people are rooting phones and producing their own custom
platform builds I cannot see how any field can be relied on to be
unique across all devices.
--
RichardC
On Oct 20, 6:26 pm, Mark Murphy wrote:
> Wayne Wenthin wrote:
> > It doesn't appear to be. The Archos 5 is only returni
Wayne Wenthin wrote:
> It doesn't appear to be.The Archos 5 is only returning 4 bytes I
> believe. If someone that is more familiar with this could speak up it
> would be cool. I would assume that the ID's are governed by the OHA if
> they are truly unique.
ANDROID_ID is definitely more th
It doesn't appear to be.The Archos 5 is only returning 4 bytes I
believe. If someone that is more familiar with this could speak up it would
be cool. I would assume that the ID's are governed by the OHA if they are
truly unique.
On Tue, Oct 20, 2009 at 8:49 AM, Agus wrote:
> Is the value
Is the value ANDROID_ID a globally unique id like the MAC address?
reference:
http://developer.android.com/reference/android/provider/Settings.Secure.html#ANDROID_ID
On Mon, Oct 12, 2009 at 9:25 AM, Wayne Wenthin wrote:
> why not
> String Android_ID = System.getString(this.getContentResolver(),
Wayne Wenthin wrote:
> Is this something that someone with an archos can test? /looks at
> Mark. I know he has copious amounts of spare time. LOL
"Copious" isn't the word I'd use. ;-)
I'll try to look into it this coming weekend, when I do more
coding-level experimentation with the Archos.
Is this something that someone with an archos can test? /looks at Mark.
I know he has copious amounts of spare time. LOL
On Mon, Oct 12, 2009 at 9:25 AM, Wayne Wenthin wrote:
> why not
> String Android_ID = System.getString(this.getContentResolver(),
> android.provider.Settings.System.ANDROID
why not
String Android_ID = System.getString(this.getContentResolver(),
android.provider.Settings.System.ANDROID_ID);
What would happen if I tried the suggested method on an Archos 5 which
doesn't actually have a phone?
On Mon, Oct 12, 2009 at 9:19 AM, Yusuf Saib (T-Mobile USA) <
yusuf.s...@t-m
http://developer.android.com/reference/android/telephony/TelephonyManager.html#getDeviceId()
Yusuf Saib
Android
·T· · ·Mobile· stick together
The views, opinions and statements in this email are those of the
author solely in their individual capacity, and do not necessarily
represent those of T
13 matches
Mail list logo