Hi.
I'm on my 2nd S3 now. First one suffered from the "sudden death syndrome".
My 2nd S3 has been perfectly fine bar the odd lock up. It's rooted and flashed with Supernexus by Faryab on v4.2.2
It has been freezing a lot lately, maybe 3 or 4 times a day but over the past few hours, it's now locked up approximately 20-30 times and I have to keep the power button pressed to reboot it. I've uninstalled any apps I have installed over the past few days. Booted into recovery and cleared cache and davlik cache (it's now saying Android is Upgrading upon every reboot). I can't even get time to backup my apps using Titanium Backup without it crashing.
What is going on anybody? Any help is much appreciated.
Try having a read of the freezing thread over in general.
boomboomer said:
Try having a read of the freezing thread over in general.
Click to expand...
Click to collapse
Thanks. It appears my full microSD card was causing the problem. Cleared a few movies off it last night and it's not crashed since. Fingers crossed!
5aq1b said:
Thanks. It appears my full microSD card was causing the problem. Cleared a few movies off it last night and it's not crashed since. Fingers crossed!
Click to expand...
Click to collapse
I guess i spoke too soon. More crashes again today
Did you do a full wipe including system format before installing the ROM? . It may be a data problem. Don't forget that 4.2.2 is also a beta firmware mate and not official like 4.1.2 so these things can happen. Also there are no custom kernels to flash to try and see if it's kernel based either.
cooza said:
Did you do a full wipe including system format before installing the ROM? . It may be a data problem. Don't forget that 4.2.2 is also a beta firmware mate and not official like 4.1.2 so these things can happen. Also there are no custom kernels to flash to try and see if it's kernel based either.
Click to expand...
Click to collapse
Hey, yeah I did a full wipe including system format before I installed the new ROM. I've had this ROM for probably 3 months now and haven't had any problems with it up until the last few weeks. Infact 4.1.2 was killing my battery in a matter of hours. 4.2.2 ROM made me love my phone again as it fixed my battery woes!
This is so frustrating...
4.2.2 being a beta version can do this but re-installing can sometimes cure it though. Changing the kernel in 4.1.2 can give you better battery if you play around with a few and if course is more stable being an official release too. You can also try a different 4.2.2 ROM. They aren't all the same.
Thanks for the reply. Im not too comfortable/confident in changing kernels due to my lack of knowledge on them!
I do however like Faryabs ROMS as I like the original Android flavoured ROMS.
Will try a reinstall!
Same Problem
5aq1b said:
Thanks for the reply. Im not too comfortable/confident in changing kernels due to my lack of knowledge on them!
I do however like Faryabs ROMS as I like the original Android flavoured ROMS.
Will try a reinstall!
Click to expand...
Click to collapse
I have the exact same issue, I was running Faryaabs rom version M1, Android 4.2.2. And a couple of days ago, I noticed it started freezing, and I have to reboot with power button. Now I installed the leaked Touchwiz 4.2.2. but the freezing remains and it has started to be worse. As you mention, 20-30 times a day. I have noticed though, when I shutt of internet, both wifi and 3/4G I get less crashes. Have you noticed the same?
If you find a solution, please inform me to.
Cheers,
Niko
Niko_v said:
I have the exact same issue, I was running Faryaabs rom version M1, Android 4.2.2. And a couple of days ago, I noticed it started freezing, and I have to reboot with power button. Now I installed the leaked Touchwiz 4.2.2. but the freezing remains and it has started to be worse. As you mention, 20-30 times a day. I have noticed though, when I shutt of internet, both wifi and 3/4G I get less crashes. Have you noticed the same?
If you find a solution, please inform me to.
Cheers,
Niko
Click to expand...
Click to collapse
I think you may have found it
Wifi for example is controled by the kernel but there is no source codes released by Samsung so thats why there are no custom 4.2.2 kernels available for the S3 or you could flash one and most likely sort the problem out.
Its a shame cos there are for other phones on this version.
Hi dude
I went to the freezing thread here and found that the DFG method solved it all. So for anyone willing to try this please head over to that thread or just download the dummy file generator apps (2 in app store) although one is only necessary.
Gl and ty for the reaponse
Xda 4life
Sent from my GT-I9300 using xda app-developers app
Related
Ok I hate starting a new thread but I have a problem that I can not seem to find any information on it,
I have had my S2 for 1.5 years and have run many many custom roms. Been using Paranoid lately. Today I tried flashing the newest Wanam Lite as my second rom keeping Paranoid as primary. (using dorimanx kernel)
Wanam failed to install. After boot the screen goes black. No problem... I will just go back to my Primary rom. Tried, Tested and True, Paranoid Android.
What's this? My phone is asking for SIM unlock code. I unlocked this phone 1 and a half years ago. Ok so I unlock it the same way i had done in the past for my S2 and many friends S2. I installed "Galaxy S Unlock" from the market and ran it. Ok phone is unlocked and I can use it like normal, as I have network signal.
But as soon as I reboot it is locked again. So now I have to unlock the SIM every time I reboot my phone.
Does anyone know why this is happening?
This is what I have tried so far.
- reinstalled ROM
- wiped dalvic
- wiped data
- wiped cache
- fixed permissions
Nothing I try solves the problem. Every time I reboot I lose my sim unlock.
Any help is appreciated.
Thanks.
anyone have any insight into this??
has this happened to anyone else?
kevjef420 said:
Ok I hate starting a new thread but I have a problem that I can not seem to find any information on it,
I have had my S2 for 1.5 years and have run many many custom roms. Been using Paranoid lately. Today I tried flashing the newest Wanam Lite as my second rom keeping Paranoid as primary. (using dorimanx kernel)
Wanam failed to install. After boot the screen goes black. No problem... I will just go back to my Primary rom. Tried, Tested and True, Paranoid Android.
What's this? My phone is asking for SIM unlock code. I unlocked this phone 1 and a half years ago. Ok so I unlock it the same way i had done in the past for my S2 and many friends S2. I installed "Galaxy S Unlock" from the market and ran it. Ok phone is unlocked and I can use it like normal, as I have network signal.
But as soon as I reboot it is locked again. So now I have to unlock the SIM every time I reboot my phone.
Does anyone know why this is happening?
This is what I have tried so far.
- reinstalled ROM
- wiped dalvic
- wiped data
- wiped cache
- fixed permissions
Nothing I try solves the problem. Every time I reboot I lose my sim unlock.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
First of all , use the following to unlock your phone, if it works for you that would be gud otherwise flash the rom again (Fresh Install)
https://dl.dropbox.com/u/21618136/GalaxSimUnlock.apk
You cannot dual boot Leaked JB based roms as of yet ..
Exatley same things happend with me at this afternoon. My sgs 2 was unlocked nearly a year ago, and I'v been tryed a new "leaked - out" rom which I've found on the Sammobile forum. I9100XXLSJ - Offical, beta... or alpha.. dunno, but 4.1.2
Few minutes later I also tried an another rom... http://forum.xda-developers.com/showthread.php?t=2037363 XXLSJ tweeked by Alliance.
I've wiped everything before every install, and I'm not sure where I've lost my "unlocked" status... Lol.. First time I was thinking its a PIN code only. Obviously I never seen this before. In the last few year I installed, and tried many roms without any issue. Mostly Darky's, CM 7-9.
But long story short: your tool solved my problem under a minute. Thank you so much MR.Killer
Ps: maybe I also tried a CM10 nighty build today.. I cant bear in my mind everything
jstonehun said:
Exatley same things happend with me at this afternoon. My sgs 2 was unlocked nearly a year ago, and I'v been tryed a new "leaked - out" rom which I've found on the Sammobile forum. I9100XXLSJ - Offical, beta... or alpha.. dunno, but 4.1.2
Few minutes later I also tried an another rom... http://forum.xda-developers.com/showthread.php?t=2037363 XXLSJ tweeked by Alliance.
I've wiped everything before every install, and I'm not sure where I've lost my "unlocked" status... Lol.. First time I was thinking its a PIN code only. Obviously I never seen this before. In the last few year I installed, and tried many roms without any issue. Mostly Darky's, CM 7-9.
But long story short: your tool solved my problem under a minute. Thank you so much MR.Killer
Ps: maybe I also tried a CM10 nighty build today.. I cant bear in my mind everything
Click to expand...
Click to collapse
Glad i helped and you never clicked the thanks button
Please CLICK THANKS IF I HELP
Mr.KiLLeR said:
First of all , use the following to unlock your phone, if it works for you that would be gud otherwise flash the rom again (Fresh Install)
https://dl.dropbox.com/u/21618136/GalaxSimUnlock.apk
You cannot dual boot Leaked JB based roms as of yet ..
Click to expand...
Click to collapse
THANK YOU VERY MUCH. This app solved my problem with the sim unlock. Saw it on the market but it wanted me to pay
I didn't know that the leaked JB could not be dual booted. That would explain the black screen. I think I will back up my primary to SD and try installing that rom again. Does this work on any kernel or just the one it is supplied with?
Anyways. Thanks again. You solved my BIG problem.
kevjef420 said:
THANK YOU VERY MUCH. This app solved my problem with the sim unlock. Saw it on the market but it wanted me to pay
I didn't know that the leaked JB could not be dual booted. That would explain the black screen. I think I will back up my primary to SD and try installing that rom again. Does this work on any kernel or just the one it is supplied with?
Anyways. Thanks again. You solved my BIG problem.
Click to expand...
Click to collapse
only 'Philz' kernel does support the leaked Jb rom or one based on it for know
The app is free to use if you get it from Spockys thread.
I believe you have to pay if you get it through play store.
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
abc.mikey said:
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
Click to expand...
Click to collapse
You mean freezes and/or fc's? You actually have to ask in the RR-thread, but I understand you only have posted 8 posts for now.
Remember RR 3.1.3 is still very new and under development, and isn't as stable as 3.1.2 is. If you want more stability, flash the 3.1.2-version.
And did you flash it with a full wipe? It's a must.
Sent from the Matrix
abc.mikey said:
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
Click to expand...
Click to collapse
The normal procedure would be to first read through the posts on the roms dev thread and see if others have had same issue and what (if any) solution is. if you dont see any comments then make one of your own explaining issue (You wont be able to do this until you have 10 posts).
Before leaving any replies on topic you should try doing a wipe/factory reset in recovery then boot to system see if you have same issues. Its advised to wipe recovery before each rom flash (Unless you have stock kernel, If you have stock rom/kernel you need to flash custom kernel before wiping. You can mostly ignore wiping if you are updating to new version of same rom however its still advised as somtimes can lead to issues.
You dont need to worry about apps/appdata and sms etc as you can easily backup them with Titanimum Backup Pro and SMS Backup etc. Get pro version of TB as you can batch backup/restore app/appdata in one go.
Donnie Sins said:
You mean freezes and/or fc's? You actually have to ask in the RR-thread, but I understand you only have posted 8 posts for now.
Remember RR 3.1.3 is still very new and under development, and isn't as stable as 3.1.2 is. If you want more stability, flash the 3.1.2-version.
And did you flash it with a full wipe? It's a must.
Sent from the Matrix
Click to expand...
Click to collapse
Thanks for the replies!
It freezes as in apps start becoming more and more unresponsive, sound if playing starts to stutter more and more until it ceases playing at all and phone us completely unresponsive except to a long hold if the power button. Sorry but I don't know what FC is.
I upgraded because the notifier informed me that there was a new ROM; I see now that it's a good idea to wait a bit now. I've downgraded to 3.1.2 which I've been very impressed with the responsiveness and stability of.
My first attempt at installing 3.1.3 was an attempt at an upgrade but didn't work very well as I think I followed the wrong procedure. But the issues I was having were with a wipe and reinstall following all the steps in the manual plus an undocumented one to install the keyboard patch for the S2 to make the keyboard work at all.
TheATHEiST ok will try reporting there next time, hopefully my post count will allow it by that time
TheATHEiST said:
The normal procedure would be to first read through the posts on the roms dev thread and see if others have had same issue and what (if any) solution is. if you dont see any comments then make one of your own explaining issue (You wont be able to do this until you have 10 posts).
Before leaving any replies on topic you should try doing a wipe/factory reset in recovery then boot to system see if you have same issues. Its advised to wipe recovery before each rom flash (Unless you have stock kernel, If you have stock rom/kernel you need to flash custom kernel before wiping. You can mostly ignore wiping if you are updating to new version of same rom however its still advised as somtimes can lead to issues.
You dont need to worry about apps/appdata and sms etc as you can easily backup them with Titanimum Backup Pro and SMS Backup etc. Get pro version of TB as you can batch backup/restore app/appdata in one go.
Click to expand...
Click to collapse
I can confirm that I have followed all the procedures (flashed at least 20 differet roms by now) and can also confirm that I have been facing a laggard and slow responsiveness throught out the rom, with couple of FCs and lockups as well. At least thrice I had to force reboot. Also I have done an extensive search and the only thread I could see on the similar issue was this.
I am posting here because of same reason as OP as I have a low post count but I have been following xda for over 2 years now.
I know the obvious answer is to downgrade to 3.1.2 or not install RR at all. This is "just reporting", you know!
Thanks!
Hey, I am also experiencing the same thing as the OP and 7mojo. My S2 would randomly freeze and the only way to get it working is a hard reboot. It happens randomly but quite often, I would say atleast 3 times a day. I have done a full wipe and re-install but no luck. Like 7mojo said, I too have searched the web and the only thing relating to this issue is this thread. Anyone else having this problem? any solutions? I hope there is an update soon.
Nevethen5 said:
Hey, I am also experiencing the same thing as the OP and 7mojo. My S2 would randomly freeze and the only way to get it working is a hard reboot. It happens randomly but quite often, I would say atleast 3 times a day. I have done a full wipe and re-install but no luck. Like 7mojo said, I too have searched the web and the only thing relating to this issue is this thread. Anyone else having this problem? any solutions? I hope there is an update soon.
Click to expand...
Click to collapse
I've had similar problems.. am guessing its due to bugs in the unstable rom. Will have to wait for the dev to release an update. For the time being, better stick with 3.1.2.
As for me, I switched to JellyBAM. And then to CM10.1. And then to Omega.
"To err is human, to forgive is divine"
Sent from my SGS II
I have flashed over 10 roms each time I do a NUKE and wipe all caches and data. I have installed roms as per instructions. But for the life of me I can not find one that will go an hour without rebooting or freezing. I have tried many different kernels as well.
Does anyone else have this problem?
Do your phones reboot all the time?
Am I doing something wrong?
Is there something wrong with just my phone?
Is this normal?
Someone advise a stable version. I just don't get it......
Maybe a battery issue.
I really don't understand it. It reboots when I'm sending a text or searching internet or swiping screens. It doesn't matter what i am doing at the time.
The most stable one I have found to work the longest without reboot is Omega Milestones with 7.13 dormaix kernel. Thats it. But I still have problem.
Please help
It could be the battery dying on you.
If it's not the battery then we could be talking hardware.
Sent from the little guy
casualt said:
I have flashed over 10 roms each time I do a NUKE and wipe all caches and data. I have installed roms as per instructions. But for the life of me I can not find one that will go an hour without rebooting or freezing. I have tried many different kernels as well.
Does anyone else have this problem?
Do your phones reboot all the time?
Am I doing something wrong?
Is there something wrong with just my phone?
Is this normal?
Someone advise a stable version. I just don't get it......
Maybe a battery issue.
I really don't understand it. It reboots when I'm sending a text or searching internet or swiping screens. It doesn't matter what i am doing at the time.
The most stable one I have found to work the longest without reboot is Omega Milestones with 7.13 dormaix kernel. Thats it. But I still have problem.
Please help
Click to expand...
Click to collapse
Have you tried going back to an official stock firmware?
Sent from my SGS II
Hello all, I am having some issues with 4.3 roms that I hope someone is able to help with.
I first noticed the problems after flashing PA 4.3, and after doing the usual restoration of my apps, I found that some of them now stutter very badly, the key apps that come to mind are Feedly, Dolphin browser, Opera, and the stock browser.
I searched the thread for users suffering from the same problems, but none seemed to have it. Therefore I took it as my own fault and tried to reflash the rom again. When flashing a rom, I always do the following: Full wipe, with system, preload, data all formatted. This I do via Philz recovery.
I then restored all my apps as usual via titanium backup, and still found the problem to exist. I took it as perhaps bad luck of mine, that my phone just would not play nice with PA 4.3. I then tried other 4.3 roms, PACman and liquidsmooth, but again the problems occurred.
This time, I eliminated my backups as a possible culprit by only downloading the affected apps via playstore immediately after a fresh install (after the entire wifi, google setup) and nothing else. However, these apps are still affected by the stuttering problem.
Flashing to 4.2.2 roms do not present this issue at all.
Therefore i searched for possible incompatibilities of the apps with 4.3, but was not able to find anything. Seeing as no other users of the roms are having the same problems as me, I can only concur that it may be something I am doing wrong, so I am hoping if anyone can help shed some light on this situation I am in, thank you.
Summary:
- Several apps stuttering on 4.3
- Full wipe fresh install with no other apps installed does not fix problem
- Issue is not present on 4.2.2
- Multiple 4.3 roms tested
Info:
Liquidsmooth JB - v2.9
Googy Max kernel 1.7.5
Philz recovery 5.11.2
If more info is required, I would be happy to provide.
did your notification drawer stuttering to? Mine drawer did that but After 2 days in usage with Custom Kernel all Run very smooth maybi you should try that to
Gesendet von meinem GT-I9300 mit Tapatalk
CroW_D said:
did your notification drawer stuttering to? Mine drawer did that but After 2 days in usage with Custom Kernel all Run very smooth maybi you should try that to
Click to expand...
Click to collapse
I did not notice my notifications drawer stutter, however i mostly run in expanded desktop mode with PIE and halo so i do not use the notifications much. I was always on googy kernel for my roms, and tried using the phone, but gave up after 1 day because the experience was terrible with stutters and all. I also tried a cache wipe and dalvik wipe but to no avail.
elencross said:
I did not notice my notifications drawer stutter, however i mostly run in expanded desktop mode with PIE and halo so i do not use the notifications much. I was always on googy kernel for my roms, and tried using the phone, but gave up after 1 day because the experience was terrible with stutters and all. I also tried a cache wipe and dalvik wipe but to no avail.
Click to expand...
Click to collapse
the above is strange indeed. I am running SlimBean 4.3 since the first beta and never experienced stutters (also with TB restores).
You could try to setup your phone from scratch with MegaWipe (it will wipe anything clean, only leaves your external SD intact), whereas I would be surprised if this will help. Otherwise did you try another kernel (e.g. Yank's)?
chrismast said:
the above is strange indeed. I am running SlimBean 4.3 since the first beta and never experienced stutters (also with TB restores).
You could try to setup your phone from scratch with MegaWipe (it will wipe anything clean, only leaves your external SD intact), whereas I would be surprised if this will help. Otherwise did you try another kernel (e.g. Yank's)?
Click to expand...
Click to collapse
Aye, hoping to exhaust every possible means before such a drastic "nuke" is attempted. I used yank before googy, but to eliminate all possible causes, i have only installed the apps that are affected on a clean fresh rom with no modifications or other apps installed. Since its impossible for 3 clean roms to be having the problem, its either me or my phone.
Oh and on an extra note, my phone has died from SDS twice, both times i have sent it back for repair. After the second time, i believe they updated my bootloader iirc, so it now has the red "!" sign after a software flash. Using the emmc checker app, it is also no longer the sds affected version.
elencross said:
Aye, hoping to exhaust every possible means before such a drastic "nuke" is attempted. I used yank before googy, but to eliminate all possible causes, i have only installed the apps that are affected on a clean fresh rom with no modifications or other apps installed. Since its impossible for 3 clean roms to be having the problem, its either me or my phone.
Oh and on an extra note, my phone has died from SDS twice, both times i have sent it back for repair. After the second time, i believe they updated my bootloader iirc, so it now has the red "!" sign after a software flash. Using the emmc checker app, it is also no longer the sds affected version.
Click to expand...
Click to collapse
I guess you are correct considering that:
(1) your procedure of flashing a rom is following the guides
(2) you tried different ROMs
(3) you tried different kernels
knowing that you had SDS problems, maybe it was not resolved 100%? I had, for quite some time, also occasional freezes and lags and the procedure here helped me to solve them, maybe also worth a try?
chrismast said:
I guess you are correct considering that:
(1) your procedure of flashing a rom is following the guides
(2) you tried different ROMs
(3) you tried different kernels
knowing that you had SDS problems, maybe it was not resolved 100%? I had, for quite some time, also occasional freezes and lags and the procedure here helped me to solve them, maybe also worth a try?
Click to expand...
Click to collapse
Thank you, I will try that out later. I AM having some bootloop issues but that is on 4.2.2, no freezes though, but the DFG seems like it wouldnt hurt to try.
elencross said:
Thank you, I will try that out later. I AM having some bootloop issues but that is on 4.2.2, no freezes though, but the DFG seems like it wouldnt hurt to try.
Click to expand...
Click to collapse
Well I tested the DFG out, now back on 4.3 but issues still present sadly. One thing i did notice about my browsers though, is that it only starts to stutter when running 2 or more tabs. On one tab alone, it is smooth. Most of the other apps are also functioning smoothly. I guess I will stick with the setup for now and use replacement apps for the affected ones.
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org