Related
Hey guys, my nookcolor has been randomly rebooting since i rooted it. Never while i was using it, i just sometimes hear the bootup sound, and look to find that my book is now on.
Im just concerned this will affect my battery, and i also don't want it rebooting while im using it.
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Divine_Madcat said:
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Click to expand...
Click to collapse
I still want to use the B&N stuff. Any rom that emits them, I will not be installing.
I think it likely that there are NC users in both camps-
Those who want the B&N stuff and those who don't.
I am one of those who don't; the Nook for Android software does better for reading ePub, imo and I am rarely near a B&N store.
Right now we have root and Market plus B&N and I would guess (could easily be wrong) that the first custom roms will be pure Android with no B&N.
We will probably end up with an option to set while flashing: retain B&N customizations or straight Android.
I base this guess on what I have seen in the other roms for various devices (mainly Droid) I have looked at.
Same here. If I want to read B&N books, I could still use their Android app on a custom ROM.
After switching to Cyanogen on my phone, it's been quite relaxing to not have to worry about provider updates bricking the thing or otherwise screwing up the rooted customizations (or just randomly resetting the thing back to factory defaults because I started up one of their apps and it got confused). Not to mention that the CM team does a far better job supporting the device than the manufacturer and my service provider does.
And yes, like other Android devices, there will probably be ROMs in both categories: completely built from scratch with no B&N portions at all, and improvements on the B&N system to add more functionality.
Fair enough for those that are interested in the reader portions - i have to admit, i bought this as a tablet, with literally 0% in it as an e-reader; i already have a Sony 505 for that. I may use it on occasion, but only as an afterthought.
However, this topic is really drifting - perhaps we should just bring it back to the rebooting issue?
Yeah, I installed the Uptime Widget on my NC today and picked it up a few ago and its uptime was 1:30; max 15h (from before it rebooted 90 minutes ago). I'll keep running it.
What we need to do is get a logcat when it happens.. So maybe overnight I'll leave it running or something. It just rebooted on me and I was semi-watching it, didn't even notice but Uptime Widget was reset to 7m up, 15:30 max..
I have started up a logcat and I'm going to leave it running while I get ready to go out for the day.. Although I just installed and fiddled with Google Earth, which failed badly, so I wonder if it caused some problem. Also saw it happen after playing with Google Maps, so I wonder about Location stuff maybe doing it.. Dunno. I just launched Maps a few ago and it's been up since. Hopefully a logcat will capture some info.
I have noticed that I've seen some crashes that don't show the Crash dialog.... TweetDeck is particularly bad about crashing viewing some Facebook posts, and in this case it just goes black for half a second then back to the list of posts. A logcat shows it crashed. But I don't know the two are related (not having the crash dialog stuff and the reboots that is).
I had it reboot on me twice last night, one time I didn't know about it until I picked it up later and noticed the uptime widget was down to some 30 minutes, and another time right before bed I hit the power button and about 10s later I saw the boot up text and a reboot happen.
Still haven't caught it on logcat.
My doesn't reboot spontaneously, but it does "lock up" and won't turn on with the power button from standby occasionally. If I remember to use the Nook Button to wake from standby, I don't seem to have this issue. If I use the power button, and it won't wake, I need to hold it down for ~15 seconds and it reboots.
AFIAK, it has done this since I purchased it (I rooted after about 1 hour with the NC in my hands).
Mine has never reboot WHILE I'm using it, it's sneaky about it. But I suppose I'd much prefer it reboot while I'm not using it than while I'm using it; I have yet to have it do a full reboot while using it.
Trying to set up a Delicious account.. yeah, that rebooted the Java VM. But only time I've made it reboot at all.
Hahah, damnit, it just rebooted after it went to sleep. I seriously think it has something to do with going to sleep. I've been sleeping it and waking it repeatedly on adb logcat and it won't crash. Figures.
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
isolated_epidemic said:
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
Click to expand...
Click to collapse
Actually not using any of those on mine.. I have Beautiful Widgets in ADW and Beautiful Widgets + Note Widget in WidgetLocker.. Not adjusting the backlight at all either, in fact I don't think I have at all since getting it now that I think about it.
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
mastroiani said:
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
Click to expand...
Click to collapse
I suspect it's a software thing, as it doesn't randomly reboot in use, it ONLY seems to happen going into standby, and I have YET to make it happen connected USB for adb.
You know actually, I think alogcat can log automatically now, maybe I should try that.. but it'd have to run for a day or so, as I only see this happen like twice a day at most.
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
wvcachi said:
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
Click to expand...
Click to collapse
I myself had not played with SetCPU at all. So had you in the past and set it to conservative, and switched it back, or you switched it from its defaults? Reminds me, per my observation that it never has rebooted while on AC or USB, was there a default profile when plugged in that it's set to ondemand vs conservative? This could start making some weird kind of sense. I'll try it, but using something called CPU Tuner since it's free..
EDIT: I looked on USB and on Battery, both times was conservative, so looks like that's the default... Does the Nook have an automatic switching utility like cpuspeed in it? Hmm.. /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is the file if anyone else wants to look.
BTW, has anyone on 1.0.1 auto-nooted etc not seen these random sneaky ninja power-off reboots? I swear mine waits until I'm not looking and reboots. I've only SEEN it do it once or twice, but in the last 5 or so days it's rebooted at least 10 times while powered off. Again NEVER while I'm using it, so I'm at least thankful for that. If it were rebooting while using it that would not be acceptable.
I have the Uptime Widget, kinda wished I had an uptime graph to see if there is a pattern.. I'm about 99% sure it never happens when plugged in AC or USB.
EDIT2: IT IS CLEARLY MOCKING ME. It just rebooted after I peeked at the governor files and let it idle to sleep.
I have the same random reboot problem since I upgraded to 1.0.1 and used auto-nooter. I only see it when it goes to sleep...or so I thought. This morning I heard it reboot and i hadn't touched it since last night. FYI, it was not plugged in when it happened. Thankfully it never reboots while in use.
Oh...ad i havent used any CPU clocking tools. Also...never saw this on 1.0. So weird but I am sure someone smarter than I will figure it out.
UPDATE- Just got out of the shower and while getting dresses...heard the Book reboot twice within a minute or two.
Wondering if its an app that is causing a fatal crash when it tries to update.
Sent from my Nooxus One using Tapatalk
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
rckymtnrfc said:
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
Click to expand...
Click to collapse
I've had one unexpected reboot today that I know of, I think this has helped, although I keep finding my Wifi turned off, even though this program I installed is only set to turn it off when the battery is extremely low. So I changed that profile and it hasn't turned itself off since, so seems to me maybe the battery reporting is a little wonky sometimes.
I've been watching, and I'll keep an eye out, but I think wvcachi is onto something.
BTW, the Nook has been primarily idle for the last 5 hours, just popped it on a few times to read an email, check on something, or see if it reboots so I haven't used it a bunch but it's lost a whopping 2% battery in that time. I also disabled the Phone stuff too, per this thread:
http://forum.xda-developers.com/showthread.php?t=883908
I am at 6.5 hours now....no rebooting so far.
Sent from my Nooxus One using Tapatalk
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.
So here is the thing my screen is turning on randomly, but i've noticed 2 things
1 - When the phone is charging the screen does not turn on
2 - when i'm downloading anything the screen does not turn on too.
So my question is, is there a way to fool my system pretending that i'm downloading something that never ends or something like that? the battery comsumption is making me crazy.
whyzack_br said:
So here is the thing my screen is turning on randomly, but i've noticed 2 things
1 - When the phone is charging the screen does not turn on
2 - when i'm downloading anything the screen does not turn on too.
So my question is, is there a way to fool my system pretenfing that i'm downloading something that never ends or something like that? the battery comsumption is making me crazy.
Click to expand...
Click to collapse
You probably have some app that is making a mess. Do you use some lockscreen or notification app? Or something similar to those.
shut_down said:
You probably have some app that is making a mess. Do you use some lockscreen or notification app? Or something similar to those.
Click to expand...
Click to collapse
I don't think so, I Just applied the Cyanogen with Gapps, nothing more, and wiped everything but the problem always come back. /=
This might be a hardware issue. I faced a similar problem a few months back. I fixed it by cleaning my phone's micro USB port and the earphone jack.
In my case, it was caused because of build up of dirt.. my phone often "assumed" that I plugged in my USB cable and/or my earphone, that's why its display would turn on randomly.
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.
.