does the cell id is unique?

by E.D.I » Thu, 17 Apr 2008 13:48:47 GMT

Sponsored Links
 i wonder if i can use the cell id as an ident in a DB on a server...

does the cell id is unique?

by Rui Martins » Thu, 17 Apr 2008 17:23:36 GMT

 Cell ID identifies the current GSM cell where the mobile phone is

Many phones can be using the same cell !

Your phone only uses one cell at once, but can negotiate data with
more than one, when doing transfer from one cell to the other.

Cell IDs, as far as I known can be reused in different countries.

So it's probably not suited to what you need.


Sponsored Links

does the cell id is unique?

by [EMAIL PROTECTED] » Thu, 17 Apr 2008 21:34:42 GMT

 Not sure if is available through Android, but you could use IMEI or
the phone number to identify the phone (the best one will be the IMEI
since is unique)


does the cell id is unique?

by [EMAIL PROTECTED] » Fri, 18 Apr 2008 17:03:18 GMT

 You should be able to build a longer string with country and carrier
and cell id that is unique.


Other Threads

1. Why isn't the "standby" instruction able to stop the thread?

Dear  All,
            Recently, I have tried to know what would happen to an
alive thread, when the device goes to sleep. I program a simple
activity that will create and start a thread printing "HERE AM I"
repeatedly through Log.d. I expect the thread would be stopped after I
"echo standby > /sys/android_power/request_state." The screen is off,
but the thread still keeps alive and prints out "HERE AM I." I don't
know why the thread can't be stopped. I test this through emulator
(1.5cupcake) and G1(1.1?), but the results are the same. Could anyone
give me some suggestions or hints about this question? Thanks in

           The following is my simple activity.

ublic class TestServiceDroid extends Activity {

        PowerManager.WakeLock lock;
        Thread h;

    public void onCreate(Bundle savedInstanceState) {

        Thread h = new Thread(new Runnable(){
                public void run(){
                                try {
                                        Log.d("TEST SERVICE","HERE AM I");
                                        } catch (InterruptedException e) {
                                                // TODO Auto-generated catch 

Best regards,


2. Troubles with SurfaceView's surfaceCreated/Destroyed

I'm writing a game using two different SurfaceView's (RollView and
CupView) in two different activities. Both SurfaceView's heavily
resemble the LunarLander demo.

The RollView SurfaceView is working fine. When leaving the Activity,
RollView's surfaceDestroyed() is called, killing the thread. If I then
re-enter that Activity, the thread is recreated in RollView's
constructor and then started in surfaceCreated().

However in CupView the thread never seems to go away. SurfaceDestroyed
is being called, but upon reentering the Activity I get the following

java.lang.IllegalThreadStateException: Thread already started.

This thrown is in surfaceCreated() at the thread.start() call.

The difference between the two, and apparently the problem, is that in
the RollView Activity I call finish() when done. When leaving the
CupView Activity, I'm doing a startActivityForResult
(i,ClassWithRollView.class);......not calling finish().

This is because after leaving the RollView, I want to return to the
CupView. Below is relevant code:

   /** This where I'm exiting the Activity with the CupView **/
    private void rollDice(){
        if (mMode==IN_PROGRESS){
                // create a new intent for the roll dice view
                Intent i = new Intent(this,RollDice.class);
                        mRollCount = mRollCount + 1;
                        if (mRollCount == 3){
                                mTurnCount += 1;
                        if (mTurnCount == 13){
                i.putExtra("my.package.RollCount", mRollCount);

/** This is CupView's surfaceCreated/Destroyed **/
        /* Callback invoked when the Surface has been created and is read to
be used. */
        public void surfaceCreated(SurfaceHolder holder){
                // start the thread here so that we don't busy-wait in run()
                // waiting for the surface to be created
                Log.d("MyApp","cup view surface created");
        /* Callback invoked when the Surface has been destroyed and must no
longer be touched.
         * WARNING: after this method returns, the Surface/Canvas must never
be touched again!
         * (Unless its REALLY asking for it.)
        public void surfaceDestroyed(SurfaceHolder holder){
                // we have to tell thread to shut down & wait for it to finish, 
else it might touch
                // the Surface(wouldn't want that!) after we return and explode
                Log.d("MyApp","cup view surface destroyed");
                boolean retry = true;
                while (retry){
                                retry = false;
                        }catch(InterruptedException e){


So why is the thread saying its already started when surfaceDestroyed
() has been called?

A possible workaround is to call finish() on the CupView Activity in
the rollDice() method above. This doesn't seem to follow common
paradigm though. Any other solutions, comments? All help is


3. Source Code for dx

4. How to find Jarsigner

5. OutOfMemoryError (external allocation too large for this process)

6. calender's sync

7. How to refer TextAppearence