Related
Hi,
I have been using my HD2 with android for a long time without too much trouble. Not long ago, while still using SD builds I would find that my phone would often freeze, this would happen almost always while surfing the web or playing games or while putting the phone under heavy load. Using nand builds the issue has gotten even worse. Every single build I have tried is almost certain to freeze during the initial setup, even if I leave it alone and give it a long time to setup and stabilize. I have been using a stock gingerbread NAND build for a week or so and it just won't be stable. It freezes during games or surfing the web mostly (though upon first installing the build, almost anything might trigger a freeze, including scrolling through a menu). I have tried task 29, and many builds but they are all giving me this issue. Even the last WINMO rom I tried did the same. I am completely baffled by this and have no idea what could be wrong. Does any one have any advise?
Thanks
Pray that you're still under warranty???
If it does it in winmo, try flashing your original stock (From HTC) ROM. This will remove HSPL and any & all customisations. Make sure the phone is in it's 'from factory' state. If it STILL has freezing issues, you need to get it repaired. If not. Start installing ROMs again from scratch.
Hope This Helps.
Thanks for the response. Yeah, I have done everything except resort to the stock ROM.
I have noticed some interesting things about the crashing behavior. If the phone has been left alone for a while, it will be able to browse the web/ play games or do intensive tasks without crashing for a decent amount of time, however once it crashes , it will very likely crash right away after I reboot. I only notice the phone (battery) is quite warm around the time it starts the crashing. I hope my hardware is screwed up, would hate to give up this phone . I bought my phone on ebay, so I don't think I have warranty either. ugh
wtf, there is seriously no one else who has heard of this?
Bump.
Are you Overclocking it? Try Underclocking it to see if it is more stable. Maybe your hardware is failing. User currentWidget to see your current usage.
Maybe you're using too much ram. o.o
The phone will get really laggy if you use up all the ram, so clear it up with a task killer.
No overclock, running at 998 (stock) and smartass governor. Tried interactive governor and still does it.
Its just strange that it crashes left and right from doing anything when I first install a build and after a few reboots it stabilizes enough to be rock solid for all tasks except playing something like angry birds or surfing the web. I tried running quadrant 10 times in a row to stress the phone and it did fine.
Could the phone be overheating? I notice its almost always warm or hot when it crashes.
poweroutlet said:
Thanks for the response. Yeah, I have done everything except resort to the stock ROM.
I have noticed some interesting things about the crashing behavior. If the phone has been left alone for a while, it will be able to browse the web/ play games or do intensive tasks without crashing for a decent amount of time, however once it crashes , it will very likely crash right away after I reboot. I only notice the phone (battery) is quite warm around the time it starts the crashing. I hope my hardware is screwed up, would hate to give up this phone . I bought my phone on ebay, so I don't think I have warranty either. ugh
Click to expand...
Click to collapse
Actually this is exactly what you should do. Flash with a Stock ROM then Take29 then start over. Remember the Stock ROM has more than just the system ROM, it overwrite your RADIO and other stuff also that are not touched by custom ROM. so if you have some corruption at radio ROM the stock ROM should fix it.
- When I mean Underclocking: set MAX Frequency to 800 Mhz and see if it is more stable. just to find the root cause by elimination
nightcraw said:
Actually this is exactly what you should do. Flash with a Stock ROM then Take29 then start over. Remember the Stock ROM has more than just the system ROM, it overwrite your RADIO and other stuff also that are not touched by custom ROM. so if you have some corruption at radio ROM the stock ROM should fix it.
- When I mean Underclocking: set MAX Frequency to 800 Mhz and see if it is more stable. just to find the root cause by elimination
Click to expand...
Click to collapse
I'll try to cap it at 800 Mhz and see if I can cause a crash. Regardless Its probably best to flash to stock rom.
Here is what I think I'll do:
Flash to stock rom.
Reflash HSPL
Task 29
Flash new radio
Flash MAGLDR
Flash new android rom
So I flashed 2.10.1 stock rom from here:
http://forum.xda-developers.com/showthread.php?t=655653
And it did not remove HSPL...though it reset my radio to 2.08.
So far things are not looking good. On the very first boot the stock winmo rom crashed and rebooted. Should I flash another winmo rom?
EDIT:
I've reflashed HSPL and also flashed the latest winmo stock rom with Radio 2.15 now. Running Android off the SD card, 2 minutes of angry birds is all it took it to freeze it. I'm starting to believe there must be some hardware damage or something, this is making no sense.
Even surfing the web in the stock winmo rom caused a reboot, the phone is getting quite hot too.
Having exact same problem... should i warranty it and send it in?
ArkAngel_X said:
Having exact same problem... should i warranty it and send it in?
Click to expand...
Click to collapse
If you are lucky enough to still have warranty, do it. I don't have that option sadly.
So I have pretty much narrowed down the cause of the problem to overheating. I let the phone cool down to about 25c and then I ran angry birds and surfed the web and it didn't crash and I played for about 15 minutes. When the temp approaches about 37-40c, the chances of a crash become pretty high, once it crashes it will keep crashing left and right until I let it cool back down.
All evidence now points to an overheating problem. Especially because it is only intensive tasks which seem to cause crashes and only the more CPU/GPU intensive tasks can cause the phone to heat up fast.
Anyone else dealt with this issue? I have no other way to prevent this than to stop heavy use of the phone when it gets warm. This is ridiculous, next thing I know, I'll be walking around with a desktop CPU heatsink mounted on my HD2...
First post WOOO
I have been having a similar issue with my HD2 (Telstra). I was running darkstone on the SD card but occasionally my phone would freeze then I would have to restart a few times to get it working (or leave it for a while). I decided to install the android desire stock ROM using NAND. I changed the radio according to the recommended 2.15.50.14.. after I did this I had a lot of problems with frequent freezing even before installing the new ROM (so during the process). I did successfully install the stock ROM but I now have the issue where if I enable internet usage within about 5 minutes my phone will freeze (but only if I am using the phone). However if I use wi-fi or usb tethering I can use the net for anywhere between 5 minutes and 8-9 hours.
I also have the problem of freezing just after boot, but apart from that my phone has never frozen unless I enable internet usage. Furthermore, this issue only became frequent after changing radios. (for the life of me I can't remember what the previous radio was). When I have more stable internet access I'll try flashing a few different radio's...
But right now funnily enough.. I'm jumping between my phone internet and someones open network in my apartment block... both of which are very sporadic...
Hope this helps somewhat (or will at least..)
There are many threads regarding this issue. If you still have the problem after trying different radios and roms, then it is probably the mainboard.
Mine was also overheating and after I tried all possible fixes, I sent it for repair. They changed the mainboard and everything is OK now. No overheating at all.
I've got a problem with my I9000, several times throughout the day it will randomly restart itself. It will be quite happily sat idle in my pocket not doing anything, and then suddenly I hear the boot-up sound from my pocket. It's just started doing this since Thursday or Friday I think it was, had nearly 700 hours uptime on it (699 hours ) and then I noticed from my SeePU notification that something was hammering the processor, running it at >90% for more than 10 minutes. Couldn't see any programs running in the background so decided to restart the phone. This is one my problem started.
It's running stock JPY with Voodoo Advance kernal, it was overclocked to 1.2GHz and had some undervolting from 800MHz down, this had been stable for all of those 699 hours, but I disabled the OC and UV yesterday to see if it was that causing the trouble, but even with it disabled the phone's still been restarting.
What would be really great is if there is some kind of crash log for Android (something similar to the Windows Event Viewer) so I can see what's causing this. Does anyone know if such a thing exists, and if it does how I might go about accessing it?
Failing that, anyone know why my phone would suddenly start restarting itself now?
had pretty much the same issue, different kernal and rom... but had an OV/UV that for the most part was stable...
then today was continually restarting.....
solution?
changed CPU scheduler to noop
changed CPU Governor to conservative (Galaxy S cpu default configuration)
Now not restarting at all... and that's with a 1.3GHz overclock... running several benchmarks and no undervolting at all.
I'll let you know if it starts acting up... but interesting that this at least fixed it for me.
Stupid thing has restarted itself twice this morning. This is ridiculous.
I've just set the schedular to noop, can't see an option to set the governor though. Will see if that sorts it.
Would really appreciate knowing if there's a log file or something though
If it was a PC you would say its overheating .
jje
Found an app on the market called OS Monitor that shows all the running processes and what load they're putting on the CPU, it also shows the dmesg and logcat log files.
Thankfully my phone hasn't restarted itself since changing the schedular, but if it does I should hopefully now be able to find out why
quick answer. Reflash the phone .
I guess reflashing and removing some dangerous apps will be good for you phone.
Hmm, well looks like it's given up on restarting itself and is just plain turning itself off now.
Looks like I'm going to have to reflash the stock kernal and see if that fixes it
Hi,
Anyone been keeping an eye on hotplugging on the n9005 ?
Mine is still unrooted, so I'm talking 100% vanilla Samsung configuration...
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
At some point, after a few hours of uptime, sometimes only after quite a many (20h+), I just notice that it will never drop below 2 or 4, never had it lock on 3 minimum, so can't comment on that scenario.
Once this happens, it's impossible to get back to single core even on very low load.
Also when leaving the device doing nothing, freq. drops to 300MHz and still 4 cores remain online.
There is obviously an impact on battery drain as well.
Only way to get back to normal is to reboot...
JP.
I've noticed the opposite issue, two cores just going offline forever until I reboot the device.
So that would point to obvious hotplugging issues, except if you ran into thermal throttling, maybe.
Were you running some heavy stuff when this happened ?
JP.
i tested it out of curiosity using the widget in system monitor app.
i have exactly the same issue as SentinelBorg above. the two cores go offline and never come back online until the next restart.
very wierd.
Well for the very least we can conclude hotplugging is flawed in the current firmware ...
As soon as we get a proper recovery (nandroid restore that don't bootloop) I'll start working on an improved kernel, this is just not acceptable for a top notch 700€ pricetagged device
JP.
Send from my Note 3 (n9005)
Latest case ...
Send from my Note 3 (n9005)
Again ...
Send from my Note 3 (n9005)
You're on full stock. Doesn't that mean you have no options regarding CPU government?
nakedtime said:
You're on full stock. Doesn't that mean you have no options regarding CPU government?
Click to expand...
Click to collapse
Correct, so I cannot do anything about this misbehaving, except reboot.
I want to know whether this is something others observe as well.
The thing is, if you're not looking at it, you won't know it's happening, cause who really keeps an eye on online cores all the time ? I do as I do kernel coding and as such also work on governors, which make me look at stuff like that.
If this happens of yours, you'll just have a hotter Note 3 with less lasting battery without knowing why, or worse without knowing battery easily could last longer if that was fixed.
This clearly is a bug in the current firmware, since as you correctly stated, being full stock unrooted, I can't be influencing this in any other way than applying load to the CPU which is clearly not the case as you can see in the screenshots... and it just happens randomly.
Once I start on a Note 3 kernel that will be in the top list of things to take care of.
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
I would have gone with the N9000 if I knew how to develop a kernel. BIG.little sounds like so much fun to dev on.
PS
Have you found any Info about the thermal throttling? I'd love to be able to manipulate the temps for less heat when over clocking.
I was actually not going to get any more Samsung device because of crappy open source support they (in fact don't) give
I ended up going for the note 3 because of the specs and exactly because it was the Qualcom and not the Exynos version and a one time offer I could not refuse, but I will go nowhere Samsung's own super secret Exynos CPUs ever again unless they change their policies, which I doubt.
I just do hope I won't regret my move...
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
exactly the same here, after a reboot everything is back to normal
Sent from my SM-N9005 using Tapatalk 2
Happened again after ~10h uptime while watching a live video stream...
Cores went to a steady 4 online, load was unchanged over a longer period (~45 mins of video stream over WiFi).
This makes little sense, hotplugging is flawed.
JP.
PS: Still stock unrooted.
Send from my Note 3 (n9005)
This is still happening for me, reboot solves it. Running 4.4.2 and thought this should be solved by now.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Stock kitkat XXUENB3, unrooted. I have a similar problem when all of the sudden all cores are stuck online with core 1 and 2 stuck at 1958 mhz and core 0 and 3 scaling normally just not going offline. A reboot fixes the issue untill it happens again randomly. This is my last Android device and I had gs2,gnex,n4 and now n9005.
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
ciprianruse88 said:
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
Click to expand...
Click to collapse
Yes, long time I've open this thread
Indeed, on TW I used to do just that, "pkill -9 mpdecision", which killed the daemon and it respawned and all was back to usual.
I've since then moved to CM11, and this never happened again ever since, so I expect this to be a TW related issue, since mpdecision had the same MD5 signature in CM11 as on my stock 4.3 TW ROM.
And it looks like if the problem still persists on KK TW...
But it's certainly not a kernel related issue, as I've use my own kernel on JB TW, where this happened as well, once I went CM11, I ported my kernel to CM, and as I mentioned, never happened ever since.
Might be TW messing with DVFS (for benchmark cheating and maybe other things...).
Maybe worth trying to use Wanam's Xposed Module and disable ROM DVFS.
JP.
2 cores always online and the other 2 always offline= Dual Core
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
SAVVAS. said:
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
Click to expand...
Click to collapse
Yes. I've did the exact same thing and cpu was dual core but after I've reset mp decision I couldn't reproduce it anymore. Good catch!
Yank555 said:
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
Click to expand...
Click to collapse
How did you enable the online core notifications in Android Tuner?
My phone shuts down on 4.3 and 4.4 based roms.
It happens much less often on 4.2 and stock based roms.
It seems to happen when the screen is off. It doesn't shut down when I'm in the middle of doing something. I've seen that on other phones.
If the screen is off, but I'm listening to the music player or Pandora, it does not shut down.
It does not seem to be overheating.
I'm on my 3rd sim card in 2 months and my second class 4 SD card. I only bought a new one b/c used the one from my old phone and thought it was best to start fresh.
Currently I'm running the first CM11, but this has been happening on CM 10.2, AOKP, and a variety of other roms.
My recovery is TWRP 2.6.3.0
I use the regular GAPPS, not PaGAPPS and the appropriate GAPPS for the given AOSP base; 4.2/3/4
I flash SuperSu-v1.65 after a full wipe when installing new roms.
The current apps I have installed in addition to what comes with CM are:
Evernote
Freecell
Google Voice
gReader Pro
Pandora
Quickoffice
Rom Toolbox Pro
Scanner Radio
Shuttle+
SMS Backup+Restore
Solitaire
Tapatalk Pro
UPM - Universal Password Manager
Xposed Installer - I don't have any modules installed at the moment and the last time today it shut down by itself was before I installed Xposed.
I know that logcats are good for tracking down errors for apps that FC, though I don't know yet how to read logs.
Is there an app I can use that can show me activity before the last shutdown?
How can I track down what's causing it?
TIA
please delete
On 2nd thought I did not feel I could contribute well.
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
aviwdoowks said:
please delete
On 2nd thought I did not feel I could contribute well.
Click to expand...
Click to collapse
Thanks for trying though.
ATTACK said:
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
Click to expand...
Click to collapse
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
FirePsych said:
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
Click to expand...
Click to collapse
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Thanks,
I had read that the SOD had been reported elsewhere, but never saw any solutions. Just lots of folks replacing their phones.
I haven't had one in the last 24 hrs on the 12/08 CM nightly and flashed the 12/09 this morning.
I also made the MPdecisions change. We'll see if it sticks. I assume since it's a system file, I'll have to make the change every time I flash a new nightly or or new rom, but that's not a big deal.
Oh, and yes SOD is probably more accurate than "shutdown" because I've noticed that the led will flash if I've received a message, but I can't revive the phone, so obviously it's not complete shut down.
ATTACK said:
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Click to expand...
Click to collapse
@ATTACK.
Thank you!
I hate to jynx myself, butthis seems to have done the trick. Only had 1 or 2 BSOD since your response and I think both times were because I forgot to make the change after flashing a new rom.
Happy Holidays
FP
This thread may have saved my phone. I keep waking up to find my phone with a blinking LED notification and me being unable to get the screen to turn on. I renamed the MPdecision file and I'll hope for the best. (^^)
So hello anybody seeing this thread and thanks for considering even reading this
so my phone now is acting crazy , this started to occur after i tried to return to the stock firmware but two things happened while installing the stock firmware
1st- i got an error copying file called "HIDDEN" error reason = size was too big so i removed it from the firmware file and installed it and it installed successfully then i restarted it to install twrp and format data from there so i wont lose my stuff on the phone and that leads to the second problem
2nd- i wasn't able to access any partition and i mean all of them [SYSTEM-DATA-CACHE] so my only solution was to change the file type and get it back to ext4 to kind of force them to be reformatted and that was successful too so i re-installed the firmware and then this problem arised
my phone's CPU usage was so high like 95% all the time and it was running on 2150mhz i think like all of the time and my battery was getting like killed in a matter of 2 hours, please have in your consideration that this was a freshly installed rom that i didn't even install any apps on it yet
so i thought maybe this firmware was bugged so i changed to NX's team s8 rom just to find out the same problem was happening again but the only difference is that when my screen is off it goes into deep sleep like normal but when i open the screen and unlock the phone the usage goes up again frome idle to 95%-100% so i thought maybe touch boost or CPU hotplug so i tried every hotplug avalaible even tried disabling them along with the touch boost but nope my 4 cores are all running and killing my battery so i thought maybe this rom too so installed linage os and RR just to find out the same problem was still there when the screen is off my phone could do like 14 hours easily on battery or more but when i open the screen it immediately goes to 95%-100% usage and my phone gets hot till like 70 degree so i changed the kernel too
so did anybody face something like this before or could at least tell me what's wrong and how can i fix it
and tell me if it could be like anything related to my phone's hardware like faulty hardware or something related to bootloader -modem etc.
please any response would be good and appreciated hope someone could help me