Database Users

Phone does not start after reboot on jamal2367 ROM, S4 GE Final-R4

Hi all,
I have this annoying issue with [AOSP] Official 4.4.2 - S4 Google Edition - Final-R4 from jamal2367; current baseband installed XXUFNA1.
Problem:
When the phone loses connection, it dies. Then there is no way I can turn it on.
if unplugged from the power: it starts to boot and it dies again, sometimes at the "samsung boot text", sometimes a bit ahead, but it does not go further than the animated logo with 4 coloured bouncing balls (it does not matter how many time I try to restart the phone)
If plugged: it survives the first part of the boot most of the time, but it loops into the animated logo with the 4 coloured bouncing balls and the phone does not start.
Solution:
Every time I have to re-install Android, by:
- deleting Dalvik, Data, System, Cache.
- Install the ROM
- Apply a factory reset
At this point, if connected to the plug, the phone starts, but I have to go through the manual installation process.
This is a bit annoying I have to admin, anyone with this kind of issue, or am I the only one?
A few more info:
Phone was working great with jamal2367 4.3 (don't remember the baseband)
After 4.4 was out I installed it, but it was booting every 5 minutes or so, I decided then to go back to 4.3.
When I went back to 4.3, baseband was changed, but I kept the hold one.
Phone started to have random reboots as well, but once every 3-4 days, so I was ok with it.
4.4 releases were progressing so, after a while I decided to put it back.
I had the problem described above with previous (recent) baseband (like ml6and mj6).
Now I have the latest, but I have got the problem anyway.
A wild guess:
The phone now charges very quickly, I am wondering if the percentage that I see is realistic. Maybe it runs out of battery, which it could explain why the phone dies on reboots, but it does not explain why it loops once plugged in and why it does not turn off normally instead of just dying with a blink of an eye.
mmm that should not be the reason
Another wild guess:
I couldn't target a specific application. Sometimes it dies using fb, sometimes maps, sometimes hangout, sometimes a after a long phone call. The first two have "location" active, but I don't think that the last two are using it.
mmm that should not be the reason either.
A consideration:
I have noticed that once Android is installed, the phone signal is quite good, but then it goes down to one or two lines only. Most of the time I have one line only (in my area) and when it disappear, 6 times out of 7 it dies.
Thanks in advance.
R
PS=I could not post this into "Galaxy S 4 i9505 Android Development"

too long
be sure to flash from zero, wipe everything then flash 4.3
if everything fils go to stock 4.3 or 4.4 TW, then flash 4.4 gpe after

racoonlab said:
PS=I could not post this into "Galaxy S 4 i9505 Android Development"
Click to expand...
Click to collapse
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care

anu.cool said:
did you try battery calibration?
Click to expand...
Click to collapse
Nope I will give it a try
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Well, when I delete Dalvik, Data, System and Cache, I do it once I am inside _teamwin recovery_, I can also think about another ROM, but the one from jamal2367 is quite popular and I find it weird that no one else have the same issue.
Thanks for your reply though.
R

Same problem here...
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!

opticus44 said:
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!
Click to expand...
Click to collapse
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R

Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655

Xv1nX said:
Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655
Click to expand...
Click to collapse
mmm there must be some way. With the latest R1.1 I cannot even answer a phone call, with Ktoonsez's Kernel, with Alucard's Kernel no button works.
:-O

mmm also installing 4.3 back gives me random reboots. I am wondering if it could a wrong baseband.

it worked perfect for me for some hours. when i deactivated some bloatwares (g. earth, g. music, ...) it crashed and stucks in a loop reboot & crash at googke logo. swipe cache or wait some minutes don`t change anything.
i tried everything, now i have no idea what to do

I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R

anu.cool said:
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Hi,
What tool do you use for a battery calibration?

racoonlab said:
I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R
Click to expand...
Click to collapse
Same issue if I put back Jamal [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1,mmm, maybe the kernel....

The last thing I can say about it is that also all the sounds are gone. I cannot reproduce any sounds, notifications, alarm etc., it does not work on videos either.

I fix my problem! And I shared the solution here:
http://forum.xda-developers.com/showthread.php?p=49502855

racoonlab said:
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R
Click to expand...
Click to collapse
Sorry, long time since I last checked in. I downloaded official stock image from sammobile and flashed through odin.

same problem here
Hi guys same problem here,
GOOGLE EDITION 4.4.2 installed by Danvdh, Kryten2k35 & Ktoonsez on Galaxy S4 GT-9505 LTE with knox 0x1, and TWRP custom recovery when the battery reaches 0% turns off the phone I put the phone on charge and starts but hangs on colored dots.
How can I fix this?
Thx

[Q] HELP: my GT-I9505 is randomly turning off and on again

Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!

pimpl said:
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
Click to expand...
Click to collapse
Hi Mate,
Not saying this is your problem but i seen some people having issues with the power button , symptoms are similar to your random reboots like in constant reset....check the power button see if is stock and easy way to check is try to go to recovery without pressing the power button.....if is really stuck or short out you should be able to go to recovery without ( for a short time) ....that will prove that the problem is coming from there...
Of course if is very sporadic wait until is happening for testing ..

I had the same problem before because I disabled knox using supersu. What I did was delete all knox related apps and everything is good.

Many users had this problems with Knox as well. Try to uninstall everything relating to Knox, maybe it will work
Gesendet von meinem GT-I9505 mit Tapatalk

pimpl said:
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
Click to expand...
Click to collapse
Delete all knox related apps via "titanum backup" and you are good to go! :good:

martikip said:
Delete all knox related apps via "titanum backup" and you are good to go! :good:
Click to expand...
Click to collapse
Well.. What can I say? Thank you SOOOO MUCH!! The problem is solved! Indeed, deleting all Knox-Entries via Titanium Bakup really solved the problem. Now, everything is fine and the system runs smoothly. Again, thank you very much!

pimpl said:
Well.. What can I say? Thank you SOOOO MUCH!! The problem is solved! Indeed, deleting all Knox-Entries via Titanium Bakup really solved the problem. Now, everything is fine and the system runs smoothly. Again, thank you very much!
Click to expand...
Click to collapse
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!

Marcelocohenarg said:
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Click to expand...
Click to collapse
Indeed, I have never had a problem again, since I deleted the Knox-stuff. Just do it and the problem will be solved!

Marcelocohenarg said:
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Click to expand...
Click to collapse
It's right uninstall Knox and be happy
Gesendet von meinem GT-I9505 mit Tapatalk

I have the same issue at the moment - Phone is completely standard (Not rooted). All has been good until the morning of the 30th August when there was a new firmware update applied. I had already had the Kit Kat update earlier in August and the phone had been working with no issue, since this 220Mb odd 'patch' the phone will just randomly reboot, I say random but it just seems after it has been idle (Screen off) for a while on unlocking I can start an app (pretty much anything) and about 5 seconds later the phone will reboot. As the OP mentioned it is a faster than normal reboot and it doesn't play the normal start up sound either.
I am not sure what the update did, it mentioned ironically that it was fixing stability issues!!! - Is there a way without rooting the phone to roll back the firmware to before the patch?
Cheers.

Factory reset worked too
I have been struggling with a similar problem on my GT-I9505 since receiving a system update on May 30, 2014 -- random reboots many times a day, plus fairly reliable reboots about 30-40 seconds into any received phone call. I tried cleaning caches, uninstalling recently installed apps and then other unneeded apps, installing new updates, and lots of other things. My last resort was rooting and removing Knox as suggested here. But first I tried a factory reset, and it worked! I've now gone several days without an unintentional reboot. It's a pain to have to restore backups and reinstall apps, but it was worth it. I hope this information is helpful to someone.

Issues on my CF auto-rooted GT i9505
My firmware is the stock I9505XXUGNG8-DBT and rooted with CF Auto-root.and Phill''s CWM.
1. When I wake up my phone by pushing the home button my first screen is frozen until I push the home button again for 2 or 3 seconds. Only since then I can use my apps.
2. By incomming phone calls my phone reboots and I lose contact, so they have to call me again, Then everything is well.
3.The time on my homescreen doesn''t synchronize until I push the home button for the second time waking up the phone .
I already used SSCF Xposed. That didn''t help.
Somebody the same issues. Or somebody who got some tips for me.

Idebutterpiep said:
My firmware is the stock I9505XXUGNG8-DBT and rooted with CF Auto-root.and Phill''s CWM.
1. When I wake up my phone by pushing the home button my first screen is frozen until I push the home button again for 2 or 3 seconds. Only since then I can use my apps.
2. By incomming phone calls my phone reboots and I lose contact, so they have to call me again, Then everything is well.
3.The time on my homescreen doesn''t synchronize until I push the home button for the second time waking up the phone .
I already used SSCF Xposed. That didn''t help.
Somebody the same issues. Or somebody who got some tips for me.
Click to expand...
Click to collapse
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk

DarkerTimes said:
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
No do I have to?

DarkerTimes said:
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
I guess this will help. Knox often causes this issues. Just uninstall everything relating to Knox with Titanium Backup
Sent from my Galaxy S4 using Tapatalk

I'm having the same problem as OP.
I've frozen all Knox related apps in Titanium Backup, but the problem persists. Do I need to fully delete the apps do you think? Is there a difference?

c0dewana said:
I'm having the same problem as OP.
I've frozen all Knox related apps in Titanium Backup, but the problem persists. Do I need to fully delete the apps do you think? Is there a difference?
Click to expand...
Click to collapse
I think I solved my problem: I deleted all Knox related items and when I rebooted my phone again it stucks on the Samsung logo. I installed the stock I9505XXUGNG8-DBT again with Odin. Installed CF Auto-root.and Phill''s CWM again. Installed Supersu again.
Now everything is working again without the frozen screen, time synchronizes and no booting by incoming phone call anymore.

[Q] Unfortunately, <process or app> has stopped

Hello experts,
I got a galaxy s3 neo and I'm facing the following issue: after some time of use (about 2~3 weeks) almost all apps or processes start to crash so I get the message mentioned in the title. A cache clean-up or a factory reset don't solve the problem, I have even installed other 2 stock roms (Italy and Austria) but at the end the behavior is the same. However, if I leave the phone uncharged for a week it works normally for 2 ~ 3 weeks. Can it be a hardware issue?? Have one of you experienced such problems??
Thank you for helping,
Clóvis

basslinejr said:
Hello experts,
I got a galaxy s3 neo and I'm facing the following issue: after some time of use (about 2~3 weeks) almost all apps or processes start to crash so I get the message mentioned in the title. A cache clean-up or a factory reset don't solve the problem, I have even installed other 2 stock roms (Italy and Austria) but at the end the behavior is the same. However, if I leave the phone uncharged for a week it works normally for 2 ~ 3 weeks. Can it be a hardware issue?? Have one of you experienced such problems??
Thank you for helping,
Clóvis
Click to expand...
Click to collapse
Try to NOT auto-download backup apps from Gplay. Do you have root or cwm installed?

MoHuToP said:
Try to NOT auto-download backup apps from Gplay. Do you have root or cwm installed?
Click to expand...
Click to collapse
Hi MoHuTop,
yeah, I actually don't use Gplay backups after flashing or rolling back to default configuration. I don't have CWM or Root anymore cause I flashed the phone with a german stock rom about one month ago. Since then the phone worked fine for 3 weeks then the apps started crashing, phone freezing, constant reboots, files like fotos became missing, whatsapp notified the backup files were missing and so on. Did a factory reset but same way it didn't solve anything (the processes start crashing on the screen to select the phones's language) so I left the phone without battery for 2 days and it's now working "fine", don't know for how much time.

basslinejr said:
yeah, I actually don't use...
Click to expand...
Click to collapse
I think you've downloaded bad apps to get UI crashing. I'm 100% sure it's software problem. Take care of your phone and give more info, if you have another issues.
Best regards.

A previous downgrade attempt has scarred me from trying to downgrade again

Back in December while i was still on 6.0.1 but on the latest monthly update at the time, I have known for awhile that there was a high android system battery drain after the february 2016 monthly update so I wanted to downgrade back to February. But when I was in the process of downgrading, I got an error on odin and it failed. After I restarted my phone I got a message saying "an error has occurred while updating the device software. Use emergency recovery function in the smart switch pc software" so at that time i was freaking out a bit and I went searching around and people said around may of 2016 samsung updated the bootloader so you couldn't downgrade to an earlier month that had the older bootloader.
I just want to know if samsung has updated their bootloader since 7.0 being on the latest bootloader. I'm currently on August security patch and want to go back to March.

I was using, if I'm not mistaken, the Android 7.0 July patch and I wanted to do an experiment. So, I downloaded version 6.0.1 and flashed using Odin.
Everything went through smoothly!
Just a curiosity, why do you want to go back to March? There are no benefits rolling back to an older patch, unless you want to test something.
Also, people say everywhere that their batteries are X with Y update and then, with Z, it got worse (or better). It actually depends on your usage, what apps you have installed, how you use your phone, etc etc etc.
Ah! My S7 Edge is the Exynos version.
Regards

angourakis said:
I was using, if I'm not mistaken, the Android 7.0 July patch and I wanted to do an experiment. So, I downloaded version 6.0.1 and flashed using Odin.
Everything went through smoothly!
Just a curiosity, why do you want to go back to March? There are no benefits rolling back to an older patch, unless you want to test something.
Also, people say everywhere that their batteries are X with Y update and then, with Z, it got worse (or better). It actually depends on your usage, what apps you have installed, how you use your phone, etc etc etc.
Ah! My S7 Edge is the Exynos version.
Regards
Click to expand...
Click to collapse
I've had a serious kernel battery drain and i've tried whatever I could to fix it. It just started out of nowhere and I can't think of any apps that would cause it to continue and so my battery life has been horrible and it doesn't even go into doze half of the time and I also has forcedoze enabled.
If you were able to go back to 6.0.1 without having an error in odin, then what did i do wrong? I put all the right files in the right place.

orlans21 said:
I've had a serious kernel battery drain and i've tried whatever I could to fix it. It just started out of nowhere and I can't think of any apps that would cause it to continue and so my battery life has been horrible and it doesn't even go into doze half of the time and I also has forcedoze enabled.
Click to expand...
Click to collapse
What model is your phone? What country?
Battery drain, doze not starting... it's normally caused by apps.
Post a screenshot from Settings -> Device Maintenance -> Battery -> Battery Usage

angourakis said:
What model is your phone? What country?
Battery drain, doze not starting... it's normally caused by apps.
Post a screenshot from Settings -> Device Maintenance -> Battery -> Battery Usage
Click to expand...
Click to collapse
sm-g935w8 (canada) right now im currently backing up apps and other stuff in smart switch so it is charging but im getting like close to 3 hours of SOT when I used to get 6 hours back on 6.0.1 february and 4 hours on the first 7.0 (march)
Android OS has a high stay awake.

orlans21 said:
sm-g935w8 (canada) right now im currently backing up apps and other stuff in smart switch so it is charging but im getting like close to 3 hours of SOT when I used to get 6 hours back on 6.0.1 february and 4 hours on the first 7.0 (march)
Android OS has a high stay awake.
Click to expand...
Click to collapse
Ohhh Canadaaa \o/
What I would suggest is to start from scratch, without restoring any backup.
If you want, you can download the current and older versions from here: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935W8/
I'm also on August security patch and I consistently get 7h+ SOT but I disable preloaded apps, (especially Facebook), use the resolution in HD and a black theme to get the benefits of the AMOLED screen.
When using Odin, make sure you put everything on the right place and use CSC file instead of HOME_CSC. It will delete all your data!

angourakis said:
Ohhh Canadaaa \o/
What I would suggest is to start from scratch, without restoring any backup.
If you want, you can download the current and older versions from here: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935W8/
I'm also on August security patch and I consistently get 7h+ SOT but I disable preloaded apps, (especially Facebook), use the resolution in HD and a black theme to get the benefits of the AMOLED screen.
When using Odin, make sure you put everything on the right place and use CSC file instead of HOME_CSC. It will delete all your data!
Click to expand...
Click to collapse
I also have apps disabled or at least HAD them disabled..i've might have enabled them except the ones i know for sure i dont need like facebook, chrome and those microsoft apps...you get the idea. I use HD resolution and keep it on black or dark theme. I use substratum and have whatever apps are supported themed to black.
Also why not home_csc if im starting from scratch?

orlans21 said:
I also have apps disabled or at least HAD them disabled..i've might have enabled them except the ones i know for sure i dont need like facebook, chrome and those microsoft apps...you get the idea. I use HD resolution and keep it on black or dark theme. I use substratum and have whatever apps are supported themed to black.
Also why not home_csc if im starting from scratch?
Click to expand...
Click to collapse
HOME_CSC will not wipe /data, CSC will. I may be crazy, but I erase things the maximum I can, so: I factory reset before updating to a new version, I use the CSC file to flash via Odin and I factory reset after I've updated. Then I log in to my Google account and start installing my apps from Play Store.
Of course I don't do it monthly (because security patches make no drastic changes). I only do it when there's a huge update (like Android 6.0 to 7.0) or when I feel the phone becomes sluggish (because I've installed and uninstalled lots of apps, for example).
When I had my Nexus 6, I also used fastboot commands and TWRP to garantee it's 100% clean (yep, you can now shout * crazy dudeeee *)

angourakis said:
HOME_CSC will not wipe /data, CSC will. I may be crazy, but I erase things the maximum I can, so: I factory reset before updating to a new version, I use the CSC file to flash via Odin and I factory reset after I've updated. Then I log in to my Google account and start installing my apps from Play Store.
Of course I don't do it monthly (because security patches make no drastic changes). I only do it when there's a huge update (like Android 6.0 to 7.0) or when I feel the phone becomes sluggish (because I've installed and uninstalled lots of apps, for example).
When I had my Nexus 6, I also used fastboot commands and TWRP to garantee it's 100% clean (yep, you can now shout * crazy dudeeee *)
Click to expand...
Click to collapse
I used to restore all my apps that way too but the last factory reset i did I just restored backup but this time ill do it that way. So now then i gotta take screenshots of where all my apps are placed on my home screen

So I attempted it and it is a success!

Mediaserver drains battery, is there a solution?

Hello i've been using G900F for 2 years. I've nearly find every solution for my issues. But there is an issue which drives me crazy: Mediaserver battery drain.
Sometimes (few times in a week) my battery is empty just in an hour. The main cause is "Mediaserver". I tried some solutions on xda but it keeps draining my battery.
If you have a solution please help me.
Thanks in advance.

muratturatci said:
Hello i've been using G900F for 2 years. I've nearly find every solution for my issues. But there is an issue which drives me crazy: Mediaserver battery drain.
Sometimes (few times in a week) my battery is empty just in an hour. The main cause is "Mediaserver". I tried some solutions on xda but it keeps draining my battery.
If you have a solution please help me.
Thanks in advance.
Click to expand...
Click to collapse
Do you still have kit kat?? Asking you because this is the kit kats (4.0.x) principal issue that have never been solved. Partley even for lollypop (5.0.x) and solved for M.M. (6.0.1). Instal last 6.0.1 firmware and don't have problems any more with mediaserver.

joedellosso69 said:
Do you still have kit kat?? Asking you because this is the kit kats (4.0.x) principal issue that have never been solved. Partley even for lollypop (5.0.x) and solved for M.M. (6.0.1). Instal last 6.0.1 firmware and don't have problems any more with mediaserver.
Click to expand...
Click to collapse
Yes I'm using KitKat because i like that version of android. 6.0.x's asking for permissions is very bad option i don't like it. I don't update to 5.0.x or 6.0x because there is no option for rooting with keeping knox 0x0.

muratturatci said:
Yes I'm using KitKat because i like that version of android. 6.0.x's asking for permissions is very bad option i don't like it. I don't update to 5.0.x or 6.0x because there is no option for rooting with keeping knox 0x0.
Click to expand...
Click to collapse
Ok..try this if staying on 4.0.x: go in settings and then in applications. Find (don't remember well ...I'm on 6.0.1) mediaserver, Archive, media archive external archive, gallary, your music app and enter in all of thees ones doing a wipe cache and wipe data. Shut down your phone and before opening again, go in recovery and make a wipe cache. Reboot and wait 5 minutes defore doing anything so media server remakes your entire multimedia archive. Should be solved for a while until the next data corruption will be present again.