Hi everyone
Last night, when i plugged my usb charger to my S3 since it was drained, my phone suddenly turns on without hitting the power button,
I tried turning it off, then plugged again, the Grey battery icon with progress showed but then i was hoping to see the battery icon with green color (the usual icon when it is charging) instead it turned on.
I tried, installing stock rom, Official one, and everything is ok, phone doesnt turn on
Tried clearing cache and dalvik, same turning on happened
Tried installing a fresh ROM, still it turned on after plugged in
Can you help me guys... It doesnt affect my phone, but its quite annoying.
Thanks guys
everyone have same problem with u mate if they use 4.4.2 base room, the issues haven't solve yet :victory:
is a "problem" that every 4.4.x porting have, just use offline mode(with ultra power save or power save if u wanna) and the job is done
franco853 said:
is a "problem" that every 4.4.x porting have, just use offline mode(with ultra power save or power save if u wanna) and the job is done
Click to expand...
Click to collapse
How can i do that?
cgren said:
How can i do that?
Click to expand...
Click to collapse
Simple, expand notification bar, then switch to rapid settings screen, here you find offline/airplane mode(depends on translation), the one with the airplane icon, after you enabled this all networks(cell net. Wifi bt ecc...) will be shut down, you can re enable wifi if u want to surf web , i suggest you to reboot the phone sometime(one every 1 or 2 days).
konohanz said:
everyone have same problem with u mate if they use 4.4.2 base room, the issues haven't solve yet :victory:
Click to expand...
Click to collapse
That is not true. I have never experienced such an issue on any rom I have flashed, I also did a quick search here on xda and cannot find anyone else with this problem.
@cgren
Does this only happen on one specific rom?
Since it does not happen in stock it might be an option in the rom/kernel you have chosen but since you have given no information I cannot check for you.
Darke5tShad0w said:
That is not true. I have never experienced such an issue on any rom I have flashed, I also did a quick search here on xda and cannot find anyone else with this problem.
@cgren
Does this only happen on one specific rom?
Since it does not happen in stock it might be an option in the rom/kernel you have chosen but since you have given no information I cannot check for you.
Click to expand...
Click to collapse
For several days, i have tried number of AOSP and Samsung based custom roms 4.4.X it same thing happens.
But on Official Samsung Roms Everything is ok.
No biggie. As long as it doesnt affect my phone's performance its fine with me. :victory:
Related
Anyone know how to solve this problem?? The phone won't go into standby mode. it just stays at the lock screen
Video on my problem
http://www.youtube.com/watch?v=ej_TzilZITk
Anyone can help please??
no one can help me??
Looks like you are using the CHT lock screen, know issue, buggy, a search would have found it ....
watcher64 said:
Looks like you are using the CHT lock screen, know issue, buggy, a search would have found it ....
Click to expand...
Click to collapse
I made a hard reset, the problem still exist...
shadowblade1990 said:
I made a hard reset, the problem still exist...
Click to expand...
Click to collapse
Well that lock screen in the video is not the stock lock screen, what mod are you using on it ....
Whatever mod you are using, could be the problem ....
shadowblade1990 said:
I made a hard reset, the problem still exist...
Click to expand...
Click to collapse
Are you using CHT lockscreen? Just use the standard one and it should be alright.
nicedude_abad said:
Are you using CHT lockscreen? Just use the standard one and it should be alright.
Click to expand...
Click to collapse
Ditto ...
Not sure how many times this needs to be said ...
But going to join you in saying it again ...
Like i said, i done a hard reset and the problem still exist, which means that the problem does not lies on CHT.
btw i am not using CHT, this video that i posted is just for reference of my problem. (which the phone does not go into standby mode and need activesync in order for it to enter standby mode) the lockscreen that i am using is the orginal HD2 lockscreen.
Same Problem
I'm having the exact same problem with my hd2. I've tried the following things to resolve it:
- Soft reset
- Hard reset
- Task 29 reset
- Formatting my sd card
- Using Artemis and Chuckyrom, both same problems
I'm going to try a stock rom now and look if that works.
Are there more people having this problem? any solutions? Tx!
EDIT: I've installed the stock rom and replaced HSPL with SPL. I'm still having the same problem. I'm going to send it to the manufacturer. Good Luck!
Would you be so kind to come back with the result ? This is a very confusing problem. There are lots of people suffering from this already !
solved
i two have had this problem and have just found out how to sort it out. basically i tried everything new radio, rom, getting rid of CHT
and in the end all it was is the usb connection!!!!
all you have to do when unplugging your usb cable is make it come out on a angle left to right. there are obviously some very delicate contacts that get knocked out of kilter making the phone think its still on mains power when its not hence never turning off
you can confirm this error by unplugging your phone going into backlight settings and seeing if you can adjust you light setting on battery power if when you adjust your light setting nothing happens you got the same prob as me
ive searched for things such as "sleep crash", "sleep bug", "screen wont turn on" etc. but can seem to find anything that tells me anything other than turn off wifi (which i tried to no avail). My issue is that when i press the power button for 1 second to turn off my archos 70 screen it will not turn back on. Same thing happens when i let it fall asleep. If i leave it plugged in and not allow it to turn off screen i have no issues. My apologies if i just don't know what words to search for ... i tried. In on the .4 firmware (latest) with no mods. This has happened through the last 3 firmwares from archos. Any ideas?
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Techngro said:
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Click to expand...
Click to collapse
I will try this and report back. I have been installing firmware over the issue
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
I am try before formatting and report back
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
this worked!!
mallman said:
this worked!!
Click to expand...
Click to collapse
spoke too soon. did not work. it stopped after a few tries
it works again if i recalibrate but wont hold.
Zoidpilot said:
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
Click to expand...
Click to collapse
by the way, the deep sleep option also kills mine.
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
ramso said:
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
Click to expand...
Click to collapse
just tried it . i hit the icon to disable sleeping. i pressed the screen button and when i went to turn screen back on it would not wake. Did i use the app wrong?
No, you use the app rigth. The app only disable deepsleep.
Sent from my A101IT using Tapatalk
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
bbop said:
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
Click to expand...
Click to collapse
err I'm afraid that I spoke too soo. My device keeps getting stuck and won't awake from sleep. This seems to happen most after switching wifi on or off, specifically whilst the device is playing music.
Zoidpilot said:
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
Click to expand...
Click to collapse
how are you installing the firmware? maybe im doing it wrong. I let the device update to latest 2.1.4 and then i wiped it via the settings and repair menu in android.
Edit**
like this??:
Step 1: Download the android 2.2 firmware for your archos tablet from here,you might a get a false positive notification from your browser as they are unaware of .AOS format, so ignore that and download it.
Step 2:Go to Menu > Settings > Device Storage & USB connection > USB connection mode of your tablet and set the connection mode to Mobile Media Device (MTP) and now connect your Tablet to pc.
Step 3:Now when the tablet is detected you will see a hard drive icon,double tap and open it and copy and paste the firmware (.AOS) file into the hard drive(make sure you dont copy it in any folder inside it like Music,Videos etc).
Unplug the USB connection and the Archos device will automatically locate the update file and will prompt you for the update,just follow the screen options and you are done,if it does not prompt you for an update then you might have accidentally misplaced the file in one of the folders,just locate the .AOS file from the file manager and and open it to start the update.
No no it wasn't that complicated... It was actually the simplest fix for a difficult problem. My device when I got it was running 2.1.2 out the box... Even then It had the screen problem. When I got the chance I installed 2.1.3 OVER THE AIR. Straight from Archos. Still had the issue though, I figured it would have been fixed but was greatly disappointed... Then I sort of just lived with the problem for awhile... I saw that the 2.1.4 update was released but was wary about downloading it because sooo many people are having issues. Just the other day though, the device cut off on me again and I figured to hell with it... So I downloaded the 2.1.4 OTA as well... no website, no manual install, I just let the device run its course on its own. After the update, it rebooted normally and it's been working great since... Sorry to hear not everyone is so fortunate... I really hope this helps somewhat
Hi everyone...
Some days ago, i was trying, OmniROM (http://forum.xda-developers.com/showthread.php?t=2544790). I follow all the steps and even get the superSU app going. One night, y saw how my nightly got updated, and in the morning, start to reboot randomly. If I push the power botton sometimes, doesn´t appear the blockscreen but the screen with the reboot option and turn off appear...
I put my cellphone back to stock with root using SuperOneClick from here: http://forum.xda-developers.com/showthread.php?t=1311081. Then, I format my sd card and internal storage...The problem persist...
I would like that someone help me, I'm tryin everything and didn't solve it...
Based on your description, it sounds like a hardware issue -more specifically, a failing power button.
I have read that some users were able to fix the issue by disassembling the phone and spraying out the switch with contact cleaner, and I have read that others had the power switch replaced altogether.
Hopefully others will chime-in with their thoughts.
Leo Dorado said:
Hi everyone...
Some days ago, i was trying, OmniROM (http://forum.xda-developers.com/showthread.php?t=2544790). I follow all the steps and even get the superSU app going. One night, y saw how my nightly got updated, and in the morning, start to reboot randomly. If I push the power botton sometimes, doesn´t appear the blockscreen but the screen with the reboot option and turn off appear...
I put my cellphone back to stock with root using SuperOneClick from here: http://forum.xda-developers.com/showthread.php?t=1311081. Then, I format my sd card and internal storage...The problem persist...
I would like that someone help me, I'm tryin everything and didn't solve it...
Click to expand...
Click to collapse
cyril279 said:
Based on your description, it sounds like a hardware issue -more specifically, a failing power button.
I have read that some users were able to fix the issue by disassembling the phone and spraying out the switch with contact cleaner, and I have read that others had the power switch replaced altogether.
Hopefully others will chime-in with their thoughts.
Click to expand...
Click to collapse
Well, i will try that. It's a shame that such a good cellphone have that problem... I really love it... Thanks for your answer.
Leo Dorado said:
Well, i will try that. It's a shame that such a good cellphone have that problem... I really love it... Thanks for your answer.
Click to expand...
Click to collapse
I had to replace my power button. this is a known issue with the s2.
I recommend this guy's services: http://stores.ebay.com/t989-refurb -- he can do the i777 even though it's not listed. He's a very nice guy and will do a fine job.
here's his video demonstration: http://www.youtube.com/watch?v=F0xMMn1DRWs
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
If this happens on a stock rom, it is probably a hardware issue.
audit13 said:
If this happens on a stock rom, it is probably a hardware issue.
Click to expand...
Click to collapse
Thank you for your reply, but this does not happen on the stock rom.
It's definitely good that this doesn't happen in stock.
Sounds like a incompatibility between the phone and rom. Have you tried earlier or later versions of lineage?
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
I can also confirm this on the latest lineageos nightly update to date. It's as if phone is on standby/sleep and no way to wake it up without rebooting the phone by holding down the power button until phone restarts. I don't need to go into recovery like OP. Anyone else?
Are we the only ones experiencing this issue? Any help would be appreciated.
Gizmotech said:
Are we the only ones experiencing this issue? Any help would be appreciated.
Click to expand...
Click to collapse
You got a reply in the other thread where you posted about it:
minealex2244 said:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.
Thank you @Gizmotech for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
Click to expand...
Click to collapse
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Providing the last_kmsg will help Simon to find a solution. If you only complain about this issue then it won't be solved. Next time make sure to include last_kmsg.
---------- Post added at 19:49 ---------- Previous post was at 19:45 ----------
shivadow said:
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
Click to expand...
Click to collapse
Really? Do you know what beta means? I'm sure that you don't. Beta means that it is not really stable (80% or less of the things are working) while stable means that 95% of the things are working. This explains why LOS 14.1 for S6 was considered stable: because everything was working. Also that issues are already listed in the forums.
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. st the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Same problem with last lineage version. Are you found solution ?
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
cRaZy-bisCuiT said:
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
Click to expand...
Click to collapse
The problem is the rom or kernel. It happens to all custom roms and kernels on the s3. No-one has found the source of the problem.
Everything custom is beta even if it is considered stable. Beta means "not final". Unless you see a rom with "final" on it then you'll encounter issues at some point.
The only truly final product if you want root is stock rom rooted. If you flash a kernel you'll get the same problem.
When my phone locks by being idle or just because I press the power botton I can't get it back unless I tap volume- and power key. This happens to me in three different ROMs by different developers. It happens on Lineage OS, AEX Aosp extended and Crdroid and the weird thing is that this happened since April 9, before that i could use those ROMs without any problem, it doesn't happens when I use a Samsung based ROM. Why not use one that's alredy working? because it makes the phone very slow, lets faced this phone without a Aosp rom is not worth using. I have clean flashed every ROM and even not restored my data and as soon as I lock the phone it's the same.
I am having the same problem here have you solved it?
1n1t3_1 said:
When my phone locks by being idle or just because I press the power botton I can't get it back unless I tap volume- and power key. This happens to me in three different ROMs by different developers. It happens on Lineage OS, AEX Aosp extended and Crdroid and the weird thing is that this happened since April 9, before that i could use those ROMs without any problem, it doesn't happens when I use a Samsung based ROM. Why not use one that's alredy working? because it makes the phone very slow, lets faced this phone without a Aosp rom is not worth using. I have clean flashed every ROM and even not restored my data and as soon as I lock the phone it's the same.
Click to expand...
Click to collapse
Bryfkogel said:
I am having the same problem here have you solve it?
Click to expand...
Click to collapse
Bryfkogel said:
I am having the same problem here have you solved it?
Click to expand...
Click to collapse
Not yet, its the same with all that ROMs as I explained and it looks like the thread is no longer active.