Anybody else dissatisfied with quality of G1?

by Eng, Cary » Tue, 30 Dec 2008 02:34:53 GMT


Sponsored Links
 I was just wondering if I'm the only one who finds the G1 a little on the 
"unpolished" side?  It just doesn't seem to have the same quality as the 
iPhone.  Maybe it's just the nature of the slide-out display and its loose 
tolerances, but it just seems a little less robust than 1-piece phones.

Cary

--~--~---------~--~----~------------~-------~--~----~



Anybody else dissatisfied with quality of G1?

by Shane Isbell » Tue, 30 Dec 2008 02:38:44 GMT


 G1 is junky. No doubt about it. I have problems with the battery and voice
as well, it keeps cutting out on me. And I live down the street from
T-Mobile USA HQ, so I know it's not the network.

Shane





--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Anybody else dissatisfied with quality of G1?

by Hong » Sat, 03 Jan 2009 18:39:09 GMT


 I had my G1 replaced since it started to randomly reboot, during phone
calls, plug-in USB, open keyboard, etc.  Even a factory reset cannot be
completed since sliding out the keyboard to type my gmail account rebooted
the phone.

Now using the replacement G1, will see how long it lasts.






--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Running multiple Services in Android

Hi,

I'm currently building some movement-detection functionality into my
application. I haven't found a way of continually monitoring the
accelerometer without keeping the phone awake all the time. In trying
to overcome this, I currently have a Service implementing
SensorEventListener. I can start this service at intervals (using
alarm manager), get readings from the device acclerometer, determine
if the device is moving, and then shut down the service. Generally,
this appears as follows:

public class MyService extends Service implements SensorEventListener
{

    @Override
    public void onCreate() {
        super.onCreate();
    }

    @Override
    public int onStartCommand(Intent intent, int flags, int startId) {
        super.onStartCommand(intent, flags, startId);
        /* Register this SensorEventListener with Android sensor
service */
        return START_STICKY;
    }

    @Override
    public IBinder onBind(Intent intent) {
        return null;
    }

    @Override
    public void onDestroy() {
        /* Unregister SensorEventListener */
        }

    /* SensorEventListener Implementation ************************/

    @Override
    public void onAccuracyChanged(Sensor sensor, int accuracy) {}

    /* Receives callback when sensor values change */
    @Override
    public void onSensorChanged(SensorEvent event) {
        /* Determine if moving & then call stopSelf() to shut service
down */
    }
}

I have a further problem, however, in that my application has a second
service which is invoked on a different schedule. As far as I know,
both of the services will be run in the same thread, which is not good
as they could conflict.

I need to know if there is a safe way to run more than one service
simultaneously within the same application. I have considered the use
of IntentService instead of the standard Service class. I am aware
that these implement their own worker thread for handling invocations.
The problem there is that I have no idea how I can implement the type
of asynchronous callbacks required by SensorEventListener from within
an IntentService. To put it another way, I have no guarantee that a
method like onSensorChanged will receive a callback before
IntentService completes its work and shuts down.

Any suggestions on a workaround to this problem are highly
appreciated.

Thanks, Declan

-- 

2. resizing the touch event generating area

is there a way to restrict the touch event generating area to a specific 
rectangle within a view? 

to be clear: i know about *onTouchEvent* and *dispatchTouchEvent. *But a 
use-case in our application forces us to completely ignore touch events in a 
specific area, ie. it should be possible to accidentally touch the bottom 
half of the screen without triggering ACTION_UP, ACTION_DOWN etc. thus, 
ACTION_DOWN, ACTION_POINTER_DOWN et al should only be triggered within the 
specified area.

maybe there is a completely obvious solution i have not come up so far...

thx, andre

-- 

3. RelativeLayout subclass ignoring explicit background color

4. Get Row Id of draggable and droppable listview

5. How to properly implement a custom AdapterView's setSelection method

6. Problem loading gadget

7. insmod on android