Ok the black plastic bezel around the phone .screen..I have notice it gets worn to a dull finish..I got a replacment phone brand new 3 days ago..and I noticed on the corners of the phones bezel..arent shiny no more but a dull finish..they must have used some really cheap plastice..i dont use a case..i either put the phone in my pocket or in a leather hip case...anyone else noticing this ware....
View 3 Replies
With this sample code, the activity is told to finish, but continues execution afterwards and displays the message. I'm trying to understand why this happens. The only fix I can think of is to place 'return' after finish.
public void someMethod() {
if( valueIsTrue) {
startActivity(new Intent(this, NewActivity.class));
CurrentActitivy.this.finish();
// return; // if uncommented, Toast doesn't show
}
Toast.maketext(this, "Some message", Toast.LENGTH_SHORT).show();}
Has anyone noticed a series of vertical dull lines (slightly yellow) when looking at the screen on an all white background with the backlight high?
Is this normal for a capacitive touch screen ? I've tried searching multiple forums and had no luck finding an answer. Edit - This is my first touchscreen device, so I'm really not sure about what is going on in there!
I apologize if this has been asked, I have searched and not found an answer. I do not use contact photos so is there a way to remove the dull gray icons that are there by default?
View 4 Replies View Relatedjust wonder if you all could take a quick look at your camera bezels around the lens for me. when i look at mine, in the top leftish part there is a small gap between the lens and the bezel. almost like the bezel it self is not completly round. seems like enough space for dust or foreign matter to get in. is it just mine? are all your glass flush on the bezel? just don't seem right. if i take the battery cover off, and press down on the bezel it makes it flush.. but is the bezel supposed to float like that? you think htc would just mail me a new bezel to stick on there? it only seems to be held on with glue of some sort. does any of this make sense at all?i have now put a small dent in the bezel from putting slight pressure on it with my finger nail.
View 12 Replies View RelatedIs the bezel around the screen metal or plastic? Will help me decide on if I put it in a case or not...
View 2 Replies View Relatedis it possible to have a lock screen where you slide the screen itself rather than have a slide bar? similar to windows phone?
View 1 Replies View RelatedThis O ring glued to the phones battery cover will stop broken lens' for good! The reason why the glass cracks is direct pressure to the red bezel. With this O ring it can not happen all the shock force is now on the battery cover not the lens.
View 49 Replies View RelatedI recently found a scratch under the bottom bezel of my desire! and that's only after one week! Do you think the paint would continue to peel off from there if I continue using my desire without and 'protection' for the front?
View 9 Replies View RelatedThe shiny silver bezel around the mini USB charging port on my phone cracked and came off. No idea how it happened but about half of it is missing. I have insurance on the phone but i was wondering if this would warrant being able to return it?
View 1 Replies View RelatedDoes anyone have a good method for cleaning the little gap/crack between the screen and the bezel of lint, dust, cheetos, etc.?
View 9 Replies View RelatedFrom the pictures on the Seidio site it looks grey. Click on "more pictures" and look at the only with the picture of the camera lens. Innocase Surface, Black
View 2 Replies View RelatedWe all know that hitting the back button on the device doesn't kill the application, it merely finishes (destroys) the activity running on the foreground.
Well I have come across some code which helps me capture the back button signal so that I cannot exit the application. The only way to exit it in such cases is to press the home key.
Now this situation presents me with a unique disadvantage! The inability to kill finish the application on a time of my own choosing allows the application to keep running in the background like nothing has changed.
So in such cases is the task manager my only friend or is there a way for me to otherwise kill this application?
I see no means by which my activity can pop itself off the activity stack to return the user to the one he was using before it was invoked. Is there one? My purpose is that my app has some data structures built from data provider queries that take 5-15 seconds to assemble and I don't want a lot of latency if it is used in a few one-shot purposes in rapid succession. I'm more than willing to let the system ask my app to die, but I'd like to keep warmed and ready otherwise.
View 4 Replies View RelatedI have one activity call a camera view activity, and in the onActivityResult, I have it start that activity again with different parameters. Android doesn't seem to like that, and gives me an error that the camera is not available if I start it right after it returns. I tried just waiting a few seconds, but this doesn't seem to work on all phones, and it sometimes crashes. Is there some way to wait until that activity finishes properly, and gives up all resources?
View 6 Replies View RelatedI've got an application that has (among other things) three Activities, let's call them A, B, and C. A is the main navigation point for the entire application, and launches B and C directly using startActivity(). They work fine that way. However, when I call C from inside B, I get a strange problem. The code for launching Activity C is exactly the same in both places. The problem is the hardware back button. In the emulator, it takes two presses of the back button in order to close Activity C and come back to B. On a G1, it takes 3 or 4 presses. Upon seeing this, I implemented the usual suspects in C - onPause(), onStop(), and onDestroy(), and onResume() in B. When I press the back button from C and it doesn't work, I get onPause(), onStop(), onDestroy () - in that order, but nothing happens. When it works (on press 3 or 4 on the G1), I get onPause(), then onResume() in B, then onStop() and onDestroy().
I've tried catching the key press of the back button and calling finish (), but that doesn't make a difference. Has anyone seen this? To pre-empt some questions: All C does is display some data. There are no threads or any other special resources that C might have an active handle to that's preventing it from closing. But out of curiosity, if it did, how would I detect that? Any ideas for further diagnostics here?
I have an EditText field and I want to pop up a new window/activity whenever a user touches/clicks the field. The new window has some widgets and of course Apply and Cancel buttons. Here is the code how I intercept the onTouch event.
EditText ctlMaskEt = (EditText)findViewById(R.id.mask_field); ctlMaskEt.setOnTouchListener(new OnTouchListener() { public boolean onTouch (View v, MotionEvent event) { popMaskEditor(); return true; } });
Everythings work fine until I click the Apply and Cancel buttons. The API finish() won't close the new window unless I click the same button one more time. Calling popMaskEditor() from a button's OnClick event handler doesn't have this problem.
I had the 1.5 android emulator starting from Eclipse perfectly nicely.... until yesterday when it suddenly won't finish booting. I haven't installed anything new (Running it on Windows Vista - i know, uck, but I'm waiting for Win 7 to hurry up), haven't even changed the java code I am trying to run. The emulator starts up, get's to the point where it shows "Android" with the nice lighting effect that goes from left to right over it and then just stays in that state. Last night I tested it by starting it up, going out to the living room, watching two hour long episodes of the first series of Doctor Who, and then coming back in (Essentially giving it 1.5 hours to do it's stuff) - it was still stuck in that state. Any ideas what I did wrong?
View 16 Replies View RelatedI have an activity that launches another activity with startActivityForResult method. I would like to terminate the called one programmatically but I don't know how to do this since in onActivityResult() method I have no information about the called activity and I cannot call finish() on it. How can I achieve this?
View 4 Replies View RelatedI just got my droid in the mail today, and I activated it about 20 minutes ago. Now I have the update notification and it is updating as we speak. It is just sitting at the screen with the caution triangle. How long does it take to finish? I am just curious.
View 4 Replies View RelatedI have been developing a game on Android and wrote a wrapper for J2ME classes,
When notifyDestroyed() is called in my ME program and calling finish() but the application doesn't close correctly.
The App goes to background and when launched again it shows an error message and presents an option to "force close" the App, if i force close it and launch again, the app launches fine but again the same has to be repeated upon every launch..
Can you please explain why the App is not being erased from memory when finish() is called.
when i check the log i found no exceptions when closing but when launched again it throws a null pointer exception.
for now to work around I placed "System.exit(0)" after calling finish () so that the app is exited abruptly, but am waiting for a valid answer on whats going on behind...?
I've been using code like: activity.finish(); activity.startActivity(new Intent(activity, activity.getClass()));
in two places: onResume(), and in an onClick() method of an AlertDialog. I'm getting the desired results when the code is called from onClick(), but I get mysterious null pointer exceptions while the runtime is trying to execute my onPause(). Is calling finish() from within one of the Activity lifecycle callbacks always a bad idea?
This code makes me nervous even though it works in the onClick(). After I call activity.finish(), I would think activity is in a questionable state by the time activity.startActivity() is invoked. Seems like an invitation to race conditions.
My use case is setting UI preferences (e.g. a different layout) in a PreferenceActivity. When I return to the main activity's onResume(), I check for preference changes and if a new layout is requested, I use the code snippet above.
I am trying to upload images with either the build in Android browser or Dolphin Browser or Firefox on imagehosters like imgur or tinypic on my Samsung Galaxy S+ with XXKQ7 stock FW, but it always hangs right from the beginning. On another forum I was told that uploading is a general issue on Android.
View 1 Replies View RelatedI have a 16Gb Nook Tablet that I wiped a long time ago and put CM7 on it. It worked great. Then I put CM9 on it, and it worked great. Then I tried to put CM10 on it. So far, no matter what build I try for CM10.0 or CM10.1, it has the exact same result: After I do the final reboot, it starts to boot up, but gives up and just shuts down (screen goes black, and you have to turn on the device again). Sometimes the CM10 logo starts spinning before it turns off, sometimes it turns off before the spinning CM10 boot logo appears.
I've tried many different builds (only for the Nook Tablet), but they all behave the same (some from the official cyanogenmod web site, some from other xda-developer forum posts for the Nook Tablet).
In main Activity, I called start Activity For Result(intentB, 100) to start a new activity B, then in B, I called startActivity(intentC) to start another activity C. Lastly I wanted to call finish Activity(100) in C to close activity B, but seemed it was not successfully destroyed(I can use BACK key to see it's still there.)
View 6 Replies View RelatedI saw another thread related to this question, but did not find the answer that was useful to me. Is it possible when the user presses the Home button to be able to finish() my activity somewhere? I saw that people were having problems with using onStop(). Has anyone found a resolution to see if this is always called on Home being pressed?
View 5 Replies View Relatedi have an interesting problem. for some reason, when i charge my phone while off, it will only charge itself to 96%, and will only charge to 100% while turned on. i noticed this and figured that maybe i did not fully charge it before i flashed it last time, so i repeated the process and got it to a "true" 100% (i know this because when i plugged it in, it immediately said battery full, as opposed to before i discovered this when after charging (while off) and it said battery full i'd pull the battery then reinsert, it would begin charging again) i then reflashed (warheads). i now run my battery until it dies completely, then charge while off (still only get to 96%), but when it finally gets to 100%, the "battery left" widget says less and less time left each time i charge. (the first time it said 24hrs, then it went to 22, then to 18, then 16, now its 14)what have i done wrong? and does anyone have ideas on how to fix this one?
View 1 Replies View RelatedTried before but didn't get no where as was not downloading as zip files , so question is have i got enough time tonight , how long will it take to to from start to finish
View 5 Replies View RelatedI wanna start out by saying I love my droid but on thing that bugs the crap out of me is the finish on the top of the thing. It looks nice and polished for a few weeks but then it starts to chip like crazy. The screen is holding up perfectly its just the corners of the bezel. I think they should have gone wth a matte or aluminum finish or even the soft finish like on the battery cover.
View 31 Replies View RelatedI would like to know whenever the top task is changing. i.e. when a new task is starting or a task is finishing or when the current active task changes. Is there an intent that is sent that I can listen to?
View 2 Replies View Related