Database Info

[Q] Automatically Rebooting

I need some help, I have a Galaxy Note 10.1 GT-N8013 and it keeps rebooting every 5 to 10 minutes? I have installed JB 4.1.1 and everything seems to work very well with the exception of the auto rebooting. The model number in settings says GT-N8000 and the Kernel is 3.0.31-125933, Is there a way to revert back to the original ICS? or is there a solution that someone can suggest to stop the auto reboot?
Thanks!

When you installed JB did you factory reset, clear cache and dalvik cache? This seems to be a major culprit for bad flashes...
Also, the JB you've installed is for the 3G version of the note 10.1. I don't know if that could be the problem either...

ultramag69 said:
When you installed JB did you factory reset, clear cache and dalvik cache? This seems to be a major culprit for bad flashes...
Also, the JB you've installed is for the 3G version of the note 10.1. I don't know if that could be the problem either...
Click to expand...
Click to collapse
Thanks for responding, I went in and cleared my cache and it seems to have worked. Thanks. I am aware that it I have the wrong Note for the JB update but I thought I would try it and see. It works very well but is there a way to get the original ICS back to my Note?

heymikep said:
Thanks for responding, I went in and cleared my cache and it seems to have worked. Thanks. I am aware that it I have the wrong Note for the JB update but I thought I would try it and see. It works very well but is there a way to get the original ICS back to my Note?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1847706
in case you using another region...
go to web samsung-updates.com/device/?id=GT-N8013 (1072.3MB)
download the full stock firmware, flash it use PDA with Odin3.

flymouse said:
http://forum.xda-developers.com/showthread.php?t=1847706
in case you using another region...
go to web samsung-updates.com/device/?id=GT-N8013 (1072.3MB)
download the full stock firmware, flash it use PDA with Odin3.
Click to expand...
Click to collapse
What is the difference between the following two:
1. KIES_HOME_N8013UEALH2_N8013XARALH2_1015435_REV00_user_low_ship.tar.rar (from link you provided)
2. GT-N8013 XAR N8013UEALI3 (from samsung-updates.com/device/?id=GT-N8013 site)
I looked at my Note and it shows GT-N8013EAYXAR Deep Gray GTN8013EYGR, which one of the two will work for my Note?

Hard Reset doesn't work/deleted apps are restored after reboot

Hello everyone,
I just joined this forum and i need some help.
I've got a very wierd problem with my samsung galaxy tab 2 7.0
Tablet: Samsung Galaxy Tab 7.0 GT-P3110 model.
Android: ver. 4.1.2
So the story behind my tablet is that my dad bought it when he working in another country,when he came back he told me that he had a broken galaxy tab 2 and he asked me to try to fix it,the problem he reported was that the tablet sometimes restarts,alot of programs have crashes and the wierdest thing is that,when I turn it off and then turn on the device (or simply restart it) the system is restored to some earlier state, this includes:
1. Apps I've deleted are still installed.
2. Widgets or app shortcuts on 'home' pages are still on their old place though I've rearranged them.
3. Same with wallpapers.
4. Same with settings.
So i tried the following:
1. Factory reset + cache clean. Even though it is supposed to be a full system wipe, it doesn't work.
2. Reinstalling a Stock ROM via ODIN. Doesn't work either and it takes about an hour to do...it says it was successful but it doesn't change anything in the tablet.
Also there is a notice in android recovery, which states:
did not match sized '/system/csc/common/system/csc/feature.xml' (no data available)
This device wasn't rooted.
So i you would ask you guys for some help,thanks.

Radowitz said:
Hello everyone,
I just joined this forum and i need some help.
I've got a very wierd problem with my samsung galaxy tab 2 7.0
Tablet: Samsung Galaxy Tab 7.0 GT-P3110 model.
Android: ver. 4.1.2
So the story behind my tablet is that my dad bought it when he working in another country,when he came back he told me that he had a broken galaxy tab 2 and he asked me to try to fix it,the problem he reported was that the tablet sometimes restarts,alot of programs have crashes and the wierdest thing is that,when I turn it off and then turn on the device (or simply restart it) the system is restored to some earlier state, this includes:
1. Apps I've deleted are still installed.
2. Widgets or app shortcuts on 'home' pages are still on their old place though I've rearranged them.
3. Same with wallpapers.
4. Same with settings.
So i tried the following:
1. Factory reset + cache clean. Even though it is supposed to be a full system wipe, it doesn't work.
2. Reinstalling a Stock ROM via ODIN. Doesn't work either and it takes about an hour to do...it says it was successful but it doesn't change anything in the tablet.
Also there is a notice in android recovery, which states:
did not match sized '/system/csc/common/system/csc/feature.xml' (no data available)
This device wasn't rooted.
So i you would ask you guys for some help,thanks.
Click to expand...
Click to collapse
My line of thought is that if you do root it, you can format the system partition which would more than likely fix this issue. But like I said, more than likely, there's no guarantee because it might be a hardware issue. Have you considered sending it in for repair? Since it's not rooted they would do it. If you don't care to send it in and are just trying stuff to see if you can get it working again, then rooting it wouldn't hurt anything. But that's your choice.
Sent from my GT-P5113 using XDA Premium 4 mobile app

njstein said:
My line of thought is that if you do root it, you can format the system partition which would more than likely fix this issue. But like I said, more than likely, there's no guarantee because it might be a hardware issue. Have you considered sending it in for repair? Since it's not rooted they would do it. If you don't care to send it in and are just trying stuff to see if you can get it working again, then rooting it wouldn't hurt anything. But that's your choice.
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the quick answer,well like i said my dad brought it from another country,and he's probably not going back so i will try to root it.

Radowitz said:
Thanks for the quick answer,well like i said my dad brought it from another country,and he's probably not going back so i will try to root it.
Click to expand...
Click to collapse
I found this to be the quickest, easiest and everything you need in one shot:
http://forum.xda-developers.com/showthread.php?t=2535083
Hope it helps and goes well!

I just tried it,saldy it didn't work even though odin said it passed,the tablet remains the same,same apps ect.

Radowitz said:
I just tried it,saldy it didn't work even though odin said it passed,the tablet remains the same,same apps ect.
Click to expand...
Click to collapse
OK, so here's where just rooting won't help. You have two options: 1) Find the stock ROM at Samsung and have it on your SD card. Or 2) choose another ROM. Whichever you choose is up to you. You're going to have to format your system in the custom recovery, by doing this your tab is wiped of all info including the stock ROM. If you format system you won't be able to boot into your tab without flashing another ROM after. If I'm repeating stuff you know, I apologize. You'll need the ROM you choose on your external sd card, because you'll want to completely format everything (except your ext sd). If you know all this, try it out and see if it helps. If you want to learn more and the steps, PM me, I'll help as much as I can!
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app

P3100 Phone keep restart - CSC error
njstein said:
OK, so here's where just rooting won't help. You have two options: 1) Find the stock ROM at Samsung and have it on your SD card. Or 2) choose another ROM. Whichever you choose is up to you. You're going to have to format your system in the custom recovery, by doing this your tab is wiped of all info including the stock ROM. If you format system you won't be able to boot into your tab without flashing another ROM after. If I'm repeating stuff you know, I apologize. You'll need the ROM you choose on your external sd card, because you'll want to completely format everything (except your ext sd). If you know all this, try it out and see if it helps. If you want to learn more and the steps, PM me, I'll help as much as I can!
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, i'm facing the same issue here. Then I've try to root the phone but failed. Can help me too Sir?

For now it can't repaired, It,s known as emmc brickbug, find the xda forum thru Playstore emmc brickbug check. In Indonesia there is website that claim can repair it by replacing the emmc chip/internal memory, but it's not proven yet, since no body in our Galaxy Tab 2 facebook group has confirmed it. More than 15 people in the group has reported this bug, and the only way to fix it is by replacing the mainboard in Samsung Service Center. I also have replaced my wife Galaxy Tab 2 10.1 mainboard with the same case. In Indonesia the cost is about US$100
Sent from my GT-P3100 using XDA Free mobile app

metallicumahua said:
For now it can't repaired, It,s known as emmc brickbug, find the xda forum thru Playstore emmc brickbug check. In Indonesia there is website that claim can repair it by replacing the emmc chip/internal memory, but it's not proven yet, since no body in our Galaxy Tab 2 facebook group has confirmed it. More than 15 people in the group has reported this bug, and the only way to fix it is by replacing the mainboard in Samsung Service Center. I also have replaced my wife Galaxy Tab 2 10.1 mainboard with the same case. In Indonesia the cost is about US$100
Sent from my GT-P3100 using XDA Free mobile app
Click to expand...
Click to collapse
Same case here, i'v tried flash with 2 rom, it take an hour and than failed, tried to flash TWRP, succed but still nothing happen

2015 Problem solved?
greatbayu said:
Same case here, i'v tried flash with 2 rom, it take an hour and than failed, tried to flash TWRP, succed but still nothing happen
Click to expand...
Click to collapse
Any updates to this problem or is this any unfixable situation. what about side load? been trying for 7 months now to fix this and nothing works... nothing at all

A new tablet will fix this issue. Seems like the only solution.
Pp.

Linuslatchman said:
Any updates to this problem or is this any unfixable situation. what about side load? been trying for 7 months now to fix this and nothing works... nothing at all
Click to expand...
Click to collapse
This error is caused due to damage of internal memory , the solution is replace the mainboard , which is very expensive

Getting erorr below error message in samsung core while doing reset factory.
phone geting restarted every time and not able to install roor apps as well in case ho wto fix the issue.
Applied the CSC:INU
did not match sized '/system/csc/common/system/csc/feature.xml' (no data available)

Main problem is, that DEBUGGING MODE is enabled only to restart, after restart is OFF

did not match sized '/system/csc/common/system/csc/others.xml' (NO Data available)
hi everyone ...i would like first to ask sorry for my bad english.. i speak french correctly but not english..
i receved a samsung mobil phone from a friend comming from turkey and i noticed that every applications that i install there are delated automatically when the phone reboot so i can not have apps there and when i try to change the language the phone reboot itself ...i tryied to flashed a new rom from the same contry that i download on sammobil and samsung-firmware.org but not when done with flash ODIN says RESET and PASS after ...and when i open the bootloader i see this message
did not match sized '/system/csc/common/system/csc/others.xml' (NO Data available) i installed X-PLORE to open and see if something is missing in csc folder and ive seen that CSC.folder is empty there is no xml code there ..
so my phone only help me to make and receve calls ..i dont know what to now ...
please if u have any suggestion tell me ....thanks

OMG! same problem here with no solution

how to fix it ?
HOW TO FIX IT ?:crying::crying:
did not match sized '/system/csc/common/system/csc/feature.xml' (no data available)

hemm Samsung INDONESIA...
i am facing the same problem here.. :crying:

I'm facing same problem her with Samsung Galaxy Tab 2 10.1 still waiting for a solution here

it seems the only sloution is to repartition emmc with any compitable box like jtag or ufi .......etc same proplem here cant find any one have these boxes from egypt

CyanogenMod 11

Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk

It IS about time.

ok so the cm wiki page says to use cwm. any reason i can't use twrp?

Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.

been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.

Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.

orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.

What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?

I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?

Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?

Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.

robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk

After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help

Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk

reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.

using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).

robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.

orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:

did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).

Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)

Gear 2 losing notification access on phone reboot

I'm on the latest leaked lollipop rom for s4 and upon reboot my gear 2 loses notification access. Has anyone else experienced this? Hard resets, factory resets and updates of both phone and gear don't seem to make a difference.

albiGib said:
I'm on the latest leaked lollipop rom for s4 and upon reboot my gear 2 loses notification access. Has anyone else experienced this? Hard resets, factory resets and updates of both phone and gear don't seem to make a difference.
Click to expand...
Click to collapse
Have you tried going in Security/notification access and allowing gear manager ? I don't have lollipop but I just thought about this...

Yes, in the lollipop rom I'm using the notification access is under sounds and notifications, and it's enabled, until I reboot. Then it loses access.

albiGib said:
Yes, in the lollipop rom I'm using the notification access is under sounds and notifications, and it's enabled, until I reboot. Then it loses access.
Click to expand...
Click to collapse
Have you also tried wiping cache partition and Dalvik cache ?

Indeed, plenty of times,including full wipes of both phone and gear, to no avail. I'll keep trying out solutions and eventually I'll get one.

albiGib said:
Indeed, plenty of times,including full wipes of both phone and gear, to no avail. I'll keep trying out solutions and eventually I'll get one.
Click to expand...
Click to collapse
Well you seem to know what you are talking about so I would say that you ROM seems not to be compatible with the G2, I have no formal knowledge though

I'm beginning to suspect as much. I'll flash another version of LL at home later and see if it's the rom I'm using at the moment (which is giving me umpteen reboots and seems to act like a thermal power plant lol)

*update* flashed different kernel and even though the permission on reboot still occurs, I now get notifications, where as before I didn't,and my phone is cool. I'll post my findings when I flash a new rom.

Same issue here.
I9505 using leaked lollipop. Original Gear running latest OTA Tizen.
Disconnect reconnect and turning off blyeooth does not trigger the issues but full reboot does.
Have tried latest Gear Manager APK leaked from S6 but did not fix.
Hoping for fix soon as its very annoying

Yep, Im pretty much on the same boat as you, latest gear OTA, using latest lollipop leak also, with exactly the same gear manager and issue. I'll certainly keep at it and post a solution, if I find one, here.

By the way, is Svoice working on your gear?

*SOLVED*
freeze 'glance view mk' in titanium backup. No more permission loss.

albiGib said:
*SOLVED*
freeze 'glance view mk' in titanium backup. No more permission loss.
Click to expand...
Click to collapse
Hello,
I flashed the last official lollipop touchwiz rom on my GT-I9505.
I have the same problem: After reboot the settings for notification access are lost, only the "glanceview mk" has access.
I have to reenable all other checkboxes (eg. "Tasker", "Tesla Unread",...) until next reboot...
Because I have no root, do you have other solutions?
Regards,
Alexander

same issue for me.
i noticed that happens after rooting my galaxy s4.
i tried reboot the phone before rooting and the permission for gear manager remain.
(sorry for the english)
Regards
Fabio

spam, delete

It happened me the same on note 4 lollipop. I fixed it disabling talkback.Apk
Check what applications remain turn on in the notification access after reboot, once you know them disable them throw application manager, and after that turn on gear manager as notification.
Sent from my SM-N910F using XDA Free mobile app

Bump. This is my problem too on 5.0

solved
albiGib said:
*SOLVED*
freeze 'glance view mk' in titanium backup. No more permission loss.
Click to expand...
Click to collapse
Thanks! Your advice eliminate the issue!

albiGib said:
*SOLVED*
freeze 'glance view mk' in titanium backup. No more permission loss.
Click to expand...
Click to collapse
any way to solve this on non rooted phone?

Galaxy S7 restarts randomly!

Hey, XDA-ers!
I got the Android Nougat 7.0 update for my Samsung Galaxy S7 SM-G930FD (DUOS) back in January if I remember correctly. And the update process went like how it normally does. But ever since I got the Nougat update, my phone restarts randomly for no reason. At first it used to restart when I click on the 'Recent Apps' button to switch between apps. When I tap on the button, the phone vibrates and restarts. The phone never over heated before this happens. During this, the phone used to restart 2-3 times a day. This went on for 2 months. Then now, the number of restarts reduced to 1-2 per day, but the problem still persists. And now, it restarts even when I don't touch the 'Recent Apps' button. So, if any of you has had a similar experience or if any of you could help me out Please share it here. It would be GREAT!
Also just one more thing- Any of you seen any DRASTIC or worse changes in battery life of your Galaxy S7 after the Android Nougat 7.0 update? Please share your thoughts here and do suggest how you solved the problem. (My battery drains so fast that I sometimes charge it twice a day. I don't even use my phone for half of the day because I'll be at school and still the battery drain is bad! )

Factory reset. Backup your data via kies and then reset it.

Change your battery

What firmware version are you running? There's at least one version of Nougat that has issues with this
https://forum.xda-developers.com/galaxy-s7/help/random-reboots-nougat-update-t3584333

Us3rNam3d said:
Factory reset. Backup your data via kies and then reset it.
Click to expand...
Click to collapse
Hey, man!
I already tried it like 3 times now. No luck!?

CurtisMJ said:
What firmware version are you running? There's at least one version of Nougat that has issues with this
https://forum.xda-developers.com/galaxy-s7/help/random-reboots-nougat-update-t3584333
Click to expand...
Click to collapse
Hey man!?
The screen shot attached has my software info. Check it out and tell me if it's one of the versions with the problem.
Thanks!

Hmm... and after the factory reset with no apps installed you are still rebooting?
Why dont you try to reflash your firmware via odin.
Download it from sammobile and reflash it.

AgentArjun56 said:
Hey man!?
The screen shot attached has my software info. Check it out and tell me if it's one of the versions with the problem.
Thanks!
Click to expand...
Click to collapse
Possibly. I can vouch for it being fixed on DQCF onwards, which is newer than DQC4. The temporary fix seems to be to use as little RAM as possible(try to cut down on background apps until the next update). That firmware isn't terribly old though. I would actually agree with trying a reflash first.

CurtisMJ said:
Possibly. I can vouch for it being fixed on DQCF onwards, which is newer than DQC4. The temporary fix seems to be to use as little RAM as possible(try to cut down on background apps until the next update). That firmware isn't terribly old though. I would actually agree with trying a reflash first.
Click to expand...
Click to collapse
I think it is also possible to reinstall the same firmware with Smart Switch from the menu "Emergency Software Recovery and Initialisation". It's like Odin but much simpler especially for beginners. As for me, I am still in DQBO and I await the update DQD7 which is beginning to be deployed in some countries. If this is not going to solve the problem, I will try to reinstall the fimware with Smart Switch. What do you think ?

GeekTN said:
I think it is also possible to reinstall the same firmware with Smart Switch from the menu "Emergency Software Recovery and Initialisation". It's like Odin but much simpler especially for beginners. As for me, I am still in DQBO and I await the update DQD7 which is beginning to be deployed in some countries. If this is not going to solve the problem, I will try to reinstall the fimware with Smart Switch. What do you think ?
Click to expand...
Click to collapse
If it's restarting due to the firmware bug then DQD7 will most definitely fix it. Beware of the emergency recovery though. Ive not used Smart Switch but the "initialization" part sounds like it would wipe the device, though that could fix any issues. Backup first, if you can.