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.
Related
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
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:
Dear All,
The case of my phone is quite peculiar because there are several very serious problems, that combine together and make it impossible to use.
> The main problem is the lag. Still after i flashed the CM 13 and i am using the last Boeffla Kernel it lags so bad that i can't use it properly. Sometime to launch an app takes 5/6 seconds. This isn't changed even with different configuration for the Kernel.
The problem connected with the lag is that it takes ages to launch the apps, specially the gapps. It takes ages to launch chrome or maps or gmail. usually after are being launched they work, but apps like chrome are difficult to use on multiple tabs for instance. In general the multitasking is very slow.
>Another problem is that after the screen is locked it it takes at least 3 seconds to to being reactivated, same timing with every phisical button that wake the device up.
>The last problem is that the connection, either 3g or any other, sometimes is present sometimes is not, but it doesn't depend on the area, for instance sometimes works in my room sometimes not.
Is there someone who can help me to find a solution for these problems?
@Volkert Gage:
If everything run fine before CM13, do a clean flash without GCrap and custom kernel - perhaps you fished the wrong GApps.
If there were problems before, go back to firmware to repair.
rp158 said:
@Volkert Gage:
If everything run fine before CM13, do a clean flash without GCrap and custom kernel - perhaps you fished the wrong GApps.
If there were problems before, go back to firmware to repair.
Click to expand...
Click to collapse
thank you for your adivice rp158,
The fact is that these kind of problems (except for the connection) are not new for the phone, i always had it, even with the original firmware.
Before the upgrade to CM 13 i tryed to sort it with the original firmware but nothing worked.
Anyway, can i ask you what gapps pack do you reckon might work better on the phone?
@Volkert Gage: I recommend strongly to flash latest firmware +factory reset. You can't expect any stable LP or MM, if Sammy JB struggles.
@rp158 i'll try to do so then, thank you.
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.
Hello all,
Last week, I broke my oneplus one's screen so I decided to try and revive an old oneplus X.
A month ago, this device was still running the latest available OxygenOS but I played around with the device at the time and decided to install Lineage 14.1. I used the following versions of TWRP and LineageOS:
- LineageOS-14.1 20181110-nightly-onyx-signed (was no longer available on the official LineageOS site)
- TWRP version 3.3.1-0-onyx
After installing LineageOS 14.1, I noticed that there were some glitches when using the phone and the UI would lagg very hard sometimes. Since my Oneplus One was still working fine at the time, I decided to not troubleshoot this any further and put the device away.
Unfortunately, last week I dropped my Oneplus One and broke its screen, so I immediately tried to fix the Oneplus X again. I figured this might have been an issue with the LineageOS 14.1 ROM so I browsed this forum for an android 9 build and found the builds by YumeMichi and by psychem.
First, I booted into TWRP and performed an advanced wipe with every option selected.
Then, I installed Yume's build using the latest version of the ROM and Yume's version of TWRP: "twrp-3.2.3-20190127-onyx".
This booted fine and looked very promising at first, however the glitching/lagging returned after a few hours of use.
Then I cleared everything again and tried psychem's version (11.08.2019 build, without MicroG). I did not change the TWRP version (still using Yume's TWRP). This would not boot but I solved that by flashing Yume's build again and then dirty flashing psychem's build on top of it. That worked fine, untill after a few hours, the lagging and glitching returned.
The past week I've been playing with the power settings and trying to find someone with a similar issue on google. No luck, unfortunately.
The, on 22/08, I noticed psychem released a new build (22.08.2019). I installed that one and at the same time enabled the option "Force use of GPU for 2D rendering" in the developer options. That seemed to do the trick. I was able to use the device for 2 days without any issues, until the glitching happened again yesterday evening.
Today I installed the 23.08.2019 build but that did not solve the issue unfortunately.
To clarify what I mean by glitching/lagging: the phone seems to work fine for 90% of the time. Everything works, the device is performing smoothly and the battely lasts more than a day, awesome.
But sometimes, the screen starts glitching, the interface is extremely laggy and the phone might even randomly reboot. This phone will then be glitchy/laggy andis unusable for an hour. Rebooting does not help, clearing caches does not help, ... The wierd thing is, the same behaviour is also present within the TWRP interface at that moment (so not only once android has booted), as you can see in this video I made. It as also present during the boot phase. But, after a certain amount of time (usually 20-60 minutes), all is fine again and the phone works perfectly.
Is there any change this is not a hardware issue and I might be able to save this phone? The only reason why I think this might not be a hardware issue is because the phone runs fine 90% of the time.
Thanks in advance!
latest build is the 23.08 build.
Try this Nougat RR 5.8.5, works great for me, no lags at all.
https://androidfilehost.com/?fid=6006931924117938132
psychem said:
latest build is the 23.08 build.
Click to expand...
Click to collapse
Thank you. I installed this one, however that did not solve the issue.
I am inclined to believe this might not be related to the ROM at all, since all the LineageOS 14.1 ROM and Yume's ROM also had the same issue and also the issue is present in the TWRP interface and during the boot cycle too.
Is there any driver/firmware/software/... that might be causing this instead of a hardware issue?
My experience with what you are describing leads me to believe one of three things may be causing this. Double tap to sleep on lockscreen enabled, Gboard and Chrome.
Try this, enable software button and disable hardware buttons and see if this resolved your issue. If so ... Toggling software buttons from time to time helps.
AOKP is the only rom this does not happen as well as OOS of course.
BuzzBradA said:
My experience with what you are describing leads me to believe one of three things may be causing this. Double tap to sleep on lockscreen enabled, Gboard and Chrome.
Try this, enable software button and disable hardware buttons and see if this resolved your issue. If so ... Toggling software buttons from time to time helps.
AOKP is the only rom this does not happen as well as OOS of course.
Click to expand...
Click to collapse
Thanks for the suggestions! I do not have Chrome and Gboard installed so that should be fine, but I have disabled the double tap to sleep/double tap to wake option yesterday. Since then I've not experienced any more glitching/lagging. If it returns I will disable the HW buttons and use on-screen buttons and report back.
Unfortunately, none of these options worked. The glitching and lagging is still there and is becoming more frequent.
Any chance I'm missing something?
acidiz said:
Unfortunately, none of these options worked. The glitching and lagging is still there and is becoming more frequent.
Any chance I'm missing something?
Click to expand...
Click to collapse
To put your mind at ease, try OOS and see if it occurs. Then you'll know for sure.
Edit: just saw your video, never seen that before.