My sgw restarts automatically for 2 or 3 sec. And sometimes after restarts it shows at far down left (safe mode)... So
Whats happening? is it a hardware problem?
Sent from my GT-I8150 using xda premium
mohza said:
My sgw restarts automatically for 2 or 3 sec. And sometimes after restarts it shows at far down left (safe mode)... So
Whats happening? is it a hardware problem?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Stock ROM or customed ?
Stock rom , then phone works normally but restarts after 2 or 3 days for example
Sent from my GT-I8150 using xda premium
I have this problem too. This happened with black notes and cow v7. However, it is less frequent now.
If it's stock rom, you could have it check to your nearest samsung service center.
i.am from indonesia and after upgrade stock rom I8150DXLC1 in march 30th i have this isue too, what happen with this room?
we can't go to samsung because there is no proove .. this is happen any time some times 2 or 3 times rebooting still cant go to normal mode, and i must pull out battery or quicly press power button to shut down then press power again to have a normaly boot, for info i use a Apach*r sdhc 8GB class 10 any problem with that maybe ?
btw sorry for my bad english
artfelin1 said:
i.am from indonesia and after upgrade stock rom I8150DXLC1 in march 30th i have this isue too, what happen with this room?
we can't go to samsung because there is no proove .. this is happen any time some times 2 or 3 times rebooting still cant go to normal mode, and i must pull out battery or quicly press power button to shut down then press power again to have a normaly boot, for info i use a Apach*r sdhc 8GB class 10 any problem with that maybe ?
btw sorry for my bad english
Click to expand...
Click to collapse
Try to re-flash the ROM again. Use CWM to wipe data and cache then use ODIN to flash the Stock ROM again.
I too am suffering from random restarts. I am running stock rom unrooted
PDA: I8150TDULA4
PHONE: I8150TDULA2
CSC: I8150TVAULA1
I have tired wiping the cache, reformatting the external SD card, doing a factory reset, no luck to all. Depending on phone usage will depend on how many restarts I get per day.
I have even tried to capture the logs with alogrec to see if I could find the culprit, but it doesn't seem to point to anything specific, the only error I seem to get (from my review of the logs) just before the restart is:
"W/dalvikvm(17668): threadid=20: thread exiting with uncaught exception (group=0x4001e578)"
I was hoping to reflash the ROM, but can't locate the ROM anywhere, was wondering if anyone had a copy?
Any help with the ROM or suggestions would be appreciated.
Thanks
On my device, it was a ram problem, when i played with the last three switches in a ram manager (hidden, content, empty) the cycles between a reboot changed. Found the most stable settings with adjusting the switches like a staircase, every ram-switch as minimal as possible.
Delmare said:
On my device, it was a ram problem, when i played with the last three switches in a ram manager (hidden, content, empty) the cycles between a reboot changed. Found the most stable settings with adjusting the switches like a staircase, every ram-switch as minimal as possible.
Click to expand...
Click to collapse
Hmmm one shouldn't have to mess around with ram manager. I hope someone has a copy of the latest VAU firmware so I can reflash the phone to rule that out.
Try here for march 2012 Indonesian Rom
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I8150&r=2#regiona
andyvbrown said:
I too am suffering from random restarts. I am running stock rom unrooted
PDA: I8150TDULA4
PHONE: I8150TDULA2
CSC: I8150TVAULA1
I have tired wiping the cache, reformatting the external SD card, doing a factory reset, no luck to all. Depending on phone usage will depend on how many restarts I get per day.
I have even tried to capture the logs with alogrec to see if I could find the culprit, but it doesn't seem to point to anything specific, the only error I seem to get (from my review of the logs) just before the restart is:
"W/dalvikvm(17668): threadid=20: thread exiting with uncaught exception (group=0x4001e578)"
I was hoping to reflash the ROM, but can't locate the ROM anywhere, was wondering if anyone had a copy?
Any help with the ROM or suggestions would be appreciated.
Thanks
Click to expand...
Click to collapse
Ultimate BackUp free [from JRummy] has a fix permissions option.....
this may sort out your random re-boots.
But, you need Root to use this....have you rooted, or do you want to?
It [rooting] can be done from Stock Recovery....check THE-E posts/tutorials.
irishpancake said:
Ultimate BackUp free [from JRummy] has a fix permissions option.....
this may sort out your random re-boots.
But, you need Root to use this....have you rooted, or do you want to?
It [rooting] can be done from Stock Recovery....check THE-E posts/tutorials.
Click to expand...
Click to collapse
Phone is currently unrooted, but am considering rooting it.
I don't think this is a permissions isuue. I'm curious to understand why you think it is?
thanks
andyvbrown said:
Phone is currently unrooted, but am considering rooting it.
I don't think this is a permissions isuue. I'm curious to understand why you think it is?
thanks
Click to expand...
Click to collapse
No particular reason specific to your device...
it is just one of those routine Android fix things, which don't hurt, but are recommended to sort out FC issues, and random re-boots.....
Here is Cyanogen's little write-up on fix permissions
It may not fix your problem, but it just may!!!
And if it does, great......but if it doesn't nothing lost, and another thing done!!
In your position, I would give it a try, either from CWM or with the App I recommended, which can do lot's more, even for free, like zipalign, and full back-up and restore Apps, cache clean, etc.
Rooting guide from THE-E....recommended via Stock Recovery!!
irishpancake said:
No particular reason specific to your device...
it is just one of those routine Android fix things, which don't hurt, but are recommended to sort out FC issues, and random re-boots.....
Here is Cyanogen's little write-up on fix permissions
It may not fix your problem, but it just may!!!
And if it does, great......but if it doesn't nothing lost, and another thing done!!
In your position, I would give it a try, either from CWM or with the App I recommended, which can do lot's more, even for free, like zipalign, and full back-up and restore Apps, cache clean, etc.
Rooting guide from THE-E....recommended via Stock Recovery!!
Click to expand...
Click to collapse
Irishpancake,
Thanks for the information, I'll look into these and give them a try. Still hopeful that someone has the ROM....
Cheers
---------- Post added at 07:27 AM ---------- Previous post was at 07:22 AM ----------
Also further errors related to my restarts from the phone logs shows:
D/LockscreenWallpaperUpdater(30999): onResume()
D/LockscreenWallpaperUpdater(30999): get drawable (public)
D/LockscreenWallpaperUpdater(30999): get drawable (keygurardupdatemonitor private get)
D/LockscreenWallpaperUpdater(30999): drawable is null(keygurardupdatemonitor private get)
D/LockscreenWallpaperUpdater(30999): set drawable
D/LockscreenWallpaperUpdater(30999): wallpaper file exist
D/dalvikvm(30999): GC_EXTERNAL_ALLOC freed 89K, 34% free 9177K/13703K, external 51441K/51717K, paused 76ms
E/dalvikvm-heap(30999): 768000-byte external allocation too large for this process.
E/GraphicsJNI(30999): VM won't let us allocate 768000 bytes
D/dalvikvm(30999): GC_FOR_MALLOC freed 0K, 34% free 9177K/13703K, external 51441K/51717K, paused 68ms
D/skia (30999): --- decoder->decode returned false
W/dalvikvm(30999): threadid=21: thread exiting with uncaught exception (group=0x4001e578)
D/GLSurfaceViewGroup( 6251): Skipped drawing due to suspendDrawingUntilResume()
E/ (30999): Dumpstate > /data/log/dumpstate_sys_error
E/AndroidRuntime(30999): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy
E/AndroidRuntime(30999): java.lang.OutOfMemoryError: bitmap size exceeds VM budget
andyvbrown said:
I too am suffering from random restarts. I am running stock rom unrooted
PDA: I8150TDULA4
PHONE: I8150TDULA2
CSC: I8150TVAULA1
I have tired wiping the cache, reformatting the external SD card, doing a factory reset, no luck to all. Depending on phone usage will depend on how many restarts I get per day.
I have even tried to capture the logs with alogrec to see if I could find the culprit, but it doesn't seem to point to anything specific, the only error I seem to get (from my review of the logs) just before the restart is:
"W/dalvikvm(17668): threadid=20: thread exiting with uncaught exception (group=0x4001e578)"
I was hoping to reflash the ROM, but can't locate the ROM anywhere, was wondering if anyone had a copy?
Any help with the ROM or suggestions would be appreciated.
Thanks
Click to expand...
Click to collapse
Download
I8150TDULA4 / 2.3.6 / January 2012 / I8150TVAULA1 / Australia (Vodafone)
I got the same problem! I'm in Indonesia too. Is that because the Rom?
same here
Hi ,
We have 2 of these in our family , both on 2.3.6 stock (UK latest version) updated by Kies , can restart twice a day or once a week - very puzzling have asked samsung and I am waiting a reply
cheers
Dear Users...this happened to me also after flashing Rebel Rom Milestone 2...i got random reboots after normal usage of about 120+ hours...i flashed XXLM8 with Odin in order to get rid of this problem...but no luck...finally i fixed permissions from CWM recovery...then as far as i know...it didnt reboot...i saw my running apps for about many many hours without any restarting of timer..i also switched to other xxlm8 based custom ROM (FAW Rls 2) but just didnt notice rebooting again...only now my phone stucks and reboots when i play hd games continuously.... that's because of Ram shortage...i advise to install only Roms without bugs...and make wipe of everything before flashing...and fixing permissions after switching to a new ROM...also clearing RAM once before playing games...Good Luck!
Sent from my GT-I8150
I experienced this issue too when I firstly bought the phone. Did you update it to the latest version? The problem is fixed for me after updating the update before value pack (sorry I forgot its name).
Hope it helps and sorry for my bad English
Related
I have created this thread as the "Hyperion 7.x | Pre GM" is temporarily closed.
I have successfully flashed the "Hyperion 7.x | Pre GM".. It works 10-15 min & then goes back to boot logo... Same problem happened with me on flashing previous version of this ROM... I doesn't face any problem while flashing other ROMs. Followed the instructions carefully.. Please help me to solve this problem...
ajay131 said:
I have created this thread as the "Hyperion 7.x | Pre GM" is temporarily closed.
I have successfully flashed the "Hyperion 7.x | Pre GM".. It works 10-15 min & then goes back to boot logo... Same problem happened with me on flashing previous version of this ROM... I doesn't face any problem while flashing other ROMs. Followed the instructions carefully.. Please help me to solve this problem...
Click to expand...
Click to collapse
which kernel are u using???
which stock rom u used when u flashed hyperion??
what steps did u take to flash hyperion detail??
ajay131 said:
I have created this thread as the "Hyperion 7.x | Pre GM" is temporarily closed.
I have successfully flashed the "Hyperion 7.x | Pre GM".. It works 10-15 min & then goes back to boot logo... Same problem happened with me on flashing previous version of this ROM... I doesn't face any problem while flashing other ROMs. Followed the instructions carefully.. Please help me to solve this problem...
Click to expand...
Click to collapse
This is because of undervolting
You can try one of these
1. If you don't need undervolting, then
1. Using root explorer go to /etc /init.d
2. There will be either one of the two files:
--> 00undervolt or
--> bacem_tweak
Just delete it if any of these is present..
Click to expand...
Click to collapse
I think hyperion has 00undervolt script..
bacem_tweak was in jelly blaat but I am not sure about it
2. If you want to use undervolting then
1. Using root explorer go to etc/init.d
2. Search for the mentioned files
3. Open with text viewer
4. Change undervolt vaue.. eg if it is -120mv, change it to -100mv or lower
Click to expand...
Click to collapse
Hi,
Please try to re-flash Hyperion and do not restore any backup be it titanium backup or cwm backup as it may restore corrupted files. The description of the problem may have one or more cause which as of now isn't clear yet.
Make sure your sd card's 2nd partition is clean as by experience, an un-cleaned 2nd partition may cause problems or boot loop.
I can't say that there's no problem with Hyperion but we tested it several times before release without getting the problem you are reporting.
If you are getting system reboot, this *maybe* caused by kernel panic, it is a situation where the system gets loaded and the only way to avoid lockups is to force the system to reboot.
In most cases, background services/applications may remain in the memory (specially root apps) as they are given high priority and can be locked in the memory. Previous builds of Hyperion has kernel panic tweak adapted from zeps scripts but it works desirable only in stabke kernels. Sadly, the tweak causes some minor problems so it was removed in 7.x.
Here's what you can do, investigate on your device/apps and see how much memory each app takes and how much background services you have (using devtools).
Also, reducing startup applications (using autostarts) will help in decreasing unnecessary system load.
Some quick and handy troubleshooting that you may try:
1. Reflash the rom
2. Reformat the 2nd partition of your SD Card
NOTE:
I/We/DevTeam cannot guarrantee that your phone will perfom as expected (based on our test) if you are using other tweaks and/or kernel.
CarlDeanCatabay said:
Hi,
Please try to re-flash Hyperion and do not restore any backup be it titanium backup or cwm backup as it may restore corrupted files. The description of the problem may have one or more cause which as of now isn't clear yet.
Make sure your sd card's 2nd partition is clean as by experience, an un-cleaned 2nd partition may cause problems or boot loop.
I can't say that there's no problem with Hyperion but we tested it several times before release without getting the problem you are reporting.
If you are getting system reboot, this *maybe* caused by kernel panic, it is a situation where the system gets loaded and the only way to avoid lockups is to force the system to reboot.
In most cases, background services/applications may remain in the memory (specially root apps) as they are given high priority
*taking a break* will come back after a while
Click to expand...
Click to collapse
hey carl
i need some help !!i ve flashed hyperion 7 GM final and fixed my wifi ,data connection problem from your dev section OP !!my wifi is connected but can't browse any thing !!data connection is fine but wifi is connected but no browsing !!!i am using white kernel 1.3.3 with wifi drivers!any suggestions to solve it???
percy215 said:
hey carl
i need some help !!i ve flashed hyperion 7 GM final and fixed my wifi ,data connection problem from your dev section OP !!my wifi is connected but can't browse any thing !!data connection is fine but wifi is connected but no browsing !!!i am using white kernel 1.3.3 with wifi drivers!any suggestions to solve it???
Click to expand...
Click to collapse
It is either the wifi driver from WhiteXP's Kernel or the mother of all host file in Hyperion 7 GM that's causing the problem.
NOTE:
Drivers are the bridge between your Wireless NIC and the system itself, it there is something wrong with the driver, we cannot expect the device (your phone) to behave as we would expect.
You can:
Re-download (to make sure files are intact) and re-install (to make sure drivers are properly installed) the wifi driver
Modify your hosts file and/or remove NetForks tweak. Instructions are posted in Hyperion's Thread in Wireless and Network Troubleshooting.
CarlDeanCatabay said:
It is either the wifi driver from WhiteXP's Kernel or the mother of all host file in Hyperion 7 GM that's causing the problem.
NOTE:
Drivers are the bridge between your Wireless NIC and the system itself, it there is something wrong with the driver, we cannot expect the device (your phone) to behave as we would expect.
You can:
Re-download (to make sure files are intact) and re-install (to make sure drivers are properly installed) the wifi driver
Modify your hosts file and/or remove NetForks tweak. Instructions are posted in Hyperion's Thread in Wireless and Network Troubleshooting.
Click to expand...
Click to collapse
Thnx for info I will try reflashing it and use another kernel!
Sent from my GT-S5360 using xda premium
@percy bro: i flashed this on my rooted stock rom. No any other kernel or tweak..
@khazir amin sir: as per ur instruction, change undervolt value to 100.. No problem till last half N hour... If any, will update the comment..
@carlDeanCatabay sir: thanx for the valuable info... Since long time wanted to try this rom... But same problem occured with each version...
Thanx to all you guys... To help me..
Sent from my Brain...
CarlDeanCatabay said:
Hi,
Please try to re-flash Hyperion and do not restore any backup be it titanium backup or cwm backup as it may restore corrupted files. The description of the problem may have one or more cause which as of now isn't clear yet.
Make sure your sd card's 2nd partition is clean as by experience, an un-cleaned 2nd partition may cause problems or boot loop.
I can't say that there's no problem with Hyperion but we tested it several times before release without getting the problem you are reporting.
If you are getting system reboot, this *maybe* caused by kernel panic, it is a situation where the system gets loaded and the only way to avoid lockups is to force the system to reboot.
In most cases, background services/applications may remain in the memory (specially root apps) as they are given high priority and can be locked in the memory. Previous builds of Hyperion has kernel panic tweak adapted from zeps scripts but it works desirable only in stabke kernels. Sadly, the tweak causes some minor problems so it was removed in 7.x.
Here's what you can do, investigate on your device/apps and see how much memory each app takes and how much background services you have (using devtools).
Also, reducing startup applications (using autostarts) will help in decreasing unnecessary system load.
Some quick and handy troubleshooting that you may try:
1. Reflash the rom
2. Reformat the 2nd partition of your SD Card
NOTE:
I/We/DevTeam cannot guarrantee that your phone will perfom as expected (based on our test) if you are using other tweaks and/or kernel.
Click to expand...
Click to collapse
well the reboot problem in my case was due to -120mV undervolting which is pre included in the rom..
and probably this is the same case here..
so please reduce the undervolt value to -100 etc
Changed the value to 100.. Worked well. But when i connect charger. It again restarted... So i deleted the 000undeevolt or whatever that file is.. N working good now.. No restart even on charging...
Thanx again Amin sir for the help...
Sent from my Brain
I'm glad I never had those problems coming from stock rom! Been using Hyperion 7 for quite sometime now and I can say that it's stable and responsively fast. I just hope that the development of Hyperion will be back. :waves at Carl
Sent from my GT-S5360 using Xparent Cyan Tapatalk 2
HYPERION 8 and HYPERION 7.. auto restard PROBLEM!!!
Sir Catabay can you help me fix auto restart problem on SAMSUNG GALAXY Y. At first i thought that it was battery problem cuz my battery got overcharge. then i buy a new one. it was ok until it happen again.. From Hyperion 8 i change ROM cuz i thnk that the rom wasnt compatible so i tried the Hyperion 7.. yet still it happens again..T_T i dont know what to do now.. i ended up erasing apps and formatting my sd card.:crying:
same problem
I had the same problem but now I'm using creeds rom 3.5 and it's stable
This is a banned rom..
Threads related to banned rom are not allowed on xda..
@Lady Android
Sent from my GT-S5360 using Tapatalk 2
sanny5 said:
This is a banned rom..
Threads related to banned rom are not allowed on xda..
@Lady Android
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
hi sanny,
i appreciate your report but i mods have warned before not to use the quote function since the report button is there
anyways,
banned roms and their discussions are not allowed on xda
Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!
i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion
Needs a trip to the Service Centre then by the sounds of it.
XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
logs?
poodleDoo said:
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
Click to expand...
Click to collapse
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
I would use ODIN or KYES to flash it back to OEM stock firmware. Also remove the micro SD card if you have one in there, sometimes corrupt cards can cause boot loop.
true
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
sharing
poodleDoo said:
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
Click to expand...
Click to collapse
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
dsilx said:
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
Click to expand...
Click to collapse
The tablet did the same without the sdcard, and I tried a couple times to do a factory reset with no luck.
The fact that it does the same with a different ROM and kernel is what makes me think it's hardware related
moonbutt74 said:
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
Click to expand...
Click to collapse
Cool, i'll get syslog installed and see if I can find anything.
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
awesome
poodleDoo said:
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
Click to expand...
Click to collapse
Awesome to hear sounds like @moonbutt74 was right
Hope it keeps working have fun
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
cool
poodleDoo said:
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
Click to expand...
Click to collapse
Well that sucks u have to have battery saver on all the time but at least its working now
hmmm
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
moonbutt74 said:
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
Click to expand...
Click to collapse
I'm running rooted deodexed stock ROM with Blackhawk 2.1 kernel.
But as I mentioned in the OP, the problem was there with the full stock device, the new ROM and kernel were installed after the problem started.
ouch
i think you pegged it right with internal storage being damaged.
only thing i can think of besides getting your money back is do a full data partition wipe and format
and a full system wipe and format
either way that has to suck. sorry i couldn't help.
m
Hi everyone!
It is a couple of months that I am having a big issue with my note 2 (N7100). I have continuous SOD. It happens more times a day, especially in the morning when I leave my phone charging all night long.
This issue appeared the first time with an unstable DN4 version (a lot of users had SOD), but after that also with other kind of roms (stock 4.4.2, CM12 based and AOSP roms).
Can anyone help me in finding a fix for such an issue?
Some additional information:
If I receive a message or if the phone is completely charged the notification led is on but the screen does not turn on, if someone calls me the phone does not rings and there is no way for me to know that I received such a call...
Please find attached last_kmsg extracted after last SOD this morning (I can't read it).
Thanks everyone for the support.
Edit: attached the log files of this mornging SOD. Can someone help me?
dicoale said:
Hi everyone!
It is a couple of months that I am having a big issue with my note 2 (N7100). I have continuous SOD. It happens more times a day, especially in the morning when I leave my phone charging all night long.
This issue appeared the first time with an unstable DN4 version (a lot of users had SOD), but after that also with other kind of roms (stock 4.4.2, CM12 based and AOSP roms).
Can anyone help me in finding a fix for such an issue?
Some additional information:
If I receive a message or if the phone is completely charged the notification led is on but the screen does not turn on, if someone calls me the phone does not rings and there is no way for me to know that I received such a call...
Please find attached last_kmsg extracted after last SOD this morning (I can't read it).
Thanks everyone for the support.
Edit: attached the log files of this mornging SOD. Can someone help me?
Click to expand...
Click to collapse
Wipe data and try to flash with odin from pc stock firmware to see what is happening. Before flashing if you want to be sure that everything is cleaned do this:
put out if you have external SD and go to your recovery and format system, cache, data, dalvik and your internal SD, reboot from your recovery to download (if your recovery ask you for reroot say no) and flash the stock fw.
Notice if your emmc has problem maybe you can't flash with odin and also revive your phone. It is your decision.
Send from my phone
vagsvag said:
Wipe data and try to flash with odin from pc stock firmware to see what is happening. Before flashing if you want to be sure that everything is cleaned do this:
put out if you have external SD and go to your recovery and format system, cache, data, dalvik and your internal SD, reboot from your recovery to download (if your recovery ask you for reroot say no) and flash the stock fw.
Notice if your emmc has problem maybe you can't flash with odin and also revive your phone. It is your decision.
Send from my phone
Click to expand...
Click to collapse
Thank you for your support!
Unfortunately I have thus kind of issue also with stock roms.
I did exactly what you said but sods were always there.
Did you gave a look to my logs? Any comments about?
Sent from my SM-N910C using XDA Free mobile app
dicoale said:
Thank you for your support!
Unfortunately I have thus kind of issue also with stock roms.
I did exactly what you said but sods were always there.
Did you gave a look to my logs? Any comments about?
Sent from my SM-N910C using XDA Free mobile app
Click to expand...
Click to collapse
Try to communicate with user psndna88 who is cooking agni kernel for n7100 and ask him to take a look.
Send from my phone
I tried factory reset, removed the memory card, no joy. It does it with battery in any charge state including fully charged. It stays on long enough to check a few things, but since it doesn't reboot while in recovery mode, it seems there is a problem in the software. Running Android 10. Any ideas?
Does it do it in safe mode?
If not it's a 3rd party app.
Stock launcher, right?
By watching running services you might see the cause list before it reboots.
Otherwise reflash it; possibly corrupted or bad firmware.
Use known good rom.
blackhawk said:
Does it do it in safe mode?
If not it's a 3rd party app.
Stock launcher, right?
By watching running services you might see the cause list before it reboots.
Otherwise reflash it; possibly corrupted or bad firmware.
Use known good rom.
Click to expand...
Click to collapse
Yes, it does it in safe mode as well.
Yes, everything is stock.
Sorry, I'm a noob, so I don't know how to watch the running services.
I will try a reflash. Any suggestions on where to find a good rom? Does it have to be a samsung rom?
Thanks!!
lapsmith said:
Yes, it does it in safe mode as well.
Yes, everything is stock.
Sorry, I'm a noob, so I don't know how to watch the running services.
I will try a reflash. Any suggestions on where to find a good rom? Does it have to be a samsung rom?
Thanks!!
Click to expand...
Click to collapse
Developer options>running services
Try clearing the system cache.
Doesn't have to be the stock rom but it would make troubleshooting easier probably.
A Samsung Experience Center at Best Buys can also run advanced diagnostics on it and reflash it.
blackhawk said:
Developer options>running services
Try clearing the system cache.
Doesn't have to be the stock rom but it would make troubleshooting easier probably.
A Samsung Experience Center at Best Buys can also run advanced diagnostics on it and reflash it.
Click to expand...
Click to collapse
Running services shows that the settings app is using 160M of ram on average out of about 1.5G. Everything else is much lower.. i think bc the phone is working on updates after factory reset.. It stays around that level and then the phone freezes before rebooting. It is always 1min 48 seconds.
I would love to try replacing the stock rom. Is that available from Samsung perhaps? If all else fails I will check with best buy...good to know! Thanks again.
lapsmith said:
Running services shows that the settings app is using 160M of ram on average out of about 1.5G. Everything else is much lower.. i think bc the phone is working on updates after factory reset.. It stays around that level and then the phone freezes before rebooting. It is always 1min 48 seconds.
I would love to try replacing the stock rom. Is that available from Samsung perhaps? If all else fails I will check with best buy...good to know! Thanks again.
Click to expand...
Click to collapse
Oh and clearing the cache didn't help.
lapsmith said:
Running services shows that the settings app is using 160M of ram on average out of about 1.5G. Everything else is much lower.. i think bc the phone is working on updates after factory reset.. It stays around that level and then the phone freezes before rebooting. It is always 1min 48 seconds.
I would love to try replacing the stock rom. Is that available from Samsung perhaps? If all else fails I will check with best buy...good to know! Thanks again.
Click to expand...
Click to collapse
Disable updates. Try disabling the internet at start up... see if that helps.
blackhawk said:
Disable updates. Try disabling the internet at start up... see if that helps.
Click to expand...
Click to collapse
Ok will try that when I get home and let you know.
lapsmith said:
Ok will try that when I get home and let you know.
Click to expand...
Click to collapse
Tried disabling internet at startup so no updates and same issue. Then tried just leaving it at the let's get started screen and still reboots. I'm guessing reflashing is next. I found instructions on youtube, do you suggest using Odin3? Also do you know of a safe place to download the stock rom? If not I guess another rom will suffice.
lapsmith said:
Tried disabling internet at startup so no updates and same issue. Then tried just leaving it at the let's get started screen and still reboots. I'm guessing reflashing is next. I found instructions on youtube, do you suggest using Odin3? Also do you know of a safe place to download the stock rom? If not I guess another rom will suffice.
Click to expand...
Click to collapse
I never had to reflash any of my phones. I'm far from the ideal mentor for how to do a reflash, lol nothing bricked yet.
If you look around on XDA you can find links. Get the exact stock rom needed for that device.
You can use a custom rom but it may end up being a Pandora's box of trouble. I run stock for a number of reasons.
Using the same rom be preferably first to ensure it was a corrupted rom.
Normally they don't become corrupted. Using a different rom introduces more variables. It could be a mobo failure in which case a custom rom might give you a work around for it or not depending what failed. It be nice to know the hardware is good from a troubleshooting prospective... and save you needless hair pulling.
A Samsung Experience Center at Best Buy might be a better option as they can reflash it to the original stock rom.
Hey, just thought I'd let you know that I found the stock rom and was able to flash it using Odin. Unfortunately, it didn't help, but something did change. Now the phone reboots every 30 seconds rather than every 1 min 48. That doesn't eliminate a firmware problem, but it also still could be hardware. Bummer. Thanks for your help and maybe I will try a non factory rom since I've got nothing to lose.
lapsmith said:
Hey, just thought I'd let you know that I found the stock rom and was able to flash it using Odin. Unfortunately, it didn't help, but something did change. Now the phone reboots every 30 seconds rather than every 1 min 48. That doesn't eliminate a firmware problem, but it also still could be hardware. Bummer. Thanks for your help and maybe I will try a non factory rom since I've got nothing to lose.
Click to expand...
Click to collapse
Developer options>running services, ram usage
Watch what ram memory is doing. If it dies at the same amount in use regardless of the rom version loaded, you got a bad ram chipset.
It may be a corruption of the bootloader files allocating memory, I don't know as it's beyond my knowledge base.
This sounds a lot like a memory issue though.
Memory allocation among processes | App quality | Android Developers
developer.android.com
Good point about the rom usage with the new vs. original rom load. Unfortunately, I didn't write down the memory usage before flashing. Now it uses about 1.8G of ram on average. The screen locks up just before the reboot so I don't see any memory spikes. Settings is using about 150M and one UI about 200
lapsmith said:
Good point about the rom usage with the new vs. original rom load. Unfortunately, I didn't write down the memory usage before flashing. Now it uses about 1.8G of ram on average. The screen locks up just before the reboot so I don't see any memory spikes. Settings is using about 150M and one UI about 200
Click to expand...
Click to collapse
Try opening some memory intensive apps and see that kills it quicker.
If you got a bad mobo better to known sooner than latter.
Good idea. I tried a few times but since the phone is fresh, there aren't many apps. I'll have to play around with it some more tomorrow. Have a good evening!
lapsmith said:
Good idea. I tried a few times but since the phone is fresh, there aren't many apps. I'll have to play around with it some more tomorrow. Have a good evening!
Click to expand...
Click to collapse
I think you're right about the memory. It works fine in recovery mode, which probably uses minimal memory. And the build I flashed is UI 2.5 whereas I think the old one was 2.0. I would imagine 2.5 is more memory intensive.
lapsmith said:
I think you're right about the memory. It works fine in recovery mode, which probably uses minimal memory. And the build I flashed is UI 2.5 whereas I think the old one was 2.0. I would imagine 2.5 is more memory intensive.
Click to expand...
Click to collapse
My only question if so, is could the bootloader have become corrupted and is somehow causing this rather than the hardware?
Just a guess... if it has basis in fact I don't know.