[Q] What to do with /data/dontpanic/last_kmsg.txt ? - LG Optimus L9 P760, P765, P768, P769

Hi everyone,
Merry Christmas!
As usual, today I was using my phone normally. I put my phone into my pocket and started studying. Then, after a while, when I checked my mobile, it was showing a different screen.
Yes, it was same like this: http://img444.imageshack.us/img444/4103/20120503188.jpg
As it says, Dont panic, so I didn't thought much about this, and tried to Power off using Power button. It was not powering my phone off. So, I simply removed the battery and then restarted.
So, all I want to ask, what is this all about, and what kind of crash it is?
Ok, for your consideration, I am attaching the log file in this post.
Thank You
Best Regards,
THAKUR

It could be kernel related, could be software related, or could just be a random glitch. Report this error to the developer of the Rom on which it occurred.
Sent from my LG using Tapatalk

Related

turning off screen kills device

ive searched for things such as "sleep crash", "sleep bug", "screen wont turn on" etc. but can seem to find anything that tells me anything other than turn off wifi (which i tried to no avail). My issue is that when i press the power button for 1 second to turn off my archos 70 screen it will not turn back on. Same thing happens when i let it fall asleep. If i leave it plugged in and not allow it to turn off screen i have no issues. My apologies if i just don't know what words to search for ... i tried. In on the .4 firmware (latest) with no mods. This has happened through the last 3 firmwares from archos. Any ideas?
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Techngro said:
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Click to expand...
Click to collapse
I will try this and report back. I have been installing firmware over the issue
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
I am try before formatting and report back
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
this worked!!
mallman said:
this worked!!
Click to expand...
Click to collapse
spoke too soon. did not work. it stopped after a few tries
it works again if i recalibrate but wont hold.
Zoidpilot said:
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
Click to expand...
Click to collapse
by the way, the deep sleep option also kills mine.
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
ramso said:
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
Click to expand...
Click to collapse
just tried it . i hit the icon to disable sleeping. i pressed the screen button and when i went to turn screen back on it would not wake. Did i use the app wrong?
No, you use the app rigth. The app only disable deepsleep.
Sent from my A101IT using Tapatalk
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
bbop said:
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
Click to expand...
Click to collapse
err I'm afraid that I spoke too soo. My device keeps getting stuck and won't awake from sleep. This seems to happen most after switching wifi on or off, specifically whilst the device is playing music.
Zoidpilot said:
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
Click to expand...
Click to collapse
how are you installing the firmware? maybe im doing it wrong. I let the device update to latest 2.1.4 and then i wiped it via the settings and repair menu in android.
Edit**
like this??:
Step 1: Download the android 2.2 firmware for your archos tablet from here,you might a get a false positive notification from your browser as they are unaware of .AOS format, so ignore that and download it.
Step 2:Go to Menu > Settings > Device Storage & USB connection > USB connection mode of your tablet and set the connection mode to Mobile Media Device (MTP) and now connect your Tablet to pc.
Step 3:Now when the tablet is detected you will see a hard drive icon,double tap and open it and copy and paste the firmware (.AOS) file into the hard drive(make sure you dont copy it in any folder inside it like Music,Videos etc).
Unplug the USB connection and the Archos device will automatically locate the update file and will prompt you for the update,just follow the screen options and you are done,if it does not prompt you for an update then you might have accidentally misplaced the file in one of the folders,just locate the .AOS file from the file manager and and open it to start the update.
No no it wasn't that complicated... It was actually the simplest fix for a difficult problem. My device when I got it was running 2.1.2 out the box... Even then It had the screen problem. When I got the chance I installed 2.1.3 OVER THE AIR. Straight from Archos. Still had the issue though, I figured it would have been fixed but was greatly disappointed... Then I sort of just lived with the problem for awhile... I saw that the 2.1.4 update was released but was wary about downloading it because sooo many people are having issues. Just the other day though, the device cut off on me again and I figured to hell with it... So I downloaded the 2.1.4 OTA as well... no website, no manual install, I just let the device run its course on its own. After the update, it rebooted normally and it's been working great since... Sorry to hear not everyone is so fortunate... I really hope this helps somewhat

[Q] Hello, please help.

Hello.
I'm having problems with my Samsung GT-I9000 ( Galaxy S 1 ), and was hoping I could get some help here.
About 4 maybe 5 months my phone has been having crashes (Is as close as I can explain them)
This is what happens:
- Talking to somebody on Whatsapp (for example, but it also crashed on me while playing games, and even when calling)
- I lock the screen and lay the phone down
- After about 2-3 seconds, the screen lights up. And shows me the conversation but does not respond
- Phone goes black for about 5 seconds
- Light vibration
- Screen shows the lock screen, loads my background and scans for media
This happens randomly about 5-10 times a day now. (Depending on how much I use the phone)
It also sometimes just turns off without any animation or sound.
What have I tried:
I first thought it was the ROM, I'm sorry if I make mistakes here but I'm a noob.
The ROM was put on there by a friend of mine, it was called Darky's ROM.
I tried to put a differed ROM on it, but the tutorials failed on me and I killed the phone. Not the "Black screen of death" but beyond that point. It wouldn't even turn on anymore.
Then I send it back to the provider, they took 2 weeks to fix it and I had my phone back. I think they put the default ROM on it but I'm not sure.
Anyhow, this did not fix the problem. As soon as I had my phone back from repair, it still crashed.
I have also updated the phone with Samsung Kies, as shown in attachment 1
Now I don't know if I should send it back again, since they couldn't fix it in the first place, or to just live with it.
The phone's "About phone" page is attachment 2
Thanks everybody for taking the time to look into this.
It's the default ROM they put on again.
I have a friend with the same phone and her's is acting so slowly for such powerful device!
Try setting up a new ROM. I know it's hard, but it's better with the no-lag fix etc...
i heard Darky's Rom is really good, but I bet there are other ROMs who are amazing.
Tutorials are kinda hard to follow for that device, but you can do it
But putting a new ROM on it didn't help.
I can believe the default slows it down, but this problem started on the Darky's rom, and is also still happening with the default.
Is not so difficult, you can change a ROM in like 10min. Try to update your phone to ICS, I'm using ICSSGS and it's blazing fast
Enviado desde mi GT-I9000 usando Tapatalk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Thanks I missed that one.
And thanks Dante for trying to help, but as I said before, changing the ROM did not help, nor updating it.
Anybody else any ideas?
...anyone?

ICS (4.0.3) oficial ROM shutdown issue

Hi guys.
Im posting here because, after updating through Kies on a mac, other than sometimes slowish ui/loadings, i'm experiencing a shutdown whenever my phone goes to lock mode. Its not frequent. Sometimes i lock it, and after some minutes when i click pwer to bring up the lockscreen, nothing happens, and i have to hold the power (for a long time) to turn it back on.
Some info:
Previous version: gb 2.3.6 rooted
Baseband: XXLPS
first update was throuh wifi. Failed. Sencond by mac. Success.
If you guys could help me find a fix, or need more info, ill be very gratefull/happy to provide.
Thanks in advance
Sent from my GT-I9100 using XDA
Same problem but mine also shut down on gingerbread.I've booked mine in for repair
Sent from my GT-I9100 using xda premium
Erakk said:
Hi guys.
Im posting here because, after updating through Kies on a mac, other than sometimes slowish ui/loadings, i'm experiencing a shutdown whenever my phone goes to lock mode. Its not frequent. Sometimes i lock it, and after some minutes when i click pwer to bring up the lockscreen, nothing happens, and i have to hold the power (for a long time) to turn it back on.
Some info:
Previous version: gb 2.3.6 rooted
Baseband: XXLPS
first update was throuh wifi. Failed. Sencond by mac. Success.
If you guys could help me find a fix, or need more info, ill be very gratefull/happy to provide.
Thanks in advance
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
You could do a factory reset, that helps many times. Type *2767*3855# in the dial pad. Backup important files first.
Thanks. Will try that.
Sent from my GT-I9100 using XDA
Apps were my issue
gee2012 said:
You could do a factory reset, that helps many times. Type *2767*3855# in the dial pad. Backup important files first.
Click to expand...
Click to collapse
After updating my GT-I9100 from Gingerbread to the official ICS 4.0.3 ROM I experienced random shutdowns as aforementioned. I also had the screen freeze and become unresponsive. Screen unresponsiveness only occurred the first two days, random shutdowns occurred for about a week. After a slew of additional app update notifications and subsequent updating, I no longer have the shutdown problem either. I originally upgraded through Kies on 4/20/2012 and by around 4/27/2012 I no longer have any issues. Btw, I'm on ATT in the U.S. and my phone is not rooted.
I did a factory reset and i noticed some things:
Self shutdown occurred only once.
The phone touch is considerably faster than gb.
The screen visuals are more vivid (i think thats because of my current wallpapers)
The apps load times are also faster, but the camera takes some time to load.
Tl;dr
I dont regret the hard reset but the shutdown happened once only after that.
Sent from my GT-I9100 using XDA
Bad news... Shutdown twice this morning, after going into lock mode(click power button)
One thing i noticed is that he takes toooo muuucchhhh to boot when holding the power button when this hapens, so i have a theory that he actually doesnt shuts down, rather it jus wont turn on the screen. Im going to try to replicate it and send some kind of warning to one of my apps, or mail myself.
Sent from my GT-I9100 using XDA
Erakk said:
Bad news... Shutdown twice this morning, after going into lock mode(click power button)
One thing i noticed is that he takes toooo muuucchhhh to boot when holding the power button when this hapens, so i have a theory that he actually doesnt shuts down, rather it jus wont turn on the screen. Im going to try to replicate it and send some kind of warning to one of my apps, or mail myself.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Indeed, it is not shutting down, but not waking the screen. This is known as the "sleep of death" (SoD) and has been discussed in dozens of threads already.
Usually caused by undervolting with values that are too low, but also occurs on some peoples phones when they are completely stock.
Changing kernel can sometimes help, or if you already have a custom kernel loaded, changing your voltage settings to be a bit higher on the 800mhz step.
Erakk said:
Hi guys.
Im posting here because, after updating through Kies on a mac, other than sometimes slowish ui/loadings, i'm experiencing a shutdown whenever my phone goes to lock mode. Its not frequent. Sometimes i lock it, and after some minutes when i click pwer to bring up the lockscreen, nothing happens, and i have to hold the power (for a long time) to turn it back on.
Some info:
Previous version: gb 2.3.6 rooted
Baseband: XXLPS
first update was throuh wifi. Failed. Sencond by mac. Success.
If you guys could help me find a fix, or need more info, ill be very gratefull/happy to provide.
Thanks in advance
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
hallo,
there is a bug in the ics update to 4.0.3. phone crahes, will not shutdown and batterylife is very poor.
in holland are some problems. samsung advised not to update to ics.
goto: nu.nl, tech
greetings
@ctomgee
Thanks alot for the information!. I'll check about it. Now i know what's the problem's name.
Sent from my GT-I9100 using XDA

[Q] Auto Reboot on any rom

Hi everyone...
Some days ago, i was trying, OmniROM (http://forum.xda-developers.com/showthread.php?t=2544790). I follow all the steps and even get the superSU app going. One night, y saw how my nightly got updated, and in the morning, start to reboot randomly. If I push the power botton sometimes, doesn´t appear the blockscreen but the screen with the reboot option and turn off appear...
I put my cellphone back to stock with root using SuperOneClick from here: http://forum.xda-developers.com/showthread.php?t=1311081. Then, I format my sd card and internal storage...The problem persist...
I would like that someone help me, I'm tryin everything and didn't solve it...
Based on your description, it sounds like a hardware issue -more specifically, a failing power button.
I have read that some users were able to fix the issue by disassembling the phone and spraying out the switch with contact cleaner, and I have read that others had the power switch replaced altogether.
Hopefully others will chime-in with their thoughts.
Leo Dorado said:
Hi everyone...
Some days ago, i was trying, OmniROM (http://forum.xda-developers.com/showthread.php?t=2544790). I follow all the steps and even get the superSU app going. One night, y saw how my nightly got updated, and in the morning, start to reboot randomly. If I push the power botton sometimes, doesn´t appear the blockscreen but the screen with the reboot option and turn off appear...
I put my cellphone back to stock with root using SuperOneClick from here: http://forum.xda-developers.com/showthread.php?t=1311081. Then, I format my sd card and internal storage...The problem persist...
I would like that someone help me, I'm tryin everything and didn't solve it...
Click to expand...
Click to collapse
cyril279 said:
Based on your description, it sounds like a hardware issue -more specifically, a failing power button.
I have read that some users were able to fix the issue by disassembling the phone and spraying out the switch with contact cleaner, and I have read that others had the power switch replaced altogether.
Hopefully others will chime-in with their thoughts.
Click to expand...
Click to collapse
Well, i will try that. It's a shame that such a good cellphone have that problem... I really love it... Thanks for your answer.
Leo Dorado said:
Well, i will try that. It's a shame that such a good cellphone have that problem... I really love it... Thanks for your answer.
Click to expand...
Click to collapse
I had to replace my power button. this is a known issue with the s2.
I recommend this guy's services: http://stores.ebay.com/t989-refurb -- he can do the i777 even though it's not listed. He's a very nice guy and will do a fine job.
here's his video demonstration: http://www.youtube.com/watch?v=F0xMMn1DRWs

[Q] Unfortunately,android.process.acore has stopped

Hi guys,
This is my first post.
I just got a Sony Z2, and yesterday I updated it to latest firmware 17.1.1.A.0.402 using flashtool. After that, everytime when I switch off my phone and turn it on, the message of "...android.process.acore has stopped" appeared.
I tried to flashed the phone again using PC Companion to re-update the same firmware. I though the error message has gone but than it is still there.
I have tried several ways as mentioned in this forum but the problem seem to be there. I don't see any problem/error caused by this error message yet.
Any idea/solution to completely remove the message?
Go into settings > apps > all apps, clear all data for anything relating to contacts then all will be fine, make sure contacts are backed up tho of course
Sent from my D6503 using Tapatalk
I have tried and have not seen the message. Will keep you updated if it has conpletely gone
Sent from my D6503 using XDA Free mobile app
It should do it did for me glad I could help
Sent from my D6503 using Tapatalk
Update: It happened again when I reboot my phone today. Is it possible a firmware bug?
I should wait for the next release, hope Sony will fix this issue.
Regards,
I'm on romaur which is 402 and haven't seen this error since I wiped contacts data so not sure, you still on stock or?
Sent from my D6503 using Tapatalk
Same issue!
tuanph.aus said:
Hi guys,
This is my first post.
I just got a Sony Z2, and yesterday I updated it to latest firmware 17.1.1.A.0.402 using flashtool. After that, everytime when I switch off my phone and turn it on, the message of "...android.process.acore has stopped" appeared.
I tried to flashed the phone again using PC Companion to re-update the same firmware. I though the error message has gone but than it is still there.
I have tried several ways as mentioned in this forum but the problem seem to be there. I don't see any problem/error caused by this error message yet.
Any idea/solution to completely remove the message?
Click to expand...
Click to collapse
I also have the same issue as the OP. It particularly happened after I upgraded to .402 using PC companion.The message will appear always after restarting. My devices has not been rooted. Tried to clear data and cache for contact apps, but after restarting, the message appeared again. I am still lazy to do a re-install because aside from the message appearing only after a restart, there are no other major effect to my Z2's performance. but clearing it will be nice though.
I have the same thing when i touch the phone immediatly when it just restarted, but when i restart and leave it untill screen goes off i don't get the message.
Sent from my Xperia Z2 with the use of Tapatalk
phscyiipfer said:
I also have the same issue as the OP. It particularly happened after I upgraded to .402 using PC companion.The message will appear always after restarting. My devices has not been rooted. Tried to clear data and cache for contact apps, but after restarting, the message appeared again. I am still lazy to do a re-install because aside from the message appearing only after a restart, there are no other major effect to my Z2's performance. but clearing it will be nice though.
Click to expand...
Click to collapse
Mafiatounes said:
I have the same thing when i touch the phone immediatly when it just restarted, but when i restart and leave it untill screen goes off i don't get the message.
Sent from my Xperia Z2 with the use of Tapatalk
Click to expand...
Click to collapse
Hi guys,
Thank you for your info.
I tried to disable contact sync of Viber and I think the message has temporarily gone. Sometimes it still pop up but not as often as before I disabled the contact sync of Viber.
Apparently, this problem is caused by contact synchronisation between Viber, Facebook, Messenger, Whatsapp, etc. Other users, such as Samsung phone users, reported that they have the same issue but when they turned off contact sync of the above-mentioned apps, the error message somehow has gone.
To be honest, I have just recently switched to android from iPhone, and I have been usings iOS for years and never seen any kind of issue/error like this on iOS. However, Sony Z2 is one of the greatest phone I ever owned and I am so happy with it, specially its crazy battery life.
Hope you guys will share your solution here if someone can fix it permanently.
Cheers,
tuanph.aus said:
Hi guys,
This is my first post.
I just got a Sony Z2, and yesterday I updated it to latest firmware 17.1.1.A.0.402 using flashtool. After that, everytime when I switch off my phone and turn it on, the message of "...android.process.acore has stopped" appeared.
I tried to flashed the phone again using PC Companion to re-update the same firmware. I though the error message has gone but than it is still there.
I have tried several ways as mentioned in this forum but the problem seem to be there. I don't see any problem/error caused by this error message yet.
Any idea/solution to completely remove the message?
Click to expand...
Click to collapse
Running any Xposed Mods ?
defsix said:
Running any Xposed Mods ?
Click to expand...
Click to collapse
Nope, running original stock firmware. No jailbreak/root.
Cheers,
Update 13.06.2014: Guys, I have tried and flashed my Z2 with UK .402 and so far so good, I dont see that error message pop-up again after reboot.
Regards,
possible fix
i had this problem, amongst others stopping my phone. i pulled the sim card out, then rebooted the phone. the phone then showed it was updating all apps i let it boot up and it seemed to work. pulled battery and put sim card back in. and all ok so far. i have sent my phone 3 times away to vodafone for this repair, with android.clock stopping, android.phone stopped working and the phone actually crashing on the samsung screen and not even booting up. each time all they do is a factory reset. like duhhhh, i have never thought of that (sarcasm). i am hoping that doing this, will give my phone some sort of permanency in it's repair. i have not rooted the phone, it is stock.
Vodofone refused to replace the handset even though it had been in so many times for repair. word of advice. steer clear of vodafone. i am cancelling all my contracts with them.
sorry that went off topic, but i want a phone that works and vodafone will not help you in that matter.
tbish said:
i had this problem, amongst others stopping my phone. i pulled the sim card out, then rebooted the phone. the phone then showed it was updating all apps i let it boot up and it seemed to work. pulled battery and put sim card back in. and all ok so far. i have sent my phone 3 times away to vodafone for this repair, with android.clock stopping, android.phone stopped working and the phone actually crashing on the samsung screen and not even booting up. each time all they do is a factory reset. like duhhhh, i have never thought of that (sarcasm). i am hoping that doing this, will give my phone some sort of permanency in it's repair. i have not rooted the phone, it is stock.
Vodofone refused to replace the handset even though it had been in so many times for repair. word of advice. steer clear of vodafone. i am cancelling all my contracts with them.
sorry that went off topic, but i want a phone that works and vodafone will not help you in that matter.
Click to expand...
Click to collapse
Xperia's have unremovable batteries, maybe you should steer clear of Samsungs
Is that a good thing or a bad thing though? Cos sometimes taking a battery out is what could be needed to fix a problem.
But point taken. Perhaps a change of manufacturer would help
Sent from my GT-I9300 using XDA Free mobile app
tbish said:
Is that a good thing or a bad thing though? Cos sometimes taking a battery out is what could be needed to fix a problem.
But point taken. Perhaps a change of manufacturer would help
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
I know people who advocated pulling the battery from devices as the only answer but I've yet to come across a situation on any device which couldn't be handled with >adb reboot or a three finger reset.
There's actually a method on Xperia devices, to disconnect the battery and plug it back. It's called "Hard Reset". Yeah you don't take the battery out in reality, but this method does it in Matrix dimension. So, the consequences are the same.

Categories

Resources