Hey guys, so I got my Pebble a few days ago and I noticed a weird glitch that has happened to me everyday where the text would randomly get really small on the watch face and any notification. I think it might have to do with Glance, because Glance seems to freeze up when this happens and eventually reboots. The text goes back to normal after this. This isn't a huge problem since it reboots very quickly, but I was just curious if there might be a fix Thanks.
So, this bug is occurring almost everyday. Again, it reboots in literally 2 seconds so it's not a huge deal, but I was just curious if anyone else had the problem. I took a picture when it happened, it's not very clear. Basically, the text gets very small and then if I go into Glance, I see this http://imgur.com/CP3dTa3. Half the screen is black and then right after I try to scroll within the screen it reboots and then it's fine for a day or so. I think it's most likely a problem with glance but I'm not sure.
PsychDrummer said:
Hey guys, so I got my Pebble a few days ago and I noticed a weird glitch that has happened to me everyday where the text would randomly get really small on the watch face and any notification. I think it might have to do with Glance, because Glance seems to freeze up when this happens and eventually reboots. The text goes back to normal after this. This isn't a huge problem since it reboots very quickly, but I was just curious if there might be a fix Thanks.
Click to expand...
Click to collapse
I've experienced this too, the small text anyway. I've never gone to look at Glance when it happens. I'll try to remember to check that next time it happens.
Unfortunately I can't really be of much help with a fix.
Sent from my LG-D801
Mandroid421 said:
I've experienced this too, the small text anyway. I've never gone to look at Glance when it happens. I'll try to remember to check that next time it happens.
Unfortunately I can't really be of much help with a fix.
Sent from my LG-D801
Click to expand...
Click to collapse
I guess I can try uninstalling glance and see if the problem disappears.
That's a bug with pebble and 3rd party apps. I've noticed it with other 3rd party apps other then glance.
I have to notice that on pebble after a factory reset and no 3rd party app.
Sent from my HTC One using Tapatalk
The small print means that the Pebble is running out of memory, usually caused by third party apps. Glance has this problem and that's the reason I don't use it. With 2.x firmware I haven't had the issue, but still not using Glance, so i don't know if the problem is solved
Verstuurd vanaf mijn Xperia Z
Thanks guys for the explanation. I suppose that makes sense. Again, not a huge issue, just my thing is that I want to make sure it's not a defect in the device.
Related
So this was happening before but I factory reset my phone and now after about a week and a half it's happening again;
everytime i either go back to the previous screen, or while i'm on a loading screen (noticed it a lot with Netflix) but i get these green pixely squares that flash on my screen... this a known issue with the version? or should i take my phone back?
I'm not really sure how to better describe it...
Have yet to experience that, had my unit for over 2 weeks.
Take it back.
-smc
I have the same problem with mine had it since it came out?
Sent from my DROID3 using XDA App
I've had the same issue. Started happening within 2 weeks, but more recently it hasn't happened much. A battery pull always fixed it for me. I'm experiencing random reboots when the phone hasn't been touched for ten minutes, this is more disconcerting to me
I haven't noticed it after a reboot for a couple days now...
But i do remember almost directly after it first happened (before i did the factory reset) my phone started doing the whole random reboots too. That's when i read the post about fixing the camera and not using the assistant backup/restore functionality when you activate the account...
I thought it had fixed all the issues but seems they're still there just, less sever...
Rebooting the phone (temporarily) fixes the issue for me
[sent from my droid]
I swear, after using the camera this happens. Until I reboot I get some kind of green checkerboard whenever the screen rotates or changes
Same here. Every time I use the camera and sleep the phone it will get hot and drain the battery. Waking the phone gives me green pixellated images and serious slowness. Battery pull after taking pictures is the only way to mitigate it...for now.
Sent from my DROID3 using XDA App
So this seems to be a common issue... has anyone been able to talk to motorola? is there an update coming out anytime soon to get it fixed? or is it just a hand full of bad phones?
smc, have you still not experienced any of these issues?
can you try seeing if it might happen after some of these scenarios listed in this thread? would be greatly appreciated!
I'm not sure if my 2 month old Note has had the following problem since day 1 but it's been doing if for a long time now.
The problem is there with a stock standard rom and any of the other custom roms and kernels that I've tried. I'm currently using Rocketrom with Speedmod kernel. I've also used Checkrom and Abyssnote kernel.
If the Note had been asleep for about 15 minutes or more when I wake it up then try to do anything like opening an app, closing an app that's already open etc there's a 2 to 3 second lag the first time I try to do anything. Everything is then normal until the next time that the Note has been asleep then it's the same story again.
Can anyone give me a clue as to what is going on here? I'm starting to think that it's hardware related, but apart from this problem the Note functions perfectly normally.
Also, if I have a CPU monitor installed, like URsafe CPU Monitor, when the lag is happening the monitor shows that the CPU is working hard.
Help please!!!!!
Does this happen after a complete hard reset with no apps installed?
Does this happen on Stock ROM?
Are you using WiFi?
Sounds like WiFi is sleeping when the screen is off, and either it is trying to connect and/or some app is wildly trying to connect using it.
Try seePU++ can tell you what the most active app is, but IIRC you have to pay for that that feature. There may be others.
PoisonWolf said:
Does this happen after a complete hard reset with no apps installed?
Does this happen on Stock ROM?
Click to expand...
Click to collapse
Yes, it happens on stock rom with no apps installed. I'm not totally sure what you mean by a complete hard reset. Can you please tell me how I do that? I'm willing to try anything to get rid of this problem.
jeromepearce said:
Are you using WiFi?
Sounds like WiFi is sleeping when the screen is off, and either it is trying to connect and/or some app is wildly trying to connect using it.
Try seePU++ can tell you what the most active app is, but IIRC you have to pay for that that feature. There may be others.
Click to expand...
Click to collapse
The problem still happens with WiFi disabled. On top of that it doesn't matter how long I leave it after I wake the phone up till I try to do something like launching an app. The problem is still there the first time I do anything with the phone.
I have rocket rom and sometimes when I turn on the screen the screen wont work. The physical buttons work but the screen is wont respond to touch.
Turning on and off the screen fixes this.
Very annoying.
Makes me appreciate Apple more.
CorruptedSanity said:
...snip...
Makes me appreciate Apple more.
Click to expand...
Click to collapse
Ban him!
appro77 said:
Yes, it happens on stock rom with no apps installed. I'm not totally sure what you mean by a complete hard reset. Can you please tell me how I do that? I'm willing to try anything to get rid of this problem.
Click to expand...
Click to collapse
Do a clean stock ROM with no root or anything.
Do a factory reset and erase your USB storage as well (i.e., tick the option when you're factory resetting).
Remove your microSD card.
Now, does the problem still occur? If it does, get your phone exchanged/repaired. It sounds like a hardware problem.
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
Really? I haven't noticed this at all on my phone. Any specific apps I can test this on?
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
Same here, totally normal.
Sent from my GT-N7000 using Tapatalk
1902 said:
Same here, totally normal.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Just not getting that myself. I am not terribly patient, and generally the most I have to wait is a second for an app to respond after waking the phone, and that is not often.
Stock unrooted HK version, never seen anything like that delay, mine works instantly on waking
Sent from my GT-N7000 using Tapatalk
Same delay here. Stock ROM, and rooted.
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
I dare say this is not normal, the only time there is a delay in opening the dialer/contacts application is when you initially boot the device and have both of those running for the first time subsequent runs have no delay what so ever on my end ( when i still had the note )
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
If this is normal it's incredibly bad that Samsung would design something like this. The wake up lag is bad enough let alone this. Can't see how it can be normal though. My SGS2 didn't have it and some other users aren't seeing it. I think I'll hang out for ICS and see if it goes away before I take any further action.
Strange issue, seems it occurs for some but not all...
Once again, I unlocked the screen after 2 hours of no use, when pressing contacts, there was a 2 second delay and when attempting to call someone there was a good 2-3 decond delay...
jeromepearce said:
Just not getting that myself. I am not terribly patient, and generally the most I have to wait is a second for an app to respond after waking the phone, and that is not often.
Click to expand...
Click to collapse
Luky you :banghead:
Sent from my GT-N7000 using Tapatalk
Despite being my first Android device I have come to accept that this is normal for this OS.
Unfortunately I have become a big whiner on this forum because of this same issue.
The day before yesterday there was an update on the kies ,LA4,after updating it felt a bit faster overall but the wake up and the incredibly annoying Contacts lag is still there.
I myself am not any particular OS follower or a fanboy of any certain brand for that matter.
So I'm stuck with Android for the time being, since I don't like both iTunes and izunes dependency, besides no big screens there.
However I suspect that this is an Android thing, as far as I know Android is based on Java and Java is known to be laggy,so until a very powerful CPU is available for mobiles, for me its either live with it or Leave it !! and since there is no alternative for now will wait and see how good ICS does and decide accordingly.
I'm on stock ROM and unrooted.
The Note seems to do this once or twice but when a program/app has been opened once it usually reopens them instantly.
This morning when turning on my Note for the first time, there was a few second delay when attempting to call someone, another delay when opening contacts and another slight delay when viewing sms messages.
However, the second time I attempy to open something it's usually immediately.
There should not be ANY delay when opening programs/apps and Ice Cream Sandwich should fix this wake up issue which some users such as myself am experiencing.
It's a shame, really since I'm getting no other lag/delay. The phone is super fast in every possible way, only sometimes it's a little slow at waking up!!
Not sure if I've seen this problem reported on this forum or another place... but I find with Droid 4 there appears to be some kind of charging bug which affects the txt display of the phone while it is plugged in. I am rooted, I used to think this was a TB bug, since I run backups when my phone charges, but I don't think so anymore since I turned off TB and it still happens randomly.
Might be related to cpu power management? I don't know... any suggestions? Anybody else experiencing the same issue?
Here is what happens, after charging, I turn on the phone display and it shows white block rectangles where my icons on my homescreen should be. Once I swipe away to a different homescreen page, the text becomes gibberish. The bug only affects homescreen now that I think about it....
I can take a screenshot next time, or if anybody is experiencing the issue please post.
Sent from my XT894 running ICS
Haven't had any problems like this. Screen shot would be nice. Have you tried a factory reset or 3rd party ROM?
podspi said:
Haven't had any problems like this. Screen shot would be nice. Have you tried a factory reset or 3rd party ROM?
Click to expand...
Click to collapse
I haven't tried 3rd party ROMs I like to stick close to stock, but this has been an ongoing issue since I loaded up the first ICS leak on the phone. I think it might be a 3rd party software issue but can't pinpoint it. I'll take a screenshot next time, thanks for the response.
Hello
Ive had numerous problems while i was on KK 4.4.2 .681 and .757 with freezeing phone, random reboots(usually once a day) and touch screen issues.
I have asked alot here and over at Sonys support forum and ppl began to point out that i could very well have a hardware problem. Although the problems i have had on KK wasnt that odd. Since ive read about others having theese problems.
But early monday morning i thought that hmm why not try what a dude here suggested. Wipe the phone completley with cache, dalvik cache and all that and flash the latest 4.3 firmware with JB. Hmm oki well i did that, and so far i havent had any reboots, or any freezes. Camera is QUICK and takes better pictures. At some point i thought the touch was acting weird but that could just be the app itself freaking out, it was only for a few seconds and after that everything was working like it should. Battery time is better aswell(although it goes down to 75% quite fast but after that its slooooow).
So do you still think i might have hardware issues ? I was about to ship my phone back to China but now it feels like it is pure software issues. And i have had big troubles with the retailer to accept this as a warranty matter since he belives its a software issue.
But then again, my phone aint operating good at all with KK 4.4.2
So far everything is fine with the phone, missing some stuff from KK but not the end of the world. But im still testing. If it will remain on without a freeze until the end of the week i could be quite certain that it is KK that ****s up my phone totally.
Please respond with thoughts.
Who told you to wipe your phone? ..lol..
Just my thoughts about touch screen, I replaced 2 days ago my "lucid" classic transparent screen protector with one Anti-Glare, which is not lucid glass like many but is rough and it influence a little little bit on the visualization of the screen, tiny, tiny thing but the touch screen is much much more responsive.
Classic issue with touch screen, unlock with patterns, with the lucid screen protector sometimes it skipped the touch and I had to try 2 times to unlock the phone if the phone was put on the table without hold it. With the new screen protector it not skip anything.
Sometime a stupid thing can be the issue.
Could be the screen protector, remember the first one I had was a antiglare, and as far as I remember I didn't have those issues then. Now I have ultraclear one. Could be that, you never know. I do have tempered glass one wich I haven't used.
Just before the phone actually froze for a few seconds just when I took a picture, but it came back with no reboot. And I got a msg on WhatsApp and messenger at the same time so that could be what was causing the lag this time. Hopefully
Sent from my C6903 using XDA Free mobile app
Still no reboot! Used camera alot and done all sorts of stuff.
And today I changed my screenprotector to see if that would rectify the touchscreen issue. I used a tempered glass screen protector. O my god how much better that protector feels! But still testing for any issues
Sent from my C6903 using XDA Free mobile app
Some updates.
No random reboots!
But two other odd things occurred and one of them is known.
1. Touchscreen went crazy, it didn't press what I wanted and so on. I noticed it actually swiped on the keyboard. Turned that function off and unistalled the app "Color notes". Touch screen bugs are known and Sony even admitted it so.
2. I couldn't send sms today, tried to several but got error. Data and so on still worked. Restarted the phone and then it worked again (might just be coincidence). Although I noticed that it at some point it had trouble sending data, took forever to get connection even though I had 3-4 pins reception. Also noticed when that sms bug occurred that it switched from 2 pins to full every time I opened the sms to send.
But still no reboots. These things maybe would trigger reboots with kitkat, I dunno.
Sent from my C6903 using XDA Free mobile app
Jonas740 said:
1. Touchscreen went crazy, it didn't press what I wanted and so on. I noticed it actually swiped on the keyboard. Turned that function off and unistalled the app "Color notes". Touch screen bugs are known and Sony even admitted it so.
Click to expand...
Click to collapse
I have it all the time, I mean not the touch screen going crazy but the swipe one on keyboard, it happen always when I click on the letter A on left side, it really piss me off.
I think I have to turn off the swipe thing too.
Ye I've read about ppl having issues like we do and they just turned it off and then it works. Sony said they would fix the touchscreen issues in updates but still not fixed.
Btw, have you noticed that the "swipe" to turn off the alarm clock is less sensitive? It takes some trys to swipe to turn it off. Although it is a good thing because it makes me pissed and I have to concentrate to turn it off wich makes me to get up Might be an intended "bug".
Sent from my C6903 using XDA Free mobile app
Jonas740 said:
Ye I've read about ppl having issues like we do and they just turned it off and then it works. Sony said they would fix the touchscreen issues in updates but still not fixed.
Click to expand...
Click to collapse
Yeah, they are very lazy to fix this issues but they are not to put on the market a "new" device and forgot about Z1.
Jonas740 said:
Btw, have you noticed that the "swipe" to turn off the alarm clock is less sensitive? It takes some trys to swipe to turn it off. Although it is a good thing because it makes me pissed and I have to concentrate to turn it off wich makes me to get up Might be an intended "bug".
Click to expand...
Click to collapse
Yes, Yes, I am glad that I am not alone. It was less sensitive even before I turned off the "keyboard swipe" thing. So not really know if it's related to that features, it shouldn't, but you confirmed a "bug" which was keeping me thinking. O Lord, I dream about a Z1 bugs free! (dream only)
might not be
eclyptos said:
Yes, Yes, I am glad that I am not alone. It was less sensitive even before I turned off the "keyboard swipe" thing. So not really know if it's related to that features, it shouldn't, but you confirmed a "bug" which was keeping me thinking. O Lord, I dream about a Z1 bugs free! (dream only)
Click to expand...
Click to collapse
Well that Alarm swipe might not be a bug actually, ive tried it back and forth and if you "lazy" swipe it fast like you would when it rings in the morning it wont turn off. But if you do apply pressure and swipe slow it will turn off. Not a huge problem for me since it actually help me getting out of bed
Jonas740 said:
Well that Alarm swipe might not be a bug actually, ive tried it back and forth and if you "lazy" swipe it fast like you would when it rings in the morning it wont turn off. But if you do apply pressure and swipe slow it will turn off. Not a huge problem for me since it actually help me getting out of bed
Click to expand...
Click to collapse
Of curse, it help me too, I get angry because of that so I have to leave my bed ..LOL..
The thing is, who know if it was meant to be like that? It was made with that purpose? Because if it isn't then it's a "bug".
I been having this annoying issue with the top left corner not responding to touch. This will often happen when I'm in a app or have multiple apps open. This never happened before. Until I got this replacement device. Has anyone else experience this issue?
can you remember if you were plugged in to the power source? I've had that few times using the phone while charging. unplug it then problem goes away. I think it's a known issue from the LG OS/software. it happens rarely so I don't really see that as a problem but surely a bug needs to be fixed.
I am having the same exact problem with my S6 edge. And looking around the Web, I've found that many others seem to be having the same problem with various devices. The only common link I've seen so far is lollipop.
Even if you rotate the screen, the dead area moves with the rotation and you still can't click on that area to access the menu, etc.
Of course, I can't find anyone official to acknowledge the problem, so I'm not sure what we can do.
Wow that's sucks. A buddy of mine is having the same issue with lollipop 5.1 I'm having this problem now after getting a brand new unopened lg g4.
Kingaries79 said:
I been having this annoying issue with the top left corner not responding to touch. This will often happen when I'm in a app or have multiple apps open. This never happened before. Until I got this replacement device. Has anyone else experience this issue?
Click to expand...
Click to collapse
I had the same issue a few days ago. This was after I flashed back to stock and just finished adding all my apps back. I don't know if flashing back or adding an app caused it. All I did was kdz back and my top left corner started working again.
Try to remove facebook messenger , restart and try it will be solved (worked with me )
FB Messenger is definitely the problem. I can pretty much guarantee it. Been testing it here and that's what I keep seeing as the cause of the issue.
samseed101 said:
FB Messenger is definitely the problem. I can pretty much guarantee it. Been testing it here and that's what I keep seeing as the cause of the issue.
Click to expand...
Click to collapse
How did you come to that determination?
Kingaries79 said:
How did you come to that determination?
Click to expand...
Click to collapse
The short version, a buttload of testing with various different phones between myself and other digital forensic examiners. Can't exactly say WHAT is causing it in their code. But we can comfortably say that it is being caused by the app. We have some speculation as to the problem, but not enough to exactly pinpoint it. But we can comfortably saw that it's Facebook Messenger.
I uninstalled the app and my screen started to work properly again. Kinda wish I knew this 3 replacement phones ago.