[Q] i9300 getting random freeze/hang up irrespective of recover/kernel/rom - Galaxy S III Q&A, Help & Troubleshooting

This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.

newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.

Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).

One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.

newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.

Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.

pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?

Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .

JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?

If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.

~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.

by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda

Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?

Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button

Related

[Q] Galaxy Player 4.0 (Int) bootloop

Hi there
So i tried to install Steve's Kernel, but my device is in Boot loop now... (my device is international, it has Physical home button....)
i did some search around and found this : http://forum.xda-developers.com/showthread.php?t=1531850
but i am not sure if this is the solution to my problem...
i can go to recovery mode and download mode by the way
so i am gonna assume i am not completely ruined....
Any ideas guys?
porkho biv9
after my first flash I was in the same situation as you. flashing the stock rom was the only solution.
But in my case it was no problem, because I had nothing important on the device. It was almost fresh out the box.
I've the experience, that doing a full wipe causes a higher possibility of getting bootloops. So I only clear the dalvik cache after flashing roms/kernels. If it boots -->everything is fine.
Do you have a backup? CWM or titanium backup?
Hi
Unfortunately i don't have any of those....
do you think that link i gave in the 1st post can be useful?
Thanks in advance....
Yes, I downloaded the .pit and .tar.md5 file and did everthing of these steps:
Flashing Time
1.3: If your device is bricked and you can go to download mode:
1.3.1: Download one of the roms (according to your device)
1.3.2: Open odin, take the .pit file and put the rom .tar.md5 in the PDA SECTION
1.3.3: Before flashing, ensure re-partition is checked.
1.3.4: Flash, when the flash is finished your device should reboot.
1.3.5: When you device reboots, you will be in recovery with red errors which are saying mostly of the time: Can't mount... To erase these errors, WIPE DATA.
1.3.6 Reboot and enjoy your restored device!
Click to expand...
Click to collapse
I had no backup too and tried everything. This (zaclimon's thread) was my last hope after 2 hours of searching and it worked.
Hey !
ah, did i read that right? Re-partition HAS TO BE CHECKED??
and do you recommend installing Steve's Kernel after i hopefully returned my device?
yes it has to be checked in this case.
I had terrasilent 1.1 and klassik rom for 2 days but I had a lot of freezes, so I flashed the stock rom 2.3.6 and steve's kernel because the main reason I wanted the SGP4.0 was the combination of wolfson DAC+wolfson+poweramp.
If you are happy with music only, than this is enough.
But now I'm using my device more often (GTA 3 is on sale right now) and flashed terrasilent v1.2 two days ago. Now I'm waiting for the next version of StratusROM and will give it a try. Because sometimes I am not completely satisfied with the performance (sometimes) and it often wakes up while deep sleep causing more battery drain than usual.
natkingcole said:
yes it has to be checked in this case.
I had terrasilent 1.1 and klassik rom for 2 days but I had a lot of freezes, so I flashed the stock rom 2.3.6 and steve's kernel because the main reason I wanted the SGP4.0 was the combination of wolfson DAC+wolfson+poweramp.
If you are happy with music only, than this is enough.
But now I'm using my device more often (GTA 3 is on sale right now) and flashed terrasilent v1.2 two days ago. Now I'm waiting for the next version of StratusROM and will give it a try. Because sometimes I am not completely satisfied with the performance (sometimes) and it often wakes up while deep sleep causing more battery drain than usual.
Click to expand...
Click to collapse
People were experiencing bootloops with steve's kernel. Right now I'm using the latest terrasilent with stratus and I don't have any bootloops. (and you can change to ext4 with terrasilent)
Hi there
you guys mind giving me link to that Transilblaba thing ?
Thanks in advance...

[Q] Samsung Galaxy SII bootloop problem

Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Phitherek_ said:
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Click to expand...
Click to collapse
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
andrewwright said:
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Click to expand...
Click to collapse
Actually I never tried to change the kernel, I am now using Samsung' s original 4.1.2 firmware. Thank you for suggestion.
MistahBungle said:
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
Click to expand...
Click to collapse
Thank you for suggestion, however my device is not rooted (yet?), so I cannot use nandroid.
Flash with philz kernel and it will be I love team work Mb :thumbup:
Running pure stock, your options are basically zero short of doing a factory reset, which may not solve the issue. You could do a clean install of stock via Odin, but if you're going to go down that path you may as well go the whole hog & root the phone (you don't necessarily have to run a custom kernel/rom if you don't want to; plenty of people run rooted stock) and receive the benefits of same (I.E the ability to make nandroid backups - much better than any other option Samsung has ever come up with).
Thank you for redirecting me to PhilZ kernel. However, I do not know which version I have to download for the Polish firmware (XXMS1), could you clarify?
Also, I have found a Siyah kernel in my search, flashed beta4 but it does not work for me, should I try with beta5? And is it a good kernel?
Siyah v6.0b5 will work and philz lsw will work siyah is very good so is philz
I had exactly the same problem this morning.My phone originally had omega v23 (with philz) installed, but it kept running hot all the time, so I flashed stock 4.1.2 xwlsw with mobile odin and everroot. My question now is should I unroot my f/w before flashing philz kernel?
No just flash it will do as its told :thumbup:
andrewwright said:
No just flash it will do as its told :thumbup:
Click to expand...
Click to collapse
thanks. In the meantime I've doing some reading and somewhere in the depth of the philz kernel thread was a post buried, where some recommended to flash the tar file via mop. That's what I've done. It seems to have worked.
But it's running hot again. I had that before with the philz kernel, but that belongs in another thread
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
andrewwright said:
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
Click to expand...
Click to collapse
Dumb question, but I find I need to flash apolo, can I just go ahead and flash it in recovery over philz or is there something I need to look out for. Also I've read about scripts for cleaning up busybox and previous kernels? this is all very confusing
Use gs2 kernel wipe script flash script first then flash dif kernel.
this
Ok, I probably accidentaly found a cause of this problem. I had Facebook information on my lock screen and when I tried to refresh it my phone went on bootloop. So probably it is the issue with the information module of the lock screen (or maybe it was just a coincidence, if so, I will let you know). I think everyone with XWLSE firmware should consider disabling this feature. Btw. really thank you guys for PhilZ recovery + root kernel and Online Nandroid Backup suggestions, they are great .

Phone freezes after boot

hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Format
System
Data
Cache
Wipe dalvik
Then flash rom
Wipe cache again
Wipe dalvik again
Reboot.
--------------
alliances+siyah
iamdutchy said:
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Click to expand...
Click to collapse
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
chrismast said:
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
Click to expand...
Click to collapse
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
iamdutchy said:
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
Click to expand...
Click to collapse
SDS is, if I am not totally wrong, kernel related (btw @rootSU got a very informative thread about it). Hence the Android version does not matter that much whereas if a rom is using an "unsafe" kernel obviously it is not SDS safe. As described in that mentioned thread, if you upgrade recovery (newest CWM versions, e.g. philz) and kernel there should me not issue with SDS.

Help on Android 4.3

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.

Wi-Fi starts up too slow, Galaxy S4

Hi guys ! Haven't found this thread anywhere so I had to ask.
When I installed a new Stock ROM everything was perfect, but as time went by, my wifi started to turn on slower and slower, now it takes him about 1 minute just to turn on. When I turn it on and go to Settings it just shows a blank page until the wifi turns on.
Please, DO NOT suggest:
1. Cache wiping
2. Safe mode and uninstalling previous apps
3. Wifi boosters
4. Advanced Wifi settings, special menu settings, turning of battery savings etc
Since I have tried all of those options
And yeah, everytime I reinstall a Stock ROM it works like a charm, but I don't have time to do it every 3-4 months just to make wifi fast as a lightning, as installing a new rom takes time and reinstalling all the apps makes me very nervous
Thanks for the answers, stay cool as always !
Other than using another kernel, not really sure what would help with that. I used to have an S4 and work on them often and hadn't seen that kind of thing before. Very odd behavior...
es0tericcha0s said:
Other than using another kernel, not really sure what would help with that. I used to have an S4 and work on them often and hadn't seen that kind of thing before. Very odd behavior...
Click to expand...
Click to collapse
I really have no idea what could it be, I recently factory reseted the phone and Wi-Fi worked again like a charm...
If the problem was kernel, can you recommend me how to find the appropriate one for my ROM and can I add it to the phone through ODIN without resetting the device ?
Thanks for the answer !
Post a screenshot of the About Phone section showing the Build Number of the software. That'll help determine which kernel to try. You'll need a custom recovery such as TWRP to install the kernel. Kernel installs are done through the recovery and only require wiping of cache and dalvik cache, not a factory reset. It's recommended to perform a backup in recovery to be able to restore if the kernel doesn't work or has adverse effects.
Here it is...will have to look up about thie things you just wrote on how to do it, cause I am a 100% dumbass for this

Categories

Resources