It is ok yesterday.
And I installed about 10 apps today and found that it will reboot if I lock the phone (the screen goes dark).
I don't remember the name of those apps.
So, how can I find out the problem of the certain app?
Must I uninstall all the apps to find out the problem?
THX!
If u go to the market and download a app called (instant uninstaller) it lets u choose to show the apps by date installed
Sent from my ADR6400L using XDA Premium App
thx！ let me try it.
So did this fix your issue? I am having the exact same problem.
I'm rooted (using ADB method), running Das BAMF 2.1 with Imoseyon's 2.54test4 kernel .
I can reproduce the a reboot everytime by doing this:
1. With the phone unplugged from the charger, press the lock button so the screen goes off. Once the screen goes off, in about 10 seconds it will reboot everytime.
2. Or, if I leave it set and the screen goes off by itself, it will reboot in about 10 seconds (after the screen goes off) everytime.
If I leave it on the charger, or never let the screen go off, it has never rebooted on me. I got this phone 2 days ago and have been battling it ever since.
UPDATE:
I have eliminated the following as a potential issue.
1. I wiped everything and flashed a new ROM, Kernal, and Radio, and still the exact same results.
2. I tried a new battery, and still the same results.
3. Tried two other kernals with each of the two ROMS, and still the same results.
Out of ideas at the moment.
Thinking of trying to flash back to stock so I can see if it still does it then.... Lost.
Solved my problem for now. Here is what I did.
1. Flashed back to these radios
CDMA: 1.13.605.7
LTE: 1.12.605.6
2. Flashed back to Froyo based ROM, Das BAMF 1.8.
Of course, I wiped everything before doing so. I've been up for about an hour now with my phone resting comfortably with no reboots at all.
Will try again in a few days to flash back to a gingerbread based rom, as I would really like to have Netflix.
If anyone has a gingerbread ROM and radio combo that they have working well together please let me know. You might also shout out which kernal you are using too.
UPDATE:
So I have obviously done some more troubleshooting on this, and I may have something to make sense of.
Since I flashed the GB MR2 radio and ThunderstickGB rom using the kernal provided with it. After bootup, I again had the reboot issues everytime the screen timed out or was locked. Just like before, It would reboot everytime unless the screen was kept on or plugged in to a charger.
I flashed back to the original Froyo radio just to see if that would make a change. Of course, I had no signal, but it would at least tell me if it were the newer MR2 or MR2.5 radios giving me fits. Even with the original radio, it still gave me the same reboots on screen timeout or locked.
So, I started over and this is what finally worked:
Flashed MR2 radio and ThunderstickGB rom again. This time, I flashed the stock GB kernal, instead of using a modified one. Bingo.... no reboots at all.
My feeling is that for some reason, some of the Kernals are undervolting the unit to a point that it shuts off or reboots. I am completely technically illiterate when it comes to the inner workings of Kernals and such, but the one common demoninator between my working Froyo and GB roms was that there was no Governor or Speed Tweak controlling the processor other than what comes in stock form.
Oh and by the way, thanks for eveyone's help with this.... I couldn't have done it without you.
Hello everyone,
Please help me solving this problem:
My X10i always stuck in boot loop whenever connect to 3G.
I've tried different SIM, ROMs and Google it but still no solution
Thank you!
Still no help?
Waiting...
I have a similar problem with my phone.
Regardless of the rom I'm using, my phone will go into a boot loop. Anywhere from 3 to 10 times before booting fully.
It doesn't seem to be any particular app or action and I don't use a task killer. Sometimes connecting to 3g will crash my phone and boot loop; other times it's attempting to delete an app or replying to a text message. Any sort of daily use can cause my phone to crash into a boot loop, which is usually remedied by taking my battery out, waiting, and putting it back in again. I'm fairly certain it's not an over heating issue because the battery and phone don't feel hot to the touch.
There seems to be no way to know when it will crash, however, it is more likely to do so if it's charging or I have my headphones in.
I've had this problem while using WB 2.2 rom, WB 2.3 rom (all versions) and EWjet 2.3 rom. I've Formatted everything I can, including the SD card.
I'm currently on a fresh install of WB 2.3 v3 and still getting the boot loop issue. This only started happening a month or so ago, so I'm beginning to think that this is a hardware issue and I may need to get my phone replaced.
Other information, I'm on Rogers and have owned my x10 for a little over 1 year, BaseBand 2.1.71, Kernel 2.6.29-00054-g5f01537, Build Number 3.0.1.G.75
I flashed the latest builds from both Coffebeans - http://forum.xda-developers.com/showthread.php?t=1547778 and Pershoot - http://droidbasement.com/galaxy/roms/cm9/p4wifi/ and I'm having the same issue with both of them. The problem is my Tab will randomly reboot then get stuck on the boot animation and just sit there forever. It's already happened twice now where my Tab rebooted sometime at night and sat at the boot animation until the battery was dead. I did do a full wipe before flashing.
Does anyone else have this issue?
Thanks.
i've ran both of those without any problems. did you come from another custom rom or from stock firmware?
foliage green said:
i've ran both of those without any problems. did you come from another custom rom or from stock firmware?
Click to expand...
Click to collapse
I came from Task650's version 14, but I've been flashing the CM9 KANGs for a while and haven't had this issue.
i have had some strange reboots...but never gotten stuck on the boot animation like that..thats the bad part about not having a battery to yank unfortunately
Sent from a Gtab 10.1 running Build 30
Well whenever I can't get something to work right, I Odin stock firmware on it and restart the custom rom process from scratch. Having a clean slate is time consuming and might not even be necessary but it's the only full proof way I can get things to work.
I wiped everything and also formatted /system in CWM and then flashed Coffeebeans latest build from 4/8. I haven't had the reboot and stuck boot animation issue, but now I'm having an issue where every time I charge the tab fully it won't wake up. I have to hold the power button to reboot it. It seems like it's the deep sleep issue, but it's been fine leaving it overnight as long as it's not connected to the charger.
Hi guys,
I have a huge problem. I had a stock GB firmware customized by Optus (carrier in Australia) on my S2 I then decided to change to the new ICS 4.0.4. I downloaded the stock unbranded firmware from SamMobile (Australia 2012 September 4.0.4 I9100XWLPW, I9100XSALP6, XSA) I updated using Odin. Before I did the update I reset the phone, did the update, it all went smoothly. After the update I reset the phone again and then proceeded to reinstall all my apps and restore my contacts, sms, etc.
The phone works and all functions on it work, however now very randomly the phone would totally freeze. The phone would be in standby, the screen would come on and it would be frozen. The screen stay on all the time and it does not respond at all. It will stay frozen until I restart the phone by pressing Home+power buttons to restart it.
After restart it all works fine for a few hours, sometimes a day and would just lock up again. The phone is not rooted and as I said i just changed the firmware from the Optus branded GB 2.3.6 to unbranded stock ICS 4.0.4 by using Odin.
Is there a way to find out what is causing the phone to lock up like that? Any suggestions would be helpful.
and then proceeded to reinstall all my apps and restore my contacts, sms, etc.
Click to expand...
Click to collapse
I hope you haven't restored any data app?
przemcio510 said:
I hope you haven't restored any data app?
Click to expand...
Click to collapse
I made sure that I didn't restore any data apps. The only apps that got restored are the ones that get automatically restored by Play store.
I have disabled the live wallpaper that I had and it seems to have stopped the freezing for the moment. I will report on what I find out.
In the mean time if anyone else has a similar issue or has a definite solution please let me know.
Thanks
i know this is a resurrection, but don't see it has been resolved.
also found same/similar problem on another topic, but no resolution either.
couldn't find any resolution anywhere on the net, but possibly i'm just missing it (searching for wrong parameters?)
anyway, a friend of mine bought second-hand (third or even fourth hand to be precise) i9100 with 2.3.6 (stock KI3) on it. the guy who sold it to him said something like: "it works best on 2.3, on 4.x it's buggy".
it was working fine, but friend wanted newer OS, so we tried update. it didn't work, and i found out CSC was broken/missing. somehow i managed to repair it, and update was finally working, but was unable to find any for our location.
so next step was to find stock rom that would work on the device, and then i tried four different 4.1.2 stock roms from this topic.
after flashing it through odin, every one was acting fine, until couple of minutes after it started freezing or rebooting randomly.
then i tried flashing CWM, and flashing from sd card, but it was all the same.
wiping data, cache and dalvik cache, prior to flashing. wiping data after flashing...
nothing seemed to work.
GB works rock solid, ICS works better than JB, but stills it freezes or restarts randomly.
tried CM10, but all the same, except it works a bit faster then official JB. but who cares about speed if it freezes/restarts constantly?
back to who knows which build... freeze... samsung galaxy s2 - i9100... with yellow triangle... booting stopped.
so i decided to dig deeper, trying to find hungarian stock build (country we were told the phone came from) not being sure that KI3 is what the phone came actually with. i found 4.0.3, put it on SD card, wiped data, cache, flashed CWM, wiped data, cache, dalvik cache, flashed 4.0.3 from sd, wiped data, booted, entered location for updates - hungary. update found, hooray... downloading... installing... rebooting... working?
nope... it's worse than ever. trying to log onto google account. typing in email add.... freeze... switching phone on - freeze... thinking about... freeze.
i couldn't sit still. yellow triangle, all those reboots/freezes... at least i wanted that triangle gone, and without a JIG, there was only solution for me was to try triangle away. it wasn't available for download in my country from play store, so luckily xda was there.
somehow i managed to download it from the device, install it, click remove the triangle... it did it's magic, rebooted... and miracle happened!
no more freezes.
so i started torturing poor phone, benchmarking, playing games, listening to music.... it seemed stable for about an hour.
so i said to myself:
- it's possible that previous owners tried to upgrade it to newer firmware, and somehow screwed up the bootloader, which was fixed by this app? maybe that was all there was from the beginning? why not try putting 4.1.2?
and i did... took 4.1.2 spanish build from already mentioned page above, flashed it... and voila. working JB... torturing the phone... playing with it... hour passes, another hour...
friend wakes up... takes his phone in awe, starts playing with it.. we talk a bit... and then that look it just froze again!
from that moment on, the phone again starts restarting or freezing randomly...
and, yes, i still have no clue what could be the cause. it doesn't matter if wifi is on or off, if you're talking on the phone or not, bluetooth and gps are always off. only thing that he noticed is that it usually happens while he's using the phone (meaning: operating the digitizer or buttons). if he starts music playback and not touching buttons or screen, it will probably play for hours.
one more thing, but i doubt it would be the case. the battery in the phone is not original one that was shipped with it, but a quality replacement.
it doesn't feel as if the phone is overheating... so i don't know what else i could do with it.
for now, it's back to 2.3.6.
we both lost a week, torturing ourselves with this problem.
i don't know is there anything i could add more?
all suggestions are welcome.
cheers
Maybe try kernel cleaning script and try philz or siyah kernels.
You shouldn't have to flash a custom kernel so your phone won't freeze, but yes, you could run a nuke script in order to wipe clean all custom ROM's leftovers.
Try flashin' jb via mobile odin, see if it keeps freezing up on you. If so, nuke it up.
Sent from the little guy
i'll try them out.
probably for the weekend, if not sooner. will report back here with info.
any other suggestions are also welcome.
thanks a lot.
cheers
ok, so here are some updates.
i finally got my hands back on my friends phone, and tried nuking remains of older flashes.
following that, i flashed stock spanish rom from above mentioned page, updated after installation to spanish update... and after a few minutes, sudden reboot...
so, went back to nuking, and flashed stock hungarian 4.0.3 i found elsewhere (mentioned in my earlier post. don't remember origin... if i find the link on another computer where i downloaded it on, i'll post the link). tried updating, says no updates found.
started torturing the device. it seemed solid, but battery reported it level was low, so hooked it up onto charger and all seemed well. but phone seemed a bit too hot.
after few minutes (this was all about half an hour to hour after flashing to 4.0.3), again freeze.
after rebooting the phone, battery was at 9%, as if processes were draining battery faster than charger recharged it.
so, i figured i gotta try original battery. so i switched his battery with genuine from my phone.
phone seems stable and less hot, for now.
still checking if it is going to freeze or reboot again.
it's about one hour since battery change. still on charger and using wifi and playing around with apps.
i'll check in with news later.
cheers
I have the same issue.but my battery is original.
What I noticed that the phone stuck when I receive an update notification.
Can I stop softwsre to ask for updates? ???
Sent from my GT-I9100G using xda app-developers app
^go to settings, about device, software update and detick auto update. that should stop it from trying to self-update.
ok, so here is an update to my friend's phone status.
currently on hungarian 4.0.3. about 3-4 freezes/reboots a day. sporadic connection breakups during calls. also, when we talk i can hear myself back. this brings me to conclusion it has to do with modem firmware. i found this topic, so i'll try putting that and see what will happen.
if that doesn't solve anything, my question is this: is there any way of knowing which firmware/rom was originally put on the device, since i don't know the real background of the device? i.e. some way of entering IMEI and finding out what should be on it?
cheers
EDIT: tried KH3 modem, no changes... i could still hear myself while talking to my friend on that device. also, it froze couple minutes later. going back to 2.3.5-2.3.6 for now.
so after couple of months, i finally got my hands back onto this phone...
gave my friend my phone, so i could play a bit with this faulty one.
i have played with it for a couple of days now, and here are things i've tried.
i received it from a friend with 2.3.5 on it which had triggered custom binary counter. he's been using it for couple months without any problems.
so i rooted it and installed triangle away again... reset counter, cleared and flashed hungarian stock (telenor) 4.1.2... random freezes again.
tried several stock roms, mostly hungarian ones (4.0.3, 4.1.2). even reformatted with .pit file... random freezes.
reformatted again with .pit and put XXLSJ, installed stability test and let it run...
cpu stability test 15.5 hours no problems, no freezes. then i realized it didn't have a sim card, so i rebooted phone and installed sim card. let it test cpu+gpu for 9 hours... no errors, no problems, no freezes.
so i thought, maybe it's all fine? but it wasn't! as soon as i took phone into my hands and started going through menus it froze!
so i tried SGII_repair, rooted and did "repair"... but nothing changed... still random freezes.
if i just let it do the stability test, it'll probably work forever.
things i've noticed:
- serial number is wrong format (14 hex digits instead of 11 alphanumeric)
- during stability test, cpu frequency dropped from 1200 to 800 mhz (maybe because it was getting warmer? 42-43C during cpu only+charging battery, and about 39-40 during cpu+gpu test)
i tried to find out which firmware is latest according to serial number via kies, but it gave me error.
i know it's from hungarian market, but don't know which exact part of it (branded or not).
don't know what previous owners did to it, and don't have backups of original efs or anything original.
i just want to make it work, don't care much about custom firmwares. i'd be happy even with unrooted stock... just for it to work!
i have no ideas what else to do.
anyone?
finally, as i couldn't resolve the problem, i returned phone to 2.3.5 and sold it as is.
thanks to all people who tried to help.
cheers
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
eranyanay said:
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
Click to expand...
Click to collapse
u can just rewert to stock ICS 4.0.3 firmware on both the phones and check for the issue (whether its firmware related or any hardware issue as such)
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
eranyanay said:
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
Click to expand...
Click to collapse
1) with 403 for some time once again to ensure no issues of freezing.
2)then a different 4.1.2 stock/custom rom altogether to check for the same(freezing) issue.
stay for some time on those firmwares and see (may be one or two charge cycles).
3) do not install any mods on top of the firmware, just stay stock and see
One of the devices is already back to 403, while the second one on stock 412
the hardest thing to tell if 403 solves it or not, as it happens occasionally, once in a week or two.
I tried two different stock roms, so that would rule out #2.
The weird thing is that wiping data is enough.
data is separated from the rom itself, yet it causes the entire device not to boot anymore.