I finally decided to do it. I had an idea to use the corner of a sheet of paper dabbed in krazy glue to slide up and down the sides and bottom of my phone while holding the screen down for a while. Surprised, it worked like a champ, and any excess glue that got anywhere on the phone was easily removed with acetone. Unless you have very sturdy hands, I would not advise this.
View 5 Replies
I just picked up a Droid today, and I just seen, above the 4 touch buttons when they are lit up, if you tilt the phone down you can see light leaking up to the edge of the screen. Does anyone else have this problem or should I return my device?
View 36 Replies View RelatedThe bottom four buttons on my droid leak light if I look at it certain angle...
View 5 Replies View Relatedso i just got my evo 0003 hrdwre ver from a sprint corp store on 7-1-10 ive noticed that the bezel is tight all the way around except where the rocker up is. if i run my finger along the outside of the bezel i can feel that its raised (very small hump) and and is not very tight to the screen like the rest of the phone. is this the beginning of this issue? its almost like there was a casting issue when molding the bezel. should i go ahead and swap it?
View 1 Replies View RelatedOkay so after scrutinizing my white evo 4g for the first time yesterday I noticed that the bottom corner of the phone has some SLIGHT lift (like .5mm above the bezel) and of course some light leakage, which doesn't bother me too much.However I thought HTC were going to fix this issue in manufacturing starting in late June? Anyway it looks like they didn't.If possible I'd really like to just keep this phone and not swap it. I am hoping the separation doesn't get worse but I wanted to ask on here if anyone knows of a way to just go ahead and fix the issue myself. Like for example would a couple tiny dots of superglue on the corner do the job? Would that hurt the phone?What about the hex screws? I am suspicious about the validity of that fix.Anyway any advice on how to fix this before it (possibly) gets worse
View 5 Replies View RelatedI'm deciding between what appears to be a common conundrum: Evo or Droid X. I was leaning towards the Droid X, but now I'm not so sure. Verizon and Sprint both have fairy similar coverage in New York (that I'm aware of), but Verizon's plan costs more than sprint's does, which is kind of a large turnoff. The previous deciding factors were issues with HTC's build quality (scree separation) and poor battery life. I wanted to know if these issues are real concerns, or just hyped up complaints that dont accurately reflect the phone.
View 10 Replies View RelatedAs all of you probably know by now, there are problems with some if not most of all of the Evo's screens and responsiveness and whatever. my question is, and i honestly apologize for sounding like a 'noob' but how do i check for the screen leakage and separation issues, and actually any other hardware issue that's been discussed? Thanks for all the input!! i honestly appreciate because if i do in-fact have this problem, i'm just gonna go back to t-mobile and get the samsung galaxy s in july, but i still give evo higher priority
View 6 Replies View RelatedI have an EVO on order with Amazon (early Oct delivery - ouch!), hoping to get one locally before then but at least I have a backup plan. I've been reading a lot about the charger port issues and the screen peeling/separation issues. Does anyone know if these manufacturing defects (assuming that's what they are) have been fixed or do new EVO's still run the risk of having these problems? I've had Verizon and AT&T before and it's always been relatively easy to get a new replacement device if the original had issues. It sounds like it's not as easy on Sprint so I'm a bit concerned...
View 5 Replies View RelatedMy Incredible fell out of my pocket when I was getting out of my car and it cracked. The touchscreen on the Incredible still works, but the glass/LCD (or digitizer) is cracked. I don't have the insurance and since it's been a few months, I can't add it.
1) How much will Verizon charge to replace the glass/LCD (or digitizer) or provide a replacement phone?
2) What is the turn around time to get it fixed?
But sometimes other small parts/and or button commands lock-up. For example; since I am new to Swype, I decided to take the tutorial and each time I would click (or even tried to slide) the next button, it wouldn't respond took about 5-7 tries.While on the phone with tech/and CS yesterday (for whole diff issue), I asked about the Capacitive Button Sensitivity - as mine wasn't working that well either (as others have mentioned). Tech had me remove the battery for 2 full minutes, and put back in - and now the Capacitive Buttons works perfectly.Anyone else having partial screen/certain buttons not responding to commands? I guess I could try removing the battery again, but I am not sure that will fix it.
View 4 Replies View RelatedI have a light bleeding through my screen....is this bad? It past the 30 days since I bought the phone, so I'm not sure if sprint.
View 22 Replies View RelatedSorry Mods but searched and could not find any answer so:- Whilst "sat" waiting for my NON 3G/NON Wifi screens to load when trying to "surf the internet" I find that my screen light goes out! Is there a way or an app that keeps my screen light on for as long as I want it to?
View 4 Replies View Relatedon my old Samsung phone I had the backlight set to turn off after 30 seconds but this didn't lock the screen. With the Wildfire however with the backlight set to turn off after 30 seconds this also locks the screen. Is there a way to set it so the light goes off without locking the screen?
View 2 Replies View RelatedI have a ClassLoader in Activity's onCreate which loads a specific class from a library, and is working fine, except that when activity is destroyed, the memory resources about the loaded class are not released.If the same activity gets created multiple times very quickly (by launching it, and destroying it by pressing the Back button), and the process doesn't happen to be killed by Android yet, the memory usage of the corresponding process grows continuously until the app crashes,and process dies.The problem is that this happens even if no objects are instantiated using the loaded class. There seems a problem with garbage collector, which doesn't seem to release resources about the loaded class on Destroy even if there are no references to it.If android would have killed the process right away when the last activity of the process gets finished, there wouldn't be a problem, but this is managed by Android system, and it doesn't always kill the process right away. A workaround may be to kill the process explicitly on destroy, but this is not encouraged way to do, as Android is supposed to manage the process.
An alternative is to have a functionality that allows a class to be unloaded onDestroy, but this doesn't exist. By design, the garbage collector is supposed to take care of this.Is there a solution regarding this?
I'm using the new US version of HTC Hero (I believe it's running 1.5) and I noticed the following pretty annoying problem that I cannot seem to tweak.
If a new calendar event or alarm come in, the screen briefly lights up to show what the message is, and then turns off after a short while. That way, I don't have to turn it on, pull down the protective screen, then the notification bar, etc.
However, with email, SMS, gtalk, and the like, the screen doesn't light up. There are settings for having a sound or vibrate, neither of which light up the screen. When I press the Menu or power button, the new notification sits happily in both the lower part of the screen and the notification area.
Yesterday I noticed a small white circle on the screen. It looks like an area on the screen the might be displaying brighter.
View 44 Replies View Relatedhow do i get the screen on my epic to light up when i receive a new notification?
View 2 Replies View RelatedI am pretty sure when I got my first few texts with handcent the screen lit up, but now it stays black when receiving a text. Is that how it is supposed to be?
View 5 Replies View RelatedPretty much what the title says. Is there any app out there that lights up the screen when you receive a sms /txt message?
View 9 Replies View RelatedI'm trying to locate a memory leak in my app (it's client for a mediacenter). So I start it up, go to the screen that lists all movies, go back to my home activity, trigger the GC a few times manually via DDMS, dump the memory heap, pull it, convert it and load it into MIT in Eclipse.
Now the movie list screen is pretty heavy, around 800k of movie objects, which should be freed when I go back to the home screen. However, it stays allocated, with the GC root as a local variable in the main thread at ActivityThread.ContextCleanupInfo (see attached screenshot).
I've tried searching but there is no documentation on this class, not even in the source code. Is there any way to avoid this kind of behavior? Am I doing something wrong or is the problem in Android? My app is open source and can be checked out here[1]. http://code.google.com/p/android-xbmcremote/
What would be the best way to debug a leaking program?
I have developed a media player (includes a background service doing the playing, and a UI, and I access getResources(), MediaStore and things like this often).
Whenever I rotate the screen or reenter the app the total memory allocated to my process grows some 70 to 100KB. After some 6-10 rotations it is dead due to an out of memory exception.
In the meantime I have removed every static modifier to global vars, added an onDestroy function that unregisters the intents and service connection (and even puts every global var to null again :P), but still the program memory grows... and dies after a few rotations.
Given the situation I even made the program stop right after just calling setContentView, and still the memory leaks:
CODE:......................
http://developer.android.com/reference/android/app/Activity.html
The Activity Lifecycle could have implementation and or design bug: One case is to initialize a big image in onCreate(), try to reuse the image during the whole lifecycle, and then recycle the image in onDestroy(). Test showed that onCreate() is called every time one navigate away from the activity and back again, but onDestroy() is not called at all. This behavour causes memory leaking for the big image (size 960*1920). After 6+ times away and back to activity, the system runs out of memory and has to kill the process.
One workaround is to initialize the big image in onResume() and recycle in onPause(), but that's not so good reuse.
Could it be better to change the process (as shown in the diagram) a little bit such as: Call onDestroy() first when a process is killed?
I created a simple app with a ListView following the ListActivity examples I found on the net.
The app has 2 activities with the first having a button to create the second. When i hit the close button on the second activity I would like it to release its memory (or at least allow it to be garbage collected).
Currently it will never release.
I must be doing something wrong here because the MyListActivity never gets released. Can anyone tell me if I am doing something wrong with the way my activities are created/destroyed? or if my usage of the ListView is wrong?
My App as a zip - http://www.mediafire.com/?l26o5hz2bmbwk6j
Screen Shot of Eclipse MAT showing the list activity never releasing memory - www.mediafire.com/?qr6ga0k
Anybody else thinking that the revs are being leaked deliberatly and they are using us to test them and find the bugs?
View 22 Replies View RelatedI definitely have a memory leak problem and i'm trying to figure out there. After 6-10 config changes i'm getting out of memory in regards to BitmapFactory. I'm kind of suspect that this is going on within adapter. I have a listview . ListItems are an thumbnail image ( ImageView ) and TextView for text.
Here is the getView code.
CODE:..................
And get ThumbnailBitmap() is basically BitmapFactory.decodeByteArray ..
Is it possible that i'm leaking drawables ? Heap is not increasing by the way .
I read the Avoiding Memory Leaks article with interest, and am concerned about danging references to the context object. I have a class like the following.
CODE:.........
Is it a problem to have a reference to a LayoutInflater object, since it must be using the context object somehow? Is there a better design pattern for what I'm trying to do here? (Use the context only to initially inflate the XML; from then on just use the View that's passed in to getView)
HTC now has an in store fix for the flying screen syndrome but you can do this at home. Take a credit card or similar type of item and wedge it in between the screen and the phones frame lifting the screen bottom as much as you can without causing further lifting damage. Then remove the battery door and locate the two holes in the photo with the tooth picks. Put a couple drops of crazy glue in each hole then remove the credit cards and quickly clamp the screen down for about a half hour. Clothes pins might work as make shift clamps try therm before starting. If you can get your screen up enough to put the crazy glue tip directly under the screen you can do this also but use very little glue and dot it maybe 4 times across the area for a good even hold then clamp. I would tape off the screen and phone frame just in case some leaks out by accident doing this method. Once the screen is secure use automotive black silicone adhesive sealant I like Permatex brand found at WalMart (now this stuff can also be used to glue the screen down but will take longer to dry 12 hours put it on a tooth pick and shove it under the lifted screen bottom then clamp) You can take this black silicone and dab a small amount around the screen crack and with your finger or a q tip force it in the light leak crack then simply take a tissue and wipe off any excess silicone before it sets you will have no damage to the phone from spilling it just wipe it off. You should now just have a tiny bit shoved in the crack with all the rest wiped off. let it set and you are done!
View 8 Replies View RelatedIs it possible to get the droid screen to light up when you receive a text when it is on silent mode for example to show that you have gotten a text?
View 7 Replies View RelatedHas anybody else ever been in an SMS (Google Voice), email, or IM conversation with somebody, with your phone continually beeping every 30 seconds when you get a new message? This happens to me a lot. The phone is sitting next to me on my desk, and each time it beeps, I pick it up, push the power button, swipe to unlock, swipe down the notifications bar, and then look to see what's new. After doing this about 30 times in an hour, I have to ask myself, is this really necessary on a modern smartphone? The dumbest dumbphone I know will light up when you get a new text. Now, I have searched high and low, and am I just stupid, or is there no setting or app available to turn the screen on for like 5 seconds and display new notifications as soon as they come in?
View 5 Replies View RelatedI had a accident with my phone i punched my phone screen out of anger but now the buttons only light up and the screen stays black what do i do?
View 2 Replies View Related