Related
I have had this phone for a while now and have had it rooted the entire time. Just recently (the last 3 -4 days) i have been getting continued calls on my phone from my number. And i cant figure out why. Im assuming it cant be me changing the build because it happened when i had cyanogen and still continues now i am on a hero build. Has anyone else had this issue and if so, some solutions would be great.
My CDMA Hero started rebooting randomly during the last week or so. I uninstalled all recently installed applications and the problem went away.
However ...
This has happened more than once, and it takes a lot of time to track down the offending app(s). I really want to know how to troubleshoot if this happens again.
If this were a Windows computer, I would go and get the minidump file and run it through windbg and it would suggest what module had caused the fault.
Is there anything like that for Hero crash / unexpected reboot? If not, what approach would you suggest for investigating these incidents?
Thanks,
Chris
Running DamageControl 2.08.1
Best thing i know to do is to run logcat with adb and try to recreate the problem.
Hard to repro...
Thanks, but the problem was so sporadic ... it would go hours, or even days, between reboots. Is it possible to use something like logcat to get the log files from *before* the current bootup?
im not that familiar with logcat, just search the string "Logcat Hero" on the Xda forums and you should be pointed in the right direction
Is there anything like /var/log/messages?
Thanks again. I went and looked at the logcat documentation and there are some options to get different kinds of output. However, I reset the phone (simulating a crash) and when that happened, the logs were cleared, so that there were no log entries visible via logcat that predated the shutdown.
Does anybody know where the actual log files are kept? There isn't a /var/log/messages or anything like that. Where do I find files equivalent to the "normal" Linux /var/log/messages?
Thanks,
Chris
Why my LG Optimus 2X freezes and/or reboot?
Most of us have the same problem, we are trying to find a solution. In the meanwhile we can solve only removing battery.
Is it related to baseband version?
It does not seem related to baseband version. The problem is present in last baseband versione too:
1035.21_210110405
FRG83G
V10b
Is it related to ROM Version?
Apparently it happens on both stock and custom ROMS
I read that it is due to wall charger problem
Some of us have the same problem recharging both from USB PC and Wall Charger
I read this is due to overheat problem
Some of us still have the problem in standby mode with battery under 25° C.
LG told me to ask for a replacement
Some of us did it and had the same issue on the replaced phone.
I read it is due to hidden menu/car navigation/ecc. ecc.
There are no prooves about it.
Could it be a ROOT problem?
No. Same thing happens on both rooted and original phones.
I got it. It's a SD problem
Some of us has this problem both with or without SD card
So it's a HW problem
We are not sure about it. Most of us (me too) think this is a SW related issue. Some other thinks about a HW one.
Anyway it looks like a Nvidia/Tegra related problem.
It happens on Motorola Atrix too:
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
So: what can I do?
Follow this thread and partecipate
Try to install latest version v10b and do a full reset.
Try to uninstall the "Any cut" application.
Try removing your SD.
NOTE: These are temporary solutions while we wait to understand something more.
Nothing else?
Sure, you can add informations here to keep updated the FAQs.
What about contacting LG?
It looks like something is moving and a new update will be released soon:
http://translate.google.com/transla...alligevel-problemer-med-optimus-2x,lid.15324/
Hey, new V10C is available. Does this solve?
Not sure yet. Some of us still have problems, but some others solved with this upgrade.
How can I help?
You can sign this petition on line
http://www.petitiononline.com/LGO2XPrb/petition.html
Last updated: Tue 7th July 2011
Mine has now shut down 3 times while i was in a call, battery pull on each occasion to rectify the problem
Added in the first question that pulling off the battery temporary solves.
1 week ago I do faced 2 time reboot each after receive sms during standby mood.
Dont know what happen.
Later I remember the reboot problem started after I had installed "Any cut" sw and started to activate the hidden menu.
Then I uninstall it and now haven facing any reboot no more.
Already 1 week pass and no reboot at all. I also never restart my O2X yet and seem everything is OK, no lag or etc on the system.
Hope this help.
Was using the original lg rom only for a good day and had one shutdown. Switched to custom rom and didnt have a reboot or shutdown yet in over a week. Appears to be software related.
Sent from my LG-P990 using XDA App
Useful topic, thanks!
My experience in 15 days of use.
with stock rom V10a and external sd:
- 1 time screen locked black in a warm day during standby
with stock rom V10a without external sd:
- many times screen locked black just after a notification (almost always after sms incoming notification)
with official rom V10b without hard reset and without external sd:
- 1 time reboot after pressing power button to exit from standby
- 2 times screen locked black the day after I've changed the useragent setting from the hiddenmenu and installed "AutomateIt" app
with official rom V10b after a hard reset 2 days ago and without external sd:
- no problem till now (2 days of use)
All the time I used both original charger (at home) and a generic usb adapter with an output current of 1mA (at office).
This is the sort of stuff that should be sent to LG to deal with. Not the idiots at call centres but the people who made the phone and get them to work on it.
Problem with these phone guys, they make a phone and then just stick out to the salesman and then when things like this happen to everyone we get no support or real contact.
It's always send it for repair. The phones are like a month old and that is really a valid response?
Time LG were held accountable (as well as other company's)
Ok, added some "Possible solutions"
Good thread, will hopefully cut down on some of the idle speculation that has been going on!
I believe that it is a software bug, namely in Nvidia's cpufreq-dvfsd driver. I saw this process misbehaving when doing a 'top' command via an ADB shell after it froze, and I'm not the only person to have witnessed that. I've posted that info over at MoDaCo.
As kholk is the only person other than Paul I know around here who might be familiar with a Linux kernel, I've asked him to take a look. Not sure what will come of that, if anything.
And just to add fuel to my argument that this is a Tegra/Nvidia issue, and *not* necessarily an LG one, check this out (from Moto Atrix forums):
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
Read from the postings that, for charger-specific reboot/lockup problem, it might be better charging from a computer USB port or a charger with lower current output (I think someone is using as low as 350mA).
Fyi, I've never had AnyCut installed and I've had these problems.
Yup, we do not have still found THE cause, but some events.
We are trying to understand if they are related to the issue.
I am reporting infos from the other thread and from this one to help people ti find a partial solution.
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
follo said:
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
Click to expand...
Click to collapse
Not necessarily. In embedded/real-time systems, timing is crucial and in some components varies according to manufacture tolerances, heat, etc. Also everybody's phone has different apps and they do things at different times so you can't say that everybody's phone is just "the same" as everyone else's.
And this bug could well be one that only happens for some very specific condition that the original developer didn't forsee when he wrote that code or tested it. But the law of chance means that so many of us are seeing it - some more than others, and some days worse than other days.
So this would explain why people think that doing something like switching launcher or taking out an SD card might be solving or making the problem worse, because every action can and does change the likelihood of this specific condition occurring by changing how the phone behaves overall, workload, sleep time, etc etc. And why all these "solutions" that people are posting are so random and unrelated but each person is convinced that theirs is the one that works!
Basically, we need more evidence from logs to see what is really going on...
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
mikeyd85 said:
Fyi, I've never had AnyCut installed and I've had these problems.
Click to expand...
Click to collapse
Im not an expert, but its work for me. I will keep you all updated if reboot happen again.
Edit: just having my FB hang in 15 second and force to close. This definately due to sw problem.
Sent from my LG-P990 using XDA App
i will believe only when i will see one
spawndk said:
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
Click to expand...
Click to collapse
they said that gingerbread update will be on 18 april to and didnt
They said jun/jul. Check out dk site.
lmerega said:
They said jun/jul. Check out dk site.
Click to expand...
Click to collapse
Well thats the most realistic schedule
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
Let me rewrite this in order to hope for a reply:
I'm running Venom One on my M7ATT. I've used both ElementalX and Bulletproof without issue, but I didn't get the battery life I wanted. I tried Franco, and it works great with one issue. Every few hours, when I would wake my phone up (more often when I had just shut it), I get either a solid-color screen, or a solid-color with a random stripe. The rest of the phone still works (I had music playing and it continued to.) My phone would require a hard reset, though, in order to get it back. Any thoughts as to what could have caused it?
Log File
I can't post links, so please copy and paste the below to view the file.
pastebin.com/HAQzDS14
Is there any chance it was the rom? I was using ViperOne. I'm now trying Android Revolution but don't want to flash the Kernel if I'm still going to have issues. Can anybody help me?
I'd post in the kernel thread, but I don't have that permission yet.