DOK2 all stock firmware here.
Got my phone back in december. My phone has been chugging alone fine until yesterday. not sure what happened but the lock screen takes minutes to come back. I tried doing a factory reset via software and when I did that the phone was still sluggish. Tried a stock recovery reset, and afterwards when i tried signing into my account and connecting to wifi at the initial setup the phone just rebooted back to the start screen again which i thought was real odd. It's currently restoring apps from the app store right now and it intermittently reboots itself while doing stuff. all while it's completely stuttering if i try to use it...
Is my phone starting to have internal memory failure? no SD card in the phone at the moment.
Should I try reflashing the DOK2 firmware via odin and then doing a reset again? Is that even possible with all the restrictions?
used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed
Check this thread for a workaround. I use an app to keep my phone from going into deep sleep.
http://forum.xda-developers.com/showpost.php?p=64584244&postcount=39
dtrinh4000 said:
used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed
Click to expand...
Click to collapse
Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.
Bruce lee roy said:
Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.
Click to expand...
Click to collapse
Did a factory reset and cleared cache, reflashed stock DOK2 from sammobile website using odin, cleared cache. things were going a little bit better at first but now just stuttering all over the place and randomly rebooting still. I only have very few apps downloaded, including facebook updates, instagram, all the samsung and google crap that forces updates...
Also want to add that booting into recovery takes a very long time, longer than i've ever noticed it taking... 7 min+ sometimes it will say "installing system updates" with the android guy chugging along, other times it will just have the android guy chugging....
Is there anything else I can try? Is there something I can test to verify that it's a hardware issue and not a software problem, like a flash memory checker?
This phone is out of warranty, and knox has been tripped so I have very limited options here. Would the Tmobile store let me do an exchange for a fee?
bump... anyone? am i really screwed?
dtrinh4000 said:
bump... anyone? am i really screwed?
Click to expand...
Click to collapse
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822
cuteman said:
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822
Click to expand...
Click to collapse
I do get some touch wiz crashes and random app crashes . since I'm on dok2 is there any other rom or recovery I can flash ? Or so some super duper erase method? I'm pretty much ready to cut my losses and sell it for parts on eBay.
i'm not alone it seems
http://forum.xda-developers.com/note-4-tmobile/help/note-4-major-slowdown-bugs-boot-loops-t3311297
http://forum.xda-developers.com/note-4-tmobile/help/looping-screen-t3319204
http://forum.xda-developers.com/note-4-tmobile/help/reboot-shutdown-wont-removing-battery-t3316875
I am having same issue. Was running stock until 3 days ago, when I got fed up with the stock reboot and slow-down. I guess it's time to save up and get a new phone.
Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....
dtrinh4000 said:
Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....
Click to expand...
Click to collapse
Well, fool me once.... Having spent $800 on a phone that broke in just over a year, hell would have to freeze over before I give Samsung any money again.
Related
I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
If you are talking about roms.. Well most are a 1. I habent heard of an official froyo update. And.if.you by chance do.brick it, there are ways to unbrick it pretty easily.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have the Bell Vibrant which is the I9000M.
I thought that Bell released an official update for their new Froyo. Check it out here
mobilesyrup.com/2010/12/08/bell-samsung-galaxy-s-vibrant-upgrade-to-os-2-2-froyo-coming-december-10th/
Did update my Bell Samsung Galaxy S GT-I9000M with Bell release Froyo available using Kies and all seemed to be running smoothly until I had issues connecting my bluetooth and trying the voicedialing features that did not work in my case and after got Force close on every apps. Did a shutdown and got the device in a loop at boot up.
Will try tonight to reload the device with 2.1 and see from there to retry 2.2.
Finger cross !
I upgraded with no problems but I did do a factory reset as things started to get a bit slow and from what Ive read it is a good idea to do a reset to get rid of any residual 2.1 stuff on the device. Since then the update has been working well for me...
KNOCK ON WOOD!!!
I have 2 SGS phones so you'll just have to add another vote to the "successful upgrade" option in addition to the one I was able to cast
I've flashed the following 2.2's without any problems so far:
- unofficial JK3 (Canada) via ODIN
- official JK4 (Canada) via Kies
- straight JPU via ODIN
- JPU Doc RomMOD v2 via update.zip recovery
No problems with flashing.
And yes, clearing data & cache is helpful (mandatory?). Backups are good!
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
ssj2miguelx said:
I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
Click to expand...
Click to collapse
AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
Cool. That makes this type of poll misleading then because someone reporting success today may have issues tomorrow (we can't change our vote correct?).
That's right. I saw your post about your phone going bust. Sorry to hear that.
I just can't get Kies to work -- it just says "connecting to device" and it hangs
Also can't install MPT USB drivers -- always fails. I installed the correct x64 bit Windows 7 drivers and everything.
Ughh
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
ssj2miguelx said:
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
Click to expand...
Click to collapse
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If your card is gonna die its gonna die no matter if you upgrade or not....Flashing just seems to speed up the corruption.
Thats a good question. People seem to be having big issues with this new Froyo update here, http://forum.xda-developers.com/showthread.php?t=867157. I really hope Bell gets a fix for this new "firmware Froyo 2.2" that they just released.
If the Nexus S is the so similar to the SGS I9000M why dont we have Gingerbread (2.3) yet?
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If I was you I'd flash the crap outta your phone. If your black screen was due to a weak internal SD then it's gunna go. So flash it and hope it goes so you can get a new(repaired) one. Of course the wait time is a bit long right now for repairs. And there's no guarantee that the newly repaired one won't blow.
Damn this phone....
And yes, clearing data & cache is helpful (mandatory?). Backups are good!
Click to expand...
Click to collapse
How to do it?
It will delete also my files (photos, music....) on the internal memory?
Regards
Sent from my GT-I9000 using Tapatalk
AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Videonut said:
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Click to expand...
Click to collapse
Is there a chance that my phone has a bad internal SDcard?
betaboy00 said:
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Click to expand...
Click to collapse
Took mine into the bell store at guilford mall, originally purchased at wireless wave.Unlocked and being used on the fido network. No issue at all, the guy took down my cell number as a way to track its progress.
ssj2miguelx said:
Is there a chance that my phone has a bad internal SDcard?
Click to expand...
Click to collapse
There's no way to know for sure. Some ppl seem to have a bunch of force closes bfore it dies and others just turn it on and it's dead.
Picked up my NC 1.0.1 today. Rooted without issue. After having a Google Talk conversation, I lost access to Marketplace, and all Google Apps? Can't log back in?
Anyone else having similar issues?
P.S. My wallpaper was changed as well ?!?!?!?!?!
p.p.s. My browsing history and favorites are gone too? Please tell me an update or something was just pushed out. I feel like I just wasted a few hours of my life here.
My rooted 1.0.1 nook has problems as well. Gets authorization error and resets data. After restoring through the clockwork recovery, had it up just for 5 minutes before it automatically reset again. Lost all my apps, market access, youtube, etc. Don't know if this issue has been discussed before. May just have to go back to stock.
It appears that something is amiss. I cannot sign back into any Google Services.
Can't establish a reliable data connection to the server
This could be a temporary problem or your phone may not be provisioned for data services. If it continues call Customer Care.
Click to expand...
Click to collapse
Would a simple re-rooting solve the issue?
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
abexman said:
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
Click to expand...
Click to collapse
I might add that I got my device it was at 1.0.0 and I rooted then reflashed to stock to upgrade to 1.0.1 and rerooted. Then I noticed after today's unexpected reboot/data wipe (the status screen during the reboot says it was wiping data) it again gave a message that it had just upgraded to 1.0.1 so I initially thought this was an issue with the device thinking the firmware upgrade was not quite done...
Mine quit working as well. Mine is a 1.0.0 that was auto-nootered. Everything was fine and I used it daily. Now it is a brick, nothing I do seems to make it boot. Every once in a while I can get the backlight to come on but nothing else and it just goes off again in a few seconds.
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
If your NC dosen't boot at all. Try doing a dd of snowfox's boot.img in dev section. See thread for more info. You'll need to boot into NF from SD.
Sent from my HTC Desire using XDA App
scottfish said:
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
Click to expand...
Click to collapse
I have tried rerooting, and restoring through clockwork...it seems to always revert and bootloop. Although the reroot lasted a week and clockwork restore hasn't lasted 24hrs twice now.
Not sure what to do but My wife is ready to kill me! I'll have to go stock till someone finds a way to bust up this authorization or just wait I read some ROMs are being developed.
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
I hadn't realized I should be doing this. I will try it. I am actually thinking that my first store purchase came w/ an update (my issue seemed to start right after a magazine trial purchase was made).
Thanks.
>DARKMAN< said:
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
Click to expand...
Click to collapse
Thank you, I will try that. All the searching I did was for disable OTA NC and such but actually searching for OTACerts brought out many many threads that were archived on this subject... I can't wait to get home to try it!
I did not rename the ota file.... will give it a go.
Idk what's the problem with Samsung phones and updates. I had the same problem with my Note 3 when KitKat got released, I had to get a replacement phone. Lucky for me the replacements Note 3 didn't have the update on it. However I wasn't so lucky with the Note 4.
I accidently hit the update on my notifications when I was half sleep.
Anyways.
Every since Lollipop been installed on my Note 4, it has been a nightmare from hell.
When I installed it on my original Note 4, I kept having my keyboard become unresponsive. Force close on multiple apps (stock Web, camera, calender, and more).
I called T-Mobile to see if they could send me a replacement. They "tried" to fix it, saying that I should do a factory reset and clear cache , which I already tried before I called numerous times.
Finally they said they said they were going to send me out a replacement phone.
I also asked if anyone have been complaining about Lollipop they said no, they were totally oblivious to Lollipop having any kinks (as always ). It's crazy they said that because I have read over 100 post bashing the new update.
I received the Note 4. I turned the phone on and Lollipop was already installed. I called T-Mobile and asked why was Lollipop installed on my replacement, they informed me that they are sending out the phones with Lollipop, and assured there would be no problems with it.
With in the first hour, my phone would turn off and not turn back on. I knew there was nothing wrong with the battery because it was on 90% and it worked flawless with another phone. So I drained all the electricity out the phone and put the battery back in. That worked, but it did over 20 times within that day. I called T-Mobile again , they told me I would have to go to a store and see if they could diagnosis the phone.
The next day I went to the store, everything came back clear on the diagnosis, but they could see it turn off randomly.
I called customer care and explained the situation and told them I need a replacement.
Now I am waiting on a replacement. If this one don't work, I think I will have to get on whole different phone. I'm on the verge of getting a flip phone because I know that I don't want to have an iPhone.
Anyone having these issues with the update Lollipop?
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
MajorTom_ said:
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
Click to expand...
Click to collapse
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
W0man09 said:
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
Click to expand...
Click to collapse
As long as you can get it into download mode something may be possible.
Odin to stock lollipop, factory reset / data wipe.
Additionally, I would consider a custom rom.
..........
If you really like kitkat better you could also Odin to stock kitkat, factory reset / data wipe.
MajorTom_ said:
As long as you can get it into download mode something may be possible.
Click to expand...
Click to collapse
Lol thanks for the help. I can't even get it to turn on, to get it in download mode. ??
. Now I'm just waiting on T-Mobile to send the replacement.
Hey all, I recently got my nexus 6, and out of the box it worked fine. I started trying it out, and realized things were crashing quite often, like google play, and gmail. Then it prompted me to install the Android 5.1 update, which is when all this started.
Upon finishing the upgrade my nexus 6 cannot get past the Optimizing Apps screen, as soon as it gets onto the "Starting Apps" state, it will simply crash, and start over, booting again. This has been very frustrating since I just got this device and want to enjoy it. I have not rooted it, I have not tampered with it and the bootloader is locked. I tried cleaning the cache partition but that didn't help. So is anyone else experiencing this with their nexus 6? I really need a way to fix this, and if I have to flash the stock image onto it, then I will. But since the bootloader is locked is that even possible?
Please help me, I don't want to send it back in and wait another eternity.
Yes it's possible. However. Try a factory reset from recovery first.
graydiggy said:
Yes it's possible. However. Try a factory reset from recovery first.
Click to expand...
Click to collapse
I've done that a zillion times. It's not working, my phone refuses to get past the "Android starting..." screen. So if you could walk me through how to flash, since I couldn't find a guide online.
I called google support, and they want to replace it. So I'm gonna do exactly that.
I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.
[email protected] said:
I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.
Click to expand...
Click to collapse
third? that makes it seem as you are the one thats not doing something right. just saying. one, ok, it happens. two, chances are very slim, but it can happen, mist likely wont. three, you are doung something wrong. if you factory reset, then it boots without android is upgrading. when you add apps, change apps, or change things in your system, or wipe dalvik, then android is upgrading happens.
[email protected] said:
I'm now on my third phone from google and they all do this. easily the worst customer service experience I've ever had in my entire life.
Click to expand...
Click to collapse
DEFINATELY operator error...
they don't "all do this", otherwise the THOUSANDS of us here on XDA who flash things constantly without issue every day would be experiencing the same thing..
hello guys
I have an issue on my S10 and thats just rebooting randomly, even sometimes when im not using it and its standby on the desk.
i search about it and saw someone elese have same problem, so i want to know what is the problem and how to fix it.
i found someone who fixed it with some solution at this topic but that is not my phone model :crying:
i just change my android version to 10 and its not fixed..
i tried home csc and csc files and even tried pit files too..
please hellllp
thanks
Did you try a data factory reset? It might be a hardware issue, I would take it to a local repair shop or contact Samsung on it.
StoneyJSG said:
Did you try a data factory reset? It might be a hardware issue, I would take it to a local repair shop or contact Samsung on it.
Click to expand...
Click to collapse
yes i did and not worked..
Justphemy said:
yes i did and not worked..
Click to expand...
Click to collapse
get the factory firmware from sammobile.com and flash it in Odin. be sure to factory reset from within the settings first or the FRP might crop up. This is the nuclear bomb method that 99% of the time fixes any glitches caused by software. You might have a hardware issue, but this will help rule that out
Youdoofus said:
get the factory firmware from sammobile.com and flash it in Odin. be sure to factory reset from within the settings first or the FRP might crop up. This is the nuclear bomb method that 99% of the time fixes any glitches caused by software. You might have a hardware issue, but this will help rule that out
Click to expand...
Click to collapse
Thanks man i will try it soon, so is it different from that what I did? I tried update to android 10 with odin, with 4 files
Justphemy said:
hello guys
I have an issue on my S10 and thats just rebooting randomly, even sometimes when im not using it and its standby on the desk.
i search about it and saw someone elese have same problem, so i want to know what is the problem and how to fix it.
i found someone who fixed it with some solution at this topic but that is not my phone model :crying:
i just change my android version to 10 and its not fixed..
i tried home csc and csc files and even tried pit files too..
please hellllp
thanks
Click to expand...
Click to collapse
I had this issue with rooted Android 9, too. But it it very strange you get this problem on Android 10 because the kernel panic problem is fixed there. When you are not rooted, you should not have this problem anyway. Try restore your software in Odin like the other users already suggested.
ThomaSEK said:
I had this issue with rooted Android 9, too. But it it very strange you get this problem on Android 10 because the kernel panic problem is fixed there. When you are not rooted, you should not have this problem anyway. Try restore your software in Odin like the other users already suggested.
Click to expand...
Click to collapse
i just checked my phone for update with Smart Switch app on pc, and that show me an update with a pda and csc codes to update.. i just do it, is it ok right now?
It should be okay, yes.
Justphemy said:
i just checked my phone for update with Smart Switch app on pc, and that show me an update with a pda and csc codes to update.. i just do it, is it ok right now?
Click to expand...
Click to collapse
Please let me know if this has worked for you. I'm having a similar problem that only started when i updated to android 10.
I have a totally stock, Verizon S10. Never had a problem with it on 9. After updating i started noticing after about 8-12 hours phone starts getting very sluggish, gets hot, has trouble even doing processor intensive things like opening camera and taking a picture without it crashing back to the OneUI launcher. Launcher would show up blank and take 5-10 seconds to restore my icons and widgets. Lock Screen lags really bad and face rec hardly works if at all. Phone gets really hot and if i look at the CPUs (Antutu BM) they are usually all maxed out.
A reboot fixes everything and then it will be fine again for another 8-12 hours and then, like clockwork, it starts up again. I've done a factory reset with data restore. Didnt fix it. Did another one without data restore and it is still happening. Would an Odin flash be different than a factory reset from the settings menu?
razen_kain said:
Please let me know if this has worked for you. I'm having a similar problem that only started when i updated to android 10.
I have a totally stock, Verizon S10. Never had a problem with it on 9. After updating i started noticing after about 8-12 hours phone starts getting very sluggish, gets hot, has trouble even doing processor intensive things like opening camera and taking a picture without it crashing back to the OneUI launcher. Launcher would show up blank and take 5-10 seconds to restore my icons and widgets. Lock Screen lags really bad and face rec hardly works if at all. Phone gets really hot and if i look at the CPUs (Antutu BM) they are usually all maxed out.
A reboot fixes everything and then it will be fine again for another 8-12 hours and then, like clockwork, it starts up again. I've done a factory reset with data restore. Didnt fix it. Did another one without data restore and it is still happening. Would an Odin flash be different than a factory reset from the settings menu?
Click to expand...
Click to collapse
no thats not worked..
i have similar problem sometimes
Perhaps reflash the same firmware with home csc
Justphemy said:
no thats not worked..
i have similar problem sometimes
Click to expand...
Click to collapse
I think I may be onto something. Do you have any battery monitoring apps? I had Accubattery, better battery stats, and gsam battery monitor installed. Gsam and BBS had battery_stats permissions granted via adb. I was beginning to wonder if they were causing some kind of memory drain so I wiped their data and uninstalled them. Immediately after that I rebooted and after 46 hours of uptime there was absolutely no problem. Phone flies and runs cool as ice.
I'm currently installing them one at a time and waiting 48 hours after each install to see if and when the problem comes back.
---------- Post added at 12:16 PM ---------- Previous post was at 12:06 PM ----------
And I'd just like to add that when my phone starts acting up it gets worse and worse to the point it won't even unlock and go to the home screen. Then it will actually reboot itself. I assume it panicked because it just doesn't have enough ram to complete any tasks.
so maybe its about the battery for you? btw my problem still alive
Guys, I got the same problem, did you guys find a way to fix it? Just realised today that even the system data, i.e fingerprints have been corrupted, what exactly is happening and how to fix this, it has been driving me crazy for the past couple of months.