Occasional hot reboots. Suspect RAM and vibration. - Galaxy S III Q&A, Help & Troubleshooting

I have a problem with occasional hot reboots of my device.
Description of the device: international galaxy s3, omega Rom (from the day of purchase, now it's 33.3), siyah kernel (also from the very beginning, now it's 1.8), extsd2intsd mod. No OC or UV is required to replicate the problem.
Typical situation when it happens: I read news in flipboard, use touch translator to translate selected word, goldendic opens.I try to edit the word in the search bar of the dictionary (by pressing backspace), and at this moment device hot-reboots itself. Hot reboot also happened in other programs (one time I was also editing search bar when it happened, another time I tried to copy a text fragment).
I thought that Swype keyboard might be the cause. So I froze it in Titanium backup. However, reboot happened with Samsung keyboard.
It's important to mention that sometimes I can replicate the reboot (playing with flipboard and dictionary), but often device works perfectly despite my attempts to cause hot reboot.
Finally, the most important part: hot reboots do not happen when I have either V6 Supercharger or Bestmultitaskingfix working. That's why I think that it's a software problem. However, supercharger causes TW redrawals plus bad multitasking (at least the version which comes with omega Rom), and Bestmultitaskingfix causes lags on my device, so I don't find them to be a decent solution.
I tried to overload ram with opened apps, but nothing happened, old apps simply closed.
So, I think that the solution could be a bootable tweak which is used in both V6 Supercharger and BestMultitaskingFix. However, I'm not aware of the structure and tweaks used in these scripts. May be someone with experience in this area could suggest something?
I would like to hear your suggestions about the problem. Any ideas will be greatly appreciated!
Update: vibration is not the cause. Device rebooted even with tactile feedback turned off.

Make a nandroid backup, and flash stock rom + kernel and do a full wipe. Test it for a little while, and see if it persists.

xSpeced said:
Make a nandroid backup, and flash stock rom + kernel and do a full wipe. Test it for a little while, and see if it persists.
Click to expand...
Click to collapse
Flashed the stock firmware (ICS - I had nandroid backup), did full wipe. So far, no reboots were observed (intentionally played with flipboard and golden dictionary). Seems that it's a software problem. Still, I need to fix my omega rom somehow...

A clean flash for Omega might be a good idea.

Frequent random boots can be the beginning of "sudden death"... look for this thread in General section....

Related

How to uninstall the "minimized touchscreen bug" patch?

Hello, sorry for the lame question. I know, simple answer is "just re-flash it", but I would really appreciate another way advised to save the config and time.
I have lot of troubles after installing the subj. (http://forum.xda-developers.com/showthread.php?t=929941).
It's LG P500 running at 2.2 Froyo (stock, rooted, custom recovery):
- after applying the first version, battery management gone, access recovered by re-applying; but since then, scrolling became not so smooth as it was before; not a big problem, so I was waiting for next version;
- now, there is 1.1 version: applied that, but all the sounds individually matched to some contacts are gone, I can choose only standard sounds from /system/media, but not from /sdcard/media; tried to re-apply, get back to first version - no changes; get back to 1.1 - and now cannot choose those sounds in any system menu - for all the contacts, alerts etc etc.; but way more important, the I/O performance severely degraded, appearing as up to 10 second to open an app., which was never observed before; "SD tools" measuring shows degrading both R and W (~5 Mb/sec less now).
Is there standard stock 2.2 kernel available separetely, maybe switching back could solve these problems?
Thanks for any thought.
It's not a patch. It's a whole different zImage (kernel?). You may want to restore your backup. If you don't have one, I uploaded the stock 2.2 kernel. It's in the 2nd page of this subforum. Look for "unflash kernel".
I suggest u flash dev cavermans v3 kernel, I loved the response of it ever since I flashed it.
OK, thanks a lot for replies and links!
Yesterday, I re-installed a kernel, tried different versions... Unfortunately, something dramatically wrong with my phone.
With ringtones, it seems I ran into that problem:
http://forum.xda-developers.com/showthread.php?t=998520
- android does not aware of /whatever/media folder anymore.
With performance, it became a bit better after moving most of apps to SD card, but still unacceptable.
Probably, I have to re-flash the whole stuff

[Q] Noob help - Rooted desire keeps freezing.!

Morning guys - i'm a sort of noob (go easy.!) that needs help with my HTC desire. I took plunge and decided to try rooting & applying custom ROM, but now have problems with the screen freezing completely at any point, then on restart the phone boots into the home launcher but screen does not respond or will not wake.
So far:
Rooted with unrevoked
HBOOT flashed to Cm7r2
Latest version of clockworkmod recovery via app
Aurora 4.1 (all dalvik caches wiped at correct points).
V6 supercharger applied on setting 5 (balanced).
Tried with kernel built in ROM (0.7) & gingercakes 0.9cfs no2way havs.
SD card partitioned with GParted (fat32 primary, 2gb primary ext4).
I've had the ROM working fine, the only other thing i can place it to is swapping the SD card, which i've changed from 4gb class to, to a samsung 16gb class 6. Does anyone think that this error could be anyway caused by the fact the card readers i've used (tried 2 different readers) both have had trouble recognising the 16gb card?? (Gparted still recognised it however)
Is it possible to be a hardware issue? Please note recovery works perfectly - wiping caches, reinstalling zip files, backups etc.....only problem is now this freezing of home launcher and no response.
Any help be greatly appreciated, give me a nudge if i haven't given enough detail.
Regards, Nick.!
Additional:- Tried unsupercharging & rebooting - no difference.
Only other thing i can think that i've done prior to the fault is attempting to install busybox for V6 supercharger - which failed every time and affected my root access on the phone. I've found that the Aurora ROM has busybox installed already. However, is it possible me trying that install has somehow affected the rooting of the phone?
So many questions, sorry guys!
Bump.....would ADAO file manager (which isn't on google market I notice) affect anything on ext4 perhaps? That was one app that i downloaded from net.
Have you tried reverting your busybox to the default version? Also, are you overclocking and or overclocking? Going to high or to low with CPU speed can cause problems like that. It has also been said that partitioning an SD card can damage them, which may be an issue you have now. You could try formatting the SD card to its default state and run like that for a while. I ran a 16gb SD card in a Droid Eris for months and it never caused a problem like that. Of course, I didn't have a partition set up on it.
Sent from my ADR6350 using Tapatalk
I've literally left the settings for speed in daemon controller alone, although i'm still learning and not sure if they are default overclocked or not?
Possibility with the SD card, i'll give it a try for sure, that'd mean i'd have to revert to an alternate ROM would it, as Aurora specifies an ext4 partition?
Thanks again though, it's a start at least
Do you set profiles in SET CPU?
Accidentally sent from my Google Nexus S using XDA Premium
Excuse noobie brain here, where will i find those CPU settings?
If so, fully wipe and install again. And what rom are you using currently that causes freeze?
Accidentally sent from my Google Nexus S using XDA Premium
Aurora V4.1 ROM i'm using. Don't think it's the ROM itself as i have had it stable for week or so, before swapping SD card from 4gb to 16gb.
I'm thinking this may be the root cause as i've just tried a complete fresh partition with Gparted & fresh install of literally just the ROM itself and on first boot it froze again. Rebooted and now seems to be stable with nothing reloaded back on it but we'll wait and see. If it freezes again i'll try my 4gb card. Didn't want to revert back to that as its only class 2.
[Q] Noob help - Rooted desire keeps freezing.! Update...!
UPDATED - Still getting same problems - have now tried a different SD card & alternative ROM (Cool3d v5).
Is it possible it could be heat related fault? The more i use the phone the more readily it happens - from the occasional freeze (okay after reboot) to complete freeze and no response on every reboot.
Does the CPU therefore have a cut out or could be freezing based on the settings that are initially loaded through daemon controller? What are safe settings for the min/max values?
Only other thing i've noticed is once fault starts to occur - clearing dalvik cache in recovery is quite unresponsive - menu holds before allowing me to clear.
Got to get to the bottom of this - don't want to revert back to original, or throw my phone in the river!!
Save clock is 1ghz. No over clock is the safest.
Do your phone wear case? If yes, it may be the caused of heat.
I'm sure the rom caused you the freeze. You can try to change a more stabler rom, eg aosp
Accidentally sent from my Google Nexus S using XDA Premium
Bit more progress - as my phone literally would freeze on loading home launcher, i connected it to pc and mounted via recovery - and deleted everything i could see for V6 SUPERCHARGER - and hey presto, very slowly, but phone booted up and is now working again.
I see the devs of V6 say about removing hardtokill if any lags occur - i think it's this portion of the script affecting my bravo.
SO, i'm going to run it totally without V6, and may try to just run the memory portion, but the instructions to disable hardtokill are a little unclear to me, could you guys tell me in simple terms how to acheive??
Thanks again for all your responses, a great help
V6 now off and all fresh re-installed with cpu max turned down also, and set to ondemand gov, will see how we go
[Q] Noob help - Rooted desire keeps freezing.! PT3.!
Still no joy with this issue guys - pulling my hair out now - after a few hours use (usually overnight) phone just freezes, then freezes on reboot, before getting worse and now will not pass alpharev's boot screen.
Installing fresh gets me into home launcher, but becomes unresponsive and freezes again.
I've tried different ROM's, different SD's, basic clean install, all without any luck. I'm thinking now it is more a hardware issue with the phone?
nikh667 said:
basic clean install
Click to expand...
Click to collapse
Did you wipe data/cache partitions/dalvik cache before flashing the rom? Did you wipe dalvik cache and cache partitions after flashing the rom?
Yep all wiped before and after.
nikh667 said:
Yep all wiped before and after.
Click to expand...
Click to collapse
Have you tried flashing a new kernel?
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
nikh667 said:
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
Click to expand...
Click to collapse
Has your device went through any physical damage (around the time the problem started)?
No physical damage apart from the battery cover being pulled off more than once(!) and a lot of obscenities being flung it's way, lol! But no, not dropped or damaged at all.
I've used the phone now all afternoon, longer than normally, with the same details on same hboot, but left some of the sense widgets off the home launcher, and it hasn't locked up once.

Phone seems slow and unresponsive

So the other day i flashed a new ROM i forget which one (flashaholic)
Anyway when it loaded the initial setup enter gmail etc.
The screen started flickering then turned off it done this each time i turned the screen on
I rebooted it done the same again
After i eventually got it setup it stopped
I have since flashed several other roms Dual boot etc.
Some of these roms i have used before with no problems BUT
Now the roms seem to run fine for the better part but become unresponsive for a few seconds when installing apps from market
I use go backup and phone screen has turned of in the middle of restore several time with several roms and wont come back on unless i reboot
I have tried alternative backup restore apps with the same outcome
It seems my internal memory has suffered some sort of problem as these problems only seem to occur when the internal memory is being written to
For the record i use superwipe script before each rom install
Anyone else experience anything like this
The short "stuttering" when installing an app from Play Store also happens to me, but well not really a big deal.
Did you try to flash a stock rom and stock kernel to start with? In addition maybe a mega wipe would also help to format all partitions (except the important once of course).
I believe it is the megawipe script i am using the problem persists when apps are updating phone becomes unresponsive
It reminds me of my HD2 days when the system was installed on both the internal and external memory
chrismast said:
The short "stuttering" when installing an app from Play Store also happens to me, but well not really a big deal.
Likewise over the last few versions of JB #Especially on multiple installs .
Same on Note 10.1 so it looks like a Google problem .
jje
Click to expand...
Click to collapse

System freezes... a lot!

Hi,
Before creating this topic I tried to run some research but I haven't found anything useful that would explain my phones recent behavioural problems. The problem with my i9300 is that the phone freezes at random while Android is operating. This happens in settings, while apps get updated, when getting phone calls, when opening an app, when registering a google account (new setup), when opening SMS app... The sreen stops responding, none of the hardware keys do anything and all I can do is take out the battery. It's just crazy and does not seem to have any rules to this madness. The problem started after flashing a new version of Sentinelrom (and CMW supporting android 4.4.2 installations). This is what I already tried to troubleshoot/resolve:
- flashing another recovery (now on latest PhilzTouch)
- flashing other roms (UltimaAOSP Valhalla, latest CM11 nightly, CM10.2 stable, Slimkat ROM) with full wipes, dalvik cache cleanup etc.
- flashing boefla kernel (during Slimkat tests)
- formating \modem
- formatting externalSD (was and is on exFAT)
- taking out externalSD for a longer period
- restoring apps from google instead of titanium backup
- not restoring any apps and settings from google
- installing apps selectivly
Nothing helped although the phone was running most stable on UltimaAOSP Valhalla (3 freezes during one day). The freeze never happened during playing a movie or listening to music. The freeze never happened while in recovery mode.
Does anyone have any other suggestion on what I can do? Any input appreciated!
Maybe your device is affected of the Sudden Death Syndrome.
Try eMMC brickbug Check from Google Play.
mischa_martin said:
Maybe your device is affected of the Sudden Death Syndrome.
Try eMMC brickbug Check from Google Play.
Click to expand...
Click to collapse
Thanks for input. I run the check. The chip may be affected by sudden death, but all of the roms I've tested (now testing Android Revolution based on 4.3 stock - 3 freezes just today) have the fix implemented. Also I have had this phone for almost 2 years now. The internal memory check within this app also found no errors. So I guess it's not related to SDS.
Freezing is usually due to nand memory having bad blocks, read the freezing thread in general forum.
Sent from my GT-I9300 using Tapatalk

[Q&A] [ROM][Sep 25][4.4.4] I9100 AOSP NeatROM v8.0st

Q&A for [ROM][Sep 25][4.4.4] I9100 AOSP NeatROM v8.0st
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
security settings crushing, and all is sloww
Hi there all
I have flashed this ROM 2 days ago and found it very good and fast.
Today i have played with the security (lock screen & apps permissions), i have chooses the face recognition for the screen-lock and a default security for all new apps.
Now all is so slow and cannot get into the security settings, it is crushing !
Please help.
I do not want to factory reset, i have already restored all my contact and apps, do not have the time to do this again.
Thank you all
My huge thanks to the developers of this amazing ROM. I really appreciate your work. With Apolo Kernel works perfect! Thank you.
eli1967 said:
Hi there all
I have flashed this ROM 2 days ago and found it very good and fast.
Today i have played with the security (lock screen & apps permissions), i have chooses the face recognition for the screen-lock and a default security for all new apps.
Now all is so slow and cannot get into the security settings, it is crushing !
Please help.
I do not want to factory reset, i have already restored all my contact and apps, do not have the time to do this again.
Thank you all
Click to expand...
Click to collapse
Eli,
I've been using the v8st for over 20 days now and have not come across such an issue.
But I have a different issue though:
The bluetooth mic levels when connected to the car's audio system renders very low voice that the person on the other end can't hear me so good.
Hope someone with a similar issue like yours' should be able to help you soon!
gps always on
Hello, i recently use this rom and find that may gps is always on in my battery usage even if i already turn off the location setting, how can i turn off my gps? Before this i found that my wifi also always on but i can turn it off by going to setting-->wifi-->advanced-->keep wifi and set always on when sleep to never, is there also settings like this for gps? Thankyou
Hi
Even by doing as per Post# 4, Wallpaper gets replaced but does not work.
Going by wallpaper details found MD5 error.
Few more issues on my device, new to this ROM. Flashed 2 days back.
1. How to increase the FONT & ICON size in Status bar, Key board letters are too small, notifications are small.
2. Screen and around the camera gets heated, during this time battery drains super fast.
3. BBS is not working, error message "Battery service could not be contacted"
Please help me with the above issues.
Thanks in advance
Sent from my GT-I9100 using Tapatalk 2
sunnyhot said:
Hi
Even by doing as per Post# 4, Wallpaper gets replaced but does not work.
Going by wallpaper details found MD5 error.
Click to expand...
Click to collapse
What post #4 are you talking about? What does not work? What gives you an MD5-error. Please be more specific.
sunnyhot said:
1. How to increase the FONT & ICON size in Status bar, Key board letters are too small, notifications are small.
Click to expand...
Click to collapse
You need to change the display density setting. Open the file /system/build.prop with a text editor and search for the line ro.sf.lcd_density=182. Change the value to something else. Bigger numbers give you bigger icons and fonts. The Default for SGS2 Roms is normally 240, Neatrom uses 182, that's why everything is smaller than on most roms. If you want to use 240, you can also flash this ZIP in Recovery: View attachment Density_240_v8.0st.zip. It's just a modified build.prop for 8.0st. There are also apps on the PlayStore that can change the density for you, but I never tried them.
sunnyhot said:
2. Screen and around the camera gets heated, during this time battery drains super fast.
Click to expand...
Click to collapse
Without more info it's impossibe to know what is draining your battery. You need to find out the app that gives you trouble with BBS or similar app.
sunnyhot said:
3. BBS is not working, error message "Battery service could not be contacted"
Click to expand...
Click to collapse
In Android KitKat, user apps are not allowed to access battery stats. It's part of Androids security policy. There's two ways to fix it:
Get Xposed Installer and install the Xposed Framework. Then, download the module Enable BatteryStats Permission - voila! Since Xposed is simply awesome for other tasks as well, I recommend this method.
If for some reason you don't want to use Xposed (e.g. if you use ART), then you have to convert BBS to a system app. There's several ways to do so, like Titanium Backup or Link2SD... However make sure that BBS gets installed in /system/priv-app/, and not in /system/app/, or else it will still not get the necessary rights.
Hi is there a way to reboot into recovery except from the home + volume + wake and also which Version of Apolo is the right one 7.1 CM?
Battery life?
Hi guys, was checking this rom out and it looks awesome!
How's the battery life though?
I'm currently on Resurrection Remix and the battery life when I have wifi on is really poor.
I'm basically looking for a 4.4.4 rom that gives maximum battery life.
Also are there any kernel recommendations?
Thanks!
Weird battery behaviour
Hello Guys. I met a very strange issue.
After flashed the ROM, the battery indicator acts very weird.
When the phone is fully charged, and I remove the charger. after reached 85%, and when the battery is gong down, the indicator is going up from 85% to 90 %.
Anybody met this ? and how to resolve ?
I already calibrated the battery, but the problem still on.
Click to expand...
Click to collapse
Try another batterry. I was facing the problem with an almost dead battery. With another one it's fixed.
---------- Post added at 01:39 PM ---------- Previous post was at 01:25 PM ----------
phirey said:
Hi guys, was checking this rom out and it looks awesome!
How's the battery life though?
I'm currently on Resurrection Remix and the battery life when I have wifi on is really poor.
I'm basically looking for a 4.4.4 rom that gives maximum battery life.
Also are there any kernel recommendations?
Thanks!
Click to expand...
Click to collapse
I'm running this with Apolo V0 kernel and I'm satisfied (on original Samsung 2000 mAh battery):
~33% a day of normal usage
~1% an hour idle (data on, sync on, location on)
~0.3% an hour night mode (data off, sync off, phone online) - translates to ~14 days of runtime
Have tweaked wakelocks/services.
---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------
txx3 said:
Hi is there a way to reboot into recovery except from the home + volume + wake and also which Version of Apolo is the right one 7.1 CM?
Click to expand...
Click to collapse
1. You can configure advanced power options to be able to reboot into recovery from a running ROM
2. Yes CM is the right Apolo for NeatROM (having superuser integrated)
Having troubles with wifi connection since this morning... My S3 and laptop works just fine but with s2 cant connect to apps like viber, whatsapp or hayday
DELETED
Today formatted extsdcard to FAT32, still I see media scanner issue.
What could be the problem? Pls help guys
Sent from my GT-I9100 using Tapatalk 2
sunnyhot said:
Today formatted extsdcard to FAT32, still I see media scanner issue.
What could be the problem? Pls help guys
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I had the same problem of battery drain because of mediascanner service running all the time and i didnt know the exact fix but i have read somewhere that formatting sd card would help fix this and it did, Anyway i didnt use much of my extSD so i removed it for now!! And no battery drain observed with mediascanner service
I can't get this to run on my phone. After carefully following the instructions my phone is stuck on the first boot screen with the yellow exclamation mark. Strangely it seems like I have TWRP installed which I can't get rid of. Even after installing the CWM linked to, the next time I manually enter recovery TWRP opens.
Update: Sucessfully installed a Cyanogen based ROM instead. Shame, I would have liked to try this one.
GAPPS not working?
Hi there, please help me. I can't get gapps to work/install. I first flashed beta version...nothing, then tried the stable version and only Chrome appeared in appdrawer. I still can't access play store (from the Nova Launcher menu option), the browser that came with the NeatRom doesn't start.
The rooting, flashing of the rROM etc all went well, according to the instructions, the only thing was that I couldn't format /preload as there was no such option in the CWM recovery. Could that be the problem maybe?
Please tell me, what am I missing here...
jokl81 said:
Hi there, please help me. I can't get gapps to work/install. I first flashed beta version...nothing, then tried the stable version and only Chrome appeared in appdrawer. I still can't access play store (from the Nova Launcher menu option), the browser that came with the NeatRom doesn't start.
The rooting, flashing of the rROM etc all went well, according to the instructions, the only thing was that I couldn't format /preload as there was no such option in the CWM recovery. Could that be the problem maybe?
Please tell me, what am I missing here...
Click to expand...
Click to collapse
No, Preload is not used in AOPS Roms, only at Sammy ROMs.
maybe your download of GAPPS or ROM is corrupted, check the MD5 file to see if there is any thing wroing.
Clear Cache from Recovery
Try to reboot
Try to re-install.
Somtimes something goes wrong and then you have effects as you mentioned.
GeScha said:
No, Preload is not used in AOPS Roms, only at Sammy ROMs.
maybe your download of GAPPS or ROM is corrupted, check the MD5 file to see if there is any thing wroing.
Clear Cache from Recovery
Try to reboot
Try to re-install.
Somtimes something goes wrong and then you have effects as you mentioned.
Click to expand...
Click to collapse
Sorry, but I gave up over AOSP and flashed the "stock" NeatRom 6.4 w/o any problems. Runs great!
Still, when I was searching for a solution, I found out, that it is possible that I didn't make a nandroid backup of /preload (when I was still on rooted stock samsung ROM - before flashing kitkat cwm and later AOSP NeatRom). I read that in the CWM recovery that comes with Siyah kernel - which I used to make a nandroid backup - you have to manually select to make a backup of the /preload part. in addition to all others... And i really didn't find a file with "preload" in the nandroid backup folder that I copied to my PC. If so, I am suppose to have trouble when/if going back to stock samsung ROM? If that is the case, maybe it would be good to update the guide for flashing the KitKat-based AOSP NeatRom. I don't really care right now, because I really like the stock NeatRom...I just hope it'll work...
NeatRom 8.0st and TWRP - no restore possible
Hi all,
hope, one of you will be able to support me ?
I'm not able to restore any of my TWRP backups done with TWRP 2.7.1.0 which came with the ROM.
All backups went well and were flagged as 'successfully'.
However, trying to restore one of them failes every time. It looks like after restoring SYSTEM and starting with DATA, it stucks.
One 'failed', no error code or any additional information.
I've a 32 GB SD installed on my i9100 and this is where I store all the TWRP backups.
Copying them to internal storage does not help.
Any ideas ?
Thx in advance,
BR,
This is a good room

Categories

Resources