Related
I would just like to know if you experts here at XDA know a solution to this. I am using the UnOff 3.0 ROM, I seriously have next to almost no apps installed, but I do have the last version of Android that Darkstone created (3.2 I believe), HSPL 3.0 and I have installed Hastarin to overclock my phone. My phone just keeps overheating and rebooting, I can't use my phone to use apps or watching videos.
I am willing to delete every file on my SD card and phone memory to fix this problem, but this is obviously my last option.
Please help me XDA, and I am very sorry if this similar situation has been solved here before, if so, please link me.
help me please
This is a known problem with the HD2 and I was suffering this during summer time when using it as navi in my car
When batt-temp rises over some 46 °C and in cahrging cradle lights start to blink orange-green and not charging any more, when temp rises further HD 2 freezes and/or reboots.
Gets worse when android runs
No solution to this yet.
It started on my HD2 (ex) last month. Came from nowhere, did not install anything or made any changes, no drops or whatsoever (in otterbox by the way) Shipped it back and got a new one (I assume refurbished)
I would recommend the same, I tried, flashing rom, clean install, (no install at all) even if you go back to factory settings, it reboots watching transformers.
Now i run wmo + android (darkstone ram edition- crazy fast) at the moment android draws 300 ma even with that no reboots at all.
CGCR said:
I would just like to know if you experts here at XDA know a solution to this. I am using the UnOff 3.0 ROM, I seriously have next to almost no apps installed, but I do have the last version of Android that Darkstone created (3.2 I believe), HSPL 3.0 and I have installed Hastarin to overclock my phone. My phone just keeps overheating and rebooting, I can't use my phone to use apps or watching videos.
I am willing to delete every file on my SD card and phone memory to fix this problem, but this is obviously my last option.
Please help me XDA, and I am very sorry if this similar situation has been solved here before, if so, please link me.
Click to expand...
Click to collapse
i have highlighted what i think might be the problem in your quote above.
when overclocked, the device will generally shutdown/reboot when the CPU is mildly stressed if the CPU can't handle the voltage/frequency combination. running your CPU overclocked to the edge of stability CAN damage your hardware. usually, removing the overclocking makes the system stable again, unless some sub system has been damaged, perhaps due to prior overclocking.
see if any of the above might have happened with you. sounds plausible...
You do know what "overclocking" means, right OP?
same problem with my mates phone it was overheating and rebooting by itself.it was a hardware problem,because its under guarantee for 12 months he send it to tmobile in uk.and they send it to htc,they changed the hardware.the only reason i know they changed the hardware because his phone was unlocked and had a different i.m.e.i number.when the phone came back it was locked also.only hardware problems has 12 months guarantee.if your phone is less then a year try this,they fix it for nothing.its htc guaranteed.
make sure you flash back the original rom and get the hspl out.if they find out they wont fix it,and charge you money to send the phone back to you.
shame this is happened,i hope you sort it out a.s.a.p
Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83
Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...
Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.
Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.
maybe reflash back to winmo then do evrything all overagain to android
I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card
the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83
it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt
Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help
I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...
Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.
Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.
i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.
freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!
Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83
Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83
Hi,
i noticed months ago the following on my IDEOS X5 (german) concerning bad battery life. It could be the reason why there are so many different reports regarding bettery lifetime of the U8800.
First - why did I start to investigate: because the phone sucked about 5-10% per hour while not beeing used / lying on my desk, so after max 20 hours the battery was empty. But this did/does not always happen....
What I did: it took some time to get used to android (its my first droid) and learn how to troubleshoot. A month after I got this phone I learned that the GSM-code *#*#4636#*#* will show you very useful information concenring battery/phone usage. I started to play around with the phone (factory reset, install/remove apps, enable/disable different options like 2G/3G/WLAN etc...) always keeping an eye on the 4636-infos.
Result: When I use WLAN the phone simetimes enters an "state" when it never again enters "sleep state" and the battery gets sucked as stated above. I switched off WLAN for a week and this did not occur while standby time increased to 48 hours and 4636 stated an "phone awake" percentage of below 20% (normal usage). Once I reenabled WLAN again it took about an day of WLAN usage to reproduce the bug and "phone awake" time increased to 100% while standby time decreased to below 20 hours. ONLY rebooting the device recovers from this "state". I further noticed that this does not happen if just WLAN is available but no 2G/3G (phone had no SIM). My conclusion is, that the
"You May Be Charged"-Popup is the culprit. It does lock the phone to this "state" for some reason, mybe when the WLAN connection is dropped while the phone is not used (traveling). Can someone reproduce this on his phone (maybe not german)?
Resolution: IMHO none. I send the device twice to reseller for service. First time the complete mainboard was changed without success regarding the battery drain. Second time nothing was done - they just returned the device to me.
Thanks.
This is a known problem, that already has a thread...
http://forum.xda-developers.com/showthread.php?t=1043760
This is affecting ALL Froyo Roms, if you want battery life, install Oxygen or CM7...which are based on Gingerbread.
There is no point in discussing this issue anymore, this is a very well known problem and Huawei doesn't care.
Sending the phone back to manufacturer won't help at all.
Thank you for the hint - it realy looks like the same issue. Knowing more about the nature of this issue could give people not willing to install custom roms a possible solution. Can someone move this thread over to that one?
katu2006 said:
This is a known problem, that already has a thread...
http://forum.xda-developers.com/showthread.php?t=1043760
This is affecting ALL Froyo Roms, if you want battery life, install Oxygen or CM7...which are based on Gingerbread.
There is no point in discussing this issue anymore, this is a very well known problem and Huawei doesn't care.
Sending the phone back to manufacturer won't help at all.
Click to expand...
Click to collapse
But Huawei is about to release official 2.3 in Q3 atleast I hope...
andreasha said:
But Huawei is about to release official 2.3 in Q3 atleast I hope...
Click to expand...
Click to collapse
Everyone is looking forward to official 2.3, but we'll have to wait and see if the "sleep" bug will be sorted.
katu2006 said:
Everyone is looking forward to official 2.3, but we'll have to wait and see if the "sleep" bug will be sorted.
Click to expand...
Click to collapse
I hope some more bugs are straightened out like headphones and internal mic at the same time. Headset button to work. Battery time!
none of my android phones could use the phone's mic when headphones were plugged in
I saw a solution for the mic-with-headphones-problem a few days ago, either here or at modaco (do not know if it is confirmed working though).
fajabird, I know that you want this to work with the ROMs provided by Huawei. Huawei obviously does not care too much about providing the community with updates (they do not even have gingerbread-support by now). This is the downside of this low priced phone.
Let me just say this: It took me about one hour to understand the ultimate-guide at modaco. It took me another hour to decide which ROM I want to use. If anything goes wrong at the installation I can easily start over again. Now I have a fully working phone with Android 2.3.5 with a battery that lasts at least 2 days, sometimes 3(if I do not play any games within that time). Of course I understand that you are probably very pissed at Huawei for providing a ROM with a bug that serious.
if you find that fix again, let us know where to look
darkado said:
if you find that fix again, let us know where to look
Click to expand...
Click to collapse
It is to be found at the Android-development-section, right here. Note that you cannot use the mic of your headset after applying this
too bad, it would be awesome to be able to use both
XphX said:
I saw a solution for the mic-with-headphones-problem a few days ago, either here or at modaco (do not know if it is confirmed working though).
fajabird, I know that you want this to work with the ROMs provided by Huawei. Huawei obviously does not care too much about providing the community with updates (they do not even have gingerbread-support by now). This is the downside of this low priced phone.
Let me just say this: It took me about one hour to understand the ultimate-guide at modaco. It took me another hour to decide which ROM I want to use. If anything goes wrong at the installation I can easily start over again. Now I have a fully working phone with Android 2.3.5 with a battery that lasts at least 2 days, sometimes 3(if I do not play any games within that time). Of course I understand that you are probably very pissed at Huawei for providing a ROM with a bug that serious.
Click to expand...
Click to collapse
Hi, thank you for sharing your experience with me. I always wanted to update to some custom roms but the time I started investigating this issue there was no stable one out there. On the other hand I thought there might be a dev interessted in more details regarding this issue helping him to sort out this nasty bug for whatever reason.
Can someone tell me, if his U8800 also has the ambient light sensor but like mine does: it won't reduce the brightness, just increase works. Thanks.
fajabird said:
Hi, thank you for sharing your experience with me. I always wanted to update to some custom roms but the time I started investigating this issue there was no stable one out there. On the other hand I thought there might be a dev interessted in more details regarding this issue helping him to sort out this nasty bug for whatever reason.
Can someone tell me, if his U8800 also has the ambient light sensor but like mine does: it won't reduce the brightness, just increase works. Thanks.
Click to expand...
Click to collapse
Mine reduces brightness but does it quite weird sometimes like adjusting several times without the light around me changing...
Mine always adjusts it way too low. If I am inside the brightness is always on minimum. I use the power-widget on the homescreen. I only change it at night, it is on max. for the whole day (the max. brightness is still kinda low, especially if it's sunny).
fajabird said:
Hi,
i noticed months ago the following on my IDEOS X5 (german) concerning bad battery life. It could be the reason why there are so many different reports regarding bettery lifetime of the U8800.
First - why did I start to investigate: because the phone sucked about 5-10% per hour while not beeing used / lying on my desk, so after max 20 hours the battery was empty. But this did/does not always happen....
What I did: it took some time to get used to android (its my first droid) and learn how to troubleshoot. A month after I got this phone I learned that the GSM-code *#*#4636#*#* will show you very useful information concenring battery/phone usage. I started to play around with the phone (factory reset, install/remove apps, enable/disable different options like 2G/3G/WLAN etc...) always keeping an eye on the 4636-infos.
Result: When I use WLAN the phone simetimes enters an "state" when it never again enters "sleep state" and the battery gets sucked as stated above. I switched off WLAN for a week and this did not occur while standby time increased to 48 hours and 4636 stated an "phone awake" percentage of below 20% (normal usage). Once I reenabled WLAN again it took about an day of WLAN usage to reproduce the bug and "phone awake" time increased to 100% while standby time decreased to below 20 hours. ONLY rebooting the device recovers from this "state". I further noticed that this does not happen if just WLAN is available but no 2G/3G (phone had no SIM). My conclusion is, that the
"You May Be Charged"-Popup is the culprit. It does lock the phone to this "state" for some reason, mybe when the WLAN connection is dropped while the phone is not used (traveling). Can someone reproduce this on his phone (maybe not german)?
Resolution: IMHO none. I send the device twice to reseller for service. First time the complete mainboard was changed without success regarding the battery drain. Second time nothing was done - they just returned the device to me.
Thanks.
Click to expand...
Click to collapse
Hey there friend, I've detailed much of this and been through a lot of troubleshooting. It did not appear to be the "You may be charged" popup as I disabled that whenever I changed ROMs. I never did get a solution for any of the Huawei ROMs, it just seemed like bad code as Dzo pointed out with the WiFi driver.
A very simple solution for me was installing one of the 2.3 ROMs, they are quite stable at the moment, especially Oxygen (although I use MIUI). You will find much better battery life with these.
Best of luck,
Ryan
My stock rom 2.2.1 Shows Android System 97% battery usage and battery drains 50% in 19minutes! With wi-fi, 3g, Bluetooth, everything is off and even i do not use it.
Flash latest official 2.2.2, wait for official 2.3, flash the custom 2.2.2 rom void or flash a custom 2.3 rom. I would recommend flashing the latest 138 or 162 to get the latest modem baseband or manually install the AMSS.bin.
Sent from my Ideos x5
andreasha said:
Flash latest official 2.2.2, wait for official 2.3, flash the custom 2.2.2 rom void or flash a custom 2.3 rom. I would recommend flashing the latest 138 or 162 to get the latest modem baseband or manually install the AMSS.bin.
Sent from my Ideos x5
Click to expand...
Click to collapse
I can't because phone do not use my external SD card somehow. In android i see files but in recovery-it does not use external sd.. I ask in forum why-but nobody answers
Backup ur data on it and format it. If that doesnt work ill send you a guide how i fixed mine, its just a partition error.
Sent from my Ideos x5
andreasha said:
Backup ur data on it and format it. If that doesnt work ill send you a guide how i fixed mine, its just a partition error.
Sent from my Ideos x5
Click to expand...
Click to collapse
I formated it via phone, then via PC - it works in powered on phone in android, but in recovery it doesn't it only sees sdcard as internal memory, if i try mount sd-ext shows error, can't mount.
Also i have problem if i use pc to copy some files to internal memory-phone switches storage mode OFF! and i can't copy files to internal 2GB memory..strange
For the past few days I seemed to be getting a lot of random force close errors on my legend, with no discernible pattern. This continued up to the point where all of a sudden pretty much every app crashed and wouldnt remain open more than a few seconds. I then tried to reboot, and since then the phone just gets stuck in a bootloop at the rom loading screen. I've tried four or five different roms, all with the same error.
I would assume this was a memory/processor malfunction, however the fact that I can still flash roms and make backups with clockwordmod suggests to me the hardware could be ok? Does anybody know of some sort of diagnostic rom I could run to check this?
Thanks guys
Matt
Here's some stuffs to check out, don't over clock, Max 600mhz, not every phone can be oc'd, maybe even try less processor speed say 480 MHz. Have u been ocing your phone on extream speed for long time, like 806+ mhz, that will kill a processor for sure.
Have you done a fix permissions with clockwork mod? This can help heaps with fc's.
If using an ext partition which type are you using 2 3 or 4, apparantly if your using ext4 and your phone is crashing it can cause even more issues.
Using lots if widgets on your screens?
Have you tried a different/new SD card?
My understanding is your rom space can eventually fail if your flashing lots n lots of roms, but you said you can flash successfully, so that sounds good.
There is a few to start you off.
Sent from my Legend using XDA
Amazingly I have managed to completely fix the problem. In a last moment of desperation before buying a new phone I decided to try wiping the battery stats, simply because I had never tried it before (didnt see the need to). Miraculously this did the trick, and I managed to boot into cyanogen 6!
I then restored a backup I made when the phone first died, and confirmed it was still broken as I expected. I then wiped the battery stats , and viola it worked!
I have no idea what is stored in the battery stats, but I am very surprised this made a difference. Thanks for your help anyway ranger.
Its been a long time since iv been this stumped, about a week ago my phone started acting very strangely, laggy performance, freezing randomly and occasionally rebooting itself, now its getting worse, getting to a point where the phone is probably rebooting itself 5-6 times a day, iv uninstalled every app, iv factory reset it, wiped cache, replaced battery, removed the SD card (in case of file system corruption) using Samsung Smart Switch did an emergency flash back to original Rom, installed every troubleshooting app out there, monitored RAM and CPU usage, all i can see is that the CPU suddenly spikes to 100% with no real reason, i cant link any particular app or process thats causing this, all of the cores on the processor appear to be coping with no faults.
The only thing i can think of thats causing this issue is either iv got a pending hardware failure on the board, or possibly bad blocks on the nand memory, however i cant see any simple way of determining this without rooting and using the likes of ODIN or other 3rd parties etc - linux commands etc.
I dont want to root it particularly if i can help it as i was thinking about selling it on to mazuma or the like and let them sort it out instead, but i think i might have to bite the bullet and try it.
Can anyone suggest anything that i might have missed?
Actually iv seen an existing thread which appears to match my issues, so iv installed wakelock on the phone for now which seems to be helping a bit, time will tell, however this isnt a solution but more of a work around, but im still thinking this could be a motherboard issue myself, however, as i think this phone is over 2 years old, i doubt samsung will replace the component, nor would they necessarily believe me if i turn around to them and say its the board that needs replacing!
Terry6680 said:
Its been a long time since iv been this stumped, about a week ago my phone started acting very strangely, laggy performance, freezing randomly and occasionally rebooting itself, now its getting worse, getting to a point where the phone is probably rebooting itself 5-6 times a day, iv uninstalled every app, iv factory reset it, wiped cache, replaced battery, removed the SD card (in case of file system corruption) using Samsung Smart Switch did an emergency flash back to original Rom, installed every troubleshooting app out there, monitored RAM and CPU usage, all i can see is that the CPU suddenly spikes to 100% with no real reason, i cant link any particular app or process thats causing this, all of the cores on the processor appear to be coping with no faults.
The only thing i can think of thats causing this issue is either iv got a pending hardware failure on the board, or possibly bad blocks on the nand memory, however i cant see any simple way of determining this without rooting and using the likes of ODIN or other 3rd parties etc - linux commands etc.
I dont want to root it particularly if i can help it as i was thinking about selling it on to mazuma or the like and let them sort it out instead, but i think i might have to bite the bullet and try it.
Can anyone suggest anything that i might have missed?
Click to expand...
Click to collapse
Deleted...