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 can't put my finger on this issue I've been having with my Note.
Don't get me wrong, this device is a godsend!
The problem I've been having is that sometimes when I take my Note out of my pocket and try to press the unlock or menu button it doesn't show anything on the screen. I've read about people having issues with delay before it pops up, but it doesn't pop up even after 10 seconds or a minute, it feels like the device 'hangs' or doesn't want to wake up. The only way I can turn the phone on again is by pressing the unlock button for like 10 seconds and the phone reboots.
I thought it was a problem with Green Power, I thought it maybe had issues turning off the wifi or data when the screen was locked and that the service would cause the OS to crash or 'hang'. When I look at my battery history after the reboot it shows that I lost a significant amount of battery (5-15%, depending on how long it took for me to 'discover' the crash) and there's a 'jump' in the graph.
Things I've tried:
Stock rom - problem persists
Different kernels - tried all the kernels available in the market including stock, problem persists
Add a bit of paper between back-cover and battery (to make sure it doesn't lose contact)
Checked if there was dust between battery connections
Tried different sim card
Tried disabling wifi and data all day (mysteriously persists)
DIfferent governors (ondemand and interactive) (the phone reverts to default governor after the forced reboot, normal? i have my phone set to interactive on boot, but somehow it skips that after the forced reboot)
I've attached a picture of the battery graph. According to the stats there's a 25 minute gap where the phone was 'stuck' and you can see that the screen was on and active for that duration.
There are NO funny apps running in the background, this is is a clean install with some standard Samsung apps frozen.
tl;dr version: phone randomly won't wake up; battery loss after forced reboot;
I might have found the issue myself. Now when I come to think of it, I think it always occurs after I've been in my car for like a 30 min drive... Maybe the phone is having trouble switching networks? Anyone know what might be causing this?
Or better yet, how can I research this issue? Can I enable some logging somewhere to track this?
I had the note for about 10 days and today, about 1 hour ago it happened to me for the first time. I tried the home button to wake the screen but nothing, tried the power , nothing and holding the power but nothing happened. I had to pull the battery.
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
tamarian said:
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
Click to expand...
Click to collapse
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
I'm on stock room and unrooted. Like I said first time it's happened.
i've had the GNote since 4 days now , and yesterday same thing happened as the device was in my pocket and i couldnt wake it up at all , battery pull solved it.
im on stock , non rooted
I can't believe that we are the only ones with this issue. Anyone else? OR better yet, how did you resolve it?
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
kirkla79 said:
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
Click to expand...
Click to collapse
Thanks for your reply. I did some research, and apparently it had to do with static being built up in the screen from wearing it towards your body in your pocket.
This issue was that you couldn't swipe the lockscreen cause the touch screen wouldn't respond. The problem we are having is that the screen won't even turn on and that the system locks up.
Same issue here with my 2 days old Galaxy Note, that's how I found this forum. In my case it went from not waking up occasionally to every time WIFI was ON (I did some experimenting with settings to see which one could be the one causing the problem). But then...occasionally it would not wake up even with WIFI OFF: very annoying. And this is my first Android, so I didn't have any custom anything, pretty much same as out of the box when I got it The only solution was to reset the handset. And definitely has nothing to do with having it in my pocket as I don't carry it in my pocket. Rang Samsung, they told me it was faulty, I returned it. Now I'm concern the next one is going to have screen issues? As so many people complain in this forum? we'll see.
My issues have been resolved after flashing AbyssNote 1.4 and when I stopped using System Tuner. I've started using Voltage Control instead and now I'm not even having problem @ 100Mhz undervolted 50mV from stock.
Same problem with my wife's Gnote, totally stock, just a small handful of apps installed. Happened twice, about a week apart.
She does a lot of travelling, maybe you're right about that. But it happens after she gets home when it's still OK.
Had the same same issue twice in two days and had to do a battery pull, just did a master reset and re -installed the applications manually, so far so go.
YOu guys think its a hardware or a software issue?
Hmm.. Happened to me too about three times in the last two weeks. I am on stock rom but rooted, and running Green Power. Hopefully samsung will fix it in the next updates. Seems like a software bug to me. Maybe not enough juice when in deep sleep?
metus666 said:
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
Click to expand...
Click to collapse
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
neunzehn77 said:
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
Click to expand...
Click to collapse
problem is it also happens on stock rom.
mfractal said:
problem is it also happens on stock rom.
Click to expand...
Click to collapse
It's very well possible that the stock kernel has faulty settings for the CPU. Haven't had the problem again with AbyssNote 1.4 and Voltage Control (even with custom cpu frequencies)
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
qazkamakazi said:
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
Click to expand...
Click to collapse
at this point we're just guessing, there haven't been any official confirmations of the problem as far as i know.
But if it's so accute that it keeps happening all the time you must have a faulty device.. call samsung ?
Like every other device on the market, the HTC ONE is not perfect, both at device and software levels it is likely that some glitches and hitches will be discovered, this is exactly the place to report those bugs. It is important here to distinguish between a bug from the device and a bug from an XDA ROM developer, the latter case must be reported in the appropriate topic and not here.
Confirmed or Known BUGS:
BUG : I find that on the odd occasion my back button or home button becomes dead.
SOLUTION : Have a read HERE
BUG : Beats causes a hissing background noise, most noticeable at low volumes.
SOLUTION : Some say disabling WiFi and re enabling it solved their issue.
BUG : Bluetooth streaming audio issues, audio keeps cutting out.
SOLUTION : Some has solved this by disabling the energy saving options or simply turn OFF WiFi. To discuss this issue click HERE
BUG :
SOLUTION :
BUG :
SOLUTION :
Post your bugs and issues and if they get confirmed frequently I will add them to this list.
I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something. A minor inconvenience.
Other than that I've not experienced anything else.
I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something.
Click to expand...
Click to collapse
Also beats causes a hissing background noise, most noticeable at low volumes.
Xperia23 said:
I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something. A minor inconvenience.
Other than that I've not experienced anything else.
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=2231832
Thank you guys, OP updated.
the cursor jumps into false positions, when i drag it to one. (keyboard)
Sometimes my keyboard disappears, when i was writing and no i didnt pressed back or anything like this.
o2 v1.27 firmware
I had a weird issue in the car the other day
I was using the USB plugged into a Fiat 500 which has the Blue & Me system. I wasn't particularly bothered about having sound through the speakers, I just wanted to charge.
The stereo turned on anyway, and I was having random directions given through the stereo, with the Highlight Video music in between!! And then the ACTUAL directions coming through the phone speakers. I just turned the stereo off but it was really weird
Martin
I've had problems with random restarts and WiFi not connecting/WiFI settings freezing. Not allowing WiFi to be switched off during sleep seems to have cured it.
HTC One M7 speaker
I got my new HTC one the othe day from Harvey Norman and I have noticed that the bottom one of the two speakers cuts in and out and if you press on it then it works, but this is for all audio has anyone had this issue or know why it is happening?
Thanks
I got my HTC One last week and the wifi signal is really weak. When I am at 5mt from the hub (virgin media) I bearly have a signal.
My boyfriend's Xperia Z (with known wifi issues) has more signal at the same distance.
Anyone else experiencing this?
Phone in pocket after call
I am surprised no one has reported this annoying bug:
1) Have the phone in the pocket
2) Listen to music via the provided headphones (same if you use bluetooth)
3) Someone calls you and you answer via headphones button
4) After you or the other party hangs the phone, the phone turns on in the pocket.
VERY annoying!!! Please report this bug to HTC (I already did)
Otherwise I just LOVE this phone!!!
Problems charging phone and file transfers.
Ive had my HTC One for just over 2 months now. Havent had any issues besides the back button not responding. But just the last few days out of the blue, i am unable to charge my phone using the provided htc micro usb cbale that came with the phone to charge my phone. Keeps saying to use supported cable or doesnt detect my phone at all. It wont even charge through the wall power point using the adapter and cable provided. Ive attempted using other micro usb cables from previous devices and still no luck. Only way to charge my phone is using the extend battery pack.But have to restart my phone before charge otherwise it wont detect usb connection.
I also unable to copy and transfer files from my phone to pc also due to the usb cable and detection issue.
Has anyone else here experienced the same issue?
If so,how did you resolve the issue?
ive contacted HTC Support and still waiting on a response.
xqlusive84 said:
Ive had my HTC One for just over 2 months now. Havent had any issues besides the back button not responding. But just the last few days out of the blue, i am unable to charge my phone using the provided htc micro usb cbale that came with the phone to charge my phone. Keeps saying to use supported cable or doesnt detect my phone at all. It wont even charge through the wall power point using the adapter and cable provided. Ive attempted using other micro usb cables from previous devices and still no luck. Only way to charge my phone is using the extend battery pack.But have to restart my phone before charge otherwise it wont detect usb connection.
I also unable to copy and transfer files from my phone to pc also due to the usb cable and detection issue.
Has anyone else here experienced the same issue?
If so,how did you resolve the issue?
ive contacted HTC Support and still waiting on a response.
Click to expand...
Click to collapse
Sounds like you have accidentally bent some pins in the connection, potentially hardware not software related. I'd return for exchange.
2G connection issues
I have no idea whether its my ONE's problem or of the connection provider........ I cant use my 2G connection, it connects and disconnects at its will........Is there any way to test whether my ONE has any problem?
Strangeness with touch screen sounds
I may be the the only one.... but I like a click sound when the touch screen is presssed for a command. This works alright on my Sensation (pyramid) but not on my new HTC (M7).
There is sometimes a very very faint noise about a second or more after touching the screen for a command, kind of a delayed reaction? Anyway no amount of tweaking volume controls or using any sound mod produces a decent loud click sound. I revert any tweaks after experimenting with them.
Setup; HTC M7ul - ARHD ROM (12 currently)
Any information on this would be gratefully received!
This has been annoying me for the past week...
When I make or receive a call people tell me that they hear me far away. People cant tell its me on the phone! Gonna try to clean the speakers with a toothbrush but this phone is fairly new, bought it in September...
Push Bug (Whats app, sms), htc stay in standby
Hey,
I'm new here and i hope, this is the right forum for my problem
I bought me a htc one a few days ago, and i've already root it, unlocked the bootloader, set it s-off. my recovery tool is twrp-2.6.3.3, and i have the ViperOne 4.3.0 with ElementalX-m7-10.10.1. for the rights management i use LBE_Security, exactly this Version: LBE_Security_RC_5.1.5446_A1_EN_VI_1st_12.20.2013.
Sometimes, 2-4 times/day, if i write with somebay via sms or whats app, and my handy is in standby and i get the message, my handy vibrates and the LED blinks green, and when i try to unlock it, with double2wake or logo2wake, my handy vibrates, but my display still is black, like it is still in standy. Music works, i can turn the volume higher or lower, and i can keep klicking the power button or double2wake or logo2wake, but my display didn't react. It only vibrates, wenn i click use double2wake or logo2wake. i have to click the power button and the lower-sound button to reboot my handy.
First i thought, maybe it is the kernel, because i used undervolt 800 and max cpu 1890mhz, so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too. this is something i can live with, but not the problem with push messages.
And i don't know how to contrain the apperance of the bug. yesterday i installed everything new, and i install lbe security master, too, but i think, i forgot to give him superuser right, because today apps pushed me things, but they weren't allowed to do this. maybe it has something to do with the bug, but today i realised it and set lbe as a superuser and then the bug appeared again. before that the bug didn't appeared. maybe it was coincidence, i don't know.
all i know, is that the bug has something to do with sms and whats push, and i'm not 100% sure, but i think it's not the fault of the kernel elementalX. Maybe it's LBE or Viper Rom's fault, or may something else.
Do somebody please help me? This bug is very annoying me and i don't know android very well, it's my first android phone.
And excuse me for my bad englisch, i am from Germany and i wasn't good in englisch in school
thepate94227 said:
Hey,
I'm new here and i hope, this is the right forum for my problem
I bought me a htc one a few days ago, and i've already root it, unlocked the bootloader, set it s-off. my recovery tool is twrp-2.6.3.3, and i have the ViperOne 4.3.0 with ElementalX-m7-10.10.1. for the rights management i use LBE_Security, exactly this Version: LBE_Security_RC_5.1.5446_A1_EN_VI_1st_12.20.2013.
Sometimes, 2-4 times/day, if i write with somebay via sms or whats app, and my handy is in standby and i get the message, my handy vibrates and the LED blinks green, and when i try to unlock it, with double2wake or logo2wake, my handy vibrates, but my display still is black, like it is still in standy. Music works, i can turn the volume higher or lower, and i can keep klicking the power button or double2wake or logo2wake, but my display didn't react. It only vibrates, wenn i click use double2wake or logo2wake. i have to click the power button and the lower-sound button to reboot my handy.
First i thought, maybe it is the kernel, because i used undervolt 800 and max cpu 1890mhz, so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too. this is something i can live with, but not the problem with push messages.
And i don't know how to contrain the apperance of the bug. yesterday i installed everything new, and i install lbe security master, too, but i think, i forgot to give him superuser right, because today apps pushed me things, but they weren't allowed to do this. maybe it has something to do with the bug, but today i realised it and set lbe as a superuser and then the bug appeared again. before that the bug didn't appeared. maybe it was coincidence, i don't know.
all i know, is that the bug has something to do with sms and whats push, and i'm not 100% sure, but i think it's not the fault of the kernel elementalX. Maybe it's LBE or Viper Rom's fault, or may something else.
Do somebody please help me? This bug is very annoying me and i don't know android very well, it's my first android phone.
And excuse me for my bad englisch, i am from Germany and i wasn't good in englisch in school
Click to expand...
Click to collapse
Sounds like you've set your minimum frequency/screen off to too low, increase it to around 800Mhz and see whether you face the same problems again.
Sent from my iPod touch using Tapatalk
thepate94227 said:
so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too.
Click to expand...
Click to collapse
There's a fix for the camera bug in Venom Hub/Addons/Other
Thank you for your answers
@spiralOut
Thank you, this add-on fixed the camera bug, I hope, it fix the other too
@n1234d
Do you mean the undervolt option during the elemtalx kernel installation? Because first I choose 800kHz, now I choose stock, I think the stock is higher than 800, right? And the bug still appeared.
And what I forget to say: I used the swift option from HTC, that i can write with swiping on my keyboard, maybe this has something to do with the bug, now today I deactivated it.
Hey,
I have an HTC One black - stock os - UK unlocked version - after 4.2.2 update.
I've got a strange problem regarding the top of the touchscreen. when the phone is horizontal, the top bit (between the top bar to the first widget) is not working. the rest of the screen working fine. when I pick the device up, the screen is working fine 70% of the time. as a result, I cant open the notification bar and it thinks that I'm clicking or re-arranging my widgets.
It's weird because IT DOES work 60% of the time.
1. did any of you experienced any of this before?
2. What do you think it is? software or I have to replace the digitizer?
3. Is it just calibration problem? I tried to calibrate the device using the keyboard screen calibration and it didn't do anything.
Thanks!
Eran.
i have a similar problem and no solution so far
sandmann241 said:
i have a similar problem and no solution so far
Click to expand...
Click to collapse
so what did you do/planing to do?
eranbaruch said:
so what did you do/planing to do?
Click to expand...
Click to collapse
Bump for more responses
I
I just started experiencing this same problem today as well. I was on a Google Edition 4.3 Rom for about 2 days, Viper 3.2 I believe and everything was initially working as it should. Suddenly I began experiencing the non responsive status bar. I cleared data & cache, fixed permissions, and even tried a factory reset with no luck. I then reinstalled the Rom and the problem persisted. I then downloaded and installed black jelly Rom along with a complete wipe of the entire storage after transferring important data to my PC, but the status bar was still unresponsive and it appeared the top 1/4 inch of display had a digitizer issue. I tried to restore an older backup of Venom Rom running Sense and I still had no luck, until I went into the browser so that I could rotate into landscape to see if I could access it from this orientation (don't know why that didn't cross my mind sooner?) After I pulled the notification shade in landscape I left it down and rotated back into portrait mode and drew the shade back up slowly, following through with the gesture all the way to the top of the display. Then the functionality from portrait was restored! I believe this is a software bug of some sort, but I'm contemplating returning it to stock and relocking the bootloader to return it. I'm actually using the Tmobile variant and it's only about 30 days old. My insurance will cover a replacement for a faulty unit, but who knows if will happen with another? After a Google search I discovered this was an issue that surfaced with quite a few One X's as well, so I'm thinking it may be a bug that's consistent with some HTC hardware of a different variants? Any updates or insight would be appreciated.
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
So weird, but same thing has been happening to me the past few days. But I have a justified cause. It started immediately after installing Franco Kernel.
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Pkt_Lnt said:
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Click to expand...
Click to collapse
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
I've since flashed stock pn, and now elementalx. It's not acted up yet. Seemes to be a better performance kernel. We'll see how battery is. Sorry to hijack your thread!
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
Click to expand...
Click to collapse
Well, so much for "scientific testing" and wishful thinking.....didn't take long to eliminate the wristwatch, now to fix the problem.
.