Related
I searched and found nothing like this.
When I boot my Nook Color, running Cyanogenmod 7, any recent nightly, wireless is off, even though it was on before booting.
I open Notifications, tap the wireless, it turns on and works fine. I've checked, airplane mode is not on.
Updating to newer nightlies doesn't work. I'm pretty sure this used to work. My glacier doesn't have this behavior.
Any thoughts on how to fix this so the wireless state is retained over boots?
I have the same thing but I actually prefer it this way since I use it so much for reading.
I think those lately night builds have screwed up a few things such wireless OFF on boot. Another itchy part (for me) is the Terminal Emulator somehow got blue background and when "exit" command, it doesn't exit but I must force it off under Managing Applications.
votinh said:
I think those lately night builds have screwed up a few things such wireless OFF on boot.
Click to expand...
Click to collapse
Ah, thanks. I suppose I can't file a bug since it is a nightly, I'll mention it on the appropriate thread and hope.
Another itchy part (for me) is the Terminal Emulator somehow got blue background and when "exit" command, it doesn't exit but I must force it off under Managing Applications.
Click to expand...
Click to collapse
Press the menu key, then "Reset term".
Yeap, that's another less painful way to close T.E.
Try downloading android assistant from the market and checking to see if you have airplane mode on through the app.
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
Try downloading android assistant from the market and checking to see if you have airplane mode on through the app.
Click to expand...
Click to collapse
I had it, and got rid of it because it wasn't doing anything for me. I'm pretty sure I had checked this before *and* I have flashed several times, but I just got it and...the airplane is blue. I've got a thread on a dev thread, I'll ask about it getting fixed, clearly shouldn't be happening.
excarnate said:
I had it, and got rid of it because it wasn't doing anything for me. I'm pretty sure I had checked this before *and* I have flashed several times, but I just got it and...the airplane is blue. I've got a thread on a dev thread, I'll ask about it getting fixed, clearly shouldn't be happening.
Click to expand...
Click to collapse
It should not be blue. Tap on it and it should turn gray. Problem solved.
Sent from my LG Optimus V using Tapatalk
Is there an actual answer for this issuer? Is this designed by the CM7 team?
thereddog said:
Is there an actual answer for this issuer? Is this designed by the CM7 team?
Click to expand...
Click to collapse
It's an Android problem. Something to do with missing radios. Happens on the touchpad too.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
Definitely not a nightly problem, it's that way in the official release too.
Sent from my NookColor using xda premium
Some smart CyanogenMod users fixed this problem. Perhaps their methods would work for you as well as they worked for me.
I guess we just have to avoid accidentally enabling airplane mode.
I actually prefer wifi off on boot as I don't need it most of the time and it just drains the battery.
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
a67543210 said:
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I can't believe this ! Is this a SAMSUNG or an Android/ICS problem ?
My version is:
4.0.3
IM74K.XXLPQ
Any custom ROMs addressed this issue or how can you avoid this on ICS? Is the only solution to go back to Gingerbread ?
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Its a bit like continual posting in the wrong forum nobody knows why ??
jje
rumz82 said:
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Click to expand...
Click to collapse
No overheating (yet) you can help if you can keep logcatting through usb cable till it lock/standby freezes and your screen won't come on when pressing power ..
Install SDK + Drivers, write in commandprompt:
adb shell logcat > save.txt
Wait for the error / freeze where screen won't come on.
Then paste here or upload somewhere might contain a lead to a solution!
Double - sry - galaxy forgot login
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
thedadio said:
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nah!
It's there on all the kernels. I myself am a Siyah user.
I moved back to GB for this weird and terribly serious issue, but that time i didn't know it was a common problem.
This is ICS' best feature for sure.
I really CAN NOT believe how this issue is NOT yet known well and haven't brought in to front line. Google knows about it and yet I haven't seen any official statements about it. How ****in unbelievable or not perhaps? Google way?? Well **** it.
Utter Nonsense. What i wonder is, really, does any Android user actually use the phone but show off only??
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
gtcardwhere said:
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
Click to expand...
Click to collapse
Do the logcat as I provided the correct command to extract it to a file.
Then do your torrent thing, and make it crash- so we can debug !
Used to happen, since I installed latest hydrog3n-ICS rom (13-05) never had those again!
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
sunshean said:
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
Click to expand...
Click to collapse
uv?
ultra-violet ? is my phone in danger of skincancer ?
dezzadk said:
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
Click to expand...
Click to collapse
Hi,
It happened to me as well after the ICS update and I tried to plug the AC charger to see what happens, and surprise...the screen turned on .
It's not a fix (especially when away with no accessories) but it's better than nothing, hope this helps; also you should try plugging the USB cable. Tell me if it helps.
Thanks,
dezzadk said:
uv?
ultra-violet ? is my phone in danger of skincancer ?
Click to expand...
Click to collapse
Haaaaahahah! He means under volting. I don't know if you was serious lol but just saying. I'm on cm9 but don't have this problem :-/.
Sent from my GT-I9100 using xda premium
Yep,I mean under volting, you need to look your kernel, and I think it doesn't work fine because your kernel has under volting so much.
Sent from my GT-I9100 using Tapatalk
Reading around and installing load monitor from play store should fix this until a better solution is found
Sent from my GT-I9100 using Tapatalk 2
Best solution is to stay on GB because is more stable, until ICS gets better cooked!
Hi,
This problem has been going months now. And it's getting worse. Before, it was just happening when I open games that use Internet connections. However, this time, even if it's just opening the lock screen the distortion problem appears. Any help, please?
Links to videos of the screen problem below:
Months before
https://www.youtube.com/watch?v=VVKhpII6MwY
Happening now
https://www.youtube.com/watch?v=XWNleEjl6-g
chubiprince said:
Hi,
This problem has been going months now. And it's getting worse. Before, it was just happening when I open games that use Internet connections. However, this time, even if it's just opening the lock screen the distortion problem appears. Any help, please?
Links to videos of the screen problem below:
Months before
https://www.youtube.com/watch?v=VVKhpII6MwY
Happening now
https://www.youtube.com/watch?v=XWNleEjl6-g
Click to expand...
Click to collapse
It could be a number of things. Have you tried flashing new firmware or a custom ROM to see if it persists? Does it jump while it is booting up? Your digitizer could be going foul whilst displaying in some spectra. I had a similar problem myself on an HTC Rezound and it turns out the presence of Nova Launcher was the problem...
Take a screenshot and put it on your computer. If it looks fine, you have bad hardware, more than likely.
kcipopnevets said:
It could be a number of things. Have you tried flashing new firmware or a custom ROM to see if it persists? Does it jump while it is booting up? Your digitizer could be going foul whilst displaying in some spectra. I had a similar problem myself on an HTC Rezound and it turns out the presence of Nova Launcher was the problem...
Take a screenshot and put it on your computer. If it looks fine, you have bad hardware, more than likely.
Click to expand...
Click to collapse
Im using stock rom. Updated my OS via OTA. Does not jump while the boot screen is loading. I'm using Nova Launcher too. I'll try to remove Nova and see what will happen.
Anyway, this are what my screen looks like after taking a screenshot. I took this after I recorded the videos.
chubiprince said:
Im using stock rom. Updated my OS via OTA. I'm using Nova Launcher too. I'll try to remove Nova and see what will happen.
Anyway, this are what my screen looks like after taking a screenshot. I took this after I recorded the videos.
Click to expand...
Click to collapse
This is really odd... Do you mind uploading a raw screenshot?
kcipopnevets said:
This is really odd... Do you mind uploading a raw screenshot?
Click to expand...
Click to collapse
I really think this has not happen to any Nexus 7 users before. Tried to look for other pictures or videos all over the web, but I couldn't find anything. Okay, I will. Wait for a sec.
EDIT: One thing I also notice is that this only happens when I'm using WIFI, Mobile Data, or when any app tries to access the web PLUS when the device is starting to heat up.
Nothing is happening right now. My device seems normal. Will upload a raw screenshot when something happens. I'll message you too. Thanks for this! Will try to remove Nova and see what will happen.
chubiprince said:
Nothing is happening right now. My device seems normal. Will upload a raw screenshot when something happens. I'll message you too. Thanks for this! Will try to remove Nova and see what will happen.
Click to expand...
Click to collapse
I have some doubt that Nova is the problem but you're welcome! Just keep me posted, I'll be glad to help.
kcipopnevets said:
I have some doubt that Nova is the problem but you're welcome! Just keep me posted, I'll be glad to help.
Click to expand...
Click to collapse
It happened again. I took a screenshot two times and all are normal. No distortions. Why is this?
chubiprince said:
It happened again. I took a screenshot two times and all are normal. No distortions. Why is this?
Click to expand...
Click to collapse
Ah, for now it seems like a hardware issue. If you don't mind, whenever you have the chance, can you try using another ROM? Graphical artifacts that don't show up in the OS are usually signs of bad hardware, though...
If that's too much of a stretch to do, can I ask a couple more questions/favors?
kcipopnevets said:
Ah, for now it seems like a hardware issue. If you don't mind, whenever you have the chance, can you try using another ROM? Graphical artifacts that don't show up in the OS are usually signs of bad hardware, though...
If that's too much of a stretch to do, can I ask a couple more questions/favors?
Click to expand...
Click to collapse
Sorry for the late reply. There was a power outage in my place, and it took hours to get the power back. Sure, I am willing to answer your questions or do any favor, as long as it will help my device.
For flashing a new ROM, well I really don't know how to flash a ROM. Plus, the instructions here are only for Windows 7. I am Windows 8 user.
chubiprince said:
Sorry for the late reply. There was a power outage in my place, and it took hours to get the power back. Sure, I am willing to answer your questions or do any favor, as long as it will help my device.
For flashing a new ROM, well I really don't know how to flash a ROM. Plus, the instructions here are only for Windows 7. I am Windows 8 user.
Click to expand...
Click to collapse
Oh man. The outage isn't your fault in the slightest so it's okay.
Earlier you specified it happens when the tablet heats up? Maybe when it acts up, try finding a way to quickly cool it off to see if the interference stops. This issue can certainly also be caused by any underlying interference. If the tablet gets hot, try holding power until the system reboots to check if the Google screen or the boot animation jump (I'm assuming they don't?) and we'll see what happens.
And in terms of bootloader unlock and all that stuff, I thought WugFresh's Nexus Root Toolkit was compatible with 8? There are definitely drivers for the N7 so if toolkit fails, I can walk you through the alternate route to unlock manually.
kcipopnevets said:
Oh man. The outage isn't your fault in the slightest so it's okay.
Earlier you specified it happens when the tablet heats up? Maybe when it acts up, try finding a way to quickly cool it off to see if the interference stops. This issue can certainly also be caused by any underlying interference. If the tablet gets hot, try holding power until the system reboots to check if the Google screen or the boot animation jump (I'm assuming they don't?) and we'll see what happens.
And in terms of bootloader unlock and all that stuff, I thought WugFresh's Nexus Root Toolkit was compatible with 8? There are definitely drivers for the N7 so if toolkit fails, I can walk you through the alternate route to unlock manually.
Click to expand...
Click to collapse
Hmmm. I'll try it by tomorrow (It's 2 AM here. Hehe). I'll try to make the device "heat up" and restart it. I haven't tried investigating if the boot animation jumps when this distortion thing happens, so, again, I'll do it tomorrow.
I tried manually updating my Gnex before thru efran's manual tutorial (on a Windows 7), so I am okay with manual unlocking the bootloader, and trying another ROM. Just tell me the steps via Windows 8, please.
chubiprince said:
Hmmm. I'll try it by tomorrow (It's 2 AM here. Hehe). I'll try to make the device "heat up" and restart it. I haven't tried investigating if the boot animation jumps when this distortion thing happens, so, again, I'll do it tomorrow.
I tried manually updating my Gnex before thru efran's manual tutorial (on a Windows 7), so I am okay with manual unlocking the bootloader, and trying another ROM. Just tell me the steps via Windows 8, please.
Click to expand...
Click to collapse
Please forgive my tardiness, I was SUPER busy this weekend, but for the most part I'm free now.
Phase them me when you're ready!
kcipopnevets said:
Please forgive my tardiness, I was SUPER busy this weekend, but for the most part I'm free now.
Phase them me when you're ready!
Click to expand...
Click to collapse
Ready!
Can I ask for the steps on how to unlock the bootloader, and then installing a new rom via Windows 8?
chubiprince said:
Ready!
Can I ask for the steps on how to unlock the bootloader, and then installing a new rom via Windows 8?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583801
This procedure should be sufficient for driver setup. I used this but you'll need adb 1.0.31 to communicate with your device.
kcipopnevets said:
http://forum.xda-developers.com/showthread.php?t=1583801
This procedure should be sufficient for driver setup. I used this but you'll need adb 1.0.31 to communicate with your device.
Click to expand...
Click to collapse
Okay got it! Will provide feedback after.
My phone is having an issue where randomly it'll just stop responding. I'll go to turn on the screen or unlock with my fingerprint, nothing happens. Hold the power button down for 1+ minute, nothing happens. Plug into my computer, no recognition on my PC that anything was plugged in. Plug into the charger, no battery light. Is this thing dying?
Finally turned on after holding the power button down. Same as yesterday. Is this a hardware issue or something with the ROM possibly?
agentfazexx said:
Finally turned on after holding the power button down. Same as yesterday. Is this a hardware issue or something with the ROM possibly?
Click to expand...
Click to collapse
Hi... Already seen that scenario a few times with no apparent reason. Last week someone posted hee with the same issue. As you did, holding power button seemed to have solved the problem...
5.1 said:
Hi... Already seen that scenario a few times with no apparent reason. Last week someone posted hee with the same issue. As you did, holding power button seemed to have solved the problem...
Click to expand...
Click to collapse
Right but holding the power button down doesn't really do anything until I let it sit, at least with today's and yesterday's occurrences.
agentfazexx said:
Finally turned on after holding the power button down. Same as yesterday. Is this a hardware issue or something with the ROM possibly?
Click to expand...
Click to collapse
You know there's really only one way to find out....go back to the stock rom for a while. You won't really be losing much, if anything. Nothing wrong with the stock ROM, rooted and kernel- it's rock solid. Between Google's backup/restore and TiBu, you can be back right where you were in an hour or so. You should have your answer within a couple of days. You may also want to install Accubattery to check your battery's capacity vs design.
I don't suppose you are running Franco's kernel or any battery saving apps like Naptime or Greenify?
jhs39 said:
I don't suppose you are running Franco's kernel or any battery saving apps like Naptime or Greenify?
Click to expand...
Click to collapse
Nope. ElementalX kernel and none of that other nonsense. Just sounds like a hardware issue since I'm holding the power button down for several minutes and nothing happens, then eventually the phone hard-reboots.
agentfazexx said:
Right but holding the power button down doesn't really do anything until I let it sit, at least with today's and yesterday's occurrences.
Click to expand...
Click to collapse
Supposing your profile is up to date, I'm running the same setup as you: PN Feb 2017 + EX Kernel 4.05... I've never had such problem...
As @v12xke advised, try loading a stock firmware and see if it happens again...
jhs39 said:
I don't suppose you are running Franco's kernel or any battery saving apps like Naptime or Greenify?
Click to expand...
Click to collapse
Does Franco or other battery saving apps cause device to lock up this way?
5.1 said:
Supposing your profile is up to date, I'm running the same setup as you: PN Feb 2017 + EX Kernel 4.05... I've never had such problem...
As @v12xke advised, try loading a stock firmware and see if it happens again...
Does Franco or other battery saving apps cause device to lock up this way?
Click to expand...
Click to collapse
They can.. Naptime can turn off your fingerprint sensor and make it hard to wake up phone. Greenify img system apps can have unintended consequences. Franco's kernel effects the responsiveness and performance of the phone because it is geared towards battery savings.
agentfazexx said:
Nope. ElementalX kernel and none of that other nonsense. Just sounds like a hardware issue since I'm holding the power button down for several minutes and nothing happens, then eventually the phone hard-reboots.
Click to expand...
Click to collapse
No (new) apps installed/updated lately?
Time to backup... Hoping you'll find an answer to your issue!
jhs39 said:
They can.. Naptime can turn off your fingerprint sensor and make it hard to wake up phone. Greenify img system apps can have unintended consequences. Franco's kernel effects the responsiveness and performance of the phone because it is geared towards battery savings.
Click to expand...
Click to collapse
I see... Thanks.
5.1 said:
No (new) apps installed/updated lately?
Time to backup... Hoping you'll find an answer to your issue!
I see... Thanks.
Click to expand...
Click to collapse
Nope, nothing new.
the same to you. ElementalX,what can i do?
zhxhwyzh14 said:
the same to you. ElementalX,what can i do?
Click to expand...
Click to collapse
What?
agentfazexx said:
What?
Click to expand...
Click to collapse
I think he meant "I have the same problem as you and I'm using EX Kernel". At least that's my translation.
zhxhwyzh14 said:
the same to you. ElementalX,what can i do?
Click to expand...
Click to collapse
EX kernel has nothing to do with your problem. First step is to hold only the power button down for two solid minutes to see if your phone reboots. This situation happens sometimes, but usually the phone reboots while your finger is on the power button. Often it starts and the phone behaves normally again. (Except in OP's case)
I'm having a similar problem after updating to 7.1.2 on the beta program.
Phone wouldn't reboot after installing 7.1.2, it took me a good few hours of pressing power + volume down to get into the stock bootloader/recovery? and started the phone that way. I then opted out of the beta program and reverted back to stock 7.1.1. While at work the phone died and after charging it would not start by pressing the power key, I had to do the whole 3-4 hr process of Power+volume down to get it to boot again. It's up and running now but I fear if it dies I will be in the same boat again with the 3-4 process.
It seems to me that the new update somehow messed with a proper shut down of the phone? It's to bad I really liked this phone up until this problem started.
Chewmasey said:
It seems to me that the new update somehow messed with a proper shut down of the phone?
It's to bad I really liked this phone up until this problem started.
Click to expand...
Click to collapse
Sorry to hear that. For the majority of others the 7.1.2 beta is working just fine, and in fact fixed a long standing BT car connection bug that was rolled out to the 5X and Pixels earlier. Maybe beta testing is not for you, but I haven't been able to connect my phone with my car since last October so I was determined to try it. I used a TWRP flashable version of the image. You may want to wait for the official Google OTA image whenever they get around to posting it... or just wait until it is out of beta.
Hey guys, Does anyone know how to fix the static screen during the boot animagion and once booted permanently? Its very annoying. I've looked around but can't find anything
Im sorry but you really didnt look... it has been said MANY times that using a custom kernel can fix it. either reStock or werewolf will fix it.
me2151 said:
Im sorry but you really didnt look... it has been said MANY times that using a custom kernel can fix it. either reStock or werewolf will fix it.
Click to expand...
Click to collapse
Neither of them work for me. Its still just static. So yes, I have looked around.
I assume you are rooted, what Rom and kernels are you running? If you have a stock based ROM you need a stock base kernel, werewolf has 2 of each. A werewolf 1.0 albatross.zip and ww 2.0 basilisk.zip for custom based rooms. (lineage-aosp rooms) And the same 2 kernels that have "stock" in the title. For stock based ROMS. Check red dragons kernel thread or try the 1.2 restock kernel. Turn off any screen lock b4 installing the zip in twrp?
I have stock rom and stock kernel.
In the settings, i have second screen to stay on and always show time.
As long as the second screen stays on, the static will not go away.
In my case, second screen stays on, so static does not go away.
What kernel do i need and where ?
tonycstech said:
I have stock rom and stock kernel.
In the settings, i have second screen to stay on and always show time.
As long as the second screen stays on, the static will not go away.
In my case, second screen stays on, so static does not go away.
What kernel do i need and where ?
Click to expand...
Click to collapse
They were mentioned above. You can also cover the proximity sensor and let both screens go off, then it should be fine.
bond32 said:
They were mentioned above. You can also cover the proximity sensor and let both screens go off, then it should be fine.
Click to expand...
Click to collapse
Covering the sensor does not turn of the screen. I dont know why.
Screen turn off ONLY during call, when i get it close to my ear but NOT when i cover it with my hand or flip the phone or what ever else you can think of.