yesterday, my tab s 10.5 has stopped working. The last thing i did was setting a profile that changes the cpu governer from ondemand to userspace and reduces the max frequency of the proccessor 1 Ghz when the screen turns off (using SetCPU) . I turned off the screen, when i pressed the power button, it would not turn on, neither will the buttons light up. I am not sure that this action is the one to blame for this situation, since i think (not sure) that i tried it once before without causing such issue
Till now, the device won't turn on no matter how many time i press any button or for how long. The only evidence that it is alive that my router still sees its ip and mac address, however it won't recognise it as android device as it does with my phone.(check attachments)
Worth mentioning: My device has root (CF-auto root by ChainFire), exynos variant, has stock rom, kernel, and recovery, and still within warranty period.
Is this situation a black screen of death?
What can i do to solve this issue? I do have some experience with odin (flashing recovery, roms, and root)(Not with this device, this device only had root using odin)
Is changing the cpu governer the cause of this black screen?
Should i still give it to customer service even though i might have voided the warranty, or do they have no way of knowing now that the device is unresponsive?
I am in the proccess of draining the battery by taping the power button using clear tape.
Thanks for reading, and would really appreciate any help.
Userspace is probably the worst governor of all governors, so why you decided to use it I don't know.
To remedy the situation hold POWER + VOL DOWN until the tablet restarts.
ashyx said:
Userspace is probably the worst governor of all governors, so why you decided to use it I don't know.
To remedy the situation hold POWER + VOL DOWN until the tablet restarts.
Click to expand...
Click to collapse
Thank you so much, my device is now working well.
Related
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
macfan74318 said:
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
Click to expand...
Click to collapse
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
sino8r said:
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
Click to expand...
Click to collapse
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
seancneal said:
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
Click to expand...
Click to collapse
Still happens to me when I try that. It occurs when you press the power button twice in succession.
Hi there,
anything new on this topic? I'm currently experiencing this annoying problem as described.
I've already tried to set the minimum clock to 368 Mhz but the bug still exists. Even setting CPU to standard clock (Max/Min @800) didn't solve the problem.
Is it possible that the reason is located already inside the overclocking kernel?
Greets
dktnecro
Generally if you're overclocking and you have lockscreen issues that are not present @ stock speeds, then it sounds to me like the overclock is too much and your system probably isn't stable.
Based on my experience overclocking computers, things can very well appear stable but if you do stress testing (8+ hours straight) things often crop up and show you that it is in fact not stable. This sounds like one of those things. And that's not good. Who knows what other corruption could occur during your use at that speed? I had the same lockscreen issues myself, and once I realized it was due to overclocking too much I ended up solving another issue I had where half of the calls I received were garbled to the person on the other end. No more lockscreen issues or garbled calls since backing off the o/c a bit.
If the issue doesn't happen at stock speeds then maybe it's just the kernel, and hopefully that isn't putting you at risk of any kind of corruption, either.
Keep in mind I really can't be 100% if overclocking will cause corruption on a phone, but based on a lot of time spend overclocking pc's I would have to guess that it can. I'm surprised that this isn't brought up more often on device forums.
Having response issues with power button. It works just have to hit it two three or four times to wake screen. Suggestions?
It's just slightly worn out from all the use, like any button would be. You could open up the phone and mess around with it. Or maybe try taking it back to verizon and seeing if they will give you a refurb.
try switching kernels, some kernels take longer to respond than others.
Thanks, I will try flashing another kernel. If that does not work I'm still under warranty and will get a refurb.
Sent from my ADR6300 using XDA App
Download CM7 and use any-key wake
Widget Locker also has this feature. I only hit the power button to reboot/power off my phone.
where in settings is any-key wake
Not sure if you are setting your cpu speeds or not....
Make sure you dont set your cpu too low. if you are using set cpu or something make sure its set to 388 ish when the screen is off. Ive seen alot of issue when you get down into the lower ranges. cpu uses alot less battery then the screen anyway.
Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.
I've got the E4GT. My phone will no longer turn on, show any sort of notification light, no sounds are made, etc. I'm pretty sure it was caused by underclocking the CPU to 800mHz but I've done this in the past with no issues. I set it with RomToolkit (and have had success going from 500mHz - 1600mHz) with the PowerSave on 500mHz min -> 800mHz max. I had my phone reboot to save the changes, and now it doesn't even seem like it's attempting to turn on. It is fully charged (at least 90% when I had it reboot).
I've just got this phone recently (so exchanging it might be an option). I'm running the LoStKernel 1.0.0.8 experimental kernel with StarBurst 1.9.8r and the ICS animations mod.
A mate of mine suggested using a jig but I don't think it will do much as the phone won't even boot to download mode.
Thanks
--
FIXED:
I took out the battery, held the power button for 10 seconds, put the battery back in and turned it on like normal. Mentioning so someone else can find it quick in the search.
I have heard that if u completely drain the battery to nothing, remove the SD card and plug it in and turn it on that it boots
Sent from my SPH-D710 using xda premium
I posted in the Q&A forum asking for people to see if there CPU Power saving part of the Power Saving mode was working correctly, because mine would limit the CPU top speed to 1.35 GHz as it should, but only for a few minutes, then go right back to 1.9GHz. No one responded, so thinking I must have a problem with my phone, I exchanged it last night for a new one. And guess what? This one does it too. So it appears a major part of saving battery by using Power Saving Mode is broken with all T-Mobile units at least, if not all of them. I called both T-Mobile and Samsung before returning it and both said they never heard of the problem before.
For comparisons sake, my wifes Note 2 in PSM locks in at 1.1 GHz and doesnt budge from there.
if you check the box in power saving mode it will lock in cpu at 1.2 (never seen it do 1.3) from what I saw, hence, power saving, so un-check it, you should get 1.8, another item that effects the cpu speed is kernels, have you tried another?
BTW, nice ride you have. sweet
TheAxman said:
if you check the box in power saving mode it will lock in cpu at 1.2 (never seen it do 1.3) from what I saw, hence, power saving, so un-check it, you should get 1.8, another item that effects the cpu speed is kernels, have you tried another?
Click to expand...
Click to collapse
Nope, checked should lock it up to 1.35, which it does, but leave it for a while and then check it, the phone will over ride it and scale back to 1.9 on its own.