Hi all,
Hope someone can help. I don't mind some bugs, I expect it with Android systems, especially when using nightly ROM builds. This one, however, is really annoying and starting to get in the way of using my phone, sometimes I can't answer the phone when someone is calling, and so on.
It's been happening since I was using Hydracore 5 and the CM10 nightlies from 2-3 weeks ago, I've since flashed Hydracore 7 and the latest nightlies in the hopes that it was a bug that was due to be fixed.
On wake, maybe 20% of the time, the screen will blink for a fraction of a second then turn off. The screen stays active since I can feel the vibrate when interacting with the unlock icon. I've not figured out how to get through it, but usually just constantly turning the screen off and on, usually 15-20 times, will eventually make the screen's light stay on. As I said, it's super annoying as it's the kind of bug that directly interferes with using the phone.
I really hope this is a known bug with a workaround but my usually good google-fu isn't finding anything. I'd hugely appreciate anyone who can point me in the right direction.
Related
I have been having some issues with the torch/flashlight LED programs recently. I didn't used to have problems and prior to this when I used the HTC torch it had the same problem. When I used older versions of MIUI I didn't have this problem with flashlight apps that I had. But now with the most recent versions (since December or so I think when they added the torch button in the notification bar) I am having the problem again.
The problem when using a flashlight app (or the button in the notification bar) the light will turn on for about a second and then turn off. It will still show it off in the app or on the notification bar. If it does not do this it does one of 2 other things. It turns on and then after one second becomes brighter and then after about 1 more second turns off. On rare occasions in an app I can turn it on and it will stay on... but then when I try and turn it off there is usually a delay of a few seconds before it actually turns off. Then it is back to turning on for a second then off.
I had seen this same problem when I used the HTC Torch previously but it went away when using different ROMs and such so it makes me believe it is some kind of software problem. Seeing that the LED does seem to work and if I use the camera it seems to actually work properly with the program I am pretty sure there is nothing actually wrong with the hardware. Has anyone else seen this problem or know what could be causing it? Is there some way or some test program I could use to find what exactly is causing the problem? If someone has had this issue before... do they know how to fix it?
EDIT: I tried manually turning on the flashlight via "echo 1 > /sys/devices/platform/flashlight.0/leds/flashlight/brightness" and it turns the light on but then after about a second gets brighter then after another second turns off. When I did a "cat /sys/devices/platform/flashlight.0/leds/flashlight/brightness" it seems something changed it from the "1" which I wrote to the file to "127". Also, when I tried to "echo 0" to the file... the change did not stay. After doing the echo and then trying to cat the file it was still "127". I then tried to the torch app in the notification bar to turn it on and then off. After I turned it off via the application, I check the file and it was then set back to 0.
EDIT: I have witnessed the issue on 3 seperate Nexus One phones... surely someone else has had the same problem and possibly come up wit a solution.
you have to be careful with the flashlight apps esp with the high brightness setting. the LED is not designed to be on constantly on the nexus one and i have heard of people burning out their LED's from leaving it on too long both in normal and high brightness modes.
i have found out while using mine esp in high brightness if its left on too long it will overheat it and flicker. ever sense i seen mine do that i never use high brightness in fear of burning it out and when i use it in normal mode i try to keep its use as short as possible and i have not had it shut off on me sense. if yours is shutting off in normal mode then i'm afraid you may have already damaged it too much and that is why its turning itself off. thats my opinion anyways.
(if roms matter, i've always ran CM6 and now currently have been running CM7 nightlies and RC's
Frito11 said:
you have to be careful with the flashlight apps esp with the high brightness setting. the LED is not designed to be on constantly on the nexus one and i have heard of people burning out their LED's from leaving it on too long both in normal and high brightness modes.
i have found out while using mine esp in high brightness if its left on too long it will overheat it and flicker. ever sense i seen mine do that i never use high brightness in fear of burning it out and when i use it in normal mode i try to keep its use as short as possible and i have not had it shut off on me sense. if yours is shutting off in normal mode then i'm afraid you may have already damaged it too much and that is why its turning itself off. thats my opinion anyways.
(if roms matter, i've always ran CM6 and now currently have been running CM7 nightlies and RC's
Click to expand...
Click to collapse
Well... I would expect... if the LED was "burned out" then it shouldn't turn on at all. The simple fact that it turns on at all means the LED isn't burnt out. Also, I would suspect that to be the case if I had not witnessed it happen on a brand new Nexus One (Old one of a friends was replaced because it was stolen). Her's had to go in for repair (turns out a cable inside the phone going to the camera was loose) and I had reverted it back to an original ROM. Once it was reverted the LED didn't have problem. Another thing that indicates to me that it is a software problem is I have seen the exact same thing before on previous versions... and it went away when changing to other ROMs. Tonight I am thinking I will wipe and flash CM7 and test it with a light app and make sure... if that has the same symptom I will flash to a shipped ROM and test it. I am pretty sure it is a software issue though. I just don't know... what... is causing the problem.
EDIT: I also forgot to mention... when it was working properly... I never witnessed it overheat and flicker though I never had it on for long periods of time. One last thing, I only saw the symptoms after a flash to a new version. When it was working properly it was always working properly. When it was acting like this on a ROM it always acted like this.
UPDATE: I did flash to CM7 nightly and the torch app works perfectly as do other apps on the market. After being back on CM7 and with the advent of the theming engine for it... I think I may just end up moving back to CM for daily use. I would like to know if anyone else has run into this issue still and/or has a solution just in case I run into the same issue later. For now I think I will just chalk it up as a kernel/ROM problem... though it doesn't explain why others didn't have the same issue =/.
I know that there are random reboot/freeze issues with this phone but I have noticed that my issue seems a bit different.
My phone goes into reboot loops and freezing only when I turn on the WiFi. I'm patiently waiting for the LG "update fix" but wanted some advice from the experts.
Im in afghanistan and only have until next week to return the phone. If it is a software issue then I dont mind waiting but if it is hardware then I dont want to get stuck with a 600.00 paperweight.
I know Im shooting in the dark but I really would appreciate some thoughts or advice.
BTW - I have had the same issues on custom ROM's and stock ROM's. I think I damn near flashed the phone with every possible thing i found on this board, haha.
well it seems like my issue is still isolated to wiFi. The phone has almost no reboots and very little freezes when WiFi is off. any ideas on if this is a possible hardware or software issue?
was it with every ROM you tried the same ?
It happens with every rom but I hate to get my hopes up but it seems to have start happening not as often. right now Im using this
[ROM][21/4-11]TK-ROM Vanilla + LG = true. v0.5.7 (Fr12)
couple of hours so far and it is better but not perfect.
Mine has just recently been randomly rebooting but was fine when I first got it. It never seems to reboot when I'm stationary only when I'm in the car or riding my bike. Twice it happened in the same location on the drive home from work which got me thinking it could be location related. The gps wasn't active at the time so I tried turning off wifi/cell tower location in the options. I managed a two hour bike ride with no reboots today whilst using gps tracking and listening to music. Yesterday the phone wouldn't go more than 10 minutes without rebooting.
Could it be bad location data in some mobile phone masts are making the phone crash due to a bug in the software?
Sent from my LG-P990 using XDA App
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!
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".
Hi. I tried to post in the EuphoriaOS thread, but I don't have enough posts to say something in the development section.
My Nexus 6 is currently using the latest official EuphoriaOS 1.1 and everything has been great up until about a month ago.
This happens sporadically. My phone will start to freeze in the middle of doing anything.
Ex1. I'm listening to Spotify and my music will freeze every 10 seconds or so. Instead of being like a normal skip, it picks up exactly where it left off.
Ex2. I push the power button to wake my phone, but nothing happens for ~3 seconds. Pushing it again will bring up my lockscreen, but my lockscreen is totally unresponsive, so I can't unlock my phone. I can use the power button to turn the screen back off. Then I will wake it again like normal, and It unlocks just fine.
Ex3. My UI in general becomes sluggish and at times completely unresponsive.
Ex4. My phone will just restart randomly. It has done it numerous times each in different applications. I haven't been able to pinpoint a cause.
I enjoy using Euphoria and do not want to update to any Marshmallow ROMs because I have everything the way I like it. My battery is great and Marshmallow currently doesn't have Xposed.
I haven't really installed anything new since before these issues started. They just happened out of the blue.
This stuff happens maybe every couple days at totally random times.
Could anyone help me in trying to fix the issues I'm having?